Sales Management Customer Relationship Human Resources Business Performance BI & Data Quality IT Tools & Vendors

Sign-in   Register
Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline
Principles and Rules Listing Page

Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards

Governance & Standards essentially points to the consistency and robustness of managing change in the BI environment. The key issue behind high cost of BI is varied IT platform, standards and processed, which have additional over-head and also make BI inefficient & defective. As an organization we can undergo different types of changes, which have to dealt by effectve governance and standards.
 
This page of 'Principles and Rules' is linked to:  BI business intelligence end-to-end view, Data Analysis/OLAP, BI platform Tools Evaluation, Data Warehousing, Data Quality,

Different Classifications of changes in a BI environment

Different Level of BI Changes:

As new BI requirements emerge in an organization across functions and locations, it may lead to:

  • New BI platforms in terms of software tools.
  • New Data-Marts in the same platforms.
  • Changed dimensional models (dimensions, attributes and facts) in the same data-marts.
  • New Reports and analytics on the same data-mart structure.
  • New BI ETL scripts due to changes in the Dimensional Model (the way data is modeled in Data-Warehouse- it can also be relational model) in Data Warehouse and OLAP .
  • Changes in the formulae and business rules.
  • Etc.

Universe and context of BI changes:

  • BI platform structuring and re-structuring: This is more fundamental change, where BI platform foundation is being set. In this context, one is guided (and not driven) by the business requirements, as one establishes the holistic dimensional models. For example, if you are creating a data-mart on sales revenue analysis, you will include all or most aspects of sales revenue management, instead of limiting it to business requirements (which might be driven by some immediate burning issue).
  • BI platform guided by multi-functional- enterprise level changes : These kind of changes include business requirements management and delivery across multiple functions.
  • Functional level change in BI requirements.
  • A process level change (within the function or across the functions)

The above bullets are essentially to sensitize the readers on the variety of changes, which are possible. The question is on how to manage the change within the given change environment, which is quite varied.

Governance Methods- Less than Ideal but a good starting point.

  • Document the standards and circulate. Establish a central monitoring process post-facto.
  • Document the standards and circulate. Establish a central monitoring process pre-facto. This means that before implementing the designs, one has to take sign-off from the central monitoring group. This is a better solution, but its important for the central monitoring group to have needed sponsorship and teeth..

Governance methods- Highly Recommended

  • Make IT responsible for any BI platform acquisition, and for contractual agreements with the software vendor.
  • Post acquisition, make IT responsible for supporting the IT platform.
  • Create a BI council, which works together to develop the standards and governance methods. This BI council will have representations from different functions and therefore, will have a greater buy-in.
  • The most ideal method is to have the BI platform and design management done by a single and central group, which has end-to-end functional and skills representation. (please refer to Business Intelligence Competency Centre in 'latest trends')

The Business Intelligence standards

BI Data-Modeling standards:

  • The Foundation Dimensions: The common set of dimensions to be used by any dimensional model in any data-mart.
  • The way to store the BI data-model: De-normalized way (like dimensional model) or normalized way (Relational Model)
  • The naming and labeling conventions of different data-elements.
  • Data-Element definition- Formulae related to different terms and associated business rules

NOTE- Above falls in the gamut of the subject of Meta-Data repository. A meta-data repository is a comprehensive documentation of organizational universe. The above mentioned elements are important part from BI perspective.

BI Process Standards:

  • BI strategy formulation and change management process
  • BI Business requirements management process.
  • Once BI Business Requirements are defined, end-to-end Change management process.
  • BI security administration process.

BI Software tool acquisition and maintenance standards:

  • Set of tools to be used for BI. (Data Quality, Data integration, Data-Warehouse Database, OLAP Server, Enterprise reporting tools)
  • Software tool acquisition process.
  • Licensing regime.
  • Maintenance and Service contracts terms and conditions.
  • A list of software development vendors, who can work for the organization. For example, An organization would not like to have 20 different vendors working on their BI platforms.

The benefits of the robust governance and standardization. It's commonsensical:

  • Reduced costs for acquisition, change management and maintenance.
  • Agility and flexibility
  • Speed to market

Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Data Warehouse application is not limited to Analytics → Principles & Rules → Store as much detailed and granular data in data warehouse as possible → Principles & Rules → Data Normalization is not the best approach in Dimensional modeling → Principles & Rules → Keep the same names and definitions for all data elements → Principles & Rules → You cannot have a super-flexible Data warehouse → Principles & Rules → Dimensional models can be extensible and scalable → Principles & Rules → Data Marts should be ideally based upon a business process and not on a department. → Principles & Rules → Business Intelligence competency groups should be well-linked with business → Practice Techniques → Aggregation Queries on slowly changing Dimensions → Practice Techniques → Documenting your data-integration system → Principles & Rules → For a Data Warehouse/Data-Mart solution, analyze well, but be decisive → Principles & Rules → Maintain a trail of the key dimensional elements from source system to loaded → Principles & Rules → Conformed dimensions are must for cross-drilling → Practice Techniques → Checksum Approach for identifying the changed records from source systems → Principles & Rules → Data Quality is a subject of business ownership and not of IT-ownership → Principles & Rules → Don't create a hype on Data Quality Program. → Principles & Rules → Sponsor for a Data Quality Program → Practice Techniques → Business Case for Data Quality → Principles & Rules → Data Quality is not Perfect Quality → Principles & Rules → Engage the Vendors in Data Quality Program → Practice Techniques → How to get more data along with Sales leads → Practice Techniques → Ask for dates instead of number of years → Principles & Rules → How to Maximize the effectiveness of Data Stewardship → Practice Techniques → Field Tips Series#1- Data Mapping and Assessment → Principles & Rules → Data Management Standards for Data Entities will be a mix of collaboration and top-down → Principles & Rules → Data Management standards for data entities are not only for IT systems → Principles & Rules → Cascade your standards and guidelines to business partners and Vendors → Principles & Rules → Data quality assurance and control guidelines are no-brainer. Publish one immediately and evolve thereafter. → 
 
Back
 
Relevant links to this page
Data Warehouse application is not limited to Analytics
Store as much detailed and granular data in data warehouse as possible
Data Normalization is not the best approach in Dimensional modeling
Keep the same names and definitions for all data elements
You cannot have a super-flexible Data warehouse
Dimensional models can be extensible and scalable
Data Marts should be ideally based upon a business process and not on a department.
Business Intelligence competency groups should be well-linked with business
Aggregation Queries on slowly changing Dimensions
Documenting your data-integration system
For a Data Warehouse/Data-Mart solution, analyze well, but be decisive
Maintain a trail of the key dimensional elements from source system to loaded
Conformed dimensions are must for cross-drilling
Checksum Approach for identifying the changed records from source systems
Data Quality is a subject of business ownership and not of IT-ownership
Don't create a hype on Data Quality Program.
Sponsor for a Data Quality Program
Business Case for Data Quality
Data Quality is not Perfect Quality
Engage the Vendors in Data Quality Program
How to get more data along with Sales leads
Ask for dates instead of number of years
How to Maximize the effectiveness of Data Stewardship
Field Tips Series#1- Data Mapping and Assessment
Data Management Standards for Data Entities will be a mix of collaboration and top-down
Data Management standards for data entities are not only for IT systems
Cascade your standards and guidelines to business partners and Vendors
Data quality assurance and control guidelines are no-brainer. Publish one immediately and evolve thereafter.
Additional Channels
Principles & Rules
Free Templates
Glossary
Key Performance Indicators

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales Leads Generation through advertising
Sales velocity (or speed of sales)
Sales Revenue SWOT
Sales Channel Management System
Sales Campaign Management
Read more...
  Customer Relationship Management
What is Customer Segmentation?
Customer Value and Profitability- BI
Customer Segmentation Parameters
Exit barriers for Customer Retention
Customer Segmentation Data Management
Read more...
  Human Resources & Leadership
Act with Decisiveness
Be straight and blunt, till you team gets used to it
Deliver Results
Customer Focus
Leadership Development- Setting the Context
Read more...
 
 
Business Performance & Planning
SWOT Analysis in Strategic blueprint Planning
Internal Info Assessment Report
Creating Strategy Blueprint
Strategy Blueprint Information Gathering
3-4 hours in reviewing a scorecard.
Read more...
  Business Intelligence & Data Quality
Handling Sparse Dimensional tables
Non-Additive Measures-Facts
Manage Leads Database Centrally
Field Tips Data Mapping & Assessment
MDM- Account and Product Management
Read more...
  IT Vendors & Tools Management
OLAP Architecture Cache Management
Multi Cube OLAP Architecture
Metadata Repository sharing
Vendor Credentials and Track-Record Evaluation
Data Profiling and Monitoring
Read more...