AURA Engineering Platform
AURA Services · Fixed scope

Balancing Evidence Review

A fixed-scope, one-week engineering review of the balancing evidence behind one high-speed rotor: tolerance planes, correction mapping, process capability, vector repeatability, assembly transfer, modal sensitivity, operating-envelope limits — and what the residual imbalance number is actually allowed to prove.

The problem this addresses

The cheapest moment to catch a gap is before metal is cut and fixtures are made. Balancing evidence is most valuable when it is connected upstream to design review, manufacturing route, fixture strategy, assembly state, and operating envelope — not treated only as an end-of-line check.

A rotor can meet its residual-imbalance grade and still carry unexamined risk. The grade is one number; the evidence is everything behind it — why that grade was chosen for this rotor and this consequence, what the rotor's manufacturing state was before balancing, how the correction was achieved, whether component-level balance survives assembly, and what the high-speed vibration and orbit behaviour actually confirm, and whether the customer-site operating conditions stay inside the intended design envelope. In most teams that evidence lives in one experienced engineer's head. This review puts it on paper.

What you get

One rotor case, reviewed end to end: balance-grade selection basis, tolerance-plane allocation, correction and measurement-plane mapping, component-vs-assembly state, machine setup, and operating-envelope assumptions.
Capability and evidence-floor check: whether the machine-process-rotor combination has demonstrated the minimum achievable residual, reduction ratio, plane separation, angular capability, and repeatability needed for the requested tolerance.
Transfer and modal check: whether component balance survives assembly, whether incremental correction separates transfer unbalance, and whether rigid/flexible behaviour and the complete speed path are supported.
A written evidence map: what is currently supported by evidence, what is assumed, and what is unverified — laid out against the AURA balancing evidence trail.
An explicit boundary statement: what the current residual-imbalance evidence does and does not prove for the release decision this rotor is facing.
One follow-up call to walk through the findings and their implications with your team.

What this is not

Not a recalculation service. The review examines the evidence structure behind your existing numbers; it does not redo your balancing or your bearing calculations.
Not a replacement for your balancing shop. It makes the reasoning behind their work explicit and reviewable — it does not compete with it.
Not a generic report. The output is specific to one rotor, one operating context, and one release decision.
Not a forensic failure investigation. Customer-site overload and operating-envelope mismatch can be reviewed only from the evidence supplied; this service does not certify field operation or assign legal responsibility.

How it works

STEP 1RequestSubmit the request form with a short description of the rotor and the decision it is facing.
STEP 2Scope callA short call to confirm the case fits the fixed scope and agree what data is needed.
STEP 3Review weekOne week from receiving the case data: evidence map and boundary statement are prepared.
STEP 4WalkthroughFindings call with your team. You keep the written evidence map.

Useful input data

Balancing evidence: balance grade, total permissible and measured residual vectors, tolerance/correction/measurement plane coordinates, allocation rule, correction history, and balance report.
Capability evidence: machine/configuration identity, minimum achievable residual, reduction-ratio evidence, plane separation, angle accuracy, filtering, runout handling, and repeated-run vector spread if available.
Rotor context: rotor speed range, operating RPM, approximate rotor layout, support architecture, intended duty cycle, and known critical-speed or vibration information.
Assembly context: component identities, angular indexing/clocking, fixtures or dummies, bearings, interfaces, adapter state, reassembly controls, and any before/after assembly measurements.
Operating envelope: intended loads, customer-site conditions, process loads, thermal limits, overload concerns, and any observed vibration/runout symptoms.

Price and scope

€1,900fixed price · one rotor · one week from case data

If the case does not fit the fixed scope, that is said plainly on the scope call — before any commitment, not after.

Request a review See a sample report Read the methodology — TN04 Release Evidence Field Guide
This review covers balancing, assembly, capability, and speed-path evidence for high-speed precision rotors. It draws on the published AURA evidence-gate methodology (Technical Notes 01–05 and Release Evidence Field Guide v1.1) and does not require disclosure of the proprietary engineering engine. It is an engineering review, not a certification, and does not replace the reviewing organisation's own release authority.