1. INFSO-RI-223782 VEGA Exploitation Plan The VEGA Integrated Development Process (VIDP) 3rd. All Hands Meeting Uwe Müller-Wilm VEGA Budapest, June 2009

2. INFSO-RI-223782 2 Budapest, June 2009VEGA Exploitation Plans Lessons learned from first year Feedback we got on ETICS Customers will not accept development of their commercial applications inside a system which is outside of either their or the control of the direct provider. This has several reasons which are: The already addressed security issues and privacy; Uncertainty about availability and sustainability of the system after the project phase; Lack of control and confidence, as system dependent decisions may be taken outside of the direct business relationship they have with VEGA.

3. INFSO-RI-223782 3 Budapest, June 2009VEGA Exploitation Plans Strategy changes Feedback we got led to a couple of strategy changes for VEGAs dissemination activities: Deviating from the usual intention to use the CERN hosted ETICS system, VEGA has now set up a local in house system with the help of CERN. System is now up and running, additional (project specific) worker nodes have to be attached to the system during the next weeks and months - this is dependent on project needs.

4. INFSO-RI-223782 4 Budapest, June 2009VEGA Exploitation Plans Applications SLE API: not only a demo project but also intended to be developed further on. Ongoing development of the API by VEGA (internal) shall use ETICS as underlying development tool; Demonstrating its usability to ESOC by the concrete phased in project and continuation on the development will be a more convincing argument than preparing simple demos or presentations or asking them to use ETICS for their own. ==> SLA EGOS-MF: a more recent project, which is also in the pipeline for further development has been phased in. Serves to: convince the internal developer teams of VEGA to use ETICS as an in house development environment; to be used as a reference project for acquisition activities.

5. INFSO-RI-223782 5 Budapest, June 2009VEGA Exploitation Plans EU Recommendations Recommendation 4: Follow up on the establishment of stronger collaborations, ratified by MoUs whenever appropriate, with the potential ETICS-2 customers. The links with industry and in particular with European Industry need to be enhanced so that true partnerships can be developed. Recommendation 5: Pay emphasis to elements crucial to future commercial viability like charging, registration, service level agreements, scalability, running ETICS services on third party resources and report as required to the EC.

6. INFSO-RI-223782 6 Budapest, June 2009VEGA Exploitation Plans Recent challenges I VEGA became a wholly owned subsidiary of Finmeccanica SpA. This new role, being a part of a european wide group of 60000 employees offers new challenges, which might have also impact on ETICS: VEGA was asked in this restructuring to contribute to a standardized inter group development environment which facilitates the information exchange among - and thus provide synergy effects between the different locally separated developer teams. This environment has got the current working title: VEGA Integrated Development Environment (VIDE)

7. INFSO-RI-223782 7 Budapest, June 2009VEGA Exploitation Plans Recent challenges II One promising output of our promotion activities is the intended set up of a complete new pilot project which we currently are discussing with a third party (a different company of our industrial grouping). In the current state we have yet not received the go ahead for this project, but have already the invitation to a presentation of the VIDE (including ETICS), which will take place in the next weeks at Rome.

8. INFSO-RI-223782 8 Budapest, June 2009VEGA Exploitation Plans Summary of Exploitation Strategy To define a set of procedures and processes, including ETICS as an Integrated Development Framework (details later). Steps to reach this goa l: I.Establishing ETICS as substantial part in VEGA's In House development procedures and processes, called VIDP. this includes also “missionary work” to our internal developer teams (this is ongoing); II.Developing applications for in and out house customers, using VIDP as a Framework; III.Disseminating the system also to other companies of our parent trust and to the customers originally intended (ESOC) providing that we make good experience with our approach; IV.Offering ETICS as a service, embedded in the VIDE to the outside world as already described in detail in the Exploitation Plans of DNA2.2.

9. INFSO-RI-223782 9 Budapest, June 2009VEGA Exploitation Plans Justification of this approach The long term activities (III-IV) are from my point of view a realistic scenario for an “ETICS after ETICS” approach. Only if the use of ETICS is proven by a new development which follows established and defined rules and processes it is possible to convince potential customers (inside my own company as well as in our parent group and also outside) from the added value of ETICS in contrast to their current development approaches.

10. INFSO-RI-223782 10 Budapest, June 2009VEGA Exploitation Plans THE VEGA Integrated Development Process The VEGA Integrated Development Process (VIDP) shall comply with the ISO/IEC 12207 standard describing Software Life Cycle Processes. ISO/IEC 12207 establishes a common framework for software life cycle processes, with well-defined terminology, on a “best practices” level. Also includes those aspects of system definition which are needed, to provide the context for software products and services. A mapping between ETICS and ISO/IEC 12207 has already been performed.mapping

11. INFSO-RI-223782 11 Budapest, June 2009VEGA Exploitation Plans VIDP shall comply with ISO/IEC 12207 in the two following modes: Management specific — to help develop an agreement concerning processes and activities. Via this agreement, the processes and activities of ISO/IEC 12207 are selected, negotiated, agreed to and performed. In this mode ISO/IEC 12207 is used for guidance in developing the agreement between a potential customer and VEGA as a custom specific project implementer. Implementation specific — to help select, structure and employ the elements of an established set of life cycle processes to provide products and services. In this mode ISO/IEC 12207 is used in the assessment of conformance of the project to the declared and established environment. According to this standard, VEGA intends to set up a set of procedures and processes which accompany a customer project from its initial outline up to its maintenance state.

12. INFSO-RI-223782 12 Budapest, June 2009VEGA Exploitation Plans VIDP, Part I: Part I is describing the relevant procedures and processes and is oriented to the template given by ISO/IEC 12207:2008, which lists: System Context specific related processes, further subdivided into: – Agreement; – Project Management - and – Technical processes. Software specific related processes, subdivided into: – Implementation; – Support specific - and – Software Reuse processes.

13. INFSO-RI-223782 13 Budapest, June 2009VEGA Exploitation Plans VIDP, Part II: Part II describes the concrete implementation of these procedures for a detailed project development / maintenance and covers the following stages of the software development life cycle: Requirement and Specification; Architecture and Design; Implementation and Build; Testing, Validation and Verification; Deployment; Maintenance, Review and Improvement.

14. INFSO-RI-223782 14 Budapest, June 2009VEGA Exploitation Plans ETICS as technical support tool VIDP intends to use ETICS for the technical realisation of the above described procedures and processes. Due to ETICS features as a complete infrastructure for managing projects and providing the relevant tools for the build process, configuration management, testing and quality metrics on a platform independent basis, it is assumed to be best suited for providing the technical base of such a Integrated development Environment as is planned.

15. INFSO-RI-223782 15 Budapest, June 2009VEGA Exploitation Plans VIDP, using ISO/IEC 12207 and ETICS Requirements and Specification Requirements and Specification Maintenance Review and Improvement Maintenance Review and Improvement Architecture and Design Testing, Validation and Verification Deployment Implementation and Build Implementation and Build The VEGA Integrated Development Process (VIDP)

16. INFSO-RI-223782 16 Budapest, June 2009VEGA Exploitation Plans Open Items and topics to discuss I 1Demo to Rome planned. It is intended to book this effort on the ETICS project? 2Integration of ETICS into VIDP needs to tailor the Layout and WEB Interface to the VEGA specific needs. Does this in any way conflict with the intentions and plans of the ETCS Grant Agreement? Solved. 3Windows Client / WN needed. Assume that this is based on CygWin? What is with Visual Studio Support? 4Security: we can perhaps live without the more subtle security requirements. What is a must is the read protection on project level. Without this, there is no base for success. Example... 5Metronome support: this issue must be solved. To risky to develop VIDP without having a clear commitment here... 6Maintenance issue, SLAs for the support of the ETICS SW after ETICS II.

17. INFSO-RI-223782 17 Budapest, June 2009VEGA Exploitation Plans Open Items and topics to discuss II Investments of VEGA into an “ETICS after ETICS "company" I am not authorized to give any commitments in this issue. Negotiations on this have to be performed on management level. However, what can be clearly said to this already now is, that any investment of VEGA beyond the current activities will not be realistic before the added value of an integration of ETICS into the VEGA project development has been proven and demonstrated by a pilot project and before substantial hints exist, that a business model for offering an ETICS integrated service is proven to demonstrate a realistic success.