Transcript Wilsaf - Blackboard

Introduction to the incident reporting system and
proposed action points
WHAT IS THIS ABOUT?
•
•
•
•
Overview on the why’s and who’s
Where we’re at
Objectives
Proposed strategy and roll out
WHY NOW?
Within the macro environment
• Gone Public
• Growth and Development
• Maintaining the lead
A System overhaul
•
•
•
•
Designated Wilsaf number
Rebranding the reporting line
Incident reporting protocol
Transparency across the company
• Why the revamp?
Why out-source?
• Wilderness’s key focus: Tourism/ Hospitality/
Sustainability
• Professional service outside of scope
• Infrastructure and knowledge
• Trusted relationships
• Reliability & Validity
RELATIONSHIPS
SATIB
• Insurance Broker
• Value add service through the Africa Incident
Management Centre:
- 24/7/365 access to incident management services
and tele-medical consults.
- Emergency/ crisis management/ evacuations etc.
- Access to other resources i.e. psychs/legal etc
Wilsaf24 (???)
•
•
•
•
A step up
Ownership
Central reporting ‘station’ for ALL incidents
Data across the company is captured= ability
to gather reliable and valid data for risk
analysis.
• Internal control over how data is used and
disseminated.
MINIMUM STANDARDS
•
•
•
•
•
Accountability
Improve internal co-ordination
Promote preparedness capacity
Promote internal policies
Job performance
CLASSIFICATION SYSTEM
What’s the world doing?
• Data comparison within industries i.e.
Aviation, mining, tourism, sport etc very high.
• Across industries or work sectors- none found.
Why a Universal classifications system?
• Cross industry comparison
• Data gathered which exceeds ANY other
company or industry of operation
Previous reporting structure
SATIB
AIM C
CAMP
JHB HEAD OFFICE
MD
DIRECTORS
OPS
CUSTOMER SERVICES
PR
HR
WILSAF AIR
New Structure
AIM C
SATIB
JHB HEAD OFFICE
RISK COMMITTEE
Regional IC
CAMP
WILSAF’S BLACKBOX
DIRECTORS
OPS
MD
WILSAF AIR
HR
CUSTOMER SERVICES
PR
Why have it structured?
• POWER!!!
• Less chance of errors in ID of incident
• Reliability & Validity in data gathered
REPORTING TOOL
What is an incident
“An incident is an unexpected or unwanted
change from normal system behavior which
causes or has the potential to cause a loss.”
Security
• Own domain
• Currently on Wordpress but shift to Drupal
platform (no functionality change).
• Restricted Access
• Strong Passwords
• Daily monitoring of site
Incident Lifecycle
Layout
•
•
•
•
•
•
Purposefully simple and uncluttered
Reporting Form
Analysis
Categorizations
Timeline
Map
Reporting Form
1)
2)
3)
4)
5)
6)
7)
8)
Where?
When?
What Happened?
Activity at the time
Agency
The Affected
Loss/ Impact
Categorization of criticality
Timeline
ROLES
Who should do what?
Who
Report
Monitor
Action
Training
Camp
✓
Regional IC ✓
✓
✓
✓
MD’s
✓
✓
CS
✓
✓
PR
✓
✓
AIM C
✓
✓
✓
Group IC
✓
✓
✓
Risk Co
Directors
✓
✓
Analyze
Policy creation
✓
Advisory only
✓
Advisory only
✓
✓
✓
CRITICALITY
Why use magnitude of loss?
• Others
– Military
– Safety critical industries (nuclear power plants)
• Simplicity
• Meaningful data
Levels of reporting
• 5 levels proposed as with levels of criticality
• Example:
-
Guest’s luggage is lost en-route to camp
$100 goes missing from guest room
Hippo damages a mokoro
Aircraft makes an emergency landing
Camp burns down after a lightning strike
ANALYSIS
What can we analyze?
•
•
•
•
•
•
•
High risk activities
Seasonal activity
Areas of incident occurrence
Regular loss of property/ assets
Regular equipment failure or damage
Criticality of incidents
Regularity of reporting
Graphs
High level
• Graph of number accidents acts under the
four types of incident:
-
Failure
Natural
Act
Accident
Next level
• Subtypes under each type i.e. what sort of
Natural incident?:
-
Getting even more specific….
• Sub sub types:
INCIDENT LEARNING SYSTEM
What is an ILS?
• A risk control process which components inc:
-
Identification
Reporting
Investigating
Communicating internally and externally
Recommending and advising
Implementing corrective actions
Incident learning
ROLL OUT PLAN
Summary
•
•
•
•
Decisions to take.
Manuals, lesson plans, online learning tools.
Workshops
Audits and Statistic reports
Decisions to take
1. Timeline on reporting
2. Who reports what
3. Who’s involved at which level
Proposed Timeline
Pilot (Jan- Feb)
Phase 2 (March-June)
Phase 3 (July- Sept)
Region Introduced
Bots & Zambezi
All other regions
Info required
Regional & camp IC
identification. CS,
Risk Co, MD’s, 3rd
party contacts.
New regional and camp IC
identification
Further system
requirements i.e. cell
phone, email, skype
access etc
Report tool functions
Taxonomy, data
platform, basic
functionality.
Include reporting functions
i.e. notifications via
email/sms. Load training
manuals
Add auditing function,
further training material/
self-assessment
capabilities
Training material
Basic intro to the
reporting tool.
Manual, Lesson plans
Videos/ inking
Continued inking, case
studies
Workshops
-
Bots & Zambezi
Other regions
Progress Reports
13th Feb
1st June
1st October
Who reports
•
•
•
•
•
•
Camps
Regional IC’s
Regional MD’s
Customer Service
Wilderness Air
3rd Party access i.e. OAT?
Who’s involved- which level?
Who
Camp/ Staff
Customer
Service
Regional IC
Regional MD
AIM C
Risk Co
Directors
Level 1
Level 2
Level 3
Level 4
Level 5
Training Material
• To include the following:
- Manual (Why, Research, Incident learning system,
understanding the online form structure etc)
- Lesson plans surrounding each step in the form
- Video material
- On-line self-assessment tool (inking)
“From all this evidence, we submit that it is
not natural for organizations to learn from
safety incidents. Even if ad hoc learning is
occurring, it is not enough.”
Cook & Rohleder 2006
Workshops
• Skills training and capacity building
• Proposed 2-3 day workshops per region
• ‘Hands-on’ approached more effective
Reports to company
• Frequency and level of stats reporting?
-
Reports to Board of Directors
Reports to Risk Committee
Brief reports to MD’s
Feedback to regional IC’s and camps