OS
From UG
(→Message Exchange Scenarios) |
(→Example 1) |
||
| Line 131: | Line 131: | ||
===== Example 1 ===== | ===== 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 ===== | ===== Example 2 ===== | ||
Revision as of 19:00, 25 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
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 Editor
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)
- numerical from and numerical to
- Cargo Cut Off Date
- Documentation Cut Off Date
- CY open date
- CY 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.
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 Booking Request 300
- 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: TBD
dev: AK
spec: #Admin
SOW 2 Modify CT and Master Editor
mantis: TBD
dev: AK
spec: #Master Editor and #CT Editor
SOW 3 Implement All Message Types
mantis: TBD
dev: Misha
spec: #All Message Types
SOW 4 Implement Email Notifications
mantis: TBD
dev: AK
spec: #Email Notifications
SOW 5 Implement Reports
mantis: TBD
dev: Kostya
spec: #Reports
SOW 6 Implement Log
mantis: TBD
dev: AK
spec: #Log
SOW 7 Implement Message Transport level
mantis: TBD
dev: AK
spec: #Message Transport level
