Fixed plant flaking with corrosion, and the site says it's meeting the intent of maintaining integrity. It's still standing, so it's fine.

Except standing isn't the required outcome. Pete and Drewbreak down what structural integrity actually means: keeping the asset in a non-degraded state so it can do its job. A structure that's lost material to corrosion but is still holding up isn't integrity maintained, it's integrity being spent.

They also cover why structural integrity isn't a separate piece of work run by a different team. It's one of the five categories in the maintenance strategy from the Asset Management Plan, and the first big call is knowing your critical assets: the ones that impact production or pose a high safety or environmental risk. Critical doesn't mean the oldest or the rustiest, it means the one that hurts most if it fails.

Break Tip: Tomorrow morning, ask two questions. First, doyou know your critical assets? Write down the structures on that list, even if it's only the five you can think of off the top of your head. Second, for each one, do you have the right inspection to manage it? Go into the system and find it: what is the inspection, how often does it run, and who last did it? A walk-past on a checklist isn't the same as someone qualified looking at the steel and concrete. If a critical structure has no list entry, no inspection against it, or an inspection nobody can show you the last result of, that's your starting point.

A 785C A-frame bearing failed. Two days of unscheduled downtime, a line bore, a proper RCA.

The RCA was genuinely good. The site found the bearing hadbeen installed wrong six months earlier, rewrote the install procedure, added QA checkpoints. Textbook root cause work.

Pete and Drew walk through what that RCA missed: an existing 1000-hour PM check had already flagged that same bearing out of spec, three times, and none of those flags ever made it into the CMMS. Once the site dug further, the same gap held across the whole mobile work group, not just the one bearing.

This is the Failure Response Model in action, four questionsto walk through after any failure, and why stopping at "we know the cause" isn't the same as being done.

Break Tip: Don't just check whether your PMs are getting done. Check whether the defects they flag get closed out. Pick one asset, pull its last few completed PM sheets, find a flagged comment, and trace it into your CMMS. Did it become a work order? If it didn't, check a handful of other assets the same way. If it's not just the one, you've got a work management gap, not a “bearing” problem.

Same site. Same fleet. Same final drives, same duty. Oneera: final drives ran to 20,000 hours before rebuild. A few years later: 15,000.

Nobody decided to stop watching the oil. It just stopped being anyone's daily job.

Pete and Drew break down FLAC (Fuel, Lubricant, Air, Coolant) as the full chain, not just an occasional oil sample: receiving and storing it clean, dispensing it right, monitoring it in service, and acting on what the results tell you. Three people control it day to day: the Maintainer at the dispensing point, the Storeman responsible for clean bulk supply, and the Engineer setting the target and following through on results.

Break Tip: Tomorrow morning, go have a look at your main dispensing point in the workshop, or the quick fill points on anasset's components. Check two things: are fill points capped or protected from the elements when not in use, and is the area around them clean? If you don't have a cleanliness standard, start there. If you do, treat what you find as a work quality education opportunity.