Navy Data Environment NDE

1
Navy Data Environment (NDE) Navy Modernization
(NM) Program Review 8 March 2005
2
NDE NM Time Line
Business Rule Initiation
General Availability Release
November
September
September
December
February
February
October
January
January
August
August
March
March
April
April
May
June
May
June
July
July
2nd Q 2004
3rd Q 2004
1st Q 2005
4th Q 2004
2nd Q 2005
3rd Q 2005
4th Q 2005
Inception Phase
Construction Phase
Elaboration Phase
Life Cycle PPI
-
Transition Phase
3
Ship Change Document - Release 1.7Release 1.7
was split into two different releases at the
request of the sponsor in order to expedite a
capability (in bold below) to the fleet.

• PR5 PR6 PR7 ACTUAL
• SCD Release 1.7
• AFOM Mouse Over 3 Left Columns New/TBD 1/07/05
  1/10/05
• CBA Add Claimant to CBA New/TBD 1/10/05 1/14/05
  
• Mods to Distributed Systems (II, IIa,
  III) New/TBD 1/12/05 1/12/05
• Mods to make POC Info avail in
• Phases II, IIa, III 1/14/05 1/12/05
• Mod to input Legacy Alt Identifier 1/19/05 1/25/
  05
• AFOM Add additional Comment fields New/TBD 1/21/
  05 Cancelled
• Update Help Pages (Reflect changes) 2/11/05 1/25
  /05
• SCD Update Export (Reflect changes) 2/11/05 1/26
  /05
• Release to test/testing TBD TBD 2/16/05 1/27/05
• Release to production TBD TBD 2/23/05 2/3/05

4
Ship Change Document - Release 1.7.1

• PR5 PR6 PR7 ACTUAL
• SCD Release 1.7.1
• SCD Split by Carriers PEO Ships
• (multiple POCs, AFOMs, CBAs, etc.) New/TBD TBD 1/
  28/05 Cancelled
• Develop ADMIN Module 1/14/05 Postponed
• Changes to Ordinal Values for AFOM 2/11/05 2/09/
  05
• SCD Split by multiple classes
• (subset Phase IIa III Indiv. SCD data)
  New TBD 2/11/05 2/23/05
• CBA Comment NEW 2/15/05
• Update Help Pages (Reflect changes) 2/11/05 2/22
  /05
• SCD Update Export (Reflect changes) 2/11/05 2/22
  /05
• Additional Help/Support Files 2/22/05
• Release to test/testing (Reflect changes)
  3/02/05
• Release to production (Reflect changes)
  3/09/05

5
Secure NDE-NM Environment Establish Secure
Operations
6
Entitled Process StatusPath to Success

• During the month of February, the NDE NM PM
  directed an administrative pause for the
  leadership in order to resolve schedule, cost and
  contractor issues.
• On 11 FEB 05, NDE NM Senior Leadership were
  briefed on five different options by NSLC. Each
  option provided a different way to develop and
  implement the NDE NM EP software/system.
• On 22 FEB 05, NDE NM Senior Leadership decided to
  pursue Option 3.
• Option 3 requires an estimated total cost of
  761,362.00, with an estimated funding allocation
  of 447,648.00 for ASC development support and
  estimated required additional funding amount of
  332,362.00.
• Option 3 will take approximately 2.5 weeks longer
  than original deployment date of 10 JUN 05,
  resulting in deployment on 27 JUN 05.

7
Entitled Process StatusPath to Success -
Continued

• Part of the funding for Option 3 will be
  allocated by a re-direction of funding at NSLC
  PAC and the remaining amount (332,362.00) will
  be funded by NAVSEA 04RP.
• Option 3 consists of a blended development team
  between NSLC, iBASEt, Arrowpoint and
  ASC/Noblestar. NSLC is the lead for development
  with iBASEt as the Prime Contractor.
• NSLC and iBASEt have successfully negotiated a
  SOW with ASC.
• iBASEt is awaiting a detailed cost estimated from
  ASC in order to issue a sub-contractor task
  statement.
• On 03 MAR 05, NSLC was formally assigned full
  time as the NDE NM EP Project Manager.
• On 10 MAR 05, NAVSEA 04RP13 was formally assigned
  as the full time NAVSEA Action Officer on behalf
  of NAVSEA 04RP.

8
Entitled Process StatusPath to Success -
Continued

• Since NAVSEA 04RP13 and NSLC were formally
  assigned
• Roles and Responsibilities have been defined.
• Communications have improved between the
  government and contractor team members.
• Daily development meetings are occurring.
• Rigorous tracking of all POAM items and issues
  is in effect.
• Prompt reporting is now occurring.
• A Risk Manager has been identified, NAVSEA
  04RP13.
• Complexity of Use Cases for Beta is currently
  being reviewed.
• On 10 MAR 05, PEO SHIPs approved deletion of six
  use cases and the addition of four use cases for
  Beta.
• Option 3 POAM is actively being refined and
  coordinated to reflect the above changes.

9
Roles and Responsibilities

• NAVSEA Program Manager/Sponsor NAVSEA 04RP
• NAVSEA NDE NM EP Action Officer NAVSEA 04RP13
• NAVSEA NDE NM EP Requirements SME PEO SHIPs
• NDE NM Secure Proj Mgr NSLC
• NDE NM (Legacy) Proj Mgr NSLC
• NDE NM Interim SCD Proj Mgr NSLC
• NDE NM Entitled Process (EP) Proj Mgr NSLC
• NDE NM EP Risk Manager NAVSEA 04RP13
• NDE NM EP Configuration Manager NAVSEA 04RP
• NDE NM EP Requirements/Design/Test Contractor
  Lead ASC
• NDE NM EP Development Lead NSLC
• NDE NM EP Development Contractor Lead iBASEt

10
Entitled Process Software Development Status

• Orig PR3 PR 5 PR 6 PR7 Actual Current
• Inception Phase
• Navy Approval of Inception Products 9/1/04 9/1/04
  9/1/04 9/1/04 9/1/04 9/1/04 Complete
• Elaboration Phase
• Alpha 1 SME Inputs to ASC 10/01/04 10/01/04 10/01/
  04 10/01/04 10/01/04 10/01/04 Complete
• Alpha 1 Requirements to NSLC 10/04/04 10/08/04 10/
  08/04 10/08/04 10/8/04 10/8/04 Complete
• Alpha 1 Software Release 11/08/04 11/08/04 12/30/
  04 12/30/04 12/30/04 12/30/04 Complete
• Alpha 1 Code Rework 4/15/05
• Alpha 2 SME Inputs to ASC 1/21/05 1/21/05
  1/21/05 1/13/05 1/13/05 1/13/05 Complete
• Alpha 2 Requirements to NSLC 12/4/04
  1/28/05 1/28/05 1/28/05 1/28/05 1/29/05
  Complete
• Alpha 2 Software Release 1/10/05 2/25/05 2/25/05
  2/25/05 4/15/05 Caution 5/12/05
• Elaboration Product Delivery 11/29/04 2/27/05 2/27
  /05 2/27/05 2/27/05 2/25/05 Complete
• Process Business Rule Update 11/29/04 2/27/05 2/27
  /05 2/27/05 2/27/05 2/25/05 Complete
• Navy Approval Elaboration Products 12/13/04 3/20/0
  5 3/20/05 3/20/05 3/20/05 On Target 3/20/05
• Construction Phase
• Beta SME Inputs to ASC 3/23/05 3/23/05 3/23/05
  4/12/05 4/12/05 Caution 4/12/05
• Beta Requirements to NSLC 2/21/05 4/1/05 4/1/05
  4/1/05 4/25/05 Caution 4/29/05

Note Red dates indicate any change from the
previous months PR Briefing.
11
Alpha 1 Development Status

• Schedule Orig PR5 Actual
• Alpha 1 SW Release 11/08/04
  12/30/04 12/30/04
• Use Cases
• Vote on Change
• Tally Vote
• Calculate Secondary Voting Options
• Issue Code rework needed
• Alpha 1 Code Review completed by SPAWAR/iBASEt
• Alpha 1 Code Review Report provided to NSLC on
  1/28/05
• Report recommends changes at NSLC
• NSLC implementing recommendations
• Alpha 1 code rework scheduled for 3/28/05 -
  4/15/05 in current POAM

12
Alpha 2 Development Status

• Schedule Orig Current
• Alpha 2 SW Release 1/10/05 5/12/05
• Use Cases being provided in Blocks
• Block 2 (Development) 5/4/05
• Initiate Idea
• Submit Ship Change
• Assign Responsibility
• Edit Ship Change
• View Ship Change
• Block 3 (Development) 4/27/05
• Perform Technical Assessment
• Find Ship Change
• Perform AFOM Review
• Perform CBA Review
• System Testing 5/06/05

13
Beta/General Availability Release (GAR)
Development Status

• Schedule Orig Current
• Beta SW Release 3/21/05 6/9/05
• GAR SW Release 4/11/05 6/27/05
• Use Cases being provided in Blocks
• Block 6 (Development) 5/19/05
• Login
• Endorse Funding Line
• Find NDE User
• Add CBA Data
• Refactor Funding
• Block 7 (Development) 5/19/05
• Manage Contact Lists
• Assign Individual to Position
• Define Position Characteristics
• Notification of Action

14
Beta/General Availability Release (GAR)
Development Status - Continued

• Schedule Current
• Block 8 (Development) 5/31/05
• Process Administrator Actions
• Set AFOM Weights
• Raise for Vote
• Close Ship Change
• Archive Ship Change
• Run Adhoc Report
• Block 9 (Development) 5/31/05
• Archive Ship Change
• Move SCD Backward in Process
• Extend SCD Time Window
• Zero Out Voting Results

15
Beta/General Availability Release (GAR)
Development Status - Continued

• Schedule Current
• Beta Code Complete/SW Release 6/09/05
• Baseline Code Complete 6/17/05
• User Acceptance Test Complete 6/24/05
• Migrate Data from SCD Complete 6/27/05
• Go Live/GAR SW Release 6/27/05

16
Entitled Process Use Cases
Future Enhancements to Entitled Process Software
Expert Tool Functionality (3)
Advanced Automated Support (12)
Advanced Reporting (3)
Advanced Admin Reporting (11)
Post DP 3 Functionality (1)
Baseline Entitled Process Software
Alpha 1 Software Release (3 Use Cases)
Alpha 2 Software Release (9 Use Cases)
Beta Software Release (18 Use Cases)
17
Entitled Process Use Cases (Detailed)
Future Enhancements to Entitled Process Software
CBA Calculation Tool
TA Determination Tool
AFOM Decision Tool
Handle Conjunctive Alterations
Handle Trade Off Funding
Modify Ship Change (Post DP 3)
Raise for Vote
Modify Funding Level (budget line up/down)
Expert Level SCD Search
Handle Capability Alteration
Display Dashboard
Auto Notification of Action
Advanced Admin Reporting (14)
Auto Populate FMP
Request Ship Change Withdrawal
Rework
Baseline Entitled Process Software
Perform AFOM
Adjudicate Funding
Assign Responsibility
Admin Reporting (11)
Initiate Idea
Perform CBA
Prioritize FMP
Tally Vote
Find Ship Change
Edit Ship Change
Vote on Change
Perform Technical Assessment
Refactor Funding
Submit Ship Change
View Ship Change
Calculate Secondary Voting Options
Linked Ship Change
Login
Notification of Action
Endorse Funding Line
Raise for Vote
18
Entitled Process Use Case Descriptions Alpha 1
19
Entitled Process Use Case Descriptions Alpha 2
20
Entitled Process Use Case Descriptions Beta
(Blocks 6 and 7)
21
Entitled Process Use Case Descriptions Beta
(Blocks 8 and 9)
22
Entitled Process Activity Use Cases
Note1 Finalize Assessment SCD has been removed
and its functionality has been distributed to
other use cases.
23
Admin Reporting Use Cases

Note 1 Administrator Adjust SCD and Create
Ad Hoc Report Use Case functionality will be
used to implement future automation opportunities
within the Baseline software. Note 2 Assign
Voting Board Members, Implement Pick Lists, and
Save Ad Hoc Reports Use Case functionality have
been absorbed into other Use Cases Note 3
Administrator Adjust SCD has been moved from
Alpha 2 to Beta Release to facilitate meeting
Alpha 2 schedule and New Find NDE User use case
has been added
24
Software Development
Note 1 Number of Use Cases indicates total
number of Use Cases identified as part of
Baseline Entitled Process Software. Second
number of Use Cases indicates number of Use Cases
that are currently fully populated (i.e. Baseline
will have 28 Use Cases and 15 are currently
populated or 28/15). Note 2 Current Values
reflect actual values at the time of the brief
while values for various phases will not change
from the initial Inception Phase estimates. Note
3 December Estimates based on end of January
rather than 14 January.
25
Entitled Process Software Development

• The following Risks are currently being managed

E D C B A
PROBABILITY

• 2 3 4 5
• IMPACT

26
Entitled Process Software Development

• (9) identified risks

27
Risks

• Purchase Order for ASC from iBASEt needs to be
  awarded, iBASEt awaiting final detailed costs
  from ASC. Action Officers iBASEt/ASC Suspense
  date 16 MAR 05 Probability B Impact 3
  Risk M
• ASC Development Environment implementation not
  complete Second server on order for ASC, upon
  receipt second server will need to configured by
  NSLC PAC for security/network. Troubleshooting
  in progress between NSLC PAC and ASC for remote
  connectivity for (3) laptops, System Interconnect
  Agreement (SIA) depicting architecture needs to
  be reviewed (ASC, iBASEt) and approved (NSLC DAA)
  in compliance with Navy Firewall Policy or manual
  solution needs to be agreed upon. Action
  Officers NSLC/ASC Suspense Date 25 MAR 05
  Probability C Impact 4
• Risk M
• 3. Oracle 8.1.7 in use at NSLC needs to be
  fully upgraded to Oracle 10G across all NDE EP
  platforms. Transition plan in development.
  Potential impact to legacy systems being
  assessed. Action Officer NSLC PAC IT
  Department Suspense Date (Transition Plan) 15
  APR 05 Cutover TBD Probability C Impact
  4 Risk M
• 4. Address all IA activities with NSLC PAC ISSM
  and document further detailed steps in POAM,
  review draft SSAA. Action Officers NSLC PAC
  ISSM Suspense date 08 APR 05 Probability B
  Impact 3 Risk M
• 5. Develop plan for Data Migration to address
  the Interim SCD and POM 06 (Access database)
  data. Action Officer NSLC Suspense date 25
  APR 05 Probability C Impact 3 Risk M

28
Risks - Continued

• Configuration Management need to consistently
  and rigorously adhere to current Configuration
  Management Plan (CMP). Action Officer NDE EP
  Configuration Manager Suspense Date 15 MAR 05
  Probability A Impact 3
• Finalize POAM baseline to include IT activities
  required, more IA detail, more data migration
  details, refinement of use case activities/level
  of complexity, capturing government acceptance
  tasks/dates for contractor deliverables, etc.
  Gain approval of POAM. Action Officer NSLC
  Suspense Date 25 MAR 05 Probability A
  Impact 4
• Risk Management (RM) Plan needs to be reviewed by
  the team and validated through the newly assigned
  Risk Manager. Scope of the RM Plan needs to
  include all aspects of the EP project not just
  requirements and design. Risk Management tool
  (Risk Radar) needs to be reviewed for use and if
  approved needs to be utilized. Training will
  needs to be conducted. Action Officer NAVSEA
  04RP13 Suspense Date 01 APR 05 Probability A
  Impact 3
• 9. System Testing Need to ensure/track
  that when the time comes for testing that all
  parties involved have the appropriate technical
  solution and access required, when the System
  Test plan is in final draft it will need to be
  reviewed and approved and personnel required to
  support testing need to be identified. Action
  Officer ASC Suspense Date 15 APR 05
  Probability B Impact 4

29
Barriers

• Continued evolution of the Interim SCD may
  introduce requirements/resource conflicts
• Finalizing level of detail in existing Business
  Rules
• Finalizing Graphic User Interface (GUI)
• Ensuring we do no harm
• Need to be able to accommodate Program and
  Execution Modules for Budget
• Need to integrate Access Database into entitled
  NDE
• Need to manage legacy data already in NDE
• Need to address interim transition of SCDs into
  NDE Logistics, Phase IV functionality

30
The Way Forward

• Rigorous Requirements Management by PM
• Interim SCD evolution limited to Release 1.7.1
• Follow strong/disciplined Change Management (CM)
  process
• SMEs working to finalize details of Business
  Rules and GUIs
• Integration Team making progress on the
  following
• Program and Execution issues
• Access Database requirements
• Data elements being identified
• Use Cases being developed
• Initial POAM developed and staffed out for
  comment
• Management of legacy data
• Logistics transition issues

31
Entitled Process Cost ASC Total
32
Entitled Process Cost NSLC Total
33
Entitled Process Cost Total
34
NDE-NM Summary

• Functional Area Level of
  Confidence
• Ship Change Document
• Release 1.7 Feb 3, 2005 Complete
• Release 1.7.1 Mar 9, 2005 Complete
• Secure NDE-NM Environment
• Operational Feb 22, 2005 Complete
• Secure AMPS NITRA (1-way) TBD MEDIUM
• Entitled Process
• Inception Phase Sept 1, 2004 Complete
  Approved
• Elaboration Phase May 12, 2005 MEDIUM
• Construction Phase June 9, 2005 MEDIUM
• Transition Phase June 27, 2005 MEDIUM

35
NDE PROGRAM REVIEW ACTION ITEMS
W3s from 10 Jan 2005
W3s from 10 Jan 2005
W3s from 14 Dec 2004

36
NDE PROGRAM REVIEW ACTION ITEMS
W3s from 13 October 2004
W3s still active from 14 July 2004
37
Questions?