|FY99 Annual Report|
DEFENSE JOINT MILITARY PAY SYSTEM (DJMS)
|DFAS ACAT IAM Program||Prime Contractor|
|Total Number of Systems:||20||N/A - Software Developed by DFAS|
|Total Program Cost (TY$):||$184M||Central Design Activity|
|Average Unit Cost (TY$):||$9M|
SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010
The Defense Joint Military Pay System (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)) by consolidating pay management functions. DJMS supports Joint Vision 2010 by providing seamless integration of Service pay capabilities. Further, it supports information superiority by increasing access to military pay information.
The fielded DJMS consists of client-server terminals and local area networks 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 Central Design Activity. DJMS data is sensitive but unclassified. DJMS was developed to prevent unauthorized access, modification, destruction, and disclosure of information to unauthorized users. DJMS applies 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, and Denver for the Army, Navy, and Air Force. DFAS consolidated the Army, Navy, and Air Force military pay management functions within DJMS. Marine Corps' Active and Reserve military pay accounts are handled in the stand-alone Marine Corps Total Force System (MCTFS), implemented in December 1994. The Marine Corps' pay accounts will not be folded into DJMS because MCTFS already features a combined pay and personnel system.
DJMS is currently in operation at 100 Army sites, 80 Air Force sites, 60 Navy sites, and 3 DFAS centers. A total of 2.2 million military pay accounts, like the types shown below, have been converted to DJMS-Active Component (DJMS-AC) and DJMS-Reserve Component (DJMS-RC):
Account Type Implementation Date
U.S. Air Force Active, Air Force Reserve, and Air October 1991
Force Health Professional Incentive Program
U.S. Army Active April 1992
U.S. Air Force Academy January 1993
U.S. Army Reserve July 1993
U.S. West Point Academy April 1994
U.S. Army Health Professional Incentive Program April 1995
and Army Reserve Officer Training Corps
U.S. Naval Academy October 1995
U.S. Air Force Officer Training Corps April 1996
and Navy Health Professional Incentive Program
U.S. Navy Reserve Officer Training Corps August 1996
U.S. Army Junior Reserve Officer Training Corps October 1996
U.S. Navy Active February 1998
U.S. Navy Reserve August 1999
In compliance with the TEMP approved by DOT&E on October 3, 1997, DJMS completed its first OPEVAL in December 1997. This OPEVAL only addressed the DJMS implementation for the Active Navy accounts, since DJMS had already completed its implementations for the Army and Air Force activities.
As a result of the OPEVAL, DJMS for the Active Navy was determined to be operationally effective, pending revision of the operating instructions. However, the system was found operationally unsuitable due to documentation and training deficiencies. The shortcomings in training were considered a Bureau of Naval Personnel problem and not a fault of the DJMS program. DJMS-AC achieved the Major Automated Information Systems Review Council approval for fielding in February 1998.
TEST & EVALUATION ACTIVITY
The plan for OPTEVFOR to conduct OPEVAL for the DJMS-RC in November 1998 was disapproved by DOT&E. The OPEVAL plan was disapproved since the DJMS-RC System Acceptance Testing (SAT), a form of DT, was not scheduled for completion until February 1999. DOT&E directed that OPEVAL should not commence until the SAT has been completed.
In May 1999, after the completion of the SAT, the OPEVAL of DJMS-RC was conducted in compliance with the DOT&E-approved TEMP dated April 19, 1999. OPTEVFOR collected test data at four Navy Reserve sites located in Minneapolis, MN; Belle Chase, LA; Mobile, AL; and Atlanta, GA, to allow a variety of technology and telecommunications options to be exercised and evaluated. During OPEVAL, pay transactions normally submitted to the Navy Reserve legacy systems were duplicated and submitted to the DJMS-RC for processing and verification.
TEST & EVALUATION ASSESSMENT
During OPEVAL, deficiencies in processing DJMS-RC error codes and aviator career incentive pay were identified. These deficiencies were attributed to the Navy interface systems and were not related to the DJMS-RC system. After the Navy Reserve Information Systems Office rectified the deficiencies in early June, OPTEVFOR conducted additional testing to verify the fixes. Test results showed that all previously identified deficiencies were successfully rectified. In late June, COMOPTEVFOR declared that DJMS-RC is operationally effective and operationally suitable and recommended DJMS-RC for fleet introduction.
DOT&E concurred with COMOPTEVFOR's recommendation and directed that: (1) OPTEVFOR conduct security and maintainability reviews after DJMS-RC is relocated to the Defense MegaCenter in Mechanicsburg, PA. (During OPEVAL, DJMRS-RC was operating at the Defense MegaCenter in Chambersburg, PA); (2) OPTEVFOR conduct additional end-to-end year 2000 compliance testing between the Navy interface systems and DJMS-RC. Some of these tests could not be performed during OPEVAL because of operational constraints; and (3) The data bases of DJMS-RC and Navy interface systems be refreshed daily to minimize record disparities and transaction rejections. Based on DOT&E recommendation and input from other OSD oversight offices, the DoD Deputy Chief Information Officer granted DJMS-RC Milestone III approval on August 11, 1999. OPEVAL of the final merged DJMS system is currently scheduled for 3QFY02.
|Join the GlobalSecurity.org mailing list|