A number on a dashboard means little without something to compare it against. Yasmin, the sourcing agent at Meridian Sourcing who represents Order B (jeans)'s buyer, checks Delta Garments' real-time output on the jeans line, but a raw output number alone cannot tell her whether an operation is stalled or simply slower by nature than the operation next to it. This lesson teaches how to compare real-time output against each operation's own target pace, calculated from its own standard minute value (SMV), rather than against another operation's different pace.
Without this comparison, a reader can mistake a naturally slower operation for a stalled one, or miss a real stall on a naturally fast operation because its output still looks larger in absolute terms than a slower operation's normal pace. Order B (jeans) mixes a confirmed line with a forecast repeat line, and both need the same fair comparison against their own target pace, not against each other's raw numbers.
You need: lesson 26.1.3's stalled line (a line whose output curve shows a flat stretch) is useful background but not required.
By the end of this lesson you can:
Not covered here: reading a multi-line dashboard in general (lesson 26.1.3), recording a single output entry (lesson 26.1.2), and building a complete tracker combining every skill in this course (lesson 26.1.5).
| Term | Meaning |
|---|---|
| Target pace | The output rate, in pieces or bundles per hour, an operation should achieve, calculated from its own standard minute value (SMV). |
| Pace gap | The difference between an operation's actual real-time output and its own target pace over the same period. |
| Standard minute value (SMV) | The standard time, in minutes, a trained operator needs to complete one operation on one piece, used to calculate a line's expected output and workload. |
| Hybrid order | One style produced under two business models at once, usually one confirmed order line and one forecast order line. |
| Stalled line | A line whose output has stopped, or fallen well below its usual pace, for longer than a normal short stop explains. |
Every operation on a line has its own standard minute value, and therefore its own target pace, which can differ sharply from the operation next to it. Comparing waistband attach's raw output directly against pocket set's raw output tells a reader nothing useful if the two operations have different SMVs; the only fair comparison is each operation's own real-time output against its own target pace, expressed as a pace gap.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| Operation complexity | A simple operation like waistband attach with a lower SMV, or a more complex one like pocket set with a higher SMV. | A higher-SMV operation has a naturally lower target pace; a lower absolute output number there is not automatically a stall. |
| Business model | Order B (jeans)'s confirmed line has one fixed shipment date pressing on every pace gap. Its forecast repeat line, part of the same hybrid order, has more schedule flexibility, but a growing pace gap still represents real lost time. | The urgency of acting on a pace gap differs between the confirmed and forecast lines, even when the gap itself is the same size. |
| How target pace is set | A target pace calculated purely from SMV, or one adjusted for a known factor like a new operator still on the learning curve. | An unadjusted target pace can make a genuinely normal ramp-up look like a stall if the comparison ignores it. |
| Number of operations tracked | A short sequence like Order A's T-shirt, or a longer sequence like Order B's jeans with washing and finishing added. | More operations, each with its own target pace, mean more pace gaps to compare before deciding where to act first. |
| How pace gap is measured | A pace gap measured over the last hour, or over the whole shift so far. | A short measurement window catches a stall faster; a whole-shift window can hide a recent stall inside an otherwise good daily average. |
On Order B (jeans)'s confirmed line, Yasmin checks real-time output for two operations. Waistband attach has completed 18 bundles in the last hour; pocket set has completed 12 bundles in the same hour. Read as raw numbers, pocket set looks like the weaker operation. But waistband attach's own target pace is 20 bundles per hour, while pocket set's own target pace, based on its higher SMV, is only 12 bundles per hour.
Once each operation is compared against its own target pace, waistband attach is actually 2 bundles behind its own target, while pocket set has exactly met its own target. The raw numbers alone would have pointed Yasmin toward the wrong operation entirely.
The worked numberWaistband attach, despite producing more bundles in absolute terms, is the operation genuinely behind its own target, while pocket set, despite producing fewer bundles, is exactly on pace. Both target pace figures are Delta Garments' own illustrative examples built for Order B (jeans)'s operations; the comparison shows why a pace gap, not a raw output count, is the number that actually matters.
A common mistake is comparing two operations' absolute output counts side by side and assuming the lower number marks the weaker operation. As Order B (jeans)'s waistband attach and pocket set show, an operation with a naturally lower target pace can produce fewer pieces while still being exactly on pace, while an operation with a higher target pace can produce more pieces while genuinely falling behind its own target. This mistake is easy to make precisely because a dashboard often lists raw output counts prominently, with target pace shown as a smaller, secondary figure a reader can skip past without a deliberate habit of checking it every time.
The cost of this mistake is not that the wrong operation gets no attention at all, but that limited management time gets spent reassuring a team about an operation that is actually fine, while the operation genuinely falling behind continues to lose ground unnoticed. On a hybrid order like Order B (jeans), where a confirmed line and a forecast repeat line share the same operations, this mistake can repeat itself on both lines at once if the habit of comparing against target pace, rather than raw output, is never established.
Two different jobs on the same line can have very different normal speeds, so comparing their raw output numbers side by side tells you nothing useful on its own. What actually matters is how far each job's own output sits from what that same job should normally produce in the same time. A job producing fewer pieces can still be exactly on pace, while a job producing more pieces can genuinely be falling behind, once each is measured against its own proper target rather than against the other.
An hour later, Yasmin checks again. Waistband attach has now completed 19 bundles against its 20-bundle target pace; pocket set has completed 10 bundles against its 12-bundle target pace.
Should Yasmin report waistband attach as the priority, since it produces more bundles in absolute terms, or pocket set, since its own pace gap is larger? Decide before opening the answer.
Yasmin should report pocket set as the priority concern, since its own pace gap of 2 bundles is larger than waistband attach's 1 bundle, regardless of which operation produces more in absolute terms.
1. Pocket set's pace gap doubled compared with waistband attach's, meaning it is falling further behind its own target, not just producing a smaller raw number. 2. Absolute output does not indicate urgency; waistband attach's higher raw count of 19 bundles does not matter if its own gap against target is smaller than pocket set's. 3. Naming the operation with the larger pace gap directs the buyer's attention to the genuinely worse trend, rather than to whichever operation simply looks busier on paper.
Yasmin does not need every operation's gap to reach zero before reporting; comparing the two gaps directly, not the raw counts, is what correctly ranks pocket set as today's larger concern.
Order B (jeans)'s own timeline allows 3 weeks for sewing within its 22-week schedule (docs/02 section 7). A 2-bundle pace gap on pocket set, if it persisted for the rest of the confirmed line's sewing days, would accumulate into a meaningful share of the sewing window's own limited slack.
The 16-bundle figure is Delta Garments' own illustrative example of what an unaddressed, consistent pace gap would total across a single day; it is not a fixed cost, since pace gaps vary hour to hour, but it shows why tracking the gap by operation, not just glancing at daily totals, catches a worsening trend before it consumes real days of Order B (jeans)'s own 3-week sewing window.
Open the real-time production tracking tracker, "Target pace comparison" sheet. Enter each operation's own SMV and shift length; the sheet calculates target pace automatically, then compares it against the real-time output you log to show each operation's own pace gap. Start with waistband attach and pocket set's figures above, then compare operations of your own.
[Download the real-time production tracking tracker workbook](../../templates/T26-C01-real-time-production-tracking-tracker.xlsx)
1. Why can't two operations be fairly compared by their raw output counts alone?
2. Waistband attach produced 18 bundles against a 20-bundle target, and pocket set produced 12 bundles against a 12-bundle target, in the same hour. Which operation is genuinely behind?
3. An hour later, waistband attach's pace gap is 1 bundle and pocket set's pace gap is 2 bundles. Which should Yasmin report as the priority concern?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Target pace | الوتيرة المستهدفة | Cadence cible | Hedef tempo | The output rate, in pieces or bundles per hour, an operation should achieve, calculated from its own standard minute value (SMV). |
| Pace gap | فجوة الوتيرة | Écart de cadence | Tempo farkı | The difference between an operation's actual real-time output and its own target pace over the same period. |
| Standard minute value (SMV) | قيمة الدقيقة المعيارية (SMV) | Valeur minute standard (SMV) | Standart dakika değeri (SMV) | The standard time, in minutes, a trained operator needs to complete one operation on one piece, used to calculate a line's expected output and workload. |
| Hybrid order | طلبية مختلطة | Commande hybride | Hibrit sipariş | One style produced under two business models at once, usually one confirmed order line and one forecast order line. |
| Stalled line | خط متوقف | Ligne à l'arrêt | Duran hat | A line whose output has stopped, or fallen well below its usual pace, for longer than a normal short stop explains. |
Next you will bring together everything this course has taught into one complete real-time production tracking tracker, covering output entries, dashboards and target pace comparisons in a single tool. Back to the course map