Oracle® Balanced Scorecard: User Guide Release 11i
Oracle® Balanced Scorecard: User Guide Release 11i
Oracle® Balanced Scorecard: User Guide Release 11i
User Guide
Release 11i
Part No. A95235-09
March 2005
Oracle Balanced Scorecard User Guide, Release 11i
Contributing Author: German Arcinegas, Patricia Perdomo, Christine Monk, Sameer Chhabra
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
The Programs may provide links to Web sites and access to content, products, and services from third parties.
Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear
all risks associated with the use of such content. If you choose to purchase any products or services from a
third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the
quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third
party, including delivery of products or services and warranty obligations related to purchased products or
services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any
third party.
Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.
Contents
Preface
1 Introduction
Balanced Scorecard Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Balanced Scorecard Perspectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Oracle Balanced Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
iii
Send Us Your Comments
Oracle welcomes your comments and suggestions on the quality and usefulness of this publication. Your
input is an important part of the information used for revision.
• Did you find any errors?
• Is the information clearly presented?
• Do you need more information? If so, where?
• Are the examples correct? Do you need more examples?
• What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate the title and part
number of the documentation and the chapter, section, and page number (if available). You can send
comments to us in the following ways:
• Electronic mail: appsdoc_us@oracle.com
• FAX: 650-506-7200 Attn: Oracle E-Business Intelligence Documentation Manager
• Postal service:
Oracle E-Business Intelligence Documentation Manager
Oracle Corporation
500 Oracle Parkway
Redwood Shores, CA 94065
USA
If you would like a reply, please give your name, address, telephone number, and electronic mail address
(optional).
If you have problems with the software, please contact your local Oracle Support Services.
v
Preface
Intended Audience
Welcome to Release 11i of the Oracle Balanced Scorecard User Guide.
This guide is intended for users who view scorecards created in Oracle Balanced
Scorecard. For information on creating scorecards, see: Oracle Balanced Scorecard
Administration Guide.
See Related Documents on page viii for more Oracle Applications product information.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible,
with good usability, to the disabled community. To that end, our documentation
includes features that make information available to users of assistive technology.
This documentation is available in HTML format, and contains markup to facilitate
access by the disabled community. Accessibility standards will continue to evolve over
time, and Oracle is actively engaged with other market-leading technology vendors to
address technical obstacles so that our documentation can be accessible to all of our
customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/ .
vii
Structure
1 Introduction
2 Using Oracle Balanced Scorecard
Related Documents
Oracle Balanced Scorecard Administrator Guide
Oracle Balanced Scorecard Install Guide
viii
1
Introduction
Scorecard Theory
In the preceding figure, each scorecard contains a set of strategic themes and
perspectives. These themes and perspectives are translated into strategic
Introduction 1-1
objectives. Strategic objectives are supported by strategic initiatives and can contain
one or more measures. Strategic initiatives are the critical projects that an organization
needs to complete to accomplish a strategic objective. Measures are the areas that an
organization needs to focus on to accomplish a strategic objective. Measures are usually
associated with a plan and an owner, so the people involved can follow-up on the
implementation of the strategy.
Scorecard Navigation
The scorecards are used and supported by three different types of users:
• Viewers who are the end-users responsible for using scorecards to monitor
performance,
• Designers who are responsible for creating the scorecards, and
• Administrators who are responsible for setting up the application and maintaining
the data structure.
The Oracle Balanced Scorecard User Guide describes how viewers can use scorecards to
monitor performance.
The Oracle Balanced Scorecard Administration Guide describes how designers and
administrators can create the scorecards and the data required to monitor performance.
Terminology
Before you begin using Oracle Balanced Scorecard, you should understand the following
terms:
• Administrator: The scorecard administrator is responsible for installing,
implementing, and maintaining Balanced Scorecard. The scorecard administrator
loads data and is responsible for managing any data-related issues. The scorecard
administrator is also responsible for creating and setting up users, and securing
scorecards, objectives, and display options.
• Alarm: Indicates the status of an objective. The possible statuses
are: acceptable, marginal, or unacceptable. The status is based on how the
objective falls within a set of defined tolerance ranges for the objective’s expected
Introduction 1-3
performance. For example, if Revenue decreases by more than 5%, then the alarm will
indicate that Revenue is either marginal or unacceptable performance, depending on
how the tolerance ranges are set. If an objective is supported by several KPIs, then
the status of the objective is the status for the default KPI for the objective.
• Custom: In this guide, "custom" is used to denote any content created using the
application.
• Designer: The scorecard designer is responsible for creating the
scorecards, views, KPIs, objectives, and dimensions. The scorecard designer defines
the default settings for scorecards and the objective report. The scorecard designer
also sets the alarm conditions for the objectives.
• KPI: A calculation or metric that is used to support an objective. Each objective can
be supported by one or more KPIs; however, there is only one default KPI for each
objective. The status of the default KPI determines the status of the objective. KPIs
can be preseeded or created by the scorecard designer.
• Objective: A metric used to gauge performance in a particular area, for
example, Increase Revenue, Reduce Service Calls, and Maximize Sales Growth.
• Preseeded: In this guide "preseeded" is used to denote any content that is provided
with Oracle Applications. For example Oracle Daily Business Intelligence provides
several preseeded KPIs that can be reused in other applications.
• Production: Refers to any scorecard which is available to viewers in the List of
Scorecard window. To be a production scorecard, the design must be complete
and the Generate Database process and the Data Load process must have been
run. Also, the user must be assigned access for the scorecard.
• Scorecard: A representation of a company strategy that maps objectives and KPIs to
the strategy using the Balanced Scorecard methodology. Viewers use the scorecard
to compare actual and planned performance.
• Strategy: A high-level plan that a company wants to follow. A strategy is generally
a collection of objectives. For example, a strategy might be to improve overall
business by increasing customer satisfaction, reducing the cost of goods sold, and
increasing sales.
• View: A way of viewing a scorecard. There are five possible views available in
Oracle Balanced Scorecard:
• Tree view
• Scorecard view
• Strategy Map view
• Detailed view
• Custom view
• Viewer: The Viewer is the user who is responsible for using the scorecard to
compare actual corporate performance to planned or forecasted performance.
List of Scorecards
The List of Scorecards window provides a hierarchical list all the scorecards for your
responsibility.
Note: The hierarchical relationships between scorecards does not imply
a roll-up of data. It only indicates a logical, parent-child relationship
between the two scorecards.
Scorecard Views
You can view scorecards using the following scorecard views:
• Custom view, page 2-3
• Detailed view, page 2-4
• Scorecard view, page 2-5
• Strategy Map view, page 2-6
• Tree view, page 2-7
Custom View
The custom view is created by the scorecard designer. Each scorecard can have an
unlimited number of custom views. Each custom view can be designed for a specific
audience or organizational schemes. For example, the scorecard designer can create a
custom view that shows only the top five objectives in a scorecard.
The custom view is the only view that enables you to navigate across multiple related
views and drill down to more detailed information for a particular scorecard. It also
contains the following unique features:
• Hot spots: Link to an objective.
• Links to custom views: Link from one custom view to another.
• Launchpads: Link to other related views or objects, such as other
reports, workbooks, or URLs. Launchpads can also contain additional information
about the objectives or strategy displayed in the view. For example, a launchpad
may explain how a specific strategic objective relates to the overall scorecard
strategy. Launchpads are indicated by an “i” icon.
Detailed View
The detailed view displays the underlying data for each objective. The underlying data
includes: Actual, Plan, Variation, and Percent of Plan data. This view enables you to
interpret how the alarms are calculated for each objective.
Scorecard View
The scorecard view lists all of the objectives in the scorecard, organized into boxes. Each
box represents a logical grouping of perspectives or strategic themes for the scorecard.
Tree View
The tree view lists all of the objectives in the scorecard, organized into a tree that
represents the perspectives or strategic themes of the scorecard. This view also shows
the KPIs that support the objective.
Note: The default KPI for an objective appears with an alarm next to it.
Alarms
Alarms indicate the status of an objective. Alarms show if actual data is
acceptable, compared to your plan, and enable you to identify data for further
analysis. You can click on an alarm to drill down to a more detailed view of the objective.
Alarm Examples
The following table shows the default alarm statuses. The scorecard designer can
customize the status for each objective.
Triggering Alarms
Alarms are triggered by comparing actual data to other data, such as a plan, budget, or
forecast. If compare to data has not been loaded, alarms are disabled.
The following factors determine how an alarm is triggered.
• System
• Is the system in production or prototype mode?
• Objective
• What are the KPI options?
• What are the dimension objects?
• What is the default periodicity?
• What are the alarm triggers?
• Data
• What is the percent deviation from the planned value?
• When was the data last collected?
Alarms by Objective
Alarms for the following objectives are calculated in a different manner.
• Trend Graph: Compares the current month’s actual values against the plan or
budget values for the last updated period for the default KPI.
• Comparison Graph: Alarms for all objectives in comparison mode are triggered as
follows:
• If any dimension object value is unacceptable, the alarm is unacceptable.
• If any dimension object value is marginal, the alarm is marginal.
• If all dimension object values are acceptable, the alarm is acceptable.
Trigger values are used to calculate a separate color for each dimension object value
for the default KPI options of the comparison dimension object.
Objective Report
The objective report provides additional information on an objective. To drill to this
report, click on the objective in the scorecard view.
Objective Report
This report shows objective performance in graph and table format. It also displays the
KPIs, KPI options, and dimensions used to calculate the performance.
Depending on how the objective was defined by the scorecard designer, the objective
report may also contain the following items:
• Cause and Effect Matrix: Shows the relationship between the underlying KPIs.
KPI Options
For each objective you can select the KPI and the KPI options that you want to
view. These options determine how the objective performance is calculated. You can
change the default KPI options to view different performance perspectives.
The following is a complete list of the available KPI options. The list of available KPI
options is configured by the scorecard designer.
• KPIs: The KPIs used to calculate the objective performance. KPIs are either
preseeded or they are created by the scorecard designer.
See: KPIs, page 2-13.
• Calculations: The calculation used to calculate the objective performance. Some
calculations can be combined with others to create a complex performance
calculation. For example, if you select Variation, Percent, and Year to Date, you can
view the Year to Date variation in percentage. The Percent and Growth, Year to
Date, and Year to Date Growth cannot be combined with other calculations.
See: Calculations, page 2-13.
KPIs
KPIs are calculations or metrics that are either preseeded by Oracle Applications or
created by the scorecard designer. Preseeded KPIs are delivered with Oracle Daily
Business Intelligence.
Alarms for preseeded KPIs are based on the default dimension settings for the KPI, as
defined by the scorecard designer. Unlike KPIs that are created by the scorecard
designer, the available periods for preseeded KPIs are determined by the Time view
by option.
You can change the default KPI options for preseeded KPI, but you cannot:
• Toggle between trend and comparison graphs
• View the comparison graph in pie chart format
If you have the appropriate security access, preseeded KPIs also enable you to:
• Drill down to related reports and links for the KPI
• Edit targets for the KPI
For more information on preseeded KPIs, see Oracle Daily Business Intelligence User Guide.
Calculations
You can select one or more of the calculations listed below to calculate performance. Not
all KPIs have all calculations enabled. The scorecard designer is responsible for enabling
the appropriate calculations.
Only the Percent and Growth, Year To Date, Year to Date Growth and Period to Date
calculations cannot be combined with other calculations.
• Variation: The amount that actual results vary from the compare to value.
• Percent: The actual results as a percentage of the compare to value.
• Cumulative YTD: The cumulative actual results for the current year. This calculation
accumulates actual data from the first day of the year to any point in time in the
year. In the objective view for balance accounts (such as Total Assets). Cumulative
YTD will be disabled since it does not apply.
• In Line Graphs, a second line of the same color illustrates the Period to Date values.
• When Period to Date is selected with a compare to value, the compare to value will
appear as a second bar. A marker over the bar will indicate the Period to Date value
against the total current value.
• You can only select one KPI and one compare to value for Period to Date calculations.
• The data compared must be based on same unit of KPI.
The list of available dimensions objects and values is defined by the scorecard designer.
Trend Graphs
Trend graphs plot data over time. Depending on the KPI options you choose, you can
either view a trend graph for single display options and compare to value (single bar
trend graph), or for multiple display options and compare to values (multiple series
trend graphs).
In all trend graphs, actual data is shown in bar format and compare to values are shown
as a trend line.
Trend graphs display one bar for each period, with a maximum of 12 periods. For
example, if the period type is Week, the trend graph would display 12 weeks of data, not
52 weeks.
The information line below the trend graph summarizes information for the last updated
period in the graph. The line is updated whenever you change a KPI option.
In the figure above, a single bar trend graph is used to show the units of beers sold
against the sales forecast. Actual sales are shown from January to June, forecasted sales
are shown from July to December, and the sales plan is shown as the trend line across
the bars.
Multiple series trend graphs show actuals for several display options and several
compare to values over time in the same graph. A legend at the bottom of the graph
indicates which series and which compare to values are shown on the graph.
In the figure above, a multiple series trend graph shows Sales, % Availability, and Market
Share data against the sales forecast.
Comparison Graphs
Comparison graphs compare the objective performance against a plan or budget for a
single period. You can view comparison graphs in either bar graph or pie chart format.
Pie charts are only available for comparison graphs. You can only view a pie chart if no
calculation method is selected or if the following calculation methods are selected:
• Contribution
• Year to Date
• Quarter-to-Date
Pie charts can display actual, or actual and plan data only. They cannot display other
display options.
Simulation Tree
In the simulation tree example above, each box in the simulation tree represents a KPI
that is driven by a formula or part of a formula. By increasing or decreasing a value in
the formula, you can determine how that KPI affects other KPIs, and see how it affects
performance.
You can reset values to their original state, print the results of different
scenarios, however, you cannot save your simulation tree scenarios.
You can drill to a trend graph for each KPI by clicking on the KPI.
In the profit and loss example above, each floating bar represents a financial account
and the value range for each account is displayed. The chart starts with the main income
account, then for each account that contributes to the net income, the floating bars move
up or down depending on whether the account represents a profit or loss. You can
change the KPI options to see how different options affect your accounts.
You drill to a trend graph for each account by clicking on the account.
Table
The table displays a maximum of 12 periods, regardless of the period selected. For
example, if the period is Week, only 12 weeks are displayed, instead of 52. You can click
Show Full Table to view the complete set of periods. The scorecard designer determines
the default number of periods displayed.
Click on a value in the table to view the comparison graph.
Cause objectives are objectives that directly or indirectly affect the performance of a
reference objective. Effect objectives are the ones that directly or indirectly are affected
by the reference objective. The relationship between cause and effect objectives is defined
by the scorecard designer, and should reflect your organization’s strategic goals.
Information
Additional information can be provided by the scorecard designer for each objective:
• Definition
Description of the objective, why it is important, and what drives its performance.
• Formulas
Description of the formulas used to calculate performance and how to interpret
the formulas.
It is a good idea to include administrative details about how the objectives roll-up
from period to period, or about how values are aggregated.
• Strategy
Description of how the objective relates to your company’s strategy, possibly
including details on cause and effect.
• Action Items
Actions necessary for the objective to be successful. This should provide information
on the due date, budget, resources assigned, and status information for each action
item.
• Objective Owner
The person responsible for the objective performance. This section may also
provide details on the expected duties and responsibilities of the objective
owner. Generally, there is one owner for each objective.
Assessments
The objective owner can use this window to enter qualitative assessments relating to
the performance of an objective. Assessments should complement the quantitative
information provided in the form of plan data, actual data, and triggered alarm colors.
For example, an assessment can provide an explanation of why an objective
under-performed, or why its performance is considered acceptable even if a quantitative
measurement suggests otherwise.
Assessments are labeled with the owner’s name and date. You can optionally specify
the period, if your assessment refers to a specific period.
Users who are not the objective owner should use the Collaboration window to enter
qualitative information on performance.
Collaboration
Any user with access to an objective can use the Collaboration window to enter
qualitative information about an objective. Collaborative comments are particularly
useful if several users have access to the same objectives, or when the same objective
appears on multiple scorecards.
A collaborative comment can include recommended performance improvements,
explanations of performance, or any other feedback.
Each comment is labeled with the user’s name and date. You can optionally specify the
period for the comment, if your comment refers to a specific period.
Printing
When you print a scorecard view or KPI report, the content of the view or report
is automatically optimized for printing by removing any unnecessary headers and
footers. You can additionally optimize the page format using your web browser’s print
options.
The following print options are available:
• Printable Page: Generates a printer-friendly version of a scorecard view or objective
report.
• Print Graph: Generates a printer-friendly version of the graph on the objective
report.
• Print Table: Generates a printer-friendly version of the table on the objective report.