The State of the Service Catalog-Service Structure Defined-Part 1 (Post 3 of 5)

A 5 post series about the Service Catalog presented to you by Dana P. Miller, Service Catalog Process Owner

Along with the Service Catalog we also developed a service structure that provides a consistent way of defining and presenting services.  You may be curious to know why we have the word “Overview” after some services, Email Overview for example.  

We use the word “overview” when we are presenting a broad service. The overview defines the service by its capabilities, benefits, and key features. Those broad services have associated Service Requests that facilitate our customers accessing the services they need. Service Requests include action words like “request” or “create” in their titles.

For example, in the Service Catalog the Email Overview service is also composed of three Service Requests that provide actionable, self-service ways for our clients to access the services they need. An overview service can have one or multiple associated service requests or none.

Email Overview
Reliable and secure email service provided through Google’s Gmail App.

Request to Create or Change Entity Email Account
Entity email accounts do not correspond directly to individuals. They are created for a group of people, such as a department or student organization.

Create an Email Alias
Faculty and staff may log-in to their directory entry and enter up to six email aliases that they wish to use.

This series about the Service Catalog is designed to help you understand how your daily work contributes to the success of IT Services and Miami University.

If you have any questions or ideas for improving the Service Catalog contact me (mille704@miamioh.ed) or enter a Continual Improvement Committee for IT Services (CIRCUIT) suggestion.

Thanks.

Dana P. Miller-Service Catalog Process Owner

Cursor_and_Dana

 

Leave a Reply

Your email address will not be published. Required fields are marked *