Free asset hierarchy template

• The MapTrack asset hierarchy template has 7 columns and room for 28 entries. Columns: Level, Functional location code, Parent code, Description, Asset type, Criticality, Maintainable.
• An asset hierarchy organises equipment into parent-child levels, typically Site, System, Asset and Component, so work and cost roll up the tree.
• A functional location code gives each node a stable address that stays the same even when the physical equipment in it is swapped out.
• Getting the hierarchy right before loading a CMMS is what makes work orders, history and cost reporting meaningful later.
• Three to five levels suits most sites; too many levels slow data entry, too few hide where failures and costs occur.

Learn more about asset tracking in MapTrack.

• Meaningful roll-ups: a clean hierarchy lets work, downtime and cost aggregate from a component up to its asset, system and site.
• Stable history: a functional location code keeps failure and cost history attached to the position even when the asset in it is replaced.
• Right-level work orders: a defined structure means jobs are raised against the correct asset or component rather than a vague area.
• Faster CMMS setup: a hierarchy agreed on paper first turns a system load from guesswork into a structured import.
• Clear criticality: tagging criticality against each node shows where to focus preventive maintenance and spares holdings.
• Easier reporting: consistent levels and codes make cost-per-asset and reliability reporting comparable across sites.
• Onboarding clarity: new planners and technicians can see how the plant is structured and where each item of equipment sits.

• Hierarchy details: organisation, site, prepared by and the date the structure was defined.
• Level: which tier the node sits at, such as Site, System, Asset or Component.
• Functional location code: the stable code or tag that addresses this node in the hierarchy.
• Parent code: the functional location of the node directly above, which sets the parent-child link.
• Description: a clear name for the site, system, asset or component.
• Asset type or class: the equipment category used for grouping and reporting.
• Manufacturer and model: useful at the asset and component levels for spares and history.
• Criticality: a rating such as high, medium or low to guide maintenance priority.
• Maintainable: whether the node is a maintainable item that work orders attach to.
• Notes: parent system, redundancy, location detail or any setup note for the CMMS load.

1. Agree the number of levels and the coding scheme before you start.

   Decide how many tiers the hierarchy will use, commonly Site, System, Asset and Component, and define the functional location coding scheme. Settling this first keeps the structure consistent across sites and prevents a costly re-code once data is loaded.

2. Map the top levels: sites and systems or functional areas.

   Start at the top and list each site, then break each site into its systems or functional areas such as a process line, a building service or a fleet group. These upper levels are where cost and reliability reporting will aggregate, so name them clearly.

3. List the assets within each system and give them codes.

   Under each system, record the maintainable assets such as a pump, conveyor or generator, and assign each a functional location code that sits under its parent. The asset level is usually where most work orders are raised, so be thorough and consistent.

4. Break critical assets down into components.

   For assets where component-level history matters, add a component tier such as a motor, gearbox or bearing assembly. Only go this deep where the detail will be used, because every extra level adds data entry effort that has to be justified by the insight it gives.

5. Assign criticality and confirm the parent-child links.

   Rate the criticality of each node and check that every code points to a valid parent, so the tree is unbroken from component up to site. A node with no parent or a wrong parent will break the roll-up of work, downtime and cost later.

6. Validate the hierarchy and load it into the CMMS.

   Review the structure with the people who maintain the plant, confirm the codes are unique and the levels are consistent, then use the agreed hierarchy as the import structure for the asset management system. Keep it under change control so additions stay disciplined.

Practical answers about the form, record keeping and using MapTrack.

This form is a starting point. Check the current requirements that apply to your equipment, work and location. The form alone does not establish compliance.

• ISO 14224 - Petroleum, petrochemical and natural gas industries: collection and exchange of reliability and maintenance data for equipment (equipment hierarchy and taxonomy)
• ISO 55001 - Asset Management Systems (systematic management of the asset base)
• ISO 55000 - Asset Management (overview, principles and terminology)

• ISO 55001:2024, Asset management system requirements (ISO catalogue)

MapTrack publishes this template. The linked authorities publish their own guidance; they haven't endorsed this form.

• Asset register template
• Asset criticality matrix
• Maintenance strategy planning template
• Equipment inventory template
• Equipment management (MapTrack)
• Maintenance
• Manufacturing