7. Job Management Contents Job Management Job Allocation/Costing Resource Availability Logic Job Costing Logic Timesheet Payroll Submission Job Management Within the "Job Creation" modal, the "Resource Requirements" section has been enhanced to enable definition of the role (group) applicable to the job to align with easyemployer's requirement of limiting a resource's shift to only having a singular role of delivery related. Figure 1. Resourcing requirements while scheduling a job. Unscheduled Reason When the "Unscheduled" checkbox is checked, then an unscheduled reason must be selected from the associated menu. Figure 2. The option to provide an unscheduled reason. Job Allocation/Costing The "Job Edit/Allocation" modal can be accessed by proceeding through job creation, or via the "Roster Management Console" using the right-click mouse options. Figure 2. The job allocation and costing option once a job has been created. Figure 3. The roster management console displaying the mouse options menu. Figure 4. The job edit and allocation console. Resource Availability Logic For a person (resource) to appear in the "Available Resources" panel (ready for allocation to the job), the following criteria need to be fulfilled: The resource is defined as delivering within the region related to the job. There is no exclusion record between the resource and the client's account. The resource has the ability, per their related resource tags, to deliver the tags defined as required against the job. There are no conflicting job allocations or unavailabilities. If another job allocation exists before the job, the resource has adequate travel time between the two. Has an existing shift record that satisfies any of the below criteria: There is an existing shift for the resource during a job period for the same role related to the job, OR There is an existing shift for the resource for the same role related to the job, outside of the job period, but within the job gap threshold (defined in custom setting), OR Has general availability (via an individual availability record or an availability template) for a resource where their employment type is not equal to "Full-Time." For an asset (resource) to appear in the "Available Resources" panel (ready for allocation to the job), the following criteria need to be fulfilled: The resource is defined as delivering within the region related to the job. There is no exclusion record between the resource and the client's account. There is no conflicting job allocation or unavailability. If another job allocation exists before the job, the resource has adequate travel time between the two. Job Costing Logic To determine the costing of a resource to deliver a job: Skedulo passes the current job as either a standalone shift or as a part of an existing shift (if one was identified it could be related to)—along with all other existing shift records within the current roster period (for each resource selected) to get the costing from easyemployer. easyemployer identifies if any award rules would be broken (if so, overtime compensation levels apply to the shift), then returns the rates to Skedulo in data sets. As these costs are for the entirety of the shift's length, to get true job costing, Skedulo then divides each data set by the shift duration and then multiplies those costs by the job’s duration and surfaces these values within the "Normal" cost and "OT" (Overtime) cost fields for the selected resources. Allowances (such as laundry etc.) are currently considered to be apart of a resource's normal compensation and therefore are rolled into and form apart of what is shown as the "Normal" cost. Figure 5. Resource job costings being displayed during job edit and allocation. Figure 6. Skedulo + easyemployer job costing flow diagram. Timesheet Payroll Submission Within the timesheet console, the ability to submit a finalized timesheet is provided via a "Submit to Payroll" button. When the timesheet console is accessed, and the following criteria met, the "Submit to Payroll" button will show: "Shifts" view/display within console has been selected (will not show when viewing jobs). Timesheet being viewed has been approved. Timesheet field of "Date/Time Timesheet Submitted for Payroll" does not already contain a value. Figure 7. A timesheet ready for submission for payroll. On selection of "Submit to Payroll" the following will occur: A check will run to see if any shift records related to the timesheet are (a) not at a status of "Complete" or "Finalized," or (b) have a break recorded without a break code value—either of these results will return an error message preventing the timesheet from being submitted. These data discrepancies are required to be resolved before the timesheet will be accepted by the payroll import endpoint. Figure 8. Examples of data discrepancies for shift records. If no data issues are detected within the records related to the timesheet, they will be submitted to easyemployer. Should the import be successful, the following actions will occur: Shift records will be created within easyemployer. In Skedulo, the timesheet field "Date/Time Timesheet Submitted to Payroll" will be timestamped. In Skedulo, the shift field "Date/Time Shift Submitted for Payroll" will be timestamped. In Skedulo, the shift status field will be updated to "Finalized." If the submission fails, easyemployer will return error codes and details of the errors. Some of these error messages will give details of the data requiring resolution. Alternatively, your easyemployer account manager should be contacted to provide additional guidance/information on how to resolve. Figure 9. Skedulo + easyemployer timesheet integration flow diagram. For guidance and information on the resource submit for approval and approval processes, refer to Timesheet Add-On. Back to top. Related articles 8. Custom Forms on the Skedulo Mobile App 6. Roster Management Functions 3. Group Events 16.1 Aged Care Service Management Console 1. Overview Comments 0 comments Please sign in to leave a comment.