Sensor-agnostic telemetry ingest for field assets
Fieldiq reads from IED/RTU telemetry, retrofit vibration sensors, temperature loggers, and historian exports via DNP3, Modbus, OPC-UA, and REST. No proprietary hardware. Handles rural intermittent connectivity without losing historical context.
What Fieldiq ingests
Fieldiq supports the full range of distribution field asset telemetry sources — existing IED outputs, RTU polling, and retrofit sensor deployments.
-
DNP3 & Modbus polling
Native DNP3 Level 2 and Modbus TCP/RTU polling from IEDs and RTUs at configurable intervals. Unsolicited response support for event-driven telemetry.
-
PI/AF historian pull
Bulk and streaming retrieval from OSIsoft PI and AVEVA System Platform tag archives. Configurable tag lists and compression deadband handling.
-
Cellular & RF mesh telemetry
Buffer-and-flush protocol for cellular-connected field sensors. Data gaps below 15 minutes are interpolated; larger gaps are flagged and timestamped for audit.
-
CSV / batch import
For utilities with existing CMMS exports or spreadsheet-based maintenance records, Fieldiq accepts structured CSV imports to bootstrap historical asset context.
-
OT-safe data path
Unidirectional data flow from field assets to Fieldiq. No inbound connections from Fieldiq to OT networks. Designed with network segmentation in mind.
-
Asset metadata enrichment
Sensor streams are tagged with asset class, manufacturer, kVA rating, installation date, and feeder ID for per-asset-class model calibration.
Supported protocols and sources
| Protocol / Source | Mode | Asset types |
|---|---|---|
| DNP3 Level 2 | Poll + unsolicited | All IED/RTU-connected assets |
| Modbus TCP/RTU | Poll | Retrofit sensors, legacy RTUs |
| OPC-UA | Subscription | Modern IEDs, substation automation |
| PI/AF REST | Batch & streaming | Historian tag archives |
| Cellular / MQTT | Push with buffer-flush | Rural pole-top sensors |
| CSV batch import | Scheduled upload | CMMS exports, maintenance logs |
Connect your existing telemetry in days, not months
Fieldiq's onboarding team handles protocol configuration, tag mapping, and historian integration. Most pilots have first telemetry flowing within 5 business days.