RegoXchange
  • This workflow is run as a scheduled or immediate Job to populate Project Cost Plans.  It can be configured to run on any desired set of projects.  It can be configured to populate the Cost Plan of Record based on Allocations or based on Assignments.
  • The Rego Group Rights portlet is a useful list view for functional administrators.  It provides a flat view of all the Global, OBS and Instance rights that have been granted to all the groups in Clarity. It can be further filtered by just the rights type and/or the security group. It is also possible to export out to file in spreadsheet (csv, xlsx) or PowerPoint formats with OOB Clarity functionality.
  • 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
  • Rego’s Clarity Adoption Metrics package consists of two sets of metrics: Project metrics, and Resource metrics. Project metrics measure how effectively project managers are using Clarity to manage their projects. Resource metrics measure how effectively resource managers are using Clarity to manage resources. Metrics are scored on a scale of 0 to 5, with higher scores indicating greater adoption and use. All metrics can be viewed numerically or graphically, and can be broken out by OBS. In addition, metric data can display as a 12-month rolling history to help identify trends. Project metrics can also display by lowest / highest adoption rates for a specific resource metric or all resource metrics. There is a variety of way to view the Adoption Metric data, therefore, Rego has made this simple by creating an Adoption Metrics object that contains multiple tabs.  Each tab displays one or more of the Project or Resource Adoption Metrics.  Based on the nature of the Metrics some tabs will allow the ability to use a pull down menu to select a specific Adoption Metric.   There is also a Metrics trending view that pulls monthly snapshots of the metrics. Project metrics consist of the following:
    • Project Status Reporting – Measures how well PMs create and publish project status reports.
    • Project Risk Adoption – Measures how well Risks are being used and managed.
    • Project Issue Adoption – Measures how well Issues are being used and managed.
    • Project Schedule – Measures how well PMs create tasks and keep the project schedule current.
    • Project Baseline – Measures whether or not baselines exist.
    • Project Zero ETC’s – Measures how well the PM assigns resources to tasks with ETCs.
    • Project Past ETC’s – Measures how many improperly scheduled tasks the PM has.
    • Project Milestone / Key Tasks – Measures how well PMs create and manage Milestones / Key Tasks.
    • Project Schedule Variance – Measures how effectively PMs manage their schedules.
    • Project Effort Variance – Measures how effectively PMs manage their project efforts.
    • Project Budget Variance – Measures how effectively PMs manage budgets or cost plans.
    • Project Unfilled Roles – Measures project roles with allocations that are already started or starting within the next 30 days.
    • Project Data Quality – Measures how effectively PMs complete the Description, Stage, Progress, Objective, and Sponsor/Business Owner fields.
    • Project Commitment – Measures the hard allocations for a project over a two week time frame.
    Resource Metrics consist of the following:
    • Resource Clarity Usage – Measures how often users log into Clarity.
    • Resource Timesheet – Measures if timesheets post in a timely manner.
    • Resource Allocation – Measures how well RMs keep total resource allocations within the expected range for future time periods.
    • Resource Actualy Utilization – Measures how well Resource allocations match actuals.
    • Resource Allocation Date in the Past – Measures how many resources are open for time entry with dates in the past.
    • Resource Data Quality – Measures how well RMs complete the Resource Manager and Primary Role fields and optionally the Skill and Employment Type fields.
    • Resource Commitment – Measures how much resource available time is committed to projects.
  • View Rate Matrix is a grid portlet that provides users a single place to view all the rates defined across multiple rate matrix without going to administration tab. Each Matrix may be defined with different columns (ex: Charge Code, Client, Department, Entity, Input type Code etc). This portlet dynamically brings only the columns associated with that rate matrix and provides the detailed information. User can view information related to one matrix at a time.
  • An HTML portlet that displays two buttons that link the user instantly to an object create page.  The portlet comes with two buttons and the buttons can be modified to link to any creation page.  Administrator can choose: Project, Idea, Application, Program, etc.
  • This solution provides an administrator the ability to log into the CA Clarity application as any user in the system.  This ability is especially helpful when troubleshooting user issues and security settings.   (Will not work with On-Demand Instances.)
  • This Process sends an email to every Action Item Assignee where the Due Date/Time has passed and the Status is either Open, or In Progress.  Users may want to modify this stalker to include Status = Deferred.  In addition, the Resource Manager for the Assignee receives a copy of the email. In order to generate emails, the SMTP gateway must be up and running and Resources must have a valid email address.
  • A process creating a new Cost Plan. Cost Plan properties:
    Name Cost Plan created on: yyyy/mm/dd hh:mm:ss
    Grouping attributes Charge Code, Transaction Type
    Start Period The earliest fiscal period with Actuals (from PPA_WIP table) or current period, if there are no actuals
    Finish Period The latest fiscal period with a non-zero allocation (from PRJ_BLB_SLICES table, SLICE_REQUEST_ID = 6
    Period Type Monthly
    Plan of Record True
    Planned Cost For periods in the past – from Actuals (Charge Code, Transaction Type, Quantity (Units), Cost (Amount) taken from Transactions (PPA_WIP & PPA_WIP_DETAILS); For current and future periods – from Allocations (Charge Code taken from the Project, Transaction Class from the Resource, Quantity from allocation slices, Cost from the Rate Matrix (NBI_PROJ_RES_RATES_AND_COSTS table)
    Pre-conditions:
    • the Project must be financially enabled.
    • if a new Team Member is added, Rate Matrix job must be run, so the rates are populated in the NBI table.
    • if the Allocation changes, allow the timeslice job to finish before running the process.
    • the Project should have the Charge Code set.
  • 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 Dashboard: Project Information portlet gives a set of high-level information about the project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet displays the name, project ID, project manager, description, start date, finish date, baseline start, and baseline finish.
  • This Portlet can be used to define User License Output information including the following:
    • Resource
    • Resource User Name
    • Resource Id
    • Email
    • Resource Manager
    • Resource Manager Email
    • Primary Role
    • Employment Type
    • Org Structure Path
    • Org Structure Lowest Unit
    • Last Logged in Date
    • User License
    • Right License
    • Access Right
    • Access Right Type
    • Access Right to OBS
    • Granted Through Type
    • Granted Through (Security Group)
    • Access Right Description
    Filters Include:
    • Resource OBS
    • Resource
    • Resource Manager
    • Primary Role
    • Employment Type
Go to Top