Building plan evaluation device and building plan evaluation method

Abstract

The present invention detects problems in movement path planning of heterogeneous agents early on. A building plan evaluation device 1 includes: a storage unit 10 that stores a layout 11 and agent type passability information 12; and an agent type route search unit 21 that searches for a route for moving from an entrance to an exit on the layout 11 for each agent type on the basis of the layout 11 and the agent type passability information 12, and outputs the found route for each agent type as an agent type route 13. The agent type route search unit 21 outputs an alert upon failing to find a route for at least one agent type.

Description

Building plan evaluation device and building plan evaluation method

[0001] The present invention relates to a building plan evaluation device and a building plan evaluation method.

[0002] With the recent trend toward barrier-free access and the spread of service robots, there has been an increase in cases where elevators are used by people moving in different ways (heterogeneous agents), such as wheelchair users and robots, rather than the pedestrians traditionally assumed to be pedestrians (normal walking agents).

[0003] As an example of a simulation technology that takes heterogeneous agents into consideration, claim 1 of Patent Document 1 describes, "a building planning support system having a simulation unit that simulates the movement of human agents and heterogeneous agents, and the elevator car object, in a building object that includes an elevator car object, in which human agents and heterogeneous agents are mixed, wherein the simulation unit has in-car occupied area information required when the heterogeneous agents get on the elevator car, and the building planning support system that simulates the movement of the elevator car object based on the in-car occupied area information of the heterogeneous agents."

[0004] Furthermore, paragraph 0009 of Patent Document 1 states, "According to the present invention, it becomes possible to devise an appropriate elevator installation plan even in an environment where heterogeneous agents are included within a building.It also becomes possible to estimate how many heterogeneous agents can be introduced within a building."

[0005] Furthermore, as a simulation technology that takes into account that possible travel routes differ depending on people's attributes, claim 1 of Patent Document 2 describes "an intra-building traffic flow setting device comprising: a database unit that stores data of a building's BIM model; a people flow simulator unit that simulates traffic flow within the building represented by the BIM model stored in the database unit; and an elevator simulator unit that simulates the operation of elevators installed in the building based on the traffic flow simulated by the people flow simulator unit, wherein the people flow simulator unit comprises: a position attribute generation unit that generates attributes of each position on each floor represented by the BIM model; and a travel demand calculation unit that calculates the travel demand for each floor represented by the BIM model, taking into account the attributes of each position generated by the position attribute generation unit."

[0006] As an example of the position attributes in Patent Document 2, Figure 4 and paragraph 0039 of Patent Document 2 state, "Figure 4 shows an example of setting position attributes on the second floor of the BIM model shown in Figure 3. Figure 4 is a plan view of the second floor, and shows the second floor divided into grids of a certain area. In the example of Figure 4, six types of position attributes are set for each grid: passable grid, impassable grid, elevator grid, end point grid, grid that only property A can pass through, and grid for general work areas."

[0007] Furthermore, paragraph 0008 of Patent Document 2 states, "According to the present invention, it is possible to calculate accurate travel demand in accordance with actual usage conditions, such as setting permitted passage areas for personnel within a building."

[0008] JP 2023-166672 A International Publication No. 2022 / 059079

[0009] When planning a large-scale building, the primary focus is on planning the movement routes of the large number of normally walking agents. As a result, the movement route planning of different types of agents, such as wheelchair users, is often put off until later. As a result, the movement route planning may be inconvenient for the different types of agents, requiring long travel times, or the plan may not even include any movement routes that the different types of agents can move through.

[0010] The problem to be solved by the present invention is to provide a building plan evaluation device and a building plan evaluation method that can detect problems in the flow line plans of different types of agents at an early stage.

[0011] In order to solve the above-mentioned problems, the building plan evaluation device of the present invention is a building plan evaluation device having a memory unit that stores layouts and agent type passability information, and an agent type route search unit that searches for a route from an entrance to an exit on the layout for each agent type based on the layout and the agent type passability information, and outputs the route for each agent type as an agent type route, and is characterized in that the agent type route search unit outputs an alert if it cannot find the route for at least one of the agent types.

[0012] Furthermore, the building plan evaluation method of the present invention is a building plan evaluation method that searches for a route from an entrance to an exit on the layout for each agent type based on the layout and agent type passability information, and outputs the route for each agent type as an agent type route, and is characterized in that an alert is output if the route cannot be found for at least one of the agent types.

[0013] According to the building plan evaluation device and building plan evaluation method of the present invention, problems in the flow line plans of different types of agents can be discovered at an early stage.

[0014] 1 is a functional block diagram of a construction plan evaluation device according to a first embodiment. FIG. 1 is a diagram illustrating an example of a layout according to the first embodiment. FIG. 2 is a diagram illustrating an example of agent type passability information according to the first embodiment. FIG. 3 is a diagram illustrating an example of an agent type route according to the first embodiment. A flowchart illustrating an example of the processing of an agent type route search unit according to the first embodiment. FIG. 4 is a diagram illustrating an example of an alert when a route cannot be found according to the first embodiment. FIG. 5 is a diagram illustrating an example of an alert related to a route travel distance according to the first embodiment. A functional block diagram of a construction plan evaluation device according to a second embodiment. FIG. 6 is a diagram illustrating an example of agent type priority information according to the second embodiment. A flowchart illustrating an example of the processing of a route verification unit according to the second embodiment. FIG. 7 is a diagram illustrating an example of an alert related to priority information according to the second embodiment. A functional block diagram of a construction plan evaluation device according to a third embodiment. FIG. 8 is a diagram illustrating an example of agent type transportation demand according to the third embodiment. A flowchart illustrating an example of the processing of a movement calculation unit according to the third embodiment. A flowchart illustrating an example of the processing of a result verification unit according to the third embodiment. FIG. 9 is a diagram illustrating an example of an alert related to an evaluation index according to the third embodiment.

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing and each embodiment, the same or similar components are designated by the same reference numerals, and redundant explanations will be omitted.

[0016] FIG. 1 is a functional block diagram of a construction plan evaluation device according to a first embodiment.

[0017] The architectural plan evaluation device 1 of this embodiment has, as functional blocks, a storage unit 10, a control unit 20, and an input / output unit 30. The storage unit 10 stores a layout 11, agent type passability information 12, and agent type routes 13. The control unit 20 has, as a functional block, an agent type route search unit 21. The input / output unit 30 has, as functional blocks, an input unit 31 and a display unit 32.

[0018] Each functional block of the control unit 20 can be realized by executing a program on a processing system including, for example, a processing device such as a CPU (Central Processing Unit), a memory, an auxiliary storage device, an input / output interface, etc. The storage unit 10 can be realized, for example, by the auxiliary storage device or memory of the processing system. The input / output unit 30 can be realized by an input / output interface. The input unit 31 can be realized by an input interface such as a keyboard, a mouse, or a touch panel. The display unit 32 can be realized by an output interface such as a display device, etc.

[0019] FIG. 2 is a diagram illustrating an example of a layout according to the first embodiment.

[0020] The layout 11 is structural information that describes the position and connections of each element within a building. The layout 11 includes information on at least one pair of an entrance 101 and an exit 102. The layout 11 is input by a building designer via the input unit 31, for example.

[0021] The layout 11 of this embodiment has as its elements an entrance 101 which is the entry point, an exit 102 which is the destination, a movable floor surface 103, an office elevator 104, a low-floor elevator 105, an escalator 106, and stairs 107.

[0022] Access is possible from the entrance 101 to the first floor 103. Access is possible from the first floor 103 to the second floor 103 by a low-floor elevator 105, an escalator 106, and stairs 107. Access is possible from the second floor 103 to the upper floor 103 where the exit 102 is located by an office elevator 104.

[0023] 2 and may include, for example, walls, security gates, etc. Furthermore, the data structure of the layout 11 is not limited. It may be in a format having a set of three-dimensional polygon data and attribute information, or may be in a format having data as a collection of two-dimensional or three-dimensional grid data.

[0024] FIG. 3 is a diagram illustrating an example of the agent type passability information according to the first embodiment.

[0025] The agent type passability information 12 is information that defines whether an agent type can pass through each element or area of ​​the layout 11. The agent type passability information 12 is set for each element or area of ​​the layout 11. The agent type passability information 12 is input by the building designer via the input unit 31, for example.

[0026] 3, the agent type passability information 12 for the escalator 106 is defined such that normal pedestrians, whose agent type is a normal walking agent, can pass (passability information is ◯), but different agent types such as wheelchair users, crutch users, and cleaning robots cannot pass (passability information is ×). Note that other different agent types may include other robots such as security robots, people pushing stretchers, people pushing carts, etc.

[0027] The agent type passability information 12 is similarly defined for other elements such as the floor surface 103 and the office elevator 104 .

[0028] The data structure of the agent type passability information 12 is not limited to that shown in Fig. 3, and may be any information that can determine whether or not passage is possible. For example, if the agent type passability information 12 has a data structure that describes only passable agent types, and passability information that, for example, only normal pedestrians are allowed to pass is defined, it can be determined that passage is not permitted for anyone other than normal pedestrians. Similarly, if the agent type passability information 12 has a data structure that describes only impassable agent types, and impassability information that, for example, only heterogeneous agents are not allowed to pass, it can be determined that normal pedestrians are allowed to pass. Therefore, the agent type passability information 12 is a higher-level concept that includes passability information and impassability information.

[0029] FIG. 4 is a diagram illustrating an example of an agent type route according to the first embodiment.

[0030] The agent type route search unit 21 searches for a route for traveling from the entrance 101 to the exit 102 on the layout 11 for each agent type based on the layout 11 and the agent type passability information 12, and outputs the route for each agent type as an agent type route 13. The manner of outputting the agent type route 13 includes, for example, storing the agent type route 13 in the storage unit 10, or displaying the agent type route 13 on the display unit 32 together with the layout 11, etc.

[0031] 4 shows a normal pedestrian movement route 111 and a wheelchair user movement route 112 as examples of the agent type route 13. The normal pedestrian movement route 111, which is the movement route of a normal pedestrian, goes from the entrance 101 to the exit 102 via the escalator 106 and the office elevator 104. On the other hand, since wheelchair users cannot use the escalator 106 as shown in the agent type passability information 12 in FIG. 3, the wheelchair user movement route 112, which is the movement route of a wheelchair user, goes from the entrance 101 to the exit 102 via the low-floor elevator 105 and the office elevator 104.

[0032] The agent type route 13 is information about the movement route from the entrance 101 to the exit 102, and any data format is acceptable. The data format of the agent type route 13 may be a format that holds a series of coordinates of points on the route, such as (0,0,0), (1,0,0), (1,1,0), (1,2,0), ..., or a format that holds only information about the points along the way, such as (entrance 101), (escalator 106), (office elevator 104), (exit 102).

[0033] FIG. 5 is a flowchart illustrating an example of processing by the agent type route search unit according to the first embodiment.

[0034] The agent type route search unit 21 of this embodiment outputs an alert when a route cannot be found for at least one agent type. It is also desirable that the agent type route search unit 21 of this embodiment outputs an alert when the length of the searched route is equal to or greater than a threshold.

[0035] As a specific example of processing, as shown in FIG. 5, the agent type route search unit 21 repeatedly processes all agent types between S1 and S11, repeatedly processes all exits 102 between S2 and S10, and repeatedly processes all entrances 101 between S3 and S9.

[0036] In S4, the agent type route search unit 21 searches for a route for the agent type being processed, from the entrance 101 being processed to the exit 102 being processed. Here, the route length is also calculated, and the shortest route is searched for so that the route length is the shortest. The search may be performed using a known method, for example, Dijkstra's algorithm. For example, if there is a combination of agent type and entrance / exit that clearly does not require route search, such as when the agent type traffic demand described below is not set, the route search process may be omitted.

[0037] If the searched route includes an elevator, the agent-type route search unit 21 preferably searches for a route by adding to the route length a value proportional to either the expected elevator waiting time or the expected elevator ride time, or their sum. As the expected waiting time, for example, the average elevator headway divided by 2 in traffic calculations can be used. As the expected ride time, for example, the travel time + door opening / closing time + boarding and alighting time in traffic calculations can be used. This makes it possible to search for the shortest route taking into account the time required to use the elevator, thereby obtaining results that are close to the route choices that people would actually make.

[0038] In S5, the agent type route search unit 21 determines whether a route has been found, and if a route has been found, the process proceeds to S6, and if a route has not been found, the process proceeds to S8, where an alert is output, and the process proceeds to S9.

[0039] In S6, the agent type route search unit 21 determines whether the length of the route is less than the threshold, and if it is less than the threshold, proceeds to S7, and if it is greater than or equal to the threshold, proceeds to S8, outputs an alert, and proceeds to S9.

[0040] In S7, the agent type route search unit 21 outputs the agent type route 13, and the process moves to S9.

[0041] In this embodiment, an example in which both the processes of S5 and S6 are performed is shown, but the present invention is not limited to this, and only the process of S5 or only the process of S6 may be performed.

[0042] FIG. 6 is a diagram illustrating an example of an alert when a route cannot be found according to the first embodiment.

[0043] As shown in Figure 6, as an example of outputting an alert in S8 of Figure 5, it is desirable that the agent type route search unit 21 display an alert 115 together with a searched range 114 when a route cannot be found. Figure 6 shows a layout 11 in which a low-floor elevator 105 does not exist. Therefore, Figure 6 shows an example in which the display screen 116 of the display unit 32 displays the searched range 114 and an alert 115 saying "Route for wheelchair users not found" together with the layout 11. This makes it easier to understand where the search was interrupted.

[0044] The searched range 114 is the range that has been searched in the process of route searching in S4 of Fig. 5. The data format and display method of the searched range 114 are not important. The data format of the searched range 114 may be a format that holds a series of point coordinates on the search range, such as (0,0,0), (1,0,0), (1,1,0), (1,2,0), ..., or a format that holds only information on route points, such as (exit 102) and (office elevator 104).

[0045] 6 shows an example in which a search is performed starting from the exit 102 as the search start point 113. By searching starting from the exit 102, the distance from the exit 102 to each point can be determined in the process of expanding the search range. This makes it possible to use this information in a people flow simulation performed in Example 3, which will be described later, as information on which direction to head in order to shorten the distance to the exit 102. However, the present invention is not limited to this, and a search may be performed starting from the entrance 101 as the search start point 113.

[0046] FIG. 7 is a diagram illustrating an example of an alert regarding a travel distance on a route according to the first embodiment.

[0047] As shown in FIG. 7 , as an example of outputting an alert in S8 of FIG. 5 , it is desirable that the agent-type route search unit 21 output an alert 115 when the searched route length is equal to or greater than a threshold. At this time, it is desirable to also display the route length for the target agent type. In FIG. 7 , the display screen 116 of the display unit 32 displays a normal pedestrian route 111 and a wheelchair user route 112 as agent-type routes 13 along with the layout 11, and displays route length indications 117 such as "Normal pedestrian route XX m" and "Wheelchair user route △△ m," respectively, and displays an alert 115 stating, "The wheelchair user's travel distance is long." This allows for early detection of inconvenient route plans for different types of agents, such as wheelchair users.

[0048] Furthermore, the condition for determining an alert may not be whether the path length of the target agent type itself is equal to or greater than a threshold, but whether the difference or ratio with respect to the path length of another agent type is equal to or greater than a threshold.

[0049] According to this embodiment, problems with the flow line plans for heterogeneous agents can be discovered early on, such as when there is no flow line along which the heterogeneous agents can move, or when the flow line plan is inconvenient for the heterogeneous agents, such as when the travel time is long.

[0050] FIG. 8 is a functional block diagram of the construction plan evaluation device according to the second embodiment.

[0051] Example 2 is a modified example of Example 1, and in addition to the configuration of Example 1, the architectural plan evaluation device 1 of this example has the following features: the memory unit 10 stores agent type priority information 14, and the control unit 20 has a route verification unit 22 as a functional block.

[0052] The agent type priority information 14 is information on the use priority for each agent type on the layout 11 .

[0053] The route verification unit 22 verifies the agent type route 13. Specifically, the route verification unit 22 displays an alert when a plurality of agent types with different usage priorities pass through a point for which a usage priority is set in the agent type route 13.

[0054] For example, if there is a priority elevator for wheelchair users, a different agent, on the route of a normal pedestrian, a normal walking agent, the priority elevator for the different agent may be used by the normal pedestrian, which may cause the priority elevator to become congested and become unavailable for the different agent, or may result in a long waiting time.When there are routes with competing usage priorities like this, it is desirable to display an alert because there is a problem with the flow line planning of the different agents.

[0055] According to this embodiment, even if there are routes with conflicting usage priorities, it is possible to display an alert indicating that there is a problem with the flow line plan for the different types of agents.

[0056] FIG. 9 is a diagram illustrating an example of agent type priority information according to the second embodiment.

[0057] The agent type priority information 14 is information that defines the use priority for each agent type in each element or area of ​​the layout 11. The agent type priority information 14 is set for each element or area of ​​the layout 11. The number of levels of use priority and expression are not important. For example, expressions such as high, medium, and low are acceptable, or expressions such as 1, 2, 3, 4, 5, ... or A, B, C, D, E, ... are also acceptable. The agent type priority information 14 is input by the building designer via, for example, the input unit 31.

[0058] 9, the agent type priority information 14 of the low-floor elevator 105 is a priority elevator for different types of agents, and the use priority is set to "low" for the agent type of a normal pedestrian, "high" for a wheelchair user and a crutch user, and "medium" for a cleaning robot. Similar settings are made for other elements or areas.

[0059] FIG. 10 is a flowchart illustrating an example of processing by the route verification unit according to the second embodiment.

[0060] For example, as shown in FIG. 10, the route verification unit 22 performs repeated processing for all agent types between S1 and S11, repeated processing for all exits 102 between S2 and S10, repeated processing for all entrances 101 between S3 and S9, and repeated processing at each point on the route between S21 and S24.

[0061] In S22, the route verification unit 22 determines whether an agent type with a different usage priority from the usage priority of the agent type currently being processed passes through the point currently being processed, i.e., whether there is a route with a conflicting usage priority. For example, the route verification unit 22 records the agent type currently being processed and information about its usage priority as a flag at the point currently being processed, and reads any other flags already recorded at the point currently being processed, and if any of these flags include an agent type with a different usage priority, it determines that an agent type with a different usage priority from the usage priority of the agent type currently being processed passes through the point currently being processed, and proceeds to S23. If it determines that no agent type will pass through, it proceeds to S24.

[0062] In S23, the route verification unit 22 outputs an alert because there are routes with conflicting usage priorities and there is a problem with the flow line plan for the different types of agents, and then the process moves to S24.

[0063] FIG. 11 is a diagram illustrating an example of an alert related to priority information according to the second embodiment.

[0064] As shown in FIG. 11 , as an example of outputting an alert in S23 of FIG. 10 , it is desirable for the route verification unit 22 to display an alert 115 when there are routes with conflicting usage priorities. At this time, it is desirable for the competing agent type routes 13 to also be displayed. In FIG. 11 , a layout 11 is shown in which the entrance 101 is located near a low-floor elevator 105. Therefore, FIG. 11 shows an example in which, along with the layout 11, a normal pedestrian route 111 and a wheelchair user route 112 are displayed on the display screen 116 of the display unit 32 as competing agent type routes 13, with explanatory displays 118 indicating "normal pedestrian route" and "wheelchair user route," respectively. An explanatory display 118 indicating "wheelchair user priority elevator" is displayed at the low-floor elevator 105, which is the conflicting point, and an alert 115 stating "There is a wheelchair user priority elevator on the shortest normal pedestrian route." This allows the user to identify the routes with conflicting usage priorities and the conflicting points for the agent types.

[0065] FIG. 12 is a functional block diagram of a construction plan evaluation device according to the third embodiment.

[0066] Example 3 is a modified example of Example 2, and in addition to the configuration of Example 2, the building plan evaluation device 1 of this example has a storage unit 10 that stores agent-type transportation demand 15 and movement calculation results 16, and a control unit 20 that has, as functional blocks, a movement calculation unit 23 and a movement verification unit 24. Note that, in Example 3, the configuration added in Example 2 is not essential, and therefore the configuration added in Example 2 may be omitted.

[0067] The movement calculation unit 23 calculates an evaluation index related to movement, which includes at least one of the movement distance and the movement time, based on the agent type route 13. Note that the evaluation index calculated by the movement calculation unit 23 may include at least one of the waiting time, the number of intersections, the number of near misses, and the number of steps overcome.

[0068] It is desirable that the movement calculation unit 23 calculates the evaluation index by performing a simulation of each agent type passing through the agent type route 13. In this case, it is desirable that the movement calculation unit 23 performs the simulation based on the agent type transportation demand 15. It should be noted that the agent type transportation demand 15 is information on transportation demand for each agent type.

[0069] The movement verification unit 24 evaluates the calculated evaluation indexes and displays an alert. For example, the movement verification unit 24 displays an alert if any of the calculated evaluation indexes is equal to or greater than a threshold, or if the difference or ratio between the evaluation index for an agent type having a normal walking attribute and the evaluation index for an agent type having other attributes is equal to or greater than a threshold. This makes it possible to evaluate evaluation indexes such as travel distance, travel time, waiting time, number of intersections, number of near misses, and number of steps climbed, and to display an alert, thereby enabling early detection of problems in the movement line plans of different types of agents.

[0070] FIG. 13 is a diagram illustrating an example of transportation demands by agent type according to the third embodiment.

[0071] The agent type traffic demand 15 is, for example, information indicating how many people are moving from where to where for each agent type. The agent type traffic demand 15 preferably includes at least data on the agent type, the entrance 101, the exit 102, and the number of people moving. In addition to this, it may also include data on the entry start time and entry end time. The agent type traffic demand 15 is used when the movement calculation unit 23 performs a movement simulation on the layout 11.

[0072] 13, row No. 1 defines a traffic demand for normal pedestrians as the agent type, with 50 people flowing from entrance A to exit X, 50 people flowing to exit Y, and 30 people flowing to exit Z from the flow start time of 08:30 to the flow end time of 08:40. Similarly, rows No. 2 to No. 5 define traffic demands for normal pedestrians, wheelchair users, crutch users, and cleaning robots, respectively.

[0073] The data structure of the agent-type transportation demand 15 is not limited to the example shown in Fig. 13. The agent-type transportation demand 15 is input by the building designer via the input unit 31, for example.

[0074] FIG. 14 is a flowchart illustrating an example of processing by the movement calculation unit according to the third embodiment.

[0075] For example, as shown in FIG. 14, the movement calculation unit 23 repeats the process between S31 and S37 at the simulation time, and repeats the process for all agents on the layout 11 between S33 and S36.

[0076] In S32, the movement calculation unit 23 causes new agents to flow onto the layout 11 based on the data of the agent type transportation demand 15. The flowed-in agents are added to the set of all agents on the layout 11.

[0077] In S34, the movement calculation unit 23 moves the agent a predetermined distance in a direction that shortens the distance to the exit 102.

[0078] In S35, the movement calculation unit 23 causes the agent to flow out of the layout 11 if the agent has arrived at the exit 102.

[0079] The movement calculation unit 23 calculates an evaluation index during or after the above processing, and stores it in the storage unit 10 as a movement calculation result 16 .

[0080] The movement calculation result 16 may hold results for each agent type, or may hold summarized data such as the average for each agent type or the overall average.

[0081] FIG. 15 is a flowchart illustrating an example of processing by the result verification unit according to the third embodiment.

[0082] For example, as shown in FIG. 15, the movement verification unit 24 repeats the process between S41 and S44 for all evaluation indexes.

[0083] In S42, the movement verification unit 24 evaluates the evaluation index and determines whether the evaluation index satisfies the alert condition. If the alert condition is not satisfied, the process proceeds to S44. If the alert condition is satisfied, the process proceeds to S43, where the movement verification unit 24 outputs an alert, and the process proceeds to S44.

[0084] FIG. 16 is a diagram illustrating an example of an alert related to an evaluation index according to the third embodiment.

[0085] As shown in FIG. 16 , as an example of outputting an alert in S43 of FIG. 15 , it is desirable that the movement verification unit 24 display an alert 115 when the evaluation index satisfies the alert condition. At this time, it is desirable that the evaluation index also be displayed. FIG. 16 shows an example in which, together with the layout 11, the display screen 116 of the display unit 32 displays an evaluation index display 119, such as "Average waiting time for normal pedestrians: XX seconds" and "Average waiting time for wheelchair users: △△ seconds," as evaluation indexes, and an alert 115 stating, "The elevator wait time for wheelchair users is long." This makes it possible to display an alert when a specified evaluation index satisfies the alert condition, thereby enabling early detection of problems with the movement line plan of heterogeneous agents.

[0086] Although the embodiments of the present invention have been described above, the present invention is not limited to the configurations described in the embodiments, and various modifications are possible within the scope of the technical concept of the present invention. In addition, some or all of the configurations described in each embodiment may be combined and applied.

[0087] 1: Architectural plan evaluation device 10: Memory unit 11: Layout 12: Passability information by agent type 13: Route by agent type 14: Priority information by agent type 15: Traffic demand by agent type 16: Movement calculation result 20: Control unit 21: Route search unit by agent type 22: Route verification unit 23: Movement calculation unit 24: Movement verification unit 30: Input / output unit 31: Input unit 32: Display unit 101: Entrance 102: Exit 103: Floor 104: Office elevator 105: Elevator for low floors 106: Escalator 107: Stairs 111: Normal pedestrian movement route 112: Wheelchair user movement route 113: Search start point 114: Searched range 115: Alert 116: Display screen 117: Route length display 118: Explanation display 119: Evaluation index display

Claims

1. An architectural plan evaluation device having: a storage unit that stores a layout and agent type passability information; and an agent type route search unit that searches for a route to travel from an entrance to an exit on the layout for each agent type based on the layout and the agent type passability information, and outputs the route for each agent type as an agent type route, wherein the agent type route search unit outputs an alert if it cannot find the route for at least one of the agent types.

2. The architectural plan evaluation device according to claim 1, wherein the agent type route search unit displays the alert together with the searched range when the route cannot be found.

3. In claim 1, the architectural plan evaluation device is characterized in that the agent type route search unit outputs an alert when the searched route length is equal to or greater than a threshold, or when the difference or ratio with respect to the route length of another agent type is equal to or greater than a threshold.

4. In claim 1, the architectural plan evaluation device is characterized in that, when an elevator is included on the searched route, the agent type route search unit searches for the route by adding a value proportional to either the expected waiting time or the expected riding time for the elevator, or their sum, to the route length.

5. An architectural plan evaluation device according to claim 1, further comprising a route verification unit that verifies the agent type route, wherein the memory unit stores agent type priority information that is information on the usage priority for each agent type on the layout, and wherein the route verification unit displays an alert when a plurality of agent types with different usage priorities pass through a point on the agent type route at which the usage priority is set.

6. An architectural plan evaluation device according to claim 1, characterized in that it has a movement calculation unit that calculates an evaluation index related to movement, including at least one of movement distance and movement time, based on the agent type route, and a movement verification unit that evaluates the calculated evaluation index and displays an alert.

7. The architectural plan evaluation device according to claim 6, wherein the evaluation index includes at least one of waiting time, number of intersections, number of near misses, and number of steps overcome.

8. In claim 6, the architectural plan evaluation device is characterized in that the movement verification unit displays an alert when any of the calculated evaluation indices is equal to or greater than a threshold value, or when the difference or ratio between the evaluation indices of the agent type having normal walking attributes and the evaluation indices of the agent type having other attributes is equal to or greater than a threshold value.

9. The architectural plan evaluation device according to claim 6, wherein the movement calculation unit calculates the evaluation index by carrying out a simulation in which each agent type passes through a route corresponding to the agent type.

10. The architectural plan evaluation device according to claim 9, wherein the memory unit stores agent type traffic demand, which is information on traffic demand for each agent type, and the movement calculation unit carries out the simulation based on the agent type traffic demand.

11. A method for evaluating architectural plans that searches for a route from an entrance to an exit on the layout for each agent type based on the layout and agent type passability information, and outputs the route for each agent type as an agent type route, and that outputs an alert if the route cannot be found for at least one of the agent types.