Lets start with some definitions first :
Business : The occupation, work, or trade in which an individual is engaged: e.g. the wholesale food business.
Process : A series of actions, adjustments, or functions bringing a couple of outcome: e.g. the process of digestion; the process of acquiring a driver’s license.
Model : A schematic description of a system, concept, or phenomenon that accounts for its recognized or inferred properties and could also be used for additional research 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 Dictionary.com internetsite”
So Enterprise Process Modelling will be defined as a schematic illustration of actions and functions carried out by an organization to achieve success in their trade and providers offered to the market and customers.
I’m positive that there would be plenty of gaps in above definition, if we try to make it complete but one thing may be inferred clearly : For a Enterprise to go about doing its enterprise and supply the proper providers and merchandise to its buyer, its understanding and control on how they carry out and operate is important and infact in current age, a aggressive edge.
Therefore, Enterprise Process Modeling may be considered as a really critical exercise each from a enterprise and technology perspective. The reasons for doing process modelling may be many, however we can outline the identical into following:
Process Documentation : Want for organization to doc their enterprise processes
Process Improvement Exercise: Organizations on the lookout for performing an analysis of current processes and the way the identical could be improved. Process modeling here could 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 primarily 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 right this moment many organizations have carry out process modeling work before implementation of main IT system for e.g. ERP, CRM, Order Administration methods etc. This definetely is a wise choice considering that most of the enterprise programs being deployed has an impact on the way you perform your corporation going forward. Once more details of finest practices in this house could be a separate dialogue itself. Especially the dialogue round need for doing process modeling/evaluation first or selecting the systems after which pursuing process modeling. I had a dialogue with one in all my clients as soon as in which it was latter and my fundamental query was now will you modify your process for the system or vice versa and whether or not the whole choice of the system would have been completely different if they already had an concept 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 area of EA is Process/Enterprise Architecture. So organizations do perform process modeling work as a standalone side to achieve a good view. Nonetheless in this case process modeling may very well be a very abstract representation of processes as a result of high degree view typically required from EA viewpoint. Organizations may go into particulars, but 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 business related project/budget. Thats a pity, generally as EA groups can add real worth given the sources to do detailed analysis of Enterprise’s architecture. Infact with SOA turning into essential method within many EA teams, I think process modeling in detail provide larger value and help in figuring out the right service mapping.
BPM : Process modeling is also the starting point for a Business Process Management projects. Typically BPM tools will provide their own modeling instruments, so care have to be taken to determine the need for process modeling. Whether it must be just for the actual BPM projects or its maintained in some larger/central process repository. I want 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 still create BPEL from the process fashions directly. Nevertheless this facet of product integration is just not essentially the most mature and care is required earlier than use.
Ok, I am certain there are a lot of more advantages of process modeling and I might get time later to elaborate in other articles/blogs.
Lets move into some features of the way to build higher process models. Some of the pre-requisites for process modeling are as follows:
1) People: That you must have good expertise within the staff from various views, you want good business analysts to undertand what needs to be modeled and engage with business users accordingly. You also want a good scribe or modeler who understands methods to map the necessities 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’d participate at acceptable phase in analysis.
2) Instruments : you would want acceptable tools to model the business enterprise processes. It may start with primary word processing instruments like word, move into graphic instruments like visio to sophisticated instruments like aris, system architect. Selection of instruments would rely upon requirements and aims for modeling and clearly different factors like value, talent units etc. I personally feel that modeling efforts in tools like word and visio is a myopic view to modeling and processes are belongings of any organizations and should be available centrally to be updated constantly. It is best to consider a repository based mostly instrument which supports commonplace modeling and reporting strategies to provide long run benefits.