|
Kifinti Newsletter
First Edition
Sept, 2010 - Vol 1, Issue 1 |
|
|
 |
| Quick Links |
Upcoming Events
Service Catalog Webinar
Thursday September 22, 2011 from 1:00 PM to 2:30 PM EDT
Kifinti Solutions and FrontRange Solutions will be hosting a Service Catalog webinar
Webinar
FrontRange Solutions Technology & Customer Case Study Event
Wednesday September 28, 2011 from 9:30 AM to 3:30 PM EDT
Kifinti and FrontRange invite you to join us for an interactive Workshop on IT Service Management. Our session will include Customer Case Studies, Networking, Best Practices and Technology Updates..
Ottawa-Carleton District School Board
ITSM Training Course Toronto
Monday October 24, 2011 at 9:00 AM EDT -to- Wednesday October 26, 2011 at 5:00 PM EDT
Kifinti Solutions will be hosting a 3 - day ITSM Training Course
Brampton Civic Hospital
HEAT Administration Training Course
Tuesday November 1, 2011 at 9:00 AM EDT -to- Friday November 4, 2011 at 5:00 PM EDT
Kifinti Solutions will be hosting a 4-day HEAT Administration Training Course
Dufferin-Peel DSB
IPCM Training Course
Monday November 28, 2011 at 9:00 AM EST -to- Wednesday November 30, 2011 at 5:00 PM EST
Kifinti Solutions will be hosting a 3-day IPCM training Course
DPCDSB - Adult Continuing Education Centre
|
|
|
| Greetings! |
Our first edition of the Kifinti newsletter is here. Our goal is to be informative, educational, fun, or at least as fun as a newsletter can be. and.... to provide it regularly (our goal is monthly). With each new edition, we will bring you a focused topic, with tips and tricks on how to implement this internally, advice from our expert consultants, thought provoking topics, words of wisdom from our clients, consultants, updates on Kifinti training dates, marketing events and more.
This issue will focus on the Service Catalog. What it is? The benefits? Pitfalls or lessons learned, and technologies to help you implement it. |
|
Service Catalog | |
Service Catalog - What is it? How can it benefit us? Where do we start defining our Service Catalog? These are all questions many organizations are asking themselves today.
What is a "Service Catalog" ? A "Service Catalog" is (ITIL Service Design) a database or structured document with information about all Live IT Services, including those available for Deployment. The Service Catalog is the only part of the ITIL Service Portfolio published to Customers, and is used to support the sale and delivery of IT Services. The Service Catalog includes information about deliverables, prices, contact points, ordering and request processes.
Implementing a Service Catalog to some organizations can be a difficult task, and many organizations struggle with the implementation of a Service Catalog. Many struggle because they are taking their IT and Business organization back to basics, and defining what it is that they deliver, and how it is that they deliver it. Starting at the beginning can make this an effort and process that is daunting and overwhelming to some.
A quote from Todd Morris of the City of London was "The service catalog project was vital to our customers and our division. It helped by formally listing our services, but more importantly, drive how we measure and improve the services we offer."
Some feedback from the City regarding their experiences are the following:
1. Engage an expert - We had a qualified consultant that had a large amount of experience with service catalog's and ITIL. You may think you know what the steps are going to entail when building a service catalog, but unless you've gone through the experience you will fall into many of the possible pitfalls that await the inexperienced.
- Drilling endlessly into CI's.
- Business vs. Technical - Unless you are experienced, you and your staff will constantly be slamming doors on avenues of interest between the two. We found living in the grey between the two allowed us to slowly build out our Technical service catalogue, while beginning on the foundations of the Business service catalog.
- Long drawn out projects - We decided on short 2 month projects that allowed us to engage staff, gather information, document it and discuss what we did well and tactics on how to improve in future phases.
2. Engage, document and approve cycle - Staff need to be engaged early on, to acclimatize themselves to the goals of the project. Once everyone is on the same page, you can begin the work of gathering the data, documenting it and ensuring their managers approve of what's being captured.
3. Communication - Early on a communication strategy was put together, to ensure everyone, from our staff, to our managers and finally our CTO, were informed as to our progress and what was next and in turn required from all stakeholders moving forward.
Brian McNamee ITIL Consultant says the "top mistakes or misunderstandings of a Service Catalog are"...
4. Assume your customer understands what you are talking about - A common mistake with many Service Catalog initiatives is defining services in technology terms, with service levels based on the metrics that are easiest for IT to track. While IT tends to be organized around technical, skill-based or asset-based silos, business users think in business outcomes. So while IT's customers may be thinking about on-boarding new employees, IT is talking about their change management process.
5. Build it and they will come - Most calatog projects stop when the document is published or posted to the corporate intranet. The document quickly becomes stale and non-relevant to your business users.
6. GoYour Own Way - Another pitfall why Service Catalogs are difficult to create is that, like other corporate service areas we are highly skilled people...in our discipline. Leveraging our internal relationships (e.g. Sales or Marketing) to help create a catalog, not only will save you time, it helps build stronger relationships with your customers.
In closing, as always, there are many tools, technologies and people available to assist you in this endeavour. Please join us for an informative webinar on implementing a Service Catalog, during this webinar you will be highlighted on the following:
- Brian McNamee (Kifinti ITIL process expert) and FrontRange, talk about the benefits of a ServiceCatalog.
- The do's and don'ts for embarking on a Service Catalog initiative.
- How technologies like FrontRange's Service Catalog can help you implement a Service Catalog within your organization.
To register for the webinar click HERE and to see an overview of the FrontRange Service Catalog Solution visit.
http://www.kifinti.com/products/frs-service-catalog
|
|
|
|
|
HEAT Tips and Tricks for Implementing a Service Catalog in FrontRange HEAT or FrontRange ITSM
| |
Implementation of a Service Catalog can take on many forms and there are many different options available from FrontRange to help organizations implement a Service Catalog. There is the Service Catalog solution, that is a separate module that you can purchase that works with both HEAT and ITSM. This module is extensive and offers approximately 70 different service request types for IT, Purchasing and Facilities. However, many customers starting out on this initiative don't realize you can also implement a Service Catalog with the tools you already own.
What we have attempted to do here is outline ways of leveraging what you own to implement a Service Catalog in HEAT or ITSM and also encourage you to ask us about the Service Catalog module from FrontRange to help you understand more about the options before you.

To implement a Service Catalog in HEAT there are many ways, and of course, it depends on how extensive you want it to be. Some of the basic building blocks and ideas of how HEAT can help you implement a Service Catalog would be the following:
Leverage the basic HEAT Configuration Tables
- Within the native HEAT application you have configuration tables that allow you to track asset / configuration information. HEAT offers you the flexibility to customize new types of Configuration Records and the flexibility to customize new types of Services.
- While not native out of the box functionality, you can configure HEAT to allow you to link those new Services in the Configuration table to existing or new Configuration Items.
Revisit the Call Log and detail table configuration
- Within the native HEAT application you have example Service Requests like "Employee Setup", and these service requests can have links to an associated "detail screen". The native configuration is "Call Type to Detail Screen", and while this may not be configured in every implementation, the ability to link type i.e. Call Type or Service Request Type, exists in the data model. This basic feature can be leveraged for all types of service requests and can easily be configured to enable you to manage the various request types I.E. "request for service, access, new employee, etc.".
Publish Requests for Service to the Web
- By leveraging HEAT Self Service you can publish portions or all of the service request form(s) enabling customers to Self Serve.
Let the Business Approve
- Automate the business approval process by using the BPAM workflow engine to send out an email to the business unit managers for appropriate approvals for the service request.
- Managers can have access to HEAT to approve requests, or emails can be used to approve the requests leveraging the Message Center.
Business as usual
- Once the request is submitted and approved, staff can complete the assignment as they normally would. However, now that we have the details about the specific request and completion we can ensure we are updating the configuration database as part of the process, keeping our configuration or asset information up to date.

There are many ways to implement a Service Catalog in ITSM, and of course, it depends on how extensive you want it to be. Some of the basic building blocks and ideas of how HEAT can help you implement a Service Catalog would be the following:
Leverage the Configuration Management Module
- Within ITSM you have the Configuration Management Module and the pre-built data model for Configuration Items and Services. This data model comes pre-built with an extensive list of CI types, as well as out of the box IT Services.
Leverage the native object linking
- One of the great strengths of the ITSM solution is the native ability to link anything to anything. As such, the Configuration Management module has pre-built links to CI's, Services and Service Level Agreements.
Revisit the Incident Module configuration
- Within the native Incident application you have the ability to define an Incident or Request. If you choose a request, as an example, an "Employee Setup" you can configure associated "detail screens" in ITSM.
Publish Requests for Service to the Web
- By leveraging ITSM Self Service, you can publish those forms or sections of those forms enabling customers to Self Serve.
Let the Business Approve
- Automate the business approval process by using the ITSM workflow to send out an email to the business unit managers for appropriate approvals for the service request.
- Managers can have access to ITSM to approve requests, or emails can be used to approve the requests leveraging the ITSM email listener.
Business as usual
- Once the request is submitted and approved, staff can complete the assignment as they normally would. However, now that we have the details about the specific request and completion, we can ensure we are updating the configuration database as part of the process keeping our configuration or asset information up to date.
|
Advice from the Kifinti Experts | |
As part of our newsletter we would like to provide for you answers to questions you may have. As this is our first of many, we are looking to solicit feedback from you on topics, and will pick some on a monthly basis and respond to them in our "Ask the experts" section.
Please send in your suggestions to paul@kifinti.com and we will include them in the October edition. |
|
|
Since this is our first newsletter, we appreciate your feedback and look forward to having this evolve into something educational, informative, and something that provides our customers insight into new and exciting topics, answers to your questions, or... simply a way to keep current on the latest offerings.
Please treat this as a work in progress, and please.... we encourage positive criticism, as we are IT people, not professional writers...:)
So provide us your feedback and we will make sure the newsletter meets the needs of you, our valued customers!
Sincerely
The Kifinti Teambenefits.
Sincerely,
|
|
|
Kifinti "Day a Month Program" |
If you need help with a report, configuration change, workflow cusotmization, training or upgrades but don't have the time to do it?
Consider leveraging the Kifinti Day a Month program and get access to an experienced consultant when you need it.
| | Purchase 12 days and get 2 at no additional cost |
|
|