AURA configuration
See where this solution sits in the connected AURA workflow.
Open product context →Engineering solution
Co-synthesise the bearing set and shaft line from the process envelope.
Select support architecture, shaft geometry and material, span, drive and tool interfaces as one candidate—then test its rotor consequence across operating states.
The engineering question
Which bearing–shaft candidate can satisfy the process envelope with credible static, dynamic, thermal and manufacturing margins?
Inputs
- Forces, moments and application points
- Torque, power and drive/tool mass and inertia
- Speed range, run-up and excitation orders
- Accuracy, error-motion and vibration limits
- Duty, thermal states and gas supply
- Envelope, material and manufacturing limits
Outputs
- Ranked bearing-set and shaft-line candidates
- Support span, reactions and interfaces
- State-dependent support and rotor models
- Tracked mode families, response and stability margins
- Candidate-specific CFD / FE/test handoff
Decision basis
The result advances or rejects a complete system candidate and states what remains screening evidence versus release evidence.
Typical commercial route
A single architecture question can start with the Architecture Screen. A full drive–shaft–tool configuration generally requires an Architecture & Evidence Package.
Relevant proof path
Inspect the capability, evidence and expected handoff.
Spindle result
Review a public record or technical basis relevant to this engineering question.
Open supporting material →Architecture Screen sample package
See how inputs, results, engineering basis and next action are presented.
Open sample output →Bring one defined requirement.
Start with a non-confidential fit check.