These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- IoT Data Analytics
- Who it's for
- Connected facilities
Connected facilities
A facilities team may have measured sources across locations. The organization and location help the Stream Owner identify where a reading belongs. The Operations Analyst reviews its collection basis and observation date before validating the source. A reviewer decision remains attached to the exact stream revision considered.
How IoT Data Analytics is set up for you
Place the source
Record the organization, location and source identity so similarly named streams do not get confused.
Match the date
Check the observation date against the sensor definition's effective interval and the snapshot coverage window when a snapshot is used.
Close the exception
Verify supporting evidence and assign due follow-up to a named person.
A facilities team may have measured sources across locations. The organization and location help the Stream Owner identify where a reading belongs. The Operations Analyst reviews its collection basis and observation date before validating the source. A reviewer decision remains attached to the exact stream revision considered.
Choose a facility source with a stable observation window. The Measurement Steward checks the definition and any mapping version; the Stream Owner links the source identity and owner. Register a normal reading and a repeated request. The Operations Analyst should find the same operation run for the repeated key, then validate the accepted scope.
Next, review a value outside its stream bounds. Confirm the saved fields by read-back before treating the anomaly run as successful. The Independent Reviewer can record a returned decision with a reason if the evidence needs work. A later correction receives a successor revision; do not apply the earlier decision to it.
The operational overview helps the Follow-up Owner find overdue work. Check the action's source, due date, status and resolution before completion. Rehearse this handoff in [implementation](/iot-data-analytics/implementation), then settle the upstream mapping in [integrations](/iot-data-analytics/integrations).
Features to start with
Roles on the team
- Stream Owner
- Owns source configuration and the collection cycle for assigned streams.
- Operations Analyst
- Validates readings, investigates anomaly outcomes and reconciles metrics.
- Independent Reviewer
- Decides source-revision reviews and checks supporting evidence.
- Follow-up Owner
- Works assigned corrective actions to a recorded resolution.
- Measurement Steward
- Maintains definitions, source mappings and approved metric rules.
Set up IoT Data Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.