Defining CI for airport IT infrastructure

[CA]

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

[CA]

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

[ARoll]

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"

[UKVIKING]

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

[CA]

Thank you UKViking

[UKVIKING]

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

[Guerino1]

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