-
Allocation Compliance for PM report gives a view of resource Allocation percentage for active resources on the team of an investment for a selected Investment Manager. It allows the PM to see resources on their project over the coming months and whether they are over or under allocated. Allocation Percentage is calculated as (‘Allocated Hours’ / ‘Available Hours’) * 100. User can further narrow their search Month Start Date and Investment Manager. User can use exact dates or relative dates for Month Start Date filter parameter. -
Course description: “Is there a way to simplify time tracking? Time is a function 90% of companies use. What are ways to have time be less of a burden to users? How can you minimize the negative perception? This session will discuss options within CA PPM or outside CA PPM to make time tracking less of a burden for all.” Download file is the presentation slide deck. -
Course description: “How are other companies storing or managing documents? This session will discuss options for using native CA PPM, linking to SharePoint, connecting directly to SharePoint, using Google docs, as well as other options. This session will also discuss options for document approval workflows within CA PPM for both collaborative documents and attachment fields.” Download file is the slide deck used during the presentation. -
The Timesheet Smoothing Process Workflow kicks-off when an individual timesheet is Submitted. It splits each transaction on the timesheet when total timesheet actuals exceed total weekly availability for the resource. Total weekly availability is determined by multiplying resource availability rate by the number of workdays in the week. Non-workdays include weekends, holidays, PTO, and other scheduled days off, as set on the resource calendar. If timesheet actuals <= total weekly availability, then the timesheet remains unchanged. But if timesheet actuals > total weekly availability, then the following occurs. Each timesheet transaction is reduced by a calculated percentage that will reduce the total regular hours to equal the total weekly availability. Then the remaining transaction hours are placed in a “Split” row for that task on that day, with an Input Type Code set based on a process parameter (which parameter can be set within the script action on the process). Note: If a single day has overtime hours, but the total timesheet actuals <= total weekly availability, no splitting occurs. -
This Process sends an email to every Action Item Assignee where the Due Date/Time has passed and the Status is either Open, or In Progress. Users may want to modify this stalker to include Status = Deferred. In addition, the Resource Manager for the Assignee receives a copy of the email. In order to generate emails, the SMTP gateway must be up and running and Resources must have a valid email address. -
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 Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource. You first choose the resource who currently has the action item(s) sitting in their queue. Next, you choose the resource you want to reassign the action item(s) to. Finally, you select one to many action items you want to re-associate before running the process. After all the fields are set, the process can be run which will re-associate the action items from one resource to the other. -
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
-
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 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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy