In this six part series, we explore how Operational Intelligence Centre (OIC) implementations can be complex and often fail to address the challenges they initially set out to solve. Here are our 6 top OIC challenges:
- Complex Business Processes
- Vendor Protectionism & the Platform Approach
- Complex IT Landscapes
- Messaging <> Collaboration
- Genuine self-service is rarely delivered
- Business Intelligence sits in chairs, not spreadsheets
2. Vendor Protectionism & the Platform Approach
“A platform enables. It helps others build value… Platforms help users create products, businesses, communities and networks of their own.” – Jeff Jarvis, What Would Google Do?
Many, if not all IT solutions are extensible provided sufficient funding is available – indeed, it’s a vendor strategy to provide the basics at a low cost then develop the revenue stream through services and add-ons. This can make an initially suitable solution unaffordable in the long term. A truly sustainable platform does not incur significant additional costs apart from perhaps those related to significant increases in usage, e.g., storage.
The platform approach is easy extensibility – so easy in fact, that end-users can extend it themselves. This approach would promote open connectivity standards, APIs and flexibility. Unfortunately, history shows that this is counterintuitive for most enterprise software vendors who insist on using proprietary formats. This limits the scope and ease of implementation of an operational intelligence system.
Hence it’s common to find multiple operational intelligence systems in place as vendors seek to protect revenue stream; each system tends to require its own analysis platform, so most organisations have multiple analysis solutions depending on the nature of their operations, user communities and history. Vendor lock-in is expensive, risky and obstructs agility. Vendor agnostic solutions do exist but they are expensive and difficult to implement, usually involving the design and development of data dictionaries or translation tools. Ultimately, as implementation and ongoing maintenance are key revenue streams it’s in the vendor’s interests for these solutions to be difficult and costly implement.
Missed a part of this series? Get the previous posts here:
Interested in finding out more about Sabisu?