|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
Table of Contents STATEMENT OF WORK ACCEPTANCE 4 SUMMARY 5 OBJECTIVES 5 SCOPE 5 DELIVERABLES 6 IMPLEMENTATION PLAN 6 COMMUNICATION PLAN 7 DATA TRADING PARTNER MANAGEMENT 7 DATA FLOW DIAGRAM 7 PROJECT SCHEDULE/MILESTONES 7 RESOURCES 8 APL LOGISTICS 8 LLS 8 APPENDIX A 9 APPENDIX B 10 Statement of Work Acceptance By signing below, The Limited, Inc. Logistics Services and APL Logistics agree with the Scope of Work provided in the document entitled “LLS Custom 315 Outbound Data Feed Supplemental SOW”. I have reviewed the business assumptions and requirements and agreed with the proposed solution as described in this document will meet my requirements. Any requirements identified or changes/additions of fields to file specification provided after written approval of this document will be considered a future deliverable or outside the scope of this project. Approved Change Requests complete with an impact assessment and priority will be required to change the project scope. _______________________________ ___________________ Customer Representative Date The Limited Inc Logistics Services _______________________________ _____________________ Carlos Camara Date Director IT APL Logistics _______________________________ _____________________ Greg Finley Date Director GLS APL Logistics Summary The Limited Inc. Logistics Services (LLS) engaged APL Logistics (APLL) to deliver a comprehensive set of logistics services as well as technology solutions (see APLL’s The Limited SOW). This document is a supplement of the technology solutions SOW that will provide LLS with carrier event filtering from the events that are generated in the Custom Outbound 315 data feed outlined in APLL’s The Limited SOW. APLL understands that LLS has other technology needs that are being addressed outside of the supplemental SOW. They are listed in Appendix B. Objectives Objectives Rank Event Filtering 1 Scope Currently APLL is delivering a custom 315 EDI data feed to LLS. LLS has requested that certain events are to be filtered and only those filtered events will be passed to LLS through the custom 315 EDI data feed. For each event code all carriers will need to create a separate EDI 315 message and transmit those messages to APLL. APLL will validate the incoming EDI 315 message, and then enhance, translate and send LLS another EDI 315 message based on the LLS 315 Implementation Guide (IG).
Approximate Word count = 1430
Approximate Pages = 5.7
(250 words per page double spaced)
|
|
|
|
|
|