BI Past, Present, Future — Interview with TEC

May 9, 2012
503 Views

TEC banner

TEC banner

Note: the following post is republished with permission from Technology Evaluation Center’s excellent blog. It is a part of a series of interviews by Jorge Garcia on trends in the analytic industry.

 

It is hard to imagine that organizations like SAP or former Business Objects (BO)—now a division of SAP—were once start-up companies. Nowadays on the business intelligence (BI) scene it’s almost impossible to avoid BusinessObjects. Like many other successful companies, SAP has grown into itself by offering a product that applied a radical approach to a business problem solution, and this is particularly true of its BusinessObjects stack of BI solutions. In this installment of my Thinking Radically interview series, I had the pleasure to speak with Timo Elliott, a prominent personality in the BI space.

Mr. Elliott was one of the first employees of the original French company Business Objects, which SAP acquired in 2007. He has held various positions, including Senior Product Director for SAP BO. With vast experience in the BI arena, Mr. Elliott is now part of SAP’s elite squad of “technology evangelists.”

Below, he comments on the past, present, and future of BI and SAP’s analytics products and technologies.

Hello, Mr. Elliott. Could you give us a brief overview of your career within the BI space and with SAP BusinessObjects?

TE: I’m a statistical economist by training, but when I left school, I wanted to see the world. I ended up working on an analytics project at Shell in New Zealand, with a makeshift system including a mainframe reporting tool, exports to Lotus 1-2-3, custom macros, and a pen plotter.

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

I’ve had a variety of roles over the last 20 years, but one thing has been consistent: I’ve always been lucky enough to have a market-facing role, spending time understanding customers’ real-life information challenges. My role now is “technology evangelist”—I spend a lot of time at conferences and using social media, doing my part to explain new BI technology and how to achieve its full benefits.

Back in the early days of BO, what do you think it did that was so radically differently to be a leader in the BI space?

TE: Clearly, we had the right product at the right time: organizations had valuable information locked away in their databases, and you had to have technical knowledge to get it out (although Oracle at the time positioned SQL as an “English-like language” for power users). We pioneered the notion of a “semantic layer” that let business people access information using standard business terms and which automatically generated the complex SQL required to get the data from the database.

BO also benefited from great management from its founders, Bernard Liautaud and Denis Payre. They were determined to create a “Silicon Valley start-up” on the outskirts of Paris that included rapid expansion and a global vision. There were a few stumbles along the way, but in the end, it became the second European software start-up (after SAP!) to reach a billion dollars (USD) in revenue.

What are the main differences in the way organizations do BI now compared with how they did it in the past?

TE: Clearly, the technology has changed a lot over the years, but the business requirements remain remarkably similar: cutting costs, finding new opportunities, beating the competition, getting closer to customers… The biggest change is perhaps that BI is now clearly mainstream—only a tiny fraction of organizations don’t have some sort of BI in place, even if it’s only using spreadsheets.

What are the most common complaints from companies about what a BI solution should do but doesn’t?

TE: The dream of most organizations is to have a BI solution that just works—people believe strongly in the benefits of BI, but wish that it were easier to put in place robust solutions.

A new wave of technology, including in-memory techniques, holds the promise of making some of the processes much simpler. But many of the most intractable problems stem from business processes themselves (organizations with 20 different definitions of “customer” etc.), and are consequently much harder to fix. There’s also the problem of expectations: as soon as you provide better BI systems, business people can (and should) move on to new and even more difficult questions. I don’t believe people will ever be completely happy with their information systems (and if they were, it might be a sign that they needed more imagination!).

SAP is working hard to position HANA with its customers and in the market. Regarding its relationship with SAP’s BI stack of products, how can SAP HANA be a real game changer for SAP BO customers and SAP customers in general?

TE: SAP HANA combines a series of technologies (in-memory, column stores, in-database calculations, etc.) to create a truly innovative alternative to traditional BI infrastructures. Early customers are now starting to reap the benefits in the form of radically faster access to large quantities of data. This is allowing them to make better decisions, earlier, and more often, and fix potential problems in real time, rather than analyzing what failed in the past.

How does HANA modify the traditional BI cycle, and what is the impact on the business?

TE: I think the biggest benefit of HANA isn’t actually its speed—after all, every new generation of databases has been faster than previous versions. What’s different about HANA is the way it “collapses the layers” between data and analysis, and radically simplifies the implementation of new BI projects. When business people come up with a new analytic need, IT should no longer have to say, “Come back in six months when we’ve managed to get the data into the data warehouse.”

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

0

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

1

How about cloud computing? What is your view on SAP’s cloud service strategy, especially for BI and in light of SAP’s recent acquisition of SuccessFactors?

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

2

From your point of view, what is the difference between BI and business analytics, and the difference in the way they are applied by organizations?

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

3

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

4

What is your view on the general maturity level of businesses in regard to BI applications? Are there key areas for improvement organizations still have to address? Which ones?

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

5

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

6

What is your position regarding the adoption of big-data technologies (especially Hadoop) and SAP’s strategy for adopting these technologies?

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

7

What’s your vision for BI, your expectations for its future?

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

8

A few countries later, I joined Business Objects in 1991 as the eighth employee—prompted largely by the realization that the project that had taken me a month at Shell could be done in less than a day using SkipperSQL (as the BO product was then called).

9

I’ve had a variety of roles over the last 20 years, but one thing has been consistent: I’ve always been lucky enough to have a market-facing role, spending time understanding customers’ real-life information challenges. My role now is “technology evangelist”—I spend a lot of time at conferences and using social media, doing my part to explain new BI technology and how to achieve its full benefits.

0

What is your favorite wine?

I’ve had a variety of roles over the last 20 years, but one thing has been consistent: I’ve always been lucky enough to have a market-facing role, spending time understanding customers’ real-life information challenges. My role now is “technology evangelist”—I spend a lot of time at conferences and using social media, doing my part to explain new BI technology and how to achieve its full benefits.

1