Czech GEA Hrabe 2014

TheConceptofCzech Public AdministrationEnterprise ArchitectureIng. Pavel Hrabě

•Motivationto researchand summary
•Czech Public AdministrationEA needs-Case study report
•Identifieddriversand expectedadjustmentsofTOGAF structure& method
•ExampleofanAccelerator–Reference Model ofApplicationArchitecture
•ProposedCzech GovernmentEA environmentand roadmap
2 The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě October 2014
Agenda

Iamin computer sciencesince 1989,
•as an analyst, solution architect, businessconsultant andenterprisearchitect(since2007)
The aim of mywork is :
•Verify theutilization rate of EAin Czech PA organizations
•Identifyreasonsof stilllittleacceptance ofthe EAin PA organizations,to analyse and objectifythem.
•Propose changes inTOGAF to solve identified contradictions
•Propose accelerators e.g. forthe application architecture.
•Propose the structure of EA environment and EA roadmap for Czech Public Administration.
Motivation

The statusof 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. TheActon 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, Communicationinfrastructure
But not architecture basedgovernance 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?
•Ifand 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 artefactsin domains (from 14)
oGeneral (meta) level
•Thesauri (business vocabulary) –1
oBusiness
•Service catalogue -0
•Process model –4
oPerformance
•System of KPI’s -full 0, partial 10 (for benchmarking initiative)
oApplication
•Application inventory and landscape –full 3, partial 4
oData
•Data architecture, e.g. Conceptual model of Enterprise –0
oTechnology –not asked
Absence of architecture in Czech PA

The need to better support of cognition, understanding and change management (9/14).
Target domainsof 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) 9 The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě October 2014
Czech PA agencies want to use GEA

Purpose of exploration and improvement
2
3
3
1
1
0
0
Centralauthorities
1
2
2
1
2
1
1
Counties
10
11
11
6
6
4
1
Alltogether
Cost reduction
Performance management
Service quality & satisfaction
eGovernment implement.
Infrastructure development
Interoperability implement.
Other: to find balance
4
4
3
2
2
2
0
Statutorycities
3
2
3
2
1
1
0
Smallcities
Wholereportin Czech atČSSI

•Interestto build architecture based on Best Practice and shareown 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, namedas bestaccess point to the Czech GEA BoK.
•Behind the portal should be operated central modelling environment & repository, complemented with social network functions.
•Public authoritieswant to getknowledgemostly 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(fromCase study)

Identifieddriversand expectedadjustmentsofTOGAF 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
WhatisyourpreferedkindofCognition?
Holistic
Detailed
Combined
Dont know
Other
8
0
3
1
Isitsolvableby layeredgranularity?
Yes
No
Partly
Dont know
12
1
1
0
Do youfeelcontradiction?
Yes
No
Partly
Dont know
13
0
1
Isitsolvableby Accelerators?
Yes
No
Partly
Dont know
No answer
12
1
0
0
1
Do youplanuse Accelerators?
Using patterns
Taylor made
Dont know
Other
No answer

ArchitecturelayersoftheEnterprise
16
Vision
Holistic
view
Wholeoverview
ofdomain/ segment
Solutionproposalforinitiative
/ project/ domain/ segment
Design / constructionofsolutionelements
History
Environment
Enterprise Architecture
SolutionArchitecture
SolutionDesign
The Concept of Czech Public Administration Enterprise Architecture, Pavel Hrabě October 2014

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)
Business
architecture
Performance architecture
Architecture IS
Technology infrastructure architecture
Security / Safety
architecture
Design / construction of solution elements
Business
architecture
Performance architecture
Architecture IS
Technology infrastructure architecture
Security / Safety
architecture

Reduction of Framework descriptionand full translationofit
•Localisedsubsetofstandard Framework (likeothercountries)
Selectionfrommeta-model and structure towards simplicity:
•Extension of meta-model by „Agenda“, „Law“, „Policy“ etc.
•Reduction of mandatory concepts in meta-model, seebelow
•Reduction of mandatory (recommended) artefacts
•Reduction of conceptdescription detail to simply existentialattributes
Addition of accelerators towards feasibility:
•Localisedreferencemodels of:
 Capabilities/processes/business services
 Application components and services
 Technology components and services
•Localisedtemplatesof artefacts (ready to use)
•Life examples from peer network
•Detailed practicalGuidelines
AdoptionofTOGAF/ArchiMateforCzech GEA(in general and for usage as EwITAforICT reform)

Extensionof 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)

DomainsofCzech GEA –inspirationexamples
(Source: OCIO HHS , 2010)
Business
Motivation
Organization
Function
Strategic context
Informationsystems
Application
Data
Technology
(Source:TOGAF, TheOpen Group, 2009
(Source: FEAF 2.0)
(Source: Gov. OfNew BrunswikEAP, 2013)

Motivation architecturearea:
•Strategy (policies, programs, …)
•Performance, Quality& Sustainability
•Compliance (laws, agendas..)
•Security & Safety
Execution ofservices (business) architecturearea:
•Organization (units, roles, actors, locations and operating modes)
•Functions (projects, processes, services)
•Environment („market“, clients, vendors, partners, products, relations, ..)
Enterprise resource architecturearea:
•Information and Knowledge
•Information systems (Applications & Data)
•People a social relations
•Information technology infrastructure
•Facility, property, technology and infrastructure(buildings, productionlines, …)
•Other assets & liabilities
Proposedfocusof Czech GEA
Motivation
Service execution
Enterprise Resources

ExpectedstructureofCzech GEA
Business architecture
IS Architecture
Technology Infrastucture
Strategy& Performance
Security& Safety

Minimalmandatorymeta-model (8 concepts)









ApplicationArchitectureReference Model
ExampleofanAcceleratorforEA development

Reference model ofApplicationArchitecture
Cross-sectionalapplicationfunctions
Compositeprocess-basedapplications
External
entities
with the
business
relations
Internal
Resources
&
Registers
Governance,
Risk
& Compliance
Organizational units and groups of users
User access
Knowledgebase
& inform.sharing
Managing
relationships
withexternal
partners
Enterprise Resource
Management
and Accounting
HR, inter.comm.
& cooperation
Foundational
& operational
systems
External
systems
Integrationand SOA platform
Reporting &
analytical
applications
Performance
& Strategy
Management
Other
registers
© Pavel Hrabě 2014

Reference model ofapplicationarchitecturein Public Administration
DMS
GIS
Archiv
CAD
MDM
EA, BPM
DWH, ETL
ITSM
Data Quality
& others
EDI
Office
IDM
ILM
Internet
Information
and
media
Employees
Technology,
Buildings
Registered
Objects
Organizational units and groups of users
PA Clients–
Citizens&
Organizations
Suppliers,
Partners
Parliament,
Government
Public
ESB, EAI
Real-timedata platform
Mobile infr.
Communic. infra.
RFID infr.
APS –
Logist.optim.
SRM
Person.appl.
Selfservice
Education
Teamwork
Informationmanagement
Knowledgemanagement
Contentmanagement
PA Presentation
GRC -Audit
& Governance
Dispatchings
Technology
Control
Managed
Registers
Extended
operational
applications
Finance
Logistics
Pers. admin& Payroll
Management ofquality,
safety& compliance
Industryspec. functions
Compositeprocess-basedapplications
External Portal
InternalPortal
Mobile Applications
CommunicationTechnology
Constituent
relationship
Management
&
Communicat-
ion
(CRM)
Open items,
Payments&
Agenda
Accounting
Agenda
systems
Partners
in PA
execution
Budgeting, reporting & analyticalapplication
Strategyand performance management
External
systems
Internal
local
systems

Czech GEA structure & roadmap proposal

More detailedstructureofGovernmentArchitecture
Czech GEA Blueprint
GEA Framework Concept
GEA Governance & LawConcept
GEA ImplementationRoadmap
GEA Tools-Set
GEA Framework
GEA KnowledgeManagement, Education& Communicatin
Institutions& resourcesforGEA develop., manag. and governance
GEA Legislation
GEA UsageGuides
GEA Management
GEA Governance
Structure
Accelerators
Method
Metamodel
Principles
•Architecturing
•Sharing
•Service
•Governance
•Client
•Efficience
•Value….
GEA Content
Reference Content
Common& SharedContent
IndividualArchitectures
As-Is
Architecture
To-Be
Architecture
GEA Roadmap
Planofprojectson thejourney
to thetargetstate
ofarchitecture
Delta (change)Δ
Graph.langu.

Ideal„greenfield“ Roadmapto GEA
GEA Reference & SharedContentProduction
Individualarchitectures
GEA Legislation
ObligationofGEA
OfficialPilot Verification
Roll-out to the entire hierarchy of public administration
Checks on projects against GEA
Project architectures
GEA Roadmap
GEA
Framework
Blueprint
Voluntary Pioneering
Gover- nance& LawConcept
GEA Institutions& Resources

Adjustedpragmaticalapproach-incrementaldevelopment
GEA Legislation
ObligationofGEA
GEA Roadmap
GEA
Framework
Blueprint
Gover- nance& LawConcept
GEA Legislation
ObligationofGEA
Δ
Δ
Δ

•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(law365/2000 Coll.)
•Development of „Whole-of-GEA“ roll-out roadmap
•Quick wins:
•Check of new invested (tendered) projects against eGovarchitecture to keep mandatory concepts
•Step-wise reduction of multiplicity of applications
Expected next steps

•CzechGEAis oneof the missing prerequisitesfor better ICT management and successful transformation of PA.
•It is recommendedto extend theexisting technologicalarchitecture bycoherent architectureof activities of the state(business architecture),informationsystems, possibly performancearchitectureof the state.
•It is recommended to useall the waysof cooperation (inter-governmental, academic, non-profitand business) toensure the transfer ofprovenexperience in the developmentanduse ofGEA.
•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ě
pavel.hrabe@vse.cz
+420 602 259 855http://www.linkedin.com/pub/pavel-hrabe/2/5a/899
http://vse.academia.edu/PavelHrabe
http://www.slideshare.net/pavelhrabe/presentations
Thankyouforyourattention

Czech GEA Hrabe 2014

Recommended

Recommended

More Related Content

Similar to Czech GEA Hrabe 2014

Similar to Czech GEA Hrabe 2014 (20)

More from Pavel Hrabe

More from Pavel Hrabe (9)

Recently uploaded

Recently uploaded (20)

Czech GEA Hrabe 2014