Schedule M - Reporting

Last updated on August 16, 2016

 

What is the purpose of this Schedule?

Who develops the supporting documents required to update the schedule?

When should the schedule be created?

When is this particular schedule used?

What is required for this schedule?

Tips

Information covered in Schedule M Attachments and Exhibits

 

What is the purpose of this Schedule?

The purpose of Schedule M is to describe the reporting requirements and types of reports, plans and other information to be prepared by TELUS under the TSMA. 

Who develops the supporting documents  required to update the Schedule? Changes within the schedule will be developed by the vendor, TELUS and then reviewed/negotiated with the Province.
When should the Schedule's supporting documents be created? As a schedule applies to all services under the TSMA,  when adding a new service, either a new attachment or a new exhibit (or both) may be required to be added to the schedule.  The appropriate document(s), attachment and/or exhibit, are always created by TELUS after the Province has documented their requirements and the requirements have been reviewed and agreed to by the Vendor (TELUS) via a Term Sheet negotiated by the Province's Legal Representative.
When is this particular schedule used? This schedule is reviewed when onboarding a new service to determine what reporting requirements are already provided and available through the TSMA.
What is required for this Schedule? It is important that you review all the requirements for this new service, then review the TSMA to view what is already provided and then document any gaps.  
Tips: For example: see attachment M9
 

Information Covered in Schedule M Attachments and Exhibits

If there are specific Reporting requirements for the proposed service, these requirements need to be documented in a new attachment to Schedule M, and can address the type of information as detailed below:

  1. Default Due Date (mandatory)
  2. Pre-Defined Reports (mandatory)
  3. TELUS Reporting Tools (mandatory)
  4. Default Method of Delivery (mandatory)
  5. Report Description
  6. Report Recipient
  7. Frequency
  8. Due Date
  9. Report Content
  10. Incident Management Reports
  11. Billing Reports and Files
 

Next Page: Schedule N - Problem Incident Management Procedures

 

Contact information

For more information please contact the Office of the Chief Information Officer