确定 SaaS 要求Identify SaaS requirements

备注

本主题是更大的设计注意事项指南的一部分。This topic is part of a larger design considerations guide. 如果你希望从指南的开头开始,请查看主要主题If you'd like to start at the beginning of the guide, check out the main topic. 若要获取此完整指南的可下载副本,请访问 TechNet 库To get a downloadable copy of this entire guide, visit the TechNet Gallery.

每个 SaaS 解决方案都将具有不同的要求、移动设备管理功能以及与本地网络和平台的集成级别。Each SaaS solution will have different requirements, mobile device management features, and levels of integration with on-premises networks and platforms. 许多 SaaS 解决方案为你提供了试用租户或服务,以评估它们的特性和功能,这是确定哪个解决方案真正满足你的需求的重要部分。Many SaaS solutions offer trial tenants or services for you to evaluate their features and functionality, which is an important part of determining which solution actually meets your needs. 但是,根据平台类型,许多 SaaS 解决方案在特性和功能方面可能有细微的差别。However, many SaaS solutions may have subtle differences in features and functionality, depending on the platform type.

大部分 SaaS 解决方案基于三种云类型:The majority of SaaS solutions are based on three cloud types:

  • 多租户Multi-tenant
  • 私有(专用)Private (dedicated)
  • 混合Hybrid

在对如何使用 SaaS 解决方案管理移动设备做出决策前,你还将需要检查这些类型的云平台体系结构之间的区别,并选择最符合组织总体需求的一项。Before making decisions on how you’ll use a SaaS solution to manage your mobile devices, you’ll also need to examine the differences between these types of cloud platform architectures and choose the one that best fits the overall needs of your organization. 个别 SaaS 解决方案对自定义、功能配置、集成和协作功能等领域具有不同的支持级别。Individual SaaS solutions have differing levels of support for areas such as customization, feature configuration, integration, and collaborative functionality.

云类型Cloud types

多租户 SaaS 解决方案即通常称为“公有”云基础结构的解决方案。Multi-tenant SaaS solutions are what are typically called “public” cloud infrastructures. 当服务的软件体系结构在单个实例中,但服务多个租户或组织时,即是这种情况。This is when the software architecture of the service is in a single instance, but serves multiple tenants or organizations. 该解决方案旨在为每个租户提供其服务(例如用户或设备管理、配置和数据支持)的保留共享。The solution is designed to provide every tenant a reserved share of its services, such as user or device management, configuration, and data support. 租户帐户和服务实际上是分离的,每个访问平台基础结构的租户都在单独的实例中。The tenant accounts and services are separated virtually, with each tenant accessing the platform infrastructure in separate instances. 多租户 SaaS 解决方案通常还提供通过在多个租户之间共享基础结构和分发开销成本赢得的成本节省。Multi-tenant SaaS solutions also typically offer cost-savings earned from sharing the infrastructure and distributing the overhead costs amongst multiple tenants. 大多数移动设备管理平台在多租户 SaaS 平台基础结构中提供。Most mobile device management platforms are offered in a multi-tenant SaaS platform infrastructure.

私有或专用云服务是针对单个组织或租户运营的 SaaS 解决方案的实例。Private, or dedicated cloud services are instances of SaaS solutions that are operated for a single organization or tenant. 这些服务可以是组织托管的私有云服务,也可以是第三方提供商托管的私有云服务。These can either be private cloud services hosted by the organization or private cloud services hosted by a 3rd party provider. 私有云解决方案通常还在服务和安全的领域更有机会实现自定义。Private cloud solutions also typically offer greater opportunities for customization, both in the areas of services and security. 某些专用 SaaS 解决方案提供移动设备管理服务作为更大的私有云租户选项的一部分。Some dedicated SaaS solutions offer mobile device management services as a part of larger private cloud tenant options.

混合 SaaS 解决方案可以提供多租户和私有云基础结构的组合或者托管(多租户或私有)和本地云基础结构的组合。Hybrid SaaS solutions can offer a combination of either multi-tenant and private cloud infrastructures, or a combination of hosted (either multi-tenant or private) and on-premises cloud infrastructures. 混合基础结构可能还包括利用外部云 SaaS 解决方案提供特定类型的服务(例如应用程序),但利用内部资源提供其他类型的服务。A hybrid infrastructure may also include leveraging an external cloud SaaS solution for delivering certain types of services (such as applications), but leveraging internal resources for other types of services. 大多数 SaaS 解决方案能够支持混合云配置,但可能在与本地或其他托管云平台的集成的深度和完整性上有很大差异。Most SaaS solutions offer the ability to support a hybrid cloud configuration, but may vary significantly on the depth and completeness of integration with on-premises or other hosted cloud platforms.

云问题Cloud questions

作为 SaaS 管理生命周期规划的一部分,你将需要回答以下有关规划云类型的问题:As part of SaaS management lifecycle planning, you’ll want to answer the following planning questions about cloud types:

  • 对于存储在 SaaS 解决方案中的移动设备数据,我需要何种级别的安全性?What level of security do I need for mobile device data stored in my SaaS solution?
  • SaaS 解决方案如何处理移动设备的地址入侵检测和数据丢失预防?How does the SaaS solution address intrusion detection and data loss prevention for mobile devices?
  • 对于移动设备或存储在移动设备上的数据,你的组织是否必须符合任何法规、认证或合规性要求?Does your organization have to comply with any regulatory, certification, or compliance requirements for mobile devices or data stored on mobile devices? 如果是,遵循这些要求是否需要特定级别的安全性、自定义、可伸缩性或复原能力?If so, do these require a specific level of security, customization, scalability, or resiliency? 如何审核和报告合规性?How is compliance audited and reported?
  • SaaS 解决方案是否需要与其他将管理移动设备的云服务或平台的连接性?Does the SaaS solution need connectivity with other cloud services or platforms that will manage mobile devices? 如果是,此连接性:If so, is this connectivity:
    • 是预配置还是标准化?Pre-configured or standardized?
    • 是否可自定义?Customizable?
    • 是否受你需要连接到的平台支持?Supported by the platforms you need to connect to?
  • 你是否需要将 SaaS 解决方案与现有本地设备管理基础结构连接?Do you need to connect your SaaS solution with an existing on-premises device management infrastructure? 如果是,此连接性:If so, is this connectivity:
    • 是否受本地设备管理平台支持?Supported by your on-premises device management platform?
    • 是否受 SaaS 解决方案支持?Supported by the SaaS solution?
    • 是否在不需要其他本地物理资源的情况下受支持?Supported without the need for additional on-premises physical resources?
  • 移动设备的基于云的服务、应用程序和进程是否将需要不同级别的安全性、自定义、可伸缩性和复原能力?Will your cloud-based services, applications, and processes for mobile devices require different levels of security, customization, scalability, and resiliency?

可伸缩性Scalability

容易伸缩是考虑或部署 SaaS 解决方案(用于管理组织中的移动设备)的主要原因之一。Ease of scalability is one of the primary reasons for considering or deploying a SaaS solution for managing mobile devices in your organization. 根据定义,公用 SaaS 解决方案通常提供几乎无限的支持任何数量的用户或移动设备的功能。By definition, public SaaS solutions typically offer a virtually limitless ability to support any amount of users or mobile devices. 私有和混合 SaaS 解决方案可能基于可用的组织资源而受制于伸缩限制。Private and hybrid SaaS solutions may be subject to scaling limits, based of available organization resources. 用于支持较大或较小数量的用户或设备的规模增加或减少通常取决于公有云的特定授权模型或每用户/设备定价包。Scaling increases or decreases to support greater or lesser number of users or devices usually depends on a specific licensing model or per user/device pricing package for public clouds.

可伸缩性问题Scalability questions

作为 SaaS 管理生命周期规划的一部分,你将需要回答以下有关规划云可伸缩性的问题:As part of SaaS management lifecycle planning, you’ll want to answer the following planning questions about cloud scalability:

  • 你的组织对于移动设备和应用程序支持基础结构中的增长或收缩具有何种类型的短期和长期规划?What type of short and long-term plans does your organization have for growth or contraction in mobile device and application support infrastructure?
  • 你的组织需要如何快速地扩展或收缩移动设备管理支持服务?How rapidly will your organization need to scale mobile device management support services upward or downward?
  • 在 SaaS 解决方案中需要支持的移动设备和/或用户的初始数量是多少?What are the initial number of mobile devices and/or users that need support in the SaaS solution? 此数量在明年发生更改的可能性有多大?How likely is this number to change in the next year? 今后 3 年呢?The next 3 years? 今后 5 年呢?The next 5 years?
  • 需要 SaaS 解决方案支持的移动设备的数量是否会按规律变化(例如季节波动)?Does the number of mobile devices needing SaaS solution support change on a regular pattern (such as seasonally)? 它是否会根据活动或非活动组织项目的数量而发生变化?Does it change according to the number of active or inactive organization projects?
  • SaaS 解决方案性能是否会根据支持的移动设备和用户的规模而发生变化?Does SaaS solution performance change depending on the scale of supported mobile device and users? 如果是,发生在哪些领域?If so, in what areas? (节点、数据、处理等)如果测量、报告和审核伸缩性能?(nodes, data, processing, etc.) How is the scaling performance measured, reported, and audited?

辅助功能Accessibility

轻松访问 SaaS 解决方案是 SaaS 体系结构的另一个重要组成部分。Easy access to the SaaS solution is another key component of the SaaS architecture. 由于 SaaS 解决方案托管在基于云的基础结构上,因此管理员、用户和设备可以从可访问 Internet 的任何位置访问它。Because the SaaS solution is hosted on a cloud-based infrastructure, it’s accessible by administrators, users, and devices from any location that has access to the Internet. 移动设备的管理通过浏览器来实现。Administration of mobile devices is done via a browser. 由于许多 SaaS 解决方案提供商运营在地理上分散的数据中心,因此用户和设备可以“在本地”访问平台,通常避免了在连接到在地理上遥远的终结点时可能产生的延迟。Because many SaaS solution providers operate geographically diverse datacenters, users and devices can access the platform “locally”, often avoiding latency and delays that can be associated with connecting to geographically distant endpoints. 通常还可以通过将 SaaS 解决方案与本地设备管理平台集成来扩展可访问性。Accessibility can also typically be expanded by integrating the SaaS solution with on-premises device management platforms.

可访问性问题Accessibility questions

作为 SaaS 管理生命周期规划的一部分,你将需要回答以下有关规划云可访问性的问题:As part of SaaS management lifecycle planning, you’ll want to answer the following planning questions about cloud accessibility:

  • 你的组织中是否存在特定的移动设备浏览器要求?Are there specific mobile device browser requirements in your organization? 如果是,SaaS 解决方案是否支持所需的浏览器?If so, does the SaaS solution support the required browser(s)?
  • 移动设备用户是否对应用程序或服务需要任何特殊的可访问性要求?Do mobile device users need any special accessibility requirements for applications or services?
  • 你的组织是否需要访问位于与用户设备或本地基础结构相同的地理位置的 SaaS 基础结构?Does your organization need to access the SaaS infrastructure located in the same geographic as the user devices or your on-premises infrastructure? 如果跨国际边界存储或移动移动设备数据,是否负法律责任?Are there legal ramifications if mobile device data is stored or moved across international borders?

复原Resiliency

由于 SaaS 基础结构基于云并且托管在多个数据中心中,因此复原相比传统的本地托管服务通常容易受到较低的稳定性或故障的影响。Since the SaaS infrastructure is cloud-based and hosted across multiple datacenters, resiliency is typically subject to less instability or outages than traditional on-premises hosted services. 多位置服务主机提供针对基于地理位置的故障和服务中断的保护,方法是使用故障转移基础结构和进程在多个数据中心节点上复制数据。Multi-location service hosts offer protection against geographic-based outages and service interruptions by using fail-over infrastructure and processes to replicate data across multiple datacenter nodes. 在故障转移期间,原始地理位置区域中可能保留也可能不保留对服务的访问权限,具体取决于 SaaS 解决方案。Depending on the SaaS solution, access to the service may or may not remain in the original geographic area during a fail-over.

复原问题Resiliency questions

作为 SaaS 管理生命周期规划的一部分,你将需要回答以下有关规划云复原的问题:As part of SaaS management lifecycle planning, you’ll want to answer the following planning questions about cloud resiliency:

  • 在发生主 SaaS 解决方案故障转移时,移动设备管理服务将会受到怎样的影响?In the event of primary SaaS solution fail-over, how will mobile device management services be impacted?
  • 存储在 SaaS 解决方案上的移动设备数据将如何在基于云的基础结构中共享?How will mobile device data stored on the SaaS solution be shared in the cloud-based infrastructure?
  • 如果主移动设备 SaaS 数据中心不可用,则故障转移数据中心是否与主数据中心位于相同的地理位置区域?If the primary mobile device SaaS datacenter isn’t available, are the fail-over datacenters in the same geographic region as the primary datacenter? 故障转移数据中心是否可以位于移动设备运行所在的国际边界之外?Is it OK for fail-over datacenters to be located outside the international borders from which the mobile devices are operating?
  • SaaS 解决方案是否具有用于概述对移动设备管理的支持的已定义服务级别协议 (SLA)?Does the SaaS solution have a defined service level agreement (SLA) outlining support for mobile device management?

最新服务Up-to-date services

SaaS 解决方案还能够通过最新的应用程序版本、功能、安全性、更新和 Bug 修复使应用程序和服务保持最新状态。SaaS solutions also are able to keep the applications and services up-to-date with the latest application version, features, security updates, and bug fixes. 通常非常快速地发布这些更新,有时甚至每天都发布。Often these updates are published very quickly, sometimes even on a daily basis. 更新可能立即对所有客户可用,也可能以分阶段的方式向一小群客户发布,具体取决于 SaaS 解决方案。Depending on the SaaS solution, updates may be instantly available to all customers or released in a phased approach to smaller groups of customers. 一个最大的好处是当为一位客户修复 Bug 时,可以使用该服务将该修复程序轻松应用到所有客户。One of the biggest benefits is that when a bug is fixed for one customer, the fix can be easily applied to all customers using the service.

服务问题Services questions

作为 SaaS 管理生命周期规划的一部分,你将需要回答以下有关规划云服务的问题:As part of SaaS management lifecycle planning, you’ll want to answer the following planning questions about cloud services:

  • 移动设备管理特性和功能在 SaaS 服务中的更新频率是多少?How often are mobile device management features and functionality updated in the SaaS service?
  • 特性和功能更新对你的任务关键移动设备应用程序和服务有哪些影响?What impact will feature and functionality updates have on your mission-critical mobile device applications and services?
  • 临时还是按计划将 SaaS 解决方案特性和功能更新部署到客户?Are SaaS solution feature and functionality updates deployed to customers on an ad hoc or planned schedule?
  • SaaS 解决方案是否支持为个别组织免除服务范围的更新?Does the SaaS solution support exemptions from service-wide updates for individual organizations?
  • SaaS 解决方案对于移动设备应用程序和移动设备管理特性和功能是否有不同的服务更新计划?Does the SaaS solution have different service update schedules for mobile device application and mobile device management features and functionality?
提示

请务必记录下每个答案,并了解答案背后的基本原理。Make sure to take notes of each answer and understand the rationale behind the answer. 之后的任务将详细阐述可用选项以及每个选项的优点/缺点。Later tasks will go over the options available and advantages/disadvantages of each option. 回答这些问题将帮助你选择最符合你的业务需求的选项。Answering these questions will help you select the option that best suits your business needs.