Airwatch

VMware Workspace One Professional - Essentials Data-
sheet
Effective: 01 January, 2017
This document, as well as the software described in it, is furnished under license. The information in this manual may only be used in
accordance with the terms of the license. This document should not be reproduced, stored or transmitted in any form, except as per-
mitted by the license or by the express permission of AirWatch.
Other product and company names referenced in this document are trademarks and/or registered trademarks of their respect-
ive companies.
VMware Workspace One Professional - Essentials Statement of Work | v.2017.01 | January 2017
Copyright 2017 VMware, Inc. All rights reserved. Proprietary and Confidential.
1
Introduction
This service provides for technical support related to the AirWatch Enterprise Mobility Management (EMM) offering.
The services provide the capabilities as defined below in this service description (the Service or Services). The
EMM solution allows customers to activate, profile, and track mobile devices and usage. This Datasheet is between
you the customer (you or Customer) and the VMware entity identified on your invoice for the purchase of this Ser-
vice (VMware). If you are located in the United States, the VMware contracting entity for the Services will be
VMware, Inc. If you are located outside the United States, the VMware contracting entity will be VMware inter-
national Limited.
This Datasheet is for informational purposes only. VMWARE MAKES NO WARRANTIES, EXPRESS OR
IMPLIED, IN THIS DATASHEET. All VMware Service engagements are governed by the VMware professional
Services General Terms and Conditions (http://www.vmware.com/files/pdf/services/tc.pdf). Notwithstanding any
contrary provision in this Datasheet, the Services may be fulfilled by AirWatch LLC, VMwares wholly owned sub-
sidiary, in which case all references in this Datasheet to VMware consultants and VMware teams should also be
deemed to apply to AirWatch consultants and teams. VMware shall remain responsible for the performance of any
services by AirWatch.
By placing your Order for the Services or utilizing the Services and associated software, you agree to the terms of
this Datasheet and the agreements incorporated by reference herein. If you are accepting this Datasheet on behalf
of a company or other legal entity, you represent that you have authority to bind such entity to the terms of this Data-
sheet, in which case you or Customer shall refer to such entity.
This Datasheet replaces all prior versions of the VMware Workspace One Professional - Essentials Datasheets.
AirWatch may update the content of the Datasheet from time to time. The new version will automatically apply once
customers renew their respective support or services package.
1. Service Overview
The deployment will include implementation of a Workspace One environment with integration supported by com-
ponents installed on-premises in the Customers data centers. This project will be organized into four phases: 1)
Introduction and Training 2) Solution Design and Pre-requisites 3) Installation, Configuration and Deploy 4) Optim-
ize and Wrap-Up.
The implementation scope includes:
1.1 Review of associated pre-requisites
1.2 Implementation of AirWatch EMM servers
1.3 Implementation of AirWatch gateway servers
1.4 VMware Identity and Access Management installation/configuration
1.5 Unified Application Catalog and Launcher
1.6 Directory Services Integration
2
2. Service Assumptions
2.1. AirWatch will assist with the installation/configuration of one environment under this Datasheet. The envir-
onment type (SaaS or On-Premises) will be implemented based on the license type purchased by the Cus-
tomer.
2.2. AirWatch will assist with iOS, Android and Windows 10 device types/operating systems only for configuration
and setup of up to five devices of each operating system. Any additional device roll-out beyond the five devices
is out of scope.
2.3. Advanced enrollment options (token based, DEP, Secure Launcher, Apple Configurator, etc.) are out of scope.
2.4. Mobile Email Management integration is out-of-scope of this Datasheet One can purchase the associated ser-
vices offering to incorporate email integration into the scope of the deployment.
2.5. Advanced PC Management (Mac/Windows scripting, product provisioning andApp Stacks) is out of scope of
this Datasheet.
2.6. Alignment of all EMM configurations and policy design with Customers requirements is the responsibility of Cus-
tomer. AirWatch will provide recommendations and assistance.
2.7. EMM configurations are limited to one Organization Group.
2.8. Content integration is out-of-scope of this Datasheet. One can purchase the associated service offering to incor-
porate Content into the scope.
2.9. Procurement and installation of hardware for any components that will be installed on-premise is the respons-
ibility of the Customer. AirWatch may provide recommendations.
2.10. AirWatch will assist in configuring a maximum of five common third-party authentication endpoints. Approved
endpoints are limited to those listed on the VMware Identity Manager Integrations Documentation support
webpage: https://www.vmware.com/support/pubs/vidm_webapp_sso.html. Additional manually configured
endpoints are outside of the scope of the deployment project.
2.11. AirWatch cannot guarantee that individual third party SAML endpoints will integrate successfully with VMware
Identity Manager given unforeseen Customer or service configurations or limitations.
2.12. Customer-specific customization for Identity Manager is out-of-scope of this Datasheet.
2.13. Installation of High Availability (HA) and Disaster Recovery (DR) is out-of-scope of this Datasheet. One can pur-
chase the associated service offering to incorporate HA/DR into the scope of a deployment.
2.14. Certificate usage for authentication is out-of-scope of this Datasheet. One can purchase the associated service
offering to incorporate certificate usage for authentication into the scope of a deployment.
2.15. Review of the console will be provided throughout the configuration; however formal training is out of scope of
this Datasheet.
2.16. The scope of the project cannot be delivered in phases and items not implemented as part of the initial deploy-
ment will be considered out-of-scope.
2.17. Pre-requisites must be completed for all installation components before any installation activities will be per-
formed.
3
2.18. AirWatch and the Customers project management will work closely together to ensure that project scope
remains consistent and issues are resolved on a timely basis. The deployments team will not provide a project
manager as a role under this Datasheet.
2.19. The Services will be performed remotely, unless agreed upon by all parties. Travel expenses will be charged to
Customer.
2.20. All work, documentation and deliverables will be conducted during typical, AirWatch local business hours and
will be provided in English.
2.21. The staffing for this Datasheet assumes all work will be completed within 12 weeks of project initiation. Should
the duration of the engagement be extended, or should the product scope materially change, a budget change
request may be issues.
2.22. Services as described in this Datasheet are deemed to be complete upon any of the following:
a. Completion of all Service Deliverables below
b. Up to a maximum of one calendar year from purchase date; Datasheet expires after 12 months
3. Engagement Timeline
The VMware Workspace One service typically takes 4 - 6 weeks to fully deliver with the pre-defined scope. The
estimated timeline for the engagement is outlined in the following table. The tasks defined each week can shift
based on Customer readiness and availability of both the Customer and the deployments team.
Week Activities
l Introduction and Kickoff meeting
One l Scope definition and success criteria definition
l Technical Architecture definition
Two l Customer completes technical pre-requisites
l Software installation of necessary components
Three - Six l Technical integration with Customer infrastructure
l Configuration and validation of Customer use case
4. Change Management
Should the scope of the initiative change, AirWatch will document the change and provide in writing a change
order document to the Customer requesting confirmation of the change and any applicable costs associated with
the agreed upon change.
4
5. Responsibilities
All AirWatch and Customer responsibilities are listed in the Service Deliverables section. The ownership is defined
as follows:
1. Primary Owner = AirWatch: AirWatch is responsible for delivery of the component, with minimal assistance
from the customers project team.
2. Joint: AirWatch and the Customers project team are jointly responsible for delivery of the component.
3. Primary Owner = CUSTOMER: AirWatch is responsible for assisting the Customer project team as needed to
deliver the component.
6. Service Deliverables
ID Description Tool/Deliverable Primary Owner Comments
Phase 1: Introduction and Training
Required to access
6.1.1 Introduction meeting Joint
resources and training
Understand service assump-
6.1.2 Review Datasheet Datasheet CUSTOMER
tions and scope
Required to access
6.1.3 Register for AirWatch ID on my.air-watch.com myAirWatch access CUSTOMER
resources and training
AirWatch Installation Firewall configuration, server
6.1.4 Review Pre-Installation Requirements Guide, Installation CUSTOMER prep, load balancer con-
Pre-Requisites figuration
Customer Requirements to proceed to the Solution Design Phase
Customer certifies com-
6.1.5 Confirm documentation review CUSTOMER pletion and comes prepared
to Design phase
Phase 2: Solution Design and Pre-Requisites
6.2.1 Solution Design Meeting Joint
Review scope/objectives and key success cri-
6.2.2 AirWatch Scope definition
teria for Customer's deployment
Review Technical Architecture deployment AirWatch Technical Hardware sizing and archi-
6.2.3 AirWatch
options Architecture Guide tecture
Pre-Installation Pre-req clarified with Cus-
Review of technical pre-installation require-
6.2.4 Requirement Work- AirWatch tomer network, database,
ments
sheet server and security teams
6.2.5 Review AirWatch Best Practices Guide Best Practices Guide AirWatch Configuration best practices
Download and setup any required soft-
6.2.6 AirWatch
ware/tools
5
Summarize pre-work, next steps and require-
6.2.7 Customer action items AirWatch
ments for Phase 3
Customer Requirements to proceed to the Deploy Phase
Servers accessible and soft-
6.2.8 Procure virtual and/or physical servers CUSTOMER
ware pre-reqs completed
6.2.9 Stage required OVA files CUSTOMER If Applicable
Configure networking/firewall and service
6.2.10 CUSTOMER Networking rules provisioned
accounts for integration
Complete and return AirWatch Pre-Installation Installation Pre-
6.2.11 CUSTOMER
Worksheet Requisites
Scope of project cannot be
Finalize configuration scope of the deployment Documented scope
6.2.12 CUSTOMER modified without agreed
project for Customer review
change control
Phase 3: Installation, Configuration and Deploy
Step 1: Installation
Enterprise Mobility Management
Pre-Installation Work-
6.3.1 Confirm completion of pre-requisites AirWatch
sheet
AirWatch Installation
6.3.2 Installation of AirWatch EMM server(s) AirWatch If Applicable
Guide
AirWatch ACC Install-
6.3.3 Installation of AirWatch Cloud Connector AirWatch
ation Guide
Identity Management &Unified Application Catalog (VMware Identity Manager)
Configuration of VMware Identity Manager &
6.3.4 AirWatch
Unified App Catalog
Step 2: Configuration
Enterprise Mobility Management (AirWatch)
6.3.5 Configure 1 Organizational Group Joint
6.3.6 Register email domain for auto-discovery Joint
Assistance configuring Directory Services integ-
ration:
Mobile Device Man-
6.3.7 l Assist with creating up to 5 users agement (MDM) Joint
l Assist with creating up to 5 administrators Guide
l Assist with adding one user group
Identity Management &Unified Application Catalog (VMware Identity Manager)
6
Complete Identity Manager Configuration:
l Sync with Active Directory users and
groups
l Integration with a maximum of five Identity and Access Integration with Customer's
6.3.8 Joint
approved third party SAML endpoints Management endpoints for single sign-on
l Configure conditional access
l Configure multi-factor authentication for
supported systems
Configure the following for Unified App Cata-

log functionality (unmanaged and without auto-
matic delivery):
l Cloud Applications (one per app type)
Public/Internal Mobile Applications (one Unified Application Configuration of application
6.3.9 l
Joint
per device type) Catalog and Launcher management policies
l Web Applications (one per device type)

l Native Workspace Application
l App Store integration
Step 3: Deploy
Define Enrollment/Registration Strategy for Defined enrollment meth-
6.3.10 Enrollment Strategy Joint
new devices odology
Successfully enrolled iOS
6.3.11 Assist with registering up to 5 iOS devices iOS devices Joint
devices
Successfully enrolled
6.3.12 Assist with registering up to 5 Android devices Android devices Joint
Android devices
Assist with registering up to 5 Windows 10 Successfully enrolled Win-
6.3.13 Windows 10 devices Joint
devices dows 10 devices
Phase 4: Optimize and Wrap-Up
6.4.1 Implement Monitoring and Maintenance CUSTOMER
AirWatch delivers Soft-
ware Related Ser-
vices completion
6.4.2 Customer Support Transition AirWatch Transition to support meeting
materials and contact
information for sup-
port/CSR.

Airwatch

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Airwatch

Uploaded by

Copyright:

Available Formats

VMware Workspace One Professional - Essentials Data-

Effective: 01 January, 2017

Identity Management &Unified Application Catalog (VMware Identity Manager)

Configure the following for Unified App Cata-

l Web Applications (one per device type)

You might also like