- Change Requests
- Cost Trend
- Cost
- Effort Trend
- Effort
- Hierarchy Summary
- Investment Drill Thru
- Investment Gantt
- Issue Summary
- Milestones
- Risk Summary
- Staff
- Status Report Summary
- Tasks
-
Summarize an ad hoc list of investments or leverage your defined hierarchies to visualize and evaluate the performance of your portfolios, including financial data analysis. Report Views include: -
Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams. Report Views include:- Allocation Discrepancies
- Resource Detail
- Resource Skills
- Resource Summary
- Resource Tasks
- Staffing Allocations
- Staffing ETC
-
Plan your future work by comparing different scenarios, including in-flight work, and determine the best course of action for your organization. Report Views include:- Roadmap Details
- Resource Investment Demand
- Roadmap Financials
- Roadmap Investment Gantt
- Roadmap Item Gantt
- Roadmap Overview – Default Scenarios
- Roadmap Overview – Single Roadmap Selection
- Scenario Comparison
-
Gain a financial view of your investments by comparing actuals to planned cost and planned benefit. Report views include:- Financial Summary
- Planned Benefit vs Actual Cost
- Actuals vs Planned Costs
-
Master your pipeline as you prioritize, visualize, and analyze ideas, assess their feasibility, and track progress from inception to execution. Report Views include:- Idea Bubble
- Idea Details
- Idea Funnel
- Idea Gantt
- Idea Overview
- Idea Staff and Effort
- Idea Status
- Idea To Dos
-
Spot opportunities to improve timesheet accuracy and resource allocations by assessing timesheet compliance and allocation. Report Views include:- Allocation Variance
- Capex vs Opex
- Hours Detail
- Resource Dtails
- Single Manager Drill Down
- Single Resource Drill Down
- Timesheet Detail
- Timesheet Summary
- Unapproved Timesheets
-
Gain an overview of program-level performance, track program milestones, and assess overall program health. Report Views include:- Change Requests
- Program Costs Trend
- Program Costs
- Program Drill Thru
- Program Effort
- Program Gantt
- Program Issues
- Program Milestones
- Program Risks
- Program Staff
- Program Status Reports
- Program Summary
- Program Tasks
-
Make sure project deliverables are completed on time by tracking work progress and monitoring task assignments. Report Views include:- Work Details
- Work Overview
- Work Risk Issue and Change
-
The Power Filter Sync functionality allows users to define rules for syncing investments to Roadmaps or Hierarchies on a scheduled (and on-demand in Roadmaps only) basis. Users may choose one or more saved views from investments that are allowed on the Roadmap/Hierarchy to define the list of investments they want that Roadmap/Hierarchy to contain. If the option to Keep Synced with Power Filter is set to Yes, then each time the process runs, the Investments returned by the saved views will be added to the Roadmap/Hierarchy if they don’t exist there already, and any investment not found in the saved views will be removed. -
Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams. Report Views include: • Over Allocation • By Project • By People • Project Resource Details • No Allocations by Project • No Allocations by People The main .rpt file will access data through the Data Warehouse. -
Actuals & ETC by Resource Assignment report provides project managers a single place to view Actuals and ETC associated with resources across multiple Tasks and Projects. It displays the following: Actual and ETC Hours by Start Date: Stacked Column chart that displays the total Actual hours and ETC hours per month of fiscal period. Grey color indicates Actuals and Purple indicates ETC hours during that month. Grid: Displays Investment name, Task, Assigned resource ETC and Actual hours per month of fiscal period. It also displays aggregated column and row totals for Actuals and ETC hours. You can further narrow your search by OBS Type, OBS Path & Start Date range. -
*Note: MUX Migrator v2.0 will only work on Clarity versions 16.1.0 and higher. The Migration Tool for Modern UX Components provides the ability to migrate Blueprints, Views, and Field Level Security between environments. Previously, the promotion of these components needed to be done manually. This functionality, to be utilized by an administrator, is available under the Custom Objects Area of Clarity. Source to Target Approach The user would first create an ‘MUX Migrator’ instance and populate the associated details. Once ready, they will use the “Populate Stage Content” action which will run a workflow in the background to populate a Staging Table with Source Environments content. (Blueprints, Views, and Field Level Security)Installation files are not provided with the download. While the MUX Migration Tool is free, it does require some time by Rego Technical Staff to install. Approximately 4 hours is required. If you are current Rego Customer, this time can be applied against a current project if you choose, or against an Ad Hoc SOW/PO you have in place with us. Please reach out to your friendly Rego Account Director to arrange to have the tool installed. Installation files are not provided with this download. They will be installed by our staff. If you are currently not a Rego client, we invite you to reach out to us at info@regoconsulting.com and we can arrange to set up an Ad Hoc bucket of hours for this install and any future work we can do for you. After a successful populate, they would navigate to the “MUX Configuration” module where they can decide on what content they want to migrate between environments. They can select one to many components they wish to migrate. Once the “MUX Configuration” sub-object is populated, the user can navigate back to the “Properties” module. Once a password is populated, the user can use the Actions drop-down to run the “Migrate Content to Environment” workflow. This will run a process that will migrate the content from the source environment to the target environment. JSON Approach The user would first create an ‘MUX Migrator’ instance and populate the associated details. They would navigate to the “MUX Configuration” module where they can decide on what content they want to migrate between environments. They can select one to many components they wish to migrate. Once the “MUX Configuration” sub-object is populated, the user can navigate back to the “Properties” module. The user can use the Actions drop-down to run the “Export JSON” workflow. This will run a process that will generate a .txt file located in the “JSON File” attribute. That file can be downloaded from the Source Environment. The user can then login to the Target Environment. The user would first create an ‘MUX Migrator’ instance and populate the associated details. Once the ‘MUX Migrator’ instance is created, they can upload the JSON File that was downloaded from the Source Environment. The user can use the Actions drop-down to run the “Import JSON” workflow. This will run a process that will generate read the file located in the “JSON File” attribute and load the configuration into the Target Environment. View Administration The user would first create an ‘MUX Migrator’ instance and populate the associated details. They would navigate to the “MUX View Administration” module where they can decide on what views they would like to update the creator of. They can also reset the “default” view displayed when logged in for a resource(s), Security Group(s), or Resource OBS Node(s). Prerequisites - The user will create the migrator instances/run the processes in the Target Environment they wish to migrate content to (E.g., Run this in PROD to migrate the content from a lower environment to PROD)
- Any attributes that are part of the Blueprints, Views, or Field Level Security must exist in the target environment.
- The user that is utilizing the content must have the following security rights associated to their account.
- XOG rights to all the associated objects
- View/edit security rights to the MUX Migrator Object and MUX Migrator Content Object
- oView rights to the MUX Migrator Staging Table Object
- API-Access
- Process Start or Process AutoStart – All
