STEP AP203

Identity and applicability

STEP AP203 covers configuration-controlled mechanical design exchange. Confirm the schema and exporter profile because the Part 21 filename extension is shared. ISO AP203 record, NIST: STEP File Analyzer and Viewer

Creo Parametric 13 distinguishes ap203_is, ap203_is_ext and ap203_e2 export options. Its parts-and-assemblies guidance associates ap203_e2 with annotation export, including GD&T, notes and symbols. This illustrates why an AP number without the selected implementation option is an incomplete description. Do not infer semantic PMI relationships merely from visible annotation graphics. PTC: exporting parts and assemblies to STEP

Use AP203 when it is the agreed exchange supported by the recipient and it carries the information required for the task. Specify whether that task needs part shape, assembly structure, configuration information or manufacturing annotations. A readable model is not automatically a complete design release. Retain the governing revision and identify the drawing, model or specification used for acceptance.

Editions matter

ISO identifies ISO 10303-203:2011 as edition 2, with publication date 2011-01, and marks it withdrawn. Its record points to ISO 10303-242:2014 as its replacement; that historical link does not establish the current AP242 edition or recipient support. The earlier modular technical specification, ISO/TS 10303-203:2005, is also withdrawn. ISO 2011 record, ISO 2005 record

The 2011 scope includes configuration control, assembly usage, several shape representations, geometric validation properties, tolerances, materials and presentation information including colors. Consequently, “AP203 never contains color or tolerances” is too broad an edition-independent rule. Scope is also not a guarantee that a particular translator implements or writes every capability. ISO edition-2 scope

For an exchange agreement, record the application protocol, edition or schema where available, source application release, export profile and receiving application release. Ask for the effective translator settings when a menu merely says “AP203.” Do not silently substitute a newer protocol for a contractual or legacy delivery requirement; agree and test the change with the recipient.

Translator examples and capability boundaries

SOLIDWORKS 2026 documents AP203 and AP214 exchange and describes its AP203 route as having no color implementation, while its AP214 route supports body, face and curve colors. It also documents wireframe exchange, optional configuration-data mapping on import, and export of a part or assembly's length unit. Treat that guidance as evidence for the documented application route, alongside the broader edition-2 scope above. SOLIDWORKS 2026: STEP files

Keep requirements for editable native features, annotation references and downstream automation explicit. A transferred solid can be useful for machining or analysis without recreating the original feature tree. Conversely, a model that looks correct can be inadequate when the receiving process needs queryable datum references or other information absent from the exchange.

Geometry, assemblies and coordinates

SOLIDWORKS 2026 exposes solid/surface versus wireframe output, an output coordinate system and an AP203 configuration-data option. It warns that STEP export can complete despite serious translation errors, with a notification directing the user to an error file. Check the report and resulting geometry rather than treating completion as acceptance. SOLIDWORKS: STEP export options

Compare expected bodies, solid-versus-surface status, component instances, placements and the chosen configuration with the source. Establish the intended units, origin and orientation through a known feature and coordinate reference. A dimension label or a matching shaded image alone is not a physical-size check. If multiple files are delivered, retain their relationships and verify that the recipient can resolve every required component from the delivered package.

Original scale example: a rectangular block intended to measure 40 × 20 × 10 mm has volume 8000 mm³. If the same numerical dimensions are interpreted in centimeters, linear dimensions increase tenfold and volume increases by 10³ = 1000, to 8,000,000 mm³. This is unit-conversion arithmetic, not a claim about AP203 storing unitless coordinates. Investigate the source, export and import interpretation before applying a corrective scale.

Validation properties and their limits

Creo 13's validation-property guidance lists ap203_is_ext and ap203_e2 among supported export choices. It describes area, volume and centroid comparisons and a separate choice to include assembly validation information. Its extended AP203 option includes colors/layers, geometric validation and associative text extensions. These are explicit translator options, not evidence that all AP203 files contain those properties. PTC: exchanging validation properties

PTC also documents import logs with entity statistics, validation-property differences and header information such as source/target units and model accuracy. Review unavailable or skipped data as well as numerical differences. PTC: import-log structure

Volume, area and centroid are useful screening comparisons under consistent units and assumptions. They do not prove identical topology or conformity of every small feature: similar total volume can coexist with a missing passage or an altered seating surface. Set acceptance limits from the actual design and downstream use, rather than adopting an arbitrary universal percentage.

NIST's STEP File Analyzer and Viewer supports AP203 and can inspect entities, attributes, validation information and basic file-format errors. That helps identify what was delivered; it does not qualify machining, inspection or structural performance. NIST software description

Practical handoff record

Provide the following alongside the model:

• Part or assembly identifier, revision and required receiving task.
• Actual AP203 edition/schema or exporter option, application releases and effective profile.
• Required geometry, configuration, annotation and non-geometric content.
• Expected units, check dimension, body/component counts and orientation reference.
• Governing acceptance requirements, translation warnings and any agreed conversions.

Reopen the delivered file in the recipient's workflow, inspect critical features and resolve warnings before release. Preserve the original alongside repaired or converted derivatives. These checks are proposed exchange practice, not a translator certification or a guarantee arising from the AP203 label.

Source scope and related reference

Standards dates above follow the ISO records' publication-date fields. Application examples are scoped to SOLIDWORKS 2026 and Creo 13 documentation; crawl dates are not treated as technical revisions. The scale calculation and proposed acceptance checks are editorial guidance.

See Drawing and model file references for the surrounding design handoff.