Web Enabled Safety System WESS

1
Web EnabledSafety System (WESS)

• Presented by Katherine Escobar
• Project Manager
• Naval Safety Center

2
The WESS Vision . . .

• An integrated system to web enable the data
  collection and information dissemination safety
  business processes for Navy Marine Corps
• Allow data transfer with DOD, other Services
  other systems with a stake in safety

3
WESS drivers .

• VCNOs Task Force Web requirements
• SECDEF/SECNAV real-time Lost-Work-Day mandate
• DOD IG DASN(S) requirements
• CNA recommendations on Improving DON Safety
  Data

4
WESS will . . .

• Reduce workload on the fleet
• Improve quantity quality of mishap hazard
  reports
• Consolidate and simplify reporting (USN USMC)
• Provide real-time reporting
• Reduce need for duplicative data bases at local
  level
• Provide web-based data retrieval and analysis
  tools
• Support disconnected computing
• Increase efficiencies

5
How we got started . . .

• Survey of other safety systems
• ALCOA
• IRS
• Air Force
• Coast Guard
• DIUCS
• Evaluation by Naval Post Graduate School
• (IT Department)
• Support from eBusiness Operations Office
• Conducted work flow analysis
• Defined major WESS functions
• Produced Software Requirements Specifications

6
What we have done so far . . .

• Upgraded hardware software
• Developed deployed 2 systems
• BASH
• WESS 1 (Injury Occupational Illness System)
• Procured contractor support to lead in-house
  development staff
• Project Manager
• Design Engineer
• Solution scenario approved by COMNAVSAFECEN
  December 2002

7
What we are doing now . . .

• Implementing WESS II Project Plan as approved by
  COMNAVSAFECEN
• Training staff on new software tools
• Procuring software minor hardware upgrades
• Completing consolidation of Navy/Marine Corps
  reporting instructions
• Resolving disconnected computing infrastructure
  issue

8
Deployment schedule . . .

• Phased implementation and deployment
• Injury Occupational Illness system deployed
• BASH system deployed
• Query and report options will be deployed
  throughout reporting system deployment cycle
• Navy Marine Corps hazard reporting system
• 12 to 18 months
• Navy Marine Corps mishap reporting system
• 24 to 36 months

9
A look at WESS I . . .

• Collects Injury Occupational Illness events at
  a level sufficient to meet SECDEF requirements
• Meets OSHA 200 log requirements
• Permits retrieval download of data so
  activities can do their own analysis
• Eliminates need for redundant local data entry
  systems
• Provides one common platform for entry of Injury
  Occupational Illness events
• Configuration Board to manage changes
• Over 1,600 registered users with over 2,100
  events entered since Jan. 2003

10
Comparing WESS I and II

• WESS I
• BASH
• 76 data elements
• 6 online reports
• Injury Occupational Illness System
• 74 data elements
• 3 reports download function

11
Comparing WESS I and II

• WESS II
• Web enables all safety business processes
• Over 2000 data elements
• Over 240 reports to program
• Utilizes more robust software development tools
  than WESS I
• Disconnected computing
• Promote data sharing via XML

12
WESS II Development Approach

• Open-source
• A program in which the source code is available
  to the general public for use and/or modification
  from its original design free of charge.
  (www.webopedia.com)
• Java Programming Language
• Platform independent development language
• Platinum Solutions - Technical support and
  programming assistance proven track record!

13
WESS II software suite . . .

• Focus
• Established vendors
• Open source
• Function in both Shore Afloat environments
• Small to no footprint on desktop (used with
  browser only)
• Examples
• Informix underlying data base engine
• Brio report building software
• Keel JAVA development framework

14
WESS .

• Discussion?