Decking History Decking History View Decking History DetailsYard Decking History Decking History View Decking History Details
The decking history details view provides more detailed information about each decking decision. For more information about specific Expert Decking penalties, see Setting penalty values (on page 1).
XPS Decking Details
|
Decking Detail |
Description |
|---|---|
|
Yard Name |
The Yard as specified in Yard Editor. |
|
Time |
Time that the decking logic was executed. yy/mmm/dd hh:mm |
|
Unit ID |
The container number. |
|
Node |
XPS; <IP Address>{Server} |
|
Decking Type |
See Decking Types (on page 1). |
|
Execution Time (ms) |
Duration of time needed to execute decking decision in milliseconds. |
|
Parameter Set |
A decking strategy applied to a specific allocation range. These strategies are specific for different conditions/departure types. See About Expert Decking strategy for ranges. |
|
Allocation Group Assigned By |
XPS N4FACT Server - if XPS assigns the allocation group. |
|
Allocation Group |
The name of the allocation group determined by the XPS N4FACT Server and used by N4 Decking. |
|
Timeframe |
The timeframe of the yard in which the decking request is made. Decking requests are generally made in either the Composite or Imminent timeframe, depending on the decker and the state of the yard. For Composite timeframe: The slot must be free in the current, imminent, and future time frames. For Imminent timeframe: The slot must be free in the current and imminent time frames Decking calls in the Imminent time frame take precedence. |
|
Chosen Slot Total Score |
Total score of all penalties applied to this decision. |
|
Strategy |
The Expert Decking Strategy that was used, that is, a set of penalties with specific settings. See Using Expert Decking strategies for more information. |
|
Penalties |
The Expert Decking penalties that were applied as part of the decking decision, along with the scoring for each penalty. You can search the online help for more details about each penalty. Certain scores will also include the calculation used to the right. Penalty information will be displayed as follows: [Penalty Name]: [Penalty total] = ([Penalty Value * Multiplier]/Divisor) For example, if you see the following penalty calculation displayed: ROWDBV: 50 = (50 * 1/1) ROWDBV penalizes each excess container in a block with above average number of containers. so this means: ROWDBV was set to 50 The Multiplier: Each excess container in a block with above average containers. So in this case, there was only one excess container. The Divisor: There is no divisor for ROWDBV. When there is no divisor, it defaults to 1. If you see the following: TIMDIS: 150 = (50 * 300/100) TIMDIS is the penalty per 100 meters of distance from the start point of the move beyond the threshold distance. Here, TIMDIS was set to 50 The Multiplier: 300 The Divisor: 100 |
|
EC Parameters |
For housekeeping moves, you can see what has been set for the following EC Parameters: PHTMHT PHTTTO PHTTAC PHTSIT Refer to Set housekeeping EC Parameters for more information. |
N4 Decking Details
You can view all Problem Solutions as well as information about Problem Solutions under Configuration Optimization Problem Solution Problem Solution view
|
Decking Detail |
Description |
|---|---|
|
Thread Name |
The specific thread on a node that runs the decking logic |
|
Config Provider |
The configuration provider code extension that was invoked for the decking decision. The configuration provider stores the configuration used by the invoked decking Problem Solution. |
|
Data Provider |
The data provider code extension that queried and prepared the data for the invoked decking Problem Solution. |
|
Solve Strategy |
The solve strategy code extension that runs the decking logic for the invoked decking Problem Solution. |
|
Allocation Group Assigned By |
N4 Decking - if N4 assigns the allocation group. |
|
Allocation Group |
The name of the allocation group determined by N4. |
|
Allocation Filter |
The name of the allocation filter determined by N4. |
|
Alternative slot 1 |
Provides the 2nd best slot decision, along with the top five penalty scores. Does not apply to decking performed in XPS. |
|
Alternative slot 2 |
Provides the 3rd best slot decision, along with the top five penalty scores. Does not apply to decking performed in XPS. |
|
Traffic Regime |
Whether the transfer zone has light, medium, or heavy traffic, which can impact decking penalties. The traffic regime is calculated separately for the different transfer types:
See Congestion impact on TZ Decker decisions for more information about traffic regimes. |
|
Urgency |
Whether this job is urgent, semi-urgent, or non-urgent. For more information about urgency, see Job urgency levels in the online help or on the Kaleris Community Portal. |
This section describes all the different decking types that appear in the Decking History view. Each type represents a decking logic invoked by either N4 or XPS.
Notes
For twin containers, two records are recorded in the Decking History view, one for each container. A "Twin" designation in the Decking Type displays for the secondary twin container only, such as "Vessel Discharge - Twin", and not for the primary twin container.
The XD Service decking types only appear when either an ECN4 XD server or N4 XD server is activated using the DKRSRV or XDSRVC privileges respectively.
The Component column has the following format: <component> IP address {user} - DKRSRV or XDSRVC. The DKRSRV or XDSRVC at the end only displays for XPS clients configured as an ECN4 XD server or N4 XD server respectively.
|
Decking Type |
Component |
Description |
Decking process(es) this logic applies to |
|---|---|---|---|
|
Bump Intruder |
XPS |
When a plan is made to a slot that already has a plan. The Bump Intruder logic moves the pre-existing plan to another slot. |
Can apply to any decking process in any part of the yard. |
|
Gate Receival Assign Position |
XPS |
When a container is received through the gate. |
Gate Moves |
|
Gate Receival (Flip) Assign Position |
XPS |
|
|
|
Housekeeping |
N4/XPS |
Housekeeping moves containers to more optimal stacks well in advance of the exit move from the ASC block, that is, before the exit move has a move time. Since these moves are considered low-priority/not urgent, they have a window of 24 hours so that they can be executed at night and in between other high-priority moves. |
Intrablock Moves |
|
Intra-block - Rehandle |
N4 |
If a target container for a work instruction is covered by a container, N4 Automation applies rehandle logic that moves blocking containers so that other planned containers can be moved. |
Intrablock Moves |
|
Intra-block - Redeck on ASC Abort |
N4 |
When an ASC order is rejected and a new location needs to be found. |
Intrablock Moves |
|
Intra-block - Move Split |
N4 |
AYC Manager splits inbound and outbound work instructions (WI) when a single ASC cannot complete the plan. |
Intrablock Moves |
|
Intra-block - Move Split - Twin |
N4 |
Twin support for intrablock split moves. |
Intrablock Moves |
|
Intra-block - Refinement |
N4 |
The process of changing the decking slot of an inbound or intrastack work instructions when the initially selected slot is not possible. |
Intrablock Moves |
|
Intra-block - Move Revision |
N4 |
The process of changing the destination of an inbound or intrastack work instruction (WI) that has a destination that is not convenient for the crane, for example because it would involve a long gantry drive. |
Intrablock Moves |
|
Intro-block - Revision - Twin |
N4 |
Twin support for move revisions |
Intrablock Moves |
|
Intra-block - Preposition |
N4 |
Prepositioning moves containers closer to their exit transfer zone as their exit moves become imminent. |
Intrablock Moves |
|
Intra-block - Twin |
N4 |
|
|
|
PR-TT Scheduler |
XPS-Client |
Whenever PR-TT creates plans for containers. |
Pre-Decking Discharge Decking Transfer Zone |
|
PR-SC Scheduler |
XPS-Client |
Whenever PR-SC creates plans for containers |
Pre-Decking Discharge Decking Transfer Zone |
|
Predecking Scheduler Note that the Predecking Scheduler decking type replaces the Vessel Pre-decking decking type |
XPS-Client |
Decking performed by the XPS client which could apply to containers on or by:
If a planned container has an EMT that falls within a relevant predecking window, Expert Decking may attempt to assign a position prior to any container movement. This action enables appropriate resources to be reserved for the eventual move time. |
Pre-Decking |
|
Rail Discharge |
XPS |
|
|
|
TZ Decking - Regular |
N4 |
The component that determines the optimal transfer point for decking containers that are planned to and from an ASC block. |
TZ Decking |
|
TZ Decking Alt |
N4 |
When an order to the transfer zone is rejected and a new location needs to be found. |
TZ Decking |
|
User <Ctrl>-A |
XPS-Client |
When a user manually decks a container |
Expert Decking |
|
Vessel Pre-decking Note that this decking type is replaced with the Predecking Scheduler decking type. |
|
|
|
|
Vessel Discharge |
XPS |
|
Expert Decking |
|
XD Advise Unit |
XPS-Client |
For when XD Client performs decking on Advise Unit request. |
XD Service |
|
XD Allocations Request |
XPS-Client |
External Decking request for XPS considering all allocations. |
XD Service |
|
XD Allocations Request - Twin |
XPS-Client |
External Decking request for XPS considering all allocations for twins. |
XD Service |
|
XD Refine Request |
XPS-Client |
External Decking request to refine a container in a row. |
XD Service |
|
XD Refine Request - Twin |
XPS-Client |
External Decking request to refine a container in a row for twins. |
XD Service |
|
XD Refine Request - Twin failed Split |
XPS-Client |
Twin split fails when making External Decking request to refine a container in a row for twins. |
XD Service |
|
XD Rehandle Request |
XPS-Client |
External Decking request for XPS rehandle. |
XD Service |
|
XD Rehandle Request - Twin |
XPS-Client |
External Decking request for XPS rehandles for twins. |
XD Service |
|
XD Decking by Allocations Request |
XPS-Client |
External Decking request for |
XD Service |
|
XD Decking by Allocations Request - Twin |
XPS-Client |
|
XD Service |
|
XD Deck on Dispatch Allocations |
XPS-Client |
External Decking request for XPS dispatch decking considering all allocations. |
XD Service |
|
XD Deck on Dispatch Allocations - Twin |
XPS-Client |
External Decking request for XPS dispatch decking considering all allocations for twins. |
XD Service |
|
XD Deck on Dispatch Refine |
XPS-Client |
External Decking request for XPS refine position. |
XD Service |
|
XD Deck on Dispatch Refine - Twin |
XPS-Client |
External Decking request for XPS refine position for twins. |
XD Service |
|
XD Drop if Floating Refine |
XPS-Client |
External Decking request for refining a floating container. |
XD Service |
|
XD Drop if Floating Refine - Twin |
XPS-Client |
External Decking request for refining a floating container for twins |
XD Service |
|
XD Vessel Discharge |
XPS-Client/XPS |
External System making a decking request upon vessel discharge. |
XD Service |
|
XD Vessel Discharge - Twin |
XPS-Client/XPS |
External System making a decking request upon vessel discharge. |
XD Service |
|
XD Vessel Discharge - Connection Failure |
XPS-Client/XPS |
N4 could not establish a connection to an N4 XD server or the XPS server’s XD service. |
XD Service |
|
XD Vessel Discharge - Timeout |
XPS-Client/XPS |
An XD request sent to an N4 XD server or the XPS server’s XD service timed out. |
XD Service |
For the XD Vessel Discharge, XD Vessel Discharge – Connection Failure, and XD Vessel Discharge – Timeout decking types, the Component is XPS when attempts to use the N4 XD server(s) failed.