Sharing eGovernment experience

1. Smals CBSS Sharing eGovernment experience Frank Robben General manager Crossroads Bank for Social Security General manager Smals Sint-Pieterssteenweg 375 B-1040 Brussels E-mail: Frank.Robben@ksz.fgov.be Website CBSS: www.ksz.fgov.be Personal website: www.law.kuleuven.ac.be/icri/frobben

2. Types of use of shared experiences • instrumental use • immediate valorization • answer to a concrete question • conceptual use • valorization in the long run • support to development of policy or strategy • legitimating use • legitimation of a proper position or proposal

3. Possible benefits of sharing experience • learning • benchmarking • cooperation platforms • stimulation of interoperability and standards • sufficient common vision on some basic principles of eGovernment • re-use of basic services • natural way to cooperative governance • recognition in the own country

4. Learning • expectations of stakeholders • citizens • companies • political decision makers • critical success factors • political • organizational • process reengineering • architectural • technical • legal • security and privacy protection • change management • solution methods

5. Benchmarking • stimulation of development of metrics related to the own institution/sector/country • cost and efficiency • quality • customer orientation • effectiveness • innovation • comparison with metrics related to the best practices in the own country or other countries • as a basis for • giving comparative account about the own performance • knowledge of strengths, weaknesses, opportunities and threats (SWOT-analysis) • permanent and structural improvements • evaluation of management and collaborators

6. Cooperation platforms • eGovernment is about integration • integrated service delivery to citizens and companies • integrated policy support • thus, need for cooperation between • government institutions • government institutions, companies and citizens • government levels • countries • multifunctional (see critical success factors) • based on • shared objectives • coordination and division of tasks, rather than centralisation • trust and transparency

7. Stimulation of interoperability and standards • interoperability • technical • syntactical • semantic • functional – processes – services • legal • organizational • based on • components • open specifications • open standards

8. Sufficient common vision • objectives • strategic • operational • basic principles • information management • information modelling • unique collection and re-use of information • validation of information (information quality) • management of information • sharing of information • protection of information • process re-engineering • participation of stakeholders • method of open co-ordination in order to meet the objectives

9. Re-use of basic services • reason • cost control • concentration on core business • faster time to market • higher possibility to adaptation • examples • network • user and access management • transformation • routing • process orchestration • state machines

10. Presentation Applications Business services Basic services Data Layered, service oriented architecture

11. Example: user and access management • identification of physical and legal persons • authentication of the identity of physical persons • management and verification of characteristics (e.g. a capacity, a function, a professional qualification) of persons • management and verification of mandates between a legal or physical person to whom an electronic transaction relates and the person carrying out that transaction • management and verification of authorizations

12. Action on Action application on Policy DENIED application User Enforcement Application PERMITTED ( PEP ) Action on application Decision Decision request reply Information request/ Policy Decision Policy reply retrieval (PDP) Information request/ reply Policy Policy Administration Policy Information Policy Information management ( PAP ) ( PIP ) ( PIP ) Manager Policy repository Authentic source Authentic source Policy Enforcement Model

13. Policy Enforcement Model • Policy Enforcement Point (PEP) • intercepts the request for authorization with all available information about the user, the action being requested, the resources and the environment • passes on the request for authorization to the Policy Decision Point (PDP) and extracts a decision regarding authorization • grants access to the application and provides relevant credentials • Policy Decision Point (PDP) • based on the request for authorization received, retrieves the appropriate authorization policy from the Policy Administration Point(s) (PAP) • evaluates the policy and, if necessary, retrieves the relevant information from the Policy Information Point(s) (PIP) • takes the authorization decision (permit/deny/not applicable) and sends it to the PEP

14. Policy Enforcement Model • Policy Administration Point (PAP) • environment to store and manage authorization policies by authorised person(s) appointed by the application managers • puts authorization policies at the disposal of the PDP • Policy Information Point (PIP) • puts information at the disposal of the PDP in order to evaluate authorization policies (authentic sources with characteristics, mandates, etc.)

15. Natural way to cooperative governance • governments reason in terms of (legal) competences • eGoverment needs cooperation • thus, need for cooperative governance models that permit real cooperation with respect for division of competences • method of open coordination • common services managed by governance structures composed of representatives of the stakeholders/users • platforms for sharing eGovernment experience could naturally evolve towards this kind of structure

16. Basis for support in the own country • gaining authority and trust • good results of benchmarks • recognition as an international best practice • arguing the own proposals • alignment with international common vision and best practices • elements of comparison • possible export of national vision, solution methods or even services to the international level

17. How to share eGovernment experience ? • official bodies, needed for • formal approval of common objectives, standards and specifications • formal approval of task sharing • preparation of legal framework • less formal cooperation platforms • exchange of information and experiences • mutual help • operational cooperation • instruments • meetings • training • databases of best practices • interactive collaborative tools • networks of advisors

18. Possible participants • policy makers • government workers • academics • service suppliers, if no direct commercial objective

19. Points of attention • most useful knowledge about experiences is tacit knowledge => need for extraction and coding • comparability of experiences • knowledge harmonization • guaranteeing knowledge quality • problem of distributed knowledge • finding the relevant knowledge • finding the right person who can help • usefulness of a common assessment framework for eGovernment ?

20. Common assessment framework ENABLERS RESULTS Leadership Human resources management Process and change management Staff results Key performance results Strategy and planning Customer- oriented results Partnerships and resources Society results INNOVATION AND LEARNING

21. More info • personal website • http://www.law.kuleuven.ac.be/icri/frobben • Crossroads Bank for Social Security • http://www.ksz.fgov.be • Smals • http://www.smals.be