Reveal route planner limitations: adding a constraint-based engine alongside Verizon Connect

What Verizon Connect documents about route planning

Verizon Connect positions the route planning module as a planner-facing tool on top of the Reveal telematics platform. The route planning product page names the following capabilities:

• Visual, drag-and-drop route planner. Assign and reassign jobs on a map and calendar view. Built around the planner sitting in front of the screen, not an autonomous optimizer.
• Cloud optimization (RouteCloud). Cloud assistance that “analyzes millions of route options” behind the drag-and-drop UI. Single optimization runs over the planner’s current input.
• Supported constraints. Time windows, vehicle capacity, driver certifications and accommodation for overnight trips. Truck-legal routing (bridge heights, weight) is claimed.
• Dynamic routing and ETAs. The page claims “dynamic routing that accommodates disruptions” and “monitored ETAs in real time.” What that maps to as a programmatic re-optimization API is not surfaced on the public page.
• Field Service Dispatch. The FSM add-on. Third-party reviews describe it as a manager dashboard with a calendar view, drag-and-drop assignment and read receipts when the technician opens the job, designed for small and mid-size service operations.

What neither the Reveal route planner nor Field Service Dispatch positions as the lead capability is a constraint-based optimization engine across the full operational problem: an input model that spans every stop, every driver, every vehicle, every depot, every skill, every time window, every SLA and every recurring cadence in one solver run, with a documented optimization API and operator-visible assignment and load-balancing modes. Multi-depot, recurring routes and named multi-day horizons are not surfaced on the public product page. That decision layer is what eLogii adds, callable over REST.

Where the Reveal route planner and Field Service Dispatch reach their boundary

The pattern is consistent across operations where this comes up:

• Planner-as-optimizer. The planner spends the morning hand-balancing jobs across drivers, areas and skills. The Reveal planner makes the placement easy to see; the cloud assistance is helpful within a single day’s view; the placement itself is the bottleneck.
• Multi-depot rebalancing. A service or distribution organization with three or four depots needs the optimizer to treat all depots as part of the same problem. Multi-depot is not listed as a supported constraint on the Reveal route planning page; cross-depot rebalancing as a single optimization input is operator work.
• Recurring service programs at scale. Quarterly preventive, monthly inspections, contract-driven recurring visits across a large customer base. Recurring or template routes are not surfaced on the Reveal route planning page; optimization across the recurring book, interacting with reactive break-fix, is its own problem.
• Constraint-heavy commercial service. A two-driver install over three days with a customer-confirmed start window, an asset-specific skill that needs the same crew back on day three, an overnight stop. The constraints are real and there are usually hundreds of jobs to satisfy them across.
• SLA-locked work mixed with flexible. The optimizer needs to protect the SLA-locked bookings, balance the flexible ones, and re-optimize on the fly when a no-access comes in.

At a glance: a 60-driver commercial services organization on Verizon Connect

A commercial services organization running break-fix and compliance work across three regional depots. Sixty drivers in the field. Two planners. The book splits roughly 50% recurring compliance visits (quarterly preventive against contracted SLA terms) and 50% reactive break-fix on regulated equipment with SLA terms. Verizon Connect covers the telematics cleanly: GPS trail on every vehicle, ELD compliance, Coach driver scoring, dashcam record, asset trackers on plant equipment.

The bottleneck shows up in the morning. Two planners spend an hour hand-balancing reactive against recurring, reconciling yesterday’s slots against today’s actual routes, and working around the driver off sick at depot 2 by manual moves across depots 1 and 3. The Reveal route planner runs on a single-day scope because the constraint model needed to span three depots and a mix of recurring and reactive work is not the shape the planner is built around. Verizon Connect tracks the vehicle, the driver, the ELD log and the dashcam record cleanly; the cross-depot, cross-day routing decision is planner-led. Adding eLogii compresses that morning hour into a 10-minute review of a constraint-aware optimization run; Verizon Connect continues to own the GPS, ELD, driver behavior and dashcam record.

The workaround in Verizon Connect and where it breaks

The workaround is the planner, with the Reveal route planner’s cloud assistance in a supporting role. The drag-and-drop planner is good at what it’s built for and an experienced planner can carry a real operation on top of it. The cloud assistance works well when the day’s shape is a stable set of stops over a small number of drivers in a single area. The friction shows up at scale: time spent on planning grows non-linearly with the number of drivers and depots; the bus-factor of the operation is the one planner who knows the territory; cross-day and cross-depot constraints get carried in heads and spreadsheets, not in the model; recurring service programs run as separate calendars reconciled by hand. When the planner takes leave, planning quality drops visibly. When the operation grows past the planner’s capacity, the team adds planners, then more planners, and the coordination tax climbs.

None of this means Verizon Connect is the wrong tool. It means there is a constraint-based optimization decision layer the planner today (and the cloud assistance partially) is the proxy for, and eLogii owns that layer.

How eLogii’s optimization engine handles this

eLogii’s engine takes a constraint model as input and produces both assignments and routes as output. The dispatcher steers it with rules they can see; the driver executes the plan in Reveal Driver or Verizon Connect Navigation in the cab.

• Two engines. The Default engine optimizes 100 tasks in under 10 seconds for high-throughput daily planning. The Advanced engine takes more factors into account and is the choice for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Three assignment modes. Optimize Everything (creates fresh routes including all assignments), Add to Routes, Keep Existing Assignments (incorporates new stops while preserving driver assignments), and Add to Routes, Keep Existing Assignments and ETAs (inserts new stops into available slots without modifying existing stop sequences or ETAs).
• Three load-balancing modes. Most Efficient Routes (fewest vehicles), Balance the Minimum Number of Routes (across load, time, distance or stop count), and Use All Vehicles / Finish as Soon as Possible (maximize speed).
• REST-callable. All six modes are programmatic. Dispatchers can lock specific routes, manually reorder stops, or re-run with new constraints. The optimizer is not a black box.
• Rule-based re-optimization. Re-route a no-access visit to the nearest driver with the right skill, without moving any customer-confirmed bookings in the next 90 minutes. Visible to the dispatcher.

How the integration sits with Verizon Connect

Verizon Connect stays in place as the system of record for GPS, ELD, driver behavior and dashcam record. The operational system of record (FSM or ERP) stays in place for the work record. The connector between eLogii and the stack is custom-built; there is no published eLogii to Verizon Connect integration on either side. Verizon Connect documents a telematics API through the Reveal developer portal. eLogii’s REST API has 70+ endpoints including the optimization endpoints. The flow:

1. Read from the operational source. eLogii reads stops, drivers, vehicles, depots and skills from the FSM, ERP or Verizon Connect directly via the Reveal API. Recurring service programs flow in alongside the daily job queue.
2. Optimize in eLogii. The run produces routes with assignments, start times, end times, overnight stops, depot start/end, SLA respect and recurring-cadence respect. Dispatcher reviews in eLogii’s dispatch desk or accepts an Auto run.
3. Write back. Routes and ETAs are written back to the operational system. Completion data flows back for the work record, asset history and reporting. Verizon Connect captures the in-cab GPS, ELD, behavior and dashcam stream on top of the planned route.
4. Driver experience unchanged. The driver opens Reveal Driver or Verizon Connect Navigation in the cab. The routing they follow is the one eLogii planned.

Most teams complete the connector build in 3 to 5 weeks. Typical first wave: the multi-depot regional book, a large recurring service program, or the business unit where the planning surface is leaking the most.

Frequently asked questions

Does Verizon Connect have an optimization engine?

Yes, in the sense that the Reveal route planner is described as a drag-and-drop planner with cloud optimization assistance (RouteCloud) that “analyzes millions of route options.” The page documents time windows, vehicle capacity, driver certifications and overnight trips as supported constraints. What it does not surface as the lead capability is constraint-based optimization across multi-day, multi-depot operations in one solver run, recurring service programs as a first-class input, operator-visible rule-based re-optimization, or a public REST surface for the optimizer itself with named assignment and load-balancing modes. That decision layer is what eLogii adds.

What is the difference between the Reveal route planner and a constraint-based routing engine?

Reveal route planner: a planner-facing drag-and-drop tool with cloud assistance, tuned around a single day’s shape, supported constraints documented as time windows, vehicle capacity, driver certifications and overnight trips. Constraint-based routing engine: given a constraint model (skills, capacity, time windows, SLAs, depots, recurring cadences, cross-day dependencies), produce the assignments themselves against an objective, with operator-visible modes and rule-based re-optimization, callable as REST endpoints. The Reveal planner does the first cleanly for smaller fleets within a day. eLogii does both for the operations where the assignment problem spans depots, days and recurring programs. The two combine: Verizon Connect keeps the GPS, ELD, driver behavior and dashcam stack; eLogii owns the constraint-based decision layer.

When is the Reveal route planner with Field Service Dispatch enough?

When planners can comfortably make assignments by hand against the day’s shape, with the Reveal route planner’s cloud assistance filling the rest within a single-day scope and Field Service Dispatch’s calendar handling the technician communication. This covers a wide band of small and mid-size fleet operations on Verizon Connect. Outgrowth: when assignment becomes a constraint-satisfaction problem across multi-depot, recurring service programs and reactive work that doesn’t fit cleanly into a single-day planner view, rather than a planner judgement call.

How does eLogii’s optimization engine integrate with Verizon Connect?

Custom integration against the Reveal API and the operational system of record (FSM or ERP). Verizon Connect documents a telematics API through the Reveal developer portal. eLogii’s REST API has 70+ endpoints including the optimization endpoints, ApiKey auth and a full-parity sandbox. Once the connector is built: eLogii reads stops, drivers, vehicles, depots and skills from the operational systems, runs the optimization, writes optimized routes and ETAs back. The driver opens Reveal Driver or Verizon Connect Navigation in the cab; the routing they follow is the one eLogii planned.

What does eLogii’s optimization engine look like in product terms?

Two engines and six configurable modes, all REST-callable. The Default engine optimizes 100 tasks in under 10 seconds for high-throughput daily planning. The Advanced engine handles multi-depot, multi-day, long-haul and constraint-heavy operations. Three assignment modes: Optimize Everything, Add to Routes Keep Existing Assignments, Add to Routes Keep Existing Assignments and ETAs. Three load-balancing modes: Most Efficient Routes, Balance the Minimum Number of Routes, Use All Vehicles / Finish as Soon as Possible. Each is callable programmatically and visible to the dispatcher as a control they can see and steer.