Rates DB (MAIN WIKI)

From UG

Revision as of 19:39, 14 April 2011

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, A rate management systems (Rate Explorer), sending an email request, telephone calls, searching tariffs, 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 operations people, Inside sales people,

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

The database would be used for various reasons

• Generating Sales Quotes
  • 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
  • Searched by Jaguar employees to
    • Quote costs
    • Compare costs
• Searching Carriers
  • Searched by Jaguar employees to compare carriers
  • History searched by Jaguar employees to better negotiate future rates
• Estimation of CT costs
• Estimate sales invoice with possible auto generation.

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.