Skip to content
Breshev EngineeringAURA Engineering Platform

Architecture Screen

Clarify the spindle architecture and proof path before CAD freeze or supplier commitment.

A bounded engineering engagement for a live custom gas-static spindle decision. It makes the operating envelope, assumptions, feasible options, governing risks and next required proof explicit before downstream cost is committed.

Bounded engineering engagementNot a production-release sign-off, supplier-selection mandate, manufacturing quote or free preliminary calculation.

At a glance

The decision boundary before detailed engineering.

WHENBefore CAD freeze, supplier commitment or expensive proof.
WE DOScreen operating states, support architecture and rotor consequence.
YOU GETFeasible options, governing risk, rotor consequence and the next proof.
BOUNDARYScreening is not manufacturing release or final acceptance.

See the actual output

A bounded engineering decision, not a pile of calculations.

The public sample shows how one controlled case carries the operating state, support result, rotor consequence, evidence boundary and next action in one decision package.

Operating state20,000 RPM
First critical family29,780 RPM
Separation48.9%
AuthoritySCREENING ONLY
See the sample decision package
Public Architecture Screen decision record showing physical screening status, separation margin and evidence boundary
Public controlled sample.Illustrates deliverable structure and evidence authority; it is not a customer-specific guarantee.
When to engage

A custom gas-static spindle decision is live.

The architecture or proof path is still uncertain and the next commitment would make change more expensive.

What you receive

A bounded decision package.

Assumptions, feasible options, governing risks, sensitivities and the next required proof.

What we need

Non-confidential machine facts.

Machine/process context, speed, loads, envelope, gas state and the decision to be made.

What it is not

Not a release or supplier mandate.

No production-release sign-off, certification, manufacturing quote or free numerical design work.

Architecture decision

Which spindle architecture is defensible enough to take forward — and what must be proved next?

The Screen stays upstream of detailed CAE. Its purpose is to reject weak options early, expose the governing operating state and define the smallest downstream proof that can still change the decision.

01

Process envelope

Loads, speed, accuracy, duty, gas supply and packaging.

02

Candidate synthesis

Direct calculation or inverse search across feasible support states.

03

Shaft-line context

Bearing placement, span, material, drive and tool interface.

04

Robustness

Worst operating corner, margin and rejected alternatives.

05

Rotor consequence

Mode-family separation, response and stability screen.

06

Next proof

What detailed CFD, FE, tolerancing or test must establish.

Architecture Screen output

A bounded architecture decision package, not a pile of plots.

Inputs, assumptions, candidate identity, numerical result, rejected states, evidence boundary and next action remain in one controlled handoff.

01 · Candidate

Selected bearing–shaft state

Geometry, restriction, clearance, supply state, shaft-line context and operating point.

02 · Consequence

Physical and rotor result

Capacity, stiffness, flow, margins, critical-speed family and response screen.

03 · Decision

Risk and next proof

Weak states rejected, open questions named and the next engineering action stated explicitly.

Engagement boundary

Architecture Screen versus Architecture & Evidence Package.

The first engagement decides what is worth carrying forward. The deeper package begins only after an architecture has been screened and a higher-authority proof path is justified.

01

Architecture Screen

What should continue?
Project state
Architecture still open.
Main question
Which option is defensible enough to take forward?
Output
Candidate, governing state, rotor consequence, rejected options and next proof.
Authority
Screening / architecture decision.
Typical next step
Supplier brief, targeted CAE/test, or deeper engineering package.
Inspect sample output →
02

Architecture & Evidence Package

What must now be proved?
Project state
Architecture already screened.
Main question
Which evidence must close the remaining decision risk?
Output
Controlled deeper analysis, evidence tasks, configuration basis and closure logic.
Authority
Scope-defined higher evidence; not automatic product release.
Typical next step
Validation, acceptance pathway or controlled design iteration.
Review the deeper package →

Project Fit Check

Start with the decision, not a full specification.

Use the on-site form for high-level, non-confidential context. The first response establishes fit, missing inputs and the appropriate engineering scope before any proprietary files are exchanged.

01Decision context

Machine/process, decision, speed range, stage and work email. No CAD or proprietary files.

02Fit & scope response

Breshev Engineering identifies the right engagement, data gaps and the evidence authority required next.

Before submitting factsPre-RFQ Decision Checklist

Expose missing decision inputs before they become supplier or CAE assumptions.

Open checklist →
Before promoting the resultArchitecture Screen stop boundaries

See when screening must stop and higher-authority evidence is required.

Open boundary map →
Before ordering detailed proofOperating State → Acceptance Evidence

Name the targeted CFD, FE, test or metrology quantity and closure rule first.

Open evidence map →

Project request · on-site form

Send the decision context. No CAD or proprietary files.

Use high-level, non-confidential facts only. The first response establishes fit, missing inputs and whether an Architecture Screen or a deeper evidence package is justified.

Data handling / NDA →

No file upload is enabled on this form. Confidential geometry, drawings and test data move only after scope and data-handling terms are agreed.