2015MTN

Enterprise Architecture

2Copyright© 2013 Mobile Telephone Networks. All rights reserved

EA Objectives

• To make available MTN current and future IT Architectures in a consistent common language (TMF TAM / eTOM), process (TOGAF) and tool (ABACUS) so that we are less dependent on individual SME knowledge and have a common reference point with a single version of the truth.

• This available knowledge is then used to:

• Plan future change (and thereby improve time-to-market) and

• Promote standardisation across the group (and thereby also improve time-to-market and reduce costs)

EA Capability Objectives

3Copyright© 2013 Mobile Telephone Networks. All rights reserved

MTN EA Framework

ArchitectureModels

Application

Data & Information

TechnologyInfrastructure

BusinessProcess

Security

Business Domain Framework

Back Office Operations (ERP)

Project Next!

Human Resource

Management

FinanceManagemen

t

Enterprise Asset

Management

Supply Chain

Management

Enterprise Customer Management

Project Orbit (EBU)

CustomerInformation

CustomerProblem

Management

CustomerOrder

CustomerBilling

Retail Customer Management

(BSS)

CustomerInformation

CustomerProblem

Management

CustomerOrder

CustomerBilling

Service & Resource Management

(OSS)

ResourceInformation

ServiceAssurance

OrderFulfillment

Rating & Charging

KeyBenefits

Common Language

Consistent view (Central

Repository)

DesignEfficiency

Standardization(tools, process)

Across all “lines of business”

and operations

OperationsSEA Hub

Ug, Zam, Sw, Rw

MTN GroupSA & Dubai

Nigeria SA RetailEBU

(Cross all)Cameroon

Iran

Benin

South SudanAfganistan BotswanaCongo

BrazzervilleCote d’Ivoire Cyprus

Ghana Guinea-BissauGuinea-Conakry

Syria Yemen Liberia Sudan

4Copyright© 2013 Mobile Telephone Networks. All rights reserved

Engagement – Deliverables

• Setup & Training• ABACUS Training

• TOGAF Training

• ABACUS Software

• Familiarisation of project artefacts

• Develop Business Architecture• Captured Business Organisation

• Captured Key Business Roles

• Captured Business Processes to Levels according to the requirements of the Opco’s

• Captured Key Business Processes to Level 4/5

• Captured Business Strategy

• Defined EA Governance

• Defined Roles & Responsibility – in progress

• Captured Common Language – in progress

Engagement

Deliverables

5Copyright© 2013 Mobile Telephone Networks. All rights reserved

One version of the truth

• Position the Abacus tool and more importantly the information within the tool to be the catalyst to achieving goals.

• This requires a strategic commitment by the team to ensure that they are trained on using the tool, regularly use and gain confidence in using it, are able to validate and maintain the information it contains.

• Use output from the tool for communication and project planning.

• Make output available to OpCo’s and bring the OpCo’s on board as quickly as possible.

• Expand the use of the tool to other business areas.