New Arden Trucking Project NATP (main)
From UG
(Created page with 'Category:New Arden Trucking Project') |
(→Suggested Solution: added Comment solution) |
||
(78 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
[[Category:New Arden Trucking Project]] | [[Category:New Arden Trucking Project]] | ||
+ | |||
+ | == General Info == | ||
+ | |||
+ | * parent mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=1884 1884] | ||
+ | * requested for Release: April 29 (staging) | ||
+ | |||
+ | == Business Needs and Requirements == | ||
+ | |||
+ | === Meetings === | ||
+ | |||
+ | ==== 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 === | ||
+ | |||
+ | 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 === | ||
+ | |||
+ | Below is a full list of functionality requested: | ||
+ | |||
+ | * [[#Billing]] | ||
+ | * [[#Reports]] | ||
+ | * [[#Documents]] | ||
+ | * [[#Virtual Groups]] | ||
+ | * [[#Flags]] | ||
+ | * [[#File Upload]] | ||
+ | |||
+ | === 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]]. | ||
+ | |||
+ | === 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]]. | ||
+ | |||
+ | === Documents === | ||
+ | |||
+ | * Truck Detailed Manifest. | ||
+ | * D/O. | ||
+ | |||
+ | See also: [[#Virtual Groups]]. | ||
+ | |||
+ | === Flags === | ||
+ | See [[#New fields]] | ||
+ | |||
+ | === New Fields === | ||
+ | |||
+ | ==== On Customer Hold ==== | ||
+ | |||
+ | See [[CT#On_Customer_Hold]] | ||
+ | |||
+ | ==== 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]] | ||
+ | |||
+ | |||
+ | See also: [[#Virtual Groups]]. | ||
+ | |||
+ | === File Upload === | ||
+ | |||
+ | Upload files (POD's) functionality required. | ||
+ | |||
+ | See: [[#Virtual Groups]] | ||
+ | |||
+ | === 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''. | ||
+ | |||
+ | == Suggested Solution == | ||
+ | |||
+ | === Deadline === | ||
+ | |||
+ | It is not clear now what can be completed by May 1. | ||
+ | |||
+ | Spec should be completed, approved and estimated (in man hours) first. | ||
+ | |||
+ | === Summary === | ||
+ | |||
+ | === Flags Solution === | ||
+ | |||
+ | See [[Gen_Tab_(component)#m1895]] | ||
+ | |||
+ | === Virtual Groups Solution === | ||
+ | |||
+ | Goto [[Virtual Groups for NATP]] | ||
+ | |||
+ | === Reports Solution === | ||
+ | |||
+ | * [[In Transit Report]] (change) | ||
+ | |||
+ | * [[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 === | ||
+ | |||
+ | See [[Documents for Virtual Group]] | ||
+ | |||
+ | === Billing Solution === | ||
+ | |||
+ | See [[Billing for Virtual Group]] | ||
+ | |||
+ | === File Upload solution === | ||
+ | |||
+ | 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
- TMS features has been discussed - see 0001920: (*NATP) TMS features
[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
[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
[edit] Virtual Groups Solution
[edit] Reports Solution
- In Transit Report (change)
- 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)
[edit] Documents Solution
See Documents for Virtual Group
[edit] Billing Solution
[edit] File Upload solution
See File Upload for Virtual Group
[edit] Comment solution
[edit] Misc
[edit] Suggested Business Process and Use Cases
See Business Process and Use Cases for NATP.