| Panel | ||||
|---|---|---|---|---|
| ||||
On this page:
|
...
In Lucidity Incident, Actions are entered either as a result of the Causal Analysis as part of an Issue or on an ad-hoc basis (as required) in the Corrective Actions section. Refer to the 'Casual Analysis' section in page in this User Guide for more details.
Actions can also be added directly into the Actions tab by the Local Administrators to allocate tasks for Managers or users to complete and vice versa. A user can also create actions for themselves.
An example of how a user's My Actions tab in Lucidity Incident may look is shown below.
...
For more detail on how to use this feature, refer to the Actions User Guide.
SETTINGS
The Settings tab is only available to the System Administrator and is where the managed lists that are available within the Filters of Lucidity Incident are generated, as well as where the root causes for Causal Analysis are created.
Settings Menu
From the Settings tab, System Administrators can:
- Add New, Edit, and Delete items from each list
- Use Filters to search each list
- Generate an Excel report for each list
- Manage Causal Analysis root causes
...
From the Managed Lists section, there is a large number of lists that are accessible. Refer to the relevant 'table of definitions' within each page of this User Guide for more details.
...
Causal Analysis
| Tip | ||
|---|---|---|
| ||
Lucidity Incident: Settings Tab: Causal Analysis
|
The Non-Conformance and Incident Issue types use the Causal Analysis questions. The questions for the Causal Analysis are configured using the ‘Incident Root Causes’ and ‘Non Conformance Root Causes.’
Refer to the 'Causal Analysis' section section in this User Guide in the 'List Issues' section for more details.
To add a new Root Cause to either the Incident or Non-Conformance Root Causes list, from the relevant Root Cause page:
- Click 'Add New'
- Complete all fields (see table of 'Definitions of Fields' table and related image below)
- Note:
- The details captured for each Root Cause may vary slightly between each system configuration. Fields marked with*are mandatory
- Once complete, click 'Save' to save changes
Definition of Fields
| Question ID | Enter question ID number Used to place the Root Cause items in a particular order Any number is accepted, '.00' will be added by default to any whole numbers |
|---|---|
| Description | Enter the description of the Incident or Non-Conformance Root Cause. This is generally a question, such as "Did the design of plant, facilities or equipment contribute to the Incident?" |
| Make This a Heading | Select Yes or No to make the item a section heading rather than a question The next 3 fields cannot be populated if 'Yes' is selected |
| Contributing Factor | Enter the contributing factor for the Incident or Non-Conformance Root Cause. This is generally a summary of the question, such as "Design of plant, facilities or equipment" and is displayed below the full question |
| Parent Question | Select the parent question if relevant. The new question will then become a sub-question of the parent |
| Has Action | Select Yes or No to determine if an Action is required to be created if the question is selected If 'No' is selected, the Contributing Factor is recorded as a Finding and no action is required |
...