The Webster Dictionary describes fatigue (also sometimes called exhaustion, tiredness, languor, lassitude or listlessness) as "a subjective feeling of tiredness which is distinct from weakness, and has a gradual onset."
Technology management transformations - and in specific, I&O transformations - suffer from fatigue in many organizations. Some of it is due to the fact that the term "transformation" is more jargon than anything real. Transformation means many things to many people and therfore we never really exit a transformation as we move from project to project, continually transforming.
If I asked you, does I&O transformation mean reshaping your architecture? Streamlining your service management and integration (SIAM) processes? Adjusting your automation strategy? Improving your application performance management to become more proactive? Reducing operational cost? Shifting your infrastructure and applications into the cloud? You would say "yes" to all of them, with all of them being described as some kind of transformation. Eliminating fatigue means following a transformation plan. The plan needs to be supported with details to shift the conversation from costs of the technology “feeds and speeds” to how the technology will enable the business to win, serve, and retain their customers.
With the holidays—and a whole lot of 2015 strategic planning activities—behind us, you’re probably have a few gifts you’d like to return and hopefully, a few gift cards you’d like to make use of. If you were really good last year,Santa left you the budget needed to develop or enhance that mobile insurance app or site you’ve wanted.
But how do you spend that budget so that the app or site that results doesn’t disappoint like those sea monkeys or x-ray glasses that you also once wanted?
It’s not hard to uncover this kind of disappointment in the mobile insurance marketplace: Mobile services that are little more than insurer bill boards, require too much data entry from users, and lack features that users have come to expect from banks, retailers, and airlines. To play catch- up with competitors and quell internal political concerns, many insurance eBusiness and technology management teams were put on the spot, rolling out mobile functionality without considering if it solved a problem for customers. While this approach addressed the business urgency, these hastily -built mobile insurance apps often fell short.
Since Tibco acquired Jaspersoft on April 28th, 2014, I keep being asked the question: “Will this deal change the BI and analytics landscape?” (If you missed the announcement, here’s the press release.)
The short answer is: it could. The longer answer goes something like this: Jaspersoft and Tibco Spotfire complement each other nicely; Jaspersoft brings ETL and embedded BI to the table, whereas Spotfire has superior data analysis, discovery, and visualization capabilities. Jaspersoft’s open source business model provides Tibco with a different path to market, and Jaspersoft can benefit from Tibco’s corporate relationships and sales infrastructure. And with its utility-based cloud service, Jaspersoft also adds another option to Spotfire’s SaaS BI offering.
But that’s only the narrow view: once you take into consideration Tibco’s history (the hint’s in the name - “The Information Bus Company”) and the more recent string of acquisitions, a much larger potential story emerges. Starting with Spotfire in 2007, Tibco has assembled a powerful set of capabilities, including (but not limited to) analytics, data management, event processing, and related technologies such as customer loyalty management and mapping. If Tibco manages to leverage all of its assets in a way that provides enterprises with a flexible and agile integrated platform that helps them turn their data into actionable information, it will be a powerful new force that has the potential of changing enterprise BI platforms market.
To get there, Tibco has a number of challenges to address. On a tactical basis, it’s all about making the Jaspersoft acquisition work:
Retaining the talent
Making it easy for clients and prospects to engage with both companies
I recently had a meeting with executives from Tech Mahindra, an Indian-based IT services company, which was refreshing for the both the candor with which they discussed the overall mechanics of a support and integration model with significant components located half a world away, as well as their insights on the realities and limitations of automation, one of the hottest topics in IT operations today.
On the subject of the mechanics and process behind their global integration process, the eye opener for me was the depth of internal process behind the engagements. The common (possibly only common in my mind since I have had less exposure to these companies than some of my peers) mindset of “develop the specs, send them off and receive code back” is no longer even remotely possible. To perform a successful complex integration project takes a reliable set of processes that can link the efforts of the approximately 20 – 40% of the staff on-site with the client with the supporting teams back in India. Plus a massive investment in project management, development frameworks, and collaboration tools, a hallmark of all of the successful Indian service providers.
From a the client I&O group perspective, the relationship between the outsourcer and internal groups becomes much more than an arms-length process, but rather a tightly integrated team in which the main visible differentiator is who pays their salary rather than any strict team, task or function boundary. For the integrator, this is a strong positive, since it makes it difficult for the client to disengage, and gives the teams early knowledge of changes and new project opportunities. From the client side there are drawbacks and benefits – disengagement is difficult, but knowledge transfer is tightly integrated and efficient.
For decades, firms have deployed applications and BI on independent databases and warehouses, supporting custom data models, scalability, and performance while speeding delivery. It’s become a nightmare to try to integrate the proliferation of data across these sources in order to deliver the unified view of business data required to support new business applications, analytics, and real-time insights. The explosion of new sources, driven by the triple-threat trends of mobile, social, and the cloud, amplified by partner data, market feeds, and machine-generated data, further aggravates the problem. Poorly integrated business data often leads to poor business decisions, reduces customer satisfaction and competitive advantage, and slows product innovation — ultimately limiting revenue.
Forrester’s latest research reveals how leading firms are coping with this explosion using data virtualization, leading us to release a major new version of our reference architecture, Information Fabric 3.0. Since Forrester invented the category of data virtualization eight years ago with the first version of information fabric, these solutions have continued to evolve. In this update, we reflect new business requirements and new technology options including big data, cloud, mobile, distributed in-memory caching, and dynamic services. Use information fabric 3.0 to inform and guide your data virtualization and integration strategy, especially where you require real-time data sharing, complex business transactions, more self-service access to data, integration of all types of data, and increased support for analytics and predictive analytics.
Information fabric 3.0 reflects significant innovation in data virtualization solutions, including:
“Figuring out how to think about the problem.” That’s what Albert Einstein said when asked what single event was most helpful in developing the Theory of Relativity. Application integration is a problem. A big problem. Not to mention data, B2B, and other domains of integration. As an industry analyst and solution architect, what I’m most interested in first is how to think about the problem.
Pop Quiz: The Goal of Integration
Which of the following statements best articulates the goal of integration strategy?
The goal of integration is to keep data in sync across two or more siloed applications.
The goal of integration is to improve business outcomes by achieving consistent, coherent, effective business operations.
The correct answer is B. Was that too easy? Apparently not, because most of the integration strategies I see are framed as if the answer were A. Most, but not all — and it’s the ones framed around B that I’m most interested in. Here’s the difference:
A-style integration centers on technology. It begins with data and business logic fractured across application silos, and then asks, “How can integration technologies make it easier to live with this siloed mess?”
B-style integration centers on business design. It begins with a businessperson’s view of well-oiled business operations: streamlined processes, consistent transactions, unified tools for each user role, purpose-built views of data, and the like. It designs these first — that is, it centers on business design — and then asks, “How can integration technologies give us coherent business operations despite our application silos?”
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.
If your organization is like nearly every other one I've talked to in the past 20+ years, you have a spaghetti chart of integration connections between all the siloed applications that run your business. Your customer is fractured across five applications. Your fulfillment process is broken across eight applications. Just try to pull together the data necessary to tell how profitable one of your products is. Or, as you implement mobile, external APIs, custom B2B connections, and more, how will you provide consistent, coherent access to your transactions and data?
Making sense of all the mess has been an important priority for years. The question is "how?" Forrester's latest research finds that it's time for a new kind of integration strategy. We call it "Digital Business Design":
A business-centered approach to solution architecture, implementation, and integration that brings business and technology design together by placing design priority on user roles, business transactions, processes, canonical information, events, and other business aspects that embody a complete definition of a business.
Two months ago, we announced our upcoming Forrester Forrsights Software Survey, Q4 2010. Now the data is back from more than 2,400 respondents in North America and Europe and provides us with deep and sometimes surprising insights into the software market dynamics of today and the next 24 months.
We’d like to give you a sneak preview of interesting results around some of the most important trends in the software market: cloud computing integrated information technology, business intelligence, mobile strategy, and overall software budgets and buying preferences.
Companies Start To Invest More Into Innovation In 2011
After the recent recession, companies are starting to invest more in 2011, with 12% and 22% of companies planning to increase their software budgets by more than 10% or between 5% and 10%, respectively. At the same time, companies will invest a significant part of the additional budget into new solutions. While 50% of the total software budgets are still going into software operations and maintenance (Figure 1), this number has significantly dropped from 55% in 2010; spending on new software licenses will accordingly increase from 23% to 26% and custom-development budgets from 23% to 24% in 2011.
Cloud Computing Is Getting Serious
In this year’s survey, we have taken a much deeper look into companies’ strategies and plans around cloud computing besides simple adoption numbers. We have tested to what extent cloud computing makes its way from complementary services into business critical processes, replacing core applications and moving sensitive data into public clouds.
Fujitsu? Who? I recently attended Fujitsu’s global analyst conference in Boston, which gave me an opportunity to check in with the best kept secret in the North American market. Even Fujitsu execs admit that many people in this largest of IT markets think that Fujitsu has something to do with film, and few of us have ever seen a Fujitsu system installed in the US unless it was a POS system.
So what is the management of this global $50 Billion information and communications technology company, with a competitive portfolio of client, server and storage products and a global service and integration capability, going to do about its lack of presence in the world’s largest IT market? In a word, invest. Fujitsu’s management, judging from their history and what they have disclosed of their plans, intends to invest in the US over the next three to four years to consolidate their estimated $3 Billion in N. American business into a more manageable (simpler) set of operating companies, and to double down on hiring and selling into the N. American market. The fact that they have given themselves multiple years to do so is very indicative of what I have always thought of as Fujitsu’s greatest strength and one of their major weaknesses – they operate on Japanese time, so to speak. For an American company to undertake to build a presence over multiple years with seeming disregard for quarterly earnings would be almost unheard of, so Fujitsu’s management gets major kudos for that. On the other hand, years of observing them from a distance also leads me to believe that their approach to solving problems inherently lacks the sense of urgency of some of their competitors.