Showing posts with label Kobielus. Show all posts
Showing posts with label Kobielus. Show all posts

Tuesday, August 18, 2009

BriefingsDirect Analysts Discuss Software AG-IDS Scheer Acquisition and Prospects for Google Chrome OS

Edited transcript of BriefingsDirect Analyst Insights Edition podcast, Vol. 44 on Software AG's acquisition of IDS Scheer and the implications of the Google Chrome operating system.

Download the transcript. Listen to the podcast. Find it on iTunes/iPod and Podcast.com. Charter Sponsor: Active Endpoints. Also sponsored by TIBCO Software.

Special offer: Download a free, supported 30-day trial of Active Endpoint's ActiveVOS at www.activevos.com/insight.

Take the BriefingsDirect middleware/ESB survey now.

Dana Gardner: Hello and welcome to the latest BriefingsDirect Analyst Insights Edition, Volume 44. I'm your host and moderator Dana Gardner, principal analyst at Interarbor Solutions.

This periodic discussion and dissection of IT infrastructure related news and events, with a panel of industry analysts, comes to you with the help of our charter sponsor, Active Endpoints, maker of the ActiveVOS visual orchestration system, and through the support of TIBCO Software.

Our topic this week on BriefingsDirect Analyst Insights Edition, and it is the week of July 13, 2009, centers on Software AG's bid to acquire IDS Scheer for about $320 million. We'll look into why this could be a big business process management (BPM) deal, not only for Software AG, but also for the service-oriented architecture (SOA) competitive landscape that is fast moving, as we saw from Oracle's recent acquisition of Sun Microsystems.

Another topic for our panel this week is the seemingly inevitable trend toward Web oriented architecture (WOA), most notably supported by Google's announcement of the Google Chrome operating system (OS).

Will the popularity of devices like netbooks and smartphones accelerate the obsolescence of full-fledged fat clients, and what can Google hope to do further to move the market away from powerhouse Microsoft? Who is the David and who is the Goliath in this transition from software plus services to software for services?

Here to help us better understand Software AG's latest acquisition bid and the impact of the Google Chrome OS are our analysts this week. We are here with Jim Kobielus, senior analyst at Forrester Research. Hi, Jim.

Jim Kobielus: Hey, Dana. Hello, everybody.

Gardner: Tony Baer, senior analyst at Ovum.

Tony Baer: Hey, Dana, good to join you again.

Gardner: Brad Shimmin, principal analyst at Current Analysis.

Brad Shimmin: Hi there, Dana, and hi, everyone out there.

Gardner: Jason Bloomberg, managing partner at ZapThink.

Jason Bloomberg: Good morning, everybody.

Gardner: JP Morgenthal, independent analyst and IT consultant.

JP Morgenthal: Hey Dana, and for you fellow people, that's @JPMorgenthal for you.

Gardner: There you go. Also, Joe McKendrick, independent analyst and ZDNet and SOA blogger. Welcome, Joe.

Joe McKendrick: Hi, Dana, glad to be here.

Gardner: Let's start on the whole Software AG bid. JP, I just learned this morning that you were an architect there at IDS Scheer. Tell us a little bit about why you think this is a big deal.

Morgenthal: No, I wasn't at IDS. I was at Software AG. I was there prior to the webMethods acquisition.

Gardner: Yes. My mistake. Sorry.

Morgenthal: No problem. It's really interesting. When we first started thinking about building out a SOA platform and making Tamino the heart of it, the metadata repository, it was one of the key applications we saw for Tamino in a SOA platform. I actually was looking for different metadata partners.

I looked at IDS Scheer back then and that's what they were sowing a while back, so I had lost track of them and come back to find that now they're driving the whole concept of business process design, which is really interesting.

It seems that the general consensus on the acquisition, though, seems to be focused heavily on their association with SAP, and that the move seems to be driven by more of a business relationship than a technical relationship. If you look at the platforms, there is some overlap between the webMethods platform and the ARIS platform.

So, it would make sense that, if they were going after something, it wouldn't be just more design functionality. There has to be something deeper there for them to grow that business even larger, and certainly SAP is a good target for going after more additional business.

Gardner: So, is this an acknowledgment that SAP needs a SOA partner and that this is Software AG's move on the dance floor to sort of step up the music a bit?

Morgenthal: SAP probably doesn't believe that they need an SOA partner, but I think that the fish are starting to nip around the outer boundaries. SAP customers are to the point now, where they are looking for something more immediate, and obviously the redevelopment of SAP as a complete SOA architecture is a long-term endeavor.

So, how do you start moving there in an incremental fashion? A lot of SOA platform vendors are starting to identify that there is a place for them on the outer edges, until SAP gets to make its full transformation.

Gardner: Hey, Jim Kobielus, do you agree that this is more than just a technology acquisition? What do you think? Does SAP need a SOA dance partner?

Kobielus: Does Software AG?

Gardner: No, SAP, and that Software AG is perhaps an intermediary step.

Kobielus: Wow, that's an interesting question. Honestly, I don't think SAP needs another dance partner here. Let's say, hypothetically SAP acquired Software AG. What could Software AG with IDS Scheer on board offer SAP that they don't already have? There is the BPM. There is the enterprise application integration (EAI). I don't really see anything obvious.

Gardner: JP, help him out. Why did you make that statement?

Feeding at the outer edge

Morgenthal: Well, I made the statement that the groups, like the combined effort of a Software AG with webMethods and IDS Scheer actually becomes one of the feeders on the outer edges of the SAP market. While SAP is in its cocoon, it needs to turn from caterpillar into SOA butterfly, and heaven knows whether that will actually survive that transformation.

There are a lot of SOA platforms starting to eat at the outer edges of the cocoon, feeding off of that, and hoping the transformation either fails or that there will be a place for them when the SOA butterfly emerges.

Kobielus: I don't think that necessarily Software AG would be a good fit for SAP. There are a lot of redundancies. I don't think that this notion of a Teutonic hegemony has legs here.

What's really interesting here is that, clearly Software AG is on a tear now to build up their whole

I think it goes both ways. You can't separate the technology from the strategic implications of this deal

SOA stack. I blogged on this under Forrester. People didn't realize that IDS Scheer is actually now a business intelligence (BI) vendor. They've got a self-service mashup BI product called ARIS MashZone, in addition to the complex event processing (CEP) product and an in-memory analytics product.

IDS Scheer, prior to this acquisition, has been increasingly positioning themselves in the new generation of BI solutions. That's been the one area where Software AG/webMethods has been deficient, from my point of view. In these SOA wars, they're lacking any strong BI or CEP capabilities.

Now, IDS Scheer, their BI, their CEP, and their in-memory analytics is all tied to business activity monitoring (BAM), and all tied to BPM. So, it's not clear whether or when Software AG, with IDS Scheer on board, might start turning all of that technology or adapting it to be more of a general purpose BI CEP capability. But, you know what, if they choose to do that, I think they've got some very strong technologies to build upon.

Gardner: Tony Baer, how do you come down on this technology, filling in the cracks, as Jim Kobielus believes, or the larger strategic implication that JP was alluding to?

Baer: I think it goes both ways. You can't separate the technology from the strategic implications of this deal.

For one thing, I don't think SAP itself thinks it needs a partner, in that, through NetWeaver, it has tried to control the middle tier in addition to the application tier, but they've not been that humongously successful in the market.

The other thing is that, yes, they have essentially defined an architecture for exposing their processes as services. They keep changing the names of it, so I forget what the latest acronym for it is. But, from the SAP standpoint what they lack is SOA governance. They lack a lifecycle there. SAP has always been very much around its own internal governance, and that's been a really interesting omission.

Other dimensions

More broadly, there are other dimensions to this deal, which is that Software AG's webMethods business gets a much deeper process-modeling path. I don't know how redundant it is with the existing modeling. I don't think there are many BPM modeling languages that are deeper than ARIS, and that's selling pretty awesomely. As a matter of fact, you can look at Oracle, which uses it as one of the paths to modeling business process, along with the technology they picked up from BEA.

Gardner: So what's the theory there, Tony, that the tool and its popularity will drag in some more on the infrastructure side?

Baer: For Software AG, what it’s going to drag in is immediate access to the SAP base, and that's huge. It also basically lays down a gauntlet to IBM and Oracle, especially Oracle, which has an OEM agreement. All of a sudden they have an OEM agreement with a major rival, as they're trying to ramp up their fusion middleware business in their SOA governance story.

Gardner: There is a lot of that going on nowadays.

Baer: Oh heck, yes, and so I see this as being incredibly disruptive, and I think a very smart move for Software AG.

Gardner: Let's go to Brad Shimmin. It seems like we've got some jockeying going on, and there aren't really too many mid-tier SOA infrastructure players left that these other behemoths can play chess with, their little pawns that they can move in front of their other players and play one OEM's agreement deal off of another, as they all try to come up with the total stack. What's your perspective, Brad? Are we almost at the end of the SOA consolidation process?

Shimmin: I don't think so. When you look at the big players, just as you said there, Dana, with their little OEM games -- reindeer games -- that get played, those are becoming less and less of an issue.

Look to the governance. About two years ago, most of the vendors are OEM. That certainly has turned around, such that these vendors, the big players we're talking about here, are very much providing in-house stacks. That speaks to what Tony and JP have been saying about getting some governance and SAP and getting better middleware and SAP customers. That's why I think this is such a big deal, and, as Tony was saying, why it's so disruptive.

It's not just that they have a fuller stack now, but there is a more complete stack for SAP customers. NetWeaver has been hanging in there. SAP definitely thinks it is middleware, but then why else would there be so many players on the outside, providing integration services for SAP applications running on not NetWeaver

But, back to your question about the smaller players, Dana, it seems like it's now a class society, where you have the big players -- the IBMs, Oracle, SAPs, and now Software AGs of the world -- and then you have the rogue players in these open-source space that are coming up, that have room to play.

We're talking about the Red Hats, the -- I'm blanking on the others here. There are probably three or four software vendors out there that are playing just in the open-source middleware space that has a great player like WSO2. Another one that's really good is MuleSource, although they're kind of limited.

Bifurcated environment

The point is that, when you have this really bifurcated environment, it gives you fewer acquisitions and more competition, and that's what's going to be great for the industry. I don't see this as leading to further consolidation at the top end. It's going to be more activity on the bottom end.

Gardner: Jason Bloomberg, isn't there no small dose of irony that the SOA landscape is being driven by folks trying to do it all? I thought the whole notion of SOA was being able to include more players and more components to interact and interoperate. What's going on?

Bloomberg: That's a important point to bring up. This IDS Scheer announcement really doesn't have anything to do with SOA. That is surprising, in a way, but also consistent with some of the fundamental disconnect we see within Software AG, between the integration folks on one hand and the BPM folks on the other.

There are some people within Software AG, typically the CentraSite team, Miko Matsumura and his strategy team, who really understand the connection between SOA and BPM. But, for the most part, basically the old guard, the German staff, just doesn't see the connection.

This fundamentally confuses the marketplace, because you have the integration-centric SOA

Whoever wrote the press release doesn't even understand that SOA is architecture. It makes you wonder where the disconnect is.

message out of Software AG. You have the metadata-driven CentraSite message that tries to pull it together, but doesn't have a dominant position within the context of the Software AG marketing. Then, you have the BPM folks, who just don't understand that SOA has anything at all to do with BPM.

If you read the 'BPM For Dummies Book' that Software AG put together, for example, they don't even understand that SOA has any connection to BPM. Software AG released a press release a few weeks ago that described SOA as a technology. Whoever wrote the press release doesn't even understand that SOA is architecture. It makes you wonder where the disconnect is.

With the IDS Scheer acquisition, if you read through what Software AG is saying about this, they're not connecting it with their SOA story. This is part of their BPM story. This is a way for them to build their vertical BPM expertise. That's the missing piece.

They have this BPM capability that they got from webMethods, and there is some Fujitsu technology in there as well. Poor Fujitsu, I guess, is the odd one out on this one. Software AG is looking to add some vertical capabilities, but because they're not tying it with the SOA story, they run the risk of continuing to be the outlier player, when it comes time to compete against Oracle and IBM.

They don't understand

Kobielus: Let me butt in a second, because in Forrester we've been discussing this. We don't think that Software AG understands fully who they are acquiring, because they don't really fully understand what IDS Scheer has on the SOA side. They don't understand the BI and CEP stuff.

So, I agree wholeheartedly with what Jason is saying. They're acquiring them just for the BPM, but that really in many ways really understates what IDS Scheer potentially can offer Software AG.

Bloomberg: Yeah, that's a good point. It's worth highlighting that IDS Scheer does have some pretty solid SOA capabilities within the context of their BPM focus.

Now the question is what Software AG will do with that part of the story. Will it get lost in the shuffle or will it really be integrated into the overall SOA stack in a way that enables them to have a better process-driven SOA story?

That's going to be a challenge for them, because that involves some shifting of thinking, not

They're acquiring them just for the BPM, but that really in many ways really understates what IDS Scheer potentially can offer Software AG.

across the whole organization, but within this sort of old guard Software AG folks who have been resistant to this part of the story.

Morgenthal: Just to add a little more fodder, if I haven't lost track of who's who in Software AG, isn't the person who ran this acquisition Dr. Kürpick, if I have that name right. Didn't he come out of SAP, and isn't he more focused on the business process end of things than the SOA end of things?

Bloomberg: Who wants to chime in on that one?

Kobielus: It is Kürpick, but I don't know what his background is.

Morgenthal: I believe he came out of SAP, and I believe his background is on integration and BPM.

Gardner: So, JP, to your point, we seem to have a mixed understanding of whether BPM is the source or a larger infrastructure benefit. I think you were making the point that the BPM could be perhaps a point on the arrow. If you've got your tool embedded, if you've got business process expertise, and you are moving down the stack from the process level, that that could be something that would drag in other aspects of a SOA environment.

Morgenthal: This is funny, because this keeps coming up over and over. Early on, I used to work with BrainStorm Group on their SOA BPM shows, and, at the height, the BPM show got up to like 600 people. I was doing the SOA side of the story in the track.

Driving the business

At the breaks, I would go talk to these people, and the BPM people would all look at me like I was talking another language, and say, "I don't deal with that." These are people who were doing BPM initiatives in their organization, they were like, "That's for the IT guys. I'm the business." So, time and time again, I found out that the BPM people were the ones driving the business.

Now, the number of people who have been attending BPM conferences has been dropping significantly, saying basically that if training went out to the business people, the business people are doing the business analysis. They are using the BPM tools like IDS Scheer more than webMethods, which would be the IT stuff.

At the BPM level, a lot of the initiatives are still, I believe, with the business and hasn't translated down into IT dollars and IT deliverables. That's a big issue now with regard to this acquisition for Software AG. Before, they could only play on the IT side of this shop. They had no story to play with the business. Now, they can go back to all those people who are still doing this at the business initiatives and have a story for them, with a roadmap, for how to bring this into IT. I think that sells well. I think IBM uses that, but I still find IBM’s tools very IT-centric.

Baer: JP, you're right on the mark there. There has always been a huge cultural divide between

The question, then, for the vendors is which vendors can really support that story in a way that doesn’t defeat the purpose by a self-serving software sales pitch.

the business folks, who felt that they own BPM, versus the IT folks, who own the architecture or the technology architecture, which would be SOA. What’s really interesting and what's going to stir up the pot some more -- and this is still on the horizon -- is BPMN 2.0, which is supposed to support direct execution.

When I was over at Oracle a few weeks back, they were talking about their strategy. They were saying, that unless a business process, as you model in BPMN, is transactionally complex, you could theoretically make that model executable and essentially ace out IT. I'm a little cynical about that, but it's going to be an interesting thing that stirs up the pot in coming months.

Bloomberg: It's interesting you mention SOA as technical architecture, because that's a fundamental misconception of what SOA is about. SOA is really more of a style of enterprise architecture that pulls together both business and IT.

But, you're right that a lot of organizations still see SOA as technical architecture, as something distinct from the BPM, and those are the organizations that are failing with SOA. That part of the "SOA is dead" straw man is that misconception of SOA as about technology. That's what’s not working well in many organizations.

On the plus side, there are a number of enterprises that do understand this point, are connecting business process with SOA, and understand really that you need to have a process driven SOA approach to enterprise architecture.

The question, then, for the vendors is which vendors can really support that story in a way that doesn’t defeat the purpose by a self-serving software sales pitch. That's always difficult, because the software sales people are there to sell the software. So you don't buy SOA. You do SOA, and doing SOA includes business process work, as well as technology work.

Telling the story

The prize goes to the vendor who really can tell that story properly. That's difficult for all of them and they're all are struggling with this. That's the story for 2010. Will it be IBM, Oracle, or Software AG who tells an architecture-driven BPM/SOA/enterprise architecture (EA) story in a way that really does help organizations solve their problems, as opposed to just pushing the software and letting customers figure out how to use it.

Gardner: Thanks, Jason. Let me go to Joe McKendrick. Joe, it sounds like something we don't talk about too often is the importance of the sales function, the sales department, and how these things enter the market. It sounds as if the sales department is selling to the business side of the house, and that's how their strategy perhaps lines up.

Or, if they've got another product set that they're going to sell to the technology side of the house, well, then that's how they're going to continue to enter the market, because that's the side where they get the PO.

But, isn’t that self-defeating, when it comes to SOA as an architectural paradigm shift, as we've mentioned here? How do we that? Is there another step that we need in bringing SOA into the market that educates or changes the sales culture so that they don't simply go after the short-term product sale, but look for more strategic sale?

McKendrick: Yeah, Dana, that's a big challenge. You're right. The sales people from the vendors have specific relationships with individuals within companies. They may tend to be IT people on one hand or you may have some folks on the business process side, depending on the types of products, and usually the paths don't cross.

I wonder, too, with SOA. That's been the challenge, as we've been discussing about SOA. It's been confined somewhat to the technical side of the house, perceptually, and the proponents of SOA tend to come from the IT side.

Gardner: I guess what I was getting at, Joe, is that the separation between SOA and products seems to be taking place not just on the buy side. It's probably taking place on the sell side as well, as is demonstrated perhaps by what we're hearing today about the IDS Scheer buy being absorbed by one part of Software AG and not across the board.

McKendrick: Absolutely. You really can’t sell SOA. Theoretically, you don't need to buy any products to start SOA in your organization. It's ludicrous to try to sell SOA, the package itself. That's something that's been discussed for years -- selling SOA in a box. You can sell individual products.

Let’s face it. It's a tough environment, and vendors are on these quarterly cycles. They need to push the product out there, and they'll call it whatever they need to call it to get the product out. Maybe SOA is even diminishing as a sales term. It's cloud nowadays.

Gardner: Jim Kobielus, do you agree that this might be what we're up against? In a down economy, sales people need to sell, and, product-by-product, that's what they're going to go after. At the same time, they do an injustice to this larger architectural shift.

Shifting the focus

Kobielus: Yeah, for sure. What gives me hope on the Software AG-IDS Scheer merger is the fact that what I heard on the briefing is that Software AG realizes they need to shift from a technology and sales driven model towards more of a solution and consulting driven business model. First of all, that's the way that you lock in the customer in terms of a partnership or an ongoing relationship to help the customer optimize their business and chief differentiation in their business.

What I found really the most valuable thing about the briefing on the acquisition that we got from them the other day was IDS Scheer adding significant value to Software AG. Software AG pointed to the business process tools under ARIS. That's a given. They focused even more on the EA modeling capabilities that IDS Scheer has, and even more on the professional services on the vertical solution side and the BPA consulting side -- consulting, consulting, consulting, relationship building, solution marketing.

I think Software AG knows that they need to put the IDS Scheer solution focus first and foremost. In a down economy, that's the way to lock in these premium engagements and these

It's interesting hearing about the BPM and SOA disconnect, and it certainly doesn't surprise me.

ongoing relationships that will be essential for Software AG to differentiate themselves from vendors like IBM, Oracle, and SAP, who have been solution focused for quite some time in the SOA sphere.

Gardner: Tony Baer, we need to wrap up on the Software AG acquisition. Are there any other takeaways that we've missed on this one?

Baer: It's interesting hearing about the BPM and SOA disconnect, and it certainly doesn't surprise me. I totally agree with Jason. The problem is that it's a perception that those business stakeholders view SOA as the technology architecture and, more specifically, business process execution language (BPEL) as that bastardized execution language, which I think is probably a little bit of envy on their part.

I can sort of understand that there is a degree of creative tension within Software AG in terms of understanding the connection between BPM and the SOA.

I very much agree with Jim -- I'm Mr. Agreeable today -- that it really is all about solution sell. I was just up doing consulting yesterday with a vendor in the tools industry and telling them that they have to do more of a solution sell.

That's a really tough nut for vendors to crack, because, as the CEO was telling me, "I agree with you, but our sales guys still have quarterly numbers that they have to meet, and if customers want product, we're not going to say no." That's a tough one.

Gardner: Brad Shimmin, do you agree that the solution sell is a multi-year process, but right now these companies need to get some POs signed? Perhaps that's what at work here in terms of filling in of the cracks with this acquisition?

Pre-sales and post-sales

Shimmin: There is pre-sales and then post-sales, and the post-sales is very separate. You have your services organization, and as everyone has been saying here, that's the key to this IDS Scheer acquisition by Software AG.

Software vendors like IBM, Oracle and SAP, which are solution based, have these well established organizations, but do nothing except go out and say, "You know what? You really need to lead with BPM, and by the way, in order to make BPM work, you need to have this great infrastructure and architecture underneath and that happens to be using our SOA components." Those guys know how to do that.

Software AG, as we said, is going to take some time to get that up to speed. In the meantime, it's all going to be driven by the numbers. You're selling infrastructure, you're selling webMethods' software endpoints to the IT folks, and you're selling ARIS to the business folks. To bring those two together is going to take quite a bit of time.

Baer: I think it's kind of important to look at IDS Scheer's numbers. They've actually flattened out. The SAP market is pretty mature. Within the webMethods space, it's younger, dynamic and growing. That could be a way to give IDS Scheer and ARIS a bit of a jolt, if Software AG can deal with those structural issues.

Gardner: Okay. In the second half of our show, let's take a look at this WOA drive. I was

Everyone thinks this is an attack at Microsoft. I'm looking at it as a Mac user and see a huge hole in the market.

impressed with the Google Chrome OS, not necessarily on its technical merits -- we don't know too much about it yet -- but the idea that Google is willing to go toe-to-toe with Microsoft and sees the marketplace is ready to absorb an OS designed of, for, and by the web.

Does anyone else share my impression that this is a harbinger of a larger shift towards the web?

Shimmin: I just think it's reflective of the shift that's already underway. When you look at Google Chrome OS, it's Linux, which is a well-established OS, but certainly not something you would call a web-oriented OS. Chrome OS is really something akin to GNOME or KDE running on top of it. So, technologically, this is nothing spectacularly new.

I think that what Google is doing, and what is brilliant about what they're doing, is that they're saying, "We are the architectural providers of the web, people who make the pipes go, and make all of you able to get to the places you want to go in the web through our index. We're going to build an OS that's geared toward you folks. We're going OEM and through vendors that are building netbooks, that are definitely making a point of contention with Microsoft. Because Microsoft, as we know, is really not pleased with the netbook vendors, because they can't run Vista or eventually Windows 7."

Gardner: Not only that, but they can't charge the full price that they would have liked to charge for an OS, because these things only sell for $400.

Shimmin: Exactly.

Morgenthal: I have differing opinion, and of course an opportunity to tick off the entire Slashdot audience. Everyone thinks this is an attack at Microsoft. I'm looking at it as a Mac user and see a huge hole in the market. I've got to pay almost $2,000 for a really good high-powered Macintosh today. All they did was take BSD Unix and really soup it up so that your basic user can use it.

Out of the slime

People on the Linux side are like, "Oh, Linux is great now. It's really usable." I've got news for you. It's no way nearly as usable as Windows or the Mac. As far as usability, Linux is still growing out of the proverbial slime.

But, if you take that concept of what Apple did with BSD and you say, "Hmm, I'm going to do that. I'm going to take Linux as my base and I'm going to really soup up the UI. I'm going to make it really oriented around the network, which I already did, and I have a lot of my apps in the Cloud, I don't necessarily need to build everything large scale. I still need to have the ability to do video, tie things in, and make that usable, but I'm also going to be able to sell it on a $400 netbook computer."

Now, you're right down the middle of the entire open market, because people can't stand Windows XP running on these netbooks. As was previously said, you can't yet run Windows 7 yet or Vista. We don't know what Windows 7 is going to look like, as far as usability, and the Mac is costing way too much.

There is a huge home run right through the middle. You just run right up the center and you've

First of all, it's vapor, because this is not going to be released, I think, until the second half of 2010.

got yourself a massive home run. It doesn't have to be about going after the enemy. It's not about hurting the enemy. It's about going after your competitors.

Gardner: If Mac OS stays in the top tier and something like Google Chrome OS comes in, the only other player to suffer is Microsoft. Isn't that who gets squeezed out?

Morgenthal: No, I actually think you're starting a grass-roots effort that could knock Apple out, because Apple's maintained its proprietary nature. If you can deliver the equivalent of an Apple-based set of functionality and the usability of the Mac on a $400 netbook, or a bigger if you want, you hurt Apple. You don't hurt Windows.

Gardner: I appreciate your point, but I think that Apple is okay at the top tier. I think this is more aimed at the bottom of the Windows tier, and the price-sensitive audience, both in the consumer and business spaces. What do you think Jim Kobielus?

Kobielus: I think it is, exactly what you said, Dana. First of all, it's vapor, because this is not going to be released, I think, until the second half of 2010.

Gardner: Yes, second half next year.

Kobielus: And, they haven't announced any real features. They haven't announced any final pricing. It will probably be nil or nothing. There's so much that has yet to be defined here. How long ago was it they introduced Android, and how much adoption does Android have in the mobile space?

Gardner: Well, it's got developer hearts and minds, which is probably important.

"Google hegemony"

Kobielus: Yeah, yeah. People keep expecting the big "Google hegemony" to evolve or to burst out, so everybody keeps latching onto these kinds of announcements as the harbinger of the coming Google hegemony and all components of the distributed internet-work Web 2.0 world. I just don't see that happening.

I think this is exciting. They've got all these kinds of projects going, but none of them has even begun to deliver for Google anything even approximating the revenue share that they get from search-driven advertising.

So, this is interesting, but a lot of Google projects are interesting. Google Fusion Tables are interesting for analytics, but I just can't really generate a big interest in this project, until I see something concrete.

Gardner: Okay. Tony Baer, are you ho-hum on this as well, or do you think that this signals that the OS gets buried underneath that layer that is your Web interface and your ability to coordinate with cloud services level?

Baer: I vote for the ho-hum. I agree with Jim. Their business model has been, so far, throwing

Some may need netbooks. Some may want smartphones. Some, like myself, still deal with regular brick computers. It's just a diversity.

as much mud at the wall as possible and seeing what sticks. To date -- and this is one place where I would actually agree with Steve Ballmer -- they've really been a one-trick pony.

You've got to put this in perspective, The Microsoft Office base is not a growing base. It does indicate, though, that there are many types of alternative clients that are emerging, and I don't think anybody has claimed those emerging clients. So, JP has an interesting point in terms of that. It basically fills the hole that Apple is not trying to fill.

Gardner: What about the iPhone. Doesn't the iPhone fill that hole? It's a low entry at $200 and does a lot of what a PC does.

Baer: Well, iPhone, compared to a computer, is low entry, but its expensive compared to a smartphone.

Shimmin: I am sorry to interrupt you, but Apple has netbook coming out in October too, so they're trying for that market as well.

Baer: I'll grant you that point. The important thing mostly is that it does point to a new diversity of clients. Some may need netbooks. Some may want smartphones. Some, like myself, still deal with regular brick computers. It's just a diversity.

So, I think that's really what Google's move heralds. As to whether Google really actually shoots in the long run, I'm waiting for the evidence.

Gardner: Okay. Jason Bloomberg, how about you, a ho-hum or a shift?

Mostly irrelevant

Bloomberg: At ZapThink, we're focused on the enterprise. We talk primarily to enterprise architects who are really trying to figure out the big picture of how enterprise IT resources can meet the ongoing changing business needs. From that perspective, Google is mostly irrelevant. So, I'm definitely in the ho-hum category.

Sure, maybe they will carve out a niche in the netbook OS market, but from the perspective of the enterprise, that's a very small piece of what they're worried about.

Gardner: Let me go to Joe McKendrick. Joe, does what Google has brought to the table have an impact on the enterprise?

McKendrick: Eventually it does. The Google Chrome OS is kind of a marker on the road. I think back to why I started using Google several years ago, and I think why a lot of people started using it. It was so fast. I used AltaVista, Yahoo, Lycos, and all these other search engines, and I just liked Google, because it was real fast. It got me to where I was going in a very fast and efficient manner.

I don't know about Chrome delivering this capacity, but I think what's happening is that the OS is becoming more something that's getting in the way of where you want to go.

I use XP and Vista both. I'd rather just get on the computer and get immediately to where I want

Why can't everyone have a client computer, a device that simply has some kind of very thin OS and the browser connecting them to all the cloud services they need?

to go on the Web and not have to fuss around with all these features with the OS - booting up, security features, updates, patches, and so forth.

I think the world is moving that way. Why can't everyone have a client computer, a device that simply has some kind of very thin OS and the browser connecting them to all the cloud services they need?

That's what's great about smartphone. I love the smartphone because it just goes to where you need to go very rapidly. You're not fussing with the OS. It's more of an embedded, invisible, thin capability, and that's what enterprises are looking for as well.

Gardner: JP, we talked about OEM agreements and how important they are behind the scenes in the technology industry. The OEM agreements that Microsoft has with their hardware vendors are perhaps seeing some strain.

Microsoft didn't do any favors for their hardware vendors with the debacle that Vista was, particularly as that came during the precious year or two before this recession. That could have driven a lot of sales that now will probably never happen.

Do you think that Google, not only has an opportunity to come into the market, as you mentioned, with a technology, but perhaps is going to be a friend of the enemy for these hardware people. They'll probably give this thing away and allow these hardware developers, distributors and creators to benefit from the services marketplace of advertising in a sort of backhanded way, and they get basically free software from Google as a result?

Who'll win the desktop?

Morgenthal: For them, it comes down to who is going to win with the desktop applications. That's what it comes down to. The only reason these hardware vendors are making the investment in Microsoft is because customers want a Microsoft platform, most likely because they are running Office or some other Microsoft application. It's what they're trained on and still comfortable with.

There's a great video out there that Google did asking people on the street, like a Jay Leno walk by, what is a browser? About 92 percent of people didn't even know what the browser was. They're like, "The browser is Google. Yeah, I go to Google." They don't understand it's an application that renders HTML. They don't know that. They have no clue.

It's very easy in this day and age, we get on a phone, we talk, and we know the stuff inside and out. You've got to realize that 92 percent of people out there don't get it. It's easy for Microsoft to go put up a video that shows how great Vista is and how people were snookered into, "Wow, that's the next version of the OS. Look how cool it is. No, it's really Vista." Of those 92 percent of people, you don't think at least 50 percent of those are still going to come in and say, "I want a Vista machine," after seeing that? Of course they are. That's why the hardware vendors don't have a choice.

Microsoft doesn't have to worry. Yes, they want to make good friends with these people, but

I don't know what Google really wants. Basically . . . they're going to throw as much mud against the wall and see what sticks.

ultimately it's the consumers who are coming in and saying, "I want this type of machine, I don't trust that Linux stuff. I don't know anything about that. I don't want to go there. I was told if I go there, I'd better know how to actually get to a command line and work." That's what they still hear.

Gardner: Tony Baer, JP says that the hardware people don't have a choice. Does Google want to give them a choice?

Baer: I don't know what Google really wants. Basically, as Jason and I were saying, they're going to throw as much mud against the wall and see what sticks. I like Jim's metaphor on them being the Xerox PARC for Web 2.0.

If Google were serious, in other words, if they really did have a more of a strategic business plan for this, I would say yes. But, as long as it's just, "Let's just throw something else out there, and by the way, this is not going to come for another 12-18 months," I have a hard time taking this seriously.

Gardner: Brad Shimmin, suppose I'm HP, Dell, or I'm Acer, and I need to sell these $400 netbooks, because that's my only growth area right now and might be for the next two years, before these corporate budgets start growing again. I could sell that thing for $400. Microsoft is going to take $150-200 just for the OS, and Google wants to give a free OS. What am I going to do?

Let the user decide

Shimmin: I would have both of them on there, and let the users make a choice. I'm still thinking about the price tag.

Gardner: For the Microsoft OS.

Shimmin: That's what I'm saying. They want to make a buck and they'll do it the best way they can. If they're getting it free from Google, they'll put it on there as a option, but they'll still pay homage to Microsoft, because, as we've been saying, it has to be. They still have ownership of the desktop.

In my mind, the curious thing about all this is that what's made the iPhone and the BlackBerry so successful is that they're self-contained machines. The OS and the hardware are very tightly controlled and very tightly integrated. What's made the PC and the Windows OS such a pain and so detrimental to productivity is that it's very much the opposite of that.

The Mac -- and I'm a Mac user too by the way -- is that it makes us more productive. The OS

The Mac . . . makes us more productive. The OS doesn't get in the way of the Internet. It actually makes the Internet better.

doesn't get in the way of the Internet. It actually makes the Internet better. It's because it's a controlled environment, but it's really expensive to do the things that way as a company, due to costs in manufacturing.

If Google Chrome is going to go out there the way Android has gone out there, which is, "Let's look for some OEM vendors to make this work and it's going to be based on Linux," I don't ever see it actually doing what the BlackBerry and the iPhone have done in terms of making the 'net better.

I think that it's going to be for those Slashdot folks, who really like that kind of thing and want to make it go. I see this taking a lot longer for the white label stuff to really make things work as well as the closed environments have.

Gardner: Well, I'm afraid we will have to leave it there. I appreciate everyone's input.

We've been talking about the acquisition by Software AG of IDS Scheer, and also the possible impact that the Google Chrome OS could have in the market. It seems most of our people think, that's not such a big deal.

I also want to take this opportunity to thank our sponsors for the BriefingsDirect Analyst Insights Edition Podcast Series; they are Active Endpoints and TIBCO Software.

I also want to thank this week's panelists, Jim Kobielus, senior analyst at Forrester Research. Thanks, Jim.

Kobielus: Always a pleasure.

Gardner: How about a little excitement there, Jim?

Kobielus: I am still overstimulated. That's a redundant statement.

Gardner: Are you overstimulated too Tony Baer, senior analyst at Ovum?

Baer: I really love these podcasts, Dana.

Gardner: Nicely done. Brad Shimmin, principal analyst at Current Analysis.

Shimmin: Still here, and not even caffeinated.

Gardner: Jason Bloomberg, managing partner at ZapThink, thanks for joining.

Bloomberg: Come to our new SOA and Cloud Governance course.

Gardner: Excellent. JP Morgenthal, independent analyst and IT consultant. What plug do you have for us JP?

Morgenthal: Until next time.

Gardner: Joe McKendrick, independent analyst and ZDNet and other web property blogger extraordinaire in SOA and BI and all sorts of things, right?

Morgenthal: Call me Joe "not a slave to fashion" McKendrick.

Gardner: Thanks very much. This is Dana Gardner, principal analyst at Interarbor Solutions. Thanks for listening and come back next time.

Download the transcript. Listen to the podcast. Find it on iTunes/iPod and Podcast.com. Charter Sponsor: Active Endpoints. Also sponsored by TIBCO Software.

Special offer: Download a free, supported 30-day trial of Active Endpoint's ActiveVOS at www.activevos.com/insight.

Edited transcript of BriefingsDirect Analyst Insights Edition podcast, Vol. 44 on Software AG's acquisition of IDS Scheer and the implications of the Google Chrome operating system. Copyright Interarbor Solutions, LLC, 2005-2009. All rights reserved.

Take the BriefingsDirect middleware/ESB survey now.


SPECIAL PARTNER OFFER

SOA and EA Training, Certification,
and Networking Events

In need of vendor-neutral, architect-level SOA and EA training? ZapThink's Licensed ZapThink Architect (LZA) SOA Boot Camps provide four days of intense, hands-on architect-level SOA training and certification.

Advanced SOA architects might want to enroll in ZapThink's SOA Governance and Security training and certification courses. Or, are you just looking to network with your peers, interact with experts and pundits, and schmooze on SOA after hours? Join us at an upcoming ZapForum event. Find out more and register for these events at http://www.zapthink.com/eventreg.html.

Thursday, August 06, 2009

BriefingsDirect Analysts Debate the 'Imminent Death' of Enterprise IT as Cloud Models Ascend

Edited transcript of BriefingsDirect Analyst Insights Edition podcast, Vol. 43 on the health of corporate IT and whether reports of its demise are premature.

Download the transcript. Read the summary blog post. Charter Sponsor: Active Endpoints. Also sponsored by TIBCO Software.

Special offer: Download a free, supported 30-day trial of Active Endpoint's ActiveVOS at www.activevos.com/insight.

Dana Gardner: Hello and welcome to the latest BriefingsDirect Analyst Insights Edition, Volume 43. I'm your host and moderator Dana Gardner, principal analyst at Interarbor Solutions.

This periodic discussion and dissection of IT infrastructure-related news and events with a panel of industry analysts and guests comes to you with the help of our charter sponsor, Active Endpoints, maker of the ActiveVOS, visual orchestration system, and through the support of TIBCO Software.

Our topic this week on BriefingsDirect Analyst Insights Edition, and it is the week of June 8, 2009, centers on the pending purported death of corporate IT, and perhaps the unplugging of the last on-premises Web server any day now.

You may recall that in the early 1990s, IT pundits, and my former boss Stewart Alsop, glibly predicted at InfoWorld that the plug would be pulled on the last mainframe in 1996. It didn't happen.

Stewart apologized, sort of, and the mainframe continues to support many significant portions of corporate IT functions. But Stewart's sentiments are newly rekindled and expanded these days through the mounting expectations that cloud computing and software-as-a-service (SaaS) will hasten the death of on-premises enterprise IT.

Some of the analyst reports these days indicate that hundreds of billions of dollars in IT spending will soon pass through the doors of corporate IT and into the arms of various cloud-service providers. We might conclude that IT is indeed about to expire. Not all of us, however, subscribe to this extent in the pace of the demise of on-premises systems, their ongoing upkeep, maintenance, and support.

To help us better understand the actual future role of IT on the actual floors inside of actual companies, we're joined by our guests and analysts this week. First, Jim Kobielus, senior analyst at Forrester Research. Hey Jim.

Jim Kobielus: Hey, Dana. Hey, everybody.

Gardner: Tony Baer, senior analyst at Ovum.

Tony Baer: Hey, Dana. How are you doing?

Gardner: Brad Shimmin, principal analyst at Current Analysis.

Brad Shimmin: Hi, Dana.

Gardner: Ron Schmelzer, senior analyst, ZapThink.

Ron Schmelzer: Hi, guys, just unplugging my mainframe, as we speak.

Gardner: And, for the first time on our show, Sandy Rogers, former program director at IDC, and now independent IT analyst and consultant. Welcome, Sandy.

Sandy Rogers: Thanks, Dana. Great to be here.

Gardner: And, as our guest this week, welcome Alex Neihaus, vice president of marketing at Active Endpoints. Hey, Alex.

Alex Neihaus: Hi, Dana. Hi, everyone.

Gardner: Well, let's start with you, Jim Kobielus, if you don't mind.

Kobielus: I don't mind.

Gardner: We've heard this before, the same story, new trend, new paradigm shift, money to be saved, pull out the plug, you'll get it off the wire, or you'll get it from much lower cost approaches to IT.

I do believe that cloud computing is going to have a pretty significant impact and we've discussed that quite a bit on our show so far. What's your take? Do we have a sense of the mix? Is there any way to predict what's going to happen in, say, five years?

Death notice premature

Kobielus: There are plenty of ways to predict what's going to happen in five years. I need to buy a dartboard. That's one of the ways. I can predict right now, based on my conversations with Forrester customers, and specifically my career in data warehousing and business intelligence (BI). This notion of the death of IT is way too premature, along the lines of the famous Mark Twain quote.

If you look at a vast majority of enterprise data warehousing in BI environment, there is a bit of a movement toward outsourcing of the date warehouse into the cloud. There is a bit of a movement toward moving more of the report and dashboard and analytic application development to the end user or to the power user or subject matter expert and away from the priesthood of mathematicians, statisticians, professional data modelers, and data-mining specialists that many large companies have.

There is a bit of a movement in both directions. But it's only movement. In other words, there aren't a substantial number of enterprises that have outsourced their data warehouse or their marts. Probably there aren't that many commercial options yet that are fit to do so. Only a handful of data warehousing vendors offer a hosted solution, a SaaS, or cloud solution. I've been telling people that 2009 is not the year of the cloud in data warehousing, nor is 2010. I think 2011 will see a substantial number of data warehouses deployed into the cloud.

Gardner: Well, Jim, will that be taking them off of the corporate network and putting them in the cloud or will they just be new ones on the cloud?

Kobielus: The component of your data-warehousing environment that will be outsourced to public cloud, initially, in many cases, will not be your whole data warehouse. Rather it will be a staging layer, where you're staging a lot of data that's structured and unstructured and that you're pulling from both internal systems, blogs, RSS feeds, and the whole social networking world -- clickstream data and the like.

They will be brought into cloud storage services that will operate as a staging layer

First is security. You need strong control and you need to also be able to monitor it 24/7, because it's the most fundamental thing that you run your business on.

where transforms, cleansing, match and merge, and all those functions will be performed on massive amounts of data. We're talking about petabytes where it makes more sense, from a dollars-and-cents standpoint to use a subscription service in a multi-tenant environment.

Gardner: We're still going to see data growing on-premises as well.

Kobielus: Yeah, we're definitely going to see data growing a lot on-premises. The core data-warehousing hub where your master data is stored -- for most companies of most sizes -- will remain on-premises for lots of reasons. First is security. You need strong control and you need to also be able to monitor it 24/7, because it's the most fundamental thing that you run your business on.

There are lots of reasons why the centerpiece of your data-warehousing environment, the master tables, were made on-premises. For the foreseeable future, I sense strong reluctance from corporate IT to outsource that. As to the whole front-end mash-up side of these all sort of developments, I'm doing a report that will be published in about a month on the uptake of that approach. But, that's several years down the road, before we see that come to fruition. So, I don't think IT is dying anytime soon.

Gardner: Tony Baer, what about applications?

Cloud is transformational

Baer: Well, I just completed actually a similar study in application lifecycle management (ALM), and I did find that that cloud certainly is transforming the market. It's still at the very early stages, but it's not going to be basically a one single, monolithic, silver-bullet approach. And, not all pieces in the app lifecycle are as well suited for the cloud as others.

I found that two areas really stuck out. One is anything collaborative in nature, where you need to communicate -- especially as development teams go more global and more distributed, and of course, as the pace of business changes the business climate and accelerates -- it's more important than ever to get everybody on the same page, almost literally. So, what I found was that planning, budgeting, asset management, project portfolio management, and all those collaborative functions did very well.

At the other end of the scale, another side that did very well was something that I think Jim was sort of hinting at, which is anything that had very dynamic resource needs,

When you're developing code, you don't want to have to deal with any type of network latencies that are going to come up when you deal with cloud.

where today you need a lot of resource, tomorrow you don't. A good example of that is testing -- if you are a corporate IT department, which has periodic releases, where you have peaks and valleys in terms of when you need to test and do regression test.

Gardner: Platform as a service (PaaS)?

Baer: Yeah. What I found though that did not map well to the cloud was anything that related to source code. There were a number of reasons for that. One is, basically, that developers like to have the stuff on their own local machines.

There is a degree of control that you like, but there are some tactical reasons. When you're developing code, you don't want to have to deal with any type of network latencies that are going to come up when you deal with cloud. No matter how good the bandwidth, there are always going to be times when there are going to be some speed bumps.

But, the other part was also related to IP, which is source code before it's compiled in the binaries. It's basically pretty naked and it's pretty ripe for stealing. This is your intellectual property. Today, if you're doing development, it's because there aren't packages that are available to supply a generic need. It's something that's a process that's unique to your organization.

So, I got a lot of reluctance out there to do anything regarding coding in the cloud. There is the Bespin project on Mozilla, but that's the exception to the rule. So, in terms of IT being dead, well, at least with regard to cloud and on-premise, that's hardly the case in ALM.

Gardner: Brad Shimmin, why do we see these reports, some of them coming out of Wall Street? They're supposed to be smart money saying $120 billion of IT is going to be in the cloud in the matter of two or three years. Is it that they don't understand what cloud is, or are they dead wrong?

Shimmin: I don't think they're dead wrong. As Tony was saying, it depends on what you're putting in the cloud. Because I follow the collaboration area, I see that happening much, much more quickly, and, frankly, much sooner than even the discussion we've been having recently about cloud computing.

Way back in the late 90s, and early "0-dots," Microsoft and IBM were making big money out of their managed hosting services for Exchange and Notes, and they are pushing that downstream a little bit more now to get to the channel and the long tail.

Gardner: So there is not a lot of intellectual property in a messaging transfer agent?

Bothersome IT functions

Shimmin: That's just it. Those are the functions that IT would love to get rid of. It's like a diseased appendix. I would just love to get rid of having to manage Exchange servers. Any of us who have touched any of those beasts can attest to that.

So, even though I'm a recovering cynic and I kind of bounce between "the cloud is just all hype" and "yes, the cloud is going to be our savior," for some things like collaboration, where it already had a lot of acceptance, it's going to drive a lot of costs. If that's what Wall Street is talking about, then, yeah, I think they're pretty much accurate.

Gardner: Ron Schmelzer, we certainly heard a lot about cost reduction. It's certainly top of mind in a recession. I also think that cloud computing can offer some significant cost savings, but to what degree are we talking about disrupting the status quo in most IT departments?

Schmelzer: It's really interesting. If you look at when most of the major IT shifts happen, it's almost always during period of economic recession. The last time was in 2000-2001, when we first started really talking about service-oriented architecture (SOA). In the mid- '90s was when we really started pushing out the Web. In the early part of the '80s, when recession was kind of bad, that's when personal computers started coming about.

You kind of go back into this package every time. Companies are like, "I hate the systems I have. I'm trying to deal with inefficiency. There must be something wrong we're doing. Let's find some other way to do it." Then, we go ahead and find some new way to do it. Of course, it doesn't really solve all of our problems. We spend the next couple of years trying to make it work, and then we find something new.

The cost-saving benefit of cloud is clearly there. That's part of the reason there is so much attention on it. People don't want to be investing their own money in their own infrastructure. They want to be leveraging economies of scale, and one of the great things that clouds do is provide that economy of scale.

From my perspective on the whole question of IT, the investments, and what's going to happen with corporate enterprise IT, I think we're going to see much bigger changes on the organizational side than the technological side. It’s hard for companies to get rid of stuff they have invested billions of dollars in.

Gardner: Wait a minute. So, this is like a neutron bomb. The people die, but the machines keep running?

Schmelzer: Actually vice versa. The machines might change and the machines might move, but IT organizations will become a lot smaller. I don't really believe in 4,000-person IT organization, whose primary job is to keep the machines running. That's very industrial revolution, isn't it?

Gardner: Sandy Rogers, the theory is good, the vision is good, but so was the theory in 1995 that you'd pull out the last mainframe in a year. What's your perspective, given that you've been tracking enterprise infrastructure software for quite some time?

The cost of change

Rogers: Well, it's interesting. Many organizations have avoided legacy modernization projects due to the cost of change. It's not just about the technology replacement. It's a loss of capabilities. It's the change in human workflow and knowledge base. All that is a critical consideration. I see enterprises all the time that are caught between a rock and a hard place, where they have specialized technologies that were built out in the client-server era. They haven't been able to find any replacements.

So the idea of software-as-a-service (SaaS), that one-to-many model, means the kinds of replacements that are available will be very generic in nature, for the most part. There will be some niche capabilities, moving way out in the time horizon. But, the ability to take a legacy system that may be very specialized, far reaching, have a lot of integrations and dependencies with two other systems is a very difficult change. A company has to get to a very specific point within their business to take on that level of risk from change.

Gardner: It's one thing to change from a legacy system to a more modern standard-based hardware and operating system platform environment and to frameworks

It's not to say it won't be done, but it certainly has a big learning curve that the whole industry will be engaging in.

for development. That's not quite the same, though, as making a transition to cloud. Do you think they go hand-in-hand?

Rogers: One thing to think about is there are so many different layers of the stack that we're talking about. When we're talking about cloud and SaaS, it's going to impact different layers. So, there may be some changes in the types of deployments that go on, the target locations.

It reminds me of the film, Pretty Woman. That's "just geography," and that's the way I envision the first wave moving out. We may want to think about leveraging other systems and infrastructure, more of the server, more of the data center layer, but there is going to be a huge number of implications as you move up the stack, especially in the middle-ware and integration space, and pick and choose different applications and their capabilities.

There are a lot of systems out there that are not designed to be run in this kind of capacity. We're still at the very beginning stages of leveraging services and SOA, when you look at the mass market. What I've been discovering in speaking with enterprises that are either doing SaaS as a business or as an enterprise is that the first thing they're thinking about is that the architecture has to able to support this kind of dynamic access and the ability to scale.

So, there's a lot of work that needs to be done to just think about turning something off, turning something on, and thinking that you are going to be able to rely on it the same way that you've relied on the systems that have been developed internally. It's not to say it won't be done, but it certainly has a big learning curve that the whole industry will be engaging in.

Gardner: Not about just pulling a plug at all.

Rogers: Yeah.

Gardner: Alex Neihaus, you're someone who's actually in the software business -- unlike the rest of us. And, by the way, thanks very much for sponsoring the show. We really appreciate it.

Neihaus: Our pleasure,

Gardner: Tell me a little bit about your perspective as someone who is delivering software, productivity, and value to enterprises. Why not go up on someone else's cloud and deliver this strictly as a service?

Borg-like question

Neihaus: We think that this is a Borg-like question -- who assimilates whom? Ron was exactly correct that cloud and the associated technologies that we describe today is today's shining new toy. What we find more interesting is not the question of whether the cloud will subsume IT or IT will subsume the cloud, but who should be creating applications?

And, there is a meta question, or an even larger question, today of whether or not end users can use these technologies to completely go around IT and create their own applications themselves? For us, that seems to be the ultimate disingenuousness, the ultimate inability for all the reasons that everyone discussed. I mean, no one wants to manage an Exchange server, and I was glad to hear Brad include Notes Server in that list, but, in fact, IT is still doing it.

So for us, the question really is whether the combination of these technologies can be made to foster a new level of collaboration in enterprises where, frankly, IT isn't going to go away. The most rapid adoption of these technologies, we think, is in improving the way IT responds in new ways, and in more clever ways, with lot more end-user input, into creating and deploying applications.

You hear a lot of people talk about the generational shift in business people. I agree that there is a lot more familiarity with IT among business end users, but we don't

For us, the cosmic question is whether we are really at the point where end users can take elements that exist in the cloud and their own data centers and create processes and applications that run their business themselves.

hear from our customers that business end users even want to be in the business of creating or manipulating applications in IT, in the cloud, or anywhere else.

Gardner: What I hear you saying is that you see the IT department as your customer, but also, at some level, the end user is your customer. You need to make them both happy, but can you make that end user happy without the IT department?

Neihaus: Our answer is no, simply because of some of the things that Sandy was talking about. There are legacy systems -- there are plenty of things lying about, would be the right way to put it -- that need to be integrated, using technologies that are modern and appropriate.

For us, the cosmic question is whether we are really at the point where end users can take elements that exist in the cloud and their own data centers and create processes and applications that run their business themselves. And our response is that that's probably not the case, and it's probably not going to be the case anytime soon. If, in fact, it were the case, it would still be the wrong thing to do in enterprises, because I am not sure many CEOs want their business end users being IT.

Gardner: Now, your product is something that's designed to make crafting and managing business processes easier and more visual. You're trying to elevate this from a code-based or tool-based process to more of a visual, something that an analyst level person could do, but not necessarily a line-of-business person. So, you've already tested the waters here and your conclusion is that IT can't go away.

Model-based environment

Neihaus: Correct. We're a model-based execution environment, and you're exactly right that we try and expose those processes to the business. But, there are what I call "pretty pictures" kinds of approaches to this, and they can exist in the cloud and they can exist in IT. But, for most people, those are customizations of existing applications.

You might go buy a call-center application and allow end users to modify the workflow. But, once you get beyond the pure human workflow, and you begin to integrate the kinds of systems that Sandy was talking about, and I think Ron was talking about, you're beyond the skill, desire, or capability of an end user.

Now, can these things be composed from elements that exist in the cloud? They could be and they probably should be. But, whether the cloud represents something that can enable business users to eliminate IT is a huge stretch for us, based on what we experience in the marketplace.

Gardner: We haven't really explored that dimension where the cloud fits. Does the cloud get between the end user and IT, or is the cloud behind IT and IT gets between the cloud and the corporate user and perhaps even their customers out in the public domain?

Brad Shimmin, recently we saw some inkling about Google Wave. What that's going to represent? I found the demo and the implications very interesting.

We've all been end users at some point and still are in many ways, for what we do day-in and day-out. I think all of us here will attest to the fact that we can be incredibly stupid.

Google seems to think that they can go directly to the end user, at least for some elements of collaboration for bringing different assets together in a common view -- maybe some check-in, check-out benefits, using a spectrum of different communication modalities and synchronicities.

What's your take? Is Alex right that we're not going to get too much out to the end user directly, that IT is going to be part of that? Or, are we perhaps being a little bit too cautious about what end users are capable of?

Shimmin: We've all been end users at some point and still are in many ways, for what we do day-in and day-out. I think all of us here will attest to the fact that we can be incredibly stupid. Yesterday, when I was sitting on Microsoft's Virtual Analyst Summit, I heard them say that what they'd like to accomplish is for users to be able to open up an Excel spreadsheet and create a BI report that would normally take IT two weeks to do.

I thought, "Hey, that's terrific, but, oh dear Lord, you don't want anyone to do that, because they're going to use the wrong datasets, they're going to perhaps have the wrong transitions and transformations for data."

It's not as simple as the picture is being painted. With Goggle Wave, as we've said before, when they are talking about certain types of collaborative applications, that sort of mashability -- as Jim put it earlier -- is something users are capable of and comfortable with. It's within the bounds of something they know how to manage, and they know that what they get out of the application is right.

When I hear about customers being able to mash-up their own BI reports, for example, I think, "How would they know? How on earth would they know that what they've gotten out of it is correct?"

Gardner: And, would the security and regulatory compliance issues be maintained?

Loss of control

Shimmin: Sure, that's the other horn on the bull. The more you move into the cloud, the less control you have over the data. The vendors that I talk to realize that fact, but they still haven't come to a point in which you can control which data resides where and what happens to that data. This is even in the collaboration space, mind you, which is I've said is really getting out there ahead of a lot other ventures,

A lot of companies that say they are pure SaaS are really still using shared data resources on the back-end, which is not a good thing, if you really need to lock down that data.

Gardner: It's not really cloud. Is it?

Shimmin: No.

Gardner: Jim Kobielus, I'm sorry I cut you off earlier, but I wanted to get across the spectrum of our analysts, before we dug down too deeply. But, now is the time to dig deeply to this point that end users, even sophisticated power users in a corporate environment, are probably not going to be in a position of doing SQL queries or even queries that have been visually abstracted for them. We need a sort of intermediary group or capability between the consumers of data and the actual production of data. Isn't that right?

Kobielus: The intermediary group is the governance group. Alex, Brad, Sandy, and the others are talking about how, as you allow the end users or encourage them or require them to mash up the hone applications in their own data, in their own presentation layer, that becomes chaos unless you have strong governance.

As Brad said, when users are given a sandbox of their own, they should know that the whole sandbox, in fact, was built and is being monitored by IT, so that you're taking the right data, doing the right transforms, and applying the right presentation components, the right data model, the right calculation, as defined by your company, its policies, and its rules. You need strong governance to keep this massive cloud sandbox from just becoming absolute chaos.

So, it's the IT group, of course, doing what they do best, or what they prefer to be doing, which is architecture, planning, best practices, templates, governance control, oversight support, and the whole nine yards to make sure that, as you deal in new platforms for process and data, such as the cloud, those platforms are wrapped with strong governance.

Gardner: Tony Baer, perhaps what we are seeing is not the demise of IT, but the transformation and elevation in the role and importance of IT.

The other part is technical. If you're going to provide them the capabilities to mash up things, which is certainly valuable, you want to do this in a protected sandbox

Instead of doing support, maintenance, patches, and keeping the red lights out and the green lights on, they're going to be involved with the governance, provisioning, security, and more innovation in terms of getting closer to the productivity benefit than simply keeping the cycles going and the hard-drive spinning.

Baer: There's no question about that. It reminds me of some of the notion that to make things simple underneath the plumbing is very complex, so make things simple on top. As Jim is saying, you can't provide users the ability to mash-up assets and start creating reports without putting some sort of boundary around it.

This is process-related, which is basically instituting strong governance and having policies that say, "Okay, you can use these types of assets or data under these scenarios, and these roles can access this and share this."

The other part is technical. If you're going to provide them the capabilities to mash up things, which is certainly valuable, you want to do this in a protected sandbox. That's where I see technical innovations that could go to cloud, which would be like enterprise mash-up hubs -- probably a good example -- or like a report center.

I could use those Excel spreadsheets to generate those reports, but they're coming from a protected set of data for which there are very stringent access controls and governance. So, it's a combination of both process and technology.

The same cloud?

Gardner: Ron Schmelzer, I'm a neat person. I like things that follow in nice little neat packages that line up, and are not crooked. What I am starting to see now in this cloud evolution is one part of a cloud being something that end users would use, inside of companies or consumers at home through their mobile devices.

I'm also seeing the cloud providing these back-end infrastructure services, automation and lower cost, and building blocks for IT. And, IT has a value-added role on top of that. But, is it the same cloud? Is it a different cloud, and how would we manage this border between, "I want to use the cloud as an end user" and "I want to use the service from the cloud through the IT department control."

Schmelzer: It sounds like you have a future in interior decoration to put things in neat boxes, but that's why we call it a cloud, right? The reason we call these things cloud is because they're kind of amorphous. They don't have well-defined boundaries.

The whole reason for the metaphor "cloud" is that in network diagrams you want to show something outside the boundaries of the IT organization, but you don't know exactly how it's configured. You just represent it visually as a cloud, right? So, that's the conceptual model we are computing here, where you don't necessarily have all the details of the implementation.

Now, the question is: is the cloud boundary at the firewall or is the cloud boundary necessarily outside of the organization? Not necessarily. There maybe internal processes in IT or the IT organization that are leveraging aspects and elements that you don't have complete control over, in which case they are very cloud-like. They have all the same features and benefits of the cloud.

What we have to be aware is that there are a lot of different things that are wrapped up in the cloud. There's SaaS and application service provider stuff that we've been doing since late '90s. There's utility computing, grid computing, elastic computing, compute on demand, and all this sort of stuff.

The question is what benefits do we want? That's what differentiates cloud.

There's an increasing need to compose and integrate silos within organizations. That has a huge implication on governance activities.

It really is a third-party provider that we're paying for on a transactional model and leveraging infrastructure we have no visibility over, rather than a model that we have ownership of. We have cost visibility, but we have elastic consumption capability. So, we're using more of the implementations of the cloud.

Gardner: Sandy Rogers, you've been tracking governance capabilities, and is it the role of IT to further govern this amorphous boundary between what a cloud, off-the-wire set of services might bring to an organization in addition to governing the IT that goes on inside of their SOA activity. Is IT going to rise up to this or you are going to say, hey, that's outside of our purview and we are not interested.

Rogers: It's certainly within the purview of both IT and business, as partners, to address governance, whether it's internal to an organization or it's leveraging facilities that are external or outside the firewall. IT is still responsible for ensuring that whatever systems are used, how and where the technologies and being used, they accomplish the business goals.

It's off-loaded for support overall. They're going to have to be responsible to ensure that it fits in line with their governance policies in their meeting to set goal. I think the availability and maturity of technologies will evolve, and it will evolve in different spaces to be one-for-one able to be replaced.

The sophistication of the solution interfaces and the management in the administrative capabilities to enable governance, are very nascent in the cloud offerings. That's an opportunity for vendors to approach this. There's an increasing need to compose and integrate silos within organizations. That has a huge implication on governance activities.

Gardner: And, that doesn't even include these outside silos.

Step back and do the basics

Rogers: Yes. It's just being exaggerated with these cloud-based environments. What I've seen in looking at SOA governance is that for those companies that don't have good governance policies, programs, and procedures to start with really are in a situation where they have to step back and do the basics. Every time you end up with some type of distributed, federated environment, you have to look at all of those issues that relate to governance, whether it's compliance, security, management, or anything like that.

SOA, or any distributed environment, exaggerates this. Cloud will exaggerate it even further. Managing contracts and legal arrangements will be a growing emphasis within IT. What's interesting in the cloud space is that we're seeing a lot of packaged services, where one company may be engaging with a service provider, and that service provider is dependent on another service provider for, say, providing some compute infrastructure services.

Gardner: An ecology approach to this.

Rogers: Yes, having the visibility, having access to the right information to perform governance is going to be an area that needs to be worked on. It will have to be worked on sooner, rather than later, to win over those C-level executives who are very nervous about relinquishing control.

Gardner: Another area that I'd like to get into, before we run out of time, is the ability for the vendors, the software providers, to make a decent living. If they're only going to deliver what they do through a cloud model and they have a subscription they are going to charge per user per month, or some similar model, can they, in fact, cover their cost and make a profit?

JP Morgenthal, who has been on our show, has been critical and says that even open source is a threat, because of the same issue. The innovative, quality software won't get developed in the future, if the models don't support it. I'll take that to Alex as a software developer and provider of value. Is there a case here that the subscription model undercuts the viability of your business?

Neihaus: I don't think so, and I'll tell you why. Like any other vendor of any product in any marketplace, we'll sell our services or our products the way customers want to buy them.

The software market is very big. The market we exist in, the business-process management system marketplace, is very big. Companies like ours and others will adapt to what customers ask for

As of yet, at least in our case, we've had no substantive demand for subscription, which is closely associated with the open-source model. It turned out to be fairly expensive over a longer period of time, or per user per month hosted Exchange or Notes mailbox pricing. -- at least for the category in which we exist.

The software market is very big. The market we exist in, the business-process management system marketplace, is very big. Companies like ours and others will adapt to what customers ask for. We can be more nimble than some of the bigger players in this marketplace to responding to that, and that's the key point.

The very large, leviathan players in the space have the most to lose from any kind of change in pricing or distribution business models. So, there's a huge lethargy in the marketplace towards changing buying behavior.

Even if we wanted to promulgate and distribute a new business model, customers are so used to buying the way they have been buying from companies for such a long time that their internal processes from decision-making to contracting are wrapped around those models. It's something we would adapt to, but I think the market is going to change relatively slowly.

Gardner: Brad Shimmin, to Alex's point that the big players, the leviathans, have the most to lose from the wholesale move to cloud, that's in semi-agreement with this concept that moving to a services provisioning subscription model has its risks compared to a license on-premises, per processor type of model. Where do you come down on that?

Vendors will adapt

Shimmin: Well, I stand firmly on the side of broader ecosystems and the power to the people. So, my feeling is that the vendors will adapt to this, just as Alex was saying, but they're doing it slowly. When I look at Microsoft, Cisco, and IBM, for example, I see three very different approaches to that.

With Microsoft, they were pretty quick to roll out their Microsoft online services and firmly undercut the pricing that their partners could give their customers on hosted Exchange, for example. But, they set it up so that those partners could then build value-add on top of it to increase their revenues. As we've been talking about here, when it comes down to just a numbers game, it's hard to make money on just a pure services contract -- unless you have a huge scale to work with.

When Microsoft rolled out Azure -- last October, I think it was -- the plan was to allow their ecosystem, their channel partners, to build applications for vertical markets. These are the things they are good at and the things that Microsoft is not good, and they can make money on those by building into the cloud.

It's these channel partners that are going to benefit the most from these standardized interfaces and the mashability component that's built into these cloud services. It's not the end users who are going to be putting things together. It's the channel partners who are going to be assembling value that they can then deliver to customers.

Gardner: Tony Baer, it seems to me that the open source rollouts of the past 10 years may be harbingers of things to come into cloud.

A lot of customers have said, "Look, just handle the infrastructure for an extra fee, and we'll to continue to pay our perpetual license."

If a large vendor wants things to go slowly, they could perhaps time things. At the same time, they might offer certain elements of their services as a service for free in order to undercut competitors and/or to entice the use of a larger solution, rather than an application or feature set. Do you expect they will see that?

Baer: To a certain extent, where you will see it is in the commodity areas. Microsoft is obviously the poster child there, because they have the most to gain and the most to lose. Actually, it's more that they have the most to lose, not so much to gain. They are really in a defensive position there.

But, when you look at enterprise software or more specialized software, I don't think that's really the case. One of the notes I was jotting down here was that I thought this may actually be very particular to my market, to the software tools market, and that it may march to a different drummer, compared to customer relationship management (CRM) or Exchange.

IBM is struggling with the pricing for how it's going to price its cloud. Hewlett-Packard's (HP's) experience so far, at least from the Mercury side which has offered testing services going back a long ways, is that in many cases, the pricing is not on the subscription model. A lot of customers have said, "Look, just handle the infrastructure for an extra fee, and we'll to continue to pay our perpetual license."

The move to the cloud and subscription pricing are two different things. One does not necessarily follow the other. That's a finding that actually surprised me.

Gardner: Ron Schmelzer, Tony Baer made a point that you could be a victim of cloud, before you could be a beneficiary of it, if you are a provider and a vendor. That's a tough transition to go through.

All transitions are similar

Schmelzer: Maybe, and I think all these transitions are like that. If you look at what happened to the Web. I was on the CRM side of things back in the mid '90s, and we thought that the Web was going to kill client-server CRM applications, and, to a certain extent, it kind of did. It just took a lot longer than we thought. I remember Siebel's dominance and they're saying, "We are not going to move to the Web."

Obviously, Salesforce put the impetus behind it, but even before Salesforce was out there in the late '90s, we were asking, "Why are we using this in-house enterprise application software system with all this great Web stuff happening over there? Why can't we put this stuff online?" The same thing is going here.

We talked about this a couple of podcasts ago, this IT divide between the IT experience at work and the IT experience at home. The home IT experience is just so much richer than what we've got at work. So, it's the same question. Why are we still using these systems in the enterprise and we have all this cloud-based mash-up stuff when we go home?

The writing is on the wall. The smart vendors will learn how to transition themselves in a way that doesn't cannibalize their existing business model. The stupid ones will be pushed to the model anyways, They can't resist it, and they will, of course, suffer.

Gardner: I think this has been a very good and interesting discussion. I'd like to go around the table before we close out, because I haven't heard too much about the death of IT in these permutations of the subject that we've gone through here.

Jim Kobielus, first to you. On a scale of 1 to 10, with 1 being IT dead and 10 being

Much of the actual guts of IT within an organization will migrate to hosted environments, and much of the development will be done by end users and power users.

IT alive, robust, and growing vibrantly, where do you think we're going to see the IT department's role in say three years?

Kobielus: Okay, in three years. I'll be really wishy-washy and give it a 5. It's almost like Schrodinger's cat. You know it's in the box, but you don't know if it's dead or alive yet. It depends on how the quark falls. But, I think that in three years time, IT will be alive, kicking, robust, and migrating toward more of a pure planning, architecture, and best practices function.

Much of the actual guts of IT within an organization will migrate to hosted environments, and much of the development will be done by end users and power users. I think that's writing on the wall.

Gardner: So, the role and impact of IT will be about the same in three years?

Kobielus: Yeah.

Gardner: Tony Baer, how do you come down -- 1 to 10?

Baer: I was really confused about Jim's answer, because I thought he said at one point that IT's role is going to change as we go to hosted services.

Gardner: We may change his mind on the show.

Doing the cool stuff

Kobielus: Actually, 20 years ago I worked as a contractor for a government agency that outsourced a vast majority of their IT to contractors. I remember that the folks who remained as the government's employees running the shop were all procurement, planning, architecture, and all the high-level, cool stuff. They didn't get their fingernails dirty.

Baer: I don't subscribe to the death of IT, because I remember 20 years ago hearing about the death of IT, when Yankee Group did the announcement of that Kodak did a big outsourcing contract, because they decided that, as a company, they were not really in the business of IT. They were in business of photography. A few years later, they realized that the business of photography really did involve IT, and they very quietly backtracked on those contracts.

Gardner: JP Morgan Chase did the same thing about five or six years ago, right?

Baer: Exactly. As Sandy was saying before, there is a lot of complexity, even if you outsource. Outsource means that you need more management. Even if you use the cloud, that requires more governance.

So, I don't see IT's role diminishing. There may be a lower headcount, but that can just as much be attributed to a new technology that provides certain capabilities to end users and also using some external services. But, that's independent of whether there's a role for IT, and I think it pretty much still has a role.

Gardner: If you have 1 to 10, give me a number.

Baer: And 10 being that it does have a role?

Gardner: Vibrant, alive, thriving, and growing like crazy.

Baer: I am going to give it an 8.

Gardner: Excellent. Brad Shimmin?

Shimmin: I'm giving it a 7 for similar reasons, I think that it's going to scale back in size little bit, but it's not going to diminish in value.

IT is not going to go away. I don't think IT is going to be suffering. IT is just a continuously changing thing.

Back to what Sandy was saying, I think it's going to be very much alive, but the value is going to be more of a managerial role working with partners. Also, the role is changing to be more of business analysts, if you will, working with their end users too. Those end users are both customers and developers, in some ways, rather than these guys just running around, rebooting Exchange servers to keep the green lights blinking.

Gardner: So, more architects, fewer admins.

Shimmin: Yup.

Gardner: Ron Schmelzer?

Schmelzer: I'm going to be your lemming here. I think it's 10. IT is not going to go away. I don't think IT is going to be suffering. IT is just a continuously changing thing. Look, IT is only 60 years old. The whole life of the entire IT-as-an-organization department within the enterprise is only 60 years.

So, IT is going to be thriving in three years. It's going to be completely different than anything we may know today or maybe it'll be mostly similar. But, I guarantee that whatever it looks like, it will be still as important as an IT organization.

Now, of course, my information tells me that the world is coming to an end at three years, my Mayan Calendar. That was a good choice on time horizon, because if you had said four years, that would mean the world is not going to exist in four years. So what kind of trick question is that?

Gardner: Well, that's why I bring it down. Sandy Rogers -- 1 to 10?

Some IT is in deep trouble

Rogers: Probably in the 7 to 8 range. I agree with everything that's been said here. I think it's up to the individual enterprises. In some enterprises, IT is in deep trouble if they do not embrace new technologies and new opportunities and become an adviser to the business. So it comes down to the transition of IT in understanding all the tools and capabilities that they have at their disposal to get accomplished what they need to.

Some enterprises will be in rough shape. The biggest changeover is the vendor community. They are in the midst of changing over from being technology purveyors to solution and service purveyors. That's where the big shift is going to happen in three years.

Gardner: Alex Neihaus, how about your choice here? 1 to 10?

Neihaus: Our self-interest is in a thriving a segment of IT, because that's who we serve. So, I rate it as a 10 for all of the reasons that the much-more-distinguished-than-I panel has articulated. I wish to say one thing, though. The role of IT is always changing and impacted by the technologies around it, but I don't think that that could be used as an argument that it's going to diminish its importance or its capabilities really inside organizations.

Gardner: Well, I'll go last and I'll of course cheat, because I'm going to break it into two questions. I think their importance will be as high or higher, so 8 to 10, but their budget, the percent of spend that they're able to derive from the total revenues of the organization, will be going down. The pressure will be on, and it will be going down.

So, from a price and monetary budgeting perspective, the role of IT will probably be down around 4. That's my take.

Thanks very much for all of your input. I also want to thank the sponsors for the BriefingsDirect Analyst Insights podcast series, Active Endpoints and TIBCO Software.

And I also want to thank our guests this week. Jim Kobielus, senior analyst at Forrester Research. Thanks Jim.

Kobielus: Always a pleasure.

Gardner: Tony Baer, senior analyst at Ovum.

Baer: Great discussion as usual.

Gardner: Brad Shimmin, principal analyst at Current Analysis.

Shimmin: Thank you, Dana. It was great today.

Gardner: Ron Schmelzer? What's your name again? Brawn? No, Ron Schmelzer, senior analyst at ZapThink.

Schmelzer: Glad to be here, and I think my mainframe is taking about three years to turn off. I'll let you know in three years.

Gardner: Thank you also Sandy Rogers, now an independent IT analyst and consultant.

Rogers: It was great to participate and be here.

Gardner: And also a special thanks to Alex Neihaus, vice president of marketing at Active Endpoints.

Neihaus: It was a thrill to join you guys today.

Gardner: Thanks for listening to BriefingsDirect. Come back next time.

Download the transcript. Read the summary blog post. Charter Sponsor: Active Endpoints. Also sponsored by TIBCO Software.

Special offer: Download a free, supported 30-day trial of Active Endpoint's ActiveVOS at www.activevos.com/insight.

Edited transcript of BriefingsDirect Analyst Insights Edition podcast, Vol. 42 on on the health of corporate IT and whether reports of its demise are premature. Copyright Interarbor Solutions, LLC, 2005-2009. All rights reserved.