WO2019030816A1 - ビルシミュレーター及びビルシミュレーション方法 - Google Patents

ビルシミュレーター及びビルシミュレーション方法 Download PDF

Info

Publication number
WO2019030816A1
WO2019030816A1 PCT/JP2017/028722 JP2017028722W WO2019030816A1 WO 2019030816 A1 WO2019030816 A1 WO 2019030816A1 JP 2017028722 W JP2017028722 W JP 2017028722W WO 2019030816 A1 WO2019030816 A1 WO 2019030816A1
Authority
WO
WIPO (PCT)
Prior art keywords
building
user
elevator
floor
simulation
Prior art date
Application number
PCT/JP2017/028722
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
貴大 羽鳥
訓 鳥谷部
正康 藤原
孝道 星野
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to JP2019535469A priority Critical patent/JP6880196B2/ja
Priority to PCT/JP2017/028722 priority patent/WO2019030816A1/ja
Priority to CN201780093651.1A priority patent/CN111108500B/zh
Publication of WO2019030816A1 publication Critical patent/WO2019030816A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/16—Real estate

Definitions

  • the present invention relates to a building simulator, and more particularly to a building simulator and a building simulation method suitable for designing a building installation for various applications having building installation such as an elevator.
  • Patent Document 1 Setting or recommending parameter settings for control devices in building equipment with maintenance such as elevators, air conditioners, security systems, and solar power generation, or recommending or offering to equipment owners such parameters and optional devices to be added later during equipment operation Is desired.
  • a parameter and equipment recommendation device for equipment recommends change values of control parameters and additional optional equipment for a recommended object of a building equipment based on operation history data, building equipment condition data, and building equipment parameter option data.
  • a simulation evaluation unit performs evaluation by simulation when a target is applied, and a recommendation result output unit that outputs the recommendation candidate when the evaluation result determination unit determines to recommend a recommendation candidate.
  • the present invention makes it possible to evaluate the degree of influence on the user by the elevator installation and to evaluate the flow line of the user, and provide a building simulator and a building simulation method capable of suitably simulating a building for various uses.
  • a building simulator is installed in a building specification including at least a layout in a building to be set, elevator information including at least a specification on an elevator installation to be set, and the building It is characterized by comprising a simulation unit that evaluates at least the layout on the condition that the flow line of the user moving in the building changes based on the user information including at least the attribute information of the user using various facilities.
  • the building simulation method is a building simulation method for evaluating a building having at least a simulation unit, including a building specification including at least a layout of the set building and at least an elevator installation set. On the condition that the flow line of the user moving in the building changes based on the elevator information including the specification and the user information including at least attribute information of the user who uses various facilities installed in the building At least the layout is evaluated by simulation.
  • a building simulator and a building simulation method capable of suitably simulating a building for various applications can be provided, which enables evaluation of the degree of influence of the elevator installation on the user and evaluation of the flow line of the user. It becomes possible. Problems, configurations, and effects other than those described above will be apparent from the description of the embodiments below.
  • FIG. 1 It is a whole schematic block diagram of a building simulator of Example 1 concerning one example of the present invention. It is a flowchart which shows the user generation
  • Comprising It is an example of a layout of the lantern un-lighting specification of a up-and-down hall board button specification, and a display example of a simulation result. It is an example of a display screen of the display part shown in FIG. 1, Comprising: It is an example of a layout of the wheelchair specification of an up-and-down hall board specification, and a display example of a simulation result. It is an example of a display screen of the display part shown in FIG. 1, Comprising: It is another display example of the layout of the wheelchair specification of an up-and-down-type hall button specification and a simulation result.
  • FIG. 1 is an overall schematic configuration diagram of a building simulator according to a first embodiment of the present invention.
  • the building simulator 1 includes a user setting unit 2, a building information setting unit 3, an elevator equipment setting unit 4, an elevator specification setting unit 5, a time zone setting unit 6, and a simulation unit 10. Ru.
  • the user setting unit 2, the building information setting unit 3, the elevator equipment setting unit 4, the elevator specification setting unit 5, and the time zone setting unit 6 may use, for example, a specific storage area (virtual area) in the server. It is realized by providing. Therefore, the simulation unit 10, which will be described in detail later, reads out from the specific storage area (virtual area) and executes various processes.
  • the simulation unit 10 includes an in-building user control unit model 11, an input device model 12, an elevator group management control unit model 13, an elevator control unit model 14, a landing output device model 15, an elevator model 16, an overall evaluation output unit 17, and , And the display unit 18.
  • the storage unit 17 is realized by, for example, a processor such as a CPU, a ROM storing a program, and a storage device such as a RAM temporarily storing data etc. of the process of executing the program read from the ROM.
  • the user setting unit 2 is a module for setting information on the user, and is realized by providing a specific storage area (virtual area) in the server as described above. For example, an occurrence floor that sets the floor where the user enters the elevator hall, a destination floor that sets the target floor with the use of the elevator, a user attribute such as a general user or a wheelchair user or a VIP user, The walking speed which is the speed at which the user moves in the elevator hall, and the generation distribution such as the generation ratio of the user for each generation floor or destination floor are set.
  • the building information setting unit 3 is a module for setting building information, and is realized, for example, by providing a specific storage area (virtual area) in the server as described above. For example, it is possible to set the number of floors of a building and the distance between floors (also referred to as floor high distance). Furthermore, set the number of people in the building to set how many people will be present on each floor of the building. In addition, building specifications on each floor can be set. With the building specification, for example, information such as a lobby floor, a parking lot floor, and a common floor can be set. In other words, it is possible to set the layout in the building.
  • the elevator installation setting unit 4 is a module for setting up elevator installation, and is realized by providing a specific storage area (virtual area) in the server as described above. For example, how many elevator cars will be installed, where on the floor the elevator cars will be installed, and as an input device, a destination floor registration device for registering a destination floor at the platform, or above the platform. Gate connection facility to perform service request for going in the direction or going down, and further, install a gate at the entrance of the landing and register the destination floor when passing the gate, or when the elevator arrives as an output device When you register the destination floor at the platform, the destination floor stop will guide you to the planned floor of each unit when you register the destination floor at the platform.
  • the destination floor stop floor light is a display unit (for example, LED display) provided on the upper part of each car, and the user presses a desired destination floor specification button at the landing (elevator hall) (or When it is touched, the designated destination floor is displayed.
  • the elevator specification setting unit 5 is a module for setting the specification of the installed elevator, and is realized, for example, by providing a specific storage area (virtual area) in the server as described above. For example, the speed of the elevator, the width of the door, the number of people, etc. may be mentioned. Further, as the operation specification, the moment when the service request is created from the landing button, the presence or absence of an immediate reservation function of lighting the elevator lantern of the car whose service has been determined for the landing button may be mentioned.
  • the time zone setting unit 6 is a module that sets a time zone for executing a simulation, and is realized by providing a specific storage area (virtual area) in the server as described above.
  • the elevator operation status in a building differs depending on the time of day. For example, in the case of an office building, there are many cases where users flow into the building in the working hours, and as the movement of the users, the floor of each user is used as the destination floor from the lobby floor. In the first half of the lunch time zone, if there is a dining room floor or floor where a restaurant is present in the building, a user who moves from the user's sitting floor of each user to the above mentioned cafeteria floor or floor where a restaurant is present Will increase.
  • the occurrence distribution setting is set to be relevant.
  • the generation distribution may be determined, or may be determined based on the on-site measurement data of past similar building specifications.
  • the method for automatically setting the occurrence rate when the time zone is set is the number of people present on each floor from the lobby floor when the attendance time zone is set.
  • Set the occurrence rate for Specifically, if the number of users going from the lobby floor to each floor is 40% in 30 minutes of working hours 8: 15 to 8: 45, the number of people on the 5th floor is 100, and the presence on the 4th floor is 100 people. If the building has 80 people, 40 users from the lobby floor to the 5th floor and 32 users from the 4th floor will be generated.
  • the method of setting the occurrence distribution for each given time zone indicates setting the occurrence floor of the occurrence floor, the user's occurrence rate for each destination floor, and the like for each time zone. Specifically, between 8:15 and 8:30, 15% of the users going from the lobby level to the other floors, between 8:30 and 8:45, going from the lobby level to the other floors Person refers to setting such as 25%.
  • the width of the time zone can be set arbitrarily, and the setting value of the occurrence distribution can also be set according to the ratio, and can be set according to the floor in detail.
  • 200 users generated from the lobby floor 10 users generated from the first floor, 80 users for the fourth floor, 130 users for the fifth floor, and so on
  • There are 125 users from the lobby floor to the 5th floor 75 users from the lobby floor to the 4th floor, 5 users from the 1st floor to the 4th floor, and 5 users from the 1st floor to the 5th floor. It is also possible to set the name and details.
  • the method of determining the generation distribution for each time zone depending on the building application means that the generation ratio is automatically set when the above-mentioned time zone is set, but the setting value fluctuates depending on the building application.
  • the time zone and the distribution of occurrence also vary depending on the building application.
  • the method of setting the generation distribution for each time zone based on the past measurement data of similar building specifications is based on, for example, whether or not the use of the building matches if the building information or the building application is similar. Judgment and other information, such as the number of floor of the building, total floor high distance which is the maximum moving distance of the elevator moving up and down the hoistway, the number of people in the building, and the elevator installation scale are prioritized And display the building information to be simulated and the building information within an error of 10%. Therefore, when a building similar to the building to be simulated is selected, the generation distribution of users in each time zone is set from the operation information of the selected building.
  • These generation distributions are set based on information on the elevator operation, for example, on the basis of measurement data by load sensors installed in the elevators, based on information on the number of users who get on and off the floors. By simulating the local usage situation, it is possible to simulate the usage situation when the building operation is started to some extent at the installation planning time.
  • the occurrence distribution is set based on information when the destination floor registration device is pressed, log information from an external device, for example, building security unlocking information, or log information from a camera. It may be a method. When setting of these pieces of information is completed, simulation can be performed.
  • the simulation unit 10 for executing the simulation is set to, for example, 100 msec as a simulation execution cycle (hereinafter referred to as a system time), constantly updates the system time, and activates each control.
  • the control unit to be started is set for each time zone set by the time zone setting unit 6, and the in-building user control model 11 which controls the floor movement of the user generated for simulation and getting on / off to the elevator, the building From input device model 12 for setting service request to elevator from internal user control model 11, elevator group management control model 13 for performing operation management in response to service request, elevator group management control model 13 Guide to the user from the elevator control unit model 14 which controls the elevator car or the opening and closing of the door in response to the received service request, the elevator group management control unit model 13 or the elevator control unit model 14 Station output device model 15 that Constituted by the Tar model 16.
  • the in-building user control unit model 11, the input device model 12, the elevator group management control unit model 13, the elevator control unit model 14, the floor output device model 15, and the elevator model 16 are an in-building user control unit and an input, respectively. It is a model for simulating an apparatus, an elevator group management control unit, an elevator control unit, a landing output device, and an elevator.
  • the evaluation under the simulation conditions set by the comprehensive evaluation output unit 17 is finally output.
  • the elevator wait time from arrival at each person's platform output from the in-building user control model 11 to the elevator ride, the boarding time from getting on the elevator to getting off, and the platform There is a service completion time from when you arrive to the destination floor.
  • define elevator waiting time of 60 seconds or more as a long waiting time, and output the long waiting rate, to what extent the number of users with long waiting times was present, with respect to the total number of people generated.
  • the maximum waiting number indicating the maximum number of users waiting for the elevator at the platform under simulation is output.
  • each elevator model 16 is input to the input floor. It took from the time it took to service and the time when the destination floor of the elevator was entered (when the destination button in the car was pressed after getting into the car of elevator model 16) to arrive at the destination floor. The time, the average time during simulation execution such as the number of input device models 12 input, the maximum time, and the minimum time are output.
  • the evaluation output from the elevator group management control unit model 13 described above is output from the elevator control unit model 14 when there is no group management specification or when only one elevator is to be simulated.
  • the operation and time management by the device are performed.
  • the elevator output status changes according to the equipment and specifications set by the elevator installation setting unit 4 and the elevator specification setting unit 5, and the movement of the user changes according to the setting status.
  • the operation of the building simulator 1 will be described below with reference to FIGS. 2 to 12 using flowcharts of these movements.
  • FIG. 2 is a flowchart showing a user generation processing flow by the simulation unit 10 configuring the building simulator 1 shown in FIG.
  • the generation process of the user is performed according to the system time updated by the simulation unit 10.
  • step S11 the system time and the user generation time are compared, and if the generation time matches, the process proceeds to step S12 as processing for generating the user. On the other hand, if they do not match, the process proceeds to step S13.
  • the user generation time uses user data created based on the user setting unit 2 set in advance.
  • the user data is composed of generation time, user attribute, walking time, generation floor or place, and further, destination floor or destination place, and these data are created for the number of people to be simulated.
  • step S12 a user generation process is performed. Details of the user generation process will be described later with reference to FIG. When the generation process is completed, the process proceeds to step S13.
  • FIG. 3 is a flowchart showing the registration determination processing flow by the simulation unit shown in FIG. 1, and is a detailed flow of the user generation processing in step S12 shown in FIG.
  • step S121 it is determined whether it is a gate interlocking specification. If it is a gate interlocking specification, device registration processing (for example, gate user registration processing) is executed as shown in step S124. The details of the device registration process (for example, the gate user registration process) will be described later with reference to FIG. On the other hand, if it is not the gate interlocking specification, the process proceeds to step S122.
  • S122 it is determined whether a registration device (destination floor registration device) is installed. If the registration device is installed, destination floor registration processing is executed as shown in step S125. The details of the destination floor registration process will be described later with reference to FIG. On the other hand, if the registration device (destination floor registration device) is not installed, the process proceeds to step S123.
  • step S123 it is determined whether the landing button specification is of the upper and lower type. If it is the upper and lower landing button specification, the process proceeds to step S126, and the upper and lower landing button registration processing is executed. Specifically, it is determined whether the response light of the up-and-down button installed at the elevator hall of the generation floor is on, and if not, if the destination floor is above the generation floor, the upper floor The upward button is pressed as a service request in the direction. If the destination floor is lower than the occurrence floor, the down button is pressed as a service request in the downward direction.
  • step S123 determines whether the above-mentioned action by the user occurs as an event of simulation conditions by the building simulator 1 of the present embodiment as the pressing of the upward direction button and the pressing of the downward direction button.
  • step S124 for example, gate user registration processing
  • destination floor registration processing in step S125 the processing proceeds to the hall standby processing described in FIG.
  • FIG. 4 is a flowchart showing the registration processing flow of the destination floor registration device by the simulation unit 10 shown in FIG. 1, and is a detailed flow of the device registration processing (for example, gate user registration processing) in step S124 described above.
  • step S1241 it is determined whether there is an available destination floor registration device. For example, a data table is prepared, and if there is a user who uses the destination floor registration device, user data is registered in this table. If data is stored in this table, it indicates that the destination floor registration device is used, and if no data is stored, it indicates that the destination floor registration device can be used. If there is an available destination floor registration device, the destination floor registration process shown in step S1244 is executed. On the other hand, if there is no available destination floor registration device, the process proceeds to step S1242.
  • step S1242 the destination floor registration device with the smallest alignment is selected.
  • the above-described data table is provided for each destination floor registration device.
  • user data is stored in the data table, it is as described above that it is recognized as a currently unavailable destination floor registration device, but registration is not complete in order to simulate the alignment of the user on the simulation.
  • select a data table with a small number of data stored in the data table and store the user data. That is, it indicates that the destination floor registration device with the smallest number of users is aligned.
  • a destination floor registration device with a small device ID is selected. When the selection is completed, the process proceeds to step S1243.
  • step S1243 +1 is added to the device standby user number (the destination floor registration device standby user number) +1 (the destination floor registration device standby user number is incremented by “1”). This makes it possible to clarify the waiting user. If it completes, it will progress to step S1245 and will perform apparatus user waiting processing (destination floor registration apparatus user waiting processing).
  • FIG. 5 is a flowchart showing a landing destination floor standby processing flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of the device user standby processing (destination floor registration device user standby processing) shown in step S 1245 in FIG. is there.
  • step S21 it is determined whether or not the user (self) is the 0-th arranger. That is, it is determined whether the user (self) is aligned at the beginning.
  • step S23 the destination floor registration process shown in step S23 is executed. The details of the destination floor registration process will be described later with reference to FIG. When the destination floor registration process is completed, the process proceeds to step S26. On the other hand, if the user is not the 0th user in step S21, the process proceeds to step S22.
  • step S22 it is determined whether the n-1st user exists.
  • step S24 a standby process is performed. Since there is a lined up user and the user is in front of the user, it indicates that the operation is not performed, and only the update of the table No. is executed. If it completes, it will progress to step S28.
  • step S25 the n-1st user is updated to the nth user. This corresponds to the task of packing up the line if there are no users in front of you in an aligned situation.
  • the n-th user data is copied to the n-1st data table which is empty. After that, by setting the nth data table to “0” or “NULL”, it is possible to simulate the aligned situation on the simulation.
  • step S26 n is updated.
  • the process proceeds to step S28.
  • step S28 it is determined whether n is a value larger than the number of waiting users. If n is a value larger than the number of standby users, the process ends. If n is equal to or less than the number of standby users, it means that there are standby users in the user, so the process returns to step S21. .
  • FIG. 6 is a flowchart showing the destination floor registration processing flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of step S23 in FIG.
  • step S 231 user attribute information and destination floor information are registered in the input device model 12.
  • the user's information is associated with the ID of the card held over the gate, and from the security side the user attribute information of a general user or a wheelchair user or VIP etc.
  • the user information and the destination floor of the user are transmitted from the elevator model 16 side.
  • user data and destination floor information are provided in advance for each user as user data in order to simplify processing, and data necessary for input can be controlled by the in-building user
  • the part model 11 is input to the input device model 12.
  • the registration of the service request on the elevator model 16 side is completed by storing necessary information on the memory held by the input device model 12.
  • the process proceeds to step S232.
  • step S232 it is determined whether assigned machine information has been assigned.
  • the elevator model 16 side determines the service number with respect to the input information, and transmits the number information as the allocation number information.
  • the transmission method simulates, on the simulation, implementing guidance for the user from the elevator model 16 side by storing necessary information on the memory held by the landing output device model 15.
  • step S233 the user update process is executed. Details of the user update process will be described later with reference to FIG. Thereafter, when the process of step S233 is completed, the process ends.
  • the assigned machine is not assigned, the assigned machine waiting process of step S234 is executed. The details of the assigned car waiting process will be described later with reference to FIG. Thereafter, when the process of step S234 is completed, the process ends.
  • FIG. 7 is a flowchart showing an assignee stand-by process flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of step S234 in FIG.
  • step S2341 it is determined whether a predetermined time has elapsed.
  • a predetermined time In the case of a normal destination floor reservation system, after performing input processing at the time of destination floor registration device or gate interlocking, if input but not assigned or abnormal display is displayed, the user's movement is again Implement the registration device input. Therefore, there is an action of waiting until some data is output after input.
  • the fixed time can be arbitrarily determined, and is set, for example, in about 3 seconds.
  • step S2342 registration (re-registration processing) of the user attribute and the destination floor information is executed again.
  • necessary input information is stored on the memory held by the input device model 12 as in step S231 of FIG. 6 described above.
  • FIG. 8 is a flowchart showing a user updating process flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of step S233 in FIG. 6 described above.
  • step S2331 the assigned elevator information output by the landing output device model 15 is stored on the user data side.
  • step S2332 the 0th user information is deleted from the standby user information. What is deleted here is not the user information itself, but the user information in the data table created for each destination floor registration device for simulating the alignment.
  • FIG. 9 is a flowchart showing a landing walk processing flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of step S2334 in FIG. 8 described above.
  • step S31 the distance L H from the registered distance to the landing (elevator hall) is acquired.
  • the distance information when the landing device such as the destination floor registration device is set in advance, the distance to each car is set, and when the assigned car is determined, only the information set in advance is acquired . For example, when the layout of the landing (elevator hall) is set, the distance is calculated from the central coordinate position of the landing device such as the destination floor registration device and the coordinate position of the central position of each car.
  • step S32 the walking distance in system time units is acquired from the walking speed. If the system time is 100 msec units, the walking distance is calculated in m units in 100 msec units.
  • step S33 a walking determination process is performed.
  • the details of the walking determination process will be described with reference to FIG.
  • FIG. 10 is a flowchart showing the walking determination processing flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of step S33 in FIG.
  • step S331 the presence or absence of a space for the user to walk is determined.
  • the space There are several ways to determine the space. For example, according to the layout and size of the building set by the building information setting unit 3 and the elevator installation setting unit 4, the maximum number of waiting users at the landing (elevator hall) and the number of waiting users before each landing are automatically set.
  • a method may be used that closely simulates the movement situation of the user. That is, the occupancy size is determined for each user, and the shortest movement route from the position of the destination floor registration device of the user to each car is created. Then, the user starts moving according to the created moving route. The user travels along the movement path as described above in response to the update of the system time. Therefore, there may be a method of determining whether there is a person's residence or obstacle in front of the user's eyes, and a space for the user's occupied size exists on another moving route. If there is a space, the process proceeds to step S332. If there is no space, the process proceeds to step S335.
  • step S332 it is determined whether there is a space in the walking direction. For example, assuming a situation in which a plurality of people are waiting in the elevator near the entrance (elevator hall) entrance, when moving from that position to the front of the elevator in the back, there is a stagnation of the user in front of the eyes. If you detour, you may reach the front of the elevator in the back. As described above, when there is no dwell in front of the eyes, it is determined that there is a space in the walking direction, and since it is possible to go straight without doing anything, the walking determination processing is ended. On the other hand, when there is stagnation in front of the eyes, it is determined that there is no space in the walking direction, and the process proceeds to step S333. Further, for example, when the number of elevator waiting people near the entrance (elevator hall) entrance exceeds a certain threshold, it may be determined that the straight traveling is not possible, and a method of determining that there is no space in the walking direction may be used.
  • step S333 an extra walking distance is added to the distance L H from the registered distance to the landing.
  • the extra walking distance is a distance corresponding to the above-mentioned bypass.
  • the staying condition of the user in front of the eyes is calculated as the distance for detouring by the number of waiting persons above the threshold ⁇ occupied size, and this distance is taken as the distance for extra walking.
  • a penalty 1 is set to a value obtained by dividing the extra walking distance by the walking speed. As a result, it is possible to store the extra time for walking as a penalty 1 for each user.
  • the walking determination processing ends.
  • step S335 it is determined that there is no space for walking in step S331, so the user will stay on the spot.
  • Penalty 2 it is set as the residence time (dwelling time).
  • step S34 the movement distance L psn of the user is calculated by (system time-registration time-penalty 1) ⁇ walking speed. If calculation is completed, it will progress to step S35.
  • step S35 as compared to the distance L H from the distance that registered the moving distance L psn user to a landing (elevator hall), it is judged whether the same or not. That is, it is determined whether it has arrived at the destination.
  • step S36 If it is determined that the movement distance L psn the user is the same as the distance L H from the distance registered until landing (elevator hall), it is determined that the destination has been reached, the hole standby process of step S36 After execution, the process proceeds to step S37. Details of the hole standby process will be described later with reference to FIG. On the other hand, as a result of the determination, if the moving distance L psn of the user is not equal to the distance L H from the registered distance to the landing (elevator hall), the landing walking process is ended as it is. In step S37, the hall arrival time is updated as user data. The arrival time of the hall can be evaluated by storing the current system time as it is and subtracting the occurrence time from the arrival time of the hall later. With the above, the platform walk processing ends.
  • FIG. 11 is a flowchart showing the hole standby processing flow by the simulation unit 10 shown in FIG. 1, and is a detailed flow of step S36 in FIG.
  • step S361 it is determined whether or not there is a service floor display (whether or not there is a split express driving specification). It is determined whether or not this is set by the elevator installation setting unit 4. For example, when high-rise and low-rise banks are divided into one bank, the user at the landing (elevator hall) selects a bank that can serve his / her destination floor. Therefore, a service floor display by a signboard or a sign display is provided at a landing (elevator hall), and the bank used by oneself is selected using such information. If there is a service floor display, the process proceeds to step S362. On the other hand, if there is no service floor display, the process proceeds to step S363.
  • step 362 only the target machines that serve their own destination floor are selected.
  • the destination floor (destination floor) of the user is the fifth floor
  • the first to third units are the first to eighth floors
  • the fourth to sixth units are the first floor and the ninth to sixteenth floors as service floors.
  • the target machine of the user is the first to third machines.
  • step S363 it is confirmed whether or not the assigned machine has been assigned. If an assigned number is assigned, the process proceeds to step S364. If no assigned number is assigned, the process proceeds to step S367.
  • step S364 it is determined whether the hall lantern or the stop floor indicator light of the target car is on. In this simulation, it judges from the virtual memory which the landing output device model 15 holds. It is determined whether the elevator model 16 side can be properly registered in the state where the assigned car is assigned, according to the situation of the hall output device model 15. For example, although it is supposed that the fifth floor is registered as the destination floor, if another floor is displayed or nothing is displayed, re-registration is required. In addition, in order to correctly simulate the setting error of the control parameter of the elevator, although it was tried to get in, when the elevator door is closed before getting on, the lantern and the stop floor indicator light are turned off, so re-registration is required.
  • step S365 when the hall lantern or the stop floor indicator light of the target machine is on, as shown in step S365, the process waits for alignment before the target machine and ends the processing. On the other hand, if the hall lantern or the stop floor indicator light of the target car has been extinguished, the destination floor registration process described above is executed in step S366.
  • the registration process here is targeted at the destination floor registration device installed in the landing (elevator hall).
  • step S367 it is determined whether the hall lantern in the target machine is on. In this simulation, it judges from the virtual memory which the landing output device model 15 holds. This assumes upper and lower button specifications, and in the case of the example described above, it is determined whether or not the hall lanterns in the first to third units are on. If the hall lanterns in the first to third units are on, the process proceeds to step S368, and the process waits for alignment before the target number machine. On the other hand, if the hall lanterns in the first to third units are off, the process proceeds to step S369.
  • step S369 it is determined whether the response lights of the upper and lower buttons of the target bank are on. In this simulation, it judges from the virtual memory which the landing output device model 15 holds.
  • the up and down type button specification when one button is pressed (registered), all linked buttons light up. Therefore, it can be determined whether or not the service request from the landing (elevator hall) is input by determining whether or not the light is on. Also, if the lantern is off but the landing button is on, the alignment position will be at the center of the landing (elevator hall) so that it can be aligned no matter which elevator arrives, since there is no immediate reservation function. .
  • step S370 If the response light is on, the process proceeds to step S370, and the process waits for alignment at the center of the landing (elevator hall). On the other hand, if the response light is off, the process proceeds to step S371, and re-registration processing of the landing up-down button is performed.
  • the processing content of the re-registration processing is the same as step S126 in FIG. 3 described above. With the above, the landing standby processing ends.
  • FIG. 12 is a flowchart showing the alignment standby process flow by the simulation unit 10 shown in FIG.
  • step S41 it is determined whether or not the lantern in the target direction of the target car has blinked. For example, in the case where the user is targeting the first car, if the landing floor is the fourth floor and the destination floor is the ninth floor, the upward movement direction is taken. Therefore, when the first car arrives, the upward door does not open, and the lantern blinks. Here, it does not apply to the arrival of the second unit or the flashing of the downward direction of the first unit. If the lantern in the target direction of the target machine is blinking, the process proceeds to step S42. If the lantern in the target direction of the target machine does not blink, the process proceeds to S43.
  • step S42 in order to indicate the arrival of the elevator, it is aligned in front of the flashing machine. Alternatively, the alignment distance is shortened, and the process proceeds to step S43.
  • step S43 it is determined whether the target car has been opened. If it is determined that the door is open as a result of the determination, the process proceeds to S114. On the other hand, if the door is closed, the alignment standby process is completed, and the system waits for the next system startup.
  • step S44 the boarding process is performed for the number of persons who can get on the target car. For example, it is assumed that the maximum number of people is 20 and the number of people already on board is 10.
  • step S45 when the boarding is completed, the current system time is stored as the boarding time. As described above, the generation time, the registration completion time, the landing (elevator hall) arrival time, and the boarding time are stored as evaluation times at the user's platform (elevator hall). These stored times can be used to evaluate various simulations.
  • the movement of the user is controlled by the in-building user control unit model 11 constituting the simulation unit 10.
  • This control monitors input and output information to the elevator model 16 side by the input device model 12 and the landing output device model 15.
  • the input device model 12 is configured, for example, by a vertical landing button or a landing destination floor registration device.
  • the elevator installation setting unit 4 can set the position of the input device model 12 at an arbitrary coordinate according to the landing (elevator hall) layout.
  • the input device model 12 has different data required for input depending on the device, they are all configured by data included in user information.
  • the user is based on user information, occurrence floor information, and destination floor information for data of whether the service request from the landing floor to the upper floor or the service request to the lower floor.
  • the input is storage of information in a virtual memory included in the simulator, and is configured by a shared memory between the in-building user control unit model 11 and the input device model 12.
  • the information is set as the input in the virtual memory included in the simulator. Since the amount of information is larger compared to the upper and lower landing buttons, when the equipment is determined by the elevator installation setting unit 4, a data size corresponding to each input device is secured on the shared memory.
  • the elevator group management control unit model 13 automatically sets a group management specification based on the information set by the building information setting unit 3, the elevator equipment setting unit 4, and the elevator specification setting unit 5. For example, when setting the distance between floors, selecting the elevator suitable for the input device model 12 such as the number of elevators, elevator speed, etc., calculation of estimated arrival time for the purpose of minimizing waiting time. Automatically set parameters to be used for actual control, such as necessary parameters, from each setting.
  • the control to assign only the approaching elevator if it is the landing button of the upper and lower type, if it is the landing button of wheelchair specification, the control to assign only the approaching elevator, if the landing button of VIP specification is installed, VIP No.
  • Carry out operation control of the elevator according to each specification such as executing control that does not respond to the new platform request for the car.
  • the destination floor registration device by knowing the destination floor at the landing (elevator hall), control is performed to suppress the number of stop floors according to the destination floor, and driving is performed to increase the transport capacity.
  • control according to the set elevator specification can also be implemented. For example, when the upper and lower landing buttons are pressed, control to switch ON and OFF is performed on the lantern which is the landing output device model 15 by selecting the specification to turn on the lantern immediately or the specification not to turn on the lantern.
  • the elevator control unit model 14 mainly executes control of a single elevator to control opening / closing control of a door, stopping of the elevator, departure, acceleration, deceleration, and travel processing. Further, similarly to the elevator group management control unit model 13, the specifications of the elevator model 16 are automatically set based on the information set by the elevator specification setting unit 5. For example, parameters related to the above-described control, such as the setting of the distance between floors and the elevator speed, are automatically set.
  • the elevator model 16 shows a car and a door where the user actually gets on and off, and changes the open / close state of the door, position information of the car, etc. in response to a command from the elevator control unit model 14 It is responsible for permitting boarding.
  • the comprehensive evaluation output unit 17 collectively outputs the simulation result.
  • the elevator wait time from arrival at each person's platform output from the building user control model 11 to the elevator ride the boarding time from boarding to the elevator to getting off, elevator hall (elevator hall Service completion time from arrival to the destination floor.
  • elevator hall elevator hall Service completion time from arrival to the destination floor.
  • the maximum waiting number indicating the maximum number of users waiting for the elevator at the platform (elevator hall) during simulation execution is output.
  • the target floor input for the elevator (elevator Average time during simulation, such as the number of times the input device model 12 has been input, such as the time taken from the time when the destination button in the car cage is pressed) to the destination position after getting on the car of the model 16 Output time, maximum time, minimum time.
  • the comprehensive evaluation output unit 17 also takes the time required for the user registration described above, the time spent for extra travel, the waiting time at the landing (elevator hall), the boarding time, and the maximum registration wait at the time of registration.
  • the number of people, the number of people waiting for the user such as the maximum number of people waiting at the platform (elevator hall), etc., and the number of people for waiting may be evaluated and output.
  • FIG. 13 is an example of a display screen of the display unit 18 shown in FIG. 1, which is a layout example of gate interlocking specifications and a display example of simulation results.
  • the display screen 20 includes, for example, a first display area 21 for displaying a layout (simulation condition), and simulation results, for example, “residence time” as a dead time and “extra”. It is comprised from the 2nd display area 22 which displays "the time which walked” etc.
  • the second display area 22 in addition to the residence time “and the time for extra walk”, “elevator waiting time” and “drift area (elevator hall)” which are the outputs from the above-mentioned comprehensive evaluation output unit 17.
  • a simulation situation of the layout where the gate installation position is bad is shown.
  • the elevator 101 is arbitrarily installed, the lantern 102 and the landing destination floor registration device 103 are installed, and the user 104 allocated to the second car stands by.
  • the user 106 allocated to the sixth unit is staying in front of the lighting unit of the lantern 108. When these conditions overlap, the user 107 passing through the gate 105 does not have a space movable by the user 106 allocated to the sixth car.
  • the elevator 101 suffers from the time required for registration in comparison with other simulation conditions and specifications despite the existence of serviceable machines. And the evaluation result is displayed in the second display area 22.
  • FIG. 14 is an example of a display screen of the display unit 18 shown in FIG. 1, which is another display example of the layout of gate interlocking specification and the simulation result.
  • the layout has a margin between the elevator and the installation position of the gate 205. Therefore, even in the state where the user 204 allocated to the sixth unit is present, there is a movable space. Therefore, even when the number of users 206 increases, the number of users who can not register in the gate 205 does not increase, so that the elevator performance can be sufficiently exhibited, and the time required for registration does not increase excessively.
  • the simulation result displayed in the second display area 22 is a good evaluation result.
  • FIG. 15 is an example of a display screen of the display unit 18 shown in FIG. 1, which is another display example of a layout of gate interlocking specifications and a simulation result.
  • the layout 300 displayed in the first display area 21 the layout in which the number of installed gates 305 is extremely small is shown. Since the number of gates 305 is small, the alignment of the users 306 causes stagnation, which limits the number of users who can pass through the gates 305. Therefore, the number of users who can not register in the gate 305 increases, and although the elevator has a serviceable machine, the time required for registration is worse as compared with other simulation conditions and specifications, and the evaluation result is It is displayed in the second display area 22.
  • FIG. 16 is an example of a display screen of the display unit 18 shown in FIG. 1, which is a layout example of the lantern lighting specification of the up-and-down landing button specification and a display example of a simulation result.
  • a layout 400 displayed in the first display area 21 shows a layout in which a simulation with a specification for lighting the lantern immediately by the landing up and down button specification is executed.
  • the upper and lower landing button 401 is pressed, all the upper and lower landing buttons 401 on the floor light.
  • the elevator is assigned to the second unit, only the lantern 403 of the second unit is turned on.
  • the lanterns 402 other than the second car are in the off state.
  • the number of users 404 at a certain threshold stays in front of the lantern lighting machine, and the users 405 of the number of waiting persons exceeding the threshold perform a standby for alignment.
  • FIG. 17 is an example of a display screen of the display unit shown in FIG. 1, which is a layout example of the lantern unlit specification of the upper and lower landing button specification and a display example of a simulation result.
  • a layout 500 displayed in the first display area 21 shows a layout in which a simulation is performed with a specification that does not light the lantern immediately in the platform vertical button specification.
  • the upper and lower landing button 501 is pressed, all the upper and lower landing buttons 501 on the floor light.
  • the lantern 502 of the second unit does not light. Therefore, the user 503 performs alignment standby from near the center of the elevator hall.
  • FIG. 18 is an example of a display screen of the display unit shown in FIG. 1, which is an example of a layout of a wheelchair specification of the up-and-down landing button specification and a display example of a simulation result.
  • the layout 600 displayed in the first display area 21 is a specification for lighting the lantern immediately in the hall up and down type button specification, and shows a layout for executing a simulation when the wheelchair elevator is the first unit. .
  • the upper and lower landing button 601 When the upper and lower landing button 601 is pressed, all the upper and lower landing buttons 601 on the floor light.
  • the lantern 602 of the second unit is lit.
  • the wheelchair user 603 is in an aligned state in order to press the wheelchair landing button near the first car. Therefore, the evaluation takes a long time to register the wheelchair user 603, and the result is displayed in the second display area 22 as a simulation result.
  • FIG. 19 is a display screen example of the display unit 18 shown in FIG. 1 and is another display example of the layout of the wheelchair specification of the up and down type landing button specification and the simulation result.
  • the layout 700 displayed in the first display area 21 is a specification for lighting the lantern immediately in the hall up and down type button specification, and shows a layout for executing a simulation when the wheelchair elevator is the third unit. .
  • the lantern 702 of the second unit is lit.
  • the wheelchair user 703 can press the wheelchair landing button 704 near the third unit, and the third unit is assigned. Therefore, since the lantern 704 of the third car is turned on, the wheelchair user 703 can register early, and the time required for registration becomes short, which is a good evaluation.
  • the simulation result is displayed in the second display area 22.
  • the layout that is the simulation condition is displayed in the first display area 21 on the screen of the display unit that constitutes the building simulator, and the result of executing the simulation with the layout is the second. Since the display area 22 is displayed, it is possible to easily grasp the simulation result of the layout visually and to evaluate the layout of buildings for various uses in advance.
  • the generation distribution for each time zone is set based on the on-site measurement data of similar similar building specifications in the past, so the use situation when building operation is started to some extent at the installation planning time. It is possible to simulate
  • FIG. 20 is a flowchart showing a process flow of the user who dismounts the elevator by the simulation unit configuring the building simulator of the second embodiment according to the other embodiment of the present invention.
  • the building simulator shown in the first embodiment the layout and the like in the case where the user moves from the vicinity of the entrance of the landing (elevator hall) to the front of the desired car is evaluated by simulation.
  • the second embodiment differs from the first embodiment in that it simulates the evaluation of the layout in the building when moving to the target position after getting off the elevator.
  • the overall configuration of the building simulator 1 is the same as that of the first embodiment shown in FIG. The differences from the first embodiment will be mainly described below.
  • step S51 it is determined whether the elevator has arrived at the destination floor and the door has been opened. As a result of the determination, when the elevator arrives at the target floor and the door opens, the process proceeds to step S52. On the other hand, if the result of the determination is that the door has been opened but the elevator has not arrived at the target floor, the process proceeds to step S54.
  • step S52 the user gets off the elevator, stores the getting-off time as the current system time in the virtual memory, and proceeds to step S53.
  • step S53 the target position walking process of the user who got off the elevator on the target floor is executed, and the process is ended. Details of the target position walking process will be described later with reference to FIG.
  • step 54 the floor of the user who is riding behind the elevator car It is determined whether there is a user who gets off on the (floor). In addition, the presence or absence of the user who alights on the said floor (floor) can be determined based on the input information etc. to a destination floor registration apparatus, for example. As a result of the determination, if the user getting off is on the back, the process proceeds to step S55. On the other hand, when the user getting out of the vehicle is not in the rear, the process ends without performing any processing.
  • step S55 the user located on the front side (car door side) of the elevator car is temporarily dismounted so that the user riding in the back of the elevator car can dismount, and the process proceeds to step S56. move on.
  • step S56 it is determined whether or not there is no user getting out of the vehicle, and as a result of the determination, if there are no users getting out on the floor, the process ends. On the other hand, when there is a user who gets off on the floor, the process of step S56 is repeatedly executed.
  • FIG. 21 is a flowchart showing a target position walking process flow by the simulation unit of this embodiment.
  • step S531 the distance L D from the getting-off position to the target position is acquired.
  • Distance L D from getting-off position to the target position based on pre-set by the user setting section 2 the user attribute information and the building information set by the setting unit 3 a getting-off position of the floor layout, buildings if Office In the case of a building, the office of the user is extracted as the target position, and in the case where the building is an apartment temporarily, the room in which the user resides is extracted as the target position.
  • the distance L D is calculated because the position of each car is acquired at the time when the landing device such as the destination floor registration device is set in advance as in the above-described first embodiment.
  • step S532 the walking distance in system time units is acquired from the walking speed of the user.
  • the walking speed of the user is the walking speed set by the user setting unit 2
  • the walking distance in system time units is calculated by walking speed ⁇ system time.
  • step S533 a walking determination process is performed.
  • the walking determination processing here is the same as the processing described using FIG. 10 in the above-mentioned first embodiment, and the space for the user's walking in step S331 and the space for the walking direction in step S332 are dismounted respectively. It is a space on the movement path from the position to the target position.
  • step S534 the movement distance Lpsn of the user is calculated by (system time-registration time-penalty 1) ⁇ walking speed.
  • step S535. the movement distance L psn of the user is compared with the distance L D from the drop- off position to the target position to determine whether they are the same. That is, it is determined whether the user has arrived at the target position. As a result of the determination, it determines that when the moving distance L psn the user is the same as the distance L D to the target position from the drop-off position has arrived at the destination, the process proceeds to step S536.
  • step S536 the destination position arrival time is updated as user data.
  • the destination position arrival time stores the current system time as it is.
  • a user in addition to the effects of the first embodiment, in a building for various uses such as an office building or a condominium, a user owns an office or a room in which he / she lives after getting off the elevator. It is possible to evaluate the in-building layout up to the point of installation planning by simulation.
  • the present invention is not limited to the embodiments described above, but includes various modifications.
  • the embodiments described above are described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described.
  • part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Geometry (AREA)
  • Operations Research (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer Hardware Design (AREA)
  • Evolutionary Computation (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Indicating And Signalling Devices For Elevators (AREA)
  • Elevator Control (AREA)
PCT/JP2017/028722 2017-08-08 2017-08-08 ビルシミュレーター及びビルシミュレーション方法 WO2019030816A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2019535469A JP6880196B2 (ja) 2017-08-08 2017-08-08 ビルシミュレーター及びビルシミュレーション方法
PCT/JP2017/028722 WO2019030816A1 (ja) 2017-08-08 2017-08-08 ビルシミュレーター及びビルシミュレーション方法
CN201780093651.1A CN111108500B (zh) 2017-08-08 2017-08-08 建筑物仿真器以及建筑物仿真方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2017/028722 WO2019030816A1 (ja) 2017-08-08 2017-08-08 ビルシミュレーター及びビルシミュレーション方法

Publications (1)

Publication Number Publication Date
WO2019030816A1 true WO2019030816A1 (ja) 2019-02-14

Family

ID=65270882

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/028722 WO2019030816A1 (ja) 2017-08-08 2017-08-08 ビルシミュレーター及びビルシミュレーション方法

Country Status (3)

Country Link
JP (1) JP6880196B2 (zh)
CN (1) CN111108500B (zh)
WO (1) WO2019030816A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021131332A1 (ja) * 2019-12-26 2021-07-01 株式会社日立製作所 建築モデルデータ支援システムおよび建築モデルデータ支援方法
JP2021189526A (ja) * 2020-05-26 2021-12-13 株式会社東芝 レイアウト支援装置、レイアウト支援方法およびプログラム
CN113836614A (zh) * 2020-06-24 2021-12-24 株式会社日立大厦*** 大楼信息显示***和大楼信息显示方法
WO2022054285A1 (ja) * 2020-09-14 2022-03-17 株式会社日立製作所 設備レイアウト異常判定装置及び設備レイアウト異常判定方法
CN115039102A (zh) * 2020-02-28 2022-09-09 株式会社日立制作所 建筑模型生成装置和建筑模型生成方法
CN117216860A (zh) * 2023-11-07 2023-12-12 天津鑫宝龙电梯集团有限公司 一种电梯井道布置图推荐方法、装置、设备及介质
JP7448465B2 (ja) 2020-12-02 2024-03-12 株式会社日立製作所 整列範囲生成装置および整列範囲生成方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113449364B (zh) * 2021-06-22 2023-01-03 上海柏涛建筑设计有限公司 一种基于辗模块的建筑物快捷布局方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000044134A (ja) * 1998-07-30 2000-02-15 Taisei Corp 建物内総合交通シミュレーションシステム
JP2005182558A (ja) * 2003-12-22 2005-07-07 Hitachi Ltd コスト予測・評価方式
JP2009096612A (ja) * 2007-10-18 2009-05-07 Hitachi Ltd 人流演算装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0728387A (ja) * 1993-07-14 1995-01-31 Hitachi Ltd 移動体の運動計画方法及び装置
JP2002208063A (ja) * 2001-01-09 2002-07-26 Hitachi Ltd エレベーターシステム及びエレベーターのレンタル方法
JP2004093851A (ja) * 2002-08-30 2004-03-25 Sekisui House Ltd モデルハウス眺望シミュレーションシステム
JP4800723B2 (ja) * 2005-09-27 2011-10-26 株式会社日立製作所 エレベータの群管理システム及びその制御方法
US9015020B2 (en) * 2007-04-23 2015-04-21 Siemens Industry, Inc. Method and system for testing a building control system
CN101403891B (zh) * 2008-11-14 2010-06-02 天津大学 电梯群控节能调度方法
US20100217640A1 (en) * 2009-02-20 2010-08-26 Mark Nichols Method and system for adaptive construction sequencing
JP5847220B2 (ja) * 2014-02-26 2016-01-20 東芝エレベータ株式会社 エレベータ群管理装置およびエレベータ群管理方法
CN107848732B (zh) * 2015-07-16 2019-06-11 三菱电机株式会社 电梯的目的地呼梯登记***及其方法
JP2017037441A (ja) * 2015-08-07 2017-02-16 株式会社東芝 プロセスシミュレータ、レイアウトエディタ及びシミュレーションシステム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000044134A (ja) * 1998-07-30 2000-02-15 Taisei Corp 建物内総合交通シミュレーションシステム
JP2005182558A (ja) * 2003-12-22 2005-07-07 Hitachi Ltd コスト予測・評価方式
JP2009096612A (ja) * 2007-10-18 2009-05-07 Hitachi Ltd 人流演算装置

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021105768A (ja) * 2019-12-26 2021-07-26 株式会社日立製作所 建築モデルデータ支援システムおよび建築モデルデータ支援方法
EP4082955A4 (en) * 2019-12-26 2024-01-24 Hitachi, Ltd. ARCHITECTURAL MODEL DATA SUPPORT SYSTEM AND ARCHITECTURAL MODEL DATA SUPPORT METHOD
WO2021131332A1 (ja) * 2019-12-26 2021-07-01 株式会社日立製作所 建築モデルデータ支援システムおよび建築モデルデータ支援方法
JP7199341B2 (ja) 2019-12-26 2023-01-05 株式会社日立製作所 建築モデルデータ支援システムおよび建築モデルデータ支援方法
CN115039102A (zh) * 2020-02-28 2022-09-09 株式会社日立制作所 建筑模型生成装置和建筑模型生成方法
JP7379270B2 (ja) 2020-05-26 2023-11-14 株式会社東芝 レイアウト支援装置、レイアウト支援方法およびプログラム
JP2021189526A (ja) * 2020-05-26 2021-12-13 株式会社東芝 レイアウト支援装置、レイアウト支援方法およびプログラム
CN113836614A (zh) * 2020-06-24 2021-12-24 株式会社日立大厦*** 大楼信息显示***和大楼信息显示方法
JPWO2022054285A1 (zh) * 2020-09-14 2022-03-17
WO2022054285A1 (ja) * 2020-09-14 2022-03-17 株式会社日立製作所 設備レイアウト異常判定装置及び設備レイアウト異常判定方法
CN115917549A (zh) * 2020-09-14 2023-04-04 株式会社日立制作所 设备布局异常判定装置及设备布局异常判定方法
JP7385761B2 (ja) 2020-09-14 2023-11-22 株式会社日立製作所 設備レイアウト異常判定装置及び設備レイアウト異常判定方法
JP7448465B2 (ja) 2020-12-02 2024-03-12 株式会社日立製作所 整列範囲生成装置および整列範囲生成方法
CN117216860A (zh) * 2023-11-07 2023-12-12 天津鑫宝龙电梯集团有限公司 一种电梯井道布置图推荐方法、装置、设备及介质
CN117216860B (zh) * 2023-11-07 2024-02-23 天津鑫宝龙电梯集团有限公司 一种电梯井道布置图推荐方法、装置、设备及介质

Also Published As

Publication number Publication date
JPWO2019030816A1 (ja) 2020-07-09
JP6880196B2 (ja) 2021-06-02
CN111108500B (zh) 2023-12-05
CN111108500A (zh) 2020-05-05

Similar Documents

Publication Publication Date Title
WO2019030816A1 (ja) ビルシミュレーター及びビルシミュレーション方法
CN102159482B (zh) 电梯组群管理装置
JP6757282B2 (ja) エレベーターシミュレーター
US8348021B2 (en) User selection of an elevator
JP2009096612A (ja) 人流演算装置
JP4515772B2 (ja) 乗客案内システムおよび表示装置
WO2019087249A1 (ja) エレベーター運行管理システムおよびエレベーター運行管理方法
WO2019217432A1 (en) System and method for landing and storing vertical take-off and landing aircraft
EP3067770B1 (en) Automatic driving system and automatic travel machine
JP2010070382A (ja) 昇降機システム
CN108861904A (zh) 使用建筑楼层平面图的目的地输入
US10155639B2 (en) Elevator notice system
KR20180137549A (ko) 엘리베이터 시스템 및 카 호출 추정 방법
CN111225866B (zh) 自动呼叫登记***以及自动呼叫登记方法
WO2019087730A1 (ja) ビル内交通予測システム、ビル内交通予測システムにおけるエレベーター乗り場レイアウトの生成方法及びプログラム
JP7184521B2 (ja) 車両運行管理方法及び車両運行管理装置
JP2009155042A (ja) 群管理エレベータ性能評価装置
JP6242952B1 (ja) Ｂｉｍシステム、方法およびプログラム
WO2020230311A1 (ja) 移動支援システム
KR101813872B1 (ko) 승객의 카 내 탑승위치를 지정하는 엘리베이터 시스템
JP6960388B2 (ja) エレベーターシステム、および、乗場釦故障検出装置
KR20190028512A (ko) 여객 이동 상황 출력 장치 및 방법
WO2018193819A1 (ja) エレベーター利用者移動予測方法およびエレベーター利用者移動予測装置
WO2019087710A1 (ja) エレベーターの上下方向人数検出システム、及び上下方向人数検出方法
JP2006268264A (ja) 建物設備仕様決定支援システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17921063

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2019535469

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17921063

Country of ref document: EP

Kind code of ref document: A1