Discussions

balusuyaswanth

TOGAF_CaseStudy_AngloPlatinum.pdf

Home >Information Systems homework help >Discussions

1Copyright (c) Anglo Platinum Limited 2006

2Copyright (c) Anglo Platinum Limited 2006

Experiences with

Enterprise Architecture Implementation

at Anglo Platinum

Presented by: Steve Rasmussen CTO Anglo Platinum

3Copyright (c) Anglo Platinum Limited 2006

Agenda

• Background – Business – Drivers for change – Architectural concepts

• Approach to implementation – Research and learn from others – Develop a target architecture – Build strong foundations – Respond to short term business

needs – Develop an EA capability

• Toolset selection – ARIS – Utilities

• Early deliverables and business successes – Business Process Models

• Utilities • Documentation

– Information and Data Models – Application Models – Technology Models

• Learnings • The Way Forward

– Governance

4Copyright (c) Anglo Platinum Limited 2006

Overview of Anglo Platinum a member of the Anglo American Group

Anglo Platinum, listed in Johannesburg, London and Brussels, is the world’s leading producer of platinum and platinum group metals, accounting for about 38% of the world’s newly mined production.

2005 2004 US$ 000 US$ 000

Total Assets 5,640.5 5,761.3 Net Sales 3,602.3 2,993.2 Profit after Tax 705.0 386.3

In addition to its wholly owned and joint venture mining and refining operations in South Africa, it participates in joint venture exploration and mining activities in Canada, Russia, Brazil and Zimbabwe. Negotiations have been concluded in the Sishuan Province in China to explore matters of joint interest.

5Copyright (c) Anglo Platinum Limited 2006

Overview of Anglo Platinum - Location

6Copyright (c) Anglo Platinum Limited 2006

Business Drivers for Change

• Drive for accurate, timely, consistent information – “One source of the truth” – Requirement for meaningful performance measurement metrics

• Business focus on certain critical processes – Safety, Health and Environment, Mining, Planning, etc.

• Reduce Business and ICT complexity – Multiple business process in place at different operational units – Various modelling methods, tools and standards across the

enterprise – “Islands of IT” needed to be “reigned in” and subject to

governance

7Copyright (c) Anglo Platinum Limited 2006

Reduce Business and ICT Complexity

Major opportunity to reduce ICT total cost of ownership (TCO) in labour, maintenance, upgrades, licensing and integration

Group ICT will work to actively reduce applications and manage technical infrastructure complexity

• Duplication • Customisation • Solutions focus • Distributed

architecture

Solutions complexity

• Business model (including JV model)

• Inconsistent business processes

• Proliferation of legal entities

A clearer and simplified business model will allow ICT to operate more effectively

Business complexity Process

complexity ICT

complexity

8Copyright (c) Anglo Platinum Limited 2006

Business and ICT Complexity Reduction Opportunities

Reduce infrastructure costs by rationalising servers

More than 400 servers ICT Infrastructure

Reduce the number of applications by between 10% and 20%

Duplication of functionality across

applications

Application Systems

Reduce interfaces through less replication and simpler integration approaches

Several different versions of key KPIsInformation

Consistent definitions of roles across business units with associated performance standards

Multiple definitions of identical

roles Organisation

Standardised process “template” with embedded best practices defined in a single repository

Multiple versions of core processes

Business Processes

Opportunity/ Benchmark Measure of Complexity

Opportunity Area

B us

in es

s D

ri ve

n IT

D ri

ve n

9Copyright (c) Anglo Platinum Limited 2006

Taking into account increasing pressure brought about by demands for reduced Business and ICT complexity, improved governance and the need for close alignment between ICT and Business, Anglo Platinum recognised the need for a structured architecture based on sound business principles.

In 2005, Anglo Platinum adopted Gartner's "good enough“ architecture approach which provides for the delivery of essential business value in the short term and the flexibility to change with business requirements.

This approach contrasts with the bullet proof, "perfect" architecture that is inappropriate to the needs of a relatively straightforward business such as mining and is rarely achieved outside of, for example, the aerospace or financial sectors.

Anglo Platinum View of Architecture

10Copyright (c) Anglo Platinum Limited 2006

Enterprise Architecture Frameworks

Three frameworks contributed to the development of the Anglo Platinum EA framework:

BIDAT

Defines the boundaries of the different architecture domains: • Business • Information • Data • Applications • Technology

Simple, easy to use Easily understood by business Already partially adopted by the company Needed to break out information from data

11Copyright (c) Anglo Platinum Limited 2006

Enterprise Architecture Frameworks

TOGAF

Comprehensive reference for EA method • Input to EA guiding principles • Development of EA roles and skills matrix • Extensive user base

Zachman

Basis for development of the conceptual framework and meta model: • Reference model to check completeness • Comprehensive but not intuitive

12Copyright (c) Anglo Platinum Limited 2006

View of Architecture

To this end, the focus of the Architecture teams, working closely with business, has been on the Business organisation, processes, policies, people, etc. and Information sources, flow and destination of information layers of the architecture as depicted in the EA “cube”.

Enterprise

©© Real IRM SolutionsReal IRM Solutions

A rc

hi te

ct ur

Ex pl

oi t o

re re

se rv

Hu m

an R

es ou

rc es

In te

lle ct

ua l C

ap ita

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

E nv

iro nm

en t

M in

e or

e bo

dy …

EnterpriseEnterprise

©© Real IRM SolutionsReal IRM Solutions

A rc

hi te

ct ur

Ex pl

oi t o

re re

se rv

Hu m

an R

es ou

rc es

In te

lle ct

ua l C

ap ita

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

E nv

iro nm

en t

M in

e or

e bo

dy …

©© Real IRM SolutionsReal IRM Solutions

A rc

hi te

ct ur

es A

rc hi

te ct

ur es

Ex pl

oi t o

re re

se rv

Hu m

an R

es ou

rc es

In te

lle ct

ua l C

ap ita

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

E nv

iro nm

en t

M in

e or

e bo

dy …

13Copyright (c) Anglo Platinum Limited 2006

Agenda

• Background – Business – Drivers for change – Architectural concepts

• Approach to implementation – Research and learn from others – Develop a target architecture – Build strong foundations – Respond to short term business

needs – Develop an EA capability

• Toolset selection – ARIS – Utilities

• Early deliverables and business successes – Business Process Models

• Utilities • Documentation

– Information and Data Models – Application Models – Technology Models – Documentation

• Learnings • The Way Forward

– Governance

14Copyright (c) Anglo Platinum Limited 2006

Difficult to justify purely on cost

Learning from Others -1

You cannot cost justify architecture. Architecture is not an expense. Architecture does not displace any other costs. Architecture is an asset. You can save orders of magnitude more money and time, but you have to invest in Architecture to enable you to do something you otherwise are unable to do, namely: “Alignment,” “Integration,” “Change,” and “Mass Customisation.”

Architecture is an Information-Age idea. “Cost Justification” was an Industrial Age idea.

John Zachman 2001

15Copyright (c) Anglo Platinum Limited 2006

Importance of research and learning from others

• Not a “silver bullet” for all business requirements • Focus on short to mid term business benefits • Use consulting resource for manpower, previous experience and to fast track deliverables

• Develop an in-house architectural support capability • Create a strong architectural governance supporting corporate governance

• Architecture is never “completed” as business and IT continually change

• EA is not a “high profile” occupation. Often advantageous to remain in the background!

Learning from Others - 2

16Copyright (c) Anglo Platinum Limited 2006

• ICT focus and investment in recent years led to relatively well developed applications and technology architectures but with few perceived benefits to business

• Business structure and processes had evolved over a longer period and on a decentralised basis

• Alignment between ICT and business was sporadic

• Different architectural domains were, and may remain, at varying levels of maturity

Develop a Target Architecture: Vision

17Copyright (c) Anglo Platinum Limited 2006

Develop a Target Architecture: Maturity Levels

Leveraging the EA to improve business benefit

Optimised5

Completing the EAManaged4

Developing the EA by applying a consistent process

Defined3

Building the EA management foundation

Repeatable2

Creating EA AwarenessInitial1

EA Capability MaturitySEI CMM *Level

* SEI CMM: Software Engineering Institute Capability Maturity Model

18Copyright (c) Anglo Platinum Limited 2006

Develop a Target Architecture: Current and target

5 Tools

People

ContentProcess

Products/Services

Current Target

4 = Managed

Initial

19Copyright (c) Anglo Platinum Limited 2006

Build strong foundations for target architectures

• Develop easily understood standards, guidelines and principles

• Establish conceptual framework and meta model

• Engage senior management in development of high level processes

• Deliver appropriate training

Build Strong Foundations

20Copyright (c) Anglo Platinum Limited 2006

EA Principle Template

Enterprise

A rc

hi te

ct ur

Ex pl

oi t o

re re

se rv

Hu m

an R

es ou

rc es

In te

lle ctu

al Ca

pi ta

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

En vir

on me

M in

e or

e bo

dy …

EnterpriseEnterprise

A rc

hi te

ct ur

Ex pl

oi t o

re re

se rv

Hu m

an R

es ou

rc es

In te

lle ctu

al Ca

pi ta

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

En vir

on me

M in

e or

e bo

dy …

A rc

hi te

ct ur

es A

rc hi

te ct

ur es

Ex pl

oi t o

re re

se rv

Hu m

an R

es ou

rc es

In te

lle ctu

al Ca

pi ta

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

En vir

on me

M in

e or

e bo

dy …

. One line principle Principle

Supporting rationale

Rationale

1. Implications resulting from the principle

Implications

Architecture Architecture Design Design ManagementManagement

21Copyright (c) Anglo Platinum Limited 2006

One of the key EA principles adopted

Enterprise

A rc

hi te

ct ur

Ex pl

oit o

re re

se rv

Hu m

an R

es ou

rc es

Int ell

ec tu

al Ca

pit al

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

En vir

on me

M in

e or

e bo

dy …

EnterpriseEnterprise

A rc

hi te

ct ur

Ex pl

oit o

re re

se rv

Hu m

an R

es ou

rc es

Int ell

ec tu

al Ca

pit al

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

En vir

on me

M in

e or

e bo

dy …

A rc

hi te

ct ur

es A

rc hi

te ct

ur es

Ex pl

oit o

re re

se rv

Hu m

an R

es ou

rc es

Int ell

ec tu

al Ca

pit al

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture En te

rp ris

e A rc

hi tec

tu re

Ca pa

bi lit

(C en

tre of

E xc

ell en

ce )

P eo

pl e

C on

te nt

P ro

ce ss

To ol

P ro

du ct

s an

d S

er vi

ce s

Sa fet

y, He

alt h,

En vir

on me

M in

e or

e bo

dy …

. Enterprise Architecture is driven by business and adds value. Principle

All EA initiatives should be in support of the business objectives and strategic initiatives, as is the case with any other ICT project. Business alignment with defined business outcomes will focus EA initiatives and prevent “analysis paralysis”.

Rationale

1. Bring EA into the mainstream of the business increasing business alignment through improved business focus and communication.

2. Transforming EA from a service to a value-adding business solution. 3. Strategic business objectives are incorporated into business and solutions

architecture. Link the EA strategy to the ICT strategy with a focus on practical execution.

4. Require the business to define their EA needs and require ICT to orchestrate services through a methodology of rigorous relationship management.

5. ICT projects that link to strategic business objectives, processes and information needs will likely receive funding.

6. Programme and project management disciplines should be applied. 7. Measure and manage the amount spent on and the value received from EA. 8. Clarify business strategies and the role of EA in achieving them. 9. EA will only be developed to the appropriate level of detail based on the

business objectives.

Implications

Architecture Architecture Design Design ManagementManagement

22Copyright (c) Anglo Platinum Limited 2006

Process Levelling Guidelines

Purpose

Guidelines

Level Detail Consistency Process detail at the same level must be consistent.

After every level is built, do a levelling exercise to check if each object at a level is relatively equivalent to the others at the same level.

Same level of detail?

Process Boundaries

Decompose into….

Start End

In- between

A true process has a clear start and end.

What is a Process Level? A process level provides a view into a business process at a specified level of detail

Process levels are organised hierarchically – the lower the process level the more detailed it would be

Process vs. Function Document business processes that flow through horizontally and affect all vertical departments.

Department (Org Unit) (Function)

Refer to Business Architecture principle:

Department (Org Unit) (Function)

Process

Model the business using a process approach, whilst retaining functional accountability for the activities. Principle

The business is still organised along functional lines, although the activities are modelled with a end-to- end process approach. This hybrid approach drives process optimisation and measurement, but maintains the benefits of functional management based on disciplines.

Rationale

Architecture Architecture Design Design ManagementManagement

Process Model Levels

Contextual

Cross Functional

Task

If you have too many levels the clarity of the hierarchical approach may be lost in the complexity of layers and levels.

Level 0 Level 0

Level 1 Level 1

Level 2 Level 2

Level 3Level 3

Level 4 Level 4

Level 5 Level 5

Activity

Work Step

Value Chain

Sub-process

Process

Enterprise Process

Process

Implementation

Operational

VIEW

Process Model Level - Definitions Level DefinitionLevel Name

Level 5

Level 4

Level 3

Level 2

Level 1

Level 0

To provide a step-by-step guide to each activity as a work instruction or taskWork Step

To provide an operational view of each sub-process with the role accountability for each activity, as well as any inputs or outputs.

Activity

To depict the implementation of the previous level to show how the processes are executed.Sub-Process

To provide a business process view of the business that can be assigned to a process owner and that can be measured.

Process

To provide a view of the cross-functional value chains of each of the enterprise processes. Each value chain component has a profound impact on achieving a strategic business objective.

Value Chain

To provide the context of the Anglo Platinum business model aligned to the strategic objectives.Enterprise Process

Level 5

Level 4

Level 3

Level 2

Level 1

Level 0

To provide a step-by-step guide to each activity as a work instruction or taskWork Step

To provide an operational view of each sub-process with the role accountability for each activity, as well as any inputs or outputs.

Activity

To depict the implementation of the previous level to show how the processes are executed.Sub-Process

To provide a business process view of the business that can be assigned to a process owner and that can be measured.

Process

To provide a view of the cross-functional value chains of each of the enterprise processes. Each value chain component has a profound impact on achieving a strategic business objective.

Value Chain

To provide the context of the Anglo Platinum business model aligned to the strategic objectives.Enterprise Process

Fo cu

s Fo

cu s

Purpose of Process Model Levelling Process level identification and defining is important to

ensure consistency of detail at each level structure models consistently across modelling projects ensure models used for analysis purposes are at the same level ensure that levels are not randomly added or omitted

23Copyright (c) Anglo Platinum Limited 2006

Build strong foundations for target architectures

• Develop easily understood standards, guidelines and principles

• Establish conceptual framework and meta model

• Engage senior management in development of high level processes

• Deliver appropriate training

Build Strong Foundations

Enterprise Architecture Summary Conceptual Framework

Version 1.03

M ay 2005

2005

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Work Step (Level 5)

Process Models

Wide Area Network

Site Network

Local Area Network

Information Applications

Information Application

Modules

Information/Network

Business Architecture

Information Architecture

Data Architecture

Application Architecture Technology Architecture

Product List

Material List

Product Models

Physical Location Hierarchy

Organisation Unit Hierarchy

Job List

Business Role List

Position ListPeople List

System Role List

Organisation Models

Risk List

Control List

Risk and Controls Models

Strategic Objectives List

Business Principles List

Strategic Models

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Product List Material List

Process/Product

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Organisation Unit Hierarchy

Business Role List

Position List

Physical Location Hierarchy

Process/Organisation

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Risk ListControl List

Process/Risk

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Strategic Objectives List

Business Principles List

Process/Strategic Business Cycles Hierarchy

Cycle Models Enterprise

Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Business Cycles Hierarchy

Process/Cycle

Document Hierarchy

Information Hierarchy Metrics Hierarchy

Information Models

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Document Hierarchy

Information Hierarchy

Metrics Hierarchy

Information/Process

Position List

Information Hierarchy

Metrics Hierarchy

Information/Organisation

Logical Databases

Data Subject Areas

Entities

Information Hierarchy

Tables

Information/Data

Information Hierarchy

Applications

Application Modules

Application Interfaces

Information/Application Source

Information Hierarchy

Metrics Hierarchy

Applications

Application Modules

Application Interfaces

Information/Application Deployment

Logical Databases

Data Subject Areas

Entities

Tables

Data Models

Logical Databases

Data Subject Areas

Entities

Position List

Data/Organisation

Server List Logical

Databases

Data/Network

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Logical Databases

Data Subject Areas

Entities

Tables

Data/Process

Applications

Application Modules

Application Interfaces

Application Hierarchy

Application Models

Position ListApplications

Application Modules

Application Interfaces

Application/Organisation

System Role List

Applications

Application Modules

Application Interfaces

Application/System Role

Server List

Applications

Application Modules

Application Interfaces

Application/Network

Enterprise Process (Level 0)

Value Chain (Level 1)

Process (Level 2)

Sub-process (Level 3)

Activity (Level 4)

Task (Level 5)

Applications

Application Modules

Application Interfaces

Application/Process

Applications

Application Modules

Application Interfaces

Logical Databases

Data Subject Areas

Entities

Tables

Application/Data

Server List Infrastructure Applications

Hierarchy

Infrastructure Applications

Technology Models

Organisation Unit Hierarchy

Position List

Physical Location Hierarchy

Server List

Network/Organisation

Server List Infrastructure Applications

Network/Infrastructure Applications

Network Models System Software Models

Application Models Data Models

Document Models Infor mation Models

Cycle Models Strategic Models

Risks and Controls Models Organisation Models

Product Models Process Models

Legend

Network Models System Software Models

Application Models Data Models

Document Models Infor mation Models

Cycle Models Strategic Models

Risks and Controls Models Organisation Models

Product Models Process Models

Legend

Organisational Unit Type Model (Organizational Chart) To provide a hierarchical view of the various types organisational units.

Organisational Unit Type 1.1

Organizational Unit Type 1.2

Organizational Unit Type 1

Organisation Model (Organizational Chart) To provide a hierarchical view of the organisational units, positions and the jobs of the whole organisation.

Organisational Unit A

Organisational Unit A.1

Job 2

Cost Center A

Position A.1 Job 3

Organisational Unit A.2

Job 4Position A.2

Position A.0 Cost Centre An accounting Cost Centre (sourced from SAP). Object Type: Organizational Unit Symbol Type: Cost Center Attributes: *Name: Name of the Cost Centre

Organisational Unit An organisational unit, e.g. company, division, Operational unit, business unit and department. Object Type: Organizational Unit Symbol Type: Organizational Unit Attributes: *Name: Name of the Organisational

Unit *Identifier: SAP Identifier *Description: Description of the

Organisational Unit *Name ext. system (alias): SAP Name

Job A generic position to group positions (sourced from SAP). Object Type: Organizational Unit Type Symbol Type: Position Type Attributes: *Name: Name of the Job *Identifier: SAP Identifier *Description: Description of Job

Job List (Organizational Chart) To provide a list of all jobs.

Job 2Job 1 Job 3

Business Role Represents the part that must be played in the execution of similar activities Object Type: Person Type Symbol Type: Position Description Attributes: *Name: Name of the Business Role *Description: Description of the Business

Role

Location A geographical location/area where business operations are conducted. Object Type: Location Symbol Type: Location Attributes: *Name: Name of the Location *Location Type: Not selected – this is a location

and not a location type

Location Model (Organizational Chart) To provide a hierarchical view of the geographical locations where business operations are conducted.

Location A.1

Location A.1.i Location A.1.ii

Location Type Model (Organizational Chart) To provide a hierarchical view of the geographical location types where business operations are conducted.

Locati on Type A.1

Location Type A.1.2

Location Type A.1.1

Location Type A geographical location type where business operations are conducted. Object Type: Location Symbol Type: Location Attributes: *Name: Name of the Location Type *Location Type: Selected – this is a location

type

Business Role List (Organizational Chart) To provide a list of all business roles.

Business Role 1

Business Role 2

Business Role 3

Business Role Allocation (Organizational Chart) Allocate a business role to jobs and/or positions.

Business Role 1

Job 1

Position A.2

Location Type Assignment Model (Organizational Chart) Assign all the locations to their respective location types.

Location Type A.1.1

Location A.1.i

Organisational Unit Type A generic type of organisational unit within the business Object Type: Organizational unit type Symbol Type: Organizational unit type Attributes: *Name: Name of the Organisational Unit Type Description: Description of the Organisational Unit type

Organisational Unit Type Assignment Model (Organizational Chart) Assign all the Organizational Units to their respective Organisational Unit Types.

Organisational Unit Type 1.1

Organizational Unit Type 1.2

Organisational Unit Type 1

Position Position that an employee is appointed in (sourced from SAP). Object Type: Position Symbol Type: Position Attributes: *Name: Name of the Position *Identifier: SAP Identifier *Employee: Person employed in position

Product List (Product Tree) Presents the products of the organisation in a hierarchical tree.

Product A

Product A.1 Product A.2

Material and Equipment List (Material diagram) Represents Equipment and Material used within the business.

Material Type 1 Material Type 2

Equipment Type 1

Equipment Type 2

Service Detail (Product/Service Exchange Diagram) To provide the detail surrounding the delivery of a specific service category

Location A.1.i Service Category1.1

Application 1

Business Role 1

Organisational Unit A.1

RAIDE IT Service 1.1.B.i

IT Service 1.1.B.ii

RAIDE

Infrastructure Application 1

Strategic Objectives Model (Objective Diagram) Presents the strategic objectives of the organisation in a hierarchical tree.

Strategic Objecti ve 1.2

Strategic Objective 1.2.1

Strtategic Objective 1.2.2

Strategic Objective Strategic objective of the organisation. Object Type: Objective Symbol Type: Objective Attributes: *Name: Name of the Strategic Objective Description: Description of the Strategic

Objective

Product Product of the organisation, e.g. Platinum, Gold, etc. Object Type: Product/Service Symbol Type: Product Attributes: *Name: Name of the Product Description: Description of the Product

Service Level Agreements (Product/Service Tree) To provide a view of the different service providers and the SLA contract agreements drawn up for each provide.

Service Level Agreement 3

Service Level Agreement 2

Organisational Unit A.1

Organisational Unit A.2

Organisational Unit B

Service Level Agreement 1

Service Level Agreement A Service Level Agreement Contract between the business and an organisational unit Object Type: Product/Service Symbol Type: Service Attributes: *Name: Name of the SLA Identifier: An identifier for the SLA *Service Type: “SLA”

SLA Structure (Product/Service Tree) To provide hierarchical breakdown of the SLA into its different schedules

Service Level Agreement 1

Service Category 1.3

Service Category 1.2

Service Category 1.1

Service Category A category into which the services is divided Object Type: Product/Service Symbol Type: Service Attributes: *Name: Name of the Schedule Identifier: An identifier for the Service Category Description: A description of the Service Category

Service Breakdown (Product/Service Tree) To provide hierarchical breakdown of the SLA Services

Service Category 1.1

Service 1.1.A

Service 1.1.B

Service 1.1.A.i Service 1.1.A.ii

Service 1.1.B.i

Service A service that forms part of a Service Category Object Type: Product/Service Symbol Type: Service Attributes: *Name: Name of the Service *Identifier: A unique identifier for the Service Description: A description of the service Service 1.1.A

Measurement 2.1.B.i

Measurement 2.1.B.ii

Service Measurements (Product Allocation Diagram) To depict which measurements are used to evaluate service delivery.

Information Technology Services (Product/Service Tree) To provide a view of the different Information Technology Services that are provided to the business

IT Service Group 1

IT Service Group 2

IT Service Group 3

IT Service Group Structure (Product/Service Tree) To provide hierarchical breakdown of the Service Group into Service Categories

IT Service Group 1

IT Service Category 1.1

IT Service Category 1.2

IT Service Breakdown (Product/Service Tree) To provide hierarchical breakdown of the IT Services

IT Service Category 1.1

IT Service 1.1.B

IT Service 1.1.A

IT Service 1.1.A.i

IT Service 1.1.B.i IT Service 1.1.B.ii

Material/Equipment Represents the material and equipment that is used within the business Object Type: Material type Symbol Type: Material type Attributes: *Name: Name of the

Material/Equipment type Description: Description of the

Material/Equipment type

Business Risks (Business Controls diagram) Represents various risks faced by the business.

Risk 2 Risk 1

Risk A specific type of risk in the organisation Object Type: Risk Symbol Type: Risk Attributes: *Name: Name of the Risk Description: Description of the Risk

IT Service Group A specific service group provided to the business by Information Technology Object Type: Product/Service Symbol Type: Information Service Attributes: *Name: Name of IT Service Group Identifier: An identifier for the IT Service Group

IT Service A service that forms part of a IT Service Category Object Type: Product/Service Symbol Type: Information Service Attributes: *Name: Name of the IT Service *Identifier: A unique identifier for the IT Service Description: A description of the IT Service

IT Service Category A category into which the IT Services group is divided Object Type: Product/Service Symbol Type: Information Service Attributes: *Name: Name of the Schedule Identifier: An identifier for the IT Service Category Description: A description of the IT Service Category

Infrastructure Application Classes Model (Application System Type Diagram) Strategically summarises the infrastructure application portfolio on the highest level.

Infastructure App Class 1

Infra structure App Class 2

I nfrastructure App Class 3

Infra structure Appli cations

Server Detail Model (Access Diagram (Physical) Depicts the configuration of the server in terms of infrastructure applications.

Server A.1.i.a

Infrastructure Application 1

Information Store 4

Logical Database 1

Application 1

Application 1.1

App 1/App 2 Interface

Infrastructure Application List (Application System Type Diagram) List the infrastructure applications for the organisation

Infrastructure Application 1

Infra structure Appl ication 2

Infrastructure Application Class List Model (Application System Type Diagram) List the infrastructure applications that belongs to an infrastructure application class.

Infastructure App Class 1

Infrastructure Application 1

Infrastructure Application 2

Infrastructure Application Class Represents a technology application class of the infrastructure application portfolio, e.g. network, DBMS. Object Type: Application System Class Symbol Type: Application System Class Attributes: *Name: Name of the Infrastructure Application

Class *Description: Description of the Infrastructure

Application Class

Infrastructure Application Any infrastructure application package, e.g. software development environment, operating system, middleware, office automation, network. Object Type: Application System Type Symbol Type: IT Systems Attributes: *Name: Name of the Infrastructure Application *Description: Description of the Infrastructure

Application

Server List Model (Network Diagram) List of servers.

Server A.1. i.a

Server A.1.i.b

Server Types (Network Diagram) List of server types.

Server Type 1

Server Type 2

Server Type A generic server description that is used to classify logical servers. Object Type: Hardware Component Type Symbol Type: Hardware Component Type Attributes: *Name: Name of the Server Type *Description: Description of the Server Type

Server Deployment Model (Network Diagram) List the logical servers per location, as well as the server types of each server.

Server A.1.i.a Server Type 1

Location A.1.i

Server A.1.i.b Server Type 2

Server A logical server hosting application, databases or office automation components. Object Type: Hardware Component Symbol Type: Hardware Component Attributes: *Name: Name of the Server *Description: Description of the Server Server Environment: Environment the server is used in Server Support: Type of support the server receives

Application Module Info/Data Usage Model (Access Diagram) List all the data and information elements accessed by the application module.

App 1.1.c Characteristic 1.1.b

Metric 1.1.a

Dimension 1.1

Fact 1.1

Entity 1.A

Attribute 1.1.b

Attribute 1.1.a

Report 2

Application 1.1

App 1.1.a App 1.1.b App 1.1.c

Application Modules Model (Application System Type Diagram) Decomposes an application functionally into modules.

Application Ownership Model (Access Diagram) Indicate the business and technical owner of an application.

Application 1

Position A.2

Position 1

Application Classes Model (Application System Type Diagram) Strategically summarises the application portfolio on the highest level.

Applicati on Class 1

Application Class 1.1

Application Class 1.2

Application Class 1.1.1

Applicati on Cla ss 1.1.2

Application Class Represents a business functional class of the application portfolio. Object Type: Application System Class Symbol Type: Application System Class Attributes: *Name: Name of the Application Class *Description: Description of the Application Class

Application Class List Model (Application System Type Diagram) List the business applications that belongs to an application class.

Application Cl ass 1.1.1

Application 1 Application 2

Application List Model (Application System Type Diagram) List all the major applications within the organisation.

Application 1 Application 2 Application 3

Application Decomposition Model (Application System Type Diagram) Decomposes a major application into sub-applications.

Appl ication 1

Application 1.1 Application 1.2 Application 1.3

Application Module A module represents a logical subset of the functionality presented by an application. The lowest level module

would be a function of the application, e.g. screen or report. Object Type: Module Type Symbol Type: Module Type Attributes: *Name: Name of the Application Module *Description: Description of the Application Module

Application Interfaces Model (Application System Type Diagram) List all the interfaces between applications.

Appl ication 1 Application 2 Appli cation 3 App 1/App 2

Interface App 2/App 3

Interface

App 1/App 3 Interface

Application Databases Model (Access Diagram) List all the databases accessed by the application.

Application 1 Logical

Database 1

Application Technology Model (Access Diagram) List all the minimum technology requirements to deploy the business application.

Server Type 1

I nfrastructure Application 1

I nfrastructure Application 2

Application 1

Application Interface An application interface represents all the connectivity between two applications. Object Type: Application System Type Symbol Type: Application System Type Attributes: *Name: Name of the Application Interface *Description: Description of the Application Interface

Application 1

Application 3

Application Dependencies Model (Application System Type Diagram) List all the dependencies between applications

Application Dependency Indicates the type of dependency between applications. Connection Type: “is predecessor of” Attributes: *Application Dependency: The type of dependency

Application An application is an application package or custom- developed system supporting a business process. Object Type: Application System Type Symbol Type: Application System Type Attributes: *Name: Name of the Application *Description: Description of the Application Operating System: The operating system the application runs on Application Life Cycle: The life cycle stage the application is currently in. Historic Cost of Ownership: Rand value of the application’s cost of ownership Estimated Cost of Application: The estimated cost of new applications Retirement Date: Date application is to be retired Data Migrated: Indicate if a retired application’s data has been migrated. Migrated Data Location: The location of the migrated data. Implementation Date: Date application was/is to be implemented.

Level 3 Sub-process Detail Model Level 4 Activity Detail Model Level 5 Task Detail Model (Function Allocation Diagram) To further explain the detail of the Sub-process/Task/Activity such as ownership.

L3 Sub-processB1-2b

Product A.1

Version 1.0

App 1.1.a

Business Role 1RAIDE

Service 1.1.A.i

Location Type A.1.2

Location A.1.i

Organisatio nal Unit A.1

RAIDE

Application 1

Job 1 RAIDEEquipment

Type 2

Reference 1

Report 2

Document 1

Position A.2

Risk 1

Organisatio nal Unit Type 1.1

Variant Area 1

RAIDE

Logical Database 1

Level 4 Activity Model (eEPC) To provide an operational view of each sub-process with the role accountability for each activity, as well as any inputs or outputs.

Event 1

L4 Activity B1-2b.i

L4 ActivityB1-2b.ii

Event 3 Event 5

Outcome 1Outcome 2

L4 ActivityB1-2b.iii L4 Activity B1-2b.iv

L3 Sub-processB1-2a

L3 Sub-processB1-2c

Event 4

Level 5 Task Model (eEPC) To provide a step-by-step guide to each activity as a work instruction or task.

L5 Task B1-2b.ii.a

L4 ActivityB1-2b.i

L5 Task B1-2b.ii.b

Event 3 Event 5

Outcome 1Outcome 2

L4 ActivityB1-2b.iii L4 Activity B1-2b.iv

Event 2

Level 2 Process Detail Model (Function Allocation Diagram) To further explain the detail of the Process such as ownership.

L2 ProcessB1-2

Measurement Type 2.1.B

Product A.1

Strategic Objective 1.2.i

Position A.2 D

Application 1

Risk 1

Level 1 Value Chain Detail Model (Function Allocation Diagram) To further explain the detail of the Value Chain such as ownership.

L1 Value Chain B1 Position A.0Risk 1 D

Level 0 Enterprise Process Model (Value Added Chain Diagram) To provide the context of the Anglo Platinum business model aligned to the strategic objectives.

Enterprise Process C

Enterprise Process A

Enterprise Process B

Level 1 Value Chain Model (Value Added Chain Diagram) To provide a view of the cross-functional value chains of each of the enterprise processes. Each value chain component has a profound impact on achieving a strategic business objective.

Value Chain B1

Value Chain B2

Level 2 Process Model (Value Added Chain Diagram) To provide a business process view of the business that can be assigned to a process owner and that can be measured.

Process B1-1

Process B1-2

Process B1-3

Event Represents a triggering or resulting state. Object Type: Event Symbol: Event Attributes: *Name: Name of the Event

Rule Outcome Indicates different outcomes. Connection Type: “leads to” Attributes: *Connection Role: Description of the outcome.

Value Chain Ownership Indicates the position that is the owner of the value chain. Connection Type: “contributes to” Attributes: *Connection Role: D(ecide)

Strategic Objective Support Indicates whether the process supports the strategic objective directly on indirectly. Connection Type: “supports” Attributes: *Strategic Objective Direct Support: Check for direct support

and uncheck for indirect support

Enterprise Process (Level 0) Represents the business at an enterprise level. Object Type: Function Symbol Type: Value Added Chain Attributes: *Name: Name of the Enterprise Process

(verb noun) *Description: Description of the Enterprise

Process *Process Level: Indicate the process level. Choose

from L0;L1;L2;L3;L4;L5 *Value Chain From: The starting point of the Enterprise

Process *Value Chain From: The final product of the Enterprise

Process

Value Chain (Level 1) A Value Chain is cross-functional and has a profound impact

on achieving strategic objectives. Object Type: Function Symbol Type: Value Added Chain Attributes: *Name: Name of the Value Chain (verb noun) *Process Level: Indicate the process level. Choose from

L0;L1;L2;L3;L4;L5 *Description: Description of the Value Chain *Value Chain From: The starting point of the Value Chain *Value Chain To: The final product of the Value Chain

Process (Level 2) A Process is a series of steps that receives inputs, adds value and transforms the inputs into outputs. Object Type: Function Symbol Type: Value Chain Attributes: *Name: Name of the Process (verb noun) *Description: Description of the Process *Process Level: Indicate the process level. Choose from

L0;L1;L2;L3;L4;L5

Level 3 Sub-process Model (Value Added Chain Diagram) To depict the implementation of the previous level reflecting how the processes are executed.

Sub-process B1-2a

Sub-process B1-2b

Sub-process B1-2c

Process Ownership Indicates the position that is the owner of the process. Connection Type: “contributes to” Attributes: *Connection Role: D(ecide)

Sub-process (Level 3) A Sub-Process is a grouping of logically related Activities. Object Type: Function Symbol Type: Value Chain Attributes: Identifier: The service’s ID & Sub-service sequence number

e.g. “EDS.F3.2.1” – only if this Sub-process is linked to a SLA

*Name: Name of the Sub-process (verb noun) *Description: Description of the Sub-process *Process Level: Indicate the process level. Choose from

L0;L1;L2;L3;L4;L5 SME: Name of Subject Matter Expert Synonyms: Synonyms to Process name Version: Version of the Sub-process

Task (Level 5) A single action that is executed as part of an Activity. Object Type: Function Symbol Type: Function Attributes: *Name: Name of the Task *Process Level: Indicate the process level.

Choose from L1; L2; L3; L4; L5 *Description: Description of the Task Source: Reference to documentation that

was used to document process Online central: Tick this box if this task is

supported by an application Auto central: Tick this box if this task is fully

automated by a batch application Manually: Tick this box if the task is

performed with no application support

Frequency: How often the task is performed

Sub-process RAIDE Indicates the participation of a position/job/role in a sub-process. Connection Type: “contributes to” Attributes: *Connection Role: R(ecommend), I(nput), A(gree),

D(ecide), E(xecute) – or a combination thereof e.g. RA, DE

Frequency: The frequency of the participation

Activity (Level 4) An Activity is a single (manual/automated) action that is executed in a specific sequence. Object Type: Function Symbol Type: Function Attributes: Identifier: The Sub-service’s ID & the

activity’s sequence number e.g. “EDS.F3.2.1.5” – if Activity is linked to SLA

*Name: Name of the Activity (verb noun) *Process Level: Indicate the process level. Choose

from L1; L2; L3; L4; L5 *Description: Description of the Activity Source: Reference to documentation that

was used to document process Online central: Tick this box if this activity is

supported by an application Auto central: Tick this box if this activity is fully

automated by a batch application Manually: Tick this box if the activity is

performed with no application support

Base Service Type: Select what type of service the

activity performs - SLA Base Service Comments: Additional comments surrounding

the base service – SLA Frequency: How often the activity is performed Constraints: Describe constraints to the activity Variations: Describe any variances in how the

activity is performed.

Version Information Indicates the version information for the specific document. Connection Type: “lies on” Attributes: *Version Date: Date the particular version was

published *Revised Item:Changes made to the document *Reason: Reasons for the changes *Reviewer: Person who made the changes

Please refer to the Meta-model standards documentation for minor differences between the L3 – L5 Detail Models

Variant Area A business area where the process varies from the norm. Object Type: Functional Cluster Symbol Type: Functional Block Attributes: *Name: Name of the Variant Area

Information Hierarchy (Knowledge Structure Diagram) A depiction of the categories that make up the Information Classes

Information Category A

Information Class 1.2

Information Category B

Document 1

Information Store 1

Document 2

Report 1

Information Category B

Information Category A

Information Category List (Knowledge Structure Diagram) A list of the various information categories use in the business.

Scorecard 1

Position 1 Position A.2

Scorecard 1.1

Scorecards Owners (Access diagram) A representation of the owner for each scorecard

Information Element Source Function allocation diagram) Depicts the various sources of the information element.

Characteristic 1.1.a

Logical Database 1

Metric 1.1.b

Characteristic 1.1.c

Entity 1.A

Attribute 1.1.a

Attribute 1.1.b

Application 1.1

App 1.1.a

Metric 1.1.a Document 3

Characteristic 1.1.a

Calculation Report 4

Measurement 2.1.B.i

Measurement 2.1.B.ii

Measurement 2.1.B.iii

Measurements (DW structure) To provide a view of the various instances measurements of a certain measurement type

Measurement Strategic Objectives (PCD) A representation of the measurements that support strategic objectives.

Objective Data F. .

Measurement Type 2.1.A

Measurement Type 2.1.B

Strategic Objective 1.2.1

Document 1 Document 2

Document 3 Document 4

Document List (Knowledge structure diagram) A list of the documents used within the business

Measurement Calculation

1.1.B

Application 1.1

Position A.1

Measurement 2.1.B.i

Logical Database 1

Measurement 2.1.B.ii

Position 1

Position A.2

Position A.3 Entity 1.1

Attribute 1.1.a

App 1.1.a

Document 2

Characteristic 1.1.a

Metric 1.1.a

Measurement Source (Function allocation diagram) Depicts the various sources of the information element.

Measurement Type 2.1.A

Measurement Type 2.1.B

Measurement Type 2.1.A.i

Measurement Type 2.1.A.ii

Measurement Perspective 2

Measurement Type Hierarchy (DW structure) To provide a logical view of the measurement types hierarchy used for process management.

Information Element: Metric Depicts a measurable attribute of the fact Symbol Type: Key Figure Object Type: ERM attribute Attributes: *Name: Name of the information element Description: A description of the information element

Scorecard Depicts a scorecard used within the business Symbol Type: Communication Structure Object Type: Cluster/Data model Attributes: *Name: Name of the Scorecard Description: A logical business-focused description of the scorecard.

Measurement Perspective 1

Measurement Perspective 2

Measurement Perspective 3

Measurement Perspective 4

Measurement Perspectives (DW structure) A classification of the measurements used by Anglo Platinum into various groups

Report List (Knowledge structure diagram) A list of the reports used within the business

Report 1 Report 2

Report 3 Report 4

Dimension Depicts a business dimension, e.g. organisation, time, or product. Symbol Type: Dimension Object Type: Cluster/Data model Attributes: *Name: Name of the dimension Description: A description of the dimension

Fact Depicts a collection of key metrics, e.g. tons mined. Symbol Type: Fact table Object Type: Cluster/Data model Attributes: *Name: Name of the fact table Description: A description of the fact

Information Class Depicts a grouping of information Symbol Type: Knowledge category Object Type: Knowledge category Attributes: *Name: Name of the Information Class Description: A logical business-focused description of the Information Class

Information Category Depicts a grouping of information Symbol Type: Documented knowledge Object Type: Documented knowledge Attributes: *Name: Name of the Information Category Description: A logical business-focused description of the Information Category

Logical Information Model (DW structure) A dimensional depiction of an information class

Dimension 1.1

Dimension 1.2

Dimension 1.3

Dimension 1.4

Fact 1.1

Fact Description (DW structure) Depicts the information elements that make up a DW fact.

Fact 1.1

Metric 1.1.a

Metric 1.1.b

Dimension Description (DW structure) Depicts the information elements that make up a DW dimension.

Dimension 1.1

Characteristic 1.1.a

Characteristic 1.1.b

Characteristic 1.1.c

Report Depicts a reports used within the business Symbol Type: Electronic Document Object Type: Information carrier Attributes: *Name: Name of the Report

Information Store Depicts a logical information store Symbol Type: Info cube Object Type: Cluster/Data model Attributes: *Name: Name of the Information store

Information Element: Characteristic Depicts a descriptive attribute of the dimension. Symbol Type: Characteristic Object Type: ERM attribute Attributes: *Name: Name of the information element Description: A description of the information element

Information Store List (DW structure) A list of the information stores

Information Store 1

Information Store 2

Information Store 3

Information Store 4

Scorecards (DW structure) To show a hierarchical breakdown of the scorecards used within the business

Scorecard 1

Scorecard 1.1 Scorecard 1.2

Scorecard Measurements (DW structure) A representation of the measurements that make up a particular scorecard.

Measurement 2.1.B.ii

Measurement 2.1.B.i

Scorecard 1

Information Classes (Knowledge Structure Diagram) A depiction of the categories of information used in the business

Information Class 1

Information Class 1.1

Information Class 1.2

Measurement Type Depicts a measurement type Symbol Type: Key figure Object Type: Entity type Attributes: *Name: Name of the measurement Identifier: An identifier for the measurement Description: A description of the measurement Frequency: How often the measurement is used Measurement Type: Checked (True) Measurement Importance: Select a level FSR Availability Rating: Select a rating

Measurement Perspective Depicts a logical grouping of measurements into the Scorecard perspectives. Symbol Type: Info Cube Object Type: Cluster/Data model Attributes: *Name: Name of the measurement perspective Identifier: An identifier for the perspective Description: A description of the perspective

Term A term/concept that needs clarification in terms of its meaning. Object Type: Technical Term Symbol: Technical Term Attributes: *Name: Name of the term *Description: The explanation/definition of the term

Abbreviations List (Technical Terms Model ) A list of all the abbreviations

Abbreviation 1

Abbreviation 2

Abbreviation 3

Term 1

Term 2

Terms List (Technical Terms Model ) A list of all the terms

Document Depicts a document used within the business Symbol Type: Document Object Type: Information carrier Attributes: *Name: Name of the Document Description: A description of the document Document Type: The type of document. Link1: The URL link for the document

Abbreviation A shortened form of a word or words. Object Type: Technical Term Symbol: Technical Term Attributes: *Name: The abbreviation *Full name: The full name

Measurement Depicts a measurement used within the business Symbol Type: Characteristic Object Type: Entity type Attributes: *Name: Name of the measurement Identifier: An identifier for the measurement Description: A description of the measurement Frequency: How often the measurement is updated. Measurement Type: Checked (False)

Measurement Calculation Describes the calculation used to determine a particular measurement Symbol Type: System Function Object Type: Function Attributes: *Name: The calculation used to determine a measurement

Information Element Calculation Describes the information element used to determine a particular information element Symbol Type: System Function Object Type: Function Attributes: *Name: The calculation used to determine the Information Element

Logical Entity Attributes Model (eERM Attribute Allocation Diagram) Depicts the attributes of a logical entity, that further describes the entity.

Entity 1.A

Attribute 1.1.d

Attribute 1.1.b

Attribute 1.1.c

Attribute 1.1.a

Logical Database 1

Logical Database 2

Logical Database 3

Logical Databases Model (IE Data Model) Strategically summarises the enterprise data on the highest level.

Logical Entities Model (IE Data Model) Depicts the logical entities of a database and the relationship between the entities.

Entity 1.1

Entity 1.2 Entity 1.3

Logical Database Represents a collection of data that is generally associated with one application. Object Type: Cluster/Data Model Symbol Type: Cluster/Data Model Attributes: *Name: Name of the Logical Database

Entity Logical entities are things of significance that the business wants to store information about. An entity is a group, class or thing. Object Type: Entity Type Symbol Type: Entity Type Attributes: *Name: Name of the Entity *Description: Description of the Entity

Unique Attribute An attribute that uniquely identifies and describes a logical entity. Object Type: ERM Attribute Symbol Type: K Attribute (ERM) Attributes: *Name: Name of the Unique Attribute *Description: Description of the Unique Attribute

Attribute An attribute that describes a logical entity. Object Type: ERM Attribute Symbol Type: D Attribute (ERM) Attributes: *Name: Name of the Attribute *Description: Description of the Attribute

Table Model (Table Diagram) Depicts the physical implementation of a logical entity as a table.

Enti ty 1.1

Table 1.1

Field 1.1.a

Field 1.1.b Attribute 1.1.b

Attribute 1. 1. a

Table A physical table in a database, or a structured data store. Object Type: Table Symbol Type: Table Attributes: *Name: Name of the Table *Description: Description of the Table

Field A physical column or field in a table. Object Type: Field Symbol Type: Field Attributes: *Name: Name of the Field *Description: Description of the Field

Subject Area Model (IE Data Model) List the subject areas of a logical database.

Subject Area 1.A

Subject Area 1.B

Subject Area A logical functional area in a logical database – usually determined according to business functionality. Object Type: Cluster/Data Model Symbol Type: Cluster/Data Model Attributes: *Name: Name of the Subject Area Description: Description of the Subject Area

Data Transformation Model (DW Transformation Model) Depicts the data transformation required to calculate an attribute.

.. .

Subject Area 1.A

Attribute 1.1.a Attribute 1.1.b

Attribute 1. 1. c

Attribute 1. 1 b Calculation

Description 1.1 a

Description 1.1 c

Description 1.1 b

Data Transformation Rule Represent the data transformation requirements. Object Type: Function Symbol Type: Transfer Rule Attributes: *Name: Name of the Transfer Rule Description: Description of the Transfer Rule

Database Ownership Model (Access Diagram) Depicts the business and technical ownership of the Logical Database.

Logical Database 1

Position 1

Position A.2

Database Technology Model (Access Diagram) Depicts the minimum technology requirements to deploy the database.

Logical Database 1

Infrastructure Application 1

Infrastructure Application 2 Server Type 1

Enterprise Architecture Meta-Model

2006

Version 01.03 M arch 2006

Business Architecture

Information

Data Application Technology

Intra- Architectural

Tech nol og y

App li cati on

Data

Inform ation

Busin es s Org ani sat ion

Busin ess M isce ll aneo us

Connection Legend

Intra- Architectural

Tech nol og y

App li cati on

Data

Inform ation

Busin es s Org ani sat ion

Busin ess M isce ll aneo us

Connection Legend

Attributes

Occurrence Copy

Assignment

Multiple Sources

Attributes

Occurrence Copy

Assignment

Multiple Sources

To be updated with IM Endeavour requirements

26Copyright (c) Anglo Platinum Limited 2006

Enterprise Architecture Process

Develop EA Meta-Model

Develop EA Products

Develop Business Process Models

Develop Information

Models

Develop Solution Models

Plan Enterprise Architecture

Meet business demand for process modelling Models accurately reflecting reality

Meet business demand for information modelling Models accurately reflecting reality

Meet ICT demand for solution modelling Models accurately reflecting realityMeta-model adherence

Meet user requirements for EA products

27Copyright (c) Anglo Platinum Limited 2006

Build strong foundations for target architectures

• Develop easily understood standards, guidelines and principles

• Establish conceptual framework and meta model • Engage senior management in development of high level processes

• Deliver appropriate training

Build Strong Foundations

28Copyright (c) Anglo Platinum Limited 2006

L0 Enterprise Processes L2 Process

L1 Value Chain

Locate Ore Body Perform Economic Evaluation

Perform Detail Planning Perform Detail Design Establish Mine Establish Processing Plant Establish Infrastructure

Operate Mine Support Operations Close Mine

Refine Product Schedule and Plan Treatment and Refinement Close Operation

Grow and Maintain Market Manage Dispatch and Delivery

Manage Corporate GovernanceManage PerformancePerform Strategic Planning

Manage Capital Investments

Manage Stakeholder Relations

Manage Physical Assets Lifecycle Manage Human Resources

Manage Supply ChainCo-ordinate SHE Risk ManagementManage Finances

Manage Information and TechnologyManage Metallurgy Manage R & D

Manage Transformation

Anglo Platinum Business Process Model 07 December 2005Version 2.03

Mine Ore Body

Market and Sell Platinum

Manage the Business

Find Platinum Source / Exploit Ore Reserves

Create Capacity

Locate Ore Body

Perform Economic Evaluation

Grow and Maintain Market

Manage Dispatch and Delivery

Support the Business

Manage Protection Services

Perform Strategic Planning

Manage Performance

Manage Corporate Governance

Manage Stakeholder Relations

Manage Transformation

Produce Refined Product

Concentrate Ore Smelt Concentrate Convert Matte

Perform Detail Planning

Establish Mine

Establish Processing Plant

Perform Detail Design

Establish Infrastructure

Manage Capital Investments

Manage Capital And Project Lifecycle

Refine Product

Schedule And Plan Treatment And Refinement

Close Operation

Concentrate Ore

Smelt Concentrate

Convert Matte

Refine Base Metals

Refine Precious Metals

Manage Metallurgy

M anage Information and Technology

Manage Physical Assets Lifecycle

Manage Human

Resources

Manage Research and Development

Manage Finances

Manage Supply Chain

Co-ordinate SHE Risk Management

Manage Protection Services

Level 2 Legend

Not yet Scheduled

Planned

Models completed to required level

L5 Task Detail (FAD) modelled

Detail model attached (Assignment)

L5 Task Flow (eEPC) modelled

Model L4 Activity Detail (FAD) modelled

L4 Activity Flow (eEPC) modelled

L2 Processes modelled

Perform Prospecting

Perform Geological Evaluation

Establish Mineral Rights

Determine New Mine

Scope

Perform Financial Modelling

Perform Mine Modelling

Perform Estimation

Establish Capacity Creation Project Plan

Establish Life of Operations Costing

Initiate Pr oject

Plan Project

Execute and Control Project

Close Project

Establish Business Case

Perform Operations Engineering

Perform Detail Operations Modelling

Perform Detail Operations Design

Perform Shaft

Development

Establish Surface

Infrastructure

Perform Underground Development

Establish Undergr ound Infrastr ucture

Perform Mine Commissioning

Build Concentrator

Build Smelter

Perform Plant Commissioning

Build Refinery Plant

Perform Housing

Development

Perform Hostel

Development

Perfor m Admin Building Development

Perform Capital Forecasting

Manage Investment

Manage Project Budget

Manage Project Execution / Integration

Plan Project Cash Flow

Perfor m Project Governance

Per form Project Risk Management

Perform Project Prioritisation

Perform Project Selection

Perform Critical Resourse Planning

And Allocation

Manage Project WBS Structures and Cost

Perform Screening And

Selecting

Perform Project Ecexution

Perform Project Fund Approval

Perform Investment Hand Over

Perform Post-Investment

Review

Perform Project Pre-Development

Perform Study Fund Appr oval

Manage Project

Plan Ore Extraction

Mine Ore

Plan Labour

L2 500 Day Turnaround

Labour Project

Rehabilitate Environment

Retrench and Redeploy Operations

Operate Mine

Support Operations

Close Mine

Crush Ore

Liberate Ore

Perform Primary Flotation

Perform Secondary Flotation

Perform Tailings Disposal

Perform Concentrator

Sampling

L2 Desiree Naudé

Perform Concentrator Consumable Additioning

L2 Desiree Naudé

Process Wet Concentrate

Perform Electric Furnace

Smelting

Perform Thickening And Belt Filtration

Perform Off Gas Cleaning

L2 Desiree Naudé

Process Molten Furnace

Matte

Perform Slag Cleaning Furnace

Smelting

Process Molten Furnace

Slag

Perform Smelter

Sampling

L2 Desiree Naudé

Perform Smelter

Consumable Additioning

L2 Desiree Naudé

Perform Smelter Effluent

Management

L2 Desiree Naudé

Convert Dry Furnace

Matte

Process Molten Converter

Matte

Treat Off Gas

L2 Desiree Naudé

Process Molten Converter

Slag

Perform Converter

Consumable Additioning

L2 Desiree Naudé

Perform Converter Sampling

L2 Desiree Naudé

Obtain Information for Scheduling and Planning of Treatment and Refinement

Optimise Schedule and Plan for Treatment

and Refinement

Rehabilitate the Environment

Retrench and Redeploy the Operations

Market Products

Manage Customer Service

Manage Customer Master Data

Manage Base Metals Sales

Manage Precious Metal Sales

Manage Sales From Smelter

Manage Billing

Manage Delivery

Manage Inter-company

Stock Transport

Define Organisation and

Relationships

Set Enterprise Strategy

Develop Long-Term Plans

L2 Strategic Long Term Planning

Develop Tactical Plans

Perform Operational

Planning

Manage Risk

Provide Legal Services

Provide Audit Services

Ensure Business Continuity

Provide Secretarial Services

Set Company Policies

Communicate with Investment

Community

Communicate with Interested

and Affected Parties

Communicate with Government

Communicate with Suppliers

Manage Joint Ventures and other Business Partners

Manage Black Economic

Empowerment

Manage Mining Charter

Manage Socio-economic

Development

Manage Women in Mining

Manage Social and Labour Plan

Develop Social and Labour Plans

Plan Information Technology

Build Core Business Solutions

Run Infrastructure

Run Core Business Applications

Run Support Business Applications

Build Support Business Solutions

Build Infrastructure

Manage Information

Manage Knowledge

Manage Payroll

Manage Human Performance

Perform HR Development

Manage Employee Relations

Perform HR Labour Management

L2 500 Day Turnaround Labour Project

Manage Personnel Administration

L2 500 Day Turnaround Labour Project

Manage Time And Attendance

Perform Talent Management

Manage Socio-economic

Development

Perform Recruitment

Perform HR Cost Planning

Perform HR Labour Control

L2 500 Day Turnaround Labour Project

Manage Accomodation Administration

Acquire Physical Asset

Install and Commission

Physical Asset

Perform Asset Tracking

Perform Plant

Maintenance

Protect Assets

Per form Engineering Change Management

Plan Research and Development Efforts

Conduct Research And Development

Manage Accounts Payable

Manage Accounts

Receivable

Manage Group Property

Manage Finance

Accounting

Manage Fixed Assets

Manage Management Accounting

Manage Corporate Finance

Manage Treasury

Manage Banking

Manage Share Options

Conduct Protection Services Investigation

Provide Access Control

Monitor Access

Manage Supply Chain Data

L2 SAP FDDs

Manage Supply Chain Demand

L2 SAP FDDs

Source Products and Services

L2 SAP FDDs

Supply Products and Services

L2 SAP FDDs

Settle Supply Chain Accounts

L2 SAP FDDs

Perform Metal

Accounting

L2 Desiree Naudé

Manage Laboratory

L2 Desiree Naudé

Manage Utilities

Perform Operational Logistics

Manage Surface Infrastructure

Provide Mine Technical Services

Survey Mine

L2 GMSI

Perform Mineral Resources

Evaluation

Direct and Lead the

Enterprise

Plan And Monitor The Business

Manage Hygiene Measurement And Monitoring

L2 SHE Process Modelling

Establish Task and Working Environment

Conditions

L2 SHE Process Modelling

Define Individual And Team Actions

L2 SHE Process Modelling

Prevent Absent and Failed Defences

L2 SHE Process Modelling

Manage Incidents

L2 SHE Process Modelling

Manage Consequences

L2 SHE Process Modelling

Identify SHE Legal and O ther Requirements

L2 SHE Process Modelling

Establish Action Management

L2 SHE Process Modelling

Establish Individual Capabilities

L2 SHE Process Modelling

Manage PPE

L2 SHE Process Modelling

Perform Observation And Behaviour Management

L2 SHE Process Modelling

Prevent Ventilation Absent And Failed Defences

L2 SHE Process Modelling

Prevent Public Health Absent And Failed Defences

L2 SHE Process Modelling

Manage Environment Monitoring

L2 SHE Process Modelling

Prevent Medical Absent And Failed Defences

L2 SHE Process Modelling

Manage Training

L2 SHE Process Modelling

Manage Safety Measurement And Monitoring

L2 SHE Process Modelling

Manage Public Health

L2 SHE Process Modelling

Manage SHE Reporting

L2 SHE Process Modelling

Establish Organisational Requirements

L2 SHE Process Modelling

29Copyright (c) Anglo Platinum Limited 2006

Build strong foundations for target architectures

• Develop easily understood standards, guidelines and principles

• Establish conceptual framework and meta model • Engage senior management in development of high level processes

• Deliver appropriate training

Build Strong Foundations

30Copyright (c) Anglo Platinum Limited 2006

Deliver appropriate training

Executive Briefings • Group ICT Management • Business Management • Business Users

Process Modelling • Business Context • Guidelines and Principles • Process Leveling • Process Modelling using AP meta model • Tools and functionality

31Copyright (c) Anglo Platinum Limited 2006

Develop an in-house architectural capability

• Transfer skills from consultants who assisted in the project • Identify internal “champions” for the cause but leave them “in situ”

Outsource non-core EA services

• Anglo Platinum has outsourced non-core ICT activities, following the “Gartner Lite” model

• Following from this, it has retained the strategically important roles of inter alia, IT Strategy, Planning and Architecture

Develop an EA Capability

The non-core EA activities associated with quality control and maintaining the integrity of the architectural framework and meta data have been outsourced

32Copyright (c) Anglo Platinum Limited 2006

Strong emphasis on meeting business needs and not “modelling for its own sake”

• Business need for and commitment to:

• Safety, Health and Environment • Labour Planning • Process standardisation • Single source of management information

…..all driving standardisation and reduced cost

Respond to short term business needs

33Copyright (c) Anglo Platinum Limited 2006

Agenda

• Background – Business – Drivers for change – Architectural concepts

• Approach to implementation – Research and learn from others – Develop a target architecture – Build strong foundations – Respond to short term business

needs – Develop an EA capability

• Toolset selection – ARIS – Utilities

• Early deliverables and business successes – Business Process Models

• Utilities • Documentation

– Information and Data Models – Application Models – Technology Models – Documentation

• Learnings

• The Way Forward – Governance

34Copyright (c) Anglo Platinum Limited 2006

EA Toolsets Considered

CASEWISE - Corporate Modeller • Meta-model extensibility impressive • Support excellent and product ease of use • UML not standard

POPKIN - System Architect • Meta-model extensible • Advanced standard UML capability • Database interfaces • Assignments a concern in terms of a levelling approach to modelling

IDS SCHEER – ARIS • Big SA local user base • Extensive set of methodologies and additional functionality • Limited meta-model extension • Selected by SAP

35Copyright (c) Anglo Platinum Limited 2006

Gartner Quadrants - Process & EA Tools

ARIS

ARI ARIS

36Copyright (c) Anglo Platinum Limited 2006

EA Toolset Selected

IDS SCHEER – ARIS

• Relevance to SAP environment • Excellent in process modelling arena • Functionally rich • Other tools available in data, application and

technology domains (but we are exploring new frontiers with ARIS)

• Future developments relating to SAP configuration

37Copyright (c) Anglo Platinum Limited 2006

ProcessProcess DefinitionDefinition

ProcessProcess ConfigurationConfiguration

222

111

ProcessProcess ExecutionExecution

333

ProcessProcess ControllingControlling4

ARIS for mySAP/ SAP Solution Manager

ARIS Web Designer/ ARIS Toolset

mySAP Solutions/ SAP NetWeaver

ARIS PPM/ SAP Netweaver

Integrated Business Process Modeling with ARIS & SAP

38Copyright (c) Anglo Platinum Limited 2006

ARIS Utilities

The following utilities were developed as add-ons to standard ARIS functionality to meet specific business requirements:

Process numberingSwim lane generators

Domino.doc synchronisationFlow Diagrams

Process variance reportingProcedure documentation

Impact Analysis Database Functional Allocation Diagrams Capturing Utility

39Copyright (c) Anglo Platinum Limited 2006

Agenda

• Background – Business – Drivers for change – Architectural concepts

• Approach to implementation – Research and learn from others – Develop a target architecture – Build strong foundations – Respond to short term business

needs – Develop an EA capability

• Toolset selection – ARIS – Utilities

• Early deliverables and business successes – Business Process Models

• Utilities • Documentation

– Information and Data Models – Application Models – Technology Models

• Learnings • The Way Forward

– Governance

40Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 1

Level 0 – Enterprise Process Model

Enterprise Process

Level 3 – Sub-process Model Sub-process

Level 1 – Value Chain Model

Level 5 - Task Model

TaskValue Chain

High Level Process Models Detailed Process Models

Level 4 - Activity Model

Activity

Level 2 – Process Model Process

Based on business demand, a large number of business processes have been standardised and modelled to levels 3 (sub-process) and 4 (activity) as appropriate

41Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 2

Where sufficient content has been captured, reports are generated with detail of roles and responsibilities allowing, in due course, for more equitable task loading

42Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 3

Manual processes for possible future automation have been identified

43Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 4L3 Develop EA Plan

SB.IT.01.05.03

L4 Determine EA

Framework Change Required

L3 Develop EA Plan

EA Framework Approved

SB.IT.01.05.02

L4 Review ExistingEA Framework

SB.IT.01.05.01

L4 Review EA Related

Governance Documents

EA Concept Change Required

EA Conceptual Framework Change

Required

SB.IT.01.05.04

L4 Develop/Update EAConcepts

SB.IT.01.05.05

L4 Develop/Update EA

Conceptual Framework

SB.IT.01.05.06

L4 Obtain EA

Framework Approval

EA Work Allocated

L3 Develop EA Plan

SB.IT.01.05.03

L4 Determine EA

Framework Change Required

L3 Develop EA Plan

EA Framework Approved

SB.IT.01.05.02

L4 Review ExistingEA Framework

SB.IT.01.05.01

L4 Review EA Related

Governance Documents

EA Concept Change Required

EA Conceptual Framework Change

Required

SB.IT.01.05.04

L4 Develop/Update EAConcepts

SB.IT.01.05.05

L4 Develop/Update EA

Conceptual Framework

SB.IT.01.05.06

L4 Obtain EA

Framework Approval

EA Work Allocated

Model Business Process Flow

Capture Business Rules

Update Business Models (Automated)

Application System A

Customer

Role A

Role B

Report A Report B R C

Work Instruction

X1 R

SOP a.1 R

Supplier

Role E

Role F

belongs to

DEPARTMENT

belongs to

DEPARTMENT

Publish MS Word Procedure

(Automated)

Application System A

Customer

Role A

Role B

Report A Report B R C

Work Instruction

X1 R

SOP a.1 R

Supplier

Role E

Role F

belongs to

DEPARTMENT

belongs to

DEPARTMENT

• Model becomes the documentation • Appropriate tools are used for each step in the process • Training focussed on the correct audience

44Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 4

L3 Develop EA Plan

SB.IT.01.05.03

L4 Determine EA

Framework Change Required

L3 Develop EA Plan

EA Framework Approved

SB.IT.01.05.02

L4 Review ExistingEA Framework

SB.IT.01.05.01

L4 Review EA Related

Governance Documents

EA Concept Change Required

EA Conceptual Framework Change

Required

SB.IT.01.05.04

L4 Develop/Update EAConcepts

SB.IT.01.05.05

L4 Develop/Update EA

Conceptual Framework

SB.IT.01.05.06

L4 Obtain EA

Framework Approval

EA Work Allocated

Model Business Process Flow

Capture Business Rules

Update Business Models (Automated)

Application System A

Customer

Role A

Role B

Report A Report B R C

Work Instruction

X1 R

SOP a.1 R

Supplier

Role E

Role F

belongs to

DEPARTMENT

belongs to

DEPARTMENT

Publish MS Word Procedure

(Automated)

• Model becomes the documentation • Appropriate tools are used for each step in the process • Training focused on the correct audience

45Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 5

PL.01.01

L4 Define Labour

Definitions

Labour Definitions Standards Planning Parameters

And Templates Required

PL.01.02

L4 Define Labour

Planning Standards

PL.01.04

L4 Defi ne

Labour Planning Parameters For Servi ces

Standardi sed Labour

Business Plan Template Enhanced

Produce Annual Or Five Year Labour Plan

PL.01.05

L4 Enhance

Standardi sed Labour

Plan Template

PL.01.03

L4 Define

Labour Planning Parameters

For Production

Labour Definitio...

Finance Manager

Monthly Shaft...

Mine Tech Services...

Mine Manager

Manager Human...

Mine Technic...

I R

Labour Plannin...

Human Resources C...

Labour Planni...

PL.01.02

L4 Define Labour

Planning Standards

Generate views for different audiences or uses. Capture process flow

Capture process detail

46Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 6

PL.01.05

L4 Enhance

Standardised Labour

Plan Template

Group HR Manager : Employee Relations

Standardise d Labour...

Human Resources Co-Ordinator

Labour Definitions Standard...

PL.01.02

L4 Define Labour

Planning Standards

PL.01.03

L4 Define

Labour Planning Parameters

For Production

PL.01.04

L4 Define

Labour Planning Parameters For Services

PL.01.01

L4 Define Labour

Definitions

Produce Annual Or Five Year Labour Plan

Capture process flow Capture process detail Generate Swimlane

Used for: • Role-based training • Process optimisation • Workflow implementation • Process control –

segregation of duties

47Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 7

Labour Planning Standa rds

Labour Planning FROG

PL.01.03

L4 Define

Labour Planning Parameters

For Production

Labour Planning Standards

PL.01.05

L4 Enhance

Standardised Labour

Plan Template

Labour Planning FROG

Standardised Labour

Business Plan Template Enhanced

Annual/Five Year Production Plan

Labour Definitions Document

Labour Definitions Standards Planning Parameters

And Templates Required

Labour Plan Template

PL.01.02

L4 Define Labour

Planning Standards

Produce Annual Or Five Year Labour Plan

Labour Planning Standards

Labour Definitions Document

Labour Planning FROG

Monthly Shaft Report

Annual/Five Year Production Plan

PL.01.04

L4 Define

Labour Planning Parameters For Services

Labour Planning FROG

Labour Planning Standards

PL.01.01

L4 Define Labour

Definitions

Capture process flow Capture process detail Generate Document

Flow

Used for: • Document management • Information flow • Training

48Copyright (c) Anglo Platinum Limited 2006

Business Process Models - 8

• Selected processes and activities have been bi-directionally (hyper-) linked to Group document management system containing standards & appropriate legislation e.g. – ISO standards, – Mines and Safety Act, – Policies and Procedures

• Enables identification of what process uses what documents

• Links to documents in the Group DMS are automatically updated

49Copyright (c) Anglo Platinum Limited 2006

50Copyright (c) Anglo Platinum Limited 2006

Information Models • Information modelling methodology based on the Science of

Informational Management (SCIAM) as developed by Russell Swanborough. (http://www.lejara.com) Used to audit the process from an information perspective, as well as the information completeness

Data Models • Data models captured only where necessary to support

information or to define application data base schemas. (Limited modelling driven by extensive use of packaged solutions)

Information and Data Models - 1

51Copyright (c) Anglo Platinum Limited 2006

Information and Data Models - 2

Ensure the Cost Effectiveness of

Labour Forecast Cost

of Labour

Plan to incur Labour (Cost

PL.07

L3 Perform Monthly

Production Planning

High

PRODUCE ANNUAL OR 5 YEAR PLAN: The actual labour forecast exists in the LOM and the 5 year labour plan is a forecast. This process may be negatively impacted due to the looped interdependencies it has. The resources needed to manage and minimise cost must also be identified?

High

The type of people resources required is well defined in both long term and short term. Need to include infrastructure

A Allocate costs per area

2 Known past costs per area

1 Maximum costs allowable for all areas

0 Initiate Management and Accomplishment for labour costs

B Key areas to have cost limits controlled in future

4 Costs allowed per area per period

6 Past costs per area per period highlighting key areas

PL.04

L3 Cost Annual Or Five Year Labour Plan

Labour Plan Cost

Verification Report

Standardised Labour

Cost Recon Report

Accomplishment Processes

Legend

Management Processes

PL.02

L3 Produce Annual

Or Five Year Labour Plan

PL.05

L3 Establish Staffing

Requirements

Daily Strength By

Organisational Unit

Employment Equity Report

HR Movement

Report

Profile Match Report

Qualification Profile Report

SAP In-service

Report

Team Make-up Report

Unoccupied Position Report

Vacancy Report

Variance Report

PL.06

L3 Perform Monthly

Production Pre-Planning

Consolidated SAP and Daycall Monthly Report

Daily Strength By

Organisational Unit

Variance Report

Labour Plan Cost

Verification Report

Standardised Labour

Cost Recon Report

Labour Plan Cost

Verification Report

Standardised Labour

Cost Recon Report

Business objective Generic informational

process

As-Is process mapping with reports

Information elements required to manage

process

Reports on which information elements

appear

Does the As-Is reports match the reports on

the framework

Does the As-Is reports match the reports on

the framework?

52Copyright (c) Anglo Platinum Limited 2006

• Capture at application module level e.g. SAP HR, MM, PS • Capture associated meta data e.g. business & technology fit • Link applications to:

• Information, data and processes • Business process owners • Documentation e.g. technology strategies, policies, procedures and

standards

• Enables Application Portfolio Management

Application Models

53Copyright (c) Anglo Platinum Limited 2006

2006

Infrastructure Applications OverviewApplication List View

Infrastructure Applications Model 29 M ay 2006Version 00.00

Internet ( Clien t)

Microsoft Off ice

Legend

Deta il model attached (Assignment) Deta il model attached (Assignment)

HUB BRIDGE SWITCH ROUTER VPNGA TEWAY

INTERNETWORKS

Thin Client

Networks

Peripherals

Components

Operating Systems

Hardware

PLATFORMS

P2P – Peer To Peer

Web Services

EIP EAI EII BPM BAM

Application Integration

Application Partitioning

MOM

Infrastructure Applications

e-Marketplace Public Exchanges

B2B

B2C

Other

Wireless

Content

Database

Internet (Server)

Basic

Other Clientware

PDA and Smart Phones

Publish

Performance

Problem

Operations

Configuration

Security

Network

Systems

Enterprise

MANAGEWARE

SERVEWARE

ORB RPC Fat

Client

Directory and Security

Formats and Protocols

MIDDLEWARE

Graphics

Internet (Client)

Office

CLIENTWARE

Office

Word Processing Spreadsheet Presentation

PIM And Contact Manager

Personal Database

Application Suite

AppleWorks

CodeWeavers CrossOver Office

Corel WordPerfect

Office

GNOME Office

IBM Lotus SmartSuite

KDE KOffice

FileMaker Pro

IBM Lotus Approach

Microsoft Access

Microsoft InfoPath

Microsoft Visual FoxPro

Sun StarOffice Base

Microsoft Outlook

Microsoft PowerPointMicrosoft Excel

Corel WordPerfect

IBM Lotus Word Pro

Microsoft Word

Sun StarOffice Writer

Corel Quattro Pro

IBM Lotus 1-2-3

Sun StarOffice Calc

Apple Keynote

Corel Presentations

IBM Lotus Freelance

Macromedia Breeze

Sun StarOffice Impress

ACT!

GoldMine

IBM Lotus Organizer

Info Select

Novell Ximian Evolution

OSAF Chandler

Microsoft Office Professional

Microsoft Office Standard

Microsoft Office OneNote 2003

Microsoft Office XP Professional

Microsoft Office XP Standard

MS Office 2000, XP Professional

MS Office 2000, XP Standard

Print And View Reports

Internet (Client)

E-mail Client

IM - Instant Messaging

Web Browser

Browser Plug-In

Adobe Acrobat Reader

Adobe SVG Viewer

AI RoboForm

Microsoft Internet Explorer

Netscape Navigator

AIM - AOL Instant Messenger

ICQ

IBM Lotus Sametime

Microsoft Outlook

Microsoft Outlook Express

Netscape Mail

Adobe Acrobat 6 Standard

Microsoft Internet

Explorer 6

AppleWorks CodeWeaversCrossOver Office

KDE KOffice

Microsoft Office

Microsoft Works

Novell Ximian Desktop

Microsoft Access

Microsoft InfoPath

Microsoft Visual FoxPro

Sun StarOffice Base

Microsoft Outlook

Microsoft PowerPoint

Microsoft Excel

Microsoft Word

Sun StarOffice Writer

Sun StarOffice Calc

Apple Keynote

Macromedia Breeze

Sun StarOffice Impress

ACT!

Novell Ximian Evolution

OSAF Chandler

Microsoft Office Professional

Microsoft Office Standard

Microsoft Office OneNote 2003

Microsoft Office XP Professional

Microsoft Office XP Standard

MS Office 2000, XP Professional

MS Office 2000, XP Standard

OfficePro2000

Microsoft Project

Print And View Reports

SLIDE/Swedge

Microsoft Access 2000

Microsoft Office 2000 Standard

Centra Conference,

eMeeting

Latitude MeetingPlace

Microsoft LiveMeeting

Microsoft Windows

NetMeeting

Raindance Web Conferencing Pro

SunForum WebEx MeetingCenter

3D-FTP AbsoluteFTP

Adobe Acrobat Reader

Adobe SVG Viewer AI RoboForm

Apple QuickTime Player

Macromedia Flash Player

Macromedia Shockwave

Player

Microsoft Internet Explorer

Netscape Navigator

Microsoft MSN Messenger

Microsoft Windows

Messenger

Yahoo! Messenger

Microsoft Outlook

Microsoft Outlook Express

Netscape Mail

Novell GroupWise

Microsoft Outlook 2000

Microsoft Outlook forms

Adobe Acrobat 6 Standard

Microsoft Internet

Explorer 6

Lotus Notes

Application in useApplication in use

Application no t in use Application no t in use

54Copyright (c) Anglo Platinum Limited 2006

Application Portfolio Model

Developing an application portfolio management capability in ARIS to measure for example Business Fit, Benefit & Utilisation, Architectural Fit & Complexity, Vendor capability …etc

2005.03 2005.04 2006.01 2006.02

0% 10% 20% 30%

40%

50%

60%

70%

80%

90%

100%

Sum of Poor Sum of Med Sum of Good

Category Business

Year

Data

2005.04 2006.01

2006.02

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Sum of Poor Sum of Med Sum of Good

Category Business Intelligence

Year

Data

2005.04 2006.01

2006.02

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Sum of Poor Sum of Med Sum of Good

Category Infrastructure

Year

Data

55Copyright (c) Anglo Platinum Limited 2006

• All Servers • Generic end-user devices e.g. PCs, printers, etc. • Conceptual Networks: e.g. Corporate, Internet, Intranet, Extranet, T&A,

Process Control, Security • Environmentals e.g. computer rooms, power loads

Linked to: • Configuration Managament Data Base (CMDB) • Documentation e.g. technology strategies, policies, procedures and

standards

Technology Models

56Copyright (c) Anglo Platinum Limited 2006

2006

Server LocationsServer List View

Server Locations Model 29 M ay 2006

Version 00.00

EA ST ERN LIMB:

Lebow a Organizational Chart

ANGLO PLATINUM Organ izational Chart

Legend

Deta il model attached (Assignment) Deta il model attached (Assignment)

Republic of South Africa

Western Limb Eastern Limb

Northern Limb

Bafokeng- Rasimone Lebowa

Potgietersr ustUnion

Maandagsh oekRustenburg PolokwaneAmandelbult Twikenham

Gauteng

60 Main 55 Marshall Anglo

Research Centre...

Senderwood Germiston

Lebow a Netw ork Topology

Anglo Plat SA

Western Limb

Eastern Limb

Northern Limb

Gauteng

Lebowa

Vertical Shaft

Middelpunt Adits & Decline

UM1Incline UM2 Incline

Lebowa

Vertical Shaft Middelpunt

Adits & Decline

UM1Incline UM2 Incline Atok Lebowa PQ

Server Room

Lebowa

LEBOWAT EST1

S_LEB_M TS

S_LEB_TN A1

SLEB01

SLEB03

SLEB04

SLEB10

SLEB30

SLEBWTS 1

SLEBWTS 2

SLEBWTS 3

SLEBWTS 4

General Server

Infrastruct ure Server

MAIL SERVER

MTS Server

Time & Attendanc e Server

WEB SERVER

WTS Server

General Server

Infrastruct ure Server

WTS Server

SLEB19

SLEB37

SLEB22

SLEB40

SLEB11

Lebow a Servers

ANGLO PLATINUM Geographical Locations

100-IIS-S01 100-OFF-S01 Advanced HelpDesk AMSTECH AMSTECHDATA

ARCTESTSERVE R1 BL2000 # 1 BL2000 # 10 BL2000 # 11 BL2000 # 12

BL2000 # 13 BL2000 # 14 BL2000 # 15 BL2000 # 16 BL2000 # 17

BL2000 # 18 BL2000 # 19 BL2000 # 2 BL2000 # 20 BL2000 # 21

BL2000 # 22 BL2000 # 23 BL2000 # 3 BL2000 # 4 BL2000 # 5

BL2000 # 6 BL2000 # 7 BL2000 # 8 BL2000 # 9 BVCONTROL-SAP1

Cost Management

System - projects

CS 500 # 1 CS 500 # 2 DocummentManagement EIS

EMPEROR ENG_Station EXTRAS FinancialPlanning GETAFIX

GMMS Housing Intranet IntranetInterfaces Knowledge

management

LEBOWATEST1 LUTHLORIEN MANAGDESK MIS NETCARE911

OZYMANDIAS Platinum Health Policies &Procedures Provident Fund RASSIE

RIVENDELL RSTEST S_ABULT_MTS S_AMS_EDA S_ARC_01

S_ARC_RAS S_ARC_SD S_BRPMS1 S_CITYBANK

S_HEX_04 S_HEX_05 S_HEX_RAS S_HEX_TNA1S_Hex_TNA1

S_Hex_TNA1! S_LEB_MTS S_LEB_TNA1S_Leb_TNA1 S_PPL_PAY

S_PPL_TNA1 S_RPM_02 S_TDSQL S_UNION_TNA1 SABU01

SABU03 SABU04 SABU10 SABU11

SABU19 SABU20

SABU07

SABU14 SABU22 SABU23

S_HEX_02

57Copyright (c) Anglo Platinum Limited 2006

2006

Conventional Mine View Model 29 M ay 2006Version 00.00

Legend

Deta il model attached (Assignment) Deta il model attached (Assignment)

W ...

UNDERGROUND (Shaft view)

Logistics Control

PARKING Walkie-talkie

Voice Network

Walkie-talkie

Shaft

Video Camera

OFFICE AREA

Surface Time Reader

Access Access

Video Camera

Belt

Battery & Lamp

Panel

Blast Box

Protein Supplement

Blast Control

Walkie-talkie

Video Camera

Panel

Security Network

Radio Network

Environmental Monitoring

Undergorund Time Reader &

Access

Ventilation Monitoring

Environmental Monitoring

Safety Equipment

Fire Control

LAMP ROOM

Scraper

Fire Sensor

Ventilator

Sensored Motor

58Copyright (c) Anglo Platinum Limited 2006

Agenda

• Background – Business – Drivers for change – Architectural concepts

• Approach to implementation – Research and learn from others – Develop a target architecture – Build strong foundations – Respond to short term business

needs – Develop an EA capability

• Toolset selection – ARIS – Utilities

• Early deliverables and business successes – Business Process Models

• Utilities • Documentation

– Information and Data Models – Application Models – Technology Models

• Learnings

• The Way Forward – Governance

59Copyright (c) Anglo Platinum Limited 2006

Learnings 1

• Start at the top – Involve business and ICT leadership early and often – EA driven by business strategies and imperatives – Maintain business support over time

• Create a sustainable centre of excellence – Need to dedicate and maintain sufficient internal resources

whilst developing business capability

• Apply 80/20 rule – Appropriate implementation rather than "perfect“ – Need to be agile: Evolve architecture to match changing

business needs / requirements

60Copyright (c) Anglo Platinum Limited 2006

• Contrary to conventional wisdom, do not shout from the mountaintop as few but the initiated will understand

• Demonstrate a few, early benefits and allow business to create demand business pull vs. IT push

• Low Profile - "implementation by stealth" • Manage expectations • Expect demand to outstrip initial resources

• Prioritise work based on business imperatives

Learnings 2

61Copyright (c) Anglo Platinum Limited 2006

Agenda

• Background – Business – Drivers for change – Architectural concepts

• Approach to implementation – Research and learn from others – Develop a target architecture – Build strong foundations – Respond to short term business

needs – Develop an EA capability

• Toolset selection – ARIS – Utilities

• Early deliverables and business successes – Business Process Models

• Utilities • Documentation

– Information and Data Models – Application Models – Technology Models – Documentation

• Learnings

• The Way Forward – Governance

62Copyright (c) Anglo Platinum Limited 2006

The Way Forward - Governance

Architecture Forum

MANDATE The Architecture Forum serves as the body that will direct, co-ordinate and recommend the organising logic for business processes. It will direct and control the architectures relating to information, data, applications and technology, captured in a set of principles, policies, guidelines and standards to achieve desired business and technical standardisation and integration

PRINCIPLES • To reduce ICT complexity. • To drive information quality and accuracy at source • To standardise processes and systems. • To stabilise existing systems by promoting standardisation. • To review all ICT investments in the light of centrally determined standards

and procedures.

63Copyright (c) Anglo Platinum Limited 2006

The Way Forward - Governance

Architectural Requirements per Project

Project stage gates at end of design and prior to implementation

• Complete level 3,4 and 5 sub-process, activities and work- steps as appropriate

• Capture Information requirements per process based on SCIAM

• Capture supportive applications and link to data, information and processes as appropriate

• Capture technology architecture required to support the application

64Copyright (c) Anglo Platinum Limited 2006

Experiences with Enterprise Architecture

Implementation at Anglo Platinum

Presented by: Steve Rasmussen CTO Anglo Platinum