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.
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Wed Apr 14, 2010 11:42 pm Post subject:
scalc in OpenOffice.org could meet your requirements. In fact swrite might do the trick. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Thanks Diarmid,
but i search for a Tool to create a Service Catalog.
I have to design a Service Catalog, and i don`t khow how to begin, or what should be in a Catalog. So it would be helpful if i found an example or even a tool to create this.
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Thu Apr 15, 2010 8:06 pm Post subject:
You don't need a tool until you know what you are going to build. If you get a specific tool first you will be driven to design your service catalogue along the tools perception rather than meeting your requirements.
Your service catalogue will contain itemized services and information about them.
Beyond that, it depends what you want it for. Who will use it? What information will they want to obtain from it?
Some organizations build a service catalogue to tell their users or customers what services are available. Others build it to tell themselves what services they provide. Others combine the two roles.
At one end of the spectrum the catalogue might describe what services do and how to obtain and use them. At the other it might identify the underpinning components that each service depends on. There could be contact and management responsibility information. There could be a roadmap of the future of the service.
I could go on speculating and adding to the list, but that does not help you. You need to start by establishing why your organization wants a service catalogue; what it will be used for; who will use it; how it will be maintained; and stuff like that. It is often the case that answering those questions leads directly to how it needs to be designed and then to what tools are needed for it. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Is there a genuine business need which will be fulfilled by such a tool, or have you been asked by someone to provide a service catalogue.
I'll wager my glass of white wine it is the latter.
In which case, find out why the person in question wants a service catalogue. Really interrogate them, get them to specify their requirements, get them to define the business problem which will be resolved by implementing a catalogue, and then determine whether a catalogue is the solution to their problems.
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