1 Asset Hierarchy PDF

Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

COMPREHENSIVE ASSET MANAGEMENT PLAN TASK SHEET ASSET HIERARCHY

APPLICATION AND PURPOSE


Reference

Asset hierarchy management allows the tracking of all assets and their associated locations using a family tree that forms relationships between physical locations, plant, processes within plant and assets constitutes within it. These relationships facilitate data collection and analysis for assets movement, maintenance and costs for individual assets, a grouping of assets or a plant level. For IWK, developing a sound asset hierarchy provides a logical record of all Asset Maintenance Significant Equipment and a unique identifier for Operation and Maintenance of that equipment. It also allows for the development and recording of equipment maintenance / inspection history against a unique ID. IWK CURRENT PRACTICE

3.3.5 to 3.3.7

Reference

IWK's current Asset Hierarchy has an asset tagging and hierarchy in place which is not formally documented. However, the tagging system and the hierarchy are generally considered adequate for the purpose of the CAMP. IWK are assigning tags and include them in the hierarchy for equipment which is nonmaintainable. This is unnecessary causing cluttering of the IFS database resulting in degraded system performance. IWK RECOMMENDED PRACTICE

4.1

Reference

IWK to formally document their Asset Hierarchy, such as tagging procedure, codes utilised in AIMS/IFS etc. Following, IWK should remove unnecessary tags from the IFS database to allow for better system performance in line with the recommended hierarchy. DATA REQUIREMENTS
Item Description Required Quality Level

3.3.3 4.1

Currently Recorded by IWK? Y/N Quality

Location Identifier Function Identifier Unique ID association

Site / Asset Equipment Type Functional Location

Unique to one location Unique to one type Functional Location

Y Y Y

OK OK OK

RELATED SECTIONS IN CAMP


Reference

Data Needs.

3.14

Revision G

Page 1 of 2

28/06/2011

ITC REQUIREMENTS Logical hierarchy in IFS. Ability to search for equipment unique identifiers. Ability to identify all equipment of a particular type at one or more locations. CURRENT ITC CAPABILITIES Logical hierarchy exists in IFS. Search capability exists but is often slow. Currently limited to searches in one location/asset only (TBC). IWK ACTION PLAN
Timeframe Reference

Formally document IWK Asset Hierarchy development including standard codes for IFS. Carry out an across-asset review once formal IWK Asset Hierarchy document is developed, reviewed and approved. Ensure all locations are adhering to formal guidelines and implement any changes as necessary. As part of review above, remove or reclassify unnecessary items (see below additional notes) that have been tagged to reduce IFS workload. IWK TRAINING REQUIREMENTS IWK CAMP Manual Overview Training. INITIAL CHAMPION ACTIVITIES

Short-term

5.1

Short-term

5.1

Short-term

5.1 3.3.3

Reference

Develop IWK Asset Hierarchy Document. WorleyParsons suggests that IWK utilise the attached high-level "Process Coordination Map" (PCM) as a starting point for their ownership of Asset Hierarchy and develop their process and procedures. ADDITIONAL/SUPPORT NOTES A recommended list of unnecessary items currently contained in IFS would include:

5.1

- man hole covers (approximately 7,000 records in IFS with no maintenance actions; should be attached to respective sewer line and not be recorded individually) - manually operated valves (generally not maintained, replacement on failure) - process flow lines (currently not recorded and not required to do so) - subcomponents of control panels (currently not recorded and not required to do so) - small electrical equipment (such as light fittings, power sockets, fuse boards, etc; currently not recorded and not required to do so) These should be in line with the hierarchy recommendations outlines in Sections 3.3.1 and 3.3.3 for guidance, and based on table 3-1.

Revision G

Page 2 of 2

28/06/2011

You might also like