1. The intended outcome of this synopsis is to gauge industry’s interest in the Agency’s follow-on C2BMC effort and does not duplicate the proposed Enhanced C2BMC effort currently posted under FedBizOps Solicitation Number HQ0147-10-R-EC2BMC. In accordance with Federal Acquisition Regulation (FAR) 52.215-3 -- Request for Information or Solicitation for Planning Purposes, (a) The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation, and (b) Although “proposal” and “offeror” are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal. This is an announcement for informational planning purposes only and does not constitute a Request for Proposal, nor is it to be construed as a commitment by the Government. 2. Background: The Missile Defense Agency (MDA) is charged with developing and fielding a Ballistic Missile Defense System (BMDS) to protect the United States (U.S.), and U.S. allies and friendly nations from ballistic missile attack. The Ballistic Missile Defense System uses a layered approach which includes sensors, kinetic energy systems, directed energy systems, battle management, and command and control elements that will engage threat missiles in all phases of flight, from Boost Phase through Midcourse and into Terminal Phase. The mission of MDA’s Command and Control, Battle Management, and Communications (C2BMC) System is to provide a Combatant Command decision aid to integrate and globally synchronize missile defense systems and operations providing optimized layered missile defense against all ranges of threat, in all phases of flight. The C2BMC System does this by collecting and processing ground and space-based sensor data (to include optical, radar and infrared) on ballistic threats into a discriminated, engageable system track (correlating traceable data from multiple sensors to target and guide interceptors to the lethal warhead) that is displayed to decision- makers, distributed to interceptor fire control units, and re-assessed for kill effects. The result is an extended network of defensive sensors, shooters, battle managers, and intelligence assets. The global C2BMC System spans the existing U.S. Combatant Command structure, allowing the warfighter to orchestrate and optimize U.S. ballistic missile defense response on a worldwide level. 3. Description: a. Request for Information (RFI). This Sources Sought Synopsis is being conducted by the MDA to gauge industry’s interest in the Agency’s follow-on C2BMC effort. The information provided will support the Agency’s Business Case Analysis (BCA) to determine the follow-on acquisition strategy for the C2BMC program. b. Current Other Transaction Agreement (OTA) Structure. Currently the engineering, development, test, integration, fielding, and operations and sustainment of the C2BMC System is handled through a Cost Plus Award Fee (CPAF) Other Transaction Agreement (OTA) with a consortium of five major defense contractors (known as the Missile Defense National Team C2BMC (Industry) [MDNTB(I)]). The OTA was awarded on a sole source basis in February 2002, and will expire in December 2011. Lockheed Martin Information Systems & Global Services is the C2BMC lead contractor, with The Boeing Company, General Dynamics Advanced Information Systems, Northrop Grumman Information Systems, and Raytheon Intelligence and Information Systems as major teammates. The team also includes a number of niche (specialty) subcontractors. The MDNTB(I) works in a “badgeless” environment where: • There is a single Statement of Work (SOW) for all teammates • There is no formal work share • There is one Award Fee pool • No one subcontractor is fully responsible for any one C2BMC capability The MDNTB(I) works closely with Government Program Office staff (i.e., military, civilian, support contractors, Federally Funded Research and Development Center (FFRDC) personnel, and University Affiliated Research Center (UARC)) personnel in execution of program requirements. c. C2BMC Program Requirements. 1) Location of Performance: Under the OTA, the MDNTB(I) is charged with the engineering, development, test, integration, and fielding of new C2BMC capabilities; and on-site operations and sustainment (including operational and depot maintenance) support for the fielded C2BMC capabilities located worldwide. Specifically the locations of work include: • Pentagon, Arlington, VA • Ft Belvoir, VA • Huntsville, AL • Colorado Springs, CO • Alaska • Nebraska • Hawaii • Japan • Germany • Italy • Israel 2) Organizations Involved: The MDNTB(I) is responsible for working with multiple organizations in executing the OTA. These organizations include, but are not limited to: • U.S. Department of Defense: - Combatant Commands (COCOMs); [European Command (EUCOM), Strategic Command (STRATCOM), Northern Command (NORTHCOM), Pacific Command (PACOM), and Central Command (CENTCOM)] - Missile Defense Agency - U.S. Air Force - U.S. Navy - U.S. Army - Office of Secretary of Defense and National Command Authorities - Defense Information Systems Agency (DISA) • U.S. Department of State • Commercial contractors for other BMDS Elements, including but not limited to: - Terminal High Altitude Area Defense (THAAD) (Lockheed Martin) - Ground Based Missile Defense (GMD) (The Boeing Company) - AN/TPY-2 Radar (Raytheon) - BMDS Targets (Lockheed Martin) - Aegis BMD (Lockheed Martin and Raytheon) - Phased-Array Tracking Radar to Intercept On Target (PATRIOT) (Raytheon) - Space Tracking and Surveillance System (STSS) (Northrop Grumman) - Space-Based Infrared System (SBIRS) (Lockheed Martin) - Cobra Dane (Raytheon) - Sea-Based X-Band Radar (SBX) (Raytheon) • Allied and host nation foreign governments, as required 3) Work Activities. The MDNTB(I) is responsible for the following: a) Operations and Support. Sustain and maintain fielded C2BMC operational hardware/software (including all related AN/TPY-2 radar communications and C2MBC interface capabilities) on a 24 hours/day, 7 days/week, 365 days/year basis via, on-site support teams, C2BMC Control Center (CCC) operations, BMDS Network Operations and Security Center (BNOSC), and appropriate configuration management and sustaining engineering. Provide the capability to respond to emergency operations and or integration of new technologies in response to changing threats. Develop, maintain, and conduct operations and operational/support training for the operational C2BMC system, to include that used by friends and allies (where applicable). b) BMDS Communications Network Interface. Interface with long-haul communications provided by DISA, operating commands, and military Services. The BMDS Communications Network (BCN) ties together sensors (both BMDS radars and space sensors) and weapons systems via the Combatant Command-Command and Control (COCOM C2) screens and Global Engagement Manager (GEM), enabling the National Command Authority and the commanders at the strategic, theater and tactical levels to optimally engage ballistic missile threats at any range, in any phase of flight, and at any time, including near simultaneous theater, regional and homeland attacks. The BMDS Communications Network builds on existing and new global grid data and communications networks to provide a robust, end-to-end, high availability, operational Communications Network (COMNET) infrastructure that quickly and unambiguously shares information across the global BMDS. This sharing of information is performed securely with special emphasis on preventing cyber attack via the BNOSC. Effective networking management and operations relies on the ability to manage, coordinate, and integrate a wide variety of equipment platforms; interfaces with other DoD communications systems; existing/evolving information standards and capabilities, and adherence to DoD Information Assurance Certification and Accreditation Process (DIACAP). DISA services are highly leveraged in providing world-wide communications. c) Development of New C2BMC Capability. The C2BMC Program employs a robust incremental development program to deliver enhanced and new capabilities to the warfighter. Each increment of capability includes the software capabilities, hardware, network connectivity, training, and logistics support. Technical capability requirements included in each software spiral are determined by the MDA Systems Engineering Directorate, in coordination with the C2BMC Program Office. Current hardware capabilities include, but are not limited to, Enterprise Work Stations (warfighter display monitors and access to BMD Planner, Situational Awareness, and Battle Management information), servers, processors, communications racks and equipment, Situational Awareness web browsers, stand-alone laptop BMD Planners, and video distribution equipment. i. Systems Engineering. Establish and follow a disciplined systems engineering process across the full spectrum of the C2MBC System, including configuration management, modeling and simulation, and test and integration processes are critical to providing U.S. and international capabilities (where applicable). ii. Quality Engineering. Implement a Parts, Material, and Process (PMAP) Program, an Operations Security (OPSEC) Plan, and comply with the MDA Security Classification Guide for secure development environment. Conduct test planning, management, and analysis, support the MDA Program Control Board process, and transition capabilities to operations. Incorporate internal and independent configuration audits as part of configuration control. Include a specialty engineering program to include safety, reliability, maintainability, human factors and information assurance engineering and the development and verification of suitability design requirements. iii. Hardware Engineering. The C2BMC System uses Commercial-off-the-Shelf (COTS) computer equipment to the maximum extent possible. For the OTA follow-on activity in 2012 onward, the Government anticipates the hardware will require a major technology refresh activity in conjunction with the development of the new software spiral. This technology refresh may span from updating key parts to a complete hardware infrastructure replacement. The current commercial hardware infrastructure will be approximately ten years old and may reach the point that replacement is mandatory due to logistics support difficulties. Additionally a new software build will be designed and built at the same time. Replacement of the previous hardware suite may provide additional capability performance improvements that also justify replacement of the hardware. iv. Spiral Development of Software Capabilities. The C2BMC Program uses spiral development (i.e., incremental development, test, and fielding) to produce the hardware, algorithms, software, network connectivity, and fielded support required to provide a system-wide, integrated ballistic missile defense capability. As C2BMC products mature they are engineered and integrated into fielded spirals. The average timeframe to develop and field a spiral is 24-36 months (depending on requirements and funding stability), with a new spiral fielded approximately every two years. Multiple spirals are in staggered stages of engineering and development at any time. Delivered spirals enable progressively increased abilities to plan ballistic missile defense, see the battle unfold on common Situational Awareness displays, remotely manage sensors worldwide, process track data to discern warhead and associated ballistic path and forward engagement information to BMD weapons systems (such as GMD, THAAD, PATRIOT, and Aegis BMD) across a global-grid communications network to defeat an adversary's attack. C2BMC software capabilities are provided in four areas: BMD Planner, Situational Awareness, C2BM Network, and GEM. • BMD Planner: The BMD Planner provides warfighters the capability to explore the effectiveness of various defensive designs in order to plan the most effective defense by optimizing the location and mix/pairing of sensors and interceptors. The BMD Planner allows the warfighter to function in three modes of activity: Deliberate Planning (24-36 months before a battle), Crisis Action Planning (hours or days before an attack, based on updated information), and Dynamic Planning (near real-time agility for changing situations). System models used in the BMD Planner include the GMD system, AN/TPY-2 radar, Aegis BMD, PATRIOT, and THAAD. • Situational Awareness: This capability is used to turn detailed data into usable information that commanders can act on in the event of a missile defense threat. Situational Awareness information is provided by the COCOM C2 screens (displays and decision aids). Situational Awareness display emphasizes a common ballistic missile picture and summary screens used at the Presidential level down to the operational level of command. The systems available include an interface with the GMD Fire Control, and Aegis BMD and PATRIOT via Link 16, sensor management control of the AN/TPY-2 radar, and a direct data connection to SBIRS information. • Command and Control, Battle Management (C2BM) Network: The C2BMC System includes the communications network capability that is required to support the C2BM functionality, and the movement of data and information within the C2BMC System’s applications (i.e., the network capability specifically tied to the execution of the core C2BMC capability). This is closely linked to, but not the same as the BMDS Communications Network referenced in paragraph 3.c.3.b, “BMDS Network Communications.” • Global Engagement Manager (GEM): The GEM provides the first BMDS battle management capability through the C2BMC System. GEM provides the foundation for various BMD Elements and external sensors and interceptors to work synergistically for optimal performance. The GEM will provide enhanced sensor management control of world-wide X-band radars, assign a specific sensor to track a specific threat, calculate the track of an incoming missile, and recommend the most effective weapon to target pairing, maximizing probability of hit/kill. 4. Response: Responses should be provided in accordance with the following guidelines. All responses should be limited to no more than twenty (20) 8.5 inch X 11 inch pages using Times New Roman 12 pt font, with one inch margins on top, bottom and sides (11 inch X 17 inch foldouts shall be counted as two pages). Responses should include the following information: a. Company profile to include number of employees, annual revenue history, office locations, DUNs number, etc. b. Explanation of the respondent’s ability to perform the capabilities described above (in whole or in part). This should include a description of the company’s effort in the past three years in support of same/similar requirement(s). Include information such as contract number (indicate if your role was a prime or subcontractor), organization supported, contract value, Government points of contact and current telephone numbers, and a brief description of how the contract referenced relates to the technical services described herein. Of particular interest are past performance examples where the company has developed international capabilities with host nations that share resources and sustain interoperability with U.S. systems; experiences where company has managed multiple contractors in a unified team developing capabilities; and experiences in fast-paced, dynamic programs with constant requirements change. c. Describe the company’s recommended approach to transition work from the current provider to ensure no break in C2BMC service and operation, and minimize schedule impact derived from transition. The company should also discuss whether it currently has specific expertise needed to execute the activities described in this RFI, or how it would gain such expertise. d. If the company recommends parts of the C2BMC Program for separate development, provide the strategy to seamlessly integrate its parts with the other parts it is not providing with minimal schedule, cost, and performance risk. e. Describe the company’s approach in fostering relationships within and across the BMDS Elements and their respective industry team (to include, but not limited to GMD, THAAD, and Aegis BMD) to ensure responsive and efficient working relationships. f. Describe the company’s recommendation on how to foster innovation within the C2BMC Program to provide new approaches to C2BMC development. Alternate approaches to C2BMC architecture and development may be considered. Explain the alternate approach and provide examples of its performance. 5. Marking. Any proprietary information should be properly marked. Potential sources are responsible for adequately marking propriety information contained in their response. 6. Response Submissions. Packages must be submitted electronically to the Contracting Officer using Microsoft Word or Portable Document Format (PDF) at the following address:
[email protected]. All responses to this announcement must be received by 21 June 2010. Submitted information will not be returned to the respondent. MDA may not acknowledge receipt of responses to this RFI. If a receipt is desired, potential sources should submit statements electronically and select “read receipt request” from electronic mail options. Communications with MDA with regard to this RFI will be permitted only electronically during the RFI response period, ending 21 June 2010. 7. Response Review. Information received will be considered solely for the purpose of determining the follow-on acquisition strategy. Notwithstanding the responses received, the follow-on acquisition strategy is at the Government’s sole discretion. The Government may use selected Federally Funded Research and Development Corporations (FFRDC), Advisory and Assistance Services, (A&AS), and Systems Engineering and Technical Assistance (SETA) contractor personnel to assist in the evaluation and administrative handling of responses submitted to this announcement. Specifically MITRE, SPARTA (and their subcontractors), and CTI personnel may be used. These persons are bound by appropriate non-disclosure agreements to protect proprietary and source selection information. The Contracting/Agreements Officer will conduct an Organizational Conflict of Interest (OCI) review to ensure that evaluators do not evaluate proposals of their competitors or of their own company. Additionally, industry partners providing the requested support must comply with applicable OCI requirements. For guidance on OCIs, see FAR Subpart 9.5. 8. Security Clearance. The highest level of personnel and facility security classifications assigned to the current program is Top Secret / Sensitive Compartmented Information (SCI).