Building management system and building management method

Abstract

To provide tenants with added values in moving into a building.SOLUTION: A system disclosed herein computes a time series of people moving from tenant areas and staying in event areas for each pair of a tenant area that can be occupied by tenants and an event area holding an event on the basis of a time series of moving people data representing the number of moving people for each pair of a moving source area and a moving destination area. The system outputs an evaluation value of an event held for each tenant area on the basis of a time series of the derived number of people staying for each pair of a tenant area and event area.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention generally relates to a technique for managing a building in which multiple tenants can reside, and relates to, for example, a novel technique for supporting activation of interactions between tenants. [Background technology]

[0002] An example of a building that can accommodate multiple tenants is an office building. In recent years (especially since the COVID-19 pandemic), the way office work is used has changed, and the way office buildings are used is also changing. It is desirable to provide added value to tenants by occupying an office building. This, for example, is expected to lead to long-term, stable occupancy by tenants.

[0003] Patent Document 1 discloses a technology for formulating city development measures that maximize the satisfaction of moving objects such as visitors. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-117503 A Summary of the Invention [Problem to be solved by the invention]

[0005] The technology disclosed in Patent Document 1 increases the satisfaction of moving objects such as visitors by determining the type of stores to be invited to the facility. In other words, this technology requires the addition of tenants to the facility, and cannot provide added value of the building to tenants already in the facility.

[0006] Such challenges may also arise for buildings other than office buildings that can accommodate multiple tenants (e.g., a one-story building with multiple areas that can accommodate multiple tenants). [Means for solving the problem]

[0007] The building management system calculates, for each pair of a tenant area where a tenant may reside and an event implementation area where an event is to be implemented, a time series of number of visitors, which is the number of people who have moved from the tenant area and are staying in the event implementation area, for each pair of a tenant area where a tenant may reside and an event implementation area where an event is to be implemented, based on a time series of number of visitors data indicating the number of people moving for each pair of a source area and a destination area. The building management system outputs, for each tenant area, an evaluation value of an implemented event, which is an implemented event, based on the calculated time series of number of visitors for each pair of a tenant area and an event implementation area. Effect of the Invention

[0008] According to the present invention, it is possible to provide added value to tenants by occupying a building. [Brief description of the drawings]

[0009] [Figure 1] 2 illustrates an example of a functional configuration of a building management system according to an embodiment. [Diagram 2] An example of the overall system configuration including a building management system is shown below. [Diagram 3] An example of an office building overview is shown below. [Figure 4] 13 shows an example of the flow of processing performed by an executed event analysis unit. [Diagram 5] 5 shows an example of calculation of the number of people moving in S403 of FIG. 4. [Figure 6] 5 shows an example of the movement number data generated in S403 of FIG. 4. [Figure 7] 5 illustrates an example of interest level calculation in S406 of FIG. 4. [Figure 8] 5 illustrates an example of AC degree calculation in S406 of FIG. 4; [Figure 9] 5A and 5B are schematic diagrams illustrating an example of the degree of alternating current calculated in S406 of FIG. [Figure 10] 13 shows an example of the flow of processing performed by the event planning support unit. [Figure 11] 13 shows an example of the flow of processing performed by the operation unit. [Figure 12] 13 shows an example of the flow of an event interest level evaluation process. [Figure 13] 13 shows an example of the structure of a table of degree of interest in held events. [Figure 14] 13 shows an example of the flow of an event interaction evaluation process. [Figure 15] 13 shows an example of the configuration of an implemented event interaction degree table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] In the following description, an "interface unit" may refer to one or more interface devices. The one or more interface devices may be at least one of the following: An I / O interface apparatus which is one or more I / O (Input / Output) interface devices. The I / O (Input / Output) interface devices are interface devices to at least one of an I / O device and a remote display computer. The I / O interface device to the display computer may be a communications interface device. The at least one I / O device may be a user interface device, for example, either an input device such as a keyboard and a pointing device, or an output device such as a display device. A communication interface apparatus which is one or more communication interface devices. The one or more communication interface devices may be one or more homogeneous communication interface devices (e.g., one or more NICs (Network Interface Cards)) or two or more heterogeneous communication interface devices (e.g., a NIC and an HBA (Host Bus Adapter)).

[0011] In the following description, a "memory" refers to one or more memory devices, which are an example of one or more storage devices, and may typically be a primary storage device. At least one memory device in the memory may be a volatile memory device or a non-volatile memory device.

[0012] In the following description, a "persistent storage device" may be one or more persistent storage devices, which are an example of one or more persistent storage devices. A persistent storage device may typically be a non-volatile storage device (e.g., an auxiliary storage device), and more specifically, may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a non-volatile memory express (NVME) drive, or a storage class memory (SCM).

[0013] Also, in the following description, "storage device" may be at least one of memory and persistent storage device.

[0014] Furthermore, in the following description, a "processor" may be one or more processor devices. The at least one processor device may typically be a microprocessor device such as a CPU (Central Processing Unit), but may also be other types of processor devices such as a GPU (Graphics Processing Unit). The at least one processor device may be a single-core or multi-core. The at least one processor device may be a processor core. The at least one processor device may also be a broader processor device such as a circuit that is a collection of gate arrays written in a hardware description language that performs part or all of the processing (e.g., an FPGA (Field-Programmable Gate Array), a CPLD (Complex Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit)).

[0015] In the following description, functions may be described using the expression "yyy unit", but the functions may be realized by one or more computer programs being executed by a processor, or by one or more hardware circuits (e.g., FPGA or ASIC), or by a combination thereof. When a function is realized by a program being executed by a processor, the function may be at least a part of the processor, since the specified processing is performed using a storage device and / or an interface device, etc., as appropriate. Processing described with a function as the subject may be processing performed by a processor or a device having the processor. A program may be installed from a program source. The program source may be, for example, a program distribution computer or a storage medium (e.g., a non-transitory storage medium) that can be read by a computer. The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

[0016] In the following description, data that produces an output in response to an input may be described using an expression such as "xxxDB", but the data may be data of any structure (for example, structured data or unstructured data), or may be a neural network that generates an output in response to an input, or a learning model such as a genetic algorithm or random forest. Therefore, "xxxDB" may be referred to as "xxx data". In the following description, the configuration of each DB is an example, and one DB may be divided into two or more DBs, or all or part of two or more DBs may be one DB.

[0017] In addition, in the following description, when elements of the same type are described without distinction, common reference symbols will be used, and when elements of the same type are described with distinction, reference symbols will be used.

[0018] An embodiment will be described below. In the embodiment, for the sake of simplicity, a building in which multiple tenants can reside is an office building, a floor has one area, one floor has one tenant, and a floor in which a tenant can reside is called an "office floor." However, the present invention is not limited thereto, and one floor may have multiple areas, one or more tenants may each have an area, two or more tenants may share one area, or one tenant may exist in two or more areas. The present invention can also be applied to buildings other than office buildings, for example, one-story buildings having multiple areas in which multiple tenants can reside.

[0019] FIG. 1 shows an example of the functional configuration of a building management system according to an embodiment. Note that "DB" is an abbreviation for database. Also, an "implemented event" is an event that has been implemented. A "new event" is an event that is newly planned but has not been implemented. When a new event is implemented, the "new event" becomes an "implemented event." Also, in this embodiment, the "building manager" may be the building owner, or a person entrusted by the building owner with planning and implementing new events (for example, an employee of a building management company).

[0020] The building management system 100 has an event analysis unit 120 that analyzes events being held, an event planning support unit 130 that supports the planning of new events, and an operation unit 140 that implements operations.

[0021] The executed event analysis unit 120 has a movement number calculation unit 121 , a executed event attribute input unit 122 , a stay number calculation unit 123 , a executed event evaluation unit 124 , and a executed event evaluation output unit 125 .

[0022] The moving number of people calculation unit 121 acquires elevator operation data (e.g., data representing the number of users boarding and alighting for each floor) and number of people sensor data for each floor (e.g., data representing the number of people obtained by a number of people sensor (e.g., the number of people entering and leaving)). The moving number of people calculation unit 111 creates people flow sensor data (i.e., data representing the time series of the number of people measured by the number of people sensor for each floor) from the time series of the number of people sensor data for each floor. The moving number of people calculation unit 121 calculates the number of people moving between floors based on the elevator operation data and the people flow sensor data for each floor, and outputs moving number of people data representing the calculated moving number of people. The moving number of people data is, for example, data of an OD (Origin-Destination) matrix representing the number of people moving from the source floor to the destination floor. The elevator operation data may be, for example, data representing the number of people boarding and alighting for each floor, or the number of passengers between floors. The number of people sensor data for each floor may be data representing the number of people entering and leaving the floor, or the number of people staying. At each point in time, the number of people entering a floor may be a number based on the total number of people getting off the elevator on that floor and the number of people passing through the entrance to that floor, and the number of people exiting a floor may be a number based on the total number of people getting on the elevator on that floor and the number of people passing through the exit to that floor.

[0023] The executed event attribute input unit 122 inputs executed event attribute data representing attributes of the executed event (for example, the type of event, the execution time, and the execution floor).

[0024] The visitor number calculation unit 123 identifies the event attributes from the event attribute data, and calculates the number of people who move from the office floor to the event floor (the floor where the event is held) and stay there for each time period during the event time (for example, the day of the event, the day of the week, the start time, and the end time of the event) represented by the identified event attribute, based on the moving number data. That is, the visitor number calculation unit 123 creates visitor number time series data representing the time series of the number of people staying on the event floor for each office floor. In this embodiment, the event floor is not an office floor (that is, the event is not held on a floor where a tenant may be present), but in the present invention, the office floor and the event floor may be the same floor. The visitor number time series data may be created from the time series data of the number of visitors and the time series data of the number of exiting visitors (for example, the visitor number from (x-1) o'clock to x o'clock may be the total number of visitors who entered floor X by x o'clock minus the total number of exiting floor X by x o'clock). Also, the time series data of the number of people entering may be created based on the time series of the input elevator operation data (and / or the time series of the people sensor data of the number of people entering on floor X) (for example, the number of people entering from (x-1) o'clock to x o'clock may be the sum of the total number of people who got off the elevator to floor X from (x-1) o'clock to x o'clock and the total number of people who entered floor X through the entrance of floor X from (x-1) o'clock to x o'clock). Also, the time series data of the number of people exiting may be created based on the time series of the input elevator operation data (and / or the time series of the people sensor data of the number of people getting on the elevator from floor X) (for example, the number of people exiting from (x-1) o'clock to x o'clock may be the sum of the total number of people who got on the elevator from floor X from (x-1) o'clock to x o'clock and the total number of people who left floor X through the exit of floor X from (x-1) o'clock to x o'clock).

[0025] The event evaluation unit 124 calculates the interest level and interaction level of the event to be held as an evaluation value of the event to be held based on the time series data of the number of people staying on each office floor. The interest level is the level of interest in the event, and is calculated for each office floor. The interaction level is the level of interaction between office floors (tenants) at the event, and is calculated for each office floor group. The "interaction level" may be the level of interaction between one floor and another, or between one floor and multiple floors. In other words, the "interaction level" may be an example of an evaluation value for an office floor group (evaluation values ​​of multiple office floors belonging to a group), or an example of an evaluation value for one office floor. The "office floor group" is a group consisting of two or more office floors with the event holding floor as the destination floor. The event evaluation unit 124 creates event evaluation result data, which is data representing an evaluation result based on the interest level of each office floor and the interaction level of each office group, and stores the event evaluation result data in the evaluation result DB 126. The level of interest may also be calculated for each office floor group.

[0026] The performed event evaluation output unit 125 outputs the performed event evaluation result data to a building management terminal, which will be described later.

[0027] The event planning assistance unit 130 includes a new event attribute input unit 131 , a new event evaluation unit 132 , and a new event evaluation output unit 133 .

[0028] The new event attribute input unit 131 inputs new event attribute data representing the attributes of a new event (e.g., the type of event, the planned implementation time (e.g., the planned date, day of the week, planned start time and planned end time of the new event), and the planned floor on which the event is to be held).

[0029] The new event evaluation unit 132 identifies, from the evaluation result DB 126, implemented event evaluation result data of implemented events having implemented event attributes similar to the new event attributes represented by the new event attribute data. The new event evaluation unit 132 predicts the interest level and interaction level of the new event based on the identified implemented event evaluation result data. The interest level of the new event is predicted for each office floor, and the interaction level of the new event is calculated for each office floor group. An "office floor group" is a group consisting of two or more office floors with the floor on which the event is scheduled to be held as the destination floor. The new event evaluation unit 132 creates new event evaluation result data, which is data representing an evaluation result based on the predicted interest level of each office floor and the predicted interaction level of each office group.

[0030] The new event evaluation output unit 133 outputs the new event evaluation result data to a building management terminal, which will be described later.

[0031] The operation unit 140 has an event guide unit 141. The event guide unit 141 determines two or more floors with high predicted interest and interaction levels based on the new event evaluation result data, and guides the new event to tenants (e.g., employees of the tenants) on each determined floor and tenants who are moving to or from the determined floor. The guidance of the new event is performed, for example, at an elevator landing on an office floor or in an elevator car. Specifically, the event guide unit 141 transmits event guidance data representing the guidance of the new event (e.g., new event attributes of the new event) to a display device at the elevator landing, a signage device on the floor, and a display device in the elevator car.

[0032] This embodiment will be described in detail below.

[0033] FIG. 2 shows an example of the overall configuration of a system including the building management system 100.

[0034] A building management system 100, an elevator group control system 202, a hall display device 204, a signage device 205, a people sensor 206, and a building management terminal 207 are communicatively connected to a network 250 within the building.

[0035] The building management system 100 is a physical computer system, but is not limited thereto and may be a logical computer system based on a physical computer system (for example, a system in a cloud environment). The building management system 100 has an interface device 171 connected to a network 250, a storage device 172, and a processor 173 connected to the devices 171 and 172. Communication is performed via the interface device 171. The storage device 172 stores the evaluation result DB 124 shown in FIG. 1. In addition, the processor 173 loads and executes a computer program from the storage device 172 to realize functions such as the implemented event analysis unit 120, the event planning support unit 130, and the operation unit 140. The building management system 100 receives elevator operation data from the elevator group management system 202 (arrow 251), receives people sensor data from the people sensor 206 for each floor (arrow 255), and receives event attribute data of implemented events and new events from the building management terminal 207 (arrow 256). In addition, the building management system 100 outputs event guide data to the car display device 203, the hall display device 204, and the signage device 205 (arrows 252A to 252C), and outputs evaluation result data of ongoing events and new events to the building management terminal 207 (arrow 257).

[0036] The elevator group control system 202 controls the operation of each elevator 201 (e.g., the raising and lowering of the car). The elevator group control system 202 transmits elevator operation data of each elevator to the building management system 100 (arrow 251). The elevator group control system 202 also transmits event guide data to an in-car display device 203 (a display device provided in the car) of the elevator 201 (arrow 252A). The in-car display device 203 receives the event guide data and displays the event guide represented by the received event guide data.

[0037] The landing display device 204 is a display device provided at the landing of the elevator 201. It is provided at the landing of at least one floor (for example, each floor where a tenant may reside). The landing display device 204 receives event information data from the building management system 100 (arrow 252B), and displays the event information represented by the received event information data.

[0038] Signage device 205 is installed on at least one floor (for example, each floor) in a building. Signage device 205 receives event guide data from building management system 100 (arrow 252C) and displays the event guide represented by the received event guide data.

[0039] The number of people sensor 219 is a device that measures the number of people entering and leaving a floor, and may be, for example, a device (e.g., an entrance and exit management device) that measures the number of people entering and leaving a floor (typically, a certain area on a floor). The number of people sensor 219 may be provided on each floor. The number of people sensor 219 transmits people sensor data indicating the measured number of people to the building management system 100 (arrow 255).

[0040] The building management terminal 207 may be an information processing terminal for a building manager (for example, a personal computer or a smartphone). The building management terminal 207 accepts input of event attributes for events in the building, and transmits event attribute data representing the event attributes to the building management system 100 (arrow 256). The building management terminal 207 also receives evaluation result data of the event from the building management system 100 (arrow 257), and displays the evaluation result represented by the evaluation result data.

[0041] FIG. 3 illustrates an example of an overview of an office building according to an embodiment.

[0042] The office building 300 has a plurality of floors 320, each of which includes two or more office floors 320T that can be occupied by tenants. The plurality of floors 320 may include floors that cannot be occupied by tenants, such as a lobby floor 320L and a common floor 320S (e.g., a floor having a common area such as a lounge area). In this embodiment, there is one common floor 320S, and the common floor 320S is an event implementation floor. However, in the present invention, any floor may be an event implementation floor.

[0043] A number of people sensor 206 and a landing display device 204 are provided at each floor 320 (e.g., a landing 321 of the elevator 101), and an in-car display device 203 is provided inside a car 310 of the elevator 101. For example, each office floor 320 is provided with an entrance / exit 340 for an exclusive area of ​​a tenant, and a number of people sensor 206 may be provided near the entrance / exit 340.

[0044] FIG. 4 shows an example of the flow of processing performed by the executed event analysis unit 120.

[0045] The held event analysis unit 120 determines whether the event to be evaluated is a held event (S401).

[0046] When the judgment result of S401 is true (S401: YES), the executed event analysis unit 120 inputs elevator operation data and people flow sensor data for the time including the event execution time of the executed event to be evaluated (S402), and creates the number of people moving data for each time interval based on the input data (S403). In addition, the executed event analysis unit 120 inputs the executed event attribute data of the executed event to be evaluated (S404).

[0047] The executed event analysis unit 120 identifies the executed event attribute from the input executed event attribute data, and for each time interval in the event execution time represented by the identified executed event attribute, calculates the number of people who moved from the office floor to the event execution floor (the floor where the event was held) and stayed there based on the moving number data for that time interval and the calculated number of people staying up to that time interval. In other words, the executed event analysis unit 120 creates visitor number time series data representing the time series of the number of people staying on the event execution floor for each office floor (S405).

[0048] The held event analysis unit 120 calculates the interest level of the held event for each office floor based on the time series data of the number of people visiting each office floor (S406). In addition, the held event analysis unit 120 calculates the interaction level of the held event for each office floor group based on the time series data of the number of people visiting each office floor (S407).

[0049] The implemented event analysis unit 120 creates implemented event evaluation result data based on the level of interest in each office floor and the level of interaction in each office group, and outputs the implemented event evaluation result data to the building management terminal 207 (S408). The implemented event analysis unit 120 also stores the implemented event evaluation result data in the evaluation result DB 126. The implemented event evaluation result data is associated with event attribute data of the evaluated implemented event. In addition to the evaluation result data, the evaluation result DB 126 may include at least some of the following data: event attribute data, time-series data on the number of visitors, data representing the level of interest in each office floor, and data representing the level of interaction in each office floor group.

[0050] FIG. 5 shows a schematic example of the movement number calculation in S403 of FIG.

[0051] The elevator operation data indicates the disembarking floor and the number of disembarking passengers for each boarding floor. According to the example shown in FIG. 5, the elevator operation data indicates that three passengers boarded from the first floor, one of them disembarked on the fifth floor, and the remaining two passengers disembarked on the seventh floor. The floor at which the passengers boarded and disembarked may be estimated from a weight sensor that measures the weight inside the car, a floor (floor where the car call was made) corresponding to the button inside the car pressed at the boarding floor, a camera installed at the landing or inside the car, or the like. The elevator operation data may exist for each time period, and the number of passengers moving for each time period is created from the elevator operation data for each time period.

[0052] FIG. 6 shows an example of the movement number data generated in S403 of FIG.

[0053] The movement number data is data of an OD (Origin-Destination) matrix that indicates the number of people who moved from a source floor to a destination floor. The movement number data may be created from elevator operation data or people flow sensor data. In the example shown in FIG. 6, floors other than the 4th to 8th floors are omitted.

[0054] The range indicated by reference numeral 601 represents the number of people who entered the event floor from each floor. The range indicated by reference numeral 603 represents the number of people who left the event floor to each floor. Such movement number data is created for each time interval (e.g., unit time). The number of people staying on the event floor for each time interval can be calculated from the time series of the movement number data. As a specific example, the number of users from the 4th floor among the number of people staying on the 8th floor (event floor) at 17:35 can be calculated as follows. The movement number data shown in FIG. 6 represents the number of people moving between 17:30 and 17:35. Assume that the number of users who moved from the 4th floor to the 8th floor at 17:30 is 3. This can be expressed as "Np(fo=4,fd=8,t=17:30)=3". Np is the number of users. fo is the source floor. fd is the destination floor. t is the time. According to the data shown in Figure 6, the number of passengers who moved from the 4th floor to the 8th floor between 17:30 and 17:35 was 14. According to the data shown in Figure 6, the number of users who moved from the 8th floor to the 4th floor between 17:30 and 17:35 was 1. Therefore, the number of people staying on the 8th floor at 17:35 (the number of people staying from the 4th floor) is 3 + 14 - 1 = 16. This can be expressed as Np (fo = 4, fd = 8, t = 17:35) = 16.

[0055] FIG. 7 shows a schematic example of the interest level calculation in S406 of FIG.

[0056] 7, the office floors are the 5th, 6th, and 7th floors, and the event will take place from 14:50 to 16:05. For each floor, the time series of the number of people visiting is expressed in two-dimensional orthogonal coordinates, with the horizontal axis corresponding to time and the vertical axis corresponding to the number of people visiting.

[0057] The interest level for each office floor is calculated based on the time series data of the number of people visiting that office floor. The cumulative or maximum value of the number of people visiting may affect the interest level. For example, the interest level may be determined based on either (1) or (2) below, or on both (1) and (2). Note that T is the length of time the event is held, and Δt is the number of people visiting and the length of time that number of people visiting continues. (1) Interest level = (1 / T)Σ(number of visitors × △t) (2) Interest level = maximum number of people present during the event

[0058] The degree of interest may also be calculated for each office floor group. According to the example shown in Fig. 7, for an office floor group consisting of the 5th, 6th, and 7th floors, the visitor count time series data for the 5th, 6th, and 7th floors that make up the office floor group may be merged, and the degree of interest for the office floor group may be calculated based on the merged visitor count time series data. Alternatively, the degree of interest for the office floor group may be calculated based on the degree of interest for each of the 5th, 6th, and 7th floors that make up the office floor group (for example, the degree of interest for the office floor group may be the sum of the degrees of interest for the multiple floors that make up the office floor group).

[0059] Fig. 8 shows a schematic example of the interaction degree calculation in S406 in Fig. 4. According to Fig. 8, a group consisting of the 6th and 7th floors is given as an example of an office floor group.

[0060] The degree of interaction of m floors (m is an integer of 2 or more) constituting the office floor group is a value based on the correlation of the number of people visiting the m floor at the event implementation time, for example, a correlation coefficient. Specifically, for example, the degree of interaction of the m floor may be based on the overlap of the visitor number time series of the m floor at the event implementation time, that is, the length of time during which the visitor numbers overlap and the number of people who overlap. According to the example shown in FIG. 8, the correlation coefficient is calculated based on the length of time during which the visitor numbers overlap (specifically, the sum of 15:15 to 15:35 and 15:45 to 16:00) and the number of people who overlap on the 6th floor and the 7th floor. More specifically, for example, the degree of interaction of floors A and B may be based on the length of time during which the visitor numbers overlap on floors A and B and the product of N(fl=A, t) and N(fl=B, t) for each time. Here, "N(fl=A, t)" is the number of people visiting the event implementation floor from floor A at time t. In addition, when calculating the degree of interaction between one floor and multiple other floors, that is, when calculating the degree of interaction for one floor when m is 3 or more, the number of people staying on the floors that overlap can be considered in the same way. For example, when calculating the degree of interaction between floor C and other floors in the building, it may be based on the product of N(fl=C,t) for each time and the sum of the number of people staying on floors other than floor C where the event is held at time t. In other words, the product of N(fl=C,t) and N(fl=D,t)+N(fl=E,t)+N(fl=F,t)···+N(fl=X,t) may be calculated (D,E,F,...,X are examples of floors other than floor C). In addition, when calculating the degree of interaction between floor C and specific floors D and E, it may be based on the product of N(fl=C,t) for each time and N(fl=D,t)+N(fl=E,t). It should be noted that the degree of interaction does not necessarily have to be calculated based on both the length of time that the number of people staying there overlaps and the number of people staying there overlaps between floors. For example, the degree of interaction between floors A and B may be based on the product of N(fl=A,t) and N(fl=B,t) for each time. This is because when calculating the degree of interaction between floors at an event, it is possible to assume that there was interaction by participating in the same event, without considering the length of time.

[0061] In this embodiment, the number of floors constituting the office floor group is assumed to be two (that is, the value of m is always assumed to be two).

[0062] FIG. 9 shows a schematic example of the degree of alternating current calculated in S406 of FIG.

[0063] According to the example shown in FIG. 9, it can be seen that the degree of interaction between the sixth and seventh floors and the degree of interaction between the fifth and sixth floors are high (a large number of people interacted and / or the duration of the interaction was long).

[0064] The level of interaction may be determined based on the result of comparing the level of interaction with a threshold value. The threshold value of the level of interaction may be a fixed value, or may be a value determined based on the levels of interaction of all office floor groups. Similarly, the level of interest may be determined based on the result of comparing the level of interest with a threshold value. The threshold value of the level of interest may be a fixed value, or may be a value determined based on the levels of interest of all office floors.

[0065] FIG. 10 shows an example of the flow of processing performed by the event planning assistance unit 130.

[0066] The event planning assistance unit 130 determines whether the event to be evaluated is a new event (S1001).

[0067] If the determination result in S1001 is true (S1001: YES), the event planning assistance unit 130 inputs new event attribute data of the new event to be evaluated (S1002).

[0068] The event planning support unit 130 identifies an implemented event having an implemented event attribute similar to the new event attribute represented by the input new event attribute data from the evaluation result DB 126 (S1003). Specifically, for example, the event planning support unit 130 calculates the similarity between the new event attribute and the implemented event attribute of each implemented event identified from the evaluation result DB 126 (a known method may be used to calculate the similarity). The event planning support unit 130 identifies an implemented event attribute having a similarity in the top X (X is a natural number), and identifies an implemented event having the identified implemented event attribute. In calculating the similarity of the event attributes, the weight of each item belonging to the event attribute may be adjusted. Hereinafter, the implemented event identified in S1003 is referred to as a "similar implemented event".

[0069] The event planning support unit 130 identifies the implemented event evaluation result data of the similar implemented event from the evaluation result DB 126, identifies the interest level of each office floor from the implemented event evaluation result data, and predicts the interest level of each office floor for the new event (S1004). For example, for each office floor, the interest level of the similar implemented event may be calculated by a method such as weighted averaging according to the similarity (similarity of event attributes) between the similar implemented event and the new event. The calculated interest level may be the predicted interest level.

[0070] The event planning support unit 130 identifies the interaction degree of each office floor group from the implemented event evaluation result data of the similar implemented event, and predicts the interaction degree of each office floor group for the new event (S1005). For example, for each office floor group, the interaction degree of the similar implemented event may be calculated by a method such as weighted average according to the similarity (similarity of event attributes) between the similar implemented event and the new event. The calculated interaction degree may be the predicted interaction degree.

[0071] The event planning support unit 130 outputs new event evaluation result data of the new event to the building management terminal 207 (S1006). The new event evaluation result data includes data representing the predicted interest level for each office floor and the predicted interaction level for each office floor group. After S1006, the event planning support unit 130 determines whether the new event has been adopted by the building manager (S1007).

[0072] The building manager looks at the information displayed on the building management terminal 207 based on the new event evaluation result data (evaluation results including predicted levels of interest and interaction for the new event) and decides whether or not to adopt the new event.

[0073] When adopting a new event, the building manager inputs the adoption of the new event to the building management system 100 (for example, inputs the adoption of the new event to a GUI that displays the evaluation results of the new event). In this case, since the event planning support unit 130 receives the input of the adoption of the new event, the determination result of S1007 becomes true (S1007: YES), and the process ends.

[0074] On the other hand, if the new event is not adopted, the building manager inputs the event attributes of the changed new event to the building management system 100 (for example, changing the content (event type) of the new event, or changing the scheduled date or time of the event without changing the content of the new event). In this case, the determination result of S1007 is false (S1007: NO), and S1002 is performed.

[0075] In S1006, the performed event evaluation result data of a similar performed event is also output to the building management terminal 207 together with the new event evaluation result data, and the evaluation result represented by the performed event evaluation result data may also be displayed on the building management terminal 207.

[0076] FIG. 11 shows an example of the flow of processing performed by the operation unit 140.

[0077] The operation unit 140 determines whether or not to introduce a new event (S1101). For example, the operation unit 140 determines whether or not new event attribute data of a new event to be introduced is in the evaluation DB 126. A "new event to be introduced" is a new event that satisfies certain conditions, such as the number of times it has been introduced is less than a predetermined number of times, or the time until the event start time is less than a predetermined time. Hereinafter, in the explanation of FIG. 11, a new event to be introduced is referred to as a "event to be introduced".

[0078] If the result of the determination in S1101 is true (S1101: YES), the operation unit 140 determines whether the announcement target event has been evaluated (specifically, whether new event evaluation result data for the announcement target event exists in the evaluation result DB 126) (S1102).

[0079] If the determination result in S1102 is true (S1102: YES), the operation unit 140 acquires new event evaluation result data of the announcement target event from the evaluation result DB 126 (S1103).

[0080] If the determination result of S1102 is false (S1102: NO), the operation unit 140 acquires from the evaluation result DB 126 the executed event evaluation result data of the executed event that is most similar to the announcement target event (S1104). Specifically, for example, the operation unit 140 identifies the new event attribute of the announcement target event and the executed event attribute of each executed event from the evaluation result DB 126, and calculates the similarity between the new event attribute and the executed event attribute of each executed event. The operation unit 140 identifies the highest similarity among the calculated similarities, and acquires from the evaluation result DB 126 the executed event evaluation result data of the executed event that has the executed event attribute with the identified similarity.

[0081] Hereinafter, the evaluation result data acquired in S1103 or S1104 will be referred to as “target evaluation result data.” The management unit 140 refers to the target evaluation result data and identifies floors with high interest levels or similarities (S1105).

[0082] The operation unit 140 creates event guidance data for the event to be guided (for example, data including information indicating new event attributes of a new event) and provides event guidance based on the event guidance data through the boarding area display device 204 or signage device 205 on the floor specified in S1105 (S1106). In other words, the operation unit 140 transmits the event guidance data for the event to be guided to the boarding area display device 204 or signage device 205 on the floor specified in S1105.

[0083] Furthermore, the operation unit 140 provides event guidance based on the event guidance data of the event to be guided, through the in-car display device 203 of the car that is stopped or is scheduled to stop at the floor specified in S1105 (S1107). The fact that the car is "stopped at the floor specified in S1105" or "scheduled to stop at the floor specified in S1105" can be specified from data from the elevator group control system 202 (e.g., data including data indicating the current position of the car and data indicating the floor where the car call was made).

[0084] FIG. 12 shows an example of the flow of the process of evaluating the level of interest in an event.

[0085] The process of evaluating the level of interest in an event is included in S408 in Fig. 4 and S1006 in Fig. 10. The process will be described below by taking S408 in Fig. 4 as an example.

[0086] The conducted event analysis unit 120 sorts the interest levels in descending order (S1201), creates a conducted event level of interest table including information on the top Y1 (Y1 is a natural number) interest levels (S1202), and outputs the table to memory (S1203).

[0087] The table of the level of interest in the carried out event is included in the table of evaluation results of the carried out event, and is output to the building management terminal 207 and / or stored in the evaluation result DB 126 .

[0088] FIG. 13 shows an example of the structure of a table of the level of interest in held events.

[0089] The table of interest levels in completed events includes completed event attribute data (data indicating the event type, event duration, and floor on which the event is held) of the completed event to be evaluated, and interest level evaluation result data in which the interest levels of the top Y1 (Y1=3 in FIG. 13) are arranged in descending order. The interest level evaluation result data indicates, for each interest level, the rank, floor, interest level, and overall ratio. For each interest level, the overall ratio is the ratio of the interest level to the total interest levels of all floors.

[0090] FIG. 14 shows an example of the flow of an event interaction evaluation process.

[0091] The event interaction evaluation process is also included in S408 in Fig. 4 and S1006 in Fig. 10. The process will be described below by taking S408 in Fig. 4 as an example.

[0092] The carried out event analysis unit 120 sorts the interaction degrees in descending order (S1401), creates a carried out event interaction degree table including information on the top Y2 (Y2 is a natural number) interaction degrees (S1402), and outputs the table to memory (S1403).

[0093] The completed event interaction level table is included in the completed event evaluation result table, and is output to the building management terminal 207 and / or stored in the evaluation result DB 126 .

[0094] FIG. 15 shows an example of the structure of an implemented event interaction level table.

[0095] The implemented event interaction level table includes implemented event attribute data of the implemented event to be evaluated, and interaction level evaluation result data in which the interaction levels of the top Y2 (Y2=3 in FIG. 15) are arranged in descending order. The interaction level evaluation result data indicates, for each interaction level, the rank, the office floor group element (the floor on which the office floor is located), and the interaction level.

[0096] The explanation with reference to Figs. 12 to 14 takes an example of an ongoing event, but the same processing can be performed for a new event.

[0097] That is, the event planning support unit 130 creates a new event interest level table including information on the top Y1 interest levels. The new event interest level table is included in the new event evaluation result table. The new event interest level table includes new event attribute data (data representing the event type, scheduled time, and scheduled floor) of the new event to be evaluated, and interest level evaluation result data in which the top Y1 interest levels are arranged in descending order.

[0098] In addition, the event planning support unit 130 creates a new event interaction degree table including information on the top Y2 interaction degrees. The new event interaction degree table is included in the new event evaluation result table. The new event interaction degree table includes new event attribute data of the new event to be evaluated, and interaction degree evaluation result data in which the top Y2 interaction degrees are arranged in descending order. The interaction degree evaluation result data indicates, for each interaction degree, the rank, the office floor group element (the floor on which the office floor is located), and the interaction degree.

[0099] Although one embodiment has been described above, this is merely an example for explaining the present invention, and the scope of the present invention is not limited to this embodiment. The present invention can be implemented in various other forms.

[0100] The above description can be summarized as follows. The following summary may include supplementary explanations and explanations of modifications of the above description.

[0101] Events held within buildings are adopted as a tool for providing added value to tenants. It is difficult for a building manager (e.g., a building administrator) to obtain sufficient information about tenants to be able to accurately estimate what kind of event is appropriate for providing added value, and therefore it is difficult to accurately estimate what kind of event is appropriate for providing added value. Such a technical problem is solved by a technical means.

[0102] That is, a building management system (e.g., building management system 100) includes a visitor number calculation unit and an implemented event evaluation unit. The visitor number calculation unit calculates a time series of the visitor number, which is the number of people who move from a tenant area and stay in the event implementation area, for each pair of a tenant area (e.g., an office floor) where a tenant may reside and an event implementation area (e.g., an event implementation floor) of the implemented event, based on a time series of the visitor number data indicating the number of people moving for each pair of a source area (e.g., a source floor) and a destination area (e.g., a destination floor). The implemented event evaluation unit outputs an evaluation value of the implemented event for each tenant area (and / or each tenant area group (e.g., each office floor group)) based on the calculated time series of the visitor number for each pair of a tenant area and an event implementation area.

[0103] Based on the evaluation of the implemented event, the building manager can plan and implement a new event that can be added value to the tenant, and the implementation of the new event becomes added value provided to the tenant. Note that one tenant area may be an area where one tenant can reside, or may be an area where two or more tenants can reside. For each of a plurality of areas, area attribute data that is data representing the attribute of the area (e.g., the use of the area, and if the area is a tenant area, the attribute of the tenant residing in the area (e.g., the tenant name, the business type, etc.)) may be stored in the building management system. The implemented event evaluation result may include an area attribute identified from the area attribute data for an area corresponding to an index value included in the implemented event evaluation result. In addition, the building management system may include an implemented event evaluation output unit, and the implemented event evaluation unit may output an evaluation value of the implemented event for each tenant area, output implemented event evaluation result data representing the implemented event evaluation result based on the evaluation value, and the implemented event evaluation output unit may output the implemented event evaluation result represented by the implemented event evaluation result data. In addition, the implemented event evaluation unit may output an evaluation value of the implemented event for each tenant area and / or each tenant area group based on the event implementation time of the implemented event, in addition to the calculated time series of the number of visitors for each pair of tenant area and event implementation area.

[0104] The multiple areas of the building may include multiple floors. The moving number of people data may be data created based on at least one of elevator operation data and people flow sensor data (for example, if the building is one-story, the moving number of people data may be created based on the people flow sensor data). The elevator operation data is data created based on the floors where users get on and off and the change in weight inside the car, and may be data that represents, for each floor, the number of people getting on at that floor and the number of people getting off at one or more floors. The people flow sensor data may be data that represents a time series of the number of people measured by a people sensor installed on each floor or area. By such technical means, the moving number of people data is created, and from the time series of the created moving number of people data, a time series of the number of people staying from the tenant area to the event implementation area can be calculated for each pair of the tenant area and the event implementation area.

[0105] The building management system may further include an event execution attribute input unit for inputting event execution attribute data representing event execution attributes, which are attributes of an event execution. The event execution attributes may include at least one of the type of event execution (e.g., content of the event execution, characteristics of the event execution), event execution time (e.g., date, day of the week, time period), and event execution area. The event execution attribute data of the event execution may be associated with the event execution evaluation result data. This allows the building manager to predict appropriate new event attributes for a new event from the relationship between the event execution evaluation result and the event execution attributes.

[0106] For each tenant area, the evaluation value of the implemented event may be the degree of interest in the implemented event for that tenant area. For each tenant area, the degree of interest in the implemented event may be based on statistics of the number of people staying in the event implementation area from that tenant area during the event implementation time. This makes it possible to estimate the degree of interest in each tenant area from the time series of the number of people staying calculated for each tenant area. For example, for each tenant area, the degree of interest in the implemented event may be based on the length of the event implementation time, the number of people staying in the event implementation area from that tenant area during the event implementation time, and the length of time that the number of people staying continues.

[0107] For each tenant area group, the evaluation value of the implemented event may be the interaction degree of the implemented event for the tenant area group. For each tenant area group, the interaction degree of the implemented event may be based on the overlap degree of the time series of the number of visitors in two or more tenant areas that constitute the tenant area group. This makes it possible to estimate the interaction degree between the tenant areas that constitute each tenant area group from the calculated time series of the number of visitors for each tenant area that constitutes the tenant area group. Note that, for each tenant area group, the interaction degree of the implemented event may be based on the value of the correlation coefficient of the time series of the number of visitors in two or more tenant areas that constitute the tenant area group.

[0108] The evaluation value of the implemented event may include both the interest level of the implemented event for each tenant area and the interaction level of the implemented event for each tenant area group. This is expected to lead to more appropriate planning of new events. For example, in order to plan a new event that is expected to have a high interaction level, the building manager can compare an implemented event attribute in which the interest level of each tenant area constituting a tenant area group is high but the interaction level of the tenant area group is low, with an implemented event attribute in which the interest level of each tenant area constituting a tenant area group is low but the interaction level of the tenant area group is high.

[0109] The building management system may further include a new event attribute input unit, a new event evaluation unit, and a new event evaluation output unit. The new event attribute input unit may input new event attribute data representing a new event attribute that is an attribute of a new event. The new event evaluation unit may predict an evaluation value of the new event for each tenant area or each tenant area group from the similarity between the new event attribute and the implemented event attribute and the evaluation value of the implemented event (for example, by changing the evaluation value of the implemented event by a degree according to the similarity), and create new event evaluation result data representing a new event evaluation result based on the predicted evaluation value of the new event for each tenant area or each tenant area group. The new event evaluation output unit may output the new event evaluation result represented by the new event evaluation result data to the building manager. This allows the building manager to determine whether the new event is appropriate, i.e., whether the implementation of the new event will add value to the tenants.

[0110] For example, if the evaluation value of the new event is the degree of interest, the number of participants in the new event can be estimated. Also, for example, if the evaluation value of the new event is the degree of interaction, the degree of interaction between tenants at the new event can be estimated. If there is a new event evaluation output unit, the implemented event evaluation output unit does not need to be present. The new event evaluation output unit may output an implemented event evaluation result of an implemented event similar to the new event in addition to the new event evaluation result, or the implemented event evaluation result may not necessarily be output since the implemented event is a past event.

[0111] In addition, the following (A) to (D) may be performed. This is expected to lead to the planning of new events with better new event attributes. For example, by repeatedly changing one element or one combination of elements among multiple elements (e.g., event type, planned event implementation time, planned event implementation area) included in the new event attributes and not changing the others, and finding the predicted evaluation value of the new event with the new event attribute after such a change, it is possible to adopt the new event with the new event attribute with the best predicted evaluation value. (A) Based on the new event evaluation result output by the new event evaluation output unit, it is determined whether or not the new event with the new event attribute is adopted by the building manager. This determination may be made, for example, based on whether or not the new event evaluation output unit receives a "yes" for adoption from the building manager. (B) If the determination result of (A) is false, the new event attribute input unit may receive input of new event attribute data representing a new event attribute from the building manager. (C) The new event evaluation unit creates new event evaluation result data for the new event having the new new event attribute. (D) A new event evaluation output unit outputs the new event evaluation result represented by the created new event evaluation result data. (E) Return to (A).

[0112] The building management system may further include an event information unit. The event information unit may provide information about the new event through an output device (e.g., the landing display device 204 or the signage device 205) provided in the tenant area or each tenant area constituting the tenant area group whose evaluation value of the new event satisfies a predetermined condition, and / or an output device (e.g., the car display device 203) in an elevator car that is stopped or is scheduled to stop in the tenant area or each tenant area constituting the tenant area group whose evaluation value satisfies a predetermined condition. As a result, the new event is unlikely to be provided to a tenant with a low evaluation value of the new event, so that an event that is not necessary for the tenant to be provided to the tenant is unlikely to be provided to the tenant, and thus, efficient new event information can be provided, and added value can be provided to the tenant that unnecessary new event information is not output to the tenant. In addition, when an evaluation value has not yet been predicted for a new event, the event announcement unit may identify implemented event evaluation result data for an implemented event having an implemented event attribute most similar to the new event attribute, and announce the new event through an output device provided in the tenant area or each tenant area constituting a tenant area group whose evaluation value represented by the identified implemented event evaluation result data satisfies a predetermined condition, and / or an output device in an elevator car parked or scheduled to stop in the tenant area or each tenant area constituting a tenant area group whose evaluation value satisfies the predetermined condition. This is expected to provide efficient announcement of the new event even if the new event has not yet been evaluated.

[0113] Also, instead of the new event attribute input unit, a new event attribute suggestion unit may be prepared. The new event attribute suggestion unit may use the implemented event attribute data of the past implemented events and the implemented event evaluation result data (for example, data including a pair of a tenant area or a tenant area group and an evaluation value) as teacher data to learn a machine learning model in which the new event evaluation result is input and a new event attribute is output. The new event attribute suggestion unit may receive a designation of a desired evaluation result (for example, a tenant area or a tenant area group and an event evaluation value (for example, an interest level or an interaction level) to be obtained for the tenant area or the tenant area group) from the building manager. Then, the new event attribute suggestion unit may input the designated evaluation result into the machine learning model, thereby outputting a new event attribute that is expected to obtain the designated evaluation result, and may propose the outputted new event attribute to the building manager (data representing the outputted new event attribute may be transmitted to the information processing terminal of the building manager).

[0114] Additionally, in this specification, a "tenant" is typically a company with one or more employees, but may also be an individual. A "tenant area" may consist of one tenant, and an "event implementation area" may consist of one tenant. In other words, there may be one tenant in a tenant area, and there may also be one tenant in an event implementation area. For example, a dinner party may be held between tenant B and tenant C at restaurant A (an example of an event implementation area). [Explanation of symbols]

[0115] 100: Building Management System

Claims

1. a visitor number calculation unit that calculates, for each pair of a tenant area where a tenant may reside and an event implementation area where an event is to be implemented, a time series of a visitor number that is the number of people who have moved from the tenant area and are staying in the event implementation area, based on a time series of mover number data that indicates the number of people moving for each pair of a source area and a destination area; an implemented event evaluation unit that outputs, for each tenant area, an evaluation value of an implemented event, which is an implemented event, based on the calculated time series of the number of visitors for each pair of the tenant area and the event implementation area; A building management system equipped with:

2. An execution event evaluation output unit is provided, the performed event evaluation unit outputs an evaluation value of the performed event for each tenant area, and outputs performed event evaluation result data representing a performed event evaluation result based on the evaluation value; the performed event evaluation output unit outputs the performed event evaluation result represented by the performed event evaluation result data. The building management system of claim 1.

3. The implemented event evaluation unit outputs an evaluation value of the implemented event for each tenant area and / or each tenant area group. The building management system according to claim 2.

4. The implemented event evaluation unit outputs an evaluation value of the implemented event for each tenant area and / or each tenant area group based on the event implementation time of the implemented event in addition to the calculated time series of the number of visitors for each pair of the tenant area and the event implementation area. The building management system according to claim 3.

5. the plurality of areas includes a plurality of floors; The moving number data is data created based on at least one of elevator operation data and people flow sensor data, The elevator operation data is data created based on floors where passengers get on and off and changes in weight inside the car, and is data representing, for each floor, the number of passengers getting on at that floor and the number of passengers getting off at one or more floors, The people flow sensor data is data representing a time series of the number of people measured by a people flow sensor installed on each floor or each area. The building management system of claim 1.

6. An event attribute input unit for inputting event attribute data representing an event attribute that is an attribute of the event, The event attributes include at least one of a type of the event, an event execution time, and an event execution area; The implemented event evaluation result data is associated with implemented event attribute data of the implemented event. The building management system according to claim 4.

7. For each of the tenant areas, the evaluation value of the held event is a degree of interest in the held event for the tenant area; For each of the tenant areas, the interest level of the event is based on statistics of the number of people staying in the event implementation area from the tenant area during the event implementation time. The building management system according to claim 4.

8. For each of the tenant areas, the level of interest in the event is based on the length of the event implementation time, the number of people staying in the event implementation area from the tenant area during the event implementation time, and the length of time that the number of people staying continues. The building management system according to claim 7.

9. For each tenant area group, the evaluation value of the implemented event is the interaction level of the implemented event for the tenant area group; For each of the tenant area groups, the interaction degree of the event is based on the overlap degree of the time series of the number of visitors in two or more tenant areas constituting the tenant area group; The building management system according to claim 3.

10. The degree of interaction of the event is based on the value of a correlation coefficient of the time series of the number of visitors in two or more tenant areas constituting the tenant area group. The building management system according to claim 3.

11. The evaluation value of the implemented event includes both a degree of interest in the implemented event for each of the tenant areas and a degree of interaction in the implemented event for each of the tenant areas; For each of the tenant areas, the degree of interest in the event is based on statistics of the number of people staying in the event implementation area from the tenant area during the event implementation time, For each of the tenant area groups, the interaction degree of the event is based on the overlap degree of the time series of the number of visitors in two or more tenant areas constituting the tenant area group; The building management system according to claim 4.

12. a new event attribute input unit for inputting new event attribute data representing a new event attribute which is an attribute of the new event; a new event evaluation unit that predicts an evaluation value of the new event for each tenant area or each tenant area group from the similarity between the new event attribute and the implemented event attribute and the evaluation value of the implemented event, and creates new event evaluation result data that represents a new event evaluation result based on the predicted evaluation value for each tenant area or each tenant area group of the new event; a new event evaluation output unit that outputs a new event evaluation result represented by the new event evaluation result data; The building management system of claim 1 further comprising:

13. an event guidance unit that provides information about the new event through an output device provided in the tenant area or each tenant area constituting a tenant area group, where the evaluation value of the new event satisfies a predetermined condition, and / or an output device in an elevator car that is stopped or is scheduled to stop in the tenant area or each tenant area constituting a tenant area group, where the evaluation value satisfies the predetermined condition; The building management system of claim 12 further comprising:

14. When a rating value has not yet been predicted for the new event, the event guide unit Identifying performed event evaluation result data for performed events having performed event attributes most similar to the new event attributes; announcing the new event through an output device provided in the tenant area or each tenant area constituting the tenant area group in which the evaluation value represented by the identified implemented event evaluation result data satisfies a predetermined condition, and / or an output device in an elevator car that is stopped or is scheduled to stop in the tenant area or each tenant area constituting the tenant area group in which the evaluation value satisfies the predetermined condition; The building management system of claim 13.

15. The following steps (A) to (D) are carried out: (A) determining whether or not the new event having the new event attribute is adopted by a building manager based on the new event evaluation result output by the new event evaluation output unit; (B) if the determination result of (A) is false, the new event attribute input unit receives input of new event attribute data representing new event attributes from the building manager; (C) the new event evaluation unit creates new event evaluation result data for the new event having the new new event attribute. (D) the new event evaluation output unit outputs the new event evaluation result represented by the created new event evaluation result data to the building manager. (E) Return to (A); The building management system of claim 12.

16. calculating a time series of the number of people staying in each pair of a tenant area where a tenant may reside and an event implementation area where an event is to be implemented, the time series of the number of people staying in the event implementation area which is the number of people who have moved from the tenant area and are staying in the event implementation area, for each pair of a tenant area where a tenant may reside and an event implementation area where an event is to be implemented, based on a time series of the number of people moving data which indicates the number of people moving in each pair of a source area and a destination area; outputting, for each tenant area, an evaluation value of an implemented event, which is an implemented event, based on the calculated time series of the number of visitors for each pair of the tenant area and the event implementation area; A building management method that uses a computer.

Images