SFDPS Airspace Data Query Request/Reply - Operational Context and Use Case Focus Group

1. Operational Context and Use Case Focus GroupSFDPS Airspace Data Query Request/Reply September 26, 2019

2. Agenda • Focus Group Updates • STDDS ISMC • Closeout • TFMData Request/Reply • Operational Context • SFDPS Airspace Request/Reply • Storyboard

3. Focus Group Updates • Schedule subject to change if service updates are released and existing Operational Context documents need to be updated • SWIFT 7 presentation posted to SWIFT website, meeting minutes being finalized • All documents are now on the NSRR as reported at SWIFT 7 • SWIFT 8 scheduled for November 7, 2019 hosted by Delta Airlines – Atlanta, GA • Registration link on SWIFT website: https://connect.lstechllc.com/index.cfm/main/swiftregistrations Only drafting Operational Context Documents moving forward *OCD – Ops Context Document UCD – Use Case Document

4. Closeout SWIM Terminal Data Distribution System - Infrastructure System Monitor and Control(STDDS – ISMC)

5. STDDS – ISMC Background • STDDS interfaces with tower and Terminal Radar Approach Control (TRACON) systems to provide SWIM data and terminal events to NAS and non-NAS consumers • STDDS interfaces with: • Runway Visual Rang (RVR) system • Electronic Flight Strip Transfer System (EFSTS) • Airport Surface Detection Equipment Model X (ASDE-X) system • Airport Surface Surveillance Capability (ASSC) system • Tower Data Link Service (TDLS) system at airports to accept, derive and publish airport information. • Standard Terminal Automation Replacement System (STARS) General NAS User Services (GeNUS) interface at TRACONs

6. STDDS – ISMC Messages • STDDS - ISMC publishes status information and messages for external systems associated with an STDDS site by providing input data to the rest of the STDDS services. The ISMC service also publishes detailed STDDS status information messages. • Airport Data Service • Surface Movement Event Service • Terminal Automation Service • Tower Departure Event Service • STDDS Status

7. Sourcing STDDS – ISMC STDDS - ISMC STDDS – System (Site) STDDS/ NEMS TAIS STARS TDES TDLS EFSTS STDDS • STDDS ISMC Data • Airport Data Service • Surface Movement Event Service • Terminal Automation Service • Tower Departure Event Service • STDDS Status

8. STDDS ISMC Operational Context Document • Introduction • Terminal Area Data • Airport Data Services • Surface Movement • Terminal Automation • 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

9. Comments Received • No feedback received • If no comments are received draft will become final version

10. Operational Context TFMData Request/Reply

11. TFMData Request/Reply Background • The TFMData Request/Reply Service allows TFMS to accept various requests for flight data and flow information • Requests based on a defined list of requests, and to evaluate the success of the system response to the request. • The request/reply client provides the capability to read valid XML documents from a specified location, submit the requests to TFMS, receive the reply messages, and store the replies as files. • All messages sent/received over JMS

12. Sourcing TFMData

13. TFMS Request/Reply Messages • Note that not all these requests and replies are 1:1 • Specific request/reply combinations are detailed in the draft document • Flight Operators can provide terminal flight data elements FDBLOCK request in the flightCreate and flightModify messages • Reply will be ERROR or SUCCESS

14. TFMData Request/Reply Processing Example Requests/Replies

15. TFMS – Request/Reply Operational Context Document • Review Guidance • Document is 400 pages, please focus review on first 3 sections • Please ensure we included enough clarity on how requests are made and how its processed as a reply • Introduction • TFMS – Request/Reply Overview • Flight Data • Flow Data • References • TFMS – Request/Reply • Service Overview • Messages • Include context of when request would be sent, and which replies correlate to which requests • Request Message Types ~220 pages, additional changes to be made to final draft • Reply Message Types ~140 pages, additional changes to be made to final draft • Appendix A: Acronyms

16. Storyboard SFDPS Airspace Data Query

17. SFDPS Airspace Data Query Background • SFDPS En Route Airspace Data Query (ERADQ) is a Request/Reply Service that allows consumers to request specific data sets by specifying values on the request messages • Users may request messages SFDPS received in the last fifteen days or they may request current flight, sector, route or altimeter data. • To fulfill these requests, SFDPS will provide four standard SOAP-over-HTTPS web services These four web services are: • En Route Flight Data Publication • En Route Airspace Data Publication • En Route Operational Data Publication • En Route General Message Publication

18. SFDPS Airspace Data Query Background • SFDPS processes request and generates response message(s) streams back to the consumer over Simple Object Access Protocol (SOAP) web service • Requests based on a defined list of requests, and to evaluate the success of the system response to the request. • 2 response data streams – SOAP and XML • SOAP responses are subscription confirmation/error responses • XML responses are the actual airspace data requested • XML response data is returned to users over the JMS connection between SFDPS and NEMS. • Reply data is only in SimpleXML format – AIXM is not available

19. SFDPS ERADQ *Subscriptions in this case refer to what users may think of as requests – essentially a one-time subscription to a specific data set matching the user’s criteria

20. JMS XML is identical to the structure/ format of the SFDPS pub/sub services – this is the actual airspace data users request SOAP over web services is the actual subscription requests and responses - “I want this specific data set” > “Ok data set approved”

21. Sourcing SFDPS Airspace Data • SWIM Flight Data Publication (SFDPS) has a multiple services, this document is concerned with the Airspace Data set • Source data comes from En Route Automation Modernization (ERAM) ARTCC ERAM / HADDS SFDPS SWIM External ARTCC • - Sector Status • - Route Status • - Altimeter Setting • - Special Activities • Airspace ERAM / HADDS • Aggregated SFDPS Data: • - Sector Information • - Route Information • - Altimeter Information • -Special Activities Airspace ARTCC ERAM / HADDS

22. SFDPS Airspace Data Message Set

23. SFDPS Airspace Data Request/Reply Messages Results of the subscription request processing. If no faults were generated, this response will contain the subscription id that the consumer can use to track the subscription Subscription Request Message containing a list of subscription criteria that will be used by SFDPS to establish a subscription Once the subscription request is processed, the actual XML containing the requested data will come in a separate stream over JMS SFDPSConnect software available to help users create/process requests/responses

24. SFDPS Airspace Data – Operational Context Document • Introduction • En Route Airspace Data Overview – Includes References • SFDPS ERADQ Service Overview • SFDPS ERADQ Subscription Requests • SDFPS ERADQ Subscription Responses • SFDPS ERADQ XML Reply Messages Appendix A: Acronyms Appendix B: Airspace Data Properties

25. References • SWIFT Focus Group Website • http://connect.lstechllc.com/index.cfm/main/opconfocusgroup • Documents • STDDS ISMC Operational Context Document Draft v0.1_2019_08_28 • If no comments received draft will become final version • TFMS Request Reply - Operational Context Document Draft v0.1 • Please review and provide comment by 10-15-19 • Next Meeting 10/24/19 • TFMS R/R Closeout, SFDPS Airspace Data Query Operational Context, SFDPS Flight Data Query Storyboard • Contacts • Jay Zimmer jay.zimmer@lstechllc.com • Felisa White felisa.white@faa.gov