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

Devices VS Assets

Perspio ingests data via configurable connectors, which bring in telemetry from diverse devices. Those devices map to real-world assets, allowing you to monitor and manage equipment holistically—even when replacing or combining trackers.

In Perspio, a device is any telemetry-producing unit, whereas an asset is a Perspio object representing the complete operational entity. Assets may ingest data from zero, one, or many devices—and even fully non-telemetry sources like ERP or CRM—so that you always have a single view of your real-world equipment.

1. Connectors

Connectors are Perspio’s integrations that ingest data from external systems and devices, translating messages into Perspio’s format for location, odometer, temperature, and more.
Perspio currently offers two connector libraries—Perspio Ingress and Perspio Data to cover data acquisition, processing, and automation workflows.
The Ingress connector library includes ‘out-of-the-box’ integrations for third-party trackers and OEM servers, with new connectors added regularly to support seamless data acquisition

Perspio Actions are used for notifications and other triggered actions within workflows—ranging from basic email/SMS alerts to advanced updates in third-party systems (e.g., writing a toll charge to an ERP contract).

Additionally, Perspio provides Device Vendor connectors (e.g., Teltonika, Geotab, Digital Matter) that capture telemetry directly from devices or their cloud platforms:

  • Perspio Ingress
    Ingest real-time telemetry from edge devices, telematics platforms, and other OT (Operational Technology) systems.

  • Perspio Data
    Integrate with enterprise systems (IT systems) such as ERPs, CRMs, HRISs, and other data repositories.

  • Perspio Actions
    Trigger downstream workflows or notifications in third-party services based on Perspio workflows.

Below is a breakdown of the most widely used connectors, organized by category.

1.1 Ingress Connectors

Purpose: Stream live data from devices, OEM clouds, and industry platforms into Perspio.

  • Device-Push (TCP/MQTT)

    • Teltonika

    • Digital Matter

  • OEM Cloud APIs

    • Geotab REST API

    • Senquip HTTPS

    • Thinxtra HTTP/MQTT

  • Connectivity Providers

    • Cisco Jasper Control Center REST API

    • Soracom REST API

1.2 Data Connectors

Purpose: Pulling batch and transactional data between Perspio and enterprise back-office systems.

  • ERP / Finance

    • SAP, Oracle, Microsoft Dynamics (via REST or SOAP).

  • CRM / Marketing

    • Salesforce, HubSpot, Zoho CRM.

  • HRIS / Workforce

    • Workday, ADP, BambooHR.

  • Logistics & Service

    • Service Jobs, Transport Dockets, Transport Docket Lines.

  • Custom SQL / JDBC

    • Connect to any database through JDBC driver.

1.3 Action Connectors

Purpose: Automate actions (emails, SMS, device commands) in response to Perspio events.

  • Email / Notification

    • SMTP, SendGrid, Mailgun.

  • SMS / Voice

    • Twilio, Nexmo.

  • Webhook / API

    • Generic HTTP/S calls.

  • Device Commands

    • OTA firmware update triggers, remote configuration.

1.4 Device Vendor Connectors

(Data captured directly from device hardware or their cloud systems — all “push” or “pull” integrations.)

  • Digital Matter (Receiver – HTTPS/TCP push from OEM server or device).

  • Teltonika (Receiver – TCP/MQTT push from device).

  • Geotab (Requester – pull via REST API).

  • Teletrac Navman (Requester – pull via REST API).

  • Senquip (Receiver – JSON push from REST API).

  • Netstar (Pinpoint) (Requester – pull via message queue).

  • Trackunit (Requester – pull via REST API).

  • Watt Watchers (Requester – pull via REST API).

  • EROAD (Requester – pull via REST API).

  • Deep Sea Electronics (Receiver – TCP push from device).

  • BlueCats (Requester – pull via REST API).

  • Nube IO (Receiver – HTTPS push from device gateway).

  • Orbcomm (Requester – pull via REST API).

  • Cal/Amp (Receiver – TCP push from device).

  • Definium Tech. (Receiver – TCP push from device).

1.5 OEM Platform Connectors

(Third-party telematics platforms — “dealer-provisioned” APIs for large OEM fleets.)

Examples:

  • JCB LiveLink (dealer-provisioned API).

  • JLG ClearSky (dealer-provisioned API).

  • Atlas Copco FleetLink (dealer-provisioned API).

  • CASE SiteWatch (dealer-provisioned API).

  • Cooltrax (dealer-provisioned API).

  • Volvo (dealer-provisioned API).
  • CAT (dealer-provisioned API).

 

2. Devices

A Device in Perspio is the physical tracker or sensor hardware sending telemetry—each identified by a unique Device ID, IMEI, or tracker code.
Key device attributes include Last Seen timestamp, battery voltage and other hardware-reported metrics.
Devices are registered automatically upon first message receipt and transition through statuses such as Active, Offline, or Inactive based on reporting frequency.

3. Representing an Asset

An Asset is the digital representation of the real-world item you’re monitoring (e.g., vehicle, AED, generator) and may have one or more devices linked to it.

In the Assets menu (Map Pin Icon under Home), assets are grouped and displayed by GPS tracking or recorded address for untracked items.
Within an asset’s details, you can configure preferred data sources—such as odometer, run hours, or custom counters—by selecting among linked devices.

Assets Without Telemetry

Not every operational item emits telemetry. You can register Non-Telemetry Assets in Perspio—assets with zero linked devices—to track items managed in back-office systems alone. This approach ensures non-telemetry assets are first-class citizens, enabling you to mutualise reporting, workflows, and compliance checks across your entire asset base.

Run Hours and Odometer can be manually logged or added via ERP, Inspection systems integration, so that information can be leveraged in the Servicing Module

Merging Devices into One Asset

When you replace a tracker, add secondary sensors, or consolidate historical data, merging devices under one asset preserves continuity, please contact our support team: support@inauro.io