Every client (especially every government client) who says I’ll never use cloud services with highly secure data needs to hear this story. In no more sensitive a place than law enforcement is just such a value proposition playing out.
Police departments in 18 states in the US, and soon Canada, are dramatically increasing the efficiency of commercial use of highways through a disruptive SaaS solution that costs a fraction of the incumbent service and mixes well with their permitting and inspection databases.
If you drive toll roads or bridges you know the value of Drivewyze. In rush hour, you can wait 10-25 minutes to pay your toll with cash or you can sign up for an electronic toll system that lets you breeze past. Drivewyze does the same for commercial trucks and fleets but not at toll booths but weigh stations, that take much longer to get through. And in the trucking business every minute lost at a weigh station can cost thousands of dollars in lost delivery time. For law enforcement the value is even higher as any time lost inspecting a safe truck is time not spent stopping an unsafe one.
The system works by helping known-good drivers and trucks register with the weigh station wirelessly as they approach it on the highway, get an all-clear, then drive right by. Trucks send their credentials to the weigh stations using any mobile device they happen to have – iPhone, Android, Blackberry. Anything with a cellular connection will do the trick. At the weigh station, they receive the information about the driver over whatever equipment they have – aging PCs and laptops are most common. The system checks each driver and truck against long-standing databases of safety records, expired licenses, past weigh station checks and other information that would indicate an unsafe driving circumstance.
Ok, so NASA failed an audit. Don’t we all? I think it is important to understand the government’s cloud computing adoption timeline before passing judgment on NASA for failing to meet its cloud computing requirements. And, as someone who has read NASA’s risk management program (and the 600 pages of supporting documentation), I can say that this wasn’t a failure of risk management policy or procedure effectiveness. Clearly, this was a failure of third-party risk management’s monitoring and review of cloud services.
The Cloud Is Nebulous
Back in 2009, NASA pioneered cloud technology with a shipping container-based public cloud technology project named Nebula -- after the stellar cloud formation. (I love nerd humor, don’t you?)
Photo Source: NASA
During 2009, NASA, to determine if current cloud provider service offerings had matured enough to support the Nebula environment, did a study. The study proved that commercial cloud services had, in fact, become cheaper and more reliable than Nebula. NASA, as a result of the study, moved more than 140 applications to the public sector cloud environment.
In October of 2010, Congress had committee hearings on cybersecurity and the risk associated with cloud adoption. But remember, NASA had already moved its noncritical data (like www.nasa.gov or the daily video feeds from the international space station, that are edited together and packaged as content for the NASA website) to the public cloud in 2009. Before anyone ever considered the rules for such an adoption of these services.
Adobe Systems is a pioneer and fast mover in the public cloud and in so doing is showing that there is nothing for infrastructure & operations professionals (IT Ops) to fear about this move. Instead, as they put it, the cloud gives their systems administrators (sysadmins) super powers ala RoboCop.
This insight was provided by Fergus Hammond, a senior manager in Adobe Cloud Services, in an analyst webinar conducted by Amazon Web Services (AWS) last month. Hammond (no relation to Forrester VP and principal analyst Jeffrey Hammond) said that Adobe was live on AWS in October 2011, just 8 months after its formal internal decision to use the public cloud platform for its Adobe Creative Cloud. Prior to this there were pockets of AWS experience across various product teams but no coordinated, formal effort as large or strategic as this.
Sourcing professionals already understand the importance of monitoring financial performance to assess risk in their key suppliers’ ability to deliver commitments. Sometimes sourcing professionals can also find valuable negotiation leverage in the financial results of their key suppliers, as is the case with Oracle’s Q4 2013 numbers . In my opinion, the revealing aspects that you can use to increase your bargaining power over the next couple of quarters, include:
I recently had the opportunity to spend some quality time with NetSuite in San Jose at its customer forum — SuiteWorld. The event gave me a long, overdue deep-dive into their current strategy and the chance to speak with many of their customers one-on-one.
The big announcement from the event was the availability of its manufacturing solution. The evening before the event started I had a good conversation with our Sourcing Analyst Liz Herbert — who spends a lot of her life focused on the SaaS providers — and asked her why NetSuite was not growing more quickly. Her response was that its lack of a manufacturing solution is partly to blame. So when it was announced by CEO Zach Nelson the next morning, it certainly helped to fill me with confidence about its future.
Back in October 2011, Microsoft named the initiative to introduce Windows Azure cloud platform into the Chinese market “Moon Cake,” which represents harmony and happiness in Chinese culture. On May 23, 2013, Microsoft made the announcement in Shanghai that Windows Azure will be available in Chinese market starting on June 6 — almost half a year after its agreement with Shanghai government and 21ViaNet to operate Windows Azure together last November. Chinese customers will finally be able to “taste” this foreign moon cake.
I believe that a new chapter of cloud is going to be written by a new ecosystem in China market, and Microsoft will be the leader of this disruption. My reasons:
The cloud market in China will be more disrupted. Due to the regulatory limitations on data center and related telecom value-added services operations for foreign players, the cloud market for both infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS) has been an easy battlefield for local players, such as Alibaba/HiChina. Microsoft’s innovative way working with both government and local service partners to break through this “great wall” shows all of the major global giants, such as Amazon.com, the great opportunity from this approach to the Chinese market. We can anticipate that they will also enter the Chinese market in the coming six to 18 months.
I've noticed a bit of a disturbing pattern of late in my cloud discussions with clients. They have been talking about hybrid cloud in the future tense. If you are planning for hybrid down the road, I have a wake up call for you. Too late, you are already hybrid.
If your company has even a single SaaS application in use today I can almost gurantee you it's connected to something inside your data center giving you hybrid cloud. So hybrid isn't a future state after you have a private cloud in place and IT Ops chooses to connect that private cloud to a public cloud. Look at it through the lens of a business process or application service which is composed of different components, some cloud-based, some on-premise. From an Infrastructure & Operations perspective, hybrid cloud means a cloud service connected to any other corporate resource (a back office app, your web site, your intranet, another SaaS app you have under contract and yes, even your private cloud). Any of these types of connections presents the same integration impact - whether you established the connection or not. If you are like the typical enterprise, that answered our Forrsights Q4 2012 Software Survey, then you have more than six SaaS applications in place today (that you know about) so cloud integration is likely well in place today. And about one third of the developers who responded to our Forrsights Q1 2013 Developer Survey said they have already deployed applications to the public cloud. Twenty-five percent also admitted to putting application integrations in place.
I’ve noticed a growing trend among Asia Pacific organizations over the past 6-12 months: complete IT resistance to SaaS has steadily given way to more pragmatic discussions, even if IT has come to the table grudgingly. Over the next two years I expect this trend to accelerate. In fact, I believe that many SaaS solutions, particularly those that cross business and functional boundaries, will be rapidly subsumed within the broader IT portfolio, even if they were originally sourced outside IT.
Many SaaS vendors report already seeing more IT involvement in procurement, requirements definition, RFP creation, and negotiations. The clear procurement guidelines published by the IT department of the Australian Government Information Management Office (AGIMO) is one high profile example. Don’t get me wrong, in most instances business decision-makers will still lead, particularly in identifying the required business processes and determining how best to consume SaaS-based services. But IT decision-makers are getting more involved, particularly around integration.
Some areas to consider as you look to work more closely with business decision-makers to evaluate and negotiate SaaS and other public cloud deals:
"Logan: That's the way things are. The way things have always been."
In Redwood City this week, the answer I heard from Oracle was an emphatic yes. At Oracle's Industry Analyst World, the company stressed its cloud bonafides against Salesforce, IBM, and SAP with its new Customer Experience (CX) Suite. The CX Suite is a horizontal offering, assembled primarily from acquisitions, newly rechristened as Oracle Marketing (Eloqua), Oracle Commerce (ATG, Endeca), Oracle Sales (Oracle CRM On Demand), Oracle Service (RightNow), Oracle Social (Collective Intellect, Vitrue, Involver), and Oracle Content (Fatwire).
The Software as a Service (SaaS) suite promises to deliver a lower total cost of ownership, easier integration, and faster time to value for a business looking to streamline its enterprise software providers. While Oracle's approach is to lead with SaaS, it also promotes an Enhance, Augment, Migrate strategy, enabling existing customers to extend an on-premises deployment --- think Siebel Loyalty --- with one or more CX products, say Eloqua's email delivery capabilities.
You Can Outrun Your Past
So what does it mean for Eloqua? Marketers using or considering Eloqua should recognize that Oracle:
Leading-edge executives at organizations drive growth, innovate, and disrupt industries through emerging technologies: social, mobile, cloud, analytics, sensors, GIS and others. 85% of executives in a recent survey shared that “the need to drive innovation and growth” would have a moderate or high impact on IT services spending. But, today’s technology buyers face a fragmented, fast-moving landscape of niche technology and services providers in newer spaces (social, mobile, cloud) as well as new offerings from their largest global partners.
Often the leading- and bleeding-edge disruption comes from business stakeholders, rather than IT or sourcing executives; sourcing executives struggle to keep up with the fast pace of change that business demands. Our research shows that this fragmented, divisional, silo approach to buying (often under the radar screen) can create risk and go against enterprise IT strategy decisions.
To help their organizations navigate through these emerging options, we have identified three key principles of IT sourcing strategy:
Change the rules for working with vendors and partners. To thrive in the world of digital disruption and to enable sourcing of emerging technologies and services that drive digital disruption, sourcing strategists must create new rules for working with technology partners. They must increase the emphasis on innovation and differentiation and treat partners who excel in these dimensions differently from other tiered suppliers.