An Enterprise Process Architecture Model provides a high-level, structured overview of an organisation’s set of business processes. It enables you also to identify candidate processes subject to business process change.
When initiating such a business process change project consider creating a Scope Diagram to analyse how a business process-in-scope interacts with its environment.
The main purpose of a scope diagram is to define and agree on the boundaries of a process. It is also an ideal tool for enhancing the communication to the stakeholders.
As a business process practitioner, you can choose between different types of scope diagrams. An overview.
An IDEF0 model represents how process activities interrelate, how resources are used by an activity, and what the result or output of each activity is. The model consists of simple box and arrow graphics and associated text supporting the graphics.
The essence of an IDEF0 model is that it allows you to to focus on how the process interfaces with its environment. An IDEF0 model describes four types of interfaces:
A variation of IDEF0, is the IGOE diagram. The acronym IGOE stands for Input-Guides-Outputs-Enablers.
The model is used to define the scope of a process including the types of problems one might face in the analysis of the process-in-scope. Besides the relationships between the process-in-scope, upstream or downstream processes, relevant documents, stakeholders etc this diagram focuses also on issues like:
This framework could be used for capturing and documenting the IGOE’s of what an organisation does.
A popular scoping technique with (Lean) Six Sigma practitioners is the SIPOC diagram. It represents a high-level view of a process. It shows the Suppliers, Inputs, Process, Outputs and Customers.
SIPOC diagrams are useful for focusing a discussion and helping project team members agree upon a common language and understanding of a process for continuous process improvement. In Six Sigma, SIPOC is often used during the “define” phase of the DMAIC improvement steps.
The purpose of a Business Interaction Model (BIM) is to provide a helicopter view of the business interactions between identified actors that play a role in the business domain-in-scope.
A common development approach is as follows:
Like a Rummler-Brache Relationship Map this diagram provides a convenient way to graphically establish boundaries on the processes to be considered for further examination.
The common characteristics of the presented scope diagrams are that they all try to get a better understanding of the business process-in-scope and enhance the communication to the stakeholders.
Undoubtedly it is a very useful but underestimated modelling technique among business process practitioners. Indeed, ideally, ‘scoping’ should be done first before embarking on extensive process mapping initiatives.