JOpt.RoutePlanner

JOpt.RoutePlanner

JOpt.RoutePlanner is DNA Evolutions’ routing and travel-time component. It provides consistent, explainable distance/time calculations and routing outputs (turn-by-turn, geometry, summaries) — and can act as the routing backbone for JOpt.TourOptimizer and other planning systems.

Current availability: JOpt.RoutePlanner is primarily offered as a SaaS component. For access, tenancy, and integration options please contact us.

Overview

Routing quality directly impacts optimization quality. If travel times are wrong, even the best optimizer produces schedules that fail in reality.

JOpt.RoutePlanner focuses on routing correctness, profile realism, and integration-friendly APIs:

• Turn-by-turn (TBT) routing results for UI and execution systems
• Profile-based routing (vehicle types, restrictions, policies)
• Matrix routing (distance/time matrices where appropriate)
• Standard output formats (JSON, GPX, etc.)
• Built on high-performance routing engines (Valhalla-based builds)

Route planning is based on Valhalla (open source): https://github.com/valhalla/valhalla/

What problems JOpt.RoutePlanner targets

JOpt.RoutePlanner is designed for real operations:

• Logistics & transportation (fleet routing profiles, realistic ETAs)
• Field service (time-feasible schedules, consistent travel-time behavior)
• Municipal operations (waste, maintenance, service rounds)
• Supply chain and distribution (repeatable, governed routing assumptions)
• Scheduling beyond routing where travel-time is a key feasibility driver

The core deliverable is a routing layer you can trust: consistent distances, durations, and route geometry that remain stable across environments and deployments.

Special capability: On-demand connections (avoid huge matrices)

Many systems build full distance/time matrices up front — which becomes expensive quickly:

• With N nodes, a full matrix has roughly N² connections.
• At enterprise scale, that is often unnecessary and slow.

How RoutePlanner helps TourOptimizer

JOpt.RoutePlanner can be connected to JOpt.TourOptimizer so that TourOptimizer requests only the connections it actually needs, when it needs them.

This yields two major benefits:

1. Compute and memory efficiency
   You avoid computing and storing a full matrix when most connections are never used.

2. Faster time-to-first-schedule
   TourOptimizer can start planning with a smaller set of required connections and expand as the search explores new moves.

This “on-demand connections” integration is especially valuable for:

• large instances,
• iterative planning,
• constraint-heavy models where only a subset of node-to-node edges matters.

Integration and deployment

Integration options

1. As a service (recommended)
   Consume RoutePlanner via an API endpoint (SaaS / managed).

2. Integrated planning platform
   Combine GeoCoder → RoutePlanner → TourOptimizer for end-to-end planning workflows.

Common integration outputs

• travel time + distance (for feasibility and costs)
• route geometry (for map visualization)
• turn-by-turn instructions (for driver/technician guidance)
• standardized exports (JSON, GPX, …)

Getting started

Because RoutePlanner is currently offered primarily as SaaS, onboarding typically looks like:

1. Contact DNA Evolutions for endpoint access.
2. Receive base URL + credentials / tenancy configuration
3. Use the API in your planning flow (directly or through TourOptimizer integration)

If you are already using TourOptimizer:

• you can start with TourOptimizer examples and later switch routing from a simple connector to RoutePlanner-backed routing with on-demand connections.