SAP took the wraps off planned updates to its data warehousing, data integration and on-demand BI plans a bit at the SAP Insider BI and Portals event in Orlando in late March. There were some modest surprises: the unexpected absence of Marge Breya, who was in Walldorf apparently getting a broader set of responsibilities (a week later, still no official word about that); a delay in the release schedule and changed naming of the next Business Warehouse release; and a strong (and thus encouraging) Data Services message that reaffirmed Business Objects openness.
Wellesley Information Services puts the Insider events on (and publishes the magazines and books), so it’s not exactly “official,” but clearly SAP dominates the event. There was a decent partner presence as well among the event sponsors, and a sizable amount of the content was from consultants, partners and customers. In all, the picture was fairly healthy. My discussions with attendees made it clear their objective was educational and hands-on, and they universally expressed satisfaction with that content. Disney properties continue to disappoint for events like this – after a decade of hosting conferences week in and week out, the Dolphin and Swan are still riddled with no-connectivity spots, and power is rarely available for laptops.
Franz Amman took the stage for Breya in the keynote slot, and the sudden switch clearly had an impact on the story, which seemed a bit disjointed. SAP issued no press releases and the only really specific news was the new name for the former 12 Sprints, now named SAP StreamWork. There were some demos, as usual, and discussion of upcoming releases without a clear timeline, but that is more of an issue for analysts and journalists than users.
A few highlights for me:
SAP is advancing BW and BW Accelerator, driving more access to non-SAP data for broader, deeper support for applications like sentiment analysis and advanced visualization. As can be seen from this link, though, from a Google search done on April 2, 2010, the branding is still trapped in the old NetWeaver messaging. There was a lot of discussion of Data Services, particularly important because of the push to make Business Warehouse and the BW Accelerator a repository for non-SAP data as well. Data Services can source data from many places into the BW, and SAP wants to get people thinking about that. “We’re dropping it into columnar format and compressing it in memory,” was the story, “and that will drive excellent performance.” I’m eager to see a customer talk about that. The planned 7.2 release was delayed, though, and now there will be a 7.3 release that makes room for advances in the architecture of SAP applications. So the priorities seem to lag the message.
SAP continues to be clear that their portfolio will have a common ribbon across all the tools, and the same UI everywhere. The objective is to “take your context along with you.” For this, role orientation – not just user name – is important, I pointed out to Amman in a conversation later. He agrees, but this was not discussed from the stage – admittedly, there wasn’t nearly enough time, given the sudden changes in plans and the absence of a clear set of messages about product plans and timing.
The BI Consumer Services (BICS) interface is important to legacy users, and users are getting protection, both technical and license-wise. Increasingly, the front end tools like Explorer will be able to run ad hoc in the next overall release with BO Universe-based views alongside in-place BICS connections to other data. It will not be necessary to convert BICS – “to get where you want to go will be seamless;” (i.e., you’ll be able to open and save in old the version.) SAP users today keep their BICS license, no additional “connection” or “integration” charges will be required.
SAP believes they will play a big role in the on-demand BI space. “Business Objects was the first BI vendor to go to on-demand; we have 300k subscribers for BI on demand,” Amman tole me. It’s a necessary part of the mix for them. One scenario: for a given customer, a warehouse picker might keep their stock list on a hand-held. For such applications, some of the UIs might not be from SAP at all – partners may build those apps and consume a stream from internal SAP data. This is a hybrid model: get the UI and templates from the cloud, use a proxy to combine your data with it.
Duet was not in the speeches; in fact it was only discussed in response to a direct question. Still, that answer suggested work is proceeding. SharePoint too, and SAP says those are not incompatible paths. Amman told me: “It’s not an either/or – we need integration with Office, we’re moving that forward. SharePoint is a different beast – everyone has multiple instances. I don’t want to force a choice, I want to support the ones they make.” Duet will continue to be an end-user and partner development environment to integrate SAP pieces into workflows for specifically purposed applications in a Windows environment.
Bottom line: SAP is still struggling to tell the Business Objects story while keeping their branding atop it. It’s strange to see SAP slides that offer BI On Demand for salesforce.com – but that’s exactly what Business Objects does, and SAP needs to get more comfortable with it. But that story is still just not loud enough; yes, the attendees are SAP customers – but very many SAP customers are Business Objects and not SAP at all. And this is all still looking rather unfamiliar to them. And NetWeaver got some ringing defense, but it’s time to acknowledge that it’s not the place to expend their branding efforts. SAP apps and Business Objects BI, data integration and warehousing technologies are the resonant labels. But recent surveys in several places have indicated that BO momentum has sputtered. That needs fixing, and soon.
Disclosures: SAP is a client of IT Market Strategy.
5 thoughts on “SAP Signals Changes At Insider Event – Vaguely”
I am a keen follower of SAP and their strategy in the data management and decision support arena.
BW is getting huge heat from Gartner, analysts (e.g. Nigel Pendse), practitioners and customers (!). Lets face it, it is not a good product. Kind of a dinosaur from the 90’s. Why do they keep ‘working’ at it, I wonder. The answer is pretty obvious; the installed base is huge and BW is completely entwined with other SAP modules, which makes it hard to get rid of it and just go for a good solution. They got the tools now (Acta-DI-DS is very good stuff)…..
SAP BW for non-SAP data; how will SAP BW handle (lets take an example) CDR records, POS records. Massive data that screams for lean an mean modelling and load architecture. Every right minded architect will never use BW for this kind of data. And this is just 1 example. Lead- and deployment times for getting BW to work is just horrific, especially when you want to get non-SAP data into BW.
Integration between BO and BW is a laugh atm. Off course, the plans are good but aren’t they always 😉 If a company is now standardized on Business Objects,using BW underneath is a nightmare and even a prime argument not to use BW. There is no integration….
And the sad thing is; If you talk 1:1 to the former Business Objects experts who now work with SAP, they acknowledge this….
SAP has got a problem, and its name is BW. They got huge chances; they got the business content, they (still) have the customers, they got the tools (e.g BO) and they got the knowledge. Now lets offer your clients a good, connected and open data management solution….
One often-overlooked aspect of SAP analytics and data warehousing is the ETL problem. Extracting and transforming SAP data to use for reporting and analytics is no simple matter. Of course, cleansing (e.g., master data management) is even harder, but even that process must start with decent ETL tools.
One great advantage of SAP BW is that it has the only robust, thorough tools for getting data out from SAP (the “extractors”).
— Dennis Moore