• Military Menu                       

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

• WMD
• Intelligence
• Homeland Security
• Space

	Director, Operational Test & Evaluation
FY97 Annual Report

JOINT ENGINEERING DATA MANAGEMENT INFORMATION
CONTROL SYSTEM (JEDMICS)

	Navy Lead Joint ACAT IAM Program Total program cost (TY$) $400M Life cycle cost (TY$) $1,100M Full-rate production (IOC) 1QFY99 Prime Contractor PRC, Inc.

SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010

The Joint Engineering Data Management Information and Control System (JEDMICS) contributes to Joint Vision 2010 concept of focused logistics by providing an automated data repositories, reproduction, and distribution of engineering drawings for the Defense Logistics Agency (DLA) and the Services. JEDMICS is a fully automated optical disk-based system designed to function in the engineering data environment. It will use a combination of optical digital mass storage and magnetic storage, files servers, digital scanners, graphics hard copy devices, graphics display workstations, and communications capabilities. Drawings are scanned in to create images for storage or received directly from the source in digital form.

EDMICS, the precursor system to JEDMICS, was implemented to handle unclassified information for the Navy and the DLA. Since being designated for migration as the Joint program, JEDMICS also will handle Army and Air Force drawings. JEDMICS will replace the Army's Digital Storage and Retrieval Engineering Data System (DSREDS) and the Air Force's Engineering Data Computer Assisted Retrieval System (EDCARS). Also, JEDMICS is designated as the engineering drawing depository for the Joint Computer-aided Acquisition and Logistics Support (JCALS) system, also on OSD oversight.

All test and evaluation to date has been on EDMICS, in compliance with the TEMP. EDMICS passed Initial Operational Test and Evaluation (IOT&E), Residual OT&E, and Milestone III in FY91. The Navy Computer and Telecommunications Station (NCTS) Pensacola conducted FOT&E on EDMICS version 2.4.4 in August 1995 at the Naval Ordnance Station (NAVORDSTA) Louisville and at Missile Command (MICOM) Huntsville. EDMICS Follow-on Operational Test and Evaluation (FOT&E) focused on interface issues (unresolved in earlier tests) and on new capabilities with hardware and software upgrades. The JEDMICS Program Office lab tested, beta tested, and deployed EDMICS version 2.5 in 1996. The proposed EDMICS versions 2.5.x will include fixes identified in version 2.5.

The next formal operational test event is scheduled in calendar 1998 on the first JEDMICS product, called version 3.0. The Milestone III Acquisition Decision Memorandum directed that:

• The Navy may continue to field EDMICS version 2.5, and

• The Navy shall obtain MAISRC approval before fielding version 3.0. Before seeking MAISRC approval, the Program Manager shall submit fully coordinated and updated TEMP, APB, Economic Analysis, and security plan/certification.

Based upon a succession of successful testing EDMICS (FOT&E of version 2.4 and version 2.5), DOT&E sees little risk with this program. Version 2.5 testing was completed successfully. The This program will continue to conduct a risk assessment of each increment to determine the level of operational testing. Program Manager's plans for additional testing will be documented in quarterly reports to ASD(C3I). DOT&E has removed this program from its operational oversight list.

The system is one of many client-server programs that are being fielded to replace stand-alone mainframe systems. When this system deployed, the Program Office and OSD oversight community failed to address the security and interoperability requirements with future deploying systems such as the joint computer-aided acquisition and logistics support system (JCALS). JCALS users must have access to EDMICS, however, no interoperability strategy had been developed. Months prior to the OT for JCALS and after the fielding and testing of EDMICS, this problem is only now being addressed. JCALS will become the bill payer to solve the interoperability and access problem, but EDMICS will lose control of how security access is determined. In the future, PMs and the DOT&E must insure that the interoperable issues are address at the beginning of a program's life cycle versus at the end.