All services are usually stored in the core repository named Service Portfolio which is divided in two parts:
Service Pipeline - This part of the repository contains services that are not yet live. They may be just proposed, or under development or construction.
Service Catalogue - This part of the repository contains active services offered to the customers; this is the only part visible to them.
In SimpleOne, services are used in each practice, not only in the Incident Management practice, for example; they are also used in Change Control practice, Request Fulfillment practice, so every ITSM/ESM object is clearly linked with a Service. In fact, service is a core element of the ITSM/ESM Solution.
One of their purposes is requests classifying; also, services are used in the Knowledge Management practice to classify the articles in the Knowledge Base.
As an SKMS (Service Knowledge Management System), SimpleOne uses services in the configuration management system to relate the Knowledge Base articles with the end-user needs.
Create a Service
Create Services and define them with descriptions, SLAs, and other service specifications stored in the Knowledge Base.
