Series: Asset Management 101 – The Blueprint.

In Part 06, we discussed the core concepts of Criticality and Risk, the tools we use to make efficient decisions. But those decisions are only as good as the information behind them. This brings us to one of the most critical assets an organisation can hold: Data.

In this post, we explore how to establish an asset management data foundation, moving away from the guesswork of “what to fix” toward the science of “how do we know”.

Remember:

You cannot manage what you do not measure. In an increasingly digital world, an asset without a data record is effectively invisible.

---

1. The Asset Register: A “Birth Certificate” for Equipment

The first key principle is that every asset your organisation owns or manages must have a unique identity. Think of it as the asset’s birth certificate or National Insurance number.

This identity is held in an Asset Register. Much like a census, it is a master list of everything you are responsible for. While every organisation needs different levels of detail, your foundation should answer five core questions for every entry:

1. What is it? (Classification/Type)
2. Where is it? (Location/GIS coordinates)
3. How critical is it? (The impact of it failing)
4. Who is responsible for it? (The owner vs. the maintainer)
5. How do we identify it? (The unique ID number or tag)

---

2. Asset Information Requirements (AIR): The Question Set

How do we decide what data to collect? We use Asset Information Requirements (AIR). These are formalised “question sets” that define what information is needed to operate the asset effectively.

A common mistake is trying to collect everything. This leads to “Data Swamps” where useful information is buried under noise. To avoid this, use the “So What?” Test:

Ask yourself: “So what happens if I don’t have this data?” If you can’t identify a specific decision that requires that data point, you probably don’t need to collect it.

Information requirements are guided by the ISO 19650 framework. We will explore the technicalities of this standard in a future session, but for now, you can consider ISO 19650 as your satnav on a long journey, it ensures your data stays on the right track from day one.

---

3. Condition vs. Performance: Arriving at Insights

Data points are often siloed, but the real power comes from combining them.

The Bridge Example:

• Condition: An inspection shows signs of wear and tear (rusting joints).
• Performance: Traffic sensors show the bridge is carrying 20% more heavy lorries than forecasted.

By combining these, we gain an “Insight” or “Asset Intelligence”. We realise the rust isn’t just old age; it’s being accelerated by over-utilisation. We can therfore calculate the Remaining Useful Life (RUL) and move our maintenance schedule forward before a failure occurs.

---

4. Data Validity: The “Data Decay” Problem

Like the physical assets themselves, data decays if not maintained. If a technician replaces a pump but doesn’t update the register, your data has “decayed”; it no longer reflects the Ground Truth.

The Solution: You must establish a “Data Culture”. The person on the tools needs to understand that updating the digital record is just as important as the physical repair. This ensures the Golden Thread (from Part 05) remains unbroken.

Takeaways

• Data is an Asset: It requires maintenance and investment, just like a pump or a building.
• Quality over Quantity: Structured, “clean” data is more valuable than a messy pile of “Swamp data”.
• Handover is Critical: The most dangerous time for data is during the handover between lifecycle stages (e.g., from the builder to the operator).
• Asset Management Data Foundation: Is one of the most critical factors in an organisations ability to fully embed Asset Management.

---

Next Step: In Part 08, we will look at Maintenance Strategies. Now that we have the data, how do we use it to move from “fixing things when they break” to “predicting the future”?