RegoXchange
  • 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.
  • 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.
  • 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.
  • 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.
  • The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task.  This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
    Column Label Description
    Timesheet Period Start Range of time periods to display filtered by start date
    Timesheet Period Finish Range of time periods to display filtered by finish date
    Resource Resource(s) to display
    Type Note on a timesheet or time entry (task specific)
  • The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task.  This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
    Column Label Description
    Timesheet Period Start Range of time periods to display filtered by start date
    Timesheet Period Finish Range of time periods to display filtered by finish date
    Resource Resource(s) to display
    Type Note on a timesheet or time entry (task specific)
  • The Timesheet Notes portlet displays all timesheet notes split out by resource, investment and task.  This is very useful in situations where you want to review multiple notes as you do not have to open each note separately. The table below describes the available filter fields in the portlet.
    Column Label Description
    Timesheet Period Start Range of time periods to display filtered by start date
    Timesheet Period Finish Range of time periods to display filtered by finish date
    Resource Resource(s) to display
    Type Note on a timesheet or time entry (task specific)
  • This is an automation to adjust the cost in financials (WIP) based on the standard weekly hours for salaried (Exempt) personnel. The process adjusts only the cost in WIP where the hours per week that are posted for a resource are more than the standard work week. The Posted hours in the timesheet and in WIP remain untouched.   For the process to calculate correctly, all time in a given week needs to be accounted for, including all non-project time. The process has three input parameters as explained below:
    • wkStdHour: Standard Weekly Hours; this can be changed in the process gel script. The parameter is based on the organization standard work week. The default is set to 40 hours.
    • xogBatchSize: The XOG batch size.  This is used to upload data in batches to avoid high memory and performance issues. The default batch size is set to 50 records.
    • username: The resource name that the process uses for uploading data. The default is set to admin.
    • It will process all the timesheets in posted state provided the timesheet has not been adjusted earlier by this process and there are no pending transactions to be posted for it. Validation is made based on Notes field, which is populated once adjustment is done by the process.
    • Notes field should not be modified in Script nor should be worked upon by any other process.
    • All the invalid transactions should be cleared and post to WIP should be finished with no pending records.
  • Timesheet compliance is a dashboard containing multiple visualizations that shows timesheet compliance data under various scenarios. Dashboard shows count of timesheets grouped by Status and total available timesheets. % Time Compliance – Gauge graph that shows percentage of completed timesheets against overall timesheets. Compliance by Resource Manager – Grid section that shows percent timesheet compliance by resource manager. Timesheet count by Employment type and Timesheet Status – Stacked column chart, each column represents Employment type and sections of the column represent count of timesheets by Status. Count of Timesheets by Months – Stacked column chart, each column represents a month and sections of the column represent count of timesheets by Status. Dashboard also const of two grid sections displaying number of Open timesheets by Organization and Vendor.
  • The Timesheet Audit portlet displays timesheet information in order to perform an audit.  The only required data needed to search the portlet is start and finish date. Additionally, you may narrow the results by filtering by resource, resource ID, OBS Unit, resource manager, timesheet status, project, and task. The portlet provides reporting on the following:
    • Resource
    • Resource ID
    • Email Icon of Resource (So the reviewer can quickly email the Resource)
    • Resource is Active
    • Resource Open for Time
    • Time Period (Start and Finish Dates)
    • Timesheet Status
    • Is Adjustment (If the timesheet is adjusted)
    • Timesheet Modified Date
    • Timesheet Posted Date
    • Timesheet Submitted By
    • Timesheet Approved By
    • Project
    • Task
    • Proposed ETC Hours
    • Pending Actual Hours
    • Total Actual Hours
  • The Timesheet Audit portlet displays timesheet information in order to perform an audit.  The only required data needed to search the portlet is start and finish date. Additionally, you may narrow the results by filtering by resource, resource ID, OBS Unit, resource manager, timesheet status, project, and task. The portlet provides reporting on the following:
    • Resource
    • Resource ID
    • Email Icon of Resource (So the reviewer can quickly email the Resource)
    • Resource is Active
    • Resource Open for Time
    • Time Period (Start and Finish Dates)
    • Timesheet Status
    • Is Adjustment (If the timesheet is adjusted)
    • Timesheet Modified Date
    • Timesheet Posted Date
    • Timesheet Submitted By
    • Timesheet Approved By
    • Project
    • Task
    • Proposed ETC Hours
    • Pending Actual Hours
    • Total Actual Hours
  • The Timesheet Audit portlet displays timesheet information in order to perform an audit.  The only required data needed to search the portlet is start and finish date. Additionally, you may narrow the results by filtering by resource, resource ID, OBS Unit, resource manager, timesheet status, project, and task. The portlet provides reporting on the following:
    • Resource
    • Resource ID
    • Email Icon of Resource (So the reviewer can quickly email the Resource)
    • Resource is Active
    • Resource Open for Time
    • Time Period (Start and Finish Dates)
    • Timesheet Status
    • Is Adjustment (If the timesheet is adjusted)
    • Timesheet Modified Date
    • Timesheet Posted Date
    • Timesheet Submitted By
    • Timesheet Approved By
    • Project
    • Task
    • Proposed ETC Hours
    • Pending Actual Hours
    • Total Actual Hours
Go to Top