Building Making It Happen
Building Making It Happen
  Sign-in         Register
    
Principles and Rules Listing Page
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts
Most of the large organizations have multiple contracts and licensing regimes for same platforms. For example, you may find multiple licenses for business objects in different markets for the same company.
 
This page of 'Principles and Rules' is linked to:  Data Warehousing, Data Analysis/OLAP, BI platform Tools Evaluation, BI business intelligence end-to-end view, Business Intelligence and performance management V,


This results in:

  • Missing out on volume, economy of scale and negotiation power of global contracts and volumes.
  • Same user existing on two different instances of the same software, and an organization ends-up paying twice for the same user.
  • Sheer administration and management of the contracts.
  • Technical skills deployment by the customer. One needs to have skilled IT resources within customer organization to handle this issue.

Consolidating licensing can range from being a quick-hit to an arduous journey. Here are some of the issues you can have in the consolidating the licensing contracts:

  • You may have long-term binding contracts, with defined jurisdictions.
  • The company with who you licensed the platform may have been recently bought-over by another company (this is quite possible in BI space, where at any point of time, half of the companies are buying the other half).
  • Very lucrative contracts from the vendor point of view, and vendor does not want to change it.

Here are the various methods in which you can do the licensing consolidation:

Having a common maintenance and services contract

There are typically two components- one is the licensing fee and other is annual maintenance, which includes support services. The support services, sometimes may not be bought from the vendor but from a third party service provider. For example you may pay license fee for your DBMS to oracle, but maintenance and services could be bought from Tata Consultancy Services (a global IT company based out of India).

Consolidating licensing regime- Usage based vs enterprise level license

An organization is able to work around with the vendors, to decide on if they want to go for enterprise level license (with certain bucket of licenses given), or usage based license (per user or/and per concurrent user).

Consolidating licensing regime for economies of scale:

With consolidation of license, one is able to move into the higher usage slabs, generally leading to less cost per unit of license.

Getting a more dedicated service from the vendor:

Consolidation of the contracts and associated volumes, will lead to reduced cost from the vendor point of view. Also to retain a larger customer, vendor may throw-in dedicated help-desk, X hours of free support from their centre of excellence for the platform.

One more scenario

The above is limited to consolidating the contracts and licenses for the same software. However, there are some other opportunities as well. One can consolidate the maintenance agreements for legacy and small platforms to a single vendor. Some organizations have a long tail of legacy BI systems. These systems are typically shrink-wrapped and are waiting for their replacement with next generation BI initiative. By consolidating their maintenance and contract to a 3rd party supplier, will help the company cut-costs and also enable a better transition during a new BI initiative.

   Access more details on this page   

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 → 
 
Back
Featured Pages
Data Quality Analysis considerations
Data Interface Exchange Controls
Data Warehouse Information Systems Assessment
Additivity of Measures-Facts

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
Customer Data Augmentation and Enrichment
Null foreign Keys in fact tables
Data Warehouse job control and audit
Data Warehouse Dimensional Model Components