EDI 300

From UG

Revision as of 18:31, 14 November 2013 (edit) Alex (Talk | contribs) (→Statuses) ← Older edit		Current revision as of 15:10, 15 November 2013 (edit) (undo) Alex (Talk | contribs) (→CY Cutoff Date)
(84 intermediate revisions not shown)
Line 2:		Line 2:
	== Intro ==		== Intro ==
		+
		+	=== 300 ===
	EDI 300 is a '''Booking Request''' message.		EDI 300 is a '''Booking Request''' message.
Line 9:		Line 11:
	The shipper or forwarder can use this transaction set to reserve cargo space.		The shipper or forwarder can use this transaction set to reserve cargo space.
-	Types of 300 message:	+	=== 301 ===
-	* '''Initial Booking'''	+	EDI 301 is a '''Booking Confirmation''' message.
-	** '''Booking confirmation (301)''' that follows with statuses: confirmed, rejected, conditionally accepted, pending	+
-	* '''Jaguar Booking Update''' - booking amendment, initiated by the customer. You can only send amendments on confirmed, conditionally accepted or pending bookings. For rejected bookings a new initial booking needs to be sent	+	This is '''incoming''' message sent by Carrier to Jaguar.
-		+
-	* '''Jaguar Booking Cancellation''' -  initiated by the customer. You can only send cancellations on confirmed, conditionally accepted or pending bookings.	+
-		+
-	* '''Carrier Booking Update''' - booking amendment, initiated by the carrier. Supported by some carriers.	+
-		+
-	* '''Carrier Booking Cancellation''' -  initiated by the carrier.	+
		+	This message is used to confirm/reject/update the Booking Request.
	=== Message Flow ===		=== Message Flow ===
-	Below covers most scenarious except updates from carriers.	+	Below is a typical flow. See also [[#Actions]].
	[[File:300 and 301 exchange.png|700px]]		[[File:300 and 301 exchange.png|700px]]
Line 44:		Line 40:
	== Business Process ==		== Business Process ==
		+
		+	Below is defined for New Booking.
	=== Actual Master BP ===		=== Actual Master BP ===
-	When Master contains actual data.	+	When Master contains '''actual''' data.
	* 1/ Combine CTs into GRPs and then into Master (currently not all operators are doing this at the moment of booking)		* 1/ Combine CTs into GRPs and then into Master (currently not all operators are doing this at the moment of booking)
	* 2/		* 2/
-	** Enter all required booking information such as containers, Vessel, Voyage, etc.	+	** Enter all missing booking related information (if any)
-	** Pass all [[#Validations]].	+	** Pass all validations.
-	* 3/ Send booking request by pressing a button in '''Master Context Menu'''. See [[#Master UI 1]].	+	* 3/ Send booking request from [[#EDI tab]]. Most data will come from Master fields.
	=== Estimated Master BP ===		=== Estimated Master BP ===
-	When Master contains estimated data.	+	When Master contains '''estimated''' data.
	* 1/ create empty master from Master template		* 1/ create empty master from Master template
-	* 2/ steps 2,3 from [[#Regular BP]]	+	* 2/ steps 2,3 from [[#Actual Master BP]]
		+	** some data will be estimated and some of it entered on EDI template (example: weight per container)
	'''Note''': User will wrap CTs inside the master with one or more groups later on (before [[EDI 301]] is transmitted)		'''Note''': User will wrap CTs inside the master with one or more groups later on (before [[EDI 301]] is transmitted)
Line 69:		Line 68:
	This tab is active only if:		This tab is active only if:
		+
	[[Master#Steamshipline]] in given Master is on the list of		[[Master#Steamshipline]] in given Master is on the list of
	active carriers in OS Admin (see [[OS#Steamshiplines]])		active carriers in OS Admin (see [[OS#Steamshiplines]])
	'''AND'''		'''AND'''
-	MOT = FCL or Client Consol (hardcoded for now,	+	[[Master#Master Mode of Transport]] = Full Container Load (AW) OR
-	in ph2 is a part of Admin)	+	Full Container Load (MLB)
		+
		+	NOTE:
		+	-----
		+	When Master MOT is set as FCL (AW or MLB) then CT/GRP could have MOT set as:
		+	FCL (AW) or
		+	FCL(MLB) or
		+	Client Consol
	See mock up below.		See mock up below.
Line 79:		Line 86:
	[[File:EDI tab.JPG|700 px]]		[[File:EDI tab.JPG|700 px]]
-	=== Booking Request / Confirmation ===	+	=== Booking Request and Confirmation ===
	'''Columns''':		'''Columns''':
-	* '''ANSI# '''	+	* '''ANSI# ''' - 300 or 301 or 997
-	* '''Message type'''	+	* '''Message type''' - Booking or Confirmation or Acknowledgement
-	* '''Date'''	+	* '''Date''' - date/time of update
-	* '''Event'''	+	* '''Event''' - see [[#Events]]
-	* '''By'''	+	* '''By''' - Jag user name (First Name + Last Name) or CT2 or Carrier
-	* '''View Message'''	+	* '''View Message''' - Link to human readable copy of a saved message
-	* '''XML'''	+	* '''XML''' - XML version of a message
	'''Rows''':		'''Rows''':
-	Before exchange is initiated only one row exists with "Create" Action.	+	Each row corresponds to one update by operator or CT2 system or VAN/Carrier.
-	After that all updates by operator, CT2 system, VAN/Carrier are carefully posted.	+	'''Actions''':
-	'''Actions'''	+	* '''create''' - see [[#300 Create]]
-		+	* '''update''' - see [[#300 Update]]
-	See  [[#Actions]]	+	* '''cancel''' - see [[#300 Cancel]]
	=== Shipping Instructions ===		=== Shipping Instructions ===
Line 112:		Line 119:
	See [[EDI 304]]		See [[EDI 304]]
-	=== Statuses ===	+	=== Status Updates ===
		+
		+	See [[EDI 315]]
		+
		+	=== Events ===
		+
		+	Each '''event''' relates to 300 message and leads to a new '''status''' with the same name.
	'''300''':		'''300''':
-	* '''created''' (new) - message was initiated by Jag user, XML created by CT2 and waiting scheduled time to be transmitted to VAN/Carrier	+	* '''created''' (new) - 300 was initiated by Jag user, XML created by CT2 and waiting scheduled time to be transmitted to VAN/Carrier
-	* '''transmitted''' - message was posted into VAN/Carriers FTP folder, waiting to be read	+	* '''transmitted''' - 300 was posted into VAN/Carriers FTP folder, waiting to be read
	* '''updated''' - Jag user initiates updates to existing 300		* '''updated''' - Jag user initiates updates to existing 300
	* '''cancelled''' - Jag user cancels existing 300		* '''cancelled''' - Jag user cancels existing 300
	'''997''':		'''997''':
-	* '''accepted''' - no errors	+	* '''acknowledged''' - 300 has no errors (corresponds to 997 accepted) // set by VAN or carrier
-	* '''rejected''' - significant errors found (syntax, structure, validations, etc)	+	* '''error''' - significant errors found in 300 (syntax, structure, validations, etc)(corresponds to 997 rejected) // set by VAN or carrier
	'''301''':		'''301''':
-	* '''conditionally accepted''' - (TBD)	+	* '''conditionally accepted''' - (300 was set as conditionally accepted by carrier)
-	* '''pending''' - (TBD)	+	* '''pending''' - (300 was set as pending by carrier)
	* '''rejected''' (300 was rejected by carrier)		* '''rejected''' (300 was rejected by carrier)
	* '''confirmed''' (300 was confirmed by carrier)		* '''confirmed''' (300 was confirmed by carrier)
Line 132:		Line 145:
	* '''canceled''' (300 was canceled by carrier)		* '''canceled''' (300 was canceled by carrier)
-	=== Actions ===	+	=== Message 300 ===
		+
		+	==== Actions ====
	See actions available for each state:		See actions available for each state:
-	[[File:Trans diag 300 301.JPG| 600px]]	+	[[File:Transition diagramm for 300 301.jpg| 700px]]
		+	General Rule
		+	------------
		+	You can only send cancellations on confirmed,
		+	conditionally accepted or pending bookings.
-	==== 300 New ====	+	==== 300 Create ====
		+	Template to create new 300 request.
		+	See [[#300 Message Form]]
		+
		+	Action Type displayed as Create.
	==== 300 Update ====		==== 300 Update ====
		+	Template to update 300 request.
		+	Action Type displayed as Update.
		+
		+	See [[#300 Message Form]]
		+
		+	NOTE:
		+	-----
		+	System is not pulling data from last saved state of 300.
		+	System pulls from Master/other entities as if it is a new 300.
	==== 300 Cancel ====		==== 300 Cancel ====
Line 160:		Line 192:
	On '''Cancel''' return user to Master Editor.		On '''Cancel''' return user to Master Editor.
-	=== New Booking ===	+	==== 300 Message Form ====
-	Once button is pressed system should:	+	Opens in pop-up.
-	* validate required fields	+
-	* show [[#Booking Preview Screen]] with title "New Booking"	+
-	=== Update Booking ===	+	Fields are defined in [[OOCL 300#300 Data Elements]].
-	Once button is pressed system should:	+	All fields are read-only and are pulled from Master entity or other entities.
-	* validate required fields	+
-	* show [[#Booking Preview Screen]] with title "Update Booking"	+
-	=== Booking Preview Screen ===	+	See mock up below.
-	It presents:	+	[[File:300 template new general.JPG]]
-	* title: '''New''' or '''Update'''	+	==== Actions and Validations ====
-	* all information that will be sent to carrier	+
-	* missing required fields info (if any)	+
-	* "'''Transmit'''" button (disabled if not all required fields are present)	+
-	* "'''Go Back...'''" button	+
-	On "'''Transmit'''":	+	If all required fields are present then show these buttons:
-	* Confirmation pop-up will be shown. It will say: "Booking Confirmation has been scheduled."	+
-	* Messages will be scheduled as defined in [[OS#Frequency]]	+
-	* send e-mail to user who submitted with details of submission (TBC with Marc, details TBD)	+
-	On "'''Go Back...'''":	+	* '''Submit''' - submit message
-	* user will be returned to Master Editor, General tab to fix required fields.	+	* '''Cancel''' - return to Est Tab
-	== Data to Send ==	+	If not all required fields are present then indicate what fields needs to be filed in and show this button:
-	* see [[OOCL 300]]	+	* '''OK''' - return to Est Tab
-	== Reporting and Notifications ==	+	==== Reefer ====
-	=== Booking Status Line ===	+	If Cargo Nature = Reefer then "Reefer info section will be added".
-	See mock up under [[#Booking Menu]].	+	TBD
-	Shows latest status/event related to the Booking.	+	==== 300 Message View ====
-	Until 301 has been received I suggest to show 300 statuses:	+	Is a read only version of [[#300 Message Form]] - without any action buttons.
-	:''new, transmitted, accepted, rejected''	+	=== Message 301 ===
-	After 301 is received I suggest to show 301 message statuses:	+	Once message is received appropriate fields in CT2 will be updated - see [[OOCL 300#301 Data Elements]].
-	:''confirmed, rejected, conditionally accepted, pending''	+	==== 301 Message View ====
-	It is possible to post more info here, for example BOOKING UPDATED	+	Is a read only version of 301 Message sent by carriers.
-	but it would be more complex and not sure if needed -alex-	+
-	=== Master Comments Tab ===	+	Opens in pop-up.
-	Post all events/updates related to all messages here:	+	Fields are defined in [[OOCL 300#301 Data Elements]].
-	* Add record every time message was sent or received	+
-	* Record content of the message, operator who initiated.	+	System will compare value of each field as received and as stored in Master and display appropriate field status for a user:
		+
		+	* confirmed
		+	* new
		+	* changed
		+
		+	See mock up below.
		+
		+	[[File:301 example.JPG|500px]]
		+
		+	== Reporting and Notifications ==
		+
		+	=== Master Comments Tab ===
-	TBC: Marc had idea here - need to ask again	+	Suggest not to duplicate here since we have log on EDI tab.
	=== Email Notifications ===		=== Email Notifications ===
-	* notification of 997 (TBC)	+	Email all [[#Events]] to [[EDI 300#Export Operator]].
-	* email defined in [[#Booking Preview Screen]] (TBC)	+
	==== Email Template ====		==== Email Template ====
Line 233:		Line 264:
	'''Sent''': <date>		'''Sent''': <date>
	'''To''': <user name>		'''To''': <user name>
-	'''Subject''': Rejected: <protocol number><message type><related master numbers>	+	'''Subject''': Rejected: <protocol number> <Event> <By> for <master number>
	Dear <user name>,		Dear <user name>,
-	The following transmission was rejected:	+	Status has changed for <master number>:
-	<protocol number><message type><related master numbers>	+	<protocol number> was <Event>
		+
		+	Updated by: <By>
	This is automated message generated by Cybertrax 2 System.		This is automated message generated by Cybertrax 2 System.
Line 245:		Line 278:
	</pre>		</pre>
-	* <protocol number>: 300, 301, etc	+	<Event> and <By> as defined in [[#Booking Request and Confirmation]].
-	* <protocol name>: Booking Request, etc	+
-	* <related master numbers>: Master numbers related to thi transmission. Example: M1234, M12414	+
	=== Reports ===		=== Reports ===
-	==== 997 Reporting ====	+	==== Updated List Masters Report ====
-	Optional for 300 (since we have 301 as a response).	+	At the core we need a report that lists Masters in the system.
-	Required for 304.	+	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 Export Operator.
-	Dashboard similar to 997 dashboard in [[SI EDI]] (Data2Log).	+	Add these filters to List Masters:
-	Provides counter of Rejected messages.	+	* [[MOT]]
		+	* [[Master#Steamshipline]]
		+	* [[EDI 300#Created On Date]]
		+	* [[EDI 300#Export Operator]]
-	Must be based off of [[#List Masters]].	+	Add these output fields:
-	=== Log ===	+	* EDI Status
		+	** map to[[EDI 300#Events]]
-	Log all related events:	+	See mock up below.
-	* when Process started	+	[[File:List Masters.JPG | 700px]]
-	* when Process ended	+
-	* 300 sent	+
-	* 301 received	+
-	* 304 sent	+
-	* 315 received	+
-	* any 997 received	+
-	Additional info to include into log event description:	+	==== Rejected Booking Dashboard ====
-	* related list of Master numbers	+
-	* status for incoming messages (such as accepted/rejected)	+	More details TBD once concept is approved.
		+
		+	Based on [[#List Masters Report]]
		+
		+	Level 1.
		+
		+	[[File:Rejected booking dashboard.JPG | 700px]]
		+
		+	Level 2.
		+
		+	[[File:List Masters BC status rejected.JPG | 700px]]
		+
		+	==== Impending Events Dashboard ====
		+
		+	* Impending cargo cut off report/dashboard.
		+	* Impending documents cut off report/dashboard
		+
		+	See mock up below.
		+
		+	More details TBD once concept is approved.
		+
		+	[[File:Impending db.JPG | 700px]]
		+
		+	=== Log ===
		+
		+	Log all [[#Events]].
	== Misc ==		== Misc ==
		+
		+	=== Move type ===
		+
		+	Need to change [[Master#Move Type/MBL]] list in Admin:
		+
		+	* archive "port to port" item
		+	* will have 4 items:
		+	** "door to port" rename into "door to cy"
		+	** "port to door" rename into "cy to door"
		+	** "door to door" leave as is
		+	** "cy/cy" rename into "cy to cy"
		+
		+	NOTE:
		+	-----
		+	Alex: I feel we need to remove this from Admin and hard code
		+	as we say did with MOT.
		+	Marc: make this area very secure instead.
		+	Kostya: TBD
		+
		+	=== Jaguar Offices ===
		+
		+	Tech Note
		+	----------
		+	There is a problem.
		+	Office addr is stored in one field tblOffice.Address
		+	Need to re-factor DB table to add separate fields that hold Zip, City, etc
		+	and trigger to support existing field. Or other solution.
		+
		+	=== Changes to Carriers Admin ===
		+
		+	==== Contract Number ====
		+
		+	Contract number for contract between Jaguar and Steamshipline.
		+
		+	UI: Add to Admin > Carriers > Steamshiplines
		+
		+	* OOCL
		+	** Format: AN, 8 chars
		+	** example: MT136710
		+
		+
		+	=== Changes to Container Size Type Admin ===
		+
		+	==== Container Size Type ISO Code ====
		+
		+	In Admin > Transportation > Container Size/Type
		+
		+	* add field "ISO code", same format/validation as D2L codes
		+	* add Long Description field (100 char string)
		+
		+	NOTE:
		+	D2L codes are based on ISO but not identical.
		+	For example, open top type.
		+	In ISO it is tagged as "UT" or U0, U1 or .... or U5.
		+	In D2L classification it is "OT"
		+	References:
		+	ISO: http://en.wikipedia.org/wiki/ISO_6346
		+	D2L: [[File:Container_Codes.xls]]
		+	[[SI_EDI#SOW_18_Fix_Container_info]]
		+
		+	==== Reefer Indicator ====
		+
		+	Add "Reefer Indicator" attribute to container types. Values: "Y" or "No"
		+
		+	=== Changes to Master Container Table ===
		+
		+	==== Container Weight ====
		+
		+	For every container table add columns/fields:
		+
		+	* '''weight'''
		+	* '''unit'''
		+
		+	Also add selector to choose one of the following:
		+
		+	* '''actual weight'''
		+	** calculated weight based on commodity assignments to containers
		+	** weight field will be read-only
		+
		+	* '''estimated weight'''
		+	** in this case system will offer place to enter estimated weight required for EDI 300
		+	** this is for the case when no actual is available yet
		+	** store this into DB
		+
		+	* '''auto-populate max'''
		+	** in this case system will populate max weight for this type size of container
		+	** weight field will be read-only
		+	** default value
		+
		+	[[File:Container table.JPG| 700px]]
		+
		+	==== Container Weight Unit ====
		+
		+	Options:
		+
		+	* kg
		+	* lb
		+
		+	==== Reefer Info ====
		+
		+	If at least one contained is reefer - see [[#Reefer Indicator]] - then present additional form.
		+
		+	Fields below are not per container - they are per container table / per Master.
		+
		+	===== Generator Set =====
		+
		+	One value from the list.
		+
		+	Options: Not Required, Clip On, Underslung
		+
		+	UI: single select
		+
		+	===== RF Temperature =====
		+
		+	* UI: textbox;
		+	* cannot be greater than 25 degrees Celsius or 77 degrees Fahrenheit and cannot be less than -30 degrees Celsius or -22 degrees Fahrenheit.
		+
		+	===== RF Temperature Unit =====
		+
		+	* options: C (Celsius) or F(Farenheit) // Unit of measurement
		+	* UI: dropdown ; default = F;
		+
		+	===== Ventilation =====
		+
		+	* Numerical
		+	* min/max = 1/3 digits
		+
		+	===== Ventilation Unit =====
		+
		+	* options: Cubic Feet per minute, Cubic meter per hour, Degrees // Unit of measurement
		+	* UI: dropdown ; default = F;
		+
		+	===== Sensitive Cargo =====
		+
		+	* options: Not Sensitive, Blood Plazma, Ice Cream, USDA Requirement
		+	* UI: dropdown ; default = F;
		+
		+	===== CO2 =====
		+
		+	* Percentage of this gas.
		+	* numeric, 0 < x < 100
		+
		+	===== O2 =====
		+
		+	* Percentage of this gas.
		+	* numeric, 0 < x < 100
		+
		+	===== Container Atmosphere =====
		+
		+	One value from the list.
		+
		+	Options:
		+	* AFAM,
		+	* CA,
		+	* MA,
		+	* Magnum,
		+	* No Preference
		+
		+	UI: single select
		+
		+	=== New Master Controls for 300 ===
		+
		+	==== Hazardous ====
		+
		+	[[Master#Hazardous]] is calculated from CTs that belong to Master.
		+
		+	In there are no CTs in Master it would be set to No.
		+
		+	We need to add option to set estimated hazardous:
		+	* checkbox "use estimated"
		+	** when use estimated is activated then show two options Y/N
		+
		+	==== Special Stowage ====
		+
		+	Add new Master field.
		+
		+	Possible values:
		+
		+	* Stow below Deck
		+	* Stow on Deck
		+	* No Special Stowage
		+
		+	UI: radio group
		+
		+	Add to Master details bottom right - see mock up below.
		+
		+	==== Booking Remarks ====
		+
		+	* AN // size 1000 chars
		+	* UI: textarea
		+
		+	UI: Master Det tab, See mock up below.
		+
		+	[[File:Special stowage.JPG|700px]]
		+
		+	=== New fields for 301 ===
		+
		+	==== CY Cutoff Date ====
		+
		+	* // Date+Time // Last possible date cargo may be delivered to CY
		+	* Editable
		+	* M Det Tab, bottom right
		+
		+	=== New Master Fields for reporting ===
		+
		+	==== Created On Date ====
		+
		+	* date Master was created
		+	* similar to this field that we have for CT
		+	* UI: read only
		+	* DB: name it CreatedOnDate
		+
		+	==== Export Operator ====
		+
		+	* Operator who is responsible for this record on Export side
		+	* default to user who created Master
		+	* UI: [[Users Selector]]
		+	* DB: name it ExportOperatorUserId
	=== Grouping inside Master ===		=== Grouping inside Master ===
Line 294:		Line 566:
	or there is a benefit of cross sharing		or there is a benefit of cross sharing
-	=== Make Address Text firlds read only ===	+	=== Make Address Text fields read only ===
	Make the following fields read-only on Masters profile:		Make the following fields read-only on Masters profile:
Line 303:		Line 575:
	[[Master#Master Pick-up Text]]		[[Master#Master Pick-up Text]]
	[[Master#Master Delivery Text]]		[[Master#Master Delivery Text]]
-
-	=== Add Estimated vs Actual Haz ===
	=== Tags for required fields ===		=== Tags for required fields ===

---

Current revision as of 15:10, 15 November 2013

Contents 1 Intro 1.1 300 1.2 301 1.3 Message Flow 1.4 Limitations 2 Business Process 2.1 Actual Master BP 2.2 Estimated Master BP 3 EDI tab 3.1 Booking Request and Confirmation 3.2 Shipping Instructions 3.3 Status Updates 3.4 Events 3.5 Message 300 3.5.1 Actions 3.5.2 300 Create 3.5.3 300 Update 3.5.4 300 Cancel 3.5.5 300 Message Form 3.5.6 Actions and Validations 3.5.7 Reefer 3.5.8 300 Message View 3.6 Message 301 3.6.1 301 Message View 4 Reporting and Notifications 4.1 Master Comments Tab 4.2 Email Notifications 4.2.1 Email Template 4.3 Reports 4.3.1 Updated List Masters Report 4.3.2 Rejected Booking Dashboard 4.3.3 Impending Events Dashboard 4.4 Log 5 Misc 5.1 Move type 5.2 Jaguar Offices 5.3 Changes to Carriers Admin 5.3.1 Contract Number 5.4 Changes to Container Size Type Admin 5.4.1 Container Size Type ISO Code 5.4.2 Reefer Indicator 5.5 Changes to Master Container Table 5.5.1 Container Weight 5.5.2 Container Weight Unit 5.5.3 Reefer Info 5.5.3.1 Generator Set 5.5.3.2 RF Temperature 5.5.3.3 RF Temperature Unit 5.5.3.4 Ventilation 5.5.3.5 Ventilation Unit 5.5.3.6 Sensitive Cargo 5.5.3.7 CO2 5.5.3.8 O2 5.5.3.9 Container Atmosphere 5.6 New Master Controls for 300 5.6.1 Hazardous 5.6.2 Special Stowage 5.6.3 Booking Remarks 5.7 New fields for 301 5.7.1 CY Cutoff Date 5.8 New Master Fields for reporting 5.8.1 Created On Date 5.8.2 Export Operator 5.9 Grouping inside Master 5.10 Extended Master Templates 5.11 Make Address Text fields read only 5.12 Tags for required fields 6 EDI Vendor Implementations 7 Wiki source files

[edit] Intro

[edit] 300

EDI 300 is a Booking Request message.

It is an outgoing Message: Jaguar sends info to Carrier.

The shipper or forwarder can use this transaction set to reserve cargo space.

[edit] 301

EDI 301 is a Booking Confirmation message.

This is incoming message sent by Carrier to Jaguar.

This message is used to confirm/reject/update the Booking Request.

[edit] Message Flow

Below is a typical flow. See also #Actions.

[edit] Limitations

We impose this limitation:

At any moment in time there could be only one Booking Request/Update 300 
and related Booking Response 301

Theoretically we could send multiple alternative booking requests to:

• different steamshiplines (to maximize chance of any booking)
• same steamshipline (say different dates)

but we are not going to support this now.

[edit] Business Process

Below is defined for New Booking.

[edit] Actual Master BP

When Master contains actual data.

• 1/ Combine CTs into GRPs and then into Master (currently not all operators are doing this at the moment of booking)

• 2/
  • Enter all missing booking related information (if any)
  • Pass all validations.

• 3/ Send booking request from #EDI tab. Most data will come from Master fields.

[edit] Estimated Master BP

When Master contains estimated data.

• 1/ create empty master from Master template
• 2/ steps 2,3 from #Actual Master BP
  • some data will be estimated and some of it entered on EDI template (example: weight per container)

Note: User will wrap CTs inside the master with one or more groups later on (before EDI 301 is transmitted)

[edit] EDI tab

This tab is active only if:

Master#Steamshipline in given Master is on the list of 
active carriers in OS Admin (see OS#Steamshiplines) 
AND
Master#Master Mode of Transport = Full Container Load (AW) OR
                                      Full Container Load (MLB) 

NOTE:
-----
When Master MOT is set as FCL (AW or MLB) then CT/GRP could have MOT set as:
FCL (AW) or
FCL(MLB) or
Client Consol 

See mock up below.

[edit] Booking Request and Confirmation

Columns:

• ANSI# - 300 or 301 or 997

• Message type - Booking or Confirmation or Acknowledgement

• Date - date/time of update

• Event - see #Events

• By - Jag user name (First Name + Last Name) or CT2 or Carrier

• View Message - Link to human readable copy of a saved message

• XML - XML version of a message

Rows:

Each row corresponds to one update by operator or CT2 system or VAN/Carrier.

Actions:

• create - see #300 Create
• update - see #300 Update
• cancel - see #300 Cancel

[edit] Shipping Instructions

See EDI 304

[edit] Status Updates

See EDI 315

[edit] Events

Each event relates to 300 message and leads to a new status with the same name.

300:

• created (new) - 300 was initiated by Jag user, XML created by CT2 and waiting scheduled time to be transmitted to VAN/Carrier
• transmitted - 300 was posted into VAN/Carriers FTP folder, waiting to be read
• updated - Jag user initiates updates to existing 300
• cancelled - Jag user cancels existing 300

997:

• acknowledged - 300 has no errors (corresponds to 997 accepted) // set by VAN or carrier
• error - significant errors found in 300 (syntax, structure, validations, etc)(corresponds to 997 rejected) // set by VAN or carrier

301:

• conditionally accepted - (300 was set as conditionally accepted by carrier)
• pending - (300 was set as pending by carrier)
• rejected (300 was rejected by carrier)
• confirmed (300 was confirmed by carrier)
• updated (300 was updated by carrier)
• canceled (300 was canceled by carrier)

[edit] Message 300

[edit] Actions

See actions available for each state:

General Rule
------------
You can only send cancellations on confirmed, 
conditionally accepted or pending bookings. 

[edit] 300 Create

Template to create new 300 request.

See #300 Message Form

Action Type displayed as Create.

[edit] 300 Update

Template to update 300 request.

Action Type displayed as Update.

See #300 Message Form

NOTE:
-----
System is not pulling data from last saved state of 300.
System pulls from Master/other entities as if it is a new 300.

[edit] 300 Cancel

Present Confirmation pop-up:

Are you sure you want to cancel this Booking?
[OK]  [Cancel]

On OK:

• schedule cancellation message
• send e-mail to user who submitted with details of submission

On Cancel return user to Master Editor.

[edit] 300 Message Form

Opens in pop-up.

Fields are defined in OOCL 300#300 Data Elements.

All fields are read-only and are pulled from Master entity or other entities.

See mock up below.

[edit] Actions and Validations

If all required fields are present then show these buttons:

• Submit - submit message
• Cancel - return to Est Tab

If not all required fields are present then indicate what fields needs to be filed in and show this button:

• OK - return to Est Tab

[edit] Reefer

If Cargo Nature = Reefer then "Reefer info section will be added".

TBD

[edit] 300 Message View

Is a read only version of #300 Message Form - without any action buttons.

[edit] Message 301

Once message is received appropriate fields in CT2 will be updated - see OOCL 300#301 Data Elements.

[edit] 301 Message View

Is a read only version of 301 Message sent by carriers.

Opens in pop-up.

Fields are defined in OOCL 300#301 Data Elements.

System will compare value of each field as received and as stored in Master and display appropriate field status for a user:

• confirmed
• new
• changed

See mock up below.

[edit] Reporting and Notifications

[edit] Master Comments Tab

Suggest not to duplicate here since we have log on EDI tab.

[edit] Email Notifications

Email all #Events to EDI 300#Export Operator.

[edit] Email Template

'''From''': cybertrax@jaguarfreight.com [cybertrax@jaguarfreight.com]
'''Sent''': <date>
'''To''': <user name>
'''Subject''': Rejected: <protocol number> <Event> <By> for <master number>

Dear <user name>,

Status has changed for <master number>:

<protocol number> was <Event> 

Updated by: <By>

This is automated message generated by Cybertrax 2 System.

<Event> and <By> as defined in #Booking Request and Confirmation.

[edit] Reports

[edit] Updated List Masters Report

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 Export Operator.

Add these filters to List Masters:

• MOT
• Master#Steamshipline
• EDI 300#Created On Date
• EDI 300#Export Operator

Add these output fields:

• EDI Status
  • map toEDI 300#Events

See mock up below.

[edit] Rejected Booking Dashboard

More details TBD once concept is approved.

Based on #List Masters Report

Level 1.

Level 2.

[edit] Impending Events Dashboard

• Impending cargo cut off report/dashboard.
• Impending documents cut off report/dashboard

See mock up below.

More details TBD once concept is approved.

[edit] Log

Log all #Events.

[edit] Misc

[edit] Move type

Need to change Master#Move Type/MBL list in Admin:

• archive "port to port" item
• will have 4 items:
  • "door to port" rename into "door to cy"
  • "port to door" rename into "cy to door"
  • "door to door" leave as is
  • "cy/cy" rename into "cy to cy"

NOTE:
-----
Alex: I feel we need to remove this from Admin and hard code 
as we say did with MOT.
Marc: make this area very secure instead.
Kostya: TBD

[edit] Jaguar Offices

Tech Note
----------
There is a problem.
Office addr is stored in one field tblOffice.Address
Need to re-factor DB table to add separate fields that hold Zip, City, etc
and trigger to support existing field. Or other solution. 

[edit] Changes to Carriers Admin

[edit] Contract Number

Contract number for contract between Jaguar and Steamshipline.

UI: Add to Admin > Carriers > Steamshiplines

• OOCL
  • Format: AN, 8 chars
  • example: MT136710

[edit] Changes to Container Size Type Admin

[edit] Container Size Type ISO Code

In Admin > Transportation > Container Size/Type

• add field "ISO code", same format/validation as D2L codes
• add Long Description field (100 char string)

NOTE:
D2L codes are based on ISO but not identical.
For example, open top type.
In ISO it is tagged as "UT" or U0, U1 or .... or U5.
In D2L classification it is "OT"
References:
ISO: http://en.wikipedia.org/wiki/ISO_6346
D2L: File:Container Codes.xls
SI_EDI#SOW_18_Fix_Container_info

[edit] Reefer Indicator

Add "Reefer Indicator" attribute to container types. Values: "Y" or "No"

[edit] Changes to Master Container Table

[edit] Container Weight

For every container table add columns/fields:

• weight
• unit

Also add selector to choose one of the following:

• actual weight
  • calculated weight based on commodity assignments to containers
  • weight field will be read-only

• estimated weight
  • in this case system will offer place to enter estimated weight required for EDI 300
  • this is for the case when no actual is available yet
  • store this into DB

• auto-populate max
  • in this case system will populate max weight for this type size of container
  • weight field will be read-only
  • default value

[edit] Container Weight Unit

Options:

• kg
• lb

[edit] Reefer Info

If at least one contained is reefer - see #Reefer Indicator - then present additional form.

Fields below are not per container - they are per container table / per Master.

[edit] Generator Set

One value from the list.

Options: Not Required, Clip On, Underslung

UI: single select

[edit] RF Temperature

• UI: textbox;
• cannot be greater than 25 degrees Celsius or 77 degrees Fahrenheit and cannot be less than -30 degrees Celsius or -22 degrees Fahrenheit.

[edit] RF Temperature Unit

• options: C (Celsius) or F(Farenheit) // Unit of measurement
• UI: dropdown ; default = F;

[edit] Ventilation

• Numerical
• min/max = 1/3 digits

[edit] Ventilation Unit

• options: Cubic Feet per minute, Cubic meter per hour, Degrees // Unit of measurement
• UI: dropdown ; default = F;

[edit] Sensitive Cargo

• options: Not Sensitive, Blood Plazma, Ice Cream, USDA Requirement
• UI: dropdown ; default = F;

[edit] CO2

• Percentage of this gas.
• numeric, 0 < x < 100

[edit] O2

• Percentage of this gas.
• numeric, 0 < x < 100

[edit] Container Atmosphere

One value from the list.

Options:

• AFAM,
• CA,
• MA,
• Magnum,
• No Preference

UI: single select

[edit] New Master Controls for 300

[edit] Hazardous

Master#Hazardous is calculated from CTs that belong to Master.

In there are no CTs in Master it would be set to No.

We need to add option to set estimated hazardous:

• checkbox "use estimated"
  • when use estimated is activated then show two options Y/N

[edit] Special Stowage

Add new Master field.

Possible values:

• Stow below Deck
• Stow on Deck
• No Special Stowage

UI: radio group

Add to Master details bottom right - see mock up below.

[edit] Booking Remarks

• AN // size 1000 chars
• UI: textarea

UI: Master Det tab, See mock up below.

[edit] New fields for 301

[edit] CY Cutoff Date

• // Date+Time // Last possible date cargo may be delivered to CY
• Editable
• M Det Tab, bottom right

[edit] New Master Fields for reporting

[edit] Created On Date

• date Master was created
• similar to this field that we have for CT
• UI: read only
• DB: name it CreatedOnDate

[edit] Export Operator

• Operator who is responsible for this record on Export side
• default to user who created Master
• UI: Users Selector
• DB: name it ExportOperatorUserId

[edit] Grouping inside Master

Add ability to group/ungroup selected CTs inside the Master.

[edit] Extended 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.

TBD: ask opers/team leads if they cross share 
     or there is a benefit of cross sharing

[edit] Make Address Text fields read only

Make the following fields read-only on Masters profile:

Master#Master Shipper Text
Master#Master Consignee Text
Master#Master Notify Text
Master#Master Pick-up Text
Master#Master Delivery Text

[edit] Tags for required fields

EDI transmission assumes strict validations.

All required fields mast be marked as colored "*" (say orange).

Add note (in orange): "* Required fields for Booking Confirmation"

[edit] EDI Vendor Implementations

• CargoSmart: CSmart 300

[edit] Wiki source files

File:BR+SI+designs Nov13a.xls