Artificial intelligence badge issuing system

Abstract

The invention discloses an artificial intelligence badge issuing system. A new badge for a user of the facility may be generated to physically access one or more regions of the facility. Access to one or more databases associated with a facility may be provided to a large language model (LLM). The LLM may be prompted to automatically complete at least a portion of a badge application form for a new badge or renewal badge for a user of the facility, where, once completed and approved, the badge application form authorizes activation of the new badge or renewal badge for the user of the facility. The LLM may automatically populate at least a portion of the badge application form by extracting corresponding information from one or more databases associated with the facility.

Description

Technical Field

[0001] This disclosure relates generally to a badge issuing system for providing badges to access security facilities. More specifically, this disclosure relates to using artificial intelligence to help automate the creation of badges in the badge issuing system. Background Technology

[0002] In conventional badge distribution systems, the process of issuing badges to users relies heavily on human input, which can increase the likelihood of errors. This also hinders the efficiency of badge operators and reduces their ability to handle the number of badges typically required to be issued within a specific timeframe. Due to this heavy reliance on manual processes, conventional badge distribution systems suffer from inefficiencies and potential risks. In some facilities, a large volume of daily badge issuance can exacerbate these challenges, leading to increased errors, delays, and vulnerability to unauthorized access. The desired outcome is a badge distribution system that automates and streamlines the badge issuance and management processes, thereby reducing reliance on manual intervention and mitigating the risks of errors and unauthorized access. The desired outcome is a way to more effectively meet daily badge issuance requirements, ensure smooth operation, and comply with security standards. The desired outcome is a way to reduce the human costs associated with manual badge issuance operations and streamline operational workflows, resulting in significant cost savings. Summary of the Invention

[0003] This disclosure relates generally to badge issuance systems. More specifically, this disclosure relates to using artificial intelligence to help automate the creation of badges in a badge issuance system. Examples can be seen in a method for generating new or renewed badges for users of a facility, wherein the badge includes access rights for physically accessing one or more areas of the facility. The method includes providing a large language model (LLM) with access to one or more databases associated with the facility, such as a human resources (HR) database. The LLM is prompted to automatically complete at least a portion of a badge application form for a new or renewed badge for that user of the facility, wherein once completed and approved, the badge application form authorizes the activation of the new or renewed badge for that user of the facility. In some cases, the badge application form includes two or more information fields, wherein the LLM automatically populates multiple information fields of the two or more information fields of the badge application form by retrieving relevant information from one or more databases associated with the facility, such as an HR database.

[0004] Another example can be seen in a system used to generate new or renewed badges for requesting users of a facility, where the badges include access permissions for physical access to one or more areas of the facility. The system includes one or more databases containing user information for multiple users of the facility, access permissions for the multiple users of the facility, and one or more user associations and / or relationships between the multiple users of the facility. A controller is operatively coupled to one or more databases. The controller is configured to provide access to one or more databases to a Large Language Model (LLM). The controller is configured to submit one or more prompts to the LLM, prompting the LLM to determine access permissions for the requesting user based at least in part on the access permissions for the multiple users of the facility and one or more user associations and / or relationships between the requesting user and one or more of the multiple users of the facility. The controller is configured to automatically create a badge request for the requesting user that includes the determined access permissions.

[0005] Another example can be seen on a non-transitory computer-readable medium on which instructions are stored. When executed by one or more processors, the instructions cause one or more processors to provide a Large Language Model (LLM) with access to one or more databases associated with a facility. The one or more processors prompt the LLM to automatically complete at least a portion of a badge request from a requesting user for the facility, wherein once completed and approved, the badge request authorizes the activation of a badge to provide the requesting user with access to at least a portion of the facility. In some cases, the badge request includes two or more information fields, wherein the LLM automatically populates multiple information fields of the two or more information fields of the badge request by retrieving relevant information from one or more databases associated with the facility. The two or more information fields of the badge request may include a name field, an access permission field, an access permission expiration date field, and one or more of the following: date of birth field, gender field, height field, weight field, hair color field, eye color field, picture field, country ID number field, blood type field, nationality field, job title field, job category field, and work location field. These are just examples.

[0006] The foregoing summary is provided to facilitate understanding of the innovative features unique to this disclosure and is not intended to be a complete description. A full understanding of this disclosure can be obtained by considering the entire specification, claims, drawings, and abstract as a whole. Attached Figure Description

[0007] This disclosure will be more fully understood by taking into account the following description of various examples in conjunction with the accompanying drawings, in which:

[0008] Figure 1 This is a schematic block diagram illustrating an exemplary system for generating new or renewed badges;

[0009] Figure 2A and Figure 2B Together they form a flowchart illustrating exemplary methods for generating new or renewed badges; and

[0010] Figure 3 This is a flowchart illustrating an exemplary method for generating new badges or renewing badges.

[0011] While this disclosure is subject to various modifications and alternatives, its details have been shown by way of example in the accompanying drawings and will be described in detail. However, it should be understood that this disclosure is not intended to limit it to the specific examples described. Rather, it is intended to cover all modifications, equivalents, and alternatives that fall within the substance and scope of this disclosure. Detailed Implementation

[0012] The following description should be read with reference to the accompanying drawings, in which similar elements in the different drawings are numbered in the same manner. The drawings are not necessarily drawn to scale and depict examples that are not intended to limit the scope of this disclosure. While examples of various elements are illustrated, those skilled in the art will recognize that many of the examples provided have suitable alternatives that can be utilized.

[0013] This document assumes that all numbers are modified by the term “about” unless otherwise explicitly stated. Expressions of numerical ranges using endpoints include all numbers contained within that range (e.g., 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).

[0014] As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural references, unless otherwise expressly stated. As used in this specification and the appended claims, the term “or” is generally used in its meaning to include “and / or,” unless otherwise expressly stated.

[0015] It should be noted that references to "one embodiment," "some embodiments," or "other embodiments" in the specification indicate that the described embodiments may include specific features, structures, or characteristics, but each embodiment need not necessarily include that specific feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in conjunction with an embodiment, it is conceivable that, whether explicitly described or not, that feature, structure, or characteristic may be applied to other embodiments, unless otherwise expressly stated otherwise.

[0016] Figure 1This is a schematic block diagram illustrating an exemplary system 10 for generating new or renewed badges for requesting users of a facility, wherein the badges include access permissions for physical access to one or more areas of the facility. System 10 includes one or more databases 12 containing information for generating new or renewed badges. The one or more databases 12 may include user information 14 for multiple users of the facility, access permissions 16 for multiple users of the facility, and one or more user associations and / or relationships 18 between multiple users of the facility. User information 14 may include a human resources (HR) database associated with the facility. The HR database may include personal information of users associated with the facility. In some cases, the one or more databases 12 may include at least a portion of an organization chart of an organization associated with the facility, wherein the organization chart identifies one or more supervisors and / or one or more colleagues for each of at least some of the users of the facility. In some cases, the one or more databases 12 may include access permissions currently assigned to a user by at least one of the one or more supervisors and / or one or more colleagues. In some cases, the one or more databases 12 may include an access log recording previous accesses made by one or more of the user's one or more supervisors and / or one or more colleagues. In some cases, one or more databases 12 may include access logs that record a user's previous visits. In some cases, one or more databases 12 may include communication logs that record communications between users of the facility (e.g., via telephone, email, Microsoft TEAMS calls / conferences, etc.). In some cases, one or more databases 12 may include information fields from previously authorized badge application forms.

[0017] Controller 20 is operatively coupled to one or more databases 12. Controller 20 is configured to provide access to predictive analytics models of the one or more databases 12. In some cases, the predictive analytics model may be or otherwise include a large language model (LLM) 22. In some cases, the LLM 22 may include one or more predictive analytics models. When providing the LLM, controller 20 is configured to submit one or more prompts to the LLM 22 that prompt the LLM 22 to determine the access permissions of the requesting user based at least in part on access permissions 16 of multiple users of the facility and one or more user associations and / or relationships 18 between the requesting user and one or more users of the facility. Controller 20 is configured to automatically create a badge request for the requesting user that includes the determined access permissions. In some cases, two or more information fields on a badge application form may include two or more of the following: name field, access permission field, access permission expiration date field, and one or more of the following: date of birth field, gender field, height field, weight field, hair color field, eye color field, image field, country ID number field, blood type field, nationality field, job title field, job category field, and work location field. In some cases, two or more information fields on a badge application form may include a hair color field, and LLM 22 (which may be a multi-model LLM) can process images of users at the facility and extract the user's hair color from the image, automatically populating the hair color field of the badge application form with the extracted hair color. The user's eye color, skin color, and other physical characteristics can be similarly extracted and automatically added to the badge application form.

[0018] In some cases, controller 20 may be configured to prompt LLM 22 for patterns in previous access events of multiple users of the facility, and to determine the access rights 16 of the requesting user based at least in part on the patterns identified in the previous access events of the multiple users of the facility and one or more user associations and / or relationships 18 between the requesting user and one or more of the multiple users of the facility. In some cases, controller 20 may be configured to automatically submit a badge request for the requesting user for approval, and once approved, the badge request automatically activates a badge for the requesting user, thereby providing physical access to one or more areas of the facility based on access rights.

[0019] In some cases, LLM 22 can automatically populate a user's access permission fields using assessed permissions derived from the user's access permissions of one or more supervisors and / or one or more colleagues. In some cases, LLM 22 can automatically populate a user's badge application form's access permission fields using assessed permissions derived at least partially from previous access by one or more of the user's supervisors and / or one or more of their colleagues. In some cases, LLM 22 can automatically populate a user's access permission fields using assessed permissions derived at least partially from the user's previous access. In some cases, LLM 22 can automatically populate a user's access permission fields using assessed permissions derived at least partially from communication logs between users of the facility (e.g., communications via telephone, email, Microsoft TEAMS calls / conferences, etc.). In some cases, LLM 22 can automatically suggest changes to one or more information fields in the information fields of the badge application form, at least partially based on one or more information fields in a previously authorized information field of the badge application form.

[0020] Figure 2A and Figure 2B This is a flowchart illustrating an exemplary method 24 for generating new or renewed badges for users of a facility, the badge including access rights for physical access to one or more areas of the facility. Exemplary method 24 includes providing access to one or more databases associated with the facility to a predictive analytics model and / or a large language model (LLM) 22, as indicated in box 26. In this example, an LLM is provided. The LLM is prompted to automatically complete at least a portion of a badge application form for the new or renewed badge for the user of the facility, wherein once completed and approved, the badge application form authorizes the activation of the new or renewed badge for the user of the facility. The badge application form may include two or more information fields, wherein the LLM automatically populates multiple information fields of the two or more information fields of the badge application form by extracting and / or determining relevant information from one or more databases associated with the facility, as indicated in box 28. In some cases, method 24 includes submitting the badge application form for approval once completed, as indicated in box 30. Method 24 may include receiving approval for the badge application form, as indicated in box 32. Approval is typically granted manually by authorized security personnel. Once approved, a user's new or renewed badge can be activated, as indicated in box 34. In some cases, new or renewed badges can be approved and activated automatically.

[0021] In some cases, one or more databases may include a human resources (HR) database associated with the facility, which contains personal information of users associated with the facility. In some cases, the badge application form may include two or more information fields, such as a name field, access permission field, access permission expiration date field, and one or more of the following: date of birth field, gender field, height field, weight field, hair color field, eye color field, picture field, country ID number field, blood type field, nationality field, job title field, job category field, and work location field. The badge application form may include a hair color field. In some cases, the LLM (which may be a multi-model LLM) may process a picture of a user of the facility to extract the user's hair color from the picture and automatically populate the hair color field of the badge application form with the extracted hair color, as indicated in box 36.

[0022] In some cases, one or more databases may include at least a portion of an organization chart of the organization associated with the facility, which identifies one or more supervisors and / or one or more colleagues of at least some of the users of the facility. In some cases, one or more databases may include access permissions currently assigned to a user by at least one of the one or more supervisors and / or one or more colleagues. Method 24 may include the LLM automatically populating the user's access permission fields using evaluated permissions derived from the user's access permissions from the one or more supervisors and / or one or more colleagues, as indicated in box 38.

[0023] continue Figure 2B One or more databases may include access logs recording previous accesses made by one or more of the user's supervisors and / or one or more of their colleagues. The LLM may automatically populate the access permissions fields of the user's badge application form using assessed permissions derived at least in part from previous accesses made by the user's one or more supervisors and / or one or more of their colleagues, as indicated in box 40. In some cases, for badge renewal, one or more databases may include access logs recording the user's previous accesses, and the LLM may automatically populate the user's access permissions fields using assessed permissions derived at least in part from the user's previous accesses, as indicated in box 42. Access permissions may be customized to allow access only to certain areas of the facility and / or only during certain time periods.

[0024] In some cases, one or more databases may include communication logs that record communications between users of the facility (e.g., communications via telephone, email, Microsoft TEAMS calls / conferences, etc.). The LLM may automatically populate user access permission fields using assessment permissions derived at least in part from the communication logs between users of the facility, as indicated in box 44. In some cases, one or more databases may include information fields from previously authorized badge application forms, and the LLM may automatically suggest changes to one or more information fields in the badge application form based at least in part on one or more of these information fields, as indicated in box 46. In some cases, suggested changes to one or more information fields may include changes to conform to naming conventions and / or formatting used for certain information. In some cases, suggested changes to one or more information fields may include changes to conform to facility-specific naming conventions and / or facility-specific formatting.

[0025] In some cases, one or more databases may include access permission expiration times for each authorized user of the facility, and method 24 may include prompting the LLM to estimate the workload of security personnel in generating new badges and / or renewing badges within a future time period (e.g., the following week) based at least in part on the access permission expiration times for each authorized user of the facility, as indicated in box 48. In some cases, one or more databases may include access badge activation times for each authorized user of the facility, and method 24 may include prompting the LLM to estimate the rate at which badges can be processed based at least in part on the access badge activation times for at least some of the authorized users of the facility, as indicated in box 50.

[0026] Figure 3 This is a flowchart illustrating an exemplary method 52 for generating a new or renewed badge. Exemplary method 52 begins with a request from HR (Human Resources) for a badge to be generated, as indicated in box 54. AI (Artificial Intelligence) can be used to search HR data sources, such as various databases, to obtain information relevant to generating the new or renewed badge, as indicated in box 56. As indicated in box 58, the badge is created. As indicated in box 60, the badge needs to be approved. This can include manual approval, such as by an authorized person reviewing the badge request. This can include automated approval, such as by an HR system or the system that creates the badge. As indicated in box 62, the badge is then activated.

[0027] Although several exemplary embodiments of this disclosure have been described thus, those skilled in the art will readily understand that other embodiments can be made and used within the scope of the appended claims. However, it should be understood that this disclosure is merely illustrative in many respects. Changes may be made to details, particularly those relating to shape, size, arrangement of parts, and exclusion and order of steps, without departing from the scope of this disclosure. The scope of this disclosure is, of course, defined by the language expressed in the appended claims.

Claims

1. A method for generating new or renewing badges for users of a facility, the badges including access permissions for physical access to one or more areas of the facility, the method comprising: Provides the Large Language Model (LLM) with access to one or more databases associated with the facility; as well as The LLM automatically completes at least a portion of a badge application form for a new or renewed badge for a user of the facility, wherein once completed and approved, the badge application form authorizes the activation of the new or renewed badge for the user of the facility. The badge application form includes two or more information fields, wherein the LLM automatically populates multiple information fields of the two or more information fields of the badge application form by retrieving relevant information from the one or more databases associated with the facility.

2. The method according to claim 1, wherein the method comprises: Once completed, submit the badge application form for approval; Receive approval for the badge application form; as well as Once approved, the user's new or renewed badge is activated.

3. The method of claim 1 or 2, wherein the one or more databases include a human resources database associated with the facility, wherein the human resources database includes personal information of the users associated with the facility.

4. The method of claim 3, wherein the two or more information fields of the badge application form include a name field, an access permission field, an access permission expiration date field, and one or more of the following: date of birth field, gender field, height field, weight field, hair color field, eye color field, image field, country ID number field, blood type field, nationality field, job title field, job category field, and work location field; optionally, wherein the two or more information fields of the badge application form include a hair color field, and wherein the LLM processes an image of the user of the facility to extract the user's hair color from the image, and automatically fills the hair color field of the badge application form with the extracted hair color.

5. The method of any one of claims 1 to 4, wherein the one or more databases include at least a portion of an organization chart of an organization associated with the facility, wherein the organization chart identifies one or more supervisors and / or one or more colleagues of at least some of the users of the facility.

6. The method of claim 5, wherein the one or more databases include access permissions currently assigned to the user by at least one of the one or more supervisors and / or one or more of the colleagues, and wherein the LLM automatically populates the user's access permission field using evaluated permissions derived from the user's access permissions by the one or more supervisors and / or one or more of the colleagues.

7. The method of claim 5, wherein the one or more databases include an access log recording previous accesses made by the user's one or more supervisors and / or one or more colleagues, wherein the LLM automatically populates the access permission field of the user's badge application form with evaluation permissions derived at least in part from the previous accesses made by the user's one or more supervisors and / or the previous accesses made by one or more colleagues.

8. The method of any one of claims 1 to 7, wherein for badge renewal, the one or more databases include an access log recording the user's previous accesses, and wherein the LLM automatically populates the user's access permission field using evaluated permissions derived at least in part from the user's previous accesses.

9. The method of any one of claims 1 to 8, wherein the one or more databases include communication logs that record communications between users of the facility, and wherein the LLM automatically populates the user's access permission field using evaluation permissions derived at least in part from the communication logs between users of the facility.

10. The method of any one of claims 1 to 9, wherein the one or more databases include information fields from a previously authorized badge application form, and wherein the LLM automatically suggests changes to one or more information fields of the badge application form based at least in part on one or more of the information fields of the previously authorized badge application form; further optionally: The proposed changes to one or more of the information fields include changes that conform to naming conventions and / or formatting; and / or The proposed changes to one or more of the information fields include changes that conform to facility-specific naming conventions.

Images