Versions Compared

Old Version 5

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

Saved on

compared with

New Version Current

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

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

Round Rectangle
bgcolor #e6f2ff

This process is used to issue an amendment to an existing MOU. To use this process an MOU should first be created and approved via the 02.05 - MOU - CRSP (Non-Cost) (MUS1) process.

Process Details

Deck of Cards
idMOU
Card
labelSummary

This process is used to issue an amendment to an existing MOU. An MOU is used to document DLC endorsements. This MOU process is used primarily for CRSP/Academic projects. 

Card
labelProcess Map

Card
labelStep Descriptions

Toggle Cloak
Start

Cloak
  • The process can be started manually by the Project Manager. In this step they have the opportunity to fill out fields in the sections: Amendment Details, Schedule, Funding Expectations, Location, Required Signatures.
  • The process can also be started by the eB Admin. If so, the eB Admin must complete all required fields.
  • When the Submit action is taken the next step is Provost Office Completes.

Toggle Cloak
Provost Office Completes

Cloak
  • In this step the Provost Office enters the Revised Total Cost, the Revised Square Footage, the Proposed Start Date and the Proposed Finish Date.
  • When the Submit action is taken the next step is MOU MM.

Toggle Cloak
MOU MM

Cloak
  • In this step the system generates the MOU Amendment Mail Merge file.
  • When this step completes successfully the next step is Team Review.

Toggle Cloak
Team Review

Cloak
  • In this step the Project Team reviews the MOU content. The process has been configured so that all of the team members (the e-Builder term is actors) must complete the Team Review step and then take the SUBMIT action.
  • If a team member was not properly assigned the process will continue without input from that person.
  • When all actors have voted for submit (Reviewed) the next step is Project Manager Final Review.

Toggle Cloak
Project Manager Final Review

Cloak
  • In this step the Project Manager reviews the MOU Amendment information that has been entered into the process enter any Project Manager Notes and indicates if the process requires any revisions.
  • If the Reviewed action is taken the next step is Program Manager Final Review.
  • If the Revise action is taken the next step is Initiator Revise.

Toggle Cloak
Program Manager Final Review

Cloak
  • In this step the Program Manager reviews the MOU Amendment information that has been entered into the process.
  • If the Submit action is taken the next step is CC Dir Review.

Toggle Cloak
CC Dir Review

Cloak

 

  • In this step the CC Director reviews the MOU Amendment information that has been entered into the process.
  • If Submit is chosen the next step is Provost Office Distributes.
  • If Revise is chosen the next step is Initiator Revise.

 

Toggle Cloak
Provost Office Distributes

Cloak
  • The Provost Office distributes the executed MOU Amendment generated by the process to the client/department.
  • If the Distributed action is taken the Provost office is indicating the MOU Amendment has been distributed, the next step is Finish.

  • If the Revise action is taken the next step is Initiator Revise.

Toggle Cloak
Initiator Revise

Cloak
  • The process reaches this step because someone has indicated revisions are necessary. The Initiator of the process has the opportunity to make edits to the information entered into the process fields and resubmit.
  • If Submit is chosen the next step is Provost Office Completes.

Toggle Cloak
Finish

Cloak