Step 1 — export the program as DMIS
The starting point is the program that already measures the part on the CMM. Export it as DMIS from the CMM software and take the file as it is: programs written in the PC-DMIS, CAMIO and PAS dialects and generic DMIS 5.x are read, UTF-16 files and inch programs included. Nothing needs to be rewritten for the scanner. You also need the CAD model the scan will be inspected against (STEP, IGES or STL) and the scan itself.
Step 2 — import and read the import notes
On import the file's encoding and dialect are detected, the feature definitions, datum definitions, alignments, constructions, tolerances and output statements become program steps, and the import ends with a short set of notes: the dialect, the state of the frame and any warnings. A construct that needs attention is named there with its reason, so you know before the run which steps to look at. A file that yields no steps is refused by name; it is not opened as an empty program.
The notes are stored with the program and shown again when it is reopened. The same import route serves the program editor, the batch window and the AI command, so a program behaves the same wherever it is loaded.
Step 3 — check the frame
A CMM program is written in its own coordinate frame, which may be rotated or shifted relative to the CAD model. Ai-Inspect registers the program's frame against the CAD by matching the program's features with the model, and accepts the registration when it is clear. When it is not, the program is marked frame-unverified: the editor asks for your confirmation before it plays, and an unattended batch run refuses to start. This is the check that prevents results which look plausible and belong to the wrong frame.
- Frame registered: the program is ready to run
- Frame unverified: confirm it in the editor before the first run
- Batch and the AI command do not run an unverified program
Step 4 — run on the scan
Load the scan and align it to the CAD; a pre-flight guard checks the alignment before the program starts. The program then runs step by step. Where the CMM program states a feature by its nominal, the measurement points are placed on the scan from that nominal, and each point passes a coverage gate — a point with no scan surface near it does not contribute. Datum alignments are rebuilt from the features measured on this scan, and constructions are rebuilt in the order the program depends on.
A feature without coverage, a nominal that contradicts the geometry found, or a construction whose inputs failed ends as a row marked N/A with its reason. A value is never carried over from the program's nominals.
Step 5 — close the open items
The run report lists every balloon that was not measured and why, and each one is marked in red on the model. From a row of the report you can jump to its step in the program editor, pick the feature again in 3D, disable a step that does not apply to a scan, and run only the steps that failed. The Measurement Copilot offers the same items as a guided list — datums first, then gaps, then a review of the FAIL rows.
A characteristic whose tolerance is tighter than the scan can resolve is refused and stays a job for the CMM. The refusals of the first run are a useful list in themselves: they show which characteristics of this part still need the touch probe.
Step 6 — export, and repeat on the series
Results are exported as PDF, Excel and CSV in balloon order, under the labels the CMM program used, and as a PAS CMM CSV for shops that keep their records in PAS. The corrected program is saved; on the next part it runs as it is, and batch mode runs it over a folder of scans with one report per part.