Attachment 1 PWS_TEMPLATE.docx

CUI

ATTACHMENT 1 – PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENTNOTE: GENERAL INFORMATION IS PRESENTED IN (RED FONT) WITH PARENTHESIS BORDERS, EXAMPLES ARE PROVIDED IN RED ITALICIZED FONT, WHILE FILL-IN GUIDANCE IS PRESENTED IN [BLUE FONT] WITH BRACKET BORDERS. PLEASE DELETE ALL RED AND BLUE FONT WHEN FINALIZING THIS DOCUMENT.

FOR

THE UNIVERSITY CONSORTIUM FOR APPLIED HYPERSONICS (UCAH)

1.0 BACKGROUND: Under the authority of 10 United States Code (U.S.C.) § 4021 and §4022, this University Consortium for Applied Hypersonics (UCAH) Agreement with Texas A&M Engineering Experiment Station (TEES) is in support of the Joint Hypersonics Transition Office (JHTO), within Office of the Assistant Secretary of Defense for Science and Technology (OASD)(S&T)) in Office of the Undersecretary of Defense Research and Engineering (OUSD (R&E)). The UCAH is a collaborative ecosystem of universities, government, industry, national laboratories, Federally-Funded Research and Development Centers (FFRDCs), University-Affiliated Research Centers (UARCs), and other partners. The mission of the consortium is to mobilize the academic community to serve Department of Defense (DoD) requirements in applied technology and workforce development relevant to hypersonic technology.

2.0 TECHNICAL REQUIREMENTS:

Respondents shall submit an executive summary of the proposed solution, which clearly addresses their vision for the Consortium, structure, and management.

2.1 Consortium Structure and Functions. At a minimum, shall address the following from the Statement of Objectives (SOO).

· Leadership & Governance

· Consortium mission and vision

· Operating charter

· Business practices

· Proposed responsibilities as Consortium Manager

· Intended level of interaction/oversight with Consortium members

· Plan/ability to assist new and nontraditional defense contractors in understanding the DoD customer, mission, and processes

· Proposed Consortium structure, processes for providing administrative and financial oversight, plans to develop and implement Consortium by-laws, plans for ensuring consistent and impactful interaction between the Government and Consortium

· Advisory Boards (AB)

· Plan for establishing ABs

· Framework for scope and accountabilities for each AB

· Membership Administration

· Outreach to potential members

· Plans for establishing shared goals, commitments, buy-in, and relationships among consortium members rather than just between members and the consortium manager

· Demonstrated current capability, as well as future plans for member retention and growth

· Consortium cost model (i.e., fees) for consortium members.

· Plan to share information across the membership

· Plan to foster teaming among the membership

· Security

· Plan for compliance with security requirements in SOO

· Capability and capacity to implement Government’s security procedures and handle, transmit and store controlled unclassified, confidential, and classified information

· Capability and capacity to manage Consortium member’s security clearance requirements

· Plan to ensure Operational Security, ensure compliance with ITAR and other regulatory and statutory obligations

· Reporting

· Plan for compliance with reporting requirements in SOO and schedule of reports

· Proposed metrics and reporting to validate that the Government’s intent for the Consortium is being met including but not limited to reinvestments, Consortium growth, level of NDC participation, cost savings, minimizing time to award, etc.

2.2 Project Solicitation, Selection and execution

· Plan for prototype/research project awards processes and execution

· Plan for Consortium members to be able to provide unsolicited solutions

· Plan for administrative oversight of prototype/research projects

· Plan to provide funding oversight for the consortium OT Agreement and all sub prototype/research projects

· Plan for University Capstone Projects

· Plan and framework for Hypersonics Journal

2.3 Services and Activities

· Plan for webpage and electronic communications

· Plan for two annual in-person events

· Plan to provide logistical and information support to membership and member-customer functions such as Industry Day events

· Plan to enhance workforce development, including training and professional courses

3.0 DELIVERY SCHEDULE: [Insert the detailed technical requirements for the proposed project – this information should not be written in first person, but it should include all of the detailed information proposed by the COMPANY to meet the Government’s requirement.]

4.0 MILESTONE PAYMENT SCHEDULE: The projected timeline to reach full or partial successful project completion will be 24 months in accordance with the milestones below. [Tie milestone payments back to the Technical Requirements.]

5.0 DATA RIGHTS ASSERTIONS: (Delete if not applicable) In accordance with the Terms and Conditions, the COMPANY is asserting data rights on Non-commercial Technical Data or Computer Software. The Government's rights to use, release, or disclose the following Technical Data or Computer Software is restricted as shown below:

[Insert proposed data rights.]

1 If the assertion is applicable to items, components, or processes developed at private expense, identify both the data and each such item, component, or process.

2 Generally, the development of an item, component, or process at private expense, either exclusively or partially is the only basis for asserting restrictions on the Government's rights to use, release, or disclose Technical Data pertaining to such items, components, or processes. Indicate whether development was exclusively or partially at private expense. If development was not at private expense, enter the specific reason for asserting that the Government's rights should be restricted.

3 Enter asserted rights category (e.g., government purpose license rights from a prior contract, limited, or specifically negotiated licenses).

4 Corporation, individual, or other person, as appropriate.

6.0 SUCCESSFUL COMPLETION CRITERIA: This agreement, or portions thereof, will be considered successfully completed upon (1) acceptance of funded milestones identified under Section 8.0 of the Performance Work Statement, (2) Government receipt and acceptance of deliverables, and (3) the delivery and demonstration of the technical requirements.

The following table provides the criteria for successful completion. Upon receipt of delivery, with associated functional testing documentation indicating proper functionality of those prototypes, the Government will make a determination of acceptance. The acceptance thresholds briefly describe the minimum acceptable standards for successful completion. These thresholds are critical to the success of prototype projects awarded through this consortium.

Flight Test

NLT

9/30/2025

7.0 SIGNIFICANT PARTICIPATION: Use of the 10 U.S.C. § 4022 prototype authority for this OT Agreement is contingent on the significant participation of at least one NDC, NRI, and/or SB. The proposed NDC(s), NRIS(s) and/or SB(s) and the nature of their participation for this OT Agreement is identified below.

Controlled by: Washington Headquarters Services CUI Category: PROCURE Limited Dissemination Control: FEDCON POC: Stephanie Koessel, Stephanie.p.koessel.civ@mail.mil

CUI