Service Oriented Architecture Workshop
Service Oriented Architecture pushed to the limit in eGovernment
Koert Declercq
Brussels, February 17th, 2010
SOA reference framework for public services
v2
© 2010 Deloitte Belgium
Content
2 Service Oriented Architecture pushed to the limit in eGovernment
• Two Findings
• Two case studies
• Preliminary conclusion
© 2010 Deloitte Belgium
Ma
turi
tyMaturity and adoption of SOA architectureFocus on business services is pivotal at level three
Service Oriented Architecture pushed to the limit in eGovernment3
Web services Standards and some Components
Limited SOA run-Time
Use of XML
Time
Some services developed, with limited exposure
SOA development and run-time environment
Web services
XML messaging
Business Services are defined
Services are being orchestrated
Business Process Modeling is in use
Broad use of SOA infrastructure
Broad use of XML
SOA governance in place
Business Process Models defined and managed
Business activity monitoring
Business process simulation
Multiple BU/business services domains are defined
Service reuse is occurring
Extensive SOA environment
Public services being leveraged and choreographed
Extensive services library
Extensive services reuse
Web 2.0 with collaboration and mash-Ups
Multiple services partners
Stage 1: Basic SOAStage 1: Basic SOA
Stage 2: Limited SOAServices
Stage 2: Limited SOAServices
Stage 3: OrchestratingSOA Services
Stage 3: OrchestratingSOA Services
Stage 4: Performance Mgmt + SOA
Stage 4: Performance Mgmt + SOA
Stage 5: Public SOAStage 5: Public SOA
© 2010 Deloitte Belgium
Requirements for business Services
Government services add specific requirements to services in a Service Oriented Architecture
4 Service Oriented Architecture pushed to the limit in eGovernment
Discoverable
Service Maintenance
Interface Granularity
Division of responsibility
Loose technology coupling
Self-Contained
Modularity
Interoperability
Reusability
Efficiency
Citizen-oriented
Ease public administration interoperability
Respect the autonomy of the single administration
© 2010 Deloitte Belgium
Case study 1: City of Rotterdam
5 Service Oriented Architecture pushed to the limit in eGovernment
New law (Wabo 2009) which forces the councils to deliver environmental permission is an integrated way with the objective to:
•Less administrative work for businesses and citizens.
•Better service by the government
•Shorter procedures
•No contra dictionary regulation.
© 2010 Deloitte Belgium
Case study 1: City of Rotterdam Citizen-oriented services are the core of the Service Oriented Architecture
6 Service Oriented Architecture pushed to the limit in eGovernment
Process Manager
Request Management
Calendaring service
Business Registry Geographical data
Actors
Data sources
Business Services
Channels
City Councils Environment Administration
Building Administration ...
Mid Office:
Back office:
Front office: email – Phone - Internet
Citizens Administrations Businesses
© 2010 Deloitte Belgium
Case Study 2: Belgian e-Health platform (www.ehealth.fgov.be)
7 Service Oriented Architecture pushed to the limit in eGovernment
End‐to‐end Encryption
Identity and access management
Index of Medical Professions
Time Stamping
Coding and Anonimisation
Logging Services
Authorized medical
beneficiariesCitizen registry
Data access services
Social security registry
Company registry
Manage Registration and vaccination of eH1N1
Cancer Registry
E-Birth (in development) …
Data sources
Services
Actors
*www.ehealth.fgov.be
Channel(Value added
services)
Basic interoperability service and respect for the autonomy of the single administration
Portal
Health care actors- Administrations
© 2010 Deloitte Belgium
SOA Reference ModelBuilding a specific governance architecture
8
End‐to‐end Encryption
Process Manager
Logging services
Authenticationservices
e-Procurement
Log auditing
Collaboration Orchestration e-Payment
e-Voting
Document Management
Process Traceability
e-Citizen Counter
Personal document
storage
e-Forms e-Tax
Service Oriented Architecture pushed to the limit in eGovernment
Coding & anonimisation