2-Step ARA_PENCAP_Final.pdf

PENCAP Advanced Research Announcement (ARA)

FA2377-26-R-B014

2-Step Advanced Research Announcement (ARA)

1.0 Overview Information

Federal Agency Name Air Force Research Laboratory, AFRL/RF, Information &

Spectrum Warfare Directorate ARA Title Precise Ensemble Network Communications Allowing Positioning, Navigation, and Timing (PNT) (PENCAP)

ARA Number FA2377-26-R-B014

ARA Type Initial Announcement

Authority This announcement is issued pursuant to 10 U.S.C. 4023

ARA Process The 2-Step Process reduces acquisition resources for both the Government and industry. It may be considered when a large number of proposals are anticipated or to determine if further Government interest is warranted. If further interest is not warranted, industry saves unnecessary bid and proposal costs, and the Government saves review time.

Intent to Propose Offerors that anticipate submitting a white paper are requested to submit an email to the agency contacts listed below in this table containing the name of the contractor, the POC, and the contractor’s intent to submit a white paper. This intent to propose is requested by 1 July 2026, 3:00pm, Eastern Daylight Time (EDT).

Step 1 White Paper Submission Due Date WHITE PAPER DUE DATE AND TIME: 17 July 2026, 3:00pm EDT. Only white papers are due at this time.

Step 2 Proposal Due Date PROPOSAL DUE DATE AND TIME: To be provided in the

Requests for Proposals sent to offerors that submit White Papers considered to meet the needs of the Air Force.

Anticipated Award Date 28 February 2027 Estimated Program Cost $9,300,000.00 Anticipated Number of Awards

The Air Force anticipates one award 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.

North American Industry Classification System (NAICS)

The NAICS Code for this acquisition is 541715 and the small business size standard is 1,000 employees.

Contract/Instrument Types

The Air Force reserves the right to award the instrument best suited to the nature of experimentation and test proposed, such as any appropriate contract type under the RFO for experimentation and test pursuant to 10 U.S.C.

4023.

Agency Contacts Gabriel Berner, Contract Specialist, AFRL/RYKSW, gabriel.berner@us.af.mil

Kathryn Skaleski, Contracting Officer, AFRL/RYKSW, kathryn.skaleski@us.af.mil mailto:gabriel.berner@us.af.mil mailto:kathryn.skaleski@us.af.mil

2.0 Full Text Announcement

2.1 Program Description:

Air Force Research Laboratory, AFRL/RF, Information & Spectrum Warfare Directorate, is soliciting white papers (and later technical and cost proposals) on the following experimentation and test effort.

2.2 Statement of Objective/Description of Technical Area(s):

Offerors must request the Statement of Objectives from the Contracting POCs in accordance with Attachment 1 of this solicitation.

2.3 Communication Between Prospective Offerors and Government

Representatives:

Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. 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.

Address questions to the Contracting POCs:

Gabriel Berner AFRL/RYKSW, Contract Specialist gabriel.berner@us.af.mil 385-633-2263

Kathryn E. Skaleski AFRL/RYKSW, Contracting Officer kathryn.skaleski@us.af.mil 385-635-7858

2.4 Within Scope Modifications:

Potential offerors are advised that due to the inherent uncertainty of experimentation and test 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 and modifications under authority of R-DFARS 235.172.

2.5 Deliverable Items:

a. Data Items: See Attachment 5, Contract Data Requirements List (CDRLs)

b. Software: Software deliverables include, but are not limited to, algorithmic models, digital simulations, source code and its corresponding executable code, processing chains, data visualization, and documentation for next-version reprogramming.

c. Hardware: Hardware deliverables include, but are not limited to, PENCAP Card Prototypes and integrated test fixtures for hardware-in-the-loop testing. The Contractor shall deliver all hardware equipment and non-consumed materials developed under this contract to the Government at the conclusion of this effort.

2.6 Schedule:

a. Overall effort: 36 Month Period of Performance (33-month technical period of performance with three (3) months for final report)

b. Data Items: Specified on individual CDRLs (Attachment 5)

c. Software: At the end of the Technical Period of Performance

d. Hardware: At the end of the Technical Period of Performance

2.7 Other Requirements:

a. This announcement incorporates RFO supplement provisions and clauses by reference. The full text of provisions and clauses can be found at Acquisition.gov.

b. Program Security Classification: Unclassified

c. OPSEC: See Attachment 1, Statement of Objectives (SOO) for OPSEC guidance.

d. Export Control: Information involved in this effort is subject to Export Control

(International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774). A Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

e. Export-Controlled Items: As prescribed by R-DFARS 225.7901-4, R-DFARS

252.225-7048, “Export-Controlled Item (JUN 2013)” is contained in this solicitation. This clause shall be contained in ALL resulting contracts.

f. Contractor Performance Assessment Reporting System (CPARS) will apply to contract awards resulting from this ARA. The final performance evaluation will be prepared at the time of completion of work. In addition to the final evaluation, interim evaluation(s) will be prepared annually. Awardees will be requested to provide a POC to receive notifications of the opportunity to provide feedback.

The contractor will be permitted 14 days to review the document and to submit additional information or a rebutting statement. If agreement cannot be reached between the parties, the matter will be referred to an individual one level above the Contracting Officer, whose decision will be final. Copies of the assessments, contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions for other procurements.

2.8 Science and Technology (S&T) Protection:

See Attachment 6: Security Risk Review – AFRLI 61-113. However, the Government may require the offeror to submit additional information &/or a mitigation plan for any identified S&T protection risks. If the Government determines the offeror failed to provide adequate additional information; or an acceptable mitigation plan; or it is determined the offeror’s S&T protection approach is high risk & does not provide adequate protection of S&T information, the Government may reject the proposal & withdraw it from consideration for award.

2.9 Other Information:

2.9.1 Government Furnished Property (GFP) Availability:

GFP is not anticipated to be made available under any resulting contract.

2.9.2 Base Support/ Network Access:

Base Support is not anticipated to be made available under any resulting contract.

2.10 Contract Type/Instrument:

The Government may award any appropriate contract type under the RFO. The anticipated contract type is a definitive (c-type) RFO-based contract. It is anticipated that awards under this ARA will generally be Cost-Plus Fixed Fee (CPFF). Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable.

2.11 Data Rights Desired:

This is an experimentation and test contract where the government anticipates funding the development of the data.

(1) Other Than Commercial Technical Data: Unlimited Rights

(2) Other Than Commercial Computer Software: Unlimited Rights

(3) Other Than Commercial Software Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary Commercial License consistent with Federal statutes and regulations

Terms used in this section are defined in the clauses at R-DFARS 252.227-7989

(DEVIATION 2026-O0036).

Offerors that propose delivery of other than commercial technical data, other than commercial computer software, or other than commercial computer software documentation subject to less than Unlimited Rights should fully explain how a portion or all of the data was developed at private expense. Specifically, offerors must explain what other than commercial technical data, other than commercial computer software, or other than commercial computer software 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 shall include the data rights assertions as required by R-DFARS 252.227- 7992 (DEVIATION 2026-O0036), Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. The assertions list will be included in Section K of each individual RFP and due at time of proposals. Assertions must be completed with specificity.

Each assertion must identify the technical data or computer software to be delivered, and the associated item, component, or process developed exclusively or partially at private expense to which it pertains. Nonconforming data rights assertion lists will not be accepted until submitted in accordance with R-DFARS

252.227-7989 (DEVIATION 2026-O0036).

In accordance with R-DFARS 252.227-7989 (DEVIATION 2026-O0036), the Government shall receive unlimited rights in all other than commercial technical data and computer software developed exclusively with Government funds.

THIRD PARTY SOFTWARE (COMMERCIAL AND OTHER THAN

COMMMERCIAL):

In accordance with R-DFARS 252.227-7989 (DEVIATION 2026-O0036) for commercial computer software, the Government will neither accept nor execute a DD Form 250 for such software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses for any commercial computer software to be delivered that are consistent with Federal Statutes, Federal Case Law, and Federal Regulations.

If any such software, other than commercial or commercial, is not reasonably identifiable at proposal submission, it must still be approved by the contracting officer prior to incorporation. This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration and performance.

Other Than Commercial Computer Software:

All other than commercial computer software will receive the appropriate level rights set forth in R-DFARS 252.227-7989 (DEVIATION 2026-O0036) which include: Unlimited rights, Government Purpose Rights (GPR), Restricted Rights, or rights identified within a specifically negotiated license attached to the contract.

R-DFARS 252.227-7989 (DEVIATION 2026-O0036) describes requirements for incorporation of third party other than commercial copyrighted computer software and computer software documentation.

End User License Agreement (EULA), Software Terms of Service (TOS), or similar legal instrument or agreement - There are common commercial software license terms within EULA, TOS, or similar legal instruments or agreements that violate Federal law and therefore shall not be included or incorporated under any awards made against this ARA. If the proposed offer includes any of these types of instruments or agreements, the offeror is required to provide a signed software license rider along with its proposal. The software license and rider will be attached to the awarded action. See the Rider Template (Attachment 10).

The following is a non-exhaustive list of terms and conditions which are inconsistent with Federal law or Government policy and shall not be included in the commercial computer software license agreement between the Licensor and the Government. Only the Contracting Officer has the authority to bind the Government:

1. The license shall not subject the Government to a contingent liability or a liability that is indefinite or indeterminate, including but not limited to:

indemnification clauses, unilateral price increases, the right to attorney fees, automatic assessment of charges, or automatic renewal provisions. These provisions constitute obligations in advance or in excess of an appropriation and violate the Anti-Deficiency Act.

2. The license shall be governed by Federal Statutes, Federal Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country. The license shall not bind the Government to litigation in a particular forum or venue or require the Government to participate in arbitration.

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

4. The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes and Termination Clauses in the underlying basic contract.

5. The Licensor shall not have the right to enter the premises or monitor Government networks for the purpose of auditing the use of the license.

6. The Licensor shall not have the authority to control or otherwise influence any litigation between a third party and the Government. The United States Department of Justice has the sole authority to represent the Government in all litigation matters.

7. The Licensor shall not use the fact that the Government is using the Licensor’s products in any notification or advertisement to the public (e.g., no publicity rights permitted).

8. The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

9. The license shall not hold the Government liable for directly imposed sales and use taxes.

The Contractor may obtain agreement from the Licensor to insert the clause below in 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 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 R-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. If the software in question is required to be delivered to the Government, the Licensor must grant the Government a sublicense that allows the Government to use the software to meet its requirements.

The Contractor shall provide documentation to clearly correlate or map any commercial computer software to be delivered 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 computer software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

3.0 Award Information

3.1 Anticipated Award Date:

See Overview

3.2 Anticipated funding:

Funding Profile ($K) FY26 FY27 FY28 FY29 Total Total 300 4,000 2,000 3,000 9,300

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.

Notice to Offeror(s)/Supplier(s): The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

4.0 Eligible Offeror:

This is an unrestricted solicitation. Small businesses are encouraged to propose.

4.1 Cost Sharing or Matching:

Cost Sharing is not required.

4.2 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. RFO 35.403(b)(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 R-DFARS 235.403(b)(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.3 Government Agencies:

If a Government agency is interested in performing work, contact the POCs identified in the ARA who will arrange discussions with the Program Manager for this effort. If those discussions result in a mutual interest to pursue your agency’s participation, the effort will be pursued independent of this announcement.

4.3.1 Foreign Participation:

Foreign Industry participation is not authorized at the prime contractor level.

This acquisition involves data that is subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Agency (https://www.dla.mil/logistics-operations/services/joint-certification-program/SpecificDD2345Instructions/) and have a legitimate business purpose may participate in this solicitation. Contact the U.S./Canada Joint Certification Program Office, Defense Logistics Agency, Logistics Information Services J34, HDI Federal Center, 74 Washington Avenue N., Battle Creek, Michigan 49037-3084, (1-877-352-2255)) or the Joint Certification Program Office (JCO) at JCP-ADMIN@DLA.MIL 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.

4.3.2 White Paper/Proposal Limits:

There are no limits on the number of white papers/proposals an offeror may submit. If an offeror submits multiple white papers/proposals, each white paper/proposal must provide unique approaches.

4.4 Ineligibility:

You may be ineligible for award if all requirements of this solicitation are not met on the white paper (and later proposal) due date as identified above.

5.0 White Paper / Proposal and Submission Information

5.1 Overview:

This Announcement consists of a Two-Step Process described in detail below. White Papers/Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement. The Air Force intends to review white papers/proposals and anticipates one award 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. Awards may be made without negotiation/discussion; however, the Government reserves the right to negotiate with those offeror(s) whose proposal is selected for funding.

ONLY WHITE PAPERS ARE BEING SOLICITED AT THIS TIME.

Offerors should be alert for any ARA amendments that may permit extensions to the white paper submission date.

https://www.dla.mil/logistics-operations/services/joint-certification-program/SpecificDD2345Instructions/ https://www.dla.mil/logistics-operations/services/joint-certification-program/SpecificDD2345Instructions/

5.2 First Step (White Paper) Instructions:

a. General: The FIRST STEP requests a white paper and a rough order of magnitude (ROM) cost. The white paper shall include a discussion of the nature and scope of the experimentation and test and the offeror’s proposed technical approach.

The Government will review the white papers in accordance with the FIRST STEP Peer or Scientific Review criteria, set forth in Paragraph 6.1 below. Based on this review, the Government will determine which of the white papers have the potential to best meet the Air Force’s needs. Offerors will be notified of the disposition of their white paper. It is anticipated that Government review of the white papers submitted will take 30 business days. Those offerors submitting white papers assessed as best meeting Air Force needs will be asked to submit a technical and cost proposal. Those offerors not requested to submit a technical and cost proposal will be notified and can request an informal feedback session based on white paper reviews. An offeror submitting a proposal without first submitting a white paper will not be eligible for an award. The cost of preparing white papers in response to this solicitation 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 RFO 31.205- 18.

b. Page Limitation: The White Paper shall be limited to 5 pages, prepared and submitted in Word format. Font shall be standard 10-point business font Arial, New Times Roman, or Calibri. Pages shall be double-spaced, 8.5 by 11 inches, with at least one-inch margins. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, diagrams, cover page, table of contents, and restrictive/proprietary markings (in header or footer). Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 5. The page limitation covers all information (foldouts counted as 1 page for each 8.5 by 11 portion). The Government will not consider pages in excess of these limitations. Offerors should submit White Paper via DoD SAFE https://safe.apps.mil to the Contracting POC, identified in the Overview Information. The maximum email file size the Government can receive is 20 MB. If a DoD SAFE drop-off invite from the AF is required, please send that request to the Contracting POC no later than 7 business days prior to the due date of proposals to ensure a drop off code is provided in a timely manner.

c. Format: The white paper will be formatted as follows:

(1) Section A: ARA Number, Title of Program, Name of Company, Business Size, Company’s Commercial and Government Entity (CAGE) number, Unique Entity Identifier (UEI) number, Contracting POC and Technical POC with appropriate telephone numbers, fax numbers, and email addresses for the POCs;

(2) Section B: Period of Performance and Task Objectives;

(3) Section C: Technical Summary and Proposed Deliverables; and

(4) Section D: Cost of Task (Rough Order of Magnitude (ROM)).

d. Technical Portion: The technical portion of the white paper shall include a discussion of the nature and scope of the experimentation and test and the offeror’s proposed technical approach/solution. It may also include any proposed deliverables. Resumes, descriptions of facilities and equipment, and a proposed Statement of Work are not required at this point.

e. Cost Portion: The cost portion of the white paper shall include a ROM cost estimate. No detailed price or cost support information should be forwarded;

only a time-phased bottom line figure should be provided.

f. Other Information: Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in RFO 52.215- 1(e).

g. White Paper/Proposal Content Summary: You may be ineligible for award if all requirements of this solicitation are not met on the white paper due date.

h. Submission: White Papers must be submitted to the Contracting Points of Contact (POCs):

Gabriel Berner, AFRL/RYKSW, gabriel.berner@us.af.mil, Kathryn Skaleski, AFRL/RYKSW, kathryn.skaleski@us.af.mil

i. Submission Due Date: See Overview

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of RFO 52.215-1(c)(3).

5.3 Second Step (Proposal) Instructions:

a. General Instructions:

(1) The SECOND STEP consists of offerors submitting a technical and cost proposal within 30 business days of the proposal request. After receipt, proposals will be reviewed in accordance with the evaluation criteria in Paragraph 6.1 below. Paragraph 6.2 addresses the proposal review and selection process. Proposals will be categorized and subsequently selected for negotiations.

(2) Offerors should apply the restrictive notice prescribed in RFO 52.215-1(e) Instructions to Offerors—Competitive Acquisition.

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

(4) Proposals must reference the announcement number FA2377-26-R-B014

(5) 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.)

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

(7) The cost of preparing proposals in response to this ARA 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 RFO 31.205-18.

(8) No classified technical proposals or cost volumes are expected. Offerors are encouraged to keep all elements of the proposal package unclassified. In the rare case where an offeror has a need to submit a classified appendix, please contact the Contracting POCs for delivery instructions.

b. Technical/Management Proposal:

(1) Page Limitations: The following describes proposal page limitations:

mailto:gabriel.berner@us.af.mil

a) The Technical/Management Proposal shall be limited to 20 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, Times New Roman, or Calibri. Pages shall be double-spaced, 8.5 by 11 inches, with at least one-inch margins. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, diagrams, cover page, table of contents, and restrictive/proprietary markings (in header or footer). Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 20. The page limitation covers all information (foldouts counted as 1 page for each 8.5 by 11 portion). The Government will not consider pages in excess of these limitations.

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

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

(2) The Technical/Management proposal(s) shall include a discussion of the nature and scope of the experimentation and test 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 volume shall include a SOW 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. In addition to the contractor proposed SOW, a Government generated SOW Supplemental attachment containing additional contracting requirements will be included in any resulting contracts. The SOO is included as Attachment 1 to this ARA.

(3) Any questions concerning the technical proposal or SOW preparation shall be referred to the Contracting POCs.

d. Cost/Business Proposal:

(1) Separate the proposal into a business section and cost section. Adequate price competition is anticipated. If it is later determined APC does not exist, and the threshold for a negotiated contract is equal to or expected to exceed $2,500,000, submission of certified cost or pricing data may be required.

a) See Attachment 3 for the Model Contract. Note that the document awarded may include contract line items (CLINs)/clauses in addition to those in the model, and/or some of the CLIN/clauses in the model 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) Identify any technical data that will be delivered with less than unlimited rights.

d) Subcontracting Plans: For efforts to exceed $900,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference RFO 19.206-2 for subcontracting plan requirements. Small business concerns are exempt from this requirement.

e) Limitations on Pass-Through Charges: As prescribed in RFO 15.110(v)(1) & RFO 15.408(v)(2), provision RFO 52.215-22, “Limitations on Pass- Through Charges- Identification of Subcontract Effort (Oct 2009) and clause 52.215-23, “Limitations on Pass-Through Charges (Jun 2020),” apply.

f) Completed Certifications and Representations (Section K) are due with the proposal. Certifications and Representations (Section K) can be found at Attachment 4 and will also be generated and sent with each RFP. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal.

g) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in the ARA, 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 RFO

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

(2) 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 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 RFO 15.404-8(a)). 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

RFO 15.404-8. 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.

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

6.0 White Paper / Proposal Review Information

6.1 Peer or Scientific Review Criteria

FIRST STEP:

White Paper Peer or Scientific Review Criteria: The Government will review White Papers to determine which of them have the potential to best meet the Air Force’s needs based on the following criteria, which are listed in equal order of importance:

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

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

c. Soundness of the offeror’s technical approach.

d. Affordability (Proposed ROM Cost Estimate for the PENCAP effort).

SECOND STEP:

Proposal Peer or Scientific Review Criteria: Proposals will be reviewed against 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 order of importance.

a. Technical:

(1) 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.

(2) The offeror’s understanding of the scope of the technical effort.

(3) 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.

(4) The potential to transition the experimentation and test 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 ARA, and that proposed GFP provides the offeror an unfair competitive advantage, then RFO 45.202 requires rental equivalent be applied to the Cost Factor for evaluation purposes only).

6.2 SECOND STEP / PROPOSAL - 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.

(1) Selectable: Proposals are recommended for acceptance if sufficient funding is available

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

Note: The Air Force anticipates one award 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. 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.

d. As indicated in Paragraph 2.8 above, the Government will conduct a S&T

Protection Initial Risk Review only for those proposals categorized as Selectable and selected for funding and negotiations.

7.0 Award Administration Information

7.1 Award Notices:

Offerors will be notified whether their proposal is recommended for award about 30 days after proposal submission. The notification is not to be construed to mean that any contract or award is assured, as availability of funds and successful negotiations are prerequisites to any award.

7.2 Administrative and National Policy Requirements:

See Section 2.0.

7.3 Reporting:

Refer to paragraph 2.5. Deliverable Items

8.0 Other Information

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

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

8.3 Feedback Sessions:

When requested, an informal Feedback Session will be provided. The process will follow the time guidelines outlined in the award notice described in Paragraph 7.1.

8.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 R-DFARS 211.274-3, Requirements 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).

8.5 Updates of Publicly Available Information Regarding Responsibility Matters:

Any contract or assistance award that exceeds $750,000; and when offeror checked “has” in paragraph (b) of the provision RFO 52.209-7, shall contain the clause/article, RFO 52.209-9 “Updates of Publicly Available Information Regarding Responsibility Matters.”

ATTACHMENTS

1. Statement of Objectives

2. Statement of Work (SOW) Supplemental Requirements

3. Model Contract

4. Section K- Representations and Certifications

5. Contract Data Requirements List (CDRLs)

6. Security Risk Review – AFRLI 61-113

7. AFRLI 61-113, Appendix I: Security Program Questionnaire

8. AFRLI 61-113, Appendix II: Research & Related Senior & Key Person Profile Worksheet

9. AFRLI 61-113, Appendix III: AFRL Privacy Act Statement for Covered Individuals

10. Software License Rider Template