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 22 Next »

Chef links directly to this page for reference. Do not delete this page.

What is a resource?

Chef is the friendly interface to the RRU Resource Management system (Unit 4). Chef relies on Unit 4 for information about organizational structure, and roles within itself to determine access to certain functionality. If you were a CAMP Admin, you will notice some differences in how Chef behaves vs. how CAMP behaved.

A resource is any person with a non-student relationship with RRU. This includes employees, academic contractors, non-academic contractors, and guests.

  • Only managers/resource administrators or delegates can create employee resource records and submit them for approval from HR. Records are released for computer account creation once HR approves. Only HR can terminate a computer account/employment for employees.

  • Resource administrators, delegates, and ‘delegates for contractors’ can create and submit contractor resource records. No approval is required from HR. Records go immediately for computer account creation. This same group can terminate a computer account/employment for contractors.

Choose from these types

Comments

Managed by manager/resource administrator?

Managed by delegate?

Managed by 'delegate for contractor?

HR approval required

Academic Contractor

  • paid by Finance

  • Associate Faculty, facilitators, Thesis and Dissertation supervisors, etc.

(tick)

(tick)

(tick)

Contractor

  • paid by Finance

  • hired for non-academic work

  • includes project managers, certain specialists, etc.

(tick)

(tick)

(tick)

CUPE

  • paid by Payroll

  • in the employee (CUPE) union

(tick)

(tick)

(tick)

Exempt

  • paid by Payroll

  • non-union employees

(tick)

(tick)

(tick)

Guest

  • not paid

  • Board of Governors, guest speakers, etc.

(tick)

(tick)

(tick)

Research

  • paid by Payroll

  • hired specifically for research work

(tick)

(tick)

(tick)

RRUFA

  • paid by payroll

  • members of the faculty (RRUFA) union

(tick)

(tick)

(tick)

Enter resource information

Don’t make this mistake

Wait! A common mistake is to enter the preferred name incorrectly. Please see the example below.

First name

Preferred Name

Last Name

Correct?

Robert

Bob

Smith

Yes! (tick)

Robert

Bob Smith

Robert

No. ❌

In the ‘preferred name' field, please enter just the name by which the person wants to be called, like ‘Bob’.

Information about the fields on the form

Follow the prompts as you enter information in the form.

Here’s important information about some of the fields:

You’ll choose a resource type to get started.

image-20240604-150311.png

The list of resource types in the drop down list come from Unit 4.

When an employee type resource is added, there is an approval checkpoint at HR before the record is moved along to have a computer account generated. And HR is the only group who can terminate a computer account.

The employee types are CUPE, Exempt, Research, and RRUFA.

When a contractor type is added, there is no HR involvement. Information goes directly to the computer account creation process. Resource administrators can manage the computer account termination date.

The contractor types are Academic Contractor, Contractor, and Guest.

The information collected for an employee type is slightly different than that collected for a contractor type. An example is shown below, where Chef is asking for “employment details”. This is for an employee type. If this were a contractor type, Chef would be asking for “business details”.

image-20240423-224426.png

-1- the Primary Groups field is a drop down list that is the same as the list used in CAMP. Eventually, this will change so that we’re using the information from Unit 4 but we cannot make that change until Unit 4 and Chef are both live and working together.

-2- / -3- The Campus Location and Office Building fields, and others you may encounter, are drop down lists from which you can choose a predetermined value. Managing information this way ensures consistency in data collection and in reports. Campus location could be ‘Colwood’ for 2005 Sooke Road, ‘Langford’ for the campus on Goldstream, or ‘Remote’ for someone who is fully remote. If you choose ‘Remote’, you will not be asked to provide an office/room, etc.

-4- The Contract start date is the date the new person will start work.

Employees will not have an account expiry date so there will be fewer notices about account expiry dates than you received previously. Contractors have expiry dates. You will continue to receive notices about these. All of these notices come from the account management process, not Chef, just as they did not come from CAMP in the past. The account creation & termination process hasn’t changed yet.

-5- Indicate where computer account related notices should go. Many departments use a shared email box for this so that more than one person can respond to notices.

-6- Only positions that report to this hiring manager or for whom this person has been designated the resource administrator (according to Unit4) will display in this dropdown list, even if it’s the delegate entering the information.

If the new person is a contractor, there will be no ‘position’ as these exist only for employees. In this case, you’ll type the person’s title.

-7- By default, new people are not added to the Contact directory located on www.royalroads.ca. Toggle this on if you want the new person’s name to be listed in the directory. A resource administrator can toggle this on behalf of a new person when they are entering the record. Once the record has been saved, only the person can toggle this option.

If the new person is faculty or associate faculty, they may wish to have a biography included in the Faculty Directory. If so, you’ll ask for that in the provisioning form, which you can complete once the person has a computer account.

Find out how to process/prevent duplicate resource records.

  • No labels