The present disclosure relates generally to security systems. The present disclosure relates more particularly to user interface notifications associated with security systems.
A security operator may operate a system to manage a number of secure locations. The system may include a large number of secure locations. Each of the number of secure locations may have a different response procedure in the event of a security alarm. As the number of secure locations increases, detecting security alarms and managing a variety of response procedures becomes difficult.
A security notification is one method to standardize a number of response procedures across secure locations. However, a security notification is traditionally generic across different types of security alarms and lacks contextualized information regarding the alarm.
One implementation of the present disclosure is a method for a person of interest (POI) monitoring system including generating a POI data structure, wherein the POI data structure includes an identifier of an individual to be monitored as a POI, causing the POI data structure to include an indication of one or more recipients to be notified upon detection of the individual, receive, from a security device, security data that describes an interaction of the individual with the security device, the security data including the identifier of the individual, determining whether the received identifier matches the identifier of the POI data structure, and causing one or more user devices associated with the one or more recipients to display a GUI notification in response to the received identifier matching the identifier of the POI data structure.
In some embodiments, generating the POI data structure further includes receiving, from a setup device, the POI data structure, generating a POI identifier for the POI data structure, receiving, from the setup device, POI information, POI tags, and POI restrictions, and storing the POI data structure with the POI identifier, the POI information, the POI tags, and the POI restrictions. In some embodiments, determining whether the received identifier matches the identifier of the POI data structure further includes receiving, from the security device, a location and an identifier associated with a monitored individual, searching a number of POI data structures with the identifier of the monitored individual, verifying, based on the search, whether the monitored individual is a POI, and determining, based on the location associated with the monitored individual, whether a POI alarm exists. In some embodiments, each of the number of POI data structures further includes one or more restricted areas and wherein the location is associated with the one or more restricted areas. In some embodiments, the security data further includes facial recognition data. In some embodiments, the security data further includes license plate recognition data. In some embodiments, the GUI notification is an email message. In some embodiments, the GUI notification is an alarm in an alarm interface. In some embodiments, the POI data structure further includes a response procedure describing one or more actions for the one or more recipients to take upon receiving the GUI notification. In some embodiments, the security device is an access control device, and wherein the interaction of the individual with the security device includes the individual presenting an identifier (ID) card to the access control device.
A person of interest (POI) monitoring system including a POI database storing a number of POI identifiers, each associated with an individual, wherein each of the POI identifiers is associated with one or more recipients to be notified upon detection of the individual, a processing circuit having at least one processor and memory, the memory storing instructions thereon, that when executed by the at least one processor, cause the processing circuit to receive, from a security device, security data that describes an interaction of a monitored person with the security device, the security data including an identifier associated with the monitored person, determine whether the received identifier matches any of the number of POI identifiers, and in response to determining a match, cause one or more user devices associated with the one or more recipients associated with the matching POI identifier to display a GUI notification.
In some embodiments, the POI database is configured to receive, from a setup device, a POI data structure, generate, a new POI identifier for the POI data structure, receive, from the setup device, POI information, POI tags, and POI restrictions, and store the POI data structure with the POI identifier, POI information, POI tags, and POI restrictions. In some embodiments, the memory further having instructions stored thereon, that when executed by the at least one processor cause, the processing circuit to receive, from the security device, a location associated with the monitored person, and verify, based on the location, that a POI alarm exists. In some embodiments, each of the POI identifiers in the POI database are further associated with one or more restricted areas, and wherein the location is associated with the one or more restricted areas. In some embodiments, the security data further includes facial recognition data. In some embodiments, the security data further includes license plate recognition data. In some embodiments, the GUI notification is an email message. In some embodiments, the GUI notification is an alarm in an alarm interface. In some embodiments, each of the number of POI identifiers in the POI database are further associated with a response procedure describing one or more actions for the one or more recipients to take upon receiving the GUI notification. In some embodiments, the security device is an access control device, and wherein the interaction of the monitored person with the security device includes the monitored person presenting an identifier (ID) card to the access control device.
Various objects, aspects, features, and advantages of the disclosure will become more apparent and better understood by referring to the detailed description taken in conjunction with the accompanying drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.
Referring generally to the FIGURES, systems and methods for notifying an individual regarding a person of interest alarm (POI) via a graphical user interface (GUI) notification is shown, according to various exemplary embodiments. Security operators using large security monitoring systems handle numerous alarms and alerts on a daily basis. Effectively sorting and responding to alarms and alerts requires human investigation and decision making. Systems that monitor numerous buildings, sites, or locations, either on-location or remotely, present challenges for a security operator. In larger systems, numerous different alarms and security events occur, generating high volumes of data, which are difficult for operators to process effectively. Tools that allow security operators to focus on the most relevant information about alarms allow for a faster response time. The expression ‘person of interest’ (POI) is commonly used to describe an individual whose presence in a monitored area is significant for security reasons. This could be because the person presents a heightened security risk or because the person is a senior or important individual within an organization. An individual can be manually added to a POI list or automatically added to a POI list, for example, based on analysis of anomalous activities. Efficiently identifying the presence of persons of interest will allow security operators to take earlier appropriate actions.
The POI GUI notification can be in the form of an email communication informing one or more notifiable individuals of a POI alarm occurring within the monitored area. The notification provides the notifiable individual with detailed, contextual information about the POI, the activity detected, the threat posed (if any), and other relevant information. Only the most relevant information can be presented to the notifiable person and any empty data fields can be omitted from the interface. This simplifies the way information is presented, making it easier for users to focus on the most important information. The interface may provide a means for the notifiable person to view the person of interest alarm details for further insight or action. The POI GUI notification described herein can be used as part of a security monitoring system, providing detailed and relevant information, together with a direct means of accessing the alarm for further action. The POI GUI notification described herein may improve upon currently available technology by storing POI information, detecting a POI from security data received from security components, generating a POI email including a POI identity, a detected activity associated with the POI, a threat posed, and specific response actions, and notifying a relevant individual with the POI email. The system described herein can store POI descriptive information, vehicle information, contact information, and historical record information in a data structure. Additionally or alternatively, the system described herein may integrate with existing security databases. For example, the system described herein may import an existing POI database, and flag POI's and generate POI notification based on the POI database. Furthermore, the system described herein may format POI notifications to integrate with existing alarm interfaces. For example, the system described herein may surface POI notifications in an existing alarm interface. Detection of a POI may be accomplished by matching security data received from security components to the information stored in the data structure. Response procedures may be tailored to the type of security alarm by storing a number of rules in the system described herein. The rules may specify different POI email recipients and POI email contents based on the location, type of alarm, and POI identity.
Building with Security System
Referring now to
Both the building 100 and the parking lot 110 are at least partially in the field of view of the security camera 102. In some embodiments, a multiple security camera 102 may be used to capture the entire building 100 and parking lot 110 not in (or in to create multiple angles of overlapping or the same field of view) the field of view of a single security camera 102. The parking lot 110 may be used by one or more vehicles 104 where the vehicles 104 may be either stationary or moving (e.g. delivery vehicles). The building 100 and parking lot 110 may be further used by one or more pedestrians 106 who can traverse the parking lot 110 and/or enter and/or exit the building 100. The building 100 may be further surrounded by a sidewalk 108 to facilitate the foot traffic of one or more pedestrians 106, facilitate deliveries, etc. In some embodiments, the building 100 may be one of many buildings belonging to a single industrial park or commercial park having a common parking lot and security camera 102. In another embodiment, the building 100 may be a residential building or multiple residential buildings that share a common roadway or parking lot.
In some embodiments, the security camera 102 is installed for purposes of monitoring a parking lot 110 and/or sidewalk 108 for accumulated snow. For example, the security camera may be configured to communicate with an image analysis device (e.g., convolutional neural network) to determine if the parking lot 110 or sidewalk 108 are covered with snow and accordingly require snow removal services. In such embodiments, vehicles 104 and/or pedestrians 106 could partially occlude the parking lot 110 or sidewalk 108. When the parking lot 110 and sidewalk 108 are partially occluded, it is possible that an image analysis system could inaccurately classify the parking lot 110 or sidewalk 108 as being covered in snow.
In some embodiments, the security camera 102 is configured to use an image analysis system to observe the parking lot 110 for the purpose of determining how many parking spaces are open and/or occupied. In some embodiments, the security camera 102 could be configured to observe the entrance(s) and/or exit(s) of building 100 for the purposes of counting the number of pedestrians 106 enter or exit the building. In this embodiment, for example, vehicles 104 might partially occlude the entrance(s) and/or exit(s) of the building 100.
Referring now to
The security monitoring system 200 is shown to include a POI system 210 and a first security component 260. The POI system 210 includes a processing circuit 220. Processing circuit 220 includes processor 230 and memory 240. The processor 230 can be a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components. Processor 230 can include a memory 240.
The memory 240 can include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memory 240 can include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The memory 240 can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. The memory 240 can be communicably connected to the processor 230 via the processing circuit 220 and can include computer code for executing (e.g., by the processor 230) one or more processes described herein.
The memory 240 is shown to include an identifier module, shown as identifier 246, and a reporter module, shown as reporter 248. The identifier 246 can be configured to identify a POI alarm given security data from one or more security components 260, as described in greater detail with further reference to
The memory 240 is shown to include an interface manager 244. The interface manager 244 can connect the POI system 210 to the plurality of security components 260 and receives security data therefrom. In some embodiments, interface manager 244 is part of other components (e.g., processor 230, POI system 210, etc.), or can be a separate entity entirely. In some embodiments, interface manager 244 can be a hardware component (e.g., router, controller, network switch, gateway, bridge, etc.), while in some embodiments, interface manager 244 can be a software component (e.g., database handler, object code, script, etc.). Interface manager 244 can be communicably connected to the plurality of security components 260 through the POI system 210, according to the exemplary embodiment. In some embodiments, interface manager 244 can be communicably connected to the reporter 248 through the processing circuit 220.
The memory 240 is shown to include a presenter module, shown as presenter 242.
Presenter 242 can send a POI GUI notification from the reporter 248 to the one or more client devices 280. According to the exemplary embodiment, the POI GUI notification can take the form of an email. However, in some embodiments, the POI GUI notification can take other forms (e.g., push notification, SMS text message, pager alert, instant message, phone call, etc.). In some embodiments, the POI GUI notification may take the form of an alarm in an alarm interface. For example, the POI GUI notification may be an alarm added to the alarm queue of a security system or BMS. Presenter 242 can be connected to client device 280 and processor 230, according to the exemplary embodiment. In some embodiments, presenter 242 can be part of other components (e.g., processor 230, POI system 210, etc.), or can be a separate entity entirely.
The memory 240 is shown to include a POI database module, shown as POI database manager 250. POI database manager 250 can maintain data relevant to operation of the POI system 210. POI database manager 250 can include one or more POI datablock(s) 252, response procedure data 256, and recipient data 258. In some embodiments, POI database manager 250 can be a hardware component (e.g., server, load balancing system, etc.), while in some embodiments, POI database manager 250 can be a software component (e.g., database management system, application programming interface, content management system, etc.). POI database manager 250 can be communicably connected to processor 230, according to the exemplary embodiment. However, in some embodiments, POI database manger 250 can be part of other components (e.g., processor 230, POI system 210, etc.), or can be a separate entity entirely.
In some embodiments, the one or more POI datablock(s) 252 can be identified through a unique POI identifier. Each of the one or more POI datablock(s) 252 can correspond to an individual POI. POI datablock(s) 252 may contain information relevant to an individual POI (e.g., name, alias, profile picture, badge number, category of threat, contact information, position, employee type, assignment, sex, race, age, height, weight, eye color, hair color, facial features, traits, tattoos, vehicle information, restriction information, etc.). The one or more POI datablock(s) 252 are shown to include POI info, shown as info 253, POI tags, shown as tags 254, and/or POI restrictions, shown as restrictions 255, according to the exemplary embodiment. Info 253 can include POI specific information as described above for POI datablock 252. Tags 254 can include brief descriptive categories of individual POI threats (e.g., threat of violence, etc.). Restrictions 255 can include POI specific rules used to determine the presence of a POI alarm given the POI (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.).
The response procedure data 256 may contain information relating to the required response protocol for a POI alarm (e.g., receptionist required actions, security personnel required actions, outside security calls to police, fire, ambulance, etc.) to be included in the POI GUI notification. The response procedure data 256 may contain steps, actions, or instructions individualized to the specific POI alarm. In some embodiments, the response procedure data 256 may contain embedded scripts to trigger further action. According to the exemplary embodiment, response procedure data 256 can be individualized and/or associable with specific security monitored locations (e.g., buildings, parking lots, campuses, cities, rooms, etc.), individual POI's (e.g., terminated employee, high-profile individual, violent individual, etc.), POI tags (e.g., threat of violence, etc.), and/or POI alarms (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.). By way of example, a first POI alarm for the presence of a terminated employee may be associated with a first response procedure (e.g., monitor individual, etc.), while a second POI alarm for a terminated employee with an associated tag ‘threat of violence’ may be associated with a second response (e.g., alert the police, etc.).
The recipient data 258 may contain information relating to the one or more recipient(s) of the POI GUI notification. Recipient data 258 can include email addresses, phone numbers, messenger contacts, pager numbers, IP addresses, and/or other contact information not listed herein. Recipient data 258 can include information relating to the recipient (e.g., name of recipient, position, alternate contacts, etc.). In some embodiments, recipient data 258 may be individualized and/or associable with specific security monitored locations (e.g., buildings, parking lots, campuses, cities, rooms, etc.), individual POI'S (e.g., terminated employee, high-profile individual, violent individual, etc.), POI tags (e.g., threat of violence, etc.), and/or POI alarms (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.). By way of example, a first POI alarm for the presence of a terminated employee may be associated with a first recipient (e.g., a human resources manager, etc.), while a second POI alarm for a terminated employee with an associated tag ‘threat of violence’ may be associated with a second recipient (e.g., a security officer, etc.).
The one or more security component 260 can be configured to provide security data to the POI system 210. The one or more security component 260 can be a physical hardware element (e.g., ingress card reader, security camera, access controller, retina scanner, fingerprint reader, etc.) and/or a non-physical element (e.g., biometric analysis, social media analysis, facial-recognition, license plate analyzer, etc.). According to the exemplary embodiment, the one or more security component 260 can be communicably coupled to the POI system 210 through the interface manager 244.
The setup device 270 can be configured to send one or more POI datablock(s) 252 and/or POI data (e.g., info 253, tags 254, restrictions 255, etc.) to the security monitoring system 200 in order to set up the POI GUI notifications. In some embodiments, setup device 270 may be a computer. However, in some embodiments, setup device 270 can take other forms (e.g., a tablet, phone, controller, script, program, etc.). Additionally, in some embodiments, setup device 270 can be part of security monitoring system 200. According to the exemplary embodiment, setup device 270 can be connected to security monitoring system 200.
The client device 280 may receive POI GUI notifications from the POI system 210. According to the exemplary embodiment, client device 280 may take the form of an email client. However, in some embodiments, client device 280 can take other forms (e.g., pager, cell phone, controller, switchboard, building management system, script, program, computer, server, etc.). According to the exemplary embodiment, client device 280 may contain user interface 282. The user interface 282 can be a touchscreen or other type of electronic display configured to present information to a user in a visual format (e.g., as text, graphics, etc.) and receive input from a user (e.g., via a touch-sensitive panel). For example, the user interface 282 may include a touch-sensitive panel layered on top of an electronic visual display. A user can provide inputs through simple or multi-touch gestures by touching the user interface 282 with one or more fingers and/or with a stylus or pen. The user interface 282 can use any of a variety of touch-sensing technologies to receive user inputs, such as capacitive sensing (e.g., surface capacitance, projected capacitance, mutual capacitance, self-capacitance, etc.), resistive sensing, surface acoustic wave, infrared grid, infrared acrylic projection, optical imaging, dispersive signal technology, acoustic pulse recognition, or other touch-sensitive technologies known in the art. Many of these technologies allow for multi-touch responsiveness of user interface 282 allowing registration of touch in two or even more locations at once. The display may use any of a variety of display technologies such as light emitting diode (LED), organic light-emitting diode (OLED), liquid-crystal display (LCD), organic light-emitting transistor (OLET), surface-conduction electron-emitter display (SED), field emission display (FED), digital light processing (DLP), liquid crystal on silicon (LCoC), or any other display technologies known in the art. In some embodiments, the user interface 282 is configured to present visual media (e.g., text, graphics, etc.) without requiring a backlight. In some embodiments, client device 280 may not contain user interface 282.
Referring now to
In step 310, the POI system 210 can receive from the setup device 270 a new POI datablock. The setup device 270 can take the form of a computer. In some embodiments, the POI system may present an input text form to the setup device 270 that can be filled out by a user using the setup device 270. Each new POI datablock can correspond to an individual POI. The new POI datablock can include POI data (e.g., info 253, tags 254, restrictions 255, etc.). POI data (e.g., info 253, tags 254, restrictions 255, etc.) may contain information relevant to an individual POI (e.g., name, alias, profile picture, badge number, category of threat, contact information, position, employee type, assignment, sex, race, age, height, weight, eye color, hair color, facial features, traits, tattoos, vehicle information, restriction information, etc.). POI data (e.g., info 253, tags 254, restrictions 255, etc.) can include info 253, tags 254, and/or restrictions 255. Info 253 can include POI specific information as described above for POI data (e.g., info 253, tags 254, restrictions 255, etc.). Tags 254 can include brief descriptive categories of individual POI threats (e.g., threat of violence, etc.). Restrictions 255 can include POI specific rules used to determine the presence of a POI alarm given the POI (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.). In some embodiments, the completed input text form is submitted by the user using setup device 270, and parsed by the POI system 210 to produce a new POI datablock. In some embodiments, the setup device 270 can send a POI datablock data structure. By way of example, the setup device 270 could parse an input text form and produce a POI datablock data structure to send to the POI system 210. Communication between the setup device 270 and POI system 210 can be through a network, a communications connection (either hardwired, wireless, or a combination of hardwired or wireless), or another technology known in the art.
In step 320, the POI system 210 can generate an identifier for the new POI datablock. The identifier can uniquely identify an individual POI datablock. The POI system 210 can generate a unique individualized identifier by maintaining a list of assigned identifiers and incrementally assigning a new POI datablock with an identifier value sequentially greater than that contained in the list of assigned identifiers. By way of example, the first POI datablock may be stored with identifier value “10000” and the second POI datablock may be stored with identifier value “10001.” In some embodiments, the POI system 210 can generate an identifier for the new POI datablock by other means not here mentioned.
In step 330, the POI system 210 can receive from the setup device 270 POI data (e.g., info 253, tags 254, restrictions 255, etc.). The setup device 270 can take the form of a computer. In some embodiments, the POI system may present an input text form to the setup device 270 that can be filled out by a user using the setup device 270. The input text form may contain fields for info 253, tags 254, and/or restrictions 255. The user may enter the info 253, tags 254 and/or restrictions 255 using the setup device 270. In some embodiments, the completed input text form is submitted by the user using setup device 270 and parsed by the POI system 210 to produce info 253, tags 254, and/or restrictions 255. In some embodiments, the setup device 270 can parse and send info 253, tags 254, and/or restrictions 255 itself. By way of example, the setup device 270 could parse an input text form and produce info 253, tags 254, and restrictions 255 to send to the POI system 210. Communication between the setup device 270 and POI system 210 can be through a network, a communications connection (either hardwired, wireless, or a combination of hardwired or wireless), or another technology known in the art.
In step 340, the new POI datablock containing POI data (e.g., info 253, tags 254, restrictions 255, etc.) can be stored with the identifier in the POI system 210. The new POI datablock can be stored as a data structure. The new POI datablock can stored such that it can be uniquely identified using the associated identifier. The new POI datablock may be stored by POI Database Manager 250 in a memory. The memory can include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions.
Referring now to
In step 410, the interface manager 244 can receive from one or more security components 260 security data identifying a location and an individual. In some embodiments, the identification may take the form of a general identifier. Security data may include a badge number, access controller identifier, finger print data, retina scan data, biometric data, facial recognition indication, event time, component location, and/or other information not here included. A general identifier may be a high-level descriptor of the POI and may include height, age, weight, name, nickname, alias, race, biometric data, voice data, license plate, and/or other information not here listed. By way of example, a security component 260 could report badge number 142094 scanned in at location 12 at 12:09 A.M.
In step 420, the identifier 246 can search a plurality of POI datablocks 252 with the general identifier of the individual received in step 410. The identifier 246 can search the plurality of datablocks 252 by matching the general identifier of the individual to information contained in the plurality of datablocks 252. By way of example, the identifier 246 could match the received badge number “142094” to stored badge number “142094” contained in info 253. The search may be a binary search, a ranked search, or another search method not here listed.
In step 430, the identifier 246 may verify, based on the search, whether the individual is a POI. According to the exemplary embodiment, the identifier 246 may verify the individual as a POI if the identifier of the general identifier matches a POI identifier associated with a POI datablock 252 stored in memory 240. Any individual with an associated POI datablock 252 can be a POI. By way of example, the identifier 246 could verify the individual with badge number 142094 as a POI based on a matching badge number of 142094 contained in info 253 associated with a POI datablock 252.
In step 440, the identifier 246 can determine, given the POI identifier, whether a POI alarm exists. According to the exemplary embodiment, the identifier 246 can determine the existence of a POI alarm by comparing the security data to the restrictions 255 associated with the POI datablock 252 identified in step 430. Restrictions 255 can include POI specific rules used to determine the presence of a POI alarm given the POI (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.). By way of example, if security data indicates that a POI is in an area listed as restricted in the restrictions 255 of the POI datablock 252 associated with the POI, then a POI alarm can be determined to exist.
In step 450, in response to determining the presence of a POI alarm, the identifier 246 may send to the reporter 248 the POI identifier, security data, and/or POI data (e.g., info 253, tags 254, restrictions 255, etc.) associated with the POI alarm. The identifier 246 can send information to the reporter 248 to build a POI GUI notification which includes information associated with the POI. The identifier 246 can send the POI identifier, security data, info 253, tags 254, and/or restrictions 255 as a data structure. By way of example, the identifier 246 can send info 253, tags 254, and/or restrictions 255 as a POI datablock data structure.
Referring now to
At step 510, the reporter 248 can receive from the identifier 246, the POI identifier, security data, and/or POI data (e.g., info 253, tags 254, restrictions 255, etc.) associated with the POI alarm. The POI identifier, security data, and/or POI data (e.g., info 253, tags 254, restrictions 255, etc.) may be received from the identifier 246 as a data structure or as unstructured data. In some embodiments, the reporter 248 can parse or otherwise structure the data received from the identifier 246.
At step 520, the reporter 248 can retrieve from the POI database manager 250 recipient data 258 associated with the POI alarm. The recipient data 258 may contain information relating to the one or more recipient(s) of the POI GUI notification. Recipient data 258 can include email addresses, phone numbers, messenger contacts, pager numbers, IP addresses, and/or other contact information not listed herein. Recipient data 258 can include information relating to the recipient (e.g., name of recipient, position, alternate contacts, etc.). Recipient data 258 may be individualized and/or associable with specific security monitored locations (e.g., buildings, parking lots, campuses, cities, rooms, etc.), individual POI'S (e.g., terminated employee, high-profile individual, violent individual, etc.), POI tags (e.g., threat of violence, etc.), and/or POI alarms (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.). The reporter 248 can retrieve recipient data 258 through a defined rules process. In some embodiments, a user may define a set of rules which determine the appropriate recipients for a given alarm. By way of example, the set of rules could be:
In some embodiments, the POI system 210 may contain default rules that can be selectively overwritten by the user. In some embodiments, the reporter 248 may not use a defined rules process and may retrieve recipient data 258 through other means not here mentioned.
At step 530, the reporter 248 can retrieve from the POI database manager 250 response procedure data 256. The response procedure data 256 may contain information relating to the required response protocol for a POI alarm (e.g., receptionist required actions, security required actions, etc.) to be included in the POI GUI notification. The response procedure data 256 may contain steps, actions, or instructions individualized to the specific POI alarm. In some embodiments, the response procedure data 256 may contain embedded scripts to trigger further action. Response procedure data 256 can be individualized and/or associable with specific security monitored locations (e.g., buildings, parking lots, campuses, cities, rooms, etc.), individual POI'S (e.g., terminated employee, high-profile individual, violent individual, etc.), POI tags (e.g., threat of violence, etc.), and/or POI alarms (e.g., presence within a restricted area, violation of restraining order, presence of terminated employee, etc.). The reporter 248 can retrieve response procedure data 256 through a defined rules process. In some embodiments, a user may define a set of rules which determine the appropriate response procedures for a given alarm. By way of example, the set of rules could be:
In some embodiments, the POI system 210 may contain default rules and response procedures that can be selectively overwritten by the user. In some embodiments, the reporter 248 may not use a defined rules process, may use a precomposed emergency response document, or may retrieve response procedure data 256 through other means not here mentioned.
At step 540, the reporter 248 can send to the presenter 242 a populated POI GUI interface. According to the exemplary embodiment, the populated POI GUI interface may contain the POI data (e.g., info 253, tags 254, restrictions 255, etc.), security data, and/or response procedure data 256 associated with the POI alarm. The reporter 248 may create the populated POI GUI interface by populating fields in a blank POI GUI interface template. In some embodiments, the user may select from multiple existing POI GUI interface templates and/or can edit existing POI GUI interface templates. The POI GUI interface templates may vary depending on the type of POI GUI notification. By way of example, a phone push notification could be shorter and link to a longer report than an email notification.
At step 550, the presenter 242 can send to the client device 280 the populated POI GUI interface. In some embodiments, other components (e.g., processor 230, POI system 210, etc.) can be configured to send the populated POI GUI interface. In some embodiments, client device 280 can take the form of a computer or other forms (e.g., pager, cell phone, controller, switchboard, building management system, script, program, computer, server, etc.). In some embodiments, the POI GUI notification can take the form of an email or other forms (e.g., push notification, SMS text message, pager alert, etc.). The form of the POI GUI notification can be determined by the user. The POI GUI notification may take multiple forms and/or may vary depending on the type of POI alarm.
Referring now to
Referring now to
Referring now to
Referring now specifically to
Person of interest subsection 802 may include the name, position, alias, badge number, badge holder employer, employee type, assignment, and/or other information not here listed. In some embodiments, person of interest subsection 802 may include a picture of the POI. Person of interest subsection 802 can include tags 254 associated with the POI. Person on interest subsection 802 can include a brief descriptive header of the subsection to orient users to the information contained within the subsection.
Contact details subsection 803 can display the contact information associated with the POI, managers, security personnel, police, and/or other individuals not here listed. Contact details subsection 803 can include an email of the POI, an office number of the POI, a cell number of the POI, an organizational contact of the POI, and/or a known address of the POI. Contact details subsection 803 can include a brief descriptive header of the subsection to orient users to the information contained within the subsection. In some embodiments, contact details subsection 803 includes pronouncers associated with contacts included in the contact details subsection 803.
Referring now specifically to
Referring now specifically to
Vehicle subsection 1001 may contain a description, plate number, state, year, make/model, color, decals, and/or other information associated with the vehicle of the POI not contained herein. In some embodiments, vehicle subsection 1001 may contain activity traced associated with the POI vehicle including activity type, activity time, building, building type, address, campus, device, and/or other information not contained herein. In some embodiments, vehicle subsection 1001 does not include activity traced associated with the POI vehicle, or contains other information or subsections not here listed. Vehicle subsection 1001 can include a brief descriptive header of the subsection to orient users to the information contained within the subsection.
Referring now to
Referring now to
Referring now to
The interface 3000 is shown to include a summary card 3002 including identification details of the person and badge being traced, the type of activity (in this example, an access granted event), the date and time of the activity, the device detecting the badge use and its location, and the case type (in this example, threat of violence). The summary card 3002 includes a “View in” option 3004, allowing the user to open a badge trace details page. Where no case type is assigned, the summary card 3002 is displayed without this information, as the view 3014 of the summary card 3002.
The interface 3000 is shown to include a details card 3006. In the details card 3006, the details of the person traced are displayed, including all badge numbers associated with that person. The details card 3006 also includes the details of the activity, such as the type of activity, local time of the activity, building and building type, address, campus, and the device detecting the badge activity 3008. The interface 3000 further includes a case management card 3010. The case management card 3010 provides more information which can be user specified for a particular badge trace.
The interface 3000 includes email footer text 3012 confirming to the recipient that they are the person to be notified in relation to a badge trace and including the expiry date of the badge trace and the identity of the person who created the trace and when the trace was created. The email footer allows the recipient to change their preferences and provides a contact email.
Referring now to
Referring now to
Cards 3416, 3418, and 3420 show different examples of the badge trace card 3406 to illustrate various options. The card shows the name and alias of the badge holder, and an icon with their profile picture 3422. Where no picture is available from the system directory, the icon is the initials of the name of the person and surname 3424. The card also displays the name 3426 of the person who created the trace, the time of creation, converted to the local time 3428 of a user interacting with the interface 3100, and the expiry date of the trace, converted to a local time 3430 of the user. Where a traced individual has been assigned multiple badges, all badges 3432 are displayed.
Referring now to
Referring now to
Referring now to
Referring now to
Where multiple badges are assigned to one person, all such badges will appear in the “Trace” section, showing their active or inactive status 4822. By selecting the “CHANGE” option, the user is presented with a window 4818, allowing them to change the name, alias, or badge number for the badge trace. Where no name, alias, or badge number is found in the system directory, a non-interactive cell displays 4820, indicating that no results were found can be displayed. As the user types in the input field, a drop-down list of possible matches is presented 4824. After the user selects a known name, alias, or email from the list 4826, the user may cancel or save the change. If saved, a transient, self-dismissing message 4828 can appear confirming that the change has been saved.
The “Expiry date” section is shown in detail 4918. When the user selects the “EDIT” option, a window 4914 can appear, displaying a calendar for the user to select the expiry date of the trace, which must be a date in the future. The “Building applied” section is shown in detail in 4916. When the user selects the “CHANGE” option, a modal window 4920 appears, allowing the user to input a different building (or none). Where no building selection is made, the section displays as shown in 4922. The procedure for making changes follows the same methodology as that for changing the identity of the badge trace (as described with reference to
The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.
The present application claims the benefit and priority to U.S. Provisional Patent Application No. 62/751,856 filed on Oct. 29, 2018, and U.S. Provisional Patent Application No. 62/751,898 filed on Oct. 29, 2018, the entire disclosures of which are incorporated by reference herein.
Number | Date | Country | |
---|---|---|---|
62751856 | Oct 2018 | US | |
62751898 | Oct 2018 | US |