Project overview

The project overview is one page that sums up the whole project. It shows the assembly as a small 3D picture, the checks closest to their limits with a way to fix each, what changed since you last saved, every component's governing utilisation, the power flow of a gearbox, the duty cycle, every validation warning, the project's details and its parts list, and then every module and component with its status, governing check and key results. Use it to see at a glance what needs work before you open a module, and to move to the component that governs.

The overview has no inputs of its own. It reads the same results as the modules and changes as soon as a solve finishes.

Opening the overview

Choose Overview at the top of the navigation, in the Project group.
To open every project here, open File › Settings and set Open projects in to Project overview. A project opens in the chosen module when it has something there; otherwise it opens in the shaft.

While a solve runs the page says "Solving…" at the top; the last results stay until the new ones are in. A project with nothing in it yet shows Nothing to sum up yet.

What the page shows

The page is a grid of cards: two columns on a wide window, one on a narrower window or a phone. Every card can be reached with the keyboard, and every value is written out, never shown by colour alone.

Header and assembly picture

The header carries the project's name and description and a tally of the components by status: how many pass, and, when there are any, how many are close to their limit, fail or are not computed.

Beside it, a small live 3D picture shows the whole assembly with its parts coloured by their checks, as the Assembly module does. It only looks: it does not turn or pick parts. Select it (or press Enter on it) to open the Assembly module. The 3D view loads only when the picture scrolls into view, draws only while it is in view and the window is shown, and turns its gears only then and when your system does not ask for reduced motion. A project with nothing to put together (no shaft and no gear set, such as a single bearing) has no picture.

Quick actions

Calculation report: the printable report, as File › Report (Ctrl+Shift+P). See Reports and export.
Export the shaft as STEP: the shaft shown in the shaft module as a STEP solid, when the project has a shaft.
Optimise: the design search. It is off for a read-only project.

Totals

Total	Meaning
Checks passed	Checks of the whole project that pass, "of" the total number of checks.
Checks failed	Checks that fail. The tile is highlighted when this is not zero.
System life	The combined rating life of the bearings on the shafts (modified, with the basic life below), shown when there are two or more.
Power loss	All losses: the bearings' friction and the gear mesh and drive losses, each shown below, with the power transmitted when it is known.
Efficiency	Output over input power with all losses, bearings included, when the project has a power path. Below it, the efficiency of the gears and drives alone, as the power flow shows it.

The totals count every check of the project, including checks that belong to no single component.

Needs attention

The five checks of the whole project with the highest utilisation, the highest first: a failing check comes before every passing one. Each line names the component and what is checked, shows the utilisation as a bar and in %, its status chip, the engine's sentence about the check and, where the engine has one, What helps: what would fix it (for example "a wider face, a larger centre distance or module, or harder flanks" for a gear's pitting safety).

Open opens the component where it is edited.
Suggest a fix is there when the assistant is available to you. Where the design search can change what governs the check, it opens Optimise set up for it: for a check of the shaft shown first, the lightest shaft (its section diameters, up to 30 % larger, not the bearing seats); for a bearing's life or static safety, the smallest outside diameter among the sizes of the same bore; for a gear pair's pitting or tooth root safety, the narrowest face width. Each search aims for 80 % of the limit (a minimum at the limit / 0.8), below the 85 % at which a check counts as close, so that the check it finds no longer reads as Close to limit. Nothing runs until you choose Search. Where no search fits (a speed check, another shaft, bolts, the other modules), or the design search is not available to you, it opens the assistant with a question in its message box, for example "BR1's modified life is at 92 % of its requirement: what are my options?", with the check and the engine's hint. The question is not sent until you send it.

Components that could not be computed are listed below under Not computed, with the reason. When every check passes with margin, the card says so (none above 85 % of its limit).

What changed

One line comparing the project with its last save, for example "Since the last save: 2 checks flipped, BR1 life −31 %": how many checks went from pass to fail or back, and the result that moved most. Before the first save, a project opened from a file, the cloud or an example is compared with how it was opened ("Since it was opened: …"); a new project says "Not saved yet". Details opens the whole comparison: the checks that flipped or moved, the results that moved with their change, and every input that differs, old → new in the units shown. It is the same comparison as axm diff.

Project details

The customer, part number, project number and report number and the latest revision of the history (with its date, who made it and its description), as the report screen's Document section keeps them with the project (see Document control). Edit in the report settings, or Add details in the report settings while the project has none, opens the report screen at that section. Below them: when the project was last changed and by whom (you, the assistant or another program, with the change), or when its file or cloud copy was last saved; which Axomek wrote the file; and where it is: the file (with Show in folder in the desktop app), the cloud project, or "Not saved yet".

Utilisation

A bar chart with one bar per component, its governing check's utilisation, the highest first; 100 % is the limit, marked by a line. The bars are named by the components' ids; the list below the chart gives each component's name, its utilisation in % and its status in words. Select a name to open the component.

Power flow

For a project with gear pairs, belt or chain drives or planetary sets: the power from the input through each stage to the output, as a diagram. Each shaft (or member) shows its speed n, torque T and power P; each stage between them its ratio i and efficiency η. Under it, the overall ratio, efficiency and loss. Show as a table gives the same as a table, one row per stage, each stage's name opening it.

Stages follow each other along the shafts: a stage whose driving gear or pulley sits on the shaft another stage drives comes after it. Each stage is shown as it is rated, at its own torque and speed: the driven member gets T·u·η at n/u. The overall efficiency under the diagram is therefore the gears' and drives' alone, the product of the stages' η. A second line adds the friction of the bearings on the train's shafts and gives the efficiency with all losses. For a project with one train, that is the Efficiency of the totals. When a stage takes in another speed or torque than the stage before it puts out, a note says so. A planetary set's losses are not computed, so its efficiency (and its train's) reads "not computed". Stages of modules that are not available to you are left out.

Duty cycle

For a project with load cases: each case's share of the time, its load factor and the share of the fatigue damage it causes in the bearing with the shortest combined life, the case with the most damage marked governing. Below, that bearing's combined modified life and the load case in which the shaft strength is weakest.

Warnings

Every validation error and warning of the project, errors first, each with its path, the engine's message and hint, and Open to go where it is edited.

Modules

One card per module with content, in the order of the navigation. Each card shows:

the module's name and the number of components, for example "2 shafts" or "1 gear pair";
a status chip (see the table below);
the module's governing check: the value, its limit (or minimum), what is checked and on which component, and a bar filled to the utilisation;
"No limits set: results are shown without checks." when the module has results but no limits, or "No results yet." when nothing could be computed.

Select a card to open the module on its governing component (or its first one).

Components

A table with one row per component, grouped by module:

Column	Content
Component	The component's id and name. Select it to open it where it is edited.
Status	The status chip.
Governing check	The check with the highest utilisation, its value and its limit or minimum. When there is no result, the reason the engine gives.
Utilisation	Value over limit for a maximum, limit over value for a minimum (a safety or a life), in %.
Key results	Up to three results: for a shaft the max deflection, max stress and 1st critical speed; for a bearing the modified life, the static safety s0 and the max contact stress; for a gear pair the ratio, the mesh efficiency and the tangential force; for a fit the fit type, the joint pressure and the torque capacity. Other modules show their own main results or the checks closest to their limits.

Parts list

The project's parts: one row per kind of part with its quantity, designation, what it is (and the items it comes from), material and mass of one. Shafts, bearings, the pinion and wheel of each gear pair (and the gears of planetary sets, bevel, worm and plastic pairs), bolts with their nuts, parallel keys, belts and chains with their pulleys, rotors, springs, ball screws and linear guides; identical parts share a row. A mass is computed from the geometry and the project's density (shafts, springs), estimated in steel (keys, and bearings from the boundary dimensions of the preset their designation names, with the share of the ring section a bearing of that type fills: an estimate, within about 10 % of typical catalogue masses) or given where the project has it (a gear's or pulley's mass on its seat, a rotor's mass). A bearing whose designation is no preset's shows "unknown". Export CSV saves the list as a CSV file for a spreadsheet (masses in kg), as axm parts --csv prints it.

Status chips

Chip	Meaning
Pass	Every check passes with a utilisation of 85 % or less.
Close to limit	Every check passes, but at least one is above 85 % of its limit.
Fail	At least one check fails.
No limits set	Results exist but there is nothing to check them against.
Not computed	The component could not be solved; the governing check column gives the reason.

A module takes the worst status of its components.

The threshold is the one of the checks banner in each module's results column, of the Projects screen's Close to limit filter and of axm summary.

Example: the two-stage gearbox

Open the example and choose Overview. The engine gives:

Item	Value
Checks	42, all passing
Components	3 shafts, 6 bearings, 2 gear pairs
Highest utilisation	pitting safety of the pinion of G2, 62.5 %
Power flow	input shaft 1450 rpm, 60 N·m, 9.111 kW; G1 i 3.526, η 99.39 %; intermediate shaft 411.2 rpm, 210.3 N·m; G2 i 2.941, η 99.11 %; output shaft 139.8 rpm, 612.9 N·m, 8.974 kW
Overall	ratio 10.37, gear and drive efficiency 98.5 %, loss 137 W
With the bearings	the six bearings' friction 42 W: all losses 179 W, efficiency 98.04 %, as in the totals
Parts	13 parts in 11 rows, 34.93 kg known; the 6 bearings' masses estimated

Every check passes with margin. The overview rounds these values to three or four significant figures.

Limits and what is not shown

The overview reports what the modules compute. It has no checks of its own: a component without limits shows No limits set, never Pass.
Modules that are not available to you are left out of the page, and out of the power flow.
A component whose inputs are invalid shows Not computed; nothing computed from invalid inputs is shown as passing.
The fix hints say what kind of change helps a check, not by how much: the check's message says how far it is from its limit.

From the command line

axm solve prints every check with its utilisation, the system life and the power loss; axm diff compares two projects; axm parts prints the parts list (--csv for a spreadsheet).

axm new box.axm.json --template gearbox-two-stage
axm solve box.axm.json
axm parts box.axm.json --csv > box.parts.csv