asset information management - transport for nsw › system › files › media › asa_stand… ·...

TN 092: 2014

Asset Standards Authority

© State of NSW through Transport for NSW of 1

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0

Technical Note TN 092: 2014

Subject: Publication pending - T MU AM 02002 TI Asset Classification Structure

For queries regarding this document [email protected]

www.asa.transport.nsw.gov.au

Issued date 30 October 2014 Effective date 30 October 2014

This technical note is issued by the Asset Standards Authority to advise that document

T MU AM 02002 TI Asset Classification Structure, Version 1.0, which is referred to in

Appendix A of standard T MU AM 02001 ST Asset Information Management, Version 1.0, is not

published on the ASA website. T MU AM 02002 TI is currently being developed and its

publication is pending.

Authorisation

Technical content prepared by

Checked and approved by

Interdisciplinary coordination checked by

Authorised for release

Signature

Name Rana Roy Angelo Koutsoukos Toby Horstead Graham Bradshaw

Position Asset Reliability Specialist

Manager Asset Stewardship

Principal Manager Network and Asset Strategy

Principal Manager Network Standards & Services

A3845553

mailto:[email protected]

http://www.asa.transport.nsw.gov.au/

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0

Asset Information Management

T MU AM 02001 ST

Standard

Version 1.0

Issued Date: 30 October 2014

Important Warning This document is one of a set of standards developed solely and specifically for use on the rail network owned or managed by the NSW Government and its agencies. It is not suitable for any other purpose. You must not use or adapt it or rely upon it in any way unless you are authorised in writing to do so by a relevant NSW Government agency. If this document forms part of a contract with, or is a condition of approval by, a NSW Government agency, use of the document is subject to the terms of the contract or approval. This document may not be current. Current standards are available for download from the Asset Standards Authority website at www.asa.transport.nsw.gov.au. © State of NSW through Transport for NSW

T MU AM 02001 ST Asset Information Management

Version 1.0 Issued Date: 30 October 2014

Standard governance

© State of NSW through Transport for NSW

Owner: Manager Asset Stewardship, Asset Standards Authority

Authoriser: Principal Manager Network and Asset Strategy, Asset Standards Authority

Approver: Director, Asset Standards Authority on behalf of ASA Configuration Control Board

Document history

Version

1.0

Summary of change

First issue

For queries regarding this document, please email the ASA at

[email protected]

or visit www.asa.transport.nsw.gov.au

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0



© State of NSW through Transport for NSW Page 3 of 42

Preface

The Asset Standards Authority (ASA) is an independent unit within Transport for NSW (TfNSW)

and is the network design and standards authority for defined NSW transport assets.

The ASA is responsible for developing engineering governance frameworks to support industry

delivery in the assurance of design, safety, integrity, construction, and commissioning of

transport assets for the whole asset life cycle. In order to achieve this, the ASA effectively

discharges obligations as the authority for various technical, process, and planning matters

across the asset life cycle.

The ASA collaborates with industry using stakeholder engagement activities to assist in

achieving its mission. These activities help align the ASA to broader government expectations of

making it clearer, simpler, and more attractive to do business within the NSW transport industry,

allowing the supply chain to deliver safe, efficient, and competent transport services.

The ASA develops, maintains, controls, and publishes a suite of standards and other

documentation for transport assets of TfNSW. Further, the ASA ensures that these standards

are performance based to create opportunities for innovation and improve access to a broader

competitive supply chain.

This standard provides information regarding the requirements for asset information

management for assets owned by TfNSW across the asset life cycle. This standard sets the

high-level requirements for asset handover, asset information management, the asset

information system and defines ownership of asset information systems and its associated data.

This standard has been approved by the ASA Configuration Control Board and is a first issue.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




Table of contents

1. ............................................................................................................................................5 Introduction

2. ...................................................................................................................................................5 Purpose2.1. ..................................................................................................................................................................... 5 Scope

2.2. ............................................................................................................................................................. 6 Application

3. ...........................................................................................................................6 Reference documents

4. ...........................................................................................................................6 Terms and definitions

5. ...............................................................................9 Asset register and asset information ownership

6. ..................................................................................................................................9 Asset information

7. ...............................................................................................................10 Asset register requirements7.1. ................................................................................................................................... 11 Reasons to create assets

7.2. .......................................................................................................................... 12 Unique identification of assets

7.3. .............................................................................................................. 12 Assets across the modes of transport

7.4. ...................................................................................................................................................... 13 Asset classes

7.5. ..................................................................................................................................................... 13 Asset portfolio

7.6. ................................................................................................................................................... 15 Asset hierarchy

7.7. ............................................................................................................................... 22 Rotable assets and tracking

7.8. ............................................................................................. 23 Asset capitalisation and the fixed asset register

7.9. ......................................................................................................... 23 Linear and discrete assets and attributes

8. .........................................................................................24 Asset classification structure framework8.1. ............................................................................................................................ 25 Asset classification structure

8.2. ............................................................................................. 27 Asset classifications and the information model

9. ........................................................................................................29 Asset information requirements9.1. ............................................................................................................................................................ 29 Asset data

9.2. ................................................................................................................................................ 30 Asset documents

9.3. .............................................................................................................................................. 30 Information quality

9.4. ...................................................................................... 30 Pre-commissioning asset information and handover

9.5. ..................................................................................................... 32 Exchange of asset information at handover

9.6. ............................................................................................................ 33 Post-commissioning asset information

9.7. ................................................................................................................................ 34 Disposal asset information

9.8. ............................................................................................................................ 35 Supporting asset information

10. ..............................................................................35 Events triggering changes to asset information

11. ...........................................................................................36 Asset information system requirements

12. .............................................................................................37 Operator and maintainer requirements

13. .........40 Asset information system ownership and custodianship of the information repositories

Appendix A – Asset classification structure framework............................................................................41 Appendix B – Suggested reading .................................................................................................................42

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




1. Introduction

The Assets Standard Authority (ASA) is committed to effective and efficient management of

Transport for New South Wales (TfNSW) assets. The ASA is collaborating with other

government and non-government organisations to continuously improve the capability,

performance and condition of the assets over the full life cycle.

This standard defines the asset information management system requirements for TfNSW

owned assets over their life cycle or portion thereof. The requirements ensure consistency,

accuracy and completeness of asset information.

The ASA expects to develop a series of related standards on specific asset coding, asset data

requirements and data standards relevant to each mode of transport and asset class for use by

Authorised Engineering Organisations (AEO) and service providers.

It is essential to ASA that asset managers and maintainers are able to demonstrate that assets

and their asset information is managed efficiently and that those assets will support TfNSW

service outcomes in the long term.

2. Purpose

The objective of this document is to inform stakeholders of the requirements for asset

information related to all assets owned and managed by TfNSW across the asset life cycle. It

sets high level requirements for asset handover, asset information management and the asset

information system as well as clarity of ownership of the asset information systems and data.

The document also specifies an asset classification structure to support a common structure,

terminology and naming for the assets to enable ease of identification, collaboration, collection,

exchange, access and reporting of the asset information.

2.1. Scope

This standard establishes the requirements of an asset information management system

including the asset register and associated asset information. This standard defines an asset

classification framework and structure required to be used in the development and maintenance

of the asset register. This standard also defines how to identify the need to create assets and

how they are to be classified and grouped.

Asset information requirements presented in this standard cover the whole of life management

of assets required to support and substantiate decisions made over the life cycle that includes

but are not limited to the following:

• finance management requirements including asset capitalisation and whole-of-life costs

• asset handover requirements including asset acceptance information Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• asset configuration change requirements including asset type approvals or sub-component

type approvals, new assets, configuration and operational changes including changes in

asset strategy and concessions to standards

This standard covers all life cycle activities that affect the functionality, performance and

integrity of TfNSW assets or systems.

2.2. Application

This standard applies to TfNSW, transport cluster agencies, AEOs and service providers

involved in the planning, delivery, operation, maintenance and disposal of assets across the

transport portfolio. This standard shall be applied during all phases of the asset life cycle.

This standard is mandated to be used by organisations, service providers or project developers

that perform asset management related services to TfNSW, including AEOs, non-AEOs and

their suppliers involved in defining, designing, implementing, commissioning, integrating into the

operating network any new or altered assets or systems. This standard also applies to the

decommissioning and disposal of assets.

The standard applies to asset information management with respect to the asset information

system, asset register and associated asset information of assets owned by TfNSW and

operated and maintained by TfNSW agencies and service providers.

3. Reference documents

Transport for NSW standards

T MU AM 02002 TI Asset Classification Structure

Legislation

Disability Discrimination Act 1992

4. Terms and definitions

The following terms and definitions apply in this document:

AEO Approved Engineering Organisations

ASA Asset Standards Authority

asset is something that has potential or actual value to an organisation. Value can be tangible

or intangible, financial or non-financial. Tangible assets are physical assets which refer to

equipment, inventory and properties owned by the organisation. Tangible assets are the

opposite of intangible assets, which are non-physical assets such as leases, brands, digital

assets, use rights, licences, intellectual property rights, reputation or agreements Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




asset information is the combined set of data (graphical and non-graphical) and documents

(drawings, manuals, plans, certificates) required to support the management of assets over the

life cycle

asset information management is the discipline of managing the asset related data and

documents to a sufficient quality to support organisational objectives and outcomes

asset information repository a recognised physical or electronic location for the storage and

management of asset information

asset information repository custodian a person responsible for managing an asset

information repository and the processes related to the creation and maintenance of the

information and provision of access to the information in the repository

asset information system a set of interrelated repositories of structured asset information and

related processes required to manage the asset portfolio over the life cycle

asset life the period from conception to end-of-life

asset portfolio assets that are within the scope of the asset management system

asset register contains the definition and description of each asset in the asset portfolio. The

asset register includes all the data required to ensure unique identification of the asset

asset system set of assets that interact or are interrelated. An asset system could also be

considered an asset

asset type assets having common characteristics that distinguish them separately (different

manufacturer, different specification and/or different components) within an asset function

attribute piece of data forming a partial description of an object or entity

availability the measure of the percentage of time that an item or system is available to perform

its designated function

CCB refers to the Configuration Control Board. Person or a group of persons assigned

responsibility and authority to make decisions on the configuration

conditional failure a defect is a conditional failure when it has the potential to become a

functional failure and occurs when the asset condition is outside a maintenance threshold but it

is still able to perform its function and does not yet have operational consequences (may need

to be monitored as part of condition assessment or repaired)

configuration interrelated functional and physical characteristics of an asset defined in asset

configuration information

configuration change refers to a change in functional and/or physical configuration of an asset

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




corridor is a zonal area within a boundary and defined by a start and end node that contains

Heavy Rail, Light Rail, Road or Ferry infrastructure assets to support the operation of transport

fleet services

data information collected and stored but not yet interpreted or analysed (graphical and non-

graphical)

document information for use in the briefing, design, construction, operation, maintenance and

disposal of a project or asset, including but not limited to correspondence, drawings, schedules,

specifications, calculations, spreadsheets, reports, manuals and certificates

drawing static, printed or geographical representation of part or all of a project or asset

dynamic data data collected over time about how the asset is operating, performing, its

condition, work done and measurements which change through its operation and maintenance

functional failure a defect is a functional failure, when the equipment cannot fully perform its

design function and causes immediate operational consequences such as train delays or loss of

power (subject to the level of available redundancy)

graphical data data conveyed using shape and arrangement in space

interchange is where customers join or transfer between modes of the transport system,

including combinations of rail, bus, car, taxi, ferry, light rail, bicycle and walking

life cycle stages for an asset from recognition of need through to disposal and any residual

risks or liability period

maintainability a characteristic of design and installation, expressed as the probability that an

item will be restored to operating condition, within a given period of time, using prescribed

procedures and resources

maintenance in the context of this document has two components:

• routine maintenance, also referred to as recurrent maintenance. Is a collective of all

preventative and repair activities excluding renewals. Includes planned inspections,

preventative maintenance, corrective maintenance and emergency response

• renewals maintenance, also referred to as capital maintenance or major periodic

maintenance (MPM). This includes the cyclic renewal and upgrading of assets to avoid

deterioration in their condition to ensure long term asset performance and financial

sustainability

MTBF mean time between failures. Is the predicted elapsed time between inherent failures of a

system during operation

MTTR mean time to repair. Is a basic measure of the maintainability of repairable items

non-graphical data data conveyed using alphanumeric characters Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




reliability the probability that a specified item will perform a specified function within a defined

environment, for a specified length of time

static data (or configuration data) defines the assets themselves (their design data) and the

normal conditions in which they operate and interact with other assets

TMP technical maintenance plan identifies which items are to be maintained, what maintenance

tasks are to be performed (packaged as service schedules), when (frequency, conditional or

statistical trigger) and where the maintenance tasks are to be performed including required

materials and consumables and tools and equipment

5. Asset register and asset information ownership

The asset register, associated asset information including data and documents are owned by

TfNSW.

A range of asset information is in existence and is continually developed by TfNSW and parties

working directly or indirectly with TfNSW. The ASA is the delegated owner of the asset register

and associated asset information. Asset information is generally restricted to that defined in

Section 9 of this document and is necessary for the effective management and sustainability of

the assets that form the TfNSW asset portfolio.

6. Asset information

Asset information is the combined set of data both graphical and non-graphical, and documents

including drawings, manuals, plans, certificates required to support the management of assets

over the life cycle. Figure 1 shows how asset information is linked to the asset register:

Figure 1 – Asset register link to asset data and documents

Accurate and complete asset information will support and substantiate key decisions taken to

ensure the following:

• maintain the condition and long term value of transport assets to ensure delivery of

required services by achieving the following: Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




o improving effectiveness on investment decisions based on total life cycle costs and

taking into consideration enterprise risk management impact areas such as safety,

security and environment

o improving effectiveness of repair and replace decisions through greater knowledge of

asset condition and utilisation

o enhancing the life of the assets through the optimisation of maintenance plans

• improve the efficiency and sustainability of services and operations by:

o reducing downtime by reducing mean time to repair (MTTR)

o improved reliability by increasing mean time between failures (MTBF)

Decisions may be based on the asset location, condition including age and remaining life,

failure probability and consequence, resource constraints, spares availability, regulatory

compliance, business priorities and whole of life costs.

The asset information shall also be used to support to following activities:

• planning (design, construct/procure), delivery (test, commission, handover) and

maintenance (maintain, refurbish, renew) and asset disposal

• compliance to relevant asset management standards and legislative requirements

• monitoring performance, condition and reliability

• asset management accountability

• managing risk

7. Asset register requirements

The asset register integrates associated asset information as well as providing a historical

record of both financial and non-financial information over each asset's life cycle.

The asset register shall provide a defined and structured inventory of what assets are owned,

operated and maintained by an entity and shall be used to determine and report on:

• the condition and integrity of the assets

• the configuration of the assets

• the location of the assets

• the history of work performed and future planned and forecasted work

• the age, expected life and remaining life of the assets

• when the assets need to be repaired, replaced or disposed

• maintenance compliance

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• maintenance effectiveness including work arising and repeat failures

• the asset maintenance plan and annual works plan including backlog

• the operational consequence (delays) resulting from asset failures

• the reliability and performance of the assets

• the life cycle costs including initial asset capital cost, accumulated maintenance costs,

depreciation and disposal cost

• the utilisation (capacity) of the assets

• the operational criticality

Figure 2 illustrates how the asset register sits at the core and is the enabler for the integration of

related asset information required to support and manage asset management activities over all

phases of the life cycle:

Figure 2 – Integrated asset information framework model

7.1. Reasons to create assets

Assets shall be created in the asset register under any of the following conditions:

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

maintenance history recorded and analysed. An asset may not be a physical asset, it may

include software and information

• the asset is a high maintenance or operational impact asset

• the asset is required for parent hierarchy grouping purposes

• the asset is a critical asset which is individually serialised and for which service life

positional and maintenance history is required

• there are safety or statutory requirements for identifying the individual asset Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• there are operational or maintenance requirements to record statistical details

• there are configuration control requirements to be satisfied including the management of

type approved assets and components including assets (or products) under trial

• there are requirements to record and manage warranty details against the asset

• to identify total cost of ownership or life cycle costs

• to assess condition over its service life

If an asset does not fall within any of the above categories, it is unlikely to be needed for entry

to the asset register.

7.2. Unique identification of assets

Assets in the asset register shall have a unique identification.

The requirements for an asset identifier are to ensure the information system stores a unique

identifier that enables allocation of data and documents against a particular asset located or

fitted to a fixed functional 'hole' at a geographic point in the system, against a linear asset or

mobile asset. The unique identifier shall contain the following:

• a unique number, usually system generated that stays with the asset for the whole of life

that enables searching for and tracking of assets and serves as the primary key to link

related asset data, attributes and documents

• a structured code that provides the primary means to identify the asset uniquely in the

operating environment and for maintenance purposes. This may contain references to its

location, asset function, kilometerage, site label or serial number to ensure uniqueness.

7.3. Assets across the modes of transport

There are seven modes of transport within the TfNSW cluster which are listed below. All assets

within the asset register shall align with one of these seven modes.

• heavy rail

• light rail

• road

• ferry

• bus

• rapid transit

• active Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




7.4. Asset classes

There are four primary asset hierarchy groups used to contain assets that exist across the

various transport modes, as shown in Figure 3. These assets are categorised by asset class

within the four groups listed below:

• fixed network infrastructure assets and systems in corridors and facilities

• mobile assets for fleet and plant

Infrastructure assets exist within the transport corridors and facilities. Facilities may exist within

a corridor for example stations, signal boxes or electrical substations, or may stand alone, for

example an operations centre, warehouse or training centre.

Facilities may also exist within a larger facility. For example a communications room or building

services room can exist within a station.

Asset Classes included at this level

Asset Classes related to the above Facilities or Corridors

Fixed Mobile

Facilities

InterchangesRest AreasElectrical FacilitiesSignalling FacilitiesCommunications FacilitiesServices FacilitiesMaintenance FacilitiesLogistics FacilitiesOperations FacilitiesTraffic Facilities

Corridor / Yard

Corridor Fleet

TrainsLight Rail VehiclesBusesFerriesWagonsLocomotivesMobile Heavy Plant & VehiclesRoad Vehicles

Plant

Minor Plant & Equipment

Network Infrastructure (Corridor & Facility) Onboard Systems (Fleet)

Rail Signalling EquipmentRail Control EquipmentControl SystemsPneumatic SupplySubstation EquipmentAerial Lines & Cable FeedersOverhead TractionEarthing, Bonding & Electrolysis EquipmentCommunications EquipmentCommunications LicencesTechnology SystemsSecurity EquipmentCustomer Information EquipmentCondition Monitoring EquipmentBuilding & Tunnel ServicesCombined Service RoutesRoad Traffic Equipment

TrackTurnoutsRoadsPavement MarkingEarthworks & GeotechLevel CrossingsBridgesDrainage & CulvertsTunnelsMisc StructuresBuildingsFencing & BarriersHardware, Software & LicencesTicketingProperty & LandscapingSignageNavigation EquipmentFixed Plant

Train SystemsLight Rail SystemsBus SystemsFerry SystemsWagon SystemsLocomotive SystemsMobile Heavy Plant & Vehicle Systems

Asset Classes related to the above Fleet

Figure 3 – Asset class relationship within the asset hierarchy

7.5. Asset portfolio

Assets in the asset portfolio held in the asset register shall be grouped and structured in

accordance with the asset classification framework defined in Section 8.

Refer to Appendix A for a sample asset classification structure applied to TfNSW assets. Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




The asset register shall include the following assets:

• facilities and interchanges

o interchanges including stations, stops, wharves, and car, bus, and cycle parking

o electrical facilities including substations, sectioning huts, distribution substation and

external low voltage supplies

o signalling facilities including signal complexes and enclosures

o communications facilities including communications rooms and enclosures

o building services facilities

o maintenance facilities

o logistics facilities

o operations facilities including drivers and training facilities

o traffic facilities

o rest areas

• corridor for heavy rail, light rail, rapid transit, road and ferry

• fleet including passenger trains, light rail vehicles, ferries, buses, mobile heavy plant and

track machines, locomotives, wagons, recording vehicles, road vehicles and their

associated fleet systems

• plant including fixed and mobile plant and equipment

• civil structures including bridges, drainage and culverts, tunnels, earthworks and geotech,

buildings, level crossings, fencing and barriers, including:

o miscellaneous facility structures such as access ramps, stairs, concourses, platforms,

canopies, plinths, jetties, moorings, piers, pontoons, slipways, dry docks, inspection

pits and bike lockers

o miscellaneous corridor structures such as airspace developments, gantries, towers,

trackslabs, walkways, cycleways, sea walls and access roads

• track including mainline track and sidings, turnouts, buffer stops, lubricators and insulated

joints

• road pavement and marking

• electrical substation including traction, non traction substation and distribution equipment

and SCADA

• electrical cable feeders, aerial lines and pole equipment

• overhead traction including overhead wiring and equipment and overhead structures

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• rail signalling and control equipment including trackside signalling equipment, level

crossing protection, ATP, interlockings, workstations, telemetry, pneumatic air supply,

power supply and cables

• control systems and technology systems

• telecommunications including customer information indicators and clocks, audio and public

address, security help points and CCTV, radio, network and terminal equipment, licences,

cables and condition monitoring equipment

• services including lifts, escalators, fire management, heating / air conditioning / ventilation

(HVAC), low voltage electrical, lighting, and hydraulic water, sewer, and drainage systems

• combined service routes and underline crossings

• hardware, software and licences

• wayfinding and signage

• earthing, bonding and electrolysis

• property and landscaping

• ticketing

• road traffic control equipment

• navigation equipment

7.6. Asset hierarchy

An asset hierarchy provides a logical representation of the asset relationship within the asset

register. Assets shall be defined at a number of different levels within the hierarchy. The asset

hierarchy ensures the following:

• assets can be viewed in a logical way in reference to how they physically relate with other

assets

• assets can be grouped in a way that they are managed and maintained

• all assets are covered

• asset specific, parent or zonal examinations are possible

• reporting at different levels

Assets from within one asset class may form part of a hierarchy with assets from another asset

class.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




7.6.1. Corridors

A corridor is a zonal area containing heavy rail, light rail, road or ferry infrastructure assets to

support the operation of fleet services. A corridor includes the heavy rail corridor, light rail

corridor, road / T Way corridor, ferry corridor and stabling yard. Refer to Figure 4 for images of

corridors across various transport modes.

1 2

3 3

3

Figure 4 – Examples of corridors and stabling yard across various transport modes

Each corridor shall include the following infrastructure assets where applicable:

• civil structures including bridges, drainage and culverts, tunnels, earthworks and geotech,

buildings, level crossings, fencing and barriers, including:

o miscellaneous corridor structures such as airspace developments, gantries, towers,

trackslabs, walkways, cycleways, sea walls and access roads

• track including mainline track and sidings, turnouts, buffer stops, lubricators and insulated

joints

• road pavement and marking

1 © State of NSW through Sydney Trains. All rights reserved. 2 © Roadrunnerz45. Permission granted under the terms of the GNU Free Documentation License. 3 © State of NSW through Transport for NSW.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• overhead traction including overhead wiring and equipment and overhead structures

• rail signalling and control equipment including trackside signalling equipment, level

crossing protection, ATP and pneumatic air supply

• services including fire management, heating / air conditioning / ventilation (HVAC), low

voltage electrical and lighting, and hydraulic water / sewer / drainage systems

• combined service routes and underline crossings


• earthing, bonding and electrolysis


• road traffic control equipment

• navigation equipment

7.6.2. Facilities and Interchanges

An interchange is a zonal area containing stations, stops, wharves, taxi ranks and car / bus /

cycle parking infrastructure assets to allow the customer to join or transfer between modes of

transport. An interchange would include at least one of the following: train station, light rail stop,

bus stop, ferry wharf, taxi rank and car / bus / cycle parking area. Refer to Figure 5 for images of

interchanges.

4 5

6 7

Figure 5 – Examples of various transport interchanges

4 © State of NSW through Sydney Trains. All rights reserved. 5 © Arsene. Permission granted under the terms of the Creative Commons Attribution 2.0 Generic license 6 © J Bar. Permission granted under the terms of the GNU Free Documentation License. 7 © Ambanmba. Permission granted under the terms of the Creative Commons Attribution-Share Alike 3.0 Unported license.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




A service facility is a zonal area containing electrical substation and distribution, signalling and

control, communications, traffic control infrastructure, building services infrastructure, property

and signage within the corridor and interchange to support the operation of fleet services.

A maintenance and logistics facility is a zonal area containing plant and equipment, materials

(including quarries), spare parts, building services infrastructure, property and signage to

support the maintenance, cleaning and testing of network infrastructure and fleet assets.

An operations facility is a zonal area containing IT and monitoring equipment, building services

infrastructure, property, and signage to support the control and security of the network

infrastructure and fleet assets as well as drivers / guards facilities and educational training

facilities.

Refer to Figure 6 for images in relation to service facilities (electrical, signalling and

communications), maintenance facilities and operations facilities.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




9 8

10 10

10 8

8

Figure 6 – Examples of service, maintenance and operations facilities

Each facility shall include the following infrastructure assets where applicable:

• civil structures including bridges, tunnels, buildings, fencing and barriers, including:

o miscellaneous facility structures such as access ramps, stairs, concourses, platforms,

canopies, plinths, jetties, moorings, piers, pontoons, slipways, dry docks, inspection

pits and bike lockers

• electrical substation including traction, non traction substation and distribution equipment

and SCADA

8 © State of NSW through Transport for NSW. 9 © State of NSW through the Department (State Transit). 10 © State of NSW through Sydney Trains. All rights reserved.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• electrical cable feeders, aerial lines and pole equipment

• rail signalling and control equipment including automatic train protection (ATP),

interlockings, workstations, telemetry, power supply and cables

• control systems and technology systems

• telecommunications including customer information indicators and clocks, audio and public

address, security help points and CCTV, radio, network and transmission and terminal

equipment, licences, cables and condition monitoring equipment

• plant including fixed and mobile plant and equipment

• services including lifts, escalators, fire management, HVAC, low voltage electrical, lighting,

and hydraulic water / sewer / drainage system

• hardware, software and licences


• earthing


• ticketing

7.6.3. Fleet

Fleet assets shall include the passenger trains, light rail vehicles, ferries, buses, track machines

and mobile heavy plant, locomotives, wagons, recording vehicles, road vehicles and their

associated onboard fleet systems. Refer to Figure 7 for images of fleet types.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




11 12

13 14

13 12

15 15

15 15

Figure 7 – Examples of fleet

11 © Hpeterswald. Permission granted under the terms of the Creative Commons Attribution-Share Alike 3.0 Unported license. 12 © State of NSW through Transport for NSW 13 © Bidgee. Permission granted under the terms of the Creative Commons Attribution-Share Alike 3.0 Australia license. 14 State of NSW through the Department (State Transit). 15 © State of NSW through Sydney Trains. All rights reserved.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




7.6.4. Plant

Plant assets cover three broad groups.

Mobile heavy plant assets are covered under fleet in Section 7.6.3 of this document as these

assets are treated as road and/or rail vehicles.

Fixed plant assets are covered under facilities in Section 7.6.2 of this document as these assets

reside within a maintenance depot, workshop facility or logistics facility.

Minor plant and equipment assets shall include those items not classified under mobile heavy

plant or fixed plant.

7.7. Rotable assets and tracking

Assets or assemblies that are fitted or removed from other assets and managed through

tracking by a serial number such as rotables like train bogies, traction motors and high voltage

circuit breakers shall also be managed in the asset register.

Refer to Figure 8 for an example of a rotable asset and tracking.

Feed

er A

Feed

er B

Feed

er C

Feed

er D

Spare

The HV Circuit Breaker servicing Feeder B shall be rotated with the Spare for Maintenance, Failure Repair or Operational requirements.

HV Circuit Breakers have unique serial numbers and need to be tracked over their useful life.

The Bogie servicing Position 1 on RollingstockCar A shall be rotated with a Spare for Failure Repair or Refurbishment requirements.

Bogies have unique serial numbers and need to be tracked over their useful life.

Note: In this example the Bogie itself is an assembly comprised of Wheels, Axles and Traction Motors. These sub assemblies may also be fitted / removed separately to the Bogie itself and shall also be tracked.

Pantograph

Bogie 1 Bogie 2

Car A

Feed

er A

Feed

er B

Feed

er C

Feed

er D

Spare

The HV Circuit Breaker servicing Feeder B shall be rotated with the Spare for Maintenance, Failure Repair or Operational requirements.

HV Circuit Breakers have unique serial numbers and need to be tracked over their useful life.

The Bogie servicing Position 1 on RollingstockCar A shall be rotated with a Spare for Failure Repair or Refurbishment requirements.

Bogies have unique serial numbers and need to be tracked over their useful life.

Note: In this example the Bogie itself is an assembly comprised of Wheels, Axles and Traction Motors. These sub assemblies may also be fitted / removed separately to the Bogie itself and shall also be tracked.

Pantograph

Bogie 1 Bogie 2

Car A

Figure 8 – Example of rotable assets and tracking

Assets or assemblies may be moved throughout their useful life due to the following reasons:

• maintenance examination - rotate interchangeable asset or assembly with a spare for

temporary maintenance purposes and to keep system operational. Maintained asset or

assembly shall be moved back into operation while spare is placed back into the spares

location.

• failure repair - rotate interchangeable failed asset or assembly with a spare to replace the

failed item. Failed asset or assembly shall be sent for repairs if it is a repairable item or

disposed if not economically viable. Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• refurbishment - rotate interchangeable degraded asset or assembly (based on condition or

age) with a spare to replace the degraded item. Degraded item shall then be sent for

refurbishment if it has a remaining useful life or disposed if not economically viable.

• operational duty - rotate interchangeable asset or assembly with a spare to support

operational requirements and to ensure even usage distribution

The asset register shall reflect the current configuration and status of all fitted assets and

assemblies as well as the location and status of removed assets and assemblies.

7.8. Asset capitalisation and the fixed asset register

New South Wales Treasury requires TfNSW to value its assets at 'fair value'. In the context of

this document 'fair value' for new assets will be based on the cost of construction of the

completed asset, and will apply to any expense with a value greater than $5000 (excluding land

and network assets which have no capitalisation threshold), with an economic benefit exceeding

12 months, and is considered a fixed asset in accordance with accounting standards. These

assets shall be included in the fixed asset register. This requirement is to ensure that the asset

value is written off over its economic life.

Assets in the fixed asset register shall be aligned to the assets in the asset register for

maintainable assets in either a one to one relationship or by aggregating costs to a summary

parent asset level, for example electrical substations and signal locations.

7.9. Linear and discrete assets and attributes

Assets shall be identified as being linear or discrete.

A linear asset shall describe an asset with a defined start and end reference, for example

kilometerage. Linear assets include corridor, track, road pavement, tunnels, and overhead

wiring. Linear asset attributes, including physical and functional configuration characteristics and

maintenance information, shall also be defined with start and end references relative to the

linear asset.

A linear asset may also have discrete attributes or features and maintenance information along

its length defined by a point reference, for example kilometerage along the asset such as weld,

joint or sign. Figure 9 provides an example of the linear data attributes for track.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




Track – Linear Data Attributes – 0 to 3 Km Track – Linear Data Attributes – 0 to 3 Km

Figure 9 – Example of linear configuration data attributes for track

A discrete asset shall describe an individual point asset that can be uniquely identified at a

known location such as geographic information system (GIS) coordinate or kilometre point.

Discrete assets include turnouts, bridges, signals, trainstops, transformers, buildings and plant.

Discrete asset attributes, including physical and functional configuration characteristics, and

maintenance information shall also be defined relative to the discrete asset.

8. Asset classification structure framework

The asset classification structure establishes a consistent definition, structure and

categorisation of assets across to asset portfolio for the following purposes:

• ensuring common terminology of assets and asset structuring within the asset register

• supporting easy exchange of asset information including asset registers, asset attributes

and documentation

• enabling the level to which assets are capitalised and depreciated

• supporting collaboration and build up of required asset information for asset handover and

acceptance

• defining the level of asset information required to be captured and managed to support and

substantiate decisions made over the asset life cycle

• supporting the development of a functional architecture model

• ensuring management of configuration change and risk

• enabling standardised and consolidated reporting

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




8.1. Asset classification structure

Each asset shall be defined according to the asset classification structure.

The asset classification structure comprises six levels as per the list below:

• level 1 - asset system

• level 2 - asset class

• level 3 - asset function

• level 4 - asset type, defines the level at which differing types of equipment essentially

provide the same function

• level 5 – component, which is linked to the asset type

• level 6 - sub component, which is linked to the component for the asset type

A system represents a grouping of asset classes, for example structures.

The asset class shall be the primary grouping of similar assets within the system, for example

bridges.

An asset function shall be associated with an asset class, for example underbridges.

Asset types consist of groups of assets that have common characteristics which distinguish

those assets that perform the same asset function.

Component parts shall be related to the asset type, which defines the build of the asset.

Sub-component parts are related to the component. The sub-component may be used as a

positional reference for example left, right, top, middle, bottom, and no.1.

Components and sub components will vary across the different asset types, for example:

different signal asset types could have different component builds.

Figure 10 illustrates the asset classification structure levels.

Figure 10 – Asset classification structure L1 – L4

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




Figure 11 illustrates an example of an asset classification structure for a track asset:

Figure 11 – Example classification structure for a track asset

Figure 12 illustrates an example of an asset classification structure for a signal asset:

Figure 12 – Example classification structure for a signal asset

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




Figure 13 illustrates an example of an asset classification structure for an electric substation

asset:

Figure 13 – Example classification structure for an electric substation asset

8.2. Asset classifications and the information model

All assets shall be classified and contain a reference to a class, function and type.

An asset type shall only belong to one asset function and an asset function shall only belong to

one asset class.

The asset type shall be used to define the unique make or model of an asset that performs a

designated function. The asset type shall be a separate identifier in the asset register. These

assets have common characteristics which distinguish them separately and need to be

managed as a unique configuration item. An asset type shall be associated with one asset

function to allow for variations such as different manufacturers, different specifications and

different components.

Asset type shall define the following:

• maintenance strategy to be applied including the technical maintenance plan. Different

asset types within the same function may adopt the same technical maintenance plan

• component and sub-component parts required to support defect identification and

management. Component and sub-components are not directly associated to the each

asset but are linked via the asset type that defines a common parts list for all assets of that

type

• warranty to be applied

• materials list (inventory) required for servicing, maintenance and repairs

The asset function shall be used to group one or more asset types that perform the same

function. The asset function shall be a separate identifier in the asset register. An asset function

shall be associated with one asset class. Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




Asset function shall define the following:

• grouping of asset types

• non-graphical data attributes required to be captured and managed, including physical,

functional, condition, operational and organisational data

• standard for the associated data attributes, including name, type, format, unit of measure,

accuracy, and range –min/max

The asset class shall be used to group one or more asset functions into a logical group. The

asset class shall be a separate identifier in the asset register.

Asset class shall define the grouping of asset functions.

Each asset in the asset register shall have a class, function and type reference.

The asset shall inherit the properties listed above relevant to its type and function.

Documents and graphical data, including position and spatial data, shall be referenced directly

to the asset in the asset register.

Figure 14 illustrates the information associated with the asset in the asset register in relation to

its classification.

Figure 14 – Asset information model linked to the asset classification

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




9. Asset information requirements

Asset information shall be derived from all stages of the asset life cycle. Figure 15 illustrates the

asset life cycle stages.

Figure 15 – Asset Life cycle stages

A formal approach to the governance of the asset information shall be required to ensure the

information is current, accurate and complete to support and substantiate asset decisions to

meet TfNSW objectives.

9.1. Asset data

Asset data and attributes associated with assets contained in an asset register is categorised

into the following data groups:

• configuration – includes physical and functional data related to identifying and providing

static referencing of manufacturer details, asset construction, asset procurement, technical

characteristics and physical relationship with other assets

• location – includes data related to physical and geospatial attributes, for example

information on environmental and spatial relationship with other assets

• condition – includes data related to past and current condition such as information on

residual life

• operational – includes data related to usage, tonnage, restrictions and criticality

• maintenance – includes data related to the management and recording of maintenance

activities

• organisational – includes data related to responsibilities of the owner, operator and

maintainer

• financial – includes data related to costing from capital acquisition, operation, maintenance

to disposal

Asset data and attributes may be static or dynamic and be of a graphical or non-graphical

nature.

Asset data and attributes requirements shall support both linear and discrete assets. Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




9.2. Asset documents

Asset documents associated with assets contained in an asset register include manuals, plans,

photos, drawings, certificates, licences, and schematics.

9.3. Information quality

Asset information shall be assessed to ensure that the quality of information is maintained as

per the requirements defined in Section 12 of this document together with targeted surveillance

audits. The information quality is determined by the following categories:

• completeness – data is complete

• correctness – data is accurate and up to date

• consistency – data is defined including business rules and format

• clarity – data is clear and unambiguous

• integrity – data is structured and relationships are maintained with other data repositories

• uniqueness – no duplication of the data

9.4. Pre-commissioning asset information and handover

The asset information system shall include asset specific pre-commissioning information for all

assets.

As part of asset handover during the asset acceptance phase, the asset information

requirements detailed in this section shall be provided and updated within the asset information

system as part the existing staged commissioning and operational readiness gates.

This is required for both new assets (investment) and for the renewal or refurbishment

(sustainability) of existing assets as shown in Figure 16.

Figure 16 – Asset data built up across the life cycle including transition at handover Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




Plan:

• documents

o reports – requirements specification, feasibility, environmental, geotech, reliability /

availability / maintainability / safety (RAMS), system safety assurance plan and hazard

log

Acquire:

• configuration data

o asset register identifier (unique identification, serial number, label / description and

classifications – class / function / type)

o construction /build – manufacturer make and model – nameplate details including

configuration attributes both linear and discrete (applicable also for type approved

assets and assets under trial)

o age – date commissioned, design life

o design information – ratings, loadings, areas, lengths

o supplier/vendor information

o failure modes, effect and criticality (FMECA)

o test/commissioning results

o warranty information

o survey information

o heritage information

o spare parts inventory

• financial data

o capital acquisition cost – linked to financial fixed asset register for depreciation

purposes

o whole of life costs to operate and maintain

• location data

o asset location including physical geographic information and geospatial referencing

(for fixed infrastructure assets) or home depot location for mobile fleet and plant

assets

o environmental information

• organisational data Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




o asset ownership

o asset maintenance demarcation and interfaces

o third party agreements

o land ownership, deeds and agreements

• documents

o maintenance standards and TMPs (including maintenance service schedules)

o maintenance manuals

o operating manuals

o drawings – concept, approved for construction (AFC) and as-built drawings,

schematics, plans and cad files

o regulatory – licensing and special conditions

o certificates and compliance – Disability Discrimination Act 1992 (DDA), Building Code

of Australia (BCA), design certificates, construction and commissioning certificates

o reports – design assumptions and calculations, inspection and test and commissioning

reports, safety assurance report

o concessions provided to design and construction standards

• operational data

o operational settings – circuit breaker trip setting

o hazards – confined space, restrictions

o risk level

o energy usage

o special requirements to operate and maintain

Note: residual defects and risks remaining at handover shall be transferred to the

operator / maintainer and managed within the asset information system.

9.5. Exchange of asset information at handover

The exchange of validated and assured data and documents shall be electronic and

implemented through an agreed exchange process determined by TfNSW and managed

between the information provider or project deliverer and the organisation responsible for

maintaining the asset information on behalf of TfNSW.

The content of the information exchange shall be sufficient to meet the requirements of this

standard. Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




The frequency and scope of each information exchange shall be defined as part of the asset

handover requirements and staged to align with the requirements of the operator and

maintainer to meet operational readiness.

The format of data and documents shall support the requirements of the information system

repository that contains the asset information such as a database, a register or planroom.

9.6. Post-commissioning asset information

The asset information system shall include asset specific post-commissioning information for all

assets. The following requirements shall be provided for asset operations and maintenance:

Operate and maintain:

• condition data

o condition information

o condition models and assessment criteria

o remaining life

• operational data

o asset criticality and assessment criteria

o asset duty including performance requirements – tonnage or volume, time in service,

hours operated, number of operations.

• maintenance data

o maintenance activities - (preventive, corrective, breakdown, upgrade / refurbish,

renewal including supporting activities, operational – for example switching and

standby, and event triggered, for example heat patrol and feeder trip)

preventive service schedules including method of scheduling (time/frequency, usage

or condition), criticality and latitude defined as part of the technical maintenance

plan

work orders for every maintenance activity

defects for every conditional and functional failure

work breakdown structures

unit rate estimates per activity

duration per activity

measurements, adjustments, calibration

materials Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




o failure information (to support MTBF and MTTR)

time failed, time attended, time rectified, time in service

failure mode, operational consequence (including service delays), failure type both

conditional and functional

root cause

o materials

spares including type, location, interchangeability, and minimum stock levels

• financial data

o maintenance costs – labour, material, plants/equipment, contract (by activity per asset

captured on the work order)

o capital value – (changes to financial fixed asset register in relation to depreciation

method, depreciation and revaluation)

• documents

o photos (asset configuration, condition)

o reports – investigation (failure / incident, reliability, condition)

o concessions provided to maintenance standards

9.7. Disposal asset information

The asset information system shall include the following asset specific decommissioning

information for all assets:

Disposal:

• maintenance data

o maintenance disposal activities

• work orders for every maintenance activity

• financial data

o disposal costs - including costs for labour, material, plants and equipment, and

contract by activity per asset captured on the work order

o residual capital value of the asset to be written off

The remaining capital cost shall be written off in the financial fixed asset register.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




9.8. Supporting asset information

The asset information system shall contain the following information to support the asset over

the life cycle:

• training materials

• competency and certification of staff

• tools and equipment

• asset maintenance plans, replacement / refurbishment plans

10. Events triggering changes to asset information

Across the asset life cycle various events will occur that shall trigger the requirement to update

the relevant asset information. These events will result from changes in asset strategy, service

strategy, new asset type, maintenance strategy including maintenance requirements, and asset

configuration. Refer to Figure 17.

Figure 17 – Events that trigger updates to the asset information across the life cycle

The following list provides examples of events which occur over the life cycle that shall trigger

the need for the asset information to be updated:

• introduction of new assets, whether it is an existing asset type or new asset type, including

asset trials

• asset relocation including rotable movement

• asset decommissioning and disposal

• minor maintenance – preventive, corrective, breakdown including inspection, testing and

calibration including component change

• major maintenance – refurbishment (component change out) / upgrade, modification and

renewal (existing like for like asset type or new asset type)

• asset revaluation

• change in assessed risk level Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• change in asset ownership, asset operator or asset maintainer (demarcation of

responsibility)

• concession to a standard

• change in operation (timetable, usage) and asset criticality

• change in regulations and standards

The financial fixed asset register may need to be updated to reflect the change in asset value.

11. Asset information system requirements

The requirements of the asset information system are as follows. The system shall:

• contain all the assets maintained by the operator and maintainer on behalf of the asset

owner in an asset register aligned with the asset classification structure and associated

asset master and reference data

• contain all the asset information on behalf of the asset owner as specified in this standard

• be capable of managing an asset register and all associated asset information, plans,

manuals and activities into a consolidated system comprising one or more integrated

repositories

• be capable of exporting data in commonly used industry standard formats

• be capable of providing integrated asset information within a reporting dashboard format to

TfNSW and approved stakeholders

• be capable of planning, scheduling, prioritising and completing asset management

activities

• be capable of storing the current and complete historical record of all asset information in a

secured, controlled environment

• be capable of providing records in relation to inventory management, work order

management , tracking of costs and asset warranty

• be sustainable, maintained fit for purpose and scalable

• be capable of enabling the delivery of the following asset management functions:

o plan and document management

o work management, including capital work, recurrent maintenance work and costing

o failure and defect management

o asset condition management

o configuration management Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




o program and project management, including estimating

o materials management

o reporting

• be capable of integrating information with the following asset management related

systems:

o incident systems

o financial systems

o procurement systems

o human resource and rostering systems

o condition monitoring and SCADA systems

o operational systems, including control and timetables

o business intelligence reporting and analysis

o maintenance requirements analysis systems

o engineering design systems

o information modelling systems

o mobile technology systems and devices, including supporting remote information

access, review, capture and update

• be capable of producing reports on the configuration, condition, planned work, work history

and performance of all assets including defect and failure and incident analysis

• be capable of integrating data

12. Operator and maintainer requirements

The requirements of the operator and maintainer are as follows. The operator and maintainer

shall:

• maintain and update the asset register and associated asset information on behalf of the

asset owner (TfNSW)

• be responsible for ensuring the quality of the asset register and associated asset

information is at the highest standards at all times

• be responsible for ensuring the asset register and associated asset information is a true

and accurate representation of the asset condition and status of all assets including assets

handed over as part of project commissioning (for both internal and external delivered

projects) Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• be responsible for ensuring all approved current TMPs and related service schedules are

fully implemented relative to each asset within the asset register

• be responsible for ensuring all approved pending new or amended TMPs are fully

implemented relative to each affected asset within the asset register within three months of

being approved

• make available to the asset owner (TfNSW) the asset register, associated asset

information and reports held in the asset information system in an agreed format

• handover the asset register, associated asset information and reports to TfNSW at the end

of contract in an agreed format

• accept new assets and update the asset register and associated asset information prior to

operational readiness, including asset modifications and disposals

• provide direct access and training in the use of the asset information system to TfNSW

nominated staff where required, including user and training materials

• provide direct access and training in the use of the asset information system to third party

maintainers where required

• be responsible for ensuring that all asset management activities are planned, scheduled,

prioritised, controlled, recorded and monitored in the asset information system over the full

life cycle of the asset, together with the planning and coordination of possessions and

access to the asset

• be responsible for ensuring that all asset management activities are recorded in the asset

information system within three business days of the activity taking place covering but not

limited to:

o material management for spares and consumables

o work order management and cost allocation for scheduled and unscheduled work,

including work arising

o servicing records for measurements, condition assessment, photos, operating

statistics, settings and adjustments to ensure asset remains within operating

threshold/tolerance

o defects / fault management for assets – part causing failure, size, criticality, status,

corrective actions, and root cause for both functional and conditional failures (for both

temporary and permanent repairs) including reference to the incident or event where

applicable

o incident management, capturing consequences such as impact on operations and

delays Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




• record all asset information in the asset information system as a result of configuration

change, including:

o asset configuration changes or modifications including modifications to individual

discrete asset and linear asset configuration changes over the length of the linear

asset

o installation and exchange of components including type approved products and

products under trial

o fitment and removal of rotable serialised assets including the location and status of the

removed assets

o changes to the TMP, including service schedules, frequency, tasks, latitude and

criticality

o changes as a result of failure and corrective action

o changes as a result of a concession to a standard. The concession document shall

also be linked to the asset in the document management system.

• generate reports to TfNSW as required from the asset information system on the following:

o current performance of the asset

o current condition of the asset

o current asset duty and utilisation of the asset

o annual works planning, delivery, production and backlog

o maintenance compliance

o asset register configuration and history

• conduct validation checks at intervals of at least six months to establish the accuracy,

validity and currency of the asset register and associated asset information

• allow TfNSW to audit the accuracy, validity and currency of the asset register and

associated asset information as requested by ASA

• monitor and analyse the asset information to detect the need for maintenance, indicated by

the following:

o a fault or defect requiring immediate attention

o a series of faults or defects comprising separate events that individually do not require

action but which collectively have passed a specified threshold of acceptability

o usage that indicates the need for preventative maintenance

o condition, where a physical property of an asset has fallen outside of acceptable limits Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0




o performance, where a measured factor has fallen below a specified level or outside of

an acceptable range

o predicted failure or the predicted and unacceptable decline of an asset

• be responsible for ensuring that the asset information is managed and secure by the:

o provision of disaster recovery and suitable storage

o allocation of roles and responsibilities for the creation, maintenance, access to and

assurance of the data

13. Asset information system ownership and custodianship of the information repositories

The ASA is the delegated owner of the asset information system and repositories which are

significant to TfNSW.

Asset information repository custodian services will be provided to the ASA by nominated

AEOs. Such services include providing appropriate repositories to hold and manage ASA

owned asset information.

The ASA will maintain a register of the information repositories that hold asset information and

the system custodians that manage that information. The custodian of an asset information

system is the party responsible for managing an asset information repository regardless of

ownership. Asset information system custodians shall meet the requirements of this and any

other relevant TfNSW document, including any agreed performance requirements.

Requirements for the provision and management of ASA owned asset information shall be

owned by the ASA but may be delegated and managed by the asset information custodian as

appropriate.

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0



Appendix A – Asset classification structure framework

Figure 18 shows the TfNSW grouping of asset classes and related asset functions by engineering discipline. Further details on asset classifications in relation to

asset classes, functions and types can be found on the ASA website (document T MU AM 02002 TI Asset Classification Structure).

Figure 18 – Asset classification structure for TfNSW


Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0



Page 42 of 42

Appendix B – Suggested reading

The following documents have not been directly referred to in this standard. However, these

documents may assist with providing some contextual information on asset information

management.

ISO55001 (2014) - Asset Management – Management Systems – Requirements

ISO55002 (2014) - Asset Management – Management Systems – Guidelines for the application

of ISO 55001

BS1192-2:2013 – Specification for the Information management for the capital / delivery phase

of construction projects using building information modelling

BS1192-3:2014 – Specification for the Information management for the operational phase of

assets using building information modelling

© State of NSW through Transport for NSW

Sup

erse

ded

by T

MU

AM

020

01 S

T v2

.0