JP2015026302A - Entering/leaving management system and control method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an entering/leaving management system capable of calculating an area having a high energy saving effect.SOLUTION: An entering/leaving management system includes: an entering/leaving control device to which a card reader disposed in each of a plurality of management areas is connected for acquiring passage history information including a date when the card reader has read a card and a card reader number and the card ID of the read card and the occurrence event information of entering or leaving; a passage history table for storing passage history information transmitted from a plurality of entering/leaving control devices; and a DB server having a stay time table in which the stay time of the predetermined management area in each time zone of the management area is calculated for each card ID, and the sum of the stay time of all the card ID is calculated in each time zone of the predetermined management area on the basis of the passage history table.

Description

  The present invention relates to an entrance / exit management system, and more particularly to an entrance / exit management system suitable for grasping the number of people entering / exiting each management area.

  In recent years, energy-saving efforts in office buildings and condominiums have been strengthened, and existing lighting equipment and air-conditioning equipment may be replaced with equipment with low power consumption. When replacing equipment, it is important to predict energy savings and cost effectiveness. For example, Patent Document 1 calculates energy saving effect and necessary cost when a device installed in a building is replaced with a device that is expected to save power and water by inputting predetermined user information. Alternative device proposal systems have been proposed.

In addition, from the viewpoint of security such as information leakage and crime prevention, an entrance / exit management system has been introduced in which a gate is provided in a specific section of a building or building and entrance / exit is managed by an authentication card such as an IC card. In this entrance / exit management system, the passage of the gate can be permitted or prohibited according to the security level of the authentication card.
Some of the above-described alternative device proposal systems apply the technology of the room entry / exit management system. For example, in Patent Document 2, an area where there is a person based on the number of people in each area that the demand monitoring control apparatus monitors the entrance / exit status for each area (section) in cooperation with the entrance / exit management system. It is described that the operation of unmanned area is stopped while the operation of the air conditioning and lighting is maintained, and the operation of the unmanned area is stopped to suppress the wasteful power consumption.

JP 2002-49671 A JP 2011-0104097 A

In the technique disclosed in Patent Document 1 above, since it is necessary to input usage conditions such as the number of users of the device, it is necessary for the user (system user) to grasp the usage status of the device in advance. There was a problem. In addition, the user needs to determine which area of the device should be preferentially replaced.
In addition, in the technology disclosed in Patent Document 2, the presence / absence of a person and the number of people in each area are detected in real time, and a region where a person is present and a region where no person is present is detected in the area, thereby finely controlling power. Techniques for performing are disclosed. However, no consideration is given to providing information for calculating energy saving proposals based on the history.
An object of the present invention is to solve the above problems and to realize an entrance / exit management system capable of calculating an area with high energy saving effect and providing information when energy saving measures are implemented.

In order to solve the above problems, the entrance / exit management system of the present invention is connected to a card reader provided in each of a plurality of management areas, and the date and time when the card reader reads the card, the card reader number, and the card read An entry / exit control device that acquires a pass history information including a card ID and entry / exit event information, a pass history table that stores pass history information sent from a plurality of the entrance / exit control devices, and the pass history Based on the table, a staying time table for obtaining the staying time of the management area for each time zone of the predetermined management area for each card ID and obtaining the sum of the staying times of all the card IDs for each time zone of the predetermined management area And having a DB server.
The present invention is also a control method for an entrance / exit management system in which a card reader is provided in each of a plurality of management areas, and when the card reader reads a card, the read date and time and the card reader number are read. A step of acquiring traffic history information including a card ID of the card and event information of entering or leaving the room, a step of adding a building number and an entrance / exit control device number to the traffic history information and storing in the traffic history table; A step of searching for a card reader related to the management area from the traffic history table with reference to a management area definition table classified by a building number, an entrance / exit control device number, and a card reader number; A search for a card ID to be performed, and a staying time for each time zone from the traffic history of the searched card ID A step of calculating,
A step of calculating the total stay time of the area by adding the stay time of the card ID for each management area number is included.

According to the present invention, since the stay time is calculated from the entrance / exit time detected by the ID card, the total stay time of the area can be obtained with high accuracy, and the accuracy of the prediction effect of the energy saving effect can be improved. .
Further, since history information at the time of reading the ID card is accumulated, the amount of information can be reduced, and the use efficiency of the DB storage device can be improved.

It is a schematic block diagram which shows the entrance / exit management system of an Example. It is a figure which shows the structure of the card ID information of an Example. It is a figure which shows the structure of the traffic permission information of an Example. It is a figure which shows the structure of the traffic history information of an Example. It is a figure which shows the structure of the traffic history table of an Example. It is a figure which shows the structure of the area table of an Example. It is a figure which shows the structure of the stay time table of an Example. It is a flowchart which shows the generation | occurrence | production event determination process of the traffic history information of the entrance / exit control apparatus of an Example. It is a flowchart which shows the residence time calculation process of the designated area of the application server of an Example, a designated time slot | zone, and designated card ID. It is a flowchart which shows the designation | designated card ID presence status acquisition process at the time of designation | designated date in the area comprised with the designated card reader of an Example. It is a flowchart which shows the process which calculates the stay time of designation | designated card ID of an Example from related traffic history, occupancy status, and a total time zone.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings.
(System configuration)
FIG. 1 is a configuration diagram illustrating an entrance / exit management system according to an embodiment of the present invention. This entrance / exit management system includes an entrance / exit control device 20 installed in the customer building 10 and a center 60. A plurality of entrance / exit control devices 20 may be installed.

The entrance / exit control device 20 installed in the customer building 10 is connected to the center 60 via the Internet 50. In addition to the entrance / exit control device 20, the customer building 10 has a customer information processing terminal 40.
The customer building 10 includes a card reader 31 that is an entrance / exit facility of the building and an electric lock 32 for the door. The entrance / exit control device 20 is connected to a card reader 31 that is an entrance / exit facility and an electric lock 32 via an external input / output interface 26 described later.

The card reader 31 is a reader device for reading card information of an IC card held by a person who enters and exits the customer building 10.
The electric lock 32 is a lock installed for each door of the management section of the customer building 10. The electric lock 32 unlocks and locks the lock according to the unlock command and the lock command from the entrance / exit control device 20.
The entrance / exit control device 20 includes a processing unit 21, a storage unit 22, an external input / output interface 26, and a network interface 27.

An external input / output interface 26, a network interface 27, and a storage unit 22 are connected to the processing unit 21. The storage unit 22 includes card ID information 23 indicating the area type of the card that can be passed, passage permission information 24 that associates the passable area type with the card reader, and operation information notified from the card reader 31. Some traffic history information 25 is stored. The processing unit 21 is equipped with a processor and controls the operation of the entrance / exit control device 20 by executing a control program (not shown) stored in the storage unit 22.
A card reader 31 and an electric lock 32 are connected to the external input / output interface 26. The external input / output interface 26 notifies the processing unit 21 of information output from the card reader 31 and the electric lock 32. The external input / output interface 26 further inputs information notified from the processing unit 21 to the card reader 31 and the electric lock 32.
The network interface 27 is an interface that inputs and outputs Ethernet (registered trademark) signals, for example. The network interface 27 connects the processing unit 21 to the Internet 50.

The customer building 10 includes a customer information processing terminal 40 that is a computer having an information processing function and a display function. The customer information processing terminal 40 browses and changes information managed by the center 60. Further, the customer information processing terminal 40 transmits control information for remotely controlling the card reader 31 and the electric lock 32 to the center 60.
In the present embodiment, a customer information processing terminal 40 is provided in the customer building 10. However, the present invention is not limited thereto, and a computer installed in a building different from the customer building 10 may be used as the customer information processing terminal 40.

The center 60 has an application server 61 and a DB (DataBase) server 62. The application server 61 and the DB server 62 are connected to each other.
The application server 61 is connected to the entrance / exit control device 20 and the customer information processing terminal 40 via the Internet 50.
The DB server 62 includes a travel history table 63, a staying time table 65, and an area table 64, which is area definition information. The application server 61 can read and write information stored in the DB server 62 by transmitting an instruction command conforming to the SQL language to the DB server 62.
In the present embodiment, the center 60 includes an application server 61 that is a processing unit and a DB server 62 that is a storage unit. However, the present invention is not limited to this, and a single server may serve as both the processing unit and the storage unit.

FIG. 2 is a diagram showing a configuration of the card ID information 23 in the present embodiment. The card ID information 23 includes an item of a card number 23a, an item of a card ID 23b, and an item of a passage permission number 23c, and defines a correspondence between management sections that can pass through the card.
In the item of the card number 23a, a unique number assigned for each card and uniquely specifying the record of the card ID information is stored.
The item of card ID 23b stores unique authentication information held by the IC card.
In the item of the passage permission number 23c, a unique number for uniquely specifying the relevance with a record of the passage permission information described later is stored.

FIG. 3 is a diagram showing a configuration of the passage permission information 24 in the present embodiment. The passage permission information 24 includes an item of a passage permission number 24a and an item of a passage permission card reader number 24b.
In the item of the passage permission number 24a, a unique number for uniquely identifying the record of the passage permission information is stored.
In the item of the permitted card reader number 24b, a list of numbers of the card readers permitted to pass is stored for the card ID holding the permitted traffic number. Since the card reader is installed for each management section, it is possible to define an accessible area according to the card pass permission number.

FIG. 4 is a diagram showing a configuration of the traffic history information 25 in the present embodiment. Although details will be described later, when the card reader 31 reads, the contents of the operation event are notified to the processing unit 21 and recorded in the traffic history information 25. The traffic history information 25 includes an item of sequence number 25a, an item of occurrence date and time 25b, an item of card reader number 25c, an item of occurrence event 25d, and a target card number 25e.
In the item of the sequence number 25a, unique number information for uniquely specifying the record of the history information is stored.
The date and time of occurrence of the history information is stored in the occurrence date and time 25b item.
The card reader number 25c item stores the number of the card reader in which the history information has been generated.
In the item of the occurrence event 25d, information indicating specific contents related to the record of the history information is stored. “Entering” and “Leaving” are cases where the door is opened and closed after authentication, and a person enters and exits. “No entry” and “Not leaving” indicate that the door is not opened and closed after authentication. This means that there was no entry or exit.
In the item of the target card number 25e, a unique number (card number 23a in FIG. 2) that uniquely specifies the association between the card ID of the card that has generated the history information and the traffic permission number information is stored. .

FIG. 5 is a diagram showing the configuration of the traffic history table 63 in the present embodiment. In the traffic history table 63, the contents of the traffic history information 25 of the entrance / exit control device 20 are notified to the application server 61 and recorded in the DB server 62. The traffic history table 63 includes an occurrence date / time 63a item, a building number 63b item, an entry / exit control device number 63c item, a card reader number 63d item, an occurrence event 63e item, and a target card ID 63f item. And have.
The date and time of occurrence of the history information is stored in the occurrence date and time 63a item.
The item of the building number 63b stores a unique number that uniquely identifies the building in which the history information has occurred.
In the entry / exit control device number 63c item, a unique number for uniquely identifying the entrance / exit control device in which the history information has been generated is stored.
The card reader number 63d item stores the number of the card reader in which the history information has been generated.
In the item of the occurrence event 63e, information indicating specific contents related to the operation in which the history information has occurred is stored.
The item of target card ID 63f stores the card ID that generated the history information.

FIG. 6 is a diagram showing the configuration of the area table 64 in the present embodiment. The area table 64 has an item of the building number 64a, an entry / exit control device number 64b, an item of the card reader number 64c, and an item of the area number 64d.
The area table shows the area where the card reader is installed for the card reader uniquely identified by the item of the building number 64a, the entry / exit control device number 64b, and the item of the card reader number 64c. Specify in the item.
The item of the building number 64a is a number for uniquely specifying the building where the card reader specified by the item of the card reader number 64c is installed.
The entry / exit control device number 64b item is a number for uniquely specifying the entrance / exit control device 20 that controls the card reader specified by the card reader number 64c item.
The item of the card reader number 64c is a number for uniquely identifying the card reader. All items managed by the DB server 62 using the building number 64a, the entrance / exit control device number 64b, and the card reader number 64c are used. The card reader can be uniquely identified from the card readers.
The item of the area number 64d is a number for designating the area where the card reader is installed, designated by the building number 64a, the entrance / exit control device number 64b, and the card reader number 64c.

  FIG. 7 is a diagram showing a configuration of the stay time table 65 in the present embodiment. The stay time table 65 includes an item of date 65a, an item of time zone 65b, an item of building number 65c, an item of area number 65d, and an item of total stay time 65e. The staying time table 65 indicates how many people have stayed in the area specified by the building number 65c and the area number 65d in the time zone determined by the item of the date 65a and the item of the time zone 65b. The information to be represented is stored in the item of the total stay time 65e. In the item of the total stay time 65e, a value calculated by “number of stayers (number of tag IDs) × number of stay seconds” is stored. The detailed procedure of calculation will be described later.

(Operation of the embodiment)
Based on FIG. 1, the operation of the entry / exit processing of the entry / exit management system will be described. It is assumed that an IC card for entering and leaving the room is distributed in advance to the person entering and exiting the customer building 10.
First, the operation when entering the room will be described. When an attendee holds the IC card for entering and leaving the room over the card reader 31, the card ID is read by the card reader 31, and the card ID is transmitted from the card reader 31 to the entrance / exit control device 20. The entrance / exit control device 20 performs a card ID authentication process for determining whether the received card ID is permitted to pass through the area. When the received card ID is permitted to pass, an unlocking command is transmitted from the entrance / exit control device 20 to the electric lock 32. When the electric lock 32 receives the unlock command, the electric lock 32 is unlocked and the person holding the IC card can pass.

Next, an outline of the card ID authentication process will be described.
When the entry / exit control device 20 receives the card ID, the following card ID authentication process is performed to determine whether or not the vehicle can pass.
First, the processing unit 21 determines whether or not the received card ID is registered in the card ID information 23 of the storage unit 22. The determination of registration is based on, for example, sequentially comparing the value of the item of the card ID 23b in FIG. 2 with the card ID.

  When the card ID is registered in the card ID information 23, the passage permission number 23c corresponding to the card ID is acquired from the card ID information 23. Thereafter, the passage permission information 24 in the storage unit 22 is searched using the obtained passage permission number 23c as a key, and the value of the passage permission card reader number 24b corresponding to the matching passage permission number 24a is obtained. If the acquired card reader number 24b includes a card reader number indicating the card reader 31 that transmitted the card ID, it is determined that the received card ID is permitted to pass.

After performing the card ID authentication process, the entrance / exit control device 20 creates a traffic history according to the authentication result, and stores the created history information in the traffic history information 25 of the storage unit 22. The traffic history is created as follows.
In the sequence number 25a, a value obtained by adding one to the sequence number of the traffic history stored last among the records already stored in the traffic history information 25 is stored. The occurrence date and time 25b stores the date and time when information to be stored in a later-described occurrence event 25d is confirmed. The card reader number 25c stores a number indicating the card reader 31 that has transmitted the card ID. The occurrence event 25d stores information determined by the process shown in FIG. The target card number 25e is a card number associated with the card ID subjected to the card ID authentication process, and stores the value of the card number 23a searched based on the card ID in the card ID information 23. In this way, each time the card ID is authenticated, one traffic history information is created (corresponding to one line of the traffic history information 25).

FIG. 8 is a flowchart showing processing for determining information to be stored in the event 25d of the above-described traffic history information 25.
When the process is started, in step S10, it is determined whether the card reader 31 that has transmitted the card ID is installed on the entry side or the exit side of the electric lock 32. If the card reader 31 is installed on the entry side of the electric lock 32, the process of step S11 is performed. If the card reader 31 is installed on the exit side of the electric lock 32, the processing after step S15 is performed.

In step S <b> 11, the entrance / exit control device 20 determines whether a door open signal indicating a state where the door of the electric lock 32 is open is detected. If a door open signal is detected (Yes), the process of step S13 is performed. If the door open signal is not detected (No), the process of step S12 is performed.
In step S12, the entrance / exit control device 20 determines whether or not a certain time has elapsed since the card ID authentication process was performed. If the predetermined time has elapsed (Yes), the process of step S14 is performed. If the predetermined time has not elapsed (No), the process of step S11 is performed.
In step S13, the information to be stored in the occurrence event 25d of the traffic history information 25 is determined to be “room entry”. When the process of step S13 ends, the process of FIG. 8 ends.

  In step S14, the information stored in the occurrence event 25d of the traffic history information 25 is determined as “not entered”. When the process of step S14 ends, the process of FIG. 8 ends.

In step S15, the entrance / exit control device 20 determines whether or not a door open signal indicating a state in which the door of the electric lock 32 is open is detected. If a door open signal is detected (Yes), the process of step S17 is performed. If the door open signal is not detected (No), the process of step S16 is performed.
In step S <b> 16, the entrance / exit control device 20 determines whether or not a certain time has elapsed since the card ID authentication process was performed. If the predetermined time has elapsed (Yes), the process of step S18 is performed. If the predetermined time has not elapsed (No), the process of step S15 is performed.

In step S <b> 17, the information to be stored in the occurrence event 25 d of the traffic history information 25 is determined as “leaving room”. When the process of step S17 ends, the process of FIG. 8 ends.
In step S18, the information stored in the occurrence event 25d of the traffic history information 25 is determined to be “unleashed”. When the process of step S18 ends, the process of FIG. 8 ends.

  The entrance / exit control device 20 transmits the created traffic history information 25 to the center 60 via the Internet 50. When the traffic history information 25 is transmitted, the target card number 25e of the traffic history information 25 is converted into a card ID based on the card ID information 23 and then transmitted. Further, when the traffic history information 25 is transmitted, the building number and the entrance / exit control device number preset in the entrance / exit control device 20 are added to the transmission data and then transmitted.

When the application server 61 of the center 60 receives the traffic history information 25 from the entrance / exit control device 20, it stores it in the traffic history table 63 of the DB server 62.
Here, transmission of the passage history information 25 by the entrance / exit control device 20 may be performed immediately after the entrance / exit control device 20 creates the passage history, or may be transmitted at regular intervals by the entrance / exit control device 20. Alternatively, it may be transmitted in accordance with a request from the center 60.

The application server 61 calculates the staying time in the specific area in the specific area for each card ID by the process shown in FIG. 9 described later. A value obtained by adding the calculated stay times in the specified time zone in the specified area for all card IDs is stored in the total stay time 65e of the stay time table 65 as a total stay time. For example, there are 24 specific time zones from midnight (0: 0: 0 to 0:59:59) to 23:00 (23:00:00 to 23:59:59) For each, the total stay time is calculated.
In addition, the total stay time may be totaled for a predetermined number of days, such as “totaling the previous day once a day”, or the application server 61 may receive the information from the customer information processing terminal 40. It may be performed when a request for aggregation is received.

FIG. 9 shows a stay time calculation process for the designated card ID in the designated area / designated time zone by the application server 61.
When the process is started, the stay time variable is initialized in step S20.
Next, in step S21, an associated card reader associated with the designated area is searched using the “building number”, “entrance / exit control device number”, and “area number” associated with the area designated from the area table 64 as search conditions. Search for. No related card reader may be acquired, and a plurality of related card readers may be acquired.

  In step S22, it is determined whether there is one or more related card readers searched in step S21. If one or more related card readers are found (Yes), the process of step S23 is performed. If no related card reader is searched (No), the value of the stay time variable is output as the calculation result, and the process of FIG. 9 is terminated.

In step S23, the search conditions include the “total time zone (occurrence date and time)”, the “building number”, the “entrance / exit control device number”, and the “card reader number of the related card reader” designated from the traffic history table 63. In addition, the related traffic history related to the designated area and the designated card ID is searched.
In step S24, the specified time zone of the specified card ID in the specified area from the start time of the specified time zone, the specified card ID, and the related card reader acquired in step S21 by the process shown in FIG. Acquires the occupancy status (in / out) at the start time.

In step S25, the stay time of the specified card ID is calculated from the related traffic history acquired in step S23, the occupancy status calculated in step S24, and the specified time zone by the process shown in FIG.
In step S26, the stay time calculated in step S25 is stored in the stay time variable, and the process of FIG. 9 is terminated.
With the above-described processing, the application server 61 calculates the stay time table 65 by storing, in the total stay time 65e, a value obtained by adding the stay time of the specific time zone in the specific area for all card IDs.

FIG. 10 shows processing for acquiring the occupancy status of the designated card ID at the designated date and time in the area configured by the designated card reader in step S24 of FIG.
When the process is started, in step S30, the traffic history is searched from the traffic history table 63 under the following search condition. The search condition is the same as any one of “the occurrence date and time is before the designated date and time”, “the target card ID is the same as the designated card ID”, and “the card reader number designated by the card reader number”. That's it.

  In step S31, it is determined whether there is one or more traffic histories searched in step S30. If one or more traffic histories have been searched (Yes), the process of step S32 is performed. If one or more traffic histories have not been searched (No), the process of step S35 is performed. In step S32, one traffic history with the latest occurrence date / time is acquired from the traffic histories searched in step S30.

In step S33, it is determined whether or not the occurrence event item of the traffic history record acquired in step S32 corresponds to either “entering room” or “not leaving room”. If the generated event item corresponds to either “entering room” or “not leaving room”, the process of step S34 is performed. If the generated event item does not correspond to either “entering room” or “not leaving room”, that is, corresponds to either “leaving room” or “not entering room”, the process of step S35 is performed.
In step S34, the occupancy status is regarded as “occupied”, and the process of FIG.
In step S35, the occupancy status is regarded as “absent”, and the processing of FIG.

FIG. 11 shows processing for calculating the stay time of the designated card ID in step S25 of FIG.
When the process is started, in step S40, it is determined whether or not the occupancy status acquired in step S24 is “in-room”. If the occupancy status is “occupied”, the process of step S41 is performed. If the occupancy status is “absent”, the process of step S42 is performed.
In step S41, 1 is stored in the occupancy flag which is a variable representing the occupancy status.
In step S42, 0 is stored in the presence flag.
In step S43, the start time of the designated time zone is stored in the room entry time variable which is a variable representing the room entry time.

  In step S44, the designated related traffic history is sorted in ascending order by date and time of occurrence. The related traffic history is a data table of a storage unit (not shown) of the application server, and as described above, “date and time of occurrence of specified time zone” and “building associated with the specified area” from the traffic history table 63. “Number”, “Entry / exit control device number associated with the specified area”, “Card reader number of related card reader”, and “Specified card ID” are searched for the specified area and the specified card ID. Related traffic history.

Next, the processing from step S45 to step S55 is repeated until the condition “until the related traffic history disappears” is satisfied.
Specifically, in step S45, it is determined whether there is an nth item of the related traffic history sorted in step S44 in the nth iteration of the iterative process from step S45 to step S55. If there is an nth related traffic history, the process of step S46 is performed to perform the nth repetitive process. If there is no nth related traffic history, the iterative process is terminated and the process of step S56 is performed. Note that n is a natural number starting from 1.

In step S46, the n-th related traffic history of the related traffic history sorted in step S44 is acquired.
In step S47, it is determined whether or not the occupancy flag is 1. If the occupancy flag is 1, the process of step S49 is performed. If the presence flag is not 1, the process of step S48 is performed.

  In step S48, it is determined whether or not the occurrence event item of the nth related traffic history acquired in step S46 corresponds to either “entering room” or “not leaving room”. If the generated event item corresponds to either “entering room” or “not leaving room”, the process of step S51 is performed. If the generated event item does not correspond to either “entering room” or “not leaving room”, that is, corresponds to either “leaving room” or “not entering room”, the process of step S55 is performed.

In step S49, it is determined whether or not the occurrence event item of the n-th related traffic history acquired in step S46 corresponds to either “leaving” or “not entering”. If the generated event item corresponds to either “leaving” or “not entering”, the process of step S53 is performed. If the generated event item does not correspond to either “leaving” or “not entering”, that is, if it corresponds to either “entering” or “not leaving”, the process of step S50 is performed.
In step S50, the value of the occurrence date / time item of the nth related traffic history acquired in step S46 is stored in the room entry time variable, and the process proceeds to step S55.

In step S51, 1 is stored in the presence flag.
In step S52, the value of the occurrence date / time item of the nth related traffic history acquired in step S46 is stored in the room entry time variable, and the process proceeds to step S55.

In step S53, the n-th related passage history acquired in step S46 from the date and time stored in the entry time variable is stored in the stay time variable for storing the stay time output as the calculation result when the processing in FIG. 11 is completed. The difference between the time until the occurrence date and time is added to the value stored in the stay time variable and then stored.
In step S54, 0 is stored in the presence flag, and the process proceeds to step S55.
In step S55, the n-th repetition is ended, and the process of step S45 is performed.

In step S56, it is determined whether the presence flag is 1. If the occupancy flag is 1, the process of step S57 is performed. If the occupancy flag is not 1, the value stored in the stay time variable is output as the calculation result, and the process of FIG. 11 is terminated.
In step S57, the difference in time from the date and time stored in the room entry time variable to the end time of the specified time zone is added to the value stored in the stay time variable and stored in the stay time variable. When the process of step S57 ends, the value stored in the stay time variable is output as the calculation result, and the process of FIG. 11 ends.

  The application server 61 calculates the stay time table 65 of the DB server 62 by performing the above-described processing for a predetermined building number and area number.

Next, an example of a program that refers to the stay time table 65 will be described.
The application server 61 proposes an “energy saving effective area” that is an area that is highly effective for energy saving measures in accordance with a request from the customer information processing terminal 40. In calculating the energy saving effective area, the customer information processing terminal 40 designates the time / time zone to be calculated. The application server 61 acquires the value of the total stay time 65e of the stay time table 65 of the DB server 62 for the calculation target time / time zone specified from the customer information processing terminal 40, and adds the values for each area. A certain “total area stay time” is calculated. An area having a large total area stay time in the calculation target period / time zone is transmitted to the customer information processing terminal 40 as an energy saving effective area. The area where the total area staying time is large means that people are crowded and can be considered as an energy saving effective area because it can be estimated that energy consumption is high.

  Further, when calculating the energy saving effective area, the “unit area total stay time” that is a value obtained by dividing the total area stay time by the total floor area of each area may be calculated. The total unit area stay time represents the density of people per unit area, and the density of people who are not affected by the size of each area can be calculated. When the DB server 62 has the total floor area for each area, an item of the total floor area 64e may be added to the area table 64.

DESCRIPTION OF SYMBOLS 20 Entrance / exit control apparatus 21 Processing part 22 Storage part, 23 Card ID information, 24 Traffic permission information, 25 Traffic history information 26 External input / output interface 27 Network interface 31 Card reader 32 Electric lock 40 Customer information processing terminal 50 Internet 60 Center 61 Application server 62 DB server 63 Traffic history table 64 Area table 65 Stay time table

Claims (5)

Passage history information including card readers connected to each of a plurality of management areas, the card reader reading date and time, the card reader number, the card ID of the read card, and entry / exit event information An entrance / exit control device to obtain
Based on the traffic history table that accumulates traffic history information sent from a plurality of the entrance / exit control devices and the traffic history table, the stay time of the management area for each time zone of the predetermined management area is obtained for each card ID. A DB server having a stay time table that calculates a sum of stay times of card IDs for each time zone of the predetermined management area;
An entrance / exit management system characterized by comprising: In the entrance / exit management system of Claim 1,
The DB server has a management area definition table classified by a building number, an entrance / exit control device number, and a card reader number,
The entrance / exit control device gives the building number and the entrance / exit control device number to notify the DB server of the traffic history information,
The DB server accumulates the building number, the entrance / exit control device number and the traffic history information notified from the entrance / exit control device to form a traffic history table, and the stay calculated from the definition table and the traffic history table An entrance / exit management system, wherein time is recorded in the stay time table. In the entrance / exit management system of Claim 1 or Claim 2,
A card reader related to an area number is searched from the traffic history table, a card ID related to the card reader is searched, a stay time for each time zone is calculated from the traffic history of the searched card ID, and each area number is calculated. An entry / exit management system comprising an application server that calculates the total area stay time by adding the stay time of the card ID to A control method of an entrance / exit management system in which a card reader is provided in each of a plurality of management areas,
When the card reader reads the card, obtaining the travel history information including the read date and time, the card reader number, the card ID of the read card, and the event information of entering or leaving the room;
Adding a building number and an entrance / exit control device number to the traffic history information and storing them in the traffic history table;
Searching for a card reader related to the management area from the traffic history table with reference to a management area definition table classified by building number, entrance / exit control device number, and card reader number;
Searching for a card ID associated with the card reader;
Calculating the staying time for each time zone from the traffic history of the searched card ID;
A control method for an entrance / exit management system, comprising: calculating a total area stay time by adding a stay time of a card ID for each management area number. In the control method of the entrance / exit management system of Claim 4,
A method for controlling an entrance / exit management system, comprising the step of dividing the total area stay time by the total floor area of each area to calculate the unit area total stay time.

Images