Skip to main content

IT Service Management - Tools

In today’s world where demand for up to date services has grown and the lead times for delivery has continued to be shortened I am often asked, what is the best tool? The answer is, of course, “it depends!” Every organization has different needs, budgets and resources, however the requirements for automated building, testing and delivering new functionality has never been greater.

Every organization must be able to look at the list of requirements for tools from both the operational and development sides of the IT organization as the functions become more and more integrated.

The starting point is a list of generic requirements. An integrated suite is preferable and should include options such as:
  • Service Portfolio
  • Service Catalog
  • Service Design Tools
  • Discovery/Deployment/Licensing Technology
  • Workflow or process engines
  • CMDB’S
  • Configuration Management Systems (CMS)
  • Self Help for Users
  • Remote Control
  • Diagnostic Utilities
  • Reporting Tools/Dashboards
  • Service Knowledge Management System (SKMS)
Depending on your requirements, goals, budget and maturity level, you may need one, several or all of the above technologies. A good suite will offer the flexibility to purchase only those modules that are currently needed by your organization with the option to add more over time.

The next step is to assess your current tools and their use. The assessment may reveal that you are not using existing tools to their fullest capability. Consider the following when evaluating existing tools and possible new purchases:
  • Support for monitoring service levels, data structure, data handling and integration
  • Integration of multi-vendor infrastructure components
  • Conformity to international open standards
  • Flexibility in implementation usage and data sharing
  • Usability
  • Distributed clients with a centralized shared database
  • Conversion requirements
  • Data backup, control and security
  • Support and scalability
The following are useful evaluation techniques:
  • Gather your Requirements. (Use the MoSCoW strategy for evaluating your requirements. Must haves (M), Should haves (S), Could haves (C), and our Won’t haves but would like to have (W)?)
  • From the MoSCoW list, create a Statement of Requirements (SOR).
  • Identify possible products
  • Determine a selection criteria
  • Evaluate products
  • Put together a short list of products
  • Score the final products
  • Rank the products
  • Select the product that meets your needs and budget
Please remember that any tool is NOT a silver bullet. Effective internal processes are critical to gaining efficiencies through tools. Tool success will likely depend on your planning, deployment, management and improvement of process.

While there are many good technologies in the marketplace today, it is important to select the one that meets your specific and unique requirements.

For more information please see ITIL Foundation, ITIL Service Design, ITIL Service Strategy


Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...