Digital twinning services for fire fighting systems

Abstract

To serve a fire safety system, all or part of the fire safety system is simulated (1404). The virtual representation may be used with a firmware (202) of an installed panel (102) or an actual panel (102) to be installed. The simulation (204) allows design, testing, troubleshooting, training, or other activities for designing, installing, or repairing the first security system. Using a virtual representation of at least part of a fire safety system can reduce latency, complexity and / or difficulty.

Description

Background Art

[0001] The present embodiments relate to fire safety systems. The fire safety system may include a fire alarm control panel connected or coupled to other fire alarm devices via one or more communication channels or networks. Fire safety systems may be quite complex, covering large spaces and / or many rooms or floors. For example, a fire safety system for a multi-story building may be installed floor by floor. The system may operate on most floors, but load balancing issues may arise as later floors are installed and join the overall system. The installation and testing of such systems typically occurs late in the construction process. Therefore, any delays due to issues with the design, logic, connectivity, or internal operability of components may result in undesirable delays. Testing of installed systems may be difficult given the occupancy of the building. Summary of the invention

[0002] Apparatus, systems, methods, and non-transitory computer readable media are provided for providing services to a fire safety system. All or part of a fire safety system is simulated. The virtual representation can be used with firmware for installed panels or actual panels to be installed. The simulation allows for design, testing, troubleshooting, training, or other activities for designing, installing, or repairing a first safety system. A virtual representation of at least part of a fire safety system can be used to reduce delays, complexity, and / or difficulty.

[0003] In a first aspect, an apparatus for providing services to a fire safety system is provided. A memory is configured to store a configuration of the fire safety system. The configuration of the fire safety system includes a panel and one or more components. A processor is configured to simulate communications of the one or more components. Execution of firmware of the panel includes processing of the simulated communications by the panel. A display is configured to display the processing of the communications.

[0004] In one embodiment, the firmware for the panel is firmware executable on the hardware of the installed panel. The communication of one or more components is simulated without executing the firmware of the one or more components.

[0005] In another embodiment, the processor is configured to execute firmware without the hardware of the panel. All fire safety systems are represented in the simulation. For example, the processor is configured to load a configuration, where the simulation is a test of the configuration including logic for running the fire safety system.

[0006] As another embodiment, the panel is configured to execute firmware. For example, a fire safety system includes a panel, a card, a detector, and an output device installed in a building. The one or more components are the card, the detector, and the output device and at least one component not installed in the building. The simulation is for at least one component not installed.

[0007] In yet another embodiment, the configuration of the fire safety system is a design configuration from fire safety system configuration software.

[0008] As an embodiment, the processor is configured to cause display on a display of one or more graphical user interfaces of one or more components, respectively, in the simulation. The graphical user interface represents the communication.

[0009] The embodiment uses a cloud server as a processor. The display is remote from the cloud server.

[0010] In various embodiments: the processor is configured to simulate communications based on logs of installed portions of the fire safety system, the simulation being for one or more components that cannot be installed, and / or the simulation being a simulation of communications corresponding to a hardware failure.

[0011] In another embodiment, a network including a fire safety system is simulated.

[0012] In a second aspect, a fire safety system includes a panel installed in a building and executing panel firmware. A first component is installed in the building and connected to the panel. A processor is configured to simulate one or more second components not installed in the building. The panel operates in response to the first component and in response to the simulation of the one or more second components.

[0013] According to one embodiment, the processor comprises a cloud server.In another embodiment, the panel operates as if the one or more second components are installed due to the simulation.

[0014] In a third aspect, a method for testing a fire safety system is provided. A configuration of the fire safety system is loaded. Interactions between parts of a first safety system are simulated based on the configuration. Results of the simulation are output.

[0015] In an embodiment, the simulation includes simulating the firmware of a panel of a fire safety system as one of the parts and the communication of other parts of the parts, wherein the entirety of the fire safety system is virtually represented. The result is output as a representation of a graphical user interface of the other parts.

[0016] According to one embodiment, a panel of a fire safety system is installed in a building. The panel is one of the components. The simulation includes simulating the communication of the other components with the panel. The results are output on the panel.

[0017] In another embodiment, the simulation is part of an automated test configuration.

[0018] Any one or more of the above aspects may be used alone or in combination. These and other aspects, features and advantages will become apparent from the following detailed description of the preferred embodiments, read in conjunction with the accompanying drawings. The present invention is defined by the appended claims, and nothing in this section should be construed as limiting these claims. Additional aspects and advantages of the present invention are discussed below in conjunction with the preferred embodiments, and may be claimed thereafter independently or in combination. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The components and drawings are not necessarily drawn to scale, emphasis instead being placed upon illustrating the principles of the embodiments. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the different views.

[0020] Figure 1 A block diagram illustrating one embodiment of a fire safety network installed in a building;

[0021] Figure 2 One embodiment of a simulation of a fire safety system with a digital twin of the entire fire safety system is shown;

[0022] Figure 3 One embodiment of a combination of installed and simulated portions of a fire safety system is shown;

[0023] Figure 4 A block diagram illustrating one embodiment of a simulation of a fire safety system in the cloud;

[0024] Figure 5 One embodiment of a display of a simulated configuration is shown;

[0025] Figure 6 One embodiment of a display of a simulated component is shown;

[0026] Figure 7 One embodiment of a display of a simulated network card for a fire safety system is shown;

[0027] Figure 8 One embodiment of a display for a simulated zone indicator card (output) module for a fire safety system is shown;

[0028] Figures 9 to 13 (inclusive FIG. 9A to FIG. 9B , FIG. 10A to FIG. 10B , FIG. 12A to FIG. 12B and FIG. 13A to FIG. 13B ) shows an embodiment of a graphical user interface for a simulator; and

[0029] Fig.14 A flow chart illustrating one embodiment of a method for testing a fire safety system. DETAILED DESCRIPTION

[0030] A virtual simulation (digital twin) of at least some of the fire panel, its peripherals, and the network is provided. For example, a simulation in a cloud environment or computer separate from the fire safety system is provided. The simulation can be run in a local computer or remotely (such as an edge application). In one embodiment, the digital twin system is automatically set up by parsing the fire safety system configuration file. Network access allows the digital twin system or simulation to be monitored and run. The simulation can interact with the installed hardware of the fire safety system, allowing the complete or entire fire safety system to be run even if some of the hardware is not running or installed.

[0031] Applications for simulation range from sales and training to assisting with development, commissioning, installation (e.g., using a mix of installed hardware and virtual components), and testing fire safety systems at scale. Additional examples include: using cloud applications as a customer sales tool to demonstrate the operation of a fire safety system; providing operational proof of concept for a large-scale system (scalability) without the required hardware; leveraging a digital twin of a fire safety system to work with approval authorities for logic approval prior to installation; allowing installers to pre-test configuration logic and debug before installing any hardware, resulting in a validated configuration; using partial installations of fire safety systems (hybrid configurations) where missing components (nodes, modules, sub-modules) are linked to installed components from a cloud service using simulation (e.g., the cloud can simulate all modules and components as the hardware is installed, and the real system under test will not show failures for missing hardware); faults); automated testing with built-in normal operation tests (Automatic Test Interface ATI); the ability to "play back" logs from a customer site or fire safety system via the cloud to enable the technical support team to reproduce bugs and provide faster, high-quality field support; provide "hands-on" operational training of fire protection systems in a classroom or distance learning environment without the required hardware; simulate the operation of products that are no longer in production or unavailable; provide a virtual R&D environment for product development; simulate faults that are extremely difficult or impossible on physical hardware (e.g., shorts or opens, which may otherwise require hardware damage); and / or shorten initialization time, allowing faster boot times, thereby reducing the time required to run system verification. Other uses include pre-acceptance of customer installations by the authority having jurisdiction, user training, customer support with quick turnaround without sending a technician to the site, on-site installation and commissioning, pre-test configurations, and / or as a sales tool.

[0032] Figure 1One embodiment of a fire safety system is shown. This embodiment is a simplified example of a fire safety system as installed in a building 100. The fire safety system can be used in a portion of a building, an entire building on one or more floors, and / or multiple building spaces. A building includes individual spaces, rooms, and / or floors, many or all of which include one or more parts of a fire safety system.

[0033] Various configurations may be planned or provided using different types and numbers of panels 102, cards 104, detectors 108, and / or outputs 110. Other types of components (nodes, modules, submodules, peripherals, and / or other fire safety system components) may be provided, such as intercoms and / or switches. The fire safety system is represented in a simplified manner to better discuss simulations, virtual representations, or digital twins to improve design, configuration, testing, installation, troubleshooting, and / or activities before, during, or after installation.

[0034] The fire safety system includes a panel 102, but multiple panels can be provided (e.g., single-node or multi-node systems). Any panel can be provided to control the operation of a partition, part, or all of the fire safety system. Generally speaking, the panel 102 carries a card 104 for linking with a computer, a computer network, a submodule, a peripheral device, and / or other parts of the fire safety system. The panel 102 can include a graphical user interface or display, as well as inputs for monitoring and / or controlling the fire safety system. The panel 102 includes one or more processors that operate by executing firmware designed specifically for the panel 102.

[0035] Any number of cards 104 can be provided. Card 104 can be directly connected to panel 102, or can be located outside the panel and connected to panel 102 in a wireless or wired manner. Card 104 includes circuits for networking, monitoring, outputting and / or controlling other components (e.g., submodules, detectors 108, outputs 110 or other peripherals). Card 104 can use wired and / or wireless connections (with or without the networking protocol of the network 106 established by card 106) to manage the communication between peripheral devices and panel 102. For example, one card 106 operates as a CAN bus, another card 104 establishes a proprietary communication network, and another card 104 provides Ethernet connection and communication. Some exemplary cards include power supplies, traditional detector line cards, detector line cards, conventional detector cards, zone indication cards, controllable relay modules, network interface cards, voice control cards, system status displays, and remote printer modules. Other cards can be provided.

[0036] Submodules may be provided, such as components connected between the card 104 and the peripherals 108, 110. Exemplary submodules include a switch control module, an LED control module, a live page board, a fan control module, a supervisory input module, an output control module, an amplifier, a telephone zone card, a firefighter master phone, and / or a live voice module. Other submodules may be provided.

[0037] Any number of peripherals may be provided, such as detectors 108 and outputs 110. Detector 108 is a smoke or gas detector. A pull switch or manual detector 108 may be included. Output 110 is a sprinkler, strobe, speaker, intercom, and / or other output for a fire safety system. Other peripherals include fans, sunshades, or other components for interacting with and / or controlling heating, air conditioning, and / or ventilation systems. Some exemplary peripherals include serial detectors, remote NAC control points, manual alarm buttons, conventional zone modules, indicator LEDs, four-way inputs, relay outputs, optical detectors, dual optical / heat detectors, dual optical / heat detectors / CO detectors, heat detectors, CO detectors, and / or heat detectors. Other peripherals may be provided.

[0038] Figure 2 and Figure 3 Different embodiments of an apparatus for providing services to a fire safety system are shown. The services include simulating all or part of the fire safety system. Figure 2 A simulation of the entire fire safety system is shown. Figure 3 A simulation of a portion of a fire safety system is shown, wherein the remainder of the fire safety system is provided by actual hardware, such as installed components.

[0039] The apparatus includes a processor 200, a memory 206, and a display 210, with or without any fire safety system hardware (e.g., panel 102, card 104, network 106, and / or peripherals). Additional, different, or fewer components may be provided. For example, the Internet, another computer network, a database, and / or other processors may be included. For another example, a graphical user interface or input device may be included.

[0040] Memory 206 is a random access memory, hard drive, cache, solid state, removable (e.g., magnetic disk or solid state drive), or other physical medium for storing data. Memory 206 or another memory may store instructions executable by processor 200. The instructions on non-transitory memory 206 are used to load, simulate, interact with installed hardware, and / or output operational or processing information for events from simulation. These instructions are used to implement FIG. 9 (including Fig. 9A and Fig. 9B ) method or another method.

[0041] In one embodiment, the memory 206 stores firmware for the panel 202, simulation models for various components to be simulated (eg, communication examples), firmware for components (communication formats for a network), and / or log files.

[0042] The memory 206 is configured to store information for the fire safety system. For example, a configuration 208 of the fire safety system is stored. The configuration provides components (e.g., panels 102, cards 104, networks 106, and / or peripherals (e.g., detectors 108 and outputs 110)) connected together with or without logic to be used. The designed or installed fire safety system configuration 208 is loaded into and stored by the memory 206.

[0043] In one embodiment, the configuration is formatted as provided by an engineering or design system, such as a "configuration tool" fire system configuration. Design configurations from fire safety system configuration software are stored. For example, a user uploads a configuration from the "configuration tool" to run the system in a virtual environment. In other embodiments, the configuration is formatted as a transformation of nodes and links between components for implementing a simulation.

[0044] The processor 200 is a general purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, an application specific integrated circuit, a tensor processor, a field programmable gate array, a digital circuit, an analog circuit, and / or a combination thereof. Based on the execution of instructions or as configured by software, firmware, and / or hardware, the processor 200 performs simulations of one or more components of the fire safety system.

[0045] In one embodiment, processor 200 is a server, such as a cloud server. Figure 4 An example is shown. A local computer 400 runs a browser 402 that shows a virtual graphical user interface 404 provided by a cloud server 410. The cloud server 410 is connected to the browser 402 of the local computer 400 via one or more computer networks. The cloud server 410 runs the simulator 204 based on the configuration 208 after the simulation is loaded by the SIM loader 412. In other embodiments, the simulation or simulator 204 is provided in a workstation or computer running locally (e.g., in a building) in the fire safety system. In yet another embodiment, the simulation or simulator 204 is provided at a computer away from the building that is to house or house the fire safety system. The remote computer implements the simulation and outputs the results on the display of the remote computer, rather than relying on a client-server device. The processor 200 can run as an edge service.

[0046] The processor 200 executes instructions for the simulator 204, which models the components of the device as provided in the configuration 208. For example, the processor 200 uses the cloud APP to demonstrate the operation of the fire protection system without any required hardware ( Figure 2 ), or only with a piece of hardware in the fire safety system ( Figure 3 ) to interact. The components, connections, and / or logic provided by the configuration 208 can be tested using the simulator 204. A graphical user interface 404 of the simulator 204 (such as a graphical user interface provided on the browser 402) allows interaction with the simulator 204 for testing, debugging, or other operations.

[0047] The simulator 204 simulates the operation of various components, such as card 104, network 106, detector 108 and / or output 110. The components to be simulated and the links or connections are provided by configuration 208 or are identified separately. In one embodiment, the simulator 204 simulates the component by simulating the communication to or from any given component. Only the communication or external transmission, display and / or reception are simulated, and the entire operation of the component is not simulated. The communication of one or more components can be simulated when the firmware for one or more components is running or not running. The simulator 204 uses messages designed for flexibility to communicate with the test automation interface, which provides messages to the panel firmware 202 and / or provides messages from the panel firmware. In alternative embodiments, the simulation includes the operation of the programming of firmware or components, such as using programming or physical models.

[0048] The simulator 204 includes an engine and interfaces, such as a program that runs a component model with or without an interface for formatting communications or establishing links with other devices (e.g., installed panels 102). Dynamic resource allocation may be used to host the simulator 204, where simulated components and / or simulated fire safety systems may be created and deleted as needed. Open source or other programming may be used.

[0049] Processor 200( Figure 2 ) or panel 102( Figure 3) executes firmware 202 for panel 102. Firmware is a program that will be or is being implemented by panel 102, including logic. The actual firmware 202 is run separately from the simulator 204. As configured by configuration 208, the actual firmware 202 is run by processor 200, panel 102, or another processor, rather than a complete simulation of panel 102. The execution of firmware 202 for panel 102 includes the processing of simulated communications by panel 102 (e.g., by firmware 202). The simulator 204 is communicatively linked to the firmware 202 (e.g., via a computer network using TCP / IP or other communication protocols / transport mechanisms). The firmware 202 is executable on the hardware of the installed panel 102 even if it has not yet been installed.

[0050] exist Figure 2 In the example of , the simulator 204 and the panel firmware 202 are deployed on the same processor 200, such as deployed as a cloud service. The user and / or configuration 208 selects the firmware version to match the configuration 208 and configures the simulator 204 to model various other components. The firmware 202 is executed without the panel 102 (i.e., without the hardware of the panel 102). The entire fire safety system is simulated using the firmware 202 and the simulator 204, and all of the fire safety system is represented in the simulation. The processor 200 is configured to load the configuration 208. The simulation is a test of the configuration including the logic for running the fire safety system.

[0051] exist Figure 3 In the example of , panel 102 is configured to execute firmware 202. The fire safety system includes panel 102, card 104, network 106, detector 108, and / or output device 110 installed in building 100. One or more components (e.g., card 104, network 106, detector 108, and / or output device 110) are not installed in building 100. The simulation is for the components that are not installed. Panel 102 operates in response to the installed components and in response to the simulation of other components. Panel 102 operates as if one or more of the components that are not installed are installed due to the simulation. Figure 3In the example of , an output device 110, a card 104, and a network 106 for the output device 110 are not installed and / or are simulated. Other allocations of simulated and installed portions of a fire safety system may be provided. For example, components are installed for one or more floors, but not for one or more other floors. A partial installation (hybrid configuration) of a fire protection system links the installed components (nodes, modules, submodules) to a simulator 204, such as using a digital twin to link to a cloud service. The processor 200 simulates all modules and components that are not installed. As the hardware is installed, the actual hardware may take over operation, causing the simulator 204 to stop simulating the component. Due to the simulation, the real system being tested will not show faults for missing hardware because the link to the simulator 204 replaces the missing hardware. This reduces diagnostic time because only new hardware-related defects introduced during installation will appear as defects. This allows phased builds to connect to ongoing sites using partial digital system points.

[0052] The display 210 is a display screen, such as a monitor, a liquid crystal display, a light emitting diode (LED) display, or another computer display. In one embodiment, the display 210 is a panel or component display, such as for actual installed hardware. Alternatively or additionally, the display 210 is a display of the processor 200 or the local computer 400 for interacting with the simulator 204 and / or the firmware 202 or displaying information from the simulator and / or the firmware. For example, the display 210 is a display screen of a local computer 400 that is remote from the cloud server 410.

[0053] The display 210 is configured by loading information (ie, images) into a display plane buffer and outputting the images to the display 210. The processor 200 or another controller (eg, the local computer 400) generates images to be displayed on the display 210.

[0054] The display 210 is configured to display the processing of the communication. The results from the simulation are displayed, such as showing the activation of components or communications and the resulting actions in other components of the fire safety system.

[0055] In one embodiment, the display 210 shows communications or operations associated with the simulator 204, while the installed hardware and / or the display 210 shows the effects on the installed hardware. In other embodiments, the display 210 shows both communications or operations (e.g., stimulus and / or response) for the simulator 204 and the effects on the installed hardware (e.g., the panel 102). A panel graphical user interface or display may be represented, or an actual display may be used.

[0056] The graphical user interface represents simulated communications. The graphical user interface shows installed and / or simulated interfaces as they appear to be installed, but other representations may be used. The look and feel of the displayed images reflects the look and feel of the installed hardware of the fire safety system. In other embodiments, the look and feel is different.

[0057] Figure 5 An example is shown in which the display 210 shows an image of one or more graphical user interfaces of one or more components in the simulation. The image displays the graphical user interface 502 (panel 1 GUI) of the panel separately from the graphical user interfaces (e.g., 500) of other components, indicating that the firmware 202 is running separately from the simulated components. The graphical user interface 500 of the simulator 204 includes an icon list of panels, cards, submodules, and peripherals of the fire protection system. The cards and / or peripherals shown are for the selected panel (e.g., the selected panel 1 as indicated by the bold line). The peripherals shown are for the selected card of the selected panel (e.g., the selected card 4 as indicated by the bold line). In the case of simulating communication, the peripherals participating in the communication are shown, such as by colored lights, flashing lights, or other highlights (e.g., detector 3 is triggered, causing alarm 3 and strobe 2 to be activated, as indicated by the bold line). The image can include outputs that simulate the outputs of the components as if they were installed on the hardware (e.g., the same as it), such as flashing LEDs or text for events.

[0058] A panel graphical user interface 502 (e.g., inputs and outputs on panel 102) is simulated in image 500. Panel graphical user interface 502 is provided as a separate image, and / or provided by actual panel hardware. In this simplified representation, panel 1 GUI shows detector 3 being activated, causing activation of alarm 3 and strobe 2. Other representations of panel outputs provided by running firmware may be used, such as flashing LEDs and / or text.

[0059] Other information may be provided, such as a line of text indicating the identification, type, address, and / or other information for any selected component. Other images may be used, such as representing each component separately. Figure 6 Exemplary images for components are shown. Figure 7 to Figure 1 3 shows various embodiments of the graphical user interface provided for the simulator 204.

[0060] Figure 6 An exemplary image is shown, showing a detector (eg, detector 1, see also FIG. 9 (including Fig. 9A and Fig. 9B) in the FDOT421 simulator GUI 600. The image represents the outputs and inputs of the detector hardware itself, the computer control available to the detector hardware, and / or any simulation models different from those available to the detector itself. The inputs and / or outputs available to the detector are listed, such as a list of communications to be output. Status, version, and / or other information (e.g., voltage, current, log, etc.) may also be displayed. Figure 6 In the example of FIG. 1 , the options for events for which outputs are generated include start-up test, smoke detection, open circuit or short circuit (e.g., as if the hardware is damaged or there is a customer installation problem). Output displays at the detector include smoke detection and communication failure, such as with text or labeled LEDs or flash codes. Additional, different or fewer options may be provided. A user or automated program may select one or more of the events to activate communication from the detector in the simulation.

[0061] Figure 7 An exemplary XDLC interface image is shown. The XDLC is a device line card that provides regional connections to various peripherals (e.g., detectors, alarm buttons, monitoring points). The XDLC interface image represents a graphical user interface for the card and simulates aspects of an XDLC device line card (e.g., peripherals by region). In the image, clicking on one of the small squares in the region will open the device details for that address (e.g., Figure 6 Graphical user interface 600).

[0062] Figure 8 An exemplary ZIC-4A interface image is shown. The ZIC-4A is a zone indicator card (e.g., a peripheral between a card or panel and another peripheral (e.g., a bell, horn, strobe). The ZIC-4A interface image emulates the Notification Appliance Circuit (NAC) available on the module. In the image, the ZIC is shown with check boxes corresponding to user-selectable events and configured zone divisions, as well as status indicators (e.g., marker LEDs).

[0063] A graphical user interface representing the actual hardware and / or other images representing the components addressed by the simulation may be provided. Various types of information may be represented, such as events, serial numbers, connections, addresses, etc.

[0064] Figure 9 (including Fig. 9A and Fig. 9B ) shows a graphical user interface 500 of the simulator 204 and a graphical user interface 502 of the firmware 202 (see Figure 5). In the example of FIG. 9 , an alarm for simulated communication is shown on the graphical user interface 500 of the simulator 204, wherein one of the boxes of peripheral devices is highlighted. A graphical user interface 600 for the highlighted peripheral device and XDLC card is also shown with communication-related operational information. The resulting display on the graphical user interface 502 of the panel 102 is shown. This shows the graphical user interface 500 of the simulator 204 and the graphical user interface 502 of the FS20M panel as presented as a cloud application. The FS20M system firmware is executing in a virtual environment. The XDLC (device line card) is a module that carries smoke detectors, alarm buttons, and other triggering devices. The smoke detector FDOT421 is shown in the alarm of the apartment 208. The FS20M system (e.g., panel GUI 502) visually indicates the alarm condition on the fire panel of the apartment 208.

[0065] Figure 10 (including Fig. 10A and Fig. 10B ) shows a view of the graphical user interface 500 of the simulator 204. Panels, cards and submodules are shown as boxes or icons. A graphical user interface 600 for selected components (e.g., submodules of two SCM-8 (switch control modules), one LCM-8 (LED control module), one SIM (supervisory input module), one OCM (output control module) and one SSD (system status display)) is shown as part of the simulator 204 graphical user interface 500. Operation and communication options for the submodules are displayed. This view shows representations of some simulated submodules in the simulated submodules as shown in the submodule diagram. The SCM and LCM represent their physical counterparts. The SIM and OCM are hardware modules, so the graphical user interface 600 has a different functional view than the actual modules.

[0066] Fig.11 An exemplary graphical user interface 500 of a simulator for configuring settings is shown. A drop-down, browse or other input is provided to identify or select a configuration to import. Naming and other inputs may be provided. This view shows the property settings for configuring the system before simulation begins. Many of the configuration items are automatically filled in.

[0067] Figure 12 (including Fig. 12A and Fig. 12B) shows an example of a collapsed view graphical user interface 500, in which graphical user interfaces 600 for various submodules (e.g., switch modules between cards and other peripherals) are shown. In this example, the modules are PSC-12 (power supply card), MLC (legacy detector line card), DLC (detector line card), XDLC (detector line card), CDC-4 (conventional detector card), ZIC-4A (zone indicator card), ZIC-8B (zone indicator card), CRC-6 (controllable relay module), and NIC-C (network interface card). This view shows a collapsed view of the modules in this configuration. The collapsed view is a true view of the modules as they would appear in the card box, with appropriate indicators (e.g., LEDs and labels).

[0068] Figure 13 (including Fig.13A and Fig. 13B ) shows an example where the graphical user interface 500 for the simulator 204 includes graphical user interfaces 600 for the XDLC, XTRI, ZIC-4A, and SSD submodules. This view shows an activated alarm on the XTRI (switch input type device). The device is configured to be on the XDLC (detector line card - address 6), and the address of the device is 11. The ZIC-4A (zone indicator card) is indicating that the bell is active on zone 1, and the SSD (system status display) is showing alarms at the XTRI-D at addresses 6-11. The small dot at address 8 in the module diagram indicates that there is an active zone, in this case zone 1.

[0069] The simulator 204 replaces installed hardware by simulating missing, uninstalled, replaced or downtime parts of the fire safety system. As discussed herein, simulation can be used for various purposes. For example, logs of installed fire safety systems can be accessed. When the firmware for the panel in the simulation is executed, the entire fire safety system or the relevant parts associated with the recorded events of interest are simulated. By replaying the logs from the customer site via the cloud, the technical support team can be helped to reproduce vulnerabilities, problems, and provide the ability to provide faster high-quality on-site support. Whether or not it is for an installed system, simulation can be used as a troubleshooting tool. Scenarios can be recreated from or for a site to investigate problems. Random or systematic tests, log-based or user-selected events (e.g., alarms, errors, etc.) can be used to initiate communications in the simulation to confirm the expected results.

[0070] In one embodiment, the simulation is for one or more components that cannot be installed. For example, a panel, firmware version, card, submodule, and / or peripheral device may no longer be manufactured or otherwise unavailable. The product may still be simulated, such as to prevent fault notifications, alarms, or other events.

[0071] In another embodiment, the simulation is a simulation of communications corresponding to a hardware failure. A simulation of a hardware failure (e.g., a short or open circuit) is provided without destroying or altering the hardware. Difficult or impossible failures on physical hardware can be simulated without damage to test the fire safety system's ability to react or appropriate action.

[0072] Simulation can be used for system validation. The pre-testing that needs to be completed is simplified. Some testing can be completed before equipment and labor are obtained using simulation. Testing of network, logic, and device configurations can be performed using simulation. Validation is provided when expansions or changes are or will be made to a site. For example, designers, commissioning engineers, and / or authorized agencies use a "digital twin" (i.e., simulation) of a fire protection system for testing. Simulation can be used for logic approval before installation. Installers can pre-test configurations and commission before installing hardware. Configuration problems can be corrected, and / or hardware requirements can be verified.

[0073] Simulations can be used to provide engineering support for site configuration. Fire system operators, commissioning engineers, technical support and / or R&D engineers can access logs for installed fire systems. The simulation plays back log events from the fire safety system or events of interest to reproduce vulnerabilities and provide changes or fixes. For example, logs are taken from a system where a failure occurred. The simulation plays back one or more events associated with the failure. After commissioning, a solution is created. The solution is tested using simulation. The installed fire safety system can then be updated.

[0074] Simulation can be used for staged builds or installations. A portion of the digital system (simulation) is connected to the site in progress. In this partial installation, the installed components (nodes, modules, sub-modules) are linked to a simulator (e.g., a cloud service). The simulator simulates all missing or non-installed components. As the hardware is installed, the real system under test will not show faults for missing hardware due to the simulation. For example, an installer, designer, commissioning engineer, facility owner, and / or authorized agency creates or accesses a configuration and virtually installs one or more components. The entire configuration can be used, with the virtual components removed when the real components are installed. Diagnostic time can be reduced because only new hardware-related defects introduced during installation will appear as defects.

[0075] Simulations can be used as a troubleshooting tool. Scenarios can be recreated from the site to investigate issues. Technical support, R&D engineers, and / or designers use simulations to create failure modes for debugging, create solutions, test solutions, and release updates for use by relevant customers.

[0076] Simulation can be used to automate operational testing. Technical support, engineers, licensing agencies, sales, and / or other personnel can demonstrate operations and / or testing for approval. A series of events can be tested, such as using test automation built into the simulator. Potential buyers and / or sales can use the simulator to demonstrate operations. Scalability can be tested without installing hardware.

[0077] Fig.14 One embodiment of a method for testing a fire safety system is shown. The simulation is used for testing, such as testing for commissioning, design, configuration approval, partial installation, and / or other purposes. Any of the uses of the simulation discussed above may be provided.

[0078] The method is implemented in the order shown or in other orders. Additional, different or fewer actions may be provided. For example, in action 1404, a simulation is provided based on an existing configuration, so action 1402 is not performed. In another example, actions 1406 and / or 1408 are not provided, such as where the fire safety system itself provides an incentive or outputs an incentive result. For another example, an action for using the results of the simulation is provided, including repeating the loading, simulating and / or outputting actions.

[0079] The method is implemented by a panel, a computer, a processor, a server, or a combination thereof. Other hardware, such as installed components of a fire safety system, may be used to implement the method.

[0080] In action 1402, a configuration of the fire safety system is loaded. For example, a user connects their computer to a fire alarm control panel via an XND module, an Ethernet port, or via a computer network (e.g., via a cloud connection). The user loads a configuration file through an interface. The panel is configured based on the configuration file. Similarly, the simulator is configured by the configuration file.

[0081] The simulator and / or user can establish a connection between existing hardware and the simulator as desired. For example, one or more ports of the interface of a panel or card are rerouted to connect with the simulator for simulating a specific component. This arrangement allows the panel or firmware for the panel to think or operate as if a fully functional set of hardware components were connected.

[0082] In action 1404, a processor implementing the simulator simulates the interaction between the parts of the fire safety system based on the configuration. The firmware of the panel of the fire safety system can be one of the parts in the simulation. Alternatively, the installed panel is used, so the firmware running on the installed panel is also a part.

[0083] Simulate the communication of any non-installed parts. The fire safety system may be virtually represented in its entirety, so that the simulation is a simulation of all parts. Panels and / or other parts may be installed. Simulate the communication form of non-installed or non-operating parts and provide them to or from the installed parts of the building. For example, install panels and components for one or more floors and / or parts of floors. The simulation is a simulation of other parts. Alternatively, the simulation is a simulation of a part being replaced or tested.

[0084] In a cloud-based simulation, modules, nodes, submodules and / or other components from the configuration appear in the simulator’s browser interface. The user can then simulate events and receive feedback from the fire protection system.

[0085] In one embodiment, simulation automatically tests the configuration. Can provide test automation of normal operation. Can provide system verification or pre-test. Tests can trigger events and query device status based on events. Tests are automated, such as using programming to trigger various communications to see results on a graphical user interface or in a log. Alternatively or additionally, tests are manual, where a user uses a graphical user interface to trigger events. With physical modules, it is difficult to create most events on demand. Simulation allows almost any event on demand. Logs generated from simulations can be viewed.

[0086] In action 1406, the interaction being simulated is a stimulus. For example, a smoke detection is simulated. In action 1408, the interaction being simulated is a response to the stimulus. For example, an alarm is simulated. Both the stimulus and the response can be simulated. Either action 1406 or 1408 can be performed by the fire safety system itself. For example, a detector is simulated, so action 1406 is performed by the simulator, and the fire safety system (e.g., a panel and bell) outputs a response.

[0087] In action 1410, the results of the simulation are output. The results can be output on a graphical user interface, a panel, or another output. For example, a log file is output. For another example, a list of events and results is output. In one embodiment, one or more graphical user interfaces of the simulator are outputs, such as showing triggering events and responses of the fire safety system (see Figure 5 , FIG9 or FIG13). Various graphical user interface representations of simulated and / or actual components may be output. The simulation may simulate the graphical user interface of the panel as output, or the panel itself may provide output (as a display on the panel).

[0088] The various improvements described herein may be used together or separately. Although illustrative embodiments of the present invention have been described herein with reference to the accompanying drawings, it should be understood that the present invention is not limited to those precise embodiments, and that various other changes and modifications may be made by those skilled in the art without departing from the scope or spirit of the present invention.

Claims

1. A device for providing services to a fire safety system, the device comprising: a memory configured to store a configuration of the fire safety system, the configuration of the fire safety system comprising a panel and one or more components; a processor configured to simulate communications of the one or more components, wherein execution of the panel's firmware includes processing of the simulated communications by the panel; as well as A display is configured to display the processing of the communication.

2. The device according to claim 1, wherein: The firmware for the panel comprises firmware executable on hardware of the installed panel, and wherein the communications of the one or more components are simulated without executing the firmware of the one or more components.

3. The device according to claim 1, wherein: The processor is configured to execute the firmware in the absence of the hardware of the panel, representing the entire fire safety system in the simulation; and The processor is configured to load the configuration, wherein the simulation is a test of the configuration including logic for operating the fire safety system.

4. The apparatus of claim 1, further comprising the panel, the panel being configured to execute the firmware, wherein: The fire safety system includes the panels, cards, detectors and output devices installed in the building; The one or more components include the card, the detector, and the output device, and at least one component not installed in the building; and The simulation is for the at least one component that is not installed.

5. The device according to claim 1, wherein: The configuration of the fire safety system includes a design configuration from fire safety system configuration software.

6. The device according to claim 1, wherein: The processor is configured to cause, in the simulation, display of a graphical user interface representing the communication on displays of one or more graphical user interfaces of the one or more components, respectively.

7. The device according to claim 1, wherein: The processor includes a cloud server, and the display is remote from the cloud server.

8. The device according to claim 1, wherein: The processor is configured to simulate the communications based on a log of an installed portion of the fire safety system.

9. The device according to claim 1, wherein: The simulation is for the one or more components that cannot be installed; The simulation is a simulation of communications corresponding to a hardware failure; or The simulation includes a network of the fire safety system.

10. A fire safety system comprising: Panels, which are installed in buildings and execute panel firmware; a first component installed in the building and connected to the panel; as well as a processor configured to simulate one or more second components not installed in the building; Wherein the panel operates in response to the first component and in response to a simulation of the one or more second components.

11. The fire safety system according to claim 10, wherein: The processor includes a cloud server.

12. The fire safety system according to claim 10, wherein: The panel operates as if the one or more second components are installed due to the simulation.

13. A method for testing a fire safety system, the method comprising: loading the configuration of the fire safety system; simulating interactions between parts of the first safety system based on the configuration; as well as Output the simulation results.

14. The method according to claim 13, wherein: The simulation comprises simulating using firmware of a panel of the fire safety system which is one of the parts and communications with other parts of the parts, wherein the fire safety system as a whole is virtually represented, and wherein outputting the result comprises outputting representations of graphical user interfaces of the other parts of the parts.

15. The method according to claim 13, wherein: A panel of the fire safety system is installed in a building, the panel being one of the parts, and wherein the simulation comprises simulating communication of other parts of the parts with the panel, and wherein the outputting comprises outputting on the panel.

Images