Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
NOTE: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
Posted: Sat Jun 03, 2006 1:23 pm Post subject: Service Catalog examples
I'm looking for Service Catalog inspiration. I've read so much on the topic that my head is spinning and my pen is dry. Yet, I haven't seen a Service Catalog that fully satisfies my thirst for business-focused service descriptions. Would you guys have some? _________________ BR,
Fabien Papleux
Accenture
Technology Consulting | Service Excellence
Red Badge Certified
We're working on this right now as well and having a hard time of it, we keep getting stuck at the application level. The service's just don't seem to be inclusive enough
I feel a little bit the same. For some reason, I don't think SAP is a service. Accounts Payable could be, but then it would be more a financial service... how does this all fit for you guys? _________________ BR,
Fabien Papleux
Accenture
Technology Consulting | Service Excellence
Red Badge Certified
Joined: Feb 02, 2006 Posts: 41 Location: Sydney, Australia
Posted: Wed Jun 07, 2006 9:41 am Post subject:
Fabien wrote:
I feel a little bit the same. For some reason, I don't think SAP is a service. Accounts Payable could be, but then it would be more a financial service... how does this all fit for you guys?
All IT parts / components of SAP (E.g. Servers / Software / Network / Internet Connection) provided by your IT Department to your organization is the IT service. The same applies to any IT systems used by your Accounts paybale.
So are you saying the business facing SLA would be written at the SAP level? With an OLA in place for the servers, network, etc. Or would you do write the SLA's at the component level?
Joined: Feb 02, 2006 Posts: 41 Location: Sydney, Australia
Posted: Fri Jun 09, 2006 8:55 am Post subject:
Lola wrote:
So are you saying the business facing SLA would be written at the SAP level? With an OLA in place for the servers, network, etc. Or would you do write the SLA's at the component level?
Normally you would have SAP as the service in your SLA, with all other components which are parts of that service (E.g. Network, Servers, software) hanging of it. I.e. One component goes down, then estimate the downtime of the service (How long would it take to bring the service up?) Measure each against one another.
Don't confuse SLA with and OLA. SLA is the agreement between IT department and business. OLA is agreement between Internal IT department Functions.
Are you saying that you promise an server availabilty level in your SLA, independently from the availability of the service? _________________ BR,
Fabien Papleux
Accenture
Technology Consulting | Service Excellence
Red Badge Certified
I would argue that items such as 'Network' or 'SAP' are not services. Would you walk up to your customer and ask them if they would like half a pound of Network? How much would half a pound of Network cost?
Basically, a service is key to communication between IS and the business. Therefore it should be defined in terms that make sense to both parties.
This becomes particularly crucial if you plan to establish a service based costing model. To do this, you will need to determine a unit price for each service in order to charge customers based on consumption. You can then use your CMDB to understand what processes, hardware, software and personnel are required to deliver that service thereby truely understanding the cost of IT.
Gartner recently published a study showing that by 2008, 70% of companies will still confuse products, services and systems. To me, the definition is very clear:
Systems are the technologies that enable services.
Services are viewed by the customer as a cohesive whole (note that this is the customer perview!) and exist to fulfill a specific business need or process.
So for example, does your company view MS Windows Server 2003 as the service IT provides, or does it view printing as the service? The same goes for software like SAP or peoplesoft, or the network. They are there, and IT is proud of them, but they don't really provide anything in and of themselves. They are there to support the greater service - which the business actually consumes.
The best approach I've found is to zoom out as far as you can, and take a fresh perspective. Is Citrix a service? No? Well, what does Citrix do? It allows you to connect remotely. Is connecting remotely really a service? Probably not - what does connecting remotely allow me to do? Work anywhere anytime? Yes, that sounds like a service I'd be willing to pay for.
I know this is a highly debated topic, so please feel free to correct me where I've gone wrong or challenge any of these ideas.
The best approach I've found is to zoom out as far as you can, and take a fresh perspective. Is Citrix a service? No? Well, what does Citrix do? It allows you to connect remotely. Is connecting remotely really a service? Probably not - what does connecting remotely allow me to do? Work anywhere anytime? Yes, that sounds like a service I'd be willing to pay for.
I like your post. This piece may be the little bit I was missing in trying to explain to people "what is a service" and I think you hit it right on the head: A service is what a customer would be willing to pay for. Just like any consumer would. Not because IT said so, but because it makes sense for the business. I'm actually going to use this example... Thanks! _________________ BR,
Fabien Papleux
Accenture
Technology Consulting | Service Excellence
Red Badge Certified
Joined: Aug 11, 2006 Posts: 262 Location: Netherlands
Posted: Sat Aug 12, 2006 1:56 am Post subject:
Quote:
I like your post. This piece may be the little bit I was missing in trying to explain to people "what is a service" and I think you hit it right on the head: A service is what a customer would be willing to pay for. Just like any consumer would. Not because IT said so, but because it makes sense for the business. I'm actually going to use this example... Thanks!
So what you are saying is, you ought to ask your customer what he thinks is a service, write that down as your baseline and work out any further (productized)detail (i.e. servers, applications etc.) according to your own practical needs (change mgt, financial mgt etc.)
I like your post. This piece may be the little bit I was missing in trying to explain to people "what is a service" and I think you hit it right on the head: A service is what a customer would be willing to pay for. Just like any consumer would. Not because IT said so, but because it makes sense for the business. I'm actually going to use this example... Thanks!
So what you are saying is, you ought to ask your customer what he thinks is a service, write that down as your baseline and work out any further (productized)detail (i.e. servers, applications etc.) according to your own practical needs (change mgt, financial mgt etc.)
In your OLA, yes... _________________ BR,
Fabien Papleux
Accenture
Technology Consulting | Service Excellence
Red Badge Certified
Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Sat Aug 12, 2006 11:35 am Post subject:
Hello All,
The Service Catalog we offer our clients is part of our Service Management solution and is a mechanism that:
- Allows Service Groups to define their services and quickly add/publish the new Services to the Service Catalog
- Allows Service Groups to define and publish SLA data
- Allows Service Groups to modify/edit their Services
- Allows Service Groups to create and publish documents and templates against their Services
- Allows Service Customers/End Users to easily search and find the Services they need
- Allows Service Customers/End Users the ability to generate Service Requests that generate Service-related Tasks
- Allows the Service Groups to manage their Service Requests and Tasks, such as prioritization of the work
- Allows the Service Customers/End Users to see the priority, progress, and status on the work as it changes
- Allows users and Service Groups the ability to see auditing, trending, run reports, etc.
- Allows users to see relationships between Services, Service Groups, Service Resources, End Users, Documents, Assets, Products, etc. in an integrated CMDB
- Etc.
Hence, "Service Management" is on operational area. This conflicts with ITIL's concept of Service Management, which is intended to be a concept for how to run an IT organization but seems to be right in line with what our customers expect Service Management to be, which is the Process by which you manage Services.
I hope this helps.
Regards, _________________ [Edited by Admin to remove link]
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum