# BISCIT Delivery Planning - User Guide
## Overview
**BISCIT Delivery Planning (BDP)** is the final piece in the puzzle sitting between **Epicor Kinetic Warehouse (EKW)** and **Proof of Delivery (POD)**. **BDP** offers proactive planning and end to end visibility from order to delivery.
The drag and drop functionality allows users to react to changing priorities quickly enhancing your planning capabilities. Increased visibility promotes earlier planning, optimizing logistics resources for greater efficiency. Consequently, it elevates the customer service experience by ensuring timely deliveries, every time.
With route optimization and seamless integration with EKW’s Delivery Staging feature, this enables your team to strategically load customer shipments onto delivery vehicles in reverse delivery sequence unlocking unprecedented efficiencies and streamlining your distribution operations.
As it is fully integrated to POD, it ensures that delivery instructions and optimized routes are effortlessly communicated. POD’s capture of ‘sign on glass’ signatures and images provide a seamless and efficient delivery confirmation experience.
**BDP** is purpose built for Epicor Kinetic, with real time integration resulting in a singular, reliable source of truth, ensuring data consistency and integrity across your operations.
***
## General Information
### Setting Up IDP Login for the BDP Application
To configure IDP login for the BDP application, follow these steps:
1. **Access Epicor Login**
* Go to .
* Log in and navigate to the **Admin** section.
2. **Manage Applications**
* Click **Manage Apps** in the **Apps** section of the Admin page.
3. **Edit the Target Application**
* Locate the application you need to log in to.
* Click the three dots (**⋮**) to the right and select **Edit**.
4. **Verify Reply URIs**
* Under **Reply URIs**, ensure the following URIs are registered:
* `https://bdp-pilot.biscit.com`
* `https://bdp-beta.biscit.com`
* `https://bdp.biscit.com`
* **Users that have BDP embedded in their Epicor environment:** Please insert the URL of your Epicor site as well, for example, if I have my BDP embedded on environment: , I will place `https://myepicorenv.co` exactly like that in the Reply URIs, same applies for the use of this URL in step 6.
5. **Enable Advanced Mode**
* In the top-right corner, click **Advanced Mode**.
* Go to the **Registered URIs** section.
6. **Check Logon and CORS Tabs**
* Ensure the **Logon** and **CORS** tabs contain the same URIs listed in step 4.
Following these steps will ensure proper IDP login configuration for the BDP application.
### DispatchPortalGroup Information
{% hint style="warning" %}
Ensure that all users that plan on operating in **BDP** (i.e. Moving data, optimizing runs) are added to a new “DispatchPortalGroup” security group.
1. After setting up with the steps below, and logging in for the first time, there will be a new security group called “DispatchPortalGroup”
2. Go to **user account and security maintenance.**
3. Enter the user to be assigned to the group.
4. Go to groups and ensure “DispatchPortalGroup” is an authorized group for the user
{% endhint %}
***
## Getting Started
1. Go to . For **Demo** please use the link below:
{% hint style="info" %}
If the user is using **BDP** for demo purposes, please use this link:
{% endhint %}
2. Agree to the **Terms of Service**.
3. Enter **Epicor** **server name** and click **Continue**.
4. Enter **User Name** and **Password**.
5. Select **Company** and **Site**.
6. Click **Log in**.
{% hint style="info" %}
This will start the CAB file install containing required services automatically
{% endhint %}
7. A pop up will appear saying the install has been successful.
1. Click **OK**, and the browser window will automatically close.
2. Continue to **Step 8**.
8. Regenerate the **Epicor Data Model** for your **Epicor environment**.
9. Refresh **Epicor application pool**.
10\. Log into **Epicor** and open the **Conversion Workbench** and run **Conversion 210**.
11\. Refresh the **Epicor application pool**.
12\. Log in to **BDP** to complete automated setup steps now that the services exist.
{% hint style="info" %}
️ Refer to the succeeding instructions to perform the final **Epicor checks**.
{% endhint %}
### Epicor Checks
{% hint style="danger" %}
️ The previous steps are the pre-requisite instructions for the following setup. Log into **Epicor** and perform some checks:
{% endhint %}
1. Open Site Maintenance.
{% hint style="info" %}
Ensure each site has an **address** and most importantly, a **Country** specified for the **address**, as this is not set by Epicor by default. This can be found under ‘Site Maintenance’, select your site, and drop down address.
{% endhint %}
2. Open User Account Security Maintenance and add users to the **DispatchPortalGroup** security group that has been automatically created during installation.
{% hint style="info" %}
Users that are not included this group will have **read-only** access in the portal. The user should now be all set up to start using **BDP** for the first time. Refer below on how to create data for **BDP**:
{% endhint %}
3. Ensure that users that are going to be accessing the BDP have access to user data within your Epicor environment.
{% hint style="info" %}
Users that do not have access to customer data will not be able to see any runs in the BDP.
{% endhint %}
4. Ensure that users that are going to be accessing the BDP have the ability to access api v1 calls within the Epicor environment. To do this:
1. Go to Epicor > User Account Security Maintenance.
2. Click 'System Access' to the navigation tree on the left.
3. Ensure the 'Allow API v1' checkbox is selected, if not, select it and click save.
{% hint style="info" %}
Users that do not have the ability to make API v1 calls will not be able to login to the application.
{% endhint %}
***
## How to create Data in BDP
{% hint style="info" %}
️Please refer to the following link to create data within BDP:\
{% endhint %}
## Login
1. Type in the **BDP** web address ( ) into the browser **Address** field, and hit **ENTER**.
2. Read the **Terms of Service**.
3. Once read and understood toggle the **I accept** switch to the right and click on **Continue**.
4. In the **Server** field, type in the license server url and click on **Continue**.
5. Enter the user credentials in the respective **User Name** and **Password** fields.
6. Click **Login**.
7. In the **Company Configuration** screen, choose the appropriate **Company** and **Plant** from the drop-down and click on **Log In**.
8. Once logged in, the user will be redirected to the **BDP** **Home** screen, where the **Dispatch Board** is also located.
a. Clicking on the **Advanced Filter** button allows the user to search using the following parameters:
1. Order Number
2. Customer Name
3. Part Number
b. The **Advanced Filter** button will appear to be highlighted in orange if a parameter has been selected.
c. The search parameters can be cleared by clicking the **Clear** button.
## **Moving Orders**
Users can move orders on the dispatch board using one of three methods:
### **Drag and Drop**
To move orders using drag-and-drop:
* Ensure the **Group By** filter is set to **Route** view.
* For **assigned orders**, expand the route card, then drag and drop the order to a new route or date.
* **Unassigned orders** can be moved without additional steps—simply grab the item from the left side of the card and drag it to the desired route or date.
* Dragging and dropping orders works at delivery level, meaning it will move all orders in a delivery.
### **Assign Route Button**
Alternatively, users can assign orders using the **Assign Route** button:
* Click the **Assign Route** button on the right side of the order card.
* Select the desired route and date.
* Click **Assign** to confirm the changes.
* You are able to assign whole routes at the top level of the card, or you can assign separate deliveries to new routes / dates as shown below when drilled down into the card.
* This view is available on the route view and the plant view, please note the plant view is a summarised version of the board and will only allow you to use this button at route level.
### **Run Page**
Users can also move orders via the **Run Page**:
* Click the order card to open the **Run Page**.
* Click the **pencil icon** on a delivery card to view all order releases assigned to that run.
* Select the **lines/releases** you wish to move.
* Click **Assign**, and the selected order lines and releases will be reassigned automatically.
* Once the page is opened, you are then able to move releases as a whole order, or by separate releases, as shown below
These methods provide a seamless and efficient way to manage order assignments.
## Comments
{% hint style="info" %}
Comments made in the **Internal Notes** section is specifically made for the dispatcher to note in making a delivery.
{% endhint %}
The BDP application allows users to add comments seamlessly across two key areas: the Run page and the Dispatch Board. These features enable effective communication and collaboration, helping users document, share, and reference important information directly within the application.
## Notes
You can access and edit two types of notes within the Dispatch Board: internal run notes and daily notes. Internal run notes provide a way to document specific details about a run, while daily notes allow users to add comments about a particular day or even a range of days, offering greater flexibility for planning and communication.
### Internal Notes
a. On the **BDP** **Home** screen, click on the comment box against a run.
b. An ‘Internal Note’ text box will appear that will allow the user to add a note against a run, once the note is complete, click save.
c. Once saved, the board will refresh and the note will be orange, indicating that there is an internal note against the run.
{% hint style="info" %}
️ NOTE: If you wish to have the internal note displayed above the run card, go to the menu > general settings, and turn on the ‘Use Note Cards’ toggle
{% endhint %}
### Daily Notes
a. On the **BDP** **Home** screen, click on the comment box against a day.
b. A comment modal will appear, allowing the user to specify a start date (the first day the note will apply), an end date (the final day the note will apply), and a note section to add details for a specific day or range of days. Click save once complete, and the board will refresh, and the selected dates with the note added will appear orange to specify that there is a note on that day.
### Run Page
a. On the **BDP** **Home** screen, select a **Run** to view it.
b. Click on the **notes** icon within a run to view the **Internal Notes**.
c. In the **Internal Notes** view, note the intended comments that a dispatcher will need while making their delivery.
Example 1:
Example 2:
c. Notes made under the **Internal Notes** will be noted as well in any packs under that run in **EPICOR**.
## Vehicle Management
{% hint style="info" %}
️ The Vehicle Management section of BDP allows the user to add new vehicles and edit existing vehicles in their fleet.
{% endhint %}
### Adding a new Truck
a. In the **Trucks** page, click on **New Truck** to initiate the creation of a new truck.
b. In the **New Truck** screen, input all the appropriate information to create the new truck.
| **Title** | **Information** |
| ----------- | ----------------- |
| ID | Input ID |
| Description | Input Description |
| Length | Input Length |
| Height | Input Height |
| Tare Weight | Input Tare Weight |
c. Click on **Create New Truck.**
### Editing a Truck
a. In the **Trucks** page, click on **pencil icon** beside a truck listing and edit the necessary information in the fields.
| **Title** | **Information** |
| ----------- | ----------------- |
| Description | Input Description |
| Length | Input Length |
| Height | Input Height |
| Tare Weight | Input Tare Weight |
c. Once done editing, click on **Update**.
d. An existing truck can also be deleted.
e. Click on **Delete Truck** to delete an existing truck.
### Adding Trailers
a. In the **Trailers** page, click on **New Trailers** to initiate the creation of a new trailers.
b. In the **New Trailers** screen, input all the appropriate information to create the new trailers.
| **Title** | **Information** |
| ----------- | ----------------- |
| ID | Input ID |
| Description | Input Description |
| Length | Input Length |
| Height | Input Height |
| Tare Weight | Input Tare Weight |
c. Click on **Create New Trailers.**
### Editing Trailers
a. In the **Trailers** page, click on **pencil icon** beside a trailers listing and edit the necessary information in the fields.
| **Title** | **Information** |
| ----------- | ----------------- |
| Description | Input Description |
| Length | Input Length |
| Height | Input Height |
| Tare Weight | Input Tare Weight |
c. Once done editing, click on **Update**.
d. An existing trailer can also be deleted.
e. Click on **Delete Trailer** to delete an existing trailer.
### Adding new Forklifts
a. In the **Forklifts** page, click on **New Forklifts** to initiate the creation of a new forklifts.
b. In the **New Forklifts** screen, input all the appropriate information to create the new forklifts.
| **Title** | **Information** |
| ----------- | ----------------- |
| ID | Input ID |
| Description | Input Description |
| Weight | Input Weight |
c. Click on **Create New Forklifts** **.**
### Editing existing Forklifts
a. In the **Forklifts** page, click on **pencil icon** beside a forklifts listing and edit the necessary information in the fields.
| **Title** | **Information** |
| ----------- | ----------------- |
| Description | Input Description |
| Weight | Input Weight |
c. Once done editing, click on **Update**.
d. An existing trailer can also be deleted.
e. Click on **Delete Forklifts** to delete an existing trailer.
## Route Management
{% hint style="info" %}
️ The Route Management page is where the user will be able to create **New Routes** and edit the said routes.
{% endhint %}
### Creating a new route.
a. In the **Route Management** page, click on the **New Route** to initiate the creation of a new route.
b. In the **New Route** screen, input all the appropriate information to create the new route.
| **Title** | **Information** |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Route ID | Input Route ID |
| Type |
Normal Route - A route that goes from the depot to the list of addresses.
Switch Route - A route that will go from the depot to a specified collection point, where deliveries on a run will be delivered from.
Remote Route - A collection point from the above switch route. Once the driver reaches the remote route, the deliveries on the run will originate from this point.
|
| Departure Time | Input Departure Time |
| Driver | Driver Name |
| Truck | Input Truck |
| Forklift | Input Forklift |
| Trailer | Input Trailer |
c. Click on **Create New Route.**
### Editing an existing route.
a. In the **Route Management** page, click on the **pencil icon** beside an existing route to edit it.
b. In the **Route** screen, all the details in an existing route can be changed.
| **Title** | **Information** |
| -------------- | ------------------------------------------------------ |
| Departure Time | Input Departure Time |
| Driver | Driver Name - A list of employees in the EPICOR system |
| Truck | Input Truck |
| Forklift | Input Forklift |
| Trailer | Input Trailer |
c. Once done editing, click on **Update**.
d. An existing route can also be deleted.
e. Click on **Delete Route** to delete an existing route.
## Settings
{% hint style="info" %}
️ The General Settings section allows the user to calibrate and setup BDP to fit the business needs.
{% endhint %}
### General Settings
a. In the **Settings** section, click on **General Settings**.
b. Set the necessary settings accordingly:
| **Title** | **Information** |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| App Version | Specifies the version the user is using for BDP. |
| Minimize Weekends |
This is a setting that will impact the Dispatch Board.
If the toggle is switched to the right, the Dispatch Board will load with weekends automatically minimized.
When the toggle is switched to the left, the weekends will be maximized like the weekdays.
|
| Unit system |
Allows the user to specify whether or not they would like to view data in Imperial or Metric system accordingly.
For example, if Metric was selected, it would display the vehicle weight/length in metres/kilograms.
If Imperial was selected, it would display in feet/pounds
|
| Decimal Accuracy | This will display the height/weight measurements to the amount of decimals specified, with maximum being 2 decimals. |
| Delivery Card Display Fields | Select which fields you would like to have displayed on the delivery card view on the run page. |
| Route Card Delivery Display Fields | Select up to 2 fields you wish to have displayed on the delivery cards while on the route view of the dispatch board. |
| Enabled Plants | Select which plants you wish to use the BDP. Selected Plants will have orders display on the dispatch board, where as deselected plants will not, even when new orders are created. Please note this is a company scoped setting. |
| Ship Via Mappings | Toggle on to Prioritise the Ship Routing Field over Ship Via Mapping when creating new orders and having them automatically mapped when in BDP. |
| Display run internal notes as cards in the dispatch board | Toggle on to display run internal notes as cards on the dispatch board. Allows users to see notes without the need to hover. |
| In Progress calculation method | Toggle on to see the In-progress status visible if one or more deliveries are shipped (regardless of status of others). Toggle off to see the In-progress status visible if one or more deliveries are shipped and all others are packed. |
c. Click **Save.**
### Company & Plant
a. In the **Settings** section, click on **Company & Plant**.
b. Choose the appropriate **Company** and **Plant** from the drop-down list.
c. Click **Save.**
### Routing
{% hint style="info" %}
#### **Important:** Obtaining an Azure Maps Key for Route Optimization
If you plan to enable **run optimization** within the BDP, you will need an **Azure Maps Key**. Follow the steps below to obtain one:
1. **Sign in to the Azure Portal**
* If you don’t have an Azure account, search for "Azure Portal" and click **Start your free account**.
* Follow the sign-up process by filling out your details.
* Once registration is complete, click **Go to Azure Portal**.
2. **Create an Azure Maps Account**
* In the Azure Portal, search for **Azure Maps Accounts** and navigate to the page.
* Click **Create**.
* Fill out the required details, including creating a new **Resource Group** to store the Maps account.
* Click **Review + Create**, then confirm the creation.
3. **Retrieve Your Azure Maps Key**
* Once the account is created, go back to the **Azure Maps Accounts** page.
* In the left-hand menu, select **Authentication**.
* Copy the **Primary Key** and enter it into your **Azure Maps Key** settings in the Dispatch Portal.
For information on pricing for Azure Maps for your region and currency, please see [Pricing - Azure Maps | Microsoft Azure](https://azure.microsoft.com/en-us/pricing/details/azure-maps/)
{% endhint %}
a. In the **Settings** section, click on **Routing**.
b. In the **Azure Maps Key** field, enter the the appropriate Azure Maps Key.
c. Click **Save.**
### Time Factors
a. In the **Settings** section, click on **Time Factors**.
| **Title** | **Information** |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OTS Delivery (minutes) | Input OTS Delivery (in minutes). This will add the minutes that have been entered against the delivery time for each one time ship to order delivery on a run. |
| Border Times (minutes) | Input Border Times (in minutes). This will add the minutes that have been entered against the delivery time for each border crossing that is present on a run. The minutes entered here will be doubled on optimisation to account for the return trip back through the border. |
| Skid Times (minutes) | Input Skid Times (in minutes). This will add the minutes that have been entered against the delivery time for each pallet on a run. A pallet will be grouped by a pack, so if there are 2 packs on a delivery, then it will be assumed that there are 2 pallets. |
| Unplanned Contingencies (minutes) | Input Unplanned Contingencies (in minutes). This will add the minutes that have been entered against the delivery time for unplanned contingencies (e.g. Stopping for food, stopping for the bathroom etc.). |
| Break times (minutes) | Input Break times (in minutes). This will add the minutes that have been entered against the delivery time for break times the driver is entitled to. This will account for how many break minutes per hour the driver is entitled to. |
| Assumes Stop Duration (minute) | Input Assumes Stop Duration (in minute). This will add the minutes that have been entered against the delivery time for assumptions on stop duration (e.g. Stopping for fuel, customer stop times etc.). |
c. Click on **Save**.
### Cost Factors
a. In the **Settings** section, click on **Cost Factors**.
| **Title** | **Information** |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Vehicle Cost (dollars) | Input Vehicle Cost (in dollars). This will be an estimate of the cost of the vehicle. (Truck Tyres, Vehicle Maintenance, Cleaning etc.) |
| Fuel Cost (dollars) | Input Fuel Cost (in dollars). This will be an estimate of the cost of fuel per km. |
| Labor Cost (dollars) | Input Labor Cost (in dollars). This will estimate the cost of labor per hour. For example, if a run is 6 hours, it will be the inputted value times 6. |
| Miscellaneous Cost(dollars) | Input Miscellaneous Cost(in dollars). This will be an estimate of miscellaneous cost per run. |
c. Click on **Save**.
### Ship Via Mappings
{% hint style="info" %}
When an order has been created in **EPICOR**, the **Ship Via Code** found in the order will be consistent to the mapping being created in **BDP** under **Ship Via Mappings** page. This will automatically assign routes of orders created in **EPICOR**.
{% endhint %}
a. In the **Settings** section, click on **Ship Via Mappings**.
a. In the **Settings** section, click on **Ship Via Mappings**.
b. Click on **+New Mapping**.
c. Select a **Ship Via** and **Route ID** using the drop-down boxes.
d. Click on **Create New Ship Via Mappings.**
## Run Page
### How to Go to Run Page.
a. Click on the **Home** section to view the **Dispatch Board.**
{% hint style="info" %}
Runs will be visible here in a calendar view on which day a run is assigned to. Run - a route assigned on a specific day. A run may also be spread across multiple days if needed.
{% endhint %}
b. click on a run to open the **Run Page**.
b. In the **Run Page**, user can edit the **Route Details.**
### Editing Route Details.
a. Beside the **Route Details** header, click on the **edit icon**.
b. In the **Edit Run Details** screen, any of the details can be edited by selecting a new item from the respective drop-down.
{% hint style="info" %}
A **Run** has a default value for all of its details once it has been created in the **Settings** section. In the scenario that a user has to edit details, due to a driver being unable to do the route, a vehicle can’t be used, etc. these can be edited in the **Edit Run Details** page.
{% endhint %}
| **Title** | **Information** |
| --------- | ----------------------------------------- |
| Driver | Edit Driver by selecting from drop-down |
| Truck | Edit Truck by selecting from drop-down |
| Forklift | Edit Forklift by selecting from drop-down |
| Trailer | Edit Trailer by selecting from drop-down |
c. Click on **Update** to complete any amendments to the **Route Details**.
### Optimising Route.
a. In the **Run Page**, estimates are calculated accordingly for **Travel Time** and **Cost** will be seen here when **Time Factors** and **Cost Estimates** have been set up in the **Settings** section.
b. Click on the **Reoptimise Route** button and click **YES** to calculate the **Travel Time** and **Est. Cost**.
### Editing a Delivery/Release.
a. In the **Run Page,** under the **Deliveries**, click on the **edit icon**.
b. Tick the appropriate order checkbox to edit the order.
{% hint style="info" %}
A single or multiple orders can be edited once the appropriate order checkboxes have been ticked.
{% endhint %}
c. Click on the calendar icon beside the date to choose a different delivery date.
d. Choose a new route in the drop-down.
e. Click on **Update Selected Releases** to complete the amendments to the selected orders.
### Viewing an Order Timeline
a. Under **Deliveries**, click on the **headset** icon beside an order.
b. This will be pull up the **Order Timeline** view
| **Title** | **Information** |
| ------------------------- | ------------------------------------------------------------- |
| Order Created | When an order is made and submitted to Epicor |
| Order Released | When the first item is release to the material queue |
| Order Allocated to picker | When an employee has picked an order and is allocated to them |
| Picking | Shows how many items have been picked |
| Order Packed | Will indicate if an order has a pack number and a pack ID |
| Order Shipped | When an order has been shipped |
## Dock Management
The **Dock Management** feature enables users to assign runs to specific docks, providing greater visibility and control over dock scheduling and activity. This functionality supports efficient coordination by allowing users to define key details such as estimated arrival and departure times and truck arrival status.
Once a run is assigned to a dock, it is displayed on the **Dock Management** board, which visually represents scheduled activity within time blocks. This allows teams to easily monitor and manage dock usage, helping to streamline operations and reduce scheduling conflicts.
This documentation will guide you through the key aspects of the Dock Management feature, including how to assign docks, view scheduled runs, and navigate the Dock Management board.
### Creating dock management data
1. Navigate to the **Run Page** for a run that is assigned to a valid route.
2. Locate the **Dock Details** section and click the **pencil icon** to edit the dock assignment.
3. In the **Edit Dock Details** modal, provide the following mandatory information:
* **Dock Number**: The dock to which the run will be assigned.
* **Load Time**: The estimated time required to load the truck once it arrives at the dock.
4. After entering the dock details, the system will generate:
* A **Reference Number**: A unique identifier that can be used as a customer reference.
* An **Arrival Date/Time**: The latest time the truck should arrive to meet the scheduled departure.
* A **Vehicle Status**: Indicates the current status of the vehicle (e.g., Pending, Arrived, Departed).
5. Once the dock information is confirmed, navigate to the **Dock Management** menu item on the left-hand side. Use the **Start Date** and **Start Time** filters to locate and view the run that was assigned to the dock.
### Updating Dock Status
Once dock details have been confirmed, users can update the **dock status** to reflect the current state of the run assigned to the dock. Updating the dock status will change the colour of the corresponding card on the **Dock Management Board**, providing a clear visual indicator of its status. A **legend** in the top-right corner of the board explains the meaning of each status colour.
**To update the dock status:**
1. Navigate to the **Run Page** for a run that has dock details assigned.
2. Click the **truck icon** to open the status update modal.
3. Update the **Confirmation** and **Vehicle Status** fields as required.
These updates ensure accurate tracking and communication of dock activity in real time.
### Adding Ad Hoc Entries
Ad hoc entries allow users to reserve or block off a dock for a specific period of time. This can be used for various operational reasons such as maintenance, scheduled breaks, or special use cases. Once an ad hoc entry is created—for example, reserving Dock 3 from 10:00 AM to 2:00 PM—no other runs can be assigned to that dock during the specified date and time. This ensures scheduling conflicts are avoided and dock availability is accurately managed.
**Creating ad hoc dock entries:**
1. Navigate to the **Dock Management** page.
2. In the top-left corner of the board, click the **plus (+) icon** to add a new entry.
3. Enter the following details:
* **Dock**
* **From Date** and **From Time**
* **To Date** and **To Time**
4. Click the **Create Ad Hoc Dock** button to save the entry.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.biscit.com/biscit-delivery-planning/biscit-delivery-planning-user-guide.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.