3IS III_Atch 1_PWS_v7.0.pdf

RFP# FA2518-23-R-0007

Attachment 1, 3IS III PWS

UNITED STATES SPACE FORCE (USSF)

SPACE DELTA 12 (DEL 12)

Schriever SFB, Colorado

Innovation, Integration, and Information Support (3IS) III

Performance Work Statement (PWS)

09 February 2023

TABLE OF CONTENTS

Paragraph # Title Page #

1 SECTION A – DESCRIPTION OF SERVICES 4

1.1 ORGANIZATION(S) SUPPORTED 4

1.2 PLACE OF PERFORMANCE 4

1.3 MISSION 5

1.3.1 STARCOM Space Delta 12 (DEL 12) and 12th Delta Operations Squadron (12 DOS) 5

1.3.2 1st Test and Evaluation Squadron (1 TES) 5

1.3.3 3rd Test and Evaluation (3 TES) 6

1.3.4 4th Test and Evaluation Squadron (4 TES) 6

1.3.5 17th Test and Evaluation Squadron (17 TES) and 14th Test Squadron (14 TS) 6

1.3.6 STARCOM Space Delta 11 (DEL 11) 6

1.3.7 25th Space Range Squadron (25 SRS) and 379 SRS 7

1.3.8 527th Space Aggressors Squadrons (527 SAS) and 26 SAS 7

1.3.9 57th Space Aggressor Squadron (57 SAS) 7

1.3.10 98th Space Range Squadron (98 SRS) 7

1.3.11 STARCOM Space Delta 10 (DEL 10), OL-B (STARCOM Wargaming) 7

1.3.12 STARCOM Space Delta 1 (DEL 1), 392d Combat Training Squadron (392 CTS) 8

1.3.13 Other Supported Organizations 9

1.4 DESCRIPTION OF SERVICES/SPECIFIC REQUIREMENTS 9

1.4.1 Security Requirements 9

1.4.2 Program Management, Administrative, Security, Personnel, Logistics and Other

Support

1.4.3 392 CTS Support 13

1.4.4 Test and Evaluation Support 15

1.4.5 Information Technology Support 18

1.4.6 STARCOM Wargaming Support 26

1.5 GENERAL INFORMATION 27

1.5.1 Contract Performance Management 27

1.5.2 Authorized Technical Direction 27

1.5.3 Contractor Employees 27

1.5.4 Access to Government Facilities 28

1.5.5 Exercises 28

1.5.6 Other Direct Costs (ODCs) 28

1.5.7 Contract Information Management 28

1.5.8 Environmental and Hazardous Materials (HAZMAT) 28

1.5.9 HAZMAT Management 29

1.5.10 Federal, State, and Local Laws 29

1.5.11 Contractor Program Manager (CPM) 29

1.5.12 Quality Assurance 30

1.5.13 Safety 31

1.5.14 Security 31

1.5.15 Contractor Manpower Reporting 35

1.5.16 Antiterrorism 35

1.5.17 General Information Training 35

1.5.18 Base Delay/Closure 36

2 SECTION B – SERVICES SUMMARY (SS) 37

3 SECTION C – GOVERNMENT FURNISHED PROPERTY AND SERVICES 38

3.1 Government Furnished Resources 38

3.2 Government Furnished Facilities 38

3.3 Government Furnished Equipment 38

3.4 Office Electronic Equipment 38

3.5 Government Furnished Services 38

4 SECTION D – APPENDICES 39

4.1 Appendix A – Status of Forces Agreement (SOFA) – Korea 39

4.2 Appendix B – Acronyms 43

4.3 Appendix C – Publications 48

4.4 Appendix D - CDRLs 52

4.5 Appendix E – Modeling and Simulation Tools 54

1 SECTION A - DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1 ORGANIZATION(S) SUPPORTED

The contract will primarily support Space Delta 12 (DEL 12) and its subordinate units (12 Delta Operations Squadron [12 DOS], 1st Test and Evaluation Squadron [1 TES], 3rd Test and Evaluation Squadron [3 TES], 4th Test and Evaluation Squadron [4 TES], 17th Test and Evaluation Squadron [17 TES] and 14th Test Squadron [14 TS]);

Space Delta 1’s, 392 Combat Training Squadron (392 CTS); Space Delta 10, OL-B (STARCOM Wargaming);

Space Delta 11’s Aggressor and Range squadrons ( 527th Space Aggressor Squadron [527 SAS], 57th Space Aggressor Squadron [57 SAS], 25th Space Range Squadron [25 SRS], and 98th Space Range Squadron [98 SRS];

and other mission partners including USSPACECOM and Space Systems Command (SSC) elements

1.2 PLACE OF PERFORMANCE

1.2.1 The primary workplace for the effort will be the Government designated facilities at Schriever SFB Colorado, the Front Range area, and geographically separated units (GSUs) at the following locations:

1.2.1.1 Buckley SFB, CO

1.2.1.2 Vandenberg SFB, CA

1.2.1.3 Cheyenne Mountain Space Force Station (SFS), CO

1.2.1.4 Colorado Springs, CO

1.2.1.5 Peterson SFB, CO

1.2.1.6 Aurora, CO

1.2.1.7 Boulder, CO

1.2.1.8 Suffolk, VA

1.2.1.9 Patrick SFB, FL

1.2.10 Kirtland AFB, NM

1.2.11 Edwards AFB, CA

1.2.12 Los Angeles AFB, CA

1.2.2 Travel

1.2.2.1 General: Travel may be required inside the continental United States (CONUS) and outside the continental United States (OCONUS) on a temporary basis to accomplish the mission. All travel will be at the direction of the Government and reimbursed/accounted for as part of the other direct costs (ODC) contract line item number (CLIN) (see paragraph 1.5.6). Contractors supporting OCONUS activities must obtain passports immediately upon hiring and ensure passports remain valid throughout the life of the contract. Approximate number of OCONUS travel days will be identified at the task order level.

1.2.2.2 Foreign Clearance Manual: All contractor travel shall be considered to be "DoD-sponsored" and will comply with the requirements found in the DoD Foreign Clearance Manual (FCM) and associated country-specific requirements in the electronic Foreign Clearance Guide eFCG).

1.2.2.2.1 The Government shall notify the contractor of a travel requirement no later than the eFCG-specified lead time (which vary by country and are normally found in Section III.D of each country's requirements) plus seven days (to allow for contractor preparation and submission of the associated eFCG requirements. While travel within the above timeframe (eFCG lead time plus seven days) is possible, the Government shall both assist the contractor as required with eFCG requirements (submitting eFCG-required justification or coordinating with travel approving officials) and assume the risk of the contractor not being able to travel if eFCG approval is not received prior to departure.

1.2.2.3 Sensitive Compartmented Information (SCI) cleared contractors: Contractors with SCI access who plan official or unofficial foreign travel shall comply with the provisions of DoDM 5105.21-V3, AFMAN14-304 and AFI71-101 and shall:

1.2.2.3.1 Report anticipated foreign travel to their contractor supervisor and the supporting Special Security Representative (SSR). The SSR shall coordinate JPAS reporting requirements per AFMAN14-304.

1.2.2.3.2 Upon completion of travel, contact AFOSI to schedule a debriefing per AFI71-101V4.

1.2.2.3.3 Obtain pre-travel briefings as identified by the supporting SSR.

1.2.2.3.4 Report any unusual incidents occurring during travel to the supporting SSR within 48 hours of return.

1.2.2.4 Special Access Programs (SAP) travel: SAP-accessed contractor personnel shall comply with the reporting requirements of Enclosure 5 to DoDM 5205.07-V2, to include pre- and post-travel reporting of both official- and non-official travel.

1.2.2.5 Synchronized Pre-deployment & Operational Tracker (SPOT). Travel under the SPOT program shall be allowed in support of contingencies, humanitarian assistance, disaster recovery operations, and other military operations or military exercises and shall be per the "DoD Business Rules for the Synchronized Pre-deployment and Operational Tracker (SPOT)" and further instructions within (which are incorporated by reference).

1.3 MISSION

1.3.1 STARCOM Space Delta 12 (DEL 12) and 12th Delta Operations Squadron (12 DOS), Schriever SFB, Colorado

1.3.1.1 DEL 12 prepares USSF forces to prevail in a contested, degraded, and operationally-limited environment through the independent test and evaluation of USSF capabilities and delivery of timely, accurate, and expert information in support of weapon system acquisition, operational acceptance, and readiness decisions.

1.3.1.2 The 12 DOS mission is to manage the cross-disciplinary processes to produce test and evaluation information for weapon system acquisition, operational acceptance, and readiness decisions to enhance space warfighting capabilities. 12 DOS manages all infrastructure and resource management functions to include command, control, communications, computers, & intelligence (C4I) architecture, information technology equipment custodian (ITEC), assessment and authorization, budget, manpower, personnel, deployments, training, facility management, finance, contracting and logistics for DEL 12. Additionally, 12 DOS manages execution of the Weapons System Evaluation Program activities on behalf of DEL 12.

1.3.2 1st Test and Evaluation Squadron (1 TES) Schriever SFB, Colorado

The 1 TES prepares USSF forces to prevail in a contested, degraded, and operationally-limited environment through the independent test and evaluation of operational-level command and control technologies and the delivery of timely, accurate, and expert information in support of weapon system acquisition, operational acceptance, and readiness decisions.

1.3.3 3rd Test and Evaluation Squadron (3 TES) Schriever SFB, Colorado

3 TES’s mission is to build test capabilities and execute integrated test and experimentation to preserve and protect freedom of maneuver to, through, and from space – deliver tactical capabilities with strategic implications. 3 TES prepares USSF forces to prevail in a contested, degraded, and operationally-limited environment through the independent test and evaluation of orbital warfare technologies and the delivery of timely, accurate, and expert information in support of weapon system acquisition, operational acceptance, and readiness decisions. 3 TES conducts independent experimentation, developmental test, operational test, and tactics development for orbital warfare systems including early involvement, planning, execution, data collection, data analysis, and reporting.

1.3.4 4th Test and Evaluation Squadron (4 TES) Peterson SFB, Colorado

1.3.4.1 Mission: Test and evaluate new space spectrum and electronic warfare related space system, missile, and missile defense capabilities in operationally realistic environments to inform warfighters and influence national resource decisions. 4 TES prepares USSF forces to prevail in a contested, degraded, and operationally-limited environment through the independent test and evaluation electromagnetic spectrum technologies and the delivery of timely, accurate, and expert information in support of weapon system acquisition, operational acceptance, and readiness decisions.

1.3.5 17th Test and Evaluation Squadron (17 TES) and 14th Test Squadron (14 TS) Schriever SFB, Colorado

1.3.5.1 The 17 TES, Schriever SFB, CO; 17 TES Det 1, Buckley SFB CO, and the 14th Test Squadron (14 TS), Schriever SFB, CO perform all aspects of test screening, test planning, test execution, test analysis, test reporting and test closeout for, mainly, space domain awareness, missile defense, and missile warning operational tests and for possible developmental tests. The 17 TES conducts DOT&E oversight and sustainment & modernization force development evaluations (FDEs), operational utility evaluations (OUEs), initial operational test & evaluations (IOT&Es), follow-on operational test and evaluations (FOT&Es), qualification operational test and evaluations (QOT&Es), operational assessments (OAs), early operational assessments (EOAs), military utility assessments (MUAs), multi-Service operational test and evaluations (MOT&Es), weapons system evaluation programs (WSEPs), sufficiency of operational test reviews (SOTRs), capabilities & limitations reports (C&LRs), military utility assessments (MUAs), command-directed testing, tactics validations, and tactics development and evaluations (TD&Es) of space forces mainly in support of Headquarters (HQ) USSF and to a much lesser extent other Services such as USAF space-related operational testing.

1.3.5.2 The 17 TES seeks to enhance the military utility of space power through the Operational Test and Evaluation (OT&E) and Developmental Test & Evaluation (DT&E) of space systems. The 17 TES determines the operational capabilities and limitations of space systems as they relate to enhancing warfighting operations.

1.3.5.3 The 17 TES provides operational effectiveness and suitability evaluations from the initial employment of operational systems (oversight testing), through evolutionary tactics development, modernization, and sustainment upgrades. The 17 TES will maximize test efficiency through integrated test efforts.

1.3.5.4 The 17 TES core competencies are OT&E/DT&E, system expertise, test and evaluation proficiency, statistical analytical expertise, and test support capabilities. The 17 TES also depends on extensive teaming with program offices, operators, and weapon system leads to produce the best possible test products for senior decision makers.

1.3.6 STARCOM Space Delta 11 (DEL 11), Schriever SFB, Colorado

DEL 11’s mission is to deliver realistic, threat-informed test and training environments through the provision of live, virtual, and constructive range and combat replication capability in order to prepare U.S. Space Force, Joint, and allied forces to prevail in contested and degraded operationally-limited space environments.

1.3.7 25th Space Range Squadron (25 SRS) and 379 SRS, Schriever SFB, Colorado

1.3.7.1 Mission: The 25 SRS and 379 SRS operate the Department of Defense's only Space Test and Training Range, providing customers with a safe and secure environment to support space control technique development and space test, training and exercise activities. The units also provide a timely, relevant and integrated space environment and effective mission planning, execution integration across all domains, and formalize STTR processes.

1.3.8 527th Space Aggressors Squadrons (527 SAS) and 26 SAS, Schriever SFB, Colorado

1.3.8.1 The mission of the 527th and 26th SAS is to prepare joint forces and coalition partners to fight in and through contested space environments by analyzing, teaching, and replicating realistic, relevant, and integrated space threats. The Space Aggressors execute their advanced training charter across two mission areas: Adversary Threat Academics and Adversary Threat Replication. Adversary Threat Academics focuses on the development of tailored instruction on adversary capabilities, tactics, techniques, and procedures, doctrine, and employment methodologies. Adversary Threat Replication focuses on the live, virtual, and constructive replication of threats across four mission sets: Global Positioning System (GPS) electronic attack (EA), satellite communication (SATCOM) EA, adversary SATCOM network replication, and “in-domain” orbital warfare threat replication.

1.3.8.2 The 26th SAS is a Reserve associate unit to the 527 SAS in a total force integration partnership. Both squadrons are co-located in Buildings 24 and 815. Support required includes, but is not limited to: IETC configuration management, hardware and software maintenance support, certification and accreditation support, system security, information assurance officer (IAO), sensitive compartmented information facility (SCIF) oversight, notice to airmen (NOTAM), information assurance vulnerability assessment (IAVA) monitoring, implementation and reporting as well as developing and documenting repeatable processes and procedures. These requirements are needed both within Buildings 24 and 815.

1.3.9 57th Space Aggressor Squadron (57 SAS), Schriever SFB, Colorado

1.3.9.1 The 57 SAS mission is to instill an adversary-focused warfighting culture by knowing, teaching, and replicating modern, emerging, and integrated space threats via adversary threat academics and virtual/live replication of adversary space and counterspace threats. The 57 SAS executes their mission in order to develop Guardians to prevail in competition and ultimately prepare a combat-credible Joint Force to deter war, and should deterrence fail, to fight and win our Nation’s wars in, from, and to space.

1.3.10 98th Space Range Squadron (98 SRS), Schriever SFB, Colorado

1.3.10.1 Mission: The 98 SRS Provides a safe, secure, operationally-representative live on-orbit test and training environment to develop lethal, agile, and resilient joint warfighters. The Orbital Warfare Range of the National Space Test and Training Complex (NSTTC) provides Space Domain Awareness, Time Space Position Information data, safety of flight, and security in support of training, test, and experimentation activities for the USSF and designated partners.

1.3.11 STARCOM Space Delta 10 (DEL 10), OL-B (STARCOM Wargaming), Schriever SFB, Colorado

1.3.11.1 STARCOM Wargaming manages the USSF Chief of Space Operations (CSO) Schriever Wargame and other associated wargame events. This includes support to US Code (USC) Title 10, Title 50, Office of the Assistant Secretary of Defense for Space Policy (ASD(SP)), USSF, and other identified wargames (approximately 16 events per year). These integrated efforts require support in the following areas: information technology, systems integration, mission development, operations support, communication, security, and other support to STARCOM Wargaming. STARCOM Wargaming hosts a series of events in support of the Schriever Wargame Series conducted annually with events culminating in a Schriever Wargame Capstone event. Additional wargame events in support of STARCOM are yet to be determined and will be manpower- and calendar-dependent. The purpose of the wargame activities is to provide an opportunity to investigate issues and implications of the political-military relationships and space system employment through management and sponsorship of an international, multi-domain, multi-agency wargame centered on space and cyberspace within the larger DoD-wide, allied, and NRO wargaming activities. In coordination with the Government Wargame Director, the contractor shall design and develop wargame materials including but not limited to objectives, scenarios, road-to-crisis, organizational structures, and campaign plans. During the planning phases of the Schriever Wargame, several workshops and seminars shall be planned and executed with the goal of developing a baseline structure to support the actual execution of the wargame capstone. Additionally, the contractor will support simultaneous and similar planning and development of the higher-level, 4-nation Combined Technical Operations Center (CTOC) and US Technical Operations Center (USTOC) cells within the wargame construct.

1.3.12 STARCOM Space Delta 1 (DEL 1), 392d Combat Training Squadron (392 CTS), Schriever SFB, Colorado

1.3.12.1 The 392 CTS provides space combat training through live, virtual, and constructive environments to prepare warfighters to win.

1.3.12.2 The 392 CTS:

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

1.3.12.2.2. Provides 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.

1.3.12.2.3. Serves as the executive agent for the Secretary of the Air Force-sponsored SPACE FLAG 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.

1.3.12.2.4. Operates a distributed mission operations center to provide space modeling and simulation in support of approved training, exercise, test, experimentation, and mission rehearsal events.

1.3.12.2.5. Provides advanced training to support the Weapons Instructors Course (WIC) and Advanced Instructors Course (AIC).

1.3.12.2.6. Recruits instructors from various enlisted and officer space operator career fields and assignments, and develop instructors via a training, certification, and evaluation program for all 392 CTS mission sets to ensure the CTS provides world-class training.

1.3.12.2.7. When appropriate, develops and maintains reserve association plans, memorandums of agreement, and memorandum of understanding in coordination with USSF and AFRC.

1.3.12.2.8. Provides subject matter expertise supporting the maturation of Space Delta 1.

1.3.13 Other Supported Organizations

1.3.13.1 310th Space Wing (310 SW), Schriever SFB, Colorado

1.3.13.1.1 The mission of the 310 SW is to provide combat ready citizen Airmen to conduct and support space operations with strategic expertise and depth.

1.3.13.2 United States Space Command (USSPACECOM), Schriever SFB, Colorado

1.3.13.2.1 Mission: The USSPACECOM mission is to deter aggression and conflict, defend U.S. and allied freedom of action, deliver space combat power for the Joint/Combined force, and develop joint warfighters to advance U.S. and allied interests in, from, and through the space domain.

1.3.13.2.2 USSPACECOM requires support for information technology, exercises, and real world contingencies. In the future, USSPACECOM may need support for security requirements, Program Management, Rapid Acquisition, and Test and Evaluation. It is possible in a real-world event that the entire battle staff will be activated within building 24 requiring support from the contractor. Battle Staff personnel includes GO/FOs performing Assessor Duties when on duty or when an issue related to their duties arises. USSPACECOM Mission Essential Support requirements will be established at the task order level. (CDRL A010 - Mission Essential Support).

1.3.13.3 Space Rapid Capabilities Office-SOF (SpRCO/SOF), Schriever SFB, Colorado

1.3.13.3.1 The Space RCO mission is to develop and deliver operationally dominant space capabilities at the speed of warfighting relevance. We expedite delivery and deployment of space capabilities in response to the Commander, US Space Command requirements as assigned by our Board of Directors

1.3.13.4 Space Systems Command Space Domain Awareness Division (SSC/ECG), Schriever SFB, Colorado

1.3.13.4.1 Mission: SMC/SPG provides Space Domain Awareness (SDA) services and capabilities to warfighters, analysts, and systems enabling the space domain, while also supporting the broader joint and multi-domain mission.

ISSA is a Government-owned suite of software capabilities managed by SMC/SPG. ISSA uses high-power analysis and visualization capabilities to provide SDA Course of Action development, threat processing, and sensor tracking.

Modeling and Simulation (M&S), and cutting edge Machine Learning and Artificial Intelligence technologies and software, including software tools as part of operational baselines by USSPACECOM operational centers, and as part of the operational baseline for the Maritime Operational Center. ISSA has numerous active web-based users on classified networks including a broad range of DoD and civilian Federal agencies.

Joint Task Force – Space Defense (JTF-SD)

1.4 DESCRIPTION OF SERVICES/SPECIFIC REQUIREMENTS

1.4.1 Security Requirements

1.4.1.1 The contractor shall require access to secret collateral, top secret-sensitive compartmented information (TS/SCI ), SAP/SAR, and other special category data during the performance of various tasks in this contract. At a minimum, ninety percent (90%) of contractor employees are required to obtain and maintain TS/SCI clearances.

1.4.1.2 The contractor shall obtain and maintain the security requirements necessary to propose for this contract in accordance with (IAW) the DD Form 254 and DoD Manual 5200.01. Duties include all integrated security disciplines; personnel, physical, industrial and information system security disciplines. The contractor shall coordinate daily visitor lists and requests for meetings and conferences to be held within the facility; process program access requests (PARs); provide on-site security support to meetings and conferences; process SCI fax materials; support courier-related duties such as wrapping, receipting, destroying, and distributing classified materials; and provide support in maintaining classified databases and SCIF operations. In addition, the contractor shall perform escort duties for non-cleared individuals requiring access to secure areas. General administrative duties shall be performed to include taking inventories of equipment and other administrative tasks. The contractor shall provide support in conducting inspections for program compliance with customer requirements; present administrative briefings to conferences and meetings when required; properly secure SCIFs; and comply with all security-related processes, to include communications security (COMSEC), operations security (OPSEC) AFI 10- 701 (Chapter 8), and information security (INFOSEC) duties.

1.4.1.2.1 Alternative Compensatory Control Measures (ACCMs): While AFI 16-1404 specifies that ACCMs are not authorized for use in the Air Force, Contractor performance may nevertheless require participation in the Joint Staff Focal Point Program (FPP) and access to Alternative or Compensatory Control Measures (ACCM) information in accordance with DoDM 5200.01, Vol 3 and CJCSM 3213-02D. Handling of ACCM/FPP information will be done "onsite" at government facilities only.

1.4.1.3 The contractor shall be compliant with the International Traffic in Arms Regulation (ITAR) with respect to release of information.

1.4.1.4 The contractor shall implement an industrial security program in support of the entire Innovation, Integration, and Information Support III (3IS III) contract that shall include their subcontractors IAW established DoD policy and procedures.

1.4.1.5 The contractor shall complete and comply with the long-term Visitor Group Security Agreement (VGSA) upon contract award.

1.4.1.6 The Government will provide initial and follow-up security procedures training to contractor personnel who work in controlled and restricted areas.

1.4.2 Program Management, Administrative, Security, Personnel, Logistics, and other Support

1.4.2.1 Program Management

1.4.2.1.1 The contractor shall perform program management by providing and orchestrating resources, financial management, administering contract actions, monitoring performance, making recommendations for improvement, supporting meetings, and preparing deliverables (Contract Data Requirements List (CDRL) A001 – Contractor’s Progress, Status, and Management Report, CDRL A003 - Cost Performance Report, CDRL A004 – Contract Funds Status Report, CDRL A005 – Management Plan).

1.4.2.1.2 The support contractor shall perform program level management, integration, cross utilization, control, and oversight of all related contractor/sub-contractor activities. Program management shall include the responsibility to assure satisfactory technical performance, program risks, oversight of schedules, costs, administration, security, reports, reviews, and similar functions and activities associated with this contract PWS. The contractor PM shall be the single interface to the 3IS III PM for program management activities and communications concerning the multi-function teams (MFT).

1.4.2.1.3 The contractor PM shall identify and recommend specific program/task tracking and reporting software applications to be used in the performance of program management responsibilities. The contractor PM shall use government-off-the-shelf (GOTS) and/or commercial-of-the-shelf (COTS) applications to the maximum extent possible in support of this contract.

1.4.2.1.3.1 The contractor PM shall maintain the approved management plan (CDRL A005) as required for Government approval. The management plan shall include specific references to the contractor’s organizational conflict of interest (OCI) plan regarding interfaces and existing or potential duplication for operational assessment and support of overall contract tasks. The management plan shall address the program management structure; the approach to be used for program management support; the reporting, administrative, and accounting mechanisms to be employed in managing the program; and, the management methodology/techniques/organizational structure used to control program execution activities under all task orders issued under the PWS cited above to include subcontractor management plans and activities.

1.4.2.1.3.2 The contractor shall identify “leads” (or whatever designation the contractor chooses) for the individual tasks/units supported on this contract. The “leads” shall be identified/accounted for under this PM task.

1.4.2.1.3.3 The contractor shall perform day-to-day contract administration. Contract administration includes responding to TPRs, implementing contract modifications and changes, negotiations, and participating in technical interchange meetings (TIMs).

1.4.2.1.3.4 The contractor shall provide timely and accurate financial management to include: cost status and forecast data, pricing data, purchasing, invoicing, and travel management; proactively identifying potential mission impacts and offering possible action plans.

1.4.2.2 Task Coordination

1.4.2.2.1 The contractor shall provide technical integration and resource management for tasks to include cross-task and reach-back integration for additional technical services, system engineering, and analysis and evaluation of initiatives. Management of the contractor’s support resources, including travel and ODCs (see paragraph 1.5.6);

interface with the Contractor Program Manager (CPM) to verify availability of funding prior to travel and support the primary task support personnel with equipment procurement issues; and keep the Contracting Officer Representatives (COR) informed of resource issues that may affect the performance of the task and recommend courses of action to mitigate problems.

1.4.2.2.2 Interface between the Government and management staff to expedite changes and modifications to include realignment of funds, level of effort adjustments and addition of in-scope effort.

1.4.2.2.3 Program, develop, maintain and deliver a database of all lessons learned. The database shall include all lessons gathered from project officers during the course of project execution and close-out.

1.4.2.2.4 Contract Transition. The contractor shall transition into and out of this contract without degradation of service to any of the supported organizations. (CDRL A008 – Transition).

1.4.2.2.5 Phase-In. The contractor shall meet with the 3IS III Program Manager (PM) and the Government phase-in team not later than three (3) days after contract award. The contractor shall develop and implement a Phase-In Plan IAW CDRL A008. The Phase-In Plan shall address at a minimum all issues identified in the incumbent contractor’s Phase-Out Plan.

1.4.2.2.6 Phase-Out. The contractor shall develop and implement a Phase-Out Plan. The Phase-Out Plan shall address all areas, issues, and concerns required for a smooth transition. A Phase-Out Plan shall be prepared and submitted no later than 90 days prior to contract expiration or within 30 days of the Contracting Officer’s (CO) request.

1.4.2.2.7 Status Briefings and Readiness. The contractor shall provide weekly briefings on Phase-In status to the Government PM, CO and the Phase-In team, discussing problems encountered in accomplishing the Phase-In, categorized as minor, major, or showstoppers; progress-to-date with schedule updates to reflect the actual progress;

any variances from efforts contained in the Phase-In Plan; any work-around plans being implemented to resolve problems and any support needed from the Government for the Phase-In.

1.4.2.3 Security

1.4.2.3.1 Building 24 is classified as a Protection Level (PL) 4 Controlled area, which requires restricted access to protect multiple levels of classified information and material (up to 7 different levels). Security level will be identified at the task order level. The contractor shall provide overall security office and general security program support for all mission partners. Task orders for security may be at the Command or unit level.

1.4.2.3.2 Contractor personnel will not detain or control unauthorized personnel seeking to gain access to our facilities but will immediately notify Security Forces in such situations.

1.4.2.3.3 Administrative Security Support. The contractor shall perform security administrative support at the appropriate security level to include but not limited to in/out processing, preparing and maintaining security forms, processing and maintaining visitor access requests, security indoc/debriefings, badging, DD Fm 254s, security inspections, proper security classification markings, assisting Emergency Management Plan, maintaining security records, supporting Antiterrorism Force Protection program and other administrative support.

1.4.2.3.4 Special Security Representative (SCIF) Management. The contractor shall validate clearances of personnel, administer existing annual training program, maintain DoD standards for SCIF operations, perform SCIF inspections, and other SCIF administrative support.

1.4.2.3.5 Information Systems Security Officer (ISSO). The contractor shall be responsible for ensuring the operational security of approximately 100 non-networked, individual systems at all classification levels within SCIF areas. The duties and responsibilities shall be commensurate with those of an ISSO as described in DoD Intelligence Information System (DoDIIS) – Joint Security Implementation Guide (DJSIG), security directives as noted in the Publications list, standard operating procedures, and Space Base Delta 1 (SBD 1) Emergency Action Plan.

1.4.2.3.6 Information Protection. The contractor shall be required to perform the following duties:

1.4.2.3.6.1 Assist in providing appropriate visitor credentials utilizing JPAS/ Scatter Castles to Building 24 POCs prior to them escorting visitors into the Building 24 Controlled Area.

1.4.2.3.6.2 Participate in the development of Security CONOPS and OIs as they relate to the operation of Building 24 in conjunction with the security office.

1.4.2.3.6.3 Perform periodic Information Protection (IP) inspections in IAW current guidance in non-SCIF areas on security containers and combination locks and conduct combination changes on cipher locks and other in-use dial combination locks. Notify the in-house Facility Manager when issues are identified. (AFI 16-1404 2.7.11. And 5.2.4)

1.4.2.4 Facilities Services. The contractor shall inspect conditions and report any issues to the COR and coordinate with Civil Engineering (CE); attend facility working group meetings; troubleshoot, schedule, and coordinate with CE for maintenance and projects; provide escort services for outside vendors; provide subject matter expertise for facility management reviews and evaluation of projects; and coordinate schedules with tenants within Building 24.

1.4.2.5 Supply Services. The contractor shall issue, maintain, and inventory all supplies and non-IT equipment;

provide shipping and receiving services when operating the loading dock; coordinate commercial air and ground shipments; coordinate property disposal activities, support building recycling program; review/analyze/maintain supply and logistics database; coordinate with Government UDM to support deployments; and support hazardous materials and environmental requirements.

1.4.2.6 Personnel Support. The contractor shall provide office of personnel management support services to include but not limited to unit manning documents, personnel management rosters, organizational change requests, in/out processing personnel, Newcomer Orientation, Organizational Defense Travel Administration, unfavorable information files, awards/recognition program, officer/enlisted performance reports, transaction register, military personnel data system update, permanent change of station, separations, retirements, enlisted and officer promotion actions, Virtual Personnel Center, leave program, and other miscellaneous support.

1.4.2.7 Administrative Support. The contractor shall provide support to mail and distribution, task management (TMT), conference room and video teleconference scheduling, schedule management, records management, travel administrator, rosters, and coordinating/editing documents (i.e., briefings, letters, reports).

1.4.3 392 CTS Support

The contractor must possess current knowledge in the following areas: Space system capabilities, space intelligence and adversary capabilities, M&S systems operations (see Appendix E for a list of M&S systems), communications systems and distributed architectures, exercise design, development and execution, software and network engineering. In support of 392 CTS mission, the contractor shall support exercises as defined in the USSF Service Exercise Plan (SEP) and other 392 CTS events (experiments, demonstrations, warfighter focused events, etc.).

(CDRL A002 – Developmental Design Drawings and Associated Lists, CDRL A009 – Scientific and Technical Reports).

1.4.3.1. In support of Mission activities, and at the Government’s direction, the contractor shall:

1.4.3.2. Operate existing and future systems capabilities and architectures in support of advanced training, demonstrations, special event assessments, exercises, and real-world contingency operations. Flexible work schedules, including 24-hour/7-day operations, shall be required periodically to support exercises, demonstrations, experiments, and contingencies according to a mutually agreed upon schedule. Maintain detailed system expertise on all aspects of operating 392 CTS M&S and Command, Control, Computer and Communications (C4I) equipment.

1.4.3.3. Lead, plan, develop, and execute exercises, experiments and training events involving multiple service and/or joint organizations by gathering information, coordinating with key players internal/external to 392 CTS and integrating their inputs, developing databases for 392 CTS, M&S, C4I systems, identifying exercise network and 392 CTS system requirements and developing space-related scenario requirements and events to meet player training objectives.

1.4.3.4. Lead, plan, develop, and execute training scenarios for all mission rehearsals and training internal to space forces and, if necessary, the interface to other DMO domains. This shall include the generation of virtual and constructive space effects that are synchronized with the scenario events. 392 CTS will coordinate all intra- and inter-domain requirements with other distributed training sites when required.

1.4.3.5. Lead, plan, develop, and execute exercises, experiments, and training events involving multiple service and/or joint organizations 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 at the main exercise sites.

1.4.3.6. Control 392 CTS exercise and event inputs as a member of the 392 CTS exercise control group (ECG), or in coordination with the host exercise control group (ECG), whose function is to maintain control of the timing, tempo and execution of the event to accomplish the desired training objectives.

1.4.3.7. Be prepared to emulate Higher Headquarters (HHQ) or other external organizations/ agencies not participating in an event (white cell).

1.4.3.8. Lead, plan, develop, and execute USSF participation in USSF, CJCS, CCMD, USAF and other Services exercises. For each event, develop schedules, plans and briefings; coordinate/monitor activities, and report on those activities through trip reports, briefings, meeting minutes, etc. As required, the contractor will participate during exercise execution as part of the exercise control group providing oversight, management and control of space and cyber events for the exercise.

1.4.3.9. Lead, plan, develop, and execute SF, Space Force level exercises, other significant advanced training events, or other USSF led exercises that focus on enhancing the combat readiness of warfighting forces. For each event, develop schedules, plans and briefings; coordinate/monitor activities, and report on those activities through trip reports, briefings, meeting minutes, etc. The contractor will participate during exercise execution as part of the exercise control group providing oversight, management and control of all events for the exercise.

1.4.3.10. Trip reports are required immediately at the end of conferences/meetings and exercise execution. Pre- IPC/CDC briefs are due 30 days prior to IPC/CDC. Exercise Readiness Review (ERR) briefings are required no later than 30 days prior to exercise execution. Execution Executive summary first duty day after exercise completion. Exercise quick look due NLT first Wednesday post execution. After Action Reports (AARs) are required within 30 days from the end of each exercise.

1.4.3.11. Assist 392 CTS in leading, planning and/or the conduct of Exercise Coordination Team (ECT) meetings.

1.4.3.12. Coordinate with Space Operations Command (SpOC), Space Readiness and Training Command (STARCOM), National Reconnaissance Office (NRO), Office of the Chief Operations Officer Deputy Director of Force Generation (SF/S7O), Joint Staff J7, United States Space Command J7, Air Force Reserve Command space associate units, and National Guard Bureau space units for each exercise and experiment. Coordinate all advanced training and manning requirements in accordance with STARCOM, DEL 1 and 392 CTS guidance and intent. The contractor will present training scenarios consistent with real world, day-to-day campaign threat conditions.

1.4.3.13. Perform maintenance and sustainment in support of DMO-S capabilities, DMO requirements, training scenarios and required databases. Provide maintenance, upgrades, and sustainment of the DMO architecture and system backbone in coordination with applicable government organizations.

1.4.3.14. Establish liaisons with key players from other DMO domains determined by the Government, collaborate with Government and other contractor teams that are supporting DMO-S development, primarily to accommodate data collection, obtain GOTS technologies and leverage best practices, procedures, and techniques.

1.4.3.15. Provide necessary daily support to set up, tear down, integrate, test, operate, and troubleshoot DMOC-S equipment and infrastructure supporting exercises, experiments, demonstrations, and training. Support may be required both in 392 CTS and at non-392 CTS locations.

1.4.3.16. Support the identification and coordination of resource requirements for the 392 CTS.

1.4.3.17. Identify design risks and support studies of hardware and software to provide the 392 CTS with solutions for DMO-S capabilities.

1.4.3.18. Support development of 392 CTS to enable it to provide an operational advanced training architecture that shall ensure a realistic combat representative training environment for space forces in each mission area to exercise sensor to decision-maker interfaces. This shall include development of new M&S and crew simulation systems.

(CDRL A006 – Software Product Specification (SPS), and CDRL A007 - Computer Software Products).

1.4.3.19. Provide technical expertise to the Government for evaluating new M&S tools and crew simulators being developed by outside contractors.

1.4.3.20. Support within existing capability any demonstrations, tests and/or special event assessments involving new space M&S and simulator systems by assisting in defining requirements, test plans and assessing the results.

1.4.3.21. Coordinate resolution of intelligence-related advanced training and exercise issues.

1.4.3.22. Ensure intelligence plans and operations inform the design of 392 CTS mission activities, and will draft appropriate intelligence background messages and intelligence-related injects into 392 CTS advanced training and exercises.

1.4.3.23. Lead the critical lessons learned program that discovers and validates observations, conducts and in-depth review to resolve valid observations, monitors and evaluates resolved observations, and disseminates lessons learned.

1.4.3.24. Support institutionalization for internal USSF lessons.

1.4.3.25. Use active (push) and passive (pull) methods to disseminate lessons to key mission partners.

1.4.4 Test and Evaluation (T&E). At the Government’s direction, the contractor shall support:

1.4.4.1 T&E. In support Operational Test & Evaluation (OT&E) and Developmental Test & Evaluation( DT&E) early involvement; test screening; integrated testing (DT&E, OT&E, and contractor testing) and dedicated DT&E and OT&E planning, execution, analysis, reporting, and closeout for DT&E tests, Production Acceptance Test & Evaluation (PAT&E), Product Qualification Testing (PGFT), Live-Fire Test & Evaluation (LFT&E), FDEs, OUEs, OAs, EOAs, WSEPs, SOTRs, IOT&Es, FOT&Es, QOT&Es, MUAs, C&LRs, MOT&Es, command-directed testing, and TD&Es in support of USSF weapons systems and programs the contractor shall: (CDRL A009 – Scientific and Technical Reports; CDRL A011 – Briefing Materials; CDRL A012 – Conference Minutes; CDRL A013 – Presentation Materials; CDRL A014 – Technical Reports – Study/Services; CDRL A015 – DoD M&S Accreditation Plan; CDRL A016 – DoD M&S Accreditation Report; CDRL A017 – Critical Task Analysis Report). Workload data will be documented at the task order level.

1.4.4.1.1 Possess current knowledge, understanding, and experience in the following areas: DoD, USSF, and AF OT&E and DT&E policies, procedures, and requirements for providing independent testing and evaluation of new and existing space systems in an operational environment. Personnel should possess in-depth knowledge and experience with all aspects of space systems including both space and ground segments. The contractor should have experience with test scheduling, test early involvement activities, test planning, execution, analysis, reporting, closeout activities of space systems; scientific test and analysis techniques (STAT); Design of Experiments (DOE), combinatorial testing, observational studies, covering arrays, deterministic testing, and descriptive and parametric/non-parametric statistics. In support of the Delta 12 test squadrons the contractor shall:

1.4.4.1.2 Support modernization and sustainment testing for WSEP and Space C2 associated systems at 1 TES, Det 4, Vandenberg SFB, CA in the role of contractor test analyst, test director, assistant test director, operations research analyst, test tool developer, technical writer, and/or data collector.

1.4.4.1.3 Support annual tests in support of 1 TES, Det 2, Cheyenne Mountain SFS, CO in the role of contractor test analyst, project manager, assistant project manager, and/or data collector and/or test tool developer.

1.4.4.1.4 Support annual tests in support of DEL 12 Test and Evaluation Squadrons in the role of contractor test analyst, test director, assistant test director, WSEP evaluation director, data collector, and/or test tool developer.

Test Analysts supporting DEL 12 will require SAP/SAR clearance to conduct test planning, execution, reporting, and analysis and closeout.

1.4.4.1.5 Additional test support for DEL 12 test squadrons will be added via contract modification as requirements are identified and funds become available.

1.4.4.2 Test Planning. In support of test planning, and at the Government’s direction, the contractor shall:

1.4.4.2.1 Lead or provide support in all aspects of test planning: support the test planning review process and managing manpower, funding, and test assets within test scope; conduct and accomplish Verification, Validation and Accreditation (VV&A) of models and simulations required for testing; participate in test planning working groups to identify and resolve test issues; and be available to travel during test planning and/or execution.

1.4.4.2.2 Lead or provide support in the development of test measures in the form of Critical Operational Issues (COIs), Objective Capabilities, Measures of Effectiveness (MOEs), Measures of Suitability (MOSs), and Measures of Performance (MOPs). The contractor shall develop a Data Management and Analysis Plan (DMAP), format prescribed by the TES, to document measure methodology, statistical methods, expected outcomes, sample sizes, definitions, etc.

1.4.4.2.3 Lead or provide support to all test planning sub-phases including developing the initial test approach, developing a feasible test concept, and the executable test concept.

1.4.4.2.4 Lead or provide support to the following: Analysis reviews (e.g., ARCs), ARC Decision Memorandums, Test Planning Reviews (TPRs) to include developing and giving TPR briefings, Combined Review Boards (CRBs) to include developing and giving CRB briefings and producing draft CRB minutes, developing statement of requirements and identified test standards, Test Readiness Review Boards (TRRBs) to include developing and giving TRRB briefings, integrated testing execution/data collection and design, Government led line-by-line reviews of test products (e.g., test plans and final reports/briefings), Joint Reliability and Maintainability Evaluation Team charters, Test Data Scoring Board procedures, accomplishing AF Forms 813 and 4437, customer briefings, site in-briefings, coordinating test site cybersecurity team site surveys and test execution assessments visits, and other test planning meetings.

1.4.4.2.5 Use Scientific Test and Analysis Techniques (STAT) whenever feasible and consistent with available resources. STAT will be used for designing and executing tests, and for analyzing the subsequent collected test data. Three specific STAT the contractor shall be able to utilize is DOE, covering arrays, and combinatorial testing.

The contractor shall develop and deliver test methodologies for each test measure with the purpose of performing statistical analysis to evaluate system performance and acquire validated truth data for these test measures. Test methodologies may include determining optimal sample sizes through power analysis and expected data distributions.