| |
A Data Integrity Project was initiated
in 2001 by the Compensation Sector, Accounting, Banking and Compensation
Branch (ABCB) of Public Works and Government Services Canada (PWGSC), to
ensure that complete and accurate data is available for pension administration
purposes. |
| |
Phase 1 of the Data
Integrity Project consisted of developing
a pension data repository to verify the accuracy of pension data from April
1, 2000, and the analysis of a selected statistically valid sample of contributor
accounts to verify the accuracy of pension data prior to April 1, 2000.
As a result of this analysis the ABCB recommended that we proceed
with Phase 2 which consists of expanding the pension data repository to
include the members' full employment history, with sufficient diagnostic
tools to validate the accuracy and completeness of pension
data for all active contributors. |
| |
In order to meet these requirements, the integrated
pension data repository (IPDR) was constructed. It stores detailed pension
contribution data, historical information from the Contributor System (salary
and service), historical Regional Pay System information (salary and service
since 1989 and Master Employee Record data since 1993), as well as election
payment information from the Estimate and Election System (ESTEL). The
IPDR therefore contains a complete and detailed collection of the members'
pension data. |
| |
Within the IPDR, a diagnostic module was developed
to verify the accuracy of key pension data by comparing salary, service
and contributions. The first test executed during the diagnostic process
used Contributor System data only. If, based on this first test, an employee's
account information on the Contributor System, was determined to be inaccurate,
a further test was performed using Regional Pay System (RPS) salary and
service data. If an account was found to be accurate using RPS data, the
RPS was deemed to be a better source of data than the Contributor System
for that particular account. As a result, transactions were created to
update the Contributor System with the RPS information; these are called "e-fix
transactions". These transactions were generated based on the verification
of certain data in the IPDR and may have consisted of only salary or leave
without pay (LWOP) changes, or a combination of both, depending on the
account. |
| |
The e-fix transactions were updated on the
Contributor System on the weekend of December 13, 2003, and they are identified
on the Contributor System with the unique source code "DI". |
| |
SALARY CHANGES |
| |
Contributor System salary records were changed
in the following manner (bear in mind that the only time this happened
was when the new data made the account pass the diagnostic test): |
| |
1. If there was no corresponding RPS salary record (entitlement
code, from and to dates, amount, etc.), the record was deleted from the
Contributor System data base.
|
| |
2. If there was a salary record on the RPS that was not on the
Contributor System, it was added to the Contributor System data base.
|
| |
3. If there was a partial match on the entitlement codes between a Contributor
System salary record and an RPS salary record but a different rate
amount, the salary records on the Contributor System were changed to
match those on the RPS.
|
| |
LWOP CHANGES |
| |
1. Periods of LWOP that were on the RPS and not on the Contributor System
data base were added.
|
| |
2. Periods of LWOP that were not on the RPS were deleted from the Contributor
System data base.
|
| |
3. In instances where the duration of periods of non-pensionable LWOP
(codes N, M, P, W, X, Y, Z, 1, 2 only) did not match the compensatory
days, the "effective from date" of the LWOP record was adjusted accordingly.
|
| |
None of the e-fix transactions which affected
LWOP data on the Contributor System contained compensatory days. The Pension
Support System uses the effective from and to dates of a LWOP period to
calculate the pension benefit when the Compensatory Days Field is blank;
therefore, not having a value in the Compensatory Days Field has no impact
on the account. |
| |
When verifying LWOP transactions on the Contributor
System, it is very important to ensure that the effective from and to dates
correctly reflect the duration of the leave. |
| |
In cases of disagreement between your records
and the data that was changed electronically (source code DI), please provide
the necessary details to the project team at the number indicated below. |
| |
If you require further clarification on this
communiqué, please contact Jan Robar at (613) 946-3321 (English
only) or Peter McDonald at (613) 946-3311 (English or French). |
[Print Version]