Assignment Mapping Grid Overview

The assignee is the person who enters progress. If you are entering schedule progress, it is activity progress. If you are entering cost progress, it is work package progress.

The Assignment Mapping grid, on the PM Compass System Settings Progress tab, identifies the assignee and approver for each update progress record type. It also identifies who is notified and who else can enter or approve progress.

Example of an Assignment Mapping Grid  

Hierarchy of data

Assignee

Approver

Project

PCA - project code 1

PCA - project code 1

Schedule Project

Schedule project code 1

Schedule project code 1

Control Account

Control Account Manager

 

Work Package

Work Package Manager

 

Activity

Code 4

Control Account Manager

In the example above, the assignee on the activity is stored in Code 4 on the activity. After the person in Code 4 enters and submits progress for the activity, the approver is notified. In the example above, the approver of the activity is the Control Account Manager.  

It is assumed that anyone from a higher level can also enter progress or approve the progress. For example, if the person in Code 4 on the activity doesn’t enter and submit progress in a timely manner, then the work package manager can enter and submit the progress. Similarly, if Code 4 on the activity is blank, the system looks for the next level up in the hierarchy to determine the assignee for the activity. In the example above, this would be the work package manager. If the Work Package Assignee was blank, the Control account manager would be assigned, and so forth.

The Project assignee and approver are required fields that serve as defaults. This ensures all activities and work packages always have an assignee.  

If you want the approver stored in Project Code 1 to approve the CAM’s progress, designate the Project Code 1 approver for all of the rows in the above grid.

Master Projects

If you are using Enter/Approve Schedule/Cost progress from the left navigation and you have selected a master project, the subproject code assignments are used - not the code assignment on the master project. For more information, see Master Projects.

Mapping Schedule Project Codes

Open Plan supports codes on the project. You can use these codes to identify the scheduler who can approve the progress at the schedule project level. To use an Open Plan project code, you must add the field in User–Defined Data and identify it in User Field Mapping.  

Schedule project codes are not supported when using Microsoft Project, but you can use custom user fields in the PM Compass project to identify an approver at that level.

The workflow uses these fields to identify who to notify to enter progress and who to notify to approve the progress. Using the above example, PM Compass would send a notification to the user ID in Code 4 on the activity. When they click the link in the notification, a list of their activities that need progress displays. After they enter and submit the progress, PM Compass notifies the approver, in this case the CAM, that there is a progress entry that they must approve.  

In System Settings, on the Progress tab, the assignment mapping grid is used to identify who the assignee and approver are for each update progress record type.  

The Assignment Mapping grid not only identifies who gets the notifications, but who has rights to modify the data. The following lists the valid fields for selection and who also has rights to progress an activity, work package or control account:

Assignee / Approver

Description

Project Assignee/Approver

The Project Assignee or Approver can reside in any Cobra project level code fields identified as a user field in user field mapping and PM Compass custom user fields.

Schedule Project Assignee / Approver

The Schedule Project Assignee or Approver can reside in any Open Plan project code fields identified as a user field in user field mapping.

Control Account Assignee

The Control Account Assignee can reside in any Cobra Mapped user fields on the control account and the Control Account Manager.  

The Project Assignee can also enter progress for tasks assigned to the Control Account Assignee.

Control Account Approver

The Control Account Approver can reside in Cobra Mapped user fields on the control account and the manager.  

The Project Approver can also approve tasks assigned to the Control Account Approver.

Work Package Assignee

The Work Package Assignee can reside in any Cobra Mapped user fields on the work package including the manager.  

The Project Assignee and the Control Account Assignee can also enter progress for tasks assigned to the Work Package Assignee.

Work Package Approver

The Work Package Approver can reside in any Cobra Mapped user fields on the work package including the manager.  

The Control Account Approver and the Project Approver can also approve tasks assigned to the Work Package Approver.

Activity Assignee

The Activity Assignee can reside in any mapped User Fields on the activity table.

Before mapping a user field, the codes and user fields must defined in User-Defined Data

The Project Assignee, the Control Account Assignee, and the Work Package Assignee can also enter progress for tasks assigned to the Activity Assignee.

Activity Approver

The Activity Approver can reside in any mapped user field on the schedule project.

The Project Approver, Control Account Approver, Work Package Approver, and the assignee's manager in the security administrator can also approve activity progress.

What do you want to do?

Specify the assignee and approver for progress entries

Add a custom field to a Projects form

Define a source field as a user field


Learn more about...