|
|
| Line 1: |
Line 1: |
| {{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}} | | {{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}} |
|
| |
|
| {{#ev:youtube|JRNan7CgZpI|960|center|A video tutorial on creating a driver profile within BorderConnect.}} | | {{#ev:youtube|JRNan7CgZpI|960|center|How to create a driver profile in BorderConnect}} |
|
| |
|
| [[File:Adddriverpage1.png|360px|thumb|right|Viewing the '''Add New Driver''' page]]The '''Add New Driver Page''' is a page in [https://borderconnect.com BorderConnect eManifest software] where the user enters the information to create a new Driver Profile. It can be accessed in the following ways: | | [[File:Adddriverpage1.png|360px|thumb|right|The Add New Driver page in BorderConnect]] |
| *From the Manage Data menu by clicking 'Create Driver'.
| |
| *From the [[Driver_Details_Page_(ACE_and_ACI_eManifest)|Driver Search Page]] by clicking the 'Create Driver' button.
| |
| *From the Add Driver/Crew for ACE eManifest Page by clicking the 'Create Driver' button.
| |
|
| |
|
| ;Save Button
| | This guide walks through how to create and configure a '''Driver Profile''' in BorderConnect. Driver profiles are used across ACE and ACI eManifest workflows and allow the system to: |
| :Saves currently entered information to a new Driver Profile. Can only be used if all required fields have been filled out. Clicking on this button will create the Driver Profile and bring the user to the [[Driver_Details_Page_(ACE_and_ACI_eManifest)|Driver Details Page]].
| |
| ;Cancel Button
| |
| :Cancels the attempt to create a new Driver Profile. Clicking on this button will disregard all entered data and bring the user to the [[Driver_Search_Page_(ACE_and_ACI_eManifest)|Driver Search Page]].
| |
| ;Clear Button
| |
| :Clears all fields on the page so that the user may enter other data instead. | |
|
| |
|
| == General Information ==
| | * Assign drivers to manifests and shipments |
| | * Auto link PARS, PAPS, and in bond shipments |
| | * Send real time clearance notifications |
| | * Maintain compliance ready driver data |
|
| |
|
| In this section of the page the user can enter the basic Driver Profile information. Please refer to the legend at the bottom of the page for guidance on which fields are required under what circumstances.
| | You can open the '''Add New Driver''' page in three ways: |
|
| |
|
| ;Driver Number
| | * '''Manage Data → Create Driver''' |
| :Unique number to identify the driver. Usually an employee number can be used if applicable. Otherwise driver's initials are also acceptable. This field is always required.
| | * '''Driver Search Page → Create Driver''' |
| | * From the '''Add Driver/Crew''' screen within an ACE eManifest |
|
| |
|
| ;First Name
| | == Page Controls == |
| :Driver's first name. This field is always required.
| |
|
| |
|
| ;Middle Name or Initial
| | {| class="wikitable" |
| :Driver's middle name or initial. This field is always optional.
| | ! Button |
| | ! Function |
| | |- |
| | | Save |
| | | Creates the driver profile once all required fields are completed |
| | |- |
| | | Cancel |
| | | Discards all entered data and returns to Driver Search |
| | |- |
| | | Clear |
| | | Empties all fields so new data can be entered |
| | |} |
|
| |
|
| ;Last Name
| | == General Driver Information == |
| :Driver's last name. This field is always required.
| |
|
| |
|
| ;Gender
| | This section captures the core identity and compliance details for each driver. |
| :Driver's gender. Can be selected using the drop down menu. This field is required when the Driver Profile will be used on ACE eManifests and the driver does not have a FAST Card or ACE ID. Otherwise it is optional.
| |
|
| |
|
| ;Date of Birth
| | {| class="wikitable" |
| :Driver's date of birth. Can be entered in the text field in the format mm/dd/yyyy or using the calendar tool. This field is required when the Driver Profile will be used on ACE eManifests and the driver does not have a FAST Card or ACE ID. Otherwise it is optional.
| | ! Field |
| | ! Required |
| | ! Description |
| | |- |
| | | Driver Number |
| | | Always |
| | | Internal identifier such as employee number or initials |
| | |- |
| | | First Name |
| | | Always |
| | | Legal first name of the driver |
| | |- |
| | | Middle Name or Initial |
| | | Optional |
| | | Middle name or initial if applicable |
| | |- |
| | | Last Name |
| | | Always |
| | | Legal last name of the driver |
| | |- |
| | | Gender |
| | | Conditional |
| | | Required if no FAST or ACE ID is provided for ACE manifests |
| | |- |
| | | Date of Birth |
| | | Conditional |
| | | Required if no FAST or ACE ID is provided for ACE manifests |
| | |- |
| | | Citizenship |
| | | Conditional |
| | | Must match travel documents used at the border |
| | |- |
| | | Terminal or Office |
| | | Always |
| | | Location the driver is assigned to within your company |
| | |- |
| | | ACE ID or FAST ID |
| | | Conditional |
| | | Required if driver is FAST approved and used in ACE |
| | |} |
|
| |
|
| ;Citizenship
| | '''Tip:''' If your terminal or office is missing, it can be created from the [[Company Details Page]] using the '''New Terminal''' option. |
| :Driver's citizenship. Can be selected using the drop down menu. If the driver is a dual citizen it is recommend to enter the citizenship that matches the documentation that will be presented at the border. This field is required when the Driver Profile will be used on ACE eManifests and the driver does not have a FAST Card or ACE ID. Otherwise it is optional. | |
|
| |
|
| ;Terminal/Office
| | == Notification Settings == |
| :The terminal or office that the driver should be assigned to. Can be selected from the terminals list using the drop down menu. This field is always required. Please note that if the desired terminal or office is not listed, more can be created from the [[Company Details Page]] by clicking the New Terminal button.
| |
|
| |
|
| ;ACE ID / FAST ID
| | [[File:driver-notification-options.png|800px]] |
| :Used to indicate a driver's FAST ID or ACE ID. If a driver is FAST approved the FAST Card number (number starting with 4270) should be entered in the text field. Otherwise an ACE ID can optionally be entered here. If an ID has been entered in the text field, the type (ACE ID or FAST ID) must be selected using the drop down menu. This field is only required when the driver is FAST approved and the Driver Profile will be used on ACE eManifests. | |
|
| |
|
| == Notification Options ==
| | Driver profiles can automatically notify drivers when shipments clear customs. |
|
| |
|
| In this section of the page the user can specify options for the driver to be notified when their shipments have been cleared by the Customs Broker. The driver can receive ACI/PARS notifications or ACE notifications or both.
| | Notifications improve dispatch flow by letting drivers know when loads are ready to cross. |
|
| |
|
| [[File:driver-notification-options.png|800px]]
| | === Supported Notification Types === |
|
| |
|
| | {| class="wikitable" |
| | ! Notification Type |
| | ! Trigger |
| | ! Requires |
| | |- |
| | | ACI or PARS Alerts |
| | | When PARS is accepted or linked to driver |
| | | PARS Checking subscription |
| | |- |
| | | ACE Alerts |
| | | When PAPS or QP In Bond is accepted |
| | | ACE eManifest |
| | |} |
|
| |
|
| ACI/PARS notifications only work for customers subscribing to BorderConnect's PARS Checking software. The notification will be sent out when a PARS Shipment gets accepted on an ACI eManifest for the driver. It will also be sent if an accepted PARS falls within a PARS Sequence for that driver.
| | All notification fields are optional. |
|
| |
|
| ACE notifications will be sent out when a PAPS or QP In-Bond shipment gets accepted on an ACE eManifest for the driver.
| | === Email Alerts === |
| | |
| All fields in this section are optional.
| |
|
| |
|
| ;Primary Email | | ;Primary Email |
| :Used to indicate an email address for the driver to receive notifications. The email address can be entered in the text field. The user should then select which type of notifications to send to the driver using the checkboxes for ACI/PARS notifications and ACE notifications. | | :Main email address for shipment clearance updates. Select ACI/PARS and or ACE alerts as desired. |
|
| |
|
| ;Secondary Email | | ;Secondary Email |
| :Used to indicate a second email address for the driver to receive additional notifications. As with the primary email, the email address can be entered in the text field. The user should then select which type of notifications to send to the driver using the checkboxes for ACI/PARS notifications and ACE notifications. | | :Backup email address for additional notifications. |
| | |
| | === SMS Text Alerts === |
|
| |
|
| ;Primary Cell Phone | | ;Primary Cell Phone |
| :Used to indicate a cell phone for the driver to receive notifications by text via SMS. The cell phone number can be entered (must include area code) into the text field. The cell phone carrier must then be selected using the drop down menu. The user should then select which type of notifications to send to the driver using the checkboxes for ACI/PARS notifications and ACE notifications. | | :Driver’s mobile number for SMS alerts. Carrier selection is required. |
|
| |
|
| ;Secondary Cell Phone | | ;Secondary Cell Phone |
| :Used to indicate a second cell phone for the driver to receive notifications by text via SMS. As with the primary cell phone, the cell phone number can be entered (must include area code) into the text field. The cell phone carrier must then be selected using the drop down menu. The user should then select which type of notifications to send to the driver using the checkboxes for ACI/PARS notifications and ACE notifications. | | :Optional backup mobile number for SMS alerts. |
| | |
| | == Best Practices for Driver Profiles == |
| | |
| | * Use legal names exactly as on border documents |
| | * Always assign a terminal or office |
| | * Enter FAST ID for FAST approved drivers whenever possible |
| | * Enable notifications to reduce dispatcher workload |
| | * Keep profiles updated when drivers change contact info |
| | |
| | == Summary == |
| | |
| | Driver Profiles are a core component of BorderConnect workflows. Once created, they allow: |
| | |
| | * Faster manifest creation |
| | * Automated shipment linking |
| | * Real time clearance communication |
| | * Improved compliance accuracy |
| | |
| | Setting them up correctly ensures smoother border crossings and fewer operational delays. |
|
| |
|
| [[Category:BorderConnect Software User Guide]] | | [[Category:BorderConnect Software User Guide]] |