Its imperative that every system needs a vision of its own working, providing a fast decision making process. But practically none software or hardware is constructed wondering about monitoring in the future. And due to the monitoring difficulties and high cost to development and maintenance, the monitoring is ignored.

After system release, software or hardware, often happens a halt in the maintenance and creating new views of its working or the creation of failure alerts or non-programmed stops. During system critical problems, its common that the companies does not have own tools that allow to determine in a practical and consistent manner the current status of the problem.

In this crisis situations, visions like the screen bellow are common, where the user or operator are limited to system native tools, delaying the problem analysis and even mistaking perceptions due to human error.

Examples of problems hardly recognizable in real time and that brings financial and/or image loss to the companies are:

Communication links down;
Application servers fail, database or telecommunication equipment;
System performance loss;
Lack of working visibility of external system or companies, third part and/or customers.

Another important subject that is neglected during development of a system is the business view in real time. This vision is provided sometimes in a form of reports, in great majority, generated after days and delaying the analysis and identification of mistakes of billing or others essential indicators.

Beyond, for each changing in business rules the vision needs to be adapted. These adaptations are several times ignored because of the cost, causing distortions in business understanding.