Remote monitoring system for elevator, user management method in remote monitoring system for elevator, and storage medium

Abstract

Provided is a remote monitoring system capable of easily performing monitoring work of an elevator, and a user management method and a user management program thereof. The remote monitoring system (1) includes a registration receiving unit (13) and a setting unit (14). The registration receiving unit (13) receives registration information. The registration information indicates registration of a second user who is a child user of a first user registered in a user management table. In the first table, each of a plurality of users is associated with a monitoring range that the user can view. The setting unit (14) sets the monitoring range that the second user who is a child user of the first user can view to a range that does not exceed the viewable monitoring range associated with the first user in the user management table when the registration receiving unit (13) receives the registration information.

Description

Technical Field

[0001] This invention relates to a remote monitoring system for elevators, a user management method within the remote monitoring system for elevators, and a storage medium. Background Technology

[0002] Patent document 1 discloses an example of a remote monitoring system for elevators. In the remote monitoring system, it is determined whether the user requesting to view the monitoring data is an authenticated user.

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent No. 4826687 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] In this case, within the remote monitoring system for elevators, the operator performing the monitoring work sometimes delegates the task to another operator. In such situations, there is a possibility that the operator delegating the task may be authorized to view the monitoring data, while the operator delegating the task may not be. In the remote monitoring system of Patent Document 1, in order for the operator delegating the task, a newly certified user must be registered to view the monitoring data. Therefore, it is sometimes not easy to delegate the monitoring work.

[0008] This invention was made to solve such a problem. This invention provides a remote monitoring system capable of easily performing elevator monitoring operations, a user management method thereof, and a storage medium storing the user management program.

[0009] Methods for solving problems

[0010] The remote monitoring system for elevators of the present invention comprises: a registration acceptance unit that accepts registration information representing the registration of a second user, the second user being a sub-user of a first user registered in a first table, wherein each of a plurality of users is associated with a monitoring range that each user can view; and a setting unit that, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, as a sub-user of the first user, can view to not exceed the range of the monitoring range that is associated with the first user in the first table.

[0011] The remote monitoring system for elevators of the present invention comprises: a storage unit that stores a first table that establishes a correspondence between each user among a plurality of users and the monitoring range that each user can view; a registration acceptance unit that accepts registration information indicating the registration of a second user, the second user being a sub-user of the first user registered in the first table; and a setting unit that, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, as a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view.

[0012] The remote monitoring system for an elevator of the present invention comprises: a registration acceptance unit that accepts registration information indicating the registration of a second user, the second user being a sub-user of a first user registered in a first table, wherein each of a plurality of users is associated with a monitoring range that each user can view; a setting unit that, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, as a sub-user of the first user, can view to not exceed the range of the monitoring range that is associated with the first user in the first table; and a storage unit that stores a second table, wherein the monitoring range that is associated with the sub-user registered according to the registration information is associated with the sub-user.

[0013] The user management method in the remote monitoring system of the elevator of the present invention includes: a registration acceptance step, which accepts registration information indicating the registration of a second user, the second user being a sub-user of a first user registered in a first table, wherein each user among a plurality of users is associated with a monitoring range that each user can view in the first table; and a setting step, which, based on the registration information accepted in the registration acceptance step, sets the monitoring range that the second user, as a sub-user of the first user, can view to not exceed the range of the monitoring range that is associated with the first user in the first table.

[0014] The storage medium of the present invention stores a user management program that enables a remote monitoring system for an elevator to perform the following steps: a registration acceptance step, which accepts registration information indicating the registration of a second user, who is a sub-user of a first user registered in a first table, in which each of a plurality of users is associated with a monitoring range that each user can view; and a setting step, which, based on the registration information accepted in the registration acceptance step, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range of the monitoring range that is associated with the first user in the first table.

[0015] Invention Effects

[0016] If the remote monitoring system of the present invention, or its user management method, or a storage medium storing the user management program is used, then the monitoring operation of the elevator can be easily performed. Attached Figure Description

[0017] Figure 1 This is a structural diagram of the remote monitoring system according to Implementation Method 1.

[0018] Figure 2 This is a diagram showing an example of a monitoring data table stored in the storage unit of Embodiment 1.

[0019] Figure 3 This is a diagram showing an example of a user management table stored in the storage unit of Embodiment 1.

[0020] Figure 4 This is a diagram showing an example of a sub-user management table stored in the storage unit of Embodiment 1.

[0021] Figure 5 This is a diagram showing an example of a display in the monitoring terminal of the remote monitoring system according to Embodiment 1.

[0022] Figure 6 This is a diagram showing an example of a display in the monitoring terminal of the remote monitoring system according to Embodiment 1.

[0023] Figure 7 This is a diagram illustrating an example of a table processed in the remote monitoring system of Embodiment 1.

[0024] Figure 8 This is a diagram illustrating an example of a table processed in the remote monitoring system of Embodiment 1.

[0025] Figure 9 This is a diagram illustrating an example of a table processed in the remote monitoring system of Embodiment 1.

[0026] Figure 10 This is a diagram illustrating an example of a table processed in the remote monitoring system of Embodiment 1.

[0027] Figure 11 This is a flowchart illustrating an example of the operation of the remote monitoring system according to Embodiment 1.

[0028] Figure 12 This is a flowchart illustrating an example of the operation of the remote monitoring system according to Embodiment 1.

[0029] Figure 13 This is a flowchart illustrating an example of the operation of the remote monitoring system according to Embodiment 1.

[0030] Figure 14This is a flowchart illustrating an example of the operation of the remote monitoring system according to Embodiment 1.

[0031] Figure 15 This is a flowchart illustrating an example of the operation of the remote monitoring system according to Embodiment 1.

[0032] Figure 16 This is a flowchart illustrating an example of the operation of the remote monitoring system according to Embodiment 1.

[0033] Figure 17 This is a hardware structure diagram of the main parts of the remote monitoring system in Implementation Method 1. Detailed Implementation

[0034] Embodiments of the object for carrying out the present invention will be described with reference to the accompanying drawings. In the drawings, the same or equivalent parts are labeled with the same reference numerals, and repeated descriptions are simplified or omitted as appropriate. Furthermore, the object of the present invention is not limited to the following embodiments; any modifications to the constituent elements of the embodiments or omissions of any constituent elements of the embodiments are possible without departing from the spirit of the present invention.

[0035] Implementation method 1.

[0036] Figure 1 This is a structural diagram of the remote monitoring system 1 according to embodiment 1.

[0037] The remote monitoring system 1 is applied to remote monitoring of multiple elevators 2. Elevators 2 are used, for example, in buildings with multiple floors. An elevator 2 is a device that transports passengers between multiple floors by moving a car (not shown) vertically. Multiple elevators 2 can also be used in a single building. In this example, the remote monitoring system 1 is applied to remote monitoring of multiple elevators 2. Each elevator 2 is identified, for example, by the building number of the building where the elevator 2 is installed, and the elevator number within that building. In this example, each elevator 2 is identified by its inherent facility name.

[0038] Each elevator 2 is equipped with an intercom 3. The intercom 3 is a communication device used for voice communication between passengers inside the elevator and the outside of the elevator. The intercom 3 is used, for example, in cases of entrapment within the elevator. The intercom 3 is connected to a first communication network 4, for example. The first communication network 4 is, for example, a wide area communication network such as a telephone line network. The first communication network 4 may also be a communication network spanning multiple countries or regions.

[0039] The remote monitoring system 1 includes multiple remote monitoring devices 5. Each elevator 2, which is the object of monitoring, corresponds to any one of the remote monitoring devices 5. A remote monitoring device 5 is a device that acquires information about the elevator 2 corresponding to that remote monitoring device 5. The remote monitoring devices 5 are, for example, configured in a building where the elevator 2 corresponding to that remote monitoring device 5 is installed. Each remote monitoring device 5 is connected to a second communication network 6, for example. The second communication network 6 is, for example, a wide area communication network such as the Internet. The second communication network 6 can also be a communication network spanning multiple countries or regions. The second communication network 6 can also be a VPN (Virtual Private Network) on the Internet, etc.

[0040] The remote monitoring system 1 includes a central management device 7. The central management device 7 may consist of one or more server devices. These server devices may be located in an information center, for example. The information center is a location for collecting and managing information about each elevator 2 that is being monitored. When the central management device 7 consists of multiple server devices, some or all of these server devices may be located in different buildings. In this case, the server devices located in different buildings communicate, for example, via a second communication network 6. Alternatively, some or all of the functions of the central management device 7 may be installed using storage or processing resources on a cloud service. The operation of the remote monitoring system 1 is performed according to one or more programs installed in the central management device 7 or other devices constituting the remote monitoring system 1, such as the remote monitoring device 5.

[0041] Multiple operators use remote monitoring system 1 to perform monitoring tasks. Each operator performs monitoring tasks, for example, in an information center. Each operator performs monitoring tasks via a call device 8 and a monitoring terminal 9. The call device 8 is, for example, a telephone for voice calls. The call device 8 is, for example, connected to a first communication network 4. The monitoring terminal 9 is, for example, a general-purpose information terminal device such as a PC (Personal Computer). The monitoring terminal 9 processes information input by the operators and displays information to them. The monitoring terminal 9 is connected to the remote monitoring device 5, for example, via a local area network based on wired or wireless communication. In remote monitoring system 1, accounts are issued to each operator. Each operator performs monitoring tasks using remote monitoring system 1 by logging in as a user of the account issued to them. In this example, each user is identified by a unique username.

[0042] Each operator has access permissions for monitoring operations. These permissions include the monitoring range from which monitoring data can be viewed, the usage period of that monitoring range, and the monitoring actions that can be performed. Monitoring data refers to information about each elevator 2 being monitored, obtained from the remote monitoring device 5, etc., used for monitoring operations. The monitoring range is information indicating the area of ​​the elevator 2 being monitored. For example, the monitoring range may be represented by listing information about the elevator 2 being monitored. Alternatively, the monitoring range may be represented by information specifying the conditions for monitoring the elevator 2 based on the building where the elevator 2 is installed or the area of ​​that building. Monitoring actions are actions performed during monitoring operations through the remote monitoring system 1. Monitoring actions include, for example, external communication with the outside of the remote monitoring system 1. External communication includes, for example, voice calls using the call device 8. Voice calls as external communication include, for example, calls with passengers in the car via the intercom 3 in the car, calls with maintenance personnel via the mobile phone 10 held by maintenance personnel, and calls with management personnel of the building where the elevator 2 being monitored is installed. In the remote monitoring system 1, the settings for each operator are matched with the user information of the account issued to that operator for management purposes.

[0043] Here, when an operator is absent, such as on a business trip, on vacation, or due to work stoppage, monitoring tasks may sometimes be delegated to another operator during their absence. Furthermore, even when the operator is present, monitoring tasks may sometimes be delegated to another operator based on factors such as workload. In such cases, the delegating operator registers the user of the account issued to the delegated operator as a sub-user of the user of the account issued to themselves. At this point, the user of the account issued to the delegating operator becomes the parent user of the user of the account issued to the delegated operator. The sub-user's permission scope is set to not exceed the parent user's permission scope. Such parent-child relationships are managed in the remote monitoring system 1. The management of parent-child relationships is performed, for example, by a user management program installed in the devices constituting the remote monitoring system 1, such as the central management device 7. Furthermore, the parent-child relationship can be one-to-one, one-to-many, many-to-one, or many-to-many. Moreover, the parent-child relationship can also include grandchildren, i.e., a multi-level relationship including sub-users of sub-users.

[0044] The central management unit 7 of the remote monitoring system 1 includes a storage unit 11, a collection unit 12, a registration and acceptance unit 13, a setting unit 14, a registration and deregistration unit 15, and a request processing unit 16.

[0045] Storage unit 11 is the part that stores information. Here, part or all of storage unit 11 can be configured separately from other parts of central management device 7. In this case, storage unit 11 can be composed of a single piece of hardware or a combination of multiple pieces of hardware. When storage unit 11 is composed of a combination of multiple pieces of hardware, each piece of hardware can be used separately according to the information to be stored.

[0046] Storage unit 11 stores information such as monitoring data tables, user management tables, and sub-user management tables. The monitoring data table contains information about the elevator 2 obtained by each remote monitoring device 5. The user management table contains information about the scope of monitoring permissions for each user. The sub-user management table contains information about the scope of monitoring permissions for users registered as sub-users.

[0047] The collection unit 12 is responsible for collecting information about the elevator 2 obtained by each remote monitoring device 5. The collection unit 12 collects information from each monitoring device via the first communication network 4. For example, the collection unit 12 collects information contained in reports received from each monitoring device.

[0048] Registration processing unit 13 is responsible for accepting registration information. Registration processing unit 13 accepts registration information, for example, via monitoring terminal 9. Registration information refers to the registration information of other users who are sub-users of any user. Here, the example of the parent user being user 1 is an example. Furthermore, the example of the sub-user being user 2 is an example.

[0049] The setting unit 14 is used to set the scope of monitoring permissions for users registered as sub-users. The setting unit 14 sets permissions based on the sub-user's registration information received by the registration acceptance unit 13 and the scope of monitoring permissions for that sub-user's parent user. The setting unit 14 sets the scope of permissions when the registration acceptance unit 13 receives the registration information. The setting unit 14 includes an object setting unit 17 and a period setting unit 18. The object setting unit 17 sets the objects to be monitored within the viewable monitoring scope. The period setting unit 18 sets the usage period for the set monitoring scope.

[0050] The registration deregistration unit 15 is used to deregister a user who has been registered as a sub-user. The registration deregistration unit 15 can, for example, deregister based on information input via the monitoring terminal 9. Alternatively, the registration deregistration unit 15 can deregister based on usage periods set for the sub-user.

[0051] The request processing unit 16 is responsible for processing requests from users sent via the monitoring terminal 9. Requests from users may include, for example, requests to view monitoring data or requests to perform monitoring actions.

[0052] Next, use Figures 2 to 4 An example of information stored in storage unit 11 will be explained.

[0053] Figure 2 This diagram illustrates an example of a monitoring data table stored in the storage unit 11 of Embodiment 1. In the monitoring data table, a correspondence is established between the facility name of each monitored object and an event associated with that object. An event is something that happens in the elevator 2, which is the monitored object. An event is an example of information about the elevator 2 obtained by the remote monitoring device 5. Event information, for example, is sent from the remote monitoring device 5 along with the facility name of the elevator 2 when the event occurs. Furthermore, an event is an example of monitoring data. Event information includes the time information of the event's occurrence. The time information can be, for example, date information in days, or time information in seconds. Events may include, for example, the start of monitoring, and reports of abnormalities from the monitored elevator 2. Furthermore, events may also include, for example, the measurement results of the elevator 2's car acceleration and historical information such as the floors the car stops at.

[0054] Figure 3 This diagram illustrates an example of a user management table stored in the storage unit 11 of Embodiment 1. In the user management table, for each user, the user's username, the name of the facility whose monitoring range includes the monitored object, and the period during which the monitoring data of that monitored object can be viewed are associated with that user. The period of use can be information in months, days, hours, or minutes, etc. This user management table is an example of the first table. A user whose username is registered in the user management table can become the parent user of other sub-users.

[0055] Figure 4 This diagram illustrates an example of a sub-user management table stored in the storage unit 11 of Embodiment 1. In the sub-user management table, for each user registered as a sub-user, the user's username, the username of the user's parent user, the facility name of the monitored object included in the monitoring scope where the user, as a sub-user, can view monitoring data, and the period during which the monitoring data of that monitored object can be viewed are associated. The sub-user management table is an example of the second table.

[0056] Next, use Figure 5 and Figure 6 The display example in monitoring terminal 9 will be explained.

[0057] Figure 5 and Figure 6This is a diagram showing an example of the display in the monitoring terminal 9 of the remote monitoring system 1 according to Embodiment 1.

[0058] exist Figure 5 The following is an example of a display when registering a sub-user. In this example, user C is registered as a sub-user of user A. The monitoring terminal 9 displays a parent user selection box 9a, a sub-user input box 9b, an object specification box 9c, a period specification box 9d, and a registration button 9e. The parent user selection box 9a is an interface for selecting the username of the user to be the parent user. For example, in the case where multiple accounts have been issued to the operator, the parent user selection box 9a is used to select which account's user to register the sub-user as. In this example, user A is selected as the parent user. The sub-user input box 9b is an interface for entering the username of the user registered as a sub-user of the selected user A. In this example, user C is entered as the sub-user. The object specification box 9c is an interface for specifying the monitoring object that user C, as a sub-user of user A, can view the monitoring data of. The monitoring object may not be specified in the object specification box 9c. The period specification box 9d is an interface for specifying the usage period during which user C, as a sub-user of user A, can view the monitoring data of the monitoring object. The usage period may not be specified in the period specification box 9d. The Registration button 9e is used to register a sub-user. When the Registration button 9e is pressed, the parent user's username, the sub-user's username, the specified monitoring object, and the usage period are displayed. Figure 5 The information specified in the image is sent from the monitoring terminal 9 to the registration acceptance department 13 of the central management device 7 as registration information.

[0059] exist Figure 6 The following is an example of an operator performing monitoring work. In this example, user C performs monitoring work as a sub-user of user A. The monitoring terminal 9 displays a facility list 9f, an event list 9g, a user input box 9h, and an update button 9i. The facility list 9f displays a list of facilities included in the monitoring scope of user C as a sub-user. The facility list 9f also displays the usage period of each facility by user C as a sub-user. The event list 9g is a list of events displayed for each facility included in the monitoring scope of user C as a sub-user. The user input box 9h is an interface for entering the username of the user performing the monitoring work. The update button 9i is a button that updates the display of the facility list 9f and event list 9g, etc., based on the permission scope of the user whose username was entered in the user input box 9h. When the update button 9i is pressed, an update request is sent from the monitoring terminal 9 to the request processing unit 16 of the central management device 7. The update request is an example of a request to view monitoring data. The update request, for example, includes information about the username entered into the user input box 9h.

[0060] Next, use Figures 7 to 10 An example of sub-user registration is provided.

[0061] Figures 7 to 10 This is a diagram illustrating an example of a table processed in the remote monitoring system 1 of embodiment 1.

[0062] When in Figure 5 When the registration button 9e is pressed on the screen, the registration receiving unit 13 receives the registration information from the monitoring terminal 9. At this time, the setting unit 14 begins to set the scope of permissions. The setting unit 14 determines whether the monitoring target and the period of use are specified in the registration information.

[0063] When both the monitored object and the usage period are specified, the setting unit 14 determines whether the scope of permissions based on the specified monitored object and usage period exceeds the scope of permissions of the user specified as the parent user in the registration information. The setting unit 14 retrieves the user management table using the parent user's username and the specified monitored object as keywords, thereby obtaining... Figure 7 The example uses Table T1, which shows the usage period. If the usage period specified in the registration information exceeds the usage period in Table T1, the central management device 7 may refuse the sub-user's registration. Furthermore, the central management device 7 may also refuse the sub-user's registration in cases of search failure, blank Table T1, etc. On the other hand, if the usage period specified in the registration information does not exceed the usage period in Table T1, the setting unit 14 registers the specified monitoring object and usage period information, along with the parent user's username and the sub-user's username, in the sub-user management table.

[0064] On the other hand, when neither the monitored object nor the user during the period of use is specified, the setting unit 14 sets the permission scope of the child user based on the permission scope of the user designated as the parent user in the registration information. The setting unit 14 retrieves the permission scope of the child user by searching the user management table using the parent user's username as the keyword. Figure 8 The example shows the parent user's username, facility name, and usage period in Table T2. The setting unit 14 retrieves Table T2 and... Figure 9 The outer product of the usernames of the sub-users in table T3, as shown in the example, generates Figure 10 The setting unit 14 registers the information generated in table T4 into the sub-user management table.

[0065] Furthermore, when only the monitored object is specified, the setting unit 14 retrieves the user management table using the username of the user specified as the parent user in the registration information and the specified monitored object as keywords, thereby obtaining the table T1 for the usage period. The setting unit 14 registers the information of the specified monitored object, the obtained table T1 for the usage period, and the usernames of the parent user and the child user together in the child user management table.

[0066] Furthermore, when only the usage period is specified, the setting unit 14 uses the username of the user designated as the parent user in the registration information as the keyword, and retrieves the user management table based on the condition that the period specified in the registration information does not exceed the usage period, thereby obtaining a table of monitored objects and usage periods. The setting unit 14 registers the information from the obtained table, along with the usernames of the parent user and the child user, into the child user management table. Alternatively, the central management device 7 may reject the registration of the child user in cases such as a search failure or a blank table.

[0067] Next, use Figures 11 to 16 The operation example of remote monitoring system 1 will be explained.

[0068] Figures 11 to 16 This is a flowchart illustrating an example of the operation of the remote monitoring system 1 according to Embodiment 1.

[0069] exist Figure 11 The image shows an example of the operation of the central management device 7 involved in the accumulation of monitoring data.

[0070] In step S101, the collection unit 12 determines whether it has received information about the facility name and the event from the remote monitoring device 5. If the determination result is "no", the central management device 7 re-enters the process of step S101. If the determination result is "yes", the central management device 7 enters the process of step S102.

[0071] In step S102, the collection unit 12 registers the received facility name and event information into the monitoring data table. This accumulates monitoring data in the monitoring data table. Then, the central management device 7 proceeds to the processing in step S101.

[0072] exist Figure 12 The image shows an example of the operation of the central management device 7 involved in the registration of a sub-user.

[0073] In step S201, the registration acceptance unit 13 determines whether registration information has been received from the monitoring terminal 9. If the determination result is "no", the central management device 7 re-enters the process of step S201. If the determination result is "yes", the central management device 7 enters the process of step S202.

[0074] In step S202, the setting unit 14 determines whether at least one of the monitored object and the period of use has been specified in the registration information. If the determination result is "no", the central management device 7 proceeds to step S203. If the determination result is "yes", the central management device 7 proceeds to step S205.

[0075] In step S203, the setting unit 14 searches the entire user management table using the parent user's username as the keyword, thereby obtaining the parent user's username, facility name, and table T2 showing the usage period. Then, the central management device 7 proceeds to step S204.

[0076] In step S204, the setting unit 14 generates table T4 by taking the outer product of the acquired table T2 and the sub-user's username table T3. The setting unit 14 registers the information in the generated table T4 into the sub-user management table. Then, the central management device 7 proceeds to the processing in step S201.

[0077] In step S205, the setting unit 14 determines whether a monitoring object has been specified in the registration information. If the determination result is "yes", the central management device 7 proceeds to step S206. If the determination result is "no", the central management device 7 proceeds to step S208.

[0078] In step S206, the setting unit 14 performs object setting processing. During object setting, monitoring objects not included in the monitoring range viewable by the parent user are excluded from the specified monitoring objects. Then, the central management device 7 proceeds to step S207.

[0079] In step S207, the setting unit 14 determines whether a usage period has been specified in the registration information for the monitoring object set in the object setting process. If the determination result is "yes", the central management device 7 proceeds to step S208. If the determination result is "no", the setting unit 14 directly sets the usage period set in the object setting process for the set monitoring object. Then, the central management device 7 proceeds to step S209. Furthermore, if multiple monitoring objects with different usage periods are set, the central management device 7 can perform the processes after step S207 separately for each monitoring object.

[0080] In step S208, the setting unit 14 performs period setting processing. Then, the central management device 7 proceeds to step S209.

[0081] In step S209, the setting unit 14 registers the sub-users' permissions in the sub-user management table. Then, the central management device 7 proceeds to the processing in step S201.

[0082] exist Figure 13 The image shows an example of the operation of the central management device 7 involved in the object setting process.

[0083] In step S301, the object setting unit 17 reads the parent user's username, the child user's username, and the facility name of the specified monitoring object from the registration information. Then, the central management device 7 proceeds to step S302.

[0084] In step S302, the object setting unit 17 retrieves the user management table using the read parent user's username and facility name as keywords. Then, the central management device 7 proceeds to step S303.

[0085] In step S303, the object setting unit 17 determines whether a search result has been found, i.e., whether the search has been successful. If the determination result is "yes", the central management device 7 proceeds to step S304. If the determination result is "no", the central management device 7 proceeds to step S305.

[0086] In step S304, the object setting unit 17 sets the monitored objects included in the monitoring range that can be viewed by the sub-user based on the search results found. Furthermore, the object setting unit 17 sets the usage period for each monitored object based on the usage period table T1 obtained as a search result. Then, the central management device 7 ends the object setting process.

[0087] In step S305, the object setting unit 17 sets the monitoring range that can be viewed by the sub-user to blank. Then, the central management device 7 ends the object setting process.

[0088] exist Figure 14 The image shows an example of the operation of the central management device 7 involved in the processing set during the period.

[0089] In step S401, the period setting unit 18 reads the parent user's username, the child user's username, and the specified usage period from the registration information. Then, the central management device 7 proceeds to step S402.

[0090] In step S402, the period setting unit 18 retrieves the user management table using the read parent user's username as the keyword, based on the condition that the period specified in the registration information is included in the usage period. Then, the central management device 7 proceeds to step S403.

[0091] In step S403, the period setting unit 18 determines whether the search has been successful. If the determination result is "yes", the central management device 7 proceeds to step S404. If the determination result is "no", the central management device 7 proceeds to step S405.

[0092] In step S404, the period setting unit 18 sets the monitored objects and their usage periods within the monitoring range that the sub-user can view, based on the search results found. Then, the central management device 7 ends the period setting process.

[0093] In step S405, the period setting unit 18 sets the monitoring range that sub-users can view and the period setting blanks. Then, the central management device 7 ends the period setting process.

[0094] exist Figure 15 The image shows an example of the operation of the central management device 7 involved in processing a request from a user who is a sub-user via the monitoring terminal 9.

[0095] In step S501, the request processing unit 16 determines whether an update request has been received and whether the user whose username is included in the update request has been registered as a sub-user in the sub-user management table. If the determination result is "no", the central management device 7 re-enters the processing of step S501. If the determination result is "yes", the central management device 7 enters the processing of step S502.

[0096] In step S502, the request processing unit 16 retrieves the sub-user management table using the username included in the update request as a keyword. Thus, the request processing unit 16 obtains information about the monitored objects that the sub-user can view and the period of their use. Then, the central management device 7 proceeds to step S503.

[0097] In step S503, the request processing unit 16 obtains the current date. The request processing unit 16 also obtains a list of monitored objects from the sub-user management table whose usage period includes the current date. Then, the central management device 7 proceeds to step S504.

[0098] In step S504, the request processing unit 16 performs a full search of the monitoring data table using the facility names of the monitored objects included in the obtained list as keywords. As a result, the request processing unit 16 obtains a list of facility names and events. Then, the central management device 7 proceeds to step S505.

[0099] In step S505, the request processing unit 16 sends the obtained list to the monitoring terminal 9, causing the monitoring terminal 9 to display it as an event list 9g. Then, the central management device 7 proceeds to the processing in step S501.

[0100] exist Figure 16 The image shows an example of the operation of the central management device 7 involved in the deregistration of a sub-user.

[0101] In step S601, the registration / deregistration unit 15 obtains the current date. The registration / deregistration unit 15 determines whether the current date has changed from a previously obtained date. If the determination result is "no," the central management device 7 re-enters the process of step S601. If the determination result is "yes," the central management device 7 enters the process of step S602.

[0102] In step S602, the registration cancellation unit 15 retrieves records from the sub-user management table whose last day of the usage period is earlier than the current date. Then, the central management device 7 proceeds to step S603.

[0103] In step S603, the registration deregistration unit 15 deletes the records obtained as search results from the sub-user management table. Here, when all records related to any sub-user are deleted, the sub-user's registration is deregistered. Then, the central management device 7 proceeds to the processing in step S601.

[0104] Furthermore, in remote monitoring system 1, the scope of permissions for monitoring tasks can be set directly without targeting the user associated with the account. For example, the scope of permissions for monitoring tasks can also be set as roles. Users are assigned roles.

[0105] Furthermore, even if any user has been registered as a sub-user of another user, the inherent scope of permissions for that sub-user set in the user management table is not particularly restricted. That is, there may be a situation where user A cannot view the monitoring data of a facility named C1, but user C can view the monitoring data before registering as a sub-user. In this case, even if user C has been registered as a sub-user of user A, user C's access to the monitoring data of the facility named C1 is unrestricted.

[0106] Furthermore, the information center can also be a location that collects and manages information from elevators 2 located in multiple countries or regions. That is, the countries or regions where the central management device 7, such as the information center, is located, and the countries or regions where each elevator 2 is located, can be different. Relay stations in the first communication network 4 can also be configured across multiple countries or regions. Nodes in the second communication network 6 can also be configured across multiple countries or regions. Both the first communication network 4 and the second communication network 6 can be communication networks that conduct digital communication, such as the Internet. In this case, the first communication network 4 and the second communication network 6 can also be the same communication network. When the central management device 7 located in the first country or region collects information from elevators 2 located in the second country or region, the first communication network 4 or the second communication network 6 can also be a communication network that includes relay stations or nodes located in a third country or region. The third country or region that includes the relay stations or nodes of the first communication network 4 or the second communication network 6 can also include multiple countries or regions. Thus, the present invention also envisions a remote monitoring system 1 that enables communication between multiple elevators 2, remote monitoring devices 5, and central management devices 7 across multiple countries or regions via a first communication network 4 and a second communication network 6.

[0107] Furthermore, the central management unit 7 can also be a system set up across multiple countries or regions. For example, if the central management unit 7 consists of multiple server units, each server unit can be configured in a different country or region. For example, it is also possible to configure a server unit equipped with some functions of the central management unit 7, such as the storage unit 11, in a first country or region, and configure a server unit equipped with other functions in a second country or region.

[0108] Furthermore, when a portion of the central management device 7, such as the storage unit 11, is composed of a combination of multiple hardware components, the individual hardware components can be configured in different countries or regions. For example, when the hardware storing monitoring data tables in the storage unit 11 is configured in a first country or region, the hardware storing user information tables can be configured in a second country or region. In this case, the hardware storing sub-user information tables can also be configured in a third country or region.

[0109] As explained above, the remote monitoring system 1 of Embodiment 1 includes a registration receiving unit 13 and a setting unit 14. The registration receiving unit 13 receives registration information. The registration information indicates the registration of a second user who is a sub-user of a first user registered in the user management table. The first table establishes a correspondence between the monitoring range accessible to each user and that user. When the registration receiving unit 13 receives registration information, the setting unit 14 sets the monitoring range accessible to the second user who is a sub-user of the first user to not exceed the range accessible to the first user that is corresponding to the first user in the user management table. Furthermore, the remote monitoring system 1 includes a storage unit 11. The storage unit 11 stores the first table. Additionally, the storage unit 11 stores a second table. In the second table, the monitoring range accessible to the sub-user registered according to the registration information, set by the setting unit 14, is corresponding to that sub-user.

[0110] Furthermore, the user management method of Implementation Method 1 includes a registration acceptance step and a setting step. The registration acceptance step is the step of accepting registration information. In the setting step, based on the registration information accepted in the registration acceptance step, the monitoring range that a second user, who is a sub-user of the first user, can view is set to not exceed the range of the monitoring range that has been established with the first user in the user management table.

[0111] Furthermore, the user management program of Implementation 1 enables the remote monitoring system 1 of elevator 2 to perform registration and acceptance steps and setting steps.

[0112] This structure allows for easy registration of child users who inherit the permission scope of their parent users. In this case, there is no need to register new, permanently independent users. Furthermore, by accessing the remote monitoring system 1 as child users, excessive permissions are not granted to the operators performing monitoring tasks, thus preventing a decrease in information security. In this way, it is easy to register child users who are granted appropriate permissions based on the existing user's permission scope, thereby facilitating the performance of elevator 2 monitoring tasks.

[0113] Furthermore, sometimes the registration information includes a designation of the monitored objects within the monitoring range that the second user can view. In this case, the setting unit 14 sets the monitoring range that the second user, as a sub-user of the first user, can view, as described below. This monitoring range is defined in the user management table as a monitoring range that can be viewed, and is associated with the first user and specified in the registration information as the monitored objects.

[0114] Furthermore, sometimes the registration information includes a specified usage period. In this case, the setting unit 14 sets the monitoring scope that a second user, who is a sub-user of the first user, can view, as described below. This monitoring scope is defined in the user management table as a viewable monitoring scope and is associated with the first user. The usage period that the first user can view in the user management table includes the monitored object for the usage period specified in the registration information. The setting unit 14 sets the period that the second user, who is a sub-user of the first user, can view for this monitored object to the usage period specified in the registration information.

[0115] With this structure, the scope of permissions granted to the second user (as a sub-user) is set to not exceed the parent user's permission scope, based on the specified range and the scope of permissions granted to the first user (as the parent user). This reduces the likelihood of compromised information security due to proxy monitoring.

[0116] Furthermore, sometimes the registration information does not include the designation of monitored objects. In this case, the setting unit 14 sets the monitoring scope that the second user, who is a sub-user of the first user, can view, as described below. This monitoring scope is defined in the user management table as the monitoring scope that can be viewed, and a monitoring object corresponding to the first user is established.

[0117] Furthermore, sometimes the registration information does not include a specified usage period. In this case, the setting unit 14 sets the monitoring scope that a second user, who is a sub-user of the first user, can view, as described below. This monitoring scope is limited to the monitoring objects corresponding to the first user as the viewing scope in the user management table. The setting unit 14 sets the period that the second user, who is a sub-user of the first user, can view for this monitoring object to the usage period that the first user is specified in the user management table for viewing the monitoring object.

[0118] With this structure, even if the scope of permissions is omitted during sub-user registration, the scope of permissions granted to the second user (who is also a sub-user) is set to not exceed the scope of permissions granted to the first user, based on the scope of permissions granted to the first user. This reduces the likelihood of compromised information security due to proxy monitoring. Furthermore, the explicit specification of permission scopes, such as the name of the individual facility being monitored, can be omitted, making it easy to proxy the monitoring of elevator 2.

[0119] Furthermore, the remote monitoring system 1 includes a registration deregistration unit 15. The registration deregistration unit 15 deregisters the second user, who is a sub-user of the first user, when the entire usage period set by the setting unit 14 expires, during the period when the second user can view the monitoring range set by the first user.

[0120] This structure ensures that sub-user registrations are deactivated upon the expiration of their usage period, thus preventing the accumulation of unnecessary sub-user registrations. This also helps prevent unauthorized access, such as stolen accounts of unused users. Consequently, information security is less likely to be compromised.

[0121] Additionally, the registration information may include restrictions on the surveillance actions that a second user, who is a sub-user of the first user, can perform. In this case, the setting unit 14 may also limit the surveillance actions that a second user, who is a sub-user of the first user, can perform to the scope restricted in the registration information.

[0122] Furthermore, in the first table, such as the user management table, a correspondence can be established between each user and the monitoring actions that can be performed. In this case, the setting unit 14 can also set the monitoring actions that can be performed by the second user, who is a sub-user of the first user, to not exceed the range of monitoring actions that can be performed and corresponded to the first user in the user management table.

[0123] Here, as a limitation on the surveillance actions that can be carried out, the registration information includes, for example, whether external communication is permitted. Furthermore, as for whether external communication is permitted, the registration information includes, for example, whether voice calls can be made via a communication device installed on the monitored object. In this case, restrictions are imposed on the operation of the calling device 8, etc., for example, through the monitoring terminal 9 or the central management device 7.

[0124] This structure allows for the restriction of unnecessary surveillance actions by the acting operator. For example, there may be situations where the acting operator is a person from an external organization who has been entrusted with a portion of the business related to surveillance operations. In such cases, external communication, such as voice calls, may sometimes be prohibited for the acting operator. Thus, even when the scope of surveillance actions is restricted for each operator, restrictions can still be imposed on surveillance actions through sub-user registration.

[0125] Furthermore, update requests can also specify the facility name of the monitored object to request the display of monitoring data for that object. In this case, the request processing unit 16 of the remote monitoring system 1 rejects the request when it receives a viewing request from a second user who is a sub-user of the first user, which exceeds the monitoring scope set by the setting unit 14 as a sub-user of the first user.

[0126] This structure prevents unauthorized access to the monitored object's data by users without viewing permissions. Therefore, information security is less likely to be compromised.

[0127] Next, use Figure 17 An example of the hardware structure of remote monitoring system 1 is given.

[0128] Figure 17 This is a hardware structure diagram of the main parts of the remote monitoring system 1 according to embodiment 1.

[0129] The functions of the remote monitoring system 1 can be implemented by a processing circuit. The processing circuit includes at least one processor 100a and at least one memory 100b. Alternatively, the processing circuit may include at least one dedicated hardware 200 instead of the processor 100a and memory 100b.

[0130] When the processing circuit includes a processor 100a and a memory 100b, the functions of the remote monitoring system 1 are implemented by software, firmware, or a combination of software and firmware. At least one of the software and firmware is described as a program. The program is stored in the memory 100b. The processor 100a implements the functions of the remote monitoring system 1 by reading and executing the program stored in the memory 100b.

[0131] The processor 100a is also called a CPU (Central Processing Unit), processing device, arithmetic device, microprocessor, microcomputer, or DSP. The memory 100b is composed of non-volatile or volatile semiconductor memories such as RAM (Random Access Memory), ROM (Read Only Memory), flash memory, EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory).

[0132] When the processing circuit has dedicated hardware 200, the processing circuit is implemented, for example, by a single circuit, a composite circuit, a programming processor, a parallel programming processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0133] Each function of the remote monitoring system 1 can be implemented separately by the processing circuitry. Alternatively, each function of the remote monitoring system 1 can also be implemented centrally by the processing circuitry. Regarding each function of the remote monitoring system 1, some can be implemented by dedicated hardware 200, and others by software or firmware. Thus, the processing circuitry implements each function of the remote monitoring system 1 through dedicated hardware 200, software, firmware, or a combination thereof.

[0134] Industrial availability

[0135] The remote monitoring system of the present invention can be applied to the remote monitoring of elevators. The user management method and user management program of the present invention can be applied to the remote monitoring system.

[0136] Label Explanation

[0137] 1: Remote monitoring system; 2: Elevator; 3: Intercom; 4: First communication network; 5: Remote monitoring device; 6: Second communication network; 7: Central management device; 8: Calling device; 9: Monitoring terminal; 10: Mobile phone; 11: Storage unit; 12: Collection unit; 13: Registration acceptance unit; 14: Setting unit; 15: Registration cancellation unit; 16: Request processing unit; 17: Object setting unit; 18: Period setting unit; 9a: Parent user selection box; 9b: Child user input box; 9c: Object specification box; 9d: Period specification box; 9e: Registration button; 9f: Facility list; 9g: Event list; 9h: User input box; 9i: Update button; 100a: Processor; 100b: Memory; 200: Dedicated hardware.

Claims

1. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The registration and acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table. In the first table, each user among multiple users is associated with the monitoring range that each user can view. as well as The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. When the registration information includes a specified usage period, the setting unit limits the monitoring range that the second user, who is a sub-user of the first user, can view to the monitoring range that can be viewed in the first table, establishes a correspondence with the first user, and the usage period that can be viewed for the first user in the first table includes the monitoring object of the usage period specified in the registration information, and sets the usage period that can be viewed for the monitoring object to the usage period specified in the registration information.

2. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The registration and acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table. In the first table, each user among multiple users is associated with the monitoring range that each user can view. as well as The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information does not include a specified period of use, the setting unit limits the monitoring scope that the second user, who is a sub-user of the first user, can view to the monitoring scope that can be viewed in the first table, and establishes a corresponding monitoring object with the first user, and sets the period that can be viewed for the monitoring object to the usage period that can be viewed for the first user in the first table.

3. The remote monitoring system for elevators according to claim 1 or 2, wherein, The elevator's remote monitoring system includes a registration deregistration unit that deregisters the second user, who is a sub-user of the first user, when the usage period set by the setting unit expires during the period when the second user can view the monitoring range set by the first user.

4. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The registration and acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table. In the first table, each user among multiple users is associated with the monitoring range that each user can view. as well as The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information contains restrictions on the surveillance actions that can be performed, the setting unit will limit the surveillance actions that the second user, who is a sub-user of the first user, can perform to the scope restricted in the registration information.

5. The remote monitoring system for elevators according to claim 4, wherein, As a limitation to the surveillance operations that can be carried out, the registration information includes whether external communication is permitted.

6. The remote monitoring system for elevators according to claim 5, wherein, As to whether external communication is possible, the registration information includes whether voice calls can be made through a communication device installed on the monitored object.

7. The remote monitoring system for elevators according to any one of claims 1-2 and 4-6, wherein, If the registration information includes a specification of the monitored objects included in the monitoring range that the second user can view, the setting unit limits the monitoring range that the second user, who is a sub-user of the first user, can view to the monitoring range that can be viewed in the first table, and establishes a correspondence with the first user for the monitored objects specified in the registration information.

8. The remote monitoring system for elevators according to any one of claims 1-2 and 4-6, wherein, If the registration information does not include the designation of a monitoring object, the setting unit limits the monitoring scope that the second user, who is a sub-user of the first user, can view to the first table as the viewing scope, and establishes a corresponding monitoring object with the first user.

9. The remote monitoring system for elevators according to any one of claims 1-2 and 4-6, wherein, The remote monitoring system of the elevator includes a request processing unit that rejects a viewing request from a second user who is a sub-user of the first user, if the request exceeds the monitoring range set by the setting unit for the sub-user of the first user.

10. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The storage unit stores a first table that corresponds to each user among multiple users and the monitoring range that each user can view. The registration acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table; as well as The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. When the registration information includes a specified usage period, the setting unit limits the monitoring range that the second user, who is a sub-user of the first user, can view to the monitoring range that can be viewed in the first table, establishes a correspondence with the first user, and the usage period that can be viewed for the first user in the first table includes the monitoring object of the usage period specified in the registration information, and sets the usage period that can be viewed for the monitoring object to the usage period specified in the registration information.

11. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The storage unit stores a first table that corresponds to each user among multiple users and the monitoring range that each user can view. The registration acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table; as well as The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information does not include a specified period of use, the setting unit limits the monitoring scope that the second user, who is a sub-user of the first user, can view to the monitoring scope that can be viewed in the first table, and establishes a corresponding monitoring object with the first user, and sets the period that can be viewed for the monitoring object to the usage period that can be viewed for the first user in the first table.

12. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The storage unit stores a first table that corresponds to each user among multiple users and the monitoring range that each user can view. The registration acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table; as well as The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information contains restrictions on the surveillance actions that can be performed, the setting unit will limit the surveillance actions that the second user, who is a sub-user of the first user, can perform to the scope restricted in the registration information.

13. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The registration and acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table. In the first table, each user among multiple users is associated with the monitoring range that each user can view. The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the monitoring range that has been established with the first user in the first table; as well as The storage unit stores a second table, in which a correspondence is established between the monitoring range that the setting unit sets for the sub-user registered based on the registration information and that sub-user. When the registration information includes a specified usage period, the setting unit limits the monitoring range that the second user, who is a sub-user of the first user, can view to the monitoring range that can be viewed in the first table, establishes a correspondence with the first user, and the usage period that can be viewed for the first user in the first table includes the monitoring object of the usage period specified in the registration information, and sets the usage period that can be viewed for the monitoring object to the usage period specified in the registration information.

14. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The registration and acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table. In the first table, each user among multiple users is associated with the monitoring range that each user can view. The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the monitoring range that has been established with the first user in the first table; as well as The storage unit stores a second table, in which a correspondence is established between the monitoring range that the setting unit sets for the sub-user registered based on the registration information and that sub-user. If the registration information does not include a specified period of use, the setting unit limits the monitoring scope that the second user, who is a sub-user of the first user, can view to the monitoring scope that can be viewed in the first table, and establishes a corresponding monitoring object with the first user, and sets the period that can be viewed for the monitoring object to the usage period that can be viewed for the first user in the first table.

15. A remote monitoring system for an elevator, wherein, The elevator's remote monitoring system includes: The registration and acceptance department accepts the registration information of the second user, who is a sub-user of the first user registered in the first table. In the first table, each user among multiple users is associated with the monitoring range that each user can view. The setting unit, when the registration acceptance unit accepts the registration information, sets the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the monitoring range that has been established with the first user in the first table; as well as The storage unit stores a second table, in which a correspondence is established between the monitoring range that the setting unit sets for the sub-user registered based on the registration information and that sub-user. If the registration information contains restrictions on the surveillance actions that can be performed, the setting unit will limit the surveillance actions that the second user, who is a sub-user of the first user, can perform to the scope restricted in the registration information.

16. A user management method in a remote monitoring system for elevators, wherein, The user management methods in the elevator's remote monitoring system include: The registration acceptance step involves accepting the registration information of a second user, who is a sub-user of the first user registered in table 1. In table 1, a correspondence is established between each user and the monitoring range that each user can view; and The setting step involves, based on the registration information accepted in the registration acceptance step, setting the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information includes a specified usage period, in the setting step, the monitoring range that the second user, who is a sub-user of the first user, can view is limited to the monitoring range that can be viewed in the first table, and a correspondence is established with the first user. The usage period that can be viewed for the first user in the first table includes the monitoring object of the usage period specified in the registration information, and the usage period that can be viewed for the monitoring object is set to the usage period specified in the registration information.

17. A user management method in a remote monitoring system for elevators, wherein, The user management methods in the elevator's remote monitoring system include: The registration acceptance step involves accepting the registration information of a second user, who is a sub-user of the first user registered in table 1. In table 1, a correspondence is established between each user and the monitoring range that each user can view; and The setting step involves, based on the registration information accepted in the registration acceptance step, setting the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information does not include a specified period of use, in the setting step, the monitoring scope that the second user, who is a sub-user of the first user, can view is limited to the monitoring scope that can be viewed in the first table, and a corresponding monitoring object is established with the first user, and the period during which the monitoring object can be viewed is set to the usage period that the first user can view the monitoring object specified in the first table.

18. A user management method in a remote monitoring system for elevators, wherein, The user management methods in the elevator's remote monitoring system include: The registration acceptance step involves accepting the registration information of a second user, who is a sub-user of the first user registered in table 1. In table 1, a correspondence is established between each user and the monitoring range that each user can view; and The setting step involves, based on the registration information accepted in the registration acceptance step, setting the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information contains restrictions on the surveillance actions that can be performed, in the setting step, the surveillance actions that the second user, who is a sub-user of the first user, can perform are limited to the scope restricted in the registration information.

19. A storage medium storing a user management program that causes a remote monitoring system for an elevator to perform the following steps: The registration acceptance step involves accepting the registration information of a second user, who is a sub-user of the first user registered in table 1. In table 1, a correspondence is established between each user and the monitoring range that each user can view; and The setting step involves, based on the registration information accepted in the registration acceptance step, setting the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information includes a specified usage period, in the setting step, the monitoring range that the second user, who is a sub-user of the first user, can view is limited to the monitoring range that can be viewed in the first table, and a correspondence is established with the first user. The usage period that can be viewed for the first user in the first table includes the monitoring object of the usage period specified in the registration information, and the usage period that can be viewed for the monitoring object is set to the usage period specified in the registration information.

20. A storage medium storing a user management program that causes a remote monitoring system for an elevator to perform the following steps: The registration acceptance step involves accepting the registration information of a second user, who is a sub-user of the first user registered in table 1. In table 1, a correspondence is established between each user and the monitoring range that each user can view; and The setting step involves, based on the registration information accepted in the registration acceptance step, setting the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information does not include a specified period of use, in the setting step, the monitoring scope that the second user, who is a sub-user of the first user, can view is limited to the monitoring scope that can be viewed in the first table, and a corresponding monitoring object is established with the first user, and the period during which the monitoring object can be viewed is set to the usage period that the first user can view the monitoring object specified in the first table.

21. A storage medium storing a user management program that causes a remote monitoring system for an elevator to perform the following steps: The registration acceptance step involves accepting the registration information of a second user, who is a sub-user of the first user registered in table 1. In table 1, a correspondence is established between each user and the monitoring range that each user can view; and The setting step involves, based on the registration information accepted in the registration acceptance step, setting the monitoring range that the second user, who is a sub-user of the first user, can view to not exceed the range in the first table that corresponds to the monitoring range that the first user can view. If the registration information contains restrictions on the surveillance actions that can be performed, in the setting step, the surveillance actions that the second user, who is a sub-user of the first user, can perform are limited to the scope restricted in the registration information.

Images