My point was more towards what should be provided by BMC rather than what a specific company should store.
As with all things Remedy, supply the generalized then through workflow/configuration choose what you need within it. In the end you want to identify software coming in through disparate discovery systems, along with possible manual entry subject to error and subsequently enforce corporate standards. I would rather have an overly large list of possible software for the identification phase. I'll let ITIL gurus, I only have the green pin, argue the finer points of process detail. .... Daniel -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: December 21, 2006 9:40 AM To: [email protected] Subject: Re: What is Definitive Software Library (DSL)? and Updates downloadable Actually, I think it is very much not intended to be "all software known to mankind". Rather, from just a few quick pokes around google there are abundant statements like the following: " The practice of effective Software Control & Distribution involves the creation of a Definitive Software Library (DSL), into which the master copies of all software is stored and from here its control and release is managed. The DSL consists of a physical store and a logical store. The physical store is where the master copies of all software media are stored. This tends to be software that has been provided from an external source. The logical store is the index of all software and releases, versions, etc. highlighting where the physical media can be located. The logical store may also be used for the storage of software developed within the organization. SC&D procedures include the management of the software Configuration Items and their distribution and implementation into a production environment. This will involve the definition of a release programme suitable for the organization, the definition of how version control will be implemented, and the procedures surrounding how software will be built, released and audited. " So it sounds like the DSL is not just a list of software titles, but it is also the actual "approved" software for use at Company "X". So unless BMC is providing "all software known to mankind" in the download, it really does not sound like it is appropriate for all of the logical (list) of "all software known to mankind" to end up as CI's for every CMDB out there. (So there has to be some filtering specifically for each implemented CMDB.) In fact it almost sounds like the first step is really the business deciding that it will use "software X" and then trying to find if it exists in anyone DSL. If so, then add it to their CMDB in like fashion. If not, then invent a new CI and contribute it back to the "greater DSL in the sky". Or is this topic just one of those ITIL classes that I have not yet been too? Anyone know if BMC has asked/told Malcom Fry about the ARSList? (If anyone has his email address... let's see if we can get him to subscribe for such ITIL questions. :) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
