Industrial IoT Data Ownership, SLAs and Exit Planning

Use the working record

Download the editable worksheet. Record the actual evidence and responsible reviewer against each relevant row. The empty results are inputs for your project, not completed tests. Add the equipment identity, operating period and reference method before assigning an outcome. Retain unsuccessful checks and the evidence from any repeat after correction.

Inventory the information before assigning rights

List raw instrument observations, calculated values, alarm history, operator annotations, configuration, asset mappings and audit records. These are different information products. Access to a trend export may not include the rule version or point history needed to interpret it. The customer and supplier should identify the actual deliverable for each category.

Distinguish information generated at the field device from information created by a platform calculation or human review. Record the unit, timestamp basis, quality state and identity reference. The agreement should make clear which rights and permissions apply to each category, with the customer's legal and procurement advisers reviewing the actual wording.

Define usable access rather than a vague export promise

Ask for a representative export containing a normal period, a missing-data interval, an alarm and an authorised correction. Verify that another tool can read it and that the fields retain their meaning. A spreadsheet full of values may still be insufficient if units, time zones, asset assignments or quality flags are absent.

Record available formats, request limits, retrieval windows and authentication arrangements. Distinguish a manual download from a supported API or scheduled transfer. If an integration relies on a paid tier, connector or additional service, include that dependency in the commercial comparison. The project should price the required operating workflow rather than an assumed feature.

Specify retention at each layer

Field devices, gateways and hosted applications may retain different records for different periods. Identify what is stored locally, what is aggregated and what is deleted or overwritten. A long chart history does not necessarily imply long retention of the original acquisition detail.

Agree the treatment of late uploads and corrections. The customer may need the original event time, arrival time and previous report version to reconstruct an incident. Backup, archive and ordinary application retention also serve different purposes. Ask how restoration is tested and which historical relationships survive it.

Give each service measure a boundary

Separate application availability, source-data freshness, notification delivery, support acknowledgement and restoration. An accessible dashboard can display stale readings, and a support ticket can be acknowledged before the field problem is resolved. A meaningful service measure names the function, observation point, clock and reporting period.

List excluded conditions and the evidence needed to apply them. Site power, operator subscriptions, customer-controlled networks and authorised maintenance may sit with different parties. The contract should describe those responsibilities without making the measurement impossible to reproduce. Use the actual supplier proposal for promised targets; this guide does not invent a standard response time.

Include the installation dependencies in the cost review

Identify device ownership, network-server accounts, SIM subscriptions, certificates, software licences and supplier-managed credentials. A customer can own the physical gateway while lacking the rights or information needed to operate it independently. Record which components can be transferred, reconfigured or replaced and who performs that work.

Separate recurring platform charges from instrument maintenance, connectivity, calibration and local attendance. Where a contract includes a minimum term or removal work, put those conditions into the comparison. The useful total cost follows the actual responsibilities across installation, operation and exit, rather than only the dashboard subscription.

Design an exit rehearsal while the project is healthy

Choose a bounded set of points and export their records, mappings and relevant history. Have the customer's nominated technical owner reconstruct a selected report. Check whether stable identities and effective configuration versions allow the result to be explained without access to the original account.

Document how users, privileged accounts and integration credentials will be transferred or revoked. The responsible IT team should control the method and destination for secrets; an ordinary handover spreadsheet should reference the approved process rather than contain passwords. Keep access continuity and secure removal as explicit acceptance tasks.

Preserve the meaning of records during migration

A new platform may use different asset names, units, time handling or alarm states. Establish a mapping and test representative normal, abnormal and missing observations before the customer relies on the new view. Preserve the original record identifier where possible so duplicates and omissions can be investigated.

Plan a controlled transition period with clear responsibility for each live function. Avoid assuming that importing historical data also recreates notification rules, permissions or escalation rosters. The operating team needs evidence that the required current functions work and that unresolved migration items have an owner.

Keep changes visible throughout the service

Review the agreement when a new site, data source or critical operating use is added. A monitoring service originally used for weekly reporting may later support time-sensitive responses. That change can affect retention, continuity and support requirements, so the technical and commercial assumptions should be revisited together.

Maintain a current register of service contacts, renewal dates, export procedures and recovery evidence. A practical exit plan is a maintained operating record. It should remain usable when the person who configured the original installation is unavailable.

Connect the decision to the project

Use Industrial iot, Hidden costs iot remote monitoring south africa, Iot solutions to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.

Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.

Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.

Sources and method

NIST SP 800-82 Revision 3 provides OT architecture and dependency background. This worksheet is a technical procurement aid; contractual rights, privacy obligations and service commitments require review of the actual agreement.

Frequently asked questions