IntraBlockDeckerDefaultConfigurationProvider
Code Extension Type: OPT_CONFIGURATION_PROVIDER (on page 1)
Purpose: The code extension that returns any configured values associated with a problem solution. This code extension pertains to the IntraBlock Decker and Rehandle Decker problem solutions.
The IntraBlockDeckerDefaultConfigurationProvider:
Sets the rehandle row limit, which is the number of rows on both side of the ASC that are searched to accept the rehandle. The rehandle row limit is 15 rows.
Allows the Rehandle Decker to rehandle hazardous containers outside of allocation range.
Allows N4 to detect the allocation group for a UFV.
Enforces the default Expert Decking strategy set for use by the N4 IntraBlock and Rehandle Deckers.
Resetting the Rehandle Decker row range
By default, the Rehandle Decker (a problem solution that uses the IntraBlockDeckerDefaultConfigurationProvider) has a row range of 15 rows on each side of the current row. This total range--coupled with any overlapping allocation range--defines the area that the Rehandle Decker searches for appropriate rehandle slots. This range can be changed in the IntraBlockDeckerDefaultConfigurationProvider by changing the getRowRehandleRange() method. You can broaden the range if you need to decrease the number of failed to decks, or tighten the range to reduce travel distance.
You can override the default row range (15) for the Rehandle Decker by customizing the IntraBlockDeckerDefaultConfigurationProvider as in the following example, where the default row range value of 15 is reset to 10.
@Override
long getRowRehandleRange() {
return 10;
}
Allowing Rehandle Decker to rehandle hazardous containers outside of allocation range
By Default, the Rehandle Decker only rehandles hazardous containers inside the rehandle row range and within the allocation range. If a valid slot is not found within the allocation range, the hazardous container fails to deck. To allow the Rehandle Decker to consider slots outside the allocation range (4th neighborhood), you can override the default value in the REHANDLE_HAZARD_OUT_ALLOCATION setting by customizing the IntraBlockDeckerDefaultConfigurationProvider code extension.
The default value for the REHANDLE_HAZARD_OUT_ALLOCATION setting is false. To rehandle containers outside the allocation range, change the REHANDLE_HAZARD_OUT_ALLOCATION setting to true.
Regardless of this setting, valid yard slots for hazardous containers must pass hazardous validations.
Allowing N4 to determine the allocation group for a UFV
By default, if the XPS privilege N4FACT is turned on, the XPS client periodically calculates and then forwards to N4 the allocation groups for each container. The N4 Intrablock Decker and Rehandle Decker in turn uses that information for decking calculations. To allow N4 to determine the allocation group for a UFV, you can override the default value in the N4_ASSIGNS_ALLOCATION_GROUP setting by customizing the IntraBlockDeckerDefaultConfigurationProvider code extension.
The default value for the N4_ASSIGNS_ALLOCATION_GROUP setting is false. To allow N4 determine the allocation group for a UFV, change the N4_ASSIGNS_ALLOCATION_GROUP setting to true.
Enforcing the 'Default' Expert Decking strategy for use by the N4 IntraBlock and Rehandle Deckers
By default, the N4 IntraBlock Decker and Rehandle Decker deck based on the Expert Decking (ED) strategy set for the blocks in XPS. You can force the N4 IntraBlock Decker and Rehandle Decker to use only the 'Default' ED strategy. To do this, you can override the default value in the ENFORCE_DEFAULT_STRATEGY_SET setting by customizing the IntraBlockDeckerDefaultConfigurationProvider code extension.
The default value of ENFORCE_DEFAULT_STRATEGY_SET setting is false. To enforce the 'Default' ED strategy, change the ENFORCE_DEFAULT_STRATEGY_SET setting to true.
The advantage of enforcing the ‘Default’ strategy is that N4 deckers allow mixing stacks and decking on planned containers.
Example:
The ED strategy for blocks A001 and A002 are set as ‘Default’ and ‘L’, respectively and 'ENFORCE_DEFAULT_STRATEGY_SET' is set to ‘true’ in the system-seeded code extension 'IntraBlockDeckerDefaultConfigurationProvider.groovy'. When you plan an intrablock split move with a rehandle, the N4 IntraBlock and Rehandle deckers use only the ‘Default’ ED strategy. Also, the ‘Decking Strategy’ field displays ‘Default’ in the Decking History Details view.