1. MSIS2013 By Jonathan Challener UPDATE ON THE ACTIVITIES OF THE OECD"S STATISTICAL INFORMATION SYSTEM COLLABORATION COMMUNITY

2. Who we are? OECD AUSTRALIAN BUREAU OF STATISTICS EUROPEAN COMMISSION INTERNATIONAL MONETARY FUND ITALIAN NATIONAL INSTITUTE OF STATISTICS STATISTICS ESTONIA STATISTICS NEW ZEALAND UNESCO INSTITUTE FOR STATISTICS UNIVERSITY OF MANCHESTER

3. Interested? INSEE National Bank of Belgium "Rich in functionalities and easy to use" "Built for ENDUSERS" "Very good process automation options" "Modern user interface and functionality" "Good perspective" "Develop our own tool will take a long time and a lot of resources" "Other similar available tools seem to no longer be improved or have blocking limitations" "To be part of a collaboration community"

4. Why collaborate?

5. Co-producing and co-developing state-of-the-art Statistical Information Systems by leveraging on community capacities. Sharing of experiences, knowledge and best practices through multilateral collaboration and building of a collective capacity. Enabling innovation at an optimal cost in a minimal time with all members benefiting from each other in terms of ideas and methods. Provide a platform for Open Data projects as identified as a priority for major member countries. Implementing standards (SDMX) for data sharing across organisations in order to improve data accessibility and quality, and reduce costs.

6. Why collaborate?

7. On what?.Stat is the central repository ("warehouse") where validated statistics and related metadata are stored. It provides the sole and coherent source of statistical data and related metadata for an organisation"s statistical data sharing, publication and electronic dissemination processes.

8. .Stat positioning in SIS

9. .Stat architecture Flexible multi- dimensional datasets Structured for human consumption Flexible access rights Referential metadata, flags, 2 languages Hierarchical and common dimensions SQL Server db with star schema,.Net Web services, web and other client applications Autonomous data owners Loosely coupled, platform independent Priority to extractions

10. .Stat key components Theme navigation & search Flexible data tables, selection and view options Interactive graphs Default and personal queries Excel, CSV, PC-Axis exports Web browser V2.0 and partly 2.1 SOAP + REST DSD, MSD, Generic Data, Compact Data, generic Metadata Authentication, Streaming SDMX Synchronised transactional 24/7 data loads XML + CSV E-mail notification Optional user-friendly GUI Entry gate, DPI.Stat Populator DotStatGet tool suite Direct SQL access Internal access

11. How?

12. Community enablers Governance, process and funding Members and culture Tools and technology

13. Strategic 5 year directions Community framework 100% community consensus updated yearly; renewed every 5y MOU Bilateral agreement between "x" and OECD Intellectual property 100% OECD but made available for use by community Governance model 100% OECD with community validation Community yearly workplan 100% community consensus OECD yearly workplan 100% OECD shared with community

14. Community activities Strategic levelManagement level Operational/Technical level Installation and support Integration of other tools Prepare SoW for GP Acceptance of GP deliverables Prepare MOU Prepare Grant request Sign off SoW for GP On-demand meetings Sign off MOU Sign off Grant Sign off governance model Sign off the 5 year strategic roadmap and its yearly update Sign off yearly workplan Monitor ongoing progress (Quarterly reviews…) Prepare Governance model, Strategic roadmap Progress reporting Prepare yearly workplan Coordinate the different development streams Bilateral activities plan Community activities

15. Supporting activities Application Lifecycle management Source code management in TFS, quality assurance, SCRUM Technical support network Install package, collaboration portal (documentation, discussions), capacity building Management meetings Quarterly management meetings, frequent developer meetings Annual workshops Collaboration partners, Interested and industry experts, interactive sessions Global development partner Support, maintenance and development

16. Funding model OECD Workplan SIS-CC coordination & support OECD Contribution Standard financial contribution by SIS-CC members SIS-CC Community Workplan Ad-hoc financial or in- kind contribution by SIS-CC members

17. Contributing to product roadmap Option 0: SIS-CC Member contributes in-kind through onsite or remote developments Option 1: SIS-CC members contributes in-kind through direct contract with OECD Global Partner Option 2: SIS-CC Member contributes financially through OECD funding

18. ACHIEVEMENTS TO DATE

19. ….. more to follow soon: -UIS.Stat, -EC.Stat, -ES.Stat (Estonia) -…...Stat World Wide platform

20. Security enhancements 3-tier architecture and 2 new web services SDMX-RI prototype integration New interface design New data structure Support of Time Series IDs Support Non-calendar year based reporting Unit and Powercode management Management of sparse datasets Improved installation package Search API to connect to 3 rd party engine Open data web services.Stat enrichment

21. As part of the 2012 workshop a process was initiated to define a JSON format based on SDMX by the SDMX-TWG – This year we launched the very first "BETA" API using an early implementation of SDMX-JSON http://oe.cd/OpenDataAPI/ Community leveraging

22. The results speak for themselves

23. Open Data API initiative for developers INEGI http://www3.inegi.org.mx/rnm/sdmx OECD https://c9.io/h4mu/sdmx-json- apps/workspace/memory/memory.html UIS http://www.uis.unesco.org/das/Country/OdataTest DRASTIC DATA http://www.drasticdata.nl/ProjectOECD/

24. Directions for the.Stat roadmap

25. NON REUSABLE REUSABLE

26. sdmx-json odata SVG Search

28. The same language said differently

33. FRAMEWORK EVOLUTIONS

34. Put in place 5 year strategic directions: – roadmap, community vision, architecture, business vision, and industrialisation Create an architecture group to drive technical and business architecture Introduce a Bi-annual workplan, reviewed annually Explore future directions for plug and play architecture and international positioning Framework evolutions

35. Further information Questions? Email: jonathan.challener@oecd.org or dotstatcollaborationsupport@oecd.org