Baseline
Measure current volume, time, cost, failure, service, risk and revenue at the workflow level.
P32 · Implementation blueprint · Mappls Logistics Optimizer
Transportation Management, Dispatch & Route Optimisation
Manual planning and disconnected transporter, order and route data inflate kilometres, empty runs, detention and planning effort.
01 · Target operating outcome
Define the change before choosing the technology
How much freight spend is locked in empty kilometres, low utilisation and avoidable detention?
Lower freight cost, empty km and planning time; higher vehicle fill, on-time delivery and asset turns.
Target
Savings opportunity validated; planning time reduced; constraint compliance accepted; live integration path agreed.
02 · Solution architecture
One connected flow from source data to operational action
Load.ai/TMS, order/vehicle matching, route and load optimisation, dispatch, ePOD, freight workflows, ETA and control-tower analytics. Mappls connects proprietary map and location intelligence with load.ai/tms, order/vehicle matching, route and load optimisation, dispatch, epod, freight workflows, eta and control-tower analytics. We start with one measurable workflow, prove the operating impact, and scale through reusable data, APIs and SaaS rather than a one-off implementation.
Data foundation
Map, customer, asset, sensor and enterprise data
Intelligence services
Search, routing, GeoAI, rules and spatial models
Role workflows
Orders · Planning · Dispatch · Control tower · Proof
Decision and outcome
Lower freight cost, empty km and planning time; higher vehicle fill, on-time delivery and asset turns.
03 · Users and RBAC
Give every stakeholder the view and actions they actually need
Sponsor / owner
Head Logistics
Sponsor / owner
Transport Planning
Manager / analyst
Control Tower
Manager / analyst
COO
Manager / analyst
Supply Chain Director
Operator / specialist
TMS Product
Operator / specialist
ERP/SAP
Operator / specialist
Fleet Operations
Operator / specialist
Transport planner
Operator / specialist
Dispatcher
The shared Mappls identity is separated from application membership. A user can be an administrator in one app, an analyst in another and a viewer elsewhere.
04 · Data and integration
Connect the minimum information needed to make the workflow real
Location foundation
Map, road, address, place, imagery, boundary and terrain layers appropriate to the decision.
Enterprise context
Customer, order, asset, vehicle, incident, task, sensor or transaction records from systems of record.
Integration pattern
APIs, SDKs, secure batch, streaming events, webhooks, files or on-premise integration depending on architecture.
Security and control
Least-privilege RBAC, audit events, encrypted transport, tenant separation and cloud, private or offline deployment.
Recommended Mappls building blocks
Load.ai / Transportation Management
Order, vehicle, load, route, dispatch, ePOD and freight workflows
Product detailsFASTag Management
Tag, toll transaction, reconciliation and route cost workflows
Product detailsClarityX Location Analytics
Market, territory, network and spatial decision analytics
Product detailsInTouch / Gtropy Fleet Platform
Tracking, trips, alerts, ETA, fleet and control tower
Product details05 · Proof of value
Use a bounded implementation to answer the scale decision
4-6 week lane/depot pilot replaying historical loads and running live shadow dispatch.
- Confirm data, geography, users and workflow: What orders, vehicle constraints, lanes and cost rules are available? How are plans overridden?
- Configure Mappls Logistics Optimizer for the selected role set
- Run baseline and intervention scenarios with real stakeholder reviews
- Evaluate agreed criteria: Savings opportunity validated; planning time reduced; constraint compliance accepted; live integration path agreed.
- Package production scope and commercial model: SaaS per vehicle/order/user + integration/NRE + managed optimisation.
06 · Rollout and operating model
Move from proof to governed adoption
Week 0–2
Discover
Baseline, data, stakeholders, security and architecture
Week 3–6
Configure
Data connection, role workflows, rules and dashboards
Week 7–10
Prove
Live users, measurement, change support and decision review
Production
Scale
Phased geographies, integrations, service model and continuous improvement