JP2022052478A - Elevator management system and elevator operation management system - Google Patents

Abstract

To provide an elevator management system capable of preventing decrease in elevator operation efficiency due to a registration of a remote mischief call.SOLUTION: A center management system 4 has an abnormality detection part 46, a database registration part 47, and a personal terminal data determination part 44, where an abnormality detection part detects abnormality in which a user identified by a user ID at a landing floor registered by a remote call does not board the car dispatched to a landing floor, the database registration part registers data prohibiting the registration of the remote call including a user ID in a user ID database 53 when the number of detected abnormality occurrences exceeds a first threshold, and the personal terminal data determination part prohibits the remote call registration including the user ID when the user ID included in the remote call data corresponds to the user ID for which the remote call registration is prohibited.SELECTED DRAWING: Figure 1

Description

The present invention relates to an elevator management system and an elevator operation management system.

In recent years, users using elevators have been able to register calls (called "remote calls") created at places away from the platform for Units (for example, elevator halls) by operating personal terminals such as smartphones. It is possible. By the time the user who registered the call arrives at the platform, the car will be dispatched to the platform floor, so that the user can board immediately after arriving at the platform.

However, although a malicious user operated a personal terminal to register a remote call, a mischievous call that did not actually get on the unit sometimes occurred. When a mischievous call occurs, the unit is dispatched to the floor where the call is generated, even though the user does not actually board the unit. Even if a call is mistakenly registered, if this call is not canceled, the unit will be dispatched to the floor where the call is generated. Alternatively, if a malicious user gets in the car and then registers multiple destination floors, the car will frequently stop on the floor where no one gets off.

When a mischievous call is registered in this way, the operating efficiency of the elevator is significantly reduced, so it has been requested that appropriate measures be taken. For example, if it is possible to detect that the registered call is a mischievous call through a personal terminal, it is not necessary to dispatch the unit to the landing floor where the mischievous call is registered by controlling the call so that the call is not answered. In this way, various techniques for dealing with mischievous calls and erroneous registration of calls have been provided.

For example, Patent Document 1 describes that "a comparator is provided that outputs an output when the number of elevator destination registrations is larger than the weight inside the elevator car, and the registration of the elevator destination floor is canceled by the comparator output". ..

Further, in Patent Document 2, "when the selected elevator reaches the stop control point, a stop at a landing on a predetermined floor is input for other passengers who are not in the vicinity of the elevator selected by a person. If not, the stop at the platform will be cancelled. "

Japanese Unexamined Patent Publication No. 50-54055 Japanese Unexamined Patent Publication No. 2000-191245

The technique disclosed in Patent Document 1 cancels the mischievous call generated in the car. Therefore, it was not possible to deal with the prank call registered before the user boarded the unit.

Further, the technology disclosed in Patent Document 2 cancels the stop at the landing if the device is not near the landing after receiving a call from the personal information terminal device, thus preventing the registration of the destination floor. I was able to do that. However, the call itself can be registered even if the user is not necessarily around the landing. Also, in recent years, since location information can be sent by various methods, whether or not the information terminal device is near the landing is not a guide for determining whether or not the user actually gets on the machine. rice field.

The present invention has been made in view of such a situation, and an object of the present invention is, for example, to prevent a decrease in elevator operation efficiency due to registration of a mischievous call.

The elevator management system according to the present invention controls the operation of the elevator based on the data transmitted from the service request device capable of registering the remote call.
This elevator management system refers to the user ID database that stores the user ID that identifies the user who uses the service request device and the user ID database, and collates the user ID included in the remote call data received from the service request device. The matching unit, the abnormality detection unit that detects the abnormality that the user specified by the user ID on the landing floor registered by remote call did not get in the car assigned to the landing floor, and the abnormality detection unit detect it. The number of occurrences of anomalies is registered in the user ID database in association with the user ID, and when the number of occurrences of anomalies exceeds the first threshold, the data that prohibits the registration of remote calls including the user ID is stored in the user ID database. By referring to the database registration unit to be registered in the user ID database and the user ID database, it is determined whether the user ID included in the remote call data corresponds to the user ID for which the registration of the remote call is prohibited, and the user ID is remote. It is provided with a remote call determination unit that prohibits registration of a remote call including a user ID when it corresponds to a user ID for which registration of a call is prohibited.

According to the present invention, when the user ID included in the remote call data corresponds to the user ID for which the registration of the remote call is prohibited, the registration of the remote call including the user ID is prohibited. It is possible to prevent a decrease in elevator operation efficiency due to registration.
Issues, configurations and effects other than those described above will be clarified by the following description of the embodiments.

It is a block diagram which shows the whole structure example of the elevator management system which concerns on 1st Embodiment of this invention. It is a figure which shows the mode that the user which concerns on 1st Embodiment of this invention operates a personal terminal and registers a remote call. It is a figure which shows the structural example of the building database which concerns on 1st Embodiment of this invention. It is a figure which shows the structural example of the ID management database which concerns on 1st Embodiment of this invention. It is a figure which shows the structural example of the user ID database which concerns on 1st Embodiment of this invention. It is a figure which shows the structural example of the log database which concerns on 1st Embodiment of this invention. It is a figure which shows the example of the display screen of the personal terminal which is displayed when the determination result of the registered remote call which concerns on 1st Embodiment of this invention is normal. It is a figure which shows the example of the display screen of the personal terminal which is displayed when the determination result of the registered remote call which concerns on 1st Embodiment of this invention is abnormal. It is a flowchart which shows the example of the whole processing performed in the center management system which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the data reception processing which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the data authentication processing which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the data collation processing which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the personal terminal data determination processing which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the elevator data determination processing which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the abnormality data determination processing which concerns on 1st Embodiment of this invention. It is a flowchart which shows the example of the processing of the elevator operation management system performed when the remote call data is received from the personal terminal which concerns on 1st Embodiment of this invention via a center management system. It is a flowchart which shows the example of the processing of the elevator operation management system performed after the registration of the remote call which concerns on 1st Embodiment of this invention is completed. It is a block diagram which shows the hardware configuration example of the computer which concerns on 1st Embodiment of this invention. It is a figure which shows the mode that the user which concerns on the 2nd Embodiment of this invention operates a personal terminal and registers a remote call. It is a block diagram which shows the whole structure example of the elevator management system which concerns on 3rd Embodiment of this invention.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the accompanying drawings. In the present specification and the drawings, components having substantially the same function or configuration are designated by the same reference numerals, and duplicate description will be omitted.

[First Embodiment]
First, an overall configuration example and an operation example of the elevator management system according to the first embodiment of the present invention will be described.

FIG. 1 is a block diagram showing an overall configuration example of the elevator management system 1.
The elevator management system 1 includes a platform elevator service request device 2, a building management system 3, a center management system 4, an elevator operation management system 6, and a unit elevator control system 7-1 to a unit elevator control system 7-N.

The landing elevator service request device 2, the building management system 3, the center management system 4, and the elevator operation management system 6 are configured to be able to communicate with each other through a communication line N such as the Internet.

The platform elevator service request device 2 (an example of a service request device) is, for example, a smartphone, a tablet terminal, or the like used by a user. In the following description, the platform elevator service request device 2 is referred to as a "personal terminal". The user requests the elevator service by operating the personal terminal and registering the call before arriving at the elevator hall on the landing floor. A call in which the user operates and registers a personal terminal at a place away from the elevator hall on the landing floor is called a "remote call".

If the remote call is valid, the car will be dispatched to the landing floor in response to the call registered in the Unit Elevator Control System 7. Then, when the user arrives at the elevator hall on the landing floor, he / she can board the car that has already arrived at the landing floor. For this reason, compared to the conventional configuration in which the user registers the landing call after arriving at the elevator hall, in the configuration according to this embodiment, the call registration is possible in advance. There is no need to register the destination floor in the car, and the elevator can be requested only once by remote calling. In addition, the remote call may allow the user to register the destination floor through a personal terminal before boarding the car, or the remote call creates only a landing call, and the user gets in the car and then enters the car. You may register the destination floor by pressing the destination floor button of.

The building management system 3 manages air conditioning, lighting, etc. of the building (building) in which the elevator is installed.

The center management system 4 is provided in a center that remotely monitors elevators operated in a plurality of buildings. When the user registers the remote call, the data of this remote call is sent to the center management system 4. Then, the center management system 4 receives data transmitted from a personal terminal capable of registering a remote call, and controls the operation of the elevator based on this data. At this time, the center management system 4 authenticates the user who uses the personal terminal based on the remote call data received from the personal terminal, and transmits the determination result to the personal terminal. When the center management system 4 determines that the registered remote call is a legitimate call, the center management system 4 transfers the remote call to the elevator operation management system 6.

Further, when the center management system 4 receives the elevator data from the elevator operation management system 6, the center management system 4 determines the abnormality of the elevator data. The elevator operation management system 6 has a function of determining whether or not the remote call transferred from the center management system 4 can be correctly registered. Therefore, if the elevator data received from the elevator operation management system 6 contains information corresponding to the mischievous call, the center management system 4 identifies the user who registered the mischievous call, and the mischievous call is performed. Memorize the number of times, etc.

The elevator operation management system 6 manages the operation of the elevators performed by the unit 1 elevator control system 7-1 to the unit N elevator control system 7-N for each unit. This elevator operation management system 6 is installed in the same building together with the elevator, but may be installed in another building. In the following description, when the Unit 1 elevator control system 7-1 to the Unit N elevator control system 7-N are not distinguished, they are referred to as "Unit 1 elevator control system 7". The elevator operation management system 6 has a configuration in which a plurality of elevators are group-managed and controlled through a plurality of unit elevator control systems 7, but a single elevator is controlled through a single unit elevator control system 7. May be good. Alternatively, the function of the elevator operation management system 6 may be built in the unit elevator control system 7. Alternatively, the functions of the elevator operation management system 6 may be built in the building management system 3 and the center management system 4. Therefore, any system may realize the function of the operation management.

Then, the elevator operation management system 6 transmits the first notification data created based on the remote call data transferred from the center management system 4 to the unit elevator control system 7, and gives a control instruction to the unit elevator control system 7. conduct. On the other hand, the elevator operation management system 6 transmits the second notification data created based on the elevator operation data received from the unit elevator control system 7 to the center management system 4 as elevator data. The data notification means is not limited to this. For example, the elevator operation management system 6 may be a method of receiving and transmitting data via the unit elevator control system 7 without communicating with the center management system 4. Generally, in order to detect a failure of an elevator remotely, the unit elevator control system 7 may send and receive data to and from the center management system 4, so the infrastructure may be diverted. In this case, the remote calls transmitted from the Unit Elevator Control System 7 are once aggregated by the Elevator Operation Management System 6, analyzed from which platform floor the request was made from the aggregated results, and the calls are made based on the data. To create.

The unit elevator control system 7 controls the operation of the elevator based on the call registered in the elevator operation management system 6. For example, the Unit Elevator Control System 7 distributes the car to the landing floor requested by the user, moves the car to the destination floor desired by the user, and opens and closes the car door and the holder. .. Further, the unit elevator control system 7 transmits data including the operation result of the elevator to the elevator operation management system 6. This data includes information such as changes in the load in the car on the landing floor and the destination floor, the time when the car arrived on the landing floor and the destination floor, and the like.

Here, a state in which a user registers a remote call will be described.
FIG. 2 is a diagram showing a user operating a personal terminal to register a remote call. FIG. 2 focuses on the Unit 1 elevator control system 7-1 and shows how a user operates a personal terminal.

The Unit 1 elevator control system 7-1 controls the operation of an elevator composed of a car 71, a motor 72, and a rope 73. A load sensor 74 for detecting a load is provided on the car floor of the car 71. As for the operation of the elevator, at least the control of allocating the car 71 to the landing floor where the remote call is registered, the control of allocating the car 71 to the destination floor, and the control of opening and closing the car door of the car 71 and the holder on the landing floor are controlled. included.

Users can register remote calls before arriving at the elevator hall by operating their own personal terminals. A user ID that identifies the user is associated with the personal terminal.

The remote call data registered in the personal terminal is transmitted to the center management system 4 through the communication line N including the Wi-Fi (registered trademark), 4G line, and the like. The data of this call includes a user ID. Then, after undergoing predetermined processing by the center management system 4 and the elevator operation management system 6, if the remote call is registered by a legitimate user, the unit 1 elevator control system 7-1 dispatches the car 71 to the landing floor. .. However, even though the user has registered a remote call in the past, he / she did not get on the car 71, or even though he / she got on the car 71, he / she did not get off because he / she registered multiple destination floors. If so, it is probable that the user maliciously used the elevator. The use of such an elevator is also called "mischievous call". If mischief calls are made many times, the operating efficiency of the elevator will drop significantly. Therefore, the center management system 4 and the elevator operation management system 6 identify the user who registers the mischievous call and call the user's attention. It is also possible to control the user who frequently registered the mischievous call so that the registration of a new remote call is not accepted.

Returning to FIG. 1, the detailed configuration of the center management system 4 and the elevator operation management system 6 will be described.

<Center management system 4>
First, a detailed internal configuration example of the center management system 4 will be described.
The center management system 4 includes a receiving unit 41, an authentication unit 42, a collating unit 43, a personal terminal data determination unit 44, an elevator data determination unit 45, an abnormality detection unit 46, and a database registration unit 47 (in the figure, "DB registration unit"). Description), a transmission unit 48, a building database 51, an ID management database 52, a user ID database 53, and a log database 54. In the figure, the database is abbreviated as "DB".

The receiving unit 41 receives data from the personal terminal and the elevator operation management system 6. Here, the data transmitted from the personal terminal includes the data of the remote call. Further, the data transmitted from the elevator operation management system 6 includes information indicating that the elevator has been used correctly, information indicating that the remote call was NG, and the like. The data transmitted from the personal terminal and the elevator operation management system 6 to the center management system 4 are encrypted by a predetermined method. Therefore, the receiving unit 41 decodes the encrypted data and then outputs the decoded data to the authentication unit 42.

The authentication unit 42 authenticates the data input from the reception unit 41. A specified ID, password, and the like are set for the data transmitted and received between the personal terminal and the center management system 4, and between the center management system 4 and the elevator operation management system 6. For example, various general-purpose applications are installed on the personal terminal, and the application for registering a remote call is approved by, for example, a business operator operating the center management system 4.

Therefore, the authentication unit 42 authenticates whether the data received by the reception unit 41 from the personal terminal or the elevator operation management system 6 is the data transmitted from the application approved by the center management system 4. At the time of this authentication, for example, a process of determining whether or not the application IDs match, whether or not the passwords defined by the center management system 4 match, and the like are performed. The authentication unit 42 authenticates the remote call data transmitted from the personal terminal, and outputs the remote call data for which a positive authentication result in which the application ID and the password match is obtained to the collation unit 43. That is, if the authentication result is OK, it is found that the data is transmitted by the correctly authenticated sender, so that the data is connected to the next process. On the other hand, if the authentication result is NG, it is found that the data is transmitted by an unauthorized sender, so that the data cannot be connected after the next processing.

The collation unit 43 refers to the user ID database 53 based on the data authenticated by the authentication unit 42, and collates the user ID and the building ID included in the remote call data received from the personal terminal. At the time of this collation, the collation unit 43 may also refer to the building database 51 and the ID management database 52 as appropriate. In the present embodiment, the collation unit 43 will be described as collating the user ID and the building ID, but the collation unit 43 refers to the user ID database 53 based on the data authenticated by the authentication unit 42, and is an individual. It may be configured to collate only the user ID included in the remote call data received from the terminal. With this configuration, only the user ID needs to be stored in the user ID database 53. Then, the collation unit 43 distributes the data to the personal terminal data determination unit 44, the elevator data determination unit 45, or the abnormality detection unit 46 based on the collation result.

The personal terminal data determination unit 44 (an example of the remote call determination unit) refers to the user ID database 53 and determines whether the user ID included in the remote call data corresponds to the user ID for which registration of the remote call is prohibited. Is determined. Then, when the user ID corresponds to the user ID for which the registration of the remote call is prohibited, the personal terminal data determination unit 44 prohibits the registration of the remote call including the user ID. Specifically, the personal terminal data determination unit 44 does not allow the remote call including the user ID to be registered in the elevator operation management system 6 when the user ID corresponds to the user ID for which registration of the remote call is prohibited. .. A user specified by a user ID for which registration of remote calls is prohibited is called a "registration prohibited user". The registration prohibited user is a user whose user ID is registered in the prohibited list described later by registering a mischievous call many times in the past. Then, the personal terminal data determination unit 44 disallows the registration of the remote call from the personal terminal to the elevator operation management system 6 if the data is received from the personal terminal used by the registration prohibited user.

Then, when the personal terminal data determination unit 44 determines that the user ID included in the remote call data corresponds to the user ID for which registration of the remote call is prohibited, the elevator operation management system 6 for the personal terminal. Outputs information notifying that the remote call has not been registered (that is, the registration of the remote call is not permitted). This information is transmitted to the personal terminal by the transmission unit 48. On the other hand, the personal terminal data determination unit 44 registers the remote call to the elevator operation management system 6 with respect to the elevator operation management system 6 unless the data is the remote call data transmitted from the personal terminal used by the registration prohibited user. Create a message instructing.

The elevator data determination unit 45 determines whether the data (referred to as elevator data) received from the elevator operation management system 6 includes abnormal data indicating that the remote call data is abnormal. This elevator data is acquired from the unit elevator control system 7 and transmitted from the elevator operation management system 6 when the elevator whose remote call is registered in the elevator operation management system 6 is operated by the unit elevator control system 7. be. Then, when the elevator data includes the abnormality data, the elevator data determination unit 45 registers the number of times the abnormality data is received in the user ID database 53 in association with the user ID detected from the elevator data. Then, the elevator data determination unit 45 creates a message for the personal terminal including the determination result of the presence / absence of abnormal data.

The abnormality detection unit 46 is an abnormality in which the user specified by the user ID at the landing floor registered by remote call did not get in the car assigned to the landing floor based on the elevator data indicating the operation status of the elevator. Is detected. Further, the abnormality detection unit 46 describes an abnormality in which the user specified by the user ID registered for the destination floor did not get off from the car moved to the destination floor registered in the elevator operation management system 6 based on the elevator data. Also detect. Then, if the determination result shows an abnormality, the abnormality detection unit 46 registers the user ID of the user in the prohibition list according to the number of times of abnormality registration for each user. The prohibition list will be described in the user ID database 53 of FIG. 5, which will be described later. The user corresponding to the user ID registered in the prohibited list cannot register the remote call until the prohibited list is cleared.

The database registration unit 47 registers the number of occurrences of an abnormality in the user ID database 53 in association with the user ID. As described above, when an abnormality is detected in which the car is not boarded in the car assigned to the landing floor registered by the user, or when an abnormality is detected in which the car is not dismounted from the car moved to the destination floor registered by the user. The database registration unit 47 registers the number of times an abnormality has occurred.

The details of the building database 51, the ID management database 52, the user ID database 53, and the log database 54 will be described with reference to FIGS. 3 to 6 to be described later.

<Elevator operation management system 6>
Next, a detailed internal configuration example of the elevator operation management system 6 will be described.
The elevator operation management system 6 includes a receiving unit 61, an authentication unit 62, a call reception determination unit 63, an input consistency determination unit 64, a call registration unit 65, an arrival determination unit 66, a boarding / alighting detection unit 67, an erroneous operation detection unit 68, and notification data. It includes a creation unit 69 and a transmission unit 70.

The receiving unit 61 receives the remote call data transmitted from the user's personal terminal and transferred from the center management system 4. Then, the receiving unit 61 outputs the remote call data to the authentication unit 62. Further, when the receiving unit 61 receives the data related to the operation of the elevator from the unit elevator control system 7, the receiving unit 61 outputs this data to the erroneous operation detecting unit 68.

Of the configurations from the receiving unit 61 to the notification data creating unit 69, the authentication unit 62, the call acceptance determination unit 63, the input consistency determination unit 64, and the call registration unit 65 on the left side of the elevator operation management system 6 are center management systems. It is a functional unit executed when the data of the personal terminal transferred from 4 is received. On the other hand, the arrival determination unit 66, the boarding / alighting detection unit 67, and the erroneous operation detection unit 68 on the right side of the elevator operation management system 6 are functional units executed after the processing of the data of the personal terminal is completed.

(Functional part on the left side of the elevator operation management system 6)
First, a configuration example of the functional unit on the left side of the elevator operation management system 6 will be described.
The authentication unit 62 authenticates the remote call data as to whether it is the data transmitted from the personal terminal transferred from the center management system 4. For this authentication, an ID, a password, and the like defined between the center management system 4 and the elevator operation management system 6 are used.

If the call acceptance determination unit 63 has a positive authentication result (OK), the call acceptance determination unit 63 determines that the authenticated remote call data is the data transferred from the center management system 4. Therefore, the call acceptance determination unit 63 accepts the registered remote call and outputs the remote call data to the input consistency determination unit 64.

The input consistency determination unit 64 determines the consistency of the remote call data transferred from the center management system 4 and input from the call reception determination unit 63. The consistency determination process includes, for example, a process of determining whether the remote call data includes information on the floor on which the user can get on and off. Then, in the input consistency determination unit 64, the landing floor and the destination floor extracted from the remote call data are matched with the floor information of the building designated by the remote call, and the landing is extracted from the remote call data. It is determined that the floor or the destination floor matches the floor information on which the car can be dispatched, and the determination result is output to the call registration unit 65.

When the result of determining the consistency of the remote call data is positive, the call registration unit 65 determines the landing floor extracted from the remote call data for one unit selected based on the remote call data. Register the including call. In addition, the call registration unit 65 can also register a call including the destination floor extracted from the remote call data or registered in the car. Then, the call registration unit 65 outputs the information of the unit in which the call is registered to the notification data creation unit 69.

If the call registered by the call registration unit 65 is normal, the notification data creation unit 69 creates the first notification data to be transmitted to the unit elevator control system 7 based on the call registered by the call registration unit 65. On the other hand, the notification data creation unit 69 manages the center that the call could not be registered when the registered destination floor is the non-stop floor of the car or the consistency judgment is NG. Create the second notification data to be transmitted to the system 4.

Further, the notification data creation unit 69 outputs the first notification data created when the remote call is correctly registered by the call registration unit 65 to the unit elevator control system 7. In addition, the notification data creation unit 69 indicates that the landing floor and the destination floor do not match the floor information of the building specified by remote call, or the landing floor or the destination floor does not match the floor information on which the car can be dispatched. The second notification data created in is output to the center management system 4.

The transmission unit 70 transmits the first notification data or the second notification data created by the notification data creation unit 69 to the corresponding transmission destination. As described above, when the call registration unit 65 can register the call, the transmission unit 70 transmits the first notification data to the unit elevator control system 7. The Unit Elevator Control System 7 that has received the notification data dispatches a car to the landing floor based on the received first notification data. On the other hand, when the call registration unit 65 cannot register the call, the transmission unit 70 transmits the second notification data to the center management system 4. The center management system 4 that has received the second notification data notifies the personal terminal that the call could not be registered.

(Functional part on the right side of elevator operation management system 6)
Next, a configuration example of the functional unit on the right side of the elevator operation management system 6 will be described. In the figure, the arrival determination unit 66, the boarding / alighting detection unit 67, and the erroneous operation detection unit 68 are described side by side, but the arrival determination unit 66 and the boarding / alighting detection unit 67 operate at different timings, and the erroneous operation detection unit 68 operates. By receiving the results from the arrival determination unit 66 and the boarding / alighting detection unit 67, an erroneous operation is detected.

The arrival determination unit 66 determines that the car has arrived at the landing floor and that the car has arrived at the destination floor based on the operation data of the elevator and the call registered in the call registration unit 65. Then, the arrival determination unit 66 outputs the arrival determination result to the erroneous operation detection unit 68.

In the boarding / alighting detection unit 67, a user who has registered a remote call based on the elevator operation data has boarded the car at the platform floor registered by the call registration unit 65, or a user who has boarded the car has called. It is detected that the vehicle has disembarked from the car on the destination floor registered by the registration unit 65. The boarding / alighting detection unit 67 detects the user's boarding / alighting based on, for example, an increase / decrease in the value detected by the load sensor 74. Then, the boarding / alighting detection unit 67 outputs the boarding / alighting detection result to the erroneous operation detection unit 68.

Based on the arrival determination result of the arrival determination unit 66 and the boarding / alighting detection result of the boarding / alighting detection unit 67, the erroneous operation detection unit 68 indicates that the user has not been able to get on / off correctly on the landing floor and the destination floor registered by remote call. , Detected as a user error. Then, the erroneous operation detection unit 68 outputs the detection result to the notification data creation unit 69.

The notification data creation unit 69 creates the second notification data including the user ID that identifies the user in which the erroneous operation is detected, based on the detection result of the erroneous operation detection unit 68. If the detection result is no erroneous operation, the notification data creation unit 69 does not perform any processing. On the other hand, the notification data creation unit 69 creates the second notification data if it is a detection result with an erroneous operation.

The transmission unit 70 transmits the second notification data based on the detection result of the erroneous operation detection unit 68 to the center management system 4. By receiving the second notification data, the center management system 4 determines whether the user actually used the elevator, made an erroneous operation, or made a mischievous call.

<Database>
Next, the configuration of each database included in the center management system 4 will be described with reference to FIGS. 3 to 6.

<Building database>
FIG. 3 is a diagram showing a configuration example of the building database 51.
The building database 51 includes fields for a bank ID, a building name, a floor, and a target elevator management No. (number).

In the bank ID field, a bank ID for identifying a bank, which is an operating unit of the elevator, is stored. One or more banks are prepared in one building, and the bank ID is managed for each building.

In the building name field, the building name of the building where the elevator managed by the center management system 4 is installed is stored.
The floor managed by the bank ID is stored in the floor field.
In the target elevator management No. field, the management No. of the elevator managed by the center management system 4 is stored.
For example, in "○ Building", there are 4 floors with "B1, 1, 2, 3" on the floor managed by one bank ID "000001", and two elevators ("000001" and "000002"). Is shown to be managed.

<ID management database>
FIG. 4 is a diagram showing a configuration example of the ID management database 52.
The ID management database 52 includes a bank ID, a building ID for personal terminals, and floor fields.

The bank ID is stored in the bank ID field.
In the building ID field for personal terminals, the building ID associated with the user ID (personal terminal) is stored. For example, if the building is an office building, no one other than the employees of the company occupying the office building can enter the building. Therefore, a user ID is assigned to an employee of the company, and a specific building ID is associated with this user ID. This specific building ID is referred to as a "building ID for personal terminals".

In the floor field, the floor managed by the bank ID is stored for each building. The bank ID is managed for each building. For example, the bank ID "0000001" has the "B1, 1, 2, 3" floor as the operation unit, and the bank ID "0000002" has the "1, 2, 3, 4, 5" floor as the operation unit.

<User ID database>
FIG. 5 is a diagram showing a configuration example of the user ID database 53.
The user ID database 53 includes fields for user ID, building ID for personal terminals, abnormal registration, and registration prohibition.

The user ID field stores a user ID that uniquely identifies the user of the elevator.
The building ID for personal terminals is stored in the building ID field for personal terminals. If the user who uses the elevator uses only one personal terminal, there is a one-to-one correspondence between the user ID associated with the personal terminal and the building ID for the personal terminal.
In this way, the user ID database 53 stores the user ID that identifies the user who uses the personal terminal and the building ID that identifies the building in which the elevator is installed in association with each other.

In the abnormality registration field, when an abnormal boarding / alighting is detected for the remote call registered in the elevator operation management system 6, the number of abnormal registrations indicating that the abnormal remote call has been registered is stored.
In the registration prohibition field, when the number of abnormal registrations stored in the abnormal registration field exceeds the first threshold value (YES determination in step S68 of FIG. 15 described later), the user ID who registered this abnormal call is used. , Data indicating that registration of a new call is prohibited (for example, "1") is stored. In the following description, storing the data "1" in the registration prohibition field is also referred to as "registering in the prohibition list". If the value stored in the registration prohibition field is other than "0", the user specified by this user ID is restricted from registering the remote call using the personal terminal. For example, even if the user tries to register the remote call, a message indicating that the registration cannot be performed is displayed on the personal terminal. Even when the number of abnormal receptions temporarily exceeds the second threshold value (YES determination in step S56 of FIG. 14 described later), the user ID may be temporarily registered in the prohibition list. In this case, the registration to the prohibition list is canceled after a certain period of time has elapsed.

<Log database>
FIG. 6 is a diagram showing a configuration example of the log database 54.
The log database 54 includes fields for remote call registration time, user ID, building ID, landing floor, destination floor, registration status, and current state.

The remote call registration time field stores the call registration time when the user registered (created) the remote call.
In the user ID field, a user ID that identifies the user who registered the remote call is stored.
In the building ID field, a building ID that identifies the building in which the elevator in which the remote call is registered is installed is stored.
The landing floor field registered by the user by remote call is stored in the landing floor field.
The destination floor field stores the destination floor registered by the user by remote call or car call.

The registration status field stores the registration status of the elevator service provided to the user based on the registered remote call. If the user has successfully boarded and disembarked on either the landing floor or the destination floor registered by remote call, the ◯ mark is stored. On the other hand, if the user makes an abnormal boarding / alighting on either the landing floor or the destination floor registered by calling, the x mark is stored.

The current status field stores the current status of the elevator service, which details the contents of the registration status field. For example, in the record on the first line from the top (user ID: 000001, building ID: 1000001), the service provided to the remote call registered with the landing floor as the 3rd floor and the destination floor as the B1 floor is all provided. Since it was completed normally, a circle is stored in the registration status. In this case, the current state is Comp (abbreviation of Complete).

On the other hand, the record on the third line from the top (user ID: 000003, building ID: 1000001) is one of the services provided to remote calls registered with the landing floor as the third floor and the destination floor as the first floor. Indicates that the user did not board the car on the landing floor. Therefore, since the current state is Hall NG (abnormality occurs on the landing floor), a cross mark is stored in the registration status. The number of abnormal registrations "1" is added to the abnormal registration field of the user ID database 53 corresponding to the user ID recorded in this record.

The record on the 4th line from the top (user ID: 000004, building ID: 1000001) is one of the services provided for remote calls registered with the landing floor as the 2nd floor and the destination floor as the 1st floor. Indicates that the user who boarded on the landing floor did not get off on the destination floor. Therefore, since the current state is Desto NG (abnormality occurs on the destination floor), a cross mark is stored in the registration status. The number of abnormal registrations "1" is added to the abnormal registration field of the user ID database 53 corresponding to the user ID recorded in this record.

The record at the bottom (user ID: 000002, building ID: 1000002) represents the service performed for the remote call registered with the landing floor as the 4th floor and the destination floor as the 1st floor. , Indicates that the car has not been dispatched to the landing floor. Here, the user ID of the record on the second line from the top and the user ID of the record on the bottom have the same code (000002), but the building IDs are different, so that they represent different users. Then, since the current state is Non service (service not executed) and the execution status of the registered remote call is neither normal nor abnormal, a hyphen is stored in the registration status.

In the present embodiment, the building ID for personal terminals managed by the ID management database 52 and the building ID managed by the log database 54 are the same, but these IDs do not have to be the same.
For example, suppose the bank is divided into lower floors and higher floors. The bank ID is associated with each target floor on which the user can get on and off. In this case, a bank ID (1) for lower floors and a bank ID (2) for higher floors are set. Therefore, as the building ID for personal terminals, either the bank ID (1) or the bank ID (2) may be set. Alternatively, the bank ID (1A) may be set as the building ID for personal terminals by defining the bank ID (1A) that combines the bank IDs (1) and (2) into one. In this way, when setting one bank ID (1A) for the building ID for personal terminals, it is necessary to associate the bank ID for each target floor in the center management system 4. When a plurality of banks (for example, (1) and (2) described above) exist in one building, the building ID for personal terminals includes one building ID (for example, the above-mentioned (1A)) for a plurality of banks. )) May be associated only for personal terminals.

Further, in the ID management database 52 shown in FIG. 4, the B1 floor is a floor on which the user can get on and off if the bank ID is "000001". Therefore, the bank ID "000001" is set for the call that the user calls the B1 floor as the landing floor and the B1 floor as the destination floor.
Further, the 4th and 5th floors are floors where users can get on and off if the bank ID is "000002". Therefore, for example, the bank ID "000002" is set for the call with the 4th floor as the landing floor and the call with the 5th floor as the destination floor.
On the other hand, the first, second and third floors are floors on which the user can get on and off regardless of whether the bank ID is "000001" or "000002". Here, when registering the 1st floor, the 2nd floor, and the 3rd floor as the landing floor or the destination floor, the bank ID "000001" is set for the 1st floor, and the bank ID "000002" is set for the 2nd floor or the 3rd floor. May be associated so that "is set.

<Display screen of personal terminal>
Next, the display screen of the personal terminal on which the determination result of the remote call is shown will be described with reference to FIGS. 7 and 8.
FIG. 7 is a diagram showing an example of a display screen of a personal terminal displayed when the determination result of the registered remote call is normal.
If the remote call with the landing floor as the 1st floor and the destination floor as the 3rd floor is normal, the "Registration" in the center of the screen is checked, and the user knows that the remote call is correctly registered in the elevator operation management system 6. Shown.

FIG. 8 is a diagram showing an example of a display screen of a personal terminal displayed when the determination result of the registered remote call is abnormal.
If the judgment result of the remote call with the landing floor as the 1st floor and the destination floor as the 3rd floor is abnormal, it is not possible to register the remote call to the elevator operation management system 6 in "Registration" in the center of the screen. A cross mark indicating is displayed. For example, if the destination floor is a non-stop floor where the elevator service is not provided, or the user is registered in the prohibited list, the center management system 4 determines that the remote call cannot be registered. Then, the user is informed that the remote call could not be registered in the elevator operation management system 6.

<Processing of center management system 4>
Next, the processing of the center management system 4 will be described with reference to FIGS. 9 to 15.
FIG. 9 is a flowchart showing an example of the overall processing performed by the center management system 4 (described as “center overall processing” in the figure).

First, the receiving unit 41 performs a data receiving process of receiving the remote call data registered from the personal terminal or receiving the elevator data or the second notification data from the elevator operation management system 6 (S1). Next, the authentication unit 42 performs a data authentication process for authenticating each data received by the reception unit 41 (S2).

Next, the collation unit 43 performs a data collation process for collating each data authenticated by the authentication unit 42 (S3). Next, the personal terminal data determination unit 44 and the elevator data determination unit 45 perform data determination processing for determining data (S4).

Further, after collating the data by the collation unit 43 performed in step S3, the abnormality detection unit 46 detects the occurrence of an abnormality on the landing floor or the destination floor registered by remote call based on the elevator data. Data abnormality detection processing is performed (S5). When an abnormality in the data is detected, the database registration unit 47 registers the user ID associated with the generated abnormality in the user ID database 53 as abnormality ID data (S6).
After steps S4 and S6, the center management system 4 ends this process.

<Data reception processing>
FIG. 10 is a flowchart showing an example of the data reception process shown in step S1.
In the data reception process, the reception unit 41 performs the data reception process (S11). Next, the receiving unit 41 decodes the data (S12) and returns the result of this processing to the entire center processing (FIG. 9).

<Data authentication processing>
FIG. 11 is a flowchart showing an example of data authentication processing.
In the data authentication process, the authentication unit 42 extracts an ID from the data decrypted in the data reception process and performs the authentication process of this ID (S21). As described above, in the authentication process, it is determined whether or not the ID of the application approved by the business operator operating the center management system 4 matches the ID extracted from the data. Then, when the IDs match, the information indicating that the authentication result is OK is returned to the center-wide processing (FIG. 9).

In this authentication process, it may be determined whether or not the specified passwords match. In this case, if the ID and password match, the information indicating that the authentication result is OK is returned to the center-wide processing (FIG. 9).

<Data collation processing>
FIG. 12 is a flowchart showing an example of data collation processing.
In the data collation process, the collation unit 43 determines whether or not the input data is output from the personal terminal for the data whose authentication result is OK (input data input to the center management system 4). Judgment (S31). The input data output from the personal terminal and input to the center management system 4 in this way is called "personal terminal data".

When the input data is the personal terminal data output from the personal terminal (YES in S31), the collation unit 43 collates the personal terminal data (S32 to S34). At this time, the collation unit 43 refers to the user ID database 53 and collates the building ID for personal terminals extracted from the personal terminal data (S32). When the collation unit 43 determines that the building ID for personal terminals extracted from the personal terminal data is not stored in the user ID database 53, the subsequent processing is skipped, and the determination result of collation NG is processed for the entire center (FIG. 12). Return to.

On the other hand, when the collation unit 43 determines that the building ID for the personal terminal extracted from the personal terminal data is stored in the user ID database 53, the collation unit 43 further refers to the user ID database 53 and retrieves the user from the personal terminal data. The ID is collated (S33). In the collation process of step S33, for example, the information on the landing floor and the information on the destination floor input at the time of registration of the remote call are also collated. For example, if the input landing floor or destination floor is not a floor that can be moved by the user specified by the personal terminal, the determination result of collation NG is obtained. Then, if the collation result of the data taken out from the personal terminal data is NG, the collation unit 43 skips the subsequent processing and returns the determination result of the collation NG to the entire center processing (FIG. 12).

On the other hand, if the collation result of the data extracted from the personal terminal data is OK, the collation unit 43 performs the personal terminal data determination process shown in FIG. 13, which will be described later (S34). The personal terminal data determination process in step S34 corresponds to the data determination process in step S4 shown in FIG.

In step S31, when the input data is not the personal terminal data output from the personal terminal (NO in S31), this input data is the data transmitted from the elevator operation management system 6 to the center management system 4. Therefore, the processing (S35 to S39) after the NO determination in step S31 is to notify the personal terminal or determine the abnormal data.

The collation unit 43 refers to the user ID database 53 and collates the user ID extracted from the input data (S35). Next, the collation unit 43 performs collation processing of elevator data which is input data (S36).

Next, the collation unit 43 determines whether or not the input data includes the second notification data (S37). The second notification data is data including notification contents output from the elevator operation management system 6 to the personal terminal or the center management system 4. This notification content includes, for example, information indicating whether or not the elevator operation management system 6 has correctly registered the remote call.

Then, when it is determined that the input data includes the second notification data (YES in S37), the collation unit 43 performs the elevator data determination process shown in FIG. 14, which will be described later (S38). The elevator data determination process in step S38 corresponds to the data determination process in step S4 shown in FIG.

On the other hand, when the collation unit 43 determines that the input data does not include the second notification data (NO in S37), the input data includes the abnormality data, and therefore performs the abnormality data determination processing shown in FIG. 15, which will be described later. (S39). The abnormality data determination process in step S39 corresponds to the data abnormality detection process in step S5 and the error ID data registration process in step S6 shown in FIG.

<Personal terminal data judgment processing>
FIG. 13 is a flowchart showing an example of personal terminal data determination processing. This process is a process in which the personal terminal data determination unit 44 determines whether or not a remote call needs to be registered based on the personal terminal data.

First, the personal terminal data determination unit 44 performs a process of detecting a user ID from the personal terminal data (S41). Next, the personal terminal data determination unit 44 refers to the user ID database 53 and determines whether or not the user ID detected from the personal terminal data is registered in the prohibited list as a registration prohibited user (S42).

If the detected user ID is not registered as a registration prohibited user (NO in S42), the personal terminal data determination unit 44 sends the output data to be processed based on the personal terminal data in the processing of the subsequent step S44. Is performed (S43). The elevator operation management system 6 to which personal terminal data is transmitted differs depending on the elevator used by the user and the building in which the elevator is installed.

Next, the personal terminal data determination unit 44 performs a process of processing the output data to be transmitted to the elevator operation management system 6 selected in step S43 (S44). By this process, the output data includes information such as that the registered call is a remote call, the landing floor and the destination floor registered by the remote call, together with the user ID. Then, the personal terminal data determination unit 44 performs a process of transmitting output data for registering the output data in the elevator operation management system 6 (S45).

On the other hand, if the detected user ID in step S42 is a registration prohibited user (YES in S42), the personal terminal data determination unit 44 registers the remote call elevator operation management system 6 based on the personal terminal data. Performs a disapproval process (S46). Therefore, the output data processed based on the personal terminal data is not transmitted to the elevator operation management system 6.

On the other hand, it is necessary to inform the user who uses the personal terminal that the registration of the remote call to the elevator operation management system 6 is prohibited. Therefore, the personal terminal data determination unit 44 performs a process of transmitting output data including a message indicating that the registration of the remote call is disallowed to the personal terminal (S47).

<Elevator data judgment processing>
FIG. 14 is a flowchart showing an example of elevator data determination processing. This process is performed when the input data received from the elevator operation management system 6 is the second notification data (YES in step S37 in FIG. 12).

First, the elevator data determination unit 45 detects the user ID from the second notification data transmitted from the elevator operation management system 6 (S51). Next, the elevator data determination unit 45 determines whether or not the second notification data includes abnormal data (S52).

If the second notification data does not include the abnormality data (NO in S52), the elevator data determination unit 45 processes the second notification data transmitted from the elevator operation management system 6 (S53). Here, the processing of the second notification data will be described. For example, when the center management system 4 sends a character string to a personal terminal for a simple ID (“1”, “2” ...) Assigned by the elevator operation management system 6, a specified message is sent to each ID. Is assigned. For example, if the ID is "1", the message "Call has been registered." Is assigned. If the ID is "2", the message "The call could not be registered" is assigned, and if the ID is "3", the message "Please wait" is assigned. In this way, the elevator data determination unit 45 processes the message assigned to the ID into transmission data as a text message to be transmitted to the personal terminal.

In addition, the elevator data determination unit 45 assigns an image ID to each ID if there are three images displayed on the personal terminal by the function of the application installed on the personal terminal. For example, if the ID is "1", the image A is assigned, and if the ID is "2", the image B is assigned. In this way, the elevator data determination unit 45 processes the image information assigned to each ID into transmission data.

After the processing of step S53, the elevator data determination unit 45 performs processing to transmit the processed second notification data as transmission data from the transmission unit 48 to the personal terminal (S57).

On the other hand, if the elevator data includes abnormal data in step S52 (YES in S52), the elevator data determination unit 45 refers to the user ID database 53 and is associated with the user ID extracted from the elevator data. A process of counting the number of times of receiving abnormal data is performed (S54). In this process, the elevator data determination unit 45 registers the number of times of receiving abnormal data in the user ID database 53. In the user ID database 53, the number of times of receiving abnormal data is stored as the number of abnormal registrations.

Next, the elevator data determination unit 45 refers to the user ID database 53, and the number of times of receiving the abnormal data associated with the user ID extracted from the elevator data (described as "the number of abnormal times of the ID" in the figure) is determined. , It is determined whether or not the second threshold value has been exceeded (S55). The second threshold value is, for example, 5 times, but may be another value.

Then, if the number of times of receiving the abnormal data exceeds the second threshold value (YES in S55), the elevator data determination unit 45 shown in FIG. 1 temporarily registers the user ID in the prohibition list (S56). The registration prohibition field of the user ID database 53 corresponds to the prohibition list. Then, storing "1" in the registration prohibition field by the elevator data determination unit 45 is a process of registering the user ID in the prohibition list.

After step S56, the elevator data determination unit 45 performs a process of causing the transmission unit 48 to transmit transmission data including a message indicating that the user ID has been registered in the prohibition list to the personal terminal (S57). On the other hand, when the elevator data determination unit 45 determines that the number of times the abnormal data has been received does not exceed the second threshold value (NO in S55), the elevator data determination unit 45 transmits transmission data including a message indicating that the abnormal data has been received. A process of transmitting data from unit 48 to a personal terminal is performed (S57).

Here, the number of abnormal registrations stored in the user ID database 53 may be accumulated without defining a period, or may be cleared to zero in a predetermined period (for example, every month).

<Abnormal data judgment processing>
FIG. 15 is a flowchart showing an example of abnormality data determination processing. This process is performed when the input data received from the elevator operation management system 6 does not include the second notification data (NO in step S37 in FIG. 12). The center management system 4 can monitor the elevator operation status one by one by inputting elevator data from the elevator operation management system 6.

First, the abnormality detection unit 46 performs a process of detecting the landing floor and the destination floor from the input abnormality data (S61). Next, the abnormality detection unit 46 determines whether or not there is an unregistered user (S62). For example, a call was registered in the elevator operation management system 6, but as shown in the log database 54 of FIG. 6, the current state is "Non service" data, or the passenger boarded from the platform but did not arrive at the destination floor. The data indicating the user is the data of the unregistered user. When the abnormality detection unit 46 determines that there is no unregistered user (NO in S62), the abnormality detection unit 46 does not perform other processing and ends this processing.

On the other hand, when the abnormality detection unit 46 determines that there is an unregistered user (YES in S62), the abnormality detection unit 46 determines whether or not the user has boarded at the landing floor registered for the remote call (S63). For example, the abnormality detection unit 46 indicates that the load did not increase or decrease even though the car door and the holder were opened after the car arrived at the landing floor, based on the detection value of the load sensor 74, by the erroneous operation detection unit 68. Judgment is made based on the detection result detected by. If there is no increase or decrease in the load, it is considered that the user has registered the floor on which he / she does not plan to board in the remote call. Therefore, the abnormality detection unit 46 detects that an abnormality has occurred on the landing floor.

When the abnormality detection unit 46 determines that the user has boarded on the landing floor (YES in S63), the abnormality detection unit 46 determines whether or not the user has disembarked on the destination floor registered in the call (S64). For example, if the load does not decrease even though the car arrives at the destination floor, it is considered that the user has registered the floor on which he / she does not plan to disembark as the destination floor. Therefore, the abnormality detection unit 46 detects that an abnormality has occurred on the landing floor.

When the abnormality detection unit 46 determines that the user has disembarked at the destination floor (YES in S64), the database registration unit 47 registers data in the log database 54 and performs a process of updating the log database 54 (S65). After that, the abnormality detection unit 46 returns to the data collation process (FIG. 12).

Further, in step S63, when the abnormality detection unit 46 determines that the user is not on the landing floor (NO in S63), the abnormality detection unit 46 outputs the landing floor abnormality log (S67). The database registration unit 47 records the landing floor abnormality log in the log database 54. Further, in step S64, when the abnormality detection unit 46 determines that the user has not disembarked at the destination floor (NO in S64), the database registration unit 47 outputs the destination floor abnormality log to the log database 54 (S66). ).

After step S66 or S67, the abnormality detection unit 46 determines whether or not the number of abnormality registrations exceeds the first threshold value (S68). The first threshold value is, for example, 10 times, but may be another value.

If the number of abnormal registrations does not exceed the first threshold value (NO in S68), the process proceeds to step S70. On the other hand, if the number of abnormal registrations exceeds the first threshold value (YES in S68), the database registration unit 47 registers the user in the prohibition list (S69). In this way, storing "1" in the registration prohibition field of the user ID database 53 for the user ID of the user whose abnormal registration count exceeds the first threshold value is called "registering the user in the prohibition list".

After the NO determination in step S68 or the processing in step S69, the database registration unit 47 updates the log database 54 with an abnormal user (S70). Therefore, in the log database 54, predetermined values are stored in the registration status field and the current status field for the record added at the time of registration of the remote call.

<Processing of elevator operation management system 6>
Next, the processing of the elevator operation management system 6 will be described with reference to FIGS. 16 and 17.
FIG. 16 is a flowchart showing an example of processing of the elevator operation management system 6 performed when remote call data is received from a personal terminal via the center management system 4. This process is performed by each functional unit on the left side of the elevator operation management system 6 shown in FIG.

First, the receiving unit 61 receives the remote call data transmitted from the personal terminal via the center management system 4 (S81). Next, the authentication unit 62 authenticates the data received by the reception unit 61 (S82). For example, the authentication unit 62 authenticates whether the data is transmitted from the center management system 4 to the elevator operation management system 6 by using the ID, password, etc. detected from the data.

Next, the call acceptance determination unit 63 determines whether or not the authentication result of the data by the authentication unit 62 is OK (S83). If the authentication result is NG (NO in S83), the process proceeds to step S89.

On the other hand, if the authentication result is OK (YES in S83), the call acceptance determination unit 63 detects the landing floor, destination floor, and type information from the received remote call data (S84). The type information is information that requests the elevator operation management system 6 to operate the elevator exclusively when the user uses a wheelchair or is a VIP, for example.

Next, the input consistency determination unit 64 determines whether or not the information on the landing floor and the destination floor detected by the call reception determination unit 63 is included in the floor information existing in the elevator of the building where the remote call is registered. Judgment (S85). For example, in a 20-story building, the lower floors are divided into 1st to 10th floors, and the higher floors are divided into 11th to 20th floors. Here, even if the remote call includes information that the landing floor is the 1st floor and the destination floor is the 20th floor, the service of directly moving the car from the 1st floor to the 20th floor cannot be provided. In this case, it is determined that the information on the landing floor and the destination floor is not included in the floor information existing in the elevator of the building in which the remote call is registered. Then, when the information on the landing floor and the destination floor is not included in the floor information existing in the elevator of the building where the remote call is registered (NO in S85), the process proceeds to step S89.

On the other hand, for example, when the lower floors of the building are from the 1st floor to the 10th floor, if the 1st floor is registered on either the landing floor or the destination floor and the 5th floor is registered on the other floor, these floor information will be displayed. It is included in the floor information existing in the elevator of the building where the remote call is registered.

Therefore, if the remote call is included in the floor information existing in the elevator of the registered building (YES in S85), in the input consistency determination unit 64, the landing floor and the destination floor detected in step S84 are elevators. It is determined whether or not the service is separated from the target (S86). For example, if a specific floor without a tenant is on the 8th floor for security reasons, it may be set so that an unspecified user cannot get off on the 8th floor. In this case, even if the user registers the 8th floor as the destination floor, the car should not be stopped on the 8th floor. In this way, certain floors may be separated from the elevator service coverage. Therefore, if the landing floor or the destination floor registered by the personal terminal is separated from the target of the elevator service (NO in S86), the process proceeds to step S89.

On the other hand, if the landing floor and the destination floor registered by the personal terminal are not separated from the target of the elevator service (YES in S86), the call registration unit 65 registers the call of the elevator landing floor (S87). At this time, the call registration unit 65 may register the call to the unit designated by the personal terminal, and the time to dispatch the car from the elevators of a plurality of units existing in the building to the registered landing floor is the longest. You may select a short machine and register the call.

Next, the call registration unit 65 registers information on the destination floor of the elevator (S88). The information on the destination floor may be registered in the car or may be registered through a personal terminal.

After step S88 or after the NO determination in steps S83, S85, S86, the notification data creation unit 69 creates the first notification data or the second notification data (S89). The first notification data includes registration information. The registration information indicates that the call registration unit 65 has correctly registered the landing floor and the destination floor, and the notification data is transmitted to the unit elevator control system 7 of the corresponding unit.

The second notification data includes non-stop or consistency NG information. The non-stop information indicates that the car cannot stop on the floor because either the landing floor or the destination floor detected from the input data is a separate floor of the elevator service. Therefore, the second notification data including the non-stop information is returned to the center management system 4. Further, the information of consistency NG indicates that the elevator service cannot be provided because either the landing floor or the destination floor detected from the input data does not exist in the building where the remote call is registered. Therefore, the second notification data including the consistency NG information is also returned to the center management system 4.

After step S89, the transmission unit 79 transmits the first or second notification data to the unit elevator control system 7 or the center management system 4 (S90), and ends this process.

FIG. 17 is a flowchart showing an example of processing of the elevator operation management system 6 performed after the registration of the remote call is completed. That is, it is a process for actually operating the elevator in response to the call registered in the elevator operation management system 6. This process is performed by each functional unit on the right side of the elevator operation management system 6 shown in FIG. The following steps S91 to S96 are mainly executed by the erroneous operation detection unit 68, and the processing results of the arrival determination unit 66 and the boarding / alighting detection unit 67 are appropriately referred to.

First, the erroneous operation detection unit 68 determines whether or not there are still unexecuted or executed calls among the calls from the personal terminals normally registered in the elevator operation management system 6 in steps S87 and S88 of FIG. Judgment (S91). If there are no unexecuted or executing calls (NO in S91), the process proceeds to step S97.

On the other hand, if there are still unexecuted or executing calls (YES in S91), the erroneous operation detection unit 68 is determined by the recorded landing call based on the data acquired from the unit elevator control system 7 of the corresponding unit. It is determined whether or not the car has arrived at the landing floor (S92). Here, the erroneous operation detection unit 68 determines whether or not the car has arrived based on the determination result of the arrival determination unit 66. If the car has not arrived at the landing floor (NO in S92), the erroneous operation detection unit 68 returns to step S91 and repeats the process.

On the other hand, when the car arrives at the landing floor (YES in S92) and the destination floor is registered by the user who got in the car, the erroneous operation detection unit 68 sets the car on which the user got on the registered elevator destination floor. Instruct registration to the elevator control system 7 of the operated unit (S93).

Next, the erroneous operation detection unit 68 determines whether or not the user who gets in the car from the landing floor has been detected (S94). Here, the erroneous operation detection unit 68 determines whether or not the user has boarded the car based on the detection result of the boarding / alighting detection unit 67. If the erroneous operation detection unit 68 cannot detect that the user has boarded the car assigned to the landing floor (NO in S94), the erroneous operation detection unit 68 proceeds to step S97.

On the other hand, if the erroneous operation detection unit 68 can detect that the user has boarded the car assigned to the landing floor (YES in S94), the destination registered in step S93 based on the data acquired from the unit elevator control system 7. Detects whether or not a car has arrived on the floor (S95). Here, the erroneous operation detection unit 68 determines whether or not the car has arrived based on the determination result of the arrival determination unit 66. If the erroneous operation detection unit 68 cannot detect that the car has arrived at the registered destination floor (NO in S95), the erroneous operation detection unit 68 returns to step S91 and repeats the process.

On the other hand, if the erroneous operation detection unit 68 can detect that the car has arrived at the registered destination floor (YES in S95), it determines whether or not the user has detected the disembarkation at the destination floor where the car has arrived. Judgment (S96). Here, the erroneous operation detection unit 68 determines whether or not the user has disembarked from the car on the registered destination floor based on the detection result of the boarding / alighting detection unit 67.

If the erroneous operation detection unit 68 cannot detect that the user has disembarked from the car on the destination floor (NO in S96), the erroneous operation detection unit 68 moves to step S97. On the other hand, if the erroneous operation detection unit 68 can detect that the user has disembarked from the car on the destination floor (YES in S96), the notification data creation unit 69 creates the second notification data (S97). Here, the second notification data created includes at least one of two types of information (registration, NG). The registration information indicates that the call registration unit 65 has correctly registered the landing floor and the destination floor, and the second notification data is transmitted to the unit elevator control system 7 of the corresponding unit. The NG information indicates that the user has not boarded the car on the registered boarding floor or has not disembarked on the registered destination floor.

After step S97, the transmission unit 70 transmits notification data to the unit elevator control system 7 or the center management system 4 (S98), and ends this process.

<Hardware configuration of computer>
Next, the hardware configuration of the computer 100 constituting the center management system 4 and the elevator operation management system 6 will be described.
FIG. 18 is a block diagram showing a hardware configuration example of the computer 100. The computer 100 is an example of hardware used as a computer that can operate as the center management system 4 and the elevator operation management system 6 according to the present embodiment. In the elevator management system 1 (see FIG. 1) according to the present embodiment, the computer 100 (computer) of each system executes a program, and the functional blocks shown in FIG. 1 cooperate with each other to perform the elevator. Realize the operation management method.

The computer 100 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103, which are connected to the bus 104, respectively. Further, the computer 100 includes a non-volatile storage 105 and a network interface 106.

The CPU 101 reads the program code of the software that realizes each function according to the present embodiment from the ROM 102, loads it into the RAM 103, and executes it. Variables and parameters generated during the arithmetic processing of the CPU 101 are temporarily written in the RAM 103, and these variables and parameters are appropriately read out by the CPU 101. However, an MPU (Micro Processing Unit) may be used instead of the CPU 101. For example, the functions of each functional unit of the center management system 4 and the functions of each functional unit of the elevator operation management system 6 are realized by a program executed by the CPU 101.

As the non-volatile storage 105, for example, HDD (Hard Disk Drive), SSD (Solid State Drive), flexible disk, optical disk, optical magnetic disk, CD-ROM, CD-R, magnetic tape, non-volatile memory or the like is used. Be done. In the non-volatile storage 105, in addition to the OS (Operating System) and various parameters, a program for operating the computer 100 is recorded. The ROM 102 and the non-volatile storage 105 record programs, data, and the like necessary for the CPU 101 to operate, and as an example of a computer-readable non-transient storage medium that stores a program executed by the computer 100. Used. For example, each database included in the center management system 4 is composed of the non-volatile storage 105.

For the network interface 106, for example, a NIC (Network Interface Card) or the like is used, and various data can be transmitted and received between the devices via a LAN (Local Area Network) connected to a terminal of the NIC, a dedicated line, or the like. It is possible. For example, the functions of the receiving unit 41 and the transmitting unit 48 of the center management system 4, the receiving unit 61 and the transmitting unit 70 in the elevator operation management system 6 are realized by the network interface 106.

In the elevator management system 1 according to the first embodiment described above, a user can operate a personal terminal to register a remote call. Here, if the user does not board the car on the registered boarding floor or disembark from the car arriving at the registered destination floor even though the user has registered the remote call, a mischievous call occurs. It is determined that it has been done. Then, the number of registrations of the mischievous call by the user who registered the remote call is recorded. When the number of registrations of mischievous calls exceeds the first threshold value, the user ID of this user is registered in the prohibition list to prohibit the registration of new calls by this user. Therefore, by registering the mischievous call, it is possible to prevent the elevator operation efficiency from being lowered due to the dispatch of the car. Also, for other users who do not make mischievous calls, the car will not stop on the floor where no one gets on or off, so the car will move smoothly to the target destination floor. Therefore, the usability is improved when using the elevator.

When a user ID is registered in the prohibited list, remote calls from personal terminals associated with this user ID will not be accepted for a certain period of time. After a certain period of time, remote call registration may be accepted from this personal terminal, but if the number of abnormal registrations exceeds a predetermined first threshold due to cumulative mischievous calls being registered, this user The ID may be re-registered in the prohibition list and the user ID may be permanently frozen. In this case, the user whose user ID is permanently frozen cannot register the remote call, so that the other user who does not make a mischievous call can continue to use the elevator, which is the original purpose.

In the elevator management system 1 according to the first embodiment, for example, the call registration by the general landing button and the car call button provided in the elevator hall is not a target for determining the mischievous call. To the last, when it is detected that the remote call has been canceled after the car has been dispatched by the remote call registered by the user, this user ID is abnormally registered by sending the user ID to the center management system 4. ..

[Second Embodiment]
Next, an overall configuration example and an operation example of the elevator management system according to the second embodiment of the present invention will be described. In the elevator management system according to the first embodiment, the user is not detected in the car, but in the elevator management system according to the second embodiment, the user is detected in the landing and the car. ..

FIG. 19 is a diagram showing a state in which a user operates a personal terminal to register a remote call.
Here, a landing camera 81 is installed at the landing on each floor, and a camera 82 inside the car is installed at the car 71. The landing camera 81 has a function of detecting a user at the landing by photographing the landing, and is used as an example of a first user detection unit. Further, the in-car camera 82 has a function of detecting a user who has boarded the car by photographing the inside of the car, and is used as an example of a second user detection unit.

Then, the boarding / alighting detection unit 67 detects a user at the landing, a user who got into the car from the landing, and a user who got off the car based on the image acquired from the landing camera 81. Here, the user at the landing is recognized as the user ID registered on the landing floor. Further, the boarding / alighting detection unit 67 detects a user in the car while the car is moving, based on the image acquired from the camera 82 in the car. Here, the user in the car is recognized as the user ID registered on the destination floor.

Then, when the erroneous operation detection unit 68 detects that the user does not get in the car even though the call of the landing floor is registered based on the image acquired from the landing camera 81, the erroneous operation detection unit 68 detects it as a user's erroneous operation. Then, the erroneous operation detection unit 68 transmits the erroneous operation detection result including the user ID of the erroneous operation user to the center management system 4. Further, when the erroneous operation detection unit 68 detects that the user does not get off the car even though the call of the destination floor is registered based on the image acquired from the landing camera 81 or the camera in the car 82, the user Detected as an erroneous operation. Then, the erroneous operation detection unit 68 transmits the erroneous operation detection result including the erroneous operation user ID to the center management system 4. Therefore, the center management system 4 can detect the mischievous call of the user based on the detection result. Then, the abnormality detection unit 46 can correctly register the abnormality of the user who made the mischievous call and register it in the prohibition list.

As the second user detection unit, not only the landing camera 81 and the in-car camera 82 described above but also the load sensor 74 may be used in combination. The boarding / alighting detection unit 67 obtains an increase / decrease in the load by dividing the load value detected by the load sensor 74 by the weight value of a general adult male (for example, 60 kg), and obtains the number of users who get on / off the car. Can be done. If the boarding / alighting detection unit 67 does not detect boarding or disembarking from the car on the registered boarding floor or destination floor based on the load value detected by the load sensor 74, the erroneous operation detecting unit 68 detects as an erroneous operation of the user specified by the user ID associated with the personal terminal, and then transmits the detection result to the center management system 4.

When the user registers the remote call, the user ID associated with the personal terminal and the password sent by the center management system 4 to the personal terminal registered in advance by short message or the like are transmitted from the personal terminal. Two-step verification that uses the input for the authentication process may be used together. By such a process, a mischievous call is registered from an unspecified personal terminal, and it is possible to avoid a situation in which a car is dispatched to a landing floor where no one is present. Alternatively, the center management system 4 may manage the user ID in association with information (MAC address) unique to the personal terminal, and specify the user ID by a plurality of information.

[Third Embodiment]
Next, an overall configuration example and an operation example of the elevator management system according to the third embodiment of the present invention will be described. In the elevator management system according to the third embodiment, the same processing as the elevator management system according to the first embodiment is applied to the elevators that are not controlled by group management.

FIG. 20 is a block diagram showing a configuration example of the elevator management system 1A according to the third embodiment.
The elevator management system 1A includes a landing elevator service request device 2, a building management system 3, an elevator operation management system 6A, and a unit 1 elevator control system 7-1.

The main configuration of the elevator operation management system 6A is realized by combining the center management system 4 and the elevator operation management system 6 according to the first embodiment. However, the first processing unit 111 excluding the receiving unit 41 and the transmitting unit 48 of the center management system 4 and the second processing unit 112 excluding the receiving unit 61 and the transmitting unit 70 of the elevator operation management system 6 are operated by an elevator. Data is input and output from each other inside the management system 6A. The elevator operation management system 6A is provided with a receiving unit 110 that receives data from an external device or system, and a transmitting unit 113 that transmits data to the external device or system.

The landing elevator service request device 2 transmits the registered remote call data via the network N. Then, the receiving unit 110 receives the remote call data and outputs the remote call data to the first processing unit 111. The first processing unit 111 and the second processing unit 112 can refer to the data in the process of processing with each other.

The transmission unit 113 transmits the call data normally registered by the second processing unit 112 to the unit 1 elevator control system 7-1. Further, the transmission unit 113 indicates that the remote call could be normally registered to the landing elevator service request device 2, or that the remote call could not be registered because the user was registered in the prohibition list. To send.

Further, if the elevator operation management system 6A is provided in the building where the Unit 1 elevator control system 7-1 is installed, it is not necessary to provide the building ID field in each database. Further, the elevator operation management system 6A may be configured by removing the building database 51.

In the elevator management system 1A according to the third embodiment described above, the elevator operation management system 6A that manages the operation of the elevator of the single unit is configured to include the first processing unit 111 and the second processing unit 112. It is a thing. Then, in the first embodiment, the center management system 4 and the elevator operation management system 6 process the data communicated with each other, whereas the processing can be executed inside the elevator operation management system 6A. .. The elevator operation management system 6A may be configured to include a plurality of unit elevator control systems 7 for group management and control of a plurality of units.

It should be noted that the present invention is not limited to the above-described embodiments, and it goes without saying that various other application examples and modifications can be taken as long as they do not deviate from the gist of the present invention described in the claims.
For example, each of the above-described embodiments describes the configurations of the apparatus and the system in detail and concretely in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to those including all the described configurations. Further, it is possible to replace a part of the configuration of the embodiment described here with the configuration of another embodiment, and further, it is possible to add the configuration of another embodiment to the configuration of one embodiment. It is possible. Further, it is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration. Specifically, each system requires an elevator operation management system 6, a unit elevator control system 7, and a center management system 4 to manage user IDs, detect mischief calls, and detect passengers. Although it has been explained that detection / management is performed, it is also easy to integrate these as one elevator management system 1. In this case, only the building information containing the system is stored in the building database 51. Alternatively, a configuration without the building database 51 itself can be considered. In a configuration without the building database 51 itself, there is no information associated with the building ID from the data transmitted from the landing elevator service request device 2. This is because when the landing elevator service request device 2 and the data request destination are determined, it is determined which building the request is for. However, if there are a plurality of elevators in the building, a similar building database may be provided, a plurality of related elevator groups may be defined as one bank, and IDs may be managed for each bank ID. Alternatively, a method may be used in which data is transmitted / received to the bank corresponding to the target landing floor or destination floor.

Further, although each system is provided with a receiving unit / transmitting unit for transmitting and receiving data to and from each other, it may be integrated into one system or a receiving unit / transmitting unit may be provided. Alternatively, it may be in the form of storing / accessing data in the internal memory.
Further, for a remote call, the center management system 4 manages input / output, manages a user who has generated a large number of mischievous calls, and restricts the input of the user, but the embodiment is not limited to these. A data table is provided in the landing elevator service request device 2 which is an input terminal for remote calls, for example, a counter for clearing every day is provided, and the counter feeds back the number of detections of mischievous calls obtained from the elevator side. It is a method to do. In this way, when the counter exceeds the threshold value, the input from the landing elevator service request device 2 to the elevator management system 1 may be restricted.

Each data table and database is stored in ROM (Read Only Memory) or storage for implementation, and the flow chart is executed by CPU (Central Processing Unit) and data is stored in RAM (Random Access Memory) that is temporarily stored. By storing and accessing the data, input / output data processing can be executed. In input / output communication, there are many cases where Ethernet (registered trademark) or wireless communication path is adopted, but there is no problem depending on the amount of data even if it is executed by serial communication. Each system shown in this implementation can be realized by storing data in a similar ROM / storage, executing processing on the CPU, and temporarily storing / accessing the RAM. Therefore, it is possible to implement these systems even if they are separated by function, and it is possible to integrate them and omit each management table.
In addition, the control lines and information lines indicate what is considered necessary for explanation, and do not necessarily indicate all the control lines and information lines in the product. In practice, it can be considered that almost all configurations are interconnected.

1,1A ... Elevator management system, 2 ... Platform elevator service request device, 4 ... Center management system, 6,6A ... Elevator operation management system, 7 ... Unit elevator control system, 41 ... Receiver unit, 42 ... Authentication unit, 43 ... Collation unit, 44 ... Personal terminal data judgment unit, 45 ... Elevator data judgment unit, 46 ... Abnormality detection unit, 47 ... Database registration unit, 48 ... Transmission unit, 51 ... Building database, 52 ... ID management database, 53 ... User ID Database, 54 ... Log database, 61 ... Receiving unit, 62 ... Authentication unit, 63 ... Call acceptance determination unit, 64 ... Input consistency determination unit, 65 ... Call registration unit, 66 ... Arrival determination unit, 67 ... Boarding / alighting detection unit, 68 ... erroneous operation detection unit, 69 ... notification data creation unit, 70 ... transmission unit

Claims (12)

In an elevator management system that controls the operation of an elevator based on data transmitted from a service request device that can register remote calls.
A user ID database that stores user IDs that identify users who use the service request device, and
A collation unit that refers to the user ID database and collates the user ID included in the remote call data received from the service requesting device.
An abnormality detection unit that detects an abnormality in which the user specified by the user ID on the landing floor registered by the remote call did not get in the car assigned to the landing floor.
The number of occurrences of the abnormality detected by the abnormality detection unit is registered in the user ID database in association with the user ID, and when the number of occurrences of the abnormality exceeds the first threshold value, the user ID is included. A database registration unit that registers data that prohibits registration of remote calls in the user ID database,
With reference to the user ID database, it is determined whether the user ID included in the remote call data corresponds to the user ID for which registration of the remote call is prohibited, and the user ID is the remote call. An elevator management system including a remote call determination unit that prohibits registration of the remote call including the user ID when the user ID is prohibited. A center management system that receives the data transmitted from the service request device, an elevator operation management system that manages the operation of the elevator, and an elevator control system that controls the operation of the elevator are provided.
The center management system includes the user ID database, the collation unit, the abnormality detection unit, the database registration unit, and the remote call determination unit.
The user ID database stores the user ID in association with the building ID that identifies the building in which the elevator is installed.
The collation unit refers to the user ID database and collates the user ID and the building ID included in the remote call data received from the service request device.
When the user ID included in the remote call data corresponds to the user ID for which registration of the remote call is prohibited, the remote call determination unit may perform the remote call including the user ID. The elevator management system according to claim 1, which is not registered in the elevator operation management system. The abnormality detection unit is acquired from the elevator control system and transmitted from the elevator operation management system when the elevator whose remote call is registered in the elevator operation management system is operated by the elevator control system. The user specified by the user ID who registered the destination floor did not get off from the car which moved to the destination floor registered in the elevator operation management system based on the elevator data indicating the operation status of the elevator. The elevator management system according to claim 1 or 2, wherein the database registration unit registers the number of occurrences of the abnormality in the user ID database in association with the user ID even when the abnormality is detected. When the remote call determination unit determines that the user ID included in the remote call data corresponds to the user ID for which registration of the remote call is prohibited, the elevator for the service request device. The elevator management system according to claim 3, which outputs information notifying that the remote call has not been registered in the operation management system. The center management system is
It is determined whether the elevator data includes abnormal data indicating that the remote call data is abnormal, and when the elevator data includes the abnormal data, the number of times the abnormal data is received is determined. The elevator management system according to claim 4, further comprising an elevator data determination unit that is associated with the user ID detected from the elevator data and registered in the user ID database. The center management system is
The elevator according to claim 5, further comprising an authentication unit that authenticates the remote call data transmitted from the service request device and outputs the remote call data for which a positive authentication result is obtained to the collation unit. Management system. The elevator operation management system transmits the first notification data created based on the remote call data transferred from the center management system to the elevator control system, gives a control instruction to the elevator control system, and performs the control instruction to the elevator control system. The elevator management system according to any one of claims 1 to 6, wherein the second notification data created based on the operation data of the elevator received from the elevator control system is transmitted to the center management system as the elevator data. The elevator operation management system is
An integrity determination unit that determines the integrity of the remote call data transferred from the center management system, and
When the result of determining the consistency of the remote call data is affirmative, the call including the landing floor extracted from the remote call data and the call including the remote call data are extracted from the remote call data or registered in the car. A call registration unit that registers calls that include the destination floor
The elevator management system according to claim 7, further comprising a notification data creation unit that creates the first notification data to be transmitted to the elevator control system based on the call registered by the call registration unit. The consistency determination unit extracts from the data of the remote call that the landing floor and the destination floor extracted from the data of the remote call are consistent with the floor information of the building designated by the remote call. It is determined that the landing floor or the destination floor is consistent with the floor information on which the car can be dispatched, and the determination result is output to the call registration unit.
The notification data creation unit outputs the first notification data created when the remote call is correctly registered by the call registration unit to the elevator control system, and the landing floor and the destination floor are the remote call. The second notification data created when it does not match the floor information of the building specified in, or when the landing floor or the destination floor does not match the floor information on which the car can be dispatched, is sent to the center management system. The elevator management system according to claim 8 to be output. The elevator operation management system is
Based on the operation data and the call registered in the call registration unit, an arrival determination unit that determines that the car has arrived at the landing floor and that the car has arrived at the destination floor.
The user who has registered the remote call has boarded the car at the landing floor registered by the call registration unit, or the user who has boarded the car has been registered by the call registration unit. A boarding / alighting detection unit that detects that the vehicle has disembarked from the car on the destination floor,
Based on the determination result of the arrival determination unit and the detection result of the boarding / alighting detection unit, the user cannot get on / off correctly at the landing floor and the destination floor registered by the remote call. It has an erroneous operation detection unit that detects as an erroneous operation.
The elevator management system according to claim 9, wherein the notification data creating unit creates the second notification data including the user ID that identifies the user in which the erroneous operation is detected. The boarding / alighting detection unit is based on the detection result of the first user detection unit that detects the user on the landing floor and the detection result of the second user detection unit that detects the user who got in the car. The elevator management system according to claim 10, wherein the elevator detects getting on the car from the car and getting off the car from the car to the landing. In an elevator operation management system that receives data transmitted from a service request device that can register remote calls and manages elevator operations.
A user ID database that stores user IDs that identify users who use the service request device, and
A collation unit that refers to the user ID database and collates the user ID included in the remote call data received from the service request device.
An abnormality detection unit that detects an abnormality in which the user specified by the user ID on the landing floor registered by the remote call did not get in the car assigned to the landing floor.
The number of occurrences of the abnormality detected by the abnormality detection unit is registered in the user ID database in association with the user ID, and when the number of occurrences of the abnormality exceeds the first threshold value, the user ID is included. A database registration unit that registers data that prohibits registration of remote calls in the user ID database,
With reference to the user ID database, it is determined whether the user ID included in the remote call data corresponds to the user ID for which registration of the remote call is prohibited, and the user ID is the remote call. An elevator operation management system including a remote call determination unit that prohibits registration of the remote call including the user ID when the user ID is prohibited.

Images