RegoXchange
  • The Investment Resource Rate portlet allows a user to search for effective (or missing) rates for resources across all investment types.  It pulls rate information from the matrix extraction tables and includes currency conversion if the environment supports multiple currencies. The portlet can be used both to search for the rate of any given resource and to determine which resources might be missing rates when an error is generated when attempting to populate a cost plan (REVMGR-20728:Rates and Costs are both missing for one or more roles/resources).  
  • Rally Software introduction including high level feature and functionality for Agile and portfolio planning and tracking, analytics and reporting, and overall benefits of Rally in the marketplace along with a product demo.
  • Learn about the various techniques and emerging methods companies are taking to capitalize Agile work. You'll learn how some companies are moving away from timesheets and using models based on story points and team rates to generate capitalization reporting.
  • Annual planning shouldn’t be an Excel nightmare—or disconnected from strategy. In this session, see how one organization used Strategic Portfolio Management (SPM) with Clarity to transform their budgeting process from reactive to strategic.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the entering of financial transactions in Clarity’s Classic User Experience.  This doc references version 16.1.2 views. Document provides basic information on the definition of a transaction and the composition of transaction items. Detail is provided on how to create a new transaction from the Transaction Entry page of the Classic User Experience. Information is provided on how to enter detail into each individual line item for a transaction.
  • A presentation slide deck from RegoU 2023.  This course was a presentation by Apptio on their Product Roadmap.
  • 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.
  • Part of the Business Transformation Collection, this bubble-chart portlet displays investments per their alignment, status and total planned benefit. The: X-axis displays the alignment Y-axis displays the status Bubble-size displays the total planned benefit
  • This stacked bar graph portlet displays the financial summary by transaction class for the current and future fiscal annual periods.  Filters are provided for:
    1. OBS
    2. Portfolio
  • This training document is a Rego Consulting Quick Reference Guide to assist with Financial Actuals and Reporting in Clarity’s Modern User Experience.  This doc references version 16.0.2 views. Document includes detail on which jobs should be run to ensure project and financial data is synchronized with the latest posted actuals. Information is provided on how to analyze cost plans and how to review actual transactions. Instructions are provided on how to analyze budget plans.
  • 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.
Go to Top