Connect machines and software: first the data, then the protocols
Good integration arises from clearly defined information, responsibilities and behaviors.
Choose useful information
Before selecting a protocol, identify the data you need and why it needs to be exchanged. A value for supervision, a command and a history require different behaviors. For each data it is convenient to define the origin, unit of measurement and update frequency.
Check systems
Controllers, gateways and applications can have different interfaces. Versions, accesses and documentation determine the real connection possibilities. The presence of a common protocol is a starting point, but does not in itself guarantee application compatibility.
Manage interruptions
A project must also include missing data, delays and loss of communication. It is necessary to distinguish an updated value from a previous one and establish how to inform the operator. Network access and segmentation must be evaluated in the context of the company infrastructure.
Try the full route
Testing must follow data from machine to application, including errors and recovery. Novabase addresses integration by relating software, electronics and automation.