CoIT & The New C-Suite Executive Exchange - CCE2012
CoIT & The New C-Suite Executive Exchange - CCE2012
Executive exchange from Connected Enterprise 2012
New C-Suite Chief Customer Officer Chief Executive Officer Chief Information Officer
Executive exchange from Connected Enterprise 2012
New C-Suite Chief Customer Officer Chief Executive Officer Chief Information Officer
Executive exchange panel at Connected Enterprise 2012
Data to Decisions Chief Information Officer Chief Marketing Officer Chief Supply Chain Officer
Informatica Sets The Stage For A New Chapter In Its History
Informatica held its annual industry analyst day February 26th to 27th, 2013 at the Rosewood Sandhill in Menlo Park. The event showcased Informatica’s go-forward strategy and road map for growth over the next three years. Key highlights include:
The Bottom Line: Informatica’s Investment In Growth Amidst A World Of Disruption Is Good News For Customers
Prospects and customers should find comfort in the investments Informatica is making to expand its product line portfolio to support a more complex world of social business, mobile enterprise, cloud computing, and big data. Informatica’s use cases of analytics, operational integration, cloud integration, master data management, and data governance, provide customers with a neutral, one-stop shop to manage their information life cycle requirements. How Informatica innovates with its customers, partners, and alliances will determine the go forward growth path. Customers will measure success by how easily the line of business executives and IT can bring order to chaos.
Your POV
Are you an Informatica customer? Do you plan to invest more or less with them in 2013? What do you think about their strategy? Add your comments to the blog or send us a comment at R (at) SoftwareInsider (dot) org or R (at) ConstellationRG (dot) com
Please let us know if you need help with your integration or MDM strategy. Sign up for a Constellation Academy Workshop or let us assist with:
Related Research
Reprints
Reprints can be purchased through Constellation Research, Inc. To request official reprints in PDF format, please contact Sales .
Disclosure
Although we work closely with many mega software vendors, we want you to trust us. For the full disclosure policy, stay tuned for the full client list on the Constellation Research website.
* Not responsible for any factual errors or omissions. However, happy to correct any errors upon email receipt.
Copyright © 2001 – 2013 R Wang and Insider Associates, LLC All rights reserved.
Contact the Sales team to purchase this report on a a la carte basis or join the Constellation Customer Experience!
Data to Decisions Innovation & Product-led Growth Leadership Chief Information Officer Chief Experience Officer
Big Data is a catchy phrase. Unfortunately, it is often misused and misunderstood. Often, Hadoop and Big Data are used interchangeably; as if the Apache Hadoop family of projects are the only solutions for Big Data, or that that only use for these projects is from Big Data. Neither is true.
As an EDW/BI practitioner, I watched the Hadoop, or really, the Map/Reduce framework, be embraced and forced into being by software developers who were frustrated by Structured Query Language (SQL) and the need to create Entity-Relationship Diagrams (ERD) as data models or schæmas. They were equally unhappy with the various work-arounds to access Relational Database Management Systems from within their programs, such as Object Relational Models (ORMs) and Data Access Objects (DAOs). At first, I felt that these developers were simply lazy.
However, as I worked more with these so-called NoSQL technologies, it helped to clarify the dissatisfaction that I felt during the years I was leading EDW and BI projects. Thirty years ago, I worked in Aerospace System Engineering, developing methods and algorithms for risk assessment using Bayesian statistics. But, by 1996, I became involved in my first EDW project. Since then, the actual structure and functions associated with the data - defined by the data, became less important than fitting the data into an artificial structure imposed by business process models.
Don't get me wrong. Relational algebra, relational calculus and the DBMS technologies that came out of this mathematics, are all very useful. And, in the right hands, SQL is a very powerful language. ERDs provide a wonderful way to map data to business processes and to both transactional and analytic systems.
But… There is so much more that can be done with the data coming from traditional human-to-machine (H2M) interactions, but increasingly from human-to-human (H2H), machine-to-machine (M2M) and machine-to-human (M2H) exchanges. The interweaving of the flows of data from such disparate sources is what drives my research today.
These, and over 70 other use cases that I'm cataloguing, come from the innovation surrounding hype of Big Data, and the Data Science movement. In a recent Quark, I've classified this innovation into 11 areas. A compete mindmap is linked from the initial mindmap shown below, and in the report.
The Quark covers the trends coming from these innovations, and develops the four keys required to bring valuable decision making processes into your organization from these innovations. It's entitled "Big Data: It's Not the Size, It's How You Use It". For such a simple report, it took over 8 months to develop. Mostly this delay was caused by the fast-paced evolution of the innovations. The executive summary from the Quark is linked from the title.
I hope that you find that information, as well as the mindmap, useful in incorporating inference, prediction, insight and performance with intuition for making better decisions.
Data to Decisions Chief Information OfficerYesterday saw the launch of the much awaited Samsung Galaxy S4 (and a worthy update it seems, if hardly earth shattering — much like occurred with the iPhone 5). There has also been much talk about Android weaknesses, hardware or software market specialization as well as Google’s rising share price (and Apple’s currently falling one). But what almost nobody discusses is: what will be the smartdevice replacement rate? This metric is beginning to matter more and more to a whole raft of audiences — from device manufacturers to mobile carriers to enterprises and to consumers.
When Apple launched the original iPhone it was correctly hailed as something special — because it was. The second iPhone was a significant improvement, both in quality (already high) but also in both form and function. But, by the time of the iPhone 4S and then the iPhone 5 the improvements had become demonstrably incremental rather than revolutionary.
The same is largely true of Android. Before the arrival of Jelly Bean in mid 2012 Android was pretty rough (but attractively open) and Android devices did not really match the iPhone. Then Samsung delivered the SIII and Note2 (and now the S4) while HTC has moved forward with its all aluminum One and Google with the LG-made Nexus. All these devices are, with Jelly Bean, now a match for the iPhone.
But here lies the rub. Once you have an iPhone 4S or 5 or HTC One or SIII or Note 2 or the latest Nexus — what is the incentive to replace these?
Of course there will always be a technoscenti who must have the latest device. They will not disappear but they are also not numbered in multiple millions (remembering that Apple sold 17M+ iPhones and Samsung sold 15M+ in Q4 of 2012 alone). One key to the future is, therefore, understanding the device replacement rate and then how it will affect different communities in different ways.
If you have invested in a shiny new smartphone (and this applies perhaps even more so to phablets and tablets) with processing power beyond what there are the apps to consume (for example the S4 will come with an octa-core processor and 2GB of RAM — as much as you would find on a full laptop of 2-3 years ago, or even today), why would you want to replace this next year, the year after or even the year after that? This is going to become the burning question and it is one with global implications.
The so-called ‘rich West’ may have had differing replacement propensities to the rest of the world. Furthermore, the case for multiple smartphones per person is not strong — and the arrival of dual SIM smartphones will only force additional device consolidation. The rest of the world may still be catching up on acquiring smartphones, but it will arrive at parity pretty soon. Yet what is clearly evident is that the cost of a smartphone is a much greater investment, as a proportion of disposable income, in the rest of the world which means that it will likely possess a much longer in-use life.
This means that, for mobile phone manufacturers, the alleged promise of a long term future selling into vacant smart device space will not last long when market saturation combined with the inevitable ‘loss of sexiness’ factor(also known as incremental improvements) occurs in the ‘rich West’. The result will achieve pretty much the same: expect smartphone replacement rates to match that of (say) laptops — which already have a life of 2-4 years.
[If you do not believe this, make a list of all your mobile devices (including laptops, mp3 players, phones, phablets, tablets, etc.) and indicate when each was bought and when you might plan to replace each. I did it for myself and, even though both an iPhone and an iPad were stolen in 2012 (and replaced by Android devices), the average age of my devices is already well over 2.5 years. As for replacement, the only device likely to see replacement in 2013 is the Windows tablet.]
Now consider the impact and implications if the smart device replacement rate is as slow as I argue it is going to be.
Consumers, whether in the rich or not-so rich worlds will not care much. They will replace devices when it suits them and value for money will count most of all. Here Google would be onto a great opportunity with its most recent Nexus, except these are so hard to find to buy. One oft-ignored aspect to remember here is that many consumers are also employees: with the rise and rise of Bring Your Own Device (BYOD) the existence of the previously parallel Enterprise and Consumer markets for smart devices is likely to disappear as the latter absorbs the former.
For device manufacturers, including Samsung and Apple, the years from 2015-2020 are going to be horrible — with high consumer expectations of ever greater cleverness being disappointed as each new evolution much looks pretty much the same. Apple may yet crack China as a cult product, and in so doing may make itself effectively a China oriented organization (after all China could absorb in number of smart devices what the rest of the world combined does). For vendors all this could be different if some new way (or category) of relevant (to the buyer) device emerges, as did the iPhone and iPad — but even this is likely only to put off painful days.
For mobile carriers and providers all this is an opportunity and a threat. The opportunity is to withdraw from the costly device-subsidy model which involves massive up front purchases from device manufacturers: eliminating this would free up significant resources, not least cash. The threat is that the 2 or 3 year contract model delivers ‘loyalty’. If the focus moves away from devices the mobile carriers will need to focus on the customer (thus far largely unheard of, outside France’s Iliad and one or two other refreshing organizations): service will be all important.
Finally there is the enterprise dimension. BYOD has the great advantage that enterprises can rely on employees to make the purchases, which frees up CAPEX and other resources. With vendors like Airwatch, Boxtone, Fiberlink, SOTI and Symantec, to name only five, offering increasingly sophisticated device and content management, having your employees buy their own devices is less and less the obstacle it was. In addition, especially if most BYOD devices stabilize around Jelly Bean (for Android), on iOS6 (for iPhones and iPads) on WindowsPhone 8 and Blackberry’s BB10, then enterprise app development will become (relatively) simpler (and many of the criticisms of a multi-furcatedAndroid, in particular, will diminish — though Apple is not as guiltless as it would like to make out) through greater OS consistency.
Indeed, as one thinks more and more about what the replacement metric means it is hard not to conclude that the long term winners are consumers and enterprises.
New C-Suite Chief Information OfficerBrand storytelling can be hard work. Not only are there all the internal hurdles to overcome, sign-offs and legal checks and so on – there is also the challenge of subject matter. What do you do if you have a complex product or solution that you are trying to explain? Which channels do you choose – and how do you incorporate social media into the mix.
I was recently speaking with a financial services industry CEO who lamented that they have the most boring product in the world. He couldn’t see how it would resonate with a social media-savvy audience.
But social media is not broadcast – especially in B2B (business-to-business) marketing. You’re not trying to reach and engage millions of people – you are (or should be) focused on the buyer’s journey and helping to ease your customer’s decision making process. That means selecting the most appropriate channel – and delivering content that provides very specific value to your customer at their point of need. And brand storytelling can form a very powerful component of your content strategy and lead nurturing program.
Still unsure of how this might work for you and your brand?
Enterprise software vendor, Teradata, have been experimenting with brand storytelling for some time and have taken a novel approach that you may want to steal (I mean “learn from”). Tapping into pop culture’s interest in forensic analysis (a la CSI), they have created a series of videos that take a new approach to case studies and product/solution brochures. The “Business Scenario Investigations” or “BSI” team dramatize business problems and then showcase how technology can be used to “solve” the problem.
Each of their videos can be found on the BSI: Teradata Facebook page as well as the YouTube channel. They cleverly provide a powerpoint version of the scenario via Slideshare and share the storyboarding process from problem definition to casting through to resolution. And while the case of the tainted lasagna may not be to your taste, it’s likely to be very appealing to those CIOs and CMOs wanting to understand how data can transform their businesses. And that’s tasty. Very tasty indeed.
Marketing Transformation Chief Marketing OfficerI've just completed reviewing the 7 RFP responses for my session at Enterprise Connect 2013 on cloud-based communications services. The RFP is a 60 page document describing the communications and collaboration requirements for a 2,000 person enterprise with three locations.
End users may obtain a copy of the RFP at no charge at www.constellationr.com/cloud.
The seven responding vendors - 8x8, Avaya, NEC, ShoreTel Sky, Siemens Enterprise Communications, Thinking Phone Networks, and Verizon - have each gone to great lengths to provide the information required by the RFP which included over 300 individual functional components along with the WAN links and pricing for the entire service over a period of 5 years.
What has made this doubly interesting is that four of the respondents, 8x8, ShoreTel Sky, Siemens, and Thinking Phones, provided reference customers that I interviewed. After doing thorough interviews, I've written case studies, which were not vendor sponsored. I learned a lot about motivations for moving to the cloud, some of which involved total cost of ownership, but others centering around other value propositions of the cloud including geo-redundancy, disaster recovery, focusing on the most important IT/telecom business issues, and so forth.
The responses will be presented on March 19, 2013 at Enterprise Connect 2013. I will also make them available in a workshop/seminar format for organizations who want to know more about cloud communications, ts costs and drivers, and for those who would like to use these RFP results to quickly get to short list of one or two providers to pursue for a cloud communications solution.
The RFP workshop contains the following items:
A sample graphic illustrating vendor responses about encryption as well as the vendor support demarcation point fis shown below. There are many other graphics and figures comparing these solutions in detail. More information is available at www.constellationr.com/cloud.
Any vendor company making PBX or call center software should have a development initiative to add WEbRTC as a channel into the PBX or contact center software alongside SIP and other communications and collaboration protocols. This can be done without too much development cost, and it will put you on the leading edge with respect to the technology curve.
Future of Work New C-Suite Next-Generation Customer Experience Tech Optimization Chief Information Officer
This is a loose phrasing of one of Netwon’s laws of physics, but it applies as well to the WebRTC standards bodies. What we are seeing with the present version of the standard is a basic capability, but we know there must be changes in the future to allow for additional use cases and evolution of capabilities. Hence, the standards and the bodies governing them will be in motion for some time to come. If not, proprietary extensions will arise, as they have done with SIP, and it will take another 10 years to sort things out. Just look at how truly compatible the SIP world is – it isn’t, even though every vendor swears that it is standards compliant.
Thank heavens for the Acme Packets of the world who are Switzerland of SIP protocols.
WebRTC will multiply this interoperability issue for any inter-domain communications significantly because of the lack of specification in the control channel, even if the audio and video codecs are the same. Microsoft articulated some of the key SDP issues the current WebRTC standard has at a new post titled, “New CU-RTC-WebHTML5Labs Prototype from MS Open Tech Demonstrates Roaming between Cellular and Wi-Fi Connections”. This post includes a reference to the functional level of the API’s available, which includes a discussion that centers on how core A/V functionality and interoperability need to work, particularly with mobile devices. It also references another post by Robin Raymond about why the SDP issue will be an anchor to WebRTC instead of providing it the wings to soar that so many some are saying the current vague standard provides.
I have the opportunity to co-chair the WebRTC conference-within-a-conference that will be held in conjunction with Enterprise Connect 2013. This is a top notch mini-conference with four goals in mind: