01 · Machine
Recorded operating basis
The machine purpose, original support architecture and documented operating behaviour define the engineering question.
Architecture & Evidence Package
Carry a screened architecture into a deeper controlled evidence package.
This deeper engagement starts after the decision and scope are defined. AURA carries the selected architecture through calculation, spindle/rotor consequence and targeted evidence work while preserving assumptions, provenance and release boundaries.
Reconstruction and method chain
Machine → geometry → pressure solution → support reactions → spindle dynamics → industrial check.
The pilot does not start from an isolated solver image. One controlled operating basis is carried from the machine question through the bearing state and rotor consequence, then compared with the evidence that actually exists.
02 · Geometry
Reconstructed geometry
Cone angle, clearances, restrictor layout and surrounding architecture are made explicit before the physical state is calculated.
03 · Pressure solution
Base-state gas-film field
The defined bearing state is solved over the conical support surface; the field is evidence for the next physical quantities, not the endpoint.
04 · Support reactions
Pressure becomes engineering support state
Integrated pressure is converted into radial, axial and moment reactions together with the support coefficients required by the spindle model.
05 · Spindle dynamics
Support state enters the machine model
Equivalent stiffness and damping are carried into the spindle model to screen response, critical states and operating consequences.
5–10%reported deviation
Applies only to the documented ALMAZ prototype and recorded operating basis. It is not a universal error bound.
06 · Industrial check
Calculated behaviour is checked against the documented basis
5–10% reported deviation applies to the documented ALMAZ prototype and recorded operating basis. It is not a universal error bound.
Review the ALMAZ case →How the engagement runs
Four controlled stages keep the decision and the evidence aligned.
The engineering chain above describes the subject matter. The pilot itself is managed as a bounded engagement with an explicit decision question and release boundary.
Scope the decision
Define the machine, operating basis, alternatives and the decision the pilot must support.
Build the controlled case
Align geometry, units, support state, loads, speed range, assumptions and available validation evidence.
Calculate and compare
Run direct calculation or inverse synthesis, configure the spindle and screen critical speeds, response and stability.
Deliver the decision package
Record results, provenance, operating state, evidence status, unresolved gaps and the next allowed action.
Inputs needed
Start from controlled machine facts.
- Machine purpose and architecture
- Operating and maximum speed
- Available shaft, tool and support geometry
- Loads, moments and performance targets
- Supply pressure, gas state and clearance limits
- Known test, benchmark or measurement data
- The engineering decision to be made
Deliverable
One package, with the boundary stated.
- Controlled input and assumption record
- Direct calculation or inverse synthesis result
- Drive Unit → Shaft → Tool → Supports configuration
- Load, flow, stiffness and damping outputs
- Critical-speed and response evidence
- Candidate comparison where included in scope
- Decision status and recommended next engineering action
Commercial structure
The scope is fixed before detailed work begins.
A written scope fixes the case, inputs, outputs, exclusions, milestones, responsibilities and the engineering decision. A narrower Architecture Screen is used when one defined decision can be closed first.
Written one-page basis
Case, inputs, outputs, exclusions, milestones and decision question are agreed before modelling begins.
Controlled handoff
The client receives the agreed report package, controlled case inputs and a clear basis for the next design, test or review decision.
Confidentiality before files
Confidential files move only after written terms. Client background IP remains client IP; AURA platform IP remains with Breshev Engineering.
Read the data-handling basis →Frequently asked questions
Bound the work before adding modelling depth.
Does a pilot require a complete CAD model?
Not always. A feasibility or architecture case can begin with controlled dimensions, loads, operating conditions and geometry limits. Higher-authority conclusions require correspondingly stronger geometry and evidence.
Does AURA replace prototype testing?
No. The pilot identifies what calculation supports, where the evidence boundary lies and which test would reduce the most decision-critical uncertainty.
Can the work start under NDA?
Yes. NDA and project-specific data-handling terms can be agreed before confidential geometry, reports or test data are transferred.
What happens if the case is not a fit?
The scope discussion stops before engagement. No confidential files are needed for the initial fit check.
Low-friction first step
Describe the machine and the decision.
Do not attach confidential files at this stage. Machine type, RPM range, constraints and the decision you need are enough for the first fit check.
AURA product / pilotaura@breshevengineering.comDirect founder contactoleksii@breshevengineering.comOleksii on LinkedIn ↗
This is the same Breshev Engineering project-request form used by the Architecture Screen. No file upload is enabled at the first-contact stage.