Application guide · 13 September 2026. Illustrative project guidance; verify device, version and license compatibility separately.
Start with the business requirement
It is easy to begin by collecting every available tag and harder to demonstrate a useful result. State whose decision the data will support. Confirming shift output, identifying a critical stop and transferring an ERP work order require different flows. Choose one line, a defined set of devices and one destination for the pilot. Tie success to an observable acceptance scenario.
Inventory more than the brand name
Record the model, firmware, protocol, interface and software version for every device. PLC access permissions and network requirements affect driver selection. A source that already exposes OPC UA does not require the same integration step as a device with only a vendor protocol. Verify the exact match in product and driver documentation; a product-family name is not enough to establish compatibility.
Agree the data contract early
Define tag names, types, engineering units, source timestamps and quality together. Agree required fields, null handling and record identifiers with the destination-system team. Writes also need permissions and acknowledgement behavior. A small representative dataset gives the teams a more useful shared reference than screenshots alone.
Make the pilot ready for handover
Test normal operation, network interruption and reconnection. Include the project backup, version inventory, certificate owner and rollback steps in the handover. This guide is a planning template. Capacity and license scope still require evaluation against the actual devices, data volume and selected product versions.
Review with your team
- Pilot owner and acceptance criteria agreed.
- Device and version inventory complete.
- Sample data contract shared.
- Network access and write permissions defined.
- Outage test and rollback plan ready.
