The below data model diagram provides a high level data model followed by SeviceNow SAM Pro. This would help SAM managers and analysts understand the various data objects on SAM Pro and how data flows between them.
1 These are data objects that are created automatically. For examples software installs and discovery models are created automatically with no manual intervention
2 These are data objects that can be created manually or automatically. For example: When integrating with SaaS Portals or while entering PPN the software models are created automatically. However, they can also be created manually
3 These are data objects that are mostly created manually. For example Entitlements are either entered manually, or through a template/contract
4 These are data objects that are created as a result on running SAM Reconciliation and are dependent on the main data objects i.e. software installs, software subscriptions, software entitlements and software models
Explanation of the data flow
1 – 2. Software Discovery, Normalization, Entitlements & Software Models
Client / Server / Engineering software
- Discovery sources such as ServiceNow Discovery, SCCM, and others detect software installations on different infrastructure resources such as Virtual machines, client machines etc. and automatically create Software Installation records in ServiceNow.
- Software installation records auto creates/link to a Discovery Model, which is then used by the Normalization Engine to standardize publisher, product, and version information.
- Regular content updates from ServiceNow add enrichment data—life-cycle details, downgrade rights, suite membership, and more.
- When purchase entitlements are entered, the related Software Models are either created automatically (via PPN) or linked manually
To understand more about Installs and Discovery models check here
To understand more about software entitlements and software models check here
SaaS software
- Through SAM Pro SaaS integrations, subscription data is imported directly from SaaS portals (e.g., Microsoft 365, Adobe, Zoom) into Subscription records.
- These subscription records automatically generate the corresponding Software Models to which entitlements can be linked.
To understand SAM Pro support on SaaS Software check here
Discovery Maps or DMAPs connect the purchased side (entitlements via Software Models) with the deployed side (installs via Discovery Models). They are the foundation for compliance and optimization calculations performed by the SAM Pro reconciliation engine. To view more details check this video here
3. Reconciliation & License-Compliance Results
- Reconciliation can run on-demand or by schedule. The engine compares entitlements, installs, and subscriptions against each publisher’s licensing rules—no manual intervention required.You can check the video to understand more about this here
- Results surface in three tiers: Product, Software Model, and License Metric. Please read about it here
- From these results SAM Pro produces a License Compliance Position: how many licenses are owned, how many are required, and the resulting compliance status. Please read about it here
- Built-in optimization identify cost-savings opportunities (e.g., Microsoft license optimization read about it here).
4 and 5 . Remediation actions
Finally based on reconciliation, SAM pro generates remediation options that provide various remediation options to the SAM manager. For example Purchase more rights or remove unlicensed installs if you are non compliant. Read more about it here.
Based on the remediation options, if removal of software install is taken the system auto generates a reclamation candidate workflow on servicenow that can be integrated with external sources to actually remove the software. Read about it here
Data Objects that Need the Closest Attention include:
- Subscriptions – Imported from SaaS portals; accuracy drives SaaS compliance.
- Software Installations (with Normalization) – Discovered installs must be normalized for correct compliance results.
- Software Entitlements – Purchase data has to be complete and correct.
- Software Models – Define specific versions/configurations and carry licensing logic; keep them tuned for accurate compliance and optimization.
Stay tuned—upcoming posts will dive into best-practice maintenance for each of these critical data objects.
2 Comments
