RegoXchange
  • Calendar View report provides a view of Projects, Milestones or Tasks that has finish date within the user selected month. User has the flexibility to choose to Calendar view as Monthly or Weekly and also number of periods that needs to be displayed in the report. Report can be filtered to show only Projects or Milestones or Tasks with the checkboxes provided. It can also be further filtered using Project Manager and Project OBS parameters.
  • This portlet shows the project costs by Month. The information displayed includes:
    • Start Date for project
    • End Date for project
    • Budgeted Cost
    • Planned Cost
    • Actual Hours
    This provides the PM with a one shot view of the total financials/actuals for the project. The Project name field is linked to the project properties page. In case of any adjustments, the PM can toggle b/w the portlet and the project with ease.  The user can filter on multiple projects, or projects by OBS, or by PMs, to view the data on the portlet.
  • This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object.  The solution is comprised of:
    • Sub-Object (Benefit Plan Details, Parent = Project)
    • Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
    • Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
    The Process to create the Benefit Plan is initiated when users check the Create Benefit Plan box on the sub-object.  Every time the Process runs it aggregates all rows from the sub-object that are flagged as Financial and creates a new Benefit Plan.  The resulting BP is not linked to any Cost Plans. Users who install this base solution will want to consider:
    • Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
    • Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
    • Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
    • Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
    Once installed, please refer to the Benefit Detail Functionality Document for how to create Benefit Detail records, initiate the process, and the Benefit Plan Creation.
  • A Quick Reference Guide to assist in managing a Custom Investment in Clarity’s Modern UX.  Reviews accessing the Custom Investment Link and navigating the tabs.
  • The Project Storyboard report is a transaction based Jaspersoft report that does not require the Load Jaspersoft Datawarehouse job to be run.  The report will pull real-time data from the transaction tables in Clarity.  This report can be run from either the Advanced Reporting or Reports and Jobs area within Clarity. The Project Storyboard report shows key aspects of a project that is organized in separate frames. Each frame in the report displays project information such as project dates, project objective, the amount, and cost of resources that are planned and actual, key accomplishments, upcoming activities, current issues and risks, and the project progress toward goals. This report can be used to analyze the project earned value and track work performance to account for cost and schedule variances.
  • This video describes the process to baseline a project using OWB. The video is available in both .m4v and .wmv formats.
  • This video describes the process to assign resources to tasks within OWB. The video is available in both .m4v and .wmv formats.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the use of the Staffing Plan in Clarity’s Modern User Experience.  This doc references version 16.0.3 views. Document provides information on how to swap between views to see investments by resource or resources by investment. Instructions on filtering are provided, as well as detail on how to update the unit of measure between FTE (Full Time Equivalent) and Hours. Tips are provided on how to expand the list of investments within each view and how to view the properties for the allocations. A Legend is also documented to provide information on each of the icons that are displayed on this page.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the creation and editing of Tasks in the Timeline View of Clarity’s Modern User Experience.  This doc references version 16.0.3 views. Doc covers how to create a new task in the Timeline View, how to insert sibling or insert child tasks, how to set Milestones, access the Details pane and add resource Assignments. Also details how to move tasks by clicking and dragging within the Timeline View.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the creation and editing of Tasks in the Timeline View of Clarity’s Modern User Experience.  This doc references version 16.0.2 views. Doc covers how to create a new task in the Timeline View, how to insert sibling or insert child tasks, how to set Milestones, access the Details pane and add resource Assignments. Also details how to move tasks by clicking and dragging within the Timeline View.
  • This training document is a Rego Consulting Quick Reference Guide to assist in the replacement of roles with named resources in Clarity’s Modern User Experience.  This doc references version 16.0.2 views. Document provides detail on soft bookings, default allocation and requested manager. Instructions are provided on how to access requests from the Staffing Plan view and how to swap the role for a named resource. If requests are not fulfilled in their entirety, details are provided on how the excess allocation is handled.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the use of Clarity’s PPM Gantt.
  • A Quick Reference Guide to assist in the creation of a Project Status Report in Clarity.  The document uses screen shots from the Classic UX with the Phoenix theme.
  • Does project and idea estimation take too long and lack visibility? This class will address one of the most common pain points within organizations: how to involve the right people within a timely project estimate. Learn Rego’s model for defining, calculating, and modifying idea and project estimates, so you can increase throughput and ROI.
  • 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 Metrics consist of the following:
    • 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 ** 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
  • A Quick Reference Card to assist in creating a project in CA PPM.  Reviews options of creating from New or New from Template.
  • The Project Status Summary report is a transaction based Jaspersoft report that does not require the Load Jaspersoft Datawarehouse job to be run.  The report will pull real-time data from the transaction tables in Clarity.  This report can be run from either the Advanced Reporting or Reports and Jobs area within Clarity. The Project Status Summary report displays summary information about a project, including current stage, overall status, key accomplishments, upcoming activities, the cost and amount of resources that are consumed, mapped risks indicating categories with a high number of risks, and a high-level Gantt chart displaying information about the project phases and key milestones.
  • The Allow PM to Give Certain Rights modification allows the project manager to delegate rights (chosen by the administrator on the PM Rights object) on his or her projects. This modification eliminates the need for project managers to request additional rights through the PMO/management and simplifies the entire process for everyone involved. The system administrator is able to customize the PM Rights object to pick which rights should be granted to users by the process. The process begins when a change is made on the newly created “Grant / Revoke” field on the project object. The process will then grant or revoke (depending on what option is selected) any rights listed in the PM Rights object to the user in the “Assign PM Rights” field on the project object.
  • 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.
  • The interface runs using a MS Excel template called Project Allocation Upload that will be distributed to users.
    1. Configuration
      1. 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.
      2. 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.
      3. The master object will store the file level data while the sub-object will store the rows that belong to the file.
      4. Users must be granted security to view and edit the master and sub-objects in order to run the upload process.
    2. Project Allocation Upload Template
      1. 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.
      2. Only the Project Allocation Upload template can be used to load records to the new objects.
      3. 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.
      4. The template must be distributed to the users that will be using the upload functionality.
      5. 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.
      6. A Staff OBS is not required but can be populated by users to have the data uploaded into CA PPM.
      7. The owner of the Project Allocation Upload template is responsible for providing users a valid list of Staff OBS Units.
      8. Investments will not be created through the interface. As such a valid Investment ID must be provided.
      9. 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.
      10. 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.
      11. Resources cannot be removed from investment teams through the interface.
      12. 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.
        1. 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..
        2. 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.
      13. The allocation template will follow the format in the screenshot area.
    3. Process
      1. 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.
      2. 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.
      3. 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.
      4. 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.
        1. Regarding the Staff OBS.  Only one OBS can be designed as the OBS that the interface will use to validate the Staff OBS records.
        2. The Staff OBS value from the template must match against the name of an OBS node in the designed Staff OBS.
        3. 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.
      5. 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.
      6. 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.
      7. 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.
  • 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 Project Compliance Stalker – PM sends an email to Project Managers (and also their managers if so desired) at a set interval to alert them to project compliance issues. Areas of compliance that are reviewed include: stale project tasks (stale = past due date), late issues and risks (past due date) and late status reports.
  • 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 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.
  • Course Description:   This class will provide a list of daily and weekly activities that every project manager should follow to leverage Clarity PPM more effectively.
  • 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.
  • 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 Dashboard: Project Information portlet gives a set of high-level information about 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 displays the name, project ID, project manager, description, start date, finish date, baseline start, and baseline finish.
  • Rally Software introduction including high level feature and functionality for Agile and portfolio planning and tracking, analytics and reporting, and overall benefits of Rally in the marketplace along with a product demo.
  • 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.
  • Learn about the various techniques and emerging methods companies are taking to capitalize Agile work. You'll learn how some companies are moving away from timesheets and using models based on story points and team rates to generate capitalization reporting.
  • This training document is a Rego Consulting Quick Reference Guide to assist with the utilization of Tasks and To Do’s in Clarity’s Modern User Experience.  This doc references version 16.1 views. Document references the Tasks and To Do’s menu items and their associated widgets.
  • A presentation slide deck from Rego University 2022.   The course discusses factors that differentiate Requirements.
    • Introduction (What & Why)
    • Definition & Uses of Requirements
    • The Challenges in Requirements in Software
    • Revisit the Agile Taxonomy
    • The Transition from Traditional to Agile
    • Rethink the Agile Portfolio
    • Guidelines and Characteristic of Taxonomy
  • This portlet displays the actual hours resources entered against investments. The per-period actual hours can be showed in days, weeks, months, quarters, or years. The data can be filtered by Resource, Resource Manager, OBS Unit, Investment and time period
Go to Top