Defining Dimension Hierarchies
You define KPI hierarchies from the Dimension Hierarchies page. Dimension hierarchies illustrate relationships between KPIs. Optimize uses Dimension hierarchies to complete the following tasks:
Evaluate KPI relationships when performing trend analysis to determine how a lower-level, or child, KPI might affect its parent KPI.
For example, suppose you define a profit KPI as a high-level KPI in a hierarchy and you create a rule that alerts you when that profit KPI is below normal. Then you define a second KPI to monitor revenue by customer region. You define that second (revenue) KPI as a child of the profit KPI, and you create a rule that alerts you when that revenue KPI is below normal. If a rule violation occurs for the parent (profit) KPI, Optimize then will evaluate the children of that KPI. Based on the relationship you defined, if Optimize discovers that a child KPI also has gone out of compliance with a rule (for example, if the revenue of a specific region is below normal), Optimize can suggest that the child KPI is a probable cause of the rule violation for the parent KPI.
Display KPI relationships on the Business Data (
Optimize for Process) and System Data pages.
Build a monitor tree, which presents a structural view of the monitored systems and business processes on the Analytics Overview page.
Important:
When Analytic Engine runs in Static DB Schema mode, you cannot create, edit, or delete dimensions, event maps, dimension hierarchies or KPI definitions. In addition, all respective buttons in the user interface will be unavailable. For more information about enabling and disabling Static DB Schema mode for the Analytic Engine, see the PDF publication Configuring BAM.