License profiles user example
The license profile feature is available in version 16.5 Update 16 and later.
See the topic License profiles for basic information about license profiles.
Example situation
A company has three departments which use a single Planning Space tenant. Each department purchases licenses for the needs of its own users:
- Each department wishes to restrict the use of its licenses to members of that department. Except that Department C wishes to allow users in any department to use its PlanningSpace Portfolio concurrent licenses.
- Departments A and C have 'PlanningSpace concurrent' licenses (valid for all of the Planning Space modules) which are to be used only by their own 'power users'. If all of these concurrent licenses are in use then the power users should be able to consume other available licenses.
- Department B wants each user to be assigned both Dataflow and Economics licenses by default at login, because its users always require both modules.
The licenses held by each department are as follows:
- Department A: 3 x PlanningSpace concurrent, 3 x Dataflow Concurrent, 3 x Economics concurrent
- Department B: 4 x Dataflow Concurrent, 4 x Economics concurrent
- Department C: 5 x PlanningSpace concurrent, 5 x Dataflow Concurrent, 5 x Portfolio concurrent
Workgroups
The needs of five users are considered in this example:
- User A1 in Department A - Power User
- User A2 in Deparment A
- User B1 in Department B
- User C1 in Department C - Power User
- User C2 in Department C
The users are assigned to workgroups defined as shown in the table:
Workgroup | Workgroup members |
---|---|
WG_A_Power | A1 |
WG_A_Standard | A1, A2 |
WG_B_Standard | B1 |
WG_C_Power | C1 |
WG_C_Standard | C1, C2 |
Everyone | Default workgroup that all users belong to automatically |
Each workgroup requires the option 'License Profile Workgroup' to be enabled. Workgroups that are already defined for other purposes can be used in license profiles if their user membership is correct.
License profiles
License profiles should be created as shown in the table and the order is critical.
Order | Licence Profile name | Workgroup assigned | Licence(s) assigned | Acquire by Default |
---|---|---|---|---|
1 | LP_A_Power | WG_A_Power | 3 x PlanningSpace concurrent | No |
2 | LP_A_Standard | WG_A_Standard |
3 x Dataflow Concurrent 3 x Economics concurrent |
No |
3 | LP_B_Standard | WG_B_Standard |
4 x Dataflow Concurrent 4 x Economics concurrent |
Yes |
4 | LP_C_Power | WG_C_Power | 5 x PlanningSpace concurrent | No |
5 | LP_C_Standard | WG_C_Standard | 5 x Dataflow concurrent | No |
6 | LP_Portfolio | Everyone | 5 x Portfolio concurrent | No |
'License.SelectionMode' application settings
When the license profiles have been configured, the license selection can be switched over to use 'Profile' mode for the modules involved: for this example all of the module (Dataflow, Economics, Financials, and Portfolio) settings must be changed.
The application settings 'License.SelectionMode' are modified in IPS Server.
Example of license allocation when a user logs in
IPS Server will attempt to allocate a license for a user session for each Planning Space module. If the module has 'License.SelectionMode' set to 'Profile' then the list of license profiles will be processed in the configured order.
One 'PlanningSpace concurrent' license can be used for access to any Planning Space module during the same user session (i.e. if the user gets a license for Dataflow, the same license will grant access to Economics, etc, in the same session). Other licenses are specific to one module.
Note: when Planning Space is launched only the Dataflow module (which also includes Reserves) will be started automatically. Other modules are started when the user clicks the module icons to launch them. However if 'Acquire by Default' is set then the user will be allocated license(s) immediately after the user launches the Planning Space application.
For example: power user A1 logs in to Planning Space and the Dataflow module starts to load; when the load is complete, IPS Server will attempt to provide a license for the user's Dataflow session by processing through the license profiles as follows:
- Check the first license profile 'LP_A_Power': user A1 is a member of the Workgroup in this profile
- If the license '3 x PlanningSpace concurrent' has an unused instance, grant it to user A1 [SUCCESSFUL ASSIGNMENT - EXIT]
- If there is no available license, continue to the next license profile
- Check the next license profile 'LP_A_Standard': user A1 is a member of the Workgroup in this profile
- If the license '3 x Dataflow concurrent' has an unused instance, grant it to user A1 [SUCCESSFUL ASSIGNMENT - EXIT]
- If there is no available license, continue to the next license profile
- Check the next license profile 'LP_B_Standard': user A1 is not a member of the Workgroup in this profile
- User A1 cannot use this profile, continue to the next license profile
- Check the next license profile 'LP_C_Power': user A1 is not a member of the Workgroup in this profile
- User A1 cannot use this profile, continue to the next license profile
- Check the next license profile 'LP_C_Standard': user A1 is not a member of the Workgroup in this profile
- User A1 cannot use this profile, continue to the next license profile
- Check the next license profile 'LP_Portfolio': user A1 is a member of the Workgroup in this profile
- User A1 can use this profile, but there is no Dataflow license included - continue to the next license profile
- There are no more license profiles available [LICENSE ASSIGNMENT WAS NOT SUCCESSFUL - INFORM THE USER - EXIT]