RegoXchange
  • 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.
  • The All Lookups and Attributes portlet provides the ability to see all static lookups in the system, as well as their lookup values. Ability to filter and view the population by lookup name and ID, value name and ID, whether or not the item is active, and whether or not the item is a system (seeded) value.  A system value is a record that comes with a base installation of Clarity as opposed to a value that was added manually or through a Clarity Add-in.
  • The All Lookups and Attributes portlet provides the ability to see all static lookups in the system, as well as their lookup values. Ability to filter and view the population by lookup name and ID, value name and ID, whether or not the item is active, and whether or not the item is a system (seeded) value.  A system value is a record that comes with a base installation of Clarity as opposed to a value that was added manually or through a Clarity Add-in.
  • The All Lookups and Attributes portlet provides the ability to see all static lookups in the system, as well as their lookup values. Ability to filter and view the population by lookup name and ID, value name and ID, whether or not the item is active, and whether or not the item is a system (seeded) value.  A system value is a record that comes with a base installation of Clarity as opposed to a value that was added manually or through a Clarity Add-in.
  • 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 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 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.
  • 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.
  • 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.
  • 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.
Go to Top