1 / 11

Global SDMX Implementation

Global SDMX Implementation. Experience from on-going projects Daniel Suranyi, Eurostat Project Officer for SDMX implementation SDMX Expert Group, 13-14 September, Paris. Challenge: Global DSD. International Projects (Eurostat perspective). Balance of Payments, National Accounts.

deiter
Download Presentation

Global SDMX Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global SDMX Implementation Experience from on-going projects Daniel Suranyi, EurostatProject Officer for SDMX implementation SDMX Expert Group, 13-14 September, Paris

  2. Challenge: Global DSD

  3. International Projects (Eurostat perspective)

  4. Balance of Payments, National Accounts • The SDMX sponsors mandated • ECB, Eurostat, IMF ECB, Eurostat, OECD • To propose Data Structure Definitions for • BPM 6 SNA 2008 • Governance • Steering Group ↔ Coordination ↔ Technical Group

  5. 2 0 1 2 2 0 1 3 0 1 4 2 Roadmap – National Accounts Preparation Organisation, planning, data flows Development Domain concepts, draft DSDs, fine tuning Consultations SDMX & NA expert review, acceptance Implementation Pilot projects, system adaption, release Production & Maintenance

  6. General Approach • Definition of domain concepts • Grouping • cross-domain • NA & BoP • NA specific • Coding • Draft DSD • Review

  7. CL Constraints Reporting matrix into SDMX artefacts Data Flow Concept Scheme Code Lists Data Structure Definitions

  8. Comparison: Use a single "Global DSD" • "Not applicable" code in all dimensions • Constraints for sub-setting code lists • "Entry gate" problem • Push: validate selection of data flow • Pull: queries more complex • Complex validation

  9. Comparison: Using multiple derived DSDs • No direct reference to"Global DSD" • to concept scheme and code lists • Multiple files / identifiers • Push: DSD ↔ data flow • Pull: direct query • Maintenance • On DSD level instead of complex mechanisms

  10. Use case: reference multiple code lists • Currently not possible in SDMX 2.1 • to extend code lists by reference • to reference multiple code lists by concept • to use hierarchical code lists for reporting • Current solution • build domain code lists based on COG

  11. Messages • "SDMX Implementation" ≠"Global DSD" • Data flows  Concepts  Reporting matrix / code lists • Best practise: domain & SDMX experts from the start • A single global DSD per domain is not sufficient • Harmonise reporting needs as far as possible • Additional intelligence around the DSD needed • Derive DSDs, but handle with care • Some technical limitations • Common way of using existing possibilities • Foresee in next version of standard

More Related