THE SOLVER IN YOUR WORKFLOW

See the plan.
Understand the choices.

A solver needs a useful working surface: the inputs, the configuration, the proposed plan and the reasons to accept or revise it. These examples show how routing and rostering can feel in a browser.

Interactive illustrations · sample data

These simplified views are based on TaskTransit and Helixor Scheduler source workflows. They are not screenshots, live solves or claims of production availability. Switch a vehicle or day to explore the presentation; the sample plans do not change.

01 / ROUTING & DISPATCH

From jobs to
a route you can review.

Inspired by TaskTransit’s dispatch optimizer: manifest-defined inputs, hard and soft constraints, objective settings and vehicle routes in one workspace.

Dispatch planningIllustrative workspace / sample plan
Depot123456Schematic map · no geographic or travel-time claim

Use directly: a dispatcher prepares jobs and fleet records in a provisioned hosted workspace, configures the supported model and reviews routes before dispatch.

Build into your product: your transport application sends the same kinds of structured records through the API and renders route results in its own map and job list.

Explore service integration →
02 / WORKFORCE ROSTERING

A week of work.
The details behind it.

Inspired by Helixor Scheduler’s weekly planning grid and day drill-down: employees, shifts, coverage, availability and assignment issues remain close to the plan.

Weekly rosterIllustrative workspace / sample assignments
Select a day to inspect the example
Person
AlexAMAM—PMPM
SamPM—AMAM—
Jordan—PMPM—AM
CaseyAMAM—PMAM

AM = morning · PM = afternoon · — = unassigned in this illustration

Use directly: a planner works in the hosted schedule, reviews coverage and assignment warnings, and revises the plan before operational use.

Embed: a Python application calls the supported local rostering entry point, then presents assignments and diagnostics in its own calendar or planning tool.

Explore embedded rostering →
SAME MODEL, DIFFERENT WORKING SURFACES

Let the manifest shape the experience.

TaskTransit’s optimizer reads input definitions, constraint types, presets and objective settings from its manifest. A domain UI can present those controls in the language of the operation. An agent can help draft the configuration; validation and review still decide what is enabled.

See the agent authoring workflow →

Choose how you want to work.

Start with a hosted walkthrough, or bring your existing application.