Creating synergy between BPM and EA in an e-government environment

5TH ANNUAL BUSINESS PROCESS EXCELLENCE SUMMITDUBAI, UAE, 2009

CREATING SYNERGY BETWEEN BPM AND EA IN AN E-GOVERNMENTENVIRONMENT

Dr Alexander Samarin

www.samarin.biz

WWW.SAMARIN.BIZ

About me

• An enterprise solutions architect– From a programmer to a systems architect

– Experience in scientific, international, governmental and industry environments

– Have created systems which work without me

– Practical adviser for design and implementation of enterprise solutions

• Current specialisation is improving business process management systems

• Book in preparation www.improving-BPM-systems.com

2 2009-05-31

Creating synergy between BPM and EA in an e-government

WWW.SAMARIN.BIZ

• Unlimited life-cycle– unpredictable and incremental evolution

• Socio-technical system– how you do something is sometimes more important

than what you do

• Collaborative system• Industrialised system• Ability for rapid innovation is important• Variety of services (up to 1000 in some catalogues)• High level of security for personal data

E-government is a very complex system

3 2009-05-31


WWW.SAMARIN.BIZ

• The architecture must provide a high level of adaptability to– policies and priorities of the Government

– structure of ministries and departments

– IT applications, systems, data and hardware

– constantly changing business processes

– size and complexity of problems to be addressed

– available budget

– level of computerisation

– all stakeholders

The goal – easy evolution of an e-government

4 2009-05-31


WWW.SAMARIN.BIZ

• Different estimations of the development/maintenance life-cycle cost ratio

Need for adaptive architecture

52009-05-31


95 %

5 %

40 %

60 %

80 %

20 %

1 – Estimated average in the IT industry2 – A real scenario (governmental client)3 – Estimated by an IT staff member

maintenance

development

1 32

WWW.SAMARIN.BIZ

– top managers– enterprise architects– business line managers– process owners– super-users– normal users– project managers– business analysts– IT managers– IT architects– IT developers

Too many internal stakeholders

62009-05-31


WWW.SAMARIN.BIZ

Process-oriented view of an enterprise

2009-05-31Creating synergy between BPM and EA in an e-government 7

WWW.SAMARIN.BIZ

• Dynamic set of artefacts• Artefacts are interconnected and interdependent• We have to anticipate potential changes:

– policies, compliance, technology, etc.

• Implementation of such changes necessitates the evolution of some artefacts and the relationships between them

• It must be easy to modify all artefacts and relationships without causing any negative effects

System architecture view of an enterprise

82009-05-31


WWW.SAMARIN.BIZ

• Business artefacts– Events– Processes– Activities– Roles– Rules– Data & documents– Audit trails– Performance indicators– Services

• Technical artefacts …

Different enterprise artefacts

9 2009-05-31


KPIs

Processes

Services

Events

Roles Data structures

Documents

Rules

Human “workflow”

Audit trails

WWW.SAMARIN.BIZ

• All artefacts must be versionable throughout their life-cycle

• All artefacts must be evolved to become – digital

– externalised

– virtual

– components of clouds

• All relationships between these artefacts are modelled explicitly

• All models are made to be executable

Main principles of adaptive architecture

10 2009-05-31


WWW.SAMARIN.BIZ

• More knowledge about functioning of the enterprise• More predictable results• More rational decisions• More comprehensive optimisation

• Also executable models are:– testable

– platform-independent

Advantages of executable models

11 2009-05-31


WWW.SAMARIN.BIZ

• Who (roles) is doing What (business objects), When (coordination of activities), Why (business rules), How (business activities) and with which Results (performance indicators).

• Make these relationships explicit and executable

What you model is what you execute

Business processes are complex relationships between artefacts

122009-05-31


WWW.SAMARIN.BIZ

• Main technologies– Business Process Management (BPM)

– Service-Oriented Architecture (SOA)

• Other technologies– ECM, BEM, BI, BRM, MDM, ESB, BAM, ITIL, …

• Profound integration with– Enterprise architecture (EA)

– Project management practices

• Principles for design of flexible systems

Adaptive architecture – a coherent set of existing technologies

13 2009-05-31


WWW.SAMARIN.BIZ

BPM is a tool for improving enterprise business performance

14 2009-05-31


BPM as a discipline

BPM as software:BPM suite (BPMS)

Any process-centric enterprise has some BPM, but how can we industrialise this BPM?

WWW.SAMARIN.BIZ

• Natural evolution of methodologies for improving enterprise business performance – Process reengineering, Lean,

ISO 9000, 6 Sigma

• One description of business processes– model in design– input for project planning and execution– executable program for coordination of work– documentation for all staff members

• Basis for use and selection of modern technologies

Business Process Management (BPM)

15 2009-05-31


From Gartner

WWW.SAMARIN.BIZ

• Definition– architectural approach for constructing

software-intensive systems from a setof universally interconnected and interdependent services (operationally independent functional units)

• Advantages– use of standard and pre-fabricated building blocks

– high level of system flexibility

Service-Oriented Architecture (SOA)

16 2009-05-31


WWW.SAMARIN.BIZ

• BPM, by revealing the artefacts and the relationships between them, provides the necessary context (e.g. granularity) for the definition of services

• SOA provides recommendationsfor the implementation, execution and governance of services

Synergy between BPM and SOA

2009-05-31Creating synergy between BPM and EA in an e-government 17

WWW.SAMARIN.BIZ

• Definition– coherent and proven set of principles,

recommendations, rules, practices, and tools which provides guidance and practical help for the design and evolution of IT and business to achieve enterprise vision and strategy

• Advantages– Validation of architectures

– Guarantee of coherence

– Optimisation of architectures

– Help and coaching

Enterprise architecture (EA) is a tool for the design of future states

18 2009-05-31


WWW.SAMARIN.BIZ

• “enterprise genotype” (a full nomenclature of enterprise artefacts) – classic EA

• “enterprise phenotype” (a set of observable characteristics such as performance)

• Formal link between them via “enterprise executable model” – EA enhanced by BPM and SOA

Enterprise executable model

19 2009-05-31


WWW.SAMARIN.BIZ

“Administration en Ligne” (AeL)

20 2009-05-31


AeL

10 first services (+25)

Common services and dictionaries

Common technical

componentsMan

agem

ent

- A

rchi

tect

ure

Fac

ilita

tion

of c

hang

es .

.

•Identity management•Access management•Common support•E-payment•E-form•Document management

•Project management - HERMES•AeL Centre

•New way to work together•Cyber-inclusion

•Tax (individual) on-line•Tax (company) on-line•Social help on-line•Portal for people•Registration of cars•Request for demonstrations•SME Geneva•Building permits•Administration of doctors•Schools on-line

WWW.SAMARIN.BIZ

Government

Partners

Internal existing

application

Existing applications for e-government

App

licat

ion

1

Internal existing

application

Internal existing

application

2009-05-3121 Creating synergy between BPM and EA in an e-government

App

licat

ion

2

App

licat

ion

3

WWW.SAMARIN.BIZ

Government

Partners

Internal existing

application

Coordination and integration (BPM/SOA-based)

e-Government

Draft architecture for e-government (initial state)

Collaborative extranet (ECM-based)between partners and government

e-gov service

e-gov service

e-gov service

Internal existing

application

Internal existing

application


ECM – Enterprise content management

WWW.SAMARIN.BIZ

Government

Partners

Internal existing

application


e-Government

Draft architecture for e-government (initial state)


e-gov service

e-gov service

e-gov service

Internal existing

application

Internal existing

application


E-government applications

WWW.SAMARIN.BIZ

Government

Partners

service


Draft architecture for e-government (future state)


serviceserviceservice

service service service service


WWW.SAMARIN.BIZ

• Formed at the federal level in Autumn 2008• Open to 26 cantons (highly autonomous) and more

than 1000 communities• Current agenda

– Rework of eGovCH (Big Picture)– Design rules for IT Architecture – Design rules for Identity and Access Management– Handling of unstructured information

Swiss E-government Architecture Committee (SEAC)

25 2009-05-31


WWW.SAMARIN.BIZ

Functional Scope Level 0 and Level 1


Services

Scope: Partners interact with Cyber-administration

This model is recursive!

Scope: Administration unitsinteract with other units and Partners through defined services

WWW.SAMARIN.BIZ

• Be legal• Be an enabler• Be effective• Be flexible• Be secure• Be social and democratic• Be methodological• Be explicit

Basic architectural principles

27 2009-05-31


WWW.SAMARIN.BIZ

=mcminstituteProf. Dr. Beat F. Schmid

© =mcminstitute

SOA: A Promising Architectural Style For Designing IT Service Infrastructures

SOA System A

Organization

WS-Interf.

Services & Infrastructure

SOA System B

SOA System C

WS-Interf.

Language

Information

Object

----------

Service-Registry

Schroth, Christoph ; Janner, Till: Web 2.0 and SOA: Converging Concepts Enabling the Internet of Services. In: IT Professional 9 (2007), Nr. 3, S. 36-41.


© =mcminstitute


SOA System A

Organization

WS-Interf.


SOA System B

SOA System C

WS-Interf.

Language

Information

Object

----------

Service-Registry



© =mcminstitute


SOA System A

Organization

WS-Interf.


SOA System B

SOA System C

WS-Interf.

Language

Information

Object

----------

Service-Registry


• Three layers: – services/infrastructure

– language

– organisation

• Exchange between each layer:– Event Bus Swiss

– common dictionaries (see www.ech.ch)

– explicit coordination of units

Inter-unit communication

28 2009-05-31



© =mcminstitute


SOA System A

Organization

WS-Interf.


SOA System B

SOA System C

WS-Interf.

Language

Information

Object

----------

Service-Registry


WWW.SAMARIN.BIZ

• Use of architecture to reduce the complexity • BPM reference model• Attention to the most difficult aspect – people• Use of explicit and executable models• Business process modelling in BPMN• Quick prototyping• Guidelines for usage of different technologies• Link with enterprise architecture

Main points of adaptive architecture

29 2009-05-31


WWW.SAMARIN.BIZ

Thank you!

Contact information:

Alexander Samarin

[email protected]

www.improving-BPM-systems.com


Technology

Creating synergy between BPM and EA in an e-government environment