-
The Capacity Planning by Role and Skill portlet displays all availability and demand in the system summarized by role. The portlet also allows the user to drill-down further into the role and separate the hours by primary skill. This portlet leverages the timeslices, and pulls availability from resources and allocation from the team records. The user is able to narrow the results by filtering on start/finish date, time period, active projects, and active resources. Using this portlet, a resource manager can quickly determine resource needs, skill needs, and overall allocation/availability of roles. -
The Capacity Planning by Skill portlet displays the capacity and demand by skill for a selected timeframe. This portlet is used to determine which skills are in high demand, being used efficiently, and how much capacity may be remaining for the time period. The portlet may be filtered by skill name, resource OBS or project OBS to narrow the results. -
The Capacity vs. Demand by Resource report displays resource capacity and demand at the resource level across investments. The report gives you visibility into the capacity, demand, and remaining capacity by resource. The report displays amounts by week or month, and in total. The amounts might be displayed as hours or FTEs. Report Prerequisites: Verify that you have completed the following prerequisites before you run this report: • The Load Data Warehouse job must be run before you run this report. If the Data Warehouse is not populated, the report will not display any data. Also, most of the report parameters do not display options. • Resource demand allocation amounts display if the resource is allocated to at least one investment and the report display type of hours as allocations. Resource demand assignment amounts display if the resource is assigned to at least one task on the investment and the report displays type of hours as assignments. -
The Capacity vs. Demand by Role report provides visibility into resource utilization by comparing available capacity to actual demand across investments at the role level. It highlights capacity, demand, and remaining capacity, helping identify potential surpluses or shortfalls. Data can be viewed by week or month and displayed in either hours or full-time equivalents (FTEs) to support detailed workforce planning and analysis. -
The Clarity Health portlet provides a quick glance into the health of key components and critical jobs in the Clarity environment. The following metrics are monitored: Process Engine Heartbeat should refresh itself every 10 minutes. Process Engine is responsible for the triggering of processes. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Time Slices Time Slices are required for accurate reporting. Best practice is for the Time Slicing job to run every minute. Please note there are some jobs that will cause the time slicing to delay so a momentary delay is normal. Green <= 10 Minutes, Yellow 11-15 Minutes, Red > 15 Minutes Datamart Extraction Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Datamart Rollup Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Full Best practice is to run a full rate matrix nightly Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Rate Matrix - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Full Load Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse - Incremental Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours Load Data Warehouse Access Rights Green <= 24 Hours, Yellow 24-48 hours, Red > 48 hours -
The Communications Object allows a user to send an html-based email to all users on a project, in a security group, or to individual users directly from Clarity. An email can be sent by creating a new entry on the Communication List page, upon saving a new entry the email process with trigger and send the email. Auto Start Solution: An email can be sent by creating a new entry on the Communication List page, upon saving a new entry the email process with trigger. On Demand Solution: All emails could be sent together as a broadcast communication by running the process manually from the Organizer. This process could also be scheduled to run on a specific time using Jobs The table below describes the available columns on the object.
Either of the on-demand process or auto start process should be active at a time. The package provides two Processes: 1. Send Notification (ID:rego_send_notification) This is an auto start process. The notification is sent immediately when a new entry is created on the Communication object. Only one email notification will be sent for one entry. Any updates to the same entry will not trigger any new notifications. 2. Email Communication (ID:rego_email_comm) This is an on-demand process that could be run from the Organizer. This send notification to all the entries on the Communication objects for which a communication was not already sent. This process does not have a Primary object. The processes are designed to work both in Oracle and Postgres environment. If the DB vendor information from Properties.xml is Postgres the SQL query for Postgres will be called. If not, the default SQL is Oracle. Important Note: Either of the processes should be active for an Implementation. If both the processes are active the on-demand process has no effect and will never send any communication. All object entries have a sent flag which will be marked whenever a notification is sent. Both the processes set the same flag on the object instance. Only with admin DB rights this flag could be overwritten. Object Name:Communication Object ID: rego_communication Flag Attribute Name: Sent (Id: rego_sent)Column Label Description From Who the email is coming from Sent To Individual users the message should send to Send to Group Security groups the message should send to (users within the security groups) Message Project Team Should this message be sent to a project team Associated Investment If Message Project Team is checked, which project should the team list be pulled from Message Subject Subject line of the email Message Content Body of the email (html) Message date Internal code used by the query -
The Communications Portlet - Simple portlet provides a simple mechanism to communicate with Clarity users. The content of the porlet can be edited easily through the Portlet administration screens within Clarity. This is a very beneficial method of delivering messages to your Clarity users all at the same time. -
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project. -
This is workflow that allows you to copy documents from one item to another. This can be altered to move documents from any place they are stored to another. In this particular instance, the focus is on moving documents from one risk to another. When creating a risk that you want to copy from, utilize the attachments section of the page and the associated lookup. The lookup is filtered to only show those risks that already have documents associated with them. Upon clicking the save button, a process runs in the background to copy the requested documents from the requested risk to this newly created risk. -
A process creating a new Cost Plan. Cost Plan properties:
Pre-conditions:Name Cost Plan created on: yyyy/mm/dd hh:mm:ss Grouping attributes Charge Code, Transaction Type Start Period The earliest fiscal period with Actuals (from PPA_WIP table) or current period, if there are no actuals Finish Period The latest fiscal period with a non-zero allocation (from PRJ_BLB_SLICES table, SLICE_REQUEST_ID = 6 Period Type Monthly Plan of Record True Planned Cost For periods in the past – from Actuals (Charge Code, Transaction Type, Quantity (Units), Cost (Amount) taken from Transactions (PPA_WIP & PPA_WIP_DETAILS); For current and future periods – from Allocations (Charge Code taken from the Project, Transaction Class from the Resource, Quantity from allocation slices, Cost from the Rate Matrix (NBI_PROJ_RES_RATES_AND_COSTS table) - the Project must be financially enabled.
- if a new Team Member is added, Rate Matrix job must be run, so the rates are populated in the NBI table.
- if the Allocation changes, allow the timeslice job to finish before running the process.
- the Project should have the Charge Code set.
-
The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active. The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date). -
The Custom License Count portlet displays the license type and number of users with each type of license. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy