Industry Testing Guide

1.1 Purpose of Industry Testing

Industry Testing is an ongoing mandatory activity to ensure a high data quality of the senders’ data files in order to reduce the number of rejected transactions. In addition, it helps the financial organizations prepare their computer systems for reporting Registered Disability Savings Plan (RDSP), Grant & Bond transactions. It also serves as an informal point of contact for financial organizations on issues related to the CDSP system.

1.2 Scope

This document is limited to the Industry Testing process and includes criteria for satisfying the related requirements.

1.3 Industry Testing Schedule

Senders can schedule a testing timeframe with the Industry Testing Team at any time. Once the files have been sent, e-mail should be forwarded to the Industry Testing mailbox following the instructions in section 3.3.1.

1.4 Service Levels

Typically, results are returned within 3 working days (time between the latter of receipt of file or e-mail request received by the CESP and results being returned to the sender).

1.5 Industry Testing Self-Assessment Questionnaire

Once industry testing is completed, a self-assessment questionnaire is sent to the issuer. The self-assessment questionnaire replaces the on-site phase II testing. Although it is not a requirement to pass Industry Testing it is part of the process and must be completed within the prescribed time frame.

The purpose of this questionnaire is for CESP to obtain information to provide assurance that an issuer’s systems-related processes function as required. This information may be used as part of future monitoring or compliance activities.

The questionnaire may be tailored based on the type of Industry Testing activity the issuer is undergoing.

2.1 Confidentiality

Test data provided by senders can contain live data including actual Social Insurance Number (SIN) information and financial information and is considered 'protected'. The data volume information, client information, etc. is competitive information and it is treated with confidentiality, as are test results. Any specific information about an issuer, agent or service provider will not be disclosed to any other Issuer, Agent or service provider.

When data files include production data such as Specimen Plans, they must be forwarded using secure methods only, as specified in section 3.3.2. Test files submitted in violation of this security requirement will not be tested by the Industry Testing Team under any circumstances.

2.2 Archiving of Industry Test Data

Industry input test data files, not test results or output files are archived for a 6 month period and may be reprocessed for multiple tests during this period upon request. Test files cannot be reprocessed under prior releases of the CDSP system or CDSP system ITS versions.

3.1 Overview

Each participating sender is responsible for providing a file or set of files for testing. Service providers must submit separate files for each sender they represent.

Industry Testing will provide testing of filenames prefixed with ‘CDSPT’. Results relating to files prefixed with a ‘CDSPT’ will be reported back to the sender in terms of number of transactions sent, processed, errors found, contracts registered and success rate per transaction type submitted for the test. This may include one file or multiple files. In the case of multiple files, a cumulative success rate will be provided.

3.2 Creating Industry Test File(s)

3.3 Submitting Industry Test File(s)

3.4 Processing Industry Test Files

Each Industry test is processed against a non-populated database. The database schema is not populated in order to give the sender complete control over the data environment used to run the test. It is intended to assist the sender in interpreting industry test results. It should be noted that the sender is responsible for the creation and submission of a baseline file containing information related to contracts, holders and beneficiaries which will be loaded into the testing environment.

At this time, the Social Insurance Registry (SIR) and CRA Validation performed in Production are NOT conducted in Industry Testing. It is a simulated process whereby the beneficiary SIN data passes all SIR validation edits.

The Industry Testing environment is based on the current date. Therefore, future dated transactions will be rejected and the sender must advise the Industry Testing Team of the testing month in which the sender wishes to process the data files. This notification would also be included in the Special Instructions email (refer to section 3.3.1.).

3.5 Running the Test

The input file(s) will be loaded into the system one at a time until they have all been validated. Financial processing will be performed on all of the input files simultaneously unless otherwise specified by the sender. Files that are illegible or do not adhere to the confidentiality requirements will not be processed and senders will be advised accordingly.

For each simulated Production Run, the following output files will be generated. Please note that, if the data test file does not meet the submission and security requirements (refer to sections 2.1 and 3.3.1), an output file will not be generated.

• .err - Error Report: error report for format and business rule errors on data within the transactions submitted.

• .pro - Processing Report: transaction report for successful transactions.

• .reg - Contract Registration Report: registration report for registration of contracts.  (Will not be generated If no registration changes).

• .sur - SIN Usability Report: The CESP will verify its beneficiary and holder SIN information with the SIR on a monthly basis. (Will only be generated upon request).

3.6 Reporting Results

Test results and transaction information will be returned to the sender using the same method as the test files were received. The filename of test results will be in the following format:

• ‘CDSPT’ + T + Authorized Agent BN + Transactions Latest Month + Date Sent + File number

3.7 Receiving Industry Test Results from the CDSP System

The RDSP output transaction files should be loaded into the sender's system to confirm the processed transactions and record grant amounts within their systems.

4.1 Success Criteria

4.2 Re-testing Conditions

Re-testing will be required under the following circumstances:

• When a sender consistently sends transactions with unacceptable error rates, based on Industry Testing Success Criteria (Annex A). The sender may not be permitted to participate in monthly production runs until they demonstrate lower error rates in industry testing.

• Situations where a new software base is implemented such as when Issuers merge or amalgamate (new data from a different source) or when the sender is changing service provider. It should be noted that this type of testing requires the submission of data simulating business from the original sender prior to the merger or amalgamation of Issuers.

• With the release of a new version of the CDSP system ITS, each participating sender will have to retest to ensure conformance to the new specifications.

• When modifications are made to the sender's system after successfully completing industry testing.

1. Who will be the primary and/or secondary contacts during Industry Testing?

Primary Contact Name:
Title:
Phone Number:

Secondary Contact Name:
Title:
Phone Number:

2. Provide the Issuer BN and approved specimen plan(s) that will be used during Industry Testing

Issuer BN:
Approved Specimen plan(s):

3. Did you receive the required documentation from the Enrollment team?

• Yes
• No

4. Have your PKI Key and MSFT account been set up?

• Yes
• No

5. When do you plan on beginning Industry Testing?

Provide start date:

6. Are all transactions submitted in the production file created by the system?

• Yes
• No

If no, please provide additional details:

7. Will you be using an internally built system or are will you be using a service provider?

• Internally built system
• Service provider: __________________

8. If using a service provider, please explain in detail their responsibilities in regards to the processing, creation and submission of production files.