Application Dashboard is a tool for guiding a Project team through a methodology to understand a company’s Notes application landscape, usage and rationalization potential. It also serves as a workflow tool for migrating application content, and providing insight into platform migration project progress. Application Dashboard also captures information about Notes application usage, size, complexity, code length, risk, code dependencies, user access, ACL access, replication, etc. By default it will also synchronize the NAB with the Active Directory…

- Reduce interaction with the business. Use ‘smart’ surveys that run per application to quantify the business relevance and usage in the near future. The dialogue with the business should have a beginning and a traceable ending.
Detect similar templates corporate wide that consolidate your business logic redevelopment program.
Eliminate redevelopment of disused code.
Have continues insight in your Application Landscape, it's usage, it’s complexity, it’s real size.
Deliver reports on; Project progress, definition of complexities, Business Intelligence, Application Migration risk, Application Rationalization potential

Easy, unobtrusive deployment.
Unprecedented insight into the a Notes application landscape.
Rationalization or platform migration now fully manageable and tool-driven.
Standardized business communication, technical data and BI capture in a single tool.
Application level traceability.
Reduce overlapping redevelopment efforts and limit project scope by identifying common or similar application templates - Access a ‘radar’ where all Application usage and complexity is dynamically monitored.
Access a common repository of rules where all stakeholders can agree on the definitions of complexity.
Create and send application related business survey questionnaires; feedback can be used to segment the Applications and reduce scope.

Application Dashboard captures information about activity, users, scale, documents, fields, code complexity (e.g. number of lines, code dependencies), replication and much more.
The main goal is to reduce the scale of the application landscape. It uses the following a ‘smart’ methodology:

1. Technical Analysis : Reduce project scope by identifying inactive, empty or highly complex databases and other out of scope criteria such as vendor and system databases

2. Business Analysis : Based on the results of step 1, apply business analysis. Use targeted surveys to the business to better understand the real need of the applications. Goal: to reduce scope even further using Business Intelligence (BI).

3. Functional Analysis : Reduce redevelopment scope by identifying both unique and structurally similar templates. Identify code functionalities that can be decommissioned...

Not a one shot report
Profound data available from usage to complexity
Capacity to communicate with the end users (The Business) through surveys
Technical Data and Business Intelligence data stored in one tool
Independent of log file analysis
Ability to define the definitions of complexity and database usage
Accurately calculate project costs and detect economic risk upfront
Content and Business logic use separate analysis methods
High-level services and consulting available.