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.
The Itil Community Forum: Forums
ITIL :: View topic - Defining CI for airport IT infrastructure
Posted: Sat Jul 07, 2007 10:09 am Post subject: Defining CI for airport IT infrastructure
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
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
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"
Joined: Sep 16, 2006 Posts: 3591 Location: London, UK
Posted: Sat Jul 14, 2007 12:59 am Post subject:
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
Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Mon Jul 23, 2007 1:08 pm Post subject:
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.
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