SecurOS System Specs v.2.7
SecurOS System Specs v.2.7
Scope of Document:
This document is intended to help build a SecurOS server / workstation best suited for your system, in the case that the ISS Server line is
not being used. This document should be used as a guideline only. Values for camera counts, bitrate, fps, and resolution may vary
project to project and specifications should be adjusted accordingly. For CPU models mentioned in this document, it is not necessary to
use the same exact ones. CPUs with similar specifications can be used.
For additional questions please contact your local ISS Support Team.
2
SECTION 1: SecurOS Operator Workstation Specifications
Sample Specifications
RAM 16 GB (2x8GB) DDR4 3200 Mhz
# CPUs 1
Intel® Core™ i5-11600K
Sample CPU (12M Cache, 3.90 GHz) or better
6 Cores / 12 Threads
256 GB or more
OS Drive
(7.2K SATA, SAS, or SSD)
4GB NVIDIA Turing / Ampere (or
Graphics
better)
Network 2 x 1 Gb
SECTION 1 NOTES:
• SecurOS uses hardware capabilities of Intel® HD Graphics (with Intel® Quick Sync Video (QSV) 2.0 technology) as well as NVIDIA® graphics cards for decompression of H.264/H.265
video. To be able to view the amount of cameras specified above, one of these technologies must be used.
• Intel® QSV support for decompression of H.264 video, starts at 3rd Generation Core Processors; Intel QSV support for decompression of H.265 video, starts at 6th Generation Core
Processors.
• For supported NVIDIA® cards, refer to: https://developer.nvidia.com/video-encode-decode-gpu-support-matrix .
• DirectX 11 or higher must be installed on SecurOS Operator Workstations and Video Servers.
• The maximum number of cameras displayed can vary depending on the camera vendor used and the H.264/H.265 codec profile.
• If using older generation NVIDIA® cards (older than Turing / Ampere), then H.265 performance would decrease by 50%.
3
SECTION 2: SecurOS Video Server Specifications - VMS Cameras (SecurOS 64-bit version)
Minimal # Recording
1 6 10
Drives
2 x 1 Gbps /
Network 2 x 1 Gb 4 x 1 Gb 2 x 10 Gbps SFP+ /
2 x 10 Gbps Ethernet
1
Max recommended on 1 server or VM.
4
SECTION 2 NOTES:
• If running SecurOS on a virtual machine (VM), the ratio between physical cores and vCPUs should be 1:2. So for a 8 physical core processor, 16 vCPUs should be allocated.
For more information on running SecurOS on a virtual environment, refer to Section 5 of this document.
• The data above is assuming that no more than 2 SecurOS Operator Workstations (each with 2 physical monitors concurrently displaying 16 cameras) are connected to the
server. Systems with more than 50 SecurOS Operator Workstations will need a dedicated SecurOS Connection Server.
• If it is required to use a higher total bitrate or total amount of cameras per server, please consult with an ISS Pre-Sales engineer.
• Cameras connected to these servers will be used for video management purposes only (video streaming/recording/motion detection/etc… – no extra ISS
analytics).
• It is assumed that there will be NO local monitoring done from the video servers.
• Storage values above are sufficient for running Windows OS and the ISS software (they don't take into account video recording). For IP cameras, storage calculations can be
done using the ISS web System Design Tool or the IP camera vendor's storage calculator. For additional information about storage calculations please consult with the ISS Pre-
Sales Team.
• Network requirements above are generally sufficient to handle all the camera streams and up to 2 simultaneous client connections (each concurrently
displaying up to 16 cameras). For larger quantities of simultaneous client connections OR the use of a NAS storage, additional network cards might have to be
installed.
5
SECTION 3: SecurOS Video Server Specifications - ISS Analytics modules
6
1
These are standard performance options that will work well with SecurOS Auto (Low Speed), Cargo, Transit, Tracking Kit, and FaceX (Controlled Scene 1-3 people) modules.
2
These are high performance options that will work well with SecurOS Auto (High Speed), SecurOS Auto (US/Middle East), FaceX (Crowd Scene 4-10 people) or FaceX used for access control
(single factor authentication). These scenarios require a higher performance per CPU Core.
3
Can be used to offload processing of additional cameras for SecurOS Auto (US/Middle East). Two cameras can be offloaded per 1 GPU.
4
Can be used to offload video decompression of the analytics cameras to the GPU. One GPU card for 25 cameras gives a 25% performance boost (so you can increase the number of cameras
supported on the server by 25% when using 1 GPU for every 25 cameras).
5
For the SecurOS Auto - Class / Color / Make / Model module, 1 of the supported GPU cards can handle 8 cameras (1 GPU per server can be used for this module, with the remaining cameras
being processed by the CPU).
6
For SecurOS Auto Stop&Go, set the camera fps to 1 / for Auto Low Speed, set the camera fps to 15.
7
For SecurOS FaceX (Crowd), it is recommended to use 1 x NVIDIA P1000 to offload video decompression to the GPU card (1 GPU for up to 25 cameras).
8
For standard performance servers, it is recommended to use 4 memory channels for 1 CPU; for high performance servers, it is recommended to use 6 memory channels for 1 CPU.
9
When selecting CPUs for Analytics Servers, it is recommended to use CPUs that support the Intel AVX-512 instruction set.
SECTION 3 NOTES:
• If running SecurOS on a virtual machine (VM), the ratio between physical cores and vCPUs should be 1:2. So for a 8 physical core processor, 16 vCPUs should be
allocated. For more information on running SecurOS on a virtual environment, refer to Section 5 of this document.
• Cameras connected to these servers will be used specifically with the ISS Analytics modules: SecurOS Auto, Cargo, FaceX, Transit, etc…
• Using more cameras than the maximum specified in the tables above is not recommended.
• If using higher camera bitrates / resolution than specified above, please consult with an ISS Pre-Sales engineer.
• It is assumed that there will be NO local monitoring done from the video servers.
• Storage values above are sufficient for running Windows OS and the ISS software (they don't take into account video recording). For IP cameras, storage
calculations can be done using the ISS web SecurOS Design Tool or the IP camera vendor's storage calculator. For additional information about storage calculations
please consult with the ISS Pre-Sales Team.
• The data above is assuming that each camera is configured to send 1 stream to the ISS recording server.
7
SECTION 4: Windows Operating System Support
• Windows 8.1 Pro
• Windows 8.1 Enterprise
• Windows 10 Pro
• Windows 10 Enterprise
• Windows 11 Pro
• Windows 11 Pro for Workstations
• Windows Server 2012 R2 Foundation
• Windows Server 2012 R2 Essentials
• Windows Server 2012 R2 Standard
• Windows Server 2012 R2 Datacenter
• Windows Server 2016 Essentials
• Windows Server 2016 Standard
• Windows Server 2016 Datacenter
• Windows Server 2019 Essentials
• Windows Server 2019 Standard
• Windows Server 2019 Datacenter
• Windows Server 2022 Standard
• Windows Server 2022 Datacenter
* SecurOS Video Server can only be installed on a 64-bit OS. SecurOS Operator Workstation can be installed on 32-bit or 64-bit OSs.
8
SECTION 6: General Notes
• For information about server specifications for ISS analytics modules not listed in this document please contact your local ISS Pre-Sales Team.
• It is possible to run SecurOS VMS cameras and SecurOS Analytics cameras on the same server. If your project requires this type of configuration, please consult
with your local ISS Pre-Sales Team.
• All new systems are sold with SecurOS version 11.X or higher.
• Information in this document is valid for SecurOS Professional, Premium, Enterprise, and MCC.
* ISS cannot guarantee the compatibility of the SecurOS software and other 3rd party VMS software on the same server.
** If using a NAS to record video/audio from a server running SecurOS, consult with the ISS Pre-Sales team for NAS interoperability.