ReliabilityX

Author: Joseph Anderson

  • Three Arguments Your Hourly Rate Wins for You 

    Three Arguments Your Hourly Rate Wins for You 

    You now have a number: what one hour on your constraint is worth. Here is how to spend it this week. None of these require a project, a budget, or anyone’s approval. 

    1. Should we take the line down for the planned work? 

    This argument usually runs on instinct and organizational politics. Operations does not want the downtime. Maintenance does not want the failure. Both positions are reasonable and neither is quantified, so the loudest voice wins and the decision gets remade every month. 

    Reprice it. 

    A four hour planned intervention on our packaging line costs $24,000 in contribution margin. That is the cost of saying yes. 

    Now the other side. Pull the history on the failure mode you are trying to prevent. If the unplanned version has historically run eight hours, it costs $48,000 each time it occurs. If it has occurred twice in the last twelve months, the expected annual exposure is $96,000. 

    The comparison is now arithmetic, and it can be documented, revisited, and defended. Sometimes the answer will be to defer, and that is fine. A deferral you can justify is worth more than a shutdown you cannot. 

    2. Is the spare part worth stocking? 

    Inventory arguments are among the longest running and least resolvable disputes in most plants, because the two sides are measuring different things. Materials management is measuring carrying cost and working capital. Maintenance is measuring the wait. 

    Price the wait. 

    A critical part with a six hour lead time on a constraint asset is protecting $36,000 every time the failure occurs. A $9,000 part with a two year expected life, against a failure mode that occurs annually, is not an inventory decision at that point. It is obviously correct, and it takes one line to show. 

    The reverse also applies, and you should be willing to run it. Plenty of parts sitting in stores protect assets with protective capacity, where the wait costs nothing. Pricing the hour cuts both ways, which is exactly what makes it credible when you use it in your favor. 

    3. Was the overtime worth it? 

    Every plant approves recovery overtime and almost none of them measure the return. 

    An overtime shift that genuinely recovers five constraint hours returns $30,000 against a few thousand dollars of premium labor. That is a decision worth repeating and worth telling your plant manager about. 

    An overtime shift spent on an asset that was never the constraint returns nothing, regardless of how much work got done. That is also worth knowing, and the honest version of this analysis is what makes people trust the favorable version later. 

    Run last month’s overtime through the rate. Whatever the answer is, you will have learned something your plant did not previously know. 

    The pattern 

    All three of these are decisions your plant is already making, repeatedly, using judgment. None of them are bad decisions. They are simply unpriced, and unpriced decisions drift toward whoever argues most persistently rather than toward whatever is worth the most. 

    You are not adding a process. You are adding a number to a conversation that was already happening. 

    This week 

    Take one real decision from your own plant this month and reprice it with your rate. Write down the before and the after. 

    Bring that repriced decision into next week, because next week we stop estimating and start counting, and you will want an example of what the rate is for.  

  • Scheduled Time or Calendar Time, and Which One to Defend 

    Scheduled Time or Calendar Time, and Which One to Defend 

    Once you have sized your hidden plant, the first challenge you get will be about the denominator. It is a fair challenge and you should have the answer ready, because the two available answers are both correct and they serve different audiences. 

    Against scheduled time 

    This measures the hours you staffed, powered, and paid for. Weekends you did not run, shifts you did not staff, and planned shutdowns are excluded. 

    It is the plant manager’s number. It is fair to the crew, because it only counts time the plant asked the asset to produce. It is defensible on the floor, because nobody can argue that you are charging them for hours the business chose not to schedule. And it is the right basis for the case you are going to build, because the action you will propose operates inside scheduled time. 

    On our packaging line, that number is $10.5mm a year. 

    Against calendar time 

    This measures the asset you actually bought, all 8,760 hours of it. 

    It is the capital committee’s number. It answers a different question: how much of the equipment on the balance sheet is producing margin, and how much capacity is available without buying new steel. It is the number a private equity buyer runs during diligence, and it is the number that competes directly with a capital request for additional capacity. 

    It is always larger, sometimes dramatically so, and it is uncomfortable in a way that is occasionally productive. 

    Why the choice matters more than the arithmetic 

    Use the wrong one in the wrong room and you lose the room. 

    Put the calendar time figure in front of a crew that has been working hard and you have told them, in effect, that their best week was a fraction of what it should have been. It reads as an accusation regardless of your intent, and the honest counting you are about to ask them for will not happen. 

    Put the scheduled time figure in front of a capital committee that is weighing a new line and you have understated your own case, because the committee is deciding about the asset, not about the shift schedule. 

    The rule is simple. Build the case on scheduled time. Keep the calendar time number in your pocket for the capital conversation, and produce it only when someone proposes buying capacity you may already own. 

    The reflex this is aimed at 

    When demand rises, the reflex is a capital request. New line, new packer, new building. The business case is straightforward, the approval path is well worn, and the request moves quickly because everyone involved knows how to evaluate it. 

    Meanwhile the hidden plant sits inside assets already on the balance sheet. It requires no capital approval, no installation window, no ramp up curve, and no additional floor space. And it produces nothing, because nobody has sized it and therefore nobody has proposed it. 

    The question worth putting in front of leadership is not whether to add capacity. It is whether to collect the capacity already purchased before purchasing more. That question has never been asked in most plants, and it is not asked because the number required to ask it does not exist. 

    The objection you will get 

    “We cannot sell everything we make.” 

    This is the right challenge and it deserves a real answer, which is that recovered hours can be taken three ways. As volume, where they convert to margin at full value. As cost, by running fewer scheduled shifts for the same output and removing premium labor and utility hours from the base. Or as capacity held, where the hidden plant becomes a capital avoidance argument and the next line gets deferred by years. 

    The mistake is treating an unsellable hour as a free one. It is not free. It was paid for. 

    This week 

    Calculate both numbers. Present one. Know which room you are in. 

  • Your Plan Is Not Your Capacity 

    Your Plan Is Not Your Capacity 

    There is a plant somewhere this month that will beat plan by three percent, hold a short celebration, and leave $10mm of contribution margin on the floor. Nobody involved will do anything wrong. 

    The mechanism is the plan itself. 

    How the plan absorbs the losses 

    Production plans get built from history, because history is the most defensible input available to a planner. Last year’s actual output becomes this year’s baseline, adjusted for demand, mix, and known changes. Nobody would design it differently, and as a scheduling instrument it works. 

    The problem is what history contains. Last year’s actuals already include last year’s unplanned stops, last year’s slow running, last year’s long changeovers, and last year’s rework. All of it is priced into the baseline as if it were a property of the asset rather than a set of losses that could be recovered. 

    So the losses get inherited, and then they get hidden, because once they are inside the plan they stop being losses and start being the plan. 

    Beat it and you are performing. Miss it and you are underperforming. In neither case does anyone ask the question that finds the money: what was the asset capable of? 

    The two plants 

    It is easier to hold if you think of it as two plants operating in the same building. 

    The visible plant is what you shipped. It is measured, reported, budgeted, forecast, and rewarded. Everything about it is well governed, and it is the plant your P&L describes. 

    The hidden plant is the output you already have every resource to produce and are not producing. Fully staffed, fully powered, fully supplied, fully paid for, and not collected. It has no reporting, no owner, and no line in the budget. 

    The hidden margin is the money trapped in the second plant. It is contribution margin that the fixed cost base has already been paid to produce. 

    That last point is what makes this an executive conversation rather than a maintenance one. You are not proposing to spend money to create capacity. You are proposing to collect capacity you have already bought. 

    What it looks like in numbers 

    Back to the packaging line. Case packer constraint, 600 bags per hour design rate, 417 scheduled hours in the month, $10 contribution margin per bag. 

    Design output at scheduled time: 250,000 bags. 

    Actual good output: 162,500 bags. 

    Hidden plant: 87,500 bags per month. 

    At $10 per bag, that is $875,000 a month, or $10.5mm a year, on one asset. 

    Last week the same asset produced a $1.5mm figure when measured against plan. The plan was concealing a factor of seven. 

    Note what this figure is measured against. Scheduled time only. It excludes weekends and unstaffed shifts entirely, which is what makes it fair to the crew and defensible on the floor. 

    The word that matters is hidden 

    Not lost. Not wasted. Not broken. 

    Hidden means already owned and not collected, and that is a fundamentally different conversation to have with a CFO. Lost capacity sounds like an accusation. Uncollected capacity sounds like an asset, which is exactly what it is, sitting on a balance sheet you are already depreciating. 

    This week 

    Take your asset. Find its design rate, confirm it against the best sustained rate you have documented evidence for, and use the lower figure. Count scheduled hours for one representative month. Multiply. Subtract actual good output. Multiply the gap by contribution margin. 

    Then resist the urge to soften the answer. 

  • Size Your Hidden Plant in Twenty Minutes 

    Size Your Hidden Plant in Twenty Minutes 

    This is the whole calculation. It takes longer to schedule the meeting about it than to do it. 

    The four inputs 

    1. Design rate. Units per hour the asset was built to produce. Start with the nameplate or the original equipment documentation. 

    2. Scheduled hours. Hours in a representative month that the plant asked this asset to produce. Exclude unstaffed shifts and planned shutdowns. 

    3. Actual good output. Units in that same month that were saleable. Good output, not gross output. Anything reworked or scrapped consumed a constraint hour you cannot resell. 

    4. Contribution margin per unit. Price less variable cost, sourced from finance in writing. 

    The arithmetic 

    Design rate times scheduled hours gives design output. 

    Design output less actual good output gives the hidden plant in units. 

    Hidden plant units times contribution margin gives your hidden margin. 

    For our packaging line: 600 bags per hour times 417 hours is 250,000 bags. Less 162,500 actual gives 87,500 bags. At $10 per bag, $875,000 a month, $10.5mm a year, one asset. 

    When the design rate is a problem 

    This is where most people stall, so here is how to handle each case. 

    The nameplate is missing. Ask the original equipment manufacturer, who will usually have it against the serial number. Failing that, use the best sustained rate the asset has actually demonstrated, documented from a production log rather than from memory. 

    The nameplate is obviously inflated. Common, particularly where the asset was specified for a different product or package format than it now runs. Use the best sustained demonstrated rate instead and note the substitution in your assumptions. 

    Nobody agrees on it. Ask two people who have run the asset at its best what it does on a good day. Take the lower figure. You are not trying to win an argument about the ceiling. You are trying to establish a number that survives challenge, and the conservative version does that better. 

    The principle throughout: a defensible number you can hold beats an ambitious number you have to retreat from. Every point you concede on the design rate makes the remaining figure harder to dismiss. 

    Write down your assumptions as you go 

    Four lines is enough. 

    Design rate, and where it came from. Scheduled hours, and what you excluded. Actual good output, and whether it is good or gross. Contribution margin, and who at finance provided it. 

    Those four lines are what turn your figure from an opinion into a calculation. The first person who challenges the number will challenge one of them, and having the answer ready is what ends the challenge rather than starting a debate. 

    Expect it to feel too big 

    It will. Nearly everyone’s first reaction to their own hidden plant figure is that it must be wrong, because a number that size would surely have been noticed. 

    It has not been noticed because nothing in the reporting system was built to notice it. The P&L cannot see uncollected capacity. The plan has already absorbed the losses. OEE, where it is tracked at all, is frequently reported as a percentage without ever being converted into money. 

    Do not shrink the number to make it comfortable. Test it, which is exactly what the next two weeks are for. If your counted losses land within about ten percent of your calculated gap, the number was right. 

    Your twenty minutes 

    Run the four inputs. Write the four assumption lines. Put the result in one sentence: this asset gives away X dollars of contribution margin per year at current performance. 

    Then carry that sentence into next week, where we start finding out where the hours actually went.

  • Your P&L Cannot See a Lost Hour 

    Your P&L Cannot See a Lost Hour 

    There is a reason smart executives look at complete, accurate financial statements every month and still cannot find the largest margin opportunity in the building. The statements are not wrong. They are answering a different question. 

    What happens to an hour that never ran 

    By the time production reaches the P&L, output has been converted into cost of goods sold, absorbed overhead, and variance. Every one of those figures describes what was produced. 

    The hours that were not produced have no representation. There is no line called capacity not collected. There is no variance account for the four hundred bags the case packer could have run during the shift it spent waiting on a changeover that took longer than it should have. 

    The only trace those hours leave is indirect. Fixed cost spread across fewer units raises absorbed cost per unit, which shows up next quarter as unit cost creep. In the review meeting, that gets discussed as inflation, supplier pricing, or product mix. It is occasionally all three. It is also, quite often, hours. 

    Why the plan makes it worse 

    The plan is the second layer of concealment, and it is well intentioned. 

    Plans are built from history, because history is the most defensible input available. Last year’s actuals become this year’s baseline, adjusted for demand and known changes. That is a reasonable way to run a scheduling function. 

    It is a terrible way to measure capacity. Every loss embedded in last year’s performance gets inherited into this year’s plan and then hidden by it. Beat the plan and the plant is congratulated. Nobody asks what the asset was capable of, because the plan has quietly become the answer to that question. 

    So you end up with a plant that looks efficient against a target that was set by its own historical losses. 

    The question that finds the money 

    Stop asking whether the plant hit plan. Ask this instead: 

    How many units did this asset have every resource to produce, and how many did it produce? 

    Every word in that sentence is doing work. Every resource means staffed, powered, supplied, and scheduled. It excludes the shifts you did not staff. It is a fair question, answerable from data you already own, and it produces a number the P&L will never give you. 

    On the packaging line we have been using, the answer is uncomfortable. At 600 bags per hour design rate across 417 scheduled hours in the month, the asset had every resource to produce 250,000 bags. It produced 162,500. 

    The gap to plan was 12,500 bags and $125,000. The gap to what the asset could actually do is 87,500 bags and $875,000 for the month. Same asset, same month, same data, and a number roughly seven times larger. 

    Two ledgers, one plant 

    It helps to think of it as two sets of books that never reconcile. 

    The financial ledger records what you shipped and what it cost. It is audited, governed, and correct. It is also complete only with respect to transactions that occurred. 

    The capacity ledger records what the assets could have delivered and did not. Nobody keeps it. It is not audited because it is not written down. And it holds the larger of the two numbers in most manufacturing plants. 

    You do not need to replace the first ledger. You need to start keeping the second one, on one asset, for one month. 

    What to do this week 

    Take the asset you picked on Monday. Find its design rate from the nameplate or the original equipment documentation, then confirm it against the best sustained rate anyone remembers running. Use the lower of the two, because a conservative number you can defend beats an ambitious one you cannot. 

    Multiply design rate by scheduled hours. Subtract actual good output. Multiply by contribution margin. 

    Expect the result to feel too large. Do not shrink it to feel comfortable. Test it instead. 

  • The Number Your Plant Missed Last Month, and Nobody Could Price It 

    The Number Your Plant Missed Last Month, and Nobody Could Price It 

    Last month your plant made money. It also missed the plan. Both of those things are on the same report, and if you walked into the morning meeting and asked what the miss was worth in contribution margin, you would most likely get silence, followed by three explanations, none of which carries a dollar sign. 

    That silence is worth about $1.5mm a year on a single asset. Here is how that number gets built. 

    The three explanations that never survive a follow up question 

    “We had a rough month.” This describes the result, not the cause. It cannot be sized, compared against last quarter, or attached to an action. It is a summary of the thing you were trying to explain. 

    “The equipment is old.” Age is not a loss category. Two identical assets, purchased the same year, installed on the same site, routinely run twenty points apart. If age were the cause, that would not happen. 

    “We are short people.” Sometimes true and usually incomplete. It rarely explains why the same crew delivered plan the month before with the same headcount. 

    None of these are dishonest. They are what capable people say when nobody has given them a counting system. The failure here is structural, not personal. 

    Why the number matters more than the excuse 

    Consider a packaging line with a case packer as the constraint. The plan for the month was 175,000 bags. Actual good output was 162,500. The gap is 12,500 bags. 

    Contribution margin on that product is $10 per bag, which is price less variable cost. Not gross margin, not revenue. Contribution margin, because the fixed cost base gets paid whether the line runs or not, so the full margin on recovered volume drops to the bottom line. 

    12,500 bags at $10 is $125,000 for the month. Annualized, that is $1.5mm on one asset. 

    That figure did not require new instrumentation, a software purchase, or a consultant. It required plan, actual, and one number from finance. 

    And here is the part worth sitting with: $1.5mm is the small number. It is the gap to a plan that was already discounted to what the line has been doing. The gap to what the asset can actually produce is considerably larger, and we will get to that. 

    Unmeasured margin never gets funded 

    This is the mechanism that keeps the money on the floor. 

    Finance cannot approve a number that does not exist. A capital committee is not hostile to reliability work, it is simply comparing proposals, and the proposal that arrives with a documented figure beats the one that arrives with a conviction. Capital flows toward the best documented problem, not the biggest one. 

    So the plant that describes its losses qualitatively competes for funding against a plant that describes them in dollars, and loses every time, regardless of which one actually has the larger opportunity. 

    Sizing the loss is not an accounting exercise you do after the improvement work. It is the first act of leadership on the problem, and it is what makes everything downstream possible. 

    What to do this week 

    Pick one asset. The one that sets the pace, where a stop stops the shipment. Pull plan against actual good output for the last eight weeks. Ask finance for contribution margin per unit, in writing, even if it is just an email. 

    Multiply the gap by the margin. Write the answer as one sentence with a dollar sign in it. 

    That sentence is a better management tool than any dashboard you will be sold this year, and it costs you fifteen minutes. 

  • Pick One Asset. Just One. 

    Pick One Asset. Just One. 

    Most efforts to quantify plant losses fail in week two, and the cause is almost always the same. Somebody decides that if one asset is worth measuring, the whole line is worth measuring, and by the end of the month there are eleven partial data sets and no defensible number. 

    One asset, followed for six weeks, produces a case you can take to a capital committee. Six assets, followed for six weeks, produce a spreadsheet nobody trusts. 

    Here is how to choose the one. 

    Test 1: It sets the pace 

    When this asset stops, does the line stop and does the shipment move? 

    That is the whole test. If output upstream of the asset simply accumulates and gets processed later, you have found a busy asset, not a constraint. Recovering an hour there costs you the same effort and returns nothing to the plant, because the hour was never the limiting factor. 

    The constraint is usually obvious to the people who run the line and frequently invisible in reporting. Ask two operators and a supervisor where the line backs up. They will agree, and they will be right. 

    A caution: the constraint moves. Product mix, seasonal demand, and a maintenance backlog can all shift it. For a six week exercise, pick the asset that is the constraint most of the time and stay with it. Chasing a moving constraint week to week is how the effort dies. 

    Test 2: You can get the data 

    You need run time and output for at least eight weeks of history, plus the ability to observe the asset for two weeks going forward. 

    Perfect data is not the standard. Retrievable data is. A production log in a binder is enough. A shift handover sheet is enough. If the asset is instrumented and you can export it, that is faster, but nothing here requires it. 

    If the data does not exist in any form, that is itself a finding worth reporting, and it usually means picking a different asset for this first pass rather than starting a data collection project you will not finish. 

    Test 3: Somebody owns it 

    There has to be a named person, an operator, a planner, or a supervisor, who can actually change something about how the asset runs. 

    This is the test people skip, and it is the one that determines whether your number turns into money. An asset nobody owns produces an interesting figure, a good slide, and no change at all. When the analysis is done, someone has to be able to act on it without waiting for a reorganization. 

    Write it down and say it out loud 

    Once you have chosen, commit publicly. Tell your plant manager which asset you are following and why. Put the name in an email. 

    This sounds like a small thing. It is the difference between an exercise that survives the first busy week and one that quietly stops. Named commitments get kept. 

    Your fifteen minutes this weekend 

    1. Name the asset. 
    1. Pull plan against actual good output for the last eight weeks. 
    1. Email finance and ask for contribution margin per unit, which is price less variable cost. If they push back, that conversation is itself worth having, because a finance blessed margin figure is nearly impossible to attack later. 
    1. Multiply the eight week gap by the margin. 
    1. Write the result as one sentence. 

    You now have one asset and one dollar figure, which is more than most plants have, and it is the input for everything that follows.

  • Business Acumen: Cost-Benefit Analysis 

    Business Acumen: Cost-Benefit Analysis 

    If you can’t turn the loss into a number, the project won’t get funded. Here’s how you turn it. 

    Cost-Benefit Analysis 

    You’ve found the loss, sized it, and picked your target. Now you have to ask for money, and that means building a case. The most common tool for deciding whether a project is worth doing is the Cost-Benefit Analysis, and the good news is the math is simple. The hard part isn’t arithmetic. It’s being honest about both sides of the ledger. 

    A Cost-Benefit Analysis weighs the benefits, the gains and savings, against the costs, the spend and investment, required to get them. The goal is to answer two questions: is this project worth doing, and how fast does it pay back? 

    Here’s the whole process in seven steps. Not seventy. Seven. 

    Step 1: Define the problem or opportunity 

    Be specific. Vague problems attract vague solutions and zero dollars. 

    • Weak: “The packaging line breaks down a lot.” 
    • Strong: “Unplanned downtime on the packaging line averages 8 hours a month, costing $24,000 a month in lost contribution.” 

    The difference between those two sentences is the difference between a complaint and a business case. 

    Step 2: Identify the solution 

    Propose a specific intervention with a scope, a timeline, and an owner. For example: precision alignment and balancing training for the six mechanics, plus a laser alignment tool kit. Concrete enough that someone could actually approve and schedule it. 

    Step 3: Estimate all the costs 

    All of them, not just the obvious capital number. The hidden ones are what sink projects after approval, when the real bill comes in higher than the pitch. 

    • Capital cost, such as equipment and tools. 
    • Labor, including training time, install labor, and project management. 
    • Materials and consumables. 
    • Lost production during install or startup. 
    • Ongoing costs, such as software licenses, maintenance, and recalibration. 

    Step 4: Estimate all the benefits 

    List both kinds, but only put the hard ones in the math. 

    Benefit type  Examples 
    Hard (use in the math)  Reduced downtime hours, less scrap and rework, less overtime, energy savings, longer asset life 
    Soft (mention, don’t count)  Improved morale, safer work, fewer customer complaints, less firefighting, easier hiring and retention 

    The discipline of using only hard dollars in the calculation is what makes your number credible upstairs. Soft benefits are real, but the moment you count them in the math, a skeptical CFO stops trusting the whole case. 

    Step 5: Calculate payback and ROI 

    Payback Period = Total Cost / Annual Benefit 

    ROI % = ((Annual Benefit – Annual Cost) / Total Cost) x 100 

    Step 6: Add the intangibles, separately 

    List the soft benefits on their own. They don’t change the math, but they tip close calls and they matter in the leadership conversation. Just keep them clearly out of the numbers. 

    Step 7: Run a sensitivity check 

    Ask the obvious “what if” questions before someone else does: 

    • What if the downtime savings come in at only half what we projected? 
    • What if costs run 20% over? 
    • What if it takes twice as long to implement? 

    If the project still wins under reasonable downside assumptions, you have a solid case. If it only works when everything goes perfectly, you don’t. 

    Real-world example: a precision alignment program. Problem: 8 hours a month of downtime tied to bearing failures, misalignment, and vibration. At $3,000 an hour in contribution, that’s $24,000 a month, or $288,000 a year. 

    Solution: laser alignment tools, training, and precision standards. 

    Costs: alignment tools $15,000, training for six mechanics $10,000, implementation labor $5,000. Total cost $30,000. 

    Benefits: six fewer downtime hours a month at $18,000 a month is $216,000 a year, plus $6,000 a year from extended bearing life and $4,000 a year from fewer rebuilds. Total benefit $226,000 a year. 

    The math: payback is $30,000 / $226,000, about six to seven weeks. ROI is (($226,000 – $30,000) / $30,000) x 100, which is 653%. 

    Verdict: invest immediately. 

    A case like that doesn’t get debated. It gets approved, because every number in it is hard, conservative, and traceable. 

    Try it yourself 

    Pick a project off your wish list and build the CBA in seven lines: 

    • Problem statement, with the dollar value of the current loss. 
    • Solution. 
    • Total cost, all in. 
    • Annual benefit, hard dollars only. 
    • Payback period. 
    • ROI percentage. 
    • Sensitivity: does it still win if the benefit is only half? 

    If you can’t fill in that first line with a real dollar number, that’s your homework before you go any further. 

    Key takeaways 

    • CBA is seven steps, not seventy. Keep it simple. 
    • Include all costs, not just the obvious capital. Hidden costs are what sink projects after approval. 
    • Use only hard benefits in the math. Mention the soft ones separately. 
    • Always sensitivity-check at half the projected benefit. If it still wins, your case is strong. 

    Coming next, Part 4, Post 2: ROI, Payback, NPV, and BCR Made Simple.

    If you are ready to turn your improvement ideas into funded projects, ReliabilityX can help. Our team works directly with your data to build clear, defensible business cases that leadership approves with confidence.

    Contact us to schedule a review of your plant and learn how to translate reliability improvements into measurable financial results.

  • Business Acumen: Where to Focus First

    Business Acumen: Where to Focus First

    You can’t fix all 30 losses at once. Even the best plants pick two or three a year. This is how you choose. 

    By now you can name the losses and size them in dollars. That creates a new and better problem: you can suddenly see more opportunity than you could possibly chase. So the skill that matters now isn’t finding losses. It’s choosing which ones to attack first. 

    The 80/20 pattern shows up here too 

    On any given line, about 80% of the loss is usually packed into just two or three of the 30 buckets. You don’t need a program that boils the ocean. You need to find those two or three in your specific plant, then match the right fix to each. Everything else can wait. 

    Three questions, in order 

    When you’re deciding where to point your effort, ask these in sequence: 

    • Which loss is biggest in dollars? Not hours. Dollars. And as you’ll see in a moment, an hour on the bottleneck is worth far more than an hour anywhere else. 
    • What will the fix cost? Capital, labor, and organizational change all count. 
    • How fast will it land? Quick wins matter more than they look, because they build the credibility that gets your slower, bigger projects approved. 

    Match the strategy to the loss 

    A breakdown is not fixed the same way as a speed loss. One of the most common mistakes is applying a single favorite tool to every problem. Here’s the rough mapping: 

    Loss type  Best strategy 
    Breakdowns  Asset strategy optimization, reliability engineering, root cause analysis, precision maintenance, lubrication management 
    Process Failures  Process engineering, design improvements, operator training 
    Setup and Adjustments  Standardized procedures, centerline management, training, discipline 
    Speed Losses  Defect elimination, line condition, materials handling improvements 
    Minor Stops  Operator care routines, incoming material specs, centerlining, workplace organization 
    Startup Defects  Structured changeover reduction, centerline standards, PM effectiveness 
    In-Process Defects  Process control monitoring, in-process checks, supplier quality, operator training 

    The bottleneck rule, and why it changes everything 

    This is the single most important idea in the post. 

    An hour saved on the bottleneck is an hour of brand-new throughput. An hour saved anywhere else is just less idle time on a machine that was never the constraint. 

    The bottleneck is the slowest step in the chain, the one that sets the pace for everything downstream of it. Always find it before you decide where to invest. The implications are blunt: 

    • Cut breakdowns on a non-bottleneck, and your total output may not move at all. 
    • Cut minor stops on the bottleneck, and every hour you save flows straight to shipments. 

    Real-world example: the same hour, two different outcomes. A snack-foods plant runs a slicer (1,200 lb/hr) feeding a fryer (1,000 lb/hr) feeding a packaging line (950 lb/hr). The bottleneck is the packaging line at 950 lb/hr, because it’s the slowest step. Now watch two equally hard engineering projects: reducing slicer breakdowns by 50% produces exactly $0 of new revenue, because the slicer was never the constraint. Reducing packaging-line minor stops by 30% directly increases shipments. Same effort, completely different financial result. Always start at the bottleneck. 

    Quick wins versus long plays 

    Sort your candidate projects on a simple grid of impact against effort. 

      Low effort  High effort 
    High impact  Do first. These quick wins build credibility.  Plan. These are your major projects. 
    Low impact  Do if easy. Fill in the gaps.  Avoid. Not worth the cycles. 

    On a typical line, the two corners look like this: 

    • Quick wins: operator care routines, kitting parts before PMs, centerline standards, basic changeover improvements, and knocking out the top five minor-stop causes. 
    • Long plays: a predictive maintenance program, machine redesigns, capital projects, and control system upgrades. 

    Try it yourself 

    Go back to the OEE calculation you ran in the last post: 

    • Identify your top three losses by hours. 
    • For each, multiply hours per week by your contribution margin to get dollars per week. 
    • Plot each one on the grid above using your gut feel for effort and impact. 
    • Pick the upper-left item as your first project. Pick the upper-right item as your annual goal. 

    Key takeaways 

    • Pick the two or three losses that hold 80% of your dollar opportunity, and ignore the rest for now. 
    • Match the strategy to the loss type. Breakdowns and speed losses are not solved the same way. 
    • An hour saved on the bottleneck is worth more than an hour saved anywhere else. Always. 
    • Quick wins build the credibility that funds the long plays. 

    Wrapping up Part 3 

    You’ve now closed the gap between naming a loss and sizing it. You can calculate where a line really stands, translate any loss into annual dollars, and choose the two or three targets that matter most, with the bottleneck rule keeping you honest about which hours actually count. 

    That’s everything you need to walk into a room with a number. What you need next is the language that turns a number into an approved project: payback, ROI, and the cost of doing nothing. That’s Part 4. 

     

    Coming next, Part 4: Building the Business Case. 

    If you are ready to identify the two or three losses that hold most of your opportunity, ReliabilityX can help. Our team works directly with your data to pinpoint the bottleneck, quantify the dollar impact, and design the strategy that delivers measurable results.

    Contact us to schedule a focused review of your plant and start turning hidden losses into recovered margin.

  • Business Acumen: The 10 Resource Losses

    Business Acumen: The 10 Resource Losses

    Equipment and labor losses cost you time. Resource losses cost you the stuff itself. And these are the ones Finance can already see. 

    Here’s why this last category is special. The equipment and human losses show up as time, and time has to be translated before Finance feels it. Resource losses skip the translation. They land straight in cost-per-unit and gross margin, which means they’re the losses your CFO is most likely to already believe. That makes them the easiest place to build a business case, and the rest of this series leans heavily on what you find here. 

    There are ten of them. 

    1. Rework. Producing a unit that isn’t acceptable as-is but can be repaired and sold. It’s a triple cost: the original materials, the labor to redo it, and the line time you spent reworking instead of making something new. 
    1. Raw Material Losses. Material lost to leaks, loose specs, contamination, damage, and poor storage. This is the one most often shrugged off as “the cost of doing business,” yet it commonly runs 1% to 3% of total raw material spend, which is real money on any plant of size. 
    1. Scrap. Material consumed in conversion that can’t be sold as the primary product: trim, edges, mixing residue. Sometimes you recover it as regrind, sometimes you don’t, but either way it dilutes your yield. 
    1. Spoilage. Product so off-spec or damaged it can’t even be reworked. This is the most expensive loss of all, because both the material and every hour of labor invested in it drop to zero value. 
    1. Packaging Materials Losses. Film, boxes, labels, and cases lost to defects, poor storage, and equipment misalignment. Often 2% to 5% of packaging spend, and almost entirely invisible until someone audits it. 
    1. Excess Inventory Losses. Cash tied up in inventory you don’t actually need, usually from forecasting errors and “just in case” thinking. Every dollar parked there is a dollar not paying down debt or funding improvements, and the carrying cost alone typically runs 15% to 25% a year. 
    1. Energy Losses. Energy wasted to compressed-air and steam leaks, idle-running equipment, oversized motors, and missing shutdown protocols. Studies consistently find 20% to 30% of plant energy is recoverable. On a plant spending $5M a year on energy, that’s $1M to $1.5M walking out the door. 
    1. Yield Losses. Giving away product because nobody trusts the process to hold a tighter spec. The classic case: a two-pound spec consistently filled at 2.05 to 2.10 pounds because the line can’t be trusted to stay above 2.0. That extra fraction of a pound on every unit is pure giveaway. 
    1. Changeover Time Losses. Production lost during product changeovers, driven by untrained operators, missing parts, and steps run one after another that could run in parallel. A line running six changeovers a week at 90 minutes each loses nine hours a week. Cutting changeover time in half is often worth $1M to $2M a year on a single line. 
    1. Overspending. Paying more than necessary on maintenance, MRO, contractors, supplies, and energy. The big driver is reactive work: every $1 of reactive maintenance costs roughly three to five times what the same job costs when planned. A plant running 40% reactive is overspending dramatically against one running 10% reactive. 

    Real-world example: the yield giveaway nobody noticed. A bagged-snack plant fills a 6 oz bag at an average of 6.18 oz, just to be sure they never go under spec. Annual volume is 50 million bags. That 0.18 oz per bag, across 50 million bags, is 9 million ounces, or 562,500 pounds of product given away every year. At a finished cost of $1.40 a pound, that’s $787,500 of pure giveaway annually, money walking straight out the door. The fix, tighter process control with predictive checkweigher feedback, cost $120,000. Payback: under two months. 

    That example is the whole category in miniature. Nothing broke. Nobody got hurt. No alarm went off. The plant simply gave away three-quarters of a million dollars a year, politely, one bag at a time, until somebody finally measured it. 

    Try it yourself 

    Identify your top three resource losses by dollar value: 

    • Pull or estimate the annual spend for each candidate: rework, scrap, packaging waste, energy, MRO, and so on. 
    • For each, estimate what a 10% reduction would save. 
    • Rank them by dollar opportunity, not by which one is easiest to fix. 

    Keep that ranked list. It becomes the raw material for the first business case we build in Part 4. 

    Key takeaways 

    • Resource losses are usually invisible until audited, and once measured they’re almost always bigger than expected. 
    • Energy waste, MRO obsolescence, and yield giveaway are the three most under-investigated buckets in most plants. 
    • Rework, scrap, and spoilage tend to get reported. The other seven buckets often don’t. 
    • Resource losses connect directly to gross margin, so reducing them moves the financial statements faster than anything else on the floor. 

    Wrapping up Part 2 

    You now have the full map. Thirty places money leaks out of a plant, sorted into machines, people, and resources, and you can tell which family any given loss belongs to. That alone puts you ahead of most rooms, because you can stop arguing about whose department is to blame and start pointing at named, sizeable targets. 

    But naming a loss isn’t the same as sizing it. A target you can’t measure still won’t get funded. So next we turn the 30 losses into numbers a CFO can act on, starting with the two that summarize everything: OEE and TEEP. 

     

    Coming next, Part 3: Measuring What Matters. 

    If you want to see where your plant’s money is quietly leaking, start with the resource losses. They’re already visible in your financials. You just have to measure them. If you want help identifying and quantifying these losses inside your operation, reach out.