|
Type |
SIMATIC WinCC Open Architecture V3.10 |
|---|---|
|
Operating system |
|
|
PC hardware requirements 1) |
|
|
Processor type |
Intel Pentium or equivalent |
|
Minimum |
Intel Pentium IV 1.6 GHz (or better)2) 3) |
|
Recommended |
|
|
RAM |
|
|
Minimum |
512 MB2) |
|
Recommended |
|
|
Hard disk |
|
|
Minimum |
HD with 500 MB available 2) |
|
Recommended |
Server large system with local logging: SCSI LVD Controller, WIDE SCSI / LVD HDD or comparable storage system with at least 500 MB of available space2) |
|
Screen and graphics card (TrueColor) |
|
|
Minimum |
1024 x 7682) |
|
Recommended |
At least 1280 x 10242) |
|
Mouse and keyboard |
3-button mouse, German keyboard |
|
DVD drive |
for software installation |
|
Local power user rights |
|
1) For actual use in plants, the hardware requirements are largely dependent on the project size and the dynamic response of the process variables. Whenever possible, use rugged, high-quality hardware with corresponding functionalities such as redundant power supply units or RAID hard disks. WinCC OA supports dual and multi-processor mode and benefits significantly from the fact that each WinCC OA Manager can be assigned to one processor core as a system process. At the same time, however, it is important that the individual cores offer the highest possible performance (high clocking), since load-critical core processes such as the event manager run on exactly one core (for this reason, multi-core machines with low-clocked cores are unsuitable for WinCC OA). As for RAM, CPU and HDD, the usual rule applies: more is better
2) System requirements generally only refer to WinCC OA Version 3.10 under the supported versions of the Windows and Linux operating systems.
3) A precondition for the minimum requirement is that the operating system used does not have any greater requirements itself
4) With a large system it is essential that the system permits not only the highest data point numbers but also a high dynamic response.
WinCC OA is ideally suited for use in very large distributed systems. The optimum design of such systems demands corresponding system knowledge of WinCC OA. Due to the event-oriented processing, individual design parameters can be increased or reduced as necessary in actual applications.
|
Type |
SIMATIC WinCC Open Architecture |
|---|---|
|
Functionality/quantity structure |
|
|
Number of alarms |
150,000 2) |
|
Alarm text (number of characters) |
System-limited1) |
|
Alarm log |
System-limited1) |
|
Process values per alarm |
1 process value + up to 32 alarm associated values per alarm |
|
Constant load of alarms, max. |
500/s 2) |
|
Message burst, max. |
15,000/10 s every 5 min2) |
|
Logs |
|
|
Log data points |
Max. 250,000 per server2) |
|
Log types |
< 20 parallel logs, different retention period for each log |
|
Data storage format |
Oracle or file system |
|
Measured values per second, max. |
Server/single-user station: 7,000/s 2) 3) |
|
User log |
|
|
Logs |
System-limited1) |
|
Type |
SIMATIC WinCC Open Architecture |
|
Table size |
System-limited by ORACLE database |
|
Graphics system |
|
|
Number of screens |
System-limited1) |
|
Number of objects per screen |
System-limited1) |
|
Number of controllable fields per screen |
System-limited1) |
|
PowerTags |
< 750,000 per server 2) |
|
User management |
|
|
User accounts |
< 4096 |
|
Configuration languages |
2 (De, En) |
|
Runtime languages |
40 (of which 8 Asian) |
|
Multi-user system |
|
|
Server |
< 2048 2) 4) |
|
Number of clients |
< 244 per server 2) 5) |
1) Dependent on the available storage space
2) Dependent on the system configuration and the system load (due to the event-oriented architecture, the system load is essentially determined by the change rates of the values to be processed)
3) By means of high-performance hardware configuration (one archiving cluster and approx. 120 distributed systems that archive parallel values in the cluster): 200,000 archived value changes per second
4) Physical limit: <2048, in practice systems have already been implemented with up to 550 distributed systems
5) Physical limit: < 244 clients per server, recommended: max. 100 clients per server