Dilemma between automation and manual execution is always a challenge for correct management decisions. It is not easy to decide, if an investment to automate a process will bring sufficient benefits and returns, especially, on a long term.
However, decision here should not be voluntary. There exist simple and reliable criteria to clearly distinguish relevance of process automation in every practical case. The criteria is process volatility. Volatile processes are difficult and impractical to automate.
Volatility of the process is easy to measure. Record multiple execution paths of the process. Build an average execution path. Measure deviations of each execution from the average. Measure volatility as median of these deviations. This will give uniform and universal criteria for processes of any nature and scale.
As a rule, volatile processes appear in new and actively developing business areas. With time, these processes become a routine and acquire better formalization. When formalization grows and volatility drops below certain level, it is clear evidence that a process is mature and stable enough to automate.
Primary features of BPMN.Sharp: Full conformance to the latest version of BPMN 2.0 specification by OMG . Import models from all major BPM vendors Strict validation of the model according to BPMN specification. Arbitrary scaling and zooming view of most complex diagrams. Support of raster and vector image output. Batch processing of multiple BPMN files. Simple API to create and edit BPMN models. 100% Microsoft .NET managed solution. Loyal open source license for private and commercial use. Grab your copy on NuGet for one-click inclusion into your solution and quick BPMN enablement. Find more details, demo project and commented code samples on GitHub .
Comments
Post a Comment