AOM-0304-B — Integrated management of Mission Trajectory in trajectory based operations environment
In Trajectory based operations (TBO) environment Mission Trajectory will be integrated into ATM network operations through all phases of trajectory lifecycle (SMT/RMT). The MT profile will be described by a 4D dataset and shared with ATM network. In addition to the 4D dataset MT may contain 4D targets ATM constraints and associated tolerances and will be subject to trajectory management processes.
MT profile will be distinct from BT in order to address specific mission requirements e.g. ARES integrated into MT description, trajectory synchronization, formation join up and split up. Providing that ARES is integrated into MT profile it will be described by the 4D dataset, and then shared with ATM network. This data can be extracted from MT description by NM system and used as an input into DCB process. In order to secure the confidentiality aspects of the mission objectives, the 4D dataset describing the trajectory profile within ARES will not be shared.
- Rationale
- Although the layered planning phases described for the Business Trajectory and Mission Trajectory can be similarly distinct, Mission Trajectory will require more emphasis on short notice to comply with operational needs. Additionally, ARES planning is an integral part of Mission Trajectory planning.
Those parts of Mission Trajectories executed within airspace reservation/restriction (ARES) (training, combat etc.) will not be shared - but any other 4D information (position, time, altitude) have to be planned, agreed and achieved. In this case the ARES requests may form an integral part of the Shared and Reference Mission Trajectory (SMT/RMT), with the airspace volume dynamically tailored for the military operation and coordinated with respect to civil traffic flows where possible, and in accordance with agreed policy and protocols.
ARES will be managed in an integrated way with trajectories and will be added to the Mission Trajectory description (SMT - RMT). Publication of SMT will trigger the ARES allocation process (ASM) through CDM.
The final outcome is the RMT, ARES allocation included.
Quick response Alert missions (priority flights and distress assistance flights) are, by their nature, not likely to be able to define a specific trajectory or airspace volume, and will need to be coordinated individually. - Forecast V3 end date
- —
- Benefits start date (IOC)
- 01-07-2029
- Full benefits date (FOC)
- 31-12-2033
- Current Maturity Level
- —
- Solution Data Quality Index
- —
- Current Maturity Phase
- R&D
- Scope
- —
- Release
- —
- PCP Status
- —
Enablers
| Code | Dates |
|---|---|
|
2015
15
2016
16
2017
17
2018
18
2019
19
2020
20
2021
21
2022
22
2023
23
2024
24
2025
25
2026
26
2027
27
2028
28
2029
29
2030
30
2031
31
2032
32
2033
33
2034
34
2035
35
2036
36
2037
37
2038
38
2039
39
2040
40
|
|
|
|
|
| AOM-0304-B | |
| A/C-61 |
V4
V5
IOC - FOC
|
| A/C-61b |
V4
V5
IOC - FOC
|
| A/C-61c |
V4
V5
IOC - FOC
|
| AAMS-16a |
V4
V5
IOC - FOC
|
| AAMS-16b |
V4
V5
IOC - FOC
|
| AAMS-17 |
V4
V5
IOC - FOC
|
| AAMS-18 | |
| CTE-C06d |
V4
V5
IOC - FOC
|
| CTE-N01 |
V4
V5
IOC - FOC
|
| CTE-N06 |
V4
V5
IOC - FOC
|
| CTE-N06a |
IOC - FOC
|
| ER APP ATC 10 |
V4
V5
IOC - FOC
|
| CTE-N02 |
IOC - FOC
|
| CTE-N03 |
IOC - FOC
|
| CTE-N04 |
IOC - FOC
|
| CTE-N06b |
IOC - FOC
|
Dependent OI Steps
| Relationship | Code | Title | Related Elements |
|---|---|---|---|
|
10
Has predecessor
|
AOM-0303 | Pan-European OAT Transit Service |    |
|
10
Has predecessor
|
AOM-0304-A | Improved and Harmonised OAT Flight Plan | |
|
10
Has successor
|
AOM-0304-C | Integrated Management of Mission Trajectories in Step 3 | |
ICAO Block Modules: