Fleet Management for Defence

For secure logistics the location of the data is a threshold condition. A platform that stores fleet movement outside India is excluded before its capabilities are considered.

Confirm MoboSafe’s proposed hosting, backup locations, subprocessors, and access arrangements against the procurement requirements. The operations manual documents access and privacy controls, not a universal residency guarantee for every integration.

The related question is who within the organisation can see what, which is an access-control design rather than a hosting one.

Knowing where every vehicle is at all times is operationally useful and, in the wrong hands, exactly the wrong information to have available.

Role-based access limits position visibility to the roles that require it, and an audit log records who viewed what.

That log matters as much as the restriction. Access that is limited but unlogged cannot be reviewed after the fact.

A convoy is tracked differently from a set of individual vehicles. What matters is the relationship between them.

Separation beyond a threshold, a vehicle stopping while others continue, and the convoy deviating as a group are each distinct events with distinct responses.

Detecting them requires the vehicles to be understood as a group rather than as a list, and alerting to reach someone immediately rather than appearing in a summary.

Geofencing here is used for control rather than efficiency. Entry to and exit from controlled zones is recorded and alerted as it happens.

The complete movement record is the other deliverable: a timestamped history of where every vehicle went, retained for the period required and exportable for review.

Both are ordinary capabilities used to an unusual standard, which is the general shape of this sector.