Asset Hierarchy Services

Your Plant's Reliability Program Is Only as Strong as Your Asset Hierarchy

Redlist builds your asset hierarchy for you, down to the equipment, components, bills of materials, and lube points, structured to ISO 14224 and delivered inside Redlist or synced to the ERP and CMMS you already own.

5 levels
Functional hierarchy modeled on ISO 14224
~10,000 records
To reach component level at a typical mill
1 pilot line
Measured baseline before you scale
Redlist or ERP
Delivered where your team works
Foundations

What Are Redlist Asset Hierarchy Services?

Most plants run a maintenance system that stops three levels short. The hierarchy goes Site to Area to Line, and ends. Every part, every work order, every dollar gets charged to "the line," and the detail planners, technicians, and accountants actually need lives in one veteran’s head. Without structure down to the component level, work orders have nothing specific to attach to, costs cannot be traced, failure patterns never surface, and tribal knowledge walks out the door at retirement.

DEFINITION

Redlist Asset Hierarchy Services build the missing layers of your maintenance data foundation for you: every area, system, and piece of equipment broken down to the maintainable component, structured to ISO 14224, with bills of materials, lube points, service tasks, and criticality rankings attached to the right assets. Whether you run everything in Redlist or keep Maximo, SAP, or JD Edwards as the system of record, the hierarchy we build lands in the platform your team already uses.

RELIABILITY MATURITY JOURNEY
01

Reactive

Fix-on-fail. No structured program.

02

Controlled

PMs exist. Execution is inconsistent.

03

Standardized

Programs scale across sites. Data captured.

04

Predictive

Condition data drives maintenance decisions.

05

Scaled Reliability

Reliability culture across the enterprise.

What a Redlist Asset Hierarchy Engagement Delivers

A plant data foundation that makes work orders, PM plans, failure data, and cost reporting actually work, for the entire facility.

Component-Level Hierarchy

Every area, system, and piece of equipment broken down to the maintainable component: bearings, sprockets, chains, gearboxes, hoses, valves, and instrumentation. Equipment boundaries structured to ISO 14224, so a drive motor is a linked asset record rather than buried inside the machine it drives.

Bills of Materials

For each asset we capture the bill of materials: part numbers, vendors, and descriptions tied to the exact equipment they belong to. Data drawn from field walkdowns, nameplates, manuals, and purchasing history, so parts are findable when a planner needs them, not scattered across records and tribal memory.

Lubrication and Maintenance Points

Every lube point, inspection point, and service task, clean, inspect, replace, lubricate, attached to the right component with the right specification: product, frequency, volume, and method captured at the point level. The foundation for a full lubrication management program that eliminates missed intervals and specification errors.

Criticality and Physical ID

Criticality rankings assigned to drive maintenance strategy, plus physical identification (QR-coded and NFC tags) applied to equipment in the field. Technicians scan and land on the exact asset record from the shop floor, no searching, no ambiguity, no wrong-equipment work orders.

3D Facility Scans

As a standard part of the engagement, we scan your facility. The scans do double duty: they let us scope the build accurately before we quote it, and they become a living spatial reference so technicians navigate the plant visually and find every asset on a map, not just in a list.

Delivered Where You Work

The hierarchy we build is not locked in our platform. Run everything in Redlist, keep Maximo, SAP, or JD Edwards as the system of record, or both. We build the structure once and deliver it wherever your workflow needs it, with bidirectional sync keeping records aligned.

Know Exactly What Your Hierarchy Is Missing

A specific, sequenced view of what your hierarchy is missing and what it will take to build it out.

Diagnostic

The Redlist Hierarchy Diagnostic

Redlist evaluates your current hierarchy across five structural dimensions, aligned to ISO 14224 and SMRP best practices: Hierarchy Depth and Structure (does it reach the equipment and component levels), Bills of Materials and Part Traceability (are part numbers attached to specific records), Lubrication and Maintenance Point Capture (is every lube and service point tagged with its specification), Criticality and Physical Identification (is criticality assessed and are assets QR/NFC tagged), and ERP and CMMS Data Governance (is the structure portable, benchmarkable, and governed). Every diagnostic delivers two documents: a scoped estimate for one pilot area, so you know what a single line costs to build out, and a full-site projection extrapolated from measured reality, not a guess.

Book a Scoping Call
Redlist maturity assessment spider chart scoring asset hierarchy structural dimensions
Reliability Foundation

Structured for Every Downstream Initiative

An asset hierarchy is not the end goal. It is the prerequisite for everything reliability-centered maintenance promises. Criticality analysis needs a defined asset base to rank. FMEA and failure-data collection need components to attach failure modes to. Condition-based maintenance needs a place to pin oil analysis, vibration, and inspection results, down to the specific bearing, not "the line." This is why reliability standards bodies treat taxonomy as step one: SMRP identifies a defined asset taxonomy as the prerequisite for reliable failure data and maintenance strategy. A hierarchy built to ISO 14224 conventions is portable, benchmarkable, and ready for whatever system, dashboard, or AI initiative comes next.

Maintenance technicians verifying asset records on a tablet in the field
How It Works

From Diagnostic to Fully Populated Data Foundation

Start small, prove the value, then expand with confidence. We build the hierarchy the way plants actually adopt it, incrementally, with your people involved at every step.

STEP 1
SCOPE

Scope

Together we pick a single line or area, ideally one that already has attention on it, so the new data pays off immediately. Using facility scans and your existing CMMS records, we estimate the effort before any work begins. You get a real number, not a guess.

STEP 2
ASSESS

Assess

Our engineers walk the pilot area, review nameplate data, evaluate the current structure, and identify the specific gaps between what exists and what a component-level structure requires. Equipment boundary issues, missing BOMs, and naming inconsistencies get flagged before build work starts.

STEP 3
BUILD

Build

Field walkdowns, data capture, and record building. Hierarchy, components, bills of materials, lube points, and maintenance points, structured to ISO 14224 and built alongside your maintenance team so the data reflects how your plant actually runs.

STEP 4
TAG & VERIFY

Tag and Verify

Physical identification applied to equipment (QR and NFC tags), GPS coordinates captured during tagging, and every record verified in the field. Technicians scan into the platform and confirm the data matches what they see on the machine.

STEP 5
DEPLOY

Deploy and Report

The pilot area goes live in your platform of choice, Redlist, your ERP, or synced across both. You receive a report showing exactly what changed: what the line looked like before, what it looks like now, and what the effort actually was.

STEP 6
EXTRAPOLATE

Extrapolate

From the pilot’s measured baseline, we build a grounded plan for the rest of the site. Scope, sequence, and timeline based on real hours per line, not an estimate. You expand at the pace that fits your budget and team, with usable data delivered at every phase.

Common Questions About Asset Hierarchy Services

How long does it take to build an asset hierarchy?

It depends entirely on scope, which is why we start with a pilot area. The pilot gives you a measured baseline, actual hours per line, that we use to build an accurate plan for the full site. A typical mill needs roughly 1,000 records to close the gap from line-level to equipment-level, and 10,000 records to reach the component level with lube points, hoses, and full maintenance tasks attached. The pilot tells us exactly how long that work takes at your facility.

Do we have to replace our CMMS?

No. We build the hierarchy to serve your workflow, inside Redlist, inside your existing ERP or CMMS (Maximo, SAP, JD Edwards), or synced across both with bidirectional data flow. Redlist is designed to integrate with existing systems through an open API, so many customers run Redlist for execution and lubrication management while keeping their existing CMMS as the system of record for work orders.

What if we already have a partial hierarchy?

That is the most common starting point. We work from what you have, most plants have solid structure down to the line or system level, and extend it to the equipment and component levels, correcting boundary and structure issues along the way. Naming inconsistencies and misclassified equipment, such as a drive motor buried inside a parent machine, get corrected as part of the build.

What is included in the bill of materials?

Part numbers, vendors, and descriptions for the components on each asset, captured from field walkdowns, nameplates, manuals, and your purchasing history, then attached to the correct equipment record so they are findable when a planner needs them. BOMs are structured so that consolidating spares and identifying obsolete parts becomes possible, not just theoretical.

How detailed should an asset hierarchy actually be?

Deep enough that work orders, parts, and costs land on a specific asset. For most plants that means five levels, down to major components and lube points. Standards like ISO 14224 define up to nine levels, but in practice the deepest levels are reserved for critical equipment where component-level reliability tracking pays for itself. Redlist engineers recommend the right depth per area, not a one-size-fits-all rule.

Who does the work, our team or yours?

Ours, with yours involved. Redlist handles the walkdowns, data capture, and record building. Your maintenance team stays in the loop on structure and naming decisions, because their adoption is the whole point. When your people have fingerprints on the data, they trust it, and they use it.

See What Your Hierarchy Is Missing

Book a scoping call and start with one line. Get a measured baseline, a real number, and a component-level data foundation your whole reliability program can build on.