1. IoT Data Analytics
  2. Data model and import order
Reference

The tables behind IoT Data Analytics

IoT Data Analytics ships with 17 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
17
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Configuration:

Organizations, People, sensor definitions and source mappings establish source ownership and effective rules.

Operations:

Sensor streams carry the lifecycle; sensor readings and source snapshots hold observation and capture context.

Execution and provenance:

Operation runs, operation steps, metric definitions and metric results explain calculations and effects. Metric observations retain observation-level values and their snapshot links.

Review and evidence:

Review decisions, evidence documents, follow up actions and state history preserve decisions and correction work.

Every table, by feature

Stream configuration

5 tablesAbout this feature
  • Sensor streams

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Sensor definitions
  • Sensor definitions

    Configured measurement and experiment definitions with effective dating.

    Linked to Organizations
  • Organizations

    Customer organizations whose web properties are measured.

  • People

    Analysts, owners and reviewers belonging to an organization.

    Linked to Organizations
  • Source mappings

    Reviewed field mappings between source and target definitions.

    Linked to Sensor definitions

Reading operations

5 tablesAbout this feature
  • Sensor readings

    Consented observation-level session and conversion event facts.

    Linked to Sensor streams
  • Sensor streams

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Sensor definitions
  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Sensor streams
  • Operation steps

    Numbered steps of an operation run with input/output and receipt state.

    Linked to Operation runs
  • State history

    Immutable lifecycle transition history for each source.

    Linked to Sensor streams, People

Anomaly review

5 tablesAbout this feature
  • Sensor streams

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Sensor definitions
  • Sensor readings

    Consented observation-level session and conversion event facts.

    Linked to Sensor streams
  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Sensor streams
  • Operation steps

    Numbered steps of an operation run with input/output and receipt state.

    Linked to Operation runs
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Sensor streams, People

Metric reconciliation

5 tablesAbout this feature
  • Metric definitions

    Approved metric definitions with grain, expressions and aggregation method.

    Linked to Sensor definitions, People
  • Metric results

    Calculated metric results persisted once per approved definition and window.

    Linked to Sensor streams, Metric definitions, Operation runs
  • Sensor readings

    Consented observation-level session and conversion event facts.

    Linked to Sensor streams
  • Sensor streams

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Sensor definitions
  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Sensor streams

Review and evidence

5 tablesAbout this feature
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Sensor streams, People
  • Evidence documents

    Supporting source evidence documents and verification state.

    Linked to Sensor streams, People
  • Follow up actions

    Assigned corrective and follow-up actions with due dates.

    Linked to Sensor streams, People
  • Sensor streams

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Sensor definitions
  • People

    Analysts, owners and reviewers belonging to an organization.

    Linked to Organizations

Execution provenance

5 tablesAbout this feature
  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Sensor streams
  • Operation steps

    Numbered steps of an operation run with input/output and receipt state.

    Linked to Operation runs
  • State history

    Immutable lifecycle transition history for each source.

    Linked to Sensor streams, People
  • Sensor streams

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Sensor definitions
  • Metric results

    Calculated metric results persisted once per approved definition and window.

    Linked to Sensor streams, Metric definitions, Operation runs

Shared and settings

3 tables
  • Metric observations

    Observation-level metric readings tied to a snapshot and source.

    Linked to Sensor streams, Source snapshots
  • Source snapshots

    Sourced snapshot captures with coverage window and freshness status.

  • Users

    Users

    Linked to Users

Keys and references

Each reading points to a parent stream. A stream points to its organization, owner and definition. A review decision and state transition point to the source revision. A metric result points to its source, definition and operation run. Keep source record identifiers stable when importing from a connected system.

Migration order

  1. Import Organizations, People and Users, then check the intended owner references.
  2. Configure sensor definitions and source mappings with their effective dates.
  3. Bring in sensor streams and attach sensor readings and source snapshots.
  4. Review metric definitions before importing observations or calculating results.
  5. Reconcile operation runs, operation steps, review decisions and supporting evidence with source revisions.
  6. Bring over open follow up actions and retained state history.

Set up IoT Data Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started