Revised Synopsis notice for the Integrated Air and Missile Defense (IAMD)Battle Command System (IBCS)Development Program, Request for Proposal (RFP) W31P4Q-06-R-0275

Subject: Synopsis for the Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) Development Program, Request for Proposal (RFP) W31P4Q-06-R-0275

Description:

The United States Army, through the Integrated Air and Mi ssile Defense (IAMD) Project Office, Huntsville, Alabama, and the U.S. Army Aviation and Missile Command (AMCOM) Acquisition Center, Redstone Arsenal, AL, has a requirement for a full and open competitive procurement for the Integrated Air and Missile Defe nse (IAMD) Battle Command System (IBCS) Development Program procurement, which will be issued by the U.S. Army AMCOM, Acquisition Center, Bldg 5303, Redstone Arsenal, Alabama 35898-5280.

The IBCS Development Program (FY 08 - FY 14) will encompass ac quiring program management, systems engineering, integration, manufacturing, test, logistics, initial production, training and deployment of the IBCS Major End Items (MEIs), the IAMD Integrated Fire Control Network (IFC-Net) and supporting products.
Todays Air and Missile Defense (AMD) systems, composed of weapons, sensors and Battle Management, Command, Control, Communications, Computers and Intelligence (BMC4I) end items, operate as self-contained entities with inherent design limitations. These systems have limited interoperability with other AMD systems and the joint community, but are unable to conduct fully integrated operations. The Army intends to connect individual weapon (launchers with interceptors) and sensor components directly onto a network to achieve net centric operations utilizing IBCS Development Program products. This includes integration and leveraging of existing and planned Future Combat Systems (FCS), Missile Defense Agency (MDA), Single Integrated Air Picture (SIAP), Army Battle Command System (ABCS), and Army IAMD capabilities.

The contracting strategy calls for a negotiated procurement, with full and open competition, for the selection of an IBCS development source using a rolling down-select method. The source selection will be conducted in two steps. The first step will be the award of up to two (2) Phase I IBCS Preliminary Design contracts with follow-on Phase II/III options. The second step in the source selection consists of an evaluation of Phase I effor ts and updated proposals to select a single offeror that presents the best value to the Government to obtain an award/exercise an option for a Phase I Post IBCS Preliminary Design effort leading to a subsequent Phase II IBCS System Development and Demons tration (SDD) option to be exercised after IAMD Milestone (MS) B approval. Additionally, at the discretion of the Government, the Phase II IBCS early contingency capability option(s) could also be exercised at the culmination of IAMD MS B.

The ori ginal contract award (Phase I) will be for an eleven (11) month period of performance. The original contract award and all options to be exercised during Phase I will be Cost Plus Fixed Fee (CPFF) efforts. The requirement will have a follow-on Post IBCS Preliminary Design Option 1, which will be for an additional four (4) month period of performance. The requirement will also have an IBCS Phase I Extension Activities Option 2, which will be for an additional eight (8) month period of performance. The SD D Phase of the contract (Phase II) will have a total period of performance of fifty-two (52) months. All options exercised during Phase II will be issued as Cost Plus Incentive Fee (CPIF) efforts. This will include Option 3, for IBCS SDD effort; Option 4 , for Additional IBCS Demonstration End items; Option 5, for IBCS Early Contingency Capability (ECC) Implementation and Demonstration; Option 6-8, which will be one year options for IBCS ECC Interim Logistics Support; and Option 9 for IBCS Low Rate Initial Production (LRIP) Long Lead Items. The Production and Deployment Phase (Phase III) of the contract will have an eleven (11) month period of performance. The requirement will include Option 10 for Test and Engineering Services, which will be issued as a CPFF effort; Option 11, for LRIP, which will be issued as a CPIF effort; Option 12, for LRIP Contractor Logistics Support, which will be issued as a CPFF effort ; and Option 13, for New Equipment Training, which will be issue as a CPFF effort.

OFFERORS ARE ADVISED THAT PERFORMANCE ON THIS PROPOSED CONTRACT WILL REQUIRE ACCESS TO DEFENSE INFORMATION / EQUIPMENT THAT IS NOT CONSIDERED APPROPRIATE FOR RELEASE TO NON-U.S. COMPANIES. THEREFORE, PARTICIPATION AT THE PRIME CONTRACTOR LEVEL IS RESTRICTED TO U.S. COMPANIES. REQUESTS FROM FOREIGN INDUSTRY FOR THE IBCS DEVELOPMENT SOLICITATION WILL NOT BE HONORED. REQUESTS FROM QUALIFIED BIDDERS FOR PARTICIPATION OF FOREIGN NATIONALS, SUBCONTRACTING TO FOREIGN COMPANIES OR PURCHASE OF FOREIGN DEVELOPED PARTS AND/OR MATERIALS WILL BE MADE IAW THE DD FORM 254.

Offerors must register to obtain access to the RFP and attachments through the limited access Program Executive Office (PEO) Missile and Space (MS) Safe website located at: https://ibcs.msl.army.mil/index_files/slide0002.html. Once at the web-site, click on the hyperlink Download RFP Sections and Attachment/Exhibit and then click on register for a new a ccount in the upper left hand corner of the page and follow the registration instructions. Registration will be complete and offerors will be provided access to the website once their TOP SECRET facility clearance has been verified. Offerors will be notifi ed via email of registration approval. At the conclusion of the Pre-Proposal Presentation to Industry, the RFP and attachments will be available for download to registered offerors on the website.

The Government anticipates conducting a Pre-Proposa l Presentation to Industry on 20 Feb 08 to brief industry on technical details concerning the Single Integrated Air Picture (SIAP) Joint Program Office (JPO) provided capabilities, and the Missile Defense Agency (MDA) provided capability. Only registered offerors and their teammates may attend the Pre-Proposal Presentation to Industry. These attendees must provide a visit request to the point of contact listed below no later than 14 Feb 08, 1600 Central Standard Time (CST).

Name: Lear Lynch
Ph one: (256) 842-7503
Fax Numbers: (256) 876-5234 or (256) 842-7684
Email: lear.lynch@conus.army.mil

An agenda for the Pre-Proposal Presentation to Industry will be provided by the Contracting Officer by email along with your Security and F acility Clearances confirmation.

Attendance at the Pre-Proposal Presentation to Industry is not required in order to receive a copy of the RFP and attachments so long as the offeror completes the registration and download the RFP a nd attachments no later than 31 Apr 08, 1600 CST.

The point of contact for this requirement is Contracting Officer, Ms. Mable Youngblood at 256-842-7326, mable.youngblood@conus.army.mil.

The Draft Request for Proposal previously released for this solicitation is no longer valid.

REVISED NOTICE -----DRAFT REQUEST FOR PROPOSAL W31P4Q-06-R-0275, INTEGRATED AIR AND MISSILE DEFENSE IAMD BATTLE COMMAND SYSTEM IBCS The draft RFP W31P4Q-06-R-0275 and all applicable attachments have been removed from the Acquisition Center web site by the Government. The web site utilized experienced technical difficulties and would not provide adequate access control of the RFP and a ttachments. As a result the Government has revised the means of gaining access to the draft RFP and applicable attachments as follows. The draft RFP and applicable attachments will be issued by the IAMD Project Office. In order to receive copies, all offerors are required to provide verification of their security clearance to the Contracting Officer before release of the draft RFP and ap plicable attachments. All security verifications shall be provided by email or fax to the Contracting Officer at the address and fax number indicated below no later than 1 Mar 07, 1200, Central Standard Time, CST. Once an offerors clearance has been verified by the Government, the IAMD Project Office will be notified, as well as the contractor, that an offeror is cleared to receive copies of the draft RFP and applicable attachments. A copy of the draft RFP and att achments can be provided electronically, Express mail on Compact Disk, or by pick-up from the IAMD Project Office, Monday thru Friday, 0800-1600, CST. The Contractor shall notify the Contracting Officer in advance, or at the time the security verificatio n is requested, the preferred method for receipt of the draft RFP and attachments. This notification shall be provided along with verification of the security clearance. Only one copy of the draft RFP and attachments shall be provided per contractor. De adline for pick-up of the draft RFP and attachment is 2 Mar 07 1600 CST. The due date for submittal of comments and/or questions reflected in Section L-24 of the draft RFP will be 10 working days from issuance of this notice, NLT 1600 CST, 2 Mar 07. Point of contact for this action is Mable N. Youngblood, 256-842-7326; Fax 256-842-7684 or 256-876-5234 mailto:mable.youngblood@redstone.army.mil or Dorphelia B. Foster, 256-876-4189; mailto:dorphelia.foster@redstone.army.mil Fax 256-842-7684 or 876-5234. All other terms and conditions of the draft RFP remain unchanged and in full force and effect except as provided above.

REVISED NOTIFICATION for the DRAFT REQUEST FOR PROPOSAL W31P4Q-06-R-0275, INTEGRATED AIR AND MISSILE DEFENSE IAMD BATTLE COMMAND SYSTEMS IBCS Draft RFP W31P4Q-06-R-0275 and all applicable attachments have been removed from the web. Additional information concerning release of RFP W31P4Q-06-R-0275 will be provided in the near future. Your points of contact for this requirement are Mable N. Youngblood, Contracting Officer, (256)842-7326; mailto:mable.youngblood@redstone.army.mil , and Dorphelia B. Foster (256)876-4189; mailto:dorphelia.foster@redstone.army.mil.

DRAFT REQUEST FOR PROPOSAL W31P4Q-06-R-0275, INTEGRATED AIR AND MISSLE DEFENSE IAMD BATTLE COMMAND SYSTEMS IBCS The DRAFT RFP for the IAMD IBCS requirement has been posted to the AMCOM Acquisition Center website: https://wwwproc.redstone.army.mil/acquisition/acqindex2.html . Once you enter the site, proceed as follows: 1. Enter Processing Point = PD9; 2. Click - View Existing Attachments and Exhibits for Solicitation; 3. Select a Solicitation Use down arrow to scroll and locate solicitation number W31PQ06R0275 without dashes; 4. A list of all applicable Attachments and Exhibit A is shown for your use. The DRAFT RFP and all applicable attachments are for planning purposes only. The Government reserves the right to change these documents. All information received will be used for planning purposes only. This notice does not constitute an Invitation for Bids, Request for Proposal, or Request for Quotes. The Government will not award a contract based on this notice and will not reimburse respondents for any cost associated with responses to this notice. Offierors should direct immediate attention to Section L of the RFP due to time restraints and deadlines reflected in Section L-18, L-24, and L-25. Formal release of the Request for Proposal RFP will be made in the immediate future. You will be notified of the RFP release and the location of the web sites in the near future. A Commerce Business Daily CBD announcement for bidders list purposes will be made before release of the RFP. Your points of contact for this requirement are Mable N. Youngblood, Contracting Officer, 256-842-7326; mailto:mable.youngblood@redstone.army.mil, and Dorphelia B. Foster 256-876-4189; mailto:dorphelia.foster@redstone.army.mil.

The Comman Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) Design, Development, Integration and Test Request for Information (RFI)is being re-issued due to ilegible narrative throughout the RFI initial submission. No informatio nal changes have been made to the following submission. The Program Executive Office, Missiles and Space on behalf of the United States Army is conducting a market survey to identify available technological solutions and approaches in support of the Integrated Air and Missile Defense (IAMD) Battle Command Syste m (IBCS) and to obtain information on risk, capability and price. The IBCS Component concept provides for an IAMD Common Battle Management, Command, Control, Communications, Computers and Intelligence (BMC4I) with Integrated Fire Control (IFC) hardware/sof tware product design, integration, and development that supports fielding of an IAMD Increment 2 Initial Operational Capability (IOC) in FY11. This notice is published in accordance with FAR Parts 10.002 and 15.201 and is a Request for Information (RFI) only in support of a market survey. All information received will be used for planning purposes only. This notice does not constitute an Invitat ion for Bids, Request for Proposal, or Request for Quotes. The Government will not award a contract based on this notice and will not reimburse respondents for any cost associated with responses to it. I. IAMD PROGRAM OVERVIEW: The U.S. Army transformation calls for a network-centric system-of-systems capability (also referred to as Plug and Fight) that integrates all Air and Missile Defense (AMD) sensors, weapons (including launchers) and BMC4I. This future IAMD System of Sys tems (SoS) architecture will enable the distributed support of engagements with available sensor assets not limited to system-centric organic sensors. AMD materiel transformation, along with other Doctrine, Organization, Training, Materiel, Leadership an d Education, Personnel and Facilities (DOTMLPF) changes, will be conducted in increments of improved capability through FY17. The IAMD Program represents a shift from a traditional system-centric weapon systems acquisition to a component-based acquisition approach. This component-based acquisition approach will provide the most efficient way to acquire and integrate the componen ts of the incremental IAMD architectures. Unlike traditional acquisition programs that focus primarily on the development of a single system or platform, the IAMD Program is structured to enable the development of an overarching net-centric capability wit h all participating AMD components functioning interdependently to provide total operational capabilities not achievable by the individual element systems. The IAMD Program achieves this objective by establishing the incremental IAMD architecture and deve loping the following: the IAMD Battle Command System (IBCS) that provides the common IAMD BMC4I capability, IFC Network capability to provide fire control connectivity and enabling distributed operations, and the Common Plug & Fight (P&F) Interface modifi cation kits that will enable weapon and sensors connectivity to the IFC network. Development of the component-unique part of the P&F Interfaces remains within the purview of the affected components project/product office. The IAMD Program will employ an evolutionary acquisition strategy consisting of multiple capability increments leading to an objective capability in FY17. This approach provides the opportunity for technology insertions into the program throughout each inc rement as high-payoff technologies mature and are ready for integration. This enables an orderly and cost-effective migration from the current system-centric architecture to the IAMD net-centric architecture. The first increment, Increment 1, is being imp lemented by the User Community, primarily involving non-materiel changes as the basis for follow-on incremental capabilities. Inc rement 2 is the focus of the IAMD Project Office. Increment 2 is structured to meet the emerging requirements for an integrated net-centric AMD capability by FY11. This capability is supported by an early Risk Mitigation phase for advancing key enabling initiatives while concurrently developing the Incre ment 2 architecture. The desired end-state of the IAMD Increment 2 physical architecture, consisting of PATRIOT, Surface Launched Advanced Medium Range Air-to-Air Missile (SLAMRAAM) Fire Unit, Advanced Sentinel, Terminal High Altitude Area Defense (THAAD), Joint Land Attack Cruise Missile Defense Elevated and Netted Sensor System (JLENS), and Medium Extended Air Defense System (MEADS) components working in an integrated manner via an IFC network to support the engagement of targets. The IFC Network will inc lude high bandwidth communications and integrated network management. The IFC Network will be Joint Net Ready Key Performance Parameters (KPP) compliant and will support AMD Composite Battalion Task Force (TF) operations. The IAMD Increment 2 will mainta in current force interfaces into Forward Area Air Defense Command and Control (FAADC2) and will include new interfaces into Future Combat System (FCS), while maintaining connectivity to the Army Battle Command System (ABCS). Other Increment 2 significant capabilities consist of the following: 1) Common battle command and control using common open services and software, and common hardware; 2) Elevated (JLENS Systems Development and Demonstration (SDD)), and ground-based 360 r adars; 3) Integrated combat identification (CID) across the IFC Network and with Joint networks; 4) Networked AMD sensors with common track management enabling both situational awareness and fire control for Air Breathing Targets (ABTs), Unmanned Aerial Ve hicles (UAV), Cruise Missile (CM), and Ballistic Missiles (BM) threats; 5) Integrated fire control across IFC Network that allows for engage on network data using PATRIOT Advanced Capability (PAC) 3, PAC-3 Missile Segment Enhancement (MSE), and/or SLAMRAAM weapons; 6) Integrated engagement operations across an IFC Network that provides for composite battalion TF battle management and engage on network data battle management: and 7) Integrated Force Operations / Engagement Operations (FO/EO) with collaborat ive planning and embedded training. The IAMD Program includes Increment 2 Systems Engineering, Integration and Test (SEI&T) activities and the development of enabling End Items (EIs) consisting of an IBCS Command Post (CP) and P&F Interface Modification Kits for applicable IAMD weapons and s ensor components. These EI products are built from modular hardware and software configuration items: open architecture computing environment, IAMD common software, communications, common platforms, common shelters, and Command Center System (CCS). Common configuration items will be evaluated and selected from Joint, other Services, and Army programs as applicable and feasible. The IAMD strategy is based on incremental consolidation and migration of BMC4I, weapons and sensor efforts using the international MEADS program and related PATRIOT-MEADS Combined Aggregate Program (CAP) extensions where appropriate. The IAMD architecture provides the underlying standards and protocols for the net-centric, P&F capability. The IBCS CPs and P&F Interface Modification Kits will include Joint solutions (as made available) such as a Joint Track Manager (JTM) and a Common Data Link Interface (C DLI) manager. Additionally, the IFC Network provides the framework to transfer fire control quality data over a high bandwidth communications channel between the IBCS and various weapons and sensors to prosecute engagements. The Joint Tactical Radio Syst em (JTRS) is identified to fill the IFC Network communications capabilities. Use of interim solutions in lieu of the Joint solution will be considered if the Joint solution does not meet near term milestones for developmen t or production. II. IBCS Statement of Objectives A. Overall Program Objectives The overall objective of the Increment 2 IBCS System Development and Demonstration (SDD) Phase is to design, develop, integrate and test the IBCS CP and P&F Mod Kit components necessary to enable the IAMD Network-centric Increment 2 architecture. 1. IAMD Overarching SEI&T Support - The IBCS contractor shall provide support to the Increment 2 overarching SEI&T and fielding activities of the IAMD Program. 2. IBCS CP Development - The contractor shall design, develop, integrate, and test a materiel releasable IBCS CP and develop technical data for all Increment 2 designated operational nodes and echelons that: 1) uses selected CAP 1 software and IAMD Govern ment Furnished Equipment/Government Furnished Information (GFE/GFI) common hardware/software configuration items that will be integrated and installed in the IBCS CP; 2) uses prime movers and shelters from a government provided source (e.g., CAP 1/ MEADS BMC4I, Command Post Program) or other available industry solutions; 3) incorporates other type classified/logistically supported Army common hardware configuration items where possible (e.g., Common Hardware Software 3 (CHS3) computing hardware); and 4) provides logistics support to operate and maintain the developmental hardware. 3. Plug and Fight (P&F) Interface Modification Kits Development - The contractor shall design, develop, integrate and test materiel releasable common P&F weapon and sensor modification kits that: 1) use IBCS managed common open architecture hardware and so ftware configuration items; and 2) use software product line type approaches to address maximum commonality and variation flexibility across all weapon and sensor components. The contractor shall deliver common P&F modification kits and provide integration support to designated weapon and sensor component integrators, who will integrate the common P&F modification kits with any component unique P&F modification kits. 4. IFC Network Development - The contractor shall design, develop, integrate and test the IAMD IFC network (high-bandwidth, fire control quality, voice and data communications) integrated into the IBCS CP and P&F Modification kits. 5. Establish, Develop (as necessary) and Manage Common Hardware and Software Configuration Items - The contractor shall evaluate, select, modify, develop (as necessary), integrate and manage common hardware and software configuration items in accordance wi th modular open architecture hardware and software architectures. For common hardware and software configuration item selections not already provided as associate sub-contractors, Government approval of make/buy decisions is required. Current IAMD common software products such as Integrated Defense Design, Common Data Link Interface Management, Common Warfighter Machine Interface, Joint Track Management and others are to be made available. The contractor shall develop additional common software modules ( not provided by the government) as required. 6. IBCS Component Integration and Test Support to IAMD - The contractor shall provide component integration and test support to the IAMD Increment 2 Program. Integration support will include supporting component (weapon, sensor) developers in testing for verifying component baseline performance verification. Integration will include, but is not limited to, verifying networked internal and external component interface interdependencies. The contractor shall maximize opportunities for early interoperabilit y certification data collection. 7. Fielding of an Increment 2 Initial Operational Capability (IOC) in FY 11 - The IBCS contractor shall support the Increment 2 IOC in FY11. The IOC will be declared when one (1) of the sixteen (16) AMD Composite Battalions, with attached JLENS Battery (B TRY) and THAAD BTRY, has been organizationally transformed and fully fielded with necessary IBCS components and IAMD enabled weapon and sensor components, as well as, associated special support items, troops are trained in the operation and maintenance of their respective systems, and Authorized Stockage List/Prescribed Load List (ASL/PLL) are issued to the units. The Increment 2 End Items quantities for the reference AMD composite battalion TF include: IBCS CP (AMD Composite Battalion TF) 10; IBCS CP (JLENS) 2; IBCS CP (THAAD) 1; P&F Mod Kits (PATRIOT Radar) 4; P&F Mod Kits (PATRIOT Launch Farm) 8; P& F Mod Kits (Sentinel Radar) 8; P&F Mod Kits (SLAMRAAM Fire Unit) 12; IFC Antenna Mod Kits (JLENS Platform) 2; Antenna Mod Kits (PATRIOT AMG) 4; and IFC Net Relay Modification Kits (PATRIOT CRG) 4. B. Technical Objectives 1. Open and Modular Software and Hardware Architecture/Standards - The IBCS component hardware and software design and implementation will be open, modular and transportable providing non-proprietary documentation required to facilitate the development and integration of third party Hardware/Software (HW/SW) and joint solutions. 2. Net Ready - The IBCS must fully support execution of joint critical operational activities identified in the applicable Joint, Inter-agency, Inter-governmental and Multi-national (JIIM) and system-integrated architectures, and the system must satisfy th e technical requirements for transition to net-centric military operations. 3. Integrated Defense Effectiveness - The IBCS will allow for flexible interceptor selection and firing doctrine within the TF. The IBCS managed integrated defenses will enable defeat of non-ballistic and ballistic platforms by exploiting fused organic and non-organic sensor data to conduct engagements up to the operationally effective range of selected missile kinematics. 4. Common Command and Control - The IBCS (Battalion and below) will incorporate common functionality that includes: defense planning, defense design, warfighter-machine interface, battle monitor and control, network interface and management (to include net initialization), track management, engagement planning, engagement decision, engagement monitoring, and staff functions. 5. Backwards Compatibility - IBCS will provide backward compatibility to enable integration and common functionality of the current force: PATRIOT battery/SLAMRAAM platoon with the Increment 2 equipped Task Force, Sentinel, and FAADC2. 6. Sustainability/Reliability - The IBCS will achieve an Operational Availability (Ao) of at least 95% and a maintenance ratio (maintenance man hours to operating hours [MMH/OH]) equal to or less than .05. 7. Force Protection and Survivability - The IBCS will be designed to be operated by soldiers wearing body armor and carrying appropriate weapons. All vehicle cabs and manned shelters should be capable of adding up-armor protection. Manned rigid wall shelt ers incorporated into the IBCS will provide an active overpressure system to prevent contamination during a Chemical, Biological, Radiological, Nuclear and Explosive (CBRNE) event that is sustainable through decontamination. 8. Battle Command on the Move - The IBCS will exploit situational awareness and understanding via the Command Operating Picture (COP) which is available to the supported force during mobile operations. C. Contract Objectives 1. IBCS Development - Multiple new or modified contracts will implement the program and technical objectives. GFE/GFI Common HW/SW configuration items within the HW/SW product-line will be integrated with other IBCS contractor provided HW/SW configuration items and used in the IBCS CP and weapon/sensor P&F modification kits. 2. Software and Hardware Data Rights Ensuring Open Architecture - The IBCS contractor shall provide software and hardware data rights to the Government to ensure that the IAMD architecture and implementation is open to third party technology acquisition an d insertion, as well as, providing key hardware or sof tware reuse configuration items to follow-on increments and other military systems. 3. Contract Relationships -The IBCS contractor shall establish a formal relationship with existing common software developers, the overarching IAMD SEI&T contractor, and weapons/sensors contractors. 4. Contract Phasing - A base contract effort for the IBCS system engineering activities will culminate in an IBCS Risk Reduction Design Review which will support the IAMD Preliminary Design Review (PDR). The contract will include an option for ful l System Development and Demonstration activities, awarded based upon the successful completion of the IAMD PDR and Defense Acquisition Board (DAB) authorization. D. Program Management/ Cost/ Schedule Objectives 1. Ensure Program Documentation and Data is Non-Proprietary - The IBCS contractor shall provide program documentation in a manner that provides full insight into the processes, rationale, and results of the work. Documentation should be non-proprie tary to facilitate the ease of program integration with other internal and external Joint and Army programs. 2. Facilitate a Life Cycle Management Focus - Current baseline and IBCS life cycle management metrics will be collected and reported in conjunction with major system reviews to demonstrate the objectives associated with the reduction of logistics fo otprints and operations and sustainment (operations and support) cost. These metrics will include (but not be limited to) IBCS HW/SW configuration item quantity comparison, Software Lines of Code (SLOC) comparison, number of Computer Software Configuratio n Items (CSCIs), user screen count comparisons, training support package comparison, and unique or single source HW/SW configuration items. 3. Best of Breed BMC4I Configuration Item Selection Processes - The IBCS contractor shall provide an acquisition approach that uses cost effective best of breed IBCS common HW/SW GFE/GFI configuration items; integrating them into incremental IBCS CP and P&F modification kits. 4. Meet IAMD Schedule Objectives - The IBCS contractors development schedule shall support the top level IAMD Increment 2 Program Milestones: PDR - September 2007; Critical Design Review (CDR) - May 2008; Design Readiness Review (DRR) - April 2009 ; Milestone C (MS C) - March 2010; and IOC - September 2011. The IBCS market survey will be conducted in two phases: 1) White papers describing the technical approach submitted to the Government Contracting Officer specified below by 22 Sep 06 followed by 2) an Industry Day to be announced at a subsequent date. The Government will not reimburse respondents for any costs associated with responses to this notice or participation in any Industry Day. White papers submitted as a result of this market survey, will facilitate the IAMD Project Office in the formulation o f an Acquisition Plan and eventually a follow-on Request for Proposal (RFP) for an IBCS System Development and Demonstration (SDD) contract. More information on Industry Day will be provided at a later date to include foreign disclosure and security guidelines. Respondents may submit questions in writing to the following points of contact: Mable N. Youngblood, (256) 842-7326, Email: Mable.Yo ungblood@redstone. army.mil; Dorphelia B. Foster, (256) 876-4189, Email: dorphelia.foster@redstone.army.mil; and Stacy Potts, (256) 842-7503, Email: stacy.potts@redstone.army.mil by 22 Sep 06. Appropriate Government response to submitted questions will be provided at Industry Day. White paper responses will consist of an Unclassified white paper on 8.5 x 11 inch paper with fonts no smaller than 12 point, one inch margins, in a Microsoft Word or Adobe file format. Each page of the submission shall contain the document identifier in t he document header. Respondents should label any information contained in the white paper that is considered proprietary. At a minimum, t he white paper shall provide 1) a description of the technical and programmatic approach with key risks and suggested mitigation approaches that address the IBCS statement of objectives, as well, as technical, contract and program management/cost/ schedule objectives; 2) a description of specific technical and programmatic approaches, to include a concept for technical documentation needed, for integrating third party solutions in an open BMC4I hardware and software architecture; 3) provide a rough order of magnitude cost; 4) comments on the IBCS Statement of Objectives, as well technical, contract and program management/cost/schedule objectives; and 5) a brief description of the firms capability and experience in providing systems in this mission area and any history of integrating third party solutions in an open BMC4I hardware and software architecture. Any contractor providing proprietary responses must be either willing to authorize disclosure of these responses to Team Innovation in Integration and all IAMD SETA contractors or make other appropriate confidentiality agreements prior to responses being c onsidered. Current IAMD SETA contractors are BAE Systems Analytical Solutions, Inc.; Dynetics, CAS and Davidson, LLC; Tecolote, Inc.; and Westar Aerospace and Defense Group, Inc. An IAMD Program Overview Briefing packet that further outlines the program will be available at the PEO Missiles and Space web site: http://www.msl.army.mil. under the IAMD Section. If you experience any problems acccessing the web site, contact Mr. Ken B ragg (256)313-3458 or email at Ken.Bragg@us.army.mil. The white paper will be limited to 50 total pages including tables, charts, and figures. The white paper will include a technical Point of Contact (POC), phone number and email. Two copies of the white paper are requested (one hard copy and one readable C ompact Disk (CD). All white papers must be received by the Contracting Officer at the following address: U. S. Army Aviation and Missile Command (AMCOM), Acquisition Center, AMSAM-AC-SM-C/ATTN: Mable N. Youngblood, Redstone Arsenal, AL 35898-5280 Not La ter Than (NLT) 1600 Hrs. (Central) on 22 Sep 06. Requests received in any other manner will not be honored.

REQUEST FOR INFORMATION (RFI)----The Program Executive Office, Missiles and Space on behalf of the United States Army is conducting a market survey to identify available technological solutions and approaches in support of the Integrated Air and Miss ile Defense (IAMD) Battle Command System (IBCS) and to obtain information on risk, capability and price. The IBCS Component concept provides for an IAMD Common Battle Management, Command, Control, Communications, Computers and Intelligence (BMC4I) with Int egrated Fire Control (IFC) hardware/software product design, integration, and development that supports fielding of an IAMD Increment 2 Initial Operational Capability (IOC) in FY11. This notice is published in accordance with FAR Parts 10.002 and 15.201 and is a Request for Information (RFI) only in support of a market survey. All information received will be used for planning purposes only. This notice does not constitute an Invitat ion for Bids, Request for Proposal, or Request for Quotes. The Government will not award a contract based on this notice and will not reimburse respondents for any cost associated with responses to it. I. IAMD PROGRAM OVERVIEW: The U.S. Army transformation calls for a network-centric system-of-systems capability (also referred to as Plug and Fight) that integrates all Air and Missile Defense (AMD) sensors, weapons (including launchers) and BMC4I. This future IAMD System of Sy stems (SoS) architecture will enable the distributed support of engagements with available sensor assets not limited to system-centric organic sensors. AMD materiel transformation, along with other Doctrine, Organization, Training, Materiel, Leadership a nd Education, Personnel and Facilities (DOTMLPF) changes, will be conducted in increments of improved capability through FY17. The IAMD Program represents a shift from a traditional system-centric weapon systems acquisition to a component-based acquisition approach. This component-based acquisition approach will provide the most efficient way to acquire and integrate the compone nts of the incremental IAMD architectures. Unlike traditional acquisition programs that focus primarily on the development of a single system or platform, the IAMD Program is structured to enable the development of an overarching net-centric capability wi th all participating AMD components functioning interdependently to provide total operational capabilities not achievable by the individual element systems. The IAMD Program achieves this objective by establishing the incremental IAMD architecture and dev eloping the following: the IAMD Battle Command System (IBCS) that provides the common IAMD BMC4I capability, IFC Network capability to provide fire control connectivity and enabling distributed operations, and the Common Plug & Fight (P&F) Interface modif ication kits that will enable weapon and sensors connectivity to the IFC network. Development of the component-unique part of the P&F Interfaces remains within the purview of the affected components project/product office. The IAMD Program will employ an evolutionary acquisition strategy consisting of multiple capability increments leading to an objective capability in FY17. This approach provides the opportunity for technology insertions into the program throughout each in crement as high-payoff technologies mature and are ready for integration. This enables an orderly and cost-effective migration from the current system-centric architecture to the IAMD net-centric architecture. The first increment, Increment 1, is being im plemented by the User Community, primarily involving non-materiel changes as the basis for follow-on incremental capabilities. Increment 2 is the focus of the IAMD Project Office. Increment 2 is structured to meet the emerging requirements for an integrated net-centric AMD capability by FY11. This capability is supported by an early Risk Mitigation phase for advancing key enabling initiative s while concurrently developing the Increment 2 architecture. The desired end-state of the IAMD Increment 2 physical architecture, consisting of PATRIOT, Surface Launched Advanced Medium Range Air-to-Air Missile (SLAMRAAM) Fire Unit, Advanced Sentinel, Ter minal High Altitude Area Defense (THAAD), Joint Land Attack Cruise Missile Defense Elevated and Netted Sensor System (JLENS), and Medium Extended Air Defense System (MEADS) components working in an integrated manner via an IFC network to support the engage ment of targets. The IFC Network will include high bandwidth communications and integrated network management. The IFC Network will be Joint Net Ready Key Performance Parameters (KPP) compliant and will support AMD Composite Battalion Task Force (TF) oper ations. The IAMD Increment 2 will maintain current force interfaces into Forward Area Air Defense Command and Control (FAADC2) and will include new interfaces into Future Combat System (FCS), while maintaining connectivity to the Army Battle Command Syste m (ABCS). Other Increment 2 significant capabilities consist of the following: 1) Common battle command and control using common open services and software, and common hardware; 2) Elevated (JLENS Systems Development and Demonstration (SDD)), and ground-based 360 radars; 3) Integrated combat identification (CID) across the IFC Network and with Joint networks; 4) Networked AMD sensors with common track management enabling both situational awareness and fire control for Air Breathing Targets (ABTs), Unmanned Aerial V ehicles (UAV), Cruise Missile (CM), and Ballistic Missiles (BM) threats; 5) Integrated fire control across IFC Network that allows for engage on network data using PATRIOT Advanced Capability (PAC) 3, PAC-3 Missile Segment Enhancement (MSE), and/or SLAMRAA M weapons; 6) Integrated engagement operations across an IFC Network that provides for composite battalion TF battle management and engage on network data battle management: and 7) Integrated Force Operations / Engagement Operations (FO/EO) with collabora tive planning and embedded training. The IAMD Program includes Increment 2 Systems Engineering, Integration and Test (SEI&T) activities and the development of enabling End Items (EIs) consisting of an IBCS Command Post (CP) and P&F Interface Modification Kits for applicable IAMD weapons and sensor components. These EI products are built from modular hardware and software configuration items: open architecture computing environment, IAMD common software, communications, common platforms, common shelters, and Command Center System (CCS). Comm on configuration items will be evaluated and selected from Joint, other Services, and Army programs as applicable and feasible. The IAMD strategy is based on incremental consolidation and migration of BMC4I, weapons and sensor efforts using the international MEADS program and related PATRIOT-MEADS Combined Aggregate Program (CAP) extensions where appropriate. The IAMD architectur e provides the underlying standards and protocols for the net-centric, P&F capability. The IBCS CPs and P&F Interface Modification Kits will include Joint solutions (as made available) such as a Joint Track Manager (JTM) and a Common Data Link Interface ( CDLI) manager. Additionally, the IFC Network provides the framework to transfer fire control quality data over a high bandwidth communications channel between the IBCS and various weapons and sensors to prosecute engagements. The Joint Tactical Radio Sys tem (JTRS) is identified to fill the IFC Network communications capabilities. Use of interim solutions in lieu of the Joint solution will be considered if the Joint solution does not meet near term milestones for development or production. II. IBCS STATEMENT OF OBJECTIVES A. OVERALL PROGRAM OBJECTIVES The overall objective of the Increment 2 IBCS System Development and Demonstration (SDD) Phase is to design, develop, integrate and test the IBCS CP and P&F Mod Kit comp onents necessary to enable the IAMD Network-centric Increment 2 architecture. 1. IAMD Overarching SEI&T Support - The IBCS contractor shall provide support to the Increment 2 overarching SEI&T and fielding activities of the IAMD Program. 2. IBCS CP Development - The contractor shall design, develop, integrate, and test a materiel releasable IBCS CP and develop technical data for all Increment 2 designated operational nodes and echelons that: 1) uses selected CAP 1 software and IAMD Govern ment Furnished Equipment/Government Furnished Information (GFE/GFI) common hardware/software configuration items that will be integrated and installed in the IBCS CP; 2) uses prime movers and shelters from a government provided source (e.g., CAP 1/ MEADS BMC4I, Command Post Program) or other available industry solutions; 3) incorporates other type classified/logistically supported Army common hardware configuration items where possible (e.g., Common Hardware Software 3 (CHS3) computing hardware); and 4) provides logistics support to operate and maintain the developmental hardware. 3. Plug and Fight (P&F) Interface Modification Kits Development - The contractor shall design, develop, integrate and test materiel releasable common P&F weapon and sensor modification kits that: 1) use IBCS managed common open architecture hardware and so ftware configuration items; and 2) use software product line type approaches to address maximum commonality and variation flexibility across all weapon and sensor components. The contractor shall deliver common P&F modification kits and provide integration support to designated weapon and sensor component integrators, who will integrate the common P&F modification kits with any component unique P&F modification kits. 4. IFC Network Development - The contractor shall design, develop, integrate and test the IAMD IFC network (high-bandwidth, fire control quality, voice and data communications) integrated into the IBCS CP and P&F Modification kits. 5. Establish, Develop (as necessary) and Manage Common Hardware and Software Configuration Items - The contractor shall evaluate, select, modify, develop (as necessary), integrate and manage common hardware and software configuration items in accordance wi th modular open architecture hardware and software architectures. For common hardware and software configuration item selections not already provided as associate sub-contractors, Government approval of make/buy decisions is required. Current IAMD common software products such as Integrated Defense Design, Common Data Link Interface Management, Common Warfighter Machine Interface, Joint Track Management and others are to be made available. The contractor shall develop additional common software modules ( not provided by the government) as required. 6. IBCS Component Integration and Test Support to IAMD - The contractor shall provide component integration and test support to the IAMD Increment 2 Program. Integration support will include supporting component (weapon, sensor) developers in testing for verifying component baseline performance verification. Integration will include, but is not limited to, verifying networked internal and external component interface interdependencies. The contractor shall maximize opportunities for early interoperabilit y certification data collection. 7. Fielding of an Increment 2 Initial Operational Capability (IOC) in FY 11 The IBCS contractor shall support the Increment 2 IOC in FY11. The IOC will be declared when one (1) of the sixteen (16) AMD Composite Battalions, with attached JLENS Battery (B TRY) and THAAD BTRY, has been organizationally transformed and fully fielded with necessary IBCS components and IAMD enabled weapon and sensor components, as well as, associated special support items, troops are trained in the operation and maintenance of their respective systems, and Authorized Stockage List/Prescribed Load List (ASL/PLL) are issued to th e units. The Increment 2 End Items quantities for the reference AMD composite battalion TF include: IBCS CP (AMD Composite Battalion TF) 10; IBCS CP (JLENS) 2; IBCS CP (THAAD) 1; P&F Mod Kits (PATRIOT Radar) 4; P&F Mod Kits (PATRIOT Launch Farm) 8; P&F Mod Kits (Sentinel Radar) 8; P&F Mod Kits (SLAMRAAM Fire Unit) 12; IFC Antenna Mod Kits (JLENS Platform) 2; Antenna Mod Kits (PATRIOT AMG) 4; and IFC Net Relay Modification Kits (PATRIOT CRG) 4. B. TECHNICAL OBJECTIVES 1. Open and Modular Software and Hardware Architecture/Standards - The IBCS component hardware and software design and implementation will be open, modular and transportable providing non-proprietary documentation required to facilitate the development and integration of third party Hardware/Software (HW/SW) and joint solutions. 2. Net Ready - The IBCS must fully support execution of joint critical operational activities identified in the applicable Joint, Inter-agency, Inter-governmental and Multi-national (JIIM) and system-integrated architectures, and the system must satisfy th e technical requirements for transition to net-centric military operations. 3. Integrated Defense Effectiveness - The IBCS will allow for flexible interceptor selection and firing doctrine within the TF. The IBCS managed integrated defenses will enable defeat of non-ballistic and ballistic platforms by exploiting fused organic and non-organic sensor data to conduct engagements up to the operationally effective range of selected missile kinematics. 4. Common Command and Control - The IBCS (Battalion and below) will incorporate common functionality that includes: defense planning, defense design, warfighter-machine interface, battle monitor and control, network interface and management (to include net initialization), track management, engagement planning, engagement decision, engagement monitoring, and staff functions. 5. Backwards Compatibility - IBCS will provide backward compatibility to enable integration and common functionality of the current force: PATRIOT battery/SLAMRAAM platoon with the Increment 2 equipped Task Force, Sentinel, and FAADC2. 6. Sustainability/Reliability - The IBCS will achieve an Operational Availability (Ao) of at least 95% and a maintenance ratio (maintenance man hours to operating hours [MMH/OH]) equal to or less than .05. 7. Force Protection and Survivability The IBCS will be designed to be operated by soldiers wearing body armor and carrying appropriate weapons. All vehicle cabs and manned shelters should be capable of adding up-armor protection. Manned rigid wall shelt ers incorporated into the IBCS will provide an active overpressure system to prevent contamination during a Chemical, Biological, Radiological, Nuclear and Explosive (CBRNE) event that is sustainable through decontamination. 8. Battle Command on the Move - The IBCS will exploit situational awareness and understanding via the Command Operating Picture (COP) which is available to the supported force during mobile operations. C. CONTRACT OBJECTIVES 1. IBCS Development - Multiple new or modified contracts will implement the program and technical objectives. GFE/GFI Common HW/SW configuration items within the HW/SW product-line will be integrated with other IBCS contractor provided HW/SW configuration items and used in the IBCS CP and weapon/sensor P&F modification kits. 2. Software and Hardware Data Rights Ensuring Open Architecture The IBCS contractor shall provide software and hardware data rights to the Government to ensure that the IAMD architecture and implementation is open to third party technology acquisition an d insertion, as well as, providing key hardware or software reuse configuration items to follow-on increments and other military systems. 3. Contract Relationships The IBCS contractor shall establish a formal relationship with existing common software developers, the overarching IAMD SEI&T contractor, and weapons/sen sors contractors. 4. Contract Phasing - A base contract effort for the IBCS system engineering activities will culminate in an IBCS Risk Reduction Design Review which will support the IAMD Preliminary Design Review (PDR). The contract will include an option for full System Development and Demonstration activities, awarded based upon the successful completion of the IAMD PDR and Defense Acquisition Board (DAB) authorization. D. PROGRAM MANAGEMENT/ COST/ SCHEDULE OBJECTIVES 1. Ensure Program Documentation and Data is Non-Proprietary The IBCS contractor shall provide program documentation in a manner that provides full insight into the processes, rationale, and results of the work. Documentation should be non-proprietary to facilitate the ease of program integration with other internal and external Joint and Army programs. 2. Facilitate a Life Cycle Management Focus Current baseline and IBCS life cycle management metrics will be collected and reported in conjunction with major system reviews to demonstrate the objectives associated with the reduction of logistics footprint s and operations and sustainment (operations and support) cost. These metrics will include (but not be limited to) IBCS HW/SW configuration item quantity comparison, Software Lines of Code (SLOC) comparison, number of Computer Software Configuration Items (CSCIs), user screen count comparisons, training support package comparison, and unique or single source HW/SW configuration items. 3. Best of Breed BMC4I Configuration Item Selection Processes - The IBCS contractor shall provide an acquisition approach that uses cost effective best of breed IBCS common HW/SW GFE/GFI configuration items; integrating them into incremental IBCS CP and P&F modification kits. 4. Meet IAMD Schedule Objectives The IBCS contractors development schedule shall support the top level IAMD Increment 2 Program Milestones: PDR September 2007; Critical Design Review (CDR) - May 2008; Design Readiness Review (DRR) April 2009; Miles tone C (MS C) March 2010; and IOC - September 2011. The IBCS market survey will be conducted in two phases: 1) White papers describing the technical approach submitted to the Government Contracting Officer specified below by 22 Sep 06 followed by 2) an Industry Day to be announced at a subsequent date. The Government will not reimburse respondents for any costs associated with responses to this notice or participation in any Industry Day. White papers submitted as a result of this market survey, will facilitate the IAMD Project Office in the formulation o f an Acquisition Plan and eventually a follow-on Request for Proposal (RFP) for an IBCS System Development and Demonstration (SDD) contract. More information on Industry Day will be provided at a later date to include foreign disclosure and security guidelines. Respondents may submit questions in writing to the following points of contact: Mable N. Youngblood, (256) 842-7326, Email: Mable.Yo ungblood@redstone. army.mil; Dorphelia B. Foster, (256) 876-4189, Email: dorphelia.foster@redstone.army.mil; and Stacy Potts, (256) 842-7503, Email: stacy.potts@redstone.army.mil by 22 Sep 06. Appropriate Government response to submitted questions will be provided at Industry Day. White paper responses will consist of an Unclassified white paper on 8.5 x 11 inch paper with fonts no smaller than 12 point, one inch margins, in a Microsoft Word or Adobe file format. Each page of the submission shall contain the document identifier in t he document header. Respondents should label any information contained in the white paper that is considered proprietary. At a minimum, the white paper shall provide 1) a description of the technical and programmatic approach with key risks and suggested mitigation approaches that address the IBCS statement of objectives, as well, as technical, contract and program management/cost/ schedule objectives; 2) a description of specific technical an d programmatic approaches, to include a concept for technical documentation needed, for integrating third party solutions in an open BMC4I hardware and software architecture; 3) provide a rough order of magnitude cost; 4) comments on the IBCS Statement of Objectives, as well technical, contract and program management/cost/schedule objectives; and 5) a brief description of the firms capability and experience in providing systems in this mission area and any history of integrating third party solutions in a n open BMC4I hardware and software architecture. Any contractor providing proprietary responses must be either willing to authorize disclosure of these responses to Team Innovation in Integration and all IAMD SETA contractors or make other appropriate confidentiality agreements prior to responses being considered. Current IAMD SETA contractors are BAE Systems Analytical Solutions, Inc.; Dynetics, CAS and Davidson, LLC; Tecolote, Inc.; and Westar Aerospace and Defense Group, Inc. An IAMD Program Overview Briefing packet that further outlines the program will be available at the PEO Missiles and Space web site: http://www.msl.army.mil. under the IAMD Section. The white paper will be limited to 50 total pages including tables, charts, and figures. The white paper will include a technical Point of Contact (POC), phone number and email. Two copies of the white paper are requested (one hard copy and one readable C ompact Disk (CD). All white papers must be received by the Contracting Officer at the following address: U. S. Army Aviation and Missile Command (AMCOM), Acquisition Center, AMSAM-AC-SM-C/ATTN: Mable N. Youngblood, Redstone Arsenal, AL 35898-5280 Not La ter Than (NLT) 1600 Hrs. (Central) on 22 Sep 06. Requests received in any other manner will not be honored.