SWIM Flight Data Publication Service (SFDPS)2016/08/18 · • Contact your FAA Project Lead August...

Presented by:

Date: Federal AviationAdministration

SWIM Flight Data Publication Service (SFDPS)

User Forum Webinar

SFDPS Team

August 18, 2016

Federal AviationAdministration

AgendaØ Welcome RemarksØ SFDPS Release 1.3.0 Ø Consumer Migration Use-CasesØ Consumer On-Ramping ProcessesØ Consumer Migration TimelineØ Consumer Migration SummaryØ FAA ContactsØ SFDPS User SurveyØ SFDPS WebsiteØ Volpe Center Presentation on SFDPS 1.3.0 Ø Q&A

August 18, 2016 SFDPS User Forum Webinar 2


SFDPS Release 1.3.0Ø Provides batching of track data and other functionsØ Will be configured to provide 12 second updates in

operational environmentØ Currently available in R&D environmentØ Will become operational on February 15, 2017Ø Requires consumers to update their clients to interpret

the new batched message format and to connect via a Solace interface



Consumer Migration Use-Cases Ø Use-Case 1: Current 1.2.9 Solace Consumer

• Test client changes with 1.3.0 in R&D• No further FNTB testing necessary

Ø Use-Case 2: Current 1.2.9 Atlantic City and Oklahoma City Consumer• Migration to Solace is mandatory• Test client changes with 1.3.0 in R&D via Solace• Plan for FNTB qualification testing

• Use-Case 3: New SFDPS Consumer • Use Solace (Unless in ATL or SLC)• Test client changes with 1.3.0 in R&D• Plan for FNTB qualification testing when using Solace



Consumer Migration Use-Cases Ø Use-Case 4: Current 1.2.9 Atlanta or Salt Lake City

Consumer • No Solace appliances in Atlanta and Salt Lake City NESGs• May choose to consume 1.3.0 data from Atlanta and Salt Lake

City NEMS § Test client changes with 1.3.0 in R&D § No further FNTB testing necessary

• May choose to migrate to Atlantic City and Oklahoma City and consume 1.3.0 data via Solace§ Test client changes with 1.3.0 in R&D via Solace§ Plan for FNTB qualification testing



Consumer On-ramping Processes1. R&D Environment

• Ready to accommodate consumer testing activities with both 1.3.0 and Solace

• Your assigned FAA Project Lead can assist with getting connected to R&D Solace and SFDPS

• A lead-time of 2-3 weeks is required to configure the R&D environment for consumer testing

2. FTI National Test Bed (FNTB)• New Solace consumers are required to undergo FNTB formal

interoperability testing • A lead-time of 3-4 weeks is required to configure the FNTB

environment for consumer testing 3. Operations

• After FNTB testing has been successfully completed, it takes 2-4 weeks to get connected to the Production environment

** Note that the above timeframes are for existing consumers only. Consumers that do not have access to R&D, FNTB, and Production NEMS will require additional time to get connected.



Consumer Migration TimelineØ Schedule:

• R&D currently available for 1.3.0 and Solace testing • 9/19/2016

§ FNTB will be ready to accept consumers for qualification testing with 1.3.0 and Solace. Your FAA Project Lead can help schedule a test session.

• 1/31/2017 § Last call for FNTB testing. After this date it is too late to complete

FNTB testing in time for the February 15th cut-over. • 2/15/2017

§ 1.3.0 cut-over to Production NEMS. Consumers must be ready to switch from 1.2.9 to 1.3.0 on this date, or risk loosing their data feed.



Consumer Migration SummaryØ Migration to 1.3.0 from 1.2.9 will be in the form of a cut-

over event Ø If you have not met all of the on-ramping milestones for

the 1.3.0 migration, you may lose access to the SFDPS data until successful completion of the on-ramping process

Ø Consumers will be treated on a first-come-first-served basis

Ø We urge you to update your consumer client to be compatible with 1.3.0 and undergo the prerequisite testing activities early, to avoid losing your data feeds from SFDPS



Consumers, Take Note


Act early to avoid losing your feedUpdate your consumer client to


FAA Contacts

Ø New SFDPS Consumers: • If you have not yet been assigned an FAA Project Lead, use

the [email protected] email address to request consumption of SFDPS data

Ø Existing SWIM Consumers: • Work with your assigned FAA Project Lead to get started with

SFDPS 1.3.0Ø For any issues

• Contact your FAA Project Lead



SFDPS User SurveyØ Please complete the SFDPS User Survey we sent last

week.https://www.surveymonkey.com/r/CX2FWQF



Coming Soon, the SFDPS WebsiteØ SFDPS user forum

announcementsØ User forum

presentationsØ Q&As on SFDPS topicsØ SFDPSConnect tutorial

videoswww.faa.gov/nextgen/programs/swim/sfdps/



SFDPS 1.3.0

Ø Presentation from Volpe Center


SFDPSVersion1.3.0BatchedTrackMessages

TheNationalTransportationSystemsCenter

Advancing transportation innovation forthepublic good

U.S. Department of TransportationJohn A. Volpe National Transportation Systems Center

April 21, 2016

2August18,2016

SFDPSBackground

q SFDPSistheSWIMinterfaceforERAM§ SFDPSreceivesCMSmessagesfromERAMviaHADDSandpublishesXMLmessages

toconsumersviaNEMSq SFDPSproducerservicesinclude:

§ Publish/Subscribeservices§ Request/Responseservices

q SFDPSpublishesfourtypesofmessages§ FlightMessagesinSimpleXMLorFIXMXMLformat

o AllflightmessagescorrelatedthroughanSFDPSflightidentifiero Flighttrackupdatemessagesavailableat:

– One-minutefrequency– 12-secondfrequency

§ AirSpacemessagesinSimpleXMLorAIXMXMLformat§ Operationalmessages§ GeneralInformationmessages

3August18,2016

InfrastructureConstraints

q Themessageratesandbandwidthusageexceededtheinfrastructurecapacity.

q InNovember,2015,SFDPSconsumersweresignificantlyrestrictedinordertoreducebandwidthandmessagerates.

q Alluserswerelimitedto:§ Flighttrackupdatesatone-minute frequencyonly§ FlightMessagesinFIXMXMLformatonly§ AirSpacemessagesinAIXMXMLformatonly§ Operationalmessages§ GeneralInformationmessages

4August18,2016

PeakBandwidthandMessageRates

SFDPS NEMS

ClientFIXM

12 Second

ClientSimpleXML

12 Second

ClientFIXMOne

Minute

20Mbps1200Msgs/sec

10Mbps600Msgs/sec

10Mbps600Msgs/sec

1.8Mbps125Msgs/sec

Asdeployed,July,2015

5August18,2016

SFDPS1.3.0– TheSolution

q SFDPS1.3.0solvestheproblemofexcessivemessagerateandbandwidthusagebybatchingtrackmessages.

q SFDPS1.3.0will:§ Substantiallyreducemessageratesandbandwidth usage

o Achievelevelscomparabletothecurrent,restrictedflow§ Removetheneedforarestricteddatafeed

o Restorethe12-secondtrackupdates

6August18,2016

OverviewofBatchinginSFDPS1.3.0

q BatchingbundlesmanytrackmessageswithsamepropertyvaluestogetherandsendsthemasoneJMSmessage

q TrackmessagesaresentfromCentersforeveryactiveflightevery12seconds§ 90%ofallmessagesand90%ofbandwidth

q Allpub/subtrackmessageswillbebatched§ Newmessagetypes– BATCH_TH,BATCH_TH_FIXM§ Upto100trackupdatesperbatch§ Tracksreturnedinarequest/responsewillnotbebatched

q Batchingisbasedonproperties:§ SourceFacility– TheARTCCthemessagecamefrom§ Trackfrequency– Oneminutefrequencyornot§ Authoritativesource– TrackcamefromcontrollingARTCCornot§ Sensitivity– Flightismilitary/sensitiveornot

7August18,2016

PeakBandwidthandMessageRates

SFDPS NEMS

ClientFIXM

12 Second

ClientSimpleXML

12 Second

ClientFIXMOne

Minute

20Mbps1200Msgs/sec 10Mbps

600Msgs/sec

10Mbps600Msgs/sec

1.8Mbps125Msgs/sec

AsDeployedJuly,2015

ClientsrestrictedtoOne-minutetracks,

FIXMonly

20Mbps1200Msgs/sec

One-minute1.8Mbps

125Msgs/sec

NoSimpleXMLAllowed

1.8Mbps125Msgs/sec

5 Mbps220Msgs/sec

2 Mbps100Msgs/sec

2Mbps100Msgs/sec

0.5Mbps85Msgs/sec

1.3.0

8August18,2016

PeakBandwidthandMessageRatesSummary

SFDPS

NEMS

ClientFIXM

One Minute Track

20 Mbps 1200 Msgs/sec


5 Mbps 220 Msgs/sec Client

SimpleXML12 Second Track

ClientFIXM

12 Second Track

As Deployed

Clients RestrictedFIXM Only

One Minute Tracks

Version 1.3.01.3.0


One Minute Track 1.8 Mbps

125 Msgs/sec

2 Mbps 100 Msgs/sec

2 Mbps 100 Msgs/sec


No Simple XML

2 Mbps 100 Msgs/sec

1.8 Mbps 125 Msgs/sec



5 Mbps 220 Msgs/sec

2 Mbps 100 Msgs/sec


9August18,2016

Howbatchingworks

q A Centersendstrackmessagesforallflightsitismonitoringeverytwelveseconds.§ Onetrackperflightevery12seconds.§ SFDPSreceivesthemallatonce.

q SFDPSassignsvaluestothebatchingproperties:§ SourceFacility§ One-minutefrequency§ Authoritative§ Sensitive

q SFDPSsortsthetrackmessagesintooneofsixbatchesbasedonthepropertyvalues.

q Ifabatchfillsupwith100messages,itissentimmediately.q Unfilledbatchesaresentafteronesecond.

10August18,2016

HowbatchingworksOne12-secondUpdate

NoNoNo

NoYesNo

YesYesNo

NoNoYes

NoYesYes

YesYesYes

OneMinuteAuthoritativeSensitive

ZAUtrackmessages 15:00:00

11August18,2016

HowbatchingworksTwoflightsoverfive12-secondupdates

NoNoNo

NoYesNo

YesYesNo

NoNoYes

NoYesYes

YesYesYes

OneMinuteAuthoritativeSensitive

ZAUtrackmessages 15:00:0015:00:1215:00:2415:00:3615:00:48

12August18,2016

Howbatchingreducesbandwidth

q Everymessageiscompressed.q Compressionimproveswithmoretextinamessage.

§ Especiallyredundanttext.§ XMLformattedmessageshavelargeamountsofredundant text.

q Asingletrackmessageiscompressedbyhalf.q Abatchoftrackmessagescanbecompressedby90%.

13August18,2016

SFDPS1.3.0ConsumerBenefits

q Userscanreceive:§ FlightData

o Choiceof12-secondtrackupdatesorone-minute trackupdates§ AirspaceData

o ChoiceofAIXMformatorSimpleXML format§ OperationalData§ GeneralMessages§ Request/response forqualifiedclientprograms

o FlightandAirspacereconstitutiono Fifteendayhistory

14August18,2016

ConsumerImpacts

q Clientprogramswillneedtoun-batchthetrackmessagesq FIXMflightdatamessages:

§ Newrootelement– MessageCollectiono NochangetoFIXMschema– remainsCore3.0/USExtension3.0o Existingusersmustmodify theircodetousethenewrootelement

§ Newmessagetype- BATCH_TH_FIXM§ Threepropertiesmoved insidetheFIXMtrackmessage

o Flightoperator, origin,destination

q SimpleXML flightdatamessages:§ NewSimpleXML schema– version1.3.8(updated06/14/2016)

o Existingusersmustreplacecurrentversion1.2schema§ Newmessagetype- BATCH_TH

15August18,2016

SFDPS ConnectVersion2.1.3

16August18,2016

SFDPSConnectOverview

q PrimarygoalofSFDPSConnectistoprovidesamplecodedemonstratinghowuserscanwriteclientapplicationstoconnecttoSFDPSviaNEMS,receiveandprocessdata.

q Secondarygoal:SFDPSConnectcanbeused,asis,toreceivedata.

17August18,2016

SFDPSConnectRelease

q Sourcecodepackagewhichincludessourcecode,configurationfilesandbuildfiles

q Executablepackagewhichcanberunwithoutabuildq DocumentationforSFDPSConnect:

§ Readme§ QuickStartGuide§ UsersGuide§ ConsumerReferenceManual

q SFDPSdocuments:§ JMSDD– detaileddescriptionsofallmessagesandfields§ WSDD– detaileddescription ofrequest/response

18August18,2016

SFDPSConnectRelease

q SFDPSConnect ReleaseandSFDPSdocumentsareavailableonNSRR

o https://nsrr.faa.gov/sites/default/files/SFDPSConnect-Release-2-1-3-08012016.zip

o https://nsrr.faa.gov/sites/default/files/SFDPSConnect-v2.1.3-source.tgzo https://nsrr.faa.gov/sites/default/files/SFDPSConnect-v2.1.3-Documentation.zip

o https://nsrr.faa.gov/sites/default/files/sfdps-connect-tutorial-1-v2_0.zipo https://nsrr.faa.gov/sites/default/files/sfdps-connect-tutorial-2-final.zip

19August18,2016

SFDPSConnectVideoTutorialSeries

q VideoTutorial1: SFDPSConnectOverview

q VideoTutorial2:SFDPSConnectPub/Subcodeoverview-includinghowtoprocessJMSdatafromSFDPS.ThissessionwillalsocoverchangesneededforprocessingbatchedTHmessages.


Q & A

Ø You can ask questions by typing your question into your webinar panel. We will read your question aloud for you and give an answer.

Ø Or, Click on ‘Raise hand’ icon. We will unmute you and you can ask your question.

14SFDPS User Forum WebinarAugust 18, 2016

Date post:	18-Sep-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

SWIM Flight Data Publication Service (SFDPS)2016/08/18 · • Contact your FAA Project Lead August...

Documents