BAA-RQR-2017-0002_ART_BAA_Call_1_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 1 (Amended)

1 13 December 2016

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 1

BAA-RQR-2017-0001

CALL 1 DESCRIPTION

Advanced Post-Boost Technology Development:

Problem Statement: Increased delta-V and reduced cost are needed to advance controllable solid post boost technologies for strategic missiles.

Technology Objectives: The objective of this effort is to design, develop, and test component technology specifically for advanced controllable solid post-boost (ASPB) propulsion systems with the goal of increasing solid post-boost delta-V and / or reduce cost relative to State Of The Art (SOTA) post boost systems for strategic missiles with potential applications for missile defense. The program emphasis is clarified in I-1.7 below and shall include incremental plans for achieving the goal and assessing goal achievement to ensure best execution of Research and Development (R&D), testing, and analysis of results. The objectives of the ASPB component technology effort should clearly contribute to the improved delta-V and/or reduce cost by an amount set by the proposer over a defined baseline for solid post boost.

Supplemental Packages: A supplemental information package for this Call 1 is available to potential offerors who are authorized to receive restricted technical information. This package includes the specifics of the current Government baseline, goals, and requirements for Advanced Post-Boost systems. See BAA III-5 about how to request the Call 1 supplemental package.

I-1.1. Scope: Call 1 encompasses all aspects of ASPB propulsion systems for strategic missiles. While many solid post-boost propulsion technologies for strategic and missile defense applications can be incorporated into the missile system to improve the range, payload, accuracy, and cost of the missile system, the government does not have the funds to address all of the possible post boost technologies in this BAA opportunity, therefore novel key technologies must be chosen. It is therefore anticipated that proposers will delineate concepts of a component, or components, of the ASPB systems that will integrate into an ASPB propulsion system to achieve the delta-V goals and / or reduce cost. The development of key technologies within a solid post boost system may leverage previous work funded and / or carried out by the government. BAA Call 1 involves the design, development of components and possibly processes specific to that component, testing, and the analysis of test results for the ASPB component technology.

Technology and Methodology Description: In order to increase the delta-V and/or decrease the cost of the ASPB propulsion system, AFRL is interested in technology development in the following areas: (1) lightweight high temperature composite case, insulation, and/or feed system assemblies and (2) integrated hot gas valves and/or other solid post-boost components made in part, or completely, through additive manufacturing. It is acceptable for offerors to propose work requiring part or all of the funding detailed below, and it is acceptable for the program to focus on one, or both, of the specific areas (1 and 2 above). For both areas, a controllable solid post-boost propulsion system baseline for delta-V and cost shall be defined by the contractor. Program emphasis should be placed on component design with consideration to part count, materials sustainability, and manufacturing complexity. The anticipated effect of the design and approach shall be clearly explained regarding contribution to 1) improved delta-V including, but not limited to, improved accuracy and 2) decreased development and production cost of the solid post-boost component and system.

Technology Development Requirements: Please note that these are program requirements rather than proposal requirements and are put forth to clarify program expectations and assist in development of the approach to the problem. Awarded programs shall meet all of the following requirements:

The contractor must define a post-boost technology baseline (including individual technologies) that will allow the measurement of progress. The chosen contractor baseline must consist of reasonable SOTA technology, and an explanation of reasonableness must be given. References to information sources used for baseline shall be provided by contractor.

With quantitative terms throughout, with the post boost system that the ASPB component is designed for, and with identifying an appropriate strategic system for that post boost system, the contractor shall define their objective for each proposed technology including the objectives’ impact on Delta-V and cost of a solid post-boost propulsion system.

Reliable method(s) to measure the improvement of the capabilities of component technologies over the selected baseline shall be described and used.

Proposed program shall define in detail the methodology (engineering and / or scientific) to develop and demonstrate all proposed technologies, and to verify progress towards objectives. This methodology shall include decision gates, a schedule, and TRL/MRL levels at all major go/no-go points.

Technology Readiness Level –It is expected that technologies and methodologies used for goal demonstration will be at least of TRL 4 at the end of the technical effort. DoD TRLs are defined in chapter 10, section 5 of the Defense Acquisition Guidebook (https://dag.dau.mil/).

The industrial sustainability of materials (inert and energetic), components, and manufacturing capability shall be addressed. Domestic sources shall be identified and used for all materials.

The program’s structure and approach shall be focused on achieving a significant advancement in support of the post-boost goal.

Model-based development shall be applied to the design and fabrication of proposed technology. Models used shall be described in enough detail, and with an assessment of design uncertainty, to provide credibility of their use. In as much as applicable, models shall be used to project technology benefits with respect to performance and cost goals.

The contractor shall identify the key risks in the development, testing, and integration of proposed technologies into a post boost propulsion system and strategic missile system. The likelihood and consequence of all identified risks in a rating scale of 1-5, and rationale for ratings shall be given. Risk mitigation strategies shall be described specifically as they pertain to the proposed work.

Proposal Requirements: The document shall define these items in sufficient detail with justified relevancy to give the Government evaluation team clear insight into all processes and technologies. These proposal requirements shall be defined in individual sections of the proposal (see III-1.4 of this BAA Call):

The contractor shall define a post-boost technology baseline (consisting of reasonable SOTA technology, including individual component technologies) that will allow the measurement of progress relative to the government baseline. The contractor shall choose their baseline such that it shall not decrease the technical value of delta-V and / or cost reduction goals relative to the government baseline. (For example, the contractor shall not set a delta-V baseline with a system that is inferior to SOTA and makes it technically less challenging to show a delta-V increase.) The proposal shall define and describe the contractors chosen solid post-boost baseline, shall define and describe the validity, reasonableness, and appropriateness of the proposed post-boost baseline, and shall do so while explaining how the contractor’s baseline fulfills the requirements of the government baseline. References to information sources used for baseline shall be provided by contractor.

The contractor shall clearly explain why the proposed ASPB system component is applicable to modern strategic missiles in terms of quantitative capabilities and dimensions. The contractor shall clearly explain why the proposed post boost system component is expected to be applicable to future SRMs.

The proposal shall articulate how progress towards the proposed solid post boost technology goals will be measured and quantified against the contractor baseline. This articulation shall include quantitative and qualitative methods to verify material properties, experimental and analytical / test methods, methods to interpret results, go/no go points, any alternate technologies that will be implemented if preferred technologies prove inadequate. This articulation shall apply to both individual technologies and their aggregate into the component system.

The proposal shall describe the models used for development and validation of the proposed solid post boost component(s) in enough detail, and with an assessment of design uncertainty, to provide credibility and benefits of their use. This description shall describe how models project technology benefits with respect to performance and cost goals. Any predictive capabilities that may improve as a result of the proposed program should be noted.

The proposal shall include a complete technical program plan including an overview of technology flow of the proposed component into a solid post boost system, an overview of technology flow of subcomponents into the proposed component, and major milestones for the proposed component with Technology Readiness Levels at those milestones. The overview shall include the analytical and test methods to characterize the proposed subcomponents and the proposed component of the solid post boost system.

The proposal shall include a complete programmatic plan along with the correlating cost, schedule, and resources (including any government furnished property) needed to carry out that plan.

The proposal shall describe the program management organization and explain why that proposed organization will facilitate a successful program.

The proposal shall describe trade studies to be carried out under the program, the trade space that will be applied to those studies, and decision gates.

The proposal shall describe a detailed risk management and systems engineering process and how that process will be applied to the entire program.

The proposal shall address sustainability of materials.

Deliverable Items:

Any contract awards resulting from this Call shall be required to deliver appropriate data items and possibly 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 items below shall be incorporated into each proposed effort. 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)

*In Table 1, each entry in “Authority” is referred to as a DID (Data Item Description). Each DID can be found in full at http://quicksearch.dla.mil/. To access the DID from this web site, copy and paste the entire “Authority” entry without the “/T” into the Document ID box and click on search, then click on the Document ID that comes up. The following (Section I-2) are additional descriptions and do not replace the corresponding DIDs and serve as a very basic overview to assist in cost estimation:

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.

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, all monthly reports shall include:

A section with title shall be given for each WBS and Major Task awarded in each monthly report. Each section title must state the WBS number and the Task number. If no progress is made under a task, the contractor shall state current status of the task and that no progress was made for the current reporting period.

For each task that has been completed, a summary of activities completed with conclusions shall be provided with the date of task completion (this entry may be copied and pasted for the remainder of monthly reports until end of contract).

For each task where progress was made during the reporting period, a brief status update till the reporting period shall be given followed by a detailed technical report for work completed during the reporting period. The detailed technical reporting shall be of the quality and completeness required for the final report.

Interim Report: Interim Reports will be submitted annually, due every 12 months to the day (unless that day falls on a weekend, holiday, or contractors regular day off, in which case the due date will be set accordingly) 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.

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

I-1.2. 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 the technical period of performance summarizing the efforts performed under the project.

Test Plan: This technical report will be submitted once for Governmental approval and updated as needed throughout the program. This plan is the detailed evaluation of the proposed Advanced Post-Boost Component intended to show advancement against the contractor baseline in regards to component (and subcomponent) design and fabrication methodology, processes, and final achieved product.

Developmental Design Drawings/Models and Associated Lists: Each necessary item (drawing, models, and associated list) shall be submitted with necessary revisions. Necessary items are what is needed to analyze and/or replicate the test plan and Advanced Post-Boost methodology on a future or concurrent efforts.

All proposals shall ensure of proper disposal of energetic material and hazardous waste, including accounting for cost of disposal if relevant.

Schedule:

The anticipated period of performance for contracts resulting from this call is thirty-two (32) month technical effort, plus 90 days for the Final Scientific and Technical Reporting Cycle.

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 to the government may be required. It shall be verified with the government whether or not the government requires the delivery of any residual contractor-acquired property. Delivery is due thirty days after end of technical effort of each contract if residual hardware is developed. The proposal should include the cost of packaging and shipping of contractor-acquired property assets to Edwards AFB.

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 A008.

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.4.9.15). If proposing GFP or GFI, it shall be intended for use within the proposed program, and 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 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 1; 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 or biweekly as a minimum, unless a different periodicity is specified by the government program manager. The biweekly telecon packages shall consist of a slide set that shall include: A technical review, programmatic review with schedule, financial status.

AWARD INFORMATION:

I-2. Anticipated Funding:

I-2.1. This funding profile is 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. Funding Profile: The anticipated total funding for all awards under Call 1 is $2,276K. The anticipated funding profile per award is provided in Table 2.

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

I-2.4. Proposals cannot exceed the funding profile per fiscal year as outlined in Table 2. 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 1’s technical goals and objectives within funding constraints.

Table 2: Anticipated Total Call 1 Funding Profile (all values in $1000s)

Type of Contracts/Instruments:

The Government anticipates awarding Cost-Plus-Fixed-Fee (CPFF) type contract(s) from proposals resulting from this call. 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 first contract is 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.4.3 through III-1.4.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. 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 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 can be submitted for this call per prime offeror; if more than that is provided the extras will be removed at random. For other calls of this BAA, the number of proposals will be determined at the release of the individual call. Submissions for this call do not affect or influence submissions for other calls on this BAA.

Proposal Structure: The proposal shall be comprised of a single volume with sections and appendices formatted per III-1.2 and the limitations below.

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: Proposal Overview: [Maximum Page Limit 4 pages] This program summary and overview section provides an introduction to all pieces of the proposed program and how these pieces interconnect. This may include a flow chart / block diagram of the Work Breakdown Structure and Tasks. This section also explains the flow and integration of research and development, use of any subcontractors, testing and analyses, and risk management. The contractor post-boost baseline is stated in terms of the overall post boost system and relevant components, delta-V, and cost. The program objectives and their relation to the contractor’s post-boost baseline are discussed. This discussion shall include how the program objectives were derived. The program structure is outlined and explained in reference to the SOW (appendix A1), V&V plan (appendix A3), the program schedule (appendix B2), and the CDRL list (Table 1).

Section 2: Contractor baseline definition and baseline technologies: [Maximum Page Limit 12 pages] The contractor post boost baseline is defined. The technologies that make up the contractor post-boost baseline are defined and scientifically justified. Images and diagrams are used where possible. An explanation of why the technologies that comprise the contractor post boost baseline are considered State of the Art is given. Any systems that previously used the defined baseline, or components thereof, are described. The compatibility of the contractor baseline with a modern strategic Solid Rocket Motor is provided along with the reasoning for the choice of SRM for the compatibility discussion. The methods by which the developed technologies under the proposed program will be compared to the contractor baseline, and the reliability of this comparison, will be discussed. How these comparisons relate to delta-V and cost will be included in this discussion.

Section 3: Proposed Technologies: [Maximum Page Limit 15 pages] The technologies proposed to demonstrate program objectives are discussed. Technologies are explained in sufficient detail to understand the underlying physics of the technology and its role in the post-boost program. The reasoning as to why the chosen technologies are the best choice to meet the objective are explained. Technology development activities within the program are rationalized in terms of impact to meeting the program objectives. Sustainability of materials and reliability of processes are addressed. Previous use of constituents of proposed technologies in a relevant systems are described where applicable, along with the benefits per the relevant system. What is new about applying the technology to the proposed objective is explained. It is described if the proposed advancement lies in the design, fabrication, or both. How success will be measured / testing of components and/or their constituents is described.

Section 4: Program Plan: [Maximum Page Limit 15 pages] The steps to reach the objective are delineated. The overarching processes and procedures to be executed are discussed in logical order of, and relation to, the steps to reach the objective. Methodologies and technologies discussed in previous sections are connected to each step of the program. The use of subcontractors and their contribution to the plan is included. Configuration control and management of hardware and testing are discussed in detail. Risk mitigation strategies are discussed. Resource management and control are defined; details of required resources should be referenced from appendices, but the resource requirements shall be sufficiently explained to support a comprehensive program.

Section 5: Program management organization: [Maximum Page Limit 5 pages] This section describes the organizational structure of the research team (Program Manager, Principle Investigator, Task Leads, other Scientists and Engineers, subcontractors, consultants) and how the program will manage personnel. The proposal will explain why the proposed personnel structure and proposed personnel are the best possible resources for the program. The roles of key personnel are defined and the responsibilities for specific program areas are assigned to specific personnel. Sufficient detail will be provided to link specific tasks in the SOW to specific roles/responsibilities in the organizational structure. Subcontractor and consultant roles are discussed in detail with particular regard to their justification on the project and their importance to the objective of the program. External interfacing of the research team with both the subcontractor/consultants and with the government shall be clearly defined. Details in appendices B and C should be referenced as much as possible; repetition of details from these appendices is not necessary as long as the connection to the program role is clear.

Section 6: Risk management and systems engineer method: [Maximum Page Limit 3 pages] The proposal will define how the program will apply risk and systems engineering processes throughout the research effort. An overview of major risks and how these risks drove the program plan are discussed. The research team’s risk management approach is explained in conjecture with examples from the defined risk analyses in Appendix A4.

Proposal Appendices Appendix A1: 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 technical methodology as well as detailed task descriptions. 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 step of the WBS. The description of task requirements will depend on the approach that is selected to describe the required effort. 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.

6.0 PERIOD OF PERFORMANCE

The period of performance shall be clearly stated using in units of months after contract award. Milestones shall be stated as a number of months after contract award. These milestones shall include the end of technical effort and end of contract period of performance.

Appendix A2: Compliance Matrix: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] The specific proposal section and specific proposal page is listed for each requirement to cite where the proposal defines compliance with the BAA Call 2 requirements (see I-1.5) and CDRL requirements (see I-2.1.2) Table 3: Appendix A2: Compliance Matrix

(Section & Page) SOW Section 4.0 (Paragraph & Page) Synopsis/Rationale

I-1.6.1

I-1.6.2

I-1.6.3

I-1.6.4

I-1.6.5

I-1.6.6

I-1.6.7

I-1.6.8

I-1.6.9

I-1.7.1

I-1.7.2

I-1.7.3

I-1.7.4

I-1.7.5

I-1.7.6

I-1.7.7

I-1.7.8

I-1.7.9

I-1.7.10

I-2.1

I-4.1

Appendix A3: Verification and Validations Plan (V&V): [Five (5) pages] The structure of the offeror’s V&V plan is described in regards to specific tasks. Reference to company procedures may be used as long as the intent or application of those procedures is clear to the government reviewers. A systematic approach shall be stressed. A method of documenting and tracing these validations shall also be described.

Appendix A4: Risks and Mitigations: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] The risks are defined using the template provided as Table 4. Major technical, management, schedule, and cost risks are listed based on the offeror’s evaluation. This appendix can only contain the risk chart defined in Table 4 with cells formatted to wrap the text. The risk chart is designed to record an assessment of the initial risk and then an assessment of the risk AFTER applying a single mitigation approach. Multiple mitigation approaches shall be defined until the offeror reaches a risk factor that it is willing to accept for the program. The following details are included in the risk chart:

I-2.4.1.1.1. Risk ID: A unique number, starting at #1, for each initial risk.

I-2.4.1.1.2. Stage: A risk is defined as “Initial” or “I” on the risk chart or “Mitigated” or “M” on the risk chart. For risks marked as “I”, the mitigation approach is left blank. Each risk shall have one “I” entry but can have multiple mitigation entries.

I-2.4.1.1.3. Risk Statement: The risk is defined in this section as a clear statement of the cause and effect of the risk. Risks should be stated in an if-then structure.

I-2.4.1.1.4. Mitigation Approach: Definition of the tasks or steps taken to reduce the risk. For initial risk assessment, this position is left blank.

I-2.4.1.1.5. Likelihood: A number between 1 and 5 (inclusive) that defines the likelihood of the risk occurring based on Table 5. For initial risks, this likelihood is evaluated without any mitigation; for mitigation assessment, this likelihood is evaluated considering the application of the defined mitigation approach for this row.

I-2.4.1.1.6. Likelihood Rationale: A justification or basis for this likelihood is cited.

I-2.4.1.1.7. Consequence: A number between 1 and 5 (inclusive) that defines the consequence of the risk occurring based on Table 6. For initial risks, this consequence is evaluated without any mitigation; for mitigation assessment, this consequence is evaluated considering the application of the defined mitigation approach for this row.

I-2.4.1.1.8. Risk factor: The risk factor is determined using the likelihood number and the consequence number in Table 7. Risk factors below 12 are considered low and assumed to not need to be mitigated. Risk factors above 19 are considered high risk and should be mitigated to a lower risk factor. Risk factors between 12 and 19 (inclusive) may be accepted or further mitigation.

Distribution A: Approved for public release; distribution unlimited.

Public Affairs Clearance Number 16239

BAA-RQR-1

ART Call 1

Table 4: Appendix A4: Risks and Mitigations

Table 5: Risk Likelihood Table

Table 6: Risk Consequence Table

Table 7: Risk Factors Table

Consequence

Appendix A5: References: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA call] – References only listed in a standard and consistent manner thorough out bibliographic format. Only include references cited elsewhere in the proposal.

Appendix B1: Work Breakdown Structure (WBS) and WBS Dictionary: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] WBS shall be broken out to at least to level three detail to consist of a single work package, which represent the efforts and objectives of a small team of individuals who are working on a very specific outcome.

Table 8: Appendix B1: Work Breakdown Structure Table

1.1

1.1.1

1.1.2

1.1.3

1.2

1.2.1

1.2.2

Table 9: Appendix B1: WBS Dictionary

Etc.

Appendix B2: Program Schedule: [no maximum page limit] This section is limited to a single schedule chart of unrestrained size (i.e. this chart may cover a number of pages or even use 11x17 paper). Ensure that the words and dates can be read on the chart.

Appendix B3: Resumes of All Key Personnel: [Maximum Page Limit 1 page per person] The section includes key personnel, including proposed technical consultants.

Appendix B4: Company’s Physical Capability Table: [Maximum Page Limit 4 pages] This section specifically details the offeror’s physical capabilities to accomplish the program plan proposed.

Appendix B5: Related Past Performance: [Maximum Page Limit 1 page per program, maximum 8 programs] This section describes related programs that support or illustrate the offeror’s technical and management capabilities to accomplish the program plan proposed. Examples of related programs should demonstrate ability to cover all aspects of the program proposed and be explicit with 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.

Appendix C1: Proposal Cost Summary: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] The offeror shall provide a cost summary in a modular fashion by severable tasks. All proposed tasks shall be included. The Government reserves the right to fund none, some, parts of, or all of the proposed tasks. Present the modular cost summary in the format below. Each task (level 3 and above) shall have subtotals. Each level 3 task shall be broken out for labor, material, and Other Direct Costs (ODC). The tasks and costs in the template are hypothetical, non-predictive, and for the purpose of example only.

Table 10: Appendix C1: Modular Cost Summary Table

1.0

$3,000,000

1.1

$400,000

1.1.1

$100,000

1.1.1 Labor

$70,000

1.1.1 Material

$20,000

1.1.1 ODC

$10,000

1.1.2

$250,000

1.1.2 Labor

$200,000

1.1.2 Material

$20,000

1.1.2 ODC

$30,000

1.1.3

$50,000

1.1.3 Labor

$50,000

1.1.3 Material

$0

1.1.3 ODC

$0

1.2

$350,000

1.2.1 etc.

Appendix C2: Cost Summary by Government Fiscal Year: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] The offeror shall provide a cost summary broken out with subtotals for each government fiscal year (GFY) and ending with the total cost for that task. The government fiscal year is any cost occurred between October 1st and September 30th. GFY 2016 starts on October 1st, 2015. The tasks and costs in the template are hypothetical, non-predictive, and for the purpose of example only.

Table 11: Appendix C2: Cost Summary by GFY

Appendix C3: Cost Summary by cost element: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] Offeror shall provide a cost summary for proposed effort/priced CLIN by major cost elements including labor categories by Government Fiscal Year (GFY) [Oct 1 to Sept 30] using the format shown below. Ensure the totals for any cost elements, which require further breakdown as specified below, agree with the totals reflected in other cost summaries in the proposal. Ensure the types and quantities of all direct charged cost elements (labor, travel, computer, etc.) are consistent with the data provided in the proposal. For cost realism purposes, identify in electronic spreadsheet labor rates by category and GFY as well as all other direct and indirect rates (such as overhead) by GFY. Offerors shall submit all cost spreadsheets in Microsoft Excel 2003 format or later. Within the workbook, all spreadsheets, cells and formulas shall be visible with no hidden fields. Any cost information submitted shall be consistent with the offeror’s approved estimating system and shall duplicate the logic and mathematical formulae reflected in the paper copy of the proposal.

Table 12: Appendix C3: Sample Cost Summary by Cost Element Format

Direct Labor Hours & Dollars

Engineering Hours

Engineering Dollars etc.

Subtotal Direct Labor Hours

Subtotal Direct Labor Dollars

Overhead

Material

Subcontracts

Other Direct Costs

Subtotal

G&A

Estimated Cost

Facility Capital Cost of Money

Fee

Total

Appendix C4: Data Rights and exceptions (if any): [Maximum Page Limit one (1) page] The government expects unlimited data rights for methodologies and technologies developed in this program; if a different level of data rights is proposed for all or part of this program, exceptions shall be detailed and justified.

Appendix C5: Government Furnished Equipment or Data: [no maximum page limit but material shall be on appendix topic] Description of any GFE required for the proposed program, including written confirmation from the government representative responsible for that material that the hardware/data is available. Each specific item (hardware or data) shall be justified to relevancy, suitability and importance to the specific role.

Appendix C6: Contract exceptions [no maximum page limit but material shall be on appendix topic] Exceptions to the sample Model Contract Terms and Conditions Appendix C7: Resource Allocations: [no maximum page limit but material shall be on appendix topic and in format defined by this BAA Call] The offeror shall submit a summary table of person loading by WBS level three subdivided by labor type broken out by each month of the proposed program. Do not reflect dollar amounts in this schedule. All hours shown in this submittal shall agree with those reflected in the cost summary. The tasks and costs in the template are hypothetical, non-predictive, and for the purpose of example only.

Table 13: Appendix C7: Resource Allocation