2.1 Equipment connectivity playbook

A disconnected machine is a black hole in your production line. You cannot improve what you cannot measure, and manual data entry is just a digitized guess. The goal of connectivity is High-Fidelity Telemetry: capturing the machine’s state, throughput, and process variables in real-time to drive automated decisions.

Protocol strategy: the connectivity pyramid

The wheel must not be reinvented. Standard manufacturing protocols must be used. Custom drivers are technical debt that will bankrupt your maintenance team.

1. The gold standard: IPC-CFX (IPC-2591)

Use for: SMT lines, modern electronics assembly, THT.
Why: It is plug-and-play. The data structure is predefined (SDK driven). No tag mapping required.
Rule: When purchasing new equipment, “Native IPC-CFX Support” should be a mandatory requirement in the RFQ to ensure seamless integration.

2. The universal translator: OPC-UA

Use for: PLCs (Siemens, Beckhoff), Injection Molding (Euromap 77), CNC (Umati).
Why: Secure, semantic, and firewall-friendly.
Requirement: Enforce encryption (such as Basic256Sha256) and strong User Authentication. Anonymous login should be disabled to maintain security.

3. The legacy adapters: SECS/GEM & MTConnect

Use for: Semiconductor front-end (SECS/GEM) or older CNCs (MTConnect).
Constraint: Requires an Edge Gateway to translate “Chatty” SECS messages into JSON/MQTT for the MES.

4. The last resort: Modbus / Digital I/O

Use for: Ancient conveyors, pumps, tower lights.
Constraint: Data is context-free (just bits). Requires heavy logic on the Edge to interpret.

Step-by-step onboarding procedure

A structured sequence must be followed to bring a machine online. Skipping steps or accepting “partial connectivity” often leads to corrupt or incomplete data.

Step 1: protocol selection & physical connection

The controller type and available ports must be identified.
Isolation must occur on the Level 0-2 Control VLAN.
Test: Verify you can ping the machine from the Edge Gateway. If unsuccessful, check the Firewall/Subnet configuration.

Step 2: time synchronization (NTP)

Data without accurate time is useless for genealogy.

Requirement: Point the machine’s clock to the local Stratum-2 NTP Server.
Validation: Monitor “Clock Skew”.
Rule: When the skew exceeds 500ms, the system should flag the data as “Suspect” and trigger a warning for investigation.

Step 3: data dictionary & tag mapping

A raw PLC tag named, for example, “DB1.DBX0.1” is meaningless to a Data Analyst. It is necessary to normalize data at the edge.

Naming Convention: Category.Asset.Variable (e.g. Oven.Zone1.ActualTemp).
Unit Standardization: All values must be converted to SI Units (Celsius, Bar, mm/s).
Boolean Logic: 1/0 must be mapped to Running/Stopped or Pass/Fail explicitly.

Step 4: identity binding (the “context” step)

Telemetry is noise unless linked to a Product.

Requirement: The machine needs to know what it is building to provide relevant context.
Method:
1. The Operator scans a Barcode (Start Event).
2. The MES sends the Unit_ID to the Machine Register.
3. The Machine attaches the Unit_ID to all subsequent process logs.
Validation: When the Unit_ID is null or missing, the system should either discard the process data or route it to a designated “Unknown Bucket” log for review.

Step 5: buffering strategy (store-and-forward)

Networks blink. Servers patch. The machine must never stop recording.

Edge Requirement: The Gateway needs to buffer data locally (e.g. using SQLite or Disk storage).
Logic:
- When the uplink is active, the system streams the data in real-time.
- When the uplink fails, the system queues the messages in a FIFO (First-In, First-Out) manner.
- When the uplink is restored, the system drains the queue while maintaining rigorous chronological order.
- Capacity: A minimum of 24 hours of local buffer capacity is strongly recommended.

Data validation rules

It is crucial to verify data integrity. Ingesting bad data can poison downstream analytics and AI/ML models.

Range Checks: When a temperature reads an impossible value like > 2000˚C (indicating a likely broken sensor), the system should replace the value with NULL or flag it as Quality=Bad to prevent recording physics-defying numbers.
Stale Data: When a value remains completely unchanged for an extended period (e.g. 60 minutes) while the machine is actively running, the system should trigger a “Sensor Frozen” alert.
Duplicate IDs: When a Serial_Number appears on two separate machines simultaneously, the system should trigger a “Cloned Unit” security alert to investigate potential scanning errors or process bypasses.

Recap: Equipment Connectivity Protocol and Data Integrity

Parameter	Requirement	Value / Tolerance	Action / Condition
Protocol Selection	Native IPC-CFX support for new SMT/assembly equipment	Mandatory in RFQ	Use OPC-UA for PLCs; SECS/GEM/MTConnect require Edge Gateway
Time Synchronization (NTP)	Machine clock skew from Stratum-2 server	≤ 500 ms	Flag data as “Suspect” and trigger warning if exceeded
Identity Binding (Unit_ID)	All process data must be linked to a product ID	Null or missing Unit_ID not permitted	Discard data or route to “Unknown Bucket” for review
Edge Buffering Capacity	Local storage during network outage	≥ 24 hours	FIFO queue; drain upon uplink restoration
Data Validation	Range check for impossible values; Stale data check during operation	> 2000°C (example); Unchanged for > 60 min	Flag as “Quality=Bad” or NULL; Trigger “Sensor Frozen” alert