Datacenter Infrastructure and Management

Vision and Scope

4-Dec-13

Version 2.0 Final

Prepared by

<partner name><partner name>

MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, our provision of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

The descriptions of other companies’ products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.

Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Datacenter Infrastructure and Management, Version 2.0 Final
Prepared by [Delivery Consultant]
“Vision and Scope" last modified on 30 Sep. 13

Datacenter Infrastructure and Management

Revision and Signoff Sheet

Change Record

Date / Author / Version / Change Reference
[Date] / [Delivery Consultant] / # / Initial draft for customer review

Reviewers

Name / Version Approved / Position / Date

Table of Contents

1 Introduction 5

2 Opportunity Statement 6

2.1 Opportunity Statement 6

3 Project Vision and Scope 8

3.1 Vision Statement 8

3.2 Benefit Analysis 9

3.3 Project Requirements 9

3.4 Business Requirements 10

3.5 Functional Requirements 10

3.6 Operational Requirements 10

3.7 Technical Requirements 11

4 Scope of the Project 12

4.1 Project Objectives 12

4.1.1 Business Objectives 12

4.1.2 Technical Objectives 12

4.2 Scope 13

4.2.1 In Scope 13

4.2.2 Out of Scope 14

4.3 Acceptance Criteria 15

4.4 Operational Critieria 15

5 Risk Management 17

1 Introduction 7

2 Opportunity Statement 8

2.1 Opportunity Statement 8

3 Project Vision and Scope 10

3.1 Vision Statement 10

3.2 Benefit Analysis 11

3.3 Project Requirements 11

3.4 Business Requirements 12

3.5 Functional Requirements 12

3.6 Operational Requirements 12

3.7 Technical Requirements 13

4 Scope of the Project 14

4.1 Project Objectives 14

4.1.1 Business Objectives 14

4.1.2 Technical Objectives 14

4.2 Scope 15

4.2.1 In Scope 15

4.2.2 Out of Scope 16

4.3 Acceptance Criteria 17

4.4 Operational Critieria 17

5 Risk Management 19

Datacenter Infrastructure and Management, Version 2.0 Final
Prepared by [Delivery Consultant]
“Vision and Scope" last modified on 30 Sep. 13

Datacenter Infrastructure and Management

1 Introduction

<Text in this format indicates instructions to the writer/editor of the document and should be removed before providing the document to the customer>.

[Customer] has selected the Microsoft Datacenter Infrastructure and Management offering to consolidate and optimize management and control of its infrastructure system and application platforms, as well as to address some key challenges around the design and deployment of a private cloud infrastructure. The goal of the Datacenter Infrastructure and Management solution offering engagement is to help organizations develop and implement private cloud infrastructures quickly while reducing both complexity and risk. The IaaS PLA provides a reference architecture that combines Microsoft software, consolidated guidance, and validated configurations with partner technology such as compute, network, and storage architectures, in addition to value-added software components.

The private cloud model provides much of the efficiency and agility of cloud computing, along with the increased control and customization that are achieved through dedicated private resources. By implementing private cloud configurations which align to the IaaS PLA, Microsoft and its services and hardware partners can help provide organizations both the control and the flexibility that are required to reap the potential benefits of the private cloud.

The IaaS PLA utilizes the core capabilities of the Windows Server operating system (OS), Hyper-V, and System Center to deliver a private cloud infrastructure as a service offering. These are also key software components that are used for every reference implementation. The target architecture is implemented through application of the pre-defined solution patterns identified in the PLA, featuring selected components of the Microsoft Windows Server Hyper-V and System Center solution. Such approach secures repeatability and standardization of the core capabilities, reducing project’s risk, while allowing extensive customization and adaptation of the solution to the customer’s specific needs and environment.

The purpose of this document is to provide a sufficient level of details about each element of the solution architecture, explaining what the project will build and deploy. This document is an outcome of an envisioning meeting during which all requirements (business, functional, technical, operational) are shared and discussed. This Vision and Scope document does not cover the implementation strategy of the solution or its design. Implementation information is contained in the Scope of Work and outcome documentation of the Solution Alignment Workshop.

2 Opportunity Statement

The Datacenter Infrastructure and Management offering reference architecture combines Microsoft software, consolidated guidance, and validated configurations with partner technology such as compute, network, and storage architectures. This offering can help organizations adopt:

· End-to-end monitoring - Monitor infrastructure and applications across the enterprise

· Private cloud- Infrastructure spanning multiple physical locations to support the organization in the event of catastrophic failure of the primary datacenter

· Hybrid cloud - Extending enterprise IaaS into the public cloud using Windows Azure, and extending fabric management across both private and public cloud to form a hybrid cloud infrastructure

· Virtual desktop infrastructure – VDI solutions built using the Microsoft virtualization and management platform

· Monitoring, incident and change management - Enabling the upgrade or planning of a large deployment of monitoring, incident and change management of backup using System Center.

2.1 Opportunity Statement

Organizations today are demanding dynamic, agile systems that can support their constantly changing business needs. IT decision-makers are challenged to quickly deploy well-architected complex data center environments and processes in order to support increasing business demands. To maximize the value of their next deployment organizations should consider:

· Eliminating disparate systems – Owning and maintaining multiple infrastructure and management systems is taxing on IT budgets and resources

· Removing infrastructure silos – Allowing each group to purchace and maintain their own IT assets encourages poor utilization patterns

· Managing service levels – Many applications require higher service levels and organizations must reduce the impact of both planned and unplanned outages

Lowering the cost of IT – Reliance on Tier 1 systems escalates the cost of delivering and maintaining infrastructure, stifling an IT organization’s ability to transform alongside the changing needs of the business.

3 Project Vision and Scope

3.1 Vision Statement

<Guidelines for a Project Vision statement:

· Purpose: Establish the project’s purpose and introduce vision of the engagement’s success and solution’s value for the customer.

· Length: One paragraph at maximum. Best Vision statements are written in one sentence.

· Guidelines: Balance all of the interests to arrive at a single vision statement; bring to light any enterprise architecture implications early.

Clearly and concisely describe the future, desired state of the customer’s environment when the project is complete. This can be a restatement of the opportunity; however, it is written as if the future state has already been achieved. This statement provides a context for decision making. It should be motivational to the project team and to the customer.

Why: A shared Vision Statement among all team members helps ensure that the solution meets the intended goals. A solid vision builds trust and cohesion among team members, clarifies perspective, improves focus, and facilitates decision making.>

[Customer] has the vision of implementing a consolidated, automated and optimized Datacenter Infrastructure and Management solution, building an integrated service management capability across heterogeneous and highly complex private cloud ecosystem.

This project fits into this vision by providing key functionalities and capabilities required to deliver integrated IT service management vision.

3.2 Benefit Analysis

< Benefit analysis section describes how the customer will gain value from the proposed solution. Section should connect the business goals and objectives with specific functional requirements to be realized from the project. These expectations should be clearly stated and be specific, measurable, attainable, realistic and timely (SMART framework). Section could also be extended through addition of following sub-sections:

3.2.1. Business goals and objectives

3.2.2. Business metrics

3.2.3. Business assumptions and constraints

3.2.4. Benefits statement

Why: Benefits analysis demonstrates that contractor fully understands the customer’s situation. It also defines the customer’s business needs, which may provide vital information when making solution and technology recommendations.>

Through implementation of the integrated Datacenter Infrastructure and Management solution [Customer] is aiming to gain the following benefits:

§ Flexible storage offers diverse storage choices that deliver performance, efficiency, and innovation while taking advantage of industry-standard hardware.

§ Continuous availability provides cost-effective, highly available services with protection against a wide range of failures and outages.

§ A complete virtualization platform delivers a fully isolated, multi-tenant environment with tools that can help ensure service level agreements (SLAs) are met, monitor resource use for reporting, and support self-service delivery.

§ Connectivity to cloud services using a common identity and management framework for more secure and reliable cross-premises connectivity.

§ Infrastructure foundation for Hybrid Cloud, Virtual Desktop Infrastructure (VDI), and Large or Complex Deployments

3.3 Project Requirements

<Identify what the solution must do. These requirements can be expressed in terms of functionality (for example, a registration Web site solution will allow the users to register for events, arrange for housing, and so on) as well as the rules or parameters that apply to that functionality (for example, the user can only register once and must stay in housing approved by the travel department). Requirements exist at both the user level and the organizational level. Please refer to the results of the Solution Alignment Workshop, as well as relevant IaaS PLA documentation to build the content of this section.

Please edit recommended text in order to reflect specifics of the particular scenario.

Why: User and organizational requirements are the key inputs to developing product scope and design strategies. Requirements are the bridge between the usage analysis and solution description. A complete statement of requirements demonstrates that project team understands its customer’s needs. The statement also becomes the baseline for more detailed technical documentation in the planning phase. Good requirements analysis lowers the risk of downstream surprises.>

Information described in the following sections defines business, functional, operational and technical requirements that must be met for the Datacenter Infrastructure and Management engagement to be successful.

3.4 Business Requirements

The Datacenter Infrastructure and Management solution offering should provide [Customer] with a Datacenter Infrastructure and Management solution featuring:

· Integrated and consolidated Infrastructure Management capability, including management of heterogeneous environment, abstraction of infrastructure resources and in-depth performance and fault management capability

· Improved SLA and service availability through end-to-end IT service monitoring and recovery

· Risk mitigation through process optimization and service deployment standardization

Process improvement through automation and decomposition of key processes and activities.

3.5 Functional Requirements

The Datacenter Infrastructure and Management solution offering solution should satisfy following functional requirements:

· End-to-end performance and fault management of the heterogeneous IT environment (infrastructure)

· Seamless integration with existing IT management systems

· Extensive knowledge base for managed infrastructure, including full health model and customized operations monitoring of the scoped environment

· Full management capabilities across physical and virtualized resources

· Abstraction of the key infrastructure resources (compute, network, storage and virtualization) in order to simplify resource provisioning and augment functional capabilities