The most common question we hear from labs looking to modernize is: “Can I just convert my existing Fluke MET/CAL procedures into Metrology.NET?”

The short answer is NO—but the reason why is the best news your lab has heard in 40 years.

There is no “direct 1:1 migration” because you cannot migrate a legacy scripted procedure into a modern, data-point-first architecture. MET/CAL is a line-by-line command language rooted in the 1980s. Metrology.NET is a model-driven ecosystem built for the 21st century.

Instead of a simple “conversion,” we offer a transformation.

The Cost Advantage: Why “Starting Over” is Smarter

When you hear you can’t “convert” code, it sounds expensive. In reality, it is the opposite. Because Metrology.NET is based on a Model-Driven Software mentality, the engineering overhead is drastically lower.

The math is simple: The cost of developing a new automation package in Metrology.NET is typically less than a tenth the cost of developing the same functionality in MET/CAL.

In many cases, it takes more time for a technician to manually update a MET/CAL procedure to support a different reference standard than it does to create a brand-new Metrology.NET test package that will run with any standard your lab owns. You aren’t just writing a procedure; you are building a capability that will never need to be rewritten.

The Power of Model-Driven Software Engineering

In MET/CAL, the hardware is hard-coded into the script. In Metrology.NET, we define the measurement models without being hardware specific.

MET/CAL Approach: “5700 10V” tells the script to output 10 Volts from the Fluke 5700A.
Metrology.NET Approach: Source.Voltage.DC “Volts= 10” and that works on the Fluke 5700A and every other lab standard that can output 10 Volts DC.

By building the “Measurement Model” first, you write significantly less code. You focus on the metrology, and the drivers handle the instrument commands.

The CLS Secret Sauce: Future-Proofing MET/CAL

As the industry’s leading MET/CAL experts, we continue to write and support MET/CAL procedures; however, we also offer a unique solution that demonstrates the power of Model Driven Software Engineering.

When Cal Lab Solutions creates a new MET/CAL procedure, we don’t start in the MET/CAL editor. We first build a Metrology.NET Test Package. Once that model is perfected, we use our proprietary custom tools to automatically build the MET/CAL procedure from the Metrology.NET Test Package.

What does this mean for you?

Universal Compatibility: Your automation requirements are stored in a modern, platform-agnostic model.
Instant Conversion: If you need that procedure in MET/CAL, it’s a click away. If you want to run it natively in Metrology.NET, it’s already done.
Future-Proof Assets: You are no longer locked into a 40-year-old scripting language. Your investment is protected in a universal test package that can be converted to whatever the future of metrology requires.

Stop Scripting and Start Modeling

The era of fighting with brittle legacy scripts is over. By migrating to Metrology.NET, you are choosing a path that is faster, cheaper to develop, and inherently more flexible.

You aren’t just moving your procedures—you are moving your lab into a future where the software works for you, not the other way around.

Metrology.NET: Build it once. Use it everywhere. Use it forever.

Questions? Email sales@callabsolutions.com or call +1 (303) 317-6670 (MST-Denver, Colorado).