Operational business intelligence shares many characteristics with traditional BI, but it also differs in many ways, the most dramatic of which is the timeliness of the data acquisition and integration process. Traditional BI can often rely on overnight or intraday batch processing for collecting and processing the data. To meet operational BI needs, the update cycles repeatedly require more frequent processing of the data and do not allow for a batch processing cycle. This has several implications with respect to ensuring data quality, two of which are governance/data stewardship and source data quality.

Best practices for a BI project dictate effective governance structures as well as a robust data stewardship program. While this may the best practice, many companies have BI programs that deliver value yet do not have adequate governance or stewardship. (I don't condone that approach.) To understand how this can happen, we need to examine the impact of governance and stewardship on both the project and the result. The first of these two impacts applies equally to both traditional and operational BI initiatives. The second is more problematic for operational BI projects.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access