gogogo
Syndetics cover image
Image from Syndetics

IT services : costs, metrics, benchmarking, and marketing / Anthony F. Tardugno, Thomas R. DiPasquale, Robert E. Matthews.

By: Contributor(s): Material type: TextTextSeries: Enterprise computing seriesPublication details: Upper Saddle River, N.J. : Prentice Hall PTR, c2000.Description: xvii, 201 p. : ill. ; 25 cmISBN:
  • 0130191957
Subject(s): DDC classification:
  • 004.0688 TAR
Holdings
Item type Current library Call number Copy number Status Date due Barcode
Standard Loan Moylish Library Main Collection 004.0688 TAR (Browse shelf(Opens below)) 1 Available 39002000211335

Enhanced descriptions from Syndetics:

PLEASE PROVIDE COURSE INFORMATION PLEASE PROVIDE

Includes bibliographical references and index.

Table of contents provided by Syndetics

  • List of Figures (p. xvii)
  • List of Tables (p. xix)
  • Preface (p. xxi)
  • Who Should Read This Book? (p. xxiv)
  • Acknowledgments (p. xxvii)
  • Chapter 1 Introduction (p. 1)
  • 1.1 Background (p. 2)
  • 1.2 Sourcing from Within--Why Insource? (p. 3)
  • 1.2.1 Customer Satisfaction (p. 5)
  • 1.2.2 Definability and Measurability (p. 5)
  • 1.2.3 Stability and Variability (p. 5)
  • 1.2.4 Predictability (p. 6)
  • 1.3 Planning for Success (p. 7)
  • 1.3.1 Understand and Define Your Problem Set (p. 7)
  • 1.3.2 Define Your Scope (p. 7)
  • 1.3.3 Establish Guiding Principles (p. 8)
  • 1.3.4 Make Fact-Based Decisions (p. 8)
  • 1.3.5 Benchmark (p. 8)
  • 1.3.6 Understand Your Goal/Define Your End State (p. 9)
  • 1.3.7 Establish Coalitions/Gain Buy-In (p. 9)
  • 1.3.8 Exercise Quality (p. 9)
  • 1.3.9 Develop a Plan and Stick To It (p. 10)
  • Chapter 2 Getting Started (p. 11)
  • 2.1 Writing the Job Ticket--"The Ask" (p. 11)
  • 2.1.1 Problem Statement (p. 12)
  • 2.1.2 Purpose/Statement of Deliverables (p. 13)
  • 2.1.3 Scope/Boundaries (p. 13)
  • 2.1.4 Team Definitions (p. 14)
  • 2.2 Forming "The Core Team" (p. 15)
  • 2.2.1 Find a Strong/Capable Project Manager (p. 16)
  • 2.2.2 Selecting the Members of the "Core Team" (p. 16)
  • 2.2.3 Staff Team with Dedicated Resources (p. 16)
  • 2.2.4 Empower the Work Group--Autonomy (p. 17)
  • 2.3 Charting the Approach (p. 17)
  • 2.3.1 Restate the Problem Set (p. 17)
  • 2.3.2 Define the Scope (p. 18)
  • 2.3.3 Define Your Work Process/Review and Feedback Loop (p. 19)
  • 2.3.4 Gain Buy-In Early (p. 19)
  • 2.3.5 Have Fun! (p. 20)
  • Chapter 3 Establishing and Managing Coalitions--Gaining Buy-In (p. 21)
  • 3.1 Establish Management Buy-In Early (p. 21)
  • 3.1.1 Supporter (p. 22)
  • 3.1.2 Non-Supporter (p. 22)
  • 3.1.3 "On the Fence" (p. 22)
  • 3.2 Establish Customer Buy-In Early (p. 23)
  • 3.3 Establish Supplier Coalitions (p. 24)
  • 3.3.1 Procure Subject Matter Experts (SMEs) (p. 24)
  • 3.3.2 Test Market for Resource Availability-- Can It Be Staffed Effectively? (p. 24)
  • 3.4 Establish an Information Network (p. 27)
  • 3.5 Identify and Understand Risk (p. 28)
  • Chapter 4 Business Linkage (p. 29)
  • 4.1 Understanding the Company Mission (p. 29)
  • 4.2 Services in a Traditional Business Framework (p. 30)
  • 4.3 Object-Oriented Service Delivery Framework (p. 32)
  • 4.4 Balancing the Services (p. 35)
  • 4.5 Services Linkages (p. 38)
  • Chapter 5 Marketing and Communications (p. 41)
  • 5.1 Marketing 101 (p. 42)
  • 5.1.1 Identify and Define the Product/Service (p. 42)
  • 5.1.2 Determine the Value and Price of the Product/Service (p. 44)
  • 5.1.3 Establish a Distribution or Delivery Vehicle (p. 46)
  • 5.2 Communicate Early and Often-- Who, What, When, Where, How (p. 48)
  • 5.2.1 Who (p. 48)
  • 5.2.2 What (p. 48)
  • 5.2.3 When (p. 49)
  • 5.2.4 Where (p. 49)
  • 5.2.5 How (p. 49)
  • 5.3 Define/Communicate the Metrics Upfront-- Quality, Cost, Delivery, Value (p. 50)
  • 5.3.1 Quality (p. 50)
  • 5.3.2 Cost (p. 53)
  • 5.3.3 Delivery (p. 53)
  • 5.3.4 Value (p. 56)
  • 5.4 Understand/Identify and Communicate Risk (p. 56)
  • 5.5 Explain Roles and Responsibilities (p. 58)
  • 5.5.1 Account Management (p. 59)
  • 5.5.2 Help Desk (p. 59)
  • 5.5.3 IT Management (p. 59)
  • 5.5.4 Operations Management (p. 60)
  • Chapter 6 Taking a Customer Approach (p. 61)
  • 6.1 Understanding Your Customers' Requirements (p. 62)
  • 6.2 Developing the Service Model (p. 62)
  • 6.2.1 Brainstorm List (p. 63)
  • 6.2.2 Work Package Grouping Example List (p. 66)
  • 6.3 One-Stop Shopping--Seamless Delivery (p. 68)
  • 6.3.1 Project Management (p. 69)
  • 6.3.2 Support Services (p. 70)
  • 6.3.3 Operations (p. 72)
  • 6.3.4 Asset Planning and Control (p. 75)
  • 6.3.5 Help Desk (p. 75)
  • 6.4 Customer Satisfaction (p. 79)
  • Chapter 7 Processes and Procedures (p. 81)
  • 7.1 Introduction (p. 81)
  • 7.2 Customer Communication (p. 81)
  • 7.2.1 Help Desk Notification Procedure (p. 83)
  • 7.2.2 Customer Escalation Process (p. 84)
  • 7.2.3 Exception Reporting Process (p. 87)
  • 7.3 Internal Communication Processes and Procedures (p. 88)
  • 7.3.1 Help Desk Off-Hour Escalation Process (p. 89)
  • 7.3.2 Team Member and Vendor Contact Lists (p. 90)
  • 7.3.3 ISD Internal Request Procedure (p. 92)
  • 7.4 Change Control Process (p. 93)
  • 7.4.1 Change Control (p. 94)
  • 7.4.2 Change Control List (p. 94)
  • Chapter 8 Structuring for Success (p. 97)
  • 8.1 Introduction (p. 97)
  • 8.2 Structuring the Organization (p. 97)
  • 8.2.1 Help Desk (p. 99)
  • 8.2.2 Job Descriptions (p. 100)
  • Chapter 9 Resource and Cost Model (p. 103)
  • 9.1 Introduction (p. 103)
  • 9.2 Resource Model (p. 104)
  • 9.2.1 Scheduled or On Demand (p. 104)
  • 9.2.2 Offered Time (p. 104)
  • 9.2.3 Skill Set (p. 105)
  • 9.2.4 Frequency (p. 105)
  • 9.2.5 Unit of Measure (p. 106)
  • 9.3 Estimating Server Units (p. 106)
  • 9.4 Resource Spreadsheet (p. 108)
  • 9.5 Cost Management (p. 109)
  • 9.6 Ongoing DB Monitoring and Maintenance (p. 110)
  • 9.7 Application Server Support (p. 112)
  • 9.8 Cost Model (p. 113)
  • Chapter 10 Benchmarking (p. 117)
  • 10.1 Why Benchmark? (p. 118)
  • 10.1.1 Understanding the Current Environment (p. 118)
  • 10.1.2 Get New Ideas (p. 118)
  • 10.1.3 Ratify Old Ideas (p. 119)
  • 10.2 Establishing a Company Profile (p. 119)
  • 10.2.1 Understand Business Context (p. 119)
  • 10.2.2 Key on Primary Areas of Concern, Vulnerability, or Exposure (p. 120)
  • 10.2.3 Understand Yourself (p. 120)
  • 10.3 Identifying Target Companies (p. 122)
  • 10.3.1 Identify Peers (p. 123)
  • 10.3.2 Utilize Vendor's Resources (p. 123)
  • 10.3.3 Coordinate Data Collection/Visits (p. 123)
  • 10.3.4 Sensitivity to Peer Sites (p. 124)
  • 10.3.5 Confidentiality (p. 125)
  • 10.4 Developing Your Questionnaire (p. 125)
  • 10.4.1 Structure Queries Appropriately (p. 125)
  • 10.4.2 Site Visit Questionnaire (p. 125)
  • 10.5 Analyzing the Benchmark Data (p. 128)
  • 10.5.1 Document, Document, Document (p. 129)
  • 10.5.2 Analyze Efficiently (p. 129)
  • 10.5.3 Be Quick or Be Dead (p. 129)
  • 10.6 Implementation (p. 130)
  • Chapter 11 Measuring Success (p. 131)
  • 11.1 Defining Success (p. 131)
  • 11.1.1 Define Success Before You Start (p. 132)
  • 11.1.2 Service Level Agreements (p. 134)
  • 11.2 Ensuring Success (p. 135)
  • 11.3 Metrics (p. 137)
  • 11.3.1 Service Level Definition (p. 137)
  • 11.3.2 Service Metrics (p. 139)
  • 11.4 When Have You Reached Success? (p. 141)
  • 11.4.1 Service Satisfaction Survey (p. 142)
  • 11.4.2 Continuous Success (p. 143)
  • Chapter 12 Lessons Learned--Key Messages (p. 145)
  • 12.1 Overview (p. 145)
  • 12.2 Processes (p. 146)
  • 12.3 People (p. 146)
  • 12.4 Communication (p. 146)
  • 12.5 Technology (p. 147)
  • Chapter 13 Frequently Asked Questions (FAQ) (p. 149)
  • Appendix A Job Descriptions (p. 153)
  • A.1 Account Manager (p. 153)
  • Education (p. 153)
  • Experience (p. 153)
  • Skills (p. 154)
  • Performance Expectations (p. 154)
  • Training and Development (p. 156)
  • A.2 Oracle System Administrator (OSA) (p. 156)
  • Education (p. 156)
  • Experience (p. 156)
  • Skills (p. 157)
  • Performance Expectations (p. 157)
  • Training and Development (p. 159)
  • A.3 System Administrator (SA) (p. 160)
  • Education (p. 160)
  • Experience (p. 160)
  • Skills (p. 161)
  • Performance Expectations (p. 161)
  • Training and Development (p. 163)
  • A.4 Database Administrator (DBA) (p. 164)
  • Education (p. 164)
  • Experience (p. 164)
  • Skills (p. 165)
  • Performance Expectations (p. 165)
  • Training and Development (p. 167)
  • A.5 Network Specialist (NS) (p. 168)
  • Education (p. 168)
  • Experience (p. 168)
  • Skills (p. 168)
  • Performance Expectations (p. 168)
  • Training and Development (p. 170)
  • A.6 Operational Manager (Ops Mgr) (p. 171)
  • Education (p. 171)
  • Experience (p. 171)
  • Skills (p. 171)
  • Performance Expectations (p. 171)
  • Training and Development (p. 173)
  • A.7 Manager Customer Services (CS Mgr) (p. 174)
  • Education (p. 174)
  • Experience (p. 174)
  • Skills (p. 174)
  • Performance Expectations (p. 174)
  • Training and Development (p. 175)
  • Appendix B Sample Service Level Agreement (p. 177)
  • Section I System Availability (p. 178)
  • Section II Problem Management (p. 179)
  • Section III Support Services (p. 181)
  • Attachment B Problem Severity Definitions (p. 182)
  • Attachment C Problem Resolution Control (p. 183)
  • Attachment D Status Call Contacts (p. 183)
  • Attachment E Escalation Contacts (p. 184)
  • Index (p. 193)

Excerpt provided by Syndetics

Preface It was not our initial intention to write a book dealing with IT services. We were assembled as a team to solve a real business problem. We were given our mission, put on our armor, jumped on our horses, and rode off to " slay dragons " in the name of customer satisfaction. The reason we draw this distinction is to point out the advantage this has for you, the reader, of being able to see demonstrated and proven results. It becomes obvious as you progress through each chapter that you are not getting a bunch of theory or unproved strategy. Instead, you are getting the benefit of a strategy and approach that has been implemented and refined, and is providing results. It is without question that we now live in an age where customer satisfaction is the primary motivating factor among industries. Businesses are focusing their efforts toward improved, expeditious, and more convenient products and services. There is a growing customer "obsession" that is having a net effect not only on what products and services a company or organization is offering, but how they are organized to deliver them. IT services are no exception. In the not too distant past, business was tied to its internal IT shop as the "only game in town" to deliver their requirements. With consulting and outsourcing strongly making their way onto the scene in the early nineties, the need to get services "inside" has waned, opening up delivery options to the business. This competition alone has probably done more for customer satisfaction than any single factor in the IT arena. As a business manager and customer of IT services, you want the most cost-effective solution that best meets your requirements regardless of who delivers them. As an IT provider of services, you want to maximize customer satisfaction by optimizing the level of service and optimizing cost. Whether the service delivery remains in-house or goes outside is almost immaterial. The delivery must go to the supplier most capable of delivering to the metrics defined. It is meeting or exceeding the customer's requirements that matters most. The "knowledge revolution" has spawned an army of "knowledge workers" equipped with "intellectual property" ready to do battle in today's "information on demand" market. As a result, there is an ever-increasing need for applications and associated infrastructure to be up and available when the customer requires them, and to keep the critical supply of information flowing. It is for this reason that your business needs to have the delivery of its IT services organized and resourced to meet the current business requirements, and at the same time be flexible enough to be able to change with the same frequency and velocity that the business does. For years, customers of IT computer services have long enjoyed the stability and predictability of centralized legacy mainframe applications. Most of their interactions with systems were through straightforward, unsophisticated, character-based screens, which essentially reflected a relatively simple single-threaded work process. Uncomplicated data structures served as the solid foundation on which the well-established custom application would reliably "chug" along. Database and system administrators lived a pretty uneventful existence, given the maturity of not only the application and hardware, but also the monitoring and maintenance tools. In the scheme of things, it is really only recently that large-scale enterprise resource planning (ERP) applications, residing on a distributed UNIX environment with sophisticated front-ends served by PC-based servers and workstations, have really begun their assault on the mainframe market. Commercial off-the-shelf (COTS) ERP packages are becoming commonplace and more and more appear to be among the strategy of major industries. With the systems trend moving in this direction, IT operations have turned their attention to the infrastructure required, both environment and support structure, to deliver the level of service to which the customer base has become accustomed. Having had the experience of little information and benchmarking from which to draw, it seemed to make sense that we put pen to paper, or more appropriately finger to keyboard. Our goal was simple: to document and share our findings, and more importantly, share the process we used to develop an integrated service delivery (ISD) model. IT Services: Costs, Metrics, Benchmarking, and Marketing was written to address the issues and challenges surrounding the development and implementation of an enterprise-wide operations center for application software. It's no mystery, if you are able to clearly define your end state, where you want to be, and if you have a "map" clearly marked with how to get there, and you have the resources and the means, then you will successfully make the "trip!" This book is your "map" to successfully developing, implementing, and measuring an ISD model. As you progress through the book you will see that there are no "magic formulas" or proprietary methodologies, just a straightforward, organized, customer-oriented approach. The key being customer-oriented. With technology so widespread and readily available, competitive advantage must be sought through other avenues. These days a main competitive advantage comes through customer care and satisfaction. Think about your last PC shopping experience. In your search you probably noticed that PCs, for the most part, are essentially all the same. What factors went into your choice? After-sale support and service, 800 number ease of use, onsite repair versus depot or mail-in repair? All of these are customer-related factors. It is for this reason that we took a customer approach in developing our ISD model. Whether it is PCs, appliances, cars, or computing operations services, customers all want to be "handled with care." Using a ground-up approach, we modeled the services required and expected by our customer base, and it was from this base set of services that we developed and defined the entire ISD model. An approach that is implemented, is working, and is proven! Here is a brief overview of what is contained within the book: Chapter 1 frames the book by describing the background and the reason for developing an integrated service delivery model. This chapter basically puts the book in perspective and gives you a frame of reference. Chapters 2 and 3 provide the detailed steps necessary to get started-from writing the "job ticket" and "charting the approach" to organizing the project and management teams. Chapters 4 and 5 describe the business linkages from a services and services framework perspective while defining the marketing and communication aspects of service development and delivery. Chapters 6 and 7 describe the development of requirements and the service model from a customer perspective. The chapters further detail how to develop the processes necessary to deliver the service model to the defined level of service. Chapters 8 and 9 detail how to structure the organization to deliver the service model, as well as how to develop a correlating resource and cost model. Chapters 10 and 11 walk you through the benchmarking process, help you to define the metrics against which you should measure your ISD delivery, and define how you know when you reach success. Chapters 12 and 13 review lessons learned and "key messages" along with the answers to frequently asked questions. Who Should Read This Book? IT Services: Costs, Metrics, Benchmarking, and Marketing was written to be viewed from multiple perspectives: the IT professional, the business manager, the customer, and the student. It serves as a "road map" for IT executives, IT managers, and IT senior technical personnel who are tackling the issues surrounding the development and implementation of an enterprise-wide operations center for commercial off-the-shelf (COTS) application software. It is a practical guide for business managers working with the IT community to develop a stable, predictable, cost-effective support infrastructure for COTS application software supporting the enterprise. It is an educational vehicle to help customers better understand what they should expect from their COTS application software support infrastructure and to be better able to articulate their requirements. It is also an educational vehicle that provides the student, the aspiring IT and business professional, with a real-life practical application of developing and implementing an integrated service delivery model. Practical, not just theory. Excerpted from IT Services: Costs, Metrics, Benchmarking and Marketing by Anthony F. Tardugno, Thomas DiPasquale, Robert Matthews All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Author notes provided by Syndetics

Anthony F. Tardugno is Manager, Site Manufacturing Information Technology for the Corporate Strategic Services Division at Xerox.

Powered by Koha