Upload the datasets that feed the demand model. Keep files in the working
session or persist them to the shared database for reuse across plans.
Upload
pick a document
New Flight Plan
Historical Flight Plan (LF)
DIIO
Pax Share Rules
Corporate prediction
Saved files
library
Schedule
Event Date Mapping
Map an event's date range from last year to the equivalent range this year.
Add as many references as you need, then Save.
How this works
Unique name = a version
(a set of events for a plan/year).
Type the same name on every event that belongs to that version.
Add row:
fill Event, Unique name and both date ranges, then press
Add row
. It saves to the database instantly.
Clear form:
empties the Event and Unique name fields so you can start a new entry.
Delete selected:
click a row in the table, then press
Delete selected
. It is removed from the database immediately.
Filter:
pick a Unique name above to see only that version's events.
Copy a plan:
pick an existing plan in
Copy from
, type a new name in
New unique name
, then press
Duplicate plan
. Every event from the source plan is copied
into the new plan immediately — edit the copies afterward as needed.
Add a reference
to
to
Copy a plan
References
Step 02 · Vectors
Load Factor Vectors
Build the 41 load-factor fallback vectors from the Historical Flight Plan (LF) data,
review or override any value, then save the set as a profile for later use when
assigning load factors to a flight plan.
How dates are mapped to the target year
Full date, not just time-of-day:
STD now keeps its complete date. Any vector that includes “STD” as a
dimension is keyed by that date mapped into the target year, so day-of-week
travel patterns carry over correctly instead of only matching by clock time.
No Reference plan selected:
every historical date maps onto the SAME month/day in the target year, then
shifts by at most 3 days (earlier on a tie) so it lands on the same weekday.
Example: Wed 25-Jun-2025 → Wed 24-Jun-2026, not Thu 25-Jun-2026.
Reference plan selected:
for dates inside one of that plan's event windows (from the Date Mapping tab),
the date maps PROPORTIONALLY into that event's target window instead — e.g. an
F1 race on 1–3-Jun-2025 mapped to 31-May–2-Jun-2026 shifts every one of its
days by −1 day. Dates outside an event window still use the same-weekday rule.
When an event jumps far
(e.g. a National Holiday moving from 5-Jun to 5-Nov), the target-year dates it
would otherwise have landed on (here, around 4–5-Jun) are left EMPTY on
purpose — we never invent numbers for a day with no real historical flights.
Those dates fall back to the vectors that don't use STD, and to the ±2h
“any flight” vectors, which pool by time-of-day only and ignore the
calendar date. Any gap dates are listed in the Mapping summary panel after Build.
Target year:
up to 20 years ahead.
Reference plan:
optional — leave it on “None” to use the
same-weekday rule for every date.
Result
Values are editable — click any Load Factor (%) cell to override the calculated value.
All 41 vectors, in fallback order. Click a row to open it in Selected vector.
Mean LF
Groups
Flights matched
Overrides
Profile
Mapping summary
Step 03 · Transit
DIIO / Pax Share Rules
Coming next.
Step 05 · Apply
Future Flight Schedule
Coming next.
Step 06 · Plan
Corporate Prediction
Coming next.
Upload Flight Plan CSV
Upload started — please wait, do not close this page...
Upload an Excel file or CVS file, enter a version name, then click Validate. Fix any errors before confirming.
⚠️
Press
Generate
after changing any filter to refresh all charts, KPIs, and tables.
📋 Days Exceeding Limits
📊 Combined Peak Analysis
👉
Each bar is one metric across the season —
green
under all limits,
orange
above the orange limit,
red
above the red limit.
Hover for value vs. limit.
Click any segment
to load that day's detail below.