Skip to Main Content
Customer Ideas Portal

The Customer Ideas Portal gives you the opportunity to submit Ideas for new features and functions to add to the products and vote up existing ideas that are important to your organization.

Ideas that you create are viewable by other customers, so please be mindful of the details you include in the title and description.

Your feedback is important and valuable. Thank you for taking the time to provide it!

Note: Product bugs or configuration requests that are specific to your organization should be submitted through a case on the Customer Success Portal.

ADD A NEW IDEA

ARM - Reporting, Charts and Analysis (ViewPoint, BowTie, Visualizer, Charts, Schedule Risk Analysis, Impact Analysis)

Showing 29 of 1113

Add a COUNTIF function to ViewPoint

Currently, if you want to count the rows that meet a certain criterion, you need to do an if statement that returns a 1 for true and a 0 for false. You then need to do an AggSum of these to see how many rows meet your criteria. Doing this through ...

Custom default confidence intervals

It would be great and a big help if the admin in ARMs could set default values for confidence intervals when setting the analysis options. At the moment, the user must all the time add the confidence intervals manually although they are the same i...

Enable Reporting on User Sessions and Activity (Historic Data)

To be able to report on historic user activity, i.e. who logs on to which application, when, which day / time and to be able to report on what activities they actually performed, i.e. added a new risk, closed a risk, escalated a risk etc. Original...

Record response score reduction level rather than discreet target score so that Waterfall chart is easier to manage

Managing the response target scores is challenging when actions close earlier than expected, all subsequent target score need adjusting to take account of the fact that the scores are out of sync. Example: If we close an action earlier, it breaks ...

Display the other BowTies that a BowTie control is linked to.

In order to identify whether or not a control is a critical control, we need to visualise where else that control is used and in how many other plans or BowTies it is used in. If a control is used in multiple BowTies, it can be deemed as a critica...

Release Notes for ARM To Include 'Discovered In Version' For Known Issues

This would make it simpler when we're determining whether we'd like to test a version of ARM, if we know whether our current version already suffers from an issue, or whether it is introduced in a later release

Recommended Changes to Risk Process Health standard report

Since I know SWORD is rebuilding standard reports for v2020, I wanted to make recommendations for one of their existing reports: the Risk Process Health report I wanted to recommend that SWORD work to incorporate some/all of the following metrics ...

Feature to run batches of reports with results collated, one page per report

Currently, risk impact analysis has to be run for each CLIN. It would be very useful to be able to run them as a batch to cover all CLINs in the project at the end of the month, with each report on one page but all of them collected together

Make all risk entries able to be displayed in a Bowtie format

Bowtie should be a visualisation of a risk, not a type of risk. If Causes and Consequences could be added as controlled lists in the Standard (not bowtie) view then these could be displayed in a bowtie format. It would also allow Cause and Consequ...