Information processing system, information processing method and program

The information processing system manages visitor safety by utilizing schedule information and chat message reactions to efficiently track and confirm the presence and safety of both employees and visitors during disasters.

JP2026041140APending Publication Date: 2026-03-10RECEPTIONIST INC
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-08-26
Publication Date
2026-03-10

AI Technical Summary

Technical Problem

Conventional safety confirmation systems fail to manage and track the safety of visitors during disasters.

Method used

An information processing system that includes a schedule acquisition unit to acquire visitor schedules, a presence determination unit to determine visitor presence in a building, and a visitor output unit to list present visitors, along with safety confirmation through chat messages and reactions.

Benefits of technology

Enables effective safety management of both employees and visitors by estimating departure times and determining presence, reducing the time and effort required for individual safety checks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026041140000001_ABST
    Figure 2026041140000001_ABST
Patent Text Reader

Abstract

To be able to manage visitors. [Solution] The information processing system is characterized by comprising a schedule acquisition unit that acquires schedule information for visitors within the building, a presence determination unit that determines whether the visitor is present in the building based on the schedule information, and a visitor output unit that outputs a list of visitors who are present in the building.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing method, and a program. [Background technology]

[0002] In recent years, there has been an increase in the number of cases where IT is used for part or all of the reception work when a visitor arrives at a company's reception desk. Specifically, whereas previously a person (for example, a receptionist) would receive the visitor and transfer the visitor to the person in charge, an increasing number of companies are now using IT to perform part of the reception work by having the visitor input a designation for receiving a visit on a terminal screen and automatically notifying the person in charge that a visitor has arrived (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-057114 A Summary of the Invention [Problem to be solved by the invention]

[0004] There is a need to check the safety of people when a disaster occurs, but conventional safety confirmation systems cannot keep track of visitors.

[0005] The present invention has been made in view of the above background, and aims to provide a technique that can manage visitors. [Means for solving the problem]

[0006] The main invention of the present invention for solving the above problem is an information processing system characterized by comprising a schedule acquisition unit that acquires schedule information of visitors within the building, a presence determination unit that determines whether the visitor is present in the building based on the schedule information, and a visitor output unit that outputs a list of visitors who are present in the building.

[0007] Other problems and solutions disclosed in this application will be made clear in the section on preferred embodiments of the invention and the drawings. [Effects of the Invention]

[0008] According to the present invention, visitors can be managed. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the overall configuration of an information processing system. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of a management server 2. [Figure 3] FIG. 2 illustrates an example of the software configuration of a management server 2. [Figure 4] FIG. 10 is a diagram illustrating the operation of the management server 2. DETAILED DESCRIPTION OF THE INVENTION

[0010] <System Overview> An information processing system according to one embodiment of the present invention will now be described. The information processing system of this embodiment aims to support user safety confirmation. In this information processing system, a message (hereinafter, a chat message) related to a chat service inquiring about the safety of multiple users is sent to the user. If a response is received from the user, the safety of the user (employee) who responded can be ascertained. A response to a chat message may be, for example, a stamp, but it may also be a chat message posted by a user in the same channel or thread as the chat message. The information processing system of this embodiment may also function as a reception system for managing visitors to a facility. The system manages schedule information for visitors who visit the facility, predicts the visitor's departure time based on the schedule information, and enables safety confirmation for visitors who have not yet left the facility. While conventional safety confirmation tools are used to confirm the safety of a company's employees (users), the information processing system of this embodiment allows for safety confirmation of not only employees but also visitors.

[0011] 1 is a diagram showing an example of the overall configuration of an information processing system. The information processing system of this embodiment is configured to include a management server 2. The management server 2 is communicably connected to a user terminal 1 via a communication network. The communication network is, for example, the Internet, and is constructed using a public telephone line network, a mobile phone line network, a wireless communication path, Ethernet (registered trademark), etc.

[0012] The user terminal 1 is a computer operated by workers and visitors. The user terminal 1 may be, for example, a smartphone, a tablet computer, or a personal computer.

[0013] The management server 2 may be a general-purpose computer such as a workstation or a personal computer, or may be logically realized by cloud computing.

[0014] <Administration Server> FIG. 2 is a diagram illustrating an example of the hardware configuration of the management server 2. Note that the illustrated configuration is an example, and other configurations may also be used. The management server 2 includes a CPU 201, a memory 202, a storage device 203, a communication interface 204, an input device 205, and an output device 206. The storage device 203 stores various data and programs, and is, for example, a hard disk drive, a solid state drive, or a flash memory. The communication interface 204 is an interface for connecting to a communication network, and is, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone network, a wireless communication device for wireless communication, or a USB (Universal Serial Bus) connector or an RS232C connector for serial communication. The input device 205 is used to input data, and is, for example, a keyboard, a mouse, a touch panel, a button, a microphone, or the like. The output device 206 is used to output data, and is, for example, a display, a printer, a speaker, or the like. Each functional unit of the management server 2 described below is realized by the CPU 201 reading a program stored in the storage device 203 into the memory 202 and executing it, and each storage unit of the management server 2 is realized as part of the storage area provided by the memory 202 and the storage device 203.

[0015] 3 is a diagram illustrating an example of the software configuration of the management server 2. The management server 2 includes a user information storage unit 231, a visitor information storage unit 232, a disaster information acquisition unit 211, a message transmission unit 212, a response acquisition unit 213, a safety determination unit 214, a safety aggregation unit 215, a schedule acquisition unit 216, a presence determination unit 217, and a visitor output unit 218.

[0016] <Storage section> The user information storage unit 231 stores information about users (hereinafter referred to as user information). The user information may include attributes such as the user's name and the user's account name in the chat service, associated with information that identifies the user (hereinafter referred to as user identification information, which may be, for example, a user ID). The user information may include, for example, information that identifies a channel or thread in which the user can view messages in the chat service. The user information may include information that indicates the department to which the user belongs.

[0017] The visit information storage unit 232 stores information related to the visit of a visitor (hereinafter referred to as visit information). The visit information can include, in association with information identifying the visitor (hereinafter referred to as visitor identification information), the visitor's entry date and time (a value can be set if the visitor has not entered the facility), user identification information identifying the user of the visitor's location (the user in charge of handling the visitor), and schedule information of the visitor. The schedule information can include a start (scheduled) date and time and an end (scheduled) date and time (or scheduled time). Note that the schedule information can be managed in a calendar system, for example, and can be information (e.g., a URL) identifying calendar information managed by the calendar system. The visit information can also include the visitor's account name in a chat service.

[0018] <Functional section> The disaster information acquisition unit 211 acquires information related to disasters (hereinafter referred to as disaster information). The disaster information acquisition unit 211 can acquire, for example, earthquake and volcano information published by the Japan Meteorological Agency as disaster information. The disaster information acquisition unit 211 can acquire, for example, disaster information from a server of the Japan Meteorological Agency or a weather company. The disaster information acquisition unit 211 can acquire, for example, earthquake and volcano information as disaster information by calling the API of the Earthquake and Tsunami Observation System (EPOS) of the Japan Meteorological Agency. The disaster information acquisition unit 211 can acquire, for example, river water level and rainfall information as disaster information by calling the disaster prevention information API of the Ministry of Land, Infrastructure, Transport and Tourism. The disaster information acquisition unit 211 can acquire, for example, disaster information by scraping the disaster prevention information page of a local government. The disaster information acquisition unit 211 can acquire, for example, observation values ​​from an earthquake sensor, a water level sensor, an anemometer, etc. as disaster information. The disaster information acquisition unit 211 may detect the occurrence of a disaster from messages posted on a social network such as X. If the disaster information meets certain criteria (for example, if the earthquake has a seismic intensity of 5 or higher, if a tsunami warning has been issued, or if a special heavy rain warning has been issued), a safety check will be carried out as described below.

[0019] The message sending unit 212 posts a chat message (hereinafter referred to as a safety confirmation message) for confirming safety so that it can be viewed by multiple users. The message sending unit 212 can send the safety confirmation message to a public channel, for example. The channel (or thread) to which the message sending unit 212 sends the safety confirmation message may be set in advance or may be designated by an administrator. The safety confirmation message can include an instruction to stamp the message once safety has been confirmed. The safety confirmation message can also include information that a disaster has occurred (for example, that an earthquake of a predetermined seismic intensity or greater has occurred).

[0020] The message sending unit 212 can also send a safety confirmation message to a visitor. The message sending unit 212 can send a safety confirmation message to a visitor as a message (second chat message) different from the safety confirmation message (first chat message) for the worker user. The message sending unit 212 can acquire the account name of a visitor who is present in the building, which is included in the visit information corresponding to the visitor, and send the safety confirmation message as a direct message addressed to the account name. The message sending unit 212 may send a chat message that mentions the account name of the visitor who is present in the building, which is included in the visit information corresponding to the visitor, to a channel in which the user of the account name participates.

[0021] The reaction acquisition unit 213 acquires reactions from each of a plurality of users to the safety confirmation message. The reactions can be stamps for the safety confirmation message. There can be a plurality of types of stamps, such as emoticons. The stamps attached to the safety confirmation message are linked to the account names that attached the stamps. The reaction acquisition unit 213 can acquire the account names that attached the stamps, for example, by inquiring of a server that provides a chat service.

[0022] The reaction acquisition unit 213 may acquire a reply to a safety confirmation message as a reaction to the safety confirmation message. For example, the reaction acquisition unit 213 may acquire, as a reaction, a chat message posted to a thread whose parent is a safety confirmation message posted to a channel. In this case, the reaction acquisition unit 213 acquires the account name of the poster of the chat message.

[0023] The safety determination unit 214 determines the safety of the user based on the response.

[0024] The safety determination unit 214 can determine, for example, that a user who has responded to a safety confirmation message (a user who has attached a stamp or a user who has sent a reply) is safe. The safety determination unit 214 can determine, for example, that a user who has responded to a safety confirmation message with a specific, previously set, indication that they are safe (a user who has attached a specific stamp indicating that they are safe) is safe. The stamp indicating safety can be set in advance.

[0025] The safety determination unit 214 can determine, for example, that the safety of a user who has not responded to a safety confirmation message has not been confirmed. Also, the safety determination unit 214 can determine, for example, that a user who has responded to the effect that some kind of problem has occurred (a user who has attached a stamp indicating that a specific problem has occurred) has a problem (has been affected by the disaster). In this case, the safety determination unit 214 may group users who have not responded to the safety confirmation message as "unresponsive" users.

[0026] The safety determination unit 214 can determine that a visitor is safe when there is a response from the visitor to a safety confirmation message sent to the visitor. The safety determination unit 214 can also determine that a visitor is safe when there is a response from a worker user to a safety confirmation message sent to the visitor. In this case, the safety determination unit 214 may determine that a visitor is safe when there is a response from a person in charge who is identified by user identification information included in the visit information corresponding to the visitor.

[0027] The safety determination unit 214 can output a list of users whose safety has been confirmed. For example, the safety determination unit 214 can acquire the account name related to the reaction, acquire user information corresponding to the acquired account name from the user information storage unit 231, and create a list of names included in the acquired user information as a list of users whose safety has been confirmed.

[0028] The safety determination unit 214 can also output a list of users whose safety cannot be confirmed. For example, the safety determination unit 214 can acquire user information stored in the user information storage unit 231, acquire account names related to reactions, and create a list of names included in the remaining user information as a list of users whose safety cannot be confirmed, excluding the user information corresponding to the acquired account names.

[0029] The safety determination unit 214 can transmit screen information to the user terminal 1 for displaying a list of users whose safety has been confirmed and / or users whose safety cannot be confirmed, and cause the user terminal 1 to display the list of users.

[0030] The safety tallying unit 215 can count the number of responses to the safety confirmation message as the number of safe users. The safety tallying unit 215 can tally the number of safe users (the number of responses) for each user department. The safety tallying unit 215 can, for example, identify the department to which the user belongs, which is identified by the user information corresponding to the account name related to the response, and perform tallying for each identified department.

[0031] The safety tallying unit 215 can also tally the number of users whose safety cannot be confirmed. The safety tallying unit 215 tally the number of user information stored in the user information storage unit 231 for each department, tally the total number of users belonging to the department, and subtract the number of safe users from the total number to determine the number of users whose safety cannot be confirmed.

[0032] The safety tallying unit 215 may tally visitors. For example, the safety tallying unit 215 can tally, for each person in charge or each department to which the person in charge belongs, the number of visitors who visited the person in charge or the department and are still in the building (have not left the building).

[0033] The safety tallying unit 215 can output the tally value. For example, the safety tallying unit 215 can transmit screen information for displaying the tally value to the user terminal 1, so that the tally value is displayed on the user terminal 1.

[0034] The schedule acquisition unit 216 acquires schedule information about the visitor in the building. For example, the schedule acquisition unit 216 can read visit information corresponding to the visitor from the visit information storage unit 232 and acquire the schedule information included in the read visit information. For example, the schedule acquisition unit 216 can access a server that provides a calendar service to acquire the visitor's schedule information. For example, the schedule acquisition unit 216 can receive schedule information from the person in charge who is scheduled to attend the visitor.

[0035] The presence determination unit 217 determines whether a visitor is present in the building based on the schedule information. The presence determination unit 217, for example, determines the end date and time of a scheduled event based on the schedule information. If the schedule information includes an end (planned) date and time, that date and time can be set as the end date and time. If the schedule information includes a start (planned) date and time and a planned time, the date and time after the planned start (planned) date and time can be set as the end date and time. If the end (planned) date and time is after the prediction target date and time (e.g., the current date and time), the presence determination unit 217 can determine that the visitor is present in the building. The presence determination unit 217 estimates the departure date and time based on the determined end date and time. The presence determination unit 217 may estimate the determined end date and time as the departure date and time, or may set a predetermined time after the determined end date and time as the departure date and time. Furthermore, if the schedule information includes the location of the event, such as conference room information, the departure time can be estimated based on the location, and the date and time after the departure time from the end date and time can be set as the departure date and time. For example, an exit time storage unit may be provided that stores standard exit times associated with information identifying locations within the building, such as conference rooms, and the presence determination unit 217 may read the exit time corresponding to the location included in the schedule information from the exit time storage unit. The presence determination unit 217 may also predict the exit date and time using a machine learning model. For example, the presence determination unit 217 may predict the exit time and obtain the exit date and time using a machine learning model created by machine learning using some or all of the following as training data: the location of the conference room, the scheduled time period, the person in charge, the department of the person in charge, the visitor, the visitor's company, the visitor's department, the number of participants in the meeting (which can be acquired from the schedule information), and the time from the end date and time of the schedule to the actual exit date and time (exit time). The presence determination unit 217 may determine that a visitor whose exit date and time is later than the date and time to be predicted (e.g., the current date and time) is present in the building.For example, the schedule acquisition unit 216 acquires visit information corresponding to the prediction target date (e.g., the current date) from the visit information storage unit 232, and the presence determination unit 217 estimates the departure date and time for each of the acquired visit information based on the schedule information included in the visit information, and determines whether the visitor indicated by the visitor identification information included in the visit information is present in the building based on whether the departure date and time is later than the prediction target date and time (e.g., the current date and time). The presence determination unit 217 may, for example, acquire location information from the visitor's mobile device and determine whether the visitor is present in the building based on the location information. Alternatively, the management server 2 may receive input that the visitor has left the building, and the input date and time may be acquired as the departure date and time.

[0036] The visitor output unit 218 outputs a list of visitors currently present in the building. The visitor output unit 218 can output a list of visitor identification information for visitors determined to be present by the presence determination unit 217. The visitor output unit 218 may output the number of visitors currently present in addition to or instead of the list of visitors. The visitor output unit 218 may refer to the visit information storage unit 232 to acquire user identification information for the visit destination included in the visit information corresponding to the visitor identification information, acquire user information corresponding to the user identification information from the user information storage unit 231, and output a list of visitors and / or the number of visitors for each user or each department of the user indicated by the acquired user information. The visitor output unit 218 may output the total number of visitors. The visitor output unit 218 may output the number of visitors currently present in the building tallied by visitor attributes (e.g., affiliated company, purpose of visit, etc.). The visitor output unit 218 may acquire location information of visitors who are present in the building and display it on a map. The visitor output unit 218 may also output schedule information of the visitors.

[0037] <Operation> FIG. 4 is a diagram illustrating the operation of the management server 2.

[0038] The management server 2 acquires disaster information (S301), and if the disaster information satisfies predetermined conditions (S302: YES), posts a safety confirmation message to a predetermined channel (S303), and determines the user's safety based on the user's response to the safety confirmation message (S304).

[0039] The management server 2 reads out the visit information stored in the visit information storage unit 232 (S305), estimates the departure date and time for each piece of visit information based on the schedule information included therein (S306), determines whether the visitor is present in the building based on whether the departure date and time is later than the current date and time (S307), and counts the number of visitors present in the building (S308).

[0040] The management server 2 counts and outputs the number of users whose safety has been confirmed and / or the number of users whose safety has not been confirmed for each department and the number of visitors (S309).

[0041] As described above, the information processing system of this embodiment makes it possible to check the safety of users based on the responses of multiple users to a single chat message. While it takes time and effort to individually receive and tally the responses to a safety check from users, the information processing system of this embodiment eliminates this time and effort. Furthermore, the information processing system of this embodiment can estimate the visitor's departure date and time based on the visitor's schedule information, determine whether the visitor is present in the building, and identify visitors who are present. This allows the safety of visitors to be checked as well.

[0042] Although the present embodiment has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention.

[0043] For example, the processing by each of the functional units of the management server 2 described above may be performed by any of the functional units. Also, a different functional unit that performs part of the processing by each of the functional units described above may be added. Also, the functional units of the management server 2 may be distributed across multiple computers.

[0044] Furthermore, the information stored in each storage unit of the management server may be stored in any of the storage units. That is, the information stored in the above-mentioned multiple storage units may be stored in one storage unit, or part of the information stored in one of the above-mentioned storage units may be stored in another storage unit.

[0045] In this embodiment, safety confirmation is performed based on reactions (stamps) to chat messages, but a safety confirmation message may be sent by email, short message service (SMS), or direct message on a social network other than a chat service, and safety confirmation may be performed based on the content of the reply to the safety confirmation message. In this case, safety may be determined to have been confirmed when there is a reply to the safety confirmation message, or the reply message may be analyzed to determine that safety has been confirmed or that a problem has occurred depending on whether the reply message states that the user is safe or that there is a problem.

[0046] In this embodiment, safety checks are performed based on reactions (stamps) to chat messages, but safety checks may also be performed by sending a safety check message to a social network (SNS) and based on reactions (stamps, comments, etc.) to the safety check message on the SNS.

[0047] In this embodiment, the presence determination unit 217 determines whether or not a visitor is present in the building, but it may also determine the probability that the visitor is present. The presence determination unit 217 can calculate the probability that the visitor will be present at the prediction target date and time (e.g., the current date and time) based on, for example, schedule information.

[0048] <Disclosures> The present disclosure also includes the following configurations. [Item 1] a schedule acquisition unit that acquires schedule information of visitors within the building; a presence determination unit that determines whether the visitor is present in the building based on the schedule information; a visitor output unit that outputs a list of the visitors who are present in the building; An information processing system comprising: [Item 2] Item 1, an information processing system according to item 1, the visitor output unit outputs the number of visitors present in the building; An information processing system characterized by: [Item 3] Item 1, an information processing system according to item 1, a sending unit that sends chat messages that can be viewed by a plurality of users to confirm the safety of the plurality of users; a reaction acquisition unit that acquires a reaction from each of the plurality of users to the chat message; a safety determination unit that determines the safety of the user depending on whether or not the user reacts; An information processing system comprising: [Item 4] Item 3. The information processing system according to item 3, the sending unit inquires about the visitor's safety using a second chat message different from the first chat message; the safety determination unit determines the safety of the visitor based on a response from the visitor or the user to the second chat message; An information processing system characterized by: [Item 5] Item 3. The information processing system according to item 3, a safety counting unit that counts the number of responses to the chat message as the number of users who are safe; An information processing system characterized by: [Item 6] Item 3. The information processing system according to item 3, the reaction is a stamp in response to the chat message; An information processing system characterized by: [Item 7] acquiring schedule information of the visitor within the facility; determining whether the visitor is present in the building based on the schedule information; outputting a list of the visitors present in the building; An information processing method characterized by being executed by a computer. [Item 8] acquiring schedule information of the visitor within the facility; determining whether the visitor is present in the building based on the schedule information; outputting a list of the visitors present in the building; A program that causes a computer to execute the following. [Explanation of symbols]

[0049] 1. User terminal 2 Management Server

Claims

1. a schedule acquisition unit that acquires schedule information of visitors within the building; a presence determination unit that determines whether the visitor is present in the building based on the schedule information; a visitor output unit that outputs a list of the visitors who are present in the building; An information processing system comprising:

2. 2. The information processing system according to claim 1, the visitor output unit outputs the number of visitors present in the building; An information processing system characterized by:

3. 2. The information processing system according to claim 1, a sending unit that sends chat messages that can be viewed by a plurality of users to confirm the safety of the plurality of users; a reaction acquisition unit that acquires a reaction from each of the plurality of users to the chat message; a safety determination unit that determines the safety of the user depending on whether or not the user reacts; An information processing system comprising:

4. 4. The information processing system according to claim 3, the sending unit inquires about the visitor's safety using a second chat message different from the first chat message; the safety determination unit determines the safety of the visitor based on a response from the visitor or the user to the second chat message; An information processing system characterized by:

5. 4. The information processing system according to claim 3, a safety counting unit that counts the number of reactions to the chat message as the number of users who are safe; An information processing system characterized by:

6. 4. The information processing system according to claim 3, the reaction is a stamp in response to the chat message; An information processing system characterized by:

7. acquiring schedule information of the visitor within the facility; determining whether the visitor is present in the building based on the schedule information; outputting a list of the visitors present in the building; An information processing method characterized by being executed by a computer.

8. acquiring schedule information of the visitor within the facility; determining whether the visitor is present in the building based on the schedule information; outputting a list of the visitors present in the building; A program that causes a computer to execute the following.

Citation Information

Patent Citations

  • Differential circuit

    JP1993007114A