1

Software Support Licensing at CLS

User Guide

2

History of Change

Ver. Released Author Changes

1.0 2014-12-22 Cigdem Oestanas Initial Creation – Chapter 1

1.1 2014-12-25 Taylan Sen Screen Shot Updates, Chapter 2 and Chapter 3

1.2 2014-12-30 Alfons Geier Introduction, Glossary and additional corrections.

1.3 2015-01-07

3

Table of Contents 1) Glossary ................................................................................................................................................. 4

2) Introduction ........................................................................................................................................... 5

3) Use case Transferring and activation of ordered/ unused licenses ...................................................... 7

a) System licenses and SSP licenses are ordered via one distributor in one order. .................................. 7

b) Product and SSP are ordered separately via one Distributor ............................................................. 22

c) Product and SSP are ordered separately via two Distributors ............................................................ 26

4) Use case: Renewal ............................................................................................................................... 28

a) Before Expire Date on CLS ................................................................................................................... 28

b) During renewal period ........................................................................................................................ 31

c) Re-Contracting / Re-Activation: ........................................................................................................... 39

5) Use case: Expansion ........................................................................................................................... 40

a) Before Renewal Period ........................................................................................................................ 41

b) During Renewal Period........................................................................................................................ 49

c) After Contract Expired ......................................................................................................................... 57

4

1) Glossary CLS: Central License Server

CLS –ID: The CLS-ID is a unique identifier at the Partner Service Contract Portal.

ERM system: is Unify’s SAP system

F-Numbers: F-Numbers are licence numbers for products but also for contracting a system for Software

Support (co-delivery) v2. They are further used for renewing the contract. The F-nrs can be seen at the

accounts at CLS.

LAC: License Activation Code to activate the Service contract for Software Support.

PSC: Partner Services Contract Portal.

PCM: The Partner Services Contract Database (PCM) is the database for the Partner Services Contract

Portal (PSC).

SIEL-ID: is a unique identifier which is assigned to each base license.

SSP: Software Support

5

2) Introduction Software Support is a service provided by Unify to its approved Partners.

To be able to get the service for a system, it has to be under service contract.

A service contract is established for a system if Software Support Service specific order items are ordered

and assigned to a system.

To be able to assign the service order items to a system these items are converted at the ERM systems to

service specific licenses (F-numbers) which are then transferred to the Central License Server (CLS) which

is Unify´s License Management tool.

At the CLS the service specific licenses have to be assigned to a system by matching to base and user /

feature licenses the fitting amount of service licenses.

Some general rules have to be kept in mind

-The service licenses are used for both contracting a system for Software Support and for renewal of the

service contract.

-The service licenses are matching to base and user/ feature licenses of systems and are handled at CLS

exactly like system base and user / feature licenses. So these licenses are also named service base

license or service user license

-Latest at CLS a unique identifier (SIEL-ID) is assigned to each base license. This makes each system

uniquely identifiable, which is important for further handling e.g. the usage of Ticket Management,

Expert Assistance, renewal etc. Also for the service base license an own SIEL is assigned.

-Because Service and System licenses provide own SIEL ID´s, with activation the service Siel is

overwritten by the system Siel (Base license). This is to have a unique identifier for a system. Therfore als

at the Partner Contract portal the SIEL if service base licenses is converted to the system Siel with

activation

-Service licenses fitting in type and amount must be matched to the system account at CLS

• If not fitting the SSP contract is not accepted and an error message is shown

• If a system is under SSP then system expansion (adding system licenses) can be done only

together with expansion of SSP contract (adding the fitting SSP licenses)

• Same applies for renewal

6

-It is important that System and SSP licenses are transferred to the End customer account. Only then

the SSP contract is valid

-SSP contract is only properly created if the transfer process is followed:

Unify account -> Distributor / Reseller account -> End customer account

The following chapters now describe in detail the handling of system and SSP licenses in various use

cases and steps.

The first use case describes how a system is taken under contract (either if ordered newly or also for

installed base).

The second use case describes how a service contract, which will expire during next 90 days is renewed.

The third use case describes how a system under service can be expanded.

7

3) Use case Transferring and activation of ordered/ unused licenses

a) System licenses and SSP licenses are ordered via one distributor in one order.

An order is transmitted to the CLS in one LAC as the System licenses and SSP licenses were ordered

together. The licenses are ordered via XX and location on the XY account. Before the licenses can be

activated on the according account, they need to be transferred. As a result the ownership of the

licenses change. The current license owner will become the Partner Company of the transferred licenses

and the selected New Owner Company will become the Sold-to company.

Note: You can only transfer licenses that have neither been used for license key generation nor have

already an End User Company assigned.

Example:

LAC 1 consists of:

F31505-K147-C1 OS Voice V8 Base

F31505-K147-C4 OS Voice V8 UC Server

F31505-K147-C2 OS Voice V8 Dynamic User

F31505-K147-C7 S Voice V8 SuSE 3 Year Upgrade Protection

F31505-K148-A512 SSP for OpenScape Voice V8 Dynamic User Contract

F31505-K148-A511 SSP for OpenScape Voice V8 Base Contract

8

Image 1.a.1 - View License Assets – Licenses Delivered

TRANSFERRING THE LICENSES: The Distributer logs into his CLS account.

1. Select the Transfer Licenses menu item.

2. Enter the License Authorization Code (LAC).

3. Enter the Partner Company to the Current License Owner field and click SEARCH.

4. The search result will only show licenses that do not have already an End User Company assigned

and still have available Quantity (un-used). If you tick the check box next to the Product name, all

contained features are selected. You can deselect features which you do not want to transfer by

un-ticking the checkbox next to the feature name

9

Image 1.a.2 – Transfer Search

10

5. Select the licenses to be transferred and click TRANSFER

6. At the Transfer Menü:

a. First the New Owner Company has to be set. Either you enter the name or search for the

company (by using the magnifier glass).

b. Then check the “LAC Generation Rules” section. Here you can choose the method how

the LAC for the transferred licenses is defined. If you want to transfer all licenses linked

to a LAC, you can use Keep existing LACs.

c. Otherwise the best choice is to let the system generate a LAC for you (Create new

system-generated LACs - 1 LAC for this transaction).

d. If you do not want to transfer all licenses linked to the LAC, use the “Licenses to

Transfer” section. Click onto the “Plus icon” to open this section.

e. In the “Licenses to Transfer” section you see all selected licenses with their available

quantity. If you only want to transfer a partial quantity, change the values in column

Quantity to Transfer appropriately.

f. In section “Header Information” you can assign the properties Sales Order #, Delivery

Note # and Purchase Order # to the new LAC.

g. It is possible to download or receive via email a comma separated list with the generated

new LAC(s) via email or download. This is controlled in section “LAC Delivery Rules”.

h. As an optional way you can trigger an email that informs and invites the new license

owner to the CLS After providing all data click NEXT.

11

Image 1.a.3 – Transfer Target Company Selection

12

7. On the confirmation page you may enter Customer Notes. Please verify the entered settings. If

the data is correct click FINISH.

Image 1.a.4 – Transfer Confirmation

8. As result of the transfer, the license quantity of the original licenses will be decreased and new

licenses will be created. Once the license transfer is complete, click the Enter another Transfer

button to start a new transfer workflow if required.

13

Once the licenses are located on the Reseller Account ( CLS terminology: SOLD TO account). The reseller

log onto CLS and has to perform the Transfer Process to the account of XXXX.

Activation Process:

1. Select the Generate and download license keys menu item.

2. Enter the LAC as the search criteria and click SEARCH

Image 1.a.5 – Search for the Licenses to be Activated – Activation with SSP – Contracting

3. Select Product and Feature that you want to activate click Generate Key

Note: The SIEL IDs for base and SSP base SIEL IDs are different.

4. Enter details to generate the license key

a. Locking ID (MAC address) of the target hardware

b. Quantity of licenses

Optional: Enter Alias Name of the target hardware (any title to identify the computer) and

click NEXT.

14

Note: When activating the licenses, you MUST obey to the rules of the license structure. If not, the CLS

will not allow the generation of the licenses and an error message will be shown. Here are some

examples:

Image 1.a.6.1 Regular System Activations – Rules must be obeyed according to specific

product settings.

15

Image 1.a.6.2 Activation with SSP – Rules must be obeyed according to specific product

settings and SSP settings.

16

Image 1.a.6.3 – SSP Licensing General Rule Warnings – Initial Activation – Contracting

17

5. Check/change/select the license owner and click NEXT.

Image 1.a.7 – Registered Company and User Info (End Customer Information)

18

6. Check the data on the confirmation page and click FINISH.

Image 1.a.8 – License Activation Confirmation

19

7. Now the license key can be downloaded.

Image 1.a.9 – Click to view and download generated license key.

Note: After the generation of the System licenses and the SSP licenses the SIEL ID of the SSP licenses will

be overwritten by the System license SIEL ID. This replacement process may take time to be processed by

CLS. License must be checked later using the “View Used Licenses” menu step.

View used licenses:

1. Select the menu: License or homepage and license management center: View used licenses

2. Enter search criteria (Locking ID, System ID , Alias Name) for the licenses enter SEARCH

3. Select licenses from the search result list and click VIEW DETAILS

20

Image 1.a.10 – View Used Licenses - Search

21

Image 1.a.11 – View Used License Details – Expire Date on CLS stands for the Renewal Period Start Date,

which is equal to 90 days before real service contract expire date on PCS.

Note: CLS expiry date is shown (= 90 days before real service (SSP) contract expiry date on PCS). This is

the start date for renewal period.

22

b) Product and SSP are ordered separately via one Distributor

Example:

LAC 1 consists of:

F31505-K147-C1 OS Voice V8 Base

F31505-K147-C4 OS Voice V8 UC Server

F31505-K147-C2 OS Voice V8 Dynamic User

F31505-K147-C7 S Voice V8 SuSE 3 Year Upgrade Protection

LAC 2 consists of:

F31505-K148-A512 SSP for OpenScape Voice V8 Dynamic User Contract

F31505-K148-A511 SSP for OpenScape Voice V8 Base Contract

Image 1.b.1 – View License Asset - Product’s order that is delivered to Distributor

23

Image 1.b.2 – View License Asset - SSP order that is delivered to the same Distributor with a different

LAC

The distributor needs to perform the steps of the transfer process as shown in previous section and

transfer the licenses from the distributor account to one reseller account. Reseller then may activate as

again described in the previous subsection.

It should be stated that the regular process is that licenses will be shifted together to reseller and then to

the end customer account and activated there

Activation is carried out like it is described in the previous subsection. However, please note that more

than one LACs may also be combined and used during an activation of the system since the orders are in

separate LACs, or also SSP licenses may be activated later separately in order to contract the system

after the system has been activated.

24

Image 1.b.3 – Generate License Key – Selection of more than one LAC – Click on “Click here to add more

LACs”

Image 1.b.4 – Generate License Key – Add More LACs – Enter the LACs to be combined and activated and

press Save

25

Image 1.b.5 – Generate License Key – Select the licenses and proceed, rest is a regular activation process

for CLS

26

c) Product and SSP are ordered separately via two Distributors

Image 1.c.1 – View License Asset - Product’s order that is delivered to the first Distributor

27

Image 1.c.2 – View License Asset – SSP Order delivered to different Distributor

28

4) Use case: Renewal

Renewal is the process of renewing the Software Support Contract by extending the amount of contract

duration over the original contract expire date. It can only achieved during renewal period. Original

contract expire date on PCM and Renewal start date on CLS actually move forward by the amount of

duration contract. For example for annual duration contracts, if the renewal is carried during renewal

period original expire date and renewal start date moves one year forward.

On CLS the date which is shown as “Expire Date” refers to “Renewal Period Start Date” due to internal

mechanics. Expire date shown on CLS, the “Renewal Period Start Date”, is 90 days before the original

contract expire date on PCM. After a successful renewal for one year contracts, this date moves one

year, both on CLS and on PCM.

The partner should also control the dates over PCM before doing any operation on the system.

Renewal is achieved by activating a new set of Base SSP Licenses and SSP User licenses on the system

that is in its renewal period.

For example, if a system gets contracted on 30.12.2013, its original contract expire date will be

30.12.2014 on PCM, and 01.10.2014 on CLS, for which CLS shows the Renewal Period Start date only,

and this date equals to 90 days before the contract expire date on PCM. If this system gets renewed

between 01.10.2014 and 30.12.2014, renewed expire date will be extended to 01.10.2015 on CLS, and

30.12.2015 on PCM.

Please note that, after the renewal operation of a system, CLS requires time to re-calculate the dates.

It is best to wait and view the details of the renewed system from “View Used Licenses” menu step.

a) Before Expire Date on CLS

Before Expire Date on CLS , which is before the renewal period starts (the renewal start date at PSC) , a

renewal is not possible

29

Image 2.a.1 – Contracted System Details before the Renewal Period Start Date. Renewal is not possible

as of 24.12.2014

30

Image 2.a.2 – Renewal is not possible as of 24.12.2014

31

b) During renewal period

During renewal period renewal is possible, Expire Date on CLS had past however 90 days upon that date

has not past yet, which means Reneal Period has been started and system is in its renewal period:

If during the search step of “View Used License” menu step, “Status” is selected as empty rather than

“Active”, status for SSP licenses will be shown as expired.

Image 2.b.1 – View Used Licenses – “Empty Status” System search in the Renewal Period as of

24.12.2014

32

After above search is conducted and the system in the renewal period is found, then “View Details” is

clicked, expired status SSP licenses will be shown and their Renewal Period Start Date or CLS Expire Date

can be displayed. It can be observed that; as of 24.12.2014 only 84 days has been past which means

system is in still Renewal Period:

Image 2.b.2 – License Details –Expired SSP licenses of a system which is in the Renewal Period as of

24.12.2014. 84 days past, the system is in Renewal Period, 6 more days to be expired on PCM, Dec 30,

2014.

33

If the same system is searched with “Active” condition, the active product licenses can be viewed as well:

Image 2.b.3 – View Used Licenses – “Active Status” System search in the Renewal Period as of

24.12.2014

34

When “View Details” is pressed after “Active Status” search is conducted, active product licenses can be

observed for the same system above:

Image 2.b.4 – License Details – “Active Status” System details that is in the Renewal Period as of

24.12.2014

35

Renewal is carried out like contracting an existing system for Software Support:

Image 2.b.5 – Select the SSP licenses that will be activated and used for Renewal

36

Press Generate Key, then enter the Locking Id of the system in renewal period, obey the rules of the CLS

for both SSP licensing and product, and activate the SSP licenses as an add-on to the existing system:

Image 2.b.6 – Enter the information of system in renewal period and proceed with add-on activation.

Obey the CLS rules that govern the SSP licenses and product, else CLS won’t allow this operation.

37

Click next, and proceed with the completion of activation described in previous section.

Let it be known that it may take a minute for CLS to recalculate the renewed dates, if License Key details

are requested to be shown quickly after the end of add-on activation process, menu step “View Used

Licenses” should be used later to observe the correct dates:

38

Image 2.b.7 – Pre-Calculated Renewal Dates. After activation it may be possible for CLS to show the pre-

calculated dates for SSP licenses wrong. It may take a minute for CLS to calculate and update it.

Image 2.b.8 – Re-Calculated and Correct Renewal Dates. See the example that is described in this

section’s entry.

39

c) Re-Contracting / Re-Activation:

Re-contracting is a similar process like Renewal and Contracting; it actually is the process that is done

after contract has been expired both on CLS and on PCM. Re-contracting is also achieved by activating a

new set of Base SSP Licenses and SSP User licenses on the system. This action leads to new contract

expire dates calculated as if this system has been freshly contracted.

For example, if a system gets contracted on 06.12.2013, its original contract expire date will be

06.12.2014 on PCM, and renewal period start date will be 06.09.2014 on CLS. After 06.12.2014, this

system can only be re-contracted, no expansion with SSP is possible at this point, and after this system

gets re-contracted later on any point than 06.12.2014, as an example on 24.12.2014, new expire dates

will be 25.09.2015 on CLS, and 24.12.2015 on PCM respectively.

40

Image 2.b.8 – Re-Contracted system.

5) Use case: Expansion

Expansion stands for two different process; expansion of regular user licenses without SSP licenses and

expansion with SSP licenses of system that is in contract duration.

Expansion of regular User licenses, is a generic process on CLS. It can be achieved by doing add-on

activation of the licenses in regard on a system. Although this process is only allowed if a system is not

contracted or its contract is already expired. If the system is contracted then Expansion must be carried

out with SSP licenses which in return may extend the duration of the contract.

Expansion with SSP licenses is the process where a contracted system’s contract duration is extended

which is dependent on the result of an expansion formula calculation; including the variables such as the

quantity of added user licenses, installed user licenses’ quantity and the days past since the system is

contracted. Contract dates only gets expanded if the result of this formula is greater or equal to 10. So

SSP expansions lesser than 10 days are not worthy and won’t change the original contract dates.

Expansion with SSP is only possible, if the system is contracted and its contract expire date on PCM has

not past yet, which means it is also possible, in the range of 90 days after the SSP licenses has been

expired on CLS, in the Renewal Period.

The partner should also control the dates over PCM before doing any operation on a system.

Please note that, after the Expansion with SSP completed, CLS requires time to re-calculate the

expanded dates. It is best to wait a minute and view the details of the renewed system from “View

Used Licenses” menu step.

41

a) Before Renewal Period

Image 3.a.1 – View Used Licenses – Search Step – System is contracted and before Renewal Period as of

25.12.2014

42

Image 3.a.2 – View Used Licenses – License Details – System is contracted and 5 days before the Renewal

Period start date as of 25.12.2014

43

During the whole contract duration, only Expansion with SSP license is possible. Expansion of regular

licenses is not allowed without SSP licenses.

Image 3.a.3 – Expansion without SSP is not permitted during contract duration, before and during

renewal period.

44

The situation is also same for the vice versa case; while doing the Expansion with SSP, also user licenses

must be expanded, else CLS will not allow the operation due to quantity requirements.

Image 3.a.4 – SSP quantity must match the User license quantity, so during expansion both SSP and User

licenses should be used.

45

As example, if a system has been contracted on 30.03.2014 with 200 SSP Users, its original contract

expire date will be 30.03.2015 on PCM, and 30.12.2014 on CLS, for which CLS shows the Renewal Period

Start date only, and this date equals to 90 days before the contract expire date on PCM. If this system

gets expanded with 100 SSP licenses on 25.12.2014, expanded expire date will be extended 90 days

[(Added Users (100) * Elapsed Days (270)) / (Installed Users (200) +Added Users (100)) = 90 >= 10] to

28.06.2015 on PCM, and 30.03.2015 on CLS.

Image 3.a.5 – Search for and select the Licenses to be used for Expansion with SPP

46

Image 3.a.6 – Enter the information of the system to be expanded with SSP and complete

the activation process.

47

Image 3.a.7 – Pre-Calculated Dates. After activation it may be possible for CLS to show the pre-calculated

dates for SSP licenses wrong. It may take a minute for CLS to calculate and update it.

48

Image 3.a.8 – Calculated and corrected dates after Expansion with SSP. See the example that is described

in this subsection’s entry.

49

b) During Renewal Period

Expansion with SSP is also possible during the Renewal Period, beginning with the “Renewal Period Date”

Expire Date on CLS till 90 days plus of Expire Date on CLS which is the exact contract end date on PCM.

During this period CLS will also keep account on the expired SSP license quantities and conducts its rules

according to the expired SSP licenses for internal mechanics to execute, since those licenses are still in

consideration for the SSP contract.

As example, if a system has been contracted on 30.12.2013 with 200 SSP Users, its original contract

expire date will be 30.12.2014 on PCM, and 01.10.2014 on CLS, for which CLS shows the Renewal Period

Start date only, and this date equals to 90 days before the contract expire date on PCM. As of

25.12.2014, the system is still in its Renewal Period, and 5 days until the expiry on PCM. If this system

gets expanded with 100 SSP licenses on 25.12.2014, expanded expire dates will be extended 120 days

[(Added Users (100) * Elapsed Days (360)) / (Installed Users (200) +Added Users (100)) = 120 >= 10] to

29.04.2015 on PCM, and 29.01.2015 on CLS. Since the Expire Date on CLS will be extended beyond the

activation date, 25.12.2014, previously expired SSP Base and SSP User licenses will their status changed

to “Active” on CLS after the Expansion with SSP is completed and the dates are extended with the

recalculation.

Image 3.b.1 – View Used Licenses – System in Renewal Period.

50

Again during renewal period, Expansion without SSP is not possible. On CLS the expired SSP

licenses will be considered if not expired on PCM, while checking the rules for activation during

Expansion. Although they will be not shown during activation.

Image 3.b.2 – Expansion without SSP is not possible even during in Renewal Period.

CLS still considers the quantities of expired SSP Licenses if contract has not been expired both

on CLS and on PCM for the Expansion process.

51

It is also not allowed to add more SSP licenses without adding more User licenses as the

Expansion with SSP license basic requirement suggests.

Image 3.b.3 – Expansion with SSP but without adding enough User License is not also possible

even during Renewal Period.

This is because CLS still considers the quantities of expired SSP Licenses if contract has not been

expired both on CLS and on PCM for the Expansion process.

52

Enough SSP and enough User licenses must be selected too before proceeding with the

Expansion with SSP during the renewal period:

Image 3.b.4 – Expansion with SSP during Renewal Period.

Select the licenses to be activated as Expansion.

53

Image 3.b.5 – Expansion with SSP during Renewal Period.

Enter the locking id of the system that will be expanded with SSP in the renewal period.

54

When the Expansion with SSP completed first, it may take a minute for CLS to calculate the

expanded dates and update the licenses as it is required:

Image 3.a.6 – Pre-Calculated Dates and pre-modified licenses.

After activation it may be possible for CLS to show the pre-calculated dates and pre-defined licenses for

SSP licenses wrong. It may take a minute for CLS to calculate and update it.

55

56

Image 3.b.7 – Re-Calculated Dates and modified licenses.

Expired SSP licenses both Base and User SSP licenses status has been updated to “Active”, and now CLS

displays them properly with the correctly extended dates.

57

c) After Contract Expired

After the SSP contract has expired both on PCM, and on CLS; which also stands for 90 days have also

past the expire Date on CLS, if Software Support is required then the system must be re-contracted by

doing a reactivation of SSP Base and SSP User licenses on the expired system. Please see section 2.c for

re-contracting / re-activation.

However, if no SSP is requested standard procedure of Expansion of User Licenses is possible after the

SSP contract has expired.

Image 3.c.1 – View Used Licenses –

Search for the system that its SSP contract has expired as of 25.12.2014

58

Image 3.c.2 – Expired SSP License Details

System that its SSP contract has expired as of 25.12.2014. More than 90 days past the Expire Date on CLS

(Renewal Period Start Date), 109 days as of 25.12.2014. 19 Days has past the Contract Expire Date

06.12.2014 on PCM.

59

The product is still active on the same system, only its SSP licenses has been expired:

Image 3.c.3 – Active product licenses on the system.

60

Image 3.c.4 – Select the product licenses to be activated.

61

Image 3.c.5 – Input the system’s info and quantities.

62

Image 3.c.5 – Expansion without SSP is completed