User manual BUSINESS OBJECTS DASHBOARD MANAGER 6.5.1

[. . . ] Dashboard Manager User's Guide Dashboard Manager 6. 5. 1 2 Dashboard Manager User's Guide Copyright No part of the computer software or this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without permission in writing from Business Objects S. A. The information in this document is subject to change without notice. If you find any problems with this documentation, please report them to Business Objects S. A. in writing at documentation@businessobjects. com. [. . . ] For example an upward trend is good for a Revenue metric but bad for an Expenses metric. MetricPolarity(metricid) The Metric polarity function will return: 1 if Metric has an upward trend is good perspective like Enterprise Revenue, profits -1 if Metric has an upward trend is bad perspective like Expenses, Churn Goal status function The Goal Status function compares the metric value to its goal and determines performance against that goal. Please refer to the scenarios specified in the scope section for the individual treatment below. Scenario 1: Compare one metric against one goal In this scenario we are only comparing one metric against one goal. The call · · Rules Dashboard Manager User's Guide 147 for this function would be GoalStatus(goalid[, -nbPeriod|date]) The function above should return for a goalid: -1 when the associated metric under-performs the target 0 when the associated metric value is equal to the target value 1 when the associated metric over-performs the target value With the input parameter of goalid, we can associate a metric and find the metric id for this goal. In addition with the metric we can determine the polarity to ascertain what under-perform and over-perform mean for that metric. An example call for this function could be - GoalStatus(goal1. goalid) where goal1 is the Revenue Plan goal and it compares the current period Revenue with the Revenue plan for this period and returns a value based on performance, taking a polarity of 1 into account for Revenue where an upward trend is good. - GoalStatus(goal1. goalid, -1) will compare the same Revenue metric against the Revenue Plan for the last period, i. e. - GoalStatus(goal1. goalid, Date(2003, 1, 1)) will compare the Revenue metric against the plan for Q1 2003 based on the January 1st, 2003 date that was passed. 148 Dashboard Manager User's Guide GYR status function GYR function helps to ascertain if performance is in the red, yellow or green zone. Functions associated with this function: GYRStatus(goalid [, -nbPeriod|date]) that will address scenario 1 below. In this scenario there is one goal for one metric and not more. In addition to the goal value table of the previous section let us consider an extract from the actual metric values as shown in the table below to complete the picture for this function. probe_id period_type period_date period_dim_id dim_key probe_value 10 10 10 10 5 7/1/2002 0 0 229 5 0 0 5 0 0 5 4/1/2003 0 0 10/1/2002 1/1/2003 301 273 335 Let us say the above is a Revenue target with a polarity of 1 as before. Example calls below illustrate the use of the GYRStatus function: - GYRStatus(goal1. goalid) will return 2 (green zone) meaning this metric value of 335 for the current period (Q2 '03) exceed the upper limit of 330 for this Revenue metric with polarity 1. - GYRStatus(goal1. goalid, -1) will return -1 (yellow under-perform zone) meaning the metric value of 273 for the previous period (Q1 '03) is between the lower limit of 260 and the target value of 290 for that period. - GYRStatus(goal1. goalid, date(2002, 10, 1)) will return 1 (yellow overperform) meaning the metric value of 301 for the specified period (Q4 '02) will lie between the target value of 280 and the upper limit of 310 Rules Dashboard Manager User's Guide 149 - GYRStatus(goal1. goalid, -3) will return -2 (Red Zone) meaning the metric value of 229 is below the lower limit of 240 for the period (Q3 '02) This function will also be very useful to track favorable and unfavorable movements. For example the scenarios below are a sample: - ((GYRStatus(goal1. goalid) = -1) and (GYRStatus(goal1. goalid, -1)=1)) then raise an alert that goal on Revenue KPI metric (associated with goalid is degrading - ((GYRStatus(goal1. goalid) = -1) and (GYRStatus(goal1. goalid, -1)=-2)) then send a message to the relevant people that the Revenue KPI metric (associated with goalid) is improving Tolerance value functions A metric associated with a goal or target can be given upper and lower tolerance limits to measure acceptable or yellow zone performance, red-zone and green-zone performance. Tolerance value function returns this value for such metrics ToleranceValue(goalid, upper|lower[, -nbPeriod|date]) The function above should return for a goalid: Upper tolerance limit value for the associated metric for the current or specified period Lower tolerance limit value for the associated metric for the current or specified period The input parameter of upper or lower specifies the specific limit value being asked. target_id 1 1 1 1 period_type 5 5 5 5 period_date 7/1/2002 10/1/2002 1/1/2003 4/1/2003 targt_value 270 280 290 300 upper_value 300 310 320 330 lower_value 240 250 260 270 The above is a relevant extract from the target value table. Some example calls for the ToleranceValue function are discussed below assuming a current complete period of Q2 '03: ToleranceValue(goal1. goalid, upper) will return 330 ToleranceValue(goal1. goalid, lower) will return 270 ToleranceValue(goal1. goalid, upper, -1) will return 320 ToleranceValue(goal1. goalid, lower, -2) will return 250 ToleranceValue(goal1. goalid, upper, date(2003, 01, 01)) will return 320 150 Dashboard Manager User's Guide % Achievement function Percent Achievement function can be thought of as a shortcut for a combination of existing functions through one call. To calculate this function, we need to get the polarity of the metric and then use the metric value compared against the goal value to get this percentage. - Scenario 1: Compare one metric against one goal This is the case with only one goal for the metric. The function call is: PercentAchieved(goalid [, nbPeriod|date]) Period date MetricID 7/1/2002 10/1/2002 1/1/2003 4/1/2003 10 10 3 3 Metric Value 10 30 20 30 GoalID 1 1 2 2 Goal value Polarity 20 20 25 25 1 1 2 2 %Achieved 0. 5 1. 5 1. 2 0. 8 PercentAchieved(goal1igoalid) will return 0. 8 (for 80%) which is for the current complete period of Q2'03 where the goalid = 2 PercentAchieved(goal1. goalid, -1) will return 1. 2 for the previous quarterly period of Q1'03 where the goalid=2 PercentAchieved(goal1. goalid, date(2002, 10, 1)) will return 1. 5 for the specified period date where the goalid=1 PercentAchieved(goal1. goalid, date(2002, 8, 17)) will return 0. 5 for goalid=1 because the specified date of August 17, 2002 will be Q3 '02. - Scenario 2: Compare one metric against all its goals An additional function is needed (in the absence of a looping construct in rules - see open issues section for details), to consider the case when one metric can have more than one goal. [. . . ] Attribute control charts plot attribute data. The types of charts are - p, np, c and u. Change is a subtraction between 2 values of a single metric. Generic formula is: Metric value Current Period - Metric value Prior period Current Versus Prior is a division between 2 values of a single metric. [. . . ]