• Published
  • Project Setup & Modifications: Key Relationships


    This page covers:

    Related pages:


    Project Setup & Modifications: Overview

    The Project object is the “glue” that holds together most other data in Amp Impact. It holds the high-level details of a project or an initiative, which is a set of activities performed to achieve certain objectives. Organizations often need to segment data on the Project object. There are several related records that are created when a project is initially set up, including Reporting Periods, Geographic Areas, Thematic Areas, Organization Roles, and Project Roles.

    Project Setup & Modifications: Data Model

    Below is the Project Setup data model subset.

    Project Setup & Modifications: Summary of Key Relationships

    There are a couple of relationships that are foundational to the overall use of Amp Impact:

    • Geographic Area through Project Geographic Area (junction object): This relationship allows organizations to relate specific Geographic Area records from the catalog of geographic areas to their Amp Impact Project.

    • Thematic Area through Project Thematic Area (junction object): This relationship allows organizations to relate specific Thematic Area records from a catalog of thematic areas (themes or strategic initiatives) to their Amp Impact Project.

    • Reporting Period: This relationship allows organizations to set a period of time for which a project's targets and results will be reported.

    • Project Role: This relationship allows organizations to associate different types of Contacts to their Project/s in Amp Impact.

    • Organization Role: This relationship allows organizations to associate Accounts/Organizations with their Project/s in Amp Impact.

    • Modification: This relationship allows organizations to track modifications to a particular project.

    Here is a summary of these relationships:

    Amp Object Label

    Amp Object API name

    Abbrv

    Object Description

    Sample Use

    Also Sometimes Called

    Key relationships (Amp object's relationship in parentheses)

    Amp Object Label

    Amp Object API name

    Abbrv

    Object Description

    Sample Use

    Also Sometimes Called

    Key relationships (Amp object's relationship in parentheses)

    Project

    ampi__Project__c

     

    The Project object holds the high-level details of a project (i.e. a set of activities performed to achieve certain objectives). This object is the 'glue' that holds together most other Amp data. The Project Object often has record types configured on it (eg to distinguish between Programs and Projects or Proposals and Projects). Project records can also be used to track a pipeline of proposals or planned projects/programs.

    An international education NGO has a portfolio-level program called "Education for All" implemented in 13 countries.
    A field office for the education NGO in Tanzania runs a project called "Education for All- Tanzania."
    The Hello Hygiene foundation manages a $1m grant to an organization named WASH-Aid for an initiative called "WASH-Aid Hygiene Promotion"

    Program(me), Grant, Investment

    Master-Detail (Project is 'Master' object): Allocation, Budget, Disbursement, Organization Role Project Geographic Area, Project Thematic Area
    Parent-child (Project is 'Parent' object): Framework, Framework Objective, Implementation Plan, Modification, Project Indicator, Project Role, Reporting Period, Risk Register, Story
    Project (self-lookup)

    Geographic Area

    ampi__Geographical_Area__c

    GA

    The Geographic Area object stores a list of geographies that can be assigned to projects to indicate where the project is being implemented. Depending on the client, this may be a list of global geographies (regions, countries) or at a more granular level (states, provinces, districts, or even villages). Geographic areas can also have a parent-child hierarchy.

    An international NGO works in 120 countries, which they group into 7 regions for management and reporting purposes. The Geographic Areas object contains records for each of the regions and countries, and includes a self-lookup so that countries can be linked to their 'parent' region.

    Area, Location

    Geographic Area (self-lookup)
    Project Geographic Area (child in lookup)

    Project Geographic Area

    ampi__Project_Geographic_Area__c

    PGA

    The Project Geographic Area object captures the geographic units (regions, countries, etc.) where a project is being implemented, for the purpose of using Amp Impact's indicators, Set Targets, and Add Results functionality. It is necessary to create Project Geographic Areas only at the level for which targets and results need to be entered. For example, if a project works in 6 countries across 2 regions but targets/results are entered at the country level only, the Project Geographic Area records need to be created only for the countries.

    The "Education for All" project is being implemented in 6 countries and needs to set targets / add results data for performance indicators at the country level, so the project manager creates 6 Project Geographic Area records (one for each country of implementation).

    Program(me) Geographic Areas, Grant Geographic Areas, Investment Geographic Areas

    Project (detail in MD relationship)
    Geographic Area (detail in MD relationship relationship)
    Project Indicator Geographic Area (child in lookup)

    Thematic Area

    ampi__Thematic_Area__c

    TA

    "Thematic Area" is a flexible term that can be defined according to how an organization categorizes their Projects/Grants/etc and/or their Indicators. This is often according to different sectors that the organization works in (for example, Education, Health, WASH, etc.). Sometimes the Thematic Area object is also used to define cross-cutting themes or strategic initiatives (for example: Gender Equality; Reduce Maternal Mortality).
    Thematic Areas can be nested in a parent-child hierarchy. It is also possible to define different types of Thematic Areas (for example, Sectors and Strategies) and differentiate them using the 'Type' field on the object.

    An international NGO categorizes its work into 5 sectors: Education, Health, Water and Sanitation, Youth Development, and Humanitarian Response. The organization also has three cross-cutting global themes: Gender Equality, Sustainability, and Capacity Building. One Thematic Area is created for these sectors and cross-cutting themes. These Thematic Areas can then be affiliated with Indicators (see Indicator Thematic Area object in this list) or Projects/Grants/etc. (see Project Thematic Area object in this list).

    Themes, Sectors, Strategies, Outcome Areas, Strategic Initiatives

    Project (detail in MD relationship)
    Thematic Area (detail in MD relationship)
    Indicator Thematic Area (child in lookup)
    Project Indicator Thematic Area (child in lookup)

    Project Thematic Area

    ampi__Project_Thematic_Area__c

    PTA

    Junction object between Thematic Area and Project

    The Education for All project works in the Education sector and also in the cross-cutting theme of Gender Equality. Two Project Thematic Area records are created to affiliate the Education and Gender Equality Thematic Areas with the project.

    *Note: In Amp Impact, if a Catalog Indicator is affiliated with a Thematic Area and this relationship is marked as 'Required,' then when a Project is afffiliated with the same Thematic Area through creation of a PTA record, a project indicator will automatically be created based off of the catalog indicator. For example: The catalog indicator "% graduation rate" is marked as a required indicator for the Education thematic area. When the "Education for All" project is affiliated with the Education thematic area, the indicator for "% graduation rate" will then be automatically assigned to the project.

    Project Themes, Project Sectors

    Project (detail in MD relationship)
    Thematic Area (detail in MD relationship)

    Project Role

    ampi__Project_Role__c

     None

    Project role is a junction object between the Contact and Project objects and allows users to affiliate internal or external contacts with their projects. This allows project managers to maintain a record of Contacts who are currently working on or have previously worked on/been associated with the project.

    A Project Role record is created for the Contact Jane Smith on the Education for All project to show that she is the current Project Manager.

    Grant Role, Investment Role

    Contact (detail in MD relationship)
    Project (child in lookup)

    Organization Role

    ampi__Organization_Role__c

     None

    Organization role is a junction object between the Account (Organization) and Project objects and allows users to affiliate accounts with their projects. This allows project managers to maintain a record of the Organizations that are currently working on or have previously worked on/been associated with a project.

    An Organization Role record is created for the Education for All project for an Organization called "Nairobi Teachers' Association" to show that they are an Implementing Partner on the project.

    Partner Organzation, Donor, Institution Role

    Account (detail in MD relationship)
    Project (detail in MD relationship)

    Reporting Period

    ampi__Reporting_Period__c

    RP

    Reporting periods represent time periods during a project. The object is commonly used to manage grant reports or progress reports (including narrative, results, financials, and files). It is an important object for Indicator Management and also for Financial Management (every Financial must link to an RP).

    The 'One for Change' project has 3 annual reporting periods (2019, 2020, 2021) and a Life of Project reporting period.

    Period, Report, Grant Report, Progress Report, Time Period

    Project (child in lookup)
    Project Indicator (many-to-many)
    Financial (parent in MD)
    Story (parent in lookup)

    Modification

    ampi_Modification__c

     

    The Modification object tracks major change requests or amendments related to project. These may be initiated by a grantee, partner, or grantmaker. Common modification types are Costed Extensions, No-Cost Extensions, and Budget Reallocation.

    A grantee requests a no-cost extension to have more time to complete the planned activities of the project.

    Change Request, Amendment, Extension

    Project (child in lookup)