When inspection means point clouds — hundreds of thousands of scanned points compared against a CAD model rather than a handful of discrete touches — PolyWorks is the software most serious metrology rooms reach for. It’s device-agnostic, deeply capable, and not something most shops have real bench strength in. So when the one person who knows PolyWorks is unavailable, complex scanning and freeform jobs stall. On-demand PolyWorks programming services keep them moving.

This is a practitioner’s view of where PolyWorks earns its place, what programming it actually involves, and how to get expert capability per project instead of hunting for a rare full-time hire.

Why PolyWorks is the point-cloud specialist

Discrete-touch CMM software is built around measuring individual features — this bore, that plane. PolyWorks|Inspector is built around dense data: it ingests scans from laser trackers, portable arms, structured-light and laser scanners, and CMMs with scanning heads, then compares that data to a CAD model and evaluates dimensions, GD&T, and surface deviation from it. That orientation is exactly why it dominates anywhere the geometry is organic or freeform — aerospace skins, castings, medical and automotive body parts — and why programming it well is a distinct skill from prismatic CMM work.

What goes into a production-ready PolyWorks routine

1. Data alignment — the foundation

Everything in PolyWorks depends on how the scan data is aligned to the CAD coordinate system. Best-fit, datum-based (RPS), feature-based, and N-point alignments each suit different parts, and choosing wrong throws every downstream measurement off. For parts with no good datum features, a proper best-fit-then-constrain strategy is the difference between a defensible result and a misleading one. This is where experience shows immediately.

2. Color-map deviation analysis

PolyWorks’ signature output is the CAD-to-part color map — a full-surface comparison showing where the part deviates from nominal, in color, across the whole geometry. It’s the single most powerful way to communicate form error to a customer or a process engineer, and building it so the scale, tolerance bands, and annotated points actually mean something is part of the craft, not an automatic button-press.

3. GD&T on freeform and prismatic features alike

PolyWorks evaluates full GD&T to ASME Y14.5 and ISO — position, profile of a surface, flatness, runout — extracting features from the scan data and applying the correct datum reference frame. Profile of a surface on a freeform part, in particular, is where point-cloud software earns its keep and where interpretation matters most.

4. Multi-device and multi-setup data fusion

One of PolyWorks’ real strengths is combining data from multiple devices and setups into a single inspection — a CMM for tight prismatic features, a laser scanner for surfaces, a tracker for large-scale points — all aligned into one coordinate system. Programming that fusion correctly, so the right device measures the right feature and the data stitches without introducing error, is advanced work.

5. Repeatable measurement objects and macros

For production, a one-off inspection isn’t enough — you need a reusable, repeatable routine. PolyWorks’ measurement objects and macro scripting let a programmer build inspections that run consistently part after part, with reporting that populates automatically. Setting this up properly is what turns a clever one-time analysis into a production tool.

Work from your data or your machine — securely

PolyWorks programming fits remote work naturally because so much of it happens on exported data. We can build the inspection from scan data and CAD you provide, or connect to your PolyWorks seat over a secure remote session. Either way your files stay on your network, you keep control of the session, and for controlled work on-site is available. The finished project — alignments, measurements, color maps, report templates — is delivered ready to run.

When to bring in PolyWorks support

• A freeform or scan-heavy part exceeds your team’s PolyWorks depth.
• You’ve added a scanner, arm, or tracker but lack the programming to use it fully.
• You need a clean color-map deviation report for a customer review.
• A job requires fusing data from multiple devices into one inspection.
• Your PolyWorks specialist is out and deadlines don’t care.

Frequently asked questions

Do you work from our scan data or our machine?

Both options work. We can build the inspection from scan data and CAD you send, or connect to your PolyWorks seat. We’ll recommend whichever fits your security needs and timeline.

Which devices does PolyWorks programming cover?

CMMs with scanning heads, laser scanners, structured-light systems, portable arms, and laser trackers — PolyWorks is device-agnostic, and we program across them, including multi-device inspections.

Can you produce color-map reports?

Yes — CAD-to-part color-map deviation analysis is a PolyWorks signature and a common deliverable, built with meaningful tolerance bands and annotations for customer review.