1 / 54

Midwest User Group Meeting

Midwest User Group Meeting. Lance LaCross, CPA Senior Solutions Consultant September 27, 2011. Upgrade from SE to EE . Agenda. Benefits of QAD Enterprise Applications SE vs. EE Process Considerations Questions & Answers. Business Requirements Today.

ismael
Télécharger la présentation

Midwest User Group Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Midwest User Group Meeting Lance LaCross, CPA Senior Solutions Consultant September 27, 2011 Upgrade from SE to EE

  2. Agenda • Benefits of QAD Enterprise Applications • SE vs. EE • Process Considerations • Questions & Answers

  3. Business Requirements Today • Companies Need A Way To Make Sense Of All The Data Being Collected Within Their Organization – Need Increased Visibility. • Need To Be Able To Answer Strategic Business Questions. • They Are Now Being Held Accountable And Therefore Need To Control And Comply. • Companies Are Growing Worldwide And They Need A System That Will Allow Them To Benefit From Their Global Operations. • They Want A System That Is Easy To Use.

  4. Why Upgrade Business Reasons to Move to The Latest Technology • Efficiency - Complete access to financial data along with role-based processes • Globalization - An integrated financial solution across the entire enterprise including multi-company, multi-currency, multi-GAAP, and multi-country organizations • Compliance - Controls for data and processes – role-based security, segregation of duties • Leverage Technology – powerful integration tools and user-definability • Ease of Use & Standardization - An easy to use, scalable solution

  5. Why Upgrade?

  6. Periodic Application Refresh Proactive Application Management Competitive Opportunity Regular Applications Value Reviews Practical Competitive Optimum Status Quo Go Live Competitiveness Competitive Erosion Time By harnessing the power of new technology, you can achieve competitive advantage

  7. Can customizations be reduced ? Can upgrade provide new business value? Productivity Cost Upgrade Cost Drivers Business justification examines the overall impact to your organization’s performance

  8. Benefits of Upgrading • Take advantage of new functionality • Reduce customizations • Reduce operational costs • Respond to globalization and consolidation needs • Increase user productivity • Ensure compliance • Optimize application and system performance • Drive lean principles throughout the organization

  9. Value of Upgrading According to Aberdeen Group, Best-in-Class manufacturing companies are 35% more likely than Laggard companies to operate on a current version of ERP.

  10. The Goal Upgrade to achieve or maintain position

  11. QAD Enterprise Edition

  12. global platform Munich domains Shared Services Sarbanes-Oxley Compliance Enterprise Integration Flexible global Deployment Common Data Global Governance Interoperability & Integration Washington Tokyo Rio de Janeiro Sydney

  13. New Features • COA Mask • Now on shared set level • Allows for a global chart of accounts with control on local (domain) combinations • Self Billing • Tax Registers • Tax register create • Italian tax registers

  14. New Features • Statutory Currency • Shared Set Merge • Daybooks / AP/AR Daybook Sets • Regional Balance Sheet / Income Statement • SSM (Service & Support) • Accrued / Deferred Revenue Reports • Operational Metrics • Pick lists for Depot orders

  15. New Features • International Legal Documents • Supports documents for shipping / receiving documents • Control file setting to keep invoiced sales orders • Reporting Framework • Create reports directly from browses • Use EE financial browses

  16. More Detail • QAD Functionality Comparison from SE to EE.xlsx

  17. Upgrade Considerations

  18. QAD 2011 EE Upgrade Considerations • Financial / Regulatory • Business • Implementation • Technical • Security • Customization • Reporting • Tools • Education / Training • Upgrade Plan

  19. Financial / Regulatory Considerations 19

  20. Financial / Regulatory Considerations • Internationalization – localizations are removed • International regulatory functionality incorporated in base product • Can impact all users • Time phased consolidation of international requirements

  21. Business Considerations 21

  22. Business Considerations • Understand your objectives in upgrading • Reporting requirements • Business analysis requirements • Is there a clear definition and understanding regarding shared services requirements ? • Measure baseline metrics before upgrade • Degree of change management or managing change that will be required 22

  23. Business Considerations • The amount of business process reengineering that is envisioned to support initiatives such as Lean, Shared services, etc. • Customer Service Applications • Support Operations • Accounts Receivable • Accounts Payable

  24. Business Considerations • General Ledger • Expanded Account Structure • New Reporting Structure • Format Positions Removed • Additional Setup • Business Relations • Shared Services • Accounts Payable • Accounts Receivables

  25. Business Considerations • Is there an understanding of what new functionality is available or net change from legacy version? • Will there be new features and functionality the business will be taking advantage? • Enhanced security • CRM • Lean manufacturing • PIM • Production schedulers • EAM • CSS • Configurator • Warehousing

  26. Implementation Approaches 26

  27. Implementation Considerations • Is this project considered a new implementation, technical upgrade or is it a reimplementation • Will a business process assessment (BPA) be required • Will business process reengineering (BPR) be required • Is this project a “lily pad” for another upgrade – If so, how can it be positioned for the next upgrade

  28. Upgrade Scenarios Technical Migration with data conversion Customization Data Conversion Small Process Changes Optimization Technical Migration without data conversion Optimization Conversion Data Load Small Process Changes Re-Implementation Re-define Business Processes Non-Intrusive Customizations Data Load 28

  29. Centralize/Standardize First QAD 2007QAD 2008/ 2009 Standard Edition QAD MFG/PRO 8.6, 9.0, eB, eB2 QAD 2011Enterprise Edition ERP Database Plant 1 ERP Database Plant 1 ERP Database Plant 1, 2 and 3 ERP Database Plant 1, 2 and 3 ERP Database Plant 2 ERP Database Plant 2 ERP Database Plant 3 ERP Database Plant 3 29

  30. Migrate first to QAD 2011 Enterprise Edition, than Centralize and Standardize QAD MFG/PRO 8.6, 9.0, eB, eB2 QAD 2011 Enterprise Edition ERP Database Plant 1 ERP Database Plant 1 ERP Database Plant 1, 2 and 3 ERP Database Plant 2 ERP Database Plant 2 ERP Database Plant 3 ERP Database Plant 3 30

  31. Technical Considerations 31

  32. Technical Considerations • Architectural • Number of databases • Number of domains • Options • Single database with multiple domains • Multiple databases with multiple domains • Single database with single domain

  33. Technical Considerations • Database and domains considerations • Strategy for points of failure (single or multiple) • Database maintenance or shutdowns strategy • Language considerations in the same database • How many sites are you willing to upgrade at once • Time zone considerations

  34. Security Considerations

  35. Role Based Security • All application security in QAD 2011 EE is role based • Roles are defined for each discrete area of the business using Segregation of Duties concepts • Roles are linked to menu functions using Role Permissions • Users are assigned access to Domains and Entities • Segregation of Duties • Users are assigned to roles for Entities and Domains • Tools provided for the automatic loading and editing of default roles and permissions • XML integration already available

  36. Security Considerations

  37. Customization Considerations

  38. Customization Considerations • The number and types of customizations to the legacy system • Is there a definitive list of customizations • Is there an understanding of who owns each customization • Is there an understanding of what each customization does • Plan to replace customizations with standard functionality • Remember - every customization in a multi domain database will need to have the domain key added • API’s and interfaces to 3rd party software • Needs to be fully identified and go forward strategy developed • Is it within scope to update 3rd party software solutions • QXtend – Integration Framework

  39. Reporting Considerations 39

  40. Reporting Considerations Requirement Solution • Ad Hoc Reporting • Inquiries • Typically A One-time Request For Data • Standard Reporting • Typically Run Weekly, Monthly, Etc. • Fairly Static In Layout, Query Parameters, Etc. • Can Be Run In Batches And On A Schedule • Forms And Labels • Invoices, Orders, Etc. • Package Labels, Barcodes • BI Reporting • Data Warehousing • Metrics/Models • OLAP Reporting • NET Browses • .NET Reporting • QAD BI 40

  41. Workbenches, Browses, Collection • Pre-set with user ability to change and create new browses

  42. Reporting • Create New, start with Browse, or modify Existing QAD reports • Add images, graphs and other controls • Additional Features: Windows Task Manager Schedules • Output documents, Excel, PDF • Release with EE includes samples • Existing reports converted over time 42

  43. Business Intelligence QAD Business Intelligence “Value -- for customers, shareholders and employees -- is either created, compromised or destroyed every time a decision is made inside an organization.”

  44. Tools Considerations 44

  45. Tools • Standard Conversion Tool • Domain Merge Tool • Custom Code Conversion Tool • Program Tracer Tool • Non-intrusive Customization Framework 45

  46. Standard Conversion Tool • Background • Finance module tables re-built • Conversion guide • Document of the conversion process and required information • Pre-conversion utilities • Define basic set up decisions, and produces data integrity reports • Conversion • Typically need to run multiple test conversions • Post conversion validation • Configuration 46

  47. Domain Conversion Tool • Purpose • Modifies a schema definition file to add domain to selected tables and indexes, and modifies simple schema validation statements • Goes through the Progress source code and modifies all search and create statements with the domain statement • Benefits • Reduces costs of manual update of the source set with the domain statement • Reduces the risks to get errors out of this manual process

  48. Source Code TransformationHow it Works Read Plug-ins Read Create Find Transform Transform Code Lines fields etc. Write

  49. Domain Merge Tool ERP Database AR ERP Database CO ERP Database PE ERP Database BR ERP Database MI ERP Database PR ERP Database CL ERP Database MX ERP Database VE AR Domain CO Domain PE Domain BR Domain MI Domain PR Domain CL Domain MX Domain VE Domain Single QAD QAD SE 2008 Database

  50. Program Tracer Tool • Purpose • To identify what customized functions are actively used in your application • To identify how users are using your QAD applications • The results of the Program Tracer helps you to eliminate customizations and/or provide feedback on customization areas that needs review • Benefits • Eliminate unused functions from those to be migrated • Analyze how users use specific functions in order to improve the overall process

More Related