The system shall be based on an open management platform with a flexible, full client-server architecture allowing scalability from small and medium systems to large and complex systems. The system must be certified to run on both physical and virtual environments (compatibility with VMware vSphere, Stratus, Hyper-V Virtualization and Nutanix) supporting High Availability configurations. The DMS user interface shall present well-arranged, relevant information to the user. It shall be ready for interaction without any overlapping windows and shall be coupled with event-oriented workflows, secured communication, and approved fire norm conformance.

The system must be designed for use with fire safety and security systems and enable users to:

  • Visualize and handle events (for example, acknowledge, silence, and reset).
  • Graphically monitor and control life safety and security systems.
  • Know where to start as the highest-priority events are highlighted.
  • Maintain continuous situational awareness of all fire and security panels with the graphical Node Map dashboard.
  • Directly navigate (with just one click) to the triggering element of an event.
  • Quickly navigate to custom operator instructions and graphical display of event locations.
  • Store and retrieve fire alarm system activity data.
  • Distribute fire, access, video and intrusion monitoring and control capabilities across a network of DMS management clients.
  • Provide Operating Procedure checklists to guide the operator, under stressful conditions, in handling significant events.
  • Display multiple video streams.
  • Automatically or manually, via graphical easy-buttons, send out remote notifications via email, SMS, and pagers with multi-level escalation, enhanced message tailoring and dynamic email attachment as well as the possibility for excluding recipients.
  • Include and exclude (isolate/de-isolate) system devices.
  • View and schedule automatic history reports.
  • View and schedule automatic (operator) tasks with revert action.
  • Provide “Ready To Arm” check for Intrusion.
  • Monitor and operate video surveillance systems. Typical video surveillance workflows shall be supported, including display of live video streams, PTZ and preset operations, recording, tagging and recording bookmarks, search and replay and multi-camera operations for operating procedures, camera groups and camera sequences.
  • Manage monitor walls and share video information and operations across the system.
  • View and handle the alarms and objects of the DMS from iOS and Android mobile phones and tablets (Mobile App) as well as from any web browser through a HTML5-based client (Flex Client).
  • Print out an ongoing record of the system’s operation (Journaling).

The system must also:

  • Include a web-based user interface that offers the same functionality as those on other workstations including operation (Flex Client).
  • Include an online engineering concept that speeds-up project commissioning time and minimizes system downtime.
  • Support a powerful and flexible library concept that allows, on the one hand standardization of system operation, and on the other a further drastic reduction of engineering time.
  • Support distributed architectures across different systems to enable scalability (up to 1.500.000 system objects) and separation by discipline and / or location.
  • Provide means for storing and archiving data for a period of more than 10 years, allowing as an option segregation of stored data in different groups.
  • Support multiple languages in the same project configuration. Project data, as well as user interface texts shall be displayed in the language of the user who is logging on the system. The user interface must support a minimum of 3 languages at the same time.
  • Support a wide range of product families from Fire Safety and Security systems.
  • Support open standard protocols (including BACnet, OPC DA, OPC UA, Modbus TCP, ONVIF, SNMP) to communicate with 3rd party devices. Communication options shall include local and networked connections.
  • Allow for custom extensions by means of a software development kit (SDK) to develop proprietary drivers, not supported by the system natively for communication with 3rd party subsystems and devices, or exchange of data with external applications by using the provided REST (Representational State Transfer) web service interfaces. The system must also provide possibilities to extend the functionality by adding new libraries containing scripts, graphic symbols, graphic templates, or object models to support subsystem integration, or optimize automated tasks.
  • Allow Enterprise Applications or other Management Systems to access real time values from integrated subsystems via OPC Server supporting the OPC DA (Data Access) specification and via BACnet Server.
  • Expose information via Cloud: The system must be able to connect to a cloud-based Building Management System (BMS) platform, that allows cloud-based SaaS applications to access data of the on-premise system.
  • The Cloud connectivity shall include:
    • A site onboarding process offering a simple engineering workflow.
    • The possibility to select the data to be exposed to the cloud.
    • The possibility to monitor and command data points and events for a fleet of sites.
    • A remote tunnel access to the DMS that allows to establish in an easy way a secure remote connection to the DMS and use the local HTML5 based client to drill down into more details for a specific site.
  • Ensure software robustness to cyber-attacks with the internationally recognized standards for industrial security ISA/IEC 62443, developed by the International Society of Automation (ISA) and adopted by the International Electrotechnical Commission (IEC).
    • The provider organization must have secure development processes certified to IEC 62443-4-1 Maturity Level 3 (ML3) or higher.
    • The building automation and control system must be certified to IEC 62443-4-2 Security Level 2 (SL2) or higher.
    • Cybersecurity guidelines must be available to support secure commissioning and deployment of the danger management system. The guidelines must describe how the system needs to be configured to foster secure operation of the products and solutions in the intended operating environment. The cybersecurity hardening guidelines must be maintained throughout the product lifecycle.
    • Cybersecurity penetration test results based on Open Web Application Security Project (OWASP) Application Security Verification Standard for systems with sensitive data (OWASP ASVS Level 2) must be available.
  • Allow for access protection, meaning that passwords must be assigned to authorized persons to guarantee transparency for tracking or authorization purposes. Password management must meet the customer’s IT guidelines; password management and the associated properties must comply with standard Windows log on and “track” the operator on each workstation.
  • Support the migration from MM8000 management stations.
  • Support an efficient engineering of floor plans based on the import of CAD files and an automatic placement of detectors.
  • Provide an easy generation of the floor plan graphics with access/evacuation route indications.