Business Intelligence & Analytics Applications
Governance Challenges


Many large organisations have multiple MI/reporting applications that have been implemented using a variety of Business Intelligence (BI) software products. Often this results over time in a BI landscape that's complicated and opaque, difficult to maintain and prone to inconsistencies in metrics definitions and output that doesn't reconcile.

This erosion in the quality and consistency within BI environments of mature organisations causes issues that impair performance compared to competitors with less complicated architectures.

Recognise any of these issues?...

Metrics do not reconcile when viewing dashboards, reports or analyses sourced from the same or different systems

Resulting in:

  • Reduced trust placed on MI by decision-makers

  • Erosion of capacity to make evidence-based business decisions in a timely manner (to identify and act on issues and opportunities) 

  • Increased effort and cost to investigate root cause of inconsistency by MI support teams

  • Higher risk of internal and external misreporting with associated economic and reputational consequences


Reduced control and governance over BI applications

Resulting in:

  • More inventory than is needed.  Slight variations in MI/reports are requested and implemented over time.  More to go wrong and to support & maintain.

  • Complicated environments that result in “sub optimal” end user experience.  Desired MI is harder to find and use.

  • Timely communication with user community is harder to achieve.  For example, notifying users of delays or quality issues in upstream data feeds that will impact dashboards and reports to which they have access.

  • A disconnect between upstream systems subject to corporate Data Governance and the MI and BI available via “self service” applications.


Inconsistent and incomplete documentation

Resulting in:

  • Consumers of MI do not know how the MI has been sourced and transformed

  • Confusion as to who are the owners of dashboards, reports and metrics

  • Increased effort to support and maintain

  • Greater resistance to change – “we might break it...”

  • Harder to rationalise MI systems. Stuck on legacy software with associated costs. 

  • More effort & time needed to migrate to cloud-based solutions

  • Challenges in providing evidence to regulatory bodies re: policy compliance (e.g. BCBS 239 – Risk Data Aggregation and Reporting)

Common Questions from within a BI Community

Each of the distinct roles within BI communities have a need for contextual information relating to BI objects.  For example, end users need to know the purpose of a dashboard or report and who the subject matter expert or business owner is; analysts need to know the definition of a KPI or metric or dashboards that will be impacted by change; and administrators need to understand the extent of duplication / redundancy across BI applications and report usage patterns.



...these are just some of the questions our solution is designed to support.