SISAI STATISTICAL INFORMATION SYSTEMS ARCHITECTURE AND INTEGRATION

Slides:



Advertisements
Similar presentations
Alignment of COBIT to Botswana IT Audit Methodology
Advertisements

ESS VIP project on Validation
Eurostat J OINT UNECE/OECD/E UROSTAT MEETING OF THE GROUP OF EXPERTS ON BUSINESS REGISTERS 3-4 September 2013, Geneva Session 1: Economic globalisation.
ESS.VIP programme architecture
Enterprise Architecture
Charting a course PROCESS.
Developing Enterprise Architecture
Standardisation in the European Statistical System Barteld Braaksma, Cecilia Colasanti, Piero Demetrio Falorsi, Wim Kloek, Miguel Angel Martínez Vidal,
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
The Challenge of IT-Business Alignment
Implementation of the Essential Standards The Australian Quality Framework (AQTF) is the national set of standards which assures nationally consistent,
Sponsorship on Standardisation Main results Barteld Braaksma, Cecilia Colasanti, Piero Demetrio Falorsi, Wim Kloek, Miguel Angel Martínez Vidal, Jean-Marc.
© M S GIS & Mapping Implementing GIS © M S GIS & Mapping Training and Information A Successful Project A Case Study - The Geo Pres Project To Finish a.
Eurostat DIME & ITDG Steering Group December 2013 ITEM 2 WORKING GROUP STRUCTURE/COLLABORATION DIME-ITDG.
Core Banking Transformation: A Roadmap to a Successful Core Banking Product Implementation - PMI Virtual Library | | © 2008 Kannan S. Ramakrishnan.
ESTAT 2012 ESSnet Workshop Session 2 Shared services Christine WIRTZ Eurostat Head of Unit "IT for statistical production" Rome, 3 December 2012.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
The future of Statistical Production CSPA. 50 task team members 7 task teams CSPA 2015 project.
Changing the way the New Zealand Aid Programme monitors and evaluates its Aid Ingrid van Aalst Principal Evaluation Manager Development Strategy & Effectiveness.
Eurostat ESS.VIP.SERV – sharing statistical services in the ESS Gergely Koevesd, Eurostat (B3) DIME/ITDG Steering committee 18 November
Eurostat Report on SDMX Reference Infrastructure User Group 1 st meeting in Luxembourg Sept 2012 Item 5.2 of the agenda November 2012IT Director's.
Eurostat Standardisation DIME-ITDG 2015 Item 6 DIME-ITDG February
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Agency Briefing - Overview
ESS Enterprise Architecture Reference Framework Jean-Marc Museux, Eurostat 2016 UNECE CSPA Workshop on CSPA Geneva
Accountability & Structured Privacy Management
Rapid Launch Workshop ©CC BY-SA.
UNECE-CES Work session on Statistical Data Editing
Data Architecture World Class Operations - Impact Workshop.
The ESS vision, ESSnets and SDMX
WP1 – Smart City Energy Assessment and User Requirements
The Open Group Architecture Framework (TOGAF)
Project Roles and Responsibilities
MGT 498 TUTORIAL Lessons in Excellence -- mgt498tutorial.com.
Implementing the ESS Vision 2020
Guidance on Natura 2000 and Forests – Scoping Document
ITDG 2012 Summary conclusions
"IT principles" Context, roadmap
ESTP TRAINING ON EGR Luxembourg – December 2014
Methodology and Corporate Architecture
ESS roadmap on Linked Open Data State of play
Alignment of COBIT to Botswana IT Audit Methodology
Towards an ESS architecture ITDG Item 3.4
IT Director's Group Meeting
22 February, ITDG/DIME Item 2 – Progress and deployment
Metadata in the modernization of statistical production at Statistics Canada Carmen Greenough June 2, 2014.
2nd SISAI meeting, June 2012 Policy for Setting up an Appropriate Environment for Storage, Distribution and Archiving of Statistical Software of.
ESS Vision 2020: ESS.VIP Validation
SISAI STATISTICAL INFORMATION SYSTEMS ARCHITECTURE AND INTEGRATION
Data Management Capability Assessment Model
Opinions after the 24/25 February 2016 Plenary
ESS Standardisation State of play
ESS.VIP VALIDATION An ESS.VIP project for mutual benefits
Giuliano Amerini Unit E6 (Transport)
Draft Methodology for impact analysis of ESS.VIP Projects
ITDG meeting of of October 2011
3rd WGM Meeting 3 May 2018 Item 2.3 Possible standards for ESS Validation.
The SDGs in Flanders November 27, 2018.
Portfolio, Programme and Project
ESS Standardisation DIME / ITDG steering group – Item for information
Shared Tools Expert Group
Partner Implications from Seminar: New Approaches to Capacity Development Break-out Group: Role of Assessment frameworks.
ESS.VIP Validation Item 5.1
CORE outcomes and follow up
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Implementing the “Vision” within the ESS
ESS.VIP.SERV Shared Services
ESSNet SERV 2 Implementing Shared SERVices
ESS Enterprise Architecture
Implementing the “Vision” within ESS
Presentation transcript:

SISAI STATISTICAL INFORMATION SYSTEMS ARCHITECTURE AND INTEGRATION WORKING GROUP 3rdMEETING 13-14 MAY 2013 ITEM 2.1.1 IT principles

"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