...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
You can configure a blended benchmark so that PACE determines the weights to use, where the weights are calculated based on the component index returns between reset dates. This type of benchmark is called floating weight blended benchmark. An example of how PACE calculates the weights and returns for these types of benchmarks follows.
...
Finally, after the system populates the Custom Index Attributes table, the entity build procedure begins. These two steps cannot be separated.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Behind the scenes, the system uses the following two columns in the Custom Index Attributes table for resetting the dates:
...
You cannot change the target dictionary and the type of custom benchmark in the Custom Index Attributes tab after you create the entity. These items are dimmed in the Custom Index Attributes tab.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The following example shows how the floating weight blended benchmark is calculated:
- Calculate the drift numbers.
Index 1 (index rtn/100) * current weight = drift #1 (15/100) * 50 = 7.5
Index 2 (index 2 rtn/100) * current weight = drift #2 (-10/100) * 50 = -5 - Calculate the new weights.
Previous weight (current weight from previous step) + Drift #1 = New weight Index 1 50 + 7.5 = 57.5
Previous weight (current weight from previous step) + Drift #2 = New weight Index 2 50 + (-5) = 45
New weight Index 1 + New weight Index 2 = Total new weight 57.5 + 45 = 102.5 - Return the numbers back to a 100 percent ratio.
Weights must equal 100 for the custom index builder process.
New weight Index 1/Total New weight * 100
57.5/102.5 = x/100 x = 56.1
New weight Index 2/Total New weight * 100
45/102.5 = x/100 x= 43.9
Anchor | ||||
---|---|---|---|---|
|
Index returns for this example are listed in the following table. Calculations for this data are described below.
January | February | |
---|---|---|
Benchmark 1 | -2% | 9% |
Benchmark 2 | -6% | 4% |
Benchmark 3 | 1% | 3% |
Anchor | ||||
---|---|---|---|---|
|
In the example defined in the following table, weights for 2/28/2002 are calculated using weights and returns from 1/31/2002.
...
Benchmark | Calculation |
---|---|
Step 1 – Drift numbers | |
Benchmark 1 | (0.02) * 65 = (-1.3) |
Benchmark 2 | (0.06) * 25 = (-1.5) |
Benchmark 3 | 0.01 * 10 = 0.10 |
Step 2 – New weights | |
Benchmark 1 | (-1.3) + 65 = 63.7 |
Benchmark 2 | (-1.5) + 25 = 23.5 |
Benchmark 3 | 0.10 + 10 = 10.1 |
Total | 63.7 + 23.5 + 10.1 = 97.3 |
Step 3 – Ratio back to 100% | |
Benchmark 1 | 63.7/ 97.3 * 100 = 65.467626 |
Benchmark 2 | 23.5/ 97.3 * 100 = 24.152107 |
Benchmark 3 | 10.1/ 97.3 * 100 = 10.380267 |
Anchor | ||||
---|---|---|---|---|
|
In the example defined in the following table, the date of 3/31/2002 is calculated using the weights and the return for 2/28/2002.
...
Benchmark | Calculation |
---|---|
Step 1 – Drift numbers | |
Benchmark 1 | 0.09 * 65.467626 = 5.892086 |
Benchmark 2 | 0.04 * 24.152107 = 0.966084 |
Benchmark 3 | 0.03 * 10.380267 = 0.311408 |
Step 2 – New weights | |
Benchmark 1 | 65.467626 + 5.892086 = 71.359712 |
Benchmark 2 | 24.152107 + 0.966084 = 25.118191 |
Benchmark 3 | 10.380267 + 0.311408 = 10.691675 |
Total | 71.359712 + 25.118191 + 10.691675 = 107.169578 |
Step 3 – Ratio back to 100% | |
Benchmark 1 | 71.359712 / 107.169578 * 100 = 66.585792 |
Benchmark 2 | 25.118191 / 107.169578 * 100 = 23.437800 |
Benchmark 3 | 10.691675 / 107.169578 * 100 = 9.976409 |
Anchor | ||||
---|---|---|---|---|
|
Given that 4/30/2002 is a reset date as set up in the business calendar, then the weights for 4/30 are equal to the weights on the last reset date of 1/31/2002. The example is described in the following table.
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
To configure a floating weight blended benchmark:
- Set up the Business Calendar to identify reset dates for the benchmark.
- Set up the date rule.
- Create the new entity for the floating weight blended benchmark.
Anchor | ||||
---|---|---|---|---|
|
Weights float until you specify a reset date. A reset date is a date on which the system no longer floats from previous values but resets to the original or last updated weights for the benchmark in the Custom Index Attributes dialog box. That is, on the reset day, the weights reset to those weights associated with the most recent date for the custom benchmark definition where the RESET_FLAG = Y in the CUSTOM_INDEX_ATTRIBUTES table for that specific entity. For more information about the RESET_FLAG, see Rebalance Floating Weights Using Reset Dates.
...
- From any Eagle window, click the Eagle Navigator button to access the Eagle Navigator.
- Enter Sources in the Start Search text box.
- Click the Sources (Reporting Center) link to access the Sources workspace.
You see the Sources window. - Click Add.
The Add Source Details dialog box appears. - Add a new interface (source) with a meaningful name such as Source for Floating Weight Reset Dates. Under Available Feed Types, select Performance. See the following figure.
- Update the Business Calendar for the source from any Eagle window, click the Eagle Navigator button to access the Eagle Navigator. Enter Business Calendar in the Start Search text box.
- Click the Business Calendar (System Management Center) link to access the Business Calendar workspace.
- Choose the source created for the floating weight blended benchmarks and select the check boxes, under the Daily column, for the reset dates. Make sure to use the Daily column — the program only uses this column. For example, if you reset on a quarterly basis, then only select four dates with a check mark.
- Click Save before exiting.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
You can set up the date rule for a floating weight blended benchmark. is located in PACE Reporting under the General Reporting option.
...
Info |
---|
If you clear the Do not build Target Dictionary below assigned level check box, the node structure below the selected node has to match the target dictionary for the entity build to run successfully. See Build the Target Dictionary at Assigned Level and Above. |
Anchor | ||||
---|---|---|---|---|
|
Optimally, you would assign a benchmark for each node of the reference entity. But this is not always the case. It is conceivable that benchmarks will not be assigned to some of the Reference entity nodes. Consider the example in the following table.
...
- Total --> Common S&P 500 – 40%
- Total --> 144A --> Health Care ML Health Care Index – 10%
- Total --> Corp L AGG – 12%
- Total --> Gov L AGG – 8%
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
In most cases, you need to manually enter weights only when you first set up the floating weight benchmark. After that, the system calculates the floating weights for you, and the system resets weights automatically at the appropriate times. However, if you need to manually change a weight on an ad hoc basis at a later date, you can do so.
...