AURA Engineering Platform logo AURA Engineering Platform

AURA use case

Gas-bearing rotor workflow for precision spindles.

Precision spindle decisions cannot stop at load capacity and stiffness. AURA connects application requirements, gas-bearing support synthesis, coefficient provenance, rotor-dynamic screening, and freeze boundaries.

Good-fit signals

  • Wafer inspection and metrology spindles
  • Ultra-precision machining and inspection rotors
  • Clean, low-friction, low-wear spindle systems
  • Early architecture screening before detailed CAE

Decision risks AURA exposes

  • Damping provenance is weak or proxy-based
  • Cross-coupling is not tracked into dynamics
  • Support spacing or overhang dominates response
  • Manufacturing tolerances are not connected to decision scope

The decision is system-level precision, not bearing load alone

For a precision spindle, the bearing candidate is only one contributor to the final error budget. Rotor overhang, support spacing, tool interface, thermal growth, residual imbalance, structural flexibility, and the chosen operating-speed corridor all act on the same outcome. A stiffness value can be correct and still be insufficient if its clearance state, frequency basis, damping provenance, or connection to rotor response is unknown.

Evidence that must travel together

  • Manufactured geometry and operating clearance
  • Direct and cross-coupled K/C coefficients with provenance
  • Rotor layout, support span, overhang, and mass properties
  • Critical-speed, response, orbit, and stability screening
  • Balance state, tolerance basis, and operating envelope

Questions the package must answer

  • Is the proposed support architecture physically plausible?
  • Does the intended RPM corridor retain adequate separation?
  • Which uncertainty consumes the clearance or response margin?
  • What remains screening evidence rather than release evidence?
  • Which measurement closes the next decision gate?

What AURA produces

AURA does not replace the team's CAE stack, metrology, or prototype testing. It creates a reviewable requirement-to-decision layer that keeps the spindle architecture, coefficient evidence, dynamic screen, validation provenance, and release boundary in the same case record.

1. Requirement basis Speed corridor, load path, precision target, envelope, and failure consequence.
2. Support synthesis Journal, thrust, conical, or combined topology placed inside the real spindle layout.
3. Coefficient ledger Load, flow, stiffness, damping, and cross-coupling preserved with method and evidence status.
4. Rotor response Campbell, separation, Bode, orbit, stability, and clearance-facing screening from the same support state.
5. Decision boundary PASS / REVIEW / SCREENING ONLY with the missing evidence and next test stated explicitly.
Claim boundary: AURA supports scoped engineering screening and decision packages. It does not make a universal production-validation claim without case-specific evidence.