OMT Fulfillment Agent & SPM License Consumption
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Everyone,
I’m looking for clarification on license consumption for users involved in the OMT–SPM integration.
In our environment, fulfillment users are assigned the role:
sn_ind_tmt_orm.order_fulfillment_agent
This role is used by users who perform fulfillment activities on Orders, Order Lines, and Order Tasks.
According to the ServiceNow OMT–SPM integration documentation, this role also contains/inherits:
it_project_user
From the documentation, this appears to be intentional so fulfillment users can access the related SPM Project / Project Task information as part of the OMT–SPM integration.
Our concern is around license consumption.
We currently have 200+ users who inherit it_project_user through sn_ind_tmt_orm.order_fulfillment_agent. However, in Subscription Management, our Strategic Portfolio Management for Telecommunications Professional subscription only shows a much smaller number of allocated users, which appears to match the users in the subscribed SPM groups.
So we would like to understand:
- Does a user with sn_ind_tmt_orm.order_fulfillment_agent consume only an OMT license, or both an OMT and an SPM license because it inherits it_project_user?
- Is the inherited it_project_user access considered part of the OMT–SPM integration entitlement, rather than a separately licensed SPM user?
- Does Subscription Management calculate SPM consumption based on subscribed groups, associated roles, effective inherited roles, or a combination of these?
- If it_project_user is inherited only through the OOB OMT fulfillment role, should those users be considered SPM licensed users for compliance purposes?
- Is there any official licensing documentation or SKU-specific guidance for this OMT–SPM integration scenario?
We want to confirm the expected OOB licensing behavior before making any changes to the role inheritance, since it_project_user appears to be part of the documented OMT–SPM integration design.
Any clarification from someone who has implemented OMT + SPM, or from ServiceNow product/licensing teams, would be greatly appreciated.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi,
Please find some of the answers below:
- Does a user with sn_ind_tmt_orm.order_fulfillment_agent consume only an OMT license, or both an OMT and an SPM license because it inherits it_project_user?
Only OMT. Users need to be licensed separately for both the applications. - Is the inherited it_project_user access considered part of the OMT–SPM integration entitlement, rather than a separately licensed SPM user?
Will get back to you on this. The it_Project_User...is it a child role that you see? - Does Subscription Management calculate SPM consumption based on subscribed groups, associated roles, effective inherited roles, or a combination of these?
No. SPMT is User based at the moment. - If it_project_user is inherited only through the OOB OMT fulfillment role, should those users be considered SPM licensed users for compliance purposes?
Same as number 2. Will get back. - Is there any official licensing documentation or SKU-specific guidance for this OMT–SPM integration scenario?
Each of them individually. But not a "pre inetgrated" pricing guide. But please give us time to sort out the "it_project_user" role.
