• Published
  • Workplanning & Resource Planning: Key Relationships


    This page covers:

    Related pages:


    Workplanning & Resource Planning: Overview

    Workplanning refers to creating an implementation plan for a project, specifying the activities that will be carried out or milestones to be reached and the timeline for these activities/milestones, and then following up to indicate the completion rate for activities. Resource planning is the process of articulating needs for staff, goods, and/or services for a project's activities.

    Workplanning & Resource Planning: Data Mote

    Below is the Workplanning & Resource Planning data model subset:

    Workplanning & Resource Planning: Summary of Key Relationships

    There are eight key relationships that are foundational to Workplanning and Resource Planning:

    • Implementation Plan: This is the detailed workplan for a project. From an Implementation Plan record, users are able to download an Excel template with reference values for picklists and lookups that can be used for Activities. A Project can have multiple Implementation Plan records.

    • Activity: An Activity is a set task performed under an Implementation Plan. Activities can be set up in a work breakdown structure and viewed in a Gantt Chart.

    • Activity Dependency: This relationship enables organizations to capture relationships between activities.

    • Position: This relationship enables organizations to monitor open and/or required job positions to implement projects successfully.

    • Role: This relationship enables organizations to keep information relating to the types of responsibilities or jobs (roles) and the costs that go hand in hand with these roles.

    • Good/Service: This relationship enables organizations to keep a collection of goods and services.

    • Assignment: This relationship enables organizations to associate Positions or Roles to Activities.

    • Procurement Requirement: This relationship enables organizations to associate Goods/Services with Activities.

    Here is a summary of these relationships:

    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

    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

    Implementation Plan

    ampi__Implementation_Plan__c

    IP

    An Implementation Plan is a detailed work plan for a Project, usually corresponding to a specific time period or category of activities for the project. The Implementation Plan record stores details about the work plan (description, timeline, etc.) and then specific Activities (on the Activity object) can be created and linked to the Implementation Plan.

    Implementation Plans can also be created for Frameworks.

    The Education for All project is a 4-year project. The Project Manager creates an Implementation Plan for each year of the project and then using the Activities object, details the specific activities and milestones for each year of the project.

    Work Plan

    Project (child in lookup)
    Framework (child in lookup)
    Activity (parent)

     

    Activity

    ampi__Activity__c

     None

    An Activity is a set task performed under an Implementation Plan. The Activity record constains all the details of the activity, including start and dates and percent completion.

    Activities can be nested under each other in a parent-child hierarchy. They can also be linked to specific Project Objectives, Project Indicators, and Financial line items within a project Budget. They can be assigned to Contacts directly through the Contact lookup field or through the Activity Assignment object.

    After creating an Implementation Plan for year 1 of the Education for All project, the project manager creates Activity records for the specific activities and milestones that will happen in year one. Examples: Create teacher training curriculum; Carry out teacher training in district A; Recruit volunteers.

    Milestones, Deliverables, Planning Elements, Actions

    Implementation Plan (child in lookup)
    Project Indicator (child in lookup)
    Framework Objective (child in lookup)
    Contact (child in lookup)
    Financial (parent)
    Activity Dependency (parent)

     

    Activity Dependency

    ampi_xx_Activity_Dependency__c

      None

    An Activity Dependency captures a relationship between two Activities when the activities need one. Activity needs to 1) Start after another has started, 2) finish after another has finished or 3) start after another has finished, or (4) finish after another has started. This dependency is displayed on the Activities Gantt chart (Lightning Web Component) as an arrow connecting the two activities.

    In the Education for All Year 1 Implementation plan, the activity 'Create teacher training curriculum' must finish before 'Carry out teacher training' can begin. These two activities are connected via a line in the Gantt chart.

     

    Activity (child in lookup)
    Financial (child in lookup)

     

    Position

    ampi_xx_Position__c

      None

    The Position object is used to track the job positions available (or required) to successfully implement projects. Users can enter the description, qualifications, start date, and cost details for each Position. Positions can be assigned to Activities through the Assignment object.
    Positions differ from Roles in that a Position is an "instance" of a Role; a Role is a general description of a duty, while a Position is filled by a specific person (Contact).

    An HR Admin for Hello Hygiene creates a Role for "Water Resources Specialist" that can be used to create positions for many projects across different locations. A specific "Water Resources Specialist" Position is created to support the WASH-Aid project in El Salvador. When a staff member is hired for this Position the Position will be linked to the Staff member's Contact record.

    Post, Resource

    Assignment (parent)
    Contact (child in lookup)
    Account (child in lookup)
    Role (child in lookup)

    Framework Objective (many-to-many via Assignment)

    Role

    ampi_xx_Role__c

      None

    The Role object stores details about types of responsibilities or jobs (Roles) and the costs associated with these roles.
    A Role is different from a Position in that it is a type or grouping of duty not specific to one project, department, or location. A Position is an 'instance' of a Role that is filled by a specific person (Contact.

    An HR Admin for Hello Hygiene creates a Role for "Water Resources Specialist" that can be used as a basis for creating Positions for many projects across different locations.

     

    Assignment (parent)
    Position (parent)

    Framework Objective (many-to-many via Assignment)

    Good/Service

    ampi__xx_Good_Service__c

      None

    Stores a catalog of goods and services that can be requested, planned, or tracked for Activities. Each Good/Service can have an expected cost, preferred procurement method, and other details.

    Goods: Laptops, Mobile phones, Cars
    Services: Evaluations, Office cleaning

     

    Procurement Requirement (parent)

     

    Assignment

    ampi__xx_Assignment__c

      None

    Junction object used to affiliate Positions or Roles to Activities, essentially showing the Positions/Roles that are necessary to successfully implement the Activity. Includes fields to track the estimated cost and effort required for the assignment.

    The "Water Resources Specialist" Position for a WASH-Aid project in El Salvador is associated to the Activity "Conduct well water quality assessment" through an Assignment record, and estimated effort for this assignment is set at 30%.

     

    Position (child in lookup)
    Role (child in lookup)
    Activity (child in lookup)

     

    Procurement Requirement

    ampi__xx_Procurement_Requirement__c

      None

    Junction object used to affiliate Goods/Services with Activities, essentially showing the goods or services required to successfully implement project activities. Includes fields to track the quantity required, due date, etc.

    "Digital Thermometer" is a Good/Service that is affiliated to the Activity "Conduct well water quality assesment" through a Procurement Request record.

    Activity Goods/Services

    Good/Service (child in lookup)
    Activity (child in lookup)