Business Process Modeling – A Perspective

Lets start with some definitions first :

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

Process : A series of actions, adjustments, or features bringing a few consequence: e.g. the process of digestion; the process of obtaining a driver’s license.

Model : A schematic description of a system, idea, or phenomenon that accounts for its identified or inferred properties and may be used for further examine of its traits: e.g. a mannequin of generative grammar;

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

So Enterprise Process Modelling can be defined as a schematic illustration of activities and capabilities carried out by a company to achieve success of their trade and services offered to the market and customers.

I am certain that there can be plenty of gaps in above definition, if we try to make it full however one thing could be inferred clearly : For a Business to go about doing its enterprise and supply the suitable companies and merchandise to its buyer, its understanding and control on how they carry out and operate is important and infact in current age, a competitive edge.

Hence, Enterprise Process Modeling may be viewed as a really important activity both from a business and technology perspective. The reasons for doing process modelling can be many, however we are able to define the same into following:

Process Documentation : Need for group to doc their enterprise processes

Process Improvement Train: Organizations looking for performing an analysis of current processes and how the same may be improved. Process modeling here can be just a part of the approach in this case. Typically a BPI exercise would contain evaluation of current as-is process, refinement of processes based mostly on six sigma, lean etc. and popping out with a revise To-BE process.

Enterprise Techniques Implementation : Although some may call it a myopic view to process modeling, nevertheless traditionally and even at the moment many organizations have perform process modeling work earlier than implementation of major IT system for e.g. ERP, CRM, Order Management systems etc. This definetely is a smart alternative considering that most of the enterprise systems being deployed has an impact on the way you carry out what you are promoting going forward. Once more details of best practices in this space could be a separate dialogue itself. Particularly the discussion round need for doing process modeling/evaluation first or selecting the programs and then pursuing process modeling. I had a discussion with one in every of my clients once in which it was latter and my fundamental question was now will you alter your process for the system or vice versa and whether the whole selection of the system would have been totally different in the event that they already had an idea of their processes which needed automation help. Anyways there are pitfalls each sides.

Enterprise Architecture : Many organizations have a separate Enterprise Architecture practices and one space of EA is Process/Business Architecture. So organizations do perform process modeling work as a standalone side to achieve an honest view. However in this case process modeling could possibly be a very abstract representation of processes due to the high degree view typically required from EA viewpoint. Organizations might go into particulars, but in my expertise its not simple to get funding for doing Process modeling work just as a project with out linking it to some specific business associated project/budget. Thats a pity, typically as EA groups can add real value given the assets to do detailed evaluation of Enterprise’s architecture. Infact with SOA changing into essential strategy within many EA groups, I think process modeling intimately provide greater worth and help in figuring out the right service mapping.

BPM : Process modeling is also the place to begin for a Enterprise Process Management projects. Typically BPM tools will provide their very own modeling tools, so care must be taken to identify the necessity for process modeling. Whether or not it needs to be only for the actual BPM projects or its maintained in some bigger/central process repository. I want a central Process repository for all process models for e.g. in tools like Telelogic system architect, aris, case sensible etc. and picking out process for BPM implementations from central repository or better still create BPEL from the process models directly. Nevertheless this facet of product integration is not probably the most mature and care is required earlier than use.

Ok, I’m positive there are lots of more advantages of process modeling and I would get time later to elaborate in different articles/blogs.

Lets move into some elements of the right way to build higher process models. Among the pre-requisites for process modeling are as follows:

1) Folks: It’s worthwhile to have good skills within the workforce from various perspectives, you need good enterprise analysts to undertand what needs to be modeled and interact with enterprise customers accordingly. You also want an excellent scribe or modeler who understands tips on how to map the requirements into models. As we are limiting it to modeling area, you might not require folks with six sigma, lean,simulation expertise although they would take part at appropriate phase in analysis.

2) Instruments : you would want appropriate instruments to mannequin the managing business process processes. It could start with primary word processing instruments like word, move into graphic tools like visio to sophisticated tools like aris, system architect. Alternative of instruments would rely upon requirements and targets for modeling and clearly other factors like cost, talent sets etc. I personally really feel that modeling efforts in instruments like word and visio is a myopic view to modeling and processes are belongings of any organizations and must be available centrally to be up to date constantly. You need to consider a repository based mostly device which helps normal modeling and reporting methods to supply long run benefits.