-
The Capacity vs. Booking Status by OBS report includes three charts. The line chart displays capacity compared to demand, with demand distributed by booking status, and actuals by period. The pie charts display demand by booking status and demand by employment type. The report also includes a detail listing of resource capacity and demand at the booking status level 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. Report Prerequisites Verify that you have completed the following prerequisites before you run this report: • Resource capacity amounts display if the resource has availability that is defined and meets the parameter criteria. • Resource demand allocation amounts display if the resource is allocated to at least one investment. Resource assignments are not required. • The Load Data Warehouse job must be run before you run this report. If the Data Warehouse is not populated, the report will not display any data. Also, most of the report parameters do not display options. -
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. Report Prerequisites: Verify that you have completed the following prerequisites before you run this report: • The Load Data Warehouse job must be run before you run this report. If the Data Warehouse is not populated, the report will not display any data. Also, most of the report parameters do not display options. • Resource demand allocation amounts display if the resource is allocated to at least one investment and the report display type of hours as allocations. Resource demand assignment amounts display if the resource is assigned to at least one task on the investment and the report displays type of hours as assignments. -
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 presentation slide deck from Rego University 2022. Presentations by Erie Insurance, University of California, San Francisco, and The Hershey Company. -
This Portlet allows users to quickly access Documents they uploaded into Projects via the Classic UI à Collaboration tab or via the New UX Documents module. Clicking on the File Name downloads the file, clicking on the Options gear allows users to export the list to Excel. -
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.
-
This training document is a Rego Consulting Quick Reference Guide to assist with creating and management of a project team in Clarity’s Modern User Experience. The document reviews accessing teams, creating a team, allocating a team on an investment, as well as additional team related information. -
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). -
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).
-
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).
-
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority. -
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority.
-
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority. -
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority.
-
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority.
-
The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date). -
The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date).
-
The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date).
Copyright 2023 • Rego Consulting Corporation • Privacy Policy