Attachment 2 - SOW Supplemental Requirements.pdf

Solicitation, Attachment 2

FA2377-26-R-B014

Statement of Work (SOW)

Supplemental Requirements (AFRL/PZL) 13 April 2026

The following paragraphs are also considered be a part of the SOW requirements and the Contractor is responsible for compliance to the same extent as the rest of the SOW.

1. Implementation of Disclosure of Information:

In order to comply with R-DFARS 252.204-7000, Disclosure of Information, the following copies of the information to be released are required at least 50 days prior to the scheduled release date:

a. One (1) copy(ies) to: Kathryn Skaleski, Contracting Officer

b. One (1) copy(ies) to: Brandon Kalbfleish, Program Manager

2. Packaging and Marking:

a. All hardware deliverable contract items shall be packaged in accordance with established commercial practices.

b. When special delivery and/or handling instructions are required, all boxes and/or crates must contain the following statement in plain sight and in bold letters:

INSTRUCTION TO RECEIVING OFFICE – DO NOT OPEN; CONTENTS ARE SENSITIVE TO

DAMAGE WHEN IMPROPERLY OPENED OR HANDLED. CONTACT THE RESPONSIBLE

TECHNICAL PROJECT OFFICER IMMEDIATELY UPON RECEIPT. CONTACT INFORMATION:

Brandon Kalbfliesh, AFRL/RYWN, brandon.kalbfriesh@us.af.mil, 937-713-4416

3. Program Manager:

The Government Program Manager for this effort is Brandon Kalbfliesh, AFRL/RYWN, brandon.kalbfriesh@us.af.mil, 937-713-4416.

4. Implementation of Patent Rights Clause:

a. Interim or Final Invention Reports 1) listing the subject invention(s) and stating that all subject inventions have been disclosed, or 2) stating that there are no such inventions, shall be sent to both the Administrative Contracting Officer at the address located on the face page of the contract award and to AFRL/PZL Patent Reporting at afmclo.jaz@us.af.mil within the timeframes specified in the Patent Rights clause of this contract.

b. Contractors shall use DD Form 882, Report of Inventions and Subcontracts, to submit these reports. The DD Form 882 shall also be used for the notification of an award of any subcontract(s) for experimental, developmental, or research work which contain a “Patent Rights” clause.

c. All other notifications required by the contract shall also be sent to the individuals in paragraph

a. This provision also constitutes the request for the following information for any subject invention for which the Contractor has retained ownership: (1) the filing date, (2) the serial number and title, (3) a copy of the patent application, and (4) the patent number and issue date.

Submittal shall be to AFRL/PZL Patent Reporting at afmclo.jaz@us.af.mil.

mailto:brandon.kalbfriesh@us.af.mil mailto:brandon.kalbfriesh@us.af.mil mailto:afmclo.jaz@us.af.mil mailto:afmclo.jaz@us.af.mil

5. Information Regarding Non-U.S. Citizens Assigned to this Project:

a. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S.

Government Information Technology (IT) networks in connection with the work on this contract must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. Department of State under international personnel exchange agreements with foreign governments. It also does not apply to dual citizens who possess U.S. citizenship, to include Naturalized citizens. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. Specific format for a waiver request will be provided upon request to the Contracting Officer. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

b. For purposes of paragraph a above, if an IT network/system does not require AFRL to endorse a Contractor’s application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires a U.S. Government sponsor to endorse the application in order for access to the IT network/system, AFRL will only endorse the following types of applications, consistent with the requirements above:

i. Contractor employees who are U.S. citizens performing work under this contract.

ii. Contractor employees who are non-U.S. citizens and who have been granted a waiver.

6. Operation Security (OPSEC):

a. Operations Security (OPSEC) must be an integral part of our daily activities. As we maintain security on our future technologies that are vital to national interest, we must recognize and prepare for the threat poised against our technology. Department of Defense policies mandate a high degree of security throughout the acquisition process. However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when our technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this contract be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in SOW. The contractor shall ensure employees receive training and follow appropriate Operations Security (OPSEC) measures during the performance of the contract.

b. This program mandates that contractor and subcontractor personnel maintain OPSEC posture by training all contract personnel involved in this effort. The contractor must ensure that employees complete Level I OPSEC training within 30 calendar days of joining the project team.

Additionally, employees are required to complete annual OPSEC awareness training. Training can be provided by the company or accessed online here:

https://securityawareness.usalearning.gov/opsec/index.htm

c. Contractor employees during the performance of this effort may be required to have access to Critical Technology Elements (CTE), Enabling technologies, Critical Program Information (CPI) or other potential sensitive information. Contractor employees will be required to protect this information from disclosure to unauthorized personnel and companies. If a disclosure occurs, the contractor shall notify the Government program and security office within 24 hours of any security incidents involving the loss, compromise, or suspected compromise of CTE/CPI. The https://securityawareness.usalearning.gov/opsec/index.htm notification must be made through secure means (encrypted email, secure email, or secure/encrypted call) appropriate to the level of the information involved. Following notification to the government program or security office, the contractor shall assist with all inquiry and investigation reports, and, if applicable, participate in a damage assessment.

7. Science and Technology (S&T) Protection (AFRLI 61-113):

The requirements below are in accordance with Air Force Research Laboratory Instruction (AFRLI) 61- 113, “S&T Protection for the Air Force Research Laboratory” and only required when there is a S&T plan called out in one of the following documents SOW, PWS, DD form 254 or is requested by the Requirements Owner.

a. S&T Protection Plan Requirement: The contractor is required to follow the S&T Protection Plan, or a comparable document (i.e. Program Protection Plan, Program Specific Protection Plan), which will be provided by the Government program or security office under a separate cover. This adherence must be maintained throughout the execution of this project effort. If applicable, the contractor shall integrate any prior planning related to the baseline system or related research, technology or program and contribute feedback for future updates to the plan. Additionally, the contractor shall develop a comprehensive Protection Implementation document detailing how they will adhere to the S&T Protection Plan through submission of the Protection Implementation Plan CDRL A013. This document must outline the training and equipping of all employees, subcontractors, vendors and other relevant personnel to ensure compliance with the plan. The contractor is also responsible for providing regular updates and keeping the program office informed of progress and any changes as the project or program advances. The contractor shall promptly inform the Government program office and security of any non-compliances within the S&T Protection Plan.

i. Also, as applicable, the contractor shall also provide a detailed plan on how they intend to address and rectify these security or requirement gaps with a detailed timeline. These documents shall be sent through secure means. Coordination with the Government program or security office must occur prior to sending information via mail or digitally.

8. Risk Identification and Security Countermeasures (RISC):

The requirements below are in accordance with Air Force Research Laboratory Instruction (AFRLI) 61- 113, “S&T Protection for the Air Force Research Laboratory” and required by AFRL/CC.

a. Security RISC Review:

i. Initial/Annual/New Research and Related (R&R) Senior/Key Person Profile: In accordance with CDRL A014, the Contractor shall provide R&R Senior/Key Person Profile Worksheet(s) throughout the lifecycle of this effort as follows: 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) ad hoc report when any new Senior/Key Personnel join the contract. Contractor shall obtain coordination from the Government on all ad hoc R&R Senior/Key Person Profile Worksheet(s) prior to the covered employee(s) receiving access to S&T information.

ii. If, at any time, during performance of this award, the contractor/subcontractor learns that its Senior/Key Research Personnel are or are believed to be participants in a Foreign Government Talent Program or have Foreign Components with a strategic competitor or country with a history of targeting U.S. technology for unauthorized transfer, the contractor shall notify the Contracting Officer no later than 5 business days from the date at this information became known.

iii. In the event a security risk is identified, and the Government determines the security risk exceeds the acceptable threshold, the Contracting Officer will promptly notify the Contractor of the Government’s recommended course of action, which may include full or partial termination of award. The Government will provide as much information/rationale as OPSEC measures allow for. In the event the Contractor wishes to challenge the Government’s decision, fundamental research awards will follow the OSD R&E Memorandum dated 6 Jun 2023. All other awards follow the Ombudsman procedures in Paragraph 11 of this document.

iv. Contractor shall flow down this requirement to all subcontractors involved in the performance of research under this effort.

9. Test Safety/Planning Requirements:

a. Contractor Support for AFRL Research Test Review, Approval and Oversight: The contractor shall comply with Air Force Research Laboratory Instruction (AFRLI) 61-103, AFRL Research Test Review, Approval and Oversight, which establishes policy for how AFRL reviews, approves, and oversees research test activities. AFRLI 61-103 paragraph 1.2 defines “test” to include laboratory and field tests, experiments and demonstrations and that this guidance applies to all AFRL test activities that involve AFRL assets (full or part ownership) or AFRL personnel (government civilian, military, and support contractors), and tests executed by organizations under contract to AFRL where AFRL holds either mishap investigative responsibility or has more than a minimal risk of liability. Paragraph 1.2.3 further defines which tests are “ground tests” and paragraph 1.3 clarifies which activities are “out of scope” for this instruction. Paragraph 2.10 describes the roles and responsibilities of program managers, scientists and engineers conducting applicable government and contractor test activities.

b. Contractor Support to Program Test Planning and Design Reviews: The contractor shall support test planning meetings and (a) design review(s) during the course of the program. The review(s), the(ir) timing, and the topics to be covered will be determined jointly among the contractor, the AFRL PM, the PM’s division technical advisor (if desired), and AFRL/DO (as applicable). The contractor shall submit the review agenda to the government for review and approval at least 15 days prior to the desired review date. Review topics shall include at a minimum technical objectives and success criteria, test article description, vehicle modifications, safety systems, airworthiness of vehicle(s) and subsystems, preliminary test plans and schedules, and instrumentation system requirements. [Reference AFRLI 61-103 (Parent and Volume 1), AFRLI 61-601]

c. Contractor Test Plan and Support to the AFRL Technical Review Boards (TRBs) and Safety Review Boards (SRBs): The contractor shall develop a flight test plan and secure AFRL approval of it prior to flight testing, to include high-speed taxi tests. The contractor will submit the draft test plan (using contractor or AFRL-specified format) to the government for review and approval at least eight (8) weeks prior to testing and the final test plan at least six

(6) weeks prior to testing. The contractor shall support safety and technical reviews, either through in-person attendance or participation via telecommunication means. The nature and scope of contractor support to the reviews will be made by the PM and government technical and safety review board chairs. The contractor shall complete any post-TRB or post-SRB actions generated by those reviews. [Reference AFRLI 61-103 (Parent and Volume 1), AFRLI 61-601]

d. Contractor Support to Air Force Mishap Investigations: In accordance with AFI 91-204 and AFRLI 61-103 Vol 1, the Contractor shall cooperate with any safety investigation in the event of a mishap (defined as an unplanned event, or a series of events, that result in damage to DoD property, occupational illness to DoD military or civilian personnel, injury to DoD military personnel on- or off-duty, injury to on-duty civilian personnel; damage to public or private property or injury and illness to non-DoD personnel caused by DoD operations). If requested by the PCO, the contractor shall immediately secure the mishap scene and/or damaged property and applicable records until released by the investigating Safety Office. If the Government investigates the mishap, the contractor and subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed. If requested by the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. This includes, but is not limited to, providing the government immediate access to all test data, test-related documents, and vehicle documentation including, but not limited to, video, pictures, witness statements, onboard recorded data, telemetered data, vehicle systems checks, and vehicle or system squawk sheets.

In accordance with AFI 91-204, paragraph 2.12, the contractor shall report mishaps involving injury or damage to USAF personnel or property. If an AFRL representative is not present during the mishap, the contractor shall notify the AFRL PM or AFRL/DO of the mishap as soon as practicable after the mishap has been debriefed at the test location, but not later than eight

(8) hours immediately following the mishap. If the AFRL PM or AFRL/DO cannot be reached in person, the contractor shall execute the alternate notification procedures as specified on the AFRL Unexpected Event Worksheet. In the event of a mishap, the data and information collected must be protected in accordance with guidance provided by a cognizant government representative. It is recommended that the contractor have an established safety representative made known to the government through whom communication will occur and the data and information collected will be transmitted. [Reference AFRLI 61-103 Volume 1, AFI 91-204]

e. Contractor-Identified Lessons Learned: At the completion of the program the contractor shall provide lessons learned to the government using AFRL Form 20, Lessons Learned.

Insights gained during the formulation, conduct, and reporting of flight test activities to include system under test design and development shall be included. However, in the case of a lesson learned that is safety related, the contractor shall notify the government immediately.

[Reference AFI 91-202 AFRL Supplement]

f. Flight Test Vehicle Airworthiness: The contractor shall provide sufficient technical documentation and detail of the vehicle and modifications, of operator experience, safety and mishap history of the air vehicle, and design/procedural safety precautions to support the government independent airworthiness assessment and associated issuance of a Civil/Public Air Operations (CAO or PAO) Letter or Military Flight Release (MFR) whichever is applicable.

The contractor shall support government reviews conducted in the course of the airworthiness assessment process. The contractor shall support Continuing Airworthiness Maintenance and Operations (M&O) on-site inspections or remote interviews conducted by the government (as applicable) [Reference AFRLI 61-601; Airworthiness Bulletins (AWB) issued by the Air Force Airworthiness Office as current and applicable]

g. Liability and insurance: The Contractor shall be responsible for, and hold the Government harmless from, loss of or damage to non-government property. The Contractor shall be responsible for, and hold the Government harmless from, bodily injury and death of persons, resulting either in whole or in part from the negligence or fault of the Contractor, its officers, agents, or employees in the performance of work under this contract.

10. Elimination of Use of Class I Ozone Depleting Substances (ODS)

Contractors shall not:

a. Provide any service or product with any specification, standard, drawing, or other document that requires the use of a Class I ODS in the test, operation, or maintenance of any system, subsystem, item, component, or process; or

i. Provide any specification, standard, drawing, or other document that establishes a test, operation, or maintenance requirement that can only be met by use of a Class I ODS as part of this contract.

b. For the purposes of Department of the Air Force policy, the following products that are pure (i.e., they meet the relevant product specification identified in AFI 32-7086[AR2] ) are Class I ODSs:

i. Halons: 1011, 1202, 1211, 1301, and 2402;

c. Chlorofluorocarbons (CFCs): CFC-11, CFC-12, CFC-13, CFC-111, CFC-112, CFC-113, CFC-114, CFC-115, CFC-211, CFC-212, CFC-213, CFC-214, CFC-215, CFC-216, and CFC-217, and the blends R-500, R-501, R-502, and R-503; and

i. Carbon Tetrachloride, Methyl Chloroform, and Methyl Bromide.

11. Ombudsman

a. An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the program manager, contracting officer, or source selection official. Further, the ombudsman does not participate in the evaluation of proposals, the source selection process, or the adjudication of protests or formal contract disputes. The ombudsman may refer the interested party to another official who can resolve the concern.

b. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution.

Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contests of OMB Circular A-76 competition performance decisions).

c. If resolution cannot be made by the contracting officer, the interested party may contact the ombudsman, AFRL/PK Technical Director; Alternate Ombudsman, AFRL/PK Deputy Director of Contracting, 1864 4th Street, WPAFB, OH 45433, 937-503-2186, AFRL.PK.WORKFLOW@us.af.mil. Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/MAJCOM/FLDCOM/DRU ombudsman level, may be http://static.e-publishing.af.mil/production/1/af_a4/publication/afi32-7086/afi32-7086.pdf https://usaf.dps.mil/sites/AFCC/AQCP/KnowledgeCenter/SitePages/DAF-Contracting-Compass/Part-23---Environment,-Sustainable-Acquisition,-and-Material-Safety.aspx?CID=d7c975cb-ed41-49ba-8b44-9279666ee32b#_msocom_2 brought by the interested party for further consideration to the Department of the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-2395, facsimile number (571) 256-2431.

d. The ombudsman has no authority to render a decision that binds the agency.

e. Do not contact the ombudsman to request copies of the solicitation, verify offer due date, or clarify technical requirements. Such inquiries shall be directed to the contracting officer.