Lets begin with some definitions first :
Business : The occupation, work, or trade in which an individual is engaged: e.g. the wholesale food business.
Process : A collection of actions, changes, or functions bringing a couple of end result: 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 recognized or inferred properties and may be used for further study 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 website”
So Enterprise Process Modelling could be defined as a schematic representation of activities and functions carried out by a corporation to achieve success of their trade and providers offered to the market and customers.
I am positive that there would be quite a lot of gaps in above definition, if we try to make it complete but one thing might be inferred clearly : For a Enterprise to go about doing its business and supply the best providers and merchandise to its buyer, its understanding and management on how they perform and operate is important and infact in current age, a competitive edge.
Hence, Business Process Modeling can be seen as a really important activity both from a enterprise and technology perspective. The reasons for doing process modelling will be many, but we will define the identical into following:
Process Documentation : Need for group to doc their enterprise processes
Process Improvement Exercise: Organizations in search of performing an evaluation of current processes and how the identical will be improved. Process modeling here would be just part of the method in this case. Typically a BPI activity would contain evaluation of present as-is process, refinement of processes based on six sigma, lean etc. and coming out with a revise To-BE process.
Enterprise Programs Implementation : Though some might call it a myopic view to process modeling, however traditionally and even at present 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 sensible alternative considering that most of the enterprise programs being deployed has an impact on how you perform your small business going forward. Once more details of finest practices in this house could be a separate discussion itself. Especially the dialogue round need for doing process modeling/evaluation first or selecting the systems after which pursuing process modeling. I had a discussion with one among my clients as soon as in which it was latter and my elementary question was now will you alter your process for the system or vice versa and whether or not the whole choice of the system would have been different in the event that they already had an thought of their processes which wanted automation help. Anyhow there are pitfalls both 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 a good view. Nevertheless in this case process modeling could possibly be a very summary illustration of processes due to the high level view typically required from EA viewpoint. Organizations might go into details, however in my expertise its not straightforward to get funding for doing Process modeling work just as a project with out linking it to some specific enterprise associated project/budget. Thats a pity, sometimes as EA groups can add real worth given the resources to do detailed analysis of Enterprise’s architecture. Infact with SOA changing into important approach within many EA groups, I think process modeling in detail provide larger value and assist in identifying the proper service mapping.
BPM : Process modeling can be the place to begin for a Enterprise Process Management projects. Typically BPM instruments will present their own modeling tools, so care should be taken to determine the necessity for process modeling. Whether it needs to be just for the particular BPM projects or its maintained in some bigger/central process repository. I favor a central Process repository for all process fashions for e.g. in instruments like Telelogic system architect, aris, case wise etc. and picking out process for BPM implementations from central repository or better still create BPEL from the process models directly. However this side of product integration will not be essentially the most mature and care is needed before use.
Ok, I’m certain there are lots of more advantages of process modeling and I would get time later to elaborate in other articles/blogs.
Lets move into some elements of how one can build higher process models. A number of the pre-requisites for process modeling are as follows:
1) Folks: You need to have good abilities within the staff from various perspectives, you want good business analysts to undertand what must be modeled and have interaction with enterprise users accordingly. You also need a very good scribe or modeler who understands find out how to map the requirements into models. As we are limiting it to modeling house, it’s possible you’ll not require people with six sigma, lean,simulation expertise although they would participate at appropriate phase in analysis.
2) Instruments : you would want acceptable instruments to mannequin the business processes. It could start with fundamental word processing tools like word, move into graphic instruments like visio to sophisticated tools like aris, system architect. Choice of tools would depend on necessities and objectives for modeling and obviously different factors like price, ability units etc. I personally feel that modeling efforts in instruments like word and visio is a myopic view to modeling and processes are belongings of any organizations and needs to be available centrally to be updated constantly. You need to consider a repository primarily based software which helps normal modeling and reporting strategies to offer long term benefits.