Pre-Onboarding

Submit a New Employee Onboarding ticket in Orion (to ensure that the equipment will be ready for the start date). This can be done as soon as possible, however cannot be moved forward until security is cleared. Recommend to submit this ticket when we have a tentative start date and Security Briefing form.

1. Equipment - DEVELOPER laptop, docking station, 2 monitors, keyboard, mouse, carrying bag

   • For contractors, only a developer laptop is required. However, verify with each contractor whether two monitors are required.

2. Access to TC Services or Applications - SM Service Manager Access, RDIMS Livelink

   • Add as a note: “____ should be added to the CAAST group in SM-GS.”

3. Software - AllFusion Erwin Data Modeler, AnyConnect VPN Client, Microsoft Access 365, Notepad++ (64-bit), SQL Developer

4. Cellphone (for employees only)

5. Elevated Privileges on a PC (Admin rights)

   • Justification: ___ will be working as a developer with Civil Aviation and requires local admin rights to perform their job duties (development, database work, etc.)

   • NOTE: This may no longer be the case. Some people have had service desk say that this will no longer be done before equipment pick-up, a separate ticket must be submitted for this. Currently confirming this with Service Desk.

6. Access to a Shared Network Folder

   • \\NCRWS548\SCRIPTS\CIVAV\ and all subfolders (Modify)

   • \\TC4S0A\GROUPS\AARA\AARAD\ and all subfolders (Modify)

   • \\NCRFS11\NACIS$\ and all subfolders (Modify)

   • \\NCRFS11\PROJLIB\ and all subfolders (Modify)

   • \\NCRFS11\POWERBLD\ and all subfolders (Modify)

   • \\TC4S0A\GROUPS\CIVAV SHARED\ and all subfolders (Modify)

7. Additional Info

___ will also require access to MyDesk Citrix (with an Entrust token generator) and GC Remote Access (GCSRA). They also require send access to the shared inbox: DSD FOAEA / LAEOEF DGSN TC-FOAEA@tc.gc.ca.

Once the user account has been created

Request a TC ID/Access card (ONCE HAVE CONFIRMED START DATE)

1. Send email to Departmental Security

   • Template found here: NCR - TC Request for ID/Access Card Instructions (RDIMS 18484474)

     • Access required: normal hours; 24 hour for IT-03 and above

     • Security file no.: In security verification email or in file no field on security briefing

     • Screening expiry: Reliability/Secret - 10 yrs from date of issue; Top Secret - 5 yrs from date of issue

   • Include an ID picture (see attachment below for specifications)

   • [For NCR] Confirm access card will be ready for the employee to pick up on the equipment pick-up date. Unless an escort is available, employees will need ID card to let themselves in to access IT kiosk on 21st floor.

1. Request Visual Studio/MSDN license

   • Send an email to DSTO Procurement and Contracting / Acquisitions et contrats DGSN DSTOProcurementandContracting-AcquisitionsetcontratsDGSN@tc.gc.ca with the details (transfer of license from who to who, etc).

2. Submit a Smart IT ticket in Orion to add them to the CIVIL AVIATION support group

3. Invite to Confluence (edit rights)

   • Send request to Edith Tremblay (usually via email or Teams chat)

   • Optional: Add them to Teams page in Confluence

4. Request Application Developer Role in Azure Portal

   • Create Work Order in Smart IT

   • Fill out request form: https://tc3oe.tc.gc.ca/ssp-pls/en/Forms/AddApplicationDeveloperRole

   • Add to TC-CivAv group (done by any owner of the security group)

To be done by Team Leads

1. Add user to distribution lists

   • TC.F NCR AFCCC RCN F.TC → for employees (also grants access to DSD CivAv Team calendar)

   • TC.F NCR AFCCC Consultants / Consultants RCN F.TC → for consultants (also grants access to DSD CivAv Team calendar)

   • DL OTT SC TFS AARAD Contributors → for update access to TFS repos

   • TC.F NCR AFCH Erwin DM EN RCN F.TC

   • Team specific DL

     • TC.F NCR AFCCC Team Avro Arrows / Equipe Avro Arrows RCN F.TC

     • TC.F NCR AFCCC Team Medevac / Equipe Medevac RCN F.TC

2. Use of Equipment Off Premises form don’t think this is used anymore….

3. Invite to meetings

   • Daily Stand-Up / Backlog Refinement / Sprint Review/Retro/Planning

   • Solution Center Community of Practice → Add to SC DEV Community of practice group in Azure

   • MSS Developers Lunch & Learn

4. Add to teams in MS Teams channels (DSD-Civil Aviation channel & Team Avro Arrows/Medevac team)

   • Tag member according to team they have joined

5. Add to appropriate team(s) in Azure DevOps