Hyperion Licensing Information

for hyperion essbase pricing policy, you can refer to the Oracle Price List
This document is for general purpose.
My main motto behind writing this post is to throw some light on types of licensing policies of softwares.
Before some time there was lot of confusion about the types of licenses. Let me explain them.
1. Named User License:
A named user license allows the software to be used by one specific user named when you purchase the software. Named user licenses may be installed on multiple computers but they may only be accessed by the named user, they may not be shared in any way. A named user license may not be used at the same time on different computers.
It can also be defined as an individual authorized by you to use the programs which are installed on a single server or multiple servers, regardless of whether the individual is actively using the programs at any given time. A non human operated device will be counted as a named user plus in addition to all individuals authorized to use the programs, if such devices can access the programs.
2. Concurrent user license or Floating user license:
A floating user license, sometimes known as a concurrent user license, allows the software to be used by more than one user at the same site but limits the number of simultaneous users to the number of licenses purchased.
For example, three floating user licenses permit three users to access the software at the same time. A fourth user must wait until one of the current users exits the software before they may use the software. A floating user license is sometimes called a concurrent or shared license. Floating user licenses should be purchased for any installation where multiple users may access the software on the same computer such as a build server.
3. Processor based license:
This is defined as the number or procesors where the software is installed and running. The number of cores and core processor licensing factor which generally ranges from 0.25 to 0.75 also decides the number of processors to be considered for licensing.
For example, an XYZ server installed and/or running the program on 6 cores and having core processor licensing factor of .25 would require 2 processor licenses (6 multiplied by a core processor licensing factor of .25 equals 1.50 which is then rounded up to the next whole number which is 2).
There are some other types of licensing terms but only these are used mostly.

Hyperion Reporting and Analysis Architecture

Lets understand the various components of Hyperion:
Workspace is a common window to view the contents of all Hyperion components.
Hyperion Reporting and Analysis:

One zero-footprint Web-based thin client provides users with access to content:

● Financial reporting for scheduled or on-demand highly formatted financial and operational reporting from most data sources including Hyperion Planning – System 9 and Hyperion Financial Management – System 9

● Interactive reporting for ad hoc relational queries, self-service reporting and dashboards against ODBC data sources

● SQR Production reporting for high volume enterprise-wide production reporting.

● Web analysis for interactive ad hoc analysis, presentation, and reporting of multidimensional data.

Hyperion Reporting and Analysis Architecture:(This diagram is taken from some Hyperion Document)

Client: The client tools consist of
Workspace: It is a DHTML Zero footprint web client and provide the user interface for viewing and interacting with the reports created using Authoring studios.
Authoring Studios: These are the client interfaces to create the reports and includes-
(a) Hyperion Interactive Reporting Studio: Windows client where you can connect to different data sources including the flat files and build very interactive presentation reports like reports in simple tabular format, pivot reports, graphs and charts with drill anywhere feature which means that you don’t have to define the hierarchy or drill path and slicing and dicing and Dashboards with many features like hyperlinks to the details reports and embedded browser which can be used to view any other web application to open within the Dashboards.
(b) Hyperion Financial Reporting Studio: Windows client where you can connect to the multidimentional data sources and create highly formatted financial reports by simply dragging and dropping rows and columns and defining page breaks.
(c) Hyperion SQR Reporting Studio: Windows client where you can connect to wide range of data sources and produce high volume pixel perfect operational reports and can be scheduled.
(d) Hyperion Web Analysis: Java applet where you can connect to different data sources using JDBC and build interactive reports and dashboards.
Smart view for office: This is a tight integration with Microsoft Office tools where ou can do analysis like drill downs, keep only and remove only options, POV manager, data refresh, copying data cells and pasting to MS Word and Powerpoint which automatically gets refreshed if the data changes in the source etc. There is one more component in smart wiew which is Hyperion Visual Explorer(HVE), where again you can view the data in presentable interactive graphs and charts.
Application Layer: It consists of two parts :
Web Tier: It consists of two parts (a) Web server- to send and receives content from the web clients. (b) Application server- it is a J2EE application server.
Web server and application server are connected using an HTTP connector.
The web Tier hosts the web applications like workspace, web analysis, interactive , SQR and financial reporting applications.
2. Services Tier: It contains services and servers that controls the functionality of the web applications and clients. Core services handles repository information, authorization, session information, documents publication.

Siebel Analytics (OBIEE) Vs Hyperion Essbase

In this post I will discuss some of the major differences between OBIEE and Hyperion Essbase.
I have got the opportunity to work on Oracle BIEE formerly known as Siebel Analytics and Hyperion Essbase. Sometimes people come up with a question that which one is the best and what are the differences. I just want to share some views which you may ar may not agree. I would appreciate any comments.

1. From a broader prospective, I felt that Hyperion Essbase is a very comprehensive BI tool with very advance features to cater specific areas of an organisation. Essbase provide options like Block storage and aggregate storage options. Block storage options can be very effective for planning and budgeting applications and it also enablles to write back the data like budget data to essbase and do what-if analysis and save their versions. Even OBIEE allows you to write back but not useful for what-if type analysis.

Organisations keeping most of their planning and analysis data in MS Excel, would find it more useful than Siebel analytics. To load data from text files, load rule files can be created which holds the information about any transformation or cleaning operation done and same load rule file can be used for many loads.

Lets discuss on some more differences-

1. Hyperion Essbase is MOLAP where as OBIEE is ROLAP- MOLAP as we store the cube data, analysis is much faster than ROLAP where data is not stored anywhere and queried directly from the source database. But when you are storing an Essbase cube you can analyse data only upto the time it was created( we call it near real time analysis) where as OBIEE gives you the 100% real time analysis. Now this all depends on the needs of an Organisation.Hyperion Essbase also provides XOLAP or hybrid OLAP where Summary level data resides in Essbase cube but detail data is retreived fom the source database. Also to load the data in the cubes or refresh the cube with fresh data, it takes some time and resource.

2. Hyperion Essbase requires a relational database to store metadata where as OBIEE does not. So you can save a lot on this.

3. Hyperion essbase use Microsoft Excel as analysis tool- This is one feature where Hyperion scores over OBIEE. Its not that OBIEE does not have integration with Excel but the way you do it in Hyperion is amazing. OBIEE only allows you to open the charts you have created in Excel or powerpoint and analyse but Hyperion places the entire cube in front of you in excel and you can drill down, add or remove dimensions, apply filters, pivot data, slice and dice and much more and also the write back capability which makes it the first choice for budgeting and forecasting applications. This is very important from implementation perspective as most of the users are already working on excel and they do not even think twice of acceping the system I mean users adaptibiliy is high and fast as compared to any other system which generally take atleast 15 days to learn and 1 month to understand and atleast 2 months to get fully used to the system and 3 months to accept the system. So a very big factor interms of a project being successful. Also, saves a lot of cost on training.

4. Pre built applications available for OBIEE- Oracle has created pre-built schemas, reports and dashboards for some major ERP's like SAP, Oracle Apps, JD Edwards, peoplesoft etc. Those warehouse pre-built schemas can be used by Hyperion but only to some extent and as the dashboards are created in OBIEE, Hyperion cannot use it. This is the scenario as of now but soon they will be available for Hyperion as well.

5. Very easy for end users to design dashboards in OBIEE. If you need a system only for your BI and reporting needs, OBIEE will be a good value proposition.

6. Advance analytics, what-if's, predictive modelling and very fast infact lightening fast system Hyperion Essbase would be effective.