Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

  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.

 

Exercise: Enter and process an Issue

  1. Create an Issue as an example. A good example is to include an Injury and Plant Damage.
  2. Illustrate the workflow - select the logged in user as both the RM and CM.
  3. Note that the Issue cannot be Approved until there is at least one action.
  4. Complete a Causal Analysis - discuss the difference between Root Causes and Findings.
  5. Note that the Issue cannot be closed until all Actions are closed.
  6. Close the actions and close the Issue.
  7. Illustrate that the Issue is now read-only, however there is a 'Reset to Draft' button on the Report page (only visible to Administrators).

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

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

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.

More information is available in the online help.
 

Exercise: Working with Dashboards

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:

 

  1. Create an Issue as an example. A good example is to include an Injury and Plant Damage.
  2. Illustrate the workflow - select the logged in user as both the RM and CM.
  3. Note that the Issue cannot be Approved until there is at least one action.
  4. Complete a Causal Analysis - discuss the difference between Root Causes and Findings.
  5. Note that the Issue cannot be closed until all Actions are closed.
  6. Close the actions and close the Issue.
  7. Illustrate that the Issue is now read-only, however there is a 'Reset to Draft' button on the Report page (only visible to Administrators).

 

 

 

 

  • No labels