Skip to content
Breshev EngineeringAURA Engineering Platform

Engineering solution

Track rotor behaviour with every bearing and operating state attached.

Carry state- and frequency-dependent support impedance into the shaft model, track physical mode families across speed and uncertainty, and preserve provenance to the final decision.

The engineering question

Does the selected bearing–shaft system remain dynamically acceptable over speed, supply, load, thermal, tolerance and adjustment states?

Inputs

  • Shaft geometry, material, mass and inertia
  • Support positions, orientation and interfaces
  • State- and frequency-dependent bearing impedance
  • Operating speed range and excitation orders
  • Unbalance, tool and drive forcing basis
  • Operating-State Key and evidence provenance

Outputs

  • Tracked lateral mode families and branch identity
  • Critical intersections and worst separation
  • Synchronous response and orbit where scoped
  • Damping and stability indicators
  • State-by-state decision and evidence basis

Decision basis

The first lateral family is one physical family: an X/Y near-degenerate pair at zero speed that can split into forward/backward branches at speed. AURA tracks that family across states instead of presenting two unrelated “Mode 1” frequencies.

Typical commercial route

Use the Architecture Screen for one defined machine consequence. Use the AURA Pilot or Evidence Review when coefficient provenance, coupling maturity or validation basis is the main issue.

Relevant proof path

Inspect the capability, evidence and expected handoff.

EVIDENCE

Coefficient passport

Review a public record or technical basis relevant to this engineering question.

Open supporting material →
DELIVERABLE

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.

Review Architecture Screen