... 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 point 1.
4. Customise the presentation for target devices and user roles
There is great appeal to the idea of making critical business information available to decision makers anywhere in the world, using current data and not depending on any additional infrastructure other than a mobile phone or PDA. Yet, as previously noted, clarity and accessibility become even more important for mobile device access. Full-scale BI reports are too ungainly to be delivered to the small screens of handheld devices, and mobile phones don't come with sophisticated input devices. Therefore, BI reports for wireless devices should be limited to a set of key performance indicators or a dashboard. In addition, navigation must be cut down to what is absolutely necessary.
5. Target reports to users
If access to reports is integrated into a transactional application, parameters can be passed to the report server that reflect the user's role selection, current navigational context, and other values that a report can use to create a targeted and customised view of the data. For instance, if the application maintains some sort of organisational tree and users can navigate from the corporate level to regional and branch office levels, the reports can show data for the currently selected node in the organisation. The user does not have to navigate down to the node again in a separate report application.
6. Use a combined push/pull model
In order to maximise the use of a BI solution, it can be helpful to push information to the users instead of depending on their ability to pull the information when needed. If your presentation layer is already integrated with a transactional application that the users rely on on a daily basis, this information push can be done on Web pages with ticklers, 'adverts' and links to reports. Alternatively, report updates can be pushed via email.
7. Keep information timely
The closer to real-time your enterprise BI data is, the more costly the implementation, especially in large scale enterprises. Keep in mind that information is only useful if it pertains to decisions that need to be made. Therefore, firms should be judicious about hat their information requirements truly are and plan accordingly.
8. Enterprise Application Integration (EAI)
Though we recommend delivering key performance indicators (KPIs) within the proper context and application (i.e., not forcing the user to a separate application), calculating and delivering KPIs often requires information integrated from other applications.
This form of EAI can be accomplished in many ways, from the database level on up to Web services, or with simple feeds from the system of record. Be aware of the EAI requirements, especially when you consider outsourcing any portion of your critical operation data. Oft overlooked in these budgets, you will need two-way communication with the outsourced data.
While the Web is a very effective distribution channel for business intelligence, Web features should only be used with a specific goal in mind or they will subtract value from a solution. Even a disciplined approach will only be successful if the potential pitfalls identified above are being managed properly. BI is most effective through the merger of EAI initiatives with relevant positioning of business intelligence. The power of EAI and BI together allows a concise focus on creating business value: disseminating easily understood information to each employee's unique information requirements, without requiring slicing and dicing on their own — and in near real-time (NRT) fashion.
Christian Donner has 20 years of experience converting data to useful information. He is a senior technical architect at Molecular, a web consulting firm located in the Boston area. He can be reached at pubs2005(AT)donners.com. Tim Michaud has16 years experience in project delivery and consulting. His experience includes EAI, BI, CRM, supporting business strategy through the development, and implementation and maintenance of mission critical systems. He is a technical program manager at Molecular. He can be reached at tim.michaud(AT)gmail.com.
