Do not use the product(s) for any other purposes than those indicated in this
document.
Only licensed users of the product(s) and the document(s) are permitted to use this document or any
information therein. Distribution, disclosure, copying, storing or use of the product(s), information or
illustrations in this document on the part of non-licensed users, in electronic or mechanical form, as a
recording or by other means, including but not limited to, photography or information storage and
retrieval systems, without the express written permission of Schneider Electric, will be regarded as a
violation of copyright laws and is strictly prohibited.
Contents
Note
We are continuously improving our documentation. This guide
may have been updated.
Please check https://buildingsdownloads.schneider-electric.com/
home for the latest version.
After reading this guide, you should understand how to import Sigma
into Building Operation, dealing with any errors or warnings that may
occur.
1.1 Prerequisites
To be able to benefit from the contents in this guide, it is recommended
that you are familiar with the Sigma Building Management System and
Building Operation.
! Warning
Alerts you that failure to take, or avoid, a specific action might
result in physical harm to you or to the hardware.
Caution
Alerts you to possible data loss, breaches of security, or other
more serious problems.
Important
Alerts you to supplementary information that is essential to the
completion of a task.
Note
Alerts you to supplementary information.
Tip
Alerts you to supplementary information that is not essential to
the completion of the task at hand.
Advanced
Alerts you that the following information applies to complex
tasks or tasks restricted by access.
1.4 Terminology
Term Description
BMS Building Management System
DNN Distributed Network Node
IC Integration Controller
IP Internet Protocol
LAN Local Area Network
PSTN Public Switched Telephone Network
UNC Universal Network Controller
XML Extensible Markup Language
2 Systems Overview
This chapter provides a high level description of the purpose of the two
servers used during and after the transition of Sigma to Building Oper-
ation.
er tion
Manag WorkS
ta
System
Ethernet
2.2.2 Graphics
You import Sigma graphics data to a Graphics folder. After you have
successfully imported the Sigma graphics, any further graphics changes
should be made using the Building Operation TGML Editor.
2.2.3 Logging
Log Sets
After importing log sets once, you make any further changes in Work-
Station (and then send their configuration data to controllers). The log
sets in the Enterprise Server then hold the master data.
You can also create new log sets at the Log Sets folder.
Contingency Logging
You view and edit contingency logs in WorkStation.
You view contingency logging (historical logging) in WorkStation by
way of Building Operation Trend Charts and Trend Log Lists.
2.2.4 Alarms
You can choose one of the following strategies regarding routing of
alarms and system messages:
Configure the alarms and system messages to be sent to the Enter-
prise Server where they are managed using WorkStations stan-
dard facilities.
Configure the alarms and system messages to be sent to both the
Enterprise Server and the Sigma Server. You would use this strat-
egy if only some of the controllers were imported to Building
Operation (partial import).
Note
In the Sigma system, the default server provides the IP address of the
backup server (where a controllers backup data is held if required fol-
lowing a controller cold start). The Enterprise Server also provides this
service, however changes made from Building Operation are not syn-
chronized with the backup server. For this reason it is recommended
that all controllers that have backup capability (i.e. those that are
ARM7 based) are configured to perform a regular backup to flash
memory.
Table 3.1: Transition Issues to Address before Data Import to Building Operation
Table 3.1: Transition Issues to Address before Data Import to Building Operation
3.2 Preparation
Preparation of the Sigma site for data import into Building Operation
requires you to execute the actions arising from all selected transition
issues.
Depending on the actions that you wish to take, and the number of
objects and controllers at your site, you may find that it is more efficient
to combine more than one action, since doing so may save the need to
open certain dialog boxes more than once. For these reasons, you should
read Appendices 2 to 6 carefully before deciding on the order that you
want to execute any actions.
However, it is recommended that you prepare in the order suggested in
the following procedure (assuming that all of the first six issues of
Table 3.1 apply):
1 Make a backup of the C:\Sigma\Data folder.
2 Ensure that you have installed Sigma Release 4.08 and Sigma
StruxureWare Building Operation Support Release 4.08.
3 Remove any PSTN zones to leave only zones using direct IP
addressing. See Appendix 2.
4 Copy all long texts as separate documents and (later) attach them
to the imported Sigma objects in Building Operation. See Appen-
dix 3.
5 Merge all log sets where configured on multiple servers. See
Appendix 4.
6 Remove all but one Sigma Server. See Appendix 5.
7 Disable all Sigma dual LANs and send the Node Configurations to
the appropriate routers and controllers. See Appendix 6.
8 Make a separate backup of the C:\Sigma\Data folder.
4 Transition
This chapter explains the steps involved in the transition of Sigma to
Building Operation. For further information on all steps involving oper-
ations in WorkStation, see the Building Operation WebHelp. For fur-
ther information on all steps involving Sigma, see the Sigma Online
Help.
The recommended procedure is:
1 For Sigma controllers on different subnets to the Enterprise
Server, configure persistent routes to access those controllers
using the Route command in a Command Prompt window.
2 In Sigma System Setup, in the Networks and Devices/Servers
folder, add and configure the Enterprise Server.
3 In WorkStation, create users to match the Sigma users.
4 Create a Sigma Interface and configure the Import host property
only.
5 Right-click the Sigma Interface and select Data import.
6 If the Data Import dialog box displays There were errors dur-
ing conversion. Continue?, click No.
7 Review all of the warnings and errors and resolve them. You can
resolve most warnings and errors by making changes in Sigma.
See Appendix 1.
8 Repeat Step 5 to Step 7 until no further conversion warnings or
errors occur, or that those occurring are acceptable.
Notes
A graphics data import operates sequentially on all of the
.swc files in the C:\Sigma\Data\Graphics\Drawings folder
(and sub-folders). Depending on the size of your Sigma sys-
tem, this could take many hours (at the rate of approximately
5 to 10 files per minute). However, you could consider
importing in smaller batches by temporarily removing
selected .swc files from the C:\Sigma\Data\Graph-
ics\Drawings folder and copying them back into the folder
when required for import.
After the initial graphics data import is complete, you can
right-click any imported graphic and re-import that graphic
alone.
Note
If you have done a partial data import (i.e. specific control-
lers only) to the Sigma Interface, set the Discard alarms
from unknown devices advanced property to True. This
ensures that the Enterprise Server ignores alarms intended
for Sigma (but remember to set the property back to False
after you have completed the Sigma transition to Building
Operation.)
Failed to convert command (piece- Piecewise command has Ensure that the shape with
wise): No scheme defined. Ignoring been added to a non- the Piecewise command is
(For Shape) scheme shape. part of a scheme.
Ignoring unsupported state test in Feed- Either alarm state or rea- Reconfigure Feedback
Back -1 (For Shape) son for state is not found command or relevant
in state list. object.
Color command not supported on a Shape that the command is Ignore.
shape with no color. on is transparent.
Ignoring chain to self. Chain command refers to Ignore.
itself.
Alarm State Alarm State name not The specified Alarm State Reconfigure Feedback/
supported is not supported. Condition command.
(Feedback and Condition commands)
RFS state Reason not supported The specified Reason for Reconfigure Feedback/
State is not supported. Condition command.
(Feedback and Condition commands)
Brush style Style name not supported Sigma line style not sup- Reconfigure shape with a
ported. supported line style.
Removing text command from non text Text command does not None.
shape. (For Shape) work on shapes.
Removing angle command on invalid Invalid variable for the None.
variable. (For Shape) command.
Removing animate command on invalid Invalid shape for the com- None.
shape. mand. Animate command
only works on rectangles
and ellipses.
Removing bar command on invalid Invalid shape for the com- None.
shape mand. Bar command only
works on rectangles and
ellipses.
2 In the main Sigma network zone folder, identify any routers and
modems that provide communication with the remote network.
3 In each remote zone folder, identify all the controllers, routers and
networks that are configured to connect to the main Sigma net-
work via PSTN.
4 Disconnect each modem from the PSTN and from the associated
controller or router.
5 Connect each disconnected controller or router to an Ethernet
socket via Cat 5/6 Ethernet cable.
6 Select the main Sigma network, and on it create all the routers and
controllers that exist in each PSTN zone that you want to replace.
Configure each router or controller with all the same properties as
in the redundant PSTN zone, except that (where appropriate):
a For Modem Type, select None instead of selecting a
modem.
b For Network, select the (main) network onto which you are
recreating the replacement routers and controllers.
7 Delete all redundant modems and DNNs.
8 Delete all redundant PSTN zones.
3 In the Long Texts dialog box, select the first long text and then
select Edit.
4 Copy the highlighted text (Ctrl+C) and then paste it into a suitable
file, for example a text file (.txt).
5 Save the .txt file into the folder that you created in Step 1. Ensure
that you type a name that you can associate with an alarm later.
6 Repeat the three previous steps for all the remaining long text
files.
7 In the WorkStation System Tree pane, create a new folder as a
repository for all long text files.
Note
You will not be able to create a new folder within the Sigma Interface
structure; you must do this under the Enterprise Server.
8 Select all the .txt files in the networked folder, and drag them to
the folder that you created in the previous step.
9 In the System Tree pane, select each alarm (child) object where
you want associated long text, and:
a Click the Attachment tab.
b Click the ( ) button and navigate to the long text file that
you want to associate with the alarm object.
10 Each time you want to view a long text attachment, click the
( ) button.
Caution
If merging substantial log sets, consider the effect of the com-
bined volume of data input to the Enterprise Server. You can
monitor the Data Buffers tab in the Node Statistics properties
for each controller as an indication of the increased data rate.
Proceed as follows:
1 Open a client of each of the servers A and B, and ensure that the
clients are adjacent to each other so that you can move easily from
one client to the other.
2 In the System Manager at each Sigma client, on the Logging
menu, select Historical Setup.
4 Make a note of all objects that are being logged in the selected log
set:
5 At the Server B client, create a new log set and click Edit.
6 Drag the same objects that you noted in Step 4 from the object
index into the Logging Objects box.
Note
This procedure assumes that the object index is identical in
both servers.
7 While still on the Objects tab, ensure that all other properties for
the newly created log set in Server B are the same as those in the
log set you opened in Server A.
8 Open the Data, Controller and Reference tabs in turn in both cli-
ents, and ensure that all properties for the newly created log set in
Server B are the same as those in the log set you opened in Server
A.
9 Repeat Step 3 to Step 8 for all remaining log sets in Server A.
Note
When configuring the client to the Building Operation
Enterprise Server, select the Enterprise Server, not the
Sigma Server.
Note
You will not be able to delete any servers until you have
deselected all clients to those servers.
5 Expand the Routers folder. For each router, in the Default Server
box, enter the number of the Sigma Server noted in Step 1.
6 Expand the Servers folder. Delete all servers except the one that
you intend to keep as the Sigma Server.
5 Expand the Servers folder, and for each server with dual network-
ing, deselect the Dual LAN box.
6 Expand the Routers folder, and for each router with dual network-
ing, deselect the Dual LAN box.
www.schneider-electric.com/buildings