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.

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
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
8. 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
9. Fin. Analyst Holds for Completion

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

Toggle Cloak
10. 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
11. Sum of Attached CORs

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

Toggle Cloak
12. Success (Decisional Step)

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

Toggle Cloak
13. 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
14. 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,
  • either the Submit or Redo Mail Merge actions.
  • If
Reviewed A/E If Reviewed - Vend is chosen the next step is
  • Submit is chosen the next step is
A/E Signatures.
  • Vendor Signature.
  • If Redo Mail Merge is chosen the next step is Time Only?

Toggle Cloak
15. A/E SignaturesVendor 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
16. 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
17. PM Review

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

Toggle Cloak
18. 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
19. Program Director Review

Cloak
  • 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
20. CC Director Executes

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

Toggle Cloak
21. 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
22. <$100 (Decisional Step)

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

Toggle Cloak
23. Deputy EVPT Review

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

Toggle Cloak
24. EVPT Executes

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

Toggle Cloak
25. CO Signature Final

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

Toggle Cloak
26. Compl CORs on 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 CORs on Hold.

Toggle Cloak
27. Compl CORs on Hold

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

Toggle Cloak
28. 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 eB Admin Resubmit.

Toggle Cloak
29. eB Admin Resubmit

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

30. Finish