"IT principles" Context, roadmap SISAI Item 2.1.1 Jean-Marc.Museux@ec.europa.eu

Corporate IT developments in the ESS Context : Corporate IT developments in the ESS Numerous ESS projects (ESSnets …) have developed IT solutions/software "Industry" move towards new architecture (Shared services , "Plug and Play", Data and metadata services, Enterprise BUS, …) Key drivers : rationalisation, reuse, cost efficiency

Guidelines sharing software Recent developments Guidelines sharing software CSPA

Objectives : Define a set of principles to be used for deciding on and designing ESS corporate IT development in the framework of ESSnets, ESS VIPs and other corporate initiatives "Industry" move towards new architecture (Shared services , "Plug and Play", Data and metadata services, Enterprise BUS, …) Key drivers : rationalisation, reuse, efficiency

Principles (definition) Actionable: They facilitate decision making and guide behavior. Succinct: They are focused. Specific enough to have a possible counter-argument. They represent a choice the organization has made. Clear in their implications. The implications and potential repercussions of following or not following the principle should be articulated. Relevant. It should be appropriate for a specific business context of an enterprise.

Principles There are four basic components that define an effective IT principle: Principle statement. Rationale. Lists the reasons for the principle. Implications. Addresses the actions that you must take to comply with the principle. The implications represent a choice — one among many — of how the principle will be implemented. Metrics that measure progress against implications.

IT principles Complementarity Coherence Decision architecture Solution & Technical architecture Business & Information architecture

CSPA principles

3 strands of principles Governance / decision principles to guide how ESS IT development takes place and under which circumstances Business and information principles to provide guidance on how to organize business processes and the linked information IT principles to provide guidance for the development of IT applications maximizing the possibility of reuse in the system (among MS and across processes)

Roadmap 2011 ITDG request 2012 SISAI and ITDG discussions SISAI 2013 – 3 contributions (ESTAT, CBS, NO) bringing an ESS perspective - discussion Progress report to ITDG (June virtual meeting) Task team (virtual) to integrate various components/contribution Proposal to November 2013 ITDG meeting

Decision Principles Eurostat

Scope Principles or Requirements No governance yet

Decision principles 1. Business alignment The IT development should be aligned with business needs and should support the realization of business outcome. These elements are developed in a business case document following industry standards.

Decision principles 2. Efficiency The developments should be cost efficient. Cost benefit analysis should include a scenario based on reusing existing components or their migration into the target architecture.

Decision principles 3. Genericity • The IT developments should target the setting up of generic, sustainable and reusable components. For achieving this, the design should be modular and based on industry and open standards (reference to ESS standards repository – in development).

Decision principles 4. Product governance Roles and responsibilities are defined ex ante for the whole life cycle of the product (Production management, User needs analysis and specifications, Design, development and documentation, Packaging, storage and distribution, Maintenance, support and training)

Decision principles 5. Established need The IT developments either correspond to an established need based on an ESS enterprise and capability architecture (top down) or are based on a broad stakeholder analysis (bottom up). A significant number of MSs have signed off for the use of the components.

Decision principles 6 Identification of resources and roles for the whole life cycle of the product At the definition of the project, the strategy, the role and responsibilities of the different partners (for whole span of product governance issues), the corresponding resources involved and the total cost of ownership are estimated. If development includes the sharing of costs, MoU are put in place to agree on responsibilities and duties of the partners over the whole life cycle of the product. The policy for support is clearly identified from the beginning.

Decision principles 7. Identify and consult stakeholders A user group is set up for collecting requirements and accompanying development. 8. Subscribe to architecture reviews Business case and cost benefit is reviewed and assessed by an appropriate body at ESS level The project owner asks for an architecture review of the product design.

Decision principles 9. Record initiative and product in the common catalogue Already at the launching phase, the initiatives and related documents should be posted in the industry catalog (to be put in place either in the context of CSPA or at ESS level ) so that partners are informed about the project scope and expected deliverables. When released, the software/service is registered in the common catalog.

Thank you for your attention