Common Elements Used When Managing Contract Agreements
Field or Control |
Description |
---|---|
Activity Status |
The current status for the step. When you add the agreement to the contract, the status is automatically set to Not Started. The step owner or contract administrator can use this status to track the progress of the step. Values are:
The Last User to Update and Last Update Timestamp fields are updated each time the status is changed. The system also records the status change, and if the step is set up to notify interested parties with status changes, then the change triggers workflow notifications. This notification occurs the next time the system runs the Workflow Notifications process. |
Clause Assignments agreement clause assignments |
Click to access the Assign Agreement Clauses Page, where you can select a clause for this agreement. |
Compliance Status |
The system displays the current status for the agreement. The initial value for this field is Not Set. Values include:
With each change of status, the system updates the Last User to Update and Last Update Date/Time fields. The system also records the status change, which triggers workflow notifications if the agreement is set up to notify interested parties with status changes. The notification occurs the next time the system runs the Workflow Notifications process. |
Due Date |
The date on which the step should be completed. You set this date when the agreement is added to the contract and you can base it on the target date of the agreement. You can change the due date on the Contract Maintenance pages. |
Financial Implication |
Enter a statement that relates to the financial implication if an agreement is compliant or not compliant. The statement can describe whether a bonus is paid or a penalty assessed if the agreement is met or not met. The system displays the financial implication on the contract if the agreement is selected. The actual bonus payment or collection for the penalty is a manual process. |
Include In Contract Document |
Select to include this agreement and its associated clauses on the purchasing contract when you author the contract document and dispatch it to the supplier. You can set up the agreement so that it serves only as an internal reminder to collect certain documentation or to perform steps before the completion of the contract. In these cases, the information should not be sent to the supplier or used in the wording of the contract document. |
Last User to Update and Last Updated On |
Displays the last user to update the status of the agreement and the date. |
Method or Verification Method |
The verification method used to indicate the task has been completed. Methods include:
|
Metric ID and Metric Description |
The metric ID that the system is using to track performance against the agreement. The field is available when the value in the Result Type field is Metric. Values for the field include:
For a definition of each value, see Metric Measurement Types. |
Negotiated Result |
When you select a result type other than None, this field becomes available. The negotiated result is the expected outcome of the agreement and represents the value of that outcome. The value for this field depends on the option you selected in the Result Type field. If you selected:
|
Notification Assignments |
Click to access the Agreement Notification Page, where you can assign the criteria by which the system sends notifications. Notifications can be sent for an agreement, verification steps, or both. When supply-side updates of agreement activities (deliverables) are enabled, you can define the notification for an external user ID. The supplier can then be notified using an e-mail that contains a URL and provides the supplier access to the specific deliverable through the supplier portal. |
Notification Comments |
Enter up to 254 characters as a description of the agreement that the system uses when it sends notifications. When notifications are external they appear in the agreement notifications sent to the supplier. Text that appears in the workflow notification worklist, if workflow is set up for the agreement. |
Perf Tolerance (performance tolerance) |
The tolerance allowed for a measurement. You establish this value when you assign the agreement to the contract on the Contract Header Agreement Assignments Page. For example, if you selected Metric in the Result Type field, and your negotiated results is 95 percent, then a five percent performance tolerance for on-time deliveries implies that 95 percent or better is acceptable, between 90 and 95 percent is considered a warning condition, and below 90 percent is unacceptable. The system can use the resulting actual values during procurement history calculations against these targets to determine whether warning or unacceptable performance notifications should be sent to interested parties. See Metric Measurements. |
Result Type |
Indicates how you are measuring the results of the agreement. If you selected a predefined agreement code, the system displays the default value from that code. When any result type except None is selected, the system provides a Negotiated Result field. Values include:
|
Step or Verification Step |
This is the step that defines the order in which verification is completed. The system begins the sequence number with 10, but you can change the sequence value to maintain the order when you insert new rows. You should leave gaps between the step numbers in case you want to insert additional verification steps at a later date. Verification steps define the criteria necessary to fulfill the agreement. After you define information for any field for the step, the system assumes you are adding verification steps to the agreement. You can delete steps on an existing contract without affecting the basic agreement. The system uses the step value to help order and locate specific verification requirements. |
Step Owner or Verification Step Owner |
The name of the person assigned this task and responsible for verifying that the step was completed. The owner can be either an internal or external person. The owner does not have to be associated to a user ID. Verification could include the step owner collecting documents or notifying the contract administrator whether a step is compliant. Note: To update the status or information for external users, the user must be listed on the Notification Assignments page and have update access to the verification step. This ensures that external users are notified and provides access for multiple external users to individual verification steps. For additional information about maintaining external users, see Maintaining Supplier Contact Information, External Users and Document Collaboration, and Understanding Contract Deliverable Verification Steps. |
Target Date |
The date by which the terms of the agreement must be completed to be compliant. You enter the date when you assign the agreement to the contract. Or, you can let the system automatically determine the date based on when an existing agreement code is selected. The date is based on the contract start or end date, or a specified number of days prior to or past the contract start or end date. Methods include:
|
Upload a File and Upload Another File |
Upload one or more documents by clicking the Upload a File link. After a file has been attached to the verification step, the Attachments section appears at the bottom of the page. You can add additional attachments by clicking the Upload another File link. |
Version |
Displays the version of the contract. Versions enable you to create and maintain multiple versions of the contract in the system. Versions provide a snapshot of the contract at a point in time and make it easier for you to view information in older contract versions. |