PPT Presentation

1
Navy Data Environment (NDE) Navy
Modernization Project Update 19 September 2001
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
Navy Modernization State January 15, 2002
MC, NAVAIR, CG, Foreign, SWD
File update (xls) and Manual
NDE
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
CDMD-OA assigns work-files to clear alerts
AMPS pulls Alteration information
IDB pulls standard table queries, Avail, Ship,
data via SQL query
LCRS pulls alteration information
IDB sends SPAWAR alteration updates via
Replication
LCRS sends status updates, No adds, no deletes.
SPAWAR IDB
LCRS FMP
VIPER
VIPER sends in avail information and BG
composition
4
NDE-NM Major Milestones

• FMPMIS-LOG
• Availability Functions Sep 4-Sep 28
• Alteration Functions Oct 2 - Dec 15
• Material Functions Oct 2 - Dec 15
• SPAWAR
• NDE-NM to IDB replication Sep 4 - Oct 26
• IDB to NDE-NM replication Oct 26 -Nov 30
• BF/BG Availability Data to NDE-NM Dec 1 - Dec
  15 replication
• SPAWAR IDB Functions running off NDE Aug 2002
• LCRS-FMP
• LCRS to NDE-NM replication Sep 4 - Dec 15

4
5
NDE-NM Major Milestones

• AMPS
• Host AMPS application Jul 27 - Oct 26
• BF/BG Availability Data to AMPS Nov 7 - Dec
  10 replication
• NDE-NM to AMPS replication Nov 7 - Dec 10
• BF tag/flag link to NDE-NM Nov 7 - Dec 10
• Master Alt List
• Unknown TBD
• TAMS
• Create Matrix Report TBD
• Integration Beta Test
• Identify Tests/Training/Ready Date Jan 14, 2002

5
6
NDE-NM FMPMIS-LOG Detail

• Availability Functions Sep 4-Sep 28
• Security Changes to Support FMPMIS Sep 4 -Sep 7
  100
• Create Use Case Sep 7 - Sep 16 100
• Create Avails (Adds) Sep 10 - Sep 17 100
• Manage Avails (Edits) Sep 17 - Sep 19 10
• Email Notification Sep 19 - Sep 21
• Avail Change Process Approval Sep 24 - Sep 28
• Alteration Functions Oct 2 - Dec 15
• Tasks not started
• Material Functions Oct 2 - Dec 15
• Tasks not started
• FMPLOG Replication for Prg/Exe Nov 1 - Dec 15

6
7
NDE-NM FMPMIS-LOG Issues

• Business Process Changes
• Recommend NAVSEA not input SA AER alterations
  for SPAWAR equipment and only be allowed to
  transition from SPAWAR Proposed SA AER
  alterations.
• Resources
• Currently have 4.5 programmers working on the
  project.
• Need a PLSQL Programmer for the next 5 months
• Need a Java/Web Programmer for the next 4 months
• Funding to Complete
• First Quarter FY02 Funding Requirements 237,750
• Risks
• Design team that is working FMPMIS integration is
  the same team that is doing defect programming
  for NDE-NM (AIPS) functions.
• Funding
• Impact
• Without additional programming support,
  FMPMIS-Log will not be integrated by January 15,
  2002.

7
8
NDE-NM SPAWAR Detail

• NDE-NM to IDB replication Aug 27 - Oct 26
• Identify data to replicate Aug 27-Aug 30 100
• Develop SQL against NDE-DEV Sep 4 - Sep 21 42
• Develop DB Link (IDB-NDE-NM) Sep 24 - Sep 24
• Test on NDE-TEST Sep 25 - Sep 28
• Put into Production Oct 1- Oct 1
• IDB to NDE-NM replication Oct 26 -Nov 30
• Identify data to replicate Oct 9 - Oct 12
• Develop SQL against IDB Oct TBD
• Develop PLSQL code to pull changes Nov TBD
• Test on NDE-TEST Dec TBD
• Put into Production Dec 15 - Dec 15
• BF/BG Availability Data to NDE-NM Dec 1 - Dec 15
• Tasks not started
• SPAWAR IDB Functions running in NDE Aug 02
• Tasks not started

8
9
NDE-NM SPAWAR Issues

• Business Process Changes
• Recommend SPAWAR input alteration data into IDB
  only during transition. IDB will replicate to
  NDE-NM. Today there are 2 ways to get data into
  NDE-NM.
• Resources
• SPAWAR is providing 2 programmers
• NAVSEA is providing 1 programmer (30k) and a
  Replication Server (85k)
• Funding to Complete
• SPAWAR paid at the end of 4th quarter for
  integration support
• First Quarter NAVSEA Funding Requirements 115k
• Risks
• NAVSEA funding will be required in Oct to
  purchase replication server to support this
  effort.
• MOA for DB Link between NDE-NM and IDB needs to
  be signed
• Impact
• SPAWAR integration could be accomplished without
  replication server, but connectivity is slow and
  would delay the project by 4-6 months.

9
10
NDE-NM LCRS Detail

• LCRS to NDE-NM replication Sep 4 - Dec 15
• Identify data to replicate Sep 4 - Sep 7 100
• Develop SQL against NDE-TEST Sep 7 - Oct 2
• Develop Triggers for LCRS Oct 2 - Oct 30
• Develop PLSQL replication procedures Oct 30- Nov
  19
• Develop DB Link (LCRS-NDE-NM) Nov 20 - Nov 20
• Test on NDE-TEST Nov 30 - Dec 15
• Put into Production Dec 15

10
11
NDE-NM LCRS Issues

• Business Process Changes
• No process changes at this time.
• Data columns that will replicate from NDE-NM to
  LCRS-FMP and vice versa have been identified.
• Resources
• Requires a PLSQL Oracle programmer for 1 month
• Funding to Complete
• First Quarter NAVSEA FY02 Funding Requirements
  12,600
• Risks
• NDE-NM has not been registered in the 8030
  database, and LCRS will not connect to NDE-NM
  until NDE-NM is legal.
• NDE-NM/SEAR MOA has not been signed by NSLC.
  Still in review with NSLCLANT security office.
• Impact
• No work can be legally done on NDE-NM without
  8030 registration.
• Without a signed MOA, Newport News will not allow
  replication.

11
12
NDE-NM AMPS Detail

• Host AMPS Application Jul 27 - Dec 10
• Sign CONOPS Jul 27 100
• Order Server Oct TBD
• Establish Production Environment Nov TBD
• Export/Import Prod database Nov TBD
• Put into Production Dec TBD
• BF/BG Avail Data to AMPS Sep 7 - Dec 10
• Contact VIPER/SPAWAR Sep 7- Sep 10
• Develop SQL against NDE-DEV Oct TBD
• Develop file transfer process Oct TBD
• Test on NDE-TEST Nov TBD
• Put into Production Dec TBD
• NDE-NM to AMPS replication
• Tasks not started

12
13
NDE-NM AMPS Issues

• Business Process Changes
• Need to define the business rules for locking
  baseline amps configuration alterations. What
  can be edited on an alteration after it is
  locked?
• Resources
• NAVSEA is providing hosting cost of AMPS for
  8,200
• SEA 53 is providing 1 ASP programmer, cost
  75,000
• NAVSEA is providing 1 NT/IIS web server, cost
  10,000
• NAVSEA is providing 1 PLSQL programmer, cost
  3,560
• Funding to Complete
• First Quarter FY02 NAVSEA Funding Requirements
  21,760
• First Quarter SEA 53 Funding Requirements
  75,000
• Risks
• No funding and there are no functional
  requirements
• Impact
• Funding must be provided in Oct, or integration
  with AMPS can not be accomplished by Jan 2002.

13
14
NDE-NM Master List Detail

• Prototype of Master List Functions
• Completed by NSLCJAX
• CD turned over to NSLCPAC
• Develop Functions in NDE-NM
• Determine data fields to add to NDE-NM
• Design Screens
• Test on NDE-TEST
• Put into Production

14
15
NDE-NM Master List Issues

• Business Process Changes
• Need to determine the input rules of RMMCO. If
  they find something wrong can they update the
  alteration data or do they just put comments in
  an appropriate remarks field.
• Resources
• Requires a Java/Web programmer for 4 months
• Funding to Complete
• First Quarter NAVSEA FY02 Funding Requirements
  57,600
• Risks
• No funding
• Impact
• Without funding Master List functions will not be
  incorporated but other integration could
  continue.

15
16
NDE-NM TAMS Detail

• Identify TAMS Functions (the Matrix report)
• Pam Smith will visit SUBLANT
• NSLCPAC will contact SUBPAC
• Develop Functions in NDE-NM
• Determine data fields to add to NDE-NM
• Design Screens
• Test on NDE-TEST
• Put into Production

16
17
NDE-NM TAMS Issues

• Business Process Changes
• Unknown at this time.
• Resources
• May require Web programmer
• Funding to Complete
• First Quarter NAVSEA FY02 Funding Requirements
  Unknown
• Risks
• Funding
• Impact
• Other Integration can continue without TAMS.

17
18
NDE-NM Action List Summary

• NAVSEA 04M
• Issue Policy on SPAWAR equipment alterations (PA,
  SA, AER).
• Provide First quarter funding in Oct FY03
• NSLC
• Get NDE-NM registered in the 8030 database
• Sign SEAR MOA (LCRS-FMP)
• Sign SPAWAR MOA
• SPAWAR
• Continue support of integration of IDB into
  NDE-NM.
• Provide 2 SPAWAR programmers for integration
  effort
• SEA 53
• Provide 1 programmer for integration efforts of
  AMPS.
• Provide a functional requirements document for
  AMPS.

18
19
NDE-NM Summary

• Integration Area Level of
  Confidence
• to complete by 15 Jan 02
• FMPMIS-LOG LOW
• The team needs a PLSQL programmer
• No funding identified
• SPAWAR-IDB HIGH
• LCRS-FMP MED
• Newport News is waiting for Registration number
  of NDE-NM.
• AMPS MED
• No funding identified
• Master List LOW
• No funding identified
• TAMS Unknown

19