POEM: SOWs

From UG

(Difference between revisions)
Jump to: navigation, search
(→Purchase Order Editor Mockups)
(→Change Requests)
Line 16: Line 16:
== Change Requests ==
== Change Requests ==
-
 
{| {{table}}
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''ID'''
| align="center" style="background:#f0f0f0;"|'''ID'''
Line 23: Line 22:
| align="center" style="background:#f0f0f0;"|'''Scope Description'''
| align="center" style="background:#f0f0f0;"|'''Scope Description'''
| align="center" style="background:#f0f0f0;"|'''Impacted Module'''
| align="center" style="background:#f0f0f0;"|'''Impacted Module'''
-
| align="center" style="background:#f0f0f0;"|'''Status'''
 
-
| align="center" style="background:#f0f0f0;"|'''Approved by'''
 
|-
|-
-
| 1||06/08/12||Simon||Move "pending" PO status from Closed tab to Open Tab in PO List||PO List||Closed||Marc/Simon
+
| 1||06/08/12||Simon||Move "pending" PO status from Closed tab to Open Tab in PO List||PO List
|-
|-
-
| 2||06/08/12||Simon||Move Open QTY Field, one spot to the right. So order should be (from left to right) - SKU, Item Description, Total QTY, Shipped QTY, Open QTY||PO Editor - Contents Tab||Closed||Simon
+
| 2||06/08/12||Simon||Move Open QTY Field, one spot to the right. So order should be (from left to right) - SKU, Item Description, Total QTY, Shipped QTY, Open QTY||PO Editor - Contents Tab
|-
|-
-
| 3||06/08/12||Simon||SKU Editor - do not allow users the ability to ADD NEW SKU as this will not be used by end-users. Create a new IMPORT capability for SKUs. ||SKU Editor||Closed||Marc/Simon
+
| 3||06/08/12||Simon||SKU Editor - do not allow users the ability to ADD NEW SKU as this will not be used by end-users. Create a new IMPORT capability for SKUs. ||SKU Editor
|-
|-
-
| 4||06/08/12||Simon/Marc||Download to Excel should basically be "dump" of the data in PO List grid. The users will filter the grid and when they click download to excel, it should just copy the data in the grid into an XLS file. ||Reporting||Closed||Marc/Simon
+
| 4||06/08/12||Simon/Marc||Download to Excel should basically be "dump" of the data in PO List grid. The users will filter the grid and when they click download to excel, it should just copy the data in the grid into an XLS file. ||Reporting
|-
|-
-
| 5||06/08/12||Simon/Marc||"Cargo Due" field should not be editable in PO Editor||PO Editor - All Tabs||Closed||Marc/Simon
+
| 5||06/08/12||Simon/Marc||"Cargo Due" field should not be editable in PO Editor||PO Editor - All Tabs
|-
|-
-
| 6||06/12/12||Simon/Marc||Remove "cancel" button from PO List screen. As this would essential serve no purpose since this is the first screen.||PO List||Closed||Marc/Simon
+
| 6||06/12/12||Simon/Marc||Remove "cancel" button from PO List screen. As this would essential serve no purpose since this is the first screen.||PO List
|-
|-
-
| 7||06/12/12||Marc||Remove "Regulatory ID" from PO as this is not a real ID. It is just a placeholder for various IDs||PO Editor & Objects||Closed||Marc
+
| 7||06/12/12||Marc||Remove "Regulatory ID" from PO as this is not a real ID. It is just a placeholder for various IDs||PO Editor & Objects
|-
|-
-
| 8||06/12/12||Marc||Added HAZ data delements into SKU Management||SKU Editor||Closed||Marc
+
| 8||06/12/12||Marc||Added HAZ data delements into SKU Management||SKU Editor
 +
|-
 +
| 9||06/14/12||Perry||For HAZ SKUs, the description for both Ocena & Air should be different||SKU Editor
|-
|-
|  
|  

Revision as of 15:25, 14 June 2012


Contents

Info

Parent Mantis: http://ct.jaguarfreight.com/mantis/view.php?id=3574

Project Stakeholders & Roles

  • Simon Kaye - CEO - Project Sponsor
  • Marc Selter - VP - Product Manager
  • Alex Dobrovolsky - Director of Technology - Solutions Architect
  • Denise Guastella - CT2 Support Manager
  • Kostiantyn Ushakov - CEO/CTO Elcosol
  • Perry Lee - CT2 Project Manager
  • <TBD> - Elizabeth Arden Engagement/Relationship Manager
  • <TBD> - Elizabeth Arden Technical Project Manager

Change Requests

ID Date Registered Change Requester Scope Description Impacted Module
106/08/12SimonMove "pending" PO status from Closed tab to Open Tab in PO ListPO List
206/08/12SimonMove Open QTY Field, one spot to the right. So order should be (from left to right) - SKU, Item Description, Total QTY, Shipped QTY, Open QTYPO Editor - Contents Tab
306/08/12SimonSKU Editor - do not allow users the ability to ADD NEW SKU as this will not be used by end-users. Create a new IMPORT capability for SKUs. SKU Editor
406/08/12Simon/MarcDownload to Excel should basically be "dump" of the data in PO List grid. The users will filter the grid and when they click download to excel, it should just copy the data in the grid into an XLS file. Reporting
506/08/12Simon/Marc"Cargo Due" field should not be editable in PO EditorPO Editor - All Tabs
606/12/12Simon/MarcRemove "cancel" button from PO List screen. As this would essential serve no purpose since this is the first screen.PO List
706/12/12MarcRemove "Regulatory ID" from PO as this is not a real ID. It is just a placeholder for various IDsPO Editor & Objects
806/12/12MarcAdded HAZ data delements into SKU ManagementSKU Editor
906/14/12PerryFor HAZ SKUs, the description for both Ocena & Air should be differentSKU Editor

SOWs

SOW 1

We will need to present a prototype of Purchase Order Event Management to Elizabeth Arden. A very simple prototype that addresses main use case(s) should suffice. Note that ERP integration and entitlement management will be out of scope for SOW1. Develop a prototype for a single shipper and single EA company. The goal of this prototype is just to demonstrate core functionality of this module. Even if we have to create a static prototype (ie.. document images, fake workflow) we'll go ahead & do it to deliver a proposal.

High Level Deliverables for SOW1

  • POEM Management Interface (view/edit/fulfill purchase orders)
  • SKU Management Interfaces (view/edit/import SKU/Items)
  • Document Center (Upload shipping documents, generate shipping/regulatory documents)
  • Auto-populate ASNs (Domestic & International)
  • Automated Notifications
  • Logging of all PO updates

Use Cases

Refer to GREEN use cases in POEM Specification: http://ct.jaguarfreight.com/wiki/POEM#Business_Requirements

Category Use Case
Review/Update Purchase OrdersReview/Update Purchase Orders
Update Purchase Order Dates
Send System Generated Notification(s)
Fulfill Purchase OrdersFulfill FULL Purchase Orders
Fulfill Partial Purchase Orders
Update Purchase Orders
Expire Purcahse Orders
Create ASNs
Send System Generated Notification(s)
Communication CenterSend System Generated Notification(s)
Shipping DocumentsGenerate Shipping Document(s)
Generate Shipping Labels
Generate Pro-Forma Regulatory Documents
Generate Packing Lists
Preview Documents
Save Documents
Print Documents
ReportingDownload to Excel
SKU ManagementAdd/update/archive SKUs
Update Packaging Data

Purchase Order List Mockups

Mantis 3612: http://ct.jaguarfreight.com/mantis/view.php?id=3612

Mantis 3613: http://ct.jaguarfreight.com/mantis/view.php?id=3613

Mantis 3616: http://ct.jaguarfreight.com/mantis/view.php?id=3616

Purchase Order Editor Mockups

Mantis 3614: http://ct.jaguarfreight.com/mantis/view.php?id=3614

ASN Submission (from POEM)

SKU Editor Mockups

Mantis 3615: http://ct.jaguarfreight.com/mantis/view.php?id=3615

File:POEM SKU Editor.jpg

File:POEM SKU Editor HAZ.jpg

Retrieved from "https://wiki.jaguarfreight.com/POEM:_SOWs"
Personal tools