ict strategy from systems to services version 1.0 version 1.0

10
ICT Strategy ICT Strategy From Systems to Services From Systems to Services Version 1.0 Version 1.0

Upload: marquis-piggott

Post on 31-Mar-2015

231 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: ICT Strategy From Systems to Services Version 1.0 Version 1.0

ICT StrategyICT Strategy

From Systems to ServicesFrom Systems to Services

Version 1.0Version 1.0

Page 2: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Strategic Direction

• The HA’s strategy is to move away from purchasing “islands of technology” to the procurement of modular, loosely-coupled, managed services.

Page 3: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Technology model

TECHNOLOGY

Business model

BUSINESS

Historical system-based architecture

Business siloed by

ICT

Solutions impose

constraints

Inwardtechnology driven

view

Focus on docume

nt exchang

e

SNMPOracle

UNIXCORBA

Applications

NTCC

Projects

RCC

Page 4: ICT Strategy From Systems to Services Version 1.0 Version 1.0

BUSINESS

TECHNOLOGY

Soft boundaries(process & services)

Processes

Services

Service Model

Business Model

Technology Model

Service-Oriented Architecture (SOA)

Outwardbusiness-

driven view

Focus on

service

Focus on

contract

Page 5: ICT Strategy From Systems to Services Version 1.0 Version 1.0

The Service Model

Aligning the Business and Technology Perspectives

Page 6: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Relationship to Enterprise Architecture

Page 7: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Relationship to ITILService Management

Page 8: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Service/Contract Model

Page 9: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Programme/Contract Mappings

NRTS

ICT+

ICT+

New (OSS)

NEW - IEP

NEW - IEP

NEW - IEP

ICT+

ICT+

New (OSS)

NTCC/TI2011+TCP/MM IAMS

New - IEP

ICT+ (BI)

Page 10: ICT Strategy From Systems to Services Version 1.0 Version 1.0

Implications for Legacy Systems

• Existing Systems become embedded into new Business Services

• Projects must specify their requirements in terms of Business Services in future procurements

• Need to focus on interfaces and their contracts including dependencies on other HA Services

• Bidders determine the most cost-effective solution

• Legacy Integration (Encapsulation) becomes the responsibility of the Service Providers (SP’s)

• It’s therefore up to SP’s whether to re-use HA Legacy or replace with COTS