OS
From UG
(→SOWs) |
(→Ocean Status Admin) |
||
| Line 49: | Line 49: | ||
** for test and prod envir | ** for test and prod envir | ||
| - | * | + | * Period (min) |
* on/off switch for transmission/receiving each of four types of messages | * on/off switch for transmission/receiving each of four types of messages | ||
| Line 57: | Line 57: | ||
* email notification groups | * email notification groups | ||
| - | + | TBD location/name of item in Admin, for example Air status/Ocean status together under Ops EDI. | |
==== Container Type Admin ==== | ==== Container Type Admin ==== | ||
Revision as of 16:15, 28 October 2013
Contents |
Info
Mantis parent: 4172
Mantis Category: Ocean Status
Wiki category: Category:Ocean Status - see all related wikis there
Definitions
- VAN - A Value-added Network (VAN) is a hosted service offering that acts as an intermediary between business partners sharing standards based or proprietary data. In the context of this project we use VAN as an intermediary between Jaguar and all carriers for message exchange.
- GLN - VAN owned by Descartes
- Descartes - EDI vendor
- Cargosmart - EDI vendor
Business Need
Core needs is to automate the following:
- booking ocean with carrier
- sending Shipping Instructions to carrier
- receiving updates from carrier
Business Analysis and Requirements
Current Biz Process
Currently operators book with and get updates from ocean carriers manually. After that they manually update CT/Master record with the information they received.
Phases
Phase one will cover OOCL carrier only.
Solution
Admins and Codes
Ocean Status Admin
Some of these can be kept in Properties file and not UI.
- FTP credentials: url, uname, pwd
- outbound and inbound
- for test and prod envir
- Period (min)
- on/off switch for transmission/receiving each of four types of messages
- list of steamshiplines participating: On/Off switch
- email notification groups
TBD location/name of item in Admin, for example Air status/Ocean status together under Ops EDI.
Container Type Admin
Container Type ISO Code
Related to http://wiki.jaguarfreight.com/wiki/SI_EDI#SOW_18_Fix_Container_info
In Admin > Transportation > Container Size/Type
If D2L codes are same as ISO then:
- Rename "D2L codes" into "ISO code"
If D2L codes are NOT same as ISO then:
- add additional field "ISO code", same format/validation
In both cases:
Reefer Indicator
Add "Reefer Indicator" attribute to container types. Values: "Y" or "No"
Steamshipline Admin
Add new attributes to Steamshipline object - see below.
Contract Number
Contract number for contract between Jaguar and Steamshipline.
UI: Add to Admin > Carriers > Steamshiplines
Format: TBD
Account Bullet
Additional info related to #Contract Number.
This is lane (Country or Region) specific.
UI: Add to Admin > Carriers > Steamshiplines
Format: TBD
In Steamshipline Admin or Ocean Status Admin.
Misc Constants
AMS SCAC Code
- AMS SCAC Code - SCAC/ACI Code. For USA trade, this is a code with normally 4 digits for AMS filing, we need this code to submit AMS filing and Jaguar is registered. Our AMS SCAC code is JAFR.
Access
Restrict access.
HTS Feature
What:
- Add this field to commodity table (for each line): HTS Number
(commodity customs code). See http://www.foreign-trade.com/reference/hscode.htm
- This field should be presented and (be required only) for records that will be booked/processed through EDI
- For both ASN and CT records
How: (ideas):
- UI: combobox? tree?
- how to upload into system and how to maintain it there?
- for ASN recs entered by Shipper on Client
HTS Automation
- postpone for phase 2?
- remember link btw HTS and SKU as it gets entered so we can do "auto-suggest"?
- upload xls with link btw SKU and xls? (PO Issued By specific?)
Changes in Master Object and Master Profile
New Container Fields
RF Temperature
- RF Temperature // Format: 9999.99 // Temperature Requirement for RF containers.
- UI: add to container profile; textfield; default = TBD
- RF Temperature Unit // C (Celsius) or F(Farenheit) // Unit of measurement
- UI: add to container profile; dropdown ; default = TBD;
Above needs to be presented/validated only for RF type of containers - use #Reefer Indicator to distinguish.
Editable in M only or in CT as well when CTs are under Master.
New Master Fields
Add new attributes to Master Entity:
- Cargo Cut Off Date // Date+Time // Last possible date cargoes may be delivered to a ship or designated point.
- Read only, M Det Tab
- Documentation Cut Off Date // Date+Time // Last possible date documentation can be sent.
- Read only, M Det Tab
- CY open date // Date+Time // First possible date cargoes may be delivered to a ship or designated point.
- CY cut-off date - same as Cargo Cut Off Date?
- MBL Type // "original" or "express" // Defines what type of MBL is used. Takes one of two values: "original" or "express"
- UI: add to Master Gen Tab below "2. Move type/MBL", default to "original"
- AES Number // AN, 15 digits // aka Internal Transaction Number (ITN), id received from Automated Export System. The ITN consists of the letters “AES” followed by the ITN: for example, “AES X20080930987654. See also http://en.wikipedia.org/wiki/Automated_Export_System
- Wood packing material // "used" or "not used" // Any wooden packaging material is used or not, this is what we have to declare to the shipping line for every single booking to USA and Canada.
Master Context Menu
Add Booking Request button to initiate 300 Booking Request message.
Message will be sent immediately and confirmation pop-up will be shown.
Master Doc Tab
- detect that given master is a subject to EDI transmission (carrier is on the EDI list)
- modify MBL template to accommodate EDI case (add new fields)
- on "generate report" send 304 Shipping Instructions and generate pdf, show confirmation
- Master Bill Of Lading
Master Comments Tab
Post all events/updates related to all messages here:
- Every time message was sent or received, content of the message, operator who initiated
Messaging
Message Transport level
FTP protocol will be used on a transport level.
Location of Inbound and Outbound folders TBD.
FTP credentials are defined in Admin.
All Message Types
This is a list of EDI messages being used here to exchange info between Jaguar and Steamshiline through Descartes GLN - see below.
Booking Request
- see 300 Booking Request
- The shipper or forwarder can use this transaction set to reserve cargo space.
- Also used for Booking Update and Booking Cancellation
Booking Confirmation
- see 301 Booking Confirmation
- This message is used to confirm the Booking Request (Message 300).
Ocean Shipping Instructions
- see 304 Shipping Instructions
- This message supplies the same information as the Shipper's Letter of Instruction. It provides all the information necessary to prepare and distribute a contract of carriage (ocean bill of lading and other shipping documents).
Shipment Status
- 315 Shipment Status
- This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.
Message Exchange Scenarios
Example 1
day 1: (Booking Request 300) JAG -> VAN -> CARRIER . day 1: (Booking Confirmation 301) JAG <- VAN <- CARRIER . day 4: (Shipping Instructions 304) JAG -> VAN -> CARRIER . day 15: (Shipment Status 315) JAG <- VAN <- CARRIER . day 35: (Shipment Status 315) JAG <- VAN <- CARRIER
Example 2
Email Notifications
Notify group defined in Admin when these messages are received:
- Booking Conf 301
- Status 315
Reports
Option 1
Increment existing List Masters report to enable operator to look at EDI activity for desired group of Masters singled out by applying certain filters such as Steamshipline and Estimated day of Departure or port.
Add these filters to List Masters:
- MOT
- Master#Steamshipline
- Master#Origin Terminal Estimated Date
- more filters TBD
Add these output fields:
- 300 message Status: yet, sent
- 301 message Status: confirmed, rejected, conditionally accepted, pending
- 304 message Status: yet, sent
- 315 message status: there are 10-20 possible values, show the last received
- more fields TBD
Option 2
Dashboard for exceptions (rejected messages, etc).
Details TBD.
Option 3
Impending cargo cut off report/dashboard.
Impending documents cut off report/dashboard
Log
Log all related events.
Human initiated:
- send 300
- send 304
EDI initiated:
- received 301
- received various 315
Access
Restrict access as required.
SOWs
SOW 1 Implement Admin
mantis: 4332
dev: AK
spec: #Admin
SOW 2 Modify CT and Master Editor
mantis: 4357
dev: AK
spec: #Master Editor and #CT Editor
SOW 3 Implement All Message Types
mantis: 4334
dev: Misha
spec: #All Message Types
SOW 4 Implement Email Notifications
mantis: 4335
dev: AK
spec: #Email Notifications
SOW 5 Implement Reports
mantis: 4336
dev: Kostya
spec: #Reports
SOW 6 Implement Log
mantis: 4337
dev: AK
spec: #Log
SOW 7 Implement Message Transport level
mantis: 4338
dev: AK
spec: #Message Transport level
SOW 8 HTS Feature
mantis: 4333
dev: AK
spec: #HTS Feature
