Building a Digital Asset Management Taxonomy: How Cryotos Manages It

Calendar
Duration:
10 min
calendar today
Published on
October 20, 2026
Featured Image

A digital asset management taxonomy is the shared structure that sorts, names, and describes every asset record. In maintenance, those records are the equipment entries in a Computerized Maintenance Management System, plus the manuals, photos, and certificates attached to each one.

This guide covers maintenance asset records, not marketing media libraries. You will build a taxonomy in four steps, document it in a register template, and see how Cryotos manages each layer.

Key Takeaways

  • Build in layers: Sort assets by class, location, and function first, then add identity, attributes, and files.
  • Use lists, not free text: Pick lists for class, status, and criticality keep search and reports clean.
  • Attach files to records: A manual linked to the asset gets used, while a manual in a shared folder gets lost.
  • Give the taxonomy an owner: Named owners and a change log stop the structure from drifting.

What Is a Digital Asset Management Taxonomy?

What a digital asset management taxonomy organises on one asset record | Cryotos

A digital asset management taxonomy gives each asset a class, a place, a name, a set of facts, and a list of files. The idea of taxonomy comes from biology: a tree of categories that moves from broad groups to specific members.

Most maintenance teams feel the gap when search fails. A taxonomy fixes four common symptoms:

  • Duplicate records: The same pump appears under three names, which splits its history.
  • Wrong documents: A technician opens an old manual because no one controls versions.
  • Reports that do not roll up: Downtime cannot be grouped by class because classes are inconsistent.
  • Slow audits: Staff search email and shared drives for proof.

Industry standards formalize the same structure. ISO 14224 defines a nine-level equipment taxonomy, from industry down to individual parts. ISO 55000 asset management standards likewise stress accurate, controlled asset information.

A taxonomy turns a pile of records into a searchable, reportable system.

The Six-Layer Stack Behind a Digital Asset Management Taxonomy

The six-layer asset taxonomy stack: class, location, function, identity, attributes, files and status | Cryotos

A digital asset management taxonomy works as six layers, and each layer answers one question about an asset. Build the layers in order, because each one depends on the layer before it.

The Six-Layer Asset Taxonomy Stack:

  • Class: What kind of asset is it? Examples are pump, chiller, and torque wrench.
  • Location: Where does it sit? Site, building, area, and line answer this.
  • Function: Which system does it serve? Compressed air and cooling water are examples.
  • Identity: What is its permanent, unique ID? No two assets share one.
  • Attributes: Which facts do you record? Make, model, serial number, criticality, and owner are typical.
  • Files and status: What is attached, and is the asset in service? Manuals, certificates, and lifecycle status live here.

Layers one to three sort the asset. Layer four names it, layer five describes it, and layer six attaches proof and control.

See how Cryotos structures classes and parent-child hierarchies in its asset tracking module.

Step 1: Define Class, Location, and Function Layers

Four-step process to build a digital asset management taxonomy | Cryotos

Define how assets are sorted before you load a single record. These three layers set the shape of the whole digital asset management taxonomy.

Set Your Classes and Hierarchy Levels

Group assets into a short list of classes, such as rotating equipment, electrical, HVAC, and instruments. Keep the hierarchy to five levels or fewer: site, area, line or system, asset, and component.

A parent-child hierarchy is a tree in which each asset sits under the system or place that contains it. Create a component record only when you plan to maintain, inspect, or replace that part on its own.

Use Location for Where and Function for Why

  • Location: Tells a technician where to walk.
  • Function: Shows which system stops when an asset fails.

Most plants need both views, so use one location tree for dispatch and a system tag for reports. A hybrid setup works like a faceted classification, where one asset can be viewed by location, by function, or by class.

Cryotos supports location-based, function-based, and hybrid structures, so teams keep every view without duplicating records. Settle these three layers first, because every later step depends on them.

Step 2: Standardize Identity and Attributes

Give every asset one permanent ID, then record the same attributes for every asset in a class. Consistency matters more than detail.

Build a Permanent ID for Every Asset

Use a short, structured code made of site, area, class, and a padded number, such as P1-UTL-CMP-003. Never reuse the ID of a retired asset, because old work orders and reports still point to it.

Choose the Attributes Each Class Must Carry

Not every field belongs on every asset. Define a core set for all assets, then add fields for each class.

  • Core fields: Make, model, serial number, install date, criticality, and owner.
  • Class fields: Flow rate and motor power for pumps, or range and tolerance for instruments.
  • Link fields: Parent asset, location, and attached documents.

Controlled Vocabulary vs Free-Text Tags for Asset Data

A controlled vocabulary is an approved list of terms that everyone must pick from. Library science uses the same idea, known as a controlled vocabulary, to keep one concept under one spelling.

AspectControlled vocabularyFree-text tags
Data entryPick one approved termType any wording
SearchOne spelling per conceptMany spellings for the same thing
ReportingGroups cleanly by class or statusNeeds manual cleanup first
ChangeNew terms need approvalNew terms appear instantly
Used forClass, status, criticality, and failure causeNotes and one-off context

Use lists for anything you filter or report on, such as class, status, and criticality. Keep free text for notes and one-off context.

Together, these fields form your asset metadata. Cryotos lets managers filter assets by any attribute and apply bulk scheduling or cost reporting to the filtered group.

Step 3: Organize the Files Attached to Each Asset

Attach every file to the asset it describes, and give each file a type. A manual stored in a shared folder gets lost, while a manual attached to the pump record is there when the technician needs it.

A linked document is a file stored on an asset record instead of in a separate folder. Linking keeps the asset and its paperwork together for its whole life.

Define a Short List of Document Types

  • Manuals and datasheets: Keep only the current revision, and archive older ones.
  • Procedures and safety documents: Link the SOP that applies to the asset class.
  • Certificates and calibration records: Add an expiry date, so lapses are visible.
  • Warranty and purchase records: Attach them at commissioning.
  • Inspection photos: Label each photo with the date and the finding.

Tag each asset with a QR label so a technician who scans it lands on the record and its files. Cryotos supports QR code scanning from its mobile app for exactly this purpose.

Document types are the layer of a digital asset management taxonomy that technicians notice first, because they open these files on the job.

Step 4: Control Ownership, Status, and Changes

A taxonomy stays accurate only when someone owns it. Assign a named owner, define lifecycle statuses, and record every change.

Taxonomy governance is the set of rules for who may add, change, or retire a term. Without those rules, every team invents its own classes.

Name Clear Owners for Every Layer

  • Taxonomy owner: Approves new classes, terms, and fields.
  • Asset owner: Keeps each asset record complete and correct.
  • Approver: Signs off status changes such as retirement.

Use Lifecycle Status to Keep Records Honest

Four statuses cover most plants: commissioning, active, retiring, and retired. Each status should control what the asset can do, such as receiving preventive maintenance tasks. This mirrors asset lifecycle management practice, where every stage has an owner.

  • Log changes: Cryotos stores field-level change history in its audit log, so each edit shows the user, the time, and the before and after values.
  • Share one structure: Teams that manage several plants often run one taxonomy through EAM software, so every site uses the same classes and terms.

A named owner and a change log keep a digital asset management taxonomy from drifting.

Taxonomy Register Template: Example Rows

Use this register to document each layer of your digital asset management taxonomy before you load data. The example rows describe a small manufacturing plant.

LayerQuestion it answersExample valuesField typeOwner
ClassWhat kind of asset is it?Centrifugal pump, air compressor, torque wrenchPick listReliability engineer
LocationWhere does it sit?Plant 1 / Utilities / Compressor roomParent-child treeMaintenance manager
FunctionWhich system does it serve?Compressed air systemPick listProduction engineer
IdentityWhat is its unique ID?P1-UTL-CMP-003Auto-numbered textMaintenance planner
AttributesWhich facts do we record?Make, model, serial number, criticality HighLists, text, and datesAsset owner
Files and statusWhat is attached, and is it in service?Manual v3, calibration certificate, status ActiveDocument type list and status listAsset owner and approver

Fill in one row per layer, then test the register against three real assets. If a technician cannot describe an asset with it, simplify the taxonomy.

How Cryotos Manages Your Digital Asset Management Taxonomy

Cryotos keeps every layer of the taxonomy inside one asset record, so structure, files, and history stay together. The platform's asset maintenance management software covers the full stack.

  • Class and hierarchy: Build site, area, line, asset, and component trees in location, function, or hybrid form.
  • Attributes: Each asset carries a full profile, including purchase date, manufacturer, model, and maintenance history.
  • QR identity and files: Every asset gets a QR or barcode label. A scan opens the record, history, and attached documents on mobile.
  • Status and approvals: Assets move through lifecycle statuses, and a move can require approval.
  • Audit trail: Field-level change history records who changed what, and when.
  • Reporting by class: A BI dashboard rolls up downtime, cost, and work by asset class, because every work order links to a classified asset.

Reliable records pay off in the field. Maintenance teams using Cryotos have reported up to 30% reduction in unplanned downtime and 25% faster repair turnaround. Results depend on how consistently teams record data.

The taxonomy sets the rules, and Cryotos applies them whenever a record is created, scanned, or changed.

Common Taxonomy Mistakes to Avoid

Most maintenance teams that struggle with a digital asset management taxonomy make the same few mistakes.

  • Too many levels: Hierarchies deeper than five levels slow technicians down.
  • Free text where lists belong: Spelling variants split reports into pieces.
  • Overlapping classes: A pump filed under two classes shows up twice in reports.
  • No owner: Without one, new terms appear unchecked.
  • No review: Plants change, so review the taxonomy at least once a year.

A simple taxonomy that people follow beats a perfect one they ignore.

Frequently Asked Questions

What is a digital asset management taxonomy in maintenance?

It is the shared structure that classifies, names, and describes asset records and their attached files. It covers classes, locations, IDs, attributes, documents, and status. The goal is to find and trust any record in seconds.

How is a taxonomy different from an asset hierarchy?

An asset hierarchy is one layer of the taxonomy: the parent-child tree of places and systems. The taxonomy also covers classes, IDs, attributes, files, and status.

How many levels should an asset taxonomy have?

Most plants work well with five hierarchy levels or fewer. ISO 14224 uses nine levels for complex process industries, which is a useful reference but more than most sites need. Add a level only when you track work at that level.

Does every asset need a QR code label?

Every maintainable asset should have one. The label links the physical item to its record, files, and history. Use durable labels in hot, wet, or dusty areas, so scans keep working.

Who should own the taxonomy?

A maintenance or reliability lead usually owns it and approves new terms. Asset owners keep individual records correct. Finance or compliance can approve status changes for high-value or regulated assets.

Can a CMMS manage a digital asset management taxonomy?

Yes. A CMMS stores the hierarchy, attributes, IDs, files, statuses, and change history in one record. Cryotos adds QR scanning, bulk actions on filtered assets, and field-level audit history.

A clear digital asset management taxonomy makes every asset record faster to find and easier to trust. Schedule a free demo to see how Cryotos manages asset structure, files, and history in one system.

Want to Try Cryotos CMMS Today?

Get Free Demo

Let AI Take Control of Your Maintenance

Cryotos AI predicts failures, automates work orders, and simplifies maintenance—before problems slow you down.

Try AI-Powered CMMS
🡢