1. 12.6.2016 BASIC ERP ARCHITECTURE Skorkovský, KPH, ESF MU,Brno

2. 12.6.2016 Simplified schema of ERP usage ERP Transaction- entries DB ERP Partners ReportsTrends Information (trends) Knowledge of methods applied for process management Decision Enterprise Key knowledgeKey decisions

3. Methods Theory of constraint Critical chain DBR Ishikawa Fishbone Diagram Boston matrix and PLC Magic Matrix (Gartner) Use of ERP analytic tools Pareto analysis SWOT (basic and advanced) MRP,MRP-II,CONWIP, Advanced Planning and scheduling Linear programming Methods of quality management

4. 12.6.2016 What could be controlled…

5. ERP The main objective of Enterprise Resource Planning, or ERP, is to integrate all departments and functions across a company into a single system by using a common database, the value of which is to be able to have only one correct set of data.

6. Isolated Data Islands 6 Management Marketing Accounting Customers Production Planning Sales Representatives Customer Orders Production Island Accounting Island Accounting Island Marketing & Sales Islands Marketing & Sales Islands Quality Management Island Quality Management Island Island of Deliveries Island of Deliveries Inventory and Production Quality Management Steel Service Center Vertical

7. 7 Management Marketing Accounting Customers Production Planning Quality management Internal Sales Customer support One Company Database One Solution One Database All Microsoft Steel Service Center Vertical Inventory and Production Sales Representatives

8. ISLAND SYSTEMS For example, records about inventory levels may be found in one database, while customer information may be found in its own separate database. Furthermore, these databases may be "island systems" (operating independently from each other and having no integration with other databases).

9. From hell to paradise –ERP (see meaning) 12.6.2016 You can change a business in order to copy rigid functions of the software ERP You can change a software in order to support your business Programming Parameter setup

10. ERP Evaluation and Succes dimensions 12.6.2016

11. Components of ERP success 12.6.2016

12. Information quality 12.6.2016  Accuracy - The information in System X is accurate  Completeness - System X provide sufficient information  Timeliness - The information in System X is up-to-date  Format - The information in System X is presented in a clear way  Relevancy - System X provide me with the information that I need to do my job

13. System quality 12.6.2016  Ease of use – System X is easy to use  Ease of learning – System X is easy to learn

14. Service quality 12.6.2016  Understanding - I have sufficient understanding about System X  Training - I have gained enough training on how to operate System X  Reliability – If the Service Support promises to do something by a certain time they will  Responsiveness - The Service Support provide prompt service  Assurance - The Service Support has adequate knowledge to help me if I experience any problems with System X  Empathy – The Service Support understands my needs

15. 12.6.2016 Technological pyramid

16. 12.6.2016 Development Tools ISVs Customer Relationship Management Supply Chain Management Financial Management Analytics Integrated homogeneous solution

17. 12.6.2016 Unique architecture Externí aplikace Zákazníci & obchodní partneři Zaměstnanci Application Server GUI (Windows) Commerce Portal Commerce Gateway (B2B) Country-specific Objects Customer-specific Objects Worldwide Generic Objects Vertical Solutions Objects Integrated Development Environment Microsoft SQL Server 2000 Microsoft Navision Database Server Database See live systém NAV

18. 12.6.2016 Main form (menu, toolbar, forms)

19. 12.6.2016 Main forms (card, list, form->sub-form )

20. 12.6.2016 Main forms (card, list, form->sub-form )

21. 12.6.2016 Main forms (card, list, form->sub-form ) Partner What

22. 12.6.2016 Table->Form principle Specification of fields in Table (object) Form (Card,Window), which is object as well and it is used to display data stored in the Table (object)

23. 12.6.2016 Table X->Table Y relations I. (example) X= Customer table Y=Post Code table Relation

24. Table X->Table Y relations II. (example) 12.6.2016

25. Relations among tables I

26. 12.6.2016 Relations among tables II

27. 12.6.2016 One table and its relations I

28. 12.6.2016 One table (Sales Line) and its relations II ERP NAV

29. Microsoft Dynamics NAV Sweet Points Windows compatible (menu, command, mutual relations to MS Office,..) Security ( ID, passwords, roles, protocols ) Menu and basic modules Shorthand keys and HELP Multilanguage Navigate and calculation (flow) fields, finding the reason why any document was created Reports Entries, dimensions 12.6.2016

30. Business Case Principles Sales Order Header Item Chair 4 pcs 30 EURO Entries in General Ledger F11=post Item Table 1 pcs 100 EURO Customer Table Item Table Sales Entry in database (Type Invoice) Item Ledger Entries in database (Type Sales) Availability, Costs,… Balance, Payments,.. F11 = posting, booking to G/L,…

31. 12.6.2016 Thanks for your attention