Contractor to Company - created by company

Contractor to Company communications can be created in the Company Portal by a company user on behalf of the contractor, for example if the Contractor Portal is not used. Users with the following contract roles can create this type of communication:

• Contract Owner

• Contract Administrator

• Company Representative

A typical lifecycle of a Contractor to Company communication which has been created on behalf of the contractor is:

1. The communication is created in the Company Portal by a company user.

2. The communication is published immediately on creation.

The following diagrams show more detailed workflows.

Communication requires agreement

Example: The Contractor Portal is not in use, and a company user needs to store in AVEVA Contract Risk Management a communication received in another system, and record that the company agreed to the communication.

The Required Response option of the communication template is set to Agreement Only or Agreement and Reply.

The possible communication states of a Contractor to Company communication, created by the company on behalf of the contractor, which requires agreement are:

• Awaiting Agreement from Company

• Agreed

• Not Agreed

• Rejected

Communication does not require agreement

Example: The Contractor Portal is not is use, and a company user wants to log communications received in another system.

The Required Response option of the communication template is set to None or Reply Only.

The possible communication states of a Contractor to Company communication which does not require agreement are:

• Approved

• Rejected