Please give me steps to make Software compliant.

[akguj]

What are the steps required to make the software compliant, particularly for Articulate Storyline?

Also, could you provide the key points or a checklist/table of criteria that need to be considered to ensure compliance?

Currently, I can see only two entitlements, and Articulate AI Assistant is showing as compliant, while the others are not.

Could you please guide me on how to make the remaining components compliant? 

[akguj]

I could see for Articulate 360 entitlement is not there. But PO is already attached to AI assistant .

[Vikram Reddy]

Hi @akguj ,

I have handled a similar SAM Pro cleanup for a publisher suite, and the key point is this: you do not manually make the software compliant. SAM Pro calculates compliance after the software models, discovery models, entitlements, allocations/subscriptions, and reconciliation data are correct.

From your screenshot, the main reason Articulate AI Assistant is compliant and the other Articulate products are not compliant is that you currently have entitlements only for Articulate AI Assistant. Those rights will not automatically cover Articulate 360, Storyline 360, Replay 360, Peek 360, or Studio 360 unless the entitlement/software model/suite relationship is configured that way.

For Articulate, first confirm what was actually purchased:

- Articulate AI Assistant only
- Articulate 360 Standard / Teams
- Articulate 360 AI
- Storyline 360 standalone
- Any other bundle/suite agreement

Recommended steps:

1. Validate the discovered installs

Go to the software installation/discovery model records for Storyline 360, Replay 360, Peek 360, Studio 360, etc.

Check:

- Publisher
- Display name
- Version
- Discovery model
- Normalization status
- Installed on
- Assigned to
- Active install

In your screenshot, I can see installs where Normalized = false. That should be fixed first because unnormalized discovery models may not reconcile correctly against the software model/entitlement.

2. Validate the Software Models

For each product showing Not compliant, open the Software Model.

Check:

- Publisher = Articulate / Articulate Global, LLC
- Product = correct product
- Version/edition are correct or set to Any Version if appropriate
- Product type = Licensable
- License under management = true
- Discovery map is populated
- Matching Discovery Models show the installs you expect

Use the Matching Discovery Models related list to confirm that Storyline 360 installs are actually matching the Storyline 360 or Articulate 360 software model.

3. Validate whether this should be modeled as a suite

If your purchase is Articulate 360, do not treat every component as a completely separate entitlement unless your license contract says that.

For example:

- Articulate 360 may cover Storyline 360
- Articulate 360 may cover Studio 360
- Articulate 360 may cover Replay 360
- Articulate 360 may cover Peek 360

In that case, the entitlement should be tied to the parent/suite software model, and the component discovery models should be mapped correctly.

If you only create entitlement records for AI Assistant, then SAM Pro will correctly show AI Assistant as compliant but continue to show the other products as not compliant.

4. Create or correct the entitlement

Create/import the entitlement using the correct software model and license metric.

Ensue you set enough rights if the right are greater than consumption the reconcilation will set it as compliant

5. Allocate or import subscriptions if the metric requires it

If the license metric is user-based, make sure the users consuming the software are represented correctly.

Depending on your design, this may be done through:

- User allocations on the entitlement
- Subscription records imported from the vendor/admin portal
- Install records assigned to users, if your metric/model uses assigned installs
- Group allocations, if licensing is managed by group

For Articulate, I would normally compare the Articulate admin console user list with the users in SAM Pro. If the product is licensed per named user/subscription, SAM needs to know who is entitled to use it.

6. Review Installs requiring action

Your screenshot shows a large number of Installs requiring action. Open that list and review the reason.

Common causes are:

- Discovery model not normalized
- No matching software model
- No entitlement for the model
- Missing Assigned to for user-based licensing
- Missing Installed on / bad CI relationship
- Install is inactive/duplicate
- Product is not set up correctly for reconciliation

Resolve these first. If Unlicensed installs is 0 but Installs requiring action is high, the issue may be data/model setup rather than simply needing more licenses.

7. Use Remediation Options

After reconciliation, open:

Software Asset Workspace > License usage > Product Result > Remediation options

Common options are:

- Purchase rights
- Create allocations
- Remove unallocated installs
- Remove unlicensed installs
- Create removal candidates

If users have the software installed but are not licensed, either allocate rights, purchase additional rights, or create removal candidates.

8. Run reconciliation again

After fixing normalization, software model mapping, entitlement, and allocation/subscription data, run reconciliation again for the Articulate publisher.

Then check:

- Product Results
- Software Model Results
- License Metric Results
- Unlicensed installs
- Installs requiring action
- Remediation options

Compliance checklist:

Criteria Required for compliance?
Discovery/install data exists -  Yes, SAM needs usage/install/subscription data
Discovery model normalized -  Yes, otherwise matching can fail
Software model exists -  Yes
Software model is licensable -  Yes
License under management Must be true if you want it reconciled - This is important
Discovery map matches installs -  Yes
Correct entitlement exists -  Yes
License metric matches contract -  Yes
Active rights are sufficient -  Yes
Users/devices allocated -  Required for allocation-based metrics
Subscription data imported -  Required for subscription-based SaaS metrics
Installs requiring action fixed -  Yes, otherwise compliance may remain inaccurate
Reconciliation rerun - Yes, status updates after reconciliation

For your specific screenshot, I would start here:

1. Fix/confirm normalization for Articulate Storyline 360 discovery models.
2. Open the Articulate 360 / Storyline 360 software model and check Matching Discovery Models.
3. Confirm whether your purchase is Articulate 360 or only Articulate AI Assistant.
4. Create/import entitlements for the correct Articulate 360 or Storyline 360 model.
5. If Articulate 360 is a suite entitlement, make sure the component apps are covered through the suite/component relationship.
6. Allocate/import users if the metric is Per User or User Subscription.
7. Rerun reconciliation.

In short: the remaining components are not made compliant from the Product Result screen. They become compliant only when the correct entitlements and license coverage are linked to the correct software models/discovery models and reconciliation is run again.

Try this

Thank you,

Vikram Karety,

ServiceNow Architect,

Octigo Solutions INC