new infrastructure architecture at the swedish...

Mats Gejnevall, Enterprise Architect

Open Group Conference, Stockholm, 2011-11-08

Infrastructure architecture at the Swedish police

| Application Consulting

RPS – What do it do

Rikspolisstyrelsen, RPS is the central governance and

service authority for the Swedish police.

The main task for RPS is to govern, coordinate and

rationalize the work of the police

RPS is responsible for central IT, method development and

education

RPS distributes the budget for the police among the

different police departments

Application Consulting

The IT strategy and IT action plan for the police


Main components of the EA function

Governs

Verksamhet

Information

Applikation

Infrastruktur

RPS EA governance PARK – RPS Architecture

RPS EA Framework

Prepare

Support

Control

Measure


Description model based on TOGAF

Terminology based on TOGAF

Tools for documentation of the architecture

Presentation format

Logical target architecture

Recommendation on requirements for common

infrastructure components

Business case

Governance model

The scope of the infrastructure architecture project

TOGAF 9

TOGAF_ACM PARK4 Förv altingsprocesser

PARK4 Förvaltning

PARK4 Bereda PARK4 Stöda PARK4 Styra PARK4 Mäta och

följa upp

«Decompose» «Decompose» «Decompose» «Decompose»

Säkerhet

Styrning/Ledning

Utveckling

Grundplattform

Lösningsplattform

Användare Integration

Information

Ärenden

Datorer

Kommunikation

CMDB

Polis i yttre tjänstPolis i yttre tjänstPolis i inre tjänst AllmänhetenAllmänheten

MainframesServers

Storage

ESBESB


Detailed descriptions of the

infrastructure components

System/Software architecture patterns

Descriptions of the connection between

current applications and infrastructure

components

This is NOT part of the infrastructure architecture

Business

Information

Application

Infrastructure


Architecture process first phase

TOGAF

Iteration

Deliverables

Context Project contract

Stakeholder & communication model

Adapted architecture framework

Vision for the architecture

Governing principles

Definition Baseline infrastructure architecture

Infrastructure requirements


Architecture process second phase

TOGAF

Iteration

Deliverables

Definition Target architecture

Suggested architecture solutions

Transition

Planning

Business cases and prioritization

Roadmap

Governance Control and maintenance


An architecture that ensures a flexible

and cost efficient future development

platform of the police application

landscape

A governance structure for the

architecture ensuring the architecture

continuously is adapted to the

requirements of the business

A governance function that supports

the development projects ensuring that

infrastructure is used in a consistent

and effective way

9

The goal and vision of the infrastructure architecture

Säkerhet

Utv.metodik

MDM

EA-ramverk

Klientplattform

SOA-ramverk

Serverplattform

Ramverk förextern

integration

Ramverk förintern

integration

ITIL

Applikations-ramverk

BI

Gemensammatjänster

LAN/WAN

ReglerE-tjänster

Datawarehouse

Ärendehantering


The architecture shall describe the entire infrastructure

landscape

The architecture shall secure that a standardized set of

lifecycle managed infrastructure components are

available with high level guidelines how these should be

used in different situations

The architecture shall minimize the number of

infrastructure solutions

The architecture shall be cost efficient and business

cases shall be available for prioritized components

The architecture must be traceable to the projects and

business requirements defined in the IT strategy and IT

plan

Requirements on the infrastructure architecture


Ensure a long-term well documented

infrastructure architecture (baseline and

target)

Create a base for collaboration (other

architects, guidelines)

Establish a clear process for architecture work

(support, control, methods, responsibilities)

Ensure competence

Governance requirements


And a number of views of the architecture in

this repository

The repository and views have been create

with SPARX EA according to the TOGAF

meta-model

All information is available on the internal

web in a clickable HTML format

Views created are:• Overview of components

• Reference models for baseline and target

architecture

• Architecture patterns describing the usage of the

components

Overview

TRM Baseline

Pattern y

Pattern x

TRM Target

Repository

The architecture is defined in a repository


Lösningsplattform

Grundplattform

Utv

ecklin

g

Sty

rnin

g/le

dn

ing

Sä

ke

rhe

t

The Technical Reference Model classifies the infrastructure

Solution platform

Basic platform

De

ve

lop

me

nt

Go

ve

rna

nce

Se

cu

rity


Basic platform

Basic platform

Computer system

Storage

Communication

Data center Infr

ast

ructu

re s

up

po

rt

Execution environment


Solution platform

Solution platform

Channels

Presentation

Infrastruktur applikations Information

Integration

Inte

grat

ion

Process


All combines into the full Technical Reference ModelSecu

rity

Go

vernan

ce

Develo

pm

ent

Basic platform

Solution platform

Channels

Presentation

Infrastruktur applikations Information

Integration

Inte

grat

ion

Process

Computer system

Storage

Communication

Data center Infr

astr

uct

ure

su

pp

ort

Execution environment


The target architecture is

defined as a number of components (sample)

Components

External communication

Business Intelligence

Data warehouse

Rules management

Master Data Management

Operational Data Store

Case management

Archiving

….


Together the components are combined into a comprehensive consistent framework for future solutions

Säkerhet

Styrning/Ledning

Utveckling

Grundplattform

Lösningsplattform

Användare Integration

Information

Ärenden

Datorer

Kommunikation

CMDB

Polis i yttre tjänstPolis i yttre tjänstPolis i inre tjänst AllmänhetenAllmänheten

MainframesServers

Storage

ESBESB


Each component is described by

its functionality and relations to other components TOGAF_ACM <<Architectural Pattern>> Regelhantering

Integration

Beroende till infrastrukturkomponenter

:Design & utv eckling av

v erksamhetsregel

:Regelhantering

Verksamhet :

Anv ändare

Regel designer :

Anv ändare

Systemadministratör

:Anv ändare

:Underhåll & adminstration av

v erksamhetsregel

:Verksamhetssystem

:Anv ändargränssnitt

:ESB

:Databas :Applikationsserv er

:Anv ändare

Central regelhantering med anrop direkt från

verksamhetssytem eller för att orkestrera en

dialog mot slutanvändaren baserad på

underlgande regelverk och given indata.

:Regellager

«flow»

«flow»

«flow»


The way forward - Roadmap

Each project in the roadmap contains a number of

standard activities

Produce more detailed requirements

Select product and perform Proof-Of-Concept(PoC)

Perform and evaluate PoC

Purchase product

Produce usage guidelines

Update the architecture

For specific components other activities will be

performed as well

Activities

Activity 1

Activity 2

Activity 3, Milestone 1

Activity 4

Activity 5 , Milestone 2

Activity 6

...

T2 T3 T4 T5 T6 T7 T8 T9 T10T1


The infrastructure architecture must be

governed to ensure long-term

TOGAF_ACM Infrastrukturförvaltning - Processer

Measure and changeControl SupportPrepare

Infrastructure governance

«Decompose» «Decompose»«Decompose» «Decompose»

Control

80%

Support

10%

Prepare

10%

Control

10%

Support

50%

Prepare

40%

Governance focuses to much

at controlling

Governace should be focused

on supporting instead


The governance of the architecture must be done

together with competence centers for the components

Each competence center also have prepare, support and control

processer

TOGAF_ACM Infrastrukturförvaltning och kompetenscenter

Development

Pre-study

Support ControlPrepare

Kompetenscenterförvaltning

KC ControlKC SupportKC Prepare

Infrastrukturförvaltning


Each competence center has different responsibilities

Business Intelligence

•Operative planning

•Operative analysis

•Strategic analysis

Information

•Master data

•Information governance

•Information modeling

Integration

•Internal integration

•External integration

Content management

•Web & Portals

•Document management

•Digital media management

•Archiving

Security

•Access control

•Net security

•Platform

•Governance

Business rules• Rules management

Process

•Case management

•Work flow

•Orchestration

•Event management

Collaboration

•Chat and text communication

•Conference system

•Information portal

•Project place

System architecture

Server platform•Open Source

•Virtualization


Each component contributes with its benefits

Decrease development and governance costs

Decreased number of platforms

High information availability and quality

Rational governance and an efficient

administration and operational support

Shortened time to deliver


Summary

The infrastructure architecture will enable the police to

create a cost efficient future based on modern

standardized best-practice infrastructure

solutions in collaboration with the business that

continuously is adapted to the future goals and

needs.


More information

Insert "Title, Author, Date"

28© 2011 Capgemini. All rights reserved.

With around 115,000 people in 40

countries, Capgemini is one of the world’s

foremost providers of consulting,

technology and outsourcing services. The

Group reported 2010 global revenues of

EUR 8.7 billion.

Together with its clients, Capgemini creates

and delivers business and technology

solutions that fit their needs and drive the

results they want.

A deeply multicultural organization,

Capgemini has developed its own way of

working, the Collaborative Business

ExperienceTM, and draws on Rightshore®,

its worldwide delivery model. More

information is available at

www.capgemini.com

Rightshore®

is a trademark belonging to Capgemini

About Capgemini

http://www.capgemini.com/





new infrastructure architecture at the swedish...

Documents