Integration Methods 4.0

Page
1(21)
Company Document Id
Schneider Electric Integration Methods
EMEA Centre of Excellence
Author Date Approved by Date
Roger Moncur 04/08/2011 Roger Moncur 04/08/2011
Integration Methods of Schneider

Electric Building Automation and
Access Control Systems
Version 4.0
Integration Methods Version: 4.0

Page
2(21)
Company Document Id
Table of contents
1. Introduction..................................................................................................................... 4
1.1 History ................................................................................................................... 4
1.2 Terminology .......................................................................................................... 4
1.3 Scope .................................................................................................................... 5
2. References ..................................................................................................................... 6
3. Integration Methods........................................................................................................ 7
3.1 Building Automation Systems............................................................................... 7
3.2 Protocols ............................................................................................................... 7
3.3 Integration Techniques ......................................................................................... 8
3.4 Gateways .............................................................................................................. 8
3.5 OPC Integration .................................................................................................... 8
4. Andover Continuum building automation and access control system........................... 9
4.1 Protocols ............................................................................................................... 9
4.3 Gateways .............................................................................................................. 9
4.3.1 Integration Gateways ............................................................................................ 9
5. TAC Vista building automation system .......................................................................... 12
5.1 Protocols ............................................................................................................... 12
5.2 Integration Techniques for Xenta 100 / 200 / 300 / 400....................................... 12
5.2.1 General ................................................................................................................. 12
5.2.2 Classic................................................................................................................... 12
5.2.3 Open...................................................................................................................... 13
5.3 Gateways .............................................................................................................. 13
5.3.1 Communcation options TAC Xenta ...................................................................... 13
5.4 OPC Integration .................................................................................................... 15
6. TAC I/Net building automation and access control system ........................................... 16
6.1 Protocols ............................................................................................................... 16

Page
3(21)
Company Document Id
6.3 Gateways .............................................................................................................. 16

7. Satchwell Sigma building automation system ............................................................... 18
7.1 Protocols......................................................................................................................... 18
7.3 Gateways .............................................................................................................. 18
7.4 OPC Integration .................................................................................................... 20
8. Appendix I....................................................................................................................... 21
8.1 OPC Servers and Tools........................................................................................ 21

Page
4(21)
Company Document Id
1. Introduction
This document outlines the principle methods for integrating Schneider Electric Buildings
Business building automation and access control systems with third party systems. Where
appropriate this document identifies integration interfaces specific to commonly found third party
systems or systems associated with particular buildings business segments.
1.1 History
Version Date Signature Comments
1.0 09-01-2011 Roger Moncur First revision.
2.0 17-02-2011 Roger Moncur Second revision
3.0 23-05-2011 Roger Moncur Third revision
4.0 04-08-2011 Roger Moncur Fourth revision
1.2 Terminology
BACnet Data Communications Protocol for Building Automation and

Control Networks
KNX Communications standard for building control networks, also
referred to as Konnex
OPC OLE for Process Control

Page
5(21)
Company Document Id
1.3 Scope
This document is intended for Schneider Electric Buildings Business engineers interested in
integration techniques.

Page
6(21)
Company Document Id
2. References

Page
7(21)
Company Document Id
3. Integration Methods
This document outlines the principle methods for integrating Schneider Electric Buildings
Business building automation and access control systems with third party systems. Where
appropriate this document identifies integration interfaces specific to commonly found third party
systems or systems associated with particular buildings business segments.
3.1 Building Automation Systems

The building automation and access control systems covered in this document are:
• Andover Continuum Building Automation and Access Control System
• TAC Vista Building Automation System
• TAC I/Net Building Automation and Access Control System
• Satchwell Sigma Building Automation System
A number of the building automation platforms listed above support open protocols for
integration. Other techniques for integration are also available and these will also be
summarised.
The following detail is examined for each building automation platform.
• Protocols
• Integration techniques
• Gateways
• OPC Integration
3.2 Protocols
A number of the building automation systems manufactured and installed by Schneider Electric
support common open protocols for communication between native controllers, other Schneider
Electric products or third-party devices: these protocols include Lonworks, BACnet and Modbus.
All the building automation systems support some form of gateway to link both open and
proprietary protocols with other manufacturer’s equipment. Note that a large number of products
from other Schneider Electric business units use Modbus as a default communications protocol
and all these products can be integrated with Schneider Electric building automation systems.
Other products from Schneider Electric support additional protocols such as DALi and KNX,
both in common use in lighting control systems, and there are a number of options available for
connecting with systems using these protocols.
This document also identifies interfaces for use with proprietary protocols that are compatible
with the different building automation products.

Page
8(21)
Company Document Id
3.3 Integration techniques

In this document integration involves the passing of data between devices either via a common
protocol shared by the control systems being connected, via a gateway providing translation
services or via PC or server based software. Such integration allows the systems to become
interoperable.
The tools and techniques for integrating each platform with other technology are identified for
each building automation system. It is sometimes necessary to deploy additional third-party
software in order to be able to complete a fully integrated solution.
3.4 Gateways
Commonly used hardware or software gateways to third-party systems supporting open or
proprietary protocols are included in this document as they can be effective in helping to specify
and achieve an integrated solution. The Continuum system and its XDriver capability allow new
gateways to be developed in-house as and when required for integration projects.
3.5 OPC Integration

The use of OPC for integration of building automation systems is becoming increasingly wide-
spread and this is becoming the integration interface of choice for a number of system
manufacturers. It is also seen by some consultants and system specifiers as the environment in
which to integrate building automation systems, at server level rather that at controller or field
device level.
It is important to understand the constraints that OPC based integration can impose on a
solution, the lack of time schedule support, for example, the way many products are priced on
an object (or Tag) basis and the fact that many OPC servers only support Data Access and are
not able to handle alarms and events.
OPC server or client software is installed on servers or workstations. In some cases it is
supplied with associated industrial PC’s or hardware platforms that host the software or support
the protocol connection to the third-party communications network.
Sometimes it is necessary to transfer data between OPC servers and to perform calculations or
logic on data before passing it on and there are a number of options available to do this usually
at additional cost. Other tools are available to allow data to navigate IP network routers which
are not able to pass standard OPC DCOM traffic.
See Appendix 1 for a list of OPC Servers and associated OPC Tools.
OPC Foundation is a useful source of information about providers of OPC technology.
URL: http://www.opcfoundation.org/

Page
9(21)
Company Document Id
4. Andover Continuum building automation and access control system

Andover Continuum is a building management system and access control system that
comprises a range of freely programmable controllers with fixed I/O and a range of I/O
expansion modules. There is also a range of networkable I/O modules that have conventional
I/O or door access capability. The system has access control capability using freely
programmable door controllers.
4.1 Protocols
The Andover Continuum building automation system supports both a proprietary Infinet protocol
for communication over IP and RS485 field networks, or BACnet IP and BACnet MS/TP open
protocols. These protocols may be mixed in the same Continuum system.
4.2 Integration Techniques

Integration between Andover Continuum and third-party systems is managed differently
depending on the primary protocol being used. If both the Continuum controllers and the third-
party system support BACnet then intercommunication between devices is managed using
BACnet rules. If intercommunication is required between Continuum Infinet or BACnet and a
different open protocol or a third-party protocol then a gateway is required. Continuum
Cyberstation software provides the engineering tools to configure the network of Continuum
controllers and define their configuration. It also is used to explore a BACnet network for
Continuum native BACnet controllers and third-party BACnet devices.
4.3 Gateways
Continuum uses XDriver technology to communicate with third party systems via gateways.
XDrivers may be deployed in three types of Continuum controller, the bCX controller/router
(both Infinet and BACnet versions), the NetController II and the ACX door access controller.
XDrivers interpret a third-party protocol via either a serial connection or IP and present values
from a third party system into dedicated Continuum objects for use locally or in other networked
controllers. These objects behave as standard objects and may be logged or used to generate
alarms. They may also be used in ‘plain english’ programs to drive cause and effect routines or
send commands via other XDrivers to systems such as Pelco Endura.
XDrivers exist for a wide range of interfaces and new XDrivers may be commissioned if
required. The following XDrivers are supported by the current 2nd generation Continuum
controllers, many more are supported on the earlier platforms.
When XDrivers are deployed into a BACnet bCX the third-party system objects will appear as
BACnet objects in Continuum.
To enquire about development of a new XDriver contact the EMEA Centre of Excellence.

Page
10(21)
Company Document Id
4.3.1 Integration Gateways

nd
XDRIVERS 2 Generation controller versions listed below
Open Protocols Device Notes
Modbus TCP bCX/NCII/ACX Enables communication to many SE products
Modbus MS/TP bCX/NCII/ACX Enables communication to many SE products
BACnet IP NCII/ACX Not BACnet bCX
M-Bus bCX/NCII/ACX Needs RS232 to M-Bus converter, max 200 M-bus devices
Lonworks NCII Needs NCII with FTT-10 port
XML bCX/NCII/ACX Web services interface as used by Pelco Endura
BMS System Device Notes

Protocols
Satchwell Sigma NCII IC-LON, 500 Sigma objects (300 SNVTS), + Lonworks XDriver
(See Section 7 below)
Satchwell Sigma bCX/NCII/ACX IC-Modbus, 1000 Sigma objects, + Modbus MS/TP XDriver or
Modbus IP Xdriver. (See Section 7 below)
Honeywell C-Bus bCX/NCII/ACX Uses Soft-Yon C-Bus interface + XDriver
Fire System Protocols Device Notes

Pelco (ESMI) FX Fire bCX/NCII/ACX Monitor FX panel or network of panels
Panel
Actionair LNS bCX/NCII/ACX Smoke fire damper monitoring and control
Clymac bCX/NCII/ACX Monitor Ziton ZP3 fire system
Cerberus bCX/NCII/ACX Monitor network of Cerberus fire panels
Gamewell bCX/NCII/ACX Monitor single or networked fire panel
Gent Vigilon bCX/NCII/ACX Monitor and limited control of fire panels
Honeywell Notifier bCX/NCII/ACX Monitor and control of ID3000 fire panel(s)
Kentec bCX/NCII/ACX Monitor networked Kentech Syncro fire panel(s)
Protec bCX/NCII/ACX Monitor networked Algo-Tec 6400MXL fire panel
Tyco bCX/NCII/ACX Monitor networked Tyco MX fire panel
Intercom Systems
Alphacom bCX/NCII/ACX Monitor Alphacom 80 Exchange system
Complus Teltronic bCX/NCII/ACX Monitor Commend GE200 comms server

Page
11(21)
Company Document Id
Leak Detection
Veeder-Root bCX/NCII/ACX Monitor TSL300/350/350R tank management systems
Lighting Control
Clipsal C-Bus bCX/NCII/ACX RS232 via C-Bus PC interface, Max 50 devices
Security Systems
Comerson bCX/NCII/ACX Control Comerson Digital CCTV system
Honeywell/Microtec bCX/NCII/ACX Monitor and control Galaxy intruder system
Pelco bCX/NCII/ACX Control Endura virtual matrix for camera and monitors
Southwest Microwave bCX/NCII/ACX Monitor Microtrak ‘Intrepid’ MTP intrusion system
Static Systems bCX/NCII/ACX IPFusion TCP driver for fire and nurse call system
Weather Station
Oregon Scientific bCX/NCII/ACX Monitor weather station and wireless detectors
BACNET GATEWAYS
Third-party gateway Device Notes
KNX EIB IntesisBox Up to 4000 KNX group addresses
DALi IntesisBox 1 channel / 64 devices
Daikin VRV DMS502B51 BACnet IP interface - see manufacturer’s data sheet
Mitsubishi SC-BGW See manufacturer’s data sheet
Johnson Controls/York E-Link Gateway York Talk interface - See manufacturer’s data sheet
Trend Controls Intesis IQ3-XNC
Hotel Booking ICS-709-B-F SysMik GmbH - Fidelio booking system interface
Home Automation GLA-BMS Crestron
Table 1
An increasing number of product manufacturers support BACnet integration via gateways. See
the official BACnet website for an up-to-date listing. http://www.bacnet.org
Please refer to the following document for more detail about XDrivers and other interfaces
available for Andover Continuum. The document can be downloaded from the Buildings
Business Extranet product information page:
URL: http://extranet.tac.com/Navigate?node=10980
Document Title: SDS-C-DRIVERLIST
Filename: Third_Party_Interface_Sales_Data_Sheet_7_2010.pdf

Page
12(21)
Company Document Id
5. TAC Vista Building Automation System

TAC Vista is a building automation system that comprises a range of freely programmable
Xenta controllers supported by flexible I/O modules together with fixed application controllers
and a recently introduced range of webserving controllers.
5.1 Protocols
The TAC Vista building automation system natively supports the Lonworks open protocol and
Modbus.
For Lonworks TAC Vista Server can different ways to connect to a LonWorks FTT-10 network,
which uses an unscreened twisted pair. The preferred way is to use TCP/IP as backbone and
access the twisted pair network through LonWorks routers or TCP/IP TAC Xenta devices. It is
also possible to connect to the FTT-10 network over USB or a plug-in adaptor in the PC. A
proprietary protocol that uses the Lonworks network is also supported. Integration is usually
carried out by direct transfer of data using Lonworks standard data types supported by Xenta
and Lonworks compatible controllers from other system manufacturers.
The Modbus protocol is included in all TAC Xenta 500/700/913 models. By using Modbus in
these devices, Modbus points are directly accessible in TAC Vista without use of a gateway. In
case Modbus points need to be transferred to LonWorks, the TAC Xenta 500/700/913 can also
act as a gateway and achieve that. The same goes for all other protocols available in Xenta 731
and 913.
Third-party gateways allow other technology with different protocols to be integrated efficiently.
5.2 Integration techniques for Xenta 100 / 280 / 300 / 400

5.2.1 General
The network communications between programmable Xenta devices can be configured using
two methods, Classic or Open. Classic and Open methods should not be mixed in the same
installation.
5.2.2 Classic
The Classic method uses proprietary communications over the Lonworks network. Passing of
data between programmable Xenta controllers is configured using the Menta programming tool
and no third-party software is required. Communications between programmable Xenta devices
and ‘LonMark’ Xenta devices such as Xenta 121 or third party Lonworks devices cannot be
configured in this type of installation although data from these devices can be viewed from the
TAC Vista workstation.

Page
13(21)
Company Document Id
5.2.3 Open
The Open method of configuration for Lonworks networks is necessary for larger systems when
routers are required to join different subnets and when integration is required between
programmable Xenta controllers and other ‘LonMark’ Xenta or third-party devices. In these
networks intercommunication is achieved by connecting ‘open’ network variables, SNVT’s,
rather than proprietary signals. A network configuration tool such as LonMaker or NL220 is
required for defining the network structure and device addresses and creating the necessary
connections. The resulting information is stored in the controllers and in an LNS database
managed by the network configuration tool.
5.3 Gateways
In most cases data from a protocol goes directly in to Vista/Xenta, but sometimes it is necessary
to pass data between two different networks, e.g. between Lon and Modbus, when a gateway is
needed. There are numerous gateways available in the market, and TAC Xenta 500/700/913
can also act as gateway between the supported protocols.
5.3.1 Communication Options TAC Xenta

Protocols Gateway
Product
Lon Modbus 1)
I/NET M-bus2) C-bus3) Micronet
4)
BACnet5) feature
TAC Xenta 511 X X X

TAC Xenta 527 X X X X
TAC Xenta 701 X X X
TAC Xenta 711 X X X
TAC Xenta 721 X X X
(6)
TAC Xenta 913 X X X X X X X X
1) Serial: Master (max 30 slaves) or slave, RS-232 or 2/4-wire RS-485, RTU or ASCII
TCP: Client only
2) Requires external RS-232 to M-Bus converter, max 200 devices
3) RS-232, max 50 devices
4) SNP, NCP or ARCnet networks supported
5) Serial: PTP (via half router, max 10 devices) or MS/TP (max 30 devices)
TCP/IP: max 10 devices
6) Xenta 913 has no logging or alarm capability

Page
14(21)
Company Document Id

LONWORKS
GATEWAYS
Proprietary Protocols Device Notes
Continuum NetController II Requires F option for free topology I/O bus, requires LON
XDriver, supports approx. 500 SNVT’s,
Lighting Control
DALi various Schneider Electric lighting control products (Former SVEA and
Merten product lines) + third-party products
Dardo Emergency lighting DLM Schneider Electric emergency lighting control product with
Lonworks gateway
Other useful gateways Device Notes

Pelco (ESMI) FX Fire Somati Lon One-way only, up to 4 FX panels, 1311 loop addresses
Panel Gateway
Pelco part no. 00393029
BACnet IP Loytec L-Gate 750 BACnet objects
BACnet IP IntesisBox Up to 3000 BACnet objects
BACnet MS/TP Loytec L-Gate 750 BACnet objects
KNX EIB IntesisBox Up to 4000 KNX group addresses
Daikin VRV DMS504B51 See manufacturer’s data sheet
Mitsubishi LMAP03U Also SC-LGW - see manufacturer’s data sheet
Stulz LIB7000 See manufacturer’s data sheet
Johnson Controls/York E-Link Gateway York Talk interface - See manufacturer’s data sheet
Trend Controls Intesis IQ3-XNC Intesis is authorised IQ3-XNC integrator
Belimo MP-Bus UK24LON Communicates with 8 compatible actuators
Hotel Booking Prolon PFG4000 Fidelio booking system interface
Crestron Home GLA-BMS Crestron Ethernet device
Automation
AMX Home Automation CTG-LON Supplier Comm-tec GmbH
Various Fieldserver See manufacturer’s data sheet
Table 2
Product documentation can be downloaded from the Buildings Business Extranet:

URL: http://extranet.tac.com/Navigate?node=10980

Page
15(21)
Company Document Id
5.4 OPC Integration

TAC Vista can integrate with third-party systems by using its inherent OPC Client and OPC
Server capabilities. Both features are enabled using software licences with additional software
required to install the OPC server. When acting as an OPC Client TAC Vista can display status
information, alarms and events and historical data (trend logs) from OPC servers providing
access to information from other manufacturer’s systems. When acting as an OPC Server
read/write access is provided to data points in the TAC Vista database and alarms from TAC
Vista devices can be delivered to a third-party OPC Client. TAC Vista supports the following
OPC standards:
OPC Server: OPC Data Access v1.0a & v2.05a

OPC Alarms and Events v1.10
OPC Client: OPC Data Access v1.0a & v2.05a

OPC Alarms and Events v1.02
OPC Historical Data Access v1.01
See Appendix I for a list of OPC Servers and OPC tools.

Page
16(21)
Company Document Id
6. TAC I/Net building automation and access control system

TAC I/Net is a building management system and access control system that comprises a range
of freely programmable controllers with fixed I/O together with fixed application controllers. The
system has access control capability using application specific controllers and it is also
configurable as an intruder detection system.
6.1 Protocols
The TAC I/Net building automation system uses a proprietary protocol for communication over
IP and RS485 field networks.

Integration between TAC I/Net systems and third-party systems is managed by using gateways
to a number of open or proprietary protocols. TAC I/Net Host software provides the engineering
tools to configure the network of native TAC I/Net controllers and define their configuration. TAC
Xenta gateways are programmed using the TAC Vista XBuilder tool.
TAC I/Net also supports integration from the host PC via ASCII text strings. These are
associated with datapoints and are sent from a serial port when a datapoint goes into an alarm
state. The text strings can be used to send commands to CCTV systems, pagers etc.
6.3 Gateways
The following gateways support TAC I/Net.

TAC I/NET GATEWAYS
Modbus TCP Xenta 913 Gateway, 100 clients, no logging capability
Modbus TCP Xenta 731 Webserver/controller, 100 clients, 300 datalog capability
Modbus MS/TP Xenta 913 31 slaves or 1 master, no logging capability
Modbus MS/TP Xenta 731 31 slaves or 1 master, 300 datalog capability
BACnet IP Xenta 913 BACnet IP client to max 10 servers, no logging capability
BACnet MS/TP Xenta 913 MS/TP Master, max 30 clients, no logging capability
BACnet PTP Xenta 913 RS232 via half-router, 10 clients, no logging capability
M-Bus Xenta 913 Needs RS232 to M-Bus converter, max 200 devices
Lonworks Xenta 913 Gateway, 1000 security points, no logging capability

Page
17(21)
Company Document Id
Lonworks Xenta 527 Webserver, 1000 security points, 300 datalog capability
Lonworks Xenta 731 Websvr/controller, 1000 security points, 300 datalog capability
Clipsal C-Bus Xenta 913 RS232 via C-Bus PC interface, Max 50 devices
Third-party gateways Device Notes

Link to various protocols NorthBT MR sub-lan device. See manufacturer’s data sheet
Compass
ASCII Interface Device Notes

CCTV/Pager/Intercom I/Net Host Text Library - feature associating an ASCII text string with I/Net
Software point. Text to COM port sent when point in alarm
Table 3
Note that a number of gateways e.g. 7797 ICI, 7771 ICI are referred to in various TAC I/Net technical
documents. These are no longer being developed and the Xenta based gateways listed above should be
used where possible.

Page
18(21)
Company Document Id
7. Satchwell Sigma building automation system

Satchwell Sigma is a building management system system that comprises a range of freely
programmable controllers with fixed or expandable I/O. The system is able to support
application specific field controllers from the Schneider Electric portfolio via Modbus or
Lonworks gateways.
7.1 Protocols
The Satchwell Sigma building automation system uses a proprietary protocol for communication
over IP and/or ARCnet networks with an optional backup communications path using RS485.

Integration between Satchwell Sigma systems and third-party systems is managed by using
gateways to a number of open or proprietary protocols. Sigma workstation software or the
optional SigmaX engineering tools maybe used to configure the network of native Sigma
controllers and define their configuration.
Satchwell Sigma also supports integration from the Sigma Server using optional additional
software, ModBMS. ModBMS enables Sigma to act as an OPC Alarms and Event Server, an
OPC Data Access server or a Modbus IP server (Note it cannot act as a Modbus server and
OPC server simultaneously). The OPC server supports up to 5000 simultaneous OPC tags,
which in practice allows many more data values to be handled because the tags are registered
and de-registered dynamically.
7.3 Gateways
Satchwell Sigma includes the following Integration Controllers (IC’s) that act as gateways for
integration to open and proprietary protocols. IC’s are programmable with standard Sigma
features and support trend logging. All Sigma controllers, including the Integration Controllers,
support a maximum of 50 global data values transferred from other controllers on the Sigma
network. Sigma controllers support 1000 objects.
In the case of the Lonworks interface the suggested maximum number of SNVT’s (in or out) is
300, allowing for the fact that individual SNVT’s can contain multiple datapoints. This results in
an associated sensible limit of 500 Sigma objects to be used for transfer of data to/from the third
party system
Two gateway options are available using a software interface running on a PC or server. IC-
GEN-OPC allows Sigma to access data from a third-party OPC server and IC-GEN-DDE allows
data to be accessed from a DDE source. The same limit on global Sigma signals applies and
the number of Sigma objects supported is 1000.

Page
19(21)
Company Document Id

SIGMA GATEWAYS
Modbus/JBus TCP S-IC3-MODBUS Modbus TCP client, 500 Sigma objects, comms. options
Modbus/JBus RTU S-IC3-MODBUS Modbus RTU Master, 500 Sigma objects, comms. options
Lonworks S-IC3-Lon FTT-10 port, 300 Sigma objects (300 SNVT’s), comms. options
Andover Continuum S-IC3-MODBUS Modbus TCP to bCX/ACX/NC II with Modbus XDriver
TAC Vista S-IC3-MODBUS Modbus TCP to Xenta 913
TAC I/Net S-IC3-MODBUS Modbus TCP to Xenta 913
DDE (Client) S-GEN-DDE PC software, 1000 Sigma objects
OPC (Client) S-GEN-OPC PC software, 1000 Sigma objects
Modbus (Server) ModBMS Software - Sigma Server addition.
OPC (Server) ModBMS Software - Sigma Server addition.
Proprietary Protocols
BAS2800+ IC-BAS Software - Sigma Server addition for comsm to BAS2800+
(RS232)
Unifact Pro S-IC3-UNIFACT Unifact Pro, 1000 Sigma objects, comms. options
ASIC/1 S-IC3-ASIC ASIC/1, 1000 Sigma objects, comms. options
Carrier S-IC3-CARRIER Dataport, 1000 Sigma objects, comms. options
York XL S-IC3-YORK YorkTalk interface, 1000 Sigma objects, comms. options
MN2000 S-IC3-MN2000 ASD Bus interface, 1000 Sigma objects, comms. options
SNP S-IC3-SNP IAC controllers, Unifact, Stulz ACU SNP interface, 1000 Sigma
objects, comms. options
McQuay S-IC3-MCQUAY Chiller interface
Fidelio S-IC3-FIDELIO Fidelio ‘Front Office’ server interface – Hotel booking system
1000 Sigma objects, comms. options
Table 4

Page
20(21)
Company Document Id
7.4 OPC Integration

Satchwell Sigma can integrate with third-party systems acting as an OPC Server by using the
ModBMS Sigma Server extension software. When acting as an OPC Server read/write access
is provided to data points in the Sigma database and alarms from Sigma devices can be
delivered to a third-party OPC Client.
OPC Server: OPC Data Access v1 & v2

OPC Alarms and Events v1
Satchwell Sigma can be configured as an OPC Client and integrate data from third-party OPC
servers by using additional software. IC-GEN-OPC software is installed on a PC, ideally
together the OPC server software, and simulates a Sigma controller with a 500 datapoint
capacity. IC-GEN-OPC supports the following OPC standard:
OPC Client: OPC Data Access v2
See Appendix I for a list of OPC Servers and OPC tools.

Page
21(21)
Company Document Id
8. Appendix I
8.1 OPC Servers and Tools

OPC Servers
Open Protocols Device/Supplier Notes
Modbus TCP & MS/TP various e.g. Matrikon, Kepware and others
BACnet IP various e.g. Cimetrics, Matrikon and others
BACnet MS/TP various e.g. Matrikon with BACnet IP to MS/TP router
Lonworks LNS various e.g. Newron, Matrikon and others
KNX EIB various e.g. Matrikon
SNMP various e.g. Matrikon
TAC Vista Schneider Electric Separate software, for Classic and Open TAC Vista networks
Andover Continuum Schneider Electric Supports Continuum Infinet or Andover Infinity
Satchwell Sigma Schneider Electric ModBMS software addition.
Honeywell C-Bus Soft-Yon Uses Soft-Yon Honeywell C-Bus interface
Johnson N1 or N2 Matrikon Requires PC connected to N1 or N2 network
Johnson N2 S4 Open Industrial PC based solution
(TAC I/Net) Schneider Electric OPC server not updated since 2004.
Pelco Fire (ESMI) Schneider Electric FX Fire panel interface
Kone Elevators Kone Interface to E-Link elevator management system
OPC Tools
Configuration tools
OPC Tool Schneider Electric Maps OPC Server objects into TAC Vista database
Mapping tools
Server to server bridge Data Manager Matrikon – for example to map SNMP to Modbus
Server to server bridge Link Master Kepware – for example to map SNMP to Modbus
Data manipulation
Calculation engine OPCCalc Exele – links to OPC servers for math and logic
Calculation engine Process Calculator Matrikon – links to OPC servers for math and logic
IP Tunnelling Tools
OPC over IP Tunneller Matrikon – helps overcome DCOM network problems
OPC over IP OPC Tunnel Softing – helps overcome DCOM network problems
Table 5

Integration Methods 4.0

Uploaded by

Copyright:

Available Formats

Integration Methods 4.0

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integration Methods 4.0

Uploaded by

Copyright:

Available Formats

Page

Integration Methods of Schneider

Integration Methods Version: 4.0

Integration Methods Version: 4.0

6.3 Gateways .............................................................................................................. 16

Integration Methods Version: 4.0

BACnet Data Communications Protocol for Building Automation and

Integration Methods Version: 4.0

Integration Methods Version: 4.0

Integration Methods Version: 4.0

3.1 Building Automation Systems

Integration Methods Version: 4.0

3.3 Integration techniques

3.5 OPC Integration

Integration Methods Version: 4.0

4. Andover Continuum building automation and access control system

4.2 Integration Techniques

Integration Methods Version: 4.0

4.3.1 Integration Gateways

BMS System Device Notes

Fire System Protocols Device Notes

Integration Methods Version: 4.0

Integration Methods Version: 4.0

5. TAC Vista Building Automation System

5.2 Integration techniques for Xenta 100 / 280 / 300 / 400

Integration Methods Version: 4.0

5.3.1 Communication Options TAC Xenta

TAC Xenta 511 X X X

Integration Methods Version: 4.0

5.3.2 Integration Gateways

Other useful gateways Device Notes

Product documentation can be downloaded from the Buildings Business Extranet:

Integration Methods Version: 4.0

5.4 OPC Integration

OPC Server: OPC Data Access v1.0a & v2.05a

OPC Client: OPC Data Access v1.0a & v2.05a

See Appendix I for a list of OPC Servers and OPC tools.

Integration Methods Version: 4.0

6. TAC I/Net building automation and access control system

6.2 Integration techniques

6.3.1 Integration Gateways

Integration Methods Version: 4.0

Third-party gateways Device Notes

ASCII Interface Device Notes

Integration Methods Version: 4.0

7. Satchwell Sigma building automation system

7.2 Integration techniques

Integration Methods Version: 4.0

7.3.1 Integration Gateways

Integration Methods Version: 4.0

7.4 OPC Integration

OPC Server: OPC Data Access v1 & v2

OPC Client: OPC Data Access v2

See Appendix I for a list of OPC Servers and OPC tools.

Integration Methods Version: 4.0

8.1 OPC Servers and Tools

Integration Methods Version: 4.0

You might also like