The cloth is woven from this chapter's 6 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.
EX 32
EX 33
EX 35
EX 36
The chapter as a draft: 7 sections, 4 exhibit wefts, one shuttle.
Lead exhibit · 32Ranked barsillustrativeOperation work content reveals the constraint before pieces move
01 / 05
Read-out
Method and source
Illustrative model for 1,000 garments. Required minutes are 1,200, 1,800, 2,400, 1,500 and 1,100. Available minutes are 2,400, 2,400, 2,000, 2,000 and 2,200. Loading equals required divided by available, multiplied by 100. No realised line performance is asserted.
Unit: percent of available minutes. Status: illustrative. Sources: S03, S04. Illustrative figures are teaching examples, not measured factory results.
The chapter's warpBar: share of the reading · square: an exhibit
Delivery reliability is an operating result, not a dispatch-room behaviour. A factory can make a defensible promise only when it can translate each order into method-based work content, compare that load with demonstrated capacity by operation and skill, and follow the order through queue, touch, rework and receipt events. Standard minutes supply the common unit, daily balancing protects flow, and monthly sales and operations planning reconciles demand with capability.[S03][S04][S42] Expediting may rescue an individual order. It cannot repair an ambiguous routing, an overloaded operation or a missing receipt record.
This chapter therefore treats the customer promise as the final link in a measured chain. Industrial engineering defines the work. Production establishes the capacity that has actually been demonstrated. Supervisors remove imbalances as conditions change. Commercial and logistics teams preserve the agreed date, quantity and proof of receipt. The measures remain useful only when each one leads to a decision before the promise is at risk.
¶ 02
7.12 min · 6 paragraphs · read with a related exhibit
Standard minutes describe a method, not a universal truth
The standard minute value, or SMV, is a work-content reference with conditions attached. The ILO defines it through the output that qualified workers can achieve without overexertion when they know and follow a specified method and are motivated to apply themselves.[S03] An SMV is therefore not the raw average of whatever happened on a shift. It is not transferable between different operation sequences, machine settings, material behaviours or quality requirements merely because the garment name is unchanged.
Industrial engineering should start with an operation breakdown that describes the work in executable terms. Each operation needs a sequence number, a clear start and finish, the machine or workstation, the attachment or folder, the material and trim condition, the quality criterion and the disposition of the completed bundle. The method release should also identify the style, product family, routing revision and effective date. Without those attributes, a time value cannot be audited against the work that was actually performed.
¶ 02
The observed time and the released standard serve different purposes. Observations describe a particular worker, method and period. The released SMV provides the planning reference for a defined method and qualified performance. The ILO discussion also distinguishes allowances within the calculation, including personal time and machinery-related allowances, before the aggregate SMV is formed.[S03] GFT would retain the observed samples, rating basis and allowance rationale beside the result rather than leaving only a final number in a routing table.
A provisional standard is legitimate during ramp, but it must be labelled as such. Its status should state the evidence still missing, such as a stable method, enough qualified observations or confirmation of the allowance basis. The planner can use that provisional value with an explicit uncertainty allowance. The reviewer should not present the resulting capacity as settled. Once the method changes, the old value remains attached to its historical orders and a new revision becomes effective for future comparisons.
¶ 04
Method control also protects workers. A standard developed for one sequence should not become a personal output target for a worker who has been given a different machine, an incomplete bundle or an unapproved material substitution. Before a variance is attributed to performance, the supervisor should be able to confirm that the released method was available, the operator was qualified for it and the required inputs were present. A work-content measure is credible only when those conditions are visible.
¶ 05
Finally, the SMV does not measure every form of time. It does not replace records of waiting for material, machine stoppage, changeover, absence, rework or dispatch queues. Those events belong in their own logs. Keeping them separate prevents a planner from hiding an operating loss inside an inflated standard and prevents an engineer from treating a necessary allowance as an unexplained delay.
¶ 06
7.23 min · 9 paragraphs · 2 exhibits
Capacity must be expressed in comparable work content
Exhibit 319 paragraphs step it
Exhibit 31RegisterillustrativePiece counts hide a heavier style mix until work content is calculated
Style
Style A
Order pieces
600
SMV per piece
6
Required standard minutes
3,600
01 / 03
Read-out
Open the full register (3 rows)
Style A
600
6
3,600
Style B
400
14
5,600
Total
1,000
Mixed
9,200
Method and source
Illustrative model. Style A requires 600 pieces x 6 standard minutes = 3,600 standard minutes. Style B requires 400 pieces x 14 standard minutes = 5,600 standard minutes. Total load is 9,200 standard minutes. SMV interpretation follows S03; all order values are assumed.
Unit: illustrative pieces and standard minutes. Status: illustrative. Sources: S03. Illustrative figures are teaching examples, not measured factory results.
Piece counts are a poor common denominator when styles have different work content. GFT would calculate required standard minutes for each order, operation and method revision by multiplying the order quantity by the applicable SMV, then sum those requirements by product family and planning period. The calculation is simple, but the master data must be precise: quantity, operation, style, routing revision and SMV status all affect the result.
The illustrative mix in Exhibit 31 shows why a total piece count cannot establish the load. The values are constructed only to demonstrate the arithmetic and do not describe a GFT factory or a forecast.
In this illustrative case, the order contains 1,000 pieces and 9,200 standard minutes, giving a mix-weighted work content of 9.2 standard minutes per piece. Style B supplies only 400 pieces but carries 5,600 of the 9,200 required standard minutes. A plan that treated all pieces as equivalent would understate the effect of changing the mix. The same arithmetic should be applied at operation level, where a style may add work to one constraint without changing the total by the same proportion.
Available capacity needs an equally explicit basis. For each operation and skill group, the factory should identify scheduled attendance, planned meetings or maintenance, approved non-production time and the number of qualified workers or compatible workstations. Available minutes are a time supply, not yet a promise of good output. The plan must then account for demonstrated rate, stoppages, learning and first-pass quality using records from comparable work.
OEE provides a useful discipline here because it retains availability, performance and quality as separate loss components rather than treating output as an unqualified equipment result.[S06] The capacity model should not multiply a general efficiency assumption through every operation without checking what that factor contains. If attended minutes have already been reduced by a recorded stoppage, applying the same availability loss again would understate capacity. If repaired pieces are counted as first-pass good, the quality factor would overstate it.
The illustrative loading pattern appears in Exhibit 32. It locates the first capacity question before the order is released, but it does not prove that the longest operation will remain the constraint in production.
The response to the illustrative 400-minute deficit is a choice, not an instruction to work faster. The supervisor and industrial engineer can test a rebalance from an operation with spare compatible capacity, a method improvement that removes work, additional qualified time, a different order sequence or a revised promise. Each option has a different mechanism and verification record. The capacity statement becomes useful when it makes those choices visible while there is still time to act.
7.32 min · 7 paragraphs · read with a related exhibit
Balancing continues after the plan is issued
A feasible plan can still become an unbalanced line. The ILO garment-sector report assigns line balancing to supervisors systematically before production through planning and daily during production. It also describes regular in-production checks using recorded output and work in progress to identify bottlenecks and their causes.[S04] The important point is the management rhythm: balancing is not a one-time industrial-engineering calculation handed down with the style file.
The pre-production balance begins with the released operation bulletin, the expected order quantity, the available skills and the machine layout. Work is allocated so that each station has a coherent assignment and the planned load is feasible at the constraint. The supervisor should also know which operations are method-sensitive, which workers can cover them and where bundles will be counted. A balance that depends on an unnamed person arriving with an unrecorded skill is not yet an executable plan.
¶ 02
During production, the line board should show planned and actual good output by interval, WIP at agreed boundaries, operation-level stoppages, quality interruptions and skill absences. The purpose is to see a forming queue before the end-of-line total falls. A station can meet its own local target while starving the next station or building an excessive buffer. The review therefore concerns the whole sequence, not isolated operator utilisation.
¶ 03
A rebalance should follow diagnosis. If the cause is a wrong work allocation, the supervisor can move a compatible operation or share work across qualified stations. If the cause is a machine fault, maintenance owns the response and the plan must reflect the interrupted capacity. If the cause is missing material, the shortage remains visible rather than being converted into an operator performance loss. If a method change is required, industrial engineering must release it before new time comparisons are made.
¶ 04
WIP limits support this review, but they should not be treated as proof of flow by themselves. A line can remain below a WIP ceiling while one order waits untouched and another is repeatedly prioritised. The board therefore needs order or bundle age as well as quantity. It also needs the reason for any deliberate sequence exception, especially when an urgent order displaces work that was already promised.
¶ 05
Note
The review should close with demonstrated capability, not with the act of rebalancing itself. Did the constraint move? Did good output increase without creating more rework? Did the oldest WIP fall? Did the new allocation remain within qualified skill coverage? Those questions connect the supervisor's intervention to delivery reliability. They also produce the evidence that the next monthly capacity review should use in place of nameplate assumptions.
¶ 06
7.42 min · 7 paragraphs · 1 exhibit
WIP age reveals problems that output totals miss
Step 1 of 6Opening
Exhibit 33 · illustrativeQueues and rework dominate an illustrative order lead time
Opening
Opening: total 0. Running total 0 illustrative calendar days · illustrative
Output is a count at a boundary.
Material wait
Material wait: adds 3. Running total 3 illustrative calendar days · illustrative
Cut and sew touch
Cut and sew touch: adds 2. Running total 5 illustrative calendar days · illustrative
Rework loop
Rework loop: adds 1. Running total 6 illustrative calendar days · illustrative
Finish and dispatch wait
Finish and dispatch wait: adds 2. Running total 8 illustrative calendar days · illustrative
Total lead time
Total lead time: total 8. Running total 8 illustrative calendar days · illustrative
Method and source · Exhibit 33
Illustrative model. Material wait 3 days + cutting and sewing touch time 2 days + rework loop 1 day + finishing and dispatch wait 2 days = total lead time 8 days. S10 supports the general connection between correction and flow, not these assumed durations.
Unit: illustrative calendar days. Status: illustrative. Sources: S10. Illustrative figures are teaching examples, not measured factory results.
7.4 · the bodyExhibit 33 above; its figures are illustrative where marked.
Output is a count at a boundary. Flow is the experience of an identified order between boundaries. Two lines can report the same daily output while one advances orders predictably and the other leaves a small population stranded for long periods. An end-of-day total cannot distinguish those conditions. Order and bundle timestamps can.
Quality is part of this flow record. A NIST Manufacturing Extension Partnership case concerning a manufacturer's returned-material process reports a large reduction in processing time alongside an increase in first-pass yield.[S10] It is not a garment-factory benchmark and its values should not be transferred as targets. The mechanism is nevertheless relevant: correction consumes touch time, repeats handling and delays the order, so repaired output cannot be treated as equivalent to work completed correctly at the first pass.
Each WIP record should identify the order, style, bundle, quantity, current operation and last completed event. A timestamp at entry to a queue and another at the start of work allow queue time to be separated from touch time. A return to an earlier operation should open a rework interval with its defect or correction reason, not overwrite the original history. The final disposition should reconcile the quantity that entered, was accepted, was repaired, was rejected or remains open.
¶ 03
The illustrative order in Exhibit 33 makes this decomposition visible. Its eight-day total is constructed from assumed durations to demonstrate the accounting, not from an observed factory.
In that illustrative case, only two of the eight days are recorded as cutting and sewing touch time. Five days sit in material, finishing or dispatch queues and one day is a rework loop. An output review focused only on sewing speed would miss most of the elapsed time. The corrective agenda would instead begin with the causes and ownership of the material wait, the repeated correction and the final queue.
¶ 05
Not every waiting interval is avoidable. A planned consolidation, a customer-approved hold or a required quality quarantine can be legitimate. The record should therefore distinguish planned waiting from an unmanaged queue and retain the authorisation where the order was deliberately stopped. The analytical error is not simply to count waiting. It is to classify every minute as waste before its purpose is known, or to hide every delay beneath a generic production label.
¶ 06
Ageing also needs a defined clock. Calendar time measures the customer's elapsed experience, while working time explains how much scheduled operating opportunity passed. Both can be useful, but they should not be mixed silently. The oldest-order age, the share of WIP beyond an agreed review threshold and the number of reopened loops provide different prompts. The threshold itself should trigger investigation rather than automatic blame, particularly during ramp or a customer-caused hold.
¶ 07
Interlude · the cloth half-woven
6 exhibits carry this chapter's argument.
Woven: sections 7.0 to 7.4Still to weave: 7.5 to 7.7
Sourced case values from the article abstract, published 3 December 2024. The gate-to-gate boundary includes in-factory yarn production, knitting, grey-fabric storage, pretreatment, dyeing, finishing and inspection, followed by cutting, sewing, garment washing, dyeing, pressing and finishing. Energy inputs include natural gas, oil and grid electricity. The 0.94 kg/piece and 56.65 tonnes/day figures are CO2 only, not CO2e. Do not use these integrated yarn, fabric and garment results as cut-make-trim-only benchmarks or GFT claims.
Unit: reported case values for the Bangladeshi T-shirt study. Status: sourced. Sources: S37.
Exhibit 34Status lampsillustrativeOTIF reconciles the due-order population with fulfilled promises
Read-out · illustrative
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.
On-time-in-full delivery, or OTIF, is meaningful only when the commercial promise and the fulfilment event are defined together. Monthly sales and operations planning is conducted at an aggregate product-family level, which is necessary for management reconciliation but too coarse to diagnose an individual customer order.[S42] The order-level OTIF record must retain the agreed date, required quantity, quantity tolerance, partial-shipment rule, receipt location and evidence that the customer received the goods.
GFT would calculate order-level OTIF as the share of orders due in the period that meet both the date and quantity conditions, expressed as a percentage of all orders due. An order-line measure may answer a different service question, but it should not be mixed with the order-level result. A single late line can make an entire order fail under one definition while barely changing a line-count measure under another. The data dictionary must state which population is being reported.
¶ 02
The date rule deserves equal care. The original customer promise, any factory acknowledgement and any customer-agreed revision should be separate fields. Performance against the current agreed promise may be commercially useful, while performance against the first promise exposes how often replanning occurred. Neither should silently replace the other. Dispatch is also not receipt. A shipment can leave the factory on the agreed day and still arrive late, which is why the selected proof-of-receipt event matters.
¶ 03
Note
Exhibit 34 summarises that illustrative population. The important control is the reconciliation between due orders, fulfilled orders and the reasons for failure.
The failure reason should point to the earliest controllable break in the chain, while preserving later events. Material release, cutting, sewing, finishing, inspection, documentation, transport and customer-receipt causes can coexist. A primary reason supports accountability, but a secondary-cause field prevents the record from hiding a sequence of problems. Free text can explain the event; a controlled reason code makes the repeated pattern reviewable.
¶ 05
Finally, OTIF should not be improved by narrowing the denominator after the fact. Cancelled orders, customer holds and agreed revisions need explicit inclusion rules and an audit trail. Commercial teams should be able to explain movement in the due population as carefully as movement in the numerator. A reliable service measure is one whose exceptions are visible enough to survive challenge from production, sales and the customer.
¶ 06
7.62 min · 8 paragraphs · 1 exhibit
Lead-time decomposition locates the delay
Exhibit 358 paragraphs step it
Exhibit 35FlowillustrativeOrder timestamps separate queue, touch and rework time
01 / 07
Read-out
Method and source
Illustrative process design. Shared order, style and routing identifiers connect the events. The rework branch returns authorised correction to production; accepted work proceeds to dispatch. S21 supports information interoperability, not this specific factory design.
Unit: . Status: illustrative. Sources: S21. Illustrative figures are teaching examples, not measured factory results.
A lead-time total becomes actionable only when its component events share an identity across commercial and production records. NIST states that the ability of different systems to exchange, understand and use product, production and business data depends critically on information standards.[S21] A garment factory does not need to adopt every possible standard before it can measure flow. It does need one governed order identifier, consistent style and routing identifiers, and agreed meanings for the events through which an order passes.
The illustrative event chain in Exhibit 35 joins the commercial promise to production and receipt. The rework branch is explicit because a corrected unit repeats part of the flow rather than creating a new, unrelated order.
Every event needs more than a timestamp. The record should carry the order and, where relevant, bundle identifier; the event code; the quantity; the operation or location; the event time; the time entered into the system; and the person or device supplying it. Event time and entry time answer different questions. A late entry can make a timely physical event appear delayed, while an overwritten timestamp can erase the evidence needed to investigate capture latency.
The boundary of each lead-time measure must be declared. Customer lead time may run from order acceptance to receipt. Factory production lead time may run from material release to dispatch. Manufacturing touch time may include only intervals in which an identified operation is being performed. These measures can coexist because they answer different questions. They become misleading when a shorter internal interval is presented as the customer's full experience.
Duration arithmetic should respect that boundary. Queue time is the interval between completion at one defined state and the start of the next eligible state, subject to the site's calendar convention. Touch time sums the relevant work intervals without silently including intervening queues. Rework time is recorded on the repeated path and linked to the originating inspection. If a bundle splits or merges, quantity reconciliation must accompany the event so that the flow record does not invent or lose pieces.
A small manual event set is preferable to a large set of unreliable timestamps. At the first shift, order acceptance, material release, cutting completion, sewing completion, finishing completion, final inspection disposition, dispatch and receipt provide a useful skeleton. Additional operation-level events can be added where they change a decision. The capture test is whether two people reviewing the same order would assign the same event, quantity and time.
The review output should be a specific intervention. A long material-release queue calls for material and planning decisions. Repeated inspection returns call for quality prevention at the originating operation. A dispatch queue after accepted production calls for documentation or transport action. Lead-time decomposition earns its place by directing the right function to the interval it can change, while leaving the order's complete history intact.
7.74 min · 12 paragraphs · 1 exhibit
S&OP reconciles demand with demonstrated capability
Step 1 of 4Demand and order review
Exhibit 36 · illustrativeThe monthly plan uses demonstrated rather than nameplate capability
Demand and order review
Demand and order review: from 0 to 1 (weeks in monthly cycle) · illustrative
Sales and operations planning supplies the management forum in which demand and supply are brought into one plan.
Capacity and constraint check
Capacity and constraint check: from 1 to 2 (weeks in monthly cycle) · illustrative
Management reconciliation
Management reconciliation: from 2 to 3 (weeks in monthly cycle) · illustrative
Release promises and actions
Release promises and actions: from 3 to 4 (weeks in monthly cycle) · illustrative
The method behind it: Warning.
Method and source · Exhibit 36
Illustrative planning sequence. S42 supports at-least-monthly management review at product-family level. The four weekly windows are assumed to show a possible sequence, not required deadlines or realised milestones.
Unit: weeks in monthly cycle. Status: illustrative. Sources: S42. Illustrative figures are teaching examples, not measured factory results.
7.7 · the bodyExhibit 36 above; its figures are illustrative where marked.
Sales and operations planning supplies the management forum in which demand and supply are brought into one plan. The source definition used here calls for performance at least monthly and management review at aggregate product-family level. It also requires detailed and aggregate plans to be reconciled.[S42] For a garment factory, that reconciliation should occur in standard minutes as well as pieces, with order-level promises rolling into product families rather than disappearing into a plant-wide average.
The supply input should be demonstrated capability by operation and skill. Industrial engineering brings current and provisional SMVs, method releases and known routing changes. Production brings attended time, stoppages and recent output for comparable cohorts. Quality brings first-pass performance and rework demand. Human resources brings demonstrated skill coverage and approved attendance plans. Materials and logistics bring release constraints and transport events. Sales brings the order book, forecast assumptions and the exact basis of each requested promise.
¶ 02
The roll-up should preserve the constraints beneath the family total. Required standard minutes can be summed across styles only after each quantity has been tied to the correct routing revision. Available minutes can be summed only where the relevant skills and workstations are genuinely interchangeable. A family-level surplus may therefore coexist with an operation-level shortage. When that happens, the meeting should see both positions and should not use the surplus to conceal the incompatible constraint.
¶ 03
The same discipline applies to the planning horizon. Near-term orders deserve a reconciliation against released methods, confirmed materials and demonstrated skill coverage. Later periods can carry wider assumptions about recruitment, training, method improvement or demand, provided those assumptions have owners and review dates. This separates a commitment that must be executed now from a capability that still has to be created. It also shows when a sales opportunity depends on an operational change rather than on spare capacity already present.
¶ 04
This is deliberately different from nameplate capacity. A machine or headcount total cannot show whether the required operations can be performed to the current method by qualified people, nor whether correction and changeover will consume part of the available time. During ramp, the review should retain a range where the evidence is thin and identify what must be learned before the range can narrow. A single apparent capacity number would hide precisely the uncertainty that the meeting needs to govern.
¶ 05
The illustrative monthly sequence in Exhibit 36 puts work-content and constraint reconciliation before management releases the plan. The monthly cadence comes from the S&OP source; the weekly placement is a GFT planning illustration, not a universal timetable.
The meeting should test a small number of explicit choices. If demand exceeds demonstrated work-content capacity, management can resequence orders, add qualified time, approve a feasible method or layout change, adjust the product mix, or revise customer promises. If demand is below available capacity, the same review can consider training, maintenance or a different release pattern without pretending that idle time is a production failure. Each scenario should show its assumptions and the constraint it relieves.
¶ 07
Promise governance belongs inside this process. Sales should not create a new date from an unvalidated piece-rate assumption, and production should not accept an overload silently and recover it through routine expediting. Where a customer request cannot be met under the demonstrated plan, the response should state the earliest feasible alternative and the conditions that could change it. That answer is more useful than a hopeful date supported only by aggregate nameplate capacity.
¶ 08
Expediting should remain an exception with a visible mechanism. The expedite record should name the order, the missed planning condition, the work displaced, the additional handling or transport required and the authority approving the exception. The next review should ask why the normal chain did not protect the promise. Repeated expedites around the same operation are evidence for capacity, method or material action, not proof that the factory has a reliable recovery capability.
¶ 09
The management scorecard should connect outcomes to their earlier signals. OTIF and customer lead time describe the result. Work-content coverage, constraint loading, oldest WIP, rework-loop age and order-event completeness show whether future promises are exposed. None of these measures should be used alone. A low WIP total can conceal starvation, a high output total can conceal late orders, and an attractive OTIF result can conceal a narrowed denominator.
GFT's practical sequence is therefore direct. Release a method-based routing. Convert orders to work content. Reconcile compatible time and skill. Balance daily against observed flow. Preserve order events through receipt. Let the monthly plan learn from that evidence. Delivery reliability then becomes a property of the operating system, rather than a recurring act of recovery at the end of the chain.
¶ 11
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.
6 sources · 17 citation marks on this pageMost cited: S03, 4 times
Grade AGrade BGrade CKnot size: citations on this page
All 6 records shown
c07-S03 · Grade A
International Labour Organization
Sector systems analysis of textiles and clothing subsector in Ghana
A particularly important calculation is the Standard Minute Value (SMV), which is defined as “the time value arrived at for a task based on the average rate of output which qualified workers will naturally achieve without over exertion provided that they know and adhere to the specified method and provided that they are motivated to apply themselves to their work.“
2023. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
NIST IR 8107: Current Standards Landscape for Smart Manufacturing Systems
The ability of disparate systems, however, to exchange, understand, and exploit product, production, and business data rests critically on information standards.
2016. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
S06Diamond Congress, Creative Construction Conference. 2023.
S10National Institute of Standards and Technology, Manufacturing Extension Partnership. 2022-08-04.
S21National Institute of Standards and Technology. 2016.
Keep the thread · chapter 07 of 14
Chapter 08 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
1.1
1.2
1.3
1.4
1.5
1.6
1.7
01Part I: The measurement contract
The first shift must make evidence as well as garments
A factory without an operating baseline cannot rely on hindsight, so GFT treats measurement as part of production from the outset.
1.1A greenfield line begins with uncertainty, not a stable average
1.2The local-processing gap raises the cost of weak operating control
1.3The earliest records become the factory's institutional memory
1.4Measurement serves decisions rather than reporting volume
Effective labour cost joins productivity with capability and fairness
A low nominal wage does not establish a low cost per good garment, so the people scorecard must include skill, supervision, attendance and working-time effects.
8.1Cost per good garment is the controlling labour measure
8.4The skill matrix records demonstrated operations
8.6Supervisor capability is a measurable production asset
Improvement closes only when the cause and result are verified
A corrective-action system should distinguish abnormal variation, test causes, verify effects and update standard work rather than count completed actions.
12.1Problem selection begins with a measurable gap
12.4Common and special causes require different responses
12.7A3 makes the reasoning inspectable
12.10Root causes compete until evidence discriminates
Maturity gates stop digital ambition outrunning discipline
The factory should earn each digital step through reliable records, active management and verified improvement rather than buy a platform to compensate for their absence.
13.1Maturity spans behaviour as well as technology
13.4Clean manual capture is the first digital asset
13.7Active management is a separate gate
13.9History-dependent models wait for usable history
The first eighteen months install a system that can prove value
GFT recommends four gated stages: clean capture, active cadence, verified improvement and a data-driven floor, with value measured in the same system throughout.
14.1Approve the operating contract before the first shift
14.3Months one to three establish clean capture
14.5Months four to eight make the cadence routine
14.8Months nine to twelve prove the improvement loop