-
The Capacity vs Allocation by OBS report is a transaction based Jaspersoft report that does not require the Load Jaspersoft Datawarehouse job to be run. The report will pull real-time data from the transaction tables in Clarity. This report can be run from either the Advanced Reporting or Reports and Jobs area within Clarity. The Capacity vs. Allocation by OBS report displays resource capacity and demand across investments. The report can be grouped by any OBS level, providing visibility into resources at any level of the organization. The report displays amounts by week or month, and in total. The amounts can be displayed as hours or FTEs. -
The Capacity vs Demand by Resource report is a transaction based Jaspersoft report that does not require the Load Jaspersoft Datawarehouse job to be run. The report will pull real-time data from the transaction tables in Clarity. This report can be run from either the Advanced Reporting or Reports and Jobs area within Clarity. The Capacity vs. Demand by Resource report displays resource capacity and demand at the resource level across investments. The report gives you visibility into the capacity, demand, and remaining capacity by resource. The report displays amounts by week or month, and in total. The amounts might be displayed as hours or FTEs. -
The Capacity vs. Demand by Role report provides visibility into resource utilization by comparing available capacity to actual demand across investments at the role level. It highlights capacity, demand, and remaining capacity, helping identify potential surpluses or shortfalls. Data can be viewed by week or month and displayed in either hours or full-time equivalents (FTEs) to support detailed workforce planning and analysis. -
No matter how hard we try, many organizations cannot pry Excel out of the hands of project and resource managers. In this class we will explore possibilities that give up the battle and embrace Excel as a great data entry tool. We will show some neat case studies on quick Excel integrations deployed at customers. -
No matter how hard we try, many organizations cannot pry Excel out of the hands of project and resource managers. In this class we will explore possibilities that give up the battle and embrace Excel as a great data entry tool. We will show some neat case studies on quick Excel integrations deployed at customers. -
A process creating a new Cost Plan. Cost Plan properties:
Pre-conditions: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:
Pre-conditions: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:
Pre-conditions: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.
-
The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active. The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).

