MDM vehicle profile configuration

BlueLightMaps supports MDM/Intune configuration to set default vehicle profiles for your organisation. These defaults are applied only on first app install and users can customise them afterward.

Important Notes

• ⚠️ Configuration on this page is only applied on first install
• ⚠️ Changing these MDM settings later will not affect existing users
• ⚠️ To apply new settings, you must uninstall and reinstall the app
• ✅ Users can customise profiles after initial setup
• ✅ Configuration applies to both emergency and non-emergency variants
• ℹ️ The routing policy keys behave differently: they are re-applied on every launch, take effect on the next app start, and lock the matching control so crews cannot change it

Configuration Keys

Choosing the right profile

Category	Use it for
Car	Response cars and other car-sized vehicles
Truck	Vans and Sprinter-type vehicles
Smooth Truck	Ambulances and patient transport (same size as Truck, avoids bumps)
Large Truck	Fire appliances: pumps, aerial ladder platforms, heavy rescue
Bicycle	Cycle responders
Pedestrian	On-foot navigation

Fire appliances should always be configured as largetruck. Dimensions decide which roads a vehicle can physically use. The profile decides how it drives them. Large Truck has the speed profile and handling of a fire appliance: it is slower than Truck on every class of road, and slowest on slip roads, residential streets and service roads. It also loses more time at junctions and turns. Truck is tuned for vans and Sprinter-type vehicles, so an appliance set up as Truck gets optimistic ETAs and can be sent on routes that are only quick in a van.

Note: Every profile is always available for crews to choose from on the device. The *_visible keys from earlier versions of this page no longer do anything and can be removed from existing configurations.

Vehicle Dimensions

Set default dimensions for truck categories (values must be strings):

Key	Type	Range	Description
truck_width	string	“1.5” – “3.5”	Width in meters
truck_height	string	“2.0” – “5.0”	Height in meters
truck_weight	string	“1000” – “35000”	Weight in kilograms
smoothtruck_width	string	“1.5” – “3.5”	Width in meters
smoothtruck_height	string	“2.0” – “5.0”	Height in meters
smoothtruck_weight	string	“1000” – “35000”	Weight in kilograms
largetruck_width	string	“1.5” – “3.5”	Width in meters
largetruck_height	string	“2.0” – “5.0”	Height in meters
largetruck_weight	string	“1000” – “35000”	Weight in kilograms

If you don’t set a profile’s dimensions, it uses these defaults:

Category	Width	Height	Weight
Truck	2.5 m	3.0 m	3,500 kg
Smooth Truck	2.5 m	3.0 m	3,500 kg
Large Truck	2.55 m	3.7 m	13,000 kg

Set all three keys (width, height and weight) for a profile. If any of the three is missing, the app ignores the other two and uses the defaults above.

The Large Truck defaults are close to a typical pump. Set your own values for anything taller or heavier, such as an aerial ladder platform.

Note: Dimensions must be provided as strings in MDM configuration due to Android restrictions format.

Note: *_weight sets the gross weight the app compares against posted limits. It does not control whether posted limits are obeyed. Emergency routing ignores weight limits by default, and by default that setting, along with any per-road exceptions, stays with the crew on the device. See Weight limits. Setting an accurate weight still matters: the moment a crew turns the exemption off, every route depends on it.

If your service needs to take that decision away from the crew, respect_weight_restrictions does it centrally. See MDM routing policy. That key is policy rather than a default, so it behaves differently from everything on this page.

Example Configurations

Fire Service Configuration

{
  "truck_width": "2.5",
  "truck_height": "3.5",
  "truck_weight": "12000",
  "largetruck_width": "2.55",
  "largetruck_height": "4.2",
  "largetruck_weight": "35000"
}