| About Ange | Contact | Products | Maritime Consultancy | IT Consultancy | People |
ParametersUsing historical data from the Sparc operation system, SYLO simulates all the moves that were done during the week based on a set of parameters. The parameters include the Crane and RTG MPH, the maximum queue length for the PM (how many PM can wait by a crane/RTG), the rule for using dump blocks and house keeping moved, the speed of the PM and the average time it take to load and unload a unit for the PM. These values are used by the simulator to |
|
|---|
StatisticsThe results from the simulator are displayed in the Main Statistics window. The simulator count how many KM the PM travelled, the number of house moves and distance, the number of RTG hours used to move the units, the number of interblock gantries. An important result of the simulator is the number of errors that it detected. An error occurs when the yard of berth configuration makes it impossible for the simulator to satisfy the need of the vessels. |
|
|---|
Fully Editable YardThe Yard layout shows all the blocks on the yard and a tool tip hints on which services are already on a block. Drag and drop can be used to move a service from a block to another, delete a service or add a service to a block using the Service Legend. |
Drag and drop with mouse
|
|---|
Fully Editable Berth PlanThe SYLO berth plan is cleverly organized to allow the user to move each vessels. Moving a vessel towards the bottom means the vessel will arrive and depart later during the week. Each day of the week is represented with a darker or lighter blue background. To move a vessel horizontally changes its berthing position. Moreover, the horizontal length of each vessel represents its length. Its height represents its berting window. All of these parameters can be edited with the mouse or with a pop-up menu. Any edition causes the simulator to recalculate to total cost of the yard. |
|
|---|
ErrorsThe simulator detects errors that will occur in the future. A common example is when several vessels, across some days, discharge to a set of blocks. This is OK in itself. But what if the block needs to load vessels all on the same day. In the example, right, the block received 240 units across 2 days. On the Wednesday, the 240 units must be loaded on the same 6 hours period to 2 different vessels. This is not possible as it would exceed the limit of RTG per block. Sylo will report this as an error. |
|
|---|
GraphsSylo provides load patterns per block. Using these graphs, the user can see drill down on congestions and find times of the week where the block could be better utilized. In the example on the right, you can see that the block is utilized nearly every day of the week for different services. On the block below, you can see congestion between 2 services on Thursday and Saturday. |
![]()
|
|---|
Vessel Load and Discharge PatternWhen clicking on a vessel, SYLO reports where the vessel discharge to and where it loads from. In the example beside, the vessel service CESW was clicked on. It reports, in red, that the vessel mostly loads from 2 blocks. It discharges less than it loads (in blue) and it discharges also to 2 blocks. In this example, this service loads and discharge from the same block (where a block has a blue and red zone) which is usually a performance concern. |
|
|---|
Load and Discharge PatternWhen clicking on a block, SYLO reports which services discharge and load to the block. The small pie charts indicates in red the load percentage and in blue, the discharge percent. In the example, right, vessel AE8, uses about 25% of all the weekly moves to the block 14B and most of the moves are loads. Once more, the block is used, in this example, to load and discharge the same vessel. |
|
|---|