Skip to content
Breshev EngineeringAURA Engineering Platform
AURA Technology

Release evidence for gas-bearing rotor systems.

AURA does not treat a bearing coefficient as a free-standing answer. It asks what that number is allowed to prove after geometry, clearance, thermal state, balance process, rotor dynamics, validation scope, and decision limits are considered.

AURA release-evidence category

Many calculation tools stop at coefficients. AURA keeps the coefficient basis and decision basis attached.

That is the difference between a calculation result and release evidence. The goal is not to expose the full solver. The goal is to make the evidence surface inspectable: provenance, residuals, applicability boundaries, and explicit claim limits.

What release evidence means

RequirementsMachine loads, speed range, precision target, environment.
GeometryBearing family, clearance state, cone/journal/thrust layout.
CoefficientsK/C matrices with method provenance and scope.
DynamicsCritical speed, whirl margin, orbit/runout, vibration risk.
ValidationRegistry anchors, residuals, leakage audit, applicability limits.
DecisionPASS / REVIEW / SCREENING ONLY / freeze boundary.

A clean number can still have weak decision authority. AURA separates physical calculation from release permission.

Why coefficients alone are not enough

Geometry and clearance: a stiffness value belongs to a manufactured and adjusted clearance state.
Thermal envelope: material growth, distortion, and clearance shift can invalidate a coefficient outside its operating state.
Balance process: the path to a residual imbalance target can matter as much as the final number.
Rotor response: vibration, orbit, critical-speed separation, damping, and whirl margin are release-facing evidence.
Balancing / assembly evidence: the chosen balance grade needs a rationale; the residual must be mapped to the correct tolerance planes; capability and vector repeatability must support the requested limit; and component-level balance does not automatically reproduce at assembly level.
Operating envelope: customer-site loads, process conditions, thermal state, duty cycle, and overload events can invalidate evidence that was valid inside the design envelope.

What AURA records

For a scoped case, the decision package can preserve the evidence path: what was assumed, what was computed, what was compared, what residuals remain, what operating envelope applies, and what the result is not allowed to claim.

Peer-reviewed physical basis

Adjustable conical air-bearing research

The International Journal of Manufacturing Research publication connects the analytical bearing model to adjustable conical support geometry, a rotor dynamic-stability criterion, pneumatic-spindle hardware and full-scale experimental verification. It supports the physical and hardware lineage beneath AURA while preserving a clear boundary: one published design family does not validate every AURA case or operating envelope.

Roadmap evidence gate

Balancing / assembly evidence

A residual-imbalance grade is not release evidence by itself. For high-speed precision rotors, the release question is broader: which rotor regime applies, why the grade was selected, where acceptance is judged, how correction and measurement planes map to the tolerance planes, whether the machine-process-rotor combination can demonstrate the requested residual, whether the vector repeats, whether component-level balance survives assembly, and what the complete speed-path response shows.

Tolerance basisRequirement edition, basis speed, permissible total, plane coordinates, centre of mass, and allocation.
Plane mappingCorrection and measurement coordinates, radii, angular reference, and transformation.
CapabilityMinimum achievable residual, reduction ratio, angle and correction capability, and guard band.
RepeatabilityVector runs across starts, settling, thermal states, and reassembly.
Assembly transferFingerprint, clocking, before/after vectors, fixtures, interfaces, and revision.
Modal speed pathModes, damping provenance, participation, acceleration, deceleration, crossings, and dwell.

Boundary: the evidence model and locked preview are a specified product direction, not yet a shipped production module. They expose the proposed evidence surface without claiming that the live AURA platform already enforces these fields.

Engineering precedents for evidence-gated release

An evidence gate prevents a result from authorising an irreversible step until its basis, applicability and independent confirmation are adequate for the decision. AURA applies this established engineering logic to gas-bearing rotor systems.

Aerospace

Design assurance

Requirements, verification results, configuration identity and applicability limits are assembled into an auditable basis before a result can support release.

Industrial acceptance

Acceptance programmes

Consequential engineering decisions are not authorised by one favourable output. They require configuration control, verification evidence, acceptance criteria and responsible approval.

Rotor systems

Release authority

AURA keeps bearing state, rotor response, balancing, tests, interfaces and operating-envelope evidence attached to the decision they are allowed to support.

Open evidence surface. Closed engineering engine.

AURA is not built around full transparency of the solver. It is built around inspectable evidence without exposing the proprietary engineering core.

Exposed

Evidence surface

Registry, residuals, benchmark anchors, applicability boundaries, technical notes, DOI records, claim boundaries, and decision limitations.

Protected

Engineering engine

Solver implementation, Breshev perturbation-method core, coefficient engine, damping logic, and decision heuristics.

Current fit

Aerostatic / gas-static systems

Precision spindles, gas-bearing rotor decisions, conical/journal/thrust support screening, semiconductor positioning, cryogenic turboexpanders, and adjacent high-speed precision rotor applications.

Scoped application track

Oil-free and hydrogen compressor rotors

AURA can support bearing/rotor architecture, coefficient provenance, dynamic screening, validation-state mapping and operating-envelope transfer. It does not claim complete compressor design, hydrogen-safety qualification or production certification.

Review the application boundary →

Practical rule

A result should not be allowed to support a release decision beyond the evidence envelope that produced it.

This is the category AURA is built around: release evidence for gas-bearing rotor systems.