RegoXchange
  • Maximize the value of your training delivery by increasing end user engagement with the course content. Discuss options to optimize efficiency and help ensure users are engaged while participating in training.
  • A presentation slide deck from Rego University 2022.   This course reviewed Adoption Metrics and Reliable Data Collection.
    • Reliable Data Collection and Business Performance
      • Adoption Metrics and Customer Adoption
      • Data Quality, Data Integrity and Ensuring User Confidence
      • Business Performance
  • A .pdf file that has the slide by slide presentation at 2015 RegoU on basic administration of CA PPM.  The agenda covers an administration overview, objects, lookups, OBS/Security, portlets, processes, and support items.
  • Course description: “Does CA PPM Timeslice functionality seem like a foreign language to you? This intro to timeslices will cover an Overview of Timeslice Fundamentals, Terminology, Best Practices, Diagnostics, and the basic SQL Constructs to get you started.”
  • This allows users without admin access to see the timeslice settings and also allows the data to be exported to excel easily.  Many organizations like to document their timeslice settings which is a manual process as you cannot export the timeslice page to excel.  This allows them to periodically export the portlet results to excel to meet their documentation requirements.
  • This allows users without admin access to see the timeslice settings and also allows the data to be exported to excel easily.  Many organizations like to document their timeslice settings which is a manual process as you cannot export the timeslice page to excel.  This allows them to periodically export the portlet results to excel to meet their documentation requirements.
  • This allows users without admin access to see the timeslice settings and also allows the data to be exported to excel easily.  Many organizations like to document their timeslice settings which is a manual process as you cannot export the timeslice page to excel.  This allows them to periodically export the portlet results to excel to meet their documentation requirements.
  • 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.
  • 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.
  • The Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects.
Go to Top