Parent Hardware Model

[rjstefani]

Our organization is working to implement Asset Management within ServiceNow, and about a month ago we had professional services come out and assist us.

During that time we were struggling with how you classify multiple configurations of 1 model. We were under the impression that you needed to create a model for each for configuration (i.e. HP EliteBook 840 G1 w/ an i5 processor would be one model and an HP EliteBook 840 G1 w/ an i7 processor would be another model). After speaking to professional services they informed us that that was incorrect. We should create one model titled EliteBook 840 G1, and then list the multiple configurations of that item on the vendor catalog item.

Since his visit we have been moving forward with professional services advice. However, as we move forward I have discovered the Parent Model field. I'm not exactly sure what the intent of the field is for. Can someone please assist me?

Based on the blogs Know Your Expert | Ben Sweetser created, it appears that we maybe heading down the wrong path based on the advice of professional services. Ben's blog states that each configuration of a model must have it's own model. This leads me to believe that we should have 1 model created called 840 G1 (which would be the parent) and then the multiple configurations of that 840 G1 tie to that parent. Then the vendor catalog items would be created to show the different information pertain to that item and the vendors we procure them from.

Thanks!

[lbless1]

I think both work, it comes down to how you want to report on the data. Ben's method provides for easier reporting.