Last updated on MARCH 08, 2017
Applies to:Oracle Real-Time Decisions Base Application - Version 126.96.36.199  and later
Information in this document applies to any platform.
We would like some clarification on the information located in section 13.6.2 ‘Calculating a Normalization Factor’ found here: (http://docs.oracle.com/cd/E17904_01/bi.1111/e16630/elements.htm#CHDDDJDI) and in Chapter 6 of the ‘Oracle Real-Time Decisions (RTD) for Developers Student Guide’.
1. Looking at the example in section 13.6.2, why was 500 used as a normalization factor? Is it because it is the average revenue per sale? If so, why was the average revenue per sale used as the normalization factor?
2. In the example, what is the difference between weights and normalization?
3. We are looking to implement a campaign that has two performance goals: Likelihood (calculated by RTD) and Value (in dollars, which will be located in a table for look up). Do we need to take into consideration normalization? Or can we use a revenue score approach as described on page 171 (Section 6-9) in the ‘Oracle Real-Time Decisions (RTD) for Developers Student Guide’?
4. Can you give an example of a scenario (not in the training document) when weights/normalization is used, an example where a Revenue Score is used and an example when a Hybrid decision is used (Section 6-10 page 172 in the student guide)?
5. Is the hybrid decision scenario mentioned in Section 6-10 the only time that weights and normalization is used?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms