Security system design device, security system design method, and security system design program

Abstract

To provide a security system design device, method, and program for designing an appropriate security system capable of allowing even an unskilled technician to obtain a sufficient security effect when constructing a security system in a security object facility.SOLUTION: A security system design device 1 comprises: an operation section 104 through which a target position is set with respect to room layout data received via an image reader 2; a list data conversion section 121 for generating a node list and an edge list based on the room layout data; a graph data generation section 122 for generating graph data based on the node list and the edge list; a sensor arrangement processing section 123 for setting types and installation positions of security units with respect to the graph data; a graph evaluation section 124 for obtaining a total value of scores of the security units which are set from a target node to nodes of respective terminal ends; and a result output section 125 through which an evaluation result including the total value is output.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] This invention relates to an apparatus, method, and program used when designing a security system (mechanical security system) that uses security machines such as passive sensors and magnetic switches for facilities to be secured, such as office buildings and stores. [Background technology]

[0002] Security systems using passive sensors and magnetic switches are being installed in office buildings, stores, and other facilities to protect against intrusions by suspicious individuals without relying on human intervention during unattended times, such as at night or on holidays. Passive sensors detect intrusions by receiving infrared light emitted from the surface of the human body, and are also called motion sensors. Magnetic switches attach a magnet to the movable part of a window or door and a switch to the frame to detect when the window or door is opened. Security systems connect passive sensors and magnetic switches placed in various locations throughout the facility to the security device itself, and when an intruder is detected through the passive sensors or magnetic switches, an alarm sounds or a security company is notified.

[0003] When building a security system for a facility to be secured, it is necessary to appropriately decide where and what kind of sensors and other security equipment to install, taking into consideration the layout of the facility to be secured and the user's (client's) budget, etc. Traditionally, skilled engineers have taken into consideration the layout and budget of the facility to be secured and decided where and what type of security equipment to install to ensure sufficient security. However, building an appropriate security system inevitably requires the experience and knowledge of skilled engineers.

[0004] For this reason, as disclosed in Patent Document 1 described below, an invention has been made relating to a security diagnosis method and device that enables even non-experts to easily obtain security diagnosis information for constructing an electronic security system. The invention disclosed in Patent Document 1 includes a memory unit for inputting and storing facility data, security device data, and surveillance target data. A behavior trajectory data creation means creates behavior trajectory data of the intruder by simulating the behavior of the intruder if he or she enters the facility based on the facility data and the surveillance target data. An installation data creation means creates placement data for the security devices to be installed within the facility based on the created behavior trajectory data and security device data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 7-334779 Summary of the Invention [Problem to be solved by the invention]

[0006] In the case of the invention disclosed in Patent Document 1, if an intruder enters a facility, the behavior of the intruder is simulated based on facility data and data on the object of surveillance, and behavioral trajectory data of the intruder is created. However, the specific method of the simulation is not disclosed. Furthermore, while location data for security devices to be installed in the facility is created from the created behavioral trajectory data and security device data, the specific algorithm for creating the location data is not disclosed. The method for simulating the intruder's behavior and the algorithm for creating the location data for security devices are parts that only an expert can create. The invention disclosed in Patent Document 1, which does not clearly and in detail disclose these parts, makes it impossible for an unskilled person to build an appropriate security system for the facility to be guarded.

[0007] In view of the above, the object of the present invention is to enable even non-expert engineers to design an appropriate security system that can provide sufficient security effects when constructing a security system for a facility to be guarded. [Means for solving the problem]

[0008] In order to solve the above problem, the security system design device of the invention described in claim 1 is: a receiving means for receiving input of floor plan data of a facility to be secured; a setting means for setting a target position for the floor plan data in response to an instruction input; a node list conversion means for creating a node list based on the floor plan data, in which the target location is defined as a target node, areas inside and outside the facility to be guarded are defined as nodes, and necessary information is associated with each of the nodes; an edge list conversion means for creating an edge list in which, when a means for enabling people to move between adjacent nodes is provided based on the floor plan data and the node list, the means is used as an edge and necessary information is associated with adjacent nodes for each edge; a generating means for generating graph data from a target node based on the node list and the edge list; a placement processing means for setting the types and locations of security machines to be placed in accordance with predetermined criteria for the graph data; evaluation means for calculating a total score of the security machines set from the target node to each terminal node based on a predetermined score for the security machine; an output means for outputting an evaluation result including the total value calculated by the evaluation means; The present invention is characterized by comprising:

[0009] According to the security system design device of claim 1, the setting means sets a target position for floor plan data received through the receiving means. The node list conversion means identifies nodes inside and outside the facility to be guarded based on the floor plan data and creates a node list. The edge list conversion means identifies edges based on the floor plan data and the node list and creates an edge list. The generation means creates graph data based on the node list and edge list. The placement processing means sets the type and placement location of security equipment to be placed for the graph data. The evaluation means calculates a total score for the security machines set from the target node to each terminal node, and an evaluation result including this total score is output through the output means. [Effects of the Invention]

[0010] According to this invention, even if one is not an experienced engineer, it is possible to design an appropriate security system that can provide sufficient security effects depending on the facility to be guarded. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a block diagram illustrating a configuration example of a security system design device according to an embodiment. [Figure 2] FIG. 1 is a diagram for explaining an example of a floor plan. [Figure 3] FIG. 10 is a diagram for explaining nodes and edges identified for a security target facility. [Figure 4] 10A and 10B are diagrams illustrating an example of a node list and an example of an edge list. [Figure 5] FIG. 10 is a diagram illustrating an example of basic graph data. [Figure 6] FIG. 10 is a diagram showing an image of a graph created from basic graph data. [Figure 7] FIG. 10 is a diagram for explaining an example of sensor arrangement graph data. [Figure 8] FIG. 10 is a diagram for explaining an example of a security machine installation criteria list. [Figure 9] FIG. 10 is a diagram illustrating an example of sensor data. [Figure 10] FIG. 10 is a diagram for explaining an example of evaluation graph data. [Figure 11] FIG. 10 is a diagram showing a graph image created from evaluation graph data. [Figure 12] FIG. 10 is a diagram for explaining a change in evaluation graph data. [Figure 13] 10 is a diagram for explaining the placement of passive sensors and magnetic switches, which are security devices, at a facility to be guarded according to the evaluation graph data after the change. FIG. [Figure 14] 10 is a flowchart illustrating processing performed by the security system design device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, with reference to the drawings, an embodiment of the device, method, and program according to the present invention will be described. This invention can be used when designing a security system for various facilities such as offices, stores, schools, factories, and ordinary homes. However, for simplicity, the following embodiment will be described using an example in which a security system is designed for an office as the facility to be secured.

[0013] [Configuration example of security system design device 1] FIG. 1 is a block diagram illustrating an example of the configuration of a security system design device (hereinafter referred to as the design device) 1 according to an embodiment. A connection terminal 101T constitutes a connection terminal to an IP network. A communication I / F (Interface) 101 converts data sent to the device via the IP network into data in a format that can be processed by the device and imports the data. The communication I / F 101 also converts data to be sent from the device into a format for transmission and transmits the data to the intended recipient via the IP network. Therefore, communication with a server device or the like connected to the IP network is performed via the connection terminal 101T and the communication I / F 101. The IP network refers to a computer network interconnected using Internet Protocol Suite technology, and is equivalent to the so-called "Internet."

[0014] Although not shown, the control unit 102 is a microprocessor configured by connecting a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and non-volatile memory via a bus, and realizes the function of controlling each unit of the design device 1. The storage device 103 is a device unit configured by a recording medium such as an SSD (Solid State Drive) and its driver, and performs operations such as recording various data to the recording medium, reading, changing, and deleting data recorded on the recording medium. The storage device 103 stores and holds necessary data and programs, and is also used as a work area for temporarily storing intermediate data generated in various processes. In this embodiment, the storage device 103 pre-stores information such as a parameter list, a security machine installation standard list, and sensor data, which will be described later.

[0015] The operation unit 104 receives user input, converts it into an electrical signal, and supplies it to the control unit 102. Specifically, the operation unit 104 includes a keyboard and a mouse (pointing device). The control unit 102 controls each component in response to the user input received through the operation unit 104, enabling the control unit 102 to execute the desired process. The connection terminal 105T serves as a connection terminal for connecting to an external device, and the external I / F (interface) 105 enables data transmission and reception between the external device and the connection terminal 105T. In this embodiment, as shown in FIG. 1, an image reader 2 is connected via the connection terminal 105T and the external I / F 105, enabling image data (image data) to be imported through the image reader 2. External devices, such as a printer, can also be connected to the design apparatus 1 via a connection terminal and external I / F (not shown).

[0016] Display controller 106 performs processing to display various pieces of display information on display 107 under the control of control unit 102. Display 107 is, for example, a display element such as an LCD (Liquid Crystal Display) or an organic EL display, and is provided with a display screen with a screen size of, for example, approximately 14 to 21 inches. Display 107 displays various pieces of display information on the display screen in accordance with the control of display controller 106. Each of files 111 to 115 is a storage unit that stores and holds various pieces of data, and may be formed in different storage areas on the storage medium of a single storage device, such as an SSD, or may be formed on the recording media of different storage devices. Alternatively, files 111 to 115 may be formed in a distributed manner on the recording media of multiple storage devices.

[0017] The floor plan data file 111 stores and holds floor plan data that forms a floor plan of the security facility. The input list file 112 stores and holds node lists and edge lists that are formed based on the floor plan data, etc. Note that, as will be described in detail later, nodes are rooms, which are areas separated by walls inside the security facility, and areas (outdoor areas) outside the security facility that are adjacent to the areas (rooms) inside the security facility and connected to the areas by edges. Furthermore, edges refer to the connections between areas, and more specifically, to doors and windows that connect nodes to each other.

[0018] The basic graph data file 113 stores and holds basic graph data formed based on the node list and edge list of the input list file 112. The basic graph data is information showing the movement route of an intruder in a guarded facility. The sensor placement graph data file 114 stores and holds sensor placement graph data formed based on the basic graph data file 113, etc. The evaluation graph data file 115 stores and holds evaluation graph data formed based on the sensor placement graph data of the sensor placement graph data file 114, etc. Details of the data stored in each of these files 111 to 115 will be described later.

[0019] The list data conversion unit 121 performs processing to form a node list and an edge list based on the floor plan data in the floor plan data file 111 and a parameter list prepared in advance in the storage device 103, and to store these in the input list file 112. The graph data generation unit 122, as will be described in detail later, generates graph data extending from a target node through nodes and edges to each terminal node, based on the node list and edge list stored in the input list file 112. The graph data generation unit 122 stores the generated graph data in the basic graph data file 113.

[0020] The sensor placement processing unit 123 sets the types and placement positions of security machines to be placed for the basic graph data stored in the basic graph data file 113, for example, in accordance with a security machine installation standard list (described later) that is prepared in advance in the storage device 103. Specifically, the sensor placement processing unit 123 performs processing to set which nodes and edges of the basic graph data will have passive sensors and magnetic switches placed on them. The sensor placement processing unit 123 stores the sensor placement graph data obtained as a result of this setting processing in the sensor placement graph data file 114.

[0021] The graph evaluation unit 124 uses the sensor location graph data in the sensor location graph data file 114 to calculate the total score of the security machines set up from the start node to each terminal node, based on predetermined scores for the security machines to be placed. Specifically, the graph evaluation unit 124 determines, for the sensor location graph data, where the security machines are set up and what their scores are, and calculates the total score of the security machines set up from the start node to each terminal node. The graph evaluation unit 124 forms evaluation graph data that indicates where the security machines are set up and what their scores are, as well as the total score of the security machines on each route, and stores this in the evaluation graph data file 115.

[0022] The result output unit 125 forms evaluation result information for output based on the evaluation graph data in the evaluation graph data file 115, and performs processing to display it on the display 107 via the display controller 106 or print it out via a printer (not shown). A user of the design device 1 refers to the displayed or printed evaluation result information and identifies routes from the target node to each terminal node whose total score value is lower than a predetermined value and routes whose total score value is higher than a predetermined value. The total score value of the security machines that are to be installed for each route will be referred to as the security score hereinafter.

[0023] The user may select a route with a security score lower than a predetermined minimum value. security machine High score security machine Or, security machine In addition, for routes with a security score higher than a predetermined maximum value, security machine A low score security machine Or, security machine The security score is set to be equal to or less than the maximum value by deleting the security score. This makes it possible for even non-expert engineers to design a security system that can properly perform machine security. The processing performed by the design device 1 of this embodiment will now be specifically described.

[0024] [Floor plan example] When designing a security system using the design device 1 shown in FIG. 1, it is first necessary to grasp the configuration of the facility to be secured using the design device 1. The configuration of the facility to be secured is not limited to the internal configuration, but must also be able to grasp all possible routes (intrusion routes) into the facility from the outside. In this embodiment, the design device 1 grasps the configuration of the facility to be secured using a floor plan of the facility to be secured. The floor plan is a diagram of a horizontal cross section at a certain height (e.g., approximately 1.5 m) from the floor of each floor, and displays the layout of the interior of the facility to be secured (the layout of rooms and compartments), the positions of windows, how the windows open, the positions of doors, how the doors open, the layout of major equipment and built-in furniture, and so on. The floor plan also identifies the positions of windows and doors, which are means of allowing people to come and go, so all possible routes (intrusion routes) can be grasped.

[0025] FIG. 2 is a diagram for explaining an example of a floor plan, for example, a floor plan of a company office that is a security facility on the third floor of a building. FIG. 2(A) is an example of a typical floor plan, and in FIG. 2(A) there are three windows on the upper wall, two windows on the left wall, and a double door on the lower wall. The inside of the double door on the lower wall is the entrance, and conference rooms are located on the left and right of the entrance. There is also a single door at the back of the entrance, which allows access to the office inside the office. In FIG. 2(A), the conference room on the left cannot be entered from the entrance, and can only be accessed from the office on the inside.

[0026] In addition, in Figure 2(A), the right-hand conference room can be accessed through a single door on the entrance side, and also through a single door on the office side. The back of the entrance and the two conference rooms are offices where employees work. In addition, in Figure 2(A), the executive office is located on the upper left side of the office, and access to the executive office is possible from the office through a single door. As can be seen in Figure 2(A), the executive office has one window on the top and left sides, the office has two windows on the top side, and the left-hand conference room has one window on the left side.

[0027] The floor plan shown in Fig. 2(A) can be captured as image data, for example, via the image reader 2 connected via the connection terminal 105T and the external I / F 105, and recorded in the floor plan data file 111. By performing image recognition on the floor plan data captured as image data in this way in the floor plan data file 111, it is possible to determine the outer perimeter of the facility to be secured, the layout of the internal rooms and sections, the positions of windows and doors, and so on.

[0028] However, floor plans are generally created as part of the design drawings when the facility to be secured is designed, and are not used regularly after construction, so they may be stored away or lost and cannot be used immediately. In this case, floor plans can be easily created (drawn) and used by using application software such as graphics software or drawing software installed in the design device 1 and operating the operation unit 104.

[0029] FIG. 2(B) is an example of a floor plan created using, for example, graphic software, and is a floor plan for the same security facility as FIG. 2(A). In the floor plan shown in FIG. 2(B), rooms and sections are indicated by straight lines, windows are indicated by hatched rectangles, and doors are indicated by solid rectangles. The floor plan shown in FIG. 2(B), created by using graphic software in the design device 1 and operating the operation unit 104, can be stored, for example, as image data in the floor plan data file 111. The floor plan of FIG. 2(B) as image data stored in the floor plan data file 111 can be subjected to image recognition to identify the outer perimeter of the security facility, the layout of the internal rooms and sections, the positions of windows and doors, and the like, as in the case of the floor plan described using FIG. 2(A).

[0030] In this way, by importing the floor plan (floor plan data) into the floor plan data file 111, the design device 1 can grasp the floor plan of the facility to be secured. Here, the floor plan is imported via the image reader 2 connected to the connection terminal 105T and the external I / F 105 of the design device 1, or is drawn using image software of the design device 1. However, this is not limited to this. For example, if the floor plan is stored on a server device on the Internet, it can also be imported via the connection terminal 101T and the communication I / F 101. It is also possible to have a floor plan created on another personal computer or the like sent as an attachment to an e-mail, and then access a predetermined mail server via the connection terminal 101T and the communication I / F 101 to obtain the floor plan.

[0031] After the floor plan (floor plan data) is imported into the floor plan data file 111, it becomes possible to design the security system using the design device 1. That is, the list data conversion unit 121, graph data generation unit 122, sensor placement processing unit 123, graph evaluation unit 124, and result output unit 125 of the design device 1 function to design the security system.

[0032] [Processing of list data conversion unit 121] Fig. 3 is a diagram for explaining nodes and edges identified for a facility to be guarded, and Fig. 4 is a diagram for explaining examples of a node list and an edge list. In Fig. 3, Fig. 3(A) is a diagram for explaining nodes and edges when using a floor plan created using the image software shown in Fig. 2(B). Also in Fig. 3, Fig. 3(B) is an example of an element list for explaining nodes and edges, which are elements in floor plan data, and Fig. 3(C) is an example of a parameter list for explaining parameters set for nodes and edges.

[0033] As described above, the list data conversion unit 121 performs processing to create a node list and an edge list based on the floor plan data, etc., of the floor plan data file 111. Prior to this processing, the list data conversion unit 121 performs processing to set a target position for the floor plan data. The user can set the target position at any position within the facility to be guarded, but it is desirable to set the target position at a node (room) that is likely to be a target (goal) for intruders or a node (room) that needs to be protected from intruders. For example, if the facility to be guarded is a company office or store, the target position can be set at a node (room) where items to be protected, such as valuables or important documents, are placed, and if it is an ordinary residence, the target position can be set at a child's room where children are likely to be present.

[0034] The user issues an instruction to execute a process for setting a target position via the operation unit 104. In this case, under the control of the control unit 102, the list data conversion unit 121 reads out floor plan data of the facility to be guarded for which a security system is to be designed from the floor plan data file 111. Next, the list data conversion unit 121 displays a floor plan formed from the read floor plan data on the display 107 via the display controller 106. Thereafter, the list data conversion unit 121 accepts a target position instruction input from the user via the operation unit 104, and sets the target position at the specified node (room) within the facility to be guarded. In this case, the user operates the operation unit 104 to specify the target position by writing a predetermined symbol (for example, an asterisk (*)) at the desired position on the floor plan. This allows the target position to be set for the floor plan (floor plan data) of the facility to be guarded.

[0035] The list data conversion unit 121 performs image recognition on the floor plan in which the target position is set, recognizes the target position as a target node, and recognizes areas inside and outside the security facility as nodes. As shown in the element list of FIG. 3(B), nodes refer to distinguishable areas on the floor plan of the security facility, and represent rooms and outdoors. More specifically, as described above, nodes refer to rooms, which are areas separated by walls inside the security facility, and areas (outdoor areas) outside the security facility that are adjacent to the areas (rooms) inside the security facility and connected to the areas by edges. The list data conversion unit 121 makes each of the recognized nodes identifiable and creates a node list, which is a list of nodes, by associating each node with a type and parameters.

[0036] The list data conversion unit 121 also performs image recognition on the floor plan in which the target position is set, and if there is a means of transportation that allows people to move between adjacent nodes, recognizes that means as an edge. As shown in FIG. 3(B), an edge refers to the connection between areas, and more specifically, as described above, refers to a door and a window. The list data conversion unit 121 makes each of the recognized edges identifiable and associates each edge with a type and an adjacent node to create an edge list, which is a list of edges.

[0037] The node list and edge list creation process performed by the list data conversion unit 121 will be specifically described below using the floor plan shown in FIG. 3(A) as an example. As described above, in the floor plan shown in FIG. 3(A), the target position is set by adding an asterisk (*) to the executive office in the upper left corner. Therefore, the list data conversion unit 121 recognizes the executive office as the target node and makes it identifiable as node 1. The list data conversion unit 121 also recognizes the executive office, office, left-side conference room, entrance, and right-side conference room as indoor areas (rooms) separated by walls. In this example, as shown in the upper left corner of each room in FIG. 3(A), the executive office is identifiable as node 2, the office as node 3, the left-side conference room as node 4, the entrance as node 5, and the right-side conference room as node 6.

[0038] Next, the list data conversion unit 121 recognizes edges. First, as described above, in this embodiment, a target position (starting node (node ​​1)) is set for the executive office, and the executive office itself is also recognized as node 2. Therefore, since node 1 and node 2 are both inside the executive office, there is no edge between these nodes as an actual connection such as a door or window. If this continues, node 1 will not be connected to any node, and will not be able to become a target node that serves as the starting point of graph data, which will be described later. Therefore, for convenience, edge 1 is set between node 1 and node 2 as a virtual connection, rather than an actual connection.

[0039] Furthermore, when viewed from the perspective of the executive room, the door connecting the executive room (node ​​2) and the office (node ​​3) is recognized as an edge and is identifiable as edge 2. Similarly, the window above the executive room is recognized as an edge and is identifiable as edge 3, and the window on the left side of the executive room is recognized as an edge and is identifiable as edge 4. Similarly, edges are recognized based on each node, but edges that have already been recognized are excluded because they would be duplicates. Therefore, the door (edge ​​2) connecting the executive room (node ​​2) and the office (node ​​3) has already been recognized when the executive room is used as the reference, and is therefore excluded when the office (node ​​3) is used as the reference.

[0040] Next, looking at the office (node ​​3) as the base, the door connecting the office (node ​​3) and the left-hand conference room (node ​​4) is recognized as an edge, and this is made identifiable as edge 5. Similarly, the door connecting the office (node ​​3) and the entrance (node ​​5) is recognized as an edge, and this is made identifiable as edge 6. Furthermore, the door connecting the office (node ​​3) and the entrance (node ​​5) is recognized as an edge, and this is made identifiable as edge 6. Furthermore, the door connecting the office (node ​​3) and the right-hand conference room (node ​​6) is recognized as an edge, and this is made identifiable as edge 7. Furthermore, the two windows on the upper side of the office (node ​​3) are recognized as edges, and these are made identifiable as edges 8 and 9.

[0041] Furthermore, when viewed from the left conference room (node ​​4) as a reference, the window on the left side of the left conference room (node ​​4) is recognized as an edge, which can be identified as edge 10. When viewed from the right conference room (node ​​6) as a reference, the door connecting the right conference room (node ​​6) and the entrance (node ​​5) is recognized as an edge, which can be identified as edge 11. When viewed from the entrance (node ​​5) as a reference, the lower door is recognized as an edge, which can be identified as edge 12.

[0042] Furthermore, as mentioned above, nodes are not limited to indoor rooms; areas (outdoor areas) outside the security facility that are adjacent to an interior room (node) and connected to the room by an edge are also nodes. Therefore, as shown in FIG. 3(A), the outdoor area connected to node 2, which is an executive office, via edge 3 is recognized as a node, and this is identifiable as node 7. Furthermore, the outdoor area connected to node 3, which is an office, via edge 8 is recognized as a node, and this is identifiable as node 8. Similarly, the outdoor area connected to node 3, which is an office, via edge 9 is recognized as a node, and this is identifiable as node 9.

[0043] Furthermore, the outdoor area connected to node 2, the executive office, via edge 4 is recognized as a node, which is identifiable as node 10. Similarly, the outdoor area connected to node 4, the conference room on the left, via edge 10 is recognized as a node, which is identifiable as node 11. Finally, the outdoor area connected to node 5, the entrance, via edge 12 is recognized as a node, which is identifiable as node 12. Outdoor nodes are terminal nodes (end nodes) when viewed from the target node (node ​​1).

[0044] The list data conversion unit 121 creates a node list and an edge list based on the results of the recognition process for the floor plan described above and the parameter list shown in FIG. 3(C), and records them in the input list file 112. As shown in FIG. 4(A), the node list consists of a node ID, a type, and parameters. The node ID in the node list is identification information that makes each node identifiable. In this embodiment, as described above, the target node is identified as node 1, the executive office as node 2, the office as node 3, ..., and the outdoor area in front of the entrance as node 12, and these are used as node IDs. Note that hereinafter, node 1 will be abbreviated as N1, node 2 as N2, and node 3 as N3.

[0045] The type of the node list corresponds to the type of the node in the parameter list, and is information indicating whether it is a target node, a room (indoor area), or an outdoor (outdoor area). The parameters correspond to the parameters of the nodes in the parameter list of FIG. 3(C), and are auxiliary information set for each node. The node ID and type of the node list are automatically identified based on the recognition processing results of the list data conversion unit 121, and the parameters of the node list are set by the user.

[0046] That is, in this embodiment, if the node is a room (indoor area), an alert level is set as a parameter for the node. The alert level indicates the degree of caution, and in this embodiment, it can be set on a five-level scale from 1 to 5, with alert level 1 being the lowest level and alert level 5 being the highest level. A security system is constructed so that nodes with higher alert levels are more highly protected. In this embodiment, as shown in FIG. 4(A), N2 (executive office) has alert level 5, N3 (office) has alert level 4, and other indoor nodes have alert level 3. In this embodiment, the alert level is used as a criterion for determining whether or not to install passive sensors. Furthermore, if the node is outdoors (outdoor area), the state (appearance) of the outdoor area is set. Specifically, as shown in FIG. 4(A), information indicating whether entry is permitted, floor (floor), road, balcony, emergency stairs, etc. is set.

[0047] In the node list of FIG. 4(A), node IDs N1 to N12 correspond to nodes 1 to 12 shown in FIG. 3(A). As described above, N1 is a target node, and its type is set to "target," and N2 to N6 are each set to a type of "room," with a parameter set to an alert level. The type of N7 to N12 is set to "outdoors." The parameters of N7, N10, and N1 are set to "outside" as the mode. The parameters of N8 and N9 are set to "balcony," and the parameter of N12 is set to "stairs." Note that "outside" means that the outdoor mode does not include any accessories such as stairs or a balcony, and is simply outdoors.

[0048] On the other hand, the edge list consists of an edge ID, a type, adjacent node 1, and adjacent node 2, as shown in FIG. 4(B). The edge ID in the edge list is identification information that makes each edge identifiable. In this embodiment, as described above, the edge connecting N1 (target node) and N2 (executive office) is identified as E1, the edge connecting N2 and N3 as E2, and the edge connecting N5 and N12 as E12. Therefore, E1, E2, ..., E12 are used as edge IDs. In the following, edge 1 will be abbreviated as E1, edge 2 as E2, edge 3 as E3, ...

[0049] The type of the edge list corresponds to the type of the edge in the parameter list in FIG. 3(C), and is indicated as either "none," "door," or "window." The type "none" indicates that the edge is a virtual edge, not an actual edge. Adjacent node 1 and adjacent node 2 correspond to the parameters for the edge in the parameter list, and are information indicating which node each edge connects to. In other words, each edge indicates that it is an edge connecting adjacent node 1 and adjacent node 2. The edge ID, type, adjacent node 1, and adjacent node 2 in the edge list are automatically identified based on the recognition processing results of the list data conversion unit 121.

[0050] In the edge list of FIG. 4(B), the edge IDs E1 to E12 correspond to edges 1 to 12 shown in FIG. 3(A). As mentioned above, E1 is a virtual edge connecting N1 (target node) and N2 (executive office). The type is set to "none," indicating that it is an edge connecting N1 and N2. Furthermore, E2 is a door connecting N2 (executive office) and N3 (office), E3 is a window connecting N2 (executive office) and N7 (outdoors), and E4 is a window connecting N2 (lead office) and N10 (outdoors).

[0051] In addition, in the edge list of FIG. 4(B), E5 is shown to be a door connecting N3 (office) and N4 (left-side conference room), and E6 is shown to be a door connecting N3 (office) and N5 (entrance). Also, E7 is shown to be a door connecting N3 (office) and N6 (right-side conference room), E8 is shown to be a window connecting N3 (office) and N8 (outdoors), and E9 is shown to be a window connecting N3 (office) and N9 (outdoors). Also, E10 is shown to be a window connecting N4 (left-side conference room) and N11 (outdoors), E11 is shown to be a door connecting N5 (entrance) and N6 (right-side conference room), and E12 is shown to be a door connecting N5 (entrance) and N12 (outdoors). In this way, the list data conversion unit 121 forms a node list (Figure 4(A)) and an edge list (Figure 4(B)) from the floor plan (Figure 3(A)) formed by the floor plan data in the floor plan data file 111, and stores them in the input list file 112.

[0052] [Processing of the graph data generation unit 122] The graph data generation unit 122 generates basic graph data based on the node list and edge list in the input list file 112, and records this in the basic graph data file 113. FIG. 5 is a diagram for explaining an example of basic graph data. As shown in FIG. 5, the basic graph data consists of a node ID, a type, and a list of adjacent nodes and edges passed through to reach those nodes (hereinafter referred to as a path list). The node IDs and types correspond to the node IDs and types in the node list shown in FIG. 4(A). The path list is information indicating the edges passed through to reach the adjacent nodes from each node, and is generated mainly based on the edge list shown in FIG. 4(B). A method for generating a path list will be explained below.

[0053] Basically, the path list of the basic graph data is created by starting from the target node, tracing adjacent indoor nodes of the facility under security, and identifying adjacent nodes connected by edges for each node toward the terminal outdoor node. Therefore, in this embodiment, the adjacent nodes adjacent to these nodes and the edges through which to reach those adjacent nodes are identified in the order of N1 → N2 → N3 → N4 → N5 → N6. For example, if it is determined that door (E2) is required to go from the executive room (N2) to the office (N3), the reverse path from the office (N3) to the executive room (N2) through door (E2) is excluded. This is because the path through door (E2) from the office (N3) to the executive room (N2) is in the opposite direction (not away from the target node). Furthermore, it may overlap with a previously identified path. The same applies to similar cases below.

[0054] Therefore, there is no need to focus on outdoor nodes and identify adjacent nodes and the edges to go to those adjacent nodes. Outdoor nodes in a guarded facility are always connected to indoor nodes via edges. Therefore, if the adjacent nodes and the edges to go to those adjacent nodes have been identified for an indoor node, identifying the edges to go from the outdoor node to the adjacent indoor node will result in the direction of identification being reversed. It will also result in overlapping with already identified routes.

[0055] Let's check the contents of the route list according to Figure 5. First, let's focus on N1 (target node). As shown in the edge list in Figure 4(B) and the floor plan in Figure 3(A), N1 (target node) is adjacent to N2 (executive office), and to get from N1 to N2, you must pass through E1 (a hypothetical edge). For this reason, as can be seen from the row for N1 in Figure 5, the adjacent node and the edge to pass through to get to that node are listed in parentheses, such as "N2(E1)." N1 has no adjacent nodes other than N2.

[0056] Next, we focus on N2 (the executive office). As shown in the edge list in Figure 4(B) and the floor plan in Figure 3(A), N2 is adjacent to N3 (the office), N7 (outdoor), and N10 (outdoor). To go from N2 to N3, you go through E2 (door), to go from N2 to N7, you go through E3 (window), and to go from N2 to N10, you go through E4 (window). Therefore, as shown in the row for N2 in Figure 5, the adjacent nodes and the edges to go through to get to that node are listed in parentheses, such as "N3 (E2)," "N7 (E3)," and "N10 (E4)." Here, as mentioned above, the path from N2 to N1 is excluded because it is in the opposite direction to the specified direction and overlaps with the path already identified when focusing on N1.

[0057] Next, let's look at N3 (office). As shown in the edge list in Figure 4(B) and the floor plan in Figure 3(A), N3 is adjacent to N4 (left-side conference room), N5 (entrance), N6 (right-side conference room), N8 (outdoor), and N9 (outdoor). To go from N3 to N4, you go through E5 (door), to go from N3 to N5, you go through E6 (door), to go from N3 to N6, you go through E7 (door), to go from N3 to N8, you go through E8 (window), and to go from N3 to N9, you go through E9 (window). For this reason, as shown in the row for N3 in Figure 5, the adjacent nodes and the edges to go through to get to each node are listed in parentheses, such as "N4 (E5)," "N5 (E6)," "N6 (E7)," "N8 (E8)," and "N9 (E9)." Here, as described above, the route going from N3 to N2 is excluded because the specific direction is reversed and the route overlaps with the route already identified with focus on N2.

[0058] Next, we focus on N4 (the left-hand conference room). As shown in the edge list in Figure 4(B) and the floor plan in Figure 3(A), N4 is adjacent to N11 (outdoors). To get from N4 to N11, one must pass through E10 (the window). For this reason, as shown in the row for N4 in Figure 5, the adjacent node and the edge to pass through to get to that node are listed in parentheses, such as "N11 (E10)." Here, as mentioned above, the route from N4 to N3 is excluded because the specific direction is reversed and it overlaps with the route already identified by focusing on N3.

[0059] Next, we focus on N5 (the entrance). As shown in the edge list in Figure 4(B) and the floor plan in Figure 3(A), N5 is adjacent to N12 (outdoor). To go from N5 to N12, one must pass through E12 (door). For this reason, as shown in the row for N5 in Figure 5, the adjacent node and the edge to pass through to get to that node are listed in parentheses, such as "N12 (E12)." As mentioned above, the route from N5 to N3 is excluded because it is the opposite of the specific direction and overlaps with the route already identified by focusing on N3. Furthermore, N5 (the entrance) is also adjacent to N6 (the right-hand conference room). However, the direction from N5 to N6 is excluded because it is the opposite of the specific direction, not the direction toward the outdoor node, which is the terminal node. Therefore, this route is understood by focusing on N6 (the right-hand conference room).

[0060] Next, we focus on N6 (the right-hand conference room). As shown in the edge list in Figure 4(B) and the floor plan in Figure 3(A), N6 is adjacent to N5 (the entrance). To get from N6 to N5, one must pass through E11 (the door). For this reason, as shown in the row for N6 in Figure 5, the adjacent node is listed in parentheses, such as "N5 (E11)," and the edge to pass through to get to that node. In this case, the route will reach N12, an outdoor node, via the route identified by focusing on N5 (the entrance) described above. Note that, as mentioned above, the route from N6 to N3 is excluded because it is in the opposite direction and overlaps with the route already identified by focusing on N3.

[0061] As mentioned above, the outdoor nodes N7, N8, N9, N10, N11, and N12 are excluded because the specific direction is reversed and they overlap with routes already identified focusing on indoor nodes. For this reason, in FIG. 5, as shown in the rows for N7 to N12, "null (no data)" is written, indicating that there is no route from the node to any other adjacent node. In this way, the graph data generation unit 122 creates basic graph data (FIG. 5) from the node list (FIG. 4(A)) and edge list (FIG. 4(B)) of the input list file 112, and records the basic graph data in the basic graph data file 113.

[0062] FIG. 6 is a diagram showing a graph image created from the basic graph data shown in FIG. 5. The graph data shown in FIG. 5 is composed of a group of nodes and a group of edges that represent the connections between the nodes. In FIG. 6, the nodes are shown as circles, the edges connecting the nodes are shown as rectangles, and the graph image is constructed by connecting these with straight lines. Therefore, FIG. 5 and FIG. 6 show the same content, just in different representation formats.

[0063] That is, as shown in Figures 5 and 6, for example, starting from N1 (target node) set in the executive office where valuables are kept, there is a route from N1 through E1 (virtually installed edge) to N2 (executive office). Furthermore, from N2, there are routes through E2 (door) to N3 (office), through E3 (window) to N7 (outside), and through E4 (window) to N10. The outdoor nodes N7 and N10 have no adjacent nodes and constitute terminal (end) nodes.

[0064] From N3 (office), there are three routes: one to N4 (left-hand conference room) via E5 (door), one to N5 (entrance) via E6 (door), and one to N6 (right-hand conference room) via E7 (door). Also, from N6 (right-hand conference room), there is a route to N5 (entrance) via E11 (door). Furthermore, from N3 (office), there are three routes: one to N8 (outdoor balcony) via E8 (window), and one to N9 (outdoor balcony) via E9 (window). In this case, the outdoor nodes N8 and N9 have no adjacent nodes, and constitute terminal (end) nodes.

[0065] There is a route from N4 (the left-hand conference room) through E10 (the window) to N11 (outside), and there is a route from N5 (the entrance) through E12 (the door) to N12 (the outside stairs). As shown in Figure 6, the outdoor nodes N11 and N12 have no adjacent nodes and constitute terminal (end) nodes. In Figure 6, N7, N8, N9, N10, N11, and N12, which are enclosed in double circles, are all outdoor nodes and are terminal (end) nodes.

[0066] As can be seen from Figure 6, there are six possible intrusion routes from the outside: E3 (window), E4 (window), E8 (window), E9 (window), E10 (window), and E12 (door), which are connected to N7, N8, N9, N10, N11, and N12. Furthermore, if an intruder enters N5 (entrance) via E12 (door) from N12 (stairs), there are two routes to N3 (office). One is from N5 (entrance) through E6 (door) to N3 (office). The other is from N5 (entrance) through E11 (door), into N6 (right-hand conference room), and then through E7 (door) to N3 (office).

[0067] Therefore, from the graph data shown in Fig. 5 and the graph image shown in Fig. 6, it can be seen that there are six intrusion routes and seven routes leading to N1 (target node). In this way, based on the basic graph data in Fig. 5 and the basic graph image in Fig. 6, all routes starting from N1 (target node) and each outdoor node as a terminal node (terminal node) can be seen. In other words, all routes leading from each outdoor node (N7 to N12) to N1 (target node) can be seen.

[0068] [Processing of the sensor placement processing unit 123] The sensor placement processing unit 123 sets the types and placement positions of security machines to be placed in accordance with predetermined criteria for the basic graph data (FIG. 5), to form sensor placement graph data, and stores this in the sensor placement graph data file 114. In this embodiment, the predetermined criteria are determined in advance, and for example, a security machine installation criteria list (hereinafter simply referred to as the installation criteria list) stored in the storage device 103 is used. FIG. 7 is a diagram for explaining an example of sensor placement graph data. Also, FIG. 8 is a diagram for explaining an example of the installation criteria list.

[0069] First, an example of the installation criteria list in Fig. 8 will be described. The installation criteria list in this embodiment includes the installation target, installation conditions, security machine The installation targets are nodes and edges. The installation conditions are determined based on the type and parameters for nodes, and based on the type for edges. security machine is installed security machine Therefore, in the security machine installation criteria list shown in Fig. 8, it is set that a PS (passive sensor) is to be installed for a node that is a room and has an alert level of 5. Also, it is set that an MG (magnetic switch) is to be installed for an edge that is a door or a window.

[0070] 8, the installation targets are simply nodes and edges, but this is not limited to this. The installation criteria list can also contain more detailed information indicating what kind of nodes and edges and what kind of security machines are to be installed. It is also possible to add information indicating the installation mode, such as the number of security machines to be installed.

[0071] For example, the installation targets can be set in more detail, such as indoor nodes connected to outdoors, indoor nodes connected only to indoor nodes, edges connecting outdoor nodes with indoor nodes, and edges connecting indoor nodes with indoor nodes. It is also possible to consider the parameters of outdoor nodes, such as edges connecting outdoor nodes that are balconies or stairs with indoor nodes. The installation conditions for nodes can also be specified as a range, such as alert levels of 5 to 4. It is also possible to set the number of passive sensors (PS) to be installed according to the alert level, or to use different types of magnetic switches (MG) for doors and windows.

[0072] As described above, the route list column of the basic graph data (FIG. 5) lists all routes from outdoor nodes to N1 (target node) in the security facility. Therefore, the sensor placement processor 123 uses the basic graph data (FIG. 5) read from the basic graph data file 113 as base data to create sensor placement graph data. That is, the sensor placement graph data is created by performing a process of installing security machines for the nodes and edges listed in the route list of the basic graph data (FIG. 5). In this case, the sensor placement processor 123 follows the standards of the installation standard list (FIG. 8) and uses the node list (FIG. 4(A)) and edge list (FIG. 4(B)) as reference data.

[0073] The processing performed by the sensor placement processor 123 will now be described in detail. First, the sensor placement processor 123 refers to the installation criteria list (FIG. 8) to determine the installation criteria for security equipment. Next, the sensor placement processor 123 refers to the route list for N1 (target node) in the read basic graph data (FIG. 5) and performs settings related to the installation of security equipment for N2 and E1. In this case, the sensor placement processor 123 refers to the node list (FIG. 4(A)) for N2 and determines whether or not it matches the installation criteria. As shown in FIG. 4(A), N2 is a room and has an alert level of 5 set as a parameter, so it matches the installation criteria, and a setting is made to install a PS (passive sensor) in N2.

[0074] Similarly, the sensor placement processor 123 refers to the edge list ("FIG. 4(B)") for E1 and determines whether it meets the installation criteria. As shown in FIG. 4(B), the type of E1 is "none," meaning that it is a virtually installed edge that is neither a door nor a window, and therefore it does not meet the installation criteria, and it can be determined that no security machine will be installed at E1. As a result, the sensor placement processor 123 forms sensor placement graph data in which the description of the route list for N1 (target node) is changed to "N2[PS]E1," as shown in FIG. 7. This indicates that a PS (passive sensor) will be installed at N2, but no security machine will be installed at E1. That is, in the description "N2[PS]E1," a description in square brackets, such as [PS], indicates that a PS (passive sensor) or MG (magnetic switch) will be installed for the node or edge described immediately before.

[0075] Similarly, the sensor placement processing unit 123 forms sensor placement graph data for N2. In the row of N2 in FIG. 7, settings related to the installation of security machines are made as shown by "N3(E2(MG))," "N7(E3(MG))," and "N10(E4(MG))." That is, as can be seen by referring to the node list in FIG. 4(A), N3, N7, and N10 are all rooms and do not satisfy the installation criteria of having an alert level of 5, so PSs (passive sensors) are not installed. As can be seen by referring to the edge list in FIG. 4(B), E2, E3, and E4 are all doors or windows, so they satisfy the installation criteria, and MGs (magnetic switches) are installed for them.

[0076] Similarly, the sensor placement processing unit 123 forms sensor placement graph data for N3. In the row of N3 in FIG. 7, settings related to the installation of security machines are made as shown by "N4(E5(MG))," "N5(E6(MG))," "N6(E7(MG))," "N8(E8(MG))," and "N9(E9(MG))." That is, as can be seen by referring to the node list in FIG. 4(A), N4, N5, N6, N8, and N9 are all rooms and do not satisfy the installation criteria of having an alert level of 5, so PSs (passive sensors) are not installed. As can be seen by referring to the edge list in FIG. 4(B), E5, E6, E7, E8, and E9 are all doors or windows, so they satisfy the installation criteria, and MGs (magnetic switches) are installed for them.

[0077] Similarly, the sensor placement processing unit 123 forms sensor placement graph data for N4. In the row of N4 in Fig. 7, settings related to the installation of a security machine are made, as shown as "N11 (E10 (MG))". That is, as can be seen by referring to the node list in Fig. 4(A), N11 does not satisfy the installation criteria of being a room and having an alert level of 5, so a PS (passive sensor) is not installed. As can be seen by referring to the edge list in Fig. 4(B), E10 is a window, so it satisfies the installation criteria, and an MG (magnetic switch) is installed therefor.

[0078] Similarly, the sensor placement processing unit 123 forms sensor placement graph data for N5. In the row of N5 in Fig. 7, settings related to the installation of a security machine are made, as shown as "N12 (E12 (MG))". That is, as can be seen by referring to the node list in Fig. 4(A), N12 does not satisfy the installation criteria of being a room and having an alert level of 5, so a PS (passive sensor) is not installed. As can be seen by referring to the edge list in Fig. 4(B), E12 is a door, so it satisfies the installation criteria, and an MG (magnetic switch) is installed for it.

[0079] Similarly, the sensor placement processing unit 123 forms sensor placement graph data for N6. In the row of N6 in Fig. 7, settings related to the installation of a security machine are made, as shown as "N5(E11(MG))". That is, as can be seen by referring to the node list in Fig. 4(A), N5 does not satisfy the installation criteria of being a room and having an alert level of 5, so a PS (passive sensor) is not installed. As can be seen by referring to the edge list in Fig. 4(B), E11 is a door, so it satisfies the installation criteria, and an MG (magnetic switch) is installed for it.

[0080] As can be seen from the rows N7 to N12 in Fig. 7, there is no list of adjacent nodes and edges passed through to reach those nodes. Therefore, as described above, after forming sensor location graph data using the list of adjacent nodes N1 to N6 and edges passed through to reach those nodes as processing targets, the sensor location graph data formation process in the sensor location processing unit 123 ends. The sensor location processing unit 123 records the sensor location graph data formed as shown in Fig. 7 in the sensor location graph data file 114.

[0081] [Processing of the graph evaluation unit 124] The graph evaluation unit 124 performs processing to calculate the total score of the security machines set on the routes from N1 to N7, N8, N9, N10, N11, and N12 based on the sensor placement graph data (FIG. 7) and the scores determined in advance for each security machine. The graph evaluation unit 124 compiles the total score of the security machines on each route as evaluation graph data and records it in the evaluation graph data file 115. Here, the scores determined in advance for each security machine are registered in the sensor data stored in the storage device 103, for example. FIG. 9 is a diagram for explaining an example of sensor data.

[0082] First, an example of sensor data in FIG. 9 will be described. As shown in FIG. 9(A), the sensor data in this embodiment has columns for identification information, type, fee, and score. The identification information is information that can uniquely identify a security machine. The type is information that indicates what kind of security machine the security machine is. In this embodiment, the type indicates whether it is a passive sensor or a magnetic switch. The fee is the price of the security machine and may include installation costs. The score is information for objectively understanding the security level for each route, and is information that indicates an evaluation value that is predetermined for each security machine.

[0083] Therefore, in this embodiment, two types of security machines are used, as shown in Figure 9(A). One is a security machine with identification information "PS", a type "passive sensor", a fee of "10,000 yen", and a score of "40". The other is a security machine with identification information "MG", a type "magnetic switch", a fee of "3,000 yen", and a score of "60".

[0084] Note that the sensor data shown in FIG. 9(A) has a simple configuration in which two types of security machines are used, but the configuration of the sensor data is not limited to this. FIG. 9(B) is a diagram for explaining another example of sensor data. The sensor data shown in FIG. 9(B) has a column for "Installation Conditions, etc." In FIG. 9(B), the identification information, type, fee, and score are the same as those in the sensor data shown in FIG. 9(A). For passive sensors, the "Installation Conditions, etc." indicates the size of the room in which the sensor can be installed, and for magnetic switches, indicates whether the sensor is for a door or a window. In the case of the sensor data in FIG. 9(B), the sensor placement processing unit 123 can also use the sensor data to identify the installation location and type of security machine.

[0085] In this embodiment, for simplicity of explanation, the sensor data will be described as having the simple configuration shown in Fig. 9(A). Fig. 10 is a diagram for explaining an example of evaluation graph data. Fig. 11 is a diagram showing a graph image created from the evaluation graph data. As can be seen from a comparison of the evaluation graph data in Fig. 10 with the sensor placement graph data in Fig. 7, the evaluation graph data has a column for alert scores, and other than this, the configuration is the same as the sensor placement graph data described using Fig. 7.

[0086] Therefore, the information shown in the route list column of the evaluation graph data in Figure 10 makes it possible to determine the routes from N1 (target node) to each of the outdoor nodes N7, N8, N9, N10, N11, and N12. Furthermore, it is possible to determine which security equipment is installed at which node and on which edge of each route. Therefore, the information shown in the route list column of the evaluation graph data in Figure 10 makes it possible to create the graph image shown in Figure 11.

[0087] The graph image in Figure 11, like the graph image in Figure 6, shows the routes from N1 (target node) to each of the outdoor nodes (terminal nodes) N7, N8, N9, N10, N11, and N12. Furthermore, the graph image in Figure 11 also shows which nodes and edges will have security equipment installed. That is, the graph image in Figure 11 shows that a PS (passive sensor) with a fee of 10,000 yen and a score of 40 will be installed in N2 (executive office). There are no nodes other than N2 (executive office) where passive sensors will be installed. The graph image in Figure 11 also shows that a magnetic switch with a fee of 3,000 yen and a score of 60 will be installed in all edges.

[0088] The graph image in Figure 11 also shows the total score of the security devices on the route from N1 to the terminal node. That is, in the case of the route from N1 → E1 → N2 → E4 → N10, a passive sensor with a score of 40 is installed at N2, and a magnetic switch with a score of 60 is installed at E4, so the total score is 40 + 60 = "100." In addition, in the case of the route from N1 → E1 → N2 → E3 → N7, a passive sensor with a score of 40 is installed at N2, and a magnetic switch with a score of 60 is installed at E3, so the total score is 40 + 60 = "100."

[0089] Also, in the case of the route N1 → E1 → N2 → E2 → N3 → E8 → N8, a passive sensor with a score of 40 is installed at N2, and magnetic switches with a score of 60 are installed at E2 and E8, so the total score is 40 + 60 + 60 = "160". Also, in the case of the route N1 → E1 → N2 → E2 → N3 → E9 → N9, a passive sensor with a score of 40 is installed at N2, and magnetic switches with a score of 60 are installed at E2 and E9, so the total score is 40 + 60 + 60 = "160".

[0090] Also, for the route N1 → E1 → N2 → E2 → N3 → E5 → N4 → E10 → N11, a passive sensor with a score of 40 is installed at N2, and magnetic switches with a score of 60 are installed at E2, E5, and E10. In this case, the total score is 40 + 60 + 60 + 60 = "220". Also, for the route N1 → E1 → N2 → E2 → N3 → E6 → N5 → E12 → N12, a passive sensor with a score of 40 is installed at N2, and magnetic switches with a score of 60 are installed at E2, E6, and E12. In this case, the total score is 40 + 60 + 60 + 60 = "220".

[0091] Furthermore, in the case of a route from N1 → E1 → N2 → E2 → N3 → E7 → N6 → E11 → N5 → E12 → N12, a passive sensor with a score of 40 is installed at N2, and magnetic switches with a score of 60 are installed at E2, E7, E11, and E12. In this case, the total score is 40 + 60 + 60 + 60 + 60 = "280". The graph evaluation unit 124 records this result in the security score column of the evaluation graph data. As a result, as shown in the security score column of the evaluation graph data in FIG. 10, the total score of the security machines on the route from N1 to the terminal node is recorded as the security score.

[0092] 11 and 10, the security score for the route to N7 is recorded as "100", the security score for the route to N8 is recorded as "160", the security score for the route to N9 is recorded as "160", and the security score for the route to N10 is recorded as "100". Furthermore, the security score for the route to N11 is recorded as "220", and the security score for the route to N12 that does not pass through the right-hand conference room is recorded as "220", and the security score for the route that passes through the right-hand conference room is recorded as "280". In this way, the evaluation graph data in which the security scores are recorded is recorded in the evaluation graph data file 115.

[0093] [Processing of result output unit 125] The result output unit 125 creates evaluation results based on the evaluation graph data recorded in the evaluation graph data file 115, and displays them on the display 107 via the display controller 106 or prints them out using a printer (not shown). The evaluation results may be in the form of a list as shown in Fig. 10 or a graph image as shown in Fig. 11, for example.

[0094] It is assumed that experience with building security systems has shown that no matter how short a route is, a route with a security score of less than 100 can be determined to have insufficient mechanical security. It is also assumed that experience with building security systems has shown that no matter how long a route is, a route with a security score of more than 200 can be determined to have excessive mechanical security. For this reason, it is assumed that the minimum security score is set to 100 and the maximum security score is set to 200, and that this information is pre-recorded in a readable manner in a predetermined storage area of ​​storage device 103, for example.

[0095] For this reason, the result output unit 125 reads the minimum security score from the storage device 103, and makes the outdoor nodes at the ends of routes whose total security score is less than the minimum value distinguishable by displaying them in reverse or, for example, in blue. The result output unit 125 also reads the maximum security score from the storage device 103, and makes the outdoor nodes at the ends of routes whose total security score is greater than the maximum value distinguishable by displaying them in reverse or, for example, in red. This makes it possible to notify the user of routes with insufficient security and routes with excessive security, and the user can, for example, use the operation unit 104 to instruct the deletion or addition of security equipment in response to the evaluation results displayed on the display 107.

[0096] In this case, under the control of the control unit 102, the sensor placement processing unit 123 functions to modify the sensor placement graph data in the sensor placement graph data file 114 by adding or deleting security devices. Thereafter, under the control of the control unit 102, the graph evaluation unit 124 functions to regenerate evaluation graph data based on the modified sensor placement graph data in the sensor placement graph data file 114 and re-record it in the evaluation graph data file 115. Thereafter, the result output unit 125 functions to re-output the evaluation results according to the modified evaluation graph data, which the user can check. The user can make further modifications as necessary.

[0097] Furthermore, for routes where the total security score is less than the minimum value, the result output unit 125 can notify the user by, for example, highlighting, flashing, or displaying in a conspicuous color, nodes or edges to which no security equipment is connected.For routes where the total security score is greater than the maximum value, the result output unit 125 can notify the user by, for example, highlighting, flashing, or displaying in a conspicuous color, nodes or edges to which removable security equipment is installed.Specifically, if a magnetic switch is installed on an edge connecting indoor nodes whose alert level is not 5, the edge can be notified as an edge that does not require the installation of a magnetic switch.

[0098] Furthermore, if a passive sensor is installed at a node other than a node with an alert level of 5, for example, at the user's instruction, the node can be notified as a node for which a passive sensor does not need to be installed. Furthermore, the result output unit 125 can also notify the user of nodes and edges to which no security machine is connected for routes where the total security score is equal to or greater than the minimum value and less than the maximum value. In this case, it is also possible to notify the user of nodes and edges to which no security machine is connected, based on the sensor data, within a range that does not exceed the maximum value.

[0099] The sensor placement correction process will be described assuming that the evaluation results are displayed on display 107 in the form of a graph image shown in Fig. 11. In the case of the evaluation results in the form of a graph image shown in Fig. 11, the security scores for the route leading to N7 and the route leading to N10 are equal to or greater than 100, which is the minimum security score, and equal to or less than 200, which is the maximum security score. Therefore, there is no need to correct the placement of security equipment for these two routes. Furthermore, for these two routes, there are no nodes or edges on which security equipment is not installed other than E1, which is a virtual edge.

[0100] The security scores for the routes to N8 and N9 are also greater than or equal to 100, the minimum security score, and less than or equal to 200, the maximum security score. Therefore, there is no need to modify the placement of security machines for these two routes. However, the security scores for the routes to N11 and N12 are greater than or equal to 200, the maximum security score, so the placement of security machines must be modified to bring the security score above the minimum and below the maximum.

[0101] In this case, the user can determine that the magnetic switches installed on edges E5, E6, E7, and E11, which connect indoor nodes with a security level other than 5, can be deleted. This is because if magnetic switches are installed on edges connecting outdoor nodes and indoor nodes, it can be determined that there is less need to install magnetic switches on edges connecting indoor nodes with a low security level.

[0102] In this case, as described above, the result output unit 125 can also notify the user that edges E5, E6, E7, and E11, which connect indoor nodes that do not have an alert level of 5, are edges that can be deleted from the security equipment. In FIG. 11, ▲ marks are added near E5, E6, E7, and E11, indicating that magnetic switches do not need to be installed on these edges. If the magnetic switches that were to be installed at E5, E6, E7, and E11 are deleted, the security scores will all be 160, as shown in parentheses near N11 and N12 in FIG. 11, satisfying the condition that the security score is greater than or equal to the minimum value and less than or equal to the maximum value.

[0103] However, in this case, the security scores of the routes branching off from N3 (office) to N8, N9, N11, and N12 are all 160, meaning there is a margin of 40 points up to the maximum security score of 200. This makes it possible to install a PS (passive sensor) in N3 (office). In this way, if the security score of the route to the terminal node is less than the maximum value, and if, based on the sensor data information in Figure 9(A), there is a node or edge where a security machine can be installed, then a security machine may be placed at that node or edge.

[0104] Fig. 12 is a diagram for explaining changes to the evaluation graph data. Fig. 12 shows an evaluation graph image formed based on the evaluation graph data of the evaluation graph data file 115 after the change. In Fig. 12, to clearly show the difference from the evaluation graph image shown in Fig. 11, x marks are added near edges E5, E6, E7, and E11 where no magnetic switches are installed. In addition, in N3 (office) where a new passive sensor has been installed, information about the installed passive sensor is shown surrounded by a square.

[0105] As a result, the security score for the routes leading to the terminal nodes N8, N9, N11, and N12 becomes 200, satisfying the condition that the security score is greater than or equal to 100 and less than or equal to 200. Note that the display of the x marks and information about the newly installed passive sensors is shown for the sake of convenience in order to simplify the explanation. However, if you wish to output evaluation graph data or an evaluation graph image showing the changed areas, it is sufficient to store both the evaluation graph data before the change and the evaluation graph data after the change in an evaluation graph data file 115 that makes them distinguishable.

[0106] Figure 13 shows the results of the evaluation of the security facility according to the changed evaluation graph data. security machine 13 is a diagram for explaining the arrangement of passive sensors and magnetic switches, which are components of the floor plan. The diagram shown in Fig. 13 can be created based on the floor plan data recorded in the floor plan data file 111 and the evaluation graph data recorded in the evaluation graph data file 115. The diagram shown in Fig. 13 can be created by the result output unit 125, and displayed on the display 107 via the display controller 106, or printed out from a printer connected to an external I / F (not shown).

[0107] As can be seen from the diagram in Figure 13, it can be visually and objectively recognized that MGs (Magnetic Switches) are installed on all edges (E3, E4, E8, E9, E10, E12) connecting outdoor nodes with indoor nodes. In addition, it can be visually and objectively recognized that PSs (Passive Sensors) are installed on N2 (Executive Office) where N1 (Target Node) is set and N3 (Office) where all nodes are connected.

[0108] [Summary of processing performed by security system design device 1] Fig. 14 is a flowchart for explaining the processing performed in the design device 1 according to the embodiment. The processing shown in Fig. 14 is executed by the control unit 102 of the design device 1, and is executed by the list data conversion unit 121, graph data generation unit 122, sensor placement processing unit 123, graph evaluation unit 124, and result output unit 125 functioning under the control of the control unit 102. When the user instructs the control unit 102 to execute a security system design process via the operation unit 104, the control unit 102 executes the processing shown in Fig. 14.

[0109] The control unit 102 executes a process of accepting floor plan data in response to operation input from the user received through the operation unit 104 and recording the data in the floor plan data file 111 (step S101). Step S101 involves processing such as importing the floor plan as image data through the image reader 2, or activating a graphics application to accept drawing input for the floor plan. It is also possible to import a floor plan stored on a server on the Internet, or to use floor plan data provided as an attachment to an e-mail and recorded in a storage device.

[0110] Next, under the control of the control unit 102, the list data conversion unit 121 starts to function. The list data conversion unit 121 converts the floor plan data in the floor plan data file 111 into a node list (FIG. 4(A)) and an edge list (FIG. 4(B)), and records these in the input list file 112 (step S102). At this time, the parameter list in the storage device 103 is referenced. Next, under the control of the control unit 102, the graph data generation unit 122 starts to function. The graph data generation unit 122 generates basic graph data (FIG. 5) from the node list and edge list in the input list file 112, and records this in the basic graph data file 113 (step S103).

[0111] Thereafter, the sensor placement processing unit 123 functions under the control of the control unit 102. The sensor placement processing unit 123 forms sensor placement graph data ( FIG. 7 ) by placing security machines at nodes and edges based on the basic graph data in the basic graph data file 113 in accordance with the installation criteria list in the storage device 103 (step S104). The sensor placement processing unit 123 records the formed sensor placement graph data in the sensor placement graph data file 114.

[0112] Next, under the control of the control unit 102, the graph evaluation unit 124 functions. Based on the sensor location graph data in the sensor location graph data file 114, the graph evaluation unit 124 calculates a security score for each route from N1 (target node) to each terminal node, and forms evaluation graph data (FIG. 10) (step S105). The security score is the total value of the scores of the security machines on each route. In this case, the graph evaluation unit 124 forms evaluation graph data by referring to the sensor data (FIG. 9(A)) stored in the storage device 103, and records this in the evaluation graph data file 115.

[0113] Thereafter, the result output unit 125 functions under the control of the control unit 102. The result output unit 125 forms evaluation result information for output based on the evaluation graph data in the evaluation graph data file 115 and outputs it (step S106). The evaluation result information can be in the form of a list shown in FIG. 10 or a graph image shown in FIG. 11, for example. This evaluation result information is displayed on the display 107 or output via a printer connected to an external I / F (not shown). In this embodiment, the evaluation result information is displayed on the display 107 and provided to the user.

[0114] Thereafter, the control unit 102 receives an operation input from the user through the operation unit 104 (step S107). The control unit 102 determines whether the received operation input is an instruction to terminate (step S108). Assume that in the determination process of step S108, it is determined that the operation input received in step S107 is not an instruction to terminate. In this case, the control unit 102 determines that the operation input is an instruction to correct the sensor placement graph data, and performs the process of step S109. In this case, the control unit 102 controls the sensor placement processing unit 123 to execute a correction process for the sensor placement graph data in the sensor placement graph data file 114 in accordance with the operation input from the user (step S109). Thereafter, the control unit 102 repeats the process from step S105, re-evaluates the security score, and re-outputs the evaluation result, thereby enabling repeated correction.

[0115] Also, suppose that in the determination process of step S108, it is determined that the operation input received in step S107 is an instruction to terminate. In this case, the control unit 102 controls each unit to execute a predetermined termination process (step S110), and terminates the process shown in Fig. 14. As a result, evaluation graph data is formed in the evaluation graph data file 115, in which the security scores from N1 (target node) to each terminal node satisfy a predetermined standard. This evaluation graph data becomes appropriate design information for the security system.

[0116] [Effects of the embodiment] Basically, a security system can be automatically designed based on floor plan data generated from a floor plan. In this case, a security score for each route from the target node to each terminal node is calculated using a score determined according to the security equipment, and the status of the mechanical security for each route can be objectively grasped based on this security score. Furthermore, the placement of security equipment can be modified as necessary. This allows even non-expert engineers to design an appropriate security system that provides sufficient security effectiveness when building a security system for a facility to be secured.

[0117] [Variations] In the above-described embodiment, edges are described as doors or windows. However, this is not limited to this. Facilities to be secured may have simple entrances and exits without doors, or inspection hatches in walls that are not originally intended to allow people to enter or exit but are large enough to allow people to pass through. These may also be added to edges. In this case, passive sensors may be provided for edges that do not open or close, and magnetic switches may be provided for inspection hatches that are provided with lids or the like.

[0118] In the above-described embodiment, each route is evaluated based on the security score. In addition, the price of the security equipment may also be taken into consideration. For example, as shown in FIG. 9, the sensor data also contains information indicating the price of each security equipment, so the total price of the installed security equipment may be calculated and output. This function may involve, for example, having the graph evaluation unit 124 calculate the total price and record it in the evaluation graph data, and having the result output unit 125 output the total price.

[0119] Furthermore, if there are multiple installable security machines with different prices, sensor placement graph data using the more expensive machine and sensor graph data using the less expensive machine may be created and output for comparison. This function can be realized as a function of the sensor placement processing unit 123. In this way, various improvements can be made to the sensor placement processing unit 123, graph evaluation unit 124, etc., so that necessary information can be added to the sensor placement graph data and evaluation graph data and they can be output.

[0120] In the above-described embodiment, the facility to be secured is an office on the third floor of a building, but this is not limiting. A security system can be constructed in the same manner for each floor of a high-rise building. In this case, it is also possible to regard parts such as stairs, elevators, and escalators as edges and process them accordingly. Furthermore, a window on a high floor of a high-rise building that cannot be opened or closed may be recognized as an edge, but it is also possible to mark the intrusion possibility as "no" and not treat it as an intrusion-possible edge.

[0121] [others] As can be seen from the above description of the embodiment, the function of the claimed acceptance means is realized in the design device 1 of the embodiment by the connection terminal 105T to which the image reader is connected, the external I / F 105, the operation unit 104 that inputs instructions to the graphics software, and the control unit 102. Also, the claimed setting means is realized by the operation unit 104 and control unit 102 of the design device 1, and the functions of the claimed node list conversion means and edge list conversion means are realized by the list data conversion unit 121 of the design device 1.

[0122] Furthermore, the function of the claimed generation means is realized by the graph data generation unit 122 of the design device 1, and the claimed placement processing means is realized by the sensor placement processing unit 123 of the design device 1. Furthermore, the function of the claimed evaluation means is realized by the graph evaluation unit 124 of the design device 1, and the function of the claimed output means is realized mainly by the result output unit 125 of the design device 1. Furthermore, the function of the claimed change processing means is realized by the operation unit 104, control unit 102, and sensor placement processing unit 103 working together.

[0123] Furthermore, the functions of the list data conversion unit 121, graph data generation unit 122, sensor placement processing unit 124, and result output unit 125 of the design device 1 can also be realized as functions of the control unit 102 by a program executed by the control unit 102. That is, a program that executes the processing of the flowchart shown in Fig. 14 provides an embodiment of a security system design program according to the present invention. Furthermore, a method that executes the processing of the flowchart shown in Fig. 14 provides an embodiment of a security system design method according to the present invention. [Explanation of symbols]

[0124] 1...security system design device (design device), 101T...connection end, 101...communication I / F, 102...control unit, 103...storage device, 104...operation unit, 105...external I / F, 105T...connection end, 106...display controller, 107...display, 111...floor plan data file, 112...input list file, 113...basic graph data file, 114...sensor placement graph data file, 115...evaluation graph data file, 121...list data conversion unit, 122...graph data generation unit, 123...sensor placement processing unit, 124...graph evaluation unit, 125...result output unit, 2...image reader

Claims

1. a receiving means for receiving input of floor plan data of a facility to be secured; a setting means for setting a target position for the floor plan data in response to an instruction input; a node list conversion means for creating a node list based on the floor plan data, in which the target location is defined as a target node, areas inside and outside the facility to be guarded are defined as nodes, and necessary information is associated with each of the nodes; an edge list conversion means for creating an edge list in which, when a means for enabling people to move between adjacent nodes is provided based on the floor plan data and the node list, the means is used as an edge and necessary information is associated with adjacent nodes for each edge; a generating means for generating graph data based on the node list and the edge list; a placement processing means for setting the placement positions and machine types of security machines in the graph data in accordance with predetermined standards and generating placement graph data; evaluation means for calculating a total score of the security machines set from the target node to each terminal node based on the placement graph data and predetermined scores for the security machines; an output means for outputting an evaluation result including the total value calculated by the evaluation means; A security system design device comprising:

2. The security system design device according to claim 1, The areas inside and outside the security facility that become the nodes are an area separated by an inner wall of the security facility and an area outside the security facility that is adjacent to the area inside the security facility and connected to the area by the edge, The edge is a door or window A security system design device characterized by:

3. The security system design device according to claim 1, The necessary information for the node is information indicating whether it is a target node, an indoor node, or an outdoor node, and parameter information, and the necessary information for the edge is information indicating whether it is a door or a window, and information indicating an adjacent node. A security system design device characterized by:

4. The security system design device according to claim 3, In the node list, the parameter information is information indicating an alert level in the case of an indoor node, and information indicating an outdoor condition in the case of an outdoor node. A security system design device characterized by:

5. The security system design device according to claim 1, A change processing means is provided for performing a change process for the placement of the security machines on the placement graph data formed by the placement processing means in response to a change instruction input. A security system design device characterized by:

6. A security system design method used in a security system design device, comprising: a receiving step of receiving input of floor plan data of the facility to be secured through a receiving means; a setting step in which a setting means sets a target position for the floor plan data in response to an instruction input; a node list conversion step in which a node list conversion means creates a node list based on the floor plan data, in which the target location is defined as a target node and areas inside and outside the guarded facility are defined as nodes, and necessary information is associated with each of the nodes; an edge list conversion step in which, when a means for enabling people to move between adjacent nodes is provided, the edge list conversion means uses the means as an edge and creates an edge list in which necessary information is associated with adjacent nodes for each edge, based on the floor plan data and the node list; a generating step in which a generating means generates graph data based on the node list and the edge list; a placement processing step in which placement processing means sets placement positions and machine types of security machines in accordance with predetermined standards for the graph data and generates placement graph data; an evaluation step in which evaluation means calculates a total score of the security machines set from the target node to each terminal node based on the placement graph data and predetermined scores for the security machines; an output step in which an output means outputs an evaluation result including the total value calculated in the evaluation step; A security system design method comprising:

7. A security system design program executed by a computer installed in a security system design device, a reception step for receiving input of floor plan data of the facility to be secured; a setting step of setting a target position for the floor plan data in response to an instruction input; a node list conversion step of creating a node list based on the floor plan data, in which the target location is defined as a target node, areas inside and outside the facility to be guarded are defined as nodes, and necessary information is associated with each of the nodes; an edge list conversion step for creating an edge list in which, when a means for enabling people to move between adjacent nodes is provided based on the floor plan data and the node list, the means is used as an edge and necessary information is associated with adjacent nodes for each edge; a generating step of generating graph data based on the node list and the edge list; a placement processing step of setting placement positions and machine types of security machines in the graph data according to predetermined criteria and generating placement graph data; an evaluation step of calculating a total score of the security machines set from the target node to each terminal node based on the placement graph data and predetermined scores for the security machines; an output step of outputting an evaluation result including the total value calculated in the evaluation step; A security system design program characterized by executing the above.

Images