The real problem is not now, it's later when you are mature enough as an organization to start looking at the data in different ways. The more data you have that is not normalized, the more challenges you will have later on trying to get a holistic view.
We allow ADDM full control to create product catalog entries and periodically review any disassociated or duplicated entries to ensure that ADDM is the source of truth not only for object names, but also attributes including product categorizations (and manufacturers). Maintaining a single list of manufacturers will benefit you in the long run, and deciding sooner rather than later to manage them will reduce the amount of effort required to align them all later. .: Mike T :. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rev M Flythe Sent: Wednesday, January 23, 2013 11:24 AM To: [email protected] Subject: CMDB / ADDM Product Catalog Configurations 7.6.4. ** Hi All, We are trying to make some decisions regarding the Product Catalog. We are using ADDM discovery to populate CIs over into the BMC.ASSET dataset. In this version of ADDM - I believe the ADDM Product Catalog is different than the CMDB Product Catalog. The setting is at: "Do not create product catalog entry." "Allow unapproved CIs." We are only normalizing with the CMDB OOB Product Catalog. Since most of the manufacturers from our environment are not listed in the Product Catalog, the CI's are being created in BMC.Asset with all the different manufacturer names within all the classes. Is this good or bad for our business? Should we add the manufacturers to the Product Catalog to normalize these assets or let the CI's remain with different manufacture names throughout the application? What are the advantages/disadvantages of not adding the manufacturers to the Product Catalog for normalization? Our company seems to think that as long as a manufacturer is listed with the CI - for ticketing purposes its OK. It will not affect us. My thoughts were - add the manufacturers to the Product Catalog and normalize it (i.e. future issues if we were to use the software licensing, contract management etc..). We are not using the assets for software / contract management etc... today though. So the thought is ... it does not matter. What are your thoughts? Are there any red flags that we should be concerned about? _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
