MPC Implementation
- Tom Fahey (Unlicensed)
- Jacob Mathews (Deactivated)
- Pamela Totas (Deactivated)
The flexibility of the Multiperiod Performance Calculator (MPC) allows it to be implemented in many different combinations of existing data. The five most common scenarios are outlined below.
Existing Daily Returns Only
If daily returns are calculated and committed on a daily basis, the MPC can create daily to-date returns and unit values. In addition, derived frequencies can be created for monthly, quarterly, and yearly frequencies.
The first time that the MPC runs, it goes back to the first daily record and updates/builds daily records going forward. Then any derived frequency records are created from that point forward.
Existing Monthly Returns Only
If monthly returns are calculated and committed on a monthly basis, the MPC can create monthly to-date returns and unit values. In addition, derived frequencies can be created for quarterly and yearly frequencies.
The first time that the MPC runs, it goes back to the first monthly record and updates/builds monthly records going forward. Then, any derived frequency records are created from that point forward.
Existing Daily Returns and Unit Values
If daily returns are calculated and committed on a daily basis and to-date returns or unit values exist from a legacy system, the multi-period calculator can create daily to-date returns and unit values. In addition, derived frequencies can be created for monthly, quarterly, and yearly frequencies.
As part of the conversion, any daily legacy data records need to be updated with the MPC locked indicator. This stops the MPC from updating these records. The first time that the MPC runs, it goes back to the first unlocked daily record and updates/builds daily records going forward. Any derived frequency records are created from that point forward.
Existing Monthly Returns and Unit Values
If monthly returns are calculated and committed on a monthly basis and to-date returns or unit values exist from a legacy system, the MPC can create daily to-date returns and unit values. In addition, derived frequencies can be created for quarterly and yearly frequencies.
As part of the conversion, any monthly legacy data records need updated with the MPC locked indicator. This stops the MPC from updating these records. The first time that the MPC runs, it goes back to the first unlocked monthly record and updates/builds monthly records going forward. Any derived frequency records are created from that point forward.
Existing Daily and Monthly Returns and Unit Values
A mix of existing monthly and daily records presents a slightly more complicated scenario, but can easily be addressed by the calculator.
If legacy monthly returns, to-date returns, and unit values exist alongside more recent daily returns that are calculated and committed on a daily basis, the MPC can create daily to-date returns and unit values. In addition, derived frequencies can be created for monthly, quarterly, and yearly frequencies.
As part of the conversion, any daily and monthly legacy data records need to be updated with the MPC locked indicator. This stops the MPC from updating these records. If only monthly legacy records exist, then the first daily record needs to be populated with the to-date returns or unit values from the prior month end, plus that day. This first daily record must also have an MPC locked indicator "P."
The first time that the MPC runs, it goes back to the daily record with a locked indicator "P" and updates/builds the daily records going forward. Any derived frequency records are created from that point forward.
The following two tables illustrate this last scenario.
Date | Freq | Return | ITD UV | MPC Locked |
|---|---|---|---|---|
04/30/1990 | M | 8.5% | 1085.00 | L |
05/31/1990 | M | 9.0% | 1182.65 | L |
06/30/1990 | M | 8.0% | 1277.26 | L |
07/15/1990 | D | 1.0% | 1290.04 | P |
07/16/1990 | D | 2.5% | 1322.29 | |
07/17/1990 | D | 0.5% | 1328.90 |
Locked monthly records have been calculated by a legacy system. As part of the implementation and prior to running the MPC for the first time, the first daily record is calculated using the most recent month to-date and unit values generated by the legacy system. This record is then locked so the values are not overwritten by the MPC. These steps are not performed by the MPC.
Scenario | Starting Frequency | Derived Frequency |
|---|---|---|
Submit as Rebuild | All Result columns, in all records, for all entities, are updated | All Base and Result columns, in all records, for all entities, are updated |
Changed Rule | All Result columns, in all records, for all entities, are updated | All Base and Result columns, in all records, for all entities, are updated |
Changed Field | Modified/New Result columns, in all records, for all entities, are updated | Modified/New Result columns, in all records, for all entities, are updated |
New Entity | All Result columns in all records for the new entities are updated | All Base and Result columns, in all records, for the new entities, are updated |
New or As Of Performance Data | All Result columns, in affected records, for the changed entities, are updated | All Base and Result columns, in affected records, for changed entities, are updated |