enterprise_architecture_as_a_tool_of_digital_state_transformation_-_m._bukowski_mac

MICHAŁ BUKOWSKI, MAC 2-06-2015

Enterprise architecture as a tool of

Digital State transformation

eGovernment: key problems

• Lack of single cross-government vision of Digital State: silo-based views.

• Lack of top-level ownership and effective cross-government decision-

making.

• Failure to provide services with a real value to citizens.

• Lack of cooperation in creation and use of shared eGovernment services.

• Lack of required skills at all levels to implement the eGovernment

program.

Based on: OASIS "Avoiding the Pitfalls of eGovernment” 2010

Government Enterprise Architecture

Strategic management tool for Digital State development:

• supports the achievement of the eGovernment objectives through their

operationalization,

• refers to a hierarchical corporation of public entities,

• uses models and principles of eGovernment development,

• refers to the area of business, data, software and technical solutions.

eGovernment: strategic objectives

Strategy for Better Government (pl „Strategia Sprawne Państwo”)

Improving citizen satisfaction with the quality of public services.

Integrated eGov Programme (pl „Program Zintegrowanej Informatyzacji Państwa”)

Increasing the number of high-quality electronic public services.

Operational Programme Digital Poland (pl „Program Operacyjny Polska Cyfrowa”)

Efficient and user-friendly electronic public services.

Digital State development

Digital State as-is

Transition states Digital State

to-be

More efficient operation

Comprehensive improvement in quality of services provided by public

entities is possible due to organizational transformation.

ITERATIVE TRANSFORMATION PLAN

Development principles

model models model

Strategy (objectives)

Enterprise architecture (including principles)

Project portfolio

Source: Sobczak, A. „Zastosowanie pryncypiów architektury korporacyjnej w organizacjach publicznych”, 2008

Enterprise architecture cascade

IT Project Manager

Public entity Chief Information Officer

Minister of Digitization

Strategic architecture

Segment architecture

Solution architecture

Solution architecture

Segment architecture

Solution architecture

The benefits of Government Enterprise Architecture

• Roadmap for key public electronic services – priorities, interrelations and

phases of their development.

• Better interoperability of public electronic services – information systems

and public entities.

• Lowering the cost of creation and re-use of the public sector services.

• Facilitating the legislative work for eGovernment.

Enterprise Architecture worldwide

Country Enterprise architecture as a part of legal system

Waseda-IAC International E-Government Ranking

UN E-Government Developement Index

2012 2014 2012 2014

South Korea 2005 3 3 1 1

Australia 2009 7 9 12 2

Singapure 2007 1 2 10 3

France - 17 19 6 4

The Netherlands 2006 20 17 2 5

Japan - 8 5 18 6

USA 1996 1 1 5 7

Great Britain 2005 9 4 3 8

…

Poland - no data 42 47 42

Sources: UN E-Government Development Index, 2014; Waseda-IAC International E-Government Ranking, 2014; „Does Enterprise Architecture Give Value to e-Government in Developed Countries?” M. Ali Hanafiah, R. Goodwin, Australia, 2013; „Analiza pryncypiów arch. korp. Holandii, Stanów Zjednoczonych oraz Wielkiej Brytanii” MAC, Poland, 2014.

Architectural works • Preliminary phase: organisation,

scope and principles.

• Architecture vision.

• Architectures: business, IT systems

(software and data), technology.

• Iterative transformation plan.

• Architecture management.

TOGAF Architecture Development Model

Enterprise architecture principles

Enterprise architecture principles of public entities:

• based on the strategic objectives of eGovernment,

• used for the design, development and provision of electronic public

services,

• related to development and operation of ICT systems that support public

electronic services.

Enterprise architecture principles

Sources of principles:

• Integrated Computerization Program.

• Strategy papers and corporate architectures of ministries and central

offices.

• Enterprise architecture principles of the Netherlands, the United States

and Great Britain.

EA Principles: areas of influence

business processes data

management IT

infrastructure

public value software principles for areas

Enterprise architecture principles

• BIZ1 Service is provided using process approach

• BIZ2 Communication and education of the service's stakeholders

• BIZ3 Standardization of service management

• BIZ4 Service has its owner

• BIZ5 Service provision is based on law in force

• BIZ6 Service is designed based on the effectiveness model

• BIZ7 Human resources necessary to provide the service

Enterprise architecture principles

• DATA1 Data standardization

• DATA2 Re-use of the data processed by the service

• DATA3 Optimal use of existing data sources

• DATA4 Open standards of data exchange

• APL1 User-centered service design

• APL2 Service availability

• GEN1 Service interoperability

• GEN2 Service measurability

• GEN3 Service provides secure data processing

EA Principles: verification of usage

Analysis Design Construction Transition Operation Withdrawal

PROJECT

ELECTRONIC PUBLIC SERVICE

Milestone: investment

decision

Milestone: 1/3 project

time

Milestone: 2/3 project

time

Milestone: operation

Milestone: readiness to service

Milestone: withdrawal

decision

Application of EA Principles

• Operational Programme Digital Poland

• Regional Operational Programmes

• Catalogue of Public Entity Digital Competences

Government Enterprise Architecture vision

Government Enterprise Architecture vision

A general description of the desired state of e-government in the long term -

from the perspective of architecture.

The objective of creating a vision

Reaching the consensus of key e-government stakeholders on the future,

desired model of Digital State.

It’s necessary to monitor Digital State development in accordance with the

adopted architecture vision.

Digital State to-be (beta)

EA Vision prototype summary

1. Reduction in duplication of solutions

Mandatory use of shared services by public entities.

2. Increasing interoperability

The exchange of data between services occurs via National Enterprise

Service Bus, and (where possible) via Domain Service Buses.

3. One-stop-shop portal for citizens and administration

Access to all public services is provided by one portal.

Public entities enterprise architecture examples

EA: Ministry of Finance

• Integrated Information System Strategy of the Ministry: one of the

essential topics is Enterprise Architecture

• The Integrated Information System will have to comply to Enterprise

Architecture Principles accepted by the Cabinet Committee for

Digitization (KRMC), and will extend the set of current 3 business

principles.

• EA has also been adopted by independently for some branches of the

Ministry: Customs Service and Tax Administration.

EA: Social Insurance Institution

• Social Insurance Institution (ZUS) is an example of a public body that has

developed it’s Enterprise Architecture and makes use of this approach.

• EA allowed ZUS to implement organizational changes that are better

planned, coordinated and that fit the strategy better than before.

• Additionally it allowed to increase the quality of services as seen from the

customer’s perspective.

Thank you!

Michał Bukowski Chairman of the Board of Public Administration IT Strategy Development

Department of Informatization

Ministry of Administration and Digitization of Poland

phone +48 22 245 54 47, mobile +48 723 997 908

michal.bukowski@mac.gov.pl

MINISTRY OF ADMINISTRATION AND DIGITIZATION OF POLAND