1. Sponsorship on Standardisation Main results Barteld Braaksma, Cecilia Colasanti, Piero Demetrio Falorsi, Wim Kloek, Miguel Angel Martínez Vidal, Jean-Marc Museux and Katalin Szép Forward-looking Feedback Workshop, The Hague, 30/31 May 2013

2. 2 Contents  Standards: definition and inventory  Process of standardisation and its governance  Framework: why, what, how  Business case for standardisation: SWOT tool  Pilot: census HUB  The way forward: next steps and further work Many thanks to other contributors (especially on the inventory) 2

3. 3 ISO definition of a standard and ESS interpretation Document Means any medium with information recorded on or in it established by consensus approved by a recognised body that provide rules, guidelines or characteristics for common and repeated use for activities or their results aimed at the achievement of the optimum degree of order in a given context Consensus among ESS members According to the formal procedure of standardisation, not necessarily implemented by legal act Sentences take the form of statement, instruction, recommendation or requirement For common and repeated use by several actors in the ESS For the production of EU statistics Aimed at the achievement of the optimum degree of order in the context of the implementation of the mission of ESS 3

4. 4 Types of normative documents (ISO)  Regulation: legally binding; adopted following European legislative procedure  Standard: consensus; adopted by ESSC  Other normative document: different adoption method Which other normative documents should be further developed into a standard?

5. 5 5 Inventory of ESS normative documents (broader than standards alone) Purpose  Common “rich” list of international statistical normative documents and standards in the ESS  Base for further analysis of normative documents (quality, consistency, coverage)  Gap analysis (what we have vs. what we need) Work still in progress (Sponsorship, ESSnet) Note: existing inventories differ in scope and attributes   UNECE: Common Metadata Framework   UN: Global Inventory of Statistical Standards   Eurostat: RAMON

6. 66 Process of standardisation (proposal for life cycle management) Process of standardisation (proposal for life cycle management) Establish the need Collect initiatives Cost-benefit analysis Stakeholder analysis Detailed proposal on development, responsibilities and resources Decision on resources and approval of other parts of the proposal

7. 77 Organisational structure for ESS standardisation (proposal) Guiding principles:  Matches procedures  Clear responsibilities  Division of labour  (Re)use existing bodies

8. 8 Framework: ESS Enterprise architecture (proposal)  Abstract model for the organisation of our business  Helps to structure discussions on to-be state  Helps to define roadmap for standards development  4 homogeneous business areas can be identified  Policy- Design - Management – Implementation  18 activities can be distinguished  Data collection, dissemination, budgeting,...  Which may allow different levels of integration 8

9. 99 Why a framework? The ESS is  A complex system/organisation  With multiple lines of business: NSI, authorities, Eurostat  Which operate in multiple geographies  Under the subsidiarity principle  And with a coordination role for Eurostat

10. 1010 How much do we want in common for each area?  Split between individual MS and ESS common Policy DesignManageImplement MS ESS Common MS ESS Common MS ESS Common MS ESS Common

11. 11 How far do we want to standardise each activity?  Autonomous: no standardisation  Interoperable: parts fit together where needed  Interoperable: parts fit together where needed (e.g. transmission standards)  Replicated: standard parts used where appropriate  Replicated: standard parts used where appropriate (e.g. common tools/ processes/ methods)  Shared: everything works the same way  Shared: everything works the same way (e.g. one single business process, information shared)

12. 1212 Business case for standardisation Why standardise, and at what cost?  Efficiency gains, quality improvement  Investment and maintenance costs, loss of autonomy Quantitative assessment difficult  Not always feasible/expensive  Requires ‘guesstimates’  Subjective elements  May depend on perspective (national, domain..)

13. 1313 Standardised SWOT tool Strengths, weaknesses, opportunities, threats (proposal)  Fixed aspects for each SWOT category (4x6)  Relevance and effect score for each aspect  Scores should be collected from all stakeholders  Fingerprints: a graphical representation (toy example)  Starting point for further analysis  See differences at a glance; organise discussions ‘Current situation’‘Full integration’ S W O T

14. 1414 Pilot: Census HUB Common architecture for dissemination of European census results:  Shared infrastructure  Decentralised data storage  Automated on-demand exchange Requires a wide range of standards

15. 1515 Evaluation aiming at standardisation  How do we collaborate?  What criteria for choice of standards?  What standards can be reused (transferability)?  What helps/hinders the implementation of standards?

16. 1616 Results of evaluation The evaluation demonstrated the importance of  a clear (standardised) business case  project organisation and management  monitoring of costs and benefits  considering national differences (legal, confidentiality, security, methodologies)  common solutions

17. 17 Further work  Operational (ESSnet)  Completion of inventory  Refinement of architectural framework (principles)  Gap analysis  Gap analysis (desired vs. actual situation)  Design of standards adoption process  Elaboration of SWOT tool  Strategic (beyond the Sponsorship)  Discussion on adequate levels of standardisation  Identification of priorities for standards development 17