Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Device Calibration Tab

The Calibration tab is where advanced configuration and fine-tuning of telemetry input values and metadata are performed for a connected device within Perspio. This screen is primarily used by technical administrators and integration specialists to validate and adjust how Perspio interprets and aligns telemetry data for a particular device.

Purpose of the Calibration Tab

The Calibration tab allows administrators to:

  • Apply offsets to telemetry values such as Run Hours and Odometer, ensuring accuracy even when a device is installed mid-life cycle.

  • View and manage identifiers critical for integration, device tracking, and troubleshooting.

  • Confirm and edit metadata that helps link the device to the correct systems and processes within your pipeline.

Keeping this section up to date ensures that data shown in dashboards, reports, and workflows is correctly aligned with reality and that telemetry pipelines function correctly without data duplication or misalignment.

Sections in the Calibration Tab

1. Offsets

This section provides manual input fields to calibrate the device’s telemetry counters:

  • Run Hours Offset: Adjusts the base value for total operational hours. Useful when installing a device in a machine that has already been used.

  • Odometer Offset: Similar to Run Hours, allows you to enter the current odometer reading to ensure the device continues tracking from the correct value.

  • Device Fuel Used Offset: Applies a baseline value to total fuel consumption if the device was installed after the asset was already in use.

2. History Settings

  • History Enabled: A toggle that determines whether historical data should be stored and used. Keeping this enabled ensures the messages sent by the device are visible in the Messages and Message Frequency Tabs.

 

3. Device Identifiers

These are key metadata values for identifying, matching, or cross-referencing the device across Perspio and external systems:

Field Description
Device Type ID Specifies the classification of device installed (e.g., Geotab GO).
Perspio Device ID The internal identifier used by Perspio.
Perspio Pipeline ID References the ingestion pipeline this device flows through.
Pipeline Instance ID Tracks the specific ingestion job used for this device.
Serial / IMEI / UUID / MAC / ICCID Hardware identifiers for troubleshooting, manufacturer registration, and telematics validation.

 

 Fields that show N/A indicate that the data was either not available from the source or not applicable to this device type.

 

4. Vendor and Tenant Metadata

  • Vendor Internal ID: ID used by the vendor system for reference.

  • Vendor Tenant Name: Typically displays the telemetry provider or telematics reseller managing this device (e.g., Inauro).

 

5. Status Flags

These values reflect whether the device is actively used and managed:

  • Is Active: Indicates if this device is currently assigned and ingesting data.

  • Enabled: A flag for whether the device is enabled within the system.

  • Managed By: Indicates which organisation or user is responsible for the device.

 

6. Mapping Reference

  • Mapping: Shows if a telemetry mapping has been assigned or completed. If this field displays N/A, the device may not yet be fully mapped, potentially impacting data alignment.

 

How and When to Use This Tab

  • When installing new devices into assets that already have runtime or mileage.

  • If telemetry data misalignment is noticed and needs correction.

  • When needing to cross-reference identifiers for support or integration validation.

  • To audit device setup across tenant pipelines.

 

Best Practices

  • Always enter accurate offsets at installation time to ensure proper data continuity.

  • Keep identifiers and metadata up to date, especially when devices are moved or reassigned.

  • Use the history toggle with caution—disabling it may result in lost or unprocessed data.

 

For any changes made in this tab, ensure that you communicate with the relevant telemetry or fleet support teams to maintain proper alignment across integrated systems.