You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Product or Result of this Process
The purpose of this process is the review and execution contracts and/or Purchase Orders. The process enables external vendors and external executors to electronically route and approve all PO's and contracts.
The process generates an e-Builder Purchase Order following issuance of the SAP PO, and automatically triggers the Contract Approval process whenever the PO data meets the thresholds for a formal contract document.
Note that in e-Builder a purchase order is referred to as a Commitment.
Process Details
This process can be started by the Administrative Assistant, CC Director, CC Planner, CC Planning Director, CC Planning Manager, Director of Finance and Administration, eB Admin, Furniture Designer, OCP Planner, Program Manager, Project Coordinator, Project Manager, SPT Commissioning Lead, SPT Lead, VPF Strategic Sourcing,
This process is also started when Send and Initialize is used as the notification option in the 4.0 Bidding Step
![](/confluence/download/attachments/145036111/04.04%20PO%20Workflow%20787%20new11.jpg?version=2&modificationDate=1589389136000&api=v2)
Note that these step descriptions are in the process of being updated.
Start
- The Project Coordinator or Project Manager fills out the required fields and executes the Submit action.
- The next step is PM Initiate Process?
When asked to identify the type of contract being requested this document may be helpful. Contract Forms.pdf
Total $ <= 0?
- The Total $ <=0? conditional checks if the amount for all commitment items entered is less than or equal to $ 0.
- If True (Yes) the next step is Initiator Revise.
- If False (No) the next step is PjFnAmt < ComAmt?
![](/confluence/download/attachments/145036111/image2020-5-13%2014%3A53%3A53.png?version=1&modificationDate=1589396033000&api=v2)
PjFnAmt < ComAmt?
- The PjFnAmt < ComAmt? conditional checks if the Projected Final Contract Amount is less than the amount of the Commitment you are trying to establish.
- If True (Yes) the next step is Initiator Revise.
- If False (No) the next step is PjFnAmt < ComAmt?
Initiator Revise
- The Initiator Revise step shares a page layout with the Start step and allows the Process Initiator to make changes and resubmit the process.
- When the Initiator takes the Resubmit action the next step is the conditional question PM Initiate Process?
PM Initiate Process?
- The PM Initiate Process? conditional step determines the path the process will take based on if the data field “Did the PM Initiate the Process?” has been marked “Yes” or "No" in the previous step.
- If True (Yes) the next step is Contract Required?
- If False (No) the next step is PM Review
Contract Required?
- The Contract Required? conditional step determines the path the process will take based on if the data field “Contract Required?” has been marked “Yes” or "No" in the previous step.
- NOTE: Contract is NOT Required if PO is for Material or Equipment ONLY purchase, Environmental Agreement < $5k, Consulting Agreement < $10k, or Construction Contract < $25k.
- If True (Yes) the next step is Contract > $10K?
- If False (No) the next step is Purch Req M.M.
Contract >$10K?
- The Contract >$10K? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount.
- If True (>$10K) the next step is Vendor Manager Review of SoS.
- If False (<=$10K) the next step is Purch Req M.M.
PM Review
- The PM reviews the process and verifies the Contract or PO being added to the project and chooses the Submit action.
- The next step is Contract Required?
Vendor Manager Review of SoS
- The Vendor Manager reviews the Selection of Source information and confirms the vendor exists in SAP.
- If Submit is chosen the next step is Contract Admin Assembles Contract.
- If Revise is chosen the next step is Initiator Revise 1.
Contract Admin Assembles Contract
- The Contract Admin reviews the process and uploads the assembled Contract Document to be executed.
- As part of this step the Contract Admin associates a bid process to this PO/Contract process by using the Contract Number Lookup. (Instructions are in included on the process page)
- If Submit is chosen the next step is Initiator Reviews Contract.
- If Revise is chosen the next step is Initiator Revise 1.
Initiator Reviews Contract
- The Process Initiator reviews the Contract Document.
- If Submit is chosen the next step is CA Manager Reviews.
- If Revise is chosen the next step is Contract Admin Assembles Contract.
CA Manager Reviews
- The DoF Procurement Manager and the Contract Admin Manager reviews the Contract Document and determine whether or not it meets the requirements for OGC Counsel Review.
- If Submit is chosen the next step is Contract Admin Releases Contract.
- If Revise is chosen the next step is Initiator Revise 1.
- If To DOF Counsel is chosen the next step is OGC Counsel Review.
OGC Counsel Review
- The DOF General Counsel reviews the Contract Document.
- If Submit is chosen the next step is Contract Admin Releases Contract.
- If Revise is chosen the next step is Initiator Revise 1.
Contract Admin Releases Contract
- The Contract Admin sends the contract to the vendor for review and signature, and records the date the contract was sent.
- If Submit is chosen the Contract Document has been sent to the vendor. The next step is Vendor Executes Contract.
- If Revise is chosen the next step is Contact Admin Assembles Contract.
Initiator Revise 1
- The Initiator Revise 1 step allows the Process Initiator to make changes and resubmit the process.
- When the Initiator takes the Resubmit action the next step is Vendor Manager review of SoS.
Hold for Vendor Contract Execution
- The Contract Admin reviews the signed contract received from the vendor, records the date they received the signed contract and then removes and replaces the unsigned contract with the received vendor signed contract into the Contract Document field.
- If Submit is chosen the next step is Contract Admin Final Review.
- If Revise is chosen the next step is Contract Admin Releases Contract.
Contract Admin Final Review
- The Contract Admin Manager reviews the vendor signed contract for final review before going to directors steps.
- If Submit is chosen the next step is Campus Construction?
- If Revise is chosen the next step is Hold for Vendor Contract Execution.
Campus Construction?
- The Campus Construction? conditional determines the path the process will take based on the Program Type of the Project Details page. This conditional will evaluate as True if the Program Type is Academic, Campus Services, Capital Group, Special, System Performance & Turn-over, or Systems Renewal.
- If True (Yes) the next step is SP&T Program?
- If False (No) the next step is OCP?
SPT Program?
- The SPT Program? conditional determines the path the process will take based on the Program Type of the Project Details page. This conditional will evaluate as True if the Program Type is System Performance & Turn-over.
- If True (Yes) the next step is SPT Director Review
- If False (No) the next step is Proj. Contract>$10m?
SPT Director Review
- The SPT Director reviews the Contract Document attached to the process.
- If Submit is chosen the next step is Proj. Contract>$10m?
- If Revise is chosen the next step is Initiator Revise 3.
Proj. Contract>$10m?
- The Proj. Contract>$10m? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount.
- If True (>$10m) the next step is Vendor Manager Review of SoS.
- If False (<=$10m) the next step is Purch Req M.M.
CC Director Review
- The CC Director reviews the Contract Document attached to the process and if required attaches the CC Director Memo.
- If Submit is chosen the next step is CA Mgr & Dir. Finance.
- If Revise is chosen the next step is Initiator Revise 3.
- If Send To OGC is chosen the next step is OGC Counsel Review.
CC Director Executes Contract
- By taking the Submit action at this step the CC Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
CA Mgr & Dir. Finance
- The Contract Admin Manager and the Director of Finance and Administration review the attached CC Director Memo and upload the Executed Memo to the process.
- If Submit is chosen the next step is VP, CSS Reviews
- If Revise is chosen the next step is CC Director Review
OCP?
- The OCP? conditional determines the path the process will take based on the Program Type of the Project Details page. This conditional will evaluate as True if the Program Type is OCP.
- If True (Yes) the next step is Proj. Contract> $500k?
- If False (No) the next step is CSM?
Proj. Contract> $500k?
- The Proj. Contract> $500k? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount.
- If True (>$500K) the next step is CSM Director Executes
- If False (<=$500K) the next step is CSM Director Reviews
OCP Director Review
- The OCP Director reviews the Contract Document attached to the process.
- If Submit is chosen the next step is Prj Contract > $10mil?
- If Revise is chosen the next step is Initiator Revise 3.
OCP Director Execute
- By taking the Submit action at this step the OCP Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
CSM?
- The CSM? step determines the path the process will take based on the Program Type of the Project Details page. This conditional will evaluate as True if the Program Type is CSG or R&M.
- If True (Yes) the next step is Proj. Contract>$5m?
- If False (No) the next step is Utilities Program?
Proj. Contract>$5m?
- The Proj. Contract>$5m? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount.
- If True (>$5m) the next step is CSM Director Review.
- If False (<=$5m) the next step is CSM Director Executes.
CSM Director Executes
- By taking the Submit action at this step the O&M Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
CSM Director Review
- The SPT Director reviews the Contract Document attached to the process.
- If Submit is chosen the next step is Prj Contract > 10mil?
- If Revise is chosen the next step is Initiator Revise 3.
Utilities Program?
- The Utilities Program? step determines the path the process will take based on the Program Type of the Project Details page. This conditional will evaluate as True if the Program Type is CUP - OPS, or Utilities.
- If True (Yes) the next step is Contract> $1M.
- If False (No) the next step is FEG Program?
Contract> $1M
- The Proj. Contract>$10m? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount.
- If True (>$1m) the next step is Utilities Director Review.
- If False (<=$1m) the next step is Utilities Director Executes.
Utilities Director Execute
- By taking the Submit action at this step the Utilities Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
Utilities Director Review
- The SPT Director reviews the Contract Document attached to the process.
- If Submit is chosen the next step is Proj. Contract>$10mil?
- If Revise is chosen the next step is Initiator Revise 3.
FEG Program?
- The FEG Program? step determines the path the process will take based on the Program Type of the Project Details page. This conditional will evaluate as True if the Program Type is Energy, or SEG.
- If True (Yes) the next step is FEG Director Review.
- If False (No) the next step is VP, CSS Executes.
FEG Director Review
- The FEG Director reviews the Contract Document attached to the process.
- If Submit is chosen the next step is Proj. Contract>$10mil?
- If Revise is chosen the next step is Initiator Revise 3.
Prj Contract > 10mil?
- The Prj. Contract > 10mil? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount
- If True (>$10m) the next step is VP, CSS Reviews.
- If False (<=$10m) the next step is VP, CSS Executes.
VP, CSS Reviews
- The VP for Campus Services and Stewardship reviews the Contract Document attached to the process.
- If Submit is chosen the next step is Campus Construction?
- If Revise is chosen the next step is Initiator Revise 3.
CP, CSS Executes
- By taking the Submit action at this step the CC Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
>$10mil <$100mil?
- The Proj. Contract>$10m? conditional step determines the path the process will take based on the amount entered for the data field Projected Final Contract Amount.
- If True (>$10m) the next step is Vendor Manager Review of SoS.
- If False (<=$10m) the next step is Purch Req M.M.
VP Finance Executes
- By taking the Submit action at this step the CC Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
EVPT Executes
- By taking the Submit action at this step the CC Director is Executing the contract.
- If Submit is chosen the next step is Contract Signature followed by the SAP PO Hold Step.
- If Revise is chosen the next step is Initiator Revise 3.
Initiator Revise 3
- The Contract <$10m conditional step determines the path the process takes based on the Current Commitment value being greater than or less than $10m.
- If True (Yes) the next step is IBO Director Executes Contract.
- If False (No) the next step is IBO Director Reviews Contract.
Contract Signature
- The IBO Director reviews the process and executes the contract, then takes the Submit action.
- The next step is Contract Signature.
Purch Req M.M.
- The IBO Director reviews the process and the contract, then takes the Submit action.
- The next step is Contract <100m.
CRSP Admin & Procurement Review
- The Contract <$100m conditional step determines the path the process takes based on the Current Commitment Value being greater than or less than $100m.
- If True (Yes) the next step is Deputy EVP Executes Contract.
- If False (No) the next step is Deputy EVPT Review.
>$25K?
- The Deputy EVPT reviews the process, signs the contract and takes the Submit action.
- The next step is Contract Signature.
Initiator Revise 2
- The Deputy EVPT reviews the process and the contract and takes the Submit action.
- The next step is Contract Signature.
SAP PO Hold Step
- The EVPT Office reviews the process and the contract and takes the Submit action.
- The next step is Contract Signature.
PO M.M
- Contract Signature will finalize the director's electronic signatures using DocuSign. Once complete it will automatically take the Code Complete action. (Signifies that e-Builder has completed a task}
- The next step is SAP PO/Contract Hold Step.
AA sends Exec. PO\Contract to vendor
- The Purchase req MM step is a mail merge automation that completes the purchase requisition from the purchase requisition template.
- The next step is DoF Procurement Review.
Finish
![](/confluence/download/attachments/145036111/image2020-5-13%2014%3A10%3A48.png?version=1&modificationDate=1589393448000&api=v2)
Enter information for each commitment item.
- Item Number - a sequential number denoting each line.
- Budget Line Item - Associate each entry with a Budget Line Item.
- Current Budget - Displays the current budget.
- Description - editable field for a description.
- Retainage Percent - enter the retainage percent when applicable.
- Amount - the amount of the the commitment line
- Allowance Item - Check if it is an allowance item.
- Custom Fields - used to enter the cost object.
Pay particulate attention to the Retainage percentage as that determines how retainage is calculated when invoices are submitted.
A Retainage of five percent should be expressed as 5.00 (as in the example)
![](/confluence/download/attachments/145036111/image2019-7-15%2014%3A18%3A41.png?version=1&modificationDate=1589387518000&api=v2)
The following list of items, though part of the budget template, cannot be used to generate a commitment. You cannot place internal charges on a PO.
If you are issuing a PO to cover vendor expenses use the reimbursable line item for that vendor type. For example, for A/E expenses use B-30-125 A/E Reimbursables.
Do Not Use list is below:
A15-005 |
A15-005 DoF Project Administration |
A15-010 |
A15-010 OCP Project Administration |
A15-015 |
A15-015 Utilities Project Administration |
A15-020 |
A15-020 SEG Project Administration |
A15-025 |
A15-025 EHS Project Administration |
A15-035 |
A15-035 Service and Support-Staff |
A15-045 |
A15-045 Employee Benefit Charges (EB) - General |
A20-050 |
A20-050 Travel Expenses |
C50-685 |
C50-685 Other MIT Internal Charges |
C55-730 |
C55-730 Steam |
C55-745 |
C55-745 Chilled Water |
F95-835 |
F95-835 EVPT Contingency |
F96-840 |
F96-840 DoF Contingency |
This process will print a Purchase Order document that can be sent to the vendor.
Purchase Order
This process is used for both signed contracts and purchase orders and it will display the desired document in the AA Sends Exec. PO/Contract to Vendor ... step.
When a contract is displayed the supporting purchase order is still generated. To print the purchase order:
- Click the Print button.
- Click the Merge Templates radio button.
- Choose Purchase Order from the drop down menu.
- Click the Print Button on the Mail Merge Templates menu.
Sample Purchase Order Document
![](/confluence/download/attachments/145036111/PO%20Image.png?version=1&modificationDate=1589387518000&api=v2)
PO Mail Merge Field |
Notes/Description |
Purchase Order Number |
The Purchase Order Number in the top right hand corner of the PO (highlighted in yellow on this example) will only appear when the process has progressed through the SAP PO/Contract Hold step. Prior to that step it is possible to preview the Purchase Order, but the PO number will not appear on the form. |
Date |
The date field is the date that the purchase order mail merge is generated. If you reprint the purchase order the date will update. |
Vendor and Vendor Address |
The Vendor and vendor addresss information is derived from the Contacts module in e-Builder. If address information is missing from that module the PO fields for this information will be blank. If you update the Contacts information in e-Builder you may reprint the PO and the information will appear as updated. |
Ship To |
This information is derived from the building information that is part of the e-Builder project information. If room information has been added to e-Builder the room information will also print on the purchase order. |
Delivery Date |
This information is hardcoded. Each purchase order will have "Per Previous Agreement" in this field. Changing this field requires the assistance of an e-B admin. |
Shipping Method |
This information is hardcoded. Each purchase order will have "N/A" in this field. Changing this field requires the assistance of an e-B admin. |
Shipping Terms |
This information is hardcoded. Each purchase order will have "N/A" in this field. Changing this field requires the assistance of an e-B admin. |
Payment Terms |
This information is hardcoded. Each purchase order will have "Net 30" in this field. Changing this field requires the assistance of an e-B admin. |
Items |
Each commitment line will use the dollar figure and commitment description for the corresponding commitment in e-Builder. Each line will be sequentially numbered beginning with 001. |
Project Number |
The project number from e-Builder. |
Project Name |
The project name from e-Builder. The project name may contain the room number. |
Project Contact |
The proect contact is derived from Project Manager 1 in e-Builder. The phone number is hard coded and is the general switchboard number for MIT DoF. |
Description of Services |
|
MIT Contract # |
|
Vendor Billing Instruction |
|
MIT Sales and Use Tax Exemption |
|