Re: New Product Catalog Data Import - Disappointed!
Some of your observations about Product Catalog data are true. When we analyzed the issue retrospectively, QA spent most energy to verify the update gets installed successfully in customer environments and there was less focus on verifying the quality of the content. Effective measures are now in place to ensure quality of data being shipped. Based on the feedback we received from the field, BMC has now withdrawn the data update and is in process of making corrections to it. Availability of corrected data would be announced separately. I have added comments below to give more clarity on the data update. Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Agree. We are in process of correcting it. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Agree. This should have been captured as alias. Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. As rightly pointed out, this could be debatable what is manufacturer name and what should be alias for manufacturer. As a thumb rule, we will refer manufacturer name with commonly used name like HP for Hewlett-Packard. But again, BMC could have been better captured as BMC Software. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. This is under way. We have taken ITSM best practices to add categorization to each product. v2 and onwards, all the data updates will have this information for all the products. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). For the short/medium term (next 12-24 months), we will focus on Software titles only. We dont plan to add any Hardware/Networking product details in data updates any soon. In addition, we are also trying to simplify the install process for this PC data updates. Currently it involves lot of manual steps. Rahul Vedak, Manager of Product Management, Atrium CMDB, BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
Re: New Product Catalog Data Import - Disappointed!
Excellent points, Peter. Given that this data should be pretty standardized, maybe we could leverage ARS community power to fix this: What about publishing the Product Catalog on a wiki or similar platform where we could all collaborate on it? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Wednesday, June 08, 2011 7:09 AM To: arslist@ARSLIST.ORG Subject: New Product Catalog Data Import - Disappointed! Hi, BMC just released new Product Catalog data based on ADDM discovery data. I was hoping to use this data immediately as we need to reconcile ADDM data with other data sources (HP uCMDB, CiscoWorks and manual audit data). I loaded the data only to find that it looks amateurish. Specifically: Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). The customer here has decided to analyse ADDM data themselves and create Product Catalog, Manufacturers and NE aliases. The BMC data as it stands is as much help as the old DSL data was (did anyone really use this?). Maybe I was expecting too much! Anyone else looked at this? Cheers Peter ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
New Product Catalog Data Import - Disappointed!
Hi, BMC just released new Product Catalog data based on ADDM discovery data. I was hoping to use this data immediately as we need to reconcile ADDM data with other data sources (HP uCMDB, CiscoWorks and manual audit data). I loaded the data only to find that it looks amateurish. Specifically: Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). The customer here has decided to analyse ADDM data themselves and create Product Catalog, Manufacturers and NE aliases. The BMC data as it stands is as much help as the old DSL data was (did anyone really use this?). Maybe I was expecting too much! Anyone else looked at this? Cheers Peter ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
Re: New Product Catalog Data Import - Disappointed!
BMC does have a QA department, don't they? Rick On Jun 8, 2011 6:09 AM, Peter Romain p.romain.arsl...@parsolutions.co.uk wrote: Hi, BMC just released new Product Catalog data based on ADDM discovery data. I was hoping to use this data immediately as we need to reconcile ADDM data with other data sources (HP uCMDB, CiscoWorks and manual audit data). I loaded the data only to find that it looks amateurish. Specifically: Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). The customer here has decided to analyse ADDM data themselves and create Product Catalog, Manufacturers and NE aliases. The BMC data as it stands is as much help as the old DSL data was (did anyone really use this?). Maybe I was expecting too much! Anyone else looked at this? Cheers Peter ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
Re: New Product Catalog Data Import - Disappointed!
IMHO - Lately the BMC QA Department is the customer base :( /IMHO On Wed, Jun 8, 2011 at 4:13 AM, Rick Cook remedyr...@gmail.com wrote: ** BMC does have a QA department, don't they? Rick On Jun 8, 2011 6:09 AM, Peter Romain p.romain.arsl...@parsolutions.co.uk wrote: Hi, BMC just released new Product Catalog data based on ADDM discovery data. I was hoping to use this data immediately as we need to reconcile ADDM data with other data sources (HP uCMDB, CiscoWorks and manual audit data). I loaded the data only to find that it looks amateurish. Specifically: Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). The customer here has decided to analyse ADDM data themselves and create Product Catalog, Manufacturers and NE aliases. The BMC data as it stands is as much help as the old DSL data was (did anyone really use this?). Maybe I was expecting too much! Anyone else looked at this? Cheers Peter ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are _attend WWRUG11 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
Re: New Product Catalog Data Import - Disappointed!
Oh that is a good one Rick. BMC's QA department seems to be more committed to clearing their queue by their deadlines than actually testing and sending bugs back to the engineers. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook Sent: Wednesday, June 08, 2011 6:14 AM To: arslist@ARSLIST.ORG Subject: Re: New Product Catalog Data Import - Disappointed! ** BMC does have a QA department, don't they? Rick On Jun 8, 2011 6:09 AM, Peter Romain p.romain.arsl...@parsolutions.co.uk wrote: Hi, BMC just released new Product Catalog data based on ADDM discovery data. I was hoping to use this data immediately as we need to reconcile ADDM data with other data sources (HP uCMDB, CiscoWorks and manual audit data). I loaded the data only to find that it looks amateurish. Specifically: Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). The customer here has decided to analyse ADDM data themselves and create Product Catalog, Manufacturers and NE aliases. The BMC data as it stands is as much help as the old DSL data was (did anyone really use this?). Maybe I was expecting too much! Anyone else looked at this? Cheers Peter ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are _attend WWRUG11 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
Re: New Product Catalog Data Import - Disappointed!
I guess they could have send it to the list for review/QA :-) From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tommy Morris Sent: Wednesday, June 08, 2011 3:19 PM To: arslist@ARSLIST.ORG Subject: Re: New Product Catalog Data Import - Disappointed! ** Oh that is a good one Rick. BMC's QA department seems to be more committed to clearing their queue by their deadlines than actually testing and sending bugs back to the engineers. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook Sent: Wednesday, June 08, 2011 6:14 AM To: arslist@ARSLIST.ORG Subject: Re: New Product Catalog Data Import - Disappointed! ** BMC does have a QA department, don't they? Rick On Jun 8, 2011 6:09 AM, Peter Romain p.romain.arsl...@parsolutions.co.ukmailto:p.romain.arsl...@parsolutions.co.uk wrote: Hi, BMC just released new Product Catalog data based on ADDM discovery data. I was hoping to use this data immediately as we need to reconcile ADDM data with other data sources (HP uCMDB, CiscoWorks and manual audit data). I loaded the data only to find that it looks amateurish. Specifically: Data has the first character as upper case and the rest as lower. This means that we see companies like Bmc, Ibm, Hp, etc. The product name data is also the same. For reports this won't look good. Then there are exceptions and possible duplicates such as the inclusion of both 'Network associates' and 'Networks Associates' (note the capital 'A'). Although open to debate the customer here thinks the normalisation aliases are the wrong way around for companies like BMC (BMC Software converts to BMC), HP (Hewlett-Packard converts to Hp), etc. The Tier 1-3 values are all the same. A suggestion of possible values would have been good. The data only includes Product class data. The opportunity to include other classes has been missed (but I hope will come later). The customer here has decided to analyse ADDM data themselves and create Product Catalog, Manufacturers and NE aliases. The BMC data as it stands is as much help as the old DSL data was (did anyone really use this?). Maybe I was expecting too much! Anyone else looked at this? Cheers Peter ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.orghttp://www.arslist.org attend wwrug11 www.wwrug.comhttp://www.wwrug.com ARSList: Where the Answers Are _attend WWRUG11 www.wwrug.comhttp://www.wwrug.com ARSlist: Where the Answers Are_ _attend WWRUG11 www.wwrug.comhttp://www.wwrug.com ARSlist: Where the Answers Are_ Blue Turtle Technologies (Pty) Limited | Reg. no.: 2003/002610/07 | Tel: +27 (0)11 206 5600 | Fax: +27 (0)11 206 5606 | http://www.blueturtle.co.za Midridge Office Estate, International Business Gateway, cnr New Road Sixth Street, Midrand, 1685 | P O Box 31331, Kyalami, 1684 DISCLAIMER: This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication represents the originator's personal views and opinions, which do not necessarily reflect those of Blue Turtle Technologies (Pty) Ltd. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
