POEM -> POEM packages -> local process environment

Basics

This view ia aggregate/intersection of all other views: it shows details of single process: it shows triggering event; input and output information objects (documents); responsible roles;standards to which process conforms to; which measures/metrics are used for measuring process and which goals the process fullfils.

Process Overview is the high perspective view on the processes in organizations and relationships among them. It shows, for example, which process replaces, depends on another process or conforms to standard or directive.

Sometimes it is useful for quality manager, for example, to get all relevant information about only one process without seeing its details (e.g. sequence of activities). A process improvement, process optimization or process audit are such cases, where every process should be examined (“Tell me everything about exactly that process!”)  

Description, concepts and relations

Process neighbourhood diagram shows only one process with all related information. It shows roles, which are responsible for this process, starting event (trigger), end event, exceptions, related documents, standards, business goals, metrics and input/output information flows. Notation, used for this diagram is specialized BPMN notation.

Concepts, used in this diagram, are combination of concepts from previously described diagramming techniques. The key concept is single process, surrounded by relevant information and enclosed in a package [ Figure 12 ]. Concepts used in this diagram are the following.

•  Process is central concept. All the details are hidden (sequence of the activities). The process is triggered by starting event

•  Starting event shows when the process is started (triggered). Any of BPMN standard starting events can be used (message, timer, rule, link, or aggregate starting event)

•  End event shows what happens when the process is finished. Any of BPMN standard end events can be used (message, error, compensation, aggregate, terminate, or cancel end even)

•  Exceptions show what should be done if the process is interrupted and who handles the exception. Any of BPMN standard intermediate events can be used. Compensation processes are shown on separate diagram called Exceptions and compensations .

•  Input information flow / artefacts show needed information anywhere in the process. This relation was already defined in the Processes and artefacts diagram (information exchange).

•  Output information flow / artefacts show results of the process. This relation was already defined in the Processes and artefacts diagram (information exchange).

•  Related standards which the process conforms to. This relation was already defined in the Processes and artefacts (standards) diagram .

•  Related metrics which are used for measuring process performance. This relation was already defined in the Processes and artefacts diagram.

•  Related business goals which are used to show compatibility of the process with business goals. This relation was already defined in the Processes and artifacts (business goals) diagram . .

•  Roles and groups show who is responsible for the process performance. Type of responsibility relation can be any of previously defined relations from Responsibilities diagram.