What is Maven Route Planning?
Route optimization engine for both analysis and daily operations
CONTENTS
-
What the product does
-
Who uses it
-
Where it fits in the workflow
-
Key concepts & terminology
-
What the product does NOT do
What this product does
-
Takes orders/stops plus constraints (time windows, capacities, rules)
-
Automatically builds efficient routes
-
Is used in two main ways:
-
Route Planning (Value Assessments / What‑ifs) – compare a customer’s current routing to “Maven‑optimized” routing
-
Inbound Planning (Daily Operations) – generate tomorrow’s route plan that will flow into Dispatch
-
Who uses it
-
Sales / solutions teams
-
Run Route Planning value assessments and ROI studies for prospects
-
-
Planners / dispatch leaders
-
Use Inbound Planning to create the daily/shift route plan
-
-
Operations leaders / analytics
-
Review KPIs (routes, miles, hours) and use scenarios for decision‑making
-
Where it fits in the workflow
A. Route Planning (Value / What‑If Mode)
-
Input: historical or extracted live data (orders, routes, constraints)
-
Engine: Maven optimizes routes on that dataset
-
Output: comparison of current vs Maven‑planned KPIs (routes, miles, hours, cost)
-
Used for:
-
Sales ROI/value stories
-
Scenario and network what‑if analysis
-
B. Inbound Planning (Operational Mode)
-
Input: live or near‑term inbound work (orders/stops) plus business rules
-
Engine: Maven builds a proposed plan for tomorrow’s routes
-
Planners/dispatch leaders:
-
Review and adjust the proposed plan
-
Approve routes and push them into Maven Dispatch
-
-
Dispatch then sends routes to drivers via the Maven Driver App and manages same‑day changes
Route Planning = “How good could your routing be?”
Inbound Planning = “What should tomorrow’s routes be so Dispatch can run the day well?”
Key concepts & terminology
-
Optimization run – a single execution that converts eligible work into routes
-
Baseline – the customer’s current or historical routing plan
-
Maven‑optimized plan – routes produced by the optimization engine
-
Constraints – time windows, capacities, geography, driver rules, customer rules, etc.
-
Proposed plan – the draft set of routes from an Inbound optimization run
-
Approved plan – the final plan planners/dispatch accept and send to Dispatch
-
KPIs – (Key Performance Indicator), number of routes, miles driven, driver hours, cost or other metrics
- ROI - (Return on investment), measures how much value you gain compared to what you spend
What this product does NOT do
-
Act as the live, day‑of dispatch UI – that is Maven Dispatch
-
Provide the driver execution workflow – that is the Maven Driver App
-
Replace your TMS – it consumes orders/stops and constraints; it does not manage the full order lifecycle, rating, or billing
-
Serve as the primary fleet visibility or compliance tool – that’s Maven Fleet and Maven ELD