anglo platinum presentation to theea forum finding the...

1Copyright (c) Anglo Platinum Limited 2006

Anglo Platinum presentation to the EA Forum

30 August 2006

Finding the business drivers In Enterprise Architecture

Philip Venter


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


Overview of Anglo Platinuma member of the Anglo American Group

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

2005 2004

R 000 US$ 000 R 000 US$ 000

Total Assets 35,789.5 5,640.5 32,522.2 5,761.3

Net Sales 22,938.0 3,602.3 19,267.0 2,993.2

Profit after Tax 4,489.9 705.0 2,486.3 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 / or mining activities in Canada, Russia, Brazil and Zimbabwe. Negotiations have been concluded in the Sishuan Province in China to explore matters of joint interest.


Location


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


Reduce Business and ICT Complexity

Major opportunity to reduce ICT total cost of ownership

(TCO) in labour, maintenance, upgrades, licensing and integration

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 infrastructurecomplexity

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 ICTto operate more effectively

Business complexity Process

complexityICT

complexity


This programme is very closely aligned to the FFF goals, particularly that of reducing organisational complexity

Standard Processes

& Org Structure

Single Repository

and Template

ICT Complexity Reduction

Sustaining Capability

Fit For Future Goal

Performance Culture

More effective support functions

Address the increasing importance of JVs

Reduce organisational complexity

More reliable delivery of projects

Improved processing productivity

Improved productivity and cost efficiency

Focus on most important business

priorities

One business


Business and ICT Complexity Reduction Opportunities

Reduce infrastructure costs by rationalising

serversMore than 400 servers

ICT

Infrastructure

Reduce the number of applications by

between 10% and 20%

Duplication of

functionality across

applicationsSystems

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/ BenchmarkMeasure of Complexity

Opportunity Area

Bu

sin

ess

Dri

ve

nIT

Dri

ve

n


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 enougharchitecture 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


Enterprise Architecture Frameworks

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

1. 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 at Anglo Platinum Needed to break out information from data


Enterprise Architecture Frameworks

2. Zachman

Basis for development of the conceptual framework and meta model:

Reference model to check completeness

Comprehensive but not intuitive

3. TOGAF

Comprehensive reference for EA method

Input to EA guiding principles

Development of EA roles and skills matrix

Extensive user base


Anglo Platinum 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 informationlayers of the architecture as depicted in the EA cube.

Enterprise

Real IRM SolutionsReal IRM Solutions

Arc

hit

ec

ture

s

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l

Business Architecture

Information Architecture

Data Architecture

Application Architecture

Technology Architecture Ente

rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Pe

op

le

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e ore

bod

y

.

EnterpriseEnterprise


Arc

hit

ec

ture

s

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Pe

op

le

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e ore

bod

y

.


Arc

hit

ec

ture

sA

rch

ite

ctu

res

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Pe

op

le

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e ore

bod

y

.


Agenda

Background

Business

Drivers for change







needs


Toolset selection

ARIS

Utilities


Utilities Documentation

Information and Data Models Application Models Technology Models

Documentation

Learnings

The Way Forward

Governance


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


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


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


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


Develop a Target Architecture: Current and target

0

1

2

3

4

5

Tools

People

ContentProcess

Products/Services

CurrentTarget

4 = Managed


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


EA Principle Template

Enterprise

Real IRM Solutions Real IRM Solutions

Arc

hit

ec

ture

s

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Pe

op

le

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e ore

body

.



Arc

hit

ec

ture

s

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Pe

op

le

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e ore

body

.


Arc

hit

ec

ture

sA

rch

ite

ctu

res

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Pe

op

le

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e ore

body

.

One line principle

Principle

Supporting rationale

Rationale

1. Implications resulting from the principle

Implications

Architecture Architecture Design Design ManagementManagement


One of the key EA principles adopted

Enterprise


Arc

hit

ectu

res

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Peo

ple

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e or

e bod

y

.



Arc

hit

ectu

res

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Peo

ple

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e or

e bod

y

.


Arc

hit

ectu

res

Arc

hit

ectu

res

Expl

oit o

re re

serv

es

Hum

an R

esou

rces

Inte

llect

ual C

apita

l



Data Architecture



rpris

e Ar

chite

ctur

e

Cap

abili

ty

(Cen

tre

of E

xcel

lenc

e)

Peo

ple

Co

nte

nt

Pro

ce

ss

To

ols

Pro

du

cts

an

d S

erv

ices

Safe

ty, H

ealth

, Env

ironm

ent

Min

e or

e bod

y

.

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


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:




Process

Process

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

Principle

The business is still organised along functional lines, althoughthe 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 Management Management

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 - DefinitionsLevel 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

Focus

Focus

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

Copyright (c) Anglo Platinum Limited 2006

24

Enterprise ArchitectureSummary Conceptual Framework

Version 1.03

May 2005

Copyright Real IRM Solutions (Pty) Ltd

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



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



Process (Level 2)


Activity (Level 4)

Task (Level 5)

Product List Material List

Process/Product



Process (Level 2)


Activity (Level 4)

Task (Level 5)


Business Role List

Position List


Process/Organisation



Process (Level 2)


Activity (Level 4)

Task (Level 5)

Risk ListControl List

Process/Risk



Process (Level 2)


Activity (Level 4)

Task (Level 5)

Strategic Objectives List

Business Principles List

Process/StrategicBusiness Cycles Hierarchy

Cycle ModelsEnterprise

Process (Level 0)


Process (Level 2)


Activity (Level 4)

Task (Level 5)

Business Cycles Hierarchy

Process/Cycle

Document Hierarchy

Information Hierarchy Metrics Hierarchy

Information Models



Process (Level 2)


Activity (Level 4)

Task (Level 5)

Document Hierarchy

Information Hierarchy

Metrics Hierarchy

Information/Process

Position List


Metrics Hierarchy

Information/Organisation

Logical Databases

Data Subject Areas

Entities


Tables

Information/Data


Applications

Application Modules

Application Interfaces

Information/Application Source


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 ListLogical

Databases

Data/Network



Process (Level 2)


Activity (Level 4)

Task (Level 5)

Logical Databases

Data Subject Areas

Entities

Tables

Data/Process

Applications

Application Modules


Application Hierarchy

Application Models

Position ListApplications

Application Modules


Application/Organisation

System Role List

Applications

Application Modules


Application/System Role

Server List

Applications

Application Modules


Application/Network



Process (Level 2)


Activity (Level 4)

Task (Level 5)

Applications

Application Modules


Application/Process

Applications

Application Modules


Logical Databases

Data Subject Areas

Entities

Tables

Application/Data

Server ListInfrastructure Applications

Hierarchy

Infrastructure Applications

Technology Models


Position List


Server List

Network/Organisation

Server ListInfrastructure Applications

Network/Infrastructure

Applications

Network Models

System Software Models

Application Models

Data Models

Document Models

Information 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

Information Models

Cycle Models

Strategic Models

Risks and Controls Models

Organisation Models

Product Models

Process Models

Legend

Copyright (c) Anglo Platinum Limited 2006

25

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

types organisational units.

OrganisationalUnit Type 1.1

Org anizationalUnit Type 1.2

OrganizationalUnit Type 1

Organisation Model(Organizational Chart)

To provide a hierarchical view of the organisational units, positions and the jobs of the whole organisation.

OrganisationalUnit A

OrganisationalUnit A.1

Job 2

Cost Center A

Position A.1 Job 3

OrganisationalUnit A.2

Job 4Position A.2

Position A.0Cost CentreAn accounting Cost Centre (sourced from SAP).

Object Type: Organizational UnitSymbol Type: Cost Center

Attributes:*Name: Name of the Cost Centre

Organisational UnitAn organisational unit, e.g. company, division,

Operational unit, business unit and department.

Object Type: Organizational UnitSymbol 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

JobA generic position to group positions

(sourced from SAP).Object Type: Organizational Unit Type

Symbol Type: Position TypeAttributes:*Name: Name of the Job

*Identifier: SAP Identifier*Description: Description of Job

Job List(Organizational Chart)

To provide a l ist of all jobs.

Job 2Job 1 Job 3

Business RoleRepresents the part that mus t be played in the execution of similar activi ties

Object Type: Person TypeSymbol 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: LocationAttributes:*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

Locat ion 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 conduc ted.

Locati on Type

A.1

Location TypeA.1.2

Location TypeA.1.1

Location Type

A geographical location type where business operations are conducted.

Object Type: LocationSymbol Type: LocationAttributes:*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 Role1

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 TypeA generic type of organisational unit within the business

Object Type: Organizational unit typeSymbol 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.

Organisationa lUnit Type 1.1

O rganizationalUnit Type 1.2

OrganisationalUnit Type 1

Position

Position that an employee is appointed in(sourced from SAP).Object Type: Position

Symbol Type: PositionAttributes:

*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

EquipmentType 1

EquipmentType 2

Service Detail(Product/Service Exchange Diagram)

To provide the detail surrounding the delivery of a specific service category

Locat ion A.1.iService Category

1.1

Application 1

Business Role 1

Organisat ional UnitA.1

RAIDEIT Service 1.1.B.i

IT Service 1.1.B. ii

RAIDE

RAIDE

InfrastructureApplication 1

Strategic Objectives Model(Objective Diagram)Presents the strategic objectives of the organisation

in a hierarchical tree.

Strategic

Objecti ve 1.2

StrategicObjective 1.2.1

StrtategicObjective 1.2. 2

Strategic ObjectiveStrategic objective of the organisation.

Object Type: ObjectiveSymbol Type: Objective

Attributes:*Name: Name of the Strategic ObjectiveDescription: Description of the Strategic

Objective

Product

Product of the organisation , e.g. Platinum, Gold, etc.Object Type: P roduct/Se rvice

Symbol Type: P roductAttributes:

*Name : Name of th e Produc tDescription: Description of the Produ ct

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 LevelAgreement 3


Organisati onal UnitA.1

Organisat ional UnitA.2

Organisational UnitB


Service Level AgreementA Service Level Agreement Contract between

the business and an organisational unitObject Type: Product/Service

Symbol Type: ServiceAttributes:

*Name: Name of the SLAIdentifier: An identifier for the SLA

*Service Type: SLA

SLA Structure(Product/Service Tree)

To provide hierarchical breakdown of the SLA into its different schedules


Servi ce Category1.3



Service Category

A category into which the services is dividedObject Type: Product/Service

Symbol Type: ServiceAttributes:

*Name: Name of the ScheduleIdentifier: An identifier for the Service CategoryDescription: A description of the Service Category

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

Service Category1.1

Service 1.1.A

Service 1.1.B

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

Service 1.1.B. i

ServiceA service that forms part of a Service Category

Object Type: Product/ServiceSymbol Type: Service

Attributes:*Name: Name of the Service

*Identifier: A unique identifier for the ServiceDescription: 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 del ivery.

Information Technology Services(Product/Service Tree)

To provide a view of the different Information Technology Services that are provided to the business

IT Service Group1

IT Service Group2

IT Service Group3

IT Service Group Structure(Product/Service Tree)

To provide hierarchical breakdown of the Service Group into Service Categories

IT Service Group1

IT ServiceCategory 1.1


IT Service Breakdown(Product/Service Tree)

To provide hierarchical breakdown of the IT Services


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/EquipmentRepresents the material and equipment that

is used within the business Object Type: Material type

Symbol Type: Material typeAttributes:

*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

RiskA specific type of risk in the organisation Object Type: Risk

Symbol Type: RiskAttributes:

*Name: Name of the RiskDescription: Description of the Risk

IT Service GroupA specific service group provided to the business by Information Technology

Object Type: Product/ServiceSymbol Type: Information Service

Attributes:*Name: Name of IT Service Group

Identifier: An identifier for the IT Service Group

IT ServiceA service that forms part of a IT Service Category

Object Type: Product/ServiceSymbol 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 dividedObject Type: Product/ServiceSymbol Type: Information Service

Attributes:*Name: Name of the Schedule

Identifier: An identifier for the IT Service CategoryDescription: 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.

I nfastructureApp Class 1

InfrastructureApp Class 2

InfrastructureApp Class 3

InfrastructureApplications

Server Detail Model(Access Diagram (Physical)Depicts the configuration of the server in

terms of infrastructure applications.

Server A.1.i.a


InformationStore 4

LogicalDatabase 1

Application 1

Application 1.1

App 1/App 2Interface

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

the organisation


InfrastructureAppl ication 2

Infrastructure Application

Class List Model(Application System Type Diagram)

List the infrastructure applications that belongs to an infrastructure appl ication

class.

InfastructureApp Class 1



Infrastructure Application ClassRepresents a technology application c lass of the

infrastructure appl ication portfolio, e.g. network, DBMS.Object Type: Application System ClassSymbol Type: Application System Class

Attributes:*Name: Name of the Infrastructure Application

Class*Description: Description of the Infrastructure

Application Class

Infrastructure ApplicationAny infrastructure application package, e.g.

software development environment, operating system,middleware, office automation, network.

Object Type: Application System Type

Symbol Type: IT SystemsAttributes:

*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 TypeSymbol 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 ServerServer Environment: Environment the server is used in

Server Support: Type of support the server receives

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

App 1.1.cCharacteristic 1.1.b

Metric 1.1.a

Dimension1.1

Fact 1.1

Entity 1.A

Attribute1.1.b

Attribute1.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)

Strategical ly summarises the application portfolio on the highest level.

ApplicationClass 1

ApplicationClass 1.1

ApplicationClass 1.2

ApplicationClass 1.1.1

ApplicationCla ss 1.1.2

Application Class

Represents a business functional class of the applicationportfolio.

Object Type: Application System ClassSymbol Type: Application Sys tem ClassAttributes:

*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

Appl ication 1 Application 2

Application List Model(Application System Type Diagram)

List all the major applications within the organisation.

Application 1 Appl ication 2 Applica tion 3

Application Decomposition Model(Application System Type Diagram)

Decomposes a major application into sub-applications.

Appl ica tion 1

Applica tion 1.1 Application 1.2 Application 1.3

Application ModuleA module represents a logical subset of the functionali typresented by an application. The lowest level module

would be a function of the application, e.g. sc reen or report.Object Type: Module Type

Symbol Type: Module TypeAttributes:*Name: Name of the Application Module

*Description: Description of the Application Module

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

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

Inte rfaceApp 2/App 3

Interface

App 1/App 3Interface

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

Application 1Logical

Database 1

Application Technology Model(Access Diagram)List al l the minimum technology requirements to

deploy the business application.

Server Type 1

I nfrastructureApplication 1

I nfrastructure

Application 2

Applica tion 1

Application InterfaceAn application interface represents al l the connec tivity between two applications.

Object Type: Application System TypeSymbol Type: Application System Type

Attributes:*Name: Name of the Application Interface

*Description: Description of the Application Interface

Application1

Applica tion3

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 ofAttributes:*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 TypeSymbol 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 applications cost of ownership

Estimated Cost of Application: The estimated cost of new applicationsRetirement Date: Date application is to be retiredData Migrated: Indicate if a retired applications 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 ModelLevel 5 Task Detail Model(Function Allocation Diagram)

To further explain the detail of the Sub-process/Task/Activi ty such as ownership.

L3 Sub-processB1-2b

Product A.1

Version 1.0

App 1.1.a

BusinessRole 1

RAID E

Service 1.1.A.i

LocationType A.1.2

LocationA.1.i

Organisational Unit A.1

RAIDE

Application1

Job 1

RAIDEEquipmentType 2

Reference 1

Report 2

Document 1

Position A.2

Risk 1

Organisatio

nal UnitType 1.1

Variant Area1

RAIDE

RAIDE

Logical

Database 1

Level 4 Activity Model(eEPC)To provide an operational view of each sub-process with

the role accountabi lity for each activity, as wel l as any inputs or outputs.

Event 1

L4ActivityB1-2b.i

L4ActivityB1-2b.ii

Event 3 Event 5

Outcome 1Outcome 2

L4Activity

B1-2b.iiiL4

Activity

B1-2b.iv

L3Sub-process

B1-2a

L3Sub-process

B1-2c

Event 4

Level 5 Task Model(eEPC)To provide a step-by-step guide to each activi ty as a work

instruction or task.

L5 Task B1-2b.ii.a

L4Activ ityB1-2b.i

L5 Task B1-2b.ii.b

Event 3 Event 5

Outcome 1Outcome 2

L4ActivityB1-2b.iii

L4ActivityB1-2b.iv

Event 2

Level 2 Process Detail Model(Function Allocation Diagram)

To further explain the detail of the Process such as ownership.

L2Process

B1-2

MeasurementType 2.1.B

Product A.1

StrategicObject ive 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

L0

Enterprise Process A

L0

Enterprise Process B

L0

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

L1

Value Chain B2

L1

Level 2 Process Model(Value Added Chain Diagram)To provide a bus iness process view of the business that can be

assigned to a process owner and that can be measured.

ProcessB1-1

L2

ProcessB1-2

L2

ProcessB1-3

L2

Event Represents a triggering or resulting state.

Object Type: EventSymbol: EventAttributes:*Name: Name of the Event

Rule Outcome

Indicates different outcomes.Connection Type: leads toAttributes:*Connection Role: Description of the outcome.

Rule OutcomeIndicates different outcomes.Connection Type: leads toAttributes:

*Connection Role: Desc ription of the outcome.

Value Chain Ownership

Indicates the position that is the owner of the value chain.Connection Type: contributes toAttributes:*Connec tion Role: D(ecide)

Strategic Objective SupportIndicates whether the process supports the strategic

object ive direct ly on indirectly.Connection Type: supportsAttributes:*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: FunctionSymbol Type: Value Added ChainAttributes:*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


A Value Chain is cross-functional and has a profound impact on achieving

strategic objectives.Object Type: FunctionSymbol Type: Value Added ChainAttributes: *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 andtransforms the inputs into outputs. Object Type: FunctionSymbol Type: Value ChainAttributes:*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-processB1-2a

L3

Sub-processB1-2b

L3

Sub-processB1-2c

L3

Process OwnershipIndicates the position that is the

owner of the process.Connection Type: contributes toAttributes:

*Connection Role: D(ecide)

Sub-process (Level 3)A Sub-Process is a grouping of logically related Activities.

Object Type: FunctionSymbol Type: Value ChainAttributes:Identifier: The services 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 ExpertSynonyms: Synonyms to Process nameVersion: Version of the Sub-process

Task (Level 5)A single action that is executed as part of an Activity.

Object Type: FunctionSymbol Type: FunctionAttributes:*Name: Name of the Task*Process Level: Indicate the process level.

Choose from L1; L2; L3; L4; L5

*Description: Description of the TaskSource: Reference to documentation that

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

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

automated by a batch applicationManually: 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/rolein a sub-process.Connection Type: contributes toAttributes:*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: FunctionSymbol Type: FunctionAttributes:Identifier: The Sub-services ID & the

activitys 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 ActivitySource: 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 - SLABase Service Comments: Additional comments surrounding

the base service SLAFrequency: How often the activity is performedConstraints: Describe constraints to the activityVariations: Describe any variances in how the

activity is performed.

Version InformationIndicates the version information for the

specific document.Connection Type: lies onAttributes:*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 AreaA business area where the process varies from the norm.

Object Type: Functional ClusterSymbol Type: Functional BlockAttributes:*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

Informat ionClass 1.2

InformationCategory B

Document 1

Information Store 1

Document 2

Report 1

Informat ion

Category B

Information

Category A

Information Category List(Knowledge Structure Diagram)A l ist 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 SourceFunction allocation diagram)Depicts the various sources of the information element.

Characteristic1.1.a

Logical

Database 1

Metr ic 1.1.b

Characteristic1.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

Characteristic1.1.a

Calculation

Report 4

Measurement2.1.B.i

Measurement

2.1.B.iiMeasurement

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.....

MeasurementType 2.1.A


StrategicObjective 1.2.1

Document 1 Document 2

Document 3 Document 4

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

MeasurementCalculation

1.1.B

Application 1.1

Position A.1

Measurement2.1.B.i

LogicalDatabase 1

Measurement2.1.B.ii

Position 1

Position A.2

Position A.3

Ent ity 1.1

Attribute 1.1.a

App 1.1.a

Document 2

Characteristic1.1.a

Metric 1.1.a

Measurement Source(Function allocation diagram)

Depicts the various sources of the information element.

MeasurementType 2.1.A


MeasurementType 2.1.A.i

MeasurementType 2.1.A.ii

MeasurementPerspective 2

Measurement Type Hierarchy(DW structure)

To provide a logical view of the measurement types hierarchy used for process management.

Information Element: MetricDepicts a measurable attribute of the fact

Symbol Type: Key FigureObject Type: ERM attribute

Attributes: *Name: Name of the information element

Description: A description of the information element

Scorecard

Depicts a scorecard used within the businessSymbol Type: Communication Structure

Object Type: Cluster/Data modelAttributes:

*Name: Name of the ScorecardDescription: A logical business-focused description of the scorecard.





Measurement Perspectives(DW structure)A classification of the measurements used

by Anglo Platinum into various groups

Report List(Knowledge structure diagram)A l ist of the reports used within the

business

Report 1 Report 2

Report 3 Report 4

DimensionDepicts a business dimension, e.g.

organisation, time, or product.Symbol Type: Dimension

Object Type: Cluster/Data modelAttributes: *Name: Name of the dimension

Description: A description of the

dimension

FactDepicts a collection of key metrics, e.g.

tons mined.Symbol Type: Fact table


*Name: Name of the fact tableDescription: A description of the fact

Information ClassDepicts a grouping of information

Symbol Type: Knowledge categoryObject Type: Knowledge categoryAttributes:

*Name: Name of the Information ClassDescription: A logical business-focused

description of the Information Class

Information CategoryDepicts a grouping of information

Symbol Type: Documented knowledgeObject Type: Documented knowledge

Attributes: *Name: Name of the Information CategoryDescription: 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

Characteristic1.1.a

Characteristic

1.1.b

Characteristic1.1.c

Report

Depicts a reports used within the business

Symbol Type: Electronic DocumentObject Type: Information carrier

Attributes: *Name: Name of the Report

Information StoreDepicts a logical information store Symbol Type: Info cube


*Name: Name of the Information store

Information Element: CharacteristicDepicts a descriptive

attribute of the dimension.

Symbol Type:CharacteristicObject Type: ERM attribute

Attributes: *Name: Name of the

information elementDescription: A description

of the information element

Information Store List(DW structure)

A list of the information stores

InformationStore 1

InformationStore 2

InformationStore 3

InformationStore 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.

Measurement2.1.B.ii

Measurement2.1.B.i

Scorecard 1

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

Information

Class 1

InformationClass 1.1

InformationClass 1.2

Measurement TypeDepicts a measurement type

Symbol Type: Key figureObject Type: Entity type

Attributes: *Name: Name of the measurement

Identifier: An identi fier for the measurementDescription: A description of the measurement

Frequency: How often the measurement is usedMeasurement Type: Checked (True)

Measurement Importance: Select a levelFSR Availability Rating: Select a rating

Measurement PerspectiveDepicts a logical grouping of measurements

into the Scorecard perspectives.Symbol Type: Info CubeObject Type: Cluster/Data modelAttributes:

*Name: Name of the measurement perspectiveIdentifier: An identifier for the perspectiveDescription: A description of the perspective

Term

A term/concept that needs clarification in terms of its

meaning.Object Type: Technical TermSymbol: 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

Abbrevia tion 1

Abbrevia tion 2

Abbrevia tion 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: DocumentObject 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 TermSymbol: Technical Term

Attributes:*Name: The abbreviation

*Full name: The full name

Measurement

Depicts a measurement used within the business

Symbol Type: CharacteristicObject Type: Entity type

Attributes: *Name: Name of the measurementIdentifier: 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 FunctionObject Type: Function

Attributes: *Name: The calculation used to determine a measurement

Information Element CalculationDescribes the information element used to

determine a particular information elementSymbol Type: System FunctionObject 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

LogicalDatabase 1

LogicalDatabase 2

Logica lDatabase 3

Logical Databases Model(IE Data Model)

Strategical ly summarises the enterprise data on the highest level.

Logical Entities Model(IE Data Model)Depic ts the logical entities of a database and the relationship

between the entities.

Entity 1.1

Entity 1.2 Entity 1.3

Logical DatabaseRepresents a collection of data that is generally

associated with one application.Object Type: Cluster/Data ModelSymbol Type: Cluster/Data Model

Attributes:*Name: Name of the Logical Database

EntityLogical entities are things of significance that the business

wants to store information about. An entity is a group,

c lass or thing.Object Type: Entity Type

Symbol Type: Entity TypeAttributes:

*Name: Name of the Entity*Description: Description of the Entity

Unique AttributeAn attribute that uniquely identifies and describes a logical

enti ty.Object Type: ERM AttributeSymbol 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 AttributeSymbol Type: D Attribute (ERM)

Attributes:*Name: Name of the Attribute

*Description: Description of the Attribute

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

Entity 1.1

Table 1.1

Fie ld 1.1.a

Fie ld 1.1.b Att ribute 1.1.b

Attribute 1. 1. a

TableA physical table in a database, or a structured data store.

Object Type: TableSymbol Type: Table

Attributes:*Name: Name of the Table

*Description: Description of the Table

Field

A physical column or field in a table.Object Type: FieldSymbol 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 Area1.A

Subject Area1.B

Subject Area

A logical functional area in a logical database usually determined according to business functionali ty.

Object Type: Cluster/Data ModelSymbol Type: Cluster/Data ModelAttributes:

*Name: Name of the Subject AreaDescription: 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 Calcula tion

+

Description 1.1 a

-

Description 1.1 c

=

Description 1.1 b

Data Transformation RuleRepresent the data transformation requirements.

Object Type: FunctionSymbol Type: Transfer Rule

Attributes:*Name: Name of the Transfer RuleDescription: Description of the Transfer Rule

Database Ownership Model(Access Diagram)

Depicts the business and technical ownership of the Logical Database.

LogicalDatabase 1

Position 1

Position A.2

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

database.

LogicalDatabase 1

Infrastruc ture

Application 1

Infrastruc tureApplication 2

Server Type 1

Enterprise Architecture Meta-Model

Copyright

Real IRM Solutions (Pty) Ltd

2006

Version 01.03 March 2006


Information

Data Application Technology

Intra- Architectural

Tech nolog y

Application

Data

Information

Business Organisat ion

Business M iscellaneous

Connection Legend

Intra- Architectural

Tech nolog y

Application

Data

Information

Business Organisat ion

Business M iscellaneous

Connection Legend

Attributes

Occurrence Copy

Assignment

Multiple Sources

Attributes

Occurrence Copy

Assignment

Multiple Sources

To be updated with IM Endeavour requirements


Enterprise Architecture Process

Develop EAMeta-Model

L3

Develop EA Products

L3

Develop BusinessProcess Models

L3

DevelopInformation

Models

L3

Develop SolutionModels

L3

Plan EnterpriseArchitecture

L2

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 reality Meta-model adherence

Meet user requirements for EA products


L0 Enterprise Processes

L2 ProcessL1 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 ProductSchedule and PlanTreatment 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 PlatinumBusiness Process Model

07 December 2005

Version 2.03

Mine Ore Body

L0

Market andSell Platinum

L0

Manage the Business

L0

Find Platinum Source /Exploit Ore Reserves

L0

Create Capacity

L0

Locate Ore Body

L1

Perform EconomicEvaluation

L1

Grow andMaintain Market

L1

Manage Dispatchand Delivery

L1

Support the Business

L0

Manage Protection Services

Perform StrategicPlanning

L1

ManagePerformance

L1

Manage CorporateGovernance

L1

Manage StakeholderRelations

L1

ManageTransformation

L1

Produce RefinedProduct

L0

Concentrate Ore Smelt Concentrate Convert Matte

Perform DetailPlanning

L1

EstablishMine

L1

EstablishProcessing Plant

L1

Perform DetailDesign

L1

EstablishInfrastructure

L1

Manage CapitalInvestments

L1

Manage CapitalAnd Project Lifecycle

L1

Manage Capital And Project Lifecycle

Refine Product

L1

Schedule AndPlan TreatmentAnd Refinement

L1

Close Operation

L1

ConcentrateOre

L1

Smelt Concentrate

L1

Convert Matte

L1

Refine BaseMetals

L2

RefinePreciousMetals

L2

Manage Metallurgy

L1

Manage Informationand Technology

L1

Manage PhysicalAssets Lifecycle

L1

ManageHuman

Resources

L1

Manage Researchand Development

L1

ManageFinances

L1

ManageSupply Chain

L1

Co-ordinate SHERisk Management

L1

Manage ProtectionServices

L1

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

PerformProspecting

L2

PerformGeologicalEvaluation

L2

EstablishMineralRights

L2

DetermineNew Mine

Scope

L2

PerformFinancialModelling

L2

Perform MineModelling

L2

PerformEstimation

L2

Establish CapacityCreation Project Plan

L2

Establish Life ofOperations Costing

L2

Initiate Project

L2

Plan Project

L2

Execute andControl Project

L2

Close Project

L2

Establish BusinessCase

L2

Perform OperationsEngineering

L2

Perform DetailOperations Modelling

L2

Perform DetailOperations Design

L2

PerformShaft

Development

L2

EstablishSurface

Infrastructure

L2

PerformUndergroundDevelopment

L2

EstablishUndergroundInfrastructure

L2

Perform MineCommissioning

L2

BuildConcentrator

L2

Build Smelter

L2

Perform PlantCommissioning

L2

Build RefineryPlant

L2

PerformHousing

Development

L2

PerformHostel

Development

L2

Perform Admin BuildingDevelopment

L2

Perform CapitalForecasting

L2

Manage Investment

L2

Manage ProjectBudget

L2

Manage ProjectExecution /Integration

L2

Plan ProjectCash Flow

L2

Perform ProjectGovernance

L2

Perform Project RiskManagement

L2

Perform ProjectPrioritisation

L2

Perform ProjectSelection

L2

Perform CriticalResourse Planning

And Allocation

L2

Manage Project WBSStructures and Cost

L2

PerformScreening And

Selecting

L2

Perform ProjectEcexution

L2

Perform ProjectFund Approval

L2

PerformInvestmentHand Over

L2

PerformPost-Investment

Review

L2

Perform ProjectPre-Development

L2

Perform Study FundApproval

L2

ManageProject

L2

Plan Ore Extraction

L2

Mine Ore

L2

PlanLabour

L2

500 Day TurnaroundLabour Project

RehabilitateEnvironment

L2

Retrench andRedeploy Operations

L2

Operate Mine

L1

Support Operations

L1

Close Mine

L1

Crush Ore

L2

LiberateOre

L2

PerformPrimaryFlotation

L2

PerformSecondaryFlotation

L2

PerformTailingsDisposal

L2

PerformConcentrator

Sampling

L2

Desiree Naud

PerformConcentratorConsumableAdditioning

L2

Desiree Naud

ProcessWet Concentrate

L2

PerformElectric Furnace

Smelting

L2

PerformThickening AndBelt Filtration

L2

PerformOff GasCleaning

L2

Desiree Naud

ProcessMolten Furnace

Matte

L2

PerformSlag Cleaning Furnace

Smelting

L2

ProcessMolten Furnace

Slag

L2

PerformSmelter

Sampling

L2

Desiree Naud

PerformSmelter

ConsumableAdditioning

L2

Desiree Naud

PerformSmelterEffluent

Management

L2

Desiree Naud

ConvertDry Furnace

Matte

L2

ProcessMolten Converter

Matte

L2

Treat Off Gas

L2

Desiree Naud

ProcessMolten Converter

Slag

L2

PerformConverter

ConsumableAdditioning

L2

Desiree Naud

PerformConverterSampling

L2

Desiree Naud

Obtain Information forScheduling and Planning ofTreatment and Refinement

L2

Optimise Scheduleand Plan for Treatment

and Refinement

L2

Rehabilitate theEnvironment

L2

Retrench and Redeploythe Operations

L2

MarketProducts

L2

ManageCustomer

Service

L2

Manage CustomerMaster Data

L2

Manage BaseMetals Sales

L2

Manage PreciousMetal Sales

L2

Manage SalesFrom Smelter

L2

ManageBilling

L2

Manage Delivery

L2

ManageInter-company

Stock Transport

L2

DefineOrganisation and

Relationships

L2

Set EnterpriseStrategy

L2

DevelopLong-Term Plans

L2

Strategic Long Term Planning

DevelopTactical Plans

L2

PerformOperational

Planning

L2

Manage Risk

L2

Provide LegalServices

L2

Provide AuditServices

L2

Ensure BusinessContinuity

L2

Provide SecretarialServices

L2

Set CompanyPolicies

L2

Communicatewith Investment

Community

L2

Communicatewith Interested

and Affected Parties

L2

Communicate withGovernment

L2

Communicatewith Suppliers

L2

Manage JointVentures and otherBusiness Partners

L2

Manage BlackEconomic

Empowerment

L2

ManageMining Charter

L2

ManageSocio-economic

Development

L2

Manage Womenin Mining

L2

Manage Social andLabour Plan

L2

Develop Socialand Labour Plans

L2

Plan InformationTechnology

L2

Build CoreBusiness Solutions

L2

Run Infrastructure

L2

Run Core BusinessApplications

L2

Run SupportBusiness Applications

L2

Build SupportBusiness Solutions

L2

Build Infrastructure

L2

Manage Information

L2

Manage Knowledge

L2

Manage Payroll

L2

Manage HumanPerformance

L2

Perform HRDevelopment

L2

Manage EmployeeRelations

L2

Perform HR LabourManagement

L2500 Day Turnaround Labour Project

Manage PersonnelAdministration


Manage TimeAnd Attendance

L2

Perform TalentManagement

L2

ManageSocio-economic

Development

L2

PerformRecruitment

L2

PerformHR Cost Planning

L2

Perform HRLabour Control


ManageAccomodationAdministration

L2

Acquire PhysicalAsset

L2

Install andCommission

Physical Asset

L2

PerformAsset Tracking

L2

PerformPlant

Maintenance

L2

ProtectAssets

L2

Perform EngineeringChange Management

L2

Plan Research andDevelopment Efforts

L2

Conduct ResearchAnd Development

L2

Manage AccountsPayable

L2

ManageAccounts

Receivable

L2

Manage GroupProperty

L2

ManageFinance

Accounting

L2

Manage FixedAssets

L2

Manage ManagementAccounting

L2

ManageCorporate

Finance

L2

Manage Treasury

L2

Manage Banking

L2

Manage ShareOptions

Conduct ProtectionServices Investigation

L2

Provide AccessControl

L2

Monitor Access

L2

Manage Supply Chain Data

L2SAP FDDs

Manage SupplyChain Demand

L2SAP FDDs

Source Productsand Services

L2SAP FDDs

Supply Productsand Services

L2SAP FDDs

Settle SupplyChain Accounts

L2SAP FDDs

PerformMetal

Accounting

L2

Desiree Naud

ManageLaboratory

L2

Desiree Naud

Manage Utilities

L2

PerformOperational Logistics

L2

Manage SurfaceInfrastructure

L2

Provide MineTechnical Services

L2

Survey Mine

L2GMSI

PerformMineral Resources

Evaluation

L2

Direct andLead the

Enterprise

L2

Plan And Monitor TheBusiness

L2

Manage HygieneMeasurement And Monitoring

L2

SHE Process Modelling

Establish Task andWorking Environment

Conditions

L2


Define Individual AndTeam Actions

L2


Prevent Absent andFailed Defences

L2


Manage Incidents

L2


Manage Consequences

L2


Identify SHE Legaland Other Requirements

L2


Establish ActionManagement

L2


Establish IndividualCapabilities

L2


Manage PPE

L2


Perform Observation AndBehaviour Management

L2


Prevent Ventilation AbsentAnd Failed Defences

L2


Prevent Public Health AbsentAnd Failed Defences

L2


Manage EnvironmentMonitoring

L2


Prevent Medical Absent AndFailed Defences

L2


Manage Training

L2


Manage Safety MeasurementAnd Monitoring

L2


Manage Public Health

L2


Manage SHE Reporting

L2


EstablishOrganisationalRequirements

L2






Engage senior management in development of

high level processes





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


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


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

The non-core EA activities associated with quality control and

maintaining the integrity of the architectural framework and meta

data have been outsourced

Develop an EA Capability


Agenda

Background

Business

Drivers for change







needs


Toolset selection

ARIS

Utilities


Utilities Documentation

Information and Data Models Application Models Technology Models

Documentation

Learnings

The Way Forward

Governance


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


Business Process Analysis Tools

ARIS


Enterprise Architecture Tools

ARIS


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


ProcessProcess

DefinitionDefinition

ProcessProcess

ConfigurationConfiguration222

111

ProcessProcess

ExecutionExecution333

ProcessProcess

ControllingControlling444

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


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 DatabaseFunctional Allocation Diagrams Capturing Utility


Agenda

Background

Business

Drivers for change







needs


Toolset selection

ARIS

Utilities


Utilities

Documentation

Information and Data Models

Application Models Technology Models

Learnings

The Way Forward

Governance


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



Where sufficient content has been captured, reports are generated with detail of

roles and responsibilities allowing, in due course, for more equitable task loading



Manual processes for possible future automation have been identified


Business Process Models - 4L3 Develop EA Plan

SB.IT.01.05.03

L4Determine EA

Framework ChangeRequired

L3 Develop EA Plan

EA FrameworkApproved

SB.IT.01.05.02

L4Review ExistingEA Framework

SB.IT.01.05.01

L4Re

anglo platinum presentation to theea forum finding the...

Documents