Questions many people will have about creating a service catalog include "what should I include in my service catalog, what should it look like and where do I start?" These questions often delay, or even derail, the adoption of a service catalog within an organization.
To help customers overcome these worries and to ensure rapid deployment, assyst is delivered with a fully formed service catalog hierarchy structure and a comprehensive set of service and service offering templates. These allow customers to use all aspects of the assyst service catalog functionality out-of-the-box.
The diagram below shows the Axios structure for the hierarchy of standard IT services, which is supplied with each service catalog implementation.
These can be used as delivered, or tailored to suit each organization's individual needs. This provides a time-saving starting point to help organizations get quickly up and running with their service catalog.
Each service then has a supporting structure of offerings (or other services). The services are also linked to the relevant Configuration Items (CIs) in the CMDB.
Organizations define and structure their services, usually as part of an initial workshop, which always provokes discussion and debate around how to best group and order these. There is no absolute way to do this and the Axios model has been based on our experience and discussion with key practitioners.