Library · Travel & housing – process groups
PLN · Demand planning from scheduling
The schedule turns into requirements: who needs to be where and when. Almost all rule-based.
10 processes
Overview
Who it's for
Teams that organize travel and housing for many people
You need
Master data of travelers and a schedule
You get
10 documented workflows with trigger, automation level, and priority
| ID | Process | Trigger | Autom. | Prio |
|---|---|---|---|---|
PLN-010 | Import and normalize daily schedule | new schedule/daily schedule version published | VOLL | Do first |
PLN-020 | Derive person-time-location matrix ("who when where") | Daily schedule import validated | VOLL | Do first |
PLN-030 | Detect travel requirement | Matrix updated; distance/travel time > `{{MIN_DISTANZ_KM}}` / `{{MIN_FAHRZEIT_MIN}}` | VOLL | Do first |
PLN-040 | Detect overnight stay requirement | Travel requirement plus call/wrap outside `{{FRÜHESTE_CALL_ZEIT}}` / `{{SPÄTESTE_WRAP_ZEIT}}` | VOLL | Do first |
PLN-050 | Determine lead, follow-up, and travel days | Overnight stay requirement detected for person and work block | VOLL | Do first |
PLN-060 | Turnaround and rest period check including travel times | Requirement plan draft generated or daily schedule delta | HITL | Do first |
PLN-070 | Consolidate requirement by location and time period | All individual requirements of a work block determined | VOLL | Do first |
PLN-080 | Submit requirement plan for approval | Consolidation completed and cost forecast available | HITL | Do first |
PLN-090 | Calculate scenario and what-if planning | Request PL/HL or detected work site/weather risk | ASSIST | Big Bet |
PLN-100 | Fix and version baseline | Approval granted from PLN-080 | VOLL | Do first |