I know this is old news, but we need it in the process. Once we analyzed the applications, we are finally able to set 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. Secondly, it helps to determine the resources needed to complete the project. This is something that is often overlooked, but in fact AppDNA calculator effort is one of the most powerful tools you can imagine to win customer confidence and also to close the deal. This is the point where is great room for improvement, it is not used as often as it should.
In fact, I personally would include some other process steps before this calculator, but because the fixed license limits for reporting, it needs to be here. For example, it makes sense to be able to include organizational data at this point, but because it is authorized information, it is still impossible. Of course, after license, you can return to this report, if necessary. Well, this also means that up to this point, you are able to plan the migration without investing on licenses. Obviously, this tool also shows why the licenses should be purchased.
What is also important is the fact that there is virtually no conjecture hidden in the tool, all based on real variables provided by the customer and the precise exact data analyzed from the applications.
All data that we can use from this time is the key to maximum efficiency, precision, and later, it also allows for ways to calculate exactly how, where and how organizations could make cost reductions while managing their applications in good organized manner. Just to clarify, the reports provided by this tool is just the starting point and shows how and how long it will take to complete the project. Later, you are able to use the cost reduction variables.
I do not want to be too detailed about how the tool works like the other part of the cost reduction lies elsewhere in the system and the big picture behind it is actually quite complicated. a hidden part of the calculations are in applications, issues and related actions
Anyway, the basic variables used for entry are related to labor :.
- Time available per day and days per month
- Time to correct the level of questions on different levels of applications
of different complexity - Number of applications (If imported only a sample of whole portfolio, you can step up)
- Number of testers and remediators
- Cost of testers and remediators
for enter the variables, it is ideal if the customer can work with the engineer during the PoC and play with the numbers themselves.
reports we then provide includes simple pie charts to show where the customer is at the moment with their applications if the deployment of the target platform without doing anything . The other graph shows how the situation will be after rehabilitation applications using the reports provided by AppDNA. The most important for customers and decision-makers is of course the time required for completion of the migration and automation can provide savings compared to manual migration.
Then there is also a summary of how much time would be used for testing and remediation actions when migrating to the current split in categories by application complexity.
Must we wait customer to make purchase decision based on this calculator only? Of course not. Thats why the report of the calculator of the effort can be exported to word document, which is 20 pages of graphs, charts, analysis results, the algorithms behind the analysis and so on. But it is very nice report because it is not too technical. He of course the technical, but the format is something for policymakers. It begins with an executive summary and is something that every decision maker would like to see.
Many times we get the question whether the document can be customized? Word Document! I understand the point ... Service providers need to customize the model to include their logos, the business plan, and so on. There is no customization directly from the AppDNA interface, but please go ahead and add your own stuff to the document by any way you can find. If I had a service provider using AppDNA as a tool for customer onboarding, building a business case and conclude the case, I would add the "sign here to order" 
I enclose a sample report for those interested. AppDNA_EffortCalculatorReport_Sample
In this process, we could immediately switch to automated workflows, but because we want to do things, there is a step before moving on to things where great victories.
0 Komentar