New Arden Trucking Project NATP (main)

From UG

(Difference between revisions)
Jump to: navigation, search
(Billing Solution)
(Suggested Solution: added Comment solution)
 
(46 intermediate revisions not shown)
Line 3: Line 3:
== General Info ==
== General Info ==
-
* parent mantis: 0001884: (CT2 Misc) Ops Changes for NATP (New Arden Trucking Project)
+
* parent mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=1884 1884]
-
* requested for Release: April 29
+
* requested for Release: April 29 (staging)
== Business Needs and Requirements ==
== Business Needs and Requirements ==
-
=== March 24 Meeting ===
+
=== Meetings ===
-
During this meeting all core and some detailed requirements have been presented and discussed. There is one related document created by Director of Operations - see ''Operations May 01'' tab on ''Copy of Trucking Project - 2010-03-24.xls'' file attached to mantis [http://mantis.jaguarfreight.com/mantis/view.php?id=1884 1884].
+
==== March 24 Meeting ====
 +
 
 +
* During this meeting all core and some detailed requirements have been presented and discussed. There is one related document created by Director of Operations - see ''Operations May 01'' tab on ''Copy of Trucking Project - 2010-03-24.xls'' file attached to mantis [http://mantis.jaguarfreight.com/mantis/view.php?id=1884 1884].
 +
 
 +
==== March 29 Meeting ====
 +
 
 +
* Core design has been reviewed.
 +
* Additional requirements discussed.
 +
* Reports finalized
 +
* See them documented in ''EA DOM (NATP) - 2010-03-29.xls '' in [http://mantis.jaguarfreight.com/mantis/view.php?id=1884 1884]
 +
 
 +
==== March 31 Meeting ====
 +
 
 +
* Additional requirements discussed.
 +
* Docs and Billing finalized
 +
* See them documented in ''EA DOM - 2010-03-31.xls'' in [http://mantis.jaguarfreight.com/mantis/view.php?id=1884 1884]
 +
 
 +
==== April 5 Meeting ====
 +
 
 +
* TMS features has been discussed - see [http://mantis.jaguarfreight.com/mantis/view.php?id=1920 0001920: (*NATP) TMS features]
=== Deadline ===
=== Deadline ===
It was requested to have all features in production by May 1.
It was requested to have all features in production by May 1.
 +
 +
=== Existing Business Process and Use Cases ===
 +
Does not exist - this is a new business.
=== Summary ===
=== Summary ===
Line 21: Line 43:
* [[#Billing]]  
* [[#Billing]]  
-
* [[#Reporting]]
+
* [[#Reports]]
* [[#Documents]]
* [[#Documents]]
* [[#Virtual Groups]]
* [[#Virtual Groups]]
Line 62: Line 84:
=== Documents ===
=== Documents ===
-
* Manifest. Is this [[Trucking Manifest (M)]] or something else?
+
* Truck Detailed Manifest.  
-
* D/O. Is this a [[Delivery Order Trucking Domestic]] or [[DO Truck (M)]] or something else?
+
* D/O.  
See also: [[#Virtual Groups]].
See also: [[#Virtual Groups]].
=== Flags ===
=== Flags ===
 +
See [[#New fields]]
-
Could be called modes as well.
+
=== New Fields ===
-
* "On Customer Hold"  
+
==== On Customer Hold  ====
-
:: On hold means on hold in OUR WAREHOUSE meaning the shipment was already "picked up" and is technically "in-transit" but with the ON HOLD differentiation from a "normal" in-transit" shipment.
+
-
* "Pending Approval Mode"
+
See [[CT#On_Customer_Hold]]
-
:: Identical to "undefined"
+
 
 +
==== Pending Approval Mode ====
 +
* (radio Y/N; default to N)
 +
* Gen tab, bottom right corner
 +
* MOT = all
 +
 
 +
 
 +
 
 +
==== Consol Warehouse ====
 +
* Code to identify specific warehouse. List of 4 numbers: {1,2,3,4}.
 +
* Add to botom right of Gen Tab
 +
* For now only for Truck modes (later we might add it to all MOTs)
 +
 
 +
Developers Note:
 +
--------------
 +
If it does not take much more time, please create Admin so that they can manage their own lists
 +
instead of hard coded 1,2,3,4. Or we can add this feature later.
 +
 
 +
==== Delivery Trucker ====
 +
 
 +
* We need this field added to Truck MOT ()
 +
 
 +
Developers Note:
 +
----------------
 +
This is the same field as [[CT#Delivery Trucker]] we have for Ocean and Air.
 +
 
 +
These flags/fields will be used as filters to generate reports, documents, groups.
 +
 
 +
==== PT number ====
 +
 
 +
see [[CT#PT Number]]
 +
 
 +
==== DT number ====
 +
 
 +
see [[CT#DT Number]]
-
These flags will be used as filters to generate reports, documents, groups.
 
See also: [[#Virtual Groups]].
See also: [[#Virtual Groups]].
=== File Upload ===
=== File Upload ===
 +
 +
Upload files (POD's) functionality required.
See: [[#Virtual Groups]]
See: [[#Virtual Groups]]
Line 105: Line 162:
  For: ESTIMATED DELIVERY TOMORROW
  For: ESTIMATED DELIVERY TOMORROW
-
List of selection criteria. (Let's call each of them '''virtual group classifier'''. These are basically filters that define what is in the group and what is out.)
+
List of selection criteria.  
* Client Company   
* Client Company   
Line 139: Line 196:
=== Flags Solution ===
=== Flags Solution ===
-
This requirements translates into adding 2 fields to Truck modes:
+
See [[Gen_Tab_(component)#m1895]]
-
 
+
-
* On Customer Hold (radio Y/N; default to N)
+
-
* Pending Approval (radio Y/N; default to N)
+
-
 
+
-
Add to bottom right corner on Gen Tab.
+
=== Virtual Groups Solution ===
=== Virtual Groups Solution ===
Line 152: Line 204:
=== Reports Solution ===
=== Reports Solution ===
-
* To Schedule Report: see [[Schedule Report for Virtual Group]]
+
* [[In Transit Report]] (change)
-
* To Generate Report: see [[Generate Report for Virtual Group]]
+
* [[Previous Day Collection]] (change)
 +
 
 +
* [[Previous Day Delivery]] (change)
 +
 
 +
* [[Approval Report]] (new report)
 +
 
 +
* [[Impending Collection]] (new report)  (Impending Col/Del)
 +
 
 +
* [[Impending Delivery]] (new report)  (Impending Col Del)
 +
 
 +
* [[Schedule Report for Virtual Group]]
 +
 
 +
* [[Generate Report for Virtual Group]]
=== Documents Solution ===
=== Documents Solution ===
Line 167: Line 231:
See [[File Upload for Virtual Group]]
See [[File Upload for Virtual Group]]
 +
 +
=== Comment solution ===
 +
 +
See [[Comment for Virtual Group]]
 +
 +
=== Misc ===
 +
 +
* [[Widget_Copy_Yes_/_No_(feature)#Implement_this_feature_for_Shipper_/_Consignee]]
 +
 +
=== Suggested Business Process and Use Cases ===
 +
 +
See [[Business Process and Use Cases for NATP]].
 +
 +
=== April 21 Changes ===
 +
see [[April 21 NATP Changes]]

Current revision as of 16:47, 24 October 2010


Contents

[edit] General Info

  • parent mantis: 1884
  • requested for Release: April 29 (staging)

[edit] Business Needs and Requirements

[edit] Meetings

[edit] March 24 Meeting

  • During this meeting all core and some detailed requirements have been presented and discussed. There is one related document created by Director of Operations - see Operations May 01 tab on Copy of Trucking Project - 2010-03-24.xls file attached to mantis 1884.

[edit] March 29 Meeting

  • Core design has been reviewed.
  • Additional requirements discussed.
  • Reports finalized
  • See them documented in EA DOM (NATP) - 2010-03-29.xls in 1884

[edit] March 31 Meeting

  • Additional requirements discussed.
  • Docs and Billing finalized
  • See them documented in EA DOM - 2010-03-31.xls in 1884

[edit] April 5 Meeting

[edit] Deadline

It was requested to have all features in production by May 1.

[edit] Existing Business Process and Use Cases

Does not exist - this is a new business.

[edit] Summary

Below is a full list of functionality requested:

[edit] Billing

One option is to bill once a day a group of CTs. Group could be defined by conditions: delivered=today; delivery location=XX.

Many other options should be possible: based on another date conditions, location conditions.

We might bill weekly.

See also: #Virtual Groups.

[edit] Reports

  • In Transit Report. Add filters:
    • Shipper / pick up location
    • Carrier / Trucker
    • Delivery location/consignee
  • Previous Day Collections / Deliveries changes:
    • none
  • "Approval Report" (new report). Filters:
    • Consignee
  • "Impending Pick ups" (new report) (based on estimated dates). Similar in concept to existing impending reports. Filters:
    • shipper/pick up location
    • carrier?
  • "Impending deliveries" (new report) (based on estimated dates). Similar in concept to existing impending reports. Filters:
    • Delivery location/consignee
    • Carrier?

See also: #Virtual Groups.

[edit] Documents

  • Truck Detailed Manifest.
  • D/O.

See also: #Virtual Groups.

[edit] Flags

See #New fields

[edit] New Fields

[edit] On Customer Hold

See CT#On_Customer_Hold

[edit] Pending Approval Mode

  • (radio Y/N; default to N)
  • Gen tab, bottom right corner
  • MOT = all


[edit] Consol Warehouse

  • Code to identify specific warehouse. List of 4 numbers: {1,2,3,4}.
  • Add to botom right of Gen Tab
  • For now only for Truck modes (later we might add it to all MOTs)
Developers Note:
--------------
If it does not take much more time, please create Admin so that they can manage their own lists
instead of hard coded 1,2,3,4. Or we can add this feature later.

[edit] Delivery Trucker

  • We need this field added to Truck MOT ()
Developers Note:
----------------
This is the same field as CT#Delivery Trucker we have for Ocean and Air.

These flags/fields will be used as filters to generate reports, documents, groups.

[edit] PT number

see CT#PT Number

[edit] DT number

see CT#DT Number


See also: #Virtual Groups.

[edit] File Upload

Upload files (POD's) functionality required.

See: #Virtual Groups

[edit] Virtual Groups

Functionality to create "virtual groups" is needed. "Virtual group" is a subset of all records. Every CT that belongs to that group should satisfy given criteria.

Example 1. All CTs that satisfy:

MOT = Truck Domestic
Move From PICK UP LOCATION A
For: CARRIER B
For: SHIPMENTS TO DESTINATION C
For: ESTIMATED COLLECTION TODAY

Example 2. All CTs that satisfy:

MOT = Truck Domestic
To DELIVERY LOCATION A
For: CARRIER D
For: SHIPMENTS FROM ALL ORIGINS 
For: ESTIMATED DELIVERY TOMORROW

List of selection criteria.

  • Client Company
  • Choice of 3 Trucking MOTs
  • Flags - see #Flags
  • Shipper location
  • Consignee location
  • Trucker Name (carrier)
  • Pick up date (estimated or actual)
  • Delivery date (estimated or actual)
  • Not Billed Records


The purpose of grouping is to be able to perform certain action on a number of selected CTs. Actions that should be supported:

  • 1. generate REPORTS (either 1 time or schedule/automate)
  • 2. generate DOCUMENTS (single d/o or consolidation d/o and manifests)
  • 3. generate BILLING
  • 4. upload files (POD's)

There is no need to save this kind of group or assign a number to it. That is why we call it virtual.

[edit] Suggested Solution

[edit] Deadline

It is not clear now what can be completed by May 1.

Spec should be completed, approved and estimated (in man hours) first.

[edit] Summary

[edit] Flags Solution

See Gen_Tab_(component)#m1895

[edit] Virtual Groups Solution

Goto Virtual Groups for NATP

[edit] Reports Solution

[edit] Documents Solution

See Documents for Virtual Group

[edit] Billing Solution

See Billing for Virtual Group

[edit] File Upload solution

See File Upload for Virtual Group

[edit] Comment solution

See Comment for Virtual Group

[edit] Misc

[edit] Suggested Business Process and Use Cases

See Business Process and Use Cases for NATP.

[edit] April 21 Changes

see April 21 NATP Changes