Bearing definition
Selected support geometry, feed architecture, clearance and the state to which the result applies.
AURA Engineering Platform · method behind the work
One controlled design basis from machine requirement to evidence.
AURA is the structured engineering platform behind the Architecture Screen. It connects process requirements, direct or inverse bearing work, bearing–shaft candidate state, rotor consequences and targeted external CFD / FE evidence without turning those tools into separate decision islands.
In business terms: one controlled decision path that shows what can proceed, what should be rejected and what evidence is still missing before commitment.
INPUTProcess requirementLoads · speed · envelope · accuracy · gas supply
CANDIDATEBearing + shaft stateGeometry · support state · shaft line · operating identity
EVIDENCETargeted verificationRotor consequence · CFD / FE · decision boundary
Direct + inverseAnalyse defined geometry or synthesise from required behaviour.
System-level handoffBearing state remains connected to shaft and rotor consequences.
Evidence-gatedAnalytical, CFD, FE and test claims keep explicit boundaries.
Decision memoryAccepted and rejected candidate states keep their rejection or acceptance reason inside the project record.
Controlled decision object
AURA returns an engineering candidate, not an isolated number.
The candidate contains bearing definition, shaft-line context, operating-state identity, physical result, rotor consequence, evidence level and the next allowed decision.
Shaft-line context
Span, material, drive and working-tool interfaces remain attached to the same candidate identity.
Operating-state identity
Load, speed, gas supply, clearance and adjustment state stay explicit rather than becoming hidden assumptions.
Physical result
Capacity, stiffness, flow and other calculated quantities are reported with their model and applicability boundary.
Rotor consequence
The selected support state is carried into mode-family, response and stability decisions when system-level verification is required.
Evidence boundary
The package states what is supported now, what remains unproven and the smallest next proof that can change the decision.
Connected chain
AURA keeps the subject-matter chain connected across ten engineering objects.
The differentiation is continuity: relationships that usually disappear between requirements, bearing tools, rotor models, external CAE and evidence records remain attached to the same candidate identity.
Decision chain · executive view
Requirements
Define the machine duty and acceptance boundary.
Inverse synthesis
Search feasible support states and reject weak options.
Bearing / shaft state
Freeze one controlled candidate basis.
Rotor consequence
Carry that state into system dynamics.
Targeted CFD / FE
Verify only decision-critical uncertainty.
Evidence boundary
Name what is proven and what remains open.
Decision
Proceed, reject, revise or commission next proof.
UNDER THE HOODThe ten technical objects below are how AURA maintains this continuity in practice.
01
Process requirements
Machine duty and acceptance boundary before geometry is fixed.
02
Inverse gas-bearing synthesis
Candidate supports generated from required behaviour.
03
Bearing–shaft candidate
Support and shaft parameters remain one object.
04
Adjustable conical pair
Controlled support changes stay inside one state identity.
05
Support impedance
Frequency- and state-dependent support behaviour.
06
Mode-family envelope
Tracked rotor branches instead of one critical number.
07
Robust rejection
Weak candidates removed before expensive CAE.
08
CFD / FE reconciliation
Detailed evidence returned without solver lock-in.
09
Requirement-to-test traceability
Assumptions and evidence stay attached to the candidate.
10
Candidate memory
Accepted and rejected states remain available for reuse.
Selective detailed verification
External CFD and FE answer a question already defined by the system model.
High-fidelity work begins only after analytical screening has narrowed the design space and named the exact state and discrepancy to resolve. AURA reconciles the resulting evidence; it is not presented as the CFD or FE solver.
Bring one live machine requirement into the decision chain.
Start with the Architecture Screen. AURA is the engineering method behind the work, not a detached software demo.