Navy Data Environment NDE

1
Navy Data Environment (NDE) Navy Modernization
(NM) Project Update February 2002
2
Naval Message Aug 01 Timeline
14 Jan 02 FMPMIS-LOG, SPAWAR, AMPS, TAMS, LCRS
System Ready
19 Oct 01 TAMS, AMPS LCRS, SPAWAR functional
requirements
16 Apr 01 AIPS functions in NDE-NM
15 Jan 02- 22 Mar 02 Run FMPMIS Log Legacy in
Parallel Train Users
25 Mar 02 Shutdown Legacy FMPMIS logistics
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar
Apr
2
3
NDE Planned Completion Dates
27 Feb 02 SPAWAR, AMPS, TAMS functional
requirements
16 Apr 01 AIPS functions in NDE-NM
29 Mar 02 FMPMIS-LOG, SPAWAR, AMPS, TAMS, LCRS
System Ready
20 Dec 01 LCRS functional requirements completed
1 Apr 02- 07 Jun 02 Run FMPMIS Log Legacy in
Parallel Train Users
07 Jun 02 Shutdown Legacy FMPMIS logistics
Apr May Oct Nov Dec Jan Feb Mar Apr May Jun Jul
3
4
Navy Modernization State March 29, 2002
MC, NAVAIR, CG, Foreign, SWD
NDE
File update (xls) and Manual
NDE-NM AIPS FMPMIS
Send, all other alts missing from NDE and send BG
BL Locks
NDE sends alerts to CDMD-OA when alts are
approved.
CDMD-OA
SEA 53 AMPS
AMPS pulls Alteration information
CDMD-OA assigns work-files to clear alerts
Replication
TAMS updates Alt status
NDE-SIDE SPAWAR
TAMS SUBLANT/SUBPAC
LCRS pulls alteration information
LCRS-FMP AIRLANT/PAC
Non-CNO Avails
5
NDE-NM FMPMIS-LOG Detail

• Orig Curr Percent
• Availability Functions
• Security Changes to Support FMPMIS Sep 7 Sep
  7 100
• Create Avails (Adds) Jan 3 Dec 21 100
• Manage Avails (Edits) Jan 11 Feb 28 90
• Email Notification Jan 18 Mar 4 95
• Avail Change Process Approval Jan 18 Mar 4
  95
• Alteration Functions
• Finalize Use Cases Feb 15 Mar 4 75
• Program Add Alt, Edit Alt, Arch Alt, Feb 28 Mar
  29
• Program Assign Applicability Feb 28 Mar 29
• Material Functions
• Finalize Use Cases Feb 28 Mar 4 75
• Program Procurement, BOM, Supercede, Copy Mar
  29 Mar 29
• FMPLOG Replication for Prg/Exe Mar 29 Mar
  29 50
• FMPMIS LOG Ready for Beta Testing Mar 29 Mar 29
• Deployment Date Jun 7 Jun 7

5
6
NDE-NM FMPMIS-LOG Issues

• Business Process Changes
• None
• Resources
• New Programmer onboard and ready to start coding
  when Use Cases are finalized.
• Funding to Complete
• Funding Provided
• Risks
• Use Cases will not be completed until early March
  giving the design team only 17 days for
  programming.
• Critical Path
• Use Cases to be finalized and turned over to the
  programming team.
• Beta Testing training material needs to be
  developed before 25 March. NSLC is developing
  training.

6
7
NDE-NM SPAWAR Detail

• Orig Curr Percent
• NDE-NM to IDB replication Oct 26 Oct 26 100
• IDB to NDE-NM replication
• Purchase SUN 420 for NDE-SIDE Nov 29 Nov 29 100
• Convert IDB from SQL to Oracle server Jan 03
  Jan 30 100
• Create Triggers to link NDE and SIDE Jan 31 Jan
  31 100
• Create Audit Triggers based on NDE Jan 31 Jan
  31 100
• Purchase Oracle Advanced Replication Feb 11 Feb
  11 100
• Test Oracle Replication between NDE/NDE-SIDE Feb
  28 Feb 28
• Configure and Ship SUN 420 to SPAWAR Jan 14 Mar
  19 70
• Develop NDE-SIDE screens to identify Proposed Mar
  25 Mar 25 10 SPAWAR Alts for a Baseline
• Put into test and ready for Beta Testing Mar
  29 Mar 29
• Put IDB in Oracle Production Dec 21 Apr 15 67
• Put into Production Jun 7 Jun 7

7
8
NDE-NM SPAWAR Issues

• Business Process Changes
• Created a new business rule SPAWAR advanced
  alterations (AA) will not be visible to anyone
  outside SPAWAR. When it is transitioned from AA
  to PA it will become visible to the rest of the
  FMP community.
• In the process of changing the way SPAWAR alerts
  SEA 53 of changes to a battle-group baseline.
  Streamlining the process.
• Resources 4-SPAWAR and 2-NSLCPAC
  programmer/operations support
• Funding to Complete
• Funding has been provided by NAVSEA and SPAWAR.
• Risks
• Security accreditation for production running on
  NMCI at SPAWAR.
• Critical Path
• Need to establish Oracle Replication between
  NDE-SIDE and NDE
• Met with SPAWAR and SEA 53 on 19-22 February to
  finalize the architecture design of creating a
  baseline and managing a baseline (changes). This
  resulted in only one minor change to the SPAWAR
  IDB/NDE-SIDE process. SPAWAR needs to develop
  screen to identify proposed SPAWAR alts for a
  baseline.

8
9
NDE-NM LCRS Detail

• Orig Curr Percent
• LCRS to NDE-NM replication
• Identify data for LCRS-FMP to use Sep 7 Sep
  7 100
• Draft MOA for SEAR to connect to NDE Nov 2 Dec
  1 100
• Sign MOA for SEAR to connect to NDE Dec 1 Feb
  25 99
• Develop SQL against NDE-TEST ECD 1 month after
  funding resolved
• Test on NDE-TEST TBD
• Put into Production TBD

9
10
NDE-NM LCRS Issues

• Business Process Changes
• No process changes at this time.
• Resources
• Requires a PLSQL Oracle programmer for 1 month
• Funding to Complete
• Requirement identified by SSNN is 16K.
• Risks
• Funding issue
• Critical Path
• MOA between Newport News , NSLC, and NAVSEA ready
  for 04M signature
• SUPSHIP Newport News needs to assign programmers
  and build the SQL query.

10
11
NDE-NM AMPS Detail

• Orig Curr Percent
• Host AMPS Application
• Sign CONOPS Jul 27 Jul 27 100
• Order Server and Delivered Dec 1 Dec 1 100
• Establish Production Environment Jan 15 Feb
  22 100
• Export/Import Prod database Jan 18 Feb 22 100
• Ready for Beta Test Jan 25 Mar 29
• Ship Avail Data to AMPS Replication
• SURFLANT/SURFPAC official data identified
  (non-CNO) Feb 15 100
• SURFLANT/SURFPAC data integration Mar 15 25
• Change AMPS to read NDE-NM avail data Jan 29 Mar
  15 20
• Ready for Beta Test Jan 29 Mar 29
• BF Baseline Process
• Define Requirements (as is) Dec 29 Jan
  17 100
• AMPS/SPAWAR joint meeting Jan 17 Jan 17 100
• AMPS/SPAWAR joint design meeting Feb 20/21 Feb
  20/21 100
• Define Requirements (Conops) Dec 29 Mar 1 90
• Program Requirements Feb 28 Mar 29 10
• Ready for Beta Test Mar 29 Mar 29

11
12
NDE-NM AMPS Issues

• Business Process Changes
• Developed a method of creating a battle group
  baseline and then created a system of sending
  alerts from NDE when there are changes.
• Resources
• 1-SEA53 programmer, 1-NSLCPAC programmer (in
  place)
• Funding to Complete
• Provided by NAVSEA 04M and SEA53.
• Risks
• Security documentation needs to be created and
  approved before a certificate can be issued.
• SEA 53 may have requirements or data elements
  that require AMPS data to be upgraded to SECRET.
• Critical Path
• AMPS web application needs to be changed to
  review and process alerts and handle security
  requirements.
• NSLCPAC needs to complete security documentation
  and get IATO/ATO after security changes are made
  to the application.

12
13
NDE-NM Master Alt List Detail

• Orig Curr Percent
• Prototype of Master Alt List Functions
• Completed by NSLCJAX Jun 1 Jun 3 100
• CD turned over to NSLCPAC Jun 12 Jun 12 100
• Develop Functions in NDE-NM
• Develop requirements Dec 21 Mar 12 90
• Develop Use Cases Dec 21 Mar 25 75
• Determine data fields to add to NDE-NM Jan
  25 Mar 29 50
• Design screens for RMMCO edits Feb 22 Apr 12 50
• Test on NDE-TEST Feb 22 Jun 1
• Put into Production Mar 29 Jul 1

13
14
NDE-NM Master Alt List Issues

• Business Process Changes
• Need to determine the input rules of RMMCO.
• Ed Moe is documenting the as-is requirements of
  the RMMCO web application that runs today.
• Steve Walker (NSLCJAX) is creating Use Cases to
  outline what is needed.
• Resources
• Requires a functional person to integrate the
  requirements into NDE.
• Requires a Java/Web programmer for 4 months
• Funding to Complete
• Unfunded
• Risks
• New programmers coming online from Silverstream.
• Critical Path
• Ed Moe will not be finished with documentation
  until 12 March.
• Steve Walker will not be finished with Use Cases
  until 25 March (based on Eds 12 March estimate).

14
15
NDE-NM TAMS Detail

• Orig Curr Percent
• Identify TAMS Functions (the Matrix report)
• Create Requirements for TAMSLANT Oct 19 Dec
  14 100
• Create Requirements for TAMSPAC Oct 19 Feb
  22 100
• Sign MOA between TAMSLANT and NDE Oct 19 Mar
  8 90
• Sign MOA between TAMSPAC and NDE Oct 19 Mar 8 90
• Develop Functions in NDE-NM
• Create interface between TAMSLANT and NDE Jan
  14 Mar 29 50
• Create interface between TAMSPAC and NDE Jan
  14 Mar 29 50

15
16
NDE-NM TAMS Issues

• Business Process Changes
• SUBLANT/SUBPAC will be sending data element
  updates to NDE-NM for their alterations.
• Resources
• No additional resources required at this time.
• Funding to Complete
• Funding requirement 15K (travel and meetings
  with SUBLANT/SUBPAC provided by NAVSEA 04M).
• Risks
• Requirements for both SUBLANT and SUBPAC now
  documented
• Critical Path
• SUBLANT/SUBPAC MOA draft sent for final review
• SUBPAC visit completed

16
17
NDE-NM Summary

• Integration Area Level of
  Confidence
• Ready for Beta 29 Mar 02
• FMPMIS-LOG HIGH
• SPAWAR HIGH
• LCRS-FMP MED
• Behind in developing database link
• AMPS MED
• Finished Spec but security may take time
• Master Alt List LOW
• Still in process of developing specs and use
  cases
• TAMS HIGH
• Work in process for SUBLANT and SUBPAC

17
18
 
NDE Navy Modernization Program Review Action
Items Date of meeting 19 Dec
01 Updated 2/22/02
Program Review 3 Actions   3-1.
Investigate what efforts are underway by SPAWAR
to support the Fleet in building a data base
system to assist with scheduling. Action SPAWAR
04 Complete. Websched is not ready for
implementation. At this point, the plan is for
VIPER to be the starting point for the data load
and then CNSL/CNSP will massage it with updated
information to which they are privy. In the
meantime, the NDE team is working with CNSL/CNSP
to integrate scheduling data found in an Excel
file on the SPEAR website into NDE. 3-2. SPAWAR
provide ECD for developing the functional spec
for their CCB process. Action SPAWAR 04
ECD 25 April 2002 (Ray Thompson and Joe
Berkley)   3-3. Send Master List requirements
and Use Cases to Mr. Klein at SPAWAR. Action
NSLC Pac Awaiting final Master List
requirements from AMP office. 3-4. Provide
deployment date for FMPMIS Logistics at next
Program Review Action NSLC Pac June 7  
Program Review 2 Actions All have been
completed.  
19
Program Review 1 Open Actions   1.1 The
process of VIPER sending non-CNO availability
information and BG composition to NDE-NM needs to
be researched. Action NSLC PAC. STATUS
Complete.   1.2. NAVSEA must coordinate/develop
business rules for SPAWAR Proposed Alts. Action
SEA 04M3. STATUS SPAWAR creates PA
alterations. SPMs transition from PA to SA/AER.
Only SPAWAR 04 modifies SPAWAR alteration
equipment brief descriptions. SPMs will no longer
be able to add or delete SPAWAR equipment
alterations. Use case has been developed and
will be adjudicated week of 25 Feb.   1-3.
SPAWAR MOA must be signed. Action SPAWAR 04/ SEA
04M.. STATUS Complete. Signed 1/25/02.  
1-4. Need to resolve issues regarding how the
BG baselines are established and locked. How are
routine changes made? How are emergent changes
made? Review AMPS CONOPS. Action SEA 04M3 lead..
STATUS Complete. A meeting was held 17 and 18
Jan, in San Diego to discuss the BF CCB
functional business rules. A follow-on meeting
was held 19-22 Feb to finalize the Use Cases for
managing BGs.   1-5. NDE NM/SEAR MOA must be
signed by NSLC. Action NSLC PAC. STATUS Capt
Odom has signed. Capt. Violette signed 2/22.
Enroute to SEA 04M. 1-6. Provide a
functional requirements document for AMPS.
Action SEA 53. STATUS Complete. Use cases
have been completed. 1-8.1-7. Necessary funds
must be provided to NSLC PAC to support NDE NM
advertised timeline in the Aug 01 NAVSEA message.
Action NAVSEA 04M, SPAWAR 04, and SEA 53.
STATUS Complete. NSLC PAC has been funded
satisfactorily.