Integration starts with a shared meaning.
Different systems can use different names for the same event—or the same name for different events. Establish the data contract, ownership and failure behaviour before committing to an interface.
Scope the right work.
- Machine and enterprise integration requirements
- Data naming, context and ownership
- Event and result exchange between systems
- Access boundaries and network constraints
Technical scope
An interface needs a contract.
Specify the meaning and ownership of the information as carefully as the mechanism used to transport it.
| Area | Define together | Example evidence |
|---|---|---|
| Identity & meaning | Define equipment identity, record identity, units, timestamps and field meaning. | A reviewed data dictionary and representative example records. |
| Failure & recovery | Agree handling of lost connections, repeated events and rejected records. | Tests that interrupt and restore the connection, including duplicate delivery. |
| System ownership | Identify which system owns each record and who can change the interface. | A responsibility matrix and documented handover boundaries. |
Useful review artefacts
- Equipment and enterprise interface schedule
- Data dictionary and exchange examples
- Connection-loss, reconciliation and acceptance plan
A planning framework, not a confirmed feature or compatibility list. Deliverables and acceptance criteria are agreed for the application.
Questions worth answering early.
- Which system is the source of truth for each record?
- What should happen during a connection failure or duplicate event?
- Which protocols, versions and interfaces are actually available?
The starting point
An interface and data scope grounded in the installed systems. Protocol support, MES compatibility and cybersecurity requirements are confirmed during discovery.