The reference code that that identifies the inventory item. In physical items, it is usually a reference number (generally with a bar code) although the device manufacturer’s serial number could be used. An Asset Tag is often used instead of Serial Number because not all items have a serial number.
A task, service or action formally assigned to a technician. In standard ITIL terminology this is also known as a "Work Order" (which should not be confused with the "Work Order form" in the Track-It! application, which is more generic). Synonyms: Assignments
Any service provided by the Service Desk, which is important to the business activity of the organization. For example: Email, Internet, CRM system, etc. The Business Services are listed in the Services Catalog.
The group of people who need to approve a Change before it can be implemented. Usually members of the CAB are responsible for (or their business depends on) specific services. In the Track-It! application, the CAB members are defined in the Change Management Policy and are called Approvers.Synonyms: CAB
The technician responsible for managing the Change Request. In the Track-It! application, the Change Coordinator is identified in the "Assigned Technician" field.
The person (end user) who receives the service provided by the Service Desk. In the Track-It! application, the Customer is indicated in the Requestor field.
The day and time at which the Request, Task, etc. must be resolved. In the case of Requests, the Due Date is calculated automatically based on the SLA, taking into account criteria such as impact, urgency, etc.
A change which, due to its extreme urgency, requires immediate action and therefore should not go through the normal approval process. Emergency Changes are applied first and documented afterwards.
An external organization or company that provides products or services that the Service Desk needs in order to provide the service. Examples: the ISP or telephony supplier, hardware suppliers, etc.
The degree to which the customers are affected. The impact is higher when a large number of customers are affected, or when the degradation of service affects the business.
A root cause of a Problems or Requests, for which relevant information has been published. A typical example is a “bug” that appears in the software manufacturer’s Knowledge Database.
The group of technicians who attend to the customers when a request is made. Level 1 technicians try to close the request directly and if this is not possible, they escalate the request to Level 2.Synonyms: 1st Level, First Level
The groups of technicians who only attend to those requests that cannot be resolved by Level 1 technicians. Level 2 technicians are usually organized into groups based on specialization (for example: Systems, Infrastructure, Database, etc.) Synonyms: 2nd Level, Second Level
A Change that meets the criteria for applying the Change Management process. It is called Non-Standard in order to be differentiated from Standard Changes, which do not need approval from the Change Manager.
A Change that meets the criteria for applying the Change Management process. Normal Changes should not be confused with Standard Changes (which do not require approval from the Change Manager).
That which causes (or may cause) a degradation of service, or which may give rise to new support requests. In the cases of support requests, the Problem is usually the root cause of the request.
The person responsible for the Problem Management process. Usually the Problem Manager also is responsible for proactively identifying Problems (usually this is done through a periodic review of Requests as well as other sources).
A formal petition reported by the customer to the Service Desk. There are several types of requests: technical support requests, service requests, complaints, etc. In all cases, they are registered in the Service Desk in order to provide follow-up.
The documented response or solution that meets the customer’s needs and allows the request to be closed. A resolution can be a summary of actions performed by a technician, step-by-step instructions for the customer to follow, an explanation, etc.
Detailed information about the costs and the potential negative aspects that could arise as a result of a Change Impementation, in terms of how customers might be affected. Usually the Risk and Impact Analysis is provided by the Change Coordinator (with the help of a Specialist if necessary) before the Change Request is submitted for approval. The Risk and Impct Analysis is often broken down into two parts: Business Risk and Technology Risk.Synonyms: Impact Analysis, Risk Analysis
The manufacturer’s reference code used to identify a specific hardware asset. The Serial number is usually printed in a tag or it is visible on the asset in some other way.
List of activities and services that are officially provided by the Service Desk. The Service Catalog is often used to classify Requests for reporting purposes and may also be used as criteria when assigning SLAs.
The days and times during which a service is provided. For example, the Service Schedule for Desktop Support might be from Monday to Friday from 9 to 5, whereas the Service Schedule for Infrastructure and Systems Support might be 24x7.
The parameters that determine the quality of the service that must be delivered. An SLA usually defines the amount of time allowed for resolution, taking into account factors such as Impact and Urgency. An SLA may include other parameters as well, such as the amount of time allowed for the initial response (once the request has been registered).Synonyms: Service Level Agreement
A technician responsible for resolving Problems, Tasks and Requests related to a specific area or technology. For example: Specialist in Microsoft Exchange.
A change where the Change Management Process is not applied because a formal procedure already exists for the change, and has been approved by the Change Manager in order to avoid the need for case-by-case approvals.
A job or action formally assigned to the technician or group of technicians. A task may (although not necessarily) form part of the resolution cycle for a Request, a Change or a Problem. In the Track-It! application, a Task is called "Assignment".
An alternative solution that allows a Request to be closed, although it does not eliminate the root cause. A workaround is often a “temporary solution” that alleviates the symptoms, as opposed to a “definitive solution” that cures the problem.