MM8000 MP4.
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.
Table of contents About this document...............................................................................................1 Acknowledgments...................................................................................................5 Definitions of terms.................................................................................................6 Building Technologies Fire Safety & Security Products 1 Safety regulations .................................................................
II Building Technologies Fire Safety & Security Products 4.1 Configuration checklist ........................................................................48 4.2 MM8000: Defining system architecture ..............................................50 4.2.1 Setting up stations...................................................................................50 4.2.2 Setting station parameters ......................................................................53 4.3 Configuring printers ..........
4.11.4 Program the Sequence .........................................................................108 4.12 Configuring the Scheduler functions................................................114 4.12.1 Overview ...............................................................................................114 4.12.2 Setting up the Scheduler.......................................................................115 4.12.3 Configuring the Organisation Modes and Typical Week.......................
About this document Purpose of this document This manual is a guide to the installation, configuration, and commissioning procedures for the MM8000 Management Station MP4.10. Scope This document applies to the MM8000 Management Station MP4.10.
are unable to provide any guarantee with regard to content, entirety or quality of the details contained in this manual. We assume no liability for problems resulting from the use of this manual. The information 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. 2 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
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: 1. Click on the "STEP WEB Client" image: 2. Choose "04 Fire -3F" from the "Product Segment" box and select “Activate filter”. 3.
048 Autronica BSxx, ICC add-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 Connectivity add-on A6V10067792_a 06.2007 MP4.10 048 A6V10067796_a 06.2007 MP4.
Modification index Version A6V10062413_a_en 006799_i_en 006799_h_en 006799_g_en 006799_f_en 006799_e_en 006799_d_en 006799_c_en 006799_b_en 006799_a_en Date 06.2007 06.2006 09.2005 06.2005 03.2005 12.2004 02.2004 10.2003 07.2003 03.2003 Notes Corresponds to version MP4.10 of the MM8000 Software Corresponds to version MP3.20 of the MM8000 Software Corresponds to version MP3.15 of the MM8000 Software Corresponds to version MP3.12 of the MM8000 Software Corresponds to version MP3.
Definitions of terms Administrative tools An option in the MM8000 menu. This option is for use by service technicians to access the system supervisor browser, the Address book, and the Composer project configuration application. Applications An option in the menu on the Summary bar. When this option is available, it is the operator’s point of access to all other software applications available for use (for example, Microsoft Word) without needing to exit the MM8000.
Free treatment Geographical view Guided treatment A form of assisted treatment (the other is ‘guided treatment’). With free treatment, a series of treatment tools are made available for the operator to use as they deem appropriate to the situation. Actions performed during free treatment are not recorded in the history browser. A ‘view’ of the hierarchical tree of the plant browser.
PTZ camera A motorised video camera that can support a remote control for positioning (Pan/Tilt) and lens adjustment (Zoom). Reaction Can be pre-configured when automatic responses and actions should be triggered by a change of state. For example, acknowledging a fire alarm could trigger an output module to stop the ventilation system. Reactions can also call Sequences. See also – Sequence Scheduler Launched through the Browsers option in the Menu (located on the Summary bar).
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.
2 Introduction This is a guide to the software installation, configuration and commissioning of the MM8000 Management Station. From point-of-sale to project handover The following is an overview of the phases or steps that occur from the point-ofsale to project handover to the customer. Documentation that supports a given step is shown on the right-hand column; see Reference Documents at p.3. Note: The steps relevant to this document are in black, while the other steps are shown in grey.
2.1 What has been changed in MP4.10 configuration tools Here is the list of modifications included in MP4.10 for new functions and software improvements. Section, Page Modifications 3.1.2, p. 14 MM8000 software requirements: .NET framework 2.0 now required 3.2.1, p.18 3.2.1.1, p.18 3.4.3, p.30 4.2.1, p. 50 4.2.2, p. 53 New installation options for Marathon-based redundant solutions 3.4.1, p.23 New welcome screen and installation menu 3.4.2.2, p.
2.2 System dimensions and compatibility list Please refer to MM8000 MP4.10 Datasheet (document no. A6V10062415). Also, latest information and compatibility issues about the current software can be found in the product Release Notes (document no. A6V10062509). 12 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
3 3.1 Installation Installation requirements This chapter lists hardware and software requirements for installation of the MM8000 system. Note: the English edition of the required software is available on the MM8000 CD, all applications are distributed free of charge and can be installed with no need for purchasing a license. 3.1.
3.1.2 MM8000 software requirements This section presents the software requirements for installation of the MM8000 system. Note that the English edition of the required software is available on the MM8000 CD. Stand-Alone (and server) station Win2000 Professional or Server + SP4 -- or-- Win XP Professional + SP1 or SP2. Win 2003 Server + SP2 See notes about XP2 Firewall at p. 17.
Client stations Win2000 Professional + SP4 -- or-- Win XP Professional + SP1 or SP2. See notes about XP2 Firewall at p. 17. Network drivers installed, network configuration including TCP/IP protocol. Video applications required for SISTORE AX: – SISTORE AX RAS. Note: SISTORE AX software has to be installed before MM8000, else: see the post-installation utility ‘Init_CCTV_env’ at p.41. – Java Runtime Environment.
If no SQL Server is available, then the Microsoft SQL Server 2000 Data Engine (MSDE 2000) or SQL Express 2005 and SQL Backward Compatibility software can be installed before MM8000. MSDE 2000, SQL Express 2005 and Sequel Backward Compatibility are available free of charge on the MM8000 software installation disk. Note 1: The installation of the MSDE 2000 is described in a ReadMe file, and requires two steps: – Installation of MSDE 2000. – Update to MSDE 2000 Service Pack 3 (SP3).
Windows XP SP2 includes firewall software that should be disabled or re-configured for MM8000 software to work properly in two specific network configurations: – Distributed architectures with Client and/or FEP stations. – Architectures including NK8000 network devices. – In general, solutions including network communications (e.g.: Video Network, OPC services, etc.) or network file access (e.g.: Intranet HTML page in treatment).
3.2 Installation types 3.2.1 Selecting the MM8000 configuration MM8000 may be set up as a single station, as a distributed system, or as a station for performing project configuration only. The installation options include: # 1 Installation type Stand-Alone station (full-featured) Meaning Install all MM8000 software layers as well as Composer and the tools for configuring MM8000.
port an uninterrupted service even in case one of the two physical devices (or part of it) fails. The virtual machine creates a perfect environment for DMS8000 software to run with only one exception, concerning the license key, which requires to be installed on a physical port and handled by the physical machine. In fact, two identical hardware keys have to be installed on the same port of the two physical machines. The figures below show the architecture.
3.2.2 Selecting Windows configuration and related security The MM8000 can be installed on PCs either belonging or not belonging to a domain. In relation to the Windows environment, the security settings can be: Standard Security Local workstation (Windows 2000 / XP Professional) not belonging to a domain. In this case MM8000 access security will only be related to the local Windows domain, which is actually named after the network name of the PC.
The table below illustrates the possible security solutions in relation to the supported architectures. The recommended solutions (no.1 and 5) are marked with a grey background. # Windows network# MM8000 Architecture Windows Software MM8000 Security User management 1 Any Stand-Alone – Windows professional Standard security User management handled by MM8000 automatically.
3.3 Installation checklist The following two checklists tell you what you need for MM8000 installation, and steps you go through to install it. Items shown in grey are not covered in this guide. ITEMS NEEDED FOR INSTALLATION If SiPass is required on the same server, SiPass server software must be installed before MM8000. If required, CCTV application software (e.g. for SISTORE AX) should preferably be already installed. If required, OPC servers should preferably be already installed.
3.4 Installation procedure 3.4.1 Welcome screen The MM8000 CD provides a welcome page that guides you in the installation process. The page appears automatically when you insert the CD. In very special cases, if the ‘Autorun’ option is disabled on your PC, you need to execute the Autorun.exe file manually in the CD main folder.
3.4.2 MM8000 stand-alone station: installing the MS software 3.4.2.1 Installing the MSDE 2000 software On the MM8000 (and MK8000) Stand-alone station, if ‘SQL Server V8.00.760’ is not installed already (check the MS-SQL icon in the task toolbar, see Fig 4, and the related ‘About’ window, available in the right-click menu), you need to install the MSDE package provided in the MM8000 CD.
3.4.2.3 MM8000 stand-alone station: installing the SQLXML 3.0 software An extension to the standard MS-SQL software is also required for handling XML files. This is a free package from Microsoft named SQL XML 3.0. It is recommended to install this software after MSDE or SQL Express 2005 and SQL 2005 Backward Compatibility. In the ‘Pre-requisites’ menu, select the ‘Install SQLXML’ options and follow the installation Wizard (Fig 5).
3.4.2.4 MM8000 stand-alone station: installing the Microsoft .NET framework V1.1 MM8000 software requires the support of the Microsoft .NET V1.1 framework library. As with other Microsoft libraries, this package is distributed free of charge and can be easily installed selecting the corresponding option in the ‘Prerequisites’ menu. In the installation procedure, you only have to agree on the terms of the license agreement (Fig 7), press ‘Install’, and then wait for the software setup to complete (Fig 8).
Fig 10 Accepting the .NET Framework V2.0 License Agreement Fig 11 Successful termination of .NET framework V2.0 setup Although not strictly required for MM8000 operations, the recommendation concerning the .NET framework update (see Fig 11) should be follow. Please refer to Microsoft support site at http://www.microsoft.com/downloads and search for “.NET Framework” in the “Windows Security and Updates” section. Building Technologies Fire Safety & Security Products 27 048_DMS_MM8000_ICC_MP4.
3.4.3 MM8000 Software set-up The installation procedure is quite similar for Stand-Alone, Client, and FEP stations. 1. Logon to computer as Administrator (or equivalent account) in the local or global domain (for details ask your network administrator). For a discussion of domains, see 3.2.2, p.20. 2. If MM8000 is already loaded on the station: – Uninstall MM8000 Start Control Panel Add/Remove Programs MM8000 MPx.yy (or DMS8000 MPx.
– Restricted: this mode is related to the Windows configuration defined as Windows security only ( see 3.2.2 at p.20). When in restricted mode, you can get the control of the user account definition in the following ways (see Fig 13): – – The internal Windows account for the MM8000 application can be customised. The default setting is “DMS8000_Proc”. You can define any other username and password you want to use. MM8000 can be denied the right to add user accounts in Windows.
Fig 14 SQL server options The external SQL server can be defined as specified in the following Fig 15. Namely: – – The SQL server Name, as required to identify the Server in the network (for details ask your network administrator). The Authentication technique, which can be based on Windows or on SQL server. In the latter case, username and password must be entered. Fig 15 Defining the external SQL server 4e.
Fig 16 Selecting the automatic Server startup In the same window, you can set the dual server option and set specify the PC names of the physical machines supporting the Marathon EverRun FT environment. Note that the IP address is not valid. Refer to section 3.2.1.1 at pag.18. 4f. Server PC name If installing a Client or FEP station, enter the network name of the server (Stand-Alone) station. Note that the IP address is not valid. 4g.
Fig 18 DMS8000 setup complete 5. In the Windows event viewer, set the Application events properties. Proceed as follows: – – Right-click ‘My Computer’. Select “Manage” in the menu that appears (Fig 19). Fig 19 – Select ‘System Tools Event Viewer Application’ in the Computer Management tree (Fig 20). Fig 20 – My Computer menu Computer Management tree Select the Properties icon .
Fig 21 – 3.4.4 Application Properties window In the General tab, set ‘Max.log size’ = 512 KB and “Overwrite events as needed”. Then, click ‘OK’ and close. Attaching & activating the hardware key At this point, you need to connect and activate the hardware key for Composer and MM8000 and restart the PC. See DMS8000 Network, Fire and Intrusion Connectivity Guide (doc.n.007083). Reference Documents are listed at p.3.
3.4.5 Changing MM8000 language (optional) During the MM8000 setup procedure, the language can be selected so that the installed texts will be localised accordingly. However, in case the setup is not equipped with the language you want to use, the text localisation is still possible at a later stage using the ‘Language Installation’ utility. LOCALISATION CHECKLIST The following steps outline what you need to do to install a new language after the installation.
3.4.6 Testing Server and FEP communication After you have connected and activated the PAK, and rebooted the PC – as documented in the DMS Connectivity Configuration Guide (007083) - you should verify that the Server and FEP stations (if any) are communicating correctly. You do this with the System Supervisor Browser (Select Start Programs MM8000 System Supervisor Browser). For more information on the System Supervisor Browser, see p.140.
– Guest: guest users can open or restore a project, print, back-up, and download it. However, they cannot modify the project configuration. – Standard: standard users have the same capability as guests, and they also have the permission to modify projects. Instead, they are not allowed to use the User Manager tool. – Administrator: administrators have full control on projects (as for the ‘Standard’ profile) and also the permissions for using the User Manager tool.
Fig 23 Composer User Manager: selecting the new user The user and domain field are then displayed in the User Data window. You now need to specify the Profile and Level attributes (Fig 24). Then, select ‘OK’ to add the new user. Fig 24 Composer User Manager: setting user’s profile and level In a short while, the list will be refreshed and the new user included in it. In certain cases, a manual refresh may be necessary: in such a condition, use the icon.
3.4.8 OPC functions MM8000 software includes both OPC client and OPC server functions. In order to connect OPC client stations and enable them to communicate with the field units controlled by MM8000, you can enable the MK8000 OPC server functions, as described in the next section. Instead, in case MM8000 has to connect to OPC server that provide the data connection to field control units, the MM8000 OPC clients functions are used (new in MP4.10). Refer to the MM8000 OPC Connectivity Guide (document no.
3.4.8.2 Modifying an MM8000 installation into an MK8000 system Also, it is possible to change an MM8000 installation (i.e. the software installed with the MM8000 MP4.10 setup) to an MK8000-only system: see the ‘SwitchPT’ utility command described at p.42. The same command can also change back the system setting to MM8000. Note that, after having switched to an MK8000 system, Composer will only be able to create and download MK8000 projects. 3.4.8.
Composer User Manager – Allows adding and removing users enabled to ac- cess Composer (any project) and defining their capability. Composer users must be defined in Windows. Export Wizard, Inspector, and MK8000 Client are all tools for MK8000 OPC server and they are not discussed in this document (see MK8000 .ICC manual). Fig 28 40 Building Technologies Fire Safety & Security Products MM8000 applications 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
3.4.10 MM8000 technical utilities The following utilities are also installed along with MM8000 software, although they are not directly available on the programs menu. 3.4.10.1 Program utilities The folder: \Utilities\ contains various sub-folders with utility programs. Some of them can be used by you for specific purposes and are documented here. We recommend using these applications carefully. Also, do not start any utility program not included in the list below.
3.4.10.2 Utilities\Tools In ‘\Utilities\’, the subfolder ‘Tools‘ contains additional useful software components. The list includes: Engineering Tools This utility allows changing various internal options and initialising databases.
NK8210ConfigurationTool.exe This program initialises the IIS (Internet Information Service) for the NK8000 Web Server to work. It should be used when the IIS software is installed after MM8000 and requires a special initialisation. Set SQL server Password: SQL database security SetSQLServerPassword.bat – Set a non-default MSDE password. This can prevent unauthorised access to the history databases from external sources.
– Set_SwitchOver_Easy.reg (outgoing password is NOT required) To set back the request of outgoing operator’s password, use the command: – Reset_SwitchOver_Easy.reg (default mode) Composer debug mode (technical support use only) – ST_DebugYes.reg – ST_DebugNo.reg Set/reset the Composer debug mode for special technical tests. Default is no debug mode. Do not set this mode unless explicitly instructed by FS DMS support.
DCOM XP Log DCOMXPLogEnable and DCOMXPLogDisable allow for enabling and disabling the event logs of DCOM call failures (refer to Microsoft documentation about the CallFailureLoggingLevel registry key). Location Format The LOCATION_FORMA command defines some “special” characters used in the event line strings to identify specific behaviours of the user interface (UI). It may happen that the customer texts include any of these characters and the software fails to present the event line correctly.
3.4.11 Further MM8000 files 3.4.11.1 Sample projects The directory: \Sample Projects contains some pre-defined Composer projects that can be used for reference or for starting a new Composer project. The list includes: Empty Project.bak This provides an empty structure that can be used to start a project for special applications (e.g. Visual Builder). In both cases, the necessary subsystem tools should also be installed.
3.4.11.3 NK8000 firmware The latest release of the NK822x firmware is provided in the folder: \NK822x - Firmware The firmware is contained in a compressed (ZIP) file. For more information on NK8000, refer to DMS8000 Network, Fire, and Intrusion Connectivity configuration guide, see Reference Documents at p.3. 3.4.
4 4.1 Configuring the MM8000 Configuration checklist DMS8000 configuration process overview The configuration checklist is a general guide to the larger configuration process. The order in which you perform the tasks in the checklist may vary depending on your personal preference. This is not an absolute guide, but rather lends context to the tasks discussed in this manual. Note: A similar configuration list is provided in the Network, Fire, and Intrusion Connectivity configuration guide.
CONFIGURING MM8000 The following steps outline what you need to do to configure MM8000. Items shown in grey are not covered in this guide. Building Technologies Fire Safety & Security Products 1. Set up the Composer project ( DMS8000 Network, Fire, and Intrusion Connectivity configuration guide) 1.1 Create a new project 1.
4.2 MM8000: Defining system architecture When setting up your project in Composer, the first thing you should do is to represent your MM8000 architecture. If you use the MM8000 default project or one of the pre-defined sample projects (see 3.4.11.1 at p.46), most of the architecture will already be set up for you, and you can skip to the next step (refer to the configuration checklist at the beginning of this section).
Fig 30 Select MM8000 physical configuration for adding a station node 3. Click the station icon to display the station node menu. Fig 31 Select Station type 4. Add a FEP (optional; if you do not need a FEP, skip to the next step). Note: Distributed architectures may also need FEP stations that you can add as shown in Fig 32. Server-only stations necessarily require at least one FEP. Fig 32 FEP stations 5. Add the Network drivers.
In the Stand-Alone and in the FEP stations, you add the Network drivers. Depending on the type of network or unit to connect, there are different types of drivers. The procedure to add the driver is the following: – In the Stand-alone station: Select the Channel collection node – In the FEP station: Select the FEP node – Insert the required network driver(s) clicking the corresponding icon on the left toolbar. For detailed information, please refer to the connectivity guides.
Fig 35 License stations Note: License stations are defined in pairs and represent the two physical PC supporting a virtual redundant server 4.2.2 Setting station parameters For each Stand Alone (server), FEP, Client and License station, add a description, set the station name and IP address, and set the event selection mode by doing the following: 1. Select and expand ‘MM8000 system’ node: Physical Configuration 2.
Fig 37 Set station names and addresses: Distributed 3. Select the ‘Client Settings’ tab. 4. Choose the event treatment settings. Fig 38 See the descriptions following Fig 38. Event treatment settings Event Selection Modes Manual: The user manually selects the event and treats it. No action is under- taken by the system. This kind of selection can be combined with one of the two treatment modes: “User driven”, and “System driven”.
combined with one of two treatment modes: “Highest” (by priority), or “Any new event” (unrestricted). – Highest priority: When the user is treating an event, any new incoming event is processed only if it has a priority higher than the event currently being treated. In this case, the processing of the event the user was treating is automatically suspended. – Unrestricted: The system automatically enters treatment mode when a new event occurs, regardless of the event type, and what the user is doing.
4.3 Configuring printers Set up any printers that will be used by the MM8000 for: Journaling: Printout of each event change-of-state; Alarm printouts: Hardcopies of event-treatment text and graphics; Reporting: Various report printouts. MM8000 printers are “system-wide” printers and handled by the MM8000 Server station. They can however be physically connected by any station visible on the network 4.3.1 Setting up printers 1.
A B C Fig 40 A B C Select printer type System Journaling - A journaling printer is used to record system activity System Reporting - History reports System Alarm Printout - Alarm printouts are used as part of the event treatment procedures 4. Select the printer to use by selecting ‘Browse’ from the Node tab of the printer (Fig 41). Alternatively, you can specify directly: Model Comment Host computer Share name Location Fig 41 Optional field where you can indicate the printer model Optional field.
Fig 42 Browsing in the network for selecting the printer 6. Select the printer and click ‘OK The printer information will be automatically set in the Composer form (Fig 43). Fig 43 Selected printer Network printers must be enabled by the administrator for the internal MM8000 user, which is defined during installation (by default ‘DMS8000_proc’, although it could be modified by the ‘Special_UT’ command, see 3.4.10.1, p. 42).
7. Setting journaling template The Journaling function also requires that the printer get linked to one of the journaling templates available (Fig 44). Currently, the template list includes Journaling templates Description 132x60 Line Printer Complete Printout template for 132-column line printer. Objects are described by a full location path that includes the entire tree. A4 Page Printer Complete Printout template for A4 laser or ink-jet printer.
8. Setting Alarm Printout options The alarm printer has to be linked to the Alarm Printout steps of the Operating Procedures (see 4.9 at p.84) that require this function (Fig 45). For each of these links, a new node is added and a specific set of options can be defined as shown in Fig 46. Fig 45 Linking Alarm Printer to the Operating Procedure printout step Fig 46 Setting alarm printout options The option list includes: – Paper Size: A3 or A4.
– Number of printed copies. – Printout template: Alarm printout templates Example (A4, event description, operating procedure, map, and 2 pages) Resize the map on the first sheet. Concatenate all information keeping the original size. Fit all information in one sheet. Building Technologies Fire Safety & Security Products 61 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
Fit maps and pages on the same sheet, starting from the second. Always print maps and pages on separate sheets. 62 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
4.4 Setting up DMS project security Once you have finished setting up the Composer project structure as detailed in the DMS Connectivity configuration guide, you are ready to configure the MM8000 system behaviour. The first step is setting up MM8000 security, which is organised in two basic criteria: User groups and Security profiles. 4.4.
A E B C D Fig 47 A B C D E Security profile example Users belong to a user Group User groups are linked to a Profile In the Profile, Groups get a Permission Type Nodes in the tree are associated to a Profile; by default, the profile association is inhered from the parent node The Profile association defines the Permission type of the Group (and related Users) on the node 4.4.2 Setting the domain name 1. Select the Domain node: Security Users Domain and then select the Node tab. 2.
Fig 48 4.4.3 Setting the security domain. Assigning user group permissions By default, there are eight user groups organised in incremental capability levels. However, new groups can be added and the default groups renamed.
Composer Enable the access to Composer. Note that users also need the authorisations configured in the Composer User Manager. System Supervisor Browser Enable the access to the supervision tool ( p.
4. Select the ‘Event Settings’ tab to change event treatment permissions (Fig 50). Namely: Fast Enable/disable the fast treatment mode. Assisted Enable/disable the assisted treatment mode. Check ‘Protocol’ if you want to enable the treatment protocol in the detailed view. Protocol Enable the display of the event history log Source commands Enable the actions available during the event treatment: – Close event – Close the command-in-progress dialog.
Fig 51 4.4.4 System Settings: modifying default system permissions for a user group Adding users and user groups Add user groups 1. Select the Users folder (see Fig 53). 2. Select the domain node. 3. Click the User Type icon to insert a new user group. The name assigned to the new group is ‘User Type #1’, ‘User Type #2’, etc. and can be customised in the tree or in the Description field of the Node tab. 68 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.
Fig 52 Add user groups Add users to the user groups 1. Expand the Users folder and the domain node to display the user groups. See Fig 53. 2. Select a user group. 3. Click the User icon to insert individual users under the user group. Note: By default, one user belonging to the project administrators group is already present in the project (it is the Windows user who created the project).
4.4.5 Assigning security profiles Each user group is associated to at least one Security Profile. Once you assign a group to a profile, you set the access permissions for that group (for example, whether they can send commands in the plant browser, or only see a display of what is going on). Note: Users with display only permissions in the plant browser can still treat events in the event list. For this activity, you will need a number of data from the customer. See p. 150 for a full list of data needed.
– 3 Only Ack – Read and Acknowledgement command – 4 All Treatment commands – Read and all commands available in event treatment (Ack, Reset); – 5 Define a customised command permission type, which can be defined in two steps: – Treatment commands: None, Ack, Reset, Both – Other commands: None, Active (change from default), Deactive (move back to default), Both Associate nodes to a Security Profile For every control unit (or other type of node) that requires a profile other than the default, associate the
4.5 Downloading the configuration as a 1st check A download is recommended at this point in the configuration process so that you can more easily track the source of any potential problems during download. You may find it useful to perform a full download now, logon as the different users that you have configured, and verify that the requested security is actually in place.
4.6 Customising general event settings 4.6.1 Overview In MM8000, an event is generated when a property of a point modifies its condition as a result of an internal or external occurrence. However, not all changes of status will result in an event - a default setting is provided to generate an event only when an operator reaction is presumably required. There are seven event categories that are associated to seven coloured lamps on the MM8000 user interface.
4.6.2 Event settings In the Node tab of ‘Supervisor System Settings MM8000 system Logical Configuration User Data Events and Points’ (see Fig 58), you can configure the event generation styles. Specifically: Max Event Number. This is the maximum event number shown by the Server. When the maximum number is reached, the next event is generated starting from 1. Enable Auto-Acknowledge. Set this flag to globally enable the automatic ac- knowledgment.
4.6.3 Point types and virtual properties The default settings that are associated with any point type and its property can be changed. For example, you may want auto-close disabled for a type of fire alarms. In ‘Supervisor System Settings MM8000 system Logical Configuration User Data Events and Points Style’ (see Fig 59), you can configure the default event style associated to the properties of each point type. First you have to select the subsystem and the point you want to modify.
4.6.4 Point icon customisation 4.6.4.1 Global modifications In the event style page (‘Supervision System settings MM8000 system Logical Configuration User Data Events and Points Style’, Fig 59) you can configure the icon associated to the point types. This icon is used for all the instances of the point type. In order to modify it globally, i.e. for all those point types of all control units, select a new icon in the drop down list (see Fig 60).
Click ‘Add icon’ to select the icon file (ICO Windows file) to add. The imported icons show in the collection space illustrated in the following Fig 62. When a new icon is present in the Custom Icons Collection, it is immediately available for selection in the drop down lists of either global (4.6.4.1 above) or individual (4.13.2 below) point customisation. In order to delete an imported icon from the MM8000 project, select the image in the collection space and click ‘Delete icon’.
4.7 Configuring the geographical tree 4.7.1 Overview Most end-users will find it easier to navigate in the plant browser using a geographical view (as opposed to logical or physical view typically imported from the local subsystem configurations). The geographical view represents a facility or structure in the way the operator knows it – the way it exists physically.
Note: In case only part of the control units have been created and imported, the geographical tree import creates the entire structure anyway, and links only the existing and imported CZ10/CZ12. 4.7.4 Setting up the geographical tree 1. Add one or more geographical trees to the project: select the icon shown in Fig 63. Fig 63 Adding the geographical tree 2. Set the linking mode: single node (uncheck the box in Fig 64) or subtree (check the box) Fig 64 Setting linking mode 2.
A B C D E Click to add a new Building in the geographical structure Click to add a new Floor in the geographical structure Click to add a new Section in the geographical structure Click to add a new Room in the geographical structure Click to add a new Generic object in the geographical structure 3. Drag points (subtrees) from the logical tree of the control units to the room in which they are located.(see Fig 66).
4.8 Configuring graphical Maps 4.8.1 Overview MM8000 can handle large Maps, representing an entire building floor with as many dynamic points as required. Maps can be navigated with zooming and panning controls. They are organised in multiple layers, which can be background or foreground layers. At least one background and one foreground layer are present in any map. Map layers contain graphical objects, which own a number of properties.
Fig 68 Map organised in multiple depths with increasing level of functional details Individual points can be associated to one or more Pages. An MM8000 Page is a view, at a selectable zooming factor of a depth. The association between points and Pages can be provided automatically by MM8000 tools and/or left to a manual setting (see section 4.13.2, p.122). Automatic association can be disabled in ‘Supervisor System Settings MM8000 System Logical Configuration Point Page Extension’.
4.8.2 Setting up graphical maps In the Composer project, Maps are located in ‘Supervisor System Settings MM8000 System Logical Configuration Graphic Maps’. 1. Create a folder structure (for example, ‘fire graphics’ or ‘intrusion maps’). 2. Insert and name your new maps in the first folder. 3. Define the map size, following the wizard during first edit session. 4. Configure a background layer. Import CAD or image files and/or drawing of your own. 5. Define the foreground layers. 6.
4.9 Customising Operating Procedures 4.9.1 Overview The Operating Procedures consist of a sequence of steps or actions that the operator will have to perform with the assisted treatment mode. For each step of a procedure, MM8000 can provide instructions and operating tools. Defining Operating Procedures is required to enable the assisted treatment mode. With no procedures defined, MM8000 will only provide the fast treatment mode.
4.9.2.1 Adding new Operating Procedures When creating the procedures, follow these guidelines: 1. Insert and name a new procedure (Fig 71). Then, proceed with the general definitions as instructed in the following steps. Fig 71 Add a new Operating Procedure 2. In the node tab, confirm or change the default treatment mode (Fig 73). The option list includes two modes: – Guided treatment: Operators are guided through a number of procedure steps.
Fig 72 Linking a scope subtree to an operating procedure 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 (see 4.13.2). Fig 73 Operating Procedure definition 5. ‘Use as default’: set this procedure as the default Operating Procedure.
lecting this option will prevent any use of the procedure apart from manual assignments to specific points (see p.123). 7. Configure the sequence of procedure steps. Choose from the available icons to insert the steps in the order that they should be followed. Note: Their order in Composer will be the same as in the MM8000. 8. Define Operating Procedure steps (Fig 74): A.
Fig 74 Operating Procedure step types 9. Set the attributes for each step. – Repeatable: Set this flag to allow the selection of the step once it has been executed and checked. The step can be re-selected but not re-checked. – Step title: Set the title of the step, as it will appear in the procedure. – Step description: Set the description of the step, as it will appear in the procedure. Note: Titles and descriptions can also be globally defined in the Operating Procedure node, see 4.9.2.2 at p.90.
Operating Procedure step: summary table # Step types Parameter(s) A Application step - Application pathname - Application parameters (optional) Example / notes – – - B Generic text None C HTML page - URL D Map None E Report None F Alarm printouts - Print Pages (associated to point) - Print Map (associated to point) - Print Operating Procedures - Attachment See example at p. 146; see printer configuration and options at p.60..
Fig 75 Operating Procedure step attributes (example, CCTV step) 10. Define all the steps that you need in the order you wish the operator to see them. 11. Repeat the steps above for all other procedures. 4.9.2.2 Operating step titles When several procedures and steps are defined, it is necessary to organise the step titles and descriptions. This is done from the Step Descriptions tab of the Operating Procedures node (Fig 76). Here you can modify titles and descriptions as well as add new ones.
Fig 77 Operating Procedure report types 4.9.2.4 Event dispatching text In the ‘Event Dispatching Text’ tab of the ‘Operating Procedures’ node you can add or remove texts that can be used in the steps handling dispatching functions (e.g. SMS step). See the following Fig 78. Fig 78 Operating Procedure dispatching texts 4.9.2.5 Associate procedures to points Typically, the Operating Procedures are automatically applied to MM8000 points according to the typical event mapping (Fig 73, p.86).
4.9.3 Configuring the Dispatching Services 4.9.3.1 Overview In the Operating Procedures (described in 4.9 at p.84), the MM8000 can support the event dispatching over e-mail, SMS services, and ESPA Paging systems. All these functions require the definition of general parameters as described in this section. 4.9.3.2 Configuring the e-mail service The e-mail service must de defined in: Supervision System settings MM8000 system Logical Configuration User Data Dispatching Services Email.
The form illustrated by Fig 80 appears. Fig 80 SMS service settings 3. Uncheck the ‘Disable’ field. 4. Configure the SMS service. The SMS service can be managed via GSM or e-mail. Select either of the two options. 5. Configure the GSM connection. If a GSM modem is used, check the documentation of your GSM modem and the installation settings on the MM8000 PC. Then, fill in the required physical line settings (port, bps, parity, data and stop bits) and the PIN code. 6. Configure the e-mail connection.
Fig 81 A Adding the ESPA Pager tool Click this icon to add the ESPA Pager as Operating Procedure tool You can now configure the ESPA parameters. Proceed as follows: 1. Select the node: Supervision System settings MM8000 system Logical Configuration User Data Dispatching Services 2. Select the ‘Pager’ node and then click the ‘Pager’ tab You can configure the following parameters (Fig 82): – Disable ‘Pager Dispatching’. Use this global option to entirely skip the Pager steps.
Fig 82 Building Technologies Fire Safety & Security Products Configuring the ESPA parameters 95 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
4.10 Configuring Reactions and Manual Triggers 4.10.1 Overview The MM8000 can be configured so that when a specific situation occurs, a command or series of commands is automatically executed. This series of commands is defined in Composer, and then is configured to automatically start when triggered by specific conditions in the field, or manually by an operator through the MM8000 interface.
Fig 83 Reaction main folder 4.10.2 Setting up Reactions Below is an overview of what you need to do to create a Reaction. 1. Define a new Reaction. – Insert the Reaction node. – Define the reachable option. 2. Define Manual Triggers if necessary (in a separate folder). 3. Configure the Reaction: – Link trigger points and Manual Triggers under the Reaction node. – Link the effect points and the Sequences under the Reaction node. – In the guided editor, define the Reaction program. 4.10.
– Name the Reaction in the Description field. – Leave ‘Reaction enabled’ checked. – Check ‘Transition to reachable’ if the Reaction includes triggers related to normal states set just after the status request. Fig 85 General Reaction settings 4.10.4 Defining Manual Triggers Manual Triggers are virtual points, acting as a simple on/off switch, which enable the operator to initiate complex Reactions with simple commands.
Fig 87 Adding a Manual Trigger Fig 88 Manual Trigger description 4.10.5 Configuring the Reaction Triggers and effects can be related any of the points in the Composer tree, including Manual Triggers. Points are linked to the Reaction node using the standard drag and drop technique. The states and commands available depend on the nature of the point. Prior knowledge of the control unit and its behaviour is needed for this phase. 1.
Fig 89 Linking triggers and effects 2. Program the Reaction logic Select the node of the Reaction and then the ‘Reaction Editor’ tab. In the page that appears you can define the Reaction logic filling in the following fields (Fig 90): Note: Text field for your free comments View type. Selection field that can change the way trigger and effect names are shown. Namely: Customer text, Technical texts, All (both customer and technical texts). Reaction program.
3.B Enter the trigger list, you can select the following statements/conditions clicking on the left menu: – Comment: To enter a text line. – – Field condition: To specify an input state. OR/XOR: To enter a logic operator and combine two conditions. Note 1: The AND logic applies by default when more conditions present. No explicit operator is required. Note 2: If multiple logic operators are combined in the same program, they are executed in this order: AND, OR and then XOR.
Access Control Transaction: – If an AC door is linked to a reaction, then you can check the transaction for a configurable Transaction Time. When occurring (instantaneously), the transaction is evaluated during a period of time (Transaction time) that allows other conditions (e.g. alarm states or other transactions) to happen and be tested along with the transaction. – Organisation mode condition: test the current MM8000 scheduler organisation mode (refer to the MM8000 Scheduler functions) 3.
The commands are specified indicating: – Field point: In the list that appears, click one (or more) of the points linked to the Reaction; the points are listed with their customer text, technical text, or both (see 2 at p. 100). – – Property: Open the drop-down list and select one of the properties of the point, typically “Active” or “Off”. The list of properties depends on the specific point. Command: Define the actual action, which one of the following: – Quiet: Set to normal state.
Fig 91 Reaction program Tip: The list of states also contains a special state called ‘Default’, which is equivalent to any of the following: Active, Acknowledged active, Unacknowledged active. In practise, it can be used to select the active state, regardless of whether the acknowledgment applies or not. Note: commands sent out to control units that are not reachable are lost. 104 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
4.11 Configuring Sequences 4.11.1 Overview In MM8000, the Sequences are macro programs configured in Composer and then downloaded for execution at runtime. A Sequence is made up by a number of instructions, including control and calculation statements as well as conditional operators and loops. You can also test the status of field objects and send out commands. Additionally, intermediate results can be stored in local or global variables and then used for further processing.
4.11.2 Setting up Sequences Below is an overview of what you need to do to create a Sequence. 1. Define a new Sequence. – Define the general options in the main node: log file and behaviour with maintenance points. – If required, add general variables. – Add a new Sequence node. 2. Program the Sequence. – In the guided editor, define the Sequence program. 4.11.
2. Click the Sequence icon to insert a new Sequence node in the Composer tree. i Note: When working with a large number of items, you may want to organise them using sub-folders as shown in Fig 93. Fig 93 A B Add a Sequence or a folder of Sequences Add a Sequence Add a folder of Sequences 3. Define the Sequence settings in the Node tab (see Fig 94). – Name the Sequence in the Description field. – Leave ‘Sequence enabled’ checked.
4.11.4 Program the Sequence The Sequence can operate on any point in the Composer tree. Affected points are linked to the Sequence node using the standard drag and drop technique. The states and commands available depend on the nature of the point. Prior knowledge of the control unit and its behaviour is needed for this phase. 1. Drag and drop the points to the Sequence node (Fig 95). The point displays as a link in the Sequence. Fig 95 Linking triggers and effects 2.
Fig 96 Starting the Sequence programming Note: In case of invalid programming, the erroneous lines show in colour (yellow) and a warning is displayed on the top (“The Sequence is not valid“…, see Fig 97). The tooltip text, shown when the mouse’s pointer is moved on the yellow areas (in the example the IF clause), indicates the detailed reason of the warning. Fig 97 Invalid Sequence 3. Edit the Sequence program. Proceed as follows: 3.
3.C Enter the instructions; you can select the following: Statements: – comment: To enter a text line. – – – – – – send command: To specify a control action. wait: To insert a programmable delay in the action list. call Sequence: To call another (valid) Sequence, which can run asynchronously (the caller does not wait for it to complete) or synchronously (the caller waits for it).
The field conditions are specified indicating: – Field point: In the list that appears, click one of the points linked to the Sequence; the points are listed with their customer text, technical text, or both (see 2 at p. 108). – – – – – – – – – – Property: Open the drop-down list and select one of the properties of the point, typically “Active” or “Alarm”. The list of properties depends on the specific point.
The commands are specified indicating: – Field point: In the list that appears, click one of the points linked to the Sequence; the points are listed with their customer text, technical text, or both (see 2 at p. 100). – – Property: Open the drop-down list and select one of the properties of the point, typically “Active” or “Off”. The list of properties depends on the specific point. Command: Define the actual action, which one of the following: – Quiet: Set to normal state.
Fig 98 i Building Technologies Fire Safety & Security Products Valid Sequence Tip: The list of states also contains a special state called ‘Default’. This state is the equivalent of any of these: Active, Acknowledged active, Unacknowledged active. In practise, it can be used to select the active state, regardless of whether the acknowledgment applies or not. 113 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
4.12 Configuring the Scheduler functions 4.12.1 Overview During a day, a building can switch between different Organisation Modes, typically the open and closed modes, depending on the activities carried on by the people working or living there. The MM8000 can offer a mechanism to perform automated programs based on a schedule related to building Organisation Modes. These programs can enhance the existing schedules, typically programmed in the safety and security units in the field.
4.12.2 Setting up the Scheduler Below is an overview of what you need to do to configure the Scheduler: 1. Configure ‘Organisation Modes and Typical Week’. – Define the Organisation Modes of your building, and assign them a name and a colour. – Configure the day types, and assign them a name and a colour. – For each day type, assign time intervals to the Organisation Modes. – Define the Typical Week: set a day type for each day of the week. 2. Add the ‘Special Days’.
– Click the Colour cell and select the colour representing the Day Type in the graphics. As long as not used in the Typical Week, types can be removed as follows: – – Click any cell in the Organisation Mode’s line. Click the Delete button. 5. Define the Day Time Intervals: – In the Day Time Intervals area, select the first day type. – Press Add to add an interval. By default, the first interval starts at 00:00, whereas the subsequent ones automatically follow the preceding interval.
Fig 100 Scheduler dialog window 4.12.4 Configuring the Special Days Special days can be defined as follows: 1. Select the Scheduler node in: Supervision System settings MM8000 system Logical Configuration User Data Scheduler. 2. Select the ‘Special Days’ tab. The form illustrated by Fig 101 appears. 3. Define the special days: – In the Calendar, select the month by scrolling left and right the pages. – Click the day of the month. – Select the Day Type you wish to assign.
Fig 101 Special days calendar 4.12.5 Configuring the Time Programs Time programs are defined following to the following procedure: 1. Select the Time Program folder: Supervision System settings MM8000 system Logical Configuration User Data Scheduler Time Program folder. 2. Click the Time Program icon to add a new program (see Fig 102). Fig 102 Adding Time Programs A 118 Building Technologies Fire Safety & Security Products Select this icon to add a new Time Program 048_DMS_MM8000_ICC_MP4.
3. Select the Time Program node. 4. Select the Node tab. The form illustrated by Fig 103 appears. 5. Enter a comment. In the ‘Comment’ section, you can add a text that can help describing the use of the program. 6. Enter the Date setting. Here you can select to launch the program: – Every Day. – On a specific date, and optionally for the subsequent years as well (check ‘Repeat yearly’). – On a specified day of the week. – On a specified day type. 7. Enter the Time setting.
Fig 104 Reminder configuration 120 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
4.13 Customising individual points 4.13.1 Overview The behaviour of each point (or node) in the Composer tree can be individually modified in the tabs associated with each point. As described below in this section, you can: Modify the point description in the MM8000 plant browser. Change which icon is associated with a point. Exclude a node from the project (off-scan). Change which Maps and pages are associated with a point. Specify which point properties will generate events.
4.13.2 Node and Points Extensor tabs 4.13.2.1 Node tab In the Node tab you can modify the point’s Description text. The change also affects the node name in the Composer tree. Note: Imported text cannot be modified here. However, the ‘Point description’ can always be modified in the Point Extensor tab (see next step). 4.13.2.2 Points Extensor tab In the ‘Points Extensor’ tab (see Fig 105), you can customise: the following – (A) Point description: Point description is normally the same as Description.
Map views (automatic pages) are assigned to points according to the point allocation on the Maps themselves. However, a manual assignment can replace or be added to the automatic association (Fig 107). Fig 106 Event Treatment Pages tab Fig 107 Associate a page manually A B C D E Enable / disable assignment of an automatic page Assign manually a page De-assign manually a page Move a page up in the assignment order Move a page down in the assignment order 4.13.
Tip: if you disable all events by mistake, just click “Default settings” (see above) again to get back the entire event configuration for this point. Note however, that this will also clear all other customisations. – (B) Property-based event: Choose from the following: – – Which properties will and won’t generate events Event category; – Severity (it affects the event sorting within the category); – History and Journaling tracking logs.
Fig 108 Point Operating Procedures extensor tab A B C C1 C2 C3 C4 C5 C6 Building Technologies Fire Safety & Security Products Enable / disable all default assignments List of properties Selected property Default state of the property (no modification is normally required here) Close-off state of the property (no modification is normally required here) Enable auto-close of the property Enable auto-ack for the property Intervention text for the property Enable / disable the auto-assignment of op.
4.13.5 Camera Extensor tab In the Camera Extensor tab (Fig 109) you can see the camera associations and manually add one or more cameras. Video cameras are assigned to points according to the coverage area defined for the camera points allocated on the Map (see the DMS8000 Graphical Map configuration guide). However, a manual assignment can replace or be added to the automatic association.
4.14 Downloading the configuration 4.14.1 Backup your data When the configuration process is complete, do not forget to backup your project. Detailed instructions for this can be found in the DMS Connectivity Configuration Guide (EDMS no. 007083). After you have backed up the project you are ready to transfer the configuration to the MM8000 Server. 4.14.
Fig 111 Checking License Data If the check outcome does not confirm that all license values are correct, then you need to extend your license. Note that, depending on the missing license code, the download may or may not complete or the MM8000 may be limited in the available functions. The check requires that the MM8000 Server tasks run. If the tasks are not running, the following error message appears: “Runtime components not responding”.
Fig 112 Domain name Fig 113 Station name Both names can be found by right-clicking the My Computer icon on the desktop. In the menu list that displays, select ‘Properties Network Identification’. Note: In a Stand-Alone station not joined to a Server domain, the station name is also the domain name. Verify that the MM8000 folder in Explorer is not selected You may want to close the Explorer prior to download.
Making sure that the server tasks are running i Note: Before downloading the configuration, the MM8000 Server must be running. If during installation you enabled MM8000 Server auto-start (p.30), then the server tasks automatically start after any reboot. If you opted for Manual start, you need to launch the MM8000 Server now; select the following: StartProgramsDMS8000Start DMS8000 Servers.
4.14.4 Downloading configuration to MM8000 To download the configuration, do the following: 1. Launch the System Supervisor Browser. Start Programs MM8000 System Supervisor Browser. 2. Wait for the Server and any FEP station icons to turn green. 3. Select a station icon in the left pane. 4. Verify that all the items listed in the right pane turn green. 5. Repeat steps 3 and 4 for each station. 6. In Composer, select the project node in the tree, and then select ‘Download’ from the Tools menu.
4.15 Setting the passwords of new users If you created users in Composer that were not already in the windows domain, their profiles will have been created automatically during the configuration download, provided that the MM8000 Server is running on the (possibly local) windows domain server. During download, Composer sets the default password ‘MM8000_pwd’ and you will need to go into user profile at the windows operating system level and modify their passwords. Use the standard Windows commands: 1.
4.16 Activating the MM8000 closed mode In the Standard Security setting (see 3.2.2 at p.20), to activate the MM8000 so that it is completely operative and the Operator Switchover function is enabled, launch the LockSystem.reg utility. Once activated, when an MM8000 user logs into the station, the MM8000 will be automatically launched. To activate the system 1. Log in as an MM8000 administrator (otherwise, you will be logged off the PC during the next step). 2. Close the MM8000 Clients. 3.
Windows 2003 Server Note that the lock procedure does not work on the Windows 2003 Domain Server unless an additional modification is made to the local security policies in order to enable the auto-logon (see figure below). To deactivate the system To disable the automatic launch of MM8000 upon MM8000 user login, deactivate the system. 1. Log in as an MM8000 Administrator. 2. Close the MM8000 Clients. 3. Double-click the ‘UnlockSystem.reg’ in the MM8000\Utilities\Reg folder.
DixieDefaultUserPassword = “” (leave blank) Reboot the PC, logon and you will get again the usual Windows interface. Building Technologies Fire Safety & Security Products 135 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
5 Testing the configuration Once the configuration has been downloaded to the MM8000, you need verify that the MM8000: Is running on the stations; Has been configured correctly; Communicates correctly with the subsystems. The following test should be started while the MM8000 is still disconnected from the subsystems to verify that the configuration performed in Composer is correct.
6 Reports MM8000 tools can provide a number of file reports (CSV format). Depending on the specific project, the available reports may be: Points deposited on Maps (or not deposited). Points associated with Operating Procedures (or not associated). Points involved in Sequences (or not involved). Points involved in Reactions (or not involved). Points associated with video cameras (or not associated). Points linked to the geographical tree structure (or not linked).
Fig 114 Export commands (example) 138 Building Technologies Fire Safety & Security Products 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
Examples of reports The export output is a text file, CSV format. See p.161 for some useful information about this type of file.
Appendix A - System supervision and event simulation A1 - System Monitor The System Monitor is an application that is installed with the MM8000. As its name implies, it monitors the MM8000 system and reports the status of the server and FEPs. In general, the System Monitor helps you quickly perform the following tasks: – Check the MM8000 status at a glance (for example, whether or not the MM8000 server is running). – View which stations are connected to the MM8000, and if they are running.
Fig 116 System Monitor right-click menu: Server is running, therefore the ‘Stop’ command is available Fig 117 DMS8000 information window (note that the version displayed in this picture may not match the official product release). Advanced menu The Advanced menu includes – Start Server in Simulation Mode: start the system with an additional application that allows simulating field events (described on page 142).
A2 – Simulating field events Starting the MM8000 Server in Simulation mode In the Advanced menu, you can start the MM8000 server in simulation mode. This mode results in starting an additional application (Field Simulator), which allows generating messages as though they were coming from the fire and intrusion control units in the field. Field Simulator The Field Simulator presents a user interface quite similar to the MK8000 Testing Client application (refer to the MK8000 ICC Manual).
A3 – Simulating from a networked computer The Field Simulator program can also run on a separate computer and connect to the MM8000 server over a LAN connection. However, this solution requires a special setting. General requirements: The simulation PC should be properly networked and equipped with MM8000 as it were a client PC (see notes about client/server settings on 3.2.2 at p.20). Setup procedure: Start the MM8000 server in simulation mode with the exact configuration to simulate.
A4 - Using the System Supervisor Browser The System Supervisor Browser can be launched from the MM8000 System Monitor menu in the Windows tray (Fig 116 above) or through the Windows Programs menu (Start Programs DMS8000 System Supervisor Browser). The browser shows the running MM8000 stations (Fig 120- A) and the associated tasks (Fig 120- B). If the list on the right hand side does not include a station, it means that the MM8000 software is not running.
Appendix B - Enabling Server auto-start During normal use of the MM8000, it is convenient to have the MM8000 Server start automatically upon system start-up. During troubleshooting and system testing, however, it may be more convenient to disable auto start. To change the auto start settings, do the following: 1. Open the services menu: Desktop Right-click My Computer Manage Services and Applications Services). 2. Select Dixie System Supervisor. 3.
Appendix C - Alarm printout (example) 1 General information Event information, Operating Procedures, and Map. Depending on the amount of data and on the configuration settings, texts and graphic may be allocated in one or more printed pages. Alarm Printout: Severe Alarm Fire alarm 8/29/2005 4:32:59 PM In operation Building A . Fire Protection . CZ10 #111 . Fire sector .
2 Graphic Map and Page(s) Depending on the graphic size and on the configuration settings, graphic Map and Pages may be allocated in one or more printed pages. 03/08/2005 16:30:48 Building Technologies Fire Safety & Security Products Page 2 of 2 147 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
Appendix D - Special settings MM8000 can provide more flexibility than what is possible with the configuration tools described in this document. This section contains further information for more advanced settings. Note: What is described here is not part of the current Composer projects for MM8000 and cannot therefore be saved and moved with the project backups. It will be up to you to keep track of the modifications and possibly re-enter the advanced settings in newer versions of MM8000 or Composer.
Fig 122 Setting dual history Server Building Technologies Fire Safety & Security Products 149 048_DMS_MM8000_ICC_MP4.10_A6V10062413_a_en.doc 06.
Appendix E- Customisation checklist Customer Customer Reference - Order # Internal Reference -Job # Date Product/Version (MM8000/MPx.
Group code Project Administrators Group Name Building Technologies Fire Safety & Security Products Windows control MM8000 Exit Operator logout Operator change password Operator switchover PAK Manager Address Book System Supervisor Browser Composer (defined in User Manager) History browser (System queries only) History browser (Personal queries) History browser (Backup/restore) History browser (Administrator) SiPass Scheduler (view) Scheduler (modify) Plant browser Closure in event treatment Re
Group code Project Administrators Group name Operator name 1 Backup Operators 2 1 Advanced Operator Group 1 2 1 2 3 4 Advanced Operator Group 2 1 2 3 4 Standard Operator Group 1 1 2 3 Standard Operator Group 2 1 2 3 Default Operator Group 1 1 2 Default Operator Group 2 1 2 User Type #1 1 2 User Type #2 1 2 User Type #3 1 2 User Type #4 1 2 User Type #5 1 2 Building Technologies Fire Safety & Security Products 152 MM8000 Installation, Configuration, and Commissioning Manual 06.
Individual Users Login ID Password (Case sensitive!) Operator name Group Other info* Composer User Manager Profile: Level: Guest/Std/Adm Std/Adv Building Technologies Fire Safety & Security Products 153 MM8000 Installation, Configuration, and Commissioning Manual 06.
Global Event Settings Max # of events in event list Enable Auto acknowledge Enable Auto close Treat subsequent events Geographical tree Node types: B=Building F=Floor S=Section R=Room Node name Other … (Generic node) Node Type 154 Building Technologies Fire Safety & Security Products Security profile MM8000 Installation, Configuration, and Commissioning Manual 06.
Operating Procedures Types: Attributes: App=Application Txt=Text Htm=HTML page Map Attributes: Rep=Report Prn=Alarm printout Dlr=Dialler Eml=e-mail SMS TV=CCTV Pg=Pager M=Mandatory O=Optional OC=On creation (alarm printout only) OT=On treatment (alarm printout only) Procedure name Sequential? (Y/N) Category Object type Object sub-type Discipline: Discipline sub-type: Step Type Title Description or Contact Attributes Path location of HTML or Application Application Parameters 1 2 3 4 5 6 7 8 9 10
Reactions Ignore Maintenance Points? Point State Or/And Point State Name: Trigger Reaction Name: Trigger Reaction Name: Trigger Reaction Name: Trigger Reaction Name: Trigger Reaction Name: Trigger Reaction Name: Trigger Reaction 156 Building Technologies Fire Safety & Security Products MM8000 Installation, Configuration, and Commissioning Manual 06.
Sequences Create Log File? Ignore Maintenance Points? Global variables Name Initial value Sequence: Parameters Instruction Building Technologies Fire Safety & Security Products Description Point State Variable Time 157 MM8000 Installation, Configuration, and Commissioning Manual 06.
Scheduler Organisation Modes Name Description Day types Name Colour Intervals Colour Start End Organ. Mode Start End Organ. Mode Start End Organ. Mode Start End Organ. Mode Typical week: Week begins: …............ (Monday or Sunday) Day Day type Sunday Monday Tuesday Wednesday Thursday Friday Saturday Time programs Name 158 Building Technologies Fire Safety & Security Products Starts Every day On day: Every week on: Every day type: At: When Organ. Mode starts: When Organ.
E-mail and SMS over e-mail dispatcher Account setting POP3 SMTP Account name Password e-mail address SMS over GSM dispatcher GSM account setting COM port Bits per second Data bits Parity Flow control (Hardware, Xon / Xoff, None) SIM PIN code SMS over e-mail dispatcher SMS setting Service provider domain Mail subject (Empty, Fixed string, SMS body) Mail body (Empty, SMS body) Max SMS body length (default 160) ESPA Pager ESPA setting COM port Bits per second Data bits Parity Stop bits Max message length Sp
Individual point customisation Customisable items: Point text Change how the name of the point appears to the end user Maps Change which Maps are associated with the point during event treatment and/or the plant browser Icon Select a new point icon from the standard list or add a new one Journal/history log Change which virtual properties are logged in the history browser and by the journaling printer Events generated Severity Determine whether a point will generate an event when it goes into any g
Appendix F - How to use CSV Files The CSV (Comma Separated Values) files are best viewed within applications that allow manipulating data that is in columnar format. Common examples of such applications are those that are used to create spreadsheets and databases. If you don't have access to either a spreadsheet or a database application, you can also retrieve the data table file into a word-processing application.
Appendix G - How to modify MK8000 projects for MM8000 In Composer, MM8000 and MK8000 projects are quite different (MM8000 requires many more system nodes and extensions than MK8000). Given an existing MK8000 project, it is possible to make it compatible with MM8000 by following the procedure illustrated here below. Instead, it is not possible to modify an MM8000 Composer project for adapting it to the MK8000 OPC Server.
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. A6V10062413_a_en Edition 06.