Versions Compared

Old Version 57

changes.mady.by.user Unknown User (robertbr@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 merges information stored in e-Builder with a document template to create a Memorandum of Understanding (MOU) and initial budget that can be shared with project sponsors or other parties.

Composition Setup
 

This process can be initiated by This process enables the engagement of the Office of the Provost, School and DLC to better define the project and budget.

Process Details

Deck of Cards
idMOU
Card
labelSummary
  • This process starts automatically when the 02.01 Team Assignment (TA) process is complete or can be initiated by the e-B admin.
  • The primary actor for this process is the Project Manager.
  • Secondary actors include the Provost Office,
    • The process does not spawn other processes

    The output of this process is an MOU which spawns a Stage 1 process. The MOU goal is to document DLC endorsements. This MOU process is used primarily for CRSP/Academic projects. 

    Card
    labelProcess Map

    Image RemovedImage Added

    Card
    labelActors and ActionsStep Descriptions

    Toggle Cloak
    Process Started by Spawn or eB AdminStart

    Cloak
    Started by the
    • The process is usually started by a spawn step in CRSP Screening Kickoff
    or
    • . The process can be started manually by the project manager.
    • The process can also be started by the eB Admin.
    • If initiated by so, the eB Admin , that person fills out the required fields and when finished Submitsmust complete the Department, Project Description, 100% CRSP Funding and Stage 1 Budget fields.
    • If started by the spawn process the fields listed above will be automatically filled out and the below action will automatically be taken.

    Submit

    • Status of Process: Submitted
    • Data field assignments made
    • Next step: PIT Meeting Required

    Toggle Cloak
    PIT Meeting Required?

    Cloak
    • The PIT Meeting Required conditional step determines the path the process will take based on if the data field "PIT Meeting Required" has been marked "Yes"
    in a previous step
    • . It will automatically take one of the following paths:
    True
    • If True (Yes)
  • Condition PIT Required = Yes
    • Next Step:
    •  the next step is PM schedules PIT meeting
    • If False (No)
  • Condition PIT Required not equal to yes
    • Next Step:
    • the next step is Provost Office Draft MOU

    Toggle Cloak
    PM Schedules PIT Meeting Occurs

    Cloak
    The
    • Once the PIT meeting has been completed the Project Manager opens and reviews the process
    ,
    • and completes the required fields
    and then Submits.

    Submit

  • Status of Process: Unchanged
    • in the form. When finished the Project Manager takes the SUBMIT action.
    • Next Step: PM Verifies Team Assignments
    Next Step: Provost Office Draft MOU

    Toggle Cloak
    Provost Office Draft MOU

    Cloak
    • The Provost Office
    reviews the process and completes
    •  drafts the MOU by completing all of the required fields
    and Submits to the team

    Submit to Team

    1. Status of Process: Unchanged
    2. Next Step: Team Review

    Toggle Cloak
    Team Review

    Cloak

    IS&T Lead, Project Manager, CC Sustainability, CC Planning Manager, EHS Project Liaison, CR Admin and OCP Planner review the process and then Submit

    Submit

    1. Status of Process: Unchanged
    2. Number of Actors to Complete Action: All Actors
    3. Next Step: Provost Office Reviews MOU Comments

    Toggle Cloak
    Provost Office Review MOU Comments

    Cloak

    The Provost Office reviews the process, fills out the required fields and takes the following action:

    Submit

    1. Status of Process: Unchanged
    2. Next Step:  Program Manager MOU Review

    Toggle Cloak
    Program Manager MOU Review

    Cloak

    The Program Manager will review the process and take one of the following actions.

    1. Submit
      1. Status of Process: Leave unchanged
      2. Causes Field Validation: Yes
      3. Data Field Assignments are Made
      4. Next Step: PM Checks Benchmark Data
    2. Revise
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: Yes
      3. Next Step: Provost Office Distributes to DLC for Review

    Toggle Cloak
    PM Checks Benchmark Data

    Cloak

    The Project Manager reviews the process and takes one of the following actions:

    1. Submit
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: YesData Field Assignments are Made
      3. Next Step: Program Manager Review
    2. Revise
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: Yes
      3. Next Step: PM Enters Benchmark and S1 Estimate

    Toggle Cloak
    PM Checks Benchmark Data

    Cloak

    The Program Manager reviews the process and takes one of the following actions:

    1. Submit
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: YesData Field Assignments are Made
      3. Next Step: MOU/Stage 1 MM
    2. Revise
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: Yes
      3. Add Comments: Yes, required
      4. Next Step: Provost Distributes to DLC for Review

    Toggle Cloak
    MOU/Stage 1 MM

    Cloak

    Code Complete

    The MOU Stage 1 MM is a mail merge automation step that completes the items below and automatically takes the action:

    Code Complete

    1. Automation Step Type: Mail Merge
    2. Mail Merge Template: MOU and Stage 1
    3. Archive Mail Merge = Yes
      1. Destination Folder = Document\02 Project Development Budgets
      2. Store in Field: MOU/Stage 1 Document (I&E)\201 Scope and Project Definition Forms (I)
    4. Next Step: CC Dir & Dir of Projects Review

    Toggle Cloak
    CC Dir and Dir of Projects Review

    Cloak

    The CRSP Admin reviews the process, adds comments and takes one of the following actions:

    1. Submit
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: Yes
      3. Next Step: Provost Office Distributes to DLC
    2. Revise
      1. Status of Process: Leave status unchanged
      2. Causes Field Validation: No
      3. Next Step: PM Revises Benchmark or S1 Estimate

    Toggle Cloak
    PM Revises Benchmark or S1 Estimate

    Cloak

    The Project Manager reviews the process, fills out the required fields and takes the following action:

    To Program Manager

    1. Status of Process: Received
    2. Causes Field Validation: Yes
    3. Data Field Assignments are Made
    4. Next Step: Program Manager Review
    Note

    e-Builder will generate a Word document for editing by the project manager. Copies of the MOU that are distributed for comment will be in PDF format and not be editable by the reviewers.

    e-Builder Instructions

    1. Step 1
    2. Step 2
    3. etc

     

     

     

     

    ...

    • , including Description of Project, Scope of Work, Assumptions and Qualifications, Design and Construction Delivery, Preliminary Range Estimate, Intent, Funding, LocationSize and Schedule and Endorsements. For any entry made into a text box where it is possible to control text attributes the Font should be set to Arial and the Font Size set to 16px.
    • It is possble to paste text from a document into e-Builder text fields. It is important that the Font be set to Arial and Font Size set to 16px.
    • Since the amount of work on the page is considerable, use the Save Draft button to save the process as necessary prior to taking the Submit action.
    • When complete, take the Submit action the next step is Team Review.

    Toggle Cloak
    Spawn Stage 1

    Cloak
    • This step will automatically spawn a 02.06 - Stage 1 Budget (S1BA) process.

    Toggle Cloak
    Team Review

    Cloak
    • 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.
    • Next Step: Provost Office Reviews MOU Comments

    Adding Comments/No Comment

    • Add your comments using the Comments tab. After adding your comments take the SUBMIT action.
    • If you have no comments, enter "N/A" or "No Comments" using the Comments tab. You must take the SUBMIT action even if you take this option not to comment.

    Escalation Rules

    • This process step has escalation rules applied. After 7 days the process moves to the next step - Provost Office Reviews MOU Comments. If you do not comment, or indicate no comment within the 7 days you will lose your opportunity to contribute to the MOU.

    Toggle Cloak
    PM Reviews Team Comments

    Cloak
    • The Project Manager reviews the MOU comments from the team.
    • When finished, the Project Manager takes the SUBMIT action.
    • If Submit is chosen the next step is Provost Office Reviews MOU Comments.
    • If Revise to Team is chosen the next step is Team Review.
    • If Void is chosen the next step is Finish.

    Toggle Cloak
    Provost Office Reviews MOU Comments

    Cloak
    • The Provost Office reviews the MOU comments from the team and makes edits to the MOU content if needed.
    • When finished the Provost Office takes the SUBMIT action the next step is Program Manager MOU Review.
    • When the DLC Endo Outside of EB action is taken the next step is Finish.

    Toggle Cloak
    PM Review

    Cloak
    • The Project Manager reviews the MOU comments from the Provost Office.
    • When finished, the Project Manager takes the Reviewed action.
    • If Reviewed is chosen the next step is Program Manager MOU Review
    • If Revise to Prov. is chosen the next step is Provost Office Reviews MOU Comments.

    Toggle Cloak
    Program Manager Hold

    Cloak
    • The Program Manager reviews the MOU content and has the option to take either the Submit or Revise action..
    • If the Program Manager clicks Reviewed the next step is Final PM Review
    • If the Program Manager clicks Revise the next Step is PM Review

    Toggle Cloak
    Final PM Review

    Cloak
    • The Project Manager reviews the MOU and has the option to select either the Submit or Revise action.
    • If the Project Manager chooses Reviewed then the next step is MOU MM.
    • If the Project Manager chooses Revise to Prov. then the next step is Provost Office Reviews MOU Comments. This option can be taken when the Project Manager wishes to engage with the Provost Office about the content of the MOU.

    Toggle Cloak
    Provost Office Obtains DLC Endorsement

    Cloak
    • The Provost Office downloads the system generated MOU.
    • The MOU is distributed to the DLC for review and endorsement.
    • The process remains in this step until the endorsed MOU is returned from the DLC. The endorsed MOU is added to the process step by uploading the document into the Executed MOU field.
    • When Submit is chosen the next step is Finish.

    Toggle Cloak
    Finish

    Cloak