RFPOI 2892

From UG

Revision as of 20:04, 19 April 2011

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 including all 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 belong to a group of users
• functionality should be able to apply individually user and group users

• 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
  • Example, shipper can create a shipment without specifying a mode (undefined)
• 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.
• Option to set access right for user to approve which mode of shipments

• 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

• Milestone visibility and/or accessibility should be set able from Admin

• Shipments should be able to segregate by mode such as Air, Ocean
• Milestones option:
  • New
  • Approved
  • Picked up
  • Departed
  • Arrived
  • Delivered
  • Archived
  • Hold
  • Rejected

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

Ops - Internal Application

• 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.
• List of shipments, fields, can be updated from dashboard
  • Every field[CT2] should be added to virtual group update

• Dashboard should be option to set for each group of operator users (admin- upper level)

• Each group of operators can have different view of dashboards depending on visibility and accessing setting per each group of users
  • Criteria:
    • Shipment that ships from, delivery to, office
    • Shipment that ships from and to region, country

• Dashboard should also provide some user setting for showing only one's list of shipments (setting - lower level allow operator to customize their own dashboard)

• Providing filter such as showing only specific mode: AIR and/or Ocean shipments that ship from X to Y
• Providing filter such as showing only specific client company or multiple client companies
• Providing filter to show only shipments that belong the particular office such as showing shipment that belong to NY office only
• Setting can be a combination of office and origin and destination shipment
• Setting for combination of filters

• Functionality to be available for each operator for the shipments that they have visibility/accessibility for

• Create master
• Add to master
• change the mode
• Comment
• Internal comment