OS

From UG

Revision as of 02:34, 10 October 2013 (edit) Alex (Talk | contribs) (→Schedule and Log) ← Older edit		Current revision as of 00:18, 16 November 2013 (edit) (undo) Alex (Talk | contribs) (→Terminology)
(171 intermediate revisions not shown)
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	+
-	* oct 7, Mon -	+	* '''Cargosmart''' - EDI vendor, VAN
-	** Marc gave high level overview to joint meeting,	+
-	** Alex started working on spec more or less full time	+
-	* oct 10, Th - present spec to tech team	+
-	* oct 11 - get L0, present spec to the joint meeting	+
-	* oct 14, Mon - start dev	+
-	== 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
		+	# receiving updates from carrier
-	To be able to:	+	=== Current Biz Process ===
-	# book ocean with ocean carriers	+	Currently operators submit BR/SI to ocean carriers through the following options:
-	# subsequently receive updates electronically	+
-	== Business Analysis and Requirements ==	+	* online systems (OOCL, CargoSmart)
		+	* emails, xls
-	=== Current Biz Process ===	+	Phone calls used to escalate absence of space.
-	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.	+	They manually update CT/Master record with the Ocean Status information they received.
-	Bookings:	+	There are some specifics across the offices and operators/client companies:
-	* ???	+
-	Updates:	+	* In HK Shipper is required to send BR/SI to Jag so then Jag forwards these docs to Carrier with minor changes
-	* actual date of departure from Origin Port	+
-	* actual arrival to Destination Port	+	* 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)
		+
		+	== Solution ==
	=== Phases ===		=== Phases ===
-	Phase one will cover OOCL carrier only.	+	Phase one will cover possibly OOCL carrier only.
-	=== Technical Requirements ===	+	=== Admin ===
-	# We will do this through Descartes.	+	Add UI Admin for Ocean Status Module.
-	== Systems Analysis ==	+	See list of controls below:
-	== Solution ==	+	==== Admin Controls ====
-	=== Admin ===	+	===== FTP Credentials =====
		+
		+	? Should we also have a choice of protocol/port or post it as a constant?
-	Add the following controls:	+	* '''Address''' (sub-domain name?)
		+	** textbox
		+	** format/min/max TBD
-	* GLN FTP credentials: url, uname, pwd	+	* '''Login'''
-	* List of steamshiplines participating: On/Off switch	+	** textbox
-	* email notification group	+	** format/min/max TBD
-	=== Master Editor ===	+	* '''Password'''
		+	** textbox
		+	** format/min/max TBD
-	==== Add EDI Status panel ====	+	Define above for:
		+	* test and prod environments (could be different)
		+	* inbound and outbound locations
-	Add panel with EDI related statuses/info. This will show what messages have been sent/received.	+	... need to finalize above with Misha/AK/Vlad?
-	Example:	+	===== 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]
-	'''Booking Request:''' sent on 2013-10-16; 1:56 pm EST by Rob Link	+	===== Steamshiplines =====
-	'''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.	+	Defines list of carriers that are currently connected for EDI exchange
		+	* multiselect
-	==== Add Action Buttons ====	+	==== Connecting through VAN vs connecting directly ====
-	Add the following buttons:	+	We are still considering options as far as how integrate:
-	* send Booking Request	+	* option 1) through VAN
-	* send Shipping Instructions	+	* option 2) directly to Steamshiplines
		+	** in this case [[#FTP Credentials]] and [[#Process Frequency]] are defined per Steamshipline
-	==== Add Validations ====	+	==== Admin Misc ====
-	* Add required fields for transmissions:	+	'''Location/name''' of this Admin in CT2 menu:
-	** TBD	+	* Admin > EDI > Ocean EDI
-	** TBD	+	* move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset)
-	* Add validations related to message sequencing:	+	'''Restrict access''' to this Admin (add an option to user access table)
-	** prohibit sending Shipping Instructions before Booking Request	+
-	=== Messaging ===	+	=== Message Transport Level and Scheduled Process ===
-	==== Types of Messages ====	+	==== Message Transport level ====
-	This is a list of EDI messages being used here to exchange info between Jaguar and Steamshiline through Descartes GLN:	+	FTP protocol will be used on a transport level.
-	* '''Booking Request''' ( [[GLN 300]] )	+	Location of Inbound and Outbound folders TBD (Vendor speccific).
-	** 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]] )	+	FTP credentials are defined in [[#Ocean Status Admin]].
-	** This message is used to confirm the Booking Request (Message 300).	+
-	* '''Ocean Shipping Instructions''' ( [[GLN 304]] )	+	==== Message process ====
-	** 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]] )	+	One process will send/receive all messages accordingly to [[#Process Frequency]] defined in Admin.
-	** This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.	+
-	==== Message Exchange Scenarios ====	+	=== Messages ===
-	* '''Scenario One (main):'''	+	==== Message Flow ====
-	1) Jag operator initiates Booking Request 300	+	Message Exchange Scenario that covers all message types:
-	Jaguar -> GLN -> Steamshipline	+
-	2) Steamshipline responds with Booking Confirmation 301	+	day 1:  (Booking Request 300)         JAG -> VAN -> CARRIER
-	Jaguar <- GLN <- Steamshipline	+	.
		+	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
-	3) Jag operator sends Ocean Shipping Instructions 304	+	Specifics of each message are described in wikis below.
-	Jaguar -> GLN -> Steamshipline	+
-	4) Steamshipline sends Shipment Status 315 with Actual Departure Date:	+	==== Booking Request ====
-	Jaguar <- GLN <- Steamshipline	+
		+	See [[EDI 300]]
-	5) Steamshipline sends Shipment Status 315 with Actual Arrival Date:	+	==== Booking Update and Cancellation ====
-	Jaguar <- GLN <- Steamshipline	+
		+	See [[EDI 300]]
-	=== Email Notifications ===	+	==== Booking Confirmation ====
-	Notify group defined in Admin when these messages are received:	+	See [[EDI 300]]
-	* Booking Conf 301	+	==== Ocean Shipping Instructions ====
-	* Status 315	+
-	=== Reports ===	+	See [[EDI 304]]
-	TBD	+
-	=== Log ===	+	==== Shipment Status ====
-	TBD	+
-	== SOWs ==	+	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