While service catalogs are not new, they are becoming increasingly critical to enterprises seeking to optimize IT efficiencies, service delivery and business outcomes. They are also a way of supporting both enterprise and IT services, as well as optimizing IT for cost and value with critical metrics and insights. In this blog, we'll look at how and why service catalogs are becoming ever more important both to IT organizations and to the businesses and organizations they serve.
What's Cooking in General with Service Catalog Deployments?
Potentially, service catalogs can span everything from supporting internal IT professional needs to end-user needs for IT support, to end-user access to internally delivered software and applications, to support for third-party cloud services across the board, to actual support for enterprise (non-IT) services as managed through an integrated service desk.
Of course the game is changing, with added pressures to support cloud, mobile and enterprise (non-IT) services. But data and dialogs from last year show clear trends that reflect pushing the bar forward in all these areas from past years — with a striking diversity of options. Indeed, enhanced automation for self-service was and remains at the very top of the list for IT service management priorities going forward.
Interestingly enough, internal IT-to-IT provisioning (new servers, deployment requests, etc.) and support for IT professional services (as in project management capabilities) remain among the highest priorities for enterprise service catalogs. But close behind, are:
■ Support for cloud and non-cloud delivered applications
■ End-user access to production services/ applications
■ End-user device (PC, laptop and mobile) provisioning
■ End-user support (help and incident management)
Perhaps not surprisingly, true "appstore" type access for end-user self-service provisioning was far behind these priorities in mid-year 2015. But current EMA dialogs show a growing interest in providing a more complete and self-sufficient storefront approach.
A Few Critical Service Catalog Dimensions
The dimensions of how this is done can range drastically in scope, but ideally enterprise service catalogs will provide metrics for cost and usage, selective service level (service quality) guarantees as appropriate, strong support for secure and appropriate access based on end-user or IT professional roles, and integrated levels of automation to make service provisioning more dynamic, accessible and efficient. Oh, and yes, in the more advanced IT environments, service catalog integrations can handshake as well with service modeling and configuration management databases (CMDBs) to enable yet more advanced levels of automation This can be especially helpful when catalog services are tied to development and DevOps initiatives.
And finally, service catalog access should span not only desktop and laptop access, but increasingly mobile access as appropriate. For instance, nearly two-thirds of our respondents in last year's research were seeking to provide mobile access to corporate application services, and that percentage is steadily climbing higher, as mobile continues to redefine IT and consumer priorities.
Growing areas of interest for service catalog inclusions: cloud and enterprise services
Even last year support for cloud services in service catalogs was striking — at nearly 90%. And cloud priorities in type reflect a growing and rich diversity. These include:
■ Internal software-as-a-service (SaaS) applications
■ Internal infrastructure-as-a-service (IaaS) services
■ Software-as-a-service from public cloud
■ Infrastructure as a service from public cloud
■ Internal platform-as-a-service (PaaS) offerings
■ Platform-as-a-service from public cloud
The above list is in ranked order based on mid-year 2015, and subsequent dialog and research in 2016 would indicate a fair amount of consistency, but with a modestly growing preference for public cloud.
Just as striking as cloud in its impact on IT is the growth of including enterprise service support through integrated service desk and IT service management options. Indeed, a separate commentary on the coming together of business process automation (BPA) and IT process automation (ITPA) — (it isn't really quite there yet) — would probably warrant at least a blog, and maybe a book. But this coming together is reflective of the striking number of IT organizations that are making the leap. Indeed, even a year ago, only 11% had no plans to consolidate IT and non-IT customer service.
In terms of service catalog specifics, the following enterprise groups were shown to depend on service catalogs to support their services:
■ Vendor and contract management
■ Facilities management
■ Enterprise operations
■ Human Resources
■ External customer facing catalog options
■ Corporate finance
What Makes for Success When It Comes to Service Catalog Adoption?
As many of my readers know by now, in most of my research I like to contrast those who view themselves as ‘extremely successful' with those who were only marginally so (the two extremes), which almost always produces meaningful patterns of difference. In this case, the following patterns arose:
Those ITSM teams who viewed themselves as extremely successful were:
■ 2X more likely to have a service catalog
■ 2X more likely to offer users access to corporate applications through mobile
■ Dramatically more likely to support cloud-related services in their catalogs. In fact they were 5X more likely to support SaaS from public cloud and 6X more likely to support PaaS from public cloud.
■ Considerably more likely to support enterprise services, including:
- 2X more likely to support human resources
- 3X more likely to support facilities management
- 2X more likely to support legal
- More than 4X more likely to support purchasing
- 5X more likely to support marketing
- Nearly 3X more likely to support enterprise operations
Given this rather heady show of data, it becomes harder and harder to argue against the impression that we're not only living in the midst of the "digital age" in which "digital transformation" is key, but that service catalogs are increasingly becoming a critical cornerstone in making digital transformation yet more of a reality. Current EMA research, underway now, will explore the role of service catalogs in optimizing IT for cost and value. I'll be sharing these highlights with you in another blog later in Q3.
While remote work policies have been gaining steam for the better part of the past decade across the enterprise space — driven in large part by more agile and scalable, cloud-delivered business solutions — recent events have pushed adoption into overdrive ...
Time-critical, unplanned work caused by IT disruptions continues to plague enterprises around the world, leading to lost revenue, significant employee morale problems and missed opportunities to innovate, according to the State of Unplanned Work Report 2020, conducted by Dimensional Research for PagerDuty ...
In today's iterative world, development teams care a lot more about how apps are running. There's a demand for fixing actionable items. Developers want to know exactly what's broken, what to fix right now, and what can wait. They want to know, "Do we build or fix?" This trade-off between building new features versus fixing bugs is one of the key factors behind the adoption of Application Stability management tools ...
With the rise of mobile apps and iterative development releases, Application Stability has answered the widespread need to monitor applications in a new way, shifting the focus from servers and networks to the customer experience. The emergence of Application Stability has caused some consternation for diehard APM fans. However, these two solutions embody very distinct monitoring focuses, which leads me to believe there's room for both tools, as well as different teams for both ...
The 2019 State of E-Commerce Infrastructure Report, from Webscale, analyzes findings from a comprehensive survey of more than 450 ecommerce professionals regarding how their online stores performed during the 2019 holiday season. Some key insights from the report include ...
Robinhood is a unicorn startup that has been disrupting the way by which many millennials have been investing and managing their money for the past few years. For Robinhood, the burden of proof was to show that they can provide an infrastructure that is as scalable, reliable and secure as that of major banks who have been developing their trading infrastructure for the last quarter-century. That promise fell flat last week, when the market volatility brought about a set of edge cases that brought Robinhood's trading app to its knees ...
Application backend monitoring is the key to acquiring visibility across the enterprise's application stack, from the application layer and underlying infrastructure to third-party API services, web servers and databases, be they on-premises, in a public or private cloud, or in a hybrid model. By tracking and reporting performance in real time, IT teams can ensure applications perform at peak efficiency — and guarantee a seamless customer experience. How can IT operations teams improve application backend monitoring? By embracing artificial intelligence for operations — AIOps ...
In 2020, DevOps teams will face heightened expectations for higher speed and frequency of code delivery, which means their IT environments will become even more modular, ephemeral and dynamic — and significantly more complicated to monitor. As a result, AIOps will further cement its position as the most effective technology that DevOps teams can use to see and control what's going on with their applications and their underlying infrastructure, so that they can prevent outages. Here I outline five key trends to watch related to how AIOps will impact DevOps in 2020 and beyond ...
With the spread of the coronavirus (COVID-19), CIOs should focus on three short-term actions to increase their organizations' resilience against disruptions and prepare for rebound and growth, according to Gartner ...
Whether you consider the first generation of APM or the updates that followed for SOA and microservices, the most basic premise of the tools remains the same — PROVIDE VISIBILITY ...