Nearly every fleet starts on breakdown replacement, and most stay there because the alternative sounds like a project. It is smaller than it looks: the useful version of a hose programme is three columns and a decision about consequence.
/01The register.
A hose register lists every assembly on every machine you intend to manage, with enough detail to re-order it without going back to the machine. That is the whole trick — the register is what turns a two-hour identification job into a two-minute one when something fails at an inconvenient time. Record the construction as printed on the layline — 2SN, 4SP and so on — with the bore, the length and both fitting types.
Per assembly
- Done
Unique ID
Physically tagged on the assembly. Everything else hangs off this.
- Who
- Maintenance
- Tool
- Hose tag
- Done
Machine and position
Which machine, which circuit, where on it. Specific enough that someone who has not seen it can find it.
- Who
- Maintenance
- Tool
- Register
- Done
Specification
Bore, grade, length, both fitting types and the angle between them.
- Who
- Maintenance
- Tool
- Register
- Done
Date fitted
The single most useful field, and the one most often missing.
- Who
- Fitter
- Tool
- Register
- Done
Criticality
What happens to production if this one fails. Drives everything downstream.
- Who
- Engineer
- Tool
- Ranking
- Done
Failure history
What failed, where, and what was changed. This is what turns a guess into an interval.
- Who
- Maintenance
- Tool
- Register
/02Rank by consequence.

| Band | Failure consequence | Approach |
|---|---|---|
| AHighlighted | Stops production, or creates a safety or environmental hazard | Planned replacement, spares held |
| B | Degrades output or takes a machine off for hours | Planned replacement, spares available at short notice |
| C | Inconvenient, easily worked around | Condition-based; replace on inspection finding |
The band-A list is usually far shorter than people expect, and that is the point. A programme that begins with the twenty assemblies that actually stop the plant gets adopted; one that begins with every hose on site gets abandoned in month two.
/03Where the interval comes from.
From your own failure history, which is why the register has a failure column. Once you have a year of records on band-A assemblies you can see where they actually fail and roughly when — and that is a defensible interval in a way a published figure is not, because it already accounts for your duty cycle, your ambient temperature and your installation quality.
Common questions
- Is planned replacement not just throwing away good hoses?
- Some, yes — that is the trade. The question is whether the value of the hose discarded early is less than the cost of the outages avoided. On band-A assemblies it usually is by a wide margin; on band-C it usually is not, which is why they stay condition-based.
- What do we tag assemblies with?
- Anything durable that survives the environment and carries a unique ID. The technology matters far less than whether the ID is legible in three years and links to a record someone maintains.
- Can we run this without maintenance software?
- Yes. A spreadsheet with those six fields beats an unused module in an expensive system. Move it into your CMMS when the discipline is established, not before.
- How long before it shows a result?
- You see the register pay off immediately in faster identification. The reduction in unplanned failures follows the first full replacement cycle on band A.







