Versions Compared

Old Version 92

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

composition-setup
Round Rectangle
bgcolor #e6f2ff

The purpose of the MOU & Stage 1 Budget process is to request DLC approval for the initial (Stage 1) budget for Academic projects. 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

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. 

Workflow StepDetail
Who can start this process?This process starts automatically (is spawned) from 02.03 CRSP Screening Kickoff (CRSPK) or it can be initiated by the e-B admin.
Who can view drafts of this process?No users
Who can view all process instances?CRSP Admin, Program Manager
Who can report on this process?All users
Who is notified as this process moves between steps?No users
Who can view/add private comments to this process?No users
Card
labelProcess Map

Image RemovedImage Added

Card
labelActors and ActionsStep Descriptions

Toggle Cloak
1. Process Start

Cloak
  • The process is usually started by
the
  • a spawn step in CRSP Screening Kickoff
or
  • . The process can be started manually by the
eB Admin
  • project manager.
  • If initiated The process can also be started by the eB Admin. If so, the eB Admin must complete the Department, Project Description, 100% CRSP Funding and Stage 1 Budget fields.
  • If started by the spawn process those the fields listed above will be automatically filled out
  • Next step: PIT Meeting Required

Toggle Cloak
2. PIT Meeting Required? Conditional Step

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:
  • If True (Yes) the next step is PM schedules PIT meeting
  • If False (No) the next step is Provost Office Draft MOU

Toggle Cloak
3. 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 in the form. When finished the Project Manager
clicks
  • takes the SUBMIT action.
  • Next Step:
Prst Office Draft MOU
Toggle Cloak
4.
  • PM Verifies Team Assignments
cloak

The Project Manager reviews the process, completes the required fields and clicks SUBMIT.

Next Step: Provost Office Draft MOU

Toggle Cloak
5. Provost Office Draft MOU

Cloak
  • The Provost Office
reviews the process and completes the required fields and SUBMITS to the team.

Next Step: Team Review

Toggle Cloak
6. Team Review

  •  drafts the MOU by completing all of the required fields, 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
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. All actors must complete their tasks and SUBMIT.

  • 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

Toggle Cloak
7. Provost Office Review MOU Comments

Cloak

The Provost Office reviews the process, fills out the required fields and clicks SUBMIT.

Next Step:  Program Manager MOU Review

Toggle Cloak
8. Program Manager MOU Review

Cloak

The Program Manager reviews the process and has the option of either submitting or asking for revisions.

  • If the program manager clicks Submit the next step is PM Final MOU Review
  • If the program manager clicks Revise the next Step: is 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
Toggle Cloak
9. Project Manager Final MOU Review

Cloak
  • The Project Manager reviews the
process and has the option to submit or to request revisions.
  • MOU comments from the team.
  • When finished, If the Project Manager chooses Submit then the next step is DRAFT MOUtakes the SUBMIT action.
  • If the Project Manager chooses Revise then Submit is chosen the next step is Provost Office Reviews MOU Comments
Toggle Cloak
10
  • .
Draft MOU
  • If Revise to Team is chosen the next step is Team Review.
  • If Void is chosen the next step is Finish.
Cloak

The Draft MOU Step is a mail merge automation step.

  • The Mail Merge Template used is MOU Draft
  • The Destination Folder = Document\02 Project Development - Budgets
    • Next Step: Provost Distributes to DLC for Review

    Toggle Cloak
    11. Provost Distributes to DLC for ReviewProvost Office Reviews MOU Comments

    Cloak
    • The Provost Office reviews the
    process, fills out the required fields and clicks SUBMIT.Next Step: PM Enters Benchmark and 51 Estimate
    • 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
    12. Project Manager EBenchmark and S1 EstimatePM Review

    Cloak
    • The Project Manager reviews the
    process, fills out the benchmark and Stage 1 data, prints the Stage 1 mail merge and attaches, then takes the following action:

    Submit

    1. Status of Process: Unchanged
    2. Data Field Assignments Made
    3. Next Step: Program Manager Review
    • 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
    Toggle Cloak
    13. Program Manager Review

    Cloak
    • The Program Manager reviews the
    process and takes one of the following actions:
    1. Submit
      1. Status of Process: Unchanged
      2. Next Step: MOU /Stage 1 MM
    2. Revise
      1. Status of Process: Unchanged
      2. Add Comments: Yes, Required
      3. Next Step: PM Enters Benchmark and 51 Estimate

    Toggle Cloak
    14. MOU Stage 1 MM

    • 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
    Cloak

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

    Code Complete

  • Automation Step Type: Mail Merge
  • Mail Merge Template: MOU & Stage 1
  • Archive Mail Merge: Yes
  • Destination Folder: Document/02 Project Development Budgets (I&E)\02.01 Scope and Project Definition Forms (I)
    • Next Step: Provost Distributes to DLC for
    • Review

    Toggle Cloak
    15. CC Dir and Dir of Projects Final PM Review

    Cloak
    • The
    CRSP Admin
    • Project Manager reviews the
    process, adds comments,
    • MOU and has the option to select either the Submit or Revise action.
    • If
    Submit is chosen the Next Step is  Provost Office Reviews
    • the Project Manager chooses Reviewed then the next step is MOU MM.
    • If
    Revise is chosen
    • the Project Manager chooses Revise to Prov. then the next step is
    PM Revises Benchmark or S1 Estimate

    Toggle Cloak
    16. PM Revises Benchmark or S1 Estimate

    Cloak

    The Project Manager reviews the process, fills out the required fields and sends to the Program Manager.

    Next Step: Program Manager Review
    • 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
    17. Provost Office ReviewObtains DLC Endorsement

    Cloak
    • The Provost Office
     reviews the process, fills out the required fields, and has the option to Submit or to Revise.

    If Submit is chosen the next step is Start 03.01 Milestone Project Estimate

    If Revise
    • 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
    PM Revises Benchmark or S1 Estimate
    • Finish.

    Toggle Cloak
    18. Start Milestone Project Estimate (Spawn Step)

    Cloak

    The Start Milestone Project Estimate spawn step creates a process instance for 03.01 Milestone Project Estimate process.

     Next Step: Finish

    19. Finish

    Note

    e-Builder generates 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.

     

     

     

    Finish

    Cloak

    ...