RegoXchange
  • “Of course we have a plan for PPM!”  This might be the response of any organization that’s considering PPM or has a solution in place. But having the technology doesn’t necessarily mean having an effective plan for it. This white paper breaks down what it means to have a strategic PPM roadmap, and why your organization should always keep it current and close at hand. We’ll define the elements that make a roadmap effective and provide seven reasons it can make the business journey worthwhile. This White Paper is downloaded from the Rego Consulting site. You will be asked to provide your email address and current ppm tool.  - http://info.regoconsulting.com/ppm-roadmap-white-paper ** No Download - Do not Add to Cart **
  • A presentation slide deck from Rego University 2022.   A course outline for strategic planning for your PPM Tool.
    • Defining the Value of a Strategic Roadmap
    • Roadmapping Methodology
    • Best Practices
    • Real-World Examples
      • Long-Term Focus
      • Short-Term Focus
      • Annual Planning Support
  • A presentation slide deck from Rego University 2022.   This document reviews the discussion around AI and the more realistic option of Predictive Modeling that exists in the near future of PPM.  Then the group worked on ideas to bring to PPM tools via PM.
    • Predictive Modeling / AI Trend
    • Why are we here?  Goals for this session
    • Creativity Workshop - Brainstorming
    • Summary of Themes
    • Qualify top Themes
  • Learn what you need to do today to be ready for the AI Innovation coming our way.
  • 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.
  • Course Description:   Does your organization struggle to understand your fully burdened TCO for the applications that enable your business? Do you use spreadsheets and disparate data sources to manually calculate TCO? This session explores the data sources needed to calculate the fully burdened TCO for applications. We will also cover marketplace tools that allow you to track spending, providing trends of applications broken down by run and development costs.
  • The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
  • The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
  • The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
  • For each process, the Process Run Metrics portlet shows the Process Name, Process Code, Description, # Running, # Completed, # Errored, and Last Run Date. This portlet is ideal for system administrators and support staff needing to monitor the health of the environment. Viewers of this portlet can get a sense of the complexity & health of the environment with the # of processes running and visibility into processes that errored out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Process Name Name of the process
    Start Date Start date of the process’s last ran date
    End Date End date of the process’s last ran date
    Description Description of the process
    Process ID ID of the process
Go to Top