You might think summer would be a good time to give acquisitions a break - to let things settle a bit. But the pace of key acquisitions continues and many deserve comment. Datacap, as we all know, is not new to IBM having many - probably 20 - joint customers. This helps shore up IBM's already packed ECM portfolio - which depended for capture on Kofax - and other partners like Datacap. The original capture assets, acquired with FileNet, were adequate but lacked forms processing and a distributed capture strategy. This acquisition plugs those gaps but more importantly provides a needed platform to overlay IBM's suite of analytics products to improve business processes with metadata extraction, document classification, and ultimately to bring text analytics to transactional business processes. Advanced capture will also help IBM in advancing areas of dynamic case management and medical records.
Open source software (OSS) and business intelligence (BI) are two related market segments where Forrester sees continually increasing interest and adoption levels. BI specifically continues to be one of the top priorities on everyone's mind. The main reason? Enterprises that do not squeeze the last ounce of information out of their data stores and applications, and do not focus on getting strategic, tactical, and operational insight into their customers, products, and operations, risk falling behind competition. And when it comes to open source, 2009 could best be described as "the year IT professionals realized that open source runs their business." The reason is simple: Over the past few years, we've seen that developers adopt open source products tactically without the explicit approval of their managers. This has shown up in numerous surveys where the actual adoption of open source ranks higher than what IT managers report. Well no longer: Forrester's Enterprise And SMB Software Survey, North America And Europe, Q4 2009 shows that management has caught on to the fact that developers increasingly use open source to run key parts of their IT infrastructure. And management has grown increasingly comfortable with it. In fact, throughout 2009, most client inquiries Forrester received regarding open source were focused on how to move from tactical adoption to strategic exploitation.
Yet, when you put the 2 and 2 together (OSS and BI), you mostly get a mixed market, where one unfortunately has to compare apples to oranges. Why? Before plunging into a tool evaluation and selection process, ask yourself the following questions, and make sure you are doing a like-to-like comparison:
VMWare has got it down: Sell a virtualization solution with anchor applications (and seats) that no service provider can live without, starting with email. This is the call we made when VMWare bought open source email and collaboration provider Zimbra from Yahoo! last February. And now they've delivered with the upgraded Zimbra Collaboration Suite Appliance 6.0 targeted at service providers and other virtual cloud hosters. What it means:
What it means #1. VMWare is solidly in the market to provision service providers with email. Service providers that want to resell Google or Microsoft's email have the benefit of low capital costs and rapid deployment. But service providers that don't want to resell another vendors' cloud services need a solution that runs at low cost on cheap servers with easy peasy provisioning. That's what the Zimbra collaboration appliance promises. Will it deliver? Love to hear from service providers on this one.
What it means #2. VMWare drives another nail into the coffin of on-premises business email. At $5/mailbox/month for cloud email, if you take away client software and mailbox administration costs, our analysis shows that it costs twice as much to host a mailbox yourself than to host it in the cloud. This offering gives service providers around the world the opportunity to compete at that price. So who would use on-premises email? Only someone with stringent requirements, massive scale, or a recent upgrade. Even the federal government is moving to cloud-based email as GSA has announced.
It’s no secret traditional news organizations are struggling to stay relevant today in an age where an always-connected generation has little use for newspaper subscriptions and nightly news programs. The Associated Press (AP), the world's oldest and largest news cooperative, is one such organization who has felt the threats which this paradigm shift carries and thus the need to intensify its innovation efforts. However, like many organizations today, its in-house IT Ops and business processes weren’t versatile enough for the kind of innovation needed.
"The business had identified a lot of new opportunities we just weren't able to pursue because our traditional syndication services couldn't support them," said Alan Wintroub, director of development, enterprise application services at the AP, "but the bottom line is that we can't afford not to try this."
To make AP easily accessible for emerging Internet services, social networks, and mobile applications, the nearly 164-year-old news syndicate needed to provide new means of integration that let these customers serve themselves and do more with the content — mash it up with other content, repackage it, reformat it, slice it up, and deliver it in ways AP never could think of — or certainly never originally intended.
Recently I published a business service management (BSM) case study on AMERICAN SYSTEMS. If you're interested in BSM, I highly recommend reading through this report. Although there are many known business alignment success stories, AMERICAN SYSTEMS takes business alignment a step further by aligning IT elements in a way that truly supports its business goals. AMERICAN SYSTEMS sought to improve the delivery and quality of its services to the business, something they were able to accomplish by introducing ITIL and COBIT standards and deploying integrated data center management software. In all, they were able to gain situational awareness, preempt and respond to issues more efficiently, and better protect information assets.
I've outlined a few key highlights from this report below:
First off, AMERICAN SYSTEMS is a government IT innovator that provides engineering, technical, and managed services to government customers. In order to meet the needs of their clients' constant demand for new and better services, they decided to shift from a reactive to a proactive way of managing and operating.
When they set out to make changes they outlined several goals:
Last week, as part of the debate on the 600B border security bill, Senator Charles E. Schumer from New York reportedly called the Indian offshore IT firms in general and Infosys in particular “chop shops” — a reference to the locations where criminals dismantle stolen cars for spare parts. As always, the Indian press has immediately reacted. But let’s not take the comment out of context; US Senator Charles Schumer calls Infosys 'chop shop' - India Business - Business - The Times of India. Senator Schumer is showing that in an election year, he is “standing up” for American jobs.
But that said, as we head into the midterm elections with 9.5% unemployment and very little job growth, there will be more comments like this unfortunately, and the Indian firms and NASSCOM need to be prepared with their own PR counterattack and story. Offshore customers would also be advised to take the same advice and have a clear PR plan ready to go at a moment’s notice in case they get raked over the coals as part of the rhetoric.
Anyone familiar with social technologies will remember the launch of Google Wave in the fall of 2009. It was a new kind of communication platform released into a beta test with 100,000 invitations sent out. Google’s strategy in limiting the rollout was designed not to overload the architecture (and perhaps to create a sense of scarcity, which it did very well). Google also wanted to develop the platform experientially based on user feedback. However, on Wednesday Google announced it was pulling the plug on Wave. Eric Schmidt tried to put a positive spin on it, describing Wave as a failed experiment that was also a learning experience. And there are certainly some lessons that can be applied to the rollout of enterprise social platforms.
Numbers Matter – Develop A Strategy For Rapid Adoption
I spoke today at SHARE’s biannual conference, giving a talk on emerging data center architectures, x86 servers, and internal clouds. SHARE is an organization which describes itself as “representing over 2,000 of IBM's top enterprise computing customers.” In other words, definitely a mainframe geekfest, as described by one attendee. I saw hundreds of people around my age (think waaay over 30), and was able to swap stories of my long-ago IBM mainframe programming experience (that’s what we called “Software Engineering” back when it was FORTRAN, COBOL, PL/1 and BAL. I was astounded to see that IMS was still a going thing, with sessions on the agenda, and in a show of hands, at least a third of the audience reported still running IMS.
Oh well, dinosaurs may survive in some odd corners of the world, and IMS workloads, while not exciting, are a necessary and familiar facet of legacy applications that have decades of stability and embedded culture behind them…
But wait! Look again at the IMS session right next door to my keynote. It was about connecting zLinux and IMS. Other sessions included more zLinux, WebSphere and other seemingly new-age topics. Again, my audience confirmed the sea-change in the mainframe world. Far more compelling than any claims by IBM reps was the audience reaction to a question about zLinux – more than half of them indicated that they currently run zLinux, a response which was much higher than I anticipated. Further discussions after the session with several zLinux users left me with some strong impressions:
Yesterday (August 5), Google announced that it was ceasing attempts to make Google Wave a viable standalone product. Considering the fanfare that the product received in the run-up to its general release (announced at Google I/O in May), it was no surprise the story burned across the blogosphere and the press. In following some of the Twitter traffic, what I found interesting was some of the low-level chuckling I saw from some competing vendors in the collaboration software space. Why? Well, before I get into that, let me make a couple of stipulations:
Google has a history of less-than-stellar product launches. In tossing Google Wave on the scrap heap (and parceling out some of its components as open-source software), the brainchild of Lars and Jens Rasmussen joins a growing number of failed products. Some of this can be attributed to mistakes that Google has made time and again in marketing and product design (my colleague Tom Grant pointed out some of this with Google Buzz). But you also have to factor in that because Google has such a high profile, every time a product under performs it draws a lot of attention, making each failure seem large. But this does not seem to slow the search engine giant's innovation engine, which brings me to my second point.
Yesterday we launched our Empowered microsite. On this site you can find lots of resources about our new book, including the blog, where to buy the book in bulk, how Forrester can help your empowered strategies, and a new HERO Project Effort-Value Evaluation tool.
First, some background. When Josh & I first began investigating HEROes (highly empowered and resourceful operatives, basically folks like you who make a difference using new technology), we knew that we needed a way to assess the effort that your projects required. And then we realized that you were tackling new technology solutions because you saw the value they could provide. So we needed to help you assess the value and the effort.
Thus was born the HERO Project Effort-Value Evaluation tool that we introduce in chapter 2. This tool includes five value questions and five effort questions that categorize your project into one of four classes and provides you some high-level guidance on what to watch out for. The online version of the tool also creates a nice email format with the results of your evaluation, which you can easily share with colleagues to get them involved in the project.
I think your best use of the tool is to sanity check your thinking on the project, get insight into the questions you need to answer before getting started, and get others on board with your project goals. If you're in business, it's a way to get IT involved. If you're in IT, it's a way to help your business colleagues scope a project and get your help with it.
We can also help you assess the project and provide additional insight into where you should dig deeper.