AI as a Layer: The Four-Layer Pattern That Finally Makes AI Useful
You've probably noticed (what we're calling) the "logo-swap test" lately: all the AI ads in market sound...
Multi-tenancy has long been the model of the outsourcing industry. Multi-tenancy is usually defined as using a single instance of an application to service multiple client...
Multi-tenancy has long been the model of the outsourcing industry. Multi-tenancy is usually defined as using a single instance of an application to service multiple client organizations (or tenants) over a single, shared infrastructure.
The value of this approach increased when service providers discovered that comprehensive IT service management platforms (such as BMC Remedy™) could be re-architected to serve multiple clients if customer data could be kept segmented and secure. The same service—help desk, desktop management, IT asset management or other IT provisioning—could be pushed out to multiple clients.
Clients enjoyed all of the benefits typically associated with outsourcing: cost-savings, efficiency and the ability to focus resources on core business competencies rather than on IT. Outsourcers benefited from the ability to easily scale up to serve multiple clients without needing to purchase and support multiple instances of the same software. The model served outsourcers well for many years.
But 3 trends are making Multi-tenancy 1.0 obsolete:
Their business models are based on the ability to apply one software infrastructure across many clients. But those infrastructures weren’t originally envisioned to support a client-centric environment in which:
Service providers have made multimillion-dollar investments in their software infrastructures. Few relish the prospect of abandoning these investments, but many are beginning to realize that Multi-tenancy 1.0, as described here, no longer allows them to keep up with changing client needs and marketplace conditions. Customization at the client level, which requires programming at the application level, will continue to be too expensive, time-consuming and risky. Changes or additions will continue to amplify risks. Customizations will be lost during upgrades and need to be redone, which again means more money, time, and risk. These problems will limit the service providers’ ability to scale.
As back-office tools, IT service management platforms will continue to provide robust, stable, process-driven, and standards-based platforms for addressing incident and problem resolution, change management, service-level agreements, and configuration management databases.
But in front-end roles where there is a growing need to provide tailored and client-centric customer innovations—such as request management via self-service portals, service catalogs, approvals, fulfillment, visibility, interactivity, collaboration, and co-created services—most IT service management platforms are inadequate. In today’s outsourcing environment, forcing a back-office system to accommodate both back- and front-end roles is an increasingly untenable proposition.
Moving from Multi-tenancy 1.0 to 2.0 imposes 8 new demands on service providers:
You've probably noticed (what we're calling) the "logo-swap test" lately: all the AI ads in market sound...
Automation Should Be the Easy Win — So Why Isn’t It? You'd think automation would be the low-hanging...
For years, "shadow IT" has been treated like a four-letter word. Ask most IT leaders, and you'll hear...