6.2 Process Analysis Tools and Value Stream Mapping
Key Takeaways
- Takt time establishes the mandatory pace of production required to match customer demand and is computed as Takt = Net Available Operating Time / Customer Demand Quantity.
- Value-Stream Mapping (VSM) visualizes both information and material flows across an end-to-end process, distinguishing between Value-Added (VA), Non-Value-Added (NVA / Waste), and Necessary Non-Value-Added (NNVA) activities.
- Process Lead Time represents the total elapsed clock time from process initiation to final delivery, whereas Cycle Time is the elapsed time required to complete one unit at an individual operational step.
- Process Cycle Efficiency (PCE) measures lean process health as PCE = (Total Value-Added Time / Total Process Lead Time) * 100%, where lean world-class operations target PCE > 25% compared to traditional processes operating below 5%.
In the Measure phase of Six Sigma DMAIC (Define-Measure-Analyze-Improve-Control), process flow analysis and Value Stream Mapping (VSM) serve as foundational techniques for establishing operational baselines. Before a Black Belt can quantify variation or process capability, the team must thoroughly map how work, materials, and information physically flow through the system. Value Stream Mapping expands traditional process flowcharting by capturing systemic relationships, inventory build-ups, information signals, and detailed time metrics across the end-to-end value chain.
Value Stream Mapping Architecture & Icons
A Value Stream encompasses all actions—both value-added and non-value-added—required to transform raw materials or initial customer requests into finished goods or completed services. Unlike standard high-level SIPOC (Suppliers, Inputs, Process, Outputs, Customers) diagrams or deployment (swimlane) flowcharts, a Value Stream Map explicitly couples material flow (moving from left to right across the lower half) with information flow (moving from right to left across the upper half).
Standard VSM Symbol Categories
- Process Boxes: Represent individual operational work centers where transformation or handling occurs. Each box contains a dedicated Data Box recording empirical process parameters.
- Data Boxes: Contain quantitative metrics collected during Gemba walks: Cycle Time ($C/T$), Changeover Time ($C/O$), Uptime (Machine Availability %), Work-in-Process (WIP) inventory, batch sizes, number of operators, and available shift time.
- Inventory Triangles: Represent material queues, storage buffers, or staging areas between process steps, labeled with the exact quantity of inventory ($I$).
- Information Flow Lines: Depict manual information flows (straight thin arrows) or electronic data transfers (zigzag lightning arrows) such as ERP/MRP scheduling, production control orders, and Kanban signals.
- Timeline Ladder: Positioned at the bottom of the map, contrasting Value-Added Processing Time (on the lower step) against Non-Value-Added Inventory Lead Time (on the upper step).
Process Time Definitions & Mathematical Formulations
Precise statistical definition of time metrics is critical for Lean Six Sigma Practitioners to quantify waste and establish production cadence:
1. Takt Time
Derived from the German word Taktzeit (meter or beat), Takt Time is the maximum allowable time per unit of product or service required to meet customer demand. It is not the time it takes to build a product, but rather the required pace of production.
Where:
- Net Available Operating Time = Total gross shift time minus planned downtime (rest breaks, meal times, shift handover, planned maintenance, and scheduled team meetings).
- Customer Demand Quantity = Total units required by the customer over the identical operating period.
Example Calculation: A manufacturing cell operates on a single 8-hour (480-minute) shift per day. Planned downtime includes two 15-minute rest breaks and a 30-minute lunch break. Daily customer demand is 420 units.
- Net Available Time = $480\text{ min} - (15 + 15 + 30)\text{ min} = 420\text{ minutes} = 25,200\text{ seconds}$.
- Takt Time = $\frac{25,200\text{ seconds}}{420\text{ units}} = 60.0\text{ seconds/unit}$. The production cell must produce exactly one conforming unit every 60 seconds to satisfy customer demand without creating overproduction waste.
2. Cycle Time ($C/T$)
Cycle Time is the actual measured time elapsed between the completion of consecutive units at a specific process step. It measures the operational speed of a process step.
- Value-Added Cycle Time ($VA C/T$): The portion of cycle time dedicated to physically transforming the part.
- Machine Cycle Time: The time required for automated equipment to complete its processing cycle.
- Operator Cycle Time: The hands-on work time required by an operator to load, unload, inspect, and run a process step.
3. Lead Time ($L/T$) & Little's Law
Process Lead Time (or Throughput Time) is the total calendar or clock time elapsed from the moment an order or part enters the process stream until it is fully completed and delivered. Inventory stored between process steps directly inflates Lead Time. Utilizing Little's Law, inventory quantities are converted into equivalent lead time:
4. Process Cycle Efficiency (PCE)
Process Cycle Efficiency measures the proportion of total lead time that is genuinely spent adding value for the customer:
In traditional non-lean processes, PCE is frequently below $5%$, meaning that over $95%$ of process lead time consists of waiting, storage, and queue delays. Lean world-class benchmark operations achieve a PCE greater than $25%$.
Categorization of Process Activities
Six Sigma practice categorizes every process task into one of three distinct operational buckets to eliminate waste and optimize flow:
| Activity Category | Operational Definition | Three Screening Criteria | Strategic Action |
|---|---|---|---|
| Value-Added (VA) | Tasks that directly transform the product or service into a state the customer desires. | 1. The customer is willing to pay for the activity.<br>2. The activity physically transforms the item.<br>3. The activity is performed correctly the first time. | Optimize & Standardize (Minimize variation) |
| Necessary Non-Value-Added (NNVA) | Tasks that add no direct customer value but are required by current regulations, laws, safety standards, or technological limitations. | 1. Customer will not pay for it.<br>2. No physical transformation occurs.<br>3. Required by external compliance or current technology. | Minimize & Streamline (Reduce duration and labor overhead) |
| Non-Value-Added (NVA / Waste) | Tasks that consume time, space, or resources without adding customer value or satisfying regulatory requirements. | 1. Customer is unwilling to pay.<br>2. No transformation occurs.<br>3. Can be eliminated without impacting product compliance. | Eliminate Completely (Identify root cause and remove) |
The 8 Wastes of Lean (TIMWOODS)
- Transportation: Excessive movement of materials, parts, or documents between locations.
- Inventory: Excess raw materials, WIP, or finished goods exceeding immediate operational requirements.
- Motion: Unnecessary physical movement of personnel (searching, bending, stretching, walking).
- Waiting: Idle time spent waiting for materials, approvals, machine cycles, or upstream work.
- Overproduction: Producing items faster, earlier, or in greater quantities than required by customer Takt time (the worst form of waste).
- Overprocessing: Performing redundant, overly precise, or unnecessary process steps beyond customer specification.
- Defects: Rework, scrap, inspection overhead, and corrective efforts caused by non-conforming work.
- Skills / Talent Underutilization: Failing to engage employees' problem-solving capabilities, intelligence, and creative ideas.
Selecting Among the Process Analysis Tools
Body of Knowledge topic V.A.2 asks Black Belts to select, use, and evaluate process analysis tools at the Evaluate level, naming value stream maps, process maps, work instructions, flowcharts, spaghetti diagrams, and the gemba walk. Value stream mapping is treated above; the point of this topic is choosing the right instrument for the question being asked.
| Tool | What it shows | Best question to answer | Blind spot |
|---|---|---|---|
| Value stream map | Material and information flow, with process time, wait time, and inventory between steps | Where does the lead time actually go? | Too coarse to expose within-step method variation |
| Process map / flowchart | Sequence of activities, decisions, and rework loops | What are the steps, and where does work loop back? | No time or distance information |
| Swimlane (deployment) map | The same flow with responsibility by function or role | Where are the handoffs, and who owns each step? | Can hide physical movement |
| Spaghetti diagram | The physical path a person, part, or document travels, drawn on a layout | How much motion and transportation does the layout force? | Says nothing about decision logic or quality |
| Work instruction | Exactly how one task is performed | Is the documented method the method actually used? | Describes the intended process, not the real one |
| Gemba walk | Direct observation of the process as it runs | What actually happens, including the undocumented workarounds? | Observer effect; one walk is one sample |
Spaghetti diagrams
A spaghetti diagram is drawn on a scale layout of the work area. Follow one operator, one part, or one document through a full cycle and draw a continuous line along the actual path taken. The result makes motion and transportation waste immediately visible, and it quantifies them: measure the total path length, multiply by the number of cycles per shift, and the walking becomes minutes of paid time.
A worked figure of the kind these produce: an operator whose path measures 132 metres per cycle, running 34 cycles per shift, walks 4.5 km per shift. At a normal walking pace that is roughly 55 minutes of paid time per shift spent moving rather than working -- a business case that a process map alone would never surface.
Spaghetti diagrams are the natural precursor to a cell redesign, a 5S event, or a point-of-use material relocation, and re-drawing the diagram after the change is the simplest possible before-and-after proof.
Comparing the documented process with the real one
The most valuable analysis in this topic is the comparison between the work instruction and the gemba observation. Three outcomes, each with a different action:
| Finding | Interpretation | Action |
|---|---|---|
| Documented and observed methods match | The standard is real | Improve the standard itself |
| Observed method is better than documented | Operators have improved it informally | Capture and standardize the better method |
| Observed method is worse, or varies by operator | The standard is impractical, unclear, or untrained | Fix the standard and the training, then re-observe |
Skipping this comparison is how teams end up modelling and improving a process that exists only on paper. Walk the process before mapping it, and map what you saw rather than what you were told.
Conducting a gemba walk
Go to the actual place, look at the actual process, and talk to the people doing the work. Practical discipline: observe a full cycle without interrupting, then ask questions; ask what happens when something goes wrong rather than whether problems occur; follow one unit end to end rather than watching one station; and observe on more than one shift, because shift-to-shift differences are frequently the largest source of variation in the whole study.
A healthcare clinic operates an urgent care department for 10 hours daily. Planned operational downtime includes two 15-minute staff huddles and one 30-minute meal break per shift. If patient demand averages 180 patients per day, what is the precise Takt time required for patient processing?
Which of the following activities performed in a chemical processing plant qualifies strictly as Value-Added (VA)?
A transactional process has a total measured process lead time of 15.0 days across all queues and handoffs. Quantitative time observation shows that actual value-added processing time totals 3.6 hours across all work steps. Assuming an 8-hour working day, what is the Process Cycle Efficiency (PCE)?