UPDATE ON THE ACTIVITIES OF THE OECD"S STATISTICAL INFORMATION SYSTEM COLLABORATION COMMUNITY MSIS2013 By Jonathan Challener Who we are? OECD STATISTICS ESTONIA AUSTRALIAN BUREAU OF STATISTICS STATISTICS NEW ZEALAND EUROPEAN COMMISSION UNESCO INSTITUTE FOR STATISTICS INTERNATIONAL MONETARY FUND UNIVERSITY OF MANCHESTER ITALIAN NATIONAL INSTITUTE OF STATISTICS 1
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" Why collaborate? 2
Why collaborate? 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. Why collaborate? 3
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. .Stat positioning in SIS 4
.Stat architecture SQL Server db with Flexible multi ‐ star schema, .Net dimensional datasets Web services web Web services, web S Structured for human d f h and other client consumption applications Flexible access rights Autonomous data owners Referential metadata, Loosely coupled, flags, 2 languages platform independent Hierarchical and Priority to extractions common dimensions .Stat key components • Theme navigation & search • Synchronised transactional 24/7 • Flexible data tables, selection and data loads view options • XML + CSV • Interactive graphs • E ‐ mail notification E mail notification • Default and personal queries • Default and personal queries • Optional user ‐ friendly GUI • Excel, CSV, PC ‐ Axis exports Entry gate, DPI Web browser • V2.0 and partly 2.1 • .Stat Populator p • SOAP + REST • DotStatGet tool suite • DSD, MSD, Generic Data, Compact • Direct SQL access Data, generic Metadata • Authentication, Streaming Internal access SDMX 5
How? Community enablers Governance, Governance, Governance, Governance, process and process and funding funding Tools and Tools and Members Members technology technology and culture and culture 6
Community framework Strategic 5 year directions 100% community consensus updated yearly; renewed every 5y MOU Intellectual property Governance model OECD yearly workplan Bilateral 100% OECD 100% OECD 100% 100% OECD agreement but made with community shared with between available community community munity yearly consensus "x" and for use by validation OECD community plan O Comm workp Community activities Community activities Bilateral activities plan Sign off governance model Sign off governance model Si Si ff ff d l d l Sign off MOU Sign off MOU Sign off the 5 year strategic Sign off the 5 year strategic Strategic level Strategic level Sign off Grant Sign off Grant roadmap and its yearly roadmap and its yearly update update Sign off yearly workplan Sign off yearly workplan Prepare MOU Prepare MOU Monitor ongoing progress Monitor ongoing progress Prepare Grant request Prepare Grant request Management level Management level (Quarterly reviews…) (Quarterly reviews…) Sign off SoW for GP Sign off SoW for GP Prepare Governance Prepare Governance Prepare Governance Prepare Governance On ‐ demand meetings On ‐ demand meetings model, Strategic roadmap model, Strategic roadmap Installation and support Installation and support Progress reporting Progress reporting Integration of other tools Integration of other tools Operational/Technical Operational/Technical Prepare yearly workplan Prepare yearly workplan Prepare SoW for GP Prepare SoW for GP level level Coordinate the different Coordinate the different Acceptance of GP Acceptance of GP development streams development streams deliverables deliverables 7
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 Funding model Standard financial Ad ‐ hoc financial or in ‐ OECD contribution by ib i b ki d kind contribution by ib i b Contribution SIS ‐ CC members SIS ‐ CC members SIS ‐ CC SIS ‐ CC Community coordination OECD OECD Workplan W k l & support Workplan 8
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 ACHIEVEMENTS TO DATE 9
.Stat World Wide platform ….. more to follow soon: ‐ UIS.Stat, ‐ EC.Stat, ‐ ES.Stat (Estonia) ‐ ….. .Stat enrichment • Security enhancements • 3 ‐ tier architecture and 2 new web services • 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 U it d P d t • Management of sparse datasets • Improved installation package • Search API to connect to 3 rd party engine • Open data web services 10
Community leveraging • As part of the 2012 workshop a process was initiated to define a JSON format based on 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 htt http:/ / oe.cd/ OpenDataAPI/ / / d/ O D t API/ The results speak for themselves 11
Open Data API initiative for developers INEGI http://www3 inegi org mx/rnm/sdmx 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/ Directions Directions for the for the .Stat roadmap .Stat roadmap 12
REUSABLE NON NON REUSABLE s dm s dm x - j s on x - j s on SVG SVG odat a odat a Sear c h Sear c h 13
The same language said differently g g y 14
15
16
FRAMEWORK EVOLUTIONS Framework evolutions • Put in place 5 year strategic directions: p y g – roadmap, community vision, architecture, business vision, and industrialisation • Create an architecture group to drive technical and business architecture • Introduce a Bi-annual workplan, reviewed p , annually • Explore future directions for plug and play architecture and international positioning 17
Further information Questions? Email: jonathan.challener@oecd.org or or dotstatcollaborationsupport@oecd.org 18
Recommend
More recommend