UNITED24 - Make a charitable donation in support of Ukraine!

Military


 DOT&E

Director, Operational Test & Evaluation
  
FY97 Annual Report

FY97 Annual Report

STANDARD PROCUREMENT SYSTEM (SPS)

DLA (lead) Joint ACAT IAM Program
Total program cost (TY$) $325M
Life cycle $2,896M
Full-rate production 4QFY01

Prime Contractor
American Management systems, Inc.
(AMS)

SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010

The Standard Procurement System (SPS) will improve the speed and effectiveness of contract placement and contract administration functions, interact more effectively with other DoD activities, and with industry, and improve visibility of contract deliverables while maintaining DoD readiness with reduced resources.

SPS will comprise components at multiple levels, including mainframe processing at a Megacenter, minicomputers at the intermediate level, and local area network-based workstations. Software will consist of selected DoD/COE operating systems, network operating systems, client-server software, distributed systems software, and AMS commercial-derivative software.

Each Service and Agency must provide the underlying infrastructure to host the SPS application software. Although SPS must accommodate Electronic Commerce/Electronic Data Interchange (EC/EDI) transactions, each Service and Agency must provide SPS the access to EC/EDI gateways. SPS supports the JV2010 operational concept of focused logistics by enabling Defense agencies to work more effectively with the civilian sector in procurement activities.


BACKGROUND INFORMATION

The SPS acquisition strategy is based on procuring and enhancing AMS' Procurement Desktop - Defense (PD2) software. AMS has four years and four increments in which to provide full SPS functionality. Increment 1 offers basic system functionality upon which successive increments will build. Increments 2 through 4 will provide increased functionality, including existing legacy procurement systems interfaces.


TEST & EVALUATION ACTIVITY

The Joint Interoperability Test Command (JITC) conducted Initial Operational Testing (IOT) in compliance with an approved Test and Evaluation Master Plan (TEMP) on Increment 1 in February-March 1997. JITC documented test findings in May 1997 in an Independent Evaluation Report (IER), stating that Increment 1 was operationally effective and suitable. DOT&E concurred with JITC's findings, and Increment 1 was fielded to select Defense Logistics Agency (DLA) and Navy sites.

JITC conducted Follow-on Operational Testing (FOT) on Increment 2 in July-August 1997. JITC documented findings in an IER in late October 1997. Three days after the completion of Increment 2 OT, the SPS Program Office sought an early fielding decision for Increment 2 with help from the ASD(C3I) Action Officer (AO). On such short notice, JITC was able to provide only emerging results. Those results described 35 major system deficiencies associated with open Priority 2 (P2) trouble reports. Developmental testers acknowledged that the P2s existed, and were either incorrectly categorized as P3s or lower during developmental testing, or had not been closed out as was reported at the Increment 2 OTRR. DOT&E nonconcurred with the Acquisition Decision Memorandum (ADM) prepared by ASD(C3I). Subsequently, JITC tested fixes while the PMO coordinated with functionals on work-arounds and re-categorization of problem reports. On November 17, 1997, DOT&E concurred in fielding Increment 2 after certification by JITC that there were no longer any Priority 2 trouble reports.


TEST & EVALUATION ASSESSMENT

Several recommendations were made to the PMO at the conclusion of Increment 1 testing to include enhancement of the data edit capabilities, developing a methodology to ensure data integrity, improving system documentation, improving reporting capabilities and improving on-line help. Increment 1 was shown to be operationally effective and operationally suitable in support of sites that were previously relying on manual operations to process procurement actions. Increment 2, after completion of fixes and work-arounds for the 35 P2s, was declared operationally effective and suitable.


LESSONS LEARNED

Test sites must be representative of the using community. Open P2s identified during Increment 2 developmental testing should have been recognized and corrected during developmental testing. To resolve these issues, Increment 3 test planning and execution will be more closely monitored by DOTE than previous increments.



NEWSLETTER
Join the GlobalSecurity.org mailing list