The current cloud catalog and how the services are used is brittle, requires regular manual intervention, and is prone to errors.
The cause of these issues are:
cloud vendors can rename services at anytime (or remove them)
cloud vendors can change the categories of a service at any time
This leads to issues where:
we don't update CRE individually selected skills if the skill/product name changes in CC. This means no-one is supporting that specific service
Old tickets with the original product name/skill won't be updated, breaking analytics
Focus area mappings will become out of date when product names change, requiring manual intervention
We need to develop a more robust solution that solves the following use cases:
customers get a comprehensive list of services to pick from in the DoiT Console
services/FA selections by CREs map to these selections so we can route tickets appropriately
changes to the cloud catalog can automatically be managed/resolved
tickets with old product values don't get lost in analytics
The current cloud catalog and how the services are used is brittle, requires regular manual intervention, and is prone to errors. The cause of these issues are:
This leads to issues where:
We need to develop a more robust solution that solves the following use cases: