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 Reviewing and Monitoring pattern when you must customize a Summary Page or define default layouts for role- or domain-specific dashboards and business performance consoles. The Reviewing and Monitoring pattern also helps developers, product managers, and designers define the best page layout for the Summary Page of a BI application and to accommodate key information. Information on this page is used primarily for reviewing and monitoring key metrics and alerts.
Selection Criteria for This Pattern Return to Top
  1. A CXO-level user needs to review the overall health of the organization and 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.
Required Screen Elements Return to Top
The Reviewing and Monitoring 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 Layouts of the Summary Page Return to Top

The following layout provides enough room to accommodate various metrics, reports, alerts, and so on for the high-level review of metrics and performance indicators and for the monitoring of key system messages and alerts. The following example is a two-column arrangement of containers (referred to as page regions). The horizontal axis 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 there are more than seven or eight metrics, it is best to create more logical groupings and assign a new tab for them.

Return to Top  

The following OBIEE sample dashboard illustrates a two-column layout:

Figure 1: Two-Column Layout

Return to Top  
If the end user is more concerned about the high-level overview of the KPIs, rather than the immediate details, the three-column layout is best. This layout accommodates more metrics or reports in the visible region of the page. You can place additional metrics below the visible region of the page.

Return to Top  
The following OBIEE sample dashboard illustrates a three-column layout:

Figure 2: Three-Column Layout

Return to Top  
The following primary metric layout is useful when you want to focus on one primary metric or report. You can arrange other metrics or reports below:

Return to Top  
The following OBIEE sample dashboard illustrates a primary metric layout:

Figure 3: Layout for a Primary Metric Representation

Return to Top  
It's important to display key notifications and messages up front in order to keep users informed. In the following layout, the Alerts and Prompts section is featured as the first component on the Summary Page. You can use this section to display key alerts, prompts, and messages for all of the key metrics.

Return to Top  
The following OBIEE sample dashboard illustrates an Alerts and Prompts section.

Figure 4: Alerts and Prompts section

Return to Top  
If you must display alerts in context to a metric on the Summary Page, you can introduce an independent message area within the page region.

Return to Top  
The following OBIEE sample dashboard illustrates an Alerts and Prompts section at the page-region level:

Figure 5: Alerts and Prompts Section at the Region Level  |  About Oracle  |  Careers  |  Contact Us  |  Legal Notices  |  Terms of Use  |  Your Privacy Rights