HQ0034-18-R-0077.pdf

JEDI Cloud RFP # HQ0034-18-R-0077

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 Post Date: July 26, 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 29

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

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

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

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

Section B3: Task Order Contract Types 41

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

SECTION C: DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK 58

Section C1: Performance Work Statement 59

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

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

Section C2: Program Management 70

JEDI Cloud Synopsis/Solicitation Page 14

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

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

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

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

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

JEDI Cloud Synopsis/Solicitation Page 15

Property (GFP) or Government Furnished Information. 122 Section C4: Contractor Control of Certain Parts of JEDI Cloud 124

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

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

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

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

a. Underlying hardware infrastructure, including networking components within the 142 data centers; 143

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

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

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

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

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

b. Has a bilaterally signed agreement (Control Agreement) that is binding for at least 11 153 years with the owner granting the prime contractor the following rights: 154

i. Unrestricted physical access; and 155

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

This Control Agreement must state that it may not be terminated by the Owner 157 without at least 120 days notice to the Government. The JEDI Cloud Contracting 158 Officer may request confirmation that the Control Agreement has not been altered or 159 terminated at any time. 160

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

SECTION D: PACKAGING AND MARKING 164

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

JEDI Cloud Synopsis/Solicitation Page 16

SECTION E: INSPECTION AND ACCEPTANCE TERMS 168

Supplies/services will be inspected/accepted at: 170

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

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

JEDI Cloud Synopsis/Solicitation Page 17

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 172

Section F1: Contract Period of Performance / Ordering Periods 173

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

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 185

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

JEDI Cloud Synopsis/Solicitation Page 18

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

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

CONUS (OCONUS). 196

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

1. Type 1 Cryptography Devices 223

2. Encryption Hardware 224 Section F6: Organizational Conflict of Interest (OCI) 226 During the period of performance, the Contractor shall notify the Government if any potential or 228 actual OCI, as described in FAR Subpart 9.5, exists for this contract for itself or its subcontractors. If 229 the Contractor believes that an actual or perceived OCI does exist on this contract, the Contractor 230 shall submit an OCI Mitigation Plan, explaining in detail how the OCI will be mitigated and/or 231 avoided. 232 Section F7: Method of Ordering 234 All DoD Contracting Offices and Ordering Activities are authorized to place TOs under the JEDI 236 Cloud ID/IQ contract IAW their delegated contracting authority. Ordering Contracting Officers 237 (OCOs) may issue TOs for services subject to their respective contracting warrant limitations. OCOs 238 have no authority to modify, add, or delete any terms and/or conditions in the base ID/IQ contract. 239 JEDI Cloud ID/IQ contract terms and conditions supersede TO special instructions, terms and/or 240 conditions where they may otherwise conflict. 241

JEDI Cloud Synopsis/Solicitation Page 19

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

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

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

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

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

(CDRL A008). 271

Section F11: Clause(s) 273 The following clause(s) are included by reference: 275 52.242-17 Government Delay Of Work APR 1984 277

JEDI Cloud Synopsis/Solicitation Page 20

SECTION G: CONTRACT ADMINISTRATION DATA 280

Section G1: Clauses Incorporated By Full Text 282

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

REPRESENTATIVE (COR) (MAR 2015) 285

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

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

(c) The Contractor is responsible for promptly providing written notification to the Contracting 299 Officer if it believes the COR has requested or directed any change to the existing contract. No action 300 shall be taken by the Contractor for any proposed change to the existing contract. No action shall be 301 taken by the Contractor for any proposed change to the contract until the Contracting Officer has 302 issued a written directive or a written modification to the contract. The Government will not accept 303 and is not liable for any alleged change to the contract unless the change is included in a written 304 contract modification or directive signed by the Contracting Officer. 305

(d) COR authority is not delegable. 307

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

252.204-7006 BILLING INSTRUCTIONS (OCT 2005) 313

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

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

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

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

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

JEDI Cloud Synopsis/Solicitation Page 21

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

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

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

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

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

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

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

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

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

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only 369 to fill in applicable fields in WAWF when creating payment requests and receiving reports in the 370 system. 371 Routing Data Table to be populated for individual TOs 373 -------------------------------------------------------------------------------------------- 374 Field Name in WAWF Data to be entered in WAWF 375 -------------------------------------------------------------------------------------------- 376 Pay Official DoDAAC 377 Issue By DoDAAC 378 Admin DoDAAC 379 Inspect By DoDAAC 380 Ship To Code 381 Ship From Code 382 Mark For Code 383 Service Approver (DoDAAC) 384 Service Acceptor (DoDAAC) 385

JEDI Cloud Synopsis/Solicitation Page 22

Accept at Other DoDAAC 386 LPO DoDAAC 387 DCAA Auditor DoDAAC 388 Other DoDAAC(s) 389 -------------------------------------------------------------------------------------------- 390

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

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

TDB 402

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

TBD 407

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

SECTION H: SPECIAL CONTRACT REQUIREMENTS 414

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

REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS 418

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

Section H1: Government Data 421

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

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

3. Any service usage data associated with JEDI Cloud users may be used for purposes of 436 providing or improving services under the contract. Such service usage data may not be sold to third 437 parties. Under no circumstances may the Contractor disclose JEDI Cloud account information to third 438

JEDI Cloud Synopsis/Solicitation Page 23 parties unless those third parties are approved subcontractors under the contract and such disclosure is 439 necessary for contract performance. 440

4. Before reusing unclassified infrastructure for another non-DoD tenant, the Contractor may be 442 required to purge the storage media IAW Attachment J-6, JEDI Cloud Cyber Security Plan and any 443 specific instructions included in a TO. The Contractor must request and obtain CCPO approval prior 444 to conducting any unclassified infrastructure and/or media destruction IAW Attachment J-6, JEDI 445 Cloud Cyber Security Plan and any specific instructions included in a TO. 446

5. The Contractor is prohibited from reusing classified infrastructure for another non-JEDI user 448 tenant or at a different classification level from which the infrastructure has been accredited without 449 CCPO approval; the Contractor is prohibited from transferring any classified infrastructure to a non-450 JEDI user. The Contractor may be required to purge classified storage media and/or destroy classified 451 infrastructure IAW Attachment J-6, JEDI Cloud Cyber Security Plan and any specific instructions 452 included in a TO. The Contractor must request and obtain CCPO approval prior to conducting any 453 classified storage media purging, classified storage media destruction, or classified infrastructure 454 destruction IAW Attachment J-6, JEDI Cloud Cyber Security Plan and any specific instructions 455 included in a TO. 456 Section H2: New Services 458

1. When new (including improved) IaaS, PaaS, or Cloud Support Package services are made 460 publicly available to the commercial marketplace in the continental United States (CONUS) and those 461 services are not already listed in the JEDI Cloud catalogs in Attachment J-1: Price Catalogs, the 462 Contractor must immediately (no later than 5 calendar days) notify the JEDI Cloud Contracting 463 Officer for incorporation of the new services into the contract in accordance with the Performance 464 Work Statement. At its discretion, the Contractor may also seek to incorporate new services into the 465 contract in advance of availability to the commercial marketplace. The JEDI Cloud Contracting 466 Officer must approve incorporation of any new services into the contract. 467

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

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

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

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

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

a. The allowable classified price premium for new services for the entire remaining 487

JEDI Cloud Synopsis/Solicitation Page 24 period of performance is the lesser expensive premium among the following: 488

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

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

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

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

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

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

a. For unclassified services, the revised catalog price shall match the commercially 515 lower price. 516

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

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

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

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

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

4. When the JEDI Cloud Contracting Officer incorporates the revised price into the Attachment 530 J-1, Price Catalogs and/or Attachment J-3: Contractor Discounts, Premiums, and Fees, as appropriate, 531 the Contractor shall update the listing of services and corresponding prices in the online pricing 532 calculator and APIs for JEDI Cloud within 24 hours. 533

JEDI Cloud Synopsis/Solicitation Page 25

Section H4: Additional Security 535

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

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

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

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

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

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

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

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

2. The Government may release to individuals, employed by support contractors and their 582 subcontractors, Information submitted by the Contractor or its subcontractors pursuant to the 583 provisions of this contract. Information that would ordinarily be entitled to confidential treatment may 584 be included in the Information released to these individuals. Accordingly, by submission of a 585 proposal or execution of this contract, the Offeror or Contractor and its subcontractors consent to a 586

JEDI Cloud Synopsis/Solicitation Page 26 limited release of its Information, but only for purposes as described in paragraph (3) of this clause. 587

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

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

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

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

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

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

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

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

c. Contractors and their subcontractors having access to Information have agreed under 607 their contract or a separate corporate non-disclosure agreement to provide the same level 608 of protection to the Information that would be provided by Government employees. Such 609 contract terms or separate corporate non-disclosure agreement shall require the contractors 610 and subcontractors to train their employees on how to properly handle the Information to 611 which they will have access, and to have their employees sign company non-disclosure 612 agreements certifying that they understand the sensitive nature of the Information and that 613 unauthorized use of the Information could expose their company to significant liability. 614 Copies of such employee non-disclosure agreements shall be provided to the Government; 615

d. Contractors and their subcontractors performing the tasks described in paragraphs 616

(3)(a-d) have agreed under their contract or a separate non-disclosure agreement to not use 617 the Information for any purpose other than performing the tasks described in paragraphs 618 (3)(a-d); and 619

e. Contractors and their subcontractors having access to technical data, computer 620 software, or computer software documentation have executed the Use and Non-Disclosure 621 Agreement specified at DFARS 227.7103-7 or have DFARS 252.227-7025 in their 622 contract. 623

5. The Government’s responsibilities under the Freedom of…