OS

From UG

Revision as of 02:16, 9 October 2013 (edit) Alex (Talk | contribs) ← Older edit		Revision as of 02:29, 9 October 2013 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 21:		Line 21:
	Mobile +32 (0)499058781		Mobile +32 (0)499058781
	Email address: egeerts@descartes.com		Email address: egeerts@descartes.com
-
	== Schedule and Log ==		== Schedule and Log ==
Line 75:		Line 74:
	== Solution ==		== Solution ==
-	== Messaging ==	+	=== Admin ===
-	=== Message sequence ===	+	=== Master Editor ===
		+
		+	=== Messaging ===
		+
		+	==== Message sequence ====
	Messaging Diagram for major scenarios - see below.		Messaging Diagram for major scenarios - see below.
Line 89:		Line 92:
	Shipment Status 315: Jaguar <- GLN <- Steamshipline		Shipment Status 315: Jaguar <- GLN <- Steamshipline
-	=== Types of Messages ===	+	==== Types of Messages ====
	Specific messages are covered in the following wikis:		Specific messages are covered in the following wikis:
Line 103:		Line 106:
	* [[315]] covers '''Shipment Status'''		* [[315]] covers '''Shipment Status'''
		+
		+	=== Email Notifications ===
		+
		+	=== Reports ===
		+
		+	=== Log ===
	== SOWs ==		== SOWs ==

---

Revision as of 02:29, 9 October 2013

Contents 1 Info 2 Contacts 3 Schedule and Log 4 Definitions 5 Training and Background Info 6 Business Need 7 Business Analysis and Requirements 7.1 Current Biz Process 7.2 Phases 7.3 Technical Requirements 8 Systems Analysis 9 Solution 9.1 Admin 9.2 Master Editor 9.3 Messaging 9.3.1 Message sequence 9.3.2 Types of Messages 9.4 Email Notifications 9.5 Reports 9.6 Log 10 SOWs 11 See Also 11.1 Documentation 11.2 EDI Messages List 11.3 Links

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:

1. book ocean with ocean carriers
2. 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

1. We will do this through Descartes.

Systems Analysis

Solution

Admin

Master Editor

Messaging

Message sequence

Messaging Diagram for major scenarios - see below.

Booking Request 300: Jaguar -> GLN -> Steamshipline

Booking Confirmation 301: Jaguar <- GLN <- Steamshipline

Ocean Shipping Instructions 304: Jaguar -> GLN -> Steamshipline

Shipment Status 315: Jaguar <- GLN <- Steamshipline

Types of Messages

Specific messages are covered in the following wikis:

• 300 covers:
  • Booking Request
  • Booking Update
  • Booking Cancellation

• 301 covers Booking Confirmation

• 304 covers Ocean Shipping Instructions

• 315 covers Shipment Status

Email Notifications

Reports

Log

SOWs

See Also

• Air Status EDI

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:

• File:Ocean booking process 2.pdf
• File:WSAddressingForMyVan.pdf

xsd files:

• File:SMFGSFAPI V2100.xsd

xml files:

• File:SMF booking response sample.xml

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.

Links

• http://www.melcogroup.com/pdf/OASISEdi1.pdf

• http://www.inttra.com/home/assets/guides/ascx12_4010_301_out_v13.pdf

• http://www.malaysiaexports.com/inex13.3.shipping.stowage.htm