Coarsening Per-Flight Commitments to TMI Vocabulary

Re-express a set of per-flight delay, spacing, and reroute commitments produced by the routing engine as standard Traffic Management Initiatives (GDP, AFP, MIT, CTOP), and compute the primary TMI parameter (program rate or miles-in-trail) from the underlying commitment data.

Step 1 of 157%

Tutorial

Coarsening: From Per-Flight Commitments to TMI Vocabulary

When the live routing engine assigns delays, reroutes, and spacings, it produces a fine-grained list of per-flight commitments. To publish those decisions to the NAS, we re-express them in the coarse vocabulary of Traffic Management Initiatives (TMIs): GDP, AFP, MIT, and CTOP.

This re-expression is called coarsening -- bundling a set of per-flight commitments into a TMI-shaped object that has the same operational effect on the flow.

Each per-flight commitment is classified by where the constraint binds:

Per-flight commitmentTMIGround hold at origin, scoped to a destination airportGDPGround hold at origin, scoped to a flow-constrained areaAFPCrossing-time spacing at a fixMITReroute with a published set of trajectory optionsCTOP\begin{array}{ll}\textbf{Per-flight commitment} & \textbf{TMI} \\ \hline \text{Ground hold at origin, scoped to a destination airport} & \textbf{GDP} \\ \text{Ground hold at origin, scoped to a flow-constrained area} & \textbf{AFP} \\ \text{Crossing-time spacing at a fix} & \textbf{MIT} \\ \text{Reroute with a published set of trajectory options} & \textbf{CTOP} \end{array}

A GDP and an AFP are coarsened the same way -- by a rate (slots per hour). The rate applies to an airport for a GDP and to a flow-constrained area (FCA) for an AFP. An MIT is coarsened by a distance in nautical miles. A CTOP is coarsened by an enumerated list of trajectory options.

↑ ↓ navigate · Enter open · Esc close · ⌘K/Ctrl K toggle