Discover
Maintenance Break
Maintenance Break
Author: Maintenance Break Podcast
Subscribed: 0Played: 5Subscribe
Share
© Maintenance Break Podcast
Description
Bite-sized lessons, one break at a time.
Whether you're on a coffee break or between jobs, Maintenance Break is your quick fix of practical insights into asset management, maintenance strategies, and reliability. Hosts Pete and Drew deliver jargon-free tips, real-world examples, and a dash of good humour—all in under 10 minutes.
Perfect for maintenance professionals, engineers, supervisors and anyone looking to make sense of the systems that keep everything running.
New episodes every fortnight.
Because sometimes, all you need is a maintenance break.
Visit us at www.jebsadvisory.com
Whether you're on a coffee break or between jobs, Maintenance Break is your quick fix of practical insights into asset management, maintenance strategies, and reliability. Hosts Pete and Drew deliver jargon-free tips, real-world examples, and a dash of good humour—all in under 10 minutes.
Perfect for maintenance professionals, engineers, supervisors and anyone looking to make sense of the systems that keep everything running.
New episodes every fortnight.
Because sometimes, all you need is a maintenance break.
Visit us at www.jebsadvisory.com
34 Episodes
Reverse
"Get out there and drive 'em like a taxi." Then the same operator drops a wheel into a pothole and gets a very different conversation. Two messages, same crew, same morning, and the operator does the maths. Pete and Drew break down why operators stop reportingdamage, and what a site can do about it: make it safe to speak up, then do something with what they say. Performance puts accident damage against a 24 hour day, per machine, per year. Cost is the fault code reset button, and how one ignored code turns a planned job into next week's breakdown. Risk is thehaul road damage everyone has stopped seeing, and the stress cracks in the frame underneath. Break Tip: Tomorrow, at shift handover, catch one operator and walk round their machine with them. Five minutes. Ask three things. What's been bumped, knocked or damaged? What alarms have you recently acknowledged or reset? And what did you tell us that nobody came back to you on? Write it down. Then take the last item on that list and find out what happened to it. Within the week, go back and tell the operator, even if the answer's "we couldn't fix it, and here'swhy."
Hundreds of hydraulic hoses reinstalled after a repair. Some have no clamp, some have no grommet, and the work order says complete.Pete and Drew walk the failure curve left to right, from oil analysis and vibration to the operator who hears it, feels the heat or smells it, and why the further left you catch a problem, the more choices you keep. Sensors and AI only tell you sooner. What happens next is people and process: identify, report, plan and schedule, execute to a standard.Break Tip: Tomorrow, pick one machine on service. Look at every hydraulic hose you can see. Are clamps in place? Are there rubber grommets between the clamp and the hose? Are there any obvious rub marks on hoses anywhere? Capture what you find. Then follow one of them back through the chain. If you find a hose that's rubbing, go into the system. Was it reported? When? If it was reported and it's still there, you know exactly where your chain breaks.
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.




