ZenTrack Power – Operations Guide

(For operations, support teams, and fleet admins)

Written By Support Team

1. Purpose & Scope

This guide explains how the ZenTrack Power behaves in day-to-day operation and what operations/fleet admins should expect once the devices are deployed.

Your deployment assumptions for this guide:

  • Trips are based on movement (not ignition).

  • Your platform receives data via your MQTT server, which is used to move data into ZenduOne.

  • BLE sensors are optional (not used in all deployments).

  • Troubleshooting is handled in a separate document.

2. What ZenTrack Power Does

Once installed and configured, the ZenTrack Power:

  • Collects GNSS data: Location, speed, heading.

  • Detects movement: Uses onboard motion detection logic (movement/vibration) to support movement-based operations and event generation.

  • Communicates via cellular network: Sends telemetry out over cellular as configured.

  • Feeds your platform via MQTT: Device data is forwarded/consumed via your MQTT server so it can be ingested and displayed in your platform (e.g., ZenduOne).

  • Monitors power: External power connected/disconnected behavior (and related alerts) is visible depending on configuration.

  • Optional BLE sensor support: BLE sensors (temperature, door, etc.) may be used for specific deployments only.

3. Daily Operations Flow

Movement-Based Operations (Trips)

  • Assets operate normally.

  • Trips/events in your platform are driven by movement, not ignition.

  • A trip begins when movement is detected and reporting criteria are met.

  • A trip ends after the configured stop/idle logic is satisfied.

Data Transmission

The device sends location and telemetry based on:

  • Movement state (moving vs stopped).

  • Reporting rules defined in configuration (time/distance/angle profiles).

  • Event triggers (e.g., towing/vibration, speeding, power loss).

  • Coverage conditions (buffering may occur in low coverage areas).

Platform Visibility

In your platform (e.g., ZenduOne), you should typically see:

  • The asset on the map with recent last-known position.

  • Movement-based trips.

  • Device telemetry where enabled (e.g., voltage/power status).

  • Events/alerts aligned to your configured rules.

In DMS, you should typically see:

  • Device online/offline state and last communication timestamps.

  • Device configuration visibility and fleet management controls.

  • Firmware management controls.

4. Operational Best Practices

  • Inventory and traceability: Maintain a clean mapping of: Asset ID ↔ Device IMEI ↔ SIM ICCID ↔ Install date.

  • Set expectations for movement-based tracking: Movement-based trips can be affected by stop duration thresholds, low-speed movement, or yard vibration.

  • Monitor for early warning signals: Watch for devices not reporting for long periods or frequent disconnect/reconnect patterns which may indicate wiring instability.

  • Use BLE only when required: Treat BLE as a deployment feature. Ensure operations knows which assets are BLE-enabled and which sensors are installed.