Service catalogue

Template:Linkless A service catalog is comprised of a list of services that an organization provides, often to its employees or customers. Each service within the catalog often includes: -A description of the service -Timeframes or service level agreement for fulfilling the service -Who is entitled to request/view the service -costs (if any) -How to fulfill the service

A User's Perspective

A consumer of the service would often go to a website to search for a specfic service, such as a request for a new laptop or change in benefits or add a new employee to a department. The service catalog site will often have searching and categorization for easy retrieval of services, particularly when an organization has hundreds if not thousands of services it provides and publishes. The user would click on the related service where a description and other details would be provided. From there, the user would enter any pertinent information regarding the service (contact information, service-specific questions) and submit the request for service. This request then often has routing and approvals, service level management and other processes which would take place within the organization to fulfill the request. A user may also go back to the site at a later time to check on the status of a request, or to view overall metrics on how the organization is performing the services it provides.

A Business Unit Managers Perspective

Business Unit Managers determine what services to "publish" to end users via the service catalog. Business Unit Managers and Analysts would determine what questions are to be asked of the user, any approvals necessary for a request, and what other systems or processes are needed to fulfill the request. Once the service is defined and the fulfillment process organized, these people or a more technical employee would build the requisite functionality into the service definition and then publish this to the service catalog.

An Example

A good example of a service catalog and this process is the startup of a new employee. This would involve:

1. A business unit manager or analyst (we'll call a service author) documenting the current process. For a new employee this likely includes finding a workspace, ordering a phone, ordering a network connection, ordering a computer, creating a login, and applying any application group permissions and other security items. Some of these items (ordering a phone, ordering a computer) can be done in parallel, while other tasks may need to be sequential (likely need a corporate login prior to applying any group permissions).

2. A service author determines what the service level agreements are for each of these tasks as well as the service level for all of the tasks combined. For a new employee, this is likely a number of days.

3. A service author determines any approvals that are needed for this request. Here, a Director or Vice President often has to approve any hires, as well as an HR representative.

4. A service author determines any costs for the service. For a new hire, the department likely gets charged for the space, computer and phone from the fulfilling department such as IT and Facilities.

5. Once the services are defined the service author would publish these services to the organization. Here, service catalog software is used to publish this service to an intranet along with categorizing it for easy retrieval by employees.

6. Once the service is published a department manager would go to the service catalog on the company intranet and request the service for a new employee filling out the required form information.

7. The request is routed to the required approvers and the service level monitoring begins via the service catalog software.

8. Once approvals are complete (often via their own form), the request is routed to the various applications for each individual fulfillment task that was defined by the author in step 1. This may be manual processes or integrations to other applications.

9. The department author goes back to the service catalog to check on his or her requests. They may see that this request has had the facilities approval and the workspace defined, but the request is still waiting on delivery of the computer and phone.

10. Once all of the fulfillment tasks are complete, the requester (Department Manager here) gets notified that the request has been completed. The service level metrics are compiled and available for future requestors.