Aegis recommends a system platform consisting of a database server (typically dedicated) and a dedicated application server. One properly-outfitted virtual application server should support up to 400-500 users, depending on usage patterns. If data acquisition from automated production and test equipment is within scope for a deployment, an additional dedicated server is recommended for machine data acquisition and/or real-time analysis data dispersal. Due to the scalable/modular/distributed nature of the Aegis system architecture, customers have the option of adding additional application or xLink servers at a later date to support increased demands or equipment sets. | Gliffy |
|---|
| imageAttachmentId | att134975319 |
|---|
| baseUrl | https://factorylogix.atlassian.net/wiki |
|---|
| name | system_architecture |
|---|
| diagramAttachmentId | att134975346 |
|---|
| pageid | 134975318 |
|---|
| containerId | 134975318 |
|---|
| timestamp | 1722343898669 |
|---|
|
Item | Description |
|---|
CPU type | Intel® Xeon™ E-Family (E3/E5/E7) or newer (or AMD equivalent) | CPU speed | Processor with a minimum of 4 cores (or 8 Hyper-threaded processors) with a minimum clock speed of 2.2 GHz More than 4 cores may be required for higher transaction environments (>100,000 MES transactions daily). | System memory | 16 GB RAM | Networking | 1,000 Mbps or higher Ethernet | System partition | 60 GB System partition (RAID 1 or similar for fault tolerance) | Database storage | 500 GB data partition RAID 10 or similar for fault tolerance and performance For environments with less than 100 transactions per minute load (140,000 transactions per day), ensure that the database disk system, at minimum, is capable of 500 IOPS with 30 MB / s random read rate. For environments with more than 100 transactions per minute load (140,000 transactions per day), ensure that your database disk system, at minimum, is capable of 5000 IOPS with a 200 MB / s random read rate. The simplest way to achieve this is through the use of an SSD or NVMe based disk system.
| Log/backup partition | 375 GB log and database backup partition RAID 10 or similar for fault tolerance and performance For environments with less than 100 transactions per minute load (140,000 transactions per day), ensure that the database disk system, at minimum, is capable of 500 IOPS with 30 MB / s random read rate. For environments with more than 100 transactions per minute load (140,000 transactions per day), ensure that your database disk system, at minimum, is capable of 5000 IOPS with a 200 MB / s random read rate. The simplest way to achieve this is through the use of an SSD or NVMe based disk system.
| Temp DB partition | SSD or NVMe disks are recommended for higher transaction environments (>140,000 MES transactions dialy). | Operating system | Microsoft Windows Server x64 2016, 2019, or 2022 Standard Edition or higher | Database software | Microsoft SQL Server x64 2014, 2016, 2017, 2019, or 2022 Server Standard Edition | Info |
|---|
Enterprise Edition recommended for 24/7 operations with less than 4 hours per week of scheduled database maintenance time per week. |
|
SSD or NVMe disks are recommended for higher transaction environments (>100,000 MES transactions daily).
Performance in high transaction environments relies heavily on an optimal SQL server which may require additional CPU, memory, and disk I/O.
In lower transaction environments, it is generally possible to co-locate the FactoryLogix Database on a preexisting database server that is servicing other databases/applications. However, it then becomes possible for other applications to potentially interfere with the proper operation of FactoryLogix. For example, an ERP system using the same database server might run a big report, consuming large amounts of CPU and disk resources, leaving FactoryLogix with inadequate resources to service the factory floor. FactoryLogix administrators should ensure that the FactoryLogix Database has adequate resources on the server to function properly. Item | Description |
|---|
CPU type | Intel® Xeon™ E-Family (E3/E5/E7) or newer or AMD equivalent | CPU speed | Processor with a minimum of 4 cores (or 8 Hyper-threaded processors) with a minimum clock speed of 2.2 GHz | System memory | 16 GB RAM | Networking | 1,000 Mbps or better Ethernet | System partition | 60 GB System partition (RAID 1 or similar for fault tolerance) | Operating system | Microsoft Windows Server x64 2016, 2019, or 2022 Standard Edition or higher | Prerequisites | Microsoft .NET Framework 4.7.2 or later |
Item | Description |
|---|
CPU type | Intel® Xeon™ processor E-Family (E3/E5/E7) or newer or AMD equivalent | CPU speed | Processor with a minimum of 4 cores (or 8 Hyper-threaded processors) with a minimum clock speed of 2.2 GHz. | System memory | 16 GB RAM Minimum | Networking | 1,000 Mbps or better Ethernet | System partition | 100 GB System partition (RAID 1 or similar for fault tolerance) | Operating system | Microsoft Windows Server x64 2016, 2019, or 2022 Standard Edition or higher | Prerequisites | Microsoft .NET Framework 4.7.2 or later |
FactoryLogix supports deployment in virtualized environments, provided that a Type 1 hypervisor, such as VMware ESXi Microsoft Hyper-V. The minimum requirements for CPU, memory, and disk storage remain the same in a virtualized environment. Because many virtualization platforms share CPU and memory across multiple virtual machines, it is important to ensure that FactoryLogix virtual servers have the dedicated resources they need in a virtual environment. A dedicated vCPU should be assigned for each core required. If hyper-threading is in use and your virtualization environment considers a single hyper-threaded processor to be 2 vCPUs, 2 vCPUs should be assigned for each physical core required. |
