Your workforce is mobile and loving it. They love it because they can get things done anywhere, anytime, on any device. You can almost see happy tails wagging as they check their email. But they haver no idea how disruptive mobile devices are to the IT status quo. Sure, mobile email is a small dog to train. But what about mobile business apps? That dog is bigger than a rhinoceros.
To keep your workforce loving your business applications as they go mobile, you will have to redesign the fundamental architecture for delivering apps. The architecture of Client-Server (and Browser-Server) is inadequate. You will need to build from an architecture of devices and services. The mobile app Internet is that architecture: local apps (including HTML5 browsers) on smart mobile devices and cloud-hosted interactions and data.
My friend and colleague John McCarthy has written a seminal report for Forrester clients sizing the market for the mobile app Internet. In this report, he lays out the growth model for mobile apps (six drivers of growth), segments the market for mobile apps+services (mobile apps, application development, mobile management, and process reinvention), and sizes the total mobile apps+services market ($54.6B by 2015).
This is an important report. Everybody should read it. Here's my take on what it means for content and collaboration professionals:
Starting with CES in early January and through the Mobile World Congress last week in Barcelona, the mobile industry has been in a feeding frenzy of announcement activity. At CES, it was centered on Android-powered tablets. During the Mobile World Congress, it was about the big Microsoft/Nokia deal and vendors scrambling to differentiate their Android handsets.
But behind all these announcements, there is a broader shift going on to what Forrester calls the mobile app Internet and the accompanying broader wave of app development and management. We have just published a report that explores the different vectors of innovation and sizes the mobile app Internet from an app sales and services opportunity.
The report looks at the three factors beyond hardware that will drive the market:
Even at $2.43/app, the app market will emerge as a $38B market by 2015 as more tablets and smart phones are sold and the number of paid for apps per device increases due to improvements in the app store experience.
A perfect storm of innovation is unleashed by the merger of mobile, cloud, and smart computing. I see innovation coming from the combination of apps and smart devices like appliances and cars, improved user experience around the apps by better leveraging the context from the sensors in the devices, and enabling the apps to take advantage of new capabilities like near field communications (NFC) for things such as mobile payments.
For the most part, enterprises understand that virtualization and automation are key components of a private cloud, but at what point does a virtualized environment become a private cloud? What can a private cloud offer that a virtualized environment can’t? How do you sell this idea internally? And how do you deliver a true private cloud in 2011?
In London, this March, I am facilitating a meeting of the Forrester Leadership Board Infrastructure & Operations Council, where we will tackle these very questions. If you are considering building a private cloud, there are changes you will need to make in your organization to get it right and our I&O council meeting will give you the opportunity to discuss this with other I&O leaders facing the same challenge.
As I’ve been researching my upcoming report on smart city governance, the topic of integrated customer call centers keeps cropping up. What is 3-1-1, and what does it mean for city governance?
In the US, the telephone number 3-1-1 was reserved by the FCC for non-emergency calls in 2003, and cities and counties across the country have since implemented comprehensive call centers to facilitate the delivery of information and services, as well as encourage feedback from citizens. Access has since extended beyond just the phone to include access through government websites, mobile phones, and even social media tools such as Twitter or applications such as SeeClickFix or Hey Gov.
As a means of background, 3-1-1 services are generally implemented at the local level – primarily at the city or county level – with examples of calls including requests for:
With Cisco's shuttering of Cisco Mail, multitenant cloud email is now (as my colleague Chris Voce called it) a battle royale between Microsoft, Google, and IBM, where the winner will have products, scale, sales channels, and big ecosystems of support.
I am not surprised that Cisco bailed on cloud email. All the signs were there:
The company overpaid for PostPath in the midst of a buying spree. PostPath (which made some folks a lot of money when it sold for $215M) was just one of 17 acquisitions Cisco made in 2007 and 2008. Clearly Cisco was feeling confident that it could buy its way into new markets. (And it did with WebEx.)
Cisco Mail was always to be released "any day now." It's fine to preannounce a product so that buyers know it's coming. But Cisco Mail never quite got shipped. The one reference customer never returned my phone calls.
Cisco's collaboration platform doesn't require email. Messaging is one of the four big boxes of collaboration stuff. (The others are conferencing, workspaces, and social technology.) Messaging in particular can be carved out and offered separately. Cisco doesn't need email. It has WebEx and video conferencing. (The jury's still out on presence, chat, video hosting, and social technology.)
Microsoft announced during last week's RSA conference that it would not be shipping Windows CardSpace 2.0. A lot of design imperatives weighed on that one deliverable: security, privacy, usability, bridging the enterprise and consumer identity worlds – and being the standard-bearer of the "identity metasystem" and the "laws of identity" to boot. Something had to give. What are the implications for security and risk professionals?
The CardSpace model had nice phishing resistance properties that cloud-based identity selectors will find hard to replicate, alas. But without wide adoption on the open Web, that wasn't going to make a dent anyway. We'll have to look for other native-app solutions over time for that.
Infrastructure & operations executives have shown a tremendous interest in looking for opportunities to take advantage of the cloud to provision email and collaboration services to their employees – in fact in a recent Forrester survey, nearly half of IT execs report that they either are interested in or plan on making a move to the cloud for email. Why? It can be more cost effective, increase your flexibility, and help control the historical business and technical challenges of deploying these tools yourself.
To date, we’ve talked about four core players in the market : Cisco, Google, IBM, and Microsoft. According to a recent blog post, Cisco has chosen to no longer invest in Cisco Mail. Cisco Mail was formerly known as WebEx Mail – and before that, the email platform was the property of PostPath, which Cisco acquired in 2008 with the intention of providing a more complete collaboration stack alongside its successful WebEx services and voice. I've gathered feedback and worked with my colleagues Ted Schadler, TJ Keitt, and Art Schoeller to synthesize and discuss what this means to Infrastructure & Operations pros and coordinating with their Content & Collaboration colleagues.
So what happened and what does it mean for I&O professionals? Here’s our take:
Another year and Citrix’s acquisition strategy of interesting companies continues as they have announced the purchase of EMS-Cortex. This acquisition has caught my eye because EMS-Cortex provides a web-based “cloud control panel” that can be used by service providers and end users to manage the provisioning and delegation administration of hosted business applications in a cloud environment such as XenApp, Microsoft Exchange, BlackBerry Enterprise Server, and a number of other critical business applications. In theory this means that customers and vendors will be able to “spin up” core business services quickly in a multi tenant environment.
It is an interesting acquisition, as vendors are starting to address the fact that for “cloudonomics” to be achieved by their customers it is important that they ease the route to cloud adoption. While this acquisition is potentially a good move for Citrix I think it will be interesting for I&O professionals to see how they plan to integrate this ease of deployment with existing business service management processes, especially if the EMS-Cortex solution is going to be used in a live production environment.
It’s been a few years since I was a disciple and evangelized for HP ProCurve’s Adaptive EDGE Architecture(AEA). Plain and simple, before the 3Com acquisition, it was HP ProCurve’s networking vision: the architecture philosophy created by John McHugh(once HP ProCurve’s VP/GM, currently the CMO of Brocade), Brice Clark (HP ProCurve Director of Strategy), and Paul Congdon (CTO of HP Networking) during a late-night brainstorming session. The trio conceived that network intelligence was going to move from the traditional enterprise core to the edge and be controlled by centralized policies. Policies based on company strategy and values would come from a policy manager and would be connected by high speed and resilient interconnect much like a carrier backbone (see Figure 1). As soon as users connected to the network, the edge would control them and deliver a customized set of advanced applications and services based on user identity, device, operating system, business needs, location, time, and business policies. This architecture would allow Infrastructure and Operation professionals to create an automated and dynamic platform to address the agility needed by businesses to remain relevant and competitive.
As the HP white paper introducing the EDGE said, “Ultimately, the ProCurve EDGE Architecture will enable highly available meshed networks, a grid of functionally uniform switching devices, to scale out to virtually unlimited dimensions and performance thanks to the distributed decision making of control to the edge.” Sadly, after John McHugh’s departure, HP buried the strategy in lieu of their converged infrastracture slogan: Change.
This week at ISSCC, Intel made its first detailed public disclosures about its upcoming “Poulson” next-generation Itanium CPU. While not in any sense complete, the details they did disclose paint a picture of a competent product that will continue to keep the heat on in the high-end UNIX systems market. Highlights include:
Process — Poulson will be produced in a 32 nm process, skipping the intermediate 45 nm step that many observers expected to see as a step down from the current 65 nm Itanium process. This is a plus for Itanium consumers, since it allows for denser circuits and cheaper chips. With an industry record 3.1 billion transistors, Poulson needs all the help it can get keeping size and power down. The new process also promises major improvements in power efficiency.
Cores and cache — Poulson will have 8 cores and 54 MB of on-chip cache, a huge amount, even for a cache-sensitive architecture like Itanium. Poulson will have a 12-issue pipeline instead of the current 6-issue pipeline, promising to extract more performance from existing code without any recompilation.
Compatibility — Poulson is socket- and pin-compatible with the current Itanium 9300 CPU, which will mean that HP can move more quickly into production shipments when it's available.