These strategies will help companies ensure they are distributing the kind of high-quality, actionable BI necessary to make real-time business decisions.
Businesses have mastered using the Web as a communication tool, and with good reason. The Internet has proven to speed connectivity between disparate organisations and enable a mobile workforce. Yet leading organisations are realising that using the Web channel to communicate business intelligence (BI) in near real-time fashion supersedes its previous use as an information dissemination and collaboration tool.
Not so long ago, paper reporting was distributed on a monthly, or less-frequent, basis. As business users became more and more technology-savvy, reporting became more "downloadable" on demand. A step in the right direction in terms of flexibility, yet this had each user slicing and dicing data as he saw fit to find hidden treasure in the information. Most individual employees have neither a full view of corporate objectives, nor the expert knowledge or the time to dig for critical information in raw or even summary data.
When it comes to delivering BI, the goals should be accessibility and clarity -- not flexibility. End users should not have to wonder how to find the information that they are looking for, and what the information they are looking at means. This focus is further heightened when new and less sophisticated delivery platforms are considered; for example, mobile devices are not equipped to handle large amounts of data manipulation, but are perfect to receive frequent updates of succinct business intelligence.
To succeed in today's competitive, fast-paced business environment, it is imperative that the right content is aggregated and delivered to the right people at the critical moment when a decision must be executed. The following eight strategies will help companies ensure they are distributing the kind of high-quality, actionable BI necessary to make real-time business decisions.
1. Pick the best delivery vehicle for your audience and your data
Core metrics that users need to develop a quick and clear understanding of the organisation's state of health should not exceed five to eight numbers. Typically, such information is not intended to be printed and taken to a meeting, and is therefore well suited for placement on a dashboard, mobile device or in a pagelet on a portal page.
Detailed reports, on the other hand, are better looked at on paper and should be provided in document format, such as PDF or Excel. Rendered documents provide much more control over the appearance of a printed report versus HTML Web pages.
2. Integrate the presentation layer
A BI solution is often built as an add-on component to the transactional system that generates much of the data. Users who work with the transactional system want access to reports from where they need it -- from within the application -- and are much less likely to navigate to a different web site that would invariably come with a different user experience. Since the value of the reports depends directly upon a user's ability to locate, analyse and use the information skillfully and appropriately, we recommend that the reports become part of the application's user interface. Furthermore, providing direct links to important reports from key locations on the interface will give you tighter control over where the reports appear and to whom.
3. Integrate the security layer
In order to effectively integrate the presentation layers of your report delivery application and your transactional application, it is necessary to integrate security layers as well. One way to accomplish this is a true integration with shared user accounts. However, this approach can be complicated if either side uses proprietary security. A simulated integration where the application authenticates with the reporting server through a service account is comparably simple and straight-forward to implement. In this scenario, the application proxies all requests to the report server and streams the results back to the client. This has the added benefit that a user does not need to access the report server directly so that it can be hidden behind a firewall. A reference implementation of a Java proxy for SQL Server Reporting Services is described in [1].
1%
2%
