This Article Applies From:
DeMeter 2.7 |
Introduction
This article lists the hardware and operating system requirements for installing DeMeter.
TABLE OF CONTENTS 1.2- Hard disks space and performances 2- DeMeter and virtual machines |
1- DeMeter hardware requirements
1.1- Specifications overview
| Minimum Configuration (*) | Recommended configuration | ||
| CPU | Speed (GHz) | 2 | |
| Cores | 8 (**) (see also here) | N/A | |
| RAM (GB) | 32 (***) | N/A | |
| Ethernet ports | Number | 2 (****) | |
| Speed (Mb/s) | 1000 (*****) | N/A | |
| Disk space | 1 TB | N/A | |
| USB Ports | 1 (for DRIM) | ||
| Display | N/A | ||
| Operating systems | Desktop OS | N/A | |
| Server OS | Windows Server 2016 Windows Server 2019 Windows Server 2022 | ||
| .Net Version | 5 | ||
(*): These recommendations are given as starting point. Key factors to be considered whenever working with DeMeter are related to:
- Overall number of connectors.
- Connector type in- use.
- The TAKT time.
- …
It should be considered good practice to monitor over a month the system to ensure system performances are sufficient. This is especially true for virtual machines whose characteristics can easily be upgraded.
Please contact the support team should you require any help in monitoring the system performances
(**): Two cores are allocated to RavenDB for database handling – 2 cores are dedicated to data retrieval and catalogue. Other cores are necessary to handle data connection to the various connectors setup in your installation. The total number of Cores will also depend on the number of Assets connected to the server (please refer to Desoutter Industrial Tools : Installing DeMeter (desouttertools.com) article for further details.
(***): RAM memory is fundamental since live information is going to be displayed directly from said memory before writing to DeMeterDB.
(****): it is advised to use one port for data recovery, and another one for configuring / consulting DeMeter.
(*****): Ensure that your factory’s network backbone also operates at 1Gb/s (minimum).
1.2- Hard disks space and performances
Ensure that the hard drives you select offer you the level of performances matching your incoming data rate.
DeMeter performances will be negatively impacted if your hard drives can not keep up with the incoming data - this is especially true if you consider DeMeter more advanced features.
The storage size required to host the data is also a key factor. The table below provides you with the data storage requirements for a production rate of 1000 tightening a day as a reference.
Note that these figures may evolve over time as new features are added, or storage is optimised.
| 1000 tightening / day data size | ||||
| Number of Tools | 1 day (GB) | 2 weeks (GB) | 1 month (GB) | 6 months (GB) |
| 1 | 0.10 | 1 | 2 | 12 |
| 50 | 5 | 50 | 100 | 600 |
It is still considered good practice to monitor the disk space used to store the data regardless of the figures provided above.
| ⚠ | Note that DeMeterBI will stop importing data when the remaining disk space goes below 10% of the initial disk space. Please also note that DeMeterDB will stop sending data to DeMeterBI when remaining disk space goes below 15% of initial disk space. Note: you will be notified in the DeMeter Configurator when the remaining disk space reaches a set threshold. |
2- DeMeter and virtual machines
DeMeter must be installed on virtual machines whose performances match the above specifications.
For easier maintenance and operations, we also advise you to interface the DRIM to DeMeter using an USB to Network adapter: in doing so, you will avoid having to dedicate one of the USB port of the server hosting the virtual machine to the DRIM, but also avoid any mapping issues.
Note that the virtual machine installation and maintenance is outside the scope of Desoutter support.