The Stack Run In Manifest screen allows carriers or empty container parks to lodge a manifest against a confirmed Stack Run In request and also allocate a driver (using their Maritime Security ID Card (MSIC) number) to the truck run.
The Stack Run In Manifest screen is accessed via the Stack Run Dashboard.
To access the manifest screen, a Stack Run must first be selected from the dashboard.
Click the 'Stack Run Request' menu option under the Stack Runs section in the main menu.
Click the "SRI MT" tab to access Stack Run In Empty Module and to view the dashboard.
The dashboard will allow carriers or empty container park to select a Confirmed Stack Run to manifest.
Click the Manifest Link against the ERN you wish to Manifest in the dashboard.
When the Manifest link is clicked, the Stack Run In Manifest screen will appear. Selecting the truck type will display the truck image for containers to be added.
To Create a Stack Run In Manifest - perform the following steps starting from the dashboard:
When a Stack Run IN for empties has been set up for Nested flat racks then the manifest screen is slightly different.
Setting up a SRI empty for a NEST is based on selecting specific ISO Codes...
When adding containers (NEST) to the truck the following screen will display to facilitate adding each flat rack number to the master flat rack. Note: th emaster could be either to bottom rack or the top rack depending on what the individual terminal requires - confirm with the terminal.
Add each flat rack in turn one at a time...
For SRIE, vessel schedule is validated at the point of creating a SRIE. To successfully save a SRIE, following conditions need to be satisfied.
If the dates of the stack run are not within MT Begin and MT cut off range date range, then the system would display an error message and prevent the user from saving the Stack run. Note that if the Empty dates are not provided by the Terminal, VBS would verify the same logic against the general cargo begin receival and cut off dates.
As a result of the amendments made to Heavy Vehicle National Law (HVNL) on 1 October 2018, Patrick Terminals would require all carriers to acknowledge and accept that they’ve complied with COR Compliance conditions applicable for the Terminal.
Carriers will be prompted to read and acknowledge COR Compliance conditions prior to completing stack run manifesting.
Carriers who do not acknowledge COR compliance conditions will not be allowed to complete manifest. Same process is applied when a carrier edit their manifest. When editing a manifest, carriers must read and accept the compliance before saving any changes.
Once you have created the manifest, you be will directed to a confirmation screen which outlines a summary of the Manifest, Truck and Driver details that have entered in the previous screens.
NOTE: Continue Manifesting button will direct you back to the Stack Run Manifesting screen using the same ERN to continue manifesting. The Manifest List button directs the user to the Stack Run Manifest list screen.
NOTE: You will need to have the correct permissions to be able to Edit or Delete a Manifest. If the Edit or Delete buttons are not visible from the Stack Run screens, you do not have the permissions to Edit or Delete a Stack Run In Manifest.
You may edit the Truck Details of a SRI MT Manifest as long as it has not arrived at the terminal.
Only the following fields will be editable when editing a Stack Run Manifest as show below:
You may not edit the Manifest Date, Truck Type or the containers on a truck. If you wish to do this, you must delete the manifest and create a new manifest.
To edit the manifest, follow the steps below: