International Portal REQUIREMENTS

From UG

Contents 1 Info 2 Glossary 2.1 High Level requirement 3 Requirements Summary 3.1 Core need 3.2 Core functionality 4 Requirements Details 4.1 International Shipper functionality 4.2 International Planner functionality 4.3 Agent functionality 4.4 Trucker functionality 4.5 Jaguar operator functionality 4.6 Other roles functionality 4.7 Common functionality 5 Q and A 6 Implementation 6.1 Pre Implementation Architect Notes 6.2 Implementation Notes 6.3 Post Implementation Architect Notes

Info

• Related mantis#:
  • 0002629: [Intl Portal] ... <proj>
  • 0002892: [Intl Portal] Implement phase 1

Glossary

High Level requirement

• 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 the information to JFS for data entry by JFS staff.

Requirements Summary

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 types of users, so each type of user can be specific in terms of configuration. In order to suit the specific needs of users, we should provide a system that can be easily configured 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

Core need

Add additional user roles to CT2: International Shipper, Agent, Trucker, etc. Make as flexible as possible.

Core functionality

• Add International Shipper role with related functionality

• option to choose ability to create/edit/delete/view/clone shipments
• option to select available fields from Admin (subset of fields)
  • Which fields are available for shipper to create/edit or view...etc
• option to create a shipper or a group of shippers
• Ability to create a report for the shipment that shipper has visibility to
• See detail: #International Shipper functionality

• Add International Planner role with related functionality

• option to validate/edit/view shipments
• options for approval
  • Auto approval
  • Manual approval
  • EDI automated validation to approve (future requirement)
  • EDI to validate to upload (import data)
• option to create a planner or a group of planners
• options for fields to update/view shipments
• options for each method of validation of shipments
• Ability to create a report for the shipment that planner has visibility to
• See detail: #International Planner functionality

• Add Agent role with related functionality

• option to choose ability to create/edit/delete/view/clone shipments
• option to create CTs, list CTs and list Master that belongs to that particular agent
• option to select available fields from Admin (subset of fields)
  • Which fields are available for agent to create/edit or view...etc
• option to create an agent or a group of agents
• ability to create reports for only specific shipments that agent has visibility to
• See detail: #Agent functionality

• Add Trucker role with related functionality

• option to edit/update/view shipments
• option to select available fields from Admin (subset of fields)
  • Which fields for a shipment that Trucker can see and/or edit
• See detail: #Trucker functionality

• Add Jaguar User role for extra functionality

• Option to set for view/access shipments right based on filters:
  • Office
  • Geographic
  • PO#
  • PO Issued by
  • Pick up Location
  • Ship to Location
  • Etc
• See detail: #Jaguar operator functionality

• Ability to add other roles with related functionality through Admin (possible? feasible?)

• See detail: #Other roles functionality

• Add some new common functionality (any role)
  • All CT2 fields should be available to manage on Admin for each role
  • Right access to fields per role (edit/delete/view etc)

• See detail: #Common functionality

Requirements Details

International Shipper functionality

• Each shipper can have different ability and right access to each shipment and list of shipment
• Each shipper can create one or many modes of transportation even undefined mode
• Each functionality can be set for each shipper's accessibility to use

• For example shipper A can only view shipments for particular shipper's company and belong to particular client company or companies but shipper B can create/edit/delete/view/clone shipments for particular shipper's company and belong to particular client company or companies

• Group of shippers can be created and each shipper can belong to a group of shippers that has the same functionality and the same right for accessibility and visibility

• For example, shipper A has ability to edit field1 but shipper B doesn't have ability to edit field1 but field1 can be available to view
• For example, shipper can create a shipment and has ability to select a mode of transportation (Undefined, Air, Ocean) that are available for the option or select undefined mode

• Each field can be set to be available for particular shippers
• option to create a shipper or a shipper group
  • customized functionality, MOT, fields, etc can be set as a group of shipper. A shipper that links to the group will have the same ability and visibility as other in the same group.

International Planner functionality

• Each planner can have different ability for approval of shipments

• options for approval
  • Auto approval
  • Manual approval
    • Single step approval process
    • Double approval process (similar to EA Stamford feature)
      • Provide a location/tab/color code status/filters/possible location to show all shipments that requires an additional finalized approval or validation process.
  • EDI automated validation to approve (future requirement)
    • This can be done by comparing ASN data against client's ERP data
      • For example, data can be PO#, Item code, quatity, date, etc (detail requirement will be defined in the future)
      • If it is match, then "approve/proceed"
      • If it is mismatch, then "review process to be determined"
  • EDI to validate to upload (import data; similar to SKU to planner mapping upload)
    • 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 receives and uploads

• Each planner can have different accessibility of shipment to approve for each mode of transportation

• For example, plannerA can approve ocean shipment only, plannerB can approve ocean shipment for single step process and air shipments for double approval process as a basic planner, plannerC can approve all the modes of transportation that he has some accessibility to as a final approval planner, and plannerD can only view shipments only.

• Each field can be set to be available for planner to validate/edit/view
• option to create a planner or a planner group
  • customized functionality, MOT, fields, etc can be set as a group of planner. A planner that links to the group will have the same ability and visibility as other in the same group.

Agent functionality

• Each agent can have different setting for functionality, visibility, and right accessibility

• This should be limited to creating a shipment record only for the shippers that would normally handle shipments for example Asia, Europe, Australia, South America, etc.
• Purpose: having agents using CT is to tie up the business relationship, relieve our respective regional office of some data entries, offer them visibility and have the possibility to capture new local business

• Each agent that is local for particular city, country will create a CT record - key in the booking information as well as the packing information and the shipping information
• Each functionality and fields can be set whether it can be available for agent

• option to choose ability to create/edit/delete/view/clone shipments
• option to create CTs, list CTs and list Masters that belong to that particular agent
  • Create CT - Agent ID must be attached to each CT created
  • List CTs, List masters - only those shipments that assigned to the particular agent
• option to select available fields from Admin (subset of fields)
  • Which fields are available for agent to create/edit or view...etc
• option to create some documents
  • Which doc that agent can create. For example Jaguar Bill of Lading and HAWB must be issued by the respective JFS regional office with some exception (we can allow some countries such as Indonesia but not China for legal issue for their bill of lading. This will remain under a strict control of JFS regional office). The other documents (DO, Pick Up order, Arrival Notice) will be generated by the Agent on JFS behalf with their own letter head. It should be flexible interm of who can create which document.

• option to create an agent or a group of agents
• ability to create reports and using Where Is report for only specific shipments that agent has visibility to
• option to choose ability to view/upload uploaded docs

Trucker functionality

• Each trucker can have different setting for functionality, visibility and right accessibility for fields and shipments

• Some trucker can only view the shipments that he has visibility to, but some trucker can update a field(s) such as Delivery by date field of shipment

• Each trucker can see shipments that associate with the shipments that belong to that trucker company
• option to create a trucker or a group of truckers
• ability to create reports for only specific shipments that that particular trucker has visibility to

Jaguar operator functionality

Other roles functionality

Common functionality

• Query
• notification

Q and A

Implementation

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.