Navy Lessons Learned Program Transition to JLLIS

1
Navy Lessons Learned ProgramTransition to JLLIS

• Captain Lee Rossetti, USN
• Director, NLLP
• March 11, 2008

2
Purpose, Objectives, Desired Effects

• Purpose
• Information Brief Navy Lessons Learned Program
  (NLLP)
• Navy JLLIS Transition Considerations
• Bandwidth and existing solutions
• NLLP usage statistics
• Result
• Better understanding of NLLP concerns and
  challenges during the transition to JLLIS.

3
Navy Lessons Learned Program

• Issue
• NLLP transition to JLLIS faces cultural,
  technological, training, and administrative
  challenges.
• Background / Discussion
• Navy culture focuses on
• Command at Sea
• Decentralized Execution
• Warfighting
• Fleet Communication realities
• Uncertain Connectivity
• Limited Bandwidth
• Fleet Knowledge Management initiatives
• Multiple Lessons Learned / Best Practices
  solutions
• Navy Budget for NLLP is not getting any bigger
• NLLP budget thru 2012 is status quo

4
How Lessons Are Distributed/Used

• Database searchable by anyone with SIPRNET
  access, or NIPRNET access and a CAC card
• Web Site averages 500 visitors/day
• Monthly Newsletter over 2,000 subscribers via
  SIPR/NIPR email
• NWDC develops and posts targeted products for
  CSG/ESG/Training commands
• NLLP Reps visit commands and conduct command
  theater-specific training
• Feedback from Numbered Fleets indicate extensive
  use for
• Port visit Reports, AT/FP planning
• Exercise planning
• Pre-deployment preps / Inchop briefs
• Operational planning
• Navy, Joint, and Interagency staffs use lessons
  to develop DOTMLPF solutions

5
How CaS works 3 Steps
Global Replication of Changes
NOC
BGhome.nsf
NOC
NOC
NOC
High-speed INTERNAL BROWSING

• Instantaneous Access
• Far Less Down Time
• Consumes No BW

6
Conclusion and Recommendations

• Navy transition timeline
• NLL Database sent to MCCLL for inclusion in JLLR
• Navy JLLIS install scheduled for 2-13 June
• Navy transition period June to October
• LL working group sidebar discussion

7
(No Transcript)
8
Who Maintains NLLP?
DIRECTOR CAPT Lee Rossetti
Newport 2 MIL, 6 CTR
Norfolk 1 CIV, 4 CTR
ACTIVE COLLECTION LT Sean Marvin
DEPUTY Mark Henning
Deployed 5 CTR
PROGRAM MGR David Perretta
JOINT LNO Steve Poniatowski
WEB DEVELOPER Kevin Cabral
C2F REP NORFOLK Pat Casey
C5F REP BAHRAIN Gil Gillespie
IT MANAGER Dave Demming
ANALYST Frank Steinbach
WEB DEVELOPER Rod Norris
C3F REP SAN DIEGO Rich Mooney
C6F REP NAPLES Jes Sutton
ANALYST Jay Corey
ANALYST Vacant
WEB DEVELOPER Matt DeTerra
C7F REP YOKOSUKA Al Choi
DATABASE ADMIN Star Ferrin
9
How Are Lessons Collected?

• Passive Collection
• Instruction process - OPNAVINST 3500.37C
• Database contains over 50K lessons
• Observations from fleet operators after the event
• 80 of lessons are submitted via naval message
• 10 of lessons are harvested from briefs,
  emails, or interviews
• 10 submitted online or via Collaboration at Sea
  (/CAS)
• Online SIPRNET and NIPRNET submission available
  for concurrent reporting
• Average time-late from event observation to
  database entry is 30 days
• Active Collection
• Evolving process - netted over 400 lessons from
  Tsunami and Katrina relief ops
• Observations from Subject Matter Experts
  concurrent with the event
• Participant interviews provide context
• Average time-late from observation to senior
  leadership review is 2-3 days

10
How Are Lessons Assessed?

• Chain of Command
• Commanding Officers approve and release
  observations
• ISIC/TF Commanders review, validate, and forward
  observations
• Fleet Commanders review, validate and approve
  lessons
• NLLP Fleet Management Site Reps (NWDC
  contractors) at Numbered Fleets facilitate
  process
• NWDC
• Conduct trend analysis
• Push critical issues to OPNAV via USFF (Tsunami,
  Katrina, GWOT Surge)
• Push data on NWDC special projects and focus
  areas to CONOPS, DOCTRINE, MBC

11
How Are Lessons Integrated/Institutionalized?

• Fleet Remedial Action Program (RAP) - instruction
  process (OPNAVINST 3500.37C)
• Fleet Staff
• Identify lessons requiring action
• Tracks to resolution - normally resolved quickly
• Navy-Wide RAP-evolving process
• NWDC analyst
• Identify lessons requiring action
• Develop RAP packages
• Staff with WCOEs/Fleet Collaborative Teams
• Forward recommendations to FFC
• Track remedial action - normally takes longer
  than Fleet RAPs to resolve

12
Collaboration at Sea (CaS) Overview
13
Replication of Changes
Ship
NOC 1
NOC 2
Carrier
NOC 4
Ship
Ship
Ship
NOC 3
Ship
Ship