20120418_DCP_DCIT_14_CBurr_AOC_FOC_Production.pptx

AOC/FOC Interface
for Data Comm
Production System
To: Data Comm DCIT AOC WG
From: Data Comm Production Sub-Team
Date: 04/18/12
Federal Aviation
Administration
Agenda
• Production System AOC Interface Overview
– Purpose/Scope
– Today and Tomorrow
•
•
•
•
Departure Clearance Summary
Data Exchange Summary
Questions/Issues
Next Steps
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
2
Purpose/Scope
• Review FAA automation for initial
implementation
• Discuss questions/issues concerning Data
Comm Production System interface with users
– Data Comm Trials is a separate activity, architecture and
time frame
– Augment DCIT discussions
• Scope
– New DCL Courtesy Copies
– Gate/Surface Location
– Subscriber Information Data Exchange
• New Web-based service
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
3
Data Exchange Summary/Subscriber Data :
AOC to TIMS
Data Link Services
Delivery Mechanism
Preferences
Subscription Mechanism for delivery of
departure clearance.
Preliminary values are:
a) None
b) PDC
c) DCL
d) DCL/PDC*
Courtesy Copy
Preferences
Subscription Preliminary values are:
(Web SDB) a) Initial DCL
b) Revised DCL
c) Initial and Revised DCL
d) Initial DCL fields
e) Revised DCL fields
Gate ID Preferences
Subscription Preliminary values are:
(Web SDB) a) PDC/DCL CC response
b) Gate ID Request message
response
DCP SE AOC Sub-team
18 April 2012
Needs discussion.
*DCL/PDC indicates
DCL will be used unless
service is unavailable, in
which case PDC will be
generated if possible.
Note that evolution
expected to involve flight
plan codes.
Assume AOCs want
everything, so this may
end up being deleted as
separate data element
Federal Aviation
Administration
4
Data Exchange Summary/DCL Courtesy Copy:
TIMS to AOC
Departure Clearance
Explicit caveat that this is CC,
Courtesy Copy Header (M) not a clearance
COURTESY COPY – NOT AN ATC
CLEARANCE
Departure Airport (?)
ICAO airport for which this copy Good to have to ensure we are
of clearance applies
dealing with same flight. Does it
need to be mandatory?
Departure Clearance
Information (M)
Copy of contents of DCL sent to Details will be provided in
aircraft, minus the beacon code
appendices of Functional
Description Document and IRD.
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
5
Data Exchange Summary/Gate ID Data : AOC
to TIMS
System
Acknowledgement/
Response (C1*)
Departure
Gate/Surface Location
(C2*)
System response that message Includes both acks and nacks in response
was received
to DCL copy sent from TDLS to User
Automation. Not required unless this is
the mechanism chosen for how to provide
Gate ID.
Note that system ack is required for legacy
PDC.
Location from which aircraft Clarify that this can be locations other
is requesting departure
than gate/stand, e.g., hangar or other
clearance. Used by FAA for
surface locations for GA or corporate
tower operations.
flights. NOTE: Current legacy PDC combines
gate ID and system ack to the PDC. Expect this
to be retained and use the same paradigm for
DCL copies, but may be refined to address
revisions. Also, could be sent as totally separate
response to Gate ID Request message (TBD).
*C1 – Conditional, based on Gate ID data
exchange mechanism
*C2 – Conditional. If currently providing,
then mandatory but mechanism is flexible
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
6
Questions/Issues
1.
DCL Courtesy Copy (CC)
•
Format (ARINC 620 flavor) being refined. Approach is to make CC as
similar to existing PDC format on assumption this is less impact on AOC
automation?
–
–
•
•
•
•
Confirm that AOCs want something that looks like a PDC rather than starting
fresh.
Confirm that AOC want data fields in PDC format, even if not sent in DCL, e.g.
CID, frequency.
Confirm no route sent to AOC when aircraft gets CAF for initial DCL,
since no route sent to aircrew.)
Current approach is to send CC for all revisions and include all changed
fields (e.g., what was sent to aircraft)
Timing of when to send CC (Tower controller need for gate ID when
approved DCL vs AOC desire only when pilot picks up, revisions prior to
initial DCL delivery)
System ack optional (desired, but not required unless this is the choice of
how to provide Gate ID to FAA)
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
7
Questions/Issues – cont’d
2.
Separate Gate ID/Surface Location Message
•
•
•
•
Evolution is to decouple Gate ID from PDC and DCL Courtesy Copy
and provide separate “message” to exchange Gate ID/Surface
Location to support taxi clearance generation
Is there any AOC desire or support for this in near-term?
Clarify Optional/Mandatory (If user is currently providing, then need to
keep providing. Desirable if AOC can make available even if not
currently providing. Operational benefit is to expedite taxi clearance
by identifying surface location.)
Mechanism
• As response to DCL Courtesy Copy (Similar to current PDC response,
versus other options)
• Request Message (Option for a separate message, e.g., start clean?)
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
8
Questions/Issues – cont’d
3.
User Preferences
a.
Subscriber Data Base (Default list via CSP, dynamic updates,
Web-based option)
b.
ICAO FPL option (Equipment capability versus preferences, PDC vs
FANS DCL)
c.
Fallback option (Do users want to revert to PDC if marked as DCL
but service is not available?)
• In addition, we still need to figure out how to get feedback
from other airlines who are not participating in DCIT.
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
9
Data Exchange Summary
Subsystem A
Messages
Direction
Subsystem B
User Automation
Subscription Create,
Delete, Update
A  B
TDLS/TIMS
User Automation
Subscription Response
A  B
TDLS/TIMS
User Automation
Subscriber List (Legacy)
A  B
N/A - FAA TDLS Program
User Automation
Legacy PDC
A  B
TDLS/TIMS
User Automation
DCL Courtesy Copy
A  B
TDLS/TIMS
User Automation
PDC or DCL CC ack
(system)
A  B
TDLS/TIMS
A  B
TDLS/TIMS
A  B
TDLS/TIMS
User Automation
User Automation
DCP SE AOC Sub-team
18 April 2012
Gate ID Request
Gate ID
Federal Aviation
Administration
10
Next Steps
• FAA Production System approach has been briefed
at DLUF and DCIT, moving forward with defined
capabilities
– DCIT AOC WG is designated forum for identifying any user
issues
• Need users to identify automation POCs to work
the details, e.g., specific mechanisms and
protocols
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
11
Questions?
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
12
Back Up
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
13
Summary: AOC Interface Today and late 2012
• What/When
– Subscriber list data - manual (email/phone) e.g., which users want PDC at
which airports. Airline coordinates with FAA separately with updates as
needed (aggregate not flight-specific); non-airline users provide lists bimonthly. Legacy PDC (pre-departure route clearance) from TDLS to AOC
Host approx. 30 min before P-Time (filed flight plan “pushback” time)
– AOC sends Gate ID (from relevant users as result of coordination with
FAA) along with sys ack from AOC or CSP
• How
– Via CSP (ARINC, SITA) from TDLS in Tower; Transparent to AOC that
they are getting from TDLS since they only see CSP
– Soon (2012, pre-Data Comm) – also available from FAA automation
(TDLS and TIMS) to any users, via open TCP/IP
• Who
– No direct interface between FAA and dispatchers or ramp towers
– Practice is for no revisions by dispatchers - usually re-file flight plan
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
14
Current FAA-AOC and Aircraft Interfaces
Gate Terminal
ACARS
Ground
Station
Terminal
Printer
Airline/User
Network
AOC/CSP
NADIN
(X.25)
AMSRP
TDLS
AMSRP - ATIS Message
Storage and Retrieval Processor
AFEPS - ACARS Front-End
Processing System
AFEPS
APN
(GATEWAY)
DCP SE AOC Sub-team
18 April 2012
ADNS
Federal Aviation
Administration
15
FAA-AOC and Aircraft Interfaces 2012 – TDLS
version 10.09 – Equal Access
Data
ACARS
Ground
Station
Gate Terminal /
Printer
CSP
Private
Network
NESG
WEST
ADNS
NESG
EAST
FTI
AOC
TDLS
Processors
A&B
DCP SE AOC Sub-team
18 April 2012
TIMS
WEST
TIMS
EAST
Service
Provider
(1 or more)
Airline / User
Computer
Federal Aviation
Administration
16
AOC Interface with Data Comm (2015/2016)
• What/When
– Legacy Subscriber List migrated to new Web-based
Subscriber Data Base
– Legacy PDC from TDLS to AOC retained
– CPDLC DCL Courtesy Copies of clearances, including
revisions, sent directly to CSP/AOC by FAA automation
• How
– PDC and DCL Courtesy Copy Via CSP (ARINC, SITA) or
other CSPs or any users via open TCP/IP from TIMS
Server in SLC or ATL
– New Data Comm Web-based Subscriber Data Base at
TIMS ADM Server (subscriber information only)
•
Who
– Same as today
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
17
Data Comm TDLS/TIMS-AOC and
Aircraft Interfaces
1. Existing CSP Path from
FAA to AOC and
aircraft via ACARS
1
2
2. New CPDLC Path from
FAA to aircraft via new
DCNS
1
2
1
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
18
Web-Based TIMS SDB High Level Architecture
CSP Web
Interface
NESG
CSP
FTI
External DMZ
Web Server
TIMS
West
SDB
Operational
Database
SDB Master
Database
Oracle
Oracle Streams
Oracle
Streams
Oracle
TIMS
East
TIMS ADM
SDB
Operational
Database
Oracle
TTCS
TTCS
Alternating Messages (Load Balancing)
TDLS
TTCS
• CSP/AOC to FAA
Subscriber Web Interface
• Connect via TCP/IP and
FAA’s FTI network
• TIMS operational
servers/DBs at SLC and
ATL
• TIMS admin server at
OKC (FAA TDLS Team)
• Subscriber Preference Data
• Whether specific flight is getting PDC or DCL at this departure airport
• Other TBD AOC preferences, such as which fields in DCL Courtesy
Copy
• Initial design is one-way only from user to FAA
SDB App
Named
Pipes
ERAM &
PC-RCU
MySQL
FDCS
DCP SE AOC Sub-team
18 April 2012
DCL
Federal Aviation
Administration
19
Departure Clearance (DCL) –
(Key Differences from PDC in red): 1/3
1. Subscriber Information for PDC and DCL (flight specific)
– User provides preferences using Web based TIMS Subscriber service
– Specifies AIDs (and/or tail number/REG) which are getting DCLs and which are
getting PDC, at the specific airport
• None - voice
• PDC only
• DCL only
• DCL primary, PDC secondary. – If DCL service is unavailable, FAA
automation may “fall back” to PDC. If user wants a previous DCL flight to
get a PDC and it is still possible (prior to P-Time – approx. 30 min), then
user needs to define preference accordingly
– DCL Courtesy Copy preferences, if applicable (TBD)
• What fields in CC (Current approach is to mimic PDC format), without
beacon code
• All revisions or only trajectory-changing?
– FAA needs 60 min prior to P-time, e.g., prior to when flight strip prints and
controller has acted on departure clearance, to ensure it is applied
• Later updates may not be acted on if system or controller has already
processed the flight
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
20
Departure Clearance –(Key Differences from PDC): 2/3
2.
PDC/DCL CC
– When controller approves the clearance and per subscriber information , FAA
automation sends following via existing CSP interface
•
PDC, as done today
•
DCL Courtesy Copy (CC) and/or Gate ID Request
3.
FOC automation responds (within 2 min) via CSP
a)
b)
System/application ack to above (mandatory)
•
PDC
–
Y - flight is eligible to receive a PDC that day
–
N – not eligible to receive a PDC
•
Initial DCL Courtesy Copy
–
Same (Y,N) responses are OK
–
FAA does not NEED anything but will accept
Gate ID –response to PDC, DCL CC or Gate ID Request Message
• optional but is required at certain airports, per coordination with FAA
• May be appended to system ack to PDC or DCL CC, or as explicit response
to a Gate ID Request message
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
21
Departure Clearance–(Key Differences from PDC): 3/3
4.
TDLS stores Gate ID from FOC.
–
5.
At some point, Pilot requests DCL via DCL Request downlink.
–
–
6.
Enables timely response to taxi clearance request.
TDLS sends stored DCL to aircraft
Pilot responds and response returned to TDLS
Revised clearance
a)
b)
PDC – Voice clearance
DCL – Revised DCL
• Revised clearance (DCL) sent to pilot
• Revised Courtesy Copy sent to AOC
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
22
Documents
• Existing FAA-CSP ICD
– Predeparture Clearance Application Segment Specification, ARINC, 12889
Rev H, Sept 1999
• FAA Draft Functional Interface Description Document,
TDLS/TIMS-AOC Automation, V0.2, April 2012 [in progress]
• FAA Draft IRD for Subscriber Data Base
– Communications Service Provider (CSP) To Tower Data Link Services
Subscriber Database (TDLS-SDB) IRD, May 2011, DRAFT V1.0
– Available on DCIT Website,
http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/tec
hops/atc_comms_services/dcit/dcit_current_documents/media/CSP_to_TDLSSDB_IRD_draft_v1.0.pdf
DCP SE AOC Sub-team
18 April 2012
Federal Aviation
Administration
23
Similar pages