BOSS - Performance Work Statement.pdf

Space Systems Command, Space Sensing Directorate, Strategic Missile Warning Ground Acquisition Delta, Data Exploitation and Tools, Applications and

Processing Laboratory (TAP Lab)

(SSC/SNGT)

Boulder Ground Innovation Facility (BGIF)

Operations Support Services (BOSS) Contract

Attachment 1

Performance Work Statement (PWS)

7 August 2024

TABLE OF CONTENTS

1.0 Overview and Background

1.1 Executive Overview

1.2 Background

1.3 BGIF & OPIR TAP Lab Infrastructure Overviews

1.4 Contractor Work Locations

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 Functions

3.4 Ethics

4.0 Performance Requirements

4.1 Program Management and ODCs 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 Tenant Support

4.2.4 Network Support

4.2.5 Security Support

4.2.6 Configuration Management

4.2.7 BGIF “Ops”

4.2.8 ISP Procurement

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 Configuration Management

4.3.5 Cloud Support

4.3.6 Security Support

4.3.7 Cyber Security Support

4.3.8 Data Management

4.3.9 OPIR TAP Lab Ops

4.3.10 Requirements Support

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

4.3.12 Capability Integration

4.3.13 Capability Transition

4.3.14 Travel

4.4 OBAC Requirements

4.4.1 Engineering Services

4.4.2 Network Support

4.4.3 TAC Support

5.0 Contract Management

5.1 Management of Personnel

5.2 Training

5.3 Identification

5.4 Places of Performance

5.5 Federal Holidays

5.6 Business Relations

5.7 Subcontract Management

5.8 Cost Control

5.9 Contract Accounting

5.10 Temporary Duty (TDY) Travel

5.11 Associate Contractor Agreement (ACA)

5.12 Interfacing with Aerospace Corporation Contact Support

5.13 Contractor Responsibility Watch List (CRWL)

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/Facilities

7.1 Utilities

7.2 Facilities

7.3 Protection from Loss

8.0 Deliverables

9.0 Acronym List

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 purpose of this PWS is to describe the performance objectives, tasks and functions for technology exploration and development, facility operations and management, and Information Technology (IT) services for the Space Systems Command (SSC), Space Sensing Directorate, Strategic Missile Warning Ground Acquisition Delta (SNG), Overhead Persistent Infrared (OPIR) Tools, Applications and Processing Laboratory (OPIR TAP Lab), Boulder Ground Innovation Facility (BGIF) and specific engineering support at the OPIR Battlespace Awareness Center (OBAC). SSC/SNGT is the Government Director for the following activities:

SSC/SNGT OPIR TAP Lab 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. 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 OPIR TAP Lab is a Geographically Separated Unit (GSU) to SSC at Los Angeles Air Force Base, California.

SSC/SNGT leadership manages the OPIR TAP Lab and also manages the BGIF. BGIF is an SSC asset. The BGIF is the Government-controlled, Government-operated facility and facility infrastructure at Boulder, Colorado. The OPIR TAP Lab is a BGIF tenant and manages the BGIF to include the physical facility and lease, infrastructure, security, and administration. In addition to the OPIR TAP Lab, the BGIF houses other tenant programs that perform development, test, and operational activities.

SSC/SNGT leadership manages specific engineering support to the OBAC. The OBAC is a facility within the Space Based Infrared System (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 and 26 IS are the primary operational users for capabilities the OPIR TAP Lab develops and deploys for use within the OBAC, but additional customers can include other military organizations, Intelligence Community (IC) organizations and foreign mission partners.

The Technical Analysis Cell (TAC) is also located within the OBAC. TAC is staffed by Aerospace Corporation (Federally Funded Research and Development Corporation; FFRDC) OPIR Subject Matter Experts (SME) who work under the direction of SSC/SNGT to execute special data analysis for several high visibility missions under day-to-day direction of Commander, 11 SWS (11 SWS/CC). TAC is currently a part of the support umbrella for this contract and the SSC/SNGT OPIR TAP Lab, but this could change prior to contract award.

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

The SSC/SNGT Government OPIR TAP Lab Director also serves as BGIF Director from a facility leasing and infrastructure management perspective.

The Boulder and OBAC Support Services (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.

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

From a general scope perspective, the Contractor responsibilities encompass the overall BGIF facility leasing, infrastructure, security alarms, badging and management functions while specifically providing the SSC/SNGT OPIR TAP Lab program’s overall IT support services. The IT support services enable SSC/SNGT OPIR TAP Lab to execute the lab’s RDT&E mission focused on developing software applications designed for the primary 11 SWS and 26 IS Missile Warning (MW), Battlespace Awareness (BA) and Technical Intelligence (TI) mission areas.

1.2 Background

SSC/Space Sensing Directorate (SSC/SN) develops, acquires and sustains space and ground systems to provide global, persistent, infrared surveillance and environmental monitoring capabilities to the warfighter and the nation for MW, BA, TI, Missile Tracking (MT), Missile Defense (MD) and Weather missions.

The Government established the OPIR TAP Lab at Boulder in 2016 to pursue activities designed to enable enhanced exploitation and dissemination of OPIR and environmental monitoring (weather) data from space sensors developed by Space and Missile Systems Center (SMC; predecessor to SSC) and other organizations. The OPIR TAP Lab implemented a model to promote competition and collaboration between algorithm developers and allow plug-and-play of different mission data processing applications followed by deployment of selected applications to OBAC. The OPIR TAP Lab and OBAC users are USSF units, however, the intent was to develop data exploitation technologies, software algorithms and applications for other services, agencies, and non-military users, such as civil, environmental, and other non-traditional users.

“OPIR TAP Lab” originally designated both the RDT&E organization and the physical facility and facility infrastructure at the Boulder site. However, in February 2024 the Government re-designated the facility and infrastructure “BGIF.” This action differentiated the OPIR TAP Lab organization and its primary RDT&E mission focus from the BGIF physical spaces, infrastructure and support structures that host both OPIR TAP Lab RDT&E and other SSC programs conducting near-operational activities.

In addition to supporting the OPIR TAP Lab’s RDT&E mission, the BGIF hosts both integrated systems that leverage parts and pieces of the OPIR TAP Lab’s resources and infrastructure, as well as major standalone tenant programs. Standalone tenants leverage the BGIF facility but not the OPIR TAP Lab’s resources. Integrated systems include the geosynchronous Wide Field of View

(WFOV) OPIR testbed, a standalone instance of the Future Operationally Responsive Ground Enterprise (FORGE) used for development, and a prototype mission data processing for the Space Development Agency (SDA). The OPIR TAP Lab supports development and operationalization of these integrated systems. The BGIFs major tenant programs include: Next Generation Geosynchronous (NGG) Interim Control Center (NICC), FORGE development and test, and a hardware sustainment function related to the SBIRS program. The BGIF has allocated space and supporting infrastructure for the Resilient MW/MT Medium Earth Orbit (MEO) Ground program to fit up a spacecraft operations center to support their Epochs 1 and 2.

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

Figure 1 – High-level BGIF & OBAC Overview

NGG 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 the BGIF provides reliable infrastructure support and quick response times to any potential mission-impacting facility/infrastructure contingencies. This increased timely support requirement is a change from the previous contract.

The Government is transitioning to FORGE. FORGE provides a common architectural framework (Mission Data Processing Architecture Framework; MDPAF) and mission processing applications (Mission Data Processing Applications; MDPAP) in SBIRS MCS and other sites supporting the USSF OPIR missions. The OPIR TAP Lab plans to retire legacy Sensor Open Framework Architecture (SOFA; software framework) and Sensor Exploitation Ground Architecture (SEGA;

hardware framework) and replace them with FORGE MDPAF prior to BOSS contract start, however that transition may be ongoing when the contract is awarded. In this PWS, FORGE should not be considered a third-party application.

The SSC/SNGT Government Director has organized OPIR TAP Lab and BGIF using “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 contractors to assign individual team members to product teams 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), A&AS and support services contractors (such as 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 2 – Notional 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 BGIF (and is also a BGIF tenant). The Government sub-leases BGIF spaces. This mission includes the full scope of facility and infrastructure operations sufficient to support OPIR TAP Lab RDT&E plus multiple integrated systems and tenant programs. The operations include maintenance of two on-prem server rooms, a power room with full redundancy and three external diesel generators. Due to the 24/7 near-operational nature of some tenant missions, keeping BGIF continuously online is a focus area of this contract.

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. This mission includes, but is not limited to, identifying and advancing technologies such as Artificial Intelligence/Machine Learning (AI/ML), data fusion and process 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 both an unclassified hardware enclave and a collateral Secret hardware enclave, both 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). From a cybersecurity perspective these requirements include maintaining Authorities to Operate (ATO) using eMASS or XACTA (secure, web-based tools used to manage cybersecurity data, workflow and reports) for at least four separate enclaves with two ATOs 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 Overviews

Figure 3 – BGIF and OPIR TAP LAB Infrastructure Overview

Figure 3. 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.

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

1.4 Contractor Work Locations

The OPIR TAP Lab and BGIF are co-located in sub-leased space in Boulder, Colorado. The OBAC is located within the SBIRS MCS at Buckley SFB, Colorado. The Government is considering extending the OPIR TAP Lab presence to the Garden of the Gods (GoG) Government-leased, Government-managed facility in Colorado Springs, Colorado.

Physical addresses of the facilities are:

• OPIR TAP Lab and BFIG: 6304 Spine Rd, Boulder CO 80301

• OBAC: 18300 E. Crested Butte Ave, Buckley SFB CO 80011

• GoG: 2424 Garden of Gods Rd, Colorado Springs, CO 80919 (tentative plan only)

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

• Wide Field of View (WFOV), 17 May 2022

• Next Gen OPIR SCG, 2 Mar 2021

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, and OBAC.

The Contractor will 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 facility, infrastructure and technical baseline the SSC/SNGT OPIR TAP Lab uses to execute its RDT&E mission. BGIF also hosts integrated systems plus other tenant programs that perform development, test, and operational type activities. BOSS Contractor support for BGIF includes (listed in order of priority): facility maintenance (power/HVAC), logistics, sustainment, physical security, and engineering. The Contractor will provide these support services for the facility and the OPIR TAP Lab, but not for other individual tenant programs.

• Second, SSC/SNGT OPIR TAP Lab at Boulder, CO is the Government organization with primary mission to perform RDT&E to explore, develop, advance, test and deploy innovative data exploitation and processing technologies, capabilities and software applications. Goal of the RDT&E activities is to enhance processing of not only space-based remote sensor OPIR, but also future proliferated sensors and other mission data and dissemination of the resulting information products to operational users. BOSS Contractor support for OPIR TAP Lab includes (listed in order of priority): cybersecurity, systems engineering, architecture engineering, integration, deployment, and software development services.

• Third, SSC/SNGT OPIR TAP Lab supports specific capabilities at the OBAC. These capabilities include developmental capabilities for 11 SWS and 26 IS plus special data analysis functions at the TAC. Data exploitation RDT&E the OPIR TAP Lab conducts at BGIF directly supports capability enhancements with 11 SWS and 26 IS. BOSS Contractor support for OBAC includes (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) 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.

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

4.1 Program Management and ODCs 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 a program manager, as one of the key personnel on the contract, 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.

4.1.1.1.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.2 The Contractor shall manage work distribution to ensure there is no Organizational Conflicts of Interest (OCI). 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.3 The Contractor shall conduct monthly Program Management Reviews (PMRs).

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.4 The Contractor shall develop and deliver the Monthly Status Report (MSR) (CDRL XX). The Contractor shall document development status, issues, concerns, monthly funds status, etc. in the MSR for the overall contract.

4.1.1.5 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.1.6 Upon request by the government the Contractor shall negotiate with tenant program contractors to accomplish non-disclosure agreements of other forms of OCI mitigation for BOSS contract personnel.

4.1.1.7 The Contractor is responsible for obtaining all non-disclosure agreements 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.2 Financial Management

4.1.2.1 The Contractor shall develop and deliver Contract Funds Status Reports (CFSRs) for the overall contract (CDRL XX).

4.1.2.2 The Contractor shall seek email authorization from the government BOSS PM for all procurements prior to executing them.

4.1.2.3 The Contractor shall develop and deliver a procurement report (CDRL XX) within five days after each purchase.

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

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. 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 least 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) 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 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 Release Train Engineer (RTE) or similar function to organize, plan, and lead work management functions for the OPIR TAP Lab and BGIF. Duties include, but are not limited to, identifying and recommending work tasks/projects that are appropriate for work management tracking and analysis, coordinating among SSC/SNGT teams at the BGIF, recommending suitable work metrics, leading collection and analysis of work task data, and reporting to the Government as required.

4.1.5.3.1 The RTE or similar function shall have at least a bachelor's degree in

Engineering or a technical field, at least 10 years industry-related experience, plus intermediate or higher training and certification in Agile or other appropriate work management methodologies.

4.1.5.4 Access to classified national security information up to TS/SCI is required under this contract. The Contractor shall comply with the contract security requirements and Contractor access to classified information as specified in the contract attachment DD Form 254. The Contractor shall immediately report any cost savings or cost impacts per NISPOM to the contracting officer. All classified material will remain under the control of the Space Force including disposition of any classified material at the completion of the contract.

4.1.5.5 Contractor performance at each location involving Sensitive Compartmented Information (SCI) will be under the exclusive security oversight of the respective Special Security Office at that base.

4.1.5.6 The Contractor shall submit personnel security investigative paperwork for trustworthiness determinations IAW Air Force Instruction (AFI) 31-601, Industrial Security Program Management, Paragraph 2.4. Trustworthy determinations are required for access to Unclassified Government Information Technology (IT) systems.

4.1.5.7 The Contractor shall enter into a Contractor Visitor Group Security Agreement, as determined by the Government, in the DISS and Joint Personnel Adjudication System (JPAS) for any efforts to be performed on Buckley SFB, CO. The Agreement will outline responsibilities in the following areas: Contractor security supervision; Standard Practice Procedures; access, accountability, storage, and transmission of classified material; marking requirements; security education; personnel security clearances; reports; security checks; security guidance; emergency protection; protection of Government resources; DD Forms 254; periodic security inspections; end of day security checks IAW the organizational Visitor Group Security Agreement.

4.1.5.8 The Contractor shall ensure Contractor personnel in-process with the facility unit security manager/information systems security officer on the first duty day in the Government facility, and out-process with the unit security manager/information systems security officer no later than the period of performance end date of this contract, or no later than the last duty day in the Government facility, in which the earliest occurrence will take precedence. Contractor personnel shall repeat this process with this contract regardless of if the employee is employed with the same Contractor, or the task performance occurs within the same Government facility. This process will facilitate issuance/retrieval of Controlled Area Badges and Common Access Cards (CAC), issuance/termination of computer accounts and building accesses.

4.1.5.9 The Contractor shall safeguard information and report cyber incidents as soon as discovered in accordance with BGIF guidance policy, SOP, applicable regulations, and Government security requirements.

4.1.5.10 The Contractor shall permit the PCO or authorized representative access to all work areas, records, and data used in the performance of this contract. The Contractor shall provide support and not interfere with Government personnel in the performance of their official duties. Access shall be provided as soon as possible, but will not exceed one (1) workday after the request.

4.1.5.11 The Contractor shall comply with DoD 5400.7-R/Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program, requirements. This regulation sets policy and procedures for the disclosure of records to the public.

See DoD 5200.1-R, Vol 4, Information Security, Program, Appendix 3 and DoD Instruction 5200.48, CUI, and the Air Force Guidance memorandum (AFGM) 2020-16-01 CUI, for marking, handling, transmitting and safeguarding Controlled Unclassified Information (CUI) material.

4.1.5.12 The Contractor shall control access to all Government-provided lock combinations to prevent unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

4.1.5.13 The Contractor shall obtain a final U.S. Government clearance at the appropriate level before obtaining access to RESTRICTED DATA and FORMERLY RESTRICTED DATA. (validate this is valid with the PCO, PM team did not add this to the TLOSS contract, it came from contracting)

4.1.5.14 The Contractor shall support routine Government compliance audits to validate safeguards implemented to protect Covered Defense Information (CDI) at all covered Contractor locations. A Government-selected representative will perform the audits. The Government will provide written notification at least 30 calendar days prior to performing a routine audit.

4.2 BGIF Requirements

Section 4.2 describes the requirements of the BOSS contractor related to BGIF operations and maintenance as well as the integration and hosting of tenants at the facility.

4.2.1 Engineering Services

4.2.1.1 The Contractor shall provide a Chief Systems Engineer to oversee all system engineering efforts in support of the tasks in this PWS. Duties include, but are not limited to defining and prioritizing technical requirements, conducting system engineering trade studies, translating requirements into viable solutions, and recommending engineering and technology investment courses of action based on the studies. Investments include, but are not limited to, exploring, advancing and implementing technologies such as AI/ML, fusion of data sources and automation to address stressing challenges and leverage evolving technology trends when appropriate. The Chief System Engineer shall coordinate with OPIR

TAP Lab and BGIF stakeholders, including tenants, to manage a strategic roadmap for TAP Lab and BGIF integration activities that addresses deconfliction of activities, recapitalization/tech refresh and new capability investments, efficiency improvements and other factors to drive efficiencies and contain life cycle costs. The Chief Systems engineer shall support the BGIF and the OPIR TAP Lab.

4.2.1.1.1 The Chief System Engineer shall have at least a master’s degree in engineering, science, technology management or related IT field, at least 10 years industry-related experience including at least 5 years software development, test, and/or integration of capabilities into operational DoD or other national security facilities (industry and/or Government roles) and possess a current TS clearance with SCI eligibility.

4.2.1.2 The Contractor shall provide a Chief Architect to oversee and plan enterprise-level evolution of the consolidated OPIR TAP Lab/BGIF/OBAC hardware/software technical baseline. Duties include, but are not limited to, ensuring the OPIR TAP Lab/BGIF/OBAC hardware/software baseline is documented, leading identification of architecture level risks, issues and opportunities, convening and running working groups (standing or temporary) when necessary to conduct studies, trades and develop solutions, developing and recommending long-term (3+ years) investments to meet strategic direction.

4.2.1.2.1 The Chief Architecture shall have at least a master’s degree in engineering, computer science or related IT field, at least 15 years industry-related experience including at least 10 years software development, integration and/or test into operational DoD or other national security facilities (industry and/or Government roles), and a current TS clearance with SCI eligibility.

4.2.1.3 The Contractor shall maintain and update the OPIR TAP Lab and BGIF System

Engineering Management Plan annually or as required by the government.

4.2.1.4 The Contractor shall provide network engineering services. This includes, but is not limited to, technical support to all intra enclave and external network (WAN/LAN) connectivity at the BGIF. BGIF currently has network interfaces to NIPR, SIPR, RTS, PWAN (Blossom Point Tracking Facility, MD link supporting WFOV tenant program), GWAN, and the SBIRS Analytical Sub-Elements (ASE). Future interfaces will include JWICS. The Contractor shall provide support for the BGIF up to the communications demarcation.