Dwyer process instrumentation application note

Application note

Dwyer application note: The 7-Step Instrument Purchase Checklist I Use Before Approving Any Budget

2026-09-08 by Marcus Feld

I sign off on instrument purchases for a mid-sized industrial company. I am not the engineer who selects every sensor, and I do not pretend to be the chemist who specifies a liquid chromatography method. I am the person who sees the request when it arrives and the invoice when it arrives three months later. This checklist comes from actual purchase orders, not from an equipment brochure.

If you approve requests for measurement instruments — even something as simple as a Dwyer sensor or as specific as a Dwyer DP transmitter — you will inherit a long list of hidden decisions. The price of the hardware is only the beginning.

Why I needed a checklist

In an operations environment, no request arrives with all the time we want. The urgent ones are the most dangerous because they skip specifications. I used to agree to rush requests because I respected the person asking. Then I built a cost tracking system, and it showed me something uncomfortable: our worst overruns were not usually the expensive instruments. They were the cheaper sensors and transmitters ordered in a hurry, with the wrong process connection, missing calibration, or overnight freight that cost more than the part itself.

This checklist is for buyers, maintenance planners, operations managers, and anyone else who has to approve an instrument budget without being a design engineer. It is not a substitute for reading a datasheet. It is a budget gate that should happen before the purchase order is sent.

The 7-step checklist

1. Identify the measured condition, not just the product name

A request that says “we need a Dwyer DP transmitter” is not a complete request. A DP transmitter is a category. I need to know whether it will measure air or liquid, what pressure range is expected, what output signal the control system needs, and what process connection is on the line. “A Dwyer sensor” is not complete either unless we know the property being measured and the environment it will live in.

I have approved a transmitter by product family and paid for an extra adapter later because the process connection was not verified. That is the kind of mistake that looks small in the review meeting and looks stupid on the final cost report.

Checkpoint: the request should name the fluid, pressure range, process connection, output signal, and environment classification before I compare quotes.

2. Match accuracy to the decision being made

The cost of a sensor climbs as the accuracy spec climbs. High accuracy is valuable when a process needs precise control, quality reporting, or compliance documentation. But if the request is just to watch a filter bag and trigger an alarm, a Magnehelic gauge or a pressure switch may be enough. Buying maximum accuracy because it sounds safer is an easy way to inflate both the purchase price and the calibration cost.

I now ask the requester to write down an acceptable tolerance before I ask suppliers for pricing. If the process can tolerate 2% full scale, I do not want to pay for 0.25% full scale unless the supplier can show why the extra cost protects us somewhere else.

Checkpoint: the acceptable error is written down before the accuracy conversation starts.

3. Keep the request in the right product family

Product family errors can be worse than wrong model numbers. A portable laser distance meter is a fine tool when someone needs to measure a building dimension and walk away. It is not the same as a 4–20 mA level transmitter mounted on a tank. Both measure distance, but only one gives a continuous signal to a controller.

Another example is liquid chromatography. A lab request may say “we need liquid chromatography,” but that phrase covers a pump, a detector, a column, an autosampler, solvent handling, software, and operator training. If I treat that request as a single product, I will probably miss half of the actual scope. The same thing happens when someone asks for a DP transmitter but only needs a local gauge with no signal output.

Checkpoint: the requester can explain what outcome they need, not just which product category they want.

4. Challenge magic expectations early

The question most people ask is “can thermal cameras see through walls?” The honest answer is no. A thermal imager reads surface temperature. It does not send radar through drywall, brick, or concrete. It can sometimes show a temperature pattern that suggests something warm or cold is inside a wall, like a hot water pipe, but that is indirect and depends on the conditions.

If an engineer writes “can thermal cameras see through walls?” and then adds “FLIR” to the product line, I treat that as a red flag. The requester has a problem to solve, not a product spec. When the supplier is transparent, they will explain the limitation before taking the order. A camera that sees through walls would be impressive, but that is not how infrared imaging works.

Checkpoint: any thermal imaging request includes a demonstration or test plan on the actual material before the final purchase commitment.

5. Ask every supplier what the price does not include

Every serious quotation should show product price, calibration if required, process fittings, mounting hardware, software setup, freight, and lead time. I have learned to ask “What’s not included?” before asking “How much is the base price?”

A supplier who shows every fee at the beginning is more credible than one who promises the lowest base price and then adds $400 in extras at invoice time. This is not about choosing the most expensive option. It is about making sure every vendor is quoting the same scope.

Checkpoint: the purchase order total matches the quoted delivered cost, not the promotional price on a datasheet.

6. Budget for two years of operation, not just the handover

An instrument purchase does not end when the box is opened. Calibration requirements, replacement parts, power supplies, operator training, and maintenance time are all part of the real cost. A liquid chromatography system only looks affordable if you ignore columns, solvents, reference standards, and waste handling. Even a simple DP transmitter or a humidity sensor may need annual calibration to keep the rated accuracy.

When I review an instrument budget now, I add an estimated two-year operating cost line. That single change reduced our average measurement purchase variance from roughly 15% over budget to about 5% over budget. I am not sure whether the savings came from better questions or from suppliers realizing I was tracking their extras, but the result is real.

Checkpoint: the cost review covers installation, calibration, consumables, and expected maintenance for at least two years.

7. Write a one-sentence acceptance test before the purchase order

The person requesting the equipment should be able to complete this sentence: this purchase is successful when ________.

For example, “The replacement DP transmitter is successful when its output matches the existing test gauge within the stated tolerance for 48 hours.” Or, “The thermal camera purchase is successful when the maintenance team can identify the same panel fault we recorded in the trial.” If nobody can write the acceptance test, the requirement is still too vague. I send it back.

Checkpoint: the acceptance test is written before the PO is approved, not after the equipment arrives.

Mistakes to check before signing

  • Ordering from memory instead of checking the actual tag. I have ordered a spare sensor by part number and then found out the instrument tag had been changed during the last shutdown. The old part number was still in the system, but the installed device was different.

  • Accepting expedited shipping on everything. Urgency fees can quickly eat the savings from a well-negotiated quote. I now ask whether the deadline is a real plant event or just the original target date.

  • Allowing a supplier to say “no problem” without writing it down. If a distributor confirms that a sensor is compatible with an existing control loop, I want that sentence in the quote email. Verbal promises do not help when the invoice arrives.

This list is not a technology guide. It is a spending discipline. From the outside, instrument buying can look like a technical job. The reality is closer to a translation job: translating a process need into a scope, then translating a scope into a total cost. Keep asking the unglamorous questions, especially when the answer seems obvious.

This was accurate as of my Q1 2025 procurement review. Instrument prices, calibration policies, and product lines change quickly, so confirm current quotes and datasheets before you commit.

Marcus Feld

Marcus Feld

Marcus Feld is an electrical test and measurement analyst specializing in multimeters, oscilloscopes, clamp meters, insulation testers, spectrum analyzers, and data loggers. He applies IEC 61010-2-030 and IEC 61010-031 concepts while examining measurement category, bandwidth, true-RMS response, input loading, and stated uncertainty. His work helps maintenance engineers and test teams choose safe instruments with performance suited to the signals and environments they actually measure.