I know, this is old news but we need to have this as part of the process. Once we have analyzed the applications, we are finally able to define variables for the project in terms of time, cost and effort. This is of course very important because everyone would like to know exactly how much migration will cost and how long it will take. On the other hand, it helps to decide the resources needed for completing the project. This is something that is often overlooked, but in fact, AppDNA effort calculator is one of the most powerful tools you could imagine for winning the trust of customer and also for closing the deal. This is the point where is big room for improvement, it is not used as often as it should.

Actually, I would personally include few other steps in the process before this calculator, but because licensing sets limitations for reporting, it needs to be here. For example it would make sense to be able to include organizational data in this stage, but because it is licensed information it is always not possible. Of course, after licensing you can come back to this report if needed. Well, it also means that up to this point you are able to plan the migration without investing on the licenses. Clearly, this tool also shows the reasons why the licenses should be purchased.

What is also important, is the fact that there is virtually zero guess work hidden in the tool, everything is based on real variables provided by the customer and the accurate exact data analyzed from the applications.

All the data we can use starting from this moment is the key for ultimate efficiency, accuracy and later it also enables ways to calculate exactly how, where and how much organizations could make cost reductions just by managing their applications in a good organized way. Just to make it clear, reports provided by this tool is just the starting point and shows how much and how long it will take to complete the project. Later on, you are able to use the variables for cost reductions.

I don´t want to be too detailed on how the tool works as the other part of cost reductions resides elsewhere in the system and the big picture behind all of this is actually quite complicated. Hidden part of the calculations are in the applications, related issues and actions.

Anyway, the basic variables used for input are related to workforce:

–          Time available per day and days per month

–          Time needed to remediate different level of issues on different complexity levels of applications

–          Number of applications (If imported only a sample of full portfolio, you can scale up)

–          Number of testers and remediators

–          Cost of testers and remediators

For inputting the variables, it is ideal if customer can work with the Engineer during the PoC and play with the numbers them self.

The reports we then provide includes simple pie charts for showing where the customer is at the moment with their applications if deploying to the target platform without doing anything. The other pie chart shows how the situation will be after remediating the applications by using the reports provided by AppDNA. Most important for the customer and decision makers is of course the timeframe needed for completing the migration and the savings automation can provide in comparison to manual migration.

Then there is also a summary of how much time would be used for testing and remediation actions during the migration, of course split in categories by application complexity.

Should we expect customer to make purchase decision based on this calculator only? Of course not. That´s why effort calculator report can be exported to word document, which is 20 pages of charts, tables, analysis results, algorithms behind the analysis and so on. But it is very nice report because it is not too technical. It of course has the technical elements, but the format is something for decision makers. It starts with executive summary and is something every decision maker would like to see.

Many times we get the question if the document can be customized? Word document! I understand the point… Service providers would like to customize the template to include their logos, terms of business and so on. There is no customization directly from AppDNA interface, but please go ahead and add your own things to the document by any way you may find. If I were a service provider using AppDNA as a tool for customer onboarding, building a business case and closing the deal, I would add the “sign here to order” 🙂

I have attached a sample report for the ones who are interested. AppDNA_EffortCalculatorReport_Sample

In this point of the process we could immediately move to automated workflows, but because we want to do it right, there is one step before moving to the things where big wins are.