Business Process Modeling – A Perspective

Lets start with some definitions first :

Enterprise : The occupation, work, or trade in which an individual is engaged: e.g. the wholesale meals business.

Process : A collection of actions, adjustments, or functions bringing a few result: e.g. the process of digestion; the process of acquiring a driver’s license.

Mannequin : A schematic description of a system, principle, or phenomenon that accounts for its recognized or inferred properties and could also be used for additional examine of its traits: e.g. a model of generative grammar;

“cited from : process. (n.d.). The American Heritage® Dictionary of the English Language, Fourth Edition. Retrieved April 30, 2007, from Dictionary.com internetsite”

So Enterprise Process Modelling might be outlined as a schematic illustration of actions and functions performed by an organization to achieve success of their trade and services offered to the market and customers.

I’m positive that there would be a number of gaps in above definition, if we try and make it complete but one thing could be inferred clearly : For a Enterprise to go about doing its enterprise and provide the proper services and products to its buyer, its understanding and control on how they carry out and operate is crucial and infact in current age, a aggressive edge.

Therefore, Enterprise Process Modeling can be seen as a really crucial activity both from a enterprise and technology perspective. The reasons for doing process modelling can be many, however we are able to define the identical into following:

Process Documentation : Need for organization to document their business processes

Process Improvement Exercise: Organizations in search of performing an evaluation of present processes and the way the same could be improved. Process modeling here can be just part of the strategy in this case. Typically a BPI exercise would involve evaluation of current as-is process, refinement of processes based on six sigma, lean etc. and popping out with a revise To-BE process.

Enterprise Techniques Implementation : Although some might call it a myopic view to process modeling, nevertheless traditionally and even right now many organizations have carry out process modeling work before implementation of major IT system for e.g. ERP, CRM, Order Administration methods etc. This definetely is a wise choice considering that most of the enterprise methods being deployed has an impact on the way you carry out your corporation going forward. Once more details of best practices in this space is usually a separate dialogue itself. Especially the discussion around need for doing process modeling/evaluation first or selecting the programs after which pursuing process modeling. I had a discussion with one of my purchasers as soon as in which it was latter and my fundamental query was now will you change your process for the system or vice versa and whether the whole choice of the system would have been different in the event that they already had an thought of their processes which needed automation help. In any case there are pitfalls each sides.

Enterprise Architecture : Many organizations have a separate Enterprise Architecture practices and one area of EA is Process/Enterprise Architecture. So organizations do perform process modeling work as a standalone aspect to achieve a decent view. However in this case process modeling could be a really abstract representation of processes due to the high level view typically required from EA viewpoint. Organizations may go into particulars, but in my experience its not easy to get funding for doing Process modeling work just as a project without linking it to some particular enterprise related project/budget. Thats a pity, generally as EA teams can add real value given the sources to do detailed evaluation of Enterprise’s architecture. Infact with SOA turning into essential method within many EA groups, I think process modeling intimately present larger value and assist in identifying the correct service mapping.

BPM : Process modeling can also be the starting point for a Business Process Management projects. Typically BPM instruments will present their own modeling tools, so care have to be taken to identify the necessity for process modeling. Whether it ought to be just for the actual BPM projects or its maintained in some greater/central process repository. I favor a central Process repository for all process fashions for e.g. in instruments like Telelogic system architect, aris, case sensible etc. and picking out process for BPM implementations from central repository or higher nonetheless create BPEL from the process models directly. Nevertheless this side of product integration just isn’t the most mature and care is needed earlier than use.

Okay, I’m certain there are a lot of more advantages of process modeling and I would get time later to elaborate in other articles/blogs.

Lets move into some points of how you can build better process models. Some of the pre-requisites for process modeling are as follows:

1) Individuals: It’s good to have good abilities within the group from numerous views, you want good enterprise analysts to undertand what needs to be modeled and interact with enterprise customers accordingly. You also need a good scribe or modeler who understands learn how to map the requirements into models. As we are limiting it to modeling space, you may not require individuals with six sigma, lean,simulation skills although they would take part at acceptable part in analysis.

2) Instruments : you would want acceptable instruments to mannequin the business process modeling notation processes. It may begin with basic word processing tools like word, move into graphic tools like visio to sophisticated tools like aris, system architect. Selection of tools would rely upon requirements and aims for modeling and obviously other factors like price, skill units etc. I personally feel that modeling efforts in tools like word and visio is a myopic view to modeling and processes are assets of any organizations and must be available centrally to be updated constantly. You need to consider a repository primarily based software which helps customary modeling and reporting techniques to provide long run benefits.