Speaking from the Data

When seeking additional resources, base your requests on verifiable benefits

The executives running a company don’t see what the troops on the ground see. Consequently, differences of opinion often occur about how the company should allocate resources.

At the extremes in a fictional world, an electrician or maintenance technician would have a candy store full of the latest test equipment, and the CFO would save money by not purchasing any test equipment. In reality, electricians and technicians know there’s an upper limit on what can be purchased, and CFOs know there’s a lower limit.

The problem is one of reaching agreement in the middle. For example, you write a capital request for purchasing 10 new DMMs that have features you badly need. The CFO sees the request and thinks, “Didn’t we buy everybody one of these last year?” He takes a walk and, sure enough, every electrician he sees has a DMM on his belt or tool pouch. He denies the request.

Photo credit: manop1984/iStock/Thinkstock

Now, let’s revise this scenario. Let’s say your plant has a large number of variable frequency drives (VFDs). You’ve had a lot of downtime in the associated systems. Over the holidays, you took a road trip to visit your cousin who lives in another state. You and your cousin, who is also a maintenance electrician were talking shop. The motor problems came up.

Your cousin said his plant also had those problems, but then he showed you the DMM he’s been using to solve them. It has a VFD mode that permits accurately analyzing non-sinusoidal waveforms and noisy signals in the controllers. This feature would have saved four hours on Line 3 last week. And unlike your DMM, this one has a low impedance input filter that eliminates those ghost readings that took you down the wrong path for days.

Now that you’re back from visiting your cousin, you want one of those meters. How do you get the value across to the CFO?

One way to do this is to go through the last few months of downtime and repair reports. Look for half a dozen outstanding examples. Talk to the other electricians and technicians to get some examples and background information.

For each line or major piece of equipment that was down, determine the excess downtime that would have been prevented if only the responding electrician or technician would have had this one DMM. Then multiply the revenue per hour of that line by the excess hours of downtime. After you have this value for each line or piece of equipment, add up the individual values to get X.

On the cover sheet of your capital request, state that in just six examples the total revenue lost was X. Make a reference to an attachment that shows the math.

For example, “The plant lost $1.7 million in revenue from just six incidents involving excess downtime that would not have been incurred if the responding technician would have had this instrument (see Attachment 3). The total number of incidents is 28; this is just a sampling.”

In the attachment, be consistent in how you describe each incident. Most important, be concise. You want this to be not just readable, but scannable. Executives rarely have time to pore over dense material. Toward that end, it’s also smart to pull out anything you find yourself repeating and put it in explanatory text that follows the six examples.

Don’t go down a wish list of meter features. Sure, you’d really like to have Bluetooth and other connectivity, and maybe some other features that exist only in a high-end meter. Limit your capital request to those you can show from the data, to be real revenue savers. Nobody likes to drink from a fire hose, and executives are especially that way.

If, for example, you’ve never had an incident in which lack of Bluetooth caused a quantifiable loss of revenue, then don’t go there. Or maybe you did have plenty of such incidents, but in your case the VFD mode just doesn’t lend itself to quantifying any savings. Pick a key feature or two. The other ones you want will probably come with the meter anyhow, and you can later write reports about the downtime you saved with your trusty new meter.

When you can speak based on the data, and speak in financial terms, you can present a compelling case. You remove opinion and bias from the discussion and help executives to decide based on the merits of a case rather than their perceptions of your alleged misconceptions.

Just make sure you’re using good data and you can verify anything you use.

About the Author

Mark Lamendola

Mark Lamendola

Mark is an expert in maintenance management, having racked up an impressive track record during his time working in the field. He also has extensive knowledge of, and practical expertise with, the National Electrical Code (NEC). Through his consulting business, he provides articles and training materials on electrical topics, specializing in making difficult subjects easy to understand and focusing on the practical aspects of electrical work.

Prior to starting his own business, Mark served as the Technical Editor on EC&M for six years, worked three years in nuclear maintenance, six years as a contract project engineer/project manager, three years as a systems engineer, and three years in plant maintenance management.

Mark earned an AAS degree from Rock Valley College, a BSEET from Columbia Pacific University, and an MBA from Lake Erie College. He’s also completed several related certifications over the years and even was formerly licensed as a Master Electrician. He is a Senior Member of the IEEE and past Chairman of the Kansas City Chapters of both the IEEE and the IEEE Computer Society. Mark also served as the program director for, a board member of, and webmaster of, the Midwest Chapter of the 7x24 Exchange. He has also held memberships with the following organizations: NETA, NFPA, International Association of Webmasters, and Institute of Certified Professional Managers.

Sign up for our eNewsletters
Get the latest news and updates

Related

In the typical facility, the plant manager has X amount of discretionary spending power that can be directed toward a single purchase. At each level of management down, discretionary spending is stepped down into smaller amounts. Anything beyond a given manager’s limit must be appealed to the next level up. For example, the Plant Engineer can’t quite swing a purchase of $5200 but the Plant Manager can approve it. This informal arrangement reduces corporate overhead and improves operational efficiency. It does not address whether the spending decisions would make financial sense to the Chief Financial Officer, but the cap at each level keeps any mistakes to a reasonably acceptable loss or misallocation of resources. Beyond the Plant Manager’s limit, there is usually a formal process for getting spending approval. It typically involves filling out a Capital Request (or similarly named form). In well-run companies, the form is very structured. It mostly wants some basic information that will give the reviewer(s) the ability to justify not just the purchase but also the cost of acquiring the capital to do so. Because the funds will typically be borrowed by the corporation, the cost of capital must be balanced against the return on investment. There will be at least one person crunching the numbers to make what is called “the business case” for the proposed spending. Making the business case is something you should do, in some way or another, when considering spending within your approved limits. If the spending is above your approved limits, then the manager above you will need a bit beefier of a business case. The business case must take into account the value obtained versus the money spent. Consider the purchase of a thermographic camera. If you intend to purchase a mid-range camera but nobody at your facility is trained and certified in its use, the purchase is probably a waste of money. You’d be better off getting an entry-level camera and then arranging for a path toward certification if you intend to have that ability in-house and it makes operational and financial sense to do so. And generally, it makes sense to have a person or two with Level I certification so they really understand how to get the most out of a camera system that’s beyond the basic level. On the other hand, if you were a manager at an electrical testing firm with several Level III Thermographers you would be wasting your thermographers if you decided to “save money” by equipping them with only basic or even intermediate camera systems. Your firm needs to be able to troubleshoot problems when that important client calls in a panic. Your thermographers need the tools to do that job, and “cost-saving” on camera systems won’t cut it. Presumably, your clients are smart enough to already have basic camera systems; they just don’t have the expertise to use advanced systems. Sometimes a different logic applies to other types of test equipment. In the typical plant, maintenance electricians need sophisticated DMMs. If they lack the training to use the features that are needed for most effectively keeping equipment running, simply choosing a less capable DMM they already know how to use is not the answer. They need the appropriate DMM along with the training on how to use those features correctly. So far, we haven’t looked at the need to crunch any numbers to make the business case. What we have done is think about the match between the purchase, the problem that needs to be solved, and the ability of the user to solve the problem using that purchase. This sounds like a common sense approach that everyone would naturally take, but people often lose sight of the reason for the purchase in the first place. The tendency is to either go all out on something they can’t use or don’t need, or to “save money” by shortchanging the end users with something that doesn’t allow them to do what they need to do. What about those numbers? When you do a purchase request, a bean counter is going to try to determine the cash flows involved (typically in monthly periods). If you write something like, “The payback period is three years,” they don’t find that helpful. Lenders care that a loan can be serviced, and cash flow is the critical factor in calculating whether it can. Thus, beancounters don’t use payback to determine whether they can afford to borrow. They use the Internal Rate of Return (IRR) or Modified Internal Rate of Return (MIRR). Formulas for both IRR and MIRR have been in spreadsheet programs for over two decades, but before that they were determined using a Business Math Calculator (about $150 in 1990). And before that, they were laboriously calculated by hand. The cash flows that are charted will be either additional revenue generated or losses prevented. To help the person who figuratively wears the green eye shade, tie the use of the test equipment to a revenue stream. A major appliance plant in Tennessee has several production lines that collectively produce $1,560,000 per hour of revenue. Thus each minute of unplanned downtime is quite costly. If the plant electrical engineer there wanted to upgrade test equipment in a way that exceeds the Plant Manager’s spending authority, he needs to help the green eye shade guy do the math. He can cite short case histories from the past two years and briefly explain how having X capability (present in the new equipment, absent in the existing equipment) would have saved Y minutes of downtime (which the green eye shade guy will calculate out in terms of revenue and cash flow). The green eye shade guy also needs to know whether each case history is a one-off that will never recur or if it’s representative of what to expect in the future. You can settle this question with a brief explanation. For example, “The responding technician did not have a [name of test equipment]. Consequently, he had to arrive at the same conclusion by other means to the tune of 24 minutes of downtime he would not have incurred if he’d had a [name of test equipment]. This problem occurred once on Line 2 and twice on Line 4.” Now the green eye shade guy can simply add up the downtime, monetize it, and create the cash flow analysis. And it’s really good for something like a power monitor. For example, “In this particular case the plant did not have a monitoring system capable of detecting short-term bursts of power, which we call transient spikes, and alerting us. Transients happen with no notice, and usually without being detected. The motor shop forensic report shows the main motor failed due to winding insulation failure caused by transients. With a power monitor detecting and reporting those transients, we would have been able to intervene before outright failure, on a scheduled basis. That would have reduced downtime by 57 minutes twice last year alone.” Making the business case for your smaller purchases means simply thinking about what you are trying to accomplish and then making sure you are spending the funds correctly to achieve that goal. But as you go up the food chain, you need to make the picture more clear. And when you appeal to corporate for approval, you need to provide reasonably accurate downtime savings numbers that can be converted by them to revenue loss prevention in specific dollar amounts.
Man staring at wall with hand-drawn question marks and money bags on it

Voice Your Opinion!

To join the conversation, and become an exclusive member of EC&M, create an account today!