1. Master Data Impact, Data Standards, and Management Process and Tools

2. Agenda  Introduction  What is Master Data?  How Does Master Data Impact the Business?  What is Good Master Data Design?  How Should Master Data be Managed?  How Does QAD Enable Data Management?  Master Data Cleansing Considerations  Question and Answer

3. Introduction  Andrew Hall  Joined Logan Consulting in 1995  QAD implementation experience since 1993

4. What is Master Data?  Referenced in many ERP modules  Customer, Supplier, Items  Drives functionality, process, and decision-making  Credit Terms, Item Status, Price Lists  Used to segment reporting  Customer Type, Item Type, Product Line, Chart of Accounts  Shared by different applications, sites, and areas

5. Impact on Business  Well Designed and Maintained Master Data results in:  Efficient processes that leverage ERP automation F MRP Planned Orders to Supplier Schedules  Mitigates and manages business risk F Customer Price Lists and Credit Limits / Terms  Improve reporting capabilities. One version of the Truth  Leverage human resources (e.g. Shared Services)  Faster implementations  Poorly Designed and Maintained Master Data results in the opposite

6. Tangible Examples  Inventory Optimization  Service and Target Customers  Maximize Spend Economics

7. Good Master Data Design  Develop an exhaustive list of Master Data  Don’t just think Customers, Suppliers, and Items  Include supporting data and IT system administration data  Design with the End in Mind  Global Statutory Reporting Requirements  Flexibility for Company Growth and Change  Data Entry Ease  Management Reporting Requirements  Structure and Functionality

8. Globally Standardized with Plug and Play Redundancy VOIP – Voice integrated - Network & ERP Single Global Security, Virus, Spyware and Spam controls Redundancy built into Global WAN to every Site with automated roll-over Site Specific Disaster Recovery Enabling Rapid Acquisition Integration Review/Upgrade Infrastructure Layer Fully Functional Multi-Lingual Website Air Gap Reverse Proxy Security Marketing/Sales/Knowledge/Training/Etc… Completely Validated Secure Access to Internal systems from any system anywhere in the world Presentation Relationship Layer Company Website Single Sign on for all Internal and External Customers and Users Global ERP Enabling Rapid Acquisition Integration Transformations built for Global Standards Enterprise Layer ERP Solution (QAD) Global eMail System, Internal and External Customer Messaging and Collaboration SharePoint Integrated Document Control & Storage Knowledge and Training Base/Center Data Warehouse for Global Reporting Requirements across all Functional Areas Enabling Rapid Acquisition Reporting CRM, Reporting/Collaboration Layer Messaging Email Instant Message WebEx/Collaboration Video Messaging SharePoint Global Knowledge/Training Base Global Dept Share Controlled Documents Globally Workflow Processing Globally Business Intelligence Global Standardized Data Warehouse Global Financial Budgeting & Consolidation Complete Global Functional Area KPI Reporting

9. Good Master Data Design  Design Globally with Local Flexibility  One standard for the entire organization  Deviate locally only as required but within the rules  Design with Cross-Functional Input  Formalized Design Meetings  One representative for each impacted functional area  Formally Document the Design  Require Business Approval of the Design Document  Design Document is THE OFFICIAL RULEBOOK

10. Managing Master Data  Clear cut process and procedure for maintenance of master data  Ownership of data is properly defined  In built workflow and authorization for adding and modifying data  Audit trails of master tables are activated and modifications are logged in the system  Must be accurate, complete, consistent, and timely

11. QAD Data Management Tools

12. Generalized Codes

13. Custom Screen Designer

14. Alerts and Workflow

15. Enhanced Controls

16. Audit Browses

17. Operational Metrics

18. Other  Align menu and field security with process and data ownership  Use Chart of Account Masks to enforce data combinations (or SE equivalent)

19. Data Cleansing Approach  Applies to New and Existing Implementations  De-Duplicate  Completeness  Adherence to Standards  Obsolescence  Is not easy and is not fun. Is necessary.

20. Conclusion  Master Data presents great opportunity for success…and failure  Design carefully and manage diligently  Master data management is not a one time affair  Use QAD’s embedded functionality to govern, manage, and audit your Master Data

21. Question and Answer