| Panel | ||||
|---|---|---|---|---|
| ||||
On this page:
|
...
Refer to the previous powerpoint for a summary of the workflow.
| Info | ||||
|---|---|---|---|---|
| ||||
|
...
Notifications
...
There are a series of built-in notifications related to the workflow. These are summarised here.
...
- Issue has been created
- Injury has occurred
- Plant damage has occurred
...
| icon | false |
|---|---|
| title | Exercise 2: Schedule an Audit |
In this exercise you use an Audit Type already within the system to schedule an audit.
...
Make a note of the Audit you have just scheduled - we will use it in Exercise 3.
Completing an Audit
Once you have an audit scheduled you are able to complete it.
...
| icon | false |
|---|---|
| title | Exercise 3: Complete an Audit |
In this exercise you will complete the Audit that was scheduled in Exercise 2.
...
Note that in order to fully complete your audit, any Actions must be Closed, and the Audit marked as Closed. There is also the option of marking the Audit as Complete as an intermediate step:
Complete: All Actions are Closed (or there are no Actions) but the Declaration is not completed.
Closed: All actions are Closed (or there are no Actions) and the Declaration is completed.
Entering Ad-Hoc Audits
Ad-hoc Audits are used when you have a completed audit that is a 'one-off' or unscheduled audit that you wish to document. They do not get scheduled i.e. they aren't planned but are completed and entered as required. Ad-hoc Audits still need to use one of the existing Audit Types.
Remember: When you create an Ad-hoc Audit, you are actually documenting the audit and its results, not just planning to do it in the future.
...
| icon | false |
|---|---|
| title | Exercise 4: Enter an Ad-Hoc Audit |
In this exercise you use an Audit Type already within the system to schedule an audit.
...
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:
- Controlled by Administrators
- Separate for Non-conformance and Incident (2 sets of questions)
- Able to be 'nested' i.e. one questions opens to reveal additional sub-questions
- Able to be classed as Findings (no linked action) or Root Causes (have a linked action).
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