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 industry standards and delivered inside Redlist or synced to the ERP and CMMS you already own.
Your CMMS Can Only Answer Questions Your Asset Hierarchy Can Ask
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 that 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 back to the equipment eating the budget. Failure patterns never surface. Tribal knowledge walks out the door when the technician who knew every bearing on that line retires.
Redlist builds the missing layers for you. Every area, system, and piece of equipment broken down to the maintainable component, structured to ISO 14224 conventions, 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.
The result: a plant data foundation that makes work orders, PM plans, failure data, and cost reporting actually work, not for one line, but for the entire facility.
Know Exactly What Your Hierarchy Is Missing
Most facilities know their maintenance system has data gaps. The challenge is knowing which gaps matter most and what it will actually take to close them. A missing part number that stalls a work order may trace back to a hierarchy that stops at the line. A downtime pattern nobody can explain may be sitting in failure records that were never attached to a specific asset.
Redlist evaluates your current hierarchy across five structural dimensions, aligned to ISO 14224 and SMRP best practices. The output is a specific, sequenced view of what your hierarchy is missing and what it will take to build it out.
Hierarchy Depth and Structure
Every plant has some structure at the top: site, area, line. The question is how far down it goes. This dimension evaluates whether your hierarchy reaches the equipment level (individual assets like conveyor drives and transformers) and the component level (bearings, sprockets, hoses, lube points). We assess whether the five-level functional hierarchy modeled on ISO 14224 is in place, whether equipment boundaries are drawn correctly (a drive motor as a linked asset record, not buried inside the machine it drives), and whether the deepest levels are reserved for critical equipment where component tracking pays for itself.
Bills of Materials and Part Traceability
Ask a planner to pull up the spare parts list for a specific saw. If the answer involves searching purchasing records or asking the technician who has been there 15 years, the BOM data does not exist in a usable form. This dimension evaluates whether part numbers, vendors, and descriptions are attached to specific equipment records, whether BOMs reflect current spares actually held in inventory, and whether the data captured during field walkdowns, nameplate inspections, and manual reviews has been consolidated into a single source of truth.
Lubrication and Maintenance Point Capture
This dimension evaluates whether every lube point, inspection point, and service task is identified, tagged, and attached to the correct component. We assess whether lubrication points carry the required specification (product, frequency, volume, method), whether clean-inspect-replace-lubricate tasks are captured at the right level of the hierarchy, and whether the data supports proactive rather than reactive maintenance workflows. Gaps here cascade directly into missed lubrication intervals, incorrect grease selection, and bearing failures that show up as unexplained downtime.
Criticality and Physical Identification
Criticality rankings are the mechanism that tells the maintenance team where to invest first. This dimension evaluates whether criticality has been assessed at the equipment level using a defined methodology, whether the criticality data actually drives PM strategy and inspection frequency, and whether every asset carries physical identification (QR-coded or NFC tags) that lets a technician scan into the exact record in the field. Without physical ID, even a well-structured hierarchy is invisible to the person standing in front of the machine.
ERP and CMMS Data Governance
This dimension evaluates whether your hierarchy is portable, benchmarkable, and governed. We assess whether the structure conforms to ISO 14224 conventions (so it works with any downstream analytics or AI initiative), whether naming standards are documented and enforced, whether a defined process exists for adding and retiring equipment, and whether the data lives in a single system of record or is duplicated across Maximo, SAP, JD Edwards, or spreadsheets. Bidirectional sync between Redlist and your existing ERP is designed to keep records aligned without creating a second source of truth.
Every diagnostic delivers two documents: a scoped estimate for one pilot area (so you know exactly what a single line will cost to build out) and a full-site projection extrapolated from measured reality, not a guess. The engagement expands at the pace your budget and team can absorb, with usable data delivered at every phase.
What a Redlist Asset Hierarchy Engagement Delivers
Component-Level Hierarchy
Every area, system, and piece of equipment broken down to the maintainable component. Bearings, sprockets, chains, gearboxes, hoses, valves, and instrumentation captured and linked correctly. Equipment boundaries structured to ISO 14224, so a drive motor is a linked asset record rather than buried inside the machine it drives. This is the detail that makes or breaks your MTBF and cost data later.
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 is drawn from field walkdowns, nameplates, manuals, and your purchasing history, then attached to the correct equipment record so parts are findable when a planner needs them, not scattered across purchasing 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. 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. Some teams run everything in Redlist. Others keep Maximo, SAP, or JD Edwards as the system of record and use Redlist for execution in the field. We build the structure once and deliver it wherever your workflow needs it, Redlist-native, pushed to your ERP, or both, with bidirectional sync keeping records aligned.
From Diagnostic to Fully Populated Data Foundation
Every Redlist asset hierarchy engagement follows the same principle: start small, prove the value, then expand with confidence. Massive upfront data engagements have a way of producing a binder of information and no lasting change. We build the hierarchy the way plants actually adopt it, incrementally, with your people involved at every step.
Step 1: 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
Our engineers walk the pilot area, review nameplate data, evaluate the current hierarchy structure, and identify the specific gaps between what exists and what a component-level structure requires. We flag equipment boundary issues, missing BOMs, and naming inconsistencies before build work starts.
Step 3: 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. Their fingerprints on the structure create the buy-in that determines whether the hierarchy actually gets used.
Step 4: 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 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 in your system before, what it looks like now, and what the effort actually was. Leadership sees a concrete demonstration of what “done right” looks like.
Step 6: 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 your team, with usable data delivered at every phase.
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 the reliability standards bodies treat taxonomy as step one. SMRP’s Equipment Reliability body of knowledge identifies a defined asset taxonomy as the prerequisite for reliable failure data and maintenance strategy development. Skip the foundation and every downstream initiative inherits the gap. Dashboards. Analytics. AI-driven maintenance recommendations. All of it sits on top of the asset data model.
A hierarchy built to ISO 14224 conventions is portable, benchmarkable, and ready for whatever system comes next.
There is no translation step because there is nothing to translate. The engineer building your program is configuring the system your team executes in. When the engagement ends, the platform is already populated with every route, every specification, and every procedure ready for your first shift.
Built by People Who Have Operated the Equipment
Redlist’s implementation team has built asset hierarchies across mills, mines, energy operations, and heavy manufacturing. Our engineers have walked the plants, read the nameplates, and traced the parts back through purchasing records. They know what a well-structured hierarchy looks like and what happens when the structure is wrong.
Equipment boundaries drawn correctly. Component-level detail reserved for the assets where it pays off. BOMs captured from field reality, not from a spreadsheet somebody exported five years ago. QR and NFC tags applied at the right density, on the right assets, in the right locations. Standards references (ISO 14224, SMRP, API) applied where they matter, not layered on for show.
The hierarchy your team receives is built for how your facility actually operates, not for how a data model looks on paper.
Shift patterns, production schedules, and environmental conditions shape every route sequence. Storage and handling recommendations account for the climate, dust exposure, and physical layout of your plant. Routes are walked, validated, and optimized in person before a single technician opens the app. The program your team receives is built for how your facility actually operates.
The Advantage of Starting With a Pilot
One Line Proves the Value
Massive plant-wide data engagements have a way of producing a binder and no lasting change. Starting with a single line means measurable output in weeks, not a proposal that sits in a folder for a quarter. You see what changed. You see what it cost. You know whether to keep going.
Measured Baseline, Real Plan
Real hours per line replace estimates and assumptions. The pilot becomes the yardstick for scoping the rest of the site, so leadership gets a grounded plan sequenced by budget and priority, not a top-down estimate that inflates on contact with reality.
Usable Data at Every Phase
Every phase of the build delivers a live, usable slice of the hierarchy. Work orders, PMs, and parts data attach to real assets from day one of that phase. You do not wait for a plant-wide cutover to see operational impact. Reliability programs improve as the data foundation extends across the facility.
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. You will know real numbers after one area instead of trusting an estimate for the whole plant. 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/CMMS (Maximo, SAP, JD Edwards), or synced across both with bidirectional data flow. We do not ask you to rip and replace. 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. If your existing hierarchy has naming inconsistencies or misclassified equipment (a drive motor buried inside a parent machine, for example), those 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, and 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. A hierarchy handed down from outside is a hierarchy nobody uses. When your people have fingerprints on the data, they trust it, and they use it.
See What Your Hierarchy Is Missing
