7.1 Process Flowcharts & SIPOC Diagrams

7.1 Process Flowcharts & SIPOC Diagrams

Process visualization is the critical first step in any quality improvement initiative. Before a team can measure, analyze, or improve an operational workflow, they must establish an unambiguous, shared mental model of how work actually flows through the organization. On the ASQ Certified Quality Improvement Associate (CQIA) examination, candidates must demonstrate complete proficiency with standard ANSI/ISO flowchart symbols, deployment (swimlane) flowcharts, macroscopic SIPOC (Supplier, Input, Process, Output, Customer) diagrams, and high-level Value Stream Mapping (VSM) concepts.

---

1. Overview of Process Mapping in Quality Improvement

In quality engineering, a process is defined as a set of interrelated or interacting activities that transforms inputs into outputs. Quality pioneer Kaoru Ishikawa noted that unmapped processes foster operational blind spots, redundant tasks, and conflicting assumptions among workers. Process mapping serves three distinct organizational purposes:

1. Baseline Current State Documentation: Capturing the process as it actually exists (the "as-is" state), which frequently differs from formal operating procedures or managerial assumptions.
2. Waste and Friction Identification: Pinpointing unnecessary handoffs, rework loops, inspection bottlenecks, approval delays, and information gaps.
3. Future State Design: Engineering an optimized, streamlined workflow (the "to-be" state) with standardized controls and mistake-proofing.

---

2. Standard Flowchart Symbols & ANSI/ISO Conventions

To ensure universal interpretability across engineering, manufacturing, healthcare, and service industries, standard flowcharting adheres to conventions codified by the American National Standards Institute (ANSI) and the International Organization for Standardization (ISO).

+-------------------------------------------------------------------------+
|                   STANDARD ANSI / ISO FLOWCHART SYMBOLS                 |
+-------------------------------------------------------------------------+
|                                                                         |
|     (  START / END  )             [  PROCESS STEP  ]                    |
|         Terminator                       Activity                       |
|      (Oval / Pill)                     (Rectangle)                      |
|                                                                         |
|          ◇ DECISION                        ( C )                        |
|       < Evaluate Rule > ──[ No ]──►      Connector                      |
|             │                          (Small Circle)                   |
|             ▼ [ Yes ]                                                   |
|                                                                         |
|        /  INPUT / DATA  /              [ DOCUMENT / REPORT ]            |
|       /________________/               [ (Printed / Digital) ]          |
|                                                                         |
+-------------------------------------------------------------------------+

Comprehensive Flowchart Symbol Reference

Rules for Constructing Robust Flowcharts

• Consistent Directionality: Flow should proceed logically from top-to-bottom and left-to-right.
• Exhaustive Decision Outputs: Every diamond decision symbol must have all outgoing paths explicitly labeled (e.g., "Yes" and "No"). A decision box must never have a single exit line.
• Closed Feedback Loops: Rework loops exiting a decision diamond must re-enter the upstream process flow at an exact operational step, never at another decision diamond.

---

3. Types of Flowcharts: Linear vs. Deployment (Swimlane)

Different organizational challenges require different process mapping formats. The two most common formats evaluated on the CQIA exam are standard linear flowcharts and cross-functional deployment flowcharts.

Linear Flowcharts

A Linear Flowchart sequences activities in a single chronological stream. It is ideal for documenting a technical procedure within a single work center or workstation where handoffs across departments are minimal.

Cross-Functional Deployment (Swimlane) Flowcharts

A Deployment Flowchart (commonly known as a Swimlane Flowchart or Matrix Flowchart) categorizes process steps by mapping them across parallel horizontal or vertical lanes. Each lane represents a specific functional department, role, team, or automated IT system.

+-------------------------------------------------------------------------+
|             CROSS-FUNCTIONAL DEPLOYMENT (SWIMLANE) FLOWCHART            |
+-------------------------------------------------------------------------+
| CUSTOMER   |  ( Start: Place Order )                                    |
|            |           │                                                |
+────────────┼───────────┼────────────────────────────────────────────────+
| SALES /    |           ▼                                                |
| CS         |    [ Receive & Enter ] ──► < Credit OK? > ──[ No ]──►( End )|
|            |         Order                      │                       |
+────────────┼────────────────────────────────────┼───────────────────────+
| PRODUCTION |                                    │ [ Yes ]               |
| / ASSEMBLY |                                    ▼                       |
|            |                            [ Assemble Unit ]               |
|            |                                    │                       |
+────────────┼────────────────────────────────────┼───────────────────────+
| QUALITY    |                                    ▼                       |
| CONTROL    |                            < QC Inspection > ──[ Fail ]──┐ |
|            |                                    │                     │ |
+────────────┼────────────────────────────────────┼─────────────────────┼─+
| LOGISTICS  |                                    │ [ Pass ]            ▼ |
| / SHIPPING |                                    ▼                 [ Rework ]
|            |                            [ Pack & Ship ] ──► ( End )     |
+-------------------------------------------------------------------------+

Operational Advantages of Swimlane Flowcharts

1. Exposing Departmental Handoffs: Most quality defects, miscommunications, and queue delays occur precisely at the boundaries where work is handed from one functional silo to another.
2. Clarifying Accountability: Eliminates ambiguity over who owns a specific operational decision or task.
3. Isolating Rework Loops: Visually illustrates the organizational cost of scrap and rework when a downstream quality gate rejects work back across three preceding departmental lanes.

---

4. The SIPOC Diagram Framework

A SIPOC (pronounced SIGH-pock) is a macroscopic, high-level process mapping tool utilized primarily during the Define phase of Six Sigma DMAIC and Lean continuous improvement projects. It establishes the high-level boundary conditions of a process before the team becomes entangled in micro-level operational details.

+-------------------------------------------------------------------------+
|                          THE SIPOC ARCHITECTURE                         |
+-------------------------------------------------------------------------+
|                                                                         |
|   [ S ]         [ I ]           [ P ]           [ O ]         [ C ]     |
|  SUPPLIERS ──► INPUTS   ──►   PROCESS   ──►   OUTPUTS   ──► CUSTOMERS   |
|                                                                         |
|  Who provides  What materials What 4-7 high   What finished  Who receives
|  the raw       or data are    level steps     goods/services the output
|  inputs?       required?      transform inputs? are created?  and sets CTQ?
|                                                                         |
+-------------------------------------------------------------------------+

The 5 Elements of SIPOC

• S — Suppliers: The internal or external entities that provide materials, data, forms, components, or services into the process (e.g., Raw material vendor, Customer service, IT database).
• I — Inputs: The specific physical materials, equipment, specifications, software data, or documentation required to execute the process (e.g., Steel coils, CAD drawings, Patient health records).
• P — Process: The top-level sequence of core transformation activities. Standard CQIA best practice dictates that the Process column must contain only 4 to 7 high-level steps, articulated using active verb-noun phrases.
• O — Outputs: The tangible products, completed services, reports, or deliverables generated by the process (e.g., Assembled engine block, Cleared payment, Approved medical claim).
• C — Customers: The internal or external individuals, departments, or end-users who receive and evaluate the outputs (e.g., Downstream assembly plant, End-user consumer, Regulatory auditor).

Representative SIPOC: Clinical Diagnostic Blood Testing

Strategic Rules for SIPOC Construction

• Start with Process or Customer: Experienced facilitators often populate the Process (P) column first to establish boundaries, followed by Outputs (O) and Customers (C), before working backward to determine Inputs (I) and Suppliers (S) (sometimes called a COPIS approach to enforce customer-centric thinking).
• Defining Process Boundaries: Every SIPOC must establish explicit boundary triggers:
  • Start Trigger (Process Start): The precise event or input receipt that initiates step 1.
  • Stop Trigger (Process End): The exact deliverable handoff that marks completion.

---

5. High-Level Value Stream Mapping (VSM)

While a standard flowchart documents the sequence of tasks, a Value Stream Map (VSM) captures both the material flow (physical movement of goods) and the information flow (schedules, production control, electronic orders) across the entire end-to-end value stream.

+-------------------------------------------------------------------------+
|                    VALUE STREAM MAP TIMELINE LADDER                     |
+-------------------------------------------------------------------------+
|                                                                         |
|   [ Process 1 ]                  [ Process 2 ]          [ Process 3 ]   |
|   Cycle Time: 45s                Cycle Time: 60s        Cycle Time: 30s |
|          │                              │                      │        |
|   ═══════╪══════════════════════════════╪══════════════════════╪══════  |
|          │ 2 Days Inventory             │ 3 Days Inventory     │        |
|          └──────────────┐               └──────────────┐       │        |
|   TIMELINE:             ▼                              ▼       ▼        |
|   Waiting / Lead Time:  [ 2 Days ]                     [ 3 Days ]       |
|   Processing Time (VA):          [ 45 sec ]            [ 60 sec ] [30s] |
|                                                                         |
|   Total Lead Time (NVA + VA) = 5 Days + 135 Seconds                     |
|   Total Value-Added Processing Time = 135 Seconds                       |
+-------------------------------------------------------------------------+

Key Metrics in Value Stream Analysis

• Cycle Time ($CT$): The actual time elapsed from the start of an individual transformation task to its completion on a single unit.
• Value-Added Time ($VA$): Time spent performing work that directly transforms the product or service into something the customer is willing to pay for.
• Total Lead Time ($LT$): The total elapsed clock/calendar time required for a unit to travel from raw material receipt through all processing, queues, staging, and storage to final customer shipment.
• Process Cycle Efficiency ($PCE$): A quantitative Lean metric expressing the proportion of lead time dedicated to true value-added transformation:

$\text{Process Cycle Efficiency (PCE)} = \frac{\text{Total Value-Added Processing Time}}{\text{Total Lead Time}} \times 100\%$