OS
From UG
(→Master New Fields) |
(→Master Editor) |
||
| Line 45: | Line 45: | ||
* contract number+account bullet to Steamshipline entity (lane specific) | * contract number+account bullet to Steamshipline entity (lane specific) | ||
* commodity customs codes table (selected when SKU is defined) | * commodity customs codes table (selected when SKU is defined) | ||
| + | |||
| + | === CT New Fields === | ||
| + | |||
| + | Add this attribute to commodity table (for each line): | ||
| + | |||
| + | * HTS # (commodity customs code) | ||
| + | ** dropdown | ||
| + | ** list of codes is defined in Admin | ||
=== Master Editor === | === Master Editor === | ||
Revision as of 06:19, 11 October 2013
Contents |
Info
Mantis parent: 4172
Mantis Category: Ocean Status
Wiki category: Category:Ocean Status - see all related wikis there
Definitions
- GLN - platform that is intermediary between Jaguar and all carriers for message exchange
- Descartes - EDI vendor who owns GLN
Business Need
Core needs is to automate the following:
- book ocean with carrier
- send Shipping Instructions to carrier
- receive 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
Admin
Add the following entities into the system manageable through Admin or Property file:
- GLN FTP credentials: url, uname, pwd
- List of steamshiplines participating: On/Off switch
- email notification groups
- ISO container size/types
- contract number+account bullet to Steamshipline entity (lane specific)
- commodity customs codes table (selected when SKU is defined)
CT New Fields
Add this attribute to commodity table (for each line):
- HTS # (commodity customs code)
- dropdown
- list of codes is defined in Admin
Master Editor
Master New Fields
Add new fields:
- Temperature Requirement (if RF containers are requested)
- Cargo Cut Off Date
- Documentation Cut Off Date
- CY open date
- CV cut-off date
- MBL Type (original / express)
- AES (Export Declaration #) ex USA
- AMS / ACI code
- Any wood packing material
Master Context Menu
Add Booking Request button to initiate GLN 300 message.
Master Doc Tab
- modify MBL template to accomodate new fields
- on "generate report" send GLN 304
Master Comments Tab
Post all events/updates related to all messages here.
Master Validations
- Add required fields for transmissions - exact list TBD.
- Add validations related to message sequencing:
- prohibit sending Shipping Instructions before Booking Request
Messaging
Types of Messages
This is a list of EDI messages being used here to exchange info between Jaguar and Steamshiline through Descartes GLN:
- Booking Request ( GLN 300 )
- The shipper or forwarder can use this transaction set to reserve cargo space.
- Also used for Booking Update and Booking Cancellation
- Booking Confirmation ( GLN 301 )
- This message is used to confirm the Booking Request (Message 300).
- Ocean Shipping Instructions ( GLN 304 )
- 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 ( GLN 315 )
- This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.
Message Exchange Scenarios
- Scenario One (main):
1) Jag operator initiates Booking Request 300
Jaguar -> GLN -> Steamshipline
2) Steamshipline responds with Booking Confirmation 301
Jaguar <- GLN <- Steamshipline
3) Jag operator sends Ocean Shipping Instructions 304
Jaguar -> GLN -> Steamshipline
4) Steamshipline sends Shipment Status 315 with Actual Departure Date:
Jaguar <- GLN <- Steamshipline
5) Steamshipline sends Shipment Status 315 with Actual Arrival Date:
Jaguar <- GLN <- Steamshipline
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
SOWs
SOW 1 Admin
mantis: TBD
dev: AK
spec: #Admin
SOW 2 Master Editor
mantis: TBD
dev: AK
spec: #Master Editor
SOW 3 Messaging
mantis: TBD
dev: Misha
spec: #Messaging
SOW 4 Email Notifications
mantis: TBD
dev: AK
spec: #Email Notifications
SOW 5 Reports
mantis: TBD
dev: Kostya
spec: #Reports
SOW 6 Log
mantis: TBD
dev: AK
spec: #Log
