Lets start with some definitions first :
Business : The occupation, work, or trade in which an individual is engaged: e.g. the wholesale meals business.
Process : A sequence of actions, modifications, or functions 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 could also 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 outlined as a schematic representation of actions and capabilities performed by an organization to achieve success of their trade and companies offered to the market and customers.
I am positive that there could be loads of gaps in above definition, if we try to make it full however one thing may be inferred clearly : For a Enterprise to go about doing its enterprise and supply the fitting services and merchandise to its customer, its understanding and control on how they carry out and operate is crucial and infact in present age, a competitive edge.
Hence, business architecture Process Modeling could be viewed as a very vital exercise both from a business and expertise perspective. The reasons for doing process modelling can be many, but we will define the same into following:
Process Documentation : Want for organization to doc their business processes
Process Improvement Train: Organizations on the lookout for performing an evaluation of present processes and how the same may be improved. Process modeling here could be just a part of the approach in this case. Typically a BPI activity would contain analysis of present as-is process, refinement of processes based on six sigma, lean etc. and coming out with a revise To-BE process.
Enterprise Techniques Implementation : Although some may call it a myopic view to process modeling, nonetheless traditionally and even today many organizations have perform process modeling work before implementation of main IT system for e.g. ERP, CRM, Order Management systems etc. This definetely is a wise alternative considering that a lot of the enterprise programs being deployed has an impact on the way you carry out your corporation going forward. Again particulars of greatest practices in this house could be a separate dialogue itself. Particularly the discussion round need for doing process modeling/analysis first or selecting the techniques after which pursuing process modeling. I had a discussion with considered one of my purchasers once in which it was latter and my fundamental query was now will you alter your process for the system or vice versa and whether or not the whole alternative of the system would have been completely different in the event that they already had an thought 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/Enterprise Architecture. So organizations do perform process modeling work as a standalone aspect to achieve an honest view. Nonetheless in this case process modeling could be a very summary illustration of processes because of the high stage view typically required from EA viewpoint. Organizations could go into particulars, however in my expertise its not easy 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, typically as EA groups can add real value given the assets to do detailed evaluation of Enterprise’s architecture. Infact with SOA becoming essential approach within many EA teams, I think process modeling intimately present higher value and assist in figuring out the proper service mapping.
BPM : Process modeling can be the place to begin for a Business Process Management projects. Typically BPM instruments will present their own modeling instruments, so care have to be taken to establish the need for process modeling. Whether it must be just for the particular BPM projects or its maintained in some greater/central process repository. I choose a central Process repository for all process models for e.g. in instruments like Telelogic system architect, aris, case wise etc. and picking out process for BPM implementations from central repository or higher nonetheless create BPEL from the process models directly. Nevertheless this aspect of product integration shouldn’t be essentially the most mature and care is needed before use.
Okay, I am sure there are numerous more benefits of process modeling and I would get time later to elaborate in other articles/blogs.
Lets move into some features of methods to build higher process models. Some of the pre-requisites for process modeling are as follows:
1) People: You must have good skills within the crew from various perspectives, you want good enterprise analysts to undertand what must be modeled and have interaction with enterprise customers accordingly. You also need a good scribe or modeler who understands how you can map the requirements into models. As we’re limiting it to modeling house, chances are you’ll not require people with six sigma, lean,simulation expertise although they would participate at acceptable phase in analysis.
2) Instruments : you would want applicable tools to model the business processes. It might start with primary word processing instruments like word, move into graphic tools like visio to sophisticated tools like aris, system architect. Choice of instruments would depend on requirements and targets for modeling and obviously different factors like price, skill sets etc. I personally really feel that modeling efforts in tools like word and visio is a myopic view to modeling and processes are belongings of any organizations and ought to be available centrally to be updated constantly. It is best to consider a repository based tool which supports commonplace modeling and reporting methods to provide long term benefits.