ATCH 01 - PWS.pdf

FA8823-23-R-0001 Attachment 1 C-SAR IDIQ PWS

PERFORMANCE WORK STATEMENT (PWS)

FOR

COMMAND AND CONTROL SYSTEM – CONSOLIDATED

(CCS-C)

SUSTAINMENT AND RESILIENCY (C-SAR)

INDEFINITE DELIVERY INDEFINITE QUANTITY (IDIQ)

CONTRACT

VERSION 1.0 – 22 MARCH 2023

Prepared by:

SSC

1050 E. Stewart Ave.

Peterson SFB, CO 80914

TABLE OF CONTENTS

Contents

CONTENTS

1 INTRODUCTION

1.1 SSC MISSION

1.2 BACKGROUND

1.3 SCOPE

2 CONTRACT DETAILS AND GENERAL REQUIREMENTS

2.1 CONTRACT TYPE

2.2 ORDERING PERIOD OF PERFORMANCE:

2.3 CONTRACT ADMINISTRATION AND MANAGEMENT

2.4 SUBCONTRACT MANAGEMENT

2.5 CONTRACTOR PERSONNEL, DISCIPLINES, AND SPECIALTIES

2.6 LOCATION AND HOURS OF WORK

2.7 SECURITY

2.8 ACCESS

2.9 MATERIALS

2.10 ASSOCIATE CONTRACTOR AGREEMENT (ACA)

2.11 BASE SUPPORT

2.12 TRAVEL / TEMPORARY DUTY (TDY)

2.13 CONTRACT SURVEILLANCE

2.14 CONTRACTOR RESPONSIBILITY WATCH LIST

2.15 FINANCIAL MANAGEMENT – COST REPORTING

2.16 TASK ORDER/DELIVERY ORDER REQUIREMENTS

2.17 NON-PERSONAL SERVICES

2.18 FEDERALLY FUNDED RESEARCH AND DEVELOPMENT CENTER (FFRDC)

2.19 PRIME AND SUPPORT CONTRACTOR RELATIONSHIPS

3.0 CONTRACTOR TASKING REQUIREMENTS

3.1 PROGRAM MANAGEMENT

3.2 CORE SUSTAINMENT AND OPERATIONS SUPPORT

3.3 CONSTELLATION CAPACITY

3.4 RESILIENCY ENHANCEMENTS

3.5 SPECIAL STUDIES

3.6 ENTERPRISE ENHANCEMENTS

3.7 TRANSITION PHASES

4.0 SPECIAL REQUIREMENTS

4.1 APPLICABLE DIRECTIVES AND SPECIFICATIONS

5 CONTRACTOR DATA REQUIREMENTS LIST (CDRL)

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

1.1 SSC 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 (SSFB), CO and alternate systems are located at Vandenberg SFB (VSFB), CA; with a test facility located at Peterson SFB (PSFB), CO.

1.3 Scope

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

Task orders/delivery orders will be issued in one or more of the service areas listed below in order to support operations, sustainment, or enhancements of CCS-C and related systems.

Core Sustainment of the current CCS-C System

Constellation Capacity

Resiliency Enhancements

Special Studies

Enterprise Enhancements

Direction to perform under any given task order/delivery order will be directed by the Procurement Contracting Officer (PCO) via issuance of an order.

2 Contract Details and General Requirements This section describes all the general requirements of this contract.

2.1 Contract Type

This is an Indefinite Delivery Indefinite Quantity (IDIQ) contract. The PCO will define contract types by task order/delivery order and/or Contract Line Item Number (CLIN).

2.2 Ordering Period of Performance:

The C-SAR IDIQ contract will have a base ordering period of five years with an option for one three-year ordering period. The contract will also include an optional six-month extension of services IAW FAR 52.217-8. The ordering period is estimated to begin on 1 December 2023 and, if all options are exercised, run through 31 May 2032. Exact dates for the Ordering Period will be defined upon contract award. Task Orders may be placed anytime during the ordering period but task order performance will not extend past 12 months after the ordering period ends. The estimated contract ordering period is:

Base Ordering Period: 1 December 2023 - 30 November 2028 Ordering Option Period: 1 December 2028 - 30 November 2031 FAR 52.217-8: 1 December 2031 – 31 May 2032

2.3 Contract Administration and Management

The following subsections specify requirements for contract management, contract administration, and personnel administration.

2.3.1 Contract Management

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The contractor shall maintain management of this contract in El Paso County, Colorado. Additionally, all prime contractor functional support (Finance, Contracting, Business Ops, Senior Program Management, etc.) for this contract shall be located in El Paso County, Colorado. Finally, the test assets and staffing shall be located in El Paso County, Colorado. The contractor will be expected to comply with management and operations expectations as outlined above from contract start.

2.3.2 Contract Administration

2.3.2.1 The contractor shall establish processes and assign appropriate resources to effectively perform the requirements of this contract. The contractor shall respond to Government requests for contractual actions on or before the requested deadline. The contractor shall have a single point of contact between the Government and Contractor personnel assigned to support contracts.

2.3.2.2 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure data collection site (i.e. System for Award Management). The contractor is required to completely fill in all required data fields using the following web address http://www.sam.gov. Reporting inputs will be for the labor executed during the period of performance in each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year.

2.3.3 Personnel Administration

The contractor shall provide training to its employees, as required, to satisfy the PWS requirements. The contractor shall make necessary travel arrangements for its employees. The contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs).

2.4 Subcontract and PPP Management

2.4.1 The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The contractor shall ensure there are no Organizational Conflict of Interest (OCI) considerations associated with management of the work distribution across prime and subcontractors. Contractors may add subcontractors to their team after notification to the PCO and the Contracting Officer Representative (COR). Subcontracting is permitted provided the teaming arrangement does not create any OCI.

2.4.2 The contractor shall subcontract with small businesses at least 15% annually of the total value (in USD) for the sustainment of CCS-C. The percentage is calculated as the total task order value (before profit or fee is calculated) less the dollar amount reserved for Public Private Partnership (PPP). All other task orders/delivery orders shall be accomplished in accordance with the contractor’s Comprehensive Subcontracting Plan. CDRL A010, Small Business Subcontractor Report, defines the reporting requirements for small business participation.

2.4.3 The contractor may be required to meet a PPP requirement on individual task or delivery orders. In these instances, the contractor shall enter into an agreement with the HQ Air Force Sustainment Center (AFSC) assigned candidate depot for software maintenance, 309th Software Engineering Group (SWEG) to perform the work. CDRL A005 – 50-50 Requirements Report and CDRL A015 – PPP Funded Organic Workload Forecast define the reporting requirements for Public Private Partnering.

2.4.4 The contactor shall provide access, workspace, and equipment at the contractor’s facility in El Paso County or Schriever SFB for all 309 SWEG staff working in support of testing, software development, system engineering, or installation. The contractor shall provide external internet access to all 309 SWEG personnel.

2.5 Contractor Personnel, Disciplines, and Specialties

2.5.1 The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The contractor shall match personnel skills to the work or task. The contractor shall provide training to its employees, as required, to satisfy the PWS requirements. The contractor shall provide the necessary resources, technical processes and infrastructure to manage, perform, and administer the contract.

2.5.2 The contractor shall ensure open, courteous/professional and clear lines of communication between contractor personnel and Government counterparts. This communication may occur daily via telephone discussions, weekly via face-to-face meetings or any other means and frequency necessary to ensure information flow is optimal.

2.5.3 The contractor shall participate in operational exercises and inspections to the fullest level possible without negatively impacting real-world operations. The contractor shall participate in local host-installation exercises and inspections when the contractor’s area of responsibility under this contract are an essential component of the exercise. This requirement includes contractor personnel on duty. Exemptions for contractor personnel involvement in exercises may be provided through local commanders when required. The contractor shall support exercise evaluation / inspection teams during the normal shifts of operation defined in this PWS.

2.5.4 The contractor shall ensure all personnel comply with all base support agreements and physical access requirements where applicable. This includes all required training to gain/maintain access to the Government site and network. The Government retains the right, without penalty, to withdraw privileges at any time for Government convenience or if the contractor violates a base support agreement.

2.6 Location and Hours of Work

2.6.1 Location

The primary Government facilities for services required by this PWS are:

Peterson Space Force Base (PSFB) CO 80914-2902 (Government test location) Schriever Space Force Base (SSFB), CO 80912 (Primary operations location) Vandenberg Space Force Base (VSFB), CA 93437 (Backup operations location)

The contractor shall provide additional support at various contractor, subcontractor and Government facilities, as necessary, to perform the requirements of this contract.

The contractor shall provide necessary facilities to perform the requirements of this contract to include, but not limited to, the following:

Support classified in-person meetings up to Secret (25 person minimum with ability to display classified presentations), preferably a space that also supports classified video and voice teleconferences

Accommodate contractor personnel that are not located on Government installations Meet minimum industry Occupational Safety & Health Administration (OSHA) standards and secure access

2.6.2 Hours

Normal workdays are Monday through Friday excluding federal holidays except in cases where the CCS-C mission needs require support on a non-standard workday. Normal workhours are generally between 0600 and 1800 unless specifically stated otherwise in each individual task order/delivery order.

2.7 Security

2.7.1 Security Compliance

The contractor shall comply with the following security requirements.

C-SAR DD Form 254, Contract Security Classification Specification.

Maintain Personnel Clearances and System Administration/Cybersecurity (previously

Information Assurance) DoD 8570 certifications commensurate with the DD Form 254.

Provide contractor support to administer Sensitive Compartmented Information (SCI) clearances. Provide infrastructure capability to perform task order work at the SCI level.

Comply with all Defense Counterintelligence and Security Agency (DCSA) security requirements for computing systems and networks.

2.8 Access

Access to Government facilities, documents, and systems shall be in accordance with the C-SAR DD Form 254.

2.9 Materials

If a task order/delivery order requires specific materials, new software tools, or hardware, it will be identified in the specific task order/delivery order. The contractor shall procure these materials according to the Bill of Materials. The contractor shall procure these materials in accordance with their approved procurement system and disclosure statement. Materials for subcontractors will be included in the Material and Other Direct Cost CLIN X011 and not embedded in subcontractor labor invoices.

2.10 Associate Contractor Agreement (ACA)

The contractor shall enter into ACAs with other contractors as required to fulfill C-SAR requirements.

2.10.1 The contractor shall enter into an ACA for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirements. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, resources, or any combination thereof, which shall ensure the greatest degree of cooperation for the execution of the program to meet the terms of the contract.

2.10.2 ACAs shall:

1. Identify the associate contractors and their relationships.

2. Identify the program involved and the relevant Government contracts of the associate contractors.

3. Describe the associate contractor interfaces by general subject matter.

4. Specify the categories of information to be exchanged or support to be provided.

5. Include the expiration date (or event) of the ACA.

6. Identify potential conflicts of interest between relevant Government contracts and the ACA and include agreements on protection of proprietary data and restrictions on employees.

2.10.3 The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

2.10.4 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement and not the Government.

2.10.5 All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended and associate contractors added or deleted as required by the Government during the performance of this contract.

2.11 Base Support

The following describes the conditions under which the Government will provide base support to the contractor during the contractor's performance of this contract.

The Government will provide equipment identified in the Government Furnished Property (GFP) list.

The contractor shall furnish all sundry office supplies used for task efforts.

Contractor employees working at government locations will be provided with all software authorized to resident personnel at the location, including email capability, internet access, and Local Area Network (LAN) access.

2.12 Travel / Temporary Duty (TDY)

2.12.1 Travel to other Government facilities or other contractor facilities may be required to perform the services required by this PWS, both within the continental United States (CONUS) and overseas. The contractor shall be responsible for obtaining any passports or visas and making travel arrangements to and from any CONUS location. All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the Government (subject to local policy and procedures), and is on a strictly cost reimbursable basis. Reimbursable travel costs include air fare, ground transportation, and per diem costs, not labor hours. Costs for travel shall be billed in accordance with (IAW) FAR 31.205-46, Travel Costs. Travel to some operational locations may require travel on military aircraft.

2.12.2 The contractor shall obtain written approval to travel from the Program Office at least five

(5) business days prior to traveling. All travel shall be charged to Travel CLIN. No pre-approval is required in the case of emergency travel; however, the contractor must notify the Government.

The contractor shall create a submission form that includes the following information: date and location of travel, purpose of travel, name and title of traveler(s), why alternative methods are not used instead of traveling, and total estimated cost of the trip.

2.13 Contract Surveillance

The Service Delivery Summary (SDS) is the list of performance objectives and standards that must be performed by the contractor. This summary details the method of surveillance the Government (through the COR, in concert with other Government personnel cognizant of the contractor performance) will use to validate and inspect the performance elements. Each task order/delivery order will have its own SDS.

2.14 Contractor Responsibility Watch List

SMC Instruction 64-101, Air Force Space Contractor Responsibility Watch List (CRWL), applies to this contract. Accordingly, if at any time during this contract, the contractor is placed on the CRWL, before executing a modification resulting from an engineering change proposal or exercising an option on this contract, the Contracting Officer must determine whether to recommend proceeding with the modification or option exercise, and if so, obtain approval to proceed from the SSC Commander. To support the Contracting Officer’s determination on whether to proceed with the modification or option, the contractor must submit documentation describing how it has addressed the conditions that resulted in its inclusion on the CRWL and why those conditions will not impact performance on this contract. The Contracting Officer will consider this information as well as other available information in making a determination.

2.15 Financial Management – Cost Reporting

The contractor shall demonstrate effectiveness in forecasting, managing, and controlling task order costs. Contractors shall provide total accountability, accuracy, disclosure, control, forecasting, estimating, and overall management of all efforts at the task order level as follows:

1. Provide management direction for compliance with performance criteria, financial and schedule objectives

2. Provide financial planning and coordination of programs cost and schedule, procurement tasks, contract administration and change control, and CDRL coordination

3. Systematically collect and report actual contract costs to provide Department of Defense (DoD) cost analysts with the needed data to estimate future costs. Contractor reports shall be prepared in accordance with the instructions contain in associated CDRLs.

2.16 Task Order/Delivery Order Requirements

2.16.1 General Requirements

Contractors shall provide services and perform tasks in accordance with separately issued task order/delivery order assignments as specified therein. Contractors shall not start performance on any requirement until the PCO issues a task order/delivery order.

2.16.2 Content

Task Order/Delivery Order Proposal Requests will be prepared by the Government and may include a statement of Work (SOW), Statement of Objectives (SOO), or Performance Work Statement (PWS); security instructions if any; any required SSC/CGM inputs; expected completion date(s); a list of deliverables; special requirements and compliance and reference documents; GFP and Government Furnished Equipment list(s) and additional data, as appropriate, to assist the contractor in understanding the requirement.

2.16.3 Changes/Deviations

Changes to task order contents, estimated costs, schedules and deliverables shall be documented by a revision/modification to the task order/delivery order. Only the PCO may authorize changes to any resulting task order/delivery order awarded under this contract

2.16.4 Activities authorized to Issue task order/delivery orders - only SSC/PKL is authorized to issue task order/delivery orders onto C-SAR.

2.17 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required contract tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual contractor employees unless it is conducted through the Public-Private Partnership task described in 2.4.3. The contractor will 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 within 2 business days.

2.18 Federally Funded Research and Development Center (FFRDC)

Government program contracts requiring interface with Aerospace FFRDC contract support:

1. This contract covers part of a program which is under the general program management of the Space Systems Command (SSC) . The Air Force has entered into a contract with The Aerospace Corporation, a California nonprofit corporation operating a Federally Funded Research and Development Center (FFRDC), for the services of a technical group that will support the DoD/U.S. Government program office by performing General Systems Engineering and Integration, Technical Review, and/or Technical Support including informing the commander or director of the various Department of Defense (“DoD”) organizations it supports and any U.S. Government program office of product or process defects and other relevant information, which, if not disclosed to the U.S. Government, could have adverse effects on the reliability and mission success of a U.S. Government program.

2. General Systems Engineering and Integration (GSE&I) deals with overall system definition;

integration both within the system and with associated systems; analysis of system segment and subsystem design; design compromises and tradeoffs; definition of interfaces; review of hardware and software, including manufacturing and quality control; observation, review and evaluation of tests and test data; support of launch, flight test, and orbital operations; appraisal of the contractors' technical performance through meetings with contractors and subcontractors, exchange and analysis of information on progress and problems; review of plans for future work; developing solutions to problems; technical alternatives for reduced program risk;

providing comments and recommendations in writing to the applicable DoD System Program Manager and/or Project Officer as an independent technical assessment for consideration for modifying the program or redirecting the contractor's efforts; all to the extent necessary to assure timely and economical accomplishment of program objectives consistent with mission requirements.

3. Technical Review (TR) includes the process of appraising the technical performance of the contractor through meetings, exchanging information on progress and problems, reviewing reports, evaluating presentations, reviewing hardware and software, witnessing and evaluating tests, analyzing plans for future work, evaluating efforts relative to contract technical objectives, and providing comments and recommendations in writing to the applicable Air Force Program Manager as an independent technical assessment for consideration for modifying the program or redirecting the contractor’s efforts to assure timely and economical accomplishment of program objectives.

4. Technical Support (TS) deals with broad areas of specialized needs of customers for planning, system architecting, research and development, horizontal engineering, or analytical activities for which The Aerospace Corporation is uniquely qualified by virtue of its specially qualified personnel, facilities, or corporate memory. The categories of TS tasks are: Selected Research, Development, Test and Evaluation; Plans and System Architecture; Multi-Program Systems Enhancement; International Technology Assessment; and Acquisition Support.

5. In the performance of this contract, the contractor agrees to cooperate with The Aerospace Corporation by 1) responding to invitations from authorized U. S. Government personnel to attend meetings; 2) by providing access to technical information and research, development planning data such as, but not limited to, design and development analyses, test data and results, equipment and process specifications, test and test equipment specifications and procedures, parts and quality control procedures, records and data, manufacturing and assembly procedures, and schedule and milestone data, all in their original form or reproduced form and including top- level life cycle cost* data, where available; 3) by delivering data as specified in the Contract Data Requirements List; 4) by discussing technical matters relating to this program; 5) by providing access to contractor facilities utilized in the performance of this contract; 6) and by allowing observation of technical activities by appropriate technical personnel of The Aerospace Corporation. The Aerospace Corporation personnel engaged in GSE&I, TR, and/or TS efforts:

(i) are authorized access to all such technical information (including proprietary information) pertaining to this contract and may discuss and disclose it to the applicable DoD personnel in a program office;

(ii) are authorized to discuss and disclose such technical information (including proprietary information) to the commander or director of the various DoD organizations it supports and any U.S. Government personnel in a program office which, if not disclosed to the U.S.

Government, could have adverse effects on the reliability and mission success of a U.S.

Government program; and

(iii) Aerospace will make the technical information (including proprietary information) available only to its Trustees, officers, employees, contract labor, consultants, and attorneys who have a need to know.

6. The contractor further agrees to include in all subcontracts a clause requiring compliance by subcontractor and supplier and succeeding levels of subcontractors and suppliers with the response and access and disclosure provisions of this Enabling Clause, subject to coordination with the contractor, except for subcontracts for commercial items or commercial services. This agreement does not relieve the contractor of its responsibility to manage the subcontracts effectively and efficiently nor is it intended to establish privity of contract between the Government or The Aerospace Corporation and such subcontractors or suppliers, except as indicated in paragraph (d) below.

7. The Aerospace Corporation shall protect the proprietary information of contractors, subcontractors, and suppliers in accordance with the Master Non-disclosure Agreement The Aerospace Corporation entered into with the Air Force, a copy of which is available upon request. This Master Non-disclosure Agreement satisfies the Nondisclosure Agreement requirements set forth in 10 U.S.C. §2320 (f)(2)(B), and provides that such contractors, subcontractors, and suppliers are intended third-party beneficiaries under the Master Non-disclosure Agreement and shall have the full rights to enforce the terms and conditions of the Master Non-disclosure Agreement directly against The Aerospace Corporation, as if they had been signatory party hereto. Each such contractor, subcontractor, or supplier hereby waives any requirement for The Aerospace Corporation to enter into any separate company-to-company confidentiality or other non-disclosure agreements.

8. Aerospace shall make the technical information (including proprietary information) available only to its Trustees, officers, employees, contract labor, consultants, and attorneys who have a need to know, and Aerospace shall maintain between itself and the foregoing binding agreements of general application as may be necessary to fulfill their obligations under the Master Non- disclosure Agreement referred to herein, and Aerospace agrees that it will inform contractors, subcontractors, and suppliers if it plans to use consultants, or contract labor personnel and, upon the request of such contractor, subcontractor, or supplier, to have its consultants and contract labor personnel execute non-disclosure agreements directly therewith.

9. The Aerospace Corporation personnel are not authorized to direct the contractor in any manner.

The contractor agrees to accept technical direction as follows:

(i)Technical direction under this contract will be given to the contractor solely by SSC.

(ii)Whenever it becomes necessary to modify the contract and redirect the effort, a change order signed by the Contracting Officer or a Supplemental Agreement signed by both the Contracting Officer and the contractor will be issued.

* Cost data is defined as information associated with the programmatic elements of life cycle (concept, development, production, operations, and retirement) of the system/program. As defined, cost data differs from “financial” data, which is defined as information associated with the internal workings of a company or contractor that is not specific to a project or program.”

10. Rationale for determination of category: the proposed contract clause does not deviate from the FAR or its supplements. The clause may be used on a repetitive basis whenever development work requiring the contractor to interact with and/or furnish information to the Government’s Aerospace FFRDC contractor for General Systems Engineering and Integration, Technical Review, and/or Technical Support. There are no new or additional cost or administrative impact on contractors or offerors beyond any cost or administrative impact contained in existing FAR or DFARS coverage.

11. Justification: The Air Force has entered into a contract with The Aerospace Corporation, a California nonprofit corporation operating a Federally Funded Research and Development Center (FFRDC), for the services of a technical group that will support the DoD/U.S.

Government program office by performing General Systems Engineering and Integration, Technical Review, and/or Technical Support. Due to this contract, it is necessary to include a special clause in the C-SAR program to cover and enable interface with Aerospace Corporation.

2.19 Prime and Support Contractor Relationships

1. The Government has or may enter into contracts with one or more of the following companies, or successor(s), to provide Advisory and Assistance Services (A&AS), and/or Systems Engineering and Technical Assistance (SETA), and/or Systems Engineering and Integration (SE&I), and/or Operations and Maintenance (O&M). Non-Disclosure Agreements (NDAs) shall be executed within 30 days after contract award of this contract or after notification of a new contract award to a successor of the contractors listed below:

MCR Federal

The Boeing Company

Lockheed Martin Space Systems Company

Sonalysts, Incorporated

2. In the performance of this Contract, the Contractor agrees to cooperate with the companies listed above (hereafter referred to as (A&AS/SETA/SE&I/O&M). Cooperation includes allowing observation of technical activities by appropriate A&AS/SETA/SE&I/O&M technical personnel, discussing technical matters related to this program and responding to invitations from authorized A&AS/SETA/SE&I/O&M personnel to attend meetings.

A&AS/SETA/SE&I/O&M personnel engaged In general systems engineering and integration effort are normally authorized access to any technical information pertaining to this Contract.

However, exceptions, such as the case where the Contractor seeks to preclude A&AS/SETA/SE&I/O&M personnel from having access to Contractor trade secrets, will be handled on a case-by-case basis. If the Contractor seeks to limit distribution of data to Government personnel only, the Contractor must submit this request in writing to the Contracting Officer. Contractor may require a separate confidentiality agreement be signed directly with any A&AS/SETA/SE&I/O&M. All NDA and confidentiality agreements shall be provided to the Contracting Officer.

3. The Contractor further agrees to include in each subcontract a clause requiring compliance by the Subcontractor and succeeding levels of Subcontractors with the response and access provisions of paragraph (b) above, subject to coordination with the Contractor. This agreement does not relieve the Contractor of responsibility to manage the Subcontracts effectively and efficiently, nor is it intended to establish privity of Contract between the Government or A&AS/SETA/SE&I/O&M and such Subcontractors. Subcontractors may require a separate NDA be signed directly with any A&AS/SETA/SE&I/O&M personnel. All NDA and confidentiality agreements shall be provided to the Contracting Officer.

4. A&AS/SETA/SE&I/O&M personnel are not authorized to direct the Contractor in any manner.

5. A&AS/SETA/SE&I/O&M Contracts will contain an organizational conflict of interest clause that requires the A&AS/SETA/SE&I/O&M Contractor to protect Contract data and prohibits the A&AS/SETA/SE&I/O&M Contractor from using such data for any purpose other than that for which the data was presented.

6. Financial data is defined as information associated with the internal workings of a company or Contractor that is not specific to a project or program. Financial data shall only be provided to the below listed Companies or successor contractors, as identified by the Contracting Officer, unless otherwise mutually agreed to by the parties:

MCR Federal

3.0 Contractor Tasking Requirements

The contractor shall perform work in accordance with separately issued task orders/delivery orders providing engineering and technical support as specified therein.

3.1 Program Management

The contractor shall be responsible for managing all aspects of the IDIQ contract and awarded task order/delivery orders, to include cost, schedule, performance and contract management.

The contractor shall act as the task integrator, ensuring all technical and program elements across all task order/delivery order provide a fully integrated approach.

The contractor shall provide status on the C-SAR task orders/delivery orders to include program management, schedule, risk management, accomplishments, issues, and upcoming events.

The contractor and its employees shall not supervise, direct or control the activities of Government personnel or the employees of any other contractor with the exception of personnel operating under the PPP.

The contractor shall provide a notice of who their designated “Technical Leads” and/or “Project Managers” are for individual task orders/delivery orders to the Government Program Manager, PCO and COR. The Technical Lead shall serve as the primary point of contact for all technical aspects of the required work. This person shall also be a prime provider of the required technical services.

The contractor, as required by individual task order/delivery order, shall provide Rough Orders of Magnitude (ROMs) cost estimates when directed by the Government. ROMs shall be + or - 25% of the actual final cost. Individual task orders/delivery orders will specify the amount of potential ROMs available.

The contractor shall procure and manage licenses, warranties and subscriptions services, as necessary to support C-SAR IDIQ tasks and the respective C-SAR task orders/delivery orders.

The contractor shall also deliver CDRLs associated with a respective task order/delivery order.

The contractor shall provide technical meeting support for SSC/CGM supporting the C-SAR IDIQ and its respective task orders/delivery orders.

3.2 Core Sustainment and Operations Support

The Contractor shall, as required by individual task order/delivery order, perform life cycle logistics support for CCS-C. This includes performing the following:

- Program management

- Operations support

- Organizational, intermediate, and depot level maintenance support

- Contractor logistics support

- Network communications maintenance

- Systems engineering, integration, and test (SEIT)

- Software and database sustainment

- Cybersecurity engineering

3.3 Constellation Capacity

The Contractor shall, as required by individual task order/delivery order, develop and deploy extensions to CCS-C to support new satellites, new constellations, and accommodate decommissioned satellites.

3.4 Resiliency Enhancements

The Contractor shall, as required by individual task order/delivery order, perform modifications to counter emerging threats (Cyber, Space and Ground) and expand Command & Control (C2) capabilities. This includes activities to significantly improve the system’s cybersecurity, such as re-designs required to close vulnerabilities; re-design and re-architecture activities needed to increase the system’s overall operational availability and any activities, such as technical refresh, designed to improve or correct the system’s overall reliability and maintainability.

3.5 Special Studies

The Contractor shall, as required by individual task order/delivery order, perform feasibility studies, trade-off studies, predictive performance measurements, impacts on operations performance, risk assessments, testing, and white papers. Task orders/delivery orders will be reserved for efforts that are within the C-SAR scope of work but beyond the available resources of the Core Operations and Sustainment Support task orders/delivery orders.

3.6 Enterprise Enhancements

The Contractor shall, as required by individual task order/delivery order, modify, develop, and deploy extensions to CCS-C which will enable compatibility with future enterprise efforts, such as Enterprise Ground Services (EGS).

3.7 Transition Phases

The contractor shall, as required by individual task order/delivery order, facilitate seamless phase-in and phase-out transition periods between incoming and outgoing contractor/Government personnel.

4.0 Special Requirements

This section describes the special requirements for this effort. The following sub-sections provide details for these special requirements.

4.1 Applicable Directives and Specifications

This section describes any compliance and reference documentation for this effort. Refer to The Compliance and Reference Documents for a list of applicable documents. If the issuance of an individual task order/delivery order requires additional compliance and reference documentation, it will be specified with the respective task order.

5 Contractor Data Requirements List (CDRL) The contractor shall provide contract deliverables as specified by the Government within each respective task order/delivery order. The list of CDRL exhibits will be on the corresponding task order/delivery order.