SOW Draft.pdf

United States Air Force Life Cycle Management Center

Architecture & Integration Directorate (AFLCMC/XA)

Directorate-Wide Indefinite Delivery/Indefinite Quantity (ID/IQ) Contract

Statement of Work (SOW)

FA8684-22-R-2006

15 March 2022

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD Contractors only; Critical Technology, 22 October 2021. Other requests shall be referred to AFLCMC/XA Security Office.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the plan. Local reproduction is authorized.

DRAFT

TABLE OF CONTENTS

1.0 Introduction

2.0 Scope

2.1. Category 1 - Capability Development / Development Planning

2.2. Category 2 – Systems Development

2.3. Category 3 - Synthetic Environment Development

3.0 Engineering, Design, and Development

4.0 Architectures

4.1. Open Architectures

4.2. Intellectual Property

4.3. Associate Contractor Agreement

5.0 Order Execution

5.1. Program Management

5.2. Systems Engineering

5.3. Security

5.3.1. Post-award deliverable

5.3.2. FOPR Requirements

5.3.3. Controlled Unclassified Information (CUI)

5.4. Operations Security (OPSEC)

5.4.1. Public Release of Information Request

5.5. Product Support

5.6. Exclusivity Agreements

6.0 Studies, Analyses and Demonstrations

7.0 Post-Award Deliverable

Table 1 – Referenced Documents

1.0 Introduction

The Air Force Life Cycle Management Center, Architecture & Integration Directorate’s (AFLCMC/XA) mission is to work with the requirements community and S&T/Industry to analyze gaps, requirements, missions, threats, and technologies and to develop systems or solutions to address warfighter needs while launching high confidence programs. AFLCMC/XA activities include Modeling, Simulation & Analysis (MS&A), Capability Development/Development Planning (CD-DP), Cost Analysis/Trades, Technical Risk Reduction/Test Engineering, Standards and Architecture Development and Curation, Software Development and Curation, and Advanced Synthetic/Virtual Simulator Environments Development for Operational Test and Training.

AFLCMC/XA (also known as the United States Government (USG) within this SOW) develops innovative approaches that bring multi-domain systems capabilities, characterization of new technologies and systems through studies, recurrent demonstration and rapid development to enable rapid prototyping, test and capability transition to yield cost effective warfighting capability. Activities within AFLCMC/XA span from hardware technology, software technology, multi-level security analysis to open architecture design and implementation.

AFLCMC/XA will support future operations by leveraging the Indefinite Delivery/Indefinite Quantity (ID/IQ) to rapidly contract for a variety of capabilities across the portfolio. The work is not envisioned for singular use, rather an enabler for multi-domain, multi-level security development, analysis, and synthetic environments.

2.0 Scope

This Statement of Work (SOW) establishes the requirements for the AFLCMC/XA Indefinite Delivery Indefinite Quantity (ID/IQ) contract within three categories. This SOW establishes three categories with specific attributes, as defined in section 2.0, quantifying the broad spectrum of AFLCMC/XA activities, projects, and programs.

Contractor(s) is defined as any vendor developing and submitting a proposal for award consideration into one or more categories; Contractors may submit proposals for one or more categories, but will be evaluated and onboard separately within each category. This SOW does not specify management activities or requirements for individual AFLCMC/XA activities, projects, or programs. Follow-on Fair Opportunity Proposal Requests (FOPR) will be developed by individual activities, projects, or programs. Each FOPR will have tailored security requirements with classification levels ranging from UNCLASSIFIED to TS//SCI/SAR.

Additionally, FOPR requirements encompass a full range of analysis, development, engineering, test, product support planning, and other acquisitions activities across multiple Department of Defense (DoD) acquisitions pathways.

XA activities, programs, and projects are ever-evolving due to rapid changes in technology, warfighter needs, and global threat posture. Post-award, categories may be added, deleted or changed through modification. Contractors awarded to a category will compete for individual Orders within their awarded category.

2.1. Category 1 - Capability Development / Development Planning Capability Development and Development Planning includes any activities associated with concept development/maturation modeling, simulation & analysis, product support planning, and future technology integration. Examples of these activities include, but are not limited to, the development of simulations at the engineering, engagement, mission, and campaign levels as well as the analysis associated with these simulations, early systems engineering plans, and models that are a part of pre-program of record activities.

Additionally, Contractors should be able to conduct hardware and software development to support activities up through Low Rate Initial Production (LRIP) while also completing associated systems engineering plans and models. Contractor activities may range in classification from UNCLASSIFIED to TS//SCI//SAR and should also consider factors related to engineering cost, product support, and test and evaluation.

2.2. Category 2 - Systems Development

Systems Development consists of innovative approaches to develop a wide range of systems addressing warfighter needs and supporting future program launch across the AFLCMC/XA portfolio. Activities include, but are not limited to, component level engineering, additive manufacturing, rapid prototyping, and requirements analysis supporting Department of Defense (DoD) acquisitions processes and any other activities up to LRIP. Systems development approaches characterize new technologies and system concepts providing evolutionary, revolutionary, and disruptive capabilities for the United States Air Force (USAF), AFLCMC/XA, Joint and other partners. Key sample attributes include, but are not limited to, open source infrastructure, early systems-engineering, integration of COTS/GOTS/Development both hardware and software, product support planning, cyber security planning, innovative capability development and transition applied within varying levels of security ranging from UNCLASSIFIED to

TS//SCI//SAR.

2.3. Category 3 – Synthetic Environment Development

Simulation Development includes, but is not limited to, development, testing, deployment, and operation within a simulated environment. Simulation development encompasses hardware and software solutions accounting for factors of product support, test and evaluation, and engineering. Activities include, but are not limited to, design and development, systems engineering, use of engineering tools, open standards, and government reference architecture associated with the development of platform-agnostic, synthetic environments that support multi-domain operational training. Simulation will operate and occur at varying levels of fidelity across geographically distributed sites and across multiple security levels ranging from UNCLASSIFIED to TS//SCI//SAR governed by personnel and facility access. Platform-agnostic, synthetic environments are the future for test of combat aircraft and training of personnel by the DoD, the USAF, Joint and other partners.

3.0 Engineering, Design, and Development

The Contractor shall plan for and develop design for new, developmental, existing and/or modified hardware and software; and support all design activities and cybersecurity as defined in individual Orders. The Contractor shall perform disciplined technical planning, coordination and execution of engineering to ensure product development includes strict application of technical metrics and processes, incorporating maintainability and supportability into the design. The Contractor shall provide technical documentation, data models, engineering tools, and support all technical reviews and airworthiness tasks as defined in individual Orders.

4.0 Architectures

4.1. Open Architectures

The Contractor shall ensure its designs incorporate open architectures that enable capabilities and allow for integration across multiple platforms, as defined in FOPRs.

4.2. Intellectual Property

The preference for data associated with the deliverables under this contract is no limitations on use, modification, reproduction, release, performance, display, or disclosure. Contracts shall deliver products, artifacts, models, and other associated items according to data rights as defined in FOPRs.

4.3. Associate Contractor Agreement

The Contractor may be required to enter into Associate Contractor Agreements (ACAs) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement in accordance with (IAW) AFFARS PGI 5317.9000.

The ACAs shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources, essential for AFLCMC/XA activities, which shall ensure the greatest degree of cooperation for the development of programs to meet the terms of the contract.

ACAs shall include the following general information:

• Identify the associate Contractors and their relationships

• Identify the program involved and the relevant Government contracts of the associate Contractors.

• Describe the associate Contractor interfaces by general subject matter.

• Specify the categories of information to be exchanged or support to be provided.

• Include the expiration date (or event) of the ACA

• Identify potential conflicts between relevant Government contracts and the ACA;

include agreements on protection of proprietary data and restrictions on employees.

The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of the failure to resolve a disagreement with an associate Contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall reside with the parties to the agreement, and not the Government.

All costs associated with the agreements are included within the individual Orders for which they apply to. Agreements may be amended as required by the Government during the performance of this contract.

5.0 Order Execution

5.1. Program Management

The Contractor shall provide for planning, coordination, organization and execution of all program management tasks to include, but are not limited to, development, documentation, reporting of all Program Management processes, products, and artifacts;

financial and contract performance documentation and reporting; configuration management and data management, including risks and issues management; cost and schedule tracking and reporting; subcontract management and reporting; product support planning; as defined in individual Orders. When applicable, costs will be collected in the following areas: Non-Recurring Engineering (NRE), material, integration, affordability, test and demonstration and will be defined in FOPRs.

5.2. Systems Engineering

The Contractor shall perform disciplined technical planning, coordination and execution of systems engineering as defined in FOPRs.

5.3. Security

5.3.1. Post-award deliverable

• The Contractor may submit deliverable as stated in paragraph 7.0 SOW at classification levels ranging from CUI to TS//SCI//SAR.

• The Contractor shall notify the Procuring Contracting Officer (PCO) within 5 working days following award if submitting a classified deliverable.

• The Contractor shall submit a DD254, Contract Security Classification Specification, to authorized individuals in AFLCMC/XA using the template provided in the solicitation. Points of contact will be provided by the PCO at time of notification.

• The Contractor shall comply with the security requirements specified in the Contractor’s DD Form 254 and direction from the AFLCMC/XA security office.

5.3.2. FOPR Requirements

As defined in FOPRs, the Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and/or CUI and classified items.

To ensure Information Security/Technology Control, the Contractor shall provide protection for classified information up to the TS//SAR//SCI level, as defined by individual Orders.

If the Contractor does not have the appropriate Facility Clearance Level in order to meet personnel security requirements, the Government Contracting Authority may sponsor the Contractor upon award, as defined in FOPRs. Once sponsorship is submitted to Defense Counterintelligence Security Agency (DCSA) the Contractor will have 3 months upon award to be in compliance with Facility Clearance Requirements. Any efforts subcontracted for the order will be held to the same standard, but the prime Contractor will act as a sponsoring authority.

5.3.3. Controlled Unclassified Information (CUI)

CUI is unclassified information requiring safeguarding and dissemination controls, consistent with applicable law, regulation, or government-wide policy.

CUI replaces the For Official Use Only (FOUO) marking. The Contractor shall identify CUI and apply proper marking, identify decontrol requirements, describe safeguarding requirements, identify proper destruction methods, apply appropriate access and dissemination controls, explain procedures for identifying and reporting security incidents and state implementations guidelines for CUI.

(See Table 1 – References 1,2,3)

5.4. Operations Security (OPSEC)

Because USG activities, projects, and programs present high potential for adversaries to target and collect program data, properly applied Operations Security (OPSEC) measures must be taken into account to protect sensitive unclassified information. The Contractor shall not confirm, deny or forward classified information that appears in the media via unclassified channels.

5.4.1. Public Release of Information Request

The Contractor shall ensure that information has been approved for public release:

• The Contractor shall submit public release approval requests using a

Department of Defense (DD) Form 1910, Clearance Request for Public Release of Department of Defense Information

• The Contractor shall submit public release requests to AFLCMC/XA, 45 days prior to requested release date.

• The Contractor shall ensure prior to release that the AFLCMC/XA Director, Public Affairs Officer, and Security have approved their submitted DD Form 1910.

5.5. Product Support

As defined in FOPRs, the Contractor shall ensure that all product support tasks and deliverables remain synchronized with technical design maturity as the effort matures to ensure a comprehensive product support strategy is established early in development planning for the life cycle. (See Table 1 – Reference 4)

5.6. Exclusivity Agreements

The Contractor shall not require other Contractors or entities to sign an exclusivity agreement that could prevent further activity within the AFLCMC/XA portfolio.

6.0 Studies, Analyses and Demonstrations

Special studies, analyses, and demonstrations shall be performed as defined in FOPRs.

7.0 Post-Award Deliverable

At the time of award, successful offerors shall develop and deliver a post-award presentation within 15 days of the effective contract date. If applicable, the Contractor shall follow security procedures as outlined in paragraph 5.3.1 of this SOW prior to submission.

CDRL A001, DI-MGMT-81605/T, Briefing Materials.

Table 1 – Referenced Documents

Reference

ID

Document Date

1 Department of Defense Instruction 5200.48, Controlled Unclassified Information

6 March 2020

2 Executive Order (E.O.) 13556 4 November 2010

3 Code of Federal Regulations (CFR) Title 32, Part 2002 – Controlled Unclassified Information

14 September 2016

4 Department of Defense Product Support Management Guide Book

23 December 2019