Technical insight
Rotor STEP File and PMI Handoff: A Buyer Checklist
Before using a STEP file to obtain a turbomolecular rotor quotation, ask the recipient to confirm what arrived: geometry, visible engineering annotations and any machine-readable product information. Use the handoff worksheet below to identify missing information before accepting the proposed scope. This is editorial purchasing guidance, not a CAD conformance service.
By Geetai Precision
- Published
- Updated
Three separate information checks
NIST distinguishes semantic PMI, which software can interpret, from graphic PMI, which preserves the visual presentation of annotations. A displayed note and a computer-interpretable requirement are therefore different kinds of information. STEP can carry geometry and PMI; the file extension alone does not describe the contents of a particular export. [1]
NIST's model-based engineering project includes surface texture, finish requirements, process notes and material specifications within PMI. Treat these as part of the information review, rather than checking only whether the rotor shape opens on screen. [2]
Autodesk's Inventor documentation lists STEP AP242 import and export with part and assembly PMI support. This is an example of documented translator support, not evidence that an individual supplier received every required item. Record the sending and receiving software versions and the export settings actually used. [3]
A rotor CAD handoff worksheet
Use one row per information category. The suggested receipts below are a buyer-created coordination aid; they are not a standard-mandated acceptance procedure. Ask the design owner to identify the governing definition and resolve conflicts between a drawing, native model and exchanged file.
| Information category | Receipt to request | Question to close |
|---|---|---|
| Geometry | An import record naming the actual file, units and included bodies; marked views of the blade passages and hub. | Do the supplied model and the received view refer to the same intended component? |
| Visible annotations | A list of the expected notes and saved views, with a marked example from the receiving application. | Which annotations are present, missing or unreadable? |
| Machine-readable PMI | Where downstream automation is required, a record of the PMI entities recognized by the receiving system. | Was the requirement interpreted as data, or only displayed as graphics? |
| Associated requirements | A manifest identifying the approved drawing, material requirements and linked specifications. | Where is each requirement defined, and which document governs any conflict? |
A receipt check, not a production release
Use screenshots as evidence of what was displayed, not as proof that all engineering information survived the exchange. If automated consumption of PMI is part of the agreed workflow, request a separate data-content check. NIST describes reports for semantic PMI, graphic PMI and validation properties, as well as a basic syntax checker. These are different checks, not interchangeable approvals. [1]
For the quotation review, mark the rotor features that need explicit discussion: blade passages, the central bore and the mating faces identified on the drawing. Ask the recipient to flag incomplete or ambiguous definitions. Do not ask the supplier to reconstruct a missing requirement from a photograph or from the apparent shape of another part.
Example: the shape arrives, but a note does not
Consider a hypothetical RFQ in which the received model displays the rotor correctly, but the sender's surface-finish note is absent. Record the missing note, ask the design owner for the controlled requirement, and have the recipient acknowledge the corrected package. Keep any affected quotation item open until that response is reviewed. This is an example decision path, not a customer case.
Do not respond to this one missing note by assuming every STEP export is unsuitable. Equally, do not treat a successful import as approval of the entire package. Close the named discrepancy and retain the specific files and receipt record used for the quotation.
Prepare a drawing-led review
For a rotor inquiry, prepare the authorized drawing and CAD package, the completed handoff worksheet and a short list of unresolved export questions. Use the rotor service page to frame the component scope and the quotation preparation page to organize the inquiry. Keep file-transfer review separate from approval of a manufacturing route.
Frequently asked questions
Does a visible PMI annotation prove that software can interpret it?
No. NIST distinguishes graphic presentation from semantic representation. Where machine interpretation is required, ask for evidence from the receiving workflow rather than relying only on the annotation's appearance. [1]
Must a STEP file always replace the drawing?
Do not assume either file has automatic precedence. Ask the design owner to identify the governing definition and specify how associated requirements are supplied. The worksheet helps record that decision; it does not establish a universal document hierarchy.
Related review paths
More from Blog
References
- STEP File Analyzer and Viewer — NIST. Accessed 2026-09-27T03:22:24.000Z.
- MBE PMI Validation and Conformance Testing — NIST. Accessed 2026-09-27T03:22:24.000Z.
- Translators (3rd Party Files) and Supported File Versions — Autodesk. Accessed 2026-09-27T03:22:24.000Z.