Connectivity is not usability
A connected IP address does not prove that operational data is usable. Teams must understand each point, unit, range, sampling time, and the difference between a real zero and a communication failure.
A durable delivery covers point semantics, time consistency, quality flags, edge buffering, diagnostics, and controlled configuration changes.
Six delivery layers
- Connection: protocol, network, session state, and security boundary.
- Tags: stable business names, types, units, ranges, and device ownership.
- Quality: acquisition time, receive time, timeout, substituted, and offline states.
- Edge: continued collection, buffering, rules, and ordered replay during outages.
- Business: mappings to equipment, processes, alarms, energy, and quality.
- Operations: topology, logs, diagnostics, versions, remote configuration, and change audit.
Implementation guidance
Validate one representative production line end to end before importing every point. Equipment, process, and software owners should jointly review names, units, frequency, and fault semantics.
Rehearse network loss, device restart, point-table changes, clock drift, duplicate replay, and conflicting updates before acceptance.
Acceptance checklist
- Can any business tag be traced to a device, address, unit, and configuration version?
- How is data buffered during an outage and deduplicated after recovery?
- Are faults, communication loss, and equipment shutdown represented as different states?
- Can site staff locate a fault at the equipment, network, gateway, or platform layer?