OS

From UG

Revision as of 05:36, 8 November 2013 (edit) Alex (Talk | contribs) (→Prerequisites) ← Older edit		Revision as of 05:43, 8 November 2013 (edit) (undo) Alex (Talk | contribs) (→Prerequisites) Newer edit →
Line 83:		Line 83:
	One process will send/receive all messages accordingly to frequency defined in Admin.		One process will send/receive all messages accordingly to frequency defined in Admin.
-
-	Exception: 300 will be sent instantly.
-
-	=== Grouping inside Master ===
-
-	Add ability to group/ungroup selected CTs inside the Master.
-
-	=== Extend Master Templates ===
-
-	Following additional fields must be copied at the moment of creating a template from Master Clone.
-
-	Add column / filter of user who created them.
-
-	=== Est GW ===
-
-	* "Est GW" checkbox
-	** NOTE: "Use Estimated Weight for Booking Request instead of actual?"
-	** above master container table
-
-	=== Add Weight per container ===
-
-	* add extra column "GW" to cont table
-	** with dropdown with '''unit''' (kg/lb) in the header of column
-
-	* if Est GW is checked then show show textfield in each line (float, format same as GW in commod table) else show calculated read only from CTs
-	** if CTs have mixed kg/lb then recalculate in '''unit''' above table
	== Messages ==		== Messages ==

---

Revision as of 05:43, 8 November 2013

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 7 Reporting and Notifications 7.1 Master Comments Tab 7.2 Email Notifications 7.2.1 Email Template 7.3 Reports 7.3.1 List Masters 7.3.2 997 Reporting 7.3.3 Message specific Reports 7.4 Log

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

Reporting and Notifications

Master Comments Tab

Post all events/updates related to all messages here:

• Add record every time message was sent or received
• Record content of the message, operator who initiated.

Email Notifications

Send email to the Email Notification group defined in Ocean Status Admin.

Send in case of these situations:

• 301 received with Rejected status

• any 997 received with Rejected status

Attach received 997 or 301 with rejection status.

See e-mail below.

Email Template

'''From''': cybertrax@jaguarfreight.com [cybertrax@jaguarfreight.com]
'''Sent''': <date>
'''To''': <user name>
'''Subject''': Rejected: <protocol number><message type><related master numbers>

Dear <user name>,

The following transmission was rejected:

<protocol number><message type><related master numbers>

This is automated message generated by Cybertrax 2 System.

• <protocol number>: 300, 301, etc
• <protocol name>: Booking Request, etc
• <related master numbers>: Master numbers related to thi transmission. Example: M1234, M12414

Reports

List Masters

At the core we need a report that lists Masters in the system.

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: new, transmitted, accepted, rejected
• 301 message Status: confirmed, rejected, conditionally accepted, pending
• 304 message Status: new, transmitted, accepted, rejected
• 315 message status: there are 10-20 possible values, show the last received
• more fields TBD

See mock up below.

997 Reporting

Optional for 300 (since we have 301 as a response).

Required for 304.

Dashboard similar to 997 dashboard in SI EDI (Data2Log).

Provides counter of Rejected messages.

Must be based off of #List Masters.

Message specific Reports

Defined in respective wikis.

Log

Log all related events:

• when Process started
• when Process ended
• 300 sent
• 301 received
• 304 sent
• 315 received
• any 997 received

Additional info to include into log event description:

• related list of Master numbers
• status for incoming messages (such as accepted/rejected)