IT-Systems International

Service Portfolio

(Service Strategy) The complete set of Services that are managed by a Service Provider. The Service Portfolio is used to manage the entire Lifecycle of all Services, and includes three Categories: Service Pipeline (proposed or in Development); Service Catalogue (Live or available for Deployment); and Retired Services.

Service Request

(Service Operation) A request from a User for information, or advice, or for a Standard Change or for Access to an IT Service. For example to reset a password, or to provide standard IT Services for a new User. Service Requests are usually handled by a Service Desk, and do not require an RFC to be submitted.

Service Validation and Testing

(Service Transition) The Process responsible for Validation and Testing of a new or Changed IT Service. Service Validation and Testing ensures that the IT Service matches its Design Specification and will meet the needs of the Business.

Simulation modelling

(Service Design) (Continual Service Improvement) A technique that creates a detailed Model to predict the behaviour of a Configuration Item or IT Service. Simulation Models can be very accurate but are expensive and time consuming to create. A Simulation Model is often created by using the actual Configuration Items that are being modelled, with artificial Workloads or Transactions. They are used in Capacity Management when accurate results are important. A simulation model is sometimes called a Performance Benchmark.

Standard

A mandatory Requirement. Examples include ISO/IEC 20000 (an international Standard), an internal security Standard for Unix configuration, or a government Standard for how financial Records should be maintained. The term Standard is also used to refer to a Code of Practice or Specification published by a Standards Organisation such as ISO or BSI.

Supporting Service

(Service Strategy) A Service that enables or enhances a Core Service. For example a Directory Service or a Backup Service

SWOT Analysis

(Continual Service Improvement) A technique that reviews and analyses the internal strengths and weaknesses of an Organisation and the external opportunities and threats which it faces SWOT stands for Strengths, Weaknesses, Opportunities and Threats.

Technical Service

Synonym for Infrastructure Service

Third Party

A person, group, or Business who is not part of the Service Level Agreement for an IT Service, but is required to ensure successful delivery of that IT Service. For example a software Supplier, a hardware maintenance company, or a facilities department. Requirements for Third Parties are typically specified in Underpinning Contracts or Operational Level Agreements.

Threat

Anything that might exploit a Vulnerability. Any potential cause of an Incident can be considered to be a Threat. For example a fire is a Threat that could exploit the Vulnerability of flammable floor coverings. This term is commonly used in Information Security Management and IT Service Continuity Management, but also applies to other areas such as Problem and Availability Management.

Transaction

A discrete Function performed by an IT Service. For example transferring money from one bank account to another. A single Transaction may involve numerous additions, deletions and modifications of data. Either all of these complete successfully or none of them is carried out.

Transition

(Service Transition) A change in state, corresponding to a movement of an IT Service or other Configuration Item from one Lifecycle status to the next.

Urgency

(Service Transition) (Service Design) A measure of how long it will be until an Incident, Problem or Change has a significant Impact on the Business. For example a high Impact Incident may have low Urgency, if the Impact will not affect the Business until the end of the financial year. Impact and Urgency are used to assign Priority.

Usability

(Service Design) The ease with which an Application, product, or IT Service can be used. Usability Requirements are often included in a Statement of Requirements.

User

A person who uses the IT Service on a day-to-day basis. Users are distinct from Customers, as some Customers do not use the IT Service directly.

Utility

(Service Strategy) Functionality offered by a Product or Service to meet a particular need. Utility is often summarised as "what it does".

Version

(Service Transition) A Version is used to identify a specific Baseline of a Configuration Item. Versions typically use a naming convention that enables the sequence or date of each Baseline to be identified. For example Payroll Application Version 3 contains updated functionality from Version 2.

Vulnerability

A weakness that could be exploited by a Threat. For example an open firewall port, a password that is never changed, or a flammable carpet. A missing Control is also considered to be a Vulnerability

Warranty

(Service Strategy) A promise or guarantee that a product or Service will meet its agreed Requirements.

Work Instruction

A Status that means Activities have started but are not yet complete. It is commonly used as a Status for Incidents, Problems, Changes etc.

Workload

The Resources required to deliver an identifiable part of an IT Service. Workloads may be Categorised by Users, groups of Users, or Functions within the IT Service. This is used to assist in analysing and managing the Capacity, Performance and Utilisation of Configuration Items and IT Services. The term Workload is sometimes used as a synonym for Throughput.