BI systems have gained increasing importance in recent years. Various reporting requirements have been developed without taking into consideration the aspects of sustainability and reusability. New developments are often added in an uncontrolled manner to existing solutions. Who vouches for data consistency? A subsequent consolidation requires much effort and is therefore expensive.
With the BI Director, existing BI architectures can be graphically processed. Reusable objects as well as redundant files can easily be detected. New developments can be planned as on the drawing board and their implementation can be monitored. With the BI Director the documentation of architectures is permanently implemented in connection with the system throughout all the project phases. Documentation and the system state do not break up.
In order to manage growth, new concepts of integration such as layer-models (LSA) or central objects are being discussed in BI strategy workshops. How can these new concepts be developed and applied on BI systems if the status quo is out of view? New guidelines are permanently being created without being able to monitor their observance sufficiently.
The BI Director allows a complete insight into your BI system. Thus, you can get a quick overview of which measures have to be taken right away and whether these are really followed through in daily development and operation. Daily updated analyses reveal violations against integration concepts and development guidelines. Thus, you can influence the development process actively.
Only if business department, BI operation and BI development work together closely, can existing problems be revealed and resolved. In a close cooperation, new developments can be sensibly planned and created. BI systems suffer from the fact that the communication between the involved parties is often bad, and experience and know-how is not transferred. The documented communication takes place in different systems or just by e-mail. Only if field reports from business department and operation (such as incidents) are taken into account, can new developments and change requests be reasonably integrated. BI projects often suffer or even fail due to bad communication!
The opportunity to create a corresponding document for each distinct project phase offers the chance for all involved parties to understand the current state of the development process. At the same time, all the parties can take part in the creation and extension of centrally filed documentation. The documentation – and visualization possibilities of the BI Director serve as a link between business department, operation and development.
The development process of BI projects has been formalized in many compnies.BI projects usually consist of standardized project phases: requirement specification, project planning, implementation, test and handover to operation (going live). However, very rarely is a standardized project control applied. As a result, a mismatch of realized architectures vs. planned architectures is often recognized before transport to test or even worse before transport to production system. At this point in time changes are possible but extraordinarily expensive. Of course, the actual architecture can be monitored at any time in the development system. But who has the time to take an overview of developments in day-to-day business?
The extraction and loading time window at night is frequently interrupted because loading dependencies are very complex, existing delta-mechanisms are not being used or ABAP-routines are simply not effective. Only insiders can evaluate loading dependencies and reduce them, if need be. A system-wide overview of unused possibilities of delta loading is difficult to gain. Also a system-wide analysis of ABAP-routines and an evaluation of their running-time is seldom made; it costs time and therefore money.
Loading dependencies become transparent through visual presentation. Pre-defined performance analyses reveal unused delta-mechanisms and non-performing ABAP-coding. With the BI Director you can react actively within critical time windows there for you can prevent that time windows are interrupted.
In business departments you can regularly hear that queries run more and more slowly. Currently HANA and the Business Intelligence Accelerator (BIA) serve as a universal remedy. Both solutions captivate with their easy integration into the system landscape; both however have a price which cannot be ignored. It already helps to stick to design recommendations (dimensioning, aggregates, etc.) to avoid performance problems. In the operation, a comprehensive monitoring of these design recommendations is difficult. In order to analyze performance problems the technical contents have to be installed. Many clients work with the technical content but do not have the necessary resources to maintain it, to predict bottlenecks, and to react adequately.
The visualization of the technical content helps to reveal performance problems.