USAGE TRACKING is a great feature within OBI EE, but it lacks enough detailed information to be as effective as it could be. It’s great for analyzing which reports are accessed the most and when, which are the long running reports, and how often your reports hit the cache. But once you have that information, then what? Do you know what might be the cause of that long running report? Do you know what reports aren’t being accessed at all? If you perform impact analysis to get a list of reports impacted by a change, can you tell how often those reports are run? With BICG IMPACT™ you can answer those questions, because we integrate additional catalog and repository information into the out-of-the-box Usage Tracking subject area. This allows you to see what physical tables are queried by a report, or what complex logical expressions might be the cause of a slow report. Now you know all about your Oracle BI.