How AppTitude™ works

AppTitude works in four simple steps:

1. Import

All your applications in any format, physical or virtual (if non-MSI, AppTitude even generates the package automatically). The import phase is where we collect and generate the DNA for each application. Here we interrogate not only the installer but also all of the binary and text file that comprise the application and, crucially, we get all this from the application directly so we are as accurate for internally developed applications as ISV supplied applications.

In addition to applications we can also import the customised OS image. We treat it like an application so we know about all of the files and configurations made to tune the OS for the organisation and it plays a key role when we analyse for issues and dependencies.

2. Analyze

Our analysis is unrivalled. We make use of heuristic algorithms (similar in concept to anti-virus algorithms) which look for defects and issues not only internally to the application, the installer and the binaries but also in terms of how the application and its function relates to the rest of the portfolio and the operating system.

Additionally we draw on external data to supplement our knowledge derived from direct analysis to provide the most complete view across all of the desired reporting. Because we separate the analysis from the DNA collection we can create new algorithms and report on future changes without the need to re-import the applications – the info is already in the DNA, we just extend the algorithms – no more worries over the impact of that upcoming service pack.

3. Report

Generate quick traffic-light toplines to show exactly which applications will migrate easily, which will need help and which will present problems and why – plus deep drill-downs with intelligent remediation advice.

Relevant information is at the heart of what we do and our reporting is designed to release the right level of detail to the right individual the right time.

4. Remediate

Intelligent Remediation™ shows your team exactly how to fix most problems – or choose auto-remediation where it makes sense (it’s much more intelligent than blanket auto-fixes that can cause more problems than they solve).

Making the right choice on what to fix and how to do it is important. Really important. Especially when you have hundreds or thousands of applications. So, the first thing is accurate reporting. Issues are then configured with fixes – the best fix may not always be to change the app, its often better to tweak the OS – the chosen fixes are reflected in the reporting so downstream users don’t just get ‘red applications’ but are supplied with the defects and how to resolve them. Transparent, configurable, robust solutions for the application and the portfolio – that’s what we call Intelligent Remediation.