The initial data representing the MT (iSMT) will be shared through the ASM process in the medium/short term planning phase, in the form of flight intentions focused on ARES demand. These flight intentions will be progressively refined and enriched with mature information regarding military operational and technical requirements, following a layered collaborative planning process. As the planning process moves closer to the execution phase, the requested ARES will be allocated through the ASM process. The improved OAT flight plan (iOAT FPL) will be filed incorporating data related to the allocated ARES and will be based on latest MET and AIM data plus ATM constraints, if any. iOAT FPL will be shared with NM and will contain trajectory 3D profile and mission specific data (e.g. a unique ARES identifier, STAY information, formation flight details, RPAS elements). Any subsequent changes until transformation in iRMT will follow the flight plan management processes.
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
|
|
|
|
AUO-0215 | |
ER APP ATC 82 |
V4
V5
IOC - FOC
|
ER APP ATC 82b |
V4
V5
IOC - FOC
|
ER APP ATC 143 |
V4
V5
IOC - FOC
|
MIL-0501 | |
MIL-0502 |
V4
V5
IOC - FOC
|
MIL-STD-03 | |
NIMS-35 |
V4
V5
IOC - FOC
|
NIMS-45 |
V4
V5
IOC - FOC
|
PRO-014 |
V5
IOC - FOC
|
Code | Title | Program | Related Elements | Analysis |
---|---|---|---|---|
PJ.07-03 | Mission Trajectory Driven Processes | SESAR 2020 Wave 1 | Analysis |