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

Mapping Tab

The Mapping tab within the Devices section of Asset Configuration provides a detailed breakdown of how telemetry data received from a device is linked to specific fields in Perspio. This tab ensures that data collected from connected hardware is interpreted correctly by the platform, enabling reliable reporting, analytics, and automated actions.

Purpose

The purpose of the Mapping tab is to define and visualise the transformation of raw telemetry values into structured, usable fields within Perspio. Each telemetry field from the device is aligned to a specific internal schema field through a structured JSON mapping.

How to Access

Navigate to:

Assets → Select an Asset → Devices tab → Select a Device → Mapping tab

 

Overview of the Mapping Tab

This tab presents the full JSON mapping configuration used to link telemetry data to Perspio fields. The mapping is displayed in a read-only code block and contains the following key sections:

1. sourceTwinId and targetTwinId

  • These fields represent the unique identifiers for the data source (device) and target (asset).

  • Ensures that data flows from the correct origin to the appropriate asset.

2. isPrimaryLocationProvider

  • A Boolean flag that indicates whether this device provides the primary location data for the asset.

3. relatedProperties

  • Lists relationships between this mapping and associated devices, primarily referencing the device ID.

4. propertyMap

  • This is the core of the tab. It defines how telemetry fields from the source device map into Perspio’s internal structure.

  • Each key-value pair links a telemetry tag to one or more internal field names.

Example mappings:

 
"crankingVoltage": "crankingVoltage",
"engineCoolantTemp": "engineCoolantTemp|coolantTemperature",
"fuelLevelPct": "fuelLevelPct",
"externalBatteryVoltage": "externalBatteryVoltage"
 
 
This means that when data is received for engineCoolantTemp, it will populate both engineCoolantTemp and coolantTemperature fields in the platform.

 

Practical Use Cases

  • Field Validation: Verifying that device tags align with expected Perspio field names.

  • Troubleshooting: Investigating telemetry discrepancies or data not appearing in the UI.

  • Custom Integrations: Reviewing field compatibility when integrating third-party telemetry providers.

 

Important Considerations

  • The mapping configuration is generated based on the selected device’s schema and source system.

  • Incorrect mappings can lead to data gaps or mismatches in dashboards, alerts, and workflows.

  • Changes to the mapping are typically managed by the technical support or platform configuration team.

  • This tab is read-only and should be used for reference. Updates, if needed, should be coordinated with your Customer Success Manager.

 

If any telemetry values are missing, misaligned, or misreported, reviewing this tab should be your first step in diagnosing the issue.