RegoXchange
  • The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. 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:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) AND project manager (PM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM or PM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. 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:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) AND project manager (PM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM or PM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Timesheet Approval - RM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. 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:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Timesheet Approval - RM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. 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:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • Portlet to show the stage of any Action Item triggered by Timesheet submission.  Portlet allows for a period start date input, filters by Resource, Approver, Action Item Status and Timesheet Status.  A link to the action item is provided for direct action by review if needed. This portlet is only for the clients who have established a process that triggers on Timesheet Status change to Submitted and to send Action Items to the person responsible for timesheet approval/validation i.e. PM for project tracking and/or RM for overall approval of the timesheet. The portlet won’t display any data if there are no timesheet Action Items.  Examples of such processes would be CA’s OOTB Project Manager Approval or the Timesheet Approval - PM and RM process found on RegoXchange.
  • Portlet to show the stage of any Action Item triggered by Timesheet submission.  Portlet allows for a period start date input, filters by Resource, Approver, Action Item Status and Timesheet Status.  A link to the action item is provided for direct action by review if needed. This portlet is only for the clients who have established a process that triggers on Timesheet Status change to Submitted and to send Action Items to the person responsible for timesheet approval/validation i.e. PM for project tracking and/or RM for overall approval of the timesheet. The portlet won’t display any data if there are no timesheet Action Items.  Examples of such processes would be CA’s OOTB Project Manager Approval or the Timesheet Approval - PM and RM process found on RegoXchange.
  • Portlet to show the stage of any Action Item triggered by Timesheet submission.  Portlet allows for a period start date input, filters by Resource, Approver, Action Item Status and Timesheet Status.  A link to the action item is provided for direct action by review if needed. This portlet is only for the clients who have established a process that triggers on Timesheet Status change to Submitted and to send Action Items to the person responsible for timesheet approval/validation i.e. PM for project tracking and/or RM for overall approval of the timesheet. The portlet won’t display any data if there are no timesheet Action Items.  Examples of such processes would be CA’s OOTB Project Manager Approval or the Timesheet Approval - PM and RM process found on RegoXchange.
  • 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
  • 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.
  • 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.
Go to Top