NAVY STANDARD INTEGRATED PERSONNEL SYSTEM (NSIPS)

The Navy Standard Integrated Personnel System (NSIPS) will consolidate the Navy active and reserve field source personnel data collection systems, both ashore and afloat. The objective is to produce a standard, single point of entry system for all personnel and pay information. The primary interfaces for NSIPS will be with systems of the Defense Finance and Accounting Service (DFAS). NSIPS provides pay and personnel functionality for the Navy reserve force in Release 0 and for the Navy active force in Release 1. The client-server architecture will have information stored at the local level and at the regional level. A corporate-level data base will be used for planning and analysis purposes.

In 1997, the PM developed a prototype system to prove out the planned architecture and "user friendliness" of the graphical user interface. PeopleSoft® was selected as the basic human resource software package. This package was customized and the Navy requirements were incorporated in Release 0 to address the Navy reserve requirements. The Release 0 OPEVAL began in mid-September 1999. Many deficiencies were noted, including inaccurate transmittal logs, missing e-mail functionality, corrupted reports, and inadequate training. The PM immediately developed a plan of actions to address these shortcomings. Beginning in October 1999, three separate software builds were installed to fix the problems and OPEVAL resumed in November 1999. In January 2000, DOT&E concurred with COMOPTEVFOR's conclusion that NSIPS Release 0 is operationally effective and operationally suitable and recommended approval for fleet introduction. NSIPS Release 0, which replaced the Reserve Standard Training, Administration, and Readiness Support (Manpower and Personnel) System, is currently operational at 260 reserve sites.

In June 2000, the PM announced a four-month schedule slip in software development and proposed that Release 1 be delivered in two separate increments. The first increment (Release 0.2) would address personnel actions and the second increment (Release 1) would address pay actions for the Navy active force. Each increment would undergo a full operational evaluation.

Operational evaluation of Release 0.2 was conducted during the period April 23 to May 4, 2001. Operational evaluation of Release 1 is scheduled for February 2002, with a fielding decision expected in May 2002. Full operational capability is planned for July 2002.

The OPEVAL results of Release 0.2 indicated that two effectiveness and eight (of ten) suitability critical operational issues were resolved satisfactorily. Interoperability and documentation were found unsatisfactory. Corrections were subsequently made and a follow-on test was conducted from July 9-27, 2001. Test results of the follow-on evaluation indicated that previously identified deficiencies had been corrected.