3
09/12/2009 Rome, SWIM-SUIT User Forum 3/25 WP4 – SWIM-SUIT Validation The validation is based on the user requirements defined in WP1, which are expected to cover such topics as : –Information content, timeliness, and accuracy; –Information update rates; –Safety aspects related to criticality of data shared/managed; –Security required for data access and management. The validation is based on the prototypes developed in WP2, which have been integrated in the overall SWIM-SUIT system within the WP3 context. WP4 produces the Validation Report and Recommendations for Further Activities

4
09/12/2009 Rome, SWIM-SUIT User Forum 4/25 Validation Objectives Demonstrate the feasibility of SWIM as a key SESAR technical enabler Assess the benefits for the whole European ATM System Define the first lessons learnt and recommendations for the future SWIM

5
09/12/2009 Rome, SWIM-SUIT User Forum 5/25 SWIM-SUIT and E-OCVM An E-OCVM based approach has been used, in line with SESAR validation strategy –SWIM-SUIT currently lies between V2 – Concept elaboration and feasibility V3 – Integration and pre-industrial development

13
09/12/2009 Rome, SWIM-SUIT User Forum 13/25 Data Collection and Analysis Methods Automatic tools are being developed to extract measurements according to the defined metrics Qualitative and quantitative analysis of collected results will be provided These results will act as an input for lessons learnt and further recommendations WP4.3 WP4.4 WP4.5

18
09/12/2009 Rome, SWIM-SUIT User Forum 18/25 Experimental Plan and Exercises All aspects of the SWIM-SUIT system are being validated: –Core functionalities: Publish, Subscribe, FO Creation –Typical Use Cases: FO Handover between ATSUs, FO Update, SDD and AID Data Exchange –More complex interaction schemes (i.e. D4.2.1 Scenario 9.1): A flight simulator updates the ETA of a flight This action triggers a sequence recalculation in the ground AMAN system The updated sequence is then accepted and published by the relevant ATSU

19
09/12/2009 Rome, SWIM-SUIT User Forum 19/25 Experimental Plan and Exercises ATSU 1ATSU 2 New Flight Level Constraint Recalculated Trajectory Recalculated Trajectory The FMS is notified of bad weather conditions over a specific segment of its route The FMS triggers a trajectory recalculation by way of a set_constraint (Flight Level) service invocation The ATSU in charge of the FO updates and publishes the new trajectory The next ATSU takes responsibility for the flight and may trigger further constraints (i.e. AMAN sequence updates) FO Handover Target Scenario: ATM-4 level Capabilities Emulation

20
09/12/2009 Rome, SWIM-SUIT User Forum 20/25 Ongoing Activities: US-Europe SWIM Interoperability Develop initial capabilities to study interoperability between US and European SWIM infrastructures in coordination with the FAA Establish connection between SWIM-SUIT prototype and Boeing US SWIM laboratories (which include technologies representative of FAA SWIM) through BR&TE Initial analysis of interoperability between SWIM-SUIT and US SWIM through SDD and FDD data sharing (transoceanic scenarios) Achieving interoperability between the two systems will provide a reference framework to evaluate performance and operational benefits to the stakeholders involved: –e.g. surveillance consumers can use Aircraft System Tracks in order to have an overall view of the air traffic status.

22
09/12/2009 Rome, SWIM-SUIT User Forum 22/25 Ongoing Activities: NATS Heathrow A-CDM Shadow Mode Application Four main demonstration areas have been identified: –Reception of an IFPL from CFMU over the SWIM Network –TSAT (DMAN) data sharing with Boeing FMS (cockpit display) –TSAT (DMAN) data sharing with Boeing ISPOC –A-CDM NATS / Air France interaction Two scenarios have been defined to match these 4 demonstration areas: –Air France departure from London Heathrow to Paris –Departure from London Heathrow to Madrid Further investigation is required

23
09/12/2009 Rome, SWIM-SUIT User Forum 23/25 Analysis of Preliminary Results and First Feedback A first set of Technical Scenarios has been carried out –Endurance and stress tests show that the system can properly handle significant workloads Pseudo Operative Validation Sessions have been started –Successfully tested core functionalities such as Subscription, FO Publishing and Handover –Further scenarios have been scheduled between December 2009 and April 2010, according to legacy systems availability

24
09/12/2009 Rome, SWIM-SUIT User Forum 24/25 Useful Resources The following deliverables can be used as reference for the validation process: –D4.2.1: Validation Plan –D4.3.1: First validation – session results and feedback (in progress) These documents will be made available for download on the SWIM-SUIT website (www.swim-suit.aero)