EDI to 4Pole REQUIREMENTS
From UG
Core Need
To automate sending invoices from Jaguar to 4Pole. At the moment we send a paper version at the end of the day. We want to send them electronically.
Requirements
With EDI established invoice should be transmitted the moment it is generated (without any extra review). If it needs to be batched then bundle could be sent once a day but not less frequently than that.
We should offer 4Pole various options for EDI.
Mantis
Project Overview
In order to comply with European Union Customs Security Program, 4Pole has requested that Notice Of Arrivals (NOA) be transmitted electronically between parties. Currently, JFS London & Paris would generate a Notice Of Arrival (NOA) in CyberTrax2 and send the PDF notice to 4Pole via email. 4Pole would then enter in the information manually into their system.
4Pole has requested that we automate this process. They employ a custom built system that currently supports electronic transfers of NOAs. Unfortunately, they do not have a set standard for this interface as each party has it's own nuances.
The objective of this project is to eliminate manual entry of NOAs by 4Pole and to comply with EU Customs Security Program requirements.
Project Stakeholders & Roles
Jaguar Freight Stakeholders
- Simon Kaye - CEO - Project Sponsor
- Marc Selter - VP - Product Manager
- Alex Dobrovolsky - Director of Technology - Solutions Architect
- Perry Lee - CT2 Support Manager
- Wassila Tahrichi - Account Manager
4Pole Stakeholders
- Ramiro Dias (ramiro.dias@4pole.com) - 4Pole Customs Director
- Guy [pronounced Gi] Gerthoffer (guy.gerthoffer@4pole.com) - 4Pole IT Director - Technical Point of Contact
- David Trouche (david.trochu@4pole.com) - 4Pole Operations & Traffic Manager
- Rejane Poitrimo (rejane.poitrimol@4pole.com) - 4Pole Customs Manager
Project Scope
The below items are in scope of this project:
- Electronic transfer of NOA data elements to 4Pole
- User Interface changes to allow JFS users to transmit NOA to 4Pole
- User Interface to display EDI log
- Provide ability to re-transmit NOAs
The below items are out-of-scope of this project:
- Implement business process changes
Project Dependencies
External Dependencies
- Success of this project is dependent on 4Pole's ability to develop a custom interface with CT2.
High-Level Timelines
- To be determined
Risks
<Identify internal and external risks to the project: schedule, resources, technical, business, cost, market conditions, external vendors/partners, etc..>
- 4Pole may require an interface that we currently do not support.
Assumptions / Constraints
<Identify all assumptions and constraints for this project>
Assumptions
- 4Pole will work in partner with JFS development team during the entire project lifecycle.
Business Requirements
1.0 Electronic transmission of NOAs to 4Pole
We will need to develop a custom interface to transmit NOA information electronically to 4Pole. This requires that we map out all required data fields and pass information via a predetermined file transmission protocol.
4Pole currently does not accept electronic NOAs. They have requested that we just come up with our own file format (all data included in existing NOA file) in a fixed-width, delimited file, EDI file, or Excel (except xlsx).
Sample NOA: Sample NOA
In addition to FTP (secure & insecure), 4Pole also supports electronic submission via email to inbound@4pole.com.
2.0 Configure Client Companies for NOA transmission
Not all client companies are in scope for electronic transmission of NOAs. We need to determine how to identify which clients are impacted and how to configure them such that only those clients will send NOAs. The business should have the ability to configure this option. Even though this interface is being developed for 4Pole, we need to be able to support this feature for other clients as well who may have different configuration settings (different file formats, FTP servers, etc..)
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)>
