Solving The Application Catalog, Normalization, Compatibility and Lifecycle Problem
Dashworks Analysis+ wraps a layer of application normalization, compatibility management and software/hardware catalog functionality around the existing Dashworks Analysis System:
Dashworks Analysis+ leverages powerful data connectors, such as Microsoft SCCM, LANDesk, and Altiris to pull thousands, if not millions, of data points during your migration or IT transformation project. It then automatically processes this data to catagorize, normalize and rationalize your IT information based on the data stored in the extensive software and hardware catalog. This allows you to understand not only what you have, but also what state your software/hardware estate is in for whatever activity you need to perform.
Never before have organizations had the ability to understand their hardware and application estate lifecycle, and act upon it right away. Continuous software management (IT Transformation in Business as Usual Mode) is a huge goal for IT teams, and the ability to manage and control it proactively will help control application security risk, license bloat and prevent overspending — putting you in the driver's seat rather than chasing after the problem.
Fast Understanding Of Your Application Estate
Your raw application inventory is examined against the software catalog and automatically categorized as 'Mapped', 'Irrelevant' or 'Unknown.' Hardware manufacturers and models are also checked against the hardware catalog and categorized as 'Mapped' or 'Unknown.' Gap fill committments ensure nothing gets missed and in-house applications can be categorized manually to achieve 100% coverage. Typically, this process alone will shrink the applications list by 70% - 80% for major transformations like Windows 10.
Normalize All Data Points To Cut Down Master List Significantly
After categorization, rather than trawling a huge list of raw application data, the normalization process reduces this output of applications and hardware manufacturers to only relevant and consolidated minor versions. On average, a reduction of 3:1 is achieved for the hardware data. For applications, it is a lot higher, often reaching over 20:1. An example would be normalizing Adobe Reader 11.0.1 and 11.0.2 to Version 11.0. On the hardware side, for example, HP, Hewlett-Packard and HP Inc. are all mapped to Hewlett-Packard.
Instantly Know The Compatibility Status Of Your Application Estate
Mapped vendor applications are then checked for compatibility with Windows 10 or other target platforms. Categorizations are either 'Compatible', 'Incompatible but upgrade path exists', 'Incompatible' and 'Unknown.' Application data is added to show the first compatible version if an upgrade path exists, and whether that is a free or paid version. Applications then have additional lifecycle information added, including 'In Support' or 'Out Of Support,' 'End of Life Date' and 'Licensable to provide further reporting value.'