• Military Menu                       

• Introduction
• Systems
• Facilities
• Agencies
• Industry
• Operations
• Countries
• Hot Documents
• News
• Reports
• Policy
• Budget
• Congress
• Links

• WMD
• Intelligence
• Homeland Security
• Space

DEFENSE PROCUREMENT PAYMENT SYSTEM (DPPS)

The Defense Procurement Payment System (DPPS) is planned to be the standard DoD procurement payment system used to calculate contract and vendor payments, grants, and other agreement entitlements. All DoD contract and vendor payment legacy systems will be consolidated into DPPS.

DPPS supports DoD contract and vendor entitlement functions through commercially derived applications software designed to operate in an open systems environment. DPPS will be implemented on Oracle Financials with four tiers. Tier One is a thin-client component acting primarily as the presentation layer. Tier Two is a web server supporting navigation via the web and workload balancing. Tier Three is an application server containing bulk of the application logic. Tier Four is a data base server. DPPS will use the Defense Financing and Accounting Service Enterprise Local Area Network. End-user hardware must be compliant with DFAS standards, which are consistent with the Defense Information Infrastructure Common Operating Environment.

The current contract and vendor payment environment is comprised of many legacy systems that were not designed to share data or manage information from the DoD corporate perspective. Inefficiencies inherent in the operation of many semi-independent efforts have increased costs, caused major resource issues, unmatched disbursements, and focused attention on erroneous contract payments. The DPPS program was chartered to correct these and other shortcomings in procurement payment systems in 1995 and the Mission Needs Statement was approved in the same year. The DoD Comptroller reaffirmed the Mission Needs Statement in February 1997. The Operational Requirements Document, which was initially approved by DFAS in December 1997, has been updated in conjunction with the TEMP. Both documents are in staffing.

During FY01, the PM conducted several phases of developmental testing with the intent to refine user requirements and to improve the software that is under development. Several Integrated Product Team meetings were held and a draft TEMP is currently in staffing.

The developmental test results showed that the initial DPS baseline solution met a significant amount of the DPPS requirements. Full compliance with the Critical Technical Parameters, however, could not be ascertained until additional end-to-end developmental testing is completed. No operational testing is expected until FY03. The Operational Test Division of the Joint Interoperability Test Command will conduct the operational testing of DPPS. A comprehensive test and evaluation assessment of DPPS will be completed after the completion of OT&E in FY03.