ADEOC Solicitation - Revision 2.pdf

Date TBD

Hybrid Advanced Research Announcement (ARA) (Open ARA and ARA with Closed Calls)

Amendment 2 – Revisions in Red

Overview Information

NAICS Code: The NAICS Code for this acquisition is 541714 (Research and Development in Biotechnology (except Nanobiotechnology)). The small business size standard is 1,000 employees.

Federal Agency Name: Air Force Research Laboratory (AFRL), 711th Human Performance Wing, Airman Systems Directorate, Airman Biosciences Division (711 HPW/RHB) Bioeffects Division (711 HPW/RHD), and Warfighter Interactions & Readiness Division (711 HPW/RHW).

ARA Title: Advanced Development of Enhanced Operator Capabilities (ADEOC).

ARA Type: This is the Initial Announcement.

ARA Number: FA8650-21-S-6005.

THIS IS A HYBRID ADVANCED RESEARCH ANNOUNCEMENT (ARA) THAT

WILL SOLICIT REQUIREMENTS THROUGH CLOSED CALLS FOR PROPOSALS

AND ACCEPTS WHITE PAPERS DURING THE OPEN PERIOD. THIS

ANNOUNCEMENT POSTS THE BASIC ARA AND DOES NOT REQUIRE

PROPOSALS AT THIS TIME. THE BASIC ARA WILL REMAIN OPEN UNTIL 11

SEPT 2028 WITH CLOSED CALLS BEING RELEASED THROUGHOUT THIS

TIME PERIOD.

Hybrid ARA Closed Calls (Closed Calls (One-Step) and Open Period (Two- Step), See Section IV for instructions): This ARA will follow a hybrid construct with the option to solicit one-step targeted, Closed Calls for specific research objectives, or a two-step Open Application process for white papers submitted during the Open Period for any research objective. The Basic Statement of Objectives (SOO) will resolicit the research objectives for submittal of white papers once the resulting proposals of the Closed Call(s) have been awarded. Submittal of white papers will be accepted within the first 72 months of the Solicitation date unless a Closed Call is in process.

For white paper submission during the Open Period, topic areas are located in Attachment 1 (ADEOC Statement of Objectives) of this document. Over the period of this ARA, Closed Calls will be issued to request proposals for specific area(s) of interest. Each Closed Call will contain specific requirements and pertinent information. When a Closed Call is issued, the specific research objective of the Closed Call will be closed off from the Open Period. The areas of the Closed Call's

SOO will reopen for white papers once the resulting proposal(s) of the Closed Call have been awarded. Proposals submitted in response to the Closed Calls will be accepted as specified in the individual Closed Calls and evaluated in accordance with the Proposal Review Information (section V). Offerors should monitor the SAM.gov website at https://sam.gov/content/home in the event this announcement is amended or Closed Calls are issued.

Proposal Due Dates and Times:

For ONE-STEP targeted, Closed Calls

First Step: PROPOSAL DUE DATE AND TIME: To be provided in each Closed Call.

For TWO-STEP Open Applications (White Papers and Proposals)

The Open Period application process under this ARA consists of a white paper step and a proposal step. The purpose of this two-step approach is to facilitate pre-screening by the U.S. Government such that detailed proposals are only sought from applicants whose white papers demonstrate the most promise for award (this also helps to reduce unnecessary proposal preparation efforts). The Government's decision to invite a Proposal will be based upon the evaluation results of a timely and compliant white paper submission. Only the most highly rated white papers will receive an invitation from the government to submit a Proposal. An Applicant that does NOT submit a timely and compliant white paper is NOT eligible to submit a Proposal for consideration for funding. An Applicant that does NOT receive an invitation from the Government to submit a Proposal is NOT eligible to submit a Proposal.

First Step: WHITE PAPER DUE DATE AND TIME: This ARA is open and effective through 10 Sept 2028 at 5:00 pm local time, WPAFB, OH. White papers may be submitted at any time during this period against research objectives unless a Closed Call(s) is in progress.

Second Step: PROPOSAL DUE DATE AND TIME: To be provided in the Requests for Proposal (RFPs) sent to offerors that submit white papers considered to best meet the needs of the Air Force.

NOTE: White paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Any white paper or proposal received in this ARA after the exact time specified for receipt of offers is "late" and will not be considered except at the Contracting Point of Contact’s discretion. It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes.

Submission: The AF requests electronic white papers/proposals be submitted as the final copy for a stated research objective using DoD SAFE (https://safe.apps.mil/) and an email confirmation listing the documents submitted via DoD SAFE. Documents shall have uniformity when labelling as such: “Company Name – Document Name – Date of Document” for all steps of submission. If a revision is needed, please request a new link and resubmit the proposal in full.

Proposals must be submitted to the Contracting Point of Contact (POC): Ms.

Stephanie Auld, AFRL/RAKHA, stephanie.auld.1@us.af.mil; and Mr. Daniel Harkins, AFRL/RAKHA, daniel.harkins@us.af.mil.

Hand Delivery: Not accepted.

Solicitation Request: The Air Force Research Laboratory (AFRL), 711th Human Performance Wing, Airman Systems Directorate, RHB, RHD, and RHW Divisions are soliciting white papers on the research efforts described in Attachment 1, ADEOC Statement of Objectives (SOO). Proposal solicitations pursuant to Closed Calls will be requested under separate Closed Call solicitations. Each Closed Call will contain specific requirements pertinent to that particular Closed Call. Unless otherwise stated in a specific Closed Call, all other requirements are listed within this ARA.

Type of Contract/Instrument: The Air Force reserves the right to award Contract(s) and/or Other Transaction(s) pursuant to 10 U.S.C. § 4023 (formerly 10 U.S.C. 2373), based on the instrument deemed most appropriate. It is anticipated that contracts awarded under this ARA will generally be Cost Plus Fixed Fee (CPFF).

REMINDER: Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

NOTE: If proposing a Federal Acquisition Regulation (FAR) based contract, the FAR clause references in this ARA shall apply. This announcement incorporates FAR and supplement provisions and clauses by reference.

The full text of these provisions and clauses can be found at https://www.acquisition.gov/browse/index/far.

If proposing an Other Transaction (OT) pursuant to 10 U.S.C. 4023, these FAR references and clauses would not apply. The terms and conditions of an OT agreement should be developed and negotiated on a case-by-case basis.

NOTE: In accordance with 10 U.S.C. 4023, the intent of this Solicitation is to identify, test, and transition specific proposed capabilities (systems/subsystems/components and associated data/documentation) to address specific military gaps aligned to the mission sets and objectives of the responsible AFRL organization(s). It is not intended to establish Advisory and Assistance Services (A&AS) contracts.

Estimated Program Cost: The total estimated program value is $300,000,000.00, with multiple awards ranging from $50,000.00 to $20,000,000.00 (the Government reserves the right to exceed this amount if determined to be in https://safe.apps.mil/ mailto:tyrone.hines.1@us.af.mil https://www.acquisition.gov/browse/index/far the best interest of the Government).

Anticipated Number of Awards: The Air Force anticipates awarding multiple awards for this announcement. However, the Air Force reserves the right to award zero, one, or more OT(s) and/or contract(s) for all, some or none of each solicited effort based on the offeror’s ability to perform desired work and funding fluctuations. There is no limit on the number of OTs or contracts that may be awarded to an individual offeror.

Brief Program Summary: The purpose of this effort is to develop, mature, validate, and ultimately transition technologies fostered under the 711 HPW/RHB, RHD, and RHW Research, Development, Test & Evaluation (RDT&E) Advanced Technology Development product lines.

• Proposed technology solutions for the Airman Biosciences Division (711 HPW/RHB) will provide the capability to enable, enhance, sustain, and/or restore the health, performance, and safety of personnel in a variety of challenging USAF/USSF mission sets. The goal is to provide advanced technologies and data products, personalized to the individual and appropriate for use in operational USAF/USSF environments.

• Proposed technology solutions for the Bioeffects Division (711 HPW/RHD) will provide the capability to field and use novel weapon technologies, including directed energy systems, and enable the development of protective equipment and mitigation strategies in extreme environments faced by USAF/USSF. These technologies include the ability to model the human in these mission spaces for weaponeering guides, wargames and mission planning.

• Proposed technology solutions for the Warfighter Interactions and Readiness Division (711 HPW/RHW) will provide the capability to increase combat capabilities through personalized learning, readiness, and cognitive improvements; and to deploy integrated solutions that develop synergies, maximize battlespace interoperability, enhance situational awareness, and increase combat power while decreasing Airman and Guardian physical and cognitive workloads.

While this acquisition is targeted for 711 HPW/RHB, RHD, and RHW product line development efforts, other AFRL/711 HPW product lines would be able to utilize this ARA if their efforts fit within the technical scope of the ARA.

The proposed acquisition would acquire specific hardware/software/data system, subsystem and/or component solutions, with advanced system development, engineering, and integration skills needed to support experimentation and development of military prototype systems for operational demonstration, assessment, and eventual transition to acquisition programs for production and deployment. Envisioned research, development, test and evaluation (RDT&E) activities encompass technology readiness levels (TRL) 5 through 7 to provide documentation and engineering analyses for acquisition program initial system design reviews. The Contractor will perform systems research and development

(R&D) at government and industrial settings. Contractor activities will include but are not limited to systems engineering, human systems integration, alerting or alarms, and communication functionality, as well as development and testing of methods, interventions, environments, and devices capable of monitoring/regulating/mitigating workload and operator demands to ensure overload in critical tasks does not occur.

Note: For TRL definitions see https://www.gao.gov/assets/680/679006.pdf, Table 11.

Multiple products will be developed and matured for transition under this acquisition. Central to the RH product lines is the development of assess/monitor/enable/enhance/sustain/restore technologies, integrated with data collection and processing, for physiological and/or cognitive state assessments and assessment of mission outcomes. Each product will be unique in its own development, but the following management/development approach would generally apply to all products:

• Evaluate existing available technologies (commercial or government "off the shelf" (COTS or GOTS)) for applicability and maturity via lab tests for specification conformance, reliability, user acceptance, and technical adequacy

• Down-select component technologies

• Conduct analysis to determine appropriate computational requirements, data collection/storage platform(s), and prototype system/sub-system interface protocols

• Develop methodologies for data collection, processing, and storage, operator alerts, and communication/intervention/remediation protocols

• Integrate component elements into a system prototype

• Conduct verification tests on the system prototype (lab and simulated end use environments)

• Validate prototype in an appropriate end user environment (i.e., operational assessment)

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 (see below) 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. If there is any doubt as to whether a response provides a competitive advantage, the answer will be posted publicly on SAM.gov for all contractors to review. For those white papers not selected to provide a full proposal, notification and feedback will be managed by the Contracting POCs.

https://www.gao.gov/assets/680/679006.pdf

Address technical questions to the Technical POCs:

• Dr. James Christensen (RHB - Biotechnology for Performance Research & Demonstration Product Line), Building 837, Wright-Patterson AFB, OH 45433, 937-904-9543, james.christensen.7@us.af.mil.

• Dr. Darrin Ott (RHB - Operational and Aeromedical Health Product Line), Building 837, Wright-Patterson AFB, OH 45433, 937-904-9572, darrin.ott.2@us.af.mil.

• Dr. Casey Pirnstill (RHD – Bioeffects Product Line Lead), 4141 Petroleum Rd, JBSA-Fort Sam Houston, TX, 78234, 419-569-2816, casey.pirnstill@us.af.mil.

• Dr. Robert Thomas (RHD – Bioeffects Core Technical Competency (CTC) Lead), 4141 Petroleum Rd, JBSA-Fort Sam Houston, TX, 78234, 210-539- 8150, robert.j.thomas.47@us.af.mil.

• Dr. Glenn Gunzelmann (RHW - Training CTC Lead), Building 852, Wright- Patterson AFB, OH 45433, 937-938-2250, glenn.gunzelmann@us.af.mil.

• Dr. Deirdre Mahle (RHW - Airman Machine Integration Product Line), Building 33, phone 937-255-0423, deirdre.mahle@us.af.mil.

• Dr. Gregory Beister (RHW - Analytic Tools Product Line), Building 33, Wright- Patterson AFB, OH, 45433, 937-938-4025, gregory.beister@us.af.mil.

Address contracting questions to the Contracting POC: Ms. Stephanie Auld, AFRL/RAKHA, 2130 8th Street, Building 45, Wright-Patterson AFB, OH 45433-7541, stephanie.auld.1@us.af.mil; and Mr. Daniel Harkins, AFRL/RAKHA, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541, daniel.harkins@us.af.mil.

mailto:james.christensen.7@us.af.mil mailto:darrin.ott.2@us.af.mil mailto:winona.constable@us.af.mil mailto:robert.j.thomas.47@us.af.mil mailto:glenn.gunzelmann@us.af.mil mailto:deirdre.mahle@us.af.mil mailto:gregory.beister@us.af.mil mailto:tyrone.hines.1@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, 711th Human Performance Wing, Airman Systems Directorate, Airman Biosciences Division (AFRL/711 HPW/RHB), Bioeffects Division (AFRL/711 HPW/RHD), and Warfighter Interactions & Readiness Division (AFLR/711 HPW/RHW) are soliciting white papers, and anticipate issuing future Closed Calls, on the following research effort:

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

Attachment 1, ADEOC Statement of Objectives (SOO).

2. OPSEC: All contractors shall participate in all activities associated with the disciplines of the organization’s Industrial Security, Information Security, Personnel Security, Operations Security (OPSEC), Antiterrorism, and Program Protection programs, following appropriate measures in each program as required for this particular contract. These are required in an effort to reduce program vulnerability from successful adversary collection, exploitation of critical information, and violations of export control requirements. The prime contractor will ensure that all subcontractors, if required, conform to these requirements as required by the prime contractor. Guidance can be provided by 711 HPW/OMS Security as needed.

3. 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 the overall contract ceiling amount.

4. Deliverable Items:

a. Data Items: To be determined for each individual award in the Open Period or on a Closed Call by Closed Call basis; however, a Final Report will be required at a minimum on all awards under the Open Period or on Closed Call by Closed Call basis. See Attachment 2 for a list of potential Contract Data Requirements List (CDRLs), DD Form 1423-1.

b. Software: Deliverables to be determined based on each award in the

Open Period, or on a Closed Call by Closed Call basis.

c. Hardware: Deliverables to be determined based on each award in the

Open Period, or on a Closed Call by Closed Call basis.

d. Other: To be determined based on each award in the Open Period, or on a Closed Call by Closed Call basis.

5. Schedule:

a. Overall effort: The overall ARA program will run for 120 months.

Schedule for each Closed Call is to be determined. Schedule for individual awards under the Open Period is to be determined.

b. Data Items: To be determined for each award.

c. Software: To be determined for each award.

d. Hardware: To be determined for each award.

6. 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 https://www.acquisition.gov/browse/index/far.

b. Program security classification: It is anticipated that the majority of the awards will be Secret classification/safeguarding capability, but security classification will be determined for each award. Highest security classification for any award is TS//SCI. A draft (sample) DD Form 254 (DD254) is attached to this ARA (see Attachment 3); but a DD254 specific to each Closed Call effort will be attached to individual Closed Calls against the ARA. If a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with the Defense Counterintelligence and Security Agency (DCSA) at https://www.dcsa.mil/.

c. TEMPEST requirements: Not applicable.

d. OPSEC: See attached Statement of Objectives (SOO) for OPSEC guidance.

e. Export Control: Information involved in Closed Calls and awards under the Open Period for this research effort may 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 a Closed Call or award under the Open Period may be subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposals.

f. Export-Controlled Items: This acquisition is expected to generate or require access to 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.

https://www.acquisition.gov/browse/index/far https://www.dcsa.mil/

g. Contractor Performance Assessment Reporting System (CPARS) will likely be applicable but will be determined on a Closed Call by Closed Call basis or Open Period award basis in accordance with FAR 42.1502 and DFARS

242.1502. Interim and final evaluations of contractor performance for contract awards will be prepared in accordance with AFFARS 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. 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.

h. Science and Technology (S&T) Protection: In accordance with Air Force Research Laboratory Instruction (AFRLI) 61-113, “Science and Technology (S&T) Protection for the Air Force Research Laboratory”, offerors are required to submit the following as part of their proposal:

1) A completed initial Standard Form (SF) 424, Research and Related Senior/Key Person Profile (Expanded) Form, (Attachment 6) for all Senior/Key Personnel proposed in support of the AFRLI 61-113 Personnel Risk Assessment requirement.

2) Documentation of a Security Program Plan in support of the AFRLI 61- 113 Initial Institution S&T Protection Program Review requirement.

This must include, at a minimum, a completed Security Program Questionnaire (Attachment 7). Submittal may also include a pre-existing plan that that the offeror uses as a matter of course or plan developed specifically for this acquisition. The purpose of requesting the plan is to assess the offeror’s capacity for protection of the Government’s S&T. Failure to demonstrate a plan adequate to meet the needs of the requirements, as determined by the Government in its sole discretion, may be grounds for considering the proposal unawardable.

Government Procedures

The Government will review the submitted S&T protection documentation only for those proposals categorized as Selectable and selected for funding and negotiations.

S&T Protection Initial Risk Review:

• Personnel Risk Assessment: The Government will review non-government research key/senior performers identified by the offeror on the initial SF 424 for workload conflicts and conflicts of interest.

• Initial Institution S&T Protection Program Review: The Government will review the offeror’s security program information submitted in accordance with paragraph 2 of this section (above) to identify any potential risks and ensure appropriate measures are in place to protect S&T information.

The Government may require the offeror to submit additional information and/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 and does not provide adequate protection of S&T information, the Government may reject the proposal and withdraw it from consideration for award.

S&T Protection Annual Risk Review: In accordance with Attachment XX (SOW Supplemental Requirements), the Contractor shall provide an SF 424 with the following information: 1) an initial report of all Senior/Key Personnel at the time of award; 2) an annual report of all Senior/Key Personnel providing support; and 3) a report for any new Senior/Key Personnel who join the contract, agreement, grant, or OT. Any updated SF 424s for new Senior/Key Personnel supporting the award require coordination from the Government prior to the contractor employee receiving access to S&T information. The purpose of this report is oversight and should not be construed as relieving the contractor/recipient of any S&T Protection requirements within the contract, grant, agreement, or OT.

7. Other Information:

a. Government Furnished Property (GFP) availability: To be determined for each award.

In accordance with FAR 45.201(b), the Contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation or rehabilitation costs.

If GFP is included in the Closed Call or requested in a proposal, the following clauses/provisions apply:

1) FAR 52.245-1 Government Property or FAR 52.245-1, Alt II if the resulting contract is with a nonprofit organization or applied research at nonprofit organizations (Apr 2012);

2) FAR 52.245-9 Use and Charges (Apr 2012);

3) DFARS 252.211-7007, Reporting of Government Furnished Property (Aug 2012);

4) DFARS 252.211-7007, Tagging, Labeling and Marking of Government Furnished Property (Apr 2012);

5) DFARS 252.245-7002, Reporting Loss of Government Property (Apr 2012);

6) DFARS 252.245-7003, Contractor Property Management System Administration (Apr 2012);

7) DFARS 252.245-7004, Reporting, Reutilization, and Disposal (May 2013).

b. Base Support / Network Access: To be determined for each award.

c. Organization Conflict of Interest: To be determined for each award.

d. Flight Testing: To be determined for each award.

e. Human Use: To be determined for each award.

f. Animal Use: To be determined for each award.

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

h. Data Rights Desired: Will be determined for each Closed Call or Open Period award. Data Rights desired by the contractor should be included with proposal submission as part of the Section K. Unless a Closed Call states otherwise, see desired rights below. Given their importance in the Peer or Scientific Review criteria, Contractors MUST clearly mark any data and/or software rights assertions in their proposals.

(1) Noncommercial Technical Data: Unlimited Rights desired, Government Purpose Rights (GPR) acceptable

(2) Noncommercial Computer Software (NCS): Unlimited Rights desired, GPR acceptable

(3) NCS Documentation: Unlimited Rights desired, GPR acceptable

(4) Commercial Computer Software Rights: Customary License acceptable

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for 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(b)(1) and 252.227-7014(b)(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(b)(2) and DFARS 252.227- 7014(b)(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 non-commercial 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 Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. The assertions list is included in Section K and due at time of proposals. Assertions must be completed with specificity. Each assertion must identify 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. See Data Assertions List (DAL) Guide, Attachment 4, for key rules and a sample listing.

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 pre-approval 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(b); and prior to delivery of such—

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

• 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(b), 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 between the Licensor and the Government (Licensee):

• 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, as these provisions may constitute obligations in advance or in excess of an appropriation and may violate the Anti-Deficiency Act.

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

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

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

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

• The Licensor shall not have the authority to control or otherwise influence any litigation between a third party and the Government.

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

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

• The license shall not disclaim all warranties through use of an "as is" provision.

• 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 ADEOC Program. In performance of the ADEOC Program, Government personnel as well as Government contractors may use the software.

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

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

• 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. Specifically, the following sections are hereby deleted from the [Software License] [and/or amended as indicated below]:

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

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

• Contract Line Item Numbers (CLIN);

• Contract Deliverables (CDRLs);

• Paragraphs in the Statement of Work (SOW); and

• 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: To be determined for each award.

2. Anticipated funding: Each Closed Call will include an anticipated funding profile/amount for that specific Closed Call. Each Open Period RFP will include an anticipated funding profile for that particular award.

III. Eligibility Information

1. Eligible Offeror: This is an unrestricted solicitation. Businesses of all sizes are encouraged to propose on all or any part of this solicitation during the Open Period and under each Closed Call.

2. Cost Sharing or Matching: Not required.

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

However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, AFRL must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made, would a determination be made concerning the FFRDC’s eligibility to receive an award.

4. Government Agencies: If a Government agency is interested in participating in this program, contact the Technical POC identified in the applicable Closed Call. 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 is not allowed at the prime level. The U.S. Prime Contractor and/or Sub-Contractor may hire foreign nationals (FN) with prior Foreign Disclosure Office (FDO) approval; however, FNs will be limited to Public Domain information only. Public Domain information is defined as information that is releasable to the general public and sometimes referred to as open source material. Examples include but are not limited to newspapers, magazines and information posted on the Internet. Any proprietary information will have to be appropriately protected.

b. This acquisition may involve data that is subject to export control laws and regulations. This determination will be made on a case-by-case basis and identified in each Closed Call. If the data is determined to be subject to export control laws, only contractors who are registered and certified with the Defense Logistics Agency (DLA) and have a legitimate business purpose may participate in this solicitation.

Contact the DLA Customer Interaction Center, 74 Washington Avenue N., Battle Creek, Michigan 40917-3084 (1-800-352-3572 / 1-877-352- 2255) 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, if applicable.

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

d. The proposal may be ineligible for award if all requirements of this solicitation are not met on the proposal due date as identified in each Closed Call.

IV. Proposal and Submission Information

1. Overview: White papers and/or proposals submitted under a Closed Call or Open Period shall be in accordance with the instructions provided in the specific Closed Call or Open Period RFP instructions, and in this announcement. Each Closed Call will be a one-step process; applications during the Open Period will be a two-step process. For individual Closed Calls and Open Period applications, the Government intends to review resulting white papers/proposals and award all, some, or none of the proposals received without negotiations/discussions. However, the Government does reserve the right to negotiate with those offerors whose proposals have been selected for funding. Offerors should be alert for any ARA/Closed Call amendments that may change proposal requirements or permit extensions to the proposal submission dates.

2. Closed Call Proposal Instructions

a. General Instructions:

1) Offerors will submit a technical and cost proposal within 30 working days of the proposal request (unless otherwise stated in the Closed Call). After receipt, proposals will be reviewed in accordance with the award criteria as defined in the Closed Call. Proposals will be categorized and subsequently selected for negotiations.

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

3) Proposals must reference the announcement number, and relevant technical areas of interest.

4) Offerors must submit one original copy of their proposals to the Contracting POC through DoD SAFE (See Submission paragraph on

pg. 3)).

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

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

7) 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 POC for delivery instructions.

e. Technical/Management Proposal To Be Solicited via Closed Calls:

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

a) The Technical/Management Proposal shall be limited to 25 pages (unless otherwise stated in the Closed Call).

Technical/Management proposals and SOWs must be provided in Microsoft Word (DOCX) format. Signed pages may be submitted in Adobe (PDF) format.

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 25 (unless otherwise stated in the Closed Call). 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. The Government will not consider pages in excess of these limitations.

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

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.

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

Additional information on prior work in this area, descriptions of available equipment, use of base support (if desired), data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal. The volume(s) shall include a SOW(s) detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation. Do not include any proprietary information in the SOW. In addition to the contractor proposed SOW, a Government generated SOW Supplemental Requirements document (see Attachment 5, Model Contract) containing additional contracting requirements will be included in any resulting contracts.

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

f. Cost/Business Proposal To Be Solicited Via Closed Calls:

1) Separate the proposal into a business section and cost section.

Adequate price competition is anticipated.

a) See Attachment 5 for Model Contract, unless otherwise stated in the Call. No sample is provided for Other Transactions. The Model Contract will provide examples of clauses that may be included in final contracts, and it will provide a basic contract structure. Contracts that are ultimately awarded against the individual Closed Calls may vary based on individual program requirements, negotiated terms and conditions, etc.

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 Model Contract, any information not technically related, etc. Provide rationale for exceptions to any portion of the Model Contract.

c) Associate Contractor Agreements: Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that require them to share information, data, technical knowledge, expertise, or resources.

The contracting officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the contracting officer will identify associate contractors with whom agreements are required.

d) Identify any technical data that will be delivered with less than unlimited rights (See section I.7.h Data Rights desired).

e) Subcontracting Plans: For efforts to exceed $750,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) for subcontracting plan requirements. Small business concerns are exempt from this requirement.

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

g) Completed Certifications and Representations will be sent when a proposal is requested and are due with the submission of the proposal. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal. See Section K, Representations and Certifications, in Attachment 5 Model Contract, and provide the completed Section K as part of the proposal package for each Closed Call (unless otherwise stated in the Closed Call).

h) If an offeror proposes the use of Government Furnished Property (GFP), other than the GFP identified in the Closed Call (if applicable), 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.

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(s) should include the following if applicable.

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

b) Labor and Overhead Rates: Direct labor hours, with their applicable rates, must be broken out and the bases used clearly identified. The source of labor and overhead rates and all pricing factors should be identified. For instance, if a Forward Pricing Rate Agreement (FPRA) is in existence, that should be noted, along with the Administrative Contracting Officer (ACO) 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)).