Operations
Fleet Management
Manage vehicles, trailers, dollies, trips, geofences, services, incidents, faults, documents, users, support, chat, and reports.
- Vehicle records
- Trips and assets
- Service and faults
Run Fleet Management, Compliance Management, EWD, live GPS, TCA/TMA/RIM evidence workflows, and Teltonika FMC650 tracker operations from one connected platform.
Phone GPS, telematics, or hybrid trip evidence
Assumed configurable device position cadence
Plus TPAA and Road Train foundations
Product tracks
The local fallback content combines the strongest v1 public message with the v2 module map, so the same JSON can later be published from MCP or the API.
Operations
Manage vehicles, trailers, dollies, trips, geofences, services, incidents, faults, documents, users, support, chat, and reports.
NHVR and chain of responsibility
Keep EWD, fatigue, driver records, pre-start checks, breach visibility, exports, and audit evidence close to the operational workflow.
Devices
Use the referenced Teltonika FMC650 (FMC650) path where a vehicle needs continuous position evidence beyond phone-only GPS.
Visibility
See active vehicles, routes, location history, geofence movements, and last-known status from mobile or telematics data sources.
Mobile
Drivers handle trip starts, work/rest activity, pre-trip checks, faults, support, and offline capture in the mobile app.
Back office
Export work diaries, breach records, trip data, documents, and operational reports for record keepers and audits.
TCA/TMA/RIM
Trackify v2 separates software subscription value from regulatory telematics obligations. The public language is careful: the site describes supported workflows and evidence paths, not an unconfirmed certification number.
Vehicle enrolment, device state, endpoint/API key configuration, position record sync, sync logs, and manual reconciliation.
Public content names Higher Mass Limits, PBS vehicle/mass monitoring, OSOM, TPAA, and Road Train Monitoring as the target scheme families.
Road Infrastructure Manager and road-manager reporting language is included where access conditions depend on location evidence.
Compliance operations snapshot
A CMS-managed version can later replace these rows with live scheme, device, and pricing content.
HML, PBS, OSOM, TPAA, Road Train
Mobile, telematics, hybrid
Trackers and devices
The FMC650 tracker story is visible on the website because some operators need continuous vehicle position records, not only mobile app trip data.
Inventory, company assignment, vehicle link, install status, warranty metadata, and decommission states.
Device health, last seen, last location, firmware/config metadata, and vehicle-level assignment.
Trips can use mobile, telematics, or hybrid sources so drivers still have a fallback if hardware goes offline.
FMC650 deployment path
Supply, configure, register, assign, install, and monitor the tracker across superadmin and customer workflows.
Launch path
The content model supports both a simple software signup and a quoted device/compliance onboarding path.
Set company, fleet size, fatigue scheme, roles, billing model, and the powered vehicles that drive subscription usage.
Bring in drivers, vehicles, trailers, dollies, documents, pre-start checklists, and reporting requirements.
For TCA/TMA/RIM or hardware-backed live GPS, configure Teltonika FMC650 devices and link them to vehicles.
Drivers capture work and trips while record keepers monitor breaches, devices, live locations, and audit-ready reports.
Commercial model
These are explicit local fallback assumptions so the site is useful before MCP/API-managed pricing is live.
Monthly software subscription for active powered vehicles, based on the v1 public pricing model.
per powered vehicle / month
Public placeholder until final v2 commercial approval.
Annual subscription for operators that want the current v1 annual price baseline.
per powered vehicle / year
Uses v1 public annual baseline for local marketing fallback content.
Quoted onboarding for complex fleets, accreditation obligations, and telematics rollouts.
quoted for your fleet
For fleets over 20 trucks or any rollout with regulatory telematics scope.
Optional tracker and compliance add-ons
These add-ons are local fallback assumptions for review before MCP/API-managed pricing is published.
+$399 once-off per vehicle
Assumed hardware, configuration, and assignment package for vehicles needing hardware-backed GPS and regulatory telematics.
+$19/month per tracker
Assumed recurring monitoring cost for connected trackers, SIM/data management, online/offline status, and last-seen checks.
+$29/month per enrolled vehicle
Assumed compliance monitoring add-on for vehicles enrolled in TCA/TMA/RIM evidence workflows. Complex setup is quoted.
Assumptions to confirm
Blog
Blog posts are rendered from structured blocks so future CMS imports can share the same renderer.
Trackify v2 brings the old paperless compliance message into a wider operating model for drivers, record keepers, and business owners.
Public product language should show the evidence workflow for TCA, TMA scheme families, and RIM access-condition support without overclaiming certification status.
The referenced Teltonika FMC650 path gives Trackify a clear device lifecycle story for hardware-backed live GPS and regulatory telematics.
Questions
FAQ content is local JSON today and ready to move behind MCP/API publishing later.
No. The local content describes Trackify's TCA/TMA/RIM workflow support and evidence path. Final accreditation status, certification number, and approval wording must be confirmed before publishing production claims.
No. The platform can support mobile GPS, telematics GPS, or hybrid tracking. FMC650 trackers are positioned for vehicles that need hardware-backed live GPS or regulatory telematics evidence.
The baseline software subscription includes admin portal, driver app, fleet records, trips, EWD/work diary, fatigue workflows, live tracking, geofencing, reporting, documents, faults, incidents, service tracking, users, billing, and settings.
Tracker and compliance add-on prices are explicit placeholders so buyers understand the commercial model. They should be replaced by MCP/API-managed published pricing once confirmed.
Start with the software trial, or talk to Trackify about FMC650 tracker deployment, TCA/TMA/RIM monitoring, and enterprise onboarding.
Local fallback pricing is assumed and must be confirmed before production publishing.