Research libraryEdge to Dashboard
Chapter 13 of 14 · Part IV · Draft web edition
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.
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.
Read-out
Derived qualitative placement of eight acceptance domains from the scope of NIST SP 800-82r3 (S17), NIST CSF 2.0 (S18), IEC 62443-3-2 (S19), CISA CPG 2.0 (S20), CISA backup guidance (S21), NIST SP 800-34r1 (S22), IEC functional safety (S23) and ISO/IEC 27001 (S24). X-axis scores cross-layer architectural span; Y-axis scores required physical and fault-injection test intensity.
Unit: derived scope and verification index (0 to 10). Status: derived. Sources: S17, S18, S19, S20, S21, S22, S23, S24.
Overture · 1 min
A connected textile factory is ready for operational dependence only when its cybersecurity boundaries, protective-safety independence and recovery procedures pass witnessed acceptance tests under degraded and adversarial conditions.[S17] A commissioning demonstration that shows live charts on a calm afternoon proves only that packets cross a wire when power, links and software behave normally.[S32] Where electrical interruptions are frequent and wide-area connectivity cannot be assumed continuous, an untested architecture fails in ways that confuse operators, corrupt production history or stall the line.[S32] Green Future Tech Limited (GFT), Hong Kong SAR, therefore treats security, functional safety and contingency recovery not as compliance paperwork, but as engineering acceptance gates governing whether a pilot line may move from shadow observation into daily operational use.[S30]
This chapter specifies the evidence pack required before a sponsor, plant manager or safety owner accepts a connected-factory deployment under GFT's Cameroon textile programme.[R06] While Cameroon's inherited sector baseline records roughly 95 percent of cotton fibre exported raw and about 5 percent processed locally, expanding domestic processing towards the national 50 percent target for 2030 requires factories whose instrumentation strengthens control rather than introducing new single points of failure.[R06] [R07] Each control maps to an observable test condition, an explicit pass-or-fail criterion set by the process or safety owner, a retained test record and a remediation path for exceptions.[S18] This chapter provides engineering reference guidance rather than investment, legal or tax advice, and it does not certify any machine, supplier or facility.[S24]
13.1
Related · chapter 076 paragraphs step it
Read-out
Illustrative zone-and-conduit design informed by NIST SP 800-82 Rev. 3 (S17), IEC 62443-3-2 (S19), CISA CPG 2.0 (S20) and IEC functional-safety principles (S23). Not a representation of an implemented GFT plant.
Unit: architectural zones. Status: illustrative. Sources: S17, S19, S20, S23. Illustrative figures are teaching examples, not measured factory results.
Read this exhibit in its chapter ↗Security and safety acceptance cannot begin until the factory defines the exact boundary of the system under test and accounts for every physical and logical path across it.[S19] In many brownfield retrofits, integration begins with an informal sketch showing an edge gateway reading a programmable logic controller (PLC), while omitting engineering laptops, cellular modems, shared switches, local buffers and safety relays.[S17] IEC 62443-3-2 makes security zones and conduits a key concept in security risk assessment for system design, requiring the team to partition the system under consideration into asset groupings with common security requirements and to document every channel connecting them.[S19]
In GFT's reference architecture, the risk assessment partitions the connected factory into explicit zones mirroring the responsibility separation established earlier in this paper.[S01] [S02] Production equipment and controllers sit in the production operational technology (OT) zone; safety sensing, logic and actuation reside in an independent safety zone; protocol adapters, edge buffers and vision nodes sit in the edge acquisition zone; historians, brokers and manufacturing operations services occupy the operations zone; an industrial demilitarised zone (DMZ) mediates external exchange; and corporate or cloud services remain in the business information technology (IT) or external zone.[S01] [S19]
A boundary definition is only as credible as its asset inventory.[S18] Before acceptance testing starts, the project team compiles a complete register of every asset inside or touching the system under consideration: spinning, weaving, dyeing, cutting and sewing controllers, IO-Link masters, Modbus converters, PROFINET switches, RFID readers, inspection cameras, edge appliances, local stores, MQTT brokers, engineering workstations, human-machine interfaces (HMIs), uninterruptible power supplies (UPS) and safety relays.[S09] [S10] [S11] [S19] The register records each asset's ISA-95 role, security zone, software version, clock source, role owner and failure consequence.[S01] [S12] [S13] [S18]
Ownership in the register is assigned to a specific factory role, such as the spinning maintenance engineer, quality systems lead or plant OT custodian, rather than an external integrator.[S18] [S24] Where an edge node runs containers under a multi-access edge computing pattern, both host appliance and deployed modules appear as distinct entries with resource and storage limits, letting the factory see which lines and KPIs are exposed when a change or vulnerability arises.[S08] [S16] [S18]
Between any two security zones, communication occurs only through a documented conduit.[S19] For each conduit, the register specifies initiating asset, receiving asset, transport protocol, application semantics, connection direction, payload direction, authentication mechanism, expected message rate and required behaviour when congested or severed.[S05] [S19] [S40] For example, the conduit between an edge node and the MQTT broker permits the edge node to initiate an outbound transport-layer-security session and publish Sparkplug birth, data and death messages, while prohibiting inbound connections from business IT to the edge appliance or controller.[S19] [S40]
Acceptance testing verifies conduit rules empirically rather than accepting firewall screenshots.[S17] [S19] During commissioning, the test engineer attempts authorised transactions and representative unauthorised connections across each boundary: probing closed ports, attempting direct write commands from the operations zone to machine registers, and simulating an unauthorised workstation joining the production switch.[S09] [S17] [S19] A conduit passes acceptance only when permitted production evidence flows cleanly, prohibited attempts are blocked, and rejections generate timestamped logs.[S17] [S19]
13.4
Technical network controls degrade rapidly if no management system governs who may change them, how exceptions are reviewed and how incidents are handled after commissioning.[S18] [S24] Because a mid-sized textile mill or garment facility in Cameroon cannot sustain a sprawling compliance bureaucracy, GFT combines the National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 2.0 for outcome-oriented goals with ISO/IEC 27001:2022 for a lean, continually improved information security management system (ISMS).[S18] [S24] [S30]
…Technology (NIST) Cybersecurity Framework (CSF) 2.0 for outcome-oriented goals with ISO/IEC 27001:2022 for a…
S18, S24, S18, S24, S30
NIST CSF 2.0 organises cybersecurity risk management around six core functions: Govern, Identify, Protect, Detect, Respond and Recover.[S18] NIST Special Publication 800-61 Revision 3 extends this structure by showing how organisations incorporate incident response recommendations and considerations across those same CSF 2.0 functions.[S1301] GFT translates these six functions into concrete acceptance evidence that a small factory team can verify and maintain during normal shifts.[S18] [S1301]
In a lean manufacturing team, cybersecurity governance works when responsibilities attach to existing operational cadences.[S18] [S30] Under Govern and Identify, the sponsor and plant manager approve the risk appetite, zone-and-conduit architecture, asset register and role assignments for data owner, process owner, OT custodian and safety officer before Phase 1 pilot operation begins.[S18] [S19] Under Protect and Detect, the OT custodian and line engineers verify access control, network segmentation, configuration baselines, clock synchronisation and stale-session alerting.[S13] [S18] [S40] Under Respond and Recover, operations and maintenance leads rehearse incident containment, manual fallback logging and isolated backup restoration.[S22] [S1301]
Each outcome is written as an observable state checked during a site acceptance walkdown.[S18] Rather than assuming a dedicated security operations centre watches alerts around the clock, the design reduces attack surface by eliminating unnecessary remote paths, restricting write capabilities at the gateway interface, and routing high-priority integrity alerts into supervised operational channels.[S17] [S19]
ISO/IEC 27001:2022 provides requirements for establishing, implementing, maintaining and continually improving an information security management system for organisations of any size and sector.[S24] Acceptance requires four working management loops before handover: a risk-treatment register linking every identified OT and edge threat to an implemented control or signed residual-risk acceptance; a change-control workflow requiring authorisation, version recording and rollback readiness before any firmware, PLC logic, vision model or KPI formula is modified; a supplier-access procedure governing integrators; and a corrective-action log tracking test failures to closure.[S08] [S18] [S24]
To make the relationship between standards, technical controls and verification concrete, Exhibit 58 maps the eight acceptance control families across their architectural span and required fault-injection intensity.[S17] [S19]
As Exhibit 58 illustrates, governance baselines under NIST CSF 2.0 and ISO/IEC 27001 span the stack from shop-floor devices to executive reviews, whereas protective safety independence and OT timing resilience require high-intensity physical fault injection at the machine level.[S17] [S18] [S23] [S24] Isolated backup restoration and contingency exercises sit in the upper-right quadrant because they combine cross-layer coordination with live restoration and reconciliation drills, though a qualitative matrix cannot substitute for executing individual tests on plant hardware.[S17] [S21] [S22]
13.7
Read-out
Derived placement from S09 (Modbus request/reply polling), S10 (IO-Link cyclic and on-request separation), S11 (PROFINET deterministic control) and S25 (RFID denim WIP tracking). Horizontal axis scales timing determinism and control sensitivity (1 = slow polling or asynchronous read, 10 = sub-microsecond isochronous control). Vertical axis scales interface diagnostic and semantic structure (1 = raw address or tag ID, 10 = structured cyclic data with separate diagnostics).
Unit: derived engineering placement (1 to 10 scale). Status: derived. Sources: S09, S10, S11, S25.
Read this exhibit in its chapter ↗13.7 · Introduction
In an office network, packet inspection delay is a minor inconvenience; on an industrial line, a security control that starves a controller CPU or disrupts cyclic communication is an operational hazard.
Exhibit 20, chapter 05: Modbus RTU/TCP (S09)
13.8 · Security appliances and polling gateways are tested under peak line load
Operational acceptance of OT security controls proceeds in two stages: non-interference verification under peak production rates, and degraded-mode verification under abnormal traffic or appliance failure.
Exhibit 20, chapter 05: Modbus RTU/TCP (S09)
13.9 · Process owners set timing and reliability thresholds before testing begins
Neither the cybersecurity standard nor the reference architecture invents universal numerical thresholds for scan-time margin, polling interval or recovery jitter, because tolerances depend on the physical process: a bale scale, dyeing vat and air-jet loom have different time constants.
Exhibit 20, chapter 05: RFID WIP read points (S25)
13.7 · the bodyThe film above follows these sub-steps.
In an office network, packet inspection delay is a minor inconvenience; on an industrial line, a security control that starves a controller CPU or disrupts cyclic communication is an operational hazard.[S17] NIST Special Publication 800-82 Revision 3 emphasises that securing operational technology requires addressing the unique performance, reliability and safety requirements of industrial environments.[S17] GFT therefore requires every OT security control, gateway polling schedule and network filter to pass operational timing and production-impact tests before acceptance.[S17]
NIST Special Publication 800-82 Revision 3 emphasises that securing operational technology requires addressing the unique performance
S17
This requirement applies across the fieldbus and industrial Ethernet protocols in a mixed-generation textile plant.[S35] Where brownfield machinery uses MODBUS, communication follows a request-and-reply model specified by function codes; aggressive polling can delay controller scan cycles or trigger timeouts.[S09] [S17] Where smart sensors connect through IO-Link, cyclic process data exchange is separated from on-request parameters, commands and events so process data flows without interference.[S10] Where high-speed machinery uses deterministic PROFINET, closed-loop control can depend on isochronous transmission with jitter below one microsecond.[S11] Any security appliance or gateway placed near these networks must prove that it respects their deterministic boundaries.[S11] [S17]
Operational acceptance of OT security controls proceeds in two stages: non-interference verification under peak production rates, and degraded-mode verification under abnormal traffic or appliance failure.[S17] During the first stage, the machine runs at maximum rated speed while the edge gateway executes its full polling schedule, local inference models process camera frames, and the zone firewall enforces its rules; engineers monitor scan times, fieldbus error counters, IO-Link event logs, PROFINET jitter and gateway resource use.[S09] [S10] [S11] [S17] [S26]
During the second stage, the test team introduces stress and failure conditions across the boundary conduit: disconnecting the operations network, saturating the firewall with blocked traffic on the non-OT side, forcing a broker failover, and power-cycling the edge gateway.[S17] [S19] Throughout these disturbances, the machine controller must continue executing its control loop without fault, cyclic process data within the machine zone must remain undisturbed, and no false command or register corruption may occur.[S10] [S17]
Neither the cybersecurity standard nor the reference architecture invents universal numerical thresholds for scan-time margin, polling interval or recovery jitter, because tolerances depend on the physical process: a bale scale, dyeing vat and air-jet loom have different time constants.[S11] [S17] Instead, the process owner and equipment engineer record the operating envelope on the machine-capture sheet before testing starts, including maximum scan-time increase, zero uncommanded state changes, and required clock precision under NTPv4 or IEEE 1588 Precision Time Protocol (PTP).[S12] [S13] [S17]
13.10
Equipment suppliers, vision integrators and automation engineers often request remote access to diagnose faults or update software.[S17] [S20] In Cameroon, where specialist vendor support for imported spinning, weaving or inspection machinery may reside abroad, structured remote maintenance has a clear rationale.[R06] [S20] Yet unmanaged remote access, such as an always-on cellular router wired into a machine switch or shared passwords, is a primary pathway for compromise and configuration drift.[S19] [S20]
The Cybersecurity and Infrastructure Security Agency (CISA) Cybersecurity Performance Goals (CPG) 2.0 require multi-factor authentication (MFA) on all OT accounts and systems that can be accessed remotely, including vendor and maintenance accounts, remotely accessible user and engineering workstations, and remotely accessible HMIs when available.[S20] IEC 62443-3-2 complements this by requiring that remote traffic cross only defined conduits terminating in an appropriate zone rather than bridging directly into production control.[S19]
In GFT's reference architecture, remote maintenance fails closed by default: when no window is active, the remote conduit is disabled and no external party can reach the industrial DMZ or operations zone.[S19] [S20] Opening a session requires a three-step sequence tested during acceptance: a named vendor engineer requests access for a specific asset, purpose and window against an ISO/IEC 27001 change-control ticket; the process owner and OT custodian approve the window and enable the time-bounded rule on the DMZ jump host; and the vendor authenticates with an individual account and MFA.[S19] [S20] [S24]
Once authenticated at the DMZ, the session is restricted to the target edge node or workstation using least-privilege rules blocking lateral movement.[S19] [S20] Every command, file transfer and change is logged with user identity and timestamp, and when the timer expires or the supervisor trips a termination switch, the session closes and credentials revoke.[S19] [S20] [S24]
Brownfield textile plants include older PLCs, panels and field devices that cannot natively support MFA or encryption.[S17] [S20] CISA CPG 2.0 accounts for this by specifying MFA on remotely accessible systems and HMIs when available, while IEC 62443-3-2 isolates legacy devices behind an intermediary boundary.[S19] [S20] Where a controller or HMI lacks strong authentication, GFT prohibits exposing it directly; remote access terminates at a hardened DMZ jump host enforcing MFA, session recording and role-based authorisation before communicating over a filtered conduit.[S19] [S20]
Interlude · the cloth half-woven
Woven: sections 13.0 to 13.10Still to weave: 13.13 to 13.19
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 ↗13.13
The single most important architectural invariant in a connected factory is that protective safety functions remain independent of data-collection gateways, edge inference models, message brokers, historians, dashboards and cloud services.[S19] [S23] As the International Electrotechnical Commission (IEC) explains, within the overall safety of a system, functional safety provides automatic protection in response to errors.[S23] IEC 61508-1:2010 sets out general requirements when electrical, electronic and programmable electronic (E/E/PE) systems carry out safety functions, establishing a safety lifecycle distinct from general-purpose information systems.[S1302]
IEC 61508-1:2010 sets out general requirements when electrical
S1302
In a textile and garment factory, physical hazards include rotating shafts on spinning frames and looms, cutting blades, heated rollers, pressurised dyeing vessels and conveyors.[S23] Emergency-stop circuits, light curtains, two-hand controls, interlock switches, over-temperature cut-outs and safety relays or safety PLCs bring equipment to a safe state automatically when a hazard or fault occurs, and none of those actions may wait for an MQTT message, an edge container or a dashboard alert.[S05] [S16] [S23] [S1302]
While edge nodes and dashboards observe safety events, the signal path from the safety system to the edge gateway must be unidirectional or galvanically and logically isolated so no monitoring fault propagates into the safety loop.[S17] [S19] [S23] Exhibit 59 illustrates how GFT separates independent protective safety from production control, edge acquisition, operations management and external access.[S19] [S23] [S1302]
Read-out
Illustrative zone and responsibility separation informed by IEC 62443-3-2 zones and conduits (S19), IEC functional safety principles (S23) and IEC 61508-1 E/E/PE safety-related system scope (S1302). Protective actuation never traverses the edge, operations or external layers.
Unit: . Status: illustrative. Sources: S19, S23, S1302. Illustrative figures are teaching examples, not measured factory results.
As shown in Exhibit 59, the protective safety zone acts directly on machine actuators and contactors while providing only an isolated, read-only diagnostic tap to the edge layer.[S19] [S23] [S1302] During safety acceptance, the safety officer and automation engineer execute witnessed fault-injection tests in a safe test mode: unplugging edge power, disconnecting or shorting the diagnostic tap, flooding the edge network interface, freezing the dashboard and severing the plant LAN.[S17] [S23] Under every condition, every emergency stop, guard interlock and protective trip must actuate within its certified response time and bring the machine to its safe state; any exception blocks commissioning.[S23] [S1302]
IEC 62443-3-2 and IEC 61508-1 also require that safety logic and parameters be protected against unintended or malicious modification over network interfaces.[S19] [S1302] Where a machine uses a programmable safety controller alongside a standard PLC, the safety program remains locked behind a physical key-switch or hardware write-protect mechanism, and no conduit from edge, operations or remote zones may alter safety parameters or bypass interlocks.[S17] [S19] [S1302] Acceptance testing verifies that parameter writes over the monitoring interface are rejected and that key-switch states are logged.[S19] [S24]
13.16
Related · chapter 096 paragraphs step it
Read-out
Illustrative store-and-forward replay sequence based on edge persistence (S29), Sparkplug host STATE and historical flush rules (S40), immutable OPC UA EventId tracking (S0902) and controlled recalculation (S24).
Unit: . Status: illustrative. Sources: S24, S29, S40, S0902. Illustrative figures are teaching examples, not measured factory results.
Read this exhibit in its chapter ↗Ransomware, media failure, power-surge corruption and human configuration errors share a common remedy: restoring a clean, known-good copy of software, logic, configurations and historical data onto replacement or wiped hardware.[S21] [S22] Yet many plants discover during an outage that their backup share sat read-write on the same network segment that malware encrypted, the PLC project file was outdated, or certificates and KPI definitions were omitted.[S08] [S21] [S22]
Joint guidance from CISA and partner authorities advises operators to regularly test backup procedures and ensure backups are isolated from network connections that could enable malware spread.[S21] NIST Special Publication 800-34 Revision 1 reinforces that testing validates recovery capabilities against their intended design, so GFT treats backup verification as a live, clean-target restoration test rather than a schedule inspection.[S21] [S22]
To satisfy CISA's isolation requirement, the backup architecture ensures that compromised credentials in the business IT or operations zone cannot delete, overwrite or encrypt recovery copies.[S19] [S21] In a small or mid-sized textile plant, this uses an access-controlled backup appliance pulling backups over a restricted conduit plus periodic offline, write-protected media stored on-site and off-site, with every artefact hashed and logged in the ISO/IEC 27001 configuration register.[S19] [S21] [S24]
The backup inventory covers four layers required to reconstruct the evidence chain: 1. Authorised PLC, drive and IO-Link master project files and machine recipes, captured on every approved change.[S10] [S21] [S24] 2. Edge operating-system images, container specifications, Modbus and OPC UA register maps, Sparkplug configurations, and approved vision weights and calibration files.[S04] [S09] [S16] [S26] [S40] 3. Switch configurations, firewall rules, NTP/PTP settings, TLS certificate authorities and MQTT broker access lists.[S12] [S13] [S19] [S21] 4. Central historian schemas, raw observation archives, event tables, ISO 22400 KPI dictionary definitions, dashboard layouts, and ISO/IEC 27001 audit and change logs.[S08] [S21] [S24]
During acceptance, the commissioning team wipes a representative edge node and a staging historian and KPI service to bare metal, disconnects internet or vendor cloud links, and has plant maintenance and OT staff restore both solely from isolated backup media and the written runbook.[S21] [S22] The test passes only when the restored edge node validates its certificates, resumes polling and local buffering, and publishes valid Sparkplug messages, while the restored historian and KPI service reproduce identical historical KPI values without manual patching.[S08] [S21] [S22] [S40]
13.19
1. Isolate zone and confirm safe machine
1. Isolate zone and confirm safe machine. Starting point. Leads to 2. Activate manual line and inspection logs (Safety confirmed). · illustrative
Unrehearsed contingency procedures fail under real disruption.
2. Activate manual line and inspection logs
2. Activate manual line and inspection logs. From 1. Isolate zone and confirm safe machine (Safety confirmed). Leads to 3. Restore clean state from isolated backup (Clean target ready). · illustrative
3. Restore clean state from isolated backup
3. Restore clean state from isolated backup. From 2. Activate manual line and inspection logs (Clean target ready). Leads to 4. Replay edge buffer by ID and source time (Host online). · illustrative
5. Enter and flag manual fallback records
5. Enter and flag manual fallback records. From 4. Replay edge buffer by ID and source time (Telemetry deduplicated). Leads to 6. Reconcile KPI totals and denominators (Provenance tagged). · illustrative
6. Reconcile KPI totals and denominators
6. Reconcile KPI totals and denominators. From 5. Enter and flag manual fallback records (Provenance tagged). Leads to 7. Resume live dashboards with sign-off (Zero KPI drift). · illustrative
7. Resume live dashboards with sign-off
7. Resume live dashboards with sign-off. From 6. Reconcile KPI totals and denominators (Zero KPI drift). Leads to 8. Log RTO/RPO and close corrective actions (Audit logged). · illustrative
8. Log RTO/RPO and close corrective actions
8. Log RTO/RPO and close corrective actions. From 7. Resume live dashboards with sign-off (Audit logged). End point. · illustrative
Illustrative recovery and reconciliation workflow informed by CISA isolated backup restoration guidance (S21), NIST SP 800-34r1 testing, training and exercise principles (S22), and NIST SP 800-61r3 incident response lifecycle alignment (S1301).
Unit: . Status: illustrative. Sources: S21, S22, S1301. Illustrative figures are teaching examples, not measured factory results.
13.19 · the bodyExhibit 60 above; its figures are illustrative where marked.
Unrehearsed contingency procedures fail under real disruption.[S22] NIST Special Publication 800-34 Revision 1 distinguishes three activities: testing validates recovery capabilities, training prepares recovery personnel for plan activation, and exercising the plan identifies planning gaps; combined, they improve plan effectiveness and organisation preparedness.[S22] In GFT's acceptance framework, a connected factory is accepted only after recovery capabilities are tested, floor and technical staff are trained on degraded-mode duties, and end-to-end contingency scenarios are exercised with documented gap closure.[S22] [S1301]
NIST Special Publication 800-34 Revision 1 distinguishes three activities
S22
This discipline matches documented operating conditions in Cameroon and the region.[S32] [S33] Because 93.3 percent of surveyed Cameroonian firms in the 2024 World Bank Enterprise Survey reported electrical outages, with 10.4 outages in a typical month across formal private firms, power transitions and partial restarts are routine.[S32] Similarly, while ITU's 2024 figure that 14 percent of Africa's population lacks mobile-broadband coverage is a regional population indicator rather than a factory link measurement, it underscores why wide-area link loss and delayed remote support must be rehearsed as standard conditions.[S33]
Recovering a server or reconnecting a cable is only the midpoint of a contingency exercise.[S22] When a digital system returns from degraded or manual operation, some events sit in edge buffers, some quality records sit on manual sheets, and some metre intervals occurred during generator transitions.[S08] [S22] [S29] [S40] Resuming dashboards without reconciling those records leaves gaps, double-counted bundles or distorted resource-intensity denominators.[S08] [S29] Exhibit 60 shows the eight-stage recovery and reconciliation sequence required for every contingency exercise and incident response.[S21] [S22] [S1301]
As Exhibit 60 demonstrates, live dashboards resume at step 7 only after edge buffers replay by source timestamp (step 4), manual fallback records enter with explicit provenance and quality flags (step 5), and ISO 22400 KPIs reconcile against physical line counters and metre totals (step 6).[S08] [S22] [S40] Step 8 records elapsed restoration time against target RTO, data loss against target RPO, and corrective-action owners and due dates in the ISO/IEC 27001 register, while leaving site-specific RTO and RPO targets to be set by process owners before testing begins.[S22] [S24]
live dashboards resume at step 7 only after edge buffers replay by source timestamp (step 4)
S08, S22, S40, S22, S24
To consolidate all seven acceptance domains into an inspectable commissioning contract, Exhibit 61 presents the GFT acceptance evidence index, where no test is marked passed in the outline and every row defines scenario, expected behaviour, measurement record, approver and exception rule.[S17] [S19] [S22] [S23]
As Exhibit 61 makes explicit, the acceptance pack does not treat all exceptions equally.[S19] [S23] An open exception in protective safety independence is a non-negotiable stop condition: no line may operate with a compromised emergency stop or guard interlock.[S23] [S1302] An open exception in zone-boundary write protection, backup restoration or KPI reconciliation blocks transition from shadow mode to operational dependence, keeping the official record on the baseline procedure until retest passes.[S19] [S21] [S22] Minor administrative findings that do not threaten safety, machine control or evidence integrity are logged with an owner, compensating control and retest date in the ISO/IEC 27001 corrective-action register, feeding into the phase-gate decisions of the implementation roadmap.[S24] [S30]
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.
31 sources · 327 citation marks on this pageMost cited: S19, 41 times
Grade AGrade BGrade CKnot size: citations on this page
All 31 records shown
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.
c13-S01 · Grade B
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 ↗c13-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 ↗c13-S04 · Grade B
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 ↗c13-S05 · Grade B
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 ↗c13-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 ↗c13-S09 · Grade B
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 ↗c13-S10 · Grade B
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 ↗c13-S11 · Grade B
PROFINET System Description: Technology and Application
For high-precision closed-loop control tasks, deterministic and isochronous transmission of time-critical process data with a jitter of less than 1 μs is possible.
2018-11. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-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 ↗c13-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 ↗c13-S16 · Grade A
ETSI GS MEC 003 V3.2.1: Multi-access Edge Computing, Framework and Reference Architecture
Multi-access Edge Computing enables the implementation of MEC applications as software-only entities that run on top of a Virtualisation infrastructure, which is located in or close to the network edge.
2024-04. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-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 ↗c13-S18 · Grade A
The NIST Cybersecurity Framework 2.0
The NIST Cybersecurity Framework (CSF) 2.0 provides guidance to industry, government agencies, and other organizations to manage cybersecurity risks.
2024-02-26. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-S19 · Grade A
IEC 62443-3-2:2020: Security for industrial automation and control systems, Part 3-2: Security risk assessment for system design
A key concept in this document is the application of IACS security zones and conduits.
2020-06. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-S20 · Grade A
Cybersecurity Performance Goals 2.0
OT: MFA is enabled on all accounts and systems that can be accessed remotely, including vendors/maintenance accounts, remotely accessible user and engineering workstations, and remotely accessible HMIs when available.
2025-12. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-S21 · Grade A
Russian State-Sponsored and Criminal Cyber Threats to Critical Infrastructure
Regularly test backup procedures and ensure that backups are isolated from network connections that could enable the spread of malware.
2022-05-09. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-S22 · Grade A
NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems
Testing validates recovery capabilities, whereas training prepares recovery personnel for plan activation and exercising the plan identifies planning gaps; combined, the activities improve plan effectiveness and overall organization preparedness.
2010-11-11. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-S23 · Grade A
Ensuring safety in the workplace
Within the overall safety of a system, functional safety refers to the aspect that provides automatic protection in response to errors.
2022-04-28. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-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 ↗c13-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 ↗c13-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 ↗c13-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 ↗c13-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 ↗c13-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 ↗c13-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 ↗c13-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 ↗c13-S40 · Grade B
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 ↗c13-S1301 · Grade A
NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile
This publication seeks to assist organizations with incorporating cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities as described by the NIST Cybersecurity Framework (CSF) 2.0.
2025-04. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗c13-S1302 · Grade A
IEC 61508-1:2010: Functional safety of electrical/electronic/programmable electronic safety-related systems, Part 1: General requirements
IEC 61508-1:2010 covers those aspects to be considered when electrical/electronic/programmable electronic (E/E/PE) systems are used to carry out safety functions.
2010-04-30. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.
Open the recorded source ↗S17 National Institute of Standards and Technology. 2023-09.
S32 World Bank Enterprise Surveys. 2025.
S30 MDPI, Sustainability. 2023-08-19.
R06 Cameroon Trade Hub. Publication date unrecorded; inherited source-text check.
R07 Ecofin Agency. Publication date unrecorded; inherited source-text check.
S18 National Institute of Standards and Technology. 2024-02-26.
S24 International Organization for Standardization and International Electrotechnical Commission. 2022-10.
S19 International Electrotechnical Commission. 2020-06.
S01 International Society of Automation. 2025-04-10.
S02 International Electrotechnical Commission. 2013-05-22.
S09 Modbus Organization. 2012-04-26.
S10 IO-Link Community. 2024-06.
S11 PROFIBUS Nutzerorganisation. 2018-11.
S12 IEEE Standards Association. 2020-06-16.
S13 Internet Engineering Task Force and RFC Editor. 2010-06.
S08 International Organization for Standardization. 2014-01.
S16 European Telecommunications Standards Institute. 2024-04.
S05 OASIS Open. 2019-03-07.
S40 Eclipse Foundation. 2022-11-16.
S1301 National Institute of Standards and Technology. 2025-04.
S22 National Institute of Standards and Technology. 2010-11-11.
S20 Cybersecurity and Infrastructure Security Agency. 2025-12.
S21 CISA and joint international cybersecurity authorities. 2022-05-09.
S23 International Electrotechnical Commission. 2022-04-28.
S35 United Nations Industrial Development Organization. 2019.
S26 MDPI, Electronics. 2025-09-18.
S31 MDPI, Sensors. 2020-04-28.
S29 MDPI, IoT. 2024-09-28.
S1302 International Electrotechnical Commission. 2010-04-30.
S04 OPC Foundation. 2025-10-22.
S33 International Telecommunication Union. 2024-11-10.
Keep the thread · chapter 13 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.