OS
From UG
(→Prerequisites) |
|||
Line 46: | Line 46: | ||
Controls: | Controls: | ||
- | + | ==== FTP Credentials === | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | * | + | ? Should we also have a choice of protocol/port or post it as a constant? |
- | ** | + | |
+ | * Address (sub-domain name?) | ||
+ | ** textbox | ||
+ | ** format/min/max TBD | ||
+ | |||
+ | * Login | ||
+ | ** textbox | ||
+ | ** format/min/max TBD | ||
+ | |||
+ | * Password | ||
+ | ** textbox | ||
+ | ** format/min/max TBD | ||
+ | |||
+ | Define above for: | ||
+ | * test and prod environments (could be different) | ||
+ | * inbound and outbound locations | ||
+ | |||
+ | ... need to finalize above with Misha/AK/Vlad? | ||
+ | |||
+ | ==== Period ==== | ||
+ | |||
+ | (in min) | ||
+ | ** Frequency (in min) we run Process that sends outgoing messages/checks for incoming | ||
+ | ** numerical / min = 1 / max = 1440 [Note: 1440 min = 24 hours] | ||
* '''Steamshiplines''': | * '''Steamshiplines''': | ||
Line 60: | Line 78: | ||
** multiselect | ** multiselect | ||
- | Location of this Admin in CT2 menu: | + | ==== Admin Misc ==== |
- | * Admin > EDI > Ocean | + | |
+ | '''Location/name''' of this Admin in CT2 menu: | ||
+ | * Admin > EDI > Ocean EDI | ||
* move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset) | * move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset) | ||
- | Restrict access to this Admin (add | + | '''Restrict access''' to this Admin (add an option to user access table) |
=== Message Transport Level and Scheduled Process === | === Message Transport Level and Scheduled Process === |
Revision as of 18:46, 10 November 2013
Contents |
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:
- booking ocean with carrier
- sending Shipping Instructions to carrier
- 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
? Should we also have a choice of protocol/port or post it as a constant?
- Address (sub-domain name?)
- textbox
- format/min/max TBD
- Login
- textbox
- format/min/max TBD
- Password
- textbox
- format/min/max TBD
Define above for:
- test and prod environments (could be different)
- inbound and outbound locations
... need to finalize above with Misha/AK/Vlad?
Period
(in min)
- Frequency (in min) we run Process that sends outgoing messages/checks for incoming
- numerical / min = 1 / max = 1440 [Note: 1440 min = 24 hours]
- Steamshiplines:
- carriers participating in EDI exchange
- multiselect
Admin Misc
Location/name of this Admin in CT2 menu:
- Admin > EDI > Ocean EDI
- move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset)
Restrict access to this Admin (add an option to user 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