Request Calibration Where to Buy Region: Global ▾
Application Note

Mitutoyo, Multimeters, and Thermal Cameras: A Scenario Guide for Admin Buyers

Posted on 2026-11-03 by Marcus Feld

I'm the office administrator at a 180-person manufacturing company. I run all the non-production purchasing — lab supplies, PPE, packaging consumables, and the precision measurement tools our QC and maintenance teams rely on. Roughly $340K a year across nine vendors, reporting to both operations and finance.

Most procurement advice I read online assumes every order should be handled the same way. Send three RFQs, pick the cheapest compliant bid, done. That approach works for toner cartridges. It does not work for a Mitutoyo tube micrometer or a thermal camera.

Here's the thing: equipment procurement isn't one problem. It's three different problems wearing the same trench coat. The right process depends on who's asking, how specific they are, and what's at stake if the wrong thing arrives.

This is how I split it now.

The three scenarios I actually work with

After taking over equipment purchasing in 2020, I kept making the same mistake. I treated every request as if somebody had already done the hard work of choosing. Sometimes they have. Sometimes they haven't. The difference matters more than the price tag.

  • Scenario A: The engineer names an exact model and gives you a part number. Your job is execution, not selection.
  • Scenario B: The engineer gives you a need, not a product. "We need a resistance tester." Now you're doing the selection, whether you want to or not.
  • Scenario C: Two brands both look defensible on paper, and you have to choose between them. Think Fluke vs FLIR thermal cameras.

Each one calls for a different process. Mixing them up is where things go sideways.

Scenario A: The engineer already picked the model

If a QC engineer hands you a spec sheet for a Mitutoyo tube micrometer, do not go find a better deal. Do not substitute the SKU. Do not offer the engineer a cheaper alternative because you saw one at 30% off from a marketplace seller. The engineer chose that model for a reason — range, resolution, anvil tip shape, the way it fits into their calibration chain — and you don't have the context to second-guess it.

Your job is execution: source it through an authorized distributor, confirm it comes with a current calibration certificate traceable to ISO/IEC 17025, get a proper invoice, and make sure the lead time fits the project.

That sounds easy. It isn't.

The accessories trap

Mitutoyo dial indicator accessories are a good example of why execution-mode orders still need attention. The mounting stems, back plates, anvils, and contact points are visually similar across product lines. But they aren't interchangeable across every indicator body. I learned this the hard way.

In 2023, I ordered a batch of indicator accessories through a reseller because the price was meaningfully lower than the authorized distributor's. The parts arrived on time. They looked right. Two of them wouldn't seat properly on our existing dial indicators. When I called the manufacturer's distributor line to confirm the part number, they explained the reseller had shipped a cross-compatible SKU from a different indicator series — same dimensions, different stem length. Close enough for casual use. Not close enough for a calibration lab.

That's when I understood the difference between "looks like the same part" and "is the part."

The cost wasn't just the returned parts. It was the two weeks of project delay while we waited on a second order, and the hour I spent explaining to my finance director why a purchase order was being reversed. Since then I don't buy Mitutoyo accessories from anyone who isn't on the authorized distributor list. If the price gap is large, I assume something is off — not that I found a bargain.

Scenario B: The engineer gives you a need, not a model

This is harder. Last October our maintenance lead sent me a message that said, in full: "We need a resistance tester. Also a multimeter, the good kind."

That's not a request. That's a wish with a deadline attached. And it's tempting to just order whatever shows up first on a distributor's category page. It's tempting to think a multimeter is a multimeter. But the details inside that request change the price, the capability, and whether the thing works for the intended job at all.

"The good kind" of multimeter

When people in industrial settings say "the good kind," they usually mean the Fluke 87 multimeter family. The 87V has become a de facto reference point for field technicians because of its CAT III 1000 V / CAT IV 600 V safety rating, its true-RMS measurement, and the simple fact that almost every electrician has used one. That's a real signal. But it's also not a complete specification.

Before I place the order I want to know: what are they measuring, where, and against what standard? A bench multimeter and a field multimeter are different tools. A meter used inside a motor control panel and a meter used on low-voltage bench electronics have wildly different safety requirements. The 87 multimeter is usually the right answer. It's right for a specific set of conditions, not universally.

Resistance tester — insulation or micro-ohm?

"Resistance tester" is the kind of phrase that could mean at least three very different instruments depending on who's saying it:

  • An insulation resistance tester (megohmmeter), used for verifying motor and cable insulation.
  • A micro-ohmmeter or milliohm meter, used for contact resistance on switchgear and joints.
  • A general-purpose four-wire resistance meter for lab work.

They look nothing alike. They cost different amounts. And if you order the wrong one, it doesn't degrade gracefully — it's just wrong for the job. So when the request is vague, my default is a two-question email: What are you measuring, and what range or accuracy do you need? That usually resolves the category, and it's cheaper than ordering twice.

Scenario C: Both brands are defensible — Fluke vs FLIR thermal cameras

This is the scenario where I actually add value, because the engineer usually has a technical preference and I'm the one who has to weigh it against everything else. Thermal cameras are a fair example. Fluke and FLIR both make industrial thermal imagers. Both have calibration and support networks. Both are credible choices for a maintenance team doing electrical or mechanical inspection.

So how do you choose? Not on brand loyalty, and not on whatever's on sale.

Here's what I want on the comparison sheet before I recommend anything:

  • Detector resolution in pixels. This determines how much detail the camera can actually resolve at a working distance. That number matters more than most of the marketing copy surrounding it.
  • Thermal sensitivity (NETD) in millikelvin. Lower is better, and it changes what the camera can see in low-contrast temperature conditions.
  • Software ecosystem — how images get off the camera and into a report. This is what engineers complain about two years after purchase, not at the point of sale.
  • Calibration and service footprint — who services the unit, how long it takes, whether there's a loaner program.
  • Warranty terms and accessory compatibility with the existing tool fleet.

Where my process diverges from what you might read elsewhere: I put software and service footprint above raw detector specs when the specs are already close. A thermal camera that the team actually uses and can get serviced quickly beats one that's technically superior on paper and awkward to live with.

That's not the advice a spec-sheet decision-maker would give. It's the advice of someone who has watched a tool sit on a shelf because it was annoying to use.

The upside of buying the team-preferred camera is a tool that actually gets used. The risk is that the team-preferred camera costs more than the spec requires. I keep asking myself: is the premium worth potentially reopening this request in six months because the cheaper unit doesn't get used? Usually, yes. But I want the engineer's sign-off on the comparison sheet before I commit, so the decision is documented and not just my judgment call.

How to tell which scenario you're in

It's not about the price of the order. It's about who did the technical selection.

If the requester gives you a brand and a model number, you're in Scenario A. Your job is authenticity, calibration, and delivery — not selection. Verify the distributor, confirm the certificate, and don't take the cheaper channel.

If the requester gives you a need without a model, you're in Scenario B. Stop. Send two questions before you buy anything. The cost of a two-question email is zero. The cost of ordering the wrong instrument is never zero.

If two brands both look defensible, you're in Scenario C. Build the comparison sheet, put software and service at the top, and get the technical owner to sign it. You don't have to be the expert. You just have to be the person who made sure the expert's decision was recorded.

What was best practice for a procurement team in 2020 is different from what it is in 2025. Five years ago, most of these tools were bought through a distributor relationship — you called, they quoted, you got a favor. Now the same tools are ordered through online distributor portals, tracked against calibration schedules, and sometimes selected through comparison sheets that live in a shared spreadsheet instead of a sales conversation. The fundamentals — traceability, authorized channels, calibration — haven't changed. The execution has.

The mistake I see most often isn't a bad purchase decision. It's using the same process for all three scenarios because it's easier than asking "which situation am I actually in?"

I still get it wrong. Last year I pushed through a resistance tester order on Scenario A logic — treated the spec as fixed when it wasn't — and it cost the project three extra weeks. The process is useful, not foolproof. Worth building anyway.

Leave a technical note