Case Study : TMF Frameworx at Telkom SA. Santa Scheepers

Transcription

1 Case Study : TMF Frameworx at Telkom SA Santa Scheepers 6 Aug 2013

2 Overview 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 Telkom 2011 Presentation Title 2

3 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! Telkom 2011 Presentation Title 3

4 Shifting vendor landscape Lines blur Lines are blurring between Network vs IT OSS vs BSS (vs ERP) ERP vendors BSS vendors OSS vendors Network vendors Business Support Systems (BSS) Operations Support Systems (OSS) Network Support Systems Policy controller sell upgrade product if wallet IT responsible empty detected Customer self help portal for network configuration Network responsible Telkom 2011 Presentation Title 4

5 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? Telkom 2011 Presentation Title 5

6 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 Never enough time and money to do all IT is trapped in the middle IT has unique perspective (complete picture) => Help align & innovate 6

7 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 Telkom 2011 Presentation Title 7

8 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 Telkom 2011 Presentation Title 8

9 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 Telkom 2011 Presentation Title 9

10 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) etom TAM SID Telkom 2011 Presentation Title 10

11 TMF Frameworx - Pro s and Con s etom SID TAM Works for Linking requirements, benefits, scope, organisational impact Does not work for Defining the organisation Internal processes Customer compliance their RFPs uses ITIL Common data language Check vendor coverage Check architectural coverage Systems of record Application data model Defining your architecture Systems of innovation Telkom 2011 Presentation Title 11

12 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 Telkom 2011 Presentation Title 12

13 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 Telkom 2011 Presentation Title 13

14 Business demand analysis Log Analyse Prioritise Architecture assessment Execute Release Business Demand (CR) As-is Architecture To-be Architecture L3 process etom Market product Requesting Organisation Strategic Alignment Application Info Flow (ABE) TAM SID Related Demands Project Benefit Priority Telkom 2011 Presentation Title 14

15 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 Telkom 2011 Presentation Title 15

16 Thank You! Santa Scheepers Snr Specialist Enterprise Architecture Information Technology Solutions