Scenarios and four-eyes approval

See the decision before you make it

Scenarios let you try changes such as "merge lines", "change vehicle type", "new shift" or "line redesign" without touching live data. Each scenario is compared by its impact on daily kilometers, number of vehicles, average ride time and monthly cost.

Change sets and the four-eyes principle

• A scenario you are happy with is converted into a change set.
• The change set is applied only after approval by an authorized person other than the one who prepared it (enforced at the database level).
• The approver can add a note, reject it or request corrections.
• Every step is written to the audit log: who changed what, and when.

Which "what if" questions can you try?

• Change vehicle or capacity: "What if this line ran a 27+1 vehicle instead of a 19+1?"
• Shift the time: "If we move departure from 08:30 to 09:00, how many people end up out of sync with their shift?"
• Remove a stop: Passengers move to the nearest stop on the same line; anyone who exceeds the walking distance limit is reported.
• Merge lines: One line's passengers are transferred to existing stops on another line.
• Optimize stop order and move passengers.
• Rebalance capacity: Evens out occupancy across lines while moving the fewest people.
• Line redesign: The routes of the selected lines are recalculated from scratch with vehicle routing.

Before/after report

Each scenario is evaluated in memory on a snapshot of live data; nothing is written to live tables. The results screen shows:

• Balance score, number of daily trips, kilometers and duration
• Average ride and walking time, number of assigned passengers
• Number of trips over capacity, people out of sync with their shift and people exceeding the walking limit
• Estimated monthly cost difference (if a vendor contract is defined)
• Affected people (limited to the user's data scope) and a map with a "SIMULATION" badge

Applying and rolling back

Each item in a change set is re-validated just before publication. Publication runs as a single transaction: capacity is checked as a whole after all items have been applied, and if anything fails the entire publication is rolled back. If live data has changed since the scenario was evaluated, the conversion is rejected, so no decision is ever applied based on a stale calculation.

A published set can be rolled back when needed: the inverse of each item is stored before publication, and "Roll back" creates a new draft set. That set also goes through the approval flow.

Frequently asked questions

Does trying a scenario affect live shuttles?

No. Scenarios are calculated in memory on a snapshot of live data; trips, assignments and lines do not change until the scenario is applied.

Can the four-eyes principle be turned off?

By default, the person who prepared a change cannot approve it, and this rule is enforced at the database level. For very small teams this restriction can be relaxed via an organization setting; in every case all steps are written to the audit log.

Can an applied change be rolled back?

Yes. A new draft set containing the inverse operations is created from the published change set and applied after approval. A line version publication cannot be rolled back directly; in that case, copying the previous version is recommended.

Where does the cost in a scenario result come from?

It is calculated from the pricing rules in the lines' vendor contracts (per km, per trip, per line or per seat). If no contract is defined, cost is shown as "no data".