Page Comparison

...

1. Equipment - DEVELOPER laptop (indicate in “Additional Information” field), 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 → *** A series of separate Software Requests are now required for Erwin, Access, and SQL Developer. ***

   • Note: MSDN license request must be sent separately through email.

4. Cellphone (for employees only)

5. Elevated Privileges on a PC (Admin rights)

   • NOTE: A separate ticket must be submitted for this.

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

...

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 SDG Procurement and Contracting / Acquisitions et contrats (TC/TC) SDGProcurementandContracting-AcquisitionsetcontratsGSN@tc.gc.ca with the details (transfer of license from who to who, etc). It is recommended to CC Rob Troy and Jorge Lobo.

2. Request local admin

   • Submit an Orion ticket.

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

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

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)

5. Invite to Confluence (edit rights) We are eventually moving off of Confluence, no new licenses are being given out. If updates need to be made, please contact a team member who has an existing license for assistance.

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

   • Optional: Add them to Teams page in Confluence

To be done by Team Leads

1. Add user to distribution lists

   • TC.F NCR AFCCC Employees / Employes 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)

   • 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

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

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

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

3. Add to teams in MS Teams channels (DSD-Civil Aviation channel)

   • Tag member according to team they have joined

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

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