On this page:
This is a training checklist to be used for instructor-led training sessions or as a reference (its not really suited as a self paced worksheet).
Issue Types and Navigation Overview
CS Incident allows 5 Issue Types to be recorded, with the 'Incident' issue Type divided into further subcategories.
Each Issue is entered and managed in 2 sections - the Report screen and the Manage screen.
Navigation and Workflow Powerpoint
This powerpoint provides a good overview - stop at the workflow section but keep the powerpoint open.
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).
Who can act as the RM and CM is controlled in CS Access via permissions. Each Issue has a RM and CM selected when it is created. Those people are sent notifications when the issue is first saved. The RM can modify these selections when they are first notified of the Issue if inappropriate selections were made.
Refer to the previous powerpoint for a summary of the workflow.
Notifications
There are a series of built-in notifications related to the workflow. These are summarised here.
Additional notifications can be created through CS Access. Typical additional notifications are:
- Issue has been created
- Injury has occurred
- Plant damage has occurred
Completing an Audit
Once you have an audit scheduled you are able to complete it.
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.