A presentation slide deck from Rego University 2022. This document reviews the best practices for Financial Management in Clarity.
|
274 results
-
-
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.
-
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.
-
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.
-
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.
-
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.
-
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) - 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) - 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) - 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.