Hi,
Our compliance function is looking to build a set of processes with sub-processes in Eramba.
I see the possibility to add a custom integer field that points to the parent process, but before I do that I wanted to inquire if there are any other ways or perhaps some best practices around implementing a custom field for this?
Thanks,
Patrik
the “Complaince Managmeent” use case, has no relation with BUs module at all. Please read the documentation on how compliance is implemented in eramba.
I’m not quite sure what you mean? We are implementing Eramba for, among other things, DORA which requires us to keep track of business units, their related processes and any assets supporting these processes.
My question regards if someone has setup their instance to allow configuring nested processes?
your initial post mentions “our compliance team” (not a dora requirement) as a generic need, in eramba software modules are grouped in “use cases” (because most use cases need a multitude of modules).
if your “compliance” team wants to use eramba for “compliance” then the use case does not relate at all with business units (see documentation).
what you are working on is a specific requirement of a specific compliance package as i now understand from your update.
eramba has this relationship now (review Risk Management use case) with the exception that “processes” link to “business Units”, not to “assets” (bu’s link to assets). we are thinking on updating a direct relationship in between process and assets, but is not %100 sure we’ll do it.
ok, a nested process is not what you mention on the parragraph above…this piece is not clear to me. but is not possible in eramba and i’m %100 is not going to exist something like that, we want two levels and basta (bu + process).
just out of curiousity, where in DORA you read the need of documenting a process and their sub-processes? is not something i’ve seen so far. maybe oyu need this for some other reason.
I just saw your post on using Eramba for Dora compliance and what you cover in in there is what I was going to write in my reply: we need to, among other things, document the change management process and document the post ICT-related incident reviews process. There are other processes, too. I believe Eramba has the features needed support to help us there.
Regarding sub-processes, that is not a requirement, no. It has just been a topic of discussion here to see if and how we can break complex processes down into smaller units if we decide to go down that route.
