OS

From UG

Revision as of 03:42, 10 October 2013 (edit) Alex (Talk | contribs) (→Admin) ← Older edit		Revision as of 04:14, 10 October 2013 (edit) (undo) Alex (Talk | contribs) (→SOWs) Newer edit →
Line 152:		Line 152:
	== SOWs ==		== SOWs ==
		+
		+	=== SOW 1 Admin ===
		+
		+	'''mantis''': TBD
		+
		+	'''dev''': AK
		+
		+	'''spec''': [[#Admin]]
		+
		+	=== SOW 2 Master Editor ===
		+
		+	'''mantis''': TBD
		+
		+	'''dev''': AK
		+
		+	'''spec''': [[#Master Editor]]
		+
		+	=== SOW 3 Messaging ===
		+
		+	'''mantis''': TBD
		+
		+	'''dev''': Misha
		+
		+	'''spec''': [[#Messaging]]
		+
		+	=== SOW 4 Email Notifications ===
		+
		+	'''mantis''': TBD
		+
		+	'''dev''': AK
		+
		+	'''spec''': [[#Email Notifications]]
		+
		+	=== SOW 5 Reports ===
		+
		+	'''mantis''': TBD
		+
		+	'''dev''': Kostya
		+
		+	'''spec''': [[#Reports]]
		+
		+	=== SOW 6 Log ===
		+
		+	'''mantis''': TBD
		+
		+	'''dev''': AK
		+
		+	'''spec''': [[#Log]]

---

Revision as of 04:14, 10 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 Master Editor 5.2.1 Add EDI Status panel 5.2.2 Add Action Buttons 5.2.3 Add Validations 5.3 Messaging 5.3.1 Types of Messages 5.3.2 Message Exchange Scenarios 5.4 Email Notifications 5.5 Reports 5.6 Log 6 SOWs 6.1 SOW 1 Admin 6.2 SOW 2 Master Editor 6.3 SOW 3 Messaging 6.4 SOW 4 Email Notifications 6.5 SOW 5 Reports 6.6 SOW 6 Log

Info

Mantis parent: 4172

Mantis Category: Ocean Status

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

Definitions

• GLN - platform that is intermediary between Jaguar and all carriers for message exchange

• Descartes - EDI vendor who owns GLN

Business Need

Core needs is to automate the following:

1. book ocean with carrier
2. send Shipping Instructions to carrier
3. receive 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
• List of steamshiplines participating: On/Off switch
• email notification group
• various core EDI related entities such as ISO container types;
• additional EDI related entities, full list contain 29 of them - see File:Codelists - SMF OCEAN - v01.18.xlsx

Master Editor

Add EDI Status panel

Add panel with EDI related statuses/info. This will show what messages have been sent/received.

Example:

Booking Request: sent on 2013-10-16; 1:56 pm EST by Rob Link
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.

Add Action Buttons

Add the following buttons:

• send Booking Request
• send Shipping Instructions

Add Validations

• Add required fields for transmissions - exact list TBD.

• Add validations related to message sequencing:
  • prohibit sending Shipping Instructions before Booking Request

Messaging

Types of Messages

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

• Booking Request ( GLN 300 )
  • 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 )
  • This message is used to confirm the Booking Request (Message 300).

• Ocean Shipping Instructions ( GLN 304 )
  • 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 )
  • This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.

Message Exchange Scenarios

• Scenario One (main):

1) Jag operator initiates Booking Request 300
        Jaguar -> GLN -> Steamshipline

2) Steamshipline responds with Booking Confirmation 301
        Jaguar <- GLN <- Steamshipline 

3) Jag operator sends Ocean Shipping Instructions 304 
        Jaguar -> GLN -> Steamshipline 

4) Steamshipline sends Shipment Status 315 with Actual Departure Date: 
        Jaguar <- GLN <- Steamshipline

5) Steamshipline sends Shipment Status 315 with Actual Arrival Date: 
        Jaguar <- GLN <- Steamshipline

Email Notifications

Notify group defined in Admin when these messages are received:

• Booking Conf 301
• Status 315

Reports

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

Log

Log all related events.

Human initiated:

• send 300
• send 304

EDI initiated:

• received 301
• received various 315

SOWs

SOW 1 Admin

mantis: TBD

dev: AK

spec: #Admin

SOW 2 Master Editor

mantis: TBD

dev: AK

spec: #Master Editor

SOW 3 Messaging

mantis: TBD

dev: Misha

spec: #Messaging

SOW 4 Email Notifications

mantis: TBD

dev: AK

spec: #Email Notifications

SOW 5 Reports

mantis: TBD

dev: Kostya

spec: #Reports

SOW 6 Log

mantis: TBD

dev: AK

spec: #Log