Job Milestones are allocated to each job on creation. The selection of which milestones will be allocated to a job occurs in the order defined in the table below. You will notice that the process proceeds from an attempt to make an exact match on the job profile progressively to a more general match on job profile.
When setting up milestones for the first time you can start out by setting up the last two profiles and then progressively add more specific milestones.
Please note that you will only be able to enter milestone header values that match one of the above 9 templates. If you enter a milestone profile that is different, the validation will display the following message:
|
Match Attempt |
Dept |
Job Type (Customs, Freight Forwarding, Both Customs and Freight Forwarding, All) |
Mode Type (SeaFreight, AirFreight etc) |
Container Class (FCL, LCL etc) |
|
1 |
Exact Match |
Exact Match |
Exact Match |
Exact Match |
|
2 |
Exact Match |
Exact Match |
Exact Match |
All Container Types |
|
3 |
Exact Match |
All Job Types |
Exact Match |
Exact Match |
|
4 |
Exact Match |
Exact Match |
All Mode Types |
Exact Match |
|
5 |
Exact Match |
All Job Types |
All Mode Types |
Exact Match |
|
6 |
Exact Match |
Exact Match |
All Mode Types |
All Container Types |
|
7 |
Exact Match |
All Job Types |
All Mode Types |
All Container Types |
|
8 |
All Departments |
All Job Types |
Exact Match |
All Container Types |
|
9 |
All Departments |
All Job Types |
All Mode Types |
All Container Types |
|
Field Name |
Description |
Validation |
Default |
|
|
Milestone |
Enter or use the Zoom button to select an event code. |
Mandatory |
Blank |
|
|
Some Helpful Hints |
The first milestone is always “JOBA”. This event is created automatically by the system when a job is added via job registration or any other process that adds jobs into the system. |
|
|
|
|
Some Helpful Hints |
The last milestone is always “JCOM”. This event is completed automatically by the system when all the previous milestones have been completed or marked as non-applicable. Since this is the last milestone, it is always a good idea to give it a high sequence number like 9999. |
|
|
|
|
Description |
This displays the description of the event.
|
None |
Display Only |
|
|
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 |
|
|
Status |
A milestone must be marked as active in order to be allocated a job when it is created. If a milestone is marked as an “Exception” milestone, then it is not added to the milestones allocated to any particular job until the exception occurs.
|
Mandatory |
Y |
|
|
Some Helpful Hints |
The CRL, AQH, IFIP events will be generated if this status is returned from Customs. The associated “Cleared” milestone should be added to your milestone setup as an Exception milestone in order for it to be added to the job milestone when the exception condition occurs. See example below. Please note that the “Cleared” milestone events will be completed when the ATD is finalised (ie. When a DOC – Date Of Clearance Event is generated) |
|
|
|
|
Manual Event |
Manual milestones are milestones that are marked as completed by the user. There is no system process that creates this event automatically (and hence completes the milestone). These are usually used for tasks that need to be completed outside of the Expedient system. Once the task is complete, the user will go into the Milestones screen from Job Registration and tick the checkbox to say that the milestone is completed or enter a date and time of completion. |
None |
Display Only |
|
|
NA By Default |
Milestones marked NA by default will be created against the job with the Not Applicable flag set to Y. This means that the milestone will not affect the status of the job unless the user elects to untick it and make it applicable. |
Mandatory |
N |
|
|
Some Helpful Hints |
If you use the MDEL milestone and mark is as N/A by default, this milestone will be marked as applicable for the job is it is an Ocean FCL job with more than 1 container when the job is added or updated in the job registration screen. |
|
|
|
|
Transhipment Event |
This indicates that this milestone is only applicable to jobs where the Vessel on the job registration screen is on a transhipment vessel.
|
Mandatory |
N |
|
|
Some Helpful Hints |
What makes a job a transhipment? In the job registration screen, if the vessel code entered has a vessel name of “TRANSHIPMENT” in the Vessels Master file. |
|
|
|
|
Some Helpful Hints |
What is special about transhipment milestones? When a transhipment job is updated so that it is no longer on a transhipment vessel, then the transhipment milestones are removed from job’s milestones. |
|
|
|
|
Hours, Condition, Event/Date |
These fields are used for specifying exceptions on a milestone. Enter the number of hours (usually in 24 hour amounts) and click on the Zoom button that appears. This will show you the list of conditions that can be used for specifying exceptions. The exception conditions should be read as follows: Should be completed X Hours PRIOR TO <Event Date> Eg. Should be completed 24 Hours PRIOR TO ETA Should be completed NO LATER THAN X Hours AFTER Event Date Eg. Should be completed NO LATER THAN 48 Hours After Job Registration Expedient can ensure that Exceptions do not fall on weekends. Please contact Expedient Software if you would like to stop exceptions falling on Saturdays and Sundays |
Optional |
Blank |
|
|
Category |
This is the category of the milestone. Select a category from the drop down list. Refer : Definition of Milestone Categories This is used to indicate the type of work of the milestone.
|
Optional |
Blank |
|
The next step in setting up Workflow is the Customer set up for Customer Level Job Tracking
Suppliers Invoice Completed/Parts Classified/CP Questions Answered
There may be multiple import supplier’s invoices added for an import job before the “Suppliers Invoice Completed” task is considered complete. Additionally, all parts for all invoices for the import job may be classified by a different user role and may be done after all invoices are entered. For Australian Customs sites, the same will apply for answering CP questions.
SICC – Supplier Invoices Completed
The SICC milestone is ticked when:
- An invoice is added or an invoice is modified or Specify Quantities option is selected AND
- The entered and calculated amounts are the same, AND
- There are no unspecified quantities, AND
- There is an SICC milestone against the job and it has not been completed.
Expedient will ask the User:
“Do you have additional invoices to add to this clearance?”(NOTE: this question is only asked if the system switch has been enabled to do so. Please let us know if you want this enabled)
PARC – Parts Classified
Ticked when:
- The SICC milestone is checked (as detailed above)
- After the user selects the “Classify” option from within the invoice or any of the reset options.
CPQA – CP Questions Answered (AU Only)
Ticked when:
- The SICC milestone is checked (as above)
- After the user selects the “Answer CP Questions” option
- After the user selects the “Classify” option from within the invoice or any of the reset options.