Oracle Usable Apps | Applications User Experience Simplicity, mobility, extensibility
Customer Role: How User Experience Research Is Conducted
Summary Page Layout
The Summary Page pattern set helps developers and product managers determine the best layout for the Summary Page based on user roles, usage patterns, and data needs. The pattern set helps them understand the advantages and disadvantages associated with displaying metrics, non-structured data, links, alerts, and prompts on the Summary Page.
Use the Correlating and Comparing pattern when you must customize a Summary Page and define default layouts for role- or domain-specific dashboards and business performance consoles. The Correlating and Comparing pattern also helps developers, product managers, and designers define page layouts for the Summary Page of a Business Intelligence (BI) application to accommodate key information. Information on this page is used primarily for comparing and correlating performance indicators and metrics.
Selection Criteria for This Pattern Return to Top
The Correlating and Comparing pattern is useful for the following user roles:
  1. A CXO-level user who reviews the overall health of the organization and must be aware of any red flags and key alerts.
  2. A middle manager (also an analyst) who reviews key metrics, analyzes problem areas, and acts accordingly.
  3. A process worker (customer service representative, clerk) who is responsible for analyzing specific metrics and performing transactions.
Required Screen Elements Return to Top
The Correlating and Comparing pattern contains the following screen elements:

Component Type
Required Component
Header Region
The header region should contain:
  • Branding logo
  • Links to other dashboards
  • Log out link
  • Links to other Oracle Business Intelligence Enterprise Edition (OBIEE) applications, such as Answers, Reports, and so on
Subpage Tabs
Multiple tabs with at least one tab for summary view. The default name of this tab should be “Summary”. This should be the default selection on launch of the application.
Regions (Containers)
Use regions or containers to contain any structured and non-structured data. No information should appear outside of a region.
Navigation Links
The Summary Page tab has the navigation links in the top-right section.
Every region may have links that enable drill-down navigation or movement to other tabs.
Use global icons for quick actions. A tooltip is required for icon descriptions.
Use icons within the container with the tile description.
Data tables use icons for the status columns.
The Alerts and Prompts section uses status icons.
Drop- Down Lists
Use drop-down lists within the containers as filters or to switch between views.
Use a drop-down list in the header section to navigate to different applications within OBIEE.
Example Layout of Summary Page Return to Top
The following layout provides a typical arrangement of page regions to accommodate one or more metrics, key performance indexes (KPIs), and reports for key tasks related to data correlating and comparing. The example that follows is a two-column arrangement of page regions. The horizontal axis arrangement is useful for representing metrics with bigger timelines and complex data. You can place the top four metrics or reports in the visible region of the page and stack the rest below these page regions. Users can access these additional metrics by scrolling the page vertically. However, if you have more than seven or eight metrics, it is best to create more logical groupings and assign a new tab for them.

Figure 1: Two-Column Layout

Return to Top  
The following three-column layout is useful when you want to highlight a high-level overview of the KPIs, rather than the immediate details. This layout accommodates more metrics or reports in the visible region of the page. Users can then scroll to view additional metrics.

Figure 2: Three-Column Layout

Return to Top  
The following two-row layout is useful when you are comparing two key metrics and KPIs. The x-axis provides maximum horizontal spacing to accommodate two large sets of data, one above the other. This layout enables you to focus on both metrics at the same time.
If you must compare and correlate historical trends for more than two metrics or KPIs, you can add more rows to this layout. You will need to reduce the height of the page regions and use spark lines to display historical data.

Figure 3: Two-Row Layout  |  About Oracle  |  Careers  |  Contact Us  |  Legal Notices  |  Terms of Use  |  Your Privacy Rights