November 13, 2008

Determining the CMDB span (part 2 of 3)

Posted in CMDB tagged , , at 3:36 pm by Molly

In part one of this series, we discussed the CMDB scope and how you can accomplish what the required categories and relationships you would include to start to plan your CMDB.  Let us look at the SPAN criteria for the CMDB.

What does the dictionary say about SPAN – “distance, full extent, the reach of anything“.  In our case, we shall describe span as an indication of the specific groups that will be tracked for each of your objects that you have already defined in the SCOPE, in other words the boundaries of our definitions.  So I hope by now that you have some idea of your scope.

Your boss: “forget span, can you just gather all the data you can find and we shall use this in the CMDB”

You: “but … where shall I start?”

As you see from this conversation that is very typical in our IT environments.  Where do you start?  What are your boundaries?

IDENTIFY WHICH CIs WILL BE STORED IN YOUR CMDB AND WHICH WILL NOT is always a good starting point in my opinion.

Example: an online news broadcaster may decide that the editorial team and the web development teams’ iMacs are more critical than those from the HR office.  They would be right to some degree, but don’t go asking the HR manager!  So define your critical CIs correctly to begin with will reap benefits later on in the architecture of your CMDB.

Span important facts:-

  • Span your projects – you’ll never populate your CMDB in one single swoop, so phase it out, split it into stages;
  • Dictated by tools;
  • Understand the risks;
  • Document it;

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: