OS

From UG

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

Info

Mantis parent: 4172

Mantis Category: proj: OS

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

Terminology

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

• Shipping Instructions (SI) - 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

Business Analysis

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

Current Biz Process

Currently operators submit info to ocean carriers through the following options:

• online form
• emails
• phone calls

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

Solution

Phases

Phase one will cover possibly OOCL carrier only.

Admin

Add UI Admin for Ocean Status Module.

See list of controls below:

Admin Controls

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?

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]

Steamshiplines

Defines list of carriers that are currently connected for EDI exchange

• multiselect

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

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)

Message Transport Level and Scheduled Process

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.

Message process

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

Messages

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.

Booking Request

See EDI 300

Booking Update and Cancellation

See EDI 300

Booking Confirmation

See EDI 301

Ocean Shipping Instructions

See EDI 304

Shipment Status

See EDI 315