CUIB KEN

CHAPTER 4
INTRODUCTION TO BUSINESS PROCESS MODELLING (BPM)

What is a Business Process?

A business process is a collection of linked, structured activities or tasks performed by people

or equipment to achieve a specific organizational goal. It takes one or more types of input and
produces an output that is valuable to the customer.

Modelling: The act of creating an abstract representation (a model) of a process to understand,

analyze, and improve it.

Key characteristics
• Definability: A clear beginning and end, with well-defined boundaries, inputs, and
outputs.
• Repeatability: The process can be executed multiple times, leading to consistent
results.
• Ordered sequence: The steps are performed in a specific, logical order.
• Value-adding: The process transforms inputs into outputs that provide value to a
customer or the next stage in the workflow.
• Flexibility: The process can be adapted and changed without disrupting operations.
• Measurability: Performance can be tracked and evaluated using metrics to identify
areas for improvement.
• Customer-oriented: The ultimate goal is to satisfy the needs of the customer or end-
user.
• Strategic alignment: The process supports the larger goals and strategy of the
organization.
• Cross-functional: While not always, many processes span multiple departments or
functions within an organization.
• Ownership: Each process should have a designated owner responsible for its
performance.
Business Process Modeling (BPM)
This is the practice of representing an enterprise's business activities, information flow, and
decision logic in a graphical form. This visual representation, often using flowcharts and
diagrams, helps analyze, document, and improve how work is done within an organization.
CUIB KEN

Core Concepts:
• Abstraction: BPM simplifies complex reality by focusing on the essential elements
of the process, ignoring irrelevant details.
• Standardization: It uses a standardized notation (like BPMN) to ensure that the
models are universally understood by all stakeholders (business and IT).
• Visualization: "A picture is worth a thousand words." Visual models make it easier to
communicate how a process works. BPM uses diagrams like flowcharts to illustrate a
business's activities, information flow, and decision logic.
• Purpose: Its main goals are to document current processes, find areas for
improvement, and enable automation.
• Methodology: It involves capturing how a business works in order to analyze and
optimize it.
Importance:
In today's competitive environment, organizations cannot rely on ad-hoc, undocumented
processes. BPM provides a single source of truth about how work is actually done (As-Is)
versus how it should be done (To-Be). It is the critical first step in Business Process
Management (the broader discipline of managing and improving processes).

Key Takeaway: BPM is not the process itself; it is the blueprint or map of the process.

The "Why": Benefits and Strategic Value

Implementing BPM offers tangible benefits across the organization:
1. Clarity and Understanding: Provides a clear, shared understanding of processes,
reducing ambiguity and miscommunication between departments.
2. Process Analysis and Identification of Inefficiencies: Visual models make it easy to
spot bottlenecks, redundancies, delays, and unnecessary steps (e.g., rework loops,
approvals from five managers).
3. Standardization and Consistency: Ensures that a process is performed the same,
efficient way every time, regardless of who executes it, leading to predictable quality.
4. Training and Onboarding: Process models serve as excellent training materials for
new employees, helping them understand their role in the larger workflow.
5. Facilitates Process Improvement: The model is the baseline for improvement
methodologies like Lean (eliminating waste) and Six Sigma (reducing variation). It
allows for "what-if" simulation before implementing costly changes.
6. Foundation for Automation: A clearly defined process model is a prerequisite for
successful Robotic Process Automation (RPA) and workflow automation. You cannot
automate a process you don't understand.
7. Compliance and Governance: Models provide documented evidence of processes for
regulatory audits (e.g., SOX, ISO) and help ensure that controls are in place.
Key components of a BPM PPT
• Visual representation: Uses diagrams, flowcharts, and other visual aids to show
processes.
• Standardized notation: Often employs notations like Business Process Model and
Notation (BPMN) to ensure consistency and clarity. Common symbols include:
CUIB KEN

− Rectangles: Activities or tasks

− Diamonds: Decision points or gateways
− Arrows: Sequence flow
− Ovals: Start and end points
− Swimlanes: Delineate ownership or responsibilities between different roles or
departments

• Process analysis: Helps identify bottlenecks, inefficiencies, and areas for

improvement.
• Stakeholder alignment: Provides a shared, visual language for all involved parties to
agree on process objectives.
• Data-driven insights: Can be used to present quantitative data and simulate potential
changes before implementation.
• Automation foundation: Establishes a clear view of existing processes, which is
essential before automating workflows.
CUIB KEN

Purpose of a BPM
• Documentation: Records and documents business processes for clarity and future
reference.
• Improvement: Facilitates continuous improvement by highlighting what is working
well and what can be optimized.
• Training: Provides new employees with a quick way to understand how their work fits
into the larger operational framework.
• Communication: Enables clear communication of complex processes to both technical
and non-technical audiences.

ASSIGNMENT
Go to [Link]
Sign up to the Lucid chart
Add me to your Lucidgroup using the email nkomekole@[Link]
Consider a business process such as enrolment at CUIB.
Design a business process flow for this activity.

Core Components of a Business Process

Every business process can be broken down into fundamental components:

1. Tasks/Activities: The individual units of work. The basic building blocks of a

process (e.g., "Approve Invoice," "Verify Customer Identity").
2. Events: Something that happens during the process. They can start (trigger), interrupt,
or end a process (e.g., "Purchase Order Received," "Payment Due Date Reached").
3. Gateways: Decision points that control the flow of the process. They are typically
represented as diamonds and can be exclusive (XOR - one path), inclusive (OR -
multiple paths), or parallel (AND - all paths).
4. Sequence Flows: Arrows that show the order in which activities are performed.
(activities, events, and branches) are triggers that illustrate a behavior within a
business process. These flow objects can start, modify, or end a process.
5. Participants (Swimlanes): The "who" in the process. This includes:
o Pools: Represent different organizations or major departments (e.g.,
Customer, Finance Department).
o Lanes: Sub-divisions within a pool, representing specific roles, teams, or
systems (e.g., Sales Representative, Accounts Payable Clerk, CRM System).
6. Data & Artifacts: The "what" that is being worked on. This includes data objects
(e.g., Invoice, Application Form), data stores, and annotations for clarification.
CUIB KEN

• The “activities“, which allow the execution of tasks, sub-processes, and activities, are
actions to be carried out to achieve the objective of the process. They can involve human
activity, such as user and manual tasks, but can also be automated in the context of
tasks, services, and scripts. If necessary, sub-processes can be used to specify and
isolate behaviors. Rectangles with rounded corners represent them.
CUIB KEN

• The “transitions” or “connections” link the different steps together.

The “gateways” direct the flows towards the following stages.

Gateways:

Gateways are steps in the process of divergences or convergences of the flow. They are able
to describe the sequence flow path of a process.

They are represented by diamonds, in the center of which is a symbol that indicates the
possible flow outputs. An exclusive gateway can be represented without a pictogram, both
CUIB KEN

possibilities exist.
We can see 5 types of gateways: parallel, exclusive, inclusive, event-based, and complex:

“Parallel” process gateways parallelize or merge the flow to indicate that tasks can be
performed simultaneously.

“Exclusive” gateways direct the process to a single transition.

“Inclusive” gateways can conditionally parallelize.

“Event-based” gateways have conditions based on events. They are used to put the process on
hold for different events.
CUIB KEN

BPMN 2.0 in Depth: Key Elements and Symbols

Category Element Symbol Description & Use Case

Events Start Event ⬤ (Single thin Triggers the process. E.g., "Customer
line) Submits Order."
Intermediate ⬤ (Double thin Occurs during the process. E.g., a timer
Event line) event for a reminder.
End Event ⬤ (Single thick Result of the process. E.g., "Order
line) Shipped."
Activities Task ▬ A single unit of work. Cannot be broken
down further in the diagram.
Sub-Process ▬[+] A compound activity that can be broken
down into a separate, lower-level
process. The [+] indicates it is expanded.
Gateways Exclusive ◇ (X inside) A decision point; only one path can be
(XOR) taken. E.g., "Is amount > $10,000?"
Parallel ◇ (+ inside) Splits the flow into multiple parallel
(AND) paths; ALL must be completed.
Inclusive ◇ (O inside) One or more paths can be taken based on
(OR) conditions.
Connectors Sequence ———> Shows the order of activities.
Flow
Message - - - -> Shows messages between different Pools
Flow (e.g., between Company and Customer).
Swimlanes Pool 🠖 Large Represents a major participant.
Rectangle
Lane Horizontal Represents a specific role or department
division within a within the Pool.
Pool

Other Modelling Notations: A Brief Overview

While BPMN is the most common, other notations exist:

1. Flowcharts: The simplest form of process diagram. Good for high-level, basic
workflows but lacks the semantic richness for complex business logic and interactions
between participants.
2. UML Activity Diagrams: Part of the Unified Modeling Language (UML), primarily
used in software engineering. It shares similarities with BPMN but is less business-
user-friendly and focuses more on system behavior.
3. EPC (Event-Driven Process Chain): A notation popularized by SAP. It is strong in
representing the control flow and is closely tied to the organizational data model. It
uses events to drive the process from one function to the next.

Why BPMN is Preferred: BPMN offers the best balance of simplicity for business users and
precision for technical implementation, making it the most versatile and widely adopted
standard.
CUIB KEN

To better understand how a process works in BPMN, we need to imagine a process instance,
like a token that advances in the process, and that can split or merge according to the actions
to be performed during the mangement of this process instance.

BPM Software Tools

BPM can be done with simple tools, but dedicated software enhances efficiency and
collaboration.

• Basic/Generic Tools:
o Whiteboards & Sticky Notes: Excellent for initial collaborative workshops
and brainstorming.
o Microsoft Visio & [Link] ([Link]): Powerful diagramming tools with
BPMN stencils. Good for static models. [Link] is free and highly capable.
• Dedicated BPM Suites:
o Signavio, ARIS, iGrafx: Enterprise-grade platforms. They support the entire
BPM lifecycle—from modelling and simulation to publishing models in a
central repository and monitoring live processes.
o Bizagi Modeler: A popular free modeller that is fully BPMN 2.0 compliant,
excellent for individuals and teams starting out.
• Automation Platforms with Modellers:
o Appian, Pega, Microsoft Power Automate: These platforms include BPMN-
like modellers to directly design and execute automated workflows.

Tool Selection Criteria: Consider cost, collaboration features, repository capabilities,

simulation features, and integration with execution engines.

Best Practices and Common Pitfalls

Best Practices:

1. Start Simple: Don't try to model your entire enterprise at once. Begin with a critical,
well-scoped process.
2. Involve the Right People: Include process participants, owners, and customers in the
modelling sessions.
3. Use a Consistent Level of Detail: A high-level model should not suddenly dive into
minute, system-level details. Create different diagrams for different audiences (e.g.,
executive summary vs. operational manual).
4. Focus on the "Happy Path" First: Model the most common, successful scenario
before adding all exceptions and error handling.
5. Validate with Stakeholders: Walk through the model with end-users to ensure it
accurately reflects reality.

Common Pitfalls to Avoid:

1. Analysis Paralysis: Over-modelling and never moving to the improvement stage.

2. Creating "Spaghetti" Models: Overly complex diagrams with crossing lines and no
swimlanes. If it looks like a plate of spaghetti, it's too complex.
CUIB KEN

3. Modelling the "Ideal" instead of the "Real": Documenting how the process should
work according to a manual, not how it actually works.
4. Ignoring Swimlanes: Failing to assign responsibilities makes it impossible to see
handoffs and bottlenecks between roles.
5. Using Non-Standard Notation: Inventing your own symbols defeats the purpose of a
standard like BPMN.

The Future of BPM and Conclusion

The Future:

• Process Mining: Technology that automatically discovers processes by analyzing

event logs from IT systems (like ERP and CRM), comparing the actual process flow
against the conceptual model.
• AI-Powered BPM: Using AI to recommend process optimizations, predict
bottlenecks, and even generate process models from natural language descriptions.
• Hyperautomation: The combination of BPM with RPA, AI, and other technologies
to automate increasingly complex work.

Conclusion:
Business Process Modelling is a fundamental skill for modern organizations. It transforms
abstract workflows into tangible, analyzable, and improvable assets. By providing a clear,
visual language (like BPMN), it empowers organizations to break down silos, enhance
communication, and systematically drive efficiency, quality, and agility. Mastering BPM is
the first and most crucial step on the journey to becoming a process-excellent organization.