On 20 January 1999, under the leadership of the Navy's Battle Force Systems Engineer (SEA05), an Alliance of Naval Sea Systems Command, Space and Warfare Systems Command, and Naval Air Systems Command field activities headed by Naval Surface Warfare Center (NSWC), Dahlgren Division, stood up the Navy Distributed Engineering Plant (DEP). The Navy DEP leveraged the Leading Edge Services (LES-98) and Defense Research and Engineering Network (DREN) asynchronous Transfer Mode (ATM) Networks to connect geographically dispersed Navy Design and Development Activities, Software Support Activities (SSA), Test and Evaluation (T&E) Facilities, and Training Centers. Integrating, at the laboratory level, actual fleet hardware and tactical computer program loads in a distributed configuration provided the Navy a controlled, repeatable environment in which to, for the first time, fault isolate and verify resolution of Battle Group interoperability problems, and system engineer at the system-of-system' and family-of-systems' level. A resounding success from stand-up', the Navy DEP was quickly recognized by the Department of Defense as an engineering tool to solve Joint interoperability problems.
Distributed Engineering Plant for Achieving Navy and Joint Interoperability
2000
18 pages
Report
No indication
English
Computers, Control & Information Theory , Common Carrier & Satellite , Military Sciences , Command control communications , Distributed data processing , Asynchronous transfer mode , Test and evaluation , Integrated systems , Systems engineering , Interoperability , Naval tactical data system , Battle management , Bmc4i(Battle management command control communications computers and intelligence)
Achieving GPS-Galileo interoperability: the challenges ahead
Online Contents | 2003
|Achieving interoperability between multiservice and multinational C2 systems
Tema Archive | 1987
|