This paper, based on a webinar by BPM analyst and blogger Sandy Kemsley, provides a
product-agnostic, in-depth look at process modeling, including:
Identifying process initiation points
Identifying touchpoints with other systems – for example, how BPM and SOA
Simulating a new process
Process modeling notation and standards – what can be modeled?
Identifying changing job roles
Creating a structured model for implementation
Identifying where ROI will be generated and how to track it
BUSINESS PROCESS MODELING
What’s in Your Process?
Every process needs to start somewhere, and one of the things you need to do when
modeling processes is to determine how your processes get kicked off.
Kicking It Off
There are various ways a process might get kicked off, including:
invoked as web service
An example of human intervention is a person fills out a form about a problem they’re
having and clicks submit. The process is kicked off by a person’s explicit action, but the
person who causes the process to start may not be in the BPM environment. They could
be in a portal environment or some other environment that hides the nature of the BPM
environment from them.
Another common way to initiate a process is to have a document arrive in a content
management system, and the document requires some sort of process in order to be
executed. There are still a lot of processes that are driven by the arrival and scanning
of paper documents, but this could be any kind of content that’s added to a content
repository. It could be a Word document; it could be an email. Whatever it is, you have
a piece of content, you add it to a content repository (for records management or other
retention purposes), and there’s typically some sort of process that needs to happen
around that document. It could be to gather information from that document, such as
keying in transactiona