Versions Compared

Old Version 6

changes.mady.by.user Unknown User (robertbr@mit.edu)

Saved on

compared with

New Version Current

changes.mady.by.user Salvatore Angelone

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

Result or Product of this Process

...

column
Sectionroundrect
bgcolor
width50%

Details

ItemDescription
Purpose 
Initiated By 
Other Actors 
Processes Spawned 
Column
width50%

To Complete this Process

This process is considered complete when a Project Coordinator, Construction Safety Officer and SEG Lead have all been assigned to the project.

The names of eligible individuals, as determined by their e-Builder role(s), are displayed in a dropdown menu for each position being filled.

Process Map

Image Removed

Info
titleWhen No PM Assigned

Area to point out difference between the Yes and No branch not obvious in the process graphic

Training

#e6f2ff

This process results in the assignment of team members to a project. The process is reviewed by the eB Admin and the selected team members are added to the project and notified.

Composition Setup
 
Deck of Cards
idTA
Card
labelSummary

This process is spawned by the 02.03.05 CRSP Screening Kickoff (CRSPS) or initiated by the e-B admin for non-CRSP projects. A project manager may initiate this process.

Note

Escalation rules apply to this process.

  • Three days after the Start step the e-B admin is notified.
    • If a PM has been identified, the e-B Admin will put that person in the role and add a note to the PM that the TA process has been in the “Team Assignment” step for 3 days but is still incomplete.
    • If the PM has not yet been assigned, the eB Admin will send an Action Item to the Program Manager requesting that the PM be assigned. Once the Action Item response is received, the PM will be put in the role and a note added to the PM that TA process has been in the “Team Assignment” step for 3 days but is still incomplete.
  • Seven days after the Start step the eB admin is notified.
    • The eB Admin will move the process to the next step, putting only identified team members in roles (and notifying them).
    • If additional team members are required, process "01.03-Add a Resource to a Project" should be used.
Card
labelProcess Map

 Image Added

Card
labelStep Descriptions

Toggle Cloak
1. Initiation

Cloak

The process is usually started by a Spawn step, but can be started by the eB Admin or Project Manager.

In this step a Program Manager. Project Manager and CC Planner can be assigned. The Program Manager is required.

When complete the Submit action is taken.

  1. If a Project Manager assignment has not been assigned the process moves to Team Assignments - Including PM.
  2. If a Project Manager has been assigned the process moves to Team Assignments - PM previously assigned.

Toggle Cloak
2.Team Assignments - PM Previously Assigned

Cloak

Each assignor in this step assigns their respective team members and takes the Submit action.

Note that some roles are required before the process moves forward.

The next step is eB Admin.

Toggle Cloak
3.Team Assignments - Including PM

Cloak

Each assignor in this step assigns their respective team members and takes the Submit action. Note that Project Manager is a required field for this step.

The next step is eB Admin

Toggle Cloak
4. eB Admin

Cloak

An eB Admin reviews the assignments and automation assigns all team members selected to the project front end and backend at the project role level and completes the process.

The next step is Finish.

Finish

...