case study : tmf frameworx at telkom sa · – lines blurring between oss/bss/network – nexus of...

Case Study :

TMF Frameworx at

Telkom SA

Santa Scheepers

6 Aug 2013

Overview

© Telkom 2011 | Presentation Title | 2

• Introduction

• Shifting vendor landscape

• Cacophony of business requirements

• Role of TMF Frameworx in Telkom

– Business Architecture

– Information Architecture

– Application Architecture

• Pro’s and con’s

• Recent activities and way forward

Introduction


• Accelerated pace of change

– New demands on IT systems

– Lines blurring between OSS/BSS/Network

– Nexus of Social, Mobile, Information, Cloud (Gartner)

• Changing landscape

– Everyone is expanding into every area

Nothing fits their box anymore!

Shifting vendor landscape – Lines blur


• Lines are blurring between

– Network vs IT

– OSS vs BSS (vs ERP)

Business Support Systems (BSS)

Network Support Systems

Operations Support Systems (OSS)

IT responsible

Network responsible

Customer self help portal for network

configuration

Policy controller sell upgrade product if

‘wallet empty’ detected BSS vendors

OSS vendors

Network vendors

ERP vendors

Shifting Vendor landscape - Cloud


• Current situation

– Hardware/software/third-party: complex, unmanageable

– Big names arrogant, expensive

– Buy-outs and mergers

• Enter, the cloud…

– Telkom = Cloud provider

– Vendors working on cloud solutions

– Mobility, BYOD

• Change and uncertainty

– Who will leap frog?

– Who will be the weakest link?

Cacophony of business requirements

• IT inundated with change requests

• Multiple business stakeholders with different focus

– Each trying to keep up with the pace of change

– Every need is urgent, important

– Sometimes not aware of each other

6 6

IT is trapped in the middle

IT has unique perspective (complete picture)

=> Help align & innovate

Never enough time and money to do all

Role of TMF Frameworx


• Describe our world orderly – a common language

– Business and IT both use it

• Hooks to hang required capabilities on

• Hooks to hang system abilities on

– Telkom and external companies use it

• Interpret vendor system descriptions

• Compare apples with apples (RFI/RFP)

• Consultants and new-comers understand it

Business Architecture


• Business architecture for OSS/BSS overhaul

program based on eTOM - with refinements

• Identified shared vs differentiated business

capabilities - eTOM processes

• Heat map - priority processes by organisation

• Business requirements linked to eTOM processes -

modeled in ARIS

• Business Process Improvement Office

– All new processes eTOM based

eTOM

Information Architecture


• Aggregated Business Entities (ABEs) defined -

Telkom refinement of SID

• ABEs : common way to refer to data in processes,

architectures, designs, etc.

• Map source, target and mastership of data in

different applications to common ABE defintions

SID

Application Architecture


• All demands & projects linked to eTOM L3

• All assessments /blue prints map to eTOM, TAM

• OSS/BSS Overhaul architecture TAM based

• Information flows mapped to ABEs

• Application portfolio mapped to TAM

• Links maintained in planningIT (Alfabet)

• Market scan: Vendors asked to map their offerings

to TAM, eTOM (and ITIL)

TAM eTOM SID

TMF Frameworx - Pro’s and Con’s


Works for Does not work for

Linking requirements, benefits, scope, organisational impact

Defining the organisation

Internal processes Customer compliance – their RFPs uses ITIL

Common data language Check vendor coverage

Application data model

Check architectural coverage

Defining your architecture

Systems of record Systems of innovation

TAM

eTOM

SID

TMF Frameworx - Pro’s and Con’s


• The good

– Frameworx is excellent for communication

• The bad

– Lured into trying to architect perfection

(we will be agile, responsive, flexible once we have…)

– Lulled into thinking we are focused on the right thing

(the experts says transforming to this is worth it)

The ugly

– No room for innovation

– Failed projects based on theory

Recent activities and way forward


• Introduce business demand analysis (next slide)

– Communicate in business terms about prioritising

benefits and processes (not CRs!)

– Group and co-ordinate demands accordingly

• Market scan to understand new vendor landscape

– compare apples with apples

Business demand analysis


Log Analyse Architecture assessment

Execute

Business Demand (CR)

Requesting Organisation

Market product

Strategic Alignment

Prioritise

As-is Architecture

Application

Info Flow (ABE)

Benefit

L3 process

…

Priority

Related Demands

Project

To-be Architecture

Release

eTOM

TAM

SID

Conclusion


• Frameworx is a great communication tool

• Used extensively to model

– Business Architecture

– Information Architecture

– Application Architecture

• Make sense of the diverse requirements

• Make sense of the shifting vendor landscape

Thank You!

Santa Scheepers

Snr Specialist – Enterprise Architecture| Information Technology Solutions

e-Mail: [email protected]|

mailto:[email protected]

case study : tmf frameworx at telkom sa · – lines blurring between oss/bss/network – nexus of...

Documents