[SA][AA]:  The ACC/Flight Object needs to be enhanced to handle Tower/TRACON controller communications eligibility and handoffs (assuming Tower/TRACON facilities do not have their own FDP).

Embedded Elements
Element Detail Notes
Port 2.1.1.3.0.1 ACC.IFP_Port

1.0

Port 2.1.1.3.0.2 ACC.FLS_Port

1.0

2.1.1.2 Flight Services (FLS)
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.11/29/2006.
GUID:  {D0323AE5-50A6-4f45-9C42-B3DFEB90B0B0}

The FLS function creates, updates, deletes, and distributes Flight Objects. Flight Objects consist of a flight plan, converted route, trajectory, and status information about a flight. Status information includes control eligibility and conformance/adherence status. Requests to FLS are previously syntactically checked; semantic validation is performed by FLS in the process of creating and updating the Flight Object by invoking FPS for the flight plan and RTC for the route.
[from ERAM SADD, Section 4.2.2]

[S1][AA]:  The FLS flight object will need to be updated to include the following information:
- a field indicating that the aircraft is data link capable (may also need to include information about type, version of datalink information - from flight plan??).
- data authority information,
- communications eligibility (note this is different from control eligibility).

[S2][AA]: Additions to the FLS flight object may include:
- FMS Trajectory information

Note: FMS Trajectory information may need to be a new trajectory stored in flight object.  The FMS trajectory might be DIFFERENT from both the Flight Plan Trajectory (ERAM) and the Aircraft Trajectory (ERAM).  The Aircraft Trajectory contains stuff like letters of agreement data that might alter the trajectory that the aircraft is unaware of. 

Note:  The filed flight plan may need to be more detailed to indicate data link type (e.g. ATN, FANS).

Connections
Connector Source Target Notes
Realisation  
Source -> Destination
ConnSource.Scope= Public
ConnSource.Role
ConnSource.RoleNote
Element.Name=
2.1.1.2 Flight Services (FLS)
Element.Type=
Object
  ConnTarget.Scope= Public
ConnTarget.Role=
 
ConnTarget.RoleNote=
Element.Name=
PPR.3.1.2.8 [S2] Conformance Management
Element.Type=
Requirement
  
 

Embedded Elements
Element Detail Notes
Port 2.1.1.2.0.2 FLS.CPT_Port

1.0

Port 2.1.1.2.0.3 FLS.ACC_Port

1.0

Port 2.1.1.2.0.1 FLS.IFP_Port

1.0

Port 2.1.1.2.0.5 [A1] FLS.CPDC_Port

1.0

Port 2.1.1.2.0.4 FLS.TJS_Port

1.0

2.1.1.4 Trajectory Services (TJS)
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.11/29/2006.
GUID:  {FED77204-BDD2-4e9c-8A61-7825BFE2A81C}

The TJS function provides clients with the capability to model trajectories. Services are also provided for deriving the predicted location and time that an aircraft will cross an adapted airspace boundary (e.g. sector, facility) based on the trajectory. Trajectory modeling is
　
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：Functional Architecture for the Data Communication System(43)