Project result 140101

March 2012

SWIM SUIT FP6 project follow-up and alignment Project 14.01.01 The P14.1.1 project processed the public deliverables of the SWIM-SUIT project, determined their applicability to the SESAR Work Programme and analysed potential gaps.

The reason for doing this was to facilitate effective and rapid uptake of SWIM-SUIT results in the SESAR Work Programme (projects, tasks and lower-level activities). The gap analysis will help other SESAR projects to identify which SWIM-SUIT results are relevant, and provide information indicating what needs to be done to adopt the results efficiently in SESAR. At a first glance, one has the impression that the SWIM-SUIT project covered many SWIMrelated aspects found in SESAR WP8 (Information Management), WP14 (Technical Infrastructure), WP10-12-13-9 (Adaptation of ATM systems) and WP3/Ops-threads (for Validation). However, upon a more detailed analysis, it becomes apparent that SWIM-SUIT has a very strong technical bias, and hence, an overwhelming link to SESAR WP14.

In short, WP14 will get benefits from SWIM-SUIT project in several domains:  SWIM-SUIT user requirement capture was closer to that of WP14 than that of WP8.

The SWIM-SUIT project never intended on defining a “Concept of Operations” so there is a low level of reusability for SESAR Operational WPs (including WP8) but offers some input for SWIM design P14.1.3, P14.1.4 and P14.2.9.  The FHA methodology used by SWIM-SUIT could be reusable for Safety Assessment providing adaptation to a (slightly) different scenario within SESAR (WP16?).  SWIM-SUIT developed a set of general architecture principles which will be adopted as a basis for the SWIM design work (P14.1.3, P14.1.4 and P14.2.9), and baseline for a real-time SWIM profile approach;  SWIM-SUIT performed a Technology Survey which will be re-used as a baseline for developing the assessment/evaluation method and the technology inventory tasks part of P14.1.2.  Technical scenarios, metrics and indicators defined by the SWIM-SUIT project for validation purposes will be reused as described and extended to cover a more complete technical verification plan as required in P14.2.9.  SWIM-SUIT Financial work (such as EMOSIA methodology application, CBA framework, Economic model and probabilistic analysis) will be reused as input for SWIM Benefits contribution in P14.04.  SWIM-SUIT Institutional work provided initial ideas of the SWIM Institutional problematic in P14.04.

However, with respect to WP14 the following major differences should be noted:  The SWIM-SUIT project has not dealt with the air/ground link. Therefore, the AGDLGMS concept has not been addressed at all.

-1-



The SWIM-SUIT project did not make use of PENS as its underlying network layer.

This is understandable given that PENS was not operational in the project’s lifetime. Instead, the SWIM-SUIT project ran its prototype over internet VPNs and consequently could not perform a full technical validation (e.g. performance, latency measures).

Concerning the apparent link to system threads, the following major point should be noted.

The SWIM-SUIT project integrated its SWIM infrastructure prototype with a number of legacy systems. Due to the operational nature of these systems, no application-level functional changes were permitted in the software. Also, in a number of cases, legacy systems could only push data into the SWIM prototype, unable to consume data from the prototype (due to security and/or operational constraints). Therefore, for these legacy systems, it is clear that the SWIM-SUIT project could not, and did not, perform V3 end-toend SWIM validation (covering both SWIM infrastructure and SWIM-enabled applications/systems). Such an end-to-end validation will obviously be paramount in SESAR. Later on, the SWIM-SUIT activities in WP2 that were ATM domain-related, such as defining the ATM Information models, simply took pre-existing work (ICOG Flight Object model, AIXM, and ASTERIX) and performed minor additions/modifications. These factors explain the low-level of results re-use proposed for SESAR WP8.

Further information:

SESAR Joint Undertaking 100 avenue de Cortenbergh 1000 Brussels Belgium Contact : SESAR Corporate Communications info@sesarju.eu Tel: +32 2 507 80 00 http://www.sesarju.eu/

-2-