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

Business intelligence need not wait for legacy conversion

Even if it takes more effort to deal with legacy system, one should proceed with the Business Intelligence initiatives, if it makes business case.
 
This page of 'Principles and Rules' is linked to:  Customer Relationship, Sales & Distribution, Focus & Money-Machine, Data Analysis/OLAP, BI platform Tools Evaluation,

Every organization has a road-map of modernizing legacy systems to new next generation platform to achieve multiple objectives of cost, efficiency and business value. Many a times, these legacy systems, carrying critical data are by-passed for Business Intelligence priorities, as they need more effort for ETL and it is felt that once they are migrated (say to SAP kind of systems having their own business warehouse), many of the Business Intelligence requirements will be met by leveraging the existing Business Intelligence framework (For example Business objects sitting on top of SAP Database or business warehouse).

This is a logical argument for an organization, which is in the initial stages of Data and Information management deployments. However, this should not be taken as a hard and fast rule, if:

  • You have already got some expertise and experience in deployment.
  • The legacy system supports a critical information requirement theme.

By involving the Legacy system as a source, will also help you to migrate the data to next generation system (say ORACLE ERP), as and when the legacy system is moved to the new platform.


Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Beware of Data Federation as an ultimate solution to your data integration solution → Principles & Rules → Periodic Rationalization & Prioritization of Information has multiple benefits → Practice Techniques → Which Metadata Architecture to use and when → Principles & Rules → Enabling Metadata Generation for Unstructured Content → 
 
Back
 
Relevant links to this page
Beware of Data Federation as an ultimate solution to your data integration solution
Periodic Rationalization & Prioritization of Information has multiple benefits
Which Metadata Architecture to use and when
Enabling Metadata Generation for Unstructured Content
Additional Channels
Principles & Rules
Free Templates
Glossary
Key Performance Indicators

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales Objectives Clarity
Sales facility Infrastructure
Sales product Mix Profitability
Sales Compensation components
Sales Leads Management SWOT
Read more...
  Customer Relationship Management
Customer Satisfaction & Retention- Data Management
Supply Chain for Customer Service and Support
Customer Service and Support Overview
Customer Service and Support - Strategic Role
Exit barriers for Customer Retention
Read more...
  Human Resources & Leadership
Give feedback closer to the observation
Develop Self and Others
Fostering Innovation
Roles and Level based Competency Segregation
Maximize the output first and then the potential
Read more...
 
 
Business Performance & Planning
Scorecards need manual finish
SWOT Assessment Report
Strategy Map to Strategic theme
Strategic Vision and Mission
Review Session should stay focused
Read more...
  Business Intelligence & Data Quality
Dimensional Modeling vs. Relational Modeling
Business Intelligence organization roles
There is never true-blue DW
Metadata Repository Extraction Design
Dimensional Attributes+ Facts + Source Matrix
Read more...
  IT Vendors & Tools Management
Collaboration and Administration Support
OLAP Architecture Cache Management
Report Development for Enterprise Reporting
Metadata Repository sharing
Vendor future plans Strategic fit
Read more...