CAF DMO 3.0_Task Order 1_Transition.docx

Initial Task Order - PWS Solicitation #: FA8621-24-R-B006

Combat Air Forces’ Distributed Mission Operations

(CAF DMO)

Transition Services Performance Work Statement (PWS)

ID/IQ: TBD, Solicitation # FA8621-24-R-B006 Task Order Number: TBD Version 1.0 Date: 18 October 2023

Prepared For:

Department of the Air Force Air Force Life Cycle Management Center AFLCMC/WNS Wright-Patterson AFB Dayton, OH 45433

DISTRIBUTION STATEMENT D:

Distribution authorized to Department of Defense and U.S. DoD contractors only; CRITICAL TECHNOLOGY; 28 April 2020. Other requests for this document shall be referenced to AFLCMC/WNS.

1.0 CAF DMO Scope

The CAF DMO scope is to provide distributed training capability to all current contractor sites and operational training sites by the end of the established transition period, as well as add distributed training capability to new sites as directed by the United States Air Force (USAF) and in accordance with (IAW) the PWS and Contract. As part of the CAF DMO Program, the contractor shall deliver its plan for transitioning distributed training service from the existing service to their service solution.

2.0 Transition Planning Services

The contractor shall produce and maintain a transition plan which details the transition services and networking services for the federate sites. The initial plan shall include all sites listed in Annex A to the IDIQ PWS. The contractor shall work with the Government to identify changes to the federate sites and continue to update the transition plan as necessary. The transition plan shall identify downtime to the network, not to exceed five calendar days per site. The plan shall provide flexibility to accommodate current training priorities. The initial transition plan shall provide for transition of sites listed in Annex A not later than Full Network Service Start Date, 24 months after contract award. Transition shall be considered complete once all federated sites and the entire Distributed Training Center (DTC) at Langley have been transitioned. The transition criteria shall also include an approved and functioning Cross Domain or Multi level Security (MLS) solution as specified in CAF DMO Contract PWS section 4.8. Transition will be complete when all sites are capable of training with all other sites, across multiple security levels, required Authorization to Operate (ATO)s, Authority to Connect, and the CAF DMO DTC is manned to support training events. The plan shall be integrated into the contractor’s Integrated Master Schedule (IMS) and Integrated Master Plan (IMP). The first 12 months of the transition period will be issued as the first task order on CAF DMO 3.0.

CDRL A005 - (DI-MGMT-81861C) Integrated Program Management Data and Analysis Report (IPMDAR) CDRL A009 - (DI-MISC-80508B/T) Transition Plan

3.0 Transition and Expansion Services

3.1 Initial Transition Services

The contractor shall provide the preparatory services necessary to architect and maintain the network. The preparatory services shall include all engineering services and security services necessary to design and establish the CAF DMO operation center(s) infrastructure which has the ability to support the federate sites listed in Annex A. The contractor shall procure, deliver, set up, and functionally check the CAF DMO gateway and network connection for the first federate service (service at the federate site). This first federate service shall be considered complete when the CAF DMO Network operations center(s) and the federate receive an ATO to operate on the network. The transition period will be issued as the first task order on CAF DMO 3.0. The architecture shall be scalable to allow for future sites.

The network service shall be capable of supporting the 7 security domains:

1. CORAL Secret (S)/SAP Cross Domain Solutions (CDS)

2. CORAL S/SAP PL2 only

3. PIANO S/SAP CDS

4. PIANO S/SAP PL2 only

5. SECRET // COLLATERAL NOFORN

6. SECRET // REL ACGU

7. SECRET // REL (UK or AU or CA BI-LAT) x3 It is desired for the network service to be capable of expanding to support no less than 14 (including the above) security domains:

1. Top Secret (TS) / Special Compartmentalized Information (SCI) / Special Access Program (SAP)

2. Top Secret (TS)/Special Access Program (SAP)

3. RED (SECRET COLLATERAL) NOFORN

4. RED FVEY CDS

5. RED Coalition CDS

6. RED AUS (bi-lat) CDS

7. RED UK (bi-lat) CDS

8. RED CA (bi-lat) CDS

9. S / Joint Simulators Environment (JSE)-Terms of Reference (TOR) PL2 only

10. TS / JSE TOR PL2 only

11. TS / SCI / JSE TOR PL2 only

3.2 Networking Standup / Networking Services

3.2.1 Networking Standup

The contractor shall stand up the new DMO Network IAW the 1-N priority list.

3.2.2 Architecture and Network Gateway

The contractor shall be responsible for the overall design, implementation, and sustainment of the CAF DMO network. The contractor shall implement the network IAW applicable CAF DMO O&I Standards (as referenced in CAF DMO Contract PWS section 2.1.5). The contractor shall be responsible for installation of equipment including site coordination and set up of equipment. The contractor shall ensure site downtime does not exceed five calendar days including equipment install, integration and functional checks.

The contractor shall provide a service utilizing an architecture that supports real-time training. The contractor shall procure, install, set up, and functionally check network gateways, including all hardware and software necessary to provide networked service to and from each site ordered. The contractor shall complete successful functional checks for each gateway. Each gateway shall have the capability to route and filter (including the ability to configure, modify and/or remove data) Distributed Interactive Simulation (DIS) data to resolve interoperability issues between diverse simulators. The gateway filter capabilities shall be dynamic in nature and configurable before and during event execution (i.e., run-time configurable). The gateway filter capabilities shall be sufficient to implement the DMO Filtering Plan. The contractor shall be responsible for maintaining the DMO Filtering Plan through the life of the contract.

The gateway shall translate between protocols for DIS, High Level Architecture (HLA), Data Distribution Service (DDS), Test and Training Enabling Architecture (TENA), and Global Reusable Interface Domain (GRID) protocol used by simulators at training sites and a common protocol on the DMO network, thereby allowing DIS, HLA, DDS, TENA and GRID sites to interact in common training events. Transmission Control Protocol/Internet Protocol (TCP/IP) protocols as identified in the CAF DMO Network Standard shall also be routed through the gateway.

Gateways shall have the capability to periods process IAW the JSIG and DoDM 5205.07 series documents, listed in para 2.1.5. In order to encrypt data, the gateway shall include National Security Agency (NSA)-approved cryptographic equipment. Cryptographic equipment shall be procured and delivered by the contractor, and keys shall be provided and managed by the contractor IAW NSA doctrine, JSIG, and DoDM 5205.07 series documents. The security documentation shall include the gateways within the security boundary of the CAF DMO network.

CDRL A012 - (DI-MISC-80508B/T) Technical Report - Study/Services (Rule Sets/Rule Set Character)

3.2.3 Availability and Latency

The contractor shall provide and maintain a network infrastructure that performs with Training Event Availability and Systems Availability rates at or above 97% and 99% respectively as calculated IAW the availability clause Section H101.

The network service shall utilize an architecture that supports real-time training. Latency/Quality of service shall not exceed a threshold of 65ms with an objective of 10ms, in compliance with IEEE 1278.2 within a theater (i.e., USAFE, PACAF, CONUS). Latency shall be calculated as the delay of single, maximum sized, CAF DMO Protocol Data Unit (PDU) from the local area network at one training site to the local area network at any another training site that is connected to the CAF DMO network, within a theater. Latency calculation shall include the delay through the gateways and a CDS/Multi-Level Solutions (MLS) guard. This does not include additional delays internal to federate systems and their own local area networks at each site.

Latency shall include delays from long haul circuits. Latency shall be measured for each active network route at least on a monthly basis and reported to the Government. Latency issues shall be reported upon identification, and a corrective action plan submitted within 48 hours.

CDRL A011 - (DI-MISC-80508B/T) Technical Report - Study/Services (Availability/Latency)

3.2.4 Network Services

The contractor shall provide network services to and from each of the federate systems for networked events. The contractor shall provide a network that allows simultaneous events numbering not less than 25% (rounded up) of the total number of operational training sites. For instance, 100 sites on the network would require a minimum of 25 simultaneous events. Any single event shall be capable of providing service to any number of operational training sites in single domain or any number of operational training sites in a multi-domain event. Any single event shall be capable of processing a connection of any approved domain on the network. It is understood that a cross-domain event with multiple high-side domains connected to a common low domain will consume multiple events. The simultaneous events shall be capable of supporting the same or disparate training requirements. The network shall be capable of supplying scheduled network services for simultaneous DMO events that may be operating at different system-high security levels and in which participating federates may be operating in different geographic areas. The contractor shall ensure network and network traffic meets all JSIG requirements and are accredited by the Authorizing Official (AO).

3.2.4.1 Circuit / Network Management

The contractor shall manage the ordering of the circuits and/or network. The contractor shall monitor network connections and coordinate directly with the service providers for resolution of all outages.

3.2.4.2 Contractor Provided Circuits / Network

The contractor shall provide circuits and network which meet requirements in the CAF DMO PWS. The contractor shall support the Government's request for information to obtain a Defense Information Systems Agency (DISA) waiver.

4.0 Interoperability Services

4.1 Integration and Testing

The contractor shall provide the services necessary to ensure integration of federates into federations necessary to meet the training objectives of DMO events. The contractor shall manage the integration test schedule and test events. The contractor shall post the schedule weekly to the website referenced in CAF DMO contract PWS section 4.12.4. The schedule shall show a 3-month projection. The contractor shall support the Test Planning Working Group (TPWG) for CAF DMO.

The contractor shall provide support, analysis, and testing to integrate sites on this task order. The contractor shall host a testbed with representative products that generate constructive entities on CAF DMO and test products for interoperability. The contractor shall provide detailed reports of interoperability and standards-compliance issues identified via the website.

CDRL A039 – (DI-MISC-80508B/T) Technical Report Study/Services Sub-Title Interoperability and Standards The contractor shall provide the services necessary to identify, assign, and track to resolution any training limitations and non-adherence to the CAF DMO standards as referenced in CAF DMO contract PWS section 2.1.5. The contractor shall produce a database of training limitations and deviations from standards. The database shall be kept current and be accessible to the Government and federates through a web-based user interface. The contractor shall support the System Problem Report Working Group (SPRWG) for CAF DMO. The SPRWG is the working forum, lead jointly by the contractor and the USAF and composed of the Federate Systems stakeholders currently members of the Distributed Mission Operations Network (DMON), responsible for documenting and managing SPRs. For the purpose of this Task Order, the CAF DMO 2.0 contractor and Government will lead the SPRWG.