zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA May 2015 A - - PowerPoint PPT Presentation

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

May 2015

A Journey to Asset Master Data

Angelo Koutsoukos, Manager

• Asset Stewardship

26 May 2015

A Journey to Asset Master Data – AMPEAK 2015 | 1

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Presentation Outline

• TfNSW

and the Asset Portfolio

• ASA

and Asset Management

• Current

landscape, issues and challenges

• Technology,

capability and processes

• Current

work in place

• Assets –

what are they?

• Asset

Classifications and the Information Model

• Where to

next in the journey?

A Journey to Asset Master Data – AMPEAK 2015 | 2

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

TfNSW’s Network

Network

• 43000 lane km of state roads
• 1505km of electrified overhead
• 1763km
• f mainline track
• 24 Bus Depots
• 1 Shipyard
• 10 Train Maintenance Centres
• 1 Light Rail

Maintenance Centre

• 9321 Bridges
• 370 Stations, 14 Stops, 107 Wharves

& Jetties

• Plus

bus stops, substations, transmission lines, CCTV, lifts, culverts, seawalls, passenger info

Fleet

• 2124 buses
• 1947 train carriages (144 diesel

and 1803 electric)

• 13 light rail

vehicles (65 carriages)

• 30 ferries
• Plus vessels/watercraft, road vehicles,

trailers, locomotives, wagons, track machines and plant

• $104bn in assets

A Journey to Asset Master Data – AMPEAK 2015 | 3

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

TfNSW and the ASA

Network Standards

& Services

Engineering Industry & Technical Development Safety, Quality, Environment

& Assurance

A Journey to Asset Master Data – AMPEAK 2015 | 4

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 5

Information over the life cycle

Asset Life Cycl·

e

Plan Acqui re

Asset data built up

• ver the life

cylce

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Current landscape

Agencies

• Multiple sources of

Asset Information (data and documents) across agencies

• Mostly

disparate IT systems with limited integration

• Over 300 systems - COTS, Bespoke

(including Excel/Access), ERP/EAMs

TfNSW

• Limited standards in place
• No common IT

platform (master source) in place for use and collaboration by

• thers

A Journey to Asset Master Data – AMPEAK 2015 | 6

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Current issues and challenges

• Lack of access and transparency
• Limited understanding of

location of data sources

• Loss of data over

the lifecycle

• Rework

due to low confidence, limited access in data

• Changes

in business model

• Lack of owners

requirements

• Decisions

not substantiated by factual and accurate data

• Lack of integrated data (silos of data)
• No common environment

A Journey to Asset Master Data – AMPEAK 2015 | 7

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Silos and loss of data

A Journey to Asset Master Data – AMPEAK 2015 | 8

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Traditional project delivery

Planning Development Design Operate & Maintain Construction Project Information / Knowledge Traditional approach (paper based and silos)

A Journey to Asset Master Data – AMPEAK 2015 | 9

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Technology, capability and processes

TfNSW has:

• embarked on a corporate

shared services Enterprise R esource P rogram (ERP) for TfNSW and Cluster agencies (e.g. Sydney Trains);

• committed

to leveraging off the ERP platform for Enterprise Asset Management (EAM)….the integrated landscape is to include spatial, non spatial and document requirements…where does BIM fit?

A Journey to Asset Master Data – AMPEAK 2015 | 10

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

BIM – Common Data Environment

Common Data Environment

Ad-hoc approach BIM approach

A Journey to Asset Master Data – AMPEAK 2015 | 11

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

BIM approach to projects

Planning Development Design Construction Project Information / Knowledge Traditional approach (paper based and silos) Digital approach (storage, access, exchange & collaboration) Operate & Maintain

A Journey to Asset Master Data – AMPEAK 2015 | 12

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Projects and BIM

Wyong to Newcastle Coal Rail Enhancement Program Wynyard Walk Oatley Station Upgrade k South West Rail Lin CBD and South East Light Rail Auburn Stabling Yard Inner West Light Rail Extension Epping to Thornleigh Third Track

A Journey to Asset Master Data – AMPEAK 2015 | 13

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset vs physical products

• The lowest level of architectural

design, the transition into physical implementation, defines the physical design down to configuration items

• These configuration items

fulfil functional requirements to enable required activities and capabilities to deliver service demands So what determines when an asset is created?

A Journey to Asset Master Data – AMPEAK 2015 | 14

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 15

When is it warranted to create an asset?

• major value asset against which work may be scheduled, costs and

maintenance history recorded and analysed

• high maintenance or operational critical asset
• required for parent Productive Unit grouping purposes (hierarchy)
• individually serialised where positional and maintenance history is

required

• safety or statutory requirements (e.g. calibration, heritage, clearances)
• operational or maintenance requirements to record statistical details

(e.g. usage, tonnage, days in service)

• configuration control requirements to be satisfied (e.g. original spec,

modifications and rotable fitment)

• requirements to record warranty details

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Current work in place – for all TfNSW assets

• Asset

Information Management Standard (AIMS)

• T MU AM

02001 ST

• Asset

classification system (ACS)

– Asset System, Class, Function & Type => defines Asset Object

• Asset

information model

– Engineering Technical Specification (TMC) linked with ACS and the Asset Register

• Standard library
• f

codes

– Locations, Corridors, Track codes – Asset Master Data linked with ACS

• Conventions

for standard naming and labelling

• Requirements

for the asset register

– Asset Structuring linked with ACS

A Journey to Asset Master Data – AMPEAK 2015 | 16

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 17

Asset information integration

• The asset register sits at the core and is the enabler for the

integration of related asset information

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset classes

Covers both Network and Fleet Assets

• Fixed (Facility,

Interchange, Feeder, Corridor) and Mobile (Fleet)

• High level Classes contain subordinate Infrastructure &

Systems Classes

A Journey to Asset Master Data – AMPEAK 2015 | 18

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset classifications

Each asset shall be defined according to the asset classification structure

• The asset classification structure comprises

the following levels:

– Level 1 - asset system – Level 2 - asset class – Level 3 - asset function – Level 4

• asset type,

which defines the level at which differing types of assets essentially provide the same function => linked to the asset together with its Technical Specification (variants in make and model or construction)

A Journey to Asset Master Data – AMPEAK 2015 | 19

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset classifications and the information model

§ § § § § § § § § § § §

Asset classifications Class – Function - Type Graphical Data

§ actual (location, position, spatial) attributes linked to an individual asset (an asset can have multiple graphical attributes)

Non-graphical Data Asset(s) Documents Class Function Type Component Sub-component

Documents § actual documents linked to the individual asset (an asset can have multiple documents) Data attributes § actual (physical, functional, condition,

• perational, organisational) attributes linked

to the individual asset (an asset can have multiple non-graphical attributes) Asset § Inherits the attribute requirements from the assigned Asset Function & Type § Inherits the technical specification requirements from the assigned TMC Asset Class Grouping of related Asset Functions Asset Function Grouping of related Asset Types Defines the data attributes to be captured Defines the attribute specification (name, type, format, unit of measure, min/max), common to an asset function, group of asset types or individual asset type Asset Type Defines the variation in types or series of assets performing the same function Together with the Asset Function defines the object within the Asset Register Aligned to a Technical Specification within the TMC framework Asset Specification (TMC) defines the material part list (inventory) defines the manufacturers warranty defines the build (components and sub components) for failure capture, analysis and reporting defines the maintenance plan § tasks (packaged into service schedules) § resources § tools § materials defines the failure modes, causes, effects and criticality (based on FMECA) relative to the failure of components

A Journey to Asset Master Data – AMPEAK 2015 | 20

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset breakdown structure

TfNSW Portfolio Type Nehvor<k Class Nehvor<k Type & No Nehvor<k Asset/System & No

Nehvo r<k Sub

Asset & No

Nehvor k A sset A ssembly & No

t

Co rri d or

Corridor Typ e/ I d Corri dor Asset/Syste m & Id Corridor Su b Asset/I d

Co r r i d or

Asse m b ly / Id

Feeder Feed e r Ty p e/ Id Feeder Asset / Syste m & Id Feeder S u b Ass et/I d Feeder Assembly/I d N etwo rk

\

I nt e r c h a n ge I n t e r c h a n ge

Typ e/ I d

I nt e rc h a nge Asset/Syste m & I d l n t:e r c h a n ge Su b Ass et/Id I nt e r c h a nge Assembl y / I d Fac i lity Fac i lity Ty p e/ I d Facility Ass et /Syste m & Id Faci lity S u b Ass e t / I d Fa cility

Ass embly / Id

Portfolio Type

f!I

eet Class

f!leet Type & Set No Fleet Su b-Type & No Fleet

Asset/System & No

f!leet S u b Asset & No

~

T r a i n T r a i n Se t Ty p e/ I d T r a i n Car Ty p e/ Id

Asset/Syste m & Id

S u b Asset / Id Fleet

~

Lig h t Ra i l Lig ht Ra il Set Ty p e/ I d Lig h t Ra i l Ca r Ty p e/ I d Ass et /Syste m & Id S u b Asset/Id

A Journey to Asset Master Data – AMPEAK 2015 | 21

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset classifications and the asset breakdown structure

A Journey to Asset Master Data – AMPEAK 2015 | 22

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset register

Asset Register and Asset Master Data

What Where Classifications

• Class
• Function
• Type

Asset Reference Data

• Corridor / Yard
• Location
• Track & Basecode
• Position
• Room
• Kilometerage
• GPS (Lat / Long)

Asset Id

• ID
• Serial No
• Barcode
• Label
• Description
• Status

Organisation Data

• Owner
• Operator
• Maintainer

Design/Construct Data

• Technical Specification
• Manufacturer
• Installation Date
• Warranty Date
• Design Life

Asset Attribute Data

• Heritage?
• Environmental?
• Design & Nameplate?
• Survey?
• Operational?
• Condition?

Finance Data

• Capitalised
• Acquisition Cost

General Specific All Classes/Functions By Class/Function

A Journey to Asset Master Data – AMPEAK 2015 | 23

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Asset master data requirements

Align with core business functions & processes to support and substantiate decisions

• Asset

data and attributes associated with assets contained in an asset register are to be defined and categorised as:

– configuration – includes physical and functional data related to identification and static referencing of manufacturer details, asset construction, asset procurement, technical characteristics, heritage and physical relationship with other assets – location – physical and geospatial attributes and spatial relationship with other assets – condition – past and current condition including residual life –

• perational

– usage, tonnage, restrictions, criticality, availability and environmental factors – maintenance – management and recording of maintenance activities –

• rganisational

–

• wner, operator

and maintainer – financial – costing from capital acquisition,

• peration,

maintenance to disposal

A Journey to Asset Master Data – AMPEAK 2015 | 24

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 25

LOD 200

Challenge!

• How is the as-built model extended to O&M?
• What data is extracted out of the model for O&M EAM systems?
• How is the as-built model maintained and shared over the life cycle?

LOD 100 LOD 300 LOD 500 LOD 400 Concept Design Model Construction Model As-Built Model As-Maintained Model Federated Model Drawings Schedules Analysis Visualisation QS Takeoff Fabrication 3D Site Construction Cost

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA

Where is the journey headed?

• ASA

to further develop detailed Asset Information requirements, Master Data Coding Standards and Libraries, including document and drawing requirements (including CAD)

• TfNSW

Enterprise Asset Management (EAM) system to align with ASA Standards

• information
• TfNSW

looking to implement BIM beyond pilot (from 2D to use of 3D models – moving to 4D & 5D with the aim to handover a fully coded digital asset

• Alignment
• f EAM and BIM

A Journey to Asset Master Data – AMPEAK 2015 | 26

zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 27

Questions?