Operational Context and Use Case Focus Group August 01, 2019

Agenda Focus Group Updates TFMS Status SFDPS General STDDS ISMC Closeout SFDPS General Operational Context STDDS ISMC Storyboard

Focus Group Updates 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 Early August 2019 TFMS Status Closeout SFDPS General STDDS ISMC Storyboard Late August 2019 SFDPS General Closeout STDDS ISMC TFMS Request/Reply Storyboard September 2019 STDDS ISMC Closeout TFMS Request/Reply SFDPS Airspace Data Query Storyboard October 2019 TFMS Request/Reply Closeout SFDPS Airspace Data Query SFDPS Flight Data Query Storyboard November 2019 SFDPS Airspace Data Query Closeout SFDPS Flight Data Query Submit PIREP (WMSCR) Storyboard December 2019 SFDPS Flight Data Query Closeout Submit PIREP (WMSCR) ----------- January 2020 Submit PIREP (WMSCR) Closeout Only drafting Operational Context Documents moving forward *OCD – Ops Context Document UCD – Use Case Document Will begin addressing Request/Reply services in August Schedule subject to change if service updates are released and existing Operational Context documents need to be updated Coordinating with each service’s producer program to get documents uploaded to NSRR, will likely result in minor updates to documentation based on their comments Next SWIFT scheduled for Aug 8, hosted by United Airlines, Denver, CO Registration link on SWIFT website: https://connect.lstechllc.com/index.cfm/main/swiftregistrations

Operational Context TFMData-Status

TFMS Messages TFMS includes multiple messages with large data sets, sent through the TFMData service Flight Data International Data Terminal Data TFMS Request Reply Flow Information TFMS Status Separate Ops Context Documents were written for Flight and Flow Plan to address Request Reply once all other Ops Context documents are completed

TFMS Status TFMData sends/receives data from multiple SWIM services, which impact the information that TFMS produces TFMData Status business function provides status of all of the data flows that directly or indirectly contribute to TFMS, this includes both TFMS and non-TFMS data flows: NAS Flight Data TBFM Flight Data SWIM Terminal Data Distribution System (STDDS) Runway Visual Range (RVR), Surface Movement Events, and Tower Departure Events Aeronautical Information Management (AIM) Special Activity Airspace (SAA) Schedule Events International Data Providers Input and Output Terminal Data Input and Output TFMData Request and Replies TFMData Flight Data TFMData Flow Information

TFMS Status Operational Context Document Introduction Traffic Flow Management Data Flows References TFMS Status Service Overview TFMData Status TFMS Status Message Types tfmdataStatus Appendix A: Acronyms

Comments No comments received If no comments are received, the first draft will become the final version Group is encouraged to review documentation to ensure we address concerns

Operational Context SFDPS General

SFDPS Messages SFDPS publishes multiple messages with large data sets, generally these are republished En Route Automation Modernization (ERAM) messages Flight Data Airspace Data Operational Data General Information Separate Ops Context Documents were written for Flight and Airspace Operational Data not applicable to Airspace Users Data pertains to traffic counts, ATC sign in/out, and beacon code counts

Sourcing SFDPS – General SWIM External ARTCC ERAM / HADDS Aggregated SFDPS General Data General Information Interim Altitude Status Unsuccessful Transmission Hold Status ERAM Status Goal is to develop a common understanding of the data Data analysis will include traceability of data Includes discussion on how data is used in the NAS

SFDPS General Messages Message Name ERAM Message Code Description General Information GH Used to communicate a free-form text message from one facility to one or more other facilities. The content of the message is the free-form text, contained in an inter-facility remarks field (11c). Interim Altitude Status Information HE Provides interim altitude status information on all active aircraft to a client during the initialization process. Hold Status Information HO Provides hold information (holding fix, and estimated fix departure time for definite-duration holds) on all active aircraft to a client during the initialization process. ERAM Status Information HS Provides ERAM up/down status, sent when an ERAM status change occurs. Unsuccessful Transmission Information UI Sent by ERAM when transmission of flight data to a remote facility is unsuccessful either due to a transmission error or because transmission of the flight data to the remote facility is inhibited.

SFDPS General Operational Context Document Introduction En Route General Data Overview En Route Automation Modernization (ERAM) References SFDPS ERGMP Service Overview Messages SFDPS General Message Types General Information - GH Interim Altitude Status Information - HE Hold Status Information - HO ERAM Status Information - HS Unsuccessful Transmission Information - UI Appendix A: Acronyms Appendix B: SFDPS General Message Properties Appendix C: Sample SFDPS General Message

Storyboard SWIM Terminal Data Distribution System (STDDS) Infrastructure System Monitor and Control (ISMC)

STDDS ISMC Background STDDS interfaces with tower and Terminal Radar Approach Control (TRACON) systems to provide terminal events and other airport information at TRACONS. Runway Visual Range (RVR) Electronic Flight Strip Transfer System (EFSTS) Airport Surface Detection Equipment Model X (ASDE-X) /Airport Surface Surveillance Capability (ASSC) Tower Data Link Service (TDLS) Standard Terminal Automation Replacement System (STARS) STDDS is suite of multiple information services Airport Data Service (APDS) Surface Movement Event Service (SMES) Terminal Automation Information Service (TAIS) Tower Departure Event Service (TDES) Infrastructure Service Monitor and Control

STDDS ISMC Messages STDDS ISMC service publishes detailed status information for individual STDDS information services Airport Data Service Surface Movement Event Service Terminal Automation Service Tower Departure Event Service STDDS Status In each information service’s status message, there is status information for individual sites and TRACON systems that provide information to each STDDS information service.

Sourcing STDDS ISMC

RVR EFSTS ASDE-X ASSC TDLS STARS Sourcing STDDS ISMC TRACON Systems RVR EFSTS ASDE-X ASSC TDLS STARS STDDS ISMC SWIM External Services Statuses STDDS Airport Data Service Terminal Automation Service Tower Departure Event Service Surface Movement Event Service STDDS ISMC Data Goal is to develop a common understanding of the data Data analysis will include traceability of data Includes discussion on how data is used in the NAS

STDDS ISMC Messages Message Name Message Code Description Airport Data Service AS Provides the status of the APDS and external RVR links associated with the service. Surface Movement Event Service SS Provides the status of the SMES and external ASDE-X/ASSC links associated with the service. Terminal Automation Service IS Provides the status of the TAIS and external STARS links associated with the service. Tower Departure Event Service TS Provides the status of the TDES and external TDLS and EFSTS links associated with the service. STDDSStatus DS Provides detailed STDDS system status every 2 minutes.

STDDS ISMC Operational Context Document Introduction STDDS ISMC Data Overview SWIM Terminal Data Distribution System Infrastructure System Monitor & Control References STDDS ISMC Service Overview Messages STDDS ISMC Message Types Airport Data Service - AS Surface Movement Event Service - SS Terminal Automation Service - IS Tower Departure Event Service - TS STDDS Status – DS Appendix A: Acronyms Appendix B: Message Headers

References SWIFT Focus Group Website http://connect.lstechllc.com/index.cfm/main/opconfocusgroup Documents TFMS Status Operational Context Document v1.0_2019/08/01_Final This is still the link to the first draft, if no comments received it will become the final draft SFDPS General Operational Context Document Draft V0.2 Contacts Jay Zimmer jay.zimmer@lstechllc.com Felisa White felisa.white@faa.gov