Innovative organizations rely on content to make informed decisions about their customers, products, and go-to-market plans. Accurate information needs to get to the right prospect, partner or client at the right time. Large companies often have multiple content management systems, particularly in industries that grow via acquisitions. Busy information workers need to make decisions, and this can get complicated if multiple systems from multiple vendors are in place.
Standards have the potential to help organizations stay agile and responsive to change. Good standards help companies streamline routine requirements and avoid re-inventing the wheel. Bad standards get ignored, fall out of date and become barriers to innovation.
CMIS (Content Management Interoperability Services) has been a much-discussed standard in the ECM world, even before its formal ratification in 2010. In our 2013 ECM survey, just 13% of content management decision-makers put CMIS front and center as part of their strategy. What I wanted to understand:
Who is using CMIS in the real world?
How are architects using it to deliver valuable content to their busy front line workers?
How are software vendors using it to respond to their customer demands to bring content into a bigger information ecosystem?
Microsoft retires support for various older products in 2014 and 2015. This means there will be no more free updates or security patches. While it’s a common occurrence to see support for older products retired by software vendors, it’s annoying if either the old stuff is still running perfectly well or if the upgrade option is financially onerous, will significantly disrupt the business or offers little in the way of real added benefit.
So in April we’ll be finally bidding farewell to support for the likes of Windows XP, Office 2003, Exchange Server 2003, and in July 2015 we’ll say adieu to support for Windows Server 2003. In addition, some more recent products will be transitioning to extended support in July 2014 - namely SQL Server 2008 and SQL Server 2008 R2 – which puts them next on the path to software heaven.
On April 8, 2014, Windows XP will reach the end of its support lifecycle and Microsoft will no longer provide security or online updates.
As a part of the Microsoft Support Lifecycle Policy, Office 2003 products receive five years of Mainstream Support and five years of Extended Support. April 8, 2014 marks the end of this 10-year support period. Running Office 2003 after the end-of-support date may expose your company to security risks and technology limitations.
Exchange Server 2003
While Exchange Server 2003 was a leader in the messaging space, after 10 years of technology progression it will reach End of Support effective April 8, 2014.
My colleague Dan Bieler laid out the overall impressions on his take of the MWC. I fully agree with his view, noticing the number of cars being displayed as attractors to make up for the lost appeal of devices.
My questions were more focused on the impact of announcements and innovation in the enterprise sector. Here is what I took in that respect from Barcelona:
Enterprise providers are preoccupied with mobile integration beyond MDM. Complexity of enterprise content integration into different mobile architectures dominated the agenda of many providers. In this context, everyone in the services arena talks about being a leader for the “end to end” value proposition. The overstretched term “end to end” means different things to different people. Vendors talk about technology stacks, service providers also talk about global reach. In this context, the exclusive alliance model for local best-of-breed providers by GEMA offers an interesting realization of the “think global, act local” concept.
Some 80,000 visitors ventured to Barcelona to attend the annual congregation for the mobile-minded, the Mobile World Congress (MWC). Long gone are the days when one single theme dominated the show. My main impression of MWC was that compared with last year, there was surprisingly little true news. I see evolution not revolution, which is somewhat odd as the overall business environment is clearly changing faster than ever.
Of course, everybody again claimed that they are active in the obligatory fields of cloud, analytics, and customer experience. However, if anything, I feel this convergence of marketing messages creates too many platitudes and undermines the practical use case scenarios that define the mobile mind shift. I went to MWC with several questionsin mind, and my main takeaways of MWC are that:
IBM is making a big push into the SaaS space – boasting 100+ SaaS offerings and $1 billion plus in targeted investments. The good news for buyers is that the strategy is broad, flexible, and open. But, the downside is that the current landscape is fragmented and inconsistent across its different offerings; buyers do not today have a simple “cloud store” where they can go and download all of these different solutions with instant provisioning and pre-built integration. So, what should buyers expect?
The central theme of Mobile World Congress 2014 for me was clearly Connected Living. I’ve been attending Mobile World Congress for quite some time — 2006 was my first, the year that it moved to Barcelona from Cannes. And, this year felt different. No longer did the event feel dominated by handset manufacturers and equipment providers. Mobile World Congress is no longer a telecom event; it is clearly a mobile event. Mobility has penetrated every industry and every aspect of life, and that diversity is now clearly felt at the show. The large presence of car manufacturers and the buzz around Facebook indicate a definitive changing of the guard. That shift is ongoing. The proliferation of connected devices, the explosion of over-the-top services and the rise of the data economy will continue to shape the industry. But for me, this year I felt excitement around our new connected lives.
The government of Singapore has released its 2014 budget, which includes S$500 million (US$400 million) to help drive economic changes at small and medium-size businesses (SMBs). This spending will focus on:
It was recently revealed that the personal data of 20 million South Koreans (40% of the country’s population) was stolen by a contract worker at the Korea Credit Bureau, toppling consumer trust in Korean credit card companies. The theft was carried out by an insider over a period of time and begs the question: How could such an incident go unnoticed? We have found that breaches such as this are usually due to:
Poor system controls for privileged users. Privileged users often have more access than they really need to do their job. By definition, these users need broad access rights, but “broad” shouldn’t imply “unlimited.”
I've just published a Quick Take report that explains why the Nevada District Court’s recent decision on some of the issues in the four-year-old Oracle versus Rimini Street case has significant implications for sourcing professionals — and, indeed, the entire technology services industry — beyond its impact on the growing third-party support (3SP) market.
January 28th was the anniversary of the Space Shuttle Challenger disaster. The Rogers Commission detailed the official account of the disaster, laying bare all of the failures that lead to the loss of a shuttle and its crew. Officially known as The Report of the Presidential Commission on the Space Shuttle Challenger Accident - The Tragedy of Mission 51, the report is five volumes long and covers every possible angle starting with how NASA chose its vendor, to the psychological traps that plagued the decision making that lead to that fateful morning. There are many lessons to be learned in those five volumes and now, I am going to share the ones that made a great impact on my approach to risk management. The first is the lesson of overconfidence.
In the late 1970’s, NASA was assessing the likelihood and risk associated with the catastrophic loss of their new, reusable, orbiter. NASA commissioned a study where research showed that based on NASA’s prior launches there was the chance for a catastrophic failure approximately once every 24 launches. NASA, who was planning on using several shuttles with payloads to help pay for the program, decided that the number was too conservative. They then asked the United States Air Force (USAF) to re-perform the study. The USAF concluded that the likelihood was once every 52 launches.
In the end, NASA believed that because of the lessons they learned since the moon missions and the advances in technology, the true likelihood of an event was 1 in 100,000 launches. Think about that; it would be over 4100 years before there would be a catastrophic event. In the end, Challenger flew 10 missions before it’s catastrophic event and Colombia flew 28 missions before its catastrophic event, during reentry, after the loss of heat tiles during take off. During the life of a program that lasted 30 years, they lost two of five shuttles.