D -- ENGINEERING SERVICES

Notice Date

December 13, 2000

Contracting Office

Defense Information Systems Agency, DITCO-NCR, 701 South Court House Road, Arlington, VA 22204-2199

ZIP Code

22204-2199

Solicitation Number

N/A

Point of Contact

Contact MAJ Bobby Myers, 703-681-2305/Contracting Officer, Barbara A. Janitis, 703-607-6913

Description

The Defense Information Systems Agency/Joint Interoperability and Engineering Organization (DISA/JIEO) is seeking vendor information to identify potential sources that can produce and maintain the Defense Information Infrastructure Common Operating Environment (DII COE) Common Operational Picture (COP) server and Visualization software packages and provide all necessary technical support to: mature and extend the DII COE COP infrastructure and architecture; increased accessibility; expand the Integrated C4I System Framework (ICSF) usefulness to a variety of user environments (e.g. Commanders-In-Chief (CINCs), Joint Task Force (JTF), Firing Unit levels); enhance ICSF's support to the joint battlespace; reduce the time and effort required for customers to produce COP applications; produce and support Global Command and Control System (GCCS) configuration definitions and mission applications; maintain the current software baseline; and support the transfer throughout Government and industry of the knowledge needed to extend and use the COE and integrate applications into the COE environment. Requirements include providing the following: a more mature and extensible ICSF infrastructure and architecture; identification of capability and tool requirements; support for existing and emerging technologies; expanded multi-platform support; integration standards and documentation; version integration support; engineering process support; DII COE, ICSF, GCCS and Global Combat Support System (GCSS) architecture support; support for C4I system interfaces (e.g., Tactical Battle Management and Command System (TBMCS), Global Command and Control System -- Maritime (GCCS-M), Global Command and Control System -- Army (GCCS-A), etc); development and documentation of Application Programmer Interfaces (APIs) and Government Off-The-Shelf (GOTS) components; documentation of associated architecture, design and programmers guidance; support for problem identification and resolution; segmentation training; government integration training; user/developer training; user technical support. The requirements also include supporting the development of interfaces to legacy systems as well as the integration of advanced capabilities into the GCCS, GCSS, ICSF, and DII COE. Potential sources must demonstrate the following: In-depth knowledge of the DII COE including its software integration approach for federated sharing of the operating system's run time environment, architectural components of infrastructure services and common support applications built on the run time environment, software reuse, and strategy for migrating of existing legacy capabilities; in-depth knowledge of the DII COE Shared Data Environment (SHADE) including its architecture, implementation approaches, re-usable data-related software components, data guidelines and standards, database design, data sharing from tight to loose federations, strategies for bridging data "stovepipes" to broaden interoperability, and concept for using Extensible Markup Language (XML); in-depth knowledge of the current state of technology, future trends in technology and integration of emerging technology into the DII COE and SHADE; in-depth knowledge of subscriber systems and the technical, schedule, and program issues associated with subscriber implementation of the DII COE; in-depth knowledge of Distributed Information Technology at all layers Network, Operating System, Architecture/Protocol and Distributed Management, and how Information Assurance has to be integrated into each layer; in-depth knowledge of and demonstrated expertise in implementing current Information Assurance-related tools, techniques, and capabilities, including proxy and firewall technology, Public Key Infrastructure (PKI) technology, Secure Sockets Layer (SSL) technology, and National Security Agency (NSA) encryption methods; knowledge of currently installed GCCS and GCSS mission applications and the DII COE components; in-depth knowledge and understanding of Unified Build, COP, Joint Mapping Tool Kit -- Visualization (JMV), ICSF, and associated communications capabilities; expertise in Track Database Manager (TDBM) processes and internal data structures; knowledge of Database Management processes and experience in use of alternative data and object management technologies including but not limited to Relational Database Management System (RDBMS), Object-oriented Database Management System (ODBMS), in memory approaches, XML; knowledge of Message Data Exchange (MDX) and Message Data Exchange Network (MDXNET) functionality required to support message exchanges via Local Area Network (LAN)/ Wide Area Network (WAN); knowledge of and skill in deployment and operation of the COP in GCCS, GCSS and other C4I systems; in-depth knowledge of the operational employment of the COP and fielded COP architectures; architectures knowledge and experience including detailed knowledge of interoperability issues and technical solutions for interoperating with coalition forces; in-depth knowledge of Combat Support applications and GCSS data sources and technical interface requirements to support integration into the COP, operational employment of the COP and fielded COP architectures, including the following: Interface/integration with the GCSS data mediation environment, interface and integration with Joint Operation Planning and Execution System (JOPES), Global Status of Readiness and Training System (GSORTS), National Imagery and Mapping Agency (NIMA) (Water and Airport static information), Global Transportation Network (GTN), Joint Total Asset Visibility -- European Command (JTAV-EUCOM), Joint Total Asset Visibility -- Pacific Command (JTAV-PACOM), Joint Total Asset Visibility -- Atlantic Command (JTAV-ACOM), Joint Personnel Asset Visibility (JPAV), & Dynamic Tracks (DTRACS) Sites and Units COP Databases and their relationships with the TDBM; knowledge of the current COP architectures and existing COP software components in DII COE Version 3.1 and how to move them to DII COE Version 4.x software baseline; expertise in Internet architectures and techniques for integrating mapping and imagery products into a Web-based environment, as evidenced by the following: Knowledge of the current Enhanced Linked Virtual Information System (ELVIS) I & II architectures, knowledge of the Combat Support application development specifics and requirements for addition to the ELVIS I & II software baselines; an understanding of the technical challenges for displaying the COP on small handheld devices such as a Palm Pilot or similar handheld platforms; in-depth knowledge of the use of map servers; demonstrated ability in maintaining the Tactical Management System software, the ICSF software, the Integrated Foundation Libraries, specialized tactical management system software, and time synchronization tools; demonstrated ability to maintain and enhance segments that are used for multi-source correlation, including correlation of classified data sources; demonstrated ability to maintain and enhance existing software segments used for Missile Early Warning; demonstrated ability to maintain and baseline source code and technical documentation developed by another vendor; demonstrated ability to support and troubleshoot software for extended periods of time in a global environment with cleared personnel who possess relevant military operational expertise; knowledge of the DII COE segmentation concept and ability to segment software; in-depth knowledge of Ground Order of Battle and expertise in relating Near-Real Time track data with structured, semi-structured, and free form amplification data, making and managing automatic track associations, making and managing data correlation; in-depth knowledge of current and emerging mapping, charting, geodesy and imagery technologies and infrastructure services; demonstrated ability to build and maintain large (1-2M Software Lines Of Code) C4I systems; a demonstrated and defined software development process including software size and schedule estimation and schedule metrics; configuration management; software quality assurance, assurance and management addressing software quality metrics, analysis and defect prevention; software inspection, software quality and schedule metrics, test strategy and procedures, and integration methodology; knowledge in developing and implementing software process improvement and experience in software process models (e.g., the Software Engineering Institute(SEI) Capability Maturity Model, NASA's experience factory, (SEI/Watts Humphrey) Personal Software Process (PSP) and/or Team Software Process (TSP); demonstrate the requisite technical staff with the minimum SECRET clearances available, low staff turnover, and the ability to cover multiple development/user sites; knowledge of and expertise in building systems based on multi-tier component-based software architectures to include: flexible information models and flexible information distribution; the use of component-based software to enable pluggable data models, sources, and algorithms (e.g. pluggable correlators); service-based architectures; support for transient client connections and variable bandwidth connections; transition strategies from the current ICSF architecture; expertise in developing systems based on server side component models and the supporting commercial technologies (e.g. Enterprise Java Beans and J2EE); and demonstrated knowledge and expertise in determining appropriate use of enterprise level technologies like Message Oriented Middleware. Potential sources should also address the following critical element: Demonstrated ability to maintain and baseline source code, which exceeds 2 million lines of code and over 272 segments developed by another vendor on a schedule-driven, overlapping, six-month product development cycle and to produce the required technical documentation. Vendors, or vendor teams, in responding to this announcement must provide a written brief indicating their demonstrated knowledge, capabilities, and relevant experience in relation to the above requirements/critical elements to the DISA POC below. Submit one electronic copy (MS Office 97 format) and one hard copy of written response to Defense Information Systems Agency (DISA) ATTN: Major Myers, 5600 Columbia Pike, Falls Church, VA 22041-2717; email address is myersr@ncr.disa.mil. Submit one electronic copy to the Contracting Officer at: janitisb@ncr.disa.mil. Written submissions must be received not later than 15 business days after this published notice. After written submissions are received, respondents may be contacted within 10 business days to schedule oral brief/questioning by a DISA technical panel.

Record

Loren Data Corp. 20001215/DSOL012.HTM (W-348 SN508865)