Attachment_L-2_Price_Scenarios_Amendment_0001.pdf

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

Price Scenarios 3 Updated 22 August 2018 4

1.0 For all scenarios: 6

a. Offerors should assume that the required solution is for an unclassified JEDI Cloud 8 requirement in accordance with the SOO and JEDI Cloud Cyber Security Plan, unless the 9 scenario explicitly states otherwise. For CONUS scenarios that do not specify an exact 10 location, the Offeror shall price the most expensive CONUS “region” or “availability 11 zone” proposed for JEDI Cloud. 12

b. Offerors should assume that all services and resources are utilized continuously, and that 13 all storage and data is retained for the duration of the order, unless the scenario explicitly 14 states otherwise. 15

c. Offerors should assume that the migration of any applications described into JEDI Cloud 16 is an instantaneous operation that takes place on day 1 of the order unless explicitly stated 17 otherwise; this migration of any applications is not to be priced. 18

d. Holidays, fiscal year end, and calendar year end have no effect on traffic patterns or 19 scenario requirements. Leap years are not to be observed. 20

e. Offerors must propose a solution that is consistent with the solicitation, including all 21 terms and conditions, requirements, and attachments, unless otherwise specified in the 22 scenario. 23

f. No classified information is required, nor should it be provided, in any response. 24

g. If Cloud Support Package offerings are required by the scenario, the Offeror shall clearly 25 identify the applicable tier of support and relevant category of services, including any 26 service constraints. If meeting the specified requirement in the price scenario is 27 dependent on ordering other Cloud Support Package offerings, then the Offeror shall also 28 identify and price all dependent Cloud Support Package offerings. 29

h. The performance characteristics of virtual CPU (vCPU) and GPU cores in JEDI Cloud, 30 including on tactical edge devices, must match the vendor’s commercial cloud offering. 31

i. Assume all applications in all scenarios are fully deployed and running in a production 32 environment. 33

j. Assume for all Ruggedized devices that the system does not need to be tested and 34 certified as meeting the standard. 35

Price Scenario 1 Sample Unclassified Application Stack 37 A scalable application has the following traffic patterns in production: 39

● Averages 4,000 requests/min during normal business hours (Monday to Friday, 0900 – 40

1700 ET) 41

● Monday from 0900ET to 1200ET traffic jumps to 400,000 requests/min 42

● Tuesday through Friday from 0900ET to 1000ET traffic jumps to 20,000 requests/min 43

● Averages 500 requests/min outside the “normal business hours” specified above 44

A globally distributed JEDI Cloud CDN routes all incoming web requests to the application 46 stack’s load balancer. 80% of the requests originate from North America, 5% of the requests 47 originate from South America, 5% of the requests originate from Europe, 5% of the requests 48 originate from Australia, and 5% of the requests originate from Asia. Static file requests are 49 routed directly to the static file store by the CDN and account for 5% of all requests, averaging 50 40 KB in size. All web requests are routed to a JEDI Cloud load balancer and average 10 KB in 51 size. Load is then distributed evenly across healthy application servers with 10% of all requests 52 resulting in an insert or update to the database. The system utilizes DNS Zone Hosting services 53 offered by the JEDI Cloud vendor and averages 1000 DNS requests/hour to a single DNS zone. 54 The main application resides on multiple nodes that are evenly distributed among the available 56 zones in the region, with a minimum of two nodes at all times. Each application node is hosted 57 on a moderate performance compute instance (8 vCPUs and 32 GB of RAM) and can handle up 58 to 500 requests per minute. During traffic spikes the number of required application instances is 59 expected to grow dynamically using the auto-scaling capabilities available from the JEDI Cloud 60 provider. Once a traffic spike has ended, the number of application nodes is expected to scale 61 back down to appropriate baseline levels. All requests are authenticated using transport layer 62 security (TLS). 63 Application activity will be pushed through a JEDI Cloud event stream (also known as a 65 message queue) with functionality similar to Apache Kafka. Assume 90% of application requests 66 result in events pushed to the queue, an average of 2 events per such requests, and each event is 67 200 KB in size. Eventually each event is read off the stream and results in an update or write to 68 the database cluster. Users may also upload files to the application, where they will be stored in 69 the static file store and retrieved dynamically according to an application specific access control 70 mechanism. Additionally, the application will store short-term session information in a JEDI 71 Cloud caching service. This session storage will start off at 1 GB in size on day 1 (do not price 72 any costs associated with the migration of all of this data to JEDI Cloud), with 100 MB added 73 each day and another 100 MB that expires each day. 74

The database cluster is hosted on six JEDI Cloud IaaS compute instances. The database contains 76 750 GB of data on day 1 (do not price any costs associated with the migration of all of this data 77 to JEDI Cloud). The nodes are evenly distributed among the available zones in the region, and 78 each node requires a compute instance with 24 vCPUs, 256 GB of RAM, and 500 GB of normal 79 SSD storage. Every minute, 500 MB of the 750 GB are updated. The data in the relational 80 database will grow in size by 0.2% per month. Each day the reads from the application and 81 analytics nodes total 1.5 TB in size. Automated snapshots are taken of the relational database 82 daily using a JEDI Cloud service and rotated every 7 days. Weekly full database backups are 83 created on Saturdays (starting the week the order is placed) and stored online for 4 weeks before 84 being rotated to offline storage. 85 Four nightly analysis jobs are run on eight high performance RAM optimized compute instances 87 requiring 32 vCPUs and 400GB of RAM each. Each instance should be powered down except 88 for the two hours they run each night. These jobs will each read 700 GB of data from the static 89 file store and 300 GB of data from the database cluster with no data preparation. Each job 90 produces 1 GB of new results which are stored in a separate, redundant, multi-zone JEDI Cloud 91 relational database service which requires 8 vCPU, 32 GB of RAM, and 3000 GB of storage. All 92 previous analysis job results are retained. This database service is separate from the database 93 cluster mentioned in the previous paragraphs. 94 The static file store resides in a single region, will contain 1 TB of static files on day 1, and will 96 grow as necessary (do not price any costs associated with the migration of all of this data to JEDI 97 Cloud). Every minute, 700 MB of the 1 TB are updated with new content (each update request is 98 500 KB). The static file store content will grow 0.2% per month. Each day the reads by the 99 application and analytic nodes total 2 TB in size (each read request averages 500 KB). 100 Of the files uploaded to the static file store, 33% require PKI encryption. Assume this application 102 has one master key, which is managed by the JEDI Cloud provider. The application will request 103 separate data keys based on that master for segments of its user population. Assume 5 new keys 104 are created every day. The application will use these keys to encrypt 1000 files per day and 105 decrypt 30,000 per day. 106 Every action that changes infrastructure configuration or alters infrastructure state is logged 108 through a JEDI Cloud logging service (assume there are 20 such actions a day). Additionally, 109 every data action taken for the managed data services is also logged through the same JEDI 110 Cloud service. The infrastructure components running this application are continuously 111 monitored through a JEDI Cloud service offering for performance degradation, which sends out 112 an email alert if defined thresholds are exceeded for any infrastructure performance metrics. 113 Additionally, there are 50 separate custom application metrics being monitored by this JEDI 114

Cloud service, 25 of which will send out an email alert if defined thresholds are exceeded. In 115 total, the JEDI Cloud service monitoring for this application sends 3 email notifications per day. 116

a. Please price this scenario: An order for a single application is placed on January 6, 118 2020, that meets the above technical requirements operating for 365 days continuously. 119

i. Please separately price all IaaS and PaaS offerings required to satisfy the above 120 technical requirements for a single application. 121

ii. Please separately price services under the Cloud Support Package line item to 122 support the application, including at a minimum: 24x7 support by phone, web, 123 and email; less than 1 hour response time for critical issues; access to detailed 124 online training materials; and guidance on application and infrastructure 125 architecture by phone using the lowest applicable tier. 126

b. Please price this scenario: The order is placed on June 7, 2021, for 50 applications total 128 across 25 separate accounts, meeting the above technical requirements operating for 365 days 129 continuously. 130

i. Please separately price all IaaS and PaaS offerings required to satisfy the above 131 technical requirements for 50 applications across 25 accounts. 132

ii. Please separately price services under the Cloud Support Package line item to 133 support the application, including at a minimum: 24x7 support by phone, web, 134 and email; less than 1 hour response time for critical issues; less than 4 hours 135 response time for moderate issues; online instructor-led and on-demand online 136 training for a total of 20 hours for 30 people; and remote in-depth architectural 137 support for refactoring applications and configuring cloud infrastructure totaling 138 40 hours. 139

c. Please price this scenario: The order is placed on June 3, 2024, for 1,000 applications 141 total across 750 separate accounts meeting the above technical requirements operating for 365 142 days continuously. 143

i. Please separately price all IaaS and PaaS offerings required to satisfy the above 144 technical requirements for 1000 applications across 750 accounts. 145

ii. Please separately price services under the Cloud Support Package line item to 146 support the application, including at a minimum: 24x7 support by phone, web, 147 and email; less than 1 hour response time for critical issues; less than 4 hours 148 response time for moderate issues; online instructor-led and on-demand online 149 training for a total of 60 hours for 200 people; and remote in-depth architectural 150 support for refactoring applications and configuring cloud infrastructure totaling 151 80 hours. 152

d. Please price this scenario: The order is placed on June 7 2027, for 1,000 applications 153 total across 750 separate accounts meeting the above technical requirements operating for 365 154 days continuously. 155

i. Please separately price all IaaS and PaaS offerings required to satisfy the above 156 technical requirements for 1000 applications across 750 accounts. 157

ii. Please separately price services under the Cloud Support Package line item to 158 support the application, including at a minimum: 24x7 support by phone, web, 159 and email; less than 1 hour response time for critical issues; less than 4 hours 160 response time for moderate issues; online instructor-led and on-demand online 161 training for a total of 60 hours for 200 people; and remote in-depth architectural 162 support for refactoring applications and configuring cloud infrastructure totaling 163 80 hours. 164

Price Scenario 2 Sample Classified COTS deployment + Tactical Edge 166 A Military Service utilizes an Enterprise Resource Planning (ERP) tool at the Secret level with a 168 relational database included as part of the ERP to conduct supply, maintenance, and 169 transportation services. The ERP has approximately 30,000 active user accounts across all 170 commodities previously mentioned. This application is deployed to CONUS data centers, but has 171 local, synced mirrors in garrison and aboard ship and in numerous austere environments, 172 including a high likelihood of intermittent disconnected state. The ERP utilizes DNS Zone 173 Hosting services offered by the cloud provider hosting the ERP. The hosted DNS service will 174 contain a single DNS zone and receive 100 DNS requests per hour. The nature of this 175 environment is such that a single user conducting maintenance can submit multiple service 176 requests each hour. 177 Supply transactions consist of: generating reports, which vary in size but involve querying into 179 the ERP’s database, submitting requisitions for parts, obligating funds, and receiving 180 requisitions. 181 Transportation transactions consist of managing shipments and movements of military 183 equipment providing logistical support to an area. Units submit movement requests for each 184 desired movement, identifying the requirement. The unit providing transportation then assigns 185 organic equipment, forwards the request for any of the requests they cannot support to other 186 units. Once a movement is completed a service request is completed for each vehicle used. 187 Emails are regularly sent by the main CONUS ERP system to the requesting and approving users 188 confirming the transportation request status. Emails are sent from a hosted messaging service 189 provided by the JEDI Cloud service provider. The ERP system sends a total of 500 messages per 190 day. 191 Across all of the areas above combined, the main CONUS ERP system deployment handles a 193 total of 1000 requests per minute with about three-quarters of those performing write operations 194 in the database. Assume each OCONUS garrison ERP system deployment handles a total of 200 195 requests per minute and each field ERP system deployment handles a total of 50 requests per 196 minute, regardless of the state of connectivity, with the same write operation ratio (three-197 quarters). Assume the size of each request for any ERP system deployment is 512 B and the 198 associated response is 128 KB. Each request is received by a simple, JEDI Cloud provided load 199 balancer which terminates SSL and then passes the request on to an available application node. 200 The JEDI Cloud virtual machines that the ERP system is running on require 8 vCPUs and 32 GB 201 of RAM per application node. Each virtual machine instance also requires 20 GB of simple Solid 202 State Disk storage. There are 50 application nodes in the main CONUS ERP system deployment, 203 20 application nodes per OCONUS garrison ERP system deployment, and 10 application nodes 204 per field ERP system deployment. Once per day, a snapshot of the entire provisioned block 205 storage for each virtual machine is taken. These snapshots are kept for 7 days. Each ERP system 206 deployment requires some JEDI Cloud virtual desktop working environments for use by the 207 Database Administrators (DBAs). These virtual desktops run Ubuntu, that requires the 208 equivalent of 2 vCPUs and 16GB of RAM, have 10 GB of storage space, and are solely used for 209 database access and tuning (they do not use or require any file sharing or additional systems or 210 services). The main CONUS ERP system deployment requires 10 virtual desktops, each 211 OCONUS garrison ERP system deployment requires 3 virtual desktops, and each field ERP 212 system deployment requires 1 virtual desktop. 213 The ERP system is deployed in OCONUS garrisons using static, modular, rapidly deployable 215 data centers. The ERP system is deployed in the field using ruggedized, portable edge devices 216 that support disconnected operations and automatic resync of all data with the rest of the ERP 217 system when possible. 218 To access the CONUS ERP system deployment while personnel are using non-government 220 communications networks, a site-to-site virtual private network (VPN) tunnel to the JEDI Cloud 221 must be utilized. 5 separate sites will each utilize a 1 Gigabit per second VPN connection 24 222 hours a day. The ERP will be expected to operate as both a completely self contained capability 223 per specific performance characteristics as defined in this scenario and also be capable of re-224 integrating (on the fly), to all appropriate external systems that require data exchange with the 225

ERP. 226

The database is currently 1 TB. A database dump will be uploaded to JEDI Cloud and then 228 imported into the new JEDI Cloud database on day 1 of the order (network usage, data storage, 229 and transaction fees associated with the transferring and importing of this data set should be 230 priced; assume the uploaded data is deleted after the import is completed; as with all scenarios, 231 do not price any migration support services). The database is expected to grow 0.5% per month. 232 The highly available database cluster for the main CONUS ERP system deployment will be 233 hosted in a JEDI Cloud service offering and requires 64 vCPUs and 400 GB of RAM. Each 234 OCONUS ERP system deployment and field ERP system deployment has a local database that 235 will use 2 compute nodes with 8 vCPUs, 64 GB of RAM, and 1TB of storage per node. Syncing 236 data between the main JEDI Cloud database and the local databases is handled by the ERP 237 system. Each OCONUS ERP system deployment writes 500 GB of data to JEDI Cloud once per 238 week, downloading any other changes that have been made. Each field ERP system deployment 239 writes 50 GB of data to JEDI Cloud once per week, downloading any other changes that have 240 been made. 241 Every action that changes infrastructure configuration or alters infrastructure state is logged 243 through a JEDI Cloud logging service, assuming there are 20 such actions a day. Additionally, 244 every data action taken for the managed data services is logged through a JEDI Cloud service. 245

Automated snapshots of the CONUS database occur daily and are kept online for 30 days before 246 rotation to offline storage along with weekly full backups taken every Saturday (starting the 247 week the order is placed) that are rotated to offline after 30 days. 248

a. Please price this scenario: The order is placed on January 6, 2020, for the above technical 250 requirements operating for 365 days continuously. In addition to the CONUS ERP system 251 deployment, assume 4 garrison OCONUS ERP system deployments and 30 field ERP system 252 deployments in ruggedized equipment. 253

i. Please separately price all IaaS and PaaS offerings in JEDI Cloud, the modular 254 data centers, and portable edge devices required to satisfy the above technical 255 requirements. 256

ii. Please price separately any non-consumption based fees or other charges 257 associated with the number of modular data centers and portable edge devices 258 required to meet the tactical edge storage and compute requirements for the 259 specified OCONUS and field ERP system deployments. 260

iii. Please separately price services under the Cloud Support Package line item to 261 support all instances of the ERP system described in the pricing scenario, 262 including at a minimum: 24x7 support by phone, web, and email; less than 1 hour 263 response time for critical issues; less than 4 hours response time for moderate 264 issues; instructor-led and on-demand online training for a total of 20 hours for 30 265 people; and remote in-depth architectural support for refactoring applications and 266 configuring cloud infrastructure totaling 40 hours. 267

iv. On January 30, 2020, a request is placed to retrieve a single offline backup of the 268 database for use in forensic investigation. Assume the backup size is 950 GB. 269 The retrieval shall be done as fast as possible, and the request is expedited. 270

b. Please price this scenario: The order is placed on June 7, 2027, for the above technical 272 requirements operating for 365 days continuously. In addition to the CONUS ERP 273 system deployment, assume 4 garrison OCONUS ERP system deployments and 30 field 274 ERP system deployments in ruggedized equipment. 275

i. Please separately price all IaaS and PaaS offerings in JEDI Cloud, the modular 276 data centers, and portable edge devices required to satisfy the above technical 277 requirements. 278

ii. Please separately price services under the Cloud Support Package line item to 279 support all instances of the ERP system described in the pricing scenario, 280 including at a minimum: 24x7 support by phone, web, and email; less than 1 hour 281 response time for critical issues; less than 4 hours response time for moderate 282 issues; instructor-led and on-demand online training for a total of 20 hours for 30 283 people; and remote in-depth architectural support for refactoring applications and 284 configuring cloud infrastructure totaling 40 hours. 285

iii. On June 30, 2027, a request is placed to retrieve a single offline backup of the 286 database for use in forensic investigation. Assume the backup size is 950 GB. 287 The retrieval shall be done as fast as possible, and the request is expedited. 288

Price Scenario 3 Sample Tactical Edge + Peered Query 291 A set of sensors on a government owned device captures 12 GB of High Definition Audio and 293 Video data per hour. This data is collected 24 hours a day. There are 40 of these government 294 devices deployed in the field for a specific operation. All of the sensor data from all of these 295 government owned devices is streamed to a dedicated cluster of JEDI Cloud ruggedized portable 296 edge devices in the field that has intermittent network access to a WAN. The cluster of one or 297 more JEDI Cloud ruggedized portable edge devices must be able to store up to 2 weeks of sensor 298 data. 299 The data must be processed daily by the portable edge devices regardless of connection; the 301 devices will use JEDI Cloud PaaS offerings to conduct image recognition and audio analysis on 302 the device itself. The analysis of video and audio will utilize a two stage, ensemble model. The 303 first stage of the model will evaluate audio and video separately. All of the models used by the 304 portable edge devices will be created and maintained by the Department. The models will be 305 trained using a JEDI Cloud service and then synced to the devices before they are taken into the 306 field. The first stage video model will be trained on 100,000 210 KB labeled 4k video frames 307 uploaded by the Department. The audio model will be trained on 100,000 2 MB WAV files 308 uploaded by the Department. The first stage models will classify and tag data for triage in which 309 triaged data will be forwarded to the second stage of the ensemble model. The second model will 310 take into account the output of both previous first stage models and will have been trained on a 311 separate set of 100,000 labeled and paired audio and video files (assume this set also consists of 312 210 KB video frames and 2 MB WAV files). 313 Twice a day, an operator in the field will run a real-time prediction analysis on the portable edge 315 devices using the ensemble model above. Results of the analysis must be accessible to, and 316 consumable by, commanders in the field using a separate viewing application that the Offeror 317 should not address as part of this scenario. Once connected to the WAN, all processed data is 318 securely transferred to the user’s JEDI Cloud account (i.e., not on the portable device), including 319 any meta-data and analysis results. On a weekly basis the raw sensor data is transferred back to 320 the user’s JEDI cloud account and stored in nearline storage for a period of 4 weeks before being 321 rotated to offline storage. Offerors may assume that the weekly raw sensor data transfer occurs 322 when a stable, high bandwidth connection is established between each portable device and JEDI 323 Cloud. 324 Assume that the scenario described in the previous paragraphs is occurring for 10 separate 326 operations simultaneously. 364 days after the initial order date, and once each month thereafter, 327 advanced data analysis (referred to as the periodic advanced data analysis) using JEDI Cloud 328 business intelligence PaaS offerings must be performed against a subset of the datasets across all 329 10 accounts. Each monthly analysis requires 32 vCPUs, 400 GB of RAM, and takes 36 hours to 330 complete. There are 100 users with access to the analytics platform. As part of this cross-account 331 advanced data analysis, each of the 10 JEDI Cloud accounts also has a single JEDI Cloud 332 relational database containing 10 TB of corroborating data. Each database is highly available, 333 requires 32 vCPUs, and has 200 GB of RAM. The cross-account analysis must include data from 334 these 10 traditional relationship databases (1 for each account, so 10 total). The cross-account 335 analysis will be looking for specific patterns as well as anomalies. The total data to be analyzed 336 is 10 PB (assume 2 PB of processed data, 500 TB of raw sensor data in online storage, and 7.5 337 PB of raw sensor data in offline storage that is loaded with a normal, non-expedited request). 338 Predictions from this analysis are performed in batch (not real-time) and must be stored in 339 another JEDI Cloud account (do not price any costs associated with the transferring or storing of 340 the prediction results). 341

a. Please price this scenario: The order is placed on September 2, 2019, for the above 343 technical requirements and operating for 15 months continuously where the classification 344 level of the source data and the analysis results is Unclassified. 345

i. Please price separately the described number of tactical edge storage and compute 346 devices. 347

ii. Please separately price all IaaS and PaaS offerings required to satisfy the above 348 technical requirements. 349

iii. Please price separately all costs such that for every operation, there is an 350 additional 10% identical spare portable tactical edge devices on-hand (minimum 351

2) at the base running the operation in case of failure (but that are not being 352 utilized). 353

iv. Identify and price any fee required upon return of the device to the vendor. 354

v. Please price separately secure destruction of all classified storage media 355

(applicable to paragraphs c, d, e, and f below in this price scenario) used upon 356 mission termination in accordance with the Cyber Security Plan. 357

vi. Include any fees should the devices be entirely destroyed 364 days after the initial 358 order is placed while in Government possession. 359

vii. Please separately price services under the Cloud Support Package line item to 360 support the applications described in the pricing scenario for the initial 12 months 361 only, including at a minimum: 24x7 support by phone, web, and email; less than 1 362 hour response time for critical issues; less than 4 hours response time for 363 moderate issues; instructor-led and on-demand online training for a total of 40 364 hours for 50 people; and remote in-depth architectural support for refactoring 365 applications and configuring cloud infrastructure totaling 80 hours. 366

viii. Identify any additional fee(s) if the Government retains the devices for an 367 additional 12 months beyond the one year initial period of performance without 368 having placed another order. For purposes of this price scenario, assume that the 369 ID/IQ option ordering period is exercised. 370

b. Please also price this scenario in accordance with the entirety of paragraph (a) 372 above, but assume the order is placed on June 7, 2027. 373

c. Please also price this scenario in accordance with entirety of paragraph (a) above, 375 but assume: the order is placed on June 7, 2021, the classification level of the source 376 data and data analysis on the portable devices at the tactical edge is unclassified, a copy 377 of all of the data transferred from all portable devices to any JEDI Cloud account is also 378 simultaneously transferred to a single JEDI Cloud account operating at Secret 379 classification, and the periodic advanced data analysis applications and results are 380 classified at Secret. 381

d. Please also price this scenario in accordance with entirety of paragraph (a) above, 383 but assume: the order is placed on September 2, 2024, the classification level of the 384 source data is Secret, and all analysis applications and results are classified at Secret. 385

e. Please also price this scenario in accordance with entirety of paragraph (a) above, 387 but assume: the order is placed on September 2, 2024, the classification level of the of 388 the source data is Top Secret/SCI, and all analysis applications and results are classified 389 at Top Secret/SCI. 390

f. Please also price this scenario in accordance with entirety of paragraph (a) above, 392 but assume: the order is placed on July 5, 2027, the classification level of the entire 393 program has been deemed a SAP at the TS/SCI level. 394

Price Scenario 4 Large Data Storage, Analysis, and Archiving 397 The following is an example of large data storage and follow up data analysis that retrieves and 399 processes chunks of data from a large offline set. 400 A collection of systems across multiple accounts (assume 100) produces a large number of log 402 entries every day. There are two different sources for the logs: (1) logs from the JEDI Cloud IaaS 403 and PaaS offerings and (2) logs from the applications deployed in those accounts. Assume a total 404 of 500 GB of logs in aggregate from all of the accounts each day. These log entries must be 405 stored in a separate JEDI Cloud account (referred to as log collection account), which the 406 individual account users have no access to (do not price the collecting, aggregating, or 407 transferring of these log files into the log collection account). The team managing the log 408 collection account only has read access to the storage. All data in the log collection account is 409 rotated to nearline storage after 30 days, and then to offline storage after 90 days from creation 410 and retained in perpetuity. Regular scans of these logs occur nightly and on-demand as described 411 below. 412 The log collection and analysis team also has another JEDI Cloud account (referred to as the 414 analysis account) for the analysis application used to analyze the data in the log collection 415 account. The analysis application stack consists of a set of ten (10) high performance GPU nodes 416 performing the analysis jobs (At Least 2 GPUs, 10 vCPUs, and 200GB of RAM per node), a set 417 of four (4) moderate performance compute nodes hosting a clustered queueing and messaging 418 system (At Least 8 vCPUs and 32GB of RAM per node), and a set of four (4) low performance 419 compute nodes hosting a web-based graphical user interface (GUI) (At Least 1 vCPU and 1GB 420 of RAM per node). The high performance GPU nodes each require an additional 50 GB of 421 simple solid state disk (SSD) block storage to be provisioned. The web application is behind a 422 JEDI Cloud load balancer that receives 100 requests per minute (512B request, 40KB response). 423 The web application requires a single, low performance (but highly available) relational database 424 that is provided as a JEDI Cloud PaaS offering (At Least 2 vCPU, 8 GB of RAM, and 100 GB of 425 storage). Assume that there is already 2 PB of offline storage, 30 TB of nearline storage, and 15 426 TB of online storage in the log collection account on day 1 of the order (do not price any costs 427 associated with the migration of all of this data to JEDI Cloud). For pricing purposes, “At Least” 428 in this paragraph means that if the proposed JEDI Cloud service(s) do not identically match the 429 specified minimum technical requirements, then the Offeror must propose the service(s) that 430 satisfy those minimum technical requirements even if the level of service exceeds what is 431 required by the scenario; in no event may an Offeror propose a service that does not meet 432 minimum technical requirements). 433 Assume that 10 on-demand analysis jobs are run each week, with 4 pulling from online data, 3 435 from nearline data, and 3 from offline data. For each online on-demand analysis job assume the 436 average target dataset is 5 TB. For each nearline on-demand analysis job assume the average 437 target dataset is 10 TB. For each offline on-demand analysis job assume the average target 438 dataset is 50 TB and that offline data may be brought online with slow access (not expedited). In 439 each case, the data is first copied in bulk to online storage (if necessary) and then analyzed. Any 440 appropriate tags or markings identified by the analysis are applied to the original source data. 441 The tags will be used in identifying that raw data at a later time for security review. Once the 442 analysis is complete, if the data being analyzed was an online copy of nearline or offline data, the 443 online copy is deleted. Nightly analysis jobs (assume 20 each night) run over online data only, 444 but may process log files from any time during the 30 day rotational period in which data is kept 445 online. Assume these nightly jobs process an average of 500 GB of online data each. 446 In total, analysis results consume 200 GB of storage per day on average. Analysis result data are 448 tagged based on their source data, method of initiation, and other key markers and those tags are 449 used in technical policy review and for billing purposes. Analysis results are saved in online 450 storage for 45 days, nearline storage for another 90 days, and then archived into offline storage. 451 Results stored offline are discarded after four (4) years. Assume the application has 4.5 TB of 452 online result data, 4.5 TB of nearline result data, and 72 TB of offline result data on day 1 of the 453 order (do not price any costs associated with the migration of all of this data to JEDI Cloud). 454 A user of the analysis application must be able to override the default lifecycle configuration set 456 for the results such as setting alternate expiration dates and moving analysis results from one 457 storage class to another. The application will execute API commands against the JEDI Cloud 458 provider to accomplish this. Assume that users will transition 500 GB of storage from nearline to 459 online each week and 200 GB of offline to online each week (not expedited). 460

a. Please price this scenario: The order is placed on January 6, 2020, for the above 462 technical requirements operating for 365 days continuously. 463

i. Please separately price all IaaS and PaaS offerings required to satisfy the above 464 technical requirements. 465

ii. Please separately price services under the Cloud Support Package line item to 466 support the applications described in the pricing scenario, including at a 467 minimum: 24x7 support by phone, web, and email; less than 1 hour response time 468 for critical issues; access to detailed online training materials; and guidance on 469 application and infrastructure architecture by phone using the lowest applicable 470 tier. 471

b. Please also price paragraph (a) above, but assuming that the order for paragraph (a) is 473 placed on January 6, 2022. 474

c. Please also price paragraph (a) above, but assuming that the order for paragraph (a) is 475 placed on January 6, 2025. 476

d. Please also price paragraph (a) above, but assuming that the order for paragraph (a) is 477 placed on January 6, 2028. 478

e. Please price this scenario: The order is placed on October 31, 2023, for a complete 480 exportation of all log data from the log collection account and all analysis results 481 associated with the analysis application account described in this scenario. Assume log 482 data totals of 15 TB of online data, 30 TB of nearline data, and 3 PB of offline data. 483 Assume analysis result data totals of 5 TB of online data, 5 TB of nearline data, and 90 484 TB of offline data. Assume this request is not time-sensitive (no rush request). Assume 485 the data must be transferred to an on-premise data storage solution provided by the 486 Department that is capable of supporting the relevant data types in this scenario. 487

f. Please also price paragraph (e) above, but assuming that the order for paragraph (c) is 489 placed on April 5, 2026. 490

g. Please also price paragraph (e) above, but assuming that the order for paragraph (c) is 492 placed on April 5, 2028. 493

Pricing Scenario 5 Rapidly Deployed, Static Data Center 495 There is a forward operating base (FOB) that is processing large quantities of data and regularly 497 engages in various activities that need large, elastic computing power. They need to rapidly get 498 access to such computing power through static, modular, rapidly deployable data center(s) in 499 short order. 500 This ruggedized data center solution must be delivered to a CONUS U.S. Military base within 502 the number of days specified in performance metric 31 in Table 5.1 of the SOO from the order 503 date. The ruggedized data center must be able to fit and be properly secured inside of a U.S. 504 military cargo aircraft or ship and commercial shipping vessel. The data center should be able to 505 operate fully (as specified below) in a fully disconnected state. Assume a solid pad for placement 506 and clean power connections are provided by the FOB. The data center must be modular 507 meaning that additional computing and storage resources can be added at a later date. 508 At minimum, each FOB site requires data center(s) to have: 510

(a) Usable storage capacity for 10 PB of data, spread across all forms of storage (objects, 511 files, databases, file systems, etc.). All storage must be redundant (three copy minimum); 512

(b) Computing power of 2000 virtual CPU cores and 200 virtual GPU cores; 513

(c) Multiple data uplink options to include fiber optic, low and high bandwidth ethernet, and 514 compatibility with standard satcom systems; and 515

(d) Implementation that meets CNSSAM TEMPEST/01-13: Red/Black Installation Guidance 516 with regard to physical separation of environment where necessary. 517

a. Please price this scenario: The order is placed on November 4, 2019, for the above 519 technical requirements operating for 365 days continuously for 4 FOB military 520 deployment sites where there is an equal split of Unclassified, Secret, and Top Secret 521 workloads at each site, including maintaining logical and physical isolation, as 522 appropriate. 523

i. Please price separately all 4 FOB sites. 524

ii. In pricing the 4 FOB sites, for any consumption-based charges, assume a single 525 copy of the application stack described in Pricing Scenario 1 is running in each 526 modular data center throughout the duration of the order. Assume any nearline or 527 offline storage remains online storage for the duration of the order. 528

iii. Please separately price services under the Cloud Support Package line item to 529 support the data center deployments described in the pricing scenario, including at 530 a minimum: 24x7 support by phone, web, and email; less than 1 hour response 531 time for critical issues; less than 4 hours response time for moderate issues; 532 instructor-led and on-demand online training for a total of 60 hours for 200 533 people; and remote in-depth architectural support for refactoring applications and 534 configuring cloud infrastructure totaling 80 hours. 535

iv. Identify and price any fees required upon return of the data centers to the vendor. 536

v. Identify and price any fees for secure destruction of all classified storage media 537 used upon mission termination in accordance with the Cyber Security Plan. 538

vi. Include any fees should the data centers be entirely destroyed at any point while 539 in Government possession. 540

vii. Identify any additional fee(s) if the Government retains the data centers for an 541 additional 5 months beyond the one year initial period of performance without 542 having placed another order. 543

b. Please also price paragraph (a) above, but assuming that the order for paragraph (a) is 544 placed on October 4, 2021. 545

c. Please also price paragraph (a) above, but assuming that the order for paragraph (a) is 546 placed on October 7, 2024. 547

d. Please also price paragraph (a) above, but assuming that the order for paragraph (a) is 548 placed on October 4, 2027. 549

Pricing Scenario 6 Containerized Data Analysis Framework 551 A military Service runs flight operations at a given base that produce logs on system function 553 and maintenance needs. Separately, a maintenance system is used by the Service to enter reports 554 on maintenance actions and scheduling. Each flight operation results in a large amount of data 555 that is streamed after flight completion to a data warehouse hosted in JEDI Cloud. Maintenance 556 records are stored in a separate system not hosted in JEDI Cloud. The Service will perform near 557 real-time predictive analysis on both the flight data and maintenance records to determine future 558 maintenance needs. 559 Each flight mission produces 500 GB of structured binary data per aircraft. Assume 20 flights 561 per 24-hour period at the base. This data is streamed into the JEDI Cloud data warehouse directly 562 post-flight. Assume the data warehouse storage backend has 1 PB of data in it on day 1 (do not 563 price any costs associated with the migration of all of this data to JEDI Cloud). A total of 250 564 maintenance records are created per day at this base in the maintenance system (this system is 565 not to be priced in this scenario). The maintenance system converts each record into a 500 KB 566 structured record, which is sent via API call to a highly available JEDI Cloud serverless function, 567 which requires 2.5GB of RAM to run. This serverless function parses the incoming data for 568 validity and stores it in a highly available JEDI Cloud NoSQL document-based data store. 569 Assume this NoSQL data store is 100 GB on day 1 (do not price any costs associated with the 570 migration of all of this data to JEDI Cloud). The run time for each execution of this function is 1 571 second. In addition, to format validity of the maintenance record, the identity of the maintenance 572 worker and their authorization to submit records for that aircraft is validated through a JEDI 573 Cloud directory service. Assume there are a total of 10,000 identity objects and 1,000 other 574 directory objects in the directory service for the base. 575 The flight operations system will push an event to a separate, highly available JEDI Cloud 577 serverless function for each flight mission once that flight’s operational data has been uploaded. 578 The serverless function requires 512MB of RAM to run. This serverless endpoint will in turn add 579 1000 events to a message queue in a JEDI Cloud message service (each message is 50KB). The 580 run time for each execution of this function is 500 milliseconds. Each message will be consumed 581 by a data analysis application, which will start a data analysis job, which is hosted in JEDI 582 Cloud. Each analysis job constructs and submits a query to the data warehouse service, which 583 returns 1 GB of data. The results of the query are analyzed alongside the maintenance record 584 data from the document store. The results of this analysis consume 5 MB of data and are stored 585 in a highly available simple NoSQL key-value based data store. Assume this NoSQL data store 586 is 500 MB on day 1. There are 10 such analysis applications in use within the overall system. 587 Each data analysis application stack is a collection of containers in a microservices architecture 589 managed by a JEDI Cloud container orchestration service. Assume each application consists of 4 590 distinct microservices, hosted in 12 separate containers, and each container requires 2 vCPU, 2 591 GB of RAM, and 1 GB of storage. The application code for each microservice for each analysis 592 job is version controlled in its own JEDI Cloud hosted code repository. On code commit to any 593 master branch a set of tests are run using continuous integration hosted by JEDI Cloud. Each 594 build for each of the code repositories requires that the build service utilize 2 vCPUs and 2 GB of 595 RAM for 10 minutes. Assume a total of 10 builds are run per day. Following successful passing 596 of the tests, a build artifact is produced and the resulting container is scheduled for zero-597 downtime redeployment. Assume 50 containers, that are each 1 GB in size, are generated and 598 uploaded to a JEDI Cloud container registry every 7 days. The container registry contains 144 1-599 GB containers on day 1 (do not price any costs associated with the migration of all of this data to 600 JEDI Cloud), and old containers are removed at the same rate that new containers are added (the 601 total number remains constant). 602 A JEDI Cloud web application firewall is employed to protect the analysis applications from 604 unwanted traffic. There are 30 custom rules in addition to any standard rules applied by the JEDI 605 Cloud vendor. In total, the data analysis applications receive 100,000 requests per day between 606 both valid and malicious actions. Automated security scans of the data analysis applications and 607 data is performed daily, which includes threat identification, reporting, and real-time notification 608 to the system owner. 609

a. Please price this scenario: The order is placed on January 6, 2020, for the above 611 technical requirements operating for 365 days continuously where the classification level 612 of the entire system is unclassified. This order is for operations on a single base. 613

i. Please separately price all IaaS and PaaS offerings required to satisfy the above 614 technical requirements. 615

ii. Please separately price services under the Cloud Support Package line item to 616 support all of the applications and services described in the pricing scenario, 617 including at a minimum: 24x7 support by phone, web, and email; less than 1 hour 618 response time for critical issues; less than 4 hours response time for moderate 619 issues; instructor-led and on-demand online training for a total of 20 hours for 30 620 people; and remote in-depth architectural support for refactoring applications and 621 configuring cloud infrastructure totaling 40 hours. 622

b. Please also price this scenario in accordance with entirety of paragraph (a) above, 623 but assume the order is placed on April 4, 2022, and the scenario is replicated at 100 624 bases. 625

c. Please also price this scenario in accordance with entirety of paragraph (a) above, 627 but assume the order is placed on September 5, 2022, and the system has been classified 628 secret. 629

d. Please also price this scenario in accordance with entirety of paragraph (a) above, 631 but assume the order is placed on September 5, 2022, the system has been classified 632 Secret, and the scenario is replicated at 100 bases. 633

e. Please also price this scenario in accordance with entirety of paragraph (a) above, 635 but assume the order is placed on July 1, 2024, and the system has been classified Top 636 Secret / SCI. 637

f. Please also price this scenario in accordance with entirety of paragraph (a) above, 639 but assume the order is placed on July 1, 2024, the system has been classified Top Secret 640 / SCI, and the scenario is replicated at 100 bases. 641

g. Please also price this scenario in accordance with entirety of paragraph (a) above, 643 but assume the order is placed on January 3, 2028, and the system has been classified as a 644 SAP at the TS/SCI level. 645

h. Please also price this scenario in accordance with entirety of paragraph (a) above, 647 but assume the order is placed on January 3, 2028, the system has been classified as a 648 SAP at the TS/SCI level, and the scenario is replicated at ten (10) bases. 649