Embedded Elements
Element Detail Notes
Port 2.1.2.0.1 [S2] MCI-E.FDP_Port
1.0
Port 2.1.2.0.3 [S2] MCI-E.GMD_Port
1.0
Port 2.1.2.0.2 [S2] MCI-E.SDP_Port
1.0
2.1.1 Flight Data Processing (FDP)
Type: Object
Status: Proposed. Version 1.0. Phase 1.0.
Package: 2.0 Ground Data Processing (GDP) Keywords:
Detail: Created on 5/10/2006. Last modified on.2/3/2007.
GUID: {213E0931-2013-482d-8664-7EF9612CA9E0}
This function accepts flight plans and flight plan amendments from controllers, airspace users, U.S. ATC Facilities, Non-U.S. ATC Facilities and other systems in the ARTCC. The FDP function generates a converted route and trajectory for each plan. For active flights, the FDP function determines whether the aircraft is in conformance with the trajectory by comparing track data received from the SDP function against the trajectory. If the aircraft is out of conformance, the controller is notified, and an adherence trajectory is created to best predict how the aircraft will return to conformance of its flight plan. The FDP function distributes flight data to GUI function interfacing facilities, provides automatic and manual handoff functions, and supports airspace sectorization.
[from ERAM SADD, Section 4.2]
The FDP provides equivalent flight data processing capability as provided in Host Computer System (HCS). These capabilities include: flight plan processing, track to flight plan pairing, and transfer of control. Improvements to capabilities such as beacon code assignment, the use of beacon code matching and comparison of current track position to predicted trajectory position for track to flight plan pairing, direct route conversion, four-dimensional trajectory modeling (altitude, latitude, longitude, and time), and the use of trajectory data to project boundary crossings for automatic handoff initiation are provided in FDP. Additional FDP capabilities that are introduced include full ICAO message integration, Area of Interest (AOI) flight plans, and flight strip posting based on flight plan trajectory passing through adaptable posting airspace.
[from ERAM SADD, Section 4.2.2]
[S1][A1]: The FDP will host the CPDC function.
[S1][A2][A3]: The FDP will be enhanced to support an interface with CPDC function.
[S2][AA]: The FDP will accept aircraft reroute information from TFM as a result of TMIs. The new route will be proposed to the current eligible controller for uplink to aircraft.
[S3]: The FDP will be augmented to account for better accuracy over a longer time horizon (e.g. minimum 2 hour high accuracy). The use of trajectory agreements will reduce controller/system perturbation of flight paths. Use of aircraft provided FMS Trajectory information will increase accuracy of ground based trajectory modelling.
Connections
Connector Source Target Notes
Realisation
Source -> Destination
ConnSource.Scope= Public
ConnSource.Role
ConnSource.RoleNote
Element.Name=
2.1.1 Flight Data Processing (FDP)
Element.Type=
Object
ConnTarget.Scope= Public
ConnTarget.Role=
ConnTarget.RoleNote=
Element.Name=
PPR.3.1.2.3 [S2] 4D Trajectory Exchange
Element.Type=
Requirement
Realisation
Source -> Destination
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：Functional Architecture for the Data Communication System(40)
