NAVSAFECOM addresses RMI concerns during review

ByRebeccaColeman

Naval Safety Command

VIRGINIA BEACH, Va More than 70 Navy,MarineCorpsandcivilianrepresentatives from across the naval enterprise gatheredhereatNavalAirStationOceana,June 14-15, to address feedback on the DepartmentoftheNavy’sRiskManagementInformation(RMI)system.

The Naval Safety Command (NAVSAFECOM), which oversees RMI, hosted the first RMI External Standards Reviewtodiscussnearly325commentsthe commandreceivedinresponsetoarequest forfeedback.

Since the Navy’s RMI launch in August 2020 NAVSAFECOM has rolled out a series of modules to expand and improve the safety reporting system which consists of four capability areas: Streamlined Incident Reporting (SIR), analysis and dissemination, safety program management and singlepointofentry RMIpromotesasaferenvironmentforthe navalenterprisebycapturingandanalyzing safety incident reporting data and streamlining the reporting process RMI, which replaced the Web-Enabled Safety System (WESS), was built for the Navy and Marine Corps and expands and adds new capabilities onto the Air Force Safety Automated System(AFSAS) Fourofthefiveservices,as wellasotherDefenseDepartmentagencies, usetheAFSASplatform.

Chris Tarsa, NAVSAFECOM executive director opened the meeting with an RMI overview noting the 137 minimum data elementsrequiredinRMIthataremandated by the Department of Defense (DoD), and the continuous improvement cycle with the phased releaseof RMI’ssafetyprogram managementmodulesorcapabilities.

“Wecontinuallysolicitfeedbackfromour customers to make this program better, to hear what our RMI customers are saying and to be responsive and transparent,” said Tarsa Forexample oneareaofimprovement addressedthequalityofinternetbandwidth

Following testing, the Navy implemented enterprise-wide changes making at-sea bandwidth speeds comparable to shorebased speeds, increasing RMI consistency andbehaviorforusersatsea.

During the conference, a robust discus-

The RiskManagement Information (RMI) system promotes a saferenvironment forthe naval enterprise bycapturing and analyzing safetyincident reporting data and streamlining the reporting process.RMI,which replaced theWeb-Enabled SafetySystem (WESS) was built for the Navyand Marine Corps and expands and adds newcapabilities onto theAirForce Safety Automated System (AFSAS) Fourofthe five services aswell as otherDefense Department agencies,use theAFSAS platform.(PHOTOBYMELISSAWENGER) sion took place on a number of issues that RMI stakeholders had submitted to NAVSAFECOM before the meeting Comments addressed a wide range of RMI categories including hazard abatement, analytics,inspectionsandtraining;however, the majority of feedback received centered ontheinvestigationsportionofRMI.

Each comment was discussed with proposed resolutions provided or tabled for further action and follow up either by NAVSAFECOM or by an integrated projectteam.

Examples of comments ranged from RMI being too cumbersome, the need for additional drop-down fields while inputting data or duplicative drop-down fields and lack of clarity in some sections A few comments conflicted with the DoD-man- dated elements which were quickly acknowledged

For the attendees the meeting was an opportunitytohearwhatissuesotherusers hadencountered,howtheyaddressedproblems,andthatNAVSAFECOMwaslistening andreceptivetotheirconcerns

“With any type of system, you’re going to havedifferentperspectives,differentintentions,” said Kimberly Cannon, director, safety engineering Naval Surface Warfare Centerheadquarters

Communication is very important to ensure stakeholders know what to expect, shesaid.Forexample,ifamoduleisn’tready bythescheduleddeliverydate,communicatinganydelaysaheadoftimewillhelpalleviatestakeholders’frustration

One frustration expressed by several stakeholders was a request for additional, oralackof,training,whichNAVSAFECOM Commander Rear Adm. Christopher Engdahlnoted.

“RMI training is one of the most critical itemsNAVSAFECOMisworkingthrough,” saidEngdahl “We’reworkinghardtofigureouttheright deliverymethodtoSailorsandgovernment employees Thetraininghastobereadyand relevant to the individual. Wemay leverage train-the-trainer models, regional SMEs or include online training NAVSAFECOM is receptivetoallsuggestions,”hesaid.

WESSwasthefirstoffivesafetyreporting systems that RMI will replace or consolidate The other four systems are the Enterprise Safety Application Management System, the Injury/Illness Tracker the Medical Mishap and Compensation and Portsmouth Naval Shipyard’s Occupational AccidentandInjuryReportSystems.

Todate,thefollowingRMISafetyProgram modulesarecomplete:Inspections,Hazard Abatement, Training and Confined Space

The remaining modules are scheduled for delivery through fiscal 2027: Job Hazard Analysis MedicalSurveillance Self-Assessment, Respiratory Protection Fall Protection, Operational Risk Management and SafetyCommittee.Oncefullyimplemented, themoduleswillhelpensureallsafetyinformation is captured to help support mitigation and that the functions will perform sufficientlyregardlessoflocation.

“The real goal of this program is mishap prevention,” said Tarsa “Learning is lost whenwedon’treallylookatthefactorsthat leaduptoanevent.

At the end of the second day, the commander thanked attendees for their participation and candor and encouraged themtokeepthefeedbackcoming.

“The goal is to make RMI better,” said Engdahl. “It’s the program we have, and feedback from the fleet ensures it is getting bettereveryday.”

Headdedsubsequentmeetingswilloccur at least once a year with next year’s agenda buildinguponthisfirstone.

“You are all part of a growing RMI communityofinterest,andwemustcollectivelyworktomakemishapreporting,analysisandinvestigationbetter,”saidEngdahl.