Follow the passenger job
Keep the original promise traceable through planning, live change, delivery, and financial closeout.
About TOOSA
Keep every passenger-trip change clear.
TOOSAPassenger job lifecycle
01Request
02Plan
03Assign
04Change
05Operate
06Close out
Current eventArrival time changedNamed review required
TOOSA — Transportation Operations Software.
The operating purpose
The hardest part is often the handoff after the plan changes.
Keep the promise, plan, authority, and closeout connected.
A request may begin in one system, an assignment in another, a partner option in a message, and an invoice in later review. TOOSA centers the passenger job that connects those responsibilities. A connected record should make ownership clearer without hiding the system of record, operating risk, or exceptions.
Build around operating truth, not a perfect-path diagram.
These principles guide how TOOSA is designed, configured, and validated.
Name authority at every handoff
A shared view should clarify who owns the next decision, action, acknowledgement, and exception.
Design for failure and recovery
Stale data, rejected options, partial updates, reconciliation, and rollback belong inside the workflow.
Focus on passenger work with consequential handoffs.
A standardized operation may need a simpler tool. TOOSA’s evaluation focus is work that crosses roles, records, partners, exceptions, and closeout.
- 01
Work crosses reservations, dispatch, vehicles, crew, partners, service, or billing.
- 02
Live exceptions change passenger commitments, resource plans, or financial review.
- 03
Teams need the source, decision, action, acknowledgement, and variance to remain connected.
A literal product identity
Six named responsibilities inside one system.
TOOSA Dispatch, Fleet, Crew, Network, Billing, and Automate are products within one system.
Network coordinates partners, affiliates, vendors, and capacity. Automate describes controlled assistance, not a separate source of authority.
Explore the product responsibilities or follow the operating record. Confirm availability and production behavior during evaluation.
Start with operating reality
Show where one passenger job loses its thread.
Bring a non-sensitive description of the trigger, handoff, decision, and closeout.