Attachment_L-3_Task_Order_001_PWS.pdf

Attachment L-3 1 Joint Enterprise Defense Infrastructure (JEDI) Cloud 2

PERFORMANCE WORK STATEMENT (PWS) 4

Task Order 001: Cloud Computing Program Office (CCPO) 6

Program Management Support 7

Updated 26 July 2018 9

1. INTRODUCTION 11

1.1 DESCRIPTION OF SERVICES 12

The resultant Task Order (TO) is being executed under the Joint Enterprise Defense 13 Infrastructure (JEDI) Cloud Indefinite Delivery/Indefinite Quantity (ID/IQ) contract. This TO is 14 for the Contractor to provide the personnel, processes, and tools necessary to effectively manage 15 JEDI Cloud within schedule, quality, and performance requirements. The Contractor shall 16 establish and maintain a formal program management organization, which shall coordinate and 17 interface with the Cloud Computing Program Office (CCPO). Interfacing with other offices 18 within the Department of Defense (DoD) is expected; however, all interactions shall be 19 coordinated through the CCPO. 20

The purpose of this PWS is to describe the performance-based services the JEDI Cloud 21 Contractor is required to deliver under performance of this TO. 22

1.2 BACKGROUND 23

The CCPO is responsible for oversight and execution of rapid adoption of cloud services across 24 DoD. CCPO’s ultimate goal is to drive evolutionary change for the acquisition and management 25 of Information Technology (IT) services in support of business and mission operations across the 26 DoD by providing access to modern, enterprise-level cloud services. The CCPO will leverage 27 public and commercial best-practices to champion the effort, minimizing barriers to accessing 28 cloud while maintaining the highest integrity and ethical standards to preserve public confidence 29 in the stewardship of Government resources. 30

CCPO is charged with managing the JEDI Cloud contract. Under this TO, the Contractor will 31 deliver a program management capability that is complementary to CCPO. Highly coordinated 32 program management capabilities between the Contractor and CCPO are critical to successful 33 execution of the JEDI Cloud contract and to optimize the contract’s capabilities in support of the 34 DoD mission. 35

2. GENERAL REQUIREMENTS 37

2.1 PLACE AND PERIOD OF PERFORMANCE 39

Work under this TO shall be primarily performed at the Contractor’s facilities for all tasks in 41 Section 3 below; however, certain tasks as identified may require meetings in the National 42 Capital Region (NCR), as defined by 10 USC § 2674(f)(2). The period of performance shall be 43 for one 12-month base year and one 12-month option year, for a total of 24 months. 44

2.2 BUSINESS RELATIONS 45

The Contractor shall successfully integrate and coordinate all activities required to execute the 46 requirements specified herein. The Contractor shall manage the timeliness, completeness, and 47 quality of the contract deliverables. The services required under this TO are not inherently 48 governmental. If the Contractor believes any actions constitute, or are perceived to constitute, 49 personal services, it shall be the Contractor's responsibility to notify the JEDI Cloud Contracting 50 Officer and Contracting Officer Representative (COR) immediately. 51

2.3 CONTRACT MANAGEMENT 52

The Contractor shall establish clear organizational lines of authority and responsibility to ensure 53 effective management of the resources assigned to this requirement. The Contractor must 54 maintain continuity between the operations at the CCPO and the Contractor's corporate offices. 55 The Contractor shall establish processes and assign appropriate resources to effectively 56 administer this contract. The Contractor shall respond to Government requests for contractual 57 actions in a timely fashion. As required in Section C2 of the ID/IQ Contract, the Contractor shall 58 have a single point of contact between the Government and Contractor personnel assigned to 59 support this TO. 60

2.4 CONTRACTOR PERSONNEL, DISCIPLINES, AND SPECIALTIES 61

An integral part of successful performance under this TO is the production of quality 62 performance requirements described in Section 3, and the responsiveness of Contractor 63 personnel in the day-to-day output of work tasks. While the end product or deliverable is vital to 64 the Contractor’s successful performance, day-to-day oversight also includes client interaction 65 and responsiveness. Accordingly, the Contractor is required to proactively maintain assigned 66 tasks and be responsive to all entities with professional business dealings related to the assigned 67 tasks. 68

The Contractor must at all times maintain an adequate workforce for the uninterrupted 69 performance of all tasks defined within this PWS. When hiring personnel, the Contractor shall 70 keep in mind that the stability and continuity of the workforce are essential. 71

3. PERFORMANCE REQUIREMENTS (TASKS) 72

3.1 General. The Contractor shall perform all tasks described in Section C2 of the contract 73 and all program management tasks in the ID/IQ contract PWS. 74

3.1.1 The Contractor shall provide a monthly Contract Progress Report (CDRL A001) 75 for overall performance under the contract and a Task Order Progress Report (CDRL A015) for 76 performance under TO 001. The Contract Progress Report shall include, but not be limited to: 77

a. Percentage of JEDI Cloud’s unclassified usage compared to the Offeror’s total 78 utilization for the following metrics: 1) Network - Volume of commercial 79 client traffic, in bytes, for public internet ingress and egress (at the logical 80 cloud boundary outside of availability zones, i.e., in and out of the CCO-81 controlled infrastructure) per month and aggregated for the duration of this 82 task order; 2) Compute - Number of physical (not virtualized) compute (CPU 83 and/or GPU) cores in use by application servers, which are defined as those 84 physical servers that host the virtualized infrastructure and platform services 85 used by end users (for example, a network router would not satisfy this 86 definition of application server); and 3) Storage - Data, in bytes, for each of 87 online, nearline, and offline averaged across the month. 88

b. Any reporting required to comply with the Monitoring Method applicable to 89 the Performance Metrics Table in the ID/IQ contract PWS. 90

c. Reporting on GFP and GFI. 91

d. Reporting required by the Quality Control Plan (CDRL A010). 92

e. Summary usage metrics. 93

f. Areas of concern. 94

3.1.2 Kickoff. The Contractor shall arrange and execute a post-award kickoff within 15 95 days after contract award in the NCR using formal materials (CDRL A016). The location 96 secured by the Contractor shall be within walking distance of a WMATA Metrorail station. This 97 event may last up to three days and may need to accommodate up to 100 people with a variety of 98 informational breakout sessions and working groups. 99

3.1.3 In-Process Reviews (IPRs). The Contractor shall arrange and execute, using formal 100 materials (CDRL A016), quarterly IPRs. IPRs are attended in person in the NCR with the CCPO, 101 unless otherwise waived by the CCPO Program Manager. Requirements of the IPR include, but 102 are not limited, overall status update; identification of any upcoming changes in offerings and 103 capabilities; specific recommendations on how to better optimize JEDI Cloud based on collected 104 data with projections on how implementation of those recommendations would improve 105 performance for that specific area; identification of areas where communication between the 106 Contractor and CCPO could be improved with recommendations on how to improve it; status of 107 and any issues around interfacing with the DoD’s provisioning tool; identification of areas of 108 concern with recommendations on how to mitigate risk; trends (overall service quality, 109 utilization, efficiency, and cost); advising on the utilization of JEDI Cloud and how it aligns to 110 the commercial trends and practices; and goal management to include recommendations and 111 status of goals as identified by the Government (if applicable); discussion of any reports 112 submitted to the CCPO required by the JEDI Cyber Security Plan during the last quarter, and any 113 agenda items provided to the Contractor within 10 days before the scheduled IPR. The 114 Contractor is responsible for providing an agenda, presentation materials, and meeting minutes 115 (CDRL A016) at the Quarterly In-Process Reviews (IPRs). 116

3.1.4 Ad Hoc Reporting/White Papers. The Contractor shall work with the CCPO to 117 satisfy ad hoc reporting needs. Delivering white papers (CDRL A012) to help inform CCPO 118 decision-making around effective implementation of JEDI Cloud. This reporting is in addition to 119 other reporting requirements mentioned herein. 120

3.1.5 Communication. The Contractor shall communicate with CCPO counterparts 121 regularly, including but not limited to Program Manager, security, technical, user engagement, 122 strategic communications, provisioning support, and contracts, and proactively raise issues that 123 may affect contract performance. 124

3.2 Security. The Contractor shall perform all tasks and submit all security deliverables 126 (CDRLs A003 and A011) necessary to provide unclassified and classified infrastructure and 127 offerings in accordance with all security requirements and timeframes required in the contract. 128 Achieving high quality security is an ongoing requirement that will require the Contractor’s 129 constant monitoring and oversight and proactive risk mitigation. 130

3.3 Small Business. Small business reporting for all TOs placed under the ID/IQ contract in 132 accordance with all applicable FAR requirements and Attachment J-10 Small Business 133 Participation Commitment Document (SBPCD) shall be submitted under TO 001 using CDRL 134 A013. Small business participation reporting to the CCPO is required for all CLINs annually; 135 however, small business participation goals are limited to those CLINs invoked in Attachment J-136 10, and is required annually. 137

3.4 Property Management. The Contractor shall provide management and reporting of 139 Government Furnished Property for all TOs placed under the ID/IQ. The Contractor shall ensure 140 its property management system is in compliance with FAR 52.245-1. In the event there are any 141 changes to the pre-approved documentation provided at time of proposal submission, the 142 Contractor shall provide updated documentation under CDRL A014, Technical Report. The 143 Contractor shall also properly handle all Government Furnished Information for all TOs placed 144 under the ID/IQ. 145

3.5 Ordering Guide. The Contractor shall deliver and maintain the Ordering Guide (CDRL 147 A008) to provide users with information and procedures to effectively place TOs against the 148 JEDI Cloud ID/IQ contract. The Ordering Guide will contain components developed by the 149 Government, such as the process within the DoD provisioning tool, which is expected to 150 constitute around 60% of the overall Ordering Guide. The Contractor will develop the content 151 for the remainder of the Ordering Guide, which will start with when a JEDI Cloud user receives 152 authorization to provision cloud offerings. The Contractor is responsible for reviewing the entire 153 Ordering Guide, including the Government-developed sections, to validate that the Guide 154 conveys a cohesive and easy-to-follow process for users. The Contractor shall address as part of 155 the Guide any specific information that users need to understand to successfully order tactical 156 edge, cloud support package, and online marketplace (including BYOL) offerings. The final 157 Ordering Guide shall be delivered 15 days after the Government provides the inputs for the 158 Government-developed sections to the Contractor. 159

3.6 Quality Control. The Contractor shall establish quality control methodologies to ensure 161 that all services for all TOs are provided in accordance with the schedule, quality, and 162 performance requirements in the contract. The Contractor shall submit a Quality Control Plan 163 (QCP) (CDRL A010) that aligns to the Quality Assurance Surveillance Plan (QASP) attached to 164 the contract at award. The Government will consider the proposed QCP of the successful 165 awardee as a basis for developing the final Government QASP attached to the contract. 166

3.7 Delivering all CDRLs to the CCPO, and to the TO ordering activities as appropriate, as 168 identified below in Section 4 IAW schedule, quality, and performance requirements. 169

4. DELIVERABLES 174

CDRL Deliverable Frequency / Date of First Submission

Medium/Format/ # of Copies

Submit To

A001 Contract Monthly Progress Report

(CMPR)

Monthly Electronic copy in Offeror’s preferred format

CCPO

A002 Transition Out Plan

As required;

Government has 15 calendar days to review, the revise and resubmit for approval five calendar days after receiving comments.

Subsequent submissions required until the Plan is approved.

Electronic copy in Offeror’s preferred format

CCPO

A003 Contract Security Management Plan

Within 30 days of contract award and then annually thereafter;

updated annually or as required to reflect necessary changes.

Electronic copy in Offeror’s preferred format

CCPO

A004 Technology Refresh Plan

Within 30 days after contract award and then semi-annually thereafter

Electronic copy in Offeror’s preferred format using Microsoft Office

CCPO

A008 Contract Ordering Guide

Within 15 days of after Government developed sections provided;

updated annually or as required to reflect necessary changes.

Electronic copy in Offeror’s preferred format using Microsoft Office

CCPO

A009 Change Management Roadmap

Within 90 days after contract award and then annually thereafter

Electronic copy in Offeror’s preferred format using Microsoft Office

CCPO

A010 Quality Control Plan

Within 30 days of contract award, then annually thereafter

Electronic copy in Offeror’s preferred format using Microsoft Office

CCPO

A011 Security Authorization Package

Various depending classification level

Electronic copy in format acceptable to the FedRAMP process

CCPO

A012 Technical Report As required Electronic copy in Offeror’s preferred format

CCPO

A013 Small Business Reporting

Annually after date of contract award

Electronic copy in Offeror’s preferred format

CCPO

A015 Task Order Monthly Progress Report

As required Electronic copy in Offeror’s preferred format

CCPO

A016 Meeting Materials Quarterly Electronic copy in Offeror’s preferred format

CCPO

Unless otherwise specified, the Government shall have fifteen business days to review and 177 provide comments to all deliverables. Any deliverables that are not commented upon within that 178 time frame are deemed approved. Offeror shall have fifteen business days to revise and resubmit 179 any deliverables that the Government provides comments upon. 180

5. TASK ORDER ADMINISTRATION 182

5.1 CONTRACTING OFFICER’S REPRESENTATIVE 184

It is emphasized only the JEDI Cloud Contracting Officer has the authority to modify the terms 186 of this TO; therefore, in no event will any understanding, agreement, modification, change order, 187 or other matter deviating from the terms of the TO or the base ID/IQ contract between the 188 Contractor and any other person be effective or binding on the Government. When/if, in the 189 opinion of the Contractor, an effort outside the existing scope of the TO is requested, the 190 Contractor shall promptly notify the JEDI Cloud Contracting Officer in writing. No action shall 191 be taken by the Contractor unless the JEDI Cloud Contracting Officer has issued a modification. 192

5.2 GOVERNMENT FURNISHED PROPERTY 194

No Government Furnished Property is required for this TO. However, reporting of the GFP for 195 all TOs placed under the ID/IQ is required under this TO. 196

5.3 SECURITY 197

All tasks must be conducted in full compliance with all security requirements of this contract, 198 including the DD Form 254 attached to this TO. 199