DRAFT_RFQ_140G0122R0010_Clauses.pdf
PDF 1 MB Posted
- Attached to
- Cloud Hosting Solutions III
- Solicitation number
- 140G0122R0010
About this file
This is a draft solicitation for the Department of the Interior seeking cloud hosting solutions. The solicitation will establish an indefinite delivery, indefinite quantity contract with a maximum value of $1 billion to provide cloud hosting services across the Department. Services will include a virtual private cloud, implementation of policies, hosting applications, and managed services optimized for the cloud environment. The contractor must have experience integrating government cloud solutions and billing procedures. Questions are due by June 24, 2022 and an industry day will be held on June 15, 2022. The period of performance is expected to be a five year base period with three two-year option periods. The selected contractor must have the capabilities to meet the requirements described in the performance work statement.
View the file
Other files
Show all 29
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
140G0122R0010 Cloud Hosting Solutions III Page 3 of 118
SECTION B - Supplies or Services/Prices 1
Description of Services 3 This is a single Indefinite Delivery, Indefinite Quantity (IDIQ) contract under which individual task 5 orders will be issued for services of DOI Wide Cloud Hosting Solutions. 6 The contractor shall provide the necessary and qualified personnel and services as needed to perform the 8 requirements set forth in the main Statement of Objectives (SOO) and as indicated in each individual task 9 order Performance Statement of Work (PWS). 10 Type of Contract 12 This is a single IDIQ contract with provisions for Firm Fixed Price (FFP) and Time and Materials/Labor 14 Hours (T&M/LH) type task orders. 15 Determination of Order Type/Price/Costs 17 The determination of individual task order type, FFP or T&M/LH, will be dependent on the level of detail 19 that the Statement of Work provides. Each task order Request for Proposal (RFP) sent to the contractor 20 will state the type of order determined appropriate by the Contracting Officer. 21 Contract Minimum and Maximum Amounts 23 In accordance with (IAW) FAR Clause 52.216-22 entitled, “Indefinite Quantity” the Maximum value of 25 the CHS III contract is $1 Billion. During the contract period of performance, including any renewal 26 periods, the Government shall place orders totaling a: 27 Minimum of $10 Million 29 Maximum amount not to exceed $1 Billion. 31 Determination of Task Order Type/Price/Costs 33 This single award IDIQ contract for the Department of the Interior allows for the placement of task orders 35 by warranted ordering contracting officers. Task Order types permitted include fixed-price and time and 36 materials/labor hour. The determination of individual Task Order type will be dependent on the level of 37 detail that the Statement of Work provides. Each Request for Proposal (RFP) and Task Order sent to the 38 contractor, will state the type of order determined appropriate by the Contracting Officer. 39 Travel 41 Travel is not anticipated under this IDIQ contract. However, if travel is determined at a later time, travel 43 shall be in accordance with individual Task Order requirements. 44 Travel, Material, and Other Direct Costs shall be reimbursed at actual costs incurred in accordance with 46 FAR 52.216-7, Allowable Cost and Payment, and the Federal Travel Regulation as applicable. These 47 items will be set forth, when applicable, on each task order. 48
140G0122R0010 Cloud Hosting Solutions III Page 4 of 118
SECTION C - Description/Specifications 50
1.0 INTRODUCTION 51
This Statement of Objectives (SOO) describes the objectives for Department of the Interior (DOI) wide 52 Cloud Hosting Services (CHS) for Information Technology Modernization and an option for Data 53 Hosting. 54 Offerors shall use this Statement of Objectives (SOO) as the basis for preparing their proposal. Offerors 56 shall ensure that they thoroughly address all aspects of the request for proposal (RFP) and Day one SOOs 57 in their proposals. 58
2.0 EXECUTIVE SUMMARY 60
The Department of Interior (DOI, Department) requires the ability to efficiently acquire secure cloud 61 services on an ongoing basis. This acquisition will establish enterprise cloud services brokers to manage 62 a portfolio of cloud computing, storage and application services across multiple vendor offerings, 63 supplying DOI with a flexible solution for the delivery of those cloud services. 64 This request for proposal and inclusive statement of objectives (SOO) presents a framework for moving 66 the DOI enterprise from the current state to a broader single hybrid Enterprise Cloud Cluster (ECC) 67 including this cloud capability enabled state. We define the current enterprise, identify key objectives, 68 and define goals in terms of how to move forward to attain cloud benefits. This will result in profound 69 changes in the DOI computing environment, technology refresh and leverage existing efforts, forging a 70 path on how to move pieces of the enterprise to full cloud adoption, significantly improving DOI’s 71 delivery of enhancements to each of DOI’s unique bureaus and service delivery programs, driving down 72 information technology (IT) sustainment costs, and enabling resources to fund high priority emerging 73 requirements. 74 Cloud services provide a wealth of benefits that DOI can leverage to provide the right services, at the 76 right place, at the right time in service to our country needs. Cloud services will enable the Bureaus to 77 improve efficiency, align with administration goals and provide a sound technical platform for our future. 78 DOI needs a consistent approach to reviewing, securing, managing and procuring cloud services to ensure 79 optimized coordination and integration between vendors, which provides the best value for the taxpayer. 80 A partnership between portfolio managers with DOI processes, will rapidly provide the benefits DOI 81 needs for success. 82 The transition to enterprise cloud services: 84
● Makes the Department more efficient 85 o Migrates from capital expenditures to operating expenditures 86 o Provides a better response to supply and demand 87 o Enables quick to market 88
● Aligns with Governmental Goals 89 o Cloud Smart 90 o Data Center Consolidation 91
● Makes Technical Sense 92 o Provides a consistent platform/approach for development 93 o Enables new technology adoption 94 o Is portable across endpoints 95 o Embeds consistent security in all cloud solutions 96
140G0122R0010 Cloud Hosting Solutions III Page 5 of 118
3.0 BACKGROUND 98
The U.S. Department of the Interior (DOI, Department) is a Cabinet-level agency that manages America's 99 vast natural and cultural resources. The Department employs an estimated 70,000 people, which includes 100 expert scientists and resource-management professionals in nine technical bureaus to include the Bureau 101 of Indian Affairs (BIA), Bureau of Land Management (BLM), Bureau of Ocean Energy Management 102 (BOEM), Bureau of Reclamation (USBR), Bureau of Safety and Environmental Enforcement (BSEE), 103 National Park Services (NPS), Office of Surface Mining Reclamation and Enforcement (OSMRE), Fish 104 and Wildlife Services (FWS), and the U.S. Geological Survey (USGS). The Department: 105
• has over 2,400 operating locations nationwide; 107
• hosts over 280,000 volunteers annually; 108
• promotes energy security and critical minerals development to create jobs for Americans; 109
• directs its efforts towards increasing access to outdoor recreation opportunities for all 110
Americans; 111
• promotes enhanced conservation stewardship, whereby all levels of government and private 112 landowners work cooperatively together; 113
• works to improve the management of species and their habitats; and 114
• works to uphold trust and relationships with Indian tribes, Alaska Natives, and insular areas and 115 to respect self-determination and sovereignty. 116
The DOI Office of the Chief Information Officer (OCIO), provides information technology support across 117 the department to ensure that DOI meets the mission, vision, and strategic objectives of its agency priority 118 goals. In alignment with these goals, OCIO’s mission is to provide available, adaptable, secure, and cost-119 effective information technology products and services to DOI programs/projects, enabling the staff to 120 provide mission-critical support to the nation. Information Technology (IT) enables the DOI to support 121 and facilitate critical services, improve action processing, and provide enhanced customer care and 122 services to DOI bureaus while maintaining the Department’s information security posture. 123 The Cloud Hosting Solutions (CHS) III acquisition puts DOI bureaus in control of how, when, and where 125 they wish to receive service. It is a catalyst to make DOI a world-class service provider and a framework 126 for modernizing DOI’s culture, processes, and capabilities to put the needs, expectations, and interests of 127 the clients first. Any employee or citizen accessing any DOI IT infrastructure should have a consistent, 128 high-quality experience. To accomplish this, the five strategies that are fundamental to the transformation 129 of DOI include: 130
• Improving the cloud services experience. At a minimum, every cloud service platform 132 should be predictable, consistent, and efficient. The OCIO and USGS are working to make 133 each touch point simplistic. 134
• Empowering DOI employees, who are the face of DOI. They provide the information, and 135 access to important products and services, and they serve with distinction every day. 136
• Achieving support services excellence. Excellent support services will let employees and 137 leaders focus on improved business processes, rather than worry about IT infrastructure 138 improvements. 139
• Establishing a culture of continuous performance improvement. Employees who strive for 140 performance improvement will apply lean strategies to examine their processes in new ways 141 and build a culture of continuous improvement. 142
• Enhancing strategic partnerships. Enhanced partnerships will allow the Department to extend 143 the reach of services available to stakeholders. 144
140G0122R0010 Cloud Hosting Solutions III Page 6 of 118
The DOI’s OCIO and USGS missions are to consistently identify, evaluate and leverage external 146 resources to improve the business delivery experience, while enhancing productivity and efficiency across 147 the enterprise. This strategy drives an unprecedented demand by our stakeholders and clients for IT 148 services and benefits. To serve this demand, the DOI is streamlining operations to better serve the 149 American public by consolidating 49 regions across 8 bureaus into 12 Unified Regions, encompassing all 150 the Department’s bureaus except for the Bureau of Indian Affairs. The new organization reduces 151 bureaucratic redundancy, improves communication between experts in the field and leaders in 152 Washington, DC, and allows for the sharing of knowledge and resources more effectively among the 153 Department’s field staff and local collaborators. 154 DOI is a federated organization that relies on bureaus and offices to manage the different infrastructure 156 components. The DOI is attempting to move into the future state of cloud services by an overarching 157 enterprise-wide strategic vision. 158 The main drivers of this effort are the increasing benefits and mandates for cloud migration and data 160 center consolidation. 161
Cloud Migration: The Office of Management & Budget (OMB) 2019 Federal Cloud Smart 163 Strategy outlines the impetus and benefits of cloud adoption in federal agencies, including 164 acceleration of data center consolidation and better utilization of existing infrastructure assets. 165
Data Center Consolidation: The Federal Chief Information Officer initiated the Federal Data 167 Center Consolidation Initiative (FDCCI) and the follow-on Data Center Optimization Initiative 168 (DCOI) to reduce the IT footprint for agencies through the consolidation of traditional data 169 centers to promote the use of Green IT, to reduce the cost of data center hardware, increase the 170 overall IT security posture of the government, and to shift IT investments to more efficient 171 computing platforms and technologies. 172
These two drivers, as well as the OMB guidance (most recent OMB M-21-05) and, from Cloud First to 174 Cloud Smart (see cloud.cio.gov), highlight the importance of harnessing the fundamental shifts in IT 175 investment patterns to increase IT efficiencies and reduce IT investments. Prior to migrating to the cloud 176 or consolidating data centers, it is critical to understand the current IT environment, facilitate informed 177 decisions with the Bureaus and offices about their portfolio, and make educated choices for applications 178 that migrate to the cloud or an on-premise hosting facility. 179
4.0 SCOPE 181
The USGS and OCIO are working together on a department-wide procurement effort to obtain a single 182 Virtual Private Center (VPC) cloud services that will support cloud and managed service requirements. 183 The purpose of the proposed Cloud Hosting Solutions (CHS) III contract is to provide access to services 184 needed to support the DOI VPC. These services can be broadly categorized as those typically presented 185 by: 186
1. A public Cloud Support Services Provider that—as demonstrated with past performance—offers 188 support services and subject matter expertise to include development (including 189 migration/implementation), sustainment, and operations in the cloud. 190
2. A public Cloud Hosting Provider that offers a Federal Risk and Authorization Management 191 Program (FEDRAMP) certified cloud platform and associated services and tools with domain 192 expertise in the offering of cloud platform infrastructure and capabilities within their platform and 193 developing industry standards. 194 https://cloud.cio.gov/
140G0122R0010 Cloud Hosting Solutions III Page 7 of 118
This document outlines objectives related to each of these categories of support separately. The purpose 196 of this effort is to acquire Cloud services to replace existing and aging infrastructure currently managed 197 by DOI and its bureaus and offices, and to allow for growth and innovation of existing and new projects. 198 The cloud support service provider or broker must provide the DOI with a technical and organizational 200 transformation roadmap that addresses all phases including architecture, engineering, implementation and 201 sustainment as well as strategic partner engagement services to accomplish this agenda. A critical facet 202 of this strategic partnership is to leverage new acquisition models built on cloud enablement to shift from 203 acquisition of network infrastructure technology as an asset, to infrastructure technology as a service 204 (ITaaS). The cloud support service provider or broker will also engage with the carriers to ensure they 205 meet all service level agreements. 206 The goal of the proposed requirement is to develop and maintain general-purpose environments that 208 support a broader DOI VDC requirement, with associated Cloud-based infrastructure and services, which 209 supports Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) with FedRAMP approved 210 deployments. The DOI is open to contractor flexibility in proposing unique solutions and submitting 211 alternative ideas as options that may increase the likelihood of meeting mission needs, result in less 212 performance risk that may improve efficiency, and reduce DOI’s present and long-term risk with 213 obtaining and utilizing cloud services. 214 Cloud services must be able to support the entire DOI as selected by projects within DOI and bureaus; 216 therefore, internal users and mission partners, must provide a robust, agile, and interoperable 217 infrastructure that provides connectivity and computing capability to deliver integrated services to clients. 218 DOI requires contractors who bring a mission focus to this program, which can continuously identify 220 methods for applying IT processes to improve DOI’s mission performance and execution. The 221 Department and bureaus require the expertise to continuously analyze, research, identify, and recommend 222 the most effective and efficient application of technology to meet DOI’s mission requirements. They 223 must also demonstrate the capability to design, engineer, install, and integrate IT infrastructure hardware, 224 software and service components. DOI will require the contractor to: 225
• Provide, under a performance-based contract, secure, highly reliable, and available IT 227 infrastructure services that meet or exceed DOI customer expectations. 228
• Continuously review, analyze, and take proactive measures to ensure that the DOI IT 229 infrastructure stays current with technological advances in the industry, while validating that 230 infrastructure investments align with the DOI Hosting Strategy Vision and mission objectives. 231
• Improve service through the implementation of standard service management and delivery 232 frameworks and associated processes. 233
• Develop and provide innovative solutions for consideration by DOI. 234
• Provide transparency to customers and end-users on service cost, performance, and satisfaction as 235 demonstrated and documented through customer satisfaction surveys. 236
• Continuously monitor cost of services and customer satisfaction for services delivered throughout 237 the life cycle of the IT infrastructure operations and support programs, as measured through Total 238 Cost of Ownership (TCO) studies. 239
• Achieve predictable costs for services to enable better budgeting for the customer base. 240
• Effectively utilize subcontract and teaming arrangements as defined in the Federal Acquisition 241
Regulation (FAR) Part 19 - Small Business Programs. 242 The primary functions of the anticipated Department-wide CHS III program are illustrated below and are 244 based on each DOI bureaus’ unique business needs, to include: 245
140G0122R0010 Cloud Hosting Solutions III Page 8 of 118
• The design, implementation, and maintenance of a well-architected Virtual Private Cloud (VPC). 247
• An implementation and enforcement of various policies within the VPC environment. 248
• A targeted location for customers to host their applications. 249
• An offering of various “managed services,” which is optimized to run in the partner Cloud 250
Service Provider (CSP) environment. These services are strategically offered to reduce the 251 requirement for individual customers to build their own alternatives utilizing their existing 252 dedicated spaces resources, and to increase the standardization of specific implementations of 253 said services. Such standardizations should improve cost efficiency and scalability of the overall 254 CHS offerings. Most of these services would likely be registered in a service catalog. 255
• A central financial control center over the entire contract award, which entails gathering 256 information for targeted billing back to customers and/or centralized common spend items that 257 may be subsidized by various components in the DOI, and appropriately facilitating the fund 258 transfers between relevant parties. Overall support for the ECC ecosystem (along with relevant 259 partners, such as DOI telecom/network support, etc.) as would typically occur in any large 260 enterprise data center located within the physical confines of a given company or agency. 261
The scope of any potential contract award may require: 263
• Architectural advice on the configuration and deployment of the DOI Cloud Hosting Solutions 265
(CHS) VPC. 266
• Strategic advice on how to improve the support of the overall DOI CHS program. 267
• Contract personnel to help complement the existing staff on the CHS team, at many ranges of 268 expertise and experience, as requested by the DOI CHS program. 269
• Contract personnel who would also be tasked with knowledge transfer to and training for 270 government staff. 271
• Access to an extremely robust CSP environment capable of supporting the wide-ranging needs of 272 a Department the size of DOI. 273
• Itemized and roll-up billing on a monthly basis to the DOI CHS program for all associated spend 274 categories. 275
• Along with government staff, provide consultation to existing and potential customers related to 276 their specific IT support needs in the DOI CHS environment. 277
• Upon request by the DOI CHS program, in-depth advice and possible active facilitation with 278 specific customers (programs and projects) to help them rationalize, architect, and plan out 279 migrations of significant existing internally deployed applications or systems into the DOI CHS 280 VPC. This could potentially include other customers’ systems that are already in the Cloud via 281 other task orders within DOI. 282
• Upon request, any other services associated with what is typically needed to facilitate the support 283 of an enterprise-scale data center deployed in an internal environment. 284
• Specific support to seamlessly migrate all existing CHS systems and associated support services 285 into an alternate environment in the event the DOI CHS would be sited at a CSP other than 286 Amazon Web Services (AWS), where the USGS CHS VPC is presently hosted. Performance of 287 the proposed migration does not require any significant impact on the DOI’s current operations. 288
The DOI will accept a technical proposal with associated cost estimates from contractor(s) who can 290 contribute to reducing the Total Cost of Ownership (TCO), without compromising objectives or 291 requirements; have existing partnerships with industry leading technology vendors and service providers; 292 and demonstrate the ability to accomplish tasks and deliverables in accordance with stated or desired 293 service levels and performance objectives. 294
140G0122R0010 Cloud Hosting Solutions III Page 9 of 118
Under a performance-based services contract, DOI will extensively use service level agreements (SLAs) 296 and metrics to monitor the performance of this contract and tasks. The DOI and contractors will baseline 297 and monitor progress, using agreed-upon performance metrics and service level agreements. The DOI 298 expects the contractors to propose meaningful performance and quality assurance metrics and 299 performance incentives in its proposal that will best advance the purposes of the contract on a cost-300 effective basis. 301 The overall objective is to perform as an enterprise cloud services provider or broker, and to continuously 303 improve such performance based on lessons learned by execution of cloud brokerage responsibilities. 304 The scope includes all cloud options, such as IaaS, Database-as-a-Service (DBaaS), and PaaS as most 305 appropriate to the requirement, depending on the uniqueness of the requirement to the DOI versus 306 commodity IT services needed by all federal agencies. The overall objectives are to: 307
• Optimize selection of the most appropriate cloud provider for a given business requirement; 309
• Reduce risk associated with consuming services (e.g., via federated security, cost, and 310 compliance); 311
• Integrate diverse cloud services to meet the diverse science mission needs; 312
• Add significant value to services (e.g., context and analytics); 313
• Provide subject matter expertise (e.g., best procurement practices consistent with the FAR); 314
• Achieve transparency in cost and performance of the cloud provider; 315
• Centralize cloud services functionality (e.g., service aggregation, archival and auditability); 316
• Provide a central point for governance according to federal government mandates; 317
• Offer various IT services to help consumers with cloud service providers or broker-related project 318 implementations, ranging from managed services to business process utility (BPU); 319
• Streamline and simplify the IT services acquisition process; 320
• Establish processes and tools to assure on-going, viable competition among selected cloud 321 providers by assuring easy migration of all DOI intellectual property and data from one cloud 322 provider to another under contract terms and conditions all parties agree to. 323
• Provide access to all support services directly from the CSP that are typically offered in their 324 normal commercial practice at no charge to the DOI; and 325
• Provide, at the DOI’s option, access to elevated levels of support from the CSP, in a tiered level 326 with accompanying payment levels that are clearly defined. 327
The DOI-wide CSP shall enable: 329
• Emerging Technology. New doors open to opportunities for service and benefits delivery that 331 currently do not exist. This will give DOI staff and clients access information via a multitude of 332 devices that may not be hardwired into DOI’s network. 333
• Interoperable Applications. Enterprise and external systems use shared services to exchange, 334 process, and present information to improve interoperability, reduce system development costs, 335 and accelerate delivery. 336
• Better Value Modern Applications. DOI makes more cost-effective investments in technology 337 and interfaces that are understandable to end users. Using the most suitable Commercial off the 338 shelf (COTS) and Government off the shelf (GOTS) tools, enterprise applications are built as 339 dynamic websites that adapt to how various browsers need to translate and display information. 340
• Flexible and Scalable Infrastructure. DOI uses technologies that provide elasticity and 341 scalability that cloud technologies allow for the sharing of capacity and support mobility, data 342 analytics, and authoritative data. 343
140G0122R0010 Cloud Hosting Solutions III Page 10 of 118
• Secure Information and Networks. Information is encrypted as it traverses through the 344 network. Devices, processes and staff are authenticated as they move between functions and are 345 authorized based on their functional role. 346
• Efficiency. Identify economies of scale, increase productivity and gain operational efficiencies. 347 Ultimately, DOI seeks to drive out redundancies; replicate support service best practices; 348 reengineer processes across the enterprise; establish service level agreements with clearly defined 349 performance measures and targets; establish customer-driven frameworks; enable technology; 350 manage performance; and apply common standards. 351
The cloud service provider or broker will provide DOI the ability to procure “third-party” services from 353 vendors that provide services on a rental or “pay as you go” nature that are designed to enhance or 354 complement the CSP environment associated with the award. CSP vendors typically have partners that 355 offer specialized or complementary services that build on the core CSP platform or services. In their 356 entirety, they present a more mature and expansive suite of Cloud services, which the Department can 357 more fully utilize. 358
Business process latency—the state of existing but not yet fully developed or manifested—is problematic 360 in all large organizations. DOI is no exception. Business process latency stifles effectiveness. A 361 reduction in latency will enable DOI to fulfill its commitments, and then, regardless of location, establish 362 efficient processes to implement our Data Hosting Vision and enable improved access to data. 363 The prime contractor is required to have demonstrated expertise in the realm of architecture, service 365 delivery, and operational support in the CSP environment identified in the Cloud Hosting Services (CHS) 366 procurement. 367 The prime contractor is required to have strong prior government experience integrating cloud hosting. 369 Experience with billing and invoicing for a government customer will also be vital to the success of CHS. 370 Awarding the contract to an experienced integrator with strong past performance is vital. The CSP or 371 broker shall: 372
• Provide access to all support services directly from the CSP at no charge to DOI that CSPs offer 374 at no charge in their normal commercial practice. 375
• Provide, at the DOI’s option, access to elevated levels of support from the CSP, in a tiered level 376 with accompanying and clearly defined payment levels. 377
• Monitoring dash-board tool must be able to integrate with the CSP. 378
• The prime contractor must be capable of migrating all existing CHS (and possibly other DOI) 379
Cloud-based systems from where they currently reside into the CHS environment that will be 380 supported under the CHS III contract. It should be noted that the CSP under any new CHS 381 award, may not be where CHS currently resides. 382
• Provide, at the DOI’s option, consulting and other Cloud-related support services on an agreed-383 upon labor schedule. The USGS currently supports a VPC and associated support services with a 384 combined government/contractor model. In general, contractors provide senior-level architecture 385 guidance, high-end technical services, and knowledge transfer. The DOI anticipates it will 386 continue to utilize contractors in that mode going forward. Additionally, periodic process and 387 data integration analysis and support services will ensure optimization of processes that directly 388 or indirectly affect cloud services, i.e. account, authentication, and configuration management. 389 The overall footprint of an expanded VPC could proportionally increase the level of required 390 contract support. While DOI may require services from any of the contractor labor categories 391 typically associated with the design, support, advancement, and management of an enterprise-392 level VPC in a public CSP environment, we are most likely to require services from the 393
140G0122R0010 Cloud Hosting Solutions III Page 11 of 118 categories identified in the attached document entitled “Labor Categories for CHS3”. A written 394 task order must be issued for required services. The DOI will submit an RFP to the contractor 395 and will issue a task order upon agreement of labor mix/level of effort. The Contracting Officer 396 will issue the task order. 397
• Assist, advise, architect, and implement a secure information system environment that complies 398 with all required federal regulations and DOI specific security objectives. 399
• Ensure data portability and migration assistance, as needed, to an in-house or another cloud 400 platform upon contract completion. 401
• Assist the DOI in creating solutions that allow the Department to monitor traffic moving in and 402 out of the cloud environment in order to meet Trusted Internet Connections (TIC) and other 403 security monitoring requirements. 404
• Agree to generally bill for Cloud-related support services by the hour based on contractually 405 established professional labor categories. Occasionally, both parties may identify and agree upon 406 fixed-price tasks. 407
The DOI requires the Contractor to develop and maintain throughout the engagement, a Master Program 409 Plan (MPP) that describes the overall target architecture, a roadmap to achieving that target architecture 410 with major milestones, and an integrated master schedule that presents a detailed work breakdown 411 structure and milestones for each of the major task groups identified. 412
5.0 PROGRAM AND PROJECT MANAGEMENT 413
The Contractor(s) shall provide the technical and functional activities necessary for the management of 414 this SOO. The Contractor shall employ a technical approach, organizational resources and management 415 controls to achieve cost, schedule and performance requirements throughout the engagement. 416 The contractor, at a minimum, shall perform the following program management activities: 418
• Develop and manage Infrastructure Modernization Program Management Plan and Project 420 Schedule, outlining the individual project Work Breakdown Structures (WBS) and resource 421 allocation to accomplish each task. 422
• Project coordination and management support between contractor employees and engineers, 423 federal staff, vendors, and future customers of the various infrastructure systems to ensure 424 integration points are in place throughout the project’s lifecycle. 425
• Support deployment planning and overall project management for the multiple locations across 426 the nationwide DOI enterprise. 427
• Provide overall quality control throughout the project’s performance and escalate issues to federal 428 management as needed. 429
• Produce briefings, program plans, and other documentation as requested for presentation to the 430 OCIO, USGS, and other bureau sponsors and stakeholders. 431
• Provide communications and outreach materials to customers on CHS service offerings. 432
• Provide executive coaching and instructional presentations regarding new functionality to DOI 433 customers; 434
• Provide meeting support such as agenda development, minutes, and action tracking; and 435
• Prepare status reports, on a weekly and ad-hoc basis, to provide an update on the project’s 436 progress and specific areas that may require management’s action. 437
5.1 Reporting 438
At the request of the Contracting Officer Representative (COR), the contractor shall provide the COR 439 with separate Project Status Reports that monitor the progress, cost, schedule, and labor hours expended 440 to date for each Task Assignment issued under this SOO (monthly). The Project Status Reports shall 441
140G0122R0010 Cloud Hosting Solutions III Page 12 of 118 include a discussion of overall personnel, financial, deliverables and milestones, risks (to include 442 opportunities) and other issues, including potential impacts on schedules or project plans and 443 recommended actions. Where relevant, the reports shall discuss these issues for each Task Assignment. 444 The Contractor/Subcontractor employee by task assignment shall include in the reports a summary of 446 expended labor hours and dollars. They shall submit each report to the government COR and Project 447 Manager in accordance with the delivery schedule agreed upon by the parties. The COR may change the 448 format and content of the reports over time to reflect the dynamic nature of the assigned activities. 449 Although the reports are due at the request of the COR, this shall not relieve the Contractor of the 450 responsibility to proactively keep the government informed of issues or problems as they occur (including 451 technical, cost or schedule issues). 452 The contractor shall also provide weekly updates that inform the COR about the status of each Task 454 Assignment as requested. 455
6.0 Statement of Objectives (SOO) 457
The DOI seeks a single integrator and one or more Cloud Support Services Providers (CSPs) to assist 458 with DOI leadership of data center consolidation and overall reduction of the DOI-owned and -managed 459 data center footprint through vendor-managed cloud services. To maximize standardization and 460 efficiency while minimizing duplicative administrative tasks, the CSP should have built in multi-tenancy 461 capability to readily provide shared service across DOI. Where cloud services are not applicable, DOI 462 continues to principally reduce application, system, and database inventories to essential enterprise levels 463 by increasing the use of virtualization and DOI on-premise consolidation. 464 Leveraging cloud services and on-premise, traditional virtualization, DOI is committed to: 466
• derive efficiency through the pooling of storage, network and compute resources, and on-demand 467 dynamic resource allocation; 468
• offer efficient shared service via Application Rationalization, use of container based and 469 serverless technology; 470
• enable automated Cloud Brokering, Multi-tenant capability, Zero Trust Networking; and 471
• leveraging DevOps industry standard practices. 472
Per federal guidance, through utilization of cloud hosting and the consolidation of data centers, DOI will 474 modernize our IT infrastructure to improve efficiency, address material weaknesses, protect data, and 475 ensure availability of IT infrastructure to staff and contractors in alignment with OMB guidance. 476 The DOI OCIO will perform ongoing analysis of existing and future DOI applications cloud hosting and 478 provide updated recommendations on the location of application hosting. 479 The overarching DOI objectives for data center consolidation are to: 481
• Maintain cross-agency goals for a highly available, scalable, and redundant data center 482 infrastructure that will substantially reduce the government’s risk and provide for fiscally 483 responsible future IT growth. 484
• Transition to commercial cloud at the highest application service level (i.e. SaaS) as the default 485 service while maintaining secure and efficient data center infrastructure to support systems which 486 cannot or should not migrate to the virtual data center environment. 487
• Optimize space and IT asset utilization and processing capacity to minimize environmental 488 impacts and achieve cost savings through energy consumption reductions and economies of scale 489 for purchasing and operational resources. 490
140G0122R0010 Cloud Hosting Solutions III Page 13 of 118
• Increase the IT security posture of DOI enterprise IT systems through implementation of 491 standardized processes and monitoring tools across all systems located in the consolidated and 492 existing data centers. 493
• Provide automated and standardized security hardening of hardware and software platforms in 494 accordance with National Institute of Standards and Technology (NIST) 800-53 and Federal 495 Information Security Management Act (FISMA) guidelines to ensure the integrity and 496 confidentiality of DOI electronic information and systems. 497
• Provide automated and standardized monitoring of IT systems for availability and performance to 498 improve service levels across the Department. 499
• Ensure continuous IT system availability and performance through implementation of 500 redundancy, load balancing, continuity of operations and disaster recovery measures. 501
• Provide advisory services and solutions that will: 502 o Satisfy FITARA reporting requirements while expanding information to incorporate 503 cloud hosting services. 504 o Catalog, standardize, and consolidate data center cloud hosting contracts. 505 o Standardize, catalog and centralize the consumption and deployment of cloud services in 506 both process and technology. 507 o Develop a storefront for intake of development requests, create presentations, budget 508 plans and projections, strategic roadmaps, and project plans to provide recommendations 509 to the DOI/Bureau Cloud Services Team for cloud service offerings to address new 510 requests for services, modernize our current cloud service portfolio, and determine which 511 non-cloud offerings are migrated to the cloud and integrated into the cloud services 512 portfolio. 513 o Provide a method to transition and/or migrate legacy applications to enterprise cloud 514 solutions. 515 o Perform ongoing analysis of existing and future DOI applications cloud hosting services 516 to provide recommendations on application hosting to the DOI cloud services managing 517 partners. 518 o Establish fundamental criteria for new applications that ensure compatibility with DOI 519 enterprise cloud solutions. 520 o Develop and implement solutions, procedures, communications and strategies that 521 enforce cloud service provider adoptions. 522
To deliver increasing value to the stakeholders and clients, the DOI is modernizing the IT infrastructure 524 across the enterprise. The purpose of this effort is to acquire professional services and the agency-wide 525 support that the DOI requires in order to adequately support the modernization of the DOI Enterprise IT 526 Infrastructure and ensure compliance with enterprise strategy and mandates for cloud migration and data 527 center consolidation. Additionally, the DOI strategy has led to the identification of the following 528 objectives: 529
1. Target vision and Architecture 531
2. Standardization and Governance 532
3. Business Processes 533
4. Automation/Orchestration wherever possible, e.g., adopting artificial intelligence 534
5. Migration to target architecture, e.g., Private Cloud/Optimized Data Center Infrastructure at 535
Major Tiered Data Centers 536
6. Seamless integration between Private and Public Cloud 537
7. Tools standardization/integration 538
8. Security and Zero Trust Network (ZTN) 539
140G0122R0010 Cloud Hosting Solutions III Page 14 of 118
6.1 Cloud Technical Statement of Objectives 540
Contractor will provide cloud and professional support services and mechanisms that enable efficient 541 enterprise IT shared services and consolidation of the U.S. Department of the Interior (DOI) data centers 542 to a target state (and number) that promotes standardization, and operational efficiency across the 543 Department without compromising availability, reliability, performance, business continuity, backup and 544 security. 545
6.1.1 Provide Cloud Support Services 546
The cloud support services provider shall: 547
1. Provide a schedule and budget estimates for proposed work activities. 548
2. Monitor and adhere to baseline (or rebaseline) scope, schedule, and costs. 549
3. Communicate within project team, DOI and bureau program/project management, and other 550 bureau leads as sponsors and/or stakeholders. 551
4. Promote continuous improvement in work processes to improve quality, timeliness, cost-552 effectiveness, and data interoperability. 553
5. Propose system improvements and enhancements to CHS III Program Management that affect 554 scope, schedule, cost, functionality, performance, data management and user experience. 555
6. Support intra-project activities, CHS III enterprise activities, technical meetings and working 556 groups, and proof of concepts that have a cloud component. 557
7. Participate in Department and cross-bureau collaborative activities and working groups with 558 approval from the Program Manager. 559
8. Participate in interface control document (ICD) development between external partners and CHS 560
III cloud-based systems. 561
9. Consult with CHS Program and Project Management on the development, maintenance and 562 operations of enterprises solutions. 563
10. Support CHS III core system integration, trouble shooting, and interface issues, both during core 564 hours and as needed outside of normal working hours. 565
11. Research new cloud and data center technologies to: 566
a. stay current and informed of changes regarding cloud providers and technologies 567
b. determine how it may impact DOI; and 568
c. recommend courses of action to the program manager. 569
12. Research and plan for new cloud activities involving multiple bureaus through the contract 570 proposal process. 571
13. Provide a development and test mode as part of the platform for tools/services/applications in the 572 Cloud within the DevOps model. 573
14. Travel to other bureaus, offices, or field centers as necessary in support of CHS III Cloud-based 574 systems. 575
6.1.2 Deliverables 576
The contractor will submit the following: 577
1. Cloud Service Provider’s Assessment and Identification: Classification, locations, contracts and 578 services, and DOI Services (Applications) provided; 579
2. Reporting mechanism(s); 580
a. Monthly cloud status reports to include task accomplishments, plans, progress, and problems. 581
b. Trip reports notes. 582
c. Meeting notes. 583
3. Cloud and Service Target Recommendations; 584
4. Information Technology Migration Plan; 585
5. Platform Implementation Plan (updated when contract options are exercised); 586
140G0122R0010 Cloud Hosting Solutions III Page 15 of 118
6. Platform IT Security Plan; 587
7. Platform Architecture Design (updated every two years); 588
8. System Engineering Management Plan (updated every two years); 589
9. Data Preservation Plan (updated every two years); 590
10. Configuration Management Plan (updated every two years); 591
11. Compliance Management Plan; 592
12. Consumer Management Plan; 593
13. Software Design Plan; 594
14. Tool Standardization/Rationalization/Integration (across Private cloud/On-premise/Public Cloud); 595
15. Data Rationalization; 596
16. Cloud affinity/brokering (guide optimal workload destination based on requirements input); and 597
17. Lessons learned and program summary for the previous year of performance. 598
6.1.3 Assumptions and Constraints 599
The U.S. Government expects the cloud support services provider will: 600
1. Offer a tiered level of service. 601
2. Continue to identify and recommend potential system and/or operations flow efficiencies for the 602 cloud-based systems as appropriate. 603
3. Provide access logs for all transactions at the request of the government. 604
4. Provide subject matter expertise as requested. 605
5. Provide interoperability across cloud platforms as integration between platforms (cloud and 606
Department virtual data centers) continue to mature. (Interoperability is a significant hurdle for 607 federal agencies in the current migration path towards Data Center Consolidation and the cloud 608 infrastructure.) 609
6. Provide application rationalization services for Department needs to include understanding, 610 consulting, advising, reviewing and recommendations to satisfy Department goals for 611 management of the portfolio for services and tools. 612
6.2 Provide Cloud Hosting Services (Platform) 613
The cloud hosting services provider shall identify, leverage and establish cloud services through 614 Federal Risk and Authorization Management Program (FedRAMP) accredited “-as a Service” 615 solutions such as: Infrastructure, Platform, and Storage. This is the principal objective. In addition, 616 requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 617 794d) are determined to be relevant. See http://www.Section508.gov to obtain information about 618 Section 508 Electronic and Information Technology (EIT) Accessibility Standards. 619
The U.S. Government expects the CHS provider to report through the prime integrator in regard to the 621 following: 622
1. Provide scope, schedule and budget proposals for future work activities. 623
2. Monitor and adhere to baseline (or rebaseline) scope, schedule, and costs. 624
3. Communicate within project team, DOI and bureau program/project management, and other 625 bureau leads as sponsors and/or stakeholders. 626
4. Promote continuous improvement in work processes to improve quality, timeliness, cost-627 effectiveness, and data interoperability. 628
5. Propose system improvements and enhancements to CHS III Program Management that affect 629 scope, data and users/usage. 630
6. Support intra-project activities, CHS III enterprise activities, technical meetings and working 631 groups, and proof of concepts that have a cloud component. 632
7. Participate in Department and cross-bureau collaborative activities and working groups with 633 approval from the program manager. 634 http://www.section508.gov/
140G0122R0010 Cloud Hosting Solutions III Page 16 of 118
8. Participate in Interface Control Document (ICD) development between external partners and 635 CHS III cloud-based systems. 636
9. Consult with CHS Program and Project Management on the development, maintenance and 637 operations of enterprises solutions. 638
10. Support CHS III core system integration, trouble shooting, and interface issues. 639
11. Research cloud technologies and stay current and cognizant of changes regarding cloud providers 640 and technologies. 641
12. Research and plan for new cloud activities including multiple bureaus through the contract 642 proposal process. 643
13. Provide a development and test mode as part of the platform for tools/services/applications in the 644
Cloud. 645
14. Travel to other bureaus or field centers as necessary in support of CHS III Cloud-based systems. 646
6.2.1 Deliverables 647
For each initial, updated, and final plan the contractor will submit the following: 648
1. Cloud Service Provider’s Assessment and Identification: Classification, locations, contracts and 649 services, and DOI Services (Applications) provided. 650
2. Reporting Mechanism(s); 651
a. Monthly cloud status charts to include task accomplishments, plans, progress, and 652 problems. 653
b. Travel reports/notes. 654
c. Meeting Notes. 655
3. Cloud and Service Target Recommendations Report. 656
4. Master Program Plan (MPP). 657
5. Annual Work Plans for all current, planned and proposed development work. 658
6. Information Technology Migration Plans. 659
7. Closure and Equipment Disposal Plan (Full Shutdown of closed Hosting Spaces). 660
8. Data Center Contracting requirements standards, Service Level Agreement (SLA), creation of 661 common compliance language. 662
9. Software Design Plan (platform). 663
10. Coordination and Communication Plan. 664
11. Compliance Management Plan. 665
12. Consumer Management Plan. 666
13. Annual lessons learned and program summary for the previous period of performance. 667
6.2.2 Assumptions and Constraints 669
The U.S. Government expects the cloud hosting services provider will: 671
1. Offer a tiered level of service. 672
2. Continue to identify and recommend potential system and/or operations flow efficiencies. for the 673 cloud-based systems as appropriate. 674
3. Provide access logs for all transactions at the request of the government. 675
4. Provide subject matter expertise as requested. 676
5. Provide peta-byte volume and scale for storage and compute to meet the Departments growing 677 needs. 678
6.3 Partnering Objectives 679
Creating a "partnership" between the DOI and the contractor(s) is a major intent of this SOO. The extent 680 to which a contractor’s services advance DOI mission accomplishment through the completion, use, and 681
140G0122R0010 Cloud Hosting Solutions III Page 17 of 118 documented results from the DOI infrastructure services and systems will determine its performance. 682 Within the context of this SOO, "partnership" means an interactive, mutually supportive professional 683 relationship that is open, collaborative, agile, and customer oriented. In addition to meeting the objectives 684 described herein, the U.S. Government expects the contractor to: 685
1. Consistently take steps to understand DOI’s crucial business issues and opportunities. 687
2. Identify and propose improvements to frameworks, processes, and services throughout the 688 performance period of the contract. 689
3. Share the risks and responsibilities of joint implementations and initiatives. 690
4. Ensure its products and services deliver tangible and meaningful business benefits. 691
5. Work collaboratively with other contractors, government agencies, and business partners to…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .