The Hong Kong Polytechnic University · FACULTY OF ELECTRICAL ENGINEERING

EE535 Chap.7 Asset Registers, Hierarchies and Chainage

- one subject, every graph, every model, every mark
7 Chapters3-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 7 of 10 · EE535

Asset Registers, Hierarchies and Chainage

The register answers what exists

An asset register is the controlled list of assets and the attributes required to manage them. Useful fields can include stable identifier, description, type, status, parent, location, manufacturer or model, installation information and criticality. The field set should follow decisions and obligations.

A register that attempts to hold every fact becomes difficult to maintain, while a thin list cannot support work, planning or reporting.

A hierarchy provides operational context

The hierarchy relates network, service, system, location, equipment and maintainable unit. It allows a technician to identify the item worked on and a manager to understand the service context of that work.

The correct depth is a design choice. Too broad a node hides component patterns, while unnecessary decomposition scatters history across objects that nobody plans, inspects or replaces independently.

Location and asset identity are not the same

A location can remain while equipment installed there changes. An asset can move while retaining its equipment identity, depending on governance.

Separating functional location from equipment identity preserves both the history of the place and the history of the item. The organisation needs explicit rules for installation, removal, replacement, refurbishment and retirement so records do not follow the wrong object.

Chainage controls position on linear infrastructure

Railway assets can require a position along a line as well as a named station or system.

Chainage provides that reference. It should use a controlled datum, direction and format, and it needs validation when infrastructure or reference systems change. A position that looks precise but uses an ambiguous datum can send work to the wrong place and distort spatial analysis.

Pair linear position with route and asset identity.

History depends on classification discipline

Classification allows comparable assets and work to be grouped, while hierarchy provides parent-child context. Both need standards and ownership.

A fault recorded at the station when the failed object is a lift door cannot support component analysis; a door event recorded at a disposable screw level may fragment the same history. Design the structure by asking which object receives condition, work, cost, failure and renewal decisions.

In this chapter

What this chapter covers

  • 01

    Asset register purpose and controlled attributes

  • 02

    Hierarchy levels from service to maintainable unit

  • 03

    Functional location and equipment identity

  • 04

    Installation, replacement and retirement rules

  • 05

    Chainage and linear position references

  • 06

    Classification for comparable analysis

  • 07

    Work-history attachment and hierarchy depth

Worked example · free

Place a station lift in a usable hierarchy

Q [10 marks]. Not a University marking scheme: AskSia assigns these study marks. AskSia-authored practice. Build a minimal hierarchy for a station lift with repeated door faults and explain where the work order and service effect should be recorded.
The hierarchy supports work downward and decisions upward.The hierarchy supports work downward and decisions upward. Tasks attach to components, while faults, cost and condition roll through subsystem and car to the train-level view.TrainCar ACar BDoor subsystemBogieHVACWheelAxlecost and faults roll upward
The hierarchy supports work downward and decisions upward. Tasks attach to components, while faults, cost and condition roll through subsystem and car to the train-level view.
  • 3Build the location and system path.
  • 3Decompose to the maintainable unit.
  • 4Attach work and service evidence correctly.
Use a path such as network, line, station, concourse, lift system and lift, then decompose the lift into maintainable units including the door subsystem. Attach the fault and repair to the door subsystem so repeat causes are visible, while preserving the parent lift and station service relationship for availability and accessibility impact. Use stable identifiers and separate the functional location from replaceable equipment where needed.
Sia tip — Stop decomposing when the lower object no longer receives a distinct work, condition, cost or replacement decision.
Glossary

Key terms

Asset Register
The controlled record of assets and the attributes needed to manage them.
Asset Hierarchy
A parent-child structure linking service, system, location, equipment and maintainable units.
Functional Location
The place or role at which equipment performs a function, capable of retaining its own history.
Equipment Identity
The stable identity of a physical item across its controlled lifecycle and movement.
Chainage
A linear position reference measured along a defined infrastructure route and datum.
Classification
A controlled grouping of assets by common characteristics for work, analysis and reporting.
FAQ

Asset Registers, Hierarchies and Chainage FAQ

How deep should an asset hierarchy go?

Go to the lowest level that receives a meaningful maintenance, condition, failure, cost or replacement decision. Stop before creating objects that technicians cannot identify consistently or that never receive distinct control. Test the hierarchy against real work orders and reports before broad deployment.

Why separate location from equipment?

A location can keep its service role after equipment is replaced, while a physical item may move or be refurbished. Separating them preserves location performance and equipment history without merging two different stories. Clear installation and removal transactions maintain the relationship between them.

What controls make chainage reliable?

Define the route, datum, direction, unit and format; validate data at entry; manage reference changes; and pair chainage with asset identity and descriptive location. A number alone can be ambiguous, especially where lines branch, datums differ or infrastructure is reconfigured.

Study strategy

Exam move

Choose a linear-infrastructure asset and draw a hierarchy from network or service down to the maintainable unit. Mark which nodes receive work, condition, failure, cost and renewal decisions. Create separate columns for functional location and physical equipment, then simulate a replacement and show which history stays with each. Add a chainage value with route, direction and datum.

Finally test three reports: repeat component faults, station service availability and work by route position. Revise the structure wherever a report would count the wrong object.

Working through Asset Registers, Hierarchies and Chainage in EE535? Sia is AskSia’s AI Electrical Engineering tutor — ask any EE535 Asset Registers, Hierarchies and Chainage question and get a clear, step-by-step explanation grounded in how EE535 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 24 of your subjects at The Hong Kong Polytechnic University, plus 1,000+ more Bibles across the AskSia library.
Sia - your EE535 tutor, unlimited, worked the way the exam marks it
The full 3-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works