IS-0305 — Automatic RBT Update through TMR
The event-based Trajectory Management Requirements (TMR) logic is specified by the ground systems on the basis of required time interval and delta of current Predicted Trajectory (PT) versus previously downlinked PT. TMR parameters can be static/globally defined or dynamic/flight-specific. This process is transparent to ATCOs and pilots (deviation alerts that are relevant for the ATCO should be associated with larger tolerance than ground-managed TMR).
- Rationale
- The objective is to improve ground trajectory prediction by use of airborne data while optimising the communication bandwidth. The improvement may be in several steps starting with fixed/pre-defined periodic downlink (possibly varying according to airspace and/or phase of flight), then event-based ground-managed TMR, then static airborne-managed TMR parameters (the detection of deviation being performed by airborne systems), then dynamic airborne-managed TMR parameters (defined on the ground and uplinked as appropriate).
- Forecast V3 end date
- -
- Benefits start date (IOC)
- 31-12-2015
- Full benefits date (FOC)
- 31-12-2019
- Current Maturity Level
- -
- Solution Data Quality Index
- -
- Current Maturity Phase
- R&D
- Scope
- -
- Release
- 2020+
- PCP Status
- -
Enablers
| Code | Title | Related Elements | Analysis | |
|---|---|---|---|---|
|
10
|
AGSWIM-38 | SWIM enabled services for AGDLGMS |   |
Analysis |
SESAR Solutions: 
PCP Elements: 
Implementation Objectives: 
ICAO Block Modules: