Download - SLIDES
© 2007 IBM CorporationDRAFT Strategy and Architecture 1
Gaining Shared Services Momentum Within HMRC
A Strategy and Architecture Driven Approach
© 2007 IBM CorporationDRAFT Strategy and Architecture 2
Contents
The essence of sharing
The UK government context
The approach at HMRC
Our services taxonomy
What we have achieved so far
Our key lessons learnt
Enabling Shared Services Within HMRC
© 2007 IBM CorporationDRAFT Strategy and Architecture 3
The essence of sharing is re-use…
People Process Mentality Technology Result
Technology ! = Changes
Presented at Open Standards 2008 - Composability within SOA, Andy Lee, CTO, Changfeng Alliance, Chief Scientist, Beijing eBridgeChina Ltd
© 2007 IBM CorporationDRAFT Strategy and Architecture 4
...and knowing how to handle change!
Collaboration Funding Model and Business
Cases
Know the answer before they ask
the question
Technology Result
Technology ! = Changes
Original presented at Open Standards 2008 “Composability within SOA”, Andy Lee, CTO, Changfeng Alliance, Chief Scientist, Beijing eBridgeChina Ltd
Still Hard
© 2007 IBM CorporationDRAFT Strategy and Architecture 5
Cross Government Shared Services
In the UK the ‘CIO Council’ was formed in January 2005 to align architectural initiatives across government. The alignment is expressed in, and enabled by, the Cross Government Enterprise Architecture (xGEA).
Shared Services are a key concern of the ‘CTO Council’, and the progress in this area can be seen in the maturity of the Government Gateway.
The current focus of the CIO Council is on shared corporate services across government (http://www.cio.gov.uk/shared_services/introduction)
© 2007 IBM CorporationDRAFT Strategy and Architecture 6
CTO Council – enabling shared services
© 2007 IBM CorporationDRAFT Strategy and Architecture 7
Shared Service Example - The UK Government Gateway
January 2001 – Government Gateway launched, heralding the start of the Government's online secure joined-up service delivery agenda. It provided multiple government departments and agencies with a common Authentication Engine, Registration and Enrolment Engine, Transaction Engine and Helpdesk Tools
July 2001 – Government Gateway wins its first major awards - Government Computing Innovation award and the Digital Britain award for joined-up government
October 2003 – Government Gateway Payment Engine launched
December 2005 – 100th live service enabled via the Government Gateway
May 2006 – The HMRC Self Assessment peak processed over 1 million submissions processed through the Government Gateway in a single month
November 2006 – The introduction of a 24 / 7 365 days a year service desk under a Managed Service Provider arrangement
January 2007 – 3 million people have submitted their Self Assessment Tax forms via the Government Gateway. Nearly 2 million people submitted their Self Assessment Tax forms via the Government Gateway in January 2007.
January 2009 – The Self Assessment submission peak surpasses all predictions, all processed within the expected timescales and with no service outage – 5.8m SA Tax submissions.
© 2007 IBM CorporationDRAFT Strategy and Architecture 8
Transformational Government Shared Services
The Cabinet Office document on Transformational Government Enabled by Technology, first published in November 2005, is the guide to a Shared Services vision for Government departments, including HMRC.
– It includes Shared Services that are not Shared Solutions
– It is focussed on services delivered to customers
Within HMRC, IMS has the key role of ensuring that the architecture is able to provide and support Shared Services.
© 2007 IBM CorporationDRAFT Strategy and Architecture 9
HMRC Context
© 2007 IBM CorporationDRAFT Strategy and Architecture 10
The Reference Architecture FrameworkCONTEXTUAL
CO
NC
EP
TU
AL
LO
GIC
AL
PH
YS
ICA
L
Business Information Information Systems
Technology Infrastructure
What is the business
of the business ?
What information does the Business
require ?
What IS functions are required ?
What technical services are required ?
How would the business be structured (ideally)?
How would the information be
related (ideally)?
How would the functions be
structured (ideally)?
How are the boxes & wires structured
(ideally) ?
Which data storage and transfer
mechanisms ?
Which packages & bespoke software?
Which h/w, systems s/w &
network components
What are the business drivers, goals and priorities?
Which physical buildings, people
etc…
WH
AT
HO
WW
ITH
WH
AT
© 2007 IBM CorporationDRAFT Strategy and Architecture 11
Traceability from Business Service to Technology
© 2007 IBM CorporationDRAFT Strategy and Architecture 12
A standard project process enables reliable delivery
Architecture
and Design
Requirements
(Complicated Needs)
Build
HMRC
Business
Operations
© 2007 IBM CorporationDRAFT Strategy and Architecture 13
Architecture
and Design
IMS Strategy & Architecture Breaks Down the Silos…
Enterprise Strategy and
Planning
Enterprise Architecture
Enterprise Portfolio
Management
Requirements
(Complicated Needs)
BuildIT
Operations
HMRC
Business
Operations
© 2007 IBM CorporationDRAFT Strategy and Architecture 14
..and avoids the project design vacuum
Channel DeliveryChannel Delivery
Customer Management
Business Process Management
Regime Specific Capabilities
Decision Management
Accounting, Debt and Resource Management
Business Intelligence
Information Management
Tax
Credits
Child TrustFund
Child Benefit
IndividualTax
BusinessTax
ConstructionIndustry Scheme
StampDuty Tax
ExciseCustoms and International
Integration
Channel DeliveryChannel Delivery
Customer Management
Business Process Management
Regime Specific Capabilities
Decision Management
Accounting, Debt and Resource Management
Business Intelligence
Information Management
Tax
Credits
Child TrustFund
Child Benefit
IndividualTax
BusinessTax
ConstructionIndustry Scheme
StampDuty Tax
ExciseCustoms and International
Integration
© 2007 IBM CorporationDRAFT Strategy and Architecture 15
The flow is simple….
Project Requirements
Complicated
Needs
Project
Architecture
Project Result
Strategic Requirements
Complex
Needs
Project Requirements
Complicated
Needs
Project
Architecture
Project Result
Strategic Requirements
Complex
Needs
What Does
Happen
What Could
Happen without S&A
© 2007 IBM CorporationDRAFT Strategy and Architecture 16
We also Encourage Continuous Improvement
RequirementsServices
Identify Funding
for Shared Needs
Design Authority
for Shared Solutions
Design Authority
For Shared Portfolio
Live Operations
Projects
NeedsCapability
© 2007 IBM CorporationDRAFT Strategy and Architecture 17
Types of Sharing
The OASIS SOA-RM () defines SOA as: “Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.”
We have an HMRC approach to sharing that is compatible with this.
© 2007 IBM CorporationDRAFT Strategy and Architecture 18
Issues of shared service provision
Funding
Project-defined solutions reflects project needs
Satisfying differing SLA’s
Accommodating change over time
Migrating from the existing “brown field”
© 2007 IBM CorporationDRAFT Strategy and Architecture 19
Types of Sharing
There are several ways to share:
– Shared system• Copy a system into another instance• Share a single instance• Have a virtual instance on a shared platform
– Shared Application Service (classic SOA)• Dynamically linked external services• Statically linked external services
– Share supporting structures• Shared business support (e.g. shared printing)• Shared infrastructure support (e.g. shared storage)
– Share Data• Master Data Management• Business Intelligence
– Shared Resource• Common Contact Centres
© 2007 IBM CorporationDRAFT Strategy and Architecture 20
Types of Sharing within Shared Solutions
‘SharedPattern’
‘SharedInstance’
‘VirtualisedInfrastructure’
‘SharedData’
‘SOA’
‘Static Linking’
‘Dynamic Linking’
‘Cloned’
‘Shared Solutions’
SOA in this diagram refers to applications where standard remote ‘call’ connection technologies, such as HTTP, are used to utilise external application services.
© 2007 IBM CorporationDRAFT Strategy and Architecture 21
Virtualised Infrastructure
Platform
Operating System
Application
Definition
Instance
Virtualisation of Platform, e.g. Mainframe context switching
Virtualisation of Environment e.g. VMWare
Virtualisation of Function e.g. Cloud Computing
© 2007 IBM CorporationDRAFT Strategy and Architecture 22
Shared Data
Platform
Operating System
Application
Definition
Instance Shared Data
through shared information pool
Shared Data Through a Shared InstanceInformation
© 2007 IBM CorporationDRAFT Strategy and Architecture 23
Shared Instance
Platform
Operating System
Application
Definition
Instance
Shared Instance for all users
Information can be shared or segregated by specific users or functions
Information
© 2007 IBM CorporationDRAFT Strategy and Architecture 24
Shared Pattern
Platform
Operating System
Application
Definition
Instance
Development costs can be reduced by copying an existing pattern and creating ‘clones’.
Platform
Operating System
Application
Definition
Instance
© 2007 IBM CorporationDRAFT Strategy and Architecture 25
Shared Oriented Applications
Platform
Operating System
Application
Definition
Instance
Reuse of existing functionality by remote invocation of another application
Platform
Operating System
Application
Definition
Instance
© 2007 IBM CorporationDRAFT Strategy and Architecture 26
Transformational Government Shared Services
You have to measure success by the outcome.
In the Transformational Government Strategy there are 8 key areas within which Shared Services must be achieved:
– Customer Service Centres
– Human Resources, Finance and Corporate Services
– Common Infrastructure
– Data Sharing
– Information Management
– Information Assurance
– Identity Management
– Technology Standards and Architecture
© 2007 IBM CorporationDRAFT Strategy and Architecture 27
Historically, ‘HMRC’ Services have been Siloed with Little Sharing
Service Security View StrategyCustomer Service Centres It is not possible to share these
services between IR and C&EOptimise the local use of services
Human Resources, Finance and Corporate Services
It is not possible to share these services between IR and C&E
Optimise the local use of services
Common Infrastructure It is not possible to share these services between IR and C&E
Optimise the local use of services
Data Sharing It is not possible to share these services between IR and C&E
Optimise the local use of services
Information Management It is not possible to share these services between IR and C&E
Optimise the local use of services
Information Assurance It is not possible to share these services between IR and C&E
Optimise the local use of services
Identity Management It is not possible to share these services between IR and C&E
Optimise the local use of services
Technology Standards and Architecture
It is not possible to share these services between IR and C&E
Optimise the local use of services
HMRC was organised as two distinct departments: Inland Revenue and Customs & Excise, with separate systems and services.
© 2007 IBM CorporationDRAFT Strategy and Architecture 28
Transformational Government Shared Services
Shared Service HMRC Security View HMRC StrategyCustomer Service Centres It is possible to share these
services with other departmentsVirtual service provision tailored
Human Resources, Finance and Corporate Services
It is possible to share these services within HMRC
A single ERP Instance to service all of HMRC
Common Infrastructure It is possible to share these services within HMRC
Virtualisation and commoditisation of platforms
Data Sharing It is possible to share these services with other departments
Given the confidential nature of the data, sharing is limited
Information Management It is possible to share these services with other departments
Standard definitions of information items shared across government
Information Assurance It is possible to share these services with other departments
In preparation for wider Data sharing in the future, HMRC will align with other Assurance standards
Identity Management It is possible to share these services with other departments
HMRC is collaborating with DWP and other EU states on Identity Management
Technology Standards and Architecture
It is possible to share these services with other departments
HMRC is actively pursuing Technology Standards
© 2007 IBM CorporationDRAFT Strategy and Architecture 29
Shared Services within HMRC
We are still a long way from where we want to be, but we are making progress in most areas and have had some real successes. The lessons we have learnt are:
– Aligning the entire business has been key, and this has been possible thanks to clear central government leadership.
– Our suppliers have also contributed to this success, in supplying key technology and know how.
– Involvement in the complete business cycle, has been vital including:• Identification of funding for shared needs (IMS Business Partners)• The Design Authority for Shared Portfolio (IMS Portfolios)