zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA May 2015 A - PowerPoint PPT Presentation

A Journey to Asset Master Data Angelo Koutsoukos, Manager - Asset Stewardship zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA May 2015 A Journey to Asset Master Data – AMPEAK 2015 | 1 26 May 2015

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? zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA • Asset Classifications and the Information Model • Where to next in the journey? A Journey to Asset Master Data – AMPEAK 2015 | 2

TfNSW’s Network Network Fleet • 43000 lane km of state roads • 2124 buses • 1505km of electrified overhead • 1947 train carriages (144 diesel and 1803 electric) • 1763km of mainline track • 13 light rail vehicles (65 carriages) • 24 Bus Depots • 30 ferries • 1 Shipyard • Plus vessels/watercraft, road vehicles, • 10 Train Maintenance Centres trailers, locomotives, wagons, track • 1 Light Rail Maintenance Centre machines and plant • 9321 Bridges zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA • 370 Stations, 14 Stops, 107 Wharves & • $104bn in assets Jetties • Plus bus stops, substations, transmission lines, CCTV, lifts, culverts, seawalls, passenger info A Journey to Asset Master Data – AMPEAK 2015 | 3

TfNSW and the ASA Network Standards Industry & Technical & Services Development zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA Engineering Safety , Quality, Environment & Assurance A Journey to Asset Master Data – AMPEAK 2015 | 4

Information over the life cycle Asset Life Cyc l· e Plan Acqu i re Asset data bu ilt up over the l ife cylce zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 5

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 zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA • Limited standards in place • No common IT platform (master source) in place for use and collaboration by others A Journey to Asset Master Data – AMPEAK 2015 | 6

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 zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA • 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

Silos and loss of data zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 8

Traditional project delivery Traditional approach (paper based and silos) Project Information / Knowledge zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA Planning Development Design Construction Operate & Maintain A Journey to Asset Master Data – AMPEAK 2015 | 9

Technology, capability and processes TfNSW has: • embarked on a corporate shared services (ERP) for Enterprise R esource P rogram 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 zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA spatial, non spatial and document requirements …where does BIM fit? A Journey to Asset Master Data – AMPEAK 2015 | 10

BIM – Common Data Environment Common Data Environment zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA Ad-hoc approach BIM approach A Journey to Asset Master Data – AMPEAK 2015 | 11

BIM approach to projects Digital approach (storage, access, exchange & collaboration) Project Information / Knowledge Traditional approach (paper based and silos) zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA Planning Development Design Construction Operate & Maintain A Journey to Asset Master Data – AMPEAK 2015 | 12

Projects and BIM Wyong to Newcastle Coal Rail CBD and South East Light Rail Auburn Stabling Yard Oatley Station Upgrade Enhancement Program zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA South West Rail Lin Inner West Light Rail Extension k Wynyard Walk Epping to Thornleigh Third Track A Journey to Asset Master Data – AMPEAK 2015 | 13

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 zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA demands So what determines when an asset is created? A Journey to Asset Master Data – AMPEAK 2015 | 14

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) zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA • configuration control requirements to be satisfied (e.g. original spec, modifications and rotable fitment) • requirements to record warranty details A Journey to Asset Master Data – AMPEAK 2015 | 15

Current work in place – for all TfNSW assets • Asset • Standard library of codes Information Management Standard – Locations, Corridors, Track (AIMS) - T MU AM codes 02001 ST • Asset classification system – Asset Master Data linked with ACS (ACS) • Conventions for standard – Asset System, Class, Function naming and labelling & Type => defines Asset • Requirements for the asset Object zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA • Asset information model register – Engineering Technical – Asset Structuring linked with Specification (TMC) linked with ACS ACS and the Asset Register A Journey to Asset Master Data – AMPEAK 2015 | 16

Asset information integration • The asset register sits at the core and is the enabler for the integration of related asset information zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 17

Asset classes Covers both Network and Fleet Assets • Fixed (Facility, Interchange, Feeder, Corridor) and Mobile (Fleet) • High level Classes contain subordinate Infrastructure & Systems Classes zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 18

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) zyxwvutsrqponmlkjihgfedcbaZYXWVUTSRQPONMLKJIHGFEDCBA A Journey to Asset Master Data – AMPEAK 2015 | 19