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: PMoorhous
New Today: 17
New Yesterday: 98
Overall: 143691

People Online:
Visitors: 62
Members: 7
Total: 69 .

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 - Defining CI for airport IT infrastructure
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Defining CI for airport IT infrastructure

 
Post new topic   Reply to topic    ITIL Forum Index -> Configuration Management
View previous topic :: View next topic  
Author Message
CA
Newbie
Newbie


Joined: Jul 06, 2007
Posts: 8

PostPosted: Sat Jul 07, 2007 10:09 am    Post subject: Defining CI for airport IT infrastructure Reply with quote

Is anyone ever define the CI for airport IT infrastructure. We are trying to define CI for Kiosk which has diffrent components CPU, Monitor, Keyboartd, pass port readers, credit card reader, printers. Kisok also has network connectivity attch with hub and switches. I am reallly appreciated if some one point us to right direction how can we define CI for Kiosk and their relationship for CMDB. An example will be a great help . Thanks in advance
Back to top
View user's profile
CA
Newbie
Newbie


Joined: Jul 06, 2007
Posts: 8

PostPosted: Mon Jul 09, 2007 11:26 pm    Post subject: Reply with quote

Can someone resposnse to my first post. The problem we are facing here is to define CI and their relationship. Every department or owner of critical system was asked to define their CI and in last few meeting we are unable to define how to pick and define CI and their relationship. Any help is really appreciated
Back to top
View user's profile
ARoll
Senior Itiler


Joined: Apr 10, 2006
Posts: 86
Location: Boise Idaho

PostPosted: Thu Jul 12, 2007 2:50 am    Post subject: Reply with quote

The primary question that would need to be asked when defining your granulatiry of CI's is: What is the problem you are trying to solve? This will help you to drive the level of detail you are wanting to go down to in your CI. Far as items that you will be tracking in your cmdb, what value will you gain from going down to specific component level i.e. keyboard mouse monitor etc? Those items may be better suited as apart of your asset management system and just be linked to from an attribute of your CI. So an approach that you may have is each unique kiosk will be its own CI so kiosk001, kiosk002 (naming convention just for example). These CI's would then have your relationships set to your switches/hubs.

also need to keep in mind is that the more detail or granularity you goto in your CI's, the more complex and difficulty in managing that level it will be.
_________________
Adam
Practitioner - Release and Control
Blue Badge

"Not every change is an improvement, but every improvement requires a change"
Back to top
View user's profile Send e-mail AIM Address Yahoo Messenger
UKVIKING
Senior Itiler


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

PostPosted: Sat Jul 14, 2007 12:59 am    Post subject: Reply with quote

Like what ARoll said

If the kiosk PC breaks, what gets replaced ?

The whole Kiosk or the PC
One way

Treat the Kiosk like an office
The office has a lan / wan / network gear
The office has an IP subnet or VLAN
The office has a PC/Workstation/Server
The PC/Server/Workstations has Operating System
The PC/S/WS has applications

I would track the O/S as a CI for patches/upgrades
Same for applications
the PC/S/WS is a CI
The peripherals are peripherals - cd rom, monitor etc
The office (Kiosk) is a CI

Link the Kiosk (CI) to the PC (CI)
The PC (CI) to the O/S etc
LInk The PC to the net gear

The PC would either have IP address or a DHCP server linkage
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

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


Joined: Jul 06, 2007
Posts: 8

PostPosted: Thu Jul 19, 2007 4:35 am    Post subject: Reply with quote

Thank you UKViking
Back to top
View user's profile
UKVIKING
Senior Itiler


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

PostPosted: Thu Jul 19, 2007 6:12 pm    Post subject: Reply with quote

No worries

Let me know how the design and implementation of the CI goes
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Guerino1
Senior Itiler


Joined: Jan 01, 2006
Posts: 500
Location: New Jersey

PostPosted: Mon Jul 23, 2007 1:08 pm    Post subject: Reply with quote

Hello CA,

Another way to think of this is that a CI is "anything at all" that you want to track through its "lifecycle".

When we work with enterprises, we get them to identify the "nouns" that are important to them.

If you list the "nouns" that are important to you, you will very quickly come up with a very large list of your CIs.

Note: Always start with the "vaguest" nouns (i.e. your Base Classes) and then start to classify them. We find that the most effective way to do this is by using Object-Oriented Analysis and Design principles as a baseline for "Class" and "Object" identification.

As for the relationships between CIs, good luck. Most enterprises we walk into limit themselves very much, in this area of CfM. The reality is that the permutation of relevant relationships is in the thousands. Defining them takes a significant investment. Implementing and maintaining them takes an even larger investment. Actually, maintaining them can be a huge investment if it's not done correctly. It took us many years to build up the catalog of Relationships we have in our commercial CMDB and that's with dedicated resources to make that happen. Doing it in an enterprise whose business is not CfM can be tough.

Anyhow, I hope this helps.

My Best,

Frank Guerino, CEO
TraverseIT
On-Demand ITIL
Back to top
View user's profile Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Configuration Management 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.