Operational Context and Use Case Focus Group February 28, 2019

Agenda Schedule Federal NOTAM System NOTAM Distribution Service (FNS-NDS) Closeout Integrated Terminal Weather System (ITWS) Operational Context SWIM Terminal Data Distribution – Tower Departure Event Service (STDDS-TDES) Preview

Ops Context Document Schedule November 2018 TAIS OCD Closeout Flight UCD Closeout FNS OCD ITWS OCD Storyboard Flow UCD Storyboard December 2018 Canceled due to holidays January 2019 Canceled due to shutdown 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 TFMS Status OCD Storyboard Aero UCD Storyboard May 2019 APDS OCD Closeout TFMS Status OCD Aero UCD SFDPS General OCD Storyboard June 2019 TFMS Status OCD Closeout Aero UCD Closeout SFDPS General OCD ISMC OCD Storyboard July 2019 SFDPS General OCD Closeout ISMC OCD ------- August 2019 ISMC OCD Closeout Schedule moved 2 months to the right due to December and January meeting cancellations At SWIFT #5 the group was interested in D-ATIS, which included in the STDDS-TDES feed TDES storyboard inserted to the February schedule and moved subsequent Ops Context documents 1 month to the right

Federal notam system – notam distribution service (FNS-NDS) Closeout Federal notam system – notam distribution service (FNS-NDS)

FNS NOTAM Publication Service publishes all FNS NOTAMS to subscribed users Publishes each NOTAM to a single message topic in Aeronautical Information eXchange Model (AIXM) 5.1 format FNS-NDS offers both Pub/Sub and Request/Reply services Ops Context will only review Pub/Sub service

FNS-NDS Operational Context Document Introduction Notice to Airmen 2.1 Introduction to NOTAMs – Explain example NOTAM and how to read it 2.2 Types of NOTAMs – List the various types of NOTAMs and when/why they are used 2.3 Federal NOTAM System – Explain FAA NOTAM Origination and Distribution services 2.4 References FNS-NDS 3.1 Service Overview 3.2 NOTAM Topic Message – Explain message headers and AIXM message body FNS Publication Message Types 4.1 NOTAMTopicMessage Appendix A: Acronyms

Feedback Expired vs Cancelled NOTAMS – Added footnote to explain differences Cancelled” status indicates a NOTAM has been manually de-activated or removed from the USNS prior to its end time by a NOTAM Issuer “Expired” do not receive a specific status in FNS-NDS, as expired NOTAMS indicate a NOTAM that was active until its end time, at which time the NOTAM was automatically deactivated by the USNS. No “Expired” status in FNS-NDS as these NOTAMS are automatically removed at their “End” time by the USNS Acronym clarifications FDC – Flight Data Center

Feedback cont. Is the NOTAM only provided in both LOCAL and ICAO format if the publisher includes both? Or is there some sort of translation process at the NOTAM office. If so is it a manual or automated process and will the NOTAM publish immediately and update with the ICAO or will the NOTAM remain as a draft until the translation is added? Most of these NOTAMs are originated via FNS FNS capability to use digital or free-text scenarios to create NOTAMs. When digital NOTAM scenarios are used, three types of translations are created Domestic (FAA) format, ICAO format and plain language The domestic format is the official one, others are provided as part of the capability of FNS All these formats are created at the time of NOTAM creation and published at the same time. NOTAM office has no role in creating them. Users can check the same data by going to the NOTAM Search application and searching for NOTAMs and looking at the various formats being provided. This is the identical information that will be delivered by NDS, which is a machine to machine interface equivalent of the NOTAM Search.

Feedback cont. I believe polygons are provided for some NOTAMS such as taxi ways and other movement area closures in the SWIM version of the NOTAMs which you can then plot on a map. Some info on how these are derived and when to expect them to be populated and why will they not always be available. I believe runway closures do not include polygons but unsure as to why. NDS does include geometries/polygons where possible and mostly for digital NOTAM scenarios Runway closure should include the geometries/polygons, if they are not then probably related to some ongoing issue or a bug. But by design they are supposed to be included. Polygons, especially for taxiway/apron NOTAMs may not perfect, because what is being delivered is version 0.1, but still should have data.

Integrated Terminal Weather Service (ITWS) Operational Context Integrated Terminal Weather Service (ITWS)

ITWS Description Provides air traffic managers and controllers current and forecasts (up to 60 minutes) of terminal weather Graphical weather information for decision support, collaboration, and common situational awareness Uses sophisticated algorithms to integrate data from FAA and NWS sensors, radars, and weather models, and from aircraft in flight Used during adverse weather at TRACONs, towers, ARTCCs, the Command Center, and airlines

Sourcing ITWS

Decomposition of ITWS Data Elements Integrated Terminal Weather Service (ITWS) Microburst/ Windshear Microburst TRACON Map Product Microburst ATIS Product Wind Shear ATIS Product Gust Front Gust Front TRACON Map Gust Front ETI Text Alerts Configured Alerts Product Hazard Text 5nm Product Hazard Text TRACON Hazard Text Long Range Terminal Weather Graphic and Text Terminal Weather Graphics Terminal Weather Text Normal Terminal Weather Text Special Precipitation Precipitation 5nm Precipitation TRACON Precipitation Long Range AP Indicated Precipitation Tornado Tornado Detections Tornado Alert Forecasts Forecast Image Forecast Accuracy Forecast Contour Storm Motion SEP Long Range Storm Motion SEP 5nm Storm Motion SEP TRACON Runway Configuration Wind Profile Miscellaneous AP Status

ITWS Operational Context Document Introduction Terminal Weather Information 2.1 ITWS Overview – Brief description of where ITWS is used and how 2.2 ITWS Weather Products – Explain weather phenomena shared by ITWS products ITWS Service Overview Explanations of each ITWS message type and associated background information (e.g., data source, rate of detection, range of detection, accuracy, precision, etc.) ITWS Message Types Appendix A: Acronyms 4.1 Microburst TRACON Map Product 4.2 Microburst ATIS Product 4.3 Wind Shear ATIS Product 4.4 Gust Front TRACON Map 4.5 Gust Front ETI 4.6 Configured Alerts Product 4.7 Hazard Text 5nm Product 4.8 Hazard Text TRACON 4.9 Hazard Text Long Range 4.10 Terminal Weather Graphics 4.11 Terminal Weather Text Normal 4.12 Terminal Weather Text Special 4.13 Precipitation 5nm 4.14 Precipitation TRACON 4.15 Precipitation Long Range 4.16 AP Indicated Precipitation 4.17 Tornado Detections 4.18 Tornado Alert 4.19 Forecast Image 4.20 Forecast Accuracy 4.21 Forecast Contour 4.22 Storm Motion SEP 5nm 4.23 Storm Motion SEP TRACON 4.24 Storm Motion SEP Long Range 4.25 Runway Configuration 4.26 Wind Profile 4.27 AP Status 4.28 ITWS Status

Storyboard SWIM Terminal Data Distribution System - Tower Departure Event Service (STDDS-TDES)

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

Sourcing STDDS-TDES

STDDS Sites

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

STDDS-TDES Operational Context Document Introduction Terminal Information Tower Departure Events Digital Automatic Terminal Information System STDDS-TDES Service Overview STDDS-TDES Publication Message Types DATISData TowerDepartureEventMessage TowerDepartureEventReconstitutionStartMessage TowerDepartureEventReconstitutionCompleteMessage ReconstitutionRequestStatusMessage Appendix A: Acronyms Appendix B: Message Headers

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

References SWIFT Focus Group Website Documents http://connect.lstechllc.com/index.cfm/main/opconfocusgroup Documents FNS Operational Context Document v1.1 – Final http://connect.lstechllc.com/files/FNS%20-%20Operational%20Context%20Document%20v1.1_2019_02_28_Final.docx ITWS Operational Context Document v0.1 – Draft http://connect.lstechllc.com/files/ITWS%20Operational%20Context%20Document%20Draft%20v0.1_2019_02_28.docx Please review ITWS and provide feedback by March 15th, 2019 Next meeting is scheduled for March 28th 2019 Present ITWS Final, STDDS-TDES Draft, STDDS-APDS Storyboard Contacts Jay Zimmer (jay.zimmer@lstechllc.com) Felisa White (felisa.white@faa.gov)