Infographic: How to hit the ground running with Hardware Asset Management normalization

[Michael Scognam]

You've just purchased Hardware Asset Management and are thrilled to normalize your hardware asset estate. Normalization is the process of standardizing discovered asset data to fill in gaps, or correct fields where the manufacturer name, product, or model are inconsistent. Asset visibility starts with data you can trust, and clean data is critical to business agility, strategy, and planning. This document will provide you key steps to achieving strong hardware product model normalization out of the gate.

[klf1123]

Per the PDF, to solve models not normalizing from a discovery source, copy the model number from the end of
the “Short description” and populate it into its real home (the model number attribute). Save the record and
the Normalize hardware model business rule will execute.

So, if I make changes to models created from a discovery source even if the discovery sources lacks certain information won't that source now think the original discovered model is missing and add it again? I am not sure how the "discovered" models are supposed to be "cleansed" to then perform the normalization? Are all the "wrong" discovered models supposed to live in the cmdb product model table rather than a discovered model table? How do the discovered models ever stay "clean" without cause of re-creation from the discovery source? I need more details on the automation occurring without the manual intervention being required.