New article
Recently updated
Managing specific issue types
Who is this article for?Administrators and Managers who want to learn about managing specific issue types .
Administrator permissions are required to follow some of these steps.
In this article, we delve into the management of specific issue types within Lucidity Incident. Whether you're dealing with non-conformances, hazards, complaints, or improvement opportunities, we'll guide you through the unique fields and processes for each. We'll also explore the critical process of causal analysis, helping you identify root causes and implement effective solutions.
1. Manage Non-conformance
Video: Manage Non-Conformance, Add New Non-Conformance
1.1. Definitions of fields - Non-conformance
| Field | Description |
|---|---|
| Remedial Action Required | Select Yes or No. |
| Proposed Remedial Action Required |
If remedial action is required, select the proposed type of action. For example: rework or replace. |
| Details of Proposed Rectification | Enter the details of the proposed rectification. |
| Client Close Out Required |
When Yes is selected, the option to add the client details appear. Enter the client's name, title, relevant comments, date signed and type name once signed. |
| Designer Close Out Required? |
When Yes is selected, the option to add the client details appear. Enter the designer's name, title, relevant comments, date signed and type name once signed. |
2. Manage Hazard
Video: Manage Hazard, Add New Hazard
2.1. Definitions of Fields - Manage hazards
| Field | Description |
|---|---|
| Are the Hazards Removed or Controlled? | Select Yes or No. |
| Is Incident Report Required? | Select Yes or No. |
| Identify Corresponding Incident Report | If an incident report is required, enter the ID# for the corresponding incident. |
3. Manage complaint
Video: Manage Complaint, Add New Complaint
3.1. Definitions of Fields - Complaint
| Category | Field | Description |
|---|---|---|
| Site Conditions and Activity | Weather |
Select weather conditions at time of complaint (if relevant) For example: hot and overcast, rain etc |
| Wind |
Select wind conditions at time of complaint (if relevant) For example: still, very windy etc |
|
| Visibility |
Select visibility conditions at time of complaint (if relevant) For example: clear, foggy etc |
|
| Water |
Select water conditions at time of complaint (if relevant) For example: cold, hot etc |
|
| Temperature |
Select temperature conditions at time of complaint (if relevant) For example: 10 - 20c, 21 - 30c etc |
|
| Site Operations/ Activities at Time of Complaint | Enter relevant details on all site operations and activities which were occurring at the time of the complaint | |
| Plant and Personnel on Site at Time of Complaint | Enter relevant details on all plant and personnel on site at the time of the complaint | |
| Summary | Summary of Findings | Enter a description to outline findings based on investigating the complaint |
| Complaint Category |
Select the complaint category For example: poor product delivery, lack of training/knowledge etc |
|
| No Basis Found for Complaint | Tick if no basis was found for the complaint |
4. Manage Improvement opportunity
Video: Manage Improvement Opportunity, Add New Improvement Opportunity
4.1 Definitions of Fields - Improvement opportunity
| Field | Description |
|---|---|
| Is the Suggestion to be Implemented? | Tick if the suggestion is to be implemented |
| Note | Add any relevant notes |
5. Causal analysis
Video: Causal Analysis
The causal analysis is not a mandatory part of an issue but it can provide guidance to the individual (typically the responsible manager) completing the investigation. It prompts the consistent approach to the implementation of the hierarchy of controls across the organisation during the investigation process. A causal analysis is completed for the incident and non-conformance issue types. The two issue types typically have separate root causes listed.
To complete a causal analysis, from the Manage page:
- Click Perform Causal Analysis.
-
Select one or more relevant root cause or finding.
Note: Sub-options may appear and also require selection or population.
-
Click Save.
For each selection that has been made, a contributing factor will now be listed on the Manage page. These can be edited at any time.
All contributing factors are reflected in the PDF of the incident and the contributing factors report.
5.1 Linked Actions
Depending on the administration configuration, some contributing factors will create a root cause and have a linked action created automatically, whilst others will only create a finding, resulting in no linked action.
For a contributing factor to be a root cause and have a linked action, the administrator needs to tick the Has Action checkbox in the causal analysis setup. Leaving the checkbox blank results in a finding.
Note: actions created as a result of the causal analysis do not include any actual action text or actionee. The action text, actionee and due date is entered by the person conducting the causal analysis. Refer to the Issue Actions section in this user guide below for more details.