Let’s consider an operational scenario. A seaport has a vessel scheduled to load bulk cargo. Staff are also preparing a freight train for dispatch. Several trucks will arrive to collect their shipments. Each transport operation has its own schedule, customer requirements and planned cargo quantity.
But what happens if two or more shipment plans rely on the same stock?
The problem may only become apparent when loading begins and the promised cargo is no longer available. By then, the terminal may have already assigned equipment and personnel. Transport may be waiting, and teams may need to revise operational schedules.
For bulk terminals, effective shipment planning goes beyond coordinating vehicle arrivals and loading operations. It connects cargo availability, shipment reservations, transport schedules and actual handling results within one operational process.
Why Bulk Cargo Shipment Plans Can Conflict
Bulk terminals frequently handle cargo moving between different modes of transport. An export terminal may receive coal or minerals by rail, accumulate the cargo in storage and then load it onto vessels. Other facilities may receive cargo by vessel for onward distribution by train or truck.
These operations are interconnected, but different teams may plan them. Railway personnel may work with wagon schedules and cargo dispatch instructions. Vessel operations teams prepare loading plans according to shipping requirements. Road transport coordinators organize individual truck collections.
Without a shared view of cargo availability, each team may plan shipments using quantities that appear available.
However, stock physically present at the terminal is not always available for a new shipment. The terminal may already have reserved some of that cargo for another customer or transport operation.
If teams prepare requests independently, they may miss the conflict until one of the operations begins. A reliable planning process must therefore identify a shortage before teams commit the same stock to multiple shipments.
Effective Planning Begins Before Transport Arrives
Along with cargo availability, the planning problem includes timing. A freight train may arrive with dozens of wagons carrying different quantities of cargo. If shipment details arrive only with the train, terminal staff have less time to prepare storage areas, equipment and unloading operations.
The same challenge applies to other transport modes. The earlier relevant information becomes available, the more time the operations team has to coordinate the work.
Pre-arrival information may include:
- Expected arrival of transport units.
- Cargo descriptions and quantities.
- Relevant transport and shipping documents.
- Wagon or vehicle identification data.
- The intended receiving or dispatch operation.
With the necessary integrations in place, a terminal operating system can receive this information from external sources before physical handling begins.
Solvo.TOS supports the use of preliminary transport and cargo data. This includes information from integrations with railway information systems and other sources of transport documentation. Terminal staff can use the incoming data during cargo receipt and subsequent operations. This reduces the need to enter the same information repeatedly.
However, receiving a transport plan in advance does not mean that the terminal has already received the cargo. The terminal must distinguish expected quantities from quantities actually registered in storage. This becomes particularly important when the terminal plans to ship incoming cargo onward.
Available Stock vs Reserved Stock
Reliable bulk cargo shipment planning follows a straightforward principle: a quantity reserved for one shipment must not remain available for another. To apply this principle, the terminal needs to distinguish inventory quantities from stock already committed to outgoing operations.
For example, a terminal may have 1,000 tonnes of cargo recorded in storage. If it reserves 600 tonnes for vessel loading, only 400 tonnes remain unreserved. This assumes the stock is otherwise eligible for the planned shipments.
A subsequent railway shipment request for 300 tonnes would leave 100 tonnes unreserved. A truck collection request for 250 tonnes could not then draw its full quantity from that same available stock.
In Solvo.TOS, a shipment request reserves the required quantity for a specific transport direction. Once the system allocates that quantity, it cannot reserve it for another shipment at the same time. The reservation links the intended dispatch operation to the committed cargo quantity.
This helps terminal personnel distinguish between stock physically recorded at the facility and stock still available for new shipment requests.
In practice, quantity alone may not determine availability. When selecting stock for a shipment, staff must also consider cargo ownership, documentation and other applicable requirements.
Vessel Loading: When the Planned Quantity Is Not the Actual Quantity
Even with a correct reservation, a shipment may not proceed exactly as planned. Consider a vessel scheduled to load 600 tonnes of dry bulk cargo. The terminal reserves the required quantity and prepares the loading operation. However, once loading ends, the confirmed quantity turns out to be 560 tonnes.
Such differences can arise for several reasons. Measurements may establish a final loaded quantity that differs from the plan. Operational circumstances may also prevent the terminal from shipping the full reserved amount.
For certain dry bulk vessel loading operations, a draft survey can determine the actual cargo quantity from changes in the vessel’s displacement.
This creates an important question: what happens to the 40 tonnes that the terminal reserved but did not load?
- If the terminal simply treats the original planned quantity as dispatched, the cargo records will no longer reflect the actual operation.
- If the unused quantity remains reserved indefinitely, later shipment plans may exclude cargo that is still physically available.
The system therefore needs to connect the original loading instruction with the confirmed result.
Solvo.TOS supports cargo reservation, partial vessel loading and the distribution of cargo quantities between vessel holds. The system can release the unused reservation after confirmation of the actual loaded quantity. Where applicable, this confirmation can use draft survey results.
The resulting records distinguish between three quantities: the original plan, the actual loaded amount and the stock still available after loading. For terminals handling multiple outgoing transport flows, this distinction helps keep subsequent shipment plans aligned with what physically occurred.
Shipment Planning Must Be Connected to Shift Operations
Even when all requested quantities are available, the terminal still needs sufficient equipment, personnel and operational capacity to complete the work. A vessel may require loading during the same shift as incoming wagon unloading. Truck collections may also need attention while equipment handles other cargo movements.
These operations create competing demands on terminal resources. That is why shipment planning needs a clear link to shift-day planning.
A shift plan translates expected operational demand into activities. Teams can then assign resources and monitor execution.
For example, terminal management may need to determine:
- Which vessel, railway and truck operations to expect during the shift.
- What cargo quantities to plan for handling.
- Which equipment and personnel the work requires.
- Which activities require coordination across different handling areas.
- What workload and productivity to expect.
However, actual operations may take longer than expected. Teams may complete only part of the work or handle quantities that differ from the original estimates. A useful planning system therefore needs to distinguish between the preliminary resource plan and the tasks assigned for execution.
Solvo.TOS supports shift-day planning through the allocation of personnel and handling equipment to operational tasks. It also records completed work and actual cargo handling volumes. This provides information for comparing planned workloads with operational results.
The terminal can therefore evaluate which shipments it planned, what work teams performed and how they used the available resources.
Cargo Handling Follows Various Routes
A shipment plan may appear simple on paper: receive the cargo, store it and dispatch it. In reality, the handling process can involve additional stages. The terminal may need to transfer bulk cargo between storage locations, repack it or handle it during container stuffing and stripping operations.
For example, cargo received by rail may first enter storage. Teams may then move it to another handling area and load it into sea containers rather than directly onto a vessel as loose bulk cargo. These activities form part of the terminal’s workload, even though they occur between the main receiving and dispatch stages.
Solvo.TOS supports internal cargo movements, repacking and bulk cargo operations involving sea containers, alongside the principal receipt, storage and dispatch processes.
Linking these activities to the corresponding cargo and transport records provides a more complete picture of the work required to fulfil a shipment. It also helps terminal personnel coordinate the operational steps between cargo availability and final dispatch.
Connecting Shipment Reservations and Operational Execution in Solvo.TOS
The challenges described above are closely connected. Pre-arrival information helps the terminal prepare for incoming transport. Cargo receipt establishes the quantities registered in the system. Shipment reservations identify the quantities committed to outgoing operations. Resource planning determines how teams will organize the work, while operational records capture what actually happened.
When teams manage these activities independently, a change in one process may not reach another. For example, a difference between planned and actual vessel loading changes the quantity available for later dispatch. A delayed train can change the workload for a shift. Additional internal handling operations can also create requirements that the original transport plan did not show.
The Solvo.TOS.Bulk module connects bulk cargo quantities, reservations and handling operations with the wider Solvo.TOS terminal operating system. It supports dry and liquid bulk cargo operations involving sea, rail and road transport. It also preserves the links between cargo records, transport movements, operational tasks and documentation.
For terminals already using Solvo.TOS, the module can extend an existing configuration to support additional bulk cargo flows. This does not require replacement of the entire terminal operating system. The specific operational workflows and integrations depend on the terminal’s configuration and requirements.
