-
This portlet provides a view into the number of timesheets that were expected to be completed for a specified time period(s) as well as the number of timesheets that were completed and the percent complete. This can also be filtered by OBS so that a company can see timesheet compliance at the OBS level. -
This video reviews the process of creating Timesheet Adjustments – making changes to a timesheet after it has been posted. -
Resource Availability – 4 Weeks displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks. This report also displays Resource Primary Role and Employment Type. User can further narrow their search by Resource Name, Resource Type & Week Start Date. User can use exact dates or relative dates for Week Start Date filter parameters. -
The Timesheet Smoothing Process Workflow kicks-off when an individual timesheet is Submitted. It splits each transaction on the timesheet when total timesheet actuals exceed total weekly availability for the resource. Total weekly availability is determined by multiplying resource availability rate by the number of workdays in the week. Non-workdays include weekends, holidays, PTO, and other scheduled days off, as set on the resource calendar. If timesheet actuals <= total weekly availability, then the timesheet remains unchanged. But if timesheet actuals > total weekly availability, then the following occurs. Each timesheet transaction is reduced by a calculated percentage that will reduce the total regular hours to equal the total weekly availability. Then the remaining transaction hours are placed in a “Split” row for that task on that day, with an Input Type Code set based on a process parameter (which parameter can be set within the script action on the process). Note: If a single day has overtime hours, but the total timesheet actuals <= total weekly availability, no splitting occurs. -
This process workflow with gel script forces billable hours on timesheet down to 40 hours, and sets overtime hours to non-billable. Timesheets with 40 or fewer hours are not touched. Process kicks off upon submission of timesheet. Steps are:- Determine if timesheet has > 40 hours. If so, proceed.
- Create a SPLIT row for each timesheet row, with Input Type Code = Non-Bill.
- Divide 40 by total timesheet ours. Store this value.
- Multiply each timesheet cell by the stored value, and enter the result into that cell.
- Take the difference (original cell value – new cell value), and enter in same cell on Split row.
- The end result will be 40 hours total on Billable rows, and overtime hours on Non-Billable rows.
-
A Resource Calendar sub-object is populated by a non-object-specific process, executed by the “Execute a Process” job, which can be scheduled. The first 7 rows of the sub-object display the standard week from the base calendar, including columns for Day of Week, Is Workday (checked/unchecked), Shifts, and work Hours available. The remaining rows display calendar exceptions, including columns for Day of Week, Exception Date, Is Exception (checked), and work Hours available. If exception changes to a workday, Is Workday column is checked, and Shifts also display. If exception changes to a non-workday, Is PTO column is checked. Resource Calendar object is filterable by Calendar Entry Type (All, Calendar Exception, Day of Week), Day of Week, Exception Date Range, Is Workday, Is Exception, Is PTO, and power filter. -
The Grant Resources Timesheet Edit Rights process will grant each resource timesheet edit instance rights to his or her own timesheets. This process will not remove any existing timesheet edit instance rights. -
The Timesheet Approval - Auto process is an auto-start process that begins once the resource submits his or her timesheet. This process bypasses a Resource Manager approval and allows the user to post his or her timesheet. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
Resource Availability – 4 Weeks is a grid portlet that displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks. If % Available is negative, this indicates an over-allocation. Zero% Average Availability indicates fully allocated (no remaining availability). Filterable by Role, Resource, Resource Type, Full-Time/Part-Time, Availability Range. Contractor Type is a custom attribute (Lookup - String) created on the Resource object. It is attached to the lookup, Contractor Type (Lookup ID: REGO_CONTRACTOR_TYPE) that has static values Part Time (PT) and Full Time(FT). -
The Timesheets by Resource portlet gives the ability to highlight the time periods where resources are working overtime or working less than 25 hours a week. The filter requires timesheet Start Date and End Date to be provided. Additionally, the information can be filtered by Resource, Resource ID, OBS Unit, Employment Type, Resource Manager, Open for Time, and Active status. This portlet displays Resource, Resource ID, Active (yes/no), Employment Type, Primary Role, Resource Manager, and Timesheet Hours Flag. The flags are set with the logic- Yellow = timesheets not posted / zero hour timesheets
- Green = where number of hours posted is > 25 and less than 45
- Red = where number of hours posted is < 25 or > 45
-
The Pending Actuals portlet displays pending actuals for resources by task. This portlet allows the user to filter on Project, Project Manager, Is Active and Is Open for Time Entry. This portlet provides Resource Managers and Project Managers a simple way to analyse which actuals have been submitted but not posted on specific tasks, as well as the aggregate pending hour total. Note: the information displayed is dependent on what the user has security rights to view. -
The Pending Actuals portlet displays pending actuals for resources by task. This portlet allows the user to filter on Project, Project Manager, Is Active and Is Open for Time Entry. This portlet provides Resource Managers and Project Managers a simple way to analyse which actuals have been submitted but not posted on specific tasks, as well as the aggregate pending hour total. Note: the information displayed is dependent on what the user has security rights to view.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy