The full power of TDengine, now free forever for up to 5,000 tags.

Explore More

Industrial Data Collection Commissioning: What to Verify Before Handoff

Juno Qiu

November 2, 2026 /

A connected data source is not necessarily a usable data service. Before handing a new collection path to operations, the integration engineer should be able to show which signals were authorized, what they mean, how failures appear and who responds when the path stops working.

Use the following checks for a bounded deployment. The site’s operating and safety procedures govern testing; arrange any interruption with the responsible owners.

Confirm the authorized path

Record the source system, interface, network zones, intermediary components, destination and intended consumer. Obtain the source owner’s approval for the selected points, access rights and expected workload. Verify that credentials and permissions match the intended operation. A read-only intent is not the same as proven read-only access.

Review network and credential controls with the site security team. NIST’s OT security guide provides risk-based context, while the specific site’s reliability and safety requirements determine the implementation.

Trace a small set of known measurements

For each selected point, compare the source identifier, destination name, equipment, value, unit, type and any available quality state. Check a known change, a stable condition and an invalid or unavailable state where safe and feasible. Record mapping and configuration versions.

Establish where timestamps originate, how time zones are represented and whether the destination shows event time, collection time or both. If the consumer relies on historical records, define the expected time range and validate any backfill separately from ongoing collection.

Test operational behavior

Agree on acceptance criteria before testing: acceptable freshness, completeness, load, alerts and recovery behavior. Measure the source and network impact against the site’s baseline. Test an approved interruption at a clearly identified boundary and observe which records are buffered, delayed, missing or duplicated. If buffering is not supported, say so; a connection returning to green does not prove that history was recovered.

Check restart behavior and the path’s response to invalid credentials or an unavailable destination where those tests are permitted. Compare records at the source and destination after recovery. Record known limitations and assign an owner to investigate any discrepancy.

Acceptance matrix

Complete the criteria with the site and consumer owners before testing. The examples below are prompts, not universal thresholds. Attach test records, configuration versions and timestamps to each result.

CheckExpected evidenceAcceptance criterion to agreeResponsible owner
Authorized path and permissionsApproved point list, network path and access testOnly the agreed sources, users and operations are permitted.Source and OT security owners
Measurement mappingTrace of known source records to destination, including unit and available qualitySelected records match their approved mappings and tolerances.Integration and source owners
Time and freshnessTimestamp origin, clock status and measured arrival ageTime semantics and observed freshness meet the consumer’s documented requirement.Integration and consumer owners
Load and availabilityBaseline and post-connection observations during an agreed windowSite-defined operating limits and service requirements are met.Source owner
Failure and recoveryApproved interruption test, alerts, record comparison and known gapsRecovery and consumer notification meet agreed criteria; unsupported recovery is recorded.Integration and destination owners
HandoffRunbook, contacts, monitoring and exception registerNamed teams accept the documented operating responsibilities.Destination and consumer owners

Mark each check pass, fail or not tested, with an evidence reference. For every exception, record its impact, owner, due date and mitigation. An unresolved exception is not a pass: the designated source, integration and consumer owners must either reject handoff or explicitly accept the residual risk within their authority. Record their sign-off and any retest required.

Hand over a service, not a connection

Provide the point list, mapping and configuration version, network and credential owners, alert destinations, troubleshooting steps and escalation contacts. Document maintenance windows, backup or recovery procedures, source dependencies and the process for approving new points. Make sure the receiving team can locate the evidence and understands what the data does—and does not—represent.

Acceptance is a joint decision by source, integration and consumer owners. A short signed record of the tests and open exceptions makes that decision repeatable when the system changes.

Related Articles