This process can be used to generate the Change Order Request (COR). One or more CORs must be included in a General Conract Change Order process in order for commitments (POs) to be changed.
When you change a commitment (PO) you must also ensure that there is sufficient budget to cover the total of the changes.
To change existing Schedule of Value (SOV) line items click the Add all existing items button. Adjust amounts by entering either positive or negative numbers in the Change Amount column.
To add a NEW SOV line item complete the Add Additional Scope Commitment Item entry fields including Custom Fields then click the Add button.
A new commitment item must have a positive dollar value. You cannot create a new commitment item with a negative value.
PLEASE DO NOT FORGET to choose a cost object when setting up the PO (click the icon in the last column named Custom Fields and choose the cost object).
Please note: CORs for a vendor are bundled in a GCCO. GCCOs can only be submitted one at a time per vendor. To avoid commitment control violations, you should only create enough CORs for the GCCO you are working on and ensure they are fully processed (in SAP) before starting your next round of CORs for the next GCCO.
Additionally, you cannot submit a COR unless the project status is an Active one and where to find this status on the details page.
Start/Initiation
- This process can be started by the roles of Administrative Assistant, CC Planner, Contractor, OCP Planner, Project Coordinator, Project Manager, and SPT Lead.
- To change existing Schedule of Value (SOV) line items click the Add all existing items button. Adjust amounts by entering either positive or negative numbers in the Change Amount column.
- To add a NEW SOV line item complete the Add Additional Scope Commitment Item entry fields including Custom Fields then click the Add button.
- A new commitment item must have a positive dollar value. You cannot create a new commitment item with a negative value.
- PLEASE DO NOT FORGET to choose a cost object when setting up the PO (click the icon in the last column named Custom Fields and choose the cost object).
- Please note: CORs for a vendor are bundled in a GCCO. GCCOs can only be submitted one at a time per vendor. To avoid commitment control violations, you should only create enough CORs for the GCCO you are working on and ensure they are fully processed (in SAP) before starting your next round of CORs for the next GCCO.
- Additionally, you cannot submit a COR unless the project status is an Active one and where to find this status on the details page.
| Step No. |
Step Name |
Description |
| 1 |
Is this a user data entry ERROR fix ONLY? |
Please only select yes if you are using this process to fix a user data entry error that occurred while entering the original Commitment (Purchase Order schedule of values). |
| 2 |
Is this Change Request for a Purchase Order Only (NO Contract)? |
ONLY select yes if this change request is to a Purchase Order and there is no Contract for the Vendor. If the aggregate of the changes and original PO meet the thresholds for a Contract then the Issue Contract process will need to be started. |
| 3 |
Ready for Owner Action |
If the COR is ready for processing as part of a GCCO indicate by answering Yes. |
| 4 |
A/E on Project |
If an A/E is on the project indicate by answering Yes. |
| 5 |
Brief Description of Change |
Enter a description of the change. |
| 6 |
Time Extension Requested (in Days) |
Indicate the time extension that is required for this COR. You may indicate 0 if there is no impact to the schedule. |
| 7 |
Vendor's Supporting Documentation |
Add any documentation that supports the change request. |
| 8 |
Commitment |
You must select the commitment (PO) that is being changed. When the commitment is selected the process will display the commitment lines and allow for changes. |
| 9 |
Date of Change |
Indicate the date of the change. |
| 10 |
Reason Code |
Indicate the reason for the change. |
| 11 |
Justification for the Change |
Indicate the justification for the change. |
| 12 |
Add All Existing Items |
Imports the schedule of values for the chosen commitment. |
| 13 |
Edit the Change Amount |
Edit the change amounts for each Commitment line item you want to modify |
| 14 |
Add Additional Scope Commitment Item |
Select the Cost Object for any new Scope Commitment Items you would like to add |
| 15 |
Select a Cost Object |
Select a Cost Object |
- The next step is Data Entry Error?
NAICS 1 = A/E?
- The NAICS 1 = A/E? Conditional step determines if the NAICS 1 number for the Company starts with 54.
- If True the next step is NAICS 2 - NOT A/E?
- If False the next step is PStatus Valid for $
NAICS 2 - NOT A/E?
- The NAICS 2 = A/E? Conditional step determines if the NAICS 2 number for the Company starts with 23.
- If True the next step is PStatus Valid for $
- If False the next step is NAICS 3 - NOT A/E?
NAICS 3 - NOT A/E?
- The NAICS 3 = A/E? Conditional step determines if the NAICS 3 number for the Company starts with 23.
- If True the next step is PStatus Valid for $
- If False the next step is Improper Change Order Type
Improper Change Order Type
- If you have reached the Improper Change Order Type step you have selected a COR process for a vendor that is designated as a Professional Services vendor. Please reach out to the e-B team if you think you have reached this step in error
- If Void is selected the next step is Finish and the process will be Void.
- If This is Construction is chosen the next step is PStatus Valid for $
PStatus Valid for $
- The $0 Change? Conditional checks if the value of the Commitment Change entered is $0.
- If True the next step is PM FIXES Project Status w/a PMUa
- If False the next step is $0 Change?
PM FIXES Project Status w/a PMUa
- If you have reached the PM FIXES Project Status w/a PMUa step it is because you are unable to proceed with a Change Order in the current project status and need to update it via a PMUa.
- When submit is chosen the next step is PStatus Valid for $
$0 Change?
- The $0 Change? Conditional checks if the value of the Commitment Change entered is $0.
- If True the next step is LOR
- If False the next step is Is this a LOR?
LOR?
- The LOR? Conditional checks if the data field Is this a LOR? is Yes.
- If True the next step is PM Uploads LOR
- If False the next step is SAP Hold Step
Is this a LOR?
- The LOR? Conditional checks if the data field Is this a LOR? is Yes.
- If True the next step is Is $ 0?
- If False the next step is Data Entry Error?
Is $ 0?
- The Is $ 0? Conditional checks if the value of the Commitment Change entered is $0.
- If True the next step is PM Uploads LOR
- If False the next step is Initiator Revise, Error
Data Entry Error?
- The Data Entry Error? conditional step determines the path process will take based on if the Data Field “Is this a user data entry ERROR fix ONLY?” has been marked “Yes” or "No" in the previous step.
- If True (Yes) the next step is eB Admin Review.
- If False (No) the next step is PO CO ONLY?
PO CO ONLY?
- The PO CO ONLY? conditional step determines the path process will take based on if the Data Field “Is this Change Request for a Purchase Order Only (NO Contract)?” has been marked “Yes” or "No" in the previous step.
- If True (Yes) the next step is Pm Enters Data.
- If False (No) the next step is COR AMT <0>?
Pm Enters Data
- The Pm Enters Data step allows the Project Manager to review what has been entered and select the the type of work this Purchase Order is written for. The choices are:
- Asbestos
- Construction
- Consultant
- Mover
- Once submitted next a series of Conditional Questions are asked.
Conditional Questions
- If the type of purchase order chosen in the previous step was Asbestos
- and the purchase order has a value less than $5000 it will be routed to the Program Manager Review step.
- and the purchase order has a value of more than $5000 it will be routed to the Contract Required step.
- If the type of purchase order chosen in the previous step was Construction
- and the purchase order has a value less than $10000 it will be routed to the Program Manager Review step.
- and the purchase order has a value of more than $10000 it will be routed to the Contract Required step.
- If the type of purchase order chosen in the previous step was Consultant
- and the purchase order has a value less than $25000 it will be routed to the Program Manager Review step.
- and the purchase order has a value of more than $25000 it will be routed to the Contract Required step.
- If the type of purchase order chosen in the previous step was Mover it will be routed to the Program Manager Review step.
Contract Required
- In this step the Project Manager reviews the information entered.
- If Submit is chosen the next step is Hold for Contract Execution
Hold For Contract Execution
- The Hold For Contract Execution step is where contracts team uploads a contract with the new aggregate total (original commitment plus new amount in this COR) to the process by uploading the contract in this step.
- If the Contract Exec action is taken the next step is Program Manager Review.
- If the Revise action is taken
Program Manager Review
- The Program Manager Review step allows the Program Manager to review the amended contract or the commitment change in the Cost Grid that reflects the change to the original commitment.
- If approved the next step is the CC Director Approval step.
- If in need of revision next step is the Initiator Revise step.
CC Director Approval
- The CC Director Approval step allows the CC Director to review the amended contract or the commitment change in the Cost Grid that reflects the change to the original commitment. If approved past this step the process status will be set to Pending.
- If approved the next step is the COR Hold for GC-CO step.
- If in need of revision next step is the Initiator Revise step.
Initiator Revise
- The Initiator Revise step shares a page layout with the Start/Initiation step and allows the Process Initiator to make changes and resubmit the process.
- If the Resubmit to Sta action is taken the next step will be the conditional question Data Entry Error? (Recommended)
- If the Resubmit to eB action is taken the next step will be the step eB Admin Review.
- If the Void action is taken the process is moved to the Finish step and voided.
eB Admin Review
- The eB Admin Review step shares a page layout with the Start/Initiation step and allows an eB Admin to make changes and resubmit the process.
- If the Approved action is taken the next step will be SAP Hold Step.
- If the Rejected action is taken the next step will be Initiator Revise.
COR Hold for GC-CO
- The COR Hold for GC-CO Step will hold all Change Order Requests until they are bundled with the GCCO Process and the process is approved. Once the GCCO process is approved the attached Change Order Request Processes (COR) will automatically take the Code Complete action.
- When the Code Complete action is taken the next step is SAP Hold Step.
SAP Hold Step
- Hold step for SAP Processing.
- Once processed the next step is the Finish step.
COR AMT <0>?
- The COR AMT <0>? conditional step determines if the data field Commitment Change Amount is a non-zero amount
- If True (Yes) the next step is Ready for Owner?
- If False (No) the next step is Comm Chng Items Mssng / Zero
Comm Chng Items Mssng / Zero
- The previous conditional step has determined that this Change Order Request is missing a commitment change or has a change amount of $0.
- The process initiator can amend this by selecting Yes for the field Is this a ZERO Dollar COR?
- Changing this to "Yes" will allow for a zero dollar COR
- Once this is fixed and the Submit action is taken next is a conditional step Zero Dollar Tot COR?
Zero Dollar Tot COR?
- The Zero Dollar Tot COR? conditional step determines the path process will take based on if the Data Field Is this a ZERO Dollar COR?: has been marked “Yes” or "No" in the previous step.
- If True (Yes) the next step is Ready for Owner?
- If False (No) the next step is COR AMT <0>?
Ready for Owner?
- The Ready for Owner? conditional step determines the path process will take based on if the Data Field Ready for Owner Action? has been marked “Yes” or "No" in the previous step.
- If you are ready for Owner's Action, the Vendor Supporting Documentation is Required for processing.
- If True (Yes) the next step is A/E on Project?
- If False (No) the next step is Initiator Hold.
Initiator Hold
- The Initiator Hold step allows the Process Initiator review the process, and fill out required fields.
- When the Submit action is taken the next step is A/E on Project?
A/E on Project?
- The A/E on Project? conditional step determines the path process will take based on if the Data Field A/E On Project? has been marked “Yes” or "No" on the process.
- If True (Yes) the next step is A/E Review
- If False (No) the next step is PM Approves/Rejects & Verify Funding.
A/E Review
- The A/E Review step allows the A/E Lead to review the process.
- If the Submit action is taken the next step is PM Approves/Rejects & Verifies Funding.
- If the Revise action is taken the next step is Initiator Revise & Resubmit
Initiator Revise & Resubmit
- The Initiator Revise & Resubmit step allows the Process Initiator review the process, and fill out required fields.
- When the Resubmit action is taken the next step is A/E on Project?
PM Approves/Rejects & Verifies Funding
- The Project Manager Reviews the process, verifies the available funding, and has the option to Submit, Revise, Reject, or Void.
- If Approve is chosen the next step is Budget Change Required.
- If Revise to A/E is chosen the next step is A/E Review.
- If Revise to Contractor is chosen the next step is Initiator Revise and Resubmit.
- If Void is chosen the next step is Finish and the process' status is set to Void.
Budget Change Req'd
- The Budget Change Req’d? conditional step determines the path process takes based on if the Data Field Budget Changehas been marked “Yes” in a previous step.
- Will this change require use of project contingency or an increase in the overall budget?
- If True (Yes) the next step is Program Manager Review and Approval.
- If False (No) the next step is COR Hold for GC-CO.
Program Manager Review and Approval
- The Program Manager reviews the process and takes an action to Void, Submit, or Revise.
- If Submit is chosen the next step is COR Hold for GC-CO
- If Revise is chosen the next step is PM Approves/Rejects & Verifies Funding
- If Void is chosen the next step is Finish and the process' status is set to Void.
Finish
