Lubinpla

How to show technical service value when nothing went wrong

Summary

Showing technical service value at a trouble-free plant takes 3 steps: a stable reading history, the deviations caught and fixed, and avoided costs labeled as estimates. This works for a supplier running a chemical or lubricant program with agreed target ranges and dated readings, as long as every claim says whether it was measured or estimated.

  • The IPMVP states that savings cannot be directly measured because they represent the absence of consumption, so they are determined by comparing measurements before and after a project with adjustments for changed conditions (EVO, 2022).

  • The US DOE FEMP M&V Guidelines, Version 5.0, state that savings typically cannot be measured directly because they represent the absence of energy or water use and related expenditures, and ask that recurring O&M savings be based on actual spending reductions (US DOE FEMP, 2024).

  • Shewhart control charts set control limits 3 standard deviations from the center line, which NIST describes as an accepted standard in industry (NIST/SEMATECH, accessed 2026).

  • ISO 50015:2014, Edition 1, gives general principles for measurement and verification of energy performance and was last reviewed and confirmed in 2025 (ISO, 2025).

This guide covers suppliers and service engineers who look after a customer's fluids, water treatment, lubricants or coatings program at a site with no recent failures. It does not cover a performance contract with guaranteed savings, which needs a formal measurement and verification plan, or the timing of a contract renewal.

Why does a plant with no problems question the value of technical service?

Good technical service produces events that did not happen. An event that did not happen leaves no entry in the plant's incident log, downtime report or cost summary, so a plant with no problems starts to wonder what the service is worth. A buyer reviewing spend sees visit hours and invoices, and nothing next to them.

Energy work runs into the same difficulty, and there it has a formal answer. The International Performance Measurement and Verification Protocol (IPMVP) states that savings "cannot be directly measured because savings represent the absence of energy/water consumption or demand" (EVO, 2022). A maintenance guide from Tractian describes the problem from the plant technician's side: prevented failures do not appear on the incident log, the production report or the maintenance cost summary (Tractian, accessed 2026).

Describing the activity in more detail does not help, because a list of visits and tests shows effort, not effect. A plant manager can use three other things: evidence that the program kept the system inside its agreed limits, a record of each drift caught early, and an honest estimate of what those catches were worth, labeled as an estimate.

How do you show technical service value at a trouble-free plant, step by step?

The three steps use records you should already have. Before you start, collect the agreed target range for each measured parameter, the dated readings for the period, the visit and work logs, and the names of the customer contacts who saw each action.

  1. Show the stable reading history. For each system, plot the dated readings against the agreed target range and state the share of readings inside it, counted from the record, not estimated.

  2. List deviations caught and fixed. For every reading that left the range or drifted toward a limit, record the value, the limit, the action, the date and the re-check result.

  3. State avoided costs as estimates. When you put a money figure on a caught deviation, show the assumptions, label it an estimate, and keep it separate from the measured items in steps 1 and 2.

Present the steps in that order. The first two are measured facts the customer can check against their own records; the third is your judgment. Open with a large avoided-cost figure and the buyer will argue about the number and ignore the evidence underneath it. Keep the whole review short enough for one contact to read in a few minutes, and attach the reading history.

Which records turn stable readings into evidence of technical service value?

A stable reading counts as evidence when it meets four conditions. It is dated, it is tied to a named system and sampling point, it is compared with an agreed target range written down before the period, and it was taken with a stated method. A reading without a date, a range or a method is an assertion, not evidence.

Keep the target range separate from what the process does on its own. The NIST/SEMATECH e-Handbook draws that line: control limits show whether a process "is producing consistent output", while specification limits show whether the product "will function in the intended fashion" (NIST/SEMATECH, accessed 2026). An agreed target range plays the part of a specification limit. A program report usually claims that readings stayed inside it, so the report should say exactly that and not claim statistical control.

Be careful with the word stable. Shewhart's rule of thumb, quoted by NIST, holds that a state of statistical control should seldom be concluded before "a sequence of not less than twenty five samples of size four that are in control" (NIST/SEMATECH, accessed 2026). A program with one reading per week collects far fewer data points than that in a quarter, so describe it as readings within range, and give the count. For how plant readings reach your records without retyping, see collecting site readings from customers without retyping.

How do you report deviations caught before they became problems?

Write each caught deviation as one dated line with five parts: the reading, the limit or target it crossed or approached, the action taken, the date of the re-check, and the re-check result. A deviation counts as evidence of service value only when all five parts are written down.

Include drifts that never left the range. A run of readings on one side of the middle of the range, or a steady move toward one limit, is a signal worth acting on. On a control chart, NIST lists eight consecutive points on one side of the center line among the Western Electric rules for detecting non-random behavior (NIST/SEMATECH, accessed 2026). Acting on such a run before any reading fails is the clearest example of prevention a program can show, but it counts only if both the run and the action are recorded.

Keep claims about cause modest. Write what was observed and done, such as "concentration 3.9% against a 5-8% range, premix corrected, re-check 5.6% two days later" (illustrative), and do not add that a failure was prevented. Whether a failure would have followed is a judgment, and judgments belong in the estimate step with their assumptions.

If the customer's staff took the reading and you advised the action, say so. The record is stronger when the customer contact can confirm it from their side.

How should you state avoided costs from technical service as estimates?

An avoided-cost figure needs its working written next to it: the event you assume was avoided, its likelihood, the cost per event and the source of each number. Label the result as an estimate and keep it apart from the measured results. A figure without its assumptions cannot be checked, and buyers will usually discount it.

Energy measurement practice sets the standard here. The US DOE FEMP M&V Guidelines state that savings "cannot be measured directly" because they represent the absence of energy or water use and related expenditures, and are instead determined by comparison with a baseline and adjustments for changed conditions (US DOE FEMP, 2024). The baseline is the set of measurements taken before the work. The guidelines also cover operation and maintenance (O&M) costs: recurring O&M savings in a performance contract "must be based on actual spending reductions" (US DOE FEMP, 2024). Technical service at a trouble-free plant rarely has a baseline of that quality, which is why its avoided costs stay estimates.

Where you can, use the customer's own figures, such as their cost of a line stop or a fluid change, and cite who gave them. Give a range rather than one number. The Tractian guide recommends conservative estimates with the reasoning visible (Tractian, accessed 2026), and that advice holds for suppliers too: a modest figure with its working shown survives a buyer's review better than a large one without.

How do you check each technical service value claim?

Every claim in the review should end up in one of three places: shown as measured, shown as an estimate, or left out. The check table below decides which. Run every line of the review through it before it goes to the customer.

Evidence item

Pass

Fail and what to do

Reading history

Dated readings, named point, agreed range written before the period

Range set after the fact: show readings only, without a pass rate

Share of readings in range

Counted from the record, with the number of readings

Estimated or rounded up: count it or drop it

Caught deviation

Value, limit, action, date and re-check all recorded

Any part missing: list it as an observation, not evidence

Avoided cost

Labeled estimate, assumptions and their sources shown

Single number without assumptions: add them or remove the figure

Prevented failure

Not claimed as measured

Stated as fact: reword as an estimated risk with assumptions

Most reviews fail on the last row. "We prevented a pump failure" cannot be measured, for the same reason IPMVP gives for savings (EVO, 2022). "Inhibitor residual was restored within two days of a low reading" (illustrative) can be. Write the second kind and let the customer draw the first conclusion. A row that fails and cannot be fixed should come out of the review, not stay in under softer wording.

Ask a colleague who did not run the program to read the review against the table. The claims that seem obvious to the service engineer are the ones most often missing a date or a re-check.

What should you not claim when a plant has had no problems?

Do not claim that technical service prevented a specific failure, that it produced a measured saving, or that the plant would have had problems without it. The records of a quiet period cannot show any of these, and a buyer who questions one will doubt the rest.

Avoid three habits in particular. First, do not report a percentage improvement without a baseline measured before the program and adjusted for changed conditions, which is how both IPMVP and the FEMP guidelines determine savings (EVO, 2022; US DOE FEMP, 2024). Second, do not take failure rates or industry cost averages from unrelated sites and present them as this plant's avoided cost. Third, do not count your visits or tests as value: they are inputs.

What you can claim is narrower and stronger: readings stayed inside the agreed range a stated number of times, specific drifts were caught and corrected on stated dates, and an estimate with stated assumptions puts a value on those catches. In Lubinpla, a supplier can share work logs and a project's measured-value history with the customer contact through Field Care, so the contact checks the records directly; the product provides no dashboard or KPI tracking. Letting the customer see the same record you report from is the plainest way to show the claims are not inflated.

Frequently asked questions

How often should you report technical service value to a plant with no problems?

Report on a fixed cycle the customer agrees to, such as quarterly or at each program review, not only when a contract is up. A short regular report builds up the record of readings and caught deviations, and that record is the evidence a quiet plant needs.

Can you count a customer's own staff readings as evidence of technical service value?

Yes, if each reading is dated, taken at the agreed point with the agreed method, and kept in the shared record. Plant managers often find readings taken by their own staff more convincing, as long as the report says who took them.

Should the technical service value review include the cost of the service itself?

The review can show what the customer paid next to what the program delivered, but keep the comparison honest: measured results and labeled estimates on one side, the service cost on the other, and no single return figure that mixes the two.

Related posts