Rates DB (MAIN WIKI)
From UG
(→Maintaining cost rates) |
(→Maintaining cost rates) |
||
Line 42: | Line 42: | ||
The system will also need to capture accessorial charges, which will also be defined per MOT. | The system will also need to capture accessorial charges, which will also be defined per MOT. | ||
- | + | ===Uses=== | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
**Searched by Jaguar employees to | **Searched by Jaguar employees to | ||
- | *** | + | ***Compare costs for different vendors |
- | *** | + | ***Quote costs based on the costs saved in the system |
- | *Searching Carriers | + | *Searching Vendors or Carriers |
**Searched by Jaguar employees to compare carriers | **Searched by Jaguar employees to compare carriers | ||
- | |||
*Estimation of CT costs | *Estimation of CT costs | ||
*Estimate sales invoice with possible auto generation. | *Estimate sales invoice with possible auto generation. | ||
+ | |||
+ | ==Maintaining Customer specific sell rates== | ||
+ | TDB | ||
+ | |||
+ | ==Generating Sales Quotes== | ||
+ | TBD | ||
+ | **Searched by Customers for general rates | ||
+ | **Searched by Customers for customer specific rates | ||
+ | **Searched by Jaguar employees to generate for Customers and enable overseas office to access rates. | ||
+ | ==Searching Costs | ||
Revision as of 13:43, 19 April 2011
Contents |
Info
0002690: [Rates DB] ..... <project>
Business Analysis and Requirements
To be written by BA. This section should cover Needs, Requirements, Background and Design Ideas. Also could include Glossary, existing business workflow, cases, etc
"Rates DB" is a code name for tariff and contract management system with additional functionality that will affect multiple modules of CT2.
Business Information
Currently there seems to be no standard in obtaining or maintaining rates. When a rate is required, operators will obtain the rates either by, searching online tariffs, searching rate management systems (Rate Explorer), sending an email request, telephone calls, searching previous emails, searching documents saved on their desktop or manually looking through paper copies of contracts or tariffs. This is currently being done by various employees with little sharing of the information.
Creating a database should allow operators throughout the organization (including overseas offices) to share and compare this information.
The system should be able to provide quick user friendly access to all current costs.
It is required to create a data base that would maintain rates for each MOT. Each MOT will be handled individually.
- Ocean FCL
- Ocean LCL
- Air
- Trucking
- Customs to also be handled separately.
The database would be used for various reasons
Maintaining cost rates
We need a system capable of adding, editing, deleting, listing, searching, sorting, querying various rates.
Each MOT will have its own rates structures and formulas necessary to maintain these rates and will be defined in those separate articles.
It is possible that each rate may have multiple variables.(minimums, maximums, weight breaks, etc...)
Rates will be linked to a specific vendor and description.
The system will also need to capture accessorial charges, which will also be defined per MOT.
Uses
- Searched by Jaguar employees to
- Compare costs for different vendors
- Quote costs based on the costs saved in the system
- Searched by Jaguar employees to
- Searching Vendors or Carriers
- Searched by Jaguar employees to compare carriers
- Estimation of CT costs
- Estimate sales invoice with possible auto generation.
Maintaining Customer specific sell rates
TDB
Generating Sales Quotes
TBD
- Searched by Customers for general rates
- Searched by Customers for customer specific rates
- Searched by Jaguar employees to generate for Customers and enable overseas office to access rates.
==Searching Costs
Main Features:
- management of tariffs and contracts (client and vendor sides)
- "Quotations" web portal for sales
- Automated population of charge table in "sales invoices"
- Automated calculation of "estimated cost and sale" for a shipment
- Etc
Pre Implementation Architect Notes
Written by Architect after previous section is completed.
Implementation Notes
To be written by Developer or BA by the time UAT is completed. Briefly defines what was implemented and how.
Post Implementation Architect Notes
Written by Architect after previous section is completed.