What is the Model Number field for exactly?

[klf1123]

When I took the Asset Management training it sounded as if the Model Number field was used for Manufacturing Part Number. However when we implemented with BDNA they used this field for the generic Model Number and so then I was wondering where the manufacturing part number should go? It appears in the tool that within the Vendor Catalog that Product ID is also listed as manufacturer part # though in the training I think that was said to be the vendor part# so that would make sense since its the vendor catalog.

The example in the SN training manual:

        Manufacturer: Hewlett Packard

        Name: HP LaserJet Printer M551dn

        Model Number: CF082A

Model from BDNA

        Manufacturer: Hewlett-Packard Company

        Name: LaserJet Enterprise 500 Color M551dn

        Model Number: M551dn

So where do I put the manufacturing part number if I use BDNA and I still need to capture the vendor part#? Why are these fields not distinctly called out in ServiceNow so that its more clear?

[Mike Allen]

In the OOB configuration, Model Number on model and Product ID are the same numbers, so, that leads me to believe that these two fields are meant to track the same information.

[Community Alums]

I cannot speak to why BDNA chose to use this as the Model number. If the Display name concatenated the Name and number, I might consider this to be appropriate and then have a separate field for Manufacturer part number, but this does not happen. This makes it feel redundant in ways that are not clear to me. I am reaching out to some folks who might know why.

As for approaches:

• Does BDNA provide the Manufacturer part number elsewhere or is it just unavailable?
• If it is elsewhere, you could go with the alternate field.
• If it is not elsewhere, you could override with the Manufacturer part number or create a Manufacturer part number field.

I'll let you know what I find out.

Ben

[klf1123]

BDNA does not provide the data somewhere else since they are only concerned with the model name normalization. I cannot override it because the Technopedia is loaded on a schedule and will overwrite the data on the next run. My thought with the integration being certified would be that ServiceNow agreed for the use of that field since in other portions BDNA created their own fields. However they then did not allow for the data to be placed somewhere else. This is causing an issue with trying to integrate the Service Catalog through to a Request and then to a PO. We have to use the Vendor Catalog to try to differentiate the products in the Catalog which is not OOB.

[klf1123]

Hi Ben - Have you heard anything else with regards to the model number field? Still have this question open. Thanks.