RFPOI 2892

From UG

Brief overview & high level context of business requirements

• The International web portal development should take into consideration the growing need for "Third party" access to CT2
• Third Party access refers to customers, shippers, suppliers, agents, truckers etc. to whom partial access of CT2 data (creating records, adding/updating specific fields) is granted.
• Each third party user type is then given some specific functionality (example of possible functionalities are listed in this article for International portal users).

• For an example of a third party user type would be customer who could create a record to book a shipment...rather than sending a request information to JFS for data entry by JFS staff.

Business Requirement

JFS would like to have an International Web portal that can be easily configurable and flexible to suit all the third party users (client companies). There are many different type of users, so each of users can be specific in term of configuration. In order to suit the specific needs of users, we should provide a system that can be easily configuring through admin module to manage each type of users such as functionality, visibility, ability, etc.

Users should be able to manage their own UI setting for their view

International Portal Scopes

• Provide options to configure user types in admin module.

• Option should be flexible for all types of clients and third party users.
  • Client, shipper, planner, agent, trucker, etc
• Each user type can be grouped for ...................

• Mode should be options to configure for each user through admin

• Mode should be option for user to create, update, and/or approve shipments
• Undefined, Air, and Ocean
• Option to select detail modes: Ocean FCL and Ocean LCL
  • Example, some planner would like to approve a shipment mode to Ocean FCL or LCL if shipper created an ocean shipment.

• All fields on CT2 should be available option on admin for configuration for each user.

• CT2 fields can be managed through admin module to be visible for user to read only or read and write for each group of users.
• CT2 mandatory fields can be set in admin
  • If a field is set as a mandatory field, it should show asterisk symbol (*) on the label, so that can be easily help user to know which field is mandatory
  • Err pop-up window should show if at least one of the mandatory fields is empty.
    • Each field should be flexible to be mandatory/optioanl for some specific group of users.

• Should be able to accommodate several options for approval of shipments and validation of ASN information provided by the shipper.

• Auto approval
• Manual approval
  • Single step approval process
  • Double approval process
• EDI automated validation to approve (future requirement)
  • This can be done by comparing ASN data against client's ERP data
    • Data can be PO#, Item code, quatity, date, etc (future requirement)
    • If it is match, then "approve/proceed"
    • If it is mismatch, then "review process to be determined"
• EDI to validate to upload (import data)
  • JFS can receive daily reports (.xls, csv, .html etc) and upload to the system for approval status to validate ASN data
  • System should be able to validate and update the system from what JFS receive and upload

• International shipments that entered through portal should be available on the OPS dashboard on internal application

• Dashboard to show list of approved shipments to segregate for air and ocean modes
  • Air Statistic dashboard
  • Ocean statistic dashboard
• Dashboard should be configured in admin for each group of operators (internal users)
• Criteria of numbers to show on the dashboard
  • Approved, Routed for pickup, book for Air, departed, arrived, and delivered.
  • Approved, Routed for pickup, book for Ocean, departed, arrived, and delivered.

• Email notification for all milestone should be able to managed in admin