Saturday, March 28, 2009

BI Giant has Clay Feet

Jean-Michel Franco opens his Information Management's March 2009 Special Report by pointing out a problem with today's corporate BI usage:


It took more than 30 years for BI to reach maturity, a little longer than it took for other key components like enterprise resource management and customer relationship management. But whilst the latter have seen the creation and redesign of entire information system landscapes in a big-bang mode, BI investments have taken place in a gradual and often ad hoc manner. In spite of unifying concepts such as the data warehouse, each decision support project often generated its own tools and selection of service providers, architectures, data models and standards. As a result, despite the fact that BI and performance management represent more than 10 percent of the typical IT budget, it can be compared to a giant with clay feet: strong footprint, but sparse foundations.

While uncoordinated, decentralized Business Intelligence implementations and usage may not have been an issue in the past, Franco says that has changed -- BI now provides companies with mission-critical functionality that requires centralized strategy and management.

Franco urges companies to "review and streamline their decision support architecture" and define "a cohesive BI roadmap." As part of the strategy, Franco recommends establishing a corporate team dedicated to Business Intelligence.

Read Franco's whole report at Information Management's website and, if you have not already read it, see my blog on establishing good BI foundations.

Thursday, March 26, 2009

Business Intelligence Foundations

When I stopped at Steve's house, his wife directed me to the backyard where I found him standing knee-deep in a muddy trench he had just dug along his newly-built family room.

Clearly frustrated, Steve climbed out of the pit and gave me the low-down on his outsourced home addition project. He thought the hired builders knew what they were doing and everything seemed fine at the time.

A few weeks later, however, Steve noticed that the windows didn't open or close smoothly. They stuck slightly when you slid them up or down. Strangely, one of the windows cracked. Coming home from a week-long vacation, Steve discovered another window had broken. With the help of a carpenter's level, Steve began to figure out the mystery.

To prove a theory, Steve grabbed his shovel and dug down to the room's concrete footings. He discovered that the main wooden beams for the new room were not even on the concrete foundation; they were off to the side.

Evidently, the concrete person poured the foundation supports in the wrong place. When the next guys on the building project discovered the error, they must not have wanted to wait for a fix. Instead, they just let their wooden beams use the ground for support.

The builders' solution could be considered short-term, at best (just long enough for Steve to pay them).

After a few rains, the weight of the room caused the beams to sink into the dirt. The walls shifted and windows began to break. If allowed to continue, more serious structural damage was sure to happen.

The cost of fixing the problem after the room was built was going to be much higher than had it been addressed properly during construction.

So it is with Business Intelligence applications. If you build on a weak foundation, you will end up paying more later to fix your sure-to-happen future problems.

If you are thinking about implementing BI, what should you establish as the BI Foundation? I see three main components:

  • Business Intelligence Team (People)
  • Business Intelligence Standards (Policies and Procedures)
  • Business Intelligence Infrastructure (Technology and Data)


If you want a successful BI initiative, critical to the success is obviously executive sponsorship for the endeavor. Once you have that, your first step needs to be establishing a team of individuals to support the future BI infrastructure and users.

You could establish your BI team in different fashions. It might be a formally recognized group with its own organizational structure and funding (such as a BI Competency Center or Center of Excellence) or it may just be an informal “community of practice” supporting BI as a spare-time activity. Regardless, you should define these individuals’ responsibilities, accountabilities, and how their activities are funded.

Next, identify potential resources for membership within the BI team. Depending on how robust you would like to make your BI support, you could consider positions such as: BI Director; BI Architect; Subject Matter Experts (data, operational systems); Analysts (Database, Data Quality, BI); and Mentors and Trainers.

Your BI Team's first responsibility will be to establish formal standards for the future BI environment, including a shared corporate language, formal agreements, and service-level agreements (SLAs).

Your organization must formally define a corporate language of business terms, which will then be implemented as a standard within the BI environment. For example, you would define the term “profit,” and identify where it resides within the operational systems (or how it is calculated if it is not a physical element).

With an enforced shared language, all BI reports created within the organization will have terms of the same meaning – for example, no report should stray from corporate standards and calculate an alternate version for “profit.”

Your BI Team also needs to formal reach certain agreements about the BI environment. For example: Communication protocols between IT, Business, and BI Team; Change control procedures; and Responsibilities and Accountabilities; and Security.

Your BI Team should establish service-level agreements on important BI topics. These SLAs establish expectations for IT, Business, and BI Team as to their performance. For example, SLAs may be created for guarantees on: Data life-cycle (latency, length of storage, historical archiving, purging, etc.); Data quality (validity of data, guaranteed synchronization with operational systems, etc.); and Services (response times, quality of service, etc.).

With the BI Team and BI Standards in place, now it is time to consider technology and data -- the BI Infrastructure.

Conceptually, I break out the BI Infrastructure into three layers: 1) the user interaction/presentation component; 2) a centralized BI repository of data and metadata; and 3) an integration mechanism.

Users interact with BI in two main ways: by automatically receiving information (“push”) and by accessing online applications as needed (“pull”).

Automatically, users can receive regularly-scheduled standard reports, exception reports, and alerts sent to destinations such as printers, e-mail, or hand-held devices. Online users have access to interactive BI applications, reports, queries, analytics, and ad-hoc report writing features. This presentation layer will integrate with Microsoft Office for easy use of tools such as Excel spreadsheets.

The next layer is the centralized BI Repository. This is the company's “single version of the truth” used for all BI needs. Your BI Team will design the repository specifically for reporting to mask the complexity of the underlying operational systems, and fully document it for the users.

Depending on your company's BI needs, the BI Repository can consist of multiple data structures, such as a main relational database for general reporting, multi-dimensional cube structures for online analysis (OLAP), and star schemas for ad-hoc reporting needs.

In addition to structured data, a BI Repository might contain unstructured data such as scanned documents, Microsoft Office documents, and other files that are free-form in nature. These types of files typically require special BI capabilities such as content indexing, document management, and search engines.

Also in the BI Repository will be the organization’s definition of abstract terms (hierarchies, Master Data Management, virtual calculations, etc.) and a metadata layer.

Lastly is the BI Integration Layer, which performs the functions of accessing the complex operational data, transforming data into understandable information, and loading the BI Repository. Here, your BI Team will define integration rules such as: Mapping of physical data (Source to Repository); Rules for calculating virtual columns; and Rules for Extract, Transform, and Load operations.

Yes, this sounds like a lot of work for just the foundation.

If you are considering skipping this critical step and jumping right into building BI applications, think about Steve standing in a muddy pit. Then picture yourself in a similar situation in the near future.

If you still decide to move forward without first implementing a solid BI foundation, be sure to have your own level and shovel nearby.

Sunday, March 1, 2009

SAS: Great Revenues in a Bad Economy

Jim Goodnight, the CEO of SAS, is happy. Not only did Gartner rank his company as a leader in the Enterprise BI Platform category, he saw a 5% revenue increase over the previous year and 2600 new customers.

In their February 2009 press release, SAS reported $2.26 billion in 2008 revenues. Goodnight says,

We achieved our 33rd year of revenue growth in the worst economy most can remember. This growth is a direct result of being a stable privately held company, which allows us to invest in long-term relationships with employees and customers.


Unliked some other BI software vendors, SAS created new jobs. At the end of 2008, SAS employed over 11K individuals, an increase of 3.5% from 2007 (240 people joined the SAS ranks as part of the acquisitions of Teragram and IDeaS Revenue Optimization).

You can read the entire press release on SAS's website.

Declining Business Intelligence Jobs in 2009?

For some time now, I have used Monster job searches to gauge demand for Business Intelligence technologies. What I failed to do, however, was keep a good record. Had I done that, I might have been able to spot BI trends. So that became my 2009 New Year's Resolution: do a consistent monthly BI job search and ponder the results.

Comparing Monster U.S. job postings in February 2009 to the previous month, I see a marked decline for BI keywords. For the standard products (e.g., SAS, Cognos, Business Objects, Reporting Services, etc.), my unscientific study shows 22% fewer job postings (5,923 openings in January and 4,594 in February).

SAS has the biggest demand within BI and it appears to be growing, at least as a percentage of the total BI jobs in the United States. In January, SAS jobs accounted for 20% of the total standard BI jobs and increased to almost 26% in February.

The open source keywords (BIRT, Pentaho, Jaspersoft, and QlikTech) experienced a much bigger decline -- 36% -- although the small number of job postings for these technologies probably makes the change meaningless (25 and 16 for January and February, respectively).

I also looked for a job posting trend for programming language keywords such as COBOL, RPG, C++, Java, and .NET. While demand for these also declined, the drop was less than that for BI products -- down only 6% (13,109 postings in January to 12,308 in February). Within this category, demand for Java far exceeded any other programming language.

Now that I have committed this New Year's Resolution to you, I will try to keep it up each month (perhaps I should have blogged about a weight loss/exercise plan!).

About Me

My Photo

Summary:

With over 20 years of industry experience, Doug Lautzenheiser has provided business intelligence services for well-known organizations such as Procter & Gamble, JPMorgan Chase, Omnicare, Wendy’s International, the State of Indiana, and the State of Oklahoma. ComputerWorld recognized one of Doug's projects with honors for innovative use of technology.  Doug is a featured blogger on BI software at Smart Data Collective.

With his broad knowledge of technologies, business processes, and industry best practices, Doug provides client value by performing strategic advisory services; leading tactical BI application development projects; and enabling dramatic reductions in time, cost, and risks through his unique automated BI consolidation application.

Doug has hands-on experience with a variety of enterprise applications. He is degreed summa cum laude in Information Systems from the University of Cincinnati. An experienced trainer and mentor, Doug has provided educational services to organizations such as National Semiconductor, Ford Motor Company, Northwest Airlines, Principal Financial Group, and Target Stores. Doug is the owner of Kencura Systems.

Talk to Doug before manually performing a large BI initiative. Doug will show you how other smart companies saved time and money by following proven methodologies and automating BI processes instead of letting somebody "wing it" with a manual approach.

Specialties:

B2B software vendor leadership. BI implementations, standardization, and consolidation; data warehousing; WebFOCUS; iWay; BI vendors (Cognos, SAP Business Objects/Crystal Reports, Microstrategy, Actuate, Hyperion/Brio, SAS, Tableau Software); ERP; and full SDLC.