Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
If you've ever been in a room with an Enterprise Architect and had to explain ServiceNow SAM Pro from scratch this one's for you.
One question comes up more than almost any other, usually right before a design workshop
"Can you send me something that shows what SAM actually covers? Like a capability map?"
What Is a SAM Capability Map?
It's not a data model. It's not a process flow. It's a structured view of what SAM Pro can do, across domains, grouped by capability - with an honest indication of what works out of the box vs. what needs configuration vs. what needs an integration or Publisher Pack.
Think of it as the one-pager you hand an EA before the architecture review so you're not starting from zero.
The 3 Domains
The map covers three distinct domains:
1. SAM Pro - On-Prem / Perpetual Licensing The core engine. Discovery, normalization, entitlement, reconciliation, optimisation, and governance. This is where 80% of your implementation effort lives.
2. SaaS License Management Connector-driven. OOB connectors for Adobe CC, M365, Salesforce, Okta, Box, Zoom, DocuSign, Tableau, Workday and more. The reconciliation rules are OOB - but they only fire once usage data is actually flowing. Worth calling that out clearly with your stakeholders upfront.
3. Engineering / Complex Licensing Oracle and IBM Publisher Packs. This is where things get interesting - PVU/RVU, ILMT integration, GLAS alignment, Java SE, ULA compliance. Not plug-and-play but genuinely powerful once configured.
