Engineering at system interfaces: where the drawing stops being true

A system is easy to defend in isolation. A motor starter “works.” A PLC “scans.” A switch “forwards.” The plant still stops because the starter’s aux contact is not the PLC’s idea of running, or because the switch forwards best-effort frames into a cyclic budget, or because the mechanical sequence assumed a point the electrical contractor never landed. Interface engineering is the habit of writing the seam: signal, protocol, timing, fail state, and owner. It is the same habit in Division 25, in OT/IT, and in electrical diagnostics when the fault only exists between boxes.

How the investigation is actually run

Pick one seam and refuse to discuss the rest until that seam has a table: signal or object, protocol or voltage, timing, fail state, owner, and the test that crosses the terminal strip. If nobody will witness that test, you have optimism, not an interface. Closed punch lists on both sides with a dead plant in the middle is the classic signature. Write it without theatre.

Two earths, two clocks, a value displayed without a quality bit, and a spec that ends at the terminal strip are the usual causes. Software seams follow the same rule as copper seams: identity, units, and conflict lists. Workshops that produce alignment posters do not replace a one-page contract.

Stop when the owner can point at a person and a test. That is enough engineering. More process language will not close a contact that was never landed.

Symptoms

Each contractor has a closed punch list. The owner has a building that does not run. Related patterns: what Division 25 coordinates, OT/IT Ethernet, network that is electrical.

Causes

Specifications that end at the terminal strip. Tests that exercise one side. Software that “integrates” by displaying a value without a quality bit. Two earths. Two clocks.

Investigation

Draw the interface as a table, not a paragraph. Witness a test that crosses the strip. If you cannot name a test, you do not yet have an interface, you have optimism. Software seams follow the same rule: connecting engineering applications.

The conclusion of interface work is an owned contract, however short. It is not a workshop that produces alignment posters.