OS
From UG
Contents |
Info
Mantis parent: 4172
Mantis Category: proj: OS
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 Analysis
Core Business Need
Core need is to automate the following:
- booking ocean with carrier
- sending Shipping Instructions to carrier
- receiving updates from carrier
Current Biz Process
Currently operators submit info to ocean carriers through the following options:
- online form
- emails
- phone calls
They manually update CT/Master record with the information they received.
Solution
Phases
Phase one will cover possibly OOCL carrier only.
Admin
Add UI Admin for Ocean Status Module.
See list of controls below:
Admin 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?
Process Frequency
Frequency (in min) we run Process that sends outgoing messages and checks for incoming
- numerical / min = 1 / max = 1440 [Note: 1440 min = 24 hours]
Connected Steamshiplines
Defines list of carriers we currently support for EDI exchange
- multiselect
Connecting through VAN vs connecting directly
We are still considering options as far as how integrate:
- option 1) through VAN
- option 2) directly to Steamshiplines
- in this case #FTP Credentials and #Process Frequency are defined per Steamshipline
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 #Process 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 . Note: VAN is optional
Specifics of each message are described in wikis 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