1.0  INTRODUCTION 

      

This document is the Preliminary DCN/ICN Pilot Program Test Software and Equipment Report [DCN/ICN, 97c]. The purpose of this document is to identify the software and equipment (hardware) needed to implement and test the DCN/ICN at the DoD CALS Office and 6-10 U.S. and allied nation defense system program offices.

1.1  System Overview

The Department of Defense Continuous Acquisition and Life­cycle Support Network/International CALS Network is a DoD and international electronic network of CALS interested subscribers and organizations that support the DoD initiated CALS strategy.

The DCN/ICN is a collection of cooperating organizations that includes the International CALS Congress as an advisory board; the DoD CALS Network; the International CALS Network; and other national, regional, or alliance networks that exchange CALS information and provide services to their customers. Figure 1.1-1 provides a top level view of the DCN/ICN relationships and the supporting organizations.

Each organization network is a subset of the Internet that provides CALS related collaboration and information services to its constituents. Supporting each network is a Local Operations Control Center (LOCC) that provides administrative, help-desk, collaboration, and CALS related information services. The Management Operations Control Center (MOCC) provides the same services on a global scale and exchanges global/local directory and information repository index information with each of the LOCCs. The sizes of each of the regional or national networks and the specific services that they may provide depends on the needs of the potential subscribers, the commitments by sponsoring organizations, as well as available resources (equipment, facilities, and personnel).

While the DCN/ICN concept leverages the existing world wide Internet and the World Wide Web (WWW) to provide services and CALS specific information content to its customers, it does not provide access to the Internet. Access to the Internet is left as a choice for the individual or organization. Similarly, subscriber software and hardware may be acquired through the subscriber's acquisition organization or optionally, the DCN/ICN shall offer this service.

The preliminary configuration for the MOCC is shown in Figure 1.1-2. The configuration shows a security server (Saturn), Web servers (Galaxy and Nebula), a database server (Condor), a development server (Vulcan), production servers (Galaxy and Condor) and a collaboration server (Nebula) as well as local client workstations.

1.2  Document Overview

Section 1 of this document identifies the purpose of this document, provides an overview of the DCN/ICN, a summary of this document as well as a list of applicable references. Appendix A identifies the software and hardware needed to test the DCN/ICN at the MOCC and the Pilot Program Sites.

1.3  Applicable Documents

Applicable documents to the DCN/ICN Pilot Program Testing are listed in Table 1.3-1.

APPENDIX A:  PILOT PROGRAM SOFTWARE AND EQUIPMENT

      

This appendix identifies the requirements as well as the selected products for the DCN/ICN Pilot Program. The products include both software and hardware equipment. Section A.1 identifies the requirements. Section A.2 identifies the selected products. Product evaluation is still in progress. Section A.3 identifies potential sources of supply.

A.1  Bill of Materials Requirements

The hardware and software requirements to support CALS DCN/ICN Pilot Program test and implementation are summarized in Table A.1-1. The majority of the requirements are for Commercial-Off-The-Shelf (COTS) software for use at the Management Operations Control Center (MOCC) or on the subscriber workstations at the Pilot Program Sites.

A.2  Bill of Materials Products

The candidate products that satisfy the DCN/ICN requirements are summarized in Table A.2-1.

Products for the requirements in Table A.2-2 have not been identified as of December 31, 1996.

A.3  Bill of Materials Suppliers

The Bill of Materials Potential Suppliers are listed in Table A.3-1.

APPENDIX B:  ABBREVIATIONS AND ACRONYMS