RFP_Attch_2_PWS_dated_20181107.pdf

PERFORMANCE WORK STATEMENT

FOR THE

505TH COMMAND AND CONTROL WING (CCW)

FOR

COMMAND AND CONTROL TECHNICAL SUPPORT CONTRACT (C2TSC)

Dated: 07 November 2018

NOT RELEASABLE TO DTIC PER DoD DIRECTIVE 5230.24

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors (EXPORT CONTROLLED DATA , ADMINISTRATIVE USE); 28 Feb 2014.

Other requests for this information shall be referred to 505 CCW, USAF, 138 Hartson Street, Hurlburt Field, FL 32544.

WARNING--This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2751 et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401, et seq. Violation of these export-control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

DESTRUCTION NOTICE—Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

TABLE OF CONTENTS

1.0 SCOPE 3

1.1 BACKGROUND 3

1.1.1 705 CTS

1.2 PROGRAM EXECUTION 7

1.2.1 Program Management

1.2.2 Operations

1.2.3 Technical Support

1.3 CDRL DELIVERABLES 23

Table 1 – CDRL/Deliverables 23

1.4 KEY PERSONNEL 25

Table 2 – Key Contractor Personnel Categories 25

1.5 GOVERNMENT-FURNISHED PROPERTY 29

1.6 GENERAL REQUIREMENTS 32

ATTACHMENT 1: OPERATIONAL SYSTEMS AND TOOLS 37

ATTACHMENT 2: DMOC MISSION AREAS 38

ATTACHMENT 3: LIST OF PLANNING DOCUMENTS 39

PERFORMANCE WORK STATEMENT

1.0 SCOPE

The contractor shall provide operational, technical, and analytical expertise for the planning and execution of training and test events, conducting Live-Virtual-Costructive (LVC) and Distributed Mission Operations (DMO) activities, providing operational support, providing non-kinetic operations training and tactics development support, and conducting operational testing (OT) of C2ISR systems. This effort includes program management, operations, and technical support tasks. Contracted work will be conducted at the Unclassified, Secret, Top Secret/Sensitive Compartmented Information (TS/SCI), and Special Access Program/Special Access Required (SAP/SAR) levels. CDRLs/deliverables are property of US government, and will include, but not be limited to, operational exercise plans, scenario development, system requirements documents, operational architectures, test plans, reports, and After Action Reports (AARs). This PWS covers the requirements at the 705 CTS at Kirtland AFB, New Mexico, and 705 CTS Operating Location Bravo (OL-B) at Nellis AFB, Nevada; all necessary management services, personnel, materials, components, supplies, maintenance, and documentation required to accomplish the full complement of tasks.

1.1 BACKGROUND

1.1.1 705 CTS Background. The mission of the 705 CTS is to develop and integrate technologies to deliver an LVC combat environment for Air Force, Joint and Coalition warfighter training. This mission requires the 705 CTS to maintain a highly-qualified staff of government and contractor personnel with expertise in warfighter training, test and evaluation, event execution, systems integration and interoperability, and LVC/DMO operations. The 705 CTS promotes the use of DMO capabilities to connect Air Force (AF), Joint, and Coalition simulators and facilities into an Operational Training Infrastructure (OTI) training environment to train to and test modern warfighting Tactics, Techniques and Procedures to prepare for major combat operations.

1.1.1.1 The 705 CTS DMOC is available to the United States Air Force (USAF), DoD, Government agencies, and Coalition partners. It serves as the USAF’s center of excellence for DMO integration and interoperability with operational experience in Army, Navy, Marine, and AF Theater Command and Control (C2) operations. The DMOC facility is an 80,000 square feet facility containing a 5,677 square feet raised floor operations area, a Sensitive Compartmented Information Facility (SCIF)/Special Access Program Facility (SAPF) area, a SCIF/SAPF Sidebay for high-side operations, a software development area, a 140-seat auditorium, 40-seat gallery, technical library, four 20-person mission planning/crew briefing rooms, and contractor office space on the second floor.

1.1.1.2 The 705 CTS military and government civilian personnel direct, oversee, and support the operations and maintenance of both the facility and mission. The 705 CTS is supplemented by contractors, who provide the technical expertise in event planning, execution, data collection, data analysis, and overall system support. DMOC military, government civilians, and contractors are responsible for the sustainment of the DMOC’s Battlespace netwroks, systems, and simulators to ensure they represent accurate versions that are concurrent with real-world warfighting systems.

1.1.1.3 The DMOC Battlespace is two enclaves containing systems that consists of various virtual and constructive AF and Joint weapon systems and simulators, a Technical Integration Cell (TIC), and a 40+ position White Force cell within the operations area. The TIC is the focal point for maintaining and monitoring the internal and external event/exercise networks, systems, and recording event data during all events/exercises. The White Force cell consists of environment generators (EG) that produce constructive entities run by man-in-the-loop control forces. The Battlespace is reconfigurable from event to event and is tailored to meet testing or training objectives identified during the event planning process. The Battlespace also includes a separate high-side environment (HSE) within the DMOC SCIF/SAPF Jumper Room to support high-side operations.

1.1.1.4 The DMOC development space (DevSpace) includes classified and unclassified development systems and networks for the design, developmental test, and acceptance testing of hardware/software solutions prior to placement on Battlespace operations floor or networks.

1.1.1.5 Utilizing the DMOC and associated resources, the 705 CTS performs LVC/DMO training, testing, and development with personnel operating live weapon systems and high fidelity virtual and constructive simulations to create a realistic synthetic combat-representative environment. DMOC resources include: simulations of airborne systems; surveillance systems; airborne and ground C2 systems; Integrated Air Defense Systems (IADS); voice communications systems; tactical/synthetic data link systems; data loggers; network analysis and routing tools; intelligence systems; and collaboration tools. Major internal DMOC systems and simulators include, but are not limited to an Air and Space Operations Center (AOC), Air Support Operations Center (ASOC) simulators, Battlespace Command and Control Center (BC3), Control and Reporting Center (CRC), Distributed Common Ground System (DCGS), Remotley Piloted Aircraft (RPA) simulator, Air Defense Artillery systems, Virtual E-3 variants Simulator, Virtual E-8 variants Simulator, and Close Air Support (CAS) simulators. The DMOC also routinely connects to a large number of external LVC/DMO-capable systems and simulators.

1.1.1.6 The DMOC leverages multiple EGs/constructive simulations and digital terrain databases to provide a realistic synthetic environment. The DMOC is capable of simulating more than 150,000 simultaneous air, ground, and surface entities in any single event. The DMOC is also involved in developing standards for modeling Information Operations (IO), Electronic Warfare (EW), and LVC/DMO.

1.1.1.7 The DMOC primarily utilizes the Distributed Interactive Simulation (DIS) protocol to interoperate with a variety of OTI simulation facilities and systems through Point-to-Point (P2P) connections, Wide Area Networks (WANs), and other DMO networks. Additionally, High Level Architecture (HLA) and Test and Training Enabling Architecture (TENA) protocols are used as required.

1.1.1.8 The 705 CTS executes VIRTUAL FLAG (VF), Coalition VF (CVF), Warfighter Focused Events (WFEs), and RDT&E events. In support of VF/CVFs, WFEs and RDT&E events, the contractor is required to attend multiple planning conferences and support preliminary meetings in order to better define event requirements. WFEs and RDT&E events may be conducted during or in conjunction with a VF/CVF or other DMOC events.

1.1.1.8.1 VF/CVF are campaign-level Large Force Exercises (LFEs) directed by the Commander, Air Combat Command (COMACC) Execution Plan (EXPLAN) 88 to provide Operational Plan (OPLAN) familiarization. These exercises support Combatant Commander (COCOM) high-interest training requirements and individual unit training objectives, typically involving 300-500 participants worldwide. Participants include representatives from fighter aircraft, bomber aircraft, air C2 platforms, ground C2 platforms, Intelligence, Surveillance and Reconnaissance (ISR) platforms, AOC, Remotely Piloted Aircraft (RPA), and ground controllers. Each VF typically includes 10-20 local simulator systems and 10-20 external simulator systems connected through 5-10 networks and multiple point-to-point connections as required. The 705 CTS has historically executed three VF and one CVF exercises annually.

1.1.1.8.2 Due to the recurring nature of VF, there may be overlap between exercise efforts. During any given year the contractor may work on portions of up to six VF exercises. VF requires a minimum of 4 to 6 months of planning efforts with a minimum 12 month planning timeline for CVF. The level of effort during the planning period varies based on required EG support, participants, security and cybersecurity requirements, planning conferences, and integration of new sites and systems.

1.1.1.8.3 Typically, VF/CVFs consist of one week of internal integration, three days of external integration, two days of academics/mission planning, one familiarization (FAM) day, and four days of execution. FAM day and execution days include mass briefings, mission planning, execution vulnerability (VUL) period, debriefings, hot washes, and executive summaries. Extended duty days are typically required during VF/CVF execution.

1.1.1.8.4 WFEs are similar to VFs but vary in scope to meet specific AF, DoD, or Coalition training requirements. WFEs typically include two to five participants focused on a single mission thread with associated training objectives. Historically the DMOC has executed/supported eight USAF Weapons School classes, two Army Joint Kill Chain Events (JKCE), and six Navy Fleet Synthetic Training (FST) exercises annually. Additional examples include, but are not limited to, support of

Headquarters Air Force (HAF)-directed events, Combat Air Force (CAF) Distributed Training Center (DTC) support, USAF Warfare Center (USAFWC) High End Advanced Training and Tactics (HEAT2), Red Kite (UK event) support, Emerald Warrior (EW) support, Northern Edge (NE) support, RED FLAG (RF) support, GREEN FLAG (GF) support, and BLUE FLAG (BF) support.

1.1.1.8.5 RDT&E events vary in scope and size and are conducted in support of formal acquisition testing/evaluation and the development or refinement of Tactics, Techniques, and Procedures (TTP). Historically, the DMOC has executed/supported up to three RDT&E events annually.

1.1.1.9 The 705 CTS OL-B supports the Virtual Test and Training Center (VTTC);

facilitating two USAF Weapons School events annually.

1.2 PROGRAM EXECUTION

The contractor shall establish, execute, and maintain the following functions in support of the government: program management, operations, and technical support.

1.2.1 PROGRAM MANAGEMENT

The contractor shall develop, execute, and maintain a defined Program Management Plan for all efforts in accordance with (IAW) industry best practices. The Government will conduct surveillance of the performance of services and various operational processes. (A001)

1.2.1.1 The contactor shall manage, control, and administer the effort to ensure successful performance of all tasks. The contractor shall provide cost, schedule, and performance tracking and forecasting of program status at the Contractor Line Item (CLIN) level. This shall be provided in a monthly status report. (A002, A003)

1.2.1.1.1 The contractor shall differentiate between appropriation types and fiscal years of funding. (A002)

1.2.1.1.2 The contractor shall ensure appropriate contractor representation at all programmatic meetings.

1.2.1.2 The contractor shall identify, actively manage and prioritize, and mitigate risks and/or issues relevant to the efforts on this contract.

1.2.1.3 The contractor shall conduct quarterly Program Management Reviews (PMRs) with the 705 CTS. The PMR shall summarize efforts during the reporting period to address, at a minimum, the following topics: (A002, A003)

a. Contractor personnel status

b. Overall resource status

c. Contractor activity schedule (6 months out)

d. Contract and CLIN budget status

e. CLIN schedule and progress status

f. Contractor-identified risks/issues and mitigation plans

g. Items requiring Government action

1.2.1.4 The contractor shall hire and retain qualified personnel at contract start sufficient to execute all tasks under this contract. The contractor shall minimize mission impact due to position vacancies or insufficient personnel qualifications. Operational tasks will vary both in length and frequency and therefore some flexible staffing capability may be required.

1.2.1.4.1 The level of effort the DMOC requires to cover all daily operations, exercise events (both O&M and RDT&E), planning, and support, is approximatly 75,000 hours of work covered in a 1920 hour man-year.

1.2.1.5 The contractor shall work with the government to prioritize and de-conflict all activities to minimize the impact to operations, pre-event activities, event execution, or post-event activities.

1.2.1.6 The PM or delegated personnel shall attend internal government meetings to include, but not limited to; weekly staff meetings, scheduling and performance meetings, technical interchanges, design reviews, test readiness reviews, exercise planning meetings, informational meetings, administrative meetings, event readiness reviews, technical and operational event briefs and debriefs, etc.

1.2.1.7 The contractor shall actively provide recommendations to the government for the approval of process and technical improvements to operations and all efforts on this contract. Recommendations shall be provided IAW the 705 CTS Strategic Planning Document (SPD) process.

1.2.1.8 Pursuant to the Program Management Plan, the contractor shall assist in the development and maintenance of current government integrated schedules.

1.2.2 OPERATIONS

1.2.2.1 The contractor is responsible for translating customer requirements into technical Battlespace requirements; identifying requirements for facility upgrades for customer test or training events; and conducting real-time troubleshooting and issue resolutions during tests or exercises.

1.2.2.2 The contractor shall support planning, leading, and directing LVC/DMO exercises and projects.

1.2.2.3 The contractor is responsible for creating development and exercise plans and schedules, coordinating with other distributed simulation sites, providing direct, hands-on event execution management, and managing event support personnel. (A006)

1.2.2.4 The contractor is responsible for maintaining a successful crew of operators for all simulators and systems used for tests and exercises.

1.2.2.5 SCENARIO DEVELOPMENT

1.2.2.5.1 The contractor is responsible for coordinating scenario development process from early discussions through scenario design, generation, testing, and execution.

1.2.2.5.2 The contractor is responsible for defining scenario requirements, writing the scenario design document, encoding player characteristics in the environment generators, configuring virtual simulation initialization files, and verifying proper execution of the scenario during event integration testing and event execution.

1.2.2.5.3 The contractor is responsible for designing and delivering realistic scenarios and providing products such as, but not limited to, Air Tasking Orders (ATO), Concept of Operations (CONOPS), and Rules of Engagement (ROE) to operational crews participating in exercises. (A012)

1.2.2.5.4 The contractor is required to have a detailed understanding of scenario generation systems and the development and testing of scenarios for a wide range of users, for applications such as theater missile defense, joint interoperability issues, degraded mission operations, cyber and space operations, and advanced combat identification systems.

1.2.2.5.5 The contractor is responsible for validating the extensive databases used to generate scenarios.

1.2.2.5.6 The contractor is responsible for developing the master exercise script which details participants and their roles, the schedule of events, and scenario execution. (A006, A011, A012)

1.2.2.6 SCENARIO DESIGN AND IMPLEMENTATION

1.2.2.6.1 The contractor shall provide the in-house expertise to support the government in all aspects of scenario design and construction. The effort shall include , but not limited to, an overall exercise plan that addresses all aspects of warfare to include Order of Battle development, adversary tactics, constructive entity generation and employment, virtual asset integration, overall campaign planning, joint force employment, communications planning, Air Tasking Order (ATO) and Airspace Control Order (ACO) development, maritime planning, Army Air Defense Artillery planning, threat Integrated Air Defense System (IADS) employment, ground force maneuver, theater ballistic missile planning, incorporation of Information Operations and Cyber Warfare, space operations, and Intelligence, Surveillance, and Reconnaissance (ISR) support. Development efforts shall involve use of current tools (i.e. TBMCS) and incorporate current, relevant scenarios. (A006, A012)

1.2.2.6.2 Contractor shall coordinate with the Exercise Director and respond within 12 hours for change requests, to include scenario changes, exercise document changes, etc.

1.2.2.6.3 Contractor shall obtain current theater relevant products to support scenario development and reflect real world problem sets.

1.2.2.6.4 The contractor shall construct, deliver and disseminate all required exercise documentation (i.e. Special Instructions [SPINs] and Air Operations Directive [AOD]) per Exercise Director; Table 1 and Attachment 3. (A006)

1.2.2.6.5 The contractor shall capture previous lessons learned and ensure they are appropriately incorporated into new scenario builds or existing scenario modifications per direction from Exercise Director. (A008)

1.2.2.6.6 The contractor shall provide technical and operational expertise capable of operating the systems listed in Attachment 1.

1.2.2.6.7 The contractor shall provide engineering test scenario support for simulation testing, integration testing, and troubleshooting\resolution of system problems.

1.2.2.6.8 The contractor shall assist the government in developing high-side/SAP/SAR training capability to include associated computer generated forces simulations, and implementing Joint Information Operations (IO) Range capabilities.

1.2.2.6.9 The contractor shall assist in the development of Joint/VF emitter databases in support of increased fidelity for EW and cyber training opportunities.

1.2.2.6.10 The contractor shall explore integrating live range-instrumented entities, such as pod-equipped aircraft and GPS-instrumented surface vehicles, into the virtual contructive environment.

1.2.2.6.11 The contractor shall work with the government or other contractor organizations as necessary, to develop joint database standards such as Common Database (CDB)/terrain models, scenario databases, and emitter databases.

1.2.2.7 EVENT SUPPORT

The contractor shall be responsible for planning, implementing, and providing support for execution of government directed events, to include, but not limited to; support of high-side operations, execution of classified test plans, and troubleshooting issues related to secure Distributed Mission Operations (DMO). Specific support is for pre-event activities, event execution, and post-event activities to include, but not limited to establishing and maintaining network connectivity with geographically distributed sites, configuring networks, supporting integration testing, and troubleshooting event/exercise support systems.

1.2.2.7.1 DMOC Directive (DD) documents will be provided by the government for each event, as a supplement to the PWS, to provide event-specific information such as schedule, networks, internal systems, external participants and event leads.

1.2.2.7.2 The contractor shall maintain the ability to meet various urgent-to-need events, to include capability to execute WFE-type events within 72 hours upon government direction.

1.2.2.7.3 The contractor shall utilize interface tools and processes to populate exercise/event scenarios with joint computer generated forces simulations.

1.2.2.7.4 The contractor shall monitor changes to customer requirements, support meetings and conferences as required, and oversee all scenario design, project execution, and applicable documentation development. (A005, A006, A012)

1.2.2.7.5 The contractor shall provide personnel who are subject matter experts competent in the mission areas and training events across all four services and multiple major weapon systems (MWS); see list of competencies identified in Attachment 2.

1.2.2.7.6 The contractor shall provide a technical lead for the overall technical effort for each event. This effort may include, but is not limited to: conducting the technical portion of the Exercise Planning Conference (EPC); translating operational requirements into technical requirements; designing the event systems architecture, developing the event test plan, coordinating technical efforts, organizing engineering support for site liaison teams and government systems;

coordinating development of individual system test plans; supervising system and integration testing; conducting daily technical briefings and debriefings;

maintaining an assessment of the technical status of the event; identifying and prioritizing technical problems; leading issue mitigation efforts; manage exercise/event releveant sotware applications/tools, and documenting and assessing technical lessons learned.(A006, A008)

1.2.2.7.7 The contractor shall identify the specific systems (computer names) needed for the exercise and provide that information to the government.

1.2.2.7.8 The contractor shall provide engineering support on DIS filter and datalink systems during integration and execution.

1.2.2.7.9 The contractor shall support the integration and operation of Battlespace systems (see Attachment 1) as required by the Exercise Director to meet operational requirements for each event.

1.2.2.7.10 The contractor shall provide the following engineering support for the sites/systems within the DMOC:

• Support site/system specific testing

• Verify systems are implemented and functional for the event

• Work with IDE contractor to troubleshoot system problems

• Verify and document resolution of system problems

• Translate site operational requirements into technical requirements

• Coordinate Battlespace architecture changes to support the site technical requirements

• Provide test plans to the 705 CTS for applicable systems

1.2.2.7.11 The contractor shall Manage Tactical Chat rooms by supporting the integration and operation of DIS Voice and VoIP equipment and configure it for use during DMOC events.

1.2.2.7.12 In close coordination with the exercise director, the contractor shall provide an exercise coordinator to conduct day-to-day exercise support, planning and execution.

1.2.2.7.13 The contractor shall provide White Force training and execution support, including, but not limited to:

• Individualized training based on the specific mission sets to be accomplished (ATO breakout, mission overview)

• Basic NGTS user operation, or similar environmental generators, and advanced EG operations/platform TTPs based on mission requirements

• Contested Degraded Operations (CDO)

• Tactical chat familiarization

• Wing Operations Center (WOC) training and support

• Tactical communications (brevity) and the use of communications equipment (Quickdraw/II, etc)

1.2.2.7.14 The contractor shall provide a customizable White Force as a control force for all major mission areas, to include but not limited to; Strike, DCA, OCA, SEAD,WAS, XINT, CAS, PR, Airlift/Tanker, WOC

1.2.2.7.15 The Contractor shall serve as White Force, including, but not limited to, Army Staff, Fires Direction Center, additional scenario enhancing agencies or assets. The contractor shall ensure participants on-site have acess to graphics to support exercise execution, and coordinate with off-site sim operators to ensure systems and scenarios are prepared for events.

1.2.2.7.16 The contractor shall supplement as White Force lead, mission set leads and/or participant when suitable exercise participants are not available.

Assignments will be based at the discretion of the Exercise Director.

1.2.2.7.17 The White Force Lead shall be operationally competent with multiple mission set experience (DCA, OCA, XINT, CAS, Strike, SEAD, WAS, XSCP, WOC, PR) responsible for the management and directing of activities for personnel driving constructive entities during the exercise.

• Provide scenario oversight to assist with exercise control

• Coordinate discrepencies/resolutions/real time scenario adjustments with the Exercise Director, Exercise Coordinator, OA Cell, and EG operators.

1.2.2.7.18 Mission Set Leads shall be the assigned mission set scenario SME, participate in mission planning, brief/debrief mission set, operate CGFs, and lead exercise participants in accordance with the Exercise Director’s discretion. Mission Set Leads will coordinate with White Force Lead for real-time scenario adjustments or discrepancy resolution.

1.2.2.7.19 Contractor shall provide OPFOR cell (Red Lead, Red SME’s, CDO SME’s) to manage enemy tactical courses of action (air, land, sea, cyber, space), to include but not limited to; manuvers, CDO, patterns of life, emmissions, communications, defenses.

1.2.2.7.19.1 Red lead shall be responsible to the Exercise Director for briefing OPFOR academics and Operational Assessment Cell coordination

1.2.2.7.19.2 Red Lead shall lead all OPFOR coordination, briefings, debriefings as required throughout all execution and planning meetings

1.2.2.7.19.3 Red SME’s shall operate all CGF’s, to include; DICE, OPFOR, NGTS, etc

1.2.2.7.19.4 CDO SME’s shall scenario plan and execute jamming (Datalinks/Comm/GPS/IFF), Tactical Chat intrusion and other requirements at the discretion of the Exercise Director

1.2.2.7.20 Contractor shall provide a Cyber SME to advise, teach and execute network warfare operations (NW Ops).

1.2.2.7.20.1 Contractor shall train warfighters and capture, record, and develop tactics, techniques, and procedures (TTPs) during Distributed Mission Operations Center (DMOC) exercises and events.

1.2.2.7.20.2 Contractor shall participate in DMOC training events throughout the planning, briefing, execution, and debriefing (PBED) process.

1.2.2.7.20.3 Contractor shall coordinate cyber support with the 624th Operations Center for DMOC Mission Assurance (MA) Operations during exercises and events.

1.2.2.7.20.4 Contractor shall coordinate with AFCYBER to work with the DMOC team as required.

1.2.2.7.20.5 Contractor shall work with DMOC’s NOC and other

personnel in order to identify, defend and defeat cyber related degraded operations during exercises and events.

1.2.2.7.20.6 Contractor shall conduct the detailed integration of cyber capabilities to include network attack (NetA), network defense (NetD), and network warfare support (NS) across air, space and cyber domains.

1.2.2.7.20.7 Contractor shall provide integrated planning and employment of NW Ops, along with electronic warfare operations (EW Ops), influence operations, as well as new and emerging cyber capabilities for use in Test and Evaluation (T&E) nomination and development.

1.2.2.7.20.8 Contractor shall support exercise scenario development, planning (Concept development, Initial Planning, Mid Planning, Final Planning), execution and Lesson Learned/TTP development for USAFWC and 505 CCW sponsored events as well as ad hoc support to local training exercises and classified theater exercises.

1.2.2.7.20.9 Contractor shall contribute to WEPTACs to ensure current weapons and tactics are integrated into DMOC exercises & events.

1.2.2.7.21 The contractor shall operate the Joint Terminal Control Training and Rehersal System (JTC-TRS), Joint Theater Air Ground System Simulator (JTAGSS), and other Close Air Support (CAS) simulation systems for, Virtual Flags and other training events.

1.2.2.7.22 The contractor shall provide operational expertise in the preparation and execution of all planning conferences. This shall include assistance with any research, documentation, planning, or briefings required by the government.

1.2.2.7.23 The contractor shall support the government in all aspects of exercise coordination to include providing operational/technical information to participants and scheduling events.

1.2.2.7.24 The contractor shall provide operationally and technically competent systems engineers to operate Battlespace weapons systems as required per Attachment 1; design scenarios across multiple constructive simulations; and provide expertise on the real-world operational characteristics of threat and friendly weapon systems, radar sensors, tracking systems, Identification Friend or Foe (IFF), datalinks, infrared sensors, theater air defense weapon systems, fire control systems, Electronic Warfare (EW), air and missile system flight performance, terrain databases, real-world mission planning tools such as Theater Battle Management Core System (TBMCS), Portable Flight Planning System (PFPS), Joint Mission Planning System (JMPS), brief/debrief and other collaboration tools, such as Tactical Chat. (A012)

1.2.2.7.25 The contractor shall provide C4I/datalink operational document development, integration support and exercise support to include exercise C4I/datalink operational concept diagram, exercise OPTASKLINK development, C4I/datalink inputs to SPINS, exercise C4I/datalink force lay down slide and OPTASKLINK derivative information for technical integration and support (i.e.

OPTASKLINK Cutsheet) (A012)

1.2.2.7.26 The contractor shall identify personnel to serve as operations/technical liaisons to each site participating in an event. As part of a site liaison team, including a government lead, the contractor shall integrate the sites operational and technical requirements into the event, maintain awareness of the site’s status, and resolve issues related to the site. The contractor’s responsibilities may include, but may not be limited to:

• Translating the site’s operational requirements into technical requirements for the event

• Coordinating architecture changes to support the site’s technical requirements

• Developing system and integration test plans

• Establishing data filtering and analysis plans

• Maintaining awareness of the site’s technical and system configuration management status

• Resolving interoperability problems related to the site

• On a case-by-case basis, site liaisons may be required to travel to their respective sites.

1.2.2.7.27 The contractor shall support the development of all required documentation in support of event approval for controlled interface and MNIS operations. (A012)

1.2.2.7.28 During events, the contractor shall support operation of controlled interface and MNIS operations, to include implementation of operational rules and verification that the operational and technical rules are effective.

1.2.2.7.29 The contractor shall support the implementation of data links (Situational Awareness Data Link (SADL), Tactical Digital Information Link (TADIL), Multifunction Advanced Data Link (MADL), Link 16, etc.) capability to support virtual and potential live training integration involving joint warfighters.

1.2.2.7.29 The contractor shall support scenario development, integration, test, and operation of two VTTC Weapons School events per year.

1.2.2.8 AFTER ACTION REPORTING

The contractor shall provide actionable lessons learned from event execution and support development of the AAR by the government; Table 1, and after action reports following the completion of compliance testing. (A008)

1.2.2.8.1 The contractor shall support technical conferences as directed, such as the annual Inter-service/Industry Training, Simulation and Education Conference

(I/ITSEC)

1.2.2.8.2 The contractor shall develop articles and make presentations on technical/operational M&S capabilities and concepts at professional conferences and symposia as directed by and coordinated through the government for release.

(A009)

1.2.2.8.3 The contractor shall deliver trip reports on all meetings that include external (i.e., non-government) attendees. When a government representative attends, the contractor traveler shall coordinate with the government representative to provide trip report information into a single trip report. (A004)

1.2.2.8.4 The contractor shall update and maintain joint System Limitations Integration Capabilities Kneeboard databases (SLICK Books), scenario database repositories, event products and other products as required by the Government.

1.2.3 TECHNICAL SUPPORT

1.2.3.1 REQUIREMENTS DEVELOPMENT AND ANALYSIS

1.2.3.1.1 The contractor shall support requirements definition for requirements for new systems and the evaluation of new systems, integration of existing systems into DMO, and system enhancements.

1.2.3.1.2 The contractor shall support requirements definition for development of OTI capabilities. These capabilities include an integrated and persistent network of OTI simulations and systems to provide a realistic training environment improving warfighter readiness within the Air Force, Joint, and Coalition community.

1.2.3.1.3 The contractor shall support requirements definition for OTI simulations and systems, scenario generation tools, mission planning tools, datalink and operational support systems, data support tools, and collaboration tools.

1.2.3.1.4 The contractor shall support the government in defining test and/or exercise objectives and supportive mission threads to effectively accomplish objectives.

1.2.3.1.5 The contractor is responsible for supporting development and integration of new capabilities by defining technical requirements, writing requirements documents, defining functional architectures, reviewing design specifications, monitoring development, developing acceptance test plans, executing acceptance tests, and writing acceptance test reports. (A006)

1.2.3.1.6 The contractor is responsible for defining distributed simulation networks and C2 communications architectures, defining data collection requirements and methods, developing analysis plans, and implementing analysis databases.

1.2.3.1.7 The contractor shall evaluate and report on issues associated with new CONOPS and TTPs and shall make operational and technical recommendation.

(A008)

1.2.3.1.8 The contractor shall perform systems engineering requirements analysis to translate operational requirements into technical requirements documents (i.e., System Subsystem Specifications [SSS]) that support the evaluation and development of new systems, integration of existing systems into DMO, and system enhancement. (A012)

1.2.3.1.9 The contractor shall provide inputs to the government detailing new technical requirements that support projects’ operational goals. (A008)

1.2.3.1.10 The contractor shall provide studies and analysis inputs (white/research papers, new and emerging reqts, technhology, etc) as directed by the government.

(A006)

1.2.3.1.11 The contractor shall provide script development to automate processes to create efficiencies and user interfaces. (A006)

1.2.3.1.12 The contractor shall work with government designated personnel to coordinate system requirements with external system sponsors.

1.2.3.1.13 The contractor shall attend product user group meetings, work with the government to host user group meetings to include developing agendas, and provide feedback to meeting sponsors.

1.2.3.2 STUDIES &ANALYSIS

1.2.3.2.1 The contractor shall perform S&A as directed by the Government through an SPD. Studies may include, but are not limited to, examining the feasibility of adapting new or upgraded simulators, systems, tools and software, potential requirements, or Battlespace/DevSpace enhancements. (A007)

1.2.3.2.2 The contractor shall provide recommendations to improve event execution and correct event issues by refining concepts and analyzing any configuration changes required to the government. The contractor shall provide technical options with cost and schedule estimates for development, and/or design and implementation of these changes. (A007)

1.2.3.2.3 The contractor shall author and/or co-author papers and presentations related to LVC/DMO on topics approved by the government, review papers presented, and contribute responses. All products will be submitted to the government for review and approval for release. Topics may include impacts for associated standards, general LVC/DMO activities, and advice to help guide LVC/DMO development. (A007)

1.2.3.3 ACCEPTANCE TESTING

1.2.3.3.1 The contractor shall provide reliable and accurate test, evaluation and acceptance recommendation for government projects.

1.2.3.3.2 The contractor shall develop system level acceptance plans to formally accept any new or modified system within the battlespace. (A006)

1.2.3.3.3 The contractor shall translate operational requirements into procedures, develop plans, execute events, and document results.

1.2.3.3.4 The contractor shall develop and review scenarios for use in all system acceptance, integration, operational, interoperability, certification, and accreditation compliance conducted by the government.

1.2.3.3.5 The contractor shall provide engineering support for all system acceptance, integration, operational, interoperability, certification, and accreditation compliance conducted by the government. (A006, A008)

1.2.3.3.6 The contractor shall support the government and its customers to define viable test events, develop test plans, ensure the operational relevance of the test focus, prioritize test items, provide operational support for the test events, and document the operational impact of test findings. This task relates to government system development, training, testing, and experimentation events; software evaluation; and system certification and accreditation. (A006, A008)

1.2.3.4 CONTROLLED INTERFACE AND MULTINATIONAL INFORMATION

SHARING

1.2.3.4.1 The contractor shall provide engineering expertise and project management for controlled interface and MNIS architectures, systems, and rule set activities.

1.2.3.4.2 The contractor shall research system information, security classification guides, Delegation of Disclosure Letter (DDL) documentation, and other applicable information to determine what information needs to be protected from non US participants.

1.2.3.4.3 The contractor shall support the development of rule sets, maintain the event CONOPS, build test plans, conduct testing, analyze results, document test reports, and provide recommendations on the viability of controlled interface and MNIS solutions. (A006, A008, A012)

1.2.3.4.4 The contractor shall provide expertise in the development and evaluation of controlled interface and MNIS simulation rule sets designed to protect information while maintaining the ability to accomplish test, training, and experimentation goals.

1.2.3.4.5 The contractor shall translate security requirements into technical rules for implementation on controlled interfaces. (A006, A008)

1.2.3.4.6 The contractor shall document technical rule sets with, including but not limited to, written reports and diagrams that provide details regarding the rules to be implemented. (A008)

1.2.3.4.7 The contractor shall support controlled interface and MNIS technical operations to include operation of network guards and filters.

1.2.3.4.8 The contractor shall support the government and contractor organizations as necessary, to conduct real-time and pre/post-event analysis of technical rule implementation. This includes, but not limited to, support of formal security testing, and evaluation of guard solutions.

1.2.3.5 CONFIGURATION MANAGEMENT

1.2.3.5.1 The contractor shall work with the government to maintain Configuration Management (CM) of all DMOC systems.

1.2.3.5.2 The contractor shall coordinate system configuration changes with the Infrastructure, Development, and Engineering (IDE) contractor.

1.2.3.5.3 The contractor shall support CM of all threat and friendly weapon system performance databases.

1.2.3.5.4 The contractor shall work with the government and IDE contractor to develop and implement CM and quality assurance activities.

1.2.3.5.5 The contractor shall coordinate all configuration and software changes with the IDE contractor.

1.2.3.5.6 The contractor shall provide technical guidance and recommendations to assist the government in prioritizing changes to the battlespace architecture.

1.2.3.5.7 The contractor shall submit Engineering Change Requests (ECRs) for architecture and documentation changes, validated system problems, and proposed system modifications.

1.2.3.5.8 The contractor shall manage all DIS Filter configuration files, controlled interface network guard rule sets, and all protocol and data link conversion configuration files.

1.2.3.5.9 The contractor shall organize and conduct periodic tests to verify system reliability and interoperability, test system changes proposed for incorporation into the battlespace baseline and document current system configurations. (A006, A008)

1.2.3.5.10 The contractor shall manage scenarios controlled, developed or installed under this PWS.

1.2.3.5.11 The contractor shall provide technical advice regarding management of all threat and friendly weapon system performance databases.

1.2.3.5.12 The contractor shall support model development and validation.

1.2.3.6 VISUAL MODEL DEVELOPMENT

The contractor shall develop, update, and maintain entity models in the Visual Database Catalog (VDC), and support the testing of models for events/exercises including, but not limited to, Joint Kill Chain Event (JKCE), Weapons School Syllabus Training, VIRTUAL FLAG, and collaborative COALITION VIRTUAL FLAG/RED FLAG exercises. Additional support includes scenario development and other work related to the VDC on systems such as the Air Force Synthetic Environment for Reconnaissance (AFSERS) and Intelligence Surveillance Reconnaissance Battle Damage Assessment (ISR/BDA) when not performing the tasks outlined below. (A006, A008, A013)

1.2.3.6.1 Specifications Generation

The contractor shall generate specifications for the completion of each model to include, but not limited to, sample imagery, dimensions, spectrum information, damage state descriptions, and any other pertinent information required. (A013)

1.2.3.6.2 Design Review

The contractor shall provide a list of model specifications and conduct a design review to present models to the government for approval as needed to support events. (A013)

1.2.3.6.3 Development

The contractor shall build entity models that are observable in current MetaVR, HPY, and Openflight systems. These models shall be constructed using software and hardware provided as GFE. Modeler shall be competent in Autodesk, ESRI Arc/GIS, MetaVR, and Gimp photo-editor. The typical development actions and definitions for each model type are provided in the table below. (A013)

1.2.3.6.4 Model Review

The contractor shall conduct a model review with the government wherein the government shall verify the accuracy of the visual models, particularly the rendering of damage states. (A013)

1.2.3.6.5 Rework/Re-review

The contractor shall record and repair any noted discrepancies and present the corrected versions at the next Model Review. (A013)

Action Definition

Hull Number Changes

Changing or affixing a specific number to the hull of a preexisting ship model

Surface Changes Changing the appearance of an existing model (i.e., changing camouflage pattern of a vehicle or adding camouflage netting)

Add Articulating Parts

Updating a previously rendered model to include moving parts (i.e., adding retractable landing gear to aircraft or rotating turret to tank) Model Upgrade Increasing the realism of an existing model

New Stationary Model

Building new models of buildings, roads, runways, and other terrain features with damage states, electro-optical (EO) and infrared (IR) spectrum views, and articulating parts

New Moving Model Building new models of ships, aircraft, tanks, trucks, etc. with damage states, both EO and IR spectrums, and articulating parts

1.2.3.6.6 Delivery

The contractor shall deliver models in current MetaVR, HPY, and Openflight systems with all required data to modify the model via DVD or CD to the DMOC Library. The contractor shall populate the VDC with all created/updated models with each incremental delivery. All models must be properly delivered in order to be considered complete. (A013)

1.2.3.7 CRC SIMULATION PACKAGE (CSP) HELPDESK

1.2.3.7.1 The contractor shall support CSP helpdesk and testing of a CSP version benchmarked across the USAF and ANG ACS which uses the distributed interactive simulation (DIS) protocol; including the identification of the CAF DMO standards which required additional development for the CSP suite.

1.2.3.7.2 The contractor shall maintain and support the CSP Help desk to improve CRC participation in CAF DMO or LVC-OT exercises and operations at DMOC which directly enhances ACS training.

1.2.3.7.3 The contractor shall conduct all work in accordance with (IAW) task order language and contract requirements. Any necessary design recommendations must be approved by government.

1.2.3.7.3.1 Provide CSP/CRC system expertise to the project for requirements/standards definition.

1.2.3.7.3.2 Evaluate/review the CAF DMO Standards describing the mission package which may impact CSP.

1.2.3.7.3.3 Establish test plans and conduct acceptance testing on new software packages.

1.2.3.7.3.4 The contractor shall perform Program Management (PM) and administrative functions for this task order.

1.2.3.7.3.5 Plan trips to support CSP testing at CONUS or remote ACS locations at the discretion of the government.

1.2.3.8 OPERATIONAL ASSESSMENT

1.2.3.8.1 The contractor shall assist the government and its customers in assessing the quality of training, testing, and experimentation events. This operational assessment shall include assisting in the coordination of event and unit objectives;

developing and implementing performance measurements; collecting and analyzing performance data; and reporting the results of these assessments into formal government AARs. (A008)

1.2.3.8.2 The contractor shall assess the value and impact from the addition of new (or modifications/upgrades to existing) C2ISR, weapon systems, and OTI capabilities into the battlespace.

1.2.3.8.3 The contractor shall report on the value and/or impact in cost, time, schedule, changes to other existing systems, system response time, system complexity and maintainability, system operations and procedures, facility support and loading, and staffing.

1.2.3.8.4 The contractor shall participate in the management and control of a system assessment process.

1.2.3.8.5 The contractor shall provide and maintain a system analysis effort for conducting and documenting studies to verify the battlespace meets government user requirements. (A007)

1.2.3.8.6 The contractor shall verify that the battlespace provides the required interfaces, properly executes approved scenarios in real-time, and provides the appropriate data for analysis and reporting.

1.2.3.8.7 The contractor shall analyze the impact of selected models on operational tests, operational test objectives, and test results. (A007, A008, A013)

1.2.3.8.8 The contractor shall analyze the test data available from each system for trends, identify and report on data required to support analysis and test objectives.

(A006)

1.2.3.9 INTEROPERABILITY

1.2.3.9.1 The contractor shall provide systems engineering services to support the government in maintaining the battlespace as an integrated, reliable, responsive, and fully functional facility for training, testing, and experimentation.

1.2.3.9.2 The contractor shall support resolution of interoperability problems identified during acceptance testing, event integration/execution, standards compliance efforts, or as otherwise directed by the government.

1.2.3.10 STANDARDS SUPPORT

1.2.3.10.1 The contractor shall provide recommendations to the development of distributed simulation standards and protocols as required by the government.

1.2.3.10.2 The contractor shall participate in the Simulation Interoperability Standards Organization (SISO), CAF DMO Standards Development Working Group (to include 5th Gen Standards), CAF DMO Test Plan & Implementation

Working Group (TPIWG), and Joint Architectures and Technical Standards (JATS) working groups, as well as similar organizations as directed by the government.

1.2.3.10.3 The contractor shall provide operational and technical support for activities involving CAF DMO Mission Package (MP) certification.

1.2.3.10.4 The contractor shall write and present technical papers addressing simulation standards issues. These papers will be coordinated through the government for approval and releasability prior to distribution or presentation.

(A008)

1.2.3.10.5 The contractor shall review and comment on proposed standards that may impact operations.

1.2.3.10.6 In coordination with the IDE contractor, the contractor shall translate CAF DMO standards criteria into system requirements.

1.2.3.10.7 The contractor shall determine realistic CAF DMO MP test methods, developing test plans,…