130 likes | 265 Views
Implementing Customer Schedules. MWUG Spring 2012 March 21 st Business Process Track 2:30 - 3:30pm. Introduction. AmSafe AmSafe is a manufacturer of restraint systems, primarily in the aviation, defense, and commercial products industries.
E N D
Implementing Customer Schedules MWUG Spring 2012 March 21st Business Process Track 2:30 - 3:30pm
Introduction AmSafe AmSafe is a manufacturer of restraint systems, primarily in the aviation, defense, and commercial products industries. AmSafe has manufacturing locations in the United States, the United Kingdom, and China, to name a few.
Introduction Phill Norrey Phill has been a consultant, specializing in MFG/PRO for over 20 years. He has implemented MFG/PRO for clients all over North America , Europe, and the far East. He joined AmSafe in January of 2011. Greg Sevison Greg has been directly involved with the development of ERP systems since 1984. In 2003, he began working with MFG/PRO, as an employee of Dura Automotive Systems. He joined Amsafe in the spring of 2008.
Introduction “What advantages are there to moving from Sales Orders to Customer Schedules?” “What are the challenges?” “How is Demand/Data Input into QAD?” “How does this affect Reporting?”
Session Agenda: Sales Orders <vs> Customer Schedules Data/Demand Input into QAD Reporting Considerations Summary & Review
I. Sales Orders <vs> Customer Schedules Sales Order Processing at Amsafe B. Why move to Customer Schedules? Customer Schedule Processing at AmSafe Realized Process Improvements
II. Data/Demand Input into QAD • A. Data From the Customer • B. Input into QAD • C. Realized Process Improvements
Data/Demand from the Customer Receive EDI Data from Radley (iCARaS) Automatic Process to Import Data into QAD Generate Spreadsheet/Report to Manage Weekly Data
Data/Demand from the Customer Realized Process Improvements: * Utilize Hosted-EDI Solution to Receive Data * Automate Process for Picking up Data from EDI System * Automate Process for Importing Data into QAD * Generation of Management Worksheet Time Requirements went from 14-16 Man Hours per Week … To approximately 10 minutes !
III. Reporting Considerations • A. How Schedules are Stored in QAD • B. Why is This a Problem? • C. Report Program Changes at AmSafe
How Schedules are Stored in QAD schd_det Release Management Schedule Detail sch_mstr Release Management Schedule Master sod_det Sales Order Detail so_mstr Sales Order Master scx_ref Scheduled Order Cross-Reference
IV. Summary & Review • A. Why Schedules Over Sales Orders? • B. EDI and Customer Schedules • Reporting Considerations • End Result at AmSafe
Contact Information: Phill Norreypnorrey@amsafe.com Greg Sevisongsevison@amsafe.com Thank You for your time and attention…