Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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

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

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?

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.
  • Following the Spawn $0

Toggle Cloak
6. Spawn $0 Budget Change

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

 

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

Toggle Cloak
3. 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 Review.

Toggle Cloak
4. Sum of Attached PCOs

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

Toggle Cloak
5. 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.
  • If False (No) the next step is Initiator Resubmit.

 

Toggle Cloak
6. 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
7. Initiator Review

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, Redo Mail Merge.
If Reviewed A/E is chosen the next step is A/E Signatures.
If Reviewed - Vend 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 Signatures

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

Toggle Cloak
9. Vendor Signature

Cloak
  • The Vendor (Contractor or Consultant) reads the comments, reviews the process fields and takes the Approve action.
  • The next step is PM Signature.

Toggle Cloak
10. PM Signature

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

Toggle Cloak
11. 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
12. Program Director Review

Cloak
  • The Program Director reads the comments, reviews the process fields and takes the Approve action.
  • The next step is Campus Construction Review.

Toggle Cloak
13. Campus Construction Review

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

Toggle Cloak
14. >=$1M (Decisional Step)

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

Toggle Cloak
15. EVPT Review

Cloak
  • The 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
  • If Modify is chosen the next step is Campus Construction Review.

Toggle Cloak
16. SAP C.O. Hold Step

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

Toggle Cloak
17. Compl PCOs on Hold

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

Toggle Cloak
18. Success? (Decisional Step)

Cloak
  • eBuilder evaluate the data field Passed Approval for a true condition.
  • If True the next step is Finish.
  • If False the next step is Initiator Resubmit.

Toggle Cloak
19. Initiator Resubmit

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

20. Finish