MCAT-BAA_22APR11.docx

BROAD AGENCY ANNOUNCEMENT

FOR THE AIR FORCE RESEARCH LABORATORY

SPACE AND MISSILE DIVISION

PROPULSION DIRECTORATE

RESEARCH AND DEVELOPMENT

Working-Draft BROAD AGENCY ANNOUNCEMENT

BAA-11-01-PKTA

22 Apr 2011

Distribution A: Approved for public release; distribution unlimited.

Public Affairs Clearance Number 10959

TABLE OF CONTENTS:

5. Schedule ……………………………………………………………………………………………....……… 9

6. Other Requirements ………………………………………………..…..…………………………............… 9

6. Proposal Content Summary...…..…………………….…………………………

1. Technical Point of Contact…... ……………………….……………....…………

2. Contracting Points of Contact.. ……………………….…………………………

3. Ombudsman…………………………………………….…………………………

VIII. OTHER INFORMATION ………………………………………………………………………………

1. Support Contractors ………………………………………….………………………………………….…. 25

BROAD AGENCY ANNOUNCEMENT

BAA-11-01-PKTA

22 APR 2011

NAICS CODE: 541712

FEDERAL AGENCY NAME: Air Force Research Laboratory, Propulsion Directorate (AFRL/RZ-West)

BROAD AGENCY ANNOUNCEMENT TITLE: Missile Component Advanced Technologies (MCAT)

BROAD AGENCY ANNOUNCEMENT TYPE: This is the initial closed-ended Broad Agency Announcement (BAA)

BROAD AGENCY ANNOUNCEMENT (BAA) NUMBER: BAA-11-01-PKTA

BRIEF SUMMARY OF MCAT BAA: This BAA describes the development of the MCAT that is of interest to the Air Force Research Laboratory (AFRL). AFRL anticipates awarding unique and independent Indefinite Delivery/Indefinite Quantity (IDIQ), Cost-Plus-Fixed-Fee (CPFF) contracts. Aside from awarding the basic IDIQ contracts, it is the Government’s intent to simultaneously award Task Order 1.

PROPOSAL DUE DATE AND TIME: THIS IS A WORKING-DRAFT BAA. PROPOSALS ARE NOT BEING REQUESTED AT THIS TIME. Proposals for the IDIQ contract and Task Order 1 will be due by TBD and delivered to AFFTC/PKTA, Attn: Marc Venzon, 5 South Wolfe Avenue, Edwards AFB, CA 93524. Proposals received after this due date and time shall be governed by the provisions of FAR 52.215-1(c) (3). See Section IV, para. 6 for additional information. It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late”. Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Early proposal submission is encouraged.

I. PROGRAM DESCRIPTION:

The Air Force Research Laboratory (AFRL), Propulsion Directorate at Edwards AFB, CA is soliciting proposals on the following research effort:

1. Statement of Objective/Needs: The AFRL is seeking proposals in the field of large solid rocket motors (SRMs). This is the functional area that corresponds to the missions of the Propulsion Directorate (RZ), Space and Missile Division (RZS), Motor Branch (RZSB), Materials Branch (RZSM) and Propellants Branch (RZSP). This functional area is also shared by the Materials & Manufacturing Directorate (RX). The goals of the Missile Component Advanced Technologies (MCAT) program are to develop and demonstrate technologies that address the Rocket Propulsion 21 (RP21) SRM booster goals. The MCAT program also seeks technologies that will reduce our reliance on the “build-em and bust-em” approach of designing SRMs by developing modeling and simulation tools that more fully describe the physical processes that occur when a SRM operates. The MCAT program seeks to develop new propellants that address the RP21 Phase 1 SRM booster goal for specific impulse (Isp) and propellant ingredients that address the RP21 SRM Phase 2 Isp goal.

2. Scope: The MCAT program encompasses all aspects of solid rocket propulsion. SRM technologies to be developed under the MCAT include but are not limited to motor cases, internal and external case insulation, nozzles including exit cones, thrust vector control, thrust vector actuators, igniters, propellant, propellant ingredients, health management, aging and surveillance, advanced solid rocket materials, model and simulation tools and sensors. The initial orders will be placed to develop advanced component technologies that achieve the stated RP21 goals and demonstrate this achievement at technology readiness level (TRL) 5 (Task Orders 1, 2 and 3) and to further develop SRM modeling and simulation tools (Task Order 1). In order to be considered for an award of a basic IDIQ contract under the MCAT program, offerors must demonstrate the ability to perform all of the above defined scope.

2.1 MCAT goals.

2.1.1 Mass fraction. The primary goal of Task Order 1 - CLIN 0001, Task Orders 2 and 3 is to demonstrate a 20% reduction in inert mass fraction of SRM boosters compared to the baseline.

2.1.2 Transition opportunities. While AFRL is interested in technologies that will fully demonstrate the RP21 SRM booster goals, we also have a desire to transition the newly developed technologies to operational missile and/or space launch systems. To affect that result, the AFRL will give special consideration to proposals that make an earnest demonstration of transitioning newly developed technologies to an operational missile or space launch system. It is possible that a proposal demonstrating transition of the newly developed technologies but not fully meeting the stated goals to be rated ahead of a proposal that fully demonstrates (or even exceeds) the goal but makes no attempt at demonstrating transition of the technologies (see Figure 1below).

Figure 1 – Goal Achievement vs. Transition Probability

2.1.3 Specific impulse. While improvements to Isp is not a specific goal of either the component development (Task Order 3) nor the demonstrator motor (Task Order 4) tasks, it is understood that recent improvements to the industry’s model & simulation capability indicate that there may be ways to improve nozzle and grain designs in such a way as to improve the delivered Isp efficiency of an SRM. Through analysis using the latest modeling and simulation capabilities, improved delivered Isp will be demonstrated by coupling the high Isp efficiency approaches with high performance 1.3 hazard class propellants. So again, special consideration may be given to a proposal that demonstrates increased delivered Isp efficiency. The AFRL may, on future task orders, order development of new propellant and propellant ingredients that will improve the delivered Isp by 2% and 5% respectively over the baseline.

2.1.4 Cost. Although cost improvements are not a goal for the MCAT program, AFRL desires technologies that do not increase cost of SRMs. Offerors shall address how proposed technologies will impact cost. Offerors shall address both hardware cost and life-cycle costs.

2.1.5 Integrated product team. It is expected that this project will encompass multiple awards, and that awardees may subcontract for key technology developments or processes. Therefore, the Integrated Product Team (IPT) process, which involves participants from all contractors and is led by the government, will be critical to foster cohesive efficiency toward end goals. An IPT plan will be included in proposals. For example, Task Order 1, CLIN 0002, modeling & simulation will require participation in an IPT, the other tasks do not require IPT participation, but offerors are encouraged to propose this if they believe it will lead to the success of the program. IPT frequency must be clarified in proposals, with a minimum IPT frequency of once every 6 months being desired. The effort will conclude with an IPT meeting prior to final report submission. All data and assessments will be reviewed by the IPT and significant findings will be clearly documented in the interim reports and final reports.

3.0 Technical Requirements/Program Plan:

3.1 Task Order 1 Conceptual Design and Modeling & Simulation - This task order will be award at the same time as the basic IDIQ contract. There are two technical contract line item numbers (CLIN) associated with this task order. Each CLIN has a different budget and period of performance associated with it. All offerors must submit a proposal of Task Order 1 in order to be considered for an award.

3.1.1 CLIN 0001 Conceptual Design - The objective of CLIN 0001 is to develop a conceptual design of a MCAT demonstration motor which uses novel advanced technologies that will demonstrate the RP21 mass fraction goals. Development of the concept shall include plans for assessing goal achievement and prioritizing risks of achieving the goals. Programmatic planning shall include definition of the technology development efforts required to ensure the success of the demo motor proposed. The highest payoff technology development efforts identified in CLIN 0001 will form the basis for the technologies that will be developed under Task Order 0002. Offerors shall also identify the analysis and testing required for demonstration and validation towards the attainment of the mass fraction goal.

3.1.1.1 Definition of the demonstration motor shall include geometric configuration, motor performance, mass properties, propellant formulation, special tooling (mandrels, cast tooling, handling) that will be needed to be procured. The offerors shall design a motor that nominally has at least 2000 lbm of propellant. Other sizes may be proposed if it furthers the AFRL goal of transitioning the technologies developed under this program into an operational system. If a motor containing less than 2000 lbm nominal propellant weight is proposed the offeror shall demonstrate a transition path for the technologies demonstrated.

3.1.1.2 As a minimum the following needs to be considered in the design of the demo motor: technical innovation, technical approach, program risk and management of the risks. The offeror shall develop a plan that provides an approach to make significant advances towards the RP21 Phase I SRM booster mass fraction goal. The RP21 Phase I mass fraction goal is to reduce the inert mass fraction of a large SRM booster by 20% compared to the baseline.

3.1.1.3 Risk assessment is critical to success as technologies introduced to the program are expected to enter at various technology readiness levels (TRL). Identify the critical risks in the development and integration of these technologies into the propulsion system and develop the plan for key risk reduction experiments necessary to mitigate these risks. The cost and schedule required for these activities shall be identified. All proposed technologies will need to be identified with their respective TRL and an appropriate risk mitigation plan. In addition, materials utilized in the design should have a material readiness level (MRL) identified to ensure all technologies derive from sustainable materials and processes.

3.1.2 CLIN 0002 Solid Rocket Motor Modeling (SRM) and Simulation Tool Development: Sub-task 3.1.2.1 Modeling Roadmap Development is mandatory; the other sub-task areas need not be proposed to but must be addressed, i.e. negative replies are requested.

3.1.2.1 Modeling Roadmap Development – The objective of CLIN 0002 is to examine the modeling tools currently in use or in development to identify gaps and/or necessary enhancements. It shall consists of a review of current capabilities, standard codes and models, validation or historical usage of the models/codes and usability/portability. The task shall also investigate and define possible weakness in the current methods, codes and models as they pertain to rocket motor development, analysis, manufacture, and sustainment. A brief survey of industry standard codes should also be included to identify any potential leveraging. The output shall include a time phased roadmap of future work based on lessons learned from previous software development tasks. This task shall be a 6 month effort, with a report to the IPT.

3.1.2.2 Performance Model Development - The effort shall upgrade the contractor’s capability to model and develop affordable high performance motors employing new material and propellant technology and advanced designs. It is anticipated, though not required, that important areas of emphasis will include the motor internal flow environment, material response, and ballistics. Validation efforts should be included as part of the modeling tool development, either though existing databases or generating new data.

3.1.2.3 Manufacturing Model Development - The contractor shall develop or enhance computational tools needed to both predict SRM component strength and performance using available or new materials or processes. Validation efforts should be included as part of the modeling tool development, either though existing databases or generating new data. The effort shall focus on propellant, insulation, and\or case level components.

3.1.2.3 Hazards Model Development - The contractor shall develop or enhance computational tools needed to both predict SRM hazards and aid in the design and development of motors with improved hazard properties. The effort shall focus on propellant and/or motor related hazards. Validation efforts should be included as part of the modeling tool development, either though existing databases or generating new data.

3.1.2.4 Reliability Model Development - The contractor shall develop or enhance computational tools needed to both predict SRM reliability and aid in the design and development of improved reliability motors. The effort may focus on the reliability of individual motor components, and/or the entire motor. It is anticipated, but not required, that the effort would include SRM propellant aging & surveillance and/or damage modeling. Validation efforts should be included as part of the modeling tool development, either though existing databases or generating new data.

3.1.2.5 SRM Diagnostics and Associated Experimental Apparatuses - The contractor shall develop or enhance the experimental methods needed to support achievement of the TSSS II program goals. Examples of diagnostics and associated experimental apparatuses may include, but are not limited to, those used to gather data to support the development of computational models, those diagnostics used to aid in the validation of computational models, and embedded and non-embedded sensors for aging & surveillance. Elements of this task may be linked to the computational modeling efforts in CLIN 0002.

3.2 Task Order 2 Missile Component Development - this task order is to develop inert components of solid rocket motors. The goal is to reduce the inert mass fraction of a solid rocket booster motor by 20% over the baseline. Offerors may propose improvements to any of the inert motor components such as the motor case, internal insulation, propellant liner, nozzle including exit cone, thrust vector control and thrust vector actuators. The supplemental data package referenced in Section III, para. 2 contains the government objectives for each component. Offerors are not required to meet the individual component objectives so long as they demonstrate that the total inert mass fraction is reduced by 20%.

3.2.1 The objective of this task is to develop those technologies identified by the offeror in Task Order 1 as having the highest payoff, highest technical risks and/or longest development schedule considering the Task Order 3 schedule. Proposals for this task order will be solicited at the time the final reports are submitted for Task Order 1, CLIN 0001. Award of this task order will be contingent on the Government’s satisfactory evaluation of technical and cost performance Task Order 1, CLIN 0001 in addition to the quality and relevance of the proposal submitted for this task order.

3.2.2 Testing required shall be identified and performed. The offeror may propose to use government facilities to perform these tests, but all test costs must be paid out of the budget identified for this task order.

3.3 Task Order 3 Rocket Propulsion 21 Demonstrator Motor - this task is to design, fabricate and test the motor that was defined in Task Order 1 - CLIN 0001. Offerors are expected to refine the designs from Task Order 1, CLIN 0001 on the basis of information learned from Task Orders 1 and 2 as well as any IR&D. Award of this task order will be contingent on the Government’s satisfactory evaluation of technical and cost performance of Task Order 0002 in addition to the quality and relevance of the proposal submitted for this task order.

3.3.1 Motor specifications. The motor designed in this task shall nominally contain 2000 lbm of propellant. Motors smaller than 2000 lbm may be proposed provided that doing so furthers the opportunity to transition technologies demonstrated in this task. For instance if the offer has identified a customer with a specific need for the motor proposed and the offeror can demonstrate that the technologies are to be transitioned upon successful demonstration, then the government may accept a smaller motor.

3.3.2 Component development. Further development of the technologies identified in Task Order 1 may be performed prior to fabricating components for the demonstration motor as necessary to reduce the technical risk.

3.3.3 Testing required shall be identified and performed. The offeror may propose to use government facilities to perform these tests, but all test costs must be paid out of the budget identified for this task order.

3.4 Future Requirements - As one of the AFRL missions is to develop innovative technologies for solid rocket boosters we expect to have requirements for technology development beyond what is spelled out in the above task orders. Technologies to be developed might be additional embodiments of the technologies from Task Orders 1 thru 3 as well as those related to propellant, propellant ingredients, health management, aging and surveillance, advanced solid rocket materials, model and simulation tools and sensors required to meet RP21 SRM booster goals.

4. Deliverable Items: Any contract awarded as a result of this BAA shall be required to deliver appropriate data items and residual hardware.

4.1 Data Requirements: All program technical and financial progress shall be reported. A sample Contract Data Requirements List (CDRL), Table 1 is provided. The items below or similar items shall be incorporated into each contract award as applicable. Applicable CDRL items shall then be incorporated into Task Orders. The Data Item Descriptions (DID) are given as references only. All reports are to be divided into sections marked as proprietary and non-proprietary information, if applicable. The Government would prefer unlimited data rights for all technology that is developed and/or modified on this effort; other rights may be negotiated as appropriate and must identify these as part of offerors terms and conditions. Appropriateness of data rights proposed by the offeror is an evaluation criterion. Offerors are encouraged to propose alternates to the items shown below for consideration and approval. Contractor’s format and report consolidation are highly encouraged and will be acceptable upon approval. Alternate or additional data items that would streamline or enhance the effectiveness of the effort are solicited. Proposals must show a list of CDRL items included in the price of the proposal. Electronic submission of data items will be required on individual Task Orders. Once posted, the model contract will contain Exhibits A and B for complete requirements.

Table 1 - Sample Contract Data Requirements List (CDRL)

Applicability Frequency

*Notes

(1) These CDRLs are not required for Task Order 1, CLIN 0001

(2) CDRL A014 is required only if an interim hazard classification will be required for any explosives developed or manufactured during the course of this contract

(3) CDRL A015 is required only if an interim hazard classification will be required for tasks where testing will be performed at a government facility

(4) Interim reports will be submitted at the mid-point for any task that is between 24 and 35 months in duration and annually for any task greater than 35 months in duration

4.2 Residual Hardware: Hardware deliveries may be required. If applicable, desired residual hardware will be identified on individual task orders and delivered to AFRL/RZSB upon the completion of the technical effort.

5. Schedule: The anticipated period of performance for Task Orders 1, 2, and 3 is -

5.1 Task Order 1, CLIN 0001: Four (4) months Technical Effort, plus three (3) months for the Final Scientific and Technical Reporting Cycle.

5.2 Task Order 1, CLIN 0002: 51 months Technical Effort, plus three (3) months for the Final Scientific and Technical Reporting Cycle.

5.3 Task Order 2: 45 months Technical Effort, plus three (3) months for the Final Scientific and Technical Reporting Cycle.

5.4 Task Order 3: 45 months Technical Effort, plus three (3) months for the Final Scientific and Technical Reporting Cycle.

6.0 Other Requirements:

6.1 Classified Material: The use of classified material is not anticipated at this time. However, if an offeror proposes to use or generate classified material, the contracting office shall be contacted for further guidance.

6.2 International Traffic in Arms Regulations (ITAR) (export control): ITAR will apply to this effort. All technical data generated or delivered under any contract resulting from this BAA is controlled by the International Traffic in Arms Regulation (ITAR), 22 CFR Sections 121 through 128, and will require the following distribution statement:

“This document contains technical data whose export is restricted by the ARMS EXPORT CONTROL ACT (Title 22, USC, Sec 2751 et seq) or the EXPORT ADMINISTRATION ACT of 1979, as amended, Title 50, USC, APP 2401 et seq. Violations of these export laws are subject to severe criminal penalties.”

6.2.1 All data generated or delivered will also require one of the following two statements depending on the content of the information:

“Distribution Statement B – Distribution authorized to U.S. Government agencies, Only (Critical Technology) (Contract Award Date). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr., Edwards AFB CA 93524-7048.”

OR

“Distribution Statement C – Distribution authorized to U.S. Government agencies and their contractors (Critical Technology) (Contract Award Date). Other requests for this document shall be referred to AFRL/RZS, 5 Pollux Dr., Edwards AFB CA 93524-7048.”

AND

Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of this document.

6.3 Certifications: Potential offerors are notified that effective 01 Jan 2005 to be eligible for an award; they must submit annual Electronic Representations and Certifications, otherwise known as On-line Representations and Certifications Application (ORCA) via the Business Partner Network (BPN) at http://www.bpn.gov/orca. These FAR level representations and certifications are required in addition to the representations and certifications specific to this acquisition. Before submitting the Electronic Representations and Certifications, contractors must be registered in the Central Contractor Registration (CCR) Database. On-line registration instructions can be accessed from the DISA CCR home page at http://www.ccr.gov.

6.4 Hazardous Materials: The handling of Hazardous Materials may apply to this effort. DFARS clause 252.223-7001 may apply to this program.

6.5 Ozone Depleting Substances: None.

6.6 Radioactive Materials: None.

6.7 Safety: The use of Ammunitions and Explosives may apply to this effort. DFARS clauses 252.223-7002 and 252.223-7003 may apply to this program.

6.8 Accounting System: In accordance with FAR 16.301-3 a contractor must have an adequate accounting system in place that can support a Government cost-reimbursement type contract.

6.9 Advanced Rocket Propulsion Plan: Although it is not mandatory, we highly recommend that offerors have an approved Advanced Rocket Propulsion Plan under the Integrated High Payoff Rocket Propulsion Technology program.

7.0 Other Information:

7.1 Joint Army Navy NASA Air Force (JANNAF): Offerors shall include a plan for participation in the JANNAF conferences, subcommittee meetings and periodic workshops in order to present current results. This participation will serve as a mechanism to report current progress to the community. JANNAF participation will be defined by the CDRL in each specific task where such participation is deemed necessary for that particular effort.

7.2 Government Furnished Property (GFP): It is possible that GFP may be involved or used in this effort; however, if GFP is required, it must be identified in the initial proposal and in the final awarded contract. If proposing Government Furnished Property (GFP), identify the source and location of the property, who owns it (include point of contact with phone number), the value of the property, approval from the property owner and how, when and for how long it will be made available under the proposed effort. Address commonality with other programs. If contributions from other efforts are proposed, identify the specific efforts, the planned start and end dates, and the applicability to the current BAA and IHPRPT. In addition, ensure all efforts are included on the proposed Task Order schedule.

7.3 Contractor Acquired Property: None.

7.4 Subcontracting Plans: Small Business Subcontracting Plans are required under FAR 19.702 for efforts anticipated to exceed $650,000. Prospective offerors shall submit applicable subcontracting plans in accordance with the requirements set forth in FAR 19.704 and DFARS 219.704 along with the technical and cost proposals. Small businesses are exempt from this requirement. If a company has a master subcontracting plan, as described in FAR 19.701 or a comprehensive subcontracting plan, as described in DFARS 219.702, a copy of the plan shall be submitted with the proposal. The subcontracting plan is a part of the business proposal and will not be included in the page count.

II. AWARD INFORMATION:

1. Anticipated Funding: The nominal funding and schedule for each task order is defined in the individual task orders. The total funding available for Task Orders 0001 thru 0003 is $15,043K. The total funding is over six Government Fiscal Years. Funding breakout is as follows:

1.1 Funding Profile, Task Order 1, CLIN 0001: The budget for CLIN 0001 is $250K, all in FY12.

1.2 Funding Profile, Task Order 1, CLIN 0002: The budget for CLIN 0002 is $2,065.5K.

1.3 Funding Profile, Task Order 2: The budget for Task Order 2 is $3,648K.

1.4 Funding Profile, Task Order 3: The budget for Task Order 3 is $9,079.5K.

2. Type of Contracts/Instruments: The Government reserves the right to award the contract type/instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the Federal Acquisition Regulation. AFRL anticipates unique and independent Indefinite Quantity/Indefinite Delivery (IDIQ), Cost-Plus-Fixed-Fee (CPFF) contract. The anticipated total minimum quantity of supplies or services is $250K. The anticipated total maximum quantity of supplies or services is $30M. The anticipated ordering period is 60 months from the IDIQ contract award date.

3. Anticipated Number of Awards: The Government anticipates to award two unique and independent IDIQ CPFF contracts.

4. Discussions: Proposals are intended to be evaluated, and award made without discussions, unless discussions are determined to be necessary. However, the Government may obtain clarifications to determine proposal acceptability. Discussions may be held with prospective awardees prior to award if needed. In the event the Government is unable to conclude negotiations with the apparent successful offeror(s), it reserves the right to conduct negotiations with another acceptable offeror.

5. Anticipated Award Date: The basic IDIQ contract is anticipated to be awarded on 30 Sep 2011.

5.1 Task Order 1 is anticipated to be awarded simultaneously with the basic IDIQ contract on 30 Sep 2011.

5.2 Task Order 2 is anticipated to be awarded on 30 Sep 2012.

5.3 Task Order 3 is anticipated to be awarded on 30 Sep 2013.

III. ELIGIBILITY INFORMATION:

1. Eligible Offeror/Applicants: Foreign or foreign-owned firms are precluded from proposing. All correspondence must reference the title and BAA number.

2. Access to Restricted Technical Information: A supplemental informational package describing the specifics of the RP21 goals and baseline is available to potential offerors who are authorized to receive restricted technical information. Any required restricted technical information is available to qualified offerors and will be provided upon request from the CPOC. Only US Contractors who are registered and certified with the Defense Logistics Services Center (DLSC), Federal Center, Battle Creek, MI, 49017-3084 (1-800-352-3572) and have a legitimate business purpose may have access to this information. If you are registered with the DLSC, you must submit a copy of the approved DD Form 2345, Military Critical Technical Data Agreement, with your request for the data.

IV. PROPOSAL APPLICATION AND SUBMISSION INFORMATION:

1. General Instructions: All offerors must comply with all provisions of FAR 52.215-1 (Jan 2004) “Instructions to Offerors – Competitive Acquisitions.” Proposals should be marked in accordance with FAR 52.215-1(e). A copy of this provision is available from http://farsite.hill.af.mil. Properly marked proprietary information will be treated in accordance with DFARS 252.227-706. Proposals must reference the BAA announcement number. Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

1.1 IDIQ Processes: It is inherent in all solicitations resulting in IDIQ contracts, that there are two (2) distinct processes that deal with proposal development, evaluation, and selection for award. The first results in the award of the IDIQ contract. The second, which follows contracts award, results in the award of a Task Order.

1.2 Proposals: Offerors must state, on the cover page of their business/cost proposal, that their proposals will be valid for 180 days from submission. Proposals submitted shall be in accordance with this announcement. To award the IDIQ contract, the Government intends to evaluate the overall proposal including Task Order 1, and demonstration and verification of the ability to successfully accomplish Task Orders 2 and 3. The offeror(s) must propose to each of the requirements listed Section I, para. 3.0. The Government will evaluate the detailed proposals including cost and pricing data for Task Order 1, and will subsequently award all, some, none, or part of the proposals received without negotiation/discussion; however, the Government reserves the right to negotiate with those offeror(s) whose proposal is selected for funding.

1.3 Amendments: Offerors should be alert for any BAA amendments that may permit extension to the proposal submission date. Any additional information will be posted on the Government Point of Enter (i.e. the Federal Business Opportunities website, http://www.fbo.gov).

1.4 A copy of the Broad Agency Announcement (BAA) Guide for Industry is available at http://www.wpafb.af.mil/library/factsheets/factsheet.asp?id=6790.

2. Content and Form of Submission for Full Proposals: Offerors must submit one-original, five hard copies, and five electronic (CD) of their proposals to the contracting office. Proposals are to be divided in three volumes: (1) IDIQ Volume 1 consisting of written technical/management information for Task Orders 1, 2, and 3; (2) IDIQ Volume 2 consisting of the Oral Presentation for all task orders; (3) IDIQ Volume 3 consisting of business/price section of Task Order 1 and Rough Order of Magnitude estimates for Task Orders 2 and 3. A detailed written technical proposal volume is not required. The oral presentation will take the place of a written technical volume. In lieu of a written technical proposal, it is required that the technical details for Task Order 1, along with the demonstration of the capability to perform Task Order 2 and 3 are conveyed during the oral presentation. The Government will check the proposal for conformation to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered.

3. IDIQ Volume 1 Technical/Management Proposal. The Technical/Management proposal shall be limited to 40 pages, prepared and submitted in Microsoft Word format. Font shall be standard 12-point business font Arial. Character spacing must be “normal,” not condensed in any manner. Pages shall be double-spaced, single-sided, 8.5-in by 11-in, with at least one-inch margins on all sides. Lines between text lines must also by 12-point. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line space requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including length narrative in such items. Pages shall be numbered starting with the cover page being Page 1, and the last page being Page 40. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5-in by 11-in portion) tables, charts, etc. A CD with the Microsoft Word version of your Technical/Management Proposal must be submitted with the hard copies of the proposal and must match the hard copy. This volume will summarize the technical skills and managements structure to be used for Task Orders 1, 2 and 3. It will include items in Section IV, para. 3.1 – 3.11

3.1 Statement of Problem: Importance of the program based on current business planning, current vision of future capabilities, and perceived customer (Government or commercial) needs.

3.2 Program Plan and Schedule: Provide proposed Program Plan with program schedule and requirements list for Task Orders 1, 2, and 3. For Task Orders 2, and 3 provide the Program Plan with the technologies and demo motor to be pursued. Also, the program schedule must show the capability of completing these tasks has been considered and is feasible. Finally for Task Orders 2 and 3, demonstrate the agreement between the program work-scope and timelines to complete component development and fabrication, and timelines for the demonstration motor fabrication and test. The schedule for all tasks represents the offeror’s commitment to perform the program tasks in a logical and timely manner. Include charts depicting timelines. Each major task identified in the SOW should appear as a separate line on the program schedule, including milestones and decision gates. All decision points (gates), planned meetings, such as kick-off, presentations (including final), Technical Interchange Meetings, Integrated Product Team meetings (Task Order 1, CLIN 0002 only), Design Reviews, etc., must be included in the schedule.

3.3 Contract and Sub-contract Management: Identify how the contract and subcontracts will be managed in terms of progress feedback, communication, written summaries, funding distribution and tracking. Describe subcontractor and consultant agreements that are to support this contract. Describe the process for notification and approval of changes to key team members by AFRL. Clearly describe firm’s organizational chain of command and systems to track and manage: payroll, labor hours, invoicing, technical/programmatic problems, and leveragability. Example information may be provided, but is not required.

3.4 Program Risk Plan: Describe the approach for identifying and mitigating program risks . Also describe how risk will be managed between the offeror and subcontractors for critical components and small/large scale tests throughout the effort. Clearly define the nature of each risk and how it impacts potential work and/or resulting technology. Risks to be considered are technical, programmatic, availability of materials, foreign suppliers/information,. Identify what processes will be used to reduce or eliminate the impact of each identified risk. Describe standards of practice for risk identification and mitigation.

3.5 Staffing: For Task Orders 1, 2, and 3, provide the staffing plan with the personnel’s current and projected capabilities for the proposed contracted effort. Identify key personnel, a description of their technical and/or management role, which key personnel would oversee program tasks and their relationship to the company (i.e., employee/title, consultant, corporate officer, subcontractor, etc.). Describe the work structure between contributors in terms of working groups, periodic technical discussion meetings, programmatic meeting, and mentoring of key personnel without extensive experience in their contribution area. The staffing plan must be definitive enough to provide the Government a clear understanding of how the offeror intends to staff the program to perform work in a timely manner with cutting edge technologies. Provide full resumes of key personnel in Appendix 2 (below).

3.6 Data Items, Contract Data Requirements List (CDRL): Proposals must show a list of priced CDRL items. The CDRL items are found in the statement of objectives. Offerors are encouraged to propose alternates or additions to the standard items that would streamline and/or enhance the effective progression of the effort. The proposed alternates or additions would then be discussed for consideration and approval by the government. Offerors are encouraged to propose alternate data items that are standard in-house reports that convey the progression and completion of the program. If an alternate data item is proposed, a description of the item, including how it is generated and the frequency, is required. This description for an alternate data item must show that the alternate will meet the documentation requirements of the listed CDRL. A sample document may be included.

3.7 Past /Present Performance Data. Each proposal must include information on each contract that the offeror considers relevant in demonstrating the ability to perform the proposed effort. Guidelines for summarizing past/present performance are given in Appendix 5, below.

3.8 IPT and External Interfaces: IPT meetings are not required for Task Order 1, CLIN 0001. In person IPT meetings are required at a minimum interval of every 6 months for Task Order 1, CLIN 0002. Verify proposed IPT meeting participation for Task Order 1, CLIN 0002; clearly state proposed in person and telecom meeting intervals. A discussion of IPT meeting participation for Task Orders 2 and 3 is not required in response to this BAA, and will be addressed in Task Order 2 and 3 proposals. Clearly identify your plan to manage your integration into the proposed IPT for this contract and to integrate technologies with other awarded contractors. This plan should include, but not be limited to, proprietary information and data control, non-proprietary data and information transfers.

3.9 Business Plan: Identify leveraging of current and future capabilities and programs with applicability of technologies to impact future advancement of M&S and inert SRM component technologies. State how this contract effort will benefit offeror’s future programs and capabilities. Give an overview that describes the approach to management of the proposed effort, use of personnel and subcontractors including small businesses, and consultant relationships. Describe government interfaces; control practices; and external interfaces such as the IPT. This section may very briefly summarize portions of the preceding sections to provide a complete overview of the plan.

3.10 Use of AFRL Facilities: If AFRL is the proposed test facility for the Task Order 3 Demonstration Motor firing, it must be clearly identified including the role of the offeror’s liaison to AFRL, any form of communication or assistance that would be requested of AFRL, and the offeror’s responsibilities/liabilities for the firing.

3.11 Appendices. The appendices will have separate page limits. Appendix 1 - Statement of Work shall have no page limits. Appendix 2 - Resumes shall be limited to 2 pages per individual. Appendix 3 - Basis of Estimates have no page limits. Appendix 4 - Past/Present Performance Data shall be limited to 10 pages. Appendix 5 - Compliance Matrix.

3.11.1 Appendix 1: Statement of Work. Provide a Statement of Work (SOW) for Task Order 1. This SOW must contain a summary description of the technical methodology as well as the task descriptions. Offerors are cautioned to include only the information which is essential to a clear, concise, and binding SOW. This document will be made part of any resulting contract. Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced in Section IV, para. 1.4 to assist in SOW preparation.

3.11.2 Appendix 2: Resumes. Full resumes of all key personnel that are anticipated to participate in any or all of Task Orders 1 – 3 must be included. Include the resumes of only key personnel to be involved in this effort for the prime contractor, key subcontractors, and consultant personnel with percentage of time that will be allocated to the entire proposed program and relevant past work experience.

3.11.3 Appendix 3: Basis of Estimates (BOE). Offerors shall submit a BOE supporting the proposed hours, subcontracts, materiel, and other direct costs by WBS/Major Task, Subtask (level 3) for Task Order 1. The BOE shall convey a clear understanding of how the labor and materials were estimated for each task in the SOW. The BOE for labor and subcontracts shall include sufficient detail to identify: what work is being performed, why the offeror believes the proposed person-loading is sufficient, and that the labor mix is appropriate for each task of the PWS. Where it is applicable historical data for similar tasks shall be identified along with any judgment factors that were applied. The applicability of the historical data shall be explained, and all factors shall be defined and justified. Do not reflect dollar amounts in the BOE.

3.11.4 Appendix 4: Past/Present Performance Data. Relevant past/present performance data will aid in the demonstration of capabilities. Provide information on completed or ongoing contracts that the offeror considers relevant in demonstrating the ability to perform the proposed effort. This information should cover work performed by other divisions, critical subcontractors, or teaming contractors only if such resources will be brought to bear on or significantly influence the performance of the proposed effort. The offeror should outline recent applicable efforts with sufficient detail to accurately analyze the approach. Each description of past/present performance data should include:

3.11.4.1 Program Title

3.11.4.2 Type of Contract

3.11.4.3 A brief description of the contract effort, indicating whether it was basic research, development, or production; briefly describe the relevance to the proposed effort and how the project and associated customer relationships can be applied to support the proposed program; and address major risks and challenges associated with the cited effort.

3.11.4.4 Company/Division Name, Subcontract Name(s), valid points of contact, addresses, phone numbers, and titles for these programs. Each reference shall include contracting agency, a valid contracting and technical point of contact, including contract number.

3.11.4.5 Period of Performance, with the original completion date and final (or current) completion date; indicate whether or not it was or is on schedule.

3.11.4.6 Original and final (or current) contract dollar value(s), indicating any over-run or under-run.

3.11.4.7 Original and final (or current) completion date, indicating any over-run or under-run.

3.11.4.8 Name, address, and phone number of Government program manager for federally funded programs.

3.11.4.9 Describe project’s relevance to IHPRPT and/or TSSS metrics.

3.11.5 Appendix 5: Compliance Matrix. The compliance matrix shown in Table 2 shall be included as an appendix to track the fulfillment of the evaluation criteria for this BAA.

Table 2 - Compliance Matrix

1b. Description of how the proposed program addresses the statement of need.

1c. Description of how the proposed program addresses the Rocket Propulsion 21 goals (as stated in the SOO).

2. Sound Technical Approach

2a. Identification of a logical and viable technical approach to meet the SOO.

2b. Clear identification of the technology to be worked and a logical path for development to a final product, including technology entrance and exit criteria.

2c. Process for validation and verification of program results, including assessment of errors and overall goal achievement.

2d. Strong technical innovation with well-considered approach(es) to maximize probability of success.