790 results
-
Assignments by Task Over Time report display all assignments by task for all resources. Information can be drilled down to yearly, quarterly or monthly level. This report helps in determining the tasks a user is assigned to or how many hours a user is assigned to a task. You can further narrow your search by OBS Type & Path, Project ID, Project Name, Task Name, Assignment Resource, Is project Active?, Is Template? And Month End date.
-
Resource Availability – 4 Weeks displays all resources with their total allocated hours by week, and an average availability percent (4 Wk Avail %) for next four weeks. This report also displays Resource Primary Role and Employment Type. User can further narrow their search by Resource Name, Resource Type & Week Start Date. User can use exact dates or relative dates for Week Start Date filter parameters.
-
Allocation Compliance Pie Chart provides the resource manager a single place to view the Allocation compliance information in the form of a Pie chart. Allocation Compliance is calculated based on the value of 'Availability to Allocation Hours %'. Allocation Compliance is 'Under Allocated (Less Than 80%)' WHEN 'Availability to Allocation Hours %’ is less than 80. Allocation Compliance is 'Appropriately Allocated (Between 80-120%)' WHEN 'Availability to Allocation Hours %' is between 80 and 120. Allocation Compliance is 'Over Allocated (Over 120%)' WHEN 'Availability to Allocation Hours %' is greater than 120. User can further narrow their search by Resource Is Active?, OBS Type, OBS Path, Allocation Start Date, Investment Name and Resource Manager. User can use exact dates or relative dates for Allocation Start Date filter parameter.
-
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 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
-
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days.
-
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days.
-
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project.
-
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project.
-
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in.
-
The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:
- The timesheet has less than 40 hours.
- The timesheet has 40 or more hours.
- The resource’s availability is less than 8hrs/day.
-
The Status Report Publish workflow process pushes values from the status report sub-object to the parent project object. The process is started when the user ticks the “Publish” Boolean field on the status report (custom field added). This workflow will update the project object with the overall status indicator, the status comment, the previous overall status, and the as of date. This eliminates the project manager having to update the fields in both the status report and the project overall.
-
The Give RM Calendar & Time Rights workflow process can be run through the "Execute a Process" job. The workflow will execute a query that gives a Resource Manager Calendar Edit and Timesheet Edit rights for their resources. These rights are not inherent for Resource Managers when they are named as an individual’s resource manager.
-
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.
-
Are you on an older version of CA PPM? Do you want to understand the value of the new features and functions in recent versions? Have you seen the new UX and do you wonder when is the right time to move over? This class is a demonstration of the new UX, new features in both classic and new UX, and the value of these features for customers.
-
Most organizations use CA PPM as part of an annual planning process, in conjunction with an ITFM or financial system. There is often a struggle to know where CA PPM fits into the process and how to effectively connect the data and processes between these tools. In this class, we will discuss how a PPM tool and an ITFM tool fit together to support annual planning.
-
Are you struggling with implementing Agile tools in your organization in addition to Clarity? This class will review best practices for implementing agile tools in conjunction with Clarity - living in a Bi-Modal world. We will discuss how Clarity can be used to govern both types of work and teams and how Agile tools should interface into Clarity.
-
A review of how Northern Trust integrates financial systems with Clarity PPM bilaterally, providing the Finance organization crucial information, and NT Project Managers with a birds-eye view of project financials. Utilizing the Rego Data Extractor and the Rego Data Processor, these information exchanges help Portfolio and Project Managers eliminate their manual and redundant efforts, solidify their overall data accuracy, and dramatically improve the content provided to their Execs for decision-making.
-
Agile is here to stay, but waterfall may be as well. Companies around the world struggle with living in a bimodal development world, while trying to go through an agile transformation. This session will discuss best practices and lessons learned within companies that have gone through agile transformations. We will also review SAFe as a potential approach.
-
No matter how hard we try, many organizations cannot pry Excel out of the hands of project and resource managers. In this class we will explore possibilities that give up the battle and embrace Excel as a great data entry tool. We will show some neat case studies on quick Excel integrations deployed at customers.
-
The Project Dependencies portlet displays all projects and their associated dependencies that the logged in user has rights to. This can assist in scheduling and visualizing the breakout of dependencies. The table below describes the available columns in the portlet. Column Label Description Project ID ID of the project Project Name Name of the project Type Relationship to above project, Parent Project (P) or Sub Project (S) Manager Manager of the project Start Start Date of the project Finish Finish Date of the project Gantt Visualization of project timelines Sort Column Used to order the columns for proper display of the portlet dimkey Internal code used by the query Inv_hlth_int Internal code used by the query Link_dbid Internal code used by the query link_toggle Internal code used by the query rel_active Internal code used by the query rel_dbid Internal code used by the query rel_mgr_dbid Internal code used by the query rel_sort Internal code used by the query -
Pie Chart Portlet displays counts of active projects with various Stale ratings. Calculation is Percent Stale Tasks = number of open (not completed) tasks with a finish date over 15 days old, divided by total open tasks. Filterable by OBS structure and project manager. Data label = project count. Mouse-over and Legend labels = stale rating. More than 90% Stale means 90 to 100% of open tasks on a project have finish dates older than 15 days. More than 71% Stale means 71 to 89% of open tasks on a project have finish dates older than 15 days. 0 - 70% Stale means fewer than 70% of open tasks on a project have finish dates older than 15 days.
-
The Milestone Task Dependency portlet shows the milestone task dependency count and has a drilldown to the details. The portlet looks at the dependency impact on milestones, and is not limited to just dependencies that are on different projects. The lag days calculation is based off of the maximum dependency impact and the drilldown portlet (Milestone Task Dependency Details :::: rego_milestone_dependency_det)shows the details for each.