Expedient User Manual – Rail Tagging
Contents
1. TOLLS TRANSPORT CARRINGTON Query has found 12 term OVR Click on the Add button to open the Terminal Code Maintenance screen Use the Add and Update toolbar buttons to maintain the Terminal information 2 Terminal Code Maintenance EXPEDIENT DEVELOPMENT File View GMA Maint Help ar 3 A re 4 b Add Update Delete Find Browse Previous Next Terminal Codes Departure Terminal Code ET Departure Terminal Name Enter new document into form kh eer d On OK any changes to the Terminals list can be seen in the Terminals zoom from the Rail Tagging Screen 12 Rail Tag Exception Report This report is available from the Container Management System folder a 3 Container Management System Container Management Input Container Management Reports Auto Email Reports Setup Vessel Arrivals 1 Stop Rail Tag Exception Report Oo n i db E This report lists all active containers where a Rail Tag has been sent and shows the latest status of the Rail Tagging process 474410 P ce D A z 132. response to 1 Stop 5 1 Stop sends the response to Expedient 6 User send the Release request to 1 Stop 7 1 Stop sends the Release response back to Expedient 8 1 Stop sends the Release request to the Terminal 9 The Terminal sends the Release response to 1 Stop 10 1 Stop sends the Release response to Expedient Accessing Rail Tagging Rail Tagging can be accessed two ways Screen Accessmethod Sea Import Job Registration Options gt More Options gt Rail Tagging El 2 Container Management Input Rail Tagging Toolbar Button Sending a Rail Tagging Request Container To send Rail Tagging requests for multiple containers on a job access the Rail Tagging screen from the Sea Import Job Registration screen To send a Rail Tagging request for a single container access the Rail Tagging screen from the Container Management Input screen ar Click Add to set up a new Rail Tagging request 5 Contaner Fail Tagging EXPEDIENT DEVELOPMENT v Job No Container CAXU6485004 Departure Terminal Q Rall Destination Q Carrier Q Date Created HA EIDO Pin Number Comtamer Job Number Dep Term Destination Carrier Rad Ta Sent Tag PIN EIDO PIN Tag Confirmed Entered CAXU6485664 3610799 A No No No OK Cancel Delete Erte Dana tre Tercera den Doce Field Name Description Job Number This is the job number that the Rail Tagging screen was accessed from Add IDG ne Delete Find Ho it PIE 4 Ne yi 12 All L H
3. RALIA RAILROAD GROUP Date Created 05 06 2012 Mia By taniab 1 Stop Details On Board Yes gt On 05 06 2012 Discharged No On Tag Details Tagged Yes Tagged On 05 06 2012 11 12 By tanlab Sent On 05 06 2012 11 17 Confirmed On 05 06 2012 11 22 Release Details EIDO Pin 25898999 Released Yes Released On 05 06 2012 11 23 By taniab Sent On 05 06 2012 13 31 Confirmed On 05 06 2012 13 32 RELEASE MANUALLY COMPLETED ON 05 06 2012 13 32 BY taniab History Resend QUIT Show message Mestory OVEK Add new Terminals To update and add new Terminals access the current list of Terminals from the Rail Tagging screen by opening the Terminal zoom ar Rail Tagging EXPADIENT DEVELOPMENT File View GMA Maint Helpi ar X b Ea J gt El a E E Add Update Delete FinN Browse Previous Next Tag All Enter PIN Clear PIN Release All Job No Container Departure Terminal Rail Destination Carrier Date Created we EIDO Pin Number TEE x Iht Container Job Number Dep Terk Destination Carrier Rail Tag Sel Tag CAKU6485664 3610 99 The zoom opens the list of Terminals in the Departure Terminals screen 11 a Departure Terminals ABALONE FISHERMEN COOPERATIVE LTD AFPC PTY LTD A RAPTIS SONS PTY LID PATRICK VI EAST SWANSON PATRICK WA FREMANTLE PATRICK NS PORT BOTANY ASL CUSTOMS SERVICES PTY LID DP WORLD WA FREMANTLE DP WORLD VI WEST SWANSON DP WORLD NS PORT BOTANY HELENS TEST TERMINAL
4. Volume Expedient User Manual Rail Tagging GB expedient Gavin Millman amp Associates Aust Pty Ltd 281 Buckley Street Essendon VIC 3040 Phone 03 9331 3944 e Web www expedientsoftware com au Table of Contents Rall PARSING Process mia is OO Oe O 2 IGT N esel ie od Context DIO O Manaos 3 fail TAGGING Information FlOW stede sees reen in eg es ee ge en ei vae ee se ede GE eo os aida 4 ACC SSINE Ral DEU iia naaa 5 sending a RallTasecint REGU CSUs ses ies EE ee Ee GE Ee linen GE Oe Ee den ER GEKEER condal 5 ele dees do EO ER ER EE OE EN OE ARE OE EO EE EE OE ER rer a EE OE EN N eee eee 7 GO N RE A EE EE EE N OE EE EO EE N N AE RA ON 7 PAI ENE IG OE ER EE EE EE OE OE HE EE EE EE OE 7 Red S EE N EE e o 8 Witharawing ed Ra TOO EE RE OE EE ida 8 EIDO Pin ii LE saansamnsenmassasesmascanvacswassanasnanstasausas eaaneaasbaatawaneaeamaesnanteaneantssaueaammnsaeasaeiaeess 8 Ee OTIN NUNO S end 8 eeano FIND ELS SG Ge oc erase se EE Oe EG GN ceba 8 Releasing Containers Re RE De RE OR EG RR DE ee GEE ee Ge N EE GR EE RE SG EE ee EO 8 COUT DUE UO So AE RA EE OE ER ER EE ER N RE EE ER ER ED 9 PA OE E 9 oi PP o EE EE EE 10 Complete NAS EE OE EE EE EO OE EE OE ER EE N 10 Add new TErmMINalS EE OE EE ER EE EE N 11 Rail Tag EXCED COM ED ON sedes ratita ii 13 RAIL TAGGING INTRODUCTION move requests send ElDO PIN numbers and request releases with terminals via 1 Stop 1 F Xpedient software contains the Rail Tagging M
5. ier HIM Lea PIN META A gt F ri N vv N Release Release Release No Validation Optional Container This is the container number to be tagged This field is Optional hidden on Add if Rail Tagging is accessed from the Job Registration screen This field is activated in Find Mode Sent Confirmed No Default From Job Registration Blank from CMS From CMS Field Name Departure Terminal Rail Destination Carrier Date Created EIDO Pin Number Container Number Job Number Dep Term Destination Carrier Rail Tag Tag Sent Description This is the 1 Stop code for the Departure Terminal Use to search the available terminals Enter a Departure Terminal here to apply to all the containers listed in the table below This is the 1 Stop code for the Rail Head Destination Use to search the available destinations Enter a destination here to apply to all the containers listed in the table below This is the 1 Stop code for the Rail Carrier Use to search the available carriers Enter a carrier here to apply to all the containers listed in the table below This is the date the Rail Tagging request was created This is the EDIO Pin Number which applies to all the containers listed in the table below This is the container number recorded for the job This is the job number This is the 1 Stop code for the Departure Terminal Use to search the available terminals Enter a Departure Te
6. ion If not it will insert data from the job registration and then flag it to be sent to 1 Stop If the container does exist for the particular job it will update the CMS with the latest information lent softwar Expedient automatically sweeps the Rail Tagging data at set intervals during the day to look for new Rail Tag requests and Release requests to send to 1 Stop This process can be customized to run at any time of the day 1 Stop will update Expedient with details for the container e g the container is on board the specified vessel the container been discharged Rail Tagging Context Diagram The below workflow illustrates how Expedient and 1 Stop interact Job Registration FCLFGX Does Container have onboard event from 1siap i CMS Rail Tag Y RAIL TAG N EDI Does contalner have discharge off vessel event from 1siop CMS CMS Run program Manual Send Ral Tag direct to Viharf Receive EICO Update PIN number Is Rad Send Date null LIpdata Pin Send Date in CMS Message to send to 1Stop HO EDI to Update Rail Send Date field in CMS Rail Tagging Information Flow The flow of messages between Expedient 1 Stop and the Terminal is shown below 1 User sends the Rail Tag request to 1 Stop through Expedient 2 1 Stop sends a response back to Expedient 3 1 Stop sends the Rail Tag request to the Terminal 4 The Terminal sends a
7. o each container m e To select many containers to request Rail Tags use the toolbar button Tag All The Rail Tag column will automatically update to Yes for each container e Select a single container for a Rail Tag request by selecting Yes in the Rail Tag column Expedient will automatically send the all Rail Tag requests and Release requests at the specified time interval to 1 Stop However if a request is urgently needed use the toolbar button Send Now to immediately send the request message Colour Coding Each container line is colour coded to indicate the status of the progress with the rail tagging and release Green Clear This colour indicates there are no outstanding actions to be taken with this container e Tagged sent and confirmed e Released sent and confirmed Amber Warning This colour indicates that some action is required by the user or the terminal but it may not be time critical e Not tagged e Tagged and confirmed but not released Red Issue This colour indicates urgent action is required by the user or the terminal Tagged but not sent Tagged and sent but not confirmed Released but not sent Released and sent but not confirmed Withdrawing a Rail Tag Where rail tags have been incorrectly requested for a container the container can be deleted from this screen unless an ACCEPTED BY TERMINAL response from 1 Stop has been received or the tag request is still awaiting a respon
8. odule which allows users to send container rail Stop will then update Expedient with the status of the container rail move Rail Tagging Process Rail Tagging involves information flow between the Shipping Line the Importer Rail Freight Forwarder 1 Stop and the Terminal Rail Tagging is not permitted unless the following Business Rules are followed 1 The Container has not already been discharged from the Vessel If the container has already been discharged Rail Tagging must be arranged direct with the Terminal 2 The Container has not already been tagged by another user Duplicate requests are not accepted Release of the Container is not permitted until the following Business Rules are followed 1 Container must have already been tagged 2 A valid Electronic Import Delivery Order EIDO must be supplied The Rail Tagging module is related to the Container Management System in Expedient Expedient automatically sweeps for data at set intervals during the day to look for new data from Import Job Registration to either add or update information in the Container Management System CMS This can be customized to run at any time of the day however we recommend between one and three times a day The automatic process will look for all jobs registered within the last 45 days with the following criteria e Job Mode Sea Freight e Job Type F L F or X The process then confirms if the container is already in the CMS for the job in quest
9. quests can be re sent until the request has been acknowledged by the terminal Use the button in the Container Details screen Rail Tagging Rejection Use the button in the Container Details screen to view more details of the messages from 1 Stop including any Response Descriptions which indicate why a Rail Tagging request or Release request has been rejected CONF GMAMLOOO00S DO RELEASE CONTAINER RELEASE AIM COMMERCIAL RELEASE NUMBER INCORRECT GMANMLOOI ES mM GMAMLDOD ry Compete Reva OM Cancel If a response to a request has not been received check the History in the Container Details so see if the delay has been caused by missing information in the original request The error text received from the terminal will be displayed in the Response Desc column Clear the error advised by the terminal and resend the release instruction Complete Release If the terminal has released the container but the release does not appear in Expedient the container can be manually released in the Rail Tag History screen using the Complete Release button Complete Release The manual release will be recorded in the Container details screen as shown below 10 GB expedient TU 2 Container Details amp Document No 5 Container No NM171717666 Job No 3020655 Vessel ANL WANGARATTA ETA 25 06 2012 Departure Terminal ARSCO A RAPTIS SONS PTY LTD Rail Destination ASLPA PATRICK NS PORT BOTANY Carrier ARGWA AUST
10. rminal here to apply to this container only This is the 1 Stop code for the Rail Head Destination Use to search the available destinations Enter a destination here to apply to this container only This is the 1 Stop code for the Rail Carrier Use to search the available carriers Enter a carrier here to apply to this container only Select whether to tag the container This is the date the EDI Rail Tag request message was sent Validation Optional Optional Optional System Generated System Generated System Generated System Generated Optional Optional Optional Optional System Generated Default From Job Registration From Job Registration Yes if the container is on board No if the container has been discharged or is not on the manifest Field Name Description Validation Default Tag Confirmed This indicates that the Terminal has accepted the Rail System From 1 Stop Tag request Generated PIN Entered This indicates that an EDIO PIN number has been System logged against the container Generated EIDO PIN This is the PIN number for the container Optional Blank Release Select whether to release the container Optional Blank Release Sent This indicates when the Release instruction was sent System Generated Release This indicates if the terminal has confirmed the release System Confirmed of the container Generated Assign a Departure Terminal a Rail Destination and a Carrier t
11. se This restriction is so that if a container that has been tagged and accepted by 1 Stop the container cannot be deleted before the rail tagging process is completed Ifthe container has been accepted and the request is required to be cancelled please action the cancellation through the 1 Stop web site EIDO Pin Number Entering PIN Numbers When 1 Stop have confirmed the Terminal acceptance of the Rail Tag the EIDO Pin Number can be added to the Rail Tagging screen e To apply one EIDO Pin number to many containers use the toolbar button Enter PIN to open the EIDO Pin Number field On OK the PIN Entered column in the table will automatically update to Yes for all the containers listed e To apply an EIDO to a single container highlight the container line in the list and use the El toolbar button Enter PIN to open the EIDO Pin Number field The EIDO Pin will be applied to the selected container only If the terminal has responded with an error to the Release instruction the PIN number can be edited and the release instruction resent Clearing PIN Numbers El Use the toolbar button Clear PIN to clear an unwanted EIDO PIN number PIN numbers cannot be cleared within Expedient if the Release has already been sent for the container Releasing Containers When a Rail Tag request has been sent and accepted by the Terminal and an EIDO PIN Number has been entered for the container a Release request can be sent e To
12. select many containers to Release use the toolbar button Release All The Release column will automatically update to Yes for each container e To select a single container for Release select Yes in the Release column for the selected container Expedient will automatically send the Release requests at the specified time interval to 1 Stop a However if a Release is urgently needed use the toolbar button send Now to immediately send the Release message Output to CSV E Use the toolbar button Output to CSV to list in a spreadsheet all the container in the table on screen Rail Tagging Status View the progress of the Rail Tagging requests by double clicking on the container line in the Rail Tagging Screen This opens the Container Details screen which shows the most recent activity between Expedient and 1 Stop 2 Container Details E Sz Document No 301 Container No CLHU4448546 Job No 3001533 Departure Terminal CTLPB DP WORLD NS PORT BOTANY Rail Destination ASLPB PATRICK NS PORT BOTANY Carrier MIST MACARTHUR INTERMODAL SHIPPING Date Created 06 03 2012 wa By helens 1 Stop Details On Board Yes On 06 03 2012 Discharged No On Tag Details Tagged Yes Tagged On 06 03 2012 11 56 By helens Sent On 06 03 2012 11 56 Confirmed On 06 03 2012 05 08 Release Details EIDO Pin PIN1234 Released Yes Released On 08 03 2012 13 45 By helens Sent On 07 03 2012 08 32 Confirmed On 07 03 2012 10 08 Show message History Re
Download Pdf Manuals
Related Search