RegoXchange
  • The Rego Estimation Module Provides a more accurate estimate earlier in the idea/project lifecycle.
    • Is applied consistently so it can be improved.
    • Retains the data in Clarity to enable analysis.
    • Provides ongoing feedback by comparing estimates to current EAC.
    • Provides historical record of estimating for projects overall as well as change requests.
  • The Rego Estimation Module Provides a more accurate estimate earlier in the idea/project lifecycle.
    • Is applied consistently so it can be improved.
    • Retains the data in Clarity to enable analysis.
    • Provides ongoing feedback by comparing estimates to current EAC.
    • Provides historical record of estimating for projects overall as well as change requests.
  • The Rego Estimation Module Provides a more accurate estimate earlier in the idea/project lifecycle.
    • Is applied consistently so it can be improved.
    • Retains the data in Clarity to enable analysis.
    • Provides ongoing feedback by comparing estimates to current EAC.
    • Provides historical record of estimating for projects overall as well as change requests.
  • The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
  • The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
  • The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
  • 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.
  • 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 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.
  • 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.
  • Are you on an older version of CA PPM?  Do you want to understand the value of the new features and functions in recent versions?  Have you seen the new UX and do you wonder when is the right time to move over?  This class is a demonstration of the new UX, new features in both classic and new UX, and the value of these features for customers.
Go to Top