A working session for the April pour window: what a mixer costs per operating hour, and what it takes off your board before ownership asks.
None of this is a Meridian problem to fix. It is a clock problem: the maintenance schedule runs on a mile, and the mixer's life runs on a hydraulic cycle at a jobsite gate. Here is what that mismatch costs today.
A loaded mixer down has minutes before the drum, and the next pour, is scrap.
An hour pouring, idling at the gate, and sitting at plant all count the same.
Odometer schedules a mixer doing eleven thousand miles as practically new.
Fife and Mossvale each guess what the other yard is about to need.
Tobias has about forty minutes to find another truck before nine yards go off in the drum. Sixty one loads went that way last year, and the cost lands in dispatch's outcomes, not in Curtis's maintenance budget, so nobody has ever priced it in one place.
Component signal on the drum, hydraulics and PTO gives Curtis days of runway instead of a forty minute scramble. The truck gets pulled before it loads, not after.
Tobias has about forty minutes to find another truck before nine yards go off in the drum. Sixty one loads went that way last year, and the cost lands in dispatch's outcomes, not in Curtis's maintenance budget, so nobody has ever priced it in one place.
Component signal on the drum, hydraulics and PTO gives Curtis days of runway instead of a forty minute scramble. The truck gets pulled before it loads, not after.
Marisol has stopped bringing the Meridian utilization chart to the board because it invites a question she cannot answer: which of those hours was revenue. Odometer based reporting was built for a truck that drives, not one that stands at a gate with the PTO loaded.
Utilization gets reported by what the drum and PTO were actually doing, not by the odometer. The board question changes from what does an hour mean to what does a pouring hour cost.
Curtis's mixers log eleven thousand miles and fourteen hundred engine hours a year, and the drum, hydraulics and PTO run the whole shift regardless of road speed. Both yards have kept parallel spreadsheets for three years because the Meridian schedule cannot be trusted for this fleet, and only 58% of PM stays on schedule as a result.
The interval follows hydraulic load and PTO hours instead of the odometer. The two shop spreadsheets stop being the real schedule and the system becomes it.
Curtis has bought the same water pump twice in a week because Mossvale had one on the shelf and Fife had no way to know it. A downed mixer then waits an average of 31 hours for a bay, partly because the bay fills with jobs pulled forward when a part was not where it needed to be.
A repair gets booked against the yard that already has the part, or the part moves before the truck does. Bay time stops being consumed by jobs that jumped the queue.
Marisol was specific about the boundary: instrument the mixers first, leave the compliance stack alone, and show something before April. That rules out anything that starts with a fleet-wide cutover.
Northwind Systems reads hydraulic temperature and drum cycle drift over days, so a failing mixer gets flagged before it loads.
Preventive intervals follow engine hours, PTO load and hydraulic cycles instead of miles, matching how a mixer actually wears at a jobsite.
Fife and Mossvale scheduling both see what the other yard has on the shelf before a repair gets booked or ordered.
Mixers get instrumented first, one truck at a time, with Meridian and the compliance record untouched through the April pour.
Two roles, two mornings. Nothing here removes Meridian. It shows what changes upstream of the Monday fault code meeting.
Six questions, about two minutes. Answer honestly and you will see exactly where the April pour window is exposed today.
Marisol needs one page for ownership. Anneke needs a baseline agreed before install, not a feeling after it. These outcomes tie back to what leadership already said out loud.