DRAFT_3IS III_Atch 9_392 CTS PWS_v1.0.pdf

Task Order FA2518-23-F-XXXX

DRAFT

RFP# FA2518-22-R-0023

Attachment 9, 392 CTS PWS

Performance Work Statement

FOR

392d Combat Training Squadron

13 October 2022

Task Order FA251822F0022

FA255017D8001

1. GENERAL TASK DESCRIPTION

The mission of the 392 CTS is to provide space combat training through live, virtual, and constructive (LVC) environments to prepare warfighters to win. In this role, the 392 CTS operates an organic state-of-the-art Systems Toolkit (STK)-based space battle laboratory (BattleLab), and the Distributed Mission Operations Center - Space (DMOC-S) training architecture, a Joint National Training Capability (JNTC) to provide space modeling and simulation (M&S) in support of advanced training, exercises, tests, experimentation, and mission rehearsal events.

Combined, these capabilities form the core of the 392 CTS M&S Enclave. The enclave provides M&S capabilities for United States Space Force (USSF) exercises, Combatant Commands (CCMDs), Services, and Combat Support Agencies. The 392d Combat Training Squadron (392 CTS) acts on behalf of USSF to plan, coordinate, and execute USSF’s flag-level SPACE FLAG (SF) exercise to provide space operators with the advanced training (AT) they need to shift from a focus on weapon system procedural currency to a mindset of executing space operations in a contested, degraded, operationally-limited (CDO) environment. Serves as the executive agent for the Secretary of the Air Force-sponsored SPACE FLAG exercise. The 392 CTS operates the USSF’s only certified Joint National Training Capability (JNTC) site, the Distributed Mission Operations Center - Space (DMOC-S) and the USSF’s only accredited training program, the SPACE FLAG (SF) exercise. In coordination with SpOC and other entities, the 392 CTS will plan and execute all SPACE FLAG exercises, to include scenario development, and will also coordinate modeling and simulation support, as required. In this role, the 392 CTS is responsible for establishing and maintaining collaborative relationships with USSF, multi-service/joint, interagency, ally, and partner organizations necessary to align efforts, maximize effectiveness and efficiency, and accomplish assigned missions. These missions include the following activities:

1) Coordinate with SpOC, STARCOM, NRO and the 1st Delta Operations Squadron to execute the USSF Service Exercise Plan (SEP) in support of USSF, multi-service, joint, interagency, and allied exercises.

2) Provide combat training planners and instructors to lead, plan, execute, and act as the executive agent for the development and execution of USSF exercises, and also USSF participation in multi-service, joint, interagency, and allied exercises. 392 CTS combat trainers will champion service level training objectives, develop scenarios and events in support of those training objectives, and will participate as exercise controllers, trusted agents, and leaders during exercise planning and execution.

3) Operate a distributed mission operations center to provide space modeling and simulation in support of approved training, exercise, test, experimentation, and mission rehearsal events. Plan and deliver modeling and simulation (M&S) capabilities to train joint warfighters on space capabilities and tactics, and prepare space warfighters for the integration of joint operating concepts during day-to-day operations.

4) . The 392 CTS uses a mixture of outside contractor-provided modeling and simulation (M&S) tools, White and Red cell support, and a professional exercise planning force to provide space operators with relevant, challenging threat scenarios. The scenarios challenge tactical operators and intelligence personnel with course of action (COA) development, vertical and horizontal communication problems with command and control (C2) decision-making authorities, and the development of innovative tactics, techniques, and procedures (TTP) within resource and time constraints. Challenges presented to the training audience include system degradations, operational limitations, and a variety of threats and attacks from a determined, thinking adversary. During the course of the exercise, space operators and intelligence personnel are able to collaborate and gain experience with repeated successes and failures based on outcomes of Red versus Blue player actions in a large-force employment exercise focused specifically on fighting within the space domain.

5) Provide advanced training (AT) to support the Weapons Instructors

Course (WIC) and Advanced Instructors Course (AIC). Identify improvements, M&S and Systems requirements and lessons learned for AT.

6) Having the USSF’s only JNTC capabilities, the 392 CTS is USSF’s representative on the Joint Staff/J7 (JS/J7) JNTC Corporate Board. The 392 CTS requires contractor support in the administration of the current USSF JNTC capabilities (DMOC-S and SF) at the 392 CTS and on the JS/J7 JNTC staff in Suffolk, VA.

2. APPLICABLE PERFORMANCE WORK STATEMENT (PWS)

PARAGRAPHS

This task order (TO) expands on or invokes the provisions of the following 3IS2 PWS paragraphs and all included subparagraphs: 1.3.2, 1.4.2, 1.4.4, 1.4.6.1.1.10, 1.4.6.1.1.18, and 1.5.14. Paragraphs not specifically referenced remain applicable to the scope of work performed under this task order.

3. SPECIFIC WORK TO BE PERFORMED

a. 392 CTS Operations Support (10) (16.7%)

1) Definition: The 392 CTS plans and delivers modeling and simulation (M&S) capabilities to train joint warfighters to be smart on space tactics and to prepare space warfighters for the integration of joint operating concepts during day-to-day operations. The M&S team operates the 392 CTS’s DMOC-S training architecture, a Joint National Training Capability (JNTC), which presents simulated space capabilities during select large and small force exercises, and uses terrestrial and satellite links to deliver simulated space effects to a pre-determined training audience.

a) The contractor shall operate existing and future M&S systems capabilities and architectures in support of advanced training, demonstrations, special event assessments, exercises, and real-world contingency operations.

The government shall provide training, funding and time to become proficient on new systems/capabilities, as appropriate, before requiring the contractor to operate future M&S systems capabilities. Flexible work schedules, including 24-hour/7-day operations, may be required periodically to support exercises, demonstrations, experiments and contingencies according to a mutually agreed upon schedule.

b) The contractor shall maintain detailed system expertise on all aspects of operating 392 CTS M&S and Command, Control, Computer and Communications (C4I) equipment. This includes Systems Administration support, as required, with no-earlier-than 7 working days’ notice of alternative schedule support. Shorter notice support will require mutual agreement between 12 Delta Operations Squadron (12 DOS), SPACE DELTA 12, and 392 CTS leadership. Support is estimated at being needed for no more than 25 days per year.

c) The contractor shall attend 392 CTS M&S related meetings in the local area, and at other locations as directed by the Government.

d) The contractor shall gather information, coordinate with key players internal and external to 392 CTS, and integrate inputs to support the execution of 392 CTS M&S activities.

e) The contractor shall establish liaisons with key M&S mission partners as required by the Government.

f) The contractor shall plan, develop, and deliver M&S training and exercise scenarios for all 392 CTS mission activities (including SPACE FLAG) and if necessary, plan, develop, and test the interface to other DMO domains.

This shall include the generation of virtual and constructive space effects that are synchronized with the scenario events.

g) The contractor shall execute 392 CTS mission activities by installing exercise-specific databases in 392 CTS M&S and C4I systems;

configuring the systems as required to operate on the exercise network;

monitoring the systems performance and making adjustments as required by changes in the scenario; and acting as exercise controllers/system experts.

h) The contractor shall control 392 CTS M&S exercise and event inputs in coordination with the exercise host’s exercise control groups (ECG).

i) The contractor shall be prepared to emulate Higher

Headquarters (HHQ) or other external organizations/agencies not participating in an event (white cell).

j) The contractor shall provide technical and communications support for new and emerging M&S capabilities provided by the government. The support shall include testing, coordinating and operating new and emerging M&S capabilities with designated mission partners. The government shall provide training, funding and time to become proficient on the applicable systems before requiring the contractor to operate new and emerging M&S systems capabilities.

k) The contactor shall provide full time 392 CTS M&S support to

Delta 5 (or as re-designated) at Vandenberg Space Force Base (SFB).

b. 392 CTS Professional Planning and Control Force (PPCF) (13) (21.7%)

1) Definition: The 392d CTS plans and executes large force employment exercises to prepare forces for combat. The Large Force Exercise (LFE) Team delivers training to CCMDs, Services, and Combat Support Agencies in order to prepare their warfighters for combat in a CDO space environment. Additionally, the 392 CTS LFE team leads the designing, planning, execution, and assessment of the new and emerging United States Space Force (USSF) service-level exercises (e.g., SPACE FLAG, POLARIS HAMMER and SKIES series of exercises).

2) USSF Service-Level Exercise Requirements:

a) The contractor shall design, develop, plan, execute, and assess

USSF service-level exercises in accordance with USSF’s Service Exercise Plan (SEP). This may include the synchronization of live, virtual, constructive (LVC) capabilities with scenario events. Flexible work schedules may be required to support LFE requirements.

b) The contractor shall provide cradle-to-grave exercise support by developing and executing a comprehensive and repeatable exercise life cycle and event planning process for USSF service-level exercises.

c) The contractor shall conduct planning conferences and working groups with training and exercise experts from SpOC and NRO units, HQ SpOC, 57/26 Space Aggressor Squadrons (SAS), NSDC, CSpOC, other

USSF Field Commands, AF Major Commands (MAJCOM), and other units/agencies (e.g., U.S. Army Space and Missile Defense Command / U.S.

Army Forces Strategic Command (SMDC/ARSTRAT), Space Test and Training Range (STTR), National Air and Space Intelligence Center (NASIC)) as required, to develop and provide realistic, comprehensive mission-related training environments based on current and near-future Red/Blue/Grey force capabilities. Scenarios within the training environment shall enable space warfighters to conduct mission rehearsals.

d) The contractor shall work with applicable units and agencies to develop scenarios and provide a master scenario events list (MSEL) to support USSF exercises.

e) The contractor shall facilitate USSF exercise event injects in coordination with the Exercise Director through the Exercise Control Group (ECG) and provide White Cell support to maintain control of the timing, tempo, and execution of the event to accomplish the desired training objectives. The contractor shall be prepared to emulate Higher Headquarters (HHQ) and/or other external organizations/agencies not participating in an event.

3) Non-USSF Exercise Requirements (e.g., CCMD, other Services, Combat Support Agencies):

a) The contractor shall develop, plan, and execute Space participation in Chairman of the Joint Chiefs of Staff (CJCS), Combatant Command (CCMD), and other service exercises, experiments and demonstrations as defined by the USSF Service Exercise Plan (SEP) and through the processes directed in Space Force Instruction (SFI) 10-204.

4) General Exercise Planning Requirements:

a) The contractor shall integrate Space and Cyber Special Access Program (SAP) Special Access Required (SAR) Advanced Program (AP) capabilities into CCMD, joint, service, and USSF exercises, as required.

b) The contactor shall provide a majority of effort for full time 392

CTS exercise support to Delta 5 (or as re-designated), and when available, provide 392 CTS exercise support to the Combined Force Space Component Command (CFSCC) (or as re-designated) at Vandenberg Space Force Base

(SFB).

c) The contractor shall develop schedules, plans and briefings;

coordinate/monitor activities, and report on those activities through trip reports, briefings, meeting minutes, etc.

d) The contractor shall participate during exercise execution as part of the exercise host’s ECG providing oversight, management and control of space and cyber events for the exercise.

e) The contractor shall plan exercises by gathering information, coordinating with key players internal/external to the 392 CTS and integrating their inputs (e.g., Provide and review information used by the government to create Task Management Tool tasks, sending and receiving emails, making and receiving phone calls, setting up and participating in video conferencing, setting up and participating in face-to-face communications, etc.); developing databases for the 392 CTS, M&S, and C4I systems; identifying exercise network and 392 CTS system requirements; and developing space-related scenario requirements and events (to include drafting scenario “ground truth documents” and Master Scenario Event Lists) to meet exercise and training objectives.

f) The contractor shall attend Joint Exercise Life Cycle events, and will aid in linking exercise host requests to USSF requirements.

g) The contractor shall provide trip reports within five (5) business days from end of conferences/meetings; a quick-look after action report (AAR) within three (3) business days after exercise execution; a final AAR no later than 30 calendar days from the end of each exercise; exercise readiness review (ERR) briefings 30 calendar days prior to the final planning conference;

and 10-day out briefs, as required.

h) The contractor shall respond to ad-hoc inquiries during normal business hours or as required by the government.

i) The contractor shall assist in the planning and execution of the annual and quarterly exercise coordination team (ECT) meetings by preparing and presenting exercise and advanced training planning and participation information for each scheduled exercise identified in the USSF SEP.

c. 392 CTS Maintenance and Sustainment (3) (5.0%)

1) Definition: The 392 CTS maintains the ability to connect with other development, experimentation and exercise centers to provide space M&S capabilities to warfighter through its operational training architecture known as the Distributed Mission Operations Center-Space (DMOC-S). The DMOC-S provides a realistic LVC environment integrating space capabilities and effects through advanced training, exercises, and mission rehearsal events. The intent of DMOC-S is to integrate USSF LVC systems with other warfighting systems to immerse the warfighter in realistic training environments. The robust infrastructure of the 392 CTS’ DMOC-S capability requires continuous oversight and management. This infrastructure includes communication systems, computer hardware and software.

a) The contractor shall maintain, sustain, and upgrade the 392 CTS DMOC-S computer (hardware, software, etc.) and communications infrastructure. This includes establishment and sustainment of the communications and computer architecture and the configuration requirements for each exercise, DMO, or advanced training event. The Government may authorize specialized training as required.

b) The contractor is responsible for upgrading configurations and all of the components for the DMOC-S infrastructure. During the upgrades of configuration objects, the contractor must assign a classification level to the object. As such, the contractor must exercise strict security discipline to ensure these objects are not mislabeled. Note: this labeling applies only to the configuration object, and not the data upon which the object will act.

c) The contractor is responsible for reviewing all DMOC-S configurations and configuration objects created, or modified, and confirming the activation of any configuration initiated by an operator.

d) The contractor shall ensure all required certification and accreditation processes are followed and completed.

e) The contractor shall collaborate with other Government and contractor teams that are supporting the 392 CTS’ DMOC-S development, primarily to accommodate data collection, obtain government-off-the-shelf (GOTs) technologies and leverage best practices, procedures and techniques.

f) The contractor shall provide necessary support to configure, integrate, test, operate, and troubleshoot 392 CTS equipment and infrastructure supporting exercises, experiments, demonstrations and training. Support may be required in 392 CTS and at TDY locations.

g) The contractor shall assist the 392 CTS in the identification and coordination of resource requirements for 392d CTS mission activities.

h) The contractor shall maintain and document current 392 CTS and MSDTE/JWICS network hardware and software, upgrade network infrastructure as needed to support current and future M&S systems, and coordinate infrastructure buildout/topology with 12 DOS to align network with modeling and simulation system requirements.

i) The contractor shall apply security patches and Special

Technical Implementation Guide (STIG) to maintain security posture of the network infrastructure. Supports Operations personnel during setup, execution, and teardown of exercise and training infrastructure (hardware and software).

j) The Contractor shall perform application loading, troubleshooting, tuning, and technical support for certain major applications in use by the 392 CTS within the 12 DOS. Applications currently include, but are not limited to: Automated Scriptor Simulator Exercise Trainer (ASSET), Combat Survivor Evader Locator (CSEL) Web Server Application Trainer (CWSAT), Distributed Information Warfare Constructive Environment (DICE), Missile Defense Space-Warning Tool (MDST), Joint Simulation Protocol Analyzer (JSPA), Global Positioning System (GPS) Environment Generator (GEG), Processing Display Subsystem-Migration (PDS-M) and Space-Based Infrared System Standard Space Trainer (SBIRS SST).

k) The contractor shall develop and maintain the 392 CTS

Configuration Management (CM) processes, build and configure the CM library, and enforce CM processes through the Configuration Management Plan (CMP).

l) The contractor shall track the licensing status of COTS technologies and recommend renewal options to the Government prior to expiration of any licensing agreements or end of life for hardware.

d. 392 CTS Project Management (2) (3.3%)

1) Definition: The 392d CTS develops strategic guidance, facilitates the Systems Implementation Process (SIP), supports administrative, budgetary, manpower, and programming functions and serves as the point of contact for coordination activities with external agencies. Additionally, the 392 CTS captures, analyzes, and shares information collected as a result of advanced training for the purpose of enhancing the combat readiness of warfighting forces. The 392 CTS lessons learned (L2) program discovers and validates observations, conducts an in-depth review to resolve observations, monitors and evaluates resolved observations, and disseminates lessons learned. For internal (i.e., USSF) lessons, the 392 CTS supports institutionalization of the lessons learned. For external lessons (non-USSF), the 392 CTS uses active (push) and passive (pull) methods to disseminate lessons to key mission partners.

a) The contractor shall assist in the development and revision/update of the 392 CTS Commander’s vision/mission statements and organizational strategy.

b) The contractor shall support, coordinate, and arrange semi-annual 392 CTS Strategic Planning conferences, when required by the government, to establish 392 CTS annual goal review and quarterly goal progress tracking.

c) The contractor shall develop, manage, and oversee the 392

CTS L2 Program. The contractor shall be responsible for organizational L2 training, the creation of a L2 repository, and assisting with gathering lessons from across the organization. The contractor shall conduct trend analysis. The contractor shall facilitate the L2 process, including conducting a regularly-held L2 Board. The contractor shall track lessons learned from cradle to grave, and monitor internal corrections within 392 CTS. The contractor shall provide a primary interface with HHQ L2 organizations ensuring 392 CTS L2 program is congruent with HHQ direction.

d) The contractor shall manage the System Implementation

Process (SIP) to ensure the proper tracking of SSC/STAO advanced training capabilities into 392 CTS Operations.

e) The contractor shall facilitate the transition of M&S requirements into technical solutions.

f) The contractor shall author, coordinate and staff all 392 CTS external agreements to include MOAs and MOUs. The contractor shall track ATO progress/status and inform the government of any changes/updates.

g) The contractor shall manage the 392 CTS CSRD process by assisting with creating, submitting, and tracking support requests. The contractor shall track CSRDs actively for 392 CTS from cradle-to-grave.

The contractor shall act as a liaison to 12 DOS, Space Delta 12 for their overall CSRD processes.

h) The contractor shall incorporate USSF, DAF and Joint policy, doctrine, guidance, concepts and other related material to ensure the 392 CTS mission is congruent with HHQ direction.

e. SPACE FLAG and Advanced Training Support (21) (34.8%)

1) Definition: The 392 CTS supports SpOC’s Ready Spacecrew Program

(RSP) by designing, planning, executing, and assessing SF exercises. These exercises (executed up to three times per fiscal year) focus on SpOC and NRO tactical operators and intelligence personnel as the primary training audience.

Each SF exercise integrates SpOC and NRO tactical space units in a large-force, space-for-space exercise, and allows crews the opportunity to utilize established TTPs and develop new and innovative TTPs to execute the space mission in a CDO environment. The 392 CTS creates the SF exercise environment by employing exercise control techniques and available Government or contractor systems (e.g., white cards, scripts, M&S) to replicate a combat representative space environment. The 392 CTS coordinates, plans, and develops event scenarios; defines intelligence support, M&S, opposing force, and communications requirements; develops, supports, participates in the exercise control architecture; and leads the White cell during event execution.

In addition to SF exercises, the 392 CTS supports unit-level Advanced

Training (AT) events utilizing organic 392 CTS M&S capabilities (e.g., the 392 CTS Battlelab) to meet specific unit-level training objectives. These small-scale AT events are highly-focused on specific SpOC Delta unit-level training objectives or tactical problems. AT is usually centered on individual units;

however, for very specific training objectives or mission rehearsal requirements, up to three units may be involved in one AT event.

Mission area expertise required for this task includes Space Domain

Awareness (SDA), Space Electronic Warfare (SEW), Missile Warning, Command and Control (C2), Cyber/Space Control Network (SCN), Intel Support, Satellite Communications (SATCOM), PNT (GPS), Orbital Warfare (OW), and National Reconnaissance Office (NRO). Additionally, this task requires program management; exercise planner expertise; orbital analysis; systems engineering;

operations assessment; information security management; and communications, administration, and logistics support. For SF and AT, the Government has the following requirements:

a) The contractor shall be well versed in SpOC and NRO space mission areas, command and control, space policy and doctrine, and space intelligence.

b) The contractor shall design, develop, plan, and execute up to three SF events in accordance with USSF’s Service Exercise Plan (SEP). This may include the synchronization of live, virtual, constructive (LVC) capabilities with scenario events. Flexible work schedules may be required to support SF requirements.

c) The contractor shall support up to 24 additional unit-level, tactical

AT events during each period of performance as approved by the Government during the annual and quarterly AT scheduling conferences.

d) The contractor shall provide cradle-to-grave exercise support by developing and executing a comprehensive and repeatable exercise life cycle and event planning process for SF exercises.

e) The contractor shall conduct planning conferences and working groups with training and exercise experts from SpOC and NRO space units, HQ SpOC, 527/26 Space Aggressor Squadrons (SAS), NSDC, CSpOC, other USSF

Field Commands, AF Major Commands (MAJCOM), and other units/agencies (e.g., U.S. Army Space and Missile Defense Command / U.S. Army Forces Strategic Command (SMDC/ARSTRAT), Space Test and Training Range (STTR), National Air and Space Intelligence Center (NASIC)) as required, to develop and provide realistic, comprehensive mission-related CDO training environments based on current and near-future Red/Blue/Grey force capabilities.

Scenarios within the training environment shall challenge unit-level TTPs and enable space warfighters to conduct mission rehearsals.

f) The contractor shall enlist the assistance of senior-level subject matter experts for SF planning and execution activities. The consultants hired under this task order shall not function as Highly Qualified Experts (HQEs) as defined by DoD Instruction 1400.25 Volume 922 (DoD Civilian Personnel Management System: Employment of Highly Qualified Experts (HQEs)).

Specifically, they shall not "provide expert experience-based mentoring, teaching, training, advice, and recommendations to senior military officers, staffs, and students" who participate in SF exercises. The consultants will advise the contractor team who will then implement their recommendations as appropriate and with Government approval.

g) The contractor shall work with applicable units and agencies to develop scenarios and provide a master scenario events list (MSEL) to support SF exercises.

h) The contractor shall plan for and integrate multiple Delta, Service, and/or Joint organizations into SF exercises and advanced training events by gathering information; coordinating with key players and stakeholders and integrating their inputs; identifying exercise network, system, and communications requirements; and developing space-related scenario requirements and events to meet the training objectives of the primary training audiences.

i) The contractor shall integrate Special Access Program/Security Access Required (SAP/SAR) capabilities into SF exercises and AT events, as required.

j) The contractor shall provide 392 CTS SF/AT Liaison Officers

(LNOs) associated with Deltas 2, 3, 4, 7, 8, 9, C2 (which includes Delta 5 and NSDC), and NRO. These LNOs will spend the majority of their effort preparing their respective units for planning and participation in SF events and exercises.

Their secondary weight of effort will be in support of unit AT events (e.g., Ready Spacecrew Program (RSP) Advanced Training Measures (RAMs), utilizing the 392 CTS Battelab, or other Government-specific M&S capabilities), and identification of unit specific SF/AT requirements.

k) The contractor shall facilitate SF exercise and AT event injects in coordination with the Exercise Director through the Exercise Control Group

(ECG) and provide White Cell support to maintain control of the timing, tempo, and execution of the event to accomplish the desired TOs. The contractor shall be prepared to emulate Higher Headquarters (HHQ) and/or other external organizations/agencies not participating in an event.

l) The contractor shall conduct hot wash/debriefings with training audiences and senior leadership, as required.

m) The contractor shall conduct in-depth analysis on the results of SF events through the use of quantitative and qualitative methods (e.g., SF assessments, surveys, and data analysis). The analysis will 1) identify opportunities for SF improvements; 2) inform USSF’s operations, training, and acquisition processes; and 3) facilitate SF requirements generation for USSF’s future dedicated advanced training capability.

n) The contractor shall provide SF/AT findings, observations, recommendations, and reports with the 392 CTS Lessons Learned (L2) and the broader Lessons Learned community, as applicable.

o) The contractor will provide a SF AAR in accordance with Air Force

Instruction (AFI) 90-1601 (or the applicable Space Force Instruction when approved).

p) The contractor shall coordinate testing of Government and/or contracted M&S capabilities involved in the exercise.

q) The contractor shall develop schedules, plans, and briefings;

coordinate and monitor activities; and report on those activities through trip reports, briefings, meeting minutes, point papers, quad charts, etc.

r) The contractor shall coordinate manning support with the units, Deltas, and HQ SpOC POCs, as applicable, for each SF exercise.

s) The contractor shall assist SpOC with the identification and coordination of resource requirements for individual SF exercises and Delta unit-level AT events.

t) The contractor shall conduct annual and quarterly 392 CTS AT scheduling meetings to schedule, deconflict, and prioritize SpOC Delta AT requirements, and manage 392 CTS AT resources and personnel resources effectively.

u) The contractor shall participate in USSF’s annual and quarterly exercise coordination team (ECT) meetings by preparing and presenting SF planning and execution information for each scheduled SF exercise identified in USSF’s SEP.

v) The contractor shall attend SF/AT related meetings in support of the Government and establish liaisons with key internal and external stakeholders supporting SF/AT events. The contractor shall collaborate with these stakeholders primarily to accommodate data and information collection, obtain government-off-the-shelf (GOTS) technologies (as directed), leverage best practices, procedures, and techniques, and integrate inputs to support execution of SF exercises and AT events.

w) The contractor shall manage and implement the 392 CTS SF

Information Security Program to ensure compliance with the DoD Information Security Program’s policies and procedures.

x) The contractor shall act as the principle advisor to the SF Exercise

Director on SF/AT information security matters.

y) The contractor shall coordinate with internal and external Government and contractor leads to establish, implement, and enforce security requirements during SF/AT conferences, working groups, and exercises.

f. SF/AT Future Capabilities Identification and Development (1) (1.7%)

1) Definition: A current LIMFAC for advancing USSF’s SF exercise is the lack of a dedicated advanced training capability. The current contractor-owned/operated capability meets the minimum requirements to provide a SF exercise; however, SF is not the contractor’s primary focus, and the current capability constrains the exercise’s ability to meet large-force employment training requirements. Therefore, the development of a dedicated capability supporting USSF’s Space Flag is required to replicate a realistic warfighting environment. This dedicated capability is critical to meeting USSF’s requirement to shift space operators’ mindsets from one focused on weapon system procedural currency to a warfighting mentality of executing space operations in a CDO environment. Due to limited manpower resources within 392 CTS, the Government requires the contractor to help identify, develop, advocate, and integrate SF/AT requirements into USSF’s future dedicated advanced training capability.

a) The contractor shall be familiar with applicable Space Delta training requirements and equipment, and assist in identifying and translating training audience SF/AT requirements into recommended technical approaches.

b) The contractor shall provide technical assistance for documenting, analyzing, tracing, and prioritizing SF/AT requirements.

c) The contractor shall support the Government by attending product and process integration meetings, technical interchange meetings, in-progress reviews, programmatic-level meetings, etc. related to SF/AT activities and the creation of a long-term dedicated capability.

d) The contractor shall provide technical support to the Government during applicable demonstrations, tests, evaluations, and/or special event assessments involving existing/new space M&S and simulator systems to determine relevancy, feasibility, and usefulness to SF/AT.

g. 392 CTS JNTC Liaison Officer Support at Joint Staff/J7 Suffolk, VA (1)

(1.7%)

1) Definition: Provide liaison officer support (LNO) to Joint Staff/J7 JNTC on-site at Joint Staff Suffolk Complex, 116 Lake View Parkway, Suffolk, VA, 23434-2697 to represent 392 CTS and USSF interests at JNTC meetings, conferences, working groups. This includes, but is not limited to, attending meetings, briefings, and conferences concerning Training Transformation (T2);

and coordinating with JNTC organizations, USSF Field Commands, JS/J7, and other JNTC stakeholder Service liaisons to socialize USSF issues, concerns, and equities and to explore potentially mutually beneficial courses of action.

a) The contractor shall coordinate and advocate for the inclusion of USSF and 392 CTS inputs into the Combatant Commander Exercise Engagement and Training Transformation (CE2T2) Program Execution Plan (PEP) development throughout the JS/J7 coordination process.

b) The contractor shall participate in the annual JNTC PEP Budget Request (PBR) working group, and support the 392 CTS JNTC PBR Unfunded Requirements (UFR) process. This support includes, but is not limited to, participating in discussions regarding PBRs proposed by USSF Field Commands and USSF-sponsored accredited programs and certified sites. Additionally, the contractor shall review, critique, and suggest improvements to submitted USSF and 392 CTS PBRs; brief USSF technical PBRs during JS/J7-led technical reviews; and socialize potential benefits of USSF-sponsored programs and sites to other stakeholder programs and/or the JNTC enterprise.

c) The contractor shall participate in Joint Investment Database (JIDB) improvement events, and populate the JIDB with applicable USSF PBR information.

d) The contractor shall review T2 technical directions, decisions, and technical elements of proposed projects and actions for validity and impact to USSF training capabilities and develop recommendations for USSF responses.

e) The contractor shall provide USSF Subject Matter Expert (SME) support to the JS/J7 Service Joint Training Division (SJTD) Joint Accreditation, Certification and Mitigation (ACM) Program.

f) The contractor shall attend USSF-related ACM meetings and establish liaisons with key Service and Joint stakeholders to integrate USSF programs with other Service and Joint programs.

g) The contractor shall coordinate with the 392 CTS, JS/J7 SJTD, and

USSF-sponsored programs and sites to schedule periodic re-accreditations and re-certifications.

h) The contractor shall compile and annotate mitigation efforts raised through the accreditation and certification processes of USSF sites and training programs.

i) The contractor shall provide USSF-approved inputs to SJTD responses to Congressional and higher headquarters inquiries; participate in SJTD program issue mitigation in-process reviews for USSF-sponsored sites and programs; review USSF self-assessments; establish an ongoing dialogue with program counterparts; participate in discussions to identify specific shortfalls and their impacts on the USSF program’s ability to train on joint tasks; write issue sheets for accreditation reports of USSF programs, and coordinate the issue sheet refinement with program counterparts.

j) The contractor shall support USSF JNTC Corporate Board (CB) participation before, during, and after JNTC CB meetings.

k) The contractor shall develop schedules, plans, and briefings;

h. 392 CTS JNTC Program Support at Schriever SFB, CO (1) (1.7%)

1) Definition: Provide day-to-day JNTC administrative and managerial support to the 392 CTS at Schriever SFB, CO. Needed support includes administering and managing the 392 CTS’s JNTC ACM requirements, assisting with the 392 CTS’s PBR process and requests, participating in the Joint Training Coordination Program (JTCP) working groups, and coordinating with JNTC program stakeholders.

a) The contractor shall support the administration of the 392 CTS’s

JNTC program.

b) The contractor shall provide JNTC ACM SME support to the 392 CTS for the JNTC accredited program (SF) and the certified site (DMOC-S).

c) The contractor shall assist the 392 CTS with development of JNTC

PBR requests to include PBR UFRs; participate as an USSF SME in the PBR

Technical working group; and provide recommendations and feedback to the 392 CTS during PBR development.

d) The contractor shall gather, compile, analyze, and report PBR measures of effectiveness on USSF JNTC capabilities to determine PBR effectiveness in mitigating Joint capability gaps and seams in accordance with standards outlined in the PEP.

e) The contractor shall participate in the JTCP working groups and periodic conferences to coordinate 392 CTS and USSF input into exercise support, and to identify complementary training requirements for other Service participation.

f) The contractor shall support preparation of the 392 CTS JTCP budget submission by coordinating with USSF stakeholders to collect and compile fiscal year JTCP operational and financial requirements.

g) The contractor shall monitor the 392 CTS portion of the JS/J7 JTCP database for changes (e.g., changes in the ability of Joint Forces support to USSF exercises), and update government-provided actual cost data in the database at the conclusion of each exercise.

h) The contractor shall participate in monthly multi-service Joint

Assessment Enabling Capability (JAEC) meetings. To support these meetings, the contractor shall gather, compile, analyze, and report PBR measures of effectiveness on USSF JNTC capabilities to determine PBR effectiveness in mitigating Joint capability gaps and seams in accordance with standards outlined in the PEP.

i) The contractor will review JNTC technical directions, decisions, and technical elements of proposed projects and actions for validity and impact to 392 CTS training capabilities, and will develop and provide recommended 392 CTS responses.

j) The contractor shall analyze Congressional proposals, Department of Defense guidance, policies, directives, and changes in resource requirements, and assesses potential operational impacts to 392 CTS accredited and certified programs.

k) The contractor shall maintain 392 CTS inputs to the JIDB for JNTC-approved USSF accredited programs and certified sites.

l) The contractor shall develop schedules, plans, and briefings;

i. Operating and Enhancing the 392 CTS BattleLab (3) (5.0%)

1) Definition: For the near term (FY22-FY24), the 392 CTS will execute USSF exercises using 392 CTS M&S Enclave capabilities. The BattleLab portion of the enclave requires specialized skills (e.g., orbital analysis, STK software enhancements, and STK operational experience) to create STK-based orbital and terrestrial models, build scenarios, and operate the BattleLab. Additionally, the current BattleLab capability requires enhancements to increase efficiencies, reduce White Cell manning requirements, and transition to a server-based application.

a) The contractor shall provide an orbital analyst well versed in STK capabilities to plan, develop, and deliver BattleLab training and exercise scenarios required to support PH, SKIES, and SFEs requiring BattleLab capabilities. When requested, the contractor shall augment BattleLab-based SF exercise scenario builds, rehearsal of concept (ROC) drills, and executions.

Flexible work schedules, including 24-hour/7-day operations, may be required periodically to support exercises according to a mutually agreed upon schedule.

b) The contractor shall establish liaisons with STK software developers to maintain detailed system expertise on operating the current (FY22) BattleLab configuration and capabilities. The contractor shall also identify, prioritize, develop, and make capability enhancements to the existing BattleLab software engine (i.e., STK commercial software). In the event the BattleLab has a major update (e.g., software revisions or transition to a server-based capability), the government shall provide training, funding, and time to become proficient on new BattleLab capabilities before requiring the contractor to operate BattleLab upgrades.

c) The contractor shall gather information, coordinate with key players internal and external to 392 CTS, and integrate inputs to support the operation and development of the BattleLab. This includes, but is not limited to, attending product and process integration meetings, technical interchange meetings, in-progress reviews, etc. related to BattleLab activities and the creation of a long-term dedicated stand-alone solution.

d) The contractor shall execute PH, SKIES, and SFE activities by creating orbital and terrestrial models using internal BattleLab software;

installing exercise-specific databases in the BattleLab systems; configuring the systems as required to operate on appropriate network(s); monitoring the systems performance and making adjustments as required by changes in the scenario; and acting as exercise controllers/system experts.

j. Server-based and Dedicated Stand-alone BattleLab Capabilities (4) (6.7%)

1) Definition: In order to realize resource and manpower savings and minimize risk of security policy restrictions, the 392 CTS requires (1) a server-based BattleLab capability, and (2) development of a dedicated stand-alone BattleLab capability to allow participation of Coalition members in USSF exercises (e.g., SF, PH, SKIES).

a) The contractor shall investigate the feasibility, costs, and timelines associated with implementing a server-based JWICS BattleLab capability and a dedicated stand-alone coalition-capable BattleLab capability. The contractor shall present their findings to the Government no later than six (6) months from award of this task order (i.e., 392 CTS Exercise Support). Upon Government approval of the accepted course of action and any additional funding needed to purchase hardware, software, licenses, etc. the contractor shall plan, design, build, and support accreditation for a server-based BattleLab capability, and a dedicated stand-alone Coalition-capable BattleLab capability.

b) The contractor shall provide IT support in the design, accreditation, and maintenance of the BattleLab networks (i.e., JWICS-based offline BattleLab, JWICS server-based BattleLab, dedicated stand-alone BattleLab network) for use by SF, PH, SKIES, and SFE exercises and events in accordance with functional specifications.

c) The contractor shall provide systems administration to the accredited BattleLab networks, which includes, but is not limited to, the required versions of Microsoft (MS) Active Directory (AD). Microsoft services will include IIS and SharePoint web servers, MS SQL, MS Exchange, Windows Security Update Services, and Group Policy administration.

d) The contractor shall provide administration and maintenance of the dedicated stand-alone BattleLab networks. System Administrators shall identify, troubleshoot, and restore network (and server and client systems when implemented) outages when they occur or as required during supported PH, SKIES, or SF events. The requirement to manage the BattleLab and dedicated stand-alone systems (hardware and software) includes the creation and maintenance of system accreditation artifacts through the required accreditation lifecycle processes. This support shall apply to the BattleLab (offline mode and server-based applications) and to dedicated stand-alone BattleLab systems.

e) Network Engineering shall provide expertise for planning facility layout, network architecture, and implementation of the BattleLab and dedicated stand-alone systems infrastructure held in Building 24 on Schriever SFB.

f) The contractor shall maintain, sustain, and upgrade the

BattleLab (hardware, software, etc.) infrastructure. This includes establishment and sustainment of the computer architecture and the configuration requirements for each exercise or advanced training event.

g) The contractor shall ensure required certification and accreditation processes are followed and completed.

h) The contractor shall provide necessary support to configure, integrate, test, operate, and troubleshoot BattleLab equipment and infrastructure supporting USSF exercises and advanced training.

i) The contractor shall maintain and document current BattleLab network hardware and software, upgrade network infrastructure as needed to support current and future USSF M&S systems, and coordinate infrastructure buildout/topology with 12 DOS to align network with BattleLab system requirements.

j) The contractor shall apply security patches and Special

Technical Implementation Guide (STIG) to maintain security posture of the BattleLab infrastructure.

k) The Contractor shall perform application loading, troubleshooting, tuning, and technical support for software applications in use by the BattleLab.

l) The contractor shall track the licensing status of BattleLab technologies and recommend renewal options to the Government prior to expiration of any licensing agreements or end of life for hardware.

k. Administrative/Logistics Support (1) (1.7%)

1) Definition: Administrative and logistics support is needed for non-SF

USSF exercises (e.g., PH, SKIES, SFE events). (Note: SF administration and logistics is covered in a separate task order, however this administration and logistics support may be required to augment SF exercises if the workload warrants.)

a) The contractor shall provide draft invitations and read-ahead documentation as applicable for key PH, SKIES, or SFE events for Government review and signature. Once the invitations and read-ahead documentation are approved and signed, the contractor shall e-mail them to the appropriate organizations and personnel. Invitations and read-ahead documentation are normally sent to recipients 45 to 60 days prior to the event.

b) The contractor shall provide the following for PH, SKIES, and SFE events: support to Space Training and Readiness Command (STARCOM) protocol (as needed for DV Day); participant registration information and clearance list; attendance rosters; and administrative logistics (e.g., administrative supplies and Building 24 coordination).

c) The contractor shall provide inputs for STARCOM Public Affairs

(PA) press releases related to USSF and other non-SF (e.g., CCMD, Service, Joint) exercises the 392 CTS supports.

d) The contractor shall review and internally coordinate meeting minutes, after action reports (AARs), and trip reports for PH, SKIES, and SFE events.

e) The contractor shall provide SharePoint management (i.e., posting documents, references, and specific exercise information) for PH, SKIES, and SFE events.

f) The contractor shall augment the Government’s qualified security lead with security and badging support for PH, SKIES, and SFE events when requested by the Government.

4. REQUIRED TRAVEL

Contractor TDY travel shall be required in conjunction with performance of this task proposal request (TPR). The Government Contracting Officer’s Representative (COR) shall approve contractor travel. All costs associated with travel shall be proposed at the subtask level. Required travel is listed in attachment (A) of this TPR.

5. OTHER DIRECT COSTS (ODC)

The contractor shall propose any necessary ODC required. The Government PM and Contracting Officer (CO) shall approve all TO ODCs prior to purchase.

Required ODCs are listed in attachment (B) of this TPR. The Government shall furnish or make available to the contractor any training necessary to accomplish the task as mutually agreed upon between the Government and the contractor.

6. DATA RIGHTS

Pursuant to the contract, the Government has unlimited rights to all deliverables of this TO. The Government shall obtain custody of all records associated with contractor deliverables and shall have exclusive control in the distribution of all products and services provided and/or developed by the contractor.

7. DELIVERABLES

a. Scientific and Technical Reports, A009, as required

1) Provide exercise planning process artifacts (planning process job aids, schedules, manning document, phone roster, MSEL, etc.).

2) Provide a comprehensive SF AAR within 30 days from the end of each SF execution.

3) Prepare, disseminate, and archive Lessons Learned in appropriate repositories.

4) Prepare and submit trip reports/meeting minutes within 5 working days after the end of a TDY or scheduled planning conference or working group.

5) Provide status update briefings within 5 working days of Government request.

6) Provide exercise readiness review (ERR) briefings 30 days prior to SF exercise execution.

7) Prepare and submit trip reports or meeting minutes within 5 working days after the end of a TDY, meeting, scheduled planning conference, working group.

8) Provide status update briefings within 5 working days of Government request.

b. Computer Software Products, A007, as required

c. Software Product Specification, A006, as required

Deliverables shall be provided according to contract data requirements list (CDRL) instructions or to a mutually agreed upon schedule.

8. SECURITY INSTRUCTIONS

The…