OS

From UG

Revision as of 02:28, 10 October 2013 (edit) Alex (Talk | contribs) (→See Also) ← Older edit		Revision as of 02:34, 10 October 2013 (edit) (undo) Alex (Talk | contribs) (→Schedule and Log) Newer edit →
Line 31:		Line 31:
	** tech training w/ Eric		** tech training w/ Eric
-	* sep 10 - 20:    BA/training phase	+	* oct 7, Mon -
-	* sep 23 - oct 4: SA/solution phase	+	** 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 ==		== Definitions ==

---

Revision as of 02:34, 10 October 2013

Contents 1 Info 2 Contacts 3 Schedule and Log 4 Definitions 5 Training and Background Info 6 Business Need 7 Business Analysis and Requirements 7.1 Current Biz Process 7.2 Phases 7.3 Technical Requirements 8 Systems Analysis 9 Solution 9.1 Admin 9.2 Master Editor 9.2.1 Add EDI Status panel 9.2.2 Add Action Buttons 9.2.3 Add Validations 9.3 Messaging 9.3.1 Types of Messages 9.3.2 Message Exchange Scenarios 9.4 Email Notifications 9.5 Reports 9.6 Log 10 SOWs

Info

Mantis parent: 4172

Mantis Category: Ocean Status

Contacts

Eric Bossdorf
Descartes Systems Group
973-393-5008
ebossdorf@descartes.com

Eric Geerts 
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

• sep 5 Th
  • contract w/ Descartes is signed, green light from Marc, started writing wiki
  • due date - ASAP per Marc

• sep 13 Fri
  • tech training w/ Eric

• oct 7, Mon -
  • 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

Training and Background Info

Business:

Technical:

Business Need

To be able to:

1. book ocean with ocean carriers
2. subsequently receive updates electronically

Business Analysis and Requirements

Current Biz Process

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.

Bookings:

•  ???

Updates:

• actual date of departure from Origin Port
• actual arrival to Destination Port

Phases

Phase one will cover OOCL carrier only.

Technical Requirements

1. We will do this through Descartes.

Systems Analysis

Solution

Admin

Add the following controls:

• GLN FTP credentials: url, uname, pwd
• List of steamshiplines participating: On/Off switch
• email notification group

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:
  • TBD
  • 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

TBD

Log

TBD

SOWs