Engineering Use Notice

Last updated: September 8, 2026

Read this before running your first analysis in Paraxis Console.

1. What an analysis result is

Each result is produced by a named analysis module of the Paraxis engines against the inputs recorded with the run. The run record stores the engine version, the input hash, the request, the verdicts and the module's assurance statement at the time of the run.
Assurance is stated per module: maturity (experimental, preliminary, engineering-checked, validated) and validation status (not evaluated, internal verification, reference-compared, independently validated). Both are shown on the result and on the Model and Validation page.

A result is not a certified engineering analysis. Unless a module is marked validated with an independent validation record, it has not been independently validated.
A result is not a substitute for the judgement of a qualified engineer, for a test, or for the applicable standards and regulatory requirements of your program.
Results must not be the sole basis for a flight, safety, procurement or contractual decision.

Check the inputs. Provisional and default values are marked as such in the run record.
Check the assurance statement and the known limitations of each module you rely on.
Keep the run record with any design decision it supports; exports carry the run identifier and engine version.

If a result looks wrong, use the in-product feedback control on the result or write to the address on the Security page. Include the run identifier.