RegoXchange
  • A presentation slide deck from Rego University 2022.   This document reviews the best practices for Financial Management in Clarity.
    • Involve the Finance Team
      • Finance will drive financial classifications, resource rates, and capitalization rules
    • Keep Things as Simple as Possible
      • Streamline financial classifications in both the Estimation and Actuals processes
    • Clarity is Not the Company’s Financial System of Record – it is a Project and Portfolio Management System
      • Clarity may never match general ledger or project accounting module 100%
    • Spend Time on the Full Architecture – Current and Future State
    • Start With Required Outputs and Work Backward
    • Integrate to Avoid Duplicate Entry
  • Bar Chart displays average percent variance for all active projects by OBS unit.  Percent variance = Planned Cost - Budgeted Cost / Budgeted Cost * 100.  Projects with no Budgeted Cost are ignored for the calculation.  Then all project variance percentages are algebraically added (some may be negative), and divided by total projects with a variance.  This yields the Average Percent Variance.  This calculation is performed for active projects in each OBS unit.  OBS units include all units at all levels where projects are attached.  Portlet filterable by OBS, Financial Status, and Financially Approved.  Vertical axis = OBS Unit Name.  Horizontal axis = Variance Percent.  Data value = Average Percent Variance.  Mouseover value = OBS Name + Average Variance Percent.
  • Bar Chart displays average percent variance for all active projects by OBS unit.  Percent variance = Planned Cost - Budgeted Cost / Budgeted Cost * 100.  Projects with no Budgeted Cost are ignored for the calculation.  Then all project variance percentages are algebraically added (some may be negative), and divided by total projects with a variance.  This yields the Average Percent Variance.  This calculation is performed for active projects in each OBS unit.  OBS units include all units at all levels where projects are attached.  Portlet filterable by OBS, Financial Status, and Financially Approved.  Vertical axis = OBS Unit Name.  Horizontal axis = Variance Percent.  Data value = Average Percent Variance.  Mouseover value = OBS Name + Average Variance Percent.
  • Bar Chart displays average percent variance for all active projects by OBS unit.  Percent variance = Planned Cost - Budgeted Cost / Budgeted Cost * 100.  Projects with no Budgeted Cost are ignored for the calculation.  Then all project variance percentages are algebraically added (some may be negative), and divided by total projects with a variance.  This yields the Average Percent Variance.  This calculation is performed for active projects in each OBS unit.  OBS units include all units at all levels where projects are attached.  Portlet filterable by OBS, Financial Status, and Financially Approved.  Vertical axis = OBS Unit Name.  Horizontal axis = Variance Percent.  Data value = Average Percent Variance.  Mouseover value = OBS Name + Average Variance Percent.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the creation of Budget Plans in Clarity’s Modern User Experience.  The document reviews submission of a cost plan for approval, approving or rejecting submitted budgets and Budget Plan facts.
  • This portlet shows the variance between the budgeted cost and the planned cost for projects. This allows for the variance to be displayed between what was planned and what was approved. This provides the PMs with the ability to better plan the costs.
  • This portlet shows the variance between the budgeted cost and the planned cost for projects. This allows for the variance to be displayed between what was planned and what was approved. This provides the PMs with the ability to better plan the costs.
  • This portlet shows the variance between the budgeted cost and the planned cost for projects. This allows for the variance to be displayed between what was planned and what was approved. This provides the PMs with the ability to better plan the costs.
  • A presentation slide deck from Rego University 2022.   This course reviewed the value of a strategic roadmap for TBM.
    • Defining the Value of a Strategic Roadmap
    • Roadmapping Methodology
    • Best Practices
    • TBM Roadmap Examples
  • Are you considering the use of CA PPM's benefits tracking for planned and/or realized benefits?  This session will be a review of common use cases for putting benefits forecasts and realized benefits into CA PPM along with the reporting available out of the box and within RegoXchange.
  • Uncover the advantages of shifting from showback to chargeback and learn how to successfully execute chargeback within your organization. In this session, we will delve into chargeback processes, focusing on industry best practices and offering expert guidance on designing and implementing effective chargeback strategies. Additionally, we will explore the utilization of the Bill of IT as a powerful tool to reinforce your chargeback approach.
  • A presentation slide deck from Rego University 2022.   This class reviewed the importance of an application health check, optimization and tuning.
    • Checking Apptio Version
    • Tools Overview
    • Configuration Tips
  • Are you struggling with implementing Agile tools in your organization in addition to Clarity? This class will review best practices for implementing agile tools in conjunction with Clarity - living in a Bi-Modal world. We will discuss how Clarity can be used to govern both types of work and teams and how Agile tools should interface into Clarity.
  • Are you struggling with implementing Agile tools in your organization in addition to Clarity? This class will review best practices for implementing Agile tools in conjunction with Clarity - living in a Bi-Modal world. We will discuss how Clarity can be used to govern both types of work and teams and how Agile tools should interface into Clarity.
  • 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.
  • In this session we will explore complex cloud use cases you can manage within ApptioOne, including accruals, forecasting, multi-cloud chargeback, RI waste analysis, and reallocations. Additionally, we will discuss Cloud Business Management reporting and its role in driving accountability, optimizing cloud spend, and creating custom reports for various roles. Join us to learn how ApptioOne can empower you to navigate today's multi-cloud environments and enhance your cloud management strategy.
  • It is quite common for Rally and Jira to coexist. However, connecting them effectively enhances the value stream for development teams and product owners. Learn what is available to make this happen along with some typical design patterns.
  • This asset in used to update investment level TSV attributes using Cost Plan, Budget plan, Actual transaction, Planned and Budgeted Benefit Cost data as needed. It uses mappings/logic from ‘Cost Rollup Mappings’ object. Compatibility – Its compatible from 16.0 onwards with Oracle, PostgreSQL and MSSQL.
  • 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.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the creation of Cost Plans in Clarity’s Modern User Experience.  The document reviews navigation to the Financial Module, the Cost Plan sub-page and creating the plan.
  • 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.
  • 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.
  • 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.
  • A Quick Reference Guide to assist in the creation of Benefit Plans in Clarity’s Classic UX.  Reviews the process to access and create the benefit plan, entering benefit details lines, and associating a benefit plan to a cost plan.
Go to Top