HQ0034-18-R-0077_0001.pdf

JEDI Cloud RFP # HQ0034-18-R-0077_0001

JEDI Cloud Synopsis/Solicitation Page 1

COMBINED SYNOPSIS/SOLICITATION FOR COMMERCIAL ITEMS 1

General Information RFP 2 Document Type: Combined Synopsis/Solicitation (IAW FAR 12.603) RFP Solicitation Number: HQ0034-18-R-0077_0001 Post Date: August 23, 2018 Classification Code: R -- Professional, Administrative, and Management Support Services Set Aside: Full and Open Competition NAICS Code: 518210 – Data Processing, Hosting, and Related Services Contracting Office Address 5 Washington Headquarters Services (WHS), Acquisition Directorate (AD) 7 4800 Mark Center Drive, Suite 09F09, Alexandria, VA 22350 8 Description 10 This is a combined synopsis/solicitation for commercial items prepared in accordance with the format 12 in Federal Acquisition Regulation (FAR) Subpart 12.6, “Streamlined Procedures for Evaluation and 13 Solicitation for Commercial Items,” as supplemented with additional information included in this 14 notice. This announcement constitutes the only solicitation. All non-price factors will be evaluated in 15 accordance with (IAW) FAR Subpart 12.602 “Streamlined Evaluation of Offers”. The price factor 16 will be evaluated IAW FAR Subpart 12.209. 17 This solicitation is a Request for Proposal (RFP) for Joint Enterprise Defense Infrastructure (JEDI) 19 Cloud for the Department of Defense (DoD). This RFP document and incorporated provisions and 20 clauses are those in effect through Federal Acquisition Circular 2005-97 (Effective: 24 January 2018; 21 updated with Class Deviation 2018-o0007) and DFARS Publication Notice 20180504 (Effective 04 22 May 2018). There is no assigned Defense Priorities and Allocations System (DPAS) rating for this 23 requirement. 24 The associated North American Industrial Classification System (NAICS) code for this procurement 26 is 518210 – “Data Processing, Hosting, and Related Services”, with a small business size standard of 27 $32.5M. 28

JEDI Cloud Synopsis/Solicitation Page 2

SECTION B: SUPPLIES OR SERVICES AND PRICES

Section B1: Schedule of Services – ID/IQ CLIN Structure

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 As Ordered Each Priced by Catalog

Unclassified IaaS and PaaS

FFP

Unclassified Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) offerings.

NET AMT

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0002 As Ordered Each Priced by Catalog

Classified IaaS and PaaS

FFP

Classified IaaS and PaaS offerings

0003 As Ordered Each Priced by Catalog

Unclassified Cloud Support Package

FFP

Unclassified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package may include training services, materials, and documentation for available services. This is not a time-and-materials or labor-hour based

CLIN.

JEDI Cloud Synopsis/Solicitation Page 3

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0004 As Ordered Each Priced by Catalog

Classified Cloud Support Package

FFP

Classified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package may include training services, materials, and documentation for available services. This is not a time-and-materials or labor-hour based CLIN.

0005 As Ordered Each To Be Completed by Offeror

Portability Plan

Deliver plan in accordance with CDRL A007.

Only the Cloud Computing Program Office (CCPO) has authority to order under this CLIN.

JEDI Cloud Synopsis/Solicitation Page 4

0006 As Ordered Each To Be Completed by

Portability Test

Demonstrate portability of data and applications to other hosting environments. Only the CCPO has authority to order under this CLIN.

0007 24 Each To Be Completed by

To Be Completed by Offeror

CCPO PM Support

FFP

CCPO Program Management (PM) CLIN will be performed per Section C2.

Only the CCPO has authority to order under this CLIN. For the purpose of this CLIN, the unit of issue “EACH” equates to a month of services.

1001 As Ordered Each Priced by Catalog

OPTION Unclassified IaaS and PaaS

Unclassified IaaS and PaaS offerings

JEDI Cloud Synopsis/Solicitation Page 5

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

1002 As Ordered Each Priced by Catalog

OPTION Classified IaaS and PaaS

1003 As Ordered Each Priced by Catalog

OPTION Unclassified Cloud Support Package

FFP

Unclassified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package may include training services, materials, and documentation

1004 As Ordered Each Priced by Catalog

OPTION Classified Cloud Support Package

FFP

Classified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package

JEDI Cloud Synopsis/Solicitation Page 6

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

1005 As Ordered Each To Be Completed by

OPTION Portability Plan

Deliver plan in accordance with CDRL A007.

Only the CCPO has the authority to order under this CLIN.

1006 As Ordered Each To Be Completed by

OPTION Portability Test environments. Only the CCPO has the authority to order under this CLIN.

1007 36 Each To Be Completed by

To Be Completed by Offeror

OPTION CCPO PM Support

FFP

CLIN will be performed IAW Section C2.

Only the CCPO has the authority to order under this CLIN. For the purpose of this CLIN, the unit of issue “EACH” equates to a month of services.

JEDI Cloud Synopsis/Solicitation Page 7

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

2001 As Ordered Each Priced by Catalog

OPTION Unclassified IaaS and PaaS

2002 As Ordered Each Priced by Catalog

OPTION Classified IaaS and PaaS

JEDI Cloud Synopsis/Solicitation Page 8

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

2003 As Ordered Each Priced by Catalog

OPTION Unclassified Cloud Support Package

FFP

Unclassified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package may include training services, materials, and documentation

2004 As Ordered Each Priced by Catalog

OPTION Classified Cloud Support Package

FFP

Classified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package

JEDI Cloud Synopsis/Solicitation Page 9

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

2005 As Ordered Each To be Completed by

2006 As Ordered Each To be Completed by

2007 36 Each To Be Completed by

To Be Completed by Offeror

OPTION CCPO PM Support

FFP

CLIN will be performed IAW Section C2 Only the CCPO has the authority to order under this CLIN. For the purposes of this CLIN, the unit of issue “EACH” equates to a month of services.

JEDI Cloud Synopsis/Solicitation Page 10

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

3001 As Ordered Each Priced by Catalog

OPTION Unclassified IaaS and PaaS

3002 As Ordered Each Priced by Catalog

OPTION Classified IaaS and PaaS

JEDI Cloud Synopsis/Solicitation Page 11

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

3003 As Ordered Each Priced by Catalog

OPTION Unclassified Cloud Support Package

FFP

Unclassified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package may include training services, materials, and documentation

3004 As Ordered Each Priced by Catalog

OPTION Classified Cloud Support Package

FFP

Classified offerings of catalog support to advise and assist with architecture, usage, provisioning, and configuration of IaaS and PaaS, to include homefront to the tactical edge. Package services may advise and assist with integration, aggregation, orchestration, and troubleshooting of cloud services. Package

JEDI Cloud Synopsis/Solicitation Page 12

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

3005 As Ordered Each To be Completed by

3006 As Ordered Each To be Completed by

3007 24 Each To Be Completed by

To Be Completed by Offeror

OPTION CCPO PM Support

FFP

CLIN will be performed IAW Section C2 Only the CCPO has the authority to order under this CLIN. For the purposes of this CLIN, the unit of issue “EACH” equates to a month of services.

JEDI Cloud Synopsis/Solicitation Page 13

Section B2: Maximum Contract Limit and Minimum Contract Guarantee 33

1. The successful awardee’s fixed unit price information (CLIN x005 Portability Plan, x006 34 Portability Test, and x007 CCPO PM Support) and proposed catalog offerings will be incorporated 35 into the resultant Indefinite-Delivery, Indefinite-Quantity (ID/IQ) contract and will serve as the basis 36 for establishing overall task order (TO) pricing for the duration of the ID/IQ. 37

2. Maximum. The maximum, as that term is used in FAR clause 52.216-22, is 38 $10,000,000,000.00. Hence, the cumulative amount of all TOs issued under this contract shall not 39 exceed $10,000,000,000.00. 40

3. Minimum. The minimum guaranteed award amount for the JEDI Cloud ID/IQ Contract is 41 $1,000,000.00. The exercise of any option does not re-establish the contract minimum guarantee. 42

4. The Government has no obligation to issue TOs under the resultant ID/IQ contract beyond 43 the amount specified in paragraph three. 44

Section B3: Task Order Contract Types 45

This single award ID/IQ contract allows for the placement of TOs by DoD warranted Contracting 46 Officers. All TOs will be firm-fixed price. 47 Section B4: Travel 49 Travel is not anticipated. However, if the JEDI Cloud Contracting Officer later determines that travel 51 is necessary for TO performance under this ID/IQ, the contract will be modified accordingly. 52 Section B5: Security 54 All tasks in support of JEDI Cloud must be conducted IAW Attachment J-6, JEDI Cloud Cyber 56 Security Plan; Attachment J-7, DD Form 254, DoD Contract Security Classification Specification for 57 ID/IQ; and other security requirements in the contract. Future TO DD Form 254s are anticipated to be 58 identical to Attachment J-7 with the exception of Block 16, Certification and Signature, and Block 17, 59 Required Distribution. Each TO ordering activity will complete Blocks 16 and 17 as appropriate. 60

SECTION C: DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK 62

Section C1: Performance Work Statement 63

ID/IQ: The Offeror’s Performance Work Statement (PWS), proposed in response to the 64 Government’s Attachment L-1 JEDI Cloud Statement of Objectives (SOO), will be incorporated into 65 the contract as Attachment J-2. The Offeror shall meet all requirements of Attachment J-6, JEDI 66 Cloud Cyber Security Plan. In the event of a conflict between the JEDI Cloud Cyber Security Plan 67 and the PWS, the JEDI Cloud Cyber Security Plan takes precedence over the PWS. For 68 administration purposes both the PWS and the JEDI Cloud Cyber Security Plan are listed as 69 attachments in Section J. However, for the purpose of FAR 52.212-4(s), they shall be deemed 70 incorporated into Section C1. 71

All Performance Metrics listed in the PWS shall apply to all TOs unless otherwise noted. Migration 72 services are outside the scope of this contract. 73

JEDI Cloud Synopsis/Solicitation Page 14

Section C2: Program Management 74

1. The Contractor shall provide overarching program management personnel, processes, and 75 tools under CLINs x007 necessary to manage and oversee all contract activities for the duration of the 76 ID/IQ within schedule, quality, and performance requirements. The Contractor shall establish and 77 maintain a formal program management organization, which shall coordinate and interface with the 78 CCPO. The Contractor shall appoint a Program Manager (PM) and Deputy PM empowered to make 79 program and project level decisions and commit resources necessary to successfully execute courses 80 of action within scope of this contract. Two key functions of the Contractor’s program management 81 support will be facilitating the timely authentication and authorization of JEDI Cloud infrastructure 82 and offerings at all classification levels and coordinating successful integration of the DoD’s 83 provisioning tool. The PM and Deputy PM shall have sufficient expertise and authority to execute the 84 following responsibilities as the authorized official: (a) serve as the official central point of contact 85 and interface between the Contractor and the CCPO PM, (b) be available as needed for CCPO 86 interaction, and (c) monitor and report on contract status (CDRL A001), Service Level Agreements 87 (SLAs), and compliance with all contract requirements. 88

2. The Government will use the Quality Assurance Plan (QASP) as one mechanism to oversee 90 Contractor performance. A majority of TOs are unlikely to have TO-level QASPs; however, the 91 Government retains the right to implement QASPs at the TO level. The Contractor’s Quality Control 92 Plan (QCP) (CDRL A010) will establish methodologies by which the Contractor will meet or exceed 93 schedule, quality, and performance requirements. 94

3. The Contractor shall implement a Small Business Participation Commitment Document 96 (Attachment J-10). This will assist in the development of capabilities of small businesses and provide 97 a maximum practicable opportunity to participate in efficient contract performance for small 98 businesses. The Contractor shall report on small business participation in the Small Business 99 Reporting (CDRL A013). 100 Section C3: Transition Out 102

1. Transition Out Plan: When requested by the JEDI Cloud Contracting Officer, the 103 Contractor will have up to 60 days to provide a Transition Out Plan (CDRL A002). The purpose of 104 the Transition Out Plan is to explain to the CCPO the procedures necessary to transition either all or a 105 part of the services under this contract, as directed by the Government. The Transition Out Plan shall 106 describe detailed recommendations for maintaining continuity of services and preventing degradation 107 of services during the transition period. The Transition Out Plan shall provide recommendations on 108 how account holders may efficiently extract their application(s) and user data in a manner that is 109 consistent with the Portability Plan. The Transition Out Plan shall address the unclassified 110 environment, classified environment, and tactical edge offerings separately. Further, the Contractor 111 shall explain the process to provide knowledge transfer to the CCPO and include job shadowing for 112 up to 30 days, training, and other activities in order to successfully transition the environment to the 113 new hosting environment. The Transition Out Plan shall include a process for identifying and 114 destroying all classified infrastructure, materials, or information IAW CCPO instructions and the 115 contract’s security requirements. 116

2. Transition Out Execution: The Contractor shall perform all activities as described in the 117 approved Transition Out Plan, excluding extraction of applications and data, which is a user 118 responsibility. The Contractor shall exercise its best efforts and cooperation to effect an orderly and 119 efficient transition to a successor. The Contractor shall deliver all technical data, computer software, 120 and computer software documentation generated in the performance of this contract, to which the 121 Government has rights. The Contractor shall execute knowledge transfer in accordance with the 122 Transition Out Plan. When directed, the Contractor shall purge all unclassified materials and 123

JEDI Cloud Synopsis/Solicitation Page 15 information and purge or destroy, as appropriate, all classified infrastructure, materials, and 124 information IAW the Transition Out Plan. The Contractor shall return any Government Furnished 125 Property (GFP) or Government Furnished Information. 126 Section C4: Contractor Control of Certain Parts of JEDI Cloud 128

1. The legally enforceable ability for the prime contractor to maintain control over certain parts 129 of JEDI Cloud is critical to meeting the security requirements of this contract. The Government 130 expects that it will need to direct the Contractor to affect alterations or configuration changes to JEDI 131 Cloud for purposes of addressing critical security vulnerabilities. The Contractor must be able to 132 decisively and rapidly respond in the interests of national defense. For the purpose of this section, the 133 direction concerning critical security vulnerabilities may come from the DoD CIO in coordination 134 with the JEDI Cloud Contracting Officer and CCPO PM. 135

2. For purpose of this section, “rapidly” means in 8 hours or less from Government notification. 136 All Government-directed alterations or configurations changes will be agreed upon by both the 137 Government and the Contractor prior to implementation. 138

3. Depending on the urgency of the circumstances, the agreed-to alteration or configuration 139 change may initially be achieved by oral direction from the JEDI Cloud Contracting Officer, but to 140 the extent it is deemed a “change” as defined by FAR clause 52.212-4(c), the change will be 141 subsequently reflected in a written agreement of the parties as soon as practicable. 142

4. Throughout the entire period of performance, the Contractor shall maintain control, as 143 defined in this section, over the following parts of JEDI Cloud for both the unclassified and classified 144 environments: 145

a. Underlying hardware infrastructure, including networking components within the 146 data centers; 147

b. Underlying software layer, including the hypervisor and networking components; 148

c. Software platform offerings (excluding third-party marketplace offerings); and 149

d. Hardware and software components of all points of presence. 150

5. “Control” means that, for the part of JEDI Cloud in paragraph 1 above, the prime contractor 151 either: 152

a. Is the owner, as defined in this section, paragraph 6, as evidenced by self-153 certification. The Government may request additional documentation to prove 154 ownership at any time and with any frequency throughout the period of performance; 155 or 156

b. Has a bilaterally signed agreement (Control Agreement) that is binding for at least 157 364 days following each respective ID/IQ ordering period with the owner granting 158 the prime contractor the following rights: 159

i. Unrestricted physical access; and 160

ii. An ability to rapidly affect changes to the owned parts. 161

c. In circumstances where the prime contractor does not have a Control Agreement that 162 covers the required period of time, the prime contractor must have a signed letter 163 from the Owner stating that the Owner agrees to provide the rights in paragraph b.i 164 and b.ii to the prime contractor when the next bilaterally signed agreement is 165 negotiated. This paragraph is intended to accommodate situations where the term of a 166 lease agreement that otherwise meets the requirements of paragraph b will end sooner 167 than the prescribed period of time. 168

d. Any Control Agreement(s) may not be terminated by the Owner without at least 120 169

JEDI Cloud Synopsis/Solicitation Page 16 days notice to the Government. The Contractor shall make a good faith effort to 170 modify all existing Control Agreement(s) no later than 180 days after award, to 171 include a provision that the Agreement may not be terminated by the Owner without 172 at least 120 days notice to the Government. At any time, the JEDI Cloud Contracting 173 Officer may request confirmation that the Control Agreement has not been altered to 174 conflict with Section C4 or terminated. 175

6. “Owner” means that, for the parts listed in paragraph 1, the entity has a legally enforceable 176 claim or title, which includes the rights listed in sub-paragraphs 5.b.i and 5.b.ii. The owner must have 177 a legally binding and recorded document evidencing ownership. 178

SECTION D: PACKAGING AND MARKING 180

Packaging and Marking Requirements will be delineated in individual TOs. 182

SECTION E: INSPECTION AND ACCEPTANCE TERMS 184

Supplies/services will be inspected/accepted at: 186

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government

0002 Destination Government Destination Government

0003 Destination Government Destination Government

0004 Destination Government Destination Government

0005 Destination Government Destination Government

0006 Destination Government Destination Government

0007 Destination Government Destination Government

1001 Destination Government Destination Government

1002 Destination Government Destination Government

1003 Destination Government Destination Government

1004 Destination Government Destination Government

1005 Destination Government Destination Government

JEDI Cloud Synopsis/Solicitation Page 17

1006 Destination Government Destination Government

1007 Destination Government Destination Government

2001 Destination Government Destination Government

2002 Destination Government Destination Government

2003 Destination Government Destination Government

2004 Destination Government Destination Government

2005 Destination Government Destination Government

2006 Destination Government Destination Government

Destination

Destination

Destination

Destination

Destination

Destination

Destination

Destination

Government

Government

Government

Government

Government

Government

Government

Destination

Destination

Destination

Destination

Destination

Destination

Destination

Destination

Government

Government

Government

Government

Government

Government

SECTION F: PERFORMANCE 188

Section F1: Contract Period of Performance / Ordering Periods 189

The Period of Performance (PoP) of the resulting ID/IQ contract is structured as one continuous two-190 year base ordering period, two continuous three-year option ordering periods, and one continuous 191 two-year option ordering period for a potential total of 10 years. After the ID/IQ Ordering PoP 192 expires, the ID/IQ terms and conditions remain effective until performance under the final TO is 193 completed and shall govern the active TOs to the same extent as if their periods of performance were 194 active during the requisite ID/IQ ordering period. 195 The ordering period structure for the resulting ID/IQ contract is detailed below (with anticipated 197 timeframes): 198

JEDI Cloud Synopsis/Solicitation Page 18

Base Ordering Period (2 years) April 17, 2019 - April 16, 2021

Option Ordering Period 1 (3 years) April 17, 2021 - April 16, 2024

Option Ordering Period 2 (3 years)

Option Ordering Period 3 (2 years)

April 17, 2024 - April 16, 2027

April 17, 2027 - April 16, 2029

Section F2: Task Order Period of Performance 201

1. Under no circumstances may a new TO be placed under the ID/IQ if the contract is 203 terminated or has expired; and 204

2. From the date the TO is placed, the PoP, inclusive of options, may only exceed one year 205 beyond the applicable PoP of the ID/IQ. 206

Section F3: Place of Performance 208 The services to be provided under the ID/IQ contract shall be accomplished at the locations identified 210 in the TOs and may necessitate effort in the Contiguous United States (CONUS) and Outside the 211

CONUS (OCONUS). 212

Section F4: Contractor Performance Evaluation 214 Interim and final evaluations of the Contractor performance will be prepared on the ID/IQ contract 216 and on each resulting TO IAW FAR Subpart 42.15 and DoD Class Deviation 2013-O0018 that has a 217 total value above $1,000,0000. The final performance evaluation will be prepared at the time of 218 contract completion. In addition to the final evaluation, interim evaluation(s) will be prepared 219 annually and prior to exercising an option. 220 Interim and final evaluations will be provided to the Contractor as soon as practicable after 222 completion of the evaluation. The Contractor will be permitted 30 days to review the document and 223 either submit additional information or a rebutting statement. If agreement cannot be reached 224 between the parties, the matter will be referred to an individual one level above the Contracting 225 Officer, whose decision will be final. 226 Copies of the evaluations, Contractor responses, and review comments, if any, will be retained as part 228 of the contract file, and may be used to support future award decisions. 229 Contractors may access evaluations through a secure Web site for review and comment at the 231 following address: 232 https://www.cpars.gov 234 Section F5: Government Furnished Property 236 The following GFP will be issued under this contract: 238

1. Type 1 Cryptography Devices 239

2. Encryption Hardware 240 Section F6: Organizational Conflict of Interest (OCI) 242

JEDI Cloud Synopsis/Solicitation Page 19

During the period of performance, the Contractor shall notify the Government if any potential or 244 actual OCI, as described in FAR Subpart 9.5, exists for this contract for itself or its subcontractors. If 245 the Contractor believes that an actual or perceived OCI does exist on this contract, the Contractor 246 shall submit an OCI Mitigation Plan, explaining in detail how the OCI will be mitigated and/or 247 avoided. 248 Section F7: Method of Ordering 250 All DoD Contracting Offices and Ordering Activities are authorized to place TOs under the JEDI 252 Cloud ID/IQ contract IAW their delegated contracting authority. Ordering Contracting Officers 253 (OCOs) may issue TOs for services subject to their respective contracting warrant limitations. OCOs 254 have no authority to modify, add, or delete any terms and/or conditions in the base ID/IQ contract. 255 JEDI Cloud ID/IQ contract terms and conditions supersede TO special instructions, terms and/or 256 conditions where they may otherwise conflict. 257

Section F8: Task Order Performance 259 At a minimum, the following paragraphs shall be applicable to all TOs issued under this contract, 261 unless otherwise specified in an individual TO. 262

1. The Contractor shall, IAW the terms and conditions set forth hereafter, execute all activities 264 necessary and incidental to the completion of the contractual effort. 265

2. When the Contractor encounters difficulty in meeting performance requirements, or 266 anticipates difficulty in complying with the contract delivery schedule or date, it shall immediately 267 notify the OCO and JEDI Cloud Contracting Officer in writing giving pertinent details; provided, 268 however, that this data shall be informational only in character and that this provision shall not be 269 construed as a waiver by the Government of any delivery schedule or any rights or remedies provided 270 by law or under this contract. 271 Section F9: Task Order Administration 273

1. Each Ordering Activity is responsible for administration of its own TOs. JEDI Cloud ID/IQ 275 contract terms and conditions supersede TO special instructions, terms, and/or conditions where they 276 may otherwise conflict. Requests for deviations or modification of the basic contract must be 277 submitted to the JEDI Cloud Contracting Officer. Terminations of TOs shall be issued by the 278 Ordering Activity. The CCPO PM shall be notified of any terminations. 279

2. A Contracting Officer Representative shall be appointed for each TO IAW the instruction of the 281 Ordering Activity. 282 Section F10: Task Order Procedures 284 Specific instructions on how to place TOs against this ID/IQ will be provided in the ordering guide 286

(CDRL A008). 287

Section F11: Clause(s) 289 The following clause(s) are included by reference: 291 52.242-17 Government Delay Of Work APR 1984 293

JEDI Cloud Synopsis/Solicitation Page 20

SECTION G: CONTRACT ADMINISTRATION DATA 296

Section G1: Clauses Incorporated By Full Text 298

252.201-9000 WHS/AD LOCAL CLAUSE: CONTRACTING OFFICER’S 300

REPRESENTATIVE (COR) (MAR 2015) 301

(a) The Contracting Officer’s Representative (COR) is a representative of the Government with 303 limited authority who has been designated in writing by the Contracting Officer to provide technical 304 direction, clarification, and guidance with respect to existing specifications and performance work 305 statement/statement of work/statement of objectives, as established in the contract. The COR also 306 monitors the progress and quality of the Contractor’s performance for payment purposes. The COR 307 shall promptly report Contractor performance discrepancies and suggested corrective actions to the 308 Contracting Officer for resolution. 309

(b) The COR is not authorized to take any direct or indirect actions or make any commitments that 311 will result in changes to price, quantity, quality, schedule, place of performance, delivery or any other 312 terms or conditions of the written contract. 313

(c) The Contractor is responsible for promptly providing written notification to the Contracting 315 Officer if it believes the COR has requested or directed any change to the existing contract. No action 316 shall be taken by the Contractor for any proposed change to the existing contract. No action shall be 317 taken by the Contractor for any proposed change to the contract until the Contracting Officer has 318 issued a written directive or a written modification to the contract. The Government will not accept 319 and is not liable for any alleged change to the contract unless the change is included in a written 320 contract modification or directive signed by the Contracting Officer. 321

(d) COR authority is not delegable. 323

(e) The COR for this contract is: Specified at time of award in the COR Designation Memorandum. 325 (end of clause) 327

252.204-7006 BILLING INSTRUCTIONS (OCT 2005) 329

When submitting a request for payment, the Contractor shall— 331

(a) Identify the contract line item(s) on the payment request that reasonably reflect contract work 332 performance; and 333

(b) Separately identify a payment amount for each contract line item included in the payment request. 334

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013) 336

(a) Definitions. As used in this clause-- 338 Department of Defense Activity Address Code (DoDAAC) is a six position code that uniquely 340 identifies a unit, activity, or organization. 341 Document type means the type of payment request or receiving report available for creation in Wide 343 Area WorkFlow (WAWF). 344 Local processing office (LPO) is the office responsible for payment certification when payment 346 certification is done external to the entitlement system. 347

JEDI Cloud Synopsis/Solicitation Page 21

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment 349 requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission 350 of Payment Requests and Receiving Reports. 351

(c) WAWF access. To access WAWF, the Contractor shall-- 353

(1) Have a designated electronic business point of contact in the System for Award Management at 355 https://www.acquisition.gov; and 356

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-358 registration available at this Web site. 359

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-361 Based Training Course and use the Practice Training Site before submitting payment requests through 362 WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page 363 at https://wawf.eb.mil/. 364

(e) WAWF methods of document submission. Document submissions may be via Web entry, 366 Electronic Data Interchange, or File Transfer Protocol. 367

(f) WAWF payment instructions. The Contractor must use the following information when 369 submitting payment requests and receiving reports in WAWF for this contract/order: 370

(1) Document type. The Contractor shall use the following document type(s). 372 2n1 Services 374 (Contracting Officer: Insert applicable document type(s). Note: If a “Combo” document type is 376 identified but not supportable by the Contractor's business systems, an “Invoice” (stand-alone) and 377 “Receiving Report” (stand-alone) document type may be used instead.) 378

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance 380 location(s) in WAWF, as specified by the contracting officer. 381 Inspect/Accept: TDB 383

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only 385 to fill in applicable fields in WAWF when creating payment requests and receiving reports in the 386 system. 387 Routing Data Table to be populated for individual TOs 389 -------------------------------------------------------------------------------------------- 390 Field Name in WAWF Data to be entered in WAWF 391 -------------------------------------------------------------------------------------------- 392 Pay Official DoDAAC 393 Issue By DoDAAC 394 Admin DoDAAC 395 Inspect By DoDAAC 396 Ship To Code 397 Ship From Code 398 Mark For Code 399 Service Approver (DoDAAC) 400

JEDI Cloud Synopsis/Solicitation Page 22

Service Acceptor (DoDAAC) 401 Accept at Other DoDAAC 402 LPO DoDAAC 403 DCAA Auditor DoDAAC 404 Other DoDAAC(s) 405 -------------------------------------------------------------------------------------------- 406

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request 409 includes appropriate contract line item and subline item descriptions of the work performed or 410 supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up 411 documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment 412 request. 413

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the 415 “Send Additional Email Notifications” field of WAWF once a document is submitted in the system. 416

TDB 418

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in 420 WAWF from the following contracting activity's WAWF point of contact. 421

TBD 423

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988. 425 (End of clause) 427

SECTION H: SPECIAL CONTRACT REQUIREMENTS 430

The Contractor shall flowdown any Section H clauses that specifically require flowdown 432 notwithstanding the language in (b)(1) of 52.212-5 CONTRACT TERMS AND CONDITIONS 433

REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS 434

(DEVIATION 2013-O0019) (SEP 2013). 435

Section H1: Government Data 437

1. The Government reserves all rights, title, and interest (including all intellectual property and 439 proprietary rights) in and to: a) any computer software (including machine images and databases) or 440 data (including text, audio, video, and images) that the Government transfers to, develops in, or 441 generates in JEDI Cloud for processing, storage, or hosting; b) any computational results or data 442 derived from the use of JEDI Cloud services; and c) any JEDI Cloud account information. 443

2. The Contractor may not prevent or otherwise impede JEDI Cloud users from exporting any 446 items under paragraph 1, and/or any associated databases, object and file storage, system 447 configurations, cloud activity logs, and network configurations. Within 30 days of expiration of the 448 contract, the Contractor shall destroy any items under paragraph 1 that remain hosted in JEDI Cloud 449 or are in the possession or control of the Contractor. 450

3. Any service usage data associated with JEDI Cloud users may be used for purposes of 452 providing or improving services under the contract. Such service usage data may not be sold to third 453

JEDI Cloud Synopsis/Solicitation Page 23 parties. Under no circumstances may the Contractor disclose JEDI Cloud account or workspace 454 information to third parties unless those third parties are approved subcontractors under the contract 455 and such disclosure is necessary for contract performance. 456

4. Before reusing unclassified tactical edge devices for a non-JEDI user, the Contractor may be 458 required to purge the storage media IAW Attachment J-6, JEDI Cloud Cyber Security Plan and any 459 specific instructions included in a TO. Unless specifically directed by the CCPO to retain and 460 preserve particular unclassified infrastructure and/or media, the Contractor may destroy unclassified 461 infrastructure and/or media IAW Attachment J-6, JEDI Cloud Cyber Security Plan and any specific 462 instructions included in a TO. 463

5. The Contractor is required to obtain CCPO approval prior to allowing non-JEDI tenants to 465 use classified JEDI Cloud infrastructure. The Contractor is prohibited from reusing classified 466 infrastructure at a different classification level from which the infrastructure has been accredited 467 without CCPO approval; the Contractor is prohibited from physically transferring any physical 468 classified infrastructure to a non-JEDI user. The Contractor may be required to purge classified 469 storage media and/or destroy classified infrastructure IAW Attachment J-6, JEDI Cloud Cyber 470 Security Plan and any specific instructions included in a TO. Unless specifically directed by the 471 CCPO to retain and preserve particular classified infrastructure and/or media, the Contractor may 472 destroy classified infrastructure and/or media IAW Attachment J-6, JEDI Cloud Cyber Security Plan 473 and any specific instructions included in a TO. 474 Section H2: New Services 476

1. Subsequent to award, when new (including improved) IaaS, PaaS, or Cloud Support Package 478 services are made publicly available to the commercial marketplace in the continental United States 479 (CONUS) and those services are not already listed in the JEDI Cloud catalogs in Attachment J-1: 480 Price Catalogs, the Contractor must immediately (no later than 5 calendar days) notify the JEDI 481 Cloud Contracting Officer for incorporation of the new services into the contract in accordance with 482 the Performance Work Statement. At its discretion, the Contractor may also seek to incorporate new 483 services into the contract in advance of availability to the commercial marketplace. The JEDI Cloud 484 Contracting Officer must approve incorporation of any new services into the contract. 485

2. Any discounts, premiums, or fees in Attachment J-3: Contractor Discounts, Premiums, and 486 Fees shall equally apply to new services, unless specifically negotiated otherwise. 487

3. The price incorporated into the JEDI Cloud catalog for new unclassified services shall not be 488 higher than the price that is publicly-available in the commercial marketplace in CONUS, plus any 489 applicable discounts, premiums or fees pursuant to paragraph 2. 490

a. New services that are proposed to be incorporated into the contract in advance of 491 availability to the commercial marketplace may potentially be considered a 492 noncommercial item. The JEDI Cloud Contracting Officer will make a fact specific 493 commerciality determination. If the new service is not a commercial item and no 494 other exception or waiver applies, the JEDI Cloud Contracting Officer may require 495 certified cost and pricing data or other than certified cost and pricing data under FAR 496 Subpart 15.4 to make a fair and reasonable price determination. 497

i. If there are any new fees associated with a new service that is proposed to be 498 incorporated into the contract in advance of availability to the commercial 499 marketplace, the new proposed fee must be provided to the JEDI Cloud 500 Contracting Officer for review and, if appropriate, approval and 501 incorporation into the contract. 502

JEDI Cloud Synopsis/Solicitation Page 24

4. The price incorporated into the JEDI Cloud catalog for new classified services may include a 503 price premium as compared to unclassified services because of the additional security requirements. 504

a. The allowable classified price premium for new services for the entire remaining 505 period of performance is the lesser expensive premium among the following: 506

i. The price premium applicable to the most comparable classified service, as 507 compared to the price for the comparable unclassified service, at the time of 508 contract award; or 509

ii. The following classified price premium as completed by the contractor as 510 part of its proposal: to be completed by Offeror; or 511

iii. The price premium proposed by the Contractor at the time the new service is 512 made available to the Government. 513

5. If a service that is ordered pursuant to a TO in the Attachment J-1, Price Catalogs is 515 eliminated from the Contractor’s publicly-available commercial catalog, the Contractor shall offer the 516 Government replacement service(s) with substantially similar functionality as, and at a price no 517 higher than, the service being eliminated for the entire remaining PoP of the applicable TO(s). The 518 replacement service(s) shall be made available at least 30 days before the service is suspended. Under 519 no circumstances may the replacement service(s) require purchase of additional services that causes 520 the price to be higher than the eliminated service in order to achieve the same functionality of the 521 eliminated service. 522

6. When the JEDI Cloud Contracting Officer incorporates the new service into the Attachment 523 J-1, Price Catalogs and/or Attachment J-3: Contractor Discounts, Premiums, and Fees, the Contractor 524 shall update the listing of services and corresponding prices in the online pricing calculator and 525 application programming interfaces (APIs) for JEDI Cloud within 24 hours. 526 Section H3: Price Changes 528

1. Within 45 calendar days of the Contractor lowering prices in its publicly-available 530 commercial catalog in CONUS, the Contractor shall submit a revised catalog for incorporation into 531 Attachment J-1, Price Catalogs as follows: 532

a. For unclassified services, the revised catalog price shall match the commercially 533 lower price. 534

b. For classified services, the revised catalog price shall be lowered by to be completed 535 by Offeror percentage of the net value difference for the newly lowered rate for the 536 unclassified service. 537

i. For example, if an unclassified service is lowered from $1.00 to $0.75, 538 resulting in a net value difference of $0.25, and the percentage in paragraph 539

(b) above is 100%, then the classified service would also be lowered by 540 $0.25; however, if the percentage in paragraph (b) above is 50% then the 541 classified service would be lowered by $0.125. 542

2. Any discounts, premiums, or fees in Attachment J-3: Contractor Discounts, Premiums, and 543 Fees shall equally apply to any services with price changes, unless specifically negotiated otherwise. 544

3. The Contractor may offer new or additional discounts at any time to be incorporated into 545 Attachment J-3: Contractor Discounts, Premiums, and Fees only upon JEDI Cloud Contracting 546 Officer approval. 547

4. When the JEDI Cloud Contracting Officer incorporates the revised price into the Attachment 548 J-1, Price Catalogs and/or Attachment J-3: Contractor Discounts, Premiums, and Fees, as appropriate, 549

JEDI Cloud Synopsis/Solicitation Page 25 the Contractor shall update the listing of services and corresponding prices in the online pricing 550 calculator and APIs for JEDI Cloud within 24 hours. 551 Section H4: Additional Security 553

1. Security requirements is one material condition of this contract. This contract and any 555 resulting TOs shall be subject to immediate termination for cause, without the requirement for a cure 556 notice, when it has been determined by the JEDI Cloud Contracting Officer that a failure to fully 557 comply with the security requirements of this contract resulted from the willful misconduct or lack of 558 good faith on the part of any one of the Contractor's directors or officers, or on the part of any of the 559 managers, superintendents, or equivalent representatives of the Contractor who have supervision or 560 direction of: 561

a. All or substantially all of the Contractor's Cloud business, or 563

b. All or substantially all of the Contractor's operations at any one plant or separate 564 location in which this contract is being performed, or 565

c. A separate and complete major industrial operation in connection with the 566 performance of this contract. 567

2. The legally enforceable ability for the prime contractor to maintain control over certain parts 569 of JEDI Cloud is another material condition of this contract. This contract and any resulting TOs shall 570 be subject to immediate termination for cause, without the requirement for a cure notice, when it has 571 been determined by the JEDI Cloud Contracting Officer that a failure to fully comply with the 572 security requirements of this contract resulted from the lack of control required by Section C4. 573 Section H5: Issuance of Subcontracts 575

1. The Contractor shall provide to the JEDI Cloud Contracting Officer written notice of all 577 subcontracts issued under this contract. For the purpose of this requirement, subcontract means a 578 contract, as defined in FAR Subpart 44.101. 579

2. The JEDI Cloud Contracting Officer’s written consent is required for all subcontractors 581 performing classified services under the contract. 582 Section H6: Limited Release Of Contractor Confidential Business Information 585

1. “Confidential Business Information,” (Information) as used in this clause, is defined as all 587 forms and types of financial, business, economic, or other types of information including technical 588 data or computer software/computer software documentation, whether tangible or intangible, and 589 whether or how stored, compiled, or memorialized physically, electronically, graphically, 590 photographically, or in writing even when -- (a) the owner thereof has taken reasonable measures to 591 keep such information secret, and (b) the Information derives independent economic value, actual or 592 potential, from not being generally known to, and not being readily ascertainable through, proper 593 means by the public. Information will include technical data, as that term is defined in DFARS 594 252.227-7013(a)(14) and 252.227-7015(a)(4). Similarly, Information does include computer 595 software/computer software documentation, as those terms are defined in DFARS 252.227-596 7014(a)(4). 597

2. The Government may release to individuals, employed by support contractors and their 598 subcontractors, Information submitted by the Contractor or its subcontractors pursuant to the 599 provisions of this contract. Information that would ordinarily be entitled to confidential treatment may 600 be included in the Information released to these individuals. Accordingly, by execution of this 601

JEDI Cloud Synopsis/Solicitation Page 26 contract, the Contractor and its subcontractors consent to a limited release of its Information, but only 602 for purposes as described in paragraph (3) of this clause. 603

3. Circumstances where the Government may release the Contractor’s or subcontractors’ 604 Information include the following: 605

a. To other contractors and subcontractors, and their employees tasked with assisting 606 the Government in handling and processing Information and documents in the 607 administration of contracts, such as file room management and contract closeout; 608

b. To other contractors and subcontractors, and their employees tasked with assisting 609 the Government in accounting support services, 610

c. To other contractors and subcontractors, and their employees tasked with assisting 611 the Government in technical and administrative support services for the JEDI Cloud 612 program, including monitoring contract progress and providing financial oversight; and, 613

d. To other contractors and subcontractors, and their employees tasked with assisting 614 the Government in furnishing advice or technical assistance in support of the 615 Government’s management and oversight of the JEDI Cloud program. 616

4. The Government recognizes its obligation to protect the Contractor and its subcontractors 617 from competitive harm that could result from the release of such Information. The limited release of 618 Information under paragraphs (3)(a-d) are permitted only under the following conditions: 619

a. The Government determines that access is required by other contractors and their 620 subcontractors to perform the tasks described in paragraphs (3)(a-d); 621

b. Access to Information is restricted to individuals with a bona fide need to possess; 622

c. Contractors and their subcontractors having access to Information have agreed under 623 their contract or a separate corporate non-disclosure agreement to provide the same level 624 of protection to the Information that would be provided by Government employees.