Research libraryEdge to Dashboard
Chapter 08 of 14 · Part III · Draft web edition
Two systems can exchange packets and still misunderstand production, so the architecture must define information, state, events and asset meaning separately.
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.
Read-out
Derived architecture stack mapping each standard's stated scope in the opened specifications to its assigned layer in GFT's reference architecture, framed within ISA-95 enterprise-to-control responsibilities (S01).
Unit: . Status: derived. Sources: S01, S04, S05, S07, S15, S40.
A connected textile factory does not achieve interoperability merely because an edge gateway delivers packets to a broker. Interoperability exists only when the machine controller, local historian, operations service and dashboard interpret every exchanged value under one grammar.[S01][S04] Two systems can share an active socket, exchange valid JavaScript Object Notation (JSON) documents under RFC 8259 rules, and still corrupt a production record because one side reports cumulative cycles since power-on while the other records good garments completed in the shift.[S0804][S08] In GFT's architecture, the semantic contract precedes the connection. Before any broker topic is subscribed, the factory specifies five layers of meaning: industrial object and service semantics via OPC Unified Architecture (OPC UA), constrained transport via Message Queuing Telemetry Transport (MQTT), session state and metric validity via Sparkplug, durable asset descriptions via the Asset Administration Shell (AAS), and visibility events via Electronic Product Code Information Services (EPCIS).[S04][S05][S40][S07][S15]
This separation is vital for industrialisation in Cameroon, where the inherited baseline records roughly 95 percent of cotton fibre exported raw and about 5 percent processed locally, against a 50 percent local-processing target by 2030.[R06][R07] Factories closing that gap cannot assume homogeneous machinery or uninterrupted links when 93.3 percent of surveyed Cameroonian firms report electrical outages in the 2024 World Bank Enterprise Survey.[S32] When power returns or a brownfield sewing line connects beside a newer dyeing range, the data spine must reconcile replayed messages, machine states, work-in-process (WIP) bundles and asset capabilities without human guesswork.[S32][S40] GFT's Cameroon textile programme starts with a spreadsheet system of record to build baseline discipline across production, quality, maintenance and resource logs. Replacing spreadsheets with automated capture is safe only when a governed contract preserves the meaning, units, denominators and provenance of every event.[S08][S41]
8.1
Related · chapter 037 paragraphs step it
Read-out
Derived qualitative placement from ISA-95 functional scope (S01), IEC 62264 Level 3/4 boundaries (S02), NIST OT performance and reliability guidance (S17) and IEC functional safety independence (S23). X-axis scores organisational scope from single machine point (1) to multi-site enterprise (10); Y-axis scores timing criticality from monthly review (1) to immediate hardware protection (10).
Unit: ordinal architectural scale (1 to 10). Status: derived. Sources: S01, S02, S17, S23.
Read this exhibit in its chapter ↗Interoperability fails first when engineers confuse the wire protocol that moves bytes with the information model that defines what those bytes mean. Legacy fieldbus integrations often expose a programmable logic controller (PLC) or gateway as a flat array of holding registers.[S09] In MODBUS, communication follows a request and reply model where services are specified by function codes operating on register addresses.[S09] At the sensor level, IO-Link cyclically transmits process data without interference from on-request parameters, commands and events, protecting deterministic scanning while leaving factory context outside the cyclic byte stream.[S10] Mapping register 40012 directly to a dashboard tile traps its meaning (whether raw needle strokes, completed seam cycles, or total pieces including rework) inside one custom script.[S04][S09]
When meaning is buried inside point-to-point scripts, every new application multiplies maintenance. If the maintenance tool, huddle board, historian and enterprise resource planning (ERP) connector parse controller addresses independently, four codebases must be updated whenever a recipe or counter scale changes, diverging silently whenever one script filters warm-up cycles and another does not.[S01][S02][S08] ISA-95 Part 1 prevents this by defining how physical assets are organised and specifying the information shared between control and enterprise functions.[S01] IEC 62264-1 reinforces this boundary by describing the manufacturing operations management domain at Level 3 and transactions within Level 3 and with Level 4.[S02] Neither standard lets an enterprise dashboard guess a Level 1 controller's memory layout.[S01][S02]
OPC UA resolves this at the machine boundary. Under OPC 10000-1, OPC UA is layered to isolate its core design from computing technology and network transport.[S04] Separating the information model from serialisation and transport allows an edge node or controller to expose a graph of typed objects, variables, methods and references that remain identical across client-server sessions or publish-subscribe messages.[S04][S0802] Instead of an anonymous integer, an OPC UA server on a spinning frame or cutting table exposes a typed MachineModule object linked to its parent WorkCentre in the ISA-95 hierarchy, carrying engineering units, valid ranges, source timestamps and quality codes.[S01][S04]
Model-to-transport separation becomes operational in OPC 10000-14, which defines the OPC UA PubSub model.[S0802] OPC UA PubSub complements client-server sessions by distributing data and events from an OPC UA source to interested observers in a device network or analytics system.[S0802] A factory thus retains OPC UA object semantics over brokered constrained links.[S04][S0802] At the edge gateway, the OPC UA address space acts as the normalisation layer: brownfield MODBUS registers and IO-Link cyclic data are read once, checked against hardware diagnostics, and mapped into typed OPC UA nodes before leaving the work centre.[S04][S09][S10]
Where a legacy controller cannot host an OPC UA server, explicit interaction metadata still applies. The World Wide Web Consortium (W3C) Web of Things Architecture 1.1 describes how an industrial edge device collects selected controller data for remote monitoring or preventive maintenance.[S14] The W3C Web of Things Thing Description 1.1 specification defines a formal model providing interactions from a small vocabulary so diverse devices and applications interoperate.[S0801] Whether normalised into OPC UA objects or W3C Thing Descriptions, GFT's rule is invariant: no raw register address, untyped byte array or unscaled count crosses the edge-node boundary into the data spine.[S04][S14][S0801]
As shown in Exhibit 33, the five core standards in GFT's data spine do not compete for the same job; each governs a distinct layer of meaning within the ISA-95 enterprise-to-control hierarchy.[S01][S04][S05][S07][S15][S40]
Exhibit 33 shows why no single protocol solves factory interoperability.[S04][S05][S40] An integration built solely on MQTT has message transport but lacks a machine object model, session-state conventions, asset submodels and business-event semantics.[S05] Conversely, local OPC UA client-server browsing alone lacks lightweight brokered session management and cross-enterprise visibility grammar.[S04][S15][S40] Exhibit 33 is a structural responsibility map rather than a performance benchmark: it establishes which specification owns each semantic concern, while site acceptance testing must verify actual gateway implementation.[S17][S30]
8.4
In many digitalisation projects, MQTT is mistakenly treated as an interoperability standard that unifies factory data. The OASIS standard for MQTT Version 5.0 defines its role accurately: MQTT is a client-server publish-subscribe transport protocol whose lightweight design, small code footprint and low bandwidth demand suit constrained Machine-to-Machine (M2M) and Internet of Things (IoT) contexts.[S05][S0803] Those transport properties suit a textile mill where gateways share constrained wireless links or buffer telemetry across intermittent wide-area connections.[S05][S32][S33] However, transport efficiency is not semantic interoperability. MQTT treats the payload as an opaque byte sequence and places no domain restriction on topic names or message bodies.[S05][S0803]
The OASIS standard for MQTT Version 5.0 defines its role accurately
S05, S0803
When a factory deploys an MQTT broker without a semantic contract above it, every publisher invents a dialect. One developer publishes JSON under RFC 8259 rules to factory/line1/loom3/speed containing {"val": 420}, a second publishes a string to garoua/spinning/ring02/rpm, and a third publishes a binary integer to cameroon/plantA/dyeing/temp without stating whether the unit is degrees Celsius or tenths of a degree.[S0804][S05] All three use valid MQTT packets, and the broker routes them without error.[S05] Yet every consumer (historian, alert service, OEE engine and energy dashboard) must maintain custom parsing code per topic, guess missing units, and assume whether timestamps reflect sensor capture or broker arrival.[S08][S13][S40]
This pattern turns a decoupled broker into hidden point-to-point dependencies. Whenever a publisher renames a JSON key from val to value or changes polling from 10 seconds to 60 seconds, downstream KPI calculations fail silently.[S08][S0804] ISO 22400-2 specifies that manufacturing KPIs are presented through their formula, corresponding elements, time behaviour and unit or dimension.[S08] Because bare MQTT carries none of those attributes natively, an ungoverned broker cannot ensure that two dashboards compute ISO 22400-2 indicators on a compatible basis.[S05][S08]
Even transport-level MQTT features can mislead personnel if their operational semantics are ungoverned. In MQTT Version 5.0, retained messages are sent to a session when it first subscribes, while a Will Message is published by the server after a network connection is closed when the connection is not closed normally.[S0803] If an integrator sets the retain flag on a production topic without session tracking, a supervisor opening a dashboard at 08:00 during a power outage receives the retained value published at 06:15 before power failed, mistaking a two-hour-old speed reading for live production.[S32][S40][S0803]
GFT therefore prohibits bare, uncontracted MQTT topics in the production spine. Where MQTT provides transport, the architecture binds five specifications onto every connection: a governed topic namespace, a schema-versioned payload, explicit units and quality flags, deterministic session state via Sparkplug or OPC UA PubSub, and named producer and consumer ownership under change control.[S04][S05][S24][S40][S0802]
8.7
1. Controller state (PLC or IO-Link)
1. Controller state (PLC or IO-Link). Starting point. Leads to 2. OPC UA object (Type, unit, quality) (Hardware read & type binding). · illustrative
To bridge bare MQTT transport and operational state awareness, the Eclipse Sparkplug Specification 3.0.0 defines an MQTT topic namespace, payload structure and session-state management approach for the Industrial Internet of Things (IIoT)…
2. OPC UA object (Type, unit, quality)
2. OPC UA object (Type, unit, quality). From 1. Controller state (PLC or IO-Link) (Hardware read & type binding). Leads to 3. Edge state rule (De-bounce & timestamp) (Local state evaluation). · illustrative
3. Edge state rule (De-bounce & timestamp)
3. Edge state rule (De-bounce & timestamp). From 2. OPC UA object (Type, unit, quality) (Local state evaluation). Leads to 4. Sparkplug message (Topic & session) (Report by exception or buffer). · illustrative
4. Sparkplug message (Topic & session)
4. Sparkplug message (Topic & session). From 3. Edge state rule (De-bounce & timestamp) (Report by exception or buffer). Leads to 5. Production event (ISA-95 & AAS link) (Session and context join). · illustrative
5. Production event (ISA-95 & AAS link)
5. Production event (ISA-95 & AAS link). From 4. Sparkplug message (Topic & session) (Session and context join). Leads to 6. EPCIS visibility event (Business step) (Batch or bundle transition), 7. Governed KPI tile (ISO 22400 formula) (Windowed KPI calculation). · illustrative
6. EPCIS visibility event (Business step)
6. EPCIS visibility event (Business step). From 5. Production event (ISA-95 & AAS link) (Batch or bundle transition). End point. · illustrative
7. Governed KPI tile (ISO 22400 formula)
7. Governed KPI tile (ISO 22400 formula). From 5. Production event (ISA-95 & AAS link) (Windowed KPI calculation). End point. · illustrative
Illustrative transformation sequence showing how a physical controller signal is normalised, transported with session state, contextualised into a production event, exported as an EPCIS visibility event and aggregated into an ISO 22400 KPI (S04, S08, S15, S40).
Unit: . Status: illustrative. Sources: S04, S08, S15, S40. Illustrative figures are teaching examples, not measured factory results.
8.7 · the bodyExhibit 34 above; its figures are illustrative where marked.
To bridge bare MQTT transport and operational state awareness, the Eclipse Sparkplug Specification 3.0.0 defines an MQTT topic namespace, payload structure and session-state management approach for the Industrial Internet of Things (IIoT), meeting the requirements of supervisory control and data acquisition (SCADA) and human-machine interface (HMI) solutions.[S40] Sparkplug organises MQTT traffic around a deterministic namespace (spBv1.0/group_id/message_type/edge_node_id/[device_id]), allowing every participant to discover edge nodes, devices, metric definitions and session transitions.[S40]
the Eclipse Sparkplug Specification 3.0.0 defines an MQTT topic namespace
S40
Sparkplug makes connection state an explicit part of data semantics. When a Sparkplug edge node connects to the broker, it registers a Death Certificate (NDEATH) via MQTT's Will Message mechanism and publishes a Birth Certificate (NBIRTH), followed by Device Birth Certificates (DBIRTH) for attached devices.[S40][S0803] The birth certificate declares all metrics exposed by that node or device, with initial values, data types, units and sequence numbers, enabling report-by-exception (NDATA and DDATA) updates thereafter.[S40]
When an edge node loses power or connectivity unexpectedly, the broker publishes the registered NDEATH message, and Sparkplug specifies that all metrics in the previous associated NBIRTH and all DBIRTH messages in that session under that edge node are now STALE.[S40][S0803] In a Cameroonian mill facing electrical outages or wireless drop-outs, a dashboard or historian following Sparkplug rules immediately marks affected machine metrics STALE upon receiving NDEATH or DDEATH, preventing operators from reading a frozen value as live.[S32][S40]
Sparkplug also specifies how edge nodes coordinate with a Primary Host Application across outages. When the Primary Host Application publishes a STATE message denoting that it is online, the edge node resumes live publishing and flushes historical data stored locally while offline.[S40] This store-and-forward flush complements local persistence, such as the industrial IoT energy-monitoring pattern where an edge server stores metre data locally before computing nine derived parameters.[S29][S40]
MISSING rather than interpolated.[S31][S32][S40]The progression from a controller register to an enterprise visibility event and governed KPI is shown in Exhibit 34, tracing how each standard adds semantic structure.[S04][S08][S15][S40]
As Exhibit 34 shows, a physical signal at Node 1 is not yet a business event at Node 6 or a KPI at Node 7.[S04][S08][S15] Hardware diagnostics are checked at the OPC UA boundary (Node 2), mechanical bounce or idle cycling is filtered at the edge rule (Node 3), session continuity is verified via Sparkplug (Node 4), Level 3 context joins the observation (Node 5), and only then does the spine emit an EPCIS visibility event (Node 6) or update an ISO 22400-2 KPI tile (Node 7).[S02][S04][S08][S15][S40] Because Exhibit 34 is an illustrative sequence, it defines required logical transformations rather than claiming a fixed software latency.
Interlude · the cloth half-woven
Woven: sections 8.0 to 8.7Still to weave: 8.10 to 8.16
Read-out
GFT arithmetic from World Bank Enterprise Surveys Cameroon 2024 Country Profile (S32). Outage-incidence gap against Sub-Saharan Africa: 93.3 percent minus 69.7 percent equals 23.6 percentage points. Outage-incidence gap against lower-middle-income economies: 93.3 percent minus 55.0 percent equals 38.3 percentage points. Monthly frequency excess: 10.4 minus 6.9 equals 3.5 outages per typical month. Compares all surveyed firms, not textile factories.
Unit: percentage points and monthly events. Status: derived. Sources: S32.
Read this exhibit in its chapter ↗8.10
Live telemetry streams and session certificates report what an asset is doing now, not what the asset is. Every machine, metre, camera cell and sensor has slowly changing master attributes: nameplate data, serial number, hierarchy location, rated power, calibration dates and maintenance manuals.[S01][S07] Plattform Industrie 4.0's Reference Architecture Model Industrie 4.0 (RAMI 4.0) organises these aspects across hierarchy levels, life-cycle value stream and architectural layers.[S03] Embedding static nameplate metadata inside every MQTT packet wastes bandwidth and creates conflicting copies across edge scripts, whereas leaving metadata in paper binders prevents dashboards from querying a frame's spindle count, kilowatt rating or calibration date.[S05][S07][S08][S40]
The Industrial Digital Twin Association (IDTA) addresses this through the Specification of the Asset Administration Shell (AAS) Part 1: Metamodel (IDTA 01001-3-0-1), defining the Administration Shell structure for meaningful exchange of asset and Industrie 4.0 component information across value networks.[S07] An AAS assigns each asset a globally unique identifier and organises its attributes into standardised submodels (digital nameplate, technical data, documentation and operational data), referencing external semantic dictionary concepts.[S03][S07]
GFT derives a strict integration rule from combining the AAS metamodel with the ISA-95 hierarchy and Sparkplug sessions: high-frequency telemetry carries only the stable asset identifier, metric identifier, value, timestamp and quality state, while durable asset descriptions reside in the AAS registry.[S01][S07][S40] Each Sparkplug DBIRTH certificate includes an immutable reference (aas_global_asset_id and aas_submodel_version) so historians, KPI services and maintenance tools join telemetry to AAS submodels on demand.[S07][S08][S40]
In a brownfield textile mill where older spinning, weaving or sewing machines predate Industrie 4.0 standards, engineers construct a repository-hosted AAS instance during the Phase 0 audit.[S07][S30][S35] As the W3C Web of Things Thing Description 1.1 specification notes, a description instance can be hosted externally when a device has resource restrictions or is retrofitted.[S0801] GFT uses a W3C Thing Description or OPC UA object to document the retrofitted machine's live edge interface, and registers an AAS instance in the factory repository for its nameplate, electrical rating, calibration record and ISA-95 work-centre assignment.[S01][S04][S07][S0801]
Where master data characteristics are exchanged, ISO 8000-120:2016 specifies requirements for representing and exchanging provenance of characteristic master data.[S41] In GFT's architecture, ISO 8000-120 governs provenance for characteristic master data in asset and material records (such as rated capacity, calibration factors or cotton fibre-length characteristics), while configuration changes follow ISO/IEC 27001 change control and KPI lineage follows GFT's historian rules.[S08][S24][S41]
8.13
Just as static asset descriptions remain separate from telemetry, continuous process waveforms remain separate from discrete material-flow events. A spindle-vibration waveform, dye-bath temperature curve and motor current trace are periodic observations about equipment state.[S04][S29] Consuming a cotton bale lot at an opening line or completing collar attachment on a garment bundle at an inspection station are discrete visibility events about physical objects moving through a process.[S15][S25]
GS1's EPCIS Standard, Release 2.0, enables applications to create and share visibility event data within and across enterprises across four dimensions:[S15]
readPoint (scanner or antenna station) and bizLocation (finishing buffer or warehouse) after the event.[S01][S15]bizStep (inspecting, packing, shipping or transforming), disposition (conformant, non-conformant or quarantined), and bizTransaction links.[S15]To trace how lint from northern Cameroonian ginning plants is spun into yarn, woven or knitted into fabric, dyed, cut and sewn into garments, raw MQTT telemetry is insufficient.[R03][S05][S15] An EPCIS chain links TransformationEvent records (bale lots to yarn, fabric rolls to cut bundles), ObjectEvent records (sewing and inspection steps) and AggregationEvent records (garments packed into cartons).[S15] Where European Union buyers require product disclosures, Regulation (EU) 2024/1781 defines a digital product passport as product-specific data specified in the applicable delegated act and accessible electronically through a data carrier.[S39] An internal EPCIS graph linked to batch and resource logs provides export-ready evidence without claiming that raw telemetry is a regulatory passport.[S15][S39]
Textile research confirms both the value and pitfalls of shop-floor object tracking: a denim case study showed radio-frequency identification (RFID) supporting work-in-process tracking, and manufacturing execution system (MES) research describes systematic shop-floor RFID deployment for real-time production data.[S25][S28] Wireless-sensor and RFID review literature stresses that node time synchronisation and spectrum sharing are vital to protect data integrity and avoid uncertain readings.[S31]
On a sewing line, a raw RFID antenna detection is not automatically a valid EPCIS event: an overhead reader may detect the same bundle tag 40 times in three minutes in an input tray or pick up a stray aisle reflection.[S15][S25][S31] GFT therefore places a three-step event-qualification state machine between raw detections and the EPCIS store:[S15][S25][S28]
Read-out
Derived qualitative positioning from opened specifications: X-axis scores built-in semantic and structural richness (from raw byte transport to typed metamodels); Y-axis scores operational reach (from local machine/edge scope to multi-enterprise value networks). Positions reflect specification scope in S04, S05, S07, S15 and S40, not performance benchmarks.
Unit: derived architectural scope index (0 to 10). Status: derived. Sources: S04, S05, S07, S15, S40.
Exhibit 35 shows why no single standard is a complete factory operating system.[S04][S05][S07][S15][S40] MQTT V5.0 (x = 2.0, y = 4.2) is a lightweight transport pipe without domain semantics.[S05] Sparkplug 3.0.0 (x = 5.5, y = 4.5) adds topic, payload and session state for SCADA and IIoT telemetry.[S40] OPC UA (x = 8.6, y = 4.0) provides deep machine and plant object modelling, while AAS (x = 8.8, y = 8.5) and EPCIS 2.0 (x = 7.8, y = 9.0) extend structured asset and event semantics across partner networks.[S04][S07][S15] These derived coordinates reflect specification scope rather than throughput benchmarks.
8.16
Raw PLC triggers
Raw PLC triggers: total 12,400. Running total 12,400 illustrative garment cycle counts per 8-hour shift · illustrative
To combine OPC UA , MQTT , Sparkplug, AAS, EPCIS and ISO 22400-2 without creating five silos, GFT uses a canonical data model and versioned interface contract .
Bounce & dry-run filter
Bounce & dry-run filter: removes 310. Running total 12,090 illustrative garment cycle counts per 8-hour shift · illustrative
Maintenance mode filter
Maintenance mode filter: removes 240. Running total 11,850 illustrative garment cycle counts per 8-hour shift · illustrative
Outage replay dedupe
Outage replay dedupe: removes 380. Running total 11,470 illustrative garment cycle counts per 8-hour shift · illustrative
Inline rework routed
Inline rework routed: removes 260. Running total 11,210 illustrative garment cycle counts per 8-hour shift · illustrative
Inline scrap rejected
Inline scrap rejected: removes 110. Running total 11,100 illustrative garment cycle counts per 8-hour shift · illustrative
Verified good units
Verified good units: total 11,100. Running total 11,100 illustrative garment cycle counts per 8-hour shift · illustrative
The method behind it: Method.
Illustrative worked-example reconciliation: 12,400 raw triggers minus 310 mechanical bounce/dry runs, minus 240 maintenance-mode cycles, minus 380 duplicate outage-replay packets (S40), minus 260 rework and 110 scrap dispositions (S15) equals 11,100 verified good units for ISO 22400 GoodQuantity (S08). Not a measured GFT factory result.
Unit: illustrative garment cycle counts per 8-hour shift. Status: illustrative. Sources: S08, S15, S40. Illustrative figures are teaching examples, not measured factory results.
8.16 · the bodyExhibit 38 above; its figures are illustrative where marked.
To combine OPC UA, MQTT, Sparkplug, AAS, EPCIS and ISO 22400-2 without creating five silos, GFT uses a canonical data model and versioned interface contract.[S04][S05][S07][S08][S15][S40] The canonical model does not replace those standards with a custom protocol; it defines the identity keys, timestamp rules, unit dictionaries and mappings that connect each representation across the spine.[S01][S06]
Without a canonical model, linking $N$ shop-floor sources to $M$ applications requires up to $N \times M$ translation scripts: for 6 equipment families and 5 applications, an illustrative mesh requires 30 pairwise translators. Mapping each source once into a governed canonical contract and each consumer once from that contract reduces the illustrative adapter count from 30 paths to $6 + 5 = 11$ governed interfaces.
for 6 equipment families and 5 applications
illustrative
This structure rests on three international standards:
enterprise / site / area / work_centre / work_unit) and respects IEC 62264-1 Level 3 and Level 4 boundaries.[S01][S02]An example of this contract for a sewing-line event appears in Exhibit 36, where all ten attributes are versioned as one unit.[S04][S24][S40]
Exhibit 36 shows why versioning applies to the full operational contract rather than only JSON syntax.[S04][S24][S40] Changing the trigger from raw cycles to inspected good pieces alters the ISO 22400-2 element to GoodQuantity, requiring a major version increment (v2.0.0), ISO/IEC 27001 change approval and an explicit historian cutover record.[S08][S24] Exhibit 36 is an illustrative template rather than a live mill record.
v2.1.0 to v2.1.1): Documentation clarifications leaving payload structure, units, state logic and KPI formulas unchanged.[S24]v2.1.0 to v2.2.0): Backwards-compatible optional metrics (such as ambient_humidity_pct in a birth certificate) that leave existing calculations intact.[S08][S40]v2.1.0 to v3.0.0): Changes to units, state transitions, KPI denominators or quality rules, requiring shadow validation and version tagging in the historian.[S08][S24][S30]The arithmetic reconciliation from Part A is charted in Exhibit 38, showing each deduction between raw PLC triggers and verified ISO 22400-2 GoodQuantity.[S08][S15][S40]
showing each deduction between raw PLC triggers and verified ISO 22400-2 GoodQuantity
S08, S15, S40
As Exhibit 38 shows, bounce and maintenance filters derive from OPC UA state modelling, replay deduplication derives from Sparkplug session rules, and rework or scrap deductions derive from EPCIS disposition binding and ISO 22400-2 definitions.[S04][S08][S15][S40] Although the counts are illustrative, the accounting structure applies to every discrete textile line: without state, session and disposition contracts, raw counters distort performance.[S08]
and rework or scrap deductions derive from EPCIS disposition binding and ISO 22400-2 definitions
S04, S08, S15, S40
Interoperability in the connected textile factory is neither a single vendor's platform licence nor an unmonitored broker connection. By assigning industrial object modelling to OPC UA, constrained transport to MQTT, session state to Sparkplug, durable asset descriptions to the Asset Administration Shell, and visibility event sharing to EPCIS within an ISA-95 and IEC 62264 frame, the factory establishes one governed language from edge to dashboard.[S01][S02][S04][S05][S07][S15][S40] The next chapter examines how the historian preserves this evidence over time so raw observations, events, KPI versions and corrections remain distinguishable and replayable.
Check the record
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.
36 sources · 326 citation marks on this pageMost cited: S40, 44 times
Grade AGrade BGrade CKnot size: citations on this page
All 36 records shown
R03 · Grade C · inherited record
Inherited evidence R03
Company profile: more than 220,000 cotton producers supported in northern Cameroon; nine ginning plants; two oil mills.
Publication date unrecorded. Inherited source-text record. The original publication has not been independently reopened for this web edition.
R06 · Grade C · inherited record
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.
R07 · Grade C · inherited record
Inherited evidence R07
SND30 restates the 50 percent local-processing target by 2030.
Publication date unrecorded. Inherited source-text record. The original publication has not been independently reopened for this web edition.
c08-S01 · Grade A
Update to ISA-95 Standard Addresses Integration of Enterprise and Manufacturing Control Systems
ANSI/ISA-95.00.01-2025, also known as ISA-95 Part 1, summarizes the scope of the manufacturing operations and control domain, discusses how physical assets of a manufacturing enterprise are organized, lists the functions associated with the interface between control functions and enterprise functions and describes the information shared among these functions.
2025-04-10. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S02 · Grade A
IEC 62264-1:2013: Enterprise-control system integration, Part 1: Models and terminology
IEC 62264-1:2013 describes the manufacturing operations management domain (Level 3) and its activities, and the interface content and associated transactions within Level 3 and between Level 3 and Level 4.
2013-05-22. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S03 · Grade B
RAMI4.0: A reference framework for digitalisation
The three dimensions of RAMI 4.0 are explained and it is shown how RAMI 4.0 unites the most important aspects of Industrie 4.0.
2018-08-09. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S04 · Grade A
OPC-10000-1: OPC Unified Architecture, Part 1: Overview and Concepts
The OPC UA is layered to isolate the core design from the underlying computing technology and network transport.
2025-10-22. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S05 · Grade A
MQTT V5.0 OASIS Standard published
These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
2019-03-07. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S06 · Grade A
ISO 23247-4:2021: Automation systems and integration, Digital twin framework for manufacturing, Part 4: Information exchange
This document identifies technical requirements for information exchange between entities within the reference architecture.
2021-10. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S07 · Grade A
Specification of the Asset Administration Shell Part 1: Metamodel, IDTA 01001-3-0-1
The aim of this document is to define selected specifications of the structure of the Administration Shell to enable the meaningful exchange of information about assets and I4.0 components between partners in a value creation network.
2024-06. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S08 · Grade A
ISO 22400-2:2014: Automation systems and integration, Key performance indicators for manufacturing operations management, Part 2: Definitions and descriptions
The KPIs are presented by means of their formula and corresponding elements, their time behaviour, their unit/dimension and other characteristics.
2014-01. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S09 · Grade A
MODBUS Application Protocol Specification V1.1b3
MODBUS is a request/reply protocol and offers services specified by function codes.
2012-04-26. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S10 · Grade A
IO-Link Interface and System Specification, Version 1.1.4
The Process Data Exchange unit cyclically transmits and receives Process Data without interference from the On-request Data (parameters, commands, and Events).
2024-06. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S12 · Grade A
IEEE 1588-2019: IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems
The protocol supports synchronization accuracy and precision in the sub-microsecond range with minimal network and local computing resources.
2020-06-16. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S13 · Grade A
Network Time Protocol Version 4: Protocol and Algorithms Specification
NTPv4 includes fundamental improvements in the mitigation and discipline algorithms that extend the potential accuracy to the tens of microseconds with modern workstations and fast LANs.
2010-06. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S14 · Grade A
Web of Things Architecture 1.1
An industrial edge device collects selected data from various controllers and makes it available to a cloud backend service, e.g., for remote monitoring via a dashboard or analyzes it for preventive maintenance.
2023-12-05. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S15 · Grade A
EPCIS Standard, Release 2.0
The goal of EPCIS is to enable disparate applications to create and share visibility event data, both within and across enterprises.
2022-06. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S17 · Grade A
NIST SP 800-82 Rev. 3: Guide to Operational Technology Security
This document provides guidance on how to secure operational technology (OT) while addressing their unique performance, reliability, and safety requirements.
2023-09. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S24 · Grade A
ISO/IEC 27001:2022: Information security, cybersecurity and privacy protection, Information security management systems, Requirements
The ISO/IEC 27001 standard provides companies of any size and from all sectors of activity with guidance for establishing, implementing, maintaining and continually improving an information security management system.
2022-10. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S25 · Grade B
An RFID-based tracking system for denim production processes
The most striking result from the case study is that a radio frequency identification application could be successfully implemented to support the tracking and tracing of work in process in denim production processes, an area in which studies about radio frequency identification applications have not been done.
2016-09-05. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S26 · Grade B
Textile Defect Detection Using Artificial Intelligence and Computer Vision: A Preliminary Deep Learning Approach
Data acquired in complex industrial settings are highly susceptible to external variables such as lighting variations and background noise, which can significantly degrade the detection accuracy of machine learning (ML) models [14].
2025-09-18. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S27 · Grade B
Digital and Sustainable Transition in Textile Industry through Internet of Things Technologies: A Pakistani Case Study
Figure 8 illustrates changes in water level, depicting fluctuations that enable the industry to optimize water usage.
2024-06-21. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S28 · Grade B
RFID-enabled real-time manufacturing execution system for mass-customization production
RFID devices are deployed systematically on the shop-floor to track and trace manufacturing objects and collect real-time production data.
2013-04. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S29 · Grade B
Industrial IoT-Based Energy Monitoring System: Using Data Processing at Edge
Once the edge receives the meter’s data, it stores the information in the database server, followed by the data processing method to find nine additional analytical parameters.
2024-09-28. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S30 · Grade B
Six-Sigma Reference Model for Industry 4.0 Implementations in Textile SMEs
The implementation of small pilot projects is recommended to test and validate the effectiveness of selected I4.0 technologies.
2023-08-19. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S31 · Grade B
A Review of IoT Sensing Applications and Challenges Using RFID and Wireless Sensor Networks
Also, time synchronization between the nodes and spectrum sharing techniques are of the utmost importance to ensure the integrity of the data or avoid uncertainty in the sensed data, without consuming all the radio resources [37].
2020-04-28. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S32 · Grade A
Enterprise Surveys: What Businesses Experience, Cameroon 2024 Country Profile
Figure 8 shows the extent to which firms face failures in the provision of electricity as measured by the percent of firms experiencing electrical outages and by the number of power outages.
2025. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S33 · Grade A
Facts and Figures 2024: Mobile network coverage
The largest coverage gap is in Africa, where 14 per cent of the population still does not have access to a mobile broadband network and therefore cannot access the Internet.
2024-11-10. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S35 · Grade A
Industrial Development Report 2020: Industrializing in the digital age
In Ghana, for instance, almost 70 percent of firms surveyed for this report fall in the analog category.
2019. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S39 · Grade A
Regulation (EU) 2024/1781 establishing a framework for the setting of ecodesign requirements for sustainable products
‘digital product passport’ means a set of data specific to a product that includes the information specified in the applicable delegated act adopted pursuant to Article 4 and that is accessible via electronic means through a data carrier in accordance with Chapter III;
2024-06-28. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S40 · Grade A
Sparkplug Specification 3.0.0
The intent and purpose of the Sparkplug Specification is to define an MQTT Topic Namespace, payload, and session state management that can be applied generically to the overall IIoT market sector, but specifically meets the requirements of real-time SCADA/Control HMI solutions.
2022-11-16. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S41 · Grade A
ISO 8000-120:2016: Data quality, Part 120: Master data: Exchange of characteristic data: Provenance
ISO 8000-120:2016 specifies requirements for the representation and exchange of information about the provenance of master data that consists of characteristic data, and supplements the requirements of ISO 8000‑110.
2016-10. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S0801 · Grade A
Web of Things (WoT) Thing Description 1.1
Thing Descriptions provide a set of interactions based on a small vocabulary that makes it possible both to integrate diverse devices and to allow diverse applications to interoperate.
2023-12-05. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S0802 · Grade A
OPC-10000-14: OPC Unified Architecture, Part 14: PubSub
PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
2025-10-22. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S0803 · Grade A
MQTT Version 5.0 OASIS Standard
Will Message: An Application Message which is published by the Server after the Network Connection is closed in cases where the Network Connection is not closed normally.
2019-03-07. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c08-S0804 · Grade A
RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
JSON defines a small set of formatting rules for the portable representation of structured data.
2017-12. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗S01 International Society of Automation. 2025-04-10.
S04 OPC Foundation. 2025-10-22.
S0804 Internet Engineering Task Force and RFC Editor. 2017-12.
S08 International Organization for Standardization. 2014-01.
S05 OASIS Open. 2019-03-07.
S40 Eclipse Foundation. 2022-11-16.
S07 Industrial Digital Twin Association. 2024-06.
S15 GS1 AISBL. 2022-06.
R06 Cameroon Trade Hub. Publication date unrecorded; inherited source-text check.
R07 Ecofin Agency. Publication date unrecorded; inherited source-text check.
S32 World Bank Enterprise Surveys. 2025.
S41 International Organization for Standardization. 2016-10.
S09 Modbus Organization. 2012-04-26.
S10 IO-Link Community. 2024-06.
S02 International Electrotechnical Commission. 2013-05-22.
S0802 OPC Foundation. 2025-10-22.
S14 World Wide Web Consortium. 2023-12-05.
S0801 World Wide Web Consortium. 2023-12-05.
S17 National Institute of Standards and Technology. 2023-09.
S30 MDPI, Sustainability. 2023-08-19.
S0803 OASIS Open. 2019-03-07.
S33 International Telecommunication Union. 2024-11-10.
S13 Internet Engineering Task Force and RFC Editor. 2010-06.
S24 International Organization for Standardization and International Electrotechnical Commission. 2022-10.
S29 MDPI, IoT. 2024-09-28.
S12 IEEE Standards Association. 2020-06-16.
S31 MDPI, Sensors. 2020-04-28.
S03 Plattform Industrie 4.0. 2018-08-09.
S35 United Nations Industrial Development Organization. 2019.
S25 Springer Nature, International Journal of Advanced Manufacturing Technology. 2016-09-05.
R03 SODECOTON. Publication date unrecorded; inherited source-text check.
S39 European Parliament and Council of the European Union, Official Journal of the European Union. 2024-06-28.
S28 Elsevier, Robotics and Computer-Integrated Manufacturing. 2013-04.
S06 International Organization for Standardization. 2021-10.
S26 MDPI, Electronics. 2025-09-18.
S27 MDPI, Applied Sciences. 2024-06-21.
Keep the thread · chapter 08 of 14
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
01Part I: Decisions before devices
GFT starts with the production decisions and infrastructure constraints that a connected architecture must serve, because visualisation alone cannot create trustworthy operating evidence.
02Part I: Decisions before devices
Each connected-factory use case needs an event, an owner, a permitted delay, a fallback and a measurable consequence before any sensor or platform is selected.
03Part I: Decisions before devices
A useful reference architecture assigns each function to a responsibility boundary and information contract before it assigns that function to a product.
04Part II: Capture at the production edge
A value becomes production evidence only when its asset, occurrence time, uncertainty and transformation history remain inspectable.
05Part II: Capture at the production edge
The safest digital retrofit begins by observing equipment through its documented interfaces and proving that acquisition does not alter control timing, protective functions or maintainability.
06Part II: Capture at the production edge
Local inspection earns its place when a valid image becomes a traceable quality decision before the fabric leaves the decision point. Acquisition, persistence and an approved fallback matter as much as inference speed.
07Part II: Capture at the production edge
The connected factory must lose remote services before it loses local evidence, and lose local evidence before it ever loses safe machine operation.
08Part III: One governed data spine
Two systems can exchange packets and still misunderstand production, so the architecture must define information, state, events and asset meaning separately.
09Part III: One governed data spine
The factory's data store is an evidence system, not a growing pile of values, so raw observations, contextual events, KPI results and corrections remain distinguishable and replayable.
10Part III: One governed data spine
The dashboard is a role-specific control surface whose freshness, definitions and next action are visible, not a gallery of independently calculated charts.
11Part III: One governed data spine
Applications should arrive as bounded, observable and reversible changes to a working production architecture, with ownership and rollback proven before scale.
12Part IV: Prove value and scale safely
This chapter specifies evidence capture rather than accounting or compliance methods: metres, denominators, allocations and life-cycle boundaries must make every displayed result reconstructable.
13Part IV: Prove value and scale safely
A connected factory is not accepted when its screens work on a normal day, but when its controls, fallbacks and recovery perform under adversarial and degraded conditions.
14Part IV: Prove value and scale safely
GFT recommends a four-phase build that earns each expansion through evidence quality, operating value, safe failure and recovery rather than device count.