You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 115
Next »
Result or Product of this Process
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 enables the engagement of the Office of the Provost, School and DLC to better define the project and budget.
Process Details
This process:
- Starts automatically (is spawned) from 02.03 CRSP Screening Kickoff (CRSPK)
- It can also be started by the e-B admin.
- Facilities the process of gathering comments from certain teams (for instance SEG or EHS) about the project and generates an MOU (Memorandum of Understanding)

1. Process Start
- The process is usually started by a spawn step in CRSP Screening Kickoff. The process can be started manually by the project manager.
- 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 the fields listed above will be automatically filled out
- Next step: PIT Meeting Required
2. PIT Meeting Required? Conditional Step
- 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" . 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
3. PIT Meeting Occurs
- 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 takes the SUBMIT action.
- Next Step: PM Verifies Team Assignments
4. Provost Office Draft MOU
- The Provost Office 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.
- Next Step: Team Review
5. PM Verifies Team Assignments
- The Project Manager verifies that the project team includes all the resources/roles required to provide input to the Provost Office so that the MOU is properly reviewed.
- Project managers are reminded that project resources appear on the Details page of each project.
- If additional roles/resources are needed the Project Manager should request those resources using the 01.03 Add Resource to a Project process.
- The Project Manager reviews the process, verifies the resources and clicks SUBMIT.
- Next Step: Team Review
6. Team Review
- 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.
7. Provost Office Reviews MOU Comments
- 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.
- Next Step: Program Manager MOU Review
8. Program Manager MOU Review
- The Program Manager reviews the MOU content and has the option to take either the Submit or Revise action..
- If the Program Manager clicks Submit the next step is Project Manager Final MOU Review.
- If the Program Manager clicks Revise the next Step is Provost Office Reviews MOU Comments. This option can be taken when the Program Manager wishes to engage with the Provost Office about the content of the MOU.
9. Project Manager Final MOU Review
- The Project Manager reviews the MOU and has the option to select either the Submit or Revise action.
- If the Project Manager chooses Submit then the next step is MOU MM.
- If the Project Manager chooses Revise 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.
10. MOU MM (Mail Merge Automation Step)
- In this step the e-Builder system uses a template to generate the MOU document and attach it to the process.
- The system has been set to generate a Word document so that the MOU can be edited duing the next step.
- Next Step: Provost Distributes to DLC for Review
11. Provost Distributes to DLC for Review
- The Provost Office downloads the system generated MOU.
- If the MOU requires any editing, the Provost Office uses Word to make the edits. For example, if a graphic was added to the document and is too large, the size may need to be reduced. If fonts were inconsistently applied those fonts can be corrected in Word.
- 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 finished, the Provost Office takes the
- Next Step: PM Enters Benchmark and 51 Estimate
12. Project Manager Enters Benchmark and S1 Estimate
- The Project Manager reviews the process, fills out the Benchmark and Stage 1 data, prints the Stage 1 mail merge and attaches it to the process and has the option to take an action to Submit or Revise.
- If Submit is chosen the next step is Program Manager Review.
- If Revise is chosen the next step is Provost Distributes to DLC for Review.
13. Program Manager Review
- The Program Manager reviews the process and had the option to take an action to Submit or Revise.
- If Submit is chosen the next step is Stage 1 MM.
- If Revise is chosen the next step is PM Enters Benchmark and 51 Estimate.
14. Stage 1 Mail Merge
- The Stage 1 MM step is a mail merge automation step that completes the below items and automatically takes the following action:
- Next Step: CC Director Review.
15. CC Dir Review
- The CC Dir reviews the process, adds comments, and has the option to take an action to Submit or Revise.
- If Submit is chosen the Next Step is Provost Office Reviews.
- If Revise is chosen the next step is PM Revises Stage 1 Estimate.
16. PM Revises S1 Estimate
- The Project Manager reviews the process, fills out the required fields and takes the Submit action to send to the Program Manager.
- Next Step: Program Manager Review
17. Provost Office Review
- 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 a spawn step which starts the 03.01 Milestone Project Estimate
- If Revise is chosen the next step is PM Revises S1 Estimate
18. Start Milestone Project Estimate (Spawn Step)
- The Start Milestone Project Estimate spawn step creates a process instance for 03.01 Milestone Project Estimate process.
- Next Step: Finish
19. Finish
Use the Download arrow at the bottom left of the PDF frame to download a copy of this presentation.
Error rendering macro 'viewpdf'
com.atlassian.confluence.macro.MacroExecutionException: com.atlassian.confluence.macro.MacroExecutionException: The viewfile macro is unable to locate the attachment "MOU and Stage 1 MPEB Training.pdf" on this page