-
Who This Checklist Is For
-
Step 1: Map Your Measurement Requirements — Not Just Specs
-
Step 2: Evaluate the Software Ecosystem (Often Overlooked)
-
Step 3: Calculate Total Cost of Ownership (TCO) — Not Just Sticker Price
-
Step 4: Account for Application-Specific Needs (Speed Sensors, Centrifuges, etc.)
-
Step 5: Final Check — Source, Delivery, and Hidden Fees
-
What to Avoid — Common Mistakes I Still See
Who This Checklist Is For
If you're searching "which Fluke multimeter should I buy" or evaluating Keithley multimeters for your lab or production line — and you're the person signing off on the PO — this is for you. I manage procurement for a mid-sized electronics test house, and over the past 7 years I've tracked $240k+ in instrument spending across 18 vendors. This checklist is what I wish I'd had from day one.
Here's the short version: 5 steps, 20 minutes to run through, and it'll save you from at least one hidden cost that eats 15% of your budget. Let's go.
Step 1: Map Your Measurement Requirements — Not Just Specs
First mistake I made: assuming higher resolution always means better. I ordered a Keithley 2000 multimeter (6½ digits) for a job that only needed 5½ digits. Paid for capability we never used. A year later, we needed low-current measurement for semiconductor testing — the 2000 didn't cut it, and we had to buy a Keithley 2400 SMU on top.
So before anything else, write down:
- Required resolution (6.5-digit for precision, 5.5-digit for most production)
- Measurement type (DCV, ACV, resistance, current, frequency, capacitance)
- Special needs (low-level current, high voltage, high speed)
- Connectivity (GPIB, USB, LAN, or all? For data logging, this matters)
I now use a one-page requirement sheet that includes a row for "future expansion." The Keithley DMM6500 has been our workhorse because its 6½-digit covers both production and R&D. But we almost bought a Fluke 8846A — great meter, but fewer connectivity options for our automated test rack.
Pro tip: If you process thousands of measurements per second, a bench DMM might not be the right tool — consider a data acquisition system instead.
Step 2: Evaluate the Software Ecosystem (Often Overlooked)
When I first started, I compared only hardware specs. Big mistake. The software cost me more than the meter in lost time.
For Keithley multimeters like the 2000 and 2010, the Keithley 2000 multimeter software (often called KickStart or Test Script Builder) lets you automate sequences without writing code from scratch. That's a real efficiency gain — our team reduced test script time from 8 hours to 1.5 hours per project after we standardized on it.
Compare that to Fluke's software suite (FlukeView, MET/CAL). Fluke's tools are solid, but their licensing can add $300–$800 per meter. And if you need custom automation, you'll likely end up writing LabVIEW or Python drivers anyway. Keithley's free scripting environment lowers that barrier.
Checklist point:
- Does the included software support your test workflow? Or is it just a basic viewer?
- Are remote control drivers available for your environment (LabVIEW, Python, C#)?
- Is there a demo or trial? (Keithley offers a 30-day KickStart trial — take it.)
Honest caveat: Fluke's mobile app for field work is better. But for benchtop and automation, Keithley's software edge is clear.
Step 3: Calculate Total Cost of Ownership (TCO) — Not Just Sticker Price
This is where my "initial misjudgment" cost me. I once chose a "bargain" alternative (not Fluke or Keithley — a lesser-known brand) because the base price was 40% lower. Here's what really happened:
- Calibration certificate not included: +$150
- No software license: +$250 for basic control
- Missing test leads (standard fluke/Keithley sets included): +$80
- Non-standard rack mount kit: +$120
- Warranty only 1 year vs. 3 years on comparable models: +$200 for extended
Total actual cost: $800 more than the Keithley 2010 I had been comparing. And the lower brand had worse drift specs.
Use this TCO template:
| Item | Cost |
| Base price | $X |
| Calibration (annual) | $Y |
| Accessories (leads, adapters, rack kit) | $Z |
| Software license (if extra) | $W |
| Warranty extension | $V |
| 3-year TCO | Sum |
Quick reference (prices as of Q1 2025, check current):
- Keithley 2000 (6.5-digit): ~$1,600 base, includes basic software and leads
- Fluke 8846A (6.5-digit): ~$2,100 base, but software license extra ~$400
- Fluke 87V (handheld): ~$500, no software needed — different class entirely
Step 4: Account for Application-Specific Needs (Speed Sensors, Centrifuges, etc.)
You might not need a multimeter for everything. But when you do, the wrong choice can force you to buy an additional device.
Example: We had to measure an electronic speed sensor output from a centrifuge model 5418. The sensor output was a pulse train at 0–10 kHz. A standard DMM couldn't capture frequency accurately — we needed a DMM with frequency measurement capability, or a separate counter. The Keithley DMM6500 handles frequency up to 1 MHz, so it worked. If we'd bought a Fluke 87V (handheld), it would have required an accessory counter.
Similarly, if your application involves measuring very low voltages (like thermocouple signals from a centrifuge chamber), you need microvolt resolution. Not all multimeters offer that.
So ask yourself: What specific measurement is my application requiring today — and what might it require next year?
Step 5: Final Check — Source, Delivery, and Hidden Fees
I learned this the hard way: a vendor quoted a great price but added rush fees because we needed the meter in 3 weeks (standard was 4). That 25% rush premium ate our savings. And one distributor charged a "small order handling fee" of $75 on a $1,200 order — ridiculous.
Before signing:
- Get a written quote with ALL line items (setup, calibration, shipping, tax)
- Check lead time — if it's non-stock, can you wait?
- Verify warranty terms (Keithley standard is 3 years on most products; Fluke is usually 3 years too)
- Ask about calibration NIST-traceable certificate: included or extra?
What to Avoid — Common Mistakes I Still See
Here are three pitfalls I've documented in our procurement system:
- Over-spec'ing resolution. A 6.5-digit meter costs 2x a 5.5-digit. If your signal noise is 100 µV, a 1 µV resolution is wasted. Be realistic.
- Ignoring software upgrade costs. Free basic software is fine — until you need logging, analysis, or automation. Budget for the full suite.
- Assuming brand X is always better. Fluke is great for field work. Keithley dominates low-level measurement and automation. They're different tools.
And if someone tells you "this is the best multimeter for everything" — run. Period.