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.


    Access

    Access via TIB

    Check availability in my library


    Export, share and cite





    Achieving GPS-Galileo interoperability: the challenges ahead

    Blanchard, Walter F. | Online Contents | 2003


    Achieving control and interoperability through unified model-based systems and software engineering

    Ingham, Michel D. / Rasmussen, Robert / Dvorak, Daniel | NTRS | 2005