Académique Documents
Professionnel Documents
Culture Documents
windows
Copyright 2008 Business Objects, an SAP company. All rights reserved. Business Objects
owns the following U.S. patents, which may cover products that are offered and
licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250;
5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698;
6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068;
6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189;
6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440;
7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and
its logos, BusinessObjects, Business Objects Crystal Vision, Business Process
On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications,
Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal
Vision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, Table
Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts,
RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are
trademarks or registered trademarks in the United States and/or other countries
of Business Objects and/or affiliated companies. SAP is the trademark or registered
trademark of SAP AG in Germany and in several other countries. All other names
mentioned herein may be trademarks of their respective owners.
Third-party Business Objects products in this release may contain redistributions of software
Contributors licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
2008-09-03
Contents
Chapter 1 Audience 7
Index 163
1
1 Audience
The first section of this guide contains information on creating metric universes
used to build analytics in Performance Manager.
2
2 Performance Manager Administrator's Guide
High-level overview
High-level overview
As an administrator of the performance management products you need to
be familiar with of BusinessObjectsInfoView and with Designer.
Business Objects recommends that you have the guides listed below ready
for reference.
BusinessObjects XI 3.0 Administrator's Guide - provides information and
procedures covering a wide range of administrative tasks.
Designer's Guide - provides complete information on how to use Designer
to design, create, and manage Business Objects universes.
BusinessObjects XI 3.0 Installation Guide - guide provides information
and procedures for installing BusinessObjects, and includes detailed
instructions for the different installation modes available.
A time period is one of the key factors in limiting queries in most deployments
that involve sets and metrics. Therefore, it is essential to consider the type
of SQL used in queries and key date fields.
Set domain: Set Analyzer tables in which sets are stored for the
segmentation engine. These are the tables required to store the Set
Analyzer data. The table names have a SET_ prefix, for example,
SET_SET_DETAIL.
CI_PROBE_VALUE
As with the set domain you can use a simple calculation to determine storage
size using the CI_PROBE_VALUE table for the metric values as follows:
CI_TARGET_VALUE
If you are using Performance Manager the CI_TARGET_VALUE table can also
be of significant size. You can estimate the size as follows:
CI_PROBE_VALUE
The metric domain can also be set up to allow separate table spaces for the
CI_PROBE_VALUE table, which typically grows quite large compared with the
other CI_ tables.
If you plan to use sets in your deployment you must consider the storage
requirement for set membership by answering the following questions:
What type of sets will be used?
What is the size of the sets?
If the sets are dynamic, what are the history requirements and what
turnover is expected?
The following example shows how you can easily estimate the size of the
Set domain of the Dashboard and Analytics repository by creating a test
table.
Example:
100 dynamic sets, an average of 100,000 members, keeping 12 months
of history, with, on average, 25% turnover
Set Analyzer also allows you to set parallel query options that improve
performance, if the database used to host the repository supports this.
Note:
-name string Do not modify -name
for a CMS.
-name Output.UK.
[interface:]
-port
[port]
BusinessObjects En-
terprise XI Release
2 Administrator's
Guide
Metric Universes
Universe overview
A universe is used to represent the underlying data schema used with the
performance management products, allowing a visual view of what can lead
to complex SQL generation. You use Designer to build universes that specify
the SQL used to define metrics. You then usePerformance Manager to create
analytics that use metrics to track performance.
The dashboards and analytics framework supports the ability to build metrics
from multiple universes. This simplifies a system universe by breaking down
the universe structure and creating a new universe for specific subject areas.
For enterprise metrics, multiple universes can be used to select from multiple
data sources.
In the diagram below subject areas 1 and 2 are defined as enterprise metrics,
and subject areas 3 and 4 as set-based metrics. The results of metric
calculations on connections 1 and 2 are written into the dashboard and
analytics repository tables that are located in the same schema as Set
Analyzer , which is Connection 3 in the diagram below.
Enterprise metrics
COUNTRY=England
A fact table is the starting point in creating metrics. In Designer you create
a universe based on the fact table and define a connection to the source
database. You then load the table into the structure pane. You create classes
to organize the measures into groups. You then use this universe in
Performance Manager to create metrics from the measures.
The following image shows a sample sales table that is used to create the
measures that are the basis of the metrics. The table contains a date field,
which is an important element for time-based metrics.
Creating a measure
To define the value for the basis of the metric calculation, in you need to
create a measure object using a field from the fact table. This example uses
the values in the sales_actual column from the sales table.
The select statement for the object, unlike that of an object in a typical
universe, does not contain an aggregate function, that is, sum, max, min,
avg, because you select the type of aggregate when you define the metric.
Creating a measure object
In Designer:
1. Using the "sales_actual " field from the Sales table, create an object.
2. Under the Properties tab, change the object qualification to Measure .
Definition of a filter
In this example we use the filter that is used does not limit the query at all,
which means that the query returns a total of sales on a period by period
basis for all orders in the fact table, Sales. The SQL behind the restriction in
this case is simply a true statement and does not limit the scope of the query.
Defining a filter
In Designer in the "Object Properties " dialog box, click the Properties tab.
1. In Designer in the "Object Properties " dialog box, click the Properties
tab.
2. Modify the object's qualification to Measure .
The SQL reads as follows:
SELECT agrfun(SALES_ACTUAL)FROM SALES WHERE sales.start_date
between @PROMPT ('BEGIN_DATE','D',,mono,free) AND @PROMPT
('END_DATE','D','D',,mono,free) AND 1=1
Once you have created and saved the metric universe, you need to make it
visible to Performance Manager to used as the basis for metric creation. In
Designer, you create a connection for the metadata, then export the universe
to the dashboard and analytics metadata tables.
Before you begin creating metrics in Performance Manager you add this
universe to the list of available universes from the "Universes " page in the
Dashboard and Analytics System Setup.
When you create filter objects you are not restricted to using the fact table
on which the metric is based. You can also use other lookup/dimension
tables.
When you modify a universe by building filters on other tables, you need to
update Dashboard and Analytics metadata with the new structure and objects.
You do this from the Universes page in the Dashboard and Analytics System
Setup by selecting the saved universe and clicking Update. The changes
and new objects are then visible for metric creation.
In the example of a filter created against a dimension table, the metric SQL
generated is:
SELECT agrfunc(SALES_ACTUAL)
FROM SALES, PRODUCT
WHERE sales.start_date between
@Prompt('BEGIN_DATE','D',,mono,free)
AND @Prompt('END_DATE','D',,mono,free)
AND SALES.PRODUCT_ID = PRODUCT.PRODUCT_ID
AND PRODUCT.DESCRIPTION='Motorola Timeport'
Refer to the Dashboards and Analytics online help for information on updating
metrics with changes in target universes.
You may not want users to be able to set aggregate functions or perhaps
using aggregate functions is not possible, for example, in calculating an
average, as in the following SQL statement:
Sum(sales.sales)/sum(sales.volume)
You need to create an Average Sales object in Designer and then edit the
definition of the object in the"Edit Properties" dialog box.
The statement says that the aggregate is already chosen and it is a sum. It
also passes in a description - note that parameters are delimited with a
semi-colon.
When you look at the universe content in Performance Manager you see
that Aggregation has been pre-set and it cannot be modified.
A self-join is used in any generated SQL that involves the table with the
self-join. Using the self-join, however, may not always lead to the desired
results. For example, if you want to calculate a rolling value for the volume
over the past three months, the date restriction needs to take into account
the past three months rather than the fixed one-month, if a monthly calendar
is used.
To achieve the desired result you can use one of two methods that are
explained in the following examples:
Date lookups
Period tables are often included in data warehouses, and are often required
in metric calculation because they contain time-related information.
A common fact table may not always contain true date fields, but may instead
contain date/period ids that provide the foreign key to a period/date dimension
table.
The figure below shows how the system universe can be made to
accommodate such a schema. Note the self-join, placed against the real
(actual) date field in the period table, or date table, in this example.
You need to force performance manager to use the period table, in this case
the dates table, when generating metric SQL. The simplest way to do this
is to modify the tables associated with the measure objects to force use of
the date table hence forcing use of the self-join as shown as follows:
SELECT agrfunc(SALES2.SALES_ACTUAL)
FROM SALES, DATES
WHERE SALES2.DATE_ID = DATE.DATE_ID)
AND DATES.ACTUALDATE between @Prompt('BE
GIN_DATE','D',,mono,free)
AND @Prompt('END_DATE','D',,mono,free)
AND SALES2.DATA_ID = DATES.DATE_ID
Standard dimension objects are then created for promotion_id and pro
mo_description from the "System Setup"against the dimension table. You
add a Global Slice Name in the "Dimension Creation" dialog box. You can
place restrictions on users to allow them to see only specific values.
You then select a measure, an aggregation function, and a dimension to
create a metric. You use these metrics to in Performance Manager to create
an Interactive Metric Trend analytic. The Interactive Metric Trend, which is
a visual representation of the data.
A link appears below the legend that allows the values in the chart to be
sliced. When selected, the Sales Actual value is split into the distinct available
values for promotion. The figure below is an example of a sliced metric.
Set-based Metrics
Set-based metrics
When a set is built, the set information is saved in one of the tables shown
below.
The tables allow you to use different data types in set creation. If the set is
a list of customers, where the customer_id is text-based, the set tables
resemble the figure below.
The structure of this table allows Set Analyzer and the performance
management framework to store membership details over time. Using this
information you can section the set members/non-members into various
sub-sets. The following is an example of a set of customers where the ID is
the customer's name. As this is a character-based key you view
SET_SET_DETAILC. The set is refreshed on a monthly basis starting on
the 1st January 1999.
Example: Period 1
Joiners: Tom, Colin, Fran
Members: Tom, Colin, Fran
Stayers:
Leavers:
When first refreshed, the set contains one row per customer in the set. The
SDATE value is set to the period time at which the set was refreshed. The
EDATE value is set to a default date, which means that the customer has
not yet left the set. This is a reserved date that implies an infinite date; in
the case of Set Analyzer the date used is 1/1/2999.
At this point, the three entries represent three customers who have met the
set criteria for the period and are therefore Members who are Joiners.
Example: Period 2
Joiners: Edd
Members: Edd, Tom, Colin
Stayers: Tom, Colin
Leavers: Fran
In period two, Fran has left the set. Set Analyzer updates the EDATE value
with the current period date to represent this. Another customer, Edd, has
joined the set. Tom and Colin are still members at this time so their records
are not updated. They are Stayers.
Example: Period 3
Joiners: Fran
Period three shows only one change. Fran, the leaver for the second period,
has now met the criteria to be a set member again. Therefore a new row
is entered with the SDATE value as his time of joining and again the EDATE
value as the default for a member. He can now be classified as a re-joiner
as there is historic information on his membership.
Example: Period 4
Joiners:
Members: Fran, Colin
Stayers: Fran, Colin
Leavers: Tom, Edd
Period 4 shows no new joiners, however, the EDATE values for Tom and
Ed have been updated to the current period date. This means they have
left the set, leaving Fran and Colin as stayers/members.
A static (non calendar-based) set does not store the history of a segment's
membership over time. This lack of history means you are able to show
the membership of the set and not be able to break this into segments.
A static set does not store history over time. It is a fixed view of a certain
period in time which explains why it is also known as a snap-shot. For
example, such a set can show all the customers who purchased goods
yesterday. This may change over time but information on who bought goods
three days earlier is not stored.
As with an enterprise universe, you can use a self-join to limit the metric
calculation to the period of metric observation. This can also be defined in
the measure Where clause if required.
The method of passing values into prompts as used in the date restriction
is also used to select the set against which the metric is to be calculated.
The self-join syntax rules apply as with the date prompts, for example, a
case-sensitive string match.
For example, in the set Collector, a dynamic set with membership history,
you can select behavioral subsets, such as Members, Joiners, Stayers, and
Leavers.
The filters under the Customer T class are used for dynamic sets with
time-based history. The members definition illustrates use of begin date and
end date prompts. In this case, the dates indicate whether the customer
entered the set in the current period or an earlier one, and whether or not
he left after the end date of the current period. These dates determine whether
the customer is in the set during the observation period.
Once you have saved the universe you can make it available to the
performance management framework as you would an enterprise universe.
As with the enterprise universe, you can use a self-join to limit the metric
calculation to the period of metric observation. The period of metric
observation can also be defined in the measure WHERE clause if required.
The method of passing values into prompts as used in the date restriction
is also used to select the set against which the metric is calculated. The
following example shows the self-join syntax. The string match is
case-sensitive.
The measure Sales Actual is defined for set-based metrics in the same
way as for enterprise universe. However, a measure called count is
introduced in the set -based universe. This example shows the measure
definition of count. Note the aggregate is preselected and the count is of
the unique id, in this example, customer_id.
The filters under the Customer T class are used for dynamic sets with
time-based history. The members definition illustrates use of begin date and
end date prompts. In this case, the dates indicate whether the customer
entered the set in the current period or an earlier one, and whether or not
he left after the end date of the current period. These dates determine whether
the customer is in the set during the observation period.
Once you have saved the universe you can make it available to the
performance management framework as you would an enterprise universe.
Below is the SQL for each of the four basic subset filters:
Members
Joiners
Stayers
Leavers
and
TSET_BEGIN_DATE
and
END_DATE
Below are descriptions of the filters in the Customer T section of the universe.
Members
FILTER=M; DESC=Members at the end of the period
CI_TID_01.sdate <= @Prompt('TSET_END_DATE','D',,mono,free) and
CI_TID_01.edate > @Prompt('TSET_END_DATE','D',,mono,free)
Joiners
FILTER=J; DESC=Members at the end of the period that were not members
at the end of the previous period
CI_TID_01 = @Prompt('TSET_BEGIN_DATE','D',,mono,free)
Joiner (p) is a member at the end of the period (p) that was not a member
at the end of the previous period.
Stayers
FILTER=S; DESC=Members at the end of the period that were members at
the end of the previous period
CI_TID_01.sdate < @Prompt('TSET_BEGIN_DATE','D',,mono,free)
and CI_TID_01.edate > @Prompt('TSET_END_DATE','D',,mono,free)
Stayer (p) is a member at the end of the period (p) that was a member at
the end of the previous period.
Leavers
FILTER=L; DESC=Non-members at the end of the period that were members
at the end of the previous period
CI_TID_01.edate = @Prompt('TSET_BEGIN_DATE','D',,mono,free)
Leaver (p) is a Non Member at the end of the period (p) that was a member
at the end of the previous period.
Example:
You can apply a quarterly metric to a segment that identifies monthly high
revenue customers to show the total revenue for these customers. These
are calculated using the filters in Customer T2.
Types of subsets
Below are the SQL definitions for each of the subset types followed by a
description of what the SQL does.
Members
FILTER=M; DESC=Members at the end of the period
CI_TID_01.sdate <= @Prompt('TSET_END_DATE','D',,mono,free) and
CI_TID_01.edate > @Prompt('TSET_END_DATE','D',,mono,free)
In the scenario shown below the customer joined in p2 and left the segment
at p9, and was definitely a member during the period of observation (p4, p5
and p6).
Joiners
FILTER=J; DESC=Members at the end of the period that were not members
at the end of the previous period
CI_TID_01.sdate <= @Prompt('TSET_END_DATE','D',,mono,free) and
CI_TID_01.edate > @Prompt('TSET_END_DATE','D',,mono,free) and
CI_TID_01.id not in ( select set_set_detail.id from
set_set_detail where set_set_detail.sdate < @Prompt('TSET_BE
GIN_DATE','D',,mono,free) and set_set_detail.edate >=
@Prompt('TSET_BEGIN_DATE','D',,mono,free) and set_set_de
tail.setversion_id = @Prompt('SET_VERSION','N',,mono,free) )
Joiners must:
Not be present during the start of the period of observation.
Be present at the end of the period of observation for the metric.
If both these criteria are met the customers are classified as joiners. In the
diagram below, the period of observation starts at p4 and ends after p6. A
joiner is, then, a customer who is not present in p3, but who is present at the
end of p6.
Stayers
FILTER=S; DESC=Members at the end of the period that were members at
the end of the previous period
CI_TID_01.sdate <= @Prompt('TSET_END_DATE','D',,mono,free) and
CI_TID_01.edate > @Prompt('TSET_END_DATE','D',,mono,free) and
CI_TID_01.id in ( select set_set_detail.id from set_set_detail
where set_set_detail.sdate < @Prompt('TSET_BE
GIN_DATE','D',,mono,free) and set_set_detail.edate >=
@Prompt('TSET_BEGIN_DATE','D',,mono,free) and set_set_de
tail.setversion_id = @Prompt('SET_VERSION','N',,mono,free) )
Leavers
FILTER=L; DESC=Non Members at the end of the period that were members
at the end of the previous period
CI_TID_01.id not in ( select set_set_detail.id from
set_set_detail where set_set_detail.sdate <=
@Prompt('TSET_END_DATE','D',,mono,free) and set_set_detail.edate
> @Prompt('TSET_END_DATE','D',,mono,free) and set_set_de
tail.setversion_id = @Prompt('SET_VERSION','N',,mono,free) )
and CI_TID_01.sdate < @Prompt('TSET_BEGIN_DATE','D',,mono,free)
and CI_TID_01.edate >= @Prompt('TSET_BE
GIN_DATE','D',,mono,free)
Leavers are present at the start of the period of observation but not at the
end. In the diagram below, leavers are present at the start of p4 and absent
at the end of p6.
Multiple fact tables are easily handled in the metric universe. The following
figure shows the customer subject area extended to encompass the
complaints fact table.
The figure below shows a completed system universe that allows metrics to
be built against sets of customers and sets of products. The product key is
character-based, therefore, SET_SET_DETAILC is used to hold set
membership information.
The schema for product is very similar to that of the customer subject area.
All prompt syntax is identical, and the only difference is the use of the aliases
of CI_PERIOD and the sales table, and the inclusion of the product table.
Advanced Topics
Metrics on metrics
Note:
This can cause additional overhead should metrics be changed in the future.
The figure below shows the tables with the appropriate joins to calculate
metrics against metrics using the statistical transformation tables. The self-join
on the table ci_period_stat.period_date follows the same syntax as the
fact table self-joins.
Tip:
When you refresh metrics first refresh the initial metric and the refresh the
metric that is based on the initial metric. Business Objects recommends that
you create a rule to refresh the second metric each time the first is refreshed.
The rules engine contains a function builder that allows access to metric
values. You query the metric values directly and do not use the system
universe.
Example:
MetricValue(metric1.id) > MetricValue(metric1.id, -1)
If the current value of metric1 is greater than the value of metric 1 for the
last period.
Example:
MetricValue(metric1.id) > MetricValue(metric1.id, -12)*1.1
If the current value of metric1 has increased by 10% over the value of
metric1 twelve months earlier.
Example:
ForecastCubic(MetricValues(metric1.id, 6), 7) > MetricValue(met
ric1.id)
Take the last six values of metric1 and forecast the seventh point using a
cubic line fit, then compare values to see if the current metric value is below
this forecast.
This section explains how to create a universe for control chart analysis. You
must have a working knowledge of process control charts and universe
design.
The examples used below are taken from the manufacturing sample universe
included with the performance management installation.
Measures
Measure objects in the universe are used by control charts to calculate the
actual data points on the control chart. Each control chart uses either one
or two measures to calculate its data points. During configuration, you select
the measure object or objects that are used in the control chart calculation.
Then, you organize these objects in classes that are translated into subject
areas.
Each measure comes from a fact table that contains the raw data. This raw
data may be at transactional level or aggregated. In the manufacturing
example, the tables individual_measurement, defect, reject, and inspection
are used as fact tables. For example, the fact table individual_measurement
is used to construct variable control charts. In the figure shown below a
number of measure objects have been created in a class called Manufacturing
Variable.
Self-joins
Each fact table must include a self-join that is used to select values during
sampling. The self-join is on the date stamp column of the fact table and
follows this exact syntax. Changes in case and spaces can cause this self-join
to fail.
In the Expression box of the Edit Join dialog box type the following SQL:
<date stamp column> between
@Prompt('BEGIN_DT','D',,mono,free) AND
@Prompt('END_DT','D',,mono,free)
Breakdown variable
Breakdown variables are used to automatically generate control charts for
each value in a dimension. For each breakdown variable that is used, a
dimension object needs to be created in the appropriate class in the universe.
Filters
Filters are used to limit a particular control chart (or set of control charts for
a breakdown variable) to a particular set of data. Control chart filters are
based on combinations of conditions that are created in the universe. In the
manufacturing example, the conditions include those that limit control charts
to particular product type, as shown below.
The conditions can be based on columns directly on the fact table, or any
table that is joined to the fact table. When designing conditions, bear in mind
that control chart filters that are configured in Performance Management can
combine conditions together.
For p, np, and u charts you can draw the measures that are used in
calculating control chart points from two different fact tables. In p charts, for
example, the value on the control chart is calculated based on the number
of rejects, which may come from one table, and the number of inspections,
which may come from another table. When two tables are involved they both
need to be constrained by a common filter that is based on common
conditions.
Systematic sampling
If systematic sampling is required in a particular subject area, a dimension
object is needed in the appropriate class based on the timestamp column in
the fact table. For the manufacturing example the Measurement Time object
Note:
Remember to include the self-joins in the relevant context.
3
3 Performance Manager Setup and Administration Online Help
Dashboard and analytic applications
Business Objects offers the following tools to help you mine your data for
trends:
Dashboard Builder
Performance Manager
Set Analysis
Predictive Analysis
Process Analysis
Mandatory tasks
Create the Performance Manager repository.
The Performance Manager repository stores the metrics, goals and
calendars leveraged across your deployment.
Define the system users.
System user accounts initialize the Dashboard and Analytics servers and
enable the Dashboard and Analytics application engines.
Connect to a universe.
Universes provide the semantic layer that maps familiar business terms
to your corporate data sources.
Note:
Users can also define metrics manually. To find out how to do this, see
the Performance Manager documentation.
Define calendars.
The calendar time periods you define are used to build the aggregated
measure results for metrics over time. This allows users to perform
time-series analysis on KPIs. You can create standard calendars or import
custom calendars adapted to your business processes.
Optional tasks
For more powerful analysis, you can also:
Associate users to dimensions.
Create associations to allow users to analyze sliced metrics, where the
value for the metric is broken down by the values on a dimension, and
lets you secure dimensions by granting access to slices to users, so that
specific users can only see results for certain slices.
For example, you could select the [Sales] metric and slice it by the
[Region] dimension in order to analyze sales per region. You could then
secure the [Region] dimension so that users working in a specific regional
sales office could only see sales results for their region.
Apply statistical calculations such as moving average, difference, or rollup
to selected calendars.
You use statistical calculations for smoothing and aggregating time-series.
For more information, see the chapter in the documentation about
Performance Manager calendars.
Related Topics
Overview of the Dashboard and Analytics deployment on page 65
Moving averages in calendars on page 105
Rollups in calendars on page 113
The Performance Manager repository on page 65
Dashboard and Analytics system users on page 77
Metric universes on page 79
Related Topics
Individual Profiler portrait properties on page 127
In Dashboard and Analytics Setup > Parameters > Options, set the
following options:
Mail Parameters
These parameters contain details of the Dashboard and Analytics SMTP
server, port number, and email address used to send automated emails
for alerts, rules, and generated lists.
Web Parameters
You need to specify mail parameters so that users can use the email features
within Dashboard and Analytics applications. For example, users can build
rules, alerts, and lists that generate emails and have the ability to email some
of the analytics.
1. Go to Dashboard and Analytics Setup > Parameters > Options.
2. In the "Mail Parameters" section, configure the following parameters:
"Outgoing SMTP server"
Type the name of the Dashboard and Analytics server from which
automated emails, such as email alerts and email lists, are sent.
"SMTP Port Number"
Enter the port number of the SMTP (Simple Mail Transfer Protocol)
server.
"From Address"
Type the email address of the SMTP server that appears in the "From"
field in email messages.
"Reply to Address"
Type the address to which automatic replies are sent. This is usually
the same as the "From Address".
3. Click Apply.
Any modifications you made are applied the next time you restart the
Dashboard and Analytics server.
By default, the web server used for Dashboard and Analytics applications is
the same server on which Dashboard and Analytics is installed. The "Web
Parameters" options allow you to specify a remote web server. If you
performed a custom installation and defined a custom URL for end users to
use to access the InfoView login page, then you need to type the custom
URL you defined here.
Note:
For information on performing a custom installation, see the BusinessObjects
Enterprise installation guide available at: http://support.businessob
jects.com/documentation.
1. Go to Dashboard and Analytics Setup > Parameters > Options.
2. In the "Web Parameters" section, configure the following parameters:
"Web server host name"
Type the name of the web server that host Dashboard and Analytics
applications.
"Web server port number"
Enter the port number of the host web server.
"Performance Manager URL"
Type the URL that end users use in their web browser to launch the
InfoView home page.
Note:
We recommend that you compare performance of processing the XLS
transformations on the client against processing the XLS transformations
on the server, in order to make the best decision for your deployment.
The optimum choice can differ depending on the client machines used
on your deployment and the number of concurrent users taxing the server.
4. Click Apply.
Any modifications you made are applied the next time you restart the
Performance Manager server.
Related Topics
Specifying general parameters in Dashboard and Analytics Setup on
page 59
Specifying general parameters in Dashboard and Analytics Setup
1. Go to Dashboard and Analytics Setup > Parameters > Options.
2. In the "General Parameters" section, configure the following parameters:
"Number Format"
Select a number format for analytics and dashboards.
"Date Format"
Select the date format for analytics and dashboards.
"Maximum Number of Columns for Optimized SQL"
Select a number to apply to SQL queries for analytics and documents.
The option allows Dashboard and Analytics to group SQL from columns
in the same table, for the number of columns you specify, and so
optimizes the calculation process.
"Individual Profiler Maximum Query Size"
Select the limit for the maximum number of rows returned for an
Individual Profiler query.
"BusinessObjects Enterprise Events Polling Time"
Select the amount of time between two polling events, measured in
seconds. The option specifies how often Dashboard and Analytics
checks for an event on the Events server in the CMC, and therefore
ensures that any new external events on the CMC are written to the
Performance Manager repository for use in rules and alerts.
3. Click Apply.
Any modifications you made are applied the next time you restart the
Dashboard and Analytics server.
Related Topics
Individual Profiler portrait properties on page 127
If their security profile allows, end users can schedule Dashboard and
Analytics tasks, such as refreshing metrics. As an administrator, you can
specify the location of the directory used to cache scheduler processes and
specify the user account associated with the processes.
1. Go to Dashboard and Analytics Setup > Parameters > Options.
Note:
If you change the parameters, any existing schedules become
incorrect. To update the definition of existing schedules to the new
schedule parameters, run the "Scheduled Programs""Check &
Cleanup" tool at Dashboard and Analytics Setup > Tools > Check
Integrity and Cleanup.
3. Click Apply.
Any modifications you made are applied the next time you restart the
Dashboard and Analytics server.
3. Select the engine for which you want to specify the minimum number of
open database connections:
Analytics
The Analytics server renders the analytics by querying the metrics
metadata and then generating the desired visualization in the format
of the selected analytic.
Repository Management
The repository manager manages the Performance Manager repository
including user security and privileges, updates to the system
parameters, and writing new metrics and rules back to the repository.
Process Analysis Engine
Process Analysys uses this engine.
Metrics Engine
The metrics engine works like an ETL tool to extract each metric value,
aggregate it, and then load it into the metadata layer on the
Performance Manager repository.
Mining Engine
Predictive Analysis uses this engine.
Rules Engine
The rules engine evaluates conditions placed against metrics, goals,
sets and then outputs sending events to other components.
Query Manager
The query manager performs Set Analysis queries and builds and
processes sets.
Profiler
The Individual Profiler uses this engine.
4. Enter the number of connections you want open concurrently for the
selected engine into the "Minimum Number of Database Connections
Kept Open" text box.
5. Click Apply.
Any modifications you made are applied the next time you restart the
Dashboard and Analytics server.
The cache refresh period settings determine how often Dashboard and
Analytics refreshes the server caches with the latest values on the
Performance Manager repository and the Central Management Server (CMS).
If you launch Dashboard and Analytics and an error message appears that
says that you cannot connect to Dashboard and Analytics, it is for one of the
following reasons:
Some of the Dashboard and Analytics servers are stopped or disabled.
The Initialization User that creates the Dashboard and Analytics server
proxies was defined inconsistently in the Central Management Server,
InfoView, and the InitConfig.properties file.
1. Log into the Central Management Console (CMC), and then click Servers.
2. Verify that all the Dashboard and Analytics servers are started.
3. If a server is not running, select the check box next to the server name,
and then click Start.
4. Make sure that all servers are enabled.
If a server is not enabled, select the check box next to the server name,
and then click Enable.
Related Topics
Performance Manager servers on page 55
2. Log into InfoView, and then click the "Preferences" button on the InfoView
toolbar.
3. In the "Dashboard and Analytics" tab, check the name of the initialization
logon user in the "Change initialization logon user" section is the same
as that specified in the InitConfig.properties file.
4. Log into the Log into the Central Management Console (CMC), and then
click Users.
5. Check that the user defined in the InitConfig.properties is listed among
the users.
Related Topics
Creating the Performance Manager repository on page 67
Note:
In previous Dashboard and Analytics versions, the Performance Manager
repository was called the Performance Management repository and the
Application Foundation repository (or AF Repo). In Application Foundation
6.x versions and earlier, the equivalent to the CMS was the BusinessObjects
repository.
If this is the first time you have installed the Dashboard and Analytics
applications, you need to create a connection to the database on which you
want to store the Performance Manager repository. You do this using
Designer.
1. Launch Designer.
2. In the "Connections" list, select Tools > Connections, then click Add.
3. Follow the instructions in the "New Connection Wizard".
For full information, consult the Designer documentation about working
with connections.
Related Topics
Performance Manager repository migration on page 71
Verifying the connection to the Performance Manager repository on
page 68
Note:
If this is the first time you have installed Dashboard and Analytics, you need
to create a connection to the Performance Manager repository.
1. Go to Dashboard and Analytics Setup > System Setup > Repository.
2. In the "Repository Information display" section, click Check.
If there is a problem with the connection, an error message provides
details.
Related Topics
Creating a connection for the Performance Manager repository on page 67
You need a connection to the target database before you can deploy the
system tables.
To deploy the system tables to the target database you have chosen as the
Performance Manager repository:
1. Go to Dashboard and Analytics Setup > System Setup > Repository
> Repository Information.
2. Click the drop-down arrow next to connection name.
3. Select the target database from the drop-down list.
The "System Tables Management" display section advises you whether
the system tables have been installed or not. If an earlier version of the
product has been installed, the module detects it and suggests an
upgrade. To upgrade the repository, click Upgrade.
Related Topics
Creating a connection for the Performance Manager repository on page 67
The repository options let you specify settings optimized for the type of
database you are using for the Performance Manager repository. You can
view the options applied to the repository and change the options if necessary.
1. Go to Dashboard and Analytics Setup > System Setup > Repository
and click View Options.
The selected encoding appears in the "Encoding" box.
Note:
By default, the encoding for Dashboard and Analytics is Unicode (UTF-8).
For encoding other than Unicode (UTF-8), the database and the processes
go through a convertor, so performance is slower.
2. To change the encoding, click the arrow next to the "Encoding" box, and
select the appropriate encoding from the list.
Note:
For certain databases, the following advanced options are activated and
allow you to customize the repository environment:
Tablespace
Index Post Script
Numeric Keys Precision
Use Long Integer Fields
Related Topics
Creating a connection for the Performance Manager repository on page 67
Creating the Performance Manager repository on page 67
You can also point your Dashboard and Analytics server to a different CMS.
This is particularly useful if your deployment includes multiple CMS databases
used for different environments. For example, you may have one CMS for
your development environment and another CMS for your production
environment.
Note:
For information on how to setup CMS authentication, refer to the
BusinessObjects Enterprise administrator's guide available at:
http://support.businessobjects.com/documentation.
To modify parameters in Dashboard and Analytics Setup you need to
be logged into InfoView as an administrator.
2. If you want to redirect to another CMS, type the name of the CMS using
the following syntax:
<server_name>.<server_domain>
3. If you want to select a different authentication, click the arrow next to the
"Authentication" box and select the type of authentication you want from
the list.
Performance Management XI to
BusinessObjects Enterprise installa-
Performance Management XI R2 and
tion guides
higher
Tip:
All documentation is in Adobe PDF format and available at: http://support.busi
nessobjects.com/documentation.
In Dashboard and Analytics Setup > Tools the "Check Integrity and
Cleanup" section allow you to perform an integrity check on the following
information stored in the Performance Manager repository:
Universes
The metric universes stored on the Performance Manager repository.
Rules
The rules set up using Performance Manager.
Metrics
The metrics defined using Performance Manager.
Alerts
Email alerts (triggered by events) created using Performance Manager.
Users
User accounts already defined in the system.
Note:
You cannot remove users while they are logged into "Dashboard and
Analytics".
Predictive Analysis
These tools help you to remove faulty or redundant data from the
Performance Manager repository.
Note:
Erasing any of the entries physically removes them from the Performance
Manager repository database.
Checking the integrity of the metric universes enables you to ensure that the
universes used to define Dashboard and Analytics metrics work correctly.
1. Go to Dashboard and Analytics Setup > Tools.
2. In the "Check Integrity" section, click Universe.
The "Check Integrity" window appears.
Checking rules allows you to ensure that any rules based on events, created
by Dashboard and Analytics users, function correctly.
1. Go to Dashboard and Analytics Setup > Tools.
2. In the "Check & Cleanup" section, click Rules.
Any rules that include errors are listed. You can delete rules here or modify
rules in Performance Manager.
3. To delete a rule, select the rule you want to delete and click Erase.
Note:
To modify a rule, exit Dashboard and Analytics Setup, open Performance
Manager and in the "Rules" tab, select the rule and click Edit. See the
Performance Manager documentation for information on editing rules.
Checking metrics allows you ensure that the metrics created and analyzed
by Dashboard and Analytics users function correctly.
1. Go to Dashboard and Analytics Setup > Tools.
2. In the "Check & Cleanup" section, click Metrics.
The "Check & Cleanup Metrics" window appears.
4. To delete a metric, select the metric you want to delete and click Erase.
Checking users allows you to remove user accounts that fail the integrity
test from the Central Management Server (CMS).
1. Go to Dashboard and Analytics Setup > Tools.
2. In the "Check & Cleanup" section, click Users.
The "Check & Cleanup Users" window appears. Any user profiles that
contain errors are flagged here.
3. To find out more information about an error click the user name.
The errors are detailed in the "Check Details" section.
4. To delete a user, select the user you want to delete and click Erase.
Note:
You cannot delete users who are currently logged into Dashboard and
Analytics.
You can check the integrity of the populations, variables, binnings, models,
and advanced metrics defined using Predictive Analysis.
1. Go to Dashboard and Analytics Setup > Tools.
2. In the "Check & Cleanup" section, click Predictive Analysis.
The "Check & Cleanup Predictive Analysis" window appears.
3. Click the drop down arrow next to the list box at the top of the window,
then select the subject area for which you want to make the integrity
check.
Any populations, variables, binnings, models or advanced metrics that
include errors are listed and more information about each error is provided
in the "Check Details" section.
4. To delete a service, select the Predictive Analysis service you want to
delete and click Erase.
Note:
You cannot delete users who are currently logged into InfoView.
Note:
The schedule parameters can be modified in Dashboard and Analytics
Setup > Parameters > Options > Scheduler Parameters.
It is recommended you check the parameter integrity whenever the Scheduler
Parameters are modified, so that any existing scheduled programs are
updated to match the new parameters.
Note:
To modify the users defined in Dashboard and Analytics Setup, you need to
be logged into InfoView as an administrator.
Note:
The system user must have Administrator rights specified in the Central
Management Console (CMC). For information on how to set security rights
for Dashboard and Analytics, see the BusinessObjects Enterprise
administrator documentation.
1. Go to Dashboard and Analytics Setup > System Setup > System
User.
2. In the "System User" section, type Administrator in the "User Name" text
box.
3. In the "Password" box, type the password.
By default, there is no password for Administrator. It is strongly
recommended that you define a password for the Administrator user. See
the BusinessObjects Enterprise administrator documentation for
information on passwords.
4. To verify that the CMC recognizes the user as a user with administrator
rights, click Check.
Note:
If an enterprise authentication error appears, the user name you entered
does not have Administrator rights allocated to it in the CMC. You need
to either launch the CMC and modify the security profile of the user, or
enter a different user name that already has administrator rights in the
CMC.
Specifying a Set Analysis guest user enables all valid Dashboard and
Analytics users to use sets. End users who do not have a profile to create
sets automatically borrow the Set Analysis guest user profile when they open
Dashboard and Analytics. The guest user allows users to visualize sets
for metric creation and analysis.
Note:
Before you can define the Set Analysis guest user, you need to set a user
in the Central Management Server (CMS) that has all of the Set Analysis
features enabled. You create the user in the CMS in the Central Management
Console. For information on how to do this, refer to the BusinessObjects
Enterprise administrator documentation.
You need to then create the same user in Set Architect, the Windows setup
application designed for Set Analysis. For information on how to set up the
Set Analysis guest user in Architect, refer to the Set Architect online help.
1. Verify that the Set Analysis guest user exists on the CMS and has all the
Set Analysis features enabled.
2. Verify that the same Set Analysis guest user is defined in Architect.
3. Go to Dashboard and Analytics Setup > System Setup > System
User.
4. In the "Set Analyzer Guest User" section, type the guest user name in
the "User Name" text box.
Note:
The Set Analysis guest user you type here must also be set up as a guest
user in Architect.
Note:
For security reasons, it is recommended that you do not allocate Administrator
rights to the Initialization user and that you do not re-use a real user profile.
The default user ID is PMUser, defined as a member of the Everyone user
group.
1. Go to Dashboard and Analytics Setup > System Setup > System
User.
2. In the "Initialization User" section, type in a valid user in the User Name
text box.
3. In the "Password" box, type the password.
4. To verify that the user is recognized by the Central Management Server
(CMS) as a user with Dashboard and Analytics rights, click Check.
Note:
If an enterprise authentication error appears, this means that the user
name you entered does not exist in the CMS. If this is the case, you need
to launch the Central Management Console, create the user, and assign
that user Everyone rights. You can then return to step 1, above.
Metric universes
The data for metrics can be supplied from metric universes built using
Designer or from data entered manually using Performance Manager.
Related Topics
About metric universes on page 80
Making metric universes available to Dashboard and Analytics users on
page 81
Metric universes contain the metrics and goals used by Dashboard and
Analytics users across a deployment. When you design universes for use
with Dashboard and Analytics, you need to follow specific design guidelines
to generate metrics.
For example, metric universes include a time parameter that allows users
to associate values of a specific calendar to the metric they want to analyze.
To create a time parameter, you need to define a query condition on a date
object.
Note:
The Performance Manager repository allows 34 characters as the maximum
length of the universe name.
Each time a metric is refreshed, the metric values for the selected calendar
are stored in the Performance Manager repository. This lets users analyze
metrics over time, and so perform time-series analysis on KPIs.
Note:
On metric universes, aggregates do not need to be defined for measures at
the universe level. This lets users apply different aggregate calculations
when they build metrics on the measures in Dashboard Builder. However,
if you select a metric universe to build an ad hoc query, using Web
Intelligence for example, measures are aggregated at the report level and
thus slow down the query run time.
Once you have a universe defined in Designer, you need to make the
universe available to Dashboard and Analytics users by following these steps:
export the universe to the Central Management Server.
Note:
You build metric universes using Designer. For step-by-step information on
how to do this, see the Designer documentation, available at: http://sup
port.businessobjects.com/documentation.
Related Topics
Adding a universe in Dashboard and Analytics Setup on page 82
A universe is the semantic layer that maps familiar business terms to table
structures in a database. Dashboard and Analytics users to select data from
universes for metrics and analytics.
Dashboard and Analytics users select source data from universes for metrics
and analytics. To make a universe available to end users, you need to add
the universe to the Performance Manager repository.
When you add a universe, certain elements that Dashboard and Analytics
applications need to build the SQL for the metrics are taken from the system
database and stored on the Performance Manager repository in the following
ci_ system tables:
ci_source contains the reference to the universe name
ci_subject contains the class names
ci_variable contains the names of the objects
ci_condition contains the conditions (or query filters)
1. Go to Dashboard and Analytics Setup > System Setup > Universes.
2. Click Add Universe.
3. In the "Add a Universe" panel, select a universe.
If the universe does not appear, click the refresh icon next to the "Measure
Universe" list box to refresh the list of available universes. The name of
the universe and the name of the folder where the universe is located
appear in the "Name" and "Folder" boxes.
4. Click OK.
A message appears confirming that the universe has been added
successfully.
4. Click Update
The information on the universe in the Performance Manager repository
is updated.
Note:
If you have metrics or goals based on a universe you want to delete, a
message appears proposing to remove these metrics and goals along with
the universe itself.
1. Go to Dashboard and Analytics Setup > System Setup > Universes
> Universe Definition.
2. Select the universe you want to remove.
3. Click Remove Universe.
4. If metrics and goals refer to the universe, a message appears that
suggests that you remove these metrics and goals along with the universe
itself.
5. If no warning message appears, click OK.
You can view the objects, sets, and filters on metrics universes once you
have pushed the universe to the Performance Manager repository. You can
check that any changes you have made to a universe are reflected in the
pushed universe on the Performance Manager repository.
You can:
view the measures and dimensions to verify the SQL for the measures
on universes.
view the conditions and subsets to see the descriptions of conditions (or
query filters) and subsets.
Note:
If you notice anything incorrect, you can open the universe using Designer,
and then make the necessary corrections. Information this is provided in the
Designer documentation at http://support.businessobjects.com/documenta
tion.
Field Description
Note:
The ci_probe_value is initially empty.
6. Populate the following columns in the ci_probe table (all other columns
are updated when the metric is created):
end_date- 6/1/2000
where the date is 6/1/2000 until you have populated the data in
ci_probe_value table. In the following example the column tells the user
at what time the metric was refreshed.
refresh_date- 11/15/2006 4:47:01 PM
Related Topics
Adding a universe in Dashboard and Analytics Setup on page 82
Updating a universe in Dashboard and Analytics Setup on page 83
For example, when you refresh the Sales Revenue sliced by the Country
dimension, sales revenue is calculated and returned for each country in the
metric universe.
Dimensions can be associated with specific user profiles so that users can
only view certain slices of data. This could be useful in an extranet situation,
or when different departments in a company need to see different slices of
a specific metric by product line, or region, for example.
Related Topics
Editing the user association of a dimension on page 96
Before you create a sliced metric, you must define dimensions in the metric
universe using Designer. When you create a sliced metric by applying a
dimension to a metric, the total value of the metric is calculated, as well as
an individual value for each slice (for each dimension value).
Tip:
For information on defining dimensions on universes, see the Designer
documentation available at: http://support.businessobjects.com/documenta
tion.
When a sliced metric is calculated, two SQL statements are executed:
a statement for the total value of all slices of the metric
a statement that includes a GROUP BY statement based on the dimension
that returns a distinct result for each slice, for each value of the dimension
object
For example, if you create a dimension object for product line on the Revenue
metric, refreshing the metric executes one SQL statement to calculate total
revenue, and one SQL statement with a GROUP BY statement on the product
line object, resulting in the display of revenue for each product line.
stores the actual value of the metric for each distinct slice
ci_probe_val for the defined time period.
ue
Note:
No row is created for a slice that returns no data.
Note:
Since values are returned for each slice and stored in the Performance
Manager repository, Business Objects does not recommend creating a sliced
metric on a dimension with a large number of distinct values.
A dimension for use on a metric is typically built using two dimensions defined
in the universe:
dimension code: a short name used for the GROUP BY clause and joins
dimension description: the long name used in displaying the slice
Creating a dimension
Note:
Since values are returned for each slice and stored in the Performance
Manager repository, Business Objects does not recommend creating a sliced
metric on a dimension with a large number of distinct values.
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Click Add.
3. In the Create Dimension panel, type a name for the new dimension.
4. To define a sliced metric for this dimension, click Yes, I want to create
sliced metrics on this dimension and select objects.
5. Click Next.
6. If the dimension has a sliced metric, click Refresh to list all the slices in
your dimension, then Next.
The slice names and slice codes are listed. You can also change the title
of the dimension in this panel.
Related Topics
Configuring a dimension association on page 92
Sliced metrics for a dimension on page 91
4. Select the universe object to use for the dimension name from the "Object
for dimension name" list.
This name is typically a long name that helps you identify the individual
slices.
5. Select the universe object to use for the dimension code from the "Object
for dimension code" list.
This object is typically a numeric key or shortened name used for the
group by and joins.
6. In the "Global slice name" text box, type a name that refers to the set of
all slices of the metric.
For example, if you are slicing on regions, you name the global slice All
Regions.
Related Topics
Creating a dimension on page 90
An association dictates which users can access which slices. You can use
an association to personalize the content of an analytic (to show only the
data that interests the user) or to secure sliced metrics (by limiting the data
that different users or groups of users can access).
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Click Add.
3. In the "Create Dimension" panel, define the dimension name.
4. Click Next.
Note:
If you are using a sliced metric for the dimension, you first refresh the
sliced metrics and then you are asked to select the association.
Related Topics
Sliced metrics for a dimension on page 91
Creating a dimension on page 90
Importing users from a universe to secure dimension
This process shows you how to import users from a universe to create an
association on a dimension.
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Click Add to create a dimension.
3. In the "Create Dimension" panel, you define the dimension name, click
Next.
4. Select Read from a database and click Next.
5. Select the universe containing user information from the list.
If necessary, click Refresh to refresh the list of available databases.
6. From the "Object for User Name" list, select the universe object (the
database column) that contains the user name.
7. From the "Object for Dimension Name" list, select the universe object to
use for defining the dimension name.
8. From the "Object for Dimension Code" list, select the universe object to
use for defining the dimension code.
9. Do one of the following:
Click End to confirm the user import from a universe.
Click Previous to return to earlier screens.
Click Cancel to cancel the dimension creation.
10. For each user in "Available Users" list, identify the default slice by
activating Default.
11. Do one of the following:
Click End to confirm the manual user import.
Click Previous to return to earlier screens.
Click Cancel to cancel the dimension creation.
Editing a dimension
You can edit the definition of a dimension, or simply edit the user association
of a dimension.
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Select a dimension from the list and click Edit.
The Update Dimension window appears.
3. Optioinally, you can modify the dimension name and the global slice
name. All other boxes are grayed out.
4. Click Next.
5. Optionally, click Refresh to list all the slices in a dimension, or change
the name of the dimension.
The slice name sand slice codes are listed.
6. Click Next.
In the next screen, you have the option of editing the association defined
for the dimension. An association dictates which people can access which
slices. Use an association to personalize the content of an analytic, or to
secure sliced metrics by limiting the data that different users or groups
can access.
7. Choose an association option.
An association dictates which users can access which slices. You can
use an association to personalize the content of an analytic (to show only
the data that interests the user) or to secure sliced metrics (by limiting
the data that different users or groups of users can access).
8. Do one of the following:
Click End.
Click Previous to return to earlier screens.
Click Cancel to cancel the dimension edit.
Related Topics
Editing the user association of a dimension on page 96
Configuring a dimension association on page 92
An association dictates which users can access which slices. You can use
an association to personalize the content of an analytic (to show only the
data that interests the user) or to secure sliced metrics (by limiting the data
that different users or groups of users can access).
If you did not define an association when you created the dimension, you
can edit the association later.
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Select the dimension from the list of available dimensions.
The dimension's current associations are listed in the bottom pane (if you
did not define associations for the dimension, this pane is empty). The
pane displays the user associated to each slice, and the slice name and
slice code of the slice to which the user is associated.
Related Topics
Configuring a dimension association on page 92
Removing a dimension
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Select the dimension from the list.
3. Click Remove.
For each data source subject you can choose a dimension to use for
individual security.
Individual security enables you to limit what users see based on a specific
dimension. Once you create dimensions, you can select a dimension for
each data source on which you want to apply Individual security. The
dimension you select, along with its associations, are applied as the secured
dimension of the data source, and dictate which data individual users can
access.
1. Go to Dashboard and Analytics Setup > System Setup > Dimensions.
2. Click Individual Security Setup at the bottom of the page.
The "Individual Security" window appears.
3. In the "Subject" pane, select the data source on which you want to apply
a secured dimension.
The available dimensions for the selected data source are listed in the
"Secured Dimension" pane.
4. Select the dimension with which you want to secure the data source.
5. Click OK.
Sliced metrics
Once you have created dimensions, you can slice metrics on them.
Analytics calendars
Most metrics are measured against a timeline, so you must create calendars
against which you can calculate metric values. You can create the calendars
based on the following types of periods:
calendar periods
custom periods
imported periods
Calendars created on this page are used to create and calculate metrics,
sets and control charts. Calendars are stored in the Performance Manager
repository. The calendar name is stored in the ci_series table and the
calendar's definition (its dates and periods) are stored in the ci_period table.
Calendar properties
Use the "Calendar Properties" panel to define the first day of the week or
year and to specify whether weekend days are included in the calendar
definitions. Calendar properties apply to all calendars you create.
Go to Dashboard and Analytics Setup > Time Config and click Options.
The Calendar Properties panel appears.
Note:
If no calendars have been created, all fields are blank. Once a calendar is
created, the properties cannot be modified.
The "Calendar Properties" panel contains the following options:
First day of the week
Select the day on which to start the weekly grain period. For example, if
the review period is Wednesday to Tuesday, define a week as beginning
on Wednesday.
First week of the year
Select the first week of the calendar year. Define the first week of the
year as the week in which January first falls, or the first week whose days
are all in January.
Weekend days
Select the days that the calendar skips systematically as weekend days.
Note:
Once you have defined calendars based on the calendar properties, the
options cannot be changed. You can edit the calendar properties if no
calendars rely on them.
Calendar granularity
Daily is the lowest possible level of granularity, therefore the shortest time
span on which a calendar can be based.
Adding a calendar
Before you create calendars, you need to define the calendar properties that
apply to all your calendars.
1. In Dashboard and Analytics Setup > Time Config > Calendar, click
Add.
The "Add a Calendar" window appears.
2. In the "Name" section, enter a name, and optionally, a description of the
calendar.
The name of the calendar is stored in the Performance Manager repository
ci_series table.
Custom periods are non-standard, but consistent blocks of time, like every
3.5 weeks, every eight months, every four days.
Related Topics
Adding a calendar on page 99
Analytics calendars on page 97
Calendar span on page 103
Importing a calendar
Quarter 5 Q2 Char(35)
Month 6 07 Char(35)
(year-to-year comparison,
Date Prior Year 10 beginning on same period date format
last year)
Note:
You must use a carriage return (Enter) after the last line of data in the .csv
file.
Calendar span
In Dashboard and Analytics Setup > Time Config > Calendars > Add,
set a calendar span.
The "From" period is the first period from which data is available. The "To"
period is typically set in the future. Extend this period as needed depending
on the grain of the calendar.
For example, if you have a three-year sales revenue goal you can extend
the calendar three years in the future. However, if you have a finer-grain
calendar (daily, for example) you can to extend it one month at a time into
the future.
Note:
Business Objects does not recommend extending calendars too far into the
future, since this adds data to the calendar table in the Performance Manager
repository. Instead, revise the calendar.
Related Topics
What is a grain? on page 152
Calendar granularity on page 99
Related Topics
Calendar span on page 103
Creating a custom period calendar on page 99
Importing a calendar on page 100
Selecting period display options for a calendar on page 102
Before you remove a calendar, you must first remove any metrics that use
the calendar in their definitions.
1. Go to Dashboard and Analytics Setup > Time Config > Calendar.
2. Select the calendar you want to delete from the list.
3. Click Remove.
Note:
All the moving average methods are externalized in the stats.ini file, which
can be customized.
You can apply moving averages to calendars. When you create a metric
based on a calendar that has a moving average associated to it, the data
points are smoothed according to the selected moving average calculation.
1. Go to Dashboard and Analytics Setup > Time Config > Moving
Average.
The "Moving Average Transformation" page appears.
2. Select a calendar from the "Calendar Name" list.
The average calculation you select is applied each time you select the
calendar for a metric.
Related Topics
Moving averages in calendars on page 105
Transformation Use
MA exponentially
weighted
MA linearly weight-
ed
MA linearly weight-
ed center
Related Topics
MA exponentially weighted on page 155
MA linearly weighted on page 156
MA linearly weighted center on page 156
MA exponentially weighted
A moving average transformation. An MA exponentially weighted
transformation finds the number of points parameter required. The smoothing
constant parameter is required:
Less than 1 weights current data more heavily
Equal to 1 weights every points identically (same as simple MA)
Greater than 1 weights old data more heavily
where a is a constant between 0 and 1, and F1 is the initial value that usually
is given the value of Y1.
As a guide in choosing a, try values close to 0 if the series has a lot of random
variation. If you wish the forecast values to depend strongly on recent
changes in the actual values, try values close to 1.
MA linearly weighted
A moving average transformation. You use a weighted moving average to
give more weight to current data. Weights can be calculated automatically
using a function.
where p is the sequence of the data points in the moving window ranging
from 1 to n. The weights must sum to a value of one.
where a is the smoothing constant and p is the sequence of the data points
in the moving window ranging from 1 to n.
MA centered
A moving average transformation.
Related Topics
What is the moving average? on page 153
If Yt is the actual observation for period t and Ft is the forecast for the same
period, then the forecast for the next period is:
Ft+1 = Ft+a(YtFt)
An SES analytic is based on the time series system universe. The SES
weight function is built into the universe. The end user can try different values
of the smoothing constant in order to find the best one.
Related Topics
MA exponentially weighted on page 155
2. From the "Calendar Name" list, select the calendar from which you want
to remove the moving average.
Any transformations applied to the selected calendar appear in the
"Defined Transformations" list on the right.
3. Select the transformation you want to remove, and then click the <<
button.
A prompt asks you if you want to delete the selected transformation.
4. Click OK.
The transformation is removed from the calendar.
What is differencing?
Difference Transfor-
Description/Application
mation
Difference Transfor-
Description/Application
mation
Related Topics
Differencing calculations on page 111
2. From the "Calendar Name" list, select the calendar from which you want
to remove the differencing.
Any transformations applied to the selected calendar appear in the
"Defined Transformations" list on the right.
3. Select the transformation you want to remove, and then click the <<
button.
A prompt asks you if you want to delete the selected transformation.
4. Click OK.
The transformation is removed from the calendar.
Rollups in calendars
Rollups create subtotals that roll up from the most detailed level to a grand
total.
Rollup calculations
Rollup Transforma-
Description/Application
tion
When you create a metric based on a calendar that has a rollup associated
to it, the data points are smoothed according to the selected rollup calculation.
1. Go to Dashboard and Analytics Setup > Time Config > Rollup.
The "Rollup Transformation" page appears.
2. Select a calendar from the list.
The rollup calculation you select is applied each time you select the
calendar for a metric.
3. From "Available Transformations", click the rollup you want to associate
to the selected calendar.
4. Click the >> button.
The rollup appears in the "Defined Transformations" list.
5. Click Add then click OK.
The selected rollup is added to the transformation page. The next time
you apply the calendar to a metric, the rollup calculation is applied to the
data series.
Related Topics
Rollup calculations on page 113
Rules templates
You can choose standard rules templates that end users use to define their
own business rules in Performance Manager. Administrators can edit the
standard rules templates to define custom templates suited to the specific
needs of the enterprise.
Note:
For information on how end users can define business rules, consult the
Performance Manager documentation.
Rules templates save end users time when they build rules in Performance
Manager to handle specific events.
For example, users could create a rule that states that when a specific metric
is refreshed, if its current value is below a certain figure, then the Dashboard
and Analytics server sends an email to the person responsible for that metric
so they can take the necessary action.
Rule components
Rules templates
The text strings and tags in the rule are interpreted as follows:
On this <events> if <a condition is met> <do actions>
can use to build a specific rule. It is these lists and function options that
you can limit or modify as an administrator.
"XML Text"
The XML syntax defines the rule. For example, the "Generic rule" template
includes the following XML text:
<TRIGGER><_1/></TRIGGER>
<CONDITION><_2/></CONDITION>
<ACTION><_3/></ACTION>
Related Topics
Rules templates on page 116
Note:
Instead of creating a rules template from scratch, you can duplicate an
existing template and then edit it.
results in the following three hyperlinks appearing when users select the
template for a business rule:
Link Tag
events <e>
schedule <s>
a metric <p>
a value <v>
do actions <a>
Link Tag
feedback <f>
6. To modify the XML text, click the arrow next to "Insert XML Tag", and
then click the tag you want to insert.
7. To validate the syntax, click Parse.
The XML syntax is checked. If there is an error in the syntax, a message
notifies you of the error.
8. Click OK.
The modified template is now available to end users when they define
business rules in Performance Manager.
For information on the template properties, see the topic on creating rules
templates.
Related Topics
Creating a rules template on page 118
Instead of creating a rules template, you can duplicate a rules template you
have already customized, and then rename and edit it.
1. Go to Dashboard and Analytics Setup > Parameters > Rules.
2. Select the template you want to duplicate.
3. Click Duplicate.
Related Topics
Creating a rules template on page 118
When you delete a rules template, it is no longer available to end users when
they build new business rules in Performance Manager. Any rules based on
that template are not impacted.
1. Go to Dashboard and Analytics Setup > Parameters > Rules.
2. Select the template you want to delete.
3. Click Delete.
Administrators can create list templates that specify the data definition, output
format, and file location for the lists generated by end users. When users
want to build a rule that includes the automated generation of a list based
4. Click the drop-down arrow next to "Subject Area", and then select a subject
from the list.
The measures and dimensions in the selected subject appear in the
Content section, in the Available information pane.
6. To select the format type for the list, click the drop-down arrow next to
"Format", and then select one of the following formats:
SQL sentence returns the executable SQL that finds the list of
customers in the database. Use the format if you want to pass the
SQL to an external campaign tool.
For example, create a set of Leavers. Monitor spending over time
following mail shots and use the SQL generated by the list to build a
new set, and track response to campaign.
XML stream useful if you want to leverage the list via an XLTS tool.
CSV text useful for exporting lists to external databases or
spreadsheets.
HTML stream useful for building HTML format reports.
Profiler Search generates the list of the selected set in an applet
that provides Individual Profiler analysis capabilities. From the list, you
can drill to a single individual to analyze their individual profile.
For information about Individual Profiler, click Dashboard and
Analytics Setup > Parameters > Individual Profiler, and then click
Help on the services bar.
TSV File the Tab Separated Values format file is designed to work
with Siebel
Metadata XML useful if you want to leverage the list via an XLTS
tool, because metadata about attributes, such as formatting, is
included.
7. Click the drop-down arrow next to "Destination", and then select one of
the following destinations from the list:
Downloaded file the list is generated to a local file.
Server file the list is generated to a file on the server you specify.
URL the list is generated to a web server at the URL you specify.
email the list is generated as an email and sent to the address you
specify.
8. Depending on the destination you selected, type the appropriate
information into the text box that appears below the "Destination" box:
Downloaded The name of the file to which the list is generated. For ex-
file ample: filename.xml
The name of the server and the file location and file name
Server file where the list is generated. For example: \\server
name\directory\filename.xml
The URL of the web server and web page where the list
URL
is generated. For example: http://webserver/lists/
In the "Default Name" box, type the name that you want
to appear in the "Subject" field of the email.
In the "To" box, type the email address to where the
eMail list is to be sent.
If you want other email addresses on copy or blind copy,
you can also type email addresses in the "Cc" and "Bcc"
boxes.
9. Click OK.
Instead of defining a new list template from scratch you can duplicate an
existing template and then modify it to create a template.
1. Go to Dashboard and Analytics Setup > Parameters > Lists.
The "List Output" panel appears.
2. Select the name of the template you want to duplicate, from the "Available
List Outputs" list, and then click Duplicate
3. In the "Output Name" box, type the new name you want to give to the list
template.
The output name needs to be meaningful to end users.
4. Define the data content, output format, and file location of the generated
list in the usual way.
2. Select the name of the template you want to delete, from the "Available
list outputs" list, and then click Delete.
The list template is deleted from the ci_list_output table in the Performance
Manager repository, and is no longer available to users.
Each time you reactivate tracing, a new log file is created in the server
directory you specify. For example: server_date.log
Note:
We recommended you monitor disk usage whenever you activate traces.
On a deployment with a lot of user activity, log files can be large and therefore
have a significant impact on disk file space.
Activating tracing
You can activate tracing on Dashboard and Analytics user activity, processes,
and modules. When you activate tracing, each internal action for those
activities, processes, and modules is recorded in a log file.
1. In Dashboard and Analytics Setup > Parameters > Trace, select the
server directory where you want the log files to be generated when tracing
is activated.
Each time you reactivate tracing, a new log file is created in the server
directory you specify, for example: server_date.log.
Note:
We recommended you monitor disk usage whenever you activate traces.
On a deployment with a lot of user activity, log files can be large and
therefore have a significant impact on disk file space.
2. In the "Select the information to log" section, select one or more of the
following options:
SQL queries queries made to corporate data sources via metrics
universes (for analytics) and ad hoc query universes (for Web
Intelligence or Desktop Intelligence reports).
System Information
User Activity the activities of each user session
Internationalization
3. In the "Enable log for these modules" section, select the engines and
modules you want to trace.
You can trace activity for the following engines and modules:
Engine/Mod
Server name Description
ule
Individual Pro-
AAIProfiler Used by Individual Profiler.
filer
4. Click Apply.
The logs are set to be saved to the destination you indicated in "Select
the destination of the log".
Related Topics
Individual Profiler portrait properties on page 127
In the Dashboard and Analytics Setup, you define the look and feel of the
portrait portion, one of the views available for this analytic. You must define
the parameter for each subject area that is used for individual analysis.
If you have the Set Analysis licence, you can find the analytic in one of the
following locations:
the "Profiler" can be found in the Sets Analytic category on the Create
New Analytic tab of Dashboard Builder
the "Individual Profiler" can be found in the edit mode of a dashboard tab
at Toolbox > New Analytic > Individual.
Note:
The metric universes used with Individual Profiler should include specific
filters and description tags for dimensions. Building universes for Individual
Profiler is explained in the Designer documentation.
Note:
You can log into any CMS from the Analytic Template Publisher.
Access rights.
Before you can publish Crystal Xcelsius templates to the CMS, you need to
have the ability to publish to and retrieve documents from the CMS. If you
do not have the correct rights for this, contact your system administrator.
Note:
The "Analytic Template Publisher" is only available in English, however these
template-based analytics once deployed are available in all languages in
which Business Objects distributes its Business Objects Enterprise products.
You need to manually deploy the templates for the Data Exploration, Bubble,
Pie and Radar chart analytics so that they can be used in Dashboard Builder.
To install the Bubble, Pie and Radar chart analytics, run the following
command line in the [BO_INSTALL_DIR]\Performance Management 12\setup
folder:
java -jar XCTemplateUploaderBatch.jar -cms [MACHINE_NAME]
-user [ADMIN_LOGIN_NAME] -pass [ADMIN_PASSWORD]
-fmkdir templates.zip
Note:
If the password is blank, you can remove the parameter -pass in the
command line.
After you have created analytic templates in Crystal Xcelsius, use the
"Analytic Template Publisher" to make the templates available in Dashboard
Builder.
1. In the "Analytic Template Publisher" home page, click Publish new
Crystal Xcelsius Template.
The "Main Template Properties and Files" page appears.
2. In the "General Properties" section, enter a template name in the
"Template Name" box.
3. Select a "Template Category" from the drop-down list.
The categories correspond to those available from InfoView in Open >
Dashboard and Analytics > Dashboard Builder > Create New Analytic.
4. Type a description.
5. In the "Template Model Properties" section, type the maximum number
of rows.
6. Select either single or multiple metrics/measures.
If you select Multiple metrics/measures, set a minimum and a maximum.
7. To have slice analysis, activate Allow Slice Analysis.
8. To allow slice navigation, activate Allow Slice Navigation.
9. In the "Upload Files" section, click Browse to navigate to the SWF and
icon files.
10. In the "Upload Files for Edition" section, click Browse to navigate to the
XLF and XLS files.
11. In the "Destination" section, select Force overwrite if you want to
overwrite an existing template with the same name.
Note:
If you select Force overwrite and inadvertently use the name of an
existing analytic, that existing analytic is overwritten. There is no way to
recover an analytic once it is overwritten.
12. Select the folder in which you want to save the template.
13. Click Next to add additional properties for the template's edit panel, or
Finish to save your template.
14. To create additional properties, type a name for each property in the
"Label" box.
15. Select the type of property.
If you select Text input, enter a default value option.
If you select Combo box, type the options list, with each option
separated by a carriage return.
Note:
To remove a property, highlight it and click Remove. To change the order
of the properties, use the Move up and Move down options.
Related Topics
Analytic Template Publisher on page 129
When you update any item for a Crystal Xcelsius template that has already
been published to the Central Management Server (CMS), you can use the
"Analytic Template Publisher" to republish it to the BusinessObjects Enterprise
repository.
1. In the "Analytic Template Publisher" home page, click Publish new
Crystal Xcelsius Template Archive (Zip file).
The "Upload Crystal Xcelsius Template Archive (Zip file)" page appears.
2. In the "Upload File" section, click Browse to navigate to the ZIP file.
3. To force a folder to be recreated in the CMS, activate Force folders
creation.
4. If there is an existing template in the ZIP file with the same name the one
in the CMS that you want to replace, activate Force overwrite.
5. Click Finish.
Note:
To download all of the templates in one action, click Download all templates.
Related Topics
Analytic Template Publisher on page 129
Property Indicates
SI_MAX_GRAPHS Note:
The maximum number of data sources should not
exceed the number of columns allocated for data
sources in the SerieValues Excel sheet.
Property Indicates
The first two columns of the SerieValues Excel sheet (three columns if the
template allows slice analysis) are reserved as identifiers or to store
dimension values, so they do not count as data sources.
For example:
there are three columns in the spreadsheet used by the Gauge template
(no slice analysis, one data source)
there are four columns in the spreadsheet used by the Pie Chart template
(allowing slice analysis and one data source only)
there are eight columns in the spreadsheet used by the Radar Chart
template (allowing slice analysis and accepting up to five data sources)
Related Topics
Downloading a Crystal Xcelsius template on page 133
Publishing a Crystal Xcelsius template archive on page 132
Related Topics
Downloading a Crystal Xcelsius template on page 133
Publishing a Crystal Xcelsius template archive on page 132
hours
days
months
Note:
Calendars are defined in Dashboard and Analytics Setup > Time Config.
1. Go to Dashboard and Analytics Setup > Control Charts > Samplings.
2. Click Add.
3. The "Create a new sampling" window appears.
4. In the "Sampling Name" box, type a name for the sampling.
5. Select Calendar-based.
6. From the "Select Calendar" list box, select the calendar you want to use
for the sampling.
7. Select or type the date and time for the "Start Time".
8. If you want to indicate a stop time, activate "Stop Time", then enter the
appropriate time.
9. Click OK.
Related Topics
Analytics calendars on page 97
You can edit samplings to change parameters, such as the time period or
the calendar on which a sampling is based.
1. Go to Dashboard and Analytics Setup > Control Charts > Samplings.
2. Select the sampling you want to edit.
3. Click Edit.
4. The "Edit an Existing Sampling" panel appears.
To modify the parameters, see the topic on specifying samplings.
Related Topics
Specifying samplings for control charts on page 138
If any control charts in the Dashboard and Analytics Setup deployment use
the sampling you want to remove, you need to delete those control charts
before you can remove the sampling.
1. Go to Dashboard and Analytics Setup > Control Charts > Samplings.
2. Select the sampling you want to remove.
3. Click Remove.
A prompt asks you to confirm if you want to remove the selected sampling.
If any control charts use the selected sampling, those control charts are
listed. You need to remove those control charts before you can remove
the sampling.
As an administrator, you can add, edit and remove filters for Process Analysis
control charts.
As an administrator, you can define filters for use in Process Analysis control
charts.
1. In Dashboard and Analytics Setup > Control Charts > Filters, click
Filters.
2. Click Add.
The "Create a New Filter" panel appears.
3. In the "Filter Name" box, type a name for the new filter as it should appear
in the list of available filters in Process Analysis.
4. Click the arrow next to "Subject Area" to select a subject area (or universe
class).
A list of available filters appears for each subject area.
5. Select the filters you want to make available for control charts.
You can select one or multiple filters.
6. Click OK.
The new filter appears in the list of available filters.
Related Topics
Adding a filter to a control chart on page 142
If any control charts in the Dashboard and Analytics Setup deployment use
the filter you want to remove, you need to delete those control charts before
you can remove the filter.
1. Go to Dashboard and Analytics Setup > Control Charts > Filters.
2. Select the filter you want to remove.
3. Click Remove.
A prompt asks you to confirm if you want to remove the selected filter. If
any control charts use the selected filter, those control charts are listed.
You need to remove those control charts before you can remove the filter.
As an administrator you can set parameters for the alarms that end users
can select when they create control charts, using Process Analysis. When
you create an alarm you set a number of rules that, when met, trigger the
alarm. By using one or more of these rules you determine the sensitivity of
the alarm. The rules are based on points that appear on the chart.
As an administrator, you can define alarms that end users can then select
when they create control charts. Alarms allow you to increase the power of
control charts is to use rules to supplement the ordinary rule governing control
limits.
1. Go to Dashboard and Analytics Setup > Control Charts > Alarms.
2. Click Add.
The "Create a new Alarm" window appears.
If any control charts in the Dashboard and Analytics deployment use the
alarm you want to remove, you need to delete those control charts before
you can remove the alarm.
1. Go to Dashboard and Analytics Setup > Control Charts > Alarms.
2. Select the alarm you want to remove.
3. Click Remove.
A prompt asks you to confirm if you want to remove the selected alarm.
If any control charts use the selected alarm, those control charts are listed.
You need to remove those control charts before you can remove the
alarm.
Aggregation functions
The Arithmetic mean (also called average or simple mean) is the sum of the
values divided by the number of values. The arithmetic mean is relevant any
time several quantities add together to produce a total.
It answers the following question: if all the quantities had the same value,
what would that value have to be in order to achieve the same total?
Related Topics
What is harmonic mean? on page 146
What is geometric mean? on page 146
Average functions
Count functions
The Geometric mean is the nth root of the product of the n values. Less often
used than the arithmetic mean, it is appropriate for averaging ratios such as
rates of change, interest rates or inflation rates. More generally, the geometric
mean is relevant any time several quantities multiply together to produce a
product.
The geometric mean answers the question: if all the quantities had the same
value, what would that value have to be in order to achieve the same product?
The formula for Geometric mean is as follows:
Note:
The values must be greater than zero.
Related Topics
What is harmonic mean? on page 146
What is arithmetic mean? on page 145
The Harmonic mean is the reciprocal of the arithmetic mean of the reciprocals
of the values. It is used to calculate average rates such as distance per time,
or speed. The formula for harmonic mean is:
Related Topics
What is arithmetic mean? on page 145
What is geometric mean? on page 146
What is a median?
The median is the midpoint of the values after they have been ordered from
the smallest to the largest, or the largest to the smallest. There are as many
values above the median as below it in the data set.
The median is less sensitive to outliers (extreme values or errors) than the
arithmetic mean is. For an odd number of values, the median is the middle
value in the ordered set. For an even number of values, the median is the
arithmetic mean of the two middle values.
What is maximum?
What is minimum?
The coefficient of Kurtosis measures the relative peak of the curve defined
by the distribution of the values. Standard normal distribution has a Kurtosis
coefficient of 0. A Kurtosis coefficient of greater than 0 indicates that the
distribution is more peaked than the standard normal distribution. A Kurtosis
coefficient of less than 0 indicates that the distribution is flatter than the
standard normal distribution.
The skew statistic measures the degree to which a variable deviates from
symmetry with the mean at the center. A skew of value zero means that the
distribution is a symmetrical curve. A positive value indicates that the values
are clustered primarily to the left of the mean with most of the extreme values
to the right of the mean. A negative skew indicates clustering to the right.
Distributions with positive skew are more common than distributions with
negative skew.
Variance is a sum of the squared deviations from the mean, divided by n-1
or n. The formula for population variance is:
The coefficient of Kurtosis measures the relative peak of the curve defined
by the distribution of the values. Standard normal distribution has a Kurtosis
coefficient of 0. A Kurtosis coefficient of greater than 0 indicates that the
distribution is more peaked than the standard normal distribution. A Kurtosis
coefficient of less than 0 indicates that the distribution is flatter than the
standard normal distribution.
The skew statistic measures the degree to which a variable deviates from
symmetry with the mean at the center. A skew of value zero means that the
distribution is a symmetrical curve. A positive value indicates that the values
are clustered primarily to the left of the mean with most of the extreme values
to the right of the mean. A negative skew indicates clustering to the right.
Distributions with positive skew are more common than distributions with
negative skew. An example of positive skew is the distribution of income.
Variance is a sum of the squared deviations from the mean, divided by n-1
or n. The formula for sample variance is:
What is sum?
What is an analytic?
What is binning?
Related Topics
What is a variable? on page 157
A control chart includes upper and lower limits that show the expected
variation in the process and a center line that shows the mean value of the
points in the chart.
What is differencing?
What is a dimension?
Related Topics
What is a sliced metric? on page 157
What is a grain?
A grain is the duration of the time periods or slices that make up metrics.
Related Topics
What is a metric? on page 153
What is a metric?
You can use metrics to track actual performance and compare it to a goal,
or use it to project a trend.
Metrics can also be created on a set universe. Set metrics allow you to track
a measure over time for a particular subject within a set.
Related Topics
What is a sliced metric? on page 157
In data analysis, you use the moving average to calculating the average
value of an indicator, over a period of time. In some time series, seasonal
variation is so strong it obscures any trends or cycles, which are very
important for the understanding of the process being observed.
Transformation Use
MA exponentially
weighted
MA linearly weight-
ed
MA linearly weight-
ed center
Related Topics
MA exponentially weighted on page 155
MA linearly weighted on page 156
MA linearly weighted center on page 156
MA exponentially weighted
A moving average transformation. An MA exponentially weighted
transformation finds the number of points parameter required. The smoothing
constant parameter is required:
Less than 1 weights current data more heavily
Equal to 1 weights every points identically (same as simple MA)
Greater than 1 weights old data more heavily
where a is a constant between 0 and 1, and F1 is the initial value that usually
is given the value of Y1.
As a guide in choosing a, try values close to 0 if the series has a lot of random
variation. If you wish the forecast values to depend strongly on recent
changes in the actual values, try values close to 1.
MA linearly weighted
A moving average transformation. You use a weighted moving average to
give more weight to current data. Weights can be calculated automatically
using a function.
where p is the sequence of the data points in the moving window ranging
from 1 to n. The weights must sum to a value of one.
where a is the smoothing constant and p is the sequence of the data points
in the moving window ranging from 1 to n.
Smoothing constants less than 1 weigh recent data more heavily. A smoothing
constant of 1 gives equal weight to each point. If the smoothing constant
exceeds 1, older data are weighted more heavily than recent data.
MA centered
A moving average transformation.
Related Topics
What is the moving average? on page 153
If Yt is the actual observation for period t and Ft is the forecast for the same
period, then the forecast for the next period is:
Ft+1 = Ft+a(YtFt)
An SES analytic is based on the time series system universe. The SES
weight function is built into the universe. The end user can try different values
of the smoothing constant in order to find the best one.
Related Topics
MA exponentially weighted on page 155
Related Topics
What is a metric? on page 153
What is a variable?
A
A Get More Help
http://www.businessobjects.com/support/
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
http://www.businessobjects.com/services/training
mailto:documentation@businessobjects.com
Note:
If your issue concerns a Business Objects product and not the documentation,
please contact our Customer Support experts. For information about
Customer Support visit: http://www.businessobjects.com/support/.
server U
descriptions 55
server parameters universe value lists 121
general 59 universes
server session cleanup 62, 63 building 81
servers checking integrity 73
starting 64 defining connections 81
Set Analysis domain 65 metric 79, 80
Set Analysis guest user 78 object metadata 84
set-based metrics 26 predictive analytic services 44
sliced metrics 88 pushing to repository 81
creating 97 removing 83
used on dimensions 91 system tables 82
SMTP updating 83
specifying server and port number 57 viewing metadata 84
starting servers 64 user
subsets 34 initialization 79
system tables 82 users
deploying 68 check integrity 75
system user 77 importing into a dimension 93
defining 77 importing manually into a dimension 94
T V
templates variables
deploying templates 130 check integrity 75
rules 115
Xcelsius 129, 130, 131, 132, 133, 137,
138
W
traces web parameters
activating 125 explanation 56
tracing web server parameters 58
activating 125
X
XML for rules 117