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

« Previous Version 14 Next »


This page covers:

Related pages:


🔎 Workplanning & Resource Planning in Amp Impact

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. Activities can be set up in a work breakdown structure and viewed in a Gantt Chart. Resource planning is the process of articulating needs for staff, goods, and/or services for a project's activities.

Workplanning & Resource Planning in Amp Impact Feature Demo Video

🔎 Workplanning & Resource Planning Setup Structure

Implementation Plan

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.

Activities

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.

Positions, Roles, & Assignments

Roles store the details about the types of responsibilities that would need to be done through the course of a project, including the associated costs.

Positions allow organizations to track available or required positions that need to be filled to complete specific project activities.

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).

Assignments are used to affiliate Positions or Roles with Activities, essentially showing the Positions/Roles that are necessary to successfully implement the Activity

Goods, Services, & Procurement Requirements

Goods or Services can be stored in a catalog that can be requested, planned, or tracked for Activities. Each Good/Service can have an expected cost, preferred procurement method, and other details.

Procurement Requirements are 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.


  • No labels