USMBOK Home Page
Access the ShopShop | Forums | Support
Introduction Code of Conduct Career Headquarters
Communities Community Membership Community Sponsorship Community Partnership Community Leadership Service: Connections™ Join Today
USMBOK™ USMBOK Best Practices USMBOK Key Measures USMBOK Extensions USMBOK Mappings USMBOK Governance Council
Program Overview Credentials Approved Education Provider Program Professional Development Credits Continuing Certification Requirements Qualifications Governance Council
Webinars
USMBOK Support USMBOK Forums
Introduction to ITSM-COE™ Curriculum Student Portal Classroom Events Web Events
About the USMBOK Permissions Linking to the USMBOK
Key Concepts
  • The Service Management System
  • Service Management Areas of Expertise
  • The Operational Alignment Models
  • The Business Planning Framework
  • The Performance Management Framework
  • The Supporting Lifecycles
  • The Policy Framework
  • The Service Lifecycle
  • The Service Transaction Engine
  • The Governance Framework

Knowledge Domains
  • USM0XX: Introduction to Knowledge Domains
  • USM1XX: Service Customer Management
  • USM2XX: Service Fulfillment Management
  • USM3XX: Service Quality Management
  • USM4XX: Service Delivery Management
  • USM5XX: Service Operations Management
  • USM6XX: Service Infrastructure Management
  • USM7XX: Service Value Management

Useful Links
  • The USMBOK Home Page
  • USMBOK Knowledge Articles
  • Best Practice Statement Library
  • Key Performance Measure Library
  • Guide to USMBOK
  • USMBOK Discussion Forums
  • USMBOK Support Service Desk

USMBOK™: Key Concepts

The Service Transaction Engine

The Service Provider Organization's "Heart" and Primary Means of Service Customer Expectations

The service transaction engine (STE) represents the collective processing of transactions or 'requests for service' by all the service provider applications and information systems.

The STE typically processes the vast percentage of the service provider workload, efficiently, effectively, automatically, and more often than not - unseen. The existence of a STE is generally ignored by most service management and best practice frameworks.

When systems, applications and infrastructure within the STE encounter issues they manifest as problems and incidents, and are managed by the event and support lifecycles.

Non STE events would include the non-incident related service requests and any event that demands manual intervention. These type of events include:

  • Add new employee
  • Requests for information
  • Requests for change (upgrade, non-incident related changes)
  • Access rights

Non-STE events may well be processed eventually, after manual intervention, by the STE. Similarly, STE events may require manual intervention, and then be returned to the STE for automated processes.

The higher the percentage of service requests processed by the STE, the higher the customer satisfaction level and overall quality of service.

Tell a FriendTell a Friend
Home | Contact us | IP Guidelines | Terms and Conditions | Privacy Policy | Copyright © 1990-2008 IMC
©USMBOK®