My question is on how Configuration Management interacts with Software Asset Management and the DSL. I would like to know how people have setup the use of the CMDB and DSL and how these 2 fit together. I would also like to know how/who updates these areas.

My take is that CI's in my CMDB will have a relationship(s) to software held in the DSL. The DSL is updated through Change Management i.e. if the software version of a product changes from version 1 to version 2. The CMDB is then automatically updated because of its relationship to the DSL.

My area of work is with Configuration Management so my knowledge on SAM is very little at the moment. We do have a process owner in place for SAM and currently have a DSL in the form of a spreadsheet.

Any advice on this area would be much appreciated and working examples of how its been successfully implemented in the real world would be great!

Thanks in advance and look forward to contributing to other topics I do have knowledge on!

My question is on how Configuration Management interacts with Software Asset Management and the DSL. I would like to know how people have setup the use of the CMDB and DSL and how these 2 fit together. I would also like to know how/who updates these areas.

This is not a simple question to answer. In some cases you will have loose references between the CMDB and CIs in the DSL, based on names, associated IDs, etc. In other cases, you will have path references, from the CMDB that point directly to things in the DSL. This latter one will allow you to drill into live details on the DSL, directly from the CMDB.

Quote:

My take is that CI's in my CMDB will have a relationship(s) to software held in the DSL. The DSL is updated through Change Management i.e. if the software version of a product changes from version 1 to version 2. The CMDB is then automatically updated because of its relationship to the DSL.

This will work in some cases, but not in all. Please note that you will also have to "triangulate" references and associations between the CDMB, the DSL, and your Source Code Control System, which will also contain versioned CIs and is critical for proper SW CfM.

It's true that in some cases, your Change Management process will update the CMDB but please keep in mind that there are so many other processes that will update it, too. Checking In or Out SW, building SW, distributing SW, etc. should all also update the CMDB as part of their workflow.

Quote:

My area of work is with Configuration Management so my knowledge on SAM is very little at the moment. We do have a process owner in place for SAM and currently have a DSL in the form of a spreadsheet.

SW CfM is a huge and very complicated space, this is why a CMDB, as referenced by ITIL for infrastructure purposes, is highly limited and incomplete. Be careful as you attempt to build out your solution. If you don't design it properly, you may seriously run the risk of crippling how your SW teams (both development and engineering) work.

Is there anything other then DSL interesting for you in the relationship between CfM and SAM?

Configuration Management and IT Asset Management (both Software and Hardware) have just different view on the same subject. Relationship between them is a long story and it is hard to talk about it without focusing on the specific area.

There is a SAM book in ITIL v2 you can read if you want to know more. you can also check ITAM best practices gathered by IAITAM or get training from them._________________Krzysztof (Chris) Baczkiewicz
IT Standards Support
Eracent

DSL may also include a physical store to hold master copies of bought in software, such as fireproof safe

Should be in several locations.

CMDB:
A database that holds logical and asset information of CIs - hardware and software.
It gives relationship of CIs, version numbers for software etc.
This is a logical versus physical store.

I am not sure how DSL can be stored in excel sheets as I read, so require some more clarification to have the idea clear.

I would put it like this: Consider a Book Library the physical shelves that have the books arranged is equivalent to the DSL and CMDB is like the index of where the books are, and details of author, version, copyright etc.
You can walk into the DSL so it is like a store house. CMDB can be accessed online as this is a record of information only. CMDB will interface into other applications used by the ITIL management groups.
DSL does not have to interface with anywhere as it is a warehouse of original software components etc._________________Ranjith Raghunathan
ITIL Foundation Certified

P.S - Most of my posts are to understand the ITIL fundamentals clearly. So please excuse if not genuine answers to questions.