OS
From UG
(Difference between revisions)
(→Messaging) |
(→Email Notifications) |
||
| Line 152: | Line 152: | ||
=== Email Notifications === | === Email Notifications === | ||
| - | + | ||
| + | Notify group defined in Admin when these messages are received: | ||
| + | |||
| + | * Booking Conf 301 | ||
| + | * Status 315 | ||
=== Reports === | === Reports === | ||
Revision as of 03:34, 9 October 2013
Contents |
Info
Mantis parent: 4172
Mantis Category: Ocean Status
Contacts
Eric Bossdorf Descartes Systems Group 973-393-5008 ebossdorf@descartes.com
Eric Geerts Director, product management Duwijckstraat 17 B-2500 Lier - Belgium Tel +32 (0)3 800 06 00 Mobile +32 (0)499058781 Email address: egeerts@descartes.com
Schedule and Log
- sep 5 Th
- contract w/ Descartes is signed, green light from Marc, started writing wiki
- due date - ASAP per Marc
- sep 13 Fri
- tech training w/ Eric
- sep 10 - 20: BA/training phase
- sep 23 - oct 4: SA/solution phase
Definitions
Training and Background Info
Business:
Technical:
Business Need
To be able to:
- book ocean with ocean carriers
- subsequently receive updates electronically
Business Analysis and Requirements
Current Biz Process
Currently operators book with and get updates from ocean carriers manually (TBD in details). After that they manually update CT/Master record with the information they received. I suppose it is the following.
Bookings:
- ???
Updates:
- actual date of departure from Origin Port
- actual arrival to Destination Port
Phases
Phase one will cover OOCL carrier only.
Technical Requirements
- We will do this through Descartes.
Systems Analysis
Solution
Admin
Add the following controls:
- GLN FTP credentials: url, uname, pwd
- List of steamshiplines participating: On/Off switch
Master Editor
Add EDI Status panel
Add panel with EDI related statuses/info. This will show what messages have been sent/received.
Example:
Booking Request: sent on 2013-10-16; 1:56 pm EST by Rob Link Booking Confirmation: pending Shipping Instructions: not yet Status updates: not yet
This is similar to GMS status panel by nature.
Add to bottom right corner of Master Details Tab where there is empty space.
Add Action Buttons
Add the following buttons:
- send Booking Request
- send Shipping Instructions
Add Validations
- Add required fields for transmissions:
- TBD
- 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
TBD
Log
TBD
SOWs
See Also
Documentation
xlsx files:
- File:CARRIER LIST SCAC.xlsx
- File:Codelists - SMF OCEAN - v01.18.xlsx
- File:Event codes.xlsx
- File:General elements and components.xlsx
- File:SMF-Ocean v01.39 E.xlsx
- File:UN TP 7065 .xlsx
pdf files:
xsd files:
xml files:
EDI Messages List
From http://www.seaboardmarine.com/SML/ui/EDI.aspx
EDI 300 - Ocean Reservation (Booking Request) EDI 301 - Ocean Confirmation EDI 304 - Ocean Shipping Instructions EDI 310 - Ocean Freight Receipt and Invoice EDI 315 - Ocean Status Details
- Booking Request (Message 300)
- The shipper or forwarder can use this transaction set to reserve cargo space.
- Booking Confirmation (Message 301)
- This message is used to confirm the Booking Request (Message 300).
- Ocean Shipping Instructions (Message 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).
- Manifest data (Message 309)
- This message is a summary of bills of lading on a manifest. It's currently being used to exchange information with several overseas governmental authorities.
- Automated Manifest System (AMS) with US Customs (Message 309)
- This system transmits inbound cargo information to US Customs and receives cargo release/hold status from US Customs.
- Bill of Lading data and Ocean Invoice (Message 310)
- This message includes all information normally found on a bill of lading, including freight charges.
- Arrival Notification (Message 312)
- This message is used to notify Consignee of shipment arrival.
- Shipment Status (message 315)
- This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.
- Terminal Operations and Intermodal Ramp Activity (Message 322)
- This message is used to communicate terminal and intermodal ramp activities (i.e. "ingates" and "outdates")
- Vessel Schedule and Itinerary (Message 323)
- This message provides all information necessary to communicate the schedule and itinerary of an ocean vessel.
