CN108693863B

CN108693863B - Elevator simulator

Info

Publication number: CN108693863B
Application number: CN201810154800.7A
Authority: CN
Inventors: 羽鸟贵大; 星野孝道; 鸟谷部训; 藤原正康
Original assignee: Hitachi Ltd
Current assignee: Hitachi Ltd
Priority date: 2017-03-30
Filing date: 2018-02-23
Publication date: 2020-12-15
Anticipated expiration: 2038-02-23
Also published as: JP2018167966A; CN108693863A; JP6757282B2; KR20190028631A

Abstract

The invention provides an elevator simulator, which can more accurately evaluate the influence of the specification of elevator equipment on a user and the influence related to the behavior of the user. In the simulation, a user is generated so as to take a behavior based on elevator information set by an elevator device setting unit in accordance with an elevator device and building information set by a building information setting unit in accordance with the entire building. The simulation is performed in this state. Thus, the influence of the specification of the elevator equipment on the user and the influence of the specification on the behavior of the user can be evaluated more accurately.

Description

Elevator simulator

Technical Field

The invention relates to an elevator simulator, in particular to an elevator simulator which is suitable for implementing simulation corresponding to elevator equipment.

Background

In a conventional elevator simulator, evaluation based on simulation when a recommendation target is applied to a building device to be recommended is performed based on recommendation candidates extracted according to predetermined conditions, operation history data of the building device to be recommended, building device condition data, and building device preference data, and the recommendation candidates are output as necessary (see patent document 1).

Documents of the prior art

Patent document

Patent document 1: japanese patent laid-open No. 2012 and 226460

Disclosure of Invention

Problems to be solved by the invention

However, in the conventional elevator simulator, even if the influence of installation of the building equipment itself can be evaluated, the influence on the user and the influence on the behavior of the user with respect to the specifications of the elevator equipment cannot be evaluated. Therefore, sufficient research is required for planning the installation of the building equipment, and a large amount of time is required for planning the installation of the building equipment. On the other hand, when the installation planning of the building equipment is under study, the convenience of the user is deteriorated, and in order to compensate for this, compensation in the operation level is required, and for example, guidance for security or the like is performed in the building, which may cause extra labor cost that is originally unnecessary.

The present invention has been made in view of the above points, and provides an elevator simulator capable of more accurately evaluating not only the influence of installation of building equipment but also the influence on a user and the influence on the behavior of the user with respect to the specifications of elevator equipment.

Means for solving the problems

In order to solve the above problems, the present invention is provided with: an elevator device setting unit that sets elevator information regarding the elevator device; a building information setting unit for setting building information relating to the building specification of the whole building; a user setting unit for setting user information including a generation time, a generation floor, a destination floor, and an attribute of a user generated by simulation in the elevator equipment; an in-building user control unit for controlling the behavior of the user; an elevator control part for managing the operation by controlling the elevator equipment; an input device for issuing a service request from the in-building user control unit to the elevator control unit; and a landing output device that outputs a result of responding to the service request, wherein the in-building user control unit simulates generation of the user and performs simulation by assuming a behavior based on the elevator information and the building information.

Effects of the invention

According to the invention, not only the influence caused by the arrangement of the building equipment can be evaluated more accurately, but also the influence of the building equipment specification caused by the behavior change of the user can be evaluated more accurately.

Drawings

Fig. 1 is a system configuration diagram of an elevator simulator according to the present embodiment.

Fig. 2 is a flowchart of an example of the user creating process according to the present embodiment.

Fig. 3 is a flowchart of an example of registration determination processing according to the present embodiment.

Fig. 4 is a flowchart of an example of the apparatus registration processing of the present embodiment.

Fig. 5 is a flowchart showing an example of the device user waiting process shown in fig. 4.

Fig. 6 is a flowchart of an example of the destination floor registration process shown in fig. 4.

Fig. 7 is a flowchart showing an example of the distribution stand-alone waiting process shown in fig. 6.

Fig. 8 is a flowchart of an example of the user update process shown in fig. 6.

Fig. 9 is a flowchart of an example of the landing walking process shown in fig. 8.

Fig. 10 is a flowchart of an example of the walking determination process shown in fig. 9.

Fig. 11 is a flowchart of an example of the hall waiting process shown in fig. 9.

Fig. 12 is a flowchart of an example of the queue waiting processing according to the present embodiment.

Fig. 13 is a layout diagram in simulation of the door interlocking system according to the present embodiment.

Fig. 14 is a layout diagram in simulation of the door interlocking system according to the present embodiment.

Fig. 15 is a layout diagram in simulation of the door interlocking system according to the present embodiment.

Fig. 16 is a layout view of a hall lantern lighting system of the vertical hall button system according to the present embodiment in simulation.

Fig. 17 is a layout diagram of a hall lantern non-lighting system of the vertical hall button system according to the present embodiment.

Fig. 18 is a layout view of the wheelchair-type simulation of the vertical landing button system according to the present embodiment.

Fig. 19 is a layout view of the wheelchair-type simulation of the vertical hall button system according to the present embodiment.

Detailed Description

One embodiment of the present invention will be described in detail below with reference to the accompanying drawings.

(1) System configuration

Fig. 1 shows a schematic configuration example of a simulation system 100 according to the present embodiment.

The simulation system 100 includes a user setting unit 1, a building information setting unit 2, an elevator equipment setting unit 3, an elevator specification setting unit 4, a time zone setting unit 5, and a simulation unit 10. The simulation section 10 includes an in-building user control section 11, an input device 12, an elevator group management control section 13, an elevator control section 14, a landing output device 15, an elevator 16, and a comprehensive evaluation output section 17.

The user setting unit 1 has a function of setting information about a user. Examples of the information on the user include: the generation floor of a floor where a user enters an elevator lobby, the destination floor indicating a destination floor set with the use of an elevator, the user attribute indicating whether the user is a general user, a wheelchair user, a VIP user, or the like, the walking speed of the user walking in the lobby, the generation distribution such as the generation ratio of the user for setting each generation floor or destination floor, and the like are set.

The building information setting unit 2 has a function of setting building information. The building information includes, for example, the number of floors of a building and the distance between floors. The building information includes information indicating the number of persons in the building, the building specification of each floor, the lobby floor, the parking lot floor, and the shared floor, which are located in each office of each floor of the building.

The elevator equipment setting unit 3 has a function of setting elevator information on the elevator equipment. The elevator equipment includes, for example, an elevator car (hereinafter, simply referred to as "car") having 6 setting parts, an installation position of the elevator car on a floor, a destination floor registration device as an input device for registering a destination floor in a hall, a vertical hall button for making a service request by moving from the hall to an upper floor or a lower floor, a door interlock device provided at a hall entrance for enabling registration of a destination floor when passing a door, a reservation stand-alone for indicating a direction when the elevator arrives as an output device and indicating a reservation stand and a reservation direction when another elevator is reserved, and can be installed at which position of a floor a destination floor stop floor or the like indicating a scheduled stop floor of each stand-alone at the hall when a destination floor is registered in the hall.

The elevator specification setting unit 4 has a function of setting the specification of the installed elevator equipment. The specifications of the elevator equipment include, for example, elevator speed, door width, rated number of people, and the like. Further, as the operation specification of the elevator equipment, the presence or absence of an immediate reservation function of lighting a single elevator indicator lamp determined in response to a service request from a hall button at the moment of the service request can be cited.

The time zone setting unit 5 has a function of setting a time zone for performing simulation. Generally, elevator operating conditions within a building are different at each time band. For example, in an office time zone, the number of users entering a building increases, and as the user's exercise, the user starts from a lobby floor and uses the work floor of each user as a destination floor. In the first half of the lunch time zone, when there is a dining room floor or a floor where a restaurant exists in the building, there are many users who move from the work floor of each user to the dining room floor or the floor where the restaurant exists. In the off-duty time zone, there are many users who move from the work floor to the lobby floor of each user, as opposed to the on-duty time zone.

The generation distributions of the time zone setting unit 5 and the user setting unit 1, such as the generation ratios of the users for each generation floor and destination floor, are set in association with each other. Here, as a method of setting the generation ratio of the user, a method of automatically setting the generation ratio after setting the time slot, a method of sequentially setting the generation distribution of the user for each arbitrary time slot, a method of determining the generation distribution for each time slot according to the building use, or a method of determining the generation distribution for each time slot based on the field measurement data of the similar building specifications in the past may be adopted.

In the method of automatically setting the generation ratio after setting the time zone, for example, when the time zone is set as an office time zone, the generation ratio of the user from a lobby floor to each floor is set according to the number of persons who enter and stay at each floor. Specifically, in the off-duty time zone 8: 15-8: between 45 and 30 minutes, in the case where the generation ratio of users going from the lobby floor to each floor is set to 40%, and in the case where the resident at the 5 th floor is 100 and the resident at the 4 th floor is 80, 40 users going from the lobby floor to the 5 th floor are generated, and 32 users going to the 4 th floor are generated.

In the method of sequentially setting the user occurrence distribution for each arbitrary time zone, the generation ratios of users for each generation floor and destination floor are set for each time zone. Specifically, it is set to be in the off-duty time zone 8: 15-8: the percentage of users who go between 30 from the lobby floor to the other floors is 15%, and in time zone 8: 30-8: the proportion of users going from lobby floor to other floors between 45 is 25%. The length of the time zone may be set arbitrarily, and the set value for generating the distribution may be set proportionally or may be set in detail for each floor.

In this setting, for example, 200 users from the lobby floor, 10 users from the floor 1, and 80 users to the floor 4, and 130 users to the floor 5 may be set, or more specifically, 125 users from the lobby floor to the floor 5, 75 users from the lobby floor to the floor 4, 5 users from the floor 1 to the floor 4, and 5 users from the floor 1 to the floor 5 may be set in detail.

In a method for determining a generation distribution for each time slot according to the building application, a set value is changed in a method for automatically setting a generation ratio after setting the time slot according to the building application. Examples of the building applications include office buildings, high-rise houses (apartment buildings), hotels, and hybrid buildings. In office buildings, for example, the users generally flow from the lobby floors to the respective floors, whereas in high-rise houses (apartment buildings), the users flow from the respective floors to the lobby floors in many cases. Further, since the time zone is also different from the office building, the time zone and the generation distribution also vary according to the use of the building.

After setting of these pieces of information is completed, simulation can be performed. The simulation unit 10 for performing simulation always updates the system time, and includes, for the purpose of simulation described below: an in-building user control section 11 that controls the movement of the floor of the user and the boarding and alighting of the elevator 16 generated, an input device 12 for setting a service request to the elevator from the in-building user control section 11, an elevator group management control section 13 that performs operation management in response to the service request, an elevator control section 14 that controls the opening and closing of the elevator car or the car door in response to the service request received from the elevator group management control section 13, a landing output device 15 that realizes guidance to the user from the elevator group management control section 13 or the elevator control section 14, and the elevator 16 on which the user rides and alighting. In the present embodiment, "user" indicates a user generated in a simulation.

The elevator group management control unit 13 finally outputs the evaluation under the set simulation condition from the integrated evaluation output unit 17, triggered by the system time of the simulation unit 10 reaching the simulation completion time. The evaluation includes an elevator waiting time from arrival at a landing to boarding, an boarding time from boarding to alighting, and a service completion time from arrival at a landing to arrival at a destination floor, which are output from the user control section 11 in the building. In addition, when the elevator waiting time of 60 seconds or more is defined as the long waiting time, for example, the present evaluation outputs the long waiting rate as an indication of how much the number of users in the long waiting time is present with respect to the number of users generated as a whole, or outputs the maximum number of waiting users as an indication of the maximum number of users waiting at the terminal in the simulation time.

The elevator group management control section 13 inputs the following evaluation based on the time input from each input device 12: the evaluation of the average time, the maximum time, the minimum time, and the like among simulation times such as numbers input by the input device 12, the time taken for the car in each elevator 16 to reach the input floor, the time taken for the user to press the destination button in the car to input the destination floor in the elevator 16, and the time taken to reach the destination position.

The evaluation output from the elevator group management control unit 13 is output from the elevator control unit 14 in the case of the non-group management system or in the case of performing a simulation of only one elevator.

The in-building user control unit 11 performs operation and time management according to equipment in order to reproduce the movement of the user at the landing specifically from the generation of the user. These motions are changed according to the output situation by changing the elevator output situation according to the facilities and specifications set by the elevator facility setting unit 3 and the elevator specification setting unit 4. These movements are explained later (refer to fig. 2 to 12).

The input device 12 corresponds to, for example, a vertical landing button and a landing destination floor registration device. The position of the input device 12 in the landing can be set to any coordinate according to the landing layout by setting with the elevator equipment setting unit 3. The input device 12 is different in data necessary for input for each target device, but data including all user information is input for each target device.

For example, in the case where the input device 12 is a vertical hall button, the input information obtained by the input device 12 is data indicating a service request to an upper floor or a service request to a lower floor from a hall, and therefore, it is determined for each user whether the service request is an upward service request or a downward service request based on the user information, the generated floor information, and the destination floor information. Here, the input information is stored in a shared memory shared by the user control unit 11 and the input device 12 in the simulation unit 10.

In the case of the method using the destination floor registration device or the door interlock method, the destination floor of the user and the user attribute are input information, not input information on the upper floor or the lower floor. The input information is stored in a common memory provided in the simulation unit 10. The amount of information is larger than that in the case of the vertical hall button, and after the device is determined by the elevator device setting unit 3, the data size corresponding to the input information obtained by each input device 12 is allocated in the common memory.

The elevator group management control unit 13 automatically sets the group management specifications based on the setting information of the building information setting unit 2, the elevator equipment setting unit 3, and the elevator specification setting unit 4. The elevator group management control unit 13 automatically extracts and sets parameters used for actual control, such as the number of elevator sections and the elevator speed, which are parameters necessary for calculating the estimated arrival time, from the setting information, in addition to the setting of the inter-floor distance, when the optimal elevator is selected for the input device 12, thereby minimizing the waiting time.

The elevator group management control section 13 performs elevator operation management corresponding to each specification. For example, when the input device 12 is provided as a wheelchair-type vertical hall button, the elevator group management control unit 13 controls only an elevator adjacent to the vertical hall button as a single allocated device. For example, when the input device 12 is provided as a landing button of the VIP system, the elevator group management control unit 13 performs control so that a predetermined unit is regarded as a VIP unit and the VIP unit does not respond to a new service request. On the other hand, when the input device 12 is a destination floor registration device, the elevator group management control section 13 controls the number of stop floors corresponding to the destination floor to be suppressed because the destination floor is known in the landing. This enables transportation with improved transport capacity.

In addition to this, the elevator group management controller 13 can perform control in accordance with a preset elevator specification. The elevator group management control section 13 switches the hall lantern as the hall output device 15 between a lit state, a extinguished state, and a flashed state, based on, for example, a specification for immediately lighting the hall lantern or a specification for not lighting the hall lantern when the up-down hall button is pressed.

The elevator control unit 14 mainly performs control of the single elevator, opening and closing control of the control door, stop, departure, acceleration, deceleration, and operation processing of the elevator. As in the case of the elevator group management control section 13, the elevator specifications are automatically set based on the information set by the elevator specification setting section 4. For example, the inter-floor distance is autonomously set, or parameters related to control, such as the elevator speed, are set.

The elevator 16 is a generic term for equipment including an elevator on which a user rides and lowers, and changes the open/close state of a door, the state of a car, and the like in accordance with a command from the elevator control unit 14. In addition, the elevator 16 is associated with a destination floor reservation system that manages registration of destination floors.

The comprehensive evaluation output unit 17 summarizes and outputs the simulation results. The simulation result includes at least information outputted from the in-building user control section 11, for example, elevator information, waiting time from arrival of each user at a landing to boarding of the elevator, boarding time from boarding of the user to alighting of the user, and service completion time from arrival of the user at the landing to arrival at a destination floor. In the present embodiment, the elevator waiting time of 60 seconds or more is defined as a long waiting time. The comprehensive evaluation output unit 17 outputs, for example, a probability (long waiting rate) indicating how many users are waiting for a long waiting time in proportion to the total number of users generated, or a maximum number of waiting users indicating the maximum number of users waiting for the elevator in the floor in the simulation time.

The comprehensive evaluation generating unit 17 outputs the average time, the maximum time, and the minimum time of the simulation times of the elevators 16, such as the time required for the elevators 16 to go to the destination floor registered by the input and start service, the time required for the elevators 16 to start arrival at the destination floor, and the number input by the input device 12, based on the input time from the input device 12.

In addition, the comprehensive evaluation output unit 17 may evaluate and output the waiting time of each user, such as the time required until the user is registered, the time required for the additional movement, the waiting time in the hall, the boarding time, and the like, for each time zone in which the building information is simulated, or the number of persons waiting for the user, such as the maximum number of registered persons waiting for the registration, the maximum number of persons waiting for the hall, and the like.

(2) Simulation example

Fig. 2 shows an example of steps of the user generation process. This process is executed by the in-building user control unit 11. In this process, a user in the simulation is generated based on the system time updated by the simulation unit 10.

In step S1, the in-building user control unit 11 compares the system time with the user generated time. When the system time matches the user generation time, the in-building user control unit 11 executes the subsequent user generation process (step S2), and when the system time does not match the user generation time, executes step S3, which will be described later.

Here, the user generation time is set by the user setting unit 1 based on the user data generated in advance. The user data includes items such as a generation time, a user attribute, a walking time, a generation floor, a generation position, a destination floor, and a destination position, and these items are generated in accordance with the simulation use of the number of persons to be simulated.

In step S3, the in-building user control unit 11 determines whether or not the user has arrived at the entrance hall (hall), and ends the user generation processing when the user has not arrived at the entrance hall, and executes the hall user generation processing when the user has arrived at the entrance hall (step S4). In this floor user creation process, the in-building user control unit 11 creates a user in a simulated manner in the floor.

Fig. 3 shows an example of the registration judgment processing procedure. This process is executed by the in-building user control unit 11. In step S11, the in-building user control unit 11 determines whether or not the specification of the elevator equipment is the door interlock system. When the specification of the elevator equipment is the door interlock system, the in-building user control unit 11 executes an apparatus registration process (step S14) described later, and on the other hand, if the specification of the elevator equipment is not the door interlock system, executes step S12.

In step S12, the in-building user control unit 11 determines whether or not a destination floor registration device is installed. When the destination floor registration device is installed, a device user waiting process (step S15) described later is executed, whereas when the destination floor registration device is not installed, step S13 described below is executed.

In step S13, the in-building user control unit 11 determines whether or not the specification of the elevator device is a method in which a vertical hall button is provided (hereinafter also referred to as "vertical hall button method"). When the specification of the elevator apparatus is the vertical hall button system, a hall button registration process (described later) is executed (step S16).

Specifically, the in-building user control unit 11 determines whether or not the response lamp of the up-down button provided in the elevator hall where the floor is created is on (step S13). When the response lamp is not turned on, the in-building user control unit 11 determines that the up button is pressed as an upward service request when the destination floor is a higher floor than the generation floor, and determines that the down button is pressed as a downward service request when the destination floor is a lower floor than the generation floor. After completion of the destination floor registration, a hall wait process (see fig. 11) described later is executed.

Fig. 4 is a diagram showing an example of the procedure of the apparatus registration process shown in fig. 3. This process is executed by the in-building user control unit 11. In step S21, the in-building user control unit 11 determines whether or not there is a device available. In the present embodiment, for example, a user data table, not shown, is prepared, and if there is a user who uses the device, the in-building user control unit 11 registers user data corresponding to the user in the user data table.

When the user data is registered in the user data table, it indicates that the user uses the device corresponding to the user data, and the device is not idle. On the other hand, when the user data is not registered in the user data table, it indicates that the device is usable. If there is a usable device, the destination floor registration process is executed (step S24). On the other hand, in the case where there is no usable device, step S22 shown below is executed.

In step S22, the in-building user control unit 11 selects the device with the shortest queue. The user data table is set for each device. If the user data is registered in the user data table, the in-building user control unit 11 identifies the device that is not free and cannot be used, and selects the user data table having a smaller number of registered data for the user who has not completed the registration but has already generated and arrived before the device, and registers the user data in order to simulate the queue, as described above. I.e. indicating that the user is queuing before the device with the least number of people in queue. The in-building user control unit 11 selects a device having a smaller device ID among, for example, 1 to 6 devices, when the number of users is the same. After the selection is completed, step S23 described below is executed.

In step S23, the in-building user control unit 11 performs +1 operation for the number of users waiting for the device. This makes it possible to clarify the number of users who are waiting. After the above-described processing is completed, the in-building user control unit 11 performs the device user standby processing described below (step S25).

Fig. 5 shows an example of the device user waiting process shown in fig. 4. This process is executed by the in-building user control unit 11. In step S31, the in-building user control unit 11 determines whether the user is the 0 th person in line. This means determining whether the user is at the head of the row before the device. In the case of the head-up mode, the user can permit the device, that is, for example, in the case of the door interlock mode, the user can operate the door, and in the case of the destination floor registration device mode, the user can input the destination floor.

In the in-building user control unit 11, in order to check whether the user is at the top row, the user data table (table No. (serial number)) is referred to determine whether the user is at the 0 th row. If the user is the 0 th user, the in-building user control unit 11 executes a destination floor registration process (see fig. 6) described later (step S33). After the completion of the destination floor registration process, the in-building user control unit 11 updates n (step S36). On the other hand, if the user is not the 0 th user, the in-building user control unit 11 executes step S32 described below.

In step S32, the in-building user control unit 11 determines whether or not the (n-1) th user is present. In the user data table, if the head user is a user having n equal to 0, the (n-1) th user indicates a user prior to the user in the queue when updating n. n-1 indicates the user who is next in the row, and the n-1 st user indicates the user who is in the row.

In the destination floor registration processing (step S33) described above, when the user is not in front of the apparatus because the user registration is completed, there is certainly no top-ranked user. When this is simulated, it means that the user data whose nth is 0 in the user data table is 0 or NULL, and therefore there is no nth-1 user. The step S34 shown below is executed when the (n-1) th user is present, and the step S35 described later is executed when the (n-1) th user is not present.

In step S34, a waiting process is executed. Since there are users who are queued, i.e. there are users in front, No action is performed, and only the (table No.) of the user data table is updated. After completion of such processing, step S37 described later is executed.

In step S35, the nth-1 st user is updated to the nth user. This corresponds to the action of the user behind the user filling up the queue when the user before under the condition of queuing leaves. In the user data table, the empty (n-1) th user data is overwritten with the nth user data. Then, the nth user data is set to 0 or NULL, so that the queuing condition of the user can be simulated. After the update is completed, step S36 is executed.

In step S36, n performs a +1 update. For example, when n is 1, the refresh operation is performed by setting n to 2. After the update operation is completed, step S37 shown below is executed.

In step S37, it is determined whether n is equal to or greater than the number of waiting users. If the conditions are consistent, the process ends, and if they are not consistent, it means that there is a user waiting, so step S31 is executed.

Fig. 6 shows an example of the destination floor registration process shown in fig. 4. This process is executed by the in-building user control unit 11. In step S41, the user attribute and the destination floor information are registered using the input device 12. Typically, the user information is associated with an ID held by a card inserted into the door. When the door is linked, user information of a general user, a wheelchair user, a VIP, or the like, and a user's destination floor are transmitted from the door security system side to the elevator-side destination floor reservation system.

However, in the present simulation, user information and destination floor information are provided in advance for each user for the sake of simple processing. The required information is input into the input device 12. The required information is stored in a common memory provided in the input device 12. After which the registration of the service request to the elevator side is completed. After the input is completed as described above, step S42 is executed.

In step S42, it is determined whether or not the distribution list information is given. After the door linkage system, the destination floor registration device specification and the input information are inputted, the elevator side determines a single service machine based on the input information. And sending the stand-alone information after the determined service stand-alone is well distributed.

In the simulation, guidance of the user by the elevator-side destination floor reservation system is performed in a simulated manner by storing necessary information in a common memory provided in the landing output device 15. The in-building user control unit 11 determines whether or not the distribution unit is given (step S42).

When the distribution of the individual computers is given, a user update process (see fig. 8) described later is executed (step S43). After the user update processing is completed, the destination floor registration processing is ended.

On the other hand, when the dispenser is not given, a dispenser standby process (see fig. 7) described later is executed (step S44). After the assignment stand-by process is completed, the destination floor registration process is ended.

Fig. 7 shows an example of the distribution stand-alone wait process shown in fig. 6. This process is executed by the in-building user control unit 11. In step S51, it is determined whether a certain period of time has elapsed. Here, in the case of a normal elevator-side destination floor reservation system, after an input process is performed by the registration of a destination floor by a destination floor registration device or an input process in the case of door interlocking, if no service-only machine is assigned or if an abnormal indication is displayed regardless of whether or not an input is made, the input process is performed again by using the registration device as the user's operation. Thus, the user waits after input until some data is output. The above-mentioned time period can be arbitrarily determined, and is usually set to about 3 seconds. If the period of time has elapsed, step S52 is executed, and on the other hand, if the period of time has not elapsed, the stand-alone distribution waiting process is ended.

In this step S52, the re-registration process is executed. Here, as in step S41 of fig. 6, the necessary information is stored in the common memory of the input device 12. After the required information is stored, the re-registration process is terminated.

Fig. 8 shows an example of the user update process shown in fig. 6. This process is executed by the in-building user control unit 11. In step S61, the in-building user control unit 11 stores the distribution unit information output by the hall output device 15 as user data. Since the individual information is distributed to be used when the user takes the elevator, a data structure is prepared so that the individual information can be stored for each user.

In step S62, the in-building user control unit 11 deletes the 0 th user information. Here, the user information itself is not deleted, but a user data table is created for each device, for example, for the purpose of simulating a queue. This is because, after the apparatus registration is performed and the dispensing unit is given, the user does not queue up in front of the apparatus because he or she moves to the dispensing unit. To simulate this operation, the 0 th user information is deleted from the user data table for the queue.

In step S63, the in-building user control unit 11 updates the registration completion time to the current system time. The in-building user control unit 11 can calculate the registration time by subtracting the generation time from the registration completion time by using the present time in the comprehensive evaluation described later. After that, the landing walking process described below (see fig. 9) is executed (step S64).

Fig. 9 shows an example of the landing walking process shown in fig. 8, and fig. 10 shows an example of the walking determination process shown in fig. 9. These processes are executed by the in-building user control unit 11.

In step S71 of fig. 9, the in-building use is performedThe person control section 11 calculates a distance L from the registered distance to the landing_H. The distance information is set to the distance from each unit at the time when the device is set in advance. At the time of deciding the allocation of the individual machines, the distance information set in advance is acquired. For example, at the time of setting the layout of the landing device, the distance L is calculated from the coordinate positions of the center coordinate position of the device and the center position of each stand-alone_H. That is, the distance L is automatically calculated at the time set by the elevator equipment setting unit 3_H. The in-building user control unit 11 includes the distance information set as described above in the user information based on the distribution individual information.

In step S72, the in-building user control unit 11 calculates the walking distance in the system time unit from the walking speed. When the system time is 100ms, the average walking distance of the user in 100ms is calculated in meters.

In step S73, a walking determination process (refer to fig. 10) is executed. In step S73, the in-building user control unit 11 determines whether or not there is a room in which the user can walk. For the determination of the presence or absence of a walkable space, several methods can be considered as described below.

As a first determination method, for example, the maximum number of people waiting at a hall and the number of people waiting at a hall before a hall are automatically set based on the building layout and the size set by the building information setting unit 2 and the elevator equipment setting unit 3. In the present embodiment, when the maximum number of waiting users is the same as the actual number of waiting users in the hall, it is determined that there is no space.

As the second determination method, a method of closely simulating the movement state of the user may be employed. In this method, the occupied size is determined for each user, the shortest movement route from the position of each user to each stand-alone is calculated, and the movement of each user is started in accordance with the movement route. In the simulation, each user moves on its movement route by the amount of walking distance described above according to the update of the system time. Since other users are staying or an obstacle exists in front of the user, it may be determined whether or not a space of the size occupied by the user exists on another moving route instead. Step S82 is performed in the case where there is a space, and on the other hand, step S85 is performed in the case where there is no space.

In step S82, it is determined whether or not there is a room in which the user can walk in the walking direction of the user. For example, in a situation where a plurality of users are waiting for an elevator near a landing entrance, when the elevator moves from its waiting position to the front of an elevator on the inside in the landing, the users may detour without moving straight, although the users stay in front of the elevator on the inside, and may reach the front of the elevator on the inside. As described above, when the user is not staying in front of other users, it is determined that there is a space in the walking direction of the user and the user can go straight forward, and therefore the walking determination process is ended. If the user is staying with another user, it is determined that there is no space in the walking direction of the user, and step S83 is executed. Further, instead of this, for example, the following may be adopted: when the number of waiting persons in the elevator near the entrance of the hall exceeds a certain threshold, it is determined that the user cannot move straight, and it is determined that there is no space in the walking direction of the user.

In step S83, the in-building user control unit 11 determines the distance L from the registered distance to the landing_HPlus the distance of the additional walk. The extra walking distance is the winding distance described above. The detour distance is calculated from the number of waiting persons x the occupied size which is equal to or greater than the threshold value for the staying state of the user, and the detour distance is taken as the extra walking distance.

In step S84, the in-building user control unit 11 adds the walking speed multiplied by the distance of extra walking as penalty term 1 and penalty term 2. Thus, for each user, the time the user is walking extra can be added as a penalty term. After that, the walking determination process is ended.

On the other hand, step S85 is a process in which the user stays at the place because it is determined in step S81 that there is no walking space for the user. In step S85, the in-building user control unit 11 adds the stay time as the penalty term 2. The in-building user control unit 11 calculates the system time × walking distance as a penalty term 1. This makes it possible to evaluate the residence time of the user in the landing as will be described later. Then, the walking determination process is ended.

After the walking determination process is completed, the in-building user control unit 11 calculates the moving distance L of the user based on the equation ((system time-registration time) × walking time) -penalty term 1_psn。

In step S75, the in-building user control unit 11 sets the user' S movement distance L_psnDistance L from the landing from the registered distance_HAnd comparing to judge whether the destination is reached. When the distances are the same, the in-building user control unit 11 determines that the destination is reached, and executes a hall wait process (see fig. 11) described later (step S76), followed by step S77. On the other hand, when the two distances are different, the landing walking process is ended.

In step S77 described above, the hall arrival time is updated as the user data. The hall arrival time can be evaluated by storing the current system time as it is and subtracting the subsequent generation time from the hall arrival time. Thus, the landing walking process is ended.

Fig. 11 shows an example of the hall wait process shown in fig. 9. This process is executed by the in-building user control unit 11. In step S91, it is determined whether or not there is a service floor indication. Which determines whether or not the setting is made by the elevator specification setting section 4. For example, in an elevator facility, when so-called group division of a high floor and a low floor is performed in one group (bank), a user selects any one of groups that can serve a desired destination floor in a landing. Therefore, the service floor display based on the bulletin board or the logo display is clearly performed in the hall, and the user refers to such information and selects any one of the groups to be used. Step S92 is executed when there is a service floor indication, while step S93 is executed when there is no service floor indication.

In step S92, a destination floor that can be served to the destination floor desired by the user is selected. For example, when a user uses 5 floors of 1 to 16 floors as destination floors and an elevator apparatus includes 6 target units, assuming that 1 to 3 units use 1 to 8 floors as service floors and 4 to 6 units use 9 to 16 floors as service floors, the target unit of the user is 1 to 3 units. After the selection of the target stand-alone is completed, step S93 shown below is executed. In the present embodiment, the target individual to be allocated is referred to as an "allocation individual".

In step S93, it is checked whether or not the distribution stand-alone is given. When the allocation of the stand-alone is given, step S94 shown below is executed, and when the allocation of the stand-alone is not given, step S97 described below is executed.

In step S94, it is determined whether or not the hall lantern or the stop floor lantern of the target unit is on. In this simulation, the determination is made based on information in a common memory included in the hall output device 15. In a state where a single machine is assigned, the destination floor reservation system on the elevator side determines whether the destination floor can be normally registered or not, based on the state of the landing output device 15. For example, if 5 floors are originally registered as destination floors, for example, if another floor is displayed or if nothing is displayed, re-registration is necessary.

In consideration of the fact that the setting error of the control parameter of the elevator is correctly simulated, for example, when the user wants to ride the elevator but the elevator car door is closed before riding the elevator, the hall lamp and the stop floor lamp are turned off, and therefore, re-registration is required. Therefore, when the hall lantern or the stop floor lantern of the target stand-alone is turned on, the user waits in line before the target stand-alone (step S95), and the hall waiting process is ended. When the hall lamp or the stop floor lamp of the target stand-alone is turned off, the destination floor registration process is executed (step S96). The destination floor registration processing here is directed to, for example, a destination floor registration device installed in a hall.

In step S97 described above, it is determined whether or not the hall lantern of the target stand-alone is on. In this simulation, the determination is made based on information in a common memory included in the hall output device 15. In the case of the above example assuming the up-down button system, it is determined whether or not the hall lantern in nos. 1 to 3 stand-alone units is on. In the case where the hall lantern is turned on, the user waits in line before pressing the hall lantern to turn on the indicated object stand-alone (step S98). On the other hand, in the case where the hall lantern is turned off, step S99 described below is executed.

In step S99, it is determined whether or not the response lamp of the up-down button of the target group is on. In this simulation, the determination is made based on the virtual storage of the hall output apparatus 15. In the case of the up-down button system, when one button (registration) is pressed, all the relevant buttons are turned on. Therefore, by determining whether or not the hall lantern is lit, it is possible to determine whether or not a service request from the hall is input.

On the other hand, when the hall lantern is off but the landing button is continuously on, the queue position is at the center of the landing due to no instant reservation function, so that the user can queue regardless of which elevator arrives. When the hall lantern is turned on, the user waits in line at the hall center position (step S100). On the other hand, when the hall lantern is off, the re-registration process of the hall up-down button is executed (step S101). The processing contents of the re-registration processing of the landing up and down buttons are the same as in step S16 described above. Thus, the hall wait processing is ended.

Fig. 12 shows an example of the queue processing. This process is executed by the in-building user control unit 11. In step S111, it is determined whether or not the hall lantern in the target direction of the target stand-alone is blinking. For example, when the user is about 1 st stand-alone, if the generation floor as a landing is 4 floors and the destination floor is 9 floors, the user is moving in an upward direction. Therefore, it represents a situation where the door upward is not opened and the indicator lamp is blinked when the No. 1 stand-alone arrives. Here, the case where the number 2 stand-alone arrives and the case where the hall lantern for the number 1 stand-alone goes down blinks are not targeted. If the hall lantern in the target direction of the target stand-alone is blinking, step S112 shown below is executed, whereas if the hall lantern in the target direction of the target stand-alone is not blinking, step S113 described below is executed.

In step S112, the arrival of the elevator is indicated by the blinking of the hall lantern, and the users at the hall are arranged before the single machine in which the hall lantern is blinking, thereby shortening the distance from the user in front.

In the above step S113, it is judged whether or not the target stand-alone is open, and if the target stand-alone is open, step S114 is executed. On the other hand, the queue waiting process is ended with the door closed, and waits until the next system start.

In step S114, an elevator boarding process is performed for the number of persons capable of boarding the elevator for the target individual. For example, when the rated number of persons is 20 and the number of persons already on the elevator is 10, the number of persons on the elevator can be (20 × 0.8) -10 ═ 6 at a loading rate of 80% of the rated number of persons. Thus, if the number of users waiting at the hall is less than 6, all users can ride the elevator, and if the number of users waiting at the hall is 7 or more, the remaining users having more than 6 people are targeted for the re-registration process of the hall waiting process shown in fig. 11.

In step S115, after the boarding of the user waiting at the landing is completed, the current system time is recorded as the boarding time.

Thus, the generation time, registration completion time, landing arrival time, and boarding time are recorded as the evaluation time of the user at the landing. With these times, evaluation of various simulations can be performed. The guideline for the user is controlled in a simulated manner by the in-building user control unit 11 as described above.

Fig. 13 shows an example of a simulation result of a landing layout in which the installation position of the door 105 is poor. In the simulation results shown below, as in fig. 14 to 19 described later, the units are arranged in the order of the unit No. 1, the unit No. 2, and the unit No. 3 from the upper left to the lower left, and the unit No. 4, the unit No. 5, and the unit No. 6 from the upper right to the lower right in the landing of the elevator facility.

The elevators 101 are installed in a predetermined arrangement, and are provided with hall lanterns 102 and a landing destination floor registration device 103, and users 104 waiting for a single machine such as a 2 nd single machine. The user 106 who targets the stand-alone No. 6 stays before the hall lantern 108 is turned on. When certain conditions are superposed, the user 107 passing through the door 105 loses the movable space due to the stay of the user 106 assigned to the 6 units. Therefore, if the number of users 107 increases, the number of users 107 that cannot be registered on the door increases, and the elevator has a single machine that can be serviced, but the time required for registration is deteriorated compared to other simulation conditions and specifications.

Fig. 14 shows a simulation result of a landing layout in which the installation position of the door 205 is good. The landing layout shown in fig. 13 has a margin in space from the entrance 210 to the door 205, compared to the landing layout shown in fig. 13.

Therefore, as shown in fig. 14, even if a large number of users 204 are present in the vicinity of the door 205 and a stand-by state is assigned to a stand-by machine (exemplified as "stand-by machine No. 6"), there is a room in which the users 206 passing through the door 205 can walk, and therefore, even when the number of new users 206 increases, the number of users assigned to the door 205 and who cannot be registered does not increase, and therefore, the performance of the elevator can be sufficiently exhibited. This makes it possible to obtain a good evaluation result without increasing the time required for registration.

Fig. 15 shows a landing layout in which the number of doors 301 provided is extremely small as compared with fig. 14. Since the number of the doors 301 is reduced to half (1) with respect to the number (2) of the doors 205 illustrated in fig. 14, stagnation due to the queue of the users 302 is easily generated in the doors 301, and a limit is generated on the number of users who can pass through the doors 301. Therefore, the number of users 302 who are allocated to the door 301 but cannot be registered increases, and the elevator is likely to serve a single machine, but the time required for registration is deteriorated as compared with other simulation conditions and specifications.

Fig. 16 is a layout for performing a simulation in which hall lantern 402 is lit immediately after a hall up/down button is installed. When the upper and lower hall buttons 401 are pressed, all the upper and lower hall buttons 401 on the floor are turned on. At this time, when the elevator is assigned to the unit 2, the hall lantern 403 of the unit 2 is turned on. The hall lantern 402 other than the number 2 stand-alone is off. It simulates: the number of users 404 who do not exceed the specific threshold stay in front of the single machine (single machine No. 2) whose hall lantern 403 is on, while the number of users 405 who wait for the number of users who exceed the specific threshold wait in a queue.

Fig. 17 is a layout for performing a simulation in a mode in which a hall up-down button is provided and a hall lantern is not lit immediately. When the upper and lower hall buttons 501 are pressed, all the upper and lower hall buttons 501 on the floor are turned on. However, even if the number 2 stand-alone is assigned, the hall lantern 502 near the number 2 stand-alone is not lit. The user 503 is shown queuing near the center of the landing because of the inability to identify the individual assigned.

Fig. 18 is an example of simulation results in the case where the wheelchair elevator is a number 1 stand-alone car in the system in which the hall up-down type button is provided and the hall lantern is instantly turned on. When the upper and lower hall buttons 601 are pressed, all the upper and lower hall buttons 601 of the floor are turned on. In the case of assigning the stand-alone No. 2, the hall lantern 602 of the stand-alone No. 2 is lit. Wheelchair users 603 press the wheelchair landing buttons located near stand-alone No. 1 and queue up as shown. Therefore, the time required before the registration of the wheelchair user 603 becomes longer, which results in poor evaluation.

Fig. 19 shows an example of simulation results in the case where the wheelchair elevator is a 3 rd stand-alone car in the system in which the hall up/down buttons are provided and the hall lantern 702 is instantly turned on.

When the upper and lower hall buttons 701 are pressed, all the upper and lower hall buttons 701 on the floor are turned on. At this time, in the case of assigning the number 2 stand-alone, the hall lantern 702 of the number 2 stand-alone is turned on. For example, the wheelchair user 703 can press the wheelchair landing button 704 near the stand-alone No. 3 to assign the stand-alone No. 3. Therefore, the hall lantern 702 of the 3 rd stand-alone is turned on, so that the wheelchair user 703 can register in advance, and the time required before registration is shortened, thereby making it a good evaluation.

(3) Effects of the present embodiment

As described above, in the elevator simulator of the above embodiment, the in-building user control unit 11 generates a user in a simulated manner so that the user takes a behavior corresponding to the elevator information and the building information, and performs simulation.

With this configuration, not only the influence of the installation of the building equipment, but also the influence of the specification of the elevator equipment on the user and the influence of the behavior of the user can be evaluated more accurately.

(4) Other embodiments

The above embodiments are illustrative of the present invention, and are not intended to limit the present invention to these embodiments. The present invention can be implemented in various forms without departing from the gist thereof. For example, in the above-described embodiment, the processing of various programs has been described sequentially, but the present invention is not particularly limited thereto. Therefore, the processing sequence can be changed or the processing can be performed in parallel as long as the processing results do not contradict each other.

Industrial applicability of the invention

The invention can be widely applied to simulators for carrying out simulation corresponding to elevator equipment.

Description of the reference numerals

1 … … user setting unit, 2 … … building information setting unit, 3 … … elevator equipment setting unit, 4 … … elevator specification setting unit, 5 … … time zone setting unit, 10 … … simulation unit, 11 … … user control unit in the building, 12 … … input device, 13 … … elevator group management control unit, 14 … … elevator control unit, 15 … … landing output device, 16 … … elevator, 17 … … comprehensive evaluation output unit, 100 … … simulation system.

Claims

1. An elevator emulator, comprising:

an elevator equipment setting part for setting elevator information of the elevator equipment comprising an input device and an output device;

an elevator specification setting unit that sets a specification of the elevator equipment including specifications of the input device and the output device;

a building information setting unit for setting building information relating to the building specification of the whole building;

a user setting unit for setting user information including a generation time, a generation floor, a destination floor, and an attribute of a user generated by simulation in the elevator equipment;

an in-building user control unit for controlling the behavior of the user;

an elevator control part for managing the operation by controlling the elevator equipment;

a service request input device for sending a service request from the in-building user control unit to the elevator control unit; and

landing output means for outputting a result in response to the service request,

the user control unit in the building simulates and generates the user so as to take a behavior based on the elevator information, the specifications of the input device and the output device, and the building information.

2. The elevator emulator of claim 1, wherein:

the system includes a comprehensive evaluation generation unit that outputs at least one of the elevator information, a time required for each user to register, a movement time, a time taken for additional movement, a landing waiting time, and a boarding time from when the user gets into the elevator to when the user leaves the elevator, as a result of the simulation.

3. The elevator emulator of claim 1, wherein:

the in-building user control unit selects specific building information and specific elevator information, which are settings closest to the building information and the elevator information, from other building information regarding building specifications of the entire other building that is actually operating and other elevator information regarding elevator devices of the other building, and sets the user information based on the specific building information and the specific elevator information.

4. The elevator emulator of claim 1, wherein:

the building information setting unit and the elevator device setting unit select specific building information and specific elevator information that are settings closest to the building information and the elevator information from results of simulations performed in the past, and set a building specification based on the specific building information and an elevator device based on the specific elevator information.