STEP AP242 can carry much more than a part’s visible shape. Depending on the authoring system, export options, protocol edition, and receiving application, an AP242 file may transmit precise geometry, assembly structure, names, colors, saved views, and product manufacturing information (PMI) such as dimensions, tolerances, datums, and surface requirements. That capability makes AP242 valuable for a model-based workflow—but it does not make every exported annotation complete, semantic, or safe for automatic consumption.
A CNC production release therefore needs a preflight at both ends of the exchange. The design organization must verify what was exported. The supplier must verify what its CAD, CAM, and inspection software actually imported. The acceptance question is not “Can the file be opened?” It is whether the transferred model and PMI preserve the same manufacturing requirements that engineering approved.
This guide explains the checks to make before programming, quoting, or inspection. It does not override the applicable drawing standard, model-based definition policy, customer contract, or released source data.
Treat the procedure as a qualification of one defined translation path. A result obtained with one CAD release, export profile, or CMM importer should not be generalized to every version. Revalidate the path after a software upgrade, translator change, new PMI entity type, or material change in downstream automation.
What STEP AP242 Is Designed to Exchange
STEP is the common name for ISO 10303, a family of standards for computer-interpretable product data. AP242 is an application protocol developed for managed model-based 3D engineering. It builds on capabilities associated with earlier AP203 and AP214 exchange while addressing product structure, geometry, PMI, and lifecycle information used in modern digital product definition.
For CNC work, an AP242 exchange may contain:
- exact boundary-representation geometry for solids and surfaces;
- assemblies and component occurrences;
- part, body, feature, layer, and product names;
- colors and presentation attributes;
- coordinate systems and saved model views;
- graphical PMI that a human can see;
- semantic PMI that software can associate with geometry;
- validation properties such as mass, area, volume, or centroids;
- revision, approval, or other product data when the exporter supports it.
An implementation rarely supports every possible entity in the standard. The export and import translators decide which content is written, read, simplified, ignored, or converted. That is why the software name and “AP242” label are not enough to prove a successful release.
The STEP Tools AP242 demonstrations illustrate how geometry, PMI, and digital-thread information can be represented. The NIST STEP File Analyzer and Viewer provides an independent way to inspect file contents and generate reports, but its output should supplement—not replace—validation in the production applications.
Presentation PMI and Semantic PMI Are Not the Same
One of the most important preflight distinctions is between PMI that looks correct and PMI that is machine interpretable.
Presentation PMI is a visual representation of annotations. It can preserve the appearance and placement of dimensions, feature control frames, datum symbols, notes, and other callouts. A reviewer can read it much like annotations on a drawing. Presentation alone may not tell software which face, cylinder, axis, or feature the annotation controls.
Semantic PMI represents the meaning and associations of a requirement in structured data. It can identify the tolerance type, value, modifiers, datum references, and the geometric elements to which the requirement applies. A capable downstream application may use those associations for inspection planning, tolerance analysis, or automation.
An AP242 file can contain presentation PMI, semantic PMI, both, or neither. Some translators create visually convincing annotations while dropping or weakening semantic associations. Others import semantic data but display it differently from the authoring system. A successful screenshot comparison therefore does not prove semantic integrity.
A practical three-level classification
Classify the exported requirement at preflight:
- Visible only: the annotation can be read, but no semantic association has been verified.
- Semantic but not consumed automatically: software can inspect the structured relationship, but the production process still relies on controlled human review.
- Semantically consumed: validated downstream software uses the data for a defined automated or assisted task, with controls for unsupported entities and exceptions.
The release package should state which level is intended. Do not advertise an automated model-based process if the supplier actually reads graphical callouts and manually recreates them in CAM or CMM software.
Establish the Model Authority Before Export
AP242 does not decide which document controls. The design organization must establish authority in the release process. A model-based definition may make the 3D model the governing source for geometry and PMI. A hybrid release may make the model authoritative for nominal shape while a 2D drawing controls tolerances, notes, finishes, or acceptance. A traditional release may treat the STEP model as reference geometry only.
Write the precedence rule clearly. If the model and drawing conflict, the supplier should stop and request clarification rather than selecting the apparently tighter or newer value. If a lightweight PDF or viewable derivative accompanies the model, state whether it is controlled, reference-only, or a human-readable representation of the same release.
The source CAD file, AP242 export, drawing, inspection plan, and purchase order must carry the same part number and revision. A correct AP242 file paired with an obsolete PDF is still an unsafe release.
Preflight the Source CAD Model
Export quality begins with the authoring model. Before translation, check the source for conditions that can confuse PMI or topology association.
Model state and configuration
Confirm the active configuration, arrangement, suppression state, and design representation. Check that optional holes, patterns, simplified components, and family-table members match the released part. Remove construction geometry or reference bodies that are not intended for transfer, or identify them unambiguously.
For an assembly, confirm the component count, occurrence identity, transform, and intended assembly level. A suppressed component, alternate position, or flexible subassembly can change the delivered structure even when the screen view looks familiar.
Units and coordinate system
Confirm length units, angular units, mass units if validation properties are used, and the coordinate system expected by manufacturing. Identify the model origin and orientation used for inspection or downstream automation. Do not assume that a saved view or displayed triad is the transferred manufacturing coordinate system.
Export a simple bounding-box or known-dimension check. A unit mismatch can create a 25.4× scale error, while an origin or axis mismatch can invalidate fixture, robot, CAM, or CMM assumptions without changing the visible shape.
Geometry health
Validate the native model before blaming the neutral format. Check for open shells, zero-thickness conditions, self-intersections, duplicate surfaces, sliver faces, very short edges, and failed features. Confirm that the intended result is a solid body when solid machining is expected.
Compute native validation properties—such as volume, surface area, mass with defined density, and center of gravity—before export. These values provide a quick comparison after translation. They do not prove topology or PMI equivalence, but a material difference is an immediate stop signal.
Audit the PMI Before Translation
Review the product manufacturing information as a requirement set, not as decoration.
- Every datum feature symbol must attach to the intended feature.
- Every feature control frame must contain the intended characteristic, tolerance value, modifiers, and datum sequence.
- Basic dimensions must fully locate or orient the controlled geometry.
- Dimensions must apply to the correct feature, model view, and product state.
- Surface texture, weld, coating, edge, and process notes must identify their intended scope.
- Saved views must expose the annotations needed for each functional area.
- General notes and default tolerances must be included or provided in a controlled companion document.
- Reference, inspection-only, and manufacturing requirements must be distinguishable.
Check whether a requirement depends on an organization-specific font, symbol, custom attribute, or annotation type that the translator may not support. Convert it to an approved standard representation or identify it in the companion documentation.
The principles of ASME Y14.5 may govern the meaning of GD&T in an applicable release, but the data exchange still has to preserve the intended association. A valid feature control frame in the authoring system can become an unassociated graphic after translation.
Choose the AP242 Export Options Deliberately
Do not use a remembered export preset without reviewing it. Record the CAD application, version, translator version, AP242 edition or conformance selection where available, encoding, and enabled content.
Relevant options may include:
- solids, surfaces, wireframe, and construction geometry;
- assembly structure versus flattened geometry;
- semantic PMI and graphical PMI;
- colors, layers, names, and user-defined attributes;
- hidden or suppressed entities;
- tessellated geometry or visualization data;
- validation properties;
- external file references versus a single exchange file;
- compressed or XML-related representations where supported.
Use the receiving supplier’s tested capability to choose an exchange profile. More data is not always safer. Including unsupported custom attributes or unnecessary geometry can increase noise. Omitting semantic PMI when an approved downstream process depends on it is much worse.
File naming and release manifest
Give the exported file a controlled identity. Include part number, revision, and file role. List it in a manifest with the native source, human-readable derivative, and any supporting specifications. Record the export application and date for traceability.
Do not overwrite the previous release with the same ambiguous filename. The supplier should be able to withdraw the obsolete file and prove which AP242 package entered programming.
Reopen the Export Outside the Authoring Session
After export, close the source file or use a clean validation environment. Reopen the AP242 file through an independent path. Ideally, inspect it in both a neutral viewer/analyzer and a representative receiving CAD or CAM application.
Check the following:
- Part or assembly opens without translator errors.
- Units and overall dimensions are correct.
- Expected solid-body and surface counts are present.
- Assembly components, names, and positions are correct.
- Volume, surface area, and other selected validation properties agree within the approved tolerance.
- Colors, layers, saved views, and coordinate systems are present when required.
- Presentation PMI is readable and placed on the intended views.
- Semantic PMI entities are present and associated with the correct geometry.
- Datum references and modifier sequences match the source.
- No annotations were converted into unassociated graphics without being flagged.
If the application reports healed, stitched, or simplified geometry, record the event. A model can become a valid solid through healing while edges, face boundaries, or identifiers change. That may affect CAM selections, PMI associations, and later revision comparison.
Validate Semantic Associations, Not Just Counts
A report that says “42 annotations imported” is weak evidence if the source also had 42 annotations. The important question is whether each requirement retained its type, value, modifier, datum sequence, and controlled feature.
Build a representative PMI test set for the release. Include plain size dimensions, a compound feature control frame, material condition modifiers, a datum feature, a profile control, an angular requirement, a surface texture callout, and a note. Use actual production data where permitted or a qualified test artifact with the same entity types.
For each item, compare:
| PMI check | Source question | Receiving-system question |
|---|---|---|
| Requirement type | Is the annotation defined with the intended semantic type? | Was that type imported or reduced to a graphic/text object? |
| Value and unit | Are nominal, limits, and unit correct? | Do the value, precision, and unit match? |
| Geometry link | Which feature or surface is controlled? | Does the imported entity reference the same geometry? |
| Datum system | Are datums and precedence correct? | Is the datum sequence intact and usable? |
| Modifiers | Are MMC, LMC, projected zone, tangent plane, or other modifiers intended? | Were all supported modifiers preserved and flagged if unsupported? |
| Saved view | Where should a human review the requirement? | Is it visible in the expected view without hiding critical context? |
| Lifecycle state | Which part/revision does it govern? | Does the imported product structure retain that identity? |
This mapping is especially important when downstream automation is planned. Automation should stop on unsupported or unassociated data, not silently omit it.
CAM Import Checks
CAM systems primarily need trustworthy machinable geometry, but PMI and names can accelerate setup when handled correctly. Verify the imported body is watertight, at the correct scale, and oriented as expected. Compare face and edge counts if they are part of a qualified translator test, while recognizing that legitimate topology changes can alter counts.
Test whether manufacturing coordinate systems, named features, colors, or layers used for process planning survive the import. Do not assume a color means “critical surface” unless that meaning is defined and supported in both systems.
If PMI is imported into CAM, determine whether it drives any automatic action or only informs the programmer. A displayed tolerance does not automatically change toolpath accuracy, stock allowance, cutter selection, or inspection strategy. The programmer must know which data is trusted and which requires manual verification.
Record translator warnings, healed faces, missing references, and manual recreations. If the shop converts AP242 into another internal format, that second translation also needs control.
The QuickCNCs CNC machining services page describes available processes. A production RFQ should still disclose the authoring system, file format, and PMI expectations so that the actual import path can be evaluated before release.
CMM and Inspection-Planning Checks
Inspection software may use semantic PMI to create characteristics, measurement paths, and report fields. That can reduce transcription, but only after the exchange is validated.
Confirm that the inspection application imports:
- the correct nominal geometry and units;
- the intended datum features and order;
- tolerance values and material condition modifiers;
- basic dimensions and feature associations;
- surface versus feature-of-size distinctions;
- saved views or presentation needed by the inspector;
- characteristic identifiers used in the balloon or quality plan.
Review every automatically created characteristic before execution. Software may support position but not every composite-control nuance, or may display a modifier without applying its full evaluation logic. Establish a documented fallback for unsupported PMI: controlled manual entry, a drawing-based characteristic, or engineering clarification.
The final inspection report should identify the part, revision, measurement program revision, units, datum setup, nominal/limits, actual results, and disposition. It should not imply that AP242 alone proves the measurement method is suitable.
Human-Readable Data Remains Important
Even in an MBD workflow, buyers and suppliers need a reviewable representation. Procurement, receiving inspection, sub-tier processors, and customer quality teams may not share the same AP242-capable software. A controlled PDF, lightweight viewer package, or generated technical data package can provide human-readable confirmation.
The companion representation should not become an uncontrolled second definition. Give it the same part/revision identity, describe its authority, and generate it from the approved source. If the human-readable view and semantic data disagree, stop the release and correct the source.
Keep non-geometric requirements visible. AP242 PMI may not carry every purchasing, packaging, certification, finish, cleanliness, marking, or delivery requirement in a form the recipient uses. Put those requirements in an appropriate controlled document and include it in the manifest.
Common AP242 Failure Modes
PMI appears but has no geometry association
The annotation can be seen in a view, yet the receiving software treats it as graphics. Do not use it for automatic inspection generation. Check exporter PMI options, translator support, and source annotation type.
Datum references are incomplete or reordered
A feature control frame may display while its structured datum links are missing. Compare source and destination semantic properties, not only the text string.
Geometry healing changes topology
Stitching or repair can split or merge faces and edges. Revalidate PMI links, CAM selections, and any face-ID-based automation. If repair is substantial, return to the design source instead of normalizing an uncontrolled derivative.
Assembly names or occurrences collapse
A flattened export may preserve shape but lose component identity and transforms. Re-export with the required product structure or provide controlled individual-part files plus a manifest.
Units or coordinate systems change
The geometry may look correct until compared with a known dimension or fixture origin. Use bounding dimensions and explicit coordinate-system checks before programming.
Unsupported annotations disappear silently
Custom symbols, notes, weld callouts, or certain surface requirements may not transfer. Maintain an exception list and a controlled companion document rather than assuming absence means “not required.”
Release Checklist for STEP AP242 PMI
Before authorizing CNC production, confirm:
- The native model, AP242 file, drawing/derivative, RFQ, and purchase order carry the same part and revision.
- The authority and precedence of the model, drawing, and companion documents are stated.
- The correct configuration, suppression state, and assembly representation were exported.
- Units, scale, orientation, origin, and required coordinate systems match.
- Native geometry validation passes before export.
- The export profile and translator versions are recorded.
- Required solids, surfaces, assemblies, names, colors, layers, and attributes are present.
- Presentation PMI is complete and readable in the required saved views.
- Semantic PMI entities exist for every requirement intended for machine consumption.
- Geometry associations, values, modifiers, and datum references match the source.
- Volume, area, mass, centroid, or other selected validation properties agree.
- Translator warnings, healing, missing entities, and manual recreation are documented.
- The CAM import uses the correct solid, unit, coordinate system, and revision.
- The CMM/inspection import has been qualified for the PMI types being consumed.
- Unsupported PMI follows a controlled manual-review path.
- A human-readable representation and non-geometric requirements accompany the model.
- Superseded files are withdrawn from supplier programming and inspection locations.
- Any conflict triggers engineering clarification before irreversible work.
What to Include in the CNC RFQ
Send the controlled AP242 file, its human-readable companion, the file manifest, quantity, material and condition, surface finishing, inspection scope, packaging, and delivery destination. Identify the source CAD application and version, export profile, expected downstream use of semantic PMI, and any known translator limitation.
Ask the supplier to confirm its receiving CAD/CAM/CMM applications and versions, whether it reads presentation or semantic PMI, whether a secondary conversion is required, and how unsupported data is reported. The goal is not to dictate proprietary software. It is to expose the actual data path before the quote becomes an order.
For prototype work, the same preflight protects fast iteration; the QuickCNCs rapid prototyping page explains the service context. When the release is ready, submit the model, controlled drawing or derivative, and requirements through the Request a Quote page.
AP242 can support a strong digital thread when the exchange is qualified. The reliable practice is to treat translation as a controlled process: define authority, validate the source, record the export profile, reopen the file independently, verify semantic associations, test the receiving applications, and retain human-readable evidence. That turns a file that merely opens into a production release that engineering, manufacturing, and inspection can use consistently.