Statement of Work

SPDB Azure Stack HCI PoC

Prepared for

SPDB

Prepared by

Yanzhi Li

Wei Shi

Date: 26 January 2022

Version: V1.0
 Table of contents
Introduction......................................................................................................................................................................................... 1

1. Project objectives and scope............................................................................................................................................... 1

1.1. Objectives........................................................................................................................................................................... 1

1.2. Areas in scope.................................................................................................................................................................. 2

1.3. Areas out of scope.......................................................................................................................................................... 5

2. Project approach, timeline, and deliverable acceptance...........................................................................................6

2.1. Timeline.............................................................................................................................................................................. 6

2.2. Deliverable acceptance process................................................................................................................................. 6

2.3. Project governance......................................................................................................................................................... 7

2.4. Project completion.......................................................................................................................................................... 8

3. Project organization................................................................................................................................................................ 9

3.1. Project roles and responsibilities............................................................................................................................... 9

4. Customer responsibilities and project assumptions................................................................................................. 10

4.1. Customer responsibilities........................................................................................................................................... 10

4.2. Project assumptions..................................................................................................................................................... 10

This Statement of Work (SOW) and any exhibits, appendices, schedules, and attachments to it are made
pursuant to Work Order 7-YN24RNEYE and describes the work to be performed (Services) by Microsoft
(“us,” “we”) for Shanghai Pudong Development Bank Co., Ltd. (“Customer,” “you,” “your”, “SPDB”)
relating to Azure Stack HCI PoC (project).

This SOW and the associated Work Order expire 30 days after their publication date (date Microsoft
submits to Customer) unless signed by both parties or formally extended in writing by Microsoft.

Introduction
Azure Stack HCI is the foundation of the next generation of Microsoft hybrid cloud architectures, using a
hyper-converged version of Windows Server to run virtualized workloads and container platforms on
proven hardware. To better support PDBA's cloud transformation and build a hybrid cloud platform for
the future, Microsoft/SPDB will conduct PoC testing of Azure Stack HCI in the SPDB POC environment.

1. Project objectives and scope

1.1. Objectives
The objectives of this project are to: Validate Azure Stack HCI basic and advanced features,
enhancements, high availability, scalability, co-existence and compatibility with existing private
cloud environment SDDC, security, performance, and management and monitoring capabilities in the
SPDB existing environment, details as shown below:

 Features Testing

Basic and advanced features, enhancements, high availability, scalability, coexistence, and compatibility
with existing private cloud environment SDDC, security, management, and monitoring capabilities.

 Performance Testing

Test storage, network, etc. for potential performance bottlenecks, especially virtualized network
responsiveness/TPS testing under high concurrent loads.

 Container platform Testing

Test the functionality of Azure Kubernetes Services on HCI clusters, including cluster architecture,
scalability, security, networking/CNI, storage, management, and monitoring.

Microsoft Services: Statement of Work

Page 1 of 14
SOWv12.1(WW)(English)(Jan2021)
1.2. Areas in scope
This section outlines the work and activities required to accomplish the objectives set forth in this
Statement of Work.

1.2.1. General project scope

Microsoft will provide Services in support of the following scope.

Features Testing
Area
Cluster & Cluster Set
Description Assumptions
 Create HCI Cluster Customer provide 8
 Create Cluster Set high-performance
 Manage Cluster test hosts
 Update Cluster
 Cluster Monitoring
 Shutdown/Restart Node
 Availability Set Configuration
 Configure & Validate Fault Domain/Update Domain
 Co-Existing with SDDC (AD/SCVMM/NC)

Microsoft Services: Statement of Work

Page 2 of 14
SOWv12.1(WW)(English)(Jan2021)
 Area Description Assumptions
Virtual Machine  Create Windows VM
 Create Linux VM
 RDP in Console
 Import VM
 Resize Memory
 Expand Disk Size
 Attach Disk
 Configure Affinity/Anti-Affinity Rule for VM
 VM Load Balancing
 Enable BitLocker
 Move VM cross Nodes - Manually
 Move VM cross Nodes - Automatically
 Move VM cross Cluster - Manually
 Move VM cross Cluster - Automatically
 Import SDDC VM to HCI Cluster
 Export HCI VM to SDDC
 Migrate VMWare VM to HCI
Software Defined  Two-Way Mirror Volumes Testing host contains
Storage  Three-Way Mirror Volumes SSD/HDD storage
 Mirror-accelerated parity volume
 Expand Volume
 Protect Volume
 Delete Volume
 Create Storage Replica /Stretched Volumes
 Config CSV in-memory Cache
 Storage Tier
Software Defined  Configure Virtual Switch The various IP
Network  Configure Logic Network/Site address segments
 Configure Virtual Network required by the
 Configure Virtual Network Adapter customer to provide
 Configure Network Controller VM from the SDN
 Configure Load Balance VM
 Configure Gateway VM
 Configure Firewall/Access Control List / NSG rule
 Configure Gateway Connection
 Configure Software Load Balance
 Configure S2S VPN Gateway
 Configure VPN
 SDN Network Mirror
 SDN Monitoring
 Configure SDN via SDN Express/SCVMM

Microsoft Services: Statement of Work

Page 3 of 14
SOWv12.1(WW)(English)(Jan2021)
 Area Description Assumptions
Windows VM  Activate The customer
 Update / Patching provides an active
 Domain Join Key or KMS Server
 SCVMM Manageability & PowerShell cmdlet address
compatibility
 SCOM MP Compatibility
System Management  Manage SDDC Cluster/HCI Cluster/Server via WAC
 Manage HCI cluster with SCOM
Azure Integration &  Register To Azure Global Azure
Connection  Azure Site Recovery (VM) subscriptions are
 Azure Backup (VM) available.
 Azure Monitor Set firewall policies
 Azure FileSync to access Azure

Performance Testing
Area Description Assumptions
Live Migration  Move multiple VM cross HCI nodes Performance testing
 Move multiple VM cross HCI clusters is limited to 1
 DiskSPD testing performance months, and limited
Storage
to 1 architect 20 days
Network  Overlay <-> Underlay TPS and 1 consultant 20
 Overlay <-> Underlay Throughput days.

AKS on HCI Testing

Area Description Assumptions
AKS Cluster  Create AKS cluster All testing will be
 Scale AKS cluster based on Microsoft
 Update Kubernetes version test case and test
 Update AKS on Azure Stack HCI scenario, will not test
customer application.
Container  Create Linux Container
Customer will choose
 Create Windows Container
monitor tools and
Network  Cluster network configuration in overlay integrate with AKS,
 CNI Network Plugin Microsoft provide
 Ingress support.
 Load Balance
 Container Network Perf. Testing
Storage  Persistent Volume Claim
 Persistent Volume
Security  AD SSO

Microsoft Services: Statement of Work

Page 4 of 14
SOWv12.1(WW)(English)(Jan2021)
 Area Description Assumptions
 Secret Encryption
Management  Manage AKS via Windows Admin Center

Monitoring  Azure Monitor

 Support customer test on-premise monitoring tool
integration, with customer chosen monitor tool
DevOps  GitOps configuration based on any git repo and Flux
(https://www.weave.works/oss/flux/) (optional)

1.2.2. Software products and technologies

The products and technology listed in the following table are required for project execution. The party
responsible for obtaining the items is indicated.

Product and technology item Version Responsibility Ready by

Azure Stack HCI 20H2 SPDB Week 0

Azure Kubernetes Service Extension for Azure Latest SPDB Week 11

Stack HCI
Windows Admin Center Latest SPDB Week 0

SCVMM 2019/UR3 SPDB Week 1

SCOM 2019/UR3 SPDB Week 1

SDN Express Latest SPDB Week 1

(https://github.com/microsoft/SDN)
Tomcat Latest SPDB Week 7

JMeter Latest SPDB Week 7

Dummy HTTP Application for Stress Testing - SPDB Week 7

1.2.3. Environments
The following environments will be required to deliver the project.

Environment Location Responsibility Ready by

(Setup)

Test on-premise Microsoft SPDB provide 8 high-end physical

servers (nodes) to create cluster set
with 3 clusters (3+3+2)

Azure Subscription: China SPDB Before project start

 For HCI Features

Microsoft Services: Statement of Work

Page 5 of 14
SOWv12.1(WW)(English)(Jan2021)
 Environment Location Responsibility Ready by
(Setup)

Testing;
 For HCI Performance
Testing;

Azure Subscription: Global SPDB Before project start

 For AKS on HCI Testing
If AKS on HCI will not GA,
will use AKS on HCI preview
version.

1.3. Areas out of scope

Any area not explicitly included in the Areas in scope section is out of scope for Microsoft during this
project. Areas out of scope for this project, include the following.

Area Description
Product licenses and subscriptions Product licenses (Microsoft or non-Microsoft) and cloud
service subscriptions are not included, unless otherwise noted
in section “Software products and technologies.”
Hardware Microsoft will not provide hardware for this project.

Data migration Data migration activities are not in scope for this project.

System integration System integration and interfaces are not in scope for
this project.
Product bugs Product upgrades, bugs, and design change requests for
and upgrades Microsoft products are not in scope for this project.
Apply configuration changes Configuration changes related to the application load
associated with this PoC
Go production, dev test environment Any installation in this project will not go production or dev
building test environment.
Process reengineering Designing functional business components of the solution is
not included.
Organizational change management Designing—or redesigning—the Customer’s functional
organization is not included.

Microsoft Services: Statement of Work

Page 6 of 14
SOWv12.1(WW)(English)(Jan2021)
 2. Project approach, timeline, and deliverable acceptance

2.1. Approach
The project will be structured following three distinct phases: Feature Testing, Performance Testing and
AKS Testing. Each phase has distinct activities that are described in the following sections.

Feature Testing Performance Testing AKS Testing

2.1.1. Engagement initiation

Before beginning the project and dispatching resources, the following prerequisites must be completed,
remotely where applicable.

Category Description
Microsoft activities  Conduct an initiation call to commence team formation and
The activities to be performed communicate expectations.
by Microsoft  Document the project launch prerequisites using input from this
SOW.
 Track the status of prerequisites and adjust the engagement
initiation phase start date accordingly.
 Conduct a detailed walk-through of the SOW with the customer
in order to agree on an initial project schedule and approach.
Customer activities  Attend and participate in the initiation call.
The activities to be performed  Assign responsibilities for project initiation and launch
by the Customer prerequisites to accountable customer resources and establish
target completion dates.
 Complete the project initiation and launch prerequisites.
 Staff the project with the required customer resources in the time
frames that were agreed upon in the initiation call.

2.1.2. Feature Testing

During the feature testing phase, the teams (Microsoft and the Customer) will reach agreement on a
shared vision for the project including verification of the identified scope, activities and assumptions
required to realize the vision.

Category Description

Microsoft activities  Build detailed test plan/case for feature testing

The activities to be performed  Conduct test based on test plan/case

Microsoft Services: Statement of Work

Page 7 of 14
SOWv12.1(WW)(English)(Jan2021)
 Category Description

by Microsoft  Build testing report

Customer activities  Provide Resources needed
The activities to be performed  Test Plan/Case review
by the Customer  Report review
Key assumptions  Global Azure subscription and hardware resources are provided.
 Internet outbound connection to Azure is ready

Deliverables

Name Description Acceptance Responsibility

required?

Testing Report Azure Stack HCI Feature Testing Report No Microsoft

2.1.3. Performance Testing

During the Performance Testing phase, the team will develop a detailed plan for the project that includes
a list of activities that are to be completed, and the project schedule.

Category Description

Microsoft activities  Build detailed test plan/case for performance testing

The activities to be performed  Conduct test based on test plan/case
by Microsoft  Build testing report
Customer activities  Provide Resources needed
The activities to be performed  Test Plan/Case review
by the Customer  Report review
Key assumptions 

Deliverables

Name Description Acceptance Responsibility

required?

Microsoft Services: Statement of Work

Page 8 of 14
SOWv12.1(WW)(English)(Jan2021)
 Testing Report Azure Stack HCI Performance No Microsoft
Testing Report

2.1.4. AKS on HCI Testing

During the AKS testing phase, the team will build all of the aspects of the solution and prepare it for final
customer testing.

Category Description

Microsoft activities  Build detailed test plan/case for Azure Kubernetes Service testing
The activities to be performed  Conduct test based on test plan/case
by Microsoft  Build testing report
Customer activities  Provide Resources needed
The activities to be performed  Test Plan/Case review
by the Customer  Report review
Key assumptions

Deliverables

Name Description Acceptance Responsibility

required?
Testing Report Azure Stack HCI – AKS Testing Report No Microsoft

2.2. Timeline
In general, the project will be completed in 3.5 months/14 weeks roughly, the timeline below is a high-
level representation, all dates, and durations are relative to the project start date and are estimates only. If
the project timeline changes significantly, a change request may be issued following the Change
management process.

Microsoft Services: Statement of Work

Page 9 of 14
SOWv12.1(WW)(English)(Jan2021)
If the project starts at 1 Jun. 2021, then project team will complete the scopes accordingly as below table:

Fiscal Year Scopes to be complete

FY21 Complete most of test cases of Feature Testing as 1.2.1

FY22 Complete testing report of Feature Testing

Complete Performance Testing and report
Complete AKS Testing and report

2.3. Project governance

The governance structure and processes the team will adhere to for the project are described in the
following sections:

2.3.1. Project communication

The following will be used to communicate during the project:

 Communication plan: this document will describe the frequency, audience, and content of
communication with the team and stakeholders. It will be developed by Microsoft and the customer
as part of project planning.
 Status reports: the Microsoft team will prepare and issue regular status reports to project
stakeholders per the frequency defined in the communication plan.
 Status meetings: the Microsoft team will schedule regular status meetings, per the frequency defined
in the communication plan, to review the overall project status, the acceptance of deliverables, and
review open issues and risks.

Microsoft Services: Statement of Work

Page 10 of 14
SOWv12.1(WW)(English)(Jan2021)
2.3.2. Risk and issue management
The following general procedure will be used to manage active project issues and risks during the project:

 Identify: identify and document project issues and risks (potential issues that could affect the
project).
 Analyze and prioritize: assess the potential impact and determine the highest priority risks and
issues that will be actively managed.
 Plan and schedule: determine the strategy for managing priority risks and issues, and identify a
resource who can take responsibility for mitigation and remediation.
 Track and report: monitor and report the status of risks and issues.
 Escalate: escalate to project sponsors the high impact issues and risks that the team is unable to
resolve.
 Control: review the effectiveness of risk and issue management actions.

Active issues and risks will be regularly monitored during the project.

2.3.3. Change management process

During the project, either party is able to request modifications to the Services described in this SOW.
These changes only take effect when the proposed change is agreed upon by both parties. The change
management process steps are:

 The change is documented: all change requests will be documented by Microsoft in a Microsoft
change request form and submitted to the Customer. The change request form includes:
o A description of the change.
o The estimated effect of implementing the change including impact on the project scope,
schedule, and fees.
 The change is submitted: the change request form will be provided to the Customer.
 The change is accepted or rejected: the Customer has three (3) business days to confirm the
following to Microsoft:
o Acceptance—the Customer must sign and return change request form.
o Rejection—if the Customer does not want to proceed with the change or does not provide an
approval within three business days, no changes will be performed.

2.3.4. Executive steering committee

The executive steering committee provides overall senior management oversight and strategic direction
for the project. The executive steering committee for the project will meet per the frequency defined in
the communication plan and will include the roles listed in the following table. The responsibilities for the
committee include:

 Making decisions about project’s strategic direction.

 Serving as a final arbiter of project issues.
 Approving significant change requests.

Microsoft Services: Statement of Work

Page 11 of 14
SOWv12.1(WW)(English)(Jan2021)
 Role Organization
Project sponsor Customer

Delivery manager Microsoft

2.3.5. Escalation path

The Microsoft project manager will work closely with the customer project manager, sponsor, and other
designees to manage project issues, risks, and change requests as described previously. The customer will
provide reasonable access to the sponsor or sponsors in order to expedite resolution. The standard
escalation path for review, approval, or dispute resolution is as follows:

 Project team member (Microsoft or the Customer)

 Project manager (Microsoft and the Customer)
 Microsoft delivery manager
 Microsoft and the Customer project sponsor
 Executive steering committee

2.4. Project completion

Microsoft will provide Services defined in this SOW to the extent of the fees available and the term
specified in the Work Order. If additional services are required, the Change management process will be
followed and the contract modified. The project will be considered complete when at least one of the
following conditions has been met:

 All fees available have been utilized for Services delivered and expenses incurred.
 The term of the project has expired.
 All Microsoft activities and in-scope items have been completed.
 The Work Order has been terminated.

3. Project organization

3.1. Project roles and responsibilities

The key project and leadership roles and the responsibilities are as follows.

Customer
Role Responsibilities
Project sponsor  Make key project decisions.
 Serve as a point of escalation to support clearing project roadblocks.
Project manager  Serve as primary point of contact for the Microsoft team
 Manage the overall project.
 Deliver the project on schedule.
 Take responsibility for customer resource allocation, risk management, and
project priorities.
 Communicate with executive stakeholders.

Microsoft Services: Statement of Work

Page 12 of 14
SOWv12.1(WW)(English)(Jan2021)
 Role Responsibilities
 Serve as primary technical point of contact.
 Take ownership of technical architecture and code deliverables.
 Review progress and PoC report

Microsoft
Role Responsibilities
 Manage and coordinate the overall Microsoft project.
 Drive delivery governance and operational excellence
Delivery manager
 Serve as a single point of contact for escalations, billing issues, personnel
matters, and contract extensions.
 Manage and coordinate Microsoft project delivery.
 Take responsibility for issue and risk management, change management,
Microsoft project project priorities, status communications, and status meetings.
manager  Coordinate Microsoft and Microsoft subcontractor resources but not
customer resources.
 Project management may be delivered remotely
 Design the overall solution. Provide guidance based on Microsoft-
Architect
recommended practices.
 Provide technical advice and guidance for in-scope Microsoft products and
technologies based on Microsoft recommended practices.
Consultant  Assist to develop and build technical solutions.
 Assist in development of architectural designs.
 Assist in preparation and delivery of technical presentations to customer.

4. Customer responsibilities and project assumptions

4.1. Customer responsibilities

In addition to Customer activities defined elsewhere in this SOW, the Customer will also be required to:

 Provide information:
o This includes accurate, timely (within three (3) business days or as mutually agreed-upon), and
complete information required for the engagement.
 Provide access to people and resources.
o This includes access to knowledgeable customer personnel, including business user
representatives, and access to funding if additional budget is needed to deliver project scope.
 Provide access to systems.
o This includes access to all necessary customer work locations, networks, systems, and
applications (remote and onsite).
 Provide a work environment.
o This consists of suitable workspaces, including desks, chairs, and Internet access.

Microsoft Services: Statement of Work

Page 13 of 14
SOWv12.1(WW)(English)(Jan2021)
 Manage non-Microsoft resources.
o The customer will assume responsibility for the management of all customer personnel and
vendors who are not managed by Microsoft.
 Manage external dependencies.
o The customer will facilitate any interactions with related projects or programs to manage
external project dependencies.

4.2. Project assumptions

The project scope, services, fees, timeline, and our detailed solution are based on the information
provided by the Customer to date. During the project, the information and assumptions in this SOW will
be validated, and if a material difference is present, this could result in Microsoft initiating a change
request to cover additional work or extend the project duration. In addition, the following assumptions
have been made:

 Work day:
o The standard work day for the Microsoft project team is between 8 AM and 5 PM, Monday
through Friday.
 Standard holidays:
o Observance of consultants’ country-of-residence holidays is assumed and has been factored
into the project timeline.
 Remote working:
o The Microsoft project team may perform services remotely.
 Language:
o All project communications and documentation will be in Chinese. Local language support and
translations will be provided by the Customer.
 Staffing:
o If necessary, Microsoft will make staffing changes. These can include, but are not limited to, the
number of resources, individuals, and project roles.
o Resource availability and dispatch may affect timelines
o Microsoft will engage specific resources as deemed necessary by Microsoft to support a specific
technical area. This could require multiple individuals engaged to support the engagement,
based on technical specialty.
 Informal knowledge transfer:
o Customer staff members who work alongside Microsoft staff will be provided with information
knowledge transfer throughout the project. No formal training materials will be developed or
delivered as part of this informal knowledge transfer.

 Other assumptions:
o All work is to be contiguously scheduled. Any breaks in the engagement calendar must be
scheduled four (4) weeks in advance or will be billed without interruption.
o Customer Lab and / or development facility is available.
o Any delay on delivering customer required items could impact the delivery schedule.
 Customer will choose monitor tools and integrate with AKS, Microsoft provide support.

Microsoft Services: Statement of Work

Page 14 of 14
SOWv12.1(WW)(English)(Jan2021)