You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 31
Next »
The General Contract Change Order process combines previously approved Change Order Requests, generated using the 06.01 Letter or Release/ Change Order Request process, into a Contract Change Order for final approval.
- This process is usually started by the project manager, however it can be started by the contractor.
- The process routes the GCCO for approval and signature by the appropriate parties based on dollar amount and program.

1. Start
- Started by the project manager or contractor who fills in the required fields and attaches the associated Change Order Requests that are to be combined into a single General Contract Change Order.
- Be sure to add the Change Order Request properly. You must access the Filter Processes screen to select COR's to be processed. On screen instructions are provided in the process.
- When finished the initiator takes the Submit action.
- The next step is PM Review?
2. PM Review
- Project managers review the submission. This step is important when the process is initiated by the contrator.
- As part of this step project managers must update the Schedule module to reflect any impacts to the schedule including the substantial complettion date.
- The project manager takes the Submit action to advance the process.
- If revisions are needed, the project manager has the option to take the Revise action to return this process to the initiator for changes.
- Following the Submit action the next step is Project Budget Change?.
3. Initiator Revise
This step allows for changes to the original information submitted by the initiator prior to resubmission and reconsideration by the project manager.
4. Project Budget Change
- The e-Builder system determines if this is a project budget change.
- If Yes (Budget Change) the next step is $0 Budget Change?.
- If No (Not a Budget Change) the next step is Time Only?.
5. $0 Change?
- The e-Builder system detemines if this is a $0 budget change?
- If Yes ($0 budget change) the next step is Spawn $0 Budget Change.
- If No (more than $0 budget change) the next step is Spawn Additional Funding.
6. Spawn $0 Budget Change
- The process $0 Budget Change is started.
- The project manager must complete the $0 Budget Change process.
- Following the Spawn $0 Budget Change step the process moves to the Fin./Analyst Hold for Completion step is started.
7. Spawn Additional Funding
- The 03.03 - Contingency Request/True-Up Form/Additional Funding Request process is started and placed in the project manager's Court.
- The next step is Fin. Analyst Holds for Completion.
8. Time Only? (Decisional Step)
- The "Is this a Time Only request" field is evaluated to determine if this is a Time Only request.
- If True (Yes) the next step is Change Order M.M
- If False (No) the next step is Sum of Attached PCOs.
9. Fin. Analyst Holds for Completion
- The Financial Analyst holds the process until a budget change/additonal funding is resolved.
- When the budget is resolved the Financial Analyst takes the Submit action.
- The next step is Time Only?
10. GC Change Order M.M
- This is a e-Builder Mail Merge step that produces the Change Order document from the Change Order template.
- The next step is PM Review Mail Merge.
11. Sum of Attached CORs
- This is an e-Builder step in which custom code sums the attached PCOs.
- The next step is Success?
12. Success (Decisional Step)
- The Success field is evaluated to determine successful execution of Step 4.
- If True (Yes) the next step is Commitment Value CO..
- If False (No) the next step is Initiator Resubmit.
13. Initiator Resubmit
- The Process Initiator reads the comments and reviews the process fields, updates as necessary and takes the Resubmit action.
- The next step is Sum of Attached PCOs.
14. PM Review Mail Merge
- The Project Manager reviews the process fields and the auto generated mail merge document and has the option to select either the Submit or Redo Mail Merge actions.
- If Submit is chosen the next step is Vendor Signature.
- If Redo Mail Merge is chosen the next step is Time Only?
15. Vendor Signature
- The Vendor reads the comments, reviews the process fields and takes the Approve action.
- The next step is Vendor Signature.
16. Vendor Signature St
- The Vendor Signature St is an e-Signature file download/automated step to download final signed e-Signature files.
- The next step is A/E Review Required?
17. A/E Review Required? (Decisional)
- If Yes (A/E Signature Required) the next step is A/E Signature.
- If No (no A/E Signature Required) the next step is PM Review.
18. A/E Signature Step
- The A/E Signature Step is an e-Signature file download/automated step to download final signed e-Signature files.
- The next step is PM Review.
19. PM Review
- The PM reads the comments, reviews the process and takes the Approve action.
- The next step is Program Manager Review.
20. Program Manager Review
- The Program Manager reads the comments, reviews the process fields and has the option to take the Approve or Modify CO actions.
- If Approve is chosen the next step is Program Director Review.
- If Modify CO is chosen the next step is Initiator Review.
21. Program Director Review
- The appropriate Program Director reads the comments, reviews the process fields and takes the Approve action.
- The next step is Campus Construction Review.
22. CC Director Executes
- The Campus Construction Director reads the comments, reviews the process fields and has the option to take either the Approve or Revise action.
- If Approve is chosen the next step is CC Director Signs.
- If the Revise action is taken the next step is PM Revise.
23. CC DIrector Signs
- The CC DIrector Signs step is an e-Signature file download step the allows documents to be signed and attached to the process.
- The next step is <100M?
24. <$100 (Decisional Step)
- The data field Change Amount is evaluated to determine if the change is less than 100 million dollars.
- If True (Yes) the next step is Dputy EVPT Executes
- If False (No) the next step is Deputy EVPT Review.
25. Deputy EVPT Review
- The Deputy EVPT reads the comments, reviews the process fields and has the option to take the Approve or Modify CO action.
- If Approve is chosen the next step is EVPT Executes.
- If Modify is chosen the next step is PM Revise.
26. EVPT Executes
- The EVPT reads the comments, reviews the process fields and has the option to take the Submit or Revise action.
- If Submit is chosen the next step is CO Signature Finalized.
- If Revise is chosen the next step is PM Revise.
27. CO Signature Final
- The CO Signature Final step is an e-Signature file download step that allows documents to be signed and attached to the process.
- The next step is Comp CORs on Hold.
28. Compl CORs on Hold Step
- The eB Admin holds the process fields and waits for the SAP Integration to pick up and automatically move the process forward.
- When complete the next step is Compl CORs on Hold.
29. Compl CORs on Hold
- eBuilder runs custom code to to complete the COR's.
- The next step is Success?.
30. Success? (Decisional Step)
- eBuilder evaluate the data field Passed Approval for a true condition.
- If True the next step is Finish.
- If False the next step is eB Admin Resubmit.
31. eB Admin Resubmit
- The eB Admin reads the comments, reviews the process fields and and takes the Resubmit action.
- The next step is Compl CORs on Hold.
32. Finish