MEGA Process BPMN Edition en

MEGA Process BPMN Edition
User Guide
MEGA 2009 SP5 R6

2nd Edition (July 2012)
Information in this document is subject to change and does not represent a commitment on the part of MEGA
International.
No part of this document may be reproduced, translated or transmitted in any form or by any means without
the express written permission of MEGA International.
MEGA International, Paris, 1996 - 2012
All rights reserved.
MEGA Process BPMN Edition and MEGA are registered trademarks of MEGA International.
Windows is a registered trademark of Microsoft Corporation.
The other trademarks mentioned in this document belong to their respective owners.
CONTENTS
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Why Model the Activity of My Enterprise? . . . . . . . . . .

Explaining how your enterprise operates . . . . . . . .
Considering changes in the organization . . . . . . . . .
Defining IT requirements . . . . . . . . . . . . . . . . . . .
Specifying interactions with partners . . . . . . . . . . .
Modeling with MEGA Process BPMN Edition . . . . . . . . .
Describing processes . . . . . . . . . . . . . . . . . . . . . .
Producing documents . . . . . . . . . . . . . . . . . . . . . .
Producing an Intranet site. . . . . . . . . . . . . . . . . . .
Upgrading and maintaining your processes . . . . . . .
Conventions Used in the Guide. . . . . . . . . . . . . . . . . .
Presentation of this Guide . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . .7
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .9
. . . . . . . . . . . . . . . . . . . . . . . . .9
. . . . . . . . . . . . . . . . . . . . . . . . .9
. . . . . . . . . . . . . . . . . . . . . . . . 10
. . . . . . . . . . . . . . . . . . . . . . . . 11
Organizational Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Example Overview . . . . . . . . . . . . . . . . . . . . . . . . .
Defining an Operation . . . . . . . . . . . . . . . . . . . . . .
Conditioning a Sequence Flow . . . . . . . . . . . . . . . .
Creating a Sequence Flow . . . . . . . . . . . . . . . . . . .
Moving Sequence Flows . . . . . . . . . . . . . . . . . . . .
Defining a Condition on a Sequence Flow . . . . . . . .
Defining Message Flows . . . . . . . . . . . . . . . . . . . . .
Defining Message Flow Content . . . . . . . . . . . . . . .
Creating a Message Flow With Content . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . 14
. . . . . . . . . . . . . . . . . . . . . . . . . 18
. . . . . . . . . . . . . . . . . . . . . . . . . 19
. . . . . . . . . . . . . . . . . . . . . . . . .19
. . . . . . . . . . . . . . . . . . . . . . . . .19
. . . . . . . . . . . . . . . . . . . . . . . . .19
. . . . . . . . . . . . . . . . . . . . . . . . . 21
. . . . . . . . . . . . . . . . . . . . . . . . .21
. . . . . . . . . . . . . . . . . . . . . . . . .22
Contents
Using an Organizational Process. . . . . . . . . . . . .
Using an Existing Organizational Process . . . . . . .
Accessing an Organizational Process Diagram . . .
Using Data Objects . . . . . . . . . . . . . . . . . . . . . . .
Creating a Data Object . . . . . . . . . . . . . . . . . . .
Associating a data object with a sequence . . . . . .
Using Data Stores . . . . . . . . . . . . . . . . . . . . . . .
Using Gateways. . . . . . . . . . . . . . . . . . . . . . . . . .
Placing a Process in its Context . . . . . . . . . . . . .
Creating an Organizational Process in a Diagram .
Calling an Organizational Process in an Operation .
Initializing an Organizational Process Diagram . . .
Defining Process Events . . . . . . . . . . . . . . . . . . .
Creating an Event . . . . . . . . . . . . . . . . . . . . . . .
Connecting Events to Sequence Flows . . . . . . . . .
Accessing Preceding or Succeeding Processes. . . .
Attaching an Event to a Process . . . . . . . . . . . . .
Using Participants . . . . . . . . . . . . . . . . . . . . . . . .
Creating an Org-Unit Participant . . . . . . . . . . . . .
Assigning Several Org-Units to a Participant. . . . .
Positioning a Participant in a Swimlane . . . . . . . .
Improving Presentation . . . . . . . . . . . . . . . . . . .
Adding Notes to Objects . . . . . . . . . . . . . . . . . .
Modifying Object Shapes . . . . . . . . . . . . . . . . . .
Modifying Object Name Presentation . . . . . . . . . .
Formatting Links. . . . . . . . . . . . . . . . . . . . . . . .
Changing Fonts. . . . . . . . . . . . . . . . . . . . . . . . .
Refining Flowchart Appearance . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Functional Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Creating a Functional Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Representing a Functional Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
System Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Managing a System Process . . . . . . . . . . . . . . . .
Creating a System Process. . . . . . . . . . . . . . . . .
Connecting a System Process to an Organizational
Creating a System Process Diagram . . . . . . . . . .
Example:. . . . . . . . . . . . . . . . . . . . . . . . . . .
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a task in a system process . . . . . . . .
Sequence Flows, Events and Message Flows . . .
Sequence flows . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Process . . . . . . . . . . . . . . . . . . . . . . . 56
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Contents
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message flows . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Step Output Gateways . . . . . . . . . . . . . .
Processing Step Input Gateways . . . . . . . . . . . . . . .
Creating a Gateway . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Gateway . . . . . . . . . . . . . . . . . . . . . . .
Creating a System Process Participant. . . . . . . . . . .
Specifying Process Behavior. . . . . . . . . . . . . . . . . . .
Compensation description . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . .60
. . . . . . . . . . . . . . . . . . . . . . .61
. . . . . . . . . . . . . . . . . . . . . . . 62
. . . . . . . . . . . . . . . . . . . . . . .62
. . . . . . . . . . . . . . . . . . . . . . .62
. . . . . . . . . . . . . . . . . . . . . . .63
. . . . . . . . . . . . . . . . . . . . . . .63
. . . . . . . . . . . . . . . . . . . . . . . 65
. . . . . . . . . . . . . . . . . . . . . . . 66
. . . . . . . . . . . . . . . . . . . . . . .67
Organizational Charts and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Creating an Organizational Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Drawing an Organizational Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Querying objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Specifying the properties of an org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Consulting the RACI Matrix of Org-Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Business Process Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Defining business process control responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Generating an RACI matrix from a business process . . . . . . . . . . . . . . . . . . . . . . . . . .76
Organizational process and operation responsibilities (RACI) . . . . . . . . . . . . . . . . . . . 77
Defining Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Organizational process and operation responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . .77
Responsibility of a participant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Using RACI Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Launching an RACI matrix from an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Creating an RACI with objects of your choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Creating a Business Process. . . . . . . . . . . . . . . . . . . .
Creating a Business Process Diagram . . . . . . . . . . . . .
Representing Product Offerings . . . . . . . . . . . . . . . . .
Defining Offerings . . . . . . . . . . . . . . . . . . . . . . . . . .
Representing Process Contextualization . . . . . . . . . .
Defining a Contextualization . . . . . . . . . . . . . . . . . . .
Creating a contextualization . . . . . . . . . . . . . . . . .
Defining context . . . . . . . . . . . . . . . . . . . . . . . . .
Launching a Report Illustrating Contextualizations . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . 86
. . . . . . . . . . . . . . . . . . . . . . .86
. . . . . . . . . . . . . . . . . . . . . . . 87
. . . . . . . . . . . . . . . . . . . . . . .87
. . . . . . . . . . . . . . . . . . . . . . . 89
. . . . . . . . . . . . . . . . . . . . . . .89
. . . . . . . . . . . . . . . . . . . . . . .90
. . . . . . . . . . . . . . . . . . . . . . .90
. . . . . . . . . . . . . . . . . . . . . . .90
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Contents
INTRODUCTION
MEGA Process BPMN Edition is software edited by MEGA International to

assist:
Organizers in improving and redesigning enterprise business processes.

Quality engineers describing the business processes of their
organization.
It enables:
Description of the detailed organization of operations during execution of

organizational processes, and the participation of each of the enterprise
org-units in these processes.
Description of product or service offerings proposed by enterprise
business processes.
Description of enterprise value chains.
Description of the enterprise organizational chart.
Detailing of information system requirements involved in these
application business processes. It is then possible to draw a map of the
enterprise organization and information system (in conjunction with
MEGA Architecture).
Why Model the Activity of My Enterprise?

Because business modeling helps you:
Explain how your enterprise operates.

Consider changes in the organization.
Defining IT requirements.
Specify collaborations with partners.
Introduction
Explaining how your enterprise operates
A diagram explaining a business process can provide a better understanding of how
an enterprise operates in cases such as:
When a person is hired.

When a persons duties change.
When instructions are not fully understood.
The standard organizational chart provides you with only an overview showing the
organizational unit hierarchy, without explaining how the enterprise functions. A
process diagram helps you better understand how your enterprise operates.
Considering changes in the organization

Management must improve processes in an enterprise in order to eliminate
weaknesses. Management can go further by transforming certain processes so that
they become key competitive advantages for the enterprise.
Formally defining processes is a way to highlight those areas needing improvement.
Defining IT requirements
Process descriptions can be supplemented by details of IT means required,
functionalities to be implemented, applications or services used.
The functionalities (which may or may not be IT) required to execute

each operation.
The applications used.
Other material or human resources required to carry out the process.
Specifying interactions with partners

Interactions with partners of the enterprise should be precisely defined to enable
automation of exchanges between the business processes of the enterprise and
those of its partners as part of an e-business or EAI (Enterprise Application
Integration) project.
Modeling with MEGA Process BPMN Edition

The powerful graphics tools of MEGA Process BPMN Edition allow you to easily
provide a detailed description of your organization.
Describing processes
You can write comments for each process element directly from the diagram. This
offers many advantages:
Describing individual elements is easier and faster than describing the

complete process.
Reports can be built automatically.
Easy retrieval of process descriptions for insertion into other processes.
The volume of text is significantly reduced.
Introduction
Producing documents
Documents are automatically generated from the elements entered when describing
the diagram.
The general structure is independent of the writer.

Documents are generated automatically.
Documents have a standard layout and consistent style.
Descriptions are automatically reused in the different documents.
Document consistency is assured.
You can modify the layout and formatting of documents generated

by MEGA Process BPMN Edition and create new ones. See the MEGA
Publisher guide.
Producing an Intranet site
MEGA Process BPMN Edition allows you to automatically generate an Intranet
site describing the processes used in the enterprise.
Upgrading and maintaining your processes

As your organization evolves, so do your processes.
MEGA Process BPMN Edition allows you to make your changes in one location,
and have them propagated to all processes involving those elements. This allows:
Rapid access to the elements that you want to modify.

Easy analysis of the impact of modifying an object in one process on
other processes containing that object.
Automatic regeneration of all documents concerned.
This User Guide is designed to help you quickly discover the power of MEGA
Process BPMN Edition.
Introduction
CONVENTIONS USED IN THE GUIDE
Remark on the preceding points.

Definition of terms used in this guide.
A tip that may simplify things.

Compatibility with previous versions.
Things you must not do.
Very important remark to avoid errors during an operation.

Commands are presented in this way: File > Open.
The names of products and technical modules are presented in this way: MEGA.
10
Introduction
Presentation of this Guide
PRESENTATION OF THIS GUIDE

The Quick Start Guide presented how to create your first diagram with MEGA.
This guide presents how to take advantage of this initial modeling to describe your
organization and improve its operation.
"Organizational Processes", page 13 explains how to improve operation of the

organizational process described in the Quick Start guide. It also presents how to
complete and integrate it with other processes of your organization. Process
descriptions can be completed by specifying the information system components
they require.
"Business Processes", page 85 presents how to specify enterprise product and
service offerings, and the breakdown of the processes producing these.
"Functional Processes", page 49 describes representation of enterprise value
chains in terms of activities. It enables freeing from the existing organization to
imagine new organization solutions for your processes.
"System Processes", page 55 enables description of the IT process required for
implementation of an organizational process by sequencing of the tasks executed.
"Organizational Charts and Responsibilities", page 69 describes how to create an
enterprise organizational chart and how to define responsibilities of persons and
org-units.
"Glossary", page 93, summarizes definitions of the main concepts covered in this
guide.
This guide is complemented by the Quick Start Guide guide, which will help you
create your first diagram with MEGA.
It is also complemented by the MEGA Common Features guide, which presents
functions common to all MEGA products, as well as by Online Help, accessible by
pressing key <F1>, which opens context-sensitive help in each MEGA Process
BPMN Edition dialog box.
More advanced technical functions are described in the MEGA Publisher guide.
11
Introduction
12
1
ORGANIZATIONAL PROCESSES
This chapter describes how to use MEGA Process BPMN Edition functions to improve business
process efficiency.
This presentation is based on the example of purchase request processing introduced in the MEGA
Process BPMN Edition Quick Start guide. Organization of this business process is modified to take
account of evolutions aimed at improving its efficiency.

"Example Overview", page 14

"Defining an Operation", page 18
"Conditioning a Sequence Flow", page 19
"Defining Message Flows", page 21
"Using an Organizational Process", page 23
"Using Data Objects", page 26
"Using Gateways", page 29
"Placing a Process in its Context", page 30
"Defining Process Events", page 33
"Using Participants", page 39
"Improving Presentation", page 43
13
1
EXAMPLE OVERVIEW
The existing organization is represented by the following diagram.
The purchase request is received by a purchasing assistant,

who enters the request and submits this for the approval of
the purchasing manager.
If the request is rejected, the purchasing manager informs
the requester.
If the request is approved, the assistant sends a completed
request to buyers responsible for issuing the order, and
sends a confirmation message to the requester.
The Quick Start guide explains how to use the main objects presented in this
diagram.
The frame containing the different components represents the

organizational process described by the diagram. Its name "Process
Purchase Request" appears in the box at top left.
An organizational process is a set of operations performed by orgunits within a company or organization, to produce a result. It is
14
Organizational Processes
Example Overview
depicted as a sequence of operations, controlled by events and

conditions.
The participants in execution of this process are org-units. They are

represented in columns for reasons of diagram readability.
An org-unit represents a person or group of persons participating in
the processes or information system of the enterprise. An org-unit can
be internal or external to the enterprise. An internal org-unit is an
organizational element of enterprise structure such as a management,
department, or job function. It is defined at a level depending on the
degree of detail to be provided on the organization (as org-unit type).
Example: financial management, sales management, marketing
department, account manager. An external organization unit is an
organization that exchanges flows with the enterprise. Example:
customer, supplier, government office.
A participant (org-unit) enables representation of org-units
assigned to execution of a group of operations of a process.
See"Using Participants", page 39 for more details on assignment of orgunits to participants in the process.
The different steps in this process are operations. Organization of these

steps is described by sequence flows.
An operation is an elementary step in an organizational process
executed by an org-unit. It cannot be broken down. An operation can be
industrial (manufacturing a component), logistical (receiving a
delivery), or can involve information processing (entering an order).
Message flows enable representation of data or information circulating

between a process and the exterior.
A message flow is information flowing within an enterprise or
exchanged between the enterprise and its business environment. A
message flow can carry a content.
Evolutions in the business process concern improvement of the following points:
The time taken to process the request, by reducing the number of

purchase requests submitted for purchasing manager approval.
Profitability, by reorganizing order processing.
Pooling business processes, by considering use contexts.
Flexibility, by identifying org-units involved in the process and their
replacements on critical operations.
15
1
In the existing process, the purchasing manager must systematically approve all
purchase requests entered by the purchasing assistant.
This approval phase causes delay in the processing of purchase requests, which can
be reduced by partially entrusting the task to the assistant. The majority of
purchase requests concern supplies in current use, and most rejections can be
decided by the assistant alone (outside-catalog purchases for example).
Two axes for improvement of process delay are decided:
Unacceptable purchase requests are rejected by the assistant, who

notifies this rejection directly to the requester.
Only those purchase requests exceeding a given amount are submitted
for purchasing manager approval.
These evolutions are indicated in the diagram as follows:
16
A "Notify Reject" operation is created and assigned to the purchasing

assistant.
A sequence flow, conditioned by rejection of the request is created
between the "Enter Purchase Request" and "Notify Reject" operations.
Another condition relating to the amount is placed on the sequence flow
between the "Enter Purchase Request" and "Approve Request"
operations.
Finally, a sequence flow is created between "Enter Purchase Request"
and "Finalize Request" for other cases.
Example Overview
In the organizational process diagram, modifications are indicated below by

numbers.
To implement these modifications, you will:
(1)
(2)
(3)
(4)
Create an operation.
Move a sequence flow.
Create a sequence flow and define a condition.
Define a default sequence flow.
Points described here are also presented in the Quick Start guide.
17
1
DEFINING AN OPERATION
An operation is a step in a process.
An operation is an elementary step in an organizational process
executed by an org-unit. It cannot be broken down. An operation can be
industrial (manufacturing a component), logistical (receiving a
delivery), or can involve information processing (entering an order).
You will create an operation and connect it to the org-unit responsible for its
execution.
To create an operation:
1.
2.
3.
Click the Operation button

and click in the diagram within the
shape of the participant responsible for its execution, the "Purchasing
Assistant".
The Create Operation dialog box opens.
Enter the name of the operation in the Name text box, for example
Notify Reject.
Click the OK button.
The operation appears in the diagram.
For more information on properties of processes and operations,

see "Specifying System Process Behavior" in "System Processes".
18
Conditioning a Sequence Flow
CONDITIONING A SEQUENCE FLOW

A sequence flow is a directional link that represents chronological organization of
the different processing steps.
A sequence flow is used to show the order in which steps of a
process will be performed. Each sequence flow has only one source and
only one target.
Creating a Sequence Flow

To create a sequence flow:
1.
2.
Click the Sequence Flow

button.
Click the first object representing the start step, for example the "Enter
Purchase Request" operation and, holding the mouse button down, draw
a line to the object representing the next step, in this case the "Notify
Reject" operation.
Moving Sequence Flows

You may need to change the predecessor or successor of a sequence flow. For
example, you can specify the "Notify Reject" operation as successor of the "Approve
Request", replacing the "End" event.
To move a sequence flow:
1. Click the sequence flow:.
The two link ends are marked with red squares.
2. Holding the <Shift> key down, position the mouse on the red square at
the end you wish to move.
A reel appears when you are correctly positioned on the link end.
3. Still holding the <Shift> key down, click the square and, holding the
mouse button down, move it to its new predecessor or successor before
releasing the mouse button.
The link appears in its new position in the diagram.
Defining a Condition on a Sequence Flow

To define a condition on a sequence flow, for example on a sequence flow between
operations "Enter Purchase Request" and "Notify Reject" :
1. Right-click the sequence flow between the "Enter Purchase Request"
and "Notify Reject" operations and in the pop-up menu that appears,
select Properties.
19
1
2.
In the dialog box that appears, select the Characteristics tab.
Click the arrow at the right of the Sequence Type box.

Select "Conditioned" in the drop-down list.
Enter the conditioning expression in the Predicate text box.
Click OK.
The text associated with the condition appears on the link which then
takes form
.
In the same way you can describe the condition relating to the amount of the
request associated with the sequence flow to the "Approve Request" operation.
3.
4.
5.
6.
Defining a default condition on a sequence flow

If several conditioned sequence flows are from the same operation, you can specify
that one of these should be used as default. For example, having completed the
"Enter Purchase Request" operation, the assistant always executes the "Finalize
Request" operation, except if the request is not acceptable and is below a given
amount.
To define that a sequence flow is used by default:
1. Right-click the sequence flow between "Enter Purchase Request" and
"Finalize Request" operations and in the pop-up menu that appears,
select Properties.
2. In the dialog box that appears, select the Characteristics tab.
3. Click the arrow at the right of the Sequence Type box.
4. Select Default in the drop-down list.
5. Complete the Predicate text box if you wish to add a comment.
6. Click OK.
The link then takes form
.
20
Defining Message Flows
DEFINING MESSAGE FLOWS

The content of message flows exchanged with the exterior can be specified.
Defining Message Flow Content

You will specify the content of message flows exchanged between the "Process
Purchase Request" process and the exterior.
To define content of a message flow:

1. Right-click the message flow and select Properties.
The properties dialog box opens.
2. Select the Characteristics tab.
3. Click the arrow at the right of the Content text box and select List
Content in the drop-down list.
The list of contents of the library appears in a dialog box.
21
1
4.
Select the name of the content, for example "Purchase Request" and
click OK.
A content can be used by several message flows, since it is not

associated with a sender or recipient.
The name of the content appears in the diagram.
Creating a Message Flow With Content

You can specify the content of message flows exchanged between a process and its
environment directly at flow creation.
To create a message flow and its content:

1. In the diagram insert toolbar, click the Message Flow button arrow,
option Message Flow With Content
2.
3.
Click the first object representing the start step, and, holding the mouse
button down, draw a line to the object representing the next step.
The Creation of Message Flow With Content dialog box opens.
In the Content drop-down list, select the content you wish to associate
with the flow.
The message flow and its content are displayed in the diagram.
You can associate several contents to the message flow; see

paragraph "Defining Message Flow Content".
22
Using an Organizational Process
USING AN ORGANIZATIONAL PROCESS

An organizational process is a set of operations performed by org-units within a
company or organization, to produce a result. It is depicted as a sequence of
operations, controlled by events and conditions.
In the initial "Process Purchase Request" process, the "Process Purchase Order"
operation is executed by a buyer.
In the new organization, "Process Purchase Order" becomes an organizational
process in which the Purchasing Manager is involved for:
Restocking.
Supplier contract negotiation.
The diagram takes a new form.
Using an Existing Organizational Process

To more closely detail behavior of a processing step such as an operation, you must
replace it by an organizational process.
23
1
To use an existing organizational process:
1.
Click the Organizational Process
button and click in the diagram
outside the frame of the described process.

The Add Organizational Process dialog box opens.
2. Click the arrow at the right of the Organizational Process text box and
select List Organizational Process in the drop-down list.
The list of organizational processes in the library appears in a dialog box.
3. Select the organizational process that interests you, for example
"Process Purchase Order".
4. Click the OK button.
5. Click the Finish button in the Add Organizational Process dialog box.
The organizational process appears in the diagram.
In this context, you can move the "Buyer" participant to position it outside the
"Process Purchase Order" frame. The "Process Purchase Order" business process
remains positioned within this participant.
Accessing an Organizational Process Diagram

To access an organizational process diagram:
1. Right-click the process, in this case "Process Purchase Order", to open its
pop-up menu.
2. Select Organizational Process Diagram.
The diagram opens in a new window.
If the process does not have a diagram, you can create it by

clicking New in its pop-up menu.
24
Using an Organizational Process
The "Process Purchase Order" organizational process diagram is shown below.
The purchase request is analyzed by the purchasing manager, who checks product
availability and requests that the product be made available.
The purchasing manager also checks stock, and if this is insufficient, requests a
buyer to send a supplier order.
Finally, based on current contracts, the buyers send orders to suppliers.
25
1
USING DATA OBJECTS
In an organizational process diagram, a data object can be used to represent the
fact that data or objects (correspondence, raw materials, finished products, etc.)
are in stock awaiting use.
In the example of the "Process Purchase Order" process, data relating to stock is
represented by the "Stock Data" data object.
A data object is used to explain how documents, data, and other
objects are used and updated during the process. A data object can
represent an electronic document, or any other type of object,
electronic or physical.
In this example, the data object "Stock Data" is represented with

an open head arrow since it is used by the "Analyze Purchase Request"
process without having been produced by one of the processes
represented in the repository.
Creating a Data Object

To create a data object:
1.
2.
In the diagram insert toolbar, click the Data Object

Click in the diagram to position the object.
The Create Data Object dialog box appears.
3.
Click the arrow at the right of the Content text box and select List
Content in the drop-down list.
The list of contents of the library appears in the dialog box.
Select the content, "Contract Data", and click OK.
4.
button.
A content can be used by several data objects.

5.
Enter Data Object State if required.
By default the data object carries the same name as its content.
The state appears between brackets.
26
Using Data Objects
6.
Click OK.
The data object appears in the diagram.
To specify that a shared object corresponds to an object collection:

1. Open the properties dialog box of the shared object and select the
Characteristics tab.
2. Click the arrow
at the right of the Collection box, and select Yes.
The shared object then takes the following form:
Information necessary for execution of operations can be consulted or updated in

the data objects.
To indicate that information was obtained from a data object, for example that stock
data used by the "Analyze Purchase Request" operation was obtained from the
"Stock Data" data object:
1.
Click the reel
in the insert toolbar.
2.
Click the data object , for example "Stock Data" and, holding the mouse
button down, draw a link to the operation.
A data object is represented by an open head arrow if it is read by a

process without having been updated by one of the processes in the
repository.
A data object is represented with a solid head arrow if it is updated
by a process and not read by any of the processes in the repository.
Associating a data object with a sequence

You can also specify that the content of a data object is sent at sequencing of two
operations, for example, a shared object "Purchase Request" can be sent between
the operations "Enter Purchase Request" and "Finalize Request".
A data object is used to explain how documents, data, and other
objects are used and updated during the process. A data object can
represent an electronic document, or any other type of object,
electronic or physical.
To simultaneously create a sequence flow and a data object:

1. Click the Sequence Flow button arrow, option Sequence Flow With
Data Object.
2.
Click the operation representing the start step, and, holding the mouse
button down, draw a line to the operation representing the next step.
The Creation of Sequence Flow With Data Object dialog box opens.
27
1
3.
In the Content drop-down list, select the content you wish to associate
with the flow.
The sequence flow and its content are displayed in the diagram.
Using Data Stores

Objects that are shared, supplied or used in processing can be stored in a data store.
A data store provides a mechanism to update or consult data that
will persist beyond the scope of the current process. It enables storage
of input message flows, and their retransmission via one or several
output message flows.
In the example of the "Process Purchase Order" process, data relating to suppliers
is represented by the "Supplier Data" data store.
To create a data store:

1.
In the insert toolbar, click the Data Store
button.
Click in the diagram to position the object.

The Add Data Store dialog box appears.
3. Enter the name of the data store.
4. Click OK.
You can specify the content of message flows exchanged between the data store
and the processes by creating message flows in your diagram.
2.
For more details on message flows, see paragraph "Defining

message flows".
28
Using Gateways
USING GATEWAYS
The following example presents a case in which processing progress is conditioned:
following analysis of a purchase request, the process either ends, or an order is sent
to a supplier.
To specify that several processing steps are accessible following a particular

processing step, you can use a gateway.
Gateways are modeling elements that are used to control how
sequence flows interact as they converge and diverge within a process.
Conversely, you can also use a gateway to indicate that a particular

processing step is available from several processing steps of a process.
For more information on gateways, see "Gateways", page 62.
29
1
PLACING A PROCESS IN ITS CONTEXT
The "Process Purchase Request" and "Process Purchase Order" processes comply
with the general process of standard purchasing, operation of which is described by
the following diagram:
Purchase requests are processed by the purchasing department. If the request is

rejected, a notification is sent to the requester, otherwise the validated request is
processed within the framework of the "Process Purchase Order" process.
If stock level drops below a minimum level, an order is sent to the supplier and
products are received by the logistics department.
When available, the product is made available to the requester by the logistics
department.
30
Placing a Process in its Context
Creating an Organizational Process in a Diagram

To create a process from a process diagram that is already open:
1.
Click the Organizational Process
button in the diagram insert
2.
toolbar.
Click within the frame of the described organizational process and within
the frame of the participant responsible for this process.
The Add Organizational Process dialog box opens.
3.
4.
Enter the organizational process name.

Click Finish.
The new process appears in the diagram.
Calling an Organizational Process in an Operation

You can create an operation that calls an organizational process. This functionality
enables, for example, replacement of the process called by another process without
disturbing description of the main process.
To create an operation that calls an organizational process:
1.
Select the Operation button
and select Organizational Process
Call.
2.
3.
Click in the diagram within the shape of the participant responsible for its
execution.
The Creation of Organizational Process Call dialog box opens.
In theOrganizational Process box, enter the name of the process
called, for example "Process Purchase Request", that could be replaced
by "Process Urgent Purchase Request".
By default, the operation carries the same name as the

organization process called.
4.
Click the OK button.

The operation appears in the diagram with the name of the organizational
process.
31
Initializing an Organizational Process Diagram

If you create the diagram of an organizational process in a particular context, such
as "Make Available" in the example, and you selected the Diagram initialization
option before clicking Create in the organizational process diagram creation
window, the new diagram that opens will be as follows.
The diagram is initialized with:
32
A note indicating the use context of the described process. In the

example above, this is the "Process Urgent Purchase Request" process
which is the owner of the "Make available" process.
The message flows exchanged by the described process with the exterior
in the initialization context.
Participants representing senders and recipients of message flows
exchanged by the process with the exterior in the initialization context.
Events of each intermediate type for each triggering sequence flow of the
described process in the initialization context.
An end event for each sequence flow, triggered by the process, leading
to another end event.
Defining Process Events
DEFINING PROCESS EVENTS

The events enabling representation of facts occurring during process execution.
An event represents a fact occurring during execution of a process,
for example a new contract concluded with a supplier. An event marks
the impact on process progress of a phenomenon internal or external to
the process. There are different natures of events: start events, catch
events, throw events and end events.
Events can be used:
Within a process to define facts internal to the process.

Outside a process to describe causes and effects of events of the process
depending on its use context.
The different event types are presented in this section.
Creating an Event
To create an event:
1.
2.
3.
Click the Event button

Click in the diagram.
The Create Event dialog box opens.
Enter the name you wish to give the event.
You can directly click the Finish button of the wizard. A catching
event without type is created.
4.
Select the nature of new event.
By default, the nature is Catching.

5.
Click Next and select the type of event you wish to create.
6.
Click Finish.
The new event appears in the diagram. The shape of the event respects
conventions linked to its type and nature.
By default the type is None.
You can directly create the most frequently used events:

1. Click the Events button in the toolbar and select from the predefined
events that which interest you.
2.

The new event appears in the diagram.
33
1
Event natures
The nature of the event enables specification of its position in the processing.
Start: start of the processing sequence

Catching: awaiting an event (arrival of a message, signal, etc.) before
continuation of processing
Send: triggering an event (message, signal, etc.) and continuation of
processing
End: end of the processing sequence
Event types
Event type enables specification of what will trigger the event and what will be
triggered by the event.
34
None: the trigger is not specified, generally at the start or end of a

process
Message: the event is receiving or sending messages
Timer: the event is triggered by a timer
Error: the event is triggered by errors or throws errors that cause
interrupt of the process
Cancel: the event reacts to cancelled process steps or triggers
cancellation
Compensation: the event handles or triggers compensation of a failed
process
Conditional: the event is triggered by a condition
Link: the event is used to connect two sections of a process
Signal: the event waits for a signal or throws a signal. One signal
thrown can be caught multiple times
Terminate: the event indicates that all process steps should be
immediately ended without compensation or event processing
Multiple: the event has multiple triggers
Escalation : the event is triggered by an error or throws a non-critical
error
Event type and nature combinations

The following table presents valid combinations of event type and nature.
Connecting Events to Sequence Flows

In a given context, a process can be connected to another process by a sequence
flow.
In the example above, the "Process Purchase Request"

process precedes the "Process Purchase Order" process.
35
1
When this latter process is described by a diagram, the process that precedes it can
be shown.
In the diagram that describes the "Process Purchase Order"

process, the "Process Purchase Request" process that
precedes it is shown.
Showing external processes.

To do this, it is necessary to specify the event involved in the sequence flow:
1. Right-click the sequence flow and select Properties.
2. In the Characteristics tab, consider the Triggering Event and
Triggered Event sections.
From this dialog box, it is possible to open diagrams containing

these events via the pop-up menu of the process that owns them
(Owner Element).
36
3.
In the Triggered Event section, click the Connect button.

The Select Query dialog box opens.
4.
Click Possible Triggered Event.

The list displayed proposes start events or catching events of the
successor process.
The successor process is generally triggered at its start and

normally has only a single start event. This start event is therefore
generally the event that interests you.
5. Select the event corresponding to the sequence flow.
6. Click OK.
If you open the organizational process diagram containing this event, you can view
the process that precedes it.
You can similarly select the triggering event of the previous process. In this case,
end events or throw events from the preceding process will be proposed.
Accessing Preceding or Succeeding Processes

In the organization of the standard purchase process, the "Process Purchase Order"
organizational process is activated after processing of the purchase request, and
itself activates the "Make Available" process.
To show, at events level, the processes preceding and succeeding the described
process, you must:
Specify the sequence flows in which the events are involved.

Activate the views enabling access to context-sensitive information.
To activate the context-sensitive view:

1.
2.
3.
Click the Views and Details button

in the diagram toolbar.
Select the View External Processes check box.
Click OK.
37
Attaching an Event to a Process

To attach an event to a process:
1. Click the event and hold the mouse button down.
2. Position the event on the border of the process.
The border of the process is highlighted.
To detach the event from the process border:
Right-click the event and select Detach.
38
Using Participants
USING PARTICIPANTS
A participant enables:
Assignment of a group of operations to one or to several enterprise orgunits.

Representation of a unit external to the process with which the process
communicates by means of message flows.
In the example of the "Process Purchase Order" process, note that "Purchasing
Assistant" and "Buyer" are participants responsible for execution of operations,
while "Supplier" is a participant external to the process.
To illustrate use of participants using this example, we shall consider that to meet
purchase requests with minimum delay, even during high workload periods, it has
been decided to introduce a degree of flexibility in the process by assigning
replacement stand-in org-units for critical operations.
At the level of the "Process Purchase Order" process diagram, this change is
represented as follows:
The "Analyze Purchase Request" operation, handled by the Purchasing

Manager, is assigned to the Purchasing Assistant when the manager is
absent.
39
Creating an Org-Unit Participant

To create an org-unit from a new participant:
1.
2.
3.
4.
5.
Click the arrow on the right of the Participant

button in the insert
toolbar, and in the drop-down list select Participant (Org-Unit).
Click in the diagram workspace within the organizational process frame.
The Create Participant (Org-Unit) - Assignments dialog box opens.
To create an org-unit from this participant, enter the name of the new
org-unit in the Org-Unit text box.
Indicate the name of the participant if you wish to specify the org-unit
role in the process.
Click the Finish button.
The participant is positioned in the diagram. If you have not specified a
name, it will carry the name of the assigned org-unit.
To hide the name of the participant, open its pop-up menu and
select Shapes and Details. In the tree on the left, click the "Short
Name" folder, then in the Content tab, clear the Short Name check
box.
Assigning Several Org-Units to a Participant

Org-units, either new or already created, can be assigned to participants of a
process.
To assign an org-unit to a participant:
1. Right-click in the grey title bar of the participant.
40
Using Participants
2.
3.
4.
5.
Open the pop-up menu of the "Purchasing Manager" participant in the

example and select Properties.

In the Characteristics tab, Assignment section, click the Connect
button.
The query dialog box opens.
Select Org-Unit and click Find.
The list of existing org-units is displayed.
Select the org-unit you wish to assign to the "Purchasing Assistant"
participant in the example, and click OK.
A new assignment appears in the properties dialog box of the participant.
6.
To specify that several instances of the participant can be involved, click

arrow
at the right of the Multiple Participant box, and in the dropdown menu, select Yes.
The participant takes the following form:
7.
Click Close.
Names of assigned org-units appear in the title bar of the participant with
the name of the participant.
To condition participation of an org-unit:

1. Open the participant properties dialog box.
41
1
2.
3.
4.
5.
In the Characteristics tab, select the line of the actor of which you wish
to condition assignment.
Click in the Conditioning column.
Enter the text of the condition.

Click Close to close the participant properties dialog box.
The text of the condition appears between brackets alongside the name
of the org-unit in the participant title bar.
Positioning a Participant in a Swimlane

The swimlane is a tool that enables improvement in graphical presentation of certain
diagram types. Objects arranged in swimlanes automatically take the same
dimensions and are aligned.
To create a swimlane and place in it the participants you have just created:
1.
2.
3.
4.
In the insert tool bar, click the Vertical Pool button

The swimlane is created.
Drag the participant into the swimlane holding the mouse button down.
Release the button when the frames of both swimlane and described
process are highlighted.
If the process frame does not appear highlighted, the participant is

considered as external to the process.
The swimlane adapts to the size of the participant.
For more details on swimlanes, see "Using swimlanes" in "Handling

MEGA objects" in the MEGA Common Features guide.
42
Improving Presentation
IMPROVING PRESENTATION
Adding Notes to Objects

You can add notes in a diagram and connect these to an object.
To create a note and connect it to an object (for example an operation):
1.
Click the Note
2.
3.

The Add Note dialog box opens.
Indicate the Name and Type of the note.
button.
4.
The note Name is automatically generated by MEGA and does not have
any special meaning.
You can choose different types of note: "Correction", "Documentation",
"Improvement", "Example", "Question", "Remark", etc.
Select for example "Remark" type and enter your note in the text box.
5.
Click the Link
button and connect the note to the operation.
43
Modifying Object Shapes

MEGA allows you to modify the shape of an object without changing its
characteristics.
1. Right-click the organizational process and select Shapes and Details.
The View dialog box appears.
The framed shape is the default configuration.

If you wish to select an alternative shape:
1. Select the shape that interests you.
The Manual shape box is automatically selected.
2. Click OK.
If you wish to use additional shapes, give them a name using the
first four letters of the name of the standard shape and copy them into
the Standard\MEGA_USR folder of the environment.
The shape used for certain objects, such as messages, varies as a
function of the type attributed to them.
If you manually indicate the shape to be used following the explanation
above, the drawing will no longer reflect the type of object.
44
Modifying Object Name Presentation

MEGA enables modification of presentation of character strings associated with the
object shape. You can for example display the predicate of a sequence flow on
several lines.
To modify presentation of character strings associated with the object shape.
1. Right-click the object and select Shapes and Details.
The View dialog box appears.
2. At the left of the View dialog box, select the character string of which you
wish to modify presentation.
The View dialog box is updated.
3.
In the Content tab, confirm that the check box on the right of character
string name is selected.
4.
Select the Font tab.

The View dialog box is updated to present all available display options.
5.
Select the options that interest you.
If this box is not selected, the name will be masked in the diagram.
45
1
6.
Click OK.
Formatting Links
The "Edit" toolbar at the right of the diagram enables formatting of links.
If this toolbar is not displayed by default:
1. Select View > Toolbars > Edit.
This toolbar now appears on your workspace.
2. Select each link then click the button corresponding to the desired line
style (simple, orthogonal, curved, double):
You can also select a link, hold down the <Ctrl> key, and then
move this link. A "nail" now appears on the link allowing you to give it
the desired form.
3.
Save and close your diagram.
Changing Fonts
To configure the font of the text displayed.
1. Select the text.
2. In the menu bar, select Format > Font.
A dialog box appears. You can select another font or font size in this dialog box.
Refining Flowchart Appearance

MEGA allows you to add graphics to improve the appearance of your flowchart. In
the diagram:
1.
Click the Basic Drawing Object button

The dialog box proposing different standard shapes opens.
46
2.
Select the Shape.

A window similar to that below appears.
3.
In the folder in which you installed MEGA, open sub-folder

MEGA_STD\Pictures.6500\Art.
Select a shape and click Open. The shape then appears in the drawing.
4.
You can create your own custom shapes or use images from other
software. For more information on creating new shapes, see the online
help or the Advanced guide.
47
48
2
FUNCTIONAL PROCESSES
This chapter presents why and how to describe value chains of the enterprise in the form of
functional processes.
When an enterprise operates out of numerous geographical locations, organization of business
process operations can vary significantly between regions.
It is therefore useful to have a summary view, independent of organizational structure, to represent
steps in the value chain connected to enterprise business and common to all organizational variants.
A functional representation of the value chain also facilitates improvement in enterprise operation.
When the operation of each organizational process is represented, this enables local optimization of
each process as explained in the previous chapter.
This structure however remains partitioned by existing organizational structures. More significant
changes require a broader view of the value chain, independent of organization. This global view is
represented by the functional process diagram.
MEGA enables the creation and description of enterprise value chains.
"Creating a Functional Process", page 50

"Representing a Functional Process", page 51
49
2
CREATING A FUNCTIONAL PROCESS
To create a functional process from the navigator:
1. Right-click the current library.
2. Select New > Functional Process.
The Create Functional Process dialog box appears.
3. Enter the name of the functional process in the Name box.
4. Click Finish.
The functional process is created and added to the list of functional processes in the
menu tree.
The Finish button is grayed if the Name box is not completed.
50
Functional Processes
Representing a Functional Process
REPRESENTING A FUNCTIONAL PROCESS

Highlighting organizational choices
Each enterprise has activities related to its business that must be performed
whatever the organization in place. These activities can be purchasing, sales, sales
administration, manufacturing, etc.
Defining their organization consists of assigning these activities to the org-units that
will perform them.
We can distinguish between:
Processes relating to the business of the enterprise: these are difficult to

change unless the enterprise decides to totally review its business.
Processing depending on organizational choices.
Diversity of variants
Most variants of a process are the result of organizational choices such as giving
preference to urgent orders, special processing for large or export orders, etc.
It is necessary to overcome this diversity in order to move on to a new set of
variants, for example processing orders via telephone or the Internet. Representing
a business process in terms of activities gives a unique representation of the value
chain, highlighting what must be done irrespective of organization choices.
Number of steps
Certain steps in an organizational process are exclusively linked to the chosen
organization. In such cases, it is useful to check whether these steps provide any
real added value to clients or only concern the way things are done.
Delivery times can also be reduced by restructuring the order of these steps.
To highlight possible improvements, you can represent a value chain by flows
exchanged between enterprise activities.
A functional activity is a step in a process. This step represents the
contribution of a business line to the process value chain.
51
2
The following diagram presents a functional process example:
"Purchase-Receipt" functional diagram
The purchase request is recorded and must then be approved. The requester is
informed of approval or rejection of the request. If the request is validated, an
analysis of the required order is carried out.
If stock is lower than a given threshold, an order is prepared and sent to the supplier
for resupply.
If the product is available, or as soon as it is received from the supplier, it is made
available to the requester.
52
Functional Processes
Representing a Functional Process
In this diagram, the business functions concerned are represented in columns.

A business function is a skill or grouping of skills of interest for the
enterprise.
In the organization previously presented, three org-units: purchasing assistant,

purchasing manager and buyer, systematically participate to execute the first four
steps: record and approve the request, analyze and send the order.
Optimization of the "Process Purchase Request" organizational process has saved
one step: when the total amount of the order is not large, the purchasing assistant
is authorized to approve or reject the purchase order.
In the case of urgent orders, you can again save steps by authorizing the purchasing
assistant to send the order when the amount is not significant.
We obtain the following functional process for processing of urgent orders:
"Urgent Purchase-Receipt" functional diagram
The first step consists of analyzing the purchase request. If the total amount is
large, normal processing is carried out.
Otherwise, the availability request and a restock request are sent, if necessary. The
rest of the functional process is identical to the normal case: when the order has
been received, it is made available to the requester.
53
2
We can define a new organizational process for processing of urgent purchase
requests, in which responsibilities of the purchasing assistant are extended.
"Process Urgent Purchase Request" Organizational Process
The purchasing assistant begins by analyzing the purchase request. If the amount
is large, the normal process purchase request process is implemented. If the
product is available, the assistant sends the availability request.
If not, the assistant sends a purchase order to the supplier. The rest of the
processing is carried out within the framework of the normal "Process Purchase
Requests" organizational process.
To analyze the purchase request and send the order, the purchasing assistant
requires data on stock levels. He will have access to the "Equipment Purchasing"
application.
This new variation of the organizational process enables faster processing for urgent
orders. It demands higher qualifications of the purchasing assistant who has more
responsibilities.
You can show systems used by operations by selecting "System

used" in the window opened from the "Views and Details" button
A system used during the execution of a step of a process

represents what is necessary to realize this step. It can be an
application or an IT service, or any other non IT resource, or more
generally a functionality.
54
3
SYSTEM PROCESSES
MEGA allows you to model the IT system process implemented when using an organizational
process. This description is made in a BPMN model detailing the sequence flow of tasks performed
when executing the application in the particular context.
The BPMN (Business Process Modeling Notation) specification was created to formalize graphical
representation of IT and business processes, offering notation easily used by all participants
concerned.
The points covered are:

"Managing a System Process", page 56

"Tasks", page 59
"Sequence Flows, Events and Message Flows", page 60
"Gateways", page 62
"Processing Step Input Gateways", page 62
"Creating a System Process Participant", page 65
55
3
MANAGING A SYSTEM PROCESS
A system process represents automated execution of an organizational process.
The system process diagram uses notation proposed by BPMN standard.
Creating a System Process

You can create a system process from the navigator or from an organizational
process diagram.
A system process is the executable representation of a process. The
elements that formalize a system process are the following: the events
of the workflow, the tasks to be carried out during the processing, the
algorithmic elements used to specify the way in which the tasks follow
each other, the information flows exchanged with the participants.
To create a system process from an organizational process diagram:

1.
2.
3.
Select the Implementation Contexts check box.

Click OK.
The Contextualization
and System Process
buttons appear

4.
Click the System Process
5.
Click in the diagram where you wish to position the system process.
The Add System Process dialog box opens.
In the System Process box, enter the name you wish to give your
process.
Click Finish.
6.
7.
button in the diagram insert toolbar.
Connecting a System Process to an Organizational Process

To specify that an organizational process is implemented by a system process in a
given context, you must create a contextualization link between the two objects.
A contextualization allows specification of the implementation of a
process by another process in a specific context, such as the
geographical location on a site.
56
System Processes
Managing a System Process
For example, the "Process Urgent Purchase Request" process is implemented by the
"Analyze Purchase Request" system process to assure speed and efficiency of
processing.
To create a connection between an organizational process and a system process

from an organizational process diagram:
1.
2.
3.

Select the Implementation Contexts check box.
Click OK.
The Contextualization
and System Process
buttons appear in
the insert toolbar.

4.
5.
Click the Contextualization

button in the insert toolbar.
Click the organizational process and, holding the mouse button down,
drag the cursor to the system process and release the mouse button.
The contextualization appears in the diagram.
Creating a System Process Diagram

The system process algorithm can be expressed by sequencing of tasks and
decisions.
57
3
Example:
The diagram below represents purchase request processing.
A product search is carried out from the referenced products repository.

If the product is new, search for a supplier and comparative study of
prices is carried out. An order is then sent and the process ends.
If the product is referenced, stock is analyzed.
If stock is sufficient, a "Make available" request is activated and the
process ends.
If stock is less than minimum stock, an order is sent to the supplier and
the process ends.
To create a system process diagram:

1. Right-click the system process name and select New > Diagram.
2. In the window that opens, select System Process Diagram, confirm
that the Diagram initialization check box is selected and click the
Create button.
The system process diagram window opens.
58
System Processes
Tasks
TASKS
Tasks correspond to process steps.
A task is an elementary step that is included within a system
process. A task is used when the work in the system process is not
broken down to a finer level of the process. Generally, an end-user and/
or an IT service are used to perform the task when it is executed.
Creating a task in a system process

To create a task:
1.
2.
In the diagram insert toolbar, click the Task button

the diagram.
Enter the task name and click OK.
then click in
The task appears in the diagram.
59
3
SEQUENCE FLOWS, EVENTS AND MESSAGE FLOWS
Sequence flows
Organization of tasks in the system process is represented by sequence flows
between tasks.
A sequence flow is used to show the order in which steps of a
process will be performed. Each sequence flow has only one source and
only one target.
Events
Events represent facts occurring during process execution.
An event represents a fact occurring during execution of a process,
for example a new contract concluded with a supplier. An event marks
the impact on process progress of a phenomenon internal or external to
the process. There are different natures of events: start events, catch
events, throw events and end events.
An example is the start or end of the system process.
Start
Final
The event can also be sending or receiving a message flow.
60
System Processes
Sequence Flows, Events and Message Flows
Message flows
Message flows represent exchanges between the system process and the exterior.
A message flow can be linked to an event of message type.
61
3
GATEWAYS
Complying with BPMN standard, several gateway types are proposed in the diagram
insert toolbar.
Gateways are modeling elements that are used to control how
sequence flows interact as they converge and diverge within a process.
To better understand the main use cases, we distinguish output gateways of a

processing step from input gateways.
Processing Step Output Gateways

In the case of an Exclusive gateway, only one output branch can be selected from
those available. The branch can be selected as a function of the Data available for
the process, or of the Events occurring during its execution.
In the case of a Parallel gateway, all output branches are processed
simultaneously.
In the case of a Complex gateway, one or several output branches can be selected
from those available.
A Complex gateway represents a combination of those above.
When the gateway has been created, its type can be modified in its properties dialog
box.
At output of a step, a gateway represents a point of divergence of sequence flows
of a process.
Processing Step Input Gateways

At input of a step, a gateway represents a point of convergence of sequence flows
of a process.
In the case of an Exclusive gateway, the process step is triggered when one of
these branches is active.
62
System Processes
Gateways
In the case of a Parallel gateway, all input branches are processed simultaneously.
Creating a Gateway
To create a gateway:
1. Click the arrow at the right of the Gateway button in the diagram insert
toolbar and select the gateway type you wish to create.
2.

The gateway appears in the diagram with shape appropriate to its type.
Modifying a Gateway
To modify a gateway:
1. Right-click the gateway and select Properties.
63
3
In the Characteristics tab, modify the name or type of the gateway.
The different gateway types proposed are:
Complex: the process can take a complex combination of paths.
Exclusive (Data): the process can take a single path from several
possible paths depending on the value of the data available. This is the
default gateway type.
Exclusive (Start): the process is triggered by the first event
occurring; others are ignored.
Exclusive (Event): the process can take a single path from several
possible paths depending on the events occurring.
Inclusive: the process can take one or several paths simultaneously.
Parallel: the process takes several parallel paths simultaneously.
Parallel (Start): the process is triggered by the first event occurring.
The other events occurring during progress of the process are also
taken into account.
3. Click OK.
2.
To display the name of a gateway, masked by default, see "Modifying Object Name
Presentation", page 45.
64
System Processes
Creating a System Process Participant
CREATING A SYSTEM PROCESS PARTICIPANT

In a system process diagram, a participant enables grouping of tasks assigned to
an application or service.
To create a participant:
1. In the diagram insert toolbar, click the arrow at the right of the
Participant button.
2.
In the list proposed, select for example Application Participant and

click in the diagram.
The participant creation dialog box appears.
3.
Click the arrow

at the right of the Application box, and select List
Application.
Click Finish.
The participant created appears in the diagram with a header containing
the name of the assigned application.
4.
To place a participant with assignment as yet unknown, select the

Participant icon.
To assign a task to a participant:
place the task within the frame of the participant.
65
3
SPECIFYING PROCESS BEHAVIOR
Complying with BPMN standard, a process can have different behaviors. With MEGA
Process BPMN Edition, these behaviors are available for organizational processes,
operations, system processes and tasks.
To describe for example that a system process is executed by a loop:
1. Right-click the process and select Properties.
2. In the Characteristics tab, click the arrow at the right of the Loop box.
A list of loop types appears.
3. Select the loop type corresponding to process behavior.
4. Click OK.
Shape of the process is modified to display the symbol of the loop.
Behaviors proposed are:
Transaction: a Transaction is a set of coordinated activities leading to a

consistent, and verifiable outcome.
Loop: a loop is a process step that is repeated as long as a condition is
true.
"Do While": the condition is evaluated before the first execution.
"Do Until": the condition is evaluated after the first execution. In this
case, the process step is executed at least once.
The predicate enables specification of the loop execution condition.
Ad Hoc: steps of an ad hoc process are not controlled or sequenced in a

particular order. Their performance is determined by the performers of
the process.
Multiple: the process is repeated a predefined number of times,
evaluated only once before it is carried out. Execution type can be
specified:
Parallel: all executions carried out simultaneously.
Sequential: executions carried out one after the other.
Compensation: a compensation defines the set of activities that are
performed during the roll-back of a transaction to compensate for
activities that were performed during the normal flow of the process.
66
System Processes
Specifying Process Behavior
Task type can be specified:
In the Characteristics tab, click the arrow at the right of the Task Type
box.
A list of task types appears.
System process call : task used to call a second process while

executing the current process.
Receive: elementary task which waits for arrival of a message from a
participant external to the process. When the message has been
received, the task is completed.
Send: task that sends a message to a participant external to the
process. When the message has been sent, the task is completed.
Manual: task executed without the help of a automatic execution engine
of a process or IT application.
Business rule: execution task of a business rule with a rules engine
which processes input data and returns calculation results.
Script: task executed by a process execution engine. The designer
defines a language that the engine is able to interpret. When the task is
ready to start, the engine executes the script. The task is completed
when script execution is completed.
Shape of the process is modified to display the symbol associated

with the task type.
Compensation description
Compensation is caused by an event occurring during process execution. This event
is placed at the edge of the interrupted process. It can be moved along the edge of
the process.
To free the event from the process, use the detach command in its pop-up menu.
This event can trigger a compensation operation.
For reasons of consistency and simplification, the compensation link

is represented in MEGA by a sequence flow. BPMN standard proposes a
specific link.
67
68
4
ORGANIZATIONAL CHARTS AND
RESPONSIBILITIES
MEGA enables representation of enterprise structure It indicates the hierarchy of org-units in the
enterprise, specifies the persons that play the role of these org-units, and shows at which site the
org-unit is located.
MEGA also enables definition of organizational process responsibilities by means of the RACI matrix
(Responsible, Accountable, Consulted, Informed) as well as business processes.
"Creating an Organizational Chart", page 70

"Business Process Responsibilities", page 75
"Organizational process and operation responsibilities (RACI)", page 77
69
4
CREATING AN ORGANIZATIONAL CHART
"Drawing an Organizational Chart", page 70
"Consulting the RACI Matrix of Org-Units", page 74
The organizational chart presents the structure of the enterprise. MEGA Process
BPMN Edition allows you to design your organizational charts using the same tools
and methods as applied to processes.
MEGA Process BPMN Edition organizational charts contain the following
descriptive objects:
Org-Units, which are generally elements defining the enterprise

structure, such as Sales Department.
Persons such as Ms. Brown, Mr. Smith, etc.
Sites that are geographical locations pivotal to the organization, such as
headquarters, plants, etc.
To create an organizational chart:

1. In the workspace, select the Main Objects navigation window.
The Main Objects window is accessed by selecting View >

Navigation Windows > Main Objects.
2.
Right-click an org-unit and select New > Diagram.
3.
In the diagram creation wizard, click Org-Unit Organizational Chart

then Create.
The corresponding organizational chart opens. It is automatically initialized with the

component org-units of the described org-unit.
Drawing an Organizational Chart

Querying objects
Create, for example, the "Shipping Department" organizational chart.
70
Organizational Charts and Responsibilities

Creating an Organizational Chart
To simultaneously add all the org-units involved in your processes that were not
automatically inserted at diagram initialization:
1.
In the diagram objects toolbar, click button
2.
3.
diagram.
In the Add Org-Unit dialog box, Select Query in the drop-down list.
In the dialog box that appears, click the Find button.
4.
then click in the
The result dialog box appears.

Select the org-units "Stock Manager", "Finished Products Storage",
"Sales Management", "Stock Management" and "Transportation Service"
holding down the <Ctrl> key.
When you click on an object while holding down the <Ctrl> key,
you add it to the list of selected objects if it was not previously selected,
or you remove it from the selection if it was.
71
4
5.
Drag-and-drop the selected objects from the result dialog box into the
diagram.
You may keep your query results in order to reuse them later. To
do this, click button Keep result in new window.
To exit org-unit creation mode, click the Esc button.
Rearrange your organizational chart so that it looks like this:
You can select several objects in the diagram. To do this, hold down
the <Shift> key while clicking on each object you wish to select. You
can also use the mouse to drag a rectangle around the desired objects.
You can assign the same size to several objects by selecting them and
then applying the Make Same Size command in the Drawing menu.
Follow the same steps to align objects: from the Drawing menu, select
Align object. Note that the last object selected is used as the
reference.
If you perform an action that you want to cancel, select Edit > Cancel.
6.
You will now add the sites where the org-units are located.
A site is the geographical location of an organization. Examples:
Boston subsidiary, Seattle plant, and more generally the headquarters,
subsidiaries, plants, warehouses, etc.
7.
Double-click the Site button
in the toolbar and successively add the
sites "Subsidiary", "Sales Office" and "Warehouse".

8. Draw the links between these objects.
Note that certain links might already exist.
72

Creating an Organizational Chart
When you create a link between two org-units, always drag from the org-unit higher
in the hierarchy down to the subordinate. Once the link is drawn, an arrowhead
indicates the direction of the hierarchy.
The name of the org-unit connected to a person is considered as

the job title of that person and is used in the document modification
history.
You can also add persons using the Person
button.
A person holds a position in an organization. He or she is

designated by name. Example: Mr. Smith.
If the Person
button does not appear in the toolbar, add it by
selecting it in the Views window.
Specifying the properties of an org-unit

To specify the properties of an org-unit:
1. Right-click the org-unit.
2. Select Properties.
When an org-unit appears in a diagram, you can describe it with a

new organizational chart using its pop-up menu.
73
4
3.
In the Org-Unit-Type list box, select the org-unit type.
There are several types of org-unit:
An "Accountable" org-unit (for example, Sales Manager).

A "Generic" org-unit: a role to be played during a project (for example,
Writer).
A "Structure" org-unit (for example, Sales Management).
A "Function" org-unit (for example, Sales Engineer).
You can also specify its details (company name, e-mail address,
telephone number, etc.).
Consulting the RACI Matrix of Org-Units

MEGA Process BPMN Edition proposes a report in the form of a matrix which
presents:
the selected org-unit and sub-org-units

the organizational processes and operations in which these org-units
intervene.
RACI is the acronym of Responsible, Accountable, Consulted,

Informed.
To consult the RACI matrix:
In the properties dialog box of the org-unit, select the RACI tab.
To generate the matrix to search for org-units in depth, you must
use report "Org-Unit and Sub-Org-Unit RACI Matrix (BPMN)". For more
details, see "Launching an RACI matrix from an object", page 81
(operation identical to business processes).
74

Business Process Responsibilities
BUSINESS PROCESS RESPONSIBILITIES

From a business process, you can:
define business process control responsibilities

view org-units concerned by the organizational processes connected to
this business process

Informed.
Defining business process control responsibilities

Business process control is the responsibility of persons. The business process
control team therefore comprises a list of persons, with the possibility of indicating
the role of each in the team.
To specify business process control responsibilities:
1. In the properties dialog box of a business process, select the
Characteristics tab.
In the Responsible Persons frame, create or connect the persons

involved in business process control.
3. Specify their roles in the team by selecting the "Yes" or "No" values in
the following drop-down lists:
"Process Manager"
"Process Owner"
"IT Manager"
"Quality Manager"
"Risk Manager"
4. When completed, click Close or select another tab in the properties
dialog box to carry out further modifications.
2.
75
4
Generating an RACI matrix from a business process
From a business process you can generate a matrix presenting:
organizational processes connected to the business process or to its subprocesses

operations of these organizational sub-processes
org-units concerned by these organizational processes and operations
To generate an RACI matrix from a business process:

1. Right-click the business process and select Report Discovery.
2. In the list of available reports, click Process Analysis.
3. From the "Business Process RACI Matrix (BPMN)" report, click Launch a
new report.
4. In the generated report, click the report title.
You obtain a result like this:
To generate a matrix to search for organizational processes and

operations in depth, you must use report "Business Process and SubProcess RACI Matrix (BPMN)". See also "Defining matrix depth level",
page 81.
76

Organizational process and operation responsibilities (RACI)
ORGANIZATIONAL PROCESS AND OPERATION

RESPONSIBILITIES
(RACI)
MEGA Process BPMN Edition enables specification of the responsibility level of

the various org-units:
on an operation
on an organizational process.
The proposed responsibilty levels are as follows:
Responsibility
Meaning
Responsible
Org-unit responsible for the operation or process
Accountable
Org-unit monitoring progress of the operation or process and

taking decisions.
There is only one "Accountable" org-unit for each action.
Consulted
Org-unit consulted as first priority before an action or

decision.
Informed
Org-unit that must be informed after an action or decision.

Informed.
Defining Responsibilities
Organizational process and operation responsibilities
To indicate the responsibility of an org-unit in an operation or organizational
process:
1. Open the properties dialog box of the operation or process.
3. In the "Org-Unit" frame, click the Connect button.
4. In the dialog box that opens, select Candidate Org-Units (RACI).
A dialog box proposes the list of org-units that execute the operation or
the process via a participant.
An org-unit can be connected directly to an operation or process or

indirectly via a participant. An RACI candidate org-unit is an org-unit
assigned to a participant.
5.
Select the org-units that interest you and click OK.

The org-units appear in the properties dialog box of the operation or
process.
77
4
6.
For each of these, in the RACI drop-down list, select a responsibility

level from the four proposed.
Responsible (R)
Accountable (A)
Consulted (C)
Informed (I)
The selected responsibility level appears with an icon corresponding to context:
Icon
Meaning
Indicates that responsibility is deduced from the participant.
The icon appears when the selected org-unit is:
- assigned to the participant, and
- declared with default responsibility: Responsible.
No icon
The icon appears when the selected org-unit is:

- assigned to the participant, and
- declared with responsibility different from default
responsibility.
- The org-unit responsible for the operation is not assigned to
this operation via a participant, or
- The org-unit accountable for the organizational process is not
assigned to this process via a participant.
Responsibility of a participant
To indicate responsibility of each of the org-units attached to a participant in the
different operations or organizational processes it executes:
1. Open the participant properties dialog box.
78

2.
Select the RACI tab.

An analysis report is displayed.
In the example above,

to the participant to
the "Process Purchase
for "Process Purchase
the "Purchasing Department" assigned

which the analysis relates, executes
Request" process and is Accountable
Order".
79
3.
Click button
.
The context of responsibility of the org-unit is indicated. You can view:
the name of the participant to which the org-unit is assigned

the name of the process that is owner of the participant
4.
80
To define the responsibility level of an org-unit related to an operation or

organizational process, click in the corresponding cell
5.
6.
7.
A selection dialog box opens.

Click the arrow at the right to display the list of responsibility levels.
Select the level that interests you.
Click OK in the selection dialog box.
8.
Click button
on the right to refresh the report.

Using RACI Matrices

MEGA Process BPMN Edition allows you to generate reports in the form of
matrices which identify and analyze data of your repository so as to have a clearer
view of the information.
For more details on the use of analysis reports, see the MEGA
Common Features guide.
Launching an RACI matrix from an object

When you launch an RACI matrix form an organizational process, the list of subprocesses is automatically deduced from the links between org-units and
organizational processes/operations.
The following are reports available from an organizational process:
Organizational Process RACI Matrix (BPMN)

This matrix queries organizational sub-processes and operations located
under the organizational process.
Organizational Process and Sub-Process RACI Matrix (BPMN)

This matrix drops n levels to retrieve sub-processes and operations
located under the organizational process.
The principle is the same with org-units and business processes.

Defining matrix depth level
You can choose to increase object query depth.
To define depth level of the matrix:
1. In the report query page, Process Analysis section, select an RACI
report that references sub-objects.
2. Launch the report properties page via the Customize & launch a new
report button.
3. Select the Settings tab, then the Level subtab.
81
4
4.
Click the Create Argument button to create a "Level" setting.
5.
In the properties dialog box of the report setting, go to the bottom, using
the scroll bar if necessary.
Create a level.
Indicate a value in the field provided.
6.
7.
If you enter value "2", the matrix will query sub-sub-processes of

the selected process. Beyond value "3", the matrix will query all
processes located below the selected process, whatever the level.
82

8.
Click OK.
The report appears in the Reports tab.
If you modify setting values, remember to refresh the generated

report.
Creating an RACI with objects of your choice

The "RACI Management (BPMN) report allows you to create a matrix which displays:
org-units in columns
operations or organizational processes in rows
Cells present RACI values: R for Responsible, A for Accountable, C

for Consulted, I for Informed.
To create an RACI matrix with objects of your choice:

1. In the Documentation navigation window, expand the Reports folder.
2. Right-click the sub-folder RACI Management (BPMN) and select New
> Report.
3. Enter a Name for your report and click Next.
4. In the dialog box concerning org-units, click the Create Argument
button.
5. Name the parameter value and click OK.
A query dialog box allows you to select the objects that interest you either
directly or via a query.
6. Click Next.
7. Similarly, in the dialog box concerning organizational processes/
operations, define what you wish to add to the analysis.
8. Click Next then Finish.
The report is displayed in the edit area.
9. Click the paragraph "RACI Management Matrix".
Click button
on the right to refresh the report if you have
modified objects or parameters of the report.
83
84
5
BUSINESS PROCESSES
This chapter presents how to describe products or services supplied by processes of the enterprise
to its customers.
The business process diagram enables representation of product or service offerings proposed by
the enterprise to each of its markets, as well as the processes that produce these.
MEGA enables creation and definition of enterprise business processes.
"Creating a Business Process", page 86

"Representing Product Offerings", page 87
"Representing Process Contextualization", page 89
85
5
CREATING A BUSINESS PROCESS
To create a business process from the navigator:
A business process represents a system that offers products or
services to an internal or external client of the company or organization.
At the higher levels, a business process represents a structure and a
categorization of the business. It can be broken down into other
processes. The link with organizational processes will describe the real
implementation of the business process in the organization. A business
process can also be detailed by a functional view.
1.
2.
3.
Right-click the current library.

Select New > Business Process.
The Create Business Process dialog box appears.
Enter the name of the business process in the Name box.
4. Click OK.
The business process is created and added to the list of business processes.
The OK button is grayed if the Name box is not completed.

In MEGA, business processes are described by diagrams.
Creating a Business Process Diagram

To create a business process diagram:
1. Right-click the business process name and select New > Diagram.
2.
86
In the dialog box that opens, select "Business Process Diagram and
click the Create button.
The diagram window opens.
Business Processes
Representing Product Offerings
REPRESENTING PRODUCT OFFERINGS

The business process diagram enables representation of product or service offerings
proposed by the enterprise to each of its markets, as well as the processes that
produce these.
In the example above, the enterprise is targeting two

customer segments, those that rent boats, and those to whom
cruises are proposed.
In the case of boat rental, the enterprise also proposes
flight ticket reservation, hotel or guesthouse reservation
and car rental.
In the case of cruises, the enterprise also proposes flight
ticket reservation, hotel reservation and car rental.
Defining Offerings
Offerings are proposed by enterprise business processes to participants outside the
enterprise.
An offering represents the making available of a product or service
supplied by an enterprise through a specific process.
Creating an offering
To create an offering:
1.
Click the Offering
button
87
5
2.
3.
Click the business process and, holding the mouse button down, draw a
link to the participant.
Release the mouse button.
The link representing the offering appears in the diagram.
Defining offering products

A product represents commodities offered for sale, either goods or
merchandise produced as the result of manufacturing, or a service, ie.
work done by one person or group that benefits another.
To specify detail of offerings of products:

1. Right-click the offering and select Properties.
3. Click the New button in the Products section and enter the name of the
product in the field that appears.
4. Select the name of the product, then click OK.
The name of the product appears in the diagram.
A product can be broken down into component products from its

properties dialog box or from the navigator.
Initializing the business process diagram

A new process diagram appears in the following form:
If you create a business process diagram in a particular context, for

example the "Provide Vacations with Boat Rental" process
and you selected the Diagram initialization check box before clicking
Create in the business process diagram creation dialog box.
The diagram is initialized with:
88
A participant representing the recipient of products exchanged by the

process with the exterior.
The products themselves, described by message flows and with contents
corresponding to the products of service offers associated with the
described process.
A start event and an end event.
Business Processes
Representing Process Contextualization
REPRESENTING PROCESS CONTEXTUALIZATION

"Defining a Contextualization", page 89
"Launching a Report Illustrating Contextualizations", page 90
The business process diagram enables representation of the context in which the
organizational or functional processes comprising the business process are used.
See "Functional Processes" for more details on functional

processes.
See "Organizational Processes" for more details on organizational
processes.
Purchasing business process diagram
In the example above, enterprise purchase processes are

shared between operational purchase processes and
investment purchase processes.
A specific organizational process is defined to process
urgent purchase of car maintenance.
Defining a Contextualization
Contextualizations enable association of processes between themselves.
A contextualization allows specification of the implementation of a
process by another process in a specific context, such as the
geographical location on a site.
89
5
Creating a contextualization
To create a contextualization:
1.
2.
Click the Contextualization

button
Click the process to be implemented and, holding the mouse button
down, draw a link to the process describing implementation. Release the
mouse button.
The link representing the contextualization appears in the diagram.
Defining context
To specify the context in which a process implements another process:
1. Right-click the contextualization and select Properties.
3. Click the Connect button in the Implementation Context section.
4. Enter the context type, org-unit or site, in the dialog box that opens.
5. Click the Find button.
6. In the list that appears, select the org-units or sites concerned and click
OK.
7. Click the Close button.
The implementation contexts appear in the diagram.
Launching a Report Illustrating Contextualizations

From a business process, you can launch a report in the form of a matrix to illustrate
contextualizations.
To launch a report illustrating contextualizations:
1. Right-click the business process concerned and select Report
Discovery.
2. In the list of available reports, expand the "Process Analysis" folder.
3. From the "Business Process Contextualization Matrix (BPMN)" report,
click Launch a new report.
90
Business Processes
Representing Process Contextualization
4.
In the page of the report, click the report name.

A matrix appears.
This matrix presents:
the functional processes of the business process in columns

the organizational processes of the business process in rows
To view a specific context (org-unit, site or product):
Click the + in the cell.
91
92
6
GLOSSARY
application
An application is a set of software tools coherent

from a software development viewpoint.
business function
A business function is a skill or grouping of skills

of interest for the enterprise.
business process
A business process represents a system that

offers products or services to an internal or
external client of the company or organization. At
the higher levels, a business process represents
a structure and a categorization of the business.
It can be broken down into other processes. The
link with organizational processes will describe
the real implementation of the business process
in the organization. A business process can also
be detailed by a functional view.
constraint
A constraint is represented by a check or a

business rule that must be applied during
processing.
content
A content designates the content of a message

flow or message, independently of its structure.
A content may be used by several message flows
or messages, since it is not associated with a
sender or with a recipient.
contextualization
A contextualization allows specification of the

implementation of a process by another process
in a specific context, such as the geographical
location on a site.
dashboard
A dashboard enables preparation of a list of

objectives
and
indicators
required
for
management of an enterprise business process,
application or org-unit such as a service.
93
94
data object
A data object is used to explain how documents,

data, and other objects are used and updated
during the process. A data object can represent
an electronic document, or any other type of
object, electronic or physical.
data store
A data store provides a mechanism to update or

consult data that will persist beyond the scope of
the current process. It enables storage of input
message flows, and their retransmission via one
or several output message flows.
diagram
A diagram is used to store drawings such as

flowcharts and organizational charts produced by
the graphic tool.
event
An event represents a fact occurring during

execution of a process, for example a new
contract concluded with a supplier. An event
marks the impact on process progress of a
phenomenon internal or external to the process.
There are different natures of events: start
events, catch events, throw events and end
events.
external org-unit
An external org-unit is an organization that

exchanges flows with the enterprise. Example:
customer, supplier, government office.
functional activity
A functional activity is a step in a process. This

step represents the contribution of a business
line to the process value chain.
functional process
A functional process is a value chain providing

results as goods or services, to an internal or
external client of the enterprise or organization.
This value chain is described as a sequence of
activities.
gateway
Gateways are modeling elements that are used to

control how sequence flows interact as they
converge and diverge within a process.
issue
An issue is an event preventing achievement of

fixed objectives for which a solution must be
found.
IT service
An IT service is a component of an application

that is available to the end user of the
application.
Glossary
junction
A junction is a grouping point for several

branches of the processing flow. It specifies that
completion of one of the grouped processing
procedures is awaited before continuing.
keyword
A keyword is a classifying description which

permits characterization of objects. A keyword
can be connected to any object.
message flow
A message flow is information flowing within an

enterprise or exchanged between the enterprise
and its business environment. A message flow
can carry a content.
objective
An objective is a goal that a company/

organization wants to achieve, or is the target set
by a process or an operation. An objective allows
you to highlight the features in a process or
operation that require improvement.
offering
An offering represents the making available of a

product or service supplied by an enterprise
through a specific process.
operation
An operation is an elementary step in an

organizational process executed by an org-unit.
It cannot be broken down. An operation can be
industrial
(manufacturing
a
component),
logistical (receiving a delivery), or can involve
information processing (entering an order).
organizational process
An organizational process is a set of operations

performed by org-units within a company or
organization, to produce a result. It is depicted as
a sequence of operations, controlled by events
and conditions.
org-unit
An org-unit represents a person or group of

persons participating in the processes or
information system of the enterprise. An org-unit
can be internal or external to the enterprise. An
internal org-unit is an organizational element of
enterprise structure such as a management,
department, or job function. It is defined at a
level depending on the degree of detail to be
provided on the organization (as org-unit type).
Example:
financial
management,
sales
management, marketing department, account
manager. An external organization unit is an
organization that exchanges flows with the
enterprise.
Example:
customer,
supplier,
government office.
95
96
parallelism
A parallelism is the simultaneous processing of

the different parts of a business process.
participant
A participant defines a partition of the actions of

a process that will be assigned to a same agent.
participant (org-unit)
A participant (org-unit) enables representation of

org-units assigned to execution of a group of
operations of a process.
person
A person holds a position in an organization. He

or she is designated by name. Example: Mr.
Smith.
product
A product represents commodities offered for

sale, either goods or merchandise produced as
the result of manufacturing, or a service, ie. work
done by one person or group that benefits
another.
project
A project is a part of a system whose study is

entrusted to the same team.
sequence flow
A sequence flow is used to show the order in

which steps of a process will be performed. Each
sequence flow has only one source and only one
target.
site
A site is the geographical location of an

organization. Examples: Boston subsidiary,
Seattle
plant,
and more generally the
headquarters, subsidiaries, plants, warehouses,
etc.
Glossary
system process
A
system
process
is
the
executable
representation of a process. The elements that
formalize a system process are the following: the
events of the workflow, the tasks to be carried
out during the processing, the algorithmic
elements used to specify the way in which the
tasks follow each other, the information flows
exchanged with the participants.
system used
A system used during the execution of a step of

a process represents what is necessary to realize
this step. It can be an application or an IT
service, or any other non IT resource, or more
generally a functionality.
task
A task is an elementary step that is included

within a system process. A task is used when the
work in the system process is not broken down to
a finer level of the process. Generally, an enduser and/or an IT service are used to perform the
task when it is executed.
97
98
INDEX
business process diagram . . . . . . . . . . . . . . 86
accountable
org-unit . . . . . . . . . . . . . . . . . . . . . . . . 74, 77
RACI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Ad Hoc
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
cancel
object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
catching
system used . . . . . . . . . . . . . . . . . . . . . . . . 54
compensation
adding notes
application
assignment
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
participant . . . . . . . . . . . . . . . . . . . . . . . . . 40
event type . . . . . . . . . . . . . . . . . . . . . . . . 34
event nature . . . . . . . . . . . . . . . . . . . . . . . 34
event type . . . . . . . . . . . . . . . . . . . . . . . . 34
process. . . . . . . . . . . . . . . . . . . . . . . . . . . 66
conditional
event type . . . . . . . . . . . . . . . . . . . . . . . . 34
conditioned
sequence flow . . . . . . . . . . . . . . . . . . . . . . 19
consulted
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . 77
responsibility. . . . . . . . . . . . . . . . . . . . . . . 78
content
BPMN activity
activity (functional) .
functional process . .
operation . . . . . . . .
task . . . . . . . . . . . .
business function
functional process .
manager . . . . . . .
business process . . .
contextualization . .
RACI matrix . . . . .
responsibility . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
. 51
. 18
. 59
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
. 75
. 85
. 89
. 76
. 75
message flow . . . . . . . . . . . . . . . . . . . . . . 21
contextualization
business process . . . .
functional process . . .
process. . . . . . . . . . .
report. . . . . . . . . . . .
system process . . . . .
control
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
89
89
89
89
90
56
business process . . . . . . . . . . . . . . . . . . . . 75
process. . . . . . . . . . . . . . . . . . . . . . . . . . . 75
correction
note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
99
Index
D
data object
folder
organizational process . . . . . . . . . . . . . . . . . 26
data store
default
sequence flow . . . . . . . . . . . . . . . . . . . . . . 20
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
diagram
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
swimlane
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
font
text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
functional
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
functional process
activity. . . . . . . . . . . . . . . . .
business function. . . . . . . . . .
value chain . . . . . . . . . . . . . .
functional process diagram . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
. 53
. 50
. 52
functionality
system used . . . . . . . . . . . . . . . . . . . . . . . . 54
E
G
end
event nature . . . . . . . . . . . . . . . . . . . . . . . 34
error
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
system process . . . . . . . . . . . . . . . . . . . . . . 62
escalation
event
event nature
..............
event type . . . . . . . . .
organizational process .
system process. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
34
34
33
60
catching. . . .
combination .
end . . . . . . .
start . . . . . .
throwing . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
34
35
34
34
34
event nature
event type
.
.
.
.
.
cancel . . . . . .
combinations .
compensation .
conditional . . .
error . . . . . . .
escalation . . .
link . . . . . . . .
message . . . .
multiple . . . . .
none . . . . . . .
signal . . . . . .
terminate. . . .
timer . . . . . . .
100
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
34
35
34
34
34
34
34
34
34
34
34
34
34
generic
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
I
improvement
note. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
improving
presentation . . . . . . . . . . . . . . . . . . . . . . . . 43
informed
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
responsibility . . . . . . . . . . . . . . . . . . . . . . . 78
inserting
IT
shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
manager
process . . . . . . . . . . . . . . . . . . . . . . . . . 75
IT service
system used . . . . . . . . . . . . . . . . . . . . . . . . 54
Index
link
object
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
formatting . . . . . . . . . . . . . . . . . . . . . . . . . 46
offering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
creating . . . . . . . . . . . . . . . . . . . . . . . . . . 87
product. . . . . . . . . . . . . . . . . . . . . . . . . . . 88
loading
location
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
loop
system process . . . . . . . . . . . . . . . . . . . . . . 66
adding notes . . . . . . . . . . . . . . . . . . . . . . . 43
operation
creating . . . .
organizational
RACI . . . . . .
responsibility .
......
process
......
......
organizational chart . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18
18
77
77
69
.
.
.
.
.
.
.
.
.
.
.
organizational process diagram .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
26
28
33
14
29
21
18
24
77
77
19
24
M
management
quality
process . . . . . . . . . . . . . . . . . . . . . . . . . 75
risks
process . . . . . . . . . . . . . . . . . . . . . . . . . 75
manager
business function . . . . . . . . . . . . . . . . . . . . 75
IT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
manual
data object . .
data store . . .
event . . . . . .
example . . . .
gateway . . . .
message flow
operation . . .
organizational
RACI . . . . . .
responsibility .
sequence flow
............
............
............
............
............
............
............
process diagram
............
............
............
org-unit
accountable. .
assignment . .
generic . . . . .
participant . .
responsibility.
structure. . . .
type . . . . . . .
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
message
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
message flow
content . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
system process . . . . . . . . . . . . . . . . . . . . . . 61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
74
40
74
40
77
74
73
assignment . . .
org-unit . . . . .
process. . . . . .
responsibility. .
system process
task . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
40
40
39
78
65
65
multiple
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
P
participant
note
note type . . . . . . . . . . . . . . . . . . . . . . . . . . 43
pool
diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 42
presentation
improving . . . . . . . . . . . . . . . . . . . . . . . . . 43
procedure
responsibility. . . . . . . . . . . . . . . . . . . . . . . 77
101
Index
process
Ad Hoc . . . . . . . . . . . . . .
compensation . . . . . . . . . .
contextualization . . . . . . .
functional. . . . . . . . . . . . .
loop . . . . . . . . . . . . . . . .
multiple . . . . . . . . . . . . . .
organizational. . . . . . . . . .
participant . . . . . . . . . . . .
task type . . . . . . . . . . . . .
transaction. . . . . . . . . . . .
viewing external processes
product
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
66
66
89
50
66
66
14
39
67
66
37
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
offering . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
S
send
event nature . . . . . . . . . . . . . . . . . . . . . . . . 34
sequence flow
conditioned. . . . . . . .
conditioning . . . . . . .
creating . . . . . . . . . .
default . . . . . . . . . . .
moving. . . . . . . . . . .
sequence flow . . . . . .
system process . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
default . . .
folder . . . .
inserting. .
manual. . .
modifying .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . 44
. . . . 44
. . . . 46
. . . . 44
. 44, 45
shape
signal
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
. 19
. 19
. 20
. 19
. 19
. 19
. 60
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
quality
management
process. . . . . . . . . . . . . . . . . . . . . . . . . 75
question
note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
start
event nature . . . . . . . . . . . . . . . . . . . . . . . . 34
structure
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
style
row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
swimlane
pool
diagram . . . . . . . . . . . . . . . . . . . . . . . . 42
system process
RACI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77, 81
business process. . . . . . . . . . . . . . . . . . . . . 76
RACI matrix
depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
remark
note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
resource
contextualization .
creating . . . . . . .
event . . . . . . . . .
gateway . . . . . . .
message flow . . .
sequence flow . . .
task . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
system process diagram .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 56
. 56
. 60
. 62
. 61
. 60
. 59
. 56
system used
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
system used. . . . . . . . . . . . . . . . . . . . . . . . 54
responsibility
level . . . . . . . . . . . . .
organizational process .
org-unit . . . . . . . . . . .
participant . . . . . . . . .
responsible
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
78
77
77
78
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
responsibility . . . . . . . . . . . . . . . . . . . . . . . 78
task
management
process. . . . . . . . . . . . . . . . . . . . . . . . . 75
task type
risk
row
style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
102
participant . . . . . . . . . . . . . . . . . . . . . . . . . 65
system process . . . . . . . . . . . . . . . . . . . . . . 59
business rule . . . . . . . . . . . . . . . . . . . . . . . 67
manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Index
process . . . . . . . .
receive. . . . . . . . .
script . . . . . . . . . .
send . . . . . . . . . .
system process call
terminate
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 67
. 67
. 67
. 67
. 67
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
text
font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
timer
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
transaction
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
type
org-unit
properties . . . . . . . . . . . . . . . . . . . . . . . 73
V
value chain . . . . . . . . . . . . . . . . . . . . . . . . . . 51
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
functional process . . . . . . . . . . . . . . . . . . . . 50
W
warning
note. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
103
Index
104

MEGA Process BPMN Edition en

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

MEGA Process BPMN Edition en

Încărcat de

Drepturi de autor:

Formate disponibile

MEGA Process BPMN Edition

MEGA 2009 SP5 R6

Why Model the Activity of My Enterprise? . . . . . . . . . .