New Arden Trucking Project NATP (main)

From UG

Contents 1 General Info 2 Business Needs and Requirements 2.1 Meetings 2.1.1 March 24 Meeting 2.1.2 March 29 Meeting 2.1.3 March 31 Meeting 2.1.4 April 5 Meeting 2.2 Deadline 2.3 Existing Business Process and Use Cases 2.4 Summary 2.5 Billing 2.6 Reports 2.7 Documents 2.8 Flags 2.9 New Fields 2.9.1 On Customer Hold 2.9.2 Pending Approval Mode 2.9.3 Consol Warehouse 2.9.4 Delivery Trucker 2.9.5 PT number 2.9.6 DT number 2.10 File Upload 2.11 Virtual Groups 3 Suggested Solution 3.1 Deadline 3.2 Summary 3.3 Flags Solution 3.4 Virtual Groups Solution 3.5 Reports Solution 3.6 Documents Solution 3.7 Billing Solution 3.8 File Upload solution 3.9 Misc 3.10 Suggested Business Process and Use Cases 3.11 April 21 Changes 3.11.1 Due dates 3.11.2 Demo Server Data 3.11.3 Create additional fields 3.11.3.1 Cargo available 3.11.3.2 Cargo due 3.11.4 Trucking Optimization Report 3.11.4.1 Hard coded conditions 3.11.4.2 Filters 3.11.4.3 Output 3.11.4.4 Schedule vs Generate

General Info

• parent mantis: 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 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 1884

March 31 Meeting

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

April 5 Meeting

• TMS features has been discussed - see 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

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

Sorry, there was a disconnect and testing on Demo server today revealed that we are missing very important Report that needs to be demonstrated to Client on Monday.

This report (#Trucking Optimization Report) is defined below along with required additional fields.

Please postpone all other work to produce this missing Report/components ASAP. See more below.

Due dates

• Ideally: April 23 NY mid day on Demo server
• Worst case: April 26 NY morning on Demo server

Demo Server Data

In order to have meaningful functionality test in NY on Demo server we need more or less latest data from staging (especially Addressbook).

Create additional fields

Cargo available

• widget: datebox
• location: Gen Tab
• default: empty
• meaning: on what date cargo is available for pick up (from Origin Door)

Cargo due

• widget: datebox
• location: Gen Tab
• default: empty
• meaning: by what date cargo should be delivered (to Destination Door)

Trucking Optimization Report

Hard coded conditions

None. (All CTs should be captured)

Filters

For April 23 NY mid day:

• Client Company // single select // match against CT#E0_Client OR CT#E1_Client OR CT#E2_Client OR CT#E3_Client
• CT#MOT // single select // only choice of Truck Domestic for May 1; add 2 more trucking modes after

• CT#Pick Up (Company - city - note) // single select
  • populate list with all unique Address_bo#Company_City_Remark fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation
• CT#Pick Up (city) // single select
  • populate list with all unique Address#City fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation
• CT#Pick Up (state) // single select
  • populate list with all unique Address#State fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation

Developer's Note:
-----------------
To simplify you can instead show a list of all US states

• CT#Pick Up (ZIP) // single select
  • populate list with all unique Address#Zip fields existing currently in DB where Address#Category equals to Address#ExportPickUpLocation

• CT#Delivery To (Company - city - note) // single select
  • populate list with all unique Address_bo#Company_City_Remark fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation
• CT#Delivery To (city) // single select
  • populate list with all unique Address#City fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation
• CT#Delivery To (state) // single select
  • populate list with all unique Address#State fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation

Developer's Note:
-----------------
To simplify you can instead show a list of all US states

• CT#Delivery To (ZIP) // single select
  • populate list with all unique Address#Zip fields existing currently in DB where Address#Category equals to Address#ExportDeliveryLocation

Output

• media: xls only

• Sort by: Cargo due, earliest on the top

• Tabs: each tab per State (from Pick Up Location)

• Fields (left to right)
  • label on xls // mapping explained
  • CT# //
  • Pick Up Location //
  • P City // Pick Up Location City
  • P State // Pick Up Location State
  • Delivery Location //
  • D City // Delivery Location City
  • D State // Delivery Location State
  • HU // Grand ttl for CT
  • Weight, lb // Grand ttl for CT
  • CBM // Grand ttl for CT
  • Cargo available //
  • Cargo due //

Schedule vs Generate

• Generate option (need by April 23 NY mid day on demo)
• Schedule option (need for release)