RegoXchange
  • 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.
  • The tech-trick shows how to retrieve logged in User related values (ex: skill set) in timesheet.
  • Pending Actuals report provides the Project Managers a single place to view all the pending actuals on tasks across multiple projects. User can view only the projects that he has access to.  Managers can use this portlet to analyze the actuals that have been submitted but not posted on tasks.  You can further narrow your search by OBS Type & Path and Assignment Total.
  • Project Budget vs Planned vs Actual by Month report provides the Project Managers a single place to view Project Budget, Planned and Actual Cost for multiple projects. Project Managers can use this view to compare various costs for that project in a particular month. User can further narrow their search by OBS Type & Path, Is Project Active?, Fiscal Month Start Date, Investment Manager and Investment Name.
  • Time by Investment report displays time spent by resources on investment(s). User can view only the investments that he has access to view. Information can be drilled to Yearly, Quarterly or Monthly level. User can further narrow their search by OBS Type & Path, Investment Name, Month Start Date and Is Project Active?.
  • This paper will help you launch a PMO—or facelift the one you’ve got—by making sure your PMO charter can handle strategic heavy lifting. It covers everything from getting stakeholder buy-in to achieving successful adoption throughout your organization. This White Paper is downloaded from the Rego Consulting site. You will be asked to provide your email address and current ppm tool.  - http://info.regoconsulting.com/launch-pmo-whitepaper ** No Download - Do not Add to Cart **
  • A Quick Reference Card to assist in the creation of a Program.
  • 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.
  • All Assignments report provides the Managers a single place to view all the assignments associated with a project(s).  User can view only the investments that he has access to. This report also displays ETC, Actuals, Total Effort, Days Old (Elapsed days between Task Finish Date and Today's Date), Days Late (Elapsed days between Task Finish date and Task Baseline Finish date) associated with the task. You can further narrow your search by OBS Type & Path,  Resource Name , Project Manager, Project Name,  Project ID,  Is project Active?, Assignment Start Date, Assignment Finish Date, Assignment Status and Task Status.
  • 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.
  • Late Tasks with Assignments report displays the list of all Tasks (with their Total ETC Hours) 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 tasks across multiple projects without going into each project individually. This report displays Project Name, Project Manager, Task Name, Task Status, Task Start Date, Task Finish Date,  Days Old (Elapsed days between Task Finish Date and Today's Date), Days Late (Elapsed days between Task Finish date and Task Baseline Finish date). User can further narrow their search by Task Name,  Task Status,  Project ID, Project Name, Project Manager, Is Milestone?, Is late?, Task Start Date, Task Finish Date and  Is Template?. User can use exact dates or relative dates for  Task Start Date and  Task Finish Date filter parameters.
  • Time by Task report displays monthly time logged to Tasks for all filtered investments. It also displays total Actual hours associated with a task. User can further narrow their search by OBS Type & Path, Charge Code, Project Name, Task Name, Task Charge Code, Task Status and Month End Date. User can use exact dates or relative dates for Month End Date filter parameters.
  • 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:
    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)
    Pre-conditions:
    • 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
    This notification will assist PMs to maintain their projects and keep them current.
  • 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 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, 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 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:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) AND project manager (PM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM or PM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field.  This process can be modified to grant project edit rights to any user within a project field.
  • Course Description:   How do companies track stage gates within Clarity PPM? This session will review some best practices for tracking, monitoring, and approving stage gates within Clarity PPM. We will also discuss pros and cons of various options to help you select the best method for your company.
  • Course Description:   Do you want to analyze the cost and utilization of Agile development resources? Do you struggle to integrate financial information with work execution information from Agile tools such as Rally Software®, Jira, or VersionOne? This session explores reporting and dashboarding approaches to provide technology leaders with KPIs and trends for Agile execution, along with views that relate Agile team activity with cost and delivery.
  • 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.
  • Course Description:  Does your company have Office 365, but you’re not sure what it can do for you? This session will cover what Office 365 is, including insights into how Office 365 can help your teams work faster and smarter.
  • Course Description:   Are your project teams using SharePoint effectively and getting the most value out of it? Is document management a daily struggle? Learn how to use SharePoint with Clarity PPM to seamlessly improve collaboration and team productivity.
  • 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 portlet displays the monthly allocation per resource. The PM can view by the RM or the resource to get the data for monthly resource allocations. The table below describes the available filter fields in the portlet.
    Column Label Description
    Work Effort Manager Manager of the Investment the Work Effort is on
    Work Effort Active Active status of the Investment the Work Effort is on
    Resource Resource’s Name
    Internal Resource ID Resource’s ID
    Zero Allocation Show Allocations that equal zero
    Open for Time Entry Is the Resource Open for Time Entry
    Resource Active Resource’s Active status
    Role Resource’s Primary Role
    OBS Unit Resource’s OBS
    Start Allocation Start Time to filter by
    End Allocation Finish time to filter by
       
  • This portlet displays the monthly allocation per resource. The PM can view by the RM or the resource to get the data for monthly resource allocations. The table below describes the available filter fields in the portlet.
    Column Label Description
    Work Effort Manager Manager of the Investment the Work Effort is on
    Work Effort Active Active status of the Investment the Work Effort is on
    Resource Resource’s Name
    Internal Resource ID Resource’s ID
    Zero Allocation Show Allocations that equal zero
    Open for Time Entry Is the Resource Open for Time Entry
    Resource Active Resource’s Active status
    Role Resource’s Primary Role
    OBS Unit Resource’s OBS
    Start Allocation Start Time to filter by
    End Allocation Finish time to filter by
       
  • Part of the Business Transformation collection, this bar-chart portlet displays number of investments per stage. This provides a holistic overview of where the projects are within the organization.
Go to Top