Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

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.

When employee goes to pickup equipment at Service Desk (LRA agent), have them request to have the MyKey creation started. They will need to show 2 pieces of ID and do not need their PRI. The LRA agent will submit the paperwork to SSC (~24-48 hour turnaround time).

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)

Review the Employee ID and Access Cards section of TC Access Control. An ID / access card identifies your role at TC, and grants access to TC spaces.

As of Oct 2022, Departmental Security will no longer accept the form 10-0401. Incomplete requests (missing information) or requests not approved by the responsible manager will not be processed.

  1. Request Visual Studio/MSDN license

  2. Add user to distribution lists

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

  4. Use of Equipment Off Premises form

  5. Archived: Telework Agreement form - EN or FR

  6. 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

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

    • Tag member according to team they have joined

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

  9. Invite to Confluence (edit rights)

    • Send request to Edith Tremblay

  10. Request Application Developer Role in Azure Portal

  • No labels