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 Other roles functionality 4.6 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 a request 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 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

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
    • For example, shipperA has ability to create/edit/delete/view/clone shipments, but shipperB has ability to view shipments only
  • option to select available fields from Admin (subset of fields)
    • Which fields are available for shipper to create/edit or view...etc
    • For example, shipper can create a shipment with undefined mode or selected mode of transportation2
  • option of create a shipper or a shipper group

• Add International Planner role with related functionality
  • option to validate/edit/view ASN data
    • options for modes to approve
    • options to update/view shipments
    • Ability for

• Add Agent role with related functionality
  • create/edit/delete/view shipments
  • per field Admin (subset of fields)
  •  ???

• • Add Trucker role with related functionality
  • create/edit/delete/view shipments
  • per field Admin (subset of fields)

• Add Jaguar User role for extra functionality
  • Option to view shipments based on filters:
    • Office
    • Geographic
    • PO#
    • PO Issued by
    • Pick up Location
    • Ship to Location
    • Etc

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

• Add some new common functionality (any role)

Requirements Details

International Shipper functionality

....

International Planner functionality

...

Agent functionality

Trucker functionality

Other roles functionality

Common functionality

• Query
• ...

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.