

You can implement data validations and automatic error correction based on common business rules. It will also help reduce the noise of bad data and assist with consolidation of redundant reports.

Additional supplementary information could be extracted from the hierarchy of data responsibilities, processes or workflows, metrics or policies pertaining to a particular report, report certification details, and other linked sources.Īdditionally, registering a BI system in Collibra offers the advantage of global lineage that captures data flows into the reports and numerous characteristics pertaining to these flows, such as data usage. It could also be important stakeholder information, supplementary attributes or additional tags or linkage to common governance asset types (such as the “line of business”). Examples of such context may include important relationships with other data assets in the platform, such as linking with the company business terms from business glossary. Additionally, human collaboration or machine learning can enrich the context around these registered report artifacts, and then broadcast this context back to the Tableau server to provide global trusted insights for business analysts. And this approach leads to a better understanding of enterprise data analytics by data consumers.

Registration of reporting server content with the data catalog that sits on a data governance platform like Collibra ensures that this key area of enterprise data analytics is open for cross-functional collaboration, processing, and enablement. We nicknamed this use case the “Catalog of Reports.” It opens up immense opportunities for business users to create a trusted report ecosystem that is easy to maintain and consistent across multiple BI deployments, while keeping the the underlying data safe and secure. Let us count the ways of how the reporting data layer can benefit from its automated registration with an enterprise-wide systemic catalog! We can explore the many benefits of modern data catalog functionalities for BI by examining the Collibra-Tableau data registration scenario unveiled in our latest release of Collibra Data Governance Center. Today, I’d like to expand this concept of achieving enterprise-wide trust in data to focus on the importance of cataloging and governing the BI reporting layer itself in the context of global data landscape. Such a catalog t reats information assets as a treasured resource and offers a preventive remedy to the common pitfalls of self-service deployments.Īs noted in my previous blog post, a catalog built on a data governance platform enables trust, accessibility, and better understanding of the data sources and sets that feed into BI reporting and analytics. Hence, there is a need for a data catalog that enables enterprise-wide tracking, processing, and intelligent management in each of these data layers of the enterprise data architecture, and with the potential to enable data citizens at large to maximize the value of data. And sometimes, they could propagate down to the raw data layer in the original data source or data store. These questions may require resolution in either provisioning or consumption data layers within the organizational data architecture. Questions of trust can arise with regards to various segments of the data flow or landscape related to business reports and underlying data sources. Despite the efforts by leading self-service BI vendors to re-calibrate and introduce local governance features, the issues that precipitate these challenges are often rooted in the data realms with scope beyond the self-service reporting system, such as Tableau server. However, the companies poised to reap the benefits of modern BI rollouts identified a set of common “ evolving challenges” around sustainability, governance, and risk management that interfere with their ability to make a lasting impact. The widespread adoption of enterprise self-service BI systems created new opportunities to further digitize and democratize business decision making, thus making it more effective.
