This page provides general recommendations for systems hosting Info360. Systems may vary depending on specific requirements due to the volume of analytics, data frequency, historical duration, etc. and these are general recommended system configurations.
For larger systems (i.e. 500+ Sensor channels), it is recommended to install Info360 on a dedicated server separate from the database for best performance.
Minimum System Requirements
Compatible 64-bit OS:
Windows 7 Pro or later, Windows Server 2012 R2, Windows 8.x Pro or later, Windows 10 Pro, Windows Server 2016/2019
Compatible web browsers:
Google Chrome 39.0 or later, Firefox 34.0 or later
.Net Framework 4.5, Microsoft Visual C++ 2012 Redistributable - x64 v11.0.61030.0, Microsoft Visual C++ 2012 Redistributable - x86 v11.0.61030.0, ISAPI and CGI restrictions(must allow for both versions of .NET v4.0) on the root level of features of IIS, IIS 7.5 ASP, and IIS 7.5 ASP.NET (it’s a feature that you have to turn on through “Turn Windows features on or off” in Control Panel), and SQL Server (Microsoft® SQL Server® 2016.1 Express, Microsoft® SQL Server® 2016.1 Standard or later)
The following are basic recommendations per tier for the server that hosts Info360. For optimal performance, the RAM amount should be increased if the server will also host the database:
# of Channels
# of Agents
0 - 200
200 - 500
40 – 100 GB
500 - 2000
*Additional processing server recommended
For custom tier, contact Innovyze for system recommendations.
Innovyze recommends using MS SQL Server 2017 Enterprise Edition for deployment with 1000 sensors or above.
The above disk size recommendation is for general reference, and may vary depending on how far the historical data will go back and how many years will the system continue to run. The following chart describes the disk needs and statistics:
Data Rows per month (w/ sampling)
Size per Row per sensor
Size per Month per sensor
Size per Month per 100 sensors
Size per Year per 100 sensors
System Topology Diagram
The following schematic shows a sample diagram of an Info360 server and the various connected components.
Primarily the Agent of Info360 performs the reading of data from the Historian and stores the sampled data in the Info360 database in SQL Server (which can be local to the Info360 server or remote within the network).
If file-based data is used, then the Info360 DCS module is used to read the files on a routine basis.