Navigate to the 'Stack Run' section in the main menu. Select the ‘Stack Run Request’ link.
If you have access to both the Stack Run in and Stack Run Out, select the SRO Tab.
A dashboard screen will appear displaying all your requested Stack Runs.
Click the 'New Stack Run' button to create a Stack Run In Request.
The Stack Run Request screen includes the following:
There is a dashboard displaying all your Stack Run Out (SRO) requests. Each SRO will be displayed as a bar on the dashboard to indicate when it begins and when it ends.
With each Stack Run the following details will be displayed:
You can click on the Stack Run in the dashboard to view the Stack Run Details.
The following screenshot displays the SRO dashboard:
The SRO dashboard will display the Day, Date and zones (0-23).
There will always be 3 days shown in the dashboard. Users will have the ability to move forwards or backwards 1 day at a time, but the first calendar day displayed on the dashboard will always default to the current facility date.
SRO requests will be displayed with a status:
The following colours represent the different SRO statuses:
|Pending (New Stack Run Created)|
|Pending (View ERN)|
|Waiting for Confirmation|
The Stack Run Out Request form is displayed in differently in the two following states:
The form below is displayed when the New Stack Run link is clicked, or when a pending SRO request is viewed.
This Stack Run Out Request Form is used to create a new Stack Run Request or update an existing request to the Stack Run.
The Stack Run Out Request Form allows you to:
When a Stack Run Out is confirmed, clicking on the Stack Run ID or the progress bar for that Stack Run, will display the following screen:
When a SRO is Confirmed, the Stack Run Out Request Form is used to assign and prioritise containers to the Stack Run.
The Stack Run Out Request Form allows you to:
A SRO request can be broken up into two parts;
Open up to the Stack Run Out dashboard.
Click the New Stack Run button. This will open up the SRO request form.
Complete the Stack Run Out Request Form, filling out the number of containers required, email address and click the Save button.
The terminal will either reject or confirm the request which will trigger an email to the email addresses specified in the SRO Request.
Note: the Request must be Confirmed before it can progress any further
As part of the SRO Request form, before confirming a Stack Run the CTO can specify when manifesting can begin and when it must stop.
The Manifest Start Date and time dictates when Manifesting can begin. Manifesting cannot start until the local facility date and time is equal to the date and time specified in this field.
The Manifest End Date and time dictates when Manifesting must stop. Once the local facility time has passed the Manifest End Date and Time, Manifesting will no longer be allowed for that Stack Run.
Once a Stack Run Out Request has been confirmed, you may begin to add containers to the SRO request.
Follow the below steps to access an existing Stack Run Out Request from the Calendar.
Note that this feature is currently only available for DPW West Swanson Terminal (CONWS)
If "Enable best pick" tick box is ticked, your SRO has been confirmed as a "Best Pick" stack run by the terminal operator. This means you can use placeholders when manifesting your stack run instead of selecting specific containers for the trucks.
You will not be able to disable "Best pick" as this tickbox will be non-editable for you. If you want to disable "best pick" option and request specific containers for manifest, please contact the terminal.
Similar to generic SRO process, you must add a list of valid containers against a SRO marked as 'Best Pick'. A message will be displayed at the top of the container list page notifying you to add valid EIDO PINs for all containers, pay any outstanding storage owing and ensure that the containers in the list aren't held prior to manifesting.
When a container is added to a Best Pick SRO, VBS will display any storage owing automatically. Storage owing is calculated based on the Stack Run Out end date and zone.
You can click on the storage value hyperlink and pay any storage owing prior to manifesting.
Once all containers are added to the SRO list, you can proceed to manifest. Manifesting will only be allowed once the following criteria is met;
If one or more of above conditions aren't met, VBS will not allow you to navigate to manifest page and would display following error messages.
Once all conditions are met, you can proceed to manifest
As containers are added to the SRO Request, a list of containers will appear in the SRO Request form as seen below.
When all the required number of containers have been assigned to the Stack Run Out, then manifesting can begin.
To check the validation progress and the vessel details of each container, click on Refresh button next to the status column.
The Refresh button will fetch the corresponding ISO, Weight, Vessel Name, Lloyds, Voyage, Stops (Customs Clear/Hold Status) and Status (Validation status) of the container.
If the container Status is in Error, you can pass the mouse cursor over the status to display the error message description. A container will be error because it has either failed 1-stop's internal validation or the terminal has returned an error response on the container.
When containers are assigned to a Stack Run Out, they cannot be used in any other Stack Run or VBS booking. Vice versa, a container cannot be assigned to a Stack Run if it is already booked elsewhere in VBS.
To remove any containers from the list, select the container(s) you wish to remove by ticking the select checkbox under the Select column and then clicking the Remove Selected button - this will remove the selected containers from the container list.
To email the list of containers to the specified email addresses, click on the Email List button. This button is enabled depending if the Send Email check box has been ticked (from the Stack Run Out Request section).
Once all the required number of containers have been pre-assigned and have an OK status, you can start manifesting against the Stack Run Out.
There are two ways to sort containers:
To set different priorities to the containers in the list, click on the allocated priority number and edit the container to the desired priority number.
The priority determines the order in which containers are listed in the container drop-down list in the Stack Run Out Manifest screen.
You may also sort all the containers already added in the list by pasting the containers in the correct sequence order. To do this, click the sort button.
Paste the containers in the pop-up window in the correct sequential order leaving a space or comma to separate each container. Click the Sort button. The containers will now take on their new priority based on the sequential order they were placed in.
Any containers that have already been manifested will be ignored during the sort process. Manifested containers will have their priorities pushed to the top and the sorted containers will take on the next available priority after the manifested containers.
Note: You cannot sort containers when the Priority Lock has been switched on by the CTO. When the priority is locked, this will be indicated by a Red lock icon next to the Priority Column.
If the CTO has enabled automatic sorting, the containers will be sorted based on their Yard Location. You will have no option to sort or change the priority of the containers you add into the SRO container list.
When containers have been added, you may also start pre-assigning EIDO pins to the containers before manifesting begins. This can performed be in 2 ways:
NOTE: Pre-assigning the EIDO PINS in the request screen is an optional feature. Users can still assign EIDO pins during the Stack Run Out manifesting process.
The SRO may be locked by the CTO in two ways:
This will be indicated by a red lock icon next to the Priority column in the SRO Container List. Only the CTO may unlock the priority of containers.
While the Container priority is locked, the following rules and restrictions will apply:
This will be indicated by a red lock icon under the blue manifest button. Only the CTO may unlock the SRO for manifesting.
While the Stack Run Out is Manifest Locked, the following rules and restriction will apply only to Carriers:
You can see the estimated discharge time of a container in the "Estimated Discharge" column. VBS receives this information from the terminal. If you do not see anything, that means the terminal did not send this information to the VBS.