1. SWIM-SUIT Final User Forum

2. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Subscription First step: SubscriptionFirst step: Subscription –On FDD subscription a client provide its own identifier (a unique “name”) and (optionally) an Endpoint (and URL) where it will be notified upon data arrival and/or service requests. –Internally, the SWIM-BOX, stores the subscription information in the “SharedDataStore” (a SB internal component) The SDS is synchronized across all SB instances. Therefore, every participant will now know about this new subscription (The SDS, in FDD, acts like a distributed registry).The SDS is synchronized across all SB instances. Therefore, every participant will now know about this new subscription (The SDS, in FDD, acts like a distributed registry).

3. Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Legacy System CFMU Legacy System CFMU Legacy System LISATM Legacy System LISATM Legacy System CRISTAL MED Legacy System CRISTAL MED Subscription Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service 1.Subscribe request 2.Create Participant The CFMU swim-box instance... CFMU Description Additional Info Participant 3.Synchronize participants list

4. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Fligth Object Creation Second step: FO creationSecond step: FO creation –A client creates a new flight and publish it on the SWIM Network via the SWIM-BOX. Upon creation, it has to provide (at least) FlightKey and Trajectory clusters which are used by the SB to determine a unique (System Wide) FlightIdentifier and a list of auto-determined receivers (they are inserted in the so called “distribution list”). Internally, the SB also stores a structure in the SharedDataStore which indicates for each flight who is the “Manager” and who are the “Users” or the “Contributors”Internally, the SB also stores a structure in the SharedDataStore which indicates for each flight who is the “Manager” and who are the “Users” or the “Contributors” –If the Flight was not already existing, the SB returns the FlightIdentifier to the client and publishes the Flight Object (i.e. A Flight Summary – auto generated - plus a set of clusters as provided by the client). Upon publication, the systems in the distribution list will receive the dataUpon publication, the systems in the distribution list will receive the data

5. Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Legacy System CFMU Legacy System CFMU Legacy System LISATM Legacy System LISATM Legacy System CRISTAL MED Legacy System CRISTAL MED Flight Object Creation Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service 1.FO Creation 2.Validate information and identify USERs and CONTRIBUTORs using FlighKey and Trajectory clusters 2.Validate information and identify USERs and CONTRIBUTORs using FlighKey and Trajectory clusters CFMU... AZ100 MANAGER USERs Flight Identifier CRISTAL MED, LISATM CRISTAL MED, LISATM CONTRIBUTOR s 3.Share FO role mapping 4.Synchronize FO roles mapping

6. SWIM-SUIT Final User Forum

7. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Flight Object Update The Manager can update its own flights. This could be due to an update of its own information or following a “contribution” from another system (playing the “Contributor” role).The Manager can update its own flights. This could be due to an update of its own information or following a “contribution” from another system (playing the “Contributor” role). The Manager provides the updated clusters to the SWIM-BOX which in turn distribute them to the systems in the distribution list.The Manager provides the updated clusters to the SWIM-BOX which in turn distribute them to the systems in the distribution list. Updated data are received by each SB local instance and notified to the local clientUpdated data are received by each SB local instance and notified to the local client

8. Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Legacy System CFMU Legacy System CFMU Legacy System LISATM Legacy System LISATM Legacy System CRISTAL MED Legacy System CRISTAL MED Flight Object Update Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service 5.FO Update 6.Internal flight update and publication 6.Internal flight update and publication Flight summary AZ100 Flight identifier LISATM Manager xx EOBD/EOBT xx ADEP xx ADES.. Flight object clusters TRAJECTORY SSR FlightKey FlightPlan.. 7.Flight Object notification 8.Legacy notification 7.Flight Object notification 8.Legacy notification

9. SWIM-SUIT Final User Forum

10. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Flight Object Handover The Manager asks to the SB to perform an handover on a given FOThe Manager asks to the SB to perform an handover on a given FO The SB forwards this request to the first “Contributor” on the basis of aircraft trajectory.The SB forwards this request to the first “Contributor” on the basis of aircraft trajectory. Once the contributor accepts the request, the SB updates the roles (in a transaction) in the SharedDataStore and publish clusters affected by this modification.Once the contributor accepts the request, the SB updates the roles (in a transaction) in the SharedDataStore and publish clusters affected by this modification.

11. Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Legacy System CFMU Legacy System CFMU Legacy System LISATM Legacy System LISATM Legacy System CRISTAL MED Legacy System CRISTAL MED Flight Object Handover Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service Flight Data Domain Publish Subscribe Service Publish Subscribe Service Shared Data Store Service 1.FO Handover 2.Discovery candidate next MANAGER using available CONTRIBUTORs and Trajectory information 2.Discovery candidate next MANAGER using available CONTRIBUTORs and Trajectory information 3.Forward the Handover request to CRISTAL MED SWIM-BOX instance 3.Forward the Handover request to CRISTAL MED SWIM-BOX instance 4.Require Handover approval 5.The legacy accept the request 6.Update Flight roles mapping LISATM... AZ100 MANAGER USERs Flight Identifier CRISTAL ME D, CFMU CRISTAL ME D, CFMU CONTRIBUTOR s 7.Update Flight summary and Flight IOPINFORMATION cluster 7.Update Flight summary and Flight IOPINFORMATION cluster Flight summary Flight object clusters AZ100 Flight identifier CRISTAL MED Manager xx EOBD/EOBT xx ADEP xx ADES.. Flight Identification IOP Information 8.Flight Object notification 9.Legacy notification 8.Flight Object notification 9.Legacy notification

12. SWIM-SUIT Final User Forum

13. Story Board: Surveillance / HMI 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

14. Data Format: Asterix Cat062 binary 3e 00 24 b9 4d 22 21 12 14 41 f5 ec 00 76 fc 69 00 22 e8 90 07 dc 04 97 00 04 10 41 00 4f 53 35 30 31 20 20 XML 33 18 20 1175 3734 2010-06- 09T09:22:51.844Z 00 41.83100759983063 12.272500991821289 260.0 OS501 24-25 June 2010 SWIM-SUIT Final ser Forum, Rome

15. HMI Components 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM HMI Adapter SWIM HMI Adapter SWIM HMI Server SWIM HMI Server Browser Client(s) Browser Client(s) Based on GeoServer and uses Google Maps Handle subscriptions and receive data from SWIM SUIT

16. HMI subscribes to data 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM HMI Adapter SWIM HMI Adapter SWIM HMI Server SWIM HMI Server SWIM Box (HMI) SWIM Box (HMI) Browser Client(s) Browser Client(s) Subscriptions defined in Config file: 1)Activated on start-up 2)De-activated on shut- down Un-subscribe Subscribe Subscriptions define: areas of interest & mode (push/pull) & data format

17. HMI receives data 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM HMI Adapter SWIM HMI Adapter SWIM Box (HMI) SWIM Box (HMI) SWIM Box (ENAV) SWIM Box (ENAV) SWIM ENAV Adapter SWIM ENAV Adapter MRT SWIM HMI Server SWIM HMI Server Browser Client Browser Client Communication Pattern: Publish/Subscribe (Multicast)