Attch2_Exh_E_22F5900 PWS.pdf

Missile Defense Agency

Integrated Research & Development for Enterprise Solutions (IRES)

1 April 2022

PERFORMANCE WORK STATEMENT

Contract Number:

HQ079617D0001

Task Order Title:

C2BMC INFRASTRUCTURE, ENGINEERING AND EVENT SERVICES

Task Order Number:

HQ085722F5900

Period of Performance:

April 1, 2022 to March 31, 2024

Task Order Type: CPIF

Page | 2

Task Order Revision History

Rev Description of Changes Date

0 Contract Award Basic 1 Apr 2022

Page | 3

Table of Contents

1.0 Purpose

2.0 Background

3.0 Scope

3.1 C2BMC –Test Environment (CTB -TE)

3.2 C2BMC –Test Articles (CTB -TA)

3.3 Joint Early Warning Lab (JEWL)

3.4 International Point of Presence (IPOP)

3.5 Core IT and Personnel Workspace

3.6 OPIR Consolidated Laboratory (OCL)

3.7 Virtualized Testing Environment for C2BMC (VTEC)

3.8 Local Control Center (LCC) Activities

3.9 BNOSC

4.0 Service Summary Items

5.0 Contract Data Requirements List (CDRL)

5.1 Contract Data Requirements List (CDRL) Identification

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

6.0 Milestones

7.0 Property

7.1 Government Property (GP)

7.2 Government Furnished Property (GFP)

7.3 Government Furnished Information (GFI)

7.4 Contractor Acquired Property (CAP)

8.0 Special Requirements

9.0 Applicable Documents

Page | 4

10.0 Statement of Objectives and Outcomes

10.1 Task Order Administration

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

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

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

10.2 Workload and Resource Management

10.2.1 Objective - Requirements Facilitation

10.2.2 Objective - Master Scheduling

10.2.3 Objective - Configuration Management and Asset Control

10.3 Security Management

10.3.1 Objective - Cybersecurity Compliance

10.3.2 Objective - Security Operations

10.3.3 Objective – Local Control Center (LCC) Activities

10.3.4 Objective – CTB-TA and VTEC

10.3.5 Objective – CTB-TE

10.3.6 Objective – JEWL and IPOP

10.4 CTB Test Environment

10.4.1 Objective - Core Routing and Switching (Red/Black)

10.4.2 Objective - Modeling and Simulation (M&S)

10.4.3 Objective - Analysis Tools

10.4.4 Objective - Interfaces

10.5 Mission System and Core IT Sustainment

10.5.1 Objective - Mission System Sustainment

10.5.2 Objective - Test Article Hardware/Software Installation

10.5.3 Objective - Core IT and Personnel Workspace Services and Sustainment

10.5.4 Objective - Maintenance Renewal, Sparing, and Tech Refresh

Page | 5

10.6 Test Events Services

10.6.1 Objective – Full Hardware-in-the-Loop (HWIL) Events

10.6.2 Objective - Sprint Hardware-in-the-Loop (HWIL) Events

10.6.3 Objective - System Pre-Mission Test (SPMT) / System Post-Flight Reconstruction (SPFR) - Hardware-in-the-Loop (HWIL) Events

10.6.4 Objective - Flight Test Event

10.6.5 Objective - International Test Event

10.6.6 RESERVED

10.6.7 Objective - Pairwise Test Event

10.7 Projects

10.7.1 Objective - Infrastructure Projects

10.7.2 RESERVED

10.7.3 Objective - Cyber Projects

10.7.4 Objective – Test Environment Projects

10.7.5 Objective - Test Article Projects

10.7.6 Objective - Event Projects

10.7.7 Objective – JEWL Projects

10.7.8 Objective – IPOP Projects

10.7.9 RESERVED

10.8 Operations and Analysis

10.8.1 Objective - Joint Early Warning Analysts

10.8.2 Objective - The Contractor shall maintain MDA IPOP

10.9 BMDS Network Operations Security Center (BNOSC)

10.9.1 Objective - BNOSC Operations and Sustainment

10.9.2 Objective - Events and Engineering Projects

Page | 6

1.0 Purpose

The Missile Defense System (MDS) - Command, Control, Battle Management, and Communications (C2BMC) Infrastructure, Engineering and Event Services task order provides engineering products and services, and mission operation activities for the Missile Defense Agency (MDA), C2BMC Program Office.

Page | 7

2.0 Background

Early in the C2BMC program, the Missile Defense Agency (MDA) established at the Missile Defense Integration and Operations Center (MDIOC) an integration, test, and experimental testbed that allows the Missile Defense National Team (MDNT) contractor and government to test and verify the performance of new versions of the C2BMC and to support fielded systems. The testbed features replicas of the systems that the MDNT designs and the environments in which they operate.

Mission execution includes a wide variety of test activities, advanced concept development, assessments, and evaluations:

• Cycle 1 Test – Installation, Integration and Checkout

• Cycle 2 Element Test – Requirements Verification, using simulation

• Cycle 3 Hardware-in-the-Loop Test – Capability verification using external BMD elements

• Cycle 4 System Test – System level verification using operational systems, sensors and weapons

• Cycle 5 Site Activation Test – System verification at operational sites

• Sustainment Test – Fielding suitability, testing changes to the operational system prior to fielding

• Experiments – Prototype and advanced concept development for future C2BMC capability.

• Theater Missile Warning assessments

• International Interoperability – Interoperability tests conducted with US and allied partner missile defense systems

• Support demonstrations of C2BMC systems to U.S. and allied partner senior leadership

To execute the mission, the following C2BMC Infrastructure Mission Areas have been established:

• C2BMC –Test Environment (CTB -TE) provides interfaces to stimulate the C2BMC Testbed – Test Articles (CTB-TA), simulates missile defense elements, and includes data collection devices, data storage arrays, and analysis tools that form the supporting system to conduct tests.

• C2BMC –Test Articles (CTB -TA) represents the deployed, fielded version of C2BMC and the current test version that the government will deploy. CTB-TA is the system under test.

• C2BMC Spiral 8.2-3 represents current operational baseline

• C2BMC Spiral 8.2-5 constitutes the current system under test

• C2BMC Spiral 8.2-7 constitutes the next generation – system under test

• International Point Of Presence (IPOP) provides the communication hub with connections to

BMD Labs (C2BMC, Aegis, Patriot, SEWS, AN/TPY-2 Radar) for participation in multi-national testing.

• Joint Early Warning Lab (JEWL) performs Theater Missile Warning (TMW) integration;

provides health and status assessments of the Theater Event System (TES).

• Personnel IT and Workspace (PITW) represents IT support and workspace for government, military, FFRDC, Systems Engineering and Technical Services (SETA) contractors, and members of the National Team at the MDIOC.

• System Test and Operations Centers (STOC) are labs that connect to operational C2BMC suites for conducting flight tests and distributed ground tests in addition to Operational Integration and testing, OPS Deployment support, and BNOSC Watchfloor Alternate Support Area.

• C2BMC System Support Center (CSSC) connects to operational, training, and test labs to provide real-world situational awareness, senior leader playbooks, test analysis, etc.

• OPIR Consolidated Laboratory (OCL) are three labs (OCL-1, OCL-2, and TSC) that use simulation and tactical systems to generate early warning messages for HWIL, Distributed Ground Test, and Flight Test events.

Page | 8

• Virtualized Testing Enclave for C2BMC (VTEC) represents an agile, virtualized Mission Suite capability in support of HWIL and Cycle Testing.

• Local Control Center (LCC) Activities describes the collection of administrative and technical support to the MDA/BC Information System Security Manager (ISSM)

• BMDS Network Operation and Security Center (BNOSC) is the single MDA entity, which transcends the individual elements within the MDA for operation, management, defense, command and control of the BMDS communications and applications

Page | 9

3.0 Scope

3.1 C2BMC –Test Environment (CTB -TE)

Plan, design, implement and sustain mission equipment and capabilities, sustain non-mission (unclassified / classified IT, voice communications, printers, etc.) equipment and capabilities, provide IT and engineering services, and operate equipment during mission execution.

3.2 C2BMC –Test Articles (CTB -TA)

Plan, design, implement and sustain mission equipment and capabilities, provide IT and engineering services, and support mission execution.

3.3 Joint Early Warning Lab (JEWL)

Plan, design, implement and sustain mission equipment and capabilities, sustain non-mission equipment and capabilities, provide IT and engineering services, and operate equipment during mission execution.

Perform technical assessments of real world missile events, flight tests, and exercises.

3.4 International Point of Presence (IPOP)

Plan, design, implement and sustain mission equipment and capabilities, sustain non-mission equipment and capabilities, provide IT and engineering services, and operate equipment during mission execution.

3.5 Core IT and Personnel Workspace

Sustain non-mission equipment and capabilities and provide IT and engineering services (Personnel IT and Workspace (PITW).

3.6 OPIR Consolidated Laboratory (OCL)

Plan, design, and implement MDIOC infrastructure and non-mission equipment

3.7 Virtualized Testing Environment for C2BMC (VTEC)

Plan, design, implement, sustain mission equipment, MDIOC infrastructure and non-mission equipment, and support mission execution. Provide hardware, software, infrastructure support and external connectivity via the TE. Sustain cybersecurity compliance and accreditation. Audio/Visual and Video Teleconference Liaison.

Provide liaison between MDA/BCX and Prime Contractor for audio/visual and video teleconferencing.

3.8 Local Control Center (LCC) Activities

Provide technical services to the MDA/BC ISSM including Cyber Documentation, Semi-Annual Reports, EndPoint Security Solutions (ESS), Cyber Tasking Order Management, Cyber System Analysis, and Command Cyber Operational Readiness Inspection (CCORI) oversight.

Page | 10

3.9 BNOSC

For all BNOSC facility areas on Beale Air Force Base (BAFB), Schriever Space Force Base (SSFB) and Cheyenne Mountain Space Force Base (CMSFB), provide IT systems/facility preventive and corrective maintenance activities ensuring BNOSC systems/facility performance and availability. Provide support for daily activities including, network management, project management and engineering design/implementation, Help Desk, and Install/Move/Add/Change (IMAC). Perform training and exercise/event support for all BNOSC and DTS Control Center (DCC) spaces.

Exhibit 1 identifies the BNOSC facility areas, if the area is designated as a critical functional area and the systems supported within the BNOSC facility. Exhibit 2 provides the performance standards for Critical and Non Critical systems.

Exhibit 1: BNOSC Areas and Systems

Systems C2

BM

C

JW

IC

S

IC

E vI Pe r

SV

O

IP

CL

AN

U

LA

N

DR

SN

Building / Room Critical Functional Area

720 / 1102-

01 STOC 1 NC* NC* NC* NC NC*

720 / 1102-

02 STOC 2 NC* NC* NC* NC NC*

720 / 1103- 01 CCC Level 2 NC NC NC NC NC

720 / 1111 Office Floor NC NC NC

720 / 1111- 01 Office NC NC NC

720 / 1111- 02 Office NC NC NC

720 / 1117- 02 Office Floor NC NC NC

720 / 1117- 03 S8.2 Ops*** Yes C C NC C

720 / 1117- 04 CCC Yes C C C C NC C

720 / 1117- 06 Office NC NC NC NC NC

Page | 11

C

JW

IC

S

IC

E vI Pe r

SV

720 / 1117- 07 Office NC NC NC NC

720 / 1117- 08 Office NC NC NC NC

720 / 1117- 09 Office NC NC NC NC

720 / 1117- 10 SUS Yes C C C NC C

720 / 1117- 12 Conference Room*** NC NC NC

720 / 1119 Office Floor NC NC NC NC NC

720 / 1119- 01 Office NC NC NC NC

720 / 1119- 02 Office Floor

NC NC NC NC

720/1119-03 Office Floor NC NC NC

720 / 1107- 01 Conference Room NC NC NC

720 / 1107- 02 CSSC Yes C C C C NC C

720 / 1306- 02/-03/-04 DCC Yes C C NC C

CMAFS/210

2J Ops Space NC* NC*

BAFB/5760-

420 Office NC*

BAFB/5760-

112 User Node NC*

Page | 12

C

JW

IC

S

IC

E vI Pe r

SV

BAFB/5760-

413 Management Node NC*

C Critical

NC Non-Critical

NC* Non-Critical unless utilized for Event Support

Note 1: BNOSC is tasked to provide maintenance support for the infrastructure (including ULAN and CLAN), facilities, and phones in these areas.

*** Liaison between MDA/BCW and the prime Audio Visual and VTC contractor.

Exhibit 2. Performance Standard Summary

Objective Area Applicable

Paragraph(s) Initial Response

Estimated Time to Repair

Situation

Report

Action Completed

BNOSC Operations & Sustainment

Recurring Maintenance As Scheduled N/A N/A As Scheduled

Incident Request

• Critical, Core Hours

10.9.1.2 30 min 1 hour*** 6 hours*** 24 hours***

• Critical, Non-Core Hours

10.9.1.2 2 hours 4 hours*** 6 hours*** 24 hours***

• Non-Critical

10.9.1.2 8 hours 24 hours*** N/A 14 days***

Install/Move/Add/Change (IMAC) Services

10.9.1.2

• Urgent N/A N/A N/A 3 days*

Page | 13

Objective Area Applicable

Paragraph(s) Initial Response

Estimated Time to Repair

Situation

Report

Action Completed

• Routine N/A N/A N/A 14 days*

Documentation/Drawing Updates 10.9.1.3 Redline N/A N/A 30 days

DCC Sustainment

• Critical, Core Hours

10.9.1.2 1 hour 2 hours*** Daily*** 72 hours***

• Critical, Non-Core Hours

10.9.1.2 2 hours 4 hours*** Daily*** 72 hours***

• Non-Critical

10.9.1.2 24 hours 48 hours N/A 14 days

Install/Move/Add/Change (IMAC) Services

10.9.1.2

• Urgent N/A N/A N/A 7 days*

• Routine N/A N/A N/A 30 days*

Documentation/Drawing Updates Redline N/A N/A 60 days

Events & Engineering Projects

IRT Project 10.9.2.2 N/A N/A N/A 90 days

QRT Project 10.9.2.3 N/A N/A N/A 150 days

Documentation/Drawing Updates 10.9.2.2,

10.9.2.3 Redline N/A N/A 60 days

CMSFB/BAFB

• Critical, Core Hours**

10.9.1.2 4 hours 4 hours Daily 72 hours

• Critical, Non-Core Hours**

10.9.1.2 6 hours 4 hours Daily 72 hours

• Non-Critical

10.9.1.2 24 hours 48 hours N/A 14 days

Page | 14

Objective Area Applicable

Paragraph(s) Initial Response

Estimated Time to Repair

Situation

Report

Action Completed

Install/Move/Add/Change (IMAC) Services

10.9.1.2

• Urgent N/A N/A N/A 7 days*

• Routine N/A N/A N/A 30 days*

Documentation/Drawing Updates Redline N/A N/A 60 days

*Number of days to complete action; excludes procurement delivery time.

**This will be activated for surge efforts, otherwise all responses will be non-critical.

*** Response times to complete action excludes A/V support by associate contractor.

Page | 15

4.0 Service Summary Items

Page | 16

5.0 Contract Data Requirements List (CDRL)

The point of delivery for all CDRL products, except as noted in Exhibit C, 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 Exhibit C for specific CDRL delivery instructions.

EVM CDRLs have additional delivery requirements. EVM CDRLs are also delivered via the CADE EVM CR website (http://cade.osd.mil/roles/submitters)

Jacobs will need to request an account in order to submit to the EVM CR. You can also email CADESupport@Tecolote.com or call the CADE/PARCA help desk at 253-564-1979.

5.1 Contract Data Requirements List (CDRL) Identification

CDRL List

Task CDRL DID Description

10.1 C001 DI-MGMT-

81861/T

22F5900:

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 C002 DIMISC-

80508B/T

22F5900: Task Order Status Report, [month ending]

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

10.2.1.1 C003 DI-MISC-80508B/T 22F5900: Work

Request History

Conveys project information for all work requests.

Includes information such as submission date, project description, need date, date complete, initial and final IMS, initial element of cost estimates and final elements of cost and customer survey results.

10.7 C004 DI-MISC-80508B/T 22F5900:

Baseline Engineering Documentation

This CDRL contains engineering documentation which potentially includes some or all of the following components: Slide Package, DoDAF Artifacts, Rack Elevation drawings, Testbed Layout drawings, CONOPS, and Requirements Traceability Matrix (RTM), Version Description Documents, and Floor Plans.

10.3.1.10 C005 DI-MISC-80508B/T 22F5900:

Assessment and

This CDRL contains the documentation required to support C&A activities: Risk Management http://cade.osd.mil/roles/submitters

Page | 17

Task CDRL DID Description Authorization Documentation

Framework (RMF) Packages, FISMA Report, DITPR Report, Vulnerability Scan and Compliance Reports, Accreditation Boundaries Report, Boundary Protection Configurations, BMDS RMF Comprehensive Package, DR/COOP IT Quarterly Tabletop and Annual Exercise Scenarios/Test Plan Packages generated under this

TO.

10.5.4.1 C006 DI-MISC 80508B/T 22F5900:

Maintenance & Spare Report

The Technology Refresh Plan takes into account the formally documented current state of the hardware necessary to execute business functions, deliver services, and maintain the logical relationships between customers, partners, and suppliers. Primarily, this superset will contain the system architecture, the storage architecture, and the network architecture across the enterprise.

10.5.4.2 C007 DI-MISC-80508B/T 22F5900:

Operational Support Documents:

Technology Refresh Plan

Identifies type, location, and frequency of recurring sustainment activities, the sparing methodology used in establishing a “Recommended Spares Requirement List” and the identification of licensing, maintenance agreements, and renewal documentation of hardware and software assets. The plan shall describe how the contractor shall develop and deliver the capabilities and outcomes identified in paragraph 10.5.4.2 of the PWS.

Page | 18

6.0 Milestones

PWS Paragraph(s) Activity Date / Days after Contract

(DAC)

10.1 Integrated Baseline Review 180 DAC and annual IBR

each year after

Page | 19

7.0 Property

7.1 Government Property (GP)

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

7.2 Government Furnished Property (GFP)

In addition to the GFP identified on IRES Contract Attachment 5, the following GFP is applicable to this task order: none

7.3 Government Furnished Information (GFI)

The following GFI is applicable to this task order: Technical documentation from the C2BMC Prime Contractor.

7.4 Contractor Acquired Property (CAP)

All CAP will be managed under the terms and conditions associated with the Government Property Management task order.

Page | 20

8.0 Special Requirements

• JEWL analyst(s), in accordance with the MDA Security Classification Guidance, must maintain a Top Secret clearance with Sensitive Compartmented Information (SCI).

Page | 21

9.0 Applicable Documents

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

Title Originator Date

JROCM 062-02

Joint Staff – Joint Requirements Oversight Council

29 Apr 2002

Page | 22

10.0 Statement of Objectives and Outcomes

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 Workload and Resource Management

10.2.1 Objective - Requirements Facilitation

The Contractor shall receive, evaluate, and manage requirements from stakeholders, testers, and users of the C2BMC mission areas and their capabilities at the MDIOC and shall ensure they are valid, accurate, complete, and understood.

Outcomes:

10.2.1.1 Implement a work request process/system, including a Requirements Review Board (RRB) that allows government personnel to submit, assess, validate, vet, prioritize, approve, track, evaluate requests, and maintain a workload history (CDRL C003)

10.2.1.2 Provide cost estimates for events, projects, and hardware and software purchases.

10.2.2 Objective - Master Scheduling

The contractor shall develop and maintain a master schedule of C2BMC services and activities (i.e., customer system loads, upgrades, test events, projects).

Outcomes:

10.2.2.1 Creates, maintains, and uses the C2BMC Executive Summary Schedule (CESS) as a basis for resource planning and a task order schedule that serves as input to the contract Integrated Master Schedule (IMS) and aids in planning and resources allocation.

10.2.2.2 Plan, evaluate, and advise the COTR on use of assets to meet requirements and avoid conflicts for resources.

10.2.2.3 Mitigate system maintenance, hardware build-outs and software refresh abilities to minimize the effect on mission requirements.

10.2.3 Objective - Configuration Management and Asset Control

The contractor shall provide configuration control for facilities and equipment. The contractor shall provide compliant management services of assets (i.e., equipment, software), from initial receipt to final disposition and maintain an auditable inventory. MDNT has configuration control of the CTB-TA.

Outcomes:

10.2.3.1 Implement a comprehensive configuration management approach and maintain configuration control for all facilities, cabling, systems, operating procedures, and assets.

Implement a mechanism for recording, tracking, and reporting the status of Configuration Items (CIs).

Page | 23

10.2.3.2 Develop and provide baselined systems artifacts (e.g. Interface Control Documents, Network Interface Control Documents, schematic, functional system overlay and architectural drawings compliant with current version of DoDAF) that clearly diagram and articulate the system or components performance, function, and physical attributes and functional relation between parts, subsystems, and systems.

10.3 Security Management

10.3.1 Objective - Cybersecurity Compliance

The Contractor shall provide services compliant with IAW DoDI 8510.01, DoDI O-8530.1, MDA 8499.01-INS, DoDI 8140.01 and all follow on directives, DoD Cybersecurity Implementation Plan, and supplementary BC policies or plans that prevent unauthorized access, use, disclosure, disruption, modification, inspection, recording, or destruction of information and/or equipment and processes that create that information for the mission areas. The Contractor will have Cyber responsibility in order to meet test and event requirements.

The contractor shall support evening shifts and on-call weekends (reference section 8 for shifts, hours and caveats) to expand schedule availability and opportunity to execute cyber and mission support activities.

Outcomes:

10.3.1.1 Perform Cyber administration and security management tasks using DISA tools and report, monitor applicable security resources for updated requirements and comply with DoD/Cyber Command Task Orders (CTO). All CTOs shall be coordinated within the constraints of the C2BMC baseline with National Team for C2BMC Test Articles and VTEC prior to action, remedy, or compliance.

10.3.1.2 Recommend security requirements and safeguards and establish processes to validate security requirements, mitigate cyber risks, and acquire certification and accreditation of systems.

10.3.1.3 Anticipate requirements for cyber accreditations and recommend a Plan of Action and Milestones (POA&M) to accomplish tasks that allow participation in events.

10.3.1.4 Demonstrate and report compliance with cybersecurity requirements using the standard scorecard.

10.3.1.5 Assess systems, networks, and using passive and active evaluations, participate in the Security Test and Evaluation (ST&E) processes, and identify vulnerabilities and deviations from acceptable configurations.

10.3.1.6 Document the results of Certification and Accreditation activities

10.3.1.7 Conduct and Support Incident Response actions and analyze malicious events and known exploitations/vulnerabilities for the creation of custom signature rule sets in coordination with the Tier II CERT.

10.3.1.8 Identify and manage government common user systems and special purpose systems that require custom security features and procedures.

10.3.1.9 Comply with RMF mitigation requirements for Category I, II, and III findings.

10.3.1.10 Obtain Authorization to Operate (ATO) for mission areas and maintains status by implementing agreed-upon set of security controls in accordance with guidelines set by the office of the Approving Official

Page | 24

10.3.1.11 Obtain Special Event Accreditations for events in which mission areas must participate.

10.3.2 Objective - Security Operations

The Contractor shall provide security management and services to ensure compliance with MDIOC, MDA and DoD standards.

Outcomes:

10.3.2.1 Perform duties as the Security Assistant as defined in the Standard Operating Procedure (SOP), coordinate for the Security Manager with Missile Defense Agency Security Department (MDA/EIR) Security Personnel on all physical and information security issues and tasks, and perform block captain activities in accordance with latest government directions.

10.3.2.2 Manage access to controlled areas, process incoming and outgoing Visit Authorization Requests, maintain open storage certification requirements, and provide guidance to occupants on the Security Classification requirements.

10.3.2.3 Receive, generate and reproduce classified material up to the SECRET classification.

10.3.2.4 Develop and maintain SOP documentation in accordance with the standard MDA/EIR procedures.

10.3.3 Objective – Local Control Center (LCC) Activities

The Contractor shall provide technical services in support of the Local Control Center (LCC) Activities.

These include Cyber Documentation, Semi-Annual Reports (via the Enterprise Reporting System), and Command Cyber Operational Readiness Inspection (CCORI) oversight (CDRL C005).

Outcomes

10.3.3.1 Cyber Document Review and Reporting

Collect, review, write, and submit required reports to the MDA Cyber Security Service Provider (CSSP) for each BC Test, Training, Remote Site, and Administrative System:

• Maintain cyber libraries, eMASS and repositories. (Documents, findings, and evidence)

• Track document submission schedules

• Collect documents from system ISSOs to include:

o Updated Network Diagrams, Mission Relevant Cyber Terrain information (as applicable) o Security Technical Implementation Guide (STIG) Compliance Report o Equipment Inventory Report, and System/Site Information Form (SIF)

10.3.3.2 Command Cyber Operational Readiness Inspection (CCORI)

• The Contractor Shall support BC data collection and correlation efforts of required artifacts for Command Cyber Operational Readiness Inspection (CCORI)

10.3.4 Objective – CTB-TA and VTEC

The Contractor shall provide DoD, MDA, and MDIOC compliant security services per paragraph 10.3 that prevent unauthorized access, use, disclosure, disruption, modification, inspection, recording, or destruction of information and/or equipment and processes that create that information for the mission

Page | 25 areas. The Contractor will have administrative Cyber responsibility for the CTB-TA and VTEC to be compliant from an IA perspective as provided by and limited by the National Team baseline, in order to meet test and event requirements. The ICCB can approve exceptions necessary to achieve or maintain appropriate cyber compliance above baseline. These security services and tools include:

• Security Engineering and Security Administration processes and products that support system certification and accreditation (C&A)

• Cybersecurity Concept of Operations

• Accreditation requirements of the DoD’s Risk Management Framework (RMF)

• Information Assurance Vulnerability Management (IAVM)

• ePolicy Orchestrator System (ePO)

• Continuous security monitoring and reporting as an MDA Tier III Computer Network Defense

(CND) organization by managing:

o DISA security tools including Endpoint Security System (ESS) o Assured Compliance Assessment Solution (ACAS) o Enterprise Mission Assurance Support Service (eMASS) o Continuous Monitoring and Risk Scoring (CMRS)

The Contractor shall provide administration and staffing to support ops requirements and FRAGOs for the following C2BMC Test Article (CTB-TA) cyber management tools such as but not limited to ACAS, SolarWinds equivalent capability, ArcSight, ESS, and CyberArk. The Contactor shall support the National Team’s use of Endgame. These tasks include:

• Administer and support the tools within the constraints of the C2BMC baseline and RMF practices

• Assist MDNT in the CTB-TA Cyber policy definition, recommendations, and resolution

10.3.5 Objective – CTB-TE

The Contractor shall provide DoD, MDA, and MDIOC compliant security services per paragraph 10.3 that prevent unauthorized access, use, disclosure, disruption, modification, inspection, recording, or destruction of information and/or equipment and processes that create that information for the mission areas. The Contractor will have full Cyber responsibility for applying cyber patches, IAVMs, CTOs, and scanning in the CTB–TE. These security services and tools include:

• Security Engineering and Security Administration processes and products that support system certification and accreditation (C&A)

• Cybersecurity Concept of Operations

• Accreditation requirements of the DoD’s Risk Management Framework (RMF)

• Information Assurance Vulnerability Management (IAVM)

• ePolicy Orchestrator System (ePO)

• Continuous security monitoring and reporting as an MDA Tier III Computer Network Defense

(CND) organization by managing:

o DISA security tools including Endpoint Security System (ESS) o Assured Compliance Assessment Solution (ACAS) o Enterprise Mission Assurance Support Service (eMASS) o Continuous Monitoring and Risk Scoring (CMRS)

The Contractor shall provide administration and staffing for the following Test Environment (CTB-TE) cyber management tools such as but not limited to ACAS, SolarWinds equivalent capability, ArcSight, ESS, and CyberArk.

Page | 26

10.3.6 Objective – JEWL and IPOP (Part of IRES Follow-On Technical Area 2: MDS MISSION

IT SUPPORT AND SOLUTIONS)

The Contractor shall provide DoD, MDA, and MDIOC compliant security services per paragraph 10.3 that prevent unauthorized access, use, disclosure, disruption, modification, inspection, recording, or destruction of information and/or equipment and processes that create that information for the mission areas. The Contractor will have full Cyber responsibility for applying cyber patches, IAVMs, CTOs, and scanning in the JEWL and IPOP. These security services and tools include:

• Security Engineering and Security Administration processes and products that support system certification and accreditation (C&A)

• Cybersecurity Concept of Operations

• Accreditation requirements of the DoD’s Risk Management Framework (RMF)

• Information Assurance Vulnerability Management (IAVM)

• ePolicy Orchestrator System (ePO)

• Continuous security monitoring and reporting as an MDA Tier III Computer Network Defense

(CND) organization by managing:

o DISA security tools including Endpoint Security System (ESS) o Assured Compliance Assessment Solution (ACAS) o Enterprise Mission Assurance Support Service (eMASS) o Continuous Monitoring and Risk Scoring (CMRS)

The Contractor shall provide administration and staffing for the following JEWL cyber management tools such as but not limited to ACAS, SolarWinds equivalent capability, ArcSight, ESS, CyberArk.

10.4 CTB Test Environment (Part of IRES Follow-On Technical Area 2: MDS MISSION IT

SUPPORT AND SOLUTIONS)

The Contractor shall determine requirements, design, implement, sustain, test, and provide configuration management for the mission areas as defined in appropriate drawings, to ensure readiness for test, events, upgrades, and maintenance.

10.4.1 Objective - Core Routing and Switching (Red/Black)

The contractor shall sustain, design, build, innovate, troubleshoot, and perform root cause analyses for CTB-TE Core Routing and Switching devices in support of multiple, simultaneous, and independent events.

Outcomes:

10.4.1.1 Use sound systems engineering practices to design and implement device solutions that gain efficiencies and reduce sustainment costs.

10.4.1.2 Configure the CTB-TE for events.

10.4.1.3 Condition message traffic to comply with Test Article ICDs or interfaces.

Page | 27

10.4.1.4 Maintain drawings to reflect systems configurations.

10.4.1.5 Design the ability to isolate Core Routing and Switching devices based on event architecture requirements.

10.4.1.6 Implement an integrated approach to operate and manage CTB-TE investments that provides for the continuous identification, selection, control, life-cycle management, and evaluation of the CTB-TE investments in a structured process resulting in a systematic method maximizing the return of CTB-TE investments.

10.4.2 Objective - Modeling and Simulation (M&S)

The contractor shall maintain a capability to stimulate CTB-TAs and test for multiple, concurrent, and independent events.

Outcomes:

10.4.2.1 Sustain model and simulation capabilities.

10.4.2.2 Operate simulations, emulators, and data manipulation tools to condition message traffic during test events.

10.4.2.3 Maintain a list of simulation scenarios in the library.

10.4.2.4 Modify simulation scenarios to meet test needs.

10.4.2.5 Record test event data, creates, and executes data playbacks.

10.4.3 Objective - Analysis Tools

The Contractor shall sustain the test analysis environment.

Outcomes:

10.4.3.1 Provide data collection tools and devices.

10.4.3.2 Provide data analysis tools, servers, desktop computers, and software.

10.4.3.3 Provide data storage and archive for all test and analysis requirements.

10.4.4 Objective - Interfaces

The Contractor shall design, implement, and sustain CTB-TE interfaces during multiple, simultaneous, and independent CTB-TA test events.

Outcomes:

10.4.4.1 Design interfaces based on Interface Control Documents (ICD) / Interface Design Documents (IDD) into the CTB-TA.

10.4.4.2 Design and manage interfaces internal to the CTB-TE and external to the CTB-TE (Reference: Accreditation Security Architecture: CTB-TA drawing).

10.4.4.3 Design interfaces for multiple, simultaneous, and independent events.

10.5 Mission System and Core IT Sustainment (Part of IRES Follow-On Technical Area 1:

ENTERPRISE INFORMATION ENVIRONMENT AND RDT&E IT SERVICES AND

SOLUTIONS)

Page | 28

This task provides for the sustainment of mission and core equipment within mission areas defined in Sections 3.1, 3.2, 3.6, 3.8. (CDRL C006)

10.5.1 Objective - Mission System Sustainment

The contractor shall provide services necessary for the information systems and network sustainment of mission systems, mission capabilities, and mission room capabilities. Sustainment activities include network management, configuration management, proactive/corrective maintenance, break/fix service restoration, for C2BMC Mission System enclaves.

Outcomes:

10.5.1.1 Configure enclaves and laboratories in a manner to enable full functionality of mission systems and capabilities.

10.5.1.2 Core Hours Break/Fix Response. Respond to degradations/failures within 8 hours and within 24 hours provide an estimated timeline associated with service restoral in accordance with contractor-developed ticket escalation procedures. Demonstrate minimal impact to mission while repair activities are initiated, conducted, and completed. Provide a summary of degradations/failures, to include the response times and a root-cause analysis in the monthly Task Order Status Review (CDRL C002).

10.5.1.3 Non-Core Hours Break/Fix Response. The response times and procedures outlined in SSI #5 in section 4 apply to incidents occurring outside of core hours but don’t begin until 0730 the following business day.

10.5.2 Objective - Test Article Hardware/Software Installation

The contractor shall manage integration of spiral loads into the CTB. This includes activities such as facilitating requirements with customers, scheduling and coordinating installation, tracking and reporting load-related issues for full life cycle to negotiate, de-conflict priorities with customers/stakeholders, and inform the C2BMC community of CTB readiness to support testing activities.

The contractor shall assess spiral loads prior to installation. Assessments require 24-48 hours to complete allowing the contractor appropriate time to determine scope, impacts, risks, schedule and overall summary of what is required to execute spiral load installations. At any time, planned install schedules and forecasts may change, experience interruptions, incur delays or be postponed by developers, stakeholders, or higher level authorities to reduce and mitigate risk to other concurrent testing activities.

The contractor shall perform spiral loads and baseline changes in the CTB-TA in accordance with the C2BMC Prime contractor’s delivered installation instructions and documentation. These services are part of an independent review of the product quality as delivered to MDA and BCX. Spiral loads are delivered using an Agile Development model through both physical media and digital delivery methods. Due to frequent changes in agile delivery schedules, spiral loads may arrive on time as originally forecasted by the developer or with little to no notice. Estimated install times can range in scope from small minor changes (minutes/hours) to enterprise-wide changes (days/weeks).

The contractor shall support C2BMC Prime Contractor’s on-site Agile Development and Integration activities where CTB-TA assets are considered extensions of the Prime Contractor’s development labs.

Support may include activities such as hardware racking and cabling, prototyping, and installation assistance as well as integration troubleshooting.

Page | 29

The contractor shall notify the COTR (or designee) to coordinate and gain approval for requested and/or required CTB-TA baseline and non-baseline (developmental) changes where the C2BMC Prime Contractor did not provide a spiral delivery, install instructions or proper documentation to execute such a change.

The contractor shall support evening shifts and weekends to expand schedule availability and opportunity to execute spiral loads and integration activities.

The contractor shall provide necessary spiral load installation, issues and status briefings as deemed appropriate by the COTR.

Outcomes:

10.5.2.1 Assess spiral loads to determine dependencies, time, scope, complexity, impacts, risks and required resources prior to installation

10.5.2.2 Develop and publish initial spiral load installation schedules and forecasts

10.5.2.3 Provide COTR and appropriate stakeholders a daily load status update when spiral loads in progress

10.5.2.4 Conduct and document post-install configuration audits, lab checkout actions, and baseline deficiency resolution prior to Cycle-1 turnover and testing

10.5.2.5 Provide troubleshooting assistance to Integration and Test teams during Cycle-1 and Cycle-2 activities

10.5.2.6 Prepare and provide a spiral install After Action Report (AAR) and documentation deficiency “Redlines” to COTR

10.5.2.7 Chair and conduct a daily status collaboration brief with C2BMC stakeholders encompassing (at a minimum): operational status and availability of all CTB-TA assets, spiral load status and technical issues of interest

10.5.2.8 Conduct regular workload prioritization and readiness briefings with COTR on planned and forecasted spiral loads and technical issues impacting CTB-TA work efforts

10.5.3 Objective - Core IT and Personnel Workspace Services and Sustainment

The Contractor shall provide services necessary for sustainment of C2BMC ancillary IT systems and capabilities and office space areas. Sustainment activities include network management, configuration management, proactive/corrective maintenance, break/fix service restoration. IT systems include:

• Classified Local Area Network (CLAN)

• Integrated Classified Environment (ICE)

• Unclassified Local Area Network (ULAN)

• Software

• Printers

• Voice communications

• Office equipment

The contractor shall provide customer support services inclusive of service desk operations, touch-labor client services, conference and event activities, Install/Move/Add/Change (IMAC) services.

Page | 30

10.5.3.1 Configure and maintain office spaces in a manner to enable full functionally of personnel.

10.5.3.2 Respond to degradations/failures within 8 hours and within 24 hours provide an estimated timeline associated with service restoral in accordance with contractor-developed ticket escalation procedures. Demonstrate minimal impact to mission while repair activities are initiated, conducted, and completed. The response times for incidents occurring outside of core hours do not begin until 0730 the following business day. A summary of degradations/failures, to include the response times and a root-cause analysis shall be documented in the monthly Task Order Status Review (CDRL C002).

10.5.3.3 Provide Tier II help desk support during core business hours (Monday-Friday: 0730h- 1600h). Resolve calls received outside of core business hours the following business day. Ensure knowledge base maintenance and development enabling first call resolution of help desk calls.

Ensure 24/7 2-hour response time for help desk support calls coming from the critical functional areas.

10.5.3.4 Manage customer experience lifecycle ensuring all requests are handled in accordance with incident response and service level objectives with communication out to customers with defined service level expectations.

10.5.3.5 Report to the MDIOC Service Desk when classified and unclassified printers are not operational and facilitate paper and toner replacements.

10.5.3.6 Service the "Unclassified Sensitive/CUI/Proprietary Information" recycle bins through the MDIOC Service Desk.

10.5.4 Objective - Maintenance Renewal, Sparing, and Tech Refresh

The contractor shall maintain and refresh hardware, software and current capabilities across all systems, services, and functional areas, excluding those served by an external baseline (e.g. The C2BMC Test Article Baseline). Maintenance and tech refresh for functional areas served by an external baseline will be specifically addressed in those sections. The contractor shall provide recommendations on critical spares, and maintain spare hardware as required (CDRL C007).

Outcomes:

10.5.4.1 Maintain and refresh hardware, software and current capabilities in accordance with industry best maintenance practices ensuring an appropriate mix between proactive and corrective maintenance, repair, and replacement to maintain availability. Document and execute sparing plans, maintenance plans, schedules, and performance expectations. Utilize system performance and maintenance trending analysis to manage the maintenance program. Manage and maintain currency on all licensing and update services for third-party software, software drivers, and diagnostic software.

10.5.4.2 Develop criteria for technology refresh of hardware, software, and current capabilities in accordance with industry best practices to ensure availability. Leverage MDA Information Technology (IT) support policy to minimize investments for IT hardware and software above MDA standards. Manage and provide the government with real-time access to a database that conforms to Defense Property Accountability System (DPAS) requirements identifying the location and acquisition details for all acquired assets. Implement an integrated approach to operate and manage hardware and software investments that provides for the continuous identification, selection, control, life-cycle management, and evaluation of the investments in a

Page | 31 structured process resulting in a systematic method to maximize investment return and allow predictable budgeting.

10.5.4.3 Maintain and refresh hardware, software and current capabilities in accordance cybersecurity requirements, ensuring an appropriate mix between proactive and corrective maintenance, repair, and replacement to maintain cybersecurity compliance.

10.5.4.4 The contractor shall complete procurements and execute work as required to support life cycle tech refresh efforts within the C2BMC Test Bed.

10.6 Test Events Services (Part of IRES Follow-On Technical Area 3: MDS Mission Operations)

This task ensures the C2BMC readiness to participate in tests and events identified in the IMTP and other activities required for the test and evaluation of the C2BMC.

10.6.1 Objective – Full Hardware-in-the-Loop (HWIL) Events

The Contractor shall plan, design, schedule, and execute Full HWIL events.

Outcomes

10.6.1.1 Develop requirements, architectures, and required lab preparations.

10.6.1.2 Monitor and de-conflict Event Protection Periods (EPPs) / Test Event Freeze.

10.6.1.3 Prepare lab equipment, such as interfaces, cybersecurity, and ancillary equipment.

10.6.1.4 Provide network engineering, test control, and system administrators during event execution.

10.6.1.5 Present an AAR to the COTR after the event.

10.6.1.6 Ensure lab is Returned-To-Baseline (RTB) or a baseline defined by COTR.

10.6.2 Objective - Sprint Hardware-in-the-Loop (HWIL) Events

The Contractor shall plan, design, schedule, and execute Sprint HWIL events.

Outcomes:

10.6.2.1 Develop requirements, architectures, and required lab preparations.

10.6.2.2 Monitor and de-conflict Event Protection Periods (EPPs) / Test Event Freeze.

10.6.2.3 Prepare lab equipment, such as interfaces, cybersecurity, and ancillary equipment.

10.6.2.4 Provide network engineering, test control, and system administrators during event execution.

10.6.2.5 Present an AAR to the COTR after the event.

10.6.2.6 Ensure lab is Returned-To-Baseline (RTB) or a baseline defined by COTR.

10.6.3 Objective - System Pre-Mission Test (SPMT) / System Post-Flight Reconstruction (SPFR) - Hardware-in-the-Loop (HWIL) Events

The Contractor shall plan, design, schedule, and execute SPMT / SPFR HWIL events.

Page | 32

10.6.3.1 Develop requirements, architectures, and required lab preparations.

10.6.3.2 Monitor and de-conflict Event Protection Periods (EPPs) / Test Event Freeze.

10.6.3.3 Prepare lab equipment, such as interfaces, cybersecurity, and ancillary equipment.

10.6.3.4 Provide network engineering, test control, and system administrators during event execution.

10.6.3.5 Present an AAR to the COTR after the event.

10.6.3.6 Ensure lab is Returned-To-Baseline (RTB) or a baseline defined by COTR.

10.6.4 Objective - Flight Test Event

The Contractor shall plan, design, schedule, and execute Flight Test events.

Outcomes:

10.6.4.1 Develop requirements, architectures, and required lab preparations.

10.6.4.2 Monitor and de-conflict Event Protection Periods (EPPs)/ Test Event Freeze.

10.6.4.3 Prepare lab equipment, such as interfaces, cybersecurity, and ancillary equipment.

10.6.4.4 Provide network engineering, test control, and system administrators during event execution.

10.6.4.5 Present an AAR to the COTR after the event.

10.6.4.6 Ensure lab is Returned-To-Baseline (RTB) or a baseline defined by COTR.

10.6.5 Objective - International Test Event

The Contractor shall plan, design, schedule, and execute International Test events.

Outcomes:

10.6.5.1 Develop requirements, architectures, and required lab preparations.

10.6.5.2 Monitor and de-conflict Event Protection Periods (EPPs)/ Test Event Freeze.

10.6.5.3 Prepare lab equipment, such as interfaces, cybersecurity, and ancillary equipment.

10.6.5.4 Provide network engineering, test control, and system administrators during event execution.

10.6.5.5 Present an AAR to the COTR after the event.

10.6.5.6 Ensure lab is Returned-To-Baseline (RTB) or a baseline defined by COTR.

10.6.6 RESERVED

10.6.7 Objective - Pairwise Test Event

The Contractor shall plan, design, schedule, and execute Pairwise Test events.

10.6.7.1 Develop requirements, architectures, and required lab preparations.

Page | 33

10.6.7.2 Monitor and de-conflict Event Protection Periods (EPPs)/ Test Event Freeze.

10.6.7.3 Prepare lab equipment, such as interfaces, cybersecurity, and ancillary equipment.

10.6.7.4 Provide network engineering, test control, and system administrators during event execution.

10.6.7.5 Present an AAR to the COTR after the event.

10.6.7.6 Ensure lab is Returned-To-Baseline (RTB) or a baseline defined by COTR.

10.7 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.

Immediate Response Tasks (IRTs) (formerly known as Routine or Minor), and Quick Response Tasks (QRTs) (formerly known as Small projects).

Outcomes:

• 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, as required. 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, as required.

• 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, as required. Participate in required MDIOC review boards (Design Review Board, Engineering and Architecture Board, as required).

• MDIOC ERB:

• Ensure compliance with the published instructions and standards (I.e. MDIOC SEP & ERB

Charter) that govern the MDIOC Engineering Review Board (ERB). Ensure completion of Systems Engineering gate reviews required in order to validate requests, align with facility standards, and integrate solutions across the MDIOC facility.

o Present to the ERB all projects impacting the MDIOC facility that meet the entry criteria defined in the charter.

o Submit briefings and supporting documentation to the MDIOC ERB as outlined in the charter.

o Reconcile any re-work actions and technical conflicts that come from the ERB and receive approval…