23F4100_PWS.pdf

PERFORMANCE WORK STATEMENT (PWS) Rev E

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: HQ086123F4100

Period of Performance: 09 NOV 2022–08 AUG 2024

Performance Work Statement Revision History

Version Date Mod # Change Description

Rev A 12 Jan 2023 P00002 10.5.5.1 add Data Injection Tool Software

Rev B 23 Feb 2023 P00003 Definitization of the Unpriced Change Order (UCO)

Rev C 7 April 2023 P00006 Addition of Cyber lead, Pool Values & PPWPs

Rev D 29 June 2023 P00009 Additional Funding for Software Procurement/ Applicable document update

Rev E 11 Aug 2023 P00010 HBTSS Surge Support

TABLE OF CONTENTS

1. PURPOSE

1.1 References

2. BACKGROUND

2.1 MDA/SS Directorate

3. SCOPE

4. SERVICE SUMMARY ITEMS

5. CONTRACT DATA REQUIREMENTS LIST

5.1 Contract Data Requirements List Identification

5.2 CDRLs and Data Item Descriptions

5.3 CDRL Tailoring

6. MILESTONES

7. GOVERNMENT PROPERTY

7.1 Additional Government-Furnished Property

7.2 Additional Government-Furnished Information

7.3 Contractor-Acquired Property

8. SPECIAL REQUIREMENTS

9. APPLICABLE DOCUMENTS

10. STATEMENT OF OBJECTIVES AND OUTCOMES

10.1 Task Order Administration

Task Order Management

Objective: Enterprise Task Order Support Task Order Award and Modification

10.2 MDA/SS Functional Support (SysAdmin, Engineering, Risk ID, and Administration)

Material and Supply Chain Management Configuration Management MDSEA Service Management

MDA/SS Functional Board Support Cyber Support System Engineering and Integration

Event Protection Period Mission Assurance/Quality Assurance Interface Exchange Service Operations, Sustainment, and Development .. 25 MDSC Activity Coordination and Stakeholder Support

10.3 MDSEA Platform

MDSEA Sustainment

MDSEA Mission Capability Upgrades (Planning and Design)

MDSEA Innovation SpOCC Normal Operations Implement Additional Site Activation [RESERVED]

10.4 Space-based Kill Assessment

SKA Operations SKA Operator Training and Certifications SKA Factory Support Center/UARC Support Computing Environment

SKA Reporting

10.5 Hypersonic and Ballistic Tracking Space Sensor

HBTSS Operations HBTSS Training and Certification HBTSS Factory Support Center HBTSS Reporting HBTSS Ground Segment Implementation

LIST OF ATTACHMENTS

Attachment 1 Capability Development ....................................................................... 1-1 Attachment 2 Authorized Activity per Zone Table ...................................................... 2-1

Page | 1

1. PURPOSE

The purpose of IRES Task Order (TO) 4100 is to develop, integrate, and sustain the Missile Defense Space Enterprise Architecture (MDSEA) Security Operations Center (SOC) and MDSEA future Operational and Research and Development (R&D) of experimental or developmental Missile Defense System (MDS) space capabilities and systems.

1.1 References

Note: Unless otherwise specified, the current revisions of the documents below shall apply.

Document ID Title

External Documents

SFFAS 10 Accounting for Internal Use Software, Federal Accounting Standards Advisory Board

Federal Acquisitions Regulation (FAR) Part 52

Applicable Clauses

Military Handbook (MIL-

HDBK)-61A

Configuration Management Guidance

Society of Automotive Engineers (SAE)/ Electronic Industries

Association (EIA)-649B

Consensus Standard for Configuration Management

DD Form 1423 Contract Data Requirements List

DoDI 5200.39 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E)

DoDD 8140.01 Cybersecurity Workforce Management

DD Form 254 Department of Defense Contract Security Classification Specification

DoDI 8500.01 DoD Cyber Exchange

None DoD Cybersecurity Discipline Implementation Plan

MDA Directive 8180.01 Enterprise Records Management

DoD 8570.01-M Information Assurance Workforce Improvement Program

HQ079617D0001 Integrated Research & Development for Enterprise Solutions (IRES) Contract

HQ079617D0001,

Attachment J-01

Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO)

22 CFR 120-130 International Traffic in Arms Regulations

MDSC-004 Joint Operations and Incident Report Process

MDA-QS-001-MAP MDA Assurance Provisions

MDA Instruction 5200.02-INS MDA Information Security Program

MDA-QS-0003-PMAP-Rev C MDA Parts, Materials and Processes (PMAP)

DI-MISC-80508B/T MDIOC Unified Facilities Guide Specification (MUFGS) & Facility Excellence Plan

MDA Software Assurance Instruction 8500.05-INS 6 April 23

Missile Defense Agency Software Assurance Requirements

HQ079620F4100 Missile Defense Space Enterprise Architecture Performance Work Statement

Page | 2

Document ID Title

MDA Directive 3000.02 Missile Defense System Asset Management Scheduling, Planning and Execution

MDA Instruction 3000.04-INS Missile Defense System Joint Engineering and Test Integrated Master Test Plan Development

MDA Directive 3200.06 Missile Defense Test Data/Information Management

National Security Telecommunications and Information Systems Security (NSTISSP) Policy No. 11

National Information Assurance Acquisition Policy

ISO 9001:2000 Quality Management Systems Requirements

MDA-QS-001-MAP-Rev C Requirements Applicability Matrix (RAM) (in approval stage)

DoDI 8510.01 Risk Management Framework

NIST Special Publication (SP) 800-53 (related: NIST

SP 800-53A)

Security and Privacy Controls for Information Systems and Organizations

HQ085720F8900 Supply Chain Product Support and Government Property Management Performance Work Statement

IRES Documents

DA-23F4100-07734 MDSEA Employment Concept

Other Applicable Standards and References

None Government documents (i.e., directives and guidance) as listed in the Specialized Warfare Development Contract (SWxDC) Contractor Statement of Work (SOW) (CSOW)

None IT Infrastructure Library

2. BACKGROUND

2.1 MDA/SS Directorate

IRES TO 23F4100 is a follow-on to HQ085720F4100, Missile Defense Space Enterprise Architecture Performance Work Statement.

3. SCOPE

The scope of IRES TO 4100 includes the maintenance, studies, analysis, detailed requirements definition, Systems Engineering (SE), preliminary and detailed system architecture designs, prototyping, and system development of Enterprise Services, ground systems, and operations centers, including 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 (i.e., launch), Ground Test (GT) and Flight Test (FT), and operations of planned space capabilities. The scope also includes providing operators and support staff, as required, to support MDA/SS missions.

Page | 3

4. SERVICE SUMMARY ITEMS

In Accordance With (IAW) HQ079617D0001, Integrated Research & Development for Enterprise Solutions (IRES) Contract, Attachment J-06, IRES Performance Evaluation and Incentive Plan, Service Summary Items (SSIs) #1–4 are common (i.e., required) on all TOs and will be assessed at the contract level (i.e., all TOs will receive the same rating—one fail all fail model) and account for 25 percent of the overall SSI rating.

SSIs #5–8 identified below represent the specific TO SSIs deemed essential to successful execution of the TO and account for 75 percent of the overall SSI rating.

Name MDSOC, SpOCC, and Test and Integration Lab (TIL) Availability

(Weight: 25% of overall SSI score)

Identifier SSI #5

Definition The MDSOC, the SpOCC, and the TIL are fully mission capable. Scope is limited to the items under the MDSEA baseline and operationally relevant quantities (e.g., Research and Development Enterprise Collaboration Services [RECS] equipment and MDA/IC equipment are excluded).

Measurable Concept Hours lost over the evaluation period (i.e., a six-month cycle)

Questions Addressed Were missions impacted by MDSOC, SpOCC, and TIL availability?

Baseline Measure Number of hours the MDSOC, the SpOCC, and the TIL were not fully mission capable (i.e., the percentage of actual uptime relative to the total numbers of planned uptime)

Hours Not Fully Mission Capable Score

≤ 8 hours 100

≤ 16 hours 90

≤ 24 hours 80

≤ 32 hours 70

≤ 40 hours 60

≤ 48 hours 50

≤ 56 hours 40

≤ 64 hours 30

≤ 72 hours 20

>72 hours 0

MDSOC Availability Score Based on Above:

Page | 4

SSI Definition

Name MDSEA Performance Management

(Weight: 30% of overall SSI score)

Identifier SSI #6

Definition

MDSEA availability, capacity, updates, Configuration Item (CI) maintenance, incident response, and service levels.

Scope is limited to only TO 4100 baselined systems/components required to be sustained in 10.2 through 10.5, and does not include RECS, MDA/IC equipment, or any Critical Items (CI) that are GFE or any capabilities owned and sustained by Parsons.

Critical time hours are defined as hours the contractor is contractually required to be operating/sustaining these systems at the MDIOC in direct support of an event or operations (as required in 10.2 through 10.5 or an activated PPWP). Critical time hours are the only hours assessed against the availability and MTTR requirements identified below. Critical time hours do not include any hours the contractor is not required to be at the MDIOC, the time from the Government determination to recall on-call personnel to the recalled personnel’s arrival and subsequent confirmation and determination of an incident, or planned down time. The contractor and the Government will jointly agree and document in the monthly TO Status Report (TOSR) if the incident caused a degradation or failure of the event or operations that the contractor was required to support, and the number of hours if it did.

Measurable Concept Monthly performance averaged for scored months

Questions Addressed Was the MDSEA available to support MDA/SS needs?

Baseline Measure Based on performance management Key Performance Indicators (KPIs)

MDSEA Performance Management

KPIs in “MDSEA Availability”

Description Objective Scoring Values

Relative Weight

Raw Score

Weighted Score

Availability (excluding planned downtime)

Percentage of actual uptime (in hours) of service relative to the total numbers of planned uptime (in hours)

>99%

10 for meeting 99%;

decrement score by 1 for each % below

20%

% of unplanned outage/unavailability due to changes

Percentage of unplanned outage (unavailability) due to the implementation of changes into the infrastructure

<3%

10 for meeting <3%;

decrement score by 1 for each % above

10%

Page | 5

Critical-time outage

Total outage from critical-time failures in MDSEA services. Critical time is the time that a service must be available (e.g., for an operation or test systems inherent availability, a tasked 12-hour period)

<1% outage of critical assets

10 for meeting <1%;

decrement score by 1 for each % above

15%

KPIs in “MDSEA Capacity”

Description Objective

Capacity reserves

Capacity management reports and recommendations are produced within

5 business days when a MDSEA IT resource (i.e., CI) is greater than or equal to 75% utilized and forecasted demand will require planned capital investment

<5 days

10 for meeting <5 days;

decrement score by 1 for each day above 5 days

5%

KPIs in “MDSEA Updates”

Description Objective

% of changes first time right

The percentage of changes that reached their goal in one deployment

>98%

10 for meeting 98%;

decrement score by 1 for each % below

5%

KPIs in “MDSEA CI Maintenance”

Description Objective

% of CIs under maintenance contract

This KPI monitors the number of deployed CIs that are within their warranty or are related to a valid maintenance contract, relative to the total number of deployed CIs

>98%

10 for meeting 98%;

decrement score by 1 for each % below

5%

Page | 6

KPIs in “MDSEA Incident

Response” Description Objective

MTTR–RDT&E

environment (critical priority)

Average time (in hours or days) between the occurrence of an incident and its resolution

Loss of a critical site, service, application, or CI that has catastrophic widespread impact to end users or a mission-critical impact to designated test, exercise, or MDS operations activities

<24 business hours after issue identification

(MTTR start time begins based on date/time of incident;

duty hours: initial indication time;

non-duty hours: second hour of the next duty day)

15 for meeting <24 hours;

decrement score by 1 for each 2-hour increment above 24 hours

15%

MTTR (high priority)

Average time (in hours or days) between the occurrence of an

Loss or degradation of a critical site, service, application, or CI that has significant impact to end users or a mission-critical impact to designated test, exercise, or MDS operations activity

<48 business hours after issue identification

(MTTR start time begins based on date/time of incident;

duty hours: initial indication time;

non-duty hours: second h our of the next duty day)

10 for meeting <48 hours;

decrement score by 1 for each day above 48 hours

10%

MTTR (medium priority)

Average time (in hours or days) between the occurrence of an

Loss, degradation, or Hazardous

Condition (HAZCON) of a site, service, application, or CI that affects administrative or

MDS/RDT&E

mission support activities

<72 business hours after issue identification

(MTTR start time begins based on date/time of incident;

duty hours: initial indication time;

non-duty hours: second hour of the next duty day)

10 for meeting <72 hours;

decrement score by 1 for each day above 72 hours

Page | 7

MTTR (low priority)

Average time (in hours or days) between the occurrence of an

An incident not meeting the criteria of Critical, High, or

Medium is categorized as

Low.

<5 business hours after issue identification (MTTR start time begins based on date/time of incident;

duty hours: initial indication time;

non-duty hours: second hour of the next duty day)

10 for meeting <5 days;

decrement score by 1 for each day above 5 days

5%

Old incident backlog

Number of open incidents older than

28 days (or any other given time frame) relative to all open incidents.

<10%

10 for meeting <10%;

decrement score by 1 for each % above

Totals:

100%

MDSEA Performance Management Score = 10 x (Sum of weighted scores): 0.00

SSI Definition

Project Success

(Weight: 10% of overall SSI score)

Identifier SSI #7

Definition Projects are completed meeting all requirements (i.e., technical, cost, and schedule)

Measurable Concept Percentage of requirements met and on schedule during evaluation period (i.e., a six-month cycle)

Questions Addressed Requirements met and on schedule per project

Baseline Measure

Percentage of requirements met and on schedule during evaluation period.

Requirement and schedule milestones will be set per project. Enter the % requirements met on completion. The schedule score is calculated by subtracting days late from 100 (e.g., 100 - 5 days late = 95%).

Weighting: 50% 50%

% Requirements Met Schedule Score

Project 1

Project 2

Project 3

Project 4

Project 5

Project 6

Averages:

Project Success Score:

Page | 8

Management rating

(Weight: 10% of overall SSI score)

Identifier SSI #8

Definition Expectations for management review are met based on the QASP monthly performance report. The contractor must provide justification for recommended 5's, and the customer must provide justification for below 3.

Measurable Concept 100% review of requirements under QASP guidelines for management/business relations, cyber, and financial

Questions Addressed How well did the contractor achieve management/business relations, financial management, and cyber compliance?

Baseline Measure QPI score from below

QPI Ratings

Six-month review results in an average of 0–2 across all performance metrics.

Six-month review results in an average of 2–3 across all performance metrics.

Six-month review results in an average of 3–4 across all performance metrics.

Six-month review results in an average of 4–4.5 across all performance metrics.

Six month review results in an average of 4.5 and above across all performance metrics.

QPI Score = 0 QPI Score =

QPI Score =

QPI Score = 75 QPI Score = 100

Enter Monthly Scores

Management Score:

Month Score Comments

Month 1

Month 2

Month 3

Month 4

Month 5

Month 6

Average:

Individual SSI components listed above are merged based on the relative weighting to give an overall SSI score:

Overall SSI Score

Component Score Relative Weight

SSI Points

SSIs #1–4—Composite Score 25.00% 0.00

SSI #5—MDSOC Availability Score 25.00% 0.00

Page | 9

Overall SSI Score

Component Score Relative Weight

SSI Points

SSI #6—MDSEA Performance Management Score

30.00% 0.00

SSI #7—Project Success Score 10.00% 0.00

SSI #8—Management Score 10.00% 0.00

Overall SSI Score: 100.00% 0.00

5. CONTRACT DATA REQUIREMENTS LIST

The point of delivery for all Contract Data Requirements List (CDRL) products is the MDA Electronic Content and Records Tool (ECaRT) system. The contractor shall deliver all such products by saving and profiling them in ECaRT, with the appropriate notification of delivery letter transmitted electronically to the Government’s Data Management Office (DMO). Refer to Attachment 1—Capability Development for specific CDRL delivery instructions.

5.1 Contract Data Requirements List Identification

The contractor shall be evaluated IAW SSIs #3 and #4, which are common (i.e., required) on all TOs and will be assessed at the contract level.

5.2 CDRLs and Data Item Descriptions

PWS

Task

CDRL

Number

DID Title CDRL Description

10.1.2.2 C001 DI-

MGMT-

81861/T

23F4100 Integrated Program Management Report (IPMR) - Full EVM

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 C002 DI-MISC-

80508B/T

23F4100: Task Order Status Report, [month ending]

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

10.1.2.2., 10.2.2, 10.2.5

C003 DI-MISC-

80508B/T

23F4100: Space Planning Layout Documentation

Notional facility layouts to support the MDSOC and all supporting activities. Identification of ergonomic efficiencies, synergy between mission areas, physical security separation, and the consolidation of IT computing hardware in Quad 2300.

10.2.9 C004 DI-AVCS-

80700A

Interface Exchange Service (IES) Spiral Code Delivery

IES spiral code delivery

10.2.9 C005 DI-IPSC-

81443A

IES User's Manual

IES user’s manual

Page | 10

PWS

Task

CDRL

Number

DID Title CDRL Description

10.2.3 C007 DI-MISC-

80711A

Charge- Back/Show-Back Metrics Report

Charge-back show-back metrics report

10.2.4 C008 DI-MISC-

80711A

Board Support and Configuration Management Reporting

Board support and CM reporting

10.4.1 C009 DI-MISC-

80711A

MDSEA

Operations Procedures for

SKA

MDSEA operations procedures for SKA

10.5.1 C010 DI-MISC-

80711A

MDSEA

Operations Procedures for

MEGS

MDSEA operations procedures for MEGS

10.4.4, 10.5.4

C011 DI-MISC-

80711A

Satellite Operations Status Report

Satellite operations status report (monthly)

10.4.2, 10.5.2

C012 DI-MISC-

80711A

Satellite Crew Certifications Completed

Satellite operations crew certification process

10.4.1, 10.5.1

C013 DI-MISC-

80711A

Program Protection Implementation Plan (PPIP)

PPIP

10.2.9 C014 DI-IPSC-

82249A

SKA Software Assurance Evaluation Report

SKA software assurance evaluation report

10.2.9 C015 DI-IPSC-

82250A

SKA Software Attack Surface Analysis Report

(SASAR)

SKA SASAR

10.2.9 C016 DI-IPSC-

82252A

SKA Vulnerability Assessment Report

SKA vulnerability assessment report

10.2.9 C017 DI-IPSC-

82251A

SKA Software Threat Assessment Report (STAR)

SKA STAR

10.2.9 C018 DI-IPSC-

82249A

HBTSS Software Assurance Evaluation Report

HBTSS software assurance evaluation report

10.2.9 C019 DI-IPSC-

82250A

HBTSS Software Attack Surface Analysis Report

(SASAR)

HBTSS SASAR

10.2.9 C020 DI-IPSC-

82252A

HBTSS

Vulnerability Assessment Report

HBTSS vulnerability assessment report

Page | 11

PWS

Task

CDRL

Number

DID Title CDRL Description

10.2.9 C021 DI-IPSC-

82251A

HBTSS Software Threat Assessment Report (STAR)

HBTSS STAR

Note: If a calendar day ends on a weekend or a holiday, the document shall be delivered the next business day.

5.3 CDRL Tailoring

The Department of Defense (DD) Form 1423, Contract Data Requirements List, associated with each CDRL is contained in the following attachment.

Adobe Acrobat

Document

6. MILESTONES

Contract Award: 9 November 2022

PWS Task Activity MAC Date

IBR 3 January 2023

Cost reports Monthly

Customer program management review

Quarterly

TOSR Monthly

10.5.5.1 Support Government

system integration testing of MEGS

Initial integration testing capability (i.e., dev and test strings)

Dev string: NLT start of Enterprise Test Readiness Review for HBTSS

Test string: Upon Government approval of Zone A declaration for the test string (estimated February 2023)

10.5.5.1 HBTSS MDSEA

communications implementation and sustainment

Provide initial support for MEGS integration

30 days after final FSC connection ATC has been approved

7. GOVERNMENT PROPERTY

In addition to any Government Property (GP) associated with paragraph 6.0 of the Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO), the following GP is applicable to this TO:

file:///C:/Users/cirasundas/Documents/4100/22F4100/RFP/Negotiations/R1.2%20Resubmission/22F4100-Exhibit-C_(Base)%2020221011%20with%20C006%20changed%20to%20Reserved.pdf

Page | 12

Equipment/Information

Office of Primary

Responsibility

(OPR)

Needed For Need By Date

Latest MDSC core configuration-managed documentation

MDA/SS Implementation Already provided

CND Services IP addresses and domain names

MDA/IC Implementation Already provided

APL-developed SKA application executables with configuration instructions and all available documentation. Will also take Virtual Machines (VMs)

SKA Program Office (PO)

Implementation Already provided

APL application installation and test support SKA PO Implementation Already provided

IES VM images, application executables, and installation instructions

MDA/SS Implementation Already provided

SWDC application installation and test support

MDA/SS Implementation Already provided

Capability to reset the root passwords on the VM images

MDA/SS Implementation Already provided

APL and HI test string connectivity test support

SKA PO Implementation Already provided

CDS team test string support for CDS installation and checkout

MDA/SS Implementation Already provided

ESL support to SKA test string connectivity and testing

MDA/SS Implementation Already provided

X-Lab support to SKA test string connectivity and testing

MDA/SS Implementation Already provided

APL dev string connectivity test support SKA PO Implementation Already provided

CDS team dev string support for CDS installation and checkout

MDA/SS Implementation Already provided

Facilities space for MDSEA physical hardware

MDA/SS Implementation Already provided

Rack space for 4 FTs Experiment Other (FEXs) and 2 patch panels in Quad 2308

MDA/SS Implementation Already provided

Three SKA GCEs SKA PO Implementation Already provided

MDA/IC master timing service MDA/IC Implementation Already provided

MDA backbone necessary to communicate with MDA/IC-provided services and required MDIOC internal/external systems

MDA/IC Implementation Already provided

MDA enterprise HBSS ePolicy Orchestrator (ePO) service

MDA/IC Implementation Already provided

MDA/IC PKI certificate management service MDA/IC Implementation Already provided

MDA/IC enterprise ACAS service MDA/IC Implementation Already provided

MDA/IC enterprise Linux system patching service

MDA/IC Implementation Already provided

MDA/IC ArcSight service MDA/IC Implementation Already provided

MDA/IC enterprise Windows system patching service

MDA/IC Implementation Already provided

Page | 13

Equipment/Information

Office of Primary

Responsibility

(OPR)

Needed For Need By Date

Four SKA CDS SKA PO Implementation Already provided

Software licenses for core COTS applications to be migrated to the MDSEA

MDA/SS Core Migration Already provided

One SKA CDS SKA PO Implementation Already provided

SKA operator training requirements (Microsoft Excel)

SKA Training With each updated software delivery

CDSs HBTSS PO Implementation Integration

Crypto devices HBTSS PO Implementation Integration

Navy Environmental Prediction System Utilizing a Nonhydrostatic Engine

(NEPTUNE)

HBTSS PO Implementation Integration

Orbit/Covariance Estimation and Analysis

(OCEAN)

HBTSS PO Implementation Integration

Ground Resource Manager (GRM) HBTSS PO Implementation Integration

Virtual Mission Operations Center (VMOC) HBTSS PO Implementation Integration

Goddard Mission Services Evolution Center

(GMSEC)

HBTSS PO Implementation Integration

7.1 Additional Government-Furnished Property

None.

7.2 Additional Government-Furnished Information

The following Government-Furnished Information (GFI) is applicable to this TO:

All requisite tenant operator training materials, manuals, Standard Operating Procedures (SOPs), and additional documents to support the activation of tenant operations from the MDIOC

7.3 Contractor-Acquired Property

All Contractor-Acquired Property (CAP) shall be managed under the terms and conditions associated with HQ085722F8900, Supply Chain Product Support and Government Property Management Performance Work Statement.

8. SPECIAL REQUIREMENTS

In addition to the special requirements in paragraph 7.0 of the Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO), the following is applicable to this TO:

This TO shall be executed IAW MDA security classification guidance.

WARNING: International Traffic in Arms Regulation (ITAR): MDS technology is restricted under ITAR, which controls the export and import of defense-related material

Page | 14 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 (FOIA).

9. APPLICABLE DOCUMENTS

In addition to the directives and regulations identified in paragraph 8.0 of the Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO), the following documents are applicable to this TO:

Document ID Title Originator Date

DoDI 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks

(TSN)

DoD Chief Information Officer (CIO)

Under Secretary of Defense (USD) for Acquisition, Technology, and

Logistics (AT&L)

Incorporate change 2; 27 July 2017

NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations

NIST April 2013;

including updates as of 22 January

CNSS Instruction

(CNSSI) 1253

Security Categorization and Control Section for National Security Systems CNSS 27 March

DoDI 8510.01 Risk Management Framework DoD 29 October

DISA Memo ENCLAVE Test and Development Security Technical Implementation Guide (STIG)

DISA 9 January

MDA-STD-001A MDA MDS High Altitude Exoatmospheric Nuclear Survivability (HAENS) Standard

MDA 24 October

Strategic Instruction (SI) 538-02

Operations, Planning, and Command and Control, Ballistic Missile Defense Systems (BMDS) Physical Security Program

U.S. Strategic Command

(USSTRATCOM)

Current version

DA-18F4100-

01627

MDSEA Employment Concept MDA/SS 31 January

MDA/DX Memo Interim Cybersecurity Guidance for RDT&E Enclaves and Systems

MDA/DX 9 January

MDA-211015-

DPBR

Spacebased Kill Assessment Program Protection Plan (PPP)

MDA/DE 1 February

None SKA Security Classification Memorandum MDA/D Current Version

Version 1.0 Hypersonic and Ballistic Tracking Space Sensor (HBTSS) Program Protection Plan

(PPP)

MDA/SS TBD

Classified Missile Defense System (MDS) Security Classification Guide (SCG)

MDA/D 26 May 2017

Page | 15

Document ID Title Originator Date

Classified Consolidated National System for Geospatial Intelligence (NGA) (CONGA)

SCG

Naval Security Group (NSG)

3 April 2018

None Spacebased Kill Assessment (SKA) Security Classification Guide (SCG)

MDA/D

17 February

None Hypersonic and Ballistic Tracking Space Sensor (HBTSS) Security Classification Guide

MDA/SS 4 April 2019

MDA Manual 3500.01-M

BMDS Change Management Process MDA/DP 14 November

MDA Directive 5000.17

Missile Defense System Operational Capacity Baseline Procedures

MDA/DE 20 February

MDA Directive 3000.10

BMDS Flight Test Concept of Operations MDA/DT 20 June 2019

MDA Policy Memo

MDA Software Assurance Requirements MDA/D 22 September

MDA Instruction

3000.07-INS

BMDS Ground Test Concept of Operations MDA/DT 17 October

MDA Manual 3000.02-M

BMDS Asset Management (BAM) MDA/DDW 12 December

Classified Spacebased Kill Assessment Element Specifications

MDA/SS 4 November

MDA/SS Directive Memo 001-2021

Missile Defense Integration and Operations Center Engineering Review Board

MDA/SS Director 6 July 2021

MDSC-003-Rev B Engineering Review Board (ERB) Charter MDA/SS Director 13 April 2015

MDA Manual 3110.01-M

Missile Defense System Operational Readiness Reporting

MDA/DW 14 July 2020

Technical Direction Letter (TDL) 18F8002-12

Task Change Request (TCR) Instruction DoD Current Version

10. STATEMENT OF OBJECTIVES AND OUTCOMES

The contractor shall meet all requirements/tasks identified in Section 10.

10.1 Task Order Administration

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

Task Order Management

This PWS element represents the stakeholder technical integration management and IRES integration management activities required to support the management of

Page | 16 requirements of the overall TO, including all reporting, briefings, awards, modifications, SSIs, etc.

Objective #1: The contractor shall manage TO execution, resources, and information to conduct, deliver, and communicate TO requirements delivery.

Outcomes:

Manage the cost, schedule, risk, and technical performance IAW the PWS.

Provide status and insight on performance, including the metrics outlined in the Quality Assurance Surveillance Plan (QASP).

Manage activities IAW the processes defined in the IRES Program Management Plan (TO 8002, CDRL C008).

Ensure all requirements are identified, managed, validated, and verified IAW the IRES Program Systems Engineering Master Plan (SEMP) (TO 8002, CDRL C005).

Ensure a common Enterprise Architecture (EA) vision is implemented to support MDA “to-be” architectures, including the identification of gaps and lessons learned.

Manage the TO workforce efficiently, mitigating workforce surge and draw-down impacts, analyzing workforce trends, and forecasting workforce needs and hiring to those requirements.

Document, revise, improve, and train to the processes required by the TO.

Report status (e.g., technical, cost, schedule). Status includes cost and schedule performance by Work Breakdown Structure (WBS) and IRES organization structure;

significant accomplishments; customer concerns or issues; TO risks and mitigation status; and performance against the IRES contract, SE and Program Integration (SEPI), and TO SSIs. Identify, track, and share performance trends with the Contracting Officer’s Representative (COR), the Contracting Officer’s Technical Representative (COTR), and applicable Government stakeholders.

Provide overall program protection and security classification management IAW the DD Form 254, Department of Defense Contract Security Classification Specification, and Missile Defense Space Center (MDSC) security procedures. Maintain all data security requirements and data release limitations as a best effort.

Objective: Enterprise Task Order Support

This PWS element scope represents the processes and toolsets of contract-wide enterprise support required for delivery of the IRES contract. This support provides the back office functions that enable the TO’s work and resources.

10.1.2.1 Enterprise Management

Objective #1: The contractor shall provide the resources and data to enable enterprise management of this TO for contracting, Human Resources (HR), business/finance, and Jacobs Enterprise Management System (JEMS)/Cobra integration.

Page | 17

Outcomes:

Contracting office provides subcontracting and limitation of funds oversight, and processes TO modifications and awards IAW contractual requirements.

Provide on-demand access to program data for MDA customers and stakeholders.

Manage export control requirements to comply with DoD and MDA requirements, including 22 Code of Federal Regulations (CFR) 120-130, International Traffic in Arms Regulations, and technical assistance agreement processes, as required.

Provide HR staff and functions to support the need for recruiting, hiring, and training a qualified workforce.

Provide business office functions to enable the execution of payroll, timekeeping, accounts receivable/payable, and travel services.

Administer small business and teammate agreements to achieve MDA and IRES small business goals.

Manage the workforce in a way that will mitigate workforce surge and draw-down impacts, analyze workforce trends, and forecast workforce needs to ensure the required staffing is available to meet the requirements of the TO.

Maintain a trained and qualified workforce that is able to perform the functions necessary to operate, support, and sustain MDIOC facilities and systems required under this TO.

Develop and document processes that will enable the requirements of the TO to be met.

Deliver quality and innovative work IAW the policy and direction provided in the IRES Information Management System (IIMS) set of processes and tools.

Objective #2: The contractor administers an IRES TO portfolio delivery system that delivers financial, Earned Value (EV), and SSI performance across TOs. The contractor shall utilize TO dashboards and automated workflows in order to manage the portfolio.

Outcomes:

Utilize an IIMS portal to host and communicate TO EV, performance data, metrics, and trends, and continuously evaluate and improve performance through the use of objective performance measures.

Objective #3: The contractor shall provide information security, physical security, export control, and cybersecurity training and processes IAW federal, DoD, and agency requirements to safeguard the conduct of the MDA mission through the IRES contract.

Outcomes:

Protect MDA-identified Critical Program Information (CPI) and critical technology to the standards required in DoD Instruction (DoDI) 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E).

Page | 18

Protect CUI from unauthorized access, disclosure, incident, or compromise.

Maintain system authorization for contractor-managed systems IAW DoDI 8510.01, Risk Management Framework.

Integrate cybersecurity requirements and considerations into SE, design, and risk management processes.

Operate contractor-managed systems IAW cybersecurity requirements.

Provide security administration IAW applicable DoD, MDA, and local security directives, policies, procedures, and instructions for physical security and for the safeguarding of BMDS-controlled and classified information, including proper document marking, classification, storage, accountability, transmittal, and destruction.

Manage and report the status of personnel requiring privileged access and the required DoD-approved Information Assurance (IA) certification 8570 for the operating system(s) and/or security-related tools/devices they support or operate.

10.1.2.2 Performance Management

Objective #1: The contractor shall perform program control to provide an EV Management (EVM) System (EVMS); associated Control Account (CA) management and scheduling common tools, training, standards, and resources; and contract-wide portfolio and project management common tools, training, standards, and resources.

Outcomes:

Develop and manage an EVMS that provides required Integrated Program Management Report (IPMR) formats and Baseline Review (BR)/Integrated BR (IBR) artifacts.

Perform an IBR (or BR) within 90 days or as otherwise specified in the TO.

Perform financial management activities in a way that ensures EVM reporting accurately reflects the current state of financial performance and status.

Structure the TO Integrated Master Schedule (IMS) for integration into the contractor’s IRES Integrated Schedule (IIS).

Manage portfolio/project practices in a way that enables technical consistency and cost effectiveness while providing an adaptable framework for planning, managing, and completing projects for a broad range of tasks and missions.

Milestone: Integrated Baseline Review

CDRL C001—Integrated Program Management Report

CDRL C002—Task Order Status Report

CDRL C003— Space Planning Layout Documentation

Objective #2: The contractor shall perform Mission Assurance (MA), Configuration Management (CM), Risk Management, and QA and Safety that promote and enforce

Page | 19 safe and sustainable work practices to prevent personnel injury, damage to property, or harm to the environment.

Outcomes:

Manage risks IAW the IRES Cybersecurity Risk Management Plan (TO 8002, CDRL C016).

Manage the quality of TO activities IAW the MDIOC Facility Quality Assurance Plan

(TO 8002, CDRL C043).

Manage asset configurations IAW the MDIOC Facility Configuration Management Plan (TO 8002, CDRL C042).

Perform activities IAW the MDIOC Facility Mishap Prevention and Safety Plan (TO 8002, CDRL C036) to prevent personnel injury and property damage.

Perform activities IAW the MDIOC Facility Environmental Program Plan (TO 8002, CDRL C037) to prevent harm to the environment and maximize sustainable practices.

Objective #3: The contractor shall produce and deliver program data to ensure the products and services provided under this TO utilize established integrated processes and practices that are standardized across the IRES contract.

Outcomes:

Integrate systems integration requirements, capability gaps, and a common architecture vision across the enterprise.

Manage critical assets—including conflict forecasting and de-confliction—across the enterprise.

Track and deliver CDRLs on time and with accurate information.

Solicit and track customer satisfaction with the services and products delivered.

Collect and share lessons learned, best practices, and accomplishments with the COR, the COTR, other Government stakeholders, and the IRES workforce.

Provide systems integration and a common MDIOC system vision and oversight that are integrated enterprise-wide IAW the IRES Program Management Plan (TO 8002, CDRL C008).

Provide AS9100-compliant core IRES processes and tailored processes.

Objective #4: The contractor shall submit compliant TO CDRLs and reports, and monitor status of all TOs’ CDRL delivery performance IAW CDRL and milestone requirements. The contractor shall document approved processes as part of an IRES-wide management system in compliance with the IRES Program Management Plan (TO

8002, CDRL C008).

Outcomes:

Track upcoming CDRL deliveries for all TOs, requirements for technical writing support, and schedules to meet on-time deliveries in support of IRES SSI #4.

Page | 20

Coordinate technical writing, process engineering, stakeholder review, and posting of approved MDA and IRES process documents in the IRES Process Asset Library

(PAL).

Provide contractual deliverables within the agreed-to schedule, in the correct formats, and to a high level of quality. Post all deliverables to ECaRT and/or the

IRES PAL.

10.1.2.3 Functional Organizational Support

Note: This area is for functional organization support. Not all TOs will require this support.

Objective #1: The contractor shall provide a functional management oversight structure to lead, manage, and assign resources within their organization.

Outcomes:

Perform leadership, management, and administrative functions. Ensure personnel are trained and equipped to accomplish objectives.

The Functional Director leads and manages the department to meet requirements.

The Functional Director delivers products and services that include the correct people, processes, and tools to meet mission requirements.

The Functional Director tactically allocates and strategically forecasts resources to ensure the sustainment, renewal, and growth of the technical expertise within the department that meets current and future requirements.

Each functional department provides training, certifications, and career growth of employees.

The Functional Director mentors and oversees the execution of event engineering, asset operations and sustainment, systems integration, and analysis to ensure technical success.

Objective #2: The contractor shall provide functional administrative and management support to communicate and deliver enterprise integration.

Outcomes:

Develop and manage coordination, collaboration, communication, integration activities, and processes between IRES senior managers and Government leaders to support and ensure accomplishment of objectives.

Develop, standardize, and deploy through processes for event engineering, asset operations and sustainment, systems integration, and analysis.

Coordinate, integrate, and deliver innovations to the TO mission areas—and IRES as a whole—to optimize efficiencies and mission effectiveness.

10.1.2.4 Procurement Services Support

Objective #1: The contractor shall provide accurate and timely procurement service functions that meet the needs of the TO.

Page | 21

Outcomes:

Maintain a procurement capability and system that support the procurement needs and provides status of procurements to stakeholders.

Purchase supplies and equipment IAW the IRES Supply Chain Risk Management (SCRM) Plan (TO 8002, CDRL C044), including an authorized suppliers list for critical systems.

Task Order Award and Modification

Objective #1: The contractor shall provide the resources and data to provide timely and accurate proposals to Government requirements for proposal and other contract modification actions, including providing support to the Integrated Product Team (IPT) and proposal development for the follow-on TO requested by the Contracting Officer (KO) or the Contract Specialist.

10.2 MDA/SS Functional Support (SysAdmin, Engineering, Risk ID, and Administration)

Material and Supply Chain Management

The contractor shall plan and execute supply chain and material management operations.

Configuration Management

The contractor shall maintain configuration control of all software hosted in the MDSEA, including Commercial Off-the-Shelf (COTS) software, contractor Mission Unique Software (MUS), and any other software approved by the Government Engineering Review Board (ERB). The contractor shall perform these actions under Government oversight of all enclaves and facilities identified within this TO IAW the Space Planning Layout Documentation (TO 4100, CDRL C003).

The contractor shall provide a comprehensive CM approach that is flexible enough to accommodate Research, Development, Test, and Evaluation (RDT&E) to provide solid operations support. The contractor shall be evaluated IAW SSIs #3 and #4, which are common (i.e., required) on all TOs and will be assessed at the contract level.

Develop, maintain, and coordinate technical documentation, including MDSEA employment, engineering drawings, and interface control specifications for existing systems that require documentation or as a result of newly developed and/or modified systems. Ensure fully coordinated, redlined change documents are available for the Government user and service technicians at the customer turnover date; formal configuration control documentation and drawings shall be updated and posted. Documentation and drawings projects shall be completed upon request and agreed upon by the COR and the contractor.

MDSEA Service Management

The contractor shall execute a service management framework using standards-based processes (e.g., IT Infrastructure Library [ITIL] version [v]3) that integrate requirements

Page | 22 management, design life cycle, implementation/change/release, and CM across the MDSEA technical architecture. Provide oversight and governance of key processes that ensure continuous improvement in evolving a MDSEA and services organization.

Specific functions include requirements management, service-level reporting, service metrics, governance (i.e., 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 that is meaningful to MDSC leadership, MDA/SS Program Managers (PMs), and MDSEA tenants. The MDSEA service management framework shall support ease of MDSEA service ordering, provisioning, and costing, enabling accurate and timely updates of Service-Level Agreements (SLAs) and charge-back/show-back reporting for each tenant consuming MDSEA and Missile Defense Space Operations Center (MDSOC) services and capabilities.

The contractor shall deliver a quarterly Charge-Back Show-Back Metrics Report (TO 4100, CDRL C007). This CDRL shall identify the consumption rates of MDSEA-managed IT resources by MDSC tenant organization/function, and attribute costs for MDSEA and MDSOC shared infrastructure and desktop/client productivity to the tenant in both a show-back and charge-back methodology based on both basic and enhanced SLAs.

MDA/SS Functional Board Support

Develop design solutions and conduct design reviews (preliminary and final) for Government approval. Participate in required MDSC and MDIOC review boards, such as the following:

ERB/MDSC Integrated Configuration Control Board (CCB) (MICCB)/MDSC Risk Review Board (RRB) (MRRB)/Work Screening Team (WST)

Mission Readiness Working Group (MRWG)

Operations Working Group (OWG)

SE and Integration Contractor (SEIC)

Incremental Engineering Technical Review (IETR)

Maintain and update applicable charters for these boards.

Provide a holistic approach to SE and Integration (SEI) for the MDSC. Submission of a report is required monthly IAW the Board Support and Configuration Management Reporting (TO 4100, CDRL C008). The contractor shall be evaluated IAW SSIs #3 and #4, which are common (i.e., required) on all TOs and will be assessed at the contract level. The contractor will report on efforts maintaining the MDSEA environment, the MDSEA SOC, the ERB/MICCB, MRRB support efforts, and MDSC equipment CM. The contractor shall execute IAW—and performance will be evaluated using—SSIs #3 and #4, which are common (i.e., required) on all TOs and will be assessed at the contract level, as well as SSI #6.

Page | 23

Cyber Support

The contractor shall provide cybersecurity subject matter expertise and Situational Awareness (SA), and support the MDA/SS Information Systems Security Manager (ISSM) in the following activities:

Support of authorization activities to ensure existing and future assets are authorized IAW Office of Management and Budget (OMB), National Institute of Standards and Technology (NIST), Committee of National Security Systems (CNSS), DoD, MDA, MDA/SS, and other applicable directives within required authorization timelines, including, but not limited to, Authorizations to Connect (ATCs), Authorizations to Operate (ATO), and Interim Authorization to Test (IATT) activities.

Timely support of compliance activities on all MDSC system components, including, but not limited to, the following:

Providing artifacts and other relevant documentation to remediate or update Enterprise Mission Assurance Support Service (eMASS) Plans of Action and Milestones (POA&Ms) NLT 30 days prior to expiration dates and Cyber Tasking Order (CTO) POA&Ms NLT 7 days prior to expiration dates

Supporting Tier III Local Command Center (LCC)/Defensive Cybersecurity Operations (DCO) activities, system patching, Security Technical Implementation Guide (STIG) patching, Assured Compliance Assessment Solution (ACAS), Endpoint Security Solution (ESS), or other security scans, including Host-Based Security System (HBSS) implementation

Responding to IA Vulnerability Alerts (IAVAs), CTOs, and system security audits.

Support is required to be delivered to the MDA/SS Cybersecurity team in time for their assessment prior to MDA/IC-directed deadlines.

Support implementation of the DoD Cybersecurity Discipline Implementation Plan’s four Lines of Effort (LOEs), as follows:

Strong Authentication

Device Hardening

Reduce Attack Surface

Alignment to Tier II Cybersecurity/Computer Network Defense (CND) Service Provider

Provide security engineering design and documentation support for MDSC projects and programs IAW the Space Planning Layout Documentation (TO 4100, CDRL C003).

Ensure system security life-cycle activities are included in program protection plans.

Develop and deliver artifacts as products of compliance activities.

Provide initial, updated, and validation of system Ports, Protocols, and Services (PPS) management information.

Page | 24

Provide support to external inspections (e.g., Defense Information Systems Agency [DISA] Command Cyber Readiness Inspections [CCRIs], MDA/ICD Controls Validation Tests [CVTs]).

Maintain appropriate cybersecurity certifications IAW DoD 8570.01-M, Information Assurance Workforce Improvement Program, and DoD Directive (DoDD) 8140.01, Cybersecurity Workforce Management, and compliance with the MDA Cybersecurity Workforce Management program.

Maintain logs associated with the implementation of documented processes, conduct periodic audits to ensure the processes are being done correctly, and provide access to or copies of those logs and audits as requested.

System Engineering and Integration

The contractor shall provide standardized SE associated with all activities under this TO. The contractor shall implement sound SE Integration and Test (SEIT) practices and follow industry best practices. The contractor shall follow the IRES Program Systems Engineering Management Plan (SEMP) (TO 8002, CDRL C005) to manage requirements development, requirements management, technical solutions, product integration, and Verification and Validation (V&V), including an appropriate set of documentation and reviews required for development and support of the full…