RECURRING PROGRAMS + OPTIMIZATION ENGINE
Verizon Connect’s Reveal route planner is a drag-and-drop planner-facing tool with cloud optimization assistance, tuned around the day’s stops. The public route planning page documents time windows, vehicle capacity, driver certifications and overnight trips as supported constraints; recurring or template routes are not surfaced as a named capability. That covers a wide band of single-day fleet routing cleanly. At thousands of recurring stops a month, with SLAs that vary by contract or service line, with cadence drift to keep capacity balanced, and where the recurring program interacts with reactive break-fix for the same drivers, single-day planning is no longer the same thing as optimization. eLogii’s engine models task and route template groups as constraint inputs to the optimizer.
Our drag-and-drop route planner lets you assign and reassign jobs. RouteCloud analyzes time windows, vehicle capacity, driver certifications and accommodation for overnight trips when building each route.
From verizonconnect.com/solutions/route-planning-software. The Reveal route planner is positioned around the day’s stops. Recurring or template routes are not listed alongside the supported constraints on the public route planning page. Constraint-aware optimization across thousands of recurring stops with interacting SLAs is its own decision layer. Verified June 2026.
The Reveal route planning page covers a single-day planner-facing tool with cloud optimization assistance. The named constraints span time windows, vehicle capacity, driver certifications and overnight trips, plus truck-legal routing. The page does not surface recurring or template routes, multi-week horizons or cadence rules as documented capabilities. Field Service Dispatch, the FSM add-on, is reviewed 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.
The platform tracks the day’s stops, holds time on the Reveal planner, captures the in-cab telematics, and runs the route calculation between assigned stops (with cloud assistance filling within the day’s shape). The vocabulary is day-first: place today’s stops on the Reveal calendar, drag-and-drop to drivers, let cloud assistance fill the rest, capture the GPS, ELD and dashcam stream as the route runs.
What the Reveal route planner does not position as the lead capability is constraint-aware optimization across the recurring program at full scale. The recurring program at scale isn’t just a calendar problem; it’s an assignment problem where SLAs interact (contract anniversaries, quarterly preventive cycles, customer service agreements), cadences drift, skill requirements pin specific drivers to specific stops, and capacity has to balance across the recurring program and the daily reactive break-fix.
The recurring programs that outgrow the Reveal route planner are concrete:
In each case, the engine doesn’t replace Verizon Connect’s telematics stack. It optimizes the work that the recurring calendar produces.
A commercial maintenance service organization running monthly, quarterly and annual PMs across a portfolio of customer sites. Fifty-five drivers in the field. Around 3,500 recurring jobs per month from the contract book, plus daily reactive break-fix for the same drivers. SLA windows vary by contract: anniversaries pinned to fixed dates, calibration on a hard 6-month cycle, regulatory inspections within calendar months, commercial programs at four-week intervals.
Verizon Connect captures the telematics cleanly: GPS trail on every vehicle, ELD compliance, Coach driver scoring, dashcam record. The planning task that grows past the Reveal route planner is the balancing: reactive break-fix for the same drivers landing on top of recurring jobs; cadence drift to keep capacity even across the month; SLA windows that need protection from the optimizer rather than from a planner spotting them in time. The Reveal planner runs against today’s shape with cloud assistance, but spanning the recurring program plus reactive break-fix across multiple depots is not its lead surface. Template-group optimization absorbs cadence drift within rules, protects SLA-locked stops, balances against reactive, and outputs one plan that’s already reconciled across the book. Verizon Connect continues to own the GPS, ELD, behavior and dashcam record; eLogii owns the optimization across it.
The workaround is the same as for the wider planning problem: the planner carries it, with the Reveal route planner’s cloud assistance in a supporting role within today’s shape. Recurring jobs are managed as separate calendar entries reconciled by hand against the day’s reactive book; the planner assigns them to drivers, balances against reactive break-fix, allows cadence drift to keep capacity even, and signs off on the day. At small recurring books, this is straightforward. At several thousand recurring jobs a month, with SLAs and cadences interacting, the planner becomes the optimizer. The friction shows up as SLA misses on specific contract programs, drive-time creep on the recurring book, and over-reliance on the one or two planners who know the recurring rules best.
Recurring programs are modeled as task and route template groups feeding the optimizer. Each template carries the cadence, skill requirements, SLA windows and depot rules; the optimizer treats them as first-class inputs alongside the daily flexible work.
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) keeps the recurring calendar and the work record. eLogii reads the recurring book and reactive break-fix from the FSM / ERP, pulls vehicle and live-position data from Verizon Connect, runs the optimization across them, and writes the optimized routes and ETAs back to the operational system.
Most teams complete the connector build in 3 to 5 weeks. Typical first wave: the recurring program that is leaking the most against SLAs today, or the contract book where cadence interactions are hardest.
30-minute custom simulation with your actual recurring book, drivers and SLAs. Projected savings in drive time, SLA hit rate and planner hours.
Not as a named capability on the Reveal route planning page. The Reveal route planner is described as a drag-and-drop planner with cloud optimization assistance tuned around the day’s stops. Recurring or template routes are not surfaced on the public product page. The assignment and route within a single day is handled by the planner, with cloud assistance filling within that day’s shape. What it does not position as the lead capability is constraint-aware optimization across thousands of recurring jobs with interacting SLAs, cadences and skill requirements, balanced against daily reactive break-fix for the same drivers in one solver run. That decision layer is where eLogii adds value.
Recurring job calendar: a list of jobs at the right cadence (monthly preventive, quarterly compliance, weekly commercial maintenance) created in the operational system or a separate calendar. Recurring program optimization: take the calendar entries, plus the daily reactive break-fix, plus the driver pool, plus the SLAs and cadences, and decide assignments and routes that respect all of them at once. The Reveal route planner and the operational system can produce the calendar. eLogii does the optimization, modeled directly through task and route template groups that feed the optimizer as constraint inputs.
When the recurring program runs to hundreds or thousands of jobs per month, when SLAs vary by contract or service line, when cadence drift (a stop shifting from week 1 to week 2 to keep capacity balanced) becomes a planning task, when the Reveal planner’s single-day scope can’t span the recurring program plus reactive break-fix in one run, and when the recurring program interacts with daily reactive break-fix for the same drivers. PM programs across hospital networks, multi-site PMs for industrial customers, recurring commercial maintenance contracts, inspection programs across regions: each of these hits the optimization decision layer rather than the day’s calendar.
Through task and route template groups: weekly, monthly, quarterly and bespoke cadences are modeled directly as inputs to the optimizer. Each template carries skill requirements, time-window constraints, SLA targets and cadence rules. When the run happens, the optimizer balances the recurring program against the daily flexible work, protects SLA-locked stops, allows cadence drift within rules, and outputs one consistent plan. Bristow & Sutor routes 200,000+ recurring case visits per year on eLogii.
Custom integration against the Reveal API and the operational system of record (FSM or ERP). eLogii reads the recurring calendar and the daily reactive book from the operational systems, plus the driver / vehicle / depot model. The optimization run considers them together. Routes and ETAs are written back; the driver opens Reveal Driver or Verizon Connect Navigation in the cab and follows the assigned route. Completion data flows back. Verizon Connect captures the in-cab GPS, ELD, behavior and dashcam stream. Typical connector build: 3 to 5 weeks.
Last updated: June 2026. Verizon Connect scope is drawn from the Verizon Connect route planning page, Reveal apps page and Tech.co Field Service Dispatch review. eLogii capabilities documented at elogiiapidocs.apidog.io.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real jobs, depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you plan today. No slides, no generic benchmarks.
