Decision statement
What must this supplier or CAE task help the OEM decide?
Decision asset · precision spindles
Custom gas-static spindle pre-RFQ decision checklist.
Use this before committing detailed CAD, a supplier brief or high-fidelity CAE. It does not calculate a spindle; it tests whether the decision basis is mature enough to brief downstream engineering without hiding architecture uncertainty.
Pre-RFQ readiness
Make the machine decision explicit before the supplier brief becomes the architecture.
The checklist stays upstream of detailed design. A checked box means the item is explicit enough to challenge, not that the engineering result has already been proven.
A · Machine decision
Make the decision explicit before turning it into geometry.
B · Operating envelope
Bound the machine state that the architecture must survive.
C · Machine / shaft constraints
Preserve the machine context instead of freezing a bearing in isolation.
D · Rotor / support consequence
Carry the support state into the spindle-level consequence.
E · Evidence path
Name the proof before commissioning the proof.
Prefer a printable working copy?The PDF contains the same 15 checks plus a supplier-independent handoff template and stop conditions.
Download PDFsupplier-independent handoff
What the pre-RFQ brief should contain.
A good RFQ does not hide architecture uncertainty inside supplier assumptions. It makes the decision, controlled state and unanswered proof questions visible.
Operating envelope
Speed, duty, loads, gas state, accuracy/process constraints and packaging limits.
Controlled architecture basis
Support type, shaft-line context and which geometry/state variables remain open.
Input provenance
Measured / specified / assumed / unknown, with units and source.
Decision-changing questions
Which discrepancy, margin or uncertainty must detailed work resolve?
Acceptance / evidence boundary
What evidence is required before freeze, prototype commitment or release?
Stop conditions
Do not freeze the brief while these remain hidden.
These are not automatic failure conditions. They are signals that the architecture question is being transferred downstream instead of resolved.
A finished CAD model exists, but the governing machine decision is still undefined.
A supplier quote is requested before the OEM has a supplier-independent architecture basis.
One stiffness value or one critical speed is treated as the complete rotor-system answer.
CFD / FE is planned without naming the operating state, discrepancy or decision it must resolve.
Acceptance evidence is discussed only after prototype hardware is already committed.
The supplier brief contains geometry but not the acceptance or evidence boundary.
The project is live, but the architecture or proof path is still uncertain?
Start with non-confidential machine facts. The Fit Check contains no numerical design work and determines whether a bounded Architecture Screen is justified.