1.0.2 - Backup Vehicle Status and Organization-Level Vehicle Settings Fixes

‍

Improved Vehicle Sharing Across Organizations

This release improves how shared vehicles are managed across multiple organization accounts and introduces a new Backup Vehicle status. Organization-level vehicle settings such as in-service date ranges and depot locations are now saved and applied more consistently, while routing continues to prevent scheduling conflicts across organizations. Additionally, we have added a new Backup Vehicle status that gives teams greater control over when vehicles are automatically assigned versus manually used.

Vehicle Settings Page

Bugfix: In-Service Date Range Settings

• Previously, when a vehicle was shared between organizations in different locations, updating the vehicle’s in-service date range settings in one organization could unintentionally update it for both.
• In-service date range settings are now stored and applied at the organization level, allowing each organization to maintain its own configuration for shared vehicles.
• This fix ensures that routing and operational logic accurately reflects organization-specific in-service date range settings.
• As part of this release, all existing in-service date ranges for a given vehicle were standardized to the most recently configured date range.
• Routing will continue to respect vehicle usage across organization boundaries.

Bugfix: Depot Location Settings

• Previously, when a vehicle was shared between organizations in different locations, updating the vehicle’s depot location in one organization could unintentionally update it for both.
• Vehicle depot location settings are now stored and applied at the organization level, allowing each organization to maintain its own configuration for shared vehicles.
• This fix ensures that routing and operational logic accurately reflects organization-specific depot settings.

New Feature: “Backup Vehicle” Status

A new Backup Vehicle status has been introduced to the Vehicle Settings page to provide greater control and flexibility during operations.

• Vehicles set to Backup Vehicle status will not be assigned automatically to routes.
• Backup vehicles can still be manually selected when needed from the Dispatch or Trip Requests pages.
• Routes configured to use a backup vehicle will continue to automatically route with that vehicle.
• Adding or removing trips on a route using a backup vehicle will not affect the vehicle assignment.
• Vehicle settings are stored at the organization level, so a shared vehicle set as a backup for one organization will not affect its status or settings in another organization, where it may be set to In Service or Out of Service.
• In rare cases where a backup vehicle does not have sufficient capacity, and another vehicle is available and in service, auto-routing or custom routing may switch to a different vehicle to accommodate the additional capacity.

Reports

Bugfix: Demand-Response - Route Path

• Previously, selecting a route would sometimes result in route paths failing to load.
• Route paths now load reliably, and performance improvements significantly reduce load times.

‍