RegoXchange
  • Course Description:   Have you considered using Rally Software® in conjunction with Clarity PPM? Have you seen or heard about the OOTB connector? This class will go through the OOTB connector in detail and show how Rego has built addons to enhance the connectivity between these two tools.
  • Course Description:   Are you struggling to implement Agile tools at your organization alongside Clarity PPM? This class will review best practices for implementing Agile tools in conjunction with Clarity PPM while living in a bimodal world. We will discuss how Clarity PPM can govern both types of work and teams and how Agile tools should interface with Clarity PPM.
  • This is a list of 12 typical maintenance items that should be completed for Clarity on an annual basis.  There is also a short list of items that should be completed periodically depending on client policies.
  • A quick reference guide that reviews all of the icons used in the vertical menu bar and provides a quick explanation on their meaning/use.
  • ** No Download - Do not Add to Cart ** KPIs and metrics have been around forever. With the prevalence of Agile integrations and an increased focus on business value, it is time for a reimagining of progress and success measurements in Clarity. In this webinar, Rego expert guides Alyson Poston and Wes McCoubrie will discuss the following: - Metrics you should monitor beyond the traditional Scope, Schedule, Cost and Effort. - Key Agile data you should incorporate into your metrics. - Today’s critical business metrics and key results (OKRs) to track. - What comes out-of-the-box with Clarity, and of those, which ones does Rego recommend you introduce into your organization. ** No Download ** follow this link to sign up to view the recorded webinar - http://info.regoconsulting.com/clarity-kpis-and-metrics-march-2021
  • What integrations are the most requested and the most utilized? This class will review the most common interfaces to and from Clarity, including best practice use cases and lessons learned from real implementations.
  • Want to keep your Clarity environment running efficiently? In this class we'll discuss how to maintain your Clarity environment through the use of jobs, processes, and configuration. We'll also cover recommended maintenance activities to ensure your environment is running optimally.
  • "Ensure you are keeping tabs on your Clarity environment. Clarity has key components that require monitoring to ensure consistent processing: - identify key modules like processes, jobs, financials, among others - identify customizations and common errors that can be improved"
  • A presentation slide deck from Rego University 2022.   This document reviews best practices for maintaining Clarity.
    • Why is it required?
    • When?
    • Processes
    • Jobs
    • DWH
    • High Volume Data
    • Access Rights
    • Volatile Date
    • Rego’s Recommendations
  • Ensure you are keeping tabs on your Clarity environment. Clarity has key components that require monitoring to ensure consistent processing: - identify key modules like processes, jobs, financials, among others - identify customizations and common errors that can be improved - Overall maintenance recommendations for Clarity Studio and MUX
  • The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment.   The following metrics are monitored:   Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours       Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment.   The following metrics are monitored:   Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes   Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours       Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours   Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours
  • The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment. The following metrics are monitored: Process Engine  Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Incremental                      Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours  
Go to Top