WSO2Con EU 2015: Implementing National Interoperability Platform
1 like629 views
The document outlines the e-Government Center of Moldova's initiative to implement a national interoperability platform aimed at providing electronic public services by 2020. It highlights existing communication, financial, and technological challenges faced by the government in data exchange, while detailing a legal framework and technical milestones achieved in deploying the platform. The initiative also emphasizes the importance of engaging both public and private sectors in data integration and service provision.
WSO2Con EU 2015: Implementing National Interoperability Platform
- 1. Implemen'ng Na'onal Interoperability Pla3orm Artur Reaboi Enterprise Architect e-‐Government Center of Moldova
- 2. About Moldova • Located between Romania and Ukraine • Area: 33.8 km2 • Popula'on: 3.5 M • Capital: Chisinau (0.7 M) • Mul'lingual country • ICT takes ~10% of GDP • Internet penetra'on – 44.81% • 99% • Mobile Penetra'on – 125%
- 3. About e-‐Government Center • CIO of the Government • Opera'onal from 2011 • Reports to Prime Minister • Responsible for Government e-‐Transforma'on Agenda • Follow us on hZp://egov.md
- 4. e-‐Transforma'on Scope and Vision By 2020 all public services will be electronic and accessible to ci'zens and business through digital means
- 5. Electronic services infrastructure ELECTRONIC SERVICE SECURITY AND IDENTITY ELECTRONIC PAYMENTS ELECTRONIC MESSAGING HOSTING DELIVERY CLIENT SUPPORT DIGITAL SIGNATURE INTEROPERABILITY
- 6. Government as a Pla3orm ELECTRONIC SERVICE SECURITY AND IDENTITY ELECTRONIC PAYMENTS ELECTRONIC MESSAGING HOSTING DELIVERY CLIENT SUPPORT DIGITAL SIGNATURE INTEROPERABILITY MPass® from 05/2012 MSign® from 05/2013 MPay® from 09/2013 MNoIfy® from 05/2012* MCloud® from 02/2013 MConnect® from 01/2015 MDelivery from mid. 2015 SSC from 01/2014*
- 7. Government data exchange problems • Problem #1 – Lack of (or insufficient) communica'on between authori'es and even between subdivisions of the same authority. • Problem #2 – Financial obstacles – some organiza'ons sell data (or access to data). • Problem #3 – Technological obstacles – incompa'bility, heterogeneous environments, lack of standards, lack of documenta'on, etc.
- 8. EIF Levels
- 9. Moving from this… SOE Registru Tax Service Customs NB of Sta's'cs Social Assurance Authority Medical Assurance Authority Min. of Jus'ce SOE Cadastre An'corrup'on Commission Prosecutors
- 10. … to this SOE Registru Tax Service Customs NB of Sta's'cs Social Assurance Authority Medical Assurance Authority Min. of Jus'ce SOE Cadastre An'corrup'on Commission Prosecutors
- 11. Legal Framework • GD nr. 656 on Approving the Interoperability Framework Program – defines the concept and delineates interoperability layers: organiza'onal, seman'c and technical – defines an ac'on plan and responsibili'es • GD nr. 404 on Pilo'ng the Interoperability Pla3orm – lists the par'cipa'ng ins'tu'ons – sets up the expected ac'ons during pilo'ng
- 12. Technical Challenges • Reduced 'me to connect to data sources • Ensuring data security and confiden'ality • Unprecedented scalability • Ensuring data integrity in a distributed environment • Ensuring enough flexibility to connect different technologies • Ensuring enough compa'bility to transform between different data models • Monitoring and complex journaling
- 14. Data virtualiza'on through media'on
- 15. N5: Presenta'on MConnect Layers N4: Monitoring and Analysis N2: Middleware N1: Data N3: Business Processing Elas'city DB1 DB2 DB3 XML CSV XLS Iden'ty Reuse DBF
- 16. Intermediate Pilo'ng Results • Deployment with automa'on (ansible) and high availability with ~ 30 nodes • 10 connected ins'tu'ons (i.e. tenants) • ~ 15 integra'on projects (i.e. ~25 web-‐services) • 700K real-‐data messages exchanged • Performance tests with only 2 ESB worker nodes showed between: – 5000 msg/sec simplest empty request/reply – 800 msg/sec 5K in size, encrypted and signed with 1024 bits length key – 200 msg/sec 5K in size, encrypted and signed with 4096 bits length key
- 17. MConnect Roadmap • Legal framework adjustments • Establish a streamlined integra'on process • Ensure consistent monitoring and SLAs • Build the Seman'c Catalogue and populate it with ini'al data structure defini'ons • Connect data sources in a generic way • Con'nue the incremental technical adop'on • Connect private sector as consumers and providers of data
- 18. Thank You website: hZp://egov.md e-‐mail: artur.reaboi@egov.md