RegoXchange
  • This process grants Project Management instance rights to all of the project team members within the program hierarchy.  Allows users to view management properties, roster and key tasks of the project.  This also allows user view access to the project in Microsoft Project.
  • The portlet shows the project spend to vendors by month.  The Vendor field picked on the portlet comes from the Vendor mentioned when creating the voucher (as displayed on the first screenshot).  This provides a nice view of identifying how much is spent by an organization on the vendor employees on their workforce.
  • The portlet shows the Overall Status and Budget Status and Amounts. It displays one row per project. The portlet shows the following main fields: Overall Status, Budget Status, Capital Budget, Operating Budget, Total Budget, Capital Planed, Operating Planned, Total Planned, Capital Actuals, Operating Actuals, Total Actuals, Budget Variance ($), Budget Variance (%) Displaying the budget variance allows the PM to understand of the project is over / under spent, and thus the costs planning needs to be re-visited.
  • The portlet shows the Overall Status and Budget Status and Amounts. It displays one row per project. The portlet shows the following main fields: Overall Status, Budget Status, Capital Budget, Operating Budget, Total Budget, Capital Planed, Operating Planned, Total Planned, Capital Actuals, Operating Actuals, Total Actuals, Budget Variance ($), Budget Variance (%) Displaying the budget variance allows the PM to understand of the project is over / under spent, and thus the costs planning needs to be re-visited.
  • Part of the Business Transformations collection, this portlet displays planned revenue as defined by a project whose goal is "Grow the business". It uses the Planned Revenue Query as a data provider.  This portlet provides a holistic overview of how many projects following the goal “Grow the Business” are Critical/ At Risk / On Track with regard to the planned revenue.
  • Part of the Business Transformations collection, this portlet displays planned revenue as defined by a project whose goal is "Grow the business". It uses the Planned Revenue Query as a data provider.  This portlet provides a holistic overview of how many projects following the goal “Grow the Business” are Critical/ At Risk / On Track with regard to the planned revenue.
  • Part of the Business Transformation collection, this portlet displays count of the planned benefits (savings) per project manager. It also displays if any of the planned benefits are Critical/ At Risk / On Track, along with the total planned benefit amount.
  • Part of the Business Transformation collection, this portlet displays count of the planned benefits (savings) per project manager. It also displays if any of the planned benefits are Critical/ At Risk / On Track, along with the total planned benefit amount.
  • Pie Chart Portlet displays counts of active projects with various Stale ratings. Calculation is Percent Stale Tasks = number of open (not completed) tasks with a finish date over 15 days old, divided by total open tasks.  Filterable by OBS structure and project manager.  Data label = project count.  Mouse-over and Legend labels = stale rating.  More than 90% Stale means 90 to 100% of open tasks on a project have finish dates older than 15 days.  More than 80% Stale means 80 to 89% of open tasks on a project have finish dates older than 15 days.  Less than 70% Stale means fewer than 70% of open tasks on a project have finish dates older than 15 days. By clicking on pie slice, a drilldown grid portlet appears with listing of projects and their Stale Ratings.
  • Pie Chart Portlet displays counts of active projects with various Stale ratings. Calculation is Percent Stale Tasks = number of open (not completed) tasks with a finish date over 15 days old, divided by total open tasks.  Filterable by OBS structure and project manager.  Data label = project count.  Mouse-over and Legend labels = stale rating.  More than 90% Stale means 90 to 100% of open tasks on a project have finish dates older than 15 days.  More than 80% Stale means 80 to 89% of open tasks on a project have finish dates older than 15 days.  Less than 70% Stale means fewer than 70% of open tasks on a project have finish dates older than 15 days. By clicking on pie slice, a drilldown grid portlet appears with listing of projects and their Stale Ratings.
  • Pie Chart Portlet displays counts of active projects with various Stale ratings. Calculation is Percent Stale Tasks = number of open (not completed) tasks with a finish date over 15 days old, divided by total open tasks.  Filterable by OBS structure and project manager.  Data label = project count.  Mouse-over and Legend labels = stale rating.  More than 90% Stale means 90 to 100% of open tasks on a project have finish dates older than 15 days.  More than 80% Stale means 80 to 89% of open tasks on a project have finish dates older than 15 days.  Less than 70% Stale means fewer than 70% of open tasks on a project have finish dates older than 15 days. By clicking on pie slice, a drilldown grid portlet appears with listing of projects and their Stale Ratings.
  • Part of the Business Transformation collection, this pie chart portlet displays realized benefit, grouped by location of project. This provides the PM with a holistic view of benefits realized across the geographical locations.
  • Part of the Business Transformation collection, this pie chart portlet displays realized benefit, grouped by location of project. This provides the PM with a holistic view of benefits realized across the geographical locations.
  • Part of the Business Transformation collection, this line chart portlet displays realized vs planned benefits overtime, for portfolio investments. This provides the PfM with a holistic view of benefits planned vs realized over a period of time.
  • The portlet, Project Change Request Count Pie with drill-down is a simple pie that displays the total count of projects in the pie. The slices are:
    • Projects with 0 change requests
    • Projects with 1 change request
    • Projects with 2-5 change requests
    • Projects with 5-10 change requests
    • Projects with over 10 change requests
    The drill down grid provides the details behind any of the slices.   Clicking on any of the segments, e.g. 11, redirects to the Projects with Change Requests portlet.
  • The portlet, Project Change Request Count Pie with drill-down is a simple pie that displays the total count of projects in the pie. The slices are:
    • Projects with 0 change requests
    • Projects with 1 change request
    • Projects with 2-5 change requests
    • Projects with 5-10 change requests
    • Projects with over 10 change requests
    The drill down grid provides the details behind any of the slices.   Clicking on any of the segments, e.g. 11, redirects to the Projects with Change Requests portlet.
  • The portlet, Project Change Request Count Pie with drill-down is a simple pie that displays the total count of projects in the pie. The slices are:
    • Projects with 0 change requests
    • Projects with 1 change request
    • Projects with 2-5 change requests
    • Projects with 5-10 change requests
    • Projects with over 10 change requests
    The drill down grid provides the details behind any of the slices.   Clicking on any of the segments, e.g. 11, redirects to the Projects with Change Requests portlet.
  • The portlet, Count by Stage with Drilldown is a simple pie based on stage OOTB field. The drill down portlet has stage as a column.   Clicking on any of the segments, e.g. Initiation, redirects to the Projects by Stage Drill portlet.
  • The portlet, Count by Stage with Drilldown is a simple pie based on stage OOTB field. The drill down portlet has stage as a column.   Clicking on any of the segments, e.g. Initiation, redirects to the Projects by Stage Drill portlet.
  • The portlet, Count by Stage with Drilldown is a simple pie based on stage OOTB field. The drill down portlet has stage as a column.   Clicking on any of the segments, e.g. Initiation, redirects to the Projects by Stage Drill portlet.
  • Horizontal Bar Chart displays one bar per manager (manager name on vertical axis).  Horizontal axis shows project count.  Filtered by Parent Stage.  Each bar shows color coded stages, where length of each color is proportional to the count.  Data label = count by stage. Mouse-over = stage name and percent count of total projects.  Legend = child stage names.  Drilldown functionality:  Clicking on a bar color yields a project grid portlet with projects in that stage for that manager.
  • Horizontal Bar Chart displays one bar per manager (manager name on vertical axis).  Horizontal axis shows project count.  Filtered by Parent Stage.  Each bar shows color coded stages, where length of each color is proportional to the count.  Data label = count by stage. Mouse-over = stage name and percent count of total projects.  Legend = child stage names.  Drilldown functionality:  Clicking on a bar color yields a project grid portlet with projects in that stage for that manager.
  • Horizontal Bar Chart displays one bar per manager (manager name on vertical axis).  Horizontal axis shows project count.  Filtered by Parent Stage.  Each bar shows color coded stages, where length of each color is proportional to the count.  Data label = count by stage. Mouse-over = stage name and percent count of total projects.  Legend = child stage names.  Drilldown functionality:  Clicking on a bar color yields a project grid portlet with projects in that stage for that manager.
  • Pie Chart displays counts of all projects by out-of-box Status Indicator attributes.  Filterable by OBS structure and Manager.  Data label displays count.  Mouse-over and Legend display Indicator name.  Chart also displays count for projects with no Indicator.
  • Pie Chart displays counts of all projects by out-of-box Status Indicator attributes.  Filterable by OBS structure and Manager.  Data label displays count.  Mouse-over and Legend display Indicator name.  Chart also displays count for projects with no Indicator.
  • Pie Chart displays counts of all projects by out-of-box Status Indicator attribute.  Filterable by OBS structure and Manager.  Data label displays count.  Mouse-over and Legend display Indicator name.  Chart also displays count for projects with no Indicator.  By clicking on a pie slice, a grid portlet appears displaying all projects with that indicator value.
  • Pie Chart displays counts of all projects by out-of-box Status Indicator attribute.  Filterable by OBS structure and Manager.  Data label displays count.  Mouse-over and Legend display Indicator name.  Chart also displays count for projects with no Indicator.  By clicking on a pie slice, a grid portlet appears displaying all projects with that indicator value.
  • Pie Chart displays counts of all projects by out-of-box Status Indicator attribute.  Filterable by OBS structure and Manager.  Data label displays count.  Mouse-over and Legend display Indicator name.  Chart also displays count for projects with no Indicator.  By clicking on a pie slice, a grid portlet appears displaying all projects with that indicator value.
  • Pie Chart displays total Ideas by Priority, filterable by Active / Inactive and by OBS structure.  Data Label and Mouse-over label display counts by Priority.  Legend shows Priority Name.  Chart also shows Ideas with No Priority.
  • Pie Chart displays count of all Ideas by Department.  Filterable by Active and Inactive, by OBS, and by Department Manager.  Data label and mouse-over show department counts.  Legend displays department names.
  • Pie Chart displays count of all Ideas by Department.  Filterable by Active and Inactive, by OBS, and by Department Manager.  Data label and mouse-over show department counts.  Legend displays department names.
  • This view depicts trends of created and resolved Incidents over time, grouped by month.  The count of incidents opened is determined by the Created Date of the Incident, and the count of Incidents closed is determined by the Resolution Date of the Incident. The view is filterable by Priority and Urgency as well as a date range.  NOTE:  The values returned are the total sum for a given month, not a cumulative total over time.
  • This view depicts trends of created and resolved Incidents over time, grouped by month.  The count of incidents opened is determined by the Created Date of the Incident, and the count of Incidents closed is determined by the Resolution Date of the Incident. The view is filterable by Priority and Urgency as well as a date range.  NOTE:  The values returned are the total sum for a given month, not a cumulative total over time.
  • This view depicts trends of created and resolved Incidents over time, grouped by month.  The count of incidents opened is determined by the Created Date of the Incident, and the count of Incidents closed is determined by the Resolution Date of the Incident. The view is filterable by Priority and Urgency as well as a date range.  NOTE:  The values returned are the total sum for a given month, not a cumulative total over time.
  • The Team Skills portlet displays Skill Proficiency and Interest Level by Resource.  Users can utilize this view to search for Resources by Skill, Parent Skill, Interest, Role, Parent Role, Resource and Resource OBS.   This portlet grants a Project Manager or Resource Manager the ability to determine which Resources best fit the needs for their project.
  • The Task Baseline Compare portlet displays the tasks in a specific Investment and provides the ability to compare the baseline hours for the tasks in each version of the baseline.
Go to Top