I-Portal REQUIREMENTS

From UG

Revision as of 13:59, 31 May 2012 by Montira (Talk | contribs)
Jump to: navigation, search


Contents

Mantis

Mantis 3547 http://ct.jaguarfreight.com/mantis/view.php?id=99
Code Branch To Be Determined
DEV Environment To Be Determined
QA Environment To Be Determined
SIT Environment To Be Determined


Introduction

The primary objective of International Portal (I-Portal) is to create a platform for CyberTrax2 to transform into Software-As-A-Service (SaaS) system that Jaguar Freight Services can offer as a fee-based service to external clients. Clients would be able to manage all aspects of their shipments from within CyberTrax2 for both domestic and international shipments. The portal should provide client users with the ability to create shipments, approve shipments, track shipments, etc.. This will streamline a business process of submitting and approving shipments and seamless communication at Elizabeth Arden. It is proposed to provide a web portal. Required software is a tool that allow a supplier to enter an Elizabeth Arden international traffic order.


The portal must be web accessible, secure, user-friendly, flexible, and scalable. The portal must also take into account data visibility rules (Clients will only be able to edit/view their own data) and system performance. This portal is mimic from ASN portal (Trucking domestic portal for Elizabeth Arden)


There are a number of features that should be postponed and released in phase two. This was done to launch international portal with core features with/without automated Purchase Order Event Management as soon as possible.


Functionality Overview

High Level Deliverable

  • Flexible Entitlements Management System
  • Flexible admin functionality for each user role
  • User Interface Templates
  • User visibility
  • External user Specific Reporting
  • Search/where is record(s) report
  • Download to Excel
  • Sorting ascending/descending
  • Internal user Specific Reporting
  • Dashboard/KPI
  • Download to Excel
  • Optimize current CT2 Client performance


Summary

  • Existing ASN portal should support two additional user roles for international shipments:
  • Shipper (a.k.a. Supplier)
  • Planner (a.k.a. EM)


Core Shipper User Functionality:

  • Manual creation
  • Create CT record
  • Edit CT record
  • Delete CT record
  • View CT record
  • Notifications
  • Appropriate visibility
  • Automated Purchase Order Event Management
  • See POEM
  • Edit CT record
  • Delete CT record
  • View CT record
  • Submit to create CT record
  • Notifications
  • Appropriate visibility
  • Flexibility admin for shipper's functionality


Core Planner User Functionality:

  • Single approval process
  • View CT record
  • set "approval status" on selected CT record
  • notifications
  • appropriate visibility
  • Double approval process
  • View CT record
  • set "approval status" on selected CT record
  • notifications
  • appropriate visibility
  • Auto approval
  • After record creation X hrs
  • Flexibility admin for planner's functionality


Client Functionality and Changes:

  • should not be affected


Core Jaguar User and Cybertrax Internal Functionality:

  • non jaguar user profile will have 3 roles defined
  • Client
  • Shipper (International portal and Domestic portal)
  • Planner (International portal and Domestic portal)
  • Jaguar User will see new additional fields
  • Jaguar User will see only shipments on Live tab when the CT has been approved by a planner or auto approved by system with rule set in admin
  • constraint on how many lines commodity table might have
  • some fields might become read only
  • additional report
  • dashboard report for approved shipments by modes with ability to create a group shipment
  • validation
  • etc


Project Stakeholders & Roles

  • Simon Kaye - CEO - Project Sponsor
  • Marc Selter - VP - Product Manager
  • Alex Dobrovolsky - Director of Technology - Solutions Architect
  • Montira Renfrew - CT2 Systems Analyst/ CT2 Project manager
  • Konstantin Ushakov - CT2 Software Developer (Elcosol)
  • Denise Guastella - CT2 Support Manager

Project Scope

<Identify in-scope and out-of-scope items>

Out-Of-Scope

  • SAS 70 & ISO27001 Compliance
  • Web Application Penetration Tests
  • High Availability (HA) Disaster Recovery environment(s)
  • 100% integration of both Internal CT2 & Client CT2
  • Functional & Non-Functional gaps in Internal CT2

Project Dependencies

  • POEM project
  • DR/KPI project

High-Level Timelines

<High-level milestone dates>

Risks

<Identify internal and external risks to the project: schedule, resources, technical, business, cost, market conditions, external vendors/partners, etc..>

Assumptions / Constraints

<Identify all assumptions and constraints for this project>

Business Requirements

Supplier/Shipper automatically generates CT record(s) by submitting P.O. to ASN portal. See diagram below.

Supplier/Shipper manually generates CT record(s) similar workflow as Truck-Dom portal. See diagram below.


Core International Shipper Functionality

Creating Shipper User and Shipper Profile

Admin - all CTs created by specific Shipper user must have:

  • MOT
  • Include mode [Y/N]
    • IF [Y]
      • THEN Default MOT is selected
      • OR THEN Allow shipper to assign MOT
    • IF [N]
    • THEN MOT is read only when it is available on the view shipment
      • MOT is not available for shipper to edit, only when planner or Jaguar operator assign the MOT
  • E0. Client Company
  • Relationship: one to many (one shipper: many E0. Client company)
    • Phase I: Start with one shipper: one E0. Client company
    • one portal: one shipper: one E0. Client company
  • Shipper
  • Relationship: single selected, one shipper company
  • Shipments Weight in [LB/KG]
  • Default value
    • LB only
    • KG only
    • KG and LB
  • Currency in [USD/EUR/GBP/HKD]
  • Default value
    • single select or multiple select option
  • POEM
  • IF [Y] THEN requested P.O. are automated available to submit to create a CT record
  • IF [N] THEN apply manual record creation

NOTE: These parameters must be defined in the Shipper Profile which is a part of the Client Profile:

1) located in "Edit user profile" window and specify role and additional specific info
2) link to UI mock-up see []


Shipper's role for current user role profile appoints through selecting shipper user role and identify shipper account on additional tab on the separate Shipper/Supplier Role Profile section:

  • functionality - when shipper roles is assigned for the user role then user is a Shipper.
  • Specific shipper profile must be defined:
  • MOT - enable/disable
  • E0. Client company - mandatory
  • Shipper - mandatory
  • POEM - enable/disable
  • Shipments Weight in [LB/KG] - mandatory
  • Currency in [USD/EUR/GBP/HKD] - mandatory


There are two additional labels below the checkbox.

  • First label contains the text: "The role allow user to add CTs".
  • Second label contains the text: "Create CT with" and means an ability for user as a Shipper to create CTs with Shipper's parameters - MOT, E0, Shipper.

Parameters of Shipper's role what was listed above are filled and stored in the three dropdown lists:

  • MOT:
label - "MOT:"
definition:
value - now is used only one MOT = Trucking-Domestic (in the future will be selected from dropdown list with set of MOT).
  • E0
label - "E0. Client Companies:"
definition:
value - must be selected one from the list of Client companies. This list reflects the set of records from "Admin > Client Companies".
  • Shipper
label - "Shipper (T1):"
definition:
value - must be selected one from the list of Shippers. This list reflects the set of records from "Admin > Address Book > Transportation" with T1="Yes".








Create CT record

  • [c] They can enter a number of lines of PO/SKU’s for only one E.M. at a time, including the piece price per PO/SKU.
  • [d] System will create one CT record per commodity line.
  • [e] Upon saving the information entered, an automatic validation notification will “pop up” asking the user to review the following information that they entered, noting the disclaimer. Read more here: CT preview and disclaimer screen
  • [g] Records created by a shipper company should display for ALL users who are a part of the same shipper company
CT preview and disclaimer screen

This screen is for the operator to "review" and "confirm" that the information they entered is correct.

This screen should contain the following information:

  • PO issued by value
  • Ship from value
  • Ship to value
  • PO value per commodity line
  • SKU value per commodity line
  • Quantity value commodity per line
  • Cargo Available Date
  • Disclaimer:
    • Failure to have the shipment available for pick up on the available date will result in chargeback’s.
CT confirmation screen

This is a confirmation to the supplier of the information they just entered and should contain the following information:

  • Number of CT records created
  • PO issued by value
  • Ship from value
  • Ship to value
  • List of the CT record numbers
  • Users Name
  • Date and time stamp
  • Should allow user to print for their records
Constraint on the number of lines in Commodity table in CTs created by Shipper User

Commodity table in CTs created by Shipper may have only ONE line.

Show only US and Canadian addresses

Show only US and Canadian addresses in:

  • Ship to Location
  • Pick up Location

Mark validation clearly

1) Add red star to required field 2) Add note to the screen "Both Loose Pkgs and Plts cant be zero at the same time on one line."

View list of CT records as a shipper

  • Shipper can view records that anyone in their company created.
  • Columns heading should have mouse over label (description).
  • Shipper should have ability to print the CT record that they view (print friendly)
  • View CTs table definitions:
  • Columns for New Tab:
    • CT Record
    • Created On
    • Pick Up Location
    • Delivery Location
    • PO
    • SKU
    • Qty
    • Piece Price
    • Total Value
  • Columns for Approved Tab:
    • CT Record
    • Approved On
    • Pick Up Location
    • Delivery Location
    • PO
    • SKU
    • Qty
    • Piece Price
    • Total Value
  • Columns for Hold Tab:
    • CT Record
    • Approved For
    • Pick Up Location
    • Delivery Location
    • PO
    • SKU
    • Qty
    • Piece Price
    • Total Value
  • Columns for Rejected Tab:
    • CT Record
    • Rejected On
    • Pick Up Location
    • Delivery Location
    • PO
    • SKU
    • Qty
    • Piece Price
    • Total Value
  • Columns for Delivered Tab:
    • CT Record
    • Created On
    • Pick Up Location
    • Delivery Location
    • PO
    • SKU
    • Qty
    • Piece Price
    • Total Value
  • Columns for Archived Tab:
    • CT Record
    • Created On
    • Pick Up Location
    • Delivery Location
    • PO
    • SKU
    • Qty
    • Piece Price
    • Total Value


  • Default order: Latest CT on top
  • Sortable?: Yes, ascending and descending,throughout all the shipments for all pages
  • Search feature: See #Search_feature_on_List_CTs
  • Action buttons per tab definitions:
    • Action Buttons for New Tab: Add, Copy or Clone, View, Edit, Delete
    • Action Buttons for Approved Tab: Copy or Clone, View
    • Action Buttons for Hold Tab: Copy or Clone, View
    • Action Buttons for Rejected Tab: Copy or Clone, View
    • Action Buttons for Archived Tab: Copy or Clone, View
    • Action Buttons for Delivered Tab: Copy or Clone, View

Edit CT record

What CTs Shipper may edit RULE

  • Shipper user may edit only records she created

When to lock CT record for edit by Shipper RULE

  • Shipper may edit an existing CT before it is approved or placed on hold or rejected by a planner.

Delete CT records

What CTs Shipper may delete RULE

  • Shipper user may delete only records she created

When to lock CT record for delete by Shipper RULE

  • Shipper may delete an existing CT before it is approved by a planner, placed on hold by a planner or rejected by a planner.

Field for text box/area that must be read only on Add/Clone shipments

  • Shipper
  • Pick up Location
  • Ship to Location
  • Created By
  • Total Value

Clone CT Record

Clone feature Exception

  • Cargo Available Date: This should be the current date, do not copy the clone date
  • E0.Client Company: This should be the same as it is set on Shipper user profile, do not copy the clone E0.Client Company
  • MOT: This should be the same as it is set on Shipper user profile, do not copy the clone MOT
  • NOTE#1: Make E0.Client Company and MOT fields for all the shipments that were created by shippers to be READ ONLY fields on the internal application. Not allow operator to change E0.client company and MOT from the individual CT, group CT, etc.
  • NOTE#2: For the group case that contained some shipments that created by shipper, should have some validation and show err message that E0. client company/MOT cannot be changed if operator tries to change the E0.client company and/or to MOT to different company or MOT that was set as shipper user profile.
  • Prevent user to clone CT with unapproved and archived addresses.

Business Requirement 2...

Business Requirement 3...

Business Process Flow 1...

Business Process Flow 2...

Business Process Flow 3...

Functional/Non-Functional Requirements

<Identify all functional and non-functional requirements. Maintain standard headings. If a specific requirement is not required, note as Not Applicable. Each functional requirement must trace back to a specific business requirement.>

CyberTrax2 Internal Application

<Identify all functional requirements for CT2 Internal Application>

User Interface Requirements

Reporting Requirements

User Access / Security Requirements

Logging Requirements

Group / Master Requirements

Filtering Requirements

Archiving Requirements

CyberTrax2 Client Application

<Identify all functional requirements for CT2 Client Application>

User Interface Requirements

Reporting Requirements

User Access / Security Requirements

Logging Requirements

Group / Master Requirements

Filtering Requirements

Archiving Requirements

Non-Functional Requirements

<Identify all non-functional requirements for both CT2 Client Application and CT2 Internal Application>

Performance Requirements

Capacity Requirements

Support / Maintenance Requirements

User Guides
Training
Log(s) Accessibility

Testing Requirements

Security Requirements

Technical Design & Solution

Mock ups

<Include mock-ups of UI changes, report changes, etc..>

Technology Stack & Architecture

<Include changes to existing Technology Stack & Architecture - new libraries, updated library versions, new software/hardware, new interfaces, etc..>

Technical Diagrams (Flow Chart, Sequence, UML, Systems Architecture, Technical Architecture, Data Architecture, etc..)

<Include architecture diagrams and flow charts>

Web / Application (New/Modified classes, methods, etc..)

<List new or modified classes and methods>

Database (DDL changes - new/modified tables, indexes, stored procedures, etc..)

<Summarize database changes>

Configuration (Config File changes)

<Summarize config changes>

Logging (Log File changes)

<Summarize Log File changes and locations>

External Interfaces (EDI Message(s), external vendors)

<Identify any new external interfaces. Include sample request and reply along with field definitions. Include Source/Target server(s)/webservice(s) and functional accounts. If this is a modification of an existing EDI message, include samples of current message(s) and new message(s)>

QUESTIONS

Admin Panel:

Q1. I-portal and ASN are separated?

  • Roles:Iportal: Shipper and planner
    • MOT: Air and Ocean only or specify MOT for each shipper one to one MOT?
    • Suggest for JG role to specify FCL, LCL, Console? with out letting shipper/planner assign
    • E0: Elizabeth Arden?
  • Roles:Truck-Dom: Shipper and Planner
    • MOT: Truck Dom only
    • E0: EA DOM PORTAL
  • Roles: combine shipper and planner?
    • All MOT: Air, Ocean, Truck Dom --> what about other trucks such as Truck air and Truck ocean
    • Should we even give International shipper to assign the breakdown of ocean from the beginning? FCL, LCL, Console?


Q2. If it does, how? what is the process? Will we change the current business process for EA DOM? If it does not, THEN?

Q3. Shipper Role:

  • one:one? for Shipper: EO.client Company?

Q4. Shipper Role:

  • one:one? one:many? For Shipper: MOT(s)?
  • Do they have ability to choose MOT?
  • MOT Air/Ocean --> available for shipper to assign? and keep the way it is for truck dom?
  • What is about Truck-air and truck-ocean? Could you describe the situation of when shipper wants to ship by truck air/ocean? When to consider? are they apart of i-portal? Should we not consider these yet only air and ocean first and we will think about that for future phase?

Q5. Who will assign MOT? Shipper? Planner? Jaguar? Do we have to give all the ability for all roles to assign/edit?

Q6.

Use case 1: Shipper assigns MOT by default from admin, or actual assign by shipper?

  • THEN Planner will approve the shipment...with date, etc including MOT?
  • THEN Planner (skip) --> automate approval

Use case 2: Shipper (NO MOT assign) view only once MOT is approved by Planner?

  • THEN Planner approves the shipment....etc including MOT assign
  • What would MOT be if automate approval for planner process. (Skip approval process)

Use case 3: Shipper and Planner (NO MOT assigned)

  • THEN Planner only approve the shipment...with date...etc without MOT assign.
  • THEN JAGUAR assigns the MOT
  • Work for AUTO approval as well


Q7. Any other fields? should allow shipper to edit? Label for all fields should be consistent for all MOTs? such as Pick up and Ship to location --> apply for all modes?

Q8. If we combine all modes, then drop down list of address should be all for all modes? or we have to narrow list of address for dom only when Truck dom is selected?

Q9. Currently create shipment Truck DOM - one line item = 1 CT (work well for TMS). for International--> what should it be (Will we use Descarte system for routing shipment same as TMS? and how as one CT can have many lines items? Should each line = each CT then Jaguar consolidates all the CT (line items) together to ship together by group/master?

Q10. Cont Tab for each mode for i-portal? not on one page--> separate shipment detail for each mode on Cont tab?

  • Any fields should be there for MOT selected? as Air and Ocean modes--> require fields can be different, should we make it common for both Air and Ocean?

Q11. Planner role: What is the process of this role for i-portal? what are the process of approvals? such as auto approval, etc?

Q12. Summary, What data feed from POEM and what process should change? such as the submission for QTY...detail of shipments....how to separate what is a part of POEM and I-portal? POEM Feed with submission ability for Shipper...if POEM not feed, shipper should create shipment from scratch like currently Truck Dom?

Q13. Shipment detail for edit or from data feed from POEM (must include in each mode for shipper and planner?)

  • FCL
  • Container#
  • Seal#
  • Size
  • Type
  • Est collection
  • Act collection
  • Request deliver
  • Act deliver
  • PO
  • SKU
  • QTY
  • Ttl# of Plts
  • Ttl PKG on plt
  • Loose PKGs
  • Ttl GW KG/LB
  • Piece price
  • total value
  • Stackable
  • Haz/non-haz
  • Ttl HU
  • CBM
  • VIEW EXP
  • streamshipline
  • booking#
  • Master BOL
  • HBOL
  • Origin terminal
  • Est/Act
  • Port of lading
  • Est/Act
  • Port of discharge
  • Est/Act
  • Destination Terminal
  • Any standard/common info for Cont tab for different modes if we allow shipper to assign MOT (air/ocean) as line by line can be different mode within one creation from shipper.
Retrieved from "https://wiki.jaguarfreight.com/I-Portal_REQUIREMENTS"
Personal tools