OS

From UG

Revision as of 18:25, 27 October 2013 (edit) Alex (Talk | contribs) (→Booking Request) ← Older edit		Revision as of 18:26, 27 October 2013 (edit) (undo) Alex (Talk | contribs) (→Master Context Menu) Newer edit →
Line 92:		Line 92:
	==== Master Context Menu ====		==== Master Context Menu ====
-	Add Booking Request button to initiate [[GLN 300]] message.	+	Add Booking Request button to initiate [[300 Booking Request]] message.
	==== Master Doc Tab ====		==== Master Doc Tab ====

---

Revision as of 18:26, 27 October 2013

Contents 1 Info 2 Definitions 3 Business Need 4 Business Analysis and Requirements 4.1 Current Biz Process 4.2 Phases 5 Solution 5.1 Admin 5.2 HTS Feature 5.3 Master Editor 5.3.1 Master New Fields 5.3.2 Master Context Menu 5.3.3 Master Doc Tab 5.3.4 Master Comments Tab 5.3.5 Master Validations 5.4 Messaging 5.4.1 Message Transport level 5.4.2 All Message Types 5.4.2.1 Booking Request 5.4.2.2 Booking Confirmation 5.4.2.3 Ocean Shipping Instructions 5.4.2.4 Shipment Status 5.4.3 Message Exchange Scenarios 5.4.3.1 Example 1 5.4.3.2 Example 2 5.5 Email Notifications 5.6 Reports 5.6.1 Option 1 5.6.2 Option 2 5.6.3 Option 3 5.7 Log 5.8 Access 6 SOWs 6.1 SOW 1 Implement Admin 6.2 SOW 2 Modify CT and Master Editor 6.3 SOW 3 Implement All Message Types 6.4 SOW 4 Implement Email Notifications 6.5 SOW 5 Implement Reports 6.6 SOW 6 Implement Log 6.7 SOW 7 Implement Message Transport level

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.

Solution

Admin

Add the following entities into the system manageable through Admin or Property file:

• GLN FTP credentials: url, uname, pwd
• update frequency in secs
• on/off switch for transmission/receiving each of four types of messages

• List of steamshiplines participating: On/Off switch
• email notification groups
• ISO container size/types (small chance that we need this!)
• contract number+account bullet to Steamshipline entity (lane specific)
• commodity customs codes table (HTS)

HTS Feature

What:

• Add this field to commodity table (for each line): HTS Number

(commodity customs code). See http://www.foreign-trade.com/reference/hscode.htm

• This field should be presented and (be required only) for records that will be booked/processed through EDI
• For both ASN and CT records

How: (ideas):

• UI: combobox? tree?
• how to upload into system and how to maintain it there?
• for ASN recs entered by Shipper on Client

• automation option:
  • remember link btw HTS and SKU as it gets entered so we can do "auto-suggest"?
  • upload xls with link btw SKU and xls? (PO Issued By specific?)

Master Editor

Master New Fields

Add new fields:

• Temperature Requirement (if RF containers are requested)
  • numerical from and numerical to
• Cargo Cut Off Date
• Documentation Cut Off Date
• CY open date
• CY cut-off date
• MBL Type (original / express)
• AES (Export Declaration #) ex USA
• AMS / ACI code
• Any wood packing material

Master Context Menu

Add Booking Request button to initiate 300 Booking Request message.

Master Doc Tab

• modify MBL template to accomodate new fields
• on "generate report" send GLN 304

Master Comments Tab

Post all events/updates related to all messages here.

Master Validations

• Add required fields for transmissions - exact list TBD.

Messaging

Message Transport level

FTP protocol will be used on a transport level.

Location of Inbound and Outbound folders TBD.

FTP credentials are defined in Admin.

All Message Types

This is a list of EDI messages being used here to exchange info between Jaguar and Steamshiline through Descartes GLN - see below.

Booking Request

• see 300 Booking Request
  • The shipper or forwarder can use this transaction set to reserve cargo space.
  • Also used for Booking Update and Booking Cancellation

Booking Confirmation

• see 301 Booking Confirmation
  • This message is used to confirm the Booking Request (Message 300).

Ocean Shipping Instructions

• see 304 Shipping Instructions
  • 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

• 315 Shipment Status
  • This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.

Message Exchange Scenarios

Example 1

day 1: (Booking Request 300)          JAG -> VAN -> CARRIER
.
day 1:  (Booking Confirmation 301)    JAG <- VAN <- CARRIER 
.
day 4:  (Shipping Instructions 304)   JAG -> VAN -> CARRIER 
.
day 15: (Shipment Status 315)         JAG <- VAN <- CARRIER
.
day 35: (Shipment Status 315)         JAG <- VAN <- CARRIER

Example 2

Email Notifications

Notify group defined in Admin when these messages are received:

• Booking Conf 301
• Status 315

Reports

Option 1

Increment existing List Masters report to enable operator to look at EDI activity for desired group of Masters singled out by applying certain filters such as Steamshipline and Estimated day of Departure or port.

Add these filters to List Masters:

• MOT
• Master#Steamshipline
• Master#Origin Terminal Estimated Date
• more filters TBD

Add these output fields:

• 300 message Status: yet, sent
• 301 message Status: confirmed, rejected, conditionally accepted, pending
• 304 message Status: yet, sent
• 315 message status: there are 10-20 possible values, show the last received
• more fields TBD

Option 2

Dashboard for exceptions (rejected messages, etc).

Details TBD.

Option 3

Impending cargo cut off report/dashboard.

Impending documents cut off report/dashboard

Log

Log all related events.

Human initiated:

• send 300
• send 304

EDI initiated:

• received 301
• received various 315

Access

Restrict access as required.

SOWs

SOW 1 Implement Admin

mantis: TBD

dev: AK

spec: #Admin

SOW 2 Modify CT and Master Editor

mantis: TBD

dev: AK

spec: #Master Editor and #CT Editor

SOW 3 Implement All Message Types

mantis: TBD

dev: Misha

spec: #All Message Types

SOW 4 Implement Email Notifications

mantis: TBD

dev: AK

spec: #Email Notifications

SOW 5 Implement Reports

mantis: TBD

dev: Kostya

spec: #Reports

SOW 6 Implement Log

mantis: TBD

dev: AK

spec: #Log

SOW 7 Implement Message Transport level

mantis: TBD

dev: AK

spec: #Message Transport level