J-6 - Model Agreement - CPO TCs.docx

Partnership Intermediary Agreement # TBD between The United States Of America

UNITED STATES AIR FORCE (USAF), AIR FORCE RESEARCH LAB (AFRL), DODAAC # FA9550 AF OFFICE OF SCIENTIFIC RESEARCH (AFOSR)

875 N. RANDOLPH ST. ROOM 3112

ARLINGTON, VA 22203

and

PI TBD, CAGE CODE # TBD

PI ADDRESS TBD

Concerning Collaborative Project Order # TBD

Total Award Amount of the CPO Agreement: $TBD

(unexercised)

OY2

(unexercised)

OY3

(unexercised)

OY4

(unexercised) 6 mos.

Extension of Services

Total Government Funded Share: $TBD

Total Recipient Funded Share: $TBD

Authority: 15 U.S.C. 3715

Effective Date: TBD

Catalog of Federal Domestic Assistance #: 12.800 – Air Force Defense Research Sciences Program

For: For the United States of America

TERMS AND CONDITIONS INCORPORATED BY REFERENCE:

This CPO incorporates terms and conditions from PIA # TBD by reference, with the same force and effect as if they were given in full text:

PART 1 - ADMINISTRATIVE INFORMATION

ARTICLE 1.1 - BACKGROUND, AUTHORITY, AND DEFINITIONS (DEC 2025)

ARTICLE 1.2 - ADMINISTRATIVE REQUIREMENTS, DISAGREEMENTS (APR 2024)

PART 2 - TERM

ARTICLE 2.7 - COLLABORATIVE PROJECT ORDERING (CPO) PROCEDURES (DEC 2025)

ARTICLE 2.9 - TRAFFICKING IN PERSONS (JAN 2026)

ARTICLE 2.10 - ENFORCEMENT (DEC 2025)

ARTICLE 2.11 - ANNUAL ELIGIBILITY REVIEW (JAN 2026)

PART 3 - MANAGEMENT OF THE PROGRAM

ARTICLE 3.1 - PROPERTY STANDARDS (JAN 2026)

ARTICLE 3.3 - BASE SUPPORT (JAN 2026)

ARTICLE 3.4 – PARTNERSHIP INTERMEDIARY ACCESS TO GOVERNMENT INSTALLATIONS (DEC 2025)

ARTICLE 3.5 - COMMON ACCESS CARDS (CAC) FOR PI PERSONNEL (DEC 2025)

ARTICLE 3.8 – PROGRAM MANAGEMENT PLANNING PROCESS (JAN 2026)

PART 4 - FINANCIAL MATTERS

ARTICLE 4.3 - PROGRAM INCOME (DEC 2025)

ARTICLE 4.5 - STANDARDS FOR FINANCIAL MANAGEMENT (DEC 2025)

ARTICLE 4.6 - AUDIT REQUIREMENTS (DEC 2025)

ARTICLE 4.8 - REVISION OF PRICE PROPOSAL BUDGETS AND PROGRAM PLANS (DEC 2025)

PART 5 - CLAIMS, DISPUTES AND APPEALS

ARTICLE 5.1 - CLAIMS, DISPUTES, AND APPEALS (DEC 2025)

PART 6 - INTELLECTUAL PROPERTY RIGHTS

ARTICLE 6.1 - PROTECTION OF PROPRIETARY INFORMATION (DEC 2025)

ARTICLE 6.2 - DATA RIGHTS (DEC 2025)

ARTICLE 6.3 - INVENTIONS (JAN 2026)

ARTICLE 6.4 - RIGHTS NOT EXCLUSIVE AND TREATMENT OF GOVERNMENT FURNISHED INFORMATION CONCERNING INVENTIONS (JAN 2026)

ARTICLE 6.5 - EXPORT CONTROL (JAN 2026)

ARTICLE 6.6 - USING TECHNICAL INFORMATION RESOURCES (JAN 2026)

ARTICLE 6.7 - FOREIGN DISCLOSURE (JAN 2026)

PART 7 - TECHNICAL AND FINANCIAL REPORTING

ARTICLE 7.1 - ANNUAL PROGRAM PLAN (JAN 2026)

ARTICLE 7.2 - ANNUAL REPORTING (JAN 2026)

ARTICLE 7.3 - QUARTERLY ACTIVITY REPORTS (JAN 2026)

ARTICLE 7.7 - REPORTING SUBAWARDS AND EXECUTIVE COMPENSATION (JAN 2026)

ARTICLE 7.9 - DISCLOSURE OF INFORMATION (JAN 2026)

ARTICLE 7.10 - REPORTING OF MATTERS RELATED TO PI INTEGRITY AND PERFORMANCE (JAN 2026)

PART 8 – MISCELLANEOUS

ARTICLE 8.1 - PROCUREMENT SYSTEM (JAN 2026)

ARTICLE 8.3 - POTENTIAL ORGANIZATIONAL & CONSULTANT CONFLICT OF INTEREST (JAN 2026) ARTICLE 8.4 - SYSTEM FOR AWARD MANAGEMENT (SAM), UNIVERSAL ENTITY IDENTIFIER (UEI), & COMMERCIAL AND GOVERNMENT ENTITY (CAGE) REQUIREMENTS (JAN 2026) ARTICLE 8.5 – PROHIBITION ON USING FUNDS UNDER AGREEMENTS WITH ENTITIES THAT REQUIRE CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS (JAN 2026)

ARTICLE 8.6 – ADMINISTRATIVE REQUIREMENTS FOR SUBAWARDS AND CONTRACTS (JAN 2026)

PART 9 - NATIONAL POLICY MATTERS AND ASSURANCES

ARTICLE 9.1 - MILITARY RECRUITING ON CAMPUS (JAN 2026)

ARTICLE 9.3 - ASSURANCES (JAN 2026)

ARTICLE 9.4 - OFFICIALS NOT TO BENEFIT (JAN 2026)

ARTICLE 9.5 - SECTION 889 (JAN 2026)

ARTICLE 9.6 - PROHIBITION ON A BYTEDANCE COVERED APPLICATION (JAN 2026)

TERMS AND CONDITIONS INCORPORATED BY FULL TEXT:

PART 1 - ADMINISTRATIVE INFORMATION

ARTICLE 1.2 - ORDER OF PRECEDENCE (APR 2024) (TAILORED)

In the event of a conflict between the terms of this agreement and other governing documents, the conflict shall be resolved by giving precedence in descending order as follows:

1. Federal statutes

2. Federal regulations

3. 2 CFR § 200, as modified and supplemented by DoD's implementation found in 2 CFR § 1104

4. Partnership Intermediary Agreement # TBD

5. The articles in this CPO

6. The attachments to this CPO

ARTICLE 1.3 - ADMINISTRATIVE RESPONSIBILITIES (DEC 2025)

A. Government representatives are:

AFOSR Contracting Officer:

Bhawana Sharma 875 N. Randolph Street Arlington, VA 22203 Phone: (703) 946-3212 e-mail: bhawana.sharma@us.af.mil

AFOSR Program Manager:

Leah Haugen 875 N. Randolph Street Arlington, VA 22203 Phone: (612) 840-3906 e-mail: leah.haugen.1@us.af.mil

PIA Administrative Office:

TBD

PIA Payment Office:

TBD

Servicing Staff Judge Advocate’s Office (for reporting):

Major Sarah Racataian Frick 875 N. Randolph Street Arlington, VA 22203 Phone: (661) 857-6002 Email: sarah.racataian_frick@us.af.mil

B. For the Partnership Intermediary:

Awardee Name TBD Awardee Address TBD

Contracts Representative:

Name: TBD Address: TBD Phone: TBD E-Mail: TBD

Program Manager:

Name: TBD Address: TBD Phone: TBD E-Mail: TBD

ARTICLE 1.5 – COLLABORATIVE PROJECT ORDER ADMINISTRATIVE RESPONSIBILITIES (JAN 2026) The Collaborative Project Order (CPO) is issued in accordance with Partnership Intermediary Agreement (PIA) number TBD. The PIA is the overarching document governing the CPO. The PIA's terms and conditions are applicable to the CPO unless otherwise noted in the CPO.

PART 2 - TERM

ARTICLE 2.1 - TERM OF THE AGREEMENT (DEC 2025) (TAILORED)

The term of this CPO is 12-months commencing on the effective date shown on the first page of the CPO plus four 12-month Option Years and an optional 6-month extension of services. The current exercised period of performance on this CPO is DD MM YYYY through DD MM YYYY. If all funds are expended prior to the end of the term, the parties have no obligation to continue and may elect to cease performance at that point. Articles in this CPO, which by their express terms or by necessary implication, apply for periods of time other than as specified in this article shall be given effect, notwithstanding this article.

ARTICLE 2.2 – EXTENDING THE TERM (DEC 2025) (TAILORED)

If the parties agree, the term of this CPO may be extended if funds are available, and opportunities reasonably warrant. Any extension shall be formalized through modification of the CPO by the AF Contracting Officer and the PI.

ARTICLE 2.3 - MODIFICATIONS (JAN 2026) (TAILORED)

A. Modifications to this CPO may be proposed by either party. Only the AFOSR Contracting Officer has the authority to act on behalf of the Government to modify this CPO. PI recommendations for any modification to this CPO shall be submitted in writing to the AFOSR Program Manager before the desired effective date with a copy to the AFOSR Contracting Officer. The PI shall detail the technical, chronological, and financial impact of the proposed modification to the program. Changes are effective only after the CPO has been modified. Only a Government Contracting Officer has the authority to act on behalf of the Government to modify this CPO. If the Government agrees to the proposed modification without change, the Government Contracting Officer may issue a modification unilaterally approving the request.

B. The AFOSR Contracting Officer may unilaterally issue minor or administrative CPO modifications (e.g., incremental funding, changes to the payment office or appropriation data, changes to Government personnel identified in this CPO, etc.).

ARTICLE 2.4 – OPTION TO EXTEND THE TERMS OF THE CPO (DEC 2025)

A. The Government may extend the term of this CPO by written notice to the PI within 30 days; provided that the Government gives the PI a preliminary written notice of its intent to extend at least 30 days before the CPO expires. The preliminary notice does not commit the Government to an extension.

B. If the Government exercises any option period, the extended CPO shall be considered to include these option terms.

C. The total duration of this CPO, including the exercise of any options under this clause, shall not exceed 60 (months), plus an additional six months for the optional extension of services.

ARTICLE 2.5 – OPTION TO EXTEND SERVICES (DEC 2025) (TAILORED)

The Government may require continued performance of any services within the limits and at the rates specified in the last option period of the CPO. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the PI within 30 days.

ARTICLE 2.6 - ORDERING PERIOD, TECHNICAL REQUIREMENTS & TOTAL AMOUNT OF THE AGREEMENT (DEC 2025) (TAILORED)

A. Ordering Period: The ordering period for this CPO is a 12-month Base Year and four 12-month Option Years for a total of up to 60 months, plus the 6-month optional extension of services if exercised. The CPO and reports shall be completed and submitted within this period of performance.

B. Technical Requirements: The PI shall perform in accordance with the Statements of Work (SOW) in the Attachments section. The overall management, including technical, programmatic, reporting, and financial and administrative matters, of the coordinated technology transfer program established under this CPO shall be accomplished by the PI.

The PI shall submit all documentation required by the articles in Part 7 of the PIA, “Technical and Financial Reporting”.

The Government shall not exercise any supervision over the PI employees performing services under this CPO.

The AFOSR Program Manager will interact with the PI to promote the effective collaboration between the Air Force, industry, academia, and other Government agencies.

C. The total amount of the agreement: The total Government Share on this agreement shall not exceed $TBD.

ARTICLE 2.8 - TERMINATION (DEC 2025) (TAILORED)

A. The Contracting Officer may terminate this CPO agreement by written notice to the PI upon a finding that the PI has failed to comply with the material provisions of this agreement.

B. Additionally, this agreement may be terminated by either party upon written notice to the other party. Such written notice shall be preceded by consultation between the parties. If the PI initiates the termination, written notification shall be provided to the Contracting Officer at least thirty (30) days prior to the requested effective date. The notification shall state the reasons for the termination, the requested effective date, and, if a partial termination, the portion to be terminated. If the Contracting Officer determines, in the case of a partial termination, that the reduced or modified portion of the award shall not accomplish the purpose for which the award was made, the Contracting Officer may terminate the award in its entirety.

C. The Government and the PI shall negotiate in good faith an equitable reimbursement for work performed toward accomplishment of program goals. The Government shall allow full credit to the PI for the Government share of the obligations properly incurred by the PI prior to termination, and those non-cancelable obligations that remain after the termination.

D. If this agreement is incrementally funded, it may be terminated in the absence of additional government funding as set forth in Article 4.1 entitled “Incremental Funding”.

E. In the event of a termination, the Government shall have a paid-up Government purpose license in any subject invention, copyright work and data made or developed under this agreement.

F. If this agreement is terminated, the Government has the rights identified in and the PI shall comply with Article 8.2 entitled “Closeout, Adjustment, Continuing Responsibilities and Collection-Reimbursement”.

G. Notwithstanding the above, for security or safety reasons or in the case of a serious breach that could lead to irreparable damage, the Contracting Officer may order immediate suspension of work, in whole or in part.

PART 3 - MANAGEMENT OF THE PROGRAM

ARTICLE 3.2 - SCOPE AND MANAGEMENT OF THE PROGRAM (JAN 2026) (TAILORED)

A. The Government and the PI are bound to each other by a duty of good faith and best effort to achieve the goals of this Collaborative Project Order (CPO). This CPO is not intended to be, nor shall it be construed as, by implication or otherwise, a corporation or other business organization.

B. The PI shall perform a coordinated technology transfer/transition program carried out in accordance with the statement of work in the Attachments section. The PI shall submit all documentation required by the articles in Part 7 of the PIA, “Technical and Financial Reporting”.

C. The PI shall accomplish the overall management, including technical, programmatic, reporting, financial and administrative matters, of the coordinated technology transfer/transition program. The Government program manager(s) may interact with the PI to promote effective collaboration between the PI and the Government.

ARTICLE 3.6 - ACCESS TO DoD BASES, GOVERNMENT FACILITIES AND/OR U.S. GOVERNMENT INFORMATION TECHNOLOGY NETWORKS (DEC 2025) (TAILORED)

Information regarding non-US citizens Assigned to this CPO –

A. PI employees requiring access to DoD bases, Government facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with any work under this agreement must be U.S. citizens. For the purposes 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. DoD or U.S. State Department 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. The above requirements are in addition to any other CPO requirements related to obtaining a CAC.

B. For the purposes of paragraph A. above, if an IT network/system does not require AFRL to endorse a PI’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 an U.S. Government sponsor to endorse the application in order for access to the IT network/system; AFRL shall only endorse the following types of applications; consistent with the requirement above:

1. PI employees who are U.S. citizens performing work under this CPO.

2. PI employees who are non-U.S. citizens and who have been granted a waiver.

C. Any additional access restrictions established by the IT network/system owner apply.

ARTICLE 3.7 - USING CLASSIFIED DATA (DEC 2025) (TAILORED)

It is anticipated that the PI may require access to classified data. In the event the PI requires access to classified data, a request for a Security Classification Specification DD Form 254, with supporting information, shall be submitted to the AF Program Manager / Contracting Officer Representative and AF Contracting Officer on the CPO. If the request is determined to be necessary for the effort, a modification to the CPO will be completed to attach a DD 254 and the PI shall comply with the attached DD 254 for the specified project.

PART 4 - FINANCIAL MATTERS

ARTICLE 4.1 - INCREMENTAL FUNDING (DEC 2025) (TAILORED)

A. The ceiling for this CPO shall not exceed $TBD.

B. The Government's share for full performance of this CPO shall not exceed $TBD. Of this amount, only $TBD is allotted and currently available for payment. In no event is the Government obligated to reimburse the PI for expenditures in excess of the total funds allotted by the Government. The Government anticipates that from time-to-time additional amounts will be allotted to the CPO by unilateral modification, until the total Government share is fully funded.

C. To minimize interruption of effort due to lack of funds, the PI shall notify the AF Contracting Officer that issued the CPO in writing whenever the amount of funds expended under the CPO, when added to anticipated costs for the following 60 days, will exceed 75% of the amount allotted by the Government. If, after notification, additional funds are not allotted, the parties agree the CPO may be terminated. The PI is not obligated to continue performance or otherwise incur costs in excess of the amount then allotted by the Government to the CPO until the AF Contracting Officer notifies the PI in writing that the amount allotted by the Government has been increased and specifies an increased amount, which shall then constitute the total amount allotted by the Government to the CPO. When and to the extent that the amount allotted by the Government to the CPO is increased, any costs the PI incurs before the increase that are in excess of the amount previously allotted by the Government to the CPO shall be allowable to the same extent as if incurred afterward, unless the AF Contracting Officer issues a termination or other notice and directs the increase is solely to cover termination or other specified expenses.

ARTICLE 4.2 - ALLOTTED FUNDING & PAYMENT INSTRUCTIONS FOR MULTIPLE ACCOUNTING CLASSIFICATION CITATIONS (JAN 2026) (TAILORED)

A. The following funds are allotted to this agreement:

FSR: TBD

PSR: TBD

DSR: TBD

TBD

FSR: TBD

PSR: TBD

DSR: TBD

TBD

TOTAL OBLIGATED FUNDS TO DATE:

B. Payment instructions for multiple accounting classification citations: This is a multiple funded line-item CPO and additional ACRNs will be assigned when new accounting classifications are available. Funds shall be paid by the specific ACRN listed on each invoice. The PI shall request the AF Program Manager review and provide concurrence that the correct ACRNs are being listed on each invoice. Concurrence from the AFRL Program Manager shall be uploaded as an attachment to the electronic grant voucher Standard Form (SF) 270, Request for Advance or Reimbursement submission through the WAWF application.

ARTICLE 4.7 - RETENTION AND ACCESS TO RECORDS (DEC 2025) (TAILORED)

The PI's financial records, supporting documents, statistical records, and all other records pertinent to this CPO shall be retained and access to them permitted in accordance with 2 CFR § 200.334 through 2 CFR § 200.338.

ARTICLE 4.9 – PAYMENT REIMBURSEMENT IN THE WIDE AREA WORK FLOW (WAWF) APPLICATION IN THE PROCUREMENT INTEGRATED ENTERPRISE ENVIRONMENT (PIEE) (DEC 2025) (TAILORED)

A. The PI shall register in PIEE at https://piee.eb.mil to have access to both the WAWF PIEE and MyInvoice applications. The PI must request payment using an electronic grant voucher Standard Form (SF) 270, Request for Advance or Reimbursement submission through the WAWF application. WAWF has been designated as the Department of Defense (DoD) standard for electronic invoicing and payment. The PI can check the status of their payments through the WAWF PIEE or my Invoice applications.

B. The electronic funds transfer (EFT) payment method must be used for this CPO.

C. The following codes will be required to process SF 270 submissions and route requests and emails correctly through the WAWF PIEE application:

D. Most payments are made within 30 calendar days as described at 2 CFR 200.305. The PI can check the status of their payments through the WAWF PIEE or my Invoice applications. The customer service telephone number for Defense Finance and Accounting Services (DFAS) is 1-800-756-4571 Option 4, then select the option associated with the pay office DODAAC indicated in the table above. For additional information, you may also visit DFAS website at https://www.dfas.mil/dfas/AskDFAS/.

ARTICLE 4.10 – LIMITATION ON GOVERNMENT LIABILITY (JAN 2026) (TAILORED)

In performing this CPO, the PI is not authorized to make expenditures or incur obligations exceeding the amount obligated by the Government. In no event is the Government obligated to reimburse the Recipient for expenditures in excess of the total funds allotted by the Government.

ARTICLE 6.8 – FOREIGN ACCESS TO TECHNOLOGY (JAN 2026) (TAILORED)

A. Definitions.

"Foreign firm or institution" means a firm or institution organized or existing under the laws of a country other than the United States, its territories, or possessions. The term includes, for purposes of this agreement, any agency or instrumentality of a foreign government, and firms, institutions or business organizations which are owned or substantially controlled by foreign governments, firms, institutions, or individuals.

"Know-how" means all information including, but not limited to, discoveries, formulas, materials, inventions, processes, ideas, approaches, concepts, techniques, methods, software, programs, documentation, procedures, firmware, hardware, technical data, specifications, devices, apparatus and machines.

"Technology" means discoveries, innovations, know-how and inventions, whether patentable or not, including computer software, recognized under U.S. law as intellectual creations to which rights of ownership accrue, including, but not limited to, patents, trade secrets, mask works, and copyrights developed under this agreement.

B. General.

The parties agree that collaboration findings may constitute a significant enhancement to the national defense, and to the economic vitality of the United States. Accordingly, access to important technology developments under this CPO by foreign firms or institutions must be carefully controlled. The controls contemplated in this article are in addition to, and are not intended to change or supersede, the provisions of the International Traffic in Arms Regulation (22 CFR pt. 120 et seq.), the DOD National Industrial Security Program Operating Manual (NISPOM) (32 CFR pt. 117) and the Department of Commerce Export Regulation (15 CFR pt. 770 et seq.)

C. Restrictions on Sale or Transfer of Technology to Foreign Firms or Institutions.

1. In order to promote the national security interests of the United States and to effectuate the policies that underlie the regulations cited above, the procedures stated in subparagraphs C.2, C.3, and C.4 below shall apply to any transfer of technology. For purposes of this paragraph, a transfer includes a sale of the company, and sales or licensing of technology. Transfers do not include:

(i) sales of products or components, or

(ii) licenses of software or documentation related to sales of products or

(iii) transfer to foreign subsidiaries of the Recipient (Recipient participants) for purposes related to this agreement, or

(iv) transfer which provides access to technology to a foreign firm or institution which is an approved source of supply or source for the conduct of research under this agreement provided that such transfer shall be limited to that necessary to allow the firm or institution to perform its approved role under this agreement.

2. The PI shall provide timely notice to the Government of any proposed transfer from the recipient of technology developed under this agreement to foreign firms or institutions. If the Government determines that the transfer may have adverse consequences to the national security interests of the United States, the PI, its subawardees, subcontractors, vendors, and the Government shall jointly endeavor to find alternatives to the proposed transfer which obviate or mitigate potential adverse consequences of the transfer but which provide substantially equivalent benefits to the PI.

3. In any event, the PI shall provide written notice to the AF Contracting Officer and AF Program Manager / Contracting Officer Representative of any proposed transfer to a foreign firm or institution at least 60 days prior to the proposed date of transfer. Such notice shall cite this article and shall state specifically what is to be transferred and the general terms of the transfer. Within 30 days of receipt of the PI's written notification, the AF Contracting Officer shall advise the PI whether it consents to the proposed transfer. In cases where the Government does not concur or 60 days after receipt and the Government provides no decision, the PI may utilize the procedures under the article in the PIA entitled Claims, Disputes and Appeals. No transfer shall take place until a decision is rendered.

4. Except as provided in subparagraph C.1 above and in the event the transfer of technology to foreign firms or institutions is not approved by the Government, but the transfer is made nonetheless, the PI shall (a) refund to the Government the funds paid for the development of the technology and (b) negotiate a license with the Government to the technology under terms that are reasonable under the circumstances.

D. Lower Tier Agreements. The PI shall include this article, suitably modified to identify the parties, in all subcontracts or lower tier agreements, regardless of tier, for experimental, development, or research work.

E. This article shall remain in effect during the term of the agreement and for five (5) years thereafter.

PART 7 - TECHNICAL AND FINANCIAL REPORTING

ARTICLE 7.4 - MONTHLY STATUS REPORTS (JAN 2026) (TAILORED)

A. The PI shall provide a monthly Technical and Business Status Report for the CPO. The PI shall send the AF Program Manager and the AF Contracting Officer one electronic copy signed by the PI's Program Manager within thirty (30) days after the end of the reporting month. Each monthly status report should be segregated into two distinct sections - Technical and Business.

1. The Technical section of the monthly report shall inform the AF Program Manager about any significant events, projects, accomplishments, anticipated problems that may affect the conduct of the planned effort, and the major thrust areas for the next 30 days. The Technical section should summarize the progress of the effort being performed, new technology assessments, and mechanisms directed towards industry/academia/small businesses, anticipated changes in the commitments of personnel and equipment, and the titles of manuscripts planned for publication.

2. The Business section of the monthly status report shall provide summarized details of the resource status of the project, including the status of contributions by each member (Government and others). The report will notify the Government of any actual or potential cost overruns, funding shortfalls, rate changes, or material financial risks that may impact performance. The report will include a quarterly accounting of current expenditures as outlined and explain any major deviations with a discussion of proposed actions to address those previously mentioned deviations. The report shall include travel status identifying starting and ending dates for each trip, the starting point and destination, and the traveler(s) for each trip.

ARTICLE 7.5 - PROJECT FINAL REPORTS (JAN 2026) (TAILORED)

A. The PI shall submit a final CPO report within 90 days after the completion of the CPO. The final report shall be sent in electronic copy to the AF Program Manager and the Project Technical POC. A courtesy copy (cc:) will be sent to the AF Contracting Officer.

B. Format

1. Cover and title page - Standard Form (SF) 298, Report Documentation Page, shall be used. Item 13 of the form should contain a 100–200 word abstract summarizing technical progress during the reporting period. Style should be third person singular past tense. Jargon, special symbols or notations, subscripts, and mathematical symbols or foreign alphabet letters are not permitted. The pages should be prepared for acquisition and distribution by the Defense Technical Information Center (DTIC). All pages should be of good quality for copying purposes. When the results of the effort have not previously been reported in scientific or technical publications, the final technical report must provide sufficient detailed discussions of findings and accomplishments obtained in pursuit of the planned research objectives. The final report shall consist of two parts, one addressing the technical achievements and the second recapping the business/financial aspects of the agreement. The technical portion of the report should be suitable for publication and is to provide a recap of the program, discussing program accomplishments. With the approval of the AF Program Manager, reprints of published articles may be submitted or attached to the technical portion of the Final Report. The business portion of the report shall contain a separate discussion of total costs incurred with an explanation for any deviations from the original business plan.

2. The report shall be prepared in accordance with the official RPPR guidance which can be found here: http://www.nsf.gov/bfa/dias/policy/rppr/index.jsp

ARTICLE 7.6 - REPORTING FINANCIAL INFORMATION (JAN 2026) (TAILORED)

The PI shall submit the Federal Financial Report (SF-425) within thirty (30) calendar days following the end of each quarter. The quarterly financial report for the CPO shall be submitted to the Government Administration Office, to the AF Contracting Officer, and to pkcontracting@us.af.mil.

ARTICLE 7.8 - DISTRIBUTION OF PROJECT REPORTS (JAN 2026) (TAILORED)

A. Publications

The PI is encouraged to publish results of the project in appropriate journals and at conferences, as appropriate following approval as required by Article 7.9 DISCLOSURE OF INFORMATION. Six (6) copies of all publications resulting from the project shall also be forwarded to the AF Program Manager as they become available.

B. Acknowledgment of Sponsorship

The PI is responsible for assuring that an acknowledgment of Government support will appear in any publication of any material based on or developed under this project, in the following terms:

"Effort sponsored in whole or in part by the Air Force Research Laboratory, USAF, under Partnership Intermediary Agreement No. TBD, Collaborative Project Order No. TBD. The U.S. Government is authorized to reproduce and distribute reprints for Governmental purposes notwithstanding any copyright notation thereon."

C. Disclaimer

The PI is responsible for assuring that every publication of material based on or developed under this CPO contains the following disclaimer:

"The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the United States Government."

D. Marking and Distribution Requirements

Mark all data in accordance with the following statement:

Appropriately identify all data as being either "proprietary" or "non-proprietary/available for public release.” It is preferred that all reported data be high-level and therefore appropriate for public release; however, if the data are proprietary, ensure that the data are appropriately identified.

PART 8 - MISCELLANEOUS

ARTICLE 8.2 - CLOSEOUT, ADJUSTMENT, CONTINUING RESPONSIBILITIES AND COLLECTION - REIMBURSEMENT (JAN 2026) (TAILORED)

Closeout, adjustment and collection of amounts due shall be accomplished in accordance with 2 CFR 200 § 344, and Subpart F. Final payment cannot be made, nor can the CPO be closed out until the PI delivers to the Government all disclosures of subject inventions required by this CPO, and an acceptable final report pursuant to Article 7.5 PROJECT FINAL REPORTS (JAN 2026), and all confirmatory instruments. The Contracting Officer may make a settlement for any downward adjustments to the Federal share of costs after close-out reports are received.

PART 9 - NATIONAL POLICY MATTERS AND ASSURANCES

ARTICLE 9.2 - U.S. FLAG AIR CARRIERS (JAN 2026) (TAILORED)

Travel supported by U.S. Government funds under this CPO shall use U.S.-flag air carriers (air carriers holding certificates under 49 U.S.C. § 41102) for international air transportation of people and property to the extent that such service is available, in accordance with the International Air Transportation Fair Competitive Practices Act of 1974 (49 CFR § 91) and the interpretative guidelines issued by the Comptroller General of the United States in the March 31, 1981, amendment to Comptroller General Decision B-138942.

ARTICLE 9.7 - OPERATIONS SECURITY (OPSEC) (JAN 2026) (TAILORED)

General Operations Security (OPSEC) procedures, policies and awareness are required to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of this CPO. The Critical Information & Indicators List (CIIL) and the AFRL OPSEC Plan will be provided upon request by the AFRL DSO Security Manager Office. The PI shall apply OPSEC in the management of the program in accordance with the AFRL security instructions provided.