1 / 24

Operational Context and Use Case Focus Group

Operational Context and Use Case Focus Group. June 27, 2019. Agenda. Focus Group Updates Data Communications Network Service (DCNS) – Data Link Dispatch (DLD) Closeout TFMS Status Operational Context SFDPS General Storyboard Aeronautical Use Case Closeout. Focus Group Updates.

zimmermann
Download Presentation

Operational Context and Use Case Focus Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Operational Context and Use Case Focus Group June 27, 2019

  2. Agenda • Focus Group Updates • Data Communications Network Service (DCNS) – Data Link Dispatch (DLD) • Closeout • TFMS Status • Operational Context • SFDPS General • Storyboard • Aeronautical Use Case • Closeout

  3. Focus Group Updates • 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 Only drafting Operational Context Documents moving forward *OCD – Ops Context Document UCD – Use Case Document

  4. Closeout Data Communications Network Service (DCNS) – Data Link Dispatch (DLD)

  5. 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.

  6. 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

  7. Sourcing DCNS-DLD

  8. 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) • Uplink/Downlink Message Data Types • 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)

  9. Comments • Can we explain “direct access into dispatcher flight tracker software” a little more? Or that is the airline’s responsibility? • Modified text to read “Allows airlines to ingest flight clearances and requests directly into airline dispatcher flight tracking software for synchronized clearance and flight planning updates” • Clarification of time zones • All times are in GMT and noted in the text • Request for examples of tail numbers • Added: “For example: N930NN, N282DF, F-GLZK, etc.” • Request for examples of ATSU and Data Link Service Providers (DSP) • Added references to the sections that include those examples in the text. • What does [.]* mean in terms of formatting? • Any free text ASCII symbols/letters/numbers

  10. Operational Context TFMData-Status

  11. 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

  12. 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

  13. 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

  14. tfmdataStatus Data Elements • service – identifies the service that is that provides the data e.g. STDSS • businessFunc – identifies the business function within the service e.g. RVR • Facility – identifies the facility that is the origin of the data e.g. PHL • direction – identifies the direction of the flow relative to the TFMData service • state – identifies if a particular flow is ENABLED or DISABLED within TFMS • time – the last time a message was received or transmitted • numberMsgs– number of message received or transmitted since the session (JMS) initiation

  15. Storyboard SFDPS General

  16. 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

  17. Sourcing SFDPS – General ARTCC SFDPS SWIM External ERAM / HADDS ARTCC ERAM / HADDS • Aggregated SFDPS General Data ARTCC • General Information • Interim Altitude Status • Unsuccessful Transmission • Hold Status • ERAM Status ERAM / HADDS

  18. SFDPS General Messages

  19. SFDPS General Operational Context Document • Introduction • En Route General Data Overview • En Route Automation Modernization (ERAM) • References • SFDPS General • 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

  20. Closeout Aeronautical Use Case

  21. Aeronautical Use Case Table of Contents 1 Introduction 1.1 SWIM Aeronautical Information Services 1.1.1 SWIM Aeronautical Data Functionality 1.1.2 Aeronautical Information Service Definitions 1.2 Overview of Use Case 2 Problem Statement 2.1 Current State 2.2 Perspectives 2.3 Current State Operational Example 2.3.1 Overview of Departure Operations in the Current State 2.3.2 En Route Operations in the Current State 2.3.3 Arrival Operations in the Current State 3 Future State 3.1 Data Exchanges 3.2 Future State Operational Examples 3.2.1 Departure Operations in the Future State 3.2.2 En Route Operations in the Future State 3.2.3 Arrival Operations in the Future State 3.3 Benefits 3.4 Conclusion Appendix A – FNS-NDS and SFDPS Airspace Messages Appendix B – Acronym Listing

  22. Data Availability Using FNS/Airspace DataImproves AU event awareness and strategic planning

  23. Comments • All comments were editorial or clarification changes, all edits were accepted • This is the last Use Case document on the schedule • Use Case Focus Group will disband unless need for new use cases are identified

  24. References • SWIFT Focus Group Website • http://connect.lstechllc.com/index.cfm/main/opconfocusgroup • Documents • DLD Operational Context Document v1.0 Final • DCNS DLD - Operational Context Document v1.0_2019_06_27_Final • TFMS Status Operational Context Document Draft v0.1 • TFMS Status - Operational Context Document Draft v0.1 • Aeronautical Use Case v1.0 Final • Aeronautical Data Use Case Doc Draft v1.0_2019_06_27_Final • Please review TFMS Status and provide feedback by June 15th, 2019 • Next meetings are scheduled for July 25 and Aug 22. Request to reschedule to Aug 1 and Aug 29 due to availability • Contacts • Jay Zimmer jay.zimmer@lstechllc.com • Felisa White felisa.white@faa.gov

More Related