Skip to content
ISBN: 013030770X
ISBN13: 9780130307705

IT Problem Management (Harris Kern's Enterprise Computing Institute)

$10.99List Price: $44.99
Save $34.00!
ISBN: 013030770X
ISBN13: 9780130307705
Formats

Conditions

A read copy, but remains in excellent condition.

Formats

Conditions

A read copy, but remains in excellent condition.

See all 1 editionsfrom $10.99

Book Overview

Preface In the past three decades, businesses have made staggering investments in technology to increase their productivity and efficiency. The technological infrastructure of these companies has become increasingly sophisticated and complex. Most companies today are extremely dependent on their technological infrastructure. Operating without it is like trying to run a business without a telephone or electricity. Businesses depend on their technology at least as much as, perhaps more than, any other utility. However, unlike the telephone and electric industries, technology has not had the benefit of 100 + years to mature under the control of a handful of companies. Thousands of companies contribute to technology, each doing whatever they think will sell the best. Extreme and rapid innovation is the rule, not the exception. Change is the rule, not the exception. The resulting complexity has posed a new challenge for companies: how to realize the potential and anticipated benefits of the investments in an environment of constant change. Businesses are so reliant on technology that they need it to operate as reliably, consistently, and universally as the telephone and electricity. We are a long way from achieving that level of service. Businesses face rising costs because of constant failures that result in lost productivity. It is very difficult and expensive to find the resources with the expertise to manage and repair their infrastructures. It is extremely difficult and expensive to keep those resources trained to manage a constantly evolving environment. But guess what. There is no choice but to invest in technology, because it has to be done. Business cannot stop investing in technology or they will be crushed by the competition. So what have they done? They have standardized to limit the diversity, the expertise required, and the problems associated with diversity. They have striven to make the infrastructure as reliable as the telephone and to keep employees productive. And they have created a team that has the skills, the facilities, and the charter to fix existing problems and reduce future problems. That team is the service center, and this book shares how the best of those teams are doing just that. Technology impacts more than just a business's internal operations. What about the company's customers? They often need support, as well. More companies are realizing the value of providing quality service to its customers. Some studies have indicated that keeping a customer costs one-tenth the price of getting a new one, while the return business from satisfied customers count for substantially more than one-tenth of a company's revenue. It makes good economic sense to spend money on keeping existing clients satisfied. For many companies, that means providing customers with quality support for the products and services they purchase. So who in the company provides that service? You guessed it-the service center. What is a service center? It is an organization whose charter and mission are to provide support services to internal or external customers, or to both. It is a concentration of expertise, processes, and tools dedicated to taking customers' requests and fulfilling them in a timely and cost-effective manner, leaving the customer delighted with the experience. A service center has a defined range of service offerings, from fixing problems to providing value-added services, and everything in between. This book is intended to help a company set up that service center and deliver those services cost effectively. The book focuses on structuring the organization and building the processes to move service requests efficiently and effectively through the organization to deliver quality service to the customer. It discusses the pitfalls that afflict many service centers and offers techniques and solutions to avoid those pitfalls. The book discusses the tools available to help a service center manage its business and deliver high quality cost-effective services to customers. The traditional help desk is still around, but many have evolved into service centers. As more businesses are faced with increasing technology costsand increasing pressure to be productive and efficient internally-while delighting external customers-many more help desks will be forced to evolve. For a well-run help desk, the evolutionis natural and not overly difficult. Most help desks were originally designed to provide one type of service, technical support. Help desks traditionally helped customers by fixing their problems and answering their questions. The help desk concentrated technical expertise, problem management processes, and tools to track and resolve customer problems, answer customer questions, and deliver that support as cost effectively as possible. Many help desks have done this quite successfully, and many have not. As their companies reengineer and look to streamline operations, many company executives have asked the simple question, "Today, you provide one type of service-technical support. How hard would it be to add additional services?" It's a fair question, because the help desk already takes service requests, tracks them, makes delivery commitments to customers, delivers the services, and charges the customers. The organization, the processes, the tools are in place. The evolution usually starts small, with simple, technology-related, value-added services, such as ordering PCs. You need a PC, contact the help desk. They'll figure out what you need, order it, track the order, install it when it arrives, and then support you if you have any questions. Voila, the help desk is now providing value-added services. Since you are ordering the equipment and maintaining and fixing it all the time, how about keeping track of it? No one else does. Again, voila, you're providing a value-added asset management service. Since you have all of that valuable information, can you report on it quarterly to the This description may be from another edition of this product.
Format:
Paperback
Language:
English
ISBN:
013030770X
ISBN13:
9780130307705
Release Date:
March 2001
Publisher:
Prentice Hall PTR
Length:
252 Pages
Weight:
1.55 lbs.
Dimensions:
9.2″ × 0.6″ × 6.9″
BusinessBusiness & FinanceBusiness & InvestingBusiness & ManagementComputer ScienceComputersComputers & TechnologyEducation & ReferenceEngineeringIndustrial, Manufacturing & Operational Systems

More by Gary Walker

Customer Reviews

4 customer ratings | 4 reviews
Write a Review

Very good book for problem solving...

I am currently working with returns and customer complains, this book helped me to lay out the problem solving procedures, flow charts and documentation. I would recomment to the people who are seeking solutions for IT or other problems.

0

Complete Guide to Service Center Processes

This is a great book for anyone involved in help desk or service center activities. I recommend this book for all IT professionals involved with production systems or anyone interested in IT methodology. This book gives the reader an appreciation for the documented processes and documentation that must be in place for a successful help desk venture.This book has process flows for the entire problem management arena complete with guidelines on how to pick the most successful strategy for your company. It helps you with the decision process by offering pros and cons for each strategy so that you can tailor the strategy for your own goals and objectives. Also present are strategies for escalating problems and the structure that must be in place to support the strategy.Other strong points of this book include the detail provided concerning the problem prioritization process, documented Triage processes, and escalation procedures. It also covers the documentation that must exist in order for a help desk to strive for cost effectiveness while meeting the goals of its customers. This books helps IT professionals in the decision making process, whether you are currently involved in help desk activities, preparing to start a help desk, or migrating your current help desk into a service center. I gave this book to our help desk and they quickly ordered a couple of copies for the other managers. This is truly a first rate narrative.

0

Unique book that fills a gap in service delivery literature

This book does, indeed, represent the first of its kind to extend problem management from a help desk function to an enterprise-wide process. Moreover, it contains some of the best practices and processes I have ever seen in print. Here are some of the highlights of what the book proposes that I know from experience works in an optimal fashion:*Managed response model, where the help desk validates issues, prioritizes them and sends them immediately to the proper tier-2 group for resolution. This is far superior to a model where the help desk attempts to resolve the issue because too many go to tier-2 anyway. In my experience the managed response model more closely aligns IT to business (tier-2 also functions in an account management role if the process and organization is mature), and there is no hand-off (tier-2 owns the problem, the help desk owns the problem management process).*The concept of a service catalog (sometimes called reference data or systems taxonomy) that allows you to capture metrics that lend themselves to Pareto analysis for system failures, etc. This is important for prioritizing fixes and patches to be released in future versions of an application.*Clear definitions of severity, priority, escalation and elevation. These are too often misunderstood or misused terms, yet each is an important element of problem management.*Detailed process for escalation and notification, which is not always implemented properly if implemented at all.*Linking problem management to service level objectives and business goals. This is alluded to in many help desk books, but rarely addressed in the detail that this book provides.*Alignment of problem management to other related processes, notably, change management. Finally, this dependency is recognized and discussed in a mainstream book. *Complete strategy for gathering and analyzing *relevant* metrics. Some gaps, but the approach is on target.*Service delivery as a concept and process is clearly described. I cannot count the times I have had to define "service delivery" and distinguish it from "application delivery" (the former addresses supporting applications in production, the latter is how they are developed and released into production - operations and maintenance vs. development and project management).Nothing is perfect, and here are some of the gaps I found:*No clearly defined acceptance criteria for bringing applications into production - the service center (help desk) should get, at a minimum, service level agreements, application profiles, troubleshooting guides and a criticality profile for every application going into production. These should be considered to be the minimum entry criteria for supporting an application.*Excellent discussion on priorities was marred by a lack of discussion about how to go about establishing a uniform baseline. I use a spreadsheet developed with a colleague that computes a criticality profile based on quantitative and qualitative measures.

0

At long last - a book that goes beyond the help desk

Finally! A book that addresses the fact that problem management goes far beyond the help desk domain and extends to encompass all of IT. Problem management the key to IT/business alignment because it directly supports achieving reliability, availability and service objectives. The approach taken in this book is, like all other books in the Enterprise Computing Institute series, to address people, process and technology. The authors start this book with standard fare on help desk organization. This information is available in virtually every help desk book on the market. However, the discussion becomes interesting when process is introduced. I thought the chapters on response models and service catalogs were particularly valuable. They certainly reflect the best practices that I have had to discover on my own as a service delivery consultant.Because I develop and implement service delivery solutions for a living I was gratified to see a chapter on this discipline. While I found little new here (I do this for a living), the approach is sound and the focus on tiers 2 and 3 roles and responsibilities is something that is consciously missing from all of the books on help desk management that I have read.I did learn a lot from the chapter on knowledge capture and sharing. This is an area that I have found to be weak in every organization in which I have had a consulting engagement. While there has been a lot written about capturing and sharing knowledge at the tier 1 (help desk) level, little has been written prior to this book about capturing and sharing knowledge across IT from a problem management point of view. Although this chapter does not provide detailed solutions it does give ideas and a good starting point from which to approach this aspect of IT problem management.The book ends with four final chapters that give a high-level overview of managing the process, service level agreements, service center tools and how to motivate IT participants in the problem management process. This book fills a large void in the IT service delivery body of knowledge because it is the first to address problem management as something larger than help desk operations. It extends the problem management process to tiers 2 and 3, which is something that the help desk books seem to only briefly address if they address it at all. Moreover, this book contains processes that are essential for aligning IT to business. As such this is a valuable addition to the professional body of knowledge for help desks and technical support specialists. If you work in production services or IT management you should definitely read this book you will also find the information in this book to be invaluable.

0