1.    Introduction

1.1      Document Purpose

This document was created to provide instructions for onboarding business services onto the myTC Account Platform, and it aims to assist all technical teams at Transport Canada, wishing to leverage the work already carried out to develop this infrastructure.

1.2      Document Conventions

This document groups and gathers the necessary specifications (at any given point in time) to produce a complete guide of the myTC Account onboarding instructions document.

Given the dynamic nature and constant improvements being implemented on this platform, updates and releases will be continuous, and subsequently versioned and saved into RDIMS.

1.3      Intended Audience

1.3.1          Non-Technical Stakeholder

Based on the goal of this document and given that its intent is to enable the onboarding of business services at large within TC, the review of this artifact by staff and business stakeholders is advised and encouraged.

Personnel may involve:

Ø  Managers;

Ø  Product Owners

Ø  Subject Matter Experts;

Ø  Analysts;

Ø  Business and Technical Writers.

1.3.2          Technical Stakeholders

The primary audience for this document include similar technical team members that have contributed to its content and will continue to do so. These include but not limited to:

Ø  Developers or SCRUM Masters;

Ø  Database Administrators;

Ø  QA Personnel and Testers;

Ø  Network and System Analysts;

Ø  Security Analysts;

Ø  Enterprise Architects.

1.4      Before you start

Prior to onboarding to the myTC Account platform, there are steps that must be undertaken in order to ensure a successful implementation of any service (operational readiness checklist)

A.     TC Access Control and TC Directory (RDIMS 15060075)

B.    Creation of each environment (Dev, ACC, etc.)

C.    Development of URLs (based on B) including the UI and API for either/both internal and external to TC

 1.    myTC Account Overview

myTC Account is Transport Canada’s online service delivery platform. It is a collection of Departmental Capabilities made up of User Features and Development Capabilities. These Department Capabilities identify common components across online services and ensure that they are built once and shared rather than duplicated.  It is an iterative platform. New features will be constantly rolled out in release packages. It is also a shared platform for all of TC to collaborate and contribute features.

myTC account is composed of 3 main modules and each of these encompasses various components.

These modules are:

Ø  myTC Account Portal;

Ø  myTC Account Micro-services – MTAPI;

Ø  myTC Account Database.

The next three subsections are a concise description of the modules and supplementary images. Each one of these could be expanded to provide more detailed specifications however; for expediency, we present information in a summary format.

If you want to become more familiar with the platform, a prompt way to do so is by reviewing subsection “2.4 What is myTC Account Sample Web Service?”.

Please note that the terms “MTOA” and “myTC Account” are synonyms that may be used interchangeably throughout components of the framework described herein.

For any additional information please contact us at:
TC.F NCR AFCE MTOA Platform Team / Équipe plateforme MTOA AFCE RCN F.TC

1.1      myTC Account Portal

The myTC Account Portal is comprised of various components and features to ensure compliance, modularity and scalability. Enhancements and/or new functionality are constantly being developed and implemented thus; the in-flux state of this document, which also implies the list below will be augmented on regular basis.

The myTC Account Portal components at this time are:

Ø  Common look and feel using the Canada's Digital Technology Super cluster (CDTS) template;

Ø  My Services Catalog;

Ø  My Requests Catalog;

Ø  Account Settings;

Ø  Common Main Navigation Bar;

Ø  Service Title Bar.

The following images illustrate the user experience when accessing the portal.

Upon consuming the myTC Account portal, the main landing page will look like the following:

Figure 2.1‑1 – example of Landing Page

The “My Services” functionality is a representation of the services which the user has been enrolled/has access to utilize:

Figure 2.1‑2 – example of My Services Page