D--Market Survey/Sources Sought for the follow on Systems Engineering and Integration (SE&I) Software and Integration efforts for the Force XXI Battle Command, Brigade and Below.

The effort proposed is a follow-on SE&I effort to existing contract DAAB07-01-D-E502, sole source to Northup Grumman Mission Systems (NGMS) as the Total Systems Integrator, systems engineer and architect. The effort includes systems architecture eng ineering, Tactical Internet architecture design and development, integration, engineering with weapon platforms and ABCS systems, software and prototype hardware design and development in support of the FBCB2 program for both terrestrial communications and L-Band Satellite communications networks. The system is specifically oriented to provide individual tactical vehicles and platforms with Situational Awareness and Command and Control capabilities. The main goal of the SE&I portion of the FBCB2 Program i s the continued evolution of the Force XXI Battle Command Brigade and Below (FBCB2) System from delivery of the FBCB2 Version 6.4 (V6.4) Software to the FBCB2 Product Line. The FBCB2 Product Line will provide a modular and scalable infrastructure to enhan ce system interoperability and performance attributes. The Product Line will be incrementally delivered, building on the current phase I work (Commanders Digital Assistant) being done by NGMS for Land Warrior. Subsequent deliveries to be covered under th is contract will add increasing FBCB2 functionality, as required, and will support a variety of variations and operational environments such as Joint Blue Force Situational Awareness (JBFSA). It is important to note that the FBCB2 Product Line must be dev eloped as a complete design with each enhancement building on top of the previous one to ensure that the overall objectives of the Product Line Objective Architecture (OA) jointly developed by Northrop Grumman Mission Systems (NGMS) and the Software Engine ering Institute (SEI), as documented in the FBCB2 Software Architecture Design Document (SWADD), are met. Blue Force Tracking (BFT): This follow-on contract also includes SE&I efforts for the FBCB2 BFT Software (FBCB2 over L-Band Satellite comms). Effort s are similar to those previously described (i.e. integration and installation of the hardware and software into various Army platforms (including with some platform sub-systems) at various Army locations, as well as various testing and training requiremen ts. Software engineering, configuration, and design work are a major portion of the BFT efforts. BFT efforts differ from site to site and resulting Operations Centers are necessarily unique to the various locations. BFT efforts include, among other task s, Tactical Operations Centers (TOCs) and Non-Line of Sight (NLOS) architectures; message routing; prototype hardware; field support; Army Battle Command System (ABCS) integration. The Period of Performance for this contract will be from June 2004 through June 2009, with a total value of approximately $40M, to include the following tasks: Systems Engineering and Integration; Program Management; development of software and prototype hardware to the objective capabilities as specified in the FBCB2 Operational Requirements Document (ORD) and User Functional Description (UFD); perform Tactical Internet design engineering to achieve appropriate network performance; integrate application software; integrate and install the hardware and software into various Army platforms (to include with some platform sub-systems) at various Army locations; testing beyond Initial Operational Test and Evaluation (IOT&E); develop logistics support plan incl uding technical manuals/technical bulletins/interactive electronic manuals (TM/TB/IETM); maintenance of logistics management information (LMI) database develop/update of support analysis plan to include maintenance planning; provisioning maintenance data; migration of FBCB2 to pc computers and small computing devices; migration of FBCB2 architecture; provide strategic vision of future FBCB2; development of software functionality and documentation necessary to accredit the FBCB2 system through the DITSCAP process. Subsequent software updates are forecasted at least on an annual basis. This effort builds onto ongoing software development. Included also is Tactical Internet Management System (TIMS). Evolution of TIMS software applicat ion and associated products from the Block 4 functionality to be demonstrated at IOTE to its objective capability as defined in the ISYSCON ORD. ISYSCON (V)4/Tactical Internet Management System (TIMS) application development continues to support FBCB2 net work management functions in the areas of Unit Task Reorganization (UTR) for Block 2 & Block 3 requirements. TIMS continues to support S6 related FBCB2 functions. TIMS development will continue to enhance the management of the Tactical Internet to includ e Situational Awareness monitoring based on future FBCB2 SA reporting implementation (i.e. SA over multicast), EPLRS monitoring, and future JTRS management requirements IAW the ISYSCON ORD. The TIMS program will begin development of the Initialization Cap ability (IC) that will enable the soldier, without the assistance of a support contractor, to create, merge, and edit the FBCB2 and TIMS operational databases. This capability is required to support FBCB2 block 3 and TIMS Block 5 requirements. ISYSCON (V )/4 TIMS and Initialization Capability (IC) associate product development continues to support FBCB2 network management functions, UTR, enhanced TI management, situational awareness, EPLRS monitoring, and JTRS management. TIMS is the Armys Brigade and Bel ow network management system. The vendor must provide software maintenance for FBCB2 software version 3.5, which is currently in use by the U.S. Army in 4 ID, 1CAV, SBCT1, and SBCT2. Track software problems found in the field, in the Central Technical Su pport Facility, and in other contractor facilities. Identify significant problems, develop software patches, and manage distribution of software patches. FBCB2 software baseline is approximately three million source lines of code composed from COTS, GOTS , and custom application software. Currently, only limited software documentation is available. System of Systems Engineering and Integration (SSE&I) effort: The SSEI effort is a joint/collaborative approach to a System of Systems Engineering and Integration (SSE&I) effort targeted at ABCS version 6.4 and subsequent versions. The SE&I team will coo rdinate systems engineering across the contractors PEO C3T contracts and with other PEO C3T contractors. The contractor shall lead and/or contribute to the following principal systems engineering tasks: Solve critical user effectiveness issues; OPORD/OPL AN dissemination from MCS to the balance of the ABCS architecture; overlay dissemination and consistency, Blue Situational Awareness, Red Situational Awareness, Fire support (call for fire), Medevac, logistics reporting. Engage peers from within NGMS to h elp solve these issues. Express a clear Concept of Operations (CONOPS) for the System of Systems. Describe and develop key Operations Threads for ABCS 6.4 and subsequent versions. Produce a unified CONOPS document for ABCS 6.4 and subsequent versions. Link CONOPS to a System Architecture and the software processes between the Battlefield Functional Area systems (BFAS). Produce an Architecture Description Document for ABCS 6.4 and beyond. This includes specifying and documenting the hardware and softwa re products in the ABCS 6.4 and subsequent versions. Define and document the software interfaces in the ABCS 6.4 architecture and subsequent versions. Define and execute the process of maintaining configuration control of these interfaces. Define and Mo del the Data Architecture for ABCS 6.4 and subsequent versions. Develop a top level Technology Transition Strategy that can be uniformly applied across all systems. Again, this effort is a continuation of the ongoing SE&I contract with NGMS, awarded in 2001, which was a continuation of the original Engineering, M anufacturing, and Development (EMD) contract DAAB07-95-D-E604, which was awarded competitively in 1995. Respondents to this survey must identify their software development practices, as the Government requires state of the art, best business practices implemented. Respondents must provide a Total System Responsibility (TSR) approach, to include any warrant y or contractor logistics support that would be considered most effective for the Army.