Use Utilization Data to Justify CI Projects


To reduce costs, our customers use Amper Utilization data to first, justify projects before getting started, and then quantify efforts after improvements have been made.


Here's a simple process:

  1. First you'll want to calculate your cost of production. What are all of your costs per hour, divided by the number of machines?
  2. To get the most accurate number, you'll want to consider costs for direct and indirect labor. That means beyond just an employee's salary, but additionally: employment taxes, health benefits, and PTO. You'll also want to take into account things like: consumable raw materials, building costs, or monthly payments on rented machinery.

    If you don't want to do the math, a conservative estimate is to assume your cost of production is $40/hour. So, every hour a machine is making parts, or not making parts, will cost the business $40 at each machine. If you're running, you're ideally selling that product for a profit, thereby offsetting those costs. If you're down, you're just losing $40/hour/machine.

    👉 You can also use downtime labeling to justify improvements before making them. For more information on this, please refer to

  3. Then you'll use utilization data to determine where to improve (typically your highest running machines or bottleneck areas).
  4. Apply cost of production to the hours being lost in your target area & determine opportunity cost . Example: a machine that runs 24 hours a day for 5 days a week will be available about 6,240 hours in a year. If it's running at 50% utilization, the company will lose about $124,800 at a $40/hour cost of production).
  5. Now identify improvements to be made and execute!
  6. Lastly, quantify your efforts and determine how much you've saved - celebrate! With Amper, any project can be quantified. After you make an improvement, use your cost of production to show how much you actually saved. Each sustained minute of increased uptime as a result of an improvement project will equal savings.

-Look at the average hours of uptime before the project & multiply that by your cost of production (discussed in step 3 above).

-Then do the same, after the project. Ensure there is a large enough sample size before finalizing your savings. The rule of thumb is to measure and compare the 30 days before and after the time period of sustained growth.

Example: do not include implementation time in measurements. Only measure 30 days before implementation and 30 days after implementation is stable.