RegoXchange
  • This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object.  The solution is comprised of:
    • Sub-Object (Benefit Plan Details, Parent = Project)
    • Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
    • Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
    The Process to create the Benefit Plan is initiated when users check the Create Benefit Plan box on the sub-object.  Every time the Process runs it aggregates all rows from the sub-object that are flagged as Financial and creates a new Benefit Plan.  The resulting BP is not linked to any Cost Plans. Users who install this base solution will want to consider:
    • Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
    • Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
    • Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
    • Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
    Once installed, please refer to the Benefit Detail Functionality Document for how to create Benefit Detail records, initiate the process, and the Benefit Plan Creation.
  • This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object.  The solution is comprised of:
    • Sub-Object (Benefit Plan Details, Parent = Project)
    • Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
    • Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
    The Process to create the Benefit Plan is initiated when users check the Create Benefit Plan box on the sub-object.  Every time the Process runs it aggregates all rows from the sub-object that are flagged as Financial and creates a new Benefit Plan.  The resulting BP is not linked to any Cost Plans. Users who install this base solution will want to consider:
    • Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
    • Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
    • Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
    • Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
    Once installed, please refer to the Benefit Detail Functionality Document for how to create Benefit Detail records, initiate the process, and the Benefit Plan Creation.
  • Allocation Compliance Column Chart provides the resource manager a single place to view the Allocation compliance information in the form of a stacked column chart. Allocation Compliance is calculated based on the value of 'Availability to Allocation Hours %'. Allocation Compliance is 'Under Allocated (Less Than 80%)' WHEN 'Availability to Allocation Hours %’ is less than 80. Allocation Compliance is 'Appropriately Allocated (Between 80-120%)' WHEN 'Availability to Allocation Hours %' is between 80 and 120. Allocation Compliance is 'Over Allocated (Over 120%)' WHEN 'Availability to Allocation Hours %' is greater than  120. User can further narrow their search by Resource Is Active?, OBS Type & Path, Associated Project OBS?, Allocation Start Date, Investment Name and Resource Manager. User can use exact dates or relative dates for Allocation Start Date filter parameter.
  • The portlet displays posted time by project for the logged in user based on time period and date range.  This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to.  The actuals are displayed per month in the form of TSVs.
  • The portlet displays posted time by project for the logged in user based on time period and date range.  This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to.  The actuals are displayed per month in the form of TSVs.
  • The portlet displays posted time by project for the logged in user based on time period and date range.  This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to.  The actuals are displayed per month in the form of TSVs.
  • The CA Clarity Hidden Page Security Locks document provides an overview of how to view and remove the locks currently being held on the system using the Security Locks hidden page.
  • The CA Clarity Hidden Page Flush Caches document provides an overview of how to clear the cache on an application server without exiting the CA Clarity Application itself utilizing a hidden page within the system.
  • The primary purpose of roles is to determine the amount of resource requests based on unapproved (uncommitted) and approved (committed) projects. Roles are non-named resources which are later allocated to named resources within CA PPM. Using roles is the best way to do "What If" scenario planning and determine needed capacity.  This document assists in making Best Practice decisions around setting up roles in Clarity.
  • Make sure project deliverables are completed on time by tracking work progress and monitoring task assignments.  Report Views include:
    • Work Details
    • Work Overview
    • Work Risk Issue and Change
    The main .rpt file will access data through the Data Warehouse.  For clients on Rego’s AWS hosting, we have versions that work with Oracle and Postgres DB and access the live database, if the Rego Odata connector is being used.
  • Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams.  Report Views include:
    • Allocation Discrepancies
    • Resource Detail
    • Resource Skills
    • Resource Summary
    • Resource Tasks
    • Staffing Allocations
    • Staffing ETC
    Demo Video -  https://www.youtube.com/watch?v=0Rzwl1-jbck&list=PLXJ5ktuWV0jiS9CvBpHvBIwpKPmA9uvwK&index=6 The main .rpt file will access data through the Data Warehouse.  For clients on Rego’s AWS hosting, we have versions that work with Oracle and Postgres DB and access the live database, if the Rego Odata connector is being used.
  • Gain an overview of program-level performance, track program milestones, and assess overall program health.  Report Views include:
    • Change Requests
    • Program Costs Trend
    • Program Costs
    • Program Drill Thru
    • Program Effort
    • Program Gantt
    • Program Issues
    • Program Milestones
    • Program Risks
    • Program Staff
    • Program Status Reports
    • Program Summary
    • Program Tasks
    Demo Video -  https://www.youtube.com/watch?v=6VceDIFjp-g&list=PLXJ5ktuWV0jiS9CvBpHvBIwpKPmA9uvwK&index=5 The main .rpt file will access data through the Data Warehouse.  For clients on Rego’s AWS hosting, we have versions that work with Oracle and Postgres DB and access the live database, if the Rego Odata connector is being used.
Go to Top