2.05 - MOU and Stage 1 Budget - CRSP (Non-Cost) (MUS1)

• 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

• 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

• 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

• 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

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

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

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

• 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

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

• 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 Final PM Review
• If the Program Manager clicks REVISE the next Step is PM 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.

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