Welcome to the Getting Started where you will learn about the Cloud and the importance of gathering requirements.

Educate Customers

Cloud Computing originates back to the 1990s where the Cloud symbol was used to reflect connections of systems across the Internet in architectural drawings. The Cloud image caught on early as a symbol of the Internet. Nearing year 2000, the Cloud definition achieved a broader recognition pertaining to the delivery of enterprise applications from a vendor's website. Today, Cloud Computing is understood to be the provisioning of secure Cloud-based services including infrastructure, storage, and web applications through public and private Clouds.

The Public Cloud is a large scale, shared infrastructure but with individually distinct customer hosting environments. The individual environments are architected to meet your business needs while leveraging part of a large infrastructure. The public Cloud, therefore, offers economies of scale and is provided by vendors like those participating in the DOI Foundation Cloud Hosting Services contact.

There are times when security, compliance to regulations and other special needs drive an entity toward tighter control and privacy of its own Cloud, in this case taking on the definition of Internal Cloud.

Services are simply the supply of value added commodities. For the Cloud and specifically for the DOI Foundation Cloud Hosting Services contract, these services, delivered through IDIQ contracts, are:

Database Hosting Services

Web Hosting Services

Development and Test Environment Hosting Services

SAP Application Hosting
Storage Services

Secure File Transfer Services

Virtual Machine Services

The infrastructure burden is owned by the Cloud vendor where they carry the responsibility in providing its customers the ability to ramp up/down services and capacities as required.

Moving to the Cloud takes planning centered around your business, technical and security requirements. The Cloud Customer Portal is dedicated to assisting in that process beginning with providing our customers access through our Request for Cloud Services form. You will be assigned customer support and access to our integrated project team who, with your staff, will help define the end-to-end planning, contracting and transition to Cloud steps.

Gather Requirements

Moving to the Cloud begins with collecting your requirements. This step is critical to beginning an efficient Cloud planning process, taking into consideration the existing system, the business and technical drivers and outcomes anticipated by the stakeholders and end users. Ensuring capture of all critical requirements is accomplished by eliciting requirements by all those stakeholders who use, operate, maintain and depend on the system.

To support this collection process, we offer use of an integrated project team (IPT) to provide you with a structured Cloud Planning Workshop that focuses on the following key activities.

Requirements development begins with the understanding of the system as it currently functions. The IPT facilitates the process using Business and Technical Analysts that specialize in development of stakeholder requirements, and specifically those experienced in infrastructure and applications integration.

Next, the team helps explore the Cloud contract for architecture and service solutions that best meet your requirements. This includes mapping business use cases to potential Cloud models.

Finally, gaps are analyzed, risks are assessed, a statement of work is created and a complete roadmap through the Cloud Customer Portal support process is established.

The DOI awarded a set of contracts valued at up to $10 billion that will expedite the Federal Cloud First Strategy. The contract will yield benefits of $100 million each year from 2016 to 2020 by defining and architecting IT solutions that take full advantage of Cloud computing benefits to maximize capacity utilization, improve IT flexibility and responsiveness, and minimize cost.

Define and Architect the Solution

Request DOI Cloud Contract Information. Use the form to contact us and obtain specific information about using our Cloud contract to meet your organization's needs.

The Cloud Planning Workshop lays the groundwork to define the Cloud services and environment definitions. During this time the IPT will assist in the final readiness for Cloud contracting including preparing supporting documentation required for the contract ordering process.

Leverage the Contract

The DOI Foundation Cloud Hosting Services Contract includes 9 IDIQ contracts, 7 service offerings; and services can be competitively procured from the DOI's 9 Cloud vendors using the DOI Foundation Cloud Hosting Services contract.

The 9 Cloud contract prime vendors include:
Aquilent, AT&T, Autonomic Resources, CGI, GTRI, IBM, Lockheed Martin, Smartronix, and Unisys

The 7 technical service lines offerings are:

seven service lines

Customers using DOI’s Foundation Cloud Hosting Services Contract will be guided through a customer lifecycle consisting of phases, process steps, and activities that are aligned to three main areas: pre-award, award, and post-award. You, the customer, will always know where you are in the lifecycle and what to expect from each phase within it.

request for svcs process

The process begins when you complete and submit the Request for Cloud Services Form. After submitting the form, a customer representative will be assigned to support your move to the cloud.

request form here
Timeline estimates and SLAs for each phase are currently being developed.

Along the way to using the Cloud contract you can rely on a developing community of Cloud technical experts, business owners and contracts specialists. You can get access to blogs, training, web seminars, breaking news, lessons learned, new directions, and other interactions with practicing experts that will be available soon. These experts can help you in developing your considerations and requirements for ongoing system operation and support.

Perform Operations and Maintenance

Several areas of interest to the business and technical owners as the application moves to the Cloud are identified here. During the lead up to the RFQ, you will want to have delineated requirements for some or all of these tools and activities to ensure you have the oversight necessary to perform operations and maintenance management.

Enterprise Scheduling and Workload Automation

Event and Impact Management

Mainframe Automation

Middleware Management

Storage Management

Application Performance Management

Availability and Performance Management

Capacity Optimization

Cloud Operations

Data Management

We will guide you with our experience and lessons learned to make certain oversight into post transition operations and maintenance management are not overlooked.