Skip to content
GREEN FUTURETECH.
Explore

Research libraryThe Industrial Data Spine

Chapter 01 of 14 · Part I · Draft web edition

A factory becomes reliably data-driven only when its records can be trusted

The binding constraint on industrial AI is often the broken chain between work, record and decision, not the absence of an algorithm.

Sections
7
Exhibits
4
Minutes
26
Sources
52
EX 02 · 4. Biased training snapshot. From 3. Distorted KPI: false fault (Silent ingestion). Leads to 5. Miscalibrated spare-part alert (Corrupted ground truth).

The cloth is woven from this chapter's 4 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, 2 exhibit wefts, one shuttle.

Lead exhibit · 02FlowillustrativeA small capture defect can compound into a wrong management action
1. Unownedcapture: wrongtick2. Lost context:no lot ID3. DistortedKPI: false fault4. Biasedtrainingsnapshot5. Miscalibratedspare-part alert6. Misallocatedmaintenancespend

Read-out1. Unowned capture: wrong tick. Starting point. Leads to 2. Lost context: no lot ID (No schema check).

Method and source

Illustrative sewing-line event traced from shop-floor capture through context, KPI calculation, training snapshot, model output and management decision. Failure mechanics are derived from technical-debt entanglement in S18 and upstream data cascades in S19.

Unit: . Status: illustrative. Sources: S18, S19. Illustrative figures are teaching examples, not measured factory results.

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

Section 1.0 · Opening · 2 min · Exhibit 01 · one movement Go to section ↓

The chapter cloth8 warp groups · one pick per paragraph

This paragraph previews 1.19 · The paper judges success by better decisions

A factory becomes reliably data-driven only when a supervisor, an engineer and a machine-learning pipeline can read the same operational record and know what physical event occurred, who owns its definition, whether the value passed quality checks and how to recover the history if a system fails.[S01][S02][S09][S26] In small and mid-sized manufacturing plants, the binding constraint on industrial analytics is rarely the absence of a statistical model.[S19][S0101] The constraint is the broken chain between shop-floor work, recorded evidence and management action.[S05][S08][S43] Green Future Tech Limited (GFT), Hong Kong SAR, anchors its work in the principle of Warp and Signal: physical production is the warp, and operational measurement is the weft. In GFT's three-part Cameroon textile programme, prepared on 31 January 2024 with source-refresh annotations retained in 2026, the sector baseline records that about 95 percent of Cameroon's cotton fibre is exported raw while about 5 percent is processed locally, against a national industrialisation target of 50 percent local processing by 2030.[R06][R07] Those baseline and target entries come from the inherited programme register, were not independently refreshed in 2026 and carry unrecorded original publication dates, so they frame the scale of the industrial ambition rather than certifying current mill output.[R06][R07] Moving from raw-fibre export to competitive yarn, fabric and garment production requires factories that can defend their daily numbers on yield, quality, downtime, order trace and resource use without hiring an enterprise data department.[R06][S02][S38] This paper specifies that alternative: an industrial data spine built on named decision rights, explicit operational meaning, enforced quality gates, reversible model releases and measured operational value.[S01][S04][S15][S36]

The urgency of governed records rises sharply when a sector seeks to rebuild domestic processing capacity under tight capital and margin constraints.[R06][R12] Inherited sector evidence illustrates the cost of operating without reliable utilisation and market alignment: CICAM's reported domestic market share fell from about 85 percent three decades ago to about 5 percent in the inherited register, while a July 2023 report recorded capacity utilisation at 33.7 percent in Garoua, 48.9 percent at CICAM 1 and 10.83 percent at CICAM 2, with underutilisation costing about CFAF 2 billion (XAF 2 billion) in 2020.[R11][R12] Meanwhile, announced third-party industrial expansion, such as the Camtext SA integrated cotton-to-textile project reported on 12 November 2025 at US$300 million (180 billion XAF) with a planned processing volume of 12,000 tonnes a year, remains an announced third-party investment target reaching optimal capacity around 2033 rather than realised factory performance.[R09][R10] Whether an operating team is rehabilitating an existing mill or commissioning a new garment line, capital equipment alone does not produce control.[S05][S36] As Exhibit 1 summarises, the gap between the inherited 5 percent local-processing baseline and the 50 percent national target by 2030 places a high penalty on untrusted operational evidence.[R06][R07]

Exhibit 1 establishes the industrial context and its evidentiary limits.[R06][R07] It shows why local value retention is a strategic priority in Cameroon, but a macroeconomic target cannot tell a spinning supervisor why roving breaks rose on the afternoon shift or tell a garment director whether an automated fabric-inspection camera is reducing customer claims.[R06][R07][S38] Answering those operational questions requires a governed chain from the shop floor to the management review table.[S05][S38]

1.13 min · 2 sub-steps · 1 exhibit

Data debt starts on the first shift

Step 1 of 3Intro

Related exhibit 09 · chapter 02Decision mapderivedData escalation adds decisions without creating a second management cadence
Emergency containment (Shift / OT)Monthly risk and S&OP gateDaily shift tier-two boardWeekly operations reviewDecision horizon in WP02 cadence (0 to 10) →Cross-domain and risk consequence (0 to 10) →Model rollbackOT safety haltQuarantine holdMissing shift logCross-domain KPI chan…Waiver expiry auditModel release sign-offAccess exception revi…

Read-outModel rollback: Decision horizon in WP02 cadence (0 to 10) 1.2, Cross-domain and risk consequence (0 to 10) 8.4. Quadrant: Emergency containment (Shift / OT)

Method and source

Derived routing matrix mapping eight recurring data and model escalations across decision horizon (x-axis: 0 = immediate shift action, 10 = monthly portfolio review) and cross-domain risk consequence (y-axis: 0 = single-line capture fix, 10 = plant-wide risk or policy gate) into WP02's existing management forums, based on S02, S11 and S23.

Unit: horizon (x) and consequence (y) index (0 to 10). Status: derived. Sources: S02, S11, S23.

Read this exhibit in its chapter ↗
Related exhibit 15 · chapter 04Control mapillustrativeA rule-coverage map reveals where fitness is assumed rather than tested
ValidityCompleten…Consisten…TimelinessUniquenessProduction logs32233Quality inspections21123Maintenance tickets21112Customer orders33224

Read-outProduction logs: Validity 3, Completeness 2, Consistency 2, Timeliness 3, Uniqueness 3 (illustrative coverage score (0 to 4))

Method and source

Illustrative scoring model (0 = untested, 1 = manual spot check, 2 = entry syntax check, 3 = automated gate with quarantine, 4 = versioned gate with full lineage) across four factory record sets and five quality dimensions, derived from ISO/IEC 25012 (S03), ISO/IEC 5259-3 (S04) and W3C DQV (S0401). Values are illustrative and not a measured GFT factory result.

Unit: illustrative coverage score (0 to 4). Status: illustrative. Sources: S03, S04, S0401. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗

1.1 · Introduction

Data debt is the future correction, reconciliation and redesign cost that a factory accumulates when it captures operational numbers with undefined fields, inconsistent identifiers and no named owner.

Exhibit 09, chapter 02: Model rollback

1.2 · Upstream capture defects compound silently across the lifecycle

When initial capture lacks explicit rules for syntax, meaning and provenance , defects multiply across reporting and analytical layers.

Exhibit 09, chapter 02: Model rollback

1.3 · Informal spreadsheet workarounds mask structural gaps

In the early phases of GFT’s Cameroon textile programme, manual spreadsheets and shift logs serve as the starting system of record .

Exhibit 15, chapter 04: Production logs

1.1 · the bodyThe film above follows these sub-steps.

Data debt is the future correction, reconciliation and redesign cost that a factory accumulates when it captures operational numbers with undefined fields, inconsistent identifiers and no named owner.[S01][S02][S18] Sculley and colleagues showed that real-world machine-learning systems incur heavy ongoing maintenance costs because models depend on unstable upstream data feeds, undeclared consumers and improvised correction scripts.[S18] In a factory, that obligation starts on the first shift when an operator writes a bundle count on a clipboard, a technician logs a fault in a chat message or a supervisor edits a spreadsheet formula to force weekly output to match the packing list.[S01][S18][S38]

1.2 Upstream capture defects compound silently across the lifecycle

1.2

When initial capture lacks explicit rules for syntax, meaning and provenance, defects multiply across reporting and analytical layers.[S01][S09][S19] Sambasivan and colleagues studied high-stakes artificial-intelligence deployments and defined data cascades as compounding events caused by upstream data problems that produce negative downstream consequences.[S19] Among the high-stakes AI practitioners they interviewed, 92 percent reported experiencing at least one data cascade, noting that such defects were typically invisible at capture, delayed in impact and avoidable through deliberate data practices.[S19] That 92 percent figure describes the interviewed sample of high-stakes AI practitioners rather than a prevalence estimate for manufacturing firms or small and medium-sized enterprises (SMEs), yet the mechanism it identifies operates directly on factory floors.[S19] Treating data entry as clerical overhead rather than engineered measurement hides upstream omissions until a management decision or model fails in production.[S04][S19]

¶ 02 · 4 sources

92 percent reported experiencing at least one data cascadeS19

S01S09S19S04

Consider how an unowned capture defect propagates through a garment plant, as traced in the illustrative sequence of Exhibit 2.[S18][S19] Suppose a sewing line loses forty minutes of output because a batch of dyed fabric arrives from finishing with uneven shade across the roll width, forcing operators to re-sort cut panels at the line feeder (an illustrative shop-floor scenario). If the line tally sheet offers only two downtime checkboxes, mechanical breakdown and operator absence, the clerk ticks mechanical breakdown to avoid leaving a mandatory field blank (illustrative). That forced misclassification corrupts every downstream stage.[S18][S19]

¶ 03 · 2 sourcesExhibit 02

S18S19

As Exhibit 2 illustrates, the error does not correct itself.[S18][S19] At the second node, the link between the sewing stoppage and the upstream fabric lot disappears because the tally sheet records only the sewing line number.[S08][S09] At the third node, the weekly key performance indicator (KPI) calculation charges the lost forty minutes against equipment availability under ISO 22400-2 time elements rather than material starvation or quality hold.[S38] At the fourth and fifth nodes, an analyst training a predictive-maintenance classifier on twelve months of logs ingests those mislabelled stoppages as mechanical failures.[S04][S18][S19] At the sixth node, management approves spare-parts expenditure for sewing heads while the dye-lot shade problem remains untouched.[S18][S19] What Exhibit 2 cannot establish is the exact frequency of such errors in a given mill before an audit; rather, it shows why ISO/IEC 5259-3 requires data-quality management across the full analytics and machine-learning lifecycle rather than as a late cleaning step.[S04][S19]

¶ 04 · 6 sources

…against equipment availability under ISO 22400-2 time elements rather than material starvation or quality…S38

Exhibit 02

S18S19S08S09S38S04

1.3 Informal spreadsheet workarounds mask structural gaps

1.3

In the early phases of GFT's Cameroon textile programme, manual spreadsheets and shift logs serve as the starting system of record. Structured manual logs are an appropriate choice when capital and connectivity are constrained, provided those sheets enforce field definitions, identifier stability and version control.[S01][S04][S16] Data debt arises when workbooks mutate privately across shifts: a morning supervisor inserts a column, an afternoon supervisor merges cells for a split order and a clerk pastes values over formulas.[S01][S09][S18] Reconciling those files at month-end consumes engineering hours needed for process improvement, and any dashboard built on top inherits their contradictions.[S18][S0101]

¶ 05 · 6 sources

S01S04S16S09S18S0101

1.43 min · 2 sub-steps · 1 exhibit

Disconnected logs fracture one production event

A manufacturing plant is a physical system in which material, machines, people and orders interact simultaneously, yet most small factories record those interactions in separate silos.[S05][S08] When a disruption occurs on the floor, it leaves partial footprints in three or four departmental logs that cannot be joined without manual investigation.[S05][S08][S0101]

1.5 One sewing stoppage produces four irreconcilable accounts

1.5

Consider a single operational event reconstructed across four typical factory logs: the sewing-line hourly board, the maintenance technician's note, the quality inspector's defect sheet and the commercial order tracker (an illustrative reconstruction grounded in IEC 62264-1 integration boundaries and GS1 EPCIS 2.0 visibility events).[S05][S08] Suppose an overlock machine on Line B begins skipping stitches at 10:12 on a Tuesday while running a cotton polo-shirt order.[S05][S08]

¶ 02 · 2 sources

…B begins skipping stitches at 10:12 on a Tuesday while running a cotton polo-shirt…S05, S08

S05S08

  1. The line supervisor's hourly sheet records output only on the clock hour, noting that Line B produced 45 garments between 10:00 and 11:00 against an illustrative target of 80 garments, with a note saying "machine trouble" and no asset identifier or exact stop timestamp.[S05][S38]
  2. The maintenance technician's log records a repair on asset OVL-14 from 10:25 to 10:50 for a worn looper, without recording which line OVL-14 was mounted on or which order was interrupted.[S05][S08]
  3. The quality inspector's sheet logs 18 rejected polo shirts under style text "Navy Polo" during the morning shift for seam skip, without recording the bundle identifier, machine identifier or whether the 18 pieces went to rework or scrap.[S08][S38]
  4. The commercial order spreadsheet shows Customer Order ORD-2026-114 short by 18 pieces at packing two days later, logging "sewing short-ship" with no link to OVL-14 or the morning quality hold.[S05][S08]
List · 3 sources

S05S38S08

Exhibit 3 contrasts these four departmental fragments with the unified record structure required by enterprise-control integration and visibility-event standards.[S05][S08][S38]

¶ 03 · 3 sourcesExhibit 03

S05S08S38

Exhibit 03RegisterderivedDisconnected shop-floor logs split one stoppage into four irreconcilable records
Record source
Line hourly sheet
Time grain
Clock hour (10:00 to 11:00)
Object identifier
Line B only
Recorded outcome
35-unit shortfall
Missing link (S05, S08, S38)
No asset ID, lot ID or exact stop duration

Read-outRecord source: Line hourly sheet. Time grain: Clock hour (10:00 to 11:00). Object identifier: Line B only. Recorded outcome: 35-unit shortfall. Missing link (S05, S08, S38): No asset ID, lot ID or exact stop duration

Open the full register (5 rows)
Line hourly sheetClock hour (10:00 to 11:00)Line B only35-unit shortfallNo asset ID, lot ID or exact stop duration
Maintenance noteRepair window (10:25 to 10:50)Machine OVL-14Looper replacedNo line assignment, wait time or order ID
Quality tally sheetMorning shift aggregateStyle description text18 seam-skip defectsNo bundle ID, machine ID or rework vs scrap state
Order progress trackerPacking date (two days later)Order ORD-2026-11418-unit short-shipNo link to quality hold or machine fault event
Governed spine eventEvent + ingestion timestampsLine B + OVL-14 + Lot + OrderState transitions + 18 rework/scrapReconciles time, object, location and business step
Method and source

Derived comparison applying IEC 62264-1 enterprise-control interface domains (S05), GS1 EPCIS 2.0 visibility event dimensions (S08) and ISO 22400-2 KPI time and quantity elements (S38) to a single shop-floor stoppage.

Unit: record attributes captured. Status: derived. Sources: S05, S08, S38.

As Exhibit 3 shows, none of the four logs is falsified, yet the factory cannot reconstruct the event from them.[S05][S08] The maintenance note shows 25 minutes of active repair (10:25 to 10:50), whereas the line lost 38 minutes between the stop at 10:12 and restart clearance at 10:50 (illustrative timestamps).[S38] Because the 13-minute wait from 10:12 to 10:25 is unrecorded in maintenance and merged into a clock hour on the line sheet, management cannot separate technician response delay from active wrench time, nor can quality prove whether the 18 defective pieces came from OVL-14 just before 10:12.[S08][S38] What Exhibit 3 does not prescribe is the transport protocol or database engine; Chapter 3 specifies the vocabulary contract and Chapter 5 the minimum architecture.[S05][S07][S08]

¶ 01 · 4 sources

The maintenance note shows 25 minutes of active repair (10:25 to 10:50)S38 · illustrative

Exhibit 03

S05S08S38S07

1.6 Interface standards and visibility events supply the missing grammar

1.6

Two international standards explain how a small team can repair these broken links without buying a monolithic software suite.[S05][S08] First, IEC 62264-1 (the ISA-95 standard) defines models and terminology for the interfaces between enterprise business systems and manufacturing operations and control systems.[S05] It organises work schedules, production performance, equipment, material lots and personnel into explicit interface domains so that an order identifier and a machine identifier meet at a defined boundary.[S05]

¶ 02 · 2 sources

IEC 62264-1 (the ISA-95 standard) defines models and terminology for the interfaces between enterprise…S05

S05S08

Second, the GS1 EPCIS 2.0 standard enables disparate applications to create and share visibility event data within and across enterprises.[S08] Rather than overwriting a status cell, an EPCIS-aligned event records what object or lot was involved, when the event occurred and was captured, where it happened down to the line or station, and why it occurred under a defined business step and disposition.[S08] Adopting that four-part event grammar even in initial structured sheets links the stoppage, repair, quality hold and order variance into one inspectable chain.[S05][S08][S09]

¶ 03 · 3 sources

the GS1 EPCIS 2.0 standard enables disparate applications to create and share visibility event…S08

S08S05S09

1.72 min · 2 sub-steps · read with a related exhibit

Small teams need decision rights more than platforms

When production, quality and finance numbers conflict in a weekly meeting, management is often tempted to buy a dashboard tool or an enterprise resource planning (ERP) module.[S02][S34][S0101] Software procurement cannot fix an accountability vacuum.[S02][S23] If nobody holds the right to decide whether reworked garments count inside hourly output, a new platform merely displays the dispute faster and at higher cost.[S02][S38]

1.8 Role assignment precedes tool selection

1.8

ISO 8000-150:2022 specifies the key considerations for organisations establishing roles and responsibilities for data-quality management.[S02] Its core principle is organisational: data quality improves only when specific roles are accountable for defining data requirements, monitoring conformance and executing corrections.[S02] Similarly, the NIST Cybersecurity Framework 2.0 states that governance activities are critical for incorporating risk management into broader enterprise strategy.[S23] A factory must therefore assign who owns domain meaning, who stewards daily capture quality and who holds technical custody before comparing software vendors.[S02][S23]

¶ 02 · 2 sources

ISO 8000-150:2022 specifies the key considerations for organisations establishing roles and responsibilities for data-quality managementS02

S02S23

In a small factory, assigning decision rights does not create a separate bureaucracy.[S02][S0101] NIST's smart-manufacturing programme observes that a typical SME cannot afford a dedicated data-analytics specialist on staff and that commercial tools remain difficult to integrate with shop-floor routines.[S0101] Governance must therefore sit inside existing operating roles: the production manager owns output and time definitions, the quality lead owns defect taxonomies and dispositions, the maintenance lead owns asset hierarchies and fault codes, and the commercial lead owns order and lot identifiers.[S02][S05][S38] Chapter 2 formalises this six-role charter with conflict-of-interest rules where one person holds multiple roles.[S02][S11][S23]

¶ 03 · 6 sources

S02S0101S05S38S11S23

1.9 A named internal champion determines whether adoption survives

1.9

Paper role descriptions fail if daily adoption is left to external consultants.[S37] In a May 2025 World Bank case study of SME digital technology adoption in Viet Nam, firms that successfully adopted the platform assigned an internal point person who championed adoption within the firm.[S37] That champion coordinates training, follows up on late logs, escalates cross-domain definition disputes and protects line stewards' time.[S02][S37]

¶ 04 · 2 sources

S37S02

Designers must also avoid assuming that integrated enterprise software already exists on the ground.[S34] In the OECD's June 2026 Western Balkans Enterprise Survey, tools supporting integrated operations, such as cloud computing, ERP and customer relationship management (CRM) systems, were used by only 10 to 20 percent of surveyed SMEs, with supplier-customer systems even rarer.[S34] That 10 to 20 percent finding describes the surveyed Western Balkans SME sample rather than a Cameroon estimate, but it warns against assuming that an SME possesses a clean ERP backbone ready for machine learning.[S34][S42] As SCITEPRESS Industry 4.0 research notes, the starting technical infrastructure and target degree of automation strongly govern MLOps complexity.[S42]

¶ 05 · 2 sources

were used by only 10 to 20 percent of surveyed SMEsS34

S34S42

Note · 3 sources

S02S37S38

Key figures from chapter 14 · Exhibit 63Key figuresderivedSeven capability measures replace a vanity count of dashboards
  • Owner + steward1. Ownership closureShare of active datasets and models with signed roles and closed actions (S02)
  • Pass + quarantine2 & 3. Contracts and quality gatesKPI dictionary coverage (S38) plus first-pass validity and quarantine resolution (S04, S1402)
  • Tested RPO / RTO4. Recovery proofMeasured isolated backup restore and offline buffer replay without duplicates (S26, S33)
  • End-to-end audit5. Lineage reproducibilitySampled KPIs and model candidates rebuilt from raw events and snapshots (S09, S15)
  • Runbook closure6. Alert diagnosis qualityAnomalies diagnosed to feed fault or drift before any retraining approval (S17, S21)
  • Baseline minus cost7. Net decision valueVerified operational gain net of preparation and support, with zero worker harm (S18, S36)

Read-out1. Ownership closure: Owner + steward. Share of active datasets and models with signed roles and closed actions (S02)

Method and source

Derived monthly measurement pack synthesised from S02, S04, S15, S17, S26, S36 and S1402. Tile 2 pairs semantic contract coverage (Measure 2) and quality-gate resolution (Measure 3) so all seven capabilities are surfaced without universal numeric targets before site baseline.

Unit: derived monthly governance and MLOps capability pack. Status: derived. Sources: S02, S04, S15, S17, S26, S36, S1402.

Read this exhibit in its chapter ↗

1.103 min · 1 sub-steps · read with a related exhibit

Reuse turns preparation from a tax into infrastructure

Related · chapter 095 paragraphs step it

Related exhibit 39 · chapter 09ReconciliationillustrativeLifecycle cost can reverse an apparent pilot return
-50050100100Grossbenefit-42Dataprep-20Integration-16Labelling-12Validation-14Monitoring-8Retraining-12Netlifecycle

Read-outGross benefit: total 100. Running total 100 illustrative index (gross benefit = 100)

Method and source

Illustrative reconciliation from gross annual operational benefit (100 index units) to net lifecycle contribution (-12 index units) for a custom history-dependent model with bespoke pipeline preparation. Cost categories derive from S18 and the upper-bound data-processing warning in S39; values are illustrative arithmetic, not a universal factory ratio.

Unit: illustrative index (gross benefit = 100). Status: illustrative. Sources: S18, S39. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗
1.10 · Introduction · paragraph 1 of 5

When a factory treats data as a by-product of isolated projects, every new question triggers another custom extraction, cleaning script and identifier mapping.[S10][S39][S0101] One effort builds a sheet for overall equipment effectiveness (OEE), a second pulls defect tallies for a camera trial and a third extracts utility bills for carbon reporting, each redefining shift boundaries, rework and good output.[S10][S38][S39]

1.11 Application-specific pipelines multiply preparation costs

In a 2025 NIST workshop report on AI and scaled data sharing in semiconductor manufacturing, manufacturers reported that data processing for a single application can reach up to 70 percent of total cost.[S39] That 70 percent figure is a manufacturer-reported upper-bound warning from semiconductor fabrication rather than a universal SME average, yet it highlights the penalty of building separate pipelines for every application.[S39] NIST's smart-manufacturing research confirms that substantial time goes into data acquisition and formatting because analytics tools use proprietary interfaces and specialised data formats.[S0101]

The alternative is to capture each operational event once with governed identity, timestamps, units and quality states, catalogued under a standard metadata model such as the W3C Data Catalog Vocabulary (DCAT) Version 3, and publish controlled views to multiple consumers.[S08][S09][S10][S0102] Across the GFT white-paper library, one governed record spine feeds four downstream uses without re-cleaning the floor logs:

  • Line performance and OEE management (WP02, WP15): uses validated availability, cycle-time and good-count events under ISO 22400-2 definitions for shift reviews and energy intensity.[S38]
  • Automated visual inspection (WP03): uses canonical defect codes, roll identifiers and inspector dispositions to test computer-vision cameras against manual inspection baselines (where inherited literature records manual accuracy of 60 to 70 percent against computer vision above 90 percent across more than 40 defect types).[R29][S04][S08]
  • Demand and order forecasting (WP04): uses clean order, dispatch and short-ship records once history accumulates, preventing stockouts from distorting demand signals.[R27][S04][S43]
  • Traceability and carbon accounting (WP05, WP16): uses lot genealogy and utility intervals across iterative data-quality improvement cycles.[S08][S09][S41]

1.122 min · 3 sub-steps · read with a related exhibit

Trust includes safety, legality and worker dignity

A factory record is not trustworthy simply because its schema validates.[S22][S29][S30] An architecture that disrupts machine reliability, exposes control networks, collects excessive personal telemetry on workers or breaches national data-protection law creates severe operational exposure.[S22][S29][S31]

1.13 Operational technology safety overrides data convenience

1.13

Factory systems interact with rotating machinery, dyeing vessels, boilers and switchgear.[S22] NIST Special Publication 800-82 Revision 3 guides operational technology (OT) security around performance, reliability and safety requirements.[S22] Data collection and model inference must remain subordinate to physical process safety: no gateway, broker or model may write unvalidated commands into safety-critical control loops, and any data-layer failure must leave machines operating safely under local control.[S22][S33] During network outages, edge devices use local store-and-forward buffering to retain event records without disturbing shop-floor control.[S22][S33]

¶ 02 · 2 sources

NIST Special Publication 800-82 Revision 3 guides operational technology (OT) security around performanceS22

S22S33

1.14 Data minimisation and human review protect the workforce

1.14

Shop-floor logs often touch operator sign-ins, bundle scans, skills matrices and camera feeds.[S29][S30] Two rules govern these records.[S29][S30] First, Regulation (EU) 2016/679 (GDPR, Recital 39) states the data-minimisation principle: personal data should be adequate, relevant and limited to what is necessary for the stated purpose.[S29] Line balance, availability, yield and energy metrics require station, line, shift or role identifiers rather than personal identity; where personal records are required (such as high-voltage maintenance certification), access follows least privilege under NIST SP 800-53 Revision 5.[S25][S29][S38]

¶ 03 · 4 sources

access follows least privilege under NIST SP 800-53 Revision 5S25, S29, S38

S29S30S25S38

Second, Principle 5.5 of the International Labour Office (ILO) 1997 code of practice states that decisions concerning a worker should not be based solely on automated processing of that worker's personal data.[S30] While the ILO code is non-binding guidance, GFT enforces it as an operating rule: no productivity score, defect tally or camera output may automatically trigger discipline, pay changes or dismissal without informed human review of material, machine and line context.[S11][S30]

¶ 04 · 2 sources

Principle 5.5 of the International Labour Office (ILO) 1997 code of practice states that…S30

S30S11

1.15 Cameroonian statutory compliance requires qualified local counsel

1.15

Factories in Cameroon must also address Law No. 2024/017 of 23 December 2024 relating to personal data protection in Cameroon.[S31] Section 19(1) of Law No. 2024/017 provides that the processing of personal data shall be subject to prior authorisation by the Personal Data Protection Authority.[S31]

¶ 05 · 1 source

…must also address Law No. 2024/017 of 23 December 2024 relating to personal data…S31

S31

Note · 2 sources

S31S29

1.162 min · 2 sub-steps · 1 exhibit

GFT's position is to govern the record before scaling the model

Step 1 of 6Order ledger (baseline)

Exhibit 04 · derivedFour admission tests separate a data spine from a data pile

Well-kept silo (standardise meaning)Governed data spine (admit to analytics)Data pile (fix ownership and capture)Unverified contract (enforce quality and backup)Ownership and meaning (Tests 1-2) →Quality and recovery (Tests 3-4) →Order ledger (baselin…Production logs (base…Quality sheets (basel…Maintenance notes (ba…Utility/carbon logs (…Spine admission gate…
Well-kept silo(standardise meaning)Governed data spine (admitto analytics)Data pile (fix ownershipand capture)Unverified contract(enforce quality and back…Ownership and meaning (Tests 1-2) →Quality and recovery (Tests 3-4) →Order ledger (baselin…Production logs (base…Quality sheets (basel…Maintenance notes (ba…Utility/carbon logs (…Spine admission gate…

Order ledger (baseline)

Order ledger (baseline): Ownership and meaning (Tests 1-2) 6.5, Quality and recovery (Tests 3-4) 4.5. Quadrant: Unverified contract (enforce quality and backup) · derived

Across GFT’s Cameroon textile programme, the sequencing principle is strict: capture cleanly from the first shift, establish one governed vocabulary and admit machine learning only after records pass explicit readiness gates.

Production logs (baseline)

Production logs (baseline): Ownership and meaning (Tests 1-2) 4, Quality and recovery (Tests 3-4) 3. Quadrant: Data pile (fix ownership and capture) · derived

Quality sheets (baseline)

Quality sheets (baseline): Ownership and meaning (Tests 1-2) 3.5, Quality and recovery (Tests 3-4) 2.5. Quadrant: Data pile (fix ownership and capture) · derived

Maintenance notes (baseline)

Maintenance notes (baseline): Ownership and meaning (Tests 1-2) 2, Quality and recovery (Tests 3-4) 2. Quadrant: Data pile (fix ownership and capture) · derived

Utility/carbon logs (baseline)

Utility/carbon logs (baseline): Ownership and meaning (Tests 1-2) 3, Quality and recovery (Tests 3-4) 4. Quadrant: Data pile (fix ownership and capture) · derived

Spine admission gate (target)

Spine admission gate (target): Ownership and meaning (Tests 1-2) 8, Quality and recovery (Tests 3-4) 8. Quadrant: Governed data spine (admit to analytics) · derived

Method and source · Exhibit 04

Derived readiness framework scoring five factory record domains across two composite axes: Ownership and Meaning (Tests 1 and 2, from S02 and S05; 0 = unowned free text, 10 = contracted owner, IDs and KPI formula) and Quality, Lineage and Recovery (Tests 3 and 4, from S01, S09 and S26; 0 = unchecked/unbacked, 10 = gated, provenance-linked and restoration-tested). Point coordinates represent an illustrative pre-governance factory baseline versus the minimum admission threshold (score >= 7 on both axes) required to enter the governed spine.

Unit: derived governance readiness score (0 to 10 scale). Status: derived. Sources: S01, S02, S05, S09, S26.

1.16 · the bodyExhibit 04 above; its figures are illustrative where marked.

Across GFT's Cameroon textile programme, the sequencing principle is strict: capture cleanly from the first shift, establish one governed vocabulary and admit machine learning only after records pass explicit readiness gates.[S02][S04][S16]

1.17 Four admission tests separate a data spine from a data pile

1.17

GFT translates international standards into four admission tests that separate a governed data spine from an uncurated data pile:[S01][S02][S05][S09][S26]

¶ 02 · 5 sources

S01S02S05S09S26

  1. Test 1: Named ownership and decision rights (ISO 8000-150, NIST CSF 2.0). Every domain has one accountable business owner who approves purpose, definitions, access and retention, supported by a line steward.[S02][S23]
  2. Test 2: Explicit operational meaning and contract (IEC 62264-1, GS1 EPCIS 2.0, ISO 22400-2). Every record uses stable site, line, asset, lot and order identifiers, separates event time from ingestion time, and binds KPIs to versioned formulas and units.[S05][S08][S38]
  3. Test 3: Enforced quality gates and lineage (ISO 8000-1, ISO/IEC 25012, ISO/IEC 5259-3, W3C PROV-O). Capture and ingestion check validity, completeness, consistency, timeliness and uniqueness; quarantine failures; flag missing or estimated states; and preserve provenance to raw events.[S01][S03][S04][S09]
  4. Test 4: Tested recoverability and portability (NIST SP 800-82 Rev 3, CISA #StopRansomware, edge buffering). Raw records, schemas, master data and KPI logic have offline encrypted backups with tested restoration and local store-and-forward buffering during disconnection.[S22][S26][S33]

Exhibit 4 maps five factory record domains across two composite axes derived from these four tests: ownership and meaning (Tests 1 and 2) on the horizontal axis, and quality, lineage and recovery (Tests 3 and 4) on the vertical axis.[S01][S02][S05][S09][S26]

¶ 03 · 5 sources

ownership and meaning (Tests 1 and 2) on the horizontal axisS01, S02, S05, S09, S26

Exhibit 04

S01S02S05S09S26

In Exhibit 4, a typical pre-governance baseline leaves production, quality, maintenance and utility logs in the lower-left "Data pile" quadrant while order ledgers sit near the middle (illustrative baseline coordinates on the derived 0 to 10 rubric).[S01][S02][S05] Training models on lower-left records imports unowned definitions and unflagged missingness directly into predictions.[S04][S18][S19] Reaching the upper-right "Governed data spine" gate (8.0, 8.0) requires passing all four admission tests during an on-site audit using the checklists in Chapters 2 through 8.[S01][S02][S09][S26]

1.18 Vision and forecasting remain subordinate to record discipline

1.18

These four tests also govern the sequence between bought computer vision (WP03) and demand forecasting (WP04):[S04][S16][S44]

¶ 05 · 3 sources

S04S16S44

  • Purchased fabric and garment vision (WP03): Pre-trained optical inspection can be trialled early because detection relies on image physics rather than years of order history, but it still requires a canonical defect taxonomy (Test 2), local validation against human inspectors on Cameroonian weaves and shades (Test 3), human-set thresholds (NIST AI RMF 1.0) and a manual inspection fallback (Test 4).[R29][S04][S11][S22]
  • Demand and order forecasting (WP04): Although McKinsey's The State of Fashion 2025 reports that AI at scale can cut forecast errors by 20 to 50 percent and inventory costs by 35 to 40 percent, those results depend on multi-year stockout-corrected order histories.[R27] A new or restructuring mill must first accumulate governed order, dispatch and short-ship records and compare any forecaster against a simple moving-average baseline before release (Chapter 9).[R12][S04][S43][S44]

1.192 min · 3 sub-steps · read with a related exhibit

The paper judges success by better decisions

An industrial data spine is judged by whether operational decisions improve, not by gigabytes stored, MQTT message rates or dashboard counts.[S07][S36][S43]

1.20 Cycle time from abnormal event to verified action is the primary test

1.20

World Bank guidance on MSME digitalisation stresses embedding monitoring and evaluation throughout design and implementation to track impact and improve learning.[S36] On the shop floor, the primary operational measure is the cycle time from an abnormal physical event to a verified corrective action across five steps:[S10][S36][S38]

¶ 02 · 3 sources

S36S10S38

  1. Detection latency: elapsed time from physical deviation to timestamped capture.[S08][S38]
  2. Validation and contextualisation: automated checking and linking to order, lot and asset identifiers.[S04][S05][S08]
  3. Diagnostic clarity: provenance showing whether the fault lies in machine, material, method or data feed.[S09][S17][S21]
  4. Action execution: bounded response by the named owner or supervisor.[S02][S11][S15]
  5. Verified effect: confirmation in subsequent records that the KPI returned to its baseline band.[S36][S38]

1.21 Technical accuracy without operational fit fails the lifecycle gate

1.21

In manufacturing data mining, the CRISP-DM lifecycle runs through six phases: business understanding, data understanding, data preparation, modelling, evaluation and deployment.[S43] A model with high offline accuracy in phase four still fails in evaluation or deployment if alerts arrive after fabric is cut, if operators cannot act on the output or if data-preparation and maintenance costs exceed gross savings.[S18][S39][S43][S0101] When resources, skills, costs or expected benefits are not met, postponing or stopping an AI project is a valid governance decision.[S44]

¶ 01 · 5 sources

S43S18S39S0101S44

1.22 How the fourteen chapters of WP14 build the spine

1.22

The fourteen chapters of this paper build that governed chain across four parts:

¶ 02
  • Part I (Chapters 1 to 4) governs meaning before scale: assigning decision rights (Chapter 2), defining the operational vocabulary and contracts (Chapter 3) and enforcing quality gates and PROV-O lineage (Chapter 4).[S02][S03][S04][S05][S08][S09][S38]
  • Part II (Chapters 5 to 8) builds the minimum durable spine: separating capture, raw evidence and curated views alongside WP18 (Chapter 5), governing time, identity, genealogy and state (Chapter 6), embedding OT safety, privacy and Cameroonian legal screening (Chapter 7), and proving offline continuity, restoration and portability (Chapter 8).[S06][S10][S15][S22][S25][S26][S27][S29][S30][S31][S32][S33]
  • Part III (Chapters 9 to 12) controls models as production change: enforcing model admission and baselines (Chapter 9), reproducible training and registries (Chapter 10), human-threshold validation and shadow release with rollback (Chapter 11), and diagnostic drift monitoring (Chapter 12).[S11][S13][S15][S16][S17][S21][S43][S44]
  • Part IV (Chapters 13 and 14) proves value and scales deliberately: measuring behavioural adoption and net lifecycle benefit (Chapter 13) and sequencing an 18-month gated roadmap with seven monthly capability metrics (Chapter 14).[S18][S35][S36][S39][S42][S44]

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.

52 sources · 361 citation marks on this pageMost cited: S05, 25 times

Grade AGrade BGrade CKnot size: citations on this page

All 52 records shown

R06 · Grade C · inherited record

Cameroon Trade Hub

Inherited evidence R06

About 95 percent of cotton fibre exported raw against 5 percent processed locally; industrialisation target of 50 percent local processing.

Publication date unrecorded. Inherited source-text record. The original publication has not been independently reopened for this web edition.

Chapter source notes

S01 International Organization for Standardization. 2022.

S02 International Organization for Standardization. 2022.

S09 World Wide Web Consortium. 2013-04-30.

S26 CISA, MS-ISAC, NSA and FBI. 2023.

S19 Association for Computing Machinery, CHI 2021. 2021.

S0101 National Institute of Standards and Technology. 2025-03-26.

S05 International Electrotechnical Commission. 2013.

S08 GS1 AISBL. 2022.

S43 Frontiers in Artificial Intelligence. 2021-06-14.

R06 Cameroon Trade Hub. Publication date unrecorded; inherited source-text check.

R07 Ecofin Agency. Publication date unrecorded; inherited source-text check.

S38 International Organization for Standardization. 2014.

S04 ISO/IEC. 2024.

S15 Google Cloud. 2024-08-28.

S36 World Bank. 2023.

R12 Business in Cameroon. Publication date unrecorded; inherited source-text check.

R11 Business in Cameroon; MMI News. Publication date unrecorded; inherited source-text check.

R09 Ecofin Agency. Publication date unrecorded; inherited source-text check.

R10 Ecofin Agency. Publication date unrecorded; inherited source-text check.

S18 Advances in Neural Information Processing Systems. 2015.

S16 Microsoft Learn, Azure Architecture Center. 2026-06-03.

S07 OASIS Open. 2019-03-07.

S34 OECD. 2026-06-26.

S23 National Institute of Standards and Technology. 2024-02-26.

S11 National Institute of Standards and Technology. 2023-01-26.

S37 World Bank. 2025-05-20.

S42 SCITEPRESS, IN4PL 2022. 2022.

S10 National Institute of Standards and Technology. 2016-02-23.

S39 National Institute of Standards and Technology. 2025.

S0102 World Wide Web Consortium. 2024-08-22.

R29 MDPI; industry inspection literature. Publication date unrecorded; inherited source-text check.

R27 McKinsey, The State of Fashion 2025. Publication date unrecorded; inherited source-text check.

S41 GHG Protocol, World Resources Institute and World Business Council for Sustainable Development. 2013.

R14 WageIndicator. Publication date unrecorded; inherited source-text check.

R15 wage.is. Publication date unrecorded; inherited source-text check.

R16 WageIndicator. Publication date unrecorded; inherited source-text check.

R32 Wise; XE. Publication date unrecorded; inherited source-text check.

S22 National Institute of Standards and Technology. 2023.

S29 European Parliament and Council of the European Union. 2016-04-27.

S30 International Labour Office. 1997.

S31 Presidency of the Republic of Cameroon. 2024-12-23.

S33 Microsoft. 2024-06-10.

S25 National Institute of Standards and Technology. 2020-12-10.

S03 ISO/IEC. 2008.

S44 The Journal of Technology Transfer, Springer Nature. 2024-07-27.

S17 Microsoft Learn, Azure Machine Learning. 2026-01-27.

S21 arXiv, author manuscript of an IEEE Transactions on Knowledge and Data Engineering article. 2020-04-13.

S06 OPC Foundation. 2025-10-22.

S27 National Institute of Standards and Technology. 2025.

S32 European Parliament and Council of the European Union. 2023-12-13.

S13 ISO/IEC. 2023.

S35 OECD. 2022-11-21.

Keep the thread · chapter 01 of 14

Chapter 02 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

02Part I: Govern meaning before scale

Named decision rights keep a small data team accountable

A workable governance model fits into existing factory roles and makes every definition, exception and release somebody's explicit decision.

  • 2.1Every critical domain receives one accountable owner
  • 2.5Ownership, stewardship and custody remain distinct
  • 2.9Line stewards need time and escalation authority
  • 2.12Definition changes follow a controlled decision
Reading time
29 min
Exhibits
5
Sections
7
Continue to chapter 02
Continue the threadChapter 02 · Named decision rights keep a small data team accountable

Find a thread.

Type to search.