Run a coordinate measuring machine and you’re almost certainly programming it in one of two environments: Hexagon’s PC-DMIS or Zeiss’s Calypso. Both produce inspection routines that drive a CMM, and that’s roughly where the similarity ends. They think about measurement differently, they fit different hardware, and a programmer fluent in one is not automatically fluent in the other. Here’s an honest, practitioner-level comparison of PC-DMIS vs Calypso — not a spec sheet, but how they actually differ on the floor.

The core difference: command-driven vs feature-based

The single most useful thing to understand is this: PC-DMIS is command-driven; Calypso is feature-based.

In PC-DMIS you build a routine as an explicit sequence — move here, take this hit, construct this feature, evaluate this dimension. It’s linear and gives you enormous, granular control, which is why veteran programmers in aerospace and complex contract inspection often prefer it: there’s almost nothing you can’t make it do. The trade-off is that it expects you to know what you’re doing at every step, and the learning curve is real.

Calypso flips the model. It’s object-oriented and feature-based — you define the characteristics you want to measure (this bore, that plane, this width), and Calypso plans the measurement strategy, travel paths, and collision-free motion around them, using its “safety plane” approach to auto-route between features. It maps cleanly onto how a print is dimensioned, which makes it faster to become productive in for prismatic, GD&T-heavy parts. The trade-off is that the abstraction can feel limiting when a part fights the feature model.

Hardware: this often decides it for you

In practice the software follows the machine. Calypso is Zeiss’s native environment and is the obvious choice on Zeiss CMMs and VAST scanning heads, where its high-speed scanning workflow (VAST Navigator) is genuinely excellent. PC-DMIS is hardware-agnostic by design and runs an enormous installed base — 70,000-plus seats — across Hexagon machines (Brown & Sharpe, DEA, Sheffield) and many third-party and retrofitted CMMs. Bought a Zeiss bridge? You’re likely in Calypso. Mixed floor or older retrofits? Likely PC-DMIS.

Scanning and freeform

Both scan, but the strengths differ. Calypso paired with VAST sensors is a benchmark for high-speed continuous scanning and freeform surface analysis, intelligently setting scan speed for the required accuracy. PC-DMIS scans strongly too, especially with CAD++ driving laser and analog sensors, and has deep sheet-metal routines prized in automotive. For pure freeform/airfoil scanning on Zeiss hardware, Calypso tends to lead; for mixed-sensor flexibility across many machine brands, PC-DMIS is hard to beat.

Learning curve and programmer availability

Calypso is generally faster to become productive in for standard prismatic parts because the feature-based approach hides path-planning detail. PC-DMIS has a steeper curve but rewards depth. The hiring reality matters here: because the two aren’t interchangeable, a Calypso shop can’t simply drop in a PC-DMIS programmer when their inspector is out, and vice versa. That single-software dependency is exactly where inspection backlogs come from — and why on-demand programming across both languages is so useful.

Side-by-side

Factor	PC-DMIS (Hexagon)	Calypso (Zeiss)
Programming model	Command / sequence driven	Feature / object driven
Best fit	Complex, non-standard, aerospace	Prismatic, GD&T-heavy, scanning
Learning curve	Steeper, deep control	Faster for standard parts
Native hardware	Hexagon + agnostic / retrofits	Zeiss CMMs & VAST heads
Scanning	Strong, multi-sensor, sheet metal	Excellent (VAST Navigator)
Install base	Largest in the world (70k+)	Very large, Zeiss ecosystem

So which should you use?

For most shops the honest answer is: use the one that matches your machine and your programmer’s fluency. Don’t switch software to chase a feature — the retraining cost almost never pays back. Switch only if you’re changing hardware anyway. And if your constraint isn’t the software but the person — one programmer, one point of failure — the fix isn’t a new package, it’s backup capacity in the language you already run.

Frequently asked questions

Can a PC-DMIS program be converted to Calypso?

Not cleanly — there’s no reliable direct translation because the underlying models differ. A part is generally re-programmed in the target software, which is also a chance to optimize it.

Which is better for GD&T?

Both handle GD&T well to ASME Y14.5 and ISO. Calypso’s feature flow maps naturally onto a dimensioned print; PC-DMIS gives more explicit control over how each callout is evaluated. The better one is the one your team knows.

We run both — can you cover both?

Yes. We program across PC-DMIS, Calypso, and other packages, so you’re covered for whichever machine is short a programmer.