Defense Information Systems Agency, NCRCO, Code DN2, 701 South Courthouse Road, Arlington, VA 22204-2199

D -- ENGINEERING, INTEGRATION, INSTALLATION, USE/DEVELOPER, AND TRAINING SUPPORT TO DISA'S DEFENSE INFORMATION INFRASTRUCTURE (DII) COMMON OPERATING ENVIRONMENT (COE) ENGINEERING OFFICE SOL DCA100-96-R-0051 DUE 080896 POC Mr. Leo J. Milanowski, Contracting Officer, (703) 607-6908, or Agency Competition Advocate, LTC James Shellington, (703) 607-6859. DISA intends to enter into negotiations with Inter-National Research Institute, Inc., Reston, VA on a non-competitive basis to provide technical support in producing Version 3.0 and future versions of the DII COE. The Government intends to award a contract for an initial twelve (12) month period, with options for two (2) additional consecutive twelve (12) month periods. Contract efforts will be focused in three areas: maturation support, engineering process support, and user and developer support. More specifically, during the first contract period, the contract will require support to: (1) Integrate and deliver DII COE 3.0 kernel and related toolsets for the first tier of supported DII platforms, to include Solaris 2.4, HP/UX 9.07 and Windows/NT 3.51 based on previous DII COE deliveries and expand platform support with kernel functionality to address Solaris 2.5, HP/UX 10.0, AIX 4.1, Digital Unix, and SGI Irix. Multi-platform support includes the ability to maintain two versions preceding the current version consistent with the vendor's operating system migration path. (2) Design and implement additional toolset components (remaining 18 of identified 37) integrated with the common toolset library developed in support of DII COE 1.0 and 2.0. These toolsets will be used during follow-on years to support compliance checking of a reference implementation of the DII kernel, allowing any COTS hardware vendor to provide kernel capability which meets DISA minimum interoperability requirements. (3) Produce Version 2.0 of the GCCS COE variant. (4) Produce Version 1.0 of the GCSS COE variant. (5) Update the DII COE Integration and Runtime Specification (I&RTS) providing additional changes such as database segmentation requirements, database segmentation tool descriptions, data base bridging products, and segmentation of developer documentation. (6) Improve and migrate existing DII COE component pieces, to include the track database manager and Common Operational Picture, to designated server platforms, to include Solaris 2.5 at a minimum. Begin Level 6 run-time integration of these same component pieces to take advantage of service-provided DII COE capabilities, to include distributed computing, expanded communications capabilities, and an improved system security architecture. Provide plans for DII COE functionality to support or be compatible with emerging technologies and architectures. This effort will begin to remove duplicative GOTS functionality in favor of comparable COTS modules within the COE and reduce reliability of the current GOTS infrastructure components on a single vendor. (7) Provide general use developer Application Programming Interfaces (APIs) to support expanded capabilities of these DII components. This effort will begin to provide additional functionality to COE consumers without tying DISA to a specific GOTS provider. (8) Continue engineering support to: enhance the DII COE architecture, support interfacing externally developed C4I systems with the GCCS and GCSS variants, assess the inclusion of GOTS and COTS components, perform problem identification and resolution, support the continued maintenance of DII COE segments housed in the COE On-Line Repository System (CSRS), train initial and replenished Government integration teams and software developers, develop or enhance existing segmentation training courses for application developers to ensure new applications conform to DII COE requirements, and continue providing integration support at the Operational Support Facility and key sites worldwide for the continued integration and maintenance support of GCCS and GCSS COE variants. Efforts planned for the second and third contract periods will: (1) Continue expansion of platform support to Open/MVS and update releases of major hardware vendor platforms identified above (i.e., Solaris 3.X, etc.) (2) Expand toolset robustness to support government compliance testing of vendor-supplied DII kernel implementations. (3) Integrate up to ten Shared Data Environment (SHADE) tools provided by outside sources. (4) Continue migration of existing DII COE components to Level 7 run-time integration, level 5 Human Computer Interface (HCI) compliance, and level 6 architectural compliance. Level 7 run-time compliance will continue to migrate GOTS-based, proprietary software to COTS-based, competitively-acquired software, to include use of technologies such as Object Linking and Embedding (OLE), Common Object Request Broker Architecture (CORBA), and the World Wide Web (WWW). Level 5 HCI compliance will migrate current unique human-computer interface styles to an industry-standard look and feel now being worked in standards working groups. Level 6 architectural compliance assessment will require impact analysis and programmer guidelines for an object-oriented approach to the management of track data objects and their display based on the Joint Mapping ToolKit (JMTK). The spatial functionality of the mapping software will be improved to enhance ease of integration with the visual and terrain components of the JMTK. (5) Produce Version 3.0 of the GCCS COE variant. (6) Produce Version 2.0 of the GCSS COE variant. (7) Update the DII COE Integration and Runtime Specification (I&RTS) providing additional changes such as inclusion of OLE, CORBA, and WWW sections as appropriate. (7) Provide general use developer APIs to support expanded capabilities of DII components. This effort will begin to provide additional functionality to COE consumers without tying DISA to a specific GOTS provider. (8) Continue engineering support to: enhance the DII COE architecture, support interfacing externally developed C4I systems with the GCCS and GCSS variants, assess the inclusion of GOTS and COTS components, perform problem identification and resolution, support the continued maintenance of DII COE segments housed in the COE On-Line Repository System (CSRS), train initial and replenished Government integration teams and software developers, develop or enhance existing segmentation training courses for application developers to ensure new applications conform to DII COE requirements, and continue providing integration support at the Operational Support Facility and key sites worldwide for the continued integration and maintenance support of GCCS and GCSS COE variants. (9) Integrate and deliver DII COE 4.0 kernel reference implementation and related toolsets for the reference implementation of DII platforms (comparable to Solaris and HP today). (10) Complete implementation and integration of object-based Common Operational Picture with full capability for target server environment. (11) Continue migration of existing DII COE component pieces to Level 8 run-time integration, level 6 HCI compliance, and level 7 architectural compliance. (12) Provide general use developer APIs to support expanded capabilities of these DII components. This effort will begin to provide additional functionality to COE consumers without tying DISA to a specific GOTS provider. (13) Produce Version 4.0 of the GCCS COE variant. (14) Produce Version 3.0 of the GCSS COE variant. (15) Update the DII COE Integration and Runtime Specification (I&RTS) providing additional changes such as the inclusion of new COTS and GOTS segments as appropriate. (16) Continue engineering support to: enhance the DII COE architecture, support interfacing externally developed C4I systems with the GCCS and GCSS variants, assess the inclusion of GOTS and COTS components, perform problem identification and resolution, support the continued maintenance of DII COE segments housed in the COE On-Line Repository System (CSRS), train initial and replenished Government integration teams and software developers, develop or enhance existing segmentation training courses for application developers to ensure new applications conform to DII COE requirements, and continue providing integration support at the Operational Support Facility and key sites worldwide for the continued integration and maintenance support of GCCS and GCSS COE variants. Interested parties may request the solicitation by sending a written request via facsimile (703-607-4340) or regular mail (address above). Please include the Solicitation No. in all correspondence See Note 22 and 26. (0163)

Loren Data Corp. http://www.ld.com (SYN# 0022 19960612\D-0001.SOL)