BAA-RQR-2017-0002_ART_BAA_Call_2_A1.docx

BROAD AGENCY ANNOUNCEMENT

FOR THE AIR FORCE RESEARCH LABORATORY

ROCKET PROPULSION DIVISION

AEROSPACE SYSTEMS DIRECTORATE

RESEARCH AND DEVELOPMENT

BROAD AGENCY ANNOUNCEMENT

BAA-RQR-2017-0002

Call 2 (Amended)

1 December 20164 January 2017

Proposal Due Date: 30 January 2017

Issuing Office: Air Force Test Center, Directorate of Contracting Edwards AFB, CA

TABLE OF CONTENTS:

Distribution A: Approved for public release; distribution unlimited.

Public Affairs Clearance Number 16239

BROAD AGENCY ANNOUNCEMENT

CALL 2

BAA-RQR-2017-0001

CALL 2 DESCRIPTION

IDIQ Contract on Solid Boost Technology:

Technology Objectives: The Solid Boost Technology (SBT) effort focuses on the design, development, and demonstration of solid propulsion technologies in support of the RP21 solid boost and orbit transfer (SBOT) specific impulse and mass fraction goals; an advanced air-launched booster (AALB) for long range strike capability; and future solid propulsion (strategic, missile defense, and tactical). Call 2 addresses BAA I-1.1.1, 1.1.2, and 1.1.3 technology needs.

Supplemental Packages: A supplemental information package is available to potential offerors who are authorized to receive restricted technical information. This package includes the specifics of the RP21 SBOT goals and government baseline as well as the AALB requirements. See BAA III-5 about how to request the Call 2 supplemental package.

Scope: Call 2 encompasses all aspects of solid rocket propulsion including but not limited to high performance composite and metallic motor cases, internal and external insulation, nozzle throats and exit cones, thrust vector control and actuators, igniters, energetic propellants and ingredients, energy and impulse management, and modeling and simulation (M&S). BAA Call 2 involves the design, development, and demonstration of solid rocket technologies; characterization of those technologies in representative environments; M&S to fully describe the physics of solid rocket motor (SRM) operation including the effects of manufacturing; and validation of solid rocket technologies and M&S tools.

IDIQ Contract: Due to the wide range of SRM technology areas of interest, AFRL anticipates awarding unique and independent Indefinite Delivery/Indefinite Quantity (IDIQ), Cost-Plus-Fixed-Fee (CPFF) contracts with a Firm-Fixed-Price (FFP) CLIN for the final report of each task order. In order to be considered for an award of a basic IDIQ contract under the ART Call 2 program, offerors must demonstrate the ability to perform all of the activities defined in the Call 2 Scope (I-1.3) to meet the Call 2 Technology Objectives (I-1.1). The anticipated total minimum quantity of supplies or services is $100K.

IDIQ Technology Development Areas: The IDIQ contract will consist of technology development areas (TDAs) based on the scope identified in I-1.3. Under the IDIQ contract, projects will be requested under these technology development areas.

TDA1 Solid Rocket Motor M&S: The projects under this TDA are to develop M&S tools to reduce predictive uncertainty in design and analysis of SRMs over current State-of-the-Art (SOTA) methods. This TDA includes development of physicochemical models, coding and software, and unit level/subscale validation experiments.

TDA2 Air-Launched Booster: The projects under this TDA are to continue development of large air-launched booster technologies for SRM-boosted strike weapons. This TDA includes refinement of air-launched booster designs as well as testing at anticipated operating environments.

TDA3 Inert Components: Projects under this TDA are to develop advanced inert components for solid rocket motors. Improvements will be sought for components such as the motor case, internal insulation, nozzle, thrust vector control and thrust vector actuators.

TDA4 Energetic Components: Projects under this TDA are to develop solid propellants for tactical and strategic motors as well as other energetic components (safe/arm, igniters, flight termination systems, destruct charges). Propellants, ingredients, and other energetic components will be developed to a sufficient maturity level in support of large scale demonstration motors and hazards testing.

TDA5 Tactical Solid Rocket Motors: Projects under this TDA shall be directed towards developing motor designs for a volumetrically efficient missile for air dominance and/or self-defense. Component technologies shall be developed and demonstrated individually as well as in integrated component demonstrations at increasing levels of complexity.

TDA6 Strategic Propulsion Component Integration: Projects under this TDA shall be directed toward integration and testing of strategic solid rocket components developed under other TDAs. Component technologies shall be integrated demonstrations at increasing levels of complexity.

Initial SBT projects: In addition to the basic IDIQ contract, two project proposals are requested for TDA1 Solid Rocket Motor M&S and TDA2 Air-Launched Booster. These project proposal requests are described in I-5 and I-6 of this call.

IDIQ Capability Requirements: Candidates shall meet all of the following requirements and the proposal shall contain a description, including historical evidence, of the capability to perform these requirements.

Contractor shall be able to design, develop, and demonstrate solid rocket motor technology. This includes the ability to incorporate emerging technology to increase performance over state-of-the-art SRMs.

Contractor shall have an organic capability to manufacture full-scale flight weight SRMs for strategic, space-launch, and tactical applications. For demonstration purposes at AFRL, this capability, as a minimum, is SRMs containing at least 2000 lbm of propellant and motor diameters in excess of 30-inches.

Contractor shall be able to develop and apply advanced M&S to SRM manufacturing, design, and test analysis. This M&S ability includes incorporation of emerging SRM technology beyond state-of-the-art.

Contractor shall be able to design and test full-scale SRM components in simulated relevant environments. This includes characterization of inert and energetic components identified in the Call 2 Scope (I-1.3).

Contractor has demonstrated the ability to transition technology development programs to strategic and tactical applications. This includes both hardware as well as software (e.g. M&S) development.

Contractor has successfully applied risk management processes in SRM development programs.

Contractor effectively uses solid rocket community forums such as JANNAF meetings and integrated product teams to disseminate program progress and results.

Deliverable Items:

Any TDA project awards resulting from this Call shall be required to deliver appropriate data items and possibly software and hardware.

Data Requirements:

ALL program technical and financial progress shall be reported. The Contract Data Requirements List (CDRL) list is provided in Table 1. The Data Item Descriptions (DID) are given as references only. If less than unlimited data is included in any reports it shall be provided in a separate section. Details of each CDRL are provided in the model contract in a DD Form 1423-1.

Table 1: Sample Contract Data Requirements List (CDRL)

The items in Table 1 shall be incorporated into the IDIQ contract. Specific TDA projects shall utilize the Table 1 CDRLs tailored to specific project requirements.

Alternate or additional data items that would streamline or enhance the effectiveness of the effort are solicited. Proposals shall show a list of CDRL items included in the price of the proposal. Electronic submission of data items shall be required on all efforts. The model contract will contain Exhibits A and B for complete requirements.

Interim Report: Interim Reports shall be submitted annually, due every 12 months to the day from the beginning of the technical effort. An interim report is required for the last portion of the technical period of performance if less than or equal to 12 months since the previous interim report. In addition to the guidelines for an interim report provided by DI-MISC-80711A/T, all interim reports shall include the following:

If no progress is made under a specific WBS element, the contractor shall state current status of the task and that no progress was made for the current reporting period. For each WBS task in progress, a detailed description of the work completed during the reporting period shall be provided. For each WBS task that has been completed, a summary of activities completed with conclusions shall be provided including the date of task completion.

Interim reports shall be of the quality and completeness required for the final report. AFRL intends to publish the interim reports to DTIC.

I-1.1.1.1.1. The Interim Report that is required for the last portion of the technical POP shall be cumulative of all work to date.

I-1.1.2. Monthly Reports: A monthly report shall be submitted from contract award until the end of the technical period of performance. In addition to the general guidelines for a monthly report provided by DI-MGM-80227, all monthly reports shall include the following:

I-1.1.2.1. Sections shall be included down to three levels for each WBS element in each monthly report. Each section title shall include the WBS number.

I-1.1.2.2. If no progress is made under a specific WBS element, the contractor shall state current status of the task and that no progress was made for the current reporting period. For each WBS task in progress, a detailed description of the work completed during the reporting period shall be provided. For each WBS task that has been completed, a summary of activities completed shall be provided including the date of task completion.

I-1.1.2.3. The monthly reports shall be of the quality and completeness required for the final report.

JANNAF Papers and Presentations: In addition to JANNAF participation as specified in I-4.1, a minimum of one paper and presentation shall be submitted to AFRL in accordance to CDRL A007 at the end of each IDIQ project summarizing the efforts performed under the project.

Schedule:

The IDIQ ordering period will be limited to 60 months starting from date of award.

Other Information:

Contractor-Acquired Property: Property acquired or fabricated under this contract and with contract funds shall be considered government property. Delivery of residual contractor-acquired property will be required. Delivery is due thirty days after end of technical effort of each contract if residual hardware is developed. The proposal shall include the cost of packaging and shipping of assets to AFRL at Edwards AFB.

All proposals shall ensure proper disposal of energetic material, including accounting for cost of disposal if proposed.

Software: All projects that stipulate computer code as a deliverable shall deliver the source and compiled code within thirty days after end of technical effort. All efforts that contain deliverable software shall meet the following requirements:

Develop a sustainable code following modern software development practices such as version control; modular code; source code documentation; theory, developer, and user manuals; administrator guide; graphical user interfaces (as required); regression suites; verification; and validation.

Be capable of satisfactorily completing functional user testing by AFRL to include installation and operation on current DoD standard desktop configuration client or DoD server core configuration connected to AFRL’s SATURN enclave.

Be developed and tested on separate Security Technical Implementation Guides (STIG) compliant and documented computers (http://iase.disa.mil/stigs/) Have no CAT I or II finding of applicable STIG Minimize CAT III finding of applicable STIGs. Recommendation for risk acceptance of any open items and the reasoning shall be documented.

When developing individual technology requirements (I-1.10) take into account information assurance controls from NIST SP 800-53 and SP 800-37 (http://csrc.nist.gov/publications/PubsSPs.html) Joint Army Navy NASA Air Force (JANNAF): Offerors shall 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. The presentations and papers will be submitted as part of CDRL A007.

Government Furnished Property or Information (GFP or GFI): It is possible that GFP or GFI may be involved or used in this effort; however, if it is required, it shall be identified in the proposal for each effort in Appendix C5 (III-1.5.9.15). If proposing GFP or GFI, appendix C5 shall identify the source and location of the item or information; 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 call. AFRL does not intend to provide GFP or GFI for this effort.

Base support: The offeror may propose to use government facilities to perform component and/or motor testing, but all test costs must be paid out of the budget identified for this task order. If the offeror proposes to use a government test facility then the offeror shall include in the proposal documentation from said facility stating: (a) the facility is capable of performing the required test (b) the facility is available during the required test period and (c) a detailed estimate of the costs associated with using the facility. Note that the costs associated with testing at a government facility will be paid out of the same budget used to fund contracts awarded under Call 2; i.e. if a government facility is used, the amount of money available for contract award will be reduced by the amount required for using the government facility.

Telecons / Status Reporting: Telecons shall be held weekly unless a different time interval is agreed upon between the government program manager and contractor. The telecon packages shall consist of a slide set that shall include: A technical review, programmatic review with schedule, and financial status.

SRM M&S Project: Gap Analysis, Material Response, Mix and Cast, and Validation This project falls under TDA1 – SRM M&S and will be awarded at the same time as the basic IDIQ contract. The project is to develop tools to reduce predictive uncertainty of SRM designs to no more than +/-2% for propellant mass fraction (Mf) and no more than +/-0.5% for delivered specific impulse (Ispd) when used in conjunction with previously developed M&S tools. The M&S Integrated Product Team (IPT) Support and Modeling Gap Analysis efforts are mandatory; other efforts need not be proposed to but must be addressed, i.e. negative replies are requested.

I-1.1.3. M&S IPT Support: The objective of this effort is to support participation in the M&S IPT led by AFRL. All offerors awarded projects under TDA1 are required to participate in the IPT. In addition to AFRL and all organizations awarded under TDA1, participants in the IPT will consist of representatives from academia, other government entities with an interest in this technology, Federally Funded Research and Development Centers (FFRDC), and other qualified commercial and non-commercial entities. The IPT will meet as necessary but at least once per quarter alternating between Edwards AFB and remote meetings (via teleconference, video conferencing, Defense Collaboration Services [DCS], or other technical means). The nature of the IPT meetings is variable; some IPT meetings are expected to be highly detailed technical briefings, while others are anticipated to be focused on coordinating activities between the Government and each offeror with few formal presentations. Offerors shall share information at the IPT meetings to the greatest extent possible including but not limited to modeling approaches, code development, model verification, validation testing, and model credibility. All data and assessments shall be reviewed by the IPT, and IPT findings shall be clearly documented in the interim and final reports. This effort shall be no less than the cumulative duration of all proposed M&S efforts under this project.

I-1.1.4. Modeling Gap Analysis: The objective of this effort is to examine the modeling tools currently in use or in development to identify gaps and/or necessary enhancements. It shall consist of a review of current capabilities, standard codes and models, validation or historical usage of the models/codes and usability/portability. The effort shall also investigate and define possible weaknesses in the current methods, codes and models as they pertain to rocket motor development, analysis, manufacture, and sustainment. A time phased roadmap of future work based on lessons learned from previous software development tasks, such as the Solid Rocket Motor Modeling and Simulation Program, Advanced Missile Propulsion Technology Program, and the Missile Component Advanced Technology Program, shall be developed. A roll-up of M&S SRM predictive uncertainty for Mf and Ispd shall be provided as part of the gap analysis including potential uncertainty reductions from the identified future work roadmap. This effort shall be no more than a 4 month effort and include a final briefing to the M&S IPT.

I-1.1.5. Material Response Models: The objective of this effort is to develop physics-based material response models (MRMs) of SRM ablative materials such as thermal insulators. The MRMs shall be universally applicable to all internal regions of a SRM with minimal to no empirical corrections and/or scaling factors. Any use of empirical corrections and scaling factors shall be justified. The MRMs shall capture and describe the physicochemical mechanisms for material ablation including, but not limited to, heat transfer modes (conduction, convection, and radiation), chemical decomposition, and thermomechanical erosion due to particle impact and fluid-thermal-structural interaction. Code verification traceable to the identified mechanisms for ablation shall be demonstrated and limited code validation shall be performed using existing data sets. Physicochemical model development, code development, verification results, and validation results shall be reviewed by the IPT. No experimental testing for validation data collection will be performed under this effort.

I-1.1.6. Mix and Cast Models: The objective of this effort is to develop physics-based models to capture the ballistic and structural variability in solid grains due to propellant mixing and casting processes. The mix and cast models (MCMs) shall simulate the manufacturing process of solid propellant grains starting from the individual propellant ingredients and ending at the final cured propellant grain. The MCMs shall include any variations in the mixing and casting process including, but not limited to, multi-batch, mixer size, and mixer power inputs. A physical model shall be developed defining the various physicochemical mechanisms involved. Code verification traceable to the identified mechanisms involved in solid propellant mixing and casting shall be demonstrated and limited code validation shall be performed using existing data sets. Physicochemical model development, code development, verification results, and validation results shall be reviewed by the IPT. No experimental testing for validation data collection will be performed under this effort.

Validation Test Design: The objective of this effort is to design validation unit tests for the SRM M&S tools, including SRM M&S tools developed outside this project. The tests shall be designed to measure distinguishable physicochemical mechanisms of the SRM M&S tool being validated and minimize the potential for confounding variables. Predicted test results shall be performed using the SRM M&S tool of interest. Model predictive and estimated experimental test uncertainty shall be included as part of the validation test design. Validation test design and assessments shall be reviewed by the IPT. No experimental testing for validation data collection will be performed under this effort.

I-1.2. M&S Project Requirements: Proposed programs shall meet all of the following requirements and the proposal shall contain a description of how each requirement will be accomplished in the proposed program and the justification behind the proposed approach. Simply restating requirements will not be considered sufficient justification to meeting the intent of the requirement.

I-1.2.1. Project shall include participation in the IPT. All data and assessments shall be reviewed by the IPT and significant IPT findings shall be clearly documented in interim and final reports.

I-1.2.2. Project shall define a baseline of current capabilities in M&S for SRM manufacturing, design, development, and analysis including specific model uncertainties and input sensitivities and how these uncertainties/sensitivities aggregate into an overall SRM propellant mass fraction and specific impulse predictive uncertainty.

I-1.2.3. Project shall develop a time-phased roadmap of future M&S work based on analysis of current capabilities and identified shortfalls. The roadmap shall contain the expected reductions in predictive uncertainty for propellant mass fraction (Mf) and delivered specific impulse (Ispd).

I-1.2.4. Project shall clearly define sources of error.

I-1.2.5. Project shall develop a usable and highly automated code for distribution to the Government and their contractors.

I-1.2.6. Project shall develop a code usable on a high power workstation – either Linux and/or Windows based.

I-1.2.7. Project shall develop and document the necessary inputs and outputs for models.

I-1.2.8. Project shall identify the overall phenomena and its relationship to the physicochemical mechanisms to be modelled and codified. The use of physics-based models for these mechanisms shall be identified. Rationale shall be provided for the use of any empirical models, and limitations for extrapolation into new technology shall be identified.

I-1.2.9. Project shall identify the demonstration and verification methods including traceability to the physicochemical mechanisms being modeled.

I-1.2.10. Project shall identify the validation method, including validation reference data and predictive capability maturity method to assess model credibility and technology readiness.

I-1.2.11. Project shall assess validation test methods or data sources used to obtain validation data with respect to test data uncertainty and isolation of planned physicochemical mechanisms to be observed.

I-1.2.12. Project shall deliver software in compliance with IDIQ requirement I-4.3.

I-1.2.13. Project shall include a minimum of one summary JANNAF paper and presentation per IDIQ requirement I-2.2.

I-1.3. Proposal Requirements: The proposal shall define the following items in sufficient detail with justified relevancy to give the Government evaluation team insight into the planned effort and its relationship to technology development.

I-1.3.1. The proposal shall define a model baseline. The proposal shall define and justify the quantified predictive uncertainty of the baseline and expected value at the end of the effort.

I-1.3.2. The proposal shall describe a complete project plan including a specified approach to develop the proposed technologies detailing all of the work, cost, schedule, and resources needed.

I-1.3.3. The proposal shall describe the project management organization and why that proposed organization is required to accomplish a successful project.

I-1.3.4. The proposal shall describe a detailed risk management and systems engineering process and specify how that process will be applied to the entire project, including selection of the M&S approach to be developed.

I-1.3.5. The schedule for each project effort shall be integrated with the schedule for CDRLs (monthly, interim, and final reports) and meetings (reviews, IPTs, and JANNAF meetings) for the most efficient use of contract funding and best timely dissemination of research.

I-1.3.6. The proposal shall identify major milestones identifying expected key findings and accomplishments. The milestones shall include planned reviews.

I-1.4. SRM M&S Project Data Requirements: The following subset of the IDIQ CDRLs is provided in Table 2 and please note CDRL items that indicate “NOT Required” in the frequency column. The CDRL numbering scheme between the IDIQ contract and each project shall be maintained in order to maintain consistency in identifying CDRLs.

Table 2: M&S Project Contract Data Requirements List (CDRL)

Schedule: The anticipated period of performance for this SRM M&S project is Thirty-six (36) months technical effort, plus 90 days for the Final Scientific and Technical Reporting Cycle.

Other Information: Reference items in section I-4.

Air-Launched Booster Project: Energy Management and Motor Refinement I-1.5. This project falls under TDA2 – Air-Launched Booster and will be awarded at the same time as the basic IDIQ contract. This project is to continue development of advanced air-launched booster technologies developed under the Missile Component Advanced Technology IDIQ Task Order 6 (MCAT TO6). Due to the wide range of possible strike weapon concepts being developed, further exploration is needed on advanced booster technology. Two current areas of interest include, development of Booster Energy Management (BEM) technologies and Motor Refinement and Environments (MRE) technologies. All project efforts (BEM and MRE) need not be proposed to but must be addressed, i.e. negative replies are requested.

I-1.5.1. Booster Energy Management (BEM): The objective of BEM is to explore technologies to manage booster net energy delivery to a strike weapon. Using the latest MCAT TO6 Advanced Air-Launched Booster (AALB) designs as a baseline, conceptual designs implementing energy management technology shall be developed which can include, but is not limited to, thrust termination, thrust vectoring, pulse motors, staging, and aerodynamic control/missile maneuvering. As part of the conceptual design development, design trades shall be performed to assess the trade-off between energy management; maximum and minimum delivered energy; impact to meeting AALB baseline performance requirements; development cost; production cost; and maturity of the proposed technologies with respect to technology readiness level (TRL) and manufacturing readiness level (MRL).

I-1.5.2. Motor Refinement and Environments (MRE): The objective of MRE is to expand the AALB design space to meet anticipated operating environments, further mature the MCAT TO6 designs, and explore alternate booster configurations. A baseline AALB design shall be tested to understand the impact of anticipated operating environments for an air-launched booster. This anticipated environments activity includes, but is not limited to, operating and storage temperatures, carriage loads (static and dynamic), flight thermomechanical loads, and general weapon system handling. Due to various potential strike weapon configurations, alternate booster configurations and designs shall be explored to expand the possible trade space for strike weapon boosters. This includes, but is not limited to, multi-stage configurations, BEM technology, motor geometry, alternate launch platforms, and motor impulse.

I-1.6. Project Requirements: Proposed projects shall meet all of the following requirements. The proposal shall contain a description of how each requirement will be accomplished in the proposed project and the justification behind the proposed approach. Simply restating requirements will not be considered sufficient justification to meeting the intent of the requirement.

I-1.6.1. Project shall include a minimum of one summary JANNAF paper and presentation per IDIQ requirement I-2.2.

I-1.6.2. BEM Requirements I-1.6.2.1. Project shall explore technologies to manage booster energy delivery to a strike weapon.

I-1.6.2.2. Project shall develop preliminary conceptual designs implementing energy management technologies.

I-1.6.2.3. Project shall assess the impact of energy management relative to the baseline AALB designs to maximum and minimum delivered energy; development cost; production cost; and the technology and manufacturing maturity of the proposed technologies.

I-1.6.3. MRE Requirements I-1.6.3.1. Project shall assess AALB components and integrated motor technologies to meet anticipated operating environments.

I-1.6.3.2. Project shall exit the technology development effort with a booster at a minimum of TRL 5.

I-1.6.3.3. Project shall explore the trade space of configuration changes and assess the impact of these changes to meeting strike weapon requirements and environments.

I-1.7. Proposal Requirements: The proposal shall define the following items in sufficient detail with justified relevancy to give the Government evaluation team insight into the planned effort and its relationship to technology development.

I-1.7.1. The proposal shall define a booster baseline. The proposal shall define and justify the expected performance and compliance with strike weapon requirements.

I-1.7.2. The proposal shall describe a complete project plan including a specified approach to develop the proposed technologies detailing all of the work, cost, schedule, and resources needed.

I-1.7.3. The proposal shall describe the project management organization and why that proposed organization is required to accomplish a successful project.

I-1.7.4. The proposal shall describe a detailed risk management and systems engineering process and specify how that process will be applied to the entire project, including selection of the technologies proposed for development.

I-1.7.5. The schedule for each proposed task order shall be integrated with the schedule for CDRLs (monthly and annual reports) and meetings for the most efficient use of contract funding and best timely dissemination of research.

I-1.7.6. The proposal shall identify major milestones identifying expected key findings and accomplishments. The milestones shall include planned reviews.

I-1.8. Air-Launched Booster Project Data Requirements: The following subset of the IDIQ CDRLs is provided in Table 3 and please note CDRL items that indicate “NOT Required” in the frequency column. The CDRL numbering scheme between the IDIQ contract and each project shall be maintained in order to maintain consistency in identifying CDRLs.

Table 3: Air-Launched Booster Project Contract Data Requirements List (CDRL)

1. Schedule: The anticipated period of performance for the Air-Launched Booster project is forty-eight (48) months technical effort, plus 90 days for the Final Scientific and Technical Reporting Cycle.

Other Information: Reference items in section I-4.

AWARD INFORMATION:

I-2. Anticipated Funding:

I-2.1. Contract Ceiling: The IDIQ has a collective ceiling of $40M that will be measured against all projects awarded.

I-2.2. Project funding: These funding profiles are an estimate only and will not be a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. All potential offerors should be aware that due to unanticipated budget fluctuations, funding in all areas may change with no notice.

I-2.2.1. SRM M&S Project: The anticipated funding for all awards under Modeling and Simulation is $3,184k. Proposals that are greater than this value should provide significant additional justification.

I-2.2.2. Funding per Award: It is anticipated that each award will be $1,000k to $1,592k. The anticipated funding profile per award is provided in Table 4.

I-2.2.3. Technically sound and affordable approaches in all of the subtopic areas outlined in sections I-5.1.1 to I-5.1.5 is desired. Due to the multiple sub-topics for this project, proposals should include flexibility to be modified by the Government in order to best suit Call 2’s technical goals and objectives within funding constraints.

Table 4: Anticipated Task Order 1 Total Funding Profile

I-2.2.4. Air-Launched Booster Project: The anticipated funding for all awards under Air-Launched Booster is $3.7k.The anticipated funding profile per year is provided in Table 5.

I-2.2.5. Funding per Award: It is anticipated that each award will be $1,500k to $1,850k. Proposals that are greater than this range should provide significant additional justification for exceeding the outlined range.

I-2.2.6. Proposals that exceed the anticipated funding profile for any year should provide additional justification. Proposals cannot exceed the funding profiles outlined in Table 5. Proposals that violate the annual fiscal profile should provide significant additional justification and include flexibility to be modified by the Government in order to best suit Call 2’s technical goals and objectives within funding constraints.

Table 5: Anticipated Task Order 2 Total Funding Profile

Type of Contracts/Instruments:

The Government anticipates awarding Cost-Plus-Fixed-Fee (CPFF) from projects resulting from this call, with a Firm-Fixed-Price (FFP) CLIN for the final report. If another type of contract is desired, please contact Contracting POC before submittal of proposal.

Negotiations:

The Government intends to evaluate proposals and award, part, some, all, or none of the proposals received. After evaluations are complete the government may enter into negotiations with companies selected for funding. Award will be predicated on successful negotiations. The government reserves the right to discontinue negotiations with any contractor should the parties fail to reach agreement on contract terms, conditions and cost/price within a reasonable time.

Anticipated Award Date:

The IDIQ contract, SRM M&S project, and Air-Launched Booster project are anticipated to be awarded by May 2017.

PROPOSAL APPLICATION AND SUBMISSION INFORMATION:

Content and Form of Submission for Proposals:

Offerors shall submit one original with five additional hard copies, and two electronic (optical disks) copies of their proposal to the contracting office. The Government will check the proposal for conformation to the stated requirements and deviation from stated requirements will be dealt with in the manner stated in each of the following sections.

Proposal Contents: All proposals will consist of a single volume with sections, appendices and tables described below.

Required Format: Proposals are to be on 8.5 inch x 11 inch pages with one (1) inch margins on all sides. Headers, footers, and page number can be in the margins, but the margins shall contain no technical information. Any technical information in the margins will not be considered. A template will be utilized to see if text extends into the margins, and if it does the specific text will be blacked out and the remaining text will be read as is.

The text will be 11-point Arial single space with 10pt spacing between paragraphs, with no text or line compression, for all text body, figures, tables or attachments, unless otherwise directly specified in the proposal structure below or BAA templates. If another font, font size, or paragraph spacing is utilized, the incorrectly formatted sections will be reformatted in the electronic version and any overflow beyond limits will be removed. The remaining document would then be evaluated as is.

Pages shall be numbered continuously throughout the proposal. The cover page and table of contents are not numbered pages. The body of the proposal (sections III-1.5.3 through III-1.5.8) shall start with page #1. Page number on the bottom of each page shall include “Page X of Y” to stipulate the current page (X) and the total number of pages in the body (Y). Appendices shall be numbered by the section, a dash, and then the page, as in A1-1 for the first page of appendix A1.

Sections shall be numbered (i.e. Section 1, Section 2, etc.), with individual sections starting on a new page with tab dividers. Subsections may be numbered within each section based on the offeror’s organization, but subsections should not start on their own individual page.

SOW, WBS, schedule items, and basis of estimates (BOE) shall use a consistent and complementary numbering system throughout the proposal. For example, SOW task 4.1.1 shall be related in task and scope to WBS 1.1, schedule task 1.1, and BOE item 1.1. If method is not followed proposal will be returned unevaluated.

Any figure and table shall be discussed in the text; otherwise, it will not be evaluated. Figures and tables shall have titles and shall be numbered.

If any item is illegible (due to font size or print blur) at 100% magnification to the evaluation team, it will not be considered.

The hardcopy of each proposal shall be mechanically bound to itself either with staples, straps, or in a ring binder so that the proposal stays physically connected through handling. Paperclips, binder clips, and/or paper clams are not sufficient.

Optical disks with the Microsoft Word version of the proposal shall be submitted with the hard copies of the proposal and exactly match the hard copy; if they do not match, the proposal will be returned unevaluated.

Appendices shall follow these format requirements and are subject to the same controls as stated above, unless stated.

All cost spreadsheets provided shall be in Microsoft Excel 2003 format or later. Within the workbook, all spreadsheets, cells and formulas shall be visible with no hidden fields.

Number of proposals: One proposal for the IDIQ contract (section III-1.4) and for each project (section III-1.5) can be submitted for this call per prime offeror; if more than that is provided the extras will be removed at random. Submissions for this call do not affect or influence submissions for other calls on this BAA.

IDIQ Proposal Structure: The IDIQ proposal shall be comprised of a single volume formatted per III-1.2 and the limitations below. The IDIQ Capabilities volume provides evidence that the offeror has the capability and capacity to perform all anticipated projects based on the TDAs identified in section I-1.5.

A cover sheet shall be included at the front of the proposal with the following information:

Title of proposal Full company name and address BAA number submitting proposal against Call number proposing to Point of contact, name, title, phone, fax number, and email CAGE code DUNS number Type of contract proposed (e.g. CPFF, FFP) Name, address, and phone number of administration (DCMA) office Name, address, and phone number of audit (DCAA) office Validity period in accordance with BAA section III-2 Appropriate markings (ITAR, destruction, competition sensitive) Table of Contents [unlimited] sections, appendices, tables, and figures Section 1: IDIQ Overview: [Maximum Page Limit 2 pages] This section provides an introduction to the TDAs to be addressed and how these TDAs are related to the offeror’s capabilities and current physical capability.

I-2.2.7. Section 2: Program Management: [Maximum Page Limit 2 pages] This section describes the organizational structure of the offeror’s research organization and how the offeror will manage personnel over the life of the effort. The proposal will explain why the proposed personnel structure and proposed personnel are the best possible resources to address the TDAs. External interfacing of the research team with both the subcontractor/consultants and with the government shall be clearly defined.

I-2.2.8. Section 3: Risk Management and Systems Engineering: [Maximum Page Limit 3 pages] The proposal will define how the offeror will apply risk and systems engineering processes for projects under the IDIQ. The research organization’s risk management approach is explained in conjunction with past examples.

Section 4: Related Past Performance: [Maximum Page Limit 8 pages, maximum 8 projects] This section describes related programs that support or illustrate the offeror’s technical and management capabilities to accomplish all anticipated IDIQ projects. Related programs should demonstrate ability to cover all TDAs and be explicit with relevancy. In addition to discussion of relevancy, details shall include contract number, government agency, government point-of-contact, contract value, contract award and end dates, and DTIC tracking number of the final report if available.

Section 5: Company’s Physical Capability: [Maximum Page Limit 4 pages] This section specifically details the offeror’s physical capacity to accomplish all IDIQ projects.

Appendix A: Statement of Work (SOW): [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] The SOW shall contain a summary description of the TDAs to be addressed. Offerors are cautioned to include only the information that is essential to a clear, logical, binding, and reasonable SOW. This document will be made part of any resulting contract. Do not include any proprietary information in the SOW. The SOW section structure below is based on the SOW description in the BAA Guide for Industry in Part III of the BAA; offerors should refer to that document for more information. All subsections of the SOW are to be numbered in outline form according to the number of the main section (i.e. 1.1, 1.2, 1.2.1.1, 1.2.1.2, etc.)

1.0 BACKGROUND

The background information should identify the requirement in very general terms; describe why the project is being pursued, and how it relates to other projects. Summarize any statutory authority or regulations affecting the overall requirement.

2.0 SCOPE

This section should provide a brief statement of what the offeror expects to accomplish under the contract — the breadth and limitations of the contract effort. It should not include specific work tasks or a description of deliverable products since this will be included in the “Tasks” section.

3.0 OBJECTIVES

This section should provide a concise overview of the contract effort goals and objectives; and how the results or end products will be used.

4.0 TASKS/TECHNICAL REQUIREMENTS

This section defines the tasks that the contractor shall complete during contract performance and would have a task description for each TDA identified in I-1.5. The description of task requirements shall be flexible enough to allow multiple projects to be performed under each TDA. The tasks shall be defined by “shall” statements that are contractually binding rather than “will” or “may” statements.

5.0 DELIVERABLES

This section should clearly state all deliverables including CDRLs and material per section I-2.

6.0 PERIOD OF PERFORMANCE

The period of performance shall be defined by project orders under the IDIQ contract. No specific period shall be identified in this section for the IDIQ.

Appendix B: Compliance Matrix: [no maximum page limit but material…