vision and scope template - cloud and enterprise · web viewvision and scope template...

Update [Customer Name] in Doc Properties

Software-Defined Data Center

Prepared for

UPDATE CUSTOMER NAME IN DOC PROPERTIESMay 6, 2023Version 1.1

Prepared by

UPDATE AUTHOR FIELD IN DOC PROPERTIESUPDATE AUTHOR POSITION IN DOC PROPERTIESUPDATE AUTHOR EMAIL IN DOC PROPERTIES

Vision and Scope Template


Prior to the parties indicating final agreement by signing a Work Order, the information contained in this document represents the current view of Partner on the issues discussed as of the date of publication and is subject to change. Furthermore, prior to the signing of the Work Order, this document should not be interpreted as an invitation to contract or a commitment on the part of Partner. After the Work Order has been signed, changes to this document will be managed through the Change Management Process described in this document.

IF THIS DOCUMENT IS INCORPORATED BY REFERENCE INTO A WORK ORDER, ALL WARRANTIES APPLICABLE TO THE WORK ORDER APPLY TO THIS DOCUMENT. PARTNER MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

The descriptions of other companies’ products in this document, if any, are provided solely as a convenience to aid understanding and should not be considered authoritative or an endorsement by Microsoft. For authoritative descriptions of any non-Microsoft products described herein, please consult the products’ respective manufacturers. © 2016 Microsoft. All rights reserved. Any use or distribution of these materials without the express authorization of Microsoft is strictly prohibited.

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

ii"document.docx"


Table of Contents

Introduction.....................................................................................................11 Project Objectives and Scope.....................................................................2

1.1 Objectives.................................................................................................................21.2 Areas Within Scope...................................................................................................3

1.2.1 General Project Scope.......................................................................................................31.2.2 Software Products / Technologies....................................................................................61.2.3 Integration and Interfaces................................................................................................61.2.4 Environments......................................................................................................................71.2.5 Training and Knowledge Transfer....................................................................................71.2.6 Testing.................................................................................................................................7

1.3 Areas Out of Scope....................................................................................................9

2 Project Approach, Timeline, and Service Deliverables.............................112.1 Approach.................................................................................................................11

2.1.1 Software Defined Datacenter.........................................................................................11

2.2 Timeline...................................................................................................................202.3 Key Service Deliverables and Acceptance Process..................................................20

2.3.1 Key Project Service Deliverables...................................................................................20

2.4 Project Governance Approach.................................................................................212.4.1 Part-Time Project Management......................................................................................212.4.2 Communication Plan........................................................................................................222.4.3 Issue and Risk Management Procedure........................................................................222.4.4 Change Management Process........................................................................................232.4.5 Escalation Process...........................................................................................................23

2.5 Project Completion..................................................................................................24

3 Project Organization and Staffing............................................................253.1 Project Organization Structure................................................................................253.2 Project Roles and Responsibilities...........................................................................25

Customer Project Roles and Responsibilities..........................................................................25[Partner] Project Roles and Responsibilities...........................................................................26

4 General Customer Responsibilities and Project Assumptions..................284.1 General Customer Responsibilities..........................................................................28

iii"document.docx"


4.2 Project Assumptions................................................................................................29

Tables

Table 1: Example...................................................................................................................2Table 2: Solution Software Required......................................................................................6Table 3: Solution Software Required......................................................................................6Table 4: Required Environments............................................................................................7Table 5: Test Types................................................................................................................7Table 6: Defect Priorities........................................................................................................8Table 7: [Partner] Activities: Envision Phase........................................................................11Table 8: Key Customer Activities.........................................................................................11Table 9: Work Products, Key Objectives, and Documents ([Partner])...................................12Table 10: Key Phase Assumptions........................................................................................12Table 11: [Partner] Activities: Planning Phase......................................................................12Table 12: Key Customer Activities.......................................................................................13Table 13: Objectives and Documents ([Partner]).................................................................13Table 14: Key Phase Assumptions........................................................................................14Table 15: [Partner] Activities: Build Phase...........................................................................14Table 16: Key Customer Activities.......................................................................................16Table 17: Key Documents and Objectives ([Partner])..........................................................17Table 18: Key Phase Assumptions........................................................................................17Table 19: [Partner] Activities: Stabilize Phase......................................................................17Table 20: Key Customer Activities.......................................................................................19Table 21: Key Phase Assumptions........................................................................................19Table 22: [Partner] Activities: Deploy Phase........................................................................19Table 23: Key Customer Activities.......................................................................................19Table 24: Key Phase Assumptions........................................................................................20Table 25: Key Deliverables...................................................................................................20Table 27: Project Management Activities.............................................................................22Table 28: Customer Roles and Responsibilities....................................................................25Table 29: [Partner] Roles and Responsibilities.....................................................................26

Figures

iv"document.docx"


Figure 1: Software Defined Datacenter project timeline (option 1—original equipment manufacturer WSSDO hardware SKU)..................................................................................20Figure 2: Software Defined Datacenter project timeline (option 2—customer-supplied hardware)............................................................................................................................20Figure 3: project organization structure...............................................................................26Figure 4: optional organization chart...................................................................................27

[READ AND DELETE: PLEASE NOTETHIS SOW TEMPLATE SHOULD BE USED FOR FIXED, NON-CUSTOMIZED, CONSULTINGOFFERS THAT ARE IN THE CATALOG AND AVAILABLE IN COMPASSONE.CUSTOM OFFERS WILL BE TREATED AS NON-MSO (MANAGED STANDARD OFFERING)AND WILL REQUIRE THE APPROPRIATE LEVEL OF REVIEW AS DERIVED THROUGH THEENTERPRISE SERVICES AUTHORIZATION POLICY (ESAP)]

v"document.docx"


IntroductionThis Statement of Work (SOW) and any exhibits, appendices, schedules, and attachments to it are made pursuant to the Work Order No. [Click here and type WO#], dated [Click here and type WO date], the terms of which are incorporated herein by reference, by and between [Customer Name] (“Customer”, “you”, “your”) and [[Partner]] (“[Partner]”, “us”, “we”, “our) or affiliate, and sets forth the services to be performed by us related to Windows Server 2016 Software Defined Datacenter (“project”). This SOW, together with the Work Order, represents the complete baseline for scope, services, Service Deliverables, and acceptance applicable to this project. All changes to this document will be managed in accordance with the Change Management Process defined below. Any terms not otherwise defined herein will assume the meanings set forth in the Work Order.

This SOW and the associated Work Order expire 30 days after their publication date, unless they have been formally extended in writing by [Partner].Note that hardware must be procured and installed prior to starting this engagement. Assisting the customer with the hardware decision (especially guidance toward a validated Windows Server Software-Defined Offer) will need to occur during pre-sales phases, or as a separate envisioning and planning engagement.

Page 1"document.docx"


1 Project Objectives and Scope

1.1 ObjectivesIn this project, [Partner] will assist UPDATE CUSTOMER NAME IN DOC PROPERTIES with integrating highly virtualized on-premises Infrastructure-as-a-Service (IaaS) capabilities into your environment using Windows Server Hyper-V, System Center 2016, and Azure Pack. This is a fixed scope project designed to establish foundational understanding of recommended practices for designing, deploying, and operating an on-premises virtualization solution using a Windows Server Software-Defined Offer approved hardware configuration.[Optional] [Customer] is seeking to make use of Microsoft Operations Management Suite (OMS) Log Analytics and backup and recovery. [Customer] has engaged [Partner] to help implement a proof-of-concept Log Analytics and backup and recovery solution that is based on the capabilities found in OMS. The objective of this workstream is to help [Customer] with initial deployment and configuration of OMS within the existing [Customer] Microsoft Azure subscription and its on-premises Windows Server 2016 virtualization environment.

The engagement will address the following projects and workstreams.Table 1: Example

Project or Workstream DescriptionSoftware Defined Datacenter [Partner] and [Customer] will work through a

series of assessment and decision making processes that support the implementation of a highly virtualized software defined datacenter that is based on Windows Server 2016 Hyper-V, System Center 2016, Windows Azure Pack, and Windows Server Software Defined (WSSD) Offer.

[Optional] OMS Log Analytics [Partner] and [Customer] will perform a limited proof of concept that uses a OMS-based log collection and dashboard capability to use the OMS Log Analytics service.

[Optional] OMS backup and site recovery

[Partner] and [Customer] will perform a limited proof of concept using a OMS-based backup and disaster recovery capability to use the Microsoft Azure Site Recovery (ASR) service.



1.2 Areas Within Scope1.2.1 General Project Scope[Partner] will provide the following services:

The development of a vision and scope document or documentation of the objective of the project

Delivery of a Windows Server 2016 technical solution alignment workshop (SAW) and documentation of the workshop in the form of a SAW summary report

Assistance with dependent architectural preparation [such as Active Directory Domain Services (AD DS), Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), Pre-Boot Execution Environment (PXE), and Windows Deployment Services]

Option 1: (default preferred option—original equipment manufacturer) Assistance with the deployment of a Windows Server Software-Defined Datacenter Offer SKU

Assistance with the configuration and deployment of the Windows Server 2016 platform on a selected OEM Windows Server Software Defined Datacenter Solution SKU

Option 2: (do-it-yourself (DIY)option—customer hardware) Assist with a deployment on customer-supplied hardware (compute, storage, and network requirements)

Help configuring and deploying the Windows Server 2016 platform on Windows Catalog certified, customer-supplied hardware

Validation of the Windows Server 2016 compute, storage, and network requirements

Assistance with the development of Windows Server 2016 and Microsoft System Center 2016 on-premises virtualization functional specification for the incorporation in the customer’s planned environment including:

Assistance with the deployment of the Hyper-V role and other related roles on Windows Server 2016

Deployment of the following System Center 2016 components:

Microsoft System Center Virtual Machine Manager (VMM)

Configuration of no more than two clouds, five user roles, and two service templates within your existing VMM environment

Microsoft System Center Operations Manager

Tuning of installed management packs



Configuration of the Operations Manager reporting portal

Service Management Automation (SMA) Microsoft System Center Service Provider Foundation (SPF)

Deployment of Windows Azure Pack using its default minimal installation deployment pattern

Standard integration of the deployed platform with your IT environment in the following manner:

Identity integration

Configuration of an Active Directory Federation Services (AD FS) instance with Update [Customer] in Doc Properties’s existing Active Directory environment to support authentication to the deployed Windows Azure Pack portal

Billing integration

Configuration of Windows Azure Pack to expose Service Reporting data in the deployed solution

Installation and configuration of the Cloud Cruiser billing adapter

Portal integration

Customization of the Windows Azure Pack tenant portal to include customer branding and theming and customization of the help system within Windows Azure Pack

Establishment of a sample customer plan using the Windows Azure Pack tenant portal

Workload integration

Implementation of standard virtual machine provisioning through the use of prebuilt gallery templates or through the integration of supported templates through the use of the Gallery Resource Import Tool (GRIT)

Support for automated virtual machine provisioning using the out-of-the-box functionality of System Center 2016 and a VMM service template that consists of Windows Server 2016 roles, Windows PowerShell, and Desired State Configuration (DSC) automation

[Optional] Integration of OMS with on-premises Operations Manager 2016 and the configuration of the Microsoft Monitoring Agent on ten identified target servers:

Direct installation for servers not monitored by Operations Manager Configuration, through the Operations Manager console, of currently

monitored servers Configuration and demonstration of applicable features, which can include

the following:



Log search [this can include event logs and Internet Information Services (IIS) logs]

Near real-time performance Active Directory assessment Alert management Capacity planning (only if currently enabled in Operations Manager) Change tracking Configuration assessment Malware assessment Security and audit assessment Microsoft SQL Server assessment System update assessment Wire data

The conducting of knowledge transfer sessions—time-permitting within the duration of the engagement—to discuss and demonstrate capabilities, which can include the following: Understanding collected data Custom query capabilities Custom dashboard capabilities

[Optional] Assistance with dependent architectural preparation for OMS Azure Site Recovery service (such as the required Azure Site Recovery service configurations for Azure and Hyper-V or for Azure and VMware), which can include:

Assistance with failover testing using the Azure Site Recovery service Assistance with the configuration of the Azure Site Recovery service and

Microsoft Azure Backup: Configuration of Azure storage as described during the workshop Configuration of the required Azure virtual networks for the Azure Site

Recovery service Added protection for no more than five sample virtual servers consisting

of no more than 500 gigabytes (GB) of total data located in the [Customer] datacenter using a Azure Site Recovery service, which has no more than two simple recovery plans (Simple Azure Site Recovery plans do not contain Azure automation workflows)

Added protection for no more than two sample compatible systems that consist of no more than 100 GB of total data and are located in a [Customer] datacenter that uses Azure Backup



Table 2: Solution Software Required

Solution Component In-Scope Feature

Description or Considerations

Scope Assumptions

Windows Server 2016 Datacenter Edition

In scope Required before the Build phase starts

System Center 2016 Datacenter Edition


Windows Azure Pack (latest update release)

In scope Optional component that supports self-service scenarios

Required before the Build phase starts

Microsoft SQL Server 2016 Enterprise Edition


Azure subscription In scope Optional component Required before the Build phase starts

1.2.2 Software Products / TechnologiesTable 3: Solution Software Required

Operating Systems

Middleware Databases Development Languages

Provided by

Windows Server 2016 Datacenter Edition

System Center 2016 Datacenter Edition andWindows Azure Pack (latest update release)

Microsoft SQL Server 2016 Enterprise Edition

Not applicable Customer

1.2.3 Integration and Interfaces[Optional] Azure OMS backup and site recovery capabilities will be integrated with an existing Azure Site Recovery-supported Hyper-V environment in your datacenter. Integration will consist of connecting Azure infrastructure with the on-premises Hyper-V environment through the use of the Azure Site Recovery service and related technologies. Additionally, Azure Backup will be configured to help protect sample compatible systems in the customer environment. The Azure OMS Log Analytics solution will not be connected with management or monitoring systems other than the Operations Manager tool set that was identified previously.No other integration or interfaces will be included as in scope other than those that are described in this SOW.

1.2.4 EnvironmentsThe following environments are included in the scope of this SOW. The target environment should be a Windows Server Software-Defined Offer supported server configuration. The target environment must include a certified Windows Server Software-Defined (WSSD) offer or Microsoft Windows Hardware Quality Labs



(WHQL)–supported server configuration with access to shared storage and network connectivity that supports the deployment of Windows Server 2016 Hyper-V, System Center 2016, and Windows Azure Pack.[Optional] For the OMS backup and site recovery workstream, the target environment must include an on-premises workload environment that includes physical and virtual machines that can collect log information from an Azure subscription and the deployed Hyper-V environment.Table 4: Required Environments

Environment Location Responsibility

Ready by

Production At [Customer] location

Customer The Build phase as defined in this SOW

[Optional] Azure subscription

[Customer] selected Azure region

Customer Within one week of project start date

1.2.5 Training and Knowledge TransferNo formal training is included in the scope of this SOW.Informal knowledge transfer will be provided throughout the project and during the scope of the project during project collaboration. Informal knowledge transfer is defined as [Customer]’s staff working alongside [Partner] staff.

1.2.6 TestingThe following testing will be performed as part of this SOW.Table 5: Test Types

Test Type Description Responsible

Provides Test Data/Cases

Guidance & Support

Environment

System validation testing—WSSD Offer

Assistance with validation of the deployed Windows Server 2016 operating system, VMM, Operations Manager, service management automation, Service Provider Foundation, and Windows Azure Pack, functionality within the customer’s environment during the Build phase. Testing duration is time-boxed to 5 days.

Customer [Partner] [Partner] Production



Test Type Description Responsible

Provides Test Data/Cases

Guidance & Support

Environment

[Optional] System validation testing—customer-supplied hardware

Assistance with validation of the deployed Windows Server 2016 operating system and System Center 2016 VMM, Operations Manager, Service Management Automation, Service Provider Foundation, and Windows Azure Pack, functionality within the customer’s environment during the Build phase. Testing duration is time-boxed to 5 days.

Customer [Partner] [Partner] Production

[Optional] Azure Site Recovery plan testing

Additional testing will include the availability of workloads and disaster recovery scenarios. Testing duration is time-boxed to 1 day as part of the implementation of the proof of concept (POC).

[Partner] Customer [Partner] Production

As defects are identified during testing, the Defect Priority will be jointly agreed upon by the Customer and [Partner]. The [Partner] team will triage the defect and fix all in-scope P1 and P2 defects. Defect priorities are shown in the following table.Table 6: Defect Priorities

Defect Priority

Description of Priority

P1 Showstopper defect. Development, testing, or production launch cannot proceed until the defect is corrected.Must fix as soon as possible. Defect is blocking further progress in this area.Solution cannot ship and the project team cannot achieve the next milestone.

P2 Defect must be fixed prior to moving to production.Does not affect test plan execution.

P3 It is important to correct the defect. However, it is possible to move forward into production using a workaround.Does not impact functionality as designed (i.e., message change in user experience program).

P4 Feature enhancement or cosmetic defect.Design change from original concepts.



1.3 Areas Out of ScopeAny area that is not explicitly listed in section 1.2 as “within scope” is out of scope for this engagement. The areas that are out of scope for this engagement include, but are not limited to, the following:

Installation of hardware (such as racks and servers) or the sourcing or procurement of hardware or software.

Implementation or integration of existing customer Microsoft, third-party, and in-house developed products, components, or solutions outside of the deployment of the Windows Server 2016 Hyper-V and System Center 2016 environment.

Deployment of the Windows Server 2016 platform on a hardware solution that is not certified.

Deployment of System Center components other than those identified as in scope.

Customization other than that which can be configured within default graphical user interfaces of in-scope products.

Windows Server operating system custom image design or configuration outside of the creation of a virtual machine image created through the use of the Microsoft System Preparation Tool for VMM deployment.

Workload application compatibility, custom application remediation or configuration, or integration of Microsoft or third-party workloads.

Building and conducting user training classes and materials. Physical-to-virtual migration or virtual-to-virtual migration. Establishing network connectivity (Point-to-Site, Site-to-Site or ExpressRoute

connectivity) to [Customer]’s Azure subscription. Customer certification and accreditation activities outside of general support

for customer processes. No data migration is included in the scope of this SOW. Ownership of artifacts for customer change management processes. Operating or maintaining [Customer]’s systems. Creation or maintenance of customized PowerShell workflows as part of the

deployment other those that were identified in the scope in this SOW. Creation or maintenance of an operating system image. Detailed design and formal review of project work products. Development of [Customer]’s operational processes and service level

agreements. Integration with third-party backup infrastructures or third-party site

recovery infrastructures. Setup or configuration of environments other than those defined in this SOW. Source code review. The customer will not provide [Partner] with access

source code or source code information not created by [Partner]. For code not created by [Partner], [Partner] services will be limited to the analysis of binary data only, such as a process dump or a network monitor trace.

[Optional] Added complex application protection. The scope of the POC is to establish the Azure Site Recovery service and promote business continuity and disaster recovery testing for representative virtual machines in order to help provide future protection of workloads.



[Optional] Backup of multitiered applications and services using Azure Backup.



2 Project Approach, Timeline, and Service Deliverables

2.1 Approach[Partner] will use the Microsoft Solutions Framework (MSF) to deliver this SOW. MSF represents an industry-tested solution development approach providing well-defined phases that address development of requirements, architectural design, detailed software design, software development, system testing, and managed release cycles. MSF organizes the solution approach into the following distinct phases during the project lifecycle.

Envision: Envisioning involves creating a business vision and defining the scope of work necessary to bring the vision to reality.

Plan: Planning continues through the development of detailed functional requirements, system and application architectures, the user interface prototype, and a detailed project plan for the remainder of the project.

Build: the Build phase begins with the first iteration of development and culminates with the “functionality complete” milestone (or Beta release).

Stabilize: the Stabilization phase involves testing and acceptance.

2.1.1 Software Defined DatacenterEnvision

Key [Partner] ActivitiesTable 7: [Partner] Activities: Envision Phase

Activity Description DetailsEnvisioning Assist with determining

mutually agreed upon vision and scope for the Software- Defined Datacenter deployment.

Identify the Windows Server 2016 and System Center 2016 requirements that will be needed to support Software Defined Datacenter design, deployment, and implementation.

Key Customer ActivitiesTable 8: Key Customer Activities

Activity DescriptionValidated fabric hardware is available and configured.

Verify that the required compute, storage, and network fabric hardware environment has been procured and is available prior to the start of the project.

Identify management and subject matter Confirm that key personnel who can



Activity Descriptionspecialist participants (management and subject matter specialists) who will be needed for the Envisioning phase.

represent all stakeholders during the Envisioning phase process have been identified.

Verify that key participants will attend Envisioning phase meetings and provide input and promote creation of the vision and scope.

Confirm key personnel are available and engaged in the envisioning process.

Work Products, Key Documents, and Objectives ([Partner])Table 9: Work Products, Key Objectives, and Documents ([Partner])

Service Deliverable DescriptionVision and scope document The vision and scope document will

include the overall scope of the project, project goals, and project objectives. This document also includes a business opportunity and current environment analysis.

Key Phase AssumptionsTable 10: Key Phase Assumptions

Key Phase AssumptionsBecause this effort is short in duration, customer decision makers, architects, and subject matter specialists will participate in the Envisioning phase and requirements gathering. Customer participants in the workshops are empowered to make final decisions during the vision and scope development.

Plan

Key [Partner] ActivitiesTable 11: [Partner] Activities: Planning Phase

Activity Description DetailsSoftware Defined Datacenter fabric and fabric management SAW

Conveyance of the Software Defined Datacenter deployment requirements

This is a review of the Windows Server 2016 Hyper-V and System Center 2016 infrastructure and hardware configuration requirements.

[Optional] OMS Log Analytics

OMS Log Analytics workshop module

This includes a presentation about the OMS log analytics service.


Azure Site Recovery service SAW module

This is an infrastructure-focused review of the requirements and capabilities of the Azure Site Recovery service (time-boxed to half a day).

Azure Site Recovery service and Azure Backup POC planning

Source and target identification (Hyper-V to Azure)

Azure Site Recovery workload identification



Activity Description Details(limited to no more than five sample or representative virtual machines)

Azure Backup workload identification (limited to no more than two sample or representative virtual machines)

Azure Site Recovery planning (limited to no more than two simple recovery plans). Simple recovery plans are those that do not contain Azure automation runbooks.


Activity DescriptionIdentify management and subject matter specialists participants who can help (management and subject matter professionals) during the requirements-gathering process.

Confirm that key personnel who can represent all stakeholders during the requirements-gathering process have been identified.

Verify that key participants will attend planning meetings, provide input, and drive functional specification refinement.

Confirm that key personnel are available and engaged in the requirements-gathering process.

Review the high-level final functional specification.

Review content, answer questions, and provide requested data during the requirements-gathering process.

Help identify and validate prerequisites.

Work Products, Key Documents, and Objectives ([Partner])Table 13: Objectives and Documents ([Partner])

Service Deliverable DescriptionHigh-level functional specification This document contains information

about Windows Server 2016 IaaS product line architecture architectural fabric and fabric management design decisions and architectural patterns.

SAW summary report Summary of customer design decisions as they relate to Windows Server 2016 IaaS product line architecture fabric and fabric management.


Key Phase AssumptionsCustomer decision makers, architects, and subject matter specialists will participate in the



Key Phase Assumptionsrequirements-gathering process.Customer will procure or implement the compute, storage, and networking hardware baseline that was agreed upon during the SAW and functional specification development before the project moves to the Build phase.

Build

Key [Partner] ActivitiesTable 15: [Partner] Activities: Build Phase

Activity Description DetailsNetwork provisioning (lab)

Network infrastructure requirements review assistance

Review of the network infrastructure to confirm that the required configuration changes that were identified in the SAW (VLANs, quality of service (QoS), firewall, and other configurations) have been identified and performed prior to installation.

Storage provisioning (lab)

Storage requirement review assistance

Review of the storage infrastructure to confirm that the required configuration changes that were identified in the SAW have been identified and performed prior to installation.

Hardware validation testing (lab)

Hardware requirement review assistance

Review of the server infrastructure to confirm that required hardware has been deployed.

Infrastructure preparation (DNS, DHCP, AD DS)

Dependent infrastructure requirement review assistance

Review of the dependent infrastructure, including DNS, DHCP, and all Active Directory, to verify that required changes have been performed.

[Option 1—choose one option] Deploy and Configure Fabric Infrastructure

Option 1: Windows Server Software Defined Datacenter Solution SKU

Validate that the Fabric Hardware (Windows Server Software-Defined Datacenter Offer SKU) is available

Assist selected OEM with deployment of Windows Server Software Defined Datacenter Offer SKU

[Option 2—choose one option] Deploy and Configure Fabric Infrastructure

Option 2: customer-supplied hardware (compute, storage, and networking)

Validate that customer-provided, Windows Catalog–certified fabric hardware is available. (WHQL)

Assist with deployment of Windows Server 2016 Hyper-V on customer-selected hardware.

Assist with validation of Windows Server 2016 Hyper-V on customer-selected hardware.

Deploy and Configure Fabric management

System Center fabric management infrastructure deployment

Deploy System Center 2016 VMM, Operations Manager, service provider foundation, service management automation, and Windows Azure Pack.

Configure Tenant Networking

Configure Tenant Tenant networking in System Center configuration

Configure VMM virtual networking and software-defined networking (SDN) for tenants.



Activity Description Details Configure tenant connectivity for

workloads. Identify and establish required

network security settings.Configure Storage Fabric storage

configuration Configure software-defined storage (SDS) integration in VMM for workloads and tenants.

Fabric management Integration

Identity integration Configure the AD FS instance with Update [Customer] in Doc Properties’ existing Active Directory environment to support authentication to the Windows Azure Pack portal.

Billing integration Configuration of Windows Azure Pack to expose Service Reporting data

Install and configure the Cloud Cruiser billing adapter.

Portal integration Customize the Windows Azure Pack tenant portal to include customer branding and theming and customize the help system within the Windows Azure Pack.

Establishment of a sample customer plan using the Windows Azure Pack tenant portal.

Workload integration Implement standard virtual machine provisioning that uses prebuilt gallery templates or the integration of supported templates that use the Gallery Resource Import Tool (GRIT)

Develop a sample service management automation workflow (based on specification and applicable samples).

Develop DSC Workflow based on specifications and applicable samples.

Management integration

Operations Manager integration

Tune installed management packs. Configure the Operations Manager

reporting portal.[Optional] OMS Log Analytics

OMS Log Analytics configuration assistance

Provide help configuring 1 OMS subscription (including administrative access setup).

Integration of OMS with on-premises Operations Manager

Provide assistance with the required steps to integrate OMS subscription with Operations Manager.

Configuration of Microsoft Monitoring Agent on up to 10 identified target servers

Perform direct installation on servers that are not monitored by Operations Manager.

Use the Operations Manager console for currently monitored server configuration.



Activity Description DetailsApplicable feature configuration and demonstration

Features can include: Log searches such as event logs,

IIS logs. Near real-time performance. AD DS assessment. Alert management. Capacity planning (only if currently

enabled in Operations Manager). Change tracking. Configuration assessment. Malware assessment. Security and audit assessment. Microsoft SQL Server assessment. System update assessment. Wire data.


Configure ASR and Azure Backup infrastructure

Configure the Azure Site Recovery service and Azure Backup vault, and verify source and target health and compatibility (the entire Build phase is time-boxed to 3 days).

Assess the deployed Hyper-V environment.

Assess the Azure subscription.Protection and recovery plan development

Assist with the set up and configure business continuity and disaster recovery options of the hybrid cloud infrastructure (the entire Build phase is time-boxed to 3 days), which includes:

Network mapping. Hyper-V configuration. Network access (firewall access, for

example).


Activity DescriptionIdentify management and subject matter professional participants who will be needed for system integration.

To help reduce deployment times, confirm that key personnel have been identified.

Answer questions and provide requested data during system integration.

Confirm that key personnel are available and engaged in the deployment process.

Perform the onsite hardware assessment. Actively assist in the onsite hardware assessment

Perform onsite hardware and virtualized system installation and configuration.

Actively assist in the onsite hardware and virtualized system installation

Review and approve the final version of the deployed solution.

Actively assist in the deployment of the identified System Center 2016 components

[Optional] Configure required permissions in System Center VMM.

Perform the VMM environment permission changes that are needed to support the Azure Site Recovery service.

Complete assigned actions by the agreed-



Activity Descriptionupon due dates.

Work Products, Key Documents, and Objectives ([Partner])Table 17: Key Documents and Objectives ([Partner])

Activity DescriptionHelp deploy the required systems. Not applicable


Key Phase AssumptionsCustomer decision makers, architects, and subject matter specialists will participate in the hardware and virtualization infrastructure deployment.The customer will integrate the private cloud architecture into the lab environment before performing the hardware integration.

Stabilize

Key [Partner] ActivitiesTable 19: [Partner] Activities: Stabilize Phase

Activity Description DetailsSystem validation testing

Help verify that systems conform to the functional requirements. This task is time-boxed to 5 days.

Validate the following system elements:

The compute, networking, and storage scale unit

Virtual machine mobility (this includes live migration and storage migration)

Hyper-V and System Center integration

Baseline virtual machine template development, deployment, and integration testing

Identify key activities that administrators should be able to complete by using the Windows Server 2016 fabric architecture

[Optional] Azure Site Recovery protection and recovery plan testing (this task is time-boxed to 1 day)

Assist with the setup and configure hybrid cloud infrastructure business continuity and disaster recovery options.

Test and validate the following system elements:

Azure Site Recovery disaster recovery scenario through a test failover)

Testing and validation of Azure Site Recovery disaster recovery scenario failover and failback through a standard failover



Key Customer ActivitiesTable 20: Key Customer ActivitiesActivity DescriptionCoordinate resources for, and conduct the testing needed to review, features and functionality.

Coordinate resources for, and conduct all testing related to, features and functionality.

Facilitate any necessary communication or information needed for testing.

Work with [Partner] to identify the project team members.

Make decisions when architectural options are presented.

Develop and communicate support strategy, procedures, and information that will be needed for your help desk and field technical support.

Identify and communicate the support strategy within the organization.

Submit and obtain approvals for the customer change control processes that will be required for production deployment in subsequent phases.Participate in system validation testing.


Key Phase AssumptionsThe customer will coordinate testing resources and communicate the support plan.The customer will, with [Partner] support, perform all testing.

Deploy

Key [Partner] ActivitiesTable 22: [Partner] Activities: Deploy Phase

Activity Description[Optional] Help move deployed workload into production.

Help configure and deploy. Deployment assistance activities are time-boxed to [Insert time 1–4 weeks].

Closeout meeting


Activity[Optional] Facilitate any change requests that are required to implement the POC solution on schedule.[Optional] Provide access to subject matter experts in areas related to POC scope, such as AD DS, storage, and networking to facilitate fast resolution of questions and problems.[Optional] Make decisions when architectural options are presented.[Optional] Lead deployment activities.




Key Phase AssumptionsThe customer will approve and implement change requests in a timely manner.[Optional] The customer will be responsible for internal readiness and communication that will be required to move the POC solution to production.The customer will upload any applicable historical data, install and configure all aspects of the application, and make any application-specific changes that will be needed to make the app production ready.

2.2 TimelineThis project consists of [insert time 6–10] weeks of technical consulting. Envisioning activities will be performed remotely in advance of any onsite work. These activities are critical to help make sure that the prerequisites are met. This is illustrated in the diagram that follows.

Figure 1: Software Defined Datacenter Project timeline (OPTION 1 – OEM WSSDO Hardware SKU)

Figure 2: Software Defined Datacenter Project timeline (OPTION 2 – Customer Supplied Hardware)

2.3 Key Service Deliverables and Acceptance Process2.3.1 Key Project Service DeliverablesThe following table outlines deliverables that will be delivered during the course of the project.Table 25: Key DeliverablesName DescriptionSolution Alignment Workshop summary report

This is a summary of customer design decisions as they relate to the IaaS product line fabric and fabric management architecture ruleset.


Envision/Plan

1 week

Build

4 weeks

Stabilize

1 week

Envision/Plan

1 week

Build

8 weeks

Stabilize

1 week


Name DescriptionHigh-level functional specification

This document contains information about the design decisions and architectural patterns found within IaaS product line fabric and fabric management.

Test cases This Microsoft Excel file contains information about planned tests and results.

[Optional] The following language should be added if any deliverable requires acceptance—delete if not required.

At specified milestones throughout the project, [Partner] will submit completed project Service Deliverables for Customer’s review and approval.

Customer’s use or partial use of a Service Deliverable will constitute acceptance of that Service Deliverable. Customer may provide its acceptance and/or rejection of deliverables electronically via email.

Within three business days from the date of submittal, Customer must either:

Accept the Service Deliverable by signing, dating and returning the Service Deliverable Acceptance Form

OR Provide a written notice rejecting the Service Deliverable, including a single

and complete list describing every reason for rejection.

Service Deliverables shall be deemed accepted unless Customer provides a timely, written rejection notice as described previously.

[Partner] will correct problems with a Service Deliverable that are identified in the written rejection notice, as described previously, and within the scope of this SOW, after which the Service Deliverable will be deemed accepted.

Issues that are outside the scope of this SOW and feedback provided after a Service Deliverable has been deemed accepted will be addressed as a potential change of scope pursuant to the Change Management process outlined in this SOW.

2.4 Project Governance Approach2.4.1 Part-Time Project Management The project will be managed by a part-time Project Manager. Typically, this is a remote role with mutually agreed-upon customer visits if necessary. Prior to the start of the engagement, a mutually agreed-upon coverage plan or meeting schedule will be documented. Because this resource is part-time and the duration of this project is brief, the following operational constraints are assumed.



Table 26: Project Management ActivitiesProject Management Description

Communications Provide one project closeout report, including budget information and time and expense.

Scope management and change control Attend one scope meeting per week remotely. Manage project change control.

Finance Provide a weekly budget burn report as part of the weekly status report that includes [Partner] time and expense .

Schedule Manage the schedule for the [Partner] scope of work and [Partner] resources.

Human resources and staff management Coordinate [Partner] resources (only), including staffing, task assignments and status reporting.

The scope of the [Partner] Part-Time Project Management Service is limited to managing [Partner] and those subcontracted through [Partner].

2.4.2 Communication PlanThe following will be used to provide formal communication during the course of the project:

The [Partner] Project Manager, working in conjunction with the Customer Project Manager, will compile status reports for distribution to both Customer and [Partner] management.

Weekly status meetings will be held to review the project’s overall status, the acceptance of deliverables, the project schedule, and open problems that were noted in the status report.

2.4.3 Issue and Risk Management ProcedureThe following general procedure will be used to manage active project issues and risks during the project:

Identify: identify and document project issues (current problems) and risks (potential events that impact the project).

Analyze and prioritize: assess the impact and determine the high-priority risks and issues that will be managed actively.

Plan and schedule: decide how high-priority risks are to be managed, and assign responsibility for risk management and issue resolution.

Track and report: monitor and report the status of risks and issues, and communicate issue resolutions.

Control: review the effectiveness of the risk and issue management actions.



Active issues and risks will be monitored and reassessed on a weekly basis. Mutually agreed-upon issue escalation and risk management processes will be defined at the outset of the project.

2.4.4 Change Management ProcessDuring the project, either party may request, in writing, additions, deletions, or modifications to the services described in this SOW (“change request”).For all change requests, regardless of origin, [Partner] will submit to Customer [Partner]’s standard Change Request Form, which will describe the proposed changes to the project, including the impact of the changes on the project scope, schedule, fees, and expenses.For all change requests that you originate, [Partner] will have a minimum of two business days from receipt of the change request to research and document the proposed change, and prepare the Change Request Form.You will have two business days from your receipt of a completed Change Request Form to accept the proposed changes by signing and returning the Change Request Form. If Customer does not sign and return the Change Request Form within the time period prescribed previously, the change request will be deemed rejected and [Partner] will not perform the proposed changes.No change to this project will be made unless it is requested and accepted in accordance with the process described in this section. [Partner] will have no obligation to perform or commence work in connection with any proposed change until a Change Request Form is approved and signed by the designated Customer Project Manager and the [Partner] Engagement Manager from both parties.

2.4.5 Escalation ProcessThe [Partner] Project Manager will work closely with the Customer Project Manager, Sponsor, and other designees to manage Project issues, risks, and Change Requests, as described in Sections 2.4.3 and 2.4.4. The standard escalation process for review and approval or dispute resolution is as follows:

Escalation Path Project Team member ([Partner] or Customer) [Partner] Project Manager / Customer Project Manager / Engagement

Manager/ Project Sponsor

2.5 Project CompletionThe project will be considered complete when any of the following conditions is met:



1. All in-scope tasks are complete.2. All funding has been utilized for hours of services delivered and expenses

incurred.3. The period of performance has expired.4. The work order is terminated pursuant to the provisions of the agreement.



3 Project Organization and Staffing

3.1 Project Organization StructureThis section describes the overall project organization structure, reporting relationships, and key project roles.The project will be organized as depicted in the following diagram.

Figure 3: optional organization chart

3.2 Project Roles and ResponsibilitiesThis section provides a brief description of key project roles and responsibilities.

Customer Project Roles and ResponsibilitiesTable 27: Customer Roles and Responsibilities

Role ResponsibilitiesCustomer Project Sponsor

Makes key project decisions, assists in escalating unresolved issues to the Executive Steering Committee, and clears project roadblocks

Customer Project Manager

Primary point of contact for [Partner] team Responsible for managing and coordinating the overall project Responsible for resource allocation, risk management, project

priorities, and communication to executive management


Engagement Manager

Microsoft Project

Manager

Partner Consultant

Partner Senior Consultant

Partner Architect

Customer project sponsor

Customer project

manager

Customer technical lead

Customer team leads


Role Responsibilities Manages day-to-day activities of the project Coordinates the activities of the team to deliver documents

and objectives according to the project scheduleCustomer Technical Team Lead

Primary point of contact for technical activities by team members listed in this table

Coordinates installation and configuration activities for required hardware elements

Primary technical point of contact for the team that is responsible for technical architecture and technical decision making or approvals

Customer Server and Virtualization Lead

Primary point of contact for hardware installation and configuration activities. These can include, but are not limited to, the following:

Installation and configuration of server hardware Interconnection of servers Physical network and storage connectivity Operating system and Hyper-V installation and configuration

Responsible for managing and performing all hardware installation–related activities

Customer Storage Lead

Primary point of contact for storage integration activities. These can include, but are not limited to, the following:

Storage connectivity Provisioning of storage Other storage allocation–related activities

Responsible for managing and configuring all storage-related activities

Customer Network Lead

Primary point of contact for networking integration activities. These can include, but are not limited to, the following:

VLAN configuration and assignment Routing configuration Dynamic IP address assignment

Responsible for managing and configuring all network-related activities

Customer AD DS Lead

Primary point of contact for networking integration activities. These can include, but are not limited to, the following:

Creation of required user accounts Security groups Required Active Directory objects

Responsible for managing and configuring all network-related activities

[Partner] Project Roles and ResponsibilitiesTable 28: [Partner] Roles and Responsibilities

Role Responsibilities[Partner] Engagement Manager

Single point of contact for billing issues, personnel matters, contract extensions, and [Partner] project status

Facilitates formal project document and objectives handover Facilitates project governance activities and leads the Project

Steering Committee, providing advice and guidance on: Project direction and scope Stakeholder communication, issue resolution, and escalation



Role Responsibilities Responsible for [Partner] resource allocation, risk

management, project priorities, and communication with executive management

Gathers and assembles project status reports and project performance reports

Coordinates the activities of the team to deliver documents and objectives according to the project schedule

[Partner] Virtualization Architect

Verifies whether Microsoft-recommended practices are being followed

Leads the envisioning session and the SAW Assists with Windows Server 2016 Hyper-V deployment,

installation, and configuration Assists with System Center 2016 VMM, Microsoft System

Center Service Manager, Operations Manager, Microsoft System Center App Controller, System Center Orchestrator, and Windows Azure Pack deployment, installation, and configuration

Assists with system testing Supports user acceptance testing

[Partner] Virtualization Consultants

Assists with the envisioning session and the SAW Performs Windows Server 2016 Hyper-V deployment, including

installation and configuration Performs System Center 2016 VMM, Operations Manager,

Service Provider Foundation, service management automation, and Windows Azure Pack deployment, installation, and configuration

Performs system testing



4 General Customer Responsibilities and Project Assumptions

4.1 General Customer ResponsibilitiesDelivery of [Partner] services depends upon, among other things, the following:

[Customer]’s involvement in all aspects of the services. [Customer]’s ability to provide accurate and complete information, as

needed. [Customer]’s timely and effective completion of the responsibilities, as

identified herein. [Customer]’s deployment of the selected hardware configuration. The accuracy and completeness of the assumptions, identified in this

document. Timely decisions and approvals by [Customer]’s management. [Customer]’s completion of site readiness activities and hardware setup. All documents and objectives have been accepted at time of delivery by

[Customer].

In addition to any Customer activities identified elsewhere in this SOW, [Customer] will perform or provide the following:

Work with the [Partner] Engagement Manager to deliver the Project on schedule.

Manage Project plans and schedules. Make key day-to-day decisions and provide a single point of contact. Provide personnel who are knowledgeable about [Customer]’s current

systems. Provide business user representatives as required by the project plan. Provide the personnel needed to conduct acceptance testing of the solution. Provide access to necessary [Customer] work sites, systems logons, and

passwords. Provide access to other materials and resources as needed and as advised

by us in advance. Provide suitable work spaces with desks, chairs, telephones, and other

related items. Provide LAN connections that give the [Partner] onsite team access to the

Internet and email. If available, provide remote access capabilities to the [Partner] team during

delivery. Assume responsibility for management of vendors who are not managed by

[Partner]. Provide access with proper licenses to the tools and third-party products that

[Partner] requires to complete its assigned tasks.



Option 1: Acquire and install the selected OEM Windows Server Software Defined Datacenter Solution SKU certified hardware configuration and provide any OEM validation report by the planned delivery start date of deployment activities.

Option 2: acquire and install a WHQL-certified hardware configuration and complete a cluster validation before the planned delivery start date and maintain a copy of the cluster validation report.

[Optional: OMS Log Analytics] One or more Microsoft Azure subscriptions and an Azure Site-to-Site VPN with sufficient bandwidth or ExpressRoute connection.

In performing services under this SOW and the applicable work order, [Partner] will rely upon instructions, authorizations, approvals, or other information provided by [Customer]’s Project Manager or personnel duly designated by [Customer]’s Project Manager.

4.2 Project AssumptionsThe Services, fees, and delivery schedule for this project are based on the following assumptions:

Throughout the project, [Partner] will submit requests for decisions or feedback for [Customer] to complete. Decisions are assigned due dates, and it is assumed that [Customer] will provide the required feedback or make decisions either by the agreed-upon due date or within three business days of the date of submittal. If a decision or feedback is not provided by the due date or within three business days, it will be addressed as a potential change of scope pursuant to the Change Management process outlined in this SOW.

Site readiness activities that are a prerequisite for the completion of [Partner] tasks (hardware deployment, for example) will be complete. Failure to complete site readiness activities that are required for [Partner] to deliver its services according to the agreed-upon project schedule can result in project delays that require Change Orders to this project and additional project costs.

This SOW is predicated on the assumption that Windows Server 2016 Hyper-V will be deployed into [Customer]’s existing AD DS, storage, and network infrastructure.

The Windows Azure Pack implementation will utilize the default “minimal installation” scenario and out-of-box functionality. No customization of the gallery items or services is in scope.

Holidays, vacation, and training time have not been factored into this SOW. All work is to be contiguously scheduled. The standard work week for the project will be Monday through Friday,

except for scheduled holidays. The customer environment will be ready in preparation for the Build and

Deploy phases. [Customer]’s existing infrastructure AD DS, DNS, and other dependent infrastructure is deployed in a supported configuration.



Product licenses. Product licenses (Microsoft or non-Microsoft) will not be provided as part of this project. You are responsible for acquiring product licenses or Azure subscriptions that are required as a result of this project.
