<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Workflow Process Visibility

Posted by Kevin Sweeney on Jun 6, 2012 7:36:02 AM



Process Visibility Process Visibility Builds User Workflow Knowledge


Converting existing partially automated or entirely manual workflow processes into a fully automated Business Process Management (BPM) solution may be accomplished in a number of ways.  Traditionally these BPM Workflow implementations are initially designed so that they mirror the existing either partially automated or entirely manual workflow processes.

The reason for this implementation plan is that following what is familiar to the user community builds upon common knowledge, process visibility.   It is this process vision or process visibility that enables the user to efficiently gain workflow knowledge when operating both the automated BPM solution and the manual systems in parallel.

As time passes and the BPM workflow processes become the accepted standard, users implement workflow changes based upon their new workflow process visibility.   At this stage the process visibility has more workflow data for the user to consider.  The addition of BPM business intelligence (BI) information points out efficiencies or bottlenecks within the process.  Armed with BPM historical BI data the organization further develops the workflow, removing additional manual data entry points.  And the cycle of continuous improvement based upon the users business needs and process visibility begins again.

For example,  when a product is received at the warehouse, a person would complete the paper work and update the inventory count and updating or checking its physical location.  With an BPM workflow process in place, inventory information could be automatically updated based upon workflow input from a bar code scanner.

Process vision or process visibility aligns more with manual processes that can be automated and does not follow the manual process exactly.  For example, a Change Notice process that is currently a manual process, has been studied at length by our client.  They have determined that the manual process has one major flaw that is effecting all aspects of their business.  The overall problem with the Change Notice workflow is that it is heavily laden with process bottlenecks causing a cycle time that is excessive and unacceptable.  With the cDevWorkflow automated workflow process for Change Notice, these time factors disappear mainly due to the user having immediate access to the Change Notice information.  Processes such as this Change Notice process can expect to realize improvement when automated and the BI data will capture your gains.

One of our Medical device clients historically processed an average of forty (40) Change Notices per month; today with an automated process they can process an average of 400 per month.  These results were not achieved over night.  They were achieved with a clear process vision or process visibility concerning what needed to be automated and then analysis of BI from runtime execution and last moving to optimize the process.

A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.

[hs_form id="9"]

Learn more about our Process Automation & IT, QA Services or Software Development products and solutions on the Web!  Visit us at: Innovative Process Solutions

Topics: workflow process graphic, bpm process, workflow process diagram, workflow process monitor, process visibility, Blog, process vision, knowledge management