Versions Compared

Old Version 16

changes.mady.by.user Unknown User (robertbr@mit.edu)

Saved on

compared with

New Version 17

changes.mady.by.user Unknown User (monzione@mit.edu)

Saved on

Key

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

...

Deck of Cards
id6.01
Card
labelSummary

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.

Card
labelProcess Map

Image RemovedImage Added

Card
labelStep Descriptions

Toggle Cloak
1. Start/Initiation

Cloak
  • Started by the Contractor or the Project Manager.

Step No.Step NameDescription
1Brief Description of ChangeEnter a description of the change.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).
2Is 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.
32Ready for Owner ActionIf the COR is ready for processing as part of a GCCO indicate by answering Yes.
34A/E on ProjectIf an A/E is on the project indicate by answering Yes.
5Brief Description of ChangeEnter a description of the change.
46Time Extension Requested (in Days)Indicate the time extension that is required for this GCO. You may indicate 0 if there is no impact to the schedule.
57Vendor's Supporting DocumentationAdd any documentation that supports the change request.
68CommitmentYou 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.
79Date of ChangeIndicate the date of the change.
810Reason CodeIndicate the reason for the change.
911Justification for the ChangeIndicate the justification for the change.


The next step is Ready for Owner?

Toggle Cloak
2. Ready for Owner?

Cloak
  • 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” in a previous step.
  • If True (Yes) the next step is Letter of Release?
  • If False (No) the next step is Initiator Hold.

Toggle Cloak
3. Initiator Hold

Cloak
  • The process initiator completes the Change Order Request and takes the Submit action.
  • The next step is Letter of Release?

Toggle Cloak
4. Letter of Release?

Cloak
  • The Letter of Release? conditional step determines the path process will take based on if the Data Field “Requesting Letter of Release?” has been marked “Yes” in a previous step.
  • If True (Yes) the next step is PM Approves/Rejects & Verifies Funding.
  • If False (No) the next step is A/E Review.

Toggle Cloak
5. A/E Review

Cloak
  • A/E Lead reviews the process and takes the Submit action.
  • The next step is PM Approves/Rejects & Verifies Funding.

Toggle Cloak
6.Initiator Revise & Resubmit

Cloak
  • The initiator reviews the process, fills out the required fields and takes the Resubmit option.
  • The next step is Letter of Release?

Toggle Cloak
7. PM Approves/Rejects & Verifies Funding

Cloak
  • The Project Manager Reviews the process, verifies the available funding, and has the option to Submit, Revise, Reject, or Void.
  • If Submit is chosen the next step is Budget Change Required.
  • If Revise is chosen the next step is A/E Review.
  • If Reject is chosen the next step is Initiator Revise and Resubmit.
  • If Void is chosen the next step is Finish.

Toggle Cloak
8. Budget Change Req'd

Cloak
  • The Budget Change Req’d? conditional step determines the path process takes based on if the Data Field “Budget Change” has been marked “Yes” in a previous step.
  • If True (Yes) the next step is Program Manager Review and Approval.
  • If False (No) the next step is COR Hold for GC-CO.

Toggle Cloak
9. Program Manager Review and Approval

Cloak
  • The Program Manager reviews the process and takes an action to Void, Submit, or Revise.
  • If Void is chosen the next step is Finish.
  • If Submit is chosen the next step is COR Hold for GC
  • If Revise is chosen the next step is PM Approves/Rejects &  Verifies Funding

Toggle Cloak
10. COR Hold for GC-CO

Cloak

The COR Hold for GC-CO Step will hold all Change Order Requests until they are bundled with the Change Order Process and the process is approved.  Once the Change Order process is approved the attached Change Order Request Processes will automatically take the Code Complete action.

The next step is SAP Hold Step.

Toggle Cloak
11. SAP Hold Step

Cloak
  • Hold step for SAP Processing.
  • The next step is Finish.

12. Finish