1. home and garden
2. pest control

INSERT PARTNER LOGO
Manuel Perez, Director of Product Management XVELA
CONNECT.
COLLABORATE.
INNOVATE.
PowerStow Today
INSERT PARTNER LOGO
Actually we never left… Navis never stopped or planned to stop supporting PowerStow.
INSERT PARTNER LOGO
PowerStow
• Powerful UI
• Easy planning tools • Quick Data reconciliation
• ShipEditor
INSERT PARTNER LOGO
INSERT PARTNER LOGO
INSERT PARTNER LOGO
•
•
Progress in our roadmap being reported regularly
Tip of the week in Xvela.com
INSERT PARTNER LOGO
INSERT PARTNER LOGO
Ship Library
EDI engine
Optimization
tools
Terminal Library
Analytics
Planning tool
INSERT PARTNER LOGO
You told us what is that we urgently need to do
D&H issues
Pending bugs
Stability and Stress calculations
Lashing
INSERT PARTNER LOGO
INSERT PARTNER LOGO
SELSEG setting not working as expected.
Self segregation in PowerStow should allow you to check segregation rules within a container.
REFRIG setting not working as expected.
This setting allows you to consider the entire container as the source of ignition. In the contrary case it consider only the plug location as the source of ignition when checking the segregation rules
Door direction
To improve visibility on source of ignition location and be able to cope with some limitations, we have made the container’s “door direction” available to the user with the possibility of manually change it.
IMO classes 1.1, 1.2 and 1.3 restricted in the outmost stacks.
Rather than the most common 1.4, the rest of explosive should not be loaded in the outmost stacks. We have just completed this development and it is available in the new version.
Clear of living quarters (CLQ) and other separation rules It seems that the calculations performed by PowerStow to check the segregation when CLQ involved not always provide the correct warning. Working on it.
Reported and solution under evaluation
Bug
Enhancement
needed
INSERT PARTNER LOGO
More than 9 DG per container ‐ it is a COPRAR 1.2 limitation
PowerStow supports up to 99 DG per unit as well as others EDI files including STIF the support more than more than 9DG per unit. Compatibility with COPRAR 2.0 will be developed in Q2‐3
Limit quantities ‐ it is a COPRAR 1.2 limitation
PowerStow supports limited quantities as well as others EDI files including STIF that support limited quantities. Compatibility with COPRAR 2.0 will be developed in Q2‐3
UNNO in projections.
PowerStow supports UNNO in projections either when importing a STIF file or when projections are planned There is a limitation on the Projection Windows. We have just completed this development and it is available in the new version.
DG details added to an existing container
UI does not reflect the information although the actual data is correctly stored.
keep wind speed and max roll angle setting when changing between ports
Flash point not available as actionable parameter
Reported and solution under evaluation
Bug
Enhancement
needed
INSERT PARTNER LOGO
Calculations consistency
Beyond the Limitations in the Tanks, hydrostatics and Bonjean lines, the actual calculations are correct. We remind you that you need to carefully select the lines you to choose to include the file to minimize the potential data distortion.
TIPS •
•
Don’t use more than 2 decimals when entry your numbers to create the Stab file.
When editing with Excel, some extra tabs after each line could be added. Ensure to remove the unnecessary tabs after each line before compiling the stability in ShipEditor
Ensure all data entered is correct by graph every table.
•
•
•
Ensure to sort *FRAMES section by XC FRAME column (Largest to smallest)
Ensure to sort *BLOCK LIGHTSHIP WEIGHT table by LCG (Largest to smallest) Extra weight is not considering weight’s boundaries.
•
Reported and solution under evaluation
Bug
Enhancement
needed
A SMART DEFINITION OF THE NSD and NST FILES SHOULD PROVIDE YOU STABILITY AND STRESS RESULTS REASONABLY CLOSE TO THE LC (OSP) IF NOT IDENTICAL. INSERT PARTNER LOGO
Lashing calculations are outdated
We are working on update the current lashing calculations to the latest regulation for the “unrestricted services/routes” together with the custom lashing based on the routing.
Lashing ROUTE based
Custom lashing is a relatively new possibility that allow you to relax lashing rules when possible. It is important to highlight that the custom lashing based on the route requires a re‐classification of the LC if you want to use this option.
Every classification society has stablished a different method to cover route‐based lashing calculations. The majority however are based on applying coefficients to the accelerations subject to the specific routes. We are currently evaluating the different methods to decide what calculations will be covered.
XVELA has included custom lashing in current PowerStow development plans Reported and solution under evaluation
Bug
Enhancement
needed
INSERT PARTNER LOGO
Ship Library
Terminal Library
EDI engine
Analytics
Optimization
tools
Planning tool
It’s closer than it looks…