Skip to Main Content
ARIS - SHARE YOUR IDEAS
How can we make ARIS better?
ADD A NEW IDEA

ARIS Extension: Risk & Compliance

Showing 58 of 1384

Survey management - reviewer does not see issues created by interviewee

the interviewee can create issues for the questionnaire and/or questions within the questionnaire.In the current view that the reviewer gets, she/he can't see that issues have been created. As a consequence, duplicate issues might be created.
Koen Maes 5 days ago in ARIS Extension: Risk & Compliance 0 Open for voting

ARCM hierarchies: Include product tree

Hi,With the current tsunami of new regulations there are more and more regulations that related to specific product categories and products (example: product safety requirements, regulation prEN 18031-1:2023).In the modelling we can document the r...
Koen Maes 7 days ago in ARIS Extension: Risk & Compliance 0 Open for voting

Synchronization to deactivate risks in ARCM

To deactivate content in standard, the synchronization of the whole database is necessary. Deactivation of a risk (e.g.) should be possible by using a seperate attribute of this object. Db wide sync should be avoided as many other parts could be a...
Benjamin Heim 13 days ago in ARIS Extension: Risk & Compliance 0 Open for voting

Data Migration

As we migrate our risks into ARIS Connect we also would like to a initial migration of the risk assessments. Assessment, assessment date, comment should be contained. Could show the technical user and comment that it's inital data migration.
Benjamin Heim 13 days ago in ARIS Extension: Risk & Compliance 0 Open for voting

Context based issue types

We would like to use issues for different topics. Therefor it is necessary to define the attributes as well as the permissions based on the context in which the issue is opened. A issue opened from a risk has a different content set as an issue re...
Benjamin Heim 13 days ago in ARIS Extension: Risk & Compliance 0 Open for voting

risk hierarchy

In design it's possible to define a hierarchy of risks (eg. risk X consits of risk X.1 and risk X.2). ARCM does not support this concept.If it would be added, the principle is that a risk assessment would be done only on the lower level risks and ...
Koen Maes about 1 month ago in ARIS Extension: Risk & Compliance 0 Open for voting

Relevant impact type(s) for a risk

In today's implementation, for any risk the assessment will always show all impact types.Approach at customers is that certain impact types are relevant only for some risks.So,it should be possible to define for a risk (or risk category) which imp...
Koen Maes about 1 month ago in ARIS Extension: Risk & Compliance 0 Open for voting

Document risk appetite in ARIS & ARCM

Today there is no standard to document the risk appetite in ARIS. However, it is an important indication when managing risks.Having the ability to document this (in a standard way), would enable further reporting and analysis about the risk situat...
Koen Maes about 1 month ago in ARIS Extension: Risk & Compliance 1 Open for voting

Be able to deactivate issues in bulk by admin users

Use case is for a customer that has only the basic ARCM roll out and issues from Connect. Their users are creating issues but some issues needs to be removed/not visible and it is complicated to deactivate issues once they are already created and ...
Tanguy Petre about 1 month ago in ARIS Extension: Risk & Compliance 1 Open for voting

Synchronize issues created in ARCM with object guid from ARIS

This use case is for a customer no having ARCM issue management but the basic config for BPM-Rollout and issues creation by viewers. It would be nice to extract issues information using the dashboard queries from ARCM and to be able to have the co...
Tanguy Petre about 1 month ago in ARIS Extension: Risk & Compliance 0 Open for voting