Related articles

What is a mail-based process?

Learn how Aconex Dashboards define a process

In Aconex, a typical construction process like an RFI or Change Request is managed using Mail. A process contains multiple mails, often between different organizations, and using different mail types. We can define and track an entire mail thread process with a single identifier. We call this a mail-based process.

Each process is configured and captured at a project level and uniquely identified by a process number. The process number is obtained from the reference number of all mails in the process.

A process is defined by:

Process Start: The mail type used to start a process. The first mail in the thread. 

Process End: The action or mail type used to end the process. For example, an RFI process might end when a Response to RFI mail type is used in a reply, or when the initiating mail is closed out. A process can be set to end after several days of inactivity automatically.

The following processes come pre-configured with Aconex Dashboard. These can be edited or removed, and new processes can be created.

  • Request For Information
  • Variation
  • Progress Claim
  • Non-Conformance Report
  • Technical Query
  • Design Query
  • Change Request
  • Extension of Time


Example

Below is an example of a change request process, where the process is started by a Change Request mail type. The process ends when the initial mail is closed out.

Processes are configured at a project level - not to a specific organization.  This means when an organization views a particular process, they always look from the project perspective. 
In this example, the consultant organization views the process as a Change Request process, even though the mail it received is a Request for Information. This is because the consultant is involved in the overall Change request processes, and the RFI is part of that process.