OS
From UG
(→All Message Types) |
(→Terminology) |
||
(37 intermediate revisions not shown) | |||
Line 5: | Line 5: | ||
'''Mantis parent:''' 4172 | '''Mantis parent:''' 4172 | ||
- | '''Mantis Category:''' | + | '''Mantis Category:''' proj: OS |
'''Wiki category:''' [[:Category:Ocean Status]] - see all related wikis there | '''Wiki category:''' [[:Category:Ocean Status]] - see all related wikis there | ||
- | == | + | == Terminology == |
+ | |||
+ | * '''Booking Request (BR)''' (aka 300) - document advising details of cargo and exporter's requirements of its physical movement (Estimated data). | ||
+ | |||
+ | * '''Shipping Instructions (SI)''' (aka 304) - same as BR but Actual and more detailed data. | ||
* '''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. | * '''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. | ||
- | * ''' | + | * '''Descartes''' - EDI vendor, VAN |
- | * ''' | + | * '''Cargosmart''' - EDI vendor, VAN |
+ | |||
+ | * '''GLN''' - '''VAN''' owned by '''Descartes''' | ||
- | + | == Business Analysis == | |
- | == Business Need == | + | === Core Business Need === |
- | Core | + | Core need is to automate the following: |
# booking ocean with carrier | # booking ocean with carrier | ||
# sending Shipping Instructions to carrier | # sending Shipping Instructions to carrier | ||
# receiving updates from carrier | # receiving updates from carrier | ||
- | |||
- | |||
=== Current Biz Process === | === Current Biz Process === | ||
- | Currently operators | + | Currently operators submit BR/SI to ocean carriers through the following options: |
- | + | * online systems (OOCL, CargoSmart) | |
+ | * emails, xls | ||
+ | |||
+ | Phone calls used to escalate absence of space. | ||
- | + | They manually update CT/Master record with the Ocean Status information they received. | |
+ | There are some specifics across the offices and operators/client companies: | ||
- | + | * In HK Shipper is required to send BR/SI to Jag so then Jag forwards these docs to Carrier with minor changes | |
- | === | + | * Some clients make decisions about what cargo to ship in the last moment. In such cases list of CTs in Master rec can be finalized also in the last moment. (HK and Arden in NY) |
+ | |||
+ | == Solution == | ||
+ | |||
+ | === Phases === | ||
+ | |||
+ | Phase one will cover possibly OOCL carrier only. | ||
+ | |||
+ | === Admin === | ||
Add UI Admin for Ocean Status Module. | 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? | |
- | ==== | + | ===== 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] | ||
- | + | ===== Steamshiplines ===== | |
- | + | Defines list of carriers that are currently connected 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 Flow ==== | |
- | + | ||
- | == | + | |
Message Exchange Scenario that covers all message types: | Message Exchange Scenario that covers all message types: | ||
Line 132: | Line 144: | ||
. | . | ||
day 35: (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]] | See [[EDI 300]] | ||
- | + | ==== Booking Update and Cancellation ==== | |
See [[EDI 300]] | See [[EDI 300]] | ||
- | + | ==== Booking Confirmation ==== | |
- | See [[EDI | + | See [[EDI 300]] |
- | + | ==== Ocean Shipping Instructions ==== | |
See [[EDI 304]] | See [[EDI 304]] | ||
- | + | ==== Shipment Status ==== | |
See [[EDI 315]] | See [[EDI 315]] | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- |
Current revision as of 00:18, 16 November 2013
Contents |
[edit] Info
Mantis parent: 4172
Mantis Category: proj: OS
Wiki category: Category:Ocean Status - see all related wikis there
[edit] Terminology
- Booking Request (BR) (aka 300) - document advising details of cargo and exporter's requirements of its physical movement (Estimated data).
- Shipping Instructions (SI) (aka 304) - same as BR but Actual and more detailed data.
- 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.
- Descartes - EDI vendor, VAN
- Cargosmart - EDI vendor, VAN
- GLN - VAN owned by Descartes
[edit] Business Analysis
[edit] Core Business Need
Core need is to automate the following:
- booking ocean with carrier
- sending Shipping Instructions to carrier
- receiving updates from carrier
[edit] Current Biz Process
Currently operators submit BR/SI to ocean carriers through the following options:
- online systems (OOCL, CargoSmart)
- emails, xls
Phone calls used to escalate absence of space.
They manually update CT/Master record with the Ocean Status information they received.
There are some specifics across the offices and operators/client companies:
- In HK Shipper is required to send BR/SI to Jag so then Jag forwards these docs to Carrier with minor changes
- Some clients make decisions about what cargo to ship in the last moment. In such cases list of CTs in Master rec can be finalized also in the last moment. (HK and Arden in NY)
[edit] Solution
[edit] Phases
Phase one will cover possibly OOCL carrier only.
[edit] Admin
Add UI Admin for Ocean Status Module.
See list of controls below:
[edit] Admin Controls
[edit] 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?
[edit] 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]
[edit] Steamshiplines
Defines list of carriers that are currently connected for EDI exchange
- multiselect
[edit] 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
[edit] 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)
[edit] Message Transport Level and Scheduled Process
[edit] 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.
[edit] Message process
One process will send/receive all messages accordingly to #Process Frequency defined in Admin.
[edit] Messages
[edit] Message Flow
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.
[edit] Booking Request
See EDI 300
[edit] Booking Update and Cancellation
See EDI 300
[edit] Booking Confirmation
See EDI 300
[edit] Ocean Shipping Instructions
See EDI 304
[edit] Shipment Status
See EDI 315