Attachment 1 Performance-Based Work Statement.pdf

FAR 52.215-3 Request for Information or Solicitation for Planning

Purposes (Oct 1997)

(a) The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation.

(b) Although "proposal" and "offeror" are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal.

(c) This solicitation is issued for the purpose of: Informing the Government’s acquisition strategy and future solicitation planning.

The documents attached to this solicitation for planning purposes are drafts and therefore are subject to change.

Boulder Ground Innovation Facility (BGIF) Operations Support

Services (BOSS)

Attachment 1

Performance Work Statement (PWS)

07 February 2025

Department of the Air Force Space Systems Command (SSC)

Space Sensing (SN) Boulder OPIR TAP Lab, Colorado

TABLE OF CONTENTS

1.0 Overview and Background

1.1 Execu ve Overview

1.2 Background

1.3 BGIF & OPIR TAP Lab Infrastructure Overview

1.4 Contractor Work Loca ons

2.0 Applicable Documents

2.1 Compliance Documents

2.2 Reference Documents

3.0 General Scope

3.1 Scope

3.2 Non-Personal Services

3.3 Inherently Governmental Func ons

3.4 Ethics

4.0 Performance Requirements

4.1 Program Management and Other Direct Costs (ODC) Requirements

4.1.1 Program Management

4.1.2 Financial Management

4.1.3 Security Management

4.1.4 Subcontractor Management

4.1.5 Work Management

4.2 BGIF Requirements

4.2.1 Engineering Services

4.2.2 Facility Support

4.2.3 Facility Tenant Support

4.2.4 Network Support

4.2.5 Security Support

4.2.6 Configura on Management Support

4.2.7 ISP Procurement Support

4.3 OPIR TAP Lab Requirements

4.3.1 Engineering Services

4.3.2 Network Support

4.3.3 OPIR TAP Lab Hardware Enclaves

4.3.4 Configura on Management

4.3.5 Cloud Support

4.3.6 Security Support

4.3.7 Cyber Security Support

4.3.8 Data Management Support

4.3.9 OPIR TAP Lab Ops Support

4.3.10 Requirements Development Support

4.3.11 OPIR TAP Lab CI/CD and S-SDLC Management Support

4.3.12 Capability Integra on Support

4.3.13 Capability Transi on Support

4.4 OBAC Requirements

4.4.1 Engineering Services Support

4.4.2 Network and Cyber Support

4.4.3 TAC Support

5.0 Contract Management

5.1 Management of Personnel

5.2 Training

5.3 Iden fica on

5.4 Places of Performance

5.5 Federal Holidays

5.6 Business Relations

5.7 Subcontract Management

5.8 Cost Control

5.9 Contract Accoun ng

5.10 Temporary Duty (TDY) Travel

5.11 Associate Contractor Agreement (ACA)

5.12 Interfacing with Aerospace Corpora on Contact Support

5.13 Contractor Responsibility Watch List (CRWL)

5.14 Con nuity of Services

6.0 Quality Assurance

6.1 Quality Control Plan (QCP)

6.2 Government Inspection

6.3 Non-Conformances

6.4 Minor Non-Conformance

6.5 Major Non-Conformance

6.6 Performance Requirements Services Summary

7.0 Government Furnished Property/Facili es

7.1 U li es

7.2 Facili es

7.3 Protec on from Loss

8.0 Deliverables (CDRLs)

9.0 Acronym List

10.0 Key Personnel Table

Table of Figures

Figure 1 - Organization Relationship Figure 2 - High-level BGIF/OBAC Overview & Acronym List Figure 3 - High-level Concept for OPIR TAP Lab Extension at GoG Facility Figure 4 - Notional SSC/SNGT Organization Figure 5 - BGIF and OPIR TAP LAB Infrastructure Overview Figure 6 - Add table with at least the “Scale Factor” details in BOSS Working Session PPT

Table of Tables

Table 1 - Place of Performance Table 2 - Federal Holidays Table 3 - Performance Objectives Table 4 - Deliverables Table 5 - Acronym List Table 6 - Key Personnel Table

1.0 Overview and Background

1.1 Executive Overview

This document is a Performance Work Statement (PWS) for a performance-based Non-Advisory and Assistance Services (A&AS) support services contract. The contract is called Boulder Ground Innovation Facility (BGIF) Operations Support Services (BOSS). The purpose of this PWS is to describe the performance objectives, tasks and functions for technology exploitation and development, facility operations and management, and information technology services for the Space Systems Command (SSC), Space Sensing Directorate, Strategic Missile Warning Ground Acquisition Delta’s (SNG) Overhead Persistent Infrared (OPIR) Tools, Applications and Processing Laboratory (OPIR TAP Lab) and BGIF.

We project that at the time of contract award the SSC/SNGT OPIR TAP Lab will be divided between “North” and “South” operating locations. OPIR TAP Lab North is the Government organization in Boulder, Colorado with the primary mission to perform Research, Development, Test and Evaluation (RDT&E) to explore, develop, enhance, test and deploy innovative data exploitation technologies, capabilities and software applications. An additional OPIR TAP Lab, with a smaller footprint than the Boulder site, is expected to be established in Colorado Springs, this site will be known as OPIR TAP Lab South, Garden of the Gods (GoG) due to its location in Colorado Springs Colorado. OPIR TAP Labs North and South are collectively known as “the OPIR TAP Lab.” The OPIR TAP Lab collaborates with Department of Defense (DoD) and other National Security, Civil and Commercial users and vendors to find innovative uses of remote sensing data.

The SSC/SNGT OPIR TAP Lab is a Geographically Separated Unit (GSU) to SSC at Los Angeles Air Force Base, California.

The BGIF is the facility in Bolder Colorado which hosts OPIR TAP Lab North as well as other Space Sensing (SN) tenant programs. The BGIF is a government-controlled, government-operated facility and an SSC/SN asset. The BGIF resides in a Lockheed Martin (LM) leased facility but is a separate entity.

SSC/SNGT is the organization responsible for the day-to-day operation and support of the OPIR TAP Lab as well as the day-to-day operation and support of the BGIF physical infrastructure (power/water), security, and administration. SSC/SNGT is the contract owner for the BOSS contract. Other tenant programs within the BGIF include Future Operationally Resilient Ground Enterprise (FORGE), Next-Generation Geosynchronous (NGG), Resilient Missile Warning/Missile Tracking (MW/MT) Medium Earth Orbit (MEO), Space Based Infrared System (SBIRS) Sustainment and the MeshOne-T (M1T) data transfer network. These tenant programs are physically hosted within the BGIF and are only within the scope of this PWS as far as common BGIF services are concerned. See Figure 1 for an ownership and logical breakout of the various organizations involved.

Figure 1 - Organization Relationship

In addition to the BGIF facility in Boulder Colorado, the OPIR TAP Lab North is logically and physically extended (currently three workstations; expect up to seven) into the Overhead Persistent Infrared (OPIR) Battlespace Awareness Center (OBAC). The OBAC is a facility within the SBIRS Mission Control Station (MCS) at Buckley Space Force Base (SFB), Colorado. The OBAC supports 24/7 space operations and intelligence missions conducted by 11th Space Warning Squadron (11 SWS) and 26th Intelligence Squadron (26 IS), respectively. 11 SWS is responsible for the OBAC facility and operations baseline. 11 SWS reports to United States Space Force (USSF), Space Operations Command (SpOC), Space Delta 4 (DEL 4). 11 SWS and 26 IS are the primary stakeholders for capabilities being researched and developed by the OPIR TAP Lab but additional stakeholders/customers may include other military organizations, Intelligence Community (IC) organizations and foreign mission partners.

Unlike the OPIR TAP Lab extension to the OBAC, the expectation is the OPIR TAP Lab North and South will share an on-prem hybrid-cloud infrastructure to support both DevSecOps Software Factory and Artificial Intelligence and Machine Learning (AI/ML) activities and initiatives with compute, storage and licensing through the Platform One service. The expectation is that by contract award an initial build-out of a new GoG on-prem hybrid-cloud data center infrastructure on a hardware baseline capable of hosting the DevSecOps Software Factory and AI/ML activities will be in place or in progress. This includes a 100GB “MeshOne-T” (M1T; USSF data transport layer) communications link connecting OPIR TAP Lab environments in Boulder and GoG. Operations and support for the GoG OPIR TAP Lab environment, as well as continued expansion, is in scope of this PWS.

The BOSS Contractor, simply referred to as “Contractor” throughout this PWS, shall exercise management and operational control over, and retain full responsibility for, performance requirements set forth in this PWS. The Contractor is encouraged to introduce new technologies and processes in order to deliver the best value products or services, as well as bring innovation to the OPIR TAP Lab and BGIF.

From a general scope perspective, Contractor responsibilities encompass the overall OPIR TAP Lab(s) information technology support services including the anticipated on-prem data center hybrid-cloud environment, LAN/WAN communications between the two OPIR TAP Lab environments (Boulder and GoG), plus LAN/WAN communications between OPIR TAP Lab at Boulder and OBAC. In addition, Contractor responsibilities encompass BGIF facility sub-leasing, infrastructure, security systems, badging and management functions sufficient to host OPIR TAP Lab and other BGIF tenants. The information technology support services enable OPIR TAP Lab to execute the lab’s RDT&E mission focused on developing software applications and algorithms designed primarily for 11 SWS and 26 IS Missile Warning (MW), Battlespace Awareness (BA) and Technical Intelligence (TI) mission areas. Contractor responsibilities also include maintaining communications interconnections to ingest OPIR data from SSC and Space Development Agency (SDA) proliferated OPIR constellations to support OPIR TAP Lab development of automation solutions using technologies such as AI/ML to address operator challenges.

All BOSS functions and activities will be task driven following an Agile methodology, and all work performed must be in accordance with all applicable regulations and guidelines IAW Section 2.0 Applicable Documents.

1.2 Background

The Government established the OPIR TAP Lab in Boulder in 2016 to enable more robust and enhanced exploitation and dissemination of OPIR and environmental monitoring (weather) data from space sensors. Congressional and community leaders realized OPIR systems were not fully exploiting the sensor data and investments made in SBIRS program data investments – too much data was being left behind. The OPIR TAP Lab created a Broad Agency Announcement (BAA) contract vehicle to expose OPIR data to a significantly broader non-traditional contractor community.

The OPIR TAP Lab then implemented an open model framework to promote competition and collaboration between application and algorithm developers to allow plug-and-play of different mission data processing chains. These processing chains of microservice containers followed a continuous integration/continuous deployment (CI/CD) model from the OPIR TAP Lab to the OBAC designed to deliver to stakeholders' operational utility and value from the OPIR data.

“OPIR TAP Lab” was originally the designation for the RDT&E organization as well as the physical facility at the Boulder site. In February 2024 the Government re-designated the facility the, Boulder Ground Innovation Facility or “BGIF.” Rationale was to differentiate the OPIR TAP Lab’s continued primary RDT&E mission focus from the BGIF physical spaces, infrastructure and support structures which now hosted more than just the OPIR TAP Lab RDT&E mission, but now also included other SSC programs conducting development, test and interim operational activities.

Figure 2 below provides a visual overview of these relationships.

Figure 2 - High-level BGIF/OBAC Overview & Acronym List

In addition to the BGIF hosting the OPIR TAP Lab as a tenant, the BGIF hosts other major standalone tenant programs. Examples of hosted tenant programs include FORGE Framework ;

NGG Interim Operations (NIO) Command and Control (C2); Resilient MW/MT MEO Data Processing (MDP) and Command and Control (C2) for Epochs 1 and 2; SBIRS Hardware Depot Contractor Logistics Support (CLS) functions; and to a smaller degree, some support for the Space Development Agency (SDA) WFOV Low Earth Orbit (LEO) Tranche 0 program.

Hosting tenant programs in the BGIF benefits the Government by leveraging on-site infrastructure (e.g., server room space, power, cooling), communications, security measures, and technical expertise in a Government-managed facility, providing Government programmatic and operational efficiencies, and giving the OPIR TAP Lab robust access to DoD OPIR data sources to support the lab’s RDT&E data exploitation mission.

Next-Gen GEO Interim Operations (NIO) hosted in the BGIF are designed to be an element of the SBIRS/Next Generation architecture performing the “no-fail” Integrated Threat Warning and Attack Assessment (ITW/AA) MW mission. Resilient MW/MT MEO Epochs 1 and 2 hosted in BGIF are designed as foundational capabilities to contribute critical tracking messages and other mission data to the MW/MT missions. These two programs make it imperative that BGIF provides reliable infrastructure support and quick response times to any potential mission-impacting facility/infrastructure contingencies. The WFOV GEO system contributes additional OPIR data to MW/MT missions; this system requires extended support. The increased requirement for timely support to these three programs is a change from the previous contract.

The Missile Warning Enterprise (to include the OPIR TAP Lab and BGIF tenant programs) are transitioning to FORGE. FORGE provides a common architectural framework and mission processing applications (FORGE Processing) in SBIRS MCS and other sites supporting the USSF OPIR missions. The OPIR TAP Lab plans to retire its legacy software framework called "Sensor Open Framework Architecture" (SOFA) and its accompanying hardware called Sensor Exploitation Ground Architecture (SEGA) and replace them with FORGE Framework prior to BOSS contract start, however that transition may be ongoing when the contract is awarded. In this PWS, FORGE is not considered a third-party application (software application developed by outside vendor and integrated into OPIR TAP Lab’s DevSecOps pipeline).

As outlined in 1.1 Executive Overview, the Government expects to logically and physically extend OPIR TAP Lab into the GoG, Colorado Springs facility. Extending OPIR TAP Lab into GoG is designed to benefit the Government by alleviating physical space constraints in BGIF, create synergies with other Government activities at GoG, and enable more distributed, secure OPIR TAP Lab operations. Figure 3 is a top-level depiction of this extension concept (shaded area; top right corner).

Figure 3 - High-level Concept for OPIR TAP Lab Extension at GoG Facility

The Government Director of SSC/SNGT has organized OPIR TAP Lab and BGIF using an Agile management approach and “product teams.” Each product team is assigned a functional area, e.g., Infrastructure, Mission Support and Engineering, Capability Integration and Delivery, etc. The Government coordinates with OPIR TAP Lab and BGIF supporting FFRDCs and technical support contractors to assign Product Owners/Managers based on mission need and individual experience levels and skills set by requirements of each contract. Each product team is designed to operate as a unified team with a “best athlete” mix of Government, FFRDC, System Engineering and Integration (SE&I), System Engineering and Technical Assistance (SETA), and A&AS support services contractors (including team members on the BOSS contract).

The Contractor will be expected to integrate into this organization construct to accomplish the requirements in the PWS. Figure 4, below, provides a notional organization structure internal to SSC/SNGT. The “Gold” boxes represent product teams where the BOSS contractor has sole ownership and responsibility for. The half “gold” half green boxes are product teams in which the BOSS contractor shares responsibility and work output with team members outside their contract.

Figure 4 - Current SSC/SNGT Organization

Section 4 Performance Requirements of this PWS identifies specific task level requirements. The requirements support SSC/SNGT Government missions in three areas:

First, the SSC/SNGT OPIR TAP Lab Government team manages and operates the day-to-day activities within the BGIF through the BOSS contractor. The BOSS Contractor directly sub-leases BGIF spaces through the primary lease holder, currently Lockheed Martin (LM). The facility is owned by a commercial real estate corporation and LM holds the primary lease for the entire building at 6304 Spine Road, Boulder. The Government will provide information on the current lease/sub-lease terms and length. The sub-lease holder (the BOSS prime contractor) has full responsibility for the BGIF portion of the building and infrastructure operations sufficient to support OPIR TAP Lab RDT&E and BGIF, including tenant support. The operations currently include maintenance of two on-prem server rooms, a power room with 240-battery back-up, UPS and three external diesel generators for short term backup power. Due to the 24/7 near-operational nature of some tenant missions, keeping BGIF computer room power continuously online is a focus area of this contract. In addition, the BOSS contractor either fully owns or contributes to the maintenance and operations of the “common support services” described in Figure 2.

Second, SSC/SNGT OPIR TAP Lab plans and executes RDT&E to explore, develop, advance, test and deploy innovative data exploitation and processing technologies, capabilities and software applications and algorithms. The OPIR TAP Lab is a DevSecOps Software Factory that supports Development, Test and Production environments running Platform One (Big Bang) virtual environments. This mission also includes, but is not limited to, identifying and advancing technologies such as AI/ML, data fusion and digitalization to apply against evolving threats and technical and operational challenges inherent in proliferated space architectures the United States is fielding.

To execute this mission, SSC/SNGT OPIR TAP Lab maintains an unclassified hardware enclave, a collateral Secret hardware enclave and the Wide Field of View (WFOV) Secret Test and Integration Network (STING) enclave, all physically located inside the BGIF, as well as several virtual enclaves. The physical enclaves rely on space, power and cooling provided by the BGIF but also have additional requirements which enable the enclaves to remain operational and are captured under the OPIR TAP Lab section of this PWS. These requirements include maintenance, administration, and recapitalization of networked hardware which provide compute, memory, storage and overall capability to execute the lab’s RDT&E mission (including AI/ML level processing requirements). Requirements also include infrastructure recapitalization at appropriate timeframes, e.g., Uninterruptible Power System (UPS) batteries, cooling units and power generators.

From a cybersecurity perspective these requirements include maintaining Authorities to Operate (ATO) using eMASS and XACTA (secure, web-based tools used to manage cybersecurity data, workflow and reports) for at least four separate enclaves with two Authorities to Connect (ATC) per enclave. Finally, SSC/SNGT OPIR TAP Lab provides developmental, engineering and operations support to select OBAC missions at Buckley SFB, CO. This mission includes developing and enhancing tools for 11 SWS and 26 IS operators and analysts, and engineering support for the TAC.

1.3 BGIF & OPIR TAP Lab Infrastructure Overview

Figure 5 - BGIF and OPIR TAP LAB Infrastructure Overview

Figure 5 depicts current conceptual design of the BGIF and OPIR TAP Lab infrastructure. In addition to a data archive, the common services environment contains security logging services, user access control, and other information security services. For more details on the OPIR TAP Lab design, refer to the applicable documents in section 2.0. The Government plans to include Cross Domain Solution (CDS) services between different security level enclaves in the OPIR TAP Lab.

This capability will be provided by a 3rd party vendor but will be supported long-term by the Contractor.

Diagram to be provided in the Bidders Library

The BGIF has network interfaces to NIPR, SIPR, RTS, PWAN (Blossom Point Tracking Facility, Maryland link supporting WFOV), Government Wide Area Network (GWAN), SBIRS Analytical Sub-Element (ASE) and M1T. The Government plans to implement a network interface to JWICS.

The Government manages all these systems including JWICS when once implemented. The Government may add other network interfaces to meet mission requirements.

Figure 6 - Scale Factor

For planning purposes figure 6 above provides an estimate as to relevant factors to help scope the level of support needed on the BOSS contract.

1.4 Contractor Work Locations

The BGIF and OPIR TAP Lab North are co-located in sub-leased space in Boulder, Colorado. The OBAC is located within the SBIRS MCS at Buckley SFB, Colorado. The Government plans to extend the OPIR TAP Lab into GoG in Colorado Springs, Colorado. For the GoG facility another Government organization leases the facility through General Services Administration and manages all aspects of the facility. The GoG facility is separate from the leasing/sub-leasing arrangement in BGIF. The Contractor will have no requirement to manage the lease for OPIR TAP Lab South extension at GoG.

Physical addresses of the facilities are:

BGIF and OPIR TAP Lab North: 6304 Spine Rd, Boulder CO 80301 OBAC: 18300 E. Crested Butte Ave, Buckley SFB CO 80011 Proposed future location: GoG (OPIR TAP Lab South): 2424 Garden of Gods Rd, Colorado

Springs, CO 80919

2.0 Applicable Documents

2.1 Compliance Documents

In executing the tasks in this PWS, the Contractor shall comply with the following documents related to the task areas.

SBIRS Security Classification Guide (SCG), 22 April 2016 Wide Field of View SCG, 1 April 2020 SBIRS Enterprise Systems Engineering Plan (ESEP), May 2017, July 2010 SMC-S-001: Systems Engineering Requirements and Products, 1, July 2013 SMC-S-002: Configuration Management, 13 June 2008 SMC-S-003: Quality Space and Launch Requirements Addendum to AS9100C, 8 May

SMC-S-012: Software Development, 16 Jan 2015 SMC-S-019: Program and Subcontractor Management, 11 August 2008 SSCI 64-101: Space Contractor Responsibility Watch List (CRWL), 8 March 2022 DoDD 5205.02E, DoD Operations Security Program IEEE 15288.2: Technical Reviews and Audits on Defense Programs, 2014SMCI 63‐103:

Software Acquisition Process Improvement Instruction, 30 Dec 2015 Next Gen OPIR SCG, 2 Mar 2021

BGIF SCIF SOP

2.2 Reference Documents

DoDI 8510.01: Risk Management Framework (RMF) for DoD Systems, 19 Jul 2022 DoD 5220.22-R, National Industrial Security Program (NISPOM) Regulation, April 2014 DoD 5220.22-M: National Industrial Security Program Manual, February 2006 DoD 5220.22-M-Sup-1: National Industrial Security Program Manual, Supplement, 1 July 1997 DoDM 8140.03: Cyberspace Workforce Qualification and Management Program, 15 Feb 2023DoDI 4630.05: Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS), 23 Apr 2007

DoDI 8500.01: Cybersecurity, 14 Mar 2014 AFMAN 33-214, Emission Security Countermeasures Reviews, Volume 2, 21 Sep 2001 AIR FORCE MANUAL 17-1301, 12 Feb 2020 ICD 705, Sensitive Compartmented Information Facilities AFI 10-601 Operational Capability Requirements Documentation and Validation, 27 Apr

AFI 31-101, Physical Security Program Management AFI 31-601, Industrial Security Program Management DAFI 32-2001, Fire and Emergency Services Program, 28 Jul 2022 94AWI32-7086, Hazardous Materials Management Program, 1 Feb 2022 AFI 33-230, Information Protection Assessment and Assistance Program DAFI 91-202, The Department of the Air Force Mishap Prevention Program, 10 Apr 2024 DAFI 91-203, Air Force Occupational Safety, Fire, and Health Standards, 25 Mar 2022 DAFI 16‐201: Department of the Air Force Foreign Disclosure and Technology Transfer

Program, 19 Jan 2021 AFMAN 14-304: The Security, Use, and Dissemination of Sensitive Compartmented

Information (SCI), December 2016 DAFMAN 63-119: Mission-Oriented Test Readiness Certification, 15 Apr 2021 TAP Lab Hardware Integration Workmanship Standard TAP Lab Secure Software Development Life Cycle (S-SDLC) DOD Data Strategy, 30 Sept 2020 Data Centric Manifesto, http://datacentricmanifesto.org/ Data Management Lexicon, May 2024 Executive Order on the Safe, Secure, and Trustworthy Development and Use of Artificial

Intelligence, 30 Oct 2023 DOD Data, Analytics, and Artificial Intelligence Adoption Strategy, 27 June 2023

3.0 General Scope

3.1 Scope

This PWS identifies requirements for support services for the BGIF, OPIR TAP Lab (North- Boulder/South-GoG), and OBAC. The Contractor shall support critical activities in three areas, all managed by a single SSC/SNGT Government customer:

First, BGIF is the Government-controlled, Government-operated facility and infrastructure at Boulder, CO. BGIF provides the space and facility infrastructure in which OPIR TAP Lab (North) executes its RDT&E mission. BGIF hosts tenant programs that perform development, test, and operational type activities for other SSC programs as well as communications systems which support the OPIR TAP Lab and all tenants. BOSS Contractor support for BGIF includes (listed in order of priority): sub-leasing, facility infrastructure (power/HVAC/lighting/water, etc.) maintenance, 24/7 physical security, alarms, access control/badging, and support logistics. HVAC includes computer room cooling plus environmental cooling/heating for work areas.

Second, SSC/SNGT OPIR TAP Lab at Boulder, CO (OPIR TAP Lab North) and GoG (OPIR TAP Lab South), Colorado Springs are both DevSecOps Software Factories and AI/ML Information Technology environments used to support SSC/SN’s RDT&E mission to explore, develop, advance, test and deploy innovative data exploitation and processing technologies, capabilities and software applications and algorithms. The goal of the OPIR

TAP Lab RDT&E activities is to enhance processing of not only current space-based remote sensor OPIR mission data, but also data from future proliferated sensors and other mission data and dissemination of the resulting information products to operational users. Contractor support for OPIR TAP Lab includes (listed in order of priority): cybersecurity, systems engineering, architecture engineering, integration, and capability deployment services. The expectation is the two OPIR TAP Lab environments will share a common on-prem data center hybrid-cloud infrastructure where the bulk of the IT on-prem infrastructure will be consolidated and shared via a M1T 100G communication link (within the same cyber security enclave accredited by USSF, S3/6).

Third, the SSC/SNGT OPIR TAP Lab has extended workstations into the OBAC for direct operator feedback on applications/algorithm and provides remote access from OBAC to the OPIR TAP Lab for the Technical Analysis Cell (TAC). The TAC, comprised of several FFRDC subject matter experts, performs a unique data analysis function in support of 11 SWS and 26 IS missions. Contractor support must ensure these capabilities and support functions are available (listed in order of priority): system engineering, operations support, technical refresh, procurement and management of hardware.

General Definitions

a) Information Technology Management – the activities related to managing support of IT to provide information for policy development, strategic planning, enterprise architecture, capital planning and investment control, resource management, procurement actions, and special projects. IT management activities include, but are not limited to, providing, developing, implementing, and monitoring the operational availability and maintainability of the BGIF and select systems in the OBAC according to industry best practices; updating and submitting infrastructure upgrade recommendations; performing resources management (monitoring processing and memory utilization); producing products in response to quick-turnaround needs to include, but limited to, briefings, presentations, fact sheets, as well as issue and reference papers. Proper IT management requires internal and external coordination, including, but not limited to: working with customers, other agencies, internal program management office staff, other external agencies, and when requested, provide information to assist in drafting responses to inquiries from Congress and other agencies.

b) Systems Engineering – the activities pertaining to software/hardware development support for all existing, planned, and future TAP Lab systems and capabilities. Typical duties include capturing both system and user requirements; coordinating with appropriate Government personnel regarding enterprise architecture; identifying functional, security, and performance standards; developing logical and physical database models; performing coding, testing, quality assurance, design, and program documentation; implementation; and maintaining interoperability between future and existing hardware and software applications. Software applications include, but are not limited to, web applications, Commercially Available-Off-The-Shelf (COTS) integration, Government-Off-The- Shelf (GOTS) integration, and custom applications development.

c) Information Technology System Administration – the activities related to planning and implementing telecommunications and information technology infrastructures; network administration which includes network access and security; server management; emergency preparedness planning; IT disaster recovery planning and execution; IT inventory control;

audio, video, and web conferencing; application system administration; user support;

workstation management; IT training and education; wireless services; and voice and data services as well as the maintenance and service related activities to ensure operational availability of the IT telecommunications and networks.

d) Cybersecurity – the activities related to the secure transmission and storage of electronic information, drafting cyber security policy and procedures, providing user awareness training, risk management, and internal and external auditing. Further cyber security activities pertain to selecting and supporting the use of electronic security hardware and software tools and mechanisms including, but not limited to, encryption devices, access control, user identification and authentication, and malicious content detection.

e) Communication and Network Engineering is the planning, oversight, and evaluation of network upgrades; support of integrated product installation schedules and critical path analysis; evaluation of system migration; support to infrastructure requirements, security analysis and implementation for personnel and computer security issues.

f) OPIR TAP Lab Data Repositories consist of both a static library and a dynamic library.

The static library is comprised of raw and intermediate processed data for specific events of interest. The dynamic library is a rolling raw data library that contains all raw data collected over a certain period. In addition, the OPIR TAP Lab maintains a library of emulated data sets for multiple sensor types in multiple orbits.

g) 3rd Party Delivered Capabilities are elements of software, hardware, and other like capabilities that are delivered to the Government by vendors that are not subcontractors of the contractor.

h) Program Management Office (PMO): The USSF office responsible for managing the contract is SSC/SNGT at Los Angeles Air Force Base, California.

i) Government Program Manager (PM): The PM provides primary program oversight and management of the contract. In collaboration with the Procuring Contracting Officer, the PM ensures the Contracting Officer’s Representative (COR) is trained before performing any COR duties and supports the COR’s performance assessment activities. Additionally, the PM will review the Contractor’s performance at periodic points in time. The PM is not authorized to direct or redirect the efforts of the Contractor or to modify any of the items of this contract.

j) Procuring Contracting Officer (PCO): Individual designated by the USSF to direct or redirect the efforts of the Contractor or to modify any of the items of this contract. The PCO appoints the COR in writing and notifies the Contractor of that appointment.

k) Contracting Officer Representative (COR): The COR is the Government representative appointed by the PCO who is responsible for monitoring, evaluating, and reporting

Contractor performance on this contract. The COR will interface with the Contractor, the PCO and the PMO. The COR is not authorized to direct or redirect the efforts of the Contractor or to modify any of the items of this contract.

3.2 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to or prepare work schedules for individual Contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute or are perceived to constitute personal services, the Contractor shall notify the PCO immediately.

3.3 Inherently Governmental Functions

The Contractor shall not perform any task of a policy, decision-making or management nature (i.e., inherently Governmental functions). All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

The Contractor shall not counsel, mentor, make judgment and discretionary decisions or perform any other activities related to supervision of Government personnel.

During performance of this PWS, any Contractor personnel shall immediately stop work and notify the PCO and their corresponding COR(s) in writing regarding any situation where there is a belief, or a reason to believe, work has been tasked which is an inherently Governmental function as defined by FAR Subpart 7.5.

3.4 Ethics

The Contractor will be highly visible to the entire acquisition community as a result of providing support to the Government. The Contractor shall present an unblemished appearance in regards to ethics, discretion, and protection of information, including the guidelines for electronic mail use listed in Air Force Instruction (AFI) 33-119 and Internet use of Air Force Instruction (AFI) 33-129

AFOSISUP.

4.0 Performance Requirements

Section 4.0 is broken out into four sections. 4.1 describes the requirements placed on the BOSS contractor for the overall execution of the contract and governs how the subsequent sections of section 4 are to be executed. Sections 4.2, 4.3 and 4.4 describe the requirements placed on the BOSS contractor relative to the respective section; the BGIF, the OPIR TAP Lab and the OBAC.

4.1 Program Management and Other Direct Costs (ODC) Requirements

Section 4.1 describes the overarching management requirements which apply to all of section 4.0 of the BOSS contract.

4.1.1 Program Management

4.1.1.1 The contractor shall provide written notice 30 days prior to departure for any staff listed as “Key” in this PWS and provide resume or other qualifications for their replacement to the Government for concurrence of acceptability. Any personnel replacing key personnel shall be of equal or greater qualification of the contract’s key personnel.

4.1.1.2 The Contractor shall provide a Program Manager to oversee all contract efforts in support of the tasks in this PWS. The program manager shall serve as lead for execution of the contract, updating stakeholders on the contract progress. The program manager shall interface with Government leadership on daily activities of Contractor work efforts. The program manager shall be the single source of programmatic knowledge and ownership of assigned work across the contract.

This position is listed as a “key position for this contract.

4.1.1.2.1 At a minimum, the program manager shall have a master’s degree in management or related engineering field, 10 years of industry-related experience, and possess a current TS Clearance with SCI Eligibility.

4.1.1.3 The Contractor shall plan and execute a Contract Kick-Off meeting, led by the contractor program manager, with the participation of all personnel listed as Key Personnel, by ATP+20 days. The Contractor shall review the Contractors Staffing plan and its execution broken out by team, the contractors proposed budget plan for the base period of the contract, a process overview and notional timeline for procurements executed on BOSS, any blockers and any major risks the contractor would like to bring to the government's attention.

4.1.1.4 The Contractor shall manage work distribution to ensure there are no Organizational Conflicts of Interest (OCI) and/or applicable Personal Conflicts of Interest (PCI). The Contractor may request to add subcontractors to their team after examination of information that there is no OCI issue or submission and approval of mitigation plan by the PCO.

4.1.1.5 The Contractor shall conduct monthly Program Management Reviews (PMRs) starting in the second month after contract award. PMR topics shall include, but are not limited to, overall program status reporting and review; program issue identification and discussion, Action Item (AI) resolution, scheduling, funding, ODC procurement plan and plan status, and other topics (as required).

4.1.1.6 The Contractor shall develop and deliver a Monthly Status Report (MSR) on a monthly basis starting at ATP+45 days (CDRL A001). The Contractor shall document development status, issues, concerns, monthly funds status, etc. in the MSR for the overall contract. The contractor shall report the previous months expenditures for labor and ODCs and well as project the next three months planned expenditures for all active CLINs. For Labor the contractor shall track and report BOSS personnel hours for OPIR TAP Lab and each tenant programs supported by BOSS when practical to attribute to individual tenants.

4.1.1.7 Upon request by the Government the Contractor shall negotiate with tenant program contractors to accomplish non-disclosure agreements (NDA) or other forms of OCI mitigation for BOSS contract personnel.

4.1.1.8 The Contractor shall be responsible for obtaining NDAs with all applicable Government, corporate, supplier, tenant program contractors and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this contract. The Contractor shall provide a copy of each NDA to the PCO and PM/COR.

4.1.1.9 The Contractor shall provide logistics support for items, systems, methods, procedures, and processes at both the BGIF and OPIR TAP Lab. Logistics support may occur during development and/or as a follow-on activity to development. Logistics support includes BGIF and OPIR TAP Lab operations, facility management, interim Contractor support, extended engineering support, extended testing support, supplies, maintenance, repairs, maintenance training, and validation and correction of data.

4.1.2 Financial Management

4.1.2.1 The Contractor shall deliver Contract Funds Status Reports (CFSR) for the overall contract (CDRL A002) on a monthly basis.

4.1.2.2 The Contractor shall seek email authorization from the Government BOSS COR for all procurements prior to executing them. This email shall denote the procurement name, quantity, purpose, requesting team, program supported, item cost and total cost.

4.1.2.3 The Contractor shall develop and deliver a quarterly procurement report starting at ATP+90 days (CDRL A003) denoting all procurements made in the previous three months accompanying a DD Form 1149 for Government signature.

4.1.2.4 The Contractor shall deliver a complete Held GFP list to the Government on an annual basis in the Government prescribed format. (CDRL A004). The list shall describe all GFP being held by the Contractor in the execution of the contract.

4.1.3 Security Management

4.1.3.1 The Contractor shall provide personnel with the appropriate clearances for all positions described in the PWS according to the Contractor Proposed Staffing Matrix.

4.1.3.2 The Contractor shall report immediately upon discovery to an appropriate OPIR TAP Lab/BGIF/OBAC Government authority any information or circumstances which they are aware of that may pose a physical threat to the security of personnel, resources and classified or controlled unclassified defense information assigned to or resident at OPIR TAP Lab/BGIF/OBAC. The Contractor shall immediately notify the OPIR TAP Lab/BGIF/OBAC Government Security Office and PCO of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified and/or controlled information.

4.1.3.3 The Contractor shall ensure required security clearances are obtained and maintained by the Contractor personnel assigned to support this PWS. Contractor shall submit the required security clearance artifacts for Government approval for these personnel. Personnel requiring a clearance must be eligible prior to commencing work on this contract but are not required to be on an active cleared position prior to commencing work on this contract. The Contractor shall complete visit requests to the necessary secure work locations using the Joint Personnel Adjudication System (JPAS), for each individual assigned to perform work on this contract, prior to the individual beginning contract performance.

4.1.3.4 BGIF access requires a minimum Interim Secret security clearance. A portion of the BGIF requires TS/SCI clearance. OPIR TAP Lab at GoG requires TBD access. OBAC access requires TS/SCI clearance. As a result of these security restrictions, 100% of the Contractor's personnel assigned to the contract must have at least Interim Secret clearance. In addition, all personnel assigned tasks at the OBAC or in the BGIF SCIF shall have and maintain TS/SCI clearances/access to perform their associated infrastructure operations, maintenance, stakeholder engagement, administration and cyber security roles and responsibilities. Limited exceptions with escort are reserved for short duration tasks by temporary vendors or subcontractors, e.g. equipment installation or repair.

4.1.3.5 At a minimum 50% of security guard staff at the BGIF shall have and maintain TS/SCI clearances/access in order to perform physical and personnel security monitoring services. This includes accessing BGIF TS/SCI facilities to conduct routine physical and personnel health security checks associated with maintaining SCI facility control during emergency responses from police, fire or other emergency responses to alarms, natural disasters, and/or personnel health emergencies. Contractor shall ensure a TS/SCI-cleared security guard is available on 2-hour recall for emergency scenarios.

4.1.3.6 The Contractor shall ensure compliance with all applicable national information security program policies and procedures to include local facility Standard Operating Procedures (SOPs), Emergency Action Plans (EAPs), and Security Classification Guides (SCGs) to ensure proper classification, safeguarding, declassification and destruction of classified information and materials.

4.1.3.7 The Contractor shall flow down to all of its subcontractors the security requirements in this contract to include but not limited to a completed and Government-approved DD 254 for each subcontractor the BOSS contractor places on the contract.

4.1.3.8 The Contractor shall ensure all Contractor personnel take the Government activity’s initial and reoccurring security training IAW AFI 31-401, Information Security Program Management, Chapter 8; AFI 31-601, Industrial Security Program Management, Chapter 3, AFI 10-701, Operations Security, Chapter 5, the Visitor Group Security Agreement, Training Section, and any other Government-required training in order to maintain required Security Clearances.

4.1.3.9 The Contractor shall ensure its personnel do not possess weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately-owned vehicle while on any installation or any office/working location covered under this contract.

4.1.3.10 The Contractor shall provide a secret-cleared identity proofing and badging officer to provide personnel access control support for the BGIF. This position shall support the BGIF visitor badging nominally 0700-1500 local time on weekdays (not including Government holidays when the BGIF is typically closed). The position shall issue temporary badges for short term visitors to the BGIF. The position shall issue permanent badges to authorized personnel and coordinate with the OPIR TAP Lab/BGIF Special Security Representatives (SSR) and the GoG Security staff as required, to have the permanent badges activated for use within the authorized areas of the facility.

4.1.3.11 The Contractor shall comply with local base procedures for entry to Air Force/Space Force controlled or restricted areas and sensitive compartmented information facilities where Contractor personnel shall work. The Government will complete an AF Form 2586, Unescorted Entry Authorization Certificate, completed and signed by the sponsoring agency’s Security Manager, before a Restricted Area Badge will be issued. Contractor employees shall have a favorably completed National Agency Check plus written Inquiries (NACI) investigation before receiving a Restricted Area Badge. Interim access may be granted IAW AFI 31-501, Personnel Security Program Management. Contractor personnel must have appropriate clearances prior to commencing work on this contract unless otherwise approved in writing by the PCO.

4.1.3.12 The Contractor shall comply with the U.S. State Department’s International Traffic in Arms. Regulations (ITAR) (22 CFR Parts 120-130 and Amendments), the Arms Export Control Act, Defense Trade Security Initiatives, State Department, USAF, and Department of Defense policies relative to the ITAR and exporting and importing data especially for non FMS cases. The Contractor shall obtain a Trade Agreement Act (TAA) with each of the foreign nations identified by the Contracting Officer Representative (COR) at the time of any resulting contract and for the duration of this contract within 90-120 days after notification, with the appropriate agencies, such as the Department of State, to export and receive technical data (direct commercial sales) in order to perform this contract. The Contractor shall maintain the TAA for the duration of the contract. The Contractor personnel shall have no direct contact with foreign nationals until ITAR requirements are met.

4.1.3.13 The Contractor shall comply with the requirements of the Directorate of Defense Trade Controls (DDTC) and the ITAR as it applies to defense services for FMS cases, including maintenance of registration with DDTC for the entire time that the defense service is being provided. Note: The Contractor shall facilitate Defense services to foreign parties with the USAF. The Contractor and its individual employees assigned to provide FMS support shall be cognizant of those sections of the ITAR 126.6(c)(7) that apply to assigned activities.

4.1.3.14 The Contractor shall comply with DD Form 254 requirements. The Government will oversee handling and storage of classified information. All classified information shall be returned to the Government upon termination of this contract. Access to SIPRNET is required and will be furnished to the Contractor for this effort.

4.1.3.15 The Contractor shall comply with all Department of Defense (DoD) Cyberspace Computer Security (COMPUSEC) policies, manuals, directives and procedures.

4.1.4 Subcontractor Management

4.1.4.1 The Contractor shall be responsible for any subcontract management necessary to integrate work performed on this contract and shall be responsible and accountable for subcontractor performance on this contract.

4.1.5 Work Management

4.1.5.1 The Contractor shall manage and coordinate development, integration and delivery cadence amongst product teams (including 3rd party application vendors) using Agile or other industry standard software development methodologies and create and maintain integration and delivery schedules for concurrent BGIF and OPIR TAP Lab activities. The Contractor shall develop and deliver regular updates to the Government during program reviews and when requested by the Government.

4.1.5.2 The Contractor shall support Technical Interchange Meetings (TIMs), working groups, external visits and other meetings as requested by the Government. The Contractor shall be responsible for developing and coordinating agendas, pre-planning with external visitors (e.g. VAR process, BGIF/GoG visit logistics/entry procedures, scheduling meeting spaces, preparing and providing presentations and demonstrations, setting up the IT environment, providing logistical and technical support, documenting minutes and actions items, and completing follow-up actions as required. Historically, events of this type occur on average four (4) times/month.

4.1.5.3 The Contractor shall provide a Chief Scrum Master or similar position whose function is to organize, plan, and lead work management functions for the OPIR TAP Lab and BGIF product teams.