Solution Framework Guide

Please note, this document is a work in progress. At this time, it is manually generated by PSE.
We will work to automated its creation post-release of the complied engagement delivery material
features within Solution Builder.

For Use Only by VMware and VMware Solution Providers

Not a Customer Deliverable
 Solution Framework Guide

© 2019 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and
intellectual property laws. This product is covered by one or more patents listed at
http://www.vmware.com/download/patents.html.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other
jurisdictions. All other marks and names mentioned herein are trademarks of their respective companies.

VMware, Inc.
3401 Hillview Ave
Palo Alto, CA 94304
www.vmware.com

© 2019 VMware, Inc. All rights reserved.

Page 2 of 23
 Solution Framework Guide

Contents

Contents...................................................................................................3
1. Document Purpose............................................................................6
2. Architecture Models and VVD Alignment...........................................7
2.1 Introduction to Architecture Models...............................................................................7
2.1.1 1 POD without NSX.........................................................................................................................8

2.1.2 1 POD with NSX.............................................................................................................................. 8

2.1.3 2 POD without NSX.........................................................................................................................8

2.1.4 2 POD with NSX.............................................................................................................................. 8

2.1.5 “PS-Custom”.................................................................................................................................... 9

2.2 VMware Validated Design Decisions............................................................................9

2.2.1 Consideration of Risk......................................................................................................................9

3. Framework and Content Documents...............................................11

4. Solution Set Delivery Instructions....................................................12
4.1 General Solution Delivery Guidance...........................................................................12
4.1.1 Introductions.................................................................................................................................. 12

4.1.2 Workshop Data Collection.............................................................................................................12

4.2 Overview of Solution Methodology Phases.................................................................13

4.2.1 Phase: Initiate................................................................................................................................ 13

4.2.2 Phase: Plan................................................................................................................................... 13

4.2.3 Phase: Assess...............................................................................................................................13

4.2.4 Phase: Design............................................................................................................................... 14

4.2.5 Phase: Implement.........................................................................................................................14

4.2.6 Phase: Knowledge Transfer..........................................................................................................14

4.2.7 Phase: Close................................................................................................................................. 14

4.3 Deliverables and Engagement Documents.................................................................15

4.3.1 Framework Documents Definitions...............................................................................................15

4.3.2 Content (Deliverable) Document Definitions.................................................................................16

4.3.3 Content Documents per Microservice Type..................................................................................16

5. Micro-Services Definitions...............................................................17
5.1 Technology Configuration Review Class Services......................................................17

© 2019 VMware, Inc. All rights reserved.

Page 3 of 23
 Solution Framework Guide

5.1.1 VMware Virtualization Health Check.............................................................................................17

5.2 Technology Discovery Class Services........................................................................20

5.2.1 Assess with vRNI for application dependency mapping as part of application migration or disaster
recovery planning......................................................................................................................................... 20
5.2.2 Assess with NI (SaaS) for application dependency mapping as part of application migration or
disaster recovery planning........................................................................................................................... 21

5.3 Design Class Services................................................................................................23

5.3.1 Continuous Availability Design......................................................................................................23

5.3.2 Design NSX-T for Network Virtualization......................................................................................24

5.3.3 Design NSX-V for Micro-segmentation and Security....................................................................24

5.3.4 Design NSX-V for Network Virtualization......................................................................................25

5.3.5 Design vRealize Automation for use in a private cloud.................................................................26

5.3.6 Highly Available Virtual Infrastructure Design...............................................................................27

5.3.7 Hybrid Cloud Extension Design.....................................................................................................28

5.3.8 Log Centralization and Analysis Sizing and Architecture Design..................................................29

5.3.9 On-premises Disaster Recovery Foundation Design....................................................................30

5.3.10 Performance and Capacity Management Sizing and Architecture Design....................................31

5.3.11 Virtualization Design......................................................................................................................32

5.4 Deploy Class Services................................................................................................34

5.4.1 Cloud Business Management of Private Cloud Deploy.................................................................34

5.4.2 Continuous Availability Deploy......................................................................................................34

5.4.3 Deploy AppDefense for Application Security.................................................................................34

5.4.4 Deploy NSX-T for Network Virtualization on ESXi........................................................................35

5.4.5 Deploy NSX-T Foundation............................................................................................................35

5.4.6 Deploy NSX-V for Micro-segmentation and Security....................................................................36

5.4.7 Deploy NSX-V for Micro-segmentation and Security....................................................................36

5.4.8 Deploy NSX-V for Network Virtualization......................................................................................36

5.4.9 Deploy NSX-V for Network Virtualization......................................................................................37

5.4.10 Deploy NSX-V Foundation............................................................................................................37

5.4.11 Deploy NSX-V Foundation............................................................................................................37

5.4.12 Deploy Open Source Toolchain for Continuous Integration with vRA...........................................38

5.4.13 Deploy PKS for use in a Private Cloud..........................................................................................38

5.4.14 Deploy vRealize Automation for use in a private cloud.................................................................38

5.4.15 Deploy vRealize Lifecycle Manager for use in a Private Cloud.....................................................39

5.4.16 Deploy vRealize Log Insight for Log Centralization and Analysis.................................................39

5.4.17 Deploy vRealize Network Insight...................................................................................................40

© 2019 VMware, Inc. All rights reserved.

Page 4 of 23
 Solution Framework Guide

5.4.18 Deploy vRealize Orchestrator with High Availability......................................................................40

5.4.19 Highly Available Virtual Infrastructure Deploy...............................................................................40

5.4.20 Hybrid Cloud Extension Deploy for VMware Cloud on Amazon Web Services............................41

5.4.21 On-premises Disaster Recovery Foundation Deploy....................................................................41

5.4.22 Performance and Capacity Management Deploy..........................................................................42

5.4.23 Virtualization Deploy......................................................................................................................42

5.4.24 VMware Cloud Foundation Deploy Service...................................................................................43

5.4.25 VMware Cloud Foundation Hardware Installation Confirmation Service.......................................44

5.4.26 VMware Cloud Foundation vRealize Automation Deployment......................................................44

5.4.27 VMware Cloud Foundation vRealize Operations Manager Deployment.......................................45

5.4.28 VMware Cloud on AWS Disaster Recovery Deploy Service.........................................................45

5.4.29 VMware Integrated OpenStack Deploy.........................................................................................45

5.4.30 VMware Validated Design for SDDC Deployment of Consolidated Design (Modules below).......46

5.4.31 VMware Validated Design for SDDC Deployment of Region A (Modules below).........................46

5.4.32 VMware Validated Design for SDDC Deployment of Region B (Modules below).........................46

5.4.33 vRealize Continuous Delivery Foundation....................................................................................46

5.4.34 vSphere Integrated Containers Deploy.........................................................................................46

5.5 Consume Class Services............................................................................................ 47

5.6 Integrate Class Services.............................................................................................47
5.7 Interoperate Class Services........................................................................................ 47
5.8 Upgrade Class Services.............................................................................................47

6. Micro-Service Type and Deliverables Reference Table...................47

7. Appendix A: Example Deliverable Scenarios...................................48
7.1 Example 1: Single Solution Set – Design Service.......................................................48
7.2 Example 2: Single Solution Set – Design Service and Deploy Service.......................49
7.3 Example 3: Single Solution Set – Design, Deploy and Integrate Services..................50
7.4 Example 4: Multiple Solution Sets – Varying Services................................................51

© 2019 VMware, Inc. All rights reserved.

Page 5 of 23
 Solution Framework Guide

1. Document Purpose
The Solution Framework Guide document is a supporting reference for those individuals involved in the
delivery of Professional Services Solution Builder derived engagements.
This document contains reference information on the following topics:
 Professional Services Architecture Models

 Framework and Content Document constructs

 General Delivery Guidance on Solution Sets

 Micro-Services Definitions

© 2019 VMware, Inc. All rights reserved.

Page 6 of 23
 Solution Framework Guide

2. Architecture Models and VVD Alignment

The VMware Validated Designs (VVD) provide a fully tested, use case proven, extensively defined
reference architecture that covers all layers of the stack from hardware and virtualization to private cloud
management. Excluding hyper-converged systems such as VMware Cloud Foundation; the VVD provides
the fastest mechanism to deliver a robust private cloud platform.
The level of definition and requirement of the VVD to meet the use cases is such that not all customers
can consume the reference architecture. Historically when this has occurred the outcome of a software
deployment largely sat with the Professional Services Consultant as they navigated through all the
relevant design decisions on a case by case basis. To attempt to reduce the variance in deployment,
Professional Services created the Architecture Review Board to review Professional Services designs.
With customer demand focused on integrations and customizations post deployment; it is more important
to ‘commoditize’ the design and deploy phases of an engagement.
To assist with this; Professional Services Engineering (PSE) has collaborated with the integrated Systems
Business Unit and varying representatives of Professional Services globally to define some ‘architecture
models’. This standardize the topology and the associated design decisions for the VMware products.
Where possible these design decisions align to the VVD. These architecture models are not designed to
detract from the value of the VVD; they are not independently tested, proven for scale or fitness for
purpose of use case like the Validated Designs are. These architecture models are a prescriptive,
standardized set of harvested best practices from the VVD with flexibility in several design decisions such
that they can be broadly consumed.
PSE has embedded these ‘Architecture Models’ into the content provided to Professional Services. The
aim is to provide the PSO Consultant with the best design decision and depending up the ISBU defined
risk of that design decision; either mandate it and define it or provide the best practice decision as the
default with information on alternatives with the associated benefits and consequences.
The topologies in these architecture models are simple to articulate and for customers to understand; the
idea is to identify the most appropriate architecture model as early as possible in an engagement. Once
that decision has been made, which should be obvious, the Consultant can use that Architecture model
context as they utilize PSE provided content (which is all categorized by Architecture Model). This
streamlines many decisions and the engagement as the selection of Architecture Model removes options
and alternatives.

2.1 Introduction to Architecture Models

The following sections describe the fundamental Architecture Models. When PSE reviewed all the VDD
decisions; it became obvious that there were two significant attributes that defined a customer
deployment.
 The customer is entitled to use VMware NSX software defined networking.

 The customer is intending to separate the management workload domain from the compute
workload domains.
These two decisions above have a flow-on effect on other decisions concerning the multi-site
recoverability of management components, cost of hardware, cost of software, size of deployment and
consequentially the type of customer and use case applicable. The use cases and customer profiles in
the sections below are not meant to be exhaustive. They are merely a starting point for consideration for

© 2019 VMware, Inc. All rights reserved.

Page 7 of 23
 Solution Framework Guide

the Professional Services Consultant. The architecture model is often defined by customer constraints
such as:
 Hardware availability

 Budget

 Software entitlement

 Customer capability to operate and manage

Note As of July 1, 2018, PSE has only implemented the architecture called “PS-Custom”. Other
architecture models will be added over time.

2.1.1 1 POD without NSX

The 1 POD without NSX architecture model (PS-001) is defined using a single vCenter server that is
managing all vSphere clusters. The single vCenter server could be managed and hosted on a vSphere
cluster that is hosting only management components; but as there is only a single vCenter and no
management plane separation between compute workload domain clusters and the vCenter hosting
cluster; it is still considered a 1 POD with NSX architecture model.
The typical customer for this type of architecture model is a small commercial customer having a small
number of workloads, likely limited management components, does not require disaster recovery of
management components and has limited resources for hardware and software.
Alternatively, a larger customer may have a use case where that use case aligns with those requirements
above.
Note: This architecture type is not explicitly available in the delivery materials at this time, although the
PS-CUSTOM architecture model (below) can be modified for 1 POD without NSX.

2.1.2 1 POD with NSX

The 1 POD with NSX architecture model (PS-002) is a slight deviation from the architecture model above;
in this instance, the customer is entitled to VMware NSX software-defined networking. They might add
east-west micro-segmentation capabilities, or they might provide management components and/or
workload virtual machines with improved disaster recovery capabilities. They want to implement a
relatively small, but highly automated environment for developers.
Note: This architecture type is not explicitly available in the delivery materials at this time, although the
PS-CUSTOM architecture model (below) can be modified for 1 POD with NSX.

2.1.3 2 POD without NSX

The 2 POD without NSX architecture model (PS-003) is defined by the use of a dedicated vCenter server
that is managing a vSphere cluster dedicated for hosting management components including other
vCenters that manage compute workload domains.
The typical customer for this architecture model is a mid-size commercial and larger; the cost and risk of
management downtime associated with failure of the single management plane in the 1 POD architecture
is considered higher than the cost of additional hardware and software associated with the design and
deployment of a dedicated management domain.

© 2019 VMware, Inc. All rights reserved.

Page 8 of 23
 Solution Framework Guide

This customer would typically be utilizing or plan to utilize several management components; for few
compute workload domains, they must scale out their management plane to support either the number of
workloads or potential number of workloads.
Note: This architecture type is not explicitly available in the delivery materials at this time, although the
PS-CUSTOM architecture model (below) can be modified for 2 POD without NSX.

2.1.4 2 POD with NSX

The 2 POD with NSX Architecture Model (PS-004) is a slight deviation from the Architecture Model
above; in this instance the customer is entitled for VMware NSX software defined networking. They might
add east-west micro-segmentation capabilities, or they might provide management components and/or
workload virtual machines with improved disaster recovery capabilities. they want to implement a highly
automated, scalable private cloud.
Note: This architecture type is not explicitly available in the delivery materials at this time, although the
PS-CUSTOM architecture model (below) is based on this architecture model.

2.1.5 “PS-Custom”
The “PS-Custom” Architecture model is flexible model that starts with the design decisions of the 2 POD
with NSX architecture. With this model as a starting point, deviations are allowed as needed to meet
Customer requirements. The architecture is not forced to align with the VMware Validated Design
Decisions.

2.2 VMware Validated Design Decisions

All the design decisions in the Professional Services Engineering content is in the context of the VDD
decisions where applicable. This includes using the ISBU VMware Validated Design decision ID’s
throughout the content. This allows the Professional Services Consultant to work from a known, validated
decision. It also promotes the use of the VDD with the customer and clearly shows where a design
decision is not aligned.
In the Professional Services Engineering materials, the VDD decisions are mapped to the Architecture
Models and a relevant decision is made whether the Architecture Model aligns to the VMware Validated
Design decision. The Architecture Model design decision could be in one of three states:
 Yes – Fully aligned.
 Flexible – Aligned by default, but the decision could be changed based upon customer
requirement.
 No – Not aligned or not applicable. For example, an NSX related design decision does not
apply to an Architecture Model that excludes NSX.
Decisions that are considered Flexible are typically those that if they had been defined as Yes would have
limited the broad consumption of the Architecture Model by customers.

2.2.1 Consideration of Risk

The ISBU assigns a risk rating to every design decision. With the aim of driving standardization and
minimizing risk, the following approach is taken:
 Flexible and assigned a High Risk by the ISBU

© 2019 VMware, Inc. All rights reserved.

Page 9 of 23
 Solution Framework Guide

These design decisions are included in the Solution Specification workbook to ensure whether
they are raised, and a decision is determined.

 Flexible and assigned a Medium Risk by the ISBU

These design decisions are included in the Solution Specification and the Design Workbook. By
default, it is expected that in a Deploy only engagement that the Professional Services Consultant
would spend minimal time on these decisions. While in a Design Service, these design decisions
are covered to provide a more broadly considered design compared to an engagement that is a
deploy only.

 Flexible and assigned a Low Risk by the ISBU

These design decisions are included in the Solution Specification as a default design decision
that can be modified if the customer specifically requires it. It is expected the Professional
Services Consultant spends extremely limited, if any, time and effort on these decisions. In a
Design Service Design workshop, this level of decision typically resides on a hidden slide that can
be uncovered if the customer specifically wants to discuss it.
 Yes or No for fully aligned or not aligned/not applicable

These design decisions are not under consideration during the engagement. So, they are treated
as Design Assumptions and surfaced in either the Scope of Work as a prerequisite and/or the
Solution Checklist depending upon the level of ISBU defined Risk assigned to that Design
Decision.
For example, a Design Decision where the Architecture Model is fully compliant means that this Design
Decision is mandatory; therefore, it is not something that can be changed during an engagement.
Therefore, it is an assumption that the customer can meet this or accept this design decision. If the risk of
the design decision is considered High, then this design decision is surfaced in the statement of work as a
prerequisite as well as in the Solution Checklist. If the design decision is assigned a medium risk, then it
is surfaced in the Solution Checklist only. If the design decision is low risk, then it is considered something
that a customer can readily meet and it is included only in the Solution Checklist as a low risk design
decision.
The most currently used VMware Validated Design decisions, how they apply to architecture models, their
risk rating and whether they are a Design Consideration or Design Assumption are included in the
framework documents folder of this Solution Set.

© 2019 VMware, Inc. All rights reserved.

Page 10 of 23
 Solution Framework Guide

3. Framework and Content Documents

The IT Value Model Professional Services go to market sales methodology along with PS Solutions
Builder. It provides a Professional Services sales person the ability to craft a solution that is very specific
to a customer based upon standardized building blocks of micro-services. These micro-services describe
how an engagement is conducted.
The offerings in the IT Value Model are termed Solution Sets, comprised of building block micro-services.
They are a packaging construct including several micro-services. Therefore, the same micro-service can
be used multiple times across multiple Solution Sets.
The Solution Set defines what the customer is acquiring and describe the solutions conceptual and logical
models. Deliverables for an engagement are in the context of the Solution Set. Therefore, the deliverables
such as Design Documents would have content that describes the solution. The micro-services do not
define the content or the deliverables; they only define how a component of a solution is executed.
Therefore, we need a means of defining the solution level content and then defining the content related to
the components of a solution.
The components of a solution are people/process/technology related component or VMware Software
Product related component.
The customer deliverables are defined at the Solution Set level; the content that is related to the
components of the Solution are defined at either the product or process level, for the Solution Set. The
content is held separately in separate documents, allowing these components to be reutilized across
different Solution Sets.
The documents that exist at the Solution Set level are referred to as Framework documents and
documents that exist at the Product or Process level as Content documents.
The Content Mapping section in this document has a table that includes all the sections located in each of
the deliverables as defined in these Framework documents and a mapping to where the content for this
section resides in the respective content document.

© 2019 VMware, Inc. All rights reserved.

Page 11 of 23
 Solution Framework Guide

4. Solution Set Delivery Instructions

This section provides detailed instructions on how to deliver the Solution Set effectively. The first section
gives detailed guidance on each micro-service that is attached to this solution set. Take guidance from
the solution builder client to determine exactly which of these micro-services is in scope for the
engagement.

4.1 General Solution Delivery Guidance

This section describes general delivery guidance for the engagement.

4.1.1 Introductions
To gain an appreciation of your audience:
 Have a self-introduction of all the participants.
Introduce yourself and highlight your VMware expertise.
Ask for everyone’s name, email address and role.
Ask each participant why they are attending and what they expect to achieve from the discussions.
Understand the overall project direction and timeline. This understanding is useful in determining what the
customer requires for a successful deployment.
The solution engagement begins with a focus on terminology and an overview. Although all participants
are encouraged to involve for the complete duration of the engagement, the occasional curious
onlookers, who need to understand only the high-level concepts (for example, senior management),
might participate only in the overview sections.

4.1.2 Workshop Data Collection

The solutions framework includes several micro-services types that have an information discovery
element:
 Technology Configuration Review

 Technology Discovery

 Gap Analysis (Assess)

 Design

 Consume

 Integrate

 Interoperate

 Upgrade

 Adoption
It is critically important to your success that you capture the information that is relevant to the slide you
are currently discussing with the customer. The slides have been rationalized and consolidated to a
minimum to streamline delivery.

© 2019 VMware, Inc. All rights reserved.

Page 12 of 23
 Solution Framework Guide

4.2 Overview of Solution Methodology Phases

4.2.1 Phase: Initiate

VMware will conduct a pre-engagement planning call with VMware, Inc. to initiate the project. Topics to be
discussed include:
 Review of project scope and objectives.

 Project timelines, scheduling, and logistics.

 Identification of key customer project team members with whom VMware will work to accomplish
the tasks defined in this SOW.
 Availability of appropriate facilities including, but not limited to, meeting rooms, work locations,
whiteboards, projectors, special access needs, any other pertinent information needed before the
VMware consultant arriving on site.
 Prerequisites and other preparation required in advance for the project kick-off.

 Security and access requirements.

4.2.2 Phase: Plan

The VMware engagement team will lead VMware, Inc. project sponsors and stakeholders in an
engagement kickoff meeting to review expectations about the purpose of the engagement, the delivery
approach, and timelines, the amount of time and effort required from the participants, expected schedule,
activities and work products. Meeting objectives include the following:
 Introduce the VMware team, roles, and responsibilities.

 Describe the project phases and agreement of key dates.

 Agree on communication and reporting processes.

 Validate the project expectations and clarifying roles and responsibilities.

 Explain the expected project results.

 Provide key stakeholders with the required terminology and knowledge to discuss and make
decisions throughout the design process.
 Attendance by key representatives from the various teams is considered mandatory.

 Refer to the product-specific knowledge transfer presentation kits for additional presentations.

 Use the session to facilitate discussions and provoke thought.

 Remind customer participants that the session is intended to give them a quick understanding of
the solution so that they can participate in the next phase (which covers design).
 Keep a running list of questions and issues for consideration in the next phase.

 End the session by discussing, defining, and scheduling the subsequent detailed requirements
gathering and design sessions.

© 2019 VMware, Inc. All rights reserved.

Page 13 of 23
 Solution Framework Guide

4.2.3 Phase: Assess

The assess phase aims to identify the current state and determine the target state from a conceptual level
perspective. This phase aims to define the customer use cases essentially. The deliverable of the assess
phase is a Gap Analysis and Recommendations document.

4.2.4 Phase: Design

The design phase varies depending upon whether the micro-services involved in the specific customer
engagement and whether these micro-services are Design Class services or Extend Class services.
Extend Class services are focused on consumption of a technology platform; while Design Class services
are focused on the infrastructure perspective.

4.2.5 Phase: Implement

The implement phase includes the deployment of technology or process change based on the respective
components prescribed design. This phase also includes a functional test element; in this the consultant
implementing a component (process/technology) performs a functional test of the component to ensure
that at completion of this phase the component meets the requirement.

4.2.6 Phase: Knowledge Transfer

This phase assists the customer with understanding the solution as a whole; this involves multiple
knowledge transfer workshops and partitioned content or a single workshop and content. The Deliverable
of this phase is the Operational Guidelines framework document.

4.2.7 Phase: Close

The project review and conclusion activities include a final presentation that summarizes the engagement
activities performed for the resulting solution. A final set of deliverables will be provided to the customer.

© 2019 VMware, Inc. All rights reserved.

Page 14 of 23
 Solution Framework Guide

4.3 Deliverables and Engagement Documents

The following section outlines the standard engagement and deliverable documents available as part of
the engagement delivery materials (EDM) available within Professional Services Solution Builder. These
documents are broken down into two document sets as outlines in the Framework and Content
Documents section above. These document sets are:
 Framework Documents

 Content Documents

Table 1 Deliverables Mapping Table

4.3.1 Framework Documents Definitions

Delivery materials for solution sets include the following documents:
 Pre-Engagement Meeting Minutes: This document captures customer-centric pre-engagement
coordination discussions including customer messaging, delivery aspects, and customer pain
points. Pre and post sales information may be captured in these meeting minutes. This document
is created and maintained by the Delivery Excellence team.
 Solution Set Overview: This document provides an overview of the specific solution capabilities
and outcomes involved in the pre-sales discussions with the customer. This document is auto-
generated by Solution Builder based upon the what was sold to a specific Customer.

© 2019 VMware, Inc. All rights reserved.

Page 15 of 23
 Solution Framework Guide

 Solution Set Checklist: This document provides a checklist of engagement and technical items to
be validated prior to VMware’s arrival at the Customer’s site. This document is auto-generated by
Solution Builder based upon the what was sold to a specific Customer.
 Engagement Summary: This document provides a closing presentation for the engagement. This
document is created and maintained by the Delivery Excellence team.

4.3.2 Content (Deliverable) Document Definitions

The following section provides a summary the all deliverables for all service types.
 Summary Report: This document provides a summary of Technology Review assessment. (Word
document)
 Summary Presentation: This document provides a summary of Technology Review assessment.
(PowerPoint presentation)
 Datacenter Discovery Workbook: This document provides data captured during a datacenter
discovery assessment. (Excel document)
 Datacenter Discovery Summary: This document provides a formal write-up of data captured
during a datacenter discovery assessment. It may contain recommendations for the Customer.
(Word document)
 Gap Analysis Recommendations: This document provides a summary of the gap analysis
assessment. (Word document)
 Solution Design: This document provides a summary of the design decisions used for a Customer
configuration and deployment of technology.
 Knowledge Transfer Workshop: This document provides materials to be used during knowledge
transfer workshops. (PowerPoint Presentation).
 Adoption Guide: This document provides materials to help customers adopt the products included
in the engagement. (PowerPoint Presentation). Note: The knowledge transfer workshop
presentation may also include adoption content.

4.3.3 Content Documents per Microservice Type

The following section lists which deliverables are associated with each microservice type. These
deliverables are available as part of the engagement delivery materials (EDM) available within
Professional Services Solution Builder.

Micro-Service Type Deliverables

Technology Configuration Review (Health Check)  Summary Report

 Summary Presentation

Technology Discovery  Datacenter Discovery Workbook

 Datacenter Discovery Summary

Gap Analysis (Assess)  Gap Analysis and Recommendations

© 2019 VMware, Inc. All rights reserved.

Page 16 of 23
 Solution Framework Guide

Design  Solution Design

Deploy  Solution Specification Workbook

 Verification Workbook

 Knowledge Transfer Workshop

 Adoption Guide

Adoption  Knowledge Transfer Workshop Adoption

Guide

Consume  Solution Design

 Solution Specification Workbook

 Verification Workbook

 Knowledge Transfer Workshop Adoption

Guide

Interoperate  Solution Design

 Solution Specification Workbook

 Verification Workbook

 Knowledge Transfer Workshop

 Adoption Guide

Integrate  Solution Design

 Solution Specification Workbook

 Verification Workbook

 Knowledge Transfer Workshop

 Adoption Guide

5. Micro-Services Definitions
This section is a reference of all micro-services defined by Professional Services Engineering; it provides
a description of the micro-service, information about the tools that support the micro-service, the structure
of delivery and what deliverables are outcomes of the micro-service.
Unless specified, each microservice will have one sub-component called a module. This
microservice/module structure is mirrored in Professional Services Solution Builder as well as any Service
Scope and Description verbiage generated from Solution Builder.

© 2019 VMware, Inc. All rights reserved.

Page 17 of 23
 Solution Framework Guide

5.1 Technology Configuration Review Class Services

This class of services is used for service types in which VMware PSO will evaluate a Customer’s
implementation of a VMware product against a preferred set of configuration parameters or best
practices. At the end of the evaluation, VMware PSO will offer recommendations to the Customer.

5.2 Technology Discovery Class Services

This class of services is used for service types in which VMware PSO will perform an assessment of a
Customer’s environment using a VMware product. At the end of the evaluation, VMware PSO will offer
present the Customer with the results of the assessment.

5.3 Design Class Services

This class of services is used for service types in which VMware PSO will perform an architectural design
for a VMware product based on a Customer’s specific needs. At the end of the design, VMware PSO will
review the design with the Customer.

5.4 Deploy Class Services

This class of services is used for service types in which VMware PSO will perform deployment of a
VMware product based a standard architecture and standard solution design decisions. Deploy class
services can also follow a Design microservice.
In this case, the Design Service deliverables - notably the Solution Design Document - become the inputs
to the Deploy Service superseding the standard architecture and standard solution design decisions of
the Deploy service.

5.5 Consume Class Services

5.6 Integrate Class Services

5.7 Interoperate Class Services

5.8 Upgrade Class Services

5.9 Adoption Class Services

5.10 Assess Class Services

6. Micro-Service Type and Deliverables Reference Table

7. Appendix A: Example Deliverable Scenarios

This section aims to provide some examples of the deliverables that would be provided to a customer;
given the different micro-services types included in that engagement.

© 2019 VMware, Inc. All rights reserved.

Page 18 of 23
 Solution Framework Guide

7.1 Example 1: Single Solution Set – Design Service

In this example, the customer has purchased a Design Service for Cloud Automation; the Solution Builder
Opportunity Information File contains the one micro-service listed:
 Cloud Automation Design
A few points can be concluded from the name of the micro-service; the major one is that it is a Design
Service and secondarily it is Cloud Automation which implies vRealize Automation.
The Design Service type as per the table in Appendix B only includes one deliverable; the Solution
Design document. So, for this engagement the total deliverables would be:

Deliverable Driven by Phase

Solution Checklist Initiate Phase

Solution Overview Initiate Phase

Solution Delivery Plan Initiate Phase (generated by Solution Builder)

Solution Design Design Phase

Engagement Summary Close Phase

All Deliverables are in the context of Private Cloud Solution Set in this example.

7.2 Example 2: Single Solution Set – Design Service and Deploy

Service
In this example, the customer has purchased a Design Service for Cloud Automation and the Deploy
Service for Cloud Automation; the Solution Builder Opportunity Information File contains the two micro-
service listed:
 Cloud Automation Design

 Cloud Automation Deploy

A few points can be concluded from the name of the micro-service; the major one is there is both a
Design Service and a Deploy Service. The other is that in this instance they are both Cloud Automation
which implies vRealize Automation.
The Design Service type as per the table in Appendix B only includes one deliverable; the Solution
Design document; while the Deploy Service includes a number of deliverables. So, for this engagement
the total deliverables would be:

Deliverable Driven by Phase

Solution Checklist Initiate Phase

Solution Overview Initiate Phase

Solution Delivery Plan Initiate Phase (generated by Solution Builder)

© 2019 VMware, Inc. All rights reserved.
Page 19 of 23
 Solution Framework Guide

Solution Design Design Phase

Solution Specification Implement Phase

Solution Verification Workbook Implement Phase

Install Guides for each Product Implement Phase

Knowledge Transfer Workshop Knowledge Transfer Phase

Adoption Guide Knowledge Transfer Phase

Engagement Summary Close Phase

All Deliverables are in the context of Private Cloud Solution Set in this example.

7.3 Example 3: Single Solution Set – Design, Deploy and Integrate

Services
In this example, the customer has purchased a Design Service for Cloud Automation, the Deploy Service
for Cloud Automation and an Integrate Service with F5; the Solution Builder Opportunity Information File
contains the three micro-service listed:
 Cloud Automation Design

 Cloud Automation Deploy

 Integrate vRealize Automation with F5

A few points can be concluded from the name of the micro-service; the major one is there is a Design
Service, a Deploy Service and an Integrate Service. The other is that in this instance they are all related
vRealize Automation.
The Design Service type as per the table in Appendix B only includes one deliverable; the Solution
Design document; while the Deploy Service includes a number of deliverables. The Integrate Service
(and similarly the Interoperate and Consume service types) do not ‘add’ deliverables; they extend an
existing deliverable with additional content. So, for this engagement the total deliverables would also be:

Deliverable Driven by Phase

© 2019 VMware, Inc. All rights reserved.

Page 20 of 23
 Solution Framework Guide

Solution Checklist Initiate Phase

Solution Overview Initiate Phase

Solution Delivery Plan Initiate Phase (generated by Solution Builder)

Solution Design Design Phase

Solution Specification Implement Phase

Solution Verification Workbook Implement Phase

Install Guides for each Product Implement Phase

Knowledge Transfer Workshop Knowledge Transfer Phase

Adoption Guide Knowledge Transfer Phase

Engagement Summary Close Phase

All Deliverables are in the context of Private Cloud Solution Set in this example.

7.4 Example 4: Multiple Solution Sets – Varying Services

In this example, the customer has purchased a Virtualization Deploy Service as well as the Design
Service for Cloud Automation, the Deploy Service for Cloud Automation and an Integrate Service with F5;
the Solution Builder Opportunity Information File contains the micro-service listed:
 Virtualization Deploy Service

 Cloud Automation Design

 Cloud Automation Deploy

 Integrate vRealize Automation with F5

A few points can be concluded from the name of the micro-service; the major one is there is a Design
Service, multiple Deploy Services and an Integrate Service. The other is that in this instance one of the
Deploy Services is for vSphere while the remaining services are all related vRealize Automation.
The most important point is that there is two Solution Sets that are involved in this engagement;
Virtualized Infrastructure and Private Cloud. Again, this information is provided in the Solution Builder
Opportunity Information File; including the mapping between the micro-services and the related Solution
Set.

© 2019 VMware, Inc. All rights reserved.

Page 21 of 23
 Solution Framework Guide

Similarly, to the other examples; the table below outlines the full deliverables, note the additional column
that categorizes the deliverables into different Solution Sets.

Solution Set Deliverable Driven by Phase

Virtualized Infrastructure

Solution Checklist Initiate Phase

Solution Overview Initiate Phase

Solution Delivery Plan Initiate Phase

Solution Specification Implement Phase

Solution Verification Workbook Implement Phase

Install Guides for each Product Implement Phase

Knowledge Transfer Workshop Knowledge Transfer Phase

Adoption Guide Knowledge Transfer Phase

Engagement Summary Close Phase

Private Cloud

Solution Checklist Initiate Phase

Solution Overview Initiate Phase

Solution Delivery Plan Initiate Phase

Solution Design Design Phase

Solution Specification Implement Phase

Solution Verification Workbook Implement Phase

Install Guides for each Product Implement Phase

Knowledge Transfer Workshop Knowledge Transfer Phase

Adoption Guide Knowledge Transfer Phase

Engagement Summary Close Phase

© 2019 VMware, Inc. All rights reserved.

Page 22 of 23
 Solution Framework Guide

© 2019 VMware, Inc. All rights reserved.

Page 23 of 23