DMS8000 Migration from DMS7000 Engineering Guide for: MM8000 MP4.
Data and design subject to change without notice. / Supply subject to availability. © 2008 Copyright by Siemens Switzerland Ltd We reserve all rights in this document and in the subject thereof.
About this document ............................................................................................... 1 Acknowledgments ................................................................................................... 3 1 Safety regulations ................................................................................... 4 1.1 Country-specific standards........................................................................ 4 1.
5 Hints and tips......................................................................................... 58 5.1 Suggested adaptations after the import of the data points. .................... 58 IV Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Safety regulations About this document Purpose of this document This manual is for use during the migration of a DMS7000 Danger Management System to a DMS8000 Danger Management System. The focus of this document is the substitution of the DMS7000 Management station products (central processor MC7003/MC7033, system console MA7003/MA7013/MA7033, compact system MT7023) with an MM8000 Management Station.
Safety regulations 1. Click on the "STEP WEB Client" image: Choose "04 Fire -3F" from the "Product Segment" box and select “Activate filter”. 2. Select “All” in the Documents section of the Quick Search page and select “Advanced Search”. 3. Enter the document number in the “Brochure No.” field (A6V10089056) and press “Enter”. Operational and safety regulations i Before groups of persons begin work on any DMS system, they must have read and understood the related documents.
Safety regulations Acknowledgments We wish to thank all the Siemens colleagues and the customers who have given us feedback and comments about this documentation. 3 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Safety regulations 1 Safety regulations This chapter describes the danger levels and the relevant safety regulations applicable for the use of FS-DMS products. Please read the following subsections, as well as the previous section "About this document" thoroughly before beginning any work. 1.1 Country-specific standards FS-DMS products are developed and produced in compliance with the relevant international and European safety standards.
Introduction 2 Introduction Siemens fire safety and security products are designed to work together. While there are many occasions where only one product may be used in a facility, when combined our products create a robust and flexible set of architectural and connectivity solutions. The possible combinations of Danger Management Systems (DMS), network choices, and subsystems used in any given plant are extensive. However the time involved with commissioning tasks can be substantial.
Introduction 2.2 Overview of DMS7000, DMS8000 system families and networks Siemens fire safety & security products are organised into three levels: Management level: Presents the events, and allows for control of the site via the management station(s). The majority of the human interface takes place at this level. Automation level: Provides data communication links between the other two levels and defines the network topology and structure.
Introduction 2.3 Additional documents Depending on your level of experience with Composer, and the architectural solutions available with our products, as well as where you are in the commissioning process, there are a number of additional documents that you may find useful. If you need a document that you don‟t have, you can download it through STEP on the Siemens Intranet.
Migration possibilities 3 Migration possibilities 3.1 Management station features As the same system software is used in DMS7000 by all family members, the only discrepancies result from hardware differences. All functions listed below are available throughout the DMS7000 family although restrictions due to shortage of disk or memory space cannot be excluded. 3.1.
Migration possibilities 3.1.3 On-line editors DMS7000 Supported in MM8000 SYSEDIT Off-line only Use Composer Doc.: MM8000 ICC Tool: Composer Text editing Off-line only Use Composer Doc.: MM8000 ICC Tool: Composer Password allocation Yes Standard Windows security Windows - - Language selection Not supported Date/time correction Yes Standard Windows clock Windows History Printout/Display Yes History browser – Option MM8000 History browser required Doc.
Migration possibilities DMS7000 Supported in MM8000 Migration procedure Reference / Reference documents / Tools Max. number of characters for data point description (level 1-5): 66 Yes (> 66 char.) See above. Doc.: MM8000 Operation, ICC Tool: Composer Max. number of characters per level: 35 Yes (> 35 char.) See above Doc.: MM8000 Operation, ICC Tool: Composer 3.1.
Migration possibilities DMS7000 Supported in MM8000 Migration procedure Reference / Reference documents / Tools poser: – Dependency of MM8000 organisation modes only. – Option MM8000 Scheduler and sequencer required Online text changes Partially supported Use MS Word for editing HTML pages. – Not supported for intervention texts in fast treatment – Supported for operating procedures with HTML step (HTML pages) e.g.
Migration possibilities 3.1.6 Graphics Graphic pages cannot be migrated. 3.1.7 Printer support DMS7000 Supported in MM8000 Migration procedure Serial printer Yes Use any printer supported by Windows. MP7011 Tape printer 40 char. No Use any printer supported by Windows. Reference / Reference documents / Tools Supported in MM8000 3.1.
Migration possibilities 3.2 Subsystem support Subsystem supported in DMS7000 Supported in MM8000 Migration procedure Reference / Reference documents / Tools CZ10 Yes Import from DMS7000 export-file See section 4.3.1 Docs: – DMS8000: CCG manual – MM8000: ICC manual Tools: – DMS7000:SWE10003 spec. – DMS7000:Exporter CZ12 Yes Import from DMS7000 export-file See section 4.3.2 Docs: – DMS8000: CCG manual – MM8000: ICC manual Tools: – DMS7000:SWE10003 spec.
Migration possibilities Subsystem supported in DMS7000 Supported in MM8000 Migration procedure Reference / Reference documents / Tools CC60 Yes No import available; to be configured manually in Composer Docs: – DMS8000: CCG manual – MM8000: ICC manual MT7000 (Terminal system) Yes (partially) No import available; to be configured manually in Composer See section 4.4.1 No import available; to be configured manually in Composer See section 4.4.
Migration possibilities 3.3 MF7013 / MF 7023 DMS7000 Supported in MM8000 Migration procedure Event command Yes Use Composer to configure reactions or convert MF7023 to a MM7033 reusing the existing hardware of the MC7033. Digital inputs Partially supported Use external I/O modules and use Composer to configure reactions. Or Convert MF7023 to an MM7033 reusing the existing hardware of the MC7033.
Migration possibilities 3.4.1 Time synchronisation DMS7000 Supported in MM8000 Migration procedure Time telegram is sent every 10 minutes to subsystems Time telegram is sent at system start-up and every day at 04 :00 Disable time synchronisation in DMS7000 (SYSEDIT), when operating both DMS in parallel Reference / Reference documents / Tools 16 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures 4 Migration procedures 4.1 Installing DMS7000 Tools 4.1.1 Installing DMS7000 Tree Editor SWE10003 spec. The DMS7000 Tree Editor SWE100003 spec. is available from the customer support centre (CSC) product support platform (PSP): http://psp.sbt.siemens.com:8080. SWE10003 spec. is a special version of the tree editor SWE10003, which can be executed in a DOS window under Windows (2000, XP). SWE10003 dos not require a HW-key. To install the DMS7000 Tree Editor SWE100003 spec.
Migration procedures 4.2 Creation of DMS7000 export files Check the CU macro node text Before creating the export files make sure that CU macro texts in the DMS7000 tree are not customised. CU macros with customised CU macro node texts are not recognised by the import function of the CZ10 and CZ12 subsystem tool of Composer. To check the CU macro node text, do the following: 1. Create in C:\SWE10003\DBS a folder . 2. Copy the DMS7000 files to the folder C:\SWE10003\DBS\. 3.
Migration procedures Correct non-default node text of the CU macro: Menu Node Define Node Name (see Fig. 2). The default CU macro node text has the following format: _/__ For example, for a CZ10 with local address 111: CZ10_/_111_ Fig. 2 DMS7000 Tree with default unit macro texts Save changes in SWE10003 (Menu Data Create MT7033 files; see Fig. 3). Exit SWE10003. Fig.
Migration procedures Create the DMS7000 export file To create the DMS7000 export file, do the following: 1. Launch the DMS7000 Data-Exporter. From the Start menu: Start Programs DMS7000-Tools Exporter (Fig. 4). 2. Click on the START export DMS7000-Data button. 3. Select your project .CFG. 4. Click on the Open button to start the export procedure. Fig. 4 DMS7000 Data-Exporter Fig.
Migration procedures Fig. 6 DMS7000 Data-Exporter: message .N04 missing Fig. 7 DMS7000 Data-Exporter: message .INX missing Fig. 8 DMS7000 Data-Exporter: message .GLB missing The DMS7000 Data-Exporter creates the following files: .TXT Tree structure .TX4 Intervention texts Check and replace special characters Special characters like äöü are not supported in the DMS7000 export file and have to be replaced before importing DMS7000 data in Composer.
Migration procedures 4.3 Subsystems 4.3.1 Import CZ10 data from DMS7000 export file To import CZ10 data from a DMS7000 export file, perform the following procedures in Composer: Adding a folder for the CZ10 system 1. Open the Composer project. 2. Create a folder for the Fire/CZ10 components. Adding a CZ10 system node 1. Select the new folder. 2. Select the CZ10 icon to add a CZ10 system node. Setting the CZ10 Local Address and the Vitality Timer 1. Select the CZ10 node. 2.
Migration procedures Fig. 9 Composer: Import data from CZ10 node Fig. 10 Composer browsing window: Selection of DMS7000 export file Fig. 11 Composer: Selection of CZ10 import data 23 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures 4.3.2 Import CZ12 data from DMS7000 export file To import CZ12 data from a DMS7000 export file, perform the following procedures in Composer: Adding a folder for the CZ12 system 1. Open the Composer project. 2. Create a folder for the Intrusion/ CZ12 components. Adding a CZ12 system node 1. Select the new folder. 2. Select the CZ12 icon to add a CZ12 node. Setting the CZ12 ‘Local Address’ and the ‘Vitality Timer’ 1. Select the CZ12 node. 2.
Migration procedures Fig. 12 Composer: Import data from CZ12 node Fig. 13 Composer: Selection of DMS7000 export file Fig. 14 Composer: CZ12 Import, language selection 25 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures Fig. 15 4.3.3 Composer: Selection of CZ12 import data Import CS4 data from SWE4 List file To import CS4 data from an SWE4 List file, perform the following procedures in Composer: Adding a folder for the CS4 system 1. Open the Composer project. 2. Create a folder for the Intrusion / CS4 components. Adding a CS4 system node 1. Select the new folder. 2. Select the CS4 icon to add a CS4 node Setting the CS4 ‘Local Address’, ‘Vitality Timer’ and ‘Sub type’ 1. Select the CS4 node. 2.
Migration procedures In a few moments, the CS4 structure is imported, and the node is represented in the Composer tree. Note: The CS4 node is renamed to match the metafile‟s name. To customise the name, click the node text, type in a new name, and press Enter. i Selecting the Import tab results in a page report being displayed. This contains the detailed logs of the latest import procedure, including all the added or removed objects. Fig. 16 Composer: Selection of CS4 List file Fig.
Migration procedures Imported with adding instance numbers Imported without adding instance numbers Fig. 18 Composer: CS4 import with/out adding instance numbers 28 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures 4.3.4 Import DMS7000 Tree To import DMS7000 Tree, perform the following procedures in Composer: 1. Add and then import the CZ10 and CZ12 control units included in the DMS7000 structure. Refer to the CZ10 and CZ12 import procedures, 4.3.1 and 4.3.2 respectively. Note: CZ10 / CZ12 subsystems must exist before importing the tree in order to enable Composer to link the fire and intrusion points to the geographical structure. 2. Add and then select a geographical tree in Composer. 3.
Migration procedures 4.4 Support of DMS7000 equipment in MM8000 During the commissioning phase of MM8000, it might be useful to run a DMS7000 equipment and a MM8000 Management station in parallel.
Migration procedures Setting the DMS7000 ‘Local Address’ and the ‘Vitality Timer’ 1. Select the DMS7000 node. 2. In the Node tab, set the „Local Address‟ and the „Vitality Timer‟. Please note that: The address value should match what is set in the local configuration of the unit. The Vitality Timer is related to the frequency of the heartbeat message periodically transmitted by the control unit.
Migration procedures 4.4.2 MF7033 Controls programmed in MF7033 do not generate messages that can be displayed in MM8000. If the states of the digital inputs shall be displayed in MM8000 or digital outputs have to be controlled by MM8000, a conversion of MF7033 to MM7033 is required. For a conversion of MF7033 to MM7033 you need to perform the following steps: Change in the systemdata file .
Migration procedures MM_IE4 M_DI_01_01_S ADF1: E1 ADF2: 01 MUX_01_01_S =1 telegram to MM8000 Active: MUX_01_01 NegLog: FALSE MM_IE4 M_DI_01_48_S ADF1: E1 ADF2: 01 MUX_01_48_S =1 telegram to MM8000 Active: MUX_01_48 NegLog: FALSE Customer pre logic telegram from MM8000 MF_TGO3 DMX_01_01_S Internal telegram MF_TGO3 Fig.
Migration procedures 4.4.3 MM7033 The following subset of MM elements is supported in MM8000: MM_IE4 for 48 digital inputs per E2A041 Multiplex module MM_OE1 for 48 digital outputs per E2A032 Demultiplex module MM_IE2 for 24 monitored inputs per E2A041 Multiplex module Other MM elements are currently not supported in MM8000. The following are the configuration procedures specific for MM7033 equipment after adding a DMS7000 node as described in section 4.4: Defining the detailed configuration 1.
Migration procedures 3. Configure the Instance Number (e.g. #1 in Fig. 22, #2 in Fig. 23, and #3 in Fig. 24). The Instance Number defines the object address in the DMS telegrams (ADF1 and ADF2; see Tab.1). You need to configure the MM7033 accordingly. A sample configuration is available on the PSP (DMS7000 – Equipment & Network components DMS7000 Version 57 MF7033 / MM7033 Release 0412). Fig.
Migration procedures Fig. 23 Composer: DMX_MM_OE1, 48 digital outputs (E2A032 DMX card) 36 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures Fig. 24 Composer: DMX MUX_MM_IE2, 24 monitored inputs (E2A041MUX card) 37 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures The table below shows the interrelationship between the Instance number and the DMS7000 telegram: MUX_MM_IE4 / DMX_MM_OE1 MUX_MM_IE2 Instance number Sector ADF1 ADF2 Sector ADF1 ADF2 1 P (E) E1 01 … 48 P (E) E1 01 … 24 2 P (E) E1 49 … 96 P (E) E1 49 … 72 3 P (E) E2 01 … 48 P (E) E2 01 … 24 4 P (E) E2 49 … 96 P (E) E2 49 … 72 5 P (E) E3 01 … 48 P (E) E3 01 … 24 6 P (E) E3 49 … 96 P (E) E3 49 … 72 7 P (E) E4 01 … 48 P (E) E4 01 … 2
Migration procedures Fig. 25 Link DMS7000 unit to a Cerloop network 4.5 Intervention texts 4.5.1 Intervention texts in DMS7000 The maximum size of a DMS7000 intervention text is 10 lines with 70 characters per line. DMS7000 allows you to assign and modify intervention texts using the SWE10003 Tree Editor, or using the on-line editor “Modify user text”.
Migration procedures 4.5.2 Fig. 26 SWE10003: Assignment of intervention text Fig. 27 SWE10003: Edit intervention text Intervention texts in MM8000 There are two ways to add intervention texts in MM8000: Intervention text that will be displayed in the event list in the fast treatment mode (see Fig. 28). Intervention text shown in an HTML page as a step of an operating procedure in the assisted treatment mode (see Fig. 30 and Fig. 31).
Migration procedures 4.5.2.1 Intervention texts in fast treatment mode In the fast treatment mode, intervention texts can be displayed in the event list (see Fig. 28): The maximum text length is 1024 characters. You assign intervention texts in Composer to specific data points. Multiple intervention texts can be assigned to the same data point depending on the MM8000 virtual properties. Disadvantages: The intervention texts cannot be changed online.
Migration procedures Configuration of intervention texts for fast treatment mode: 1. Select the data point. 2. Open “Event and OP Extensor view” (see Fig. 29). (A) Event setting: Uncheck “Use default”. (B) Select virtual property. (C) Intervention Text: Add text. Note: You can enter the intervention texts manually or by copying it from the DMS7000 export file .TX4 or the SWE1000r .LIS file. A B C Fig. 29 Composer: Configuration of intervention text 4.5.2.
Migration procedures Operating procedures can be assigned to all data points of the project or to specific data points depending on the MM8000 discipline types, virtual properties and operating modes. HTML pages can reside on any PC reachable through the network Disadvantages: The operating procedures (intervention texts) cannot be assigned online. High engineering effort if a large number of operating procedures have to be assigned to a large number of specific data points (no inheritance).
Migration procedures Fig. 31 MM800 assisted treatment: HTML-page in guided treatment mode Configuration of intervention texts for assisted treatment mode: For each individual intervention text, you need to configure an operating procedure and create an HTML page in Composer. Setting up operating procedures In the Composer project, the operating procedures are located in: Supervisor System Settings MM8000 System Logical Configuration data Operating Procedures.
Migration procedures 1 - Free treatment, if the steps should be available for the operators without a specific sequence of steps. A B Fig. 32 Composer: General operating procedure settings Adding new operating procedures When creating the procedures, do the following: 1. Select the Procedure icon to insert and name a new procedure (see Fig. 33). Fig. 33 Composer: Add a new operating procedure 45 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.
Migration procedures 1. In the node tab, confirm or change the default treatment mode (see Fig. 34, A). The option list includes two modes: 0 - Guided treatment: A list of steps guides the operators through the procedure (Fig. 31); 1 - Free treatment: No guided procedure is provided (see Fig. 30). 2. For Guided treatment, define the Sequential execution option (Fig. 34, B).
Migration procedures Object type: Area, section, zone, etc. Object sub-type: Manual call-point, automatic detector, etc. Discipline type: Fire, Intrusion, etc. Discipline sub-type: Detection, Extinguishing, Burglary, Theft, etc. These multiple selections will define a set of events for which the procedure will be automatically assigned. If more procedures will cover the same set of events, then one will be selected as default assignment, whereas the others may be manually assigned to individual points. 6.
Migration procedures A B C D E Fig. 36 Composer: Set the attributes for HTML step. Associate procedures to points Typically, the operating procedures are automatically applied to MM8000 points according to the typical event mapping. However, you can disable the automatic mechanism for some or all procedures: Enable Auto assignment: Un-check this box (see Fig. 34, D). In order to associate operating procedures to individual points, customise the Event and OP extensor tab with the following steps (see Fig.
Migration procedures Uncheck any selected operating procedures. Uncheck the box None. Select the operating procedure to be assigned. If you do not see all the previously defined operating procedures, it might be a refresh problem in Composer. In order to bypass this problem, select another data point and reselect the one you want to configure. Fig.
Migration procedures 4.5.2.3 Dependency of organisation mode DMS7000 allows the association of intervention texts depending on the organisation of the control unit where the data point belongs to (see Fig. 26). MM8000 allows the association of operating procedures (intervention texts on HTML pages) depending on organisation modes. Each operating procedure can be assigned to an organisation mode (see Fig. 34, F). Prior to this assignment, the organisation modes have to be defined in the scheduler node: 1.
Migration procedures Fig. 39 Composer: Scheduler, definition of special days 3. Assign the operating procedure to one of the previously defined operating modes (see Fig. 40, A). 51 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures A Fig. 40 Composer: Assign operating procedure to organisation mode 4. Optionally it is possible to define sequences, which are executed when the organisation mode changes: Define sequences (see Fig. 41) Define scheduler time programs (see Fig. 42) Link sequences to scheduler time programs Configure start condition for the sequence (see Fig. 40, A) 52 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures Fig. 41 Composer: Sequences A Fig. 42 Composer: Time program 53 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures The current operating mode is visible for the MM8000 user, when opening the Scheduler from the Menu Browsers (see Fig. 43, A). In the Scheduler it is possible to change the Day Type during runtime for the current date or any date in the future. This will influence the organisation mode depending on the configuration of the Day Type. Note: The current date is highlighted on the calendar, and if a Day Type was changed, it is indicated by a pencil for that date (see Fig. 43, B).
Migration procedures Fig. 44 MM8000: Intervention text for organisation mode “Close” Fig. 45 MM8000: Scheduler, organisation mode “Open” 55 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Migration procedures Fig. 46 4.6 Network 4.6.1 Cerban MM8000: Intervention text for organisation mode “Open” Direct connections to Cerban networks are not supported by MM8000. Possible migration scenarios: Cerban network in end-loop configuration Connect all existing data concentrators in an end-loop configuration.
Migration procedures Program MK7022 EPROM Connect MK7022 to MM8000: Note: NS8010 ISO1745 Driver is required on MM8000 Connect subsystems to NK8000 Network Install NK822x Ethernet Ports Connect subsystems via Cerban (or ISO1745 for CC114x) to NK822x Connect NK822x to the LAN Connect MM8000 to the LAN: Note: NS8210 NK8000 Network Driver is required on MM8000 4.6.
Hints and tips 5 Hints and tips 5.1 Suggested adaptations after the import of the data points. CZ10: The import function assigns to all imported data points the same symbol (10104). It is recommended to make the following changes: 1. For manual call point zones and detectors: The symbols should be adapted manually in Composer Points Extensor view (that is, replace the symbol 10104 with 10606 in the Points Extensor view; see Fig. 47). Fig. 47 Composer: Replacement of Point Icons 2.
Hints and tips Fig. 48 Composer: Children view, sorted column Description CZ12: The import function assigns the symbol (10403) to intrusion zones, the symbol 10404 for door lock control, and 10306 for all detectors. If the detector is not a door contact, the symbol should be changed to symbol 200 … 245; see Fig. 49 Fig. 49 Composer: Replacement of Point Icons 59 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
Hints and tips Create a geographical tree: 1. Insert Geographical node to the project. 2. Insert the nodes for plant corresponding to the tree structure of the DMS7000 topological tree. Note: By default, texts of generic folders are not displayed in the event bar. 3. Link the data points into the geographical tree. Fig. 50 MM8000: Plant browser, geographical tree as preferred view 60 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.
Hints and tips Fig. 51 MM8000: Event showing the text from the geographical tree 61 Building Technologies Fire Safety & Security Products 016_DMS_DMS8000_Migration_from_DMS7000_MP4.15_A6V10062443_a_en.doc 06.
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. A6V10062443_a_en Edition 06.
