Architect's Supplemental Instructions Business Process
Architects use the Architect's Supplemental Instructions (ASI) business process to distribute instructions or design-related changes to the project team.
Characteristics
This is a Project-level business process with a workflow, provided in the system template.
Record Statuses
| Status | Resulting State |
|---|---|
| Acknowledged | terminal |
| Canceled | terminal |
| Closed | terminal |
| Awaiting_Review | non-terminal |
| Contractor_Review | non-terminal |
Workflow
The default workflow for the Architect's Supplemental Instructions business process is set up in a certain way; however, it may be used differently by your organization. Typically, a user with the necessary permissions can create the record and either move it directly to the end step or send it to others for review or approval. The recipients in the second step can approve or reject the record or send it on to others.
Related Processes
The Architect's Supplemental Instruction business process might create the following business processes: Change Request
The Architect's Supplemental Instruction business process might be created by the following business processes: Not applicable
Creating an Architect's Supplemental Instructions Record
Create an Architect's Supplemental Instructions record by navigating to Field Management / Architect's Supplemental Instructions on the Project/Shell tab, or from the Tasks log on the Home tab or relevant Project/Shell tab. Act on an existing Architect's Supplemental Instructions task that has been assigned to you from the Tasks log.
Complete the Architect's Supplemental Instructions form and attach related documents, if needed. After completing the form, select Send, and select an action in the Workflow Actions list to determine the next step in the workflow. Select Send to route the form to the next assignee.
Note:
You must enter a value in all required fields (*) before you can save the form.- Go to your Project tab, and switch to User mode.
- In the left Navigator, select Field Management, and then select Architect's Supplemental Instructions.
- On the Architect's Supplemental Instructions page, select Create. Complete the form. You can select Save at any time to save a draft version of the form. Draft versions are stored under Drafts.
- To add attachments, go to the Attachments tab, and select Attach Files
.
- After completing the form, select Send.
- On the Workflow Action Details tab, select who should receive this BP.
- If permitted, you can add users to the CC list. These users will receive a notification about this BP but are not assigned a task.
- If permitted, you can select lists of members in the Contact List section. These members also receive a notification about this BP but are not assigned a task.
- If permitted, you can adjust task due dates for all users, or set individual task due dates for each assignee.
- Select Send.
- In the Notification window, review the content, and select OK.
The record moves to the next step in the workflow.
Completing the Architect's Supplemental Instructions Form
Key Information
Key information from the organization issuing this ASI
| Field Name | Access | Description |
|---|---|---|
| Title | Required | Enter a title. |
| ASI Issuance Date | Editable | Date that the architect issued the ASI |
| AE Project Number | Editable | Architect's or Engineer's project number |
| ASI Number | Editable | ASI number from the project architect |
Distribution
ASI distribution quantities
| Field Name | Access | Description |
|---|---|---|
| Architect Copies | Editable | ASI copies to the architect |
| Owner Copies | Editable | ASI copies to the owner |
| Field Copies | Editable | ASI copies to the field |
| Contractor Copies | Editable | ASI copies to the contractor |
| Consultant Copies | Editable | ASI copies to the consultant |
| Other Copies | Editable | ASI copies to the other parties |
Description
Instructions and drawings that pertain to this ASI. This information might appear in formal printouts of this ASI.
| Field Name | Access | Description |
|---|---|---|
| Detailed Description | Editable | Detailed information about the short-description field. The field size can be expanded. |
| Drawings | Editable | A list of drawings related to the project |
Architect Information
Details of the Architect for this ASI
| Field Name | Access | Description |
|---|---|---|
| Legal Vendor Name | Required | Lists the legal vendor name if the vendor name is different from the vendor's full legal business name, the vendor has a name longer than 50 characters, or both. |
| Full Name | Editable | Full name of the primary contact |
| Vendor Contact Phone | Required | Phone number of the main vendor contact |
| Contact Email | Required | Contact email address for the main vendor |
| Address | Editable | Street address, P.O. box, apartment, suite, unit, building, floor, and so on. Do not include the contact's name. |
| City | Editable | City |
| State/Province | Editable | State or province |
| State/Province - Other | Editable | If selecting a country without defined states, provinces, or regions, this field provides additional information. |
| Country | Editable | Country |
| Zip/Postal Code | Editable | ZIP Code or postal code |
Reference Contract Details
Details about the referenced contract relevant to the ASI
| Field Name | Access | Description |
|---|---|---|
| Contract | Editable | Contract that is a reference to this record |
| Vendor Name | Editable | Name or nickname for this vendor. This field must be unique to each vendor. This name will be the primary way this company is identified in the system. |
| Effective Date | Editable | The date on which the contract takes effect |
Cost & Schedule Information
Information about the potential cost and schedule impact of this ASI
| Field Name | Access | Description |
|---|---|---|
| Cost Impact | Editable | Indicates whether there is a cost impact |
| Schedule Impact | Editable | Indicates whether there is a schedule impact |
| Owner Estimate | Editable | If there is a cost impact, this field shows the total amount of the cost impact. |
| Est. Schedule Impact (Days) | Editable | If the schedule is impacted, this field indicates the number of days that impact the schedule. |
| Cost Impact Notes | Editable | If there is a cost impact, this field describes the reason. |
| Schedule Impact Notes | Editable | Description of why the schedule is impacted, if a schedule impact is indicated. |
| Create a Change Request? | Editable | If selected, automatically create a change request upon approval of this record. |
| Change Request Record | Editable | Link to the created Change Request record, after it is created |
Record Information
System information about this record
| Field Name | Access | Description |
|---|---|---|
| Record Number | Read-Only | System-assigned record number |
| Status | Read-Only | Record status for a workflow BP record is based on the workflow action preceding the current workflow step. |
| Creator | Read-Only | Creator of this record |
| Creation Date | Read-Only | Date that the record was created |
| Record Last Update Date | Read-Only | Date that the record was last updated |
| Business Process Record URL | Read-Only | A shareable link to this record, for anyone with the necessary permissions |
| Project Number | Read-Only | Unique Project Number |
| Project Name | Read-Only | Name of the project |