Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Functionality to identify the risks to a project/grant, develop mitigation strategies for risks, conduct periodic assessments of risks, and track risk status.

The table below categorizes the Risk Management functional area and includes a description, the sample uses, and other ways we see it implemented.

This table could be a helpful starting point to understand design principles for the Risk Management functional area in Amp Impact.


Functional Area

Amp Object Label

Amp Object API name

Abbrv

Object Description

Sample Use

Also Sometimes Called

Key relationships (Amp object's relationship in parentheses)

Sometimes connects to

Risk Management

Risk

ampi__Risk__c

 

A Risk can be an issue that may disrupt a project or activity, or an incident/issue that has already occurred. The Risk record holds details such as the category, level, and mitigation strategy for the risk. A Risk can be related to a specific Activity or to a Risk Register (collection of risks) that is associated to a Project.

Examples of risks: Election Protest, Climate Change, Staff Turnover, Economic Recession

Issues, Incidents, Events

Risk Register (child in lookup)
Activity (child in lookup)

 

Risk Management

Risk Register

ampi__Risk_Register__c

 

A Risk Register record serves to group Risks (child records) together. Risk Registers can be related to a specific Project or to a different object through a custom lookup.

Education for All has separate risk registers for its Tanzania Project and Kenya Project and an operational risk register for the whole organization.

 

Risk (parent)
Project (child in lookup)

 

Risk Management

Risk Assessment

ampi__Risk_Assessment__c

 

Object to store details of periodic evaluation of Risks. Can be related to a project Reporting Period and also assigned to a Contact.

The Education for All Tanzania project reviews the Risks in its Risk Register on an annual basis to determine which risks are closed, which ones need a mitigation strategy, etc.

 

Risk (child in lookup)
Reporting Period (child in lookup)
Contact (child in lookup)

 

Risk Management

Risk Action

ampi__xx_Risk_Action__c

 

Object to store details of mitigation actions for potential risks or response actions for risks that have occured. Risk Actions can be assigned to Contacts.

One of Educations for All Tanzania's identified risks is Election Protest. An associated Risk Action describes a mitigation plan that will take effect if this risk occurs.

Risk Treatments, Risk Mitigation Measures

Risk (child in lookup)
Contact (child in lookup)

 

Risk Management

Risk Relationship

ampi__xx_Risk_Relationship__c

 

Junction object that allows Risks to be affiliated with each other in a many-to-many relationship. Also allows a many-to-many relationship between Risks and Activitiies or Risks and Framework Objectives.

For the Education for All project, there is a Risk Relationship between the "Economic Recession" risk and the "Election Protest" risk where Economic Recession is identified as a contributing factor to Election Protest.

 

Risk (child in lookup x2)
Activity (child in lookup)
Framework Objective (child in lookup)

 

Risk Management

Risk Cause

ampi__xx_Risk_Cause__c

 

This object is used to capture details about potential or actual causes for risks.

A Risk Cause for the "Election Protest" risk could be "Opposing party loses election."

 

Risk (child in lookup)

 

  • No labels