TELEMETRY
Telemetry that means something chemically.
Stream controller, sensor, and lab data from the accounts you treat into one asset-scoped model. Reconcile sensor values against lab results, deliveries, and inventory — not just plot them.
WHAT IT ACTUALLY DOES
What it actually does
Multi-source ingestion
Ingest controller, PLC/SCADA, MQTT, historian, manual and LIMS lab results, and CSV/PDF water reports into one hierarchy.
Asset-scoped hierarchy
Customer → Site → Unit → Asset → DataStream — every signal belongs somewhere a field engineer can find it.
Reconciliation
Reconcile sensors, lab results, deliveries, inventory, and model state instead of treating each source as a separate chart.
Modeled-state alarming
Alarm when predicted calcite saturation crosses the deposition threshold at the hottest wall — not when conductivity crosses a number someone typed in 2019.
Fleet rollups
Dashboards and fleet views across the accounts you treat that roll up without erasing asset identity.
Export and portability
Your account data leaves with you. Export is a product feature, not a retention lever.
DATA HIERARCHY
Customer → Site → Unit → Asset → DataStream
Telemetry is useless if it is not bound to the asset that owns the risk. This is the hierarchy everything hangs on — across the accounts you treat.
Illustrative hierarchy. Not customer data.
AI SUPERVISION
AI on the telemetry layer
Supervision that checks streams against lab results, mass balance, and the chemistry model — not a raw threshold chatbot.
Sensor validation and drift detection
Cross-checks each stream against lab results, mass balance, and the chemistry model. Flags the probe that is lying before it becomes a decision.
Alarm triage and deduplication
Correlates related alarms across streams and assets into one explained event with a probable cause and a severity — grounded in modeled state where chemistry applies.
Data quality scoring
Every asset carries a confidence score reflecting how much of its state is measured, how much is inferred, and how stale the inputs are.
HOW IT WORKS
From signal to chemically meaningful state
Connect sources
Connect controllers, historians, lab feeds, and file uploads to the site and asset at the account you treat.
Scope to DataStreams
Map each measured parameter to a DataStream under an Asset — one measured parameter from one source at one asset.
Reconcile
Cross-check sensors against lab results, deliveries, inventory, and model estimates.
Compute and alarm
Feed the chemistry solver and twins; alarm on modeled chemistry state and deposition risk, not raw thresholds alone.
Export
Export history and evidence when you need it — including when you change tools or leave a chemical-major’s portal.
OUTPUTS
What you get out
- Asset-scoped time series at operating cadence
- Reconciled views across sensors, lab, deliveries, and inventory
- Alarms on modeled chemistry state and deposition risk
- Fleet rollups with drill-down to the asset
- Portable exports of your history
WHO THIS IS FOR
Who this is for
- Service companies running controllers and lab cadence across the accounts they treat
- Branch and technical teams that need fleet visibility without losing asset context
- Compliance program leads who need evidence they can hand to a customer or an auditor
- Service companies that want their own stack instead of a chemical-major’s portal
Connect the signals you already collect.
30-minute technical walkthrough — we can map a sample controller export and a lab report live.