Use > Plan > Application Portfolio Management > Optimization Types

Optimization Types

Each optimization record is associated with a optimization type. The optimization type defines the algorithm logic and directs how the optimization result is calculated. Currently, Application cloudification is the only optimization type supported. It provides users with a quick way to identify the optimal cloud-based delivery model of an application within the target portfolio.

The analysis is divided into two primary categories: business suitability and technical suitability. Each category is composed of six dimensions. For details of these dimensions, see the Configuration tab.

The following tabs are included:

General tab

This tab contains the following basic information of the optimization type.

Field Description
Title The title of the optimization type. Currently, Application cloudification is the only optimization type supported.
Description A description that captures the details of the record.
Model A classification applied to optimization type. Currently, Application cloudification model is the only model supported.
Created by The name of the user that created the record.
Creation time The time that the record was created.

Configuration tab

This tab shows how the cloudification recommendation are calculated:

Category Dimension Description
Business alignment Regulatory Whether regulatory restrictions are identified that might prevent the application from moving into a public-cloud environment.
Security Whether there are security constraints identified for the application.
Workload variability Whether there are any technical workload variability issues that might prevent the application from moving into a public-cloud environment.
Service availability Whether the availability service level required by the application is aligned with most major public cloud service providers to date.
Geography Whether there are any geographic impediments for moving the application into a public-cloud environment.
Vendor support Whether vendor support issues are identified that might prevent the application from moving into a public-cloud environment.
Technical alignment Infrastructure compatibility Whether the application is tied to individually-defined servers or legacy operating systems.
Interfaces Whether there are issues identified with the application interfaces that might prevent the application from moving to a public-cloud environment.
Architecture Whether there are any architecture issues that might prevent the application from moving into a public-cloud environment.
Performance Whether the performance requirements of this application are compatible with public cloud environments, in terms of bandwidth and latency characteristics.
Internet suitability Whether the application utilizes non-internet technologies or requires performance, reliability, or security greater than expected standard internet connectivity.
Cloud operating model Whether there are any proprietary restrictions identified that might prevent the application from being compatible with a public-cloud environment.

By clicking the title of each dimension, you can view the survey questions that fall into this category from the right pane.

The decision of the cloud-based delivery model follows the Cask Principle. The security level of the following cloud-based delivery models is in descending order:

  1. On-premise infrastructure (most secured)

    This delivery model reflects a traditional on-premise (physical or virtualized infrastructure) delivery model that for some organizations is inherently more suited for their organizational structure.

  2. Private cloud

    This delivery model brings the cloud “in house”. It reflects a private cloud using automation and virtualization technologies to deliver pools of scalable compute, storage, and I/O resources on-site.

  3. Virtual private cloud

    This delivery model still provides a private cloud but in a vendor managed environment. The cloud environment is provided at a service supplier location and usually is highly standardized.

  4. Public cloud (least secured)

    This delivery method reflects a public cloud in the traditional sense, whereby resources are dynamically provisioned using a self-service model.

If the algorithm result of any dimension is on-premise, the delivery model should be On-premise. The Public cloud delivery model is recommended only when the algorithm results for all dimensions are Public cloud.

Sample report tab

This tab contains two optimization reports of the sample data.

Note The reports are not intended to provide a definitive answer as to whether this application should or should not move to the cloud. It is intended to provide potential cloud suitability from a business and a technical point of view.

Field Description
ID The application ID.
Title The name of the application.
Business suitability The optimal cloud solution for the business.
Technical suitability The optimal cloud solution for the technical infrastructure.
Recommendation The final recommendation for the cloud delivery model.
View details A graphical report of the score of each dimension.

Related topics