Czech GEA Hrabe 2014

The Concept

of Czech Public Administration

Enterprise Architecture

Ing. Pavel Hrabě

• Motivation to research and summary

• Czech Public Administration EA needs - Case study

report

• Identified drivers and expected adjustments of

TOGAF structure & method

• Example of an Accelerator – Reference Model of

Application Architecture

• Proposed Czech Government EA environment and

roadmap

October 2014The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě2

Agenda

I am in computer science since 1989,

• as an analyst, solution architect, business consultant

and enterprise architect (since 2007)

The aim of my work is :

• Verify the utilization rate of EA in Czech PA organizations

• Identify reasons of still little acceptance of the EA in PA

organizations, to analyse and objectify them.

• Propose changes in TOGAF to solve identified contradictions

• Propose accelerators e.g. for the application architecture.

• Propose the structure of EA environment and EA roadmap for

Czech Public Administration.


Motivation

The status of ICT in Czech PA

The law 365/2000 Coll. on information systems of public

administration

• Strategic IT, Accreditation & Attestation, methodology, guidelines

• Registration of applications (IS o ISVS) and data elements (ISDP)

The law 111/2009 Coll. The Act on Basic Registers

• Register of Citizens, Register of Organizations, Register of Land

parcels and Addresses, Register of Rights & Liabilities

Other eGovernment achievements:

• Gov. portal, Data Boxes, Service places – Czech POINTs,

Communication infrastructure

But not architecture based governance processes at all.

• Big space for improvement of IT governance processes via

architecture


Why Czech Government needs Government Enterprise

Architecture? Because:

• Czech Government wants to transform Public

Administration and its IT

• Other Governments successfully did it already

• Biggest corporations also did it already

• EA helped most of states and corporations to be

leaders and we wish to be at least successful follower.

It is not a question „If“, just „When“, „Who“, „How“ or

„Which way“ and this is subject of our investigation.


Summary

Czech Public Administration EA

usage status and requirements

Case study report


Selected 14 agencies from four different levels of PA:• 3 central ministries

• 4 counties

• 4 big municipalities - statutory cities

• 3 small cities

Five areas of research:• If, what and why want agencies further explore, understand and

improve?

• If and what architectures are already maintained?

• GEA in context of other disciplines, legislation and structure of PA?

• Readiness and resources for GEA?

• Readiness for knowledge sharing?

Typically half a day interview with one or two managers.


Goals, scope and method of Case Study

Identified ratio of architectural artefacts in domains (from 14)

o General (meta) level

• Thesauri (business vocabulary) – 1

o Business

• Service catalogue - 0

• Process model – 4

o Performance

• System of KPI’s - full 0, partial 10 (for benchmarking initiative)

o Application

• Application inventory and landscape – full 3, partial 4

o Data

• Data architecture, e.g. Conceptual model of Enterprise – 0

o Technology – not asked


Absence of architecture in Czech PA

The need to better support of cognition, understanding

and change management (9/14).

Target domains of exploration and improvement:

• Business (12)

• Performance (9)

• Data (5) and Application (5)

• Technology (2)

Architecture before Legislation (13/14)

Federative (integrated) modelling across PA layers (11/14)

EA is an „upper“ discipline for BPM (11/14) and QM (8/14)


Czech PA agencies want to use GEA


Purpose of exploration and improvement

2

33

1

1

0 0

Central authorities

1

2

21

2

1

1

Counties

10

11

11

6

6

4

1

All together

Cost reductionPerformance managementService quality & satisfactioneGovernment implement.Infrastructure developmentInteroperability implement.Other: to find balance

4

43

2

2

2

0

Statutory cities

3

2

3

2

11

0

Small cities

Whole report in Czech at ČSSI

https://www.google.cz/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCAQFjAA&url=http://www.cssi.cz/cssi/system/files/all/SI_2014_1-2_5_Hrabe.pdf&ei=Jd4hVPi1IauBywPAsYLABA&usg=AFQjCNHCNbJ_9Y_Rx-fYEJVz0QPqTJ9gMw&sig2=GoJmffs5t3xYZDeU-sR1bA&bvm=bv.75775273,d.bGQ&cad=rjt

• Interest to build architecture based on Best Practice and share own results

in Czech GEA community network (12/14).

• Expected (8/14) leading role of Ministry of Interior, not fulfilled in past.

• „Portal of Servants“, internal portal of PA ČR, named as best access point

to the Czech GEA BoK.

• Behind the portal should be operated central modelling environment &

repository, complemented with social network functions.

• Public authorities want to get knowledge mostly about (from 14):

• Federative architecture content, across layers and domains (11)

• Examples and experience (11)

• Business Cases, projects (9)

• Peer-reviewed scientific articles (7)

• Others (including foreign examples) (3)


Willingness to be governed and to share

• Full localization to Czech language and context

• User friendliness, uniform graphical visualization,

navigation

• Simplicity, clarity, brevity, intelligibility, common sense

• Practical managerial outputs, real examples, directly

applicable patterns and guidelines

• Leadership of authority, timeliness of reference content,

environment (IT system) for knowledge sharing – GEA

BoK


Requirements for GEA Framework(from Case study)

Identified drivers and expected

adjustments of TOGAF structure

& method


Holistic broad understanding versus deep exploration into

detail.

• Layered model of architectures by granularity (level of detail).

GEA versus other disciplines BPM, QM - CAF, PM, ...

• Also solved by proper layered model

• GEA cover question of concept existence

• Other disciplines focused on detail

Comprehensiveness versus feasibility (costs, resources,

time) of architecture maintenance

• Accelerators (localised guidelines, templates, reference

models and practical examples.


Identified GEA contradictions

„Holistic x detailed“ is solvable by layered architecture:

„Comprehensiveness x feasibility“ is solvable by accelerators like reference

models:


Ratio of contradiction solving

7

0

7

0 0

What is your prefered kind of Cognition?

Holistic

Detailed

Combined

Dont know

Other

80

3

1

Is it solvable by layered granularity?

Yes

No

Partly

Dont know

12

11

0

Do you feel contradiction?

Yes

No

Partly

Dont know13

000 1Is it solvable by Accelerators?

Yes

No

Partly

Dont know

No answer12

10

0

1

Do you plan use Accelerators?

Using patterns

Taylor made

Dont know

Other

No answer

Architecture layers of the Enterprise

16

Vision

Holistic

view

Whole overview

of domain / segment

Solution proposal for initiative

/ project / domain / segment

Design / construction of solution elements

History Environment

Enterprise Architecture

Solution Architecture

Solution Design

October 2014The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě

Architecture Vision

Holistic view of the Enterprise

Motivation

Solution architectures

Domain and segment architectures

Service execution Enterprise Resources

Segment enterprise architectures ( for division, industry, …)

Sectional (transversal) solution architectures ( for initiatives, projects, segment, domains)

Businessarchitecture

Performance architecture

Architecture IS Technology

infrastructure architecture

Security / Safetyarchitecture

Design / construction of solution elements

Businessarchitecture

Performance architecture

Architecture IS Technology

infrastructure architecture

Security / Safetyarchitecture


Reduction of Framework description and full translation of it• Localised subset of standard Framework (like other countries)

Selection from meta-model and structure towards simplicity:• Extension of meta-model by „Agenda“, „Law“, „Policy“ etc.

• Reduction of mandatory concepts in meta-model, see below

• Reduction of mandatory (recommended) artefacts

• Reduction of concept description detail to simply existential attributes

Addition of accelerators towards feasibility:• Localised reference models of:

Capabilities/processes/business services

Application components and services

Technology components and services

• Localised templates of artefacts (ready to use)

• Life examples from peer network

• Detailed practical Guidelines


Adoption of TOGAF / ArchiMate for Czech GEA(in general and for usage as EwITA for ICT reform)

Extension of meta-model towards comprehensiveness:

• new concepts especially in area of resources

E.g. for People, Knowledge, Asset & Liabilities, Security,

• Addition of whole new domains

Performance

Security

People

Assets

Production Technology

Facility

• Addition of new artefacts

• Extension of Preliminary phase by Enterprise Ontology and derived Thesauri

• Extension of ADM by phases for new domains


Additional changes to TOGAF and ArchiMate(for PA reform purpose)

Domains of Czech GEA – inspiration examples


(Source: OCIO HHS , 2010)

Business

Motivation

Organization

Function

Strategic context

Information systems

Application Data

Technology

(Source:TOGAF, The Open Group, 2009

(Source: FEAF 2.0)(Source: Gov. Of New Brunswik EAP, 2013)

Motivation architecture area:• Strategy (policies, programs, …)

• Performance, Quality& Sustainability

• Compliance (laws, agendas..)

• Security & Safety

Execution of services (business) architecture area:• Organization (units, roles, actors, locations and operating modes)

• Functions (projects, processes, services)

• Environment („market“, clients, vendors, partners, products, relations, ..)

Enterprise resource architecture area:• Information and Knowledge

• Information systems (Applications & Data)

• People a social relations

• Information technology infrastructure

• Facility, property, technology and infrastructure (buildings, production lines, …)

• Other assets & liabilities


Proposed focus of Czech GEA

Motivation

Service execution

Enterprise Resources


Expected structure of Czech GEA

Business architecture

IS Architecture

Technology Infrastucture

Stra

tegy

& P

erf

orm

ance

Secu

rity

& S

afet

y

Minimal mandatory meta-model (8 concepts)


Application Architecture Reference

Model

Example of an Accelerator for EA development

24 October 2014The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě

Reference model of Application Architecture


Cross-sectional application functions

Composite process-based applications

External entities with the business relations

InternalResources

&Registers

Governance, Risk

& Compliance

Organizational units and groups of users

User access

Knowledge base & inform.sharing

Managingrelationshipswith external

partners

Enterprise Resource Management

and Accounting

HR, inter.comm. & cooperation

Foundational& operational

systems

Externalsystems Integration and SOA platform

Reporting & analytical

applications

Performance & StrategyManagement

Otherregisters

© Pavel Hrabě 2014

Reference model of application architecture in

Public Administration


DMS GIS

Archiv CADMDMEA, BPM DWH, ETL

ITSM Data Quality

& others

EDI

OfficeIDM

ILM Internet

Informationand

media

Employees

Technology,Buildings

RegisteredObjects

Organizational units and groups of users

PA Clients –Citizens &

Organizations Suppliers,Partners

Parliament,Government

Public

ESB, EAI Real-time data platformMobile infr. Communic. infra. RFID infr.

APS –Logist.optim. SRM

Person.appl. Selfservice

Education Teamwork

Information management

Knowledge management

Content managementPA Presentation

GRC - Audit & Governance

DispatchingsTechnology

Control

ManagedRegisters

Extendedoperationalapplications

Finance

Logistics

Pers. admin & Payroll

Management of quality,safety & compliance

Industry spec. functions

Composite process-based applications

External PortalInternal Portal Mobile ApplicationsC

om

mu

nic

atio

nTe

chn

olo

gy ConstituentrelationshipManagement & Communicat-ion

(CRM)

Open items, Payments &Agenda Accounting

Agenda systems

Partnersin PA

execution

Budgeting, reporting & analytical application

Strategy and performance management

External systems

Internallocal

systems




Czech GEA structure & roadmap

proposal

28 October 2014The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě

More detailed structure of Government

Architecture


Czech GEA Blueprint

GEA Framework Concept

GEA Governance & LawConcept

GEA ImplementationRoadmap

GEA Tools-Set

GEA Framework

GEA Knowledge Management, Education & Communicatin

Institutions & resources for GEA develop., manag. and governance

GEA Legislation

GEA Usage Guides

GEA Management GEA Governance

Structure

AcceleratorsMethod

Metamodel Principles• Architecturing• Sharing• Service• Governance• Client• Efficience• Value ….

GEA Content

Reference Content

Common & Shared Content

Individual Architectures

As-IsArchitecture

To-BeArchitecture

GEA Roadmap

Plan of projects on the journeyto the target stateof architectureDelta (change) ∆

Graph.langu.


Ideal „greenfield“ Roadmap to GEA


GEA Reference & SharedContent Production

Individualarchitectures

GEA Legislation

Obligationof GEA

Official Pilot Verification Roll-out to the entire hierarchy of public administration

Checks on projects against GEA

Project architectures

GEA Roadmap

GEAFrameworkBlueprint

Voluntary Pioneering

Gover-nance &

LawConcept


GEA Institutions& Resources

Adjusted pragmatical approach

- incremental development





GEA Legislation

Obligationof GEA




GEA Roadmap

GEAFrameworkBlueprint


Gover-nance &

LawConcept

GEA Institutions & Resources



GEA Legislation

Obligationof GEA





GEA Institutions & Resources

∆ ∆ ∆

• Activities to run in parallel:

• Empowerment of architecture capabilities of MoI

• Modelling of core architect. artefact for capturing key eGovernment

achievements (BR, DB, CzP, KIVS, Portal, JIP, …)

• Proposals of reference models for public authorities

• Development of Czech GEA Framework based on standards and

knowledge transfer

• Update of methodology for public authorities to update their ICT

roadmaps (law 365/2000 Coll.)

• Development of „Whole-of-GEA“ roll-out roadmap

• Quick wins:

• Check of new invested (tendered) projects against eGov architecture

to keep mandatory concepts

• Step-wise reduction of multiplicity of applications


Expected next steps

• Czech GEA is one of the missing prerequisites for better ICT management and successful transformation of PA.

• It is recommended to extend the existing technological architecture by coherent architecture of activities of the state (business architecture), information systems, possibly performance architecture of the state.

• It is recommended to use all the ways of cooperation (inter-governmental, academic, non-profit and business) to ensure the transfer of proven experience in the development and use of GEA.

• Building of whole operational environment of Czech National EA, including all adaptation and localization, legislation, institutions, resources and knowledge transfer will be a long-term program which needs smart and feasible implementation roadmap to achieve both, quick and final benefits.

• TOGAF and ArchiMate standards are great foundation for own Czech GEA and can be later extended.

• For Public Administration is definitely needed to simplify TOGAF and to equip it with localised Best Practice content like Application Architecture Reference Model.


Conclusions

Contact:

Pavel Hrabě

[email protected]

+420 602 259 855

http://www.linkedin.com/pub/pavel-hrabe/2/5a/899

http://vse.academia.edu/PavelHrabe

http://www.slideshare.net/pavelhrabe/presentations


Thank you for your attention

mailto:[email protected]

http://www.linkedin.com/pub/pavel-hrabe/2/5a/899

http://vse.academia.edu/PavelHrabe

http://www.slideshare.net/pavelhrabe/presentations

Government & Nonprofit

Czech GEA Hrabe 2014