Distance Support Governance Board

1
Distance Support Governance Board

• 03 DECEMBER 2008

2
Agenda

• Introductions (USFF 1400-1410)
• LCS Distance Support Interface LCSCLASSRON
  (1410-1440)
• POM 10 Funding Determination
• Distance Support Way Ahead USFF N74 (1440-1510)
• Approve single resource sponsor concept
• Support to complete FSA
• FY 08/09 Execution PMW 240 (1510-1535)
• Approve FY 09 spend Plan including funding
  shortfall
• Round Table (1535-1545)
• Recommended new actions

3

• LCS Distance Support

Commodore Chris Nygard
4
Desired Outcomes/Objectives
Context

• Distance Support is the center of gravity for
  work flow on LCS
• Fully Incorporate Distance Support capability and
  applications in LCS
• Define LCS Distance Support resource sponsorship
  and responsibilities
• Provide Systems Integrator to Program Office or
  LCS CLASSRON

Desired Outcome
5
LCS Distance Support Processes

• MAINTENANCE
• Preventive Maintenance (3M)
• Corrective Maintenance
• Budget Management
• Remote Monitoring

• MEDICAL
• Monitoring Consumption Data
• Ordering Medical Materiel
• Reconciling Inventory
• Medical Reports

• TRAINING
• Training Team Requirements
• Crew Proficiency Ashore
• Qualifying Ashore

S2S

• ADMINISTRATION
• Personnel Records
• Pay Records
• Legal Records
• EVALs
• FITREPs
• Bills

• SEA WARRIOR
• Career Management
• Personal Development
• Learning References

SKED 3.2
S2S
BCS / LMAIS eFSM
S2S SIPR NIAPS

• OPERATIONS
• Sending Messages
• Requesting Port Visits
• Sending Foreign Country Clearances
• CASREPs
• SORTS
• LOGREQ
• FP ISP

• LOGISTICS
• Inventory Management
• Document Creation/Issue
• Financial Management
• Food Services
• Fuel

245 Processes migrate ashore LCSRON becomes
extension of ship
6
FREEDOM Shipyard Lessons Learned

• Establish connectivity as early in the process as
  possible
• Required for installation and testing of NIAPS
  and NIAPS reliant applications
• T1 line
• INMARSAT (single pipe)
• Not the standard Navy version - Installation and
  connection - complex, more training
• Establish a DITCO Account early - involves
  several organizations
• NIAPS
• Complete SOVT before attempting application
  installation and testing
• NIAPS Technician present during all application
  installation and testing
• Monitoring - Replication rates Health (HAMS)
• Appoint a Gatekeeper - Manage bandwidth
  scrutinize file transmission
• Training - Crew Systems Administrator training
  prior to NIAPS installation
• Crew Participation
• Deconflict coordinate training and assistance
  early
• Training - NIAPS Administrator and User Training

7
Barriers

• Manning
• Right resources to manage and perform work
• Sustainment
• Ownership Funding
• Development and Continuous Improvement
• No single POC for systems, databases, processes,
  and testing
• Continue to find innovative methods
• Automation -- information directly to end user
• Process modification
• Competition for Resources
• SIPR NIAPS
• S2S Webform development

8
Webform Sustainment

• Execution
• Webforms established as tool for minimal S/F
  input to transfer workload to the LCSRON.
• Barrier
• No funding or sponsorship FY10
• 500K/year for both LCS 1 and LCS 2
• Funding for FY08/09 came from SEA 21 and
  Congressional funds
• Status
• Unfunded for FY10
• Recommendation
• DSGB recommend to OPNAV to designate resource
  sponsor to oversee and fund webform development
  and sustainment.

9
Products and Organization
LOTS OF GOOD INVOLVEMENT WITH NO SINGLE BELLY
BUTTON
INVOLVEMENT
SPONSOR
CERTIFICATION AND ACCREDIDATION
CLEAR LINES OF RESPONSIBILITY?
10
Recommended Actions

• Designate a webform resource sponsor
• Clearly define LCS Distance Support
  responsibilities
• Provide Systems Integrator to Program Office or
  LCS CLASSRON

11
Distance Support Way Ahead

• Bob Moser
• USFF N74
• 3 December 2008

12
Desired Outcomes/Objectives
Context

• Distance Support capability may be enhanced by
  more appropriately assigning responsibility and
  accountability
• Current Distance Support structure is stove-piped
  and incoherent
• To date, a capability based assessment has been
  partially completed.
• FAA and FNA complete
• FSA languishing
• LCS 1 is in the Fleet Distance Support
  (transport and content) must be delivered
• Agree to way ahead for Distance Support
• Identify potential single OPNAV resource sponsor
  to lead
• Complete FSA
• Assign responsibility for development of DS
  support plan

Desired Outcome
13
Background

• 2004 - USFF established the Distance Support
  Governance Process
• Output
• DSGB Revised Charter signed by DCOM (Aug 07)
• Assigned membership (TYCOMs, Sponsors, Functional
  Area leads
• Established Operational Assessment Group (OAG) to
  support technical assessments
• Addressed roles and responsibilities to support
  requirements determination
• DNS Policy Paper (Mar 07)
• Established formal definition for Distance
  Support
• Assigned OPNAV N4 and N6 as resource sponsors
• Avenue to forward requirements
• Directed JCIDS compliance
• A lot of activity, but modest production

14
Capabilities-Based Assessment (CBA)

• Functional Area Analysis (FAA) completed
• Defines what we need to do
• Reviewed and approved by DSGB (Mar 08)
• Distributed by e-mail and posted on DS portal
• Functional Needs Analysis (FNA) completed (Jun
  08)
• Defines what we can/cant do (Gaps)
• Functional Solutions Analysis (FSA) initiated
• Validate DOTMLPF gaps, develop recommended
  solutions
• Languishing, lack of subject matter experts.

15
Distance Support As-Is
Not Integrated Lacks Off-Ramp
16
A More Coherent Approach
Functional Area Requirements
Platform Sponsor Requirements
DSGB
17
Potential Single Resource Sponsors

• OPNAV N4
• PROs
• Has stake in content
• Integral to NIAPS process
• Responsible for Global Distance Support Center
  (GDSC)
• CONs
• Not responsible for transport afloat or ashore
• Not responsible for shore infrastructure
• OPNAV N6
• PROs
• Responsible for transport including shipboard and
  shore services
• CONs
• Not responsible for applications and software
  (content)
• No linkage to GDSC
• OPNAV N8
• PROs
• Own most urgent problem LCS DS
• Should have developed DS support plan
• CONs

18
Recommendation

• DSGB push single resource sponsor recommendation
  to DNS
• Establish more formal Echelon I program
  management
• Resource Sponsor support FSA
• CNSF/N86 produce LCS DS support plan to influence
  POM-10 Redux/PR-11

LCS 1 is here Need to Deliver Coherent Distance
Support
19
Distance Support UpdateFor the DSGB

• CAPT Jim Dick, APM for Distance Support
• 03 December 2008

20
Agenda

• DS Overview
• FY 09 Product Plan Review/Status
• FY 09 Whats Covered
• FY 09 Whats Not Covered
• Additional Distance Support Issues
• Distance Support Takeaways
• Recommendations/Decisions

21
Distance Support Program Elements
Middleware CRM/SOS/SDE
Infrastructure
Shared Data Environment (SDE) Common trouble
ticket routing and tracking system Vital data
source for multiple users
Global Distance Support Center (GDSC) 24/7/365
single point of entry for Fleet reach-back (naval
msg, email, phone, Web, chat, walk-in) Routes
trouble tickets to appropriate Source Of Support
(SOS)
Navy Information/Application Product
Suite (NIAPS) DS IT product, to facilitate
fielding of functionality on all
platforms Tailored/integrated application/content
load (bundled) Bandwidth mitigating solution
(bi-directional data replication) Ship controls
data flow/bandwidth usage
Anchordesk Website Access to authoritative shore
SOS Link to DS metrics Repository/access for DS
and SOS documentation Entry point to join
NIAPS Same content as NIAPS DS portal/updated
via replication afloat
My Metrics Customizable scorecard based on
trouble ticket data Web enabled Supports
informed resource allocation decisions
Distance Support Products Users Navy Enterprise
Ship and Shore HW/SW
Shore HW/SW
Tech Solution
Shore HW/SW
Shore HW/SW
Shore HW/SW
N6 (FY 10 and out)
OPNAV Sponsor
N4
N4
N4
N4
Distance Support Governance Board/Operational
Advisory Group (DSGB/OAG)
Requirements
SOS funds connectivity to system and continued
life-cycle support of the SOS Join SDE
Funded authoritative data sources provide links
to Web sites and continue life-cycle support of
their sites DS Web site can provide hosting
Users access system to view metrics Propose new
data/metrics requirements
Application/content sponsor funds joining NIAPS,
application/content life-cycle support
Applications/content developed IAW NIAPS
technical standards
Fund unique call center requirements Utilize
centrally funded Tier 1 services Join SOS
Functional Area Customers Maintenance Logistics
Medical/MPTE Warfighting
22
Program Highlights

• CRM
• Enterprise CRM stood up at NSWC Crane
• RMC and GDSC Logistics (NAVSUP) part of SDE
• LCS Remedy Forms added to CRM
• NIAPS
• Trident Warrior 2008
• Amendment servers at RNOSC West (running) and
  Bahrain (eqpt in place)
• NIAPS 2.1
• LCS-1 Support NIAPS Shore server, shipboard
  installation and web form development
• Permanent PMW 240 APM for DS in place
• High Interest Items and Major Issues/Concerns
• Requirements management and funding
• OPNAV sponsor advocacy
• Continued LCS support
• NIAPS Schoolhouse Training/Stand-Up

23
FY 09 Product Plan Review

• FY 09 plan does not appear to account for the
  recurring installation and training costs
  (2400K) that were covered in FY 08 using
  carry-over dollars
• Increasing costs to continue support of the
  fielding levels desired by the TYCOMs (Fleet
  Support , development environment complexity,
  Integration, Test and Evaluation, Information
  Assurance/ Accreditation requirements)
• Maintenance of 4 deployed baselines increases
  IA/Update/Fleet Support costs
• Implementing programmatic discipline to
  requirements management, development, TE,
  Configuration Management and Version Release
  processes incurs additional costs
• eCRM costs slightly exceeding projections.
  Remainder of CRM remains within budget

24
FY 09 Product Plan Review
Per the Transition Plan, installation and
training costs should be captured in this line
item and it does not reflect the 2.4M required
in FY 09
25
FY 09 Whats Covered in Product Plan Funding

• 2 releases of NIAPS
• April 2009
• October 2009 (includes implementation of PKI sign
  on)
• Reduced level of Fleet Support (Tier 2 Help Desk)
• 1 FTE (funded)
• Maintenance of the NIAPS framework and current
  hosted applications/content (status quo) between
  releases
• Support for 4 product baselines
• Development environment for 1.0 (subs only), 1.2,
  2.0 and 2.1
• Tech support
• Minimum sustainment of NIAPS development
  infrastructure and Global Collaborative
  Infrastructure
• Defers software maintenance upgrades/renewals
• Defers hardware upgrades (storage expansion) and
  addition of new amendment server locations
  (Bahrain, Norfolk)
• Integrate NIAPS as part of CANES Early Adopters
  Program

26
FY 09 Whats Not Covered

• NIAPS Application Integration/Updates
• No roll-out of additional or upgraded hosted
  application functionality (Configuration
  freeze) between releases
• NIAPS Installation and Training
• Approximately 100 installations (NIPR)
• Associated training delivery
• Leaves all 1.2 ships as is, limits 2.X upgrades
  to current 2.0 ships only (63 currently in the
  Fleet)
• Robust Fleet Support (Tier 2 Help Desk)
• 3 additional FTE to sustain FY 08 level of
  support
• Participation/Support for TRIDENT WARRIOR
  Exercise

27
FY 09 Shortfall Discussion

• Surface Ship AIT installations and training are
  the biggest risk
• Not reflected in the DSGB Product Plan
• FY 08 work was forward-funded in FY 07 not
  reflected in the 11M TOA
• No allowance in FY 09 for continued installations
  and training
• SIPR installations funded separately by USFF at
  end of FY 08 not considered a shortfall
• Mitigation options limited by risk
• Development and release costs tied to meeting
  Fleet/TYCOM desired fielding levels
• Importance of DS solution increasing with
  implementation of LCS
• NIAPS is a key shipboard component
• eCRM essential to work flow/accomplishment
• For FY 10 and beyond, must align the work to the
  budget
• Tin Cup not a viable option
• Focus on prioritization of work based on
  governance process

28
NIAPS Hosted Application Cost Sharing

• Distance Support Program transition concept
  included a revised Join NIAPS process that
  included a fee structure for hosted applications
  and content
• Implements CNO policy on Distance Support that
  states, The functional area content owners shall
  bear the cost of applications and associated data
  that ride on Distance Support
• One-time charge for new applications joining
  NIAPS
• Annual, recurring charge to cover the cost of
  application integration and testing
• Additional charges for applications that desire
  more frequent updates/releases
• The Join NIAPS fee structure was never
  implemented and the Distance Support Program has
  been bearing the full cost of integration and
  testing for all applications and content which is
  exceeding programmed funding
• Given the complexity of the NIAPS environment and
  desired update frequency by some of the hosted
  apps, recommend reexamining the imposition of a
  fee structure

29
Additional Distance Support Issues

• NIAPS Fielding
• Compliance with the Navy Modernization Plan (NMP)
  Process requires all software installs/upgrades
  to take place during designated modernization
  windows
• AIT installations during designated
  availabilities
• Adherence to NMP will result in slower
  upgrade/standardization across the Fleet
• Hosted application owners cannot tie delivery of
  Fleet-wide capability to NIAPS release schedule
• PMW 240 will work to establish an update process
  for hosted apps within the NIAPS framework that
  will allow more frequent refresh of content
• Customer Relationship Management
• Continue to participate in Contact Center
  Consolidation efforts
• Examine opportunities for increased efficiencies
  with other CRM-related organizations
• Program Management
• Continue to build PM staff to support move toward
  POR status
• Baseline requirements and build a program within
  the FY 10 and out funding profiles
• Implement programmatic elements such as
  Integrated Master Schedule, Configuration
  Management, Test Evalation
• Work with OAG to establish Functional
  Review/Configuration Control Boards for NIAPS and
  eCRM Shared Data Environment

30
Distance Support Takeaways

• Distance Support requirements are not well
  base-lined and aligned to funding
• Need to align work to funding continued Tin
  Cup approach not viable
• Biggest shortfall is in NIAPS NIPR Installation
  and Training
• Definition of requirements through the JCIDS will
  be a key step for POM 12
• Explore fair-share funding through NIAPS fee
  structure to support for updates of NIAPS
  content/functionality between releases
• NIAPS remains a key enabler for new capability
• Integration into LCS concept of operations
• Replication/data compression functionality within
  CANES
• Working with OAG to establish Functional
  Review/Configuration Control Boards for NIAPS and
  eCRM Shared Data Environment
• Establish robust dialogue between Users and
  Technical Community
• Application operational testing and release
  management
• Communications and change management

31
Recommendation

• Execute FY 09 Product Plan as described
• Solicit alternative funding sources within the
  FRE to support NIAPS installations and training
  as well as NIAPS application and integration
  updates
• Explore option for hosted application fees to
  defray costs and increase flexibility for content
  delivery

32
(No Transcript)
33
Distance Support and LCS

• Developing new ship and shore based Distance
  Support
• technical capabilities, applications and
  operating procedures is
• critical to the transformational LCS concepts of
  minimal
• manning and multi-crewing. LCS DS capabilities
  must expand
• in a collaborative manner as the Navy operates
  ships
• with fewer Sailors, improves Navy work processes,
  
• shapes tomorrows infrastructure, and
• delivers the future Fleet.

DS/NIAPS IS THE CTR OF GRAVITY FOR WORK FLOW ON
LCS.
34
NIAPS/DS/Communications LCS Integrator
Comms Connectivity
Crew
Intermediate User
Ship
INTEGRATOR
Database Manager
Data End User
Program or App Manager
Feedback
35
NIAPS Resident LCS DS Applications

• S2S Webforms
• Developed and deployed within NIAPS and CRM
  products to enable movement of LCS work ashore
• Created for those processes not covered by
  existing applications, but requiring distance
  support
• Actions identified and promulgated via SOPs and
  created business rules.
• Enhanced Food Service Management (eFSM)
• Streamlines ordering, reconciling and documenting
  a ships food supply process by enabling an
  individual located at Naval Base San Diego to
  generate menus and coordinate food ordering for a
  ship located thousands of miles away
• LMAIS
• BCS
• Automates receive, stow and issue functions
• SKED
• Allows planning and scheduling of maintenance
  tasks ashore
• Pushes only relevant maintenance procedure data
  to sailor onboard ship for execution on tablet PC
• Simplifies and automates shipboard maintenance
  reporting requirements
• eSOMS
• A program/database that allows the ship to print
  tags rather than handwrite them
• Maintains a database so that once a tag out has
  been done on a system or piece of equipment the
  tags required are permanently stored to reduce
  time/manpower required in the future
• Coordinates so that one tagout of a piece of
  equipment can support multiple jobs
• Sea Warrior Applications (CMS/ID, NKO, NeL, ETJ,
  AILE, NAFL)

36
NIAPS Resident DS Applications

• S2S Webforms
• Developed and deployed within NIAPS and CRM
  products to enable movement of LCS work ashore
• Created for those processes not covered by
  existing applications, but requiring distance
  support
• Actions identified and promulgated via SOPs and
  created business rules.
• Enhanced Food Service Management (eFSM)
• Streamlines ordering, reconciling and documenting
  a ships food supply process by enabling an
  individual located at Naval Base San Diego to
  generate menus and coordinate food ordering for a
  ship located thousands of miles away
• LMAIS
• BCS
• Automates receive, stow and issue functions
• SKED
• Allows planning and scheduling of maintenance
  tasks ashore
• Pushes only relevant maintenance procedure data
  to sailor onboard ship for execution on tablet PC
• Simplifies and automates shipboard maintenance
  reporting requirements
• eSOMS
• A program/database that allows the ship to print
  tags rather than handwrite them
• Maintains a database so that once a tag out has
  been done on a system or piece of equipment the
  tags required are permanently stored to reduce
  time/manpower required in the future
• Coordinates so that one tagout of a piece of
  equipment can support multiple jobs
• Sea Warrior Applications (CMS/ID, NKO, NeL, ETJ,
  AILE, NAFL)

37
S2S Webforms

• Ship Crews, LCSRON Staff and NAVSEA identified
  245 Work Processes
• Instructions, bills, messages, logs, program
  reports, etc.
• 90 Work Processes identified as must have for
  operations in 2009
• Spiral 1 Addressed the must have processes
• Shipboard 58 Webforms created
• Shore Corresponding Remedy forms includes
  additional data elements and output requirements
• Spiral 2 Will address remaining processes and
  emergent concerns
• Create entry dashboard
• Data mine remaining 150 Webforms
• Give the Off-Crew access
• NIAPS ashore
• Connect Shore to Ship (two-way communication)
• Identify a solution for sending classified
  information (SIPR NIAPS)
• Develop automation

38
CBA Final Step

• FSA Support
• SMEs
• Tiger Team of warfare enterprise and provider
  functional area SMEs who produced the FNA top
  level requirements
• USFF N40, 41, 43, 70, 8
• CNO N4 and N6
• CNO N163
• PEOs EIS and C4I
• PMW 240 and 160
• FSA Progress
• DOTMLPF analysis 75 complete for afloat 0
  ashore
• Additional SME support highlighted above required
  to complete
• Last step integrates afloat/shore into
  comprehensive end-to-end analysis

39
JCIDS CBA Timeline (Revised 081203)
40
Backups
41
FY 08 Product Plan Review

• FY 08 execution included approx 2045K of
  carry-over from FY 07 for NIAPS installation and
  training
• Fleet Supports costs averaging 250K above
  Program Plan budget
• Included approx 400K in support to NSWC PHD for
  TRIDENT WARRIOR participation
• eRM transition from NSLC Mech to NSWC Crane
  resulted in one-time cost overlaps of approx 600K

42
FY 08 Product Plan Review
Delta reflects the 2M paid ahead in FY 07 for
NIPR installations and training
43
Revised Work Breakdown Schedule

• Defines NIAPS work in 8 functional areas
• Program Management
• Pilot Programs (including Join NIAPS for new
  application/content)
• NIAPS Software Engineering
• NIAPS Software Test Integration
• Accreditation (including IA requirements)
• Installations
• Infrastructure Support
• Fleet Software Support
• Provides greater fidelity than Product Plan
  descriptions
• Allows for identification of cost drivers and
  development of offset strategies

44
FY 09 NIAPS Program Cost Breakdown