Modeling tips
Stay organized with collections
Save and categorize content based on your preferences.
This page contains tips for modeling business rules in the API.
Ports
How do I restrict vessel class compatibility at certain ports due to draft or
international laws?
Specify costs in the corresponding Port only for allowed vessel class.
How do I forbid transshipment at certain ports?
Set the transshipment cost to infinite (or a very large value).
Demands
What can be included in the freight rate?
Freight rate can include any relevant metric for the liner shipping company such
as economic value, environmental impact, customer satisfaction. Regarding the
latter, a penalty for not serving demand should be added to the freight rate.
Can the model handle demands with same origin-demand pairs but different
specifications?
Yes.
Leg candidates
What advantage do leg candidates offer compared to actual port
connections?
Leg candidates of the API support modeling of:
- Multiple trajectories between the same two ports
- Arbitrary cost functions for different velocities on the same trajectory
- Vessel class specific costs
- Vessel class restrictions (due to draft for canals or international laws)
Most importantly, leg candidates define an unambiguous definition of port
connections. This is not the case with physical port connections which allow for
many interpretations in possible operations (cost, idle time, …).
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-08-06 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["This page provides guidance on modeling business rules within the API, focusing on ports, demands, and leg candidates."],["Control vessel access to ports by manipulating costs and transshipment options, and incorporate diverse factors into freight rates to reflect business priorities."],["Leverage leg candidates for detailed route modeling, including multiple trajectories, customized cost functions, vessel-specific attributes, and restrictions, enabling a clear definition of port connections."],["The model supports demands with identical origin-destination pairs but varying specifications."]]],["The provided content details API modeling tips for business rules. To restrict vessel class compatibility at ports, costs are specified for allowed classes only. Transshipment can be forbidden by setting its cost to infinite. Freight rates can include various metrics like economic value or environmental impact. The API handles demands with the same origin-destination but different specifications. Leg candidates allow for multiple trajectories, arbitrary cost functions, vessel-specific costs, and class restrictions, providing an unambiguous definition of port connections.\n"]]
