Dms 8000

DMS8000 MP4.
10
Application &
Planning
For:
- MM8000 Management Station
- MK8000 OPC Server
- MT8001 Management Terminal
- NK8000 Networks
With WW8000 Composer
Building Technologies
Fire Safety & Security Products
Data and design subject to change without notice. / Supply subject to availability.
© 2007 Copyright by
Siemens Switzerland Ltd
We reserve all rights in this document and in the subject thereof. By acceptance of the document the recipient acknowledges these rights
and undertakes not to publish the document nor the subject thereof in full or in part, nor to make them available to any third party without our
prior express written authorization, nor to use it for any purpose other than for which it was delivered to him.
About this document...............................................................................................5
Definitions of terms...............................................................................................10
1 Products concept..................................................................................11
1.1 Danger management systems ................................................................11
1.2 Connectivity – NK8000 networks ............................................................12
1.2.1 NK8222, NK8223 or NK8225? ...............................................12
1.3 Configuration – WW8000 Composer ......................................................14
2 Management level configurations .......................................................15

2.1 MM8000 Management Station / MK8000 OPC Server configurations ...15
2.1.1 Stand-alone configurations.....................................................15
2.1.2 Client/server configurations ....................................................16
2.1.3 Distributed configurations .......................................................16
2.2 NK8000 network configurations ..............................................................18
2.2.1 DMS8000 Multiple host configuration – CMSDL/IP................18
2.2.2 DMS8000 multiple host configuration – BACnet/IP................18
2.2.3 DMS8000 single-host configuration – support of dial-up
connections.............................................................................19
3 Automation level configurations .........................................................20

3.1 Configurations supported by MM8000 / MK8000 ...................................20
3.2 Configurations supported by MT8001.....................................................22
3.3 Configuration types .................................................................................23
3.3.1 ISO1745 direct configuration ..................................................23
3.3.2 Cerloop configuration .............................................................25
3.3.3 CS1115 / FC330A direct configuration ...................................27
3.3.4 SI410/420 Sintony direct configuration...................................28
3.3.5 Video LAN configuration.........................................................30
3.3.6 Access control LAN configuration...........................................32
3.3.7 BACnet/IP LAN configuration .................................................34
3.3.8 Remote notification configuration ...........................................35
3.3.9 OPC integration configuration ................................................36
3.3.10 NK822x serial configuration....................................................37
3.3.11 NK822x LAN/WAN configuration............................................40
3.3.12 NK8225 Ethernet Port with BACnet Gateway configuration ..43
3.4 NK8000 Networks ...................................................................................46
3.4.1 Hardware configurations.........................................................46
3.4.1.1 Installation ..............................................................48
3.4.2 Subsystem connectivity solutions...........................................50
3.4.2.1 Subsystems connected via RS232 interface .........50
3.4.2.2 Subsystems connected via RS485 interface .........51
3.4.2.3 Subsystems connected via LON interface .............51
3.4.2.4 Cerloop network connected via MK7022 ...............52
3.4.2.5 Power supply supervision 2
and I/O-module
connected via I C-bus ............................................53
3.4.3 Parameterisation.....................................................................53
rd
3.5 3 party systems.....................................................................................54
4 NK8000 Application examples.............................................................55

4.1 Local system ...........................................................................................55
4.2 Distributed, campus-style systems .........................................................56
4.3 Wide area extension systems .................................................................57
4.4 Interactions..............................................................................................58
5 NK8000 Network planning....................................................................60
3
Building Technologies DMS8000_Application_Specification_&_Planning_MP4.10_A6V10063710_a_en
Fire Safety & Security Products 06.2007
5.1 IT rules ....................................................................................................60
5.1.1 Repeater rules ........................................................................60
5.1.2 Cable lengths..........................................................................61
5.2 Dedicated safety and security networks .................................................61
5.2.1 Application example with commercial Ethernet components .62
5.2.2 Application example with Industrial Ethernet components .....63
5.2.3 Application example with OTN (Open Transport Network) ....65
5.3 Shared network .......................................................................................66
5.3.1 Information you need to give to your customer ......................67
5.3.2 Security and Application Port numbers ..................................67
5.4 Datalink characteristics ...........................................................................68
5.4.1 LON ........................................................................................68
5.4.2 Serial interface (RSxxx)..........................................................68
5.4.3 Modems ..................................................................................68
5.4.4 Ethernet ..................................................................................69
5.4.5 FDDI / CDDI............................................................................70
5.4.6 xDSL .......................................................................................70
6 Licenses.................................................................................................71
Appendix A – Network connectivity options ......................................................72
Appendix B – Checklist.........................................................................................73
4
About this document
About this document
Scope
This document applies to the following Siemens FS products:
– MM8000 Management Station
– MK8000 OPC Server for Subsystems
– MT8001 Management Terminal
– NK8000 Networks
(With WW8000 Composer)
Target group
This documentation is intended for the following users:
Sales personnel Persons responsible for the sale of products, and service to customers. They
assess a customer’s desires and needs, then determine the appropriate products
and configurations in order to produce a quotation. They provide customers and
consultants with the basic information necessary to begin installation, configura-
tion, and commissioning activities.
Liability disclaimer
We have taken every possible care in preparing this manual. The contents of this
manual are revised regularly and brought up to latest standards. Nevertheless, we are
unable to provide any guarantee with regard to content, entirety or quality of the de-
tails contained in this manual.
We assume no liability for problems resulting from the use of this manual. The infor-
mation contained in this document may be changed without prior notice. We reserve
the right to publicize any such changes by issuing updated versions or new editions.
5
Siemens Building Technologies DMS8000_Application_Specification_&_Planning_MP4.10_A6V10063710_a_en
Fire & Security Products 06.2007
About this document
Reference documents
The most recently released documentation for customers can be found in the STEP
Documentation Repository System released at SBT FS for end-users via the STEP
Web Client interface at the following address:
https://intranet.sbt.siemens.com/dbcom/en/db_porta/client.asp
The following describes one way to search and find a document:

 To learn about other ways to locate a document, see DMS8000 Quick Reference
Guidelines for Search and Finding DMS Documents in STEP
(STEP #A6V10064704).
1. Click on the "STEP WEB Client" image.
2. Choose "04 Fire -3F" from the "Product Segment" box and select “Activate filter”.
3. Select “All” in the Documents section of the Quick Search page and select “Ad-
vanced Search”.
4. Enter the document number in the “Brochure No.” field (e.g. A6V10062415 or
007121) and press “Enter”.
Hint: For a specific version, specify the Market Package as *MPn.nn* in the “Classi-
fication No.” field (e.g. *MP4.10*).
Note: STEP provides no results when the number of found objects is equal to or
greater than 200.
Product and Document Name Document no. Date Last up-

date
Sales documents
MM8000
023 Product Datasheet A6V10062415_a 06.2007 MP4.10
053 System Description A6V10062417_a 06.2007 MP4.10
039 Sales Presentation A6V10062423_a 06.2007 MP4.10
074 Sales Guide A6V10062427_a 06.2007 MP4.10
074 Tender Specifications A6V10062419_a 06.2007 MP4.10
074 Offer Template A6V10062429_a 06.2007 MP4.10
MK8000
023 Product Datasheet A6V10062405_a 06.2007 MP4.10
039 Sales Presentation 007121_a 03.2003 MP1.10
074 Sales Guide 004970_b 03.2003 MP1.10
MT8001
023 Product Datasheet 006952_e 09.2005 MP3.15
053 System Description 008605_a 09.2005 MP3.15
039 Sales Presentation 007346_b 03.2003 MP1.01
074 Sales Guide 007286_c 09.2005 MP3.15
074 Tender Specifications 007788_c 09.2005 MP3.15
023 Demo Material 008078_b 09.2005 MP3.15
6
About this document
NK8000
023 Product Datasheet NK8223 A6V10062431_a 06.2007 MP4.10
PICS
023 Product Datasheet NE8000 A6V10062421_a 06.2007 MP4.10
039 Sales Presentation A6V10062435_a 06.2007 MP4.10
074 Sales Guide A6V10062439_a 06.2007 MP4.10
Technical documents
MM8000
073 Release Notes MP4.10 A6V10062455_a 06.2007 MP4.10
073 Release Notes MP3.20-03 A6V10075048_a 06.2007 MP3.20-03
073 Release Notes MP3.20-02 A6V10067812_a 04.2007 MP3.20-02
073 Release Notes MP3.20-01 009421_b 12.2006 MP3.20-01
073 Release Notes MP3.15 008901_b 09.2005 MP3.15
073 Release Notes MP3.12 008899_a 06.2005 MP3.12
048 Autronica BSxx, ICC ad-on 008750_a 06.2006 MP3.20
048 LIST SCU 2000, ICC add-on 009248_a 06.2006 MP3.20
048 MAXSYS PC601, ICC add-on 008751_a 06.2006 MP3.20
048 CP100, ICC add-on 009848_a 06.2006 MP3.20
048 R Card M5 ICC add-on A6V10064742_a 06.2007 MP4.10
048 MODBUS ICC add-on A6V10067800_a 06.2006 MP3.20
048 CDDL-CDSF ICC add-on A6V10067787_a 06.2006 MP3.20
048 DLCS ICC add-on A6V10067792_a 06.2007 MP4.10
048 GEUTERBRUECK ICC add-on A6V10067796_a 06.2007 MP4.10
029 Operation A6V10062409_a 06.2007 MP4.10
022 Operation Quick Reference A6V10067779_a 06.2007 MP4.10
048 Installation, Configuration and A6V10062413_a 06.2007 MP4.10
Commissioning (ICC)
022 Configuration Quick Reference A6V10075052_a 06.2007 MP4.10
019 Localisation - Engineering guide A6V10062459_a 06.2007 MP4.10
MK8000
048 Release Notes for MP4.10 A6V10062459_a 06.2007 MP4.10
073 Release Notes for MP3.20 009423_a 06.2006 MP3.20
Release Notes for MP1.10 007076_a 04.2003 MP1.10
Commissioning (ICC)
7
About this document
MK8000 Interface Specifications

019 MK8000 OPC Server 004971_h 06.2006 MP3.20
019 CS11 EP5 004974_e 02.2004 MP1.31
019 CS11 EP7 007546_b 02.2004 MP1.31
019 FC700A 008596_a 12.2004 MP3.10
019 CS1115 009843_a 06.2006 MP3.20
019 FC330A 009842_a 06.2006 MP3.20
019 CS440 004973_b 10.2003 MP1.30
019 CS4 007078_b 10.2003 MP1.30
019 CZ12 007079_b 10.2003 MP1.30
019 CZ10 007080_b 10.2003 MP1.30
019 STT11 007081_c 10.2003 MP1.30
019 DMS7000 007082_b 10.2003 MP1.30
019 GW-20/NK8210 007122_b 10.2003 MP1.30
019 GW-21 007124_b 10.2003 MP1.30
019 MK7022 007125_b 10.2003 MP1.30
019 CK11 EP5 007126_b 02.2004 MP1.31
019 CK11 EP7 007129_b 02.2004 MP1.31
019 SK11 007127_b 10.2003 MP1.30
019 NK8223 (CDI-Net) 007154_b 10.2003 MP1.30
019 CS6 Guarto 007545_b 02.2004 MP1.31
019 SI410 Sintony 008597_a 12.2004 MP3.10
019 CC60 007547_b 10.2003 MP1.30
019 NK822x 007879_b 02.2004 MP1.31
019 CF9000 007880_a 10.2003 MP1.30
019 SIMATRIX 007881_a 02.2004 MP1.31
019 Philips/Burle CCTV 008085_a 02.2004 MP1.31
019 SiPass 008607_a 03.2006 MP3.20
019 TELSCAN 009426_a 03.2006 MP3.20
019 SIMATRIX 009427_a 03.2006 MP3.20
019 SISTORE 009428_a 03.2006 MP3.20
019 Video Camera 009429_a 03.2006 MP3.20
MT8001
048 Operation 006611_e 09.2005 MP3.15
022 Operation Quick Reference 008088_a 09.2005 MP3.15
048 Installation, Configuration and 006647_e 09.2005 MP3.15
Commissioning (ICC)
019 Localisation - Engineering guide 008083_b 09.2005 MP3.15
016 History Analysis Installation 006962_b 03.2003 MP1.00
8
About this document
NK8000
073 Release Notes for MP4.10 A6V10062457_a 06.2007 MP4.10
073 Release Notes for MP3.20-01 009422_b 12.2006 MP3.20-01
Commissioning (ICC)
DMS8000 and Composer

023 Composer Datasheet A6V10062403_a 06.2007 MP4.10
054 Composer Technical Manual A6V10062401_a 06.2007 MP4.10
022 Composer Quick Reference A6V10067783_a 06.2007 MP4.10
048 Network and Subsystems Con- A6V10062425_a 06.2007 MP4.10
nectivity Guide
048 Access Control Connectivity A6V10062451_a 06.2007 MP4.10
048 Video Connectivity A6V10062457_a 06.2007 MP4.10
048 OPC Connectivity A6V10065253_a 06.2007 MP4.10
048 Graphical Map Configuration A6V10062441_a 06.2007 MP4.10
022 Graphical Map Config. Quick A6V10069550_a 06.2007 MP4.10
Ref.
016 Migration from DMS7000 A6V10062443_a 06.2007 MP4.10
MK8000 OPC Server:

In addition to the documents available through the STEP documentation system, the
OPC Foundation publishes a number of other documents that are necessary and/or
useful for understanding the underlying principles used in the MK8000 OPC Server.
These PDF documents can be downloaded from www.opcfoundation.org. Select
“Downloads” on the main page of the site. See “Comments” below for navigation de-
tails. *
* Registration may be required.
Name Date Comments

OPC DA 2.05a (Data Access Interface Specifications) 2002-06-28 OPC site: “Specifications”
Also available in STEP
#004971_h
OPC via DCOM with XP SP2 2006-03-30 OPC site: “White Papers”
Also available in STEP
#004971_h
Training
Siemens Fire & Security Products offers a comprehensive training program. You can
find information about courses in the Siemens Intranet.
Modification index
Current version Date Notes
A6V10063710_a_en 06.2007 6th Application & Planning edition for all Siemens DMS, Network,
and 3rd party products
9
Definitions of terms
Definitions of terms
Hierarchical level concept A Danger Management System can be structured into 3 hierarchical levels:
 Management level (central evaluation)

The majority of the human interface takes place at this level. Standard computers running a variety of dis-
play, management, and analysis software packages usually provide the functionality.
 Automation level (local evaluation and data communication)

The majority of the real-time control functions are carried out at this level. The devices are self-contained
controllers and communication products distributed as required within the building.
The local evaluation part consists mainly of the control units.
The data communication part consists of the transmission path between the local control units and the
terminal system.
 Field level (data acquisition)

This level contains the devices that connect to the physical items of a plant, including sensors and actua-
tors. Products in this level are simple in nature, but may provide some local control and safety-functions.
At this level we can find elements as:
-Automatic detectors
-Manual call points
-Signalling devices, contacts
-Control elements
The individual elements are usually combined in alarm zones and are connected to the control unit.
Automation level configu- The Automation level configuration relates to the variety of possible connections of subsystems (control
ration panels, such as AlgoRex) via possible network structures to the DMS (connectivity of automation level
subsystems to management level).
BAU (Siemens) Building Automation products.
DMS Danger Management System.
FS (Siemens) Fire Safety and Security products.
Head end The head end of a system is the Management Station on the management level providing the User Interface
to the final user.
HVP (Siemens) Heating and Ventilation products.
LAN Local area network.
Management level con- The Management level configuration relates to the configuration possibilities of DMS Client/Server structure
figuration itself, without taking into account any subsystem connectivity. The DMS acts as a management level gate-
way providing downstream connectivity to the automation, and exposing data upstream via the user inter-
face.
SES (Siemens) Security Systems.
Total Building Solutions TBS is a combined Market Offering of the Divisions BAU, FS and SES with the scope to describe the Sie-
(TBS) mens Building Technologies (SBT) approach to the integrated building management systems.
WAN Wide area network.
10
Products concept
1 Products concept
One of Siemens Building Technologies’ (SBT) primary goals is to be able to provide
complete integration solutions to our customers. Complete integration includes fire
safety, security, and building automation systems built by various Siemens and third-
party suppliers.
As the needs and expectations of the market continue to advance at the pace of tech-
nology, SBT aims to provide products that meet those needs and expectations.
Siemens’ family of products are designed to serve the market for small to medium-size
local systems, campus-size configurations (LAN applications), and for geographical
networks (WAN applications). Additionally, in cases where another supplier is making
the integration, Siemens provides open system solutions enabling integration of our
subsystems.
See the following to determine which product or combination of products best suit your
customer’s needs.
1.1 Danger management systems

Siemens offers the following Danger Management System (DMS) solutions:
 MM8000 Management Station:

The MM8000 provides integrated management and handling, decentralised system
operation and centralised maintenance. The MM8000 is designed to replace older
management stations such as LMSmodular, LMS6, and DMS7000.
MM8000 also offers the following advantages:
– Flexibility – The system can be built and configured to fit different situations.
– Scalability – MM8000 will easily grow to support more subsystems, disciplines,
and stations as needed.
– Reliability – The MM8000 is based on the concept of autonomous subsystems
and distributed control. Furthermore, redundant configurations can be imple-
mented.
– Security – The operator will have access to exactly what is defined.
– 3 Party integration – The MM8000 architecture allows for open system solu-
rd
rd
tions and for the integration of 3 party devices.
 MK8000 OPC Server for Subsystems:

The MK8000 OPC Server product concept provides open system solutions to our
rd
customers, enabling our subsystems to be integrated into 3 party management
systems.
The objective is to offer the OPC Data Access (DA) Server product in parallel with
complete offerings including our MM8000 management station software.
The OPC DA Server product allows us to technically integrate FS subsystems into

building automation unit head-ends, thereby supporting the SBT Total Building So-
lutions offering.
11
Products concept
 MT8001 Management Terminal:
The MT8001 Management Terminal provides a common user interface to Fire and
Intrusion subsystems of different generations. The user interface is designed for in-
tuitive operation by non-technical users.
MT8001 provides basic management station functionality to those users who would
not normally have access to such a device. And it provides this functionality at the
most convenient location for personnel trusted with the responsibility of reacting to
security events. These people may be security guards, but more commonly, they
may also be receptionists, concierges, janitors, or general technical service person-
nel.
For these reasons, the operation (or user interface) of MT8001 has been kept as
simple as possible.
1.2 Connectivity – NK8000 networks

NK8000 connects various subsystems over TCP/IP and Ethernet or BACnet/IP and
Ethernet with the MM8000 and the MK8000 systems, and offers serial connectivity to
MM8000, MK8000, and MT8001 systems.
The following make up the NK8000 product family:

 NK8223 Ethernet Port for DMS8000 systems
 NK8222 Ethernet Port for a single subsystem for DMS8000 systems
 NK8225 Ethernet Port with BACnet Gateway for DMS8000 systems
1.2.1 NK8222, NK8223 or NK8225?

The NK822x Ethernet Ports are used to connect local and distributed safety and secu-
rity devices to the NK8000 network. The NK822x port provides a first level of centrali-
sation, and acts as a secure communication partner for DMS8000. All ports come with
optional housing solutions with autonomous power supplies. Additionally, the NK8223
/ NK8225 can be serially connected to a local management station.
The NK8222 allows connection of a single safety or security subsystem to the NK8000
network, and is best suited for distributed systems or geographical networks where
only one subsystem has to be connected to a remote management system (such as a
bank application: centralisation of security systems of branches).
rd
The NK8223 allows connection of multiple SBT and 3 party subsystems to the
NK8000 network, and is best suited for local systems, campus-size or wide area ex-
tension systems, where more than one subsystem has to be connected, or system ex-
tensions with additional subsystems are expected.
The NK8225 offers the same connectivity capabilities as the NK8223. In addition, it
provides BACnet connectivity between NK8225s for network-wide interactions and
provides BACnet gateway functionality for CS11 AlgoRex, FC700A, and SIG-
MASYS/D100 fire detection systems, and Guarto CS6 and SI410/420 Sintony intru-
sion detection systems to DMS8000 hosts.
12
Products concept
NK8222
 1 serial connection supporting a single fire, gas, intrusion detection, CCTV, or a
digital I/O system
Or
 LON adapter for connecting 1 CS6 Guarto intrusion detection system
NK8223
 Up to 4 serial connections supporting fire, gas, and intrusion detection systems,
CCTV, and digital I/O’s
And
 LON adapter for connecting up to 4 CS6 Guarto intrusion detection systems
NK8225
 Same capabilities as NK8223
 BACnet connectivity (native protocol conversions) supporting CS11 AlgoRex,
FC700A, and SIGMASYS/D100 fire, and CS6 Guarto and SI410/420 Sintony
intrusion detection systems
NK8222, NK8223
 TCP/IP on Ethernet connectivity for connection to local and remote management
stations. Transport protocol CMSDL/IP or CEI79-5 featuring 64-bit encryption
(FEAL algorithm) for high security banking applications, and support of switched
lines;
 Simultaneous multiple host connectivity (up to four) using CMSDL/IP protocol (with-
out encryption);
 Upstream serial connectivity to a local management station (MM8000 / MK8000 /
MT8001) using an RS232 line via CMSDL serial protocol;
 The upstream devices (MM8000 or MK8000) must be equipped with the NS8210
Network Driver for TCP/IP on Ethernet connectivity or with the NS8012 CDI-Net
Driver for serial connectivity.
NK8225
 Same as NK8222, NK8223 above
 BACnet/IP on Ethernet connectivity for connection to local and remote DMS8000
management stations;
 Conversion of native protocols (CS11 AlgoRex,, FC700A, SIGMASYS/D100,
SI410/420 Sintony, and CS6 Guarto) to BACnet;
 Enhanced network-wide interaction machine* supporting logical combinations be-
tween subsystems connected to other NK8225s (CS11 AlgoRex, FC700A, SIG-
MASYS, D100, CS6 Guarto, Sintony SI410/420)
 The DMS8000 upstream devices (MM8000 or MK8000) must be equipped with the
NS8011 Network Driver for BACnet/IP on Ethernet connectivity, the NS8210 Net-
work Driver for TCP/IP on Ethernet connectivity, or with the NS8012 CDI-Net Driver
for serial connectivity.
 *See more about interactions in section 4.4.
13
Products concept
NK822x
 Direct support for local digital I/O with up to 16 non-supervised inputs and 8 relay
outputs;
 Interaction machine supporting logical combinations between locally connected
subsystems (CS11 AlgoRex, SIGMASYS/D100, SI410/420 Sintony, CS6 Guarto,
CF9000, Philips-Burle);
 Optional dial-up connectivity via modem for wide area extension systems.
1.3 Configuration – WW8000 Composer

MM8000, MK8000, MT8001, and NK8000 can be configured in a fast, safe, and easy
way with Composer (using the subsystem tool concept). Composer is the common
configuration tool for all DMS8000 products.
 For more information on Siemens DMS products, refer to the “Reference docu-
ments” section in “About this document” on page 6.
14
Management level configurations
2 Management level configurations

This section lists the management configuration types that are supported in DMS8000
MP4.10 for:
– MM8000 Management Station
– MK8000 OPC Server
– NK8000 Networks
To see network connectivity options, refer to Appendix A.
2.1 MM8000 Management Station / MK8000 OPC Server configura-

tions
The following management configuration types are supported in MM8000/MK8000:
– Stand-alone station
– Client/server configuration
– Distributed configuration which may include SiPass access control and/or CCTV
– Redundant solution configuration
2.1.1 Stand-alone configurations

Characteristics:
– Stand-alone station that contains all software levels (Client and Server);
– Provides a straightforward solution for small and medium-size systems.
Fig. 1 MM8000 or MK8000 stand-alone configuration (MM8000 shown)

15
2.1.2 Client/server configurations

Characteristics:
– Distributed client and server communicate via TCP/IP connection;
– Provides a straightforward solution for small and medium-sized systems.
Fig. 2 MM8000 / MK8000 client/server configuration TBS
2.1.3 Distributed configurations

Characteristics:
– Software architecture distributed on different hardware;
– Each station is specialised for a single function;
– Optional redundancy solution with dual servers to prevent service interruption.
MM8000: The client provides the user interface. The server handles all the func-
tionality provided by MM8000, and holds the configuration database. The FEP
(Front-end processor) provides the drivers for the different network connections
(such as Cerloop, NK8000, etc.);
New! MM8000 now provides OPC client functionality for OPC Data Access
Server subsystems.
MK8000: The server provides OPC functionality while the FEP (Front-end proc-
essor) provides “background” functionality.
This architecture provides the highest performance solutions for large systems
that require both multiple FEPs and coordinated management.
16
The following are examples of distributed configurations:
Fig. 3 MM8000 / MK8000 redundant configuration with dual servers
Note: For technical details regarding a redundancy configuration solution, please con-
tact customer support.
Fig. 4 MM8000 / MK8000 + SiPass distributed configuration

Note: MM8000 / MK8000 and SiPass servers may reside separately.
17
2.2 NK8000 network configurations

NK8000 safety and security networks are supported by MM8000 and MK8000 MP4.10
in the configurations described in section 2.1 (up to four hosts). Additionally, the
NK8225 supports BACnet subsystem connectivity for up to fours hosts for MM8000 /
MK8000.
2.2.1 DMS8000 Multiple host configuration – CMSDL/IP

Characteristics:
– Communication layer equipped with NS8210 Network driver
– Up to four hosts
Fig. 5 NK8225 DMS8000 CMSDL multiple host configuration
2.2.2 DMS8000 multiple host configuration – BACnet/IP

Characteristics:
– Communication layer equipped with NS8011 BACnet Network Driver for
DMS8000
– Conversion of native protocols to BACnet (CS11 AlgoRex, FC700A, SIG-
MASYS/D100, SI410/420 Sintony, CS6 Guarto) in NK8225
– Up to four DMS8000 hosts
Fig. 6 NK8225 DMS8000 BACnet multiple host configuration

Note: CS11 AlgoRex connectivity direct or via Cerloop.
18
2.2.3 DMS8000 single-host configuration – support of dial-up connections

Characteristics:
– Communication layer equipped with NS8210 Network driver and modem(s)
– NK822x dial-ups as primary (no Ethernet connection) or secondary (in case net-
work is down) via PSTN
Fig. 7 NK8000 dial-up configuration
19
Automation level configurations
3 Automation level configurations

3.1 Configurations supported by MM8000 / MK8000
The MM8000 / MK8000 MP4.10 support the following:
Automation level configuration types

– Direct RS-232
– Cerloop
– CDI-Net
– NK8000
– Direct LAN
Network components
– NK822x
– MK7022
– GW-21
– GW-20
Control units
Note: For control unit versions, see MM8000 MP4.10 Release Notes (STEP
#A6V10062455)
Fire detection systems:

– CS11 AlgoRex
– FC700A
– CS1115 (FC330A)
– CZ10
– STT11 (Système de Télécommande et Télésignalisation)
– STT20
– STT2410
– SIGMASYS / D100
Intrusion detection systems:

– CS4
– SI410/420 Sintony
– CS440
– CZ12
– CS6 Guarto
Gas detection systems:

– CC60
Video systems:
– SIMATRIX, SIMATRIX NEO video crossbars
– SISTORE AX, CX, MX (including NVR*), MXpro, SX Digital Video Recorders
(DVRs)
– TELSCAN
– IP cameras (fixed) equipped with:
– CCIS1337-LP / CFVA-IP / CVVA-IP
*Network Video Recorder

20
Access control:
– SiPass Integrated Access Control System
– CerPass CC30 (connected via SiPass)
Building automation:
‡
– DESIGO PX
General automation and I/O systems:

– SIMATIC S7
– MF7033/MM7033 digital PLC unit
– CF9000 I/O systems
Remote notification:
‡
– ESPA Paging System
rd
3 party systems:
– A number of 3 party systems are supported via NK822x or MM8000 drivers.
rd
 For details, see section 3.5.
Section 3.3 details the configuration types supported by MM8000 and MK8000.
Note: Combinations of automation level configurations are also supported.
 For network connectivity options, see Appendix A.
‡
MM8000 only
21
3.2 Configurations supported by MT8001

The MT8001 MP3.15 supports the following:

– Direct RS-232
– Cerloop
– NK8000 local host (requires NK8000 MP3.15)
Network components
– MK7022
– NK822x (requires NK822x MP3.15)
Control units
– CS11 AlgoRex
– FC700A
– CZ10

– CS440
– CS6 Guarto

– CC60
General I/O systems:

– CF9000 I/O systems
Section 3.3 details the configuration types supported by MT8001.

22
3.3 Configuration types

3.3.1 ISO1745 direct configuration
Fig. 8 ISO1745 direct configuration
System architecture
This configuration allows for integration of CS11 AlgoRex (or FC700A) fire panels.
The CK1142 (or FG700A) provides the liaison to MM8000 / MK8000 / MT8001.
Communication / connection
The upstream side of the gateway (CK1142 or FG700A) is connected to the DMS via
serial line. The downstream side of the gateway is connected to one (or more) CS11
AlgoRex (or FC700A) fire panels via the proprietary C-Bus.
23
Subsystems that can be connected in this way
Type Name Supported by

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Fire panel CS11 AlgoRex X X X
Fire panel FC700A X X X
Network devices required
Type Name Version

‡
Gateway for CS11 CK1142
‡
Gateway for FC700A FG700A
Additional components required for the various management station types
Type Additional Name Version

components
Foreign station OPC client head end Any OPC DA2.0x OPC DA2.0x
compliant client
OPC Server MK8000 MP4.10
ISO1745 Driver NS8010
MM8000 ISO1745 Driver NS8010 MP4.10
MT8001 None MP3.15
Limits and restrictions
Type Version Restrictions

MM8000 MP4.10 Up to three serial connections to ISO1745 driver
MK8000 (three CK1142).
MT8001 MP3.15 One serial connection only for CK1142.
‡
See MM8000 MP4.10 Release Notes (STEP #A6V10062455)
24
3.3.2 Cerloop configuration
Fig. 9 Cerloop configuration
System architecture
This configuration allows for integration of a number of Cerloop (proprietary Class A
loop) connectable control panels. The MK7022 provides the liaison to MM8000 /
MK8000 / MT8001.
The upstream side of the MK7022 gateway is connected to the DMS via serial line.
The downstream side of the MK7022 is connected via Cerloop to different fire & secu-
rity control units. A CS11 AlgoRex cluster can be connected to the Cerloop via the
CK1142 gateway (configured for Cerloop).
25

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Fire panel CS11 AlgoRex X X X
Fire panel CZ10 X X X
Intrusion panel CS440 X X X
Intrusion panel CS4 X X
Intrusion panel CZ12 X X
Gas panel CC60 X X X
Digital PLC unit MF/MM7033 X X X
Système de STT11 X X X
Télécommande et
Télésignalisation
Type Name Version

‡
Gateway for Cerloop MK7022
‡
Gateway for STT11 SK11

components
compliant client
ISO1745 Driver NS8010
MM8000 ISO1745 Driver NS8010 MP4.10
MT8001 None MP3.15

MM8000 MP4.10 With stand-alone/server stations, up to three serial
MK8000 connections to ISO1745 driver (three MK7022).
More lines can be supported via FEP stations (max 8
lines per FEP).
MT8001 MP3.15 One serial connection only.
Note: Up to four data evaluation devices (MM8000 / MK8000 / MT8001 / MF7033)

may be connected to the Cerloop.
‡
26
3.3.3 CS1115 / FC330A direct configuration
Fig. 10 RS-232 direct configuration
System architecture
This configuration allows for integration of CS1115 (or FC330A) fire panels.
Via serial line RS-232.

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Fire panel CS1115 X X
FC330A X X

components
compliant client
Fire CNDL Driver NS8015
MM8000 Fire CNDL Driver NS8015 MP4.10

MM8000 MP4.10 Up to four serial connections to CNDL driver.
MK8000
MT8001 MP3.15 CS1115 / FC330A not supported.
27
3.3.4 SI410/420 Sintony direct configuration
Fig. 11 Serial configuration via RS-232
Fig. 12 Serial configuration via LAN tunnelling
System architecture
This configuration allows for integration of SI410/420 Sintony intrusion panels.
The connection can be via:
– Serial line RS-232;
– LAN, where the SI410/420 is equipped with a SMN36 serial / LAN adapter.* On
the management station, a software module provides a virtual COM port.
* External adapter (e.g. LANTRONIX UDS100 or UDS10) can also be used.
28

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Intrusion panel SI410/420 Sintony X X
Network devices required (for LAN tunnelling)
Type Name Version

LAN/RS-232 adapter SMN36 See Sintony documentation
(internal)
LAN/RS-232 adapter See LANTRONIX documentation
(external)

components
compliant client
SI410/420 Sintony NS8014
driver
LAN/RS-232 LANTRONIX See
software redirector LANTRONIX
(for LAN tunnelling) (or equivalent) documentation
MM8000 SI410/420 Sintony NS8014 MP4.10
driver
LAN/RS-232 LANTRONIX See
software redirector LANTRONIX
(for LAN tunnelling) (or equivalent) documentation

MM8000 MP4.10 Connectivity limited to number of serial and virtual
MK8000 serial ports.
MT8001 MP3.15 SI410/420 Sintony direct connectivity not
supported.
29
3.3.5 Video LAN configuration
Fig. 13 Video LAN configuration
System architecture
This configuration allows for the integration of CCTV to MM8000 and MK8000.
The CCTV devices are connected to the DMS via LAN.

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
CCTV SISTORE AX X X
SISTORE CX X X
SISTORE MX X X
SISTORE MXpro X X
SISTORE SX X X
TELSCAN video web X X
server *
IP cameras (fixed)
rd
3 party systems  See DMS8000 Video Connectivity Configu-
ration guide (STEP #A6V10062457).
*Note: IP cameras can be connected to SISTORE MX. If connected directly, they are
configured as single-line TELSCAN.
30

components
compliant client
Appropriate software SISTORE,
according to specific TELSCAN
device
MM8000 Appropriate software SISTORE MP4.10
according to specific TELSCAN
rd
device 3 party
systems*
IP camera devices CCIS1337-LP
CFVA-IP
CVVA-IP
 *See section 3.5 on page 54 and DMS8000 Video Connectivity Configuration guide
rd
(STEP #A6V10062457) for supported 3 party subsystems.

MM8000 MP4.10 None
MK8000 MP4.10 Event treatment and diagnostics only; live video not avail-
able
MT8001 MP3.15 CCTV not supported
31
3.3.6 Access control LAN configuration
Fig. 14 SiPass LAN configuration
System architecture
This configuration allows for the integration of access control to MM8000 /MK8000.
The Advanced Central Controller(s) (either SiPass ACC or Cerpass CC30 via SiPass)
manages communication between devices and the DMS + SiPass server via LAN.
Note: The SiPass server can be separate from the MM8000 / MK8000 server.
Type Name Version Supported by

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
‡
Access control SiPass X X
Integrated
rd
3 party  See DMS8000 Access Control Connectivity
systems Guide (STEP # A6V10062451).

Type Name Version
LAN devices
‡
32

components
compliant client
MM8000 / Access Control SiPass Integrated
MK8000 software
SiPass Driver NS8018

MM8000 MP4.10 None
MK8000
MT8001 MP3.15 Not supported
33
3.3.7 BACnet/IP LAN configuration
Fig. 15 Direct LAN configuration for subsystems
System architecture
This configuration allows for the integration of DESIGO PX building automation con-
trollers.
The subsystems are connected to the DMS via LAN.

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Building DESIGO X
‡
automation PX

components
compliant client
BACnet Driver NS8011
MM8000 BACnet Driver NS8011 MP4.10

MM8000 MP4.10 Displays events to indicate when conditions are
abnormal – no additional information regarding an
event is available on the management station.
‡
Up to 50 DESIGO PX can be connected.
MT8001 MP3.15 DESIGO PX not supported.
‡
See MM8000 MP4.10 Release Notes (STEP #A6V10062455) for PX models and quantity supported.
34
3.3.8 Remote notification configuration
Fig. 16 Remote notification configuration
System architecture
This configuration allows for the integration of a paging system to MM8000.
The paging system is connected to the DMS via RS-232.

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
‡
Paging System ESPA X
compliant paging
devices

components
MM8000 Paging dispatching
services

MM8000 MP4.10 1 paging system
MK8000 MP4.10 Paging system not supported
MT8001 MP3.15
‡
35
3.3.9 OPC integration configuration
Fig. 17 OPC integration configuration
System architecture
rd
This configuration allows for the integration of 3 party subsystems equipped with an
OPC server.
OPC connectivity for subsystems can be provided in “light” or “full” mode.

- Light: Free, but requires more engineering (e.g. SIMATIC S7)
 See the OPC Connectivity Guide (STEP #A6V10065253)
- Full: Requires development of a Composer subsystem tool (e.g. RCO
R-Card M5)
rd
3 party subsystems are connected via Ethernet to the OPC server, which may run on
the MM8000 Management Station or on a networked PC. MM8000 connects to the
OPC server for all of the communication to/from the subsystems.

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
‡
I/O System SIMATIC S7 X
‡
Access Control RCO R-Card M5 X

components
rd
MM8000 3 party OPC server

MM8000 MP4.10 8 OPC connections Please contact customer sup-
10,000 OPC tags (in total) port for more connections, tags.
‡
36
3.3.10 NK822x serial configuration
Fig. 18 NK8000 serial configuration for MM8000 / MK8000

Note: Not all subsystems are configurable for MK8000. See section 3.1 for details.
System architecture
loop), Cerban and/or RS485 connectable control panels. In addition it allows for
Guarto (CS6) integration via LON-bus. One of the NK822x Serial Ports provides the li-
aison for a local management station (MM8000 / MK8000).
The NK822x is connected on upstream side via RS-232 (proprietary CMSDL protocol)
to the management system.
Note: A (temporary) Ethernet network link is required for configuration download.
On the downstream side, the NK822x is connected via serial lines and/or via LON-bus
to a number of different fire & security control units.
 For supported downstream configurations/protocols of NK822x, please refer to the

NK822x-Ethernet Port datasheets. (See “Reference documents page 6.)
37

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Fire panel CS11 AlgoRex X X
Fire panel FC700A X X
Fire panel CZ10 X X
Fire panel SIGMASYS X X
Fire panel D100 X X
Intrusion panel CS6 Guarto X X
Gas panel CC60 X X
Digital PLC unit MF/MM7033 X X
Système de Té- STT11* X X
lécommande et X
STT20 *
Télésignalisation X
STT2410 *
Video Crossbar SIMATRIX X X
Video Crossbar SIMATRIX NEO X X
Input/Output CF9000 and X X
DF8020/40;
excluding
DF8045/46
 See section 3.5 on page 54 for supported 3 party
rd rd
3 party systems
subsystems.
* Cerloop connectivity only
Type Name Version

Ethernet Port NK822x MP4.10
‡
‡
‡
38

components
compliant client
CDI-Net Driver NS8012
MM8000 CDI-Net Driver NS8012 MP4.10

MM8000 MP4.10 - Upstream serial connectivity is limited to one host
MK8000
- Host must be equipped with NS8012 CDI-Net Driver
- NS8012 CDI-Net Driver supports max. 3 NK822x’s
MT8001 MP3.15 Serial connection to the NK822x is not supported
39
3.3.11 NK822x LAN/WAN configuration
Fig. 19 NK8000 LAN/WAN configuration
System architecture
loop), Cerban and/or RS485 connectable control panels. In addition it allows for CS6
Guarto integration via LON-bus. The NK822x Ethernet Ports provide the liaison to
MM8000 / MK8000.
Additionally, the NK822x provides serial connectivity to a local host (MM8000 /

MK8000 / MT8001) using an RS-232 line via CMSDL protocol.
The NK822x is connected on the upstream side via Ethernet to the MM8000 and/or
the MK8000, and on the downstream side via serial lines and/or via LON-bus to a
number of different fire & security control units.
Dial-up lines can optionally be used as a backup connection in the event the network
is down, or as a primary connection when no network is present.
 For supported downstream configurations/protocols of NK822x please refer to the

NK822x-Ethernet Port datasheets. (See “Reference documents” page 6.)
40

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Fire panel CZ10 X X
Fire panel D100 X X
Gas panel CC60 X X
Digital PLC unit MF/MM7033 X X
Système de Té- STT11* X X
lécommande et X
STT20*
Télésignalisation X
STT2410*
Video Crossbar SIMATRIX X X
Video Crossbar SIMATRIX NEO X X
Input/Output CF9000 and X X
DF8020/40;
excluding
DF8045/46
 See section 3.5 on page 54 for supported 3 party
rd rd
3 party systems
subsystems.
* Cerloop connectivity only
Type Name Version

Ethernet Port NK822x MP4.10
‡
‡
‡
41

components
compliant client
Network Driver NS8210
MM8000 Network Driver NS8210 MP4.10
Modem NK8021 (Analog);
Siemens M20 or
MC35i (GSM)

MM8000 MP4.10 - NK822x supports logical connections to a max. of 4
MK8000 hosts (MM8000 and/or MK8000) via CMSDL/IP protocol
- Only one host can be supported using the CEI 79-5 en-
crypted protocol
- Up to 500 NK822x can be connected to an MM8000 /

MK8000, however please contact customer support for
configurations of over 100
- Upstream serial connectivity is limited to one host
- Up to four CS6 Guarto intrusion panels per NK8223 /

NK8225 are supported
- NK822x supports one modem, and up to 5 phone num-

bers
- GSM modems: SIM pin must be disabled
- NS8210 Network Driver supports up to 64 modems
- NK8000 requires static IP-addresses (i.e. DHCP is not

supported)
MT8001 MP3.15 LAN connections to the NK822x are not supported
42
3.3.12 NK8225 Ethernet Port with BACnet Gateway configuration
Fig. 20 NK8225 Ethernet Port configuration
System architecture
This configuration allows for integration of fire and intrusion detection systems.
The NK8225 is connected on upstream side via Ethernet to MM8000 and/or MK8000
(BACnet). On the downstream side it is connected via serial lines and/or via LON-bus
to a number of different fire & security control units.
 For supported downstream configurations/protocols of NK8225 please refer to the

NK8225 Ethernet Port with BACnet Gateway datasheet. (See “Reference docu-
ments” page 6.)
43

MM8000 MK8000 MT8001
MP4.10 MP4.10 MP3.15
Fire panel D100 X X
Type Name Version

Ethernet Port with NK8225 MP4.10
BACnet Gateway
‡
‡

components
compliant client
BACnet Driver NS8011
MM8000 BACnet Driver NS8011 MP4.10
‡
44

MM8000 MP4.10 - NK8225 supports logical connections to a max. of 4
MK8000 hosts via proprietary CMSDL/IP protocol*, OR via
BACnet/IP protocol
- Only one host can be supported using the CEI79-5
protocol*
- Dial-up via CEI protocol and network-wide-interactions**
via BACnet are currently not compatible
- Up to four CS6 Guarto intrusion panels per NK8225 are
supported
- NK8000 requires static IP-addresses (i.e. DHCP is not
supported)
- Default UDP Port 47808 (hex BAC0) for BACnet con-
nectivity (configurable)
- BACnet Broadcast Management Device (BBMD) is sup-
ported in NK8225 (NK8225 can be installed on different
TCP/IP subnets)
- Max. 150 COV subscriptions per device object
- Max. 10,000 pairs of BACnet multi-state input and multi-
state output objects are supported (soft limit)
 * See section 3.3.11 for configuration details for these protocols.
 ** See section 4.4 for details on interactions.
45
3.4 NK8000 Networks

This section provides more specific details of the NK8000 components
3.4.1 Hardware configurations
NK8223 / NK8225
The NK8223/NK8225 Ethernet ports are available in four hardware configurations:
NK8223.2 Base module

NK8225.2 – 1 Ethernet line for remote station
– 2 serial lines for subsystems/local station/modem
NK8223.4 Base module + 2-port serial extension

NK8225.4 – 1 Ethernet line for remote station
NK8223.CL2 Base module + LON extension

NK8225.CL2 – 1 Ethernet line for remote station
– 1 LON line for subsystems
NK8223.CL4 Base module + LON and 2 port extensions

NK8225.CL4 – 1 Ethernet line for remote station
NK8222
The NK8222 Ethernet port is available in two hardware configurations:
NK8222.2 Base module

– 1 Ethernet line for remote station
– Max 1 subsystem
NK8222.CL2 Base module + CerCom extension

– 1 Ethernet line for remote station
– Max. 1 subsystem
46
Further options
The following are available for all of the NK822x products:
DF8040 8-input module – 8 input (non supervised) module for acquiring digital contacts. A
on I2C bus max of 2 modules can be directly connected to NK822x. For more
connectivity (as well as for supervised inputs), it is necessary to use
a CF9003 CPU on one of the serial connections.
DF8020 8-output relays – 8 output (non supervised) relay module for controlling digital con-
module on I2C bus tacts. Only one module can be directly connected to NK822x. For
more connectivity, it is necessary to use a CF9003 CPU on one of
the serial connections.
DF8090 power supply – Optional module for supervising the NK822x power supply and
supervision module on I2C detecting power failures and battery low conditions. It is not needed
bus when NK822x is installed in a fire or intrusion control unit, whose
power supply is already supervised.
NE8001 – Wall-mountable, metallic cabinet with DIN-rail, including power

supply unit.
Input: 100 – 240 Vac; Output: 12Vdc 4A.
NE8002 – Wall-mountable, metallic cabinet with DIN-rail.
NZ8201 – NK822x mounting kit for CS11

Card holders and cable set for installing NK822x in CS11 or CS440
NZ8202 – NK822x mounting kit for CS6 Guarto

Mounting plate, card holders and cable set for installing NK822x in
CS6
NZ8203 – NK822x mounting kit for SI410 Sintony

Mounting plate, card holders and cable set for installing NK822x in
SI410 Sintony (standard or Scandinavian housings)
Further options: Cable for connecting SI410 to NK822x must be or-

dered separately from the intrusion product range (80064100001
SAQ18 Cable link X25 SAQ18).
Modem – NK8021 analog modem

Analog modem for public switched telephone network (PSTN)
47
3.4.1.1 Installation
Typically NK822x are installed in the enclosure of the subsystem and powered from
the supervised power supply of the subsystem.
NK822x Ethernet Ports are supplied in a plastic box, easy to install on DIN-rails.
Alternatively the NK822x can be installed without the plastic box using the specific
mounting kits for CS11 AlgoRex/CS440, CS6 Guarto, or SI410/420 Sintony.
Fig. 21 NK822x mounting option for CS11 AlgoRex
Fig. 22 NK822x mounting option for CS6 Guarto
Fig. 23 NK822x mounting option for SI410/420 Sintony
48
Stand-alone installations of NK822x are possible with the compact and convenient
NE8001 and NE8002 housing solutions.
 NE8001 includes a DIN-rail, power supply, and DF8090 Power supply supervision
module and is pre-wired for a fast and easy installation of the NK822x.
 NE8002 the empty enclosure including the mounted DIN-rail
Fig. 24 NE8001 housing with installed NK822x and DF80xx modules
49
3.4.2 Subsystem connectivity solutions

The following control units are supported:

– CS11 AlgoRex
– FC700A
– CZ10
– SYSMASYS / D100

– CS4
– CS440
– CZ12

– CC60
Video systems:
– SIMATRIX video crossbar;

– CF9000 I/O systems (via IC-2 RS232/RS485 interface converter)
rd
3 party systems:
– A number of 3 party systems are supported either via NK822x or MM8000
rd
drivers.
 For details, see section 3.5.
3.4.2.1 Subsystems connected via RS232 interface
Fig. 25 Example of subsystems connected via RS232 interface
50
3.4.2.2 Subsystems connected via RS485 interface

 Siemens CF9000 I/O systems (CF9003, DF8020, DF8040, DF8045, DF8046 mod-
ules)
Fig. 26 Example of a subsystem connected via RS485 interface
Note: The serial interface COM1 can be configured either as RS232 or RS485 inter-
face. This configuration requires hardware revision E or later.
3.4.2.3 Subsystems connected via LON interface

 Siemens CS6 Guarto intrusion detection systems (up to 4 CS6)
Fig. 27 Example of subsystems connected via LON interface

51
3.4.2.4 Cerloop network connected via MK7022

The following control units are supported in a Cerloop configuration:

– CS11 AlgoRex
– CZ10
– STT20
– STT2410

– CS4
– CS440
– CZ12

– CC60

The Cerloop network is connected via the MK7022 to the NK8223 / NK8225.
Fig. 28 Example of Cerloop network connected via MK7022
Note: NK8223 / NK8225 can handle up to 4 independent Cerloop networks.
52
3.4.2.5 Power supply supervision and I/O-module connected via I2C-bus

The following Siemens DF80xx modules are supported:
– DF8090 Power supply supervision module (max. 1 module)

– DF8020 8-output relays module (max. 1 module)
– DF8040 8-input module (max. 2 modules)
3.4.3 Parameterisation
The NK8000 configuration is part of the Composer tool environment. To perform the
SW-configuration for NK8000 market packages MP2.0 and later, a WW8000 Com-
poser license is required.
The configuration tool includes connection parameters, as well as interaction parame-

ters (with AND, OR, XOR, and NOT logic combinations).
53
3.5 3rd party systems

The MM8000 and MK8000 Danger Management Systems, and the NK8000 Networks
rd
MP4.10 support the following 3 party systems:
Note: The following systems are available as add-on packages.*

 Please refer to product-specific documentation.

– Direct RS-232
– NK8000
– Direct LAN
– OPC connectivity (client/server)
Network components
– NK822x
Control units
MODBUS-based systems
CDDL/CDSF-based systems

‡
– Autronica BSxxx
‡
– LIST SCU 2000

‡
– MAXSYS PC6010

‡
– CP100
Video systems:
– Philips Burle Allegiant LTC 8x00 video switchers (available in standard setup)
‡
– Geutebrück MultiScope II Plus and MultiScope III DVRs
Access control:
‡
– RCO R-Card M5
* More add-on packages may be available than what is listed above. Check on the
FS-DMS Intranet (PSP).
‡
MM8000 only
54
NK8000 Application examples
4 NK8000 Application examples

4.1 Local system
Most of the sites where a management station is installed are local systems.
Examples for local systems are:
– Hotels
– Office buildings
– Shopping centres
– Public buildings (such as museums)
The following figure shows the various subsystem connections of an NK8223 in a local
system.
MM8000 MM8000
Stand-alone setup Stand-alone setup
+ NK8210 driver + NK8210 driver …up to 4 hosts
LON
Fig. 29 Example of a local system
The management station is connected via TCP/IP LAN to the NK8223/NK8225 for the
centralisation of:
– CF9000 I/O System (RS485 party lines for multiple units (directly connected or via
IC-2 converter);
– CCTV SIMATRIX crossbar or Philips-Burle;
– Cerloop network via MK7022 (CS11 AlgoRex, CZ10, STT11, STT20, STT2410
(Système de Télécommande et Télésignalisation), CC60 (Gas), CS440, CS4,
CZ12 intrusion control units, and DMS7000 units);
– Up to 4 CS6 Guarto units on the LON line;
– Serial connection to CS11 AlgoRex, FC700A, SIGMASYS, D100, CZ10, CC60
(Gas), SI410/420 Sintony, CS440, CS4, and CZ12 intrusion control units.
Optionally, DF80xx modules for up to 16 digital inputs, 8 relay outputs, or power

2
supply supervision can also be installed on the local I C bus.
55
4.2 Distributed, campus-style systems

Examples for campus size systems are:
– Universities
– Airports
– Amusement parks (e.g. Disneyland)
– Industries
– Pharmaceutical companies
– Hospitals
– Automobile manufacturing plants
The following figure shows a typical campus site configuration. The subsystems of
each building are connected to an NK822x Ethernet Port. The NK822x are connected
via the LAN or WAN to the remote management station.
Fig. 30 Example of NK822x connection to distributed systems
56
4.3 Wide area extension systems

Examples for wide area extension systems are:
– Metros
– Pipelines
– Banks with a network of branch offices
– Telecom providers
The following figure shows a typical geographical network configuration. The head-
quarters is equipped with several subsystems connected to an NK8223 / NK8225
Ethernet Port. The branches where a single fire or security subsystem needs to be
centralised, are equipped with NK8222 Ethernet Ports for a single subsystem. The
NK822x are connected via the LAN or WAN to the remote management station(s).
Additionally, dial-ups are available via modem as backup connectivity in case the net-
work is down.
Fig. 31 Example of a wide area expansion system

57
4.4 Interactions
Interactions are possible between the subsystems connected to NK822x and the lo-
cally connected I/O modules. Incoming messages can trigger one or more command
messages to other subsystems.
Note: Incoming messages can be combined with the logical operators AND, OR,
XOR, and NOT.
The configuration is done via an easy to use interactions tool, and then downloaded to
the NK822x.
Fig. 32 Local interactions between subsystems connected to NK8223/NK8225
Fig. 33 Local interactions on NK8222
58
Limitations:
Local interactions are limited to the following subsystems:
– CS11 AlgoRex
– FC700A
– STT20
– STT2410
– SIGMASYS
– D100
– CS6 Guarto
– CF9000
– Local NK8000 I/O (DF80xx modules)
– NK7022 Cerloop interface
– Philips-Burle video switcher
While the NK8225 is capable of the same local interactions as the NK8223, it is also
capable of network-wide interactions via BACnet/IP to subsystems connected to
other NK8225s.
Fig. 34 Local and network-wide interactions on NK8225
Limitations:
Network-wide interactions on the NK8225 via BACnet/IP are possible for the same
subsystems as local interactions.
Note: Network-wide interactions and dial-up connections are not currently compatible.
59
NK8000 Network planning
5 NK8000 Network planning

NK8000 networks can be built as a dedicated safety- and security IP network, or can
be integrated into an existing customer network (shared network). The IT rules apply
in both cases.
5.1 IT rules
The NK8000 network supports the IEEE 802.3 Ethernet 10BaseT standard, which is
based on a star topology.
The cable specification for this standard is minimum Cat.5 UTP. We recommend you
use Cat.6 cable, however, which fulfils the specification for 100BaseTX networks.
Note: The maximum length for an Ethernet segment for Ethernet 10BaseT and
100BaseTX is 100m.
5.1.1 Repeater rules

It is possible to extend the Ethernet length using repeaters (hubs). However, you can-
not use infinite repeaters to extend the cable.
Note: The transfer speed determines the number of repeaters you can install.
10Mbps network
For a 10Mbps network, the 5-4-3 repeater rule is valid. This rule means that you can
attach a maximum of 5 segments, with 4 repeaters in serial, but you can only attach 3
segments to other devices.
The better way to extend line length is using a bridge/switch, or a router or fibre ca-
bles. Consider the extra costs using this method.
60
Segment 1
Repeater (Hub) 2 Repeater (Hub) 1
1 2 3 4 5 6 SD 1 2 3 4 5 6 SD
Upl ink Upl ink
100B ase-T X 100B ase-TX 100Bas e-T X 100B ase-T X
13 14 15 13 14 15
1 2 3 4 5 6 13 14 F DX 1 2 3 4 5 6 13 14 F DX
ON ON
LANbooster 123 PWR A /L
A /L
FDX
A/ L
FDX 1 23
LANbooster 123 P WR A/L
A/ L
FDX
A/L
F DX 1 23
7 8 9 10 11 12 7 8 9 10 11 12
7 8 9 10 11 12 7 8 9 10 11 12
Segment 2
Segment 3
Repeater (Hub) 3
1 2 3 4 5 6 SD
Upl ink
100B ase-T X 100B ase-TX
13 14 15
F DX
1 2 3 4 5 6 13 14
A /L ON
FDX
A/ L
FDX 1 23
7 8 9 10 11 12
7 8 9 10 11 12
Segment 4
Repeater (Hub) 4
1 2 3 4 5 6 SD 1 2 3 4 5 6 SD
Upl ink Upl ink
100B ase-T X 100B ase-TX 100B ase-T X 100B ase-TX
13 14 15 13 14 15
1 2 3 4 5 6 13 14 F DX 1 2 3 4 5 6 13 14 F DX
ON ON
A /L
FDX
A/ L
FDX 1 23
A /L
FDX
A/ L
FDX 1 23
7 8 9 10 11 12 7 8 9 10 11 12
7 8 9 10 11 12 7 8 9 10 11 12
Segment 5
Field Field Field
Fig. 35 10BaseT network with up to 4 repeaters in serial star topology
100Mbps network
For a 100Mbps network, it is not possible to extend the line length with the 5-4-3 re-
peater rule. This is due to the faster speed.
The maximum number of repeaters in serial for 100Mbps Ethernet is 2.
5.1.2 Cable lengths

Optimally, you should use Cat. 6 twisted pair cable.
Note: The maximum cable length is 100 meters, installed as follows:
– 90 meters fixed installed cable (Horizontal cabling)
– 10 meters patch cables (both sides together)
The cable length for fibre optic depends on the Ethernet technology employed.
 Please refer to the table in section 5.4.4, “Ethernet” on page 69.
5.2 Dedicated safety and security networks

We recommend you build dedicated safety and security networks whenever it is pos-
sible. Advantages of dedicated safety and security networks are:
– You control the network;
– You choose the components;
– You can place the network components in your own housings;
– You can profit from power supplies with battery backup of the control units;
– There is no risk that other bandwidth-intensive applications will reduce the per-
formance of the network.
Disadvantages of dedicated safety- and security networks are:

– You need trained staff for commissioning and maintenance of the network;
– You may need to keep some additional spare parts in stock.
– Higher installation costs.
61
5.2.1 Application example with commercial Ethernet components

The following drawing shows a NK8000 network based on commercial Ethernet
components.
MM8000MM8000MM8000 MM8000
MM8000
Server Client
Stand-alone Client
Client
Switch Switch SD
Router
CO N SO L E
LOOP
1 2 3 4 5 6 SD 1 2 3 4 5 6 SD
O K
Upli nk Upli nk
B1
B2
BR I
LP
DSU
100B as e-T X 1 00Bas e-T X 10 0B ase -T X 10 0Bas e-TX S/ T CP U
S3
13 14 15 13 14 15
1 2 3 4 5 6 1 3 14 FDX 1 2 3 4 5 6 13 14 F DX
ON O N
LANbooster 123 P WR A/ L
A/ L
FD X
A/L
FDX 123
LANbooster 123 P WR A/L
A/L
FD X
A/L
FDX 123
WI C 0 O K FD X 100 LN K
AU X W IC 1 O K
7 8 9 10 11 12 7 8 9 10 11 12
7 8 9 10 11 12 7 8 9 10 11 12 Cisco 172 0
WAN
Switch
1 2 3 4 5 6 SD
Upli nk
100B as e-T X 1 00Bas e-T X
13 14 15
1 2 3 4 5 6 1 3 14 FDX
ON
A/ L
FD X
A/L
FDX 123
7 8 9 10 11 12
7 8 9 10 11 12
Repeater (Hub) SD
Router
CO N SO L E
LOOP
1 2 3 4 5 6 SD 1 2 3 4 5 6 SD
Upli nk Uplink
OK
B1
B2
BR I
LP
DSU
100B as e-T X 1 00Bas e-T X 100B ase-T X 1 00B ase -TX S/ T CP U
S3
13 14 15 13 14 15
1 2 3 4 5 6 1 3 14 FDX 1 2 3 4 5 6 13 14 F DX
ON ON
A/ L
FD X
A/L
FDX
LANbooster 123 PW R A /L
A /L
F DX
A/ L
FDX
WI C 0 O K FD X 100 LN K AU X W IC 1 O K
123 1 23
7 8 9 10 11 12 7 8 9 10 11 12
7 8 9 10 11 12 7 8 9 10 11 12 Cisco 172 0
10BaseT 10BaseT 10BaseT 10BaseT
Field Field Field Field
Fig. 36 NK8000 network based on commercial Ethernet components
In the example in Fig. 36, the MM8000 Server and Client stations are connected to
100BaseT Switches, whereas the Ethernet Ports are connected to 10BaseT Hubs.
One Ethernet Port is connected via Router and WAN to the centre.
When planning a dedicated safety- and security network with commercial Ethernet
components, consider the following aspects:
– Be aware that the maximum length of a segment is 100m;
– Use Category 5 TP cable or better (Category 6 recommended);
– Install RJ45 outlets close to the DMS PCs and Ethernet Ports;
– Install the network components in a safe place, where only our service engineers
can access;
– Connect the network components to a UPS (Uninterruptible Power Supply);
– Keep spare parts for the network components.
62
5.2.2 Application example with Industrial Ethernet components

With Industrial Ethernet from Siemens A&D, it is possible to build up large and power-
ful networks. Components that are designed specifically for industry enable problem-
free data exchange over long distances.
Industrial Ethernet networks can be built up either electrically or optically, both in a lin-
ear structure as well as in redundant ring structures. The structure incorporates either
an OSM (Optical Switch Module) or an ESM (Electrical Switch Module). Transmis-
sions between the modules take place on fibre optic cables for OSM or TP/ITP
(Twisted Pair / Industrial Twisted Pair) cables for ESM.
Redundant networks increase the overall security and reduce installation down times.
It is vital for safety and security applications that network reconfiguration time be as
fast as possible after a network fault. The extremely fast reaction times after detection
ensure that a network can be reconfigured to a functioning network infrastructure
within fractions of a second.
The following application example shows a NK8000 network built with Industrial
Ethernet components in a redundant optical ring structure.
MM8000
MM8000 MM8000 MM8000
MM8000
Server
Stand-alone Client Client
Client
OSM TP 62 OSM TP 62
OMC-TP11
OSM BC08
FO
redundant
OSM TP 22
ring
NK822X
OSM TP 22
OMC-TP11
NK822X
Field
NK822X NK822X
Field
Field Field
NK822X
Field
Fig. 37 NK8000 network built with Industrial Ethernet components
63
The Ethernet Ports are connected via OMC (Optical Media Converters) or directly via
OSM (Optical Switch Modules) to the redundant network.
The total size of a network with Industrial Ethernet OSM can be up to 150km.
The maximum length for the fibre optic cable is:
– 3 km with multimode fibre optic cable
– 26 km with single mode fibre optic cable
You can find more information about Industrial Ethernet at:

http://www.siemens.com/industrial-ethernet
64
5.2.3 Application example with OTN (Open Transport Network)

OTN (Open Transport Network) from Siemens Atea is an optical fibre based transmis-
sion system for voice, data, LAN, and video information. This system allows intercon-
nection of electronic equipment found in complex, basically industrial installations
through one single network, irrespective of the distances to be bridged.
Today, OTN is probably the most powerful multiplexer for large, private environments
with mixed communication needs such as railways, metros, light rails, mines, airports,
pipelines, and so on.
OTN is exactly what its name implies:
– OPEN
It can handle nearly all existing physical interface standards, but also very spe-
cific communication protocols in special environments via its interface cards.
– TRANSPORT
It carries different types of information (such as voice, data, LAN, and video)
completely transparently throughout the network, and does so with high availabil-
ity.
– NETWORK
It is based on fibre optic technology in a future-proof network infrastructure,
spanning any distance.
An OTN network is built up with nodes that are interconnected by a dual fibre optic
ring. A network consists of up to 250 nodes.
Each node is mounted in a 19" rack and is equipped with network cards, interface
cards, and one or more power supply modules. The network cards provide communi-
cation between the optical rings and the interface cards.
On both rings, consecutive TDM (Time Division Multiplexing) frames circulate in oppo-
site directions. These frames provide communication between the nodes.
Fig. 38 OTN network node
The OTN system offers a capacity of 150 Mbps (OTN-150), 600 Mbps (OTN-600) and
2.5 Gbps (OTN-2500). It can be deployed in networks covering distances from a few
hundred meters up to 2000 km. The distance between two consecutive OTN nodes in
the network depends on the fibre characteristics and the type of optical transceivers
used (from 2 km with multimode fibre up to 95 km with G.652/G.653 fibre).
65
The following image shows a NK8000 network, which uses an OTN network as
backbone.
MM8000
MM8000MM8000
MM8000
MM8000
Server Client
Stand-alone Client
Client
Ethernet
Ethernet 100BaseT 100BaseT
OTN Node
N215
FO redundant ring
Ethernet
Ethernet 10BaseT 10BaseT
Field Field Field
Fig. 39 NK8000 network built with OTN as backbone
NK8000 is only one of the applications that can share the OTN network, together with
CCTV-, access control-, and telephony applications (not shown in Fig. 39).
You can find more information about OTN at:

http://www.ic.siemens.be/icn/otn/eng/about.shtm
5.3 Shared network

It is possible to integrate FS NK8000 and management station products into a cus-
tomer’s network, however you need to be aware of / satisfy the following require-
ments:
 Only Ethernet is supported
 The DMS PC (in general) supports 10BaseT, 100BaseT, and so on, but this de-
pends on the network card in the PC
 NK822x supports ONLY 10BaseT, Half-duplex
 Each management station-PC and each NK822x needs a fixed IP-Address (NO
DHCP)
 An RJ45 Ethernet outlet must be close to the facility
66
Also, you will need to determine the following regarding the client’s network:
 Maintenance times for the network (shutdown of the network)

 Network utilisation (Load > 30 – 40 % is bad on shared network)
 Collision rate (< 5% is good)
 Stability of the network (> 99.9% is good)
 Availability of the network (Downtime)
 Access time to the network (timeouts / access time < 1 sec. is good)
 Responsibility for the data transfer over the network
 Building sites (dredgers destroy cables, etc.)
 Redundancy of the network
 UPS (uninterruptible power supply) for the network components?
5.3.1 Information you need to give to your customer

To integrate FS NK8000 and management station products into a customer’s network,
ensure that your customer is aware of the following information:
 DHCP is not supported from any device;

 NK822x supports only Half-duplex and 10 Mbps;
 Only Ethernet RJ 45 copper cable Cat. 5, 5E, or 6 is supported;
 If the network is down, it is not possible to receive any information via the network;
 The responsible person for the network is the customer, and not Siemens
FS/FIS/SES. The customer should sign a contract that Siemens FS/SES disclaims
any liability for the customer’s existing network.
Your customer will also need to know the following:
 The IP-address for each NK822x and each DMS PC (tell where the devices are in-
stalled);
 Redundancy network devices or paths available.
5.3.2 Security and Application Port numbers

Most companies use a Firewall or a Proxy server to protect the company network from
outside. Also within a company’s network, rules exist, and not everything is allowed.
For example, maybe only e-mail and File transfer applications are allowed, and Re-
mote access (Telnet) is prohibited.
Each of these applications has a Port number. This Port number identifies the type of
application. For example the Port number for the e-mail application (SMTP) is 25.
Generally, the network administrator allows only a few Port numbers, and the rest are
prohibited.
The following Port numbers are used by NK8000:

– TCP Port number 3001 (NK822x)
– TCP Port number 3001…3004 in multiple host configurations
– TCP Ports 20 and 21 (FTP for the configuration download to NK822x)
– TCP Port 4000 for service messages
– UDP Port 47808 (hex BAC0) is default for BACnet connectivity, but is configur-
able
The network administrator must allow these Port numbers; otherwise our applica-
tion is prohibited in the network.
Note: More TCP/IP ports may be needed for MM8000/MK8000.
 For details, see the MM8000 Sales Guide (STEP #A6V10062427).
67
5.4 Datalink characteristics

5.4.1 LON
LON transceiver type: FTT-10 topology:
– Doubly terminated bus topology
– Free topology
Speed: 78kbps (given by FTT-10)
Cable type: any kind of twisted pair cable, UTP (Unshielded Twisted Pair) preferred
Cable length: Depends on cable quality
– Typ. 1’400m for doubly terminated bus topology (UTP Category 3), up to 2’400m
with perfect cabling
– Typ. 500m for free topology (UTP Category 3)
Max. nodes per segment: 64
Max. nodes per sub-network: 128
Max. number of repeaters per sub-network: 4 (5 segments)
Detailed specifications:
http://www.echelon.com/Support/documentation/
Section: Engineering Bulletins → Media & Wiring
5.4.2 Serial interface (RSxxx)
Transceiver Media Max. Nodes Topol- Max. Connector Max. Distance Remarks URL
per Segment ogy Speed Type without spe-
cial HW
RS 232 3 wires point-to-point PTP 115kbps D-Sub 9 15 Meter www.phoenixcontact.de
D-Sub 25 www.wut.de
RJ 45
RS 422 2 twisted point-to-point PTP 1Mbps* 1km* * speed-
pairs distance
trade-off
RS 485 1 twisted ~32, depending bus 1Mbps* 1km* * speed-
master-slave pair on addressing distance
trade-off
RS 485 2 twisted ~32 bus 1Mbps* 1km* * speed-
pair depending on distance
addressing trade-off
5.4.3 Modems
cial HW
Tele- point-to-point PSTN 56kbps World-wide www.westermo.se
phone analog over the PSTN www.blackbox.com
Line cat. 64 kbps (public www.zyxel.com
3 ISDN basic switched tele-
rate Inter- phone network)
face
Wireless GSM World-wide
over the GSM
(Global System
for Mobile
communica-
tions)
68
5.4.4 Ethernet
cial HW
10Base2 Copper 30 Bus 10 Mbps Coax con- 185 Meter Max. 4 Re- www.blackbox.com
Coax necter BNC peaters in www.anixter.com
cable 50 serial (5 www.alliedtelesyn.co
 RG 58 segments) m
and max. on www.rad.com
3 segments
nodes con-
nected
10Base5 Copper 100 Bus 10 Mbps Vampire 500 Meter Max. 4 Re-
Coax 50 taps with peaters in
 15 Pin AUI serial (5
connector segments)
10BaseT 4-wire 1024 per the Star 10 Mbps RJ 45 100 Meter Max. 4 Re-
Copper whole network peaters in
CAT. 6 serial (5
100  segments)
imped-
ance
10BaseF 2 wire 1024 per the Star 10 Mbps ST, SC, or Up to 2 km
Fibre 50, whole network various depending on
62,5 or connector the link budget
100 m
100BaseT 4-wire 1024 per the Star 100 Mbps RJ 45 100 Meter Max. 2 Re-
Copper whole network peaters in
cat. 6 100 serial and the
 imped- cable be-
ance tween the two
repeaters
max. 5 meter
7 Switches in
serial
100BaseT4 8-wire 1024 per the Star 100 Mbps RJ 45 100 Meter Max. 2 Re-
Cat. 3 or whole network peaters in
better serial / 7
100  Switches in
imped- serial
ance
100BaseF 2-wire 1024 per the Star 100 Mbps ST, SC or 412 Meter @
fibre 50 whole network various Half-duplex
or 62,5 connector 2000 Meter @
m Full-duplex
1000BaseT 8-wire Star 1000 Mbps RJ 45 100 Meter
Cat. 5
100 
imped-
ance
1000BaseC 8-wire Star 1000 Mbps RJ 45 25 Meter
X Cat. 5
150 
imped-
ance
1000BaseS 2-wire Star 1000 Mbps ST, SC or 550 Meter @
X fibre 50 various 50 m
or 62,5 connector 275 Meter 62,5
m m
1000BaseLX 2-wire Star 1000 Mbps ST, SC or 5000 Meter @
fibre 9 various 9 m
m, 50 or connector 550 Meter @
62,5 m 50 m
550 Meter @
62,5 m
69
5.4.5 FDDI / CDDI
cial HW
FDDI 2-wire 500 DAS Sta- Dual ring 100 Mbps MIC 2 km from
fibre 62,5 tions station to sta-
m tion
100km the
whole ring
5.4.6 xDSL
cial HW
ADSL 2-wire Point-to-point Point-to- Down- 5.4 km @ 1.544 www.blackbox.com
copper point stream Mbps www.anixter.com
1.544 to 6.1 1.2 km @ 6.1 www.zyxel.com
Mbps Mbps
Upstream
16 to 640
kbps
CDSL 2-wire Point-to-point Point-to- Down- 5.4 km Proprietary
telephone point stream 1 technology
lines Mbps from Rock-
Upstream well and
128 kbps Nortel
HDSL 4-wire Point-to-point Point-to- 1.544 Mbps 3.6 km T1/E1 service
twisted point on two between
pair twisted pair server and
6-wire lines phone com-
twisted 2.48 Mbps pany or within
pair on three a company
twisted pair
lines
IDSL 2-wire Point-to-point Point-to- 128 kbps 5.4 km Similar to the
telephone point ISDN BRI
lines service but
data only (no
voice on the
same line)
RADSL 2-wire Point-to-point Point-to- Down- Depending on Not standard-
telephone point stream the transfer rate ised
line 1.544 to 6.1 up to 18 km
Mbps
Upstream
16 to 640
kbps
SDSL 2-wire Point-to-point Point-to- 1.544 Mbps 3.6 km Same as
twisted point (USA and HDSL but
pair Canada) requiring only
2.048 Mbps one line of
(Europe) twisted pair
VDSL Existing Point-to-point Point-to- Down- 1.3 km @ 12.9 VDSL is
2-wire point stream 12.9 Mbps currently a
telephone to 52 Mbps 900 m @ 25 draft version
lines Upstream Mbps
1.5 to 2.3 300 m @ 52
Mbps Mbps
70
Licenses
6 Licenses
For each product – MM8000, MK8000, MT8001, and NK8000 – a number of licenses
(ordering options) are available. Licenses needed depend on the system architecture
and size.
 For more details, please consult the “Details for ordering” section in the product
datasheet or contact your local sales distribution centre.
Be aware that actual calculations are available through the local sales channels.
71
Appendix A – Network connectivity options
The following matrix shows the connectivity options currently available for DMS800 systems.
KEY: DMS MM8000 and MK8000 MP4.10; MT8001 MP3.15 (Important: currently, MT8001 is not compatible with 4.10 and requires NK8000 3.15)
MM/MK MM8000 and MK8000 MP4.10
MM MM8000 MP4.10
Direct Direct CDI-Net
Network Cerloop NK8000
RS232 LAN GWxx
Connection
NK822x GW00 / 01
Upstream interface device
NK8225 NK8222 / NK8223 / NK8225 GW20 / 21
Upstream data-link protocol BACnet/IP CMSDL serial CEI 79-5 /IP CMSDL/IP CMSDL serial
Downstream network Direct Cerloop LAN Direct Cerloop Direct Cerloop Direct Cerloop Direct Cerloop Direct Cerloop
Downstream interface device - MK7022 - - MK7022 - MK7022 - MK7022 - MK7022 - MK7022
CS11 AlgoRex EP5 & EP7 DMS DMS MM/MK MM/MK DMS DMS MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK
FC700A DMS MM/MK DMS MM/MK MM/MK MM/MK
CS1115 MM/MK
FC330A MM/MK
CZ10 DMS DMS DMS MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK
CC60 DMS DMS DMS MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK
STT11 DMS DMS MM/MK MM/MK MM/MK
STT20 MM/MK MM/MK MM/MK
STT2410 MM/MK MM/MK MM/MK
SIGMASYS/D100 (field test only) MM/MK MM/MK MM/MK MM/MK
CS440 DMS DMS DMS MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK
CS4 MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK
Subsystems
CZ12 MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK MM/MK
CS6 Guarto (via LON interface) MM/MK DMS MM/MK MM/MK
SI410/420 Sintony MM/MK MM/MK MM/MK DMS MM/MK MM/MK
MF7033 / MM7033 DMS DMS MM/MK MM/MK MM/MK
CF9000 I/O DMS MM/MK MM/MK MM/MK
SIMATIC S7 MODBUS MM MM MM MM
SIMATIC S7 OPC MM
SIMATRIX, SIMATRIX NEO MM/MK MM/MK MM/MK MM/MK
Philips-Burle MM/MK MM/MK MM/MK
SISTORE AX, CX, MX, MXPro, SX MM/MK
TELSCAN MM/MK
IP cameras (*) MM/MK
SiPass ACC MM/MK
CerPass CC30 (via SiPass) MM/MK
ESPA Pager MM
Autronica BSxxx
LIST SCU 2000 (field test only)
MAXSYS PC601
CP100 MM MM MM MM
CDDL/CDSF units (field test only)
MODBUS units (field test only)
M5 R-card
72
Appendix B – Checklist
This checklist covers the networking and management station part of a project. It will help you to structure technical
details while you and the representatives of the customer or the consultant are in the specification phase.
Customer profile
System configuration
Migration status
Is the project a new system? Yes No
If no, are there parts to be migrated to the new system? Yes No
Is this a replacement of an existing system? Yes No
If yes, from which manufacturer?
Yes No
Do you have existing SBT subsystems to be migrated?
If yes, what type of subsystems?
rd
3 party integration
rd
Is it planned to integrate any 3 party subsystems?
Yes No
If yes, manufacturer and model of subsystem?
Do you know if this subsystem is supported by any of our gateways?

Yes No
If no, check with FS-DMS hotline to learn if this protocol is supported.
[email protected]
Phone: +49 89 9221 8000
Fax: +49 89 636 720 000
73
Network
Point-to-point (serial) connections
Are we in control of all the lines?
Yes No
Is the specification of all the cabling available?

Yes No
Are all lines to be used within the specification (distance limits)?

Yes No
Are leased lines / PSTN / ISDN lines to be used?

Yes No
Network connections
(a) Management station connectivity

How many management stations are foreseen?
Is a management level network foreseen (interconnection of different man-

Yes No
agement stations only)?
If yes, what type of management level network (Ethernet, Token Ring,

FDDI, ATM, etc.)
(b) Management station to gateway connectivity

Is a network planned to connect management station(s) and gateway(s)?
Yes No
If yes, what type of network (Ethernet, Token Ring, FDDI, etc.)
Is the network used exclusively for our safety and security applications? Yes No
Are we in control of the network? Yes No
If not, who is in control of the network?
What other data is transferred over the network?
74
(c) Network configuration

For each DMS-PC and Ethernet Port we need to know:
 IP-Address
 Subnet mask
 Default Gateway
Note: IP addresses must be static (DHCP not supported).
Who is the responsible person for the IP-addresses and router configuration?
Is a remote access neccessary?

Yes No
If yes, how? (IntERnet IntRAnet, dial-up)
Firewall configuration:
Are the necessary ports open?
TCP Port 3001…3004 (NK822x)
TCP Port 20 (FTP)
Yes No
TCP Port 21 (FTP)
UDP Port 47808 (BACnet) Yes No
Yes No
Yes No
Availability
Does the customer specify the network availability?
Yes No
Are there special requirements regarding error / failure rate? No

Yes
If yes, what are the requirements?
Is the power supply of the network components backed up by a UPS?

Yes No
Which components have to be attached to the UPS? (hubs, routers, ...)
Is a redundant backup line for the network planned?

Yes No
If yes, which type of dial-up (ISDN, PSTN, GSM)?
75
Siemens Switzerland Ltd
Building Technologies Group
International Headquarters
Fire Safety & Security Products
Gubelstrasse 22
CH-6301 Zug
Tel +41 41 724 24 24
Fax +41 41 724 35 22
www.sbt.siemens.com
Document no. A6V10063710_a_en DMS8000 Sales Material

Edition 06.2007 Section 4

Dms 8000

Uploaded by

Copyright:

Available Formats

Dms 8000

Uploaded by

Document Information

Original Title

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

Dms 8000

Uploaded by

Copyright:

Available Formats

DMS8000 MP4.

2 Management level configurations .......................................................15

3 Automation level configurations .........................................................20

4 NK8000 Application examples.............................................................55

5 NK8000 Network planning....................................................................60

Appendix A – Network connectivity options ......................................................72

About this document

The following describes one way to search and find a document:

Product and Document Name Document no. Date Last up-

MK8000 Interface Specifications

DMS8000 and Composer

MK8000 OPC Server:

Name Date Comments

 Management level (central evaluation)

 Automation level (local evaluation and data communication)

 Field level (data acquisition)

BAU (Siemens) Building Automation products.

DMS Danger Management System.

FS (Siemens) Fire Safety and Security products.

HVP (Siemens) Heating and Ventilation products.

LAN Local area network.

SES (Siemens) Security Systems.

WAN Wide area network.

1.1 Danger management systems

 MM8000 Management Station:

MM8000 also offers the following advantages:

 MK8000 OPC Server for Subsystems:

The OPC DA Server product allows us to technically integrate FS subsystems into

1.2 Connectivity – NK8000 networks

The following make up the NK8000 product family:

1.2.1 NK8222, NK8223 or NK8225?

 *See more about interactions in section 4.4.

1.3 Configuration – WW8000 Composer

2 Management level configurations

To see network connectivity options, refer to Appendix A.

2.1 MM8000 Management Station / MK8000 OPC Server configura-

2.1.1 Stand-alone configurations

Fig. 1 MM8000 or MK8000 stand-alone configuration (MM8000 shown)

2.1.2 Client/server configurations

Fig. 2 MM8000 / MK8000 client/server configuration TBS

2.1.3 Distributed configurations

The following are examples of distributed configurations:

Fig. 3 MM8000 / MK8000 redundant configuration with dual servers

Fig. 4 MM8000 / MK8000 + SiPass distributed configuration

2.2 NK8000 network configurations

2.2.1 DMS8000 Multiple host configuration – CMSDL/IP

Fig. 5 NK8225 DMS8000 CMSDL multiple host configuration

2.2.2 DMS8000 multiple host configuration – BACnet/IP

Fig. 6 NK8225 DMS8000 BACnet multiple host configuration

2.2.3 DMS8000 single-host configuration – support of dial-up connections

Fig. 7 NK8000 dial-up configuration

3 Automation level configurations

Automation level configuration types

Fire detection systems:

Intrusion detection systems:

Gas detection systems:

*Network Video Recorder

General automation and I/O systems:

 For details, see section 3.5.