IVMS | Notion

<aside> CONTENTS

</aside>

In-Vehicle Monitoring System (IVMS) is the dedicated live monitoring interface within the Tepra ecosystem. It transforms foundational asset and configuration data from Tepra Core into actionable intelligence. Designed for operational visibility, IVMS enables fleet supervisors and operations teams to monitor real-time movement, driver behavior, and signal activity, while also providing tools for historical investigation, alerts, and reporting.

Prerequisites

To use IVMS effectively, ensure the following prerequisites are met:

Assets are created in Tepra Core: Vehicles, drivers, trailers, and groups must be registered and assigned (active not archived).
Devices installed and configured: Tracking devices must be installed on vehicles and reporting properly.
Permissions assigned: Users must have the appropriate IVMS permissions via Tepra Core (see Permissions Summary).
Zones and Places defined: Geofences need to be created in Tepra Core for use in monitoring and event detection.
Subscribed to IVMS: The IVMS application must be active and assigned to users through Tepra Core.

Purpose & Functionality

IVMS enables:

Live monitoring of vehicles, trailers, and assets.
Visual representation of trips, parked durations, and movement patterns.
Signal-based monitoring (e.g., ignition, speed, RPM, ACC status).
Replay and investigation of previous trips and events.
Custom dashboards to visualize operational KPIs.
Event creation, management, and response.
Access to driver and vehicle-level analytics.
Alert and notification monitoring.
Access to historic and scheduled reports.
Real-time filtering of monitored assets and driving behavior.

Integration Across Modules

IVMS depends on several components from Tepra Core:

Assets: Vehicles, trailers, and drivers configured in Core are available for live tracking in IVMS.
Groups & Ownership: Filtering and access in IVMS respects group structure and permissions defined in Core.
Zones: Geofences created in the Locations section of Core are utilized in event triggers and visual overlays.
Accounts & Permissions: Role-based access to IVMS functionality is determined by the permissions granted in the Core Accounts module.

Likewise, IVMS data supports other modules:

Fleet: Events generated by IVMS can create cases or logs in the Fleet module.
Reports: Data collected by IVMS is reflected in system-wide analytics and operational reports.