Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page covers:

Table of Contents
minLevel1
maxLevel3
stylecircle

Frameworks Data Model

Image RemovedImage Added

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

Amp Object Label

Amp Object API name

Abbreviation

Object Description

Sample Use

Also Sometimes Called

Key relationships (Amp object's relationship in parentheses)

Sometimes connects to

Objective

ampi_Catalog_Objective__c

 None

The Objective object is used to store Impact, Outcome, Output, etc statements that are used in Logframes. It contains a catalog of the objectives which can be added to different Projects and Frameworks. To facilitate consistent structures in analytics, it also contains custom Project-specific Objectives. This object enables users building Frameworks to add predefined Objectives to a Framework or to instead of only creating custom objectives for each project. Most Objectives will have a Level (eg Impact, Outcome, Output; custom levels can be defined). Objectives can be nested under Parent Objectives (eg Outputs under an Outcome).

A grantmaker requires grantees to pursue an Outcome "Improve living standards of women". The Admin has created this and 5 other standard Objectives as records in the Objective catalog. Applicants or Grantees can add this outcome as an Objective when setting up a Framework for a Project.

Result, Result Statement, Outcome, Output, Goal, Strategic Priority

Objective (self-lookup)

Indicator (Objective is usually the Parent if a many-to-one relationship exists between Indicators and Objectives)
Thematic Area (lookup or many-to-many)

Framework

ampi__xx_Framework__c

 None

The Framework object groups together Framework Objectives in a Logframe or Logic Model for a Project/Grant/Programme. It can contain a mix of standard and custom Framework Objectives and will sometimes go through an Approval Process. A Project can have one or more Frameworks (eg if a Funder requires reporting against specific Outcome or Output Statements that differ from the organizational Framework), though typically Projects will have just one Framework.

FCDO's Gender Equity Framework is related to the project and contains the FCDO Goals, Outcomes, and Outputs that the Project aims to achieve.

Result Framework, Logframe, Result Matrix, Logic Model, Theory of Change

Framework Objective (Framework is parent in a lookup)
Project (Framework is child in a lookup)

Budget
Implementation Plan

Framework Objective

ampi__Objective__c

 None

The Framework Objective object contains a statement of something a Project aims to achieve. Framework Objectives have a parent-child hierarchy, allowing users to group Outputs under Outcomes under Strategic Priorities (for example). Framework Objectives can be specific to one project, can be added from a catalog of standard Objectives, or can be copied from another Framework

The Education For All project has three outcomes: Improve adolescent literacy, Improve adolescent numeracy, and Improve adolescent social-emotional learning. Each of these are Framework objectives within the Project and each have Project Indicators connected to them.

Result, Result Statement, Outcome, Output, Goal, Strategic Priority (in the context of a Project, Grant, or Program)

Framework (FO is child in a lookup)
Project (FO is child in a lookup)
Objective (FO is child in a lookup)
Project Indicator (many-to-many via the PIO object)
Activity (FO is parent in a lookup)
Risk (FO is parent in a lookup)

Financials (FO as parent in a lookup)
Assignments (FO as parent, if assigning resources at Output level)

Project Indicator Objective

ampi_Project_Indicator_Objective__c

PIO

Project Indicator Objective is a junction object which connects Project Indicators and Framework Objectives.

Indicator " # of women trained" and "# of women employed" are related to Project Objective "Improve living standards of women"