OS

From UG

Contents 1 Info 2 Definitions 3 Business Need 4 Business Analysis and Requirements 4.1 Current Biz Process 4.2 Phases 5 Prerequisites 5.1 Admin 5.2 Message Transport Level and Scheduled Process 5.2.1 Message Transport level 5.2.2 Message process 6 Messages 6.1 Booking Request 6.2 Booking Update and Cancellation 6.3 Booking Confirmation 6.4 Ocean Shipping Instructions 6.5 Shipment Status

Info

Mantis parent: 4172

Mantis Category: Ocean Status

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

Definitions

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

• GLN - VAN owned by Descartes

• Descartes - EDI vendor

• Cargosmart - EDI vendor

Business Need

Core needs is to automate the following:

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

Business Analysis and Requirements

Current Biz Process

Currently operators book with and get updates from ocean carriers manually. After that they manually update CT/Master record with the information they received.

Phases

Phase one will cover OOCL carrier only.

Prerequisites

Admin

Add UI Admin for Ocean Status Module.

Controls:

• FTP Credentials:
  • url textbox
  • uname textbox
  • pwd textbox
  • for outbound and inbound messages
  • for test and prod environments

• Period (min)
  • how often we run Process that sends messages/checks for incoming

• Use Message <type X>
  • checkbox
  • on/off switch for activating each of four types of messages: 300, 301, 314, 315

• Steamshiplines:
  • carriers participating in EDI exchange
  • multiselect

Location of this Admin in CT2 menu:

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

Restrict access to this Admin (add line to 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 frequency defined in Admin.

Messages

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

EDI messages being used here to exchange info between Jaguar and Steamshiline through VAN - see 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