Wiki source code of Compliance
Last modified by Jannis Klein on 2024/08/13 07:31
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{aagon.priorisierung}} | ||
2 | 80 | ||
3 | {{/aagon.priorisierung}} | ||
4 | |||
5 | {{aagon.floatingbox/}} | ||
6 | |||
7 | A recalculation of the compliance is needed to calculate the status of the products. The calculation checks whether the number of existing licenses matches the actual usage. | ||
8 | |||
9 | |||
10 | |||
11 | You can see whether this is the case by looking at the status of the license in the workspace: | ||
12 | |||
13 | |**Symbol**|**Status**|**Explanation** | ||
14 | |[[image:63_LicMan_Vollständig lizenziert_311.png||height="18" width="250"]]|Fully licensed |Sufficient licenses are assigned to the product to cover usage. | ||
15 | |[[image:index_002.png||height="21" width="250"]]|Not enough licenses assigned|There are insufficient or no licenses assigned to the product. | ||
16 | |[[image:index_004.png||height="21" width="250"]]|Can use right to new version|An Upgrade to a new software version has been found in the DNA catalogue. The license can then be moved and upgraded. | ||
17 | |[[image:index_005.png||height="21" width="250"]]|Clear|There are no licenses or consumers assigned to this product. | ||
18 | |[[image:index_006.png||height="15" width="250"]]|A calculation error has occurred|An error has occurred during calculation, which means that the usage cannot be calculated. | ||
19 | |[[image:index.png||height="20" width="250"]]|Licensed for concurrent use|The licenses are limited by the software itself. | ||
20 | | |License does not have enough base licenses|There are more Upgrade/Update licenses than base licenses available. | ||
21 | |||
22 | = Perform a Compliance Recalc = | ||
23 | |||
24 | {{aagon.infobox}} | ||
25 | Please note that a full and correct licence recalculation can only be performed when both the products and the licenses have been neatly linked and all necessary info has been entered! | ||
26 | {{/aagon.infobox}} | ||
27 | |||
28 | You run the compliance recalculation by selecting //Recalculate// in the ribbon bar. The recalc compares the usage and availability of licenses including coefficients and generates a balance sheet. Note that for DNA2, the entire DNA2 Recalculation is already included in //Recalculate//. | ||
29 | |||
30 | Use Full Recalc to do a complete ACMP DNA Recalculation. The Full Recalc function only applies to DNA and not to DNA2. | ||
31 | |||
32 | = Customize the licence consumption = | ||
33 | |||
34 | To assign licenses directly to a consumer, click //Customize //in the ribbon bar. A new window opens, divided into the tabs Assignments and Priorities. | ||
35 | |||
36 | {{aagon.infobox}} | ||
37 | Note that to display changes, a Recalc must be performed! | ||
38 | {{/aagon.infobox}} | ||
39 | |||
40 | {{aagon.infobox}} | ||
41 | Note that consumers with manual license assignments are always prioritised higher than consumers with automatic assignments! | ||
42 | {{/aagon.infobox}} | ||
43 | |||
44 | == Assignments == | ||
45 | |||
46 | This tab displays all consumers, both automatic and manual, for the selected product. Here you have the option of manually assigning a specific license to a specific consumer. An exact assignment would normally not appear in the license calculation, since the licenses are assigned to the consumers randomly. | ||
47 | |||
48 | You can manually assign a license to each consumer or enter a new license. To do this, click on the arrow in the Manual Assignment column. | ||
49 | |||
50 | If the consumer is to be ignored in the usage calculation, enable the corresponding checkbox. You can now enter the reason for ignoring in the Reason column. Manual assignment of a license is now no longer possible for this consumer and the consumer no longer generates any usage in compliance for the product. | ||
51 | |||
52 | == Priorities == | ||
53 | |||
54 | Only consumers who have been manually assigned a license in the //Assignments// tab appear in the tab. These manual assignments can be prioritised. This means that in the event of under-licensing, the consumers that have been prioritised higher will receive a license, so that a consumer with a lower priority may not receive a license. | ||
55 | |||
56 | To set the structure, use the arrows on the right side of the window. | ||
57 | |||
58 | When you have made the assignments and set the priorities, close the window with //Done//. | ||
59 |