Check why a task is marked as non-compliant

This article explains why a task or asset might appear red (marked as non-compliant) in the BriqSafe web app. It is intended for inspectors, engineers, and others involved in managing asset compliance and risk assessments.

Note

Required role: Inspector or Engineer

Why a Task or Asset Is Marked Non-Compliant

An asset appears red or non-compliant when one or more of its measured parameters fall outside the satisfactory range defined by the applicable control regime. This state is calculated automatically by the rule engine based on entered compliance data.

Understanding Asset Parameter Compliance

To determine the compliance status of an asset, the system evaluates a set of parameters specific to the asset type. Each parameter entry shows its value alongside a badge indicating whether it is satisfactory or unsatisfactory.

1. Open the asset's Parameters section.
2. Enter values into the dynamic form, which is configured according to the asset type.

If any parameter value falls outside the acceptable range, that parameter is flagged as unsatisfactory, causing the asset’s overall satisfaction state to become unsatisfactory (marked red).

The rule engine combines all parameter statuses to derive an overall satisfactory or unsatisfactory state for the asset. When unsatisfactory parameters trigger risk rules, the system auto-creates draft technical recommendations linked to those specific parameters.

Manual Override of Asset Compliance Status

If professional judgement differs from the automatically calculated status, inspectors or engineers can manually override the asset’s satisfactory or unsatisfactory state.

1. Open the asset and go to the Assessment section.
2. Change the satisfactory/unsatisfactory toggle to the desired state.
3. Save by choosing Confirm assessment.

When overridden, a banner appears indicating the assessment has been manually set. The rule engine will not overwrite this manual state during recalculations, so it persists through parameter edits until manually removed.

To return to the automatic evaluation, remove the override in the Assessment section. This reverts the source to calculated and clears the banner.

Note: The asset’s assessment toggle is disabled until at least one parameter assessment has been saved and processed initially.

How Compliance Triggers Cases and Recommendations

When a parameter breaches its threshold, and the associated job is completed, the system evaluates whether escalation is needed.

1. Complete the job normally—even if a reading is out of range (breach does not block completion).
2. The server evaluates the breach post-completion.
3. If escalation is warranted, the app confirms: "Job completed. A case was created for review."

The rule engine raises cases automatically but only one open case per asset-and-rule pair exists at any time. Further breaches on the same asset and rule increase the severity but do not create duplicates while the existing case is open.

Failed sensor readings currently do not auto-create cases; instead, they produce draft technical recommendations.

Reviewing Draft Technical Recommendations

When parameter readings cross regime thresholds, the system auto-generates draft technical recommendations under the asset’s Technical Recommendations tab.

• Drafts carry an Auto-generated badge and show a status of Needs Approval.
• Each draft details the problem, suggested solution, priority, and the triggering parameters.
• Drafts are proposals only and have no active effect until approved by a reviewer.

To approve or dismiss a draft, reviewers select the draft and follow the review dialog, choosing suggested activities, confirming approval, or entering dismissal reasons as needed.

Common Reasons a Task or Asset Is Marked Red

• One or more parameter values exceed acceptable thresholds for its asset type.
• A manual override has set the asset status to unsatisfactory.
• An open case exists for the asset related to a compliance breach.
• Associated follow-up actions or recommendations have not yet been approved or completed.

Additional Considerations

• Changing an asset’s type after entering parameters can invalidate compliance data.
• An asset without a linked system cannot generate activities until linked, even if parameters exist.
• Manual overrides persist through parameter edits and require a user to clear them to return to automatic evaluation.
• Compliance activities and statuses update automatically—there is no manual generation step.
• Completed follow-up jobs linked to a recommendation automatically close it; no manual closure is required.