We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Please provide steps to make the software complaint from screenshot.

akguj
Tera Contributor

 

I want to make software complaint in SAMPRO and attached screenshots of the data from the relevant tables. Please review them and let me know the steps I should follow so I can use the same process for other software complaints. Let me know if you need any additional details.

 

 

M1.pngM2.pngM3.pngm4.pngM5.png

3 REPLIES 3

pr8172510
Kilo Sage

 

Hi @akguj ,

From your screenshots, the product is showing Not compliant because installations are getting counted, but entitlement/license reconciliation is not matching correctly.

 

Steps to Make Software Compliant

  1. Verify Software Model
  • Open Software Model:

 

Altair Engineering Monarch Complete
  • Ensure:
    • Product type = Licensable
    • License under management = Checked
    • Discovery model mapped correctly
  1. Verify Discovery Model Mapping
    Your installations:
  • Monarch 2023
  • Monarch 2024

must match the same discovery model used in Software Model.

  1. Check Software Installations
    Go to:

 

Software Installations
Verify:
  • Publisher = Altair Engineering
  • Product normalized properly
  • Install status active
  • Installation counted in reconciliation
  1. Verify Entitlement
    Open:

 

Software Entitlements
Ensure:
  • License metric = Per Named User
  • Rights count is sufficient
  • State = In use
  • Active rights >= installs
  1. Run Reconciliation
    Navigate:

 

SAM Pro → License Workbench
Then:
  • Open product result
  • Click Reconcile or Run Reconciliation
  1. Check User Allocation
    For Per Named User licenses:
  • Installations should have Assigned to populated
  • Empty Assigned to may cause non-compliance
  1. Verify Downgrade / Upgrade Rights
    If entitlement covers:
  • Monarch Complete

but installs are:

  • Monarch 2023
  • Monarch 2024

then ensure:

  • Upgrade rights are configured
    OR
  • Product use rights are mapped correctly
  1. Recalculate Compliance
    After updates:

 

SAM Pro → Content Service → Reconciliation

Run reconciliation again.

Usually compliance issue occurs because:

  • Assigned to is empty
  • Discovery model mismatch
  • Entitlement rights lower than installs
  • Upgrade rights not configured

akguj
Tera Contributor

Hello @pr8172510 
Thanks for your reply.

If the assigned to field is empty on installation table then it will affect compliance correct?

Hi @akguj,

Yes, you are  correct. If the Assigned to field is empty on the Software Installation table, it Will  affect compliance, especially for Per Named User license metrics.