Draft CAF DMO 3.0 IQID PWS.docx

DRAFT

Combat Air Forces’ Distributed Mission Operations

(CAF DMO)

Performance Work Statement (PWS)

RFP NO: DRAFT

Prepared For:

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

Page ii

GENERAL INFORMATION

This is a non-personal services contract to provide Distributed Mission Operations services. The contractor may be referred to as a DMO Operation and Integration (O&I) contractor in order to reduce changes to other existing government contracts.

Program Overview The Combat Air Force (CAF) DMO services shall provide distributed training to capable Air Force trainers worldwide, by establishing a virtual environment to conduct distributed training events, from daily team training to large scale exercises that provides a safe, realistic training environment at a lower cost than live fly. To support this distributed training environment, the CAF DMO Program shall establish interoperability standards, which documents common formats for dissimilar trainers to exchange data for effective training.

The CAF DMO Program shall also provide a security solution that allows trainers of different security levels to train together. The CAF DMO Program supports the Distributed Mission Operations Center at Kirtland AFB, NM with on-site support as well as the Air Combat Command (ACC) Distributed Training Center (DTC) at Langley AFB, VA and the Virtual Test and Training Center (VTTC) at Nellis AFB, NV.

CAF DMO Objective The overall objective of the DMO Program is to provide the CAF a persistent virtual training environment to increase operational effectiveness by integrating DMO as a component of readiness training.

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.

Contractor Personnel The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training and experience.

The Procuring Contracting Officer (PCO) or base commander may restrict employment of any contract employee, or prospective contract employee, at a government installation, who is identified as a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its populace. Contract managers and supervisors are included in the definition of employees. All contract employees must be able to read, write, speak, and understand the English language.

Contract personnel, IAW DFARS 211.06, shall identify themselves as contractor personnel by introducing themselves or being introduced as such and displaying distinguishing badges for meetings with Government personnel. Contractor personnel shall identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

The contractor shall not employ any person who is an employee of the Unites States Government if the employment of that person would create a conflict of interest, nor shall the contractor employ any person who is an employee of the Department of Defense (DoD) or any subordinate branch of the DoD, either military or civilian, unless such person seeks and receives approval IAW the Joint Ethics Regulation, DoDD 5500.07R, and any applicable regulations of their subordinate branch of the DoD

Location and Hours of Work Accomplishment of tasks required by this contract requires work IAW 4.4.4

Voluntary Protection Program The contractor shall produce a Safety and Health Plan and generic site safety checklist (customizable for all sites). The contractor’s plan shall include appropriate measures to ensure the contractor reacts promptly to investigate, correct, and track alleged safety and health violations and/or uncontrolled hazards in contractor work areas. Installation-specific references and policies may be included (or attached) to the plan. See Section H Special Contract Requirement.

The contractor shall comply with the specific health and safety requirements identified in this PWS, as well as the Occupational Safety Health Act (Public Law 91-596). The contractor shall comply with the health and safety rules of the Government installation that concern related activities not directly addressed in this PWS.

The contractor shall take reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way coming in contact with the performance of this requirement. The contractor shall take additional immediate precautions identified by the PCO for health and safety purposes.

APPLICABLE DOCUMENTS

Government Documents The following standards, specifications, and handbooks form a part of the PWS to the extent specified herein.

DoD Handbooks and Manuals and Directives MIL-STD-882D Environment, Safety, and Occupational Health (ESOH) DoDD 2040.2 International Transfer of Technology, Goods, Services, and Munitions DoDD 5200.1-PH DoD Guide to Marking Classified Documents DoDD 5230.24 Distribution Statements on Technical Documents DoDD 5230.25 Withholding Unclassified Technical Data from Public Release DoDD 5200.39 Critical Program Information (CPI) Protection Within the Department of Defense DoDD 8500.1 Information Assurance DoDD 8500.2 Information Assurance (IA) Implementation DoD Manual 5200.1 The Acquisition Systems Protection Program 32 Code of Federal Regulations, Part 117, National Industrial Security Program Operating Manual (NISPOM), 24 February 2021 DoDD 5500.07R Joint Ethics Regulation DoD 4161.2M DoD Manual for the Performance of Contract Property Administration Intelligence Community Directive (ICD) 503, IC Information Technology Systems Security Risk Management, Certification and Accreditation DoDM 5205.07 SAP Security Manual, Volume 1 (V1) General Procedures DODM 5205.07 SAP Security Manual, Volume 2 (V2) SAP Access Determination Process DoDM 5205.07 SAP Security Manual, Volume 3 (V3) Physical Security Guidance for Special Access Program Facilities (SAPFs) DoDM 5205.07 SAP Security Manual, Volume 4 (V4) Classification and Marking Guidance

U.S. Air Force Standards and Instructions AFI 33-200 Information Assurance Management

Industry Standards SISO-REF 010 Enumerations for Simulation Interoperability SISO-REF 010.1 Operations Manual for the Distributed Interactive Simulation Product Support Group (DIS PSG) Enumerations Working Group (EWG) IEEE STD1278 IEEE Standard for Distributed Interactive Simulation Series IEEE STD 1516 series High Level Architecture (HLA)

Joint Manuals Joint SAP (Special Access Program) Implementation Guide (JSIG)

US Government Publications, Instructions, and Guides NIST SP 800-53, Recommended Security Controls for Federal Information Systems and Organizations NIST SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, Building Effective Security Assessment Plans NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View NIST SP 800-30, Guide for Conducting Risk Assessments CNSSI 1253, Security Categorization and Control Selection for National Security Systems UCDMO CDS Overlay UCDMO CDS Security Assessment Guide CAF DMO Standards MP23/4 CAF DMO CORAL 1.2 / PIANO 1.0 / FVEY 1.0 Rulesets CAF DMO Filtering Plan GFM-A Contractor Inventory Control Point (C-ICP) Implementation Guide NCDSMO CDS Overlay NCDSMO CDS Security Assessment guide

Simulator Common Architecture, Requirements, and Standards (SCARS) Simulator Common Architecture Requirements and Standards (SCARS) Engineering Capabilities Board (SECB) Charter, 2 February 2021 Standards Maintenance Plan (SMP) for Simulator Common Architecture Requirements and Standards (SCARS), 2 February 2021 SCARS Standards

Order of Precedence In case of a conflict between this document and the references cited herein, this document shall take precedence. Nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained.

PROPERTY AND SERVICES

Government Furnished Property (GFP) Inventory and Control The GFP list may be found in attachment X. The Contractor shall inventory, track, control and manage all GFP IAW Federal Acquisition Regulation (FAR) 52.245-01 and DoD 4161.2M. The contractor shall notify and receive authority from the PCO before modifying any GFP. A task order is considered that authority.

Government Property Damage Prevention Contractor personnel shall prevent loss, damage, destruction, or theft to Government property while performing the services under this contract. The contractor shall report within two business days, to the Administrative Contracting Officer (ACO)/ Contracting Officer Representative (COR), who in-turn will provide all pertinent facts relating to each instance of damage to Government property to the PCO. The Contractor, as directed by the ACO/COR, shall immediately secure the damaged equipment until directed to release it by the investigating authority, through the PCO. If the Government elects to conduct an investigation of the incident, the Contractor shall cooperate fully and assist Government personnel until completion of the investigation.

Contractor Furnished Property and Services Except for those items specifically stated to be government furnished in attachment X, the contractor shall furnish all materials, facilities, equipment and personnel required to perform this PWS. The contractor shall acquire and maintain a TOP SECRET facility clearance level (FCL) from the Defense Counterintelligence and Security Agency (DCSA). Where applicable, the Contractor’s employees performing work in support of this contract shall have been granted and maintain a SECRET security clearance from the Defense Industrial Security Clearance Office.

Supply Support The contractor shall perform supply support activities and document in the Logistics Plan an approach to identification, development, and procurement of common and peculiar equipment support and handling equipment in a cost-effective manner. Supply support activities could include cataloging, monitoring, collecting, storing, maintaining, repairing, distributing, reporting, transferring, and disposing of equipment and mission specific.

The contractor shall deliver a Training Device Inventory Checklist/Record. The contractor shall also provide data in response to cataloging and equipment valuation requests from the Simulators Division Equipment and Logistics Managers. The Training Device Inventory Checklist/Record provides the means for organic reporting of GFE in the Air Force Equipment Management System.

CDRL A0XX DI-MISC-81191 Training Device Inventory Checklist/Record (ICL/R)

Government Furnished Material (GFM) The contractor shall meet all Government Furnish Material – Accounting (GFM-A) Information Technology (IT), process, procedure, and start-up requirements as directed in the GFM-A Contractor Inventory Control Point (C-ICP) Implementation Guide. Accountability (GFM-A) in the Accountable Property System of Record (ASPR). The contractor shall maintain a current connection agreement (Interface Control Agreement), and security documentation (System Authorization Access Request – DD Form 2875) with Defense Automatic Addressing System (DAAS) Transaction Services.

The contractor shall conduct GFM-A transaction reporting either by interfacing current inventory control system transactions or by conducting manual transactions as a self-service module user in the GFM-A ASPR. Upon election of the interface option, the contractor shall meet the frequency and minimum version of the Defense Logistics Management Standards (DLMS) transaction. The contractor shall establish a GFM-A “Go-Live” date upon contract award.

Financial Improvement Audit Readiness (FIAR) The contractor shall provide property accountability/control of contractor managed and possessed GFP through implementation of integrated logistics and contractor processes (from acceptance and receipt to disposition) IAW DoDM 4140.01, V6, DoDI 5000.64, and Financial Improvement Audit Readiness/Remediation (FIAR) guidance. The contractor shall provide property related reports through GFM-A electronic or Chief Financial Officer (CFO) reporting methods listed in the paragraphs below. As independently assessable elements under FIAR, the contractor shall audit, track, maintain, update, report, and reconcile GFP (GFE and GFM) transactions in the Air Force designated Accountable Property System of Record (APSR), see paragraphs below for type-requirements.

FIAR GFP Reporting

DFARS PGI 245.103-72 “GFP attachments to solicitations and awards” establishes requirements for documenting in contract attachments the property to be provided as GFP or authorized as GFP in performance of a contract. As a result, the contractor shall report GFP status quarterly to ensure TS mission critical assets are accurately recorded in the AF property and logistics systems under FIAR guidance.

See http://dodprocurementtoolbox.com for style, format, and step-by-step tutorials on completing the Consolidated GFP Attachment Version 2.0. As the acting SCM and Inventory Control Point (ICP) for the training system, the contractor shall submit authorizations to attain Contractor-ICP (C-ICP) designation and supply coding requisite to conducting FIAR reporting transactions.

CDRL AXXX - DI-MGMT-81947B/T, Government Furnished Property Inventory and Forecasting Report

The Contractor shall clearly identify, track and report GFP managed and possessed by the Contractor quarterly to enable a complete, current, and auditable financial record of all transactions regarding GFP accountable to the contract IAW DoD FMR 7000.14, Financial Management Regulation with the Chief Financial Officer (CFO) Report. The Contractor shall have a process to create and provide property-related reports as directed by the Government Contracting Officer.

CDRL AXXX - DI-MGMT-80259/T, Physical Inventories Report

FIAR GFE REPORTING

The Contractor shall report GFE status annually to ensure TS mission critical assets are accurately recorded in the AF property and logistics systems’ under FIAR. The Government Property Inventory report provides the information required for Government reporting of CAF DMO GFE in the Defense Property Accountability System (DPAS). The Contractor shall also support equipment valuation requests from the Simulators Program Office.

CDRL AXXX - DI-MGMT-80441D, Government Property Inventory

FIAR GFM-A Reporting

The contractor shall report Government Furnished Material. The contractor shall implement an interface control agreement to allow direct communication into the government APSR in order to track and report GFP. With the government interface requirements, the contractor shall meet all GFM-A Information Technology (IT), process, procedure, and start-up requirements as directed in the GFM-A C-ICP Implementation Guide. The contractor shall maintain a current connection agreement (Interface Control Agreement), and security documentation (System Authorization Access Request - DD Form 2875) with Defense Automatic Addressing System (DAAS) Transaction Services. With the government self-service option, the contractor shall submit detailed information for all government property in the format determined by the AF. As the acting Supply Chain Manager (SCM) and Inventory Control Point (ICP) for the training system, the PMO shall submit authorizations to attain contractor (C-ICP) designation and supply coding requisite to conducting GFM-A transactions.

The contractor shall conduct GFM-A transaction reporting either by interfacing current inventory control system transactions’ or by conducting manual transactions as a self-service module user in the GFM-A APSR, as directed by the government. Upon implementation of the interface requirements, the contractor shall meet the frequency and minimum version of the DLMS transactions as listed in Section 1 and Appendix E of the C-ICP Implementation Guide. Under the self-service module option, the contractor shall enter GFM-A logistic events into the APSR as quickly as possible on the day that they occur, but before end of day processing is run. The contractor shall establish a GFM-A “Go-Live” date upon contract award and brief status of GFM-A reporting at the contract post-award conference.

Contractor Inventory Control Points (C-ICP)

The contractor shall manage all property procured by a contractor as Government Furnished Property (GFP), which is identified within the contract. The means for which the C-ICP will manage the GFP will include but is not limited to: Inventory Management, Asset Management, Maintenance Activities, Supplier Management, Packaging, Handling, Storage and Transportation, and Configuration Management. The C-ICP is also responsible for requisition processing, shipping, receiving, in-transit visibility/tracking/reporting, property accountability and handling of classified material. The Contractor shall establish and maintain a contractor Inventory Management System (IMS) to provide asset visibility and inventory status reporting.

The Contractor’s Inventory Management System is required to contain records for the program’s parts that provide comprehensive logistics, procurement, and technical data required to accomplish supply support analysis, parts ordering, property accountability, and funds control.

The Contractor shall ensure these part records are structured in the inventory management system to maintain part configuration control, approved part substitution and interchangeability identification, serialized item control, notice of special handling requirements, and record item consumption data. IAW AFI 23-101

The Contractor shall ensure accurate pricing of property IAW DOD and Air Force policy directives with supported documentation. Documents supporting accountability and/or financial information will be maintained for 10 years IAW DoD 7000.14-R vol. 1 Chapter 9.

The Contractor’s C-ICP shall determine, procure, repair, service, store, receive and dispose of unique spare parts and support equipment. The Contractor shall have the capability to handle and store classified property and comply with the requirements of DD Form 254, if required. Disposal of classified/unclassified consumable/repairable components will be IAW with the assigned demilitarization code. DEMIL Codes may be found in DoD Manual 4160.28, Vol 2.; https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/416028p.pdf

The Contractor shall disposition C-ICP managed property through Scrap or Disposal when the government determines it is not beneficially repairable, excess, or obsolete. Considerations, such as lead time for new procurement, out of production items, mission requirements and Operations Tempo, must be considered prior to determining that an asset is beyond economical repair.

Following disposition, the C-ICP shall remove components from Contractor accountability by reducing the inventory balance in the Inventory Management System and physically scrapping in-place at a Source of Repair (SOR) or issuing disposed of property at the Main Operating Base (MOB) to the Air Force for processing. The Contractor shall maintain a record of disposition actions and report IAW reporting instructions.(IAW DoDI 5000.64)

The Contractor shall gain and maintain access to CSWS Data Exchange (CSWS DE)/D375. CSWS DE is the bridge between CLS activities and Air Force legacy systems that do not allow commercial access. It is the single automated source to provide mission essential packaging, shipping, and transportation data to Air Force systems. Access to CSWS DE is available through the AF Portal and requires a valid CAC/PKI, DD 2875, sponsor letter and non-disclosure statement. Forms are available through the application owner identified on the AF Portal.

The Contractor shall enter required data as identified in the CSWS DE Student Training Course Guide and the CSWS DE Checklists on the Training & Documentation page within D375. This includes, but is not limited to, basic management data, asset data, item management and equipment specialist data, packaging and transportation data, logistics reassignment data, and spares computation data.

PROGRAM INVENTORIES AND AUDITS

The Contractor shall perform an inventory of all CAF DMO assets at contract award (ramp-up transition), annually over the contract period, contract completion (ramp-down transition) and within 30 days of CO direction. The Contractor shall also audit all GFP prior to “Go-Live” date for FIAR transaction reporting. The government reserves the right to oversee this audit. Random sampling during the inventory may only be considered for non-recompetition support package spares. All other assets shall be a 100% inventory.

The Contractor shall support a Government audit to ascertain that a complete set of documentation and software packages exists, with the latest revisions incorporated. The software audit shall include a complete audit of all software licenses. All software shall be licensed to the Government, or the Contractor shall facilitate the transfer of the license to the successor Contractor. This set of documentation and software packages shall be suitable for procurement purposes.

The Contractor shall conduct an inventory audit of all GFP assets with Government oversight during the transition period and annually. The Government reserves the right to monitor the audit. This audit will be performed to ascertain the existence and condition/serviceability of these items. The government will perform an annual audit of all government-owned program assets. The Contractor shall be given timely, but NLT 30 calendar days’ notice of all audits prior to beginning the audit and support Government participation in the audit when requested at no additional cost.

The Contractor shall deliver to the successor contractor an initial inventory of all the CAF DMO assets with the final inventory that is to be delivered, as agreed by the Transition IPT. The Contractor shall provide a summary of audit results, correct any materiel deficiencies, and update the inventory control system. The Contractor shall support any review/audit of all CAF DMO assets and/or inventory control system at no additional cost. The Contractor shall jointly reconcile all inventory items and anomalies with the Government and successor contractor.

CDRL AXXX - DI-MGMT-80441D, Government Property Inventory

Consumables

The Contractor shall provide all consumable items as part of each annual CLS CLIN. These assets will not be tracked as part of the RSP; however, the Contractor shall maintain separate inventory records on these items. Records shall be made available to the Government upon request.

INVENTORY CONTROL

With the interface control requirements, the Contractor shall procure, implement and maintain an inventory control system, compliant with Defense Logistics Management Standards, to track the status of all CAF DMO assets. The Government shall approve the inventory control system before use and the inventory data will be maintained 100% accurate by the close of the business day. The new inventory control system shall be in place at the end of the Initial Contract Transition. Asset tracking shall comply with FAR 52.245-1 and DFARS 252.211-7007. The Contractor shall support creation and implementation of new reports and/or formats, as directed by the Government.

CDRL AXXX- DI- DI-MGMT-81947B/T, Government Furnished Property Inventory and Forecasting Report

MATERIAL INSPECTION AND RECEIVING REPORT (DD250)

At the time of each delivery of supplies or services under this contract, the Contractor shall prepare and furnish to the Government a Material Inspection and Receiving Report in the manner and to the extent required by DFARS 252.246-7000, 252.232-7006. The Contractor shall ensure two copies of the receiving report (DD250) paper copies or the Wide Area Workflow (WAWF) electronic report shall be distributed with the shipment.

ITEM UNIQUE IDENTIFICATION (IUID)

The Contractor shall follow the applicable IUID requirements in Section I, DFARS Clauses 252.211-7003 and 252.211-7007 and MIL-STD-130N.

The Contractor shall ensure cost data is accurate and that it is entered for all GFP items and shall determine which GFP items fall under the requirements of DFARS Clause 252.211-7007 and Simulators Program Office IUID Implementation Guide (Attachment 7). For items that require a virtual Unique Item Identifier (UII), the Contractor shall mark them with a UII. The Contractor shall submit an IUID marking plan 90 days after contract award and individual Marking Activity Verification Reports upon device modification and/or upon completion of the annual GFP audits.

As specified in DFARS Clause 252.211-7003, paragraph (c)(1)(iii), the Contractor shall list, for delivered items, only those embedded items that have a UII due to the item's delivered spare having a UII. The Contractor shall use Automated Identification Technology for unique identification of items. The Contractor shall have necessary equipment required to read the IUID labels on applicable equipment.

The Contractor shall follow the applicable IUID requirements in Section I, DFARS Clauses 252.211-7003 and 252.211-7007 and MIL-STD-130N as specified in individual task orders.

The Contractor shall label new equipment and maintain all IUID tags on all CAF DMO equipment IAW the policies as stated above. The Contractor shall report the items that are IUID compliant within the annual inventory. The Contractor shall comply with all marking requirements within 90 days after receipt of property. The Contractor shall use and update the IUID National Registry for all applicable Government property.

The Contractor shall determine which GFP items fall under the requirements of DFARS Clause 252.211-7007. For items that require a virtual Unique Item Identifier (UII), the Contractor shall mark them with a UII. Embedded items will not require a UII until they are removed.

As specified in DFARS Clause 252.211-7003, paragraph (c)(1)(iii), the Contractor shall list, for delivered items, only those embedded items that have a UII due to the item's delivered spare having a UII. This includes, but is not limited to, delivered end items, assemblies, subassemblies, components and spares purchased as end items.

In addition, this includes legacy items in inventory or use. Any embedded item that is originally unlabeled, but its delivered spare is labeled, shall be labeled through the maintenance cycle.

The Contractor shall use automated identification technology for unique identification of items. The Contractor shall use virtual UII in accordance with DoD Guidelines for the UII Version 1.2 dated Nov 2006. The Contractor shall enter the IUID data for all marked components into the WAWF database.

CDRL AXXX, DI-MGMT-81803/T, IUID Marking Plan

CDRL AXXX, DI-MGMT-81804A, Unique Identification (IUID) Marking Activity & Verification Report

General Equipment Valuation (GEV)

The contractor shall perform, update, and report GEV on Government furnished special tooling, special test equipment, and all General Equipment owned by the Government, especially assets exceeding the appropriate capitalization threshold ($1M for Air Force general fund assets). The contractor shall accomplish GEV in accordance with Generally Accepted Accounting Principles (GAAP) prescribed in the Statement of Federal Financial Accounting Standards Number 6 (SFFAS No. 6) or SFFAS No. 35 where applicable. The contractor may only use the “Deemed Cost” methodology identified in OUSD/AT&L Memo for Strategy and Implementation Guidance for General Equipment Valuation to establish the CAF DMO opening balance statement of financial assertion. The contract shall report GEV periodic adjustments for existing property in accordance with contract GFP (GFE and GFM) reporting methods. The contractor shall report GEV adjustments resulting from contract modifications, modernizations, upgrades, improvements, and new procurements at government acceptance using the Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) system per contract DD250 requirements.

CDRL AXXX, CDRL AXXX- DI-MGMT-81947B/T, Government Furnished Property Inventory and Forecasting Report

CDRL AXXX, DI-MGMT-80441D, Government Property Inventory

SPECIFIC SERVICES & TASKS

The contractor shall provide the technical expertise, security expertise, and management expertise to execute the CAF DMO program and accomplish USAF directed training objectives for CAF DMO federates.

Federate Site Survey The contractor shall perform a site survey for each federate site, as directed by the Government via task order. The contractor shall collaborate and coordinate with the federate system provider and/or from the base support personnel in determining the method of implementation for network services required to connect the federate system to the CAF DMO network, including any network gateway. The contractor shall produce a site survey report for each federate site.

CDRL A009 (DI-MISC- 80508B) Technical Report – Site Survey Report

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 Appendix A. 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. The plan shall provide flexibility to accommodate current training priorities. The initial transition plan shall provide for transition of sites listed in Appendix 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 PWS section 4.8. Transition will be complete when all sites are capable of training with all other sites, across multiple security levels, required ATO/ATCs, and the CAF DMO DTC is manned to support training events. (DI-MISC-80508B) Site Standup & Transition Plan The plan shall be integrated into the contractors Integrated Master Schedule (IMS).

CDRL A004 (DI-MGMT-81650/T) Integrated Master Schedule

Transition and Expansion Services

1.1.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 Authority to Operate (ATO) to operate on the network. The architecture shall be scalable to allow for future sites. The network service shall be capable of supporting no less than 13 security domains to include the list below:

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

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

3. CORAL S/SAP PL2 only

4. PIANO S/SAP CDS

5. PIANO S/SAP PL2 only

6. RED

7. RED FVEY CDS

8. RED Coalition CDS

9. RED AUS (bi-lat) CDS

10. RED UK (bi-lat) CDS

11. RED CA (bi-lat) CDS

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

13. TS / JSE TOR PL2 only

1.1.2 Network Expansion Services

The contractor shall provide the preparatory services necessary to expand the design and infrastructure of the CAF DMO network as directed by the government via task order.

Networking Standup / Networking Services

1.1.3 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 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 such as H.323, H.264, G.722.1, XMPP, HTTP, and HTTPS 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 A009 (DI-MISC-80508B) Technical Report - Study/Services (Rule Sets/Rule Set Charters/Standards/Security)

1.1.4 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 A008 (DI-MISC-80508B) Technical Report - Study/Services (Availability/Latency)

1.1.5 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, and 120 sites would require the network to support a minimum of 30 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).

1.1.5.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.

If the government decides to transition part(s) of the network from contractor provided circuits and network to government provided circuits and network (Defense Information Systems Agency (DISA)), the contractor shall manage the ordering of the government network and circuits. The contractor shall monitor all network connections and coordinate directly with the government service providers for resolution of all outages.

1.1.5.2 Contractor Provided Circuits / Network

The contractor shall provide circuits and network, as required by task order, which meet requirements in this PWS. The contractor shall support the government's request for information to obtain a DISA waiver.

1.1.6 Training Event Support

The contractor shall operate and maintain a help desk for scheduling and conducting DMO training events. The help desk shall be available via toll-free telephone, facsimile, and a web interface. The help desk shall normally operate from 7am to 7pm EST Monday –Friday, excluding federal holidays. When a DMO event is being executed, the help desk shall be available from one hour before the scheduled event until one hour after the event ending time, regardless of normal operating hours. The contractor shall track and resolve trouble tickets and network issues. The contractor shall accept routine federate requests with lead time for scheduling DMO events Not Later Than (NLT) one hour and Not Earlier Than (NET) 30 calendar days during normal help desk hours, and NLT 24 hours and NET 30 days for scheduling events outside normal help desk hours. While planning for larger exercises will take place beyond the 30-day limitations, event connection requirements will be coordinated within 30 days (i.e., Red Kite, Virtual Flags, etc.).

CAF DMO services, which were scheduled within the aforementioned lead times, shall be able to support events 24 hours a day, 7 days a week (i.e., DMO events can be executed at any time once they have been scheduled). The contractor shall configure and operate the network in support of scheduled training, testing, and maintenance events. The contractor shall supply bandwidth management services for operational sites. The contractor shall offer an online scheduling service to schedule the DMO network. The contractor shall provide the services and coordinating activities necessary to conduct DMO events.

1.1.7 Continuous Monitoring Services

The contractor shall sustain service for meeting JSIG requirements (reference listed in PWS section 2.1.4) through centralized security controls for system monitoring, audit file collection and analysis, vulnerability scanning, patching and anti-virus signature distribution.

The contractor shall perform all ongoing activities associated with Risk Management Framework (RMF) Step 6, Continuous Monitoring of Security Controls. This recurring step includes providing services specified in the Continuous Monitoring Plan to sustain Authorizations to Operate (ATOs). Continuous Monitoring is defined as a quarterly assessment to validate that security controls are still properly protecting the information systems in accordance with the ATOs. On a quarterly basis, the contractor shall perform a system assessment in accordance with each Continuous Monitoring Plan. The contractor shall document results in a Continuous Monitoring Report for each of the information systems. Deliverables include quarterly Continuous Monitoring Reports which shall accompany documentation provided under Section 4.11.1 to maintain security compliance.

CDRL A009 Technical Report Study/Services Sub-Title Interoperability and Standards (DI-MISC-80508B)

1.1.8 Access Point Connectivity Services

The contractor shall be responsible for the overall design, implementation, system administration, and sustainment of Access Point Connectivity (APC) kits.

APC Kits shall include a video teleconferencing (VTC) system, Voice over Internet Protocol (VoIP) telephone, access to all CAF DMO data repositories, printer and scanner functionality, boundary protection, and digital-signature functionality. APC Kits shall also include local file storage with read and write media, and Digital Video Disk (DVD) and Compact Disk (CD) read/write drives. APC Kits shall include security controls which support connecting to the CAF DMO network at all security levels, but not more than one security level at a time. The contractor shall provide an implementation and verification report, documenting successful post-installation testing of all APC Kit functions listed above.

CDRL A009 Technical Report Study/Services Sub-Title Interoperability and Standards (DI-MISC-80508B)

Interoperability Services

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 PWS section 4.12.4. The schedule shall show a 3-month projection. The contractor shall manage the Test Planning Working Group (TPWG) for CAF DMO.

The contractor shall provide support, analysis, and testing to integrate sites which have been awarded via 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 A009 Technical Report Study/Services Sub-Title Interoperability and Standards (DI-MISC-80508B) 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 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 manage the System Problem Report Working Group (SPRWG) for CAF DMO. The SPR Working Group (SPRWG) is the working forum, lead jointly by the Contractor and the USAF and composed of the Federate Systems stakeholders currently members of the DMON, responsible for documenting and managing SPRs.

Additional Federate Testing Support The contractor shall support additional federate testing as requested by the government. Future efforts will be negotiated through a separate task order.

Configuration Control Board (CCB) Services The contractor shall implement, manage, and maintain a DMO System Level Configuration Management process for the DMO CCB. The contractor shall perform the duties of the Configuration Manager and the CCB Secretariat to support the government CCB. These configuration management services include, but are not limited to, maintaining DMO system level documents; providing configuration controls to baseline documentation; archiving past baselines and resolving configuration control problems. The CCB obtains and reviews configuration changes, including federate changes, for impacts to DMO interoperability and DMO training. The contractor shall coordinate and include the federate changes in the IMS.