Understand auto-generated technical recommendations

This article explains how BriqSafe automatically creates technical recommendations when asset parameters indicate compliance issues and how to work with these recommendations. It is intended for engineers and inspectors involved in risk assessments and asset management.

Note

Required role: Engineer for entering parameters; Inspector for reviewing recommendations; Manager for scheduling.

Entering Asset Parameters and Generating Recommendations

Technical recommendations are automatically created when asset parameters show values that exceed compliance thresholds.

1. Open the asset and go to the Parameters section.
2. Enter parameter values in the dynamic form, which depends on the asset type.
3. Each parameter row displays its value and a badge indicating Satisfactory or Unsatisfactory.
4. Out-of-range parameter values cause the asset's state to become unsatisfactory.
5. The rule engine evaluates all parameters and derives the asset's overall satisfaction state.
6. When a parameter breaches a threshold linked to a risk rule, the system automatically creates a draft technical recommendation associated with that parameter.

Note: Changing an asset’s type after entering parameters can invalidate the data. Also, an asset must be linked to a system to generate activities from recommendations.

Understanding Auto-Generated Draft Technical Recommendations

When a parameter reading crosses a regime-specific threshold, the system raises a draft recommendation for review.

1. Open the asset and select the Technical Recommendations tab.

2. Locate drafts under the Drafts (auto-generated) section. Each draft carries an Auto-generated badge and a Needs Approval status.

3. Open a draft to view:

   • The Problem description
   • The suggested Solution
   • The Priority
   • The Triggered by panel listing the parameter values causing the threshold breach.

4. Drafts are proposals only and have no effect until approved or dismissed.

Note: The same parameter breach on the same asset does not create duplicate drafts; the system reuses the existing draft unless a different rule or asset triggers a new one.

Reviewing, Approving, or Dismissing Draft Recommendations

Reviewers confirm whether auto-generated drafts should become active work or be discarded.

1. Open the draft recommendation to launch the Review recommendation dialog.
2. Edit the Problem, Solution, and Priority if necessary.
3. Select one or more Suggested activities describing the corrective work. At least one is required to approve.
4. Click Approve or Update & review to confirm. The status changes to Approved, recording the approver and time.
5. Alternatively, select Dismiss, enter a reason of at least 10 characters, and confirm. The status becomes Dismissed.

Important: Approving or dismissing requires edit access. These actions are only available in the web app, not mobile. Re-approving an already approved item does not apply changes. Deletion is a separate, manager-only action with a soft delete preserving audit history.

Scheduling Approved Technical Recommendations

Only approved recommendations can be scheduled as one-time follow-up jobs for onsite correction.

1. Open the location’s Recommendations tab.
2. Select the approved recommendations to schedule.
3. Add them to the control scheme as one-time activities.
4. In the Scheduler, assign a date and an engineer to create the visit carrying the follow-up job.

Note: Scheduling requires separate Manager-level permission. Scheduling creates jobs but does not alter the recommendation details. Technical-recommendation activities do not recur.

Automatic Closure of Recommendations

An approved recommendation closes automatically when all its suggested activities have linked completed jobs.

1. Complete each follow-up job as scheduled.
2. The system checks the linked recommendation after job completion.
3. When every suggested activity has a completed job, the recommendation status changes to Closed automatically.

Note: Partial completion does not close the recommendation. A manual close action is not required but can be forced with proper permissions if work was verified outside the system.