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

1 Updated sections 3.9, 5.1, 8.0, & 10.9.2 30 Sep 2022

B addition of scope - External Sensors Laboratory language, sections

3.10 and 3.11 of the PWS 3/1/2023

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

3.10 Enterprise Sensors Lab (ESL)………………………………………………………………. 13

3.11 Other MDA/BCX Supported Networks…………………………………………………..… 13

4.0 Service Summary Items

5.0 Contract Data Requirements List (CDRL)

5.1 Contract Data Requirements List (CDRL) Identification

5.2 CDRL Tailoring

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)

Page | 4

8.0 Special Requirements

9.0 Applicable Documents

10.0 Statement of Objectives and Outcomes

10.1 Task Order Administration

10.1.1 Objective - Task Order Management

10.1.2 Objective - Enterprise Task Order Support

10.1.3 Objective - Task Order Award and Modification

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

Page | 5

10.5.3 Objective - Core IT and Personnel Workspace Services and Sustainment

10.5.4 Objective - Maintenance Renewal, Sparing, and Tech Refresh

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 ............................................................. Error! Bookmark not defined.

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

Page | 7

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 | 8

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 | 9

• 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

• Enterprise Sensors Laboratory (ESL) conducts Research and Development (R&D) and provides test facilities for demonstrating Infra-Red (IR) measurement level fusion of Overhead Persistent IR (OPIR), Airborne IR, Static IR sources to detect, track, and discriminate threats and to increase BMDS effectiveness under raid scenarios by enhancing the utility of existing assets for BMDS OPIR Architecture (BOA).

Table 1 shows the mission areas and the government stakeholders who collaborate with MDA/BCX.

Table 1. Mission Area and Stakeholders

Mission Area Stakeholders

CTB-TE BCX

CTB-TA BCE, BCT, BCD, BCX

IPOP BCX

JEWL BCDS, BCX

CSSC BC, BCW, BCT, BCX

STOC BCW, BCT, BCX

IT-Personnel Workspace MDA/BC personnel at the

MDIOC: Gov’t, Military, FFRDC, SETA, MDNT, Contractor

OCL BCT, BCX, NG (SWDC)

VTEC BCT, BCX, MDNT

LCC Activities BCE

BNOSC BCW

ESL BCDV

Page | 10

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 | 11

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 C2BMC JWICS ICE vIPer SVOIP CLAN ULAN DRSN

Building / Room

Critical Functional Area

Critical / Non-Critical

720/1102-01 STOC 1 NC* NC* NC* NC* NC* NC* NC*

720/1102-02 STOC 2 NC* NC* NC* NC* NC* NC* NC*

720/1103-01 CCC Level

NC NC NC NC NC

720/1111 Office Floor NC NC NC NC NC

720/1111-01 Office NC NC NC

720/1111-02 Office NC NC NC

720/1117-03 CCC – S8.2

OPS***

Yes C C C C NC C

720/1117-06 Office NC NC NC NC NC

720/1117-07 Office NC NC NC NC NC

720/1117-08 Office NC NC NC NC NC

720/1117-09 Office NC 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

Page | 12

720/1119-01 Office NC NC NC NC

720/1119-02 Office Floor NC NC NC NC NC NC

720/1119-03 Office Floor NC NC NC NC NC NC

720/1107-01 Conference Room

NC NC NC NC

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

720/1306- 02/03/04

DCC Yes C C C C

CMSFS/2102J OPS Space NC* NC*

BAFB/5760-

Office NC*

BAFB/5760-

User Node NC*

BAFB/5760-

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

Page | 13

Objective Area Applicable

Paragraph(s) Initial Response

Estimated Time to Repair

Situation

Report

Action Completed

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*

• 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

Page | 14

Objective Area Applicable

Paragraph(s) Initial Response

Estimated Time to Repair

Situation

Report

Action Completed

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

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.

3.10 Enterprise Sensors Lab (ESL)

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

3.11 Other MDA/BCX Supported Networks

Procure and deliver requested materials (consumables, hardware) for use in maintaining other MDA/BCX supported networks.

Page | 15

4.0 Service Summary Items

In accordance with the IRES Performance Evaluation and Incentive Plan, Service Summary Items (SSIs) 1 through 4 are common [required] on all task orders and will be assessed at the contract level (i.e., all task orders will receive the same rating).

SSI # Title Description Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

SSI 5

Sustainment Efforts:

Critical Incident Responses (IRs): Critical is defined by the tech and customer as mission critical and given a priority of High or Critical in Remedy

Mission critical incident requests are responded to within 2 hours and fixed within 24 hours, excluding extenuating circumstances beyond Contractor control.

4 or more mission critical incident requests did not meet established times for incident response and completion.

3 mission critical incident requests did not meet established times for incident response and completion.

2 mission critical incident requests did not meet established times for incident response and completion.

1 mission critical incident request did not meet established times for incident response and completion.

No mission critical incident requests are identified or 100% of mission critical incident requests meet established times for incident response and completion.

Each category will be measured independently, and then an SSI score will be given based on the lowest performance of evaluated efforts. Extenuating circumstances are provided for tickets outside of Contractor control for consideration by COTR to not include in monthly evaluation.

Sustainment Efforts:

BNOSC

BNOSC Mission Critical and Non Critical Tickets and Maintenance tasks are completed by their expected hours (per the location chart included above)

Contractor missed more than 4 critical OR 5 non critical / maintenance tasks.

3 mission critical OR no more than 4 non critical / maintenance tasks did not meet established times

2 mission critical OR no more than 3 non critical / maintenance tasks did not meet established times

1 mission critical OR no more than 2 non critical / maintenance tasks did not meet established times

0 critical tickets, OR no more than 1 non critical / maintenance tasks did not meet established times

Sustainment Efforts:

Mission Response Team (MRT) Request for Service items (RFSs)

(Rated Monthly)

Sustainment effort RFS's are completed by their negotiated date with no impact to mission excluding extenuating circumstances beyond Contractor control

4 or more MRT RFS's did not meet established times for incident completion.

3 MRT RFS's did not meet established times for incident completion.

2 MRT RFS's did not meet established times for incident completion.

1 MRT RFS's did not meet established times for incident completion.

0 MRT RFS's did not meet established times for incident completion.

QPI Score = 0 QPI Score = 2.5 QPI Score = 5 QPI Score = 7.5 QPI Score = 10

Page | 16

Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

SSI 6

Management, measurement ratings

(Rated Quarterly)

Expectations for management review are met based on the

QASP monthly performance report.

Contractor must provide justification for recommended 5's and the customer must provide justification for below 3.

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

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

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

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

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

100% review of Requirements under QASP guidelines for management/ business relations, financial, labs, BNOSC, and JEWL.

QPI Score = 5 QPI Score = 10 QPI Score = 15 QPI Score = 22 QPI Score = 25

SSI 7a Cyber/End Point Security Solutions (ESS)

(Rated Monthly)

ESS Cert Compliance over assessment period to be evaluated

(MDA Standard is 100%)

No proactive actions were taken to raise compliance score, and cannot explain less than 60% overall compliance score.

Overall compliance score is greater than or equal to 60% and less than 70%

Overall compliance score is greater than or equal to 70% and less than 80%

Overall compliance score is greater than or equal to 80% and less than 90% is greater than or equal to 90%.

Contractor will provide data for every scan accomplished in each lab that month, explanations for dips, and proactive steps taken for non-compliant systems.

Enclaves are all weighted equally and score for ESS is average of total enclaves evaluated over the assessment period. The final scan of the month will be rated

Page | 17

Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

QPI Score = 0 QPI Score = 1 QPI Score = 2 QPI Score = 3 QPI Score = 4 unless extenuating circumstances effect the final scan, in that case the rest of the month's performance should be considered.

Justification provided for devices not included and devices outside contractor control are not included in QPI scoring.

Disputed dashboard numbers will be provided for justification why should not be included in monthly scoring.

If Cyber activities were impacted by events, then Cyber scores will not be deducted for work unable to be completed during an event. Event and timeline of impact will be listed with circumstances outside of Contractor control for why should not be included in scoring

SSI 7b

Cyber/Assured Compliance Assessment Solution (ACAS)

(Rated Monthly)

ACAS Scanning compliance over assessment peiod to be evaluated

(MDA Standard is 95%)

Less than 70% compliant with no action plan or low score explanations.

Overall compliance score is greater than or equal to 70% and less than 75% on scannable devices

Overall compliance score is greater than or equal to 75% and less than 85% on scanable devices.

score is greater than or equal to 85% and less than 90% on scannable devices.

is greater than or equal to 90% on scannable devices.

Contractor will provide data for every scan accomplished in each lab that month, explanations for dips, and proactive steps taken for non-compliant systems.

Enclaves are all weighted equally and score for ACAS is average of total enclaves evaluated over the assessment period. The final scan of the month will be rated unless extenuating circumstances effect the final scan, in that case the rest of

Page | 18

Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

QPI Score = 0 QPI Score = 1 QPI Score = 2 QPI Score = 3 QPI Score = 4 the month's performance should be considered.

Justification provided for devices not included and devices outside contractor control are not included in QPI scoring.

Percentages are based on security center numbers. Disputed dashboard numbers will be provided for justification why should not be included in monthly scoring.

If Cyber activities were impacted by events, then Cyber scores will not be deducted for work unable to be completed during an event. Event and timeline of impact will be listed with circumstances outside of Contractor control for why should not be included in scoring

SSI 7c

ArcSight

(Rated Monthly)

ArcSight validation of devices uptime over assessment period

ArcSight devices are running less than 60% of the time and are connected, available, and reporting to Tier II, other than planned maintenance.

ArcSight devices are running 60% to 70% of the time and are connected, available, and reporting to Tier II, other than planned maintenance.

ArcSight devices are running 70% to 80% of the time and are connected, available, and reporting to Tier II, other than planned maintenance.

ArcSight devices are running 80% to 90% of the time and are connected, available, and reporting to Tier II, other than planned maintenance.

ArcSight devices are running at least 90% of the time and are connected, available, and reporting to Tier II, other than planned maintenance. 2

Contractor will send a cert validation email every Friday and provide summary.

Downtimes outside Contractor’s control and planned maintenance are reported to Government in montly TOSR and not considered in scoring.

If Cyber activities were impacted by events, then Cyber scores will not be deducted for work unable to be completed during an event. Event and timeline of impact will be listed with circumstances outside of Contractor control for why should not be included in scoring

QPI Score = 0 QPI Score = .5 QPI Score = 1 QPI Score = 1.5 QPI Score = 2

SSI 7d Cyber Ark

(Rated Monthly) n/a

This SSI will be updated upon available evaluation criteria. When updated 7a will receive (3) QPI Points, 7b will receive (3)

Page | 19

Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

QPI points, 7c will receive (2) QPI points and 7d will receive 2 QPI points. Total SSI points for SSI 7 will remain at (10) possible QPI points.

SSI 8

Authorization to Operate (ATO) Status

(Rated Quarterly)

Contractor is rated on work done to prepare an enclave for ATO renewal. If no ATO renewal data is due, Contractor is rated on ATO compliance.

Scorecard: Less than 60%

Scorecard: 60% to 69.99%

Scorecard: 70% to 79.99%

Scorecard: 80% to 89.99%

Scorecard: 90% or higher

ATO scorecard is completed each quarter and total is scored based on total available points that quarter.

Items outside Contractor’s control are not considered.

If Cyber activities were impacted by events, then Cyber scores will not be deducted for work unable to be completed during an event. Event and timeline of impact will be listed with circumstances outside of Contractor control to be detailed for why should not be considered in scoring

QPI Score = 0 QPI Score = 2 QPI Score = 3 QPI Score = 4 QPI Score = 5

SSI 9 Cyber Event Preparedness (Rated Quarterly)

Contractor is rated on overall cyber posture and event readiness.

than 60%

Scorecard: 60% to 69.99%

Scorecard: 70% to 79.99%

Scorecard: 80% to 89.99%

Scorecard: 90% or higher 20

Cyber Event scorecard is completed each quarter and total is scored based on total available points that quarter

Page | 20

Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

QPI Score = 0 QPI Score = 14 QPI Score = 16 QPI Score = 18 QPI Score = 20

If Cyber activities were impacted by events, then Cyber scores will not be deducted for work unable to be completed during an event. Event and timeline of impact will be listed with circumstances outside of Contractor control to be detailed for why should not be considered in scoring In addition to Cyber Event scorecard, a hygiene finding can result in a deduction of 2.5 points per finding per event up to a maximum of 20 points per quarter. Only formal inspection results should be considered and only if hygeine is applicable to the event. Hygeine is defined as password files, open ports, unlocked racks, and open KVMs.

Contractor will explain any findings outside of contractor control for consideration by COTR to not be applicable to deduction of points from event. Password files older than the last ACD date will not be included.

Purchasing of tools, or unnaproved projects by the Government that would cut down or eliminate hygiene findings also be considered for exemption.

SSI 10

CTO and Plan of Action & Milestone (POAM)

(Rated Monthly)

Contractor is rated on evaluation criteria included in QASP and delivered in montly TOSR.

than 70%

Scorecard: 70% or higher

Scorecard: 80% or higher

Scorecard: 90% or higher

Scorecard: 100%

CTO and POAM scorecard is completed every month and additional data about the state of CTOs and POAMs are provided.

POAMs that have been submitted for extension are not considered but will still be reported. Extenuating circumstances or other activity outside of contractor control will not be considered.

Page | 21

Performance

Threshold

Unacceptable

Performance Threshold

Poor Performance

Performance Threshold

Meeting Requirements

Performance Threshold

Exceeding Some Requirements

Performance Threshold

Exceeding Many Requirements

Weight Assessment Method

QPI Score = 0 QPI Score = 2 QPI Score = 3 QPI Score = 4 QPI Score = 5

If Cyber activities were impacted by events, then Cyber scores will not be deducted for work unable to be completed during an event. Event and timeline of impact will be listed.

Page | 22

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.

http://cade.osd.mil/roles/submitters

Page | 23

Task CDRL DID Description

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

Assessment and Authorization Documentation

This CDRL contains the documentation required to support C&A activities: Risk Management 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

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

10.9.1

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.

5.2 CDRL Tailoring

The DD Form 1423 associated with each CDRL is attached in the following document.

22F5900-Exhibit-C_( Base).pdf

Page | 24

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 | 25

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 | 26

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

8.1 United States Forces Korea Wartime Clause

(The following USFK Wartime Clause applies ONLY when traveling within the jurisdiction of the USFK. When performing overseas for efforts in other jurisdictions, the MDA Wartime Clause applies.)

CONTINUANCE OF PERFORMANCE DURING ANY STATE OF EMERGENCY IN THE

REPUBLIC OF KOREA (ROK)

Invited Contractor (IC) and Technical Representative (TR) status shall be governed by the U.S.-ROK Status of Forces Agreement (SOFA) as implemented by United States Forces Korea (USFK) Reg 700-19, which can be found under the “publications” tab on the US Forces Korea homepage http://www.usfk.mil

(a) Definitions. As used in this clause—

“U.S. – ROK Status of Forces Agreement” (SOFA) means the Mutual Defense Treaty between the Republic of Korea and the U.S. of America, Regarding Facilities and Areas and the Status of U.S. Armed Forces in the Republic of Korea, as amended

“Combatant Commander” means the commander of a unified or specified combatant command established in accordance with 10 U.S.C. 161. In Korea, the Combatant Commander is the Commander, United States Pacific Command.

“United States Forces Korea” (USFK) means the subordinate unified command through which US forces would be sent to the Combined Forces Command fighting components.

COMUSK means the commander of all U.S. forces present in Korea. In the Republic of Korea, COMUSK also serves as Commander, Combined Forces Command (CDR CFC) and Commander, United Nations Command (CDR UNC).

“USFK, Assistant Chief of Staff, Acquisition Management” (USFK/FKAQ) means the principal staff office to USFK for all acquisition matters and administrator of the U.S.-ROK SOFA as applied to US and Third Country contractors under the Invited Contractor (IC) and Technical Representative (TR) Program (USFK Reg 700-19).

“Responsible Officer” (RO) means A senior DOD employee (such as a military E5 and above or civilian GS-7 and above), appointed by the USFK Sponsoring Agency (SA), who is directly responsible for determining and administering appropriate logistics support for IC/TRs during contract performance in the ROK.

“Theater of operations” means an area defined by the combatant commander for the conduct or support of specified operations.

“Uniform Code of Military Justice” means 10 U.S.C. Chapter 47

(b) General.

Page | 27

(1) This clause applies when contractor personnel deploy with or otherwise provide support in the theater of operations (specifically, the Korean Theater of Operations) to U.S. military forces deployed/located outside the United States in—

(i) Contingency operations;

(ii) Humanitarian or peacekeeping operations; or

(iii) Other military operations or exercises designated by the Combatant Commander.

(2) Contract performance in support of U.S. military forces may require work in dangerous or austere conditions. The Contractor accepts the risks associated with required contract performance in such operations. The contractor will require all its employees to acknowledge in writing that they understand the danger, stress, physical hardships and field living conditions that are possible if the employee deploys in support of military operations.

(3) Contractor personnel are not combatants and shall not undertake any role that would jeopardize their status. Contractor personnel shall not use force or otherwise directly participate in acts likely to cause actual harm to enemy armed forces.

(c) Support.

(1) Unless the terms and conditions of this contract place the responsibility with another party, the COMUSK will develop a security plan to provide protection, through military means, of Contractor personnel engaged in the theater of operations when sufficient or legitimate civilian authority does not exist.

(2) (i) All Contractor personnel engaged in the theater of operations are authorized resuscitative care, stabilization, hospitalization at level III military treatment facilities, and assistance with patient movement in emergencies where loss of life, limb, or eyesight could occur. Hospitalization will be limited to stabilization and short-term medical treatment with an emphasis on return to duty or placement in the patient movement system.

(ii) When the Government provides medical treatment or transportation of Contractor personnel to a selected civilian facility, the Contractor shall ensure that the Government is reimbursed for any costs associated with such treatment or transportation.

(iii) Medical or dental care beyond this standard is not authorized unless specified elsewhere in this contract.

(3) Unless specified elsewhere in this contract, the Contractor is responsible for all other support required for its personnel engaged in the theater of operations under this contract.

(d) Compliance with laws and regulations. The Contractor shall comply with, and shall ensure that its personnel supporting U.S Armed Forces in the Republic of Korea as specified in paragraph (b)(1) of this clause are familiar with and comply with, all applicable—

(1) United States, host country, and third country national laws;

(i) The Military Extraterritorial Jurisdiction Act may apply to contractor personnel if contractor personnel commit crimes outside the United States.

Page | 28

(ii) Under the War Crimes Act, United States citizens (including contractor personnel) who commit war crimes may be subject to federal criminal jurisdiction.

(iii) When Congress formally declares war, contractor personnel authorized to accompany the force may be subject to the Uniform Code of Military Justice.

(2) Treaties and international agreements;

(3) United States regulations, directives, instructions, policies, and procedures; and

(4) Orders, directives, and instructions issued by the COMUSK relating to force protection, security, health, safety, or relations and interaction with local nationals. Included in this list are force protection advisories, health advisories, area (i.e. “off-limits”), prostitution and human trafficking and curfew restrictions.

(e) Pre-deployment/departure requirements. The Contractor shall ensure that the following requirements are met prior to deploying/locating personnel in support of U.S. military forces in the Republic of Korea.

Specific requirements for each category may be specified in the statement of work or elsewhere in the contract.

(1) All required security and background checks are complete and acceptable.

(2) All contractor personnel meet the minimum medical screening requirements and have received all required immunizations as specified in the contract. In the Republic of Korea, all contractor employees subject to this clause shall comply with the same DoD immunization requirements applicable to Emergency Essential DoD civilians -INCLUDING ANTHRAX IMMUNIZATION. The Government will provide, at no cost to the Contractor, any Korean theater-specific immunizations and/or medications not available to the general public.

(3) Contractor personnel have all necessary passports, visas, and other documents required to enter and exit a theater of operations and have a Geneva Conventions identification card from the deployment center or CONUS personnel office—if, applicable.

(4) Country and theater clearance is obtained for contractor personnel. Clearance requirements are in DOD Directive 4500.54, Official Temporary Duty Abroad, DOD 4500.54-G, DOD Foreign Clearance Guide, and USFK Reg 1-40, United States Forces Korea Travel Clearance Guide. Contractor personnel are considered non-DOD personnel traveling under DOD sponsorship.

(f) Processing and departure points. Deployed contractor personnel shall—

(1) Under contingency conditions or under other conditions as specified by the Contracting Officer, process through the deployment center designated in the contract, prior to deploying. The deployment center will conduct deployment processing to ensure visibility and accountability of contractor personnel and to ensure that all deployment requirements are met;

(2) Use the point of departure and transportation mode directed by the Contracting Officer; and

(3) If processing through a deployment center, process through a Joint Reception Center (JRC) upon arrival at the deployed location. The JRC will validate personnel accountability, ensure that specific theater of operations entrance requirements are met, and brief contractor personnel on theater-specific policies and procedures.

Page | 29

(g) Personnel data list.

(1) The Contractor shall establish and maintain with the designated Government official a current list of all contractor personnel that deploy with or otherwise provide support in the theater of operations to U.S.

military forces as specified in paragraph (b)(1) of this clause. The Synchronized Pre-deployment and Operational Tracker (SPOT) is the designated automated system to use for this effort. This accountability requirement is separate and distinct from the personnel accountability requirement listed in the U.S–ROK SOFA’s Invited Contractor/Technical Representative Program (as promulgated in USFK Regulation 700- 19).

(2) The Contractor shall ensure that all employees on the list have a current DD Form 93, Record of Emergency Data Card, on file with both the Contractor and the designated Government official.

(h) Contractor personnel.

(1) The Contracting Officer may direct the Contractor, at its own expense, to remove and replace any contractor personnel who jeopardize or interfere with mission accomplishment or who fail to comply with or violate applicable requirements of this clause. Contractors shall replace designated personnel within 72 hours, or at the Contracting Officer’s direction. Such action may be taken at the Government’s discretion without prejudice to its rights under any other provision of this contract, including the Termination for Default clause.

(2) The Contractor shall have a plan on file showing how the Contractor would replace employees who are unavailable for deployment or who need to be replaced during deployment. The Contractor shall keep this plan current and shall provide a copy to the Contracting Officer and USFK Sponsoring Agency (see USFK Reg 700-19) upon request. The plan shall—

(i) Identify all personnel who are subject to U.S. or Republic of Korea military mobilization;

(ii) Identify any exemptions thereto;

(iii) Detail how the position would be filled if the individual were mobilized; and

(iv) Identify all personnel who occupy a position that the Contracting Officer has designated as mission essential.

(i) Military clothing and protective equipment.

(1) Contractor personnel supporting a force deployed outside the United States as specified in paragraph (b)(1) of this clause are prohibited from wearing military clothing unless specifically authorized in writing by the COMUSK. If authorized to wear military clothing, contractor personnel must wear distinctive patches, arm bands, nametags, or headgear, in order to be distinguishable from military personnel, consistent with force protection measures and the Geneva Conventions.

(2) Contractor personnel may wear military-unique organizational clothing and individual equipment (OCIE) required for safety and security, such as ballistic, nuclear, biological, or chemical protective clothing.

(3) The deployment center, the Combatant Commander, or the Sponsoring Agency shall issue OCIE and shall provide training, if necessary, to ensure the safety and security of contractor personnel.

Page | 30

(4) The Contractor shall ensure that all issued OCIE is returned to the point of issue, unless otherwise directed by the Contracting Officer.

(j) Weapons.

(1) If the Contractor requests that its personnel performing in the theater of operations be authorized to carry weapons, the request shall be made through the Contracting Officer to the COMUSK. The COMUSK will determine whether to authorize in-theater contractor personnel to carry weapons and what weapons will be allowed.

(2) The Contractor shall ensure that its personnel who are authorized to carry weapons—

(i) Are adequately trained;

(ii) Are not barred from possession of a firearm by 18 U.S.C. 922; and

(iii) Adhere to all guidance and orders issued by the COMUSK regarding possession, use, safety, and accountability of weapons and ammunition.

(iv) The use of deadly force by persons subject to this clause shall be made only in self-defense, except:

(v) Persons subject to this clause who primarily provide private security are authorized to use deadly force only as defined in the terms and conditions of this contract in accordance with USFK regulations and policies (especially, USFK Regulation 190-50).

(vi) Liability for the use of any weapon by persons subject to this clause is solely the responsibility of the individual person and the contractor.

(3) Upon redeployment or revocation by the COMUSK of the Contractor’s authorization to issue firearms, the Contractor shall ensure that all Government-issued weapons and unexpended ammunition are returned as directed by the Contracting Officer.

(k) Evacuation.

(1) In the event of a non-mandatory evacuation order, unless authorized in writing by the Contracting Officer, the Contractor shall maintain personnel on location sufficient to meet obligations under this contract.

(l) Theater Specific Training. Training Requirements for IC/TR personnel shall be conducted in accordance with USFK Reg 350-2 Theater Specific Required Training for all Arriving Personnel and Units Assigned to, Rotating to, or in Temporary Duty Status to USFK.

(m) USFK Responsible Officer (RO). The USFK appointed RO will ensure all IC/TR personnel complete all applicable training as outlined in this clause.

(n) Changes. In addition to the changes otherwise authorized by the Changes clause of this contract, the Contracting Officer may, at any time, by written order identified as a change order, make changes in Government-furnished facilities, equipment, material, services, or site. Any change order issued in accordance with this paragraph shall be subject to the provisions of the Changes clause of this contract.

(o) Subcontracts. The Contractor shall incorporate the substance of this clause, including this paragraph, in all subcontracts that require subcontractor personnel to be available to deploy with or otherwise

Page | 31 provide support in the theater of operations to U.S. military forces deployed/stationed outside the United States in—

(1) Contingency operations;

(2) Humanitarian or peacekeeping operations; or

(3) Other military operations or exercises designated by the Combatant Commander.

(p) The Contracting Officer will discern any additional GFE, GFP or logistical support necessary to facilitate the performance of the enhanced requirement or necessary for the protection of contractor personnel. These items will be furnished to the Contractor at the sole discretion of the Contracting Officer and may be provided only on a reimbursable basis.

Page | 32

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 | 33

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.1.1 Objective - Task Order Management

This PWS element represents the Stakeholder Technical Integration Management and IRES Integration Management activities required to support the management of requirements of the overall TO, which includes 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 in accordance with the PWS.

• Provide status and insight on performance, to include the metrics outlined in the Quality

Assurance Surveillance Plan.

• Manage activities in accordance with the processes defined in the IRES Program Management

Plan (CDRL TO8002 C008).

• Ensure all requirements are identified, managed, validated, and verified in accordance with the contractor’s IRES Systems Engineering Master Plan.

• Ensure a common Enterprise Architecture 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 drawdown 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

WBS and IRES organization structure; significant accomplishments; customer concerns or issues;

TO risks and mitigation status; performance against the IRES contract, SE&PI, and TO SSIs.

• Identify,…