May 5, 2016
Feature Story
Three Steps for Transitioning
to a New DW/BI Environment
Patty Haines
Chimney Rock Information Solutions

Organizations are now dealing with the challenges of working with multiple versions of their data warehouse/business intelligence (DW/BI) environment, continuing to use previous versions while building out their new environment.

They have been through generations of their data warehouse program with multiple architectures, including multiple schemas and databases. Some of these environments may not have been fully implemented, utilized, or well documented but became critical to the business community.

What should you do when your organization begins the journey to build and implement a redesigned DW/BI environment? Can the previous environment live in harmony with these new environments or should it be scheduled for imminent retirement?

There will be new tables for the new DW/BI environment with possibly new levels of detail and different aggregates. There may be different data sources. What should the business users do? How do they utilize both the previous and new DW/BI environments—or should they? What approach should you take to help your user community down a temporary but nonetheless challenging road?

The previous DW/BI environment often has more subjects populated utilizing more sources than the new environment will have when the first release is implemented. There may be hundreds of legacy reports and queries users have built and depend on that provide insights into their business. The users have learned the pieces of data that are questionable and know the work-arounds or data plugs they need to complete before distributing these reports.

When implemented, the new DW/BI environment will have more complete data. It will deliver more snapshots and historical data. It will also provide a complete data dictionary with business definitions and examples of each piece of data, along with better audit controls not part of the previous environment.

There are numerous options for organizations to take, but all require analysis and discussion with business users to develop a road map for implementing the new environment quickly and accurately. Here are the three steps you can take to build that road map.

Step 1. Evaluate both DW/BI environments

A good starting point is to analyze the DW/BI environments by understanding and comparing the differences in architecture. Create a subject and source map for both environments that shows the type of data in each and makes the differences in available data clearly visible.

Include the detail and summary levels and how data is aggregated, the triggers for creating new records, and if and how changes and deletions are identified, captured, and processed in these environments.

This analysis will help determine if tables from the previous and new DW/BI environments can be joined together accurately or if a set of bridge tables can be built to help merge data from both environments. This should be a temporary measure used for a short period of time until the new DW/BI environment has the same subjects and sources as the previous one, fulfilling the needs of the business community. It may be decided that the two environments are so different they need to remain separate.

Step 2. Evaluate existing reports and queries

Understand how your previous DW/BI environment is being used by your business community. Start by building an inventory of reports that are currently used in the previous environment, providing information about the purpose, responsible user, distribution, frequency, main subject, and priority or ranking of the report. It is helpful to understand the lineage of data from the source through the tables into the query tool, reports, and queries.

Through this report analysis, many of the reports and queries may be marked for retirement. Some may be removed because they duplicate other reports; some can be modified slightly by adding parameters to the report to provide more flexibility; and some may be incorrect and should not be used by the community because of data issues.

This analysis will help identify the minimum requirements of the business community and help the DW/BI team understand what needs to occur next in the DW/BI road map.

Step 3. Build the road map

Finally, plan and build the road map with the right steps to get the new DW/BI environment into production and make it a useful tool for the business community. The plan needs to clearly delineate which environment to use for specific needs. It may include building bridge tables to enable some users to use tables or sets of tables from both environments or, perhaps, building a temporary user interface that accesses both environments accurately and when appropriate. It may entail rolling out this new environment for some users and not for others based on the type of reports and queries each group needs. Make this period of transition user friendly and easy to understand.

The plan should include the next subjects and capabilities the new DW/BI environment will provide, along with a planned schedule to help the users understand how it will be built out and when they will need to rebuild reports. The DW/BI project team may need to consider helping the users redesign and create their reports in the new environment, so together they can create as much reusability as possible. The plan should also encompass a time frame for retirement of the previous DW/BI environment (e.g., by sets of tables, subjects, or sources) along with corresponding reports and queries.

Summary

It’s time to build out your road map—your plan and schedule—by defining the way to help the business community get the reports they need from the previous DW/BI environment and by defining the way your enterprise moves to the new environment. As your business community begins to see the advantages of your new environment, they will want to speed down that road even faster.

To ensure your new DW/BI environment is a success, work with your business community to get down that bumpy road as smoothly and quickly as possible. The journey will be worth it.

Patty Haines is founder of Chimney Rock Information Solutions, a company specializing in data warehousing and data quality.

TDWI Onsite Education: Let TDWI Onsite Education partner with you on this journey! TDWI Onsite helps you develop the skills to build the right foundation with the essentials that are fundamental to BI success. We bring the training directly to you—our instructors travel to your location and train your team. Explore the listing of TDWI Onsite courses and start building your foundation today.

 
Announcements
NEW TDWI Infographic
Data Warehouse Modernization in the Age of Big Data Analytics
NEW Best Practices Report
Data Warehouse Modernization in the Age of Big Data Analytics
NEW Ten Mistakes to Avoid
In Preparing for IoT Analytics
NEW Business Intelligence Journal
Business Intelligence Journal, Vol. 21, No. 1
NEW TDWI E-Book
Data-Driven Analytics: Knowing What You Don't Know
NEW Checklist Report
Seven Best Practices for Adopting Data Warehouse Automation
contents
Feature
Three Steps for Transitioning to a New DW/BI Environment

What Makes BI 'Enterprise'?
Feature
ETMs for Analytics:
The Internet of Things

Mistake: Failure to Think Through Deployment Readiness
Education & Events
Seminar in San Francisco
Modern Data Modeling //
Big Data

Embassy Suites, San Franciso Airport-Waterfront
May 23–26
Seminar in Boston
Leadership // Data Governance and Data Quality

The Westin Copely Place
June 6–9
TDWI Accelerate in Boston
The Westin Copley Place
July 18–20
Webinars
When Worlds Collide: Using the Data Lake to Connect Old and New Technologies
Thursday, May 12
Delivering Business Value Faster with Visual Data Discovery
Wednesday, May 25
Getting to the Next Level with Visual Analytics and Governed Data Discovery
Tuesday, May 31
Agile, Fast, and Flexible: Five BI and Data Management Strategies for Meeting New Business Challenges
Thursday, June 9
Marketplace
TDWI Solutions Gateway
Oracle – See the Full Picture with Oracle Data Visualization
TDWI White Paper Library
Is the Data Warehouse Dead? (An Information Difference Research Study)
TDWI White Paper Library
7 Ways Alteryx Makes Data Preparation, Blending & Analysis Easier for Excel

Premium Member Discounts

Ready to take the CBIP Exams or attend our next conference? Take advantage of these exclusive member discounts.

$275

Discount

on TDWI Accelerate

$26

Discount

on CBIP Exam Guide

Flashpoint Insight
What Makes BI 'Enterprise'?

Business intelligence helps management better understand the condition of their organization through descriptive analysis while moving into predictive analytics to better assist and plan with forward-looking analysis.

It is useful to individuals running their own businesses and to executives in global corporations. In the past, only the latter businesses were referred to as “enterprise,” but the democratization of powerful technologies means even smaller companies can access disparate data and visualize analytics as larger enterprises do.

However, enterprises often fail when attempting to add BI to their IT offerings. One problem is that many technologists look to technology first. To address enterprise BI, start by understanding what management needs and then translate that into technical solutions.

The companies that build a truly integrated platform, with data and metadata fully shared and managed from source through desktop, will have a strong advantage. Software developers need to provide a smooth, vertically integrated information chain from source to visualization.

Learn more: Read this article by downloading the Business Intelligence Journal (Vol. 21, No. 1).

 
TDWI Research SNapshot
ETMs for Analytics: The Internet of Things

The Internet of Things (IoT)—a network of connected devices that can send and receive data over the Internet—is a hot market topic. These devices might be cellphones or wearable devices or sensors on components on airplanes and on machines in oil rigs. It is predicted that there will be tens of billions of these devices connected over the Internet in the next few years.

The idea behind IoT has been around for years, but the combination of cheap compute, advances in microprocessors, and more advanced software is making this a reality. This network is a trend in and of itself, but the analytics that can be performed on this data is where the value is. Analytics will play a big role in IoT, from the simple to the complex.

Although only 16% of respondents are analyzing IoT data in their organizations today, more than double that amount said they are thinking about it (see Figure 15). The use cases for IoT are wide, varied, and growing across virtually every industry. We asked respondents and subject matter experts to provide examples of how IoT is being used in organizations today. These include:

Quantified self. This is the movement to gather information about a person’s daily life. Several healthcare organizations reported using or planning to use wearable medical devices to monitor patients. Some organizations utilize wearable fitness devices in conjunction with loyalty programs. Other businesses promote wearable fitness devices to encourage healthy lifestyles. For instance, one respondent mentioned that her company organized teams that are using wearable fitness devices for company activity challenges between business units. The organization feels that this promotes fitness and team building.

Preventive maintenance. The idea behind preventive maintenance is to identify and fix problems with equipment and other assets before they occur. The data associated with past failures is used to predict the probability of potential future problems. One respondent from a financial institution stated that they are using IoT to gather information at branch and ATM networks to understand behavior and prevent equipment failures. Others mentioned that IT is using it to predict data center failures. Respondents in other industries said that they are using the IoT to monitor systems in remote locations (such as in the utility industry) or to monitor complex, expensive equipment such as on an oil rig.

Asset monitoring and tracking. Tracking assets (especially expensive assets) can help maintain the bottom line. Some respondents in the transportation industry are using radio-frequency identification (RFID) to track assets. Others cited using RFID to track items such as produce to promote freshness.

Can’t disclose. Some respondents felt that their IoT implementations were too sensitive to discuss because they provide competitive advantage.

(Click for larger image)
Click to view larger

Of course, there are many other use cases for IoT. This is an emerging technology that is in its infancy. However, TDWI expects to hear much more about IoT in the coming few years. Some important areas will be around data management, data security, data connectivity, and data analysis for IoT.

Read the full report: Download TDWI Best Practices Report: Emerging Technologies for Business Intelligence, Analytics, and Data Warehousing.

 
Flashpoint Rx
Mistake: Failure to Think Through Deployment Readiness

Most likely an IoT analytics project will involve IT and/or developers, so they need to be ready. IT readiness falls into several categories, including technology readiness, data management readiness, analytics readiness, and security readiness.

Although organizations often think through the technology needed for processing and managing the data along with how to build their skill set, they often don’t think through what happens once the analytics are developed and ready to be deployed.

For example, as we mentioned, models are one kind of analytics that might be utilized to examine IoT data and take action. Yet, TDWI research has found that it can often take months to deploy an analytics model into production. There are a few reasons for this. First, organizations often re-code a model after it is produced. This can take time, although vendors do provide software that can make this process faster. Additionally, organizations often don’t think about who is responsible for deploying the model. Successful organizations have dedicated staff to operationalize projects.

Model management is also important for deployment because models can get stale and must be updated over time. Even models developed in a stream need to be managed. It is also important to make sure that the model is documented. A model repository can be helpful in monitoring and updating models that are instantiated into a process.

Read the full issue: Download Ten Mistakes to Avoid in Preparing for IoT Analytics (Q1 2016).