Before starting your work with ITSM of your SimpleOne solution, at first, set the basic information about your IT infrastructure.
Role required: admin. |
Create User records of the SimpleOne solution to make them manage your ITSM processes.
Create Groups and assign users to them to perform the ITSM tasks and manage processes in groups. approving change requests, resolving incidents, receiving email notifications, or performing work order tasks.
Create your Configuration Items (CI) such as IT service components required for proper service delivery in Configuration Management Database (CMDB).
Within the CMDB, determine the following configuration records:
|
Within Knowledge Base, specify IT Services with specifications, SLA documentation, or content items of other sorts. This information is available for the SimpleOne end-users as external service specifications.
Within the Knowledge Base Dictionary, determine the following components and attributes of the content items:
|
Create and descibe your IT Services within Service Catalog. Service Catalog Management grants your customers actual information and details about provided IT Services and their statuses.
Within Service Portfolio, describe your services with all the needed information:
|
Within Knowledge Base (KB), specify IT Services with specifications, SLA documentation, or content items of other sorts. This information is available for the SimpleOne end-users as external service specifications.
Within SimpleOne, you can log your ITSM entities by inquiries received from users via phone call, e-mail, or self-service portal.
Learn more about creating a Self-Service Portal. |
Inquiry is a high-level entity that can be converted to the request of the other type (Incident, Problem, Change Request, Request).
|
ITSM-ticket types:
To made a transformation "Inquiry → Other request", follow the steps below:
Manual creation. Navigate to the ticket creating form ...description... how to create .... what was created |
States: Registered.
Categorization and prioritization are basic identification procedures and
According to the best ITIL practices, it is crucial to categorize a problem defining its priority and specifying the related information. Use the Problem form to create or update the problem and to establish relationships with related records.
...description... how bad is it? impact, urgency
A priority identifies the importance of a problem. It depends on the Impact and Urgency values and according to the priority matrix. ...description... how fast should be solved
Impact / Urgency | Low | Medium | High | Very High |
---|---|---|---|---|
Low | Low | Low | Moderate | High |
Medium | Low | Moderate | High | Critical |
High | Moderate | High | Critical | Critical |
Very High | Critical | Critical | Critical | Critical |
user responsible
Push the Assign to me button to assign a problem to your User record.
...description...
...description...
...description...
SLA not breached for some tickets |
To create a task, enter the follow the steps below:
To enter the creating task form, select the Create New option creating form.
Initializing → In progress → Completing
...description...
State / Ticket | Incident | Problem | Change Request | Request Template |
---|---|---|---|---|
Registered | ✓ | ✓ | ✓ | ✓ |
Authorization | ✓ | ✓ | ||
Assigned | ✓ | ✓ | ||
Scheduled | ✓ | |||
In Progress | ✓ | ✓ | ✓ | ✓ |
Postponed | ✓ | ✓ | ||
Information Needed | ✓ | |||
External Processing | ✓ | |||
Completed | ✓ | ✓ | ✓ | ✓ |
Rejected by User | ✓ | ✓ | ||
Post Implementation Review | ✓ | |||
Closed | ✓ | ✓ | ✓ | ✓ |
Known Error | ✓ |