CMDB modeling: Software as an attribute, not as a CI

[ChasingSleep]

Hi guys,

We are in the planning phase of a conf mgm prc implementation.

We are considering two possibilities for the software:

1) To consider a software as a CI, with relationships to where it is installed (PC) and with its license.

2) To consider a software as an attribute of a PC CI. This way we could simplify the whole thing (less relationships), and we could still control license usage by counting attributes (tool automated).

I think option 2 quite interesting, but I do not remember seeing this kind of modeling around. What do you think? Have you ever worked this way?

Regards

[mnsmith]

Hi

It's really up to what you want to get out of a CMDB and if you are comfortable having software as an attribute, then that's fine by me. However, here are a few things you might want to think about:

- are there any attributes you want to store against software, for example the physical location of the installation CD? If so, it will make life easier have a software CI, so that you don't have to duplicate this information on every PC CI.
- when rolling out new software, will it be easier for you to updated each PC CI with the new software or just update the one software CI to link to all PCs? You may not know this yet if you've not selected a tool but if you have, you might be limited by what the tool can (and cannot) do.

Hope that helps

Mick Smith
_________________
Mick Smith
Change, Configuration and Release Manager

[pel]

Seems doable.
However, this would mean that you'd have one attribute for each software and software version that you've deployed.

If your CMDB can handle that many different object types (would make many otherwise simliar CIs different due to software), either that or you would break the first normal form (leads to issues when searching - among other things).

Edit: I.e. - no, that does not seem like a very good idea. But as UKViking says - it depends.

[UKVIKING]

There is a thread (recent) in which I describe how I would create SW as a CI

But you can ignore that if you wish
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[ChasingSleep]

Thank you guys, it seemed like a good ideia, but you raised some interesting issues... I'm gonna take a closer look at this.

And UK, who am I to ignore any of your posts...

[UKVIKING]

Well if you are chasing sheep, you would miss me .


Wait.. it is Chasing Sleep not... sheep

Well baaa on my part

giggle
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter