Simulation modeling (Service Design) (Continual Service Improvement) A technique that creates a detailed Model to predict the behavior. 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 modeled, 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.
Single Point of Contact (Service Operation) Providing a single consistent way to communicate with an Organization or Business Unit. For example, a Single Point of Contact for an IT Service Provider is usually called a Service Desk.
Single Point of Failure (SPOF) (Service Design) Any Configuration Item that can cause an Incident when it fails, and for which a Countermeasure has not been implemented. A SPOF may be a person, or a step in a Process or Activity, as well as a Component of the IT Infrastructure.
See Failure.
SIP Service Improvement Plan
SKMS Service Knowledge Management System
SLA Service Level Agreement
SLAM Chart (Continual Service Improvement) A Service Level Agreement Monitoring Chart is used to help monitor and report achievements against Service Level Targets. A SLAM Chart is typically color coded to show whether each agreed Service Level Target has been met, missed, or nearly missed during each of the previous 12 months.
SLM Service Level Management
SLP Service Level Package
SLR Service Level Requirement
SMART (Service Design) (Continual Service Improvement) An acronym for helping to remember that targets in Service Level Agreements and Project Plans should be Specific, Measurable, Achievable, Relevant and Timely.
SMO Service Maintenance Objective
Snapshot (Service Transition) The current state of a Configuration as captured by a discovery tool. Also used as a synonym for Benchmark.
See Baseline.
SoC Separation of Concerns
SOP Standard Operating Procedures
SOR Statement of requirements
Source See Service Sourcing.
Specification A formal definition of Requirements. A Specification may be used to define technical or Operational Requirements, and may be internal or external. Many public Standards consist of a Code of Practice and a Specification. The Specification defines the Standard against which an Organization can be Audited.
SPI Service Provider Interface
SPM Service Portfolio Management
SPO Service Provisioning Optimization
SPOF Single Point of Failure
Stakeholder All people who have an interest in an Organization, Project, IT Service etc. Stakeholders may be interested in the Activities, targets, Resources, or Deliverables. Stakeholders may include Customers, Partners, employees, shareholders, owners, etc.
See RACI.
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 Organization such as ISO or BSI.
See Guideline.
Standard Change (Service Transition) A pre-approved Change that is low Risk, relatively common and follows a Procedure or Work Instruction. For example password reset or provision of standard equipment to a new employee. RFCs are not required to implement a Standard Change, and they are logged and tracked using a different mechanism, such as a Service Request.
See Change Model.
Standard Operating Procedures (SOP) (Service Operation) Procedures used by IT Operations Management.
Standby (Service Design) Used to refer to Resources that are not required to deliver the Live IT Services, but are available to support IT Service Continuity Plans. For example a Standby data center. may be maintained to support Hot Standby, Warm Standby or Cold Standby arrangements.
Statement of Requirements (SOR) (Service Design) A Document containing all Requirements for a product purchase, or a new or changed IT Service. See Terms of Reference.
Status The name of a required field in many types of Record. It shows the current stage in the Lifecycle of the associated Configuration Item, Incident, Problem etc.
Status Accounting (Service Transition) The Activity responsible for recording and reporting the Lifecycle of each Configuration Item.
Storage Management (Service Operation) The Process responsible for managing the storage and maintenance of data throughout its Lifecycle.
Strategic (Service Strategy) The highest of three levels of Planning and delivery (Strategic, Tactical, Operational). Strategic Activities include Objective setting and long term Planning to achieve the overall Vision.
Strategy (Service Strategy) A Strategic Plan designed to achieve defined Objectives.
Super User (Service Operation) A User who helps other Users, and assists in communication with the Service Desk or other parts of the IT Service Provider. Super Users typically provide support for minor Incidents and training.
Supplier (Service Strategy) (Service Design) A Third Party responsible for supplying goods or Services that are required to deliver IT services. Examples of suppliers include commodity hardware and software vendors, network and telecom providers, and Outsourcing Organizations
See Underpinning Contract, Supply Chain.
Supplier and Contract Database (SCD) (Service Design) A database or structured Document used to manage Supplier Contracts throughout their Lifecycle. The SCD contains key Attributes of all Contracts with Suppliers, and should be part of the Service Knowledge Management System.
Supplier Management (Service Design) The Process responsible for ensuring that all Contracts with Suppliers support the needs of the Business, and that all Suppliers meet their contractual commitments.
Supply Chain (Service Strategy) The Activities in a Value Chain carried out by Suppliers. A Supply Chain typically involves multiple Suppliers, each adding value to the product or Service.
See Value Network.
Support Group (Service Operation) A group of people with technical skills. Support Groups provide the Technical Support needed by all of the IT Service Management Processes.
See Technical Management.
Support Hours (Service Design) (Service Operation) The times or hours when support is available to the Users. Typically this is the hours when the Service Desk is available. Support Hours should be defined in a Service Level Agreement, and may be different from Service Hours. For example, Service Hours may be 24 hours a day, but the Support Hours may be 07:00 to 19:00.
Supporting Service (Service Strategy) A Service that enables or enhances a Core Service. For example a Directory Service or a Backup Service.
See Service Package.
SWOT Analysis (Continual Service Improvement) A technique that reviews and analyses the internal strengths and weaknesses of an Organization and the external opportunities and threats which it faces SWOT stands for Strengths, Weaknesses, Opportunities and Threats.
System A number of related things that work together to achieve an overall Objective. For example:
A computer System including hardware, software and Applications.
A management System, including multiple Processes that are planned and managed together.
For example a Quality Management System.
A Database Management System or Operating System that includes many software modules that are designed to perform a set of related Functions.
System Management The part of IT Service Management that focuses on the management of IT Infrastructure rather than Process.