Call for CC DROIDS Attachments.pdf

FA2391-23-S-2403

PACER BAA

Attachment 1 26 July 2023

STATEMENT OF OBJECTIVES

Collaborative Center for the Design and Research Of InterDisciplinary Systems

(CC DROIDS)

1.0 INTRODUCTION

1.1. Purpose: The Aerospace Systems Directorate of the Air Force Research Laboratory

(AFRL/RQ) shall set up a partnership with an American university by establishing a Collaborative Center for the Design and Research Of InterDisciplinary Systems (CC DROIDS). The purpose of the CC DROIDS is to complement AFRL in pursuit of its goal to lead the research and development of novel design methods and tools for the optimization and assessment of revolutionary aerospace vehicles. CC DROIDS is an organizational concept to bolster common research interests through collaboration among the participants. Developing a Collaborative Center is expected to be mutually beneficial, increasing the agility and responsiveness of AFRL research efforts while providing experience and mentorship to students.

1.2. Competency Areas: The Multidisciplinary Sciences and Technology Center (MSTC) within AFRL leads the integration of multiple disciplines to discover and exploit new phenomena for system level optimization and the assessment of revolutionary aerospace vehicles from concept development through preliminary design. Our goal is to model systems--and systems of systems--to a level of fidelity necessary to capture the physics which drive system design and to perform design space exploration.

Current competency areas within MSTC are:

1.2.1. Design Space Exploration: Multifidelity model-based systems engineering

(MBSE); single-vehicle mission to campaign-level effectiveness analysis; system of systems analysis; cost effectiveness analysis; logistics and sustainment footprints; deterministic gradient and non-gradient based optimization methods;

propulsion and subsystem integration; fuel and system thermal management; risk-quantified large-scale (104 design variables, 106 constraints) design space exploration; high-fidelity system level design optimization.

1.2.2. Multifidelity Modeling and Analysis for Design Optimization: Sensitivity analysis; computational fluid dynamics; linear and nonlinear structural mechanics and structural dynamics; linear and nonlinear computational aerothermoelasticity;

aeroservoelastic analysis; uncertainty quantification and design under uncertainty;

goal-oriented adaptive, high-order finite-element analysis; aerodynamic conceptual design; novel configuration assessment; rapid assessment method development; structural conceptual design; high-fidelity structural topology optimization, secondary structure weight estimation; design for life; design for manufacture.

1.2.3. Multidisciplinary Technology Development, Assessment, and Validation:

Aerothermoelastic wind tunnel testing; ground vibration testing; remotely piloted vehicle (RPV) scaled flight testing; multidisciplinary technologies assessment;

data assimilation in multidisciplinary design analysis and optimization (MDAO).

2.0 OBJECTIVES

2.1 The objectives for CC DROIDS are to develop research activities which align with the Technology Areas of MSTC, to foster close research collaboration between AFRL and university partners, to mentor highly qualified students, and to exploit existing engineering software or develop new software where needed.

2.1.1 Technology Areas: AFRL’s MSTC has a mandate to support a wide range of computational and experimental requirements for future Air Force capabilities.

The focus for this Collaborative Center will be on developing multidisciplinary technologies and computational methods required to perform reliable, multi-fidelity, multidisciplinary analysis and design exploration of aerospace vehicles across size, speed, and altitude space from small UAVs to transport platforms, including subsonic to hypersonic configurations. The Collaborative Center will need to perform research in the following areas--which mirror the research thrusts of MSTC outlined above--applied to one or more Air Force relevant capabilities.

It is expected that the proposed work is contextualized against the current state of the art, including previous AFRL MSTC research efforts.

a. TA1: Design Space Exploration

Risk-quantified design space exploration: Develop and exploit robust design methods, reliability-based design, design under uncertainty, multi-level optimization, multi-objective optimization, gradient and non-gradient based optimization methods for quantative risk assessment in multidisciplinary design of large-scale problems (104 design variables, 106 constraints)

Effectiveness-based design: Integrate operations analyses with multi-fidelity vehicle design (vehicle class/type, aerodynamic shape, topological and structural layout, propulsion and subsystem integration and sizing, etc.) to evaluate the impact of vehicle parameters on system operational behavior. A modeling framework is needed to allow consistent assessment of designs with multiple power and propulsion systems.

Brayton-based, Rankine-based, electric, and hybrid systems may be evaluated for power supply, as well a range of ducted and unducted propulsors. Support non-gradient-based, gradient-based, and mixed optimization. Consider parameterization of the mission profile for mission optimization.

Digital engineering: Integrate MBSE practices and tools into aerospace system design processes to improve collaboration and ensure a consistent representation of the system across all models and teams. Centralize requirements and design artifacts for long-term preservation and traceability.

b. TA2: Multifidelity Modeling and Analysis for Design Optimization

Efficient multidisciplinary analysis with design sensitivities: low-to-high-fidelity coupled physics analysis with computed analytic, semi-analytic, and numerical design sensitivities. Aerodynamic, structural dynamic, thermal, acoustic, controls, and other potential physical disciplines that couple to produce emergent physical phenomena not present in single discipline analyses (e.g., aeroelasticity). Steady, time-periodic, transient, and chaotic responses, including critical points representative of changes in stability. Methods of transferring data across physical interfaces in a conservative and consistent manner (e.g., load/displacement). Adaptively learned multi-fidelity surrogate models and methods for accelerating analysis while maintaining fidelity (e.g., physics and statistics-based Reduced Order Models (ROMs), leverage of time periodicity, and critical point identification).

Goal-oriented adaptive analyses: Develop, test, and exploit goal-oriented algorithms for adapting analysis to engineering problems in a quantitative, machine-oriented, objective driven manner that accounts for varied uncertainty sources and updates during design space exploration. Blend local adaptations based on discretization, numerical order, and fidelity, and possibly other algorithmic properties to meet desired objectives, including numerical accuracy and computational cost. Technical challenges include handling large parameter variations, high-order generation and deformation of high-quality meshes, including high-order space-time meshes, adaptivity in the presence of coupled physics, generating fast and accurate sensitivities. Leverage ideas in multi-fidelity surrogate construction, Bayesian inference and updating, and heterogeneous computing resources. Test on meaningful benchmarks to quantify benefits of adaptive approaches.

Design Under Uncertainty: Address modeling, parametric, and numerical sources of uncertainty. Develop forward and inverse uncertainty propagation methods to trade efficiency and accuracy when quantifying aleatoric and epistemic uncertainties encountered in multidisciplinary design such that follow-on design phases start with conservative estimates of performance. New methods should be scalable (>20 variables) and compatible with multiple fidelity representations of single physics and multi-physics models, and their associated uncertainties. Methods including but not limited to Bayesian updating, integrating multiple information sources, adaptive dimension reduction, global sensitivity analysis, and novel stochastic collocation techniques.

c. TA3: Multidisciplinary Technology Development, Assessment, and

Validation

Aeroelastic modal topology optimization: Coupling structural and aerodynamic analysis for structural topology optimization of air vehicles where the optimality criteria are mode and mode shape based. This may include experimental validation of the transient response of a representative structure.

Experimental data in MDAO: Incorporating experimental data with uncertainty into the design process to account for un-modeled physics, aleatory uncertainty, correction factors, truth data, or hardware in the loop design. This may include in-situ experiments within the design process or post processed data.

Quantified technology assessment: Incorporation of computational and experimental techniques into a system engineering design and technology assessment process and computing framework.

Employing/utilizing/including probabilistic approaches, quantitatively assess the impact of suites of technologies on a vehicle design’s measures of performance and effectiveness. Benefits and penalties should be captured in a coupled manner to account for total system impacts, and probabilistically to account for uncertainty in estimates and coupling.

Multidisciplinary technologies: Develop and demonstrate technologies that create improved capabilities by leveraging the synergy between multiple disciplines. Explore the performance space to understand coupled system behavior, and how that behavior can be best exploited.

Explore how system performance is improved through application of the technology to representative systems or sub-systems. Two examples are active aeroelastic wing technology and multifunctional structures.

2.2 Quality of Personnel:

2.2.1 Successful pursuit of these technology challenges requires a high caliber of research personnel. Collaborative Center team members must be highly accomplished in their research activities and well regarded in their technical areas.

Any short-term, entry-level, or student researchers supporting the research must be well-skilled and/or highly trainable, directly supervised, and prepared to contribute effectively with minimal oversight.

2.3 Collaboration:

2.3.1 A major goal within AFRL is to establish a cooperative relationship with external researchers in order to increase the agility and responsiveness of research efforts.

It is desired to pursue a collaborative effort in multidisciplinary sciences and design. The objective of the collaboration is to provide research in aerospace vehicle design through a broad and agile base of expertise. The collaborative research is expected to further new multidisciplinary research areas of unique interest to the Air Force. By conducting this collaborative research, AFRL and the Collaborative Center can accelerate innovative research in a variety of areas.

It is envisioned that there will be regularly scheduled interaction between the Collaborative Center researchers and AFRL researchers including, but not limited to: annual reviews, in-person technical interchange meetings at both the collaboration facilities and AFRL, as well as regular video conference meetings.

Such connectivity allows the research to be more focused and establishes a synergistic working relationship with AFRL personnel which can significantly raise productivity. This close relationship with AFRL also maximizes transition opportunities for the collaboratively developed technologies. More specific expected elements of the Collaborative Center include:

a. The collaborative research program will begin with a kickoff period in which researchers will have detailed meetings with MSTC personnel so that technical issues and proposed solutions can be fully understood by all team members. This period may include visit(s) to WPAFB and tours of Air Force facilities to initiate discussions regarding facility usage by projects within the Collaborative Center.

b. Annual reviews will be held alternately at the Collaborative Center research site and at Wright-Patterson AFB.

c. Numerous less formal meetings throughout the period of performance will also be held. A plan for future, long-term growth of the collaborative multi-disciplinary science research capability is required. Researchers in the Collaborative Center will need to interface not only with Air Force researchers but also with the Air Force’s key collaborators, such as, but not limited to, a large network of academics funded by AFOSR, AFRL (Aerospace Systems Directorate and other technical directorates/divisions/branches), DARPA, NASA and other government and industry organizations. The best fit for the Collaborative Center will be research teams that have the ability and willingness to form dynamic partnerships, and which have demonstrated success working in a cross-organizational fashion.

d. To facilitate collaboration and integration into AFRL methods and processes, it is desired that the Collaborative Center will allocate funding for supporting students to work on site at WPAFB, typically during summer months, to offset the cost of local housing, relocation, etc.

e. The Collaborative Center is expected to publish or otherwise make publicly available results of work performed under this agreement to the extent the results are deemed publicly releasable by AFRL. It is highly desirable that the Collaborative Center pursue peer-reviewed publication of its research.

f. ITAR work is not anticipated in this Collaborative Center, but if such work is necessary or deemed advantageous, the university must be able to support ITAR research, in which case a detailed security plan adhering to ITAR restrictions will be required.

g. Students funded through the Collaborative Center will be encouraged to apply for scholarships not impinging on the technical objectives of the Collaborative Center.

h. To maximize collaborative opportunities and transition potential, it is encouraged but not required students be US citizens.

2.4 Software:

2.4.1 Because of the computational focus of the Collaborative Center, software will be a critical medium of research and an important product of the collaboration.

Research and development may utilize software from AFRL and from other readily available sources, as required. Emphasis will be placed on software engineering practices that will maximize efficiency in development and flexibility in reuse and interoperation. Software development and scientific computing skills such as version control (git), testing, documentation, containerization, etc., are desired, since it is expected that effective software will lead to significant advances in capability that will be shared between the Collaborative Center, AFRL, and other partners. Software development plans shall include integration into AFRL computational codes and frameworks. For MBSE tasks, the use of the Dassault’s Catia Magic System of Systems Architect should be considered before new development is undertaken. For military utility analysis, the preferred tool is AFSIM. If tasks require the development of vehicle geometry and surface/volume discretization the use of the Computational Aircraft Prototype Syntheses (CAPS) should be considered before new development is undertaken.

If tasks require thermal and structural analysis with sensitivities the use of the Multidisciplinary design Adaptation and Sensitivity Toolkit (MAST) should be first considered. Finally, if tasks require the development or use of RANS or Euler computational fluid dynamics the use of either FUN3D or ChiDG should be considered before new development, or the use of an alternate code is undertaken.

3.0 DELIVERABLES

3.1 Interim Performance Reports

3.2 Financial Reports--Reimbursement

3.3 Publishing Project Results

3.4 Final Performance Report

3.5 Reporting of Subawards and Executive Compensation

3.6 Disclosure of Information

3.7 Reporting of Matters Related to Recipient Integrity and Performance

3.8 Software

4.0 OPERATIONS SECURITY (OPSEC)

4.1 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 person involved on this agreement to 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 this SOO. The Recipient shall ensure employees receive training and follow appropriate OPSEC measures during the performance of the agreement.

Attachment 2

Statement of Work (SOW) Supplemental Requirements for Assistance Instruments (AFRL/PZL)

Oct 2022

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

1. Science and Technology (S&T) Protection: The requirements below are in accordance with Air Force

Research Laboratory Instruction (AFRLI) 61‐113, “Science and Technology (S&T) Protection for the Air Force Research Laboratory”.

a. Initial/Annual/New SF 424, Research and Related Senior/Key Person Profile (Expanded)

Form, Requirement: The Recipient shall provide an SF 424 with the following information:

i. Initial SF 424: An initial report of all Senior/Key Personnel at the time of award. This form is required with proposal submission.

ii. Annual SF 424: An annual report of all Senior/Key Personnel providing support. The first submission is due 30 days after 12 months after receipt of award. Subsequent submissions are due every 12 months after first annual submission, and throughout the technical effort.

iii. New/Revised SF424: A report for any new Senior/Key Personnel who join the contract, agreement, grant, or OT. Any updated SF 424s for new Senior/Key Personnel supporting the award require coordination from the Government prior to the Recipient employee receiving access to S&T information. These reports are required to provide updates and supplements to the SF 424 as appropriate during the period of performance. Identify changes from previous versions. Permanent change pages shall conform to the requirements, quality, style, and format of the basic documentation.

Submission: Annual and Revised SF 424s shall be submitted electronically in Microsoft Office Suite compatible format, PDG, or RTF as coordinated with the Air Force Program Manager. For email delivery, include the award number in the subject line. The recipient shall submit one copy of the SF 424 to:

(1) AFRL Program Manager

(2) AFRL/RQOS Security

Note: Submit electronically. Electronic submittals shall be either encrypted or password protected.

Mark all data delivered with the following Distribution Statement: Distribution authorized to A: Approved for public release, distribution is unlimited.

Attachment 3

FA8650-24-2-XXXX Page 1

COOPERATIVE AGREEMENT ARTICLES

Collaborative Center for the Design and Research Of InterDisciplinary Systems

(CC DROIDS)

TABLE OF CONTENTS

PART 1 ADMINISTRATIVE INFORMATION

1.00 ADMINISTRATIVE REQUIREMENTS AND ORDER OF PRECEDENCE

1.01 ADMINISTRATIVE RESPONSIBILITIES

1.02 DELEGATION OF ADMINISTRATION

PART 2 TERM

2.00 TERMINATION

2.01 TRAFFICKING IN PERSONS

2.02 ENFORCEMENT

2.03 MODIFICATIONS

PART 3 MANAGEMENT OF THE PROGRAM

3.00 TITLE TO PROPERTY

3.01 PROPERTY SYSTEM

3.02 SCOPE AND MANAGEMENT OF THE PROGRAM

3.03 BASE SUPPORT

3.04 RECIPIENT ACCESS TO AIR FORCE INSTALLATION

3.05 COMMON ACCESS CARDS (CAC) FOR RECIPIENT PERSONNEL

3.06 ACCESS TO USAF BASES, AFRL FACILITIES AND/OR U.S. GOVERNMENT INFORMATION

TECHNOLOGY NETWORKS

PART 4 FINANCIAL MATTERS

4.00 INCREMENTAL FUNDING

4.01 PAYMENT-REIMBURSEMENT-WAWF (ONR)

4.05 PROGRAM INCOME-RESEARCH

4.06 COST PRINCIPLES

4.07 STANDARDS FOR FINANCIAL MANAGEMENT

4.08 AUDIT REQUIREMENTS

4.09 RETENTION AND ACCESS TO RECORDS

4.10 REVISION OF BUDGETS AND PROGRAM PLANS

PART 5 CLAIMS, DISPUTES AND APPEALS

5.00 CLAIMS, DISPUTES, AND APPEALS

PART 6 INTELLECTUAL PROPERTY RIGHTS

6.00 INVENTIONS

6.01 DATA RIGHTS

PART 7 TECHNICAL AND FINANCIAL REPORTING

7.00 INTERIM PERFORMANCE REPORTS

7.01 FINANCIAL REPORTS- REIMBURSEMENT

7.02 PUBLISHING PROJECT RESULTS

7.03 FINAL PERFORMANCE REPORT

7.04 REPORTING SUBAWARDS AND EXECUTIVE COMPENSATION

FA8650-24-2-XXXX Page 2

7.05 DISCLOSURE OF INFORMATION

7.06 REPORTING OF MATTERS RELATED TO RECIPIENT INTEGRITY AND PERFORMANCE

7.07 SOFTWARE

PART 8 MISCELLANEOUS PERFORMANCE ISSUES

8.00 PROCUREMENT SYSTEM

8.01 CLOSEOUT, ADJUSTMENT, CONTINUING RESPONSIBILITIES AND COLLECTION

REIMBURSEMENT

8.02 USING TECHNICAL INFORMATION RESOURCES

8.03 SYSTEM FOR AWARD MANAGEMENT AND UNIQUE ENTITY IDENTIFIER REQUIREMENTS

PART 9 NATIONAL POLICY REQUIREMENTS

9.00 NONDISCRIMINATION NATIONAL POLICY REQUIREMENTS (SEPTEMBER 2017)

9.01 ENVIRONMENTAL NATIONAL POLICY REQUIREMENTS (JANUARY 2021)

9.04 OTHER NATIONAL POLICY REQUIREMENTS (SEPTEMBER 2021)

9.05 ADDITIONAL REQUIREMENTS – NATIONAL POLICY REQUIREMENTS.

1.00 ADMINISTRATIVE REQUIREMENTS AND ORDER OF PRECEDENCE (MAR 2015)

(a) This award is governed by the guidance in the Code of Federal Regulations (CFR), Title 2, Subtitle A, Chapter II, Part 200, "Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards," as modified and supplemented by the Department of Defense's (DoD) interim implementation found at 2 CFR part 1104, "Implementation of Government wide Guidance for Grants and Cooperative Agreements.” (79 FR 76047, December 19, 2014, as amended at 85 FR 49506, August 13, 2020).

(b) 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 part 200* as modified and supplemented by DoD's interim implementation found in 2 CFR Part 1104

(4) Award-specific terms and conditions

(5) Attachments to this award if any

(c) In case of disagreement with any requirements of this award, the recipient shall contact the grants officer in order to resolve the issue. The recipient shall not assess any costs to the award or accept any payments until the issue is resolved.

1.01 ADMINISTRATIVE RESPONSIBILITIES (MAR 2015)

(a) Government Representatives are:

(1) Grants Officer: TBD

(2) Grants Negotiator: TBD

(3) Government Program Manager: TBD

FA8650-24-2-XXXX Page 3

(4) Finance: TBD

(5) Grants Administration Office: TBD

(6) Paying Office: TBD

1.02 DELEGATION OF ADMINISTRATION (MAR 2015)

(a) The administrative duties listed below have been delegated to the grants administration office:

(1) During performance:

(i) Approve provisionally all Requests for Advance or Reimbursement (SF 270).

(ii) Perform property administration.

(iii) Perform plant clearance.

(iv) Approve requests for Registration of Scientific and Technical Information Services (DD Form1540).

(v) Perform cash management by reviewing quarterly Federal Financial Report (SF 425) and, after conferring with the AFRL grants officer, make appropriate adjustments to predetermined scheduled payments by modifying the agreement.

(vi) Obtain Interim Inventions Reports (DD Form 882)

(vii) Obtain Interim Technical Reports

(b) Upon expiration of agreements:

(1) Obtain final payment request, if any.

(2) Obtain the final Federal Financial Report (SF 425).

(3) Obtain final property report and dispose of Government Property on those assistance awards containing residual Government Property.

(4) Perform a review of final incurred costs and assist the awarding grants officer in resolving exceptions, if any, resulting from questioned costs.

(5) Perform cost sharing adjustments, if applicable.

(6) Assure that all refunds due the Government are received.

(7) Notify the grants officer when the final SF270 and/or SF425 indicates an unexpended balance.

(8) Obtain Final Inventions Report (DD Form 882). Negative reports required.

(i) Obtain Patent Clearance from (Insert POC or email address).

FA8650-24-2-XXXX Page 4

2.00 TERMINATION (MAR 2015)

(i) The grants officer may terminate this agreement by written notice to the recipient upon a finding that the recipient has failed to comply with the material provisions of this agreement.

(ii) 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 recipient initiates the termination, written notification shall be provided to the grants officer at least 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 grants officer determines, in the case of a partial termination, that the reduced or modified portion of the award will not accomplish the purpose for which the award was made, the grants officer may terminate the award in its entirety.

(iii) The Government and the recipient will negotiate in good faith an equitable reimbursement for work performed toward accomplishment of program goals. The Government will allow full credit to the recipient for the Government share of the obligations properly incurred by the recipient prior to termination, and those non-cancelable obligations that remain after the termination. The cost principles and procedures described in the article entitled "Cost Principles" shall govern all costs claimed, agreed to, or determined under this article.

(iv) If this agreement is incrementally funded, it may be terminated in the absence of additional government funding as set forth in the article entitled Incremental Funding.

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

(vi) If this agreement is terminated, the Government has the rights identified in and the recipient shall comply with the article entitled Closeout, Adjustments, Continuing Responsibilities and Collection.

(vii) Notwithstanding the above, for security or safety reasons or in the case of a serious breach that could lead to irreparable damage, the grants officer may order immediate suspension of work, in whole or in part.

2.01 TRAFFICKING IN PERSONS (MAR 2015)

(a) This award is subject to the requirements of section 106 (g) of the Trafficking Victims Protection Act of 2000 (22 U.S.C. 7104, as implemented by 2 CFR 175). If the recipient or any subawardee (i) engages in severe forms of trafficking in persons or has procured a commercial sex act during that the period of time of the grant or cooperative agreement is in effect or (ii) uses forced labor in the performance of the grant or cooperative agreement, the Government shall be authorized to terminate the grant or cooperative agreement without penalty.

2.02 ENFORCEMENT (MAR 2015)

(a) In addition to the remedies identified in the article entitled Termination, the Government may use any of the remedies identified in 2 CFR 200 § 339 when determined appropriate.

2.03 MODIFICATIONS (MAR 2015)

FA8650-24-2-XXXX Page 5

(a) Modifications to this agreement may be proposed by either party. Recipient recommendations for any modifications to this agreement shall be submitted in writing to the Government program manager before the desired effective date with a copy to the grants officer. The recipient shall detail the technical, chronological, and financial impact of the proposed modification to the program. Changes are effective only after the agreement has been modified. Only the grants officer has the authority to act on behalf of the Government to modify this agreement. If the Government agrees to the proposed modification without change, the grants officer may issue a modification unilaterally approving the request.

(b) The grants officer or administrative grants officer may unilaterally issue minor or administrative agreement modifications (e.g., changes in the paying office or appropriation data, changes to Government personnel identified in the agreement, etc.).

3.00 TITLE TO PROPERTY (MAR 2015)

(a) Unless otherwise stated in the Award, title to personal property acquired with agreement funds shall vest in the recipient upon acquisition, except that supplies shall be managed in accordance with 2 CFR 200 § 314. Title to real property shall vest in the recipient subject to conditions contained in 2 CFR 200 §311. The recipient shall dispose of real property in accordance with grants officer instructions issued pursuant to 2 CFR 200 § 311.

3.01 PROPERTY SYSTEM (MAR 2015)

(a) The recipient's property system shall meet the standards as set forth in 2 CFR 200 § 310 - 316.

3.02 SCOPE AND MANAGEMENT OF THE PROGRAM (MAR 2015)

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

(b) The recipient shall perform a coordinated research and development program carried out in accordance with the Statement of Work entitled, "Collaborative Center for Design and Research of InterDisciplinary Systems (CC DROIDS) ", dated “DATE”. The recipient shall submit all documentation required by Part 7, Technical and Financial Reporting.

(c) The recipient shall accomplish the overall management, including technical, programmatic, reporting, financial and administrative matters, of the coordinated research program. The Government program manager(s) may interact with the recipient to promote effective collaboration between the recipient and the Government.

3.03 BASE SUPPORT (MAR 2015)

(a) Base support shall be provided by the Government to the recipient in accordance with this article.

(1) Base support includes Government-controlled working space, material, equipment, services (including automatic data processing), or other support (excluding use of the Defense Switched Network (DSN)) which the Government determines can be made available at, or through, any Air Force installation where this agreement shall be performed.

FA8650-24-2-XXXX Page 6

(2) Following are installations where base support will be provided: AFRL/RQVC, Facility 20146, Building 146, Wright-Patterson AFB, OH 45433.

3.04 RECIPIENT ACCESS TO AIR FORCE INSTALLATIONS (OCT 2019)

(a) The recipient shall obtain base identification and vehicle passes, if required, for all personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the assistance instrument. Recipient personnel are required to wear or prominently display installation identification badges or recipient-furnished, recipient identification badges while visiting or performing work on the installation.

(b) The recipient shall submit a written request on company letterhead to the grants officer listing the following: assistance instrument number, location of work site, start and stop dates, and names of employees and subcontractor employees needing access to the base. The letter will also specify the individual(s) authorized to sign for a request for base identification credentials or vehicle passes. The grants officer will endorse the request and forward it to the issuing base pass and registration office or Security Forces for processing. When reporting to the registration office, the authorized individual(s) should provide a valid driver’s license, current vehicle registration, valid vehicle insurance certificate, to obtain a vehicle pass.

(c) During performance the recipient shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials and vehicle passes for any employee who no longer requires access to the work site.

(d) When work under this assistance instrument requires unescorted entry to controlled or restricted areas, the recipient shall comply with AFI 31-101, Integrated Defense, and DODMAN5200.02_AFMAN 16-1405, Air Force Personnel Security Program.

(e) Upon completion or termination of the assistance instrument or expiration of the identification passes, the prime recipient shall ensure that all base identification passes issued to employees and subcontractor employees are returned to the issuing office.

(f) Failure to comply with these requirements may result in withholding of final payment.

3.05 COMMON ACCESS CARDS (CAC) FOR RECIPIENT PERSONNEL (OCT 2019)

(a) For installation(s)/location(s) cited in the assistance instrument, recipients shall ensure Common

Access Cards (CACs) are obtained by all recipient or subcontract personnel who meet one or both of the following criteria:

(1) Require logical access to Department of Defense computer networks and systems in either:

(i) the unclassified environment; or

(ii) the classified environment where authorized by governing security directives.

(2) Perform work, which requires the use of a CAC for installation entry control or physical access to facilities and buildings.

(b) Recipients and their personnel shall use the following procedures to obtain CACs:

FA8650-24-2-XXXX Page 7

(1) Recipients shall provide a listing of personnel who require a CAC to the grants officer. The government will provide the recipient instruction on how to complete the Contractor Verification System (CVS) application and then notify the recipient when approved.

(2) Recipient personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local Military Personnel Flight (MPF)).

(c) While visiting or performing work on installation(s)/location(s), recipient personnel shall wear or prominently display the CAC as required by the governing local policy.

(d) During the performance period of the assistance instrument, the recipient shall:

(1) Within 7 working days of any changes to the listing of the assistance instrument personnel authorized a CAC, provide an updated listing to the grants officer who will provide the updated listing to the authorizing government official;

(2) Return CACs in accordance with local policy/directives within 7 working days of a change in status for personnel who no longer require logical or physical access;

(3) Return CACs in accordance with local policy/directives within 7 working days following a CACs expiration date; and

(4) Report lost or stolen CACs in accordance with local policy/directives.

(e) Within 7 working days following completion/termination of the assistance instrument, the recipient shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

(f) Failure to comply with these requirements may result in withholding of final payment.

3.06 ACCESS TO USAF BASES, AFRL FACILITIES AND/OR U.S. GOVERNMENT INFORMATION

TECHNOLOGY NETWORKS (NOV 2016)

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

Government Information Technology networks in connection with the work on this agreement must be U.S. citizens. 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. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Grants Officer prior to providing access. The above requirements are in addition to any other agreement requirements related to obtaining a Common Access Card (CAC).

4.00 INCREMENTAL FUNDING (MAR 2015)

(a) In no event is the Government obligated to reimburse the recipient for expenditures in excess of the total funds allotted by the Government to this agreement. The Government anticipates that from time to time additional amounts will be allotted to this agreement by unilateral modification, until the total Government share is fully funded.

(b) If additional funds are not made available, this agreement may be terminated pursuant to the article entitled Termination. The recipient is not obligated to continue performance or otherwise incur costs in excess of the amount then allotted to the agreement by the Government or, if this is a cost sharing

FA8650-24-2-XXXX Page 8 agreement, the amount then allotted by the Government to the agreement plus the recipient's corresponding share, until the grants officer notifies the recipient 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 this agreement. When and to the extent that the amount allotted by the Government to the agreement is increased, any costs the recipient incurs before the increase that are in excess of the amount previously allotted by the Government or if this is a cost-sharing agreement, the amount previously allotted by the Government to the agreement plus the recipient's corresponding share, shall be allowable to the same extent as if incurred afterward, unless the grants officer issues a termination or other notice and directs that the increase is solely to cover termination or other specified expenses.

4.01 PAYMENT-REIMBURSEMENT-WAWF (ONR) (MAR 2015)

(a) The recipient shall request payment by reimbursement by electronically submitting Standard Forms

(SF) 270, Requests for Advance or Reimbursement, through Wide Area Work Flow (WAWF), https://wawf.eb.mil.

(b) The following codes will be required to route requests and emails correctly through WAWF

AWARD NUMBER: TBD

TYPE OF DOCUMENT: TBD

CAGE CODE: TBD

ISSUED BY DODAAC: TBD

ADMIN DODAAC: TBD

GOVERNMENT PROGRAM MANAGER: TBD

SERVICE ACCEPTOR OFFICE DODAAC: TBD

PAY OFFICE DODAAC: TBD

APPROVAL OFFICE DODAAC: TBD

SEND E-MAIL NOTIFICATIONS for completed SF 270: TBD

(c) WAWF has been designated as the Department of Defense (DoD) standard for electronic invoicing and payment. To facilitate this effort for universities and non-profit organizations with awards administered by the Office of Naval Research (ONR) Regional Offices, DoD has established the ONR Electronic Payment System (PayWeb), https://onronline.onr.navy.mil/payweb/, as an initial entry point to WAWF. If the recipient participates in the PayWeb system, electronic requests for payment shall be submitted to the Administrative Grants Officer (AGO) at the Administrative Office in Block TBD of the award, using the standard PayWeb processes.

(d) Participation in the PayWeb system requires the recipient to obtain an External Certificate Authority

(ECA) certificate from an approved certificate authority for access. Operational Research Consultants (ORC), http://www.eca.orc.com, and VeriSign, http://www.verisign.com/gov/ieca, are approved ECA authorities. Questions or requests for technical assistance in implementing certificates should be addressed to the Navy PKI Help Desk at 1-800-304-4636. The recipient shall contact the AGO at the Administrative Office in Block TBD of the award for instructions to register and use WAWF/ PayWeb.

(e) Electronic submission of payment requests requires the recipient to register in WAWF and have the appropriate CAGE code activated. The recipient's System for Award Management (SAM) Electronic Business Point of Contact (EBPOC) is responsible for activating the CAGE code in WAWF by calling 1-866-618-5988. Once the recipient's CAGE Code is activated, the CCR EBPOC will self-register in WAWF and follow the instructions for a group administrator. ONR Regional Offices will assist in this process. The ONR Regional Office is listed as the Administrative Office in Block TBD of the award.

FA8650-24-2-XXXX Page 9

(f) If the recipient does not participate in the ONR PayWeb system, payment requests may be submitted electronically via WAWF. The recipient shall contact the AGO at the Administrative Office in Block TBD of the award for instructions regarding registration in and use of WAWF.

(g) Recipients may also request reimbursement by submitting original SFs 270, Requests for Advance or

Reimbursement, to the Administrative Grants Officer (AGO) with a copy to the AFRL Grants/Agreements Officer and AFRL Program Manager.

(h) Final payment will be made only after delivery and acceptance of the final report prepared in accordance with the article entitled TBD.

4.05 PROGRAM INCOME-RESEARCH (MAR 2015)

(a) Any program income earned shall be used in accordance with 2 CFR 200 § 307 as follows:

(1) All program income earned during the project period shall be added to funds committed to the project by the Government and recipient organization and be used to further eligible program objectives.

(2) The recipient may deduct costs associated with generating program income from gross income to determine program income, provided these costs are not charged to the agreement.

(3) The recipient has no obligation to the Government for program income earned after the end of the project period.

(4) The recipient will have no obligation to the Government for program income earned from license fees and royalties for copyrighted material, patents, patent applications, trademarks and inventions produced under the agreement.

4.06 COST PRINCIPLES (MAR 2015)

(a) The cost principles applicable to this agreement are contained in 2 CFR 200, Subpart E, Cost

Principles. 2 CFR 200 describes the cost principles for determining allowability of costs applicable to lower tier, cost type contracts or awards under this agreement shall be determined by type of entity receiving the lower tier contract or award.

4.07 STANDARDS FOR FINANCIAL MANAGEMENT (MAR 2015)

(a) The recipient's financial management system shall comply with the standards identified in 2 CFR 200

§ 302.

4.08 AUDIT REQUIREMENTS (MAR 2015)

(a) The recipient shall comply with the audit requirements of 2 CFR 200, Subpart F Audit Requirements.

Subrecipient(s) shall comply with the audit requirements appropriate for the type of entity receiving the award as required.

4.09 RETENTION AND ACCESS TO RECORDS (MAR 2015)

(a) Recipient's financial records, supporting documents, statistical records, and all other records pertinent to an award shall be retained and access to them permitted in accordance with 2 CFR 200 § 334-338.

FA8650-24-2-XXXX Page 10

4.10 REVISION OF BUDGETS AND PROGRAM PLANS (MAR 2015)

(a) The budget plan is the financial expression of the program as approved during the award process.

The budget includes the sum of the Government cost share and the recipient cost share, if any.

Recipients shall report deviations from budget and program plans and shall request prior approvals for budget and program plan revisions for all situations listed in 2 CFR 200 § 308.

5.00 CLAIMS, DISPUTES, AND APPEALS (MAR 2015)

(a) General. Parties shall communicate with one another in good faith and in a timely and cooperative manner when raising issues under this article. Department of Defense (DoD) policy is to resolve issues through discussions and mutual agreement at the grants officer's level prior to submission of a claim. Where unassisted negotiations fail to resolve issues in controversy, the parties agree to consider the use of Alternative Dispute Resolution (ADR) procedures to the maximum extent practicable.

(b) Alternative Dispute Resolution. ADR should be used whenever practicable as a relatively inexpensive and expeditious procedure to resolve issues in controversy. ADR is any mutually agreed to voluntary means of settling issues in controversy without resorting to formal administrative appeals or litigation.

ADR techniques shall be mutually agreed to and may be used at any appropriate time during the process.

(c) Claims Resolution Process. When a claim cannot be resolved by the parties, the parties agree to use the procedures identified in DoDGARs 22.815 as the administrative process to resolve claims, disputes and appeals. For purposes of this article the Grant Appeal Authority will be the applicable AFRL Technology Director.

(d) Non-exclusivity of Remedies. Nothing in this article is intended to limit a recipient's right to any remedy under the law.

6.00 INVENTIONS (MAR 2015)

(a) The clause entitled Patent Rights (Small Business Firms and Nonprofit Organizations, (37 CFR

401.14(a)) is hereby incorporated by reference and is modified as follows: replace the word "contractor" with "recipient"; replace the words "agency," "Federal Agency" and "funding Federal Agency" with "Government"; replace the word "contract" with "agreement"; delete paragraphs (g)(2), (g)(3) and the words "to be performed by a small business firm or domestic nonprofit organization" from paragraph (g)(1). Paragraph (l), Communications, point of contact on matters relating to this clause will be the servicing Staff Judge Advocate's office.

(b) Interim or final Invention Reports 1) listing 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 Grants Officer at the address located in the agreement and to the Grants Officer/Patent Administrator at det1.afrl.pk.patents@us.af.mil, with a courtesy copy (cc:) to the government Program Manager/Project Engineer. Please include in the subject line of the e-mail the contract number followed by the words "Invention Reporting." Also include in the body of the e-mail the names of the Government Project Engineer/Program Manager and his/her office symbol. The recipient shall file Invention (Patent) Reports on the DD Form 882, Report of Inventions and Subcontracts, as of the close of each performance year and at the end of the term for this agreement.

Annual reports are due 90 days after the end of each year of performance and final reports are due

FA8650-24-2-XXXX Page 11

90 days after the expiration of the final performance period. Negative reports are also required annually.

(c) The DD Form 882 may also be used for the notification of any subaward(s) for experimental, developmental or research work which contain a "Patent Rights" clause, with a cc: to the government Program Manager/Project Engineer.

(d) All other notifications (e.g., disclosure of each subject invention to the grants officer within 2 months after the inventor discloses it) shall also be sent to the e-mail address above, with a cc: to the government Program Manager/Project Engineer.

(e) This provision also constitutes the request for the following information for any subject invention for which the recipient has retained ownership: 1) the filing date, 2) serial number and title, 3) a copy of the patent application and 4) patent number and issue date. Submittal shall be to the grants officer / patent administrator e-mail address listed above, with a cc: to the government Program Manager/Project Engineer.

6.01 DATA RIGHTS (MAR 2015)

(a) All rights and title to data, as defined in 48 CFR 27.401, generated under this agreement shall vest in the recipient.

(b) Assertion of copyright.

(1) The recipient may assert copyright in any work that is eligible for copyright protection if the recipient acquires ownership of it under this award, either by developing it or otherwise.

(2) With respect to any work in which you assert copyright, DoD reserves a royalty-free, nonexclusive and irrevocable license to:

(i) Reproduce, publish, or otherwise use the work for Federal Government purposes; and

(ii) Authorize others to reproduce, publish, or otherwise use the work for Federal Government purposes.

(c) Data produced under the award.

(1) The Federal Government has the right to:

(i) Obtain, reproduce, publish, or otherwise use the data produced under this award; and

(ii) Authorize others to receive, reproduce, publish, or otherwise use the data produced under this award for Federal Government purposes.

(d) The recipient is responsible for affixing appropriate markings indicating rights on all data delivered under the agreement. The Government will have unlimited rights in all data delivered without markings.

(e) The recipient shall include this article, suitably modified to identify the parties, in all lower tier contracts and awards, regardless of tier, for experimental, developmental, or research work.

(f) When the intangible property is no longer needed for the originally authorized purpose, the recipient must contact the awarding office to arrange for disposition in accordance with the procedures specified in 2 CFR 200-313(e).

FA8650-24-2-XXXX Page 12

7.00 INTERIM PERFORMANCE REPORTS (MAR 2015)

(a) Recipients shall submit Interim Performance Reports in accordance with this article and 2 CFR 200 §

329. The recipient may submit reports in electronic form.

(b) Content: Reports shall detail technical progress to date and report on all problems, technical issues, or major developments that arose during the reporting period. The reports shall discuss each of the topics listed below:

(1) A comparison of actual accomplishments with the goals and objectives established for the period, the findings of the investigator, or both.

(2) Reasons why established goals were not met, if appropriate.

(3) Other pertinent information including analysis and an explanation of cost overruns.

(c) Submission: The recipient shall submit Interim Performance Reports quarterly within 30 days after completion of the reporting period throughout the term of the agreement. The first period begins on the effective date of the agreement. The recipient shall submit one copy of the Interim Performance Report to:

(…