What STEP actually is
STEP, formally ISO 10303, is an international, vendor-neutral standard for representing and exchanging digital product data between independent CAD, CAM and other engineering systems. That neutrality is the point: a model built in one CAD package can be opened and measured in another without proprietary lock-in. But STEP is a container format with different application protocols, and what a specific STEP file contains depends on which protocol was used and what the exporting system chose to include, not on the fact that the file extension is .step.
What a drawing traditionally carries
A 2D drawing communicates dimensions, tolerances, GD&T callouts, material notes, surface finish requirements and revision history in a form built specifically for human interpretation, independent of whatever 3D file accompanies it. None of that is guaranteed to also exist inside a bare-geometry STEP file. A drawing and a geometry file have historically covered different ground for a reason: one describes shape precisely, the other describes intent and requirement precisely, and a flat PDF drawing on its own also lacks the exact 3D topology a STEP file provides.
Where Model-Based Definition changes this
Model-Based Definition (MBD) is the practice of using the 3D model itself as the primary carrier of product-definition information, including dimensions, tolerances, GD&T, datums and material requirements, rather than pushing all of that into a separate drawing. ISO 16792 formalises this directly: it specifies requirements for digital product-definition data and explicitly supports two methods of application, a 3D-model-only workflow and a 3D-model-with-2D-drawing workflow.1 Critically, MBD does not mean the drawing disappears by definition — it means the model can carry what the drawing used to carry alone, if the workflow and the exporting system actually put that information into it.
STEP AP242 is the specific application protocol most commonly used to exchange this kind of richer, model-based product definition — Product and Manufacturing Information (PMI: dimensions, tolerances, GD&T, datums) can travel inside an AP242 file, not just bare geometry. But a .step extension by itself says nothing about whether that happened. Two STEP files from two different source systems, both technically valid, can carry completely different amounts of usable information.
The real failure mode
The costly mistake is not choosing STEP or the drawing — it is assuming that having a 3D file at all means the manufacturing definition is complete. NIST research into model-based product definition describes this gap directly: information that a traditional drawing carried implicitly, such as manufacturing constraints, process information and material requirements, is often not captured in the digital model that is meant to replace that drawing, even in current industrial practice.2 A positional tolerance, a datum reference, or a surface-finish callout that lives only on the drawing and never made it into the STEP file's PMI will not show up no matter how carefully the geometry is inspected.
A second, quieter version of the same mistake shows up on a revision: a drawing revision can change a tolerance or add a note while the accompanying STEP file's geometry looks unchanged, or vice versa. Reading only one file consistently, out of habit, is how that kind of mismatch gets missed.
A practical checklist
Before treating a STEP file as sufficient on its own: check whether it actually contains PMI (many viewers will show this directly) or only geometry; check the drawing's revision block against the STEP file's own metadata if both are present; and when in doubt, read both, since neither is reliably complete alone. This is standard practice for a reason, not an outdated habit STEP is meant to replace.
Why this matters beyond one file format
The deeper point generalises past STEP specifically: a machine-readable model that actually carries its product-definition information reduces how much of that information has to be reconstructed by hand at each downstream step — planning, programming, inspection. But that only holds if the information was put there in the first place. Reading and reconciling both formats, rather than assuming one supersedes the other, is exactly the kind of structural requirement a manufacturing intelligence system has to handle explicitly rather than assume away.