-
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 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. -
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.
-
The Pending Actuals portlet displays pending actuals for resources by task. This portlet allows the user to filter on Project, Project Manager, Is Active and Is Open for Time Entry. This portlet provides Resource Managers and Project Managers a simple way to analyse which actuals have been submitted but not posted on specific tasks, as well as the aggregate pending hour total. Note: the information displayed is dependent on what the user has security rights to view. -
The Program Dashboard Sub-Project Open Issues portlet gives the ability to view issues on sub-projects of a program that are not closed or resolved. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the sub-project name, issue name, owner, target date, status and priority. -
The Program Dashboard Sub-Project Open Issues portlet gives the ability to view issues on sub-projects of a program that are not closed or resolved. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the sub-project name, issue name, owner, target date, status and priority.
-
The Program Dashboard Sub-Project Change Requests portlet gives the ability to view all change requests of sub-projects of a program. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by status, in descending order, and then by target date. It displays the sub-project name, change request name, owner, status, target date, approved by, and the priority. -
The Program Dashboard Sub-Project Change Requests portlet gives the ability to view all change requests of sub-projects of a program. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by status, in descending order, and then by target date. It displays the sub-project name, change request name, owner, status, target date, approved by, and the priority.
-
The Program Dashboard Sub-Project Change Requests portlet gives the ability to view all change requests of sub-projects of a program. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by status, in descending order, and then by target date. It displays the sub-project name, change request name, owner, status, target date, approved by, and the priority.
-
The Proposed Estimates vs. Task Estimates portlet gives the ability to identify when the Proposed Estimates for any given task exceed the Task Estimates. The portlet filters by investment name, investment ID, project OBS unit, investment active (yes/no/all), investment manager, resource name, resource ID, resource OBS unit, resource active (yes/no/all), and resource manager. Additionally, the results can be filtered by the proposed ETC greater than task ETC flag (yes/no/all). The information provided on the portlet includes the investment name, investment ID, investment active (yes/no), investment start/end dates, task name, resource name, resource active (yes/no), resource manager, total hours, total ETC, proposed ETC greater than task ETC flag (yes/no), pending actual hours, and proposed ETC hours. -
The purpose is to show actual hours, planned effort and remaining effort at the resource level, with the addition of OBS levels to support filtering and manipulation of the exported data. -
The purpose is to show actual hours, planned effort and remaining effort at the resource level, with the addition of OBS levels to support filtering and manipulation of the exported data.
-
Project managers may use this portlet to show the planned effort and the remaining effort on projects. Includes actual hours as well as estimate at completion. You may narrow the results by filtering by project name, project manager, project OBS, or active flag. The portlet will display each project by ID, name, project manager, planned effort (total allocation hours), actual hours, remaining effort (ETC), and estimate at complete (actual + ETC). -
The Benefits by Year portlet summarizes Benefit totals by year and is searchable by Project, OBS and Portfolio. The results display both Budgeted Benefit Plans and Forecast Plans and the associated Cost Plan. Users can make use of this portlet to view Benefit Plan totals across an OBS or Portfolio or to compare the Budgeted Benefit of a Project versus the current plan. -
The Dashboard: Project Status Single-line portlet gives an overview of the project overall status as well as the status indicators on the "current" status report object. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. This portlet displays the report date, symbols relating to the overall status, scope, schedule, cost/effort, and the overall explanation across a single line in the portlet. -
The Time By Type - Pie Chart portlet is a graphical representation of time by type of investment for all resources the logged in user has security rights to view. This portlet pulls from the daily timeslices, and can be used for determining what types of projects receive the majority of hours. The filter option allows for entry of a specific start date and finish date. -
The Missing Time by PM portlet displays all missing or late timesheets for resources staffed on a project where the logged in user is the project manager. Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Project managers may use this portlet to determine the timesheet status of resources staffed on their projects. You may narrow the results by filtering by resource manager, period start, resource name, or status. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet. -
The Missing Time by PM portlet displays all missing or late timesheets for resources staffed on a project where the logged in user is the project manager. Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Project managers may use this portlet to determine the timesheet status of resources staffed on their projects. You may narrow the results by filtering by resource manager, period start, resource name, or status. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet.
-
The Dashboard: Open Risks portlet gives an overview of all risks that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the risks first by priority and then by target date. It displays the name, owner, target date, probability impact, and priority. -
The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date). -
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority. -
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority.
-
The Dashboard: Financial Summary by Charge Code portlet displays financial information from the project summarized by Charge Code. The portlet is added to the dashboard page of a project and will pull all actuals by charge code on the project. The user may filter by date range to narrow the results. -
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy