Optimization Scorecard
Important:The product name for this user guide has changed from Foundation and Cloudscape to Business Service Discovery and Migration Planning. Previous UI pages known as Foundation have changed to Business Service Discovery. Previous UI pages known as CloudScape have changed to Migration Planning.
This report is designed so you can easily prioritize your application portfolio for a myriad of optimization activities. As an example, if you use some of the complexity criteria you could understand which apps in your portfolio would be easiest to migrate versus hardest in terms of complexity.
| • | Standard Templates |
| • | How the Math is Done |
| • | Available Criteria |
This area will contain preloaded criteria, tags, and weights to produce scorecards without the need of the user to complete the scorecard criteria selection process.
Note:More information to come in this section.
All criteria start out with a base 100 points available to be granted. The criteria type determines how many points of the base 100 an object receives. The product of this is then multiplied against the weight to determine the final score.
There are two primary types of scoring criteria:
|
Type |
Purpose |
Description |
Final Calculation Example |
|
Relative |
Provide a relative scaling score regardless of the assessment size |
We will rank all applications from top to bottom based on the selected criteria. The rank number is then divided by the total number of rank-able items to produce a percentile score. |
Percentile * 100 * Weight = Score |
|
Boolean |
Provide a scoring mechanism for unrankable or scalable criteria. Boolean means that there is a TRUE/FALSE statement as to whether a given object has the selected criteria. |
If a given object (device or stack) has the select criteria (e.g. rscore:rehost) then it will receive 100 points. Note:If it is a device level criteria, the stack will receive 100 points for every device that matches the selected criteria. |
(Count of Objects w/ selected Criteria) * 100 * Weight = Score |
For more details on the criteria see Available Criteria.
The following table lists the available criteria.
|
Name |
Description |
Use Case |
Type |
Calculation |
|
Predictive Cloud Run Cost |
Prioritize application stacks with lower cloud cost according to selected Cloud Provider. The source of this pricing can be found on the IaaS Cloud Pricing page |
Economical |
Relative |
Percentile rank all apps by sum of hourly cost |
|
High Connectivity |
Prioritize application stacks with high amounts of connectivity. Connectivity being defined as the number of times we've seen this app connecting to any device. This is the opposite of Low Connectivity. |
Complexity |
Relative |
Percentile rank all apps by sum netstat connections |
|
Low Connectivity |
Prioritize application stacks with low amounts of connectivity. Connectivity being defined as the number of times we've seen this app connecting to any device. This is the opposite of Low Connectivity. |
Complexity |
Relative |
Percentile rank all apps by sum netstat connections |
|
High Number of Users |
Prioritize application stacks that connect to many IPs in a chosen location(s). A distinct IP is used to correlate to a user. This is the opposite of Low Number of Users. |
Business Impact |
Relative |
Percentile rank all apps by count of distinct IPs coming from a specific location(s) |
|
Low Number of Users |
Prioritize application stacks that connect to few IPs in a chosen location(s). A distinct IP is used to correlate to a user. This is the opposite of Low Number of Users. |
Business Impact |
Relative |
Percentile rank all apps by count of IPs coming from a specific location(s) |
|
Location Prioritization |
Prioritize application stacks that have more devices located in a specified location(s). |
Data Center Lease Running Out |
Boolean |
Devices the chosen location(s) get points |
|
Devices Over Provisioned |
Prioritize application stacks that have more devices that are over provisioned (not using their available resources). This is the opposite of Devices Under Provisioned. |
Economical |
Relative |
This is calculated by pulling all servers in the environment whose 95th percentile CPU or Memory utilization is less than or equal to 50% of their provisioned resources. The CPU and memory percentiles are then added together to form a single utilization metric. This metric is then ranked against the rest of the over provisioned population. |
|
Devices Under Provisioned |
Prioritize application stacks that have more devices that are under provisioned (exhausting their available resources). This is the opposite of Devices Over Provisioned. |
Performance |
Relative |
This is calculated by pulling all servers in the environment whose 95th percentile CPU or Memory utilization is greater than 50% of their provisioned resources. The CPU and memory percentiles are then added together to form a single utilization metric. This metric is then ranked against the rest of the under provisioned population. |
|
Low Device Count |
Prioritize application stacks that have a low number of devices in them. This is the opposite of High Device Count. |
Complexity |
Relative |
Percentile rank all apps by count of servers |
|
High Device Count |
Prioritize application stacks that have a high number of devices in them. This is the opposite of Low Device Count. |
Complexity |
Relative |
Percentile rank all apps by count of servers |
|
Large Storage Footprint |
Prioritize application stacks that are using a large amount of storage. This is the opposite of Small Storage Footprint. |
Economical & Complexity |
Relative |
Percentile rank all apps by sum of utilized storage |
|
Small Storage Footprint |
Prioritize application stacks that are using a small amount of storage. This is the opposite of Large Storage Footprint. |
Speed & Complexity |
Relative |
Percentile rank all apps by sum of utilized storage |
|
Stack Tags |
Prioritize application stacks that have a specified tag key value pair. |
Custom |
Boolean |
Stacks having the selected key value pair (Tag Key : Tag Value) get points |
|
Device Tags |
Prioritize application stacks that have devices that have a specified tag key value pair. |
Custom |
Boolean |
Stacks having devices having the selected key value pair (Tag Key : Tag Value) get points |