Start with one operational decision
A pilot does not need to connect the entire factory. Choose one decision: preparing a shift report, validating a production order or relating energy use to a product. Record who handles that process today, how often it happens and which information they use. Measure a baseline before claiming an improvement. Report preparation time, missing records and manual corrections are different measures and should be tracked separately. Assign an owner who can confirm whether the resulting information is actually useful.
Agree on a data contract
Automation engineers own source tags and quality codes; production teams define shifts, products and downtime meanings; IT owns the destination schema, access and retention. Specify an equipment identifier, source timestamp, engineering unit and quality field for every record. Whether a temperature is in Celsius or Fahrenheit, or when a counter resets, may matter more than establishing a connection. Include those cases in the test dataset. Avoid relying on a tag name as the only explanation of a value.
Run a controlled first connection
Begin with read-only access wherever possible. Use a test database rather than a production ERP endpoint. Validate a small set of tags in OPC Router and inspect triggering, transformation and destination writes separately. Include network outages, slow destinations, duplicate messages, bad quality and service restarts in acceptance tests. Document the expected record count and recovery behaviour for each case before running it. That makes a failed test useful rather than a matter of interpretation.
Expand only after measuring
At the end of the pilot, compare source and destination counts, latency distributions, error logs and replay results. Screenshots alone do not establish data completeness. Agree on acceptable limits with the plant team; there is no universal latency target for every use case. Name the operational owner, rollback procedure and change window before moving to another line. Reusing the same template on different equipment also deserves an acceptance test because tag semantics and timing may differ.
Take a concrete brief to the meeting
Prepare one page with the target decision, source and destination systems, data owner, sample record, expected load, outage tolerance and acceptance criteria. Our integration planner creates an initial connection brief; the project readiness checklist highlights missing responsibilities. Together they help make licence discussions and commissioning plans specific enough to review.
Technical references
Check manufacturer documentation for product capabilities. Project steps and examples were prepared by OPC Turkey.