Michael Capellas gets things done. His appointment to lead the Cisco-EMC JV – Acadia – is good news for the market and for users. I am particularly interested in, as it aligns with my research focus, how the company will invest in the R&D to create the Services platform required to automate and manage transformational solutions. Both EMC and Cisco bring some interesting piece-parts to the table (e.g. Voyence, Smarts, Tidal Software, etc). However, the challenge to create a truly innovate service management platform is greater than their current inventory of software and their internal expertise.
Acadia’s ‘service’ model is presently Build-Operate-Transfer. My question is, can (or will) the organization work to address the growing requirement for a Build-Operate-Manage model where the user is more reliant on partners to manage the growing complexity of their solutions? The JV wasn’t formed with any intent towards becoming an outsourcer, but bringing a JV to market based on deep expertise and an ability to ensure architectural predominance for Acadia’s investors must make some form of ongoing ‘managed services‘ fairly appealing. I look forward to what Acadia will bring to the market.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Mobile Scenario: Taking Mobility to the Next Level
The definition of "mobile" in the post-app era will involve new interactions such as bots and conversations, new devices such as wearables...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.