MAST_BAA_with_Calls.pdf

BAA-RQR-2014-0002

BROAD AGENCY ANNOUNCEMENT

FOR THE AIR FORCE RESEARCH LABORATORY

ROCKET DIVISION

AEROSPACE SYSTEMS DIRECTORATE

RESEARCH AND DEVELOPMENT

BROAD AGENCY ANNOUNCEMENT

21 April 2014

Issuing Office: Air Force Test Center, Directorate of Contracting

Edwards AFB, CA

Distribution A: Approved for public release; distribution unlimited.

Public Affairs Clearance Number 14189

TABLE OF CONTENTS:

BROAD AGENCY ANNOUNCEMENT

I. PROGRAM DESCRIPTION:

I-1. Statement of Needs:

I-2. General Requirements:

II. ELIGIBILITY INFORMATION:

II-1. Eligible Offeror/Applicants:

II-2. Access to Restricted Technical Information:

III. PROPOSAL APPLICATION AND SUBMISSION INFORMATION:

III-1. General Instructions:

III-2. Proposal/White Paper Validity Period III-3. Amendments:

III-4. BAA Guide:

III-5. Supplemental Information Package:

IV. AWARD ADMINISTRATION INFORMATION:

IV-1. One-Step Process:

IV-2. Two-Step Process:

IV-3. Closed Process:

IV-4. Awarding of Contracts:

IV-5. White Paper Selection:

IV-6. Award Notices:

IV-7. Proposal Categories:

IV-8. Sequence of Awards:

V. AGENCY CONTACTS:

V-1. Technical Point of Contact (TPOC):

V-2. Contracting Points of Contact (CPOC):

V-3. Ombudsman:

VI. OTHER INFORMATION:

VI-1. BAA Value:

VI-2. Support Contractors:

VI-3. Technical Support Contractors (Post-Award) VI-4. Communication:

VI-5. Debriefings:

VI-6. Wide Area Work Flow Notice:

VI-7. Item Identification and Valuation:

VI-8. Forward Pricing Rate Agreements:

VI-9. Pre-Award Clearance:

VI-10. Excessive Pass-Through Charges:

VI-11. Associate Contractor Agreements:

VI-12. Post-Award Small Business Program Re-representation:

VI-13. Future Calls:

VI-14. Technology Readiness Levels (TRL)

VII. Bibliography

BROAD AGENCY ANNOUNCEMENT CALL 1

I. CALL 1 DESCRIPTION

I-1. A&S Technology Development Requirements:

I-2. Deliverable Items:

I-3. Schedule:

I-4. Other Information:

II. AWARD INFORMATION:

II-1. Anticipated Funding:

II-2. Type of Contracts/Instruments:

II-3. Discussions:

II-4. Anticipated Award Date:

III. PROPOSAL APPLICATION AND SUBMISSION INFORMATION:

III-1. Content and Form of Submission for Proposals:

IV. PROPOSAL CONTENT SUMMARY:

IV-1. Ineligibility:

IV-2. Submission Dates and Times:

IV-3. Incorrect Submittal:

IV-4. Funding Restrictions:

V. PROPOSAL REVIEW INFORMATION:

V-1. Evaluation Criteria:

V-2. Review and Selection Process:

VI. PROPOSAL CONTENT CHECKLIST:

BROAD AGENCY ANNOUNCEMENT

21 April 2014

NAICS CODE: 541712

FEDERAL AGENCY NAME: Air Force Research Laboratory, Aerospace Systems Directorate (AFRL/RQ-West)

BROAD AGENCY ANNOUNCEMENT TITLE: Motor Aging and Surveillance Technology (MAST) Development and Demonstration

BROAD AGENCY ANNOUNCEMENT TYPE: This is a Broad Agency Announcement (BAA) with multiple calls

BROAD AGENCY ANNOUNCEMENT (BAA) NUMBER: BAA-RQR-2014-0002

BRIEF SUMMARY OF MAST BAA: This BAA describes the development of the Motor Aging and Surveillance Technology (MAST) Development and Demonstration that are of interest to the Air Force Research Laboratory (AFRL). The Government anticipates making one initial call with additional calls in the future. The Government anticipates awarding independent Cost-Plus-Fixed-Fee (CPFF) for technical efforts with a Firm-Fixed-Price (FFP) final report for all efforts awarded under this BAA It is anticipated that the second call will occur in FY15, a third call should occur in FY16, and a fourth call may occur in FY17. Calls 1 and 2 are anticipated to utilize closed one-step process where calls 3 and 4 are anticipated to utilize closed two-step process. The closed one-step and two-step processes will be described in section IV of this BAA.

BAA ORDERING PERIOD: 60 months after initial release

PROPOSALS DUE DATE AND TIME: Proposals due date and time will be specified in each call. Proposals received after the due date and time shall be governed by the provisions of FAR 52.215-1(c) (3). Specific information will be located in each call. It should be noted that this Edwards Air Force Base 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 because of security delays will be considered “late”. Furthermore, if offerors utilize commercial carriers to deliver proposals, they may not honor time-of-day delivery guarantees on military installations.

I. PROGRAM DESCRIPTION:

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

I-1. Statement of Needs:

I-1.1. Development of technologies to determine the state of solid rocket motors (SRMs) on an individual basis at any point within their service life (past, present, and future) with an acceptable confidence level in order to enable safe and successful mission completion. These technologies must reduce the predictive uncertainty of the service life estimate (RP21 Aging and Surveillance (A&S) goals see BAA section III-5), with negligible impact to other RP21 goals.

I-1.2. Demonstrate RP21 2017 A&S goal achievement (reduce the predictive uncertainty of the service life estimate by 20%), with negligible impact to other RP21 goals.

I-2. General Requirements:

I-2.1. Data Rights:

I-2.1.1. In exchange for paying for development of the data, the Government expects technical data, Non-Commercial Software (NCS), and NCS documentation developed entirely at Government expense to be delivered with unlimited rights. Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with Government purpose rights at minimum.

I-2.1.2. Offerors that propose delivery of technical data, NCS, or NCS documentation subject to less than unlimited rights will be considered.

I-2.1.3. Offerors that propose delivery of technical data, NCS, or NCS documentation subject to less than unlimited rights shall document fully:

I-2.1.3.1. What technical data, NCS, or NCS documentation was developed using indirect cost pools and/or costs not allocated to a Government contract

I-2.1.3.2. How this data/software will be incorporated into the MAST effort

I-2.1.3.3. How the incorporation will benefit the program

I-2.1.3.4. Whether those portions or processes are segregable from the overall proposed effort

I-2.1.4. The Government expects that delivery of technical data, NCS, and NCS documentation subject to less than unlimited rights will fully meet program needs.

I-2.1.5. Appropriateness of data rights proposed by the offeror is a part of the evaluation or award in each call.

I-2.2. Integrated Product Team (IPT): All efforts resulting from this BAA will operate within an integrated product team (IPT) arrangement led by AFRL. All offerors awarded contracts under this BAA are required to participate in the IPT. In addition to AFRL and all organizations awarded contracts under this effort, 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 upon their request or invitation. The IPT will meet as necessary but at least once per quarter alternating between Edwards AFB and remote meetings (via teleconference, video conferencing, Defense Connect Online [DCO], 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. It is EXCEEDINGLY desirable that offerors share information at IPT meeting to the greatest extent possible including but not limited to development, technical results, and demonstration plans. In addition to IPT meetings, individual awarded contractors will need to have routine meetings, as needed based on size and level of effort, with the Government to discuss progress, schedule, and any ongoing issues.

I-2.3. 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.

I-2.4. Export Control Information:

I-2.4.1. International Traffic in Arms Regulations (ITAR): ITAR will apply to this effort.

All technical data generated or delivered resulting from this BAA is controlled by ITAR, 22 CFR 120-131, and will require the export-controlled statement.

I-2.4.2. Export Administration Regulation (EAR): Commerce Control List (CCL) that includes “items” (i.e., “commodities,” “software,” and “technology”) developed under this effort may be subject to EAR (Title 15 CFR Export Administration Regulations, part 770. and Title 15 CFR part 779 Technical Data.), and these efforts need to implement the regulation requirements and the export-controlled statement

I-2.4.3. Export-Controlled Statement:

"WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.)

or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25."

When it is technically not feasible to use the entire statement, an abbreviated marking may be used, and a copy of the full statement added to the "Notice to Accompany Release of Export Controlled Data" required by DoD Directive 5230.25.

I-2.5. All data generated or delivered will also require one of the following two statements depending on the content of the information and the requirement of the CDRL. The use of the least restrictive distribution statement possible is required.

I-2.5.1. “Distribution Statement B – Distribution authorized to U.S. Government agencies only (Critical Technology) (Submittal Date). Other requests for this document shall be referred to AFRL/RQR, 5 Pollux Dr., Edwards AFB, CA 93524-7048.”,or

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

I-2.6. All data generated or delivered will also require the following statement:

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

I-2.7. 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 System for Award Management (SAM) https://www.sam.gov. 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 SAM. On-line registration instructions can be accessed from SAM home page at https://www.sam.gov.

I-2.8. Hazardous Materials: The handling of hazardous materials may apply to efforts resulting from this BAA. DFARS clause 252.223-7001 may apply to this program.

I-2.9. Ozone Depleting Substances: None.

I-2.10. Radioactive Materials: None.

I-2.11. 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.

I-2.12. 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.

I-2.13. 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 business 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 cost proposal. If applicable, an individual subcontracting plan shall be submitted along with the master subcontracting plan. The subcontracting plan is a part of the cost proposal and will not be included in the page count.

II. ELIGIBILITY INFORMATION:

II-1. Eligible Offeror/Applicants:

Foreign or foreign-owned firms are precluded from proposing.

II-2. Access to Restricted Technical Information:

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 to the Contracting Point of Contact (CPOC) for verification.

III. PROPOSAL APPLICATION AND SUBMISSION INFORMATION:

III-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-7016, Rights in Bid or Proposal Information (JAN 2011). 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.

III-2. Proposal/White Paper Validity Period

Offerors must state, on the cover page of each volume of their proposal(s) or white paper(s), that their proposal is valid for at least 180 days from submission. Any proposal received that does not include this information in the specified location will be assumed valid for 360 days from the submission date. Proposals submitted shall be in accordance with this announcement.

III-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 Wide Point of Enter (i.e. the Federal Business Opportunities website, http://www.fbo.gov).

III-4. BAA Guide:

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

III-5. Supplemental Information Package:

A supplemental information package describing the specifics of the RP21 goals and government baseline is available to potential offerors who are authorized to receive restricted technical information (see II-2). The supplemental information package also includes a more complete bibliography to help define state-of-the-art. This supplemental package contains information that will assist offerors in understanding the RP21 goals and may aid in developing a quality proposal. To receive supplemental package(s), submit a letter of your request to all contracting points of contact as follows: Ms. Cynthia Randall, cynthia.randall@us.af.mil; Mr. Richard Barzaghi richard.barzaghi@us.af.mil;

Ms. Judy Gayler judy.gayler@us.af.mil; and Mr. Timothy Palen timothy.palen@us.af.mil. Include your organization’s cage code with the request.

IV. AWARD ADMINISTRATION INFORMATION:

IV-1. One-Step Process:

The one-step process is used to request full technical and cost proposals from each offeror. The proposals are evaluated in accordance with the solicitation criteria, and all of a selected proposal, part of a selected proposal, or none of the proposals are selected.

IV-2. Two-Step Process:

The two-step process is sometimes used when a large number of proposals are anticipated. Potential offerors are invited to submit brief descriptive white papers in lieu of full proposals. The individual BAA call will state whether an unfavorable white paper evaluation will bar the offeror from further consideration. Full proposals are requested from those offerors selected in the white paper evaluation process. When proposals are received, they are evaluated and selected.

IV-3. Closed Process:

This approach allows for white paper and/or proposal submittals at a specified date and time as set forth in the BAA. Late white paper and proposal provisions (IAW FAR 52.215-1(c)(3)) are usually included in the BAA.

IV-4. Awarding of Contracts:

The Government intends to evaluate white paper/proposals to award, part, some, all, or none of the white papers/proposals received without negotiations/discussions; however, the Government reserves the right to negotiate with offeror(s) whose proposal(s) is(are) selected for funding.

IV-5. White Paper Selection:

If call utilized a two-step process, offerors will be notified whether their white paper(s) is (are) selected to submit a full proposal(s) by letter or e-mail. The notification is not to be construed to mean the award of a contract is assured, as availability of funds, selection of full proposal, and if necessary, successful negotiations are prerequisites to any award.

IV-6. Award Notices:

Offerors will be notified whether their proposal is recommended for award, by letter or e-mail. The notification is not to be construed to mean the award of a contract is assured, as availability of funds and if necessary, successful negotiations are prerequisites to any award.

IV-7. Proposal Categories:

IV-7.1. Category I: Proposal is well conceived, scientifically and technically sound, pertinent to the program goals and objectives, and offered by a responsible contractor with the competent scientific and technical staff and supporting resources needed to ensure satisfactory program results. Proposals in Category I are recommended for acceptance (subject to availability of funds) and normally are displaced only by other Category I proposals.

IV-7.2. Category II: Proposal is scientifically or technically sound but may require further development and is recommended for acceptance, but at a lower priority than Category I.

IV-7.3. Category III: Proposal is not technically sound or does not meet agency needs.

Proposals in Category III are recommended for rejection, except as identified in BAA section IV-8.

IV-8. Sequence of Awards:

Only proposals receiving a rating of Category I or II will be eligible for selection for funding and award. Category I proposals are recommended for acceptance and normally will be displaced only by other Category I proposals. Category I proposals will normally be funded/awarded before a Category II proposal is selected. If there are no Category I proposals for the call, a Category II proposal may be selected for funding and award. Category II proposals are not always funded. It may be the case that while your overall proposal may be ranked Category II (or even Category III) a certain part of the proposal may be ranked Category I (or II). In this case, the flexibility of the BAA process will allow the Government to fund that portion of your proposal that is of high interest to the Government. It may also be the case that another division of the laboratory or even another agency may be interested in your proposed approach (or a portion of the proposal) and provide funds to make an award for your effort. Once again, the flexibility of this process allows us to make awards in these instances.

Category III proposals, with the exception of certain parts of the proposal (as described above), are recommended for rejection.

V. AGENCY CONTACTS:

Any correspondence must reference the BAA title and number. Correspondence is preferred in email over all other methods.

V-1. Technical Point of Contact (TPOC):

Questions of a technical nature shall be directed to the Technical Point of Contact (TPOC), as specified below:

Name: Dr Erik Weber Address: AFRL/RQRM 4 Draco Drive, Bldg 8351 Edwards AFB, CA 93524 Telephone: 661-275-5004 Email: erik.weber@us.af.mil

V-2. Contracting Points of Contact (CPOC):

Questions of a contractual/business nature shall be directed to the contracting office, as specified below:

Contracting Officer

Name: Ms. Judy Gayler Address: AFTC/PZRA 5 South Wolfe Avenue, Bldg 2800 Edwards AFB, CA 93524

Telephone: 661-277-7748 Fax: 661-277-0470 E-mail: judy.gayler@us.af.mil

Contract Specialist

Name: Ms. Cynthia Randall Address: AFTC/PZRA 5 South Wolfe Avenue, Bldg 2800 Edwards AFB, CA 93524 Telephone: 661-277-3986 Fax: 661-277-0470 E-mail: cynthia.randall@us.af.mil

V-3. Ombudsman:

In accordance with AFFARS 5301.91, an Ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition announcement. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the Contracting Officer listed above for resolution. AFFARS Clause 5352.201-9101 Ombudsman (Nov 2012) will be incorporated into all contracts awarded under this BAA.

The Ombudsman is as follows:

Air Force Test Center Vice Commander

1 South Rosamond Blvd Edwards AFB, CA 93524-3784 Phone: 661-277-2810 Fax: 661-277-7593 E-mail: afftc.pk.workflow@edwards.af.mil

Review AFFARs 5301.91 for further information regarding concerns, issues, disagreements, and recommendations that cannot be resolved at the Center level.

VI. OTHER INFORMATION:

VI-1. BAA Value:

The sum of all contracts awarded against this BAA shall not exceed $20M.

VI-2. Support Contractors:

Only Government personnel will evaluate the proposals for selection. AFRL/RQ-West has contracted for various business and staff support services, some of which require contractors to obtain administrative access to proprietary information submitted by other contractors. Administrative access is defined as “handling or having physical control over information for the sole purpose of accomplishing the administrative functions specified in the administrative support contract, which do not require the review, reading, or comprehension of the content of the information on the part of non-technical professionals assigned to accomplish the specified administrative tasks”. These contractors have signed general non-disclosure agreements and organizational conflict of interest statements. The required administrative access will be granted to non-technical professionals. A few examples of the administrative tasks performed include assembling and organizing information for R&D case files; accessing library files for use by Government personnel; and handling and administration of proposals, contracts, contract funding, and queries. Any objection to administrative access must be submitted/ delivered in writing to the Contracting Officer before submission of proposal and shall include a detailed statement of the basis for the objection.

VI-3. Technical Support Contractors (Post-Award)

There is the potential that contracted technical experts will be utilized after award to provide insight into specific areas of interest. Necessary arrangements would be put in place to address data rights.

VI-4. Communication:

Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. E-mail communication is highly desired. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

VI-5. Debriefings:

When requested, a debriefing will be provided. The debriefing process will follow the time guidelines set out in 10 USC 2305(b)(5).

VI-6. Wide Area Work Flow Notice:

Any contract award resulting from this announcement will contain the clause at DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports (Jun 2012), which requires electronic submission of all payment requests. The clause cites three possible electronic formats through which to submit electronic payment requests and receiving reports. Effective 01 October 2006, the Department of Defense adopted Wide Area Work Flow-Receipt and Acceptance (WAWF-RA), as the electronic format for submission of electronic payment requests. Any contract resulting from this announcement will establish a requirement to use WAWF-RA for invoicing and receipt/acceptance, and provide coding instructions applicable to this contract.

Contractors are encouraged to take advantage of available training (both web-based and through your cognizant DCMA office), and to register in the WAWF-RA system.

Information regarding WAWF-RA, including the web-based training and registration, can be found at https://wawf.eb.mil/. Note: WAWF-RA requirement does not apply to Universities that are audited by an agency other than DCAA.

VI-7. Item Identification and Valuation:

Any contract award resulting from this announcement may contain the clause at DFARS 252.211-7003, Item Identification and Valuation, (Dec 2013) which requires unique item identification and valuation of any deliverable item for which the Government’s unit acquisition cost is $5,000 or more; subassemblies, components, and parts embedded within an item valued at $5,000 or more; or items for which the Government’s unit acquisition cost is less than $5,000 when determined necessary by the requiring activity for serially managed, mission essential, or controlled inventory.

Also included are any DOD serially managed subassembly, component, or part embedded within a delivered item and the parent item that contains the embedded subassembly, component, or part. Per DFARS 211.274-3 policy for valuation, it is DoD policy that contractors shall be required to identify the Government’s unit acquisition cost for all items delivered, even if none of the criteria for placing a unique item identification mark applies. Therefore, your proposal must clearly break out the unit acquisition cost for any deliverable items. Per DFARS 211.274-3 policy for valuation, “the Government’s unit acquisition cost is the contractor’s estimated fully burdened unit cost at time of delivery to the Government for cost type or undefinitized line, subline, or exhibit line items” (per DoD, “fully burdened unit costs” to the Government would include all Direct, Indirect, G&A costs, and an appropriate portion of fee). If you have questions regarding the unique item identification requirements, please contact the contracting point of contact listed above. For more information, see the following website: http://www.acq.osd.mil/dpap/pdi/uid/.

VI-8. Forward Pricing Rate Agreements:

Offerors who have forward pricing rate agreements (FPRA’s) and forward pricing rate recommendations (FPRR’s) should submit them with their proposal.

VI-9. Pre-Award Clearance:

Pursuant to FAR 22.805, a pre-award clearance must be obtained from the U.S.

Department Of Labor, Employment Standards Administration, Office Of Federal Contract Compliance Program’s (OFCCP) prior to award of a contract (or subcontract) of $10,000,000 or more unless the contractor is listed in OFCCP’s National Pre-award Registry http://www.dol-esa.gov/preaward. This registry indicates that the contractor has been found to be “in compliance” within the past two years with The Equal Employment Opportunity (EEO) regulations that the OFCCP is mandated to enforce.

The registry is updated nightly and facilities reviewed more than 2 years ago are removed and new ones are added. Award may be delayed if you are not currently listed in the registry and the contracting officer must request a pre-award clearance from the

OFCCP.

VI-10. Excessive Pass-Through Charges:

Any contract award resulting from this announcement may contain the clause at FAR 52.215-23, Limitations on Pass – Through Charges (Oct 2009) which requires the contractor to identify in its proposal the percentage of effort to be performed by the prime contractor and the percentage expected to be performed by each subcontractor.

If the contractor intends to subcontract more than 70% of the total cost of work under the contract, then it shall identify the amount of the contractor's indirect costs and profit applicable to the subcontract work, and a description of the value added by the contractor. If any subcontractor intends to subcontract to a lower tier subcontractor more than 70% of the total cost of its work, then it shall identify the amount of the subcontractor's indirect costs and profit applicable to the lower tier subcontract work, and a description of the value added by the subcontractor.

VI-11. Associate Contractor Agreements:

Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contract projects that specify requirements for them to share information, data, technical knowledge, expertise, or resources. The Contracting Officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources, or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the Contracting Officer will identify associate contractors with whom agreements are required. ACA are anticipated due to the multiple award nature of the contract to share information, data, and some technical knowledge. The language from AFFARS IG IG5317.9000 (2013), Associate Contract Agreements or similar language should be included in the Statement of Work

VI-12. Post-Award Small Business Program Re-representation:

As prescribed in FAR 19.308, FAR Clause 52.219-28, “Post-Award Small Business Program Re-representation (July 2013),” is incorporated by reference in this solicitation.

This clause will be contained in any contracts resulting from this solicitation. This clause requires a contractor to re-represent its size status when certain conditions apply. The clause provides detail on when the re-representation must be complete and what the contractor must do when a re-representation is required.

VI-13. Future Calls:

Future call(s) are anticipated on this BAA. The future call may have addition, reduction, or modification of subtopics and/or requirements. Contractor who did not propose or were not awarded in any call can propose the same or new effort in later calls.

VI-14. Technology Readiness Levels (TRL)

TRL as defined in the Technology Readiness Assessment (TRA) Guidance (Apr 2011) at http://www.acq.osd.mil/ddre/publications/docs/TRA2011.pdf will be used in this BAA.

VII. Bibliography

A more complete bibliography is available from the contracting office upon verification of eligibility and request (see III-5).

1. Le, Anhduong; Sun, L; and Miller, Timothy, Detectability of Delaminations in Solid Rocket Motors with Embedded Stress Sensors, AFRL-RZ-ED-JA-2011-415, Air Force Research Laboratory, Edwards AFB, CA, Oct 2011

2. Oberkampf, W. L. and Barone, M. F., Measures of agreement between computational and experiment: Validation metrics, Journal of Computational Physics. 217(1), 5-36 (2006).

3. Ruderman, Gregory; Health Management Issues and Strategy for Air Force Missiles, AFRL-PR-ED-TP-2005-272, AFRL, Edwards AFB, CA, Nov 2005

4. Logan, R., and Nitta C., Comparing 10 Methods for Solution Verification, and Linking to Model Validation, UCRL-TR-210837, University of California, Livermore, CA, Mar 2005

5. Chelner, Herbert; Embedded Sensor Technology for Solid Rocket Motor Health Monitoring, ADA405070, Micron Instruments, Simi Valley, CA, July 2002

BROAD AGENCY ANNOUNCEMENT

CALL 1

BAA-RQR-2014-0002

21 April 2014

I. CALL 1 DESCRIPTION

I-1. A&S Technology Development Requirements:

I-1.1. Technology Development Objectives: This effort focuses on developing technologies including physics-based models and embedded sensor analysis technologies to meet the RP21 A&S goals. These technologies will appreciably increase our detection, prediction, and/or understanding of aging in SRMs and their safe operation.

I-1.2. All technology development efforts shall:

I-1.2.1. Illustrate reduction of reliance on dissection of motors and depot operations to determine asset viability, and logically lead to the ability to predict the lifetime of an individual solid rocket motor with greater fidelity

I-1.2.2. Primarily apply to large scale monolithic and segmented SRMs such as may be used for strategic, space launch, and ballistic missile systems, and ideally to tactical missile systems with minimal alterations

I-1.2.3. Designed for use in environments for tactical and strategic missile systems to include, but not limited to, manufacturing, operational (for example: cyclic temperatures, vibrational loads, wind shear), motor handling, storage, and transport

I-1.2.4. Be designed taking into account other factors to include, but not limited to, size constraints, data transfer, and other operational constraints

I-1.2.5. Surpass accuracy of previously funded efforts (for example: Service Life Prediction Technology [SLPT], Critical Defect Assessment [CDA], Sensors and Applications Modeling [SAM], Non-Destructive Evaluation Data Processing [NDE-DP], and various Advance Missile Propulsion Technology [AMPT] and Missile Component Advanced Technology [MCAT] Task Orders) in the area of SRM health modeling including, but not limited to, AFRL funded efforts (references are included in supplemental information package refer to BAA section III-5)

I-1.2.6. Develop individual technology derived requirements from program requirements and methods to verify them (inspection, demonstration, test, analysis). The requirements and method are subject to approval by the integrated product team (IPT)

I-1.2.7. Exit the Call 1 technology development effort at a minimum of TRL 4

I-1.2.8. Use open, well documented, and industry accepted standards

I-1.2.9. Confirm the proposed quantifiable improvement over the current state of the art along with how much they contribute to meeting the RP21 A&S goal and any impacts to other RP21 goals (Definitions are included in supplemental information package refer to BAA section III-5)

I-1.2.10. Develop a proposed concept of operation (CONOPs) for the technology as well as the method that will be used to integrate the technology into the operational system – not just the missile but the overall weapon system

I-1.2.11. Design technology that is operable, sustainable, supportable, interoperable, modular, and reliable over the expected life time of the system for the operational users

I-1.2.12. Disseminate the results at JANNAF and/or other relevant forums

I-1.2.13. Estimate the payoffs to the operational system

I-1.2.14. Develop a plan to validate and verify technology for a future RP21 demonstration effort

I-1.3. All efforts that contain computer code/software shall:

I-1.3.1. 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.

I-1.3.2. The code shall be capable of satisfactorily completing functional user testing to include installation and operation on current DoD standard desktop configuration client or DoD server core configuration connected AFRL’s SATURN enclave.

I-1.3.3. The code shall comply with AFI 33-210 certification and accreditation to including:

I-1.3.3.1. No CAT I or II finding of Security Technical Implementation Guides

(STIG)

I-1.3.3.2. Documentation of CAT III finding of STIGs that will be recommended for risk acceptance and the reasoning

I-1.4. Subtopic 1 Requirements: Physics-based modeling and their validation and verification All the modeling efforts shall:

I-1.4.1. Clearly define sources of error

I-1.4.2. Perform a detailed uncertainty and sensitivity analysis of the model

I-1.4.3. Develop a usable and highly automated code for distribution to the Government and their contractors

I-1.4.4. Develop a code usable on a high power workstation – either Linux or Windows based

I-1.4.5. Develop and document the necessary inputs for models throughout the life of the system including test methods for all modeling efforts

I-1.4.6. Document all outputs from the codes

I-1.4.7. Validate and verify codes (ref. 2 and 4), including development of experimental techniques as necessary

I-1.5. Subtopic 2 Requirements: Embedded sensors for propellant, liner, and insulation (PLI) flaw detection analysis Develop a design methodology to determine the necessary number and location of embedded sensors to detect propellant, liner, and insulation (PLI) flaws’ (separations, cracks, bubbles, and inclusions) size, location, and development, as well as the uncertainty associated with each measurement. Also, develop an analysis methodology to use sensor data to determine flaw size and location with respective uncertainties in order to provide actionable information. The system needs to do more than simply notify the user that a change has occurred; it needs to provide a starting point for other investigative techniques at a minimum, and ideally, the system will determine the flaws’ size, severity, growth potential, and location. This effort should be focused on model development utilizing previously developed solid rocket motor sensor technologies without significant manufacturing and/or physical demonstration. All efforts in this area shall:

I-1.5.1. Develop a method to determine the necessary number and location of embedded sensors to detect propellant flaws’ size, location, and development, as well as the uncertainty associated with each measurement

I-1.5.2. Develop automated method for analyzing sensor data to determine flaw’s current size and location

I-1.5.3. Develop automated method to address the effects of aging, temperature, humidity, and other environmental factors on what the sensor measures and the system’s predictions

I-1.5.4. Develop sensor placement plan for representative motors (representing a range of possible configurations) and analytically assess configuration’s flaw detection capability

I-1.5.5. Assess the impact of embedded sensors on the motor integrity, longevity, safety margins, performance, and inert weight

I-1.5.6. Determine effects of a failure of one or more sensors on the system, and any redundancy necessary

I-1.5.7. Determine the analytical uncertainty associated with each step in the measurement and automated analysis. An output of the automated analysis should be the total uncertainty magnitude

I-1.5.8. Theoretically investigate the means and manufacturing methodology by which the embedded sensor data will be transferred out of the motor without violating any safety, security standards, or other relevant regulations (e.g.

Explosive Operating Instructions [EOIs], Hazards of Electromagnetic Radiation to Ordnance [HERO])

I-1.5.9. Theoretically investigate the long-term viability of embedded sensor system (drift, tin whiskers, failure state …)

I-1.5.10. Be capable of handling and evaluating as many flaws as there are in any given motor

I-1.5.11. Not entail development of sensing technologies

I-2. Deliverable Items:

Any contract awards resulting from this call shall be required to deliver appropriate data items; and possibly software and hardware.

I-2.1. Data Requirements:

I-2.1.1. ALL program technical and financial progress shall be reported. The baseline Contract Data Requirements List (CDRL) list is provided in Table 1. The items below or similar items shall be incorporated into each proposed effort as applicable. Relevant CDRL items shall then be incorporated into each effort.

The Data Item Descriptions (DID) are given as references only. All reports are to be divided into sections with appropriate markings for distinguishing proprietary versus non-proprietary information.

I-2.1.2. Offerors are encouraged to propose an alternate CDRL list adding or deleting any of the items shown below for Government consideration and approval. If an alternate CDRL is proposed, the offeror must demonstrate the benefits of using the alternate. Contractor’s format and report consolidation are highly encouraged and may be acceptable upon request. 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 shall be required on individual efforts. The model contract will contain Exhibits A and B for complete requirements.

Table 1: Sample Contract Data Requirements List (CDRL) CDRL Authority Description Frequency A001 DI-ADMN-81373/T Presentation Material As Required A002 DI-MGMT-81468/T Contract Funds Status Report (CFSR) Quarterly A003 DI-FNCL-80331A/T Funds and Man-Hour Report (FMHR) Monthly A004 DI-MGMT-80227/T Contractor’s Progress, Status & Management Report Monthly

A005 DI-SESS-81785/T Systems Engineering Management Plan (SEMP) Once &

Revisions A006 DI-MISC-80711A/T Scientific and Technical Reports, Subtitle Interim Report As required *(1)

B001 DI-MISC-80711A/T Scientific and Technical Reports, Subtitle Final Report Once & Revision

B002 DI-IPSC-81443A/T Software User Manual Once, if necessary

B003 DI-SESS-81002E/T

Developmental Design Drawings/Models and Associated

Lists Once, if necessary *Notes

(1) CDRL A006 will be submitted annually and at the end of the technical effort.

I-2.1.3. Interim and Final Report: Interim Reports will be submitted annually, due every 12 months to the day from the beginning of the technical effort, and submitted on the day of the end of the technical effort. The last interim report (submitted at the end of the technical effort) will be reviewed by the Government, but subsequent submission of a camera-ready version will not be required. The final report firm fixed price effort will commence at the end of the technical effort and will be used to generate an acceptable Final report.

I-2.1.4. Residual Hardware: Residual hardware deliveries may be required. If applicable, residual hardware will be identified for individual efforts and delivered to AFRL/RQRM upon the completion of the technical effort. Delivery due thirty days after end of technical effort of each contract if there is residual hardware developed.

I-2.1.5. Software: All efforts that develop computer code shall deliver the source and compiled code thirty days after end of technical effort of each contract.

I-3. Schedule:

The anticipated period of performance for contracts resulting from this call CLIN 0001 or CLIN 0002 is twelve to thirty-six months technical effort, plus 90 days for the Final Scientific and Technical Reporting Cycle.

I-4. Other Information:

I-4.1. 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 A001.

I-4.2. 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 must be identified in the proposal for each effort. If proposing GFP or GFI 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 and RP21.

I-4.3. Contractor Acquired Property: None anticipated.

I-4.4. Base support: None anticipated.

II. AWARD INFORMATION:

II-1. Anticipated Funding:

II-1.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.

II-1.2. Funding Profile: The anticipated funding profile for this call is provided in Table 2.

The split between subtopics is notional and the budget will be managed to the topic level. The values provided are for all efforts and not per award.

II-1.3. Funding Per Effort: It is anticipated that all efforts resulting from this call will be between $500,000 and $1,000,000. Efforts that are less than or greater than this range should provide additional justification.

Table 2: Anticipated Call 1 Funding Profile (all values in $1000s) A&S Topic Title FY14 FY15 FY16 FY17 Total

Call 1 Tech

Developments $120 $1,900 $300 $680 $3,000

1.1 Physics-Based

Models $80 $1,444 $200 $376 $2,100

1.2 Analysis for

embedded sensor flaw detection

$40 $456 $100 $304 $900

II-2. Type of Contracts/Instruments:

The Government anticipates awarding Cost-Plus-Fixed-Fee (CPFF) type contract(s) from proposals 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.

II-3. Discussions:

The Government intends to evaluate proposals and award, part, some, all, or none of the proposals received without negotiations/discussions; however, the Government reserves the right to negotiate with offeror(s) whose proposal(s) is(are) selected for funding.

II-4. Anticipated Award Date:

The first contract is anticipated to be awarded on 13 November 2014.

III. PROPOSAL APPLICATION AND SUBMISSION INFORMATION:

III-1. Content and Form of Submission for Proposals:

Offerors must submit one-original with four additional hard copies, and two electronic (CD) copies of their proposal(s) 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.

III-1.1. Proposal Contents: One (1) technical, one (1) management, and one (1) price volume

III-1.2. Required Format: Proposals are to be on 8.5x11 inch pages with one (1) inch margins on all sides. Headers, footers, and page number can be in the margins, but the margins must contain no substantial information. 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 not evaluated, 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. If another font, font size, or paragraph spacing is utilized, a conversion factor will be determined and amount over the limit will be removed. For example if 9pt Calibri font is utilized when expanded the 8 pages paper would be 11 7/19 pages long so 3 7/19 pages or 29.7% would be removed. The remaining document would then be evaluated as is. Any figures need to utilize 11 point or larger font to the greatest extent possible, and not be utilized for adding narrative at a smaller size. If evaluation team deems that, a figure is being used to add narrative, it will not be evaluated. Any figure must be discussed in the text;

otherwise, it will not be evaluated. If any item is illegible to the evaluation team, it will not be considered. A cover sheet shall be included on the top of each volume with the information from section call 1 section III-1.2.1 and the cover sheet is not included in the page count. 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 the proposal will be returned unevaluated. Appendixes shall follow these format requirements and are subject to the same controls, unless stated.

III-1.2.1. A cover sheet shall be included before each volume with the following information:

III-1.2.1.1. Title of proposal

III-1.2.1.2. Volume title

III-1.2.1.3. Full company name and address

III-1.2.1.4. BAA number submitting proposal against

III-1.2.1.5. Subtopic proposing to

III-1.2.1.6. Point of contact, name, title, phone, and fax number

III-1.2.1.7. CAGE code

III-1.2.1.8. DUNS number

III-1.2.1.9. Type of contract proposed (e.g. CPFF, FFP)

III-1.2.1.10. Name, address, and phone number of administration (DCMA) office

III-1.2.1.11. Name, address, and phone number of audit (DCAA) office

III-1.2.1.12. Validity period in accordance with BAA section III-2

III-1.2.1.13. Appropriate markings (ITAR, destruction, competition sensitive)

III-1.3. Number of proposals: Up to two total proposals can be submitted for this call, if more than that is provided the extras will be removed at random. This does not mean only one proposal for each topic, two proposal could be provided for either topic and none for the other. For other calls of this BAA, the number of proposals will be determined at the release of the individual call.

III-1.4. Technical Volume

III-1.4.1. Technical Volume Contents: Identify how the proposed technology along with necessary components will be developed to appreciably improve knowledge of an individual SRM’s health and reduce uncertainty in the service life estimate. The technical volume shall give a description of the technology to be developed; it shall also describe how the technology will meet the technical area requirements (For example: 1. Physics-based models needs to meet requirements in BAA section I-1 and I-2; and call 1 sections I-1.1, I-1.2, I-1.3, I-1.4, and I-2. 2. Embedded sensor analysis needs to meet requirements in BAA section I-1 and I-2; and call 1 sections I-1.1, I-1.2, I-1.3, I-1.5, and I-2).

Briefly summarize previous efforts in this area. Define how the proposed project will improve upon the state-of-the-art and meet the…