| Panel | ||||
|---|---|---|---|---|
| ||||
On this page:
|
...
Issue Types and Navigation Overview
...
Lucidity Incident allows 5 Issue Types to be recorded, with the 'Incident' issue Type divided into further subcategories.
...
| Info | ||
|---|---|---|
| ||
This powerpoint provides a good overview - stop at the workflow section but keep the powerpoint open. The Lucidity Incident Quick Reference Guide provides the essential workflow and entry type information you will need to get started. Download as: PDF | Powerpoint (animated) |
Workflow, Responsible Manager and Closeout Manager
...
Each Issue goes through a 4 step workflow. There are two main approval 'gates' that each Issue must pass through as part of the workflow, which are controlled by the Responsible Manager (RM), and the Closeout Manager (CM). This sounds a bit complicated (but its not).
...
| Info | ||||
|---|---|---|---|---|
| ||||
|
'No Further Action Required'
...
Any Issue can be marked as 'No Further Action Required'. This removes the workflow and places the Issue directly in the Closed state. This can be reversed at any time.
Notifications
...
There are a series of built-in notifications related to the workflow. These are summarised here.
...
All additional notifications are 'scoped' based on which parts of the business that the Notifee (user) can view. i.e. if their permissions don't allow them to see Issues related to Division A, they they will not receive notifications related Division A Issues.
Causal Analysis
...
As part of the example a Causal Analysis was completed. The questions that are asked within this step are:
...
There is more information about the Casual Analysis in the online help.
Reporting
...
There are a series of reports accessible via the Issues > Reports menu. Open the Plant Damage report as an example - if a damage value was entered in the example Issue, it will be included in the report.
Dashboard
...
A Dashboard is provided that allows data to be viewed as graphs, tables and news feeds. Each User who has access to the Dashboard is able to create their own Dashboard(s), using the widgets available. Widgets can then be edited to filter the data displayed.
...
| Info | ||||
|---|---|---|---|---|
| ||||
Until a CS Incident site has a substantial amount of data, there is very little to view on the Dashboard. For this exercise, log in to the demo site: https://demo.integralcs.com/home/login/incident
|
Statistics
...
The Statistics module allows labour hour data to be entered, and by combining it with injury information (LTI / MTI etc) from CS Incident, produces Injury Frequency rates (LTIFR etc). The maths that is used to create the frequency rates, and the way in which labour hour data is entered is explained in the online help.
...
| Info | ||||
|---|---|---|---|---|
| ||||
Until a CS Incident site has a substantial amount of data, there is very little to view in the Statistics module. For this exercise, log in to the demo site: https://demo2.integralcs.com/home/login/incident
|
Permissions
...
Permissions are managed via CS Access, in the same manner as other IntegralCS modules. There are a number of built in Roles relating to CS Incident, covering functions such as:
- Administrator
- Manager
- Responsible Manager (specific role)
- Closeout Manager (specific role)
- Create Issue (base level permission)
Lucidity App
...
Lucidity App allows incident and hazards to be entered via a mobile device using an app. The Lucidity App provides a reduced set of fields to enter either an Incident or Hazard.
...
For more information about the Lucidity App go to: Lucidity Mobile App User Guide
Checklist
...
-
Review Quick Reference Guide
-
Entering and Editing Issues
-
Managing Issues - Processing Workflow
-
Managing Issues - Causal Analysis and Actions
-
Reports
-
My Emails
- Printing Report
- Printing All
-
- Statistics
- Dashboard
-
Notifications
-
Built in
- Ad-hoc
-
- App
- Entering Hazards
- Entering Incidents
- Online / offline mode
...