Site Director limitations and recommendations - Metasys - LIT-12011832 - General System Information - Metasys System

The following tables describe performance guidelines and limitations of the Metasys system Site Directors.

Note: Upgrade the Site Director to Metasys Release 12.0 to take advantage of encrypted communications. For best performance also upgrade the network engines to the newer release. Network engines at Release 5.2 or later function with Release 12.0, but to ensure best performance, upgrade engines to newer versions as soon as it is practical.

Table 1. Engine Site Director limitations and recommendations
Maximum allowed	Type of Site Director
Maximum allowed	NAE35 SNE1050x	NAE45 SNE1100x	NAE55 SNE2200x	NAE85	NCE25 SNC replacements of NCE25 ¹
Total engines	3	3	4	4	1 ²
Simultaneous SMP users	2	2	4	10	2
Objects in device ³	2,500	2,500	5,000	25,000	2,500
Objects within a single folder	300	300	700	700	300
Dynamic values per graphics	100
Results displayed in a global search	500
Languages	1
Objects in entire system	3 million/ 750k (for ADX Site Director Only)
Characters in the name of an object	400
Characters in the description of an object	64
Nesting levels for object creation	7
Extensions per object	10
Sets for third-party BACnet states text	1,000
Characters for a third-party BACnet states text	60
Members for a multi-value third-party BACnet states text	500
Non-Simultaneous SMP users	Limited only by memory capacity
SMP user views	Limited only by memory capacity
Simultaneous browsers per client computer	2 (Mix of online, SCT, and Simulation)
DLLR load extension	Limited only by memory capacity. If you plan to attach a large number of load extensions to a single DLLR object, consider the memory limitation. For load extensions attached to one DLLR object, there is a 64 KB text limit for the list of the Loads fully qualified references. Load Limit = (64 x 1024)/average number of characters per load. 1024 Bytes equals 1 KB. For example, if your DLLR object is configured with Loads that have fully qualified references that average 100 characters (including dots) in length, then you can support approximately 650 loads (64 x 1024/100) for that DLLR. If you reach the memory limit, you may need to combine loads. For example, if a site has multiple physical meters, split the meters across multiple controllers and apply appropriate DLLR loads, if possible. Otherwise, use Interlock or Multiple Command objects to reduce the number of loads added to the DLLR.
DLLR objects	Limited only by memory capacity.

Table 2. Server Site Director limitations and recommendations
Maximum allowed	Type of Site Director
Maximum allowed	ADS Desktop	ADS-Lite-E ⁴	ADS-Lite-A ⁵	ADX	OAS
Total engines	14 ⁶	5 ⁷	4 ⁸	1,000 ⁹	OASMIN: 0 OASSTD: up to 2
Simultaneous SMP users	5	5	5	10/25/ 50/100 ¹⁰	5
Dynamic values per graphics	100
Results displayed in a global search	2,000
Languages	18
Objects in entire system	3 million/ 750k (for ADX Site Director Only)
Objects in device ¹¹	Limited by SQL Server storage capacity
Objects within a single folder	700
Characters in the name of an object	400
Characters in the description of an object	64
Nesting levels for object creation	7
Extensions per object	10
Sets for third-party BACnet states text	1,000
Characters for a third-party BACnet states text	60
Members for a multi-value third-party BACnet states text	500
Non-Simultaneous SMP users	Limited only by memory capacity
SMP user views	Limited only by memory capacity
Simultaneous browsers per client computer	2 (Mix of online, SCT, and Simulation)
DLLR load extension	Limited only by memory capacity. If you plan to attach a large number of load extensions to a single DLLR object, consider the memory limitation. For load extensions attached to one DLLR object, there is a 64 KB text limit for the list of the Loads fully qualified references. Load Limit = (64 x 1024)/average number of characters per load. 1024 Bytes equals 1 KB. For example, if your DLLR object is configured with Loads that have fully qualified references that average 100 characters (including dots) in length, then you can support approximately 650 loads (64 x 1024/100) for that DLLR. If you reach the memory limit, you may need to combine loads. For example, if a site has multiple physical meters, split the meters across multiple controllers and apply appropriate DLLR loads, if possible. Otherwise, use Interlock or Multiple Command objects to reduce the number of loads added to the DLLR.
DLLR objects	Limited only by memory capacity.

Table 3. Maximum number of users supported on Metasys Server type Site Directors
Type of Metasys Server	Computer supported platform		Site Management Portal (SMP) Users (up to)	Metasys UI Users (up to)
Type of Metasys Server	Desktop	Server	Site Management Portal (SMP) Users (up to)	Metasys UI Users (up to)
ADS05U	Yes	-	5	5
OASSTD	Yes ¹²	Yes ¹³	5	5
OASMIN	Yes¹²	Yes¹³	5	5
ADX10U	-	Yes	10	25
ADX25U	-	Yes	25	25
ADX50U	-	Yes	50	50
ADX100U ¹⁴	-	Yes	100	50

Table 4. Maximum number of network engines supported based on Metasys Server type and Server size
Site Director with maximum users	1 to 14 engines	1 to 25 engines	1 to 50 engines	1 to 100 engines	1 to 300 engines	1 to 1,000 engines
ADS05U	ADS
ADX10U		Small ADX	Medium ADX	Medium/Large ADX	Large/Extra Large ADX	Extra Large ADX
ADX25U		Small ADX	Medium ADX	Medium/Large ADX
ADX50U				Medium/Large ADX
ADX100U				Medium/Large ADX
For ADS/ADX computer hardware requirements, refer to the Technical Specifications section of this document: For Unified ADS refer to Application and Data Server (ADS) system requirements. For small and small to medium Unified ADX refer to Extended Application and Data Server system requirements (Unified 10 or 25 User ADX). For medium to large Split ADX refer to Extended Application and Data Server system requirements (Split 10 or 25 User ADX). For medium to large and large Unified ADX refer to Extended Application and Data Server system requirements (Unified 50 or 100 User ADX). For large to extra large and extra large Split ADX refer to Extended Application and Data Server system requirements (Split 50 or 100 User ADX).

¹ SNC2515x-0xx, SNC2515x-04x, SNC1612x-0xx, and SNC1612x-04x.

² An NCE25 or SNC can only act as Site Director for itself.

³ Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and interlocks.

⁴ The ADS-Lite-E cannot host servers.

⁵ The ADS-Lite-A cannot host servers.

⁶ Varies with concurrent connection.

⁷ Supports up to five of the following: SNE1100x, SNE1050x, SNC2515x-0xx, SNC2515x-04x, SNC1612x-0xx, SNC1612x-04x, NAE35, NAE45, NCE25, NIE29, NIE39, and NIE49.

⁸ Supports up to 3 NAE-Lite units plus up to 1 SNE110Lx, NIE29, NIE39, and NIE49.

⁹ Depends on computer hardware. See the table Maximum number of network engines supported based on Metasys Server type and Server size for more information.

¹⁰ Depends on version of ADX.

¹¹ Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and interlocks.

¹² Virtual Machine or Turnkey only.

¹³ Virtual Machine only.

¹⁴ Metasys for Validated Environments does not support the 100 user ADX.

Site Director limitations and recommendations - Metasys - LIT-12011832 - General System Information - Metasys System - 12.0

Metasys System Configuration Guide