surendro15@gmail - cdn-edunex.itb.ac.id
Transcript of surendro15@gmail - cdn-edunex.itb.ac.id
2
Process Modeling
• Process Modeling requires a critical set of skills and techniques
that enable people to understand, communicate, measure, and
manage the primary components of business processes.
• Business Process Modeling is the set of activities involved in
creating representations of an existing or proposed business
process. It can provide an end-to‐end perspective or a portion of
an organization’s primary, supporting, or management processes.
3
Process Modeling
A model refers to a simplified representation of a thing, concept, or
activity. Models can be mathematical, graphical, physical, narrative, or
a combination of these.
Models have a wide range of applications in business environments,
including
Organizing (structuring)
Discovery (learning)
Forecasting (predicting)
Measuring (quantifying)
Explaining (teaching, demonstration)
Verification (validation)
Control (constraints, objectives).
Business processes can be expressed through modeling at many
levels of detail, ranging from highly abstract to highly detailed. A
fully‐developed business process model will typically represent several
perspectives serving different purposes.
4
Process Model Contents
A process model includes icons that represent workflow, data flow,
events, decisions, gateways, and other elements of the process itself.
A process model can contain illustrations and information about
The icons (representing the process elements) used in the
illustrations
The relationships among the icons
The relationships of the icons to their environment
How the icons represented behave or perform.
6
Process Components
Process components specify the properties, behavior, purpose, and
other elements of the business process. You can use some modeling
tools to capture and catalogue process components and the
information associated with each component to organize, analyze, and
manage an organization’s portfolio (i.e., collection) of processes.
7
Purpose of Process Modeling
Process models are the means to
• Manage organization processes
• Analyze process performance
• Define changes.
Process models can express a target business state or specify the
requirements for resources to enable effective business operations,
such as people, information, facilities, automation, finance, and energy.
9
Commonly Used Process Modeling Notations
For example, musical notation includes universally recognized symbols
for notes and clefs. Similarly, a business process modeling notation
includes icons (pictures) and connectors that help show relationships
among the various real‐life components of a business process.
17
Event Process Chain (EPC)
Event Process Chains range from very
simple to very complex.
EPC describes events as either
triggering or resulting from a process
step, called a “function.” Thus, the flow
is normally event‐function‐event. EPC
relies heavily upon logical operators
called “rules.” The basic rule objects
are “AND,” “OR,” and “Exclusive OR.”
These rule objects express decisions,
tests, parallelism, and convergence in
the process flow. A simple EPC
consists of just these objects plus
arrows that define relationships
between them.
19
IDEF
IDEF is a family of modeling notation concepts that are described in a Federal
Information Processing Standard (FIPS) that was developed by the US Air
Force. It is a notation and technique that is one part of a methodology for
defining the work processes and information systems in manufacturing
environments.
20
IDEF
The notation employs a very simple set of symbols consisting of process boxes with
arrows showing inputs, outputs, controls, and mechanisms. Although each level of the
model is read left to right and top to bottom, the numbering system used for the major
steps are represented in a way that allows for easy association between parent and
child levels of decomposition in the process. Thus, a child process box named A1.3 is
interpreted to be a child process of the parent diagram A1. Each successive level of
decomposition uses another decimal point to continue this easy traceability of lineage.
21
Value Stream Mapping
Value Stream Mapping is a technique used in Lean Manufacturing. Not to be
confused with Value Chain notation, Value Stream Mapping expresses the physical
environment and flow of materials and products in a manufacturing environment.
At Toyota, where the technique originated, it is known as "Material and Information
Flow Mapping." Value Stream Mapping is used to add process resource costs and
time elements to a process model, to incorporate the view of the process efficiency.
23
Value Chain
Value chain notations are a category of symbol sets used to visualize the accumulation of
value or steps toward achievement of a goal.
Sometimes groups of steps are summarized under a “process superior” object. These
models generally flow from left to right, describing the sub‐processes that directly
contribute to producing value for the organization’s customers (clients or constituents).
The concept of the value chain was introduced by Michael Porter in his works on
corporate strategy and is typically applied at the enterprise modeling and planning level.
24
SIPOC
SIPOC stands for Supplier, Input, Process, Output, and Customer. It is a style of
process documentation used in Six Sigma. There is no standard or preferred
notation set and this technique may be satisfied by completing a table with those
headings.
The SIPOC model is often used to gain an initial consensus on what areas of a
process are under study.
25
System Dynamics
• System Dynamics models are “activity on arrow” diagrams rather than
“activity on node” diagrams like most of the other notations.
• System Dynamics models are especially useful in developing dynamic
lifecycle‐type models that focus on the overall business system’s
performance and the impact of changing the key variables that affect
overall performance.
• These are more often used to model an entire enterprise or line of
business rather than lower‐level workflow type models. System
Dynamics models are often used to describe the enterprise business
“architecture” from a dynamic behavioral perspective, rather than a static
structural perspective.