Monday, August 20, 2007

No SAP DW, No Oracle BI, but Kalido. Why?

I am asked this question a number of times. I give the same answer that Bill Hewitt, Kalido's CEO and President, gave to Jim Ericson in a recent interview. It goes like this;

"All the ERP vendors are saying it's about SOA. SAP says we can provide everything: middleware, information management, transaction systems. Oracle says the same thing. What customer in their right mind wants to go back to buying every piece of their stack from one vendor? If you want to deliver your applications with a database flavor, then Oracle is a great place to go. If you want to deliver your middleware with a manufacturing flavor, SAP is a great place to go. But SAP has rolled out their second try at MDM [master data management], and it's failing because while they understand applications, they don't understand data. Oracle understands data but they don't understand applications. What we promote is maintaining separation between the five layers of your IT environment that move at different speeds: your infrastructure, your security, your information management, your applications and your user interface. Eventually, SOA is going to be the technology that brings all that together, but I don't think you should need to have your information management come out of your transaction systems or vice versa. What customers want is interoperability between the layers of the IT stack so they can make changes that suit their environment as they grow or shrink or change in other ways."

No comments:

Loading...