Who is this article for?

Administrators and Managers who want to learn about configuring Incident settings.

Administrator permissions are required to follow some of these steps.

The Settings tab, exclusively accessible to system administrators, serves as the control centre for generating managed lists utilised in Lucidity Incident filters and for creating root causes employed in causal analysis. This critical area allows administrators to configure essential elements that shape the functionality and analytical capabilities of the Lucidity Incident system.

1. Settings

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.

Important: Care must be taken when editing settings to ensure that any entries in lists that are modified do not have unintentional consequences, as all existing issues, causal analysis etc. that have used a particular selection in a list will be also modified.

2. Managed Lists

From the managed lists section, there is a large number of lists that are accessible.

2.1. Managing Companies and Contractors

A managed list for companies and a separate list for contractors appears in various locations in the Incident module. Typically, they are used for the following purposes. 

• Companies: the list of companies is managed in Lucidity Access and typically includes all companies that are used as a regular contractor or supplier to the organisation. This list is used throughout the entire Lucidity suite (e.g. Access, Contractor, Induction).
• Contractors: the list of contractors in managed in Lucidity Incident and typically includes one off contractors who may be a subbie of a subbie of a subbie for example. It's typically a contractor who isn't a regular supplier but was on site at the time of the issue and therefore needs to be listed in the report.

Note: These are guidelines only and can be utilised in anyway that suits. It may be preferred to only utilise on of the lists and not use the other at all.

2.2. Adding a new Injury Severity

Lucidity Incident allows for full flexibility to create a range of injury severity options for reporting, and then control which of these flows through to the (e.g. LTIFR and MTIFR) and which do not.

To add a new injury severity and specify how it is treated for injury frequency rate reporting purposes, from the Managed Lists menu:

1. Search for and locate the Injury Severities managed list.

2. The current injury severity options will be displayed, including whether each option contributes to an injury frequency rate calculation. 

3. Click Add New to create a new injury severity option.
4. Enter the label and description for the new injury severity option.
5. Select the calculation type from the drop-down list.
6. The example below does not contribute to any calculation as calculation type = do not report.

7. Click Save.
8. The new injury severity option will now appear in the injury report form and in relevant managed lists.

3. 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. 

To add a new root cause to either the incident or non-conformance root causes list, from the relevant Root Cause page:

1. Click Add New.

2. Complete all fields.

Note: The details captured for each root cause may vary slightly between each system configuration. Fields marked with * are mandatory

3. Once complete, click Save to save changes.

3.1. Definition of Fields

3.2. System Settings within Lucidity Access

Some settings for Lucidity Incident are managed via the Settings tab within Lucidity Access as they apply to more than one Lucidity application. These include:

• Division
• Location
• Business Unit
• Project

4. Further reading

• Configuring Incident reports
• Using Actions and Dashboards in Incident
• Configuring Incident statistics