Attch2_Exh_F_20F4100 PWS.pdf

PERFORMANCE WORK STATEMENT

Missile Defense Agency (MDA)

Integrated Research & Development for Enterprise Solutions (IRES)

Contract Number: HQ079617D0001

Task Order Title: Missile Defense Space Center (MDSC) Operations and

Maintenance

Task Order Number: HQ085720F4100

Period of Performance: 24 JUL 2020 – 08 AUG 2022

Page | 2

Table of Contents

1.0 Purpose

1.1 References

2.0 Background

2.1 MDA/SS Directorate

3.0 Scope

4.0 Service Summary Items ........................................................... Error! Bookmark not defined.

5.0 Contract Data Requirements List (CDRL)

5.1 CDRL and DIDS

5.2 CDRL Tailoring ........................................................... Error! Bookmark not defined.

6.0 Milestones

7.0 Government Property

7.1 Additional Government Furnished Property

7.2 Additional Government Furnished Information

7.3 Contractor Acquired Property

8.0 Special Requirements

9.0 Applicable Documents

10.0 Statement of Objectives and Outcomes

10.1 Task Order Administration

10.1.1 Task Order Management ........................... Error! Bookmark not defined.

10.1.2 Enterprise Task Order Support ................ Error! Bookmark not defined.

10.1.3 Task Order Award and Modification ....... Error! Bookmark not defined.

10.2 Mission Capability Development

10.2.1 Mission Capability Upgrades

10.2.2 Technical Projects

10.2.3 MDSEA Innovation

10.2.4 SKA Operationalization Support

10.2.5 Design, Build, and Implement the HBTSS Ground Segment

10.2.6 Missile Defense Space Operations Center (MDSOC) (Facility

Infrastructure)

10.2.7 Additional site activation [RESERVED]

10.3 MDSC Sustainment

10.3.1 MDSEA Service Management

10.3.2 MDSEA environment

Page | 3

10.3.3 MDSEA / MDSC modifications / repairs

10.3.4 Storage:

10.3.5 Cyber Support

10.3.6 Logistics Support

10.3.7 General visit and DV support and escorts

10.3.8 Factory Support Center(s)

10.3.9 MDSOC Sustainment and Support [RESERVED]

10.3.10 MDA/SS Functional Board Support

10.3.11 NOC Capabilities

10.3.12 Engineering

10.3.13 Data Management

10.3.14 Specialized Products and Services

10.3.15 Core Decommission Project

10.4 Satellite Operations

10.4.1 MDSOC Operational Processes and Procedures

10.4.2 Space Based Kill Assessment (SKA) Mission Support

10.4.3 Hypersonic and Ballistic Tracking Space Sensor (HBTSS)

Mission Support [RESERVED]

10.5 Mission Support Tasking (MST) [RESERVED]

Attachment 1 – Capability Development

Attachment 2 – MDSC Core to MDSEA Migration Items Error! Bookmark not defined.

Attachment 3 – Migration Schedule ..................................... Error! Bookmark not defined.

Attachment 4 – SKA Operationalization Schedule............. Error! Bookmark not defined.

Page | 4

1.0 Purpose

Develop, Integrate and Sustain the MDSEA SOC and MDSEA for future Operational and

Research and Development (R&D) of Experimental or Developmental BMDS space capabilities and systems.

1.1 References

Document Name Date

MDSEA Concept of Employment Current Version

MDA Assurance Provisions, MDA-QS-001-MAP Current Version

MDA Security Classification Guideline Current Version

Configuration Management Guidance, MIL Handbook-61A Current Version

Consensus Standard for Configuration Management, SAE/EIA-649B Current Version

FAR Part 52 Applicable Clauses Current Version

DoDI 8500.01 Current Version

Cybersecurity and NIST SP 800-53 Current Version

DoDI 8510.01, Risk Management Framework Current Version

National Security Telecommunications and Information Systems Security Policy No. 11

(NSTISSP 11)

Current Version

MDA Directive 3000.02, Ballistic Missile Defense System Asset Management

Scheduling, Planning and Execution

Current Version

Government Documents (Directive & Guidance) as listed in SWDC CSOW Current Version

MDA Directive 8180.01, Enterprise Records Management Current Version

MDIOC Unified Facilities Guide Specification (MUFGS) and Facility Excellence Plan Current Version

BMDS Integrated Master Test Plan Current Version

TBD Others

2.0 Background

2.1 MDA/SS Directorate

This task order is a follow-on to IRES task order HQ0796-18-F-4100 “Missile Defense Space

Enterprise Architecture”.

Page | 5

3.0 Scope

Develop, Integrate, Sustain, and Operate the MDSEA SOC and MDSEA for future Operational and Research and Development (R&D) of Experimental or Developmental BMDS space capabilities and systems. This scope includes maintenance, studies, analysis, detailed requirements definition, system engineering, preliminary and detailed system architecture designs, prototyping, and system development of Enterprise Services, ground systems, and operations centers to include all supporting facilities, infrastructure, networks, development, integration, logistics plans, cybersecurity and physical security protection plans, and supporting cost and schedule estimates for the development, fielding (launch), ground and flight test, and operations of planned space capabilities. Provide operators and support staff as required to support MDA/SS missions.

There are three main lines of effort contained within the technical tasking area of this PWS:

1. Capability Development (10.2)

2. MDSC Sustainment (10.3)

3. Satellite Operations (10.4)

A forth minor line of effort is the mission support tasking area for future TBD project efforts

(10.5)

Page | 6

4.0 RESERVED

5.0 Contract Data Requirements List (CDRL)

The point of delivery for all CDRL products is the MDA E-CaRT system. The Contractor shall deliver all such products by saving and profiling them in E-CaRT, with the appropriate notification of delivery letter transmitted electronically to the Government’s Data Management

Office. Reference Attachment 1 for specific CDRL delivery instructions. Contract Data

Requirements List (CDRL) Identification. The contractor shall be evaluated in accordance with

Service Summary Items (SSIs) 3 & 4 which are common (required) on all task orders and will be assessed at the contract level.

5.1 CDRL and DIDS

PWS

Task

CDRL

Number

DID Title CDRL Description

10.1.22 C001 DI-

MGMT-

81861/T

HQ079618F4100:

Integrated Program

Management Report

Contains data for measuring cost and schedule performance. The IPMR is structured around seven formats that contain the content and relationships required for the electronic submissions.

10.1.2.2, 10.5

C002 DI-MISC-

80508B/T

HQ079618F4100:

Task Order Status

Report, [month ending]

Provides significant accomplishments, issues, concerns, lessons learned, and risks associated with the task order.

10.2.6, 10.3.3.3, 10.3.15, 10.3.16, 10.5, Attach 1

C003 DI-MISC-

80508B/T

HQ079618F4100:

Project Engineering

Documentation

This CDRL contains engineering documentation that potentially includes all of the following components:

Slide Package, DoDAF Artifacts, Rack Elevation drawings, Facility Layout drawings, Employment

Concept, and Requirements Traceability Matrix

(RTM), Version Description Documents, Floor Plans, and Integrated Master Schedule (IMS).

10.2.5.1, 10.2.6

C004 DI-MISC-

80508B/T

HQ079618F4100:

Space Planning

Layout

Documentation

Notional facility layouts to support the Missile

Defense Space Operations Centers and all supporting activities. Identification of ergonomic efficiencies, synergy between mission areas, physical security separation, and the consolidation of IT computing hardware in the 2200 quadrant.

10.3.14.2 C005 DI-AVCS-

80700A

COMPUTER

SOFTWARE

PRODUCT END

ITEM

MDSC Interchange System (MIS) Spiral Code

Delivery

10.3.14.2 C006 DI-IPSC-

81443

SOFTWARE USER

MANUAL (SUM)

MIS User’s Manual

10.3.6.3 C007 DI-

MGMT-

81453B

DATA

ACCESSION LIST

(DAL)

Data Accession List

10.4 C008 DI-

MGMT-

80441C

Government

Property Inventory

Report

Government Property Physical Inventory Count or

Custodial Balance Report

10.4.2.6 C009 DI-MISC-

80711A

Scientific and

Technical Reports

Mission CONOPs

10.3.1 C010 DI-MISC-

80711A

Scientific and

Technical Reports

Chargeback Showback Metrics Report

Page | 7

10.3.13 C011 DI-MISC-

80711A

Scientific and

Technical Reports

Data Management Plan

10.3 C012 DI-MISC-

80711A

Scientific and

Technical Reports

Board Support and Configuration Management

Reporting

10.4.1.1.1 C013 DI-MISC-

80711A

Scientific and

Technical Reports

Ground Segment Procedures Completed

10.4.1.1.2 C014 DI-MISC-

80711A

Scientific and

Technical Reports

Operations Status Report for MDSOC

10.4.1.3.1 C015 DI-MISC-

80711A

Scientific and

Technical Reports

MDSOC Crew Certifications Completed

10.4.2.5 C016 DI-MISC-

80711A

Scientific and

Technical Reports

SKA Event Support & Planning

10.4.2.7 C017 DI-MISC-

80711A

Scientific and

Technical Reports

Program Protection Implementation Plan

10.4.2.9 C018 DI-MISC-

80711A

Scientific and

Technical Reports

MDSOC SKA Operations Support Status Reporting

10.4.3.10 C019 DI-MISC-

80711A

Scientific and

Technical Reports

MDSOC HBTSS Operations Support Status

Reporting

* Calendar days. If calendar day ends on weekend or holiday, the document shall be delivered on the next workday.

Page | 8

6.0 Milestones

PWS Task Activity MAC

Integrated Baseline Review (IBR) 6

Cost Reports Monthly

DAL Quarterly

Customer Program Management Review Quarterly

IRES-SWDC Event Collaboration Meetings Per event

IRES-SWDC Facilities Collaboration Meetings Monthly

MIS Spiral Code Delivery

30 days following MIS Spiral development completion

Internal Use Software Valuation Report 60 days following Code Delivery

Software User Manual Delivery

30 days following MICCB approval of version release

Weekly Activity Reports [WARs] Weekly

Task Order Status Report [TOSR] Quarterly

10.2.4.1

SKA Operationalization Equipment Installation

Complete 8

10.3.2.2 Core to MDSEA Migration Complete 7

10.2.4.1 SKA Second Test String 7

10.2.5.1 Design the MDA EGS system (MEGS)

30 days following government approval of trades

10.2.5.1

Support government system integration testing of

MEGS

Initial integration testing capability

10.2.5.2 Implement/Build Payload Data Manager (PDM) 15

10.2.5.3

HBTSS MDSEA Communications Implementation and Sustainment

Provide initial support for Dev s string comms to the Performer factory locations.

10.2.5.3

HBTSS MDSEA Communications Implementation and Sustainment

Provide initial support for MEGS integration

10.2.6 Missile Defense Space Operations Center (MDSOC) 17

Page | 9

PWS Task Activity MAC

10.2.4.2 SKA Integration 19

10.2 Integrate External Program Managed systems 60 days following Code Delivery

7.0 Government Property

In addition to the any GP associated with IRES Contract SOO, paragraph 6.0, the following GP is applicable to this task order:

Equipment/Information OPR Needed For Latest MDSC Core Configuration Managed

Documentation

SS Implementation

CND Services IP addresses and domain names IC Implementation

APL developed SKA application executables with configuration instructions and all available documentation. Will also take VMs.

SKA

PO

Implementation

APL application installation and test support SKA

PO

Implementation

MIS VM images, application executables, and installation instructions

SS Implementation

SWDC application installation and test support SS Implementation

Capability to reset the root passwords on the VM images SS Implementation

APL and Host Integrator test string connectivity test support

SKA

PO

Implementation

CDS Team test string support for CDS installation and checkout

SS Implementation

ESL support to SKA test string connectivity and testing SS Implementation

X-Lab support to SKA test string connectivity and testing SS Implementation

Ground Test support to test string SKA connectivity and testing

SS Implementation

APL dev string connectivity test support SKA

PO

Implementation

CDS Team dev string support for CDS installation and checkout

SS Implementation

ESL support to SKA dev string connectivity and testing SS Implementation

X-Lab support to SKA dev string connectivity and testing SS Implementation

Facilities space for MDSEA physical hardware SS Implementation

Rack space for 4 FEXs and 2 Patch Panels in the 2308 SS Implementation

Three SKA GCEs SKA

PO

Implementation

MDA/IC Master Timing Service IC Implementation

MDA Backbone necessary to communicate with

MDA/IC provided services and required MDIOC internal/external systems

IC Implementation

MDA Enterprise HBSS ePO Service IC Implementation

MDA/IC PKI Certificate Management Service IC Implementation

MDA/IC Enterprise ACAS Service IC Implementation

MDA/IC Enterprise Linux System Patching Service IC Implementation

Page | 10

Equipment/Information OPR Needed For MDA/IC ArcSight Service IC Implementation

MDA/IC Enterprise Windows System Patching Service IC Implementation

One SKA CDS SKA

PO

Implementation

Software licenses for Core COTS apps to be migrated to the MDSEA

SS Core Migration

From SWDC PWS:

NSA approved HFGS cryptographic solution, including KIVs, with documentation

HFGS Interface System with documentation

SKA CDS with documentation

MDA backbone connectivity with required throughput

PAC hardware and software, to include test machines and router

MOU/MOA with DSS and JHU/APL for system accreditation

Interconnect Security Agreement (ISA) between

MDA/MDSC and JHU/APL

Required training for customized APL-provided

HW/SW

T1 connectivity between HFGS and HSV with adequate bandwidth to meet 10Mbs requirement

Early Warning System (EWS) software

EWS software maintenance

Orion support is provided by MDA/DTR

Event configuration RFSs should include, at a minimum, the event mission asset checklist, the

MDA/DTR Communications and Viewing Plan, and a MDSC Communications and Viewing Plan MDSC

Collision Avoidance (COLA) Process document

IRES AdminGenser equipment

Latest MDSC Core Configuration Managed

Documentation

SS Implementation

CND Services IP addresses and domain names IC Implementation

APL developed SKA application executables with configuration instructions and all available documentation. Will also take VMs.

SKA

PO

Implementation

APL application installation and test support SKA

PO

Implementation

MIS VM images, application executables, and installation instructions

SS Implementation

SWDC application installation and test support SS Implementation

Capability to reset the root passwords on the VM images SS Implementation

APL and Host Integrator test string connectivity test support

SKA

PO

Implementation

CDS Team test string support for CDS installation and checkout

SS Implementation

ESL support to SKA test string connectivity and testing SS Implementation

X-Lab support to SKA test string connectivity and testing SS Implementation

Page | 11

Equipment/Information OPR Needed For Ground Test support to test string SKA connectivity and testing

SS Implementation

APL dev string connectivity test support SKA

PO

Implementation

CDS Team dev string support for CDS installation and checkout

SS Implementation

ESL support to SKA dev string connectivity and testing SS Implementation

X-Lab support to SKA dev string connectivity and testing SS Implementation

Facilities space for MDSEA physical hardware SS Implementation

Rack space for 4 FEXs and 2 Patch Panels in the 2308 SS Implementation

Three SKA GCEs SKA

PO

Implementation

MDA/IC Master Timing Service IC Implementation

MDA Backbone necessary to communicate with

MDA/IC provided services and required MDIOC internal/external systems

IC Implementation

MDA Enterprise HBSS ePO Service IC Implementation

MDA/IC PKI Certificate Management Service IC Implementation

MDA/IC Enterprise ACAS Service IC Implementation

MDA/IC Enterprise Linux System Patching Service IC Implementation

MDA/IC ArcSight Service IC Implementation

MDA/IC Enterprise Windows System Patching Service IC Implementation

One SKA CDS SKA

PO

Implementation

Software licenses for Core COTS apps to be migrated to the MDSEA

SS Core Migration

SKA Operator Training Requirements (Excel) SKA Training

7.1 Additional Government Furnished Property

In addition to the Government Furnished Property (GFP) identified on IRES Contract

Attachment 5, the following GFP is applicable to this task order: none.

7.2 Additional Government Furnished Information

The following Government Furnished Information (GFI) is applicable to this task order: All requisite SKA operator training material, manuals, standard operating procedures, and additional documents to support the activation of SKA operations from the MDIOC.

7.3 Contractor Acquired Property

All Contractor Acquired Property (CAP) shall be managed under the terms and conditions associated with task order 18F8900 – Government Property Management task order.

8.0 Special Requirements

In addition to the special requirements in IRES contract SOO, paragraph 7.0, the following are applicable to this task order:

This task order shall be executed in accordance with the MDA security classification guidance.

WARNING - INTERNATIONAL TRAFFIC IN ARMS REGULATION (ITAR): Ballistic

Page | 12

Missile Defense System (BMDS) technology is restricted under the International Traffic in Arms

Regulation (ITAR), which controls the export and import of defense-related material and services. Activities under this task must comply with the safeguarding of this information.

Parties must disclose any proposed use of foreign nationals, their country of origin, and what activities each would participate in under this task.

WARNING- This document contains information that may be exempt from mandatory disclosure under the Freedom of Information Act.

9.0 Applicable Documents

In addition to the directives and regulations identified in the IRES Contract SOO, paragraph 8.0, the following documents are applicable to this task order:

Page | 13

Title Originator Date

DoDI 5200.44, “Protection of Mission Critical Functions to

Achieve Trusted Systems and Networks (TSN)”

DoD CIO

USD/AT&L

NIST SP 800-53, “Security and Privacy Controls for Federal

Information Systems and Organizations”

NIST

CNSSI 1253, “Security Categorization and Control Section for

National Security Systems”

CNSS

ENCLAVE Test and Development Security Technical

Implementation Guide (STIG) Memo

DISA

MDA BMDS High Altitude Exoatmospheric Nuclear

Survivability (HAENS) Standard

MDA

Strategic Command Directive (SD) 538-2, Operations, Planning, and Command and Control, Global ballistic Missile Defense

Systems (GBMDS) Physical Security Program

USSTRATCOM

MDSEA Employment Concept MDA/SS

Interim Cybersecurity Guidance for RDT&E Enclaves and

Systems (MDA/DX Memorandum, 9 January 2018)

MDA/DX

MDIOC Unified Facilities Guide Specification (A024-8003-3699) MDIOC

Spacebased Kill Assessment Program Protection Plan (PPP) MDA/DE

SKA Security Classification Memorandum MDA/D

Hypersonic and Ballistic Tracking Space Sensor (HBTSS)

Program Protection Plan (PPP), Version 1.0

MDA/SS

Ballistic Missile Defense System (BMDS) Security Classification

Guide (Change 1) (with classified appendix)

MDA/D

Consolidated National System for Geospatial Intelligence (NGA)

(CONGA) SCG

NSG

Spacebased Kill Assessment (SKA) Security Classification Guide MDA/D

Hypersonic and Ballistic Tracking Space Sensor (HBTSS)

Security Classification Guide

MDA/SS

MDA Manual 3500.01-M, “Change Management Process”

MDA Directive 5000.17, “Ballistic Missile Defense System

Operational Capacity Baseline Procedures”

MDA Directive 3000.10 and MDA Instruction 3000.07-INS

Ballistic Missile Defense System Asset Management Directive

3000.02

Page | 14

10.0 Statement of Objectives and Outcomes

The contractor shall meet all requirements/tasks identified within section 10 as follows:

10.1 Task Order Administration

This PWS section contains the scope, objectives and outcomes to provide Task Order (TO) administration and management within the integrated framework of the IRES contract. This PWS element includes both TO specific and IRES contract scope required to manage and administer

TOs.

10.2 Mission Capability Development

All capability development described in this section will follow the procedure/tasks identified in

Attachment 1 - Capability Development. The contractor shall execute in accordance with and performance will be evaluated using PWS 4.0 SSI #7.

10.2.1 Mission Capability Upgrades

Provide engineering expertise and capabilities to maintain mission systems across the MDSC facility. Work with the MDSC staff to prioritize the execution of maintenance activities within available funding constraints. Upon identification of the need for a system upgrade, the contractor shall establish statement of need, coordinate data elements, develop a schedule, establish stakeholder requirements, brief ERB & MICCB boards, develop detailed designs, define capabilities, perform network and software design, perform development and testing, establish connectivity, develop lessons learned, and document operating procedures and updating architecture drawings as appropriate.

10.2.2 Technical Projects

The contractor shall provide technical oversight for all phases of project planning, design, scheduling, execution and reporting to ensure technical solutions for projects meet their mission, goals, and objectives. The Contractor shall implement solutions, upgrades, enhancements and reconfigurations completing the planning, design, procurement, implementation, documentation and configuration management activities.

10.2.2.1 MDA Enterprise Ground Services (MEGS)

The contractor shall develop the design including software and hardware to which will be used to implement MEGS providing the following services for the Satellite Operations portion of

HBTSS:

TT&C

Ground Resource Management

Ground Resource Scheduling

Front End Processing (includes RF equipment)

Crypto Integration

EGS Platform to include C2MS/GMSEC Messaging bus

Data storage

Data analysis (telemetry)

Flight dynamics

Mission Management

Simulation

External communications

Page | 15

The contractor shall use services available in the EGS service catalog to the maximum extent possible. Note: EGS Service Catalog is available at:

https://confluence.di2e.net/display/public/EGS/Service+Catalog

For services not in the EGS service catalog the contractor shall recommend to the Gov’t the service that best meets HBTSS needs during the SRR/PDR/DDR process for approval.

For services not in the EGS service catalog the contractor shall use the EGS Software

Development Kit to integrate selected applications to provide the service functions.

The contractor shall present the S/W packages utilized to provide the above services for

Government Approval using the MDA/SS SRR/PDR/DDR processes.

The contractor shall use the EGS BOM to inform an open framework H/W design that will host the S/W applications providing the above Satellite Operations services. The contractor shall present the H/W design for Government Approval using the MDSC SRR/PDR/DDR processes.

Results of SRR/PDR/DDR shall be shared with all HBTSS vendors. The design shall be compliant with the approved MDSEA architecture.

Objective 1: The contractor shall derive requirements associated with HBTSS and MEGS integration into the MDIOC.

Outcomes:

Conduct customer coordination and communications

Support collaboration with team members to document and develop a Requirements

Traceability Matrix (RTM) which identifies specific requirements, derived requirements, and all infrastructure requirements

Vet the RTM with applicable stakeholders and receive approval by the COTR

Manage the RTM as a “living document” and provide notification of all updates to the

COTR

Deliver high-level requirements to the ERB/DRB

Conduct facility assessment and provide infrastructure requirements to support implementation

Objective 2: The contractor shall develop concepts and designs required to support future implementation of the derived requirements associated with MEGS into the MDIOC.

Outcomes:

Conduct customer coordination and communications

Develop concepts and initial designs sufficient to identify hardware and software necessary to integrate MEGS within the MDIOC

Identify required facility support requirements

Integrate design activities with MDIOC team, including the IRES personnel to obtain

MDA/SS ERB design approval

Develop a Rough Order Magnitude cost estimate to implement the design

Develop a draft schedule to implement the design

Objective 3: The contractor shall implement concepts and designs required to support operations of the derived requirements associated with MEGS into the MDIOC.

Outcomes:

Conduct customer coordination and communications

Page | 16

Develop concepts and initial designs sufficient to identify hardware and software necessary to integrate MEGS into the MDIOC

Integrate design activities with MDIOC team, including the MEGS personnel

Identify and deliver cost estimates for continued MEGS sustainment

Establish draft MEGS baseline

Conduct acceptance testing and obtain government acceptance of MEGS

Develop a Rough Order Magnitude cost estimate to implement the design

Develop a draft schedule to implement the design

Develop a draft of the Cybersecurity documentation to support ATO

Collaborate with required external stakeholders to define requirements to support MEGS installation

Support the software identification, planning, and installation and checkout

Page | 17

10.2.3 MDSEA Innovation

This section will not be required to follow the follow the procedure/tasks identified in

Attachment 1 - Capability Development.

Collaborate within IRES program to identify and deliver new capabilities o Utilize enterprise solutions and toolsets when appropriate to improve MDSC operations

Continuously monitor new technology or industry trends that could be applied the MDSC mission

Collaborate with MDA/SS System Engineering to identify potential Small Business

Innovation Research opportunities

Maintain a Technology Watch list including: Cloud/Containerization Services (e.g.

Kubernetes/Docker/Istio) in prep for HBTSS/MEGS; Software Defined Data Center;

Data Analytics; DevSecOps and Cyber Technologies

The contractor shall assist with concept exploration and feasibility of new MDSC capabilities as directed by the Government.

10.2.4 SKA Operationalization Support

10.2.4.1 Implement the SKA operationalization equipment package

This package will be supplied as GFE from a previous task order and will require the contractor to perform:

Requirements Analysis o RMF steps 1 (Preparation) and 2 (system categorization)

Design o Develop architectural views o Network connectivity including but not limited to: CNET, BCN, NSITE, OSF o Shared services: integrate to leverage Enterprise Services / deliver to tenants o MDSEA organic services o RMF step 3 (controls identification) o Facilities updates

Implementation o Procurement o Facility modifications o Equipment installation o Services implementation o Workload implementation o Testing o Baselining o CM documentation updates

A notional installation schedule for installation is provided in Attachment 4 through line 133.

The contractor shall update and keep the installation schedule current. In addition the contractor will clone the existing Test string and provide a second test string dedicated for GTI event support. The contractor shall provide this capability by 1 March 2021.

Page | 18

10.2.4.2 SKA Integration

Integrate SKA into the BMDS Operations network including Modeling & Simulation (M&S) and

Ground Test Capability in the MDSEA SKA Development, Test and Operational environments.

The contractor shall utilize the MDSC Engineering Review Board approved high-level requirements and processes in Attachment 1 to accomplish the following:

Requirements Analysis and derivation to identify:

o SKA Operational, Test and Development String Interfaces (e.g. BCN, CNET, FSC, OSF, NSITE, C2BMC TIL, X-Lab, ESL, HI payload and Testbed, etc.)

o Functional capabilities

Support for real & simulation time in Ground Test architectures

Provides for data distribution and transfer via approved methods from

SKA Operational and Test Strings to FSC, MDDC

Supports the SKA Ground Segment in meeting BMDS level requirements levied in BMDS SS SCN-0182 and SCN-0183 o BMDS Design Suitability Requirements Compliance, to include but not limited to:

Adheres to MDA Quality, Safety and Mission Assurance Isolation

Protection Profile, Resiliency-Maintainability-Availability metrics, System Monitoring, environmental, supply chain, etc.

o Infrastructure

Ensures capability to support simultaneous test, training and operations

(implies multiple ops and test strings)

Provision physical and virtual compute infrastructure for SKA M&S workloads in Development, Test and Operational Environments

Adherence to MDA-STD-004, " Position, Navigation, and Timing

Standard"

Enables Software promotion processes and enables evolving implementation of DevSecOps capabilites.

o Cyber Security and BMDS Safety/Mission Assurance

Ensures the MDSEA SKA Development, Test and Operational comply, as applicable, with DODI 8500.01 and BMDS level requirements levied in

BMDS SS SCN-0183

Design o Develop architectural views o Develop Network connectivity System and Services Views (SV’s and SvcV’s ) o Develop Ports, Protocol and Services Management requests o Shared services: integrate to leverage Enterprise Services / deliver to tenants o Integrate External Program Managed systems (e.g. Simulation Interface Unit

(SIU), NSITE) into MDSEA o MDSEA organic services o RMF package updates and PPSM approvals o Facilities updates

Implementation o Procurement o Facility modifications o Equipment installation

Page | 19 o Services implementation o Workload implementation o Testing o Baselining o CM documentation updates

A notional installation schedule for installation is provided in Attachment 4 in its entirety

(placeholder, notional schedule needs to be updated with Test environment work to get to

GT ready state). The contractor shall update and keep the installation schedule current.

10.2.4.3 SKA Operator Training

Objective – Fully Trained SKA Operators

The training syllabus for SKA operators is not yet developed so the contractor shall plan, schedule, and execute a training syllabus with APL to obtain training required to proficiently operate the SKA system to support training as needed.

Operators that are both qualified to operate SKA and oversea training plan updates to sustain a trained cadre of SKA operators.

10.2.5 Design, Build, and Implement the HBTSS Ground Segment

10.2.5.1 Design and Implement the MDA EGS System (MEGS)

The contractor shall deliver the Detailed Design Review (DDR) for HBTSS MEGS 30 days after notification of government acceptance of recommended applications to provide the following

MEGS services:

MEGS Service Application Type Source Notes:

TT&C Service

Embedded TT&C services:

a. UX

b. Automation

c. Storage

Neptune TT&C

Full mission capability provided by

L3Harris/

Northrop

Grumman MUS

GFE L3Harris/

Northrop

Grumman/

NRL

NEPTUNE per Gov direction, Integration by

IRES/NRL/Parsons/

L3Harris/Northrop Grumman

Storage Services TBD – This may be a lien

New

Dev

IRES/Parso ns

Integration by IRES/Parsons

Orbit Analysis/Flight

Dynamics Service

OCEAN and STK GFE/

COTS

NRL OCEAN per Gov direction, Integration by IRES/NRL

Page | 20

Embedded FD specific services:

a. UX

b. Storage

Mission Management

Service

Embedded MM specific services:

a. UX

b. Storage

VMOC GFE L3Harris/

Northrop

Grumman/

NRL

VMOC per Gov direction, Integration by IRES/NRL

MDA EGS Message

Bus

MDA EGS

Message Bus

GFE EGS Message bus per Gov direction, Integration by IRES/Parsons

Front End Processing

Service

AceCTK COTS IRES/

Parsons

Integration by IRES/Parsons

Gateway Service AceCCT COTS IRES/

Parsons

Integration by IRES/Parsons

Ground Resource

Management (GRM)

Embedded GRM specific services

a. UX

b. Automation

c. Storage

GRM GFE NRL Integration by

IRES/NRL/Parsons

Ground Resource

Scheduler (GRS)

EGS GRS GFE NRL/

Parsons

Integration by

IRES/NRL/Parsons

Data Delivery

Service

Eval Data Delivery

Service (EDDS)

New

Dev

IRES/

Parsons

Integration by IRES/Parsons

Cross Domain

Solution

Radiant Mercury GFE MDA CDS

Office

Integration by IRES/Parsons

Page | 21

Simulation Service TBD GFE L3 Harris/

Northrop

Grumman and USG

GEP

Provider

Integration by IRES/Parsons

The contractor shall provide:

Infrastructure design needed to implement the MEGS workloads.

Capacity for two local Zone A workloads and one Zone B workload.

Infrastructure requirements for HBTSS MEGS will based on government supplied workload estimates in these areas:

o Compute o Storage o Data archival offloaded from Zone A to the Zone B environment via one-way data diode o System backup and restoral capability is required

Network and Software shall be based on IRES developed, government approved designs.

Facility modifications for the MEGS capability that are required o Cabling, power (RPP), HVAC, and design elements

Complete requirements analysis and design approach

The contractor shall provide MDSEA infrastructure to implement a government provided Cross

Domain Solution (CDS) 2 months after CDS delivery.

The contractor shall provide the MEGS infrastructure to host services 6 months after the MEGS

DDR is approved by the government.

The contractor shall install initial services as they are available starting 7 months after MEGS

DDR is approved by the government. The contractor will support government system integration testing 11 months after MEGS DDR is approved by the government. The contractor shall support software and hardware updates as available from initial supplier or the corresponding applications MUS. The contractor will support continued government system integration testing efforts through Ground Readiness Review (GRR) which is estimated to be 20 months after MEGS DDR is approved by the government. The MEGS component deliveries shall be as follows for integration into the MDSEA Zone B (Dev) environment:

Page | 22

Months after DDR Approval

MEGS Service Initial Service

Application

Delivery to

IRES (Current

“as-is” unmodified versions)

Services and MUS

(L3Harris/Northrop

Grumman)

Application

Delivery for Initial

Integration

Initial

Syst.

Integration

Start

Services and

MUS

Application

Delivery for

Final

Integration

Final Syst.

Integration

Start

Telemetry, Tracking and

Commanding Service

(GFE)

1 9 11 13 13

Storage Service (TBD) TBD TBD 11 TBD 13

MDA EGS Message Bus

(GFE)

1 5 11 13 13

Ground Resource

Management (GFE)

1 9 11 13 13

Ground Resource

Scheduler (GFE)

1 8 11 13 13

Data Delivery

Service(New Dev)

N/A 8 11 13 13

Orbit Analysis/Flight

Dynamics Service (Ocean)

(GFE)

1 9 11 13 13

Front End Processing

Service (COTS)

1 9 11 13 13

Gateway Service (COTS) 1 9 11 13 13

Mission Management

Service (VMOC MDK)

(GFE)

1 13 11 13 13

Simulation Service (GFE) N/A 10 11 13 13

The contractor shall provide MEGS H/W & S/W Design and Implementation efforts including:

Procure infrastructure

Procure Non-GFE MDA Enterprise Ground Service (MEGS) applications

MEGS System integration

Deploy Platform as a Service (PaaS)

Integrate SATOPS services

Implement applications as services

Integrate services provided by other MDA sources

Page | 23

Support integration of HBTSS MUS with MEGS services

Facility modifications

Equipment installation

Support integration with MDA/IC provided communications connectivity o This includes support of inbound tasking messages and queues

Support ICD Development

Workload implementation

Testing

Support eMass updates

Support Baselining

MDSEA CM documentation updates

Any additional infrastructure H/W and S/W for MEGS

Provide the ability to deploy a repeatable, consistent and version controlled software environment into development, test and operational infrastructure, preferably through automation

Provide the ability to deploy validated, version controlled software into deployed environments, preferably through automation

Provide configuration control to ensure that software, testing and deployment tools are maintained such that the operational software is baseline always available to support on demand deployment on to “bare metal”

Execute software onboarding such that MDSEA processing time from receipt of new software to incorporation into a new deployment baseline, or rejection is less than 96 hours, excluding time spent waiting for government approvals

CDRL C004 applies. The contractor shall be evaluated in accordance with Service Summary

Items (SSIs) 3 & 4 which are common (required) on all task orders and will be assessed at the contract level.

10.2.5.2 Implement/Build Payload Data Manager (PDM)

The contractor shall deliver a HBTSS PDM capability in MDSEA by 31 Oct 2021 in accordance with the following:

HBTSS PDM infrastructure, to include platform, is required

Contractor shall provide components to implement the PDM workloads.

Contractor shall provide infrastructure capacity for two local Zone A workloads and one

Zone B workload to support HBTSS PDM requirements

Contractor shall provide infrastructure for HBTSS PDM based on government supplied workload estimates in these areas:

o Compute o Storage o Data archival offloaded to the RDT&E environment via one-way link o System backup and restoral capability is required

Network and Software shall be based on IRES developed, government approved designs

Facility modifications/constraints o Facility modifications for the HBTSS PDM capabilities are required o Contractor shall provide cabling, power (RPP), HVAC, and facilities

Page | 24

Requirements and design approach were started under a previous effort and the following effort is required:

Implementation o Procure infrastructure o Procure platform software o Platform integration o Integrate services provided by other MDA sources o Support integration of HBTSS PDM algorithms and MUS o Facility modifications o Equipment installation o Support integration with MDA/IC provided communications connectivity o Services implementation o Workload implementation o Testing o eMass updates o Baselining o CM documentation updates o Additional H/W and S/W

Provide the ability to deploy a repeatable, consistent and version controlled software environment into development, test and operational infrastructure, preferably through automation

Provide the ability to deploy validated, version controlled software into MDSEA string environments, preferably through automation

Provide configuration control to ensure that software, testing and deployment tools are maintained such that the operational software is baseline always available to support on demand deployment on to “bare metal”

Execute software onboarding such that MDSEA processing time from receipt of new software to incorporation into a new deployment baseline, or rejection is less than 96 hours, excluding time spent waiting for government approvals.

CDRL C004 applies. The contractor shall be evaluated in accordance with Service Summary

10.2.5.3 HBTSS MDSEA Communications Implementation and Sustainment

Implement approved network communications hardware changes with minimal disruption to planned data collection and satellite operations activities.

The contractor shall provide physical connectivity to designated Points of Presence in support of

HBTSS activities. The contractor shall provide the capability of establishing logical connections with external organizations using these physical communications links, and will enable transmission and receipt of information over the connections, in accordance with MDSEA, MEGS and PDM activities.

The contractor shall support HBTSS by providing connectivity to designated communications

Points of Presence (POP) within the MDIOC. The contractor shall collaborate with HBTSS

Page | 25 performers, MDA/IC, and the HBTSS Program Office to provide inputs to HBTSS communications connectivity, such as establishing communications paths and troubleshooting outages. The contractor shall support, coordinate and collaborate with HBTSS, MDA/IC, and other personnel as necessary in support of the HBTSS operational, development and experimental missions.

The contractor shall support the establishment, scheduling, execution and enablement of communications to the following PoPs and systems:

ESL

C2BMC

Ground Entry Points (TBD PoP within bldg. 720)

Real-Time Transfer Service (TBD PoP within bldg.. 720)

BMDS Communications Architecture (TBD PoP within bldg. 720)

BOA (TBD PoP within bldg. 720)

MDA/IC provided Add Site PoPs

MDA/IC provided Factory Site PoPs

Factory Support Center Connectivity

10.2.6 Missile Defense Space Operations Center (MDSOC) (Facility Infrastructure)

The contractor shall support the design and implementation of the Missile Defense Space

Operations Centers (MDSOC). The contractor shall integrate MDSEA into the MDSOC to support existing and future space based or other sensor systems. The MDSEA SOC shall have the capability to provide all phases of space system lifecycle from design, development, integration, test, launch, operations, transition to Service Provider Agencies (e.g. Air Force), or system disposal (end of life). Provide MDSEA liaison and coordination required in the outfitting of the MDSEA Space Operations Center (MDSOC) with MDA facilities and IC and DTR organizations. This includes installations of video walls, connections to the video distribution system, phones, radios, computers (connections and the equipment). Requirements and design performed under previous efforts. Tasks to be performed under this task order:

Implementation o Procurement o Facility modifications o Equipment installation o Services implementation o Workload implementation o Testing o eMass Updates o Baselining o CM documentation updates o Virtual Desktop Infrastructure (VDI) capability to support hosted missions will be in accordance with IRES developed, government approved design

Maintaining an IMS of all work being performed for the MDSOC implementation CDRL C003

(IMS) and C004 apply. The contractor shall be evaluated in accordance with Service Summary

Page | 26

10.2.7 Additional site activation [RESERVED]

Support operations that provides continuity of operations (COOP) at other sites.

Support the bed down of a new emerging capability yet to be identified that will operate up to and including at SAP/SCI classification levels.

10.3 MDSC Sustainment

10.3.1 MDSEA Service Management

The contractor shall execute a Service Management Framework using standards-based processes

(e.g. ITIL v.3) that integrate requirements management, design lifecycle, implementation/change/release and configuration management across the MDSEA technical architecture. Provide oversight and governance of key processes that ensure continuous improvement in evolving a Missile Defense Space Enterprise Architecture and Services

Organization. Specific functions include: Requirements Management, Service Level Reporting, Service Metrics, Governance (Incident, Problem, Change, Configuration, and Release

Management), and the development, management, and reporting of performance and consumption metrics.

The contractor’s Service Management Framework shall support transparent MDSEA service economics leveraging a constantly improving methodology that describes MDSEA Services in a manner meaningful to MDSC leadership, MDA/SS Program Managers and MDSEA tenants. The

MDSEA Service Management Framework shall support ease of MDSEA service ordering, provisioning, and costing which enables accurate and timely updates of Service Level

Agreements and chargeback/showback reporting for each tenant consuming MDSEA and

MDSOC services and capabilities. The contractor shall deliver a Chargeback Showback Metrics report quarterly. Deliver this IAW CDRL (C010). This CDRL shall identify the consumption rates of MDSEA managed IT resources by MDSC tenant organization/function and attributes costs for MDSEA and MDSOC shared infrastructure and desktop/client productivity to the tenant in both a showback as well as chargeback methodology based on both basic and enhanced service level agreements.

10.3.2 MDSEA environment

The contractor shall maintain the MDSEA prototype and migrate the items identified in

Attachment 2 – MDSC Core to MDSEA Migration Items.

Sustainment of all MDSEA machines and network equipment

System scanning

System patching

System O/S updates

Workload software updates

Responding to user support requests (IRs)

Establishing/maintaining CM documentation

QA activities

Application of ESS policy updates

Page | 27

User account management

Problem resolution

CVT support

CDS Support

System trending analysis

Network analysis

Fault analysis

Data management

Quality assurance

Transition the support of the MDSC from the Core to MDSEA.

A notional migration schedule is provided as Attachment 3. The contractor shall update and keep the migration schedule current. The contractor shall plan for supporting the Core as required to facilitate migration efforts. Migration items includes legacy software identified for sustainment during the MDSEA Prototype PDR:

VM Creation o Lift and shift or rebuild of VMs o Network: Certificate creation

Physical machine transition o Establish connectivity

Testing

Baselining

CM documentation updates

Collaboration and coordination with SWDC--ESL , BOA, and STSS

10.3.3 MDSEA / MDSC modifications / repairs

10.3.3.1 Provide a level of effort for MDSEA / MDSC modifications / repairs

Coordinate system modification requests

Provide a level of effort and annual material budget for “break fix repairs”.

Perform system engineering related to system modification requests o Requirements o Design o Implementation

Update CM documentation

QA activities

Provide impact analysis for new systems that may be hosted in the MDSEA & MDSOC.

Outcome will be a ROM that would be provided to the program of the system wanting to come in or modification efforts to support existing programs.

o Preliminary workload analysis o Requirements o Design o ROM development

10.3.3.2 MDSEA / MDSC Small Projects

The Contractor shall plan, design, schedule, and execute small projects. The COTR will issue an approval for small projects in the RFS tool, and prioritization for all work

Page | 28 associated with these tasks. The contractor shall use an estimate of 10 small projects annually including labor and materials.

10.3.3.3 Small Technical Projects

Objective – Small Project

The Contractor shall plan, design, schedule, and execute small projects. The COTR will issue technical direction letters (TDLs), schedule, and prioritization for all work associated with this task.

Operate in the context of the System Engineering Management Plan (SEMP) and established governance processes reflected through standardized engineering artifacts and an integrated systems engineering approach to design efforts to meet technical requirements.

Collaborate with government to obtain required CIO and DX approvals as required.

Perform project oversight to include customer coordination and communications and respond to requests for information and problem resolution.

Plan and develop sequenced, resource-loaded schedules. Identify resources needed to accomplish the project and ensure all resources have the proper work authorizations. Identify risks, work sequencing, critical paths, and procurement lead-times.

Initiate requirements management activities. Document and track requirements in a

Requirements Traceability Matrix (RTM) which identifies specific and derived requirements.

Develop design solutions and conduct design reviews (preliminary and final) for government approval. Participate in required MDIOC review boards (Project Steering Committee, Design

Review Board, Engineering and Architecture Board).

Develop, maintain, and coordinate technical documentation to include Technical Data Packages, engineering drawings, and interface control specifications for existing systems that require documentation or because of newly developed and/or modified systems. Ensure fully coordinated, redlined change documents are available for the government user and service technicians at customer turnover date; formal configuration control documentation and drawings updated and posted within 60 days of work/project completion.

CDRL C003 Baseline Engineering Documentation (Due date will be identified in each project.)

The contractor shall evaluated in accordance with Service Summary Items (SSIs) 3 & 4 which are common (required) on all task orders and will be assessed at the contract level.

Execute a project change management process.

Complete project close out activities.

Page | 29

10.3.3.4 Software Upgrades and Maintenance

Mission critical software Change Requests (CRs) will be reviewed with program office staff for approval to implement via software patches based on available resources. Maintain K-constants, databases, scripts, etc. to support operations. System Problem Reports (SPRs) and CRs will be documented, reviewed, and prioritized in the event that additional funds are placed on contract to implement a future software build.

Maintain Mission operational and supporting space and ground software to meet functionality and performance.

Capture unexpected results as best effort to identify the most likely cause and associated path forward to maintain the operational capability of the system.

Document, prioritize, and disposition software change requests with MDA/SS participation in setting the priorities based on available resources.

Implement approved software patches, with minimal disruption, to planned data collection operations.

Maintain configuration management of software in accordance with the contractor’s policies and procedures.

Maintain Mission information assurance in accordance with the system accreditation and the DD Form 254 as best effort, ensuring required system security controls are maintained, needed patches are tested and implemented, and accreditation requirements are met. Where Government funding to upgrade non-security-compliant software is not available, contractor will require approval for the continued use of the non-compliant software.

10.3.3.5 Hardware Upgrades and Maintenance

The contractor will provide best effort to replace failed units to the extent that COTS replacements can be found that provide plug-and-play replacement of functionality while also adhering to Supply Chain Risk Management best practices.

Maintain all Mission operational and supporting ground hardware to meet required functionality and performance to the extent that availability and attainability of COTS replacements allow.

Restore loss of critical mission function within 72 hours of government notification or contractor awareness (whichever occurs first) of loss of function where redundant units or replacements are available. If redundant or replacement units are not available, restore mission function as soon as possible utilizing available resources.

Implement approved hardware changes with minimal disruption to planned data collection operations.

Maintain proper inventory and configuration management of hardware in accordance with program configuration control processes.

Provide notice to of any support/obsolescence issues and develop a recommended action plan for presentation at the next logistics review.

Maintain all hardware to support information assurance requirements in accordance with the system accreditation and the DD…