Sublicensing
Sublicensing can occur at many levels. The most common example is that a customer has simply created more users in the system than was contractually agreed.
However, another example may be the use of components or functions that are not included in the existing license model. Often, in this case, customers do not even know that you have violated the license agreement. To avoid such things, functions should be disabled, removed or simply not installed during the installation or configuration of the system (feel free to contact us about this).
Overlicensing
Strange but true: many customers voluntarily pay too much! There are many reasons for overlicensing.
For example, many customers pay support costs for systems that have not been used for years or are no longer offered or further developed. Once the license agreements have been concluded, they are generally not viewed again. Our experience shows that we can often demonstrate a large savings potential by optimizing Oracle Hyperion licenses.
Availability of Hyperion licenses
Especially with software from Hyperion (now Oracle), another problem for many customers is that the licenses they want no longer seem to be available.
For example, a customer who opts for the on-premises product Hyperion Financial Management may only be offered the Financial Consolidation (FCCS) cloud solution because the right contacts seem to be missing.
Contact us if you are looking for licenses for:
-
Hyperion Planning
-
Hyperion Financial Financial Management (HFM)
-
Hyperion Data Relationship Management (DRM/MDM)
-
Hyperion Financial Data Quality Management (FDM EE)
-
Hyperion Essbase
