UNITED24 - Make a charitable donation in support of Ukraine!



Director, Operational Test & Evaluation
FY97 Annual Report

FY97 Annual Report


Total program cost (TY$) $70M
Life cycle cost (TY$) $1,140M
Full-rate production (IOC) 2QFY98

Prime Contractor


The Defense Joint Military Pay System (DJMS) simplifies standardization of military pay policies and procedures among the Services. DJMS provides consistent service to its customer base and supports the Office of the Under Secretary of Defense for Personnel and Readiness (OUSD(P&R)) strategy to consolidate pay and personnel management. DJMS supports Joint Vision 2010 by providing seamless integration of Service pay capabilities. Further, it supports information superiority by increasing access to information.

The fielded DJMS consists of client/server terminals and local area networks (LANs) that provide input to the Defense Finance and Accounting Service (DFAS) central sites. DJMS software has been and continues to be developed within DFAS through the Financial Systems Organization (FSO).

DJMS data is sensitive but unclassified (SBU). DJMS is being developed to prevent unauthorized access, modification, destruction, and disclosure of information to unauthorized users. DJMS will apply controlled access protection of Class C2, as set forth in DoD Standard 5200.28.


DFAS operates military pay functions at central sites in Indianapolis, Cleveland, Denver, and Kansas City for the Army, Navy, Air Force, and Marine Corps, respectively. The DFAS is in the final phases of consolidating the Army, Navy, and Air Force military pay management functions within DJMS. Marine Corps active and reserve military pay accounts are handled in the standalone Marine Corps Total Force System (MCTFS), implemented in December 1994. The Marine Corps will not be folded into DJMS because MCTFS already features a combined pay and personnel system. The consolidation will allow DJMS and MCTFS to be more responsive and flexible in supporting the DoD mission requirements.

DJMS currently is in operation at 100 Army sites, 80 Air Force sites, 3 Navy sites, and 3 DFAS centers. A total of 1.79M military pay accounts of the types shown below have been converted to DJMS-Active Component (DJMS-AC) and DJMS-Reserve Component (DJMS-RC):

Account Type Implementation Date

US Air Force Active, Air Force Reserve, and Air October 1991

Force Health Professional Incentive Program

US Army Active April 1992

US Air Force Academy January 1993

US Army Reserve July 1993

US Army Military Academy April 1994

US Army Health Professional Incentive Program April 1995

and Army Reserve Officer Training Corps

US Naval Academy October 1995

US Air Force Officer Training Corps April 1996

and Navy Health Professional Incentive Program

US Navy Reserve Officer Training Corps August 1996

US Army Junior Reserve Officer Training Corps October 1996

The remaining 575K accounts (in two types) are planned for conversion as follows:

Account Type Scheduled Implementation Date

Navy Active January 1998

Navy Reserve November 1998

The final step of the consolidation will be merging the DJMS Active Component and Reserve Component systems (AC/RC Merge). The merged DJMS will be slimmed down from the current AC and RC systems, have fewer lines of code and common routines and tables, and will require fewer personnel to maintain. From 3QFY98 through 4QFY00, DJMS incrementally will implement system changes and reconfigure DJMS into a single, standard system.


OPTEVFOR conducted a DJMS risk assessment on January 14-16, 1997 at the DFAS Center in Denver and on January 23-24, 1997 at DFAS in Cleveland, in accordance with the DOT&E guidelines for software-intensive systems. Along with the results of the risk assessment, OPTEVFOR briefed the operational test concept to DOT&E on February 21, 1997.

In compliance with the TEMP approved October 3, 1997, DJMS had its first operational test since being placed on OSD oversight in October 1996. This operational test addressed only the DJMS implementation for the active Navy accounts, since DJMS had already completed its implementations for the Army and Air Force activities. The at-sea connectivity portion of this evaluation occurred December 3-12, 1997, on board the USS Enterprise and the USS Dwight D. Eisenhower.


As a result of the OPEVAL during 1QFY98, DJMS for the Active Navy was determined to be operationally effective, pending revision of operating instructions. However, the system was found operationally unsuitable, due to training deficiencies. The shortcomings in training, however, were considered a Bureau of Naval Personnel problem and not a fault of the DJMS program. Accordingly, the Navy plans to resolve these training deficiencies before the transition to DJMS.

Join the GlobalSecurity.org mailing list