- 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: -
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
-
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 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 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.
-
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 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) -
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.
