274 results
-
Many times Roles are spread out geographically or by function and these Roles will have different rates. For example, a developer in India may charge $25/hour vs a Developer in US may charge $50/hour. When the project team has a requirement of several developers, the PM will have to add a region specific role (Developer-US, Developer-India) so that the right rates can be applied when a cost plan is created. This creates a challenge in terms of Resource Management. As the Demand and Capacity can be spread between different region specific roles. Proper configuration on the Rate Matrix can allow you to have one Role name but different rates based on Location or Department. This allows greater flexibility and takes away the redundancy of Role Names. You can do so with the Project Team Member Properties.
-
Actuals & ETC by Resource Assignment report provides project managers a single place to view Actuals and ETC associated with resources across multiple Tasks and Projects. It displays the following: Actual and ETC Hours by Start Date: Stacked Column chart that displays the total Actual hours and ETC hours per month of fiscal period. Grey color indicates Actuals and Purple indicates ETC hours during that month. Grid: Displays Investment name, Task, Assigned resource ETC and Actual hours per month of fiscal period. It also displays aggregated column and row totals for Actuals and ETC hours. You can further narrow your search by OBS Type, OBS Path & Start Date range.
-
Benefits by year report provide the project manager a single place to view Benefit plan (Forecast /Budgeted) and its associated benefit for various years across multiple projects. Information is displayed in a bar graph and user can further drill down the details to investment level. Project Managers can use this report to analyze if the projects are giving intended benefits and take appropriate decisions accordingly. User can further narrow their search by OBS Type & Path, Plan Type (Budget/Forecast), Year and Is Plan of Record?.
-
Project Budget vs Planned vs Actual by Month report provides the Project Managers a single place to view Project Budget, Planned and Actual Cost for multiple projects. This report displays Project Budget vs Planned vs Actual by Month in the form of clustered bar chart over a period of time. User can further drill down the information to investment level by selecting a particular bar within the chart. User can further narrow their search by OBS Type & Path, Project(s), Project Manager, Month Start and End Date.
-
Project Cost within Budget report displays count of projects that are within or exceeding budget in the form of a bar chart. It also displays Total budget cost and Planned cost. User can further drill down the details to investment level. You can further narrow your search by OBS Type & Path and Investment Manager.
-
Benefits by year report provides the project manager a single place to view Benefit plan and its associated benefit for various years across multiple projects. Project Managers can use this report to analyze if the projects are giving intended benefits and take appropriate decisions accordingly. User can further narrow their search by OBS Type & Path, Investment Name, Investment Manager, Investment Type, Plan Type and Is Plan of Record?.
-
Course description: “How does my financial forecast and budget (project/program/portfolio) relate to the department/cost center budgets that finance prepares? Is there a better way to link the two together? This is a topic many organizations struggle with, and this session will review tools and processes that can help solve this problem.”
-
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.
-
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.
-
Does project and idea estimation take too long and lack visibility? This class will address one of the most common pain points within organizations: how to involve the right people within a timely project estimate. Learn some Rego best practices for defining, calculating, and modifying idea and project estimates, so you can increase throughput and ROI.