<h2>Query - Software Model table and Software Discovery Model tables</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>Understand if there is a connection between the <strong>Software model table</strong> and <strong>Software Discovery model tables </strong>?<br /><br /></li><li>Does the <strong>Software model table</strong> have any impact on the <strong>Software Discovery model table</strong> and by that to the discovered installed softwares ?</li><li>We use software model table for our request management and the Software discovery model & installed software tables are populated from external discovery sources as part of the CMDB and would like to understand if these tables have any rules or scripts that we need to consider.</li></ul></section></div><div ><h3 >Release</h3><section><ul style="list-style-position: inside;"><li>All</li></ul></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>Discovery models are auto-populated with <strong>install table</strong> during the Discovery process, which is a specific piece of software installed on the CI.<br /><br /></li><li>Then Discovery Models will be normalized according to content library. This means each install record will auto-generate a Discovery Model if there’s not an existing one. And each Discovery Model can be associated with multiple install records.<br /><br /></li><li>While Software Model is a model that is available to users which can be purchased, where various entitlements associated with the Software Models need to be created by the customer.<br /><br /></li><li>If you open up a Software Model record, there is a “<strong>show matching Discovery Model</strong>” link, which will display all the associated Discovery Models, meaning multiple Discovery Models can be associated with one Software Model.<br /><br /></li><li>For example, a generic software model Adobe Photoshop (version = anything) will find various versions of Adobe Photoshop Discovery Models. The parameters created for Software Model (version, edition, platform, language) will define the filters when finding its Discovery Models.<br /><br /></li><li>During our reconciliation process, we look into one software model and its entitlements, then track through its Discovery Models to install records, then license those installs.<br /><br /></li><li>The Software Model has a <strong>Discover Map</strong> (DMAP).<br /><br /></li><li>The <strong>DMAP</strong> dictates which Discovery Models will be mapped to the Software model during the reconciliation process.<br /><br /></li><li>It is recommended to use the DMAP provided in the content library, however customers can create their own.<br /><br /></li><li>Software Install Conditions can also be used to specify conditions that need to be met for an install to be mapped to a Software Model.</li></ul></section></div><div ><h3 >Related Links</h3><section><ul style="list-style-position: inside;"><li>For more details please refer the product documentation on Software Asset Management here below<br /><br /> <ul style="list-style-position: inside;"><li><a title="Discovery Model" href="https://docs.servicenow.com/csh?topicname=c_DiscoveryModels.html&version=latest" rel="nofollow">Discovery Model</a><br /><br /></li><li><a title="Software Model" href="https://docs.servicenow.com/csh?topicname=c_SoftwareAssetMgmt.html&version=latest" rel="nofollow">Software Model</a></li></ul> </li></ul></section></div></article></div>