RegoXchange
  • Bar Chart displays average percent variance for all active projects by OBS unit.  Percent variance = Planned Cost - Budgeted Cost / Budgeted Cost * 100.  Projects with no Budgeted Cost are ignored for the calculation.  Then all project variance percentages are algebraically added (some may be negative), and divided by total projects with a variance.  This yields the Average Percent Variance.  This calculation is performed for active projects in each OBS unit.  OBS units include all units at all levels where projects are attached.  Portlet filterable by OBS, Financial Status, and Financially Approved.  Vertical axis = OBS Unit Name.  Horizontal axis = Variance Percent.  Data value = Average Percent Variance.  Mouseover value = OBS Name + Average Variance Percent.
  • This portlet displays the monthly allocation per resource. The PM can view by the RM or the resource to get the data for monthly resource allocations. The table below describes the available filter fields in the portlet.
    Column Label Description
    Work Effort Manager Manager of the Investment the Work Effort is on
    Work Effort Active Active status of the Investment the Work Effort is on
    Resource Resource’s Name
    Internal Resource ID Resource’s ID
    Zero Allocation Show Allocations that equal zero
    Open for Time Entry Is the Resource Open for Time Entry
    Resource Active Resource’s Active status
    Role Resource’s Primary Role
    OBS Unit Resource’s OBS
    Start Allocation Start Time to filter by
    End Allocation Finish time to filter by
       
  • Learn about the various techniques and emerging methods companies are taking to capitalize Agile work. You'll learn how some companies are moving away from timesheets and using models based on story points and team rates to generate capitalization reporting.
  • Course Description:   Are your project teams using SharePoint effectively and getting the most value out of it? Is document management a daily struggle? Learn how to use SharePoint with Clarity PPM to seamlessly improve collaboration and team productivity.
  • Course Description:  Does your company have Office 365, but you’re not sure what it can do for you? This session will cover what Office 365 is, including insights into how Office 365 can help your teams work faster and smarter.
  • Course Description:   How do companies track stage gates within Clarity PPM? This session will review some best practices for tracking, monitoring, and approving stage gates within Clarity PPM. We will also discuss pros and cons of various options to help you select the best method for your company.
  • The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
  • The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field.  This process can be modified to grant project edit rights to any user within a project field.
  • The PM Stalker – Submit Status Report workflow process will email any project manager that has not submitted a status report in the last two weeks. This process will ensure that all status reports are kept up-to-date and provide management with a reliable overview of the status on the project.
  • The Status Report Publish workflow process pushes values from the status report sub-object to the parent project object. The process is started when the user ticks the “Publish” Boolean field on the status report (custom field added). This workflow will update the project object with the overall status indicator, the status comment, the previous overall status, and the as of date. This eliminates the project manager having to update the fields in both the status report and the project overall.
  • The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) AND project manager (PM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM or PM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated.  This process is needed if a resource or set of resources were added to projects without having their primary role filled in.
Go to Top