Risk Management Information System

1
Risk Management Information System
Way Ahead for Mishap Reporting19th Executive
Safety BoardCol James D Grace, DirectorCMC
Safety Division
2
Background

• 2007 Booze Allen Hamilton Study of the Mishap
  Reporting System
• DASN (S) Initiatives to fast track procurement of
  a new RMIS
• Significant Under Reporting of Class C/D Mishaps
• DSES Driving a Standard Data Element Approach
  across DoD

3
RMIS

• Joint SECNAV/CNO CMC Objective for a single
  DoN-Wide RMIS
• Formal Acquisition Program to
• Facilitate unit level safety program management
  and provide aggregate reporting, analysis and
  tracking of reportable mishap and hazards
• Address and correct deficiencies in current
  safety reporting systems
• Process will move establishment of program from
  non-dedicated funding lines to dedicated support
  and long term sustainability

4
Why its Needed

• WESS reporting is inconsistent below the Class
  A/B level
• Low reporting rates are attributed to voluminous
  data requirements, lack of training, and lack of
  internet access in forward or remote areas
• Extraction of data for analysis is overly complex
  
• Does not support roll-up to higher Commands or
  drill-down to subordinate units
• The lack of an appropriated funding line means
  that resources to properly train, support, and
  maintain services are insufficient and unstable
  in the long term

5
Current Status

• DASN(S) seeking Acquisition Sponsor (N4 or N8)
• DoN PEO (C41) PMW-150 Identified as Program
  Manager for RMIS as a Rapid Development and
  Deployment Project
• ACMC Requested POCs from PR and C4 in support of
  SD in RMIS development
• Development will be resourced through IL

6
Challenges

• Reduce data input required by the reporting unit
• Promote better reporting
• Tap into other data systems to automatically
  retrieve information
• Enter SSN results in autofill of Name, Rank,
  Unit, MOS, Marital Status, etc.
• Scrutinize and eliminate data that has no value
  in reducing mishaps
• Application of MCTFS as template for roll-up or
  drill-down of aggregate reporting and analysis
• Cannot make ANY system provide visibility across
  Chain of Command until uniform definition of the
  organization is integrated into the system

7
Standard Data Elements (SDE)

• DoD project to move all service mishap and
  injury/illness reporting to common/shared data
  structure
• Goal is to reconcile injuries reported through
  medical to mishaps (Safety Reporting)
• Defines what the mishap reporting system must
  provide to DoD/DSES
• Currently proposed to only address A/B Mishaps

8
Questions
9
Backup Slides
10
What is RMIS?

• Mishap Reporting
• Supports DoN Mishap Reporting and Investigation
  Processes
• Produce all required reports
• Support data extraction and analysis at all
  levels of Chain of Command
• Capture, Track and Monitor Near-Miss Incidents
• Provides a Quick Entry Capability of Key Mishap
  information
• Ease of Use and Full training supported on
  Internet

11
What is RMIS?

• Beyond Mishap Reporting (Priority 1 Capabilities)
• Interface with Maintenance/Equipment Reporting
  Systems (Product Deficiency Reports)
• Interface with Facility Inspections and
  Deficiency Tracking
• Assign and Track Action Items from Accident
  Investigations
• Automatic Email Notification for due dates,
  inspections, overdue items
• Support data extraction and analysis at all
  levels of Chain of Command
• Ability to produce statutory reports (OSHA 300
  Log)
• Provide for submission and tracking of Employee
  Suggestions
• Confined Space Management Entry, Permits,
  History
• System for uniform Root Causal Factors analysis

12
RMIS Stakeholders

• BUMED
• CFFC
• CNIC
• COMSUBFOR
• COMSURFOR (CNSF)
• DASN (Safety)
• DON CIO
• HQMC
• MARFORCOM
• MSC
• NAVAIR/NAVAIRLANT

• NAVFAC
• NAVSAFCEN
• NAVSEA
• NECC
• NETC
• NNWC
• OPNav (N4)
• OSD
• PACFLT
• TECOM
• SURLANT

13
RMIS Requirements

• Ease of Use/ Intuitive Navigation
• Reduce Data Entry / Increase Efficiency
• Standardization of Processes and Data
• Full Lifecycle Safety Risk Management
  Functionality
• Accessibility to Data
• Accessibility to Application
• Workflow Capabilities
• Document Management

• External Data Exchange
• NMCI Certification
• PKI
• Security
• Help/Training
• Tracking Unit Identity Codes (UIC) and Standard
  Naval Distribution Lists (SNDL)
• Data Migration
• 508 Compliance
• Reporting
• Future Technology