AFSIM FORGE ARA - FA2391-25-R-B002.pdf

1-Step Advanced Research Announcement

Overview Information

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/RQ Aerospace Systems Directorate

Advanced Research Announcement Title: ADVANCED FRAMEWORK FOR

SIMULATION, INTEGRATION, AND MODELING FOR THE GREATER ENTERPRISE

(AFSIM FORGE)

Advanced Research Announcement Type: This is the Initial Announcement.

This Announcement is issued pursuant to 10 USC 4023.

Advanced Research Announcement Number: FA2391-25-R-B002

Intent to Propose: Offerors that anticipate submitting a proposal are requested to submit an e-mail to Megan Rosenbeck, Megan.Rosenbeck@us.af.mil, and Logan Hartley, at Logan.Hartley@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 21 February 2025 by 3:00 p.m. WPAFB local time. The Intent to Propose is intended to be an informative courtesy to AFRL and is not a prerequisite to propose.

Proposal Due Date and Time: 10 March 2025, 3: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).

Submission: Proposals must be timely submitted to the Contracting Point of Contact (POC): Megan Rosenbeck and Logan Hartley, AFRL/RQKPD in accordance with instructions below. The AF requests electronic proposals be submitted using DoD SAFE (primary method) to send to the following email addresses:

Megan.Rosenbeck@us.af.mil and Logan.Hartley@us.af.mil

The maximum email file size the Government can receive is 20 MB. Multiple submissions may be needed to facilitate delivery of the entire proposal.

Contractors should request a DoD SAFE drop-off invite from the AF. Please send that request to Megan.Rosenbeck@us.af.mil and Logan.Hartley@us.af.mil no later than 7 days prior to the due date of proposals to ensure a drop off code is provided in a timely manner.

If attempted DoD SAFE delivery is not possible for any reason and DoD SAFE delivery is confirmed as not possible by the Contracting Officer, Megan Rosenbeck, encrypted email delivery to Megan.Rosenbeck@us.af.mil and Logan.Hartley@us.af.mil will be considered an acceptable back-up method. Please confirm encryption method with Megan Rosenbeck and Logan Hartley prior to delivery.

Solicitation Request: Air Force Research Laboratory, AFRL/RQ, Aerospace Systems Directorate, 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. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this ARA will generally be IDIQ Contracts with Cost Plus Fixed Fee Task Orders. Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

Anticipated Number of Awards: The Air Force anticipates awarding 2-4 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:

The Advanced Framework for Simulation, Integration, and Modeling (AFSIM) is a government-owned, open-source, and community-informed military simulation framework primarily used by the U.S. Department of Defense (DoD) acquisition, operations analysis, and research and engineering communities. AFSIM provides these communities with an ever-expanding toolset to ease scenario and model creation, strengthen analytical conclusions, and enrich virtual wargaming experiences. AFSIM benefits from a passionate user community that contributes directly to its development and evolution. With broad representation from all branches of the U.S. military and affiliated U.S. Government (USG) agencies, industry, academia, and international partners, this community increasingly uses AFSIM to assess and compare emerging weapon system concepts, refine operational employment tactics, and ultimately inform research investment and acquisition decisions.

The Aerospace Systems Directorate of the Air Force Research Laboratory (AFRL) at Wright-Patterson Air Force Base (AFRL/RQ) currently manages, develops, maintains, and freely distributes AFSIM to benefit the entire defense innovation base. AFSIM is available to all USG agencies and eligible DoD industry partners at no cost. AFRL shares AFSIM with industry partners through an information transfer agreement, making it the ideal tool to support internal research and development activities. AFRL also shares AFSIM with other USG agencies through a memorandum of understanding.

The purpose of FORGE is to mature and scale AFSIM as an enterprise capability while fostering a vibrant community of users, developers, and maintainers contributing to its evolution.

Communication Between Prospective Offerors and Government Representatives: Contracting Officer, Megan Rosenbeck is the Communication Point of Contact both before and after the solicitation release. All communication after solicitation release must be in writing to maximum extent practical.

Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. Discussions with the point 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 all questions to the Contracting POC: Megan Rosenbeck, Contracting Officer, at Megan.Rosenbeck@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Aerospace Systems Directorate, Strategic Planning & Analysis Division is soliciting technical and cost proposals on the following research effort:

1. Statement of Objective/Description of Technical Area(s):

a. See Attachments 1 and 2, Statement of Work and Task Order Statement of Objectives.

b. Controlled Distribution Information: Please be aware that additional controlled distribution information (including the Basic SOW, Task Order SOO, and Task Order SOW Template) is available for those who possess a valid DD Form 2345, pass Security vetting, and timely request the information from the Contracting Officer identified in this ARA. The SOW and SOO will be disseminated by request once a valid Military Critical Technical Data Agreement DD2345 is provided and the offeror has a Supplier Performance Risk System (SPRS) score of 110 (if the score is less than 110, please provide mitigation plan to achieve 110 prior to award) and then must properly be vetted by AFRL/RQOS.

c. Please also note Section 9 “Technical Proposal Submission” in the Task Order Statement of Objectives for page allocation. This is intended to assist proposal preparation and is mandatory.

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: Please see Attachment 4 CDRL List (Please note – No Final Report is required)

b. Software: Applicable in accordance with Attachment 2 Task Order Statement of Objectives

c. Hardware: No initial hardware items required, but the potential exists that hardware could be developed in the course of research. As such, all hardware developed under this program will be made a CLIN deliverable.

4. Schedule:

a. Overall effort: IDIQ Period of Performance 50 Months

b. Ordering Period: 44 Months

c. Task Order 0001 Period of Performance: 26 Months

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

e. Software: Specified in Task Order Statement of Objectives

f. Hardware: Not 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 Acquisition.gov.

b. Program security classification: The solicitation DD 254 is at the Secret level. A TS/SCI DD 254 will be developed prior to award. Please see Attachment 5, IDIQ Draft/Solicitation DD254. Offerors must verify their Cognizant Security Office information is current with Defense Counterintelligence and Security Agency (DCSA) at www.dcsa.mil.

c. OPSEC: See the Basic SOW and TO SOW Template for OPSEC guidance.

d. Export Control: Information involved in this research effort 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.

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

f. Contractor Performance Assessment Reporting System (CPARS) is required IAW DFARS 242.1502, DoD Class Deviation 2013-O0018, Past Performance Evaluation Thresholds and Reporting Requirements, 24 Sep 2013 for 6.4+ efforts over 1M. Interim and final evaluations of contractor performance for contract awards will be prepared in accordance with DFFARS

5342.1503. 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. CPARS will be conducted per task order. 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.

g. Science and Technology (S&T) Protection: See Attachment 10: 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.

6. Other Information:

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

b. Base Support / Network Access: Not Anticipated.

c. Potential Organizational Conflict of Interest: As prescribed in DFFARS

5309.507-2 (b), 5352.209-9001, “Potential Organizational Conflict of Interest (OCT 2019)” is contained in this solicitation.

To ensure AFSIM remains an enduring MS&A capability for the greater DAF and DoD, DAF leadership have secured resources to establish a Model Management Office (MMO) and further accelerate AFSIM’s growth, adoption, and evolution for the greater enterprise. The Air Force plans to use two contracts to realize this vision. FORGE, described in this solicitation, will be used to mature and scale AFSIM as an enterprise capability while fostering a vibrant community of users, developers, and maintainers contributing to its evolution. The second contract, AMMO (AFSIM Model Management Office), is expected to provide non-personnel services for a DAF enterprise MMO for AFSIM. AMMO services will include administration and general clerical support, business management, program and product management, engineering support, and application support. AMMO and FORGE will be closely coupled with positions under AMMO providing systems engineering support and/or technical direction to the contractor(s) developing the system (i.e., AFSIM) under FORGE. This relationship has led to the government identifying a potential organization conflict of interest as defined in 5352.209-9001.

d. Multiple awards subject to Fair Opportunity are anticipated.

e. Data Rights Desired:

(1) Other than 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

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 noncommercial technical data and NCS developed or delivered under this contract are of significant concern to the Government. The Government will therefore evaluate any restrictions on the use of noncommercial 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 accordance with DFARS 252.227-7013(c)(1) and 252.227-7014(c)(1), the Government shall receive unlimited rights in all noncommercial technical data and computer software developed exclusively with Government funds.

In accordance with DFARS 252.227-7013(c)(2) and DFARS 252.2277014(c)(2), the Government shall receive Government Purpose Rights in all noncommercial technical data and computer software developed with mixed funding. “Developed with mixed funding” means, “development was accomplished partially with costs charged to indirect cost pools and/or costs not allocated to a government contract, and partially with costs charged directly to a government contract. Offerors that propose delivery of noncommercial technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how a portion of the data was developed at private expense. Specifically, offerors must explain what noncommercial 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 noncommercial technical data with Limited Rights, NCS with Restricted Rights, or NCS documentation with Limited Rights will be considered. Proposals should fully explain what noncommercial 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 Use, Release, or Disclosure Restrictions. The assertions list is included in Section K 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 DFARS 252.227-7017.

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):

If any such software, noncommercial 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 preapproval by the contracting officer, as described above, continues throughout contract administration.

Noncommercial Computer Software:

DFARS 252.227-7014(d) describes requirements for incorporation of third party noncommercial copyrighted computer software and computer software documentation and is incorporated as follows:

The Contractor shall not, without the written approval of the Contracting Officer, incorporate any copyrighted computer software or computer software documentation in the software or documentation to be delivered under this contract unless the Contractor is the copyright owner or has obtained for the Government the license rights necessary to perfect a license or licenses in the deliverable software or documentation of the appropriate scope set forth in DFARS 252.227- 7014(c), and prior to delivery of such—

(1) Computer software, has provided a statement of the license rights obtained in a form acceptable to the Contracting Officer; or

(2) Computer software documentation has affixed to the transmittal document a statement of the license rights obtained.

In addition, all noncommercial computer software will receive the appropriate level rights set forth in DFARS 252-7014(c), which could include: Unlimited rights, GPR, Restricted Rights, or specifically negotiated license.

Commercial Computer Software:

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.

The following is a non-exhaustive list of terms and conditions which are inconsistent with Federal law and shall not be included in the commercial computer software license agreement between the Licensor and 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 premise 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.

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

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

2. 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 AFSIM FORGE Program. In performance of the AFSIM FORGE Program, Government personnel as well as Government contractors may use the software, subject to any negotiated limits on number of users, as applicable.

3. The license shall not limit the Government’s use of the software at other Government and Government contractor sites.

4. The license shall not restrict the Government 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 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.

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

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.

II. Award Information

1. Anticipated Award Date: 15 September 2025

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 and should not be proposed.

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 Contracting Officer identified in the ARA. 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 participation at the prime contractor level is prohibited.

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 Agency 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-800-352-3572) 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.

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 regarding 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 ARA amendments that may change proposal requirements or permit extensions to the proposal submission date.

Offerors should be aware that supplemental information is available for those who have an approved DD Form 2345 and pass security vetting. To gain access to this information offerors must request from Megan Rosenbeck at Megan.Rosenbeck@us.af.mil and provide their valid DD Form 2345.

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.

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

ii. Proposals must reference the announcement number FA2391-25-R- B002.

iii. Offerors must submit complete proposal electronically in accordance with submission instructions.

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

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

vi. 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 FAR 31.205-18.

vii. 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 Officer for delivery instructions.

b. Offerors must propose to the Task Order (TO) and have a TO award to be eligible for award of a Basic IDIQ. Offerors must propose to the Basic IDIQ:

i. Basic IDIQ

a) Basic IDIQ proposal-Technical and Management

b) Basic IDIQ Statement of Work (SOW) in response to applicable

Statement of Work (SOW). The SOW proposed must match the Government provided SOW as all IDIQ awards must contain identical SOWs for this ARA.

c) Basic IDIQ Business Proposal (including Subcontracting Plan, if applicable, in accordance with FAR 19.7)

ii. Task Order (T.O.) 0001

a) T.O. 0001 Proposal-Technical and Management

b) T.O. 0001 SOW Template must be used in response to applicable

SOO

c) T.O. 0001 Cost (T.O. only) and Business Proposal

c. Technical/Management Proposal:

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

a) The Technical/Management Proposal shall be limited to 20 pages for the Basic IDIQ; and the Technical/Management Proposal shall follow section 9 of the Task Order SOO for T.O. 0001 with the pages prepared and submitted in Microsoft Word format. 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 20 for the IDIQ.

Section 9 of the TO SOO must be followed for the T.O. 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 has no page limit but must utilize the TO SOW Template for the Task Order. The IDIQ SOW must match the IDIQ SOW included with this ARA. The government reserves the right to remove non-task-oriented paragraphs which have been included in the solicitation to assist proposal preparation prior to any resulting award.

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) for the Basic IDIQ, T.O. 0001 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. These volumes 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 attachment containing additional contracting requirements will be included in any resulting contracts. The IDIQ SOW and TO SOO attachments are referenced as Attachments 1 and 2 to this ARA. Proper vetting much be accomplished prior to their distribution.

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

d. Cost/Business Proposal:

i. 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,000,000, submission of certified cost or pricing data may be required.

a) See Attachment 7 for the Solicitation. The solicitation is intended as a courtesy example only. Note that the document awarded may include contract line items (CLINs)/clauses/articles in addition to those in the model, and/or some of the CLIN/clauses/articles 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) 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. No ACA are anticipated for initial award. However, 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 if applicable and associate contractors with whom agreements are required.

d) Identify any technical data that will be delivered with less than unlimited rights. Please be aware that AFRL requires unlimited rights to the AFSIM deliverables.

e) Subcontracting Plans: For efforts to exceed $750,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR 19.704 and DFARS 219.704 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 IDIQ ceiling amount.

f) Limitations on Pass-Through Charges: As prescribed in FAR 15.408(n)(1) & 15.408(n)(2), provision 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 at Attachment 7. 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 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 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. The cost must be broken out by each objective and option. 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 breakdowns 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.

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

IDIQ and Task Order criteria listed below. The overall evaluation of the Basic IDIQ is of greater importance than the evaluation of Task Order

0001 listed below. The IDIQ criteria are of equal importance. The Task Order criteria are of equal importance. Within the overall evaluation of the Task Order criteria, the Task Order technical aspect is ranked as the first order of priority and the Task Order cost/price is a substantial factor but is ranked as the second order of priority.

a. Basic IDIQ Technical Criteria:

i. The offeror's understanding of the scope of the technical effort.

ii. The soundness of the offeror's approach to realize program objectives in a manner consistent with its desired business and coordination strategy.

iii. The offeror’s experience and qualifications related to advancing the solicitation objectives and initiatives.

iv. The soundness of the offeror’s approach to respond to emergent, multi-domain needs including development agility and staffing flexibility at multiple security levels.

b. Task Order Technical Criteria:

i. The offeror’s understanding of the scope of the task order objectives.

ii. The soundness of the offeror’s technical approach including the extent to which the offeror has identified potential obstacles or risks to task order objectives and has proposed realistic strategies to overcome those obstacles or risks.

iii. The soundness of the offeror’s staffing approach including the extent to which the offeror’s organizational structure is coherent with the proposed technical approach.

iv. The offeror’s relevant experience and qualifications to perform the work including the proposed personnel’s skills and experience with methods, technologies, or tools identified in the proposed technical approach.

v. The extent to which the offeror’s approach will enhance the value of AFSIM. Any proposed restriction on technical data or software that will impede the distribution of AFSIM under the liberal terms and conditions of the AFSIM Information Transfer Agreement will be considered.

c. Cost/Price (applicable to TOs): 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 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.

d. As indicated in Paragraph 5. (f) 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.

VI. Award Administration Information

1. Award Notices: Offerors will be notified whether their proposal is recommended for award on or about 25 April 2025. The notification is not to be construed to mean that any contract or 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: Please see Attachment 4 CDRL List.

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. Informal Feedback Sessions:

a. Contracts: When requested, a Feedback Session will be provided with content consistent with the procedures that govern BAAs (FAR 35.016).

Although this is an ARA, the informal feedback will include content consistent with the procedures that govern BAAs.

The process will follow the time guidelines outlined in the award notice described in Paragraph VI.1.

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

5. Pre-Award Clearance: Pursuant to FAR 22.805, a pre-award clearance must be obtained from the U.S. Department Of Labor, 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 https://www.dol.gov/agencies/ofccp/pre-award. 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.

6. Updates of Publicly Available Information Regarding Responsibility

Matters: Any contract or assistance award that exceeds $600,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.”

7. No Required Teaming: Any reference to “team” or “team-of-teams” is not intended to imply or require formal contractor teaming toward shared requirements on any contracts. Contracts and corresponding requirements will be stand-alone obligations. Such reference is intended to provide notice that orders and objectives under this program will relate to a common objective of AFSIM advancement and may relate to each other. Some orders or objective may benefit from collaboration made possible through Associate Contractor Agreements, Non-Disclosure Agreements, Subcontractor arrangements, or other appropriate means. No teaming is required.

8. 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. A DD254 is applicable. Offerors must verify their Cognizant Security Office information is current with Defense Counterintelligence and Security Agency (DCSA) at www.dcsa.mil.

i. This effort is subject to export control. Offerors must submit a Certified DD Form 2345, Militarily Critical Technical Data Agreement, with proposal and also…