MM8000 MP4.
Data and design subject to change without notice. / Supply subject to availability. © 2009 Copyright by Siemens Switzerland Ltd We reserve all rights in this document and in the subject thereof.
Table of contents About this document...............................................................................................1 1 Safety regulations ..............................................................................................3 1.1 Country-specific standards ........................................................................3 1.2 Assembly, installation, commissioning and testing work ...........................3 1.3 Modifications to the system design and the products ............
.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.4.6 Runtime user management ......................................................71 Downloading the configuration as a 1st check.........................................72 Customising general event settings .........................................................73 4.6.1 Overview ...................................................................................73 4.6.2 Event settings .......................................................
Appendix A - System supervision and event simulation ................................148 A1 - System Monitor.........................................................................................148 A2 - Simulating field events..............................................................................150 A3 - Simulating from a networked computer ....................................................151 A4 - Using the System Supervisor Browser .....................................................
About this document Purpose of this document This manual is a guide to the installation, configuration, and commissioning procedures for the MM8000 Management Station. Scope This document applies to the MM8000 Management Station MP4.20.
Liability disclaimer for damage or injuries Before products are delivered, they are tested to ensure they function correctly when used properly. Siemens disclaims all liability for damage or injuries caused by the incorrect application of the instructions, or the disregard of danger advisories. This disclaimer applies in particular to personal injuries or damage caused by: – Improper and/or incorrect use. – Disregard of safety instructions in the documentation or on the product.
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 2.1 Project Workflows 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 (refer to the list of Reference Documents in DMS8000 MP4.20 Documentation Resource Information Guide, document no. A6V10089056). Note: The steps relevant to this document are in black, while the other steps are shown in grey.
2.2 What has been changed in MP4.20 configuration tools Here is the list of modifications included in MP4.20 for new functions and software improvements. 2.2.1 Section, Page Modifications 3.1.1, p. 6 New screen resolution supported: 2560x1600. 3.1.2, p. 7 Support for Windows Server 2008 SP1 (SP2 for Windows Server 2003). p. 27 New ULC option in the installation procedure. 3.4.10.2, p. 38 New functions in the Engineering Tools. 3.4.10.4, p. 40 Registry commands are now fully documented. 4.2.
3 Installing MM8000 MM8000 can be installed for the following architectures: z Single Station (Stand-Alone station) z Distributed System (Stand-Alone server plus Client and/or FEP stations) 3.1 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 DMS8000 CD, all applications are distributed free of charge and can be installed with no need for purchasing a license.
FEP station z x86 32-bit CPU, 900 MHz (2.4 GHz or faster if used for video application) z 1 Gbytes RAM z 15 GB free disk space, NTFS (no FAT/FAT32) partition required z Serial line adapter (if serial connectivity is used) z 100 (or 1000) BaseT Network Card 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 DMS8000 CD.
z SiPass Integrated software for integrated access control (required before install- ing MM8000, see notes at p 9) z OPC server(s), local and/or networked, as required by the OPC connectivity Client stations z Windows XP Professional SP2 or SP3 Æ See notes about XP SP2,SP3/Vista Firewall at p.9. Windows Vista SP1 Business, Ultimate, or Enterprise edition Æ See notes about Vista at p.
Internet Information Services (IIS) is available but not installed in Windows. You can install IIS by selecting Control Panel Æ Add/Remove Programs Æ Add/Remove Windows components (follow the on-screen instructions to install, remove, or add components to IIS). For more information on IIS, see Æ http://www.microsoft.com/WindowsServer2003/iis/default.mspx or http://www.iis.net/ Note: ISS should be installed before MM8000.
Windows Vista includes several new features. Among them, two have a significant impact on the MM8000 operations. Namely: – UAC security – Virtualization of program files and registry entries 1) The UAC (User Account Control) is a security-related feature that is enabled by default in Window Vista. The UAC main goal is to reduce the risk of undetected attacks to the operating system by prompting users to ensure they are authorized and want to perform a potentially harmful action.
3.2 MM8000 Installation types 3.2.1 Selecting the MM8000 configuration The DMS8000 CD includes various products (see 3.4.1 at p.16); referring to MM8000, the installation options include: # Installation type Meaning 1 Stand-Alone / Server station (full-featured) Install all MM8000 software layers as well as Composer and the tools for configuring MM8000.
Fig.1 Redundant server architecture When using the redundant option, the MM8000 setup procedure requires a few more parameter settings, as described at pag.29. The MM8000 License Server does not run on the virtual machine. Instead, a new MM8000 setup option (License Station) has been provided, which is meant for the physical machines and only includes the license-related components that need to check the physical ports. Fig.
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: z Local Windows workstation 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 MM8000 users defined in Composer will be local Windows users.
# Windows network# MM8000 Architecture Windows Software Security option User management 1 Any Stand-Alone - Windows professional Standard security User management handled by MM8000 automatically. 2 Any Stand-Alone - Windows professional Advanced security Configuration and maintenance of MM8000 user accounts is required on the station.
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, video application software (e.g. for SISTORE DVR) should preferably be already installed. If required, OPC servers should preferably be already installed.
3.4 Installation procedure 3.4.1 Welcome screen The DMS8000 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. As shown in Fig.3 below, the welcome page presents a menu including the following commands: – Install MM8000 – Install MK8000 OPC server Î See MK8000 ICC manual (document no.
Fig.4 MM8000 Station Selection Page The Stand-Alone / Server type (Fig.5) presents the most complete list of required applications or pre-requisites: MSDE 2000 (or SQL Express 2005+compatibility pack), SQLXML 3.0, .NET framework V1.1 and V2.0. Live Video and Alarm printouts require additional software (see 3.1.2 at p.7). Note the colour of the installation options: z Grey colour: software installed z Green colour: software not installed Fig.
3.4.2 MM8000 stand-alone station: installing the MS software 3.4.2.1 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 started from the setup page (Fig.5), you only have to agree on the terms of the license agreement (Fig.
Fig.9 Accepting the .NET Framework V2.0 License Agreement Fig.10 Successful termination of .NET framework V2.0 setup Although not strictly required for MM8000 operations, the recommendation concerning the .NET framework update (see Fig.10) should be followed to ensure software stability. Please refer to Microsoft support site at Æ http://www.microsoft.com/downloads and search for “.NET Framework” in the “Windows Security and Updates” section. 3.4.2.
Due to important security concerns, it is strongly recommended to customise the SQL default user information (see p.39). 3.4.2.4 Installing SQL Express 2005 + Backward Compatibility Pckg If you do not want to install MSDE 2000 (e.g. for Windows Vista), you may install the SQL Express 2005. Note that in this case MM8000 also requires the “SQL 2005 Backward Compatibility” package. Microsoft .NET V2.0 framework library is a pre-requisite for SQL Express 2005 Installing SQL Express 2005 1.
In the resulting window (Fig.14), you can find any errors or warnings found (see the Status column). Use the Filter command to limit what items are visible in the list. Follow the Message link and read any related information that may indicate if and why your system cannot fully support SQL software. Fig.14 System Configuration Check before installing SQL Express 2005 6. If no critical errors are present, you are allowed to press Enter to continue. 7.
9. The next window (Fig.17) allows setting SQL authentication mode. Confirm the default option (Windows Authentication Mode) and click Next. Fig.17 Selecting the SQL Express 2005 authentication mode. 10.The configuration window that follows (Fig.18) configures SQL user options. In general, we recommend enabling both options (Enable User Instances and Add user to the Server Administration role) unless specific security issues apply (contact IT Manager). Fig.18 Configuring the SQL Express 2005 users 11.
Fig.20 Ready to install SQL Express 2005 12.At this point, setup installs the software. This may take a few minutes. A setup progress window (Fig.21) displays on the screen, and a summary log is finally available in the next window (Fig.22). Click Summary Log to open and possibly save the log file. The Summary Log window also shows a link to the Surface Area Configuration tool (also available in the SQL Express folder of Windows Start menu). The use of this tool is not required for MM8000 operations.
13.Click Finish to close the setup procedure. You now need to add the Backward Compatibility Package. Installing Backward Compatibility Package 1. From the setup page (Fig.5), launch the installation of SQL Express 2005 Backward Compatibility Package. 2. In the Welcome window, click Next (Fig.23) and Next again to confirm you accept the License Agreement (Fig.24). Fig.23 Installing SQL Express 2005 Backward Compatibility Package Fig.24 License Agreement for Backward Compatibility Package 3.
Fig.26 Selecting the Backward Compatibility Package features to install Fig.27 Ready to install the Backward Compatibility Package 5. At this point, the setup installs the software. When completed, click Finish to close the last setup window (Fig.28). Fig.28 Completing the Backward Compatibility Package setup 3.4.2.5 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.
Fig.29 Starting the SQL XML Installation Wizard You have to accept the terms in the license agreement, then enter your name and company, and finally confirm the installation folder. After that, in the Setup Type step, press the Install Now button (Fig.30) and wait for the setup procedure to complete. Fig.30 26 Building Technologies Fire Safety & Security Products Selecting the SQL XML Setup Type MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
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.13. Updating previous MM8000 versions Important: Check update instructions on the latest Release Notes! 2.
get the control of the user account definition in the following ways (see Fig.32): – The internal Windows account for the MM8000 application can be customised. The default setting is “DMS8000_Proc” (see also 3.5 at p.43). Here you can define any other username and password you want to use. – Composer security can be enabled (it is disabled by default) to remove the access restrictions.
Tools (see 3.4.10.2 p.38). Æ MM8000 configuration functions for ULC compliance are described in Appendix H at p.174. 4d. External SQL server settings If no SQL server is available on the local PC and a Stand-Alone or Server type has been selected, the setup procedure cannot proceed and proposes three possible solutions (see Fig.33): – Indicating a Server available in the network: Click Next. – Stopping the setup and install the Microsoft SQL server Desktop Engine (MSDE). Click Cancel.
Fig.35 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 3.2.1.1 at pag.11. 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.37 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.38). Fig.38 – Select: System Tools Æ Event Viewer Æ Application in the Computer Management tree (Fig.39). Fig.39 – My Computer menu Computer Management tree Select the Properties icon . The Application Properties window appears (Fig.
Fig.40 – 3.4.4 Application Properties window In the General tab, set Max.log size = 512 KB and Overwrite events as needed. Then, click OK to 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 (document no.A6V10062425). The software required for handling the license key is automatically installed with the MM8000 setup.
At this point, you can notice the new MM8000 System Monitor icon in the Windows taskbar at the bottom right of the screen. Also, while starting up, status messages are displayed reporting the server task conditions (Fig.41). Fig.41 3.4.5 MM8000 System Monitor icon Changing MM8000 language (optional) During the MM8000 setup procedure, the language can be selected so that the installed texts will be localised accordingly.
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.152.
3.4.8.1 MM8000 including MK8000 OPC Server The MK8000 OPC server functions can be activated in the node: Supervisor … Æ MM8000 System Æ Logical Configuration Æ User Data In the Node tab (Fig.42), select the project type: – MM8000 only – MM8000 with MK8000 OPC Server Referring to the MK8000 specific parameter setting (Multi-State Mode: Threshold or Bitmask), please see the MK8000 ICC Manual. Note: The MK8000 license is required for running the OPC Server. Fig.
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 setup) to an MK8000-only system: use the Product Type tab of the Engineering Tools described in 3.4.10.2 at p.39. The same tool 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.
Tool applications z Composer Plug-in Installer – Shows which plug-ins are currently loaded and available in Composer, and allows for removing and installing plug-ins. Æ Refer to the Composer Technical Manual, document no.A6V10062401. z 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. Î Refer to the Composer Technical Manual, document no.A6V10062401.
Line monitor The Line Monitor utility can connect to the MM8000 (MK8000) communication drivers and trace the messages on the screen or disk. See the on-line manual for more information (select Help Æ On-line Manual in the Line Monitor program Menu). NW8202 This program allows setting the IP address in the NK822x units. Refer to the NK8000 Installation, Configuration, and Commissioning Manual (document no.A6V10062437).
z Product Type – Modifying the internal setting related to the DMS8000 product type: MM8000 or MK8000. Running this procedure results in a global change in the activated server software and in the default Composer project setting. Note that this command does not affect the Composer project (see p.173). The command toggles from MM8000 to MK8000 and then vice versa. z Station Names – Updating the DMS8000 environment after any change in the Windows network names of the computers.
Start / Stop servers – Start_system.bat – Start servers – START_Server.exe - Start Server application – STOP_Server.exe - Stop Server application After MM8000 software installation, Start and Stop commands are available on the desktop, where two shortcuts are created, named “Start Server” and “Stop Server”, respectively. 3.4.10.4 Registry scripts The directory: \Utilities\Reg contains various registry-setting scripts. Only a few of them can be useful to you.
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. In such a case, you can change any of the characters in the special sets so as no conflict with customer texts occurs. Just modify the “LOCATION_FORMA.reg” file, launch it, and restart DMS8000 server.
Setting debug mode can result in a large amount of disk space being used for technical logs. 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: z Empty Project.bak This provides an empty structure that can be used to start a project for special applications (e.g. Visual Builder).
3.4.11.3 NK8000 firmware NK822x (NK8222, NK8223, NK8225) The latest release of the NK822x firmware is provided in the folder: \NK822x - Firmware The firmware is contained in compressed (ZIP) files. The list includes: – NK8223_x.yy_Build_zz.zip (for NK8222 and NK8223 units) – NK8225_x.yy_Build_zz.zip (for NK8225 units) NK823x (NK8232, NK8235) The latest release of the NK822x firmware is provided in the folder: \NK823x - Firmware The firmware is contained in compresse
Fig.46 Add-on Manager Window Fig.47 Selecting the MM8000 Extension Product Name file 3. If your MM8000 installation includes a customized MM8000 internal account (see Fig.32 at p.28), then deselect the checkbox Use default MM8000 User account (described in 3.5 at p.43) and specify the customized username and password. 4. Click Install (or Update if a previous version is detected).
4 Configuring MM8000 4.1 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. 1. Set up the Composer project (Æ DMS8000 Network, Fire, and Intrusion Connectivity configuration guide) 1.1 Create a new project 1.2 Define the general structure of the project tree, taking into account the goal of presenting a structure that is clear to the final users 2. Define the MM8000 system architecture 2.1 Set up stations 2.2 Set station parameters p.47 p.
4.2 Defining MM8000 system architecture 4.2.1 Overview 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.42), 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.49 Select Station type 3. 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.50. Server-only stations necessarily require at least one FEP. Fig.50 FEP stations 4. 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.
Fig.51 Connect FEP driver to the channel collection on the main station 6. Add Client stations, if necessary. Note: For large systems, multiple stations can also be organised in folders, see Fig.52. Also, note that Client stations do not need to be linked to the StandAlone station. Fig.52 Adding a client stations 8. Add License stations, only necessary for redundant server solutions. Fig.
4.2.3 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. Enter the following in the Node tab: – Description – Station Name, which is the PC name in the network Note: If you do not know this name, right-click the My Computer icon on the desktop.
Fig.56 Event treatment settings Event Selection Modes z 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”. – User driven: The system suggests to the user what event should be treated first by displaying it at the top of the Event list (most important event). However, the user is allowed to treat all other events in his/her preferred order.
Maintenance settings This option applies only when the MM8000 station is in maintenance mode. That is, when it is set to show the events related to the part of the system in maintenance state only. If the checkbox is set, the MM8000 operator receives a notification message when a new event occurs but it is not listed because the generating point is not set in maintenance state. Event Selection Type This option applies only to Automatic and By notification modes.
Fig.57 Primary Client tab Configuring the Primary client mode To enable/disable the primary Client mode, select/de-select the Primary Client checkbox in the Primary Client tab. In the same tab, you can modify the client priority list: Select a station and change its position using the Up/Down arrows to define its priority in becoming the primary client. 4.3 Configuring printers 4.3.
Fig.58 A MM8000 Printer toolbar Select this icon to add a new printer 2. Insert the printer selecting one of the following options: – System Alarm Printout, if alarm printout is used during event treatment. – System Reporting, if a printer for history reports is required. – System Journaling, if a logging printer is used for recording system activity. The support of Alarm Printout printers requires some software components included in Internet Explorer 6.0 or later. A B C Fig.
Fig.60 Browse for the printer (or enter data directly) 4. Locate network printers. Note: Printers can be both local and networked. When browsing to locate a network printer (Fig.61), double-click the network node to open the subtree, and continue the navigation until you reach the printer. Fig.61 Browsing in the network for selecting the printer 5. Select the printer and click OK. The printer information will be automatically set in the Composer form (Fig.62). Fig.
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. Objects are described by a full location path that includes the entire tree. 132x60 Line Printer Reduced Printout template for 132-column line printer.
Fig.64 Filtering events in journaling 8. Alarm Printout only: setting printout options: The alarm printer must be linked to the Alarm Printout steps of the Operating Procedures (see 4.9 at p.85) that require this function (Fig.65). For each of these links, a new node is added and a specific set of options can be defined as shown in Fig.66. Fig.
Fig.66 Setting alarm printout options The option list includes: – Paper Size: A3 or A4. – Orientation: Portrait, Landscape, or automatically oriented depending on the printout. – 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. 58 Building Technologies Fire Safety & Security Products MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
Alarm printout templates Example (A4, event description, operating procedure, map, and 2 pages) Concatenate all information keeping the original size. Fit all information in one sheet. Fit maps and pages on the same sheet, starting from the second. Building Technologies Fire Safety & Security Products 59 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
Alarm printout templates Example (A4, event description, operating procedure, map, and 2 pages) Always print maps and pages on separate sheets. 60 Building Technologies Fire Safety & Security Products MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
4.4 Setting up the 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.
Referring to Fig.67, note the following configuration settings: – User Allen Brimley is a member of the Advanced Operator Group 1 (Fig.67-A). – In the Fire Safety Profile, the Advanced Operator Group 1 (Fig.67-B) is assigned permissions or privileges – in this case, it has Full Control privileges (Fig.67-C). – What the group users can see and control is determined, e.g. in the Fire Protection folder, by the associated Profile Id (Fig.67-D) and the related permissions (Fig.67-E).
4.4.2 Setting the domain name 1. Select the Domain node: Security Æ Users Æ Domain and then select the Node tab. 2. Specify the Domain name (Fig.68). Note: In a Single Station configuration, the domain name is the PC name. In a Distributed System configuration, whenever a network domain security applies, it must be the network domain name. Fig.68 4.4.3 Setting the security domain. Assigning user group permissions By default, there are eight user groups organised in incremental capability levels.
modify the programs (Full Control vs.
Fig.69 Client Settings: modifying default system permissions for a user group 4. Select the Event Settings tab to change event treatment permissions (Fig.70). Namely: Protocol Enable the display of the event history log Allow Event Closure Enable the command to close the treated events Allow Closing Command in Progress Dialog Enable the command to close the dialog box showing the treatment command in progress (e.g.
5. Select the System Settings tab to change event treatment permissions (Fig.71). Namely: Station operation mode Define open or closed station mode for the users of the group. In closed mode, MM8000 takes over the Windows interface and only the authorised applications can run. Auto-logoff time Set the maximum inactivity time (in minutes) after which the users of the group are automatically logged out. Zero means no auto-logoff.
Fig.71 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.73). 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.
Fig.72 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.73. 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). Fig.
To assign security profiles, perform the following steps: 1. Select the Security-Users-Profiles folder. Fig.74 Click the Profiles folder to add a profile 2. Click the Profile ID icon to add a Security Profile. (Such as All, Fire, Intrusion, Restricted, and so on.) Tip: Set up the most commonly used profile as the default profile. 3. Drag and drop a user group to the appropriate profile. 4. Select the user group link that you created when you dragged / dropped. 5.
Fig.76 Changing profile to a subtree of nodes z A security profiles is defined by default and associated to all nodes. z Every node in composer has a profile. If you do not specifically set it, it assumes the default profile. z Profiles are inherited from the parent node (though you can apply different pro- files to individual children nodes), so you can change the profile for an entire subtree by changing only the profile for the top node. z If Standard Security is enabled during software setup (Æ 3.2.
4.4.6 Runtime user management MM8000 users can also be added at runtime using the User Management program in the Administrative Tools menu. The User Management tool is described in the MM8000 Operation Manual, document no.A6V10062409. In Composer, you can easily view and import the runtime user configuration. Proceed as follows: 1. Select the User: Security Æ Users and then select the Node tab. 2.
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.80), you can configure the event generation and treatment styles. Specifically: z 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. z Enable Auto-Acknowledge. Set this flag to globally enable the automatic ac- knowledgment.
Fig.80 Building Technologies Fire Safety & Security Products Event generation and treatment styles 75 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
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.81), 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.81) 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.82).
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. Fig.84 Icon size formats Note: You can prepare the file to be imported using any graphic tool capable of generating ICO format files.
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.
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.85. Important If the geographical structure is expected to grow to over thousand objects (e.g. > 5000), performances in the Composer configuration may decrease drastically.
Fig.87 A B C D E Geographical objects 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 4. Drag points (subtrees) from the logical tree of the control units to the room in which they are located.(see Fig.88).
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.90 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.131). Automatic association can be disabled in Supervisor System Settings Æ MM8000 System Æ Logical Configuration Æ Point Page Extension. Fig.
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.93). Then, proceed with the general definitions as instructed in the following steps. Fig.93 Add a new Operating Procedure 2. In the node tab, confirm or change the default treatment mode (Fig.95). The option list includes two modes: – Guided treatment: Operators are guided through a number of procedure steps.
Fig.94 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.2131). Fig.95 Operating Procedure definition 5. Use as default: set this procedure as the default Operating Procedure.
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.96): A. Application (Guided mode only): Define a step supported by an external Windows application, whose pathname and parameter(s) should be specified (that is, a file pathname such as “C\SecurityProcedure.doc”). B.
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.94.
Operating Procedure step: summary table # Step types Parameter(s) Example / notes A Application step - Application pathname - Application parameters (optional) - E.g.: Notepad.exe - E.g.: Textfile.txt B Generic text None - C HTML page - URL - E.g.: company.intranet\fire-drill.htm D Map None E Report None - See 4.9.2.
Fig.97 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. Building Technologies Fire Safety & Security Products 91 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
Pager messages Fig.98 Configuring paging message Settings (as for other type of steps): Repeatable: specify here whether the step can be executed more than once. Attributes (as for any other type of step): Step Title, Description and Execution Attribute (MANDATORY, OPTIONAL, or AUTOMATIC). Message Recipients: Timeout for reply from Receiver: enter the timeout (in min.) before registering the step failure Note that the Reply from Receiver must be enabled as shown in 4.9.4.4 at p.102.
Pager messages: Advanced Settings Check the Advanced Settings mode in the Message Content section (see Fig.98 above) to enable the detailed configuration of the paging message format. The advanced page allows entering one field at the time and formatting the message contents with maximum flexibility. Use the Add line and Delete line buttons to insert and remove a field, respectively.
The Fig.100 below shows an example of advanced formatting, The Composer window in the centre illustrates the field settings referred to the event information (on the top) and to the resulting paging message (at the bottom). The paged message includes: – A fixed text (“Fire”) – Date and Time – A fixed EOL – Characters 4-10 of the 6th section of logical text, “O01-03” in the figure – A fixed EOL – Characters 1-4 of the 5th section of logical text, “1.
Fig.101 Operating Procedure step titles and descriptions 4.9.2.3 Event Dispatching Individual Text In the Event Dispatching Individual Text tab, you can add or remove texts that can be used in the steps handling dispatching functions (e.g. SMS step). See the following Fig.102. Fig.102 Operating Procedure dispatching texts 4.9.2.
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.95, p.87). However, you can disable the automatic mechanism for some or all procedures (again, Fig.95, p.87), or modify the automatic assignment for some specific points. You can customise individual points on the “Event and OP extensor” tab. When needed, associate an Operating Procedure to the selected properties (see 4.13.3 at p. 132). 4.9.
Contacts and Groups Contacts are representing single persons and the corresponding records contain personal information and data required for the event notification. A Group can collect a number of contacts (or other groups), thus allowing for an easy multiple selection of recipients of multicast notifications. Main commands can close (and then re-open) the In the Info Page Toolbar, the command icon allows to open the Group Configuration Tree.
4. Click the Save changes icon to confirm the modifications. In case of mistakes, use the Cancel icon changes. to quit without saving the Assign a contact to a group 1. Select the Group to which a contact has to be assigned. to open the Group Manager (Fig.106) 2. Click the command icon 3. Select the contact to assign in the list of the left. 4. Click the command icon to assign the contact to the group. The contact name appears in the list on the right, as new member of the group. Fig.
tion of new custom attributes to allocate new fields (see the Notes field in Fig.107). Fig.107 Import mapping Building Technologies Fire Safety & Security Products 99 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
4.9.4 Configuring the Dispatching Services 4.9.4.1 Overview In the Operating Procedures (described in 4.9 at p.85), 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.4.
4.9.4.3 Configuring the SMS service The SMS service must de defined in: Supervision System settings → MM8000 system → Logical Configuration → User Data Æ Dispatching Services Æ SMS Proceed as follows: 1. Select the SMS node. 2. Click the SMS tab. The form illustrated by Fig.109 appears. Fig.109 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.
4.9.4.4 Configuring the Paging service In order to use the Pager tool in the Operating Procedure steps, the tool must first be installed as one of the Dispatching Services. Proceed as follows: 1. Select the Dispatching Services node in: Supervisor System Settings → MM8000 System Æ Logical configuration Æ User Data 2. Click the ESPA Pager icon to add the tool (see Fig.110). Fig.
Fig.111 Configuring the ESPA parameters Building Technologies Fire Safety & Security Products 103 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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.112 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.
– Leave the option Reaction enabled checked. – Check Transition to reachable if the Reaction includes triggers related to normal states set just after the status request. Fig.114 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. As illustrated in the following Fig.
Fig.116 Adding a Manual Trigger Fig.117 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.
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.119): – Note: Text field for your free comments – Show: Selection checkboxes that can change the way trigger and effect names are shown. Namely: Customer text, Technical text, or both. – Reaction program: This is a large field where the Reaction logic is specified in an IF/THEN programming scheme.
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 and no brackets are used, AND, OR and XOR execute in this order.
Note: More than one point can be selected as Field condition in order to check multiple states (AND or OR logic can be selected) in a single instruction. Use the Shift or Ctrl key to select more Field point items, then select a (common) Property and condition State for all of them, and finally define the AND/OR logic. Access Control Transaction as Field condition: – If an AC door is linked to a reaction, then you can check the transaction for a configurable Transaction Time.
3.D Enter the Effect program, you can select the following statements/conditions clicking on the left menu: – Comment: To enter a text line. – Send command: To specify a control action. – Wait: To insert a programmable delay in the action list (see example below). – Wait and re-check: To insert a programmable delay and then re-evaluate the trigger status before proceeding with the action list, e.g. to verify that the trigger status is stable. Note: This instruction also includes an IF/THEN/ELSE clause.
In the Wait and Wait and re-check commands. The delays are programmable in hours, minutes, seconds, and tenths of sec. Note: The max. delay can be: 23h, 59’,59.9”. In the Switch Camera to Monitor command, camera and monitor are selected in drop-down lists that include the devices linked to the reaction node (step 1 above). 3.E Check the resulting Reaction program as shown on the screen (see the example in Fig.120 below).
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. Building Technologies Fire Safety & Security Products 113 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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.122. Fig.122 Add a Sequence or a folder of Sequences A B Add a Sequence Add a folder of Sequences 3. Define the Sequence settings in the Node tab (see Fig.123). – Name the Sequence in the Description field. – Leave the field Sequence enabled checked. Fig.
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 required points to the Sequence node (Fig.124). The point displays as a link in the Sequence. Fig.124 Linking triggers and effects 2.
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.126). 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.126 Invalid Sequence 3. Edit the Sequence program. Proceed as follows: 3.A By default, a new Sequence only includes a comment field and the [STOP].
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). – set organisation mode: modify the current MM8000 scheduler organisation mode (refer to the MM8000 Scheduler functions).
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.117). – 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.108). – 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. Active: Set to active state.
Fig.127 Valid Sequence i 122 Building Technologies Fire Safety & Security Products 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. MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
4.11.4.1 Example of VBscript in MM8000 sequence ' ' ' ' ' ' ' ' ' ' ' ' ' ' ' ' Example of VBS code using the MM8000_GetValue function This program shows and saves on disk the value of an MM8000 object's property MM8000_GetValue (.
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 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. – Click the Start Time cell and enter the starting time (hh:mm). – Click the small arrow in the Name cell and select the Organisation Mode associated to the time interval. – Repeat the three steps above for all the required intervals.
Fig.129 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.130 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.130 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. If required, add a new subfolder (click 3. Click the Time Program icon ) or select an existing subfolder. to add a new program (see Fig.131). Fig.131 Adding Time Programs 4. Select the Time Program node. 5.
In the Comment section, you can add a text that can help describing the use of the program. 7. 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. 8. Enter the Time setting. Here you can select to launch the program: – At a given time of the day. – At the beginning or end of a specified Organisation Mode.
Fig.133 Reminder configuration 10.Link the sequences (discussed in 4.11 at p.114) to be executed (Fig.134). Click the Sequence node and drag and drop it on the Time Program node (Fig.134). A new node displays representing the link to the Sequence. Fig.134 Linking a Sequence to a Time Program 130 Building Technologies Fire Safety & Security Products MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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: z Modify the point description in the MM8000 plant browser. z Change which icon is associated with a point. z Exclude a node from the project (off-scan). z Set the command feedback timeout. z Change which Maps and pages are associated with a point.
received. The default value of 30 sec may be modified to better suit specific network configurations. Fig.135 Point Extensor tab A B C D Point description text: It may be modified here when not imported Icon number Off scan checkbox: If checked, point and all its children are ignored Command timeout (top node of each subsystem unit): used to declare the command failure if no feedback is received from the subsystem. 4.13.3 Event and OP Extensor tab In the Event and OP extensor tab (see Fig.
– Enable Auto-Ack (C4): Check this option to enable automatic acknowledge when the event is opened for treatment. This will only work when global auto-ack is also enabled (see 4.6 at p.73). – Intervention text (C5):Add a short text that will be displayed in the event list in the fast treatment mode. Multiple lines of text can be handled.
4.13.4 Event Treatment and Plant Browser tabs In the Event treatment Pages and Plant browser Pages tabs (Fig.137) you can see the graphic Map associations and manually add one or more associated page. 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.138). Fig.137 Event Treatment Pages tab Fig.
4.13.5 Camera Extensor tab In the Camera Extensor tab (Fig.139) 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. The first four cameras, whose names show in red colour, are available in the MM8000 Quad views.
Fig.140 Setting the camera Preset Position 136 Building Technologies Fire Safety & Security Products MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
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 DMS8000 Network, Fire and Intrusion Connectivity Guide (document no.A6V10062425). After you have backed up the project you are ready to transfer the configuration to the MM8000 Server. 4.14.
Fig.142 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.143 Domain name Fig.144 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 DMS8000 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.29), then the server tasks automatically start after any reboot.
4.14.4 Downloading configuration to MM8000 To download the configuration, do the following: 1. Launch the System Supervisor Browser. 2. 3. 4. 5. 6. i Start Æ Programs Æ DMS8000 Æ System Supervisor Browser Wait for the Server and any FEP station icons to turn green. Select a station icon in the left pane. Verify that all the items listed in the right pane turn green. Repeat steps 3 and 4 for each station. 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 When you create users in Composer that are not already present in the Windows user list, new accounts are created automatically during the configuration download, provided that this standard behaviour was not disabled during software setup (see the Advanced Security options at p.13 and p. 27). With standard security settings, Composer creates new Windows users during download and sets for them the default password “MM8000_pwd”.
4.16 Activating the MM8000 closed mode In the Standard Security setting (see 3.2.2 at p.13), 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 Server 2003 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.
5 Testing the configuration Once the configuration has been downloaded to the MM8000, you need verify that the MM8000: z Is running on the stations; z Has been configured correctly; z 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 Creating configuration reports MM8000 tools can provide a number of file reports (CSV format). Depending on the specific project, the available reports may be: z Points associated with Operating Procedures (or not associated). z Points involved in Reactions (or not involved). z Points involved in Sequences (or not involved). z Points linked to the geographical tree structure (or not linked). z Points deposited on Maps (or not deposited). z Points excluded (off-scan).
Fig.146 Export command on the “Style” node Examples of reports The export output is a text file, CSV format. See p.172 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.148 System Monitor right-click menu: Server is running, therefore the Stop command is available Fig.149 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 at p.150). While running in this mode, MM8000 does not communicate with the filed, but only with the simulator.
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: z 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.13). Setup procedure: z 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.148 above) or through the Windows Programs menu (Start Æ Programs Æ DMS8000 Æ System Supervisor Browser). The browser shows the running MM8000 stations (Fig.152- A) and the associated tasks (Fig.152- B). If the list on the left hand pane does not include any station, it means that the MM8000 software is not running. Fig.
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 In operation 8/29/2005 4:32:59 PM 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 155 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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. 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.154 Setting dual history Server D4 - Dual systems: Twins Manager The Twins Manager is a special add-on tool that can be optionally installed in Composer to simplify the configuration of a double MM8000. This type of configuration comprises two complete and identical systems connected to the field using network solutions that allow for multiple routing. Twin servers vs.
z Values of Network Addresses and Names: given the A settings, a numeric or alphanumeric offset is initially applied to the B settings. For example, swapping the first time from A to B results in the IP address of all the PC stations being offset by 32 (e.g. “10.10.1.2” on A becomes “10.10.1.34” on B). In the B configuration, you can modify the default offset and manually set the actual address (and names) of your network.
Fig.156 Locating the ST Plug-ins folder The list of available plug-ins displays in the Available Packages area on the right 4. In the list of plug-ins, locate and select the Twins Manager tool. 5. Click Install. Using the Twins Manager Once installed, the Twins Manager can be added to any Composer project tree using the corresponding icon (Fig.157). Fig.
The Twins Manager node should always appear in the last position of the project tree (see Fig.158 above). If the Twins Manager node is located elsewhere, the download procedure may fail to properly reproduce the project structure in the runtime environment. In that case, in the Plant Browser navigation, you may find a node structure that does not exactly match the one defined in Composer.
Appendix E - Customisation checklist Customer Customer Reference - Order # Internal Reference -Job # Date Product/Version (MM8000/MPx.x) Administrator log-in Administrator Logon ID: Password: Internal MM8000 account Password: Stations Types: # Type Stand-Alone / Server station, License station (max 2) Client or FEP station Station Name IP Address (single station system will use the localhost address 127.0.0.
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 DMS8000 Contacts 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 (Read-only) Scheduler (Full Control) Plant browser Closure in even
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 163 MM8000 Installation, Function & Configuration, Commissioning, Safet
Individual Users Login ID Password (Case sensitive!) Operator name Group Other info* Composer User Manager Profile: Level: Guest/Std/Adm Std/Adv 164 Building Technologies Fire Safety & Security Products MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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 Building Technologies Fire Safety & Security Products Security profile 165 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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 If an
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 Building Technologies Fire Safety & Security Products 167 MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 06.
Sequences Create Log File? Ignore Maintenance Points? Global variables Name Initial value Sequence: Parameters Instruction 168 Building Technologies Fire Safety & Security Products Description Point State Variable Time MM8000 Installation, Function & Configuration, Commissioning, Safety Regulations 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 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 do not 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.
Appendix H - ULC compliance Event categories When ULC mode is set, the standard MM8000 event categories (Severe alarm, Alarm, Fault, Exclusion, Anomaly, Non default, and Warning) are replaced by ULCspecific categories. Namely: # 1 2 Category Fire Alarm Emergency Colour RED YELLOW Acronym ALM EMG 3 Supervisory YELLOW SUP 4 Building Safety YELLOW BLDG 5 Trouble YELLOW TBL 6 Exclusion ORANGE EXCL 7 Advisory BLUE ADV Description Fire alarms only.
Appendix I - Time synchronisation Time synchronisation from MM8000 server/FEP station: The MM8000 system (server or FEP station) issues a time synchronisation command to the connected subsystems daily at 4 a.m. (local time), and additionally when the PC date or time is modified in Windows. In turn, the PC can be synchronised by an external source (a dedicated network or domain application, a web service, or other).
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.
