RegoXchange
  • The Late Project Action Items portlet displays all action items related to active projects that the logged in user has view rights to.  The action items displayed are those that are past their due date with a status of “In Progress” or “Open”.   The portlet provides a Project Manager the ability to view and track action items across multiple projects without going into each project individually. In a single consolidated list, all late project action items can be easily viewed, along with the project with which they are associated, the individual assigned, and the owner of the action item.
  • The Late Milestones portlet displays all action items related to active projects that the logged in user has view rights to.  The milestones displayed are those that are not closed but are past their finish date or past their baseline finish date.  The portlet provides a Project Manager the ability to view and track action items across multiple projects without going into each project individually. This portlet provides a single consolidated view of late milestones based on the current project baseline, and the age of the milestone. The portlet will display the Project ID, Project Name, Project Manager, Milestone Name, Due Date, Baseline Date, Days Late (calculated from baseline dates), and Days Old (calculated from today’s date).
  • The Incident Notes portlet displays all of the notes that have been entered against Incidents in a single view.   This allows users to more efficiently look at the notes, regardless of security rights, without having to enter each incident individually to view them.
  • The Resource Data Issues portlet is used to identify data exceptions related to resource setup.  This portlet helps to identify where resources are missing key data or are possibly sitting in an exception state.  This view will show resources that have one or many exceptions, including inactive resources. There is no security built into this portlet - all resources will show.  The only required field in the filter is Days, which is the number of days since the user last logged in. The user may also narrow the results by resource, OBS, or project type.
  • The Project Data Issues portlet is used to identify data exceptions related to project setup.  This portlet helps to identify where projects are missing key data or are possibly sitting in an exception state.  This view will show projects that have one or many exceptions, including inactive projects. The user may also narrow the results by project, OBS, or project type.
  • The Project Data Issues portlet is used to identify data exceptions related to project setup.  This portlet helps to identify where projects are missing key data or are possibly sitting in an exception state.  This view will show projects that have one or many exceptions, including inactive projects. The user may also narrow the results by project, OBS, or project type.
  • The Assignments by Task Over Time portlet displays all assignments by task for all resources using the timeslices. This portlet is useful for determining which tasks a user is assigned to or how many hours the user is assigned to a task. The user may filter on certain criteria that include: project name/ID, date range, resource name/ID, and resource OBS unit.
  • The All Tasks portlet displays all tasks related to active projects that the logged in user has view rights to.  The portlet provides the project manager a single place to view tasks across multiple projects without having to go into each project individually, and allows for more efficient management and reporting across projects. The portlet displays project actuals and estimates from the project (datamart tables). The portlet allows analysis like:
    • PMs may have several critical tasks that were supposed to start on a certain date.  To verify progress, they filter for that start date to perform a review of the tasks.
    • PMs can review days late to see how tasks are doing against the baseline date (<7 days is green, 7-14 is yellow, and >14 is red)
    • PMs can review days old to see how tasks are doing against today’s date (<7 days is green, 7-14 is yellow, and >14 is red)
    The table below describes the available columns in the portlet. The first 10 are configured in the default view:
    Column Label Description
    Project ID Unique project identifier
    Project Name Name of the project
    Project Manager Manager of the project
    Task Name Name of the task
    Task Status Not Started, Started, or Completed
    Task Start Start Date of this task
    Task Finish Finish Date of this task
  • The All Tasks portlet displays all tasks related to active projects that the logged in user has view rights to.  The portlet provides the project manager a single place to view tasks across multiple projects without having to go into each project individually, and allows for more efficient management and reporting across projects. The portlet displays project actuals and estimates from the project (datamart tables). The portlet allows analysis like:
    • PMs may have several critical tasks that were supposed to start on a certain date.  To verify progress, they filter for that start date to perform a review of the tasks.
    • PMs can review days late to see how tasks are doing against the baseline date (<7 days is green, 7-14 is yellow, and >14 is red)
    • PMs can review days old to see how tasks are doing against today’s date (<7 days is green, 7-14 is yellow, and >14 is red)
    The table below describes the available columns in the portlet. The first 10 are configured in the default view:
    Column Label Description
    Project ID Unique project identifier
    Project Name Name of the project
    Project Manager Manager of the project
    Task Name Name of the task
    Task Status Not Started, Started, or Completed
    Task Start Start Date of this task
    Task Finish Finish Date of this task
  • The All Risks portlet displays all risks related to active projects that the logged in user has view rights to access.  The portlet provides the project manager a single place to view risks across multiple projects without having to go into each project individually, and allows for more efficient management and reporting across projects. The portlet displays Project ID, Project, Risk ID, Risk, Category, Assigned to, Status, Probability, Impact, Priority, Target Resolution Date, and Days opened. The filter allows narrowing down of the risks by several different criteria. Note: Only the projects that the user has viewer rights to see will show up in the list.
  • The All Incidents portlet shows all Incidents the user has view rights on and provides a single view to increase ease of management. Status indicators provide a quick overview of incident statuses so a user may prioritize. The filter then allows the user to narrow their search using date ranges and/or resources assigned. Other alternatives for filtering include the status, urgency, priority or impact of the Incident.
  • The All Incidents portlet shows all Incidents the user has view rights on and provides a single view to increase ease of management. Status indicators provide a quick overview of incident statuses so a user may prioritize. The filter then allows the user to narrow their search using date ranges and/or resources assigned. Other alternatives for filtering include the status, urgency, priority or impact of the Incident.
  • Very seldom will an organization only deliver using Agile. Some work lends itself better in using Waterfall. The need for a dual operating model will drive the need for a deliberate tooling architecture that will usually include a PPM and an Agile tool.
  • When marking a Status Report 'Final' in a grid/list view, the system doesn't create a new 'Draft' report like it does when using the Status Report UI. For groups that prefer to manage in a grid/list, they need to always have a draft.
  • The Task-At-A-Glance Notes portlet provides a view of project tasks and assignments in an easy to read format, similar to popular sticky – note applications.  This portlet will display all tasks on a project, ‘pinning’ them to a dashboard.  Each task will include the resources assigned to them, as well as the ETCs left for the resource, and the actuals that they have posted.  Each sticky note allows you to link to the task details, as well as the resource assignment details. In addition to important assignment detail, each pin on the individual task’s note indicates if the task finishes before the baseline (green), or if it is going to finish after the baseline (red).
  • The Program Dashboard Sub-Project Status portlet gives the ability to view the most recent status report for all sub-projects on 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. This portlet displays each sub-project, type of status, and the symbol related to the severity.
  • The Program Dashboard Sub-Project Status portlet gives the ability to view the most recent status report for all sub-projects on 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. This portlet displays each sub-project, type of status, and the symbol related to the severity.
  • The Program Dashboard Sub-Project Status portlet gives the ability to view the most recent status report for all sub-projects on 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. This portlet displays each sub-project, type of status, and the symbol related to the severity.
  • The Program Dashboard Sub-Project Open Risks portlet gives the ability to view all risks on the 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 value, in descending order, and then by target date. It displays the sub-project name, risk name, owner, target date, status, probability, impact and value.
  • The Program Dashboard Sub-Project Open Risks portlet gives the ability to view all risks on the 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 value, in descending order, and then by target date. It displays the sub-project name, risk name, owner, target date, status, probability, impact and value.
  • This Project Variances portlet provides a project manager a consolidated view of all of their active projects and open project tasks and shows them the baseline variance for the task EAC’s and the task start and finish dates.  This gives the project manager a single place to view and manage how their projects are progressing against their baselines. The PM can easily detect when projects are running behind and pinpoint which tasks are causing the variance in the schedule.
  • This Project Variances portlet provides a project manager a consolidated view of all of their active projects and open project tasks and shows them the baseline variance for the task EAC’s and the task start and finish dates.  This gives the project manager a single place to view and manage how their projects are progressing against their baselines. The PM can easily detect when projects are running behind and pinpoint which tasks are causing the variance in the schedule.
  • This portlet shows the project costs by Month. The information displayed includes:
    • Start Date for project
    • End Date for project
    • Budgeted Cost
    • Planned Cost
    • Actual Hours
    This provides the PM with a one shot view of the total financials/actuals for the project. The Project name field is linked to the project properties page. In case of any adjustments, the PM can toggle b/w the portlet and the project with ease.  The user can filter on multiple projects, or projects by OBS, or by PMs, to view the data on the portlet.
  • This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object.  The solution is comprised of:
    • Sub-Object (Benefit Plan Details, Parent = Project)
    • Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
    • Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
    The Process to create the Benefit Plan is initiated when users check the Create Benefit Plan box on the sub-object.  Every time the Process runs it aggregates all rows from the sub-object that are flagged as Financial and creates a new Benefit Plan.  The resulting BP is not linked to any Cost Plans. Users who install this base solution will want to consider:
    • Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
    • Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
    • Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
    • Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
    Once installed, please refer to the Benefit Detail Functionality Document for how to create Benefit Detail records, initiate the process, and the Benefit Plan Creation.
Go to Top