[SmartStruxure Solution]

SmartStruxure solution compatible

1

Architectural Guidelines 1.4

The architectural guidelines are intended to outline
important considerations that need to be taken
when designing a SmartStruxure solution.
A SmartStruxure solution has few hardcoded
limitations. Therefore, most of the
recommendations are based on tests and software
design.

Architectural summary
The strategy for the recommendations provided in
the following tables is to allow the system to
support any realistic combination within the
recommended limits without negative effect on the
total performance.

Table: Architecture
Function

Enterprise Server

Automation Server

Comment

Number of servers

125

See the Architecture

section

Number of concurrent
10
WebStation or WorkStation
connections

Enterprise Server: 2
engineering users
Automation Server: 1
engineering user

Number of concurrent
mobile connections

Function

Enterprise Server

Automation Server

Comment

Maximum number of Xenta

280/300/401 devices per
servera

100

30b

Maximum number of
LonWorks devices per
server

200

64b

LonWorks devices include

MNL devices and Xenta
100 devices

Total number of Xenta

280/300/401 devices and
LonWorks devices per
server

200

64b

Xenta 4xx I/O modules

hosted by a Xenta
280/300/401 device are not
counted as LonWorks
devices

Maximum number of NVs

on local node

400

400

Maximum number of
LonWorks networks

One local node on the

Enterprise Server

a) Xenta 280/300/401 needs to be of version 3.6 or higher. In version 3.8, a new feature improves the performance up to 500%
when reading values in StruxureWare Building Operation.
b) When using both LonWorks and BACnet MS/TP networks on the Automation Server, the network with more than 10 devices
connected is considered to be the main network. The other network then supports up to 10 devices. The main network will
support the number of devices specified in the table for the used protocol. For example, if the Automation Server has 64
LonWorks devices connected to it, the BACnet MS/TP network can support 10 devices.
Schneider Electric | Building Business
www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013

2013 Schneider Electric. All rights reserved.

Table: LonWorks

[SmartStruxure Solution]

SmartStruxure solution compatible

2

Table: Modbus
Function

Enterprise Server

Automation Server

Comment

Maximum number of RTU

slave devices

62

62

Maximum 31 devices per

COM port x 2 ports = 62
Enterprise Server: Requires
2 serial ports to be available

Maximum number of TCP

server devices

100

100

Maximum number of TCP

gateways

32

Maximum number of
2
concurrent TCP client
connections when acting as
TCP server

Maximum number of RTU

masters when acting as a
serial slave

Maximum 1 RTU master

per COM port x 2 ports = 2
Enterprise Server: Requires
2 serial ports to be available

Maximum number of
Modbus objects per server

2,500

2,500

Total number of objects for

TCP (including gateways)
and serial

Enterprise Server

Automation Server

Comment

Maximum number of
N/A
BACnet MS/TP devices per
server

50a

BACnet MS/TP devices

include b3 devices
50 user-defined objects

Maximum number of
BACnet/IP devices per
server

50

Maximum number of BBMD No practical limit known

per server

No practical limit known

Maximum number of
foreign devices per sever

64

Function

600

64

a) When using both LonWorks and BACnet MS/TP networks on the Automation Server, the network with more than 10 devices
connected is considered to be the main network. The other network then supports up to 10 devices. The main network will
support the number of devices specified in the table for the used protocol. For example, if the Automation Server has 64
LonWorks devices connected to it, the BACnet MS/TP network can support 10 devices.

Schneider Electric | Building Business

www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013

2013 Schneider Electric. All rights reserved.

Table: BACnet

[SmartStruxure Solution]

SmartStruxure solution compatible

3

Table: Trend logs

Function

Enterprise Server

Automation Server

Comment

Maximum number of
internal trend logs

2,000

1,000

Maximum number of
extended trend logs

25,000

1,500

Maximum number of
records per internal trend
log

100,000

100,000

Maximum number of
600,000
records per extended trend
log

600,000

Number of records per

implicit log

N/A

500

Maximum number of trend

log records per server

2.5 billion

3.8 million

Function

Enterprise Server

Automation Server

Comment

Maximum number of active

alarms

10,000

1,000

Maximum number of alarms 10,000

displayed in WorkStation

1,000

Maximum number of alarms 1,000

displayed in WebStation

1,000

Automation Server

Comment

Maximum number of events 200,000

10,000

Maximum number of events 6,000

displayed in WorkStation

6,000

Maximum number of events 6,000

displayed in WebStation

6,000

Built-in logs for all I/O

module points; not
changeable

Table: Alarms

Function

Enterprise Server

2013 Schneider Electric. All rights reserved.

Table: Events

Schneider Electric | Building Business

www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013

[SmartStruxure Solution]

SmartStruxure solution compatible

4

Table: Web Services

Function

Enterprise Server

Automation Server

Comment

Maximum number of
connections

Web services and

EcoStruxure Web Services

Maximum number of values No practical limit known

consumed by the server

2,000

Time to read 1000 values

3 seconds

1 second

Architectures
To be able to scale the number of Automation
Servers you can have in a system without having a
negative impact on the performance, you need to
look at the communication load and intensity
between the Automation Servers, and between the
Automation Servers and the Enterprise Server. Two
important aspects must be considered:

An Automation Server should be limited to send

values to 64 other Automation Servers. If values
need to be sent out to more than 64 Automation
Servers, the recommendation is to send the value
via other Automation Servers in a two-step
approach.

Automation Server to Automation Server

communication
Enterprise Server to Automation Server
communication

Figure: Automation Server sending values

Enterprise Server to Automation Server

communication
The Enterprise Server can send out values to a
maximum of 64 Automation Servers if the update
frequency is 10 seconds or less. If more than 64
Automation Servers are needed, the
recommendation is to send the values via other
Automation Servers in a two-step approach. If the
transfer interval is greater than 10 seconds, there is
no limitation on how many Automation Servers the
Enterprise Server can communicate with.

2013 Schneider Electric. All rights reserved.

Automation Server to Automation Server

communication
An Automation Server should be limited to receive
values from 10 other Automation Servers. This is an
important limitation and exceeding it will have
significant negative impact on the performance and
the general behavior of the system. If values need
to be received from more than 10 Automation
Servers, the recommendation is to send the value
via other Automation Servers in a two-step
approach.

Figure: Automation Server receiving values

Schneider Electric | Building Business

www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013

[SmartStruxure Solution]

SmartStruxure solution compatible

5

These two properties are the key measurement

points when monitoring the load of the Automation
Server. They need to be considered at all times,
especially when getting close to (or exceeding) the
defined limits. The properties can be trend logged
or online plotted in a standard trend chart. These
properties are not available for the Enterprise Server
because Windows Task Manager can be used
instead.

Enterprise Server communication load

In addition to the above strict limitations, the total
communication load on the Enterprise Server must
be considered. This includes events, extended
trend logs, and alarms. In systems with significant
communication load, the following
recommendations exist:
The performance of the PC is important. Use
solid-state drive, in combination with significant
RAM memory size and CPU performance.

Automation Server database

The Automation Server database has a limit of
104,000 objects. This limitation is normally more
than adequate but might be restrictive if a
significant number of LonWorks devices are used.
A trend log with thousands of records is counted as
only one object.

Install the Enterprise Server on a solid state

drive and the Enterprise Server database to a
second disk (RAID).

You can see the number of objects the database

contains in the Tree size property of the
System/Modules/RuntimeDBManager/RtDb Object
Tree object.

The size of the database impacts backup and

upgrade time. Limit the total size of the
historical database by limiting the size and
quantity of the extended trend logs.

Concurrent users
User type definitions:

Don't schedule all the reports to be generated

at the same time.

Design considerations
Load measurements
There are two server properties that are relevant for
understanding the load on the Automation Server:
Memory usage (%)
CPU usage (%)
The Memory usage (%) property measures the
current RAM memory usage. The memory usage
should never exceed 80 %. No peaks should be
seen above this limit.
The CPU usage (%) property measures the current
CPU load in the Automation Server. The CPU
usage should stay below 80 %. It is normal that the
CPU usage peaks at 100 % on occasion when
lower priority activities are performed. This peak
does not affect the overall performance.

An operator views and monitors the system

and can make changes to the system, such as
create trend logs, alarms, schedules, users,
and perform some object property changes.
An engineer also makes other changes to the
system that are typically not supported by
WebStation, such as create and change
Graphics, Function Block, and Script objects;
create devices; import and export; and backup
and restore.
The server accepts one change at a time and
queues up concurrent changes. Changes made by
an operator are quickly handled by the server and
no noticeable delay occurs when the changes
queue up. Some of the engineering changes might
take a longer time. Changes made during that time
are handled by the server when the engineering
change is finished.

2013 Schneider Electric. All rights reserved.

Figure: Enterprise Server sending values

Backup operations
Back up the system when users are not interacting
with the servers or the system. In larger systems,
the scheduled backups of the Automation Servers
are recommended to be split over time.

Schneider Electric | Building Business

www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013

[SmartStruxure Solution]

SmartStruxure solution compatible

6

Minimizing the quantity of references between

the Automation Servers.
Minimizing the transfer interval intensity of the
references between the Automation Servers.
Avoid using alarms and trend logs to monitor values
outside of the Automation Server where the alarm
or the trend log resides to minimize the quantity of
references.
Recommendations on how to minimize the transfer
interval intensity:
The transfer interval for an Automation Server to
Automation Server variable should be kept to the
longest possible time.
The transfer interval when a Function Block or
Script program input gets a value from another
Automation Server equals the program cycle time.
The transfer intervals for these values are in many
cases unnecessarily short. Create a server value so
you can change the transfer interval manually for a
program input:
Create a server value on the Automation Server
where the program resides.
Bind the server value to read the value from the
other Automation Server.
Configure the transfer interval.
Bind the server value to the program input.
If short update intervals are required, monitor the
CPU and memory usage of the Automation Server
where the value resides.

Field busses
All field busses
Do not use the change of value trend log type to
monitor a value outside of the Automation Server
where the trend log resides.
If possible, avoid having the Automation Server poll
values for alarms or trend logs from devices on a
field bus. Instead, use the capabilities of the field
bus protocol to transfer the value to the Automation
Server where the alarm or trend log resides.

LonWorks
A LonWorks device template can in rare cases
include thousands of objects. Each member of
each NV/CP is an object. When using these device
templates, there is a risk that the number of objects
the Automation Server database can support is
exceeded.
To limit unnecessary communication, bind variables
in the LonWorks devices to objects created in the
local node when the variables need to be monitored
for alarm or trend logging. Use alarms and trend
logs in the server to monitor the variables. There is
no need to bind Xenta 280/300/401 variables to the
local node, because a special event-driven protocol
is used for these devices.
BACnet
The number of BACnet objects that can reside
under the Application folder in a server has no
tested limit.
To limit unnecessary communication, create
BACnet objects in the server, and if possible, use
COV to avoid polling. Use alarms and trend logs in
the server to monitor the BACnet objects.
Modbus
Multi-read is supported, but not multi-write.
To be able to use the maximum number of Modbus
RTU devices when the Automation Server is the
master, both COM ports must be used for Modbus.
If one of these ports is used for BACnet MS/TP, the
supported number is limited to half.
Modbus only allows you to poll values, so alarms
monitoring Modbus values consume bandwidth
and will at some point affect the network
performance. To avoid this, create a server value so
you can manually change the transfer interval for an
alarm:
Create a server value on the Automation Server
where the alarm resides.
Bind the server value to read the value from the
Modbus device.
Configure the transfer interval.
Bind the server value to the alarm.

Schneider Electric | Building Business

www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013

2013 Schneider Electric. All rights reserved.

References between Automation Servers

There are two main things to consider when
optimizing the Automation Server to Automation
Server communication:

[SmartStruxure Solution]

SmartStruxure solution compatible

7

supply, the second slot for the Automation Server,

and the remaining slots are used for the I/O
modules and if needed, additional PS-24V power
supplies.

2013 Schneider Electric. All rights reserved.

I/O modules
The I/O module bus supports 32 devices. This limit
is determined by the terminal base hardware and
cannot be extended. Out of the 32 addressable
slots, the first slot is used for the PS-24V power

Schneider Electric | Building Business

www.schneider-electric.com/buildings
Trademarks and registered trademarks are the property of their respective owners.
03-14027-01-en

July 2013