Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: DSlade
New Today: 90
New Yesterday: 105
Overall: 144024

People Online:
Visitors: 61
Members: 6
Total: 67 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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.


The Itil Community Forum: Forums

ITIL :: View topic - Seeking Thoughts on This
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Seeking Thoughts on This

 
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion
View previous topic :: View next topic  
Author Message
valawman
Newbie
Newbie


Joined: Sep 21, 2006
Posts: 7
Location: Vienna, VA - USA

PostPosted: Wed Jun 08, 2011 9:10 pm    Post subject: Seeking Thoughts on This Reply with quote

My organization will be rolling out a new service management product late this summer. It is part of a project that includes the implementation of a CMDB and, while much progress has been made in work on that area, there is a concern that not all CI's will be discovered or instrumented by the product in time for the launch date. That being the case, my organization is attempting to determine and agree on the best way to categorize CI's and services not yet discovered or instrumented by the new tool, this in order to categorize incidents properly but with enough flexibility to grow and accomodate services and CI's as the tool matures. We're not looking for a silver bullet to resolve this but are wondering if others had to face a similar issue and what approach was taken to address it.
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3307
Location: London, UK

PostPosted: Wed Jun 08, 2011 10:22 pm    Post subject: Reply with quote

It is rather easy

P I C S V

1 - ignore the tool / auto discovery
2 - use the service desk to find out what services are being provided
3 - Identify the components of each service, server etc
4 - use the SD and DC staff to find out where they are, what they are etc
5 - populate the CMDB
6 - give the CMDB to the SD to use - it is for them to do first

Autodiscovery does not find the CIs....it finds interfaces or connections that meet the criteria - set the criteria too weak and get too much crap

set it to tight and get nothing

You have to use the Autodiscovery as a tool to verify certain informaiton and that is it, It does not replace staff crawling on the floor in the DC nor techs updating visio, excel or word documents about things.
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
valawman
Newbie
Newbie


Joined: Sep 21, 2006
Posts: 7
Location: Vienna, VA - USA

PostPosted: Wed Jun 08, 2011 11:40 pm    Post subject: Reply with quote

UKVIKING...appreciate the response.

I agree that planning is the key element in all this. Ideally, every service and associated CI's should be defined. What of the instance where this has not been completed for every CI, or there is a CI that is part of a service that has yet to be defined? In some ways it would seem to be similar to what we saw with the CTI structure in Remedy in that it was recommended to include an Item called "Miscellaneous" for those unanticipated issues.

We have been defining services and CI's as part of this project, but we're getting close to deadlines and implementation dates. Another question is at what point do you feel comfortable with what has been defined to where you can move forward? I'm betting that the answer is "it depends."
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3307
Location: London, UK

PostPosted: Thu Jun 09, 2011 4:00 pm    Post subject: Reply with quote

there are two answers

1 - it depends

2 - Config mgmt is like the movie the never ending tale

once you have gone through and made all the CIs for your services, you have to go back and periodically verify, add, change subtract

It is NOT static
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
StanleyLuces
Newbie
Newbie


Joined: Mar 20, 2011
Posts: 6
Location: Makati, Philippines

PostPosted: Thu Jun 09, 2011 8:18 pm    Post subject: Reply with quote

CI's not being discovered during the intial roll out is NOT and should not be a concern in my opinion... I believe service management should adapt to the company's changing requirements.. no matter how dynamic it is.

I remember a case study during my OSA wherein a company started out with just Request fullfillment and nothing else.. then grew to inlcude all process and functions as time goes on..

Simply put.. with just your current CI's and categories, roll it out.. then when something new gets discovered - new CI's, new categoreis etc .. then just add it.

I seem to always hear this kind of concern during initial roll out of service management systems and what it does is uneccessarily prolong the roll out date.. dont worry.. no one says you cannot improve on it later on.. ITIL doesnt - "Continual Service Improvement" ryt? =)
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3307
Location: London, UK

PostPosted: Thu Jun 09, 2011 11:11 pm    Post subject: Reply with quote

All

The initial definition of a service may be fit for purpose when you roll out the tool. For ex

you identified -

EMAIL as a service
You create /allocate servers as CIs.
you create / allocate applications as CIs
you create / allocate system services as CIs

Then after several tickets were raised on the email service as identifed, you realize that EMAIL as a service is actualy multiple services that make up the service called EMAIL

You have a blackberry service
you have executive staff email
you have the normal staff email
you have email filtering (message labs)
you have etc

You now need to adjust / update the CMDB by continually going through the verification and status accounting piece on a periodic basis.

You have identified 10 servers as the server farm for the mail service - however, it turns out that 6 of them are for zzzz and 3 are for xxxx and 1 is for xxx. Are they all production - or test or development servers.

All need to be in the CMDB for the IT SM tool.

The Confug mgmt role does not end merely because you filled in the blanks on the CIs for the servers.

All the fungible - data that expires - data needs to be verified periodically and regularly.

I would be ready to move forward with the CMDB once I have the policy, process and the procedures in place and when the initial set of data is entered and verified as well as defined what is in scope for the initial deployment
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
valawman
Newbie
Newbie


Joined: Sep 21, 2006
Posts: 7
Location: Vienna, VA - USA

PostPosted: Fri Jun 10, 2011 4:24 am    Post subject: Reply with quote

The key issue here is that it is not static. I think a lot of people feel more comfortable if it were, but that is not the case...nor could it be the case. It then becomes incumbent on the organization to decide how to best handle newly identified/newly realized services and their CI's.

I do appreciate the feedback!
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3307
Location: London, UK

PostPosted: Fri Jun 10, 2011 5:46 am    Post subject: Reply with quote

valawman

The policy / process documents should define how to identify any new service terminate old services etc

the policy provides the guidance
the process defines what is to be done when
the procedures the step by step
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.