Skip to content
GREEN FUTURETECH.
Explore

Research libraryWP14

WP14 · Draft web edition · as of 2026-10-30

The Industrial Data Spine

Data governance and lightweight MLOps for small factory teams

EX 02 · 5. Miscalibrated spare-part alert. From 4. Biased training snapshot (Corrupted ground truth). Leads to 6. Misallocated maintenance spend (Unchallenged threshold).
Chapters
14
Exhibits
63
Findings
10
Minutes
385

Each weft is one exhibit's own data, normalised; each warp group is a chapter. The probe reads the exhibit's own value where it crosses. Procedural visualisation, not a measurement.

Operate the evidence first

Operate 4 exhibits from 4 chapters before reading a word.

The weft the probe was reading, lifted out of the cloth: the same exhibit at full size, with the probe as its cursor. Choose a weft, step through it, compare its series.

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-out5. Miscalibrated spare-part alert. From 4. Biased training snapshot (Corrupted ground truth). Leads to 6. Misallocated maintenance spend (Unchallenged threshold).

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.

Read this exhibit in its chapter ↗
Exhibit 17FlowderivedLineage reconstructs a KPI and a model prediction on separate paths
Raw event logQuality gatev1.2Curated eventstoreKPI calculationv2.0Shift managementreviewDataset snapshotPipeline andmodel v1.1Dispositiondecision

Read-outRaw event log. Starting point. Leads to Quality gate v1.2.

Method and source

Derived provenance graph linking raw visibility event, versioned quality gate, curated record, KPI formula execution, shift review, frozen dataset snapshot, pipeline run and model decision, based on W3C PROV-O (S09), Google Cloud MLOps lineage requirements (S15) and W3C PROV Primer (S0403).

Unit: . Status: derived. Sources: S09, S15, S0403.

Read this exhibit in its chapter ↗
Exhibit 37ScheduleillustrativeA recovery exercise proves the whole chain, not only the backup
0501001502001. Safety check & baseline freeze2. Sever WAN & verify local capture3. Inject poison message & reboot edge4. Restore offline backup to sandbox5. Reconnect WAN & drain local queue6. Reconcile restored & live KPIs7. Log defects, owners & sign-off

Read-out1. Safety check & baseline freeze: from 0 to 20 (elapsed exercise minutes)

Method and source

Illustrative 240-minute factory continuity and recovery drill sequence derived from contingency testing guidance in S0801, periodic incident-response exercises in S27, and offline backup restoration testing in S26. Timings are explicitly illustrative planning durations for a half-day drill, not measured GFT operational benchmarks.

Unit: elapsed exercise minutes. Status: illustrative. Sources: S26, S27, S0801. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗
Exhibit 50Decision mapderivedHigher consequence demands more independent release authority
Over-governed low riskMandatory multi-role gateProportionate steward checkUncontrolled release riskOperational consequence (0 to 10) →Approval independence (0 to 10) →Advisory order planni…Quality vision assistWorker-affecting anal…Control-connected OT

Read-outAdvisory order planning: Operational consequence (0 to 10) 2.8, Approval independence (0 to 10) 3.5. Quadrant: Proportionate steward check

Method and source

Derived consequence-to-authority matrix based on S11 human threshold authority, S14 integrated AI risk management, S22 OT safety constraints, S23 ERM governance, and S30 worker-data protection. Coordinates represent ordinal governance tiers rather than empirical probabilities.

Unit: derived governance score (0 to 10 scale). Status: derived. Sources: S11, S14, S22, S23, S30.

Read this exhibit in its chapter ↗

The paper's argument

One argument, woven across 14 chapters.

Chapter read-out · hover or focus a thread

Factory directors and operations managers in small and mid-sized manufacturers, Quality, maintenance, industrial-engineering and sustainability leads, IT and OT practitioners responsible for factory systems, Data analysts and machine-learning practitioners working with constrained teams, Technology vendors and integrators serving emerging-market factories, Development-finance and technical-assistance teams assessing digital readiness

0126 min · 4 exhibits

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.

  1. 01 / 05The thesis

    A small factory needs one governed chain from operational event to decision and model, with named ownership, explicit meaning, quality gates, reversible releases and measured value, rather than an enterprise data department.

    14 chapters · 4 parts · 385 minutes

    Prepared for: Factory directors and operations managers in small and mid-sized manufacturers, Quality, maintenance, industrial-engineering and sustainability leads, IT and OT practitioners responsible for factory systems, Data analysts and machine-learning practitioners working with constrained teams, Technology vendors and integrators serving emerging-market factories, Development-finance and technical-assistance teams assessing digital readiness

  2. 02 / 05Part I · Govern meaning before scale

    Cameroon's local-processing ambition requires factories whose daily records can support operating, customer and sustainability decisions. GFT's programme evidence base, prepared 31 January 2024, records about 95 percent of cotton fibre exported raw and about 5 percent processed locally, against a 50 percent by 2030 target. These entries were not refreshed in 2026 and their original source dates are unresolved (R06, R07).

    Part I · chapters 01 to 04 · 111 minutes · 19 exhibits

  3. 03 / 05Part II · Build the minimum durable spine

    This paper argues for an industrial data spine, not a large data department. The spine is one governed chain from event capture and operational meaning to quality control, model release, monitoring and value review. It assigns decision rights, defines identifiers and KPIs, preserves lineage, and keeps defined data services available during network interruption …

    Part II · chapters 05 to 08 · 110 minutes · 18 exhibits

  4. 04 / 05Part III · Control models as production change

    … without providing power or protective safety. Drawing on 44 opened sources, the paper distinguishes raw events from curated records, separates transport from semantics, and places quality gates before training. Lightweight MLOps adds only controls a small team can sustain: versioned data and code, an experiment and model register, human-set thresholds, shadow release, rollback, …R01S28

    Part III · chapters 09 to 12 · 112 minutes · 18 exhibits

  5. 05 / 05Part IV · Prove value and scale deliberately

    … drift monitoring and practised incident response. Security, privacy and Cameroonian legal screening shape the design. Value is measured against an operating baseline and net of preparation, integration and maintenance. The closing illustrative 18-month roadmap sets decision gates and seven capability measures. GFT's Cameroon textile programme supplies the starting point: capture cleanly from the first shift, then earn the right to model.R09R14

    Part IV · chapters 13 to 14 · 52 minutes · 8 exhibits

The cloth seen from above

Inspect any of the 63 exhibits before accepting the conclusion.

Weaving draft · 14 chapters × 63 exhibits

One column per chapter, one knot per exhibit; the glyph is its type family, as on the chips above. Select a knot to open the exhibit below.

Exhibit 01 · chapter 01 · Key figures

01
02
03
04
05
06
07
08
09
10
11
12
13
14
Exhibit 01 · chapter 01Key figuressourcedLocal-processing ambition raises the cost of untrusted evidence
  • 95%Raw cotton fibre exportedApproximate inherited sector baseline (R06; original date unrecorded)
  • 5%Cotton fibre processed locallyApproximate inherited sector baseline (R06; original date unrecorded)
  • 50%National processing targetSND30 local-processing target by 2030 (R07; policy target, not realised output)

Read-outRaw cotton fibre exported: 95%. Approximate inherited sector baseline (R06; original date unrecorded)

Method and source

Inherited GFT programme evidence base prepared 31 January 2024. R06 and R07 were not refreshed in 2026 and their original publication dates are unrecorded. Figures describe sector-level baseline and policy ambition, not a current GFT factory measurement or causal productivity claim.

Unit: percent of cotton fibre. Status: sourced. Sources: R06, R07.

Read this exhibit in its chapter ↗

Interlude · findings against chapters

10 findings, each argued across the paper.

Finding 01 of 10

Governance begins with decision rights and a named internal champion, not with a platform purchase.S02S23S37

Finding 02 of 10

A shared operational vocabulary must precede integration because transport protocols do not supply business meaning.S05S06S07S38

Finding 03 of 10

Data quality is a lifecycle discipline, and upstream defects can compound into delayed downstream failures.S01S03S04S19

Finding 04 of 10

Lineage from source record to dataset, model and decision is the minimum evidence needed for reproducibility and audit.S09S15

Finding 05 of 10

Small teams should adopt MLOps in stages, with automation earned by operational need rather than copied from large technology firms.S16S20S42

Finding 06 of 10

Monitoring should open a diagnosed response, not trigger indiscriminate automatic retraining.S17S21S27

Finding 07 of 10

OT safety, least privilege, tested recovery and worker-data limits belong in the initial design.S22S25S26S29S30

Finding 08 of 10

Offline buffering and portable records protect continuity better than an assumption of permanent connectivity or vendor access.S32S33S05S08

Finding 09 of 10

The business case must count data preparation, integration and maintenance, then compare net value with a pre-model baseline.S18S36S39S43

Finding 10 of 10

GFT's manual data spine is the right starting system, but scale should follow passed ownership, quality, recovery and value gates.S02S04S16S44

Chapter 02 · strongest recurrence of finding 01 · Named decision rights keep a small data team accountable

Cell strength is the recurrence of each finding's key terms in each chapter's text, computed from this web edition and scaled to the strongest chapter. It is a reading guide, not a citation.

Evidence stays attached

Source quality is part of the argument.

Every knot on the edge is one of the 375 records the chapters cite, sorted by grade. The counters filter them; select a record to read it and to light the chapters that cite it. A grade describes the supplied evidence record, not independent validation by the website; missing references are excluded.

All 375 records shown

c01-S01 · Grade A

International Organization for Standardization

ISO 8000-1:2022: Data quality, Part 1: Overview

The series defines which characteristics of data are relevant to data quality, specifies requirements applicable to those characteristics, and provides guidelines for improving data quality.

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

Open the recorded source ↗

Cited inc01-S01: 1 chapter

0102030405060708091011121314

Keep the definitions stable

Use the same term for the same boundary.

45 terms, each with one definition for the whole paper. The punched row shows the chapters whose text uses the term.

Canonical model
A shared representation of important entities and events that reduces repeated translation between applications while preserving source detail.
Completeness
The degree to which required records and fields are present at the grain needed for a decision.
Concept drift
A change in the underlying data relationship or distribution over time that can invalidate a model's previous mapping.
Counterfactual
The credible account of what would have happened without the model or data intervention, used to assess claimed benefit.
Data contract
A versioned promise describing a dataset's schema, semantics, ownership, timing, quality expectations and compatibility rules.
Data custodian
The technical role responsible for operating storage, access, backup, recovery and related controls without owning business meaning.
Data domain
A bounded subject area such as production, quality, maintenance, orders, people or sustainability used to assign accountability.
Data governance
The decision rights, accountability, policies and controls used to manage data throughout its lifecycle.
Data leakage
The use of information during training or evaluation that would not legitimately be available for the intended prediction, inflating apparent performance.
Data lineage
The traceable path from source records through transformations to a dataset, KPI, model or decision.
Data minimisation
Limiting personal data to what is adequate, relevant and necessary for a stated processing purpose.
Data owner
The role accountable for a dataset's purpose, definition, access, quality expectations and retention.
Data quality
The fitness of data for a stated purpose, assessed through explicit characteristics and measures rather than a general claim of cleanliness.
Data steward
The role that performs recurring definition, quality, correction and coordination work close to a business domain.
Dataset snapshot
An immutable, identified version of a training, validation or test dataset with its manifest, quality state and lineage.
Edge computing
Processing close to machines or work activities so capture, inference or control can continue with limited dependence on remote services.
EPCIS
A GS1 standard for creating and sharing visibility event data within and across enterprises.
Event time
The time at which the represented operational event occurred, as distinct from when its record arrived or was processed.
Feature
A model input derived from source data under a documented definition, transformation, time window and missing-value rule.
Human oversight
Informed human authority to set thresholds, interpret limits, intervene, override and stop a system according to consequence.
Idempotency
The property that processing the same event again produces no additional unintended effect, enabling safe retry and replay.
Industrial data spine
The governed chain of ownership, identifiers, events, quality controls, storage, models and decisions that connects factory work to reusable evidence.
Ingestion time
The time at which a system received an event record, used to diagnose delay, replay and late arrival.
ISA-95
The enterprise-control integration framework, standardised in the IEC 62264 series, used to model interfaces and terminology between business and manufacturing systems.
KPI dictionary
The governed register of each indicator's purpose, formula, inputs, unit, time basis, grain, exclusions, owner and version.
Least privilege
Granting a person or process only the access required for its assigned task, for only as long as needed.
Master data
Relatively stable records describing entities such as assets, lines, styles, operations and units that give transactional events their context.
Metadata
Structured information that describes a dataset or artefact, including meaning, origin, version, quality, rights and retention.
MLOps
The practices and controls used to develop, validate, release, monitor and retire machine-learning systems reliably in their operating context.
Model registry
A controlled record of model artefacts, versions, evidence, approval and lifecycle status.
Model retirement
The controlled withdrawal of a model from use while preserving the records needed to explain its historical outputs and decisions.
MQTT
A client-server publish-subscribe messaging transport that requires separate payload schemas and operational semantics.
OPC UA
OPC Unified Architecture, an industrial interoperability framework that includes information modelling and secure communication.
Operational technology
Hardware and software that monitor or control physical devices and processes, where performance, reliability and safety are primary constraints.
Provenance
Evidence about where a record or artefact came from, which processes changed it and which agents were responsible.
Quarantine
A controlled state that isolates failed records from normal consumption while preserving them for diagnosis, correction and reprocessing.
Recovery point objective
The maximum targeted interval of data loss after disruption, set by business consequence and verified through recovery evidence.
Recovery time objective
The targeted time to restore a service or record set after disruption, verified through an exercised recovery procedure.
Rollback
A tested return to a previously approved model, configuration or operating procedure after a release is suspended.
Schema
The formal structure of a record, including fields, types, required values and constraints.
Shadow deployment
Operating a model on live inputs without allowing its outputs to affect decisions, used to collect release evidence.
Store-and-forward
Durable local buffering of records during disconnection, followed by controlled synchronisation when communication returns.
System of record
The authoritative source for a defined class of information, with other copies explicitly subordinate or derived.
Timeliness
The degree to which data arrive and become usable within the period required by the decision.
Validity
The degree to which a record conforms to its defined types, domains, formats and rules.
01 / 45

Recurs inreading guide, not a citation

Canonical model: 1 of 14 chapters use the term

Cut to length

Plan the reading, then take the paper with you.

Chapters 01 to 02 fit in 60 minutes, with 5 minutes to spare.

Start chapter 01 · 2 chapters in 60 min

WP14 · Draft web edition

The Industrial Data Spine

Chapters
14
Exhibits
63
Findings
10
Minutes
385

Cut length 2 chapters · 55 min

The PDF has passed its publication gates: 276 rendered A4 pages, 2.1 MB.

Download the verified PDF
Continue the thread · next paperWP15 · Utilisation Decides

Issued by Green Future Tech Limited, Hong Kong SAR. This research is not investment, legal or tax advice. Illustrative calculations require local validation before an operating or financing decision.

Find a thread.

Type to search.