Skip to content
GREEN FUTURETECH.
Explore

Research libraryMeasure Before You Model

Chapter 04 of 14 · Part I · Draft web edition

A metric is not a measurement until its error is understood

Operational definitions, data-quality controls and measurement-system analysis must precede target comparisons and automated analytics.

Sections
7
Exhibits
5
Minutes
25
Sources
9
EX 17 · Rejected: removes 45. Running total 855 illustrative pieces started

The cloth is woven from this chapter's 5 exhibits: each weft is one exhibit's own data, normalised; each warp group is a section. The probe reads the exhibit's own value where it crosses. Procedural visualisation, not a measurement.

The chapter as a draft: 7 sections, 4 exhibit wefts, one shuttle.

Lead exhibit · 17ReconciliationillustrativeA count reconciliation preserves unfinished and corrected work
02505007501,0001,000Pieces started-100Still in progress-45Rejected-90Accepted after rework765First-pass good

Read-outPieces started: total 1,000. Running total 1,000 illustrative pieces started

Method and source

Illustrative worked example, not factory evidence. Assumed starts are 1,000 pieces. Partition: 100 still in progress, 45 rejected, 90 accepted after rework and 765 first-pass good. Arithmetic: 1,000 - 100 - 45 - 90 = 765. Repaired pieces remain separately visible and are not first-pass good.

Unit: illustrative pieces started. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

The chapter's warpBar: share of the reading · square: an exhibit

Section 4.0 · Opening · 1 min · no exhibit of its own · one movement Go to section ↓

Overture · 1 min

A factory can calculate a precise percentage from records that do not mean what management thinks they mean. The remedy is a metric contract: a versioned definition of the decision, counting event, formula, unit, time basis, source record and owner, accompanied by evidence that the measurement process is fit for that decision. GFT recommends that no greenfield KPI receive a hard target, a worker consequence or an automated interpretation until those conditions are met. This is not a demand for perfect data. It is a requirement to know where error enters, how large it is relative to the decision, and what remains uncertain after checking.

¶ 01

This discipline separates three questions that dashboards often compress into one tile. What does the number mean? Can the records be trusted for the intended use? Does an observed change exceed the variation created by counting, inspection, timing or meter reading? The chapters on production, quality and management cadence can then use the resulting measures without repeatedly negotiating their meaning.

¶ 02

4.13 min · 9 paragraphs · 1 exhibit

The data dictionary begins with formula and unit

ISO 22400 presents manufacturing KPIs through their formulas, corresponding elements, time behaviour, units and other characteristics. That structure is the starting point because a familiar name such as output, availability or yield does not determine a calculation.[S01] A GFT metric contract turns the name into instructions that two people can apply independently to the same events and obtain reconcilable results.

The formula should use operational nouns rather than vague labels. First-pass good pieces divided by pieces reaching first completion is more useful than good divided by total, because both numerator and denominator now have a counting event. The unit should also survive scrutiny. Pieces, bundles, standard minutes and garments accepted at final inspection are not interchangeable. A ratio may be dimensionless, yet its numerator and denominator still require the same piece basis and process boundary.

¶ 02

Inclusion and exclusion rules finish what the formula starts. The contract states whether samples, training output, interrupted bundles, customer returns and subcontracted work enter the population. It identifies the operation or gate at which completion occurs. It says whether a repaired unit remains a first-pass failure after final acceptance. These are not rare technical exceptions. They are ordinary production events that can otherwise move a KPI without any change in the underlying work.

¶ 03

The time basis needs equal care. A shift total can mean scheduled attendance, planned production time or elapsed time between system timestamps. The contract therefore names the shift calendar, event-time zone, cut-off, late-arrival rule and permitted reporting latency. It also distinguishes event time from entry time. A record entered after the review may be valid for a weekly reconciliation but unavailable for the shift decision that already took place.

¶ 04

Rounding is a presentation rule, not a licence to alter source values. The contract preserves the unrounded numerator and denominator, states when rounding occurs and prevents rounded line ratios from being averaged into a plant ratio. The plant calculation sums compatible numerators and denominators first, then divides. If the populations are not compatible, the correct response is separate reporting rather than a weighted average whose meaning has been lost.

¶ 05

Ownership completes the definition. A business owner approves purpose and use. A data steward maintains validation and resolves record issues. A system custodian controls implementation. One person may hold more than one role in a small factory, but the accountabilities remain visible. Formal data governance supplies the decision rights and enforcement that an informal spreadsheet convention lacks.[S22]

¶ 06 · 1 source

S22

Exhibit 16 converts these requirements into a minimum contract. It is deliberately more extensive than a dashboard label because it must support capture, calculation, review and later migration.

Exhibit 16RegisterderivedThe metric contract makes independent calculations reconcilable
Contract group
Purpose
Required entries
Decision, user, owner, review forum
Failure prevented
A number without an action

Read-outContract group: Purpose. Required entries: Decision, user, owner, review forum. Failure prevented: A number without an action

Open the full register (9 rows)
PurposeDecision, user, owner, review forumA number without an action
PopulationBoundary, inclusions, exclusions, identityUnlike events counted together
CalculationFormula, numerator, denominator, unitRival formulas under one KPI name
TimeEvent, shift calendar, cut-off, latencyFalse comparison across periods
CaptureSource event, authoritative record, stewardUnowned transcription and correction
QualityCompleteness, validity, consistency, timeliness, uniqueness, accuracyClean appearance despite unfit records
MeasurementRepeatability, reproducibility, bias, resolution evidenceMeasurement error read as process change
PresentationPrecision, rounding, roll-up and suppression rulesFalse precision and unstable aggregation
ChangeVersion, approval, effective date, migration policyHistory silently rewritten
Method and source

Derived field structure. Formula, elements, time behaviour and unit follow S01. Ownership follows S22. Structured quality and fitness-for-use controls follow S23 and S24. No factory performance values are asserted.

Unit: required contract fields. Status: derived. Sources: S01, S22, S23, S24.

The table is a control surface, not administration for its own sake. A field should be removed only when it cannot affect a decision or reconciliation. Conversely, a visually simple KPI may need a substantial contract because its consequences are substantial. The effort belongs where misinterpretation could change staffing, pay, customer promises or investment.

¶ 01
Note

4.23 min · 9 paragraphs · 1 exhibit

Good output needs an unambiguous counting event

Related · chapter 019 paragraphs step it

Related exhibit 01 · chapter 01Stacked compositionillustrativeAccepted output can conceal the work needed to recover quality
820First-pass accepted120Recoveredby rewo…60Rejectedor pe…

Read-outFirst-pass accepted: 820 of 1,000 illustrative garments in a closed inspection cohort (82 percent)

Method and source

Assumed cohort: 1,000 distinct garments with recorded initial inspection outcomes. At cut-off, 820 first-pass accepted plus 120 accepted after rework plus 60 rejected or pending equals 1,000. Final accepted output is 940. Recovery counts garments, not correction events. Pending work is not assumed to be scrap.

Unit: illustrative garments in a closed inspection cohort. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗
4.2 · Introduction · paragraph 1 of 9

Output becomes measurable only when a unit crosses a defined boundary. At a sewing operation, the event may be a completed bundle accepted by the next operation. At end of line, it may be a garment passing inspection without correction. At dispatch, it may be a saleable garment released for shipment. Each event answers a different management question. Combining them produces an apparently convenient total that conceals work in progress, rework and rejection.

First-pass yield makes the distinction especially important. The NIST Manufacturing Extension Partnership case links a first-pass-yield improvement with reduced processing time, but its reported result belongs to that manufacturer's improvement case, not to a garment factory or a universal benchmark.[S10] The transferable lesson is methodological: units accepted only after repair consumed additional processing, so final acceptance cannot replace the first-pass measure.

OEE also retains quality as a component beside availability and performance. Its quality rate is based on processed good amount over processed amount in the formulation reviewed by Ádám and Sebestyén.[S06] That does not make every good-count definition interchangeable. A factory must state whether its production quality component accepts repaired pieces, while its separate first-pass KPI must continue to exclude them. The metric contract prevents a repaired unit from erasing the original loss merely because a later composite needs a final good count.

Five mutually useful records should therefore coexist: pieces started, pieces reaching first completion, first-pass good pieces, pieces entering correction and rejected pieces. Work in progress reconciles starts with completions. Corrected pieces need a disposition such as accepted after rework, still in correction or rejected. A piece count should not be inferred from bundle counts without a reliable pieces-per-bundle record and an exception rule for partial bundles.

The denominator follows the question. First-pass yield at an operation uses pieces reaching their first completion at that operation when management wants to understand the operation's ability to produce correctly. A start-to-date yield uses pieces started when management wants to include the effect of unfinished work. Neither is universally superior. They become misleading when the name remains yield while the denominator changes between lines or periods.

Exhibit 17 shows the same illustrative population as a partition. Every started piece appears once, so the flow can be checked before any ratio is calculated.

The reconciliation must also survive roll-up. Summing first-pass good pieces and completions across operations is valid only when each operation retains its own boundary and no piece is counted twice within the same KPI. A plant end-of-line yield should not be presented as the product of operation yields unless the routing, sampling and unit identity actually support that calculation. The safer daily control is to preserve operation-level counts and a separate end-of-line population, then investigate differences rather than force them into one formula.

Manual counts need practical controls at the point of work. The counter records the boundary, bundle identity where applicable, event time and any partial quantity. A supervisor resolves discrepancies against physical work before the shift closes. Corrections retain the original value, revised value, reason and author. Automation can later capture the same event, but a sensor does not settle the definition. It merely implements the counting rule it has been given.

4.33 min · 8 paragraphs · 1 exhibit

Structured records need explicit quality dimensions

Step 1 of 4Piece counts

Exhibit 18 · illustrativeA control map locates the hand-off that still needs evidence

CompleteValidConsistentTimelyUniqueAccuratePiece counts332321Defect records232321Attendance322132Meter reads231231
Compl…ValidConsi…TimelyUniqueAccur…Piece counts332321Defect records232321Attendance322132Meter reads231231

Piece counts

Piece counts: Complete 3, Valid 3, Consistent 2, Timely 3, Unique 2, Accurate 1 (illustrative control score from 0 to 3) · illustrative

A correct formula cannot rescue records that are missing, duplicated, late or detached from reality.

Defect records

Defect records: Complete 2, Valid 3, Consistent 2, Timely 3, Unique 2, Accurate 1 (illustrative control score from 0 to 3) · illustrative

Attendance

Attendance: Complete 3, Valid 2, Consistent 2, Timely 1, Unique 3, Accurate 2 (illustrative control score from 0 to 3) · illustrative

Meter reads

Meter reads: Complete 2, Valid 3, Consistent 1, Timely 2, Unique 3, Accurate 1 (illustrative control score from 0 to 3) · illustrative

Method and source · Exhibit 18

Illustrative deployment template, not an assessment of GFT or any factory. Score 0 means absent, 1 designed, 2 executed and 3 evidenced by a retained test result. Values are constructed to demonstrate how control coverage can be reviewed. Quality dimensions follow S24 within the structured-data concern framed by S23.

Unit: illustrative control score from 0 to 3. Status: illustrative. Sources: S23, S24. Illustrative figures are teaching examples, not measured factory results.

4.3 · the bodyExhibit 18 above; its figures are illustrative where marked.

A correct formula cannot rescue records that are missing, duplicated, late or detached from reality. ISO/IEC 25012 defines a general quality model for structured data retained in a computer system, which supports treating data quality as a defined evaluation problem rather than a general complaint about spreadsheets.[S23] The model does not make a manual sheet reliable by virtue of being typed into an application. The factory still has to specify intended use, checks and evidence.

The UK Government Data Quality Framework describes quality as fitness for purpose and sets out completeness, uniqueness, consistency, timeliness, validity and accuracy as core dimensions. It also warns that quality needs and trade-offs depend on the user.[S24] This matters on a garment floor. A line interruption record may need to be available immediately even if its cause is provisional, while a monthly cost reconciliation can wait for a complete and reviewed population. One service level should not be imposed on both.

¶ 02 · 1 source

S24

Each dimension needs an operational test. Completeness compares received records with an expected population, such as active lines, shifts or meters, rather than counting rows already present. Validity checks types, allowed codes and feasible ranges. Consistency tests whether related records contradict one another, such as completions exceeding starts without an explained opening balance. Timeliness measures the interval between event and availability for a named decision. Uniqueness detects repeated identities or duplicate events. Accuracy compares a sample with physical work, reference instruments or adjudicated evidence.

¶ 03

These tests belong at capture and again during roll-up. Capture controls prevent avoidable errors and return ambiguous entries to the person who can still inspect the work. Roll-up controls detect failures between systems, incompatible master data and calculations applied to the wrong population. A valid individual record can still produce an invalid plant KPI if the aggregation includes a closed line, repeats a corrected event or mixes different method revisions.

¶ 04

Accuracy deserves separate treatment because a fully populated, valid and timely record may still be wrong. A defect code can belong to the permitted vocabulary yet describe the wrong observable fault. A meter value can have the expected format yet come from the wrong meter. Accuracy checks therefore require an external reference and a sampling procedure. The reference itself needs review, especially when expert judgement is used to adjudicate inspection or defect categories.

¶ 05

Failed checks need disposition rules. Some records can be rejected immediately, such as an impossible timestamp. Others should be quarantined with the source retained, such as a duplicate bundle event whose physical status is unclear. A provisional value may support a shift review only when its status travels with the KPI. Silent imputation, deletion or overwriting removes the evidence needed to diagnose the failed hand-off.

¶ 06

Exhibit 18 provides an illustrative control-planning matrix. The scores do not assess a real factory. They show how a team can record whether a control is absent, designed, executed or supported by retained evidence for each log and dimension.

The matrix should lead to a small number of repairs, not a second reporting burden. For each weak cell, the steward records the failing records, decision affected, root hand-off, corrective action and retest result. A high design score means little without retained execution evidence. The control map becomes useful when a reviewer can move from a cell to the actual exception log and see what changed.

¶ 08
Key figures from chapter 07 · Exhibit 34Key figuresillustrativeOTIF reconciles the due-order population with fulfilled promises
  • 80Orders dueIllustrative denominator
  • 64Received on time and in fullIllustrative numerator
  • 16Not OTIFSix short, four late, two received late after dispatch, four other
  • 80%OTIF64 divided by 80, multiplied by 100

Read-outOrders due: 80. Illustrative denominator

Method and source

Illustrative worked example. 64 OTIF orders + 16 orders not OTIF = 80 orders due. OTIF rate = 64 / 80 x 100 = 80 percent. These are assumed values used to demonstrate the calculation.

Unit: illustrative orders and percent. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗

4.42 min · 6 paragraphs · read with a related exhibit

Time and identity prevent false comparisons

Factories compare periods, lines and styles. Those comparisons are valid only when identity survives the comparison. A line code reused after a layout change, an operation code reused after a method revision or a style code attached to a revised routing can make unlike work appear continuous. The result is a clean time series whose meaning has quietly broken.

Shared vocabularies and standards support interoperability among datasets, according to W3C guidance.[S25] GFT would apply that principle before selecting integration technology. The minimum identifiers cover line, operation, style, order, shift, employee or team where justified, machine, material batch and meter. Each identifier has one authoritative owner and a defined relationship to the production event. Free-text substitutes are permitted only as controlled exceptions, not as parallel master data.

¶ 02 · 1 source

S25

Effective dating is more useful than overwriting. A routing record retains the method revision and the interval during which it applied. A line assignment retains its start and end. A defect code retains its definition and successor if the taxonomy changes. Historical events then resolve against the master-data version in force at event time, while current planning uses the current version. This avoids both dangers: rewriting the past with today's structure and freezing tomorrow's work inside obsolete codes.

¶ 03

Shift identity requires a calendar rather than a date extracted from a timestamp. Work crossing midnight belongs to the shift defined by the operating calendar, not automatically to the calendar date on which the event occurred. The contract records the shift start, end and approved exceptions. Late entries retain both the production shift and the entry timestamp. This allows an operations review to use the intended population and a data-quality review to measure reporting delay.

¶ 04

Comparisons also need population flags. Style, order, routing revision, staffing cohort and machine configuration can explain why two output records are not like for like. These fields should not become an excuse to discard inconvenient results. They define cohorts in advance, so a supervisor can compare similar work and an analyst can state the limitations of a pooled result. A changed routing is a new comparison condition, not a silent edit to old history.

¶ 05

Identity controls extend to people with restraint. A performance system should collect the least personal information needed for the operational decision, restrict access and avoid turning a team process measure into an unsupported individual verdict. This is a design recommendation, not a claim of legal compliance. Where worker identity is necessary for skill, attendance or allocation records, its purpose and permitted use belong in the data contract and governance review.

¶ 06

4.53 min · 11 paragraphs · 2 exhibits

Measurement variation can mimic process variation

Step 1 of 6Define the decision and material difference

Exhibit 20 · illustrativeMeasurement-system evidence gates consequential target use

Define the decisionand materialdifferenceStudyrepresentativeitems and blinded…Assess measurementerrorsCompare measurementerror with thedecision gapRelease for definedtarget useRepair, redefine orlimit the decision
Define the decision and materialdifferenceStudy representative items and blindedrepeatsAssess measurement errorsCompare measurement error with thedecision gapRelease for definedtarget useRepair, redefine orlimit the decision

Define the decision and material difference

Define the decision and material difference. Starting point. Leads to Study representative items and blinded repeats. · illustrative

A KPI observes production through a measurement system.

Study representative items and blinded repeats

Study representative items and blinded repeats. From Define the decision and material difference, Repair, redefine or limit the decision (Retest). Leads to Assess measurement errors. · illustrative

Assess measurement errors

Assess measurement errors. From Study representative items and blinded repeats. Leads to Compare measurement error with the decision gap. · illustrative

Compare measurement error with the decision gap

Compare measurement error with the decision gap. From Assess measurement errors. Leads to Release for defined target use (Fit for use), Repair, redefine or limit the decision (Not fit). · illustrative

Release for defined target use

Release for defined target use. From Compare measurement error with the decision gap (Fit for use). End point. · illustrative

Repair, redefine or limit the decision

Repair, redefine or limit the decision. From Compare measurement error with the decision gap (Not fit). Leads to Study representative items and blinded repeats (Retest). · illustrative

The method behind it: Minimum evidence pack.

Method and source · Exhibit 20

Illustrative GFT control flow based on the measurement-error categories in S40. Acceptance is relative to the intended decision, not a universal Gauge R&R threshold. A failed gate returns to repair or redefinition before target use.

Unit: decision sequence. Status: illustrative. Sources: S40. Illustrative figures are teaching examples, not measured factory results.

4.5 · the bodyExhibit 20 above; its figures are illustrative where marked.

A KPI observes production through a measurement system. When the observed value changes, the cause may be the work, the instrument, the observer, the recording practice or a combination of them. NIST's Gauge R&R guidance explicitly addresses errors affecting gauges and instruments in production, including repeatability, reproducibility, stability and bias.[S40] The management mistake is to interpret every movement as process performance before separating these sources.

Repeatability asks whether the same method, observer and instrument produce close results on the same item under repeated conditions. Reproducibility asks whether the result remains sufficiently close when observers, gauges or other defined conditions change. Bias concerns systematic difference from a reference. Stability concerns behaviour over time. Resolution concerns whether the instrument or recording increment can distinguish a difference that matters to the decision. These are distinct failure modes, so a single calibration sticker cannot answer all of them.

¶ 02

Garment-floor measures need the same scepticism even when no conventional gauge is present. Defect grading depends on observers, reference samples, lighting, instructions and the condition presented. Piece counting depends on bundle integrity, boundary discipline and duplicate handling. Timestamp measures depend on clocks, event definitions and when an operator presses a key. Meter reading depends on instrument identity, units, resolution and transcription. A manual process is still a measurement system.

¶ 03

A useful study begins with the decision, not with a generic pass mark. The team states the smallest difference that would trigger action and the consequence of a wrong classification. It then selects items that represent the actual range of work, including difficult borderline cases where inspection agreement matters. Observers perform blinded repeats in a randomised order where practical. The study records raw outcomes and conditions rather than retaining only a final agreement percentage.

¶ 04

For continuous measures, a simple decomposition can guide the analysis: observed variation contains process variation and measurement variation under stated assumptions. The assumptions matter. If the same item changes between readings, if observers learn the sequence or if gauge error grows with the measured value, the simple decomposition is not enough. The study design should expose those conditions rather than hide them inside a single ratio.

¶ 05

For attribute decisions, agreement statistics must preserve the confusion pattern. An inspector who misses defects creates a different risk from one who rejects good garments, even when total agreement is identical. The review therefore separates false acceptance, false rejection and disagreement on defect type. A reference set needs an adjudication rule and periodic review, because calling one expert's answers truth merely relocates the measurement problem.

¶ 06

Exhibit 19 illustrates why a central result alone is insufficient. Three constructed observers have the same median accepted count but different ranges across blinded repeats of one reference set. The ranges are observed study outcomes in this example, not confidence intervals and not evidence from a factory.

The example does not say which observer is correct. It shows that Observer B's repeat outcomes vary more and that a reference comparison is needed to assess bias. Nor does the range establish a universal acceptance limit. The factory compares the observed measurement error with the decision gap. A small target difference cannot support a confident ranking if routine observer variation is wider than that difference.

¶ 08

Exhibit 20 places this evidence before target use. Repair may mean recalibration, a better reference set, clearer defect definitions, a revised counting event, additional observer practice or a coarser but more honest KPI precision. Repeating the same study without changing the measurement system is not repair.

Measurement-system analysis also changes management behaviour. Where error is material, leaders use ranges, longer observation windows or physical verification rather than false precision. They do not rank workers on differences the measurement system cannot resolve. They may continue to collect a provisional measure for learning, provided its limitation is visible and no high-stakes consequence depends on it.

¶ 10

4.62 min · 8 paragraphs · read with a related exhibit

A control limit is not a specification or a target

Control limits, specifications and targets answer different questions. A control limit describes expected process behaviour under a stated statistical method and baseline. A specification states a requirement that a product or process must satisfy. A target states the result management wants. Confusing them can make a capable process look unacceptable, make an unacceptable process look stable or provoke intervention whenever ordinary variation occurs.

NIST describes statistical process control as a comparison between what is happening now and what happened previously, using historical data or a process model to calculate limits for expected measurements.[S09] The baseline is therefore part of the result. A limit calculated during an unstable ramp, under a different method or from a mixture of unlike styles does not acquire authority merely because software draws it precisely.

¶ 02 · 1 source

S09

The measurement-system gate comes first. If observer variation or meter error is material, a control chart may signal changes in the measurement process rather than the production process. The team should retain the study evidence beside the chart configuration and state any remaining limitation. This is especially important when inspection standards, reference samples or timestamp practices change, because the apparent process population may no longer be continuous.

¶ 03

A stable baseline is not simply a long sequence of numbers. The reviewer examines the production conditions, exclusions, sampling frequency and missing records, then documents why the baseline population is suitable. Known interventions and method revisions are marked. Points are not removed merely because they are inconvenient. Any exclusion retains its reason and the effect on the calculated limits, so baseline construction does not become an unreviewed route to a preferred answer.

¶ 04

The control method must fit the record. Defect proportions, counts, continuous cycle times and rare events have different statistical needs. Sample size and sampling frequency affect interpretation. Where the factory lacks the conditions for a defensible chart, a run chart with contextual notes and physical investigation is more honest than an elaborate limit calculation. The objective is to direct attention to unusual evidence, not to display statistical vocabulary.

¶ 05

Specifications remain visible on their own terms. A customer requirement is not recalculated from factory history, and a process inside control limits can still produce nonconforming work. Conversely, a process can meet a specification on average while an unusual point warrants investigation. Management review needs both answers: whether behaviour is stable relative to its baseline and whether output satisfies requirements.

¶ 06

Targets sit beside rather than inside this logic. A target can be intentionally beyond current capability, but the gap should prompt resource and method decisions rather than repeated adjustment to routine noise. When a verified intervention changes the process, the team documents the new baseline before adopting new limits. Limits are not reset after every movement, because that would erase the evidence needed to distinguish sustained change from ordinary variation.

¶ 07

A chart therefore needs a contract of its own: measure version, population, sampling rule, baseline period, calculation method, limit version, specification source, target basis and response rule. The reviewer records what action a signal should trigger and who has authority to investigate. Without those fields, the chart is only a picture of variation, not a governed control.

¶ 08

4.73 min · 9 paragraphs · read with a related exhibit

Definition changes require versioned migration

Related · chapter 099 paragraphs step it

Related exhibit 43 · chapter 09Material flowillustrativeMaterial records must connect accepted product, residual streams and destinations
Fabric and trim receivedDeclared factory bounda…Accepted garmentsCutting offcutsTrim and packagingUnresolved differencePreparation for reuseRecycling with evidenceDocumented disposal

Read-outFabric and trim received to Declared factory boundary: 1,000 illustrative kilograms of fabric and trim in one period

Method and source

Illustrative mass balance, not a GFT or factory result. Assumed input is 1,000 kg. Factory outputs are 800 kg in accepted garments, 140 kg of cutting offcuts, 40 kg of trim and packaging, and a 20 kg unresolved difference, totalling 1,000 kg. Offcut destinations are 80 kg reuse, 50 kg recycling and 10 kg disposal. Trim and packaging destinations are 25 kg recycling and 15 kg disposal. Every real link would require a source record and destination evidence; the unresolved difference cannot be allocated silently.

Unit: illustrative kilograms of fabric and trim in one period. Status: illustrative. Sources: S35. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗
4.7 · Introduction · paragraph 1 of 9

Metric definitions will change as the factory learns, customer requirements evolve and source capture improves. The risk is not change itself. The risk is an untraceable change that makes a new result look like an improvement or decline against an incompatible history. Data governance is a process of setting and enforcing priorities for managing and using data, which gives definition change an explicit decision right rather than leaving it to whoever edits a spreadsheet first.[S22]

A change request begins with the reason and the decision affected. It distinguishes correction of an implementation error from a deliberate change in operational meaning. Fixing a denominator mapping in code is not the same as deciding that repaired garments now count as first-pass good. The first restores the approved contract. The second creates a new measure version and may invalidate comparisons, incentives and model features built on the old one.

The request records the current definition, proposed definition, source-event implications, owner, approvers and effective date. It identifies every affected surface: source sheet, validation rule, line board, plant report, export, sustainability calculation, incentive rule and analytical dataset. A small factory can keep this register in a controlled workbook. What matters is completeness and accountability, not the sophistication of the tool.

Back-calculation requires evidence, not preference. If the retained raw events contain enough information to calculate both versions, the steward may rebuild history and reconcile the result to the original records. The back-calculation keeps its own version and test evidence. If the old events do not contain the new distinction, history must not be fabricated. The report carries a break, explains the difference and, where useful, presents overlapping old and new measures during a controlled transition.

Parallel operation provides a practical bridge. Both definitions run on the same events for a suitable review window, with differences investigated and explained. The purpose is not to choose the more flattering series. It is to prove that the new rule captures the intended population, that source systems implement it consistently and that users understand the new comparison basis. The transition ends through the same approval route that authorised it.

Migration acceptance uses concrete reconciliation cases. The worked example in the metric contract becomes a test fixture, joined by boundary cases such as partial bundles, repairs, late entries, changed routings and duplicate events. Expected outputs are agreed before release. Source totals reconcile to KPI inputs, KPI outputs reconcile to every report and corrections preserve their history. A visual check of the new dashboard cannot replace these tests.

Historical extracts carry the definition version with the values. This prevents a later analyst from treating differently defined observations as one training population. Models and rules that consume the KPI receive an impact review before migration. If a threshold was learned under one inspection or counting regime, it remains provisional until validated under the new one. The same caution applies to external benchmarks and target commitments.

Retirement is also controlled. When a measure no longer supports a decision, the owner records why it is withdrawn, which reports lose it and how its history remains accessible. Removing an inconvenient KPI without a record damages institutional memory just as surely as redefining it in secret. A useful data dictionary therefore contains active, superseded and retired versions, with their effective intervals and relationships.

GFT's practical rule is that the history of meaning is part of the operating record. The factory does not need a heavy governance bureau to preserve it. It needs one accountable owner, one visible change register, reproducible calculations and the discipline to leave a discontinuity visible when evidence cannot bridge it. That discipline protects every later comparison, from a shift review to an investment model.

Check the record

The chapter keeps its sources within reach.

Every knot is a source this chapter cites; select one to read its record, or filter the register by grade. Publication dates and inherited-source limits stay explicit. Read the paper's full evidence summary.

9 sources · 19 citation marks on this pageMost cited: S22, 3 times

Grade AGrade BGrade CKnot size: citations on this page

All 9 records shown

c04-S01 · Grade A

International Organization for Standardization

ISO 22400-2:2014 Automation systems and integration: Key performance indicators for manufacturing operations management, Part 2: Definitions and descriptions

The KPIs are presented by means of their formula and corresponding elements, their time behaviour, their unit/dimension and other characteristics.

2014-01. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.

Open the recorded source ↗
Chapter source notes

S01 International Organization for Standardization. 2014-01.

S22 United States Federal Data Strategy. 2020.

S23 ISO/IEC. 2008.

S24 UK Government Data Quality Hub. 2020-12-03.

S10 National Institute of Standards and Technology, Manufacturing Extension Partnership. 2022-08-04.

S06 Diamond Congress, Creative Construction Conference. 2023.

S25 W3C. 2017-01-31.

S40 NIST/SEMATECH. 2003.

S09 NIST/SEMATECH. 2003.

Keep the thread · chapter 04 of 14

Chapter 05 picks up the thread.

Move the shuttle along the rack to preview any chapter: its sections, exhibits and reading time. Draft web edition. This research is not investment, legal or tax advice; illustrative models are not measured factory results.

The paper's rack · 14 boltsBolt length: reading time

05Part II: Measure the operating system

Production measures must expose losses, not compress them

Good output is the result, while the production system must retain the component losses that explain why the result occurred.

  • 5.1Nameplate capacity is not saleable throughput
  • 5.3OEE retains its three components
  • 5.5Aggregated downtime hides the action required
  • 5.7Performance loss needs a work-content reference
Reading time
27 min
Exhibits
5
Sections
7
Continue to chapter 05
← Previous: chapter 03, A KPI cascade succeeds only when the line can act on itContinue the threadChapter 05 · Production measures must expose losses, not compress them

Find a thread.

Type to search.