STEP vs Parasolid for CNC RFQs: Which CAD Format Should You Send?

When a machine shop asks for a 3D model, the practical question is not which file extension is “best” in the abstract. The question is which file the supplier can import without changing geometry, losing product structure, or misunderstanding the released revision. For most CNC RFQs, STEP is the safest vendor-neutral baseline. Parasolid can be the cleaner handoff when the sender and receiver use compatible Parasolid-based systems and have confirmed the supported version.

That is the short answer. A reliable STEP versus Parasolid file selection still depends on what must travel with the shape: a single solid or an assembly, body and component names, colors and layers, product manufacturing information, material attributes, or only nominal geometry. It also depends on what the supplier will do next in CAM, inspection planning, and document control.

This guide explains those differences for CNC buyers and engineers. It does not treat either format as a replacement for a controlled drawing. The 3D model supplies nominal geometry; the drawing or an explicitly governed model-based definition supplies tolerances, finishes, notes, acceptance criteria, and revision authority.

The recommendation in one minute

Use STEP AP242 as the default neutral exchange format when several suppliers, CAD systems, CAM systems, or long-term archive needs are involved. AP242 is the current STEP application protocol intended for managed model-based 3D engineering and can carry richer product structure and PMI than older STEP practices, although the receiving software must support those entities.

Also provide Parasolid .x_t when the selected supplier requests it, especially when both CAD and downstream CAM use the Parasolid kernel. A same-kernel transfer can avoid some of the geometric translation that occurs when a model is mapped from one representation to another.

Use .x_b only when both sides have confirmed binary Parasolid support and version compatibility. The binary file can be more compact, but it is less convenient for manual identification, text-based comparison, or troubleshooting than .x_t.

For a quote-ready package, include:

1. One controlled 3D file in the agreed format.
2. A controlled 2D PDF drawing, unless the contract explicitly governs a complete MBD dataset.
3. A release note naming the part number, revision, units, export format and schema, and source CAD version.
4. Any assembly, reference geometry, or mating-component data needed to understand function.
5. A list of critical characteristics and required inspection evidence.

What a STEP file is

STEP is the common name for ISO 10303 product-data exchange. It is not one single, unchanging translator. The standard contains application protocols that define which kinds of product information can be represented. For mechanical CAD exchange, the protocols most often encountered are AP203, AP214, and AP242.

A STEP file normally uses the text-based Part 21 exchange syntax and the extensions .step or .stp. It can represent boundary-representation geometry, analytic surfaces, trimmed surfaces, topology, assemblies, and selected attributes. The exact content depends on the exporter, the chosen application protocol, and the receiving application’s importer.

For CNC quotation, the main strength of STEP is broad interoperability. A buyer can send one neutral file to suppliers using different CAD and CAM systems. The limitation is that every exchange passes through an exporter and an importer. Both must agree on the entities, tolerances, units, assembly structure, and optional attributes being transferred.

The NIST STEP File Analyzer can report useful file-level information, such as the STEP schema, product structure, geometry counts, PMI-related entities, and validation properties. It does not replace opening the file in the supplier’s production system, but it is valuable for release checks and troubleshooting.

AP203, AP214, and AP242 are not interchangeable labels

The AP designation matters because it describes the intended information model, not just the appearance of the solid after import.

AP203

AP203 was developed for configuration-controlled 3D design of mechanical parts and assemblies. In practice, it became a widely supported baseline for solid geometry and product structure. Older AP203 exports may carry less presentation information than AP214 or AP242. AP203 Edition 2 expanded capabilities, including representation of additional product and geometric information, but software menus do not always disclose the edition clearly.

AP203 remains usable when the RFQ needs dependable nominal geometry and the supplier’s older software has proven support for it. It should not be selected merely because it appears first in an export menu.

AP214

AP214 originated around automotive mechanical design and became popular for CAD exchange because it could preserve more presentation and organization data, including colors, layers, and richer assembly information in many implementations. Those details help when a supplier uses color or layer conventions to distinguish stock, keep-out zones, sealing faces, or reference components.

AP214 support is widespread, but it is no longer the forward-looking choice for a new controlled MBD process. A buyer may still request it when a proven supplier toolchain imports AP214 more reliably than AP242.

AP242

AP242 brings together the major mechanical-design capabilities associated with AP203 and AP214 and extends the standard for managed model-based 3D engineering. It is the preferred STEP protocol when the release needs semantic PMI, presentation PMI, product structure, validation properties, or a durable neutral representation.

AP242 capability is not binary. A CAD system may export AP242 geometry but omit semantic PMI; another may show annotation graphics but not expose machine-readable feature-control frames to CAM or CMM software. The STEP application protocol overview from STEP Tools is useful background, but the decisive test is the actual sender-to-receiver workflow.

For an RFQ, state the protocol explicitly: for example, STEP AP242, millimeters, assembly structure retained. Do not rely on .stp alone to communicate that information.

What a Parasolid file is

Parasolid is a geometric modeling kernel developed by Siemens and licensed for use in many CAD, CAM, and CAE products. A Parasolid transmit file stores model data in the kernel’s exchange representation. Common extensions are .x_t for text and .x_b for binary.

Parasolid is not a neutral international standard in the same sense as STEP. It is a proprietary kernel format with published exchange behavior available through licensed implementations. Its practical advantage is directness: when the source and destination applications both use compatible Parasolid kernels, the receiver may be able to read the model without translating the geometry into a different kernel representation.

That advantage can matter for complex blends, trimmed surfaces, small edges, tolerant geometry, and multi-body parts. It is not a guarantee. Application-level features, constraints, design history, configurations, and proprietary metadata usually do not become editable native features merely because both systems use Parasolid.

Siemens describes the current kernel and supported product-development use cases on its Parasolid product page. For an RFQ, the buyer still needs to ask which Parasolid version the supplier’s importer supports.

Parasolid .x_t and .x_b

Both extensions are Parasolid transmit formats. They are different serializations of Parasolid model information, not different geometric modeling methods.

Choose .x_t when traceability and troubleshooting matter

The .x_t file is a text representation. It is the more common choice for supplier exchange because it is broadly recognized and its header can be inspected with a text editor. That can help a document-control owner confirm the file type and version without opening the CAD model. Text files are also easier to compare at a basic file level, although a text diff is not a meaningful substitute for a geometric comparison.

Choose .x_b when a confirmed workflow prefers binary

The .x_b file is binary. It may be smaller and faster to read or write for large models, depending on the model and software. It is not human-readable and may be less convenient for systems that inspect, scan, or transform text-based engineering data.

Do not assume that every application offering “Parasolid” accepts both forms. Ask the supplier to confirm .x_t or .x_b, the highest supported Parasolid version, and whether the importer preserves assemblies and attributes required for the job.

How STEP and Parasolid preserve solids, surfaces, and topology

Both formats can represent precise boundary-representation models. A B-rep describes a solid through connected faces, edges, and vertices, along with the underlying surface and curve geometry. A valid solid requires consistent topology: face loops must close, edge use must agree, and the shell must bound a volume.

The important difference is the translation path.

With STEP, the exporter maps the source CAD model into STEP entities. The receiver maps those STEP entities into its own kernel. If the systems use different modeling tolerances or represent certain surfaces differently, the importer may need to sew adjacent faces, merge vertices, or rebuild trims. A successful “solid” status after import is a useful check, but it does not prove that every radius, hole, edge, or face boundary is identical to the source.

With Parasolid-to-Parasolid exchange, the geometry can remain closer to the receiving kernel’s native representation. The receiver still interprets a transmit file and may upgrade it to a newer kernel version, but it may avoid a cross-kernel conversion. When the receiving application uses another kernel, Parasolid also becomes a translated exchange and its same-kernel advantage is reduced.

Surface models require extra care in either format. A collection of surfaces can look complete while containing gaps, overlaps, reversed normals, or open boundaries. Tell the supplier whether the intended deliverable is one watertight solid, several solid bodies, or intentionally open surfaces.

Assembly structure, names, and attributes

A CNC RFQ may include a single machined component, a multi-body part, or an assembly that explains interfaces. The chosen export settings determine whether the file arrives as one flattened body or as a structured product tree.

STEP can carry product and assembly relationships, component instances, names, colors, layers, and selected properties. AP214 and AP242 implementations usually provide more useful presentation and product-structure options than a minimal older export. Parasolid transmit files can carry assemblies and attributes supported by the creating application, but application-specific metadata may not survive outside the original CAD environment.

Before release, check these items in an independent receiving application:

• Part number and revision are visible in the filename or release manifest.
• Assembly instances are not unintentionally flattened.
• Component names remain recognizable.
• Suppressed or reference-only components are handled intentionally.
• Multi-body parts contain the expected number of bodies.
• Colors and layers used to communicate manufacturing meaning are preserved or replaced by explicit notes.
• Coordinate systems, origins, and named datums required for programming are identifiable.

Do not encode a critical requirement only through a color, layer, or body name. Put acceptance requirements in the controlled drawing, PMI dataset, or release specification.

PMI and model-based definition

Product manufacturing information includes dimensions, tolerances, datum systems, surface texture, notes, and other annotations associated with the 3D model. Two forms need to be distinguished.

Presentation PMI is graphical. It lets a person see annotation planes, callouts, and symbols. Semantic PMI stores machine-readable meaning, such as a tolerance value associated with a specific feature and datum reference frame. CAM or CMM software may use semantic information to support feature recognition or inspection planning.

STEP AP242 is the stronger neutral choice when PMI/MBD must be exchanged. It was designed to support model-based engineering information beyond shape alone. Still, PMI survives only when the authoring system exports it correctly and every downstream application imports the required entities.

Parasolid primarily transfers geometric model data. Some application attributes can travel, but a complete MBD release often depends on additional application-specific data or another standardized representation. Do not assume that a Parasolid file exported from a CAD system contains the semantic GD&T visible on screen.

For an MBD RFQ, perform a round-trip or independent-viewer test. Compare annotation count, associated geometry, datum references, tolerance values, units, and saved views. If the supplier cannot demonstrate semantic PMI support, include a controlled 2D drawing or a human-readable 3D PDF as an interpretation aid while keeping the contractual authority explicit.

CAD kernels and version compatibility

Every CAD and CAM system uses a geometric kernel or a proprietary geometry engine. Kernel identity helps predict translation risk, but it does not determine the full result. The application controls export settings, assembly packaging, attributes, configurations, and the version of the exchange library.

Parasolid transmit files contain a format version. Newer applications can commonly read older transmit versions, while an older importer may reject a file written by a newer kernel. When sending Parasolid, export to the supplier’s supported version rather than automatically choosing the newest available.

STEP files also vary by protocol and implementation. An older CAM release might import AP203 or AP214 reliably but fail on an AP242 construct it does not understand. In that case, provide the newer controlled master plus an agreed compatibility export, and identify which file governs nominal geometry.

The most dependable compatibility question is specific: “Can your production CAM release import this exact test file as the expected bodies with no geometry-repair warning?” A generic statement that a shop “accepts STEP and Parasolid” is not enough for a complex model.

STEP translation, stitching, and repair risk

Geometric repair is not automatically an error. Importers often reconcile small numerical differences so adjacent faces form a valid body. The risk is an undocumented repair that changes a functional boundary.

Common warning signs include:

• The source is a solid, but the imported result is a sheet body.
• The imported model contains more or fewer bodies than expected.
• A face is missing, inverted, or replaced.
• A very small edge or sliver face appears near a blend or trimmed surface.
• Cylinders, cones, or planes arrive as generic spline surfaces.
• Holes or pockets are no longer recognized as expected features.
• The model bounding box or mass properties differ beyond a justified numerical tolerance.
• The importer reports sewing, tolerant edges, invalid geometry, or automatic healing.

When a warning occurs, do not silently continue into CAM. Record the source file checksum, importer and version, message, repaired entity, and disposition. Compare validation properties or mass properties when available. Overlay the imported body against a trusted reference or use a geometric comparison tool. If a repair alters a critical face, request a new export or native-file review.

The NIST analyzer can support file-level inspection of STEP data. The production decision must still be based on the geometry as imported into the actual CAD, CAM, and inspection environment.

Effects on CAM programming and CMM planning

CAM software needs usable nominal geometry for stock definition, setup orientation, feature selection, toolpath boundaries, collision checking, and verification. A model can display correctly yet create extra programming work if analytic faces become splines, edges are fragmented, or a closed region imports as disconnected surfaces.

Parasolid can reduce that cleanup in a compatible same-kernel workflow. STEP can be equally successful when the translators are mature and the export is clean. The RFQ should not predict programming hours from the extension alone. Ask the supplier to identify import warnings and any required geometry repair as a quotation assumption.

CMM programming has a related but different need. The nominal model supports alignment, feature construction, point distribution, and comparison. Acceptance limits come from the controlled drawing or validated semantic PMI. If a translator changes topology, a CMM program may lose face associations when the model is replaced, even if the visible shape is nearly unchanged. Revision control should therefore connect the exact model file to the inspection program and report template.

For complex parts, request confirmation that the quoted model opens in both the planned CAM system and the inspection-planning system. That check is more useful than asking whether the supplier owns a particular software brand.

When STEP should be the primary RFQ file

Prefer STEP when:

• The RFQ will go to several suppliers using different software.
• The receiving CAD/CAM kernel is unknown.
• The buyer needs a vendor-neutral archive.
• Assembly structure, colors, names, or AP242 PMI need to travel.
• The supplier specifically requests STEP.
• Procurement wants one controlled neutral baseline across bidders.
• A future supplier transfer must not depend on access to one proprietary CAD system.

For new releases, AP242 is usually the best starting point. Use AP214 or AP203 only when a proven compatibility requirement justifies it. Record that exception in the release manifest so a later team does not mistake the compatibility export for the preferred master.

When Parasolid should be the primary or companion file

Prefer Parasolid when:

• The authoring and receiving applications use compatible Parasolid kernels.
• The model contains complex trimmed surfaces or blends that translate poorly through the available STEP path.
• The supplier has tested the exact Parasolid version in production CAM.
• Fast, direct geometry exchange matters more than vendor-neutral archiving.
• The supplier requests .x_t as its preferred programming input.

Even then, consider including STEP as a companion neutral file. If the two imports disagree, stop and resolve the source rather than allowing the supplier to choose the easier-looking body. Name one governing file for nominal geometry and document why the second file is included.

Why the RFQ still needs a controlled 2D drawing

A precise 3D solid does not automatically define manufacturing acceptance. Unless a validated MBD process says otherwise, it does not reliably communicate every tolerance, datum relationship, surface finish, edge condition, thread requirement, coating note, heat treatment, marking instruction, inspection frequency, or revision approval.

The drawing should state which dimensions are basic, which surfaces are critical, how GD&T applies, and which general tolerances govern unspecified features. It should also identify material, finish, special processes, and document revision. The model and drawing must share the same part number, revision, units, and configuration.

If the model and drawing conflict, the RFQ needs a stated order of precedence and a clarification process. Do not rely on a generic title-block sentence if the organization uses MBD for some parts and drawing-based definition for others.

QuickCNCs uses the released model to evaluate manufacturability and programming scope, while the controlled drawing establishes the required acceptance details. Buyers preparing a package for CNC milling services should include both when tolerances, finishes, or inspection records influence the quote.

File submission preflight checklist

Complete this check before issuing the RFQ:

1. Open the exported file in a different application or independent viewer.
2. Confirm units without relying on model size as a guess.
3. Confirm the expected number of solids, surfaces, and assembly components.
4. Check the bounding box and, where practical, volume or mass properties.
5. Inspect small blends, deep pockets, thin walls, threaded regions, and trimmed surfaces.
6. Confirm part origin, orientation, and any required coordinate systems.
7. Confirm assembly names and instance positions.
8. Verify AP203, AP214, or AP242 for STEP; verify .x_t or .x_b and version for Parasolid.
9. Confirm whether PMI is presentation-only or semantic and test its import.
10. Compare the model and drawing part number, revision, and units.
11. Remove suppressed, obsolete, or unrelated components unless they are intentionally supplied as references.
12. Use a filename that includes the part number and revision without ambiguous words such as final2 or latest.
13. Generate a checksum when document-control requirements justify it.
14. List the native source CAD system and version in the release note.
15. Ask the supplier to report import or healing warnings before programming.

For a broader view of how production software affects the handoff, see CNC machining software for aluminum and titanium components.

STEP and Parasolid comparison table

RFQ decision factor	STEP	Parasolid
Ownership	ISO 10303 neutral standard	Siemens Parasolid kernel format
Common extensions	.step, .stp	.x_t text, .x_b binary
Best use	Multi-supplier and cross-platform exchange	Confirmed compatible kernel workflow
Geometry	Precise B-rep, surfaces, solids, topology	Precise Parasolid geometry and topology
Translation path	Source kernel to STEP to receiving kernel	More direct for compatible Parasolid systems; translated for other kernels
Assemblies	Supported; result depends on protocol and exporter/importer	Supported within application and transmit capabilities
Colors and layers	Often supported, especially AP214/AP242 implementations	Attribute transfer varies by application
PMI/MBD	AP242 can carry presentation and semantic PMI	Not a complete vendor-neutral MBD substitute by itself
Version concern	AP protocol and translator implementation	Parasolid transmit version and .x_t/.x_b support
Human inspection	Part 21 text can be inspected at file level	.x_t partly inspectable; .x_b is binary
Long-term archive	Stronger vendor-neutral choice	Better treated as a working exchange unless archive policy accepts it
Main risk	Translation, stitching, unsupported entities, lost attributes	Kernel-version mismatch and application metadata loss

Recommendations for common procurement scenarios

Multi-supplier competitive RFQ

Send STEP AP242 plus the controlled drawing. Ask every bidder to confirm successful import and disclose repair warnings. This gives suppliers a common neutral baseline and makes quotation assumptions easier to compare. Add Parasolid only when a bidder requests it, and keep the STEP file as the shared reference unless engineering approves another authority.

Known supplier using a compatible Parasolid workflow

Send .x_t at the supplier’s supported version, the drawing, and optionally STEP AP242 as a neutral reference. Ask the supplier to confirm body count and key validation properties after import. Use .x_b only if binary transfer has been tested.

AP242 model-based definition

Send AP242 with semantic PMI, a release manifest, and a human-readable view of the annotations. Require the supplier to demonstrate that its CAD, CAM, and CMM tools preserve the PMI associations needed for the part. If that cannot be demonstrated, add a controlled drawing rather than assuming visible annotations are machine-readable.

Legacy CAM system

Ask which STEP protocol and Parasolid version the system accepts. Export a controlled compatibility copy from the released master and label it clearly. Do not overwrite the master or change the contractual revision merely to satisfy an old importer.

Complex surface model with STEP healing warnings

Test Parasolid if both sides support compatible kernels. Compare body count, validation properties, and critical surfaces between the source and imported result. If neither neutral route is dependable, arrange a controlled native-file handoff and document the application version and configuration.

Long-term supplier transfer and archive

Retain the native source, a validated STEP AP242 derivative, the controlled drawing or MBD package, the release manifest, and checksums where required. Parasolid may remain a useful manufacturing derivative, but a neutral STEP file reduces dependence on one kernel ecosystem.

Build a quote-ready release package

The file extension is only one line in the RFQ. A complete package should tell the supplier what to manufacture, what controls acceptance, and what evidence must return with the parts.

Include the part number, revision, quantity, material and condition, finish, delivery need, critical characteristics, inspection documentation, and any approved alternate. State whether the 3D file controls nominal geometry and whether the drawing or semantic PMI controls tolerances. Identify reference-only assembly data so it is not mistaken for production scope.

Do not send several unlabeled geometry files and expect the shop to decide which one is correct. If STEP and Parasolid are both included, name the governing file and the reason for the companion file. A short manifest can prevent more ambiguity than another uncontrolled export.

For a supplier review, use the neutral format that reaches the widest qualified bidder set, add Parasolid when it reduces a demonstrated translation risk, and keep the controlled drawing aligned with the same revision. That approach makes STEP versus Parasolid file selection a traceable engineering decision rather than a preference hidden in an export menu.

When the package has passed the preflight checks, request a CNC machining quote and ask the supplier to confirm the actual imported body count, units, and any geometry-repair messages before programming.