From UG

Revision as of 21:48, 2 July 2013 (edit) Alex (Talk | contribs) (→Stop) ← Older edit		Revision as of 02:57, 3 July 2013 (edit) (undo) Alex (Talk | contribs) (→Definitions) Newer edit →
Line 276:		Line 276:
	=== Vehicle ===		=== Vehicle ===
-	It is a mobile machine that transports  cargo such as cars, trucks, trains, ships, boats and aircraft.	+	It is a mobile machine that transports  cargo such as trucks, trains, ships, boats and aircraft.
	=== Carrier ===		=== Carrier ===
Line 282:		Line 282:
	Company that operates [[#Vehicle]].		Company that operates [[#Vehicle]].
-	=== Stop ===	+	=== Location ===
		+
		+	==== Origin Door ====
		+
		+	==== Destination Door ====
		+
		+	==== Stop ====
	For given CT '''Stop''' is a temporary location to which [[#Carrier]] delivers it.		For given CT '''Stop''' is a temporary location to which [[#Carrier]] delivers it.

---

Revision as of 02:57, 3 July 2013

Contents 1 Info 2 Ver 1 3 Ver 2 3.1 Definitions 3.1.1 Vehicle 3.1.2 Carrier 3.1.3 Location 3.1.3.1 Origin Door 3.1.3.2 Destination Door 3.1.3.3 Stop 3.1.4 Leg 3.1.5 Non Stop Move 3.1.6 Multi Stop Move 3.1.7 Pool Point 3.2 Ver 2 Business Needs 3.3 Ver 2 Systems Analysis and Solution 3.3.1 Impact on ER Model 3.3.2 Impact on CT Editor 3.3.3 Impact on Reports 3.3.4 Impact on pdfs 3.3.5 Impact on Accounting 3.3.6 Impact on EDI interface 3.3.7 Impact on Notifications 4 SOWs

Info

"Pool Point" is a project. Main goal is to add Pool Point concept to the CT2 system.

First attempt was in 2010. See #Ver 1. This was never implemented.

Second attempt is current (2013). See #Ver2.

Ver 1

This section was commented out.

Ver 2

Parent mantis: 4168

Definitions

Vehicle

It is a mobile machine that transports cargo such as trucks, trains, ships, boats and aircraft.

Carrier

Company that operates #Vehicle.

Location

Origin Door

Destination Door

Stop

For given CT Stop is a temporary location to which #Carrier delivers it.

Later same carrier or another carrier picks CT up from there to move to another Stop or Destination Door.

Not all stops need to be recorded in the system. But some of them are mandatory (example: Port of Origin).

One special type of stop is a #Pool Point.

Leg

For given CT Leg is a one non-stop trip between Stops or between Origin Door and Stop or between Stop and Destination Door. It is done on the same #Vehicle with the same #Carrier.

Leg as entity has the following attributes:

• Origin
• Destination
• mode of transport (air vs truck vs ...)
• Carrier
• Vehicle id (such as trailer id for MOT= Truck Dom)

Non Stop Move

CT is moving Non stop if it moves from Pick Up/Origin Door to Delivery Location/Destination Door with one carrier (truck/plane/ship) without a #Stop.

In this case trip has one #Leg.

Multi Stop Move

In this case CT has a #Stop.

In some cases stops result in change of a carrier.

Such trips have more than one leg:

"Pick Up Location -> Stop1 -> Stop2 -> ... Stop N -> ... -> Delivery Location"

Pool Point

Pool Point is a special location / #Stop that is used for transferring and consolidation of CTs/commodities.

See example below.

Ver 2 Business Needs

• add a concept of #Pool Point to CT2
  • store them in the system with associated address and name

• when load info is passed from TMS to CT2:
  • identify if this CT travels through #Pool Point
  • tag CT as "delivered" / send "delivered" message to client users only if delivered to Delivery Location (not a Pool Point)

Above is possible due to recent fixes in TMS.

Above will eliminate workarounds operators have used so far to accommodate Pool Point moves.

Ver 2 Systems Analysis and Solution

Impact on ER Model

Decision is made to Implement #Multi Stop.

Now Truck - Domestic CT could be only part of one or two loads.

In case of two loads we are able to accomodate "Pick Up Trucker" (to Pool Point) and "Delivery Trucker" (from Pool Point) info:

• carrier name
• trailer id

It was suggested to increment ER structure to be able to collect info about #Multi Stop / multi leg trips.

For just 2 leg trips such as "Pick Up -> Pool Point/Stop -> Delivery" we could have created a simpler solution. But this would limit us in the future.

Note that this will be used across all MOTs in the future.

Impact on CT Editor

Interface will not change. Later it will be re-factored

Impact on Reports

Interface will not change.

Known reports affected:

• Main
• DR/KPIs

Impact on pdfs

None.

Impact on Accounting

TBD

Impact on EDI interface

Increment code to capture moves through Pool Point.

Use AddressTypeDesc="Pool Point" attribute/value pair of ShipToInformation.

Update DB.

Impact on Notifications

Notify client users only if delivered to Delivery Location.

Do not notify that delivered to Pool Point.

SOWs