The intent is to prepare a list of tasks that will prepare for a new employee or consultant to join the Financial Systems Team.
DSD-Finance Contractor and Employee Onboarding
Created by Bruce Williams specifically for Finance
May 14, 2020
Assumption: contractor/employee has been successfully passed his/her interview, accepted the work, and has passed security clearance screening.
1-2 weeks before start date
Find office for contractor to work (needed before submitting NSR)
Submit NSR
Developer Laptop
Laptop lock and docking station
Dual monitors
Local Admin Rights (may need a separate NSR)
Jabber, Webcam and Headset
Cloud Services Account (may need to make this request directly to Ryan Lefebvre and Jonathan Racicot after contractors TC account is created)
Oracle - Ora Client 11g
Entrust Intelligence
Hummingbird Connectivity 2008 X64
Submit Non Standard Product Justification (NSPJ) for the following software:
Visual Studio Pro
http://tcapps/Corp-Serv-Gen/5/NSPJ-JUPNS/u001-eng.aspx
Get Access Card form filled out and signed by DSD-Finance manager
Set up access to Oracle Applications Development Environment.
In addition to Inquiry and Technical Support a developer will need the Appliction Developer functionality and System Adminsitration functionality. System Administration in order to simulate other user responsibilities in the development environment in an attempt to reproduce user production problems in the development environment.
Set up access to Oracle Applications Acceptance Environment.
Using RDIMS 38866 Integrated User Access Form for Financial and Material Management Systems obtain access to the following applications:
Oracle R12 - Inquiry and Technical Support
Salary Management System
Hyperion
Business Objects
Set up Unix Account.
1 week before start date
Make sure that you’ve received confirmation from Service Desk that the NSR has been actioned and that the contractor’s equipment is ready and waiting in the Service Kiosk on the 21st floor
Find 1 or 2 “buddies” on team that the contractor will be able to shadow during his/her first week
Add contractor to DL OTT AFCCB (ALL) distribution list (should we re-instate Staff distribution list to only communicate with employees to prevent any possible issues with regard to employee-only events/communication?)
Contact Service Desk to have contractor added to the APPS_Finance group in SMGS
First Day
Meet contractor in lobby. Bring access card form and get contractor’s ID created.
Take contractor to Service Kiosk to pick up equipment.
Take contractor to his/her desk then introduce the contractor to his/her “buddies”.
Buddies should help contractor install any tools/products needed for development
Install from L:/12i/Developer_Software/SQL Navigator 6.4
Install from L:/12i/Developer_Software/Putty
Install from L:/12i/Developer_Software/Surround SCM Client (Seapine Software)
Install from L:/12i/Developer_Software Workflow Builder
Install from L:/12i/Developer_Software BI Publisher
Buddies should help the employee/contractor access:
DSD-Finance Confluence pages
through Confluence access Oracle Applications On-Line Documentation
Azure DevOps
Install and use MS Teams
Access Oracle Applications Software Development Environment
Query up purchase order T8080-190820
Navigate to the Distributions screen and provide an explanation of the financial distribution; specifically responsibility centre, line object, PI code, and allotment.
Load up Business Objects and run a GL Account Analysis by RC and Project for RC 1873 and project 65AA.
Load up SQL Navigator in the Oracle Applications Development environment and run the following SQL:
select count(*) from GL_CODE_COMBINATIONS;
Load up SMGS and access incident IM310120.
Introduce the contractor to the team he/she will be working with at DSD-Finance
Contractor should be made aware of Fire/Evacuation Procedures
Contractor should be made aware of guidelines/process for leave and absences. Note: contractors are not paid for any leave and are not permitted to work from home (exceptions to this rule will be up to manager’s discretion).
Contractor should be made aware of DSD-Finance employees and management contact names, numbers and e-mail addresses. Names of Importance can be found in the following DSD Hierarchy chart:
Contractor should be told who to contact in case of emergency or issues that come up: Michel Brault RC Manager Applications Finance
First Week
Contractor should continue to shadow a “buddy” for the first week. Focus should be on showing the contractor the common tools and procedures used in DSD-Marine for application development and support (depending on the contractor’s role).
One of DSD-Marine’s scrum masters should meet with the contractor to give an overview of Scrum/Agile and how we work at DSD-Marine including a tutorial on creating and using PBI’s and tasks in DevOps.
Buddy should focus on showing the contractor the tools and procedures used to work, including proper use of SMGS, DevOps (repos), proper coding standards, push and pull requests from Git, and how code reviews are done
Proper use of databases and queries should be demonstrated to the contractor with appropriate guidelines to prevent accidents from happening
By the end of the first week, the contractor should be able to be given a PBI, break it down into tasks, complete development, and submit for code review. In the case of a DATA fix, the contractor should be able to identify how the work was done and show that due diligence was followed in resolving the issue.
Contractor should be able to work (or prepared to work) without any immediate supervision - though work quality, output, and workplace behaviours will be regularly reviewed by management.
First Month
Fully integrated into a project and/or scrum team, working and producing quality results
Quality of work is continuously improving based on code reviews by DSD-Marine developers and overall review by scrum masters/supervisors/managers.