Assessment

The phase in which the cloud readiness and other key metrics defining the cloud compatibility of the application landscape are determined is the Assessment section. This phase typically follows the phase in which IT assets and application data is collected. The Assessment is the first step where active decisions in the context of a cloud transformation are made. As all other sections of the Transformation Cockpit, the Assessment has a global and an application mode.

The global mode allows you to view your complete application landscape in terms of cloud readiness, migration timing, migration risk, cloud benefit and container readiness. The list of applications can be filtered by clicking on the various chart components, such as the different bars or dots in the scatter plot.

When selecting an Application asset from the left sidebar, you are presented with the assessment results of the selected application - the application mode of the Assessment section. All the results stem from an underlying, configurable set of Assessment Rules.

After selecting an application from the sidebar, you'll find the aggregated assessment results at the top of the page. At the bottom, a detailed breakdown of the results. In between are the options for choosing the 6R Migration Strategy and the Migration Timing.

Overall Assessment Results

The overall assessment results are the results of aggregating all assessment rule outcomes for the application in scope. Some outcomes will be shown as recommendations which have 3 different possible types:

• PROHIBITS: Assessment outcomes which cannot (or should not) be applied to the application as it would be in contradiction to the assessment result.
• SUGGESTS: Assessment outcomes which are suggested to be applied by the assessment outcome.
• REQUIRED: Assessment outcomes which need to be applied in order to comply with the assessment rules specified.

Selecting an outcome will filter the assessment rules to these relevant of the selected output. The filter can reset by clicking the symbol above the rules on the top right. These recommendations are about the migration strategy and the cloud service strategy which you choose. The suggested migration strategy will be pre-selected by default (green border around the box) below the recommendations, but you can still chose to select another strategy. Depending on the migration and cloud service strategy you get a suggested cloud proposal in the Target Architecture which will appear in Saved Proposals (suggested proposals are marked as such with a tag on top of the card). This proposal will not be selected automatically. You can still select a proposal with different strategies in the Target Architecture.

The assessment recommendations should give you an idea of which target architecture preferences are important and could or should be adapted. The preferences should be aligned with the recommendations to get the best possible cloud proposals. If you get a warning, this means that some target architecture preferences are not aligned with the recommendations and need an adaption. You can adapt the preferences and will get some recommendations on the single settings. This allows us to provide you with cloud proposals that best suit your needs, and you have the option of defining settings that are more or less important in your eyes.

The results are explained below by way of example.

Data Completeness

To execute calculations, each Assessment Rule needs specific information about the application, the application's deployment stack, or related business layer assets. The degree to which there is enough data available to execute all rules is indicated by the data completeness. Prior to analyzing the results, it is crucial to monitor each application's degree of data completeness. Since the assessment results might not be trustworthy, you should think about gathering extra data if the data completeness is rather poor.

Note

Txture displays assessment findings independent of the level of completeness attained in the data. Results are displayed unless there is nearly no data available. You must constantly be conscious of the fact that low-quality data compromises the accuracy of the assessment's findings. You must decide for yourself how much you can trust the results if the data quality and completeness are poor.

Cloud Readiness

An application's readiness for migration can be quickly determined by looking at its cloud readiness. The outcomes of all the rules that have cloud readiness as a result are compiled into the cloud readiness score. The first apps to be moved are those with a high cloud readiness (low hanging fruits). The cloud readiness score is a number that ranges from 0 to 100, where higher numbers indicate better results.

Cloud Benefit

Applications where a cloud deployment can yield significant benefits are highlighted by the cloud benefit.
The cloud benefit is expressed as a number between 0 and 100, where larger numbers indicate superior performance.

Migration Risk

The risk associated with moving an application to the cloud is indicated by the migration risk. Usually, applications with a high migration risk are moved later in time.
A number between 0 and 100 represents the migration risk. High values should be interpreted negatively since they indicate increased risk, as opposed to cloud readiness or benefit.

Migration Strategy

A key result of any assessment is the migration strategy. As part of the assessment, Txture determines which 6R Migration Strategy is most feasible for each application. These strategies focus on the process of moving your applications and data to the cloud. They tell you how to migrate your existing assets:

• Rehost (Lift & Shift): Move the application “as-is” with minimal changes.
• Replatform: Modify the application to take advantage of cloud features (e.g. making changes to the application code, configuration, or infrastructure).
• Repurchase: Replace the application with a cloud-based service (SaaS).
• Refactor: Completely redesign the application for the cloud.
• Retire: Remove applications that are no longer needed.
• Retain: Keep some applications on your existing infrastructure for now.

Cloud Service Strategy

In addition to the migration strategy, one or several possible cloud service strategies are shown: Cloud Infrastructure, Containerization, Cloud Runtime Platforms, or Managed Services. These strategies deal with how you will run your applications and leverage cloud services once migrated. They define the specific cloud-based environment you’ll use:

• Cloud Infrastructure: The application is deployed in the cloud on infrastructure-as-a-service offerings, such as virtual cloud servers.
• Containerization: Package your application in containers for portability and isolation.
• Cloud Runtime Platforms: Utilize platforms designed for specific application types (e.g., Java Runtime Environment in the cloud).
• Managed Services: Use cloud provider services for tasks like infrastructure management, security patching, and database management.

Migration Timing

The suggested migration timing provides an approximate timeline for phasing in the application migration. Creating migration waves and a migration roadmap is a great usage for this classification.

Strategic Cloud Provider

This outcome shows which cloud provider is strategically recommended for the assessed application. For example, if an application communicates with another application that is already hosted at certain cloud provider, the same provider will be recommended, to e.g. decrease latency.

Assessment Results Breakdown

For further transparency, Txture provides a detailed analysis of all the outcomes at the bottom of the Assessment page when it is in app mode. This perspective aids in your comprehension of the results. The rules are assigned to the following four categories:

1. Application complexity: This category contains rules relating to an application's complexity. This comprises, for example, communication protocols employed, information security importance, and protocol encryption.

2. Technical configuration: This category contains rules concerning the technological complexity of the application's deployment stack. This covers, for example, the presence of bare metal or mainframe installations, as well as the percentage of already virtualized components of the deployment stack.

3. Business perspective: This category contains rules concerning the impact of this application on your business. This includes, for example, whether the program serves essential business activities, is necessary for business continuity, or is nearing the end of its lifecycle.

4. Data risk: This category contains rules relating to the application's data risk. This includes, for example, if technical application components operate in various regions or countries, whether this application communicates person-identifying information or processes or stores confidential information.

• Rule categories are shown to the left of this view (see screenshot above). There you can find aggregated assessment outcomes for the according category.
• To the right, you can find the rules of the currently selected category. You can switch between categories by selecting a category card.
• When a rule is properly executed, the result is displayed on the right. Additionally, you can check if any of the data needed to properly execute each rule is missing for that rule.
• Using the bell icon on the right, you can turn off a rule if you determine it isn't applicable to the application you are assessing.

Insights into Assessment Rules

If you are uncertain how a rule works, you can get more information by hovering over the small question mark symbol next to each rule. You will also see the rule's data requirements and the output parameters that the rule affects.

The screenshot below shows details about the rule “Critical business processes are supported”:

• If data is available, this rule checks the property “Business Criticality” of assets of the type “Business Processes” that are linked to the application in scope.
• The rule increases the migration risk score if highly critical business processes are linked to the application.
• A click on “Show 1 affected element” reveals the business process that is linked to the application in scope.

Assessment Result Decisions

To make a well-informed decision about a migration strategy, you must first understand the concept of the 6R Migration Strategies. In case you don't know the 6Rs yet, you can find out more in our blog post.

You have the option to follow Txture's Assessment results or go with your own judgment. After you confirm your choice using the Select button, your decision will be logged in the application asset's properties.

Making decisions in conjunction with the stakeholders of the applications is advised. Use the Comments or Assessment Key Observations feature to document reasons for your decision. While commenting is useful during the decision-making process, you can also fill in Assessment Key Observations in the corresponding text field (see screenshot above). Unlike comments, the assessment key observations are saved in the application asset's properties. This means that you can create reports based on significant observations entered during an application's assessment phase.

Note

Make decisions only if you have sufficient data completeness or you have concluded that a lower data completeness is appropriate for this application.