Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Round Rectangle
bgcolor#e6f2ff

The General Contract Change Order process combines previously approved Change Order Requests, generatedusing the 06.01 Letter or Release/ Change Order Request process, into a Contract Change Order for final approval.

Note

3/27/2018 - Both the process and the instructions here are being updated.

Composition Setup
 
Deck of Cards
id6.02 Deck)
Card
labelSummary
  • 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.
Card
labelProcess Map

Image RemovedImage Added

Card
labelStep Descriptions

Toggle Cloak
1. Start

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

Toggle Cloak
2. PM Review

Cloak
  • Project managers review the submission. This step is important when in the process is initiated by the contratorso 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 impacts to the schedule changes including the substantial complettion date.
  • The project manager 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?.

Toggle Cloak
3. Initiator Revise

Cloak

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

Toggle Cloak
4. Project Budget Change (Decicional Step)

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

Toggle Cloak
5. $0 Change? (Decisional Step)

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

Toggle Cloak
6. Spawn $0 Budget Change

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

Toggle Cloak
7. Spawn Additional Funding

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

Toggle Cloak
28. Time Only? (Decisional Step)

Cloak
  • 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 PCOs.CORs.

Toggle Cloak
9. Fin. Analyst Holds for Completion

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

Toggle Cloak
310. GC Change Order M.M

Cloak
  • This is a e-Builder Mail Merge step that produces the Change Order document from the Change Order template.
  • The next step is Initiator PM Review Mail Merge.

Toggle Cloak
411. Sum of Attached PCOsCORs

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

Toggle Cloak
512. Success? (Decisional Step)

Cloak
  • The Success field is evaluated to determine successful execution of Step 4.
  • If True (Yes) the next step is Change Order M.M Commitment Value CO..
  • If False (No) the next step is Initiator Resubmit.

Toggle Cloak
13. Commitment Value CO

Cloak

This is a code step that processes the Change Orders.

Toggle Cloak
14. Success?

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

Toggle Cloak
15. GC Change Order M.M. (Mail Merge)

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

Toggle Cloak
616. Initiator Resubmit

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

Toggle Cloak
717. Initiator PM Review Mail Merge

Cloak
  • The
Process Initiator (
  • Project Manager
)
  • reviews the process fields and the auto generated mail merge document and has the option to select
one of the following actions, Reviewed A/E, Reviewed - Vend, If Reviewed - Vend
  • either the Submit or Redo Mail Merge actions.
  • If
Reviewed A/E is chosen the next step is A/E Signatures.
  • Submit is chosen the next step is Vendor Signature.
  • If Redo Mail Merge is chosen the next step is Time Only?

Toggle Cloak
8. A/E Signatures18. Vendor Signature

Cloak
  • The Lead A/E Vendor reads the comments, reviews the process fields and takes the Approve action.
  • The next step is Vendor Signature.

Toggle Cloak
919. Vendor Signature St

Cloak
  • The Vendor (Contractor or Consultant) reads the comments, reviews the process fields and takes the Approve actionSignature St is an e-Signature file download/automated step to download final signed e-Signature files.
  • The next step is A/E Review Required?

Toggle Cloak
20. A/E Review Required? (Decisional)

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

Toggle Cloak
21. A/E Signature

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

Toggle Cloak
1022. PM SignatureReview

Cloak
  • The PM reads the comments, reviews the process and takes the Approve action.
  • The next step is Program Manager Review.

Toggle Cloak
1123. Program Manager Review

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

Toggle Cloak
1224. Program Director Review

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

Toggle Cloak
25. <10m? (Decisional Step)

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

Toggle Cloak
26. CC Director Executes13. Campus Construction Review

Cloak
  • The Campus Construction Director reads the comments, reviews the process fields and has the option to take either the Approve Submit or Modify CO Revise action.
  • If Approve Submit is chosen the next step is >=$1M? CC Director Signs.
  • If Modify CO the Revise action is taken the next step is Initiator Review.step is PM Revise.

Toggle Cloak
27. CC DIrector Signs

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

Toggle Cloak
1428. >=$1M <$100 (Decisional Step)

Cloak
  • The data field Change Amount is evaluated to determine if the chance change is greater than or equal to $1Mless than 100 million dollars.
  • If True (Yes) the next step is Dputy EVPT Review.Executes
  • If False (No) the next step is SAP C.O. Hold Step. Deputy EVPT Review.

Toggle Cloak
1529. Deputy EVPT Review

Cloak
  • The Deputy EVPT Office 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 SAP C.O. Hold Step EVPT Executes.
  • If Modify is chosen the next step is Campus Construction Review PM Revise.

Toggle Cloak
16. SAP C.O. Hold Step30. EVPT Executes

Cloak
  • The eB Admin holds EVPT reads the comments, reviews the process fields and waits for the SAP Integration to pick up and automatically move the process forward.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.

Toggle Cloak
31. CO Signature Finalize

Cloak
  • 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 When complete the next step is Compl PCOs on Hold.

Toggle Cloak
1732. Compl PCOs CORs on Hold

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

Toggle Cloak
1833. Success? (Decisional Step)

Cloak
  • eBuilder evaluate 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 Initiator eB Admin Resubmit.

Toggle Cloak
1934. Initiator eB Admin Resubmit

Cloak
  • The Process Initiator eB Admin reads the comments, reviews the process fields and and takes the Resubmit action.
  • The next step is Compl PCOs CORs on Hold.

20. Finish

 

35. Finish

Card
labelChange Log
DateChangeeB Admin
4/3/2018Process updated to enable signaure step for CC Director when value of GCCO is <10 milion. (Workflow v4.1)RB/SA
4/3/2018WIKI documention (Step Descriptions and Process map updated)RB