These screens are used to set up the milestones that will be assigned to each export or domestic job on creation (or entry into the workflow). These screens can be found in Administration > Job Tracking
Export and Domestic Job Milestones
Export Job milestones are assigned to an export or domestic job upon creation (i.e. the “JOBA” Job Add event). This screen is found in Administration > Job Tracking > Export Job Milestones.
|
Field Name |
Description |
Validation |
Default |
|
|
Header The header fields are used to determine which set of milestones is applicable to a job when it is created. The “profile” of the job is determined first and then a match for that profile is found in this screen. NOTE: The search for a match for the profile occurs in stages. That is, if a specific match is not found then a more general match is searched for and if no match is found then the default set of milestones will be used.
|
||||
|
Dept |
Select the Department code. Use Zoom to search for a department or enter ‘ALL’ to set the Milestones for all Departments |
N/A | Blank | |
|
Job Type |
Collect – The Prepaid/Collect flag on the Import Job Registration Screen is “Collect”.
Prepaid – The Prepaid/Collect flag on the Import Job Registration Screen is “Prepaid”. All – Applies to all jobs (both prepaid and collect). |
N/A | Blank | |
|
Mode Type |
This field corresponds to the “Job Type” of the department on the job registration screen. Select ALL for all Job Types |
N/A | Blank | |
|
Container Class |
This field corresponds to the “Job Class” field on the job registration screen for Ocean jobs. Select ALL for all Job Classes |
N/A | Blank | |
|
Detail This section of the screen is used to define the steps involved in the lifecycle of a job and the sequence in which they occur. Each milestone sequence must begin with the JOBA (Job Add) event and finish with the JCOM (Job Completed) event. |
||||
|
Milestone |
This is an event code. Any event can be used as a milestone. This milestone will be completed against a job when the event itself has been created. This may occur automatically via a system process. The completion of any milestone will update the status of the job. The status of the job is always the last completed milestone. The status of a job will not be marked as “JCOM” (Job Complete) until all milestones are completed or marked N/A. Milestones that are completed by the creation of an event cannot be “uncompleted”. |
Mandatory | Blank | |
|
Description |
This displays the description of the event. |
N/A | N/A | |
|
Sequence |
A positive number indicating the numeric sequence in which the milestones are expected to be completed. NOTE: Milestones can be completed out of sequence. |
Mandatory | Blank | |
|
Active |
A milestone must be marked as active in order to be allocated a job when it is created. |
Mandatory | Yes | |
|
Manual |
A manual milestone can be completed manually. That is, the “Milestones” option can be used to enter a milestone completion date and time. When a user enters a milestone completion date and time against the milestone, this creates an event. This means that the milestone cannot be “uncompleted”. |
N/A | Yes | |
|
NA By Default |
This indicates that this milestone is created as N/A. The user has the option to untick the N/A flag against the job after creation. |
Mandatory | No | |
|
Transhipment |
Not Applicable for Export Jobs |
N/A | N/A | |
|
Hours |
To be used with Condition and Event When the event is a date, hours should be in 24 hours amounts (eg 48) |
N/A | Blank | |
|
Condition |
To be used with Hours and Event Select a condition from the predefined zoom list. |
N/A | Blank | |
|
Event/Date |
To be used with Hours and Condition Select an event from the predefined zoom list. |
N/A | Blank | |
The Hours, Condition, Event combination determines an exception condition for the milestone.
NOTE: The event can be another milestone event in the same sequence. In this case the number of hours for the condition can be less than 24 hours.