ATCH 01_C-SAR TO1_PWS.pdf

FA8823-24-F-0000 Attachment 1 C-SAR Task Order 1: PWS

PERFORMANCE WORK STATEMENT (PWS)

FOR

COMMAND AND CONTROL SYSTEM – CONSOLIDATED

(CCS-C)

SUSTAINMENT AND RESILIENCY (C-SAR)

CORE SUSTAINMENT AND OPERATIONS SUPPORT TASK

ORDER

VERSION 1.0 – 9 MARCH 2023

Prepared by:

SSC

1050 E. Stewart Ave.

Peterson SFB, CO 80914

TABLE OF CONTENTS

Contents

CONTENTS

1 INTRODUCTION

1.1 SSC/CGM MISSION

1.2 BACKGROUND

1.3 OVERVIEW

2 APPLICABLE DOCUMENTS

3 SPECIFIC REQUIREMENTS

3.1 PROGRAM MANAGEMENT. THE CONTRACTOR SHALL:

3.2 ORGANIZATIONAL AND INTERMEDIATE LEVEL MAINTENANCE. THE CONTRACTOR SHALL:

3.3 CONTRACTOR LOGISTICS SUPPORT AND NETWORK COMMUNICATIONS MAINTENANCE. THE CONTRACTOR SHALL:

3.4 SYSTEMS ENGINEERING. THE CONTRACTOR SHALL:

3.5 DEPOT LEVEL SOFTWARE MAINTENANCE. THE CONTRACTOR SHALL:

3.6 TEST FACILITIES SUPPORT. THE CONTRACTOR SHALL:

3.7 CYBERSECURITY ENGINEERING SUPPORT. THE CONTRACTOR SHALL:

3.8 SAFETY. THE CONTRACTOR SHALL:

3.9 120-DAY TASK ORDER PHASE-IN ACTIVITIES. THE CONTRACTOR SHALL:

CONTRACTOR DATA REQUIREMENTS LISTS (CDRL)

1 Introduction The Space Systems Command (SSC) supports operation of military satellites to ensure continuous, uninterrupted, secure, and anti-jam communications for the warfighter. SCC collaborates with operational customers and supports suppliers to provide timely operations capabilities across the full spectrum of conflict.

1.1 SSC/CGM Mission

SSC develops, acquires, equips, fields, and sustains lethal and resilient space capabilities.

1.2 Background

The CCS-C system provides United States Space Force (USSF) and United States Space Command (USSPACECOM) satellite control capabilities. Current programs include the Defense Satellite Communications System (DSCS) III, Milstar Satellite Communications System, Advanced Extremely High Frequency (AEHF), and Wideband Global Satellite (WGS) Communication Systems. Quantities of each satellite family are defined in the CCS-C System/Subsystem Specification. Other satellite families or programs, and network modifications and upgrades may be included in the future. Capabilities include mission, activity, and maneuver planning; telemetry processing; commanding; orbit and attitude management; resource management; space vehicle and ground system simulation; support planning and execution; and interfaces with dedicated ground and payload control systems. Satellite platform and payload state-of-health operations include launch, early-orbit, on-orbit operations, anomaly resolution, and disposal operations. CCS-C provides information assurance measures to ensure that unclassified and SECRET data processed in all areas is protected. Primary operational systems are located at Schriever Space Force Base (SFB) (SSFB), CO and alternate systems are located at Vandenberg SFB, CA; with a test facility located at Peterson SFB (PSFB), CO.

1.3 Overview

Note: “Software” throughout this PWS refers to software and all related data products.

During the performance of this Task Order, the contractor shall provide the following services:

• Sustain the current CCS-C System to meet the requirements in the CCS-C System/Subsystem Specification (SSS).

• Provide Program Management ensuring effective management of resources to meet technical objectives on schedule and within budget.

• Provide depot level software maintenance support, including installation and testing of all upgrades, for the Space Operations Center (SOC) at Schriever SFB and Backup Space Operations Center – Vandenberg (BSOC-V).

• Provide organizational level hardware and software maintenance support.

• Provide System and Software Engineering for the CCS-C system, including enhancements or development related to cybersecurity resilience and new capabilities, and specifications derived from the baseline system specification.

• Provide Technical Order (TO) support functions for CCS-C TOs.

• Establish and maintain Configuration Management to ensure compliance with design and performance requirements.

• Maintain and support Government owned Test Facilities and Development Laboratory equipment at the Secret level.

• Provide Sustaining Engineering support to include reliability/maintainability/availability (RMA) data analysis, RMA model and simulation updates, obsolescence analysis, and recurring cybersecurity support for the CCS-C system and test assets/support facilities.

• Provide seamless support to satellite operations during the transition from the CCS-C Production and Sustainment Contract (CPASC) contract to C-SAR contract.

2 Applicable Documents The contractor shall refer to the C-SAR IDIQ Attachment 12 for the applicable Compliance and Reference Documents. There are no additional applicable documents necessary for this Task Order.

3 Specific Requirements The following sections specify the Performance Objectives and Performance Elements for the contract.

NOTE: When “contractor format” is referenced throughout paragraphs 3.1-3.9, the contractor shall provide a contractor generated, consistent, open-standard format, unless otherwise agreed to by the Government.

3.1 Program Management. The contractor shall:

Program Management tasks shall integrate work across all open task/delivery orders under the C-

SAR IDIQ.

3.1.1 Identify and maintain all CCS-C licenses, service contracts, warranties and subscription services.

Performance Standards

STD #1: Obtain licenses according to the order of precedence of DoD license agreements as directed by the Government.

STD #2: Notify the Government representative via e-mail when renewal of licenses, service contracts, warranties and subscription services are complete.

STD #3: Annually, at the end of the fiscal year, and in contractor format, provide the Government representative a detailed list of all licenses, service contracts, warranties and subscription services including expiration dates.

Contract Data Requirements List (CDRL(s)) N/A

3.1.2 Provide approximately four engineering (cost and hours) Rough Order of Magnitude (ROM) estimates annually for any changes to hardware, software or operations and maintenance procedures upon request from the Procuring Contracting Officer (PCO). ROM development should not exceed 640 hours annually in total. These ROMs are separate from actual proposals that will be reimbursed under CLIN X012 Proposal Preparation.

Performance Standards

STD #1: Produce and deliver estimates, in contractor format, within 30 calendar days of the PCO request.

STD #2: Provide the Government access to ROMs by notifying the Government once the ROM is available via a contractor managed file sharing site.

CDRL(s) N/A

3.1.3 Maintain a resource loaded schedule for hardware/software releases, system modifications, patch releases, Risk Management Framework (RMF) artifact deliveries IAW 3.7.3 of this PWS, testing, and other maintenance actions.

Performance Standards

STD #1: Manage and obtain Government approval of the schedule through the weekly Schedule and Prioritization Working Group (SAPWG).

STD #2: Maintain the schedule on a contractor managed share site and notify the Government via e-mail with an updated version on a weekly basis.

CDRL(s) N/A

3.1.4 Prepare for and brief the technical status of program management, schedule, risk management, accomplishments, issues and upcoming events for all PWS tasks in the CCS-C Program Management Review (PMR).

Performance Standards

STD #1: Conduct the PMR with the Government quarterly.

STD #2: Post the meeting charts (to include the PMR agenda) to a contractor managed file sharing site and notify the Government via e-mail of their location at least five business days before the meeting.

STD #3: Post the meeting minutes to a contractor managed file sharing site and notify the Government via e-mail of their location within five business days after meeting.

CDRL(s) N/A

3.1.5 Provide program management and technical support for reoccurring meetings.

STD #1: Provide support for the weekly Program Management Integrated Product Team (PM-IPT) meetings, to include all technical presentations.

STD #2 Post the meeting minutes to a contractor managed file sharing site and notify the Government via e-mail of their location within 3 business days after meeting.

CDRL(s) N/A

3.1.6 Provide PM support for 1 hour ad hoc meetings including, but not limited to, Technical Interchange Meetings (TIMs), Interface Control Working Groups (ICWGs), and other technical forums.

Performance Standards STD #1: Provide PM support for approximately 50 ad hoc meetings per year.

CDRL(s) N/A

3.1.7 Systematically collect and report actual contract costs for cost reimbursable CLINs.

Contractor reports shall be prepared in accordance with the instructions contained in the most recently approved versions of DI-FNCL 82162 and DI-FNCL-81765 IAW DODI 5000.02 and DFARS 252.234-7003, Notice of Cost and Software Reporting System.

Performance Standards

STD #1: Use a documented standard Cost and Software Data Reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04–M–1, CSDR Manual; and provides for generation of timely and reliable information.

STD #2: Use the Government-approved CSDR plan for this contract, DD Form 2794, and related Resource Distribution Table for reporting IAW CSDR Data Item Descriptions (DIDs).

STD #3: The Contractor shall require and flow down the requirement for CSDR reporting from subcontractors with a subcontract that exceeds $50 million or any subcontracts valued between $20 million and $49 million that are designated by the Government as being high risk, high value, or high technical interest.

STD #4: For any non-firm fixed price CLINs, submit an Integrated Program Management Report (IPMR) and a Contract Funds Status Report (CFSR) consistent with the Office of the Secretary of Defense (OSD) Central Repository for Earned Value Management (EVM) Data Policy Manual functional requirements and a Performance and Cost Report (PCR).

CDRL(s) A001, Contract Work Breakdown Structure (CWBS) A002, Contract Funds Status Report (CFSR) A003, Cost and Hour Report (FlexFile), Contractor Cost Data Reporting (CCDR) A004, Software Resources Data Reporting (SRDR), Software Maintenance Report A005, DoD Requirement Report to USC 2466 (50/50) A006, Technical Data Report A007, Contractor Cost Data Reporting 1921-3 Report A008, Integrated Program Management Report (IPMR) Formats 1, 5, and 6

3.1.8 Maintain equipment accountability of the following:

• All GFP listed in the GFP List (IDIQ attachment 17)

• All system hardware within the CCS-C system baseline

STD #1: Maintain all GFP IAW FAR Part 45 and DFARS Part 245 to include Financial Improvement and Audit Remediation (FIAR) requirements.

STD #2: Work with Tobyhanna Army Depot (TYAD) for all depot level hardware repair and replacement actions.

STD #3: Work with TYAD, as required, for all intermediate level hardware repair and replacement actions.

STD #4: Conduct a GFP inventory audit, and system baseline equipment inventory audit, and provide a Government Property Inventory Report for each, annually.

CDRL(s) A009, Government Property Inventory Report (GPIR)_GFP A014, Government Property Inventory Report (GPIR)_System Config

3.1.9 Maintain a contractor managed share site & data repository for all task/delivery orders.

Performance Standards

STD #1: Ensure the repository reflects the most current version of Task Order deliverables except engineering drawings.

STD #2: Administer the repository including management of users, groups, and permissions.

STD #3: Ensure the repository reflects the most current versions of CCS-C Contract baselined specifications, reports, and documents listed in the CDRL.

STD #4: Conduct annual data reduction and clean-up on the repository.

STD #5: Provide, in contractor format, a recommended list of data reduction items for the Government’s review prior to deletion.

STD #6: Ensure the repository is up to date and functional for Government access a minimum of 20 hours per week during standard working hours.

STD #7: The repository shall provide data protection up to the Controlled Unclassified Information (CUI) level and include two-factor authentication IAW DoDI 8520.03, Enclosure 3, 2.c.4 and 3.b.5.

CDRL(s) N/A

3.1.10 Provide the technical and functional activities needed at the Task Order level to accomplish the C-SAR program cost, schedule and performance objectives.

Performance Standards

STD #1: Provide program management oversight, planning and control, contract and subcontract management, Configuration Management (CM) and Data Management (DM), security and administrative support

STD #2: Provide technical management and administrative support required to execute the C-SAR contractual tasks.

STD #3: Provide a Small Business Subcontractor Report on supporting small business.

STD #4: Implement efficiencies, process improvements, cost reduction initiatives throughout the period of performance.

STD #5: Maintain a list of estimates and impacts for Government use in funding prioritization.

STD #6 Provide timely notice of variances to the Government in order to reprioritize requirements to stay within specified contractual obligations and negotiated dollar thresholds.

STD #7 Provide a weekly activity report to SSC/CGM, in contractor format, via email.

STD #8: Execute contract management across all of the Task Orders, incorporating risk reduction, opportunity analysis, and enterprise wide technical solutions.

CDRL(s)

A010, Small Business Subcontractor Report A011, Data Accession List (DAL) A012, Engineering Change Proposals

3.1.11 Meet the Public Private Partnership (PPP) requirement (IDIQ PWS 2.4.3) with the Ogden Air Logistics Complex (OO-ALC)/309th Software Engineering Group (309 SWEG).

STD #1: Maintain at least 11 individuals under the PPP agreement.

STD #2: Personnel shall be utilized in the execution of the requirements listed in section

3.4 – 3.7 of this PWS.

CDRL(s) A005, Requirement Report 50/50 A015, PPP Funded Organic Workload Forecast

3.1.12 Procure materials, licenses, new software tools, or hardware IAW the contractor’s approved procurement system and disclosure statement and in the direct support of services provided under this effort.

Performance Standards STD #1: Utilize the Material and Other Direct Cost CLIN. Materials for the prime and subcontractors shall be invoiced against the Material and Other Direct Cost CLIN and not embedded in labor invoices.

CDRL(s) N/A

3.1.13 Travel as required in order to perform requirements under this PWS. In general, travel costs are airfare, ground transportation, and per diem costs, not labor hours.

Performance Standards STD #1: The contractor shall obtain written approval to travel from the Program Office or Contracting Officer’s Representative (COR) at least five (5) business days prior to traveling. No pre-approval is required in the case of emergency travel; however, the contractor must notify the Government of the travel within 2 days from commencement of travel.

STD #2: All travel shall be charged to the Travel CLIN.

CDRL(s) N/A

3.2 Organizational and Intermediate Level Maintenance. The contractor shall:

NOTE: This activity includes the SOCs at Schriever SFB, CO and the BSOC-V at Vandenberg Tracking Station, CA.

3.2.1 Provide organizational and intermediate level support for CCS-C operational locations.

Tasks include, but are not limited to, Mission Problem Report (MPR) resolution, System Administrator (SA) support, installation support, maintain critical spares and bench stock, perform Preventive Maintenance Inspections, remove and replace faulty equipment, restore system to operations, draft schedule requests and maintain organizational maintenance procedures, including creating, modifying, and deleting new or existing procedures.

Performance Standards

STD #1: The contractor shall draft approximately 150 sustainment requests annually and submit to Government prior to a scheduled or planned sustainment event (separate from the 1000 IMDS jobs in STD #5).

STD #2: Identify and correct approximately 60 planned and unplanned system outages or operational issues annually and return the mission system to a fully operational status (included in the 1000 IMDS jobs in STD #5).

STD #3: For any unscheduled maintenance, notify the SSC/CGM Program Manager of an event occurring via e-mail within two hours of event start.

STD #4: For any unscheduled maintenance, provide a detailed timeline, corrective actions taken and operational impact to SSC/CGM via e-mail within one business day.

STD #5: Respond to and resolve approximately 1000 Integrated Maintenance Data System (IMDS) jobs annually, not including password resets.

STD #6: Provide 24x7 on-site support.

STD #7: Maintain critical spares and bench stock assets, with accurate inventories IAW the authorized sparing levels referenced in the GFP list. Complete back order requests.

STD #8: Perform all required Preventative Maintenance Inspections.

STD #9: Provide SA support IAW 4 Space Operation Squadron (SOPS) processes/instructions, organization level maintenance work instructions and maintenance TOs.

STD #10: Maintain organization level maintenance work instructions in order to support day-to-day operational support needs.

CDRL(s) A013, Technical Manual Contract Requirements (TMCR)

3.2.2 Provide support for BSOC-V.

STD #1: Perform site-specific duties to include, but not limited to, system administration, computer support, equipment and precision measurement equipment custodial responsibilities, and software license management.

STD #2: Provide all support as required to ensure 21st Space Operations Squadron/Vandenberg Tracking Station (VTS) and VSFB guidance is followed for the BSOC- V.

STD #3: Provide on-site support, for 16 hours per day, during operational deployments and checkouts to BSOC-V, approximately 4 times per year.

STD #4: During deployment activities, in contractor format, provide a running daily status, lessons learned, and any relevant actions taken via e-mail notification to the assigned 4 SOPS and SSC/CGM Government representative by 1600 MT.

STD #5: Provide a deployment activities summary delivered via e-mail notification to the assigned 4 SOPS and SSC/CGM Government representative and posted to a contractor managed file sharing site within 5 business days of deployment completion.

CDRL(s) N/A

3.2.3 Monitor system performance at all CCS-C locations.

Performance Standards

STD #1: Monitor and assess the physical hardware health, including status, memory/CPU/Network utilization, number of hardware faults, hypervisor error messages, and hardware configurations.

STD #2: Monitor and assess the virtual machines’ health, including status, memory/CPU/network utilization, operating system errors and application or service errors on a virtual machine.

STD #3: Monitor and assess any attached, virtualized or relevant data storage for health including storage usage, free space remaining, input/output operations per second, latency, hardware faults and controller error messages.

STD #4: Monitor and assess network equipment health including equipment status, network utilization, network capacity, and hardware faults.

STD #5: Monitor and assess relevant environmental parameters including server room temperature and power status.

STD #6: Report system performance trends, relevant system performance deviations and any anticipated performance exceptions to the Government quarterly, in contractor format, via a contractor managed share site.

CDRL(s) N/A

3.2.4 Respond to maintenance notifications, determine if each is resolvable at the organizational level within 60 minutes (average) of problem notification or arrival on site, and complete any necessary final replacement or corrective actions. This task supports task 3.2.1.

STD #1: Identify the specific hardware or software component that has failed

STD #2: Document all maintenance actions in IMDS.

STD #3: Notify TYAD personnel, who will contact the appropriate hardware vendor for repair or replacement actions.

STD #4: Resolve IMDS jobs per the following timelines:

Calendar Days from Initiation to Closure

0 days (same day) days days days

Percentage of MPRs Closed 55% 75% 84% 100%

3.3 Contractor Logistics Support and Network Communications Maintenance.

The contractor shall:

3.3.1 Accurately document and complete changes to the technical orders, manuals, and engineering drawings resulting from any maintenance actions, and leave redlines on site for organizational level maintenance.

Performance Standards

STD #1: Begin updating the affected drawings found during maintenance actions within 10 business days.

STD #2: Submit TO changes for TOMA approval within 10 business days.

STD #3: Notify the Government representative upon submittal and provide a summary of drawing changes submitted.

CDRL(s) A013, Technical Manual Contract Requirements (TMCR)

3.3.2 Perform obsolescence, technical refresh, and spares management activities.

Performance Standards

STD #1: Maintain knowledge of the lifetime of all system components to ascertain when components (software and hardware) will become obsolete and thus unsupportable by the vendors.

STD #2: Purchase, integration, test and installation of replacement components that are within the CCS-C COTS software or hardware product lines will be managed as part of the hardware/software sustainment effort.

STD #3: Conduct obsolescence studies and leverage RMA analysis conducted in 3.4.6.

STD #4: Submit, in contractor format, an annual obsolescence report via contractor managed share site and via e-mail to the Government.

STD #5: Submit, in contractor format, an annual prioritized, recommended spares list supported by quantified analysis.

STD #6: Provide monthly status at the end of each calendar month upon receiving authority to purchase equipment spares and provide a final report that includes all items purchased and received.

CDRL(s) N/A

3.3.3 Assist technicians approximately 30 times (recorded in IMDS) annually in trouble shooting and correcting CCS-C communications links to maintain the CCS-C communications network.

Performance Standards

STD #1: Respond with on-site support within 24 hours.

3.4 Systems Engineering. The contractor shall:

3.4.1 Manage all Deficiency Reports, Problem Reports, Enhancement Reports, Data Product Updates, Maintenance Updates (MUs) and Initial Development (IDs), Hardware Modifications, and any other software changes (together called Change Requests [CRs]) Performance Standards

STD #1: Comply with TO 00-35D-54, USAF Deficiency Reporting, Investigation, and Resolution.

STD #2: Manage and administer a CR database, including management of users, groups and permissions, and license management.

STD #3: Utilize the CR database to process all CRs, track technical solutions, and track all changes made to the system.

STD #4: Present for Government approval, all open CRs to the monthly CCS-C CCB with proposed recommendations, prioritization, level of effort, and validation criteria required for resolution as described in the CCS-C Configuration Management Plan (CMP).

STD #5: Recommend for Government approval, CR assignment to a software release via the weekly SAPWG process as described in the CCS-C CMP.

STD #6: Following the CCB, deliver in contractor format, a CR database report to the Government via a contractor managed share site.

CDRL(s) N/A

3.4.2 Ensure proper implementation of all required interfaces within and among systems IAW all applicable Interface Control Documents/Drawings (ICDs).

Performance Standards

STD #1: Participate in approximately 12 external interface control working groups annually.

STD #2: Manage and update all CCS-C Interface Documents/Drawings IAW the CMP.

CDRL(s) B001, Interface Design Description (IDD)

3.4.3 Perform configuration management to include the identification, control, accounting and auditing of the functional and physical characteristics of CCS-C systems.

NOTE: This includes updates to all system and subsystem specifications controlled by the contractor.

Performance Standards

STD #1: Comply with the Government approved, contractor developed, Configuration Management Implementation Plan (CMIP), consistent with the latest versions of SAE GEIA- HB-649A, ANSI/EIA-649-1, and NIST-SP-800-128 and in compliance with the CCS-C CMP.

CDRL(s) B002, Specification Change Notice (SCN) B003, System Subsystem Specification (SSS) B004, Software Product Specification (SPS) B019, Engineering Change Proposal (ECP) B020, Configuration Management Implementation Plan (CMIP)

3.4.4 Provide technical support for ad hoc taskings (NTE 40 hours per tasking), including, but not limited to, higher headquarter requests, program office projects, and other user requests.

Performance Standards

STD #1: Support approximately 15 technical reviews annually within 3-5 business days unless the Government approves a longer schedule.

CDRL(s) N/A

3.4.5 Provide engineering level of effort estimates.

Performance Standards

STD #1: Provide approximately 18 engineering level of effort estimates (in hours), excluding change requests, annually for any changes to hardware, software or operations and sustainment procedures requested by the Government.

STD #2: Deliver engineering estimates via e-mail in contractor format within 5 business days of the Government request or as agreed upon by both parties.

CDRL(s) N/A

3.4.6 Develop and provide RMA reports for all systems identified in paragraph 1.2 of this PWS in accordance with the approved Reliability Program plans.

Performance Standards

STD #1: Prepare and submit for approval a Reliability Program Plan in accordance with SMC-S-013, Sections 5.1.2, 5.1.3, 5.1.4, 5.1.5, 5.1.6, 5.1.8, 5.2, and 5.3.

STD #2: Ensure reports for SSFB and BSOC-V are reflective of mission system availability and shall be 100% accurate based on site outage times recorded in IMDS.

STD #3: Ensure reports contain remaining time to Mean Time Between Failures (MTBF) at both the system and component level, current operating times and other relevant MTBF metrics.

STD #4. Produce reports for the CCS-C Test Facility (CTF) based on contractor-captured data.

CDRL(s) B005, Technical Report – Study/Services. Reliability Status Report

3.4.7 Maintain and sustain the CCS-C to meet documented system requirements in CDRL B003

SSS.

Performance Standards

STD #1: Ensure CCS-C availability is greater than or equal to .9758 for the Schriever SOC Ops Mode.

STD #2: Ensure CCS-C dependability is greater than or equal to .99825.

STD #3: Maintain the System Subsystem Specification within the DOORs ® database.

STD #4: Comply with the Government approved, contractor developed Integrated Master Processes document.

CDRL(s) B003, System Subsystem Specification (SSS) B021, SEMP_Integrated Master Processes (IMP)

3.4.8 Provide technical support and management (to include hosting meetings, publishing agendas, and publishing meeting minutes) for all required configuration control/release planning and technical meetings.

Performance Standards

STD #1: Manage approximately 60 regularly scheduled configuration management and system working group meetings per year.

STD #2: Support approximately 210 technical interchange meetings per year.

STD #3: Support approximately 60 ad-hoc configuration management meetings per year.

STD #4: Manage the semi-monthly Systems Engineering IPT (SEIPT) meetings (24 per year).

STD #5: Manage the monthly cybersecurity working group.

STD #6: Support approximately 24 Test IPT meetings per year.

STD#7: Post the meeting minutes to a contractor managed file sharing site and notify the Government via e-mail of their location within 3 business days after meeting.

CDRL(s) N/A

3.4.9 Provide technical support for systems integration.

STD #1: Integrate software baselines IAW paragraph 3.5.4 of this PWS.

STD #2: Provide task planning, technical analysis, implementation, and identification of integration improvements.

STD #3: Participate in all technical reviews, as required, to complete systems integration.

CDRL(s) N/A

3.4.10 Incorporate changes to TOs, manuals, and engineering drawings that are affected as the result of changes to the system.

NOTE: Engineering drawings may include changes or updates to rack assembly drawings, component assembly drawings, connection diagrams, floor layouts, power and grounding and drawing trees for the CCS-C baselines.

Performance Standards

STD #1: Submit AFTO 27s to the Government identifying required changes to the TOs as a result of a software release defined in section 3.5.4 in this PWS.

STD #2: Make changes to engineering drawings as needed.

STD #3: Provide configuration management of all CCS-C technical drawings in a contractor identified database and provide access to Government personnel.

STD #4: Ensure configuration management of drawings is IAW EIA-649-1, Configuration Management Requirements for Defense Contracts.

STD #5: Ensure change history, to include drawing change requests and any deviations from that form, will be delivered with the drawings for review.

STD #6: Ensure CCS-C engineering drawings will be compliant with the most current version of MIL-STD-31000, with the exception of the drawing tree, or deviations agreed upon in advance with the Government.

STD #7: Provide 100% accurate technical data at pre-publication reviews.

STD #8: Maintain an Enhanced Technical Information Management System (ETIMS) account.

STD #9: Provide accurate and complete changes per the most current version of MIL-STD- 31000 standards for drawings and TO 00-5-15 series for Technical Orders.

CDRL(s) B006, Product Drawings/Models and Associated Lists B007, Software Users Manual B017, Technical Manual Contract Requirements (TMCR)

3.4.11 Provide the Equipment Specialist (ES)/TOMA with TO status monthly to include open issues, planned TO publications and status of Recommended Changes (RCs)/Publication Change Requests (PCRs) and drawing change requests.

STD #1: Provide information in a contractor format and e-mail to the ES/TOMA and post on contractor managed share site.

CDRL(s) N/A

3.4.12 Provide infrastructure and system configuration support for CCS-C operational systems and test facility.

Performance Standards

STD #1: Provide rack and cable design installation and cable management for CCS-C at operational locations and test facility for the following approximated efforts:

• Two moves per year - moving six workstations to a new locations

• One move every two years - moving the operations center to a different mod

STD #2: Provide hardware installation support for replacing and relocating hardware including: qualification, testing, documentation, planning and execution for the following approximated efforts::Two moves per year - moving six workstations two a new locations

• Two moves per year - moving six workstations to a new locations

• One move every two years - moving the operations center to a different mod

STD #3: Perform troubleshooting for ground system assets for including; entire end item, assemblies and subassemblies (including SW and firmware), system administration, technical assistance and fault detection/fault isolation.

3.5 Depot Level Software Maintenance. The contractor shall:

NOTE: This currently includes all CCS-C software at the SOCs at Schriever SFB, CO and the BSOC-V at Vandenberg Tracking Station, CA, the Government CCS-C Test Facility at Peterson SFB, CO, and contractor development labs.

3.5.1 Perform an initial impact assessment of all software related CRs after receipt from the originator.

Performance Standards

STD #1: Follow SMC-S-012, Software Development for Space Systems as tailored in the C- SAR IDIQ Compliance and Reference Documents contract attachment.

STD #2: Provide initial assessment within 24 hours for Cat I CRs, 10 calendar days for Cat IIU CRs, and 30 calendar days for all remaining CR types, unless otherwise directed by the Government.

STD #3: Assess all CRs and submit them to the Change Control Board (CCB) within 45 calendar days of initial assessment for acceptance or deferral, unless otherwise directed by the Government.

CDRL(s) N/A

3.5.2 Design, develop, and modify software to satisfy requirements, prevent performance degradation, prevent or correct system failures, provide for system growth, or improve overall system capabilities and effectiveness, as identified by CRs. This task supports the expected number of releases and software fixes as outlined in section 3.5.4.

Performance Standards

STD #1: Follow SMC-S-012, Software Development for Space Systems, as tailored in the C-SAR IDIQ Compliance and Reference Documents contract attachment.

STD #2: The contractor shall comply with the Government approved Software Development Plan.

CDRL(s) B008, Software Development Plan B019, Engineering Change Proposal (ECP)

3.5.3 Test software releases/modifications and hardware installations/upgrades to ensure changes will fix the problem or provide the enhancement identified in the CR and not degrade the integrity of the system. This task requires new CRs to be opened or existing CRs to be updated in the event testing uncovers a system issue. This task supports the expected number of releases and software fixes annually as outlined in section 3.5.4.

Performance Standards

STD #1: Follow SMC-S-012, Software Development for Space Systems and SMC-S-024, Test Requirements for Ground Systems; both as tailored in the C-SAR IDIQ Compliance and Reference Documents contract attachment.

STD #2: Submit test plans and procedures, for Government review and approval, via e-mail and contractor managed share site 2 weeks prior to formal testing unless otherwise granted relief by the Government.

STD #3: Provide the Government the opportunity to observe or witness all test activities.

STD #4: Provide technical and test support for operations checkout of software releases in conjunction with 4 SOPS operators.

STD #5: Provide the issue author with three business days to confirm that the implemented change functions as needed.

STD #6: Provide the Government a resolution plan within 30 calendar days for any issues that degrade the performance or integrity of the system.

CDRL(s) B009, Software Test Plan (STP) B010, Software Test Description (STD) B011, Software Test Report (STR)

3.5.4 Deliver frequent software releases, utilizing modern software practices for CCS-C, implementing approximately 900 CRs annually. These releases shall support normal sustainment releases, cybersecurity updates as outlined in section 3.7.4 of this PWS, anomaly resolution, and operational outages.

STD #1: Follow SMC-S-012, Software Development for Space Systems, as tailored in the C-SAR IDIQ Compliance and Reference Documents contract attachment.

STD #2: Provide resolution of 100% of Cat I CRs within 60 calendar days of receipt from the originator.

STD #3: Provide resolution of Cat IIU CRs with the following schedule:

91% within 90 calendar days, 98% within 180 calendar days, and 100% within 365 calendar days.

STD #4: Provide resolution of Cat IIR CRs with the following schedule:

100% within 365 calendar days of opening; based on an estimated 150 errors per year.

B007, Software Users Manual (SUM) B012, Software Installation Plan (SIP) B013, Software Version Description (SVD)

3.6 Test Facilities Support. The contractor shall:

Maintain and support the Government owned CCS-C Test Facility (CTF). With the exception of the CCS-C Development Laboratories (CDLs), all test assets are housed in Government facilities.

All facilities may be utilized by outside organizations approved by the Government for relevant testing. The Government will be allowed access to the labs at any time to conduct tasks to include, but not limited to, tours and component evaluations. Any lab contention will be adjudicated by the Government.

NOTE: The contractor is responsible for the system accreditation of all lab assets located at the contractor’s facility.

3.6.1 Provide maintenance, support, and troubleshooting for the Government owned test environments.

Performance Standards

STD #1: Ensure labs are reserved two (2) business days prior to scheduled test activities.

STD #2: Ensure equipment is consistent and compatible with providing an operationally representative replica of the existing operational system.

STD #3: Provide support to the CTF during normal duty hours.

STD #4: Respond to unscheduled CTF outages within one (1) business day of notification.

STD #5: Assume responsibility for COMSEC user activities such as configuration management, password resets and key loading.

STD #6: Provide organizational level support. Tasks include, but are not limited to, System Administrator (SA) support, installation support, maintain critical spares and bench stock, perform Preventive Maintenance Inspections, remove and replace faulty equipment, restore system to operations and draft Schedule Requests (SR).

3.7 Cybersecurity Engineering Support. The contractor shall:

Integrate cybersecurity requirements, functional activities and corrective actions into sustainment activities; and shall coordinate with the program’s Government representatives (i.e. Program Manager, Systems Engineer, and Information System Security Manager) IAW DoDI 8500.01 and 8510.01, including policies, standards, special publications, instructions and guidance from the DoD, JCS, NIST, FIPS, CNSS, Defense Information Systems Agency (DISA), Department of the AF (DAF) and SSC/CGM organization.

3.7.1 Provide appropriately qualified and certified personnel working cybersecurity and information technology activities (full or part time) under this Task Order and ensure required certifications (both cybersecurity and computing environment) are maintained.

Performance Standards

STD #1: Provide a personnel listing IAW DODD 8140.01 and DODI 8570.01-M as a means for identifying, tracking and reporting cybersecurity and cyber IT positions and personnel, including subcontractor personnel, and update within 10 calendar days of any changes in personnel, personnel certifications, or personnel cybersecurity duties.

STD #2: Provide cybersecurity expertise for other meetings listed throughout this PWS as required.

CDRL(s) B014, Cybersecurity Work Force (CSWF) Report

3.7.2 Ensure that any design change, integration change, configuration change, or installation of hardware and software is IAW established cybersecurity directives and does not violate the terms and conditions of the authorization-to-operate (ATO) issued by the Authorization Official (AO) for the CCS-C system.

Note: The DISA Unified Capabilities (UC) Approved Products List (APL), and software that has undergone National Information Assurance Partnership (NIAP) evaluation have been published on the Approved Products Compliance List (APCL).

Performance Standards

STD #1: Apply cybersecurity configuration management practices in the contractor-developed CMIP consistent with NIST SP-800-128 guidance and IAW Section 3.4.3 of this

PWS.

STD #2: Ensure that evaluated and approved products are employed, where applicable.

STD #3: Make available to the Government all product information via a contractor managed share site.

3.7.3 Comply with the required DoD Cybersecurity Risk Management Framework (RMF).

Performance Standards

STD #1: Incorporate an RMF artifact delivery schedule within the schedule as defined in section 3.1.3 of this PWS, capturing the status of the submission frequency of the identified RMF artifacts per system sustainment cybersecurity-related activity performed under this Task Order, and identified RMF package delivery timeframe within the related activity.

STD #2: Deliver as scheduled the RMF package deliverables that are appropriate to the system sustainment activity being accomplished.

STD #3: Provide 100% accurate technical data of all current baselines in all artifacts that are created and maintained by the contractor.

CDRL(s) B015, DoD Risk Management Framework (RMF) Package Deliverables

3.7.4 Track, analyze, and assess for applicability, approximately 500 posted (DoD Directives, advisories, bulletins and alerts) patches and malware signatures per year for all CCS-C hardware and software platforms.

Performance Standards

STD #1: Maintain accounts for Vulnerability Alerts, bulletins, and technical advisories from the US Cyber Command DoD Computer Emergency Readiness Team and for computer-host antivirus definitions and intrusion detection and prevention signatures from vendors of host’s operating systems.

STD #2: Monitor COTS software vendors’ publications/web sites for updates and security patches not issued as DoD Directives, advisories, bulletins and alerts.

STD #3: Begin review/assessment of vulnerability patches and antivirus signatures within one business day of posting.

STD #4: Generate Change Requests associated with posted directives as needed IAW section 3.4.1 of this PWS.

CDRL(s) A012/B019, Engineering Change Proposal (ECP)

3.7.5 The contractor shall deliver and install fully tested vulnerability patch and virus signature releases for the CCS-C system every 60 calendar days (6 times annually) IAW section 3.5.4 of this PWS. The contractor shall deliver and install approximately 4 fully tested emergency vulnerability patch and virus signature releases per year.

Performance Standards

STD #1: The contractor shall implement vulnerability patches and/or antivirus signatures via software releases IAW NIST 800-53 Control SI-2 and the Government approved implementation schedule.

STD #2: Deliver the associated RMF artifacts as the result of accomplishing this task IAW section 3.7.3 of this PWS

CDRL(s) B013, Software Version description (SVD) B015, DoD Risk Management Framework (RMF) Package Deliverables

3.7.6 Work with the program office on developing a Government approved continuous monitoring and implementation plan to ensure all CCS-C security controls and cybersecurity capabilities can be monitored and controlled over time for effectiveness and adherence to the Authorizing Official’s accepted risk level.

Performance Standards

STD #1: Submit the monitoring strategy within 45 calendar days of Task Order start.

STD #2: Follow DoDI 8510.01 and be aligned with concepts in NIST SP 800-137 STD #3: Ensure monitoring capabilities (at the system, enclave, or enterprise level) are engineered into the system and can be used by the operational community to include Defensive Cyberspace Operations (DCO) organizations providing cybersecurity services.

STD #4: Perform vulnerability scans at least once per month using applicable Defense Information Systems Agency (DISA) Field Security Operations (FSO) guidance and tools, or Government approved equivalent.

NOTE: DISA guidance includes but is not limited to: Security Technical Implementation Guides (STIG), Security Checklists, National Institute of Standards and Technology (NIST) Guides, and National Security Agency (NSA) Guides. DISA tools include but are not limited to: Assured Compliance Assessment Solution (ACAS), Security Content Automation Protocol (S-CAP) benchmarks, Security Readiness Review (SRR) Scripts, and Host Based Security System (HBSS) that are used to monitor, detect, and defend the DoD computer networks and systems.

STD #5: Monitor the DISA Information Assurance Support Environment (IASE) website for applicable guidance and tool updates on a quarterly basis.

STD #6: Notify the program Information System Security Manager (ISSM) via e-mail of anomalies or new vulnerabilities identified within 48 hours.

STD #7: Submit the native scan results from any tools and a vulnerability report with a recommended course of action to resolve any findings within 14 calendar days of each monthly scan. Findings that cannot be fixed or mitigated shall be placed on the RMF Plan of Actions and Milestones (POAM).

STD #8: Generate approximately 200 cybersecurity related CRs to identify and track required fixes for findings discovered from scans, testing, or operations, IAW Section 3.7.5, 3.5.4, and 3.4.1 of this PWS.

CDRL(s) B015, DoD Risk Management Framework (RMF) Package Deliverables B019, Engineering Change Proposal (ECP)

3.7.7 Establish and implement a Supply Chain Risk Management (SCRM) process to ensure that the delivered system, maintenance equipment, and supplies (e.g., spares and repair parts) do not incorporate counterfeit parts, malicious code, or any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations.

Performance Standards

STD #1: Use DoD-approved hardware and software products and sources that have completed Interoperability (IO) and Cybersecurity certification.

3.8 Safety. The contractor shall:

3.8.1 The Contractor shall establish, document, and adhere to a system safety risk management process (as defined in the Integrated Master Processes [IMP], Task Order Attachment 4).

STD#1: The Contractor shall apply systems engineering and risk management principles, criteria, and techniques to minimize mishap risks within the constraints of operational effectiveness, time, and cost throughout all phase of the system or end-item life cycle and that complies with MIL-STD-882E, tailored task 102, and the Systems Safety Management Plan

(SSMP).

STD#2: The Contractor shall utilize a safety process that includes a means for identification and analysis of hazards (including results from failure mode and effects analysis performed per the SEP) over the system life cycle, assessment of mishap risk expressed as severity and probability of consequences, determination of risk mitigating measures, implementation of measures to reduce risks to acceptable levels, verification of risk reduction, acceptance of residual risks by appropriate authorities, tracking of hazards and residual risks throughout the system life cycle, and timely communication of that information to the Program Office.

B016, System Safety Hazard Analysis Report

3.9 120-day Task Order Phase-in Activities. The contractor shall:

Conduct phase-in activities.

3.9.1 Facilitate a seamless phase-in transition from the current contractor/Government personnel beginning at Task Order period of performance start date.

Performance Standards

STD #1: Within 7 days of Task Order award identify a plan and schedule, which will be used to transfer knowledge between the outgoing contractor and incoming contractor.

STD #2: Establish and maintain effective communication with the outgoing contractor and Government personnel for the period of the transition.

STD #3: Take control of the System Subsystem Specification within DOORS within 30 calendar days of Task Order period of performance start date.

STD #4: Take control of the CR database within 60 calendar days of Task Order period of performance start date.

STD #5: Maintain the current Public Private Partnership (PPP) by coordinating with the 517th engineering group to ensure a Partnering Agreement and Implementation Agreement are drafted and approved by the end of the transition period.

CDRL(s) N/A

3.9.2 Accept responsibility for all GFP, and for all CCS-C system baseline equipment.

Performance Standards

STD #1: Accomplish a GFP joint inventory with Government points of contact within 30 business days after contract award.

STD #2: Document and take accountability of all GFP within 60 calendar days after contract award.

STD #3: Complete a joint inventory of all CCS-C system baseline equipment within 30 business days after contract award.

CDRL(s) B018, Government Property Inventory Report (GPIR)_GFE B022, Government Property Inventory Report (GPIR)_System Config

3.9.3 Provide sufficient staffing appropriate to meet program phase-in milestones.

Performance Standards

STD #1: Ensure program management, contracting, and technical management personnel are in place at Task Order award.

STD #2: Be capable of implementing Cat I DR fixes within 60 calendar days of Task Order period of performance start date.

CDRL(s) N/A

3.9.4 Provide necessary facilities at task order award to accommodate contractor personnel and teammates.

Performance Standards

STD #1: Facility must meet minimum industry Occupational Safety & Health Administration standards and secure access.

3.9.5 Transition the Development lab environments from the incumbent’s facility to the gaining contractor’s facility.

STD #1: All program labs must be fully accredited by the Defense Counterintelligence and Security Agency upon completion of the 120-day transition period.

STD #2: Facility housing the labs must meet minimum industry standards for HVAC, commercial and technical power, safety standards, fire suppression, security access and security clearance level requirements in accordance with the DD-254.

Contractor Data Requirements Lists (CDRL) The contractor shall provide deliverables as described in the PWS and CDRL. Deliverables shall be specified by the Government. Format and delivery schedule for deliverables are outlined in CDRLs. The table below lists the formal CDRL deliverables for this contract. A-CDRLs will be included in the cost of CLIN X001. B-CDRLs will be included in the cost of CLIN X003. There are other technical documents related to this contract that are described in the task statements in paragraph 3 of this PWS.

# TITLE PWS Paragraph

A001 Contract Work Breakdown Structure 3.1.7

A002 Contract Funds Status Report 3.1.7

A003 Cost and Hour Report 3.1.7

A004 Software Maintenance Report 3.1.7

A005 Requirement Report 50/50 3.1.7

A006 Technical Data Report – Cost and Software Data Report 3.1.7

A007 Contractor Cost Data Report (DD Form 1921-3) 3.1.7

A008 Integrated Program Management Report (IPMR) 3.1.7

A009 Government Property Inventory Report (GPIR)_GFP 3.1.8

A010 Small Business Subcontractor Report 3.1.10

A011 Data Accession List (DAL) 3.1.10

A012 Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)

3.1.10

A013 Technical Manual Contract Requirements (TMCR) 3.2.1, 3.3.1

A014 GPIR_System Configuration 3.1.8

A015 PPP Funded Organic Workload Forecast 3.1.11

B001 Interface Design Description (IDD) 3.4.2

B002 Specification Change Notice (SCN) 3.4.3

B003 System Subsystem Specification (SSS) 3.4.3, 3.4.7

B004 Software Product Specification (SPS) 3.4.3

B005 Reliability Status Report 3.4.6

B006 Product Drawings/Models and Associated Lists 3.4.10

B007 Software Users Manual (SUM) 3.4.10, 3.5.4

B008 Software Development Plan (SDP) 3.5.2

B009 Software Test Plan (STP) 3.5.3

B010 Software Test Description (STD) 3.5.3

B011 Software Test Report (STR) 3.5.3

B012 Software Installation Plan (SIP) 3.5.4

B013…