OS

From UG

Revision as of 02:29, 9 October 2013 (edit) Alex (Talk | contribs) ← Older edit		Current revision as of 00:18, 16 November 2013 (edit) (undo) Alex (Talk | contribs) (→Terminology)
(184 intermediate revisions not shown)
Line 1:		Line 1:
-	[[Category:OpsMisc]]	+	[[Category:Ocean Status]]
	== Info ==		== Info ==
Line 5:		Line 5:
	'''Mantis parent:''' 4172		'''Mantis parent:''' 4172
-	'''Mantis Category:''' Ocean Status	+	'''Mantis Category:''' proj: OS
-	== Contacts ==	+	'''Wiki category:''' [[:Category:Ocean Status]] - see all related wikis there
-	'''Eric Bossdorf'''	+	== Terminology ==
-	Descartes Systems Group	+
-	973-393-5008	+
-	ebossdorf@descartes.com	+
-	'''Eric Geerts'''	+	* '''Booking Request (BR)''' (aka 300) - document advising details of cargo and exporter's requirements of its physical movement (Estimated data).
-	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 ==	+	* '''Shipping Instructions (SI)''' (aka 304) - same as BR but Actual and more detailed data.
-	* sep 5 Th	+	* '''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.
-	** contract w/ Descartes is signed, green light from Marc, started writing wiki	+
-	** due date - ASAP per Marc	+
-	* sep 13 Fri	+	* '''Descartes''' - EDI vendor, VAN
-	** tech training w/ Eric	+
-	* sep 10 - 20:    BA/training phase	+	* '''Cargosmart''' - EDI vendor, VAN
-	* sep 23 - oct 4: SA/solution phase	+
-	== Definitions ==	+	* '''GLN''' - '''VAN''' owned by '''Descartes'''
-	== Training and Background Info ==	+	== Business Analysis ==
-	Business:	+	=== Core Business Need ===
-	Technical:	+	Core need is to automate the following:
-	== Business Need ==	+	# booking ocean with carrier
-		+	# sending  Shipping Instructions to carrier
-	To be able to:	+	# receiving updates from carrier
-		+
-	# book ocean with ocean carriers	+
-	# subsequently receive updates electronically	+
-		+
-	== Business Analysis and Requirements ==	+
	=== Current Biz Process ===		=== 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.	+	Currently operators submit BR/SI to ocean carriers through the following options:
-	Bookings:	+	* online systems (OOCL, CargoSmart)
-	* ???	+	* emails, xls
-	Updates:	+	Phone calls used to escalate absence of space.
-	* actual date of departure from Origin Port	+
-	* actual arrival to Destination Port	+
-	=== Phases ===	+	They manually update CT/Master record with the Ocean Status information they received.
-	Phase one will cover OOCL carrier only.	+	There are some specifics across the offices and operators/client companies:
-	=== Technical Requirements ===	+	* In HK Shipper is required to send BR/SI to Jag so then Jag forwards these docs to Carrier with minor changes
-	# We will do this through Descartes.	+	* Some clients make decisions about what cargo to ship in the last moment. In such cases list of CTs in Master rec can be finalized also in the last moment. (HK and Arden in NY)
-		+
-	== Systems Analysis ==	+
	== Solution ==		== Solution ==
-	=== Admin ===	+	=== Phases ===
-	=== Master Editor ===	+	Phase one will cover possibly OOCL carrier only.
-	=== Messaging ===	+	=== Admin ===
-	==== Message sequence ====	+	Add UI Admin for Ocean Status Module.
-	Messaging Diagram for major scenarios - see below.	+	See list of controls below:
-	Booking Request 300: Jaguar -> GLN -> Steamshipline	+	==== Admin Controls ====
-		+
-	Booking Confirmation 301: Jaguar <- GLN <- Steamshipline	+
-		+
-	Ocean Shipping Instructions 304: Jaguar -> GLN -> Steamshipline	+
-		+
-	Shipment Status 315: Jaguar <- GLN <- Steamshipline	+
-	==== Types of Messages ====	+	===== FTP Credentials =====
-	Specific messages are covered in the following wikis:	+	? Should we also have a choice of protocol/port or post it as a constant?
-	* [[300]] covers:	+	* '''Address''' (sub-domain name?)
-	** '''Booking Request'''	+	** textbox
-	** Booking Update	+	** format/min/max TBD
-	** Booking Cancellation	+
-	* [[301]] covers '''Booking Confirmation'''	+	* '''Login'''
		+	** textbox
		+	** format/min/max TBD
-	* [[304]] covers '''Ocean Shipping Instructions'''	+	* '''Password'''
		+	** textbox
		+	** format/min/max TBD
-	* [[315]] covers '''Shipment Status'''	+	Define above for:
		+	* test and prod environments (could be different)
		+	* inbound and outbound locations
-	=== Email Notifications ===	+	... need to finalize above with Misha/AK/Vlad?
-	=== Reports ===	+	===== Frequency =====
		+
		+	Frequency (in min) we run Process that sends outgoing messages and checks for incoming
		+	* numerical / min = 1 / max = 1440  [Note: 1440 min = 24 hours]
-	=== Log ===	+	===== Steamshiplines =====
-	== SOWs ==	+	Defines list of carriers that are currently connected for EDI exchange
		+	* multiselect
-	== See Also ==	+	==== Connecting through VAN vs connecting directly ====
-	* [[Air Status EDI]]	+	We are still considering options as far as how integrate:
		+	* option 1) through VAN
		+	* option 2) directly to Steamshiplines
		+	** in this case [[#FTP Credentials]] and [[#Process Frequency]] are defined per Steamshipline
-	=== Documentation ===	+	==== Admin Misc ====
-	xlsx files:	+	'''Location/name''' of this Admin in CT2 menu:
-	* [[File:CARRIER LIST SCAC.xlsx]]	+	* Admin > EDI > Ocean EDI
-	* [[File:Codelists - SMF OCEAN - v01.18.xlsx]]	+	* move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset)
-	* [[File:Event codes.xlsx]]	+
-	* [[File:General elements and components.xlsx]]	+
-	* [[File:SMF-Ocean v01.39 E.xlsx]]	+
-	* [[File:UN TP 7065 .xlsx]]	+
-	pdf files:	+	'''Restrict access''' to this Admin (add an option to user access table)
-	* [[:File:Ocean booking process 2.pdf]]	+
-	* [[File:WSAddressingForMyVan.pdf]]	+
-	xsd files:	+	=== Message Transport Level and Scheduled Process ===
-	* [[File:SMFGSFAPI V2100.xsd]]	+
-	xml files:	+	==== Message Transport level ====
-	* [[File:SMF booking response sample.xml]]	+
-	=== EDI Messages List ===	+	FTP protocol will be used on a transport level.
-	From http://www.seaboardmarine.com/SML/ui/EDI.aspx	+	Location of Inbound and Outbound folders TBD (Vendor speccific).
-	EDI 300 - Ocean Reservation (Booking Request)	+	FTP credentials are defined in [[#Ocean Status Admin]].
-	EDI 301 - Ocean Confirmation	+
-	EDI 304 - Ocean Shipping Instructions	+
-	EDI 310 - Ocean Freight Receipt and Invoice	+
-	EDI 315 - Ocean Status Details	+
		+	==== Message process ====
-	* Booking Request (Message 300)	+	One process will send/receive all messages accordingly to [[#Process Frequency]] defined in Admin.
-	** The shipper or forwarder can use this transaction set to reserve cargo space.	+
-	* Booking Confirmation (Message 301)	+	=== Messages ===
-	** This message is used to confirm the Booking Request (Message 300).	+
-	* Ocean Shipping Instructions (Message 304)	+	==== Message Flow ====
-	** 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)	+	Message Exchange Scenario that covers all message types:
-	** 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)	+	day 1:  (Booking Request 300)         JAG -> VAN -> CARRIER
-	** This system transmits inbound cargo information to US Customs and receives cargo release/hold status from US Customs.	+	.
		+	day 1:  (Booking Confirmation 301)   JAG <- VAN <- CARRIER
		+	.
		+	day 3:  (Booking Update 300)          JAG -> VAN -> CARRIER
		+	.
		+	day 3:  (Booking Confirmation 301)    JAG <- VAN <- CARRIER
		+	.
		+	day 10: (Shipping Instructions 304)  JAG -> VAN -> CARRIER
		+	.
		+	day 15: (Shipment Status 315)        JAG <- VAN <- CARRIER
		+	.
		+	day 35: (Shipment Status 315)        JAG <- VAN <- CARRIER
		+	.
		+	Note: VAN is optional
-	* Bill of Lading data and Ocean Invoice (Message 310)	+	Specifics of each message are described in wikis below.
-	** This message includes all information normally found on a bill of lading, including freight charges.	+
-	* Arrival Notification (Message 312)	+	==== Booking Request ====
-	** This message is used to notify Consignee of shipment arrival.	+
		+	See [[EDI 300]]
-	* Shipment Status (message 315)	+	==== Booking Update and Cancellation ====
-	** This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.	+
-		+	See [[EDI 300]]
-	* 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)	+	==== Booking Confirmation ====
-	** This message provides all information necessary to communicate the schedule and itinerary of an ocean vessel.	+
-	=== Links ===	+	See [[EDI 300]]
-	* http://www.melcogroup.com/pdf/OASISEdi1.pdf	+	==== Ocean Shipping Instructions ====
-	* http://www.inttra.com/home/assets/guides/ascx12_4010_301_out_v13.pdf	+	See [[EDI 304]]
-	* http://www.malaysiaexports.com/inex13.3.shipping.stowage.htm	+	==== Shipment Status ====
-	*	+	See [[EDI 315]]

---

Current revision as of 00:18, 16 November 2013

Contents 1 Info 2 Terminology 3 Business Analysis 3.1 Core Business Need 3.2 Current Biz Process 4 Solution 4.1 Phases 4.2 Admin 4.2.1 Admin Controls 4.2.1.1 FTP Credentials 4.2.1.2 Frequency 4.2.1.3 Steamshiplines 4.2.2 Connecting through VAN vs connecting directly 4.2.3 Admin Misc 4.3 Message Transport Level and Scheduled Process 4.3.1 Message Transport level 4.3.2 Message process 4.4 Messages 4.4.1 Message Flow 4.4.2 Booking Request 4.4.3 Booking Update and Cancellation 4.4.4 Booking Confirmation 4.4.5 Ocean Shipping Instructions 4.4.6 Shipment Status

[edit] Info

Mantis parent: 4172

Mantis Category: proj: OS

Wiki category: Category:Ocean Status - see all related wikis there

[edit] Terminology

• Booking Request (BR) (aka 300) - document advising details of cargo and exporter's requirements of its physical movement (Estimated data).

• Shipping Instructions (SI) (aka 304) - same as BR but Actual and more detailed data.

• 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.

• Descartes - EDI vendor, VAN

• Cargosmart - EDI vendor, VAN

• GLN - VAN owned by Descartes

[edit] Business Analysis

[edit] Core Business Need

Core need is to automate the following:

1. booking ocean with carrier
2. sending Shipping Instructions to carrier
3. receiving updates from carrier

[edit] Current Biz Process

Currently operators submit BR/SI to ocean carriers through the following options:

• online systems (OOCL, CargoSmart)
• emails, xls

Phone calls used to escalate absence of space.

They manually update CT/Master record with the Ocean Status information they received.

There are some specifics across the offices and operators/client companies:

• In HK Shipper is required to send BR/SI to Jag so then Jag forwards these docs to Carrier with minor changes

• Some clients make decisions about what cargo to ship in the last moment. In such cases list of CTs in Master rec can be finalized also in the last moment. (HK and Arden in NY)

[edit] Solution

[edit] Phases

Phase one will cover possibly OOCL carrier only.

[edit] Admin

Add UI Admin for Ocean Status Module.

See list of controls below:

[edit] Admin Controls

[edit] FTP Credentials

? Should we also have a choice of protocol/port or post it as a constant?

• Address (sub-domain name?)
  • textbox
  • format/min/max TBD

• Login
  • textbox
  • format/min/max TBD

• Password
  • textbox
  • format/min/max TBD

Define above for:

• test and prod environments (could be different)
• inbound and outbound locations

... need to finalize above with Misha/AK/Vlad?

[edit] Frequency

Frequency (in min) we run Process that sends outgoing messages and checks for incoming

• numerical / min = 1 / max = 1440 [Note: 1440 min = 24 hours]

[edit] Steamshiplines

Defines list of carriers that are currently connected for EDI exchange

• multiselect

[edit] Connecting through VAN vs connecting directly

We are still considering options as far as how integrate:

• option 1) through VAN
• option 2) directly to Steamshiplines
  • in this case #FTP Credentials and #Process Frequency are defined per Steamshipline

[edit] Admin Misc

Location/name of this Admin in CT2 menu:

• Admin > EDI > Ocean EDI
• move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset)

Restrict access to this Admin (add an option to user access table)

[edit] Message Transport Level and Scheduled Process

[edit] Message Transport level

FTP protocol will be used on a transport level.

Location of Inbound and Outbound folders TBD (Vendor speccific).

FTP credentials are defined in #Ocean Status Admin.

[edit] Message process

One process will send/receive all messages accordingly to #Process Frequency defined in Admin.

[edit] Messages

[edit] Message Flow

Message Exchange Scenario that covers all message types:

day 1:  (Booking Request 300)          JAG -> VAN -> CARRIER
.
day 1:  (Booking Confirmation 301)    JAG <- VAN <- CARRIER 
. 
day 3:  (Booking Update 300)          JAG -> VAN -> CARRIER
.
day 3:  (Booking Confirmation 301)    JAG <- VAN <- CARRIER
.
day 10: (Shipping Instructions 304)   JAG -> VAN -> CARRIER 
.
day 15: (Shipment Status 315)         JAG <- VAN <- CARRIER
.
day 35: (Shipment Status 315)         JAG <- VAN <- CARRIER
.
Note: VAN is optional

Specifics of each message are described in wikis below.

[edit] Booking Request

See EDI 300

[edit] Booking Update and Cancellation

See EDI 300

[edit] Booking Confirmation

See EDI 300

[edit] Ocean Shipping Instructions

See EDI 304

[edit] Shipment Status

See EDI 315