Telemetry Ingestion
Telemetry ingestion is the process of collecting data from machines, vehicles, or sensors and bringing it into one place so you can see what’s happening instantly. Whether it’s a temperature reading from a remote pump or an engine fault code from a delivery truck, that information flows automatically into Perspio, letting you spot issues early, schedule repairs fast, and keep a clear record of every step—all without using spreadsheets or notes.
What Do We Mean by Telemetry Ingestion?
Telemetry ingestion is the process that automatically collects data from devices—anything from environmental sensors to vehicles, pumps and third-party events—and brings it into a single platform for you to review and act on, delivering real-time, timestamped streams of metrics, logs, and alerts.
How Do We Ingest Telemetry Data?
We can bring in telemetry straight from the device manufacturers themselves—using hardware from companies like Digital Matter, Teltonika, or Milesight—or tap into data already embedded by OEMs such as Geotab, Teletrac Navman and Cooltrax.
-
Direct from Devices: We pull raw metrics, GPS, sensor readings and more via APIs or lightweight collectors on trackers from vendors like Digital Matter (asset trackers and IoT gateways), Teltonika (vehicle and asset GPS trackers), and Milesight (LoRaWAN® sensors, gateways, and controllers).
-
Via Device OEMs: For vehicles or equipment with factory-installed telematics, we integrate with platforms such as Geotab’s embedded OEM data feeds, Teletrac Navman’s onboard TCU connections, and Cooltrax’s refrigerated-fleet sensors.
This approach ensures we capture every data stream—whether it’s a rugged asset tracker in the field or a vehicle’s built-in telematics—so Perspio unified, end-to-end view of your assets in a single environment.
What Data Do We Like to Have?
To unlock Perspio’s full capabilities, ingest the following fields consistently:
-
Asset/Device ID: Globally unique identifier.
-
Timestamp: ISO 8601 in UTC for ordering and synchronization.
-
Location: GPS latitude & longitude for geospatial analytics.
-
Sensor Readings: Temperature, voltage, fluid levels, etc.
-
Operational Status & Events: Engine on/off, door open/closed, fault codes.
-
Metadata: Firmware version, device model, device manufacturer and etc.
What Data Do We Push Back In?
Perspio supports bidirectional workflows by writing enriched data back into source systems:
-
Event Acknowledgements: “Incident logged,” “Task assigned.”
-
Command & Control: Remote lock/unlock, reboot and mode changes.
-
Analytics Outputs: Predictive maintenance forecasts, utilization scores.
-
Enriched Attributes: Resolved asset names, category tags, region labels.
Which Connectors Exist Now?
Explore our full Connectors Catalog:
More connectors will be added overtime.
For assistance with a new integration or to suggest additional connectors, please contact support@inauro.io.