Advanced Research Announced (ARA), MSDEW Call 03 Aircraft Defensive Electro-optical Protection Technologies (ADEPT)

Overview Information

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

Federal Agency Name: Air Force Research Laboratory, AFRL/RFZ Information & Spectrum Warfare Division

ARA Title: Multi-Spectrum Defensive Electronic Warfare (MSDEW)

ARA Number: FA8650-20-S-1119 (Basic ARA)

Call Title: MSDEW Call 03: Aircraft Defensive Electro-optical Protection Technologies

(ADEPT)

Call Number: FA2377-26-R-B011

Authority: This announcement is issued pursuant to 10 USC 4023

THIS IS A ONE-STEP SOLICITATION FOR CALL 03 ISSUED UNDER THE MSDEW

ARA. Unless otherwise stated in this call, all requirements listed within the Basic

ARA announcement are considered applicable. Offerors should monitor the Contract

Opportunities website at www.sam.gov in the event this announcement is amended.

Proposal Due Date and Time:

ONE-STEP CALL

• PROPOSAL DUE DATE and TIME – *09 November 2026/2 p.m. EST*

NOTE: Proposal receipt after the due date and time shall be governed by the provisions of RFO 52.215-1(c)(3). Early proposal submission is encouraged.

Prior to Proposal Submission: Offerors should email the Contracting POCs at the emails indicated below indicating the desire to submit a proposal and include their company CAGE code. The Contracting POCs will confirm the company’s active status in the Joint Certification program and then respond with an emailed link/passphrase to DoD SAFE, a secure Department of Defense website designed for the exchange of sensitive information. The DoD SAFE link will allow for the secure download of

Attachments 1 and 2, Technical Area Statement of Objectives (SOOs), and Attachment 5 Solicitation DD254. Attachments 1,2, and Attachment 5 cannot be posted due to Controlled Unclassified Information

(CUI). The Offeror should request a DoD SAFE link to “drop off” the proposal from the Contracting Points of Contact (POCs) identified below. Offerors are required to have emailed the Contracting POCs and request the DoD SAFE link by date/time.

http://www.sam.gov/

Overview: Proposals submitted under this call shall be in accordance with the instructions provided both herein and within the basic ARA announcement. Offerors can propose to more than one technical area. If a potential offeror wishes to be considered for more than one technical area, they must submit separate proposals for each technical areal. The

Government intends to review resulting 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 call amendments that may change proposal requirements or permit extensions to proposal submission dates. No classified submittals will be accepted. The cost of preparing cost and technical proposals in response to this Solicitation is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in RFO 31.205-18.

Proposal and Submission Instructions:

The paragraphs below identify proposal format and content.

a. General Instructions:

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

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

(3) Proposals must reference the announcement number FA2377-26-R-B011 and relevant technical area(s).

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

(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 Call is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in RFO 31.205-18.

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

b. Offerors must propose to a minimum of one technical area to be considered for an award:

(1) For each technical area:

a) Proposal-Technical and Management

b) Statement of Work (SOW) in response to applicable Statement of Objectives

(SOO)

c) Business Proposal (including Subcontracting Plan, if applicable, in accordance with RFO 19.109)

c. Technical/Management Proposal:

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

a) The Technical/Management Proposal shall be limited to 7 pages for each technical area, prepared and submitted in Microsoft Word format.

b) The Statement of Work (SOW) shall be limited to 10 pages for each technical area.

(2) Font shall be standard 10-point business font Arial, New Times Roman, or Calibri.

Pages shall be double-spaced, 8.5 by 11 inches, with at least one-inch margins. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, diagrams, cover page, table of contents, and restrictive/proprietary markings (in header or footer). Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than

Page 7. The page limitation covers all information (foldouts counted as 1 page for each 8.5 by 11 portion). The Government will not consider pages in excess of these limitations.

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

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

(5) The Technical/Management proposal(s) for each technical area 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 SOWs detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation.

Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced above to assist in SOW preparation. In addition to the contractor proposed SOW, a Government generated SOW attachment containing additional contracting requirements will be included in any resulting contracts. The technical area SOOs are referenced as Attachments 1 and 2 to this Call.

http://www.afrl.af.mil/contract/default.htm http://www.afrl.af.mil/contract/default.htm

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

d. Cost/Business Proposal:

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

a) See Attachment 7for the Model Contract. 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. The contracting officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the contracting officer will identify associate contractors with whom agreements are required.

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

e) Subcontracting Plans: For efforts to exceed $900,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference RFO 19.206-2 for subcontracting plan requirements. Small business concerns are exempt from this requirement. If an IDIQ contract arrangement is anticipated, the basis for the subcontracting plan should reflect the entire ceiling amount.

f) Limitations on Pass-Through Charges: As prescribed in RFO 15.110(v)(1) and RFO

15.110 (v)(2)(i), provision 52.215-22, “Limitations on Pass-Through Charges- Identification of Subcontract Effort (Oct 2009) and clause 52.215-23, “Limitations on

Pass-Through Charges (Jun 2020),” apply.

g) Completed Certifications and Representations (Section K) are due with the proposal.

Certifications and Representations (Section K) can be found at Atch 6. 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 Call, the offer must specifically identify each piece of GFP in the

Cost/Business Proposal and propose and substantiate a rental cost for evaluation purposes in accordance with RFO 45.201. Include the following information in the proposal:

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

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

(iii) The amount of rent that would otherwise be charged in accordance with RFO

52.245-9, Use and Charges; and

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

(2) Cost Element Breakdown: Clear, concise, and accurate cost proposals reflect the offeror's financial plan for accomplishing the effort contained in the technical proposal. As a part of its cost proposal, the offeror shall submit the information outlined below, together with supporting breakdowns. All direct costs (labor, material, travel, computer, etc.) as well as labor and overhead rates should be provided by contractor fiscal year (CFY). Detailed cost element breakdowns by

Government Fiscal Year or calendar year are not required. The supporting schedules may include summary level estimating rationale used to generate the proposed costs.

The cost element 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 RFO 15.404-8(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 RFO 15.404-8(a)(2). 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) See information provided in basic ARA announcement (Section IV).

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

Submission: Proposals must be submitted electronically to the Contracting Points of Contact (POCs):

Lesley Breitzman, Contract Specialist, AFRL/RFZW, lesley.breitzman@us.af.mil

Richard Bailey, Contracting Officer, AFRL/RFZW, richard.bailey.26@us.af.mil

Type of Contract/Instrument: The Government may award any appropriate contract type under the FAR or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. The Air Force intends to award a FAR based action. It is anticipated that awards under this Call will generally be Cost type with Cost Plus Fixed Fee (CPFF) completion type contracts. Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

Contract Structure: As shown in the model contract (Attachment 7), the CLIN structure of the contract will include a singluar Experimentation, Evaluation & Assessment CLIN (e.g. CLIN 0001) for the entire scope of effort at the time of award. As external funding sources are identified (e.g. F-35, F-22, LARICM, etc.), the Government may establish standalone CLINs for specific external customer projects that are included in the scope and cost/price of CLIN 0001. This contract structure ensures proper alignment of project to funding source and appropriate obligation and expenditure of funding. The details of each external customer CLIN (i.e. estimated cost/price, period of performance, deliverables, etc.) will be determined internally within the Government. An administrative contract modification will be executed unilaterally by the Contracting Officer to establish the standalone external customer CLIN and decrease the cost/price of CLIN 0001 (i.e. overall no change in contract price). There will be no further negotiation for these CLINs as the project(s) and cost/price are included in the scope of the overall effort and cost/price of CLIN 0001.

Estimated Call Value: The total estimated call value is $74,633,000.00 (the AF reserves the right to exceed this amount if determined to be in the best interest of the Government). Each estimated technical area contract value is further listed in Section II below.

Anticipated Number of Awards: The Air Force anticipates awarding two (2) CPFF completion contracts (one (1) contract each) for the two technical area identified in this call. However, the Air Force reserves the right to award one, all, or none of the proposals. Offerors may submit proposals for one or both of the technical area SOO’s.

Brief Call Summary: See referenced Statements of Objectives (SOO). Offeror must request Attachments 1, and/or 2 for the technical area SOO’s, as well as Attachment 5 DD254 from the Contract Specialist/ Contracting Officer.

Communication Between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

mailto:lesley.breitzman@us.af.mil mailto:richard.bailey.26@us.af.mil mailto:edward.rooks.1@us.af.mil

Address technical questions to the Technical POCs:

Primary Technical POC Secondary Technical POC Robert Desonia Edward Rooks

AFRL/RFLW AFRL/RFLW

2241 Avionics Circle, WPAFB, OH 45433 2241 Avionics Circle, WPAFB, OH 45433 robert.desonia.1@us.af.mil edward.rooks.1@us.af.mil

Address contracting questions to the Contracting POCs:

Lesley Breitzman Richard Bailey Contract Specialist Contracting Officer

AFRL/RFZW AFRL/RFZW

lesley.breitzman@us.af.mil richard.bailey.26@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Photonics and Optical Dominance Division (AFRL/RFLW) is soliciting technical and cost proposals on the following research effort. Unless otherwise stated in this call, all requirements listed within the basic ARA solicitation are considered applicable. See basic ARA for further detailed descriptions of items listed below.

1. Statement of Objective/Needs: The overarching objective of the ADEPT program is to create pre-emptive or reactive countermeasure solutions-including expendable, directed energy, and novel developmental concepts-to protect U.S. and allied aircraft and aircrew in contested airspace.

Multiple science & engineering (S&T) skillsets, such as the following, are required to meet this overall objective:

• Threat software and hardware exploitation

• Laboratory threat evaluation and assessment

• Laser-based testing

• Open-air testing

• Digital engineering using Modelling, Simulation, and Analysis (MS&A)

• Missile aeronautics modelling

• Aircraft and flare signature modelling in the various Electro-Optical (EO) bands

• High-performance computing optimization

• Prototype Countermeasure (CM) hardware creation

Missile Warning Systems (MWS) performance data is another necessary component for effective countermeasure evaluation. AFRL’s Integrated Threat Warning Laboratory (ITWL) or other groups within the Department of War (DoW) and Allies will be utilized for MWD data.

mailto:robert.desonia.1@us.af.mil mailto:edward.rooks.1@us.af.mil mailto:lesley.breitzman@us.af.mil mailto:richard.bailey.26@us.af.mil

The ADEPT program and associated tasks are divided into two technical areas:

1. Hardware & Executable Analysis of Threats (HEAT)- focusing on threat hardware and software exploitation. The objective of this technical area is to generate a foundational understanding of foreign EO-guided threats and to produce high-fidelity, critical modeling inputs of those systems. The primary outputs will be used to inform the broader ADEPT program's countermeasure design and Research, Development, Testing & Evaluation ( RDT&E) efforts.

The scope of threats includes foreign EO-guided missiles, associated launch equipment, and other airborne threats such as high-speed loitering drones.

2. Advanced Countermeasure Engineering (ACE)- focusing on providing continuous, highly specialized scientific and engineering support to characterize emergent threats, execute complex laboratory and open-air testing, and iteratively develop digital threat models. Efforts will directly feed intelligence databases and inform parallel countermeasure design efforts within the ADEPT portfolio.

An overarching task that bridges all the above technical areas is countermeasure design. To accomplish this task, collaboration between all technical areas is expected.

Each technical area should include the primary objective to create and improve countermeasure technologies to increase aircraft and aircrew survivability. Using data from all the technical areas above, the government seeks to improve countermeasure techniques and technologies for transition to operational use.

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

3. Deliverable Items:

a. Data Items: See Attachment 4, CDRLs

b. Software: The contractor shall develop software as required by the Statement of Objectives. Software development may include (but is not limited

to) software of image & signal processing algorithms, software interfaces, data processing, modeling and simulation.

c. Hardware: Specific examples of hardware include equipment purchases or equipment upgrades to support the R&D work being performed. The contractor shall deliver all hardware equipment and non-consumed materials developed and/or acquired under this contract to the Government at the conclusion of this effort.

4. Schedule: Each contract Period of Performance (PoP) will be 84 months overall (81 months technical PoP with 3 months for final reporting).

5. Other Requirements:

a. Program Security Classification: This program security classification level of

TS/SCI and SAP. See DD254 (Attachment 5). Offerors must verify their Cognizant Security Office information is current with Defense Counterintelligence and Security Agency (DCSA) at www.dcsa.mil.

b. Export Control: Information involved in this effort is subject to Export Control (International Traffic in Arms Regulation (ITAR)); therefore, a Certified

DD Form 2345, Militarily Critical Technical Data Agreement, is required to be submitted with the proposal.

c. Contractor Performance Assessment Reporting System (CPARS): CPARS is applicable.

d. Unique/Special Clauses: None.

e. Associate Contractor Agreement: Anticipated. Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that specify requirements for them to share information, data, technical knowledge, expertise, or resources. The Contracting Officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the Contracting Officer will identify associate contractors with whom agreements are required.

f. Options: Not anticipated.

g. EVMS: Not anticipated.

h. Ground and Flight Test: Field and flight tests anticipated.

i. Science and Technology (S&T) Protection: See basic ARA.

6. Other Information:

a. Government Furnished Property (GFP) Availability: Not anticipated.

b. Government Furnished Information (GFI) Software: Modeling System for Advanced Investigation of Countermeasures (MOSAIC) software simulation system, Fast Line-of-Sight Imagery for Target and Exhaust Signatures

(FLITES) synthetic scene generator, Spectral and In-band Radiometric Imaging of Target and Scenes (SPIRITS) software synthetic aircraft signature generator, and Open-Architecture Surrogate Imaging Sensor (OASIS) threat surrogate

c. Base Support/Network Access: Yes, Area B, Bldg. 620, Dynamic Infrared Mobile Evaluation (DIME) Facility, Laser Infrared-countermeasure Development

(RID) Range, DIME Mobile Laboratory (DML), and Wraith Higher Performance Computing (HPC) resources. Access to NIPRNet, SIPRNet, and JWICS to facilitate execution of tasks.

d. Organizational Conflict of Interest (OCI): In order to mitigate any potential OCI, as prescribed in RFO 9.507-1:

http://www.dcsa.mil/

POTENTIAL ORGANIZATIONAL CONFLICT OF INTEREST

(a) There is potential organizational conflict of interest (see RFO Subpart 9.5, Organizational and Consultant Conflicts of Interest) due to the likelihood of prospective contractors gaining access to other companies’ proprietary information during contract performance. Accordingly:

(1) Restrictions are needed to ensure that the proprietary information is safeguarded, and to prevent the contractor from having an unfair competitive advantage in concurrent or future acquisitions. The applicable time period for this restriction is during contract performance and for as long as the information remains proprietary.

(2) As a part of the proposal, the offeror shall provide the contracting officer with complete information of previous or ongoing work that is in any way associated with the contemplated acquisition.

(b) The organizational conflict of interest clause in this solicitation may not be modified or deleted.

ORGANIZATIONAL CONFLICT OF INTEREST

(a) The following restrictions and definitions apply to prevent conflicting roles which may bias the Contractor's judgment or objectivity, or to preclude the Contractor from obtaining an unfair competitive advantage in concurrent or future acquisitions.

(1) Descriptions or definitions:

"Contractor" means the business entity receiving the award of this contract, its parents, affiliates, divisions and subsidiaries.

"Development" means all efforts towards solution of broadly-defined problems. This may encompass research, evaluating technical feasibility, proof of design and test, or engineering of programs not yet approved for acquisition or operation.

"Proprietary Information" means all information designated as proprietary in accordance with law and regulation, and held in confidence or disclosed under restriction to prevent uncontrolled distribution. Examples include limited or restricted data, trade secrets, sensitive financial information, and computer software; and may appear in cost and pricing data or involve classified information.

"System" means the system that is the subject of this contract.

"System Life" means all phases of the system's development, production, or support.

"Systems Engineering" means preparing specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, and supervising design.

"Technical Direction" means developing work statements, determining parameters, directing other Contractors' operations, or resolving technical controversies.

(2) Restrictions: The Contractor shall perform systems engineering and/or technical direction, but will not have overall contractual responsibility for the system's development, integration, assembly and checkout, or production. The parties recognize that the Contractor shall occupy a highly influential and responsible position in determining the system's basic concepts and supervising their execution by other Contractors. The Contractor's judgment and recommendations must be objective, impartial, and independent. To avoid the prospect of the Contractor's judgment or recommendations being influenced by its own products or capabilities, it is agreed that the Contractor is precluded for the life of the system from award of a DoD contract to supply the system or any of its major components, and from acting as a subcontractor or consultant to a DoD supplier for the system or any of its major components.

(b) The Contractor may gain access to proprietary information of other companies during contract performance. The Contractor agrees to enter into company-to-company agreements to: (1) protect another company's information from unauthorized use or disclosure for as long as it is considered proprietary by the other company; and, (2) to refrain from using the information for any purpose other than that for which it was furnished. For information purposes, the Contractor shall furnish copies of these agreements to the contracting officer. These agreements are not intended to protect information which is available to the Government or to the

Contractor from other sources and furnished voluntarily without restriction.

(c) The Contractor agrees to accept and to complete all issued task orders, and not to contract with Government prime Contractors or first-tier subcontractors in such a way as to create an organizational conflict of interest.

(d) The above restrictions shall be included in all subcontracts, teaming arrangements, and other agreements calling for performance of work which is subject to the organizational conflict of interest restrictions identified in this clause, unless excused in writing by the contracting officer.

e. Data Rights: Unlimited data rights are desired for this call. See detailed information contained within the basic ARA. Data Rights asserted by the contractor should be included with submission as part of the Section K (Reps and Certs – Attachment 6).

II. Award Information:

1. Anticipated Award Date: 22 March 2027

2. Anticipated funding:

ADEPT Program Value - Overall

FY27 ($K) FY28 ($K) FY29 ($K) FY30 ($K) FY31 ($K) FY32 ($K) FY33 ($K) Total ($K)

11,249 8,741 10,907 10,753 10,935 10,941 11,107 74,633

Tehcnical Area 1-Hardware & Executable Analysis of Threats (HEAT)

FY27 ($K) FY28 ($K) FY29 ($K) FY30 ($K) FY31 ($K) FY32 ($K) FY33 ($K) Total ($K)

1,775 1,645 1,915 1,985 2,055 2,125 2,195 13,695

Technical Area 2- Advanced Countermeasure Engineering (ACE)

FY27 ($K) FY28 ($K) FY29 ($K) FY30($K) FY31 ($K) FY32 ($K) FY33 ($K) Total ($K)

9,474 7,096 8,992 8,768 8,880 8,816 8,912 60,938

This funding plan is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

III. Eligibility Information:

1. Eligible Offeror: This is an unrestricted solicitation.

2. Other:

a. Foreign Participation: Foreign Participation is not authorized on this call due to the sensitive nature of the technology and its level of classification.

b. Export Control: This acquisition involves data that is subject to export control laws and regulations. Offeror must submit a copy of their approved DD Form 2345, Military Critical Technical Data agreement with their proposal.

NOTE: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date, as identified in this call.

IV. Proposal Review Information:

1. Proposal – Peer or Scientific Review Criteria: Proposals will be evaluated through Peer or Scientific Review using the criteria below, in equal order of importance:

a. Technical Merit:

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

2) Soundness of the offeror’s technical approach, including whether the proposal demonstrates related experience and qualifications of technical personnel.

3) Proposal’s potential to advance technology and the state of the art as well as to meet mission and agency needs.

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

b. Cost/Price: The cost/price criterion includes the realism of the proposed cost.

Cost/Price is a substantial factor for each technical area but ranked as the second order of priority. (If an offeror proposes the use of GFP other than any GFP identified in this Call, and that proposed GFP provides the offeror an unfair competitive advantage, then RFO 45.202 requires rental equivalent be applied to the Cost Factor for evaluation purposes only).

Note: Upon evaluation, the technical area proposal must be categorized as “selectable” in order to be considered for award.

2. Proposal – Review and Selection Process:

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

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

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

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.

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

V. Award Administration Information:

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

VI. Other Information:

Proposal Content Checklist: See Basic ARA.

ATTACHMENTS:

Attachment 1: Placeholder TA 1 HEAT Statement of Objectives (SOO)

Attachment 2: Placeholder TA 2 ACE Statement of Objectives (SOO)

Attachment 3: AFRL/PZL SOW Supplemental Requirements

Attachment 4: Contract Data Requirements List (CDRLs)

Attachment 5: Placeholder Draft Contract Security Classification Specification (DD254)

Attachment 6: Section K (Reps/Certs)

Attachment 7: Model Contract