Attachment 1. Stament Of Work.pdf

CUI

ATTACHMENT 1

24/7 Network Operations Center (NOC) Statement of Work (SOW)

(U) United States Space Force (USSF)

(U) Space Systems Command (SSC)

(U) Space Command and Control (Space C2)

Acquisition and Management of Services Contract

Date 09 October 2024

Controlled by: Space Systems Command (SSC) Controlled by: Space Command and Control (Space C2) CUI Category: CUI//PROCURE Distribution/Dissemination Control: FEDCON POC: Maj Logan Bolitho, logan.bolitho@spaceforce.mil DRAFT

This page intentionally left blank.

DRAFT

CHANGE CONTROL SUMMARY

Revision (Rev). A revision should be used to identify a new base product associated with a contract modification. Do not remove changes from the change table when the document is revised since they may lend important historical value.

Version (Ver). A change that is administrative in nature does not require the document to be re-staffed. Changes that remove or add items periodically assessed or affect items assessed in frequency of assessment or thresholds must be re-staffed for approval. Consolidate changes when possible. Include a summary of the changes incorporated in the change table.

Rev/Ver Date Description

1.0 Sep 24 Initial SOW

2.0 Oct 2024 Revisition of SOW

CUI 4

Table of Contents 1 Introduction 2 Program Management

2.1 General

2.2 Agile Management

2.3 Meeting Support and Travel

2.4 Contract Data Requirements List (CDRL)

2.6 Associate Contractor Agreements & Other Agreements

3 Personnel & Staffing

3.1 General

3.2 Key Program Personnel

3.3 Personnel Clearances, Network, and Facility Access

4 Tier 1 24/7 Support Team

4.1 24/7 NOC Stand-Up

4.2 General 24/7 Tier 1 Support

4.3 24/7 Software Product Monitoring

4.4 24/7 Network Monitor Function – Level 0 Support

4.5 24/7 Network Monitor Function – Level 1 Support

4.6 24/7 Infrastructure and Platform Monitoring

5 Tier 2 Infrastructure Support Response

5.1 General

5.2 Infrastructure Support

5.3 Operations and Service Desk Support

6 Placeholder – any MOSSAIC COA Scope

6.1 TBD

7 Transition Support

7.1 On-Ramp Plan

7.2 Transition Plan for Closeout

CUI 5

1 Introduction The Space Command and Control (C2) government System Program Office (SPO) is responsible for developing software and the supporting architecture for the Organize, Understand, Plan, Decide, Direct, and Monitor capabilities within the C2 Joint Capability Areas (JCAs). The program plans to employ a modular contracting strategy to take advantage of managing and implementing separate lines of effort. Line of Effort (LOE) 0 provides the foundational structure for Systems Engineering, Integration, and Test (SEIT) and security-classification-specific Infrastructure, Platform, Networks, and Data layers (LOE1) (Figure 1). LOE0 and LOE1 support cross-capability integration, test, and fielding for Space C2 software developed using an Agile-based, Development, Security, and Operations (DevSecOps) Rapid Delivery Framework.

Software development and capabilities primarily support LOE2 Space Domain Awareness, LOE3 Theater Support, and LOE4 Space Defense. The software LOEs are focused on individual customer requirements to tailor software development for the unique operational mission areas and to simplify customer prioritization of the product backlog for each mission area.

The Space C2 Program Office will provide customer support by establishing a 24 hours-a-day, 7-days a week (24/7) Network Operations Center (NOC) at Vandenberg Space Force Base (VSFB) at the Secret and Top Secret / Sensitive Compartmented Information (TS/SCI) levels. The NOC provides 24/7 product support such as operational dashboard monitoring, call tree notifications, and general “Tier 1” support as shown in Figure 2. This support spans Space C2 software products, WarpCore (Data as a Service) data layer, and Space C2 on-prem infrastructure (known as C2 Operational [C2Ops] environment) through dashboard(s) on the Space C2 WarpCore system and initial SPO-provided procedures.

The 24/7 NOC scope includes Tier 1 network support using network-provided dashboard(s) and procedure(s) for the Space Awareness Resilient Tactical Network (SPARTAN) and Space Domain Awareness Network (SDANet), at a minimum. The 24/7 NOC utilizes insights from other networks, such as but not limited to MeshOne-T, Space Defense Interface Network (SDIN), Communications Processing System (CPS), to report out issues identified and associate scope of impacts.

The Space C2 Program also requires regular duty hours infrastructure and operations support, this includes system administration and maintenance of on-prem hardware (C2Ops and TBD MOSSAIC Scope). The 24/7 NOC principally resides within LOE1 and supports LOEs 0, 2, 3, and 4 within the total Space C2 portfolio.

<TBD paragraph on Maintenance of Space Situational Awareness Integrated Capabilities (MOSSAIC) Scope>

This contract scope is grouped in the following categories:

- General support to users including Tier 0 and Tier 1 actions and system monitoring.

- Software monitoring of all Commercial-Off-The-Shelf (COTS) and Government-Off-The- Shelf (GOTS) software. DRAFT

CUI 6

- Network support and monitoring of all network feeds that impact C2 SDA to include Tier 1 support to SPARTAN and SDAnet.

- Infrastructure support to physical hardware.

- Legacy systems and infrastructure support inherited from MOSSAIC

- A transition plan to ensure continuous 24/7 monitoring and support.

Figure 1: Space C2 Lines of Effort

CUI 7

Figure 2: Notional Product Support Tier Structure

CUI 8

2 Program Management

2.1 General

2.1.1 The Contractor shall provide program management and staffing resources necessary to plan, manage, direct, control, and report on all activities contributing to requirements identified herein.

2.1.2 The Contractor shall utilize government-furnished communication tools to include, but not limited to: Google Electronic Mail (e-mail) (Impact Level (IL)-4 e-mail), Microsoft (MS) Teams, Mattermost, Jira, Jira Align, and Confluence.

2.1.3 The Contractor shall utilize government-furnished common services identified within the current Service Description Document managed via the Space C2 Configuration Management Board (CMB). Exceptions to use of specified common services shall be approved by the Government.

2.1.4 The Contractor shall maintain awareness of the Space C2 Development Teams implementation of a Development, Security, and Operations (DevSecOps) approach as managed by the Space C2 CMB.

2.1.5 The Contractor shall proactively support collaborative root cause analysis and incorporate results in future processes, tooling, instrumentation, procedural changes, and/or software development to minimize reoccurrence of cyber, operational, and/or development disruptions.

2.1.6 The Contractor shall provide contract status information for SPO management purposes.

This includes SPO level reviews, executive reviews, independent program reviews and assessments, inspections, milestone events, budget excursions, and user conferences.

2.1.7 The Contractor shall define conditions and process in writing for notifying the SPO of significant events to include security violations, cyber/network intrusions, criminal investigations, adverse financial and schedule information, and mishap reports regarding hardware or personnel. The contractor shall report significant events to the Government Lead, or their designee, within 24 hours of the event.

2.1.8 The Contractor shall notify the Government Lead, or their designee, of Government Senior Leadership or other stakeholder program visits as well as program media exposures. The contractor shall report events within 48 hours of identification or within 24 hours of the event, whichever comes sooner.

2.1.9 The Contractor shall establish necessary subcontracts and ensure the flow down of Intellectual Property assertions, Program Management requirements, and Personnel and Staffing requirements. The Contractor shall ensure that subcontractor data available to the Contractor is also available to the Government (to be delivered in the DAL). DRAFT

CUI 9

2.1.10 The Contractor shall maintain an Organizational Conflict of Interest (OCI) plan as applicable.

2.2 Agile Management

2.2.1 The Contractor shall support Agile team planning and provide input for dependencies between expected product support and software and development, as well as on-prem infrastructure impacts to external development.

2.2.2 The Contractor shall collect metrics to include, but not limited to, System uptime, Cost per incident, Mean time between critical failures and mean time to restore.

2.2.3 The Contractor shall maintain a quarterly, one-year, and five-year roadmap forecast within the SPO-provided Jira instance that includes at a minimum: major upgrades, technology changes, significant concept of operations changes, and product end-of-life.

2.2.4 The Contractor shall coordinate and gain approval of product technical baseline changes and the timing of any migration / adoption through the Space C2 CMB ahead of change implementation. This includes, but is not limited to, changes to product resourcing, security, interfaces (i.e., connections, data, messaging), commercial tooling, and any major product revisions.

2.2.5 The Contractor shall provide weekly activity reports summarizing key milestones, activities, and operational benefits (e.g., removed X-hours of manual tasks with automated function).

2.3 Meeting Support and Travel

2.3.1 The Contractor shall conduct a Kick-off Meeting within 30 days of contract award to include, at a minimum: special topics, roadmap review, and risk and mitigation plans.

Meeting read ahead materials shall be made available NLT 7 days prior to meeting.

2.3.2 The Contractor shall develop post-meeting minutes and respond to post-meeting action items as requested by the SPO within 24 hours of the meeting ending.

2.3.3 The Contractor shall conduct a monthly Program Management Review (PMR) alternating each month between an Executive-level PMR and a Program Manager-level PMR. The PMR shall be virtual, unless otherwise specified by the Government Lead, or their designee. The PMR draft agenda shall sent to the Government Lead no less than five (5) business days prior to the PMR and the agenda shall be approved by the Government Lead.

2.3.4 The Contractor shall develop post-PMR minutes and respond to post-PMR action items.

2.3.5 The Contractor shall obtain written approval by the Government Lead, or their designee, ahead of travel that is already authorized in the contract. DRAFT

CUI 10

2.3.6 The Contractor shall support quarterly, multi-day (nominally three-day), in-person Program Increment events in Colorado Springs, Colorado. The location, duration, and frequency may change as requested by the SPO.

2.3.7 The Contractor shall support quarterly, two-week long, in-person test events at operator location(s). Initial operator location will be at Vandenberg Space Force Base, CA;

alternative locations may include, but are not limited to, Dahlgren Naval Support Facility, VA and Schriever SFB, CO. The duration and frequency may change as requested by the SPO.

2.3.8 The Contractor shall make their own travel and lodging arrangements and shall ensure all required security requirements (e.g., Visit Requests) required for access to installations and/or facilities are completed prior to travel. Compact Cars and Economy seats shall be used when available.

2.3.9 The Contractor shall support meetings with mission partners and stakeholders as needed at required classification levels at a minimum Quarterly.

2.4 Contract Data Requirements List (CDRL)

2.4.1 The Contractor shall provide the CDRLs identified in Table 2. The SPO will review the submission of data per the CDRL prior to acceptance, acceptance criteria will include verification of appropriate intellectual property markings.

Table 2: Contract Data Requirements List

# CDRL Frequency A001 Cost Funds Status Report (CFSR) Monthly A002 Program Protection Implementation Plan (PPIP) Once A003 Data Accession List (DAL) Periodic A004 Program Management Review (PMR) Monthly

2.4.2 A001 CFSR shall follow SPO-provided template.

2.4.3 A002 PPIP shall address the Government’s Program Protection Plan and follow the section formatting contained within

2.4.4 A003 DAL shall include the below items at a minimum. A003 DAL Submission shall include meeting minutes, briefing material, bill of materials, and other documentation as requested by the SPO.

• Transition plan,

• Small Business Contract Plan as applicable,

• PMR material and meeting minutes,

• Weekly activity reports,

• 24/7 NOC-specific procedures, training, and call-trees, and

• Architecture drawings.

CUI 11

• Program Management plan,

• Staffing Plan,

• Subcontract information,

• Organizational Conflict of Interest Plan

2.4.5 A004 PMR shall include content provided within the SPO-provided template. This includes, but is not limited to:

• Internal (execution) product risks,

• External (dependency) product risks,

• Metrics,

• Organizational structure and projected staffing changes that spans a minimum of a

30-day forecast,

• Obligation and expenditure status and forecast,

• Invoice status,

• Travel projections, and

• Bill of materials.

2.6 Associate Contractor Agreements & Other Agreements

2.4.6 The Contractor shall enter into ACAs with the contractors listed at Vandenberg Space

Force Base (VSFB) to support cross-project integration for accomplishment of the SPO’s requirement. Additional contractors requiring ACAs may be identified by the SPO throughout the duration of the contract.

2.4.7 The Contractor shall establish ACAs with new vendors within 45 days of notification by the Government.

2.4.8 The ACA(s) shall include the basis for sharing information, data, technical knowledge, expertise and resources essential to integration, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

2.4.9 The ACA(s) shall include the following general information:

• Identification of the associate contractors and their relationships;

• Identification of the program involved and the relevant Government contracts of the associate contractors;

• Description of the associate contractor interfaces by general subject matter to include specification of the categories of information to be exchanged or support to be provided;

• Inclusion of cross-collaboration for development of RFCs or any changes that may be presented to a Space C2 CMB.

• The expiration date (or event) of the ACA;

• Identification of potential conflicts between relevant Government contracts and the

ACA; and

CUI 12

• Inclusion of agreements on protection of proprietary data and restrictions on employees.

2.4.10 The Contractor shall provide a copy of the ACA(s) to the Contracting Officer(s) for review before execution of the document by the cooperating contractors.

2.4.11 The Contractor shall not be relieved of contract requirements or entitled to adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

2.4.12 Liability for the improper disclosure of proprietary data contained in or referenced by agreements shall rest with the parties to the agreement and not the Government. If improper disclosure of proprietary data occurs, the Government shall be notified immediately.

2.4.13 All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended by the Government during the performance of this contract.

2.4.14 The contractor shall cooperate with Federally Funded Research and Development Center (FFRDC) contracts, as identified within the Space C2 contractors list.

3 Personnel & Staffing

3.1 General

3.1.1 The Contractor direct support personnel shall be located on-site at VSFB.

3.1.2 The Contractor shall provide coverage to provide on-site 24/7 support.

3.1.3 The Contractor shall provide infrastructure support on a 5-days-a-week, 12-hours-a-day (5/12) basis, as well as limited weekend and late-night support during test events, with on-call support for non-duty hours and weekends. See Section 5.1 for further details.

3.2 Key Program Personnel

3.2.1 The Contractor shall establish and maintain an organizational team structure possessing the knowledge, skills, and experience capable of performing all requirements.

3.2.2 The Contractor shall assign to the contract those persons, whose resumes, were submitted in their proposal as required in the Request for Proposal (RFP) to fill the Key Personnel requirements of the contract. These persons shall fill the Key Personnel positions for not less than one year from the contract effective date.

3.2.3 The Contractor shall ensure that during the first year of contract performance period; no Key Personnel substitutions will be permitted unless such substitutions are necessitated by an individual's sudden illness, death, or termination of employment. In any of these events, the Contractor shall promptly notify the Contracting Officer and provide the information required by paragraph below.

CUI 13

3.2.4 Key Personnel are required to be 100% assigned to this effort for a minimum of the first 12 months unless there is an unforeseen circumstance. If Key Personnel for whatever reason become unavailable for work under the contract for a continuous period exceeding 30 working days the Contractor shall propose a substitution of such Key Personnel.

3.2.5 All proposed Key Personnel substitutions shall be submitted, in writing, to the Contracting Officer and Contracting Officer Representative (COR) at least fifteen (15) calendar days before motnhly PMR. Each request shall provide a detailed explanation of the circumstances necessitating the proposed substitution, a complete resume for the proposed substitute and any other information required by the Contracting Officer. All proposed substitutes shall have qualifications equal to or higher than the qualifications of the original Key Personnel being replaced and shall meet the minimum Key Personnel labor category requirements.

3.2.6 The Contracting Officer and COR will evaluate Key Personnel substitution requests and promptly notify the Contractor, in writing, of whether the request is approved or disapproved. All disapprovals will require resubmission of another substitution within fifteen (15) calendar days.

3.2.7 If the Contracting Officer determines that suitable and timely replacement of Key Personnel who have been reassigned, terminated, or have otherwise become unavailable to perform under the contract is not reasonably forthcoming or that the resultant reduction of productive effort would impair the successful completion of the contract, the contracting officer shall take appropiate action in acccordance with the conditions set and agreed upon in the contract.

3.2.8 The labor categories and personnel listed below are identified as key personnel for this contract:

3.2.8.1 List to be filled in by Contract Awardee: <Key Personnel Duty Title> (<labor category>) – Responsible for <insert responsibilities here>.

3.3 Personnel Clearances, Network, and Facility Access

3.3.1 All Contractor direct support personnel shall be TS/SCI eligible.

3.3.2 All Contractor direct support personnel shall be US citizens and shall obtain and maintain a Common Access Card (CAC) (see DoD Manual (DoDM-1000.13-M-V1) for CAC issuance criteria).

3.3.3 All Contractor direct support personnel shall obtain and maintain Secret Internet Protocol Router Network (SIPRNet) access.

3.3.4 A minimum of 25% of contractor direct support personnel shall obtain and maintain Joint Worldwide Intelligence Communications System (JWICS) access. DRAFT

CUI 14

3.3.5 The Government Contracting Officer’s Representative will determine who is nominated for SCI access based upon recommendations from the Contractor’s Program Manager

3.3.6 The SPO will provide the system security classification and guidance as required. Work involving access to or production of classified information will be performed at the direction of the SPO. All classified material will remain under the control of the Department of the Air Force including disposition of any classified material at the completion of the contract. Other security instructions applicable to this contract will be determined by the SPO as required.

3.3.7 The Contractor shall obtain the latest facility/installation and IT requirements for network access from the applicable local Security Office. Granting of logical and physical access privileges remains a local policy and business operation function of the local facility.

4 Tier 1 24/7 Support Team

4.1 24/7 NOC Stand-Up

4.1.1 The Contractor shall establish and maintain a 24/7 NOC at VSFB.

4.1.2 The Contractor shall modify and maintain Government provided procedures, training, call trees, and other product support material as needed. Where necessary, the Contractor shall coordinate and build call tree procedures, troubleshooting procedures, and training products to support the 24/7 NOC operations. This includes modifications in support of added applications and/or systems.

4.1.3 The Contractor shall coordinate with platform, data, and application teams to modify monitoring / operational dashboards as needed to support the Contractor’s ability to efficiently run through troubleshooting procedures. This includes modifications in support of added applications and/or systems.

4.1.4 The Contractor shall develop a consolidated training plan for 24/7 NOC team member certification.

4.1.5 The Contractor shall develop and implement 24/7 NOC crew facility layout in coordination with 18 SDS, Space C2 platform teams, and other Contractor-identified units. Note: The SPO anticipates the 24/7 support team will sit on the TS/SCI operational floor in VSFB Building 8401.

4.1.5.1 A minimum of 50% of crew strength must be maintained as bench strength in the event of incapacitation.

4.2 General 24/7 Tier 1 Support DRAFT

CUI 15

4.2.1 The Contractor shall provide 24/7 Tier 1 support to Space C2 software products, network interfaces, network infrastructure, infrastructure, and platform services. Tier 1 support can be generally defined as:

• Account/password resets

• Simple restores

• System response

• Service request ticket submissions via KM Jira helpdesk

• Initiation of Tier 2 after hour support recalls / call trees

• Enablement of 2-minute system support and roll back procedures as required

• Initiation of rollback or failover procedures if procedures dictate such actions

• System status documentation by shift

• End of shift reporting

4.2.2 The Contractor shall provide system health utilizing dashboards and call tree procedures.

4.2.3 The Contractor shall utilize screen captures, user-reported symptoms, and any other available information to document off nominal conditions.

4.2.4 The Contractor shall report deviations from nominal system conditions in an end of shift report, to include what software or systems are showing off nominal conditions, the symptoms, and the time of such symptoms. All end of shift reports shall be consolidated and stored on a Government designated platform.

4.2.5 The Contractor shall relay off-nominal conditions to Tier 2 and/or Tier 3 product support tiers based on documented procedures. The information shall be relayed at the lowest security level possible, while still providing meaningful data.

4.2.6 The Contractor shall coordinate with the Space C2 configuration management and cyber teams to disposition any system configuration changes required to respond to system outages.

4.3 24/7 Software Product Monitoring

4.3.1 The Contractor shall provide 24/7 on-site support for Space C2 software capabilities.

This includes monitoring at Secret for on-prem and cloud-hosted (Impact Level-6) software applications and will include monitoring at TS/SCI for cloud-hosted software applications in the future.

4.3.2 The Contractor shall resolve basic user system access issues identified in Section 4.2.

4.3.3 The Contractor shall track system status and trends from the provided dashboards to predict and restore system operational capabilities in a Government approved report.

4.3.4 The Contractor shall execute workflows to inform and track Tier 2 support regarding a failure mode or degradation of service pertaining to that system. In the case of unclear DRAFT

CUI 16

cause of degradation, the Contractor shall perform initial contact to multiple Tier 2 contacts to further identify the source of the failure.

4.3.5 The Contractor shall provide 24/7 on-call software support to include reach-back capabilities for all Commercial-Off-The-Shelf (COTS) and Government-Off-The-Shelf (GOTS) software.

4.3.6 The Contractor shall serve as a 24/7 help desk. This includes assisting users with resolving basic system access issues and maintaining track of system status to understand which systems are up/down to support users who are having problems with system access.

4.4 24/7 Network Monitor Function

4.4.1 The Contractor shall provide 24/7 on-site support for Space C2 networking capabilities.

This includes network monitoring across Secret and TS/SCI for the following systems:

• SPARTAN (network)

• SDANet (network)

• SDIN (network)

• MeshOne-T (network)

• CPS (network)

• WarpCore (data layer)

• NDPP (software and external hardware system)

4.4.2 The Contractor shall leverage the SPO JIRA ticketing system to track and close all networking issues regarding system failures.

4.4.3 The Contractor shall provide trained personnel that are continuously observing delivered dashboards, executing procedures that have been approved by the Government, and notifying Tier 2 and 3 teams of unusual behavior which could eventually lead to system failure or degradations in network connectivity.

4.4.4 The Contractor shall respond to inquiries from operators, developers, and stakeholders.

4.5 24/7 Network Monitor Function – Tier 1 Support

4.5.1 The Contractor shall execute tier 1 support directly for SPARTAN and SDANet.

4.5.2 The Contractor shall execute additional network connectivity checks to validate all network failures and to further identify the source of failed connection.

4.5.3 The Contractor shall monitor networking metrics to identify network congestion or other aspects of network degradation and report to the appropriate.

4.5.4 The Contractor shall continuously analyze workflow of metrics to further identify root causes in order to support reduction in cost latency, and increased throughput quarterly.

CUI 17

4.5.5 The Contractor shall execute pre-determined contingency plans in the case of significant degradation to restore network service to critical operations.

4.5.6 The Contractor shall notify affected operators regarding a degradation in capability of network connectivity and perform pre-determined workflows.

4.5.7 The Contractor shall notify affected operators when network capabilities are restored or improved to nominal capabilities.

4.6 24/7 Infrastructure and Platform Monitoring

4.6.1 The Contractor shall provide Tier 1 24/7 support to include monitoring dashboards, performing trend analysis using key data parameters from dashboards, notification of "yellow" system state, rapid escalation of "red" system state to Tier 2, and executing pre-canned procedures to include potentially failing over from Side A to Side B if failure is significant.

4.6.2 The Contractor shall execute workflows to inform and track Tier 2 support regarding a failure mode or degradation of platform or infrastructure service. In the case of unclear cause of degradation, the contractor shall perform initial contact to multiple Tier 2 contacts to further identify the source of the failure.

5 Infrastructure Support Response

5.1 General

5.1.1 The Contractor shall provide 5/12 support as specified in Section 3.1.3. This support shall include:

• One primary and one secondary technician on call via telecom

• 2-hour response time from initial contact and acknowledgement

5.1.2 The Contractor shall document discrepancies using three categories:

• Routine: no impact to operational mission, can be resolved during normal duty hours

• Urgent: results in limited system degradation, mission essential operations are not affected

• Emergency: directly impacts mission capability and requires immediate action

5.2 Infrastructure Support

5.2.1 The Contractor shall maintain the below Space C2 Infrastructure items located in VSFB

Building 8401. All Section 5.2 actions are in regards to the below infrastructure items.

• Firewalls

• Switches

• Linux and Windows VMs

• Cloud/Blade server configurations

CUI 18

• Desktop support

• Storage arrays

• Edge Devices

• Last mile connectivity to KM environment(s)

• Manage external data feeds to Space C2 environments

5.2.2 The Contractor shall provide support to transition Space C2 mission operations from existing systems to modern products through scheduled and unscheduled support actions that maintain the status and health of the system and enable quick restoral of service once a failure occurs. This support includes, but is not limited to:

• Fault detection and isolation

• Replacement of failed Line Replaceable Units (LRUs)

• Accomplishment of scheduled/preventive maintenance actions

• Identification of system improvements and modifications

• Obsolescence management

• Configuration control of system network and software within the boundary

• File and database administration

• Installation of approved updates

• Stock control of on-site spares, miscellaneous parts, and work order residue

5.2.3 The Contractor shall train and provide on-prem support to the Space C2 Hardware as a Service (HaaS) team.

5.2.4 The Contractor shall deliver hands-on expertise and configuration as well as maintain admin and super user accounts for each.

5.2.5 The Contractor shall ensure each of the items are properly documented, configuration controlled through Space C2 CMB process, and up to date with security relevant software/firmware upgrades.

5.2.6 The Contractor shall conduct and support system level troubleshooting and fault isolation.

5.2.7 The Contractor shall maintain an operational relevant spare posture for on-prem infrastructure.

5.2.8 The Contractor shall manage software licenses and warranties required to run and support all on-prem infrastructure. This includes managing license and certificate expirations, ensuring that expiration dates are not hit.

5.2.9 The Contractor shall coordinate with Base IT, Infrastructure Teams, the SPO, and other relevant organizations for connections and approvals for changes.

5.2.10 The Contractor shall participate in local area and Space C2 change boards when they impact or have the potential to impact Space C2 efforts.

CUI 19

5.2.11 The Contractor shall coordinate and support the execution of various cybersecurity analyses to include both hands-on vulnerability tests as well as passive cyber analyses.

5.2.12 The Contractor shall maintain appropriate on-prem expertise to complete all urgent and non-urgent tasking to include on-boarding and training new members of the team.

5.2.13 The Contractor shall work with the SPO and HaaS teams to determine and prioritize tasking.

5.2.14 The Contractor shall inform the SPO and HaaS teams in a timely manner for high-risk tasks or those to which the on-prem team does not have the full scope or skills required to complete the task safely and efficiently.

5.3 Operations and Service Desk Support

5.3.1 The Contractor shall serve as an extension of Space C2 teams, acting as a standalone service desk to users during regular hours.

5.3.2 The Contractor shall assist with access and visit requests to the facility with Government coordination and approval.

5.3.3 The Contractor shall perform file transfers from low to high side to support tests and/or operations with Government approval.

5.3.4 The Contractor shall establish and maintain user accounts and role-based access controls

(RBAC).

5.3.5 The Contractor shall assign, renew, and change account passwords (also discussed in Section 4.2).

6 Placeholder – any MOSSAIC Scope

6.1 TBD

6.1.1 TBD

7 Transition Support

7.1 Transition-in Plan

7.1.1 The Contractor shall develop and ensure the successful implementation of a transition-in plan and identify dependencies which will require government acceptance.

7.1.2 The on-ramp plan shall include a plan for the successful transfer of the MOSSAIC Scope under the MOSSAIC DSC2-D contract, current 24/7 support under the NISSC II contract, and the Space C2 Infrastructure as a Service on-prem support under the Iris/KTAC FedSIM contract. DRAFT

CUI 20

7.1.3 The on-ramp plan shall include how the Contractor shall successfully integrate services and products and their respective environments. This includes, but is not limited to SDANet, SPARTAN, C2Ops on-prem, and the Space C2 software (i.e., ATLAS, Iris, Hyperion clusters).

7.1.4 The on-ramp plan shall include the staffing required over time to complete the on-ramp and the Contractor’s plan for obtaining the associated staffing profile.

7.1.5 The Contractor shall develop and maintain a checklist and schedule of actions that must be accomplished by the end of the on-ramp period, not to exceed a 60-day duration.

7.1.6 The Contractor shall identify within the first 30 days of the on-ramp period all the government property, information, and/or data that the Contractor plans to transition for use on this effort.

7.1.7 The Contractor shall manage and execute the on-ramp plan to support transition of sustainment responsibilities, ensuring mission requirements are met without interruption.

7.1.8 The Contractor shall assume management responsibility for all government property, information, and/or data identified and approved by the SPO by the end of the on-ramp period.

7.1.9 The Contractor shall perform an accounting inventory during the on-ramp period to transfer equipment accountability.

7.1.10 The Contactor shall work with the SPO within the first 21 days of the on-ramp period to identify Associated Contractor Agreements (ACA) and Agreements with government organizations needed for execution of this requirements document and shall execute those agreements by the end of the on-ramp period.

7.1.11 The Contractor shall conduct an initial kick-off meeting and bi-weekly management reviews, during the on-ramp period, to provide status of the transition tasks, risks, and issues. The Contractor shall conduct more frequent reviews if needed to ensure successful completion of all transition tasks needed to support full transference from the various incumbents to the 24/7 NOC contract by the end of the on-ramp period.

7.2 Transition Plan for Closeout

7.2.1 The Contractor shall support a transition to a new contract(s) and/or new contractor(s) upon period of performance completion. Transition support shall begin up to 6-months prior to contract end or as specified by the SPO.

7.2.2 The Contractor shall ensure the successful implementation of a transition plan and identify dependencies which will require government acceptance.

7.2.3 The transition plan shall ensure the successful transfer of responsibility for the total contract scope, or alternative sub-scope as specified by the SPO. Transfer of DRAFT

CUI 21

responsibility includes ensuring the successful integration of services and products and their respective environments.

7.2.4 The Contractor shall manage and execute the transition, ensuring mission requirements are met without interruption.