Sigma v4.08 (3.46.80) To StruxureWare Building Operation v1.6 Transition Guide

Satchwell Sigma
Sigma to Building Operation Transition Guide

Copyright Notice
We at Schneider Electric have tried to make the information contained in this
document as accurate and reliable as possible. Nevertheless, Schneider Electric
disclaims any warranty of any kind, whether express or implied, as to any matter
whatsoever relating to this document, including without limitation the
merchantability or fitness for any particular purpose. Schneider Electric will, from
time to time, revise the product(s) described in this document and reserves the
right to make such changes without obligation to notify the purchaser. In no event
shall Schneider Electric be liable for any indirect, special, incidental or
consequential damages arising out of purchase or use of this document or the
information contained herein.
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.
Copyright 2014 Schneider Electric

All brand names, trademarks and registered trademarks
are the property of their respective owners. Information
contained within this document is subject to change
without notice. All rights reserved. www.schneider-electric.com/buildings
Contents
1 About this Guide 5

1.1 Prerequisites ............................................................................................................... 5
1.2 Acrobat (PDF) Conventions....................................................................................... 5
1.3 Typographic Conventions .......................................................................................... 6
1.4 Terminology ............................................................................................................... 7
2 Systems Overview 9
2.1 Server Architecture .................................................................................................... 9
2.2 Enterprise Server ........................................................................................................ 10
2.2.1 Controllers, Objects and Segments ......................................................................... 10
2.2.2 Graphics .................................................................................................................. 10
2.2.3 Logging ................................................................................................................... 10
2.2.4 Alarms ..................................................................................................................... 10
2.2.5 Day-to day Configuration Changes......................................................................... 11
2.2.6 Default Server ......................................................................................................... 11
2.3 Sigma Server .............................................................................................................. 12
2.3.1 Core Configuration Changes................................................................................... 12
2.3.2 Backup Server ......................................................................................................... 12
3 Review and Preparation 13
3.1 Transition Issues......................................................................................................... 13
3.2 Preparation ................................................................................................................. 16
4 Transition 17
Appendix 1 - Warning and Error Messages 21
1.1 Data Import Conversion Warning Messages ............................................................. 22
1.2 Data Import Conversion Error Messages ................................................................... 24
1.3 Programmable Object Warning Messages ................................................................. 25
1.3.1 Impact on Graphics ................................................................................................. 26
1.3.2 Impact on Text Reports ........................................................................................... 27
1.3.3 Impact on Programmable Object Properties ........................................................... 27
1.3.4 Manual Override ..................................................................................................... 27
1.4 Graphics Data Import Conversion Failed Message ................................................... 28
1.5 Graphics Error Messages in the Trace File ................................................................ 28
Appendix 2 - Remove PSTN Zones 31
Appendix 3 - Prepare Long Text 33
Appendix 4 - Merge Log Sets 37
Appendix 5 - Decommission Sigma Servers 41
Appendix 6 - Disable Dual LANs 45
Schneider Electric, Dec 2014 3 (48)

4 (48) Schneider Electric, Dec 2014

Sigma to Building Operation Transition Guide 1 About this Guide
1 About this Guide

This guide explains how to import a Sigma building management sys-
tem to Building Operation. The information contained within this guide
applies to Sigma Release 4.08 and Building Operation Version 1.6.
For information about Building Operation, refer to the Building Opera-
tion WebHelp.
For information on third party products, we refer you to the instructions
delivered with the third party product.
If you discover errors and/or unclear descriptions in this guide, please
contact your Schneider Electric representative.
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.
1.2 Acrobat (PDF) Conventions

If reading this guide online in Adobe Acrobat Reader (.PDF file for-
mat), numerous hypertext links exist for all entries in the Table of Con-
tents, and other standard cross references. These links are indicated
when the cursor changes to a hand with a pointing finger.

1 About this Guide Sigma to Building Operation Transition Guide
1.3 Typographic Conventions

The following conventions are used in this guide:
Bold is used for option names.
Italics are used for references to external manuals.
In addition, the following specially marked texts may occur throughout
the guide:
! 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.

Sigma to Building Operation Transition Guide 1 About this Guide
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

1 About this Guide Sigma to Building Operation Transition Guide

Sigma to Building Operation Transition Guide 2 Systems Overview
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.
2.1 Server Architecture

The server architecture (see Fig. 2.1) provides:
A Sigma Server. This server allows you to make core configura-
tion changes.
An Enterprise Server, acting as a server for the Sigma network and
devices after the transition.
Sigma Server Enterprise Server
er tion
Manag WorkS
ta
System
Sigma programming data Data Imports:

Controllers and Objects
Graphics
Log Sets
Ethernet
Sigma Server PC Enterprise Server PC Sigma Network
Fig. 2.1: Server Architecture

2 Systems Overview Sigma to Building Operation Transition Guide
2.2 Enterprise Server

The Enterprise Server provides day-to-day operation and enables you to
make selected configuration changes. It receives alarms and handles all
logging.
2.2.1 Controllers, Objects and Segments

After you have imported controller, object and segment data, you can
view the data in WorkStation. You can only make changes to core
Sigma data at the Sigma Server.
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).

Sigma to Building Operation Transition Guide 2 Systems Overview
2.2.5 Day-to day Configuration Changes

Day-to day configuration changes should be made in WorkStation and
these cover:
Object overrides (Force).
Various secondary properties covering Short Form Edit.
Time Extensions.
2.2.6 Default Server

You configure the Enterprise Server as the default server for all routers
and controllers. The default server is the destination for:
Sigma System Messages (priorities 26 and 27). System messages
indicate issues with the Sigma system rather than issues with the
monitored plant.
Undeliverable alarms. Sigma controllers use the default server as
the destination for any alarms (and logs) that cannot be delivered
to their configured destination.
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.

2 Systems Overview Sigma to Building Operation Transition Guide
2.3 Sigma Server

The Sigma Server is the master for controller and network configura-
tion. It also contains the master controller backup data (point files).
Almost all day-to-day functions move from the Sigma Server to the
Enterprise Server (although they are still available in Sigma). In gen-
eral, do not use these day-to-day functions at the Sigma Server, to avoid
conflict in the configuration of the system as a whole.
The functions that remain in use at the Sigma Server are:
Core configuration changes.
Backup server.
2.3.1 Core Configuration Changes

The Sigma Server holds the master data and is where you make major
configuration changes. Following changes, you import Sigma itera-
tively at the Enterprise Server. This covers all controllers and network
configuration as well as object configuration (with the exception of
Short Form Edit and Time Extension).
2.3.2 Backup Server

The Sigma Server is the backup server for all controllers and provides:
The master copy of the Sigma configuration data.
Database alignment, which should be enabled to update the master
copy of the Sigma configuration data with the latest controller run-
time data (for example, totalized values).
Controller cold-start service (refresh of a controller configuration
database). The preferred cold-start service is provided by the con-
troller (from flash backup). However, in the event of a controller
replacement, only the Sigma backup server can compile and trans-
mit the configuration data (from the master copy) to the new con-
troller.

Sigma to Building Operation Transition Guide 3 Review and Preparation
3 Review and Preparation

Transition from Sigma to Building Operation is achieved in two phases:
Review and preparation stage (this chapter), where you plan and
make changes to Sigma before starting work in Building Opera-
tion.
Transition stage, where you import Sigma controller data into
Building Operation, resolve any warnings and errors, and then
import log sets, graphics and alarms. Errors are typically resolved
at a Sigma client.
3.1 Transition Issues

Table 3.1 lists the transition issues and where necessary, a summary of
the action that you may need to take in Sigma before importing Sigma
data into Building Operation.
Review the issues in the following table and decide which of them are
relevant to your site. For all except the first five issues, action is not pos-
sible except for you to inform the customer of the issue or of the Build-
ing Operation alternative.
When you have decided on the action required, see Section 3.2, Prep-
aration.

3 Review and Preparation Sigma to Building Operation Transition Guide
Table 3.1: Transition Issues to Address before Data Import to Building Operation
Issue Alternative Action

Controllers in zones con- None. Autodialled control- Move all Autodial controllers to a sin-
nected by Autodial. lers and their objects are not gle network using IP addressing. See
imported. Appendix 2.
Sigma long texts. None. Long text is not Re-create each Sigma long text as a
transferred. document and attach to relevant Build-
ing Operation object. See Appendix 3.
Multiple server logging. None. Architecture man- Where logging is performed across
dates one Sigma Server. multiple servers, merge log sets to
achieve a single file. See Appendix 4.
Multiple Sigma Servers. None. Architecture man- Decommission additional Sigma Serv-
dates only one Enterprise ers. See Appendix 5.
Server and one Sigma
Server.
Sigma dual LANs. None. Dual LANs Disable Sigma dual LANs. See
adversely affect system per- Appendix 6.
formance.
The order of segments and The order of segments and None. See Building Operation Web-
objects is configurable. objects is alphabetic. Help.
Mnemonic display of None. Sigma mnemonics None.
objects and segments. are removed on data
import.
Configurable System Man- Status bar, properties pane, None. See Building Operation Web-
ager status bar. alarm grouping and filter- Help.
ing.
Dynaview. Trend charts None. See Building Operation Web-
Help.
User-configurable context None. Menus are not con- None.
menu commands. verted.
Preamble text that is part of None. None.
variable Short Texts (e.g.
Temp).
Object status (logged, con- None. None.
tingency logging, database
align or in alarm) not indi-
cated in Segments folders).
System Manager Object List View Quick Filter. None. See Building Operation Web-
Types filter. Help.

Sigma to Building Operation Transition Guide 3 Review and Preparation
Table 3.1: Transition Issues to Address before Data Import to Building Operation
Issue Alternative Action

Alarm Extractions. Alarm/event grouping and None. See Building Operation Web-
filtering facilities Help.
Extended display parame- None. None.
ters in the System Manager
main pane.
Remote Alarm Manager. Building Operation can None. See Building Operation Web-
deliver alarms to e-mail Help for alarm management.
addresses.
Advanced Toolkit option. None. None.
Active Psychrometric Chart None. None.
option.
Flexima option. Web Reports and Web Ser- None. See Building Operation Web-
vices. Help.
Sigma graphics support pat- Pattern fills are replaced by None.
tern fills. gradient fills.
Routines. Plain English scripting. None. See Building Operation Web-
Help.
Scheduled actions. None. None.
Alarm information when None. A user is required to None. User logs on to Building Opera-
there is no one logged on. log on. tion. See Building Operation Web-
Help.
Alarm Banner. Alarm icon in notification None. See Building Operation Web-
area. Help.
Online monitoring of third None. None.
party devices such as PCs.
Alarm and Report log sets. None. None.
Routesets. One route is required to the Set up a persistent route.
Enterprise Server.
Live Printing. None. None.
Group retiming of control- None. None.
lers to non-server time/date.
Storage of the alarm limit Add Sigma event type None.
threshold in the event data- column to Alarms pane or
base. enable Details view.

3 Review and Preparation Sigma to Building Operation Transition Guide
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.

Sigma to Building Operation Transition Guide 4 Transition
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.
9 Configure the Server number, IP address, and Subnet mask

properties of the Sigma Interface (note: if there are no DNNs in
the network, change the Maximum concurrent checks property
from its default of 1 to 10). Refer to the Building Operation Web-
Help.
10 Select an object in the Controllers folder and check that it is read-
ing valid data from the Sigma controller.
11 Right-click the Graphics folder and select Data import.

4 Transition Sigma to Building Operation Transition Guide
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.
12 Right-click the Log Sets folder and select Data import.

13 In Sigma System Setup, via the Networks and Devices folder,
configure the Enterprise Server to be the default server for all rout-
ers and controllers.
14 In WorkStation, create a Workspace and assign it to a user group.
15 Log on to Building Operation as a member of the user group to
which the Workspace is assigned.
16 Set up alarm filters (for example, Critical, General, and System
alarms) to match the alarm filters set up in your Sigma system. See
the WebHelp topic Alarms Pane and Alarm View Customiza-
tion.
17 Create a new Panel. Within the panel, create a Graphics pane, and
then select an imported graphic to be the main (welcome) graphic
that will be displayed when you log on to WorkStation. Customize
the size of the panel using the Edit Layout command from the
Actions menu. Save your changes.
18 Save the Workspace.

Sigma to Building Operation Transition Guide 4 Transition
19 In the Controller Items\Routesets folder, configure all routesets

so that alarms are routed to the Enterprise Server or to the Sigma
Server (or both) as required.
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.)
20 In Sigma System Diagnostics:

a Select Node, and for all transitioned routers and controllers,
via the Options menu, select Download Node Configura-
tion.
b Select Controllers, and for all transitioned controllers, via the
Options menu, select Download Files and send Alarm Rout-
ing (Routeset.rec) and IP Address Translation (Att.set). Verify
that alarms are arriving at the expected server(s).
21 In Sigma System Setup, via the Networks and Devices folder,
select your Sigma network folder, and on the Device Monitor tab,
set the Monitoring Server to None.
22 In WorkStation, send all logs sets to controllers.
23 Make a backup of the C:\Sigma\Data folder.

4 Transition Sigma to Building Operation Transition Guide

Appendix 1 - Warning and Error Messages

This appendix provides information relating to warnings and errors gen-
erated when you are importing Sigma data to Building Operation.
When you initiate a data import, some of the following types of message
may be generated:
Conversion warnings - details of minor issues arising before the
actual data import at the Sigma Interface object (or if relevant, at
the Log Sets folder object). If there are then no conversion errors,
the data import process continues to completion. These warnings
are generated in the Data Import dialog box.
Conversion errors - details of conversion errors arising before the
data import at the Sigma Interface object. These messages are gen-
erated in the Data Import dialog box. After examining the error
messages, you decide either to proceed with, or to cancel the data
import. Conversion errors are more serious than conversion warn-
ings and should be addressed.
Graphics conversion failed message - occurs when a graphic
import process encounters a large graphic and its converted size is
larger the configured maximum size. This message is generated in
the Data Import dialog box.
Graphics conversion error messages - shown in the data import
trace file after a data import at the Graphics folder object (unless
the conversion fails completely, in which case the message is dis-
played in the Data Import dialog box).
Table 1.1 to Table 1.5 contain messages displayed in the Data Import
dialog box and in the trace file (for graphics imports).

1.1 Data Import Conversion Warning Messages

Table 1.1 shows some typical conversion warning types and
causes, and the action you might take to remove/resolve them
before re-importing.
Table 1.1: Data Import Conversion Warnings
Example Cause Action

Modem found. Ignoring controller: 'Controller Building Operation Re-engineer zones to
name'. Zone name: 'Zone name' does not support dial- use IP addressing. See
up (PSTN) zones. Appendix 2.
PSTN not supported in port config for port Port Building Operation Either ignore or recon-
number does not support figure port in Node tab.
PSTN.
Not converting network type 19K2 for name Serial (PPP) config- Ignore.
ured for a controller.
Ignoring BAS node 'BAS x32' Device number: n Building Operation Upgrade all BAS con-
does not support BAS trollers to Sigma.
and ignores BAS
devices.
Programmable object is returning short text in Multiple return state-
Either accept the warn-
addition to returning a string. Conversion will be ments in the Pro-
ing or revise the object
approximate. Object name a (Unc, Obj)b grammable object.
in Sigma. See Table 1.3
See Table 1.3 for
for details.
details.
Unable to determine units for optimiser as space
Space temp object Configure space temp
temp object is not set (Unc, Obj). Defaulting to
not configured. object.
short text n
Unable to determine units for optimiser due to Input object not of Ignore.
type of space temp object. Type is: 44 (Unc, the expected type.
Obj). Type. Defaulting to short text n
Unable to determine units for optimizer as space Incorrect Space temp
Configure space temp
temp object data not obtainable (Unc, Obj). object reference.
object reference.
Defaulting to short text n
Removed invalid character in mnemonic Mne- Control characters None.
monic not supported and
were removed.

Table 1.1: Data Import Conversion Warnings

Converting object title from Object name to
Object name 2 to make it unique in the segment Identical object or Either accept that
Segment name Previous entry causes duplicate. segment titles in a duplicates will be
segment are not sup- renamed, or rename
Converting segment title from 'Segment name' to ported; duplicates are them in Sigma before
Segment name 2 to make it unique in the seg- renamed. import.
ment Segment name
Ignoring unsupported logset type Logset type Only Change of Ignore.
name. Log Set name Log Set name Value and Interval
log sets are sup-
ported.
a. Messages are generalized.
b. Unc = Controller number, Obj = Object number.

1.2 Data Import Conversion Error Messages

Table 1.2 shows some typical conversion error types and causes, and
the action you might take to remove/resolve them before re-importing.
Table 1.2: Data Import Conversion Errors

Unable to find equivalent for unit 'unit' Data importer cannot Ensure that the file
in C:\Sigma\Data\ XmlExport\units.txt. find a mapping for a C:\Sigma\Data\XmlEx-
Property name 'Property'. Object (Unc, Sigma short text value. port\units.txt contains a mapping
Obj)a. Short text number: n. for the short text value, using one
or both of the following solu-
tions:
Add a new short text map-
ping to the units.txt file.
Modify (in Sigma) all
instances of the short text
(identified in the warning
message) to match an exist-
ing mapping. Refer to
instructions contained in the
units.txt file.
Problem finding unit: Not a valid unit: Data importer cannot Ensure that the mapping for the
find a valid Building short text value in
Operation unit for a C:\Sigma\Data\XmlEx-
particular short text port\units.txt contains a valid
mapping. unit that Building Operation can
use. Refer to instructions con-
tained in the units.txt file.
Index entry to point that does not exist Sigma index entry has Resolve with SigmaX.
in point file. Shortcut not created. no corresponding
Object nameb (Unc, Obj) object in the Sigma
point file.
Object has no slot configured. Ignoring Slot in the (x96) con- Assign the slot in the Sigma x96
Mnemonic (Obj - Object name) troller not configured. controller.
Optimiser has linear and logarithmic Linear and Logarith- Reconfigure optimiser as either
settings. Conversion will not be correct. mic operation not sup- linear or logarithmic, not both.
Object name (Unc, Obj) ported for the same
object.
Backup terminal can't be zero for The Backup Server is Configure the Backup Server
Device name. Device number not configured for the number in Sigma System Setup.
Device number specified controller.

Table 1.2: Data Import Conversion Errors

Object type mismatch problem between Object database cor- Resolve with SigmaX.
index.rec and pntfle.rec Type should ruption.
be equal to Type for Object name
(Unc, Obj)
Checking control object stage, failed to Object database cor- Resolve with SigmaX.
find object (Unc, Obj) ruption.
Reference object item for missing Object not found in Recreate object or configure the
object/controller (Unc, Obj) in logset the index, possibly log set.
logset name deleted.
Ignoring logset item for missing object/ Object not found in Recreate object or configure the
controller (Unc, Obj) in logset logset the index, possibly log set.
name deleted.
a. Unc = Controller number, Obj = Object number.
b. Messages are generalized.
1.3 Programmable Object Warning Messages

A property in Building Operation can either display a string, an enumer-
ation of strings or a numeric value. In Sigma, the RETURN value for a
programmable object can be any of three types (see Items 1 to 3 in
Table 1.3) depending on which RETURN statement is executed. Each
RETURN type provides a different type of programmable object in
Building Operation after a data import.
However, if more than one return statement type exists in a programma-
ble object in Sigma, the conversion program can only select one of the
three types of RETURN statement, forcing the conversion of only one
type of programmable object. A conversion warning is displayed each
time multiple RETURN statements are encountered, before you can
proceed with the data import.
Items 4, 5, 6, and 7 show the type of programmable object that is created
in Building Operation for each possible multiple return statement com-
bination. In item 4, for example, a programmable analog object will
always be created, and the returned short text value will be numeric
rather than a text string.

The information provided in the message enables you to identify the

object. You can then decide whether to modify the program to resolve
the conversion warning.
Table 1.3: Programmable Object Return Statements
Item Return Statement Conversion Warning

1 RETURN abc Programmable string None.
object, Value = string.
2 RETURN VIA Programmable analog None.
TEXT NNN VALUE object, Value = float-
nnn.nn ing point number.
3 RETURN TRUE/ Programmable enu- None.
FALSE or RETURN merated object, Value
TEXT 61 = strings from short
text table (where
used).
4 Return statements 1 Programmable analog Programmable object has RETURN VIA
and 2 in combination object. in addition to returning a string. Conver-
sion will be approximate. Object namea
(Unc, Obj)b
5 Return statements 1 Programmable enu- Programmable object is returning short
and 3 in combination merated object. text in addition to returning a string. Con-
version will be approximate. Object
name (Unc, Obj)
6 Return statements 2 Programmable analog Programmable object has RETURN VIA
and 3 in combination object. in addition to returning other short text.
Conversion will be approximate. Object
name (Unc, Obj)
7 Return statements 1, Programmable analog Programmable object is returning short
2, and 3 in combina- object. text in addition to returning a string. Con-
tion version will be approximate. Object
name (Unc, Obj)
a. Messages are generalized.
b. Unc = Controller number, Obj = Object number.
1.3.1 Impact on Graphics

When a graphic displays the primary short text value of a programmable
object, only one kind of return statement has an impact on what is dis-
played. For the combination of return statements shown in item 4 of
Table 1.3, for example, the graphic will only display a numeric value
because the programmable object is an analog type. The return state-
ment that has a string value (e.g. RETURN abc) will therefore never
affect the graphic.

Similarly, the combination of return statements shown in item 5 will

never cause the display of the string value in a graphic; only enumerated
short text strings will be shown because the short text Return statement
(e.g. RETURN TEXT 61) will always be selected for this combination.
1.3.2 Impact on Text Reports

When you create a text report, the following occurs:
Item 4: if a short text number is returned, the RETURN VIA result
is displayed, otherwise, the string value is displayed.
Item 5: if a short text number is returned, the RETURN TEXT
result is displayed, otherwise, the string value is displayed.
Item 6: the numeric value is always shown. If the RETURN TEXT
statement is executed, the resulting display will show 100 or 0
depending on the current status of the object. This is determined
by the optional true/false parameter. If true/false is omitted, the
parameter defaults to false, which has a value of 0.
Item 7: This is a combination of the previous items. Only the
numeric value will be displayed (unless there is no short text, in
which case the string value will be shown).
1.3.3 Impact on Programmable Object Properties

When you select the Basic tab for a programmable object, the Type
property (in the General Information group) states which type of pro-
grammable object has been converted, i.e. one of:
Programmable analog
Programmable string
Programmable enumerated
1.3.4 Manual Override

If the programmable object is manually set to on or off, Sigma will dis-
play the short texts 460 or 461 (which have default text values of on
or off). In Building Operation, this only works well for the enumerated
programmable object type, where the text on or off will be displayed
correctly.

1.4 Graphics Data Import Conversion Failed Message

Table 1.4 shows the error message that occurs when a graphic conver-
sion exceeds the configured maximum size.
Table 1.4: Graphics Import Error Messages
Conversion Failed Message Cause Action Required

Conversion failed: Converted Sigma graphic conversion has Increase the size limit speci-
graphic exceeded maximum size created a graphic that is larger fied in the Graphics folder
than the size specified in the properties, or reduce the size
Graphics folder properties. of the Sigma graphic.
1.5 Graphics Error Messages in the Trace File

Table 1.5 contains examples of error messages that might be con-
tained in the graphics trace file during a graphics data import.
In each case, the trace file identifies a specific graphic that you
can examine to help determine the cause of the error message.
The path of the graphics trace file is C:\ProgramData\Schneider

Electric StruxureWare\Building Operation 1.x\DataIm-
port\Trace.DataImport.Graphics.txt
(1.x denotes the software version executing.)

Object or controller not found (Unc, The configuration data for Either:
Obj) (For Shape) the controller has not been
Modify the specified
found within the sigma
graphic to use an
database. The bind is still
existing object
effective.
or
Create the object in
Sigma.
Potentially conflicting commands act- Multiple incompatible Simplify the commands for
ing on object visibility. (For Shape) commands configured on a the shape.
shape.
Bitmap not found: Folder\Bitmap file- Bitmap file for the shape Ensure that bitmap file
name (For Shape) does not exist in Sigma. exists in Sigma.
Control characters removed from Control characters not sup- Verify that the text is
string. (For Shape) ported and were removed acceptable with characters
from the shape text strings. removed.


Unknown font (For Shape) Invalid font structure. Verify that font used is
acceptable.
Failed to convert command (Command Command Type property/ Reconfigure the command
name): Problem description (For Object type combination with a supported type.
Shape) not supported.
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.


Removing bitmap command on invalid Invalid shape for the com- None.
shape. mand. Bitmap command
only works on rectangles,
ellipses and schemes.
Removing color command on invalid Invalid shape for the com- None.
shape. mand. Color command
ellipses and polygons.
Removing path command on invalid Invalid shape for the com- None.
shape. mand. Path command only
works on lines and
schemes.
Removing picture command on invalid Invalid shape for the com- None.
shape. mand. Picture command
ellipses and schemes.
Removing text command from non text Text command does not None.
shape. work on shapes.
Removing spin command on scheme. Spin command is not None.
appropriate on schemes.

Appendix 2 - Remove PSTN Zones

The purpose of reconfiguring PSTN (Autodial) connected controllers is
to ensure that all controllers that exist in isolated dialup zones are using
direct Internet Protocol addressing. Any controllers that are not recon-
figured will not form part of the Sigma Interface in Workstation after a
data import.
You will also need to configure port forwarding to ensure that all the
routers and controllers that you will reconfigure on the network can
connect to the internet.
The following procedure is a simplified guide to removing PSTN zones
and reconfiguring devices on the main Sigma network.
1 In System Setup, expand the Networks and Devices folder (the
following example contains a PSTN zone setup:

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.

Appendix 3 - Prepare Long Text

The purpose of preparing long text is to ensure that when a Sigma alarm
occurs in WorkStation, you have local access to information associated
with the cause of the alarm.
In this procedure, you create one new file for each long text associated
with an alarm. You then drag the long text files into a specially created
Building Operation folder, and attach each file to an imported Sigma
alarm object.
On a networked folder:
1 Create a new folder within a networked folder, in which to tempo-
rarily save multiple files.
In the Sigma Alarm Manager:
2 On the Configure menu, select Long Text.
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.


Appendix 4 - Merge Log Sets

The purpose of merging log sets on to a single server is to ensure that
when the servers (except one) are later removed, all log sets are avail-
able and in the correct place to be imported into Building Operation.
In this procedure you merge log sets from different servers to just a sin-
gle server. Assume that two Sigma Servers are called Server A and
Server B, each have log sets configured, and that all log sets on both
servers are to be merged onto Server B.
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.

3 At the Server A client, In the Historical Logging Setup dialog

box, select the first log set and then select Edit.
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.


Appendix 5 - Decommission Sigma Servers

The purpose of decommissioning Sigma servers is to ensure that the
server architecture for Sigma in Building Operation meets the require-
ment of one Enterprise Server and one Sigma Server.
The following procedure is a guide to decommissioning additional serv-
ers:
1 Determine which server is to become the sole remaining Sigma
Server and note the server number.
2 In the Sigma System Manager, in System Setup, expand the Net-
works and Devices folder.
3 Expand the Controllers folder. For each controller:
a In the Node tab, in the Default Server box, enter the number
of the Sigma Server noted in Step 1.

b In the Backup Server tab, in the Backup Server box, enter

the number of the Sigma Server noted in Step 1.
4 Expand the Clients folder. In each client, in the Servers window,

deselect all redundant servers and ensure that the Sigma Server
you intend to keep is selected (but see note below).
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.

Appendix 6 - Disable Dual LANs

The purpose of disabling all Sigma dual LANs is to ensure satisfactory
communications with Building Operation. After disabling this function
on each device, you send the Node configuration to the appropriate rout-
ers, servers and controllers.
The following procedure is a guide to disabling Sigma dual LANs:
1 Compile a list of all controllers, servers, and routers that utilise
dual LANs.
2 In the System Manager, in System Setup, expand the Networks
and Devices folder.
3 Expand the Controllers folder.
4 For each controller with dual networking, in the Node tab, dese-
lect the Dual LAN box.
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.

7 In the System Manager, on the Utilities menu, select Diagnostics.
8 In the Sigma Diagnostics window, select Node.

9 Select the node number of the first controller, server, or router on
the list you compiled in Step 1.
10 On the Options menu, select Download Node Configuration.
11 Repeat Step 9 and Step 10 for each subsequent controller, server,

or router on the list you compiled in Step 1.

Copyright 2014 Schneider Electric Schneider Electric
All brand names, trademarks and registered trademarks Malm, Sweden
are the property of their respective owners. Information +46 40 38 68 50
contained within this document is subject to change
without notice. All rights reserved.
Product Support Services
+44 (0) 1628 741147
SIG-BO-TRANS 12/14 product.support@schneider-electric.com
www.schneider-electric.com/buildings

Sigma v4.08 (3.46.80) To StruxureWare Building Operation v1.6 Transition Guide

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Sigma v4.08 (3.46.80) To StruxureWare Building Operation v1.6 Transition Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Satchwell Sigma

Sigma to Building Operation Transition Guide

Copyright 2014 Schneider Electric

1 About this Guide 5

Schneider Electric, Dec 2014 3 (48)

4 (48) Schneider Electric, Dec 2014

1 About this Guide

1.2 Acrobat (PDF) Conventions

Schneider Electric, Dec 2014 5 (48)

1.3 Typographic Conventions

6 (48) Schneider Electric, Dec 2014

Schneider Electric, Dec 2014 7 (48)

8 (48) Schneider Electric, Dec 2014

2.1 Server Architecture

Sigma Server Enterprise Server

Sigma programming data Data Imports:

Sigma Server PC Enterprise Server PC Sigma Network

Fig. 2.1: Server Architecture

Schneider Electric, Dec 2014 9 (48)

2.2 Enterprise Server

2.2.1 Controllers, Objects and Segments

10 (48) Schneider Electric, Dec 2014

2.2.5 Day-to day Configuration Changes

2.2.6 Default Server

Schneider Electric, Dec 2014 11 (48)

2.3 Sigma Server

2.3.1 Core Configuration Changes

2.3.2 Backup Server

12 (48) Schneider Electric, Dec 2014

3 Review and Preparation

3.1 Transition Issues

Schneider Electric, Dec 2014 13 (48)

Issue Alternative Action

14 (48) Schneider Electric, Dec 2014

Issue Alternative Action

Schneider Electric, Dec 2014 15 (48)

16 (48) Schneider Electric, Dec 2014

9 Configure the Server number, IP address, and Subnet mask

Schneider Electric, Dec 2014 17 (48)

12 Right-click the Log Sets folder and select Data import.

18 (48) Schneider Electric, Dec 2014

19 In the Controller Items\Routesets folder, configure all routesets

20 In Sigma System Diagnostics:

Schneider Electric, Dec 2014 19 (48)

20 (48) Schneider Electric, Dec 2014

Appendix 1 - Warning and Error Messages

Schneider Electric, Dec 2014 21 (48)

1.1 Data Import Conversion Warning Messages

Example Cause Action

22 (48) Schneider Electric, Dec 2014

Table 1.1: Data Import Conversion Warnings

Example Cause Action

Schneider Electric, Dec 2014 23 (48)

1.2 Data Import Conversion Error Messages

Table 1.2: Data Import Conversion Errors

Example Cause Action

24 (48) Schneider Electric, Dec 2014

Table 1.2: Data Import Conversion Errors

Example Cause Action

1.3 Programmable Object Warning Messages

Schneider Electric, Dec 2014 25 (48)

The information provided in the message enables you to identify the

Table 1.3: Programmable Object Return Statements