RegoXchange
RegoXchange
  •

    Capacity Graph – Investment – Postgres

    $0.00
    The Capacity Graph - Investment portlet displays Availability, Allocations, Assignments and Actuals for active resources in a single project. This portlet pulls from timeslices and allows the user to filter on weekly, monthly, or quarterly data. This portlet provides a Project Manager with a simple way to analyse:  Allocations vs. Actuals and Allocations vs. ETC.  Depending on metric goals, the graph allows the user to determine where areas of improvement may exist.
    Details

  • Capacity Graph – Investment – SQL

    $0.00
    The Capacity Graph - Investment portlet displays Availability, Allocations, Assignments and Actuals for active resources in a single project. This portlet pulls from timeslices and allows the user to filter on weekly, monthly, or quarterly data. This portlet provides a Project Manager with a simple way to analyse:  Allocations vs. Actuals and Allocations vs. ETC.  Depending on metric goals, the graph allows the user to determine where areas of improvement may exist.
    Details

  • Capacity Graph – Oracle

    $0.00
    The Capacity Graph portlet displays Availability, Allocations, Actuals and Assignments for one or more active resource(s) in a single view. This portlet pulls data from timeslices, and allows the user to filter on a weekly, monthly or quarterly data.  The Estimated Time to Complete (ETC) and Allocation data will only show for projects that are active. This portlet provides Resource Managers, PMOs and Executives with a simple way to analyse:  Allocations vs. Availability, Allocations vs. Actuals, Allocations vs. ETC and ETC vs. Availability.  The graph allows the user to determine where areas of improvement may exist and quickly identify potential areas of constraint. Note: the information displayed is dependent on what the user has security rights to view.
    Details

  • Capacity Graph – Postgres

    $0.00
    The Capacity Graph portlet displays Availability, Allocations, Actuals and Assignments for one or more active resource(s) in a single view. This portlet pulls data from timeslices, and allows the user to filter on a weekly, monthly or quarterly data.  The Estimated Time to Complete (ETC) and Allocation data will only show for projects that are active. This portlet provides Resource Managers, PMOs and Executives with a simple way to analyse:  Allocations vs. Availability, Allocations vs. Actuals, Allocations vs. ETC and ETC vs. Availability.  The graph allows the user to determine where areas of improvement may exist and quickly identify potential areas of constraint. Note: the information displayed is dependent on what the user has security rights to view.
    Details

  • Capacity Graph – SQL

    $0.00
    The Capacity Graph portlet displays Availability, Allocations, Actuals and Assignments for one or more active resource(s) in a single view. This portlet pulls data from timeslices, and allows the user to filter on a weekly, monthly or quarterly data.  The Estimated Time to Complete (ETC) and Allocation data will only show for projects that are active. This portlet provides Resource Managers, PMOs and Executives with a simple way to analyse:  Allocations vs. Availability, Allocations vs. Actuals, Allocations vs. ETC and ETC vs. Availability.  The graph allows the user to determine where areas of improvement may exist and quickly identify potential areas of constraint. Note: the information displayed is dependent on what the user has security rights to view.
    Details

  • Create Forecast from Actuals and Allocations – Oracle

    $0.00
    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)
    Pre-conditions:
    • 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.
    Details

  • Create Forecast from Actuals and Allocations – Postgres

    $0.00
    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)
    Pre-conditions:
    • 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.
    Details

  • Create Forecast from Actuals and Allocations – SQL

    $0.00
    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)
    Pre-conditions:
    • 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.
    Details

  • Idea Allocations Uploader

    $0.00
    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.
    Details

  • My Allocations – Oracle

    $0.00
    The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices.  It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants.  This will display both active and inactive projects.
    Details

  • My Allocations – Postgres

    $0.00
    The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices.  It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants.  This will display both active and inactive projects.
    Details

  • My Allocations – SQL

    $0.00
    The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices.  It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants.  This will display both active and inactive projects.
    Details

  • Over/Under Allocation by Resource JS Tdb

    $0.00
    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.
    Details

  • Project Allocation Uploader – Oracle

    $0.00
    The interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.
    1. Configuration
      1. 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.
      2. 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.
      3. The master object will store the file level data while the sub-object will store the rows that belong to the file.
      4. Users must be granted security to view and edit the master and sub-objects in order to run the upload process.
    2. Project Allocation Upload Template
      1. 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.
      2. Only the Project Allocation Upload template can be used to load records to the new objects.
      3. 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.
      4. The template must be distributed to the users that will be using the upload functionality.
      5. 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.
      6. A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.
      7. The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.
      8. Investments will not be created through the interface. As such a valid Investment ID must be provided.
      9. 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.
      10. 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.
      11. Resources cannot be removed from investment teams through the interface.
      12. 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.
        1. 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..
        2. 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.
      13. The allocation template will follow the format in the screenshot area.
    3. Process
      1. 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.
      2. 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.
      3. 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.
      4. 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.
        1. Regarding the Staff OBS.  Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.
        2. The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.
        3. 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.
      5. 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.
      6. 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.
      7. 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.
    Details

  • Project Allocation Uploader – Postgres

    $0.00
    The interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.
    1. Configuration
      1. 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.
      2. 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.
      3. The master object will store the file level data while the sub-object will store the rows that belong to the file.
      4. Users must be granted security to view and edit the master and sub-objects in order to run the upload process.
    2. Project Allocation Upload Template
      1. 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.
      2. Only the Project Allocation Upload template can be used to load records to the new objects.
      3. 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.
      4. The template must be distributed to the users that will be using the upload functionality.
      5. 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.
      6. A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.
      7. The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.
      8. Investments will not be created through the interface. As such a valid Investment ID must be provided.
      9. 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.
      10. 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.
      11. Resources cannot be removed from investment teams through the interface.
      12. 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.
        1. 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..
        2. 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.
      13. The allocation template will follow the format in the screenshot area.
    3. Process
      1. 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.
      2. 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.
      3. 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.
      4. 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.
        1. Regarding the Staff OBS.  Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.
        2. The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.
        3. 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.
      5. 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.
      6. 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.
      7. 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.
    Details

  • QRG – Staffing Overview – Clarity – Modern UX 16.2.1

    $0.00
    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.
    Details

  • QRG – Staffing: Allocations Timeline – Clarity – Modern UX 16.1.2

    $0.00
    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.
    Details

  • QRG – Staffing: Allocations Timeline – Clarity – Modern UX 16.2.1

    $0.00
    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.
    Details

  • Resource Allocation by Percent – Oracle

    $0.00
    This portlet shows resource allocation by percent and hours, and gives ability to filter on allocation percent. The RM can use the portlet to see if any of the resources is over/ under allocated.
    Details

  • Resource Allocation by Percent – Postgres

    $0.00
    This portlet shows resource allocation by percent and hours, and gives ability to filter on allocation percent. The RM can use the portlet to see if any of the resources is over/ under allocated.
    Details

  • Resource Allocation by Percent – SQL

    $0.00
    This portlet shows resource allocation by percent and hours, and gives ability to filter on allocation percent. The RM can use the portlet to see if any of the resources is over/ under allocated.
    Details

  • Resource Availability – 4 Weeks – Oracle

    $0.00
    Resource Availability – 4 Weeks is a grid portlet that displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks.  If % Available is negative, this indicates an over-allocation.  Zero% Average Availability indicates fully allocated (no remaining availability). Filterable by Role, Resource, Resource Type, Full-Time/Part-Time, Availability Range.  Contractor Type is a custom attribute (Lookup - String) created on the Resource object. It is attached to the lookup, Contractor Type (Lookup ID: REGO_CONTRACTOR_TYPE) that has static values Part Time (PT) and Full Time(FT).
    Details

  • Resource Availability – 4 Weeks – Postgres

    $0.00
    Resource Availability – 4 Weeks is a grid portlet that displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks.  If % Available is negative, this indicates an over-allocation.  Zero% Average Availability indicates fully allocated (no remaining availability). Filterable by Role, Resource, Resource Type, Full-Time/Part-Time, Availability Range.  Contractor Type is a custom attribute (Lookup - String) created on the Resource object. It is attached to the lookup, Contractor Type (Lookup ID: REGO_CONTRACTOR_TYPE) that has static values Part Time (PT) and Full Time(FT).
    Details

  • Resource Availability – 4 Weeks – SQL

    $0.00
    Resource Availability – 4 Weeks is a grid portlet that displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks.  If % Available is negative, this indicates an over-allocation.  Zero% Average Availability indicates fully allocated (no remaining availability). Filterable by Role, Resource, Resource Type, Full-Time/Part-Time, Availability Range.  Contractor Type is a custom attribute (Lookup - String) created on the Resource object. It is attached to the lookup, Contractor Type (Lookup ID: REGO_CONTRACTOR_TYPE) that has static values Part Time (PT) and Full Time(FT).
    Details

  • Resource Availability – 4 weeks (JS Report)

    $0.00
    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.
    Details

  • Resource Management | OOTB Intro – RegoU 2021

    $0.00
    Do you want to understand the OOTB configuration and functionality of resource management?  In this class, we will review the OOTB objects, views, and functions of assignments, allocations, and other related areas.  We will cover both classic and new UX highlighting differences.
    Details

  • Resource Management Summary Dashboard – Power BI in Oracle AWS

    $0.00
    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  
    Details

  • Resource Over-Allocation Notification – Oracle

    $0.00
    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.
    Details

  • Resource Over-Allocation Notification – Postgres

    $0.00
    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.
    Details

  • Resource Over-Allocation Notification – SQL

    $0.00
    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.
    Details

  • Resource Team Allocation – Oracle

    $0.00
    This portlet displays the % allocation of resources to projects. The portlet shows if the resource is allocated to the projects as an individual resource or as part of an Agile team, in which case it will display the resource % allocation to the team and what that will represent in terms of % allocation to the project. The Total Allocation % display the allocation of the resource to all investments is allocated to. Remaining Capacity and Over/Under columns will help identify the resources that still have availability and the ones that are over allocated.
    Details

  • Resource Team Allocation – Postgres

    $0.00
    This portlet displays the % allocation of resources to projects. The portlet shows if the resource is allocated to the projects as an individual resource or as part of an Agile team, in which case it will display the resource % allocation to the team and what that will represent in terms of % allocation to the project. The Total Allocation % display the allocation of the resource to all investments is allocated to. Remaining Capacity and Over/Under columns will help identify the resources that still have availability and the ones that are over allocated.
    Details

  • Resource Team Allocation – SQL

    $0.00
    This portlet displays the % allocation of resources to projects. The portlet shows if the resource is allocated to the projects as an individual resource or as part of an Agile team, in which case it will display the resource % allocation to the team and what that will represent in terms of % allocation to the project. The Total Allocation % display the allocation of the resource to all investments is allocated to. Remaining Capacity and Over/Under columns will help identify the resources that still have availability and the ones that are over allocated.
    Details

  • RM Governance – Postgres

    $0.00
    The RM Governance portlet provides resource availability, allocation, and comparison of the two values at 2, 4, and 8-week intervals. Allows searching on any RM or resource OBS instead of pre-filtering for the logged in user.
    Details

  • RM Governance – SQL

    $0.00
    The RM Governance portlet provides resource availability, allocation, and comparison of the two values at 2, 4, and 8-week intervals. Allows searching on any RM or resource OBS instead of pre-filtering for the logged in user.
    Details

  • RM Stalker – Allocation over 120% – Oracle

    $0.00
    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 greater than 120% where Resource(s) and Project(s) are active over the next 90 days. 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.
    Details

Copyright 2023 •  Rego Consulting Corporation • Privacy Policy

Go to Top