790 results
-
Time by Assignment report displays time logged to assignments and its associated actuals on monthly basis for all filtered investments. It also displays total ETC and Actual hours associated with an assignment. User can further narrow their search by OBS Type & Path, Investment Type, Investment Charge Code, Investment Name, Task Name, Resource Name, Assignment Start Date and Assignment Finish Date. User can use exact dates or relative dates for Assignment Start and Finish Dates filter parameters. -
Rego’s Clarity Adoption Metrics package consists of two sets of metrics: Project metrics, and Resource metrics. Project metrics measure how effectively project managers are using Clarity to manage their projects. Resource metrics measure how effectively resource managers are using Clarity to manage resources. Metrics are scored on a scale of 0 to 5, with higher scores indicating greater adoption and use. All metrics can be viewed numerically or graphically, and can be broken out by OBS. In addition, metric data can display as a 12-month rolling history to help identify trends. Project metrics can also display by lowest / highest adoption rates for a specific resource metric or all resource metrics. There is a variety of way to view the Adoption Metric data, therefore, Rego has made this simple by creating an Adoption Metrics object that contains multiple tabs. Each tab displays one or more of the Project or Resource Adoption Metrics. Based on the nature of the Metrics some tabs will allow the ability to use a pull down menu to select a specific Adoption Metric. There is also a Metrics trending view that pulls monthly snapshots of the metrics. Project metrics consist of the following: - Project Status Reporting – Measures how well PMs create and publish project status reports.
- Project Risk Adoption – Measures how well Risks are being used and managed.
- Project Issue Adoption – Measures how well Issues are being used and managed.
- Project Schedule – Measures how well PMs create tasks and keep the project schedule current.
- Project Baseline – Measures whether or not baselines exist.
- Project Zero ETC’s – Measures how well the PM assigns resources to tasks with ETCs.
- Project Past ETC’s – Measures how many improperly scheduled tasks the PM has.
- Project Milestone / Key Tasks – Measures how well PMs create and manage Milestones / Key Tasks.
- Project Schedule Variance – Measures how effectively PMs manage their schedules.
- Project Effort Variance – Measures how effectively PMs manage their project efforts.
- Project Budget Variance – Measures how effectively PMs manage budgets or cost plans.
- Project Unfilled Roles – Measures project roles with allocations that are already started or starting within the next 30 days.
- Project Data Quality – Measures how effectively PMs complete the Description, Stage, Progress, Objective, and Sponsor/Business Owner fields.
- Project Commitment – Measures the hard allocations for a project over a two week time frame.
- Resource Clarity Usage – Measures how often users log into Clarity.
- Resource Timesheet – Measures if timesheets post in a timely manner.
- Resource Allocation – Measures how well RMs keep total resource allocations within the expected range for future time periods.
- Resource Actualy Utilization – Measures how well Resource allocations match actuals.
- Resource Allocation Date in the Past – Measures how many resources are open for time entry with dates in the past.
- Resource Data Quality – Measures how well RMs complete the Resource Manager and Primary Role fields and optionally the Skill and Employment Type fields.
- Resource Commitment – Measures how much resource available time is committed to projects.
-
** No Download - Do not Add to Cart ** As Clarity's Modern UX continues to evolve with each release, so has the transition conversation among Clarity Product Owners and Administrators. It's no longer a question of "if" and "when;" the question is, how? In this webinar, we'll explore some best practices that enable a successful shift from Classic to Modern. Through a collaborative discussion of overarching strategies to a step-by-step checklist, this session is designed to help you quickly position your users to take advantage of Clarity's latest and greatest capabilities. Nothing to Download - See Link below. http://info.regoconsulting.com/when-to-move-to-modernux-aug-2020 -
** No Download - Do not Add to Cart ** Organizational metrics that support any Agile methodology Yes–it's possible. Join our Rego expert guides to learn about industry-proven Agile metrics as well as new ideas to measure success across multiple levels of your value stream Nothing to Download - See link below. http://info.regoconsulting.com/agile-metrics-july-2020 -
Notify the PM with a list of tasks for their project as soon as the Timesheet is submitted. This is a good substitute for PM approval. When a timesheet is submitted, then the PM knows the time entered by person. This is an Auto-start process in Clarity named PM Time Notification - On Timesheet Submission and will be automatically spawned when a Timesheet is submitted. When the process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The Progress when 100% and the Status is Completed, an email would have arrived to the Project Manager with subject: “Resource <Name> has entered the following time on your Investment(s) for the week starting <Timesheet Start Date> ”. This email will list the Investments managed by the PM where task was entered by the Resource submitting the timesheet. Each PM would get a separate notification. PM for project X notified, and PM for project Y gets notified in another email. Therefore, one timesheet may spawn out multiple emails. But, if both the Projects have the Same PM, then only a single email gets sent out. “Opt-out Timesheet Notifications" checkbox is provided on the Project for PM’s who do not want to get notified on those projects. -
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.
-
A process that:- is a weekly email to a project manager. All of the content will be for where the person getting the email is the PM
- shows aggregate data for all of their projects
- sends the PM a reminder email at the end of each week showing the items that the PM needs to do. Maybe call it Weekly PM reminder.
- Shows the mentioned data in sections as follows:
- Past Due issues
- Only active projects
- Only open issues – not resolved or closed
- Show project name, project ID, issue name, issue priority, target resolution date, color (only red or yellow)
- Logic for Yellow = where target resolution is within the next week
- Logic for Red = target resolution date is in the past
- URL LINK: to that issue
- Past Due Risks
- Only active projects
- Only open risks – not resolved or closed
- Show project name, project ID, risk name, risk priority, target resolution date, color (only red or yellow)
- Logic for Yellow = where target resolution is within the next week
- Logic for Red = target resolution date is in the past
- URL LINK: to that risk
- Past Due Status Report
- Only active projects
- Show project name, project ID, report date, most recent overall status, color (only red or yellow)
- Only 1 line per project – show even if there is no status report
- Logic for Yellow = where latest status report date > 7 days ago
- Logic for Red = latest status report date is > 14 days ago
- URL LINK: to status report list
- Past Due Milestones
- Only active projects
- Only open milestones
- Show project name, project ID, task name, task finish date, color (only red or yellow)
- Logic for Yellow = where finish is within the next week
- Logic for Red = finish date is in the past
- URL LINK: to that milestone
- Past Due Forecast
- Only active projects
- Show project name, project ID, last updated date, most recent total plan of record amount, color (only red or yellow)
- Only 1 line per project – show even if there is no finish plan
- Logic for Yellow = where last updated date of the plan of record > 14 days ago
- Logic for Red = where last updated date of the plan of record > 30 days ago
- URL LINK: to cost plan
- Allocation Summary for the Project Team
- Past Due issues
- Unfilled Roles that need to be staffed
- Resources Actuals +/- 25% of Allocation
- Resource ETC +/- 25% of Allocation
- Pending Change Controls / Approval Status
- In addition to the Past Due Milestones, upcoming milestones
- Budget Summary
- Actual vs. Planned
- Burndown estimate
-
The interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.- Configuration
- A master object called Allocation Upload Files will be created. The object will contain a required attachment field on the create page that will receive the Project Allocation Upload MS Excel file.
- A new sub-object called Allocation Upload Records will be created. This object will contain the fields necessary to receive the data rows from the Project Allocation Upload template.
- The master object will store the file level data while the sub-object will store the rows that belong to the file.
- Users must be granted security to view and edit the master and sub-objects in order to run the upload process.
- Project Allocation Upload Template
- The Project Allocation Upload template must remain static. Any changes other than creating additional time periods or additional rows will cause the process to error.
- Only the Project Allocation Upload template can be used to load records to the new objects.
- The Project Allocation Upload will only accept months across the x-axis in the format DD/MM/YYYY. The month headers must appear in the first row of the template and contain the first day of the month.
- The template must be distributed to the users that will be using the upload functionality.
- Users will be required to enter an Investment ID and Resource ID so the process can correctly identify investments and resources to upload the allocation hours against.
- A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.
- The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.
- Investments will not be created through the interface. As such a valid Investment ID must be provided.
- Resources can be added to the investment team through the interface. If a valid Resource ID is provided the resource’s allocation will be updated if the resource already exists on the investment. If the resource does not already exist on the investment the resource will be added to the team along with the allocation hours.
- The Project Allocation Upload template will accept hours, not allocation percentages. Because CA PPM stores allocations as percentages of a resource’s availability the upload process must convert hours to a percentage. As a result small rounding errors may occur in the neighborhood of .01 hours per month.
- Resources cannot be removed from investment teams through the interface.
- The Project Allocation Upload template will support allocation uploads to different instances of the same role on the same investment as long as different Staff OBS units are provided.
- If multiple instances of the same role are assigned to the investment with the same Staff OBS the process will not know which instance of the role to upload the hours to. In these cases the process will consider these records as invalid. The PM will need to manually remove one of the instances or upload the hours manually..
- If multiple instances of the same role with the same Staff OBS unit are assigned to the same investment in the upload template the monthly hours will be totaled by investment, by role, by Staff OBS.
- The allocation template will follow the format in the screenshot area.
- Process
- To initiate the Allocation Interface a user will create a new Allocation Upload File instance, attach the Project Allocation Upload Template, and save the record. The file attachment field is an “enter-once” field, meaning that once a value has been set it cannot be changed. If a user wishes to upload another field they will create a new record.
- After the file has been attached the user will be presented with two check box fields, one to Validate and one to Validate and Upload. Checking either or both options will initiate the process.
- The process will first determine if any sub-object instances exist for the file. In other words, do any records already exist in the Allocation Upload Records sub-object pertaining to the newly uploaded file. If there are no records in the sub-object the process will use the uploaded file and read its contents into the sub-object. If errors are encountered during the file read they will be written to the process console, the process will throw an error, and end.
- Next, records will be validated. Only the sub-object instances that belong to the master object will be validated. Records belonging to other master object instances will not be validated or processed. All records in a status of Ready for Processing, Failed Validation, or Xog Load Error will be validated. Records will fail validation if an investment is not found corresponding to the investment ID provided, a resource is not found corresponding to the resource ID provided, or the date provided is not valid, or a provided Staff OBS does not yield a match. Records that fail validation will be flagged as invalid along with a description as to why they failed validation. Records that pass validation will be flagged as Ready for Processing and locked. The sub-object instances can be exported to excel if further analysis is required. If the Validate & Upload option was not selected the process will end here.
- Regarding the Staff OBS. Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.
- The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.
- If the Staff OBS value matches against multiple nodes in the Staff OBS the record will be flagged as invalid as the process will not know which node to use.
- If the Validate & Upload option was selected the process will continue and any valid records will be xog’ed into the investment team. The xog will be executed as the user that initiated the process so any security rules enforced by xog will be respected by the process.
- Successful records will be flagged as Processed Successfully in the sub-object and remain locked. Records that did not load successfully, due to a xog error or security limitation will be flagged as Xog Load Error, unlocked, and updated with a description containing the full xog output.
- Records that failed validation or failed the xog load can be manually edited and revalidated, and attempt to be uploaded again. Subsequent runs of the process will not read in data from the file, but rather process only sub-object instances that currently exist.
- Configuration
-
This process pulls in the total hours tracked, by resource, by task, for a given project for the weekly time period that ended. The information is sent to the Project Manager listed on the project. This process can be scheduled via the Execute a Process job. -
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero. -
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero.
-
The Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects. -
The PM Stalker – Submit Status Report workflow process will email any project manager that has not submitted a status report in the last two weeks. This process will ensure that all status reports are kept up-to-date and provide management with a reliable overview of the status on the project. -
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request. -
Would you like to get an overview of the fundamentals of Agile? This session will dispel the misconceptions of Agile and provide an understanding and definition of terms such as “bi-modal”, “Scrum”, “Kanban”, “weighted shortest job first” and “SAFe”. We will also talk about how Clarity fits into the Agile discussion and provide thoughts and practices on how PMOs are responding to this trending methodology. -
Agile metrics can be very different from traditional waterfall metrics. This session will walk through some of the key Agile metrics describing how and why they are used. Effective methods in reporting and sharing will also be covered. -
This portlet displays the % allocation of resources to projects. The portlet shows if the resource is allocated to the projects as an individual resource or as part of an Agile team, in which case it will display the resource % allocation to the team and what that will represent in terms of % allocation to the project. The Total Allocation % display the allocation of the resource to all investments is allocated to. Remaining Capacity and Over/Under columns will help identify the resources that still have availability and the ones that are over allocated. -
Part of the Business Transformation collection, this bar-chart portlet displays investments and (if exists) any child investments, which are at risk with regard to the schedule of the investments. -
Funnel Chart displays aggregated counts of Ideas by “Idea Progress”, a custom attribute. Chart shows Idea Progress names in legend, and count total is available as a mouse-over. No filters available on this portlet. -
The Global Action Items portlet will help users and clarity admins to keep track of action items in the CA PPM system. This is useful to keep track of Timesheet Approval through Action Item or any other Action Item related workflows. The portlet displays Name, Type Assignee, Created by, Due Date, Health and Status of the Action Items as default columns. The portlet provides Project, Project Manager, Project OBS, Assignee, Status and Due Dates of the Action Items as default filters. -
The Investment Resource Rate portlet allows a user to search for effective (or missing) rates for resources across all investment types. It pulls rate information from the matrix extraction tables and includes currency conversion if the environment supports multiple currencies. The portlet can be used both to search for the rate of any given resource and to determine which resources might be missing rates when an error is generated when attempting to populate a cost plan (REVMGR-20728:Rates and Costs are both missing for one or more roles/resources). -
The Investment Resource Rate portlet allows a user to search for effective (or missing) rates for resources across all investment types. It pulls rate information from the matrix extraction tables and includes currency conversion if the environment supports multiple currencies. The portlet can be used both to search for the rate of any given resource and to determine which resources might be missing rates when an error is generated when attempting to populate a cost plan (REVMGR-20728:Rates and Costs are both missing for one or more roles/resources).
-
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. -
It is quite common for Rally and Jira to coexist. However, connecting them effectively enhances the value stream for development teams and product owners. Learn what is available to make this happen along with some typical design patterns. -
Have you considered using Rally in conjunction with Clarity? Have you seen or heard about the OOTB connector? This class will go through the OOTB connector in detail and show how Rego has built our ad-on to enhance the connectivity between these two tools. -
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. -
In this session you’ll hear about how Hershey’s is using Clarity and Rally to plan and manage their work in a hybrid project management environment. Some of the key capabilities used in both tools will be covered and you’ll hear about their integration approach. -
This training document is a Rego Consulting Quick Reference Guide to assist with Idea approval and conversion to projects in Clarity’s Modern User Experience. This doc references version 16.1 views. Doc reviews setting Ideas as Approved and converting Ideas to projects. -
This training document is a Rego Consulting Quick Reference Guide to assist resource managers with the adjusting of timesheets. This doc references version 16.1 views. Document provides guidance on how to use the Review & Approve tab to adjust time that has already been entered by a resource. -
A presentation slide deck from Rego University 2022. Presentations by Erie Insurance, University of California, San Francisco, and The Hershey Company. -
A presentation slide deck from Rego University 2022. This document reviews the best practices for project management in Clarity. - Typical PM Activities
- Use Clarity: Get Off of Excel
- Make Information Easier to Access
- Make Flags Easy to Identify
- Simplify & Automate Reporting
- Open Discussion #3
- Work with a Regular Cadence
- Sample Schedule
-
The Auto-Approve Old Timesheets workflow process can be run through the "Execute a Process" job and may be used to quickly close out timesheets for a specified timeframe for period closure. The workflow will execute a query that will automatically approve ALL (no matter the status of the timesheet) timesheets that have a time period start date before the Approve Date specified within the process itself. -
Launch a Team chat with your users directly from the Clarity PPM tool. This is a good way to collaborate with the team and users for any quick update or interaction. This is a scheduled process in Clarity named Sync MS Team Launching Chat URL and will be scheduled to run for various frequency. When the process kick in it will be setting the Team link into the custom URL attribute of the Resource, which can be used to Launch Team chat from the tool. Sync Process come with two parameters for the Support team, which they can use as per there environment configurations. These two Gel parameters for quick configuration are:- launchMSTeamField: parameter for the Custom Resource Field to store Launch URL
- emailAddressField: parameter for field to pick mail address in SRM_RESOURCES table
-
Connect with user and get familiar with them via Office 365/Azure Profile photos synced with the Clarity PPM Avatars. This is a good way to collaborate with the team and users for any quick update or interaction. This is a scheduled process in Clarity named Sync Profile Photo from Office 365 and will be scheduled to run as a job. When the process is executed, it will be setting the Microsoft O365 profile photo into the users Avatar photo in Clarity PPM and optionally, sync custom attribute of the Resource with profile photo, which can be used for quick identification of the user. Sync Process come with some parameters for the Support team, which they can use as per there environment configurations. These some important Gel parameters for quick configuration are:- msProfilePicField : Custom Resource Field to store Photo, if not provided process will skip syncing the custom field.
- msTenantId: Microsoft Azure Tenant Id
- msClientId: Microsoft Azure Application client Id
- msClientSecret: Microsoft Azure Application client Secret
- msTeamPhotoSize: Define size of the photo to be fetched
- syncPPMAvatar: Parameter to Sync PPM User Avatar photo from MS Team
-
The PM Dashboard portlet provides an overview of all projects for which the user is the Project Manager without navigating to and opening each project individually. All critical information related to the project status is displayed in this portlet. Status indicators display the project’s statuses. Graphical stoplights and numbers provide an overview of all late Action items, Issues, Risks, Tasks, and Milestones. -
The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices. It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants. This will display both active and inactive projects.
