1. Operational Context and Use Case Focus Group
September 6, 2018

2. Agenda Schedule TBFM SFDPS Flight SFDPS Airspace Feedback
Operational Context

3. Ops Context Document Schedule
July 2018
TBFM Closeout
SFDPS Flight
SFDPS Airspace Storyboard
Early Sept. 2018
TBFM, SFDPS Flight Closeout
SFDPS Airspace
Late Sept. 2018
SFDPS Airspace Closeout
TAIS Storyboard
Oct. 2018
TAIS
FNS Storyboard
Nov. 2019
TAIS Closeout
FNS
ITWS Storyboard
Dec. 2018
FNS Closeout
ITWS
ADPS Storyboard
Jan. 2019
ITWS Closeout
ADPS
TFMS Status Storyboard
Feb. 2019
ADPS Closeout
TFMS Status
SFDPS General Storyboard
March 2019
TFMS Status Closeout
SFDPS General
ISMC Storyboard
April 2019
SFDPS General Closeout
ISMC
May 2019
ISMC Closeout
Modified schedule moving forward to account for changes to TBFM Ops Context Document

4. TBFM
Closeout

5. TBFM Operational Context Document
1 Introduction
TBFM Aircraft Metering
2.1 TBFM Overview
2.2 Time Based Metering
2.3 TBFM Traffic Management Capabilities
2.4 References
3 TBFM MIS Service Overview
3.1 Aircraft Information <air>
3.2 Configuration Information <con>
3.3 Other Information <oth>
3.4 Adaptation Information <adp>
3.5 Synchronization
4 TBFM MIS Message Types
4.1 Aircraft Information – Air
4.1.1 Flight Plan Information Group – flt
4.1.2 Tracking Information Group – trk
4.1.3 Meter Reference Point Assignments Group – mrp
4.1.4 Estimated Time of Arrivals Group – eta
4.1.5 Scheduled Time of Arrivals Group – sta
4.1.6 Scheduling Information Group – sch

6. TBFM Operational Context Document cont.
4.2 Configuration Information – Con
4.2.1 Arrival Airport Configuration Group – aac
4.2.2 Airport Acceptance Rate Group – aar
4.2.3 TRACON Acceptance Rate Group – tar
4.2.4 Gate Acceptance Rate Group – gar
4.2.5 Meter Point Acceptance Rate Group - mar
4.2.6 Runway Acceptance Rate Group - rar
4.2.7 Super Stream Class Configuration Group - scc
4.2.8 Satellite Airport Configuration Group – sac
4.3 Other Information – Oth
4.3.1 TMA Metering Status Group – tmg
4.3.2 TMA Interface Group – int
4.4 Adaptation Information – Adp
4.4.1 TRACON Name Information Group – trn
4.4.2 Gate Names Information Group – gan
4.4.3 Airport/Runway/Configuration Names Group – apn
4.4.4 Meter Reference Point Names Group – mrn
4.4.5 Stream Class Names Group – scn
4.5 Synchronization Message
Appendix A: Acronyms

7. Feedback Received Editorial
Added subsections as needed
Based on discussion at July Ops Context Focus Group Meeting:
Expanded description of how TBFM system works
Added “2.4 References” to provide additional information how the system works
Informational
Added examples of populated data elements as needed
Explained further concept of Meter Reference Element “MRE”

8. SFDPS – Flight
Closeout

9. SFDPS – Flight Operational Context Document
Introduction
En Route Flight Data Overview - En Route Automation Modernization, References
SFDPS ERFDP – Service Overview, Message Types
SFDPS ERFDP Message Types
Flight Plan Information – FH
Flight Amendment Information – AH
Converted Route Information – HX
Cancellation Information – CL
Departure Information – DH
Aircraft Identification Amendment Information – IH
Hold Information – HH
Progress Report – PH
Flight Arrival Information – HV
Flight Plan Update Information – HU
Expected Departure Time Information – ET
Position Update – HP
Tentative Flight Plan Information – NI
Tentative Flight Plan Removal – NL
Appendix A: Acronyms
Appendix B: Flight Data Properties
Tentative Flight Plan Amendment Information – NU
Batch Track Information – BATCH_TH
Drop Track Information – RH
Interim Altitude – LH
Automated Radar Terminal System (ARTS) Flow Control Track/Full Data Block Information – HZ
Beacon Code Reassignment – BA
Beacon Code Restricted – RE
FDB Fourth Line – HF
Point Out Information – HR
Inbound Point Out Information – PT
Handoff Status – OH
Flight Plan Reconstitution Message – DBRTFPI

10. Feedback Received Editorial Informational
Incorporated all editorial feedback received
Reworded confusing text, consistent usage of acronyms
Added subsections as needed
Informational
Clarifications:
Added example data elements as needed
Specified FIXM version 3.0
How flight plan “merge” functionality works
“Controller” vs. “AU” vs. “ATC” clarification
Defined “Beacon Code”
Defined all letter codes for various data elements
“Intrafacility” vs. “Interfacility”

11. SFDPS – Airspace
Context

12. Decomposition of SFDPS – Airspace Data Elements
SWIM Flight Data Publication Service – Airspace
Sector Information
Sector Assignment Status
Sector Assignment Reconstitution
Route Information
Route Status
Route Status Reconstitution
Altimeter Information
Altimeter Setting
Altimeter Status Reconstitution

13. Sourcing SFDPS - Airspace
SWIM External
ARTCC
ERAM / HADDS
Sector Status
Route Status
Altimeter Setting
Aggregated SFDPS Data:
Sector Information
Route Information
Altimeter Information
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

14. SFDPS – Airspace Data Operational Context Document
Introduction
En Route Airspace Data Overview – Includes References
SFDPS ERADP Service Overview
SFDPS ERADP Message Types
Sector Assignment Status – SH
Route Status – HR
Special Activities Airspace – SU
Adapted Route Status Reconstitution – DBRTRI
Altimeter Status Reconstitution – DBRTAI
Sector Assignment Reconstitution – DBRTSI
Appendix A: Acronyms
Appendix B: Airspace Data Properties

15. SFDPS – Airspace Service Description
SFDPS is the SWIM program developed to provide flight information services to a wide variety of consumers in a manner that complies with SWIM standards and requirements.
Service Interface
Publish/Subscribe via JMS
Message Sets
Message Name
Description
Sector Assignment Status – SH
The Sector Assignment Status Message is used to communicate current sector and Terminal Radar Approach Control (TRACON) configurations. A sector or TRACON may either be closed or open. If the sector or TRACON is open, it is composed of one or more Fixed Airspace Volumes (FAV).
Route Status – HR
A Route Status message is used to communicate whether some adapted departure and/or arrival routes are active or not. A route status is indicated by the route name followed by either “ON” or “OFF.”
Special Activity Airspace – SU
The SU message is the Special Activities Airspace (SAA) Information message provides the status and schedules for the SAA.
Altimeter Setting – HA
The HA Altimeter-Setting message is used to communicate altimeter reference data for a particular station, generally an airport. The altimeter reference data includes the data reporting time (35a), the reporting station (13.3), and the altimeter setting (34a).
Adapted Route Status Reconstitution – DBRTRI
The Adapted Route Status Reconstitution message is sent when a client first connects to a HADDS or when a client reconnects to a HADDS due to a disruption in communication.
Altimeter Status Reconstitution – DBRTAI
The Altimeter Status Reconstitution message is sent when a client first connects to a HADDS or when a client reconnects to a HADDS due to a disruption in communication.
Sector Assignment Reconstitution – DBRTSI
The Sector Assignment Reconstitution message is sent when a client first connects to a HADDS or when a client reconnects to a HADDS due to a disruption in communication.

16. References SWIFT Focus Group Website Documents
Documents
TBFM – Operational Context Document
SFDPS – Flight – Operational Context Document
SFPDS – Airspace – Operational Context Document
Please review SFDPS – Airspace and provide feedback by September 20th, 2018
Next meeting will be September 27th, 2018
Contacts
Jay Zimmer
Felisa White