who we are? on the activities... · •v2.0 and partly 2.1 •optional user‐friendly gui entry...
TRANSCRIPT
1
UPDATE ON THE ACTIVITIES OF THE OECD"S
STATISTICAL INFORMATION SYSTEM
COLLABORATION COMMUNITY
MSIS2013By Jonathan Challener
Who we are?
OECD
AUSTRALIAN BUREAU OF STATISTICS STATISTICS ESTONIA
EUROPEAN COMMISSION
INTERNATIONAL MONETARY FUND
ITALIAN NATIONAL INSTITUTE OF STATISTICS
STATISTICS NEW ZEALAND
UNESCO INSTITUTE FOR STATISTICS
UNIVERSITY OF MANCHESTER
2
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?
3
Why collaborate?
Co‐producing and co‐developing state‐of‐the‐art StatisticalInformation Systems by leveraging on community capacities.
Sharing of experiences, knowledge and best practices throughmultilateral 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?
4
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
5
.Stat architecture
Flexible multi‐dimensional datasets
S d f h
SQL Server db with star schema, .Net
Web services web Structured for human consumption
Flexible access rights
Web services, web and other client applications
Autonomous data owners
Referential metadata, flags, 2 languages
Hierarchical and common dimensions
Loosely coupled, platform independent
Priority to extractions
.Stat key components• Theme navigation & search
• Flexible data tables, selection and view options
• Interactive graphs
• Default and personal queries
• Synchronised transactional 24/7 data loads
• XML + CSV
• E‐mail notification • Default and personal queries
• Excel, CSV, PC‐Axis exports
Web browser
• V2.0 and partly 2.1
E mail notification
• Optional user‐friendly GUI
Entry gate, DPI
• .Stat Populator• SOAP + REST
• DSD, MSD, Generic Data, Compact Data, generic Metadata
• Authentication, Streaming
SDMX
p
• DotStatGet tool suite
• Direct SQL access
Internal access
6
How?
Community enablers
Governance,Governance,Governance, process and funding
Governance, process and funding
Members and cultureMembers and culture
Tools and technologyTools and technology
7
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 m
odel 100% OECD
with community validation
munity yearly
plan
100% community
consensus
OECD yearly workplan 100% OECD
shared with community
Comm
workp O
Community activities
Si ff d lSi ff d l
Bilateral activities plan Community activities
Strategic levelStrategic level
Management levelManagement level
Prepare MOU
Prepare Grant request
Sign off SoW for GP
Prepare MOU
Prepare Grant request
Sign off SoW for GP
Sign off MOU
Sign off Grant
Sign off MOU
Sign off Grant
Sign off governance model
Sign off the 5 year strategic roadmap and its yearly
update
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
Sign off yearly workplan
Monitor ongoing progress (Quarterly reviews…)
Prepare Governance
Operational/Technical level
Operational/Technical level
Installation and supportIntegration of other tools
Prepare SoW for GP
Acceptance of GP deliverables
Installation and supportIntegration of other tools
Prepare SoW for GP
Acceptance of GP deliverables
On‐demand meetingsOn‐demand meetingsPrepare Governance
model, Strategic roadmapPrepare Governance
model, Strategic roadmap
Progress reporting
Prepare yearly workplan
Coordinate the different development streams
Progress reporting
Prepare yearly workplan
Coordinate the different development streams
8
Supporting activities
Application Lifecycle managementSource code management in TFS, quality assurance, SCRUM
Technical support networkInstall package, collaboration portal (documentation, discussions), capacity building
Management meetingsQuarterly management meetings, frequent developer meetings
Annual workshopsCollaboration partners, Interested and industry experts, interactive sessions
Global development partnerSupport, maintenance and development
Funding model
OECD Standard financialib i b
Ad‐hoc financial or in‐ki d ib i b
OECD
SIS‐CC
coordination
Contributioncontribution by SIS‐CC members
SIS‐CC
Community
W k l
kind contribution by SIS‐CC members
OECD
Workplan
& support Workplan
9
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
10
.Stat World Wide platform
….. more to follow soon:‐ UIS.Stat,
‐ EC.Stat,
‐ ES.Stat (Estonia)
‐ …..
• Security enhancements
• 3‐tier architecture and 2 new web services
.Stat enrichment
• 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
U it d P d t• Unit and Powercode management
• Management of sparse datasets
• Improved installation package
• Search API to connect to 3rd party engine
• Open data web services
11
• As part of the 2012 workshop a process was initiated to define a JSON format based on
Community leveraging
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 // d/O D t API/http://oe.cd/OpenDataAPI/
The results speak for themselves
12
Open Data API initiative for developers
INEGIhttp://www3 inegi org mx/rnm/sdmxhttp://www3.inegi.org.mx/rnm/sdmx
OECDhttps://c9.io/h4mu/sdmx‐json‐apps/workspace/memory/memory.html
UIShttp://www.uis.unesco.org/das/Country/OdataTest
DRASTIC DATAhttp://www.drasticdata.nl/ProjectOECD/
Directions Directions for the for the .Stat .Stat roadmaproadmap
13
NON
REUSABLE
NON REUSABLE
sdmx-json
odataSVGSearch
14
The same language said differentlyg g y
15
16
17
FRAMEWORK EVOLUTIONS
• Put in place 5 year strategic directions:
Framework evolutions
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