Can I have two risk assessment methodologies for the same entity? How to do so?

ChuanYanF
Tera Guru

Dear experts,

 

I am facing a problem when defining a risk assessment methodology for my entity. Currently my client wants to have two different risk assessment methodologies for the same entity. As far as I know, currently the risk assessment methodology is read-only and will populate based on the Entity Class. How can I enable them to choose the risk assessment methodology when they are assessing a risk themselves rather than just a read-only field?

1 REPLY 1

HenkHeath
Tera Expert

Hello @ChuanYanF 

 

Although the default RAM is selected for the entity class, you may assess the risk using any number of RAMs in Advanced Risk.

 

As an example;

Entity Class - Business Units  (default RAM = Enterprise Risk)

Entity = Workshop  (created from the Entity Type Business Unit, and Class Business  Unit)

Risk + Risk Statement = Risk of Fire

 

Requirement - Assess the workshop for risks using RAM = OHS Risk assessment 

 

When you select Assess, the Risk Assessment instance will automatically create a risk assessment using the default Enterprise Risk.  This is the easy automated triggering of a risk assessment.

 

What the OOTB also provides is Scoping or Scheduler under you Risk  Assessment Planning

Navigate to Risk Workspace > List > Risk assessment planning >   

and then select either Risk assessments or Scoped entities

 

Follow the playbook in either of these instances.  They are similar.  One focusses on the entity and all it's risks and the other focusses on the risks and all entities involved.  

 

In both of these you will select the methodology

HenkHeath_0-1744785908918.png

 

Now select your secondary RAM, do the assignment & frequency and initiate the assessments.

 

you will then end up with a scenario where for 1 entity with a specific risk, it has been assessed using 2 different methodologies. (below image is just an example to illustrate what it would look like )

HenkHeath_1-1744786407243.png

 

I hope this helps