[wso2con eu 2017] implementing data exchange infrastructure in government
TRANSCRIPT
Implementing Data Exchange Infrastructure in Government
Artur ReaboiEnterprise Architecte-Government Center of Moldova
About e-Government Center
• CIO of the Government of Moldova• Operational from 2011• Reports to Prime Minister• Responsible for e-Government strategy• Implementing e-Government as a Platform• Follow us on http://egov.md
The problem (1 of 2)Too many public services are asking for too many documents issued by different governmental organizations.
The problem (2 of 2)Internal government processes tend to take longer because there is lack of real-time information.
Governmental data exchange needs
• Automated decisions based on authoritative data– Not a document exchange!– Abstracted/virtualized data sources
• Access to real-time data– Data synchronization only for analysis in one cluster
• Life events distribution instead of synchronization– Enabling a pro-active government
Governmental data exchange needs
• Enable a clear process for new connections and their change management
• Ensure secure connections• Control access to restricted data (personal,
commercial secret, etc.)• Abstract technical differences• Enable technical advances
Interoperability common obstacles• Agreeing on a responsible body for
implementation• Defining data exchanges before reengineering
involved business processes• Seeking for acceptance from authoritative data
sources to expose data• Ensuring proper SLA (especially HA)• Ensuring sustainability of data sources
Ways of connecting systems
• Direct, ad-hoc, without any governance• Just recommending some common standards
and hoping for the best• Using a distributed but uniform solution based
on local adaptation servers• Using a centralized hub and responsible
organization
Deployment• NGINX Plus cluster (active/passive)• WSO2 ESB cluster: 1 manager and 2 workers• WSO2 ESB Analytics cluster (2 servers)• Microsoft SQL Server cluster for persistence• SVN cluster for deployment sync• MLog (Elasticsearch) used for selective logging• MPass used as SSO to management consoles• MAccess used as UI for some data access
Results
• Around 30 public authorities involved• More than 65 web-services in production• Estimating around 25 M messages in 2017• Scalable throughput: 400 signed msg/sec/node
over https and with logging• Added latency: up to 100 ms
Lessons learned
• Interoperability is a journey• Implementation is faster when centralized• Implement generic services with data providers and
publish life events from source• Establish a sustainable team of integration specialists• Ensure a long-term relationship with solution vendor
Future plans• Clarify and simplify the connection process
– Promote Interoperability Law– Implement interactive Semantic Catalog, including:
• Semantic assets management• Electronic requests for new data exchanges• Defined data categories and SLAs
• Lean more on event-based data exchange scenarios• Modernize public services using data exchange
Public services modernization
20
RATIONALIZATION REENGINEERING DIGITIZATION DELIVERY
Eliminate obsolete services
Consolidate related services
Identify life scenarios and business events
Review and simplify general legal framework
Business process automation
Mechanisms to apply and deliver services online
Mechanisms to check application status
Inter-agency data exchange
Multiple delivery channels
Deliver central services locally
Customer-centered delivery
Quality and delivery standards
Continuous improvement
Administrative streamlining
Business process optimization
Eliminate un-necessary documents
Review and simplify specific legal framework
COORDINATION AND PROGRAM/PROJECT MANAGEMENT
MONITORING AND CONTROL
COMMUNICATION, TRAINING AND MARKETING