J-4-NRO_SOO.docx

National Reconnaissance Office (NRO) Collaborative Project Order (CPO) Statement of Objectives (SOO)

1.0 PURPOSE

The purpose of this Collaborative Project Order (CPO) is to enable Government-directed technology transfer, early-stage technology transition, and ecosystem engagement activities in support of National Reconnaissance Office (NRO) mission priorities, in coordination with the Air Force Office of Scientific Research (AFOSR), and consistent with the authority and objectives of the Umbrella Partnership Intermediary Agreement (PIA).

Under this CPO, the Partnership Intermediary shall operate as a non-inherently governmental enabling mechanism to provide facilitation, analytic, coordination, and engagement support that enhances the Government’s ability to identify, assess, and connect research, innovation, mission-relevant technologies, partners, and transition pathways aligned to NRO intelligence, space reconnaissance, and national security mission needs.

This CPO supports NRO-aligned activities spanning multiple locations, mission organizations, and functional efforts—including technology awareness, transition pathway shaping, commercialization-adjacent engagement, and ecosystem coordination—while preserving Government authority over all decisions related to prioritization, intelligence operations, acquisition, transition execution, and operational adoption.

All activities under this CPO shall be executed solely in accordance with Government direction and documented in AFOSR-approved Project Plans, consistent with applicable intelligence community, Department of Defense, and Department of the Air Force authorities, policies, and security requirements.

2.0 BACKGROUND

2.1 National Reconnaissance Mission Context

The National Reconnaissance Office (NRO) is a Department of Defense organization and a member of the United States Intelligence Community responsible for developing, acquiring, launching, and operating space-based reconnaissance systems in support of U.S. national security.

The NRO operates within a highly dynamic and rapidly evolving space and technology environment characterized by accelerating commercial innovation, increasing system complexity, expanding data volumes, and compressed timelines for relevance. Maintaining technological advantage requires continuous awareness of emerging science, technologies, partners, and innovation pathways that may inform future intelligence capabilities and mission architectures.

To support this environment, NRO engages across government, industry, academia, laboratories, and non-traditional technology communities to improve visibility into innovation trends, emerging capabilities, and potential transition pathways—without committing to specific acquisition, programmatic, or operational outcomes.

2.2 NRO Innovation, Commercialization, and Transition Environment NRO technology development and innovation activities occur within the broader Intelligence Community and Department of Defense ecosystem, requiring coordination across multiple organizations, missions, and stakeholders. These activities may involve:

· Engagement with basic and applied research organizations;

· Interaction with commercial space, dual-use technology providers, and non-traditional performers;

· Participation in cross-government working groups, technical exchanges, and exploratory forums; and

· Early-stage examination of technologies and methods that may inform future intelligence collection, processing, or mission integration concepts.

These activities are designed to accelerate learning, reduce transition friction and improve awareness of technologies and partners capable of supporting NRO mission priorities. This Collaborative Project Order (CPO) provides a compliant, flexible mechanism to support such activities in a facilitative and non-binding manner.

2.3 Technology Transfer, Transition, and Commercialization Context Within the NRO mission context:

· Technology transfer is applied as the intentional sharing and dissemination of ideas, data, information, and enabling technologies arising from Department of the Defense–funded research, development, and innovation activities to external partners, including industry, academia, and non-traditional space enterprises, for awareness and collaboration purposes.

· Technology transition is applied as structured transition enablement focused on:

· Early-stage pathway identification,

· Stakeholder connectivity,

· Transition and feasibility awareness,

· Commercialization or adoption planning, and

· Alignment with applied research, prototyping, experimentation, or operational pathways

· Commercialization enablement activities may support awareness of dual-use opportunities, non-Government maturation pathways, and market-driven adoption mechanisms, where appropriate, without obligating the Government to pursue specific vendors, technologies, or acquisition strategies.

Activities conducted under this CPO support transition readiness and informed decision-making, not system insertion, acquisition execution, or fielding outcomes.

2.4 Use of the Partnership Intermediary Agreement Mechanism

This CPO is executed under the Partnership Intermediary Agreement (PIA), authorized by 15 U.S.C. § 3715 and 10 U.S.C. § 2514, which enables the Department of the Air Force to leverage qualified non-Federal entities to facilitate collaboration, ecosystem engagement, and transition awareness activities.

The PIA mechanism supports NRO by enabling:

· Rapid, compliant engagement with traditional and non-traditional partners;

· Non-FAR facilitation, coordination, and engagement activities;

· Separation of inherently governmental decision-making from non-governmental support; and

· Flexible execution aligned to mission tempo and evolving technology landscapes.

All Government direction, prioritization, and acceptance of work under this CPO remains with AFOSR, consistent with the Umbrella PIA governance framework.

2.5 Relationship to AFRL, AFOSR, and the DAF S&T Enterprise

While NRO is mission- and capability-focused, activities under this CPO may intersect with broader Department of the Air Force and AFRL science and technology efforts, including basic research, applied research, prototyping, and transition pipelines.

Coordination with AFRL, AFOSR, and other DoD and Government organizations may occur, when authorized, to:

· Inform technology awareness and pathway shaping;

· Support alignment between research investments and operational needs; and

· Enable connectivity across the DAF research, innovation, and acquisition ecosystem.

Such coordination does not alter NRO’s mission responsibilities or AFOSR’s role as the sole directing authority under this CPO.

2.6 Relationship to the Umbrella PIA SOO

This CPO is issued under, and subject to, the terms and conditions of the Partnership Intermediary Agreement (PIA) Umbrella Statement of Objectives (SOO), which is incorporated herein by reference.

The Umbrella SOO defines the full menu of allowable Task Areas, Additional Capabilities, roles, authorities, financial controls, and execution constraints applicable to this CPO.

2.7 Activated Task Areas

For this CPO, the Government may activate one or more of the following Task Areas, as defined in the PIA Umbrella SOO:

· Task Area 1 — Partnership Development & Agreement Enablement

· Task Area 2 — Technology Transfer, Technology Transition & Market Intelligence

· Task Area 3 — STEM, Workforce & Talent Pipeline Development

· Task Area 4 — Technical Expertise, Studies & Analytic Assessments

· Task Area 5 — Data Tools, Analytic Platforms & Innovation Support

· Task Area 6 — Program Management, Engagement and Governance Support & Event Facilitation

· Task Area 7 — Outreach, Communication & Knowledge Transfer

· Task Area 8 — Other Government-Directed, T3-Aligned Facilitative Support

Activation of a Task Area authorizes only the categories of activity that may be directed by the Government. Task Areas do not constitute requirements, minimums, or guarantees of work.

Specific activities, deliverables, staffing, schedules, and funding associated with any Task Area shall be defined solely through Government-approved Project Plans.

2.8 Additional Capabilities

The following Additional Capabilities from the PIA Umbrella SOO may be utilized under this CPO when expressly directed by the Government and documented in an approved Project Plan:

· A.1 — Collaboration Environments & Technical Engagement Environments - includes co-working, meeting, event, or secure collaboration environment — may be provided or accessed when expressly directed by the Government. Any such environment, including size, location (e.g., proximity to AFOSR facilities), duration, configuration, or security posture, shall be specified in an approved Project Plan and is not guaranteed or required absent such direction.

· A.2 — Innovation Ecosystem Support & Cross-Sector Enablement

· A.4 — Data-Enabled Insights & Cross-Portfolio Integration

· A.5 — Communication Platforms, Tools & Knowledge-Sharing Infrastructure

· A.6 — Government-Approved Special Capability

Additional Capabilities are enabling functions only and shall not be proposed, priced, or performed as stand-alone services. Utilization of any Additional Capability shall be bounded by Government direction, approved Project Plans, available funding, and applicable security requirements.

2.9 Sponsor-Specific Scope Context

This CPO is managed by AFOSR under the AFRL Partnership Intermediary Agreement. Activities conducted under this CPO may support AFOSR priorities and, when authorized by the Government, may involve engagement with other AFRL directorates or divisions as mission partners or co-funders. Such participation does not alter AFOSR’s role as the sole directing authority under this CPO.

2.10 Relationship to Reporting and Deliverables

Reporting requirements and deliverables under this CPO are governed by Government-issued attachments and approved Project Plans. Deliverables are execution artifacts only and do not expand or modify the scope authorized by the Umbrella SOO or this CPO.

3.0 ROLES, AUTHORITIES, AND MISSION PARTNER FRAMEWORK

Roles, authorities, and execution constraints applicable to this Collaborative Project Order (CPO) are governed by the Partnership Intermediary Agreement (PIA) Umbrella Statement of Objectives (SOO), which is incorporated herein by reference.

This section summarizes the CPO-specific application of those roles and authorities in support of National Reconnaissance Office (NRO) mission-aligned technology transfer, early-stage transition enablement, and ecosystem engagement activities conducted in partnership with AFOSR.

Nothing in this CPO alters the roles, authorities, or limitations established in the Umbrella SOO.

3.1 AFRL / AFOSR Role (Managing Organization)

The Air Force Office of Scientific Research (AFOSR), as the managing organization for this CPO under the AFRL Partnership Intermediary Agreement (PIA), serves as the sole Government authority responsible for direction, oversight, prioritization, and stewardship of all activities executed under this CPO. Under this CPO, AFOSR shall:

Serve as the sole Government authority for direction, approval, prioritization, and acceptance of work;

· Approve, modify, and oversee all Project Plans executed under this CPO;

· Provide Government direction, guidance, and prioritization to the Partnership Intermediary consistent with this SOO;

· Review deliverables and assess performance against outputs, metrics, and outcomes established through Government direction and documented in AFOSR-approved Project Plans; and

· Ensure compliance with statutory authority, Department of the Air Force policy, and the separation of inherently governmental and non-governmental functions.

Nothing in this CPO authorizes NRO, mission partners, or any other organization to provide direction to the Partnership Intermediary independent of AFOSR.

3.2 Mission Partner Role (NRO)

NRO participates in this CPO as a mission partner and co-sponsor, supporting technology transfer, early-stage transition, and commercialization enablement activities aligned to NRO’s space enterprise mission.

NRO participation may include, when coordinated through AFOSR-established governance mechanisms:

· Identification of mission needs, capability gaps, priority technology areas, and transition interests;

· Participation in Government-led reviews, working groups, engagement forums, cohort activities, and coordination events;

· Provision of technical, operational, or market context to inform ecosystem engagement, pathway shaping, and transition awareness; and

· Coordination across multiple NRO-aligned organizations, stakeholders, or execution environments, as authorized.

The Partnership Intermediary shall not seek or accept direction, prioritization, or approval from Mission Partners without AFOSR authorization. Should a Mission Partner provide such direction, the PI's procedure is to refer the Mission Partner to the AFOSR COR and concurrently notify the COR of the communication.

3.3 Partnership Intermediary Role

The Partnership Intermediary operates under this CPO as a non-inherently governmental enabling entity, consistent with the Umbrella SOO, and shall:

· Provide facilitative, analytic, coordination, and engagement support aligned to NRO mission needs, as authorized through AFOSR-approved Project Plans;

· Support technology transfer awareness, transition pathway shaping, ecosystem engagement, and commercialization-adjacent activities as directed by the Government;

· Enable coordination across multiple concurrent NRO-aligned execution environments, when authorized; and

· Maintain AFOSR as the sole Government authority for direction, approval, and performance assessment.

The Partnership Intermediary shall not:

· Perform inherently governmental functions;

· Make funding, acquisition, selection, prioritization, or approval decisions;

· Negotiate, execute, or legally draft agreements;

· Recommend specific vendors, technologies, or acquisition strategies; or

· Obligate the Government or third parties.

All activities performed under this CPO are advisory, descriptive, facilitative, and non-binding in nature.

3.4 Concurrent Execution Environment Support

Activities under this CPO may support multiple NRO-aligned execution environments operating simultaneously, which may differ by location, mission focus, or functional emphasis.

Support across concurrent environments may include, when authorized through AFOSR-approved Project Plans:

· Parallel engagement activities, cohorts, or working groups;

· Coordination across research, transition, commercialization, and ecosystem engagement efforts; and

· Shared analytics, reporting, and knowledge-transfer products.

Nothing in this section requires uniform execution models, staffing constructs, or activity distribution across environments. All scope, sequencing, and prioritization decisions remain solely within Government authority.

All activities, decisions, and execution actions under this CPO shall remain fully traceable to Government direction and documented Project Plans.

4.0 SCOPE

This Collaborative Project Order (CPO) applies the authorities and allowable scope of the Umbrella Partnership Intermediary Agreement (PIA) to NRO-specific objectives in support of mission-aligned technology transfer, early-stage technology transition, commercialization enablement, and innovation ecosystem engagement.

Under this CPO, the Partnership Intermediary shall provide non-inherently governmental facilitation, analytic, coordination, and engagement support to enable AFOSR-directed activities that support NRO mission priorities, including technology awareness, pathway identification, partner connectivity, commercialization readiness, and ecosystem coordination.

This CPO is structured to support multiple, concurrent NRO innovation and transition efforts, which may operate in parallel across different locations, organizational constructs, and mission focus areas, while preserving Government control over all decisions related to requirements, prioritization, acquisition, transition execution, and operational adoption.

4.1 Mission Problem Framing & Opportunity Context

When expressly directed by AFOSR through an approved Project Plan, allowable activities may include non-binding support to frame NRO mission needs and opportunity spaces, including:

· Translation of Government-provided mission challenges, capability gaps, or areas of interest into descriptive problem statements or engagement constructs;

· Support for shaping workshops, working groups, or engagement activities aligned to NRO mission priorities and space enterprise needs; and

· Documentation of operational, architectural, or enterprise context to inform ecosystem engagement and early transition or commercialization awareness.

All activities under this subsection are advisory and descriptive in nature and do not constitute requirements definition, acquisition planning, or operational tasking.

4.2 Technology Transfer, Transition & Commercialization Enablement Scope When expressly directed by AFOSR through an approved Project Plan, allowable activities may include:

· Technology transfer awareness activities, including dissemination of Government-funded research outcomes, enabling technologies, data, and insights to relevant external audiences;

· Early-stage technology transition support, including pathway identification, stakeholder mapping, feasibility awareness, and transition-adjacent planning;

· Industry engagement, market exposure, and ecosystem outreach activities;

· Commercialization enablement activities focused on awareness of dual-use potential, non-Government maturation pathways, and market-driven adoption mechanisms; and

· Connectivity between NRO mission needs and relevant academic, industry, nonprofit, Government, and commercial space stakeholders.

Activities under this CPO may support multiple potential transition pathways, including advanced development, prototyping, experimentation, or commercial adoption, but do not require or imply system insertion, acquisition execution, or fielding outcomes.

4.3 Partnership, Agreement & Ecosystem, Environment and Engagement Scope When authorized by AFOSR, allowable activities may include:

· Identification, assessment, and engagement of partners across academia, industry, nonprofit organizations, Government laboratories, and non-traditional or commercial space entities;

· Facilitation and coordination support related to non-FAR collaboration instruments (e.g., MOUs, MOAs, EPAs, CRADAs), consistent with statutory authority and Government determinations;

· STEM and workforce ecosystem engagement activities aligned with AFOSR scientific priorities and long-term talent pipeline objectives;

· Collaboration environments, engagement platforms, and coordination tools (including physical, virtual, or secure collaboration environments when authorized) that support Government-directed activities across Task Areas

· Support for cohorts, working groups, conferences, workshops, collaborative forums, and ecosystem convenings spanning Government, academia, and industry; and

· Enablement of bidirectional information flow between research performers, commercial partners, and NRO stakeholders.

The Partnership Intermediary shall not negotiate, execute, approve, or legally draft agreements on behalf of the Government.

4.4 Analytics, Studies & Decision-Support Enablement

When authorized by AFOSR, allowable activities may include:

· Access to subject-matter experts (SMEs) and technical expertise;

· Structured studies, landscape assessments, commercialization or ecosystem analyses, and descriptive analytic products;

· Development and use of Government-owned sandbox environments, data tools, dashboards, and visualization products;

· Exploratory data prototyping and analytic proof-of-concept activities to support experimentation planning, technology transition awareness, or decision insight; and

· Documentation of engagement outcomes, lessons learned, and non-binding insights to support Government awareness and decision-making.

All analytic outputs shall remain descriptive and advisory and shall not include recommendations or decisions related to funding, acquisition, or operational employment.

4.5 Outreach, Communication & Knowledge Transfer

When expressly directed by AFOSR, allowable activities may include:

· Preparation of factual, Government-approved outreach and knowledge-transfer products;

· Documentation and dissemination of engagement outcomes, ecosystem insights, and transition awareness products; and

· Support for internal and external communication materials (e.g., briefings, summaries, reports, digital content), subject to Government review, approval, and public release controls.

Outreach activities under this CPO shall be non-advocacy in nature and shall not promote specific vendors, solutions, or acquisition outcomes.

4.6 Nature of Support & Scope Control

All activities performed under this CPO shall be facilitative, analytic, descriptive, and non-binding in nature. The Partnership Intermediary:

· Shall not perform inherently governmental functions;

· Shall not make funding, acquisition, selection, prioritization, or approval decisions;

· Shall not obligate the Government or third parties; and

· Shall not perform system development, acquisition execution, or operational fielding activities.

All work under this CPO shall be initiated only through AFOSR-approved Project Plans and shall remain within the Task Areas and Additional Capabilities authorized under the Umbrella PIA SOO and activated for this CPO.

Nothing in this section expands or limits the Task Areas or Additional Capabilities available to the Government under the Umbrella PIA.

5.0 OBJECTIVES

Objectives under this Collaborative Project Order (CPO) emphasize technology transfer awareness, early-stage technology transition enablement, ecosystem connectivity, and structured collaboration in support of NRO mission priorities and downstream Government decision-making.

Objectives under this CPO are enabling in nature and focus on awareness, connectivity, pathway shaping, and collaboration readiness. They do not require or imply system development, acquisition execution, operational fielding, or transition outcomes under this CPO.

Specifically, objectives of this CPO include:

· Advance Technology Transfer and Transition Awareness Increase visibility, understanding, and accessibility of technologies, research outcomes, and innovation activities relevant to NRO mission needs by supporting Government-directed technology transfer and early-stage transition awareness activities.

· Enable Transition Pathway Identification and Shaping Identify, map, and describe potential transition, integration, commercialization, or adoption pathways—including Government, commercial, and dual-use pathways—without requiring system insertion, acquisition decisions, or fielding outcomes.

· Strengthen Industry, Academic, and Innovation Ecosystem Connectivity Expand and strengthen mission-aligned engagement across Government organizations, industry (including non-traditional vendors and small businesses), academia, nonprofit entities, laboratories, and innovation intermediaries to improve partner awareness, readiness, and connectivity.

· Support Commercialization and Dual-Use Awareness Enable awareness of commercialization opportunities, market relevance, and dual-use potential for technologies aligned with NRO mission areas through descriptive assessments, ecosystem mapping, and partner engagement activities, consistent with Government determinations.

· Support Cohorts, Cross-Functional Teams, and Collaborative Working Groups Enable the formation and support of Government-directed cohorts, working groups, cross-functional teams, and collaborative forums—including integration of interns, fellows, graduate students, and emerging talent—designed to accelerate learning, collaboration, and transition readiness across NRO mission priorities.

· Provide Data-Enabled Insight and Decision Support Improve NRO situational awareness and planning through descriptive analytics, landscape assessments, market intelligence, ecosystem studies, and data-enabled tools that inform transition prioritization, partnership strategy, and mission alignment without recommending funding or acquisition decisions.

· Enable Mission-Focused Engagement and Collaboration Forums Support NRO priorities through workshops, industry days, technical exchanges, challenges, conferences, and other engagement mechanisms that increase shared understanding, alignment, and readiness across Government and non-Government stakeholders.

· Support Transparent, Compliant, and Auditable Execution Enable clear planning, documentation, reporting, and assessment of Government-directed activities conducted under this CPO through outputs, metrics, and outcomes established by the Government and documented in approved Project Plans.

Achievement of these objectives will be assessed at the CPO level solely against outputs, metrics, and outcomes established through Government direction and documented in AFOSR-approved Project Plans and associated performance or reporting frameworks. Objectives do not, by themselves, create performance requirements or authorize work absent such Government direction.

6.0 GOVERNANCE FRAMEWORK

All work under this CPO shall be executed only in accordance with AFOSR-approved Project Plans, which define authorized scope, funding, schedule, deliverables, and performance expectations.

AFOSR, as the managing organization for this CPO under the AFRL Partnership Intermediary Agreement (PIA), will establish and maintain appropriate governance constructs (e.g., boards, working groups, review forums) to provide oversight, coordination, and performance management for activities conducted under this CPO, consistent with Sections 3.0 (Roles and Authorities) and 4.0 (Scope).

Mission Partners may participate in AFOSR-established governance structures, coordination forums, and review activities, as appropriate; however, AFOSR retains sole authority for direction, approval, prioritization, and acceptance of work under this CPO.

The Partnership Intermediary shall support governance processes by preparing materials, facilitating coordination, tracking actions and decisions, and documenting outcomes. The Partnership Intermediary shall not serve as a decision-maker, exercise approval authority, or perform inherently governmental functions.

7.0 ILLUSTRATIVE ACTIVITY LEVELS (FOR PROPOSAL DEVELOPMENT ONLY)

This section is provided solely to support offeror proposal development and understanding of the potential scale, variability, and mix of activities that may be authorized under this Collaborative Project Order (CPO).

The illustrative ranges below do not constitute operational plans, forecasts, requirements, guarantees, minimums, or performance expectations and shall not be interpreted as required staffing levels, activity volumes, or deliverable targets.

Actual activity levels, staffing, outputs, priorities, sequencing, and geographic distribution will be determined exclusively by the Government through AFOSR-approved Project Plans and may differ materially from the illustrative ranges provided.

Multiple NRO-aligned activities, locations, cohorts, or engagement constructs may operate concurrently under this CPO when authorized by the Government.

7.1 Illustrative Level of Effort

For proposal planning purposes only, the illustrative annual level of effort under a single NRO CPO may range from approximately:

· 8,000 to 16,000 labor hours per year

This illustrative range generally corresponds to approximately 2 to 8 full-time equivalent (FTE) personnel, depending on the mix of Task Areas activated, emphasis on technology transition support, commercialization enablement, cohort or working-group activity, analytics, data prototyping, engagement volume, and use of specialized expertise.

These figures are provided only as scale context and do not represent staffing expectations, commitments, or guarantees.

7.2 Illustrative Engagements, Cohorts, and Convenings (Non-Binding) When authorized through Government-approved Project Plans, illustrative annual ranges may include a mix of engagement activities such as:

· Major engagements: approximately 2 to 10 per year, which may include large conferences, industry days, cohort kickoffs, multi-day workshops, or enterprise-level forums. Event scale, duration, participation levels, and location may vary widely.

· Minor engagements or interactions: approximately 50 to 250 per year, including meetings, technical exchanges, working sessions, cohort meetings, mentoring sessions, or virtual engagements.

· Cohorts, cross-functional teams, or working groups: approximately 5 to 25 active efforts operating concurrently or episodically, potentially spanning Government, academia, industry, and non-traditional partners.

All engagement formats, frequency, and scale will be determined by the Government and documented in approved Project Plans.

7.3 Illustrative Analytics, Data Prototyping, and Knowledge Products (Non-Binding) For proposal planning purposes only, illustrative annual ranges may include:

· Structured studies, assessments, or analytic reports: approximately 6 to 30 per year;

· Dashboards, data tools, analytic platforms, or data prototypes (new development or sustained operation): approximately 3 to 12 per year; and

· Recurring updates or performance-tracking products, as directed by the Government, which may be event-driven, milestone-based, cohort-based, or periodic (e.g., quarterly).

Specific metrics, milestones, data maturity expectations, and evaluation criteria will be defined only at the Project Plan level.

7.4 Illustrative Technology Transition, Commercialization, and Partnership Enablement (Non-Binding) When expressly authorized by the Government, illustrative planning ranges may include:

· Technology transition or commercialization enablement actions, including pathway mapping, partner matching, transition readiness awareness, or ecosystem coordination: approximately 10 to 50 supported actions per year, subject to Government authority and approval.

· Partnership or agreement enablement actions (e.g., MOUs, MOAs, EPAs, CRADAs, or similar non-FAR instruments): approximately 10 to 40 supported actions per year, subject to Government determinations.

The Partnership Intermediary shall not negotiate, execute, or approve agreements on behalf of the Government.

7.5 Illustrative SME, Specialized Expertise, and Talent Support (Non-Binding) For proposal planning purposes only:

· Subject-matter expert (SME), technical, commercialization, data, or specialized expertise support may range from approximately 300 to 3,000 hours per year, depending on portfolio breadth, technical depth, cohort activity, commercialization focus, analytic requirements, and engagement priorities.

7.6 Illustrative Task Area Distribution (Non-Binding)

For planning purposes only:

· Individual Task Areas may represent approximately 10% to 40% of total annual level of effort.

· Distribution across Task Areas is expected to vary over time and is not intended to be uniform, static, or predictive.

· Multiple Task Areas may be active simultaneously across different NRO-aligned efforts, locations, or focus areas.

8.0 TASK AREAS (MENU OF SERVICES)

This section defines the Task Areas that constitute the menu of allowable facilitative, analytic, and engagement-based services that may be authorized under this Collaborative Project Order (CPO), consistent with the Partnership Intermediary Agreement (PIA) Umbrella Statement of Objectives (SOO).

One or more Task Areas may be activated only through Government-directed Project Plans approved by AFOSR. Task Areas define allowable scope only and do not constitute required work, minimum activity levels, or guarantees of effort. Activities are authorized solely when expressly directed by the Government and documented in an approved Project Plan.

The Partnership Intermediary may not perform inherently governmental functions; may not negotiate, execute, or commit the Government; and may not draft or revise legal instruments.

Task Area 1 — Partnership Development & Agreement Enablement Facilitative and analytic support to identify, assess, and engage mission-aligned partners and enable Government-directed partnership and collaboration activities across Government organizations, industry (including non-traditional and commercial space entities), academia, nonprofit organizations, and allied partners.

Activities support ecosystem connectivity, collaboration readiness, and non-binding agreement enablement, consistent with statutory authority and Government determinations. When

Government-directed, activities may include facilitation and coordination related to non-FAR collaboration instruments (e.g., MOUs, MOAs, EPAs, CRADAs).

The Partnership Intermediary shall not negotiate, execute, or approve agreements on behalf of the Government.

Task Area 2 — Technology Transfer, Technology Transition & Market Intelligence Facilitative and analytic support to enhance awareness, engagement, and readiness related to technology transfer, early-stage technology transition, and commercialization enablement aligned to NRO mission needs.

Activities may include, when Government-directed:

· Dissemination and awareness of relevant technologies, research outcomes, data, and innovation activities;

· Ecosystem, stakeholder, and market intelligence relevant to potential transition or commercialization pathways;

· Identification and descriptive mapping of Government, commercial, dual-use, or hybrid transition pathways;

· Connectivity between NRO mission needs and applied research organizations, industry, non-traditional vendors, and commercial space enterprises; and

· Descriptive feasibility, readiness, or pathway-awareness analyses.

Support may include awareness of Department of the Air Force and AFRL transition, innovation, and SBIR/STTR pipelines, including Phase III partner identification or non-binding matchmaking activities.

The Partnership Intermediary shall not draft topics, evaluate proposals, recommend awards, select performers, or obligate Government funds.

All activities under this Task Area remain descriptive, facilitative, and non-binding.

Task Area 3 — STEM, Workforce & Talent Pipeline Development Facilitative support for STEM, education, and workforce ecosystem activities aligned with NRO mission priorities and long-term talent pipeline objectives, when authorized by the Government.

Activities may include support for:

· Intern, fellow, graduate student, or early-career researcher engagement activities;

· Cross-functional learning teams, cohorts, or workforce exposure initiatives; and

· Engagement with academic institutions and training partners.

Activities emphasize exposure, engagement, and ecosystem strengthening and shall not include recruiting, hiring, personnel selection, or workforce decision-making.

Task Area 4 — Technical Expertise, Studies & SME Access Access to technical expertise, subject-matter experts, and structured analytic studies to support Government awareness, planning, experimentation, and situational understanding.

Activities may include landscape assessments, technical studies, workshop synthesis products, and descriptive analytic outputs.

Activities remain non-binding and shall not include recommendations or decisions related to funding, acquisition, or operational employment.

Task Area 5 — Data Tools, Analytic Platforms & Innovation Support Support for Government-owned data integration, descriptive analytics, visualization tools, dashboards, analytic platforms, and data-enabled collaboration environments that enhance situational awareness, transition insight, and planning.

Activities may include:

· Descriptive data prototyping and exploratory analytics;

· Development or operation of Government-owned dashboards or analytic environments;

· Integration of datasets to support portfolio insight, experimentation learning, or ecosystem visibility; and

· User enablement or documentation related to Government-owned tools.

All data, tools, platforms, and analytic outputs shall remain Government-owned and shall comply with applicable security, safeguarding, and data protection requirements identified in the Umbrella PIA and/or applicable Project Plans.

Task Area 6 — Program Management, Engagement Support & Event Facilitation Program coordination, documentation, reporting, governance support, and event facilitation services that support execution of this CPO without exercising decision-making authority.

Activities may include planning support, logistics coordination, action tracking, and facilitation of Government-directed engagements such as workshops, industry days, technical exchanges, working groups, cohorts, forums, demonstrations, or similar activities.

Task Area 7 — Outreach, Communication & Knowledge Transfer Preparation and dissemination of factual, non-promotional, non-advocacy communication and knowledge-transfer materials in support of Government-directed technology transfer, transition, and commercialization awareness activities.

May include websites or portals, newsletters, fact sheets, stakeholder updates, success-story documentation, social media content, paid advertising, briefings, videos, outreach and other factual dissemination products, subject to Government review, approval, and applicable public release controls.

Task Area 8 — Other Government-Directed, T3-Aligned Facilitative Support Other facilitative, analytic, coordination, or enablement support activities expressly directed by the Government and authorized through an approved Project Plan, provided such activities:

· Remain non-inherently governmental;

· Do not involve legal drafting, negotiation, or acquisition decision-making;

· Do not obligate the Government or third parties; and

· Do not expand the scope of this CPO or the Umbrella PIA.

This Task Area provides flexibility to address emerging or cross-cutting Government needs that cannot be reasonably anticipated at the time of CPO issuance and do not otherwise align cleanly with Task Areas 1–7.

Additional Capabilities (A.1–A.6) Additional Capabilities identified in the Umbrella PIA SOO (A.1–A.6) are enabling mechanisms only and do not constitute independent Task Areas or stand-alone services.

Additional Capabilities may be utilized only when expressly authorized by the Government and documented in an AFOSR-approved Project Plan, to support execution of authorized Task Areas.

When activated, Additional Capabilities may include, as appropriate:

· Collaboration environments and technical engagement spaces (physical, virtual, or hybrid) to support Government-directed workshops, technical exchanges, working groups, facilitated discussions, or ecosystem engagement activities;

· Specialized tools, platforms, or infrastructure needed to support analytic, coordination, or engagement activities;

· Secure or controlled-access environments, when required by the Government, consistent with applicable security guidance and Project Plan direction;

· Specialized facilitation, technical, or operational support that enables effective execution of authorized activities but does not involve inherently governmental functions.

The scope, scale, location, duration, configuration, and security posture of any Additional Capability shall be defined solely at the Project Plan level and may vary over time based on mission needs, funding, and Government direction.

Nothing in this section authorizes the Partnership Intermediary to initiate or propose contractor-directed use of Additional Capabilities or to expand the scope of this CPO or the Umbrella PIA.

9.0 PERFORMANCE STANDARDS

The Partnership Intermediary shall perform all activities under this Collaborative Project Order (CPO) strictly in accordance with Government direction and the requirements established in AFOSR-approved Project Plans.

At a minimum, the Partnership Intermediary shall:

· Deliver accurate, well-organized, and professional-quality outputs consistent with Government direction and CPO requirements;

· Meet timelines, milestones, and reporting schedules established in Government-directed Project Plans;

· Maintain timely responsiveness to AFOSR direction, requests, and governance actions, consistent with AFOSR’s role as the sole directing authority under this CPO;

· Ensure all activities comply with applicable laws, regulations, and Government policies, including security, safeguarding, and data protection requirements identified in the Umbrella PIA and/or applicable Project Plans; and

· Operate strictly within the authorized scope of Government-directed Project Plans, refrain from contractor-initiated work outside approved scope, and comply with all non-inherently governmental limitations, including no negotiation authority, no commitment authority, and no legal drafting.

Performance under this CPO will be assessed only against outputs, metrics, and outcomes established through Government direction and documented in AFOSR-approved Project Plans and associated performance or reporting frameworks.

10.0 FINANCIAL MANAGEMENT AND COST TRANSPARENCY

The Partnership Intermediary shall maintain sound financial management practices and internal controls sufficient to ensure full compliance with statutory, regulatory, and Government-directed requirements applicable to this Partnership Intermediary Agreement (PIA) and all Collaborative Project Orders (CPOs).

The Partnership Intermediary shall:

· Demonstrate their financial management system is adequate and compliant with the requirements of 2 CFR 200.302.

· Demonstrate the ability to maintain transparent financial reporting in a manner that is transparent, timely, detailed, and sufficient to support Government oversight, reconciliation, and the audit requirements of 2 CFR 200, Subpart F Audit Requirements.

· Demonstrate the ability to maintain internal financial management controls sufficient to ensure all costs are fully traceable to specific tasks and across orders, are supported by adequate documentation, and which prevents unallowable costs, improper allocation, duplication, or commingling of funds across CPOs or sponsors.

The specific requirements in the bullets that follow apply to Cost-Reimbursable CPOs. For Firm-Fixed-Price (FFP) CPOs, these requirements are not applicable unless explicitly incorporated into the individual FFP CPO.

· Comply with 2 CFR Part 200 (Uniform Guidance) cost principles, including allowability, allocability, reasonableness, consistency, and documentation requirements, as applicable to the nature of this PIA.

· Charge only allowable, allocable, and reasonable costs incurred solely for Government-directed activities authorized in an approved CPO and aligned to the associated Project Plan.

· Align all costs to approved Project Plans, budgets, and funding authorizations, and not incur, obligate, or commit costs outside AFOSR authorization or beyond the scope of an approved CPO.

· Maintain transparent financial reporting for all CPO, including labor, indirects, other direct costs (ODCs), and all other cost elements, in a manner sufficient to support Government oversight, reconciliation, and audit.

· Ensure costs are fully traceable to specific CPOs and Government-directed tasks, and supported by adequate source documentation, labor records, and cost substantiation.

· Operate within Government-approved ceilings, caps, or cost controls, as established in the PIA, individual CPOs, or subsequent Government direction.

· Obtain prior Government review and approval for any changes to labor rates, indirect rates, or cost structures.

· Refrain from incurring costs in anticipation of future CPOs, modifications, or funding, unless expressly authorized in writing by the Government.

· Provide timely access to financial records, supporting documentation, and cost data, as reasonably requested by the Government for oversight, reconciliation, audit, or review purposes.

· Immediately notify the Government of any actual or potential cost overruns, funding shortfalls, rate changes, or material financial risks that may impact performance.

· Maintain internal controls sufficient to prevent unallowable costs, improper allocation, duplication, or commingling of funds across CPOs or sponsors.

· Ensure subcontractor, partner, or third-party costs, if applicable, comply with the same cost principles, documentation standards, and Government-directed limitations applicable to the Partnership Intermediary.

Performance will be assessed against CPO-defined outputs, metrics, and outcomes.

11.0 DELIVERABLES FRAMEWORK

11.1 Deliverables Authority

Deliverables under this CPO are execution artifacts only and shall be established solely through Government direction and documented in AFOSR-approved Project Plans, consistent with the reporting and deliverables framework set forth in Attachment J-7 (Reporting & Deliverables).

Nothing in this section authorizes work, establishes scope, or creates deliverable requirements independent of approved Project Plans.

11.2 Project Plan Alignment

All deliverables shall:

• Be directly aligned to Government-directed activities authorized in approved Project Plans;

• Support program execution, oversight, traceability, and cost allowability; and

• Be scoped, scheduled, and prioritized by the Government through Project Plans and associated governance mechanisms.

Deliverable content, format, frequency, and level of detail may vary by Task Area, mission focus, location, and funding level and may be modified through Government direction without amendment to this SOO.

11.3 Ownership and Use Rights

Unless otherwise directed by the Government:

• All deliverables shall be reviewable and editable by the Government;

• Deliverables shall be provided in Government-specified formats; and

• All deliverables shall be Government-owned, with unlimited Government use rights, consistent with the terms of the PIA and applicable law.

12.0 SECURITY CONSIDERATIONS

The Partnership Intermediary shall comply with all applicable Department of the Air Force, AFRL, AFOSR, and NRO security requirements as specified in the Umbrella PIA and/or applicable Project Plans.

The contractor shall establish and maintain a comprehensive security program in accordance with all applicable Department of Defense (DoD) and Department of the Air Force (DAF) regulations. The contractor's Facility Security Officer (FSO) is responsible for the generation and management of all security plans and procedures.

12.1 Personnel Security & Clearances

This effort may require access to classified information, including North Atlantic Treaty Organization (NATO), Communications Security (COMSEC), Top Secret (TS), and Sensitive Compartmented Information (SCI).

· Clearance Levels: Contractor personnel shall possess a security clearance appropriate to their role. While some key personnel will require a final TS clearance, it is anticipated that only a limited number of positions will necessitate this level. Other personnel may require a final Secret clearance. The government will specify the required clearance level for each position.

· Non-Disclosure Agreements (NDA): All contractor personnel supporting and associated with this effort must have a current NDA on file prior to accessing any sensitive or classified information.

12.2 Information & Operations Security (OPSEC)

The contractor is responsible for safeguarding all government information, from initial handling to final disposition.

· Governing Directives: The program is subject to the National Industrial Security Program (NISP) and will adhere to 32 Code of Federal Regulations (CFR), Part 117.

· Controlled Unclassified Information (CUI): The contractor shall identify, handle, and protect CUI in accordance with DoDM 5200.01, Volume 4, and DFARS 252.204-7012.

· Derivative Classification: Any classified information generated during contract performance shall be derivatively classified and marked consistent with the source material.

· OPSEC Program: The contractor must implement an OPSEC program consistent with AFI 10-701 to protect sensitive and critical information throughout the period of performance.

12.3 System & Communications Security

· System Security Plan (SSP): The contractor shall prepare and maintain an SSP for their information system(s) in accordance with established security categorization and impact levels.

· Communications Security (COMSEC): The contractor may require access to a COMSEC account and must manage all COMSEC equipment and materials in accordance with NSTISS 4005.

12.4 Common Access Cards (CAC)

· In support of long-term project assignments, a Common Access Card (CAC) will be issued to select contractor personnel whose duties require access to Department of Defense (DoD) computer networks, systems, and applications. The provision of CACs is on a strict, as-needed basis. All procedures related to the lifecycle of the CAC, from issuance to final return, will adhere to the Air Force Federal Acquisition Regulation Supplement (AFFARS) Subpart 5352.242-9001, "CACs for Contractor Personnel."

12.5 Required Training

Contractor personnel must complete all required security training, including but not limited to:

· Operations Security (OPSEC) Awareness

· Controlled Unclassified Information (CUI)

· Information Security (AFI 16-1404)

· Antiterrorism and Force Protection (AFI 10-245)

13.0 DATA HANDLING AND TRANSFER REQUIREMENTS

The Partnership Intermediary shall manage all data, tools, documentation, and analytic outputs produced under this CPO to ensure Government ownership, continuity, and transition.

The Partnership Intermediary shall:

• Maintain data and documentation in formats that are fully transferable to the Government or a Government-designated successor;

• Ensure AFOSR retains ownership, full access, and reuse rights to all Government-funded data, tools, platforms, and outputs; and

• Support orderly data transfer, handoff, and knowledge continuity at Project Plan closeout or upon PIA transition, recompete, or completion.

Access to the…