Architecture Models to Support Accessible eGovernment Services for All

1. Architecture Models to Support Accessible eGovernment Services for All Karl Wessbrandt, the Swedish Administrative Development Agency 19 April 2007

2. Locallevel • Elections to the Municipal Council • The Municipal Council elects the Municipal Executive Board • Regional level • Elections to the County Council • Assembly • The County Council Assembly elects the County Council Executive Board • National level • Elections to the Riksdag (Swedish parliament) • The Riksdag elects the Prime Minister, who forms a government 21 Countys 290 Municipalities The democratic system in Sweden

3. Directing the Operations of Government Agencies Appropriation directions, allocation of appropriations and assignments Appointments to senior posts and organisational form Laws and ordinances Performance Management §

4. eGovernment targeted areas • Service Quality • Efficiency • Working Conditions • Impact on Society • Transparency

5. Cabinet Industry Representatives Verva - The AdministrativeDevelopment Agency Representatives Regulations Guidelines Representatives Municipalities & Counties Government Agencies

6. Verva – instruments • Prepare and issue guidelines and ordinances to national agencies • ICT-procurement for public sector • To promote common development and activities • To promote joint action within the public sector and with the private sector

7. A Public Administration that is Connected and Coherent Inter Office Organi- sation eID & Dynamic Chan- nels Back Office Front Office Service eID Personal eID

8. Joined-up eGov Services: Coherent Case Processing standardized messages Agency A Service Oriented Support Stove-pipe systems Information Content XML Schema, Metadata, Controlled terminology Web catalog Agency B XML-converter Internet Secure eLink Transport Information Management Platform Infra Services

9. € € € € € € € € € € € e-Identification modelTop Down?

10. ? € € € € € € € € € € € e-Identification modelBottom Up? Internet Banking: Some 3 million accountholders (out of a population of close to 9 million) ”Soft eID’s” Download over the net No Cards – now…

11. CA • Contract. • ”Token” or other method to handle keys. • Safe identification method. • Client hardware and software. • Help Desk and Revocation. Issuer • Secure Channel • Revocation information • Helpdesk and Service.: User e-Id Service Model Relying Party

12. Period Payment CA • The User pays • For Certificate. • For Usage. • etc Issuer Transaction Payment • Relying Party pays: • For Active User. • For Usage • etc € € € User e-Id Cost Model Relying Party

13. What´s in the message envelope?Good practice schema structure, designed for re-use

14. Semantic interoperability: Example from a modeling workshop about the concept ”person”

15. Example: Termbank of the National Health & Welfare Board http://app.socialstyrelsen.se/termbank/

16. Critical issues & success factors for eGovernment development Interoperability layers and supporting services Models and Guidelines IT Framework Agreements

17. Interoperability Layers Legal interoperability Organisational interoperability Semantic interoperability Technical interoperability Based on IDABC EIF

18. Framework of Architectures Interoperability Architecture Enterprise architecture Statskontoret

19. Architecture Framework for eGovernment User demands and neeeds Common Front End Functions Common Resources and Structures Enterprise systems Enterprise systems Enterprise systems eGovernment Specifications Statskontoret 2004 Guidelines Regulations Procurements Verva as a platform for collaboration Specifications Standards Methods Processes Interfaces

20. Approach according to the OASIS SOA Reference Model • Framework – stating basic principles, independent of specific standards or technologies • Reference Architectures – with more detailed guidelines, from different viewpoints and for different sectors, including references to standards or common specifications • Concrete Architectures, describing the details needed to implement specific solutions 1 and 2 are central issues, 2 and 3 are handled by the sectors, by the user organisations and by the vendors and consultants concerned

21. Map and Publish Electronic Information Exchange per Public Authority Municipality Y Region Z Municipality X • Provide info about • Data Base Name • Purpose • Legal basis • Secrecy level (if any) • Access fees (if any) • Information security • Information Interface • Communication Interface • etc. Authority F Authority A Agency B Board C Agency E Authority D Open Catalog Service Public Internet Access

22. A coherent process from idea to working solution to build a collaborative eGovernment system practice Working, collaborative implementations implementation Guidelines Procurements Ordinances eGovernment Function Specifications development Processes Interfaces Specifications Methods Standards eGovernment Reference Architectures idea eGovernment Architecture Framework General Market Function Specifications Formal standards De facto Standards Specifications Methods Processes Interfaces

23. Karl Wessbrandt, the Swedish Administrative Development Agency karl.wessbrandt@verva.se