Faults

Faults are used to document component or system failures and non-conformances. Each fault belongs to a parent project, but faults are not typically presented on a per-project basis due to the frequency of cross-project component reuse.

Scope

Faults are intended to represent a single instance of a failure. For example, if a prototype main bearing fails, an engineer may log a fault titled:

Cracked Prototype Main Bearing

The fault entity would then be used to describe the failure, including the upload of associated media.

As with tasks, faults support collaboration and discussion functionality, and any discussion relating to the failure should take place on the fault.

Fault Statuses

By default, faults can take one of two statuses:

1. Open
2. Closed

When a new fault is logged, it assumes the Open status. To reach the Closed status, a fault must first be reviewed in-line with the workspace review and approval configuration, then its status can again be modified via the task page or a task board.

Customisation Options

In keeping with both our considered opinion on engineering operations and our preference for opinionated software, the default fault status options are fixed. However, it is technically feasible to customise these options on a per-workspace basis.

If you would like to discuss product tailoring options, please contact us.

Fault Severities

By default, faults can take one of three severities:

1. Low
2. Medium
3. High

Fault severity must be assigned during fault creation, and can be modified via the fault page.

info

The default severity configuration will soon change to align with MIL-STD-882E.

Customisation Options

In keeping with both our considered opinion on engineering operations and our preference for opinionated software, the default task priority options are fixed. However, it is technically feasible to customise these options on a per-workspace basis.

If you would like to discuss product tailoring options, please contact us.