Читайте также: |
|
Deploy service assets in patterns that are most effective in delivering value to customers. For example, multiple segments exist within internal and external markets. Each segment may have distinct requirements and common requirements with respect to other segments. Segments may exist within an organization such as the various user profile s and activity patterns discussed earlier in Section 5.5.3. Deployment of service assets should be in patterns that most effectively deliver the required utility and warranty in each segment across the Service Catalogue. Some segments may require dedicated capacity at one level even if they share lower levels of infrastructure with other segments (Figure 7.13). Customer s are willing to pay a premium for the privilege, making it easier for such a deployment pattern to pass the requirements of Financial Management.
Figure 7.13 Example of a pattern for deployment of assets based on market segments
A template for deploying asset s is defined by the need to provide high levels of warranty for services in terms of capacity and continuity. In such cases, rather than have dedicated resource s, it is necessary to have shared service asset s to provide multiple levels of redundancy (Figure 7.14). Such patterns are also useful for service provider s to reduce the footprint of expensive infrastructure and to build economies of scale.
Figure 7.14 Example of a shared services pattern for capacity and continuity
Deployment patterns in Service operation by themselves define operational strategies for customers. Apart from the deployment of service assets, such strategies may include a particular set of service design s, service level options (or limits), and charging policies that recover the costs of assets.
Дата добавления: 2015-11-14; просмотров: 60 | Нарушение авторских прав
<== предыдущая страница | | | следующая страница ==> |
Pricing as a design constraint | | | Hosting the Contract Portfolio |