Talk:Service Catalog

From Wikipedia, the free encyclopedia

[edit] Is Service Catalog for User or Customer?

I am just learning ITIL -- as I work my way through ITIL Foundation training, it seems that Service Catalog, as defined in the Service Level Management process, is primarily a document intended for the Customer (the one who will pay for the service, negotiate agreements, etc.). However, this article describes a service catalog that is very much intended for the User, which seems quite different from what ITIL specifies (does the article reflect the reality of how the term is coming to be used in the marketplace?). Any comments from someone more expert in ITIL and ITSM? West81 20:24, 15 December 2006 (UTC)

The SC is divided into halves – The Business Service catalog and the Technical Service Catalog

Service Level Management supports Service Catalog Management in the creation of a customer facing Business Service Catalog written with the customer in mind describing services without too much technical language or detail. Where as in the Technical Services Catalog services will be described with detail including all of the technical specifications.

SERVICE LEVEL AGREEMENT STRUCTURES There are different types of Service Level Agreement structures: Customer Based – Separate SLA’s for each customer covering multiple services. This is used if separate customers have very different needs and requirements. Service Based – An SLA covering one single service for all customers that use that service. This is used when the requirements of IT services differs little between each customer; Multi-Level SLA - It is possible however that neither of the above options is suitable in which case a multi-level SLA could be used. This type of structure reduces the duplication of effort while still providing customization to customers and services.

Multi-Level SLA’s cover: Corporate Level – All generic issues are covered e.g. the corporate security service where passwords and ID cards are serviced; Customer Level – Issues specific to a customer can be dealt with e.g. the security requirements for one department within and organization is higher than the other; Service Level – All issues relevant to a specific service (in relation to the specific customer) are covered e.g., the email service for a particular department may need to be encrypted, and require secure backups.

SLA DESIGN When designing the contents of an SLA there are certain set criteria that need to be covered: • Introduction • Service Hours • Availability targets • Reliability • Support Arrangements • Transaction response Times • Disaster recovery • Reporting Requirements • Incentives and Penalties

SLA LIFECYCLE The lifecycle of the SLA has the following phases: • Begin with the creation of the Service Catalog. • Discuss Service Level Requirements with the customer are discussed • Service level requirements are mapped against Service catalog • Sign Service Level Agreement once all negotiations on requirements are completed and agreed upon by the Service Level Manager and the customer • Ongoing and frequent review of achievements comprised of feedback on how well the service level agreement has been managed • Appendices (where appropriate) may be needed based on reviews. These would be added to the SLA. • Review and renew of SLA’s

[edit] Links

I think the recent commercial link to a Software Catalog provider is inappropriate—it seems this section should either list multiple major providers or none at all. Due to conflict of interest, I will not edit the links section, but I encourage an impartial party to clean it up. West81 15:12, 14 December 2006 (UTC)

What is inappropriate about listing all vendors? It is information after all. I think listing only few is unfair. —Preceding unsigned comment added by Serviceguy (talk • contribs) 01:55, 21 May 2008 (UTC)

Wikipedia is not for advertising or promotion. I think I have removed all the links to commercial vendors. Do not re-add them wtihout discussing them here first. KnightLago (talk) 02:15, 21 May 2008 (UTC)