-
Part of the Business Transformation Content collection, this bar chart portlet displays count of ideas per business unit. This provides a holistic view of the idea pipe-line in an organization providing them a high-level of ideas converted, approved, unapproved per business unit. -
Horizontal Bar Graph displays total number of projects for each Business Owner/Sponsor for a selected Project Parent Stage (only Project Investments included). Vertical Axis displays Business Owner name. Horizontal Axis displays number of projects. Filter selectable for any Project Parent Stage. Color coding of bar and legend are synchronized to detail stage under the parent. Total for each detail stage displays on each segment of the bar. A mouseover displays a percent of total for each detail stage. -
Out of the box, there is no way to export or report on the Modern UX Roadmap Grid view. This report allows the end user to select one or more roadmaps and provides an exportable view of several OOTB fields from those roadmaps. When exported to and open in excel, the first tab will display a combined view of all selected Roadmaps, one row for every Roadmap Item, and additional tabs will display Roadmap-specific views. Custom attributes may be added to the report by your developers. -
This video describes the process review and approve/reject Pending Actuals and ETCs within OWB. The video is available in both .m4v and .wmv formats. -
This video describes the process either a Start or Finish date on a project in OWB. The date (start or finish) will determine the point from which all tasks in the project are then scheduled. The video is available in both .m4v and .wmv formats. -
This video provides an overview of utilizing the various views available within Open WorkBench. The video is available in both .m4v and .wmv formats. -
Part of the Business Transformation collection, this grid portlet displays idea details for all ideas (active and inactive) and all status conditions. This is an editable portlet based on the Ideas data provider. Filterable by OBS structure, Active/Inactive, and Status. -
This training document is a Rego Consulting Quick Reference Guide to assist with the management of Roadmap items within the Grid View in Clarity’s Modern User Experience. This doc references version 16.0.3 views. Instructions are provided to help users add and remove columns, move columns, pin columns and sort rows of data. The document provides guidance on how to use the View Options function to manage Per-Period Metrics. Includes guidance on how to update Roadmap data from the Grid View and how to use the In Plan column to rank investments. -
This training document is a Rego Consulting Quick Reference Guide to assist with General Navigation in Clarity’s Modern User Experience. This doc references version 16.0.3 views. Doc reviews the Menu Bar and User Tool Bar. -
This training document is a Rego Consulting Quick Reference Guide to assist with the adding of resources to the Staff tab for Ideas in Clarity’s Modern User Experience. This doc references version 16.0.2 views. Document provides detail on how to add resources to the Staff tab, Default Allocation % and Per-Period metrics. -
This training document is a Rego Consulting Quick Reference Guide to assist with General Navigation in Clarity’s Modern User Experience. This doc references version 16.0.2 views. Doc reviews the Menu Bar and User Tool Bar. -
A Quick Reference Guide to assist with the creating and managing of Cost Plans in Clarity. The document uses screen shots from the Classic UX using the Phoenix theme. -
A Quick Reference Guide to assist in the creation of risks, issues and change requests in Clarity. The document show this with screenshots from the Classic UX with the Phoenix theme. -
A Quick Reference Guide to assist in creating a project from a template in Clarity’s Classic UX. Document uses screen shots to walk through the process. Document uses the Phoenix Theme. -
A slide deck from Rego’s training class on Portfolio Management using Clarity’s Classic UX. Covers an introduction to Portfolio Management including definition, portfolio contents, PfM roles and responsibilities, how portfolios work, data used, key deliverables, prerequisites for starting PfM, and PfM security. -
Pie Chart displays projects by Baseline Finish Variance—is current project finish beyond baseline finish; or is current project finish on or before baseline finish. Filterable by OBS structure and Finish Date range. Data labels show percent within baseline vs percent outside baseline. Mouse-over shows Within or Outside label and percent of total projects. Legend shows color coded Within Baseline and Outside Baseline labels. Drilldown: Clicking on a pie slice yields a grid portlet of projects either Within or Outside Baseline. -
The Percent Time by Type and Timescale - Grid portlet shows a breakout of time by timescale for resources the logged in user has view rights for using the timeslices. This portlet gives the Clarity user the ability to show the amount of hours spent on a project by week, month, quarter and year. Using this portlet, the Clarity user can get an overview of all hours in a time period or use the filter to search for a specific dataset (as required). The portlet provides a filter for OBS and date ranges. -
Late Milestones report displays the list of all milestones that are not closed but are past their finish date or past their baseline finish date. The report provides Project Manager the ability to view and track late milestones across multiple projects without going into each project individually. This report displays Project ID, Project Name, Project Manager, Milestone Name, Due Date, Baseline Date, Days Late (Elapsed days between Task Finish date and Task Baseline Finish date), and Days Old (Elapsed days between Task Finish Date and Today's Date). User can further narrow their search by Project ID, Project Name, Project Manager Name, Milestone Name, Due Date between, Baseline Date between, Is Milestone?, Is late?, Task Status, Is Template?. User can use exact dates or relative dates for Due Date between and Baseline Date between filter parameters. -
All Risks report provides the project manager a single place to view risks across multiple projects. This report displays Project Information such as ID, Name & Manager, Risk Information such as its ID, Name, Owner, Status, Probability, Impact, Target Resolution Date & Days Open. You can further narrow your search by Risk Status, Risk Name Risk Impact, Risk Owner, Project Name and Project Manager. -
All Tasks report provides the Project Managers a single place to view all the tasks associated with a project(s). User can view only the investments that he has access. Project Managers can use this report to view the progress of the tasks and check how the tasks are performing against baseline date. User can further narrow their search by OBS Type & Path, Investment Name, Month Start Date and Is Project Active?. -
All Change Requests report provides the project manager a single place to view change requests across multiple projects. This report displays Project Information such as ID & Name, Change Request Information such as its ID, Name, Category, Owner, Status, Priority, Expected Close Date and Days Open. You can further narrow your search by OBS Type & Path, Change Request Status, Change Request Name, Change Request Category, Change Request Owner, Project Name and Project Manager. -
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 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.
-
“PM Stalker – Project Validations & Issues” executes various queries against the Clarity database and sends an email to all PMs who have one or more projects with any of the following conditions:- Resources have booked time in the past week (validation needed)
- Inactive Resources with ETCs still on the project
- Tasks past their Finish Date but not completed
- Task Role Assignments in the past
-
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 updates the team, assignment and timesheet roles with the primary role where they do not match. This way, the PM can push all roles to team and assignment for that project before they do a cost plan. -
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. -
When a task is marked as complete the process looks to any tasks that are dependent on the newly completed task. If a task is marked as “Not Started” and all of the dependency tasks are marked as complete then the process will change the task status to “Started” and email all resources that are assigned to the task that has started. The process notifies resources that a task is ready to start and saves the project manager the manual effort of updating dependent tasks. NOTE: The process relies on task dependencies and is most useful in those environments where task dependencies are managed. -
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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy