ERP 10 Hardware Sizing Guide - Spiceworks
An Epicor White PaperERP 10 HardwareSizing Guide
ERP 10 Hardware Sizing GuideTable of ContentsIntroduction.1Hardware sizing guide for up to 15 user load.2ERP 10 – Hardware sizing guide (up to 50 user load).4ERP 10 Application usage Load Expectation (up to 50 user load).5ERP 10 – Hardware for up to 200 user load.6ERP 10 Application usage Load Expectation (up to 200 user load).8ERP 10 – Application Server/Hypervisor/Reporting Server.9ERP 10 – SQL Server.10ERP 10 – Hardware sizing for up to 2,000 Users.12ERP 10 – Hardware sizing for up to 4,000 Users.12Scale Out Configurations.12ERP 10 – Virtual Appserver on VMware.13ERP 10 – Virtual Appserver on Hyper-V.14ERP 10 – Virtual SQL Server on VMware.15ERP 10 – Virtual SQL Server on Hyper-V.16ERP 10 – Hardware sizing on Virtual Servers.17Hardware Requirements for Other Epicor Systems.17Other Epicor Systems.18Network.19Appendix.21b
ERP 10 Hardware Sizing GuideIntroductionWelcome to the Epicor ERP 10 Hardware Sizing Guide. The goal of this guide is toprovide a practical approach to sizing your Epicor ERP 10 application and databaseserver to obtain the best performance possible from your Epicor software. It willalso help you plan for the future growth of your system.The key to success in getting your hardware sized correctly is to define yourapplication load correctly and then to match it with the appropriate hardwareresources. Choosing a hardware architecture which can grow as your businessand/or application load grows is also important.It is very difficult to accurately come up with a hardware recommendation thatmatches your unique application usage. Many of our customers find this guidevery useful and accurate after they have followed all the steps described here.There are cases where the provided recommendations may fall short for whateverreason. It is therefore very difficult to guarantee or imply that the hardwarepurchased using this guide will solve your unique business requirements. Toimprove the odds of success, we highly recommend that you work with the EpicorTechnical Solutions group and implement their hardware sizing recommendations.This guide is meant for customers buying new hardware and software so werecommend latest software versions supported by Epicor ERP. If you want todetermine if other versions of software are supported then please contact Epicortechnical support.Please note that you should consult Epicor Technical Services for High Availabilityand Business Continuity customer requirements as this sizing guide cannot getinto details of that topic.1
ERP 10 Hardware Sizing GuideHardware sizing guide for up to 15 user loadTable 1Small ERPERP 10 Physical Server. This configuration can support standard load of 15 Office Datacollection users. See table 2 for the definition of standard load.Operating System & SQL Server Windows Server 2012 Standard Edition SQL Server 2012 Standard Edition (supports upto 16 cores on Standard SKU)ApplicationsEpicor ERP 10, Epicor Web Access (EWA), Enterprise Search (ES),Epicor Social Enterprise (ESE)Processors1 x CPU socket recommendations: Intel Xeon E5-2450 v2 2.50GHz, 20M Cache, 8.0GT/s QPI, Turbo, 8C, 95WIt is recommended to leave Hyper-Threading enabled (check BIOS settings).Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.Memory (RAM)32 GB ECCStorage – Option #1 - HDD and2 x 146GB 15k RPM HDDs in RAID 1, 3 Gbps, 4 x 200GB SSDs in RAID 1 or 10, 3 GbpsOperating system and page file on HDD SQL Database and reports on SSDs.SSD (Recommended)Note - MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting better by theday, if you maintain a warranty coverage on Enterprise MLC SSDs then you can purchaseMLCs.Storage Option #2 (you can usethis option if your SAN passesthe SQLIO test)Existing Storage AreaNetwork (SAN)To find out if your SAN delivers sufficient performance for SQL database, see the “Testingthe performance of an existing SAN” section in the Appendix for details on how to run astorage benchmarking tool (SQLIO).Required SQLIO results at all times including during peak load from other applicationusage on the SAN:Database drive letter (location of SQLmdf file):Must be able to deliver at least 100MB/sec at a latency of less than 5ms.Transaction log drive letter (location of SQL log file):Must be able to deliver at least 30MB/sec at a latency of less than 5ms.Tempdb drive letter (location of SQL temp db file):Must be able to deliver at least 50MB/sec at a latency of less than 5ms.NetworkFor good network performance, use 1 Giga bit (or faster) network cards.To ensure that network latency is as low as possible between the Epicor applicationserver and the SQL database server, add at least two network cards: One dedicated network card that is directly connected to the SQL database (Cable from network card to network card). One dedicated network card that is connected to the LAN (and is processing all networktraffic except SQLdatabase traffic).2
ERP 10 Hardware Sizing GuideTable 2Load expectation for up to 15 user load (Small ERP)Application UsageLoad DescriptionInteractive Application LoadTypical application usage by end-users using ERP 10 via Smart Client and/orbrowser and / or mobile devices.Automation and heavy processingIf you are processing more than 25K transactions (insert, update or delete) in anyone hour period of the working day then schedule this activity to less busy time ofthe day. 25K transaction is the sum total of all sources of automatic processing.1. Epicor Service Connect (ESC)2. Imports (e.g. PO, Sales Order, ARinvoice and Shipping)3. Automatic updating of data notcovered by ESC4. Heavy reporting.Custom Code (BPM is not countedas Custom code)If this activity cannot be scheduled to less busy time of the day then please discussthe server sizing with Epicor technical services.Heavy and concurrent reporting should be scheduled to less busy time of the day oron a separate reporting appserver.No (If yes then discuss the increase in usage with Epicor technical services)In-house custom applicationrunning on Epicor ERP 10 machineand/or using Epicor ERP 10database and/or Epicor ERP 10appserver directlyMRP (Manufacturing customers)MRP regeneration will be scheduled during less busy times. For daily MRP runs useMRP net change.If your business requires you to run more than 2 processes and 2 schedulers forMRP run then discuss the increase usage with Epicor technical services.Growth and acquisition of newNousersSeasonal peaksNo3
ERP 10 Hardware Sizing GuideERP 10–Hardware sizing guide (up to 50 user load)Table 3Medium ERPERP 10 Physical Server. This configuration can support standard load of 50 Office Data collection users. See table 4 for the definition of standard load.Operating System & SQL ServerWindows Server 2012 Standard EditionSQL Server 2012 Standard Edition (supports up to 16 cores on Standard SKU)ApplicationsEpicor ERP 10, Epicor Web Access (EWA), Enterprise Search (ES),Epicor Social Enterprise (ESE)Processors1 x CPU socket recommendations: Intel Xeon E5-2667 v2 3.3GHz, 25M Cache, 8.0GT/s QPI, Turbo, HT, 8C, 130WIt is recommended to leave Hyper-Threading enabled (check BIOS settings).Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.Memory (RAM)64 GB ECCStorage – Option #1 - HDD andSSD (Recommended)2 x 146GB 15k RPM HDDs in RAID 1, 3 Gbps4 x 200GB SSDs in RAID 1 or 10, 3 GbpsOperating system and page file on HDDSQL Database and reports on SSDs.Note - MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting betterby the day, if you maintain a warranty coverage on Enterprise MLC SSDs then youcan purchase MLCs.Storage Option #2 (you can usethis option if your SAN passes theSQLIO test)To find out if your SAN delivers sufficient performance for SQL database, see the“Testing the performance of an existing SAN” section in the Appendix for details onhow to run a storage benchmarking tool (SQLIO).Existing Storage Area Network(SAN)Required SQLIO results at all times including during peak load from otherapplication usage on the SAN:Database drive letter (location of SQL mdf file):Must be able to deliver at least 100MB/sec at a latency of less than 5ms.Transaction log drive letter (location of SQL log file):Must be able to deliver at least 30MB/sec at a latency of less than 5ms.Tempdb drive letter (location of SQL temp db file):Must be able to deliver at least 50MB/sec at a latency of less than 5ms.NetworkFor good network performance, use 1 Giga bit (or faster) network cards.To ensure that network latency is as low as possible between the Epicor applicationserver and the SQL database server, add at least two network cards: One dedicated network card that is directly connected to the SQL database (Cable from network card to network card). One dedicated network card that is connected to the LAN (and is processing allnetwork traffic except SQL database traffic).4
ERP 10 Hardware Sizing GuideERP 10 Application usage Load Expectation(up to 50 user load)Table 4Load expectation for up to 50 user load (Medium ERP)Application UsageLoad DescriptionInteractive Application LoadTypical application usage by end-users using ERP 10 via Smart Client and/orbrowser and/or mobile devices.Automation and heavy processingIf you are processing more than 50K transactions (insert, update, or delete) in anyone hour period of the working day then schedule this activity to less busy time ofthe day. 50K transaction is the sum total of all sources of automatic processing.Epicor Service Connect (ESC)Imports (e.g. PO, Sales Order, ARinvoice and Shipping)3Automatic updating of data notcovered by ESCHeavy reporting.If this activity cannot be scheduled to less busy time of the day then please discussthe server sizing with Epicor technical services.Heavy and concurrent reporting should be scheduled to less busy time of the day oron a separate reporting appserver.Custom Code (BPM is not countedas Custom code)In-house custom applicationrunning on Epicor ERP 10 machineand / or using Epicor ERP 10database and / or Epicor ERP 10appserver directlyNo (If yes then discuss the increase in usage with Epicor technical services)MRP (Manufacturing customers)MRP regeneration will be scheduled during less busy times. For daily MRP runs useMRP net change.If your business requires you to run more than 3 processes and 3 schedulers forMRP run then discuss the increase usage with Epicor technical services.Growth and acquisition ofnew usersNoSeasonal peaksNo5
ERP 10 Hardware Sizing GuideERP 10–Hardware for up to 200 user loadTable 5ERP ServerERP 10 Physical Server Machine. This configuration can support standard load of 200Office Data collection users. See table 6 for the definition ofstandard load.Operating System & SQL ServerWindows Server 2012 Standard Edition SQL Server 2012 Standard Edition (supportsup to 16 cores on Standard SKU)ApplicationsEpicor ERP 10, Epicor Web Access (EWA), Enterprise Search (ES),Epicor Social Enterprise (ESE)Processors2 x CPU sockets with following configuration Intel Xeon E5-2667v2 3.3GHz, 25M Cache, 8.0GT/s QPI, Turbo, HT, 8C, 130W(or better)It is recommended to leave Hyper-Threading enabled (check BIOS settings).Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.Memory (RAM)96 GB ECCStorage – Option #1 – Fusion-IOOperating system and page file: 2 x 15K HDD in RAID 1.PCI-Express based card i.e. Fusion Fusion-IO should hold SQL database (MDF file), SQL transaction log (LDF file) and SQLIO (SAS / SATA based) storagetempdb files.Epicor Reports – 2 x 15K HDD in RAID 1Total 4 15K RPM HDD (3 Giga bits /seconds SATA or SAS) Quantity 1, at least 785 GB ,Fusion-IO cardStorage – Option #2 - SSD(Recommended)Operating system and page file: 2 x Solid State Drive in RAID 1.Solid State Drive (SAS / SATAbased) storageSQL transaction log (LDF file): 2 x Solid State in RAID 1. (Only Epicor SQL Log file onthis drive)SQL database (MDF file): 4 x Solid State Drive in RAID 10.SQL tempdb: 2 x Solid State Drive in RAID 1. (This will house at least 8 tempdb files)Epicor Reports – 2 x Solid State Drive in RAID 1Total drives - 12 Solid State Drives (3 Giga bits /seconds SATA or SAS)Note - MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting betterby the day, if you maintain a warranty coverage on Enterprise MLC SSDs then you canpurchase MLCs.6
ERP 10 Hardware Sizing GuideStorage Option #3 (you can usethis option if your SAN passesthe SQLIO test)To find out if your SAN delivers sufficient performance for SQL database, see the“Testing the performance of an existing SAN” section in the Appendix for details onhow to run a storage benchmarking tool (SQLIO).Existing Storage Area Network(SAN)Required SQLIO results at all times including during peak load from other applicationusage on the SAN:Database drive letter (location of SQL mdf file):Must be able to deliver at least 100MB/sec at a latency of less than 5ms.Transaction log drive letter (location of SQL log file):Must be able to deliver at least 30MB/sec at a latency of less than 5ms.Tempdb drive letter (location of SQL temp db file):Must be able to deliver at least 50MB/sec at a latency of less than 5ms.NetworkFor good network performance, use 1 Giga bit (or faster) network cards.To ensure that network latency is as low as possible between the Epicor applicationserver and the SQL database server, add at least two network cards: One dedicated network card that is directly connected to the SQL database(Cable from network card to network card). One dedicated network card that is connected to the LAN (and is processing allnetwork traffic except SQL database traffic).7
ERP 10 Hardware Sizing GuideERP 10 Application usage Load Expectation(up to 200 user load)Table 6Load expectation for up to 200 user load (ERP Server)Application UsageLoad DescriptionInteractive Application LoadTypical application usage by end-users using ERP 10 via Smart Client and / orbrowser and / or mobile devices.Automation and heavy processingIf you are processing more than 100K transactions (insert, update or delete) in anyone hour period of the working day then schedule this activity to less busy time ofthe day. 100K transaction is the sum total of all sources of automatic processing.1. Epicor Service Connect (ESC)2. Imports (e.g. PO, Sales Order, ARinvoice and Shipping)3. Automatic updating of data notcovered by ESC4. Heavy reporting.If this activity cannot be scheduled to less busy time of the day then please discussthe server sizing with Epicor technical services.Heavy and concurrent reporting should be scheduled to less busy time of the dayor on a separate reporting appserver.Custom Code (BPM is not countedas Custom code)In-house custom applicationrunning on Epicor ERP 10 machineand / or using Epicor ERP 10database and / or Epicor ERP 10appserver directlyNo (If yes then discuss the increase in usage with Epicor technical services)MRP (Manufacturing customers)MRP regeneration will be scheduled during less busy times. For daily MRP runs useMRP net change.If your business requires you to run more than 6 processes and 6 schedulers forMRP run then discuss the increase usage with Epicor technical services.Growth and acquisition of newusersNoSeasonal peaksNo8
ERP 10 Hardware Sizing GuideERP 10–Application Server/Hypervisor/Reporting ServerTable 7Table NameApplication Server APP01Operating SystemWindows Server 2012 Standard EditionApplicationsEpicor ERP 10, Epicor Web Access (EWA), Enterprise Search (ES),Epicor Social Enterprise (ESE)Processors2 x CPU sockets with following configuration: Intel Xeon E5-2690 v2 3 GHz (or better)It is recommended to leave Hyper-Threading enabled (check BIOS settings).Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.Memory (RAM)64 GB ECCSolid State Drive (SAS/ SATA based) storage(recommended)Operating system: 2 x 15k RPM HDDs in RAID 1.The following files are stored in 2 x SSDs in RAID 1: Epicor ERP 10 files. Reports and temporary data (EpicorData).Two SSDs are required.Two SCSI / SAS HDDs are required.When using this configuration as virtual host buy enough disk space for all VMs.NetworkFor good network performance, use 1 Giga bit (or faster) network cards.To ensure that network latency is as low as possible between the Epicor applicationserver and the SQL database server, add at least two network cards: One dedicated network card that is directly connected to the SQL database(Cable from network card to network card). One dedicated network card that is connected to the LAN (and is processing all networktraffic except SQL database traffic).9
ERP 10 Hardware Sizing GuideERP 10–SQL ServerTable 8Table NameSQL Server – SQL01Operating System & SQLServerWindows Server 2012 Standard EditionApplicationsEpicor ERP 10, Epicor Web Access (EWA), Enterprise Search (ES), Epicor Social Enterprise (ESE)Processors2 x CPU sockets with following configuration:SQL Server 2012 Standard Edition (supports up to 16 cores on Standard SKU, you may wantto consider enterprise edition for high availability and online indexing features) Intel Xeon E5-2667 v2 3.3GHz, 25M Cache, 8.0GT/s QPI, Turbo, HT, 8C, 130WIt is recommended to leave Hyper-Threading enabled (check BIOS settings).Disable Power Saving options and C-States in BIOS. Enable Turbo Boost.Memory (RAM)128 GB ECCStorage – Option #1 –Operating system and page file: 2 x 15K HDD in RAID 1.Fusion-IO (Recommended) Fusion-IO should hold SQL database (MDF file), SQL transaction log (LDF file) andPCI-Express based cardSQL tempdb files.i.e. Fusion IO (SAS / SATAEpicor Reports – 2 x 15K HDD in RAID 1based) storageTotal 4 15K RPM HDD (3 Giga bits /seconds SATA or SAS) 1 Fusion-IO cardStorage – Option #2 – SSDSolid State Drive (SAS /SATA based) storageOperating system and page file: 2 x Solid State Drive in RAID 1.SQL database (MDF file): 4 x Solid State Drive in RAID 10.SQL transaction log (LDF file): 2 x Solid State in RAID 1. (Only Epicor SQL Log file on thisdrive)SQL tempdb: 2 x Solid State Drive in RAID 1. (This will house at least 8 tempdb files)Epicor Reports – 2 x Solid State Drive in RAID 1Total drives - 12 Solid State Drives (3 Giga bits /seconds SATA or SAS)Note - MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting better bythe day, if you maintain a warranty coverage on Enterprise MLC SSDs then you canpurchase MLCs.10
ERP 10 Hardware Sizing GuideStorage Option #3 (youcan use this option if yourSAN passes the SQLIOtest) Existing Storage AreaNetwork (SAN)To find out if your SAN delivers sufficient performance for SQL database, see the “Testing theperformance of an existing SAN” section in the Appendix for details on how to run a storagebenchmarking tool (SQLIO).Required SQLIO results at all times including during peak load from other application usageon the SAN:Database drive letter (location of SQL mdf file):Must be able to deliver at least 100MB/sec at a latency of less than 5ms at all times.Transaction log drive letter (location of SQL log file):Must be able to deliver at least 30MB/sec at a latency of less than 5ms at all times.Tempdb drive letter (location of SQL temp db file):Must be able to deliver at least 50MB/sec at a latency of less than 5ms at all times.NetworkFor good network performance, use 1 Giga bit (or faster) network cards.To ensure that network latency is as low as possible between the Epicor application serverand the SQL database server, add at least two network cards: One dedicated network card that is directly connected to the SQL database (Cable fromnetwork card to network card). One dedicated network card that is connected to the LAN (and is processing all networktraffic except SQL database traffic).11
ERP 10 Hardware Sizing GuideERP 10–Hardware sizing for up to 2,000 UsersTable 9ServerQuantityAppserver1 x APP01SQL Server1 x SQL01Integration Services and Reporting1 X APP01ERP 10–Hardware sizing for up to 4,000 UsersTable 10ServerQuantityAppserver2 x APP01SQL Server1 x SQL01Integration Services and Reporting1 X APP01Load balancerF5 switch or KEMP LoadMasterScale Out Configurations12
ERP 10 Hardware Sizing GuideERP 10–Virtual Appserver on VMwareTable 11Table NameVMWAREAPP01Host softwareVMware vSphere 5.5Guest OSWindows Server 2012 Standard EditionVirtual CPU count4 virtual CPUsCreate a full CPU reservation to ensure that the virtual machinehas dedicated access to physical CPU cores.It is not recommended to overcommit CPU resources.Memory (RAM)12 GB (reserved RAM)It is not recommended to overcommit memory resources.If needed, disable Memory Ballooning so that the virtualapplication server has a dedicated amount of RAM.Ensure that the RAM on the host supports ECC.Physical CPU requirements(host requirements)See APP01Virtual hard diskUse Thick Provisioning and ensure that Eager Zeroing is in use.Enable Storage I/O Control (SIOC) and set the threshold to25ms.Virtual hard disk controllerUse the Paravirtual SCSI adapter.Guest OS virtualization softwareInstall and use the latest VMware Tools.NetworkEnsure that the physical host has multiple physical networkcards which are all utilized by the hosted virtual machines.Use the VMXNET3 virtual network card.Load balancingPhysical load balancing appliance recommended like F5 switchor Kemp LoadMaster.VM Backup softwareVM level snapshot backup works for Epicor ERP 10.File-level backups are supported.13
ERP 10 Hardware Sizing GuideERP 10–Virtual Appserver on Hyper-VTable 12Table NameHYPERVAPP01Host softwareWindows Server 2012 Standard Edition with Hyper-V roleGuest OSWindows Server 2012 Standard EditionVirtual CPU count4 virtual CPUsCreate a full (100%) virtual machine reserve to ensure that the virtual machine hasdedicated access to physical CPU cores.It is not recommended to overcommit CPU resources.Memory (RAM)12 GB (reserved RAM)Select Static memory when you allocate memory to the virtual machine.It is not recommended to overcommit memory resources.Ensure that the RAM on the host supports ECC.Physical CPU (host) requirementsSee APP01Virtual hard diskUse Fixed Size virtual hard disks.Virtual hard disk controller Use the IDE Controller option for the virtual hard disk that contains the OS. Use the SCSI Controller option for all other virtual hard disks.Guest OS virtualization softwareInstall and use the latestIntegration Services.NetworkUse the Network Adapter virtual network card (and not the Legacy NetworkAdapter).Load balancingPhysical load balancing appliance recommended. Software based works too. UseMulticast Mode if you are using Microsoft Network Load Balancing (NLB). This isrecommended for stability reasons.Backup softwareVM level snapshot backup works for Epicor ERP 10.File-level backups are supported.14
ERP 10 Hardware Sizing GuideERP 10 – Virtual SQL Server on VMwareVirtualization of SQL Server takes careful planning and appropriate resources to optimize performance. Youshould work with the Epicor Technical Services Group or Hardware Sales Team to develop and approve a SQLvirtualization plan.Table 13Table NameVMWARESQL01Host softwareVMware vSphere 5.5Guest OSWindows Server 2012 Standard EditionVirtual CPU countMinimum 4 virtual CPUs, increase vCPU count as dictated by the loadCreate a full CPU reservation to ensure that the virtual machine has dedicatedaccess to physical CPU cores.It is not recommended to overcommit CPU resources.Memory (RAM)24 GB (reserved RAM)It is not recommended to overcommit memory resources.If needed, disable Memory Ballooning so that the virtual application server has adedicated amount of RAM.Ensure that the RAM on the host supports ECC.Physical CPU requirementsSee SQL01(host requirements)Virtual hard diskUse Thick Provisioning and ensure that Eager Zeroing is in use.Enable Storage I/O Control (SIOC) and set the threshold to 25ms.Virtual hard disk controllerUse the Paravirtual SCSI adapter.Guest OS virtualization softwareInstall and use the latest VMware Tools.NetworkEnsure that the physical host has multiple physical network cards which are allutilized by the hosted virtual machines.Use the VMXNET3 virtual network card.VM Backup softwareVM level snapshot backup works for Epicor ERP 10. When you virtualize SQLServer be sure to test and make sure differential backup works correctly inyour case.File-level backups are supported.15
ERP 10 Hardware Sizing GuideERP 10 – Virtual SQL Server on Hyper-VVirtualization of SQL Server takes careful planning and appropriate resources to optimize performance. Youshould work with the Epicor Technical Services Group or Hardware Sales Team to develop and approve a SQLvirtualization plan.Table 14Table NameHYPERVSQL01Host softwareWindows Server 2012 Standard Edition with Hyper-V roleGuest OSWindows Server 2012 Standard EditionVirtual CPU countMinimum 4 virtual CPUs, increase vCPU count as dictated by the loadCreate a full (100%) virtual machine reserve to ensure that the virtual machine hasdedicated access to physical CPU cores.It is not recommended to overcommit CPU resources.Memory (RAM)24 GB (reserved RAM)Select Static memory when you allocate memory to the virtual machine.It is not recommended to overcommit memory resources.Ensure that the RAM on the host supports ECC.Physical CPU (host) requirementsSee SQL01Virtual hard diskUse Fixed Size virtual hard disks.Virtual hard disk controller Use the IDE Controller option for the virtual hard disk that contains the OS. Use the SCSI Controller option for all other virtual hard disks.Guest OS virtualization softwareInstall and use the latest Integration Services.NetworkUse the Network Adapter virtual network card(and not the Legacy Network Adapter).Backup softwareVM level snapshot backup works for Epicor ERP 10. When you virtualize SQL Serverbe sure to test and make sure differential backup works correctly in your case.File-level backups are supported.16
ERP 10 Hardware Sizing GuideERP 10–Hardware sizing on Virtual ServersTable 15ServerQuantityAppserver1 x VMWAREAPP01 per 25 interactive users OR 1 x HYPERVAPP01 per 25interactive usersSQL ServerSee SQL01 for physical SQL ServerSee VMWARESQL01 for SQL Server on VMwareSee HYPERVSQL01 for SQL Server on Hyper-VVirtualization of SQL Server takes careful planning and appropriate resources tooptimize performance. You should work with the Epicor Technical Services Groupor Hardware Sales Team to develop and approve a SQL virtualization plan.Integration Services and Reporting1 x VMWAREAPP01 or HYPERAPP01 for 8 to 10 concurrent long running reportduring busy time.Load BalancingF5 switch or Kemp LoadMasterHardware Requirements for Other Epicor SystemsEpicor Client machine / Epicor WorkstationFor desktop / network clients, keep in mind that other installed applications, specifically Microsoft products, have requirementsof their own over and above the requirements for Epicor ERP 10. The Epicor client will perform better on workstations thathave sufficient memory and processor power to run all your applications.Table 16Recommended ConfigurationOperating SystemWindows Vista / 7 or 8 Professional(32-bit or 64-bit*)Processor2.8 GHz or higher. Recommended dual core 32-bit or 64-bit processor and SATAhard drives. SSD is especially beneficial if the workstation runs multiple applicationsat the same time.RAM4 GB (add more RAM if the workstation is shared by multiple applications)Disk Space for EpicorSmart Client Software2 GBMonitorSVGA or higher adapter Color SVGA monitor with 1024 X 768 resolutionDVD-RDVD-R drive (if not on server)OtherInternet connection recommendedfor online support and downloading latest updates17
ERP 10 Hardware Sizing GuideOther Epicor SystemsTable 17System TypeHardware DescriptionRemote Desktop ServicesFor every 100 users use server configuration described by APP01Epicor Service Connect1 X VMWAREAPP01 OR 1 X HYPERVAPP01EPMDepending on load either use1 X SQL01 or 1 x Medium ERP configurationAFR1 X VMWAREAPP01 OR 1 X HYPERVAPP01Handheld EquipmentDevice Requirements Screen size minimum of 240 x 320 Device must support MS Terminal Services client IEEE 802.11 Radio Frequency standards supportAccess Points IEEE 802.11 Radio Frequency standards supportBarcode EquipmentSupport for Bar 39 BarcodeMES WorkstationPioneerPOS Stealth M5Same configuration as Epicor workstation (Table 12)PrinterAt least one laser printer required for standard reports and formsMust have current Windows driversHardware for any other system?If you have purchased any other software license from Epicorplease work with the Epicor Technical Solutions or Epicor HardwareSales group to see if you need extra servers to run them. Someapplications can be installed on one shared server.CommunicationsAn Internet connection is required to access the Epicor OnlineSupport Center for interim and commercial releases and remotesupport. DSL or higher quality connection recommended.18
ERP 10 Hardware Sizing GuideNetworkHardware RecommendationsA 1 Gbit (or faster) n
server and the SQL database server, add at least two network cards: One dedicated network card that is directly connected to the SQL database (Cable from network card to network card). One dedicated network card that is connected to the LAN (and is processing all network traffic except SQL database traffic). ERP 10 Hardware Sizing Guide
Then, MRP II extended to ERP systems [5], [8], [9]. Table 1 depicts the evolution of ERP systems. TABLE I. ERP EVOLUTION [5] Year Chronology 2009 ERP Cloud 2000s Extend ERP 1990s ERP 1980s MRP II 1970s MRP 1960s IC There is no single critical factor that can guarantee the success of the ERP system.
ERP MAS 90, Sage ERP MAS 200, and Sage ERP MAS 200 SQL. This manual also contains information and troubleshooting tips on the configuration of the various operating systems and environments in which the Sage ERP MAS software is supported. The instructions contain detailed technical information on the configuration ofFile Size: 1MB
SAP ERP For the purposes of this document the term SAP ERP is used generically and can refer to either SAP S/4HANA or SAP ERP 6. When needed, SAP S/4HANA or SAP ERP 6 are refered to specifically. SAP ERP 6.0 SAP ERP 6.0 Refers to the required SAP ERP 6 and EHP level that is supported by this solution
ERP ERP Components ERP Key Resources Multiprocessor End Users :Peripherals Key Components OS Platform. MS-SQL IBM-DB2 DBMS System Traffic Monitoring Remote Access Software:End Users DBA Business ERP Functional Areas ERP and Virtualization. ERP virtual machine (VM) server technology MissionCritical Hardware Virtualization .
2.4 Other types of control valves 40 2.5 Control valve selection summary 42 2.6 Summary 46 3 Valve Sizing for Liquid Flow 47 3.1 Principles of the full sizing equation 48 3.2 Formulae for sizing control valves for Liquids 51 3.3 Practical example of Cv sizing calculation 52 3.4 Summary 54 4 Valve Sizing for Gas and Vapor Flow 55
Battery Sizing Example 4. Sizing with Software 5. Battery Charger Sizing Saft Battery 2 Sizing. The Art and Science of Battery Sizing Saft Battery . 2-8 hr. battery backup normal Time (hh:mm:ss) Current (A) Paralleling Switchgear 8 120V to 600V (typical) DC bus 24, 48 or 125Vdc
Modern ERP (MERP) chapter Global Bike (GB) BY WEEK MERP Chapter 1: Introduction to ERP Systems MERP Chapter 2: ERP Technology MERP Chapter 3: ERP and Business Process Redesign MERP Chapter 4: Process Mapping MERP Chapter 5: ERP Life Cycle: Planning and Package Selection MERP Chapter 6: ERP
The Ross ERP 6.2 Change Summary Guide describes the enhancements to Ross ERP 6.2 applications. Intended audience It is intended for the person(s) responsible for maintaining the data for Ross ERP applications in your company. Users of this guide should have a working knowledge of the Ross ERP applications as this guide covers enhancements in
