06.02 General Contract Change Order (GCCO)

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

• This step is in the process so that a GCCO submitted by a conractor is immediatley reviewed by the project manager before being forwarded to others. (If the project manager started the process this may seem like a duplicate step.)
• The Project Manager reviews the submission.
• As part of this step project managers must update the Schedule module to reflect any changes including the substantial complettion date.
• The Project Manger 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?.

This step allows for changes to the original information submitted by the initiator prior to resubmission and reconsideration by the project manager.

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

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

• The process $0 Budget Change is started and placed in the project manager's Court.
• The Projet 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.

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

• 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 GC Change Order M.M
• If False (No) the next step is Sum of Attached CORs.

• The Financial Analyst holds the process until budget changes or additonal funding is resolved.
• When resolved the Financial Analyst takes the Submit action.
• The next step is Time Only?

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

• This is an e-Builder step in which custom code sums the attached PCOs.
• The next step is Success?

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

This is a code step that processes the Change Orders.

• This is a code step that evaluates the success of the Commitment Value CO step.
• If successful the next step is GC Change Order MM. (Mail Merge)
• If unsuccessful the next step is Initiator Resubmit.

• The GC Change Order mail merge generates the General Change Order document.
• The next step is PM Review Mail Merge.

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

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

• The Vendor reads the comments, reviews the process fields and takes the Approve action.
• The next step is Vendor Signature.

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

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

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

• The PM reads the comments, reviews the process and takes the Approve action.
• The next step is 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.

• A series of decisional steps determines which program director approves.
• The appropriate Program Director reads the comments, reviews the process fields and takes the Approve action.
• The next step is Campus Construction Review.

• This is a decison step to determine signature authority and proper routing.
• If <10 million the next step is CC Director Executes.
• If >10 million the next step is CC Director Reviews.

• The Campus Construction Director reads the comments, reviews the process fields and has the option to take either the Submit or Revise action.
• If Submit is chosen the next step is CC Director Signs.
• If the Revise action is taken the next step is PM Revise.

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

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

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

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

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

• eBuilder runs custom code to complete the COR's.
• The next step is Success?.

• eBuilder evaluates the data field Passed Approval for a true or false condition.
• If True (passed approval) the next step is Finish.
• If False (failed approval) the next step is 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.