Hey everyone!

We released Version 4.94.0 on Tuesday, November 11, 2025.

This release introduces a comprehensive upgrade to the Run Suggestion framework — adding multi-level configuration control (Booking, Passenger, Tenant), smarter routing validations, OSRM-based travel accuracy, and operational safeguards like load-time capping and cross-country checks for more reliable, efficient, and flexible route optimization.

Key Highlights

Booking-Level Run Suggestion Settings

Dispatchers can now configure Run Suggestion constraint settings directly from the Booking Form in the Operations screen. This allows fine-tuning of routing logic for specific bookings without altering global or user-level defaults.

• Added a Run Suggestion Settings section with a JSON editor on the Booking Form.
• Booking-level configurations override Tenant, Fleet, Account/Site, and Passenger-level settings.

• Real-time JSON validation ensures configuration accuracy.
• Configurations persist with the booking record and can be re-opened anytime.

Value Delivered

• Granular control per booking
• Accurate routing for exceptions
• Preserves higher-level defaults while allowing case-based overrides

Passenger-Level Run Suggestion Settings (CIM Screen)

Dispatchers can now manage Run Suggestion constraints at the Passenger Profile level within CIM, allowing consistent application of passenger-specific routing rules.

• Added a Run Suggestion Settings JSON editor on Passenger Profiles.
• Configuration hierarchy: Booking → Passenger → Account → Fleet → Tenant.
• Real-time validation and merge logic for overlapping keys.
• Fully backward compatible with existing configurations.

Value Delivered

• Personalization for passengers with unique routing requirements
• Simplified configuration management across profiles
• Increased accuracy for recurring passengersGranular control per booking

“No Shared Ride” Control for Specific Trips

Dispatchers can now exclude specific passengers or accounts from shared ride routing by setting “NoSharedRide”: true in the Run Suggestion JSON settings.

• Configurable across multiple hierarchy levels: Passenger, Account, Account Type, Fleet.
• Hierarchical priority ensures most specific rule takes precedence.
• Integrated with Run Suggestions using Google OR to exclude these trips.
• Default behavior remains unchanged if the setting isn’t defined.

Value Delivered

• Greater control over trip grouping and passenger privacy.
• Compliance-friendly single-passenger routing.
• Clear and flexible rule hierarchy.

Load Time Capping for Address-Based Calculations

To improve the realism of load time estimates, the system now caps Address-based Load Times to 45 minutes by default.

• Introduced a configurable cap (default: 45 minutes).
• Prevents unrealistic load times caused by data anomalies.
• Maintains backward compatibility with existing calculations.

Value Delivered

• More reliable and practical route planning
• Reduced dispatch adjustments due to inflated time estimates

Enhanced Distance Matrix with OSRM Speeds

The Distance Matrix has been strengthened with OSRM speed data integration for more accurate and resilient travel-time calculations.

• Introduced hybrid Mapbox + OSRM calculation model.
• Improved data consistency during API outages or degraded responses.
• Enhanced accuracy in travel-time predictions used in Run Suggestions.

Value Delivered

• Increased routing precision.
• More stable system behavior under load.
• Enhanced reliability for optimization engine.

Soft and Hard Constraint Classification

Dispatchers now have explicit control over constraint flexibility through Soft and Hard constraint settings.

• Added explicit Soft/Hard type for time-window constraints.
• Updated Run Suggestion engine to respect constraint type behavior.
• Fully compatible with legacy constraint definitions.

Value Delivered

• Improved flexibility in scheduling rules.
• Greater control over route optimisation behavior.
• Clearer differentiation between strict and flexible timing requirements.

Cross-Country Validation to Reduce API Overhead

Introduced geographic validation to detect and exclude routing scenarios involving multiple countries, improving efficiency and reducing invalid API calls.

• Added pre-validation check before Distance Matrix or Routing API calls.
• Trips spanning multiple countries are now marked infeasible with a clear message: “Routing between different countries is not supported.”
• System continues processing feasible trips and capacities.

Value Delivered

• Optimized API usage
• Reduced processing noise from invalid routing scenarios
• Faster and cleaner Run Suggestion execution

We value your feedback and appreciate your continued support! Thank you for choosing TOBI.