Using the planning settings screen to configure how applications are costed and planned including ROI projections
The planning settings screen can be found under the main planning menu.
Default settings will be configured, which can all be edited by clicking the edit button at the top of the screen.
The base values section is where you can set the values that will be used when calculating the duration and effort that it will take to complete the application's transformation work.
The transformation is divided into tasks and an effort (in days) is entered for each task for each different 7R option. The final column is the duration (in working days) that the work is going to be completed over.
These are the base values for a LOW COMPLEXITY & LOW-RISK application and will be used as the basis for more complex and higher-risk applications.
The scoring categories are used to set the ranges for low, medium, high and very high for both complexity and risk.
This shouldn't normally need to be altered from the default settings.
The settings in the table above would mean an application's transformation with a Risk score of 35 and a Complexity score of 28 would be Risk = Medium, Complexity = Low.
The weighting section is used to apply a multiplier to the base values set in the first section, based on the category the application falls into.
The Complexity weighting will be applied to all efforts in the base value table (except for testing)
The Risk weighting will be applied to the effort assigned to testing in the base value table.
The Complexity weighting will also be applied to the duration, although this can be toggled on or off in the base value section.
Costs and Contingency
This section allows you to set your day rate that will be used to calculate the transformation costs for each application.
The blended day rate should be entered, this should be an average cost across all resource types.
A percentage can be applied for project management, which will increase the transformation cost of every application by the percentage entered here.
A contingency amount can also be set here and the cost of each application's transformation will be increased by the percentage entered here.
Future Run Costs
The future run costs section is used to set the parameters the system uses when calculating the ROI of an application being moved to the cloud.
The future run cost feature works by taking the matched machine type and cost from the underlying servers, (usually obtained by the server discovery tool and imported with the server data). The sum of all the future run costs for all the servers within an application is the future run cost for the application if Rehosted.
The other values are target values and calculated using the future costs for a Rehost.
E.g. If an application has a future run cost of £1000 per month (Rehost), setting 65% as the refactor future run cost would give the application £650 as a future run cost if refactored.