Security ecosystem, device and method for communicating with communication devices based on workflow interactions

A device monitors execution of a safety workflow, the safety workflow comprising one or more triggers and one or more responsive actions. The device provides, at a display screen, an indication of the safety workflow and respective visual indications of: a physical sensor that generated sensor data of a trigger of the safety workflow; and a communication device associated with a responsive action to the trigger. The device detects, via an input device, an interaction with one or more of the respective visual indications to interact with one or more of the physical sensor and the communication device. Based on the interaction, the device one or more of: retrieves the sensor data; initiates communication with the communication device; and sends the sensor data to the communication device.

BACKGROUND OF THE INVENTION

Managing multiple devices within a security ecosystem can be a time-consuming and challenging task. This task typically requires an in-depth knowledge of each type of device within the security ecosystem in order to produce a desired workflow when a security event is detected. For example, consider a school system that employs a security ecosystem comprising a radio communication system, a video security system, and a door access control system. Assume that an administrator wishes to implement a first workflow that notifies particular radios if a door breach is detected. Assume that the administrator also wishes to implement a second workflow that also notifies the particular radios when a security camera detects loitering. In order to implement these two workflows, the access control system may have to be configured to provide the notifications to the radios and the video security system may have to be configured to provide the notifications to the radios. Thus, both the access control system and the video security system may need to be configured separately in order to implement the two workflows. As is evident, this requires the administrator to have an in-depth knowledge of both the video security system and the access control system. Thus, the lack of continuity across systems is a burden to administrators since an in-depth knowledge of all systems within the ecosystem may be needed in order to properly configure workflows within the ecosystem.

In order to reduce the burden on administrators and enhance their efficiency, a need exists for a user-friendly interface tool that gives administrators the ability to configure and automate workflows that control their integrated security ecosystem. It would also be beneficial if such a tool equips administrators with the capabilities they need to detect triggers across a number of installed devices/systems and quickly take actions (execute workflows) to reduce the risk of breaches and downtime by automatically alerting the appropriate teams and executing the proper procedures.

DETAILED DESCRIPTION OF THE INVENTION

In order to address the above-mentioned need, a system, method, and apparatus for implementing workflows across multiple differing systems and devices is provided herein. During operation, a computing device, such as a workflow server, may monitor one or more triggers that occur in the differing systems and devices based on sensor data generated by, and received from one or more sensors, and, in response, implement one or more actions that may include communicating with one or more communication devices across the differing systems and devices, for example to dispatch security personnel associated with the one or more communication devices to locations at which the sensor data was collected that lead to the triggers. However, it may be challenging to communicate to the one or more communication devices the sensor data that lead to the one or more triggers and/or to change and/or control the safety workflows. Thus, there exists a need for an improved technical system, device, and system for communicating with communication devices based on workflow interactions.

Hence, provided herein is a computing device, for example in the form a workflow server interacting with a workstation, which monitors execution of a safety workflow and/or a plurality of safety workflows. A safety workflow is understood to include an association between a trigger, which occurs when certain conditions are met as determined using sensor data from a physical sensor, and an action, which occurs in response to the trigger and which may include at least an electronic interaction and/or communication with a communication device. One example trigger may comprise determining that a given door is open (e.g. and/or has been open for a given time period) and a responsive action may comprise communicating with a given communication device to dispatch security personnel operating the communication device to the location of the open door.

The computing device further provides, at a display screen (e.g. of the workstation), an indication of a safety work flow and respective visual indications of a physical sensor that generated sensor data of a trigger of the safety workflow and a communication device associated with a responsive action to the trigger. An input device may be used to detect an interaction with one or more of the respective visual indications to one or more of retrieve the sensor data, communicate with the communication device, and send the sensor data to the communication device.

An aspect of the specification provides a method comprising: monitoring, at a computing device, execution of a safety workflow, the safety workflow comprising one or more triggers and one or more responsive actions; providing, via the computing device, at a display screen, an indication of the safety workflow and respective visual indications of: a physical sensor that generated sensor data of a trigger of the safety workflow; and a communication device associated with a responsive action to the trigger; detecting, via the computing device and an input device, an interaction with one or more of the respective visual indications to interact with one or more of the physical sensor and the communication device; and based on the interaction, one or more of: retrieving the sensor data; initiating communication with the communication device; and sending the sensor data to the communication device.

Another aspect of the specification provides a device comprising: a network interface; and a processor configured to: monitor execution of a safety workflow, the safety workflow comprising one or more triggers and one or more responsive actions; provide, at a display screen, an indication of the safety workflow and respective visual indications of: a physical sensor that generated sensor data of a trigger of the safety workflow; and a communication device associated with a responsive action to the trigger; detect, via an input device, an interaction with one or more of the respective visual indications to interact with one or more of the physical sensor and the communication device; and based on the interaction, one or more of: retrieving, via the network interface, the sensor data; initiating, via the network interface, communication with the communication device; and sending, via the network interface, the sensor data to the communication device.

Each of the above-mentioned aspects will be discussed in more detail below, starting with example system and device architectures of the system in which the embodiments may be practiced, followed by an illustration of processing blocks for achieving an improved security ecosystem, device and method for communicating with communication devices based on workflow interactions.

Example embodiments are herein described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to example embodiments. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a special purpose and unique machine, such that the instructions, which execute via processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. The methods and processes set forth herein need not, in some embodiments, be performed in the exact sequence as shown and likewise various blocks may be performed in parallel rather than in sequence. Accordingly, the elements of methods and processes are referred to herein as “blocks” rather than “steps.”

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus that may be on or off-premises, or may be accessed via cloud in any of a software as a service (SaaS), platform as a service (PaaS), or infrastructure as a service (IaaS) architecture so as to cause a series of operational blocks to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions, which execute on the computer or other programmable apparatus provide blocks for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. It is contemplated that any part of any aspect or embodiment discussed in this specification can be implemented or combined with any part of any other aspect or embodiment discussed in this specification.

Turning now to the drawings, wherein like numerals designate like components,FIG.1illustrates a security ecosystem100capable of configuring and automating workflows across multiple systems. The security ecosystem100is interchangeably referred to hereafter as the system100. Furthermore, workflows as referred to herein may alternatively be referred as security workflows as workflows as referred to herein may be used to implement security-based action and/or security base processes.

The various components of the system100are in communication via any suitable combination of wired and/or wireless communication links, and communication links between components of the system100are depicted inFIG.1, and throughout the present specification, as double-ended arrows between respective components; the communication links may include any suitable combination of wireless and/or wired links and/or wireless and/or wired communication networks, and the like.

As shown, the security ecosystem100comprises a public-safety network130, a video surveillance system140, a private radio system150, and an access control system160. A workflow server102is coupled to each system130,140,150, and160. The workstation101is shown coupled to the workflow server102, and is utilized to configure the workflow server102with workflows, for example as generated by a user. It should be noted that although the components inFIG.1are shown geographically separated, these components can exist within a same geographic area, such as, but not limited to a school, a hospital, an airport, a sporting event, a stadium, a factory, a warehouse and/or any other suitable location and/or building and the like. It should also be noted that although only networks and systems130,140,150,160are shown inFIG.1, many more networks and/or systems may be included in the security ecosystem100and/or any suitable number of networks and/or systems may be included in the security ecosystem100.

The workstation101may comprise a computer configured to execute Motorola Solution™'s Orchestrate™ and Ally™ dispatch and incident management software. As will be discussed in more detail below, the workstation101is configured to present a user with a plurality of triggers capable of being detected by the network and systems130,140,150,160as well as present the user with a plurality of actions capable of being executed by the network and systems130,140,150,160. The user will be able to generate workflows and upload these workflows to the workflow server102based on the presented triggers and actions. While only one workstation101, the system100may comprise a plurality of workstations101.

The workflow server102may comprise a server running Motorola Solution™'s Command Central™ software suite comprising the Orchestrate™ platform. While the workflow server102is depicted as one device, the workflow server102may be implemented as one or more computing devices, one or more servers, one or more cloud computing devices, and the like, and/or the functionality of the workflow server102may be geographically distributed.

The workflow server102is configured to receive workflows generated by the workstation101(and/or a plurality of workstations101) and implement the workflows. Furthermore, the workflow server102may implement (e.g., concurrently, and the like) different workflows associated with different workstations. Particularly, the workflows are implemented by analyzing events detected by the network and systems130,140,150,160and executing appropriate triggers. In a particular example, a user may generate a workflow on the workstation101that has a trigger comprising the video surveillance system140detecting a loitering event, and has an action comprising notifying radios within the public-safety network130. When this workflow is uploaded to the workflow server102, the workflow server102will notify the radios of any loitering event detected by the video surveillance system140.

The public-safety network130is configured to detect various triggers and report the detected triggers to the workflow server102. The public-safety network130is also configured to receive action commands from the workflow server102and execute the actions. In some examples, the public-safety network130comprises includes typical radio-access network (RAN) elements such as base stations, base station controllers (BSCs), routers, switches, and the like, arranged, connected, and programmed to provide wireless service to user equipment, report detected events, and execute actions received from the workflow server102.

The video surveillance system140is configured to detect various triggers and report the detected triggers to the workflow server102. The video surveillance system140is also configured to receive action commands from the workflow server102and execute the actions. In one example, the video surveillance system140comprises a plurality of video cameras that may be configured to automatically change their field-of-views over time. The video surveillance system140is configured with a recognition engine/video analysis engine (VAE) that comprises a software engine that analyzes any video captured by the cameras using, for example, any suitable process which may include, but is not limited to machine learning algorithms, convolutional neural networks (CNNs), and the like. Using the VAE, the video surveillance system140is capable of “watching” video to detect any triggers and report the detected triggers to the workflow server102. These triggers may include, but are not limited to, appearance searches and unusual Activity Detection (e.g., loitering). In a similar manner, the video surveillance system140is configured to execute action commands received from the workflow server102. In some examples, the video surveillance system140comprises an Avigilon™ Control Center (ACC) server having Motorola Solution™'s Access Control Management (ACM)™ software suite.

The private radio system150may comprise a private enterprise radio system that is configured to detect various triggers and report the detected triggers to the workflow server102. The private radio system150is also configured to receive action commands from the workflow server102and execute the actions. In some examples, the private radio system150comprises a MOTOTRBO™ communication system having radio devices that operate in the Citizens Broadband Radio Service (CBRS) spectrum and combines broadband data with voice communications.

The access control system160comprises an Internet-of-Things (IoT) network which may serve to connect every-day devices to the Internet. Devices such as cars, kitchen appliances, medical devices, sensors, doors, windows, HVAC (heating, ventilation, and air conditioning) systems, drones, . . . , etc. can all be connected through the IoT network of the access control system160. Indeed, any suitable device that can be powered may be connected to the internet to control its functionality. The access control system160generally allows objects to be sensed or controlled remotely across existing network infrastructure. For example, the access control system160may be configured to provide access control to various doors and windows. In particular, the access control system160is configured to detect various triggers (e.g., door opened/closed) and report the detected triggers to the workflow server102. The access control system160is also configured to receive action commands from the workflow server102and execute the action received from the workflow server102. The action commands may take the form of instructions to lock, open, and/or close a door or window.

As is evident, the security ecosystem100allows an administrator using the workstation101to generate rule-based, automated workflows between technologies to enhance efficiency, and improve response times, effectiveness, and overall safety. The security ecosystem100generally has the capability to detect triggers across a number of devices within network and systems130,140,150,160and quickly take actions by automatically executing the proper procedure (i.e., executing the appropriate action once a trigger is detected).

The network and systems130,140,150,160are next described in further detail.

FIG.2illustrates a security ecosystem capable of configuring and automating workflows. In particular,FIG.2shows the security ecosystem100with an expanded view of the public-safety network130. As shown, the public-safety network130comprises a dispatch center131, a public-safety core network132, a gateway133, a radio access network (RAN)135, a plurality of personal-area networks (PANs)136, and at least one radio137, such as a public-safety radio and the like (however the radios137may include, but are not limited to, any suitable combination of communication devices, such as mobile phones, two-way radios, and the like). As shown, each PAN136comprises a radio137acting as a hub to smart devices/accessories/sensor138(interchangeably referred to hereafter as the sensors and/or a sensor138). Hereafter the radios137may be interchangeably referred to as a communication device137.

The gateway133may comprise an Avigilon™ Control Center running Avigilon's Access Control Management software. The gateway133is configured to run any suitable Application Program Interface (API) to provide communications between the public-safety core network132and the workflow server102.

A public safety officer (not shown inFIG.2) may be equipped with sensors138that determine various physical and environmental conditions surrounding the public-safety officer. These conditions may be reported back to, for example, the dispatch center131or the workflow server102so an appropriate action may be taken. For example, police officers may have a sensor138(e.g. in the form of a gun-draw sensor) that determines when a gun is drawn. Upon detecting that an officer has drawn their gun, a notification may be sent back to the dispatch operator and/or the workflow server102so that, for example, other officers in the area may be notified of the situation.

It is envisioned that the public-safety officer may have an array of these sensors138available to the officer at the beginning of a shift. The officer may select and pull sensors138off a shelf, and form a personal-area network (PAN)136with the devices that may accompany the officer on their shift. For example, the officer may pull a gun-draw sensor, a body-worn camera, a wireless microphone, a smart watch, a police radio, smart handcuffs, a man-down sensor, a bio-sensor, and the like. All sensors138pulled by the officer may be configured to form a PAN136by associating (pairing) with each other and communicating wirelessly among the devices. At least one device may be configured with a digital assistant. In some examples, a PAN136comprises more than two sensors138, so that many sensors138may be connected via a PAN136simultaneously.

A method called bonding may be used for recognizing specific sensors138and thus enabling control over which accessories are allowed to connect to each other when forming a PAN136. Once bonded, accessories then can establish a connection without user intervention. A bond may be generated through a process called “pairing”. The pairing process may be triggered by a specific request by the user to generate a bond from a user via a user interface on the accessories. Thus, as shown, public-safety network130incorporates PANs136generated as described above. In some examples, radios137and sensors138form a PAN136, with communication links between sensors138and radios137taking place utilizing a short-range communication system protocol such as a Bluetooth communication system protocol. In this particular example, a PAN136may be associated with a single officer. Thus,FIG.2illustrates multiple PANs136associated with multiple officers (not shown).

The RAN135may include various RAN elements such as base stations, base station controllers (BSCs), routers, switches, and the like, arranged, connected, and programmed to provide wireless service to user equipment (e.g., the radios137, and the like) in a manner known to those of skill in the relevant art. The RAN135may implement a direct-mode, conventional, or trunked land mobile radio (LMR) standard or protocol such as European Telecommunications Standards Institute (ETSI) Digital Mobile Radio (DMR), a Project 25 (P25) standard defined by the Association of Public Safety Communications Officials International (APCO), Terrestrial Trunked Radio (TETRA), or other LMR radio protocols or standards. In other examples, the RAN135may implement a Long Term Evolution (LTE), LTE-Advance, or 5G protocol including multimedia broadcast multicast services (MBMS) or single site point-to-multipoint (SC-PTM) (including, but not limited to open mobile alliance (OMA) push to talk (PTT) over cellular (OMA-PoC)), a voice over IP (VoIP), an LTE Direct or LTE Device to Device, or a PTT over IP (PoIP) application may be implemented. In still further examples, the RAN135may implement a Wi-Fi protocol for example operating in accordance with an IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g) or a WiMAX protocol for example operating in accordance with an IEEE 802.16 standard.

The public-safety core network132may include one or more packet-switched networks and/or one or more circuit-switched networks, and in general provides one or more public-safety agencies with any suitable computing and communication needs, transmitting any suitable public-safety-related data and communications.

For narrowband LMR wireless systems, the public-safety core network132may operate in either a conventional or trunked configuration. In either configuration, a plurality of communication devices is partitioned into separate groups (talkgroups) of communication devices. In a conventional narrowband system, each communication device in a group is selected to a particular radio channel (frequency or frequency & time slot) for communications associated with that communication device's group. Thus, each group is served by one channel, and multiple groups may share the same single frequency (in which case, in some examples, group IDs (identifiers) may be present in the group data to distinguish between groups using the same shared frequency).

In contrast, a trunked radio system and its communication devices use a pool of traffic channels for virtually an unlimited number of groups of communication devices (e.g., talkgroups). Thus, all groups are served by all channels. The trunked radio system works to take advantage of the probability that not all groups need a traffic channel for communication at the same time.

Group calls may be made between radios137and other devices via wireless transmissions in accordance with either a narrowband or a broadband protocol or standard. Group members for group calls may be statically or dynamically defined. That is, in a first example, a user or administrator may indicate to the switching and/or radio network (such as at a call controller, PTT server, zone controller, or mobile management entity (MME), base station controller (BSC), mobile switching center (MSC), site controller, Push-to-Talk controller, or other network device) a list of participants of a group at the time of the call or in advance of the call. The group members (e.g., communication devices) could be provisioned in the network by the user or an agent, and then provided some form of group identity or identifier, for example. Then, at a future time, an originating user in a group may cause some signaling to be transmitted indicating that he or she wishes to establish a communication session (e.g., join a group call having a particular talkgroup ID) with each of the pre-designated participants in the defined group. In another example, communication devices may dynamically affiliate with a group (and also disassociate with the group) c based on user input, and the switching and/or radio network may track group membership and route new group calls according to the current group membership.

The radios137generally serve as PAN main devices, and may be any suitable computing and communication device configured to engage in wireless communication with the RAN135over the air interface as is known to those in the relevant art. Moreover, one or more radios137are further configured to engage in wired and/or wireless communication with one or more local sensor138via a local communication link. The radios137may be configured to determine when to forward information received from PA sensors138to, for example, a dispatch center or the workflow server102.

Some examples of sensors138follow:

In some examples, a sensor138may comprise a sensor-enabled holster that maintains and/or provides state information regarding a weapon or other item normally disposed within the user's sensor-enabled holster. The sensor-enabled holster may detect a change in state (presence to absence) and/or an action (removal) relative to the weapon normally disposed within the sensor-enabled holster. The detected change in state and/or action may be reported to a radio137via its short-range transceiver, which may forward the state change to the dispatch center131or the workflow server102. In some examples, the sensor-enabled holster may also detect whether the first responder's hand is resting on the weapon even if it has not yet been removed from the holster and provide such information to portable radio137.

In some examples, a sensor138may comprise a biometric sensor (e.g., a biometric wristband) for tracking an activity of the user or a health status of a user, and may include one or more movement sensors (such as an accelerometer, magnetometer, and/or gyroscope) that may periodically or intermittently provide to a radio137indications of orientation, direction, steps, acceleration, and/or speed, and indications of health such as one or more of a captured heart rate, a captured breathing rate, and a captured body temperature of the user, for example accompanying other information. This information may be reported to a radio137which may forward the information to the dispatch center131and/or the workflow server102.

In some examples, a sensor138may comprise an accelerometer to measure acceleration. Single and multi-axis models are available to detect magnitude and direction of the acceleration as a vector quantity, and may be used to sense orientation, acceleration, vibration shock, and falling. The accelerometer may determine if an officer is running. A gyroscope is a device for measuring or maintaining orientation, based on the principles of conservation of angular momentum. One type of gyroscope, a microelectromechanical system (MEMS) based gyroscope, uses lithographically constructed versions of one or more of a tuning fork, a vibrating wheel, or resonant solid to measure orientation. Other types of gyroscopes could be used as well. A magnetometer is a device used to measure the strength and/or direction of the magnetic field in the vicinity of the device, and may be used to determine a direction in which a person or device is facing. This information may be reported to a radio137which may forward the information to dispatch center131and/or the workflow server102.

In some examples, a sensor138may comprise a heart rate sensor that uses electrical contacts with the skin to monitor an electrocardiography (EKG) signal of its wearer, or may use infrared light and imaging device to optically detect a pulse rate of its wearer, among other possibilities. This information may be reported to a radio137which may forward the information to the dispatch center131and/or the workflow server102.

In some examples, a sensor138may comprise a breathing rate sensor138to monitor breathing rate. The breathing rate sensor may include use of a differential capacitive circuits or capacitive transducers to measure chest displacement and thus breathing rates. In other examples, a breathing sensor may monitor a periodicity of mouth and/or nose-exhaled air (e.g., using a humidity sensor, temperature sensor, capnometer or spirometer) to detect a respiration rate. Other possibilities exist as well. This information may be reported to a radio137which may forward the information to the dispatch center131and/or the workflow server102.

The dispatch center131may comprise, and/or may be part of, a computer-aided-dispatch center (sometimes referred to as an emergency-call center or public-safety answering point), that may be manned by an operator providing any suitable dispatch operations. For example, the dispatch center131may comprise a graphical user interface that provides the dispatch operator any suitable information about public-safety officers. As discussed above, some of this information originates from sensors138providing information to radios137, which forwards the information to the RAN135and ultimately to the dispatch center131.

In a similar manner, information about public-safety officers may be provided to the workflow server102. This information may originate from the sensors138providing information to the radios137, which forwards the information to the RAN135and ultimately to the workflow server102via the public-safety core network132and the gateway133. For example, a sensor138comprising a gun-draw sensor may send an indication to the workflow server102that a gun has been drawn. This may serve as a “trigger” for the workflow server102to initiate a particular “action”, for example, notifying surrounding officers (for example on a particular talkgroup) by having their radios137provide an alarm indicating the triggering event. Thus, the workflow server102may provide instructions to any sensor138or radio137by sending an “action” to a sensor138in response to a trigger being received.

FIG.3illustrates a security ecosystem capable of configuring and automating workflows. In particular,FIG.3shows the security ecosystem100with an expanded view of the video surveillance system140. As shown, the video surveillance system140comprises a plurality of image sensors and/or cameras142and the gateway141.

Cameras142may be fixed or mobile, and may have pan/tilt/zoom (PTZ) capabilities to change their field-of-view. The cameras142are generally understood to comprise image sensors and hence may also be referred to as images sensors. Cameras142may also comprise circuitry configured to serve as a VAE143(only one of which is depicted inFIG.3, though it is understood that any camera142may comprise circuitry configured to serve as a VAE143). The VAE143comprises a software engine that analyzes analog and/or digital video. The VAE143is generally configured to “watch” video and detect pre-selected objects such as license plates, people, faces, automobiles. The VAE143may also be configured to detect certain actions of individuals, such as fighting, loitering, crimes being committed, . . . , etc. and/or actions of objects, such as speeding, a car driving on a pedestrian walkway, a car moving against the flow of traffic, . . . , etc.; however the VAE143may be configured to detect any suitable action. The VAE143may contain any of several object/action detectors. Each object/action detector “watches” the video for a particular type of object or action. Object and action detectors can be mixed and matched depending upon what is trying to be detected. For example, an automobile object detector may be utilized to detect automobiles, while a fire detector may be utilized to detect fires. Combinations of object detectors may be utilized to detect combinations of objects, such as automobiles on fire, and the like, automobiles that are not on fire, and the like.

The gateway141may comprise an Avigilon™ Control Center running Avigilon's Access Control Management software. The gateway141is configured to run any suitable Application Program Interface (API) to provide communications between any cameras142and the workflow server102.

FIG.4illustrates a security ecosystem capable of configuring and automating workflows. In particular,FIG.4shows the security ecosystem100with an expanded view of the private radio system150. As shown, the private radio system150comprises the gateway151, system infrastructure152, and at least one radio153. Communications from the radio153to the workflow server102passes through the system infrastructure152, the gateway151, and ultimately to the workflow server102. Hereafter the radios153may be interchangeably referred to as a communication device153.

The gateway151may comprise an Avigilon™ Control Center running Avigilon's Access Control Management software. The gateway151is configured to run any suitable Application Program Interface (API) to provide communications between any of the system infrastructure152and the workflow server102.

The system infrastructure152comprises any suitable equipment to provide wireless communications to and from the radio153. The system infrastructure152may comprise Motorola Solution™'s MOTOTRBO™ equipment, such as an SLR Series Repeater (e.g., SLR 1000, SLR 5000, or SLR8000 repeater) configured to provide two-way radio service to radio153.

Although only a single radio153is shown inFIG.4, any suitable number of radios153may be present within the private radio system150. Each radio153may comprise a MOTOTRBO™ two-way radio (such as a Motorola Solution™ XPR 5000 Series radio) with digital technology providing integrated voice and data communication.

FIG.5illustrates a security ecosystem capable of configuring and automating workflows. In particular,FIG.5shows the security ecosystem100with an expanded view of the access control system160. As shown, the access control system160comprises a gateway162and a plurality of IoT devices163coupled to the gateway162. Data passed from the workflow server102to the IoT devices163passes through the network161, the gateway162and ultimately to the IoT device163. Conversely, data passed from the IoT devices163to the workflow server102passes through the gateway162, the network161, and ultimately to the workflow server102.

The gateway162may comprise an Avigilon™ Control Center running Avigilon's Access Control Management software. The gateway162is configured to run any suitable Application Program Interface (API) to provide communications between any IoT device163and the workflow server102.

The network161may comprise one of many networks used to transmit data, including, but not limited to, a network employing one of the following protocols: conventional, or trunked LMR standard or protocol such as ETSIDMR, a 25 standard defined by the APCO, TETRA, or other LMR radio protocols or standards; LTE protocol, LTE-Advance protocol, or 5G protocol including multimedia broadcast MBMS or SC-PTM protocol (including, but not limited to an OMA-PTT OMA-PoC), a VoIP protocol, an LTE Direct or LTE Device to Device protocol, or a PoIP protocol, a Wi-Fi protocol for example operating in accordance with an IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g) or a WiMAX protocol for example operating in accordance with an IEEE 802.16 standard.

FIG.6is a block diagram of the workflow server102ofFIG.1. As shown, the workflow server102comprises a network interface601, a storage component602(e.g. as depicted a database, but may comprise any suitable memory and/or storage component), and a processor603. The processor603is understood to include any suitable logic circuitry.

The network interface601includes any suitable components for communicating with other suitable components of the system100, in particular, as depicted, to the workstation101, the gateways133,141,151,162of the networks and systems130,140,150,160, and the like. Components of the network interface601include any suitable processing, modulating, and transceiver components that are operable in accordance with any one or more standard or proprietary wireless interfaces, wherein some of the functionality of the processing, modulating, and transceiver components may be performed by means of the processor603through programmed logic such as software applications or firmware stored on the storage component602(e.g., standard random access memory) or through hardware. The network interface601may include any suitable wired or wireless network interfaces, including, but not limited to, Ethernet interfaces, T1 interfaces, USB interfaces, IEEE 802.11b interfaces, IEEE 802.11g interfaces, and the like.

The processor603may comprise a digital signal processor (DSP), general purpose microprocessor, a programmable logic device, or application specific integrated circuit (ASIC), and the like, and is generally configured to receive triggers from various gateways, systems, and networks (e.g. of the system100). The processor603is further configured to execute (or cause to be executed) a particular action for a trigger that is received. More particularly, when the processor603receives a trigger from any network or system, the processor603may access the storage component602to determine an action for the particular trigger. Once an action has been determined, the processor603will execute the action, or cause the action to be executed. In order to perform the above, the processor603may execute an instruction set/software (e.g., Motorola Solution™'s Command Central™ software suite comprising the Orchestrate™ platform) which may be stored at the storage component602.

The storage component602may comprise standard memory (such as Random Access Memory (RAM), Read Only Memory (ROM), and the like) and generally serves to store associations between triggers and actions. Examples of various triggers and actions are illustrated in in Table 1, below.

FIG.7is a block diagram of the workstation101ofFIG.1utilized to generate a workflow. As shown, the workstation101comprises a network interface701, a storage component702, a processor703, and a graphical user interface (GUI)704.

The network interface701includes any suitable components for communicating with other suitable components of the system100, in particular, as depicted, to the workflow server102. Components of the network interface701include any suitable processing, modulating, and transceiver components that are operable in accordance with any one or more standard or proprietary wireless interfaces, wherein some of the functionality of the processing, modulating, and transceiver components may be performed by means of the processor703through programmed logic such as software applications or firmware stored on the storage component702(e.g., standard random access memory) or through hardware. The network interface701may include any suitable wired or wireless network interfaces, including, but not limited to, Ethernet interfaces, T1 interfaces, USB interfaces, IEEE 802.11b interfaces, IEEE 802.11g interfaces, and the like.

Processor703may comprise a DSP), general purpose microprocessor, a programmable logic device, or an ASIC and may be configured to execute Motorola Solution™'s Orchestrate™ and Ally™ dispatch and incident management software which may be stored at the storage component702. The execution of such software may allow users of the GUI704to generate workflows (i.e., actions and their associated responses) by receiving user inputs at the GUI704that define various triggers and their associated actions, which will ultimately be uploaded to the workflow server102and stored in the storage component602.

The storage component702may comprise standard memory (such as RAM, ROM, and the like) and serves to store instructions as software. Particularly, Motorola Solution™'s Orchestrate™ and Ally™ dispatch and incident management software may be stored at the storage component702.

The GUI704generally provides a man/machine interface for receiving an input from a user and displaying information. For example, the GUI704may provide a mechanism of conveying (e.g., displaying) user-generated workflows. Thus, the GUI704may also provide a mechanism for a user to input workflows into a displayed form. In order to provide the above features (and additional features), the GUI704may include any combination of a display screen705(e.g., a computer screen, which may include a touch screen, a monitor, and the like) and any suitable combination of one or more input devices706(e.g. a keyboard and mouse combination).

FIG.8illustrates the generation of a workflow. More particularly,FIG.8illustrates a dashboard800rendered at the display screen705utilized for the generation of workflows. As depicted, the dashboard800consists of the following main components:a selection panel801(e.g. on a left-hand side), which lists available triggers806and actions807;a workspace802, which comprises a large area in the middle of the dashboard800used to generate workflows that define the connections between triggers and actions. Each workflow in the workspace is displayed as a separate field808,809with an outline and a title. As shown inFIG.8, two fields808,809are shown, one labeled “trigger” and another labeled “action”.

While the dashboard800is depicted in a particular configuration, the dashboard800may have any suitable configuration; for example, the selection panel801may be on a right-hand side, a top side or a bottom side relative to the workspace802.

The triggers806represent the events originating from various sensors, software, and devices within the security ecosystem100. The actions807represent the possible responses to the triggers that may be implemented via any suitable various sensors, software, and devices within the security ecosystem100, including, but not limited to, the radios137,153.

After a workflow is deployed (i.e., uploaded to the workflow server102), its actions activate when the triggers occur. Triggers and actions appear on the workspace after they are dragged and dropped from the triggers806and actions807tabs respectively. For example, as depicted, the field808represents a trigger806that may have been dragged and dropped to the workspace802and the field809represents an action807that may have been dragged and dropped to the workspace802. Connecting the triggers and actions on the workspace (as described below) will generate a workflow.

The triggers806and the actions807are generally stored at the storage component702and represent integrations across multiple products. In other words, triggers806and the actions807comprise triggers and actions for any suitable components available in the security ecosystem100. This includes cameras, sensors, IoT devices, radios, . . . , etc. As administrators add additional technology pieces to the security ecosystem100, those pieces may be automatically made available for workflow generation as discussed herein.

In order to associate a trigger806with an action807in the workspace802, a user selects a trigger806from all possible triggers806, and drags and drops it onto workspace802, as represented by the field808. The user then selects an action807for the trigger806that is in the workspace802, and drags and drops it onto workspace802. Once in the workspace802, a trigger806may be referred to as a trigger node, and an action807may be referred to as an action node. In order to associate the trigger806with the action807, they are connected. To connect a trigger node to an action node, a user may click an end of the trigger node (e.g. that is closest to the action node) and drag a line to the action node, or vice versa. However, any suitable process for connecting nodes is within the scope of the present specification.

As shown inFIG.9, which depicts the dashboard800in use, a trigger “ALPR Delivery Truck”901has been associated with an action “Unlock Backdoor”902by dragging a line903between the two, thereby forming a workflow904. While only one trigger901and one action902is depicted in the workflow904, the workflow904may comprise any suitable number of triggers (e.g. a trigger group) and any suitable numbers of associated action (e.g. an action group). Hence, if any of the triggers within a trigger group occurs, the workflow904is initiated causing the action to be executed. For example, as depicted ALPR stands for automated license plate reader, which may be one of the IoT devices163; as such, according to the workflow904, when automated license plate reader of the access control system160“reads” a license plate of a delivery truck (e.g. the trigger901), an associated backdoor (e.g. of a warehouse) is opened; such a backdoor may also comprise one of the IoT devices163. While note depicted, a memory in the system100may also store a list of license plates for which the backdoor is to be opened and the trigger901may include comparing a number of the license plate that is read with license plates in such a list, such that the backdoor is opened only when the license plate is on the list.

Furthermore, it is understood that the system100may comprise a plurality of IoT devices163that are automated license plate readers, and that the trigger901may be for a particular automated license plate reader; as such, while not depicted, the actions807may include respective “ALPR” actions807for other automated license plate reader. Similarly, it is understood that the system100may comprise a plurality of IoT devices163that are backdoors, and that the action902may be for a particular backdoor; as such, while not depicted, the actions807may include respective “Unlock Backdoor” actions807for other backdoors.

For example, as depicted the triggers806include a trigger806for detecting loitering at a particular “North West” (e.g. NW) staircase of a particular building (e.g. “Loitering NW Staircase”) that may be detected using a VAE143of one or more cameras142and the like. The triggers806further includes a trigger806for detecting whether a particular backdoor is open (e.g. “Backdoor Open”) that may be detected using a VAE143of one or more cameras142and/or an open/closed sensor on the backdoor and the like. The triggers806further includes a trigger806for detecting whether a particular individual, for example a first responder and/or police officer and/or security guard having an identifier “SAM12” has an elevated body temperature (e.g. “Elevated Body Temp SAM12”) that may be detected using a biometric sensor of one or more sensors138and the like.

For example, as depicted the actions807include an action807for notifying a first responder and/or police and/or security dispatch (e.g. “Notify Dispatch”) such as the dispatch center131. The actions807further includes an action807for alerting a particular talkgroup identified by the identifier TG1 and/or Talkgroup #1 (e.g. “Alert TG1”) such as a particular talkgroup of the radios137(and/or the radios153). The actions807further includes an action807for alerting a particular security team identified by the identifier Security Team 6 (e.g. “Alert Security Team 6”) which may be associated with a particular group of the radios137(and/or the radios153) and which may, or may not, be associated via a talkgroup.

However, the triggers806and actions807may include any suitable triggers and actions, which may be dragged and dropped, and the like, into the workspace802, and associated with each other to generate workflows.

For example, as also shown inFIG.9, the trigger “ALPR Delivery Truck”806may be added to the workspace802a second time from the selection panel801, as a trigger “ALPR Delivery Truck”905, and associated with a different action “Alert Security Team 6” 906 (e.g. added as an action807from the selection panel801) by dragging a line907between the two, thereby forming a workflow908. Such an example illustrates that a given trigger806may be used more than once to generate a workflow904,908, in association with different actions807. Similarly, a given action807may be used more than once in the workspace802to form workflows with different triggers806.

Similarly, as also shown inFIG.9, the trigger “Loitering NW Staircase”806may be added to the workspace802from the selection panel801, as a trigger “Loitering NW Staircase”909, and associated with action “Alert Security Team 6” 910 (e.g. added as an action807from the selection panel801) by dragging a line911between the two, thereby forming a workflow912. Such an example illustrates that a given action807may be used more than once to generate a workflow908,912, in association with different triggers806.

As illustrated inFIG.10, a single trigger may be associated with multiple actions in a workflow. Thus, in an illustrated workflow1000, a trigger1001of “ALPR Delivery Truck” may be associated with an action1003of “Unlock Back Door”1003as well as associated with an action1002of “Alert TG 1”. When the workflow1000is uploaded to the workflow server102, and the automatic license plate detects a delivery truck, workflow server102will cause both the back door to unlock and an alert to be sent on Talkgroup #1.

In a similar manner multiple triggers may be associated with a single action. Thus, in an illustrated workflow1004, both a trigger1005of “Elevated Body Temp SAM 12” and a trigger1006of “Loitering NW Staircase” will cause an action1007of “Notify Dispatch”1008. When the workflow1004is uploaded to the workflow server102, the workflow server102notifies the dispatch center when either a police officer (and the like) identified by the identifier “SAM 12” has an elevated body temperature (e.g. above a threshold body temperature”, or when loitering is detected in the NW staircase.

As mentioned above, it may be challenging to communicate to the one or more communication devices the sensor data that lead to the one or more triggers and/or to change and/or control the safety workflows.

In order to address such a problem, the workflow server102may be adapted to: monitor execution of a safety workflow, the safety workflow comprising one or more triggers and one or more responsive actions; provide, at a display screen, an indication of the safety workflow and respective visual indications of: a physical sensor that generated sensor data of a trigger of the safety workflow; and a communication device associated with a responsive action to the trigger; detect, via an input device, an interaction with one or more of the respective visual indications to interact with one or more of the physical sensor and the communication device; and based on the interaction, one or more of: retrieve the sensor data; initiate communication with the communication device; and send the sensor data to the communication device.

Hereafter, workflows may be interchangeably referred to as safety workflows as it is understood that workflows as described herein may be used to implement procedures and/or processes related to safety and/or public safety of persons and/or personnel, for example at a school, a hospital, an airport, a sporting event, a stadium, a factory, a warehouse and/or any other suitable location and/or building and the like. Hereafter, the workflow server102may be interchangeably referred to as a computing device (e.g. which may be implemented as one or more computing devices, one or more servers, one or more cloud computing devices, and the like). Hereafter, it is understood that any of the sensors138, cameras142, IoT devices163comprise physical sensors that may generate sensor data that may be provided to the workflow server102to determine whether a trigger has occurred.

Attention is next directed toFIG.11which depicts portions of an example of the system100, with cameras142-1,142-2, communication devices153-1,153-2, and an IoT device163deployed in a building1100. In particular,FIG.11depicts a top view of a cross-section of a floor of the building1100showing physical locations of the cameras142-1,142-2, the communication devices153-1,153-2, and the IoT device163.

In particular, a first camera142-1is positioned to acquire images of a first door1102(e.g. to a room number 4); for example, as depicted, the first door1102is in a field-of-view of the first camera142-1. Similarly, a second camera142-2is positioned to acquire images of the first door1102and a second door1104(e.g. to a room number 5); for example, as depicted, the doors1102,1104are both in a field-of-view of the second camera142-2. In particular, images from the cameras142-1,142-2may be used to determine whether a given door1102,1104is opened or closed, for example using a respective VAE143(not depicted) of the cameras142-1,142-2. Such images from the cameras142-1,142-2are understood to comprise sensor data, for example from physical image sensors of the cameras142-1,142-2.

Furthermore, the IoT device163may comprise an object that controls the second door1104to be opened or closed, and/or determine whether the second door1104is open or closed; hence, the IoT device163may comprise a physical sensor which may be used to determine whether the second door1104is opened or closed, for example using sensor data from the IoT device163.

While not depicted, the communication devices153-1,153-2are understood to be operated by respective security personnel, such as security guards deployed in the building1100, and the like. However, one or more of the communication devices153-1,153-2may be operated by other types of personnel, such as a janitor, and the like.

Also depicted inFIG.11are the workstation101, with the display screen705and the one or more input devices706(interchangeably referred to hereafter as the input device706and/or the input devices706), as well as the workflow server102, and the gateways141,151,162. Furthermore, communication links are shown between the cameras142and the gateway141, the communication devices153and the gateway151, and the IoT device163and the gateway162; such communication links are shown in the form of dashed double-ended arrows to better distinguish them from the walls and rooms of the building1100. While other components of the system100are not depicted, it is understood that any suitable components, as previously described, may be present. For example, while components of the public-safety network130are not depicted, they may nonetheless be present.

As depicted, it is understood that the workflow server102may be implementing and/or monitoring security workflows associated with the building1100. For example, as depicted, the cameras142-1,142-2, and the IoT device163for the second door1104, are transmitting respective sensor data1106-1,1106-2,1106-3(e.g. interchangeably referred to hereafter as the sensor data1106) to the workflow server102via respective gateways141,162. For example, the sensor data1106-1from the first camera142-1may comprise video and/or images that include the first door1102and/or an indication (e.g. generated via a respective VAE143) that the first door1102is open or closed). The sensor data1106-2from the second camera142-2may comprise video and/or images that include the doors1102,1104and/or respective indications (e.g. generated via a respective VAE143) that the first door1102is open or closed, or that the second door1104is open or closed. For simplicity, hereafter, reference may be made to video or images of the cameras142, but reference to “video” may be understood to include images, and similarly reference to “images” may be understood to include video.

The sensor data1106-3from the IoT device163may include an indication of whether the second door1104is open or closed. When the sensor data1106include indications as to whether the doors1102,1104are open or closed, such indications may be generated and transmitted (and/or only generated and transmitted) when a respective door1102,1104changes state from being open to being closed, or being closed to being opened; in other examples, such indications may be transmitted periodically. In examples where the sensor data1106-1,1106-2include video and/or images of the doors1102,1104, such images of the doors1102,1104may be streamed periodically and/or may comprise a live-stream, and/or such images of the doors1102,1104may be transmitted (and/or only transmitted) when a respective door1102,1104changes state from being open to being closed, or being closed to being opened.

Regardless, the workflow server102is understood to monitor workflows that may have been generated using the dashboard800and implement a workflow when the sensor data1106indicates that a respective trigger has occurred. Furthermore, the workflow server102may store the sensor data1106, for example at the storage component602, for example in association with respective times that the sensor data1106was generated and/or received. Indeed, in some examples, the sensor data1106may be time stamped, such that sensor data1106(e.g. such as video and/or images acquired by a camera142at a given time and/or within a given time period).

For example, attention is next directed toFIG.12which depicts a dashboard1200to monitor workflows; the dashboard1200may be similar to the dashboard800, but which has been adapted to include a selection panel1201and a workspace1202. The selection panel1201is generally for selecting indications of previously generated security workflows1204-1,1204-2, which may be referred to hereafter, respectively, as a first workflow1204-1and a second workflow1204, and/or interchangeably referred to, hereafter, collectively as the security workflows1204and/or, generically, as a security workflow1204. In particular, as depicted, the selection panel1201may specifically show active workflows1204, for example, workflows for which a trigger has occurred. For example, the first workflow1204-1may have been initiated when the first door1102to a room number 4 in the building1100was opened, and the second workflow1204-1may have been initiated when the second door1104to a room number 5 in the building1100was opened.

The workspace1202is generally to show indications of respective triggers and actions for the security workflows1204-1,1204-2. As such, the view of the dashboard1200depicted inFIG.11may be referred to as a workflow view and/or workflow mode of the dashboard1200.

Hereafter, while it is understood that workflows, triggers and actions are components that may be implemented at the workflow server102, and indications of workflows, triggers and actions depicted at the dashboard1200are visual indications of workflows, triggers and actions, for simplicity, hereafter, when discussing such indications with reference to the dashboard1200, reference will be made to respective workflows, triggers and actions rather than indications thereof.

Furthermore, the security workflows1204may have been generated using the dashboard800. In particular, the dashboards800,1200may be components of a dashboard application being implemented by the workflow server102and/or the workstation101, for example using Motorola Solution™'s Command Central™ software suite comprising the Orchestrate™ platform (e.g. at the workflow server102) and/or the Motorola Solution™'s Orchestrate™ and Ally™ dispatch and incident management software (e.g. at the workstation101). Indeed, the dashboard800may be to generate and edit workflows, while the dashboard1200may be to monitor and/or select workflows that have been provided to the workflow server102, for example to show status of respective triggers and actions, as well as to edit workflows and/or interact with sensors and/or communication devices associated with workflows as described hereafter.

Furthermore, while the dashboard1200shows only two workflows1204, any suitable number of workflows1204may be shown at the dashboard1200. Furthermore, as other workflows1204become active, such active workflows1204may appear, for selection, at the selection panel1201, and respective triggers and actions may appear at the workspace1202(e.g. as controlled by the workflow server102); similarly, as other workflows1204become inactive, such inactive workflows1204may disappear from the selection panel1201, and respective triggers and actions may disappear from the workspace1202(e.g. as controlled by the workflow server102).

As depicted at the selection panel1201, the first workflow1204-1has been selected for example using the input device706. To show selection of the first workflow1204-1, the first workflow1204-1is depicted in a heavier line than the second workflow1204-2. Similarly, to show selection of the first workflow1204-1, at the workspace1202, a trigger and actions of the first workflow1204-1are depicted in heavier line than a trigger and actions of the second workflow1204-2.

As depicted, the first workflow1204-1comprises a trigger1206of determining that the first door1102is open, specifically based on the sensor data1106-1from the first camera142-1.

The first workflow1204-1further comprises an action1208of alerting personnel (e.g. a security guard) associated with the first communication device153-1when the trigger1206occurs; such an action1208may include the workflow server102automatically transmitting a dispatch command to the first communication device153-1when the trigger1206occurs (e.g. using an automated voice command and/or message in any suitable format), to dispatch personnel (e.g. a security guard) associated with the first communication device153-1to the first door1102.

As depicted, the first workflow1204-1further comprises an action1210of alerting personnel (e.g. a security guard) associated with the second communication device153-2when the action1208fails to occur; the action1210may be similar to the action1208but a dispatch command may be transmitted to the second communication device153-2rather than the second communication device153-2. Indeed, the first workflow1204-1further illustrates that a workflow may include a plurality of actions which may be provided in a cascading manner, and the like, such that, when a first action fails to occur and/or fails to execute, a second action may occur; such a failure may occur when the first communication device153-1fails to acknowledge the dispatch command (and the like), within a given time period (e.g. 1 minute, 2 minutes, and/or any other suitable time period).

Such conditional actions may be incorporated into a workflow via the dashboard800adapted to include such conditional actions in the selection panel801and/or the workspace802may be adapted to include components (e.g. which may be accessed via menus, pointers (e.g. a mouse), and the like), for making an action conditional.

The first workflow1204-1, as depicted in the workspace1202, furthermore visually indicates that the action1210occurs in response to the action1208failing; for example a line from the action1208to the action1210is of a different format than a line from the trigger1206to the action1208(e.g. the line from the action1208to the action1210includes a solid circle indicating that the action1210is conditional on the action1208failing).

As will be explained in more detail, as depicted in the workspace1202, the trigger1206includes an electronic button1212which may be selected to view stored sensor data1106-1and/or live sensor data1106-1, add the trigger1206to another workflow, and the like. As depicted, the electronic button1212is in a shape of a camera to indicate that the electronic button1212is for initiating processes associated with the first camera142-1, as described hereafter.

For example, a menu1213associated with the electronic button1212is depicted, which may be provided at the display screen705when the electronic button1212is selected. The menu1213includes a list of selectable options which, when selected, may cause the workflow server102(and/or the workstation101) to perform a respective process. |For example, as depicted, the menu1213includes a selectable option to “View Saved Video”, which, when selected, may cause stored video (e.g. stored sensor data1106-1at the storage component602) from the first camera142-1to be provided at the display screen705that included an event that caused the trigger1206to occur (e.g. the first door1102being opened). Furthermore, as depicted, the menu1213includes a selectable option to “View Live Video”, which, when selected, may cause live video (e.g. sensor data1106-1currently being streamed) from the first camera142-1to be provided at the display screen705. Furthermore, as depicted, the menu1213includes a selectable option to “Add To Workflow”, which may enable the trigger1206to be added to another workflow, such as the second workflow1204-1, or another, non-active workflow; selection of “Add To Workflow” may cause the dashboard1200to be at least temporarily replaced with the dashboard800for editing workflows.

Similarly, the action1208includes an electronic button1214which may be selected to contact the first communication device153-1, transmit stored sensor data1106-1to the first communication device153-12(e.g. images showing the first door1102opened), transmit live sensor data1106-1to the first communication device153-12, add the action1208to another workflow, and the like.

For example, a menu1215associated with the electronic button1214is depicted, which may be provided at the display screen705when the electronic button1214is selected. The menu1215includes a list of selectable options which, when selected, may cause the workflow server102(and/or the workstation101) to perform a respective process. |For example, as depicted, the menu1215includes a selectable option “PTT” which, when selected, may cause a Push-To-Talk call to be initiated to the first communication device153-1for example from a further communication device associated with the user of the workstation101using, for example, the network interface701and any suitable combination of speakers and microphones at the workstation101(e.g. such as a headset worn by the user of the workstation101); indeed the network interface701may generally represent a communication device associated with the user of the workstation101. While such an example is described with respect to a PTT call, any suitable process for communicating with the first communication device153-1is within the scope of the present specification (e.g. a mobile and/or cellular phone call, and the like). As depicted, the menu1215includes a selectable option “TG1” which, when selected, may cause a group communications session to be initiated to a talkgroup “Talkgroup #1” of which the first communication device153-1may be a member, for example using a further communication device associated with the user of the workstation101such as the network interface701.

As depicted, the menu1215further includes a selectable option to “Share Saved Video”, which, when selected, may cause stored video (e.g. stored sensor data1106-1) from the first camera142-1that included an event that caused the trigger1206to occur (e.g. the first door1102being opened) to be transmitted to the first communication device153-1, for example by the workflow server102. Furthermore, as depicted, the menu1215includes a selectable option to “Share Live Video”, which, when selected, may cause live video (e.g. sensor data1106-1currently being streamed) from the first camera142-1to be streamed and/or transmitted to the first communication device153-1, for example by the workflow server102. Furthermore, as depicted, the menu1215includes a selectable option to “Add To Workflow”, which may enable the action1208to be added to another workflow, such as the second workflow1204-1, or another, non-active, workflow; selection of “Add To Workflow” may cause the dashboard1200to be at least temporarily replaced with the dashboard800for editing workflows.

As depicted, the action1208further includes a label “FAIL” which indicates that the action1208has failed; for example, the first communication device153-1may not have acknowledged the dispatch command, as described above, within a given time period. Such a label may further indicate that the action1210is being implemented in response to failure of the action1208.

Similarly, the action1210includes an electronic button1216which may be selected to contact the second communication device153-2, transmit stored sensor data1106-1to the second communication device153-2(e.g. images showing the first door1102opened), transmit live sensor data1106-1to the second communication device153-2, add the action1210to another workflow, such as the second workflow1204-1, and the like.

For example, a menu1217associated with the electronic button1216is depicted, which may be provided at the display screen705when the electronic button1216is selected. The menu1217includes a list of selectable options which, when selected, may cause the workflow server102(and/or the workstation101) to perform a respective process. The menu1217is understood to be substantially similar to the menu1215, however corresponding processes occur with respect to the second communication device153-2, rather than the first communication device153-1, or with respect to the action1210, rather than the action1208. Furthermore, from the menu1217, it is understood that the second communication device153-2is also a member of “Talkgroup #1”.

As depicted, the action1210further includes a label “Dispatched” which indicates that personnel associated with the second communication device153-2has been dispatched to the location of the first door1102. For example, the label “Dispatched” may be provided at the action1210in response to the second communication device153-2acknowledging a dispatch command (and the like), within a given time period.

The labels “Fail” and “Dispatched” of the actions1208,1210may be dynamic however, and may be updated (e.g. by the workflow server102) as status of the respective actions1208,1208. For example, the label “Dispatched” may have previously been “Waiting For Acknowledgement” and the like until the second communication device153-2acknowledged a dispatch command.

However, status of an action (and/or a trigger) may be visually provided in any suitable manner using, for example, different colors associated with different statuses and the like. For example, an action may be depicted as green when being implemented successfully, an action may be depicted as red when the action fails, or an action may be depicted as yellow when a status is being determined.

The second workflow1204-2may comprise a trigger1218of determining that the second door1104is open, specifically based on the sensor data1106-3from the IoT device163associated with the second door1104. The second workflow1204-2further comprises an action1220of alerting personnel (e.g. a security guard) associated with the second communication device153-2when the trigger1218occurs, similar as described with respect to the actions1208,1210.

The trigger1218includes an electronic button1222that may be similar to the electronic button1212, but in the shape of the IoT device163associated with the second door1104, and may be used to view stored the sensor data1106-3that caused the trigger1218to occur (e.g. which may textually indicate that the second door1104was opened or closed and optionally a time that the second door1104opened or closed), view live sensor data1106-3, and add the trigger1218to another workflow, such as the first workflow1204-1, and the like.

For example, a menu1223associated with the electronic button1222is depicted, which may be provided at the display screen705when the electronic button1222is selected. The menu1223includes a list of selectable options which, when selected, may cause the workflow server102(and/or the workstation101) to perform a respective process. The menu1223is understood to be substantially similar to the menu1213, however corresponding processes occur with respect to the sensor data1106-3(e.g. IoT sensor data) rather than video. For example, selectable options to “View Saved Sensor Data” and “View Live Sensor Data”, when selected, may respectively cause the workflow server102to provide stored sensor data1106-3and/or or live sensor data1106-3at the display screen705(e.g. textual indications of a stored or live status of whether the second door1104is opened or closed). When the stored sensor data1106-3, the stored sensor data1106-3may be particular to when the IoT device163detected that the second door1104was opened, and a time that the second door1104was opened may also be provided at the display screen705. Similarly, a selectable option “Add To Workflow” of the menu1223may be used to add the action1220to another workflow.

The action1220includes an electronic button1224that may be similar to the electronic button1216as described herein, but adapted for the second workflow1204-1. For example, the electronic button1224may be used to initiate a call with the second communication device153-2, and/or an associated talkgroup, transmit stored or live sensor data1106-3to the second communication device153-2, and add the action1220to another workflow.

For example, a menu1225associated with the electronic button1224is depicted, which may be provided at the display screen705when the electronic button1224is selected. The menu1217includes a list of selectable options which, when selected, may cause the workflow server102(and/or the workstation101) to perform a respective process. The menu1225is understood to be substantially similar to the menu1217, however corresponding processes occur with respect to the sensor data1106-3(e.g. IoT sensor data) rather than video, and with respect to the action1220rather than the action1210. For example, selectable options to “Share Saved Sensor Data” and “Share Live Sensor Data”, when selected, may respectively cause the workflow server102to transmit stored or live sensor data1106-3to the second communication device153-2. Similarly, a selectable option “Add To Workflow” may be used to add the action1220to another workflow.

As depicted, the second workflow1204-2further comprises a “human-in-the-loop” workflow component1226between the trigger1218and the action1220. Such a “human-in-the-loop” workflow component1226may be incorporated into a workflow via the dashboard800adapted to include such “human-in-the-loop” workflow components in the selection panel801. In particular, the “human-in-the-loop” workflow component1226comprises an action that occurs via a user of the workstation101, and the like, contacting a given person (e.g. a human), who may be identified and/or contacted via an electronic button1228which, when actuated, may initiate a phone call, and the like, with a phone associated with the given person and/or which may enable providing the phone number of the given person and/or may enable a given person to be selected from a contact list and initiation of phone call with a phone of the given person.

For example, a menu1229associated with the electronic button1228is depicted, which may be provided at the display screen705when the electronic button1228is selected. The menu1229includes a list of selectable options which, when selected, may cause the workflow server102(and/or the workstation101) to perform a respective process. For example, as depicted, the menu1229includes a selectable option “Bob Smith-212-555-1212”, which, when selected, causes a call to be initiated to “Bob Smith” at the phone number “212-555-1212”, from the workstation101(e.g. via the network interface701, and the like), so that the user of the workstation101may verbally instruct “Bob Smith” to verify the trigger1218. While this example is described with respect to a phone call, any other suitable type of communication for contacting a contact is within the scope of the present specification, including, but not limited to, an Internet Protocol (IP) based video call, texting, emails, messages, and the like.

In this example, it is understood that “Bob Smith” associated with the phone number “212-555-1212” is a default contact for the “human-in-the-loop” workflow component1226. However, as depicted, the menu1229further comprises a selectable option to “Select Contact” which, while not depicted, may cause a contact list to be provided at the display screen705from which another contact may be selected.

Furthermore, as depicted, the menu1229further comprises a selectable option to “Change Default Contact” which, while not depicted, may cause a contact list to be provided at the display screen705from which a different contact may be selected as a default contact; in such examples, the selectable option “Bob Smith-212-555-1212” at the menu1229may be replaced with contact information of the different contact that was selected as the default contact. Alternatively, the selectable option to “Change Default Contact” may enable a different phone number, and the like, for the current default contact to be provided via the input device706, and the like (e.g. a different phone number, email address, etc., for “Bob Smith”).

While not depicted, the menu1229may further include a field for receiving a phone number via the input device706which may be used to initiate a call, and the like, to a user to verify the trigger1218.

Regardless, the user of the workstation101may initiate a call and/or a communication session and/or a text session with a phone, and/or other communication device of the given person (e.g. using a telephone and/or other communication device, which may be separate from the workstation101and/or incorporated into the workstation101). On the call, and the like, the user of the workstation101may ask that the given person verify that the second door1104is open (e.g. and/or verify that any real world components associated with a given trigger are in a state indicated by the given trigger and/or verify that a given trigger has actually occurred). The given person may walk to the second door1104and visually verify that the second door1104is open; the given person may then tell the user of the workstation101(e.g. via a call, message, and the like) that the second door1104is open; the user of the workstation101may operate the input device706to actuate an electronic button1230associated with the “human-in-the-loop” workflow component1226, to initiate the action1220.

As depicted, the electronic button1230includes text “Verify” indicating a current status of the “human-in-the-loop” workflow component1226; specifically “Verify” generally indicates that the trigger1218has not yet been verified. However, when the electronic button1230is actuated, the text may change to “Verified” indicating that the trigger1218has been verified. Hence, as depicted, the text at the electronic button1230generally provides a status of the “human-in-the-loop” workflow component1226, however the status of the “human-in-the-loop” workflow component1226may be provided in any suitable manner, for example as an indicator separate from the electronic button1230.

Hence, the second workflow1204-2illustrates that a workflow as provided herein may include a “human-in-the-loop” workflow component, and that the dashboard800may be adapted accordingly.

In some examples, the depicted electronic buttons may only be selected for a selected active workflow. Hence, as depicted, as the first workflow1204-1is depicted as selected, the electronic buttons1212,1214,1216may be available for selection while the electronic buttons1222,1224,1228may not be available for selection. For example, while the electronic buttons1222,1224,1228may still be depicted when the associated second workflow1204-2is not selected, the electronic buttons1222,1224,1228may be grayed out and/or otherwise not actuatable (e.g. until the second workflow1204-2is selected). Such a scheme may prevent the electronic buttons1222,1224,1228from being accidently actuated when a workflow, other than the second workflow1204-2, is selected. However, in other examples, the electronic buttons1222,1224,1228may be actuatable regardless of which workflow1204is selected. Similar comments apply to the electronic buttons1212,1214,1216when a workflow1204, other than the first workflow1204-1, is selected. Regardless, a user may use the input device706to switch between the workflows1204via the selection panel1201.

As depicted, the dashboard1200further includes an electronic button1232which, when actuated, causes the dashboard1200to switch to a map (e.g. and/or floorplan) view and/or a map mode. AtFIG.12, the dashboard1200includes an electronic button1301, which, when actuated, causes the dashboard1200to switch back to the workflow view depicted inFIG.11.

For example, attention is next directed toFIG.13which depicts another aspect of the dashboard1200. In particular,FIG.13depicts the dashboard1200in a map view in which the workspace1202has been replaced with a map and/or floor plan-based workspace1302that shows one or more of a map1304and a floorplan of the building1100showing current locations of one or more physical sensors and one or more communication devices, for example associated with the active workflows1204.

In particular, similar toFIG.12, the first workflow1204-1is again shown as being selected.

For example, as depicted, the map1304shows icons at respective locations of the cameras142, the IoT device163associated with the second door1104in the building1100, and the communication devices153, as well as respective locations of the doors1102,1104.

While the example ofFIG.13shows the map1304as a floorplan of the building1100, in other examples the map1304may be for an outdoor location, depending, for example, on locations of locations of the cameras142, IoT devices163, communication devices137,153, sensors138, and the like.

While such icons (and the doors1102,1104) are indicated using reference numbers that are the same as the reference numbers of the cameras142, the IoT device163and the communication devices153(and the doors1102,1104), such similar numbering is used only for simplicity and it is understood that the cameras142, the IoT device163and the communication devices153are not physically part of the map1304. Furthermore, the icons for the cameras142also show orientation of the cameras142. For example, an icon for the first camera142-1comprises a picture of a camera with a lens thereof pointed at the first door1102; similarly, an icon for the second camera142-2comprises a picture of a camera with a lens thereof pointed at the first door1102and the second door1104.

The icon for the IoT device163is merely represented as a small box at the second door1104, but may have any suitable format and/or configuration.

As depicted, the icons for the cameras142comprise respective pictures of respective types of the communication devices153(e.g. as depicted, respective picture a radio and/or a two-way radio). It is understood that locations of the icons for the cameras142may change at the map1304as the communication devices153move in the building1100; as such, it is understood that the communication devices153may be reporting their respective locations (e.g. in the form of Global Positioning System (GPS) coordinates, and the like) to the workflow server102, which updates the dashboard1200accordingly, and/or the building1100may comprise location determining devices (e.g. such as the cameras142and/or other cameras and/or a beaconing system) that determine respective locations of the communication devices153and report such respective locations the workflow server102which updates the dashboard1200accordingly.

In some examples, only icons for a selected workflow1204may be depicted. However, as depicted, for the selected first workflow1204-1, indications of respective triggers and actions for the selected first workflow1204-1are depicted. For example, as depicted, the map1304further includes, at the icon for the first camera142-1, an indication1306indicating that the sensor data1106-1from the first camera142-1caused the trigger1206to occur; while the indication1306comprises text “Trigger”, the indication1306may include any suitable combination of text, graphics, colors and the like. Similarly, as depicted, the map1304further includes, at the icon for the first communication device153-1, an indication1308indicating that the action1208failed; while the indication1308comprises text “Fail”, the indication1308may include any suitable combination of text, graphics, colors, and the like indicating a status of the action1208. Similarly, as depicted, the map1304further includes, at the icon for the second communication device153-2, an indication1310indicating that the action1210is occurring in association with the second communication device153-2, for example indicating that the second communication device153-2has been dispatched; while the indication1310comprises text “Dispatched”, the indication1310may include any suitable combination of text, graphics, colors and the like indicating a status of the action1210. The indications1308,1310,1306may be dynamic and may be updated (e.g. by the workflow server102) as status of associated triggers and actions change.

As depicted, the map1304further shows an indication1312at a location of an event that may have caused the trigger1206of the selected first workflow1204-1to occur. For example, as depicted, the indication1312is located adjacent the first door1102and comprises text “Trigger Location”, though the indication1312may include any suitable combination of text, graphics, and the like. Furthermore, the workflow server102may determine the location of an event that may have caused the trigger1206of the selected first workflow1204-1using a VAE143at the workflow server102and/or a VAE143of one or more of the cameras142-1,142-2and/or any camera142may have the first door1102in a respective field-of-view.

In some examples, the icons for the cameras142, the IoT device163associated with the second door1104in the building1100, and the communication devices153may comprise electronic buttons similar to corresponding electronic buttons1212,1214,1216,1222,1224with similar functionality provided when actuated, for example with respective menus, similar to the menus shown inFIG.11, being provided when actuated. For example, the icons for the cameras142-1,142-2may comprise electronic buttons respectively similar to the electronic button1212which, when actuated, may cause respective menus to be provided similar to the menu1213(e.g. with a menu for the second camera142-2providing selectable options to access stored or live the sensor data1106-2and add another trigger to a workflow1204, for example based on the sensor data1106-2from the second camera142-2, and the like). Similarly, the icons for the communication devices153-1,153-2may be respectively similar to the electronic buttons1214,1216.

In particular, as a camera142, an IoT device163and/or a communication device153may be associated with more than one workflow1204(and/or an inactive workflow), it is understood that menus provided when a respective electronic button is actuated may be for a selected workflow1204. Hence, as the first workflow1204-1is selected, the menus provided when a respective electronic button is actuated may be for the first workflow1204-1.

However, in some examples, a camera142, an IoT device163and/or a communication device153depicted at the map1304may not be associated with a workflow. For example, as described herein, the second camera142-2is not associated with a workflow; as such, when an icon for the second camera142-2is actuated, the corresponding menu1314is adapted accordingly. For example, as depicted, the menu1314includes a selectable option to “View Saved Video”, which, when selected, may cause another menu to be provided to select a time period for which stored sensor data1106-2from the second camera142-2is to be provided at the display screen705. For example, a user of the workstation101may select the selectable option to “View Saved Video” to review video of the first door1102in a time period in which the first door1102was detected to have been opened using the sensor data1106-1for the first camera142-1. As depicted, the menu1314includes a selectable option to “View Live Video”, which, when selected, may cause live sensor data1106-2from the second camera142-2to be provided at the display screen705.

As depicted, the menu1314includes a selectable option to “Send Saved/Live Video”, which, when selected, may cause another menu to be provided to select a time period for which stored sensor data1106-2from the second camera142-2is to be transmitted to a communication device153, which may also be selected from such an another menu; such an another menu may also enable selection of a communication device153to which live video from the second camera142-2is transmitted.

As depicted, the menu1314includes a selectable option to “Add To Workflow”, which, when selected, may cause another dashboard to be provided, such as the dashboard800. for example to cause a trigger associated with the second camera142-2to be added to a workflow which may include, but is not limited to, a selected workflow1204, such as the first workflow1204-1, or another workflow. For example, a trigger similar to the trigger1206may be added to the first workflow1204-1such that, when sensor data1106-1from the second camera142-2indicates that the first door1102is opened, the action1208, and/or the action1210, occurs. Such a trigger may have been prepopulated at the dashboard800, for example as a trigger806, or such a trigger may be generated using any suitable process (e.g. a CNN of a VAE143associated with the second camera142-2may be configured to detect when the first door1102is opened or closed; in some examples such a configuration may occur based on CNN layers of a CNN of a VAE143associated with the first camera142-1).

Attention is now directed toFIG.14, which depicts a flowchart representative of a method1400for communicating with communication devices based on workflow interactions. The operations of the method1400ofFIG.14correspond to machine readable instructions that are executed by the workflow server102, and specifically the processor603. In the illustrated example, the instructions are represented by the blocks ofFIG.14and may be stored at the storage component602. The method1400ofFIG.14is one way that the processor603and/or the workflow server102and/or the system100may be configured. Furthermore, the following discussion of the method1400ofFIG.14will lead to a further understanding of the system100, and its various components.

The method1400ofFIG.14need not be performed in the exact sequence as shown and likewise various blocks may be performed in parallel rather than in sequence. Accordingly, the elements of method1400are referred to herein as “blocks” rather than “steps.” The method1400ofFIG.14may be implemented on variations of the system100ofFIG.1, as well.

Furthermore, some aspects of the method1400may correspond to machine readable instructions that are executed by the workstation101, and specifically the processor703, for example in conjunction with the workflow server102. For example, in the description of the method1400, reference will be made to providing certain components at the display screen705; while the workstation101may control the display screen705to render such components, the workflow server102may provide such components to the workstation101to cause the workflow server102to render such components. Hence, the workflow server102may provide such components via the display screen705of the workstation101, though the workflow server102may provide such components remotely from the display screen705.

At a block1402, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) monitors execution of a safety workflow1204, the safety workflow1204comprising one or more triggers and one or more responsive actions, as described above.

In particular, the one or more triggers may be based on respective sensor data from one or more physical sensors, such as the sensors138, the cameras142, the IoT devices163, and the like, and the one or more responsive actions may be implemented via one or more communication devices, such as the communication devices137,153.

For example, hereafter the method1400will be described with reference to monitoring the first workflow1204-1, though, at the block1402, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) may monitor any suitable number of workflows1204.

Hence, using the first workflow1204-1, the trigger1206and the actions1208,1210as an example, at a block1404, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) provides, at the display screen705, an indication of the safety workflow1204-1(e.g. a selected workflow) and respective visual indications of: a physical sensor (e.g. the first camera142-1) that generated sensor data (e.g. the sensor data1106-1) of a trigger1206of the safety workflow1204-1; and a communication device153-1,153-2associated with a responsive action1208,1210to the trigger1206.

In some examples, the indication of the safety workflow1204-1of the block1404may comprise a visual representation of the safety workflow1204-1itself, for example as depicted inFIG.12. In these examples, the respective visual indications (e.g. of a physical sensor that generated sensor data of the trigger1206of the safety workflow1204-1and a communication device153-1,153-2associated with a responsive action1208,1210to the trigger1206) may be provided on the visual representation of the safety workflow1204-1itself. For example, again with reference toFIG.12, the respective visual indication of the physical sensor that generated sensor data of the trigger1206of the safety workflow1204-1may comprise the electronic button1212which, as depicted, is in the form of an icon of a camera, and which, when actuated, may enable processes associated with the first camera142-1via the menu1213.

Similarly, again with reference toFIG.12, the respective visual indication of a communication device153-1,153-2associated with a responsive action1208,1210to the trigger1206may comprise the electronic buttons1214,1216which, as depicted, are in the form of icons representing respective types of the communication devices153-1,153-2, and which, when respectively actuated, may enable processes respectively associated with the communication devices153-1,153-2, for example via the menus1215,1217.

In other examples, the indication of the safety workflow1204-1may comprise one or more of the map1304and a floorplan showing current locations of the one or more physical sensors (e.g. the cameras142-1,142-2and the IoT device163associated with the second door1104) and the one or more communication devices153-1, and the respective visual indications may be located at one or more of the map1304and the floorplan and show respective current locations of the physical sensor and the communication device(s) associated with the safety workflow1204-1. Hence, in some examples, with reference toFIG.13, the respective visual indications of a physical sensor and a communication device153of the block1404may comprise the map1304in combination with the indications1306,1308,1310, and in further combination with respective icons for the first camera142-1and the communication devices153-1,153-2, as well as respective menus (e.g. similar to the menus1213,1215,1217, the menu1314, and the like).

At a block1406, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) detects, via the input device706, an interaction with one or more of the respective visual indications to interact with one or more of the physical sensor (e.g. the first camera142-1) and the communication device (e.g. one or more of the communication devices153-1,153-2).

For example, at the example ofFIG.12, the electronic buttons1212,1214,1216may be actuated to cause a respective menu1213,1215,1217to be provided at the display screen705from which certain processes may be selected for implementation, as previously described. Alternatively, at the example ofFIG.13, electronic buttons of the various icons depicted may be actuated to cause a respective menu to be provided at the display screen705from which certain processes may be selected for implementation, as previously described.

Based on the interaction of the block1406, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device), may, at a block1408, retrieve (e.g., via the network interface601) the sensor data1106-1(e.g. that cause the trigger1206to occur). For example, the interaction of the block1406may comprise selecting the selectable option “View Saved Video”, and/or the selectable option “View Live Video” of the menu1213to retrieve the sensor data1106-1, or receive live sensor data1106-1. In particular, when the selectable option “View Saved Video” is selected, video and/or images of the sensor data1106-1may be retrieved from the storage component602and may be provided at the display screen705, for example in a window at, and/or on, the dashboard1200.

Alternatively, and/or in addition based on the interaction of the block1406, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device), may, at a block1410, initiate (e.g., via the network interface601) communication with a communication device153-1,153-2of one of the actions1208,1210. For example, the interaction of the block1406may comprise selecting the selectable option “PTT” of the menu1215, or the menu1217″ to initiate a call with a respective communication device153-1,153-2.

In some examples, a communication device153with which communications may be initiated at the block1410, may be one of a group of associated communications devices153; for example, the communication devices153-1,153-2may be members of a talkgroup. In these examples, the method1400may further comprise initiating a communications session between the group of associated communications devices153and a further communication device associated with a user associated with the computing device, for example, the user of the workstation101.

Alternatively, and/or in addition based on the interaction of the block1406, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device), may, at a block412, send (e.g., via the network interface601) the sensor data1106-1to a communication device153-1,153-2of one of the actions1208,1210. For example, the interaction of the block1406may comprise selecting the electronic button1214or the electronic button1216, to sending the sensor data1106-1to a respective communication device153-1,153-2. For example, the interaction of the block1406may comprise selecting the selectable option “TG1” of the menu1215, or the menu1217″ to initiate a call with a respective talkgroup which may include one or more of the communication devices153-1,153-2.

Alternatively, and/or in addition based on the interaction of the block1406, the processor603and/or the workflow server102(e.g. and/or any other suitable computing device), may, at a block1412, send sensor data1106to a communication device153-1,153-2of one of the actions1208,1210. For example, the interaction of the block1406may comprise selecting the selectable option “Share Saved Video” and or selecting the selectable option “Share Live Video” of the menu1215, or the menu1217″ to respectively transmit stored sensor data1106-1or live sensor data sensor data1106-1to a respective communication device153-1,153-2.

Hence, it is understood that the method200may comprise the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) based on the interaction of the block1406, one or more of (e.g. in any suitable combination): retrieving sensor data1106; initiating communication with a communication device153; and sending the sensor data1106to the communication device153.

The method1400may include any other suitable features.

For example, the method1400may further comprise the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) detecting, via the input device706, a selection of a further safety workflow; and updating the display screen705to show a respective indication of the further safety workflow and respective further visual indications of a further physical sensor and a further communication device153associated with a respective trigger and a respective action of the further safety workflow.

For example, with reference toFIG.12, when the second safety workflow1204-2is selected at the selection panel1201, the associated trigger1218, action1220and “human-in-the-loop” workflow component1226may be highlighted, with associated visual indications of the IoT device163and the second communication device153-2in the form of the electronic buttons1222,1224being made available for selection.

Similarly, with reference toFIG.13, when the second safety workflow1204-2is selected at the selection panel1201, indications similar to the indications1306,1310,1312may be respectively located at icons for the IoT device163, the second communication device153-2and at a location of the second door1104. When the “human-in-the-loop” workflow component1226has not yet been used to verify the trigger1218, an indication at the second communication device153-2may indicate “Waiting For Verification Before Dispatching” and the like, and change to “Dispatched” once the “human-in-the-loop” workflow component1226has been used to verify the trigger1218, and/or be visually changed in any suitable manner (e.g. using different colors for different statuses).

The method1400may further comprise the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) providing, at the display screen,705a respective indication of a further sensor, not currently involved in the execution of the safety workflow1204-1; detecting, via the input device706, an input to add a further trigger to the safety workflow1204-1based on the further sensor; and responsive to detecting the input, modifying the safety workflow1204-1to include the further trigger for future executions of the safety workflow1204-1.

For example, as described above with respect toFIG.13, it is understood that the second camera142-2is not currently involved in the execution of the safety workflow1204-1. However, the selectable option “Add To Workflow” of the menu1314may be used to add a trigger associated with the second camera142-2to the first workflow1204-1(e.g. such that the action1208and/or the action1210occurs when the sensor data1106-2is used to detect that the first door1102is open).

The method1400may further comprise the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) providing, at the display screen705, a respective indication of a further communication device, not currently involved in the execution of a safety workflow1204; detecting, via the input device706, an input to add a further responsive action to the safety workflow1204based on the further communication device; and responsive to detecting the input, modifying the safety workflow1204to include the further responsive action for future executions of the safety workflow1204.

For example, as described above with respect toFIG.12, it is understood that the first communication device153-1is not currently involved in the execution of the safety workflow1204-1. However, the selectable option “Add To Workflow” of the menu1215may be used to add an action (e.g. similar to the action1208) associated with the first communication device153-1to the second workflow1204-2.

Furthermore, as has already been described, the selectable options “Add To Workflow” at the menus1215,1217,1225, and the like, may be used to add an action associated with a respective communication device153to a safety workflow. While the examples provided herein have been described with respect to only two communication devices153, both of which are components of the safety workflow1204-1, when electronic buttons for other communication devices137,153are in the building1100, and/or shown on the map1304(e.g. in the form of icons), such electronic buttons, when selected, may cause a menu similar to the menus1215,1217,1225to be provided, but with a selectable option of “Add To Workflow” included that enables adding an action for a corresponding communication device137,153to a workflow, similar to as described with respect to the selectable option “Add To Workflow” of the menu1314.

The method1400may further comprise the processor603and/or the workflow server102(e.g. and/or any other suitable computing device) providing, at the display screen705, a further respective visual indications of: a “human-in-the-loop” workflow component1226of a safety workflow1204; and a current status of the “human-in-the-loop” workflow component1226; providing, at the display screen705, options for modifying parameters of the “human-in-the-loop” workflow component1226including one or more of: an identity of a person to be contacted to verify the trigger; and contact information for contacting the person; and responsive to receiving, via the input device706, a modification to the parameters, modifying the safety workflow1204to include modified parameters of the “human-in-the-loop” workflow component1226for future executions of the safety workflow1204.

For example, with reference toFIG.12, the workspace1202generally provides a visual indication of the “human-in-the-loop” workflow component1226and a current status of the “human-in-the-loop” workflow component1226in the form of the text at the electronic button1230.

Furthermore, the menu1229generally provides selectable options for modifying parameters of the “human-in-the-loop” workflow component1226including modifying the identity of a person to be contacted to verify the trigger1218; and contact information for contacting the person. For example, the selectable options “Select Contact” and/or “Change Default Contact” may be used to change the person to be contacted to verify the trigger1218and/or an associated phone number, and the like.

Attention is next directed toFIG.15which depicts processes that may occur in the system100when the selectable option of “Share Saved Video” and/or the selectable option of “Share Live Video” are selected from the menu1217.FIG.15is substantially similar toFIG.11with like components having like numbers.

In particular, as depicted, when the selectable option of “Share Saved Video” and/or the selectable option of “Share Live Video” are selected from the menu1217, the sensor data1106-1from the first camera142-1may be retrieved from the storage component602and transmitted to the second communication device153-2and/or live sensor data1106-1from the first camera142-1may be transmitted to the second communication device153-2. Regardless,FIG.15provides an example of at least the blocks1408,1412of the method1400.

Attention is next directed toFIG.16which depicts processes that may occur in the system100when the selectable option of “PTT” is selected from the menu1217.FIG.16is substantially similar toFIG.11with like components having like numbers.

In particular, as depicted, when the selectable option of “PTT” is selected from the menu1217, the workflow server102initiates a call1600between the workstation101and the second communication device153-2, as represented in FIG.16by way of double-ended arrows indicating communication links between the workstation101, the workflow server102, the gateway151and the second communication device153-2being heavier than double-ended arrows of other communication links. Regardless,FIG.16provides an example of at least the block1408,1410of the method1400.

As should be apparent from this detailed description above, the operations and functions of electronic computing devices described herein are sufficiently complex as to require their implementation on a computer system, and cannot be performed, as a practical matter, in the human mind. Electronic computing devices such as set forth herein are understood as requiring and providing speed and accuracy and complexity management that are not obtainable by human mental steps, in addition to the inherently digital nature of such operations (e.g., a human mind cannot interface directly with RAM or other digital storage, cannot transmit or receive electronic messages, implement electronic workflows, and the like).