JP7808263B2 - Security system design device, security system design method, and security system design program - Google Patents

Description

This invention relates to devices, methods, and programs used when designing security systems (mechanical security systems) that use security devices such as passive sensors and magnetic switches for facilities to be secured, such as office buildings and stores.

In office buildings, stores, and other facilities, security systems using passive sensors and magnetic switches are being installed 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, detecting 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 sensor or magnetic switch, an alarm is sounded or a security company is notified.

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. Traditionally, experienced engineers would take into consideration the layout and budget of the facility to be secured and decide 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 experienced engineers.

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 allows even non-experts to easily obtain security diagnosis information for building a mechanical 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 behavioral trajectory data creation means creates behavioral trajectory data for the intruder by simulating the behavior of the intruder if he or she enters the facility based on the facility data and 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 behavioral trajectory data and security device data. The invention has the following configuration.

Japanese Patent Application Publication No. 7-334779

In the case of the invention disclosed in Patent Document 1, if an intruder enters a facility, the intruder's behavior is simulated based on facility data and security target data, and intruder behavior trajectory data is created. However, the specific method of simulation is not disclosed. Furthermore, while location data for security devices to be installed within the facility is created from the created behavior trajectory data and security device data, the specific algorithm for creating the location data is not disclosed. The method of simulating intruder behavior and the algorithm for creating security device location data are areas that only an expert can handle. The invention disclosed in Patent Document 1 does not clearly and in detail disclose these aspects, and therefore an unskilled person cannot build an appropriate security system for the facility to be guarded.

In light of the above, the objective of this project is to enable 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.

In order to solve the above problem, the security system design device of the invention described in claim 1 comprises:
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;
and an output means for outputting an evaluation result including the total value calculated by the evaluation means.

According to the security system design device described in 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 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 the total score of the security equipment set from the target node to each terminal node, and the evaluation result including this total score is output through the output means.

This invention allows even non-expert engineers to design an appropriate security system that provides sufficient security effectiveness for the facility being guarded.

1 is a block diagram illustrating a configuration example of a security system design device according to an embodiment. FIG. 1 is a diagram for explaining an example of a floor plan. FIG. 10 is a diagram for explaining nodes and edges identified for a security target facility. 10A and 10B are diagrams illustrating an example of a node list and an example of an edge list. FIG. 10 is a diagram illustrating an example of basic graph data. FIG. 10 is a diagram showing an image of a graph created from basic graph data. FIG. 10 is a diagram for explaining an example of sensor arrangement graph data. FIG. 10 is a diagram for explaining an example of a security machine installation criteria list. FIG. 10 is a diagram illustrating an example of sensor data. FIG. 10 is a diagram for explaining an example of evaluation graph data. FIG. 10 is a diagram showing a graph image created from evaluation graph data. FIG. 10 is a diagram for explaining a change in evaluation graph data. 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. 10 is a flowchart illustrating processing performed by the security system design device according to the embodiment.

Embodiments of the device, method, and program according to the present invention will be described below with reference to the figures. This invention can be used when designing a security system for various facilities such as offices, stores, schools, factories, and private homes. However, for simplicity, the following embodiments will use an example in which a security system is designed for an office as the facility to be secured.

[Configuration example of security system design device 1]
FIG. 1 is a block diagram illustrating an example 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 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 that can be sent, 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."

The control unit 102, although not shown, 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 part of the design device 1. The storage device 103 is a device unit consisting of a recording medium such as an SSD (Solid State Drive) and its driver, and records various data to the recording medium, and reads, modifies, and deletes data recorded on the recording medium. In addition to storing and retaining necessary data and programs, the storage device 103 is also used as a working 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 standards list, and sensor data, which will be described later.

The operation unit 104 accepts user input, converts it into electrical signals, and supplies them to the control unit 102. Specifically, it consists of a keyboard, mouse (pointing device), and other components. This allows the control unit 102 to control each component in response to the user's input received through the operation unit 104, thereby executing the desired processing. The connection terminal 105T constitutes a connection terminal for connecting to external devices, and the external I/F (interface) 105 enables data transmission and reception between the external device connected to 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, allowing image data (image data) to be imported via the image reader 2. External devices, such as a printer, can also be connected to the design device 1 via a connection terminal and external I/F (not shown).

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

The floor plan data file 111 stores and holds floor plan data that forms the 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. As will be described in more detail below, 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 these areas (rooms) inside the security facility and connected to these areas by edges. Edges refer to the connections between areas, and more specifically, to the doors and windows that connect nodes to each other.

The basic graph data file 113 stores and holds basic graph data formed based on the node list and edge list in the input list file 112. The basic graph data is information showing the movement route of an intruder within 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 in 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.

The list data conversion unit 121 creates 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 stores these in the input list file 112. The graph data generation unit 122, as will be described in more detail below, generates graph data from the target node, passing 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.

The sensor placement processing unit 123 sets the type and location of security machines to be deployed for the basic graph data stored in the basic graph data file 113, for example, in accordance with a security machine installation standards list (described below) 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 installed. 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.

The graph evaluation unit 124 uses the sensor placement graph data in the sensor placement graph data file 114 to calculate the total score of the security machines set up from the starting node to each terminal node, based on the scores predetermined for the placed security machines. Specifically, the graph evaluation unit 124 determines, from the sensor placement 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 starting 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.

The result output unit 125 creates evaluation result information for output based on the evaluation graph data in the evaluation graph data file 115, and performs processing to display the information on the display 107 via the display controller 106 or print it out via a printer (not shown). The user of the design device 1 references the displayed or printed evaluation result information to identify routes from the target node to each terminal node with total scores lower than a predetermined value and routes with total scores higher than a predetermined value. The total score of the security machines installed for each route is hereinafter referred to as the security score.

For routes where the security score is lower than a predetermined minimum value, the user can replace security machines with ones with higher scores or add security machines to bring the security score above the minimum value. For routes where the security score is higher than a predetermined maximum value, the user can replace security machines with ones with lower scores or remove security machines to bring the security score below the maximum value. This allows even non-expert engineers to design a security system that can provide appropriate mechanical security. The processing performed by the design device 1 of this embodiment will now be described in detail.

[Example of floor plan]
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 guarded in the design device 1. The configuration of the facility to be guarded 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 guarded using a floor plan of the facility to be guarded. 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 guarded (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, etc. The floor plan also identifies the positions of windows and doors, which are means of allowing people to move in and out, so all possible routes (intrusion routes) can be grasped.

Figure 2 is a diagram illustrating an example of a floor plan, such as the floor plan of a company office on the third floor of a building, which is a security facility. Figure 2(A) is an example of a typical floor plan, and Figure 2(A) shows 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 doors 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 provides access to an office inside the office. In Figure 2(A), the left-hand conference room cannot be entered from the entrance, and can only be accessed from the office on the inside.

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 upper left side of the office is the executive office, and employees can access the executive office from the office through the single door. As can be seen in Figure 2(A), the executive office has one window on the top and one on the left side, the office has two windows on the top side, and the left-hand conference room has one window on the left side.

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

However, floor plans are generally created as part of the design drawings when the security facility is designed, and are not used regularly after construction. As such, they may be stored away or lost and become unavailable for immediate use. In such cases, 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.

Figure 2(B) is an example of a floor plan created using, for example, graphics software, and is a floor plan for the same security facility as Figure 2(A). In the floor plan shown in Figure 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 Figure 2(B), created by using graphics 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. As with the floor plan described using Figure 2(A), the floor plan of Figure 2(B) as image data stored in the floor plan data file 111 can be subjected to image recognition to determine the outer edges of the security facility, the layout of internal rooms and sections, the location of windows and doors, and so on.

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 an image reader 2 connected to the connection end 105T and external I/F 105 of the design device 1, or is drawn using the design device 1's image software. 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 end 101T and 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 and retrieve this via the connection end 101T and communication I/F 101 to a specified mail server.

After the floor plan (floor plan data) has been 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.

[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.

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., in 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 target position can be set by the user at any position within the facility to be guarded, but it is desirable to set the target position to a node (room) that is likely to be a target 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 to a node (room) where items to be protected, such as valuables or important documents, are located, and if it is an ordinary residence, the target position can be set to a children's room where children are likely to be present.

The user issues a command to execute the target position setting process via the operation unit 104. In this case, under the control of the control unit 102, the list data conversion unit 121 reads out the floor plan data of the facility to be secured, for which a security system is being 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 secured. In this case, the user operates the operation unit 104 to indicate the target position by writing a specified symbol (for example, an asterisk (*)) at the desired position on the floor plan. This allows the target position to be set in the floor plan (floor plan data) of the facility to be secured.

The list data conversion unit 121 performs image recognition on the floor plan on which the target position is set, recognizing the target position as a target node and recognizing areas inside and outside the guarded facility as nodes. As shown in the element list in Figure 3 (B), nodes refer to distinguishable areas on the floor plan of the guarded facility, and represent rooms and outdoors. More specifically, as described above, nodes are rooms, which are areas separated by walls inside the guarded facility, and areas outside the guarded facility (outdoor areas) that are adjacent to the areas inside the guarded facility (rooms) and connected to them 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.

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 movement that allows people to pass between adjacent nodes, it recognizes that means as an edge. As shown in Figure 3(B), an edge refers to the connection between areas, and more specifically, as described above, refers to a door or 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.

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 Figure 3(A) as an example. As described above, in the floor plan shown in Figure 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 Figure 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.

Next, the list data conversion unit 121 recognizes edges. First, as described above, in this embodiment, the target position (starting node (node 1)) is set for the executive office, and the executive office itself is recognized as node 2. Therefore, since node 1 and node 2 are both inside the executive office, there are no edges between these nodes that represent actual connections such as doors or windows. If this were to remain the case, node 1 would not be connected to any other node, and would therefore not be able to become the target node that serves as the starting point for the graph data described below. Therefore, for convenience, edge 1 is set between node 1 and node 2 as a virtual connection, rather than an actual connection.

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 as 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.

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 is identifiable as edge 5. Similarly, the door connecting the office (node 3) and the entrance (node 5) is recognized as an edge, and is identifiable as edge 6. Furthermore, the door connecting the office (node 3) and the entrance (node 5) is recognized as an edge, and is 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 is identifiable as edge 7. Furthermore, the two windows on the upper side of the office (node 3) are recognized as edges, and are identifiable as edges 8 and 9.

Furthermore, when viewed from the left conference room (node 4), 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), 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), the lower door is recognized as an edge, which can be identified as edge 12.

Furthermore, as mentioned above, nodes are not limited to indoor rooms; areas outside the guarded facility (outdoor areas) that are adjacent to rooms (nodes) inside the facility and connected to those rooms by edges also become nodes. Therefore, as shown in Figure 3(A), the outdoor area connected to node 2, which is an executive office, via edge 3 is recognized as a node, and 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 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 is identifiable as node 9.

Furthermore, the outdoor area connected to node 2, the executive office, via edge 4 is recognized as a node, and 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, and is identifiable as node 11. Finally, the outdoor area connected to node 5, the entrance, via edge 12 is recognized as a node, and is identifiable as node 12. Outdoor nodes are terminal nodes (end nodes) when viewed from the target node (node 1).

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 Figure 3(C), and records them in the input list file 112. As shown in Figure 4(A), the node list consists of a node ID, 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 identifiable 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.

The type of the node list corresponds to the type of node in the parameter list, and is information indicating whether it is a target node, a room (indoor area), or outdoors (outdoor area). The parameters correspond to the parameters of the nodes in the parameter list in Figure 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.

That is, in this embodiment, if the node is a room (indoor area), the parameter for the node is set to an alert level. The alert level indicates the degree of caution required, 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 Figure 4(A), N2 (the executive office) is set to alert level 5, N3 (the office) to alert level 4, and other indoor nodes are set to alert level 3. In this embodiment, the alert level serves as a criterion for determining whether or not to deploy passive sensors. Furthermore, if the node is outdoors (outdoor area), the state (appearance) of the outdoor area is set. Specifically, as shown in Figure 4(A), information indicating whether entry is permitted, the floor (floor), road, balcony, emergency stairs, etc. is set.

In the node list of Figure 4(A), node IDs N1 to N12 correspond to nodes 1 to 12 shown in Figure 3(A). As mentioned above, N1 is the target node and its type is set to "target," while N2 to N6 are of type "room" and have an alert level set as a parameter. 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.

On the other hand, the edge list, as shown in Figure 4(B), consists of an edge ID, type, adjacent node 1, and adjacent node 2. 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. Note that, below, edge 1 will be abbreviated as E1, edge 2 as E2, edge 3 as E3, ...

The type of the edge list corresponds to the type of edge in the parameter list in Figure 3(C) and is indicated as either "none," "door," or "window." The type "none" indicates that the edge is a virtual edge rather than 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.

In the edge list of Figure 4(B), the edge IDs E1 to E12 correspond to edges 1 to 12 shown in Figure 3(A). As mentioned above, E1 is a virtual edge connecting N1 (target node) and N2 (executive office). The type is "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 room) and N10 (outdoors).

In addition, in the edge list of Figure 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 creates a node list (Figure 4(A)) and an edge list (Figure 4(B)) from the floor plan (Figure 3(A)) formed from the floor plan data in the floor plan data file 111, and stores these in the input list file 112.

[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.

Essentially, the path list for the basic graph data is created by starting from the target node, tracing adjacent indoor nodes in the facility under security, and identifying adjacent nodes connected by edges for each node toward the outdoor node, which is the terminal 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). It also overlaps with a previously identified path. The same applies to similar cases below.

Therefore, there is no need to focus on outdoor nodes and identify adjacent nodes and the edges to be taken to reach 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 be taken to reach those adjacent nodes have been identified for an indoor node, identifying the edges to be taken to get from an outdoor node to an adjacent indoor node will result in the direction of identification being reversed. It will also result in overlapping with routes that have already been identified.

Check the contents of the route list according to Figure 5. First, 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.

Next, let's focus on N2 (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 (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). For this reason, as shown in the row for N2 in Figure 5, adjacent nodes are listed in parentheses, with the edges passed through to get to that node, such as "N3 (E2)," "N7 (E3)," and "N10 (E4)." Here, as mentioned above, the path from N2 to N1 is excluded because it runs in the opposite direction to the specified direction and overlaps with the path already identified when focusing on N1.

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-hand conference room), N5 (entrance), N6 (right-hand 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 those nodes are listed in parentheses: "N4 (E5)," "N5 (E6)," "N6 (E7)," "N8 (E8)," and "N9 (E9)." Here, as mentioned above, the route from N3 to N2 is excluded because the specific direction is reversed and it overlaps with the route already identified with a focus on N2.

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, you must pass through E10 (window). For this reason, as shown in the row for N4 in Figure 5, the adjacent node is listed in parentheses, such as "N11 (E10)," and the edge to pass through to get to that node. 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.

Next, we focus on N5 (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 get 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 is listed in parentheses, such as "N12 (E12)," with the edge to be passed through to get to that node. 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. N5 (Entrance) is also adjacent to N6 (Right-side Conference Room). However, the direction from N5 to N6 is excluded because it is the opposite of the specific direction, rather than the direction toward the outdoor node, which is the terminal node. Therefore, this route is understood by focusing on N6 (Right-side Conference Room).

Next, we will 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, you 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)," with the edge to be passed through to get to that node. In the case of this route, the outdoor node N12 is reached 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 the specific direction is reversed and it overlaps with the route already identified by focusing on N3.

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 for indoor nodes. For this reason, in Figure 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 adjacent node. In this way, the graph data generation unit 122 creates basic graph data (Figure 5) from the node list (Figure 4(A)) and edge list (Figure 4(B)) in the input list file 112, and records it in the basic graph data file 113.

Figure 6 shows a graph image created from the basic graph data shown in Figure 5. The graph data shown in Figure 5 is composed of a group of nodes and a group of edges that represent the connections between the nodes. In Figure 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, Figures 5 and 6 show the same content, just in different formats.

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

From N3 (office), there are three routes: one to N4 (left-side conference room) via E5 (door), one to N5 (entrance) via E6 (door), and one to N6 (right-side conference room) via E7 (door). Also, from N6 (right-side 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 further adjacent nodes, and constitute terminal (end) nodes.

There is a route from N4 (left-hand conference room) through E10 (window) to N11 (outside), and there is a route from N5 (entrance) through E12 (door) to N12 (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 surrounded by double circles, are all outdoor nodes and are terminal (end) nodes.

As can be seen from Figure 6, there are six possible routes of intrusion 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 route is from N5 (entrance) through E6 (door) to N3 (office). The other route is from N5 (entrance) through E11 (door), into N6 (right-hand conference room), and then through E7 (door) to N3 (office).

Therefore, from the graph data shown in Figure 5 and the graph image shown in Figure 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 Figure 5 and the basic graph image in Figure 6, all routes starting from N1 (target node) and each outdoor node as the terminal node (terminal node) can be seen. In other words, all routes leading from each outdoor node (N7-N12) to N1 (target node) can be seen.

[Processing of the sensor placement processing unit 123]
The sensor placement processing unit 123 sets the types and locations of security machines to be placed in accordance with predetermined criteria for the basic graph data ( FIG. 5 ), to form sensor placement graph data, which is then stored 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.

First, an example of the installation criteria list in FIG. 8 will be described. The installation criteria list in this embodiment has columns for installation target, installation conditions, and security machine . The installation targets are nodes and edges. Furthermore, the installation conditions are determined based on the type and parameters for nodes, and based on the type for edges. The security machine is information that identifies the security machine to be installed. 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 nodes that are rooms and have an alert level of 5. It is also set that an MG (magnetic switch) is to be installed for edges that are doors or windows.

Note that in Figure 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 the type of nodes and edges and the type of security machines to be installed. It is also possible to add information indicating the installation mode, such as the number of security machines to be installed.

For example, 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 take into account the parameters of outdoor nodes, such as edges connecting outdoor nodes that are balconies or stairs with indoor nodes. 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 PSs (passive sensors) to be installed depending on the alert level, or to use different types of MGs (magnetic switches) for doors and windows.

As mentioned above, the route list column of the basic graph data (Figure 5) lists all routes within the security facility from outdoor nodes to N1 (target node). For this reason, the sensor placement processing unit 123 creates sensor placement graph data using the basic graph data (Figure 5) read from the basic graph data file 113 as base data. That is, the sensor placement graph data is created by performing a process to install security machines on the nodes and edges listed in the route list of the basic graph data (Figure 5). In doing so, the sensor placement processing unit 123 follows the standards of the installation criteria list (Figure 8) and uses the node list (Figure 4(A)) and edge list (Figure 4(B)) as reference data.

The processing performed by the sensor placement processing unit 123 will now be described in detail. First, the sensor placement processing unit 123 refers to the installation criteria list (Figure 8) to determine the installation criteria for security equipment. Next, the sensor placement processing unit 123 refers to the route list for N1 (target node) in the read basic graph data (Figure 5) and configures the installation of security equipment for N2 and E1. In this case, the sensor placement processing unit 123 refers to the node list (Figure 4(A)) for N2 to determine whether it meets the installation criteria. As shown in Figure 4(A), N2 is a room and has an alert level of 5 set as a parameter, so it meets the installation criteria, and a PS (passive sensor) is configured to be installed in N2.

Similarly, the sensor placement processing unit 123 references the edge list (Figure 4(B)) for E1 to determine whether it meets the installation criteria. As shown in Figure 4(B), E1's type is "none," meaning it is a virtually installed edge that is neither a door nor a window, so it does not meet the installation criteria and it can be determined that no security equipment will be installed at E1. As a result, the sensor placement processing unit 123 creates sensor placement graph data in which the route list entry for N1 (target node) is written as "N2[PS]E1," as shown in Figure 7. This indicates that a PS (passive sensor) will be installed at N2, but no security equipment will be installed at E1. In other words, in the entry "N2[PS]E1," entries in brackets, such as [PS], indicate that a PS (passive sensor) or MG (magnetic switch) will be installed for the node or edge immediately preceding it.

In a similar manner, the sensor placement processing unit 123 creates sensor placement graph data for N2. In the row for N2 in Figure 7, settings for 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 from the node list in Figure 4(A), N3, N7, and N10 are all rooms and do not meet the installation criteria of having an alert level of 5, so PSs (passive sensors) will not be installed. As can be seen from the edge list in Figure 4(B), E2, E3, and E4 are all doors or windows, so they meet the installation criteria, and MGs (magnetic switches) will be installed for them.

In a similar manner, the sensor placement processing unit 123 creates sensor placement graph data for N3. In the row for N3 in Figure 7, settings for the installation of security devices are configured, 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 from the node list in Figure 4(A), N4, N5, N6, N8, and N9 are all rooms and do not meet the installation criteria of having an alert level of 5, so no PS (passive sensor) will be installed. As can be seen from the edge list in Figure 4(B), E5, E6, E7, E8, and E9 are all doors or windows, so they meet the installation criteria, and MGs (magnetic switches) will be installed for them.

In a similar manner, the sensor placement processing unit 123 creates sensor placement graph data for N4. In the row for N4 in Figure 7, settings are made regarding the installation of security equipment, as shown as "N11 (E10 (MG))." That is, as can be seen by referring to the node list in Figure 4(A), N11 does not meet the installation criteria of being a room and having an alert level of 5, so a PS (passive sensor) will not be installed. As can be seen by referring to the edge list in Figure 4(B), E10 is a window, so it meets the installation criteria, and an MG (magnetic switch) will be installed for it.

In a similar manner, the sensor placement processing unit 123 creates sensor placement graph data for N5. In the row for N5 in Figure 7, settings are made regarding the installation of security equipment, as shown as "N12 (E12 (MG))." That is, as can be seen by referring to the node list in Figure 4(A), N12 does not meet the installation criteria of being a room and having an alert level of 5, so a PS (passive sensor) will not be installed. As can be seen by referring to the edge list in Figure 4(B), E12 is a door, so it meets the installation criteria, and an MG (magnetic switch) will be installed for it.

In a similar manner, the sensor placement processing unit 123 creates sensor placement graph data for N6. In the row for N6 in Figure 7, settings are made regarding the installation of security equipment, as shown as "N5 (E11 (MG))." That is, as can be seen by referring to the node list in Figure 4(A), N5 does not meet the installation criteria of being a room and having an alert level of 5, so a PS (passive sensor) will not be installed. As can be seen by referring to the edge list in Figure 4(B), E11 is a door, so it meets the installation criteria, and an MG (magnetic switch) will be installed for it.

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

[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 each route from N1 to N7, N8, N9, N10, N11, and N12 based on the sensor placement graph data ( FIG. 7 ) and 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.

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

Therefore, in this embodiment, as shown in Figure 9 (A), two types of security machines are used. 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".

Note that the sensor data shown in Figure 9(A) has a simple configuration in which two types of security machines are used, but the configuration of sensor data is not limited to this. Figure 9(B) is a diagram illustrating another example of sensor data. The sensor data shown in Figure 9(B) has a column for "Installation conditions, etc." In Figure 9(B), the identification information, type, fee, and score are the same as those in the sensor data shown in Figure 9(A). For passive sensors, "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 doors or windows. In the case of the sensor data in Figure 9(B), the sensor placement processing unit 123 can also use this data to identify the installation location and type of security machine.

In this embodiment, for simplicity's sake, the sensor data will be described as having the simple configuration shown in Figure 9(A). Figure 10 is a diagram for explaining an example of evaluation graph data. Figure 11 is a diagram showing a graph image created from the evaluation graph data. As can be seen by comparing the evaluation graph data in Figure 10 with the sensor placement graph data in Figure 7, the evaluation graph data has a column for alert scores, and the rest of the configuration is the same as the sensor placement graph data described using Figure 7.

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 graph image shown in Figure 11 can be created using the information shown in the route list column of the evaluation graph data in Figure 10.

The graph image shown in Figure 11, like the graph image shown 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 shown in Figure 11 also shows what kind of security equipment will be installed at which nodes and edges. 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 at N2 (executive office). There are no other nodes where passive sensors will be installed besides N2 (executive office). 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 at all edges.

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, for the route 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. For the route 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.

Also, for 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, for 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.

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.

Also, 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 Figure 10, the total score of the security machines on the route from N1 to the terminal node is recorded as the security score.

That is, as shown in Figure 11 and also in Figure 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 with the security scores recorded is recorded in the evaluation graph data file 115.

[Processing of the 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.

It is assumed that experience in 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 in 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, the minimum security score is set to 100 and the maximum security score to 200, and this information is pre-recorded in a readable format in a specified memory area of storage device 103, for example.

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 security score totals are 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 security score totals are greater than the maximum value distinguishable by displaying them in reverse or, for example, in red. This allows the user to be notified of routes with insufficient security and routes with excessive security, and the user can, for example, use the operation unit 104 to instruct the removal or addition of security equipment in response to the evaluation results displayed on the display 107.

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 equipment. Then, 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. Then, 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.

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 and edges that are not connected to security equipment. 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 and edges that have removable security equipment installed. Specifically, if a magnetic switch is installed on an edge connecting indoor nodes that do not have an alert level of 5, the result output unit 125 can notify the user that the magnetic switch does not need to be installed on that edge.

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 where 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 security machines are not 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 security machines are not connected, based on sensor data, as long as the total security score does not exceed the maximum value.

The sensor placement correction process will be explained assuming that the evaluation results are displayed on display 107 in the form of a graph image shown in Figure 11. In the case of the evaluation results in the form of a graph image shown in Figure 11, the security scores for the routes leading to N7 and N10 are 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 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 the virtual edge E1.

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.

In this case, the user can determine that they can remove the magnetic switches installed on edges E5, E6, E7, and E11, which connect indoor nodes with a security level other than 5. This is because if magnetic switches are installed on edges connecting outdoor 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.

In this case, as mentioned 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 Figure 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 on E5, E6, E7, and E11 are deleted, the security scores will all be 160, as shown in parentheses near N11 and N12 in Figure 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.

However, in this case, the security scores for 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 for the route to the terminal node is less than the maximum value, and if a node or edge where security equipment can be installed is present based on the sensor data information in Figure 9 (A), security equipment may be deployed at that node or edge.

Figure 12 is a diagram for explaining changes to evaluation graph data. Figure 12 shows an evaluation graph image formed based on the evaluation graph data in the evaluation graph data file 115 after the changes. In Figure 12, to clearly show the difference from the evaluation graph image shown in Figure 11, an x has been 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.

As a result, the security score for the routes leading to the terminal nodes N8, N9, N11, and N12 will be 200, satisfying the condition that the security score must be greater than or equal to 100 and less than or equal to 200. Note that the display of the x marks and information about newly installed passive sensors is for convenience of explanation. However, if you wish to output evaluation graph data or an evaluation graph image showing the changes, you can simply store both the evaluation graph data before the changes and the evaluation graph data after the changes in an evaluation graph data file 115 that makes them distinguishable.

Figure 13 is a diagram for explaining the placement of passive sensors and magnetic switches, which are security devices, in a facility to be guarded according to the changed evaluation graph data. The diagram shown in Figure 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 Figure 13 can be created by the result output unit 125, for example, 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).

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. Furthermore, 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.

[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 the security system design processing via the operation unit 104, the control unit 102 executes the processing shown in Fig. 14.

In response to user input received through the operation unit 104, the control unit 102 accepts floor plan data and executes a process of recording it in the floor plan data file 111 (step S101). Step S101 involves importing the floor plan as image data through the image reader 2, or launching a graphics application to accept drawing input for the floor plan. It is also possible to import floor plans stored on a server on the Internet, or to use floor plan data provided as an attachment to an email and recorded in a storage device.

Next, under the control of the control unit 102, the list data conversion unit 121 begins to function. The list data conversion unit 121 converts the floor plan data in the floor plan data file 111 into a node list (Figure 4(A)) and an edge list (Figure 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 begins to function. The graph data generation unit 122 generates basic graph data (Figure 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).

Then, under the control of the control unit 102, the sensor placement processing unit 123 begins functioning. The sensor placement processing unit 123 creates sensor placement graph data (Figure 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 created sensor placement graph data in the sensor placement graph data file 114.

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

Then, under the control of the control unit 102, the result output unit 125 functions. 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 this (step S106). The evaluation result information can be in the form of a list as shown in FIG. 10 or a graph image as 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.

The control unit 102 then accepts operation input from the user via the operation unit 104 (step S107). The control unit 102 determines whether the accepted operation input is an instruction to terminate (step S108). Assume that the determination process of step S108 determines that the operation input accepted 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 modify 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 process to modify the sensor placement graph data in the sensor placement graph data file 114 in accordance with the operation input from the user (step S109). The control unit 102 then repeats the process from step S105, re-evaluates the security score, and re-outputs the evaluation results, allowing repeated modifications.

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 the specified termination process (step S110), and terminates the process shown in Figure 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 predetermined criteria. This evaluation graph data becomes appropriate design information for the security system.

[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.

[Modification]
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.

Furthermore, in the above-described embodiment, each route is evaluated based on the security score. In addition to this, 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, for example, involve the graph evaluation unit 124 calculating the total price and recording it in the evaluation graph data, and the result output unit 125 outputting the total price.

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 can 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 and graph evaluation unit 124, etc., so that necessary information can be added to the sensor placement graph data and evaluation graph data and output.

In addition, in the above-described embodiment, the facility to be secured is an office on the third floor of a building, but this is not limited to this. A security system can be constructed in the same way for each floor of a high-rise building. In this case, it is also possible to treat parts such as stairs, elevators, and escalators as edges. Furthermore, windows on the upper floors of a high-rise building that cannot be opened or closed may be recognized as edges, but they may not be treated as edges that allow entry, for example, by setting the entry possibility to "no."

[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.

Furthermore, the function of the claimed generation means is realized by the graph data generation unit 122 of the design device 1, and the function of the claimed placement processing means is realized by the sensor placement processing unit 123 of the design device 1. Further, 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. Further, 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.

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. In other words, a program that executes the processing of the flowchart shown in FIG. 14 provides one 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 one embodiment of a security system design method according to the present invention.

1...Security system design device (design device), 101T...Connection terminal, 101...Communication I/F, 102...Control unit, 103...Storage device, 104...Operation unit, 105...External I/F, 105T...Connection terminal, 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 (7)

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;
and an output means for outputting an evaluation result including the total value determined by the evaluation means. 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 security system design device is characterized in that the edges are doors and windows. The security system design device according to claim 1,
The security system design device is characterized in that the necessary information for the nodes is information indicating whether the nodes are target nodes, indoor nodes, or outdoor nodes, and parameter information, and the necessary information for the edges is information indicating whether the nodes are doors or windows, and information indicating adjacent nodes. 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. The security system design device according to claim 1,
a change processing means for performing a process of changing 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 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 determined in the evaluation step. 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 guarded facility 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;
and an output step of outputting an evaluation result including the total value calculated in the evaluation step.