There is an ECN4 extension called No_Operator that enables you to use a PDS system to dispatch TBD units. You can obtain the necessary files for this extension through Navis Professional Services.
Navis maintains and tests only the ECN4Web extension points in ECN4Web, and ensures that the requests to the custom context are operational. Navis does not maintain the .war files or test against customized .war files.
The Customer acknowledges that any external development created by Navis, Customer, or any third party which utilizes Groovy or any other programming language ("External Development") or uses an ECN4/ECN4Web extension, is considered a modification or enhancement to Navis's generally available Software and will not be supported under Navis's standard Maintenance and Support program. Customer may retain Navis Services to assist in the maintenance and support of such externalizations pursuant to a separate Externalization Support Work Order (ESWO). Additionally, Customer acknowledges that the use of any development documentation provided by Navis ("Documentation") is for educational purposes only and at Customer's sole risk. Navis disclaims all warranties and/or conditions, whether express or implied, regarding External Development and/or Documentation, including but not limited to those of completeness or fitness for any particular purpose. Navis reserves the right to change the code extension API's and/or Documentation at any time.
Prerequisites:
In order for a CHE to carry out a dispatch via PDS, the CHE needs ot be available and the PDS left must be received from either the IDLE or JOB LIST form, otherwise they will not receive instructions.
If a PDS message contains a container ID and a position that are in conflict, the container ID overrides the position.
ECN4 always picks the first TBD unit job in the job list.
To install the ECN4 extension to enable PDS to self-dispatch TBD units:
You will need to contact Professional Services to obtain the following necessary files for this ECN4 extension:
LiftNoOperator.jar - Needs to be included in the class path for ECN4
ListNoOperatorWeb.war - Needs to be extracted to a folder on the same level as ECN4Web
No_operator_stateModel.xml
No_operator_formModel.xml
Include these four files in your ECN4-ext directory where you have ECN4 installed.
Also, you need to add the following elements to the ecn4_settings.xml file under: <component name="xmlrdt">
Under <component name="stateModelFiles">, set the following:
<setting name="NOOP" value="runtime/ecn4-ext/no_operator_stateModel.xml"/>
Under <component name="formModelFiles">, set the following:
<setting name="NOOP" value="runtime/ecn4-ext/no_operator_formModel.xml"/>
Merging logic for PDS TBD unit dispatch
When using PDS, TBD units can only be merged in the following situations:
There's at least one TBD unit job in the list
N4 must know the container ID
The container is unplanned
After a lift, if ECN4 tries to merge the TBD unit with a planned container, ECN4 won't accept the lift and will go back to the job list.
The TBD units merge validation will not run in the following situations:
Where the slot is empty due to wrong inventory
There's more than two containers in a slot due to wrong inventory
The container is being lifted from a heap (that is, the position is not known).
If the merge validation doesn't run due to the above circumstances, the Hatch Clerk validates the TBD unit at the quay.
If an idle CHE gets a lift from a position that has no container and no TBD unit jobs are marked, it goes to NOOP:FORM_UNKNOWN_REHANDLE.