1. IoT Data Analytics
  2. Features
  3. Stream configuration
Feature · Stream configuration

Stream configuration

Set the source, owner and effective measurement rule before collection begins.

OverviewMy streams
IoT Data Analytics · Stream configuration

My streams

Sensor streams

New
NumberNameStream dateStatusOwnerRevision
SS-39228Stream 39022 OctConfigured280
SS-34394Stream 71226 OctCollecting770
SS-81502Stream 98903 OctValidated730
SS-55936Stream 30716 OctAnalyzed520
SS-94160Stream 98613 OctPublished260
6 of 6 records
Stream 390Sensor streams · SS-39228
Configured
Stream date22 Oct
Revision280
Example screen with sample data

What you can do

Configure the measurement source

The Admin records the organization and its people. The Measurement Steward maintains the active sensor definition. The effective dates and policy reference tell the Stream Owner which rule belongs to a stream on a given collection date. A source mapping records the originating field, target field and transform rule when values enter from another system. The stream carries its source record identity, owner, definition, date and current revision.

How the work is organized

  • Organization. The Admin keeps the organization and active people available for ownership.
  • Definition. The Measurement Steward sets effective dates and reviews each mapping version.
  • Stream. The Stream Owner links the source identity, definition and owner before collection.

A stream is the working context for readings, anomaly review and reconciliation. Keep its revision visible so later decisions point to the version that was actually reviewed. The setup record gives a reviewer a path back to the organization, definition and owner.

What to agree during setup

Agree how source identities are assigned and how a changed definition becomes effective. If two source fields look alike, resolve their mapping before readings arrive. Decide who may retire a definition and who checks the change against existing streams.

Test a source dated just before a definition change, then one dated just after it. The Measurement Steward should identify the applicable definition for each date. The Stream Owner should identify the mapped source field and confirm the intended owner and organization on both streams.

Check the handoff on an actual case

Consider a stream whose observed date falls near a definition change. The owner checks the effective interval and the source record identity, then confirms that the intended organization and definition are linked. If a mapping changed, the steward inspects its version and effective date before the next collection. The stream is ready to collect only when the owner can explain the applied rule.

Have the Operations Analyst open the configured stream before registering a reading. Ask them to name its source identity and effective definition. If the mapping version changed after the stream date, the Measurement Steward checks which version applies before the analyst continues.

What your team sees

  • My streams — Streams assigned to the current owner, with their date, status and revision.
  • Stream status board — Sources grouped by their current lifecycle state.

Follow the work through

See the related process for the handoff and the data model for the connected records.

What it keeps track of

Data model
Sensor streams
Measured web properties with lifecycle status and observed outcome fields.
Sensor definitions
Configured measurement and experiment definitions with effective dating.
Organizations
Customer organizations whose web properties are measured.
People
Analysts, owners and reviewers belonging to an organization.
Source mappings
Reviewed field mappings between source and target definitions.

Who uses it

Permissions
Measurement Steward
, Stream Owner, Admin.

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