1. Operational Context and Use Case Focus Group
April 25, 2019

2. Agenda Schedule Updates to STDDS Documentation
SWIM Terminal Data Distribution – Tower Departure Event Service (STDDS-TDES)
Closeout
STDDS Airport Data Service (APDS)
Operational Context
Data Communications Network Service (DCNS) – Data Link Dispatch (DLD)
Preview

3. Ops Context Document Schedule
February 2019
FNS OCD Closeout
ITWS OCD Flow UCD
TDES OCD Storyboard MET UCD Storyboard
March 2019
ITWS OCD Closeout Flow UCD Closeout
TDES OCD MET UCD
APDS OCD Storyboard
April 2019
TDES OCD Closeout MET UCD Closeout
APDS OCD
DLD OCD Storyboard Aero UCD Storyboard
May 2019
APDS OCD Closeout
DLD OCD Aero UCD
TFMS Status OCD Storyboard
June 2019
DLD OCD Closeout Aero UCD Closeout
TFMS Status OCD
SFDPS General OCD Storyboard
July 2019
TFMS Status OCD Closeout
SFDPS General OCD
ISMC OCD
August 2019
SFDPS General OCD Closeout
September 2019
ISMC OCD Closeout
*OCD – Ops Context Document
UCD – Use Case Document
STDDS Ops Context Documents
STDDS program reviewed Ops Context docs for TAIS, SMES, APDS and TDES
SWIFT will provide ISMC doc to STDDS for review once drafted
Added DLD to April 2019, all other Ops Context Docs move 1 month to the right
Will address Request/Reply services once all Pub/Sub services are completed

4. Updates to STDDS Documentation
Received feedback from STDDS program on TAIS, APDS, TDES, and SMES
Revisions ensured all information was factually correct and updated to latest STDDS versions
Updated previous Ops Context Documents for SMES and TAIS
STDDS TAIS - Operational Context Document v1.2_2019_04_25_RevA
STDDS SMES Operational Context Document v1.1_2019_04_25_RevA
Included edits to APDS and TDES Ops Context Documents we are presenting today

5. Closeout
SWIM Terminal Data Distribution System - Tower Departure Event Service (STDDS-TDES)

6. STDDS-TDES Description
All Consumer Capabilities
Publishes Digital Automatic Terminal Information System (D-ATIS) information sent automatically to aircraft and operators at airports associated with STDDS TRACONs
Internal FAA Only Capabilities
Sends departure events for all flights from select towers associated with a TRACON
The service provides a reconstitution mechanism for end-users interested in receiving historic departure events upon startup

7. Comments
reconstitution requests but I did not see any information on if those requests by airlines are even possible or if you the request would have to be generated internally by the FAA/NAS. If external requests by airlines are possible ( I don’t think they are) we may want to include how to structure a request message or make that request.  The unclear part to me was “Note: This message is available only for internal NAS consumers.”(page 13/14) Are airlines considered internal NAS consumers? Or is this the same the as “All tower departure event reconstitution messages are considered sensitive and are not shared outside of the FAA.” (page 11) The prior sounds like airlines may be considered as NAS customers where the second sounds like they are not. I guess I’m asking for clarification on what is an internal NAS customer and if that group is the same group that has the ability to submit requests or is this 2 different populations.

8. Sourcing STDDS-TDES

9. STDDS-TDES Operational Context Document
Introduction
Terminal Information
Digital Automatic Terminal Information System
Tower Departure Events and Clearance Delivery
References
STDDS-TDES Service Overview
STDDS-TDES Publication Message Types
DATISData
TowerDepartureEventMessage
TowerDepartureEventReconstitutionStartMessage
TowerDepartureEventReconstitutionCompleteMessage
ReconstitutionRequestStatusMessage
Appendix A: Acronyms

10. STDDS-TDES Internal FAA Only Service Description Service Interface
STDDS TDES publishes departure events derived from Tower Data Link System (TDLS) and Electronic Flight Strip Transfer System (EFSTS) for all flights from towers associated with a STDDS Terminal Radar Approach Control (TRACON). In addition, the service provides a reconstitution mechanism for end-users interested in receiving historic departure events upon startup. TDES also publishes D-ATIS data received from TDLS.
Service Interface
Publish/Subscribe via JMS
Message Sets
Message Name
Description
TowerDepartureEventMessage
Sent upon the receipt of a corresponding event from EFSTS and/or TDLS. The MsgType indicates if this event is new (DE) or reconstituted (DR). Both types of messages may be enhanced with SFDPS flight plan data.
Note: The DR messages are available only for internal NAS consumers.
TowerDepartureEventReconstitutionStartMessage
Indicates the beginning of a set of reconstituted messages
Note: This message is available only for internal NAS consumers.
TowerDepartureEventReconstitutionCompleteMessage
Indicates the end of a set of reconstituted messages
ReconstitutionRequestStatusMessage
Response to a reconstitution request. The MsgType indicates if the reconstitution request has been accepted (RA) or rejected (RF).
DATISData
Sent upon the receipt of D-ATIS data from TDLS and repeated periodically per D-ATIS message data type (nominally every 60 seconds).
Note: The D-ATIS message data type is contained in the first character of the dataHeader field. Possible values: ‘C’ for Combined, ‘D’ for Departure, ‘A’ for Arrival.
Internal FAA Only

11. Operational Context
SWIM Terminal Data Distribution System – Airport Data Service (STDDS-apdS)

12. STDDS-APDS Description
Service only has one function/capability
Sends runway visual range observations for select towers associated with a TRACON
RVR describes the distance from the runway that a pilot can expect to see runway surface markings
Different pilot/equipage categories require minimum values of RVR for legal airport approaches in various weather conditions

13. Sourcing STDDS-APDS

14. STDDS-APDS Operational Context Document
Introduction
Terminal Information
Runway Visual Range
References
STDDS-APDS
Service Overview
RVRUpdateMessage
STDDS-APDS Publication Message Types
RVRDataUpdateMessage
airport
runwayData
Appendix A: Acronyms

15. STDDS-APDS Service Description Service Interface Message Sets
The Airport Data Service sends runway visual range observations for select towers associated with a TRACON..
Service Interface
Publish/Subscribe via JMS
Message Sets
Message Name
Description
RVRDataUpdateMessage
Sent periodically (nominally every 60 seconds) and upon change of any published fields received from RVR.

16. Data Communications Network Service (DCNS) – Data Link Dispatch (DLD)
Preview
Data Communications Network Service (DCNS) – Data Link Dispatch (DLD)

17. Controller-Pilot Communications
In addition to using voice, pilots and ATC exchange command and control messages digitally using Controller-Pilot Data Link Communications (CPDLC)
Clearances, requests, position reports, etc.
Historically these messages are not shared with airline dispatchers
CPDLC between ground-based air traffic controllers and airborne flight crews flow through the Future Air Navigation System (FANS) Gateway sub-component of the DCNS.

18. DCNS-DLD Description
Receives copies all CPDLC messages that flow through the FANS Gateway in DCNS, converts them to XML format and publishes them to SWIM for use by airline dispatch (Flight Operations Center)
DLD messages benefit airline dispatch functions:
Improved ability to maintain operational control of flight
Improved situational awareness for Dispatch Function
Real-time receipt of messages
Allows for direct access into Dispatcher Flight Tracker Software
Enables analytics that support operational improvements

19. Sourcing DCNS-DLD

20. Decomposition of DCNS-DLD Messages
ATS Facility Notification
AFN Contact (FN_CON)
AFN Acknowledgement (FN_AK)
AFN Complete (FN_COMP)
AFN Contact ADVISORY (FN_CAD)
AFN Response (FN_RESP)
CPDLC Connection Management
CPDLC Connection REQUEST (CR1)
CPDLC Connection CONFIRM (CC1)
CPDLC Disconnect REQUEST (DR1)
CPDLC
CPDLC Uplink Message (CPDLC_UL)
CPDLC Downlink Message (CPDLC_DL)
Technical Notifications
Message Assurance (MAS)
September 7, 2018

21. DCNS-DLD Operational Context Document
Introduction
Controller-Pilot Communications
CPDLC Messaging
References
DCNS-DLD Service Overview
DCNS-DLD Message Types
AFN Contact (FN_CON)
AFN Acknowledgement (FN_AK)
AFN Complete (FN_COMP)
AFN Contact ADVISORY (FN_CAD)
AFN Response (FN_RESP)
Message Assurance (MAS)
Appendix A: Acronyms
CPDLC Connection REQUEST (CR1)
CPDLC Connection CONFIRM (CC1)
CPDLC Disconnect REQUEST (DR1)
CPDLC Uplink Message (CPDLC_UL)
CPDLC Downlink Message (CPDLC_DL)

22. DCNS-DLD Service Description Service Interface Message Sets
The service provides a copy of the data link messages that are exchanged between the aircraft and the NAS automation system (e.g. a copy of en route dispatch messages, formerly EDM, to AOC). The Data Link Dispatch Service sends XML formatted Air Traffic Services (ATS) Facility Notification (AFN), Controller-Pilot Data Link Communications (CPDLC), and Technical (TECH) Notifications messages to authorized service consumers.
Service Interface
Publish/Subscribe via JMS
Message Sets
Message Name
Description
AFN Contact (FN_CON)
AFN logon message sent by the aircraft to the specified ATSU.
AFN Acknowledgement (FN_AK)
Uplink response sent by the ATSU receiving the AFN logon message to the aircraft providing the status of the AFN logon attempt.
AFN Complete (FN_COMP)
Response sent by the aircraft to the ATSU initiating the FN_CAD providing the status of the AFN logon to the specified ATSU.
AFN Contact ADVISORY (FN_CAD)
Uplink message sent by an ATSU instructing an aircraft to send an FN_CON (AFN logon) to a specified ATSU.
AFN Response (FN_RESP)
Downlink response sent by the aircraft to the ATSU that initiated the FN_CAD indicating an intent to send an FN_CON to the specified ATSU.
Message Assurance (MAS)
Uplink message to request a CPDLC connection.
CPDLC Connection REQUEST (CR1)
Downlink message to confirm a CPDLC request.
CPDLC Connection CONFIRM (CC1)
Downlink message to request a CPDLC disconnect.
CPDLC Disconnect REQUEST (DR1)
Uplink FANS message
CPDLC Uplink Message (CPDLC_UL)
Downlink FANS message
CPDLC Downlink Message (CPDLC_DL)
Provided only in a response to a CPDLC uplink messages referring to the message ID in the A620 header.

23. References SWIFT Focus Group Website Documents
Documents
TDES Operational Context Document v1.0 – Final
APDS Operational Context Document Draft v0.2
Please review APDS and provide feedback by May 15th, 2019
Next meeting is scheduled for May 23, 2019 – the day after the SWIFT
Suggest moving this date 1 week later to May 30, 2019 Present STDDS-APDS Final, DCNS-DLD Draft, TFMS Status Preview
Contacts
Jay Zimmer
Felisa White

24. Backup

25. STDDS Sites

26. STDDS D-ATIS Sites Location (TRACON) Feeding Airports
Albuquerque (ABQ)
KABQ
KELP
Anchorage (A11)
PANC
Atlanta (A80)
KATL
Boston (A90)
KBOS
Buffalo (BUF)
KBUF
KCLE
Central Fla (F11)
KMCO
Charlotte (CLT)
KCLT
KGSO
Chicago (C90)
KMDW
KORD
Columbus (CMH)
KCMH
Dallas (D10)
KOKC
KDAL
KDFW
Denver (D01)
KDEN
Detroit (D21)
KDTW
Honolulu (HCF)
PHNL
Houston (I90)
KAUS
KMSY
KSAT
KHOU
KIAH
Indianapolis (IND)
KCVG
Location (TRACON)
Feeding Airports
Indianapolis (IND)
KIND
Jacksonville (JAX)
KCHS
KJAX
Kansas City (MCI)
KMCI
KTUL
Louisville (SDF)
KSDF
Memphis (M03)
KBNA
KLIT
KMEM
Miami (MIA)
KMIA
KPBI
KRSW
KFLL
KSJU
Milwaukee (MKE)
KMKE
Minneapolis (M98)
KMSP
New York (N90)
KEWR
KHPN
KJFK
KLGA
KTEB
Northern California (NCT)
KOAK
KRNO
KSFO
KSJC
Location (TRACON)
Feeding Airports
Northern California (NCT)
KSMF
Omaha (R90)
KOMA
Philadelphia (PHL)
KPHL
Phoenix (P50)
KLAS
KPHX
Pittsburgh (PIT)
KPIT
Portland (P80)
KPDX
Potomac (PCT)
KADW
KBWI
KDCA
KIAD
Providence (PVD)
KPVD
Raleigh Durham (RDU)
KRDU
Salt Lake (S56)
KBOI
KSLC
Seattle (S46)
KSEA
Southern California (SCT)
KBUR
KLAX
KONT
KSAN
KSNA
KVNY
St. Louis (T75)
KSTL
Tampa (TPA)
KTPA
Windsor Locks (Y90)
KALB
KBDL

27. STDDS APDS Sites Currently deployed at 132 sites, planned for 145
Location (TRACON)
Feeding Airports
Potomac (PCT)
KADW
KBWI
KDCA
KIAD
KRIC
Providence (PVD)
KBTV
KPVD
Raleigh Durham (RDU)
KRDU
Salt Lake (S56)
KBIL
KBOI
KSLC
Seattle (S46)
KMWH
KGEG
KBFI
KPAE
KSEA
KALW
Southern California (SCT)
KBUR
KLAX
KLGB
KONT
KSAN
KSNA
KVNY
St. Louis (T75)
KCGI
KSTL
KSUS
Tampa (TPA)
KBTR
KGPT
KTPA
Windsor Locks (Y90)
KALB
KBAF
KBDL
KORH
Location (TRACON)
Feeding Airports
Albuquerque (ABQ)
KABQ
KELP
Anchorage (A11)
PANC
Atlanta (A80)
KBHM
KTYS
KATL
KCSG
KMCN
KMGM
Boston (A90)
KACK
KBOS
Buffalo (BUF)
KBUF
KCLE
KSYR
Central Fla (F11)
KDAB
KMCO
Charlotte (CLT)
KCLT
KGSO
Chicago (C90)
KFWA
KSPI
KDPA
KMDW
KORD
Columbus (CMH)
KCMH
KDAY
Dallas (D10)
KDFW
Denver (D01)
KCOS
KDEN
KGJT
Detroit (D21)
KFNT
KDTW
Location (TRACON)
Feeding Airports
Detroit (D21)
KYIP
Houston (I90)
KAUS
KCRP
KMSY
KSAT
KHOU
KIAH
Indianapolis (IND)
KCVG
KEVV
KHUF
KIND
Jacksonville (JAX)
KCAE
KCHS
KJAX
KSAV
Kansas City (MCI)
KFSM
KICT
KMCI
KTUL
Memphis (M03)
KLIT
KMEM
Miami (MIA)
KMIA
KPBI
KFLL
Milwaukee (MKE)
KGRB
KMKE
Minneapolis (M98)
KBIS
KFAR
KGFK
KMSP
New York (N90)
KACY
Location (TRACON)
Feeding Airports
New York (N90)
KEWR
KHPN
KISP
KJFK
KLGA
KTEB
Northern California (NCT)
KFAT
KMRY
KOAK
KRNO
KSFO
KSJC
KSMF
Omaha (R90)
KDSM
KOMA
Philadelphia (PHL)
KAVP
KPHL
KILG
Phoenix (P50)
KAMA
KPHX
Pittsburgh (PIT)
KCRW
KAGC
KPIT
Portland (P80)
KEUG
KLMT
KMFR
KPDX
KPSC