SMARTER SUPPLY CHAINS. STRONGER BUSINESS.
Supply Chain Partners — Connecting People, Process, Technology

SCP expertise / Tools and techniques

Process Mapping and Analysis

Understand the work, agree the handovers and choose a map people can use.

Process mapping as a business conversation

Choose a map the audience can use.

A process map should help people agree how work happens, where responsibilities pass between teams and what needs to change. SCP would select the framework, notation and level of detail around that purpose and the people involved.

APQC Process Classification Framework®

Which processes should we consider?

APQC’s PCF is a reference taxonomy: a structured set of process categories and names that can provide a common language for organising work and comparing performance. Use it to check coverage, group related activities and connect process ownership and measures.

It does not prescribe a complete workflow for every organisation. Select and adapt relevant processes, then map how they actually operate across the client’s teams and systems. A classification framework and a workflow map serve different purposes.

APQC: process frameworks ↗

BPMN / Object Management Group

How should the workflow be described precisely?

Business Process Model and Notation (BPMN) provides standard symbols and rules for process behaviour. It is intended to connect business understanding with technical implementation, and can represent events, activities, decisions, participants and messages.

Use it when precise exceptions, system interactions or delivery handovers matter. A restrained, well-explained BPMN model can work for business users; a dense model with specialist detail may need a simpler companion view.

OMG: BPMN overview and standard ↗

Business-facing views

What helps people understand and agree?

Use a simple flowchart or swimlane map to discuss steps, decisions, responsibilities and handovers. Start with a SIPOC or a short end-to-end overview when the scope and boundaries need agreement first.

Use plain-language activity names, a small consistent symbol set and an explained legend. A simplified flowchart is useful in its own right; label its notation clearly rather than implying it is a complete BPMN model.

Explore process and swimlane mapping →

One process, linked levels of detail

  1. Orient: use an APQC-informed process inventory or an agreed local framework to identify the area, scope, owner and measures.
  2. Discuss: walk through an accessible business map with the people doing the work. Confirm the trigger, outcome, decisions, handovers, delays and important exceptions.
  3. Specify: add detailed BPMN, decision tables or interface views where development, controls or automation require precision.
  4. Keep aligned: retain common process and step IDs, owners and versions across the views. Link requirements, functional specifications, RACI responsibilities and test scenarios; review changes with affected users.

A business-level Customer Promise Protection view

Illustrative discussion summary, not a complete BPMN diagram:

  1. Recognise the delivery risk
  2. Check stock and supply
  3. Agree an authorised response
  4. Confirm and monitor the promise

The business workshop checks that this describes the work. Linked detail then explains missing data, approval limits, unavailable stock and the outcomes to test.

We would agree the presentation with the audience rather than require every user to read the most technical model. Retain the detail needed for the decision, without losing the connection to the validated business process.

Sources reviewed 17 October 2026: APQC: process frameworks and process maps ↗; OMG: BPMN ↗. The selection approach, linked views and example above are SCP proposals. APQC content is referenced here rather than reproduced as a client-specific process catalogue.

Process mapping or process mining?

Workshops and observation explain the work as people understand it. Process mining examines event records to reveal recorded paths, timing and variation. Use them together where suitable data exists, checking that system events represent the operating reality.

Read our process mapping and process mining article →

Techniques in this guide

Open a technique for when to use it, its output and related service links.

Define

SIPOC, including constraints and measures

Where does the process start and end?

Explore this technique

What it produces

Scope and interfaces.

Supply-chain example

Set the boundary from supplier confirmation to customer receipt and name the owners.

Related services

Method reference for SIPOC, including constraints and measures (opens in a new tab) ↗
Understand

Process mapping and swimlane mapping

Where do handovers, decisions or rework occur?

Explore this technique
Understand

Value-stream mapping

Where does elapsed time accumulate across material and information flows?

Explore this technique

What it produces

Current/future-state maps.

Supply-chain example

Separate working time from waiting across replenishment and fulfilment.

Related services

Method reference for Value-stream mapping (opens in a new tab) ↗
Understand

Gemba observation

Does the documented process match actual work?

Explore this technique

What it produces

Observation record.

Supply-chain example

Observe picking, replenishment or exception handling with the people doing the work.

Related services

Method reference for Gemba observation (opens in a new tab) ↗
Understand

Check sheets and a data-collection plan

Can teams record incidents consistently?

Explore this technique

What it produces

Defined event log.

Supply-chain example

Record comparable delivery failures or stock discrepancies before ranking causes.

Related services

Method reference for Check sheets and a data-collection plan (opens in a new tab) ↗
Understand

Spaghetti diagrams

Where is avoidable travel or handling?

Explore this technique

What it produces

Movement map.

Supply-chain example

Map avoidable movement between storage, workstations, docks and dispatch.

Related services

Method reference for Spaghetti diagrams (opens in a new tab) ↗
Define

SCOR-informed process and metric alignment

Are functions using compatible process and performance definitions?

Explore this technique

What it produces

Shared scorecard.

Supply-chain example

Align process and performance definitions across functions before comparing results.

Related services

Method reference for SCOR-informed process and metric alignment (opens in a new tab) ↗
Understand

Business Process Model and Notation (BPMN)

When a workflow needs precise events, decisions, exceptions and interactions, with views suited to the audience.

Explore this technique

What it produces

A process model with agreed notation, detail, ownership and links to requirements and tests.

Supply-chain example

Use a simple business view of a shortage response, with linked BPMN detail for exception and approval behaviour.

Choose the framework, notation and level of detail →

Related services

Method reference for Business Process Model and Notation (BPMN) ↗
Define

APQC Process Classification Framework (PCF)

When the organisation needs common process names, coverage and ownership before mapping detailed workflows.

Explore this technique

What it produces

A tailored process inventory or architecture mapped to the relevant reference categories and local owners.

Supply-chain example

Check the coverage of related planning and delivery processes, then map their actual cross-team handovers.

Choose the framework, notation and level of detail →

Related services

Method reference for APQC Process Classification Framework (PCF) ↗

Discuss the decision you need to improve

Explore how these techniques could support your operation, with the scope and depth agreed around your needs.