Data Boxes Explained: Cycle Time, Changeover Time, Uptime, and Shifts

Learning Objectives

By the end of this lesson, you will be able to:

• Define the purpose and function of a Data Box in a Value Stream Map
• Identify and explain the four core metrics captured in a Data Box: Cycle Time, Changeover Time, Uptime, and Shifts
• Correctly read and interpret Data Box information on a current-state map
• Understand how Data Box metrics connect to lead time analysis and waste identification

Imagine you are walking the floor of a manufacturing plant with a clipboard and a stopwatch. You stop at a welding station. The operator is working steadily, but you notice the machine sits idle every two hours while tooling is swapped out. Further down the line, an assembly cell runs only one shift, while the stamping press before it runs three. Somewhere in that gap — between what you see and what you can measure — is where waste hides. This is exactly the problem that the Data Box in Value Stream Mapping was designed to solve. Without a standardised way to capture process performance data directly on the map, your VSM becomes little more than a diagram of boxes and arrows. Data Boxes transform it into a diagnostic tool.

What Is a Data Box and Where Does It Appear?

In VSM notation, a Data Box is a rectangular information panel placed directly beneath each process step icon on the map. Its role is to capture the quantitative performance data that describes how that process actually operates — not how it was designed to operate, and not how managers hope it operates, but how it performs in reality today. This distinction is critical. The current-state map is a factual document, and the Data Box is where that factual data lives.

As shown in standard Kaizen Institute VSM materials, a typical Data Box beneath an “Assembly” process might read:

C/T: 45 sec — C/O: 800 sec — 3 Shifts — Scrap: 2%

Each of these entries is a specific metric with a specific meaning. Together they give you an accurate picture of process capacity, stability, and efficiency. Let’s examine each one in detail.

Cycle Time (C/T)

Cycle Time is the time elapsed between one unit completing a process step and the next unit completing the same step. In practical terms, it is the rhythm of the process — how frequently a finished piece exits the workstation. Cycle Time is measured in seconds and is observed directly on the shop floor. It is not a theoretical calculation from an engineering standard; it is a real observation.

Cycle Time plays a central role in VSM analysis because it is compared directly against Takt Time — the rate at which customers demand products. If a process has a Cycle Time greater than Takt Time, that process is the bottleneck. If it is significantly lower than Takt Time, there may be overproduction occurring. Either condition signals waste that needs to be addressed in the future-state design.

Changeover Time (C/O)

Changeover Time is the elapsed time from the last good piece of one product type to the first good piece of the next product type. This is the complete SMED definition — it includes internal changeover activities, adjustments, trial runs, and first-article inspection. Changeover Time is recorded in seconds on the Data Box.

Long Changeover Times create pressure to run large batches. Large batches create inventory. Inventory creates lead time. This chain of cause and effect is one of the most important dynamics that VSM reveals. When you see a Data Box showing C/O: 7,200 sec (as in the Ferrero Russia example from Kaizen Institute reference materials), you are looking at a two-hour changeover that is almost certainly driving significant overproduction waste upstream and downstream. The Data Box makes this visible at a glance, setting the stage for a SMED kaizen event in the future state.

Uptime (or OEE / TRS)

Uptime — sometimes expressed as OEE (Overall Equipment Effectiveness) or its French equivalent TRS (Taux de Rendement Synthétique) — measures the percentage of scheduled production time during which the machine or process is actually producing good parts. It is expressed as a percentage and accounts for availability losses (breakdowns, changeovers), performance losses (speed reduction, minor stoppages), and quality losses (scrap, rework).

Uptime is one of the most revealing figures on the Data Box. A process running at 55% uptime is effectively available for only slightly more than half the time it is scheduled to run. When you calculate capacity for that process, you must account for this reality. Processes with low uptime are typically unreliable, forcing upstream processes to build buffer stock and downstream processes to wait. The Data Box makes this instability quantifiable and visible to the entire improvement team.

Number of Shifts

The Shifts entry records how many production shifts the process operates per day. This is expressed as a simple number: 1 shift, 2 shifts, or 3 shifts. It appears simple, but it carries important implications for capacity analysis. A process running 1 shift has significantly less available time than a process running 3 shifts. When two adjacent processes run different numbers of shifts, the VSM team must investigate why. Is one process intentionally limited because of low demand? Or is it running fewer shifts because management believes it has enough capacity, when in fact it is the hidden bottleneck?

Shift information is also essential for calculating Available Production Time, which feeds directly into the Takt Time formula: Available Time ÷ Customer Demand = Takt Time. Without knowing how many shifts a process runs, you cannot accurately assess whether it can meet customer requirements.

Practical Example: Apex Automotive Seating

Consider Apex Automotive Seating, a fictitious Tier 2 supplier producing seat frames for an automotive OEM. During their first VSM exercise, the team walked the line and populated Data Boxes for each process step. The stamping press showed: C/T: 5 sec — C/O: 7,200 sec — 3 Shifts — Uptime: 55%. The welding station showed: C/T: 30 sec — C/O: 300 sec — 2 Shifts — Uptime: 78%. The final assembly cell showed: C/T: 50 sec — C/O: 0 sec — 1 Shift — Uptime: 90%.

Before the VSM exercise, the plant manager believed the stamping press was the high-performing workhorse of the line — it ran three shifts and had an extremely fast Cycle Time. But the Data Boxes told a different story. The 7,200-second changeover on the press was forcing the team to run massive batches, creating days of inventory between stamping and welding. The 55% uptime meant the press was actually unavailable nearly half the time, despite running three shifts. Meanwhile, the final assembly cell — running only one shift — had a Cycle Time of 50 seconds against a Takt Time of 45 seconds, making it the true bottleneck.

None of this was visible until the Data Boxes were filled in. The team used these insights to prioritise a SMED event on the press, a TPM programme to improve uptime, and an evaluation of extending assembly to two shifts. The Data Boxes were the foundation of every decision.

Key Takeaways

• Data Boxes are fact-based: They capture real, observed process performance — not targets, standards, or assumptions. Always measure directly on the floor.
• Cycle Time drives bottleneck analysis: Comparing C/T across all process steps and against Takt Time immediately reveals where flow is being constrained.
• Changeover Time drives batch size decisions: High C/O times are a root cause of large batches, excess inventory, and extended lead times — and a primary target for kaizen.
• Uptime reveals hidden capacity loss: A process with low uptime is an