-
Capture and present allocation data by Team for the Investments included in your Roadmap to enable the ability to compare to Targets or Limits. Allocation data can be presented in Hours or FTE, for Teams Only. -
This training document is a Rego Consulting Quick Reference Guide to assist with utilization of the Staffing page in Clarity’s Modern User Experience. This doc references version 16.2.1 views. Document provides detail on the layout and capabilities of the Staff Grid as well as the Allocations Timeline. Information is provided on columns, widgets and filtering. Instructions are provided on how to save Views. Summary information is provided on the layout of the Allocation Timeline and includes detail on the Investment Timeline and the Resource Histogram. Investment Timeline summary contains information on the Allocations by Investments and the Allocations by Resources tabs. While the Resource Histogram section provides screenshots on Resource Availability and Resources by Role. -
This training document is a Rego Consulting Quick Reference Guide to assist with Allocations Timeline in Clarity’s Modern User Experience. This doc reviews the Investment Timeline and the Resource Histogram sections of the Allocations Timeline.
-
Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams. Report Views include: • Over Allocation • By Project • By People • Project Resource Details • No Allocations by Project • No Allocations by People The main .rpt file will access data through the Data Warehouse. -
Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams. Report Views include: • Allocation Discrepancies • Resource Detail • Resource Skills • Resource Summary • Resource Tasks • Staffing Allocations • Staffing ETC Demo Video - https://www.youtube.com/watch?v=0Rzwl1-jbck&list=PLXJ5ktuWV0jiS9CvBpHvBIwpKPmA9uvwK&index=6 -
Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams. Report Views include: • Over Allocation • By Project • By People • Project Resource Details • No Allocations by Project • No Allocations by People The main file will access data through custom queries created via Rego Odata connector. -
This training document is a Rego Consulting Quick Reference Guide to assist with Allocations Timeline in Clarity’s Modern User Experience. This doc reviews the Investment Timeline and the Resource Histogram sections of the Allocations Timeline. -
Allocation Compliance Column Chart provides the resource manager a single place to view the Allocation compliance information in the form of a stacked column chart. Allocation Compliance is calculated based on the value of 'Availability to Allocation Hours %'. Allocation Compliance is 'Under Allocated (Less Than 80%)' WHEN 'Availability to Allocation Hours %’ is less than 80. Allocation Compliance is 'Appropriately Allocated (Between 80-120%)' WHEN 'Availability to Allocation Hours %' is between 80 and 120. Allocation Compliance is 'Over Allocated (Over 120%)' WHEN 'Availability to Allocation Hours %' is greater than 120. User can further narrow their search by Resource Is Active?, OBS Type & Path, Associated Project OBS?, Allocation Start Date, Investment Name and Resource Manager. User can use exact dates or relative dates for Allocation Start Date filter parameter. -
The portlet displays posted time by project for the logged in user based on time period and date range. This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to. The actuals are displayed per month in the form of TSVs. -
The portlet displays posted time by project for the logged in user based on time period and date range. This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to. The actuals are displayed per month in the form of TSVs.
-
The portlet displays posted time by project for the logged in user based on time period and date range. This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to. The actuals are displayed per month in the form of TSVs.
-
The Over/Under Allocation 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 Over/Under Allocation by Resource report displays resource remaining capacity amounts by resource. The report displays amounts by week or month, and in total. The amounts can be displayed as hours or FTEs. -
The idea allocation uploader allows you to import in allocations from an external Excel spreadsheet. Populate an Excel template with required fields then import them directly from the Clarity UI. Once imported you’ll see the allocations right on the Team tab of the Idea. -
The Allocation Compliance Pie Chart portlet gives a view of active resources' allocation compliance within a date range and OBS displayed in a pie chart. It allows the user to the percentage of resources over, under, and adequately staffed on projects over a selected time period. This portlet leverages the daily allocation and daily availability slices as well as only active investments. The portlet provides filters for specific dates (required) and OBS. -
Allocation Compliance Pie Chart report provides resource managers a single place to view Allocation compliance for various resources. It displays the following: Allocated Hours by OBS chart: Pie chart that displays percentage of resources that are fully allocated (80 -120 %) and under allocated (less than 80%) for a particular OBS and selected period range. Grid: Displays Resource Name, Resource Id, Primary Role, Booking Manager, Period, Allocated hours and Actual hours during that period. You can further narrow your search by OBS Type, OBS Path & Period Date range. -
Allocation Compliance Column Chart report provides resource managers a single place to view Allocation compliance for various resources. It displays the following: Allocated Hours by OBS chart: Stacked Column chart that displays percentage of resources that are fully allocated (80 -120 %) and under allocated (less than 80%) for a particular OBS and selected period range. Grid: Displays Resource Name, Resource Id, Primary Role, Booking Manager, Period, Allocated hours and Actual hours during that period. You can further narrow your search by OBS Type, OBS Path & Period Start Date range. -
Allocation Compliance by RM report provides resource managers a single place to view Available hours, Allocation Hours and Allocation Percentage of Resources. It considers the resources of selected resource manager and it displays the following: Allocation Details Grid: Displays Resource and its Allocated hours, Available hours and Allocation percentage (Allocated hours/Available Hours) Allocation Percent by Resource: Bar chart that displays Allocation Percentage (top 10) for various resources during the selected Time frame. You can further narrow your search by Resource Manager & Month Start Date range. -
Allocation Compliance by PM report provides project managers a single place to view Available hours, Allocation Hours and Allocation Percentage of Investment Team Resources. It considers the investments of selected project manager and it displays the following: Allocation Details Grid: Displays Resource and its Allocated hours, Available hours and Allocation percentage (Allocated hours/Available Hours) Allocation Percent by Resource: Column chart that displays Allocation Percentage for various resources during the selected Time frame. You can further narrow your search by Project Manager & Month Start Date range. -
Allocation Compliance Area Chart provides the resource manager a single place to view the Monthly Resource Allocation compliance for all resources in the form of an Area chart. Allocation Compliance is calculated based on the value of 'Availability to Allocation Hours %' Allocation Compliance is 'Under Allocated (Less Than 80%)' WHEN 'Availability to Allocation Hours %’ is less than 80 Allocation Compliance is 'Appropriately Allocated (Between 80-120%)' WHEN 'Availability to Allocation Hours %' is between 80 and 120 Allocation Compliance is 'Over Allocated (Over 120%)' WHEN 'Availability to Allocation Hours %' is greater than 120 User can further narrow their search by Resource Is Active?, OBS Type, OBS Path and Month Start Date. User can use exact dates or relative dates for Month Start Date filter parameter. -
Resource Availability – 4 Weeks displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks. This report also displays Resource Primary Role and Employment Type. User can further narrow their search by Resource Name, Resource Type & Week Start Date. User can use exact dates or relative dates for Week Start Date filter parameters. -
Allocation Compliance for PM report gives a view of resource Allocation percentage for active resources on the team of an investment for a selected Investment Manager. It allows the PM to see resources on their project over the coming months and whether they are over or under allocated. Allocation Percentage is calculated as (‘Allocated Hours’ / ‘Available Hours’) * 100. User can further narrow their search Month Start Date and Investment Manager. User can use exact dates or relative dates for Month Start Date filter parameter. -
Allocation Compliance Pie Chart provides the resource manager a single place to view the Allocation compliance information in the form of a Pie chart. Allocation Compliance is calculated based on the value of 'Availability to Allocation Hours %'. Allocation Compliance is 'Under Allocated (Less Than 80%)' WHEN 'Availability to Allocation Hours %’ is less than 80. Allocation Compliance is 'Appropriately Allocated (Between 80-120%)' WHEN 'Availability to Allocation Hours %' is between 80 and 120. Allocation Compliance is 'Over Allocated (Over 120%)' WHEN 'Availability to Allocation Hours %' is greater than 120. User can further narrow their search by Resource Is Active?, OBS Type, OBS Path, Allocation Start Date, Investment Name and Resource Manager. User can use exact dates or relative dates for Allocation Start Date filter parameter. -
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 interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.- Configuration
- A master object called Allocation Upload Files will be created. The object will contain a required attachment field on the create page that will receive the Project Allocation Upload MS Excel file.
- A new sub-object called Allocation Upload Records will be created. This object will contain the fields necessary to receive the data rows from the Project Allocation Upload template.
- The master object will store the file level data while the sub-object will store the rows that belong to the file.
- Users must be granted security to view and edit the master and sub-objects in order to run the upload process.
- Project Allocation Upload Template
- The Project Allocation Upload template must remain static. Any changes other than creating additional time periods or additional rows will cause the process to error.
- Only the Project Allocation Upload template can be used to load records to the new objects.
- The Project Allocation Upload will only accept months across the x-axis in the format DD/MM/YYYY. The month headers must appear in the first row of the template and contain the first day of the month.
- The template must be distributed to the users that will be using the upload functionality.
- Users will be required to enter an Investment ID and Resource ID so the process can correctly identify investments and resources to upload the allocation hours against.
- A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.
- The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.
- Investments will not be created through the interface. As such a valid Investment ID must be provided.
- Resources can be added to the investment team through the interface. If a valid Resource ID is provided the resource’s allocation will be updated if the resource already exists on the investment. If the resource does not already exist on the investment the resource will be added to the team along with the allocation hours.
- The Project Allocation Upload template will accept hours, not allocation percentages. Because CA PPM stores allocations as percentages of a resource’s availability the upload process must convert hours to a percentage. As a result small rounding errors may occur in the neighborhood of .01 hours per month.
- Resources cannot be removed from investment teams through the interface.
- The Project Allocation Upload template will support allocation uploads to different instances of the same role on the same investment as long as different Staff OBS units are provided.
- If multiple instances of the same role are assigned to the investment with the same Staff OBS the process will not know which instance of the role to upload the hours to. In these cases the process will consider these records as invalid. The PM will need to manually remove one of the instances or upload the hours manually..
- If multiple instances of the same role with the same Staff OBS unit are assigned to the same investment in the upload template the monthly hours will be totaled by investment, by role, by Staff OBS.
- The allocation template will follow the format in the screenshot area.
- Process
- To initiate the Allocation Interface a user will create a new Allocation Upload File instance, attach the Project Allocation Upload Template, and save the record. The file attachment field is an “enter-once” field, meaning that once a value has been set it cannot be changed. If a user wishes to upload another field they will create a new record.
- After the file has been attached the user will be presented with two check box fields, one to Validate and one to Validate and Upload. Checking either or both options will initiate the process.
- The process will first determine if any sub-object instances exist for the file. In other words, do any records already exist in the Allocation Upload Records sub-object pertaining to the newly uploaded file. If there are no records in the sub-object the process will use the uploaded file and read its contents into the sub-object. If errors are encountered during the file read they will be written to the process console, the process will throw an error, and end.
- Next, records will be validated. Only the sub-object instances that belong to the master object will be validated. Records belonging to other master object instances will not be validated or processed. All records in a status of Ready for Processing, Failed Validation, or Xog Load Error will be validated. Records will fail validation if an investment is not found corresponding to the investment ID provided, a resource is not found corresponding to the resource ID provided, or the date provided is not valid, or a provided Staff OBS does not yield a match. Records that fail validation will be flagged as invalid along with a description as to why they failed validation. Records that pass validation will be flagged as Ready for Processing and locked. The sub-object instances can be exported to excel if further analysis is required. If the Validate & Upload option was not selected the process will end here.
- Regarding the Staff OBS. Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.
- The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.
- If the Staff OBS value matches against multiple nodes in the Staff OBS the record will be flagged as invalid as the process will not know which node to use.
- If the Validate & Upload option was selected the process will continue and any valid records will be xog’ed into the investment team. The xog will be executed as the user that initiated the process so any security rules enforced by xog will be respected by the process.
- Successful records will be flagged as Processed Successfully in the sub-object and remain locked. Records that did not load successfully, due to a xog error or security limitation will be flagged as Xog Load Error, unlocked, and updated with a description containing the full xog output.
- Records that failed validation or failed the xog load can be manually edited and revalidated, and attempt to be uploaded again. Subsequent runs of the process will not read in data from the file, but rather process only sub-object instances that currently exist.
- Configuration
-
The interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.
- Configuration
- A master object called Allocation Upload Files will be created. The object will contain a required attachment field on the create page that will receive the Project Allocation Upload MS Excel file.
- A new sub-object called Allocation Upload Records will be created. This object will contain the fields necessary to receive the data rows from the Project Allocation Upload template.
- The master object will store the file level data while the sub-object will store the rows that belong to the file.
- Users must be granted security to view and edit the master and sub-objects in order to run the upload process.
- Project Allocation Upload Template
- The Project Allocation Upload template must remain static. Any changes other than creating additional time periods or additional rows will cause the process to error.
- Only the Project Allocation Upload template can be used to load records to the new objects.
- The Project Allocation Upload will only accept months across the x-axis in the format DD/MM/YYYY. The month headers must appear in the first row of the template and contain the first day of the month.
- The template must be distributed to the users that will be using the upload functionality.
- Users will be required to enter an Investment ID and Resource ID so the process can correctly identify investments and resources to upload the allocation hours against.
- A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.
- The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.
- Investments will not be created through the interface. As such a valid Investment ID must be provided.
- Resources can be added to the investment team through the interface. If a valid Resource ID is provided the resource’s allocation will be updated if the resource already exists on the investment. If the resource does not already exist on the investment the resource will be added to the team along with the allocation hours.
- The Project Allocation Upload template will accept hours, not allocation percentages. Because CA PPM stores allocations as percentages of a resource’s availability the upload process must convert hours to a percentage. As a result small rounding errors may occur in the neighborhood of .01 hours per month.
- Resources cannot be removed from investment teams through the interface.
- The Project Allocation Upload template will support allocation uploads to different instances of the same role on the same investment as long as different Staff OBS units are provided.
- If multiple instances of the same role are assigned to the investment with the same Staff OBS the process will not know which instance of the role to upload the hours to. In these cases the process will consider these records as invalid. The PM will need to manually remove one of the instances or upload the hours manually..
- If multiple instances of the same role with the same Staff OBS unit are assigned to the same investment in the upload template the monthly hours will be totaled by investment, by role, by Staff OBS.
- The allocation template will follow the format in the screenshot area.
- Process
- To initiate the Allocation Interface a user will create a new Allocation Upload File instance, attach the Project Allocation Upload Template, and save the record. The file attachment field is an “enter-once” field, meaning that once a value has been set it cannot be changed. If a user wishes to upload another field they will create a new record.
- After the file has been attached the user will be presented with two check box fields, one to Validate and one to Validate and Upload. Checking either or both options will initiate the process.
- The process will first determine if any sub-object instances exist for the file. In other words, do any records already exist in the Allocation Upload Records sub-object pertaining to the newly uploaded file. If there are no records in the sub-object the process will use the uploaded file and read its contents into the sub-object. If errors are encountered during the file read they will be written to the process console, the process will throw an error, and end.
- Next, records will be validated. Only the sub-object instances that belong to the master object will be validated. Records belonging to other master object instances will not be validated or processed. All records in a status of Ready for Processing, Failed Validation, or Xog Load Error will be validated. Records will fail validation if an investment is not found corresponding to the investment ID provided, a resource is not found corresponding to the resource ID provided, or the date provided is not valid, or a provided Staff OBS does not yield a match. Records that fail validation will be flagged as invalid along with a description as to why they failed validation. Records that pass validation will be flagged as Ready for Processing and locked. The sub-object instances can be exported to excel if further analysis is required. If the Validate & Upload option was not selected the process will end here.
- Regarding the Staff OBS. Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.
- The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.
- If the Staff OBS value matches against multiple nodes in the Staff OBS the record will be flagged as invalid as the process will not know which node to use.
- If the Validate & Upload option was selected the process will continue and any valid records will be xog’ed into the investment team. The xog will be executed as the user that initiated the process so any security rules enforced by xog will be respected by the process.
- Successful records will be flagged as Processed Successfully in the sub-object and remain locked. Records that did not load successfully, due to a xog error or security limitation will be flagged as Xog Load Error, unlocked, and updated with a description containing the full xog output.
- Records that failed validation or failed the xog load can be manually edited and revalidated, and attempt to be uploaded again. Subsequent runs of the process will not read in data from the file, but rather process only sub-object instances that currently exist.
- Configuration
-
Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks. Email has links to each resource so that allocation modifications can be made as required. -
Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks. Email has links to each resource so that allocation modifications can be made as required.
-
Process sends an email to RM, for resources assigned, that indicates the allocation percentage for each resource for the next 6 weeks. Email has links to each resource so that allocation modifications can be made as required.
-
The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job. -
The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job.
-
The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job.
-
Based on the pre-determined schedule frequency, this job will send an email to Resource Managers that have a Resource meeting the criteria of: Average allocations are less than 100% where Resource(s) and Project(s) are active over the next two weeks. This serves as a reminder to Resource Managers to monitor and manage allocations. The contents of the email include a message indicating the Resource Manager has at least one Resource meeting this criteria and a table indicating the Resource and that resource’s average, next 90 days allocations. -
Based on the pre-determined schedule frequency, this job will send an email to Resource Managers that have a Resource meeting the criteria of: Average allocations are less than 100% where Resource(s) and Project(s) are active over the next two weeks. This serves as a reminder to Resource Managers to monitor and manage allocations. The contents of the email include a message indicating the Resource Manager has at least one Resource meeting this criteria and a table indicating the Resource and that resource’s average, next 90 days allocations.
-
Based on the pre-determined schedule frequency, this job will send an email to Resource Managers that have a Resource meeting the criteria of: Average allocations are less than 100% where Resource(s) and Project(s) are active over the next two weeks. This serves as a reminder to Resource Managers to monitor and manage allocations. The contents of the email include a message indicating the Resource Manager has at least one Resource meeting this criteria and a table indicating the Resource and that resource’s average, next 90 days allocations.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy