All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

IoT Data Analytics
Start now
More

Features

Industries

Reference

More

IoT Data Analytics · Available now

Trace each reading from source to decision.

IoT Data Analytics tracks measured sources from configuration through readings, anomaly review and metric reconciliation. An organization owns a sensor definition and its effective dates.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewStreams collecting readings
IoT Data Analytics · Sensor streams

Streams collecting readings

validation waits for the operations analyst

New sensor stream
Sensor streams in view
6
Total device count
206
Collecting
6
NumberNameStream dateStatusDevice countDevice session count
SS-16617Cold room temperature, Reno11 OctCollecting2726
SS-32739Boiler pressure, North plant21 OctCollecting211
SS-11441Line 2 vibration, assembly28 OctCollecting396
SS-66777Loading dock humidity, Boise26 OctCollecting3917
SS-93394Water flow, east wing14 OctCollecting4011
6 of 6 records
Cold room temperature, RenoSensor streams · SS-16617
Collecting
Stream date11 Oct
Device count27
Device session count26
Decide source reviewSS-16617 · Cold room temperature, Reno

The Independent Reviewer records the decision for the source revision.

Waiting for Independent Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
17
Saved views
14
Roles with set permissions
6
Reports and dashboards
8
Features

Follow each measured source

Every feature works on the same records. Pick one to see the screen your team works in.

Stream configuration

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

  • Organization
  • Definition
  • Stream
  • Sensor streams
  • Sensor definitions
  • Organizations
  • People
  • Source mappings
Explore stream configuration
OverviewMy streams
IoT Data Analytics · Stream configuration

My streams

Sensor streams

New
NumberNameStream dateStatusOwnerRevision
SS-39228Cold room temperature, Reno30 OctConfiguredLinh Tran280
SS-34394Boiler pressure, North plant03 NovCollectingCamila Duarte770
SS-81502Line 2 vibration, assembly11 OctValidatedLinh Tran730
SS-55936Loading dock humidity, Boise24 OctAnalyzedEli Rosen520
SS-94160Water flow, east wing21 OctPublishedEli Rosen260
6 of 6 records
Cold room temperature, RenoSensor streams · SS-39228
Configured
Stream date30 Oct
OwnerLinh Tran
Revision280
Example screen with sample data
Process

From observation to result

Reading to reviewed result ships ready to use. One step needs a named approval before the work moves on: Decide source review (Independent Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Configure source

    Link the source to its owner and effective measurement rule.

    Cold room temperature, RenoSS-16617 · Measurement Steward
    Configure sourceBy Measurement Steward

  2. Collect readings

    Bring observations into the named stream with their source reference.

    Cold room temperature, RenoSS-16617 · Stream Owner
    Collect readingsBy Stream Owner

  3. Validate readings

    Check outcomes and keep the registration run traceable.

    Cold room temperature, RenoSS-16617 · Operations Analyst
    Validate readingsBy Operations Analyst

  4. Review anomalies

    Compare observed readings with effective bounds and confirm the effect by read-back.

    Cold room temperature, RenoSS-16617 · Operations Analyst
    Review anomaliesBy Operations Analyst

  5. Decide source review

    The Independent Reviewer decides on the exact source revision when approval is required.

    Cold room temperature, RenoSS-16617 · Independent Reviewer
    Decide source reviewBy Independent Reviewer
    ApprovalThe Independent Reviewer records the decision for the source revision.

  6. Calculate results

    Reconcile eligible readings with an approved metric definition.

    Cold room temperature, RenoSS-16617 · Operations Analyst
    Calculate resultsBy Operations Analyst

Start with Source setup

Inside a record

Know where readings originated

Open any sensor stream to see its follow-up actions, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Stream date, Device count and Device session count.

  2. 2
    Follow-up actions

    Each line is linked to this sensor stream.

  3. 3
    Who works on it

    Stream Owner, Operations Analyst and Independent Reviewer, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Decide source review, with who decides.

Streams collecting readingsCold room temperature, Reno
IoT Data Analytics · Sensor streams

Cold room temperature, Reno

Collecting

Log activity
1
Record details
Stream date11 Oct
Device count27
Device session count26
2
Follow-up actions

Cold room temperature, Reno

TitleDue dateStatus
Inspect Reno cold room probe04 NovOpen
Calibrate north boiler gauge28 OctIn progress
Review Line 2 bearing wear23 OctOpen
Follow-up actions
6
3

Who works on it

  • Stream OwnerManage sensor streams, sensor readings
  • Operations AnalystManage sensor readings, operation runs, operation steps, metric…
  • Independent ReviewerManage review decisions, evidence documents
5

Approvals

  • Decide source reviewIndependent Reviewer
    Approved
Example screen with sample data
Approvals

Review the exact source revision

OverviewApprovals
IoT Data Analytics · Overview

Approvals

Signed in as Independent Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SS-43757Cold room temperature, Reno
    Requested by Stream Owner
    Validated0dActions
  • SS-72941Boiler pressure, North plant
    Requested by Stream Owner
    Validated2dActions
  • SS-54286Line 2 vibration, assembly
    Requested by Stream Owner
    Validated5dActions
  • SS-27330Loading dock humidity, Boise
    Requested by Stream Owner
    Validated4dActions

Who approves what

DecisionApprover
Decide source reviewThe Independent Reviewer decides on the exact source revision when approval is required.Independent Reviewer
Approve review decisionsIndependent Reviewer
2 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens IoT Data Analytics to the work that is theirs. Pick a role to see what it starts with.

Stream Owner

Owns source configuration and the collection cycle for assigned streams.

This is the first screen this role sees.

OverviewStream status board

Stream status board

Sensor streams · Stream Owner

Configured2
Cold room temperature, RenoPine Ridge Packaging
Water flow, east wingEastbank Distribution
Add
Collecting2
Boiler pressure, North plantNorth Basin Foods
Freezer door cycles, PortlandEastbank Distribution
Add
Validated1
Line 2 vibration, assemblyMorrow Industrial Works
Add
Analyzed1
Loading dock humidity, BoisePine Ridge Packaging
Add
Example screen with sample data

Roles and permissions

Reports

See outcomes and follow-up

Review stream status, anomaly outcomes, metric history and overdue work.

Overview
IoT Data Analytics · Overview

IoT Data Analytics dashboard

This quarter

Follow-up actions in view
6
Open
3
In progress
3
Due date within 14 days
5

Sensor streams by status

How far records got this quarter

StageReachedStep
Configured41
Collecting2561%
Validated1248%
Analyzed975%

Device count by status

Sample totals per stage

10.0k0
10.0kConfigured
10.0kCollecting
6.0kValidated
4.0kAnalyzed
7.0kPublished
Example screen with sample data
  1. 01Stream lifecycle by organization

    Show stream status and owner within each organization.

  2. 02Anomaly review by stream

    Compare reading value, bounds, quality flag and anomaly score for each stream.

  3. 03Reading outcomes

    Group accepted, pending and rejected readings by parent stream.

  4. 04Metric result history

    Compare result value, status and period for each metric and source.

  5. 05Run reconciliation queue

    Show failed or reconciliation-required runs with their source revision and reason.

  6. 06Snapshot freshness

    Show coverage windows, capture dates and freshness status.

  7. 07Review decision history

    Show the decision, reviewer and source revision with reason and evidence reference.

  8. 08Follow-up due work

    Show assigned action status, due date and resolution by source.

All reports and dashboards

Who it's for

Adapt the measurement cycle

See how IoT Data Analytics fits your kind of team.

Industrial equipment monitoring

Equipment teams tracking measured streams and condition exceptions.

Connected facilities

Facility teams reviewing measurements across locations.

Device operations

Device operations teams comparing device activity and accepted readings.

Controls

Trace changes through each run

Each stage of reading to reviewed result names the role that acts and the status it records, so a change is never anonymous.

OverviewReading to reviewed result
IoT Data Analytics · Process

Reading to reviewed result

Each stage, the role that acts and the status it records

Process stages
11
Approval steps
1
Roles involved
5
Tables touched
8
Collect readings
Stream Owner
StatusConfigured → Collecting
Validate readings
Operations Analyst
StatusCollecting → Validated
RecordsState history
Analyze source
Operations Analyst
StatusValidated → Analyzed
Reading to reviewed result
  1. Start
    Collect readingsConfigured → Collecting
    Stream Owner
  2. Step
    Validate readingsCollecting → Validated
    State history
  3. Approval
    Decide source reviewIndependent Reviewer
    Review decisions
  4. Step
    Analyze sourceValidated → Analyzed
    Operations Analyst
  5. Step
    Publish and follow upAnalyzed → Published
    Follow-up Owner
Example screen with sample data

See each stage in detail

AI agent

Ask Proto about the working record

Ask Proto to prepare source review and trace a metric result.

It can

  • Stream Owner: Find assigned streams that are collecting and show their current source revision.
  • Operations Analyst: Prepare the reading scope and run history for a named anomaly review.
  • Independent Reviewer: Gather the source revision, decision history and linked evidence for a decision.
  • Measurement Steward: Compare a metric result with its definition, source window and operation run.

Stays with a person

  • A person remains responsible for the review decision and for accepting a changed measurement rule.
  • Proto can prepare the linked records and point out an unresolved run, but the named owner checks the source and evidence before changing status or approving a result.
  • Usage depends on the selected ERP.AI plan and the work Proto performs.
  • Review pricing before expanding the operating scope.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • IoT Data Analytics
  • Measurement source
  • Snapshot source
  • External step receiver
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 17 tables
17tables
  • Stream configuration5
  • Reading operations5
  • Anomaly review5
  • Metric reconciliation5
  • Review and evidence5
  • Execution provenance5
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Establish ownership

    Name the organization, source owner, analyst, steward, reviewer and follow-up owner for a pilot stream.

  2. Configure the source

    Record its source identity, effective definition, field mapping and collection basis.

  3. Rehearse readings

    Register a normal observation and a repeated request; inspect the operation key, numbered steps and outcome.

  4. Review an anomaly

    Compare a reading with its effective bounds, verify the stream read-back and record a decision for the source revision when required.

  5. Reconcile a metric

    Select an approved definition, calculate from eligible readings and inspect the persisted result and run.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for IoT Data Analytics.

All questions
How do I get started?

Click Get started, then use Proto to configure IoT Data Analytics for your business. Begin with one stream, an effective sensor definition, representative readings and the people who own validation and review.

What does a stream represent?

A stream is the measured source with its organization, owner, definition, source record identity, date, status and revision. Readings and decisions link back to it.

How are readings checked?

The analyst inspects readings linked to a stream, records their outcomes and validates the source. The registration run uses an operation key to handle a repeated request.

How is an anomaly reviewed?

The analyst compares the observed value with the effective bounds and checks the quality flag. The run is marked successful after the stream fields are read back. A required reviewer decision stays tied to the source revision.

Who makes a review decision?

The Independent Reviewer records the decision, reason and evidence reference for the exact source revision. Agree that handoff during setup.

How are metrics calculated?

A manual reconciliation uses eligible readings and an approved metric definition. The result is linked to its source and operation run, with a guard for a zero denominator.

What happens when a source is corrected?

The owner writes a successor revision. Earlier runs, state history and metric results remain available for comparison.

Can I see overdue work?

The operational overview includes an overdue follow-up exception queue. Each action has an assignee, due date, status and resolution.

Where do source readings come from?

Agree the measurement source and field mappings during setup. Snapshots record their source system and coverage window so the team can inspect the input context.

Set up IoT Data Analytics your way.

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

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appIoT Data Analytics

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.