| 2007 R0, R0.1 |
2007 R1 (all) |
2009 R1 (all), R2, R2.11 |
2009 R2.2 |
2010 R1 |
2010 R2 (all) |
|||
|---|---|---|---|---|---|---|---|---|
|
Windows |
Windows 7 |  |
|
|
||||
| Windows Server 2008 |
|
|
|
|
||||
| Windows Vista | |
|
|
|
|
|||
| Windows Server 2003 |
|
|
|
|
|
|
||
| Windows XP Pro | |
|
|
|
|
|
||
| Windows 2000 Server SP4 |
|
|
|
|
|
|
||
| Windows 64 bit |
Windows 7 | |
|
|||||
| Windows Server 2008 R2 |
|
|
|
|||||
| Windows Server 2008 |
|
|
|
|
||||
| Windows Vista | |
|
|
|
||||
| Windows Server 2003 R2 |
|
|
|
|
||||
Windows 7 (Ultimate and Professional Editions)
Windows Server 2008 (Standard and Enterprise Editions) = initial release/service pack 1 and release 2 (x64 only)
Windows Vista (Ultimate and Business Editions) = initial release, and service pack 1 and service pack 2
Windows Server 2003 (Standard and Enterprise Editions) = service pack 1/release 2, and service pack 2
Windows XP (Professional Edition) = service pack 2 (including 2a, 2b and 2c), and service pack 3
Crystal Reports XI release 2 is not supported by vendor (SAP) on Windows Server 2008.
The following table lists the recommended PC configurations for a variety of client and server scenarios. In the table the term 'object' refers to a database item whereas 'point' refers to a specific type of database item that stores I/O (aka point or tag). Historic points are database points that have been enabled for historian archive.
| Application | PC Requirement |
|---|---|
| WebX client | 2GHz CPU, 256MB RAM, 50MB free disk space |
| ViewX client | 2GHz CPU, 512MB RAM, 200MB free disk space |
| Stand-alone server, max 1000 objects |
2GHz CPU, 512MB RAM, 500MB free disk space, high performance graphics card |
| Stand-alone server max 10,000 objects 1-2 remote clients |
2GHz CPU, 512MB RAM, 500MB free disk space, high performance graphics card |
| Server with 10,000 objects, 5,000 historic points stored for 2 years online, 3 or more clients |
2x 2GHz CPU (ie. dual core), 2GB RAM, 100GB free disk space, separate disk (incl controller) for historic data. Windows server operating system ie 2003, 2008 or Win7 |
| Server with 50,000 objects, 25,000 historic points stored for 2 years online, multiple clients |
2x 3GHz CPU (ie. dual core ), 6GB RAM, 100GB free disk space, separate disk (incl controller) for historic data. Windows server operating system ie. 2003, 2008 or Win7 |
| Server with 100,000 objects, 75,000 historic points stored for 2 years online, multiple clients |
4x 3GHz CPU (ie. quad core or 2x dual core ), 6GB RAM, 140GB RAID 5 disk set for OS and configuration database. 2TB RAID 5 disk for historic archive Windows server operating system ie. 2003, 2008 or Win7 |
| Server with 175,000 objects, 100,000 historic points stored for 2 years online, multiple clients |
4x 3GHz CPU (ie. quad core or 2x dual core ), 12GB RAM, 140GB RAID 5 disk set for OS and configuration database. 2TB RAID 5 disk for historic archive 64 bit Windows server operating system ie 2003, 2008 or Win7 |
| Server with 250,000 objects, 150,000 historic points stored for 2 years online, multiple clients |
8x 3GHz CPU (ie. 8 cores in total), 24GB RAM, 140GB RAID 5 disk set for OS and configuration database. 4TB RAID 5 or RAID 0+1 disk set for historic archive 64 bit Windows server operating system ie 2003, 2008 or Win7 |
The typical point to object ratio is 1:2. So for a system with 50,000 points or tags you would have 100,000 objects in your configuration database.This ratio will vary based on your application and is only provided as a guide.
The amount of disk space required is determined by the number of historic records in the historian and events in the event journal. Each historic record is 32 bytes in size and archive is based on acquisition rate and whether you have compression enabled or not. The Event record is 768 bytes in size and all the alarm states are by default entered into the event journal as are configuration edits and other run-time events such as user logon, etc.