SAM suite inference links unrelated software models through Microsoft downgrade rights chain<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue The SAM suite inference engine may infer software models (e.g. Microsoft Windows 10) into suites they do not directly belong to (e.g. Microsoft Visual Studio with GitHub Professional) due to the downgrade rights chain from the Enterprise edition. Symptoms Software models appear under unexpected suites in reconciliation resultsMicrosoft Windows 10 installations counted under Visual Studio Enterprise entitlementSuite inference results include products with no direct suite child relationshipReconciliation shows unexpected license consumption for suites Cause The SAMSuiteEngine runs two stages: Build suite structure from cmdb_m2m_suite_model and entitlementsInfer best suite via ranking rules Rule 4 (tiebreaker) prefers the suite with the lower downgrade-rights count. The downgrade rights chain spans three tables: samp_dmap_downgrade_model (source from content service)samp_sw_downgrade_model (consolidated)Entitlements The scheduled job SAM - Create downgrades/upgrades for a software entitlement walks the downgrade map. Suite children edges (cmdb_m2m_suite_model) and downgrade edges (samp_sw_downgrade_model) are separate tables, but the inference ranking algorithm uses downgrade-rights depth as a tiebreaker. This causes the downgrade traversal to pull Windows 10 under Visual Studio Enterprise via the downgrade chain during ranking, even though Windows 10 is not a direct suite child. Resolution This is expected behavior based on the downgrade rights model in the content library.To control which installations get counted under a specific suite, use Product Install Conditions (samp_sw_product_install_condition) to filter which installations are eligible for suite membership.Review the downgrade rights chain for the affected suite: navigate to samp_sw_downgrade_model and trace the path from the Enterprise edition to the base product.If the inference is producing incorrect results for your licensing compliance, contact your SAM administrator to adjust the Product Install Conditions for the affected suite.