FA8650-18-S-1672-BAA.pdf

1-Step Broad Agency Announcement

Overview Information To access hyperlinks from this electronic solicitation – Hit CTRL and click on the link.

NAICS Code: The NAICS Code for this acquisition is 541715 (Research and Technology in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology), and the small business size standard is 1,000 employees.

Federal Agency Name: Air Force Research Laboratory, AFRL/RYZT Sensors Directorate

Broad Agency Announcement Title: Precision Real-time Engagement Combat Identification Sensor Exploitation (PRECISE)

Broad Agency Announcement Type: Initial Announcement

Broad Agency Announcement Number: FA8650-18-S-1672

Catalog of Federal Domestic Assistance (CFDA) Number(s): N/A

Intent to Propose: Offerors that anticipate submitting a proposal are requested to submit an e-mail to Anar Wagner, at anar.wagner@us.af.mil and Bryan Fleckenstein at bryan.fleckenstein@us.af.mil containing the name of the contractor, the POC, and the contractor’s intent to submit a proposal. This “Intent to Propose” is requested by 09 April 2018, 2:00 p.m. local time.

Proposal Due Date and Time: 23 April 2018, 2:00 p.m. Wright-Patterson AFB, OH, local time. NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late.” Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Be advised, if the U.S. Postal Service is used, this building only receives U.S. Postal Mail twice a week and delivery by that means may not meet the proposal due date and time. Early proposal submission is encouraged.

Submission: Proposals must be submitted to the Contracting Point of Contact

(POC):

Mr. Barry Kain, AFRL/RQKSR phone: 937-713-9986 Bldg. 45, 2130 8th St.

Wright-Patterson AFB, OH 45433-7541 mailto:anar.wagner@us.af.mil mailto:bryan.fleckenstein@us.af.mil

Solicitation Request: Air Force Research Laboratory, AFRL/RY Sensors Directorate, AFRL/RYZT Advanced Plans and Programs Division, AFRL/RYZT Advanced Programs Branch, Wright Patterson Air Force Base is soliciting technical and cost proposals on the research effort described below.

Type of Contract/Instrument: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the FAR or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research.

The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this BAA will generally be Cost Plus Fixed Fee. Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.)

Estimated Program Cost: $33.6M

Anticipated Number of Awards: The Air Force anticipates awarding two awards for this announcement. However, the Air Force reserves the right to award zero, one, or more contracts for all, some or none of the solicited effort based on the offeror’s ability to perform desired work and funding fluctuations.

Brief Program Summary: This program – the Precision Real-Time Engagement Combat Identification Sensor Exploitation (PRECISE) program – will primarily develop technologies that continue to advance combat ID for warfighters.

PRECISE will leverage current efforts supporting the Air to Air Hydravision program, and is principally focused on radar-based identification of air and ground targets for airborne platforms, both tactical and reconnaissance. The effort may investigate other sensors to include electro-optical, infrared, and multi- and hyperspectral. Improvements in these areas may involve and include technical assessments, prototype hardware and software modifications and development, systems engineering development, performance simulations, system integration, laboratory demonstrations, flight demonstrations, and participation in large demonstrations/ exercises.

Communication Between Prospective Offerors and Government Representatives:

Questions and open discussions from prospective offerors to Government representatives is encouraged until submission of proposals. The government contracting POC for communications is Bryan Fleckenstein (see contact info below).

Technical questions to the technical POC, Mr. Andrew Freeman (see contact info below), are also encouraged; however no guidance will be given regarding technical approach. 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.

Government responses will be consolidated and posted to Fed Biz Opps during the BAA open period.

Address technical questions to the Technical POC:

Mr. Andrew Freeman, AFRL/RYZT 2241 Avionics Circle, Bldg. 620

WPAFB OH 45433

Phone: (937) 713-8158 Email: andrew.freeman.6@us.af.mil

Address contracting questions to the Contracting POC:

Mr. Bryan Fleckenstein, AFRL/RQKSR 2130 8th St., Bldg. 45

WPAFB OH 45433

Phone: (937) 713-9982 Email: bryan.fleckenstein@us.af.mil

Mr. Barry Kain 2130 8th St., Bldg. 45

WPAFB OH 45433

Phone: (937) 713-9986 Email: barry.kain@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Sensors Directorate

(AFRL/RYZT) is soliciting technical and cost proposals on the following research effort:

1. Statement of Objective/Description of Technical Area(s): refer to attached SOO (Attachment 1 to Model Contract)

2. Within Scope Modifications: Potential offerors are advised that due to the inherent uncertainty of research and development efforts, awards resulting from this announcement may be modified during performance to make within scope changes, to include but not limited to, modifications which increase overall contract ceiling amount.

3. Deliverable Items:

a. Data Items: See attached DD Form 1423-1 CDRLS (Exhibit A of the Model Contract).

b. Software: The contractor shall procure software to include Commercial off the Shelf (COTS) software if not available through government channels and required for the performance of this program. The contractor shall deliver all software developed under this contract with unlimited data rights. Any mailto:bryan.fleckenstein@us.af.mil mailto:barry.kain@us.af.mil commercial software furnished shall be acquired with customary license rights. Delivery of the software can be tailored to allow contractor’s format.

c. Hardware/Materials/Residual Materials: The contractor shall procure/deliver special test equipment needed for demonstration and test if not available through government channels. In addition the contractor shall procure materials if they are not available through government channels and are required for the performance of this program. The contractor shall deliver all developed and acquired hardware, equipment and non-consumed materials developed under this contract. Unique Identification (UID) may apply.

4. Schedule:

a. Overall effort: 63 months (60 months to complete the technical and programmatic R&D portion and 3 additional months for preparation of the final technical report.)

b. Data Items: Specified on individual CDRL(s)

c. Software: 30 November 2023 (anticipated)

d. Hardware/Materials/Residual Materials: 30 November 2023 (anticipated)

5. Other Requirements:

a. This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at http://farsite.hill.af.mil/

b. Program security classification: Secret., Offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil. Please reference the DD254, Attachment 2 of the Model Contract

c. OPSEC: See attached SOO for OPSEC guidance.

d. Export Control: Information involved in this research will be subject to

Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774).

If effort may be subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

f. Export-Controlled Items: As prescribed by DFARS 225.7901-4, DFARS 252.225-7048, “Export-Controlled Item (JUN 2013)” is contained in this solicitation. This clause shall be contained in ALL resulting contracts.

6. Other Information:

Government Furnished Property (GFP) is not anticipated to be made available under any resulting contract.

a. Base Support/ Network Access: N/A

b. Multiple awards subject to Fair Opportunity are not anticipated.

c. Data Rights Desired:

http://farsite.hill.af.mil/ http://www.dss.mil/

(1) Technical Data: Unlimited Rights

(2) Non-Commercial Software (NCS): Unlimited Rights

(3) NCS Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary License

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in technical data and NCS developed or delivered under this contract are of significant concern to the Government. The Government will therefore carefully consider any restrictions on the use of technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology.

In exchange for paying for development of the data, the Government expects technical data, 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 at least Government Purpose Rights. Offers that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how the data was developed at private expense. Specifically, offers must explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable.

Offerors that propose delivery of technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License Rights will be considered. Proposals should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated and how the incorporation will benefit the program and whether those portions or processes are segregable.

Offerors shall include the data rights assertions as required by DFARS 252.227-7017, Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. The assertions list is included in Section K and due at time of proposals. Assertions must be completed with specificity. Each assertion must identify both the data and each such item, component, or process listed. Nonconforming assertions lists will be rejected.

Terms used in this section are defined in the clauses at 252.227-7013, Rights in Technical Data-Noncommercial Items, and 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.

THIRD PARTY SOFTWARE (COMMERCIAL AND NONCOMMERCIAL):

DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software. Any third party software (commercial and noncommercial) to be incorporated into a deliverable must be clearly identified in the proposal. Prior to delivery of any third party software, the contractor will obtain an appropriate license for the Government, and the written approval of the contracting officer.

Any third party software to be delivered to the Government that are not reasonably identifiable at proposal submission, must still be approved by the contracting officer prior to incorporation into a system deliverable.

This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

The Government will neither accept nor execute a DD Form 250 for the software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses that comply with the following terms and conditions for the Government (Licensee):

1. The license shall not subject the Government to liability that is indefinite or indeterminate, such as an indemnification clause, as it would constitute an obligation in advance or in excess of an appropriation and violate the Anti-Deficiency Act.

2. The license shall not create a contingent liability for the Government.

This includes, but is not limited to: unilateral price increases, automatic assessment of charges, and automatic renewal of the license.

3. The license shall be governed by Federal Statutes, Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country.

4. The license shall not include non-substitution language that would preclude or limit the Government from using another vendor/reseller and/or product to fulfill Government requirements.

5. The license shall not comment on entitlement to attorney fees.

6. The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes Clause in the underlying basic contract.

7. The Licensor shall not have the right to enter the premise or monitor the networks of Licensee for the purpose of auditing the use of the license.

8. The Licensor shall not use any injunctive relief clauses as the Licensor cannot prevent the Licensee from performing mission operations.

9. The Licensor shall not have the authority to control any litigation between a third party and the Licensee.

10. The Licensor shall not use the fact that the Licensee is using the Licensor's products in any notification to the public (e.g., no publicity rights permitted).

[IF APPLICABLE] Additionally, the Contractor may be required to obtain licenses that comply with the following terms and conditions, based on the Government’s needs:

1. [IF APPLICABLE] The license shall not disclaim all warranties through use of an “as is” provision.

2. [IF APPLICABLE] The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the [PROGRAM NAME]. In performance of the [PROGRAM NAME], Government personnel as well as Government contractors may use the software.

3. [IF APPLICABLE] [The license shall not limit the Government’s use of the software at other Government and Government contractor sites.] [The license shall authorize the Government to use the software at the following sites: [list]].

4. [IF APPLICABLE] The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

5. [IF APPLICABLE] The Licensee shall not be restricted from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

The Contractor may obtain agreement from the Licensor to insert the clause below to its respective software licenses intended to be transferred to the Government:

“In the event that any of the provisions of the [Software License] are determined to be inconsistent with Federal law and/or do not otherwise satisfy the Government's needs, the parties to the [Software License] hereby agree that such provisions shall be null and void as they pertain to the Government. Specifically, the following sections are hereby deleted from the [Software License] [and/or amended as indicated below]:

[Section X: deleted; Section Y: amended as follows […]”

If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license and such use will not subject the Government to the terms of the license.

The Contractor shall provide documentation to clearly correlate or map software license(s) to:

a) Contract Line Item Numbers (CLINS);

b) Contract Deliverables (CDRLS);

c) Paragraphs in the statement of work (SOW); and

d) Portions of any functional block diagrams and/or system architecture diagrams, so that it can be readily determined where certain commercial software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

II. Award Information

1. Anticipated Award Date: 30 August 2018

2. Anticipated funding for the program (not per contract) FY18 $2.6M; FY19

$7.2M; FY20 $7.6M; FY21 $7.6M; FY22 $6.6M; FY23 $2M ($33.6M total) This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

III. Eligibility Information

1. Eligible Offeror: This is an unrestricted solicitation. Small businesses are encouraged to propose.

2. Cost Sharing or Matching: Cost Sharing is not required.

3. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (FFRDCs) contemplating submitting a proposal, as either a prime or subcontractor. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS

235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a solicitation. However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, AFRL must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made, would a determination be made concerning the FFRDC’s eligibility to receive an award.

4. Government Agencies: If a Government agency is interested in performing work, contact the technical POC identified in the BAA. If those discussions result in a mutual interest to pursue your agency's participation, the effort will be pursued independent of this announcement.

5. Other:

a. Foreign participation: Foreign Nationals (FNs) can be employed by the US

Prime Contractor or Subcontractor, however, FNs will be limited to Public Domain information unless the contractor has obtained the proper License or Technical Assistance Agreement that authorizes disclosure of Classified Military Information (CMI) and/or Controlled Unclassified Information (CUI) to foreign entities pursuant to the Department of State’s ITAR or Department of Commerce’s EAR. Public Domain information is defined as information that is releasable to the general public and sometimes referred to as open source material. Any proprietary information will be appropriately protected.

b. This acquisition involves data that are subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Services Center (DLSC) and have a legitimate business purpose may participate in this solicitation. Contact the Defense Logistics Services Center, 74 Washington Avenue N., Battle Creek, Michigan 40917-3084 (1-800-352-3572) for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your proposal.

c. There are no limits on the number of proposals an offeror may submit.

d. You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date as identified above.

IV. Proposal and Submission Information

1. Overview: Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement. The Government intends to review proposals and award some, all, or none of the proposals received without negotiation/discussion;

however, the Government reserves the right to negotiate with those offeror(s) whose proposal is selected for funding.

Offerors should be alert for any BAA amendments that may change proposal requirements or permit extensions to the proposal submission date.

http://www.dlis.dla.mil/jcp/

For additional information, a copy of the Broad Agency Announcement (BAA) Guide for Industry is located at http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf?

2. Content and Form of Proposal Submission: The paragraphs below identify proposal format and content.

a. General Instructions:

i. Offerors should apply the restrictive notice prescribed in FAR 52.215- 1(e) Instructions to Offerors—Competitive Acquisition. Offerors should consider proposal instructions contained in the Broad Agency Announcement (BAA) Guide for Industry, which can be accessed on line at http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf?

This guide is specifically designed to assist the offeror in understanding the BAA proposal process.

ii. Technical/management and cost/business volumes should be submitted in separate volumes and must be valid for 180 days.

iii. Proposals must reference the announcement number FA8650-18-S- 1672.

iv. Offerors must submit one-original and 4 hard copies of their proposals to the Contracting POC.

v. Offerors must include 2 CDs in Microsoft Office or Adobe format containing all electronic versions of required submittals. All electronic versions must match the hard copies.

a) The cost file(s) spreadsheets must be in Microsoft Excel and include the formulas for calculating cost element bases (i.e., G&A, O/H, etc.)

b) The CDs should be labeled with the company name and proposal title.

vi. Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

vii. The cost of preparing proposals in response to this BAA is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

viii. No classified technical proposals or cost volumes are expected.

Offerors are encouraged to keep all elements of the proposal package unclassified. In the case where an offeror has a need to submit a classified appendix, please contact the technical POC for delivery instructions.

http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf

b. Technical/Management Proposal:

i. Page Limitations: The following describes proposal page limitations:

a) The Technical/Management Proposal shall be limited to 30 pages.

Technical/Management proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

b) Font shall be standard 10-point business font Arial.

c) Character spacing must be “normal,” not condensed in any manner.

d) Pages shall be double-spaced (must use standard double-space function in Microsoft Word), double sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

e) All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

f) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 30. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc.

g) The proposal page limit does not include the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to 4 pages.

h) Please Note: The Government will check the proposal and SOW for conformance to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered for review purposes.

ii. The Technical/Management proposal(s) shall include a discussion of the nature and scope of the research and the technical approach.

Additional information on prior work in this area, descriptions of available equipment, use of base support (if desired), data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal. (This/These) volume(s) shall/ include a SOW(s) detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation. Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced above to assist in SOW preparation. In addition to the contractor proposed SOW, a Government generated SOW attachment containing additional contracting requirements will be http://www.afrl.af.mil/contract/default.htm http://www.afrl.af.mil/contract/default.htm included in any resulting contracts. The SOW attachment is included as Attachment 3 to the Model Contract.

iii. Any questions concerning the technical proposal or SOW preparation shall be referred to the Technical POC.

c. Cost/Business Proposal:

i. Separate the proposal into a business section and cost section.

Adequate price competition is anticipated.

a) See Attachment 1 for the Model Contract(s) Note that the document awarded may include contract line items (CLINs)/clauses/articles in addition to those in the model(s), and/or some of the CLIN/clauses/articles in the model(s) may be deleted, depending on the specific circumstances of the individual award. Any additions or deletions will be negotiated with the offeror prior to award.

b) The business section should contain all business aspects to the proposed contract, such as type of contract, any exceptions to terms and conditions of the announcement including the model contract, any information not technically related, etc. Provide rationale for exceptions.

c) Associate Contractor Agreements: Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that require 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.

d) Identify any technical data that will be delivered with less than unlimited rights.

e) Subcontracting Plans: For efforts to exceed $700,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) for subcontracting plan requirements. Small business concerns are exempt from this requirement. If an IDIQ contract arrangement is anticipated, the basis for the subcontracting plan should reflect the entire ceiling amount.

f) Limitations on Pass-Through Charges: As prescribed in FAR 15.408(n)(1) & 15.408(n)(2), provisions 52.215-22, “Limitations on Pass Through Charges- Identification of Subcontract Effort (Oct 2009),” apply.

g) Completed Certifications and Representations (Section K) are due with the proposal. Certifications and Representations (Section K) can be found as attachment 2 to this BAA. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal.

h) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in the BAA, the offer must specifically identify each piece of GFP in the Cost/Business Proposal and propose and substantiate a rental cost for evaluation purposes in accordance with FAR 45.202. Include the following information in the proposal:

(i) A list describing all Government property that the offeror or its subcontractors propose to use on a rent-free basis. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the contracting officer having cognizance of the property);

(ii) The dates during which the property will be used and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent;

(iii) The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges; and

(iv) The voluntary consensus standard or industry leading practices and standards to be used in the management of Government property, or existing property management plans, methods, practices, or procedures for accounting for property.

ii Cost Element Breakdown: Clear, concise, and accurate cost proposals reflect the offeror's financial plan for accomplishing the effort contained in the technical proposal. As a part of its cost proposal, the offeror shall submit the information outlined below, together with supporting breakdowns. All direct costs (labor, material, travel, computer, etc.) as well as labor and overhead rates should be provided by contractor fiscal year (CFY). Detailed cost element breakdowns by Government Fiscal Year or calendar year are not required. The supporting schedules may include summary level estimating rationale used to generate the proposed costs. The cost element breakdown(s) should include the following if applicable.

a) Direct Labor: Direct labor should be detailed by number of labor hours by category of labor.

b) Labor and Overhead Rates: Direct labor hours, with their applicable rates, must be broken out and the bases used clearly identified. The source of labor and overhead rates and all pricing factors should be identified. For instance, if a Forward Pricing Rate Agreement (FPRA) is in existence, that should be noted, along with the Administrative Contracting Officer’s (ACO's) name and telephone number. If the rates are based on current experience in your organization, provide the historical base used and clearly identify all escalation, by year, applied to derive the proposed rates. If computer usage is determined by a rate, identify the basis used and rationale used to derive the rate.

c) Material/Equipment: List all material/equipment items by type and kind with associated costs and advise if the costs are based on vendor quotes, data and/or engineering estimates; provide copies of vendor quotes and/or catalog pricing data.

d) Subcontractor Costs: Submit all subcontractor proposals and analyses with your cost proposal (See FAR 15.404-3(b)). If the subcontractor will not submit cost and pricing information to the offeror, this information must be submitted directly to the Government for analysis. On all subcontracts and interdivisional transfers, provide the method of selection used to determine the subcontractor and the proposed contract type of each subcontract.

An explanation shall be provided if the offeror proposes a different amount than that quoted by the subcontractor. The offeror’s proposal must:

(i) Identify principal items/services to be subcontracted.

(ii) Identify prospective subcontractors and the basis on which they were selected. If non-competitive, provide selected source justification

(iii) Identify the type of contractual business arrangement contemplated for the subcontract and provide rationale

(iv) Identify the basis for the subcontract costs (e.g., firm quote or engineering estimate, etc).

(v) Identify the cost or pricing data submitted by the subcontractor.

(vi) Provide an analysis of the proposed subcontract in accordance with FAR 15.404-3(b). Provide an analysis concerning the reasonableness, realism and completeness of each subcontractor’s proposal. If the analysis is based on comparison with prior prices, identify the basis on which the prior prices were determined to be reasonable. The analysis should include, but not be limited to, an analysis of: materials, labor, travel, other direct costs and proposed profit or fee rates.

e) Special Tooling or Test Equipment: When special tooling, and/or test equipment is proposed, attach a brief description of items and indicate if they are solely for the performance of this particular contract or project and if they are or are not already available in the offeror's existing facilities. Indicate quantities, unit prices, whether items are to be purchased or fabricated, whether items are of a severable nature and the basis of the price. These items may be included under Direct Material in the summary format.

f) Consultants: When consultants are proposed to be used in the performance of the contract, indicate the specific project or area in which such services are to be used. Identify each consultant, number of hours or days to be used and the consultant's rate per hour or day. State the basis of said rate and give your analysis of the acceptability of the consultant's rate.

g) Travel: Travel costs must be justified and related to the needs of the project. Identify the number of trips, the destination and purpose. Travel costs should be broken out by trip with number of travelers, airfare, per diem, lodging, etc.

h) Computer Use: Detail the amount and kind of computer usage, the cost, and how the costs were derived.

i) Facilities Capital Cost of Money: If Facilities Capital Cost of Money is proposed, a properly executed DD Form 1861 is required.

j) Project Funding Profile: Offerors should include a project funding profile by Government Fiscal Year (GFY) (1 Oct through 30 Sept) for budgetary purposes. This will enable the Government to easily identify program funding needs by GFY.

k) If an offeror takes exceptions to the requirements called out in the announcement (e.g., base support, Government-furnished property (GFP), CDRLs), the exceptions should be clearly stated in the cost proposal.

l) 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.

m) Cost/Business proposals have no page limitations.

d. Proposal Content Summary: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

V. Proposal Review Information

1. Peer or Scientific Review Criteria: Proposals will be reviewed using the criteria listed below. The technical aspect, which is ranked as the first order of priority, shall be reviewed based on the following criteria that are of equal importance.

a. Technical:

i. Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

ii. The offeror’s understanding of the scope of the technical effort.

iii. Soundness of the offeror’s technical approach including whether the proposal identifies major technical risks, clearly defines feasible mitigation efforts, and demonstrates related experience and qualifications of technical personnel.

iv. The potential to transition the research and development deliverables to future Government needs. Any proposed restriction on technical data or computer software will be considered.

b. Cost/Price: The cost/price criterion includes the realism of the proposed cost. Cost/Price is a substantial factor, but ranked as the second order of priority. (If an offeror proposes the use of GFP other than any GFP identified in this BAA, and that proposed GFP provides the offeror an unfair competitive advantage, then FAR 45.202 requires rental equivalent be applied to the Cost Factor for evaluation purposes only).

2. Review and Selection Process

a. Categories: Based on the Peer or Scientific Review, proposals will be categorized as Selectable or Not Selectable (see definitions below). The selection of one or more sources for award will be based on the Peer or Scientific Review, as well as importance to agency programs and funding availability.

i. Selectable: Proposals are recommended for acceptance if sufficient funding is available.

ii. Not Selectable: Even if sufficient funding existed, the proposal should not be funded.

Note: The Government reserves the right to award some, all, or none of proposals. When the Government elects to award only a part of a proposal, the selected part may be categorized as Selectable, though the proposal as a whole may not merit such a categorization.

b. No other criteria will be used.

c. Prior to award of a potentially successful offer, the Contracting Officer will make a determination regarding price reasonableness.

VI. Award Administration Information

1. Award Notices: Offerors will be notified whether their proposal is recommended for award on or about 1 June 2018. The notification is not to be construed to mean the award of a contract is assured, as availability of funds and successful negotiations are prerequisites to any award.

2. Administrative and National Policy Requirements: See Section I.

3. Reporting: Refer to paragraph I.3.a Deliverable Items

VII. Other Information

1. Acquisition of Commercial Items: Based upon market research, the Government is not using the policies contained in Part 12, Acquisition of Commercial Items, in this solicitation. However, interested offerors may identify to the Contracting Officer their interest and capability to satisfy the Government’s requirement with a commercial item within 15 days of this notice.

2. Support Contractors: Only Government employees will participate in Peer or Scientific Reviews. Offerors are advised that employees of commercial firms under contract to the Government may be used to administratively process proposals, monitor contract performance, or perform other administrative duties requiring access to other contractors' proprietary information. These support contracts include nondisclosure agreements prohibiting their contractor employees from disclosing any information submitted by other contractors or using such information for any purpose other than that for which it was furnished.

3. Debriefings: If a debriefing is requested in accordance with the time guidelines set out in FAR 15.505 and 15.506, a debriefing will be provided, but the debriefing content may vary to be consistent with the procedures that govern BAAs (FAR 35.016).

4. Item Unique Identification and Valuation. It is DoD policy that contractors shall be required to identify the Government’s unit acquisition cost for all deliverable end items for which Item Unique Identification applies.

Therefore, proposals must clearly break out the unit acquisition cost for any deliverable items. See DFARS 211.274-3, Policy for Valuation, for more information. (Per DoD, “fully burdened unit costs” to the Government would include all direct, indirect, G&A costs, and an appropriate portion of fee). For more information, see the following website:

http://www.acq.osd.mil/dpap/pdi/uid/index.html.

5. Pre-Award Clearance: Pursuant to FAR 22.805, a preaward 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 Preaward Registry http://www.dol-esa.gov/preaward. Award may be delayed if you are not http://www.acq.osd.mil/dpap/pdi/uid/index.html currently listed in the registry and the contracting officer must request a preaward clearance from the OFCCP.

6. Updates of Publicly Available Information Regarding Responsibility Matters: Any contract award that exceeds $550,000.00; and when offeror checked “has” in paragraph (b) of the provision FAR 52.209-7, shall contain the clause/article, FAR 52.209-9 “Updates of Publicly Available Information Regarding responsibility Matters (JUL 2013).”

7. Proposal Reminders: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

a. Proposals are due to the Contracting POC.

b. Proposals are due no later than the due date and time specified in this announcement.

c. Proposal page limits are strictly enforced.

d. The Cost/Business Proposal must contain all information described in the

Content and Form of Proposal Submission Section.

e. Offerors other than small businesses must include a subcontracting plan.

f. Proposals must be submitted in the format specified.

g. Offerors who have Forward Pricing Rate Agreements (FPRA’s) or Forward

Pricing Rate Recommendations (FPRR’s) should submit them with their proposal.

h. DD254 is applicable and offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

i. If effort is subject to export control, offerors must submit a Certified DD Form 2345, Militarily Critical Technical Data Agreement, with proposal.

http://www.dss.mil/

ATTACHMENTS

List of Attachments:

1. Model Contract

a. CDRLS (Exhibit A)

b. Statement of Objectives (SOO) (Attachment 1)

c. DD 254 (Attachment 2)

d. SOW Supplemental Requirements (Attachment 3)

e. ANSI Standard Format Guidelines (Attachment 4)

f. SF 298 (Attachment 5)

g. Payment Instruction Table (Attachment 6)

2. Section K

3. Section L