WO2018207469A1 - Abnormality detection system - Google Patents

Abnormality detection system Download PDF

Info

Publication number
WO2018207469A1
WO2018207469A1 PCT/JP2018/010935 JP2018010935W WO2018207469A1 WO 2018207469 A1 WO2018207469 A1 WO 2018207469A1 JP 2018010935 W JP2018010935 W JP 2018010935W WO 2018207469 A1 WO2018207469 A1 WO 2018207469A1
Authority
WO
WIPO (PCT)
Prior art keywords
abnormality
detection system
area
abnormality detection
information
Prior art date
Application number
PCT/JP2018/010935
Other languages
French (fr)
Japanese (ja)
Inventor
健二 今本
小熊 賢司
努 宮内
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Publication of WO2018207469A1 publication Critical patent/WO2018207469A1/en

Links

Images

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B61RAILWAYS
    • B61LGUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L23/00Control, warning, or like safety means along the route or between vehicles or vehicle trains
    • B61L23/04Control, warning, or like safety means along the route or between vehicles or vehicle trains for monitoring the mechanical state of the route
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B61RAILWAYS
    • B61LGUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L25/00Recording or indicating positions or identities of vehicles or vehicle trains or setting of track apparatus
    • B61L25/06Indicating or recording the setting of track apparatus, e.g. of points, of signals
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00Testing or monitoring of control systems or parts thereof
    • G05B23/02Electric testing or monitoring

Definitions

  • the present invention relates to an abnormality detection system.
  • the railway system consists of a lot of on-site equipment installed along the line, such as traffic lights, track circuits, and switchboards.
  • each field device In order to operate the railway safely and smoothly, each field device has high reliability and safety.
  • a malfunctioning system of equipment is provided because malfunctions of field equipment interfere with railway operation.
  • the device abnormality detection system and the field device are connected via a network, and when the device abnormality detection system detects an abnormal operation of the field device, the device is repaired or replaced by maintenance work or the like.
  • each field device When each field device operates abnormally, it can be detected by the device abnormality detection system. On the other hand, if an abnormal event (such as a fire along the line, an earthquake, a power failure, or a ground fault) that affects the behavior of multiple field devices installed within a certain range occurs, the response is further delayed. There is a possibility that it will lead to damage expansion, and there is a case where it is necessary to take an urgent action faster than when an abnormality occurs in a single device. For example, when a ground fault occurs, it is necessary to stop power supply from nearby substations immediately and stop trains traveling in the vicinity. For this reason, it is necessary to specify the presence / absence of an area abnormality along the railway line, the occurrence location, factors, and solution means.
  • an abnormal event such as a fire along the line, an earthquake, a power failure, or a ground fault
  • Patent Document 1 devises a common failure factor detection system that identifies an area where an abnormal event has occurred.
  • the system disclosed in Patent Document 1 is intended to detect the occurrence of a fire or an overflow accident in each area in a nuclear power plant.
  • a plurality of devices are installed in each area, and each device is connected to a common failure factor detection system by a cable.
  • the common failure factor detection system receives device failure signals simultaneously from a plurality of devices installed in the same area, it determines that an area abnormality has occurred in the area.
  • Patent Document 1 a single method (whether device failure signals are simultaneously received from a plurality of devices) is used to determine the occurrence of an area abnormality.
  • the judgment criteria may differ depending on the types of area abnormalities assumed. Therefore, it is necessary to enable determination according to the type of area abnormality assumed.
  • an abnormality detection system includes an apparatus abnormality detection system connected to a plurality of field devices via a network, and an abnormality that affects the behavior of the plurality of field devices.
  • An area abnormality detection system that detects an area abnormality that is an event, a database, and an alarm device are included.
  • the equipment abnormality detection system detects that an abnormality has occurred in the field equipment, it sends the abnormality occurrence information, which is information about the abnormality in the field equipment, to the area abnormality detection system, and the area abnormality detection system receives the received abnormality occurrence information. It is configured to record in the abnormality occurrence history of the database.
  • the area abnormality detection system when the area abnormality detection system receives the abnormality occurrence information of the first field device among the plurality of field devices from the device abnormality detection system, the area abnormality detection system searches the abnormality occurrence history to obtain the first abnormality in the past predetermined time zone. It is determined whether or not an abnormality has occurred in the related equipment of the field device, and if an abnormality has occurred in the related equipment, the user is notified through the alarm device that an area abnormality has occurred.
  • an area abnormality can be detected early and with high accuracy.
  • area abnormality means an abnormal event that affects the behavior of multiple field devices (that is, multiple field devices cause an abnormality), and the device itself. Rather than failure, it means a disaster, such as a fire, earthquake, or ground fault.
  • a plurality of devices that are affected when an area abnormality occurs are not necessarily limited to devices installed at the same point (base), but are devices that are discretely installed within a predetermined range (area). There is also.
  • FIG. 1 is a block diagram showing a configuration of an abnormality detection system according to an embodiment of the present invention. Note that the abnormality detection system described in the present embodiment detects a device abnormality or an area abnormality in a railway system.
  • the abnormality detection system includes a plurality of field devices 101, a device abnormality detection system 301 that detects that an abnormality has occurred in the field device 101, an area abnormality detection system 401 that determines the occurrence of an area abnormality, a related device list, and an abnormality occurrence. It has a database 501 for recording information and an alarm device 601. In FIG. 1, only two field devices 101 are shown, but three or more field devices 101 may exist in the abnormality detection system.
  • Each field device 101 is connected to the device abnormality detection system 301 via the network 201, and the device abnormality detection system 301, the database 501, and the alarm device 601 are connected to the area abnormality detection system 401.
  • the device abnormality detection system 301, the database 501 and the alarm device 601 may be configured to be connected to the area abnormality detection system 401 via the network 201, or as shown in FIG. May be connected to the area abnormality detection system 401 by different transmission lines.
  • the field device 101 is a device used in a railway facility (railway system) such as a traffic light, a track circuit, and a switch.
  • the plurality of field devices 101 may be different types of devices, or may be the same type of devices.
  • each field device 101 may be installed in a geographically different position (Of course, it does not prevent that some field devices 101 are installed in the same position).
  • each field device 101 is configured to be able to communicate with the device abnormality detection system 301 via the network 201.
  • the device abnormality detection system 301 determines whether there is an abnormality in the field device 101 based on information transmitted from the field device 101 via the network 201. When it is detected that an abnormality has occurred in the field device 101, the device abnormality detection system 301 transmits that fact to the area abnormality detection system 401.
  • the area abnormality detection system 401 determines the type of abnormality that has occurred in the railway system based on the information received from the device abnormality detection system 301 and the information recorded in the database 501, and transmits the determination result to the alarm device 601. To do.
  • the area abnormality detection system 401 is a user of the abnormality detection system (this is, for example, an administrator or a worker of the railway system. In the following, it may be simply abbreviated as “user”).
  • Input device such as a keyboard for recording a device list).
  • the alarm device 601 is a device for notifying the operator of the railway system of an alarm indicating that an abnormality in the field device 101 or an area error has occurred, and notifies the operator of an alarm such as a display screen or a speaker. For having an output device.
  • Each of the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 is a computer having at least a CPU (Central Processing Unit) and a memory.
  • a general-purpose computer such as a known personal computer (PC) or server computer is used. It may be a simple computer.
  • the functions of the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 described below are implemented by software (computer program).
  • the CPU of the area abnormality detection system 401 executes a program
  • the area abnormality detection system 401 operates as an apparatus that performs various processes described below.
  • the device abnormality detection system 301 and the alarm device 601 the functions described below are realized by the CPU executing the program.
  • the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 are not necessarily a general-purpose computer such as a PC. As another embodiment, at least one of these (for example, the alarm device 601) may be a terminal device such as a mobile phone. Alternatively, at least one of these may be configured by dedicated hardware. Further, the functions of the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 are not necessarily implemented by software. Some or all of these functions may be implemented by an FPGA (Field Programmable Gate Array) or the like. It may be implemented by hardware such as ASIC (Application Specific Integrated Circuit).
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the database 501 is a storage device (storage means) having a non-volatile storage medium such as a magnetic disk and records information used in the abnormality detection system (related device list and abnormality occurrence information, which will be described later). Details of the information recorded in the database 501 will be described later.
  • the database 501 may be a single magnetic disk, for example.
  • an apparatus such as a file server, or a computer on which data management software such as a database management system (DBMS) is installed may be used as the database 501.
  • DBMS database management system
  • the abnormality detection system may include a plurality of device abnormality detection systems 301 and area abnormality detection systems 401.
  • two or more functions among the functions of the area abnormality detection system 401, the device abnormality detection system 301, the alarm device 601, and the database 501 described below are physically one. It may be realized by a device (PC, server, etc.).
  • all of the functions of the area abnormality detection system 401, the device abnormality detection system 301, the alarm device 601, and the database 501 may be implemented in one PC.
  • an abnormality detection method in this abnormality detection system mainly an area abnormality detection method will be described.
  • an outline of the abnormality detection method and information used for abnormality detection will be described.
  • the equipment abnormality detection system 301 acquires information on the state of the on-site equipment 101 from each on-site equipment 101 via the network 201, and determines whether there is an abnormality in the on-site equipment 101 using the information.
  • the field device 101 transmits information indicating that an abnormality has occurred to the device abnormality detection system 301.
  • this information transmitted from the field device 101 to the device abnormality detection system 301 is referred to as “abnormality occurrence information”.
  • the abnormality occurrence information is sent from the device abnormality detection system 301 to the area abnormality detection system 401 and accumulated in the database 501.
  • the abnormality occurrence information is stored in a kind of table called abnormality occurrence history provided in the database 501.
  • FIG. 2 shows a configuration example of the abnormality occurrence history 3000 and an example of abnormality occurrence information accumulated in the abnormality occurrence history 3000.
  • Information recorded in each line of the abnormality occurrence history 3000 is abnormality occurrence information.
  • the abnormality occurrence information is information including a date and time 3001, a device ID 3002, and contents 3003.
  • the device ID 3002 represents identification information of the field device 101 in which an abnormality has occurred (hereinafter, the identification information of the field device 101 is simply referred to as “device ID”).
  • the date and time 3001 represents the date and time when the abnormality occurred in the field device 101 specified by the device ID 3002, and the content 3003 is information regarding the content of the abnormality that occurred in the field device 101, for example, an error code transmitted from the field device 101. Etc.
  • the area abnormality detection system 401 sorts a plurality of abnormality occurrence information transmitted from the device abnormality detection system 301 based on the date and time 3001 and stores them in the abnormality occurrence history 3000 (for example, the abnormality occurrence information is in chronological order from the oldest date and time). Should be sorted and stored).
  • the area abnormality detection system 401 refers to the received abnormality occurrence information and the abnormality occurrence history 3000 every time the abnormality occurrence information is received from the equipment abnormality detection system 301, so that the abnormality occurrence sent from the field device 101 is generated. It is determined (estimated) whether the information is caused by an area abnormality. In this determination, the area abnormality detection system 401 uses a related device list and a confirmation time list, which will be described later.
  • the related equipment list and confirmation time list must be prepared before the operation of the anomaly detection system starts.
  • the field device 101 that is determined to have an abnormality by the device abnormality detection system 301 is referred to as an “abnormal device”.
  • a field device that is assumed to have the same influence as an abnormal device when an area abnormality occurs is referred to as a “related device”.
  • the user of the anomaly detection system creates a related device list and a confirmation time list required during operation and records them in the database 501.
  • the contents will be described below.
  • the related equipment list is a list of combinations of multiple on-site equipment that are expected to be affected when an area abnormality occurs.
  • FIG. 3 is an example of the related device list 2010 in the present embodiment.
  • an abnormal event to be assumed is selected, and a combination of field devices that are considered to affect the device behavior when the event occurs is specified for each event.
  • Whether or not an abnormal event occurs on site equipment depends on the installation position or installation method of each site equipment. For example, when a fire is assumed as an abnormal event, there is a high possibility that a plurality of field devices installed in the same instrument box will cause the same abnormality.
  • the related device list 2010 is configured to be able to store a combination of on-site devices that are affected for each assumed abnormal event.
  • the related device list 2010 includes a device ID column 2011, an installation position column 2012, and a related device information column 2013 as shown in FIG.
  • the device ID column 2011 stores the identifier of the field device
  • the installation position column 2012 stores information on the position where the field device is installed.
  • the related device information column 2013 includes a plurality of assumed area abnormality columns (2013-1, 2013-2,).
  • the assumed area abnormality column (2013-1, 2013-2,...) Is a column provided for each assumed area abnormality. In the example of FIG.
  • column 2013-1 is a column corresponding to the abnormal event “ground fault”
  • column 2013-2 is This column corresponds to the abnormal event “fire”.
  • the number of assumed area abnormality columns provided in the related device list 2010 is not limited to two.
  • the related device list 2010 may be provided with the same number of assumed abnormal events as the number of assumed abnormal events.
  • the related device (device ID) of the device 001 is “device 002”.
  • the device ID 2011 is “device 002”
  • the related device (device ID) of 002 is “device 003”.
  • FIG. 3 shows an example in which the number of related devices for one field device (for example, “device 001”) is only one, there may be a plurality of related devices for one field device.
  • the anomaly detection system is based on the assumption that when an abnormality occurs in a certain field device 101 (referred to as “device A”) and a related device of device A, there is a high possibility that an area abnormality has occurred. Based on the above, it is determined whether or not an area abnormality has occurred. Therefore, when the abnormality detection system receives the abnormality occurrence information from the device A, the abnormality detection system 3000 searches the abnormality occurrence history 3000 to check whether the abnormality occurrence information transmitted from the related device of the device A is recorded (of course, the related device). (See also list). However, when the abnormality occurrence history 3000 is searched, only a certain range of abnormality occurrence information included therein is searched.
  • abnormality occurrence information abnormality occurrence information having a time difference of a predetermined value or more
  • time difference from the abnormality occurrence date / time of the device A is related to the area abnormality. It is presumed to be information about abnormalities that do not have sex. Therefore, when searching the abnormality occurrence history 3000, the abnormality detection system refers to the date and time (date and time 3001) of the abnormality occurrence information, and the time difference between the date and time 3001 and the abnormality occurrence date and time of the device A is within a predetermined time range. What is necessary is just to search abnormality occurrence information. In this embodiment, this predetermined time range is referred to as “confirmation time”.
  • the user needs to set a confirmation time before starting the operation of the abnormality detection system, but the time until the area abnormality affects each field device may vary depending on the type of area abnormality. Therefore, when the user sets the confirmation time, it is set for each assumed area abnormal event. For example, the confirmation time when the ground fault is assumed as the area abnormality is set to 30 seconds, and when the fire is assumed, the confirmation time is set to 1 hour.
  • the confirmation time for each assumed area abnormal event is recorded in the database 501 as a confirmation time list 2500.
  • FIG. 4 shows an example of the confirmation time list 2500.
  • a confirmation time set for the abnormal event is recorded in the confirmation time list 2500.
  • An assumed event 2501 represents an assumed abnormal event, and a confirmation time set for the assumed abnormal event is recorded in the confirmation time 2502.
  • the assumed event 2501 includes an assumed area abnormality column 2013-1, 2013-2,. . .
  • the same anomalous event that is recorded in is recorded.
  • an upper limit value and a lower limit value of the confirmation time allocated to the assumed abnormal event are recorded. For example, in the example of FIG. 3, “0 second or more and 30 seconds or less” is recorded in the confirmation time 2502 of the row where the assumed event 2501 is “ground fault”. However, at least one of the upper limit value and the lower limit value may be recorded in the confirmation time 2502.
  • the confirmation time is not less than 0 seconds and not more than the upper limit value.
  • the confirmation time is not less than the lower limit value. It means that there is.
  • the anomaly detection system determines whether an area anomaly has occurred by referring to the related device list 2010 and the confirmation time list 2500. For example, in the example of FIG. 3, by referring to the related device list 2010, it is specified that the related device of the device 001 is the device 002 (when the assumed abnormal event is “ground fault”). In the confirmation time list 2500 of FIG. 4, it is recorded that the confirmation time (0 seconds or more) is 30 seconds or less when the type (factor) of the abnormal event (area abnormality) is “ground fault”. .
  • the abnormality detection system determines that a ground fault has occurred.
  • the abnormality detection system can determine that a fire (an area abnormality) has occurred.
  • the data storage format of the related device list and the confirmation time list described here is an example, and information may be stored in a format other than this.
  • information that is, “ ⁇ ” indicating whether each field device is a related device is recorded in the related device list 2010, but each field device is a related device.
  • the confirmation time may be recorded in the related device list 2010.
  • Information other than that shown in FIG. 3 may be recorded in the related device list.
  • the abnormality detection processing is roughly divided into device abnormality detection processing (step 1010), area abnormality determination processing (steps 1020 to 1030), and alarm output processing (step 1040).
  • the device abnormality detection system 301 determines whether a device abnormality has occurred based on information transmitted from the field device 101. Specifically, the field device 101 in which the device abnormality has occurred transmits abnormality occurrence information to the device abnormality detection system 301 via the network 201, and the device abnormality detection system 301 receives this abnormality occurrence information, thereby It is detected that an abnormality has occurred in the device 101 (step 1010).
  • Each field device 101 may transmit abnormality occurrence information to the device abnormality detection system 301 when a desired function is not performed due to a failure of a hardware component in the field device 101 or the like. However, when an operation slightly different from the normal operation is performed, that is, when an indication of a failure appears, the abnormality occurrence information may be transmitted to the device abnormality detection system 301. If the field device 101 is configured to transmit abnormality occurrence information to the device abnormality detection system 301 at the time when a failure sign appears, the abnormality detection system is in an area even if the field device 101 is not broken. It is effective because it can detect abnormalities.
  • each field device when no device abnormality has occurred, each field device periodically transmits normal operation information, and the device abnormality detection system 301 detects an abnormality in the field device 101 when transmission of normal operation information from the field device is interrupted. It may be determined that occurrence has occurred. In this way, even when the field device 101 is in a state where it cannot transmit the abnormality occurrence information (for example, the communication function abnormality of the field device 101, the network disconnection, etc.), the device abnormality detection system 301 is connected to the field device 101. It is possible to detect that an abnormality has occurred.
  • the abnormality detection system 301 is connected to the field device 101. It is possible to detect that an abnormality has occurred.
  • the device abnormality detection system 301 When the device abnormality detection system 301 detects that an abnormality has occurred in the field device 101, the device abnormality detection system 301 transmits the fact to the area abnormality detection system 401.
  • the area abnormality detection system 401 receives information indicating that an abnormality has occurred in the field device 101 from the device abnormality detection system 301, it records the abnormality occurrence information in the field device 101 in the database 501.
  • the device abnormality detection system 301 may use the time when the abnormality occurrence information is received as the abnormality occurrence date and time. In this way, even when the field device does not have a clock device for recognizing the abnormality occurrence date and time, the time when the abnormality has occurred in the field device can be recorded in the database 501.
  • the area abnormality detection system 401 is based on information recorded in the database 501 (related device list, past abnormality occurrence information), and area abnormality determination results (the presence / absence of area abnormality, occurrence location, generation factor, etc.) Is transmitted to the alarm device 601.
  • the area abnormality detection system 401 searches the abnormality occurrence history 3000, and abnormality information of other field devices 101 (field devices other than the abnormality devices) within a period specified by the confirmation time recorded in the confirmation time list 2500. Is recorded (step 1020).
  • a different time range may be recorded for each possible area abnormality. For this reason, when a plurality of different confirmation times are recorded in the confirmation time list 2500, the area abnormality detection system 401 records abnormality information of field devices other than abnormal devices for a plurality of time ranges (confirmation times).
  • Check the confirmation time list 2500.
  • the area abnormality detection system 401 detects abnormality information based on the contents of the related device list 2010 and the confirmation time list 2500 recorded in the database 501. It is confirmed whether or not the recorded field device 101 is related to an abnormal device (step 1021).
  • the device ID of the abnormal device that is, the field device 101 determined to have an abnormality in step 1010 is “device 002”, and is included in the abnormality occurrence date and time of the device 002 (that is, the abnormality occurrence information transmitted from the device 002).
  • the case where the abnormality occurrence date and time) is “January 1, 2017 4:30” is assumed.
  • the abnormality occurrence history 3000 records that an abnormality occurred in the device 003 at 3:25 on January 1, 2017 (that is, in the device 003 at least one hour before the abnormality occurred in the device 002. An abnormality has occurred).
  • the confirmation time list 2500, and the abnormality occurrence history 3000 are those shown in FIGS. 3 and 2, respectively, in step 1020. It was detected that an abnormality occurred on site equipment 101 (equipment 003) other than the anomalous equipment (equipment 002) within 1 hour before 4:30 or within 30 seconds from 4:30 on January 1, 2017. In step 1021, the device 003 is determined to be a device related to the abnormal device (device 002).
  • the area abnormality detection system 401 searches the abnormality occurrence history 3000, and an abnormality of the related device occurs within a predetermined past period (within a confirmation time). However, if it is confirmed that there is no area abnormality with respect to the related device of the field device 101 (that is, the abnormal device) where the abnormality has occurred due to maintenance work, on-site confirmation, etc., the device of the related device Abnormal information may be excluded from the search target. For example, when an operator of the railway system confirms that there is no area abnormality with respect to the related equipment of the abnormal equipment by on-site confirmation or the like, that fact is registered in the database 501.
  • step 1020 or step 1021 even if there is a record in the abnormality occurrence history 3000 that a device abnormality has occurred with respect to the device related to the abnormal device, the area abnormality detection system 401 does not determine that an area abnormality has occurred. It is good to do so.
  • the area abnormality detection system 401 determines that an area abnormality has occurred, and an alarm device 601 indicates that the area abnormality has occurred. (Step 1022).
  • the area abnormality detection system 401 records the abnormality occurrence information received from the device abnormality detection system 301 in the abnormality occurrence history 3000 of the database 501.
  • the area abnormality detection system 401 may also record the area abnormality determination result in the database 501.
  • the area abnormality detection system 401 estimates the type (occurrence factor) of the area abnormality and the location where the abnormality has occurred, and notifies the alarm device 601 of the information as well. .
  • the area abnormality detection system 401 may record information notified to the alarm device 601 in the database 501. The contents notified to the alarm device 601 will be described later.
  • step 1020 when there is no abnormality record of the related device within the confirmation time (step 1020: No, or step 1021: No), it is determined that the device has failed, and the alarm device 601 is notified that the device has failed (step). 1030). Similar to step 1022, in step 1030, the area abnormality detection system 401 records the received abnormality occurrence information in the abnormality occurrence history 3000.
  • the alarm device 601 presents an alarm regarding abnormality occurrence information and area abnormality determination results to the user (step 1040).
  • FIG. 6 is an example of an alarm screen 6010 that the alarm device 601 presents to the user.
  • the area abnormality detection system 401 estimates whether an abnormality is a single device failure (single device abnormality) or an area abnormality, and in the case of an area abnormality, the type of area abnormality (cause of occurrence) and the location where the abnormality occurred. And the alarm device 601 is notified of the information.
  • the alarm device 601 creates an alarm screen as shown in FIG. 6 based on the information received from the area abnormality detection system 401 and presents it to the user. In the example of FIG.
  • Area abnormality is displayed in bold with an underline as an abnormality type
  • “Ground fault” is displayed in bold with an underline as an occurrence factor (estimation factor)
  • “Route X Kapprox X neighborhood” is displayed in bold with an underline. This indicates that the anomaly that occurred is an area anomaly, the cause (estimated factor) was a ground fault, and the location where the anomaly occurred was “around line X km X”. Further, as shown in FIG. 6, other information may be displayed on the alarm screen.
  • an example of an area abnormality occurrence factor and an estimation method of an abnormality occurrence location will be outlined.
  • the field device 101 (abnormal device) determined to have an abnormality in step 1010 is “device 001”, and is determined to be a related device of the abnormal device (device 001) in step 1021.
  • a case where the field device 101 is “device 002” will be described as an example.
  • the area abnormality detection system 401 estimates that the position recorded in the installation position column 2012 of the abnormal device (device 001) and the related device (device 002) described in the related device list 2010 is an abnormality occurrence location. This may be notified to the alarm device 601.
  • the area abnormality detection system 401 is also associated with the devices 001 and 002 recorded in the related device list 2010 (this related device may be a field device that has not yet output abnormality occurrence information).
  • the position recorded in the installation position column 2012 may be extracted, and this may be notified to the alarm device 601 as a range that may be affected by an area abnormality.
  • the area abnormality detection system 401 is assumed to be an abnormal event (an abnormal event described in an assumed area abnormal column (2013-1, 2013-2,...) In the related device list 2010.
  • the alarm device 601 may be notified of the occurrence of an area abnormality as “ground fault” or “fire”.
  • the area abnormality detection system 401 may estimate the cause of the area abnormality based on the abnormality content (content of abnormality occurrence information) received from the field device 101.
  • the area abnormality detection system 401 may notify the alarm device 601 of a plurality of events (factors) as possible events.
  • the area abnormality detection system 401 may notify the estimated occurrence probability of each event as shown in FIG.
  • the alarm device 601 may present work contents for responding to the detected abnormal event to the user. Further, when the area abnormality detection system 401 notifies the alarm device 601 of the estimated occurrence probability of each event, the alarm device 601 may perform processing such as not outputting an event with an estimated occurrence probability equal to or less than a predetermined probability. good.
  • the abnormality detection system according to the present embodiment can notify the user that an abnormality of the field device 101 or an area abnormality has occurred by repeatedly performing the process of FIG.
  • the confirmation time is determined for each assumed area abnormality. Therefore, when the abnormality detection system identifies the cause of the abnormality by executing the processing of FIG. 5, the determination processing (steps 1020, 1021, etc.) of FIG. 5 is performed using the same confirmation time regardless of the type of the abnormal device. .
  • a different confirmation time may be set for each field device (related device). For example, a field device with a higher failure rate has a higher probability of accidental breakage at the same timing as another field device, and therefore, an operation in which the confirmation time is set short can be considered.
  • the abnormal device is the device 001 and the assumed area abnormality type is “ground fault”
  • the related devices of the device 001 are the devices 002 and 004, but the failure rate of the device 002 is the failure of the device 004. Assume that the rate is higher than the rate.
  • the abnormality detection system may be configured so that the confirmation time can be set such that the confirmation time of the device 002 with respect to the device 001 is 20 seconds or less and the confirmation time of the device 004 with respect to the device 001 is 30 seconds or less.
  • the confirmation time is set in this way, even if the device 002 has an abnormality 25 seconds before the device 001 has an abnormality, the abnormality detection system has detected that an area abnormality (ground fault) has occurred. Do not judge. However, if an abnormality of the device 004 occurs 25 seconds before the abnormality of the device 001 occurs, the abnormality detection system determines that an area abnormality (ground fault) has occurred. As described above, since the confirmation time may vary depending on the type of area abnormality, the confirmation time set for each field device can be set to a different value for each type of area abnormality.
  • Each failure rate may be updated at any time based on observation data during operation. Further, a failure rate that assumes a failure rate change (bathtub curve) with the passage of time, taking into account the device installation time and maintenance execution time, may be used.
  • the confirmation time may be determined in consideration of the number of related field devices.
  • the anomaly detection system may issue different types of alarms based on the difference in the date and time of occurrence of anomalies between a plurality of field devices (abnormal equipment and related equipment) (hereinafter referred to as “abnormality occurrence time difference”). As the abnormality occurrence time difference is shorter, it can be determined that each device abnormality is less likely to be an accidental event, so it is possible to issue an alarm accordingly.
  • the abnormality detection system determines that an area abnormality has occurred, if the abnormality occurrence time difference between the abnormal device and the related device is 1/10 or less of the upper limit of the confirmation time, a special alarm is output and the abnormality occurrence time difference is An alarm may be output if it is less than or equal to 1/2 of the upper limit value of the confirmation time, and a warning may be output if the difference in abnormality occurrence time is more than that.
  • the confirmation time assigned to a certain area abnormality is 360 seconds or less
  • the abnormality detection system outputs a special alarm if the abnormality occurrence time difference is within 36 seconds, and alarms within 180 seconds. May be output and a warning message may be issued within 360 seconds.
  • This alarm output may be performed regardless of whether or not an area abnormality has occurred. That is, even if an abnormality has occurred in the two field devices, the area abnormality detection system 401 (or the alarm device 601) does not detect that an area abnormality has occurred.
  • the alarm device 601 may output an alarm corresponding to the determined difference by determining the difference in occurrence date and time.
  • the abnormality detection system may estimate the cause of area abnormality based on the abnormality occurrence time difference. For example, when the difference in abnormality occurrence time between the abnormal device and the related device is very small (within several seconds or the like), there is a high possibility that an area abnormality such as a ground fault has occurred in a short time, which affects many field devices. On the other hand, when the abnormality occurrence time difference is large (several minutes to several tens of minutes), there is a high possibility that an area abnormality such as a fire or flooding takes some time to affect multiple devices. Thus, when there is a correlation between the abnormality occurrence time difference between the abnormal device and the related device and the area abnormality, it is effective to estimate the cause of the area abnormality based on the abnormality occurrence time difference.
  • the abnormality detection system may estimate the cause of the area abnormality in consideration of the installation position of each field device 101.
  • a plurality of (for example, four) field devices (hereinafter referred to as device A, device B, device C, and device D) are connected to device A, device B, device C, and device D. Assume that they were installed in order. If an abnormality occurs in the order of device A, device B, device C, and device D, it is highly likely that a physical abnormal event such as a fire or overflow is a factor.
  • the abnormality detection system estimates the cause of the area abnormality
  • information other than the information received from the field device 101 may be used. For example, information related to natural phenomena (rainfall, lightning, intense heat, earthquake, etc.) around the field device 101, geographical information (such as a river nearby), and the like may be used.
  • the anomaly detection system uses information about natural phenomena to estimate the cause of area anomalies, the information actually measured and collected by the anomaly detection system may be used, or prior forecast information such as weather forecasts may be used .
  • the alarm device 601 displays an alarm on the screen
  • the same content may be presented to the user by another means such as sound, lamp lighting, vibration (vibration function of the mobile terminal, etc.).
  • the abnormality detection system 401 may cause an external system to perform control in consideration of the type of area abnormality and the location where the area abnormality has occurred.
  • the abnormality detection system has a configuration in which the area abnormality detection system 401 is connected to a railway operation management system, a railway security system, or a substation system that manages a substation via the network 201, and the operation management system or the railway security system.
  • the train entry to the area may be restricted by notifying the system that an area abnormality has occurred and information on the area where the abnormality has occurred (considered).
  • the area abnormality detection system 401 may notify the substation system that manages the substation of the occurrence of the area abnormality (and information on the area where the abnormality is considered to occur), and may limit power supply to the area.

Abstract

Provided is an abnormality detection system for detecting area abnormality along railroad lines quickly and with a high degree of precision using existing field equipment and an equipment abnormality detection system, comprising: the equipment abnormality detection system connected to a plurality of field equipment via a network; an area abnormality detection system for detecting an area abnormality which is an abnormal event affecting behaviors of the plurality of field equipment; a database; and an alarm device. The equipment abnormality detection system, upon detecting the occurrence of an abnormality in field equipment, transmits information regarding the occurrence of the abnormality to the area abnormality detection system, and the area abnormality detection system records the received abnormality occurrence information in an abnormality occurrence log in the database. Also, when abnormality occurrence information pertaining to a first field equipment among the plurality of field equipment is received from the equipment abnormality detection system, the area abnormality detection system determines whether an abnormality occurred in equipment related to the first field equipment during a prescribed past time period by searching the abnormality occurrence log, and reports the occurrence of an area abnormality via the alarm device if any such occurrence is found.

Description

異常検出システムAnomaly detection system
 本発明は、異常検出システムに関する。 The present invention relates to an abnormality detection system.
 鉄道システムは、信号機や軌道回路、転てつ器等、沿線に多数設置される現場機器から構成されている。鉄道を安全かつ円滑に運行するため、各現場機器は高い信頼性と安全性を備える。現場機器の不具合は鉄道運行へ支障をきたすため、各機器の動作状態を常時確認することで故障や異常を検出する機器異常検出システムが設けられている。機器異常検出システムと現場機器はネットワークで接続されており、機器異常検出システムが現場機器の異常動作を検出した場合、保守作業等により当該機器の補修や置換えが実施される。 The railway system consists of a lot of on-site equipment installed along the line, such as traffic lights, track circuits, and switchboards. In order to operate the railway safely and smoothly, each field device has high reliability and safety. In order to detect malfunctions and abnormalities by always checking the operating state of each equipment, a malfunctioning system of equipment is provided because malfunctions of field equipment interfere with railway operation. The device abnormality detection system and the field device are connected via a network, and when the device abnormality detection system detects an abnormal operation of the field device, the device is repaired or replaced by maintenance work or the like.
 各現場機器単体が異常動作した場合は機器異常検出システムで検知する事が可能である。一方、ある一定範囲内に設置された複数の現場機器の挙動に影響が及ぶような異常事象(沿線火災、地震、電源異常、地絡発生等)が発生した場合、対応が遅れることで更なる被害拡大へ繋がる可能性があり、機器単体の異常発生時よりも早急な対応が必要となる場合がある。例えば地絡が発生した場合、早急に周辺変電所からの給電を停止し、近隣を走行する列車を停止させる必要がある。そのため、鉄道沿線におけるエリア異常有無や発生場所、要因、解決手段を特定する事が必要となる。しかし鉄道沿線は非常に広範囲に渡るため、エリア異常用に新たな検出用センサを導入する場合、センサ設置や運用に掛かるコストが膨大となる。以下の説明では、ある一定範囲内に設置された複数現場機器の挙動に影響が及ぶような異常事象を「エリア異常」と呼び、その影響範囲を「エリア」と呼ぶ。 各 When each field device operates abnormally, it can be detected by the device abnormality detection system. On the other hand, if an abnormal event (such as a fire along the line, an earthquake, a power failure, or a ground fault) that affects the behavior of multiple field devices installed within a certain range occurs, the response is further delayed. There is a possibility that it will lead to damage expansion, and there is a case where it is necessary to take an urgent action faster than when an abnormality occurs in a single device. For example, when a ground fault occurs, it is necessary to stop power supply from nearby substations immediately and stop trains traveling in the vicinity. For this reason, it is necessary to specify the presence / absence of an area abnormality along the railway line, the occurrence location, factors, and solution means. However, since the railway line extends over a very wide area, when a new detection sensor is introduced for an area abnormality, the cost for installing and operating the sensor becomes enormous. In the following description, an abnormal event that affects the behavior of a plurality of field devices installed within a certain range is referred to as “area abnormality”, and the influence range is referred to as “area”.
 たとえば特許文献1には、異常事象が発生したエリアを特定する共通故障要因検知システムが考案されている。特許文献1に開示されているシステムは、原子力プラント内の各エリアにおける火災や溢水事故の発生を検出する事を目的とする。各エリアには複数機器が設置されており、各機器は共通故障要因検知システムとケーブルで接続されている。共通故障要因検知システムは、同一エリアに設置された複数機器から機器故障信号を同時に受け取った場合、当該エリアでエリア異常が発生したと判定する。 For example, Patent Document 1 devises a common failure factor detection system that identifies an area where an abnormal event has occurred. The system disclosed in Patent Document 1 is intended to detect the occurrence of a fire or an overflow accident in each area in a nuclear power plant. A plurality of devices are installed in each area, and each device is connected to a common failure factor detection system by a cable. When the common failure factor detection system receives device failure signals simultaneously from a plurality of devices installed in the same area, it determines that an area abnormality has occurred in the area.
特開2015-228051号公報Japanese Patent Laying-Open No. 2015-228051
 特許文献1に開示の技術では、エリア異常の発生の判定に単一の手法(複数機器から機器故障信号を同時に受け取ったか否か)が用いられる。しかしエリア異常として想定される異常事象が複数ある場合、想定されるエリア異常の種類によって判断基準は異なり得る。よって、想定されるエリア異常の種類に応じた判定を可能にする必要がある。 In the technique disclosed in Patent Document 1, a single method (whether device failure signals are simultaneously received from a plurality of devices) is used to determine the occurrence of an area abnormality. However, when there are a plurality of abnormal events assumed as area abnormalities, the judgment criteria may differ depending on the types of area abnormalities assumed. Therefore, it is necessary to enable determination according to the type of area abnormality assumed.
 上記課題を解決するために、本発明の一実施形態に係る異常検出システムは、複数の現場機器とネットワークを介して接続された機器異常検出システムと、複数の現場機器の挙動に影響を及ぼす異常事象であるエリア異常の検出を行う、エリア異常検出システムと、データベースと、警報装置と、を有する。機器異常検出システムは、現場機器に異常が発生したことを検出すると、現場機器の異常についての情報である異常発生情報をエリア異常検出システムに送信し、エリア異常検出システムは受信した異常発生情報を、データベースの異常発生履歴に記録するよう構成されている。エリア異常検出システムはまた、複数の現場機器のうち第1の現場機器の異常発生情報を機器異常検出システムから受信すると、異常発生履歴を検索することで、過去の所定の時間帯に第1の現場機器の関連機器に異常が発生したか判定し、関連機器に異常が発生していた場合、警報装置を介して、ユーザにエリア異常が発生した旨を通知する。 In order to solve the above problems, an abnormality detection system according to an embodiment of the present invention includes an apparatus abnormality detection system connected to a plurality of field devices via a network, and an abnormality that affects the behavior of the plurality of field devices. An area abnormality detection system that detects an area abnormality that is an event, a database, and an alarm device are included. When the equipment abnormality detection system detects that an abnormality has occurred in the field equipment, it sends the abnormality occurrence information, which is information about the abnormality in the field equipment, to the area abnormality detection system, and the area abnormality detection system receives the received abnormality occurrence information. It is configured to record in the abnormality occurrence history of the database. In addition, when the area abnormality detection system receives the abnormality occurrence information of the first field device among the plurality of field devices from the device abnormality detection system, the area abnormality detection system searches the abnormality occurrence history to obtain the first abnormality in the past predetermined time zone. It is determined whether or not an abnormality has occurred in the related equipment of the field device, and if an abnormality has occurred in the related equipment, the user is notified through the alarm device that an area abnormality has occurred.
 本発明によれば、エリア異常を早期かつ高精度に検出できる。 According to the present invention, an area abnormality can be detected early and with high accuracy.
本発明の一実施形態に係る異常検出システムの構成図である。It is a block diagram of the abnormality detection system which concerns on one Embodiment of this invention. 異常発生履歴の例である。It is an example of abnormality occurrence history. 関連機器リストの例である。It is an example of a related equipment list. 確認時間リストの例である。It is an example of a confirmation time list. 異常検出処理の流れ図である。It is a flowchart of an abnormality detection process. 警報画面の例である。It is an example of an alarm screen.
 以下、本発明の実施例を図面を参照しながら説明する。なお、先にも述べたが、以下の説明において「エリア異常」とは、複数現場機器の挙動に影響を及ぼす(つまり複数の現場機器が異常をきたす)異常事象のことを意味し、機器そのものの故障というよりはむしろ、たとえば火災、地震、または地絡などの、災害を意味する。エリア異常が発生した時に影響を受ける複数の機器は、必ずしも同一地点(拠点)に設置されている機器には限定されず、所定の範囲(エリア)内に離散的に設置された機器であることもある。 Hereinafter, embodiments of the present invention will be described with reference to the drawings. As described above, in the following description, “area abnormality” means an abnormal event that affects the behavior of multiple field devices (that is, multiple field devices cause an abnormality), and the device itself. Rather than failure, it means a disaster, such as a fire, earthquake, or ground fault. A plurality of devices that are affected when an area abnormality occurs are not necessarily limited to devices installed at the same point (base), but are devices that are discretely installed within a predetermined range (area). There is also.
 図1は、本発明の一実施例に係る異常検出システムの構成を示すブロック図である。なお、本実施例で説明する異常検出システムは、鉄道システムにおいて機器の異常やエリア異常を検出するものとする。 FIG. 1 is a block diagram showing a configuration of an abnormality detection system according to an embodiment of the present invention. Note that the abnormality detection system described in the present embodiment detects a device abnormality or an area abnormality in a railway system.
 異常検出システムは、複数の現場機器101と、現場機器101で異常が発生したことを検出する機器異常検出システム301と、エリア異常発生を判定するエリア異常検出システム401と、関連機器リストおよび異常発生情報を記録するデータベース501と、警報装置601を有する。なお、図1では2つの現場機器101だけが示されているが、異常検出システム内に現場機器101が3つ以上存在していてもよい。 The abnormality detection system includes a plurality of field devices 101, a device abnormality detection system 301 that detects that an abnormality has occurred in the field device 101, an area abnormality detection system 401 that determines the occurrence of an area abnormality, a related device list, and an abnormality occurrence. It has a database 501 for recording information and an alarm device 601. In FIG. 1, only two field devices 101 are shown, but three or more field devices 101 may exist in the abnormality detection system.
 各現場機器101は、ネットワーク201を介して機器異常検出システム301と接続されており、またエリア異常検出システム401には、機器異常検出システム301とデータベース501と警報装置601が接続されている。機器異常検出システム301とデータベース501と警報装置601は、ネットワーク201を介してエリア異常検出システム401に接続されるように構成されていてもよいし、あるいは図1に示されるように、ネットワーク201とは異なる伝送線でエリア異常検出システム401に接続されていてもよい。 Each field device 101 is connected to the device abnormality detection system 301 via the network 201, and the device abnormality detection system 301, the database 501, and the alarm device 601 are connected to the area abnormality detection system 401. The device abnormality detection system 301, the database 501 and the alarm device 601 may be configured to be connected to the area abnormality detection system 401 via the network 201, or as shown in FIG. May be connected to the area abnormality detection system 401 by different transmission lines.
 現場機器101はたとえば、信号機、軌道回路、転てつ器等の、鉄道施設(鉄道システム)で用いられる機器である。なお、複数の現場機器101はそれぞれ異なる種類の機器であってもよいし、同じ種類の機器であってもよい。また各現場機器101は、地理的に異なる位置に設置されていてよい(もちろん一部の現場機器101が同じ位置に設置されていることを妨げるものではない)。 The field device 101 is a device used in a railway facility (railway system) such as a traffic light, a track circuit, and a switch. The plurality of field devices 101 may be different types of devices, or may be the same type of devices. Moreover, each field device 101 may be installed in a geographically different position (Of course, it does not prevent that some field devices 101 are installed in the same position).
 本実施例において、各現場機器101はネットワーク201を介して機器異常検出システム301と通信可能に構成されている。機器異常検出システム301は現場機器101からネットワーク201経由で送信されてくる情報をもとに、現場機器101の異常の有無を判定する。現場機器101に異常が発生したことを検知すると、機器異常検出システム301はその旨をエリア異常検出システム401に送信する。 In this embodiment, each field device 101 is configured to be able to communicate with the device abnormality detection system 301 via the network 201. The device abnormality detection system 301 determines whether there is an abnormality in the field device 101 based on information transmitted from the field device 101 via the network 201. When it is detected that an abnormality has occurred in the field device 101, the device abnormality detection system 301 transmits that fact to the area abnormality detection system 401.
 エリア異常検出システム401は、機器異常検出システム301から受領した情報やデータベース501に記録された情報をもとに、鉄道システム内で発生した異常の種類を判定し、判定結果を警報装置601に送信する。またエリア異常検出システム401は、異常検出システムのユーザ(これは例えば鉄道システムの管理者や作業者である。以下では単に「ユーザ」と略記することもある)がデータベース501に情報(後述する関連機器リスト等)を記録するための、キーボードなどの入力デバイスを備えている。 The area abnormality detection system 401 determines the type of abnormality that has occurred in the railway system based on the information received from the device abnormality detection system 301 and the information recorded in the database 501, and transmits the determination result to the alarm device 601. To do. In addition, the area abnormality detection system 401 is a user of the abnormality detection system (this is, for example, an administrator or a worker of the railway system. In the following, it may be simply abbreviated as “user”). Input device such as a keyboard for recording a device list).
 警報装置601は、現場機器101の異常や、エリア異常が発生した旨の警報を、鉄道システムの作業者に通知するための装置であり、ディスプレイ画面やスピーカー等の、作業者に警報を通知するための出力デバイスを有する。 The alarm device 601 is a device for notifying the operator of the railway system of an alarm indicating that an abnormality in the field device 101 or an area error has occurred, and notifies the operator of an alarm such as a display screen or a speaker. For having an output device.
 エリア異常検出システム401、機器異常検出システム301、そして警報装置601はそれぞれ、少なくともCPU(Central Processing Unit)とメモリを有するコンピュータであり、たとえば公知のパーソナルコンピュータ(PC)やサーバコンピュータ等の、汎用的なコンピュータであってよい。そして本実施例では、以下で説明するエリア異常検出システム401、機器異常検出システム301、そして警報装置601の機能は、ソフトウェア(コンピュータプログラム)によって実装されているものとする。たとえばエリア異常検出システム401のCPUがプログラムを実行することにより、エリア異常検出システム401は以下で説明する各種処理を行う装置として動作する。同様に、機器異常検出システム301や警報装置601でも、CPUがプログラムを実行することによって、以下に説明する機能が実現される。 Each of the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 is a computer having at least a CPU (Central Processing Unit) and a memory. For example, a general-purpose computer such as a known personal computer (PC) or server computer is used. It may be a simple computer. In this embodiment, the functions of the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 described below are implemented by software (computer program). For example, when the CPU of the area abnormality detection system 401 executes a program, the area abnormality detection system 401 operates as an apparatus that performs various processes described below. Similarly, in the device abnormality detection system 301 and the alarm device 601, the functions described below are realized by the CPU executing the program.
 ただし、エリア異常検出システム401、機器異常検出システム301、そして警報装置601は必ずしもPC等の汎用的なコンピュータでなくてもよい。別の実施形態として、これらのうち少なくとも1つ(たとえば警報装置601)が、携帯電話などの端末装置であってもよい。あるいはこれらの少なくとも1つが、専用のハードウェアによって構成されていてもよい。また、エリア異常検出システム401、機器異常検出システム301、そして警報装置601の機能が必ずしもソフトウェアによって実装されている必要はなく、これらの機能の一部または全部が、FPGA(Field Programmable Gate Array)やASIC(Application Specific Integrated Circuit)等のハードウェアによって実装されていてもよい。 However, the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 are not necessarily a general-purpose computer such as a PC. As another embodiment, at least one of these (for example, the alarm device 601) may be a terminal device such as a mobile phone. Alternatively, at least one of these may be configured by dedicated hardware. Further, the functions of the area abnormality detection system 401, the device abnormality detection system 301, and the alarm device 601 are not necessarily implemented by software. Some or all of these functions may be implemented by an FPGA (Field Programmable Gate Array) or the like. It may be implemented by hardware such as ASIC (Application Specific Integrated Circuit).
 データベース501は、磁気ディスク等の不揮発性の記憶媒体を有する記憶装置(記憶手段)で、異常検出システムで用いられる情報(後述する、関連機器リストや異常発生情報等)が記録される。データベース501に記録される情報の詳細については後述する。データベース501は、たとえば単体の磁気ディスクでよい。あるいはファイルサーバ等の装置、またはデータベース管理システム(DBMS)等のデータ管理用のソフトウェアが実装されたコンピュータが、データベース501として用いられてもよい。 The database 501 is a storage device (storage means) having a non-volatile storage medium such as a magnetic disk and records information used in the abnormality detection system (related device list and abnormality occurrence information, which will be described later). Details of the information recorded in the database 501 will be described later. The database 501 may be a single magnetic disk, for example. Alternatively, an apparatus such as a file server, or a computer on which data management software such as a database management system (DBMS) is installed may be used as the database 501.
 なお、異常検出システムの信頼性や可用性を確保するため、異常検出システムは、機器異常検出システム301やエリア異常検出システム401のそれぞれを複数台有していてもよい。逆に、システム構成を簡素化するため、たとえば以下で説明するエリア異常検出システム401、機器異常検出システム301、警報装置601、データベース501の機能のうち、2つ以上の機能が物理的に一つの装置(PC、サーバ等)で実現されていてもよい。たとえば1つのPCに、エリア異常検出システム401、機器異常検出システム301、警報装置601、そしてデータベース501の機能の全てが実装されるように構成されていてもよい。 In addition, in order to ensure the reliability and availability of the abnormality detection system, the abnormality detection system may include a plurality of device abnormality detection systems 301 and area abnormality detection systems 401. Conversely, in order to simplify the system configuration, for example, two or more functions among the functions of the area abnormality detection system 401, the device abnormality detection system 301, the alarm device 601, and the database 501 described below are physically one. It may be realized by a device (PC, server, etc.). For example, all of the functions of the area abnormality detection system 401, the device abnormality detection system 301, the alarm device 601, and the database 501 may be implemented in one PC.
 以下では、この異常検出システムにおける異常検出方法、主にエリア異常の検出方法について説明する。まず異常検出方法の概要、及び異常検出で使用される情報について説明する。 In the following, an abnormality detection method in this abnormality detection system, mainly an area abnormality detection method will be described. First, an outline of the abnormality detection method and information used for abnormality detection will be described.
 機器異常検出システム301は各現場機器101から、現場機器101の状態についての情報をネットワーク201経由で取得し、その情報を用いて現場機器101の異常の有無を判定している。現場機器101に異常が発生した場合、現場機器101は異常が発生したことを示す情報を機器異常検出システム301に送信する。本実施例では、現場機器101が機器異常検出システム301に送信するこの情報のことを「異常発生情報」と呼ぶ。異常発生情報は機器異常検出システム301からエリア異常検出システム401に送られ、データベース501に蓄積される。 The equipment abnormality detection system 301 acquires information on the state of the on-site equipment 101 from each on-site equipment 101 via the network 201, and determines whether there is an abnormality in the on-site equipment 101 using the information. When an abnormality occurs in the field device 101, the field device 101 transmits information indicating that an abnormality has occurred to the device abnormality detection system 301. In this embodiment, this information transmitted from the field device 101 to the device abnormality detection system 301 is referred to as “abnormality occurrence information”. The abnormality occurrence information is sent from the device abnormality detection system 301 to the area abnormality detection system 401 and accumulated in the database 501.
 異常発生情報は、データベース501内に設けられる、異常発生履歴と呼ばれる一種のテーブルに格納される。図2に、異常発生履歴3000の構成例と、異常発生履歴3000に蓄積される異常発生情報の例を示す。異常発生履歴3000の各行に記録されている情報が、異常発生情報である。異常発生情報は図2に示されるように、日時3001、機器ID3002、内容3003を含む情報である。機器ID3002は、異常が発生した現場機器101の識別情報を表す(以下では、現場機器101の識別情報のことを単に「機器ID」と呼ぶ)。日時3001は、機器ID3002で特定される現場機器101に異常が発生した日時を表し、内容3003は、現場機器101で発生した異常の内容に関する情報で、例えば現場機器101から送信されてくるエラーコード等である。 The abnormality occurrence information is stored in a kind of table called abnormality occurrence history provided in the database 501. FIG. 2 shows a configuration example of the abnormality occurrence history 3000 and an example of abnormality occurrence information accumulated in the abnormality occurrence history 3000. Information recorded in each line of the abnormality occurrence history 3000 is abnormality occurrence information. As shown in FIG. 2, the abnormality occurrence information is information including a date and time 3001, a device ID 3002, and contents 3003. The device ID 3002 represents identification information of the field device 101 in which an abnormality has occurred (hereinafter, the identification information of the field device 101 is simply referred to as “device ID”). The date and time 3001 represents the date and time when the abnormality occurred in the field device 101 specified by the device ID 3002, and the content 3003 is information regarding the content of the abnormality that occurred in the field device 101, for example, an error code transmitted from the field device 101. Etc.
 エリア異常検出システム401は、機器異常検出システム301から送信されてくる複数の異常発生情報を、日時3001に基づいてソートして、異常発生履歴3000に格納する(たとえば日時の古い順に異常発生情報がソートされて格納されるとよい)。またエリア異常検出システム401は、機器異常検出システム301から異常発生情報を受信する度に、受信した異常発生情報と異常発生履歴3000とを参照することで、現場機器101から送られてきた異常発生情報が、エリア異常に起因するものか判定(推定)する。この判定の際、エリア異常検出システム401は、後述する関連機器リストと確認時間リストを用いる。 The area abnormality detection system 401 sorts a plurality of abnormality occurrence information transmitted from the device abnormality detection system 301 based on the date and time 3001 and stores them in the abnormality occurrence history 3000 (for example, the abnormality occurrence information is in chronological order from the oldest date and time). Should be sorted and stored). In addition, the area abnormality detection system 401 refers to the received abnormality occurrence information and the abnormality occurrence history 3000 every time the abnormality occurrence information is received from the equipment abnormality detection system 301, so that the abnormality occurrence sent from the field device 101 is generated. It is determined (estimated) whether the information is caused by an area abnormality. In this determination, the area abnormality detection system 401 uses a related device list and a confirmation time list, which will be described later.
 続いて、関連機器リストと確認時間リストについて説明する。関連機器リストと確認時間リストは異常検出システムの運用開始前に準備されている必要がある。なお、以下の説明では、機器異常検出システム301によって異常が発生したと判定された現場機器101を「異常機器」と呼ぶ。そして、エリア異常が発生した場合に異常機器と同様の影響が及ぶことが想定される現場機器を「関連機器」と呼ぶ。 Next, the related equipment list and confirmation time list will be described. The related equipment list and confirmation time list must be prepared before the operation of the anomaly detection system starts. In the following description, the field device 101 that is determined to have an abnormality by the device abnormality detection system 301 is referred to as an “abnormal device”. A field device that is assumed to have the same influence as an abnormal device when an area abnormality occurs is referred to as a “related device”.
 運用前に必要となる準備段階において、異常検出システムのユーザは運用時に必要となる関連機器リストと確認時間リストを作成し、データベース501へ記録する。以下、その内容を説明する。 At the preparatory stage required before operation, the user of the anomaly detection system creates a related device list and a confirmation time list required during operation and records them in the database 501. The contents will be described below.
 関連機器リストとは、エリア異常が発生した場合に影響が及ぶと想定される複数の現場機器の組合せをリスト化したものである。図3は、本実施例における関連機器リスト2010の例である。ユーザが関連機器リスト2010を作成する際、想定する異常事象を選定し、当該事象が発生した場合に機器挙動へ影響が及ぶと考えられる現場機器の組合せを事象ごとに特定する。異常事象発生の現場機器への影響の有無は、各現場機器の設置位置または設置方法に依存する。例えば異常事象として火災を想定する場合、同一器具箱内に設置された複数の現場機器が同様の異常を起こす可能性が高い。一方、異常事象として地絡や電源異常を想定した場合、複数の現場機器間の物理的な距離が離れていたとしても、それらの現場機器同士が電気的な干渉関係にある場合は同様の異常を起こす可能性が高いと考えられる。そのため関連機器リスト2010は、影響が及ぶ現場機器の組合せを、想定する異常事象ごとに格納可能に構成されている。 The related equipment list is a list of combinations of multiple on-site equipment that are expected to be affected when an area abnormality occurs. FIG. 3 is an example of the related device list 2010 in the present embodiment. When the user creates the related device list 2010, an abnormal event to be assumed is selected, and a combination of field devices that are considered to affect the device behavior when the event occurs is specified for each event. Whether or not an abnormal event occurs on site equipment depends on the installation position or installation method of each site equipment. For example, when a fire is assumed as an abnormal event, there is a high possibility that a plurality of field devices installed in the same instrument box will cause the same abnormality. On the other hand, if a ground fault or power supply abnormality is assumed as an abnormal event, even if the physical distances between multiple field devices are separated, the same abnormality may occur if the field devices are in an electrical interference relationship with each other. It is thought that there is a high possibility of causing. Therefore, the related device list 2010 is configured to be able to store a combination of on-site devices that are affected for each assumed abnormal event.
 関連機器リスト2010は図3に示す通り、機器IDカラム2011、設置位置カラム2012、関連機器情報カラム2013を有する。関連機器リスト2010の各行には、異常検出システム内の現場機器の情報と、その現場機器の関連機器についての情報が記録されている。機器IDカラム2011には現場機器の識別子が格納され、設置位置カラム2012には、現場機器の設置されている位置の情報が格納される。関連機器情報カラム2013内には、複数の想定エリア異常カラム(2013-1,2013-2,...)が含まれる。想定エリア異常カラム(2013-1,2013-2,...)は、想定されるエリア異常ごとに設けられるカラムである。図3の例では、2つの想定エリア異常カラム(2013-1,2013-2)が示されているが、カラム2013-1は異常事象“地絡”に対応するカラムで、カラム2013-2は異常事象“火災”に対応するカラムである。なお、関連機器リスト2010に設けられる想定エリア異常カラムの数は2に限定されない。関連機器リスト2010には、想定される異常事象の数と同数、想定エリア異常カラムが設けられてよい。 The related device list 2010 includes a device ID column 2011, an installation position column 2012, and a related device information column 2013 as shown in FIG. In each row of the related device list 2010, information on the field device in the abnormality detection system and information on the related device of the field device are recorded. The device ID column 2011 stores the identifier of the field device, and the installation position column 2012 stores information on the position where the field device is installed. The related device information column 2013 includes a plurality of assumed area abnormality columns (2013-1, 2013-2,...). The assumed area abnormality column (2013-1, 2013-2,...) Is a column provided for each assumed area abnormality. In the example of FIG. 3, two assumed area abnormal columns (2013-1, 2013-2) are shown, but column 2013-1 is a column corresponding to the abnormal event “ground fault”, and column 2013-2 is This column corresponds to the abnormal event “fire”. Note that the number of assumed area abnormality columns provided in the related device list 2010 is not limited to two. The related device list 2010 may be provided with the same number of assumed abnormal events as the number of assumed abnormal events.
 想定エリア異常カラム(2013-1,2013-2,...)のそれぞれには、複数の現場機器の機器IDが記述されたカラム(図3におけるカラム2013-11,2013-12,2013-13,...,2013-21,2013-22,2013-23,...)が設けられており、これらのうち“○”の記述されたカラムに対応する現場機器が関連機器であることを表す。図3の例では、機器ID2011が“機器001”の行において、想定エリア異常カラム2013-1に含まれるカラム(2013-11,2013-12,2013-13,...)のうち、カラム2013-12に“○”が記録されている。これは異常事象が地絡の場合、機器001の関連機器(の機器ID)が“機器002”であることを表している。また機器ID2011が“機器002”の行では、想定エリア異常カラム2013-2に含まれるカラムのうち、カラム2013-23に“○”が記録されており、これは異常事象が火災の場合、機器002の関連機器(の機器ID)が“機器003”であることを表している。図3では、1つの現場機器(たとえば“機器001”)に対する関連機器の数が1つだけの例が示されているが、1つの現場機器について、関連機器は複数存在することもある。 In each of the assumed area abnormality columns (2013-1, 2013-2,...), Columns in which device IDs of a plurality of field devices are described (columns 2013-11, 2013-12, 2013-13 in FIG. 3). ,..., 2013-21, 2013-22, 2013-23, etc.), and among these, the on-site equipment corresponding to the column in which “O” is described is a related equipment. To express. In the example of FIG. 3, among the columns (2013-11, 2013-12, 2013-13,...) Included in the assumed area abnormality column 2013-1, in the row where the device ID 2011 is “device 001”, the column 2013 “○” is recorded in -12. This indicates that when the abnormal event is a ground fault, the related device (device ID) of the device 001 is “device 002”. In the row where the device ID 2011 is “device 002”, among the columns included in the assumed area abnormality column 2013-2, “◯” is recorded in the column 2013-23, and this indicates that if the abnormal event is a fire, This indicates that the related device (device ID) of 002 is “device 003”. Although FIG. 3 shows an example in which the number of related devices for one field device (for example, “device 001”) is only one, there may be a plurality of related devices for one field device.
 本実施例に係る異常検出システムは、ある現場機器101(仮にこれを「機器A」と呼ぶ)と、機器Aの関連機器に異常が発生した場合、エリア異常が発生した可能性が高いという前提に基づいて、エリア異常が発生したか否かを判定する。そのため、異常検出システムは機器Aから異常発生情報を受領すると、異常発生履歴3000を検索することで、機器Aの関連機器から送信された異常発生情報が記録されていないか確認する(もちろん関連機器リストも参照する)。ただし、異常発生履歴3000を検索する際、その中に含まれる一定の範囲の異常発生情報だけが検索される。 The anomaly detection system according to the present embodiment is based on the assumption that when an abnormality occurs in a certain field device 101 (referred to as “device A”) and a related device of device A, there is a high possibility that an area abnormality has occurred. Based on the above, it is determined whether or not an area abnormality has occurred. Therefore, when the abnormality detection system receives the abnormality occurrence information from the device A, the abnormality detection system 3000 searches the abnormality occurrence history 3000 to check whether the abnormality occurrence information transmitted from the related device of the device A is recorded (of course, the related device). (See also list). However, when the abnormality occurrence history 3000 is searched, only a certain range of abnormality occurrence information included therein is searched.
 エリア異常が発生したことにより、機器Aに異常が発生してから他の現場機器(関連機器)へもエリア異常の影響が及ぶまでには、一定程度の時間を要することがある。そのため、異常発生履歴3000を検索する際、機器Aの異常発生日時との時間差がある程度以上ある異常発生情報が検索されればよい。また、エリア異常が各現場機器に影響を及ぼす時間は有限である(一定の上限がある)ことが多いと考えられる。それゆえ、異常発生履歴3000内の異常発生情報の中で、機器Aの異常発生日時との時間差があまりに大きい異常発生情報(所定値以上の時間差がある異常発生情報)は、エリア異常との関連性がない異常に関する情報と推定される。したがって、異常発生履歴3000を検索する際、異常検出システムは異常発生情報の日時(日時3001)を参照し、日時3001と機器Aの異常発生日時との時間差が所定の時間範囲内に収まっている異常発生情報を検索すればよい。本実施例では、この所定の時間範囲のことを「確認時間」と呼ぶ。 When an area abnormality occurs, it may take a certain amount of time from the occurrence of an abnormality in device A until the area abnormality affects other field devices (related devices). Therefore, when searching for the abnormality occurrence history 3000, it is only necessary to search for abnormality occurrence information having a time difference with the abnormality occurrence date and time of the device A to some extent. In addition, it is considered that the time during which an area abnormality affects each field device is often finite (there is a certain upper limit). Therefore, in the abnormality occurrence information in the abnormality occurrence history 3000, abnormality occurrence information (abnormality occurrence information having a time difference of a predetermined value or more) whose time difference from the abnormality occurrence date / time of the device A is too large is related to the area abnormality. It is presumed to be information about abnormalities that do not have sex. Therefore, when searching the abnormality occurrence history 3000, the abnormality detection system refers to the date and time (date and time 3001) of the abnormality occurrence information, and the time difference between the date and time 3001 and the abnormality occurrence date and time of the device A is within a predetermined time range. What is necessary is just to search abnormality occurrence information. In this embodiment, this predetermined time range is referred to as “confirmation time”.
 異常検出システムの運用開始前に、ユーザは確認時間を設定する必要があるが、各現場機器にエリア異常の影響が及ぶまでの時間は、エリア異常の種類によって異なり得る。よってユーザが確認時間を設定する際は、想定するエリア異常事象ごとに設定を行う。例えば、エリア異常として地絡を想定した場合の確認時間は30秒、火災を想定した場合は1時間とする等、想定するエリア異常事象ごとに異なる確認時間が設定されると良い。 The user needs to set a confirmation time before starting the operation of the abnormality detection system, but the time until the area abnormality affects each field device may vary depending on the type of area abnormality. Therefore, when the user sets the confirmation time, it is set for each assumed area abnormal event. For example, the confirmation time when the ground fault is assumed as the area abnormality is set to 30 seconds, and when the fire is assumed, the confirmation time is set to 1 hour.
 想定するエリア異常事象ごとの確認時間は、データベース501に確認時間リスト2500として記録される。図4に確認時間リスト2500の例を示す。確認時間リスト2500には、想定される異常事象ごとに、その異常事象に対して設定されている確認時間が記録される。想定事象2501は想定される異常事象を表しており、確認時間2502には、想定される異常事象に対して設定された確認時間が記録される。 The confirmation time for each assumed area abnormal event is recorded in the database 501 as a confirmation time list 2500. FIG. 4 shows an example of the confirmation time list 2500. In the confirmation time list 2500, for each assumed abnormal event, a confirmation time set for the abnormal event is recorded. An assumed event 2501 represents an assumed abnormal event, and a confirmation time set for the assumed abnormal event is recorded in the confirmation time 2502.
 想定事象2501には、関連機器リストの想定エリア異常カラム2013-1,2013-2,...に記録される異常事象と同じものが記録される。確認時間2502には、想定される異常事象に割り当てられている確認時間の上限値及び下限値が記録される。たとえば図3の例では、想定事象2501が“地絡”の行の確認時間2502には“0秒以上30秒以下”が記録されている。ただし、上限値と下限値のうち少なくとも一方のみが確認時間2502に記録されていてもよい。上限値のみが確認時間2502に記録されている場合、確認時間は0秒以上かつその上限値以下であることを表し、下限値のみが記録されている場合には確認時間はその下限値以上であることを意味する。 The assumed event 2501 includes an assumed area abnormality column 2013-1, 2013-2,. . . The same anomalous event that is recorded in is recorded. In the confirmation time 2502, an upper limit value and a lower limit value of the confirmation time allocated to the assumed abnormal event are recorded. For example, in the example of FIG. 3, “0 second or more and 30 seconds or less” is recorded in the confirmation time 2502 of the row where the assumed event 2501 is “ground fault”. However, at least one of the upper limit value and the lower limit value may be recorded in the confirmation time 2502. When only the upper limit value is recorded in the confirmation time 2502, it indicates that the confirmation time is not less than 0 seconds and not more than the upper limit value. When only the lower limit value is recorded, the confirmation time is not less than the lower limit value. It means that there is.
 異常検出システムは、関連機器リスト2010と確認時間リスト2500を参照することで、エリア異常が発生しているかを判定する。たとえば図3の例では、関連機器リスト2010を参照することで、機器001の関連機器は機器002であること(想定される異常事象が“地絡”の場合)が特定される。そして図4の確認時間リスト2500には、異常事象(エリア異常)の種類(要因)が“地絡”の場合には確認時間が(0秒以上)30秒以下であることが記録されている。そのため、たとえば時刻1時10分42秒に機器001に異常が発生した時、その時点(1時10分42秒)から過去30秒以内、つまり時刻1時10分12秒から1時10分42秒の間に、機器002に異常が発生していたならば、異常検出システムは地絡が発生していると判定する。 The anomaly detection system determines whether an area anomaly has occurred by referring to the related device list 2010 and the confirmation time list 2500. For example, in the example of FIG. 3, by referring to the related device list 2010, it is specified that the related device of the device 001 is the device 002 (when the assumed abnormal event is “ground fault”). In the confirmation time list 2500 of FIG. 4, it is recorded that the confirmation time (0 seconds or more) is 30 seconds or less when the type (factor) of the abnormal event (area abnormality) is “ground fault”. . Therefore, for example, when an abnormality occurs in the device 001 at time 1:10:42, within the past 30 seconds from that point (1:10:42), that is, from 1:10:12 to 1:10:42 If an abnormality has occurred in the device 002 during the second, the abnormality detection system determines that a ground fault has occurred.
 また、図3の例では、想定される異常事象が“火災”の場合、機器003の関連機器が機器002であることが、関連機器リスト2010に記録されている。また図4の確認時間リスト2500には、異常事象の種類が“火災”の場合には確認時間が1時間以上であることが記録されているので、機器003に異常が発生した時刻から1時間以上前に機器002に異常が発生していた場合、異常検出システムは火災(というエリア異常)が発生していると判定することができる。 Further, in the example of FIG. 3, when the assumed abnormal event is “fire”, it is recorded in the related device list 2010 that the related device of the device 003 is the device 002. Further, in the confirmation time list 2500 of FIG. 4, when the type of abnormal event is “fire”, it is recorded that the confirmation time is one hour or more, so one hour from the time when the abnormality occurred in the device 003 If an abnormality has occurred in the device 002 before, the abnormality detection system can determine that a fire (an area abnormality) has occurred.
 なお、ここで説明した関連機器リスト及び確認時間リストのデータ格納形式は一例であり、これ以外の形式で情報が格納されていてもよい。たとえば図3の例では、関連機器リスト2010には、各現場機器が関連機器であるか否かを表す情報(つまり“○”)のみが記録されているが、各現場機器が関連機器であるか否かを表す情報に加えて、関連機器リスト2010内に確認時間が記録されるように構成されていてもよい。また図3に示されている以外の情報が関連機器リストに記録されてもよい。 Note that the data storage format of the related device list and the confirmation time list described here is an example, and information may be stored in a format other than this. For example, in the example of FIG. 3, only information (that is, “◯”) indicating whether each field device is a related device is recorded in the related device list 2010, but each field device is a related device. In addition to the information indicating whether or not, the confirmation time may be recorded in the related device list 2010. Information other than that shown in FIG. 3 may be recorded in the related device list.
 次に異常検出システムで実施される異常検出処理の流れを、図5を用いて説明する。異常検出処理は大まかには、機器異常検出処理(ステップ1010)、エリア異常判定処理(ステップ1020~1030)、警報出力処理(ステップ1040)に分けられる。 Next, the flow of the abnormality detection process performed in the abnormality detection system will be described with reference to FIG. The abnormality detection processing is roughly divided into device abnormality detection processing (step 1010), area abnormality determination processing (steps 1020 to 1030), and alarm output processing (step 1040).
 機器異常検出処理では、機器異常検出システム301は現場機器101から送信されてくる情報をもとに、機器異常の発生有無を判定する。具体的には、機器異常が発生した現場機器101はネットワーク201を介して、機器異常検出システム301へ異常発生情報を送信し、機器異常検出システム301はこの異常発生情報を受信することで、現場機器101に異常が発生したことを検知する(ステップ1010)。 In the device abnormality detection process, the device abnormality detection system 301 determines whether a device abnormality has occurred based on information transmitted from the field device 101. Specifically, the field device 101 in which the device abnormality has occurred transmits abnormality occurrence information to the device abnormality detection system 301 via the network 201, and the device abnormality detection system 301 receives this abnormality occurrence information, thereby It is detected that an abnormality has occurred in the device 101 (step 1010).
 なお、各現場機器101は、現場機器101内のハードウェア部品の故障などの原因で所望の機能を果たさなくなった時点で異常発生情報を機器異常検出システム301に送信してもよいが、あるいは故障ではないが、正常時とは若干異なる動作を行うようになった場合、つまり故障の予兆が現れた時点で異常発生情報を機器異常検出システム301に送信してもよい。故障の予兆が現れた時点で異常発生情報を機器異常検出システム301に送信するように現場機器101が構成されていれば、現場機器101が故障していない場合であっても異常検出システムがエリア異常を検出できることもあるため、有効である。 Each field device 101 may transmit abnormality occurrence information to the device abnormality detection system 301 when a desired function is not performed due to a failure of a hardware component in the field device 101 or the like. However, when an operation slightly different from the normal operation is performed, that is, when an indication of a failure appears, the abnormality occurrence information may be transmitted to the device abnormality detection system 301. If the field device 101 is configured to transmit abnormality occurrence information to the device abnormality detection system 301 at the time when a failure sign appears, the abnormality detection system is in an area even if the field device 101 is not broken. It is effective because it can detect abnormalities.
 また、機器異常が発生していない場合に各現場機器は正常動作情報を定期的に送信し、機器異常検出システム301は現場機器からの正常動作情報の送信が途絶した時、現場機器101に異常が発生したと判定しても良い。このようにすることで、現場機器101が異常発生情報を送信できないような状態となった場合(たとえば現場機器101の通信機能異常、ネットワーク切断等)でも、機器異常検出システム301は現場機器101に異常が発生したことを検知できる。 In addition, when no device abnormality has occurred, each field device periodically transmits normal operation information, and the device abnormality detection system 301 detects an abnormality in the field device 101 when transmission of normal operation information from the field device is interrupted. It may be determined that occurrence has occurred. In this way, even when the field device 101 is in a state where it cannot transmit the abnormality occurrence information (for example, the communication function abnormality of the field device 101, the network disconnection, etc.), the device abnormality detection system 301 is connected to the field device 101. It is possible to detect that an abnormality has occurred.
 機器異常検出システム301は現場機器101に異常が発生したことを検知すると、その旨をエリア異常検出システム401に送信する。エリア異常検出システム401は機器異常検出システム301から現場機器101に異常が発生した旨の情報を受信すると、データベース501に現場機器101に異常発生情報を記録する。なお、現場機器101が異常発生日時を送信することに代えて、機器異常検出システム301は、異常発生情報を受信した時刻を異常発生日時としてもよい。このようにすると、現場機器が異常発生日時を認識するための時計装置を保有していない場合であっても、データベース501に現場機器で異常が発生した時刻を記録することができる。 When the device abnormality detection system 301 detects that an abnormality has occurred in the field device 101, the device abnormality detection system 301 transmits the fact to the area abnormality detection system 401. When the area abnormality detection system 401 receives information indicating that an abnormality has occurred in the field device 101 from the device abnormality detection system 301, it records the abnormality occurrence information in the field device 101 in the database 501. Instead of the field device 101 transmitting the abnormality occurrence date and time, the device abnormality detection system 301 may use the time when the abnormality occurrence information is received as the abnormality occurrence date and time. In this way, even when the field device does not have a clock device for recognizing the abnormality occurrence date and time, the time when the abnormality has occurred in the field device can be recorded in the database 501.
 エリア異常判定処理では、エリア異常検出システム401は、データベース501に記録した情報(関連機器リスト、過去の異常発生情報)に基づき、エリア異常判定結果(エリア異常の有無、発生場所、発生要因等)を警報装置601へ送信する。まず、エリア異常検出システム401は異常発生履歴3000を検索し、確認時間リスト2500に記録されている確認時間で指定された期間内に他の現場機器101(異常機器以外の現場機器)の異常情報が記録されているか確認する(ステップ1020)。確認時間リスト2500には、想定されるエリア異常毎に異なる時間範囲(確認時間)が記録されていることがある。そのためエリア異常検出システム401は確認時間リスト2500に複数の異なる確認時間が記録されている場合には、複数の時間範囲(確認時間)について、異常機器以外の現場機器の異常情報が記録されているか確認する。 In the area abnormality determination process, the area abnormality detection system 401 is based on information recorded in the database 501 (related device list, past abnormality occurrence information), and area abnormality determination results (the presence / absence of area abnormality, occurrence location, generation factor, etc.) Is transmitted to the alarm device 601. First, the area abnormality detection system 401 searches the abnormality occurrence history 3000, and abnormality information of other field devices 101 (field devices other than the abnormality devices) within a period specified by the confirmation time recorded in the confirmation time list 2500. Is recorded (step 1020). In the confirmation time list 2500, a different time range (confirmation time) may be recorded for each possible area abnormality. For this reason, when a plurality of different confirmation times are recorded in the confirmation time list 2500, the area abnormality detection system 401 records abnormality information of field devices other than abnormal devices for a plurality of time ranges (confirmation times). Check.
 他の現場機器の異常情報が記録されている場合(ステップ1020:Yes)、エリア異常検出システム401はデータベース501に記録されている関連機器リスト2010と確認時間リスト2500の内容に基づき、異常情報が記録されていた現場機器101が異常機器の関連機器であるか否か確認する(ステップ1021)。 When abnormality information of other field devices is recorded (step 1020: Yes), the area abnormality detection system 401 detects abnormality information based on the contents of the related device list 2010 and the confirmation time list 2500 recorded in the database 501. It is confirmed whether or not the recorded field device 101 is related to an abnormal device (step 1021).
 ステップ1020,1021で行われる処理の例を、図3、図2を用いて説明する。ここでは異常機器、つまりステップ1010で異常が発生したと判定された現場機器101の機器IDが“機器002”であり、機器002の異常発生日時(つまり機器002から送信された異常発生情報に含まれる異常発生日時)が“2017年1月1日 4時30分”であったケースを想定する。異常発生履歴3000には、2017年1月1日 3時25分に機器003に異常が発生した旨が記録されている(つまり、機器002に異常が発生する1時間以上前に、機器003に異常が発生している)。そのため、関連機器リスト2010と確認時間リスト2500、そして異常発生履歴3000の内容がそれぞれ、図3、図2に示されたものであった場合、ステップ1020では、確認時間(2017年1月1日 4時30分から1時間以上前、あるいは2017年1月1日 4時30分から30秒以内)内に異常機器(機器002)以外の現場機器101(機器003)で異常が発生したことが検出され、またステップ1021で機器003は異常機器(機器002)の関連機器であると判定される。 An example of processing performed in steps 1020 and 1021 will be described with reference to FIGS. Here, the device ID of the abnormal device, that is, the field device 101 determined to have an abnormality in step 1010 is “device 002”, and is included in the abnormality occurrence date and time of the device 002 (that is, the abnormality occurrence information transmitted from the device 002). The case where the abnormality occurrence date and time) is “January 1, 2017 4:30” is assumed. The abnormality occurrence history 3000 records that an abnormality occurred in the device 003 at 3:25 on January 1, 2017 (that is, in the device 003 at least one hour before the abnormality occurred in the device 002. An abnormality has occurred). Therefore, when the contents of the related device list 2010, the confirmation time list 2500, and the abnormality occurrence history 3000 are those shown in FIGS. 3 and 2, respectively, in step 1020, the confirmation time (January 1, 2017) is displayed. It was detected that an abnormality occurred on site equipment 101 (equipment 003) other than the anomalous equipment (equipment 002) within 1 hour before 4:30 or within 30 seconds from 4:30 on January 1, 2017. In step 1021, the device 003 is determined to be a device related to the abnormal device (device 002).
 また、別の実施形態として、例えば異常機器が検出された時、エリア異常検出システム401は異常発生履歴3000を検索して、過去の所定期間内(確認時間内)に関連機器の異常が発生していないか判定するが、保守作業や現地確認等により異常の発生した現場機器101(つまり異常機器)の関連機器に対するエリア異常が発生していないことが確認されている場合、その関連機器の機器異常情報を検索対象から除外しても良い。例えば鉄道システムの作業者が現地確認等により異常機器の関連機器に対するエリア異常が発生していないことを確認した場合、その旨をデータベース501に登録しておく。そしてステップ1020またはステップ1021において、異常発生履歴3000内に異常機器の関連機器について機器異常が発生している旨の記録があったとしても、エリア異常検出システム401はエリア異常が発生したと判定しないようにするとよい。 As another embodiment, for example, when an abnormal device is detected, the area abnormality detection system 401 searches the abnormality occurrence history 3000, and an abnormality of the related device occurs within a predetermined past period (within a confirmation time). However, if it is confirmed that there is no area abnormality with respect to the related device of the field device 101 (that is, the abnormal device) where the abnormality has occurred due to maintenance work, on-site confirmation, etc., the device of the related device Abnormal information may be excluded from the search target. For example, when an operator of the railway system confirms that there is no area abnormality with respect to the related equipment of the abnormal equipment by on-site confirmation or the like, that fact is registered in the database 501. In step 1020 or step 1021, even if there is a record in the abnormality occurrence history 3000 that a device abnormality has occurred with respect to the device related to the abnormal device, the area abnormality detection system 401 does not determine that an area abnormality has occurred. It is good to do so.
 ステップ1020で検出された機器の情報が異常機器の関連機器である場合(ステップ1021:Yes)、エリア異常検出システム401はエリア異常が発生したと判定し、エリア異常が発生した旨を警報装置601に通知する(ステップ1022)。また、ここでエリア異常検出システム401は、機器異常検出システム301から受信した異常発生情報をデータベース501の異常発生履歴3000へ記録する。またエリア異常検出システム401は、エリア異常の判定結果についてもデータベース501に記録してよい。 When the device information detected in step 1020 is related to the abnormal device (step 1021: Yes), the area abnormality detection system 401 determines that an area abnormality has occurred, and an alarm device 601 indicates that the area abnormality has occurred. (Step 1022). Here, the area abnormality detection system 401 records the abnormality occurrence information received from the device abnormality detection system 301 in the abnormality occurrence history 3000 of the database 501. The area abnormality detection system 401 may also record the area abnormality determination result in the database 501.
 エリア異常が発生した旨を警報装置601に通知する時、エリア異常検出システム401は、エリア異常の種類(発生要因)や異常の発生場所の推定を行って、その情報も警報装置601に通知する。またエリア異常検出システム401は、警報装置601に通知される情報をデータベース501に記録してもよい。警報装置601に通知される内容については後述する。 When notifying the alarm device 601 that an area abnormality has occurred, the area abnormality detection system 401 estimates the type (occurrence factor) of the area abnormality and the location where the abnormality has occurred, and notifies the alarm device 601 of the information as well. . The area abnormality detection system 401 may record information notified to the alarm device 601 in the database 501. The contents notified to the alarm device 601 will be described later.
 一方、確認時間内に関連機器の異常記録がない場合(ステップ1020:No、またはステップ1021:No)、機器単体故障と判定し、機器単体故障が発生した旨を警報装置601に通知する(ステップ1030)。ステップ1022と同様、ステップ1030でもエリア異常検出システム401は、受信した異常発生情報を異常発生履歴3000へ記録する。 On the other hand, when there is no abnormality record of the related device within the confirmation time (step 1020: No, or step 1021: No), it is determined that the device has failed, and the alarm device 601 is notified that the device has failed (step). 1030). Similar to step 1022, in step 1030, the area abnormality detection system 401 records the received abnormality occurrence information in the abnormality occurrence history 3000.
 警報出力処理では、警報装置601は異常発生情報およびエリア異常判定結果に関する警報をユーザに提示する(ステップ1040)。図6は、警報装置601がユーザへ提示する警報画面6010の例である。先に述べたとおり、エリア異常検出システム401は異常が機器単体故障(機器単体異常)かエリア異常かを推定し、またエリア異常の場合にはエリア異常の種類(発生要因)や異常の発生場所の推定を行って、その情報を警報装置601に通知する。警報装置601はエリア異常検出システム401から受け取った情報をもとにして、図6に示すような警報画面を作成し、ユーザに提示する。図6の例では、異常種別として“エリア異常”が下線付きの太字で表示され、また発生要因(推定要因)として“地絡”が下線付きの太字で表示され、そして発生場所のカラムでは“路線X キロ程X付近”が下線付きの太字で表示されている。これは発生した異常がエリア異常で、その発生要因(推定される要因)が地絡で、異常の発生場所が“路線X キロ程X付近”であることを表している。また図6に示すように、これ以外の情報も警報画面に表示されてよい。以下ではエリア異常の発生要因や異常の発生場所の推定方法の例を概説する。 In the alarm output process, the alarm device 601 presents an alarm regarding abnormality occurrence information and area abnormality determination results to the user (step 1040). FIG. 6 is an example of an alarm screen 6010 that the alarm device 601 presents to the user. As described above, the area abnormality detection system 401 estimates whether an abnormality is a single device failure (single device abnormality) or an area abnormality, and in the case of an area abnormality, the type of area abnormality (cause of occurrence) and the location where the abnormality occurred. And the alarm device 601 is notified of the information. The alarm device 601 creates an alarm screen as shown in FIG. 6 based on the information received from the area abnormality detection system 401 and presents it to the user. In the example of FIG. 6, “Area abnormality” is displayed in bold with an underline as an abnormality type, “Ground fault” is displayed in bold with an underline as an occurrence factor (estimation factor), and “ "Route X Kapprox X neighborhood" is displayed in bold with an underline. This indicates that the anomaly that occurred is an area anomaly, the cause (estimated factor) was a ground fault, and the location where the anomaly occurred was “around line X km X”. Further, as shown in FIG. 6, other information may be displayed on the alarm screen. In the following, an example of an area abnormality occurrence factor and an estimation method of an abnormality occurrence location will be outlined.
 エリア異常の種類(発生要因)や異常の発生場所の推定にあたっては、様々な方法が用いられて良く、ここではいくつかの例を概説する。なお、以下の説明においては、ステップ1010で異常が発生していると判定された現場機器101(異常機器)が“機器001”であり、ステップ1021で異常機器(機器001)の関連機器と判定された現場機器101が“機器002”であるケースを例にとって説明する。 様 々 Various methods may be used to estimate the type (occurrence factor) of the area abnormality and the place where the abnormality occurs, and here are some examples. In the following description, the field device 101 (abnormal device) determined to have an abnormality in step 1010 is “device 001”, and is determined to be a related device of the abnormal device (device 001) in step 1021. A case where the field device 101 is “device 002” will be described as an example.
 たとえばエリア異常検出システム401は、関連機器リスト2010に記載されている異常機器(機器001)および関連機器(機器002)の設置位置カラム2012に記録されている位置を異常発生場所であると推定し、それを警報装置601に通知するとよい。また、これに加えてエリア異常検出システム401は、関連機器リスト2010に記録されている機器001および機器002の関連機器(この関連機器は、まだ異常発生情報を出力していない現場機器でもよい)の設置位置カラム2012に記録されている位置を抽出して、これをエリア異常により影響がでる可能性のある範囲として警報装置601に通知しても良い。 For example, the area abnormality detection system 401 estimates that the position recorded in the installation position column 2012 of the abnormal device (device 001) and the related device (device 002) described in the related device list 2010 is an abnormality occurrence location. This may be notified to the alarm device 601. In addition to this, the area abnormality detection system 401 is also associated with the devices 001 and 002 recorded in the related device list 2010 (this related device may be a field device that has not yet output abnormality occurrence information). The position recorded in the installation position column 2012 may be extracted, and this may be notified to the alarm device 601 as a range that may be affected by an area abnormality.
 またエリア異常検出システム401は関連機器リスト2010で想定している異常事象(想定エリア異常カラム(2013-1,2013-2,...)に記述されている異常事象。図3の例では、“地絡”や“火災”である)をエリア異常の発生要因として、警報装置601に通知するとよい。あるいはエリア異常検出システム401は、現場機器101より受信した異常内容(異常発生情報の内容)に基づき、エリア異常の発生要因を推定してもよい。発生要因が一意に特定できない場合は、エリア異常検出システム401は可能性のある事象として複数事象(要因)を警報装置601に通知しても良い。可能性のある事象として複数事象が存在し得る場合、図6に示すように、エリア異常検出システム401は各事象の推定発生確率を併せて通知しても良い。 The area abnormality detection system 401 is assumed to be an abnormal event (an abnormal event described in an assumed area abnormal column (2013-1, 2013-2,...) In the related device list 2010. In the example of FIG. The alarm device 601 may be notified of the occurrence of an area abnormality as “ground fault” or “fire”. Alternatively, the area abnormality detection system 401 may estimate the cause of the area abnormality based on the abnormality content (content of abnormality occurrence information) received from the field device 101. When the occurrence factor cannot be uniquely identified, the area abnormality detection system 401 may notify the alarm device 601 of a plurality of events (factors) as possible events. When multiple events may exist as possible events, the area abnormality detection system 401 may notify the estimated occurrence probability of each event as shown in FIG.
 また警報画面6010をユーザへ提示する場合、警報装置601は検出した異常事象に対応するための作業内容をユーザへ提示しても良い。またエリア異常検出システム401が各事象の推定発生確率を警報装置601に通知してきた場合、警報装置601は推定発生確率が所定の確率以下の事象は、警報として出力しない等の処理を行っても良い。本実施例に係る異常検出システムは、図5の処理を繰り返し行うことで、現場機器101の異常やエリア異常が発生したことをユーザに通知することができる。 Further, when the alarm screen 6010 is presented to the user, the alarm device 601 may present work contents for responding to the detected abnormal event to the user. Further, when the area abnormality detection system 401 notifies the alarm device 601 of the estimated occurrence probability of each event, the alarm device 601 may perform processing such as not outputting an event with an estimated occurrence probability equal to or less than a predetermined probability. good. The abnormality detection system according to the present embodiment can notify the user that an abnormality of the field device 101 or an area abnormality has occurred by repeatedly performing the process of FIG.
 なお、上で説明した例では、確認時間は想定するエリア異常ごとに決められている。そのため、異常検出システムが図5の処理を実行することで異常要因を特定する場合、異常機器の種類に関わらず、同じ確認時間を用いて図5の判定処理(ステップ1020,1021等)を行う。しかし別の実施形態として、想定するエリア異常に加えて、現場機器(関連機器)ごとに異なる確認時間が設定されてもよい。例えば故障率が高い現場機器ほど別の現場機器と同じタイミングで偶発的に壊れる確率が高いため、確認時間を短く設定する運用が考えられる。 In the example described above, the confirmation time is determined for each assumed area abnormality. Therefore, when the abnormality detection system identifies the cause of the abnormality by executing the processing of FIG. 5, the determination processing ( steps 1020, 1021, etc.) of FIG. 5 is performed using the same confirmation time regardless of the type of the abnormal device. . However, as another embodiment, in addition to the assumed area abnormality, a different confirmation time may be set for each field device (related device). For example, a field device with a higher failure rate has a higher probability of accidental breakage at the same timing as another field device, and therefore, an operation in which the confirmation time is set short can be considered.
 具体例を用いて説明する。たとえば異常機器が機器001で、そして想定されるエリア異常の種類が“地絡”の場合に機器001の関連機器が、機器002と機器004であるが、機器002の故障率が機器004の故障率よりも高い場合を想定する。その場合、たとえば機器001に対する機器002の確認時間は20秒以下、機器001に対する機器004の確認時間は30秒以下、と確認時間を設定できるように、異常検出システムが構成されていてもよい。この様に確認時間が設定されると、機器001の異常が発生するより25秒前に機器002の異常が発生していたとしても、異常検出システムはエリア異常(地絡)が発生したとは判断しない。ただし機器001の異常が発生する25秒前に機器004の異常が発生していた場合には、異常検出システムはエリア異常(地絡)が発生したと判定する。なお、上でも述べたとおり、確認時間はエリア異常の種類によって異なり得るので、現場機器ごとに設定される確認時間は、エリア異常の種類ごとに異なる値を設定可能である。 This will be explained using a specific example. For example, when the abnormal device is the device 001 and the assumed area abnormality type is “ground fault”, the related devices of the device 001 are the devices 002 and 004, but the failure rate of the device 002 is the failure of the device 004. Assume that the rate is higher than the rate. In that case, for example, the abnormality detection system may be configured so that the confirmation time can be set such that the confirmation time of the device 002 with respect to the device 001 is 20 seconds or less and the confirmation time of the device 004 with respect to the device 001 is 30 seconds or less. When the confirmation time is set in this way, even if the device 002 has an abnormality 25 seconds before the device 001 has an abnormality, the abnormality detection system has detected that an area abnormality (ground fault) has occurred. Do not judge. However, if an abnormality of the device 004 occurs 25 seconds before the abnormality of the device 001 occurs, the abnormality detection system determines that an area abnormality (ground fault) has occurred. As described above, since the confirmation time may vary depending on the type of area abnormality, the confirmation time set for each field device can be set to a different value for each type of area abnormality.
 確認時間を故障率に基づいて設定する場合、各現場機器の故障率(1時間あたりの平均故障率=1/MTBF)として各現場機器の製造者による公称値を用いても良いし、実運用時の観測データより算出した故障率を用いても良い。各故障率は、運用時の観測データを元に随時更新しても良い。また機器設置時期や保守実施時期を加味した、時間経過に伴う故障率変化(バスタブ曲線)を想定した故障率が用いられても良い。関連する現場機器数が多数存在する場合、そのうちのどれかが単位時間内に故障する確率は台数に比例して高くなる。よってユーザが確認時間を設定する際、関連する現場機器の数を加味して確認時間を決定しても良い。例えば故障率10-5の現場機器が10台設置されており、それぞれが関連機器である場合、ユーザは機器全体としての故障率を10-4(=機器単体故障率10-5×関連機器数10台)と算出した上で、各機器の確認時間を設定しても良い。 When setting the confirmation time based on the failure rate, the nominal value by the manufacturer of each field device may be used as the failure rate of each field device (average failure rate per hour = 1 / MTBF), or actual operation You may use the failure rate calculated from the time observation data. Each failure rate may be updated at any time based on observation data during operation. Further, a failure rate that assumes a failure rate change (bathtub curve) with the passage of time, taking into account the device installation time and maintenance execution time, may be used. When there are a large number of related field devices, the probability that any one of them will fail within a unit time increases in proportion to the number. Therefore, when the user sets the confirmation time, the confirmation time may be determined in consideration of the number of related field devices. For example, when 10 on-site devices with a failure rate of 10 −5 are installed and each is a related device, the user sets the failure rate of the entire device to 10 −4 (= unit failure rate of 10 −5 × number of related devices) (10 units) and the confirmation time of each device may be set.
 異常検出システムは、複数の現場機器(異常機器と関連機器)の異常発生日時の差(以下ではこれを、「異常発生時間差」と呼ぶ)に基づき、異なる種類の警報を出しても良い。異常発生時間差が短いほど、それぞれの機器異常が偶発的な事象である可能性が低いと判断できるため、それに応じた警報を出すことが考えられる。例えば異常検出システムがエリア異常が発生したと判定した時、異常機器と関連機器の異常発生時間差が確認時間の上限値の1/10以下であった場合は特別警報を出力し、異常発生時間差が確認時間の上限値の1/2以下であれば警報を出力し、異常発生時間差がそれ以上であれば注意報を出力しても良い。具体的には、あるエリア異常に割り当てられている確認時間が360秒以下の場合、異常検出システムは、異常発生時間差が36秒以内の場合は特別警報を出力し、180秒以内の場合は警報を出力し、360秒以内の場合には注意報を出すようにして良い。なお、この警報出力は、エリア異常の発生有無とは無関係に行われてもよい。つまり2台の現場機器に異常が発生したが、エリア異常検出システム401はエリア異常が発生したとは判断しなかった場合でも、エリア異常検出システム401(または警報装置601)はそれぞれの機器の異常発生日時の差を求め、警報装置601は求められた差に応じた警報を出力してもよい。 The anomaly detection system may issue different types of alarms based on the difference in the date and time of occurrence of anomalies between a plurality of field devices (abnormal equipment and related equipment) (hereinafter referred to as “abnormality occurrence time difference”). As the abnormality occurrence time difference is shorter, it can be determined that each device abnormality is less likely to be an accidental event, so it is possible to issue an alarm accordingly. For example, when the abnormality detection system determines that an area abnormality has occurred, if the abnormality occurrence time difference between the abnormal device and the related device is 1/10 or less of the upper limit of the confirmation time, a special alarm is output and the abnormality occurrence time difference is An alarm may be output if it is less than or equal to 1/2 of the upper limit value of the confirmation time, and a warning may be output if the difference in abnormality occurrence time is more than that. Specifically, when the confirmation time assigned to a certain area abnormality is 360 seconds or less, the abnormality detection system outputs a special alarm if the abnormality occurrence time difference is within 36 seconds, and alarms within 180 seconds. May be output and a warning message may be issued within 360 seconds. This alarm output may be performed regardless of whether or not an area abnormality has occurred. That is, even if an abnormality has occurred in the two field devices, the area abnormality detection system 401 (or the alarm device 601) does not detect that an area abnormality has occurred. The alarm device 601 may output an alarm corresponding to the determined difference by determining the difference in occurrence date and time.
 また異常検出システムは、異常発生時間差に基づき、エリア異常の発生要因を推定しても良い。例えば異常機器と関連機器の異常発生時間差が非常に小さい場合(数秒以内等)、短時間に多数の現場機器へ影響する、地絡等のエリア異常が発生した可能性が高い。一方、異常発生時間差が大きい場合(数分~数10分)、複数機器へ影響が及ぶまでにある程度の時間が掛かる、火災や溢水等のエリア異常が発生した可能性が高い。このように、異常機器と関連機器の異常発生時間差とエリア異常の間に相関がある場合には、異常発生時間差に基づき、エリア異常の発生要因を推定することは有効である。 Also, the abnormality detection system may estimate the cause of area abnormality based on the abnormality occurrence time difference. For example, when the difference in abnormality occurrence time between the abnormal device and the related device is very small (within several seconds or the like), there is a high possibility that an area abnormality such as a ground fault has occurred in a short time, which affects many field devices. On the other hand, when the abnormality occurrence time difference is large (several minutes to several tens of minutes), there is a high possibility that an area abnormality such as a fire or flooding takes some time to affect multiple devices. Thus, when there is a correlation between the abnormality occurrence time difference between the abnormal device and the related device and the area abnormality, it is effective to estimate the cause of the area abnormality based on the abnormality occurrence time difference.
 また異常検出システムは、各現場機器101の設置位置を考慮して、エリア異常の発生要因を推定してもよい。たとえばある鉄道路線上に、複数(たとえば4つ)の現場機器(以下ではこれらを、機器A,機器B,機器C,機器Dと呼ぶ)が、機器A,機器B,機器C,機器Dの順に設置されていたとする。もし機器A,機器B,機器C,機器Dの順に異常が発生した場合、火災や溢水等の物理的な異常事象が要因となっている可能性が高いと考えられる。 Further, the abnormality detection system may estimate the cause of the area abnormality in consideration of the installation position of each field device 101. For example, on a certain railway line, a plurality of (for example, four) field devices (hereinafter referred to as device A, device B, device C, and device D) are connected to device A, device B, device C, and device D. Assume that they were installed in order. If an abnormality occurs in the order of device A, device B, device C, and device D, it is highly likely that a physical abnormal event such as a fire or overflow is a factor.
 また異常検出システムがエリア異常の発生要因を推定する際、現場機器101より受信した情報以外の情報を使用しても良い。例えば、現場機器101周辺の自然現象(降雨、雷、猛暑、地震等)、地理情報(近隣に川がある等)等に関する情報が用いられてもよい。異常検出システムがエリア異常の発生要因の推定に自然現象に関する情報を用いる場合、異常検出システムが実際に測定・収集した情報を用いても良いし、天気予報等の事前予報情報を用いても良い。 Further, when the abnormality detection system estimates the cause of the area abnormality, information other than the information received from the field device 101 may be used. For example, information related to natural phenomena (rainfall, lightning, intense heat, earthquake, etc.) around the field device 101, geographical information (such as a river nearby), and the like may be used. When the anomaly detection system uses information about natural phenomena to estimate the cause of area anomalies, the information actually measured and collected by the anomaly detection system may be used, or prior forecast information such as weather forecasts may be used .
 上では、警報装置601は画面に警報を表示する例を説明したが、同様の内容を音、ランプ点灯、振動(携帯端末のバイブレーション機能等)、といった別の手段によりユーザへ提示してもよい。 In the above, an example in which the alarm device 601 displays an alarm on the screen has been described, but the same content may be presented to the user by another means such as sound, lamp lighting, vibration (vibration function of the mobile terminal, etc.). .
 エリア異常検出システム401がエリア異常と判定した場合、異常検出システムは外部のシステムにエリア異常の種類やエリア異常の発生している場所を考慮した制御を行わせても良い。例えば異常検出システムは、エリア異常検出システム401が鉄道の運行管理システムや鉄道保安システム、あるいは変電所を管理する変電システム等とネットワーク201を介して接続された構成をとり、運行管理システムや鉄道保安システムにエリア異常が発生した旨及び異常の発生している(と考えられる)エリアの情報を通知することで、当該エリアへの列車進入を制限させてもよい。またエリア異常検出システム401は、変電所を管理する変電システムへエリア異常発生(及び異常の発生していると考えられるエリアの情報)を通知し、当該エリアへの給電を制限してもよい。 When the area abnormality detection system 401 determines that an area abnormality has occurred, the abnormality detection system may cause an external system to perform control in consideration of the type of area abnormality and the location where the area abnormality has occurred. For example, the abnormality detection system has a configuration in which the area abnormality detection system 401 is connected to a railway operation management system, a railway security system, or a substation system that manages a substation via the network 201, and the operation management system or the railway security system. The train entry to the area may be restricted by notifying the system that an area abnormality has occurred and information on the area where the abnormality has occurred (considered). The area abnormality detection system 401 may notify the substation system that manages the substation of the occurrence of the area abnormality (and information on the area where the abnormality is considered to occur), and may limit power supply to the area.
 以上のように処理を実装することにより、鉄道沿線におけるエリア異常を高精度かつ早期に検出できる。 By implementing the processing as described above, it is possible to detect an area abnormality along the railway along with high accuracy and early.
101 現場機器
201 ネットワーク
301 機器異常検出システム
401 エリア異常検出システム
501 データベース
601 警報装置
2010 関連機器リスト
2500 確認時間リスト
3000 異常発生履歴
6010 警報画面
101 field device 201 network 301 device abnormality detection system 401 area abnormality detection system 501 database 601 alarm device 2010 related device list 2500 confirmation time list 3000 abnormality occurrence history 6010 alarm screen

Claims (13)

  1.  複数の現場機器にネットワークを介して接続された機器異常検出システムと、
     複数の前記現場機器の挙動に影響を及ぼす異常事象であるエリア異常の検出を行う、エリア異常検出システムと、
     データベースと、
     警報装置と、
    を有する異常検出システムにおいて、
     前記機器異常検出システムは、前記現場機器に異常が発生したことを検出すると、前記現場機器の異常についての情報である異常発生情報を前記エリア異常検出システムに送信し、前記エリア異常検出システムは受信した前記異常発生情報を、前記データベースが有する異常発生履歴に記録するよう構成されており、
     前記エリア異常検出システムはまた、複数の前記現場機器の中の第1の現場機器の前記異常発生情報を前記機器異常検出システムから受信すると、前記異常発生履歴を検索することで、過去の所定の時間帯に前記第1の現場機器の関連機器に異常が発生したか判定し、
     前記関連機器に異常が発生していた場合、エリア異常が発生したと判断し、前記警報装置を介してユーザにエリア異常が発生した旨を通知する、
    ことを特徴とする、異常検出システム。
    A device abnormality detection system connected to a plurality of field devices via a network;
    An area abnormality detection system that detects an area abnormality that is an abnormal event affecting the behavior of the plurality of field devices;
    A database,
    An alarm device;
    In an anomaly detection system having
    When the device abnormality detection system detects that an abnormality has occurred in the field device, the device abnormality detection system transmits abnormality occurrence information, which is information about the abnormality of the field device, to the area abnormality detection system, and the area abnormality detection system receives The abnormality occurrence information is configured to be recorded in the abnormality occurrence history of the database,
    The area abnormality detection system also receives the abnormality occurrence information of the first field device among the plurality of field devices from the device abnormality detection system, searches the abnormality occurrence history, Determine whether an abnormality has occurred in the related equipment of the first field device in the time zone,
    When an abnormality has occurred in the related device, it is determined that an area abnormality has occurred, and the user is notified that an area abnormality has occurred via the alarm device.
    An anomaly detection system characterized by that.
  2.  前記異常発生情報には、異常の発生した前記現場機器の識別情報と、異常の発生した日時情報が含まれており、
     前記データベースは、前記エリア異常が発生した場合に影響が及ぶと想定される現場機器の組合せについての情報である関連機器リストと、前記エリア異常検出システムが前記異常発生履歴を検索する際の検索範囲を示す確認時間と、を保持しており、
     前記エリア異常検出システムは、前記関連機器リストを用いて、前記第1の現場機器の関連機器を特定する、
    ことを特徴とする、請求項1に記載の異常検出システム。
    The abnormality occurrence information includes identification information of the field device where the abnormality has occurred, and date information when the abnormality has occurred,
    The database includes a related device list that is information on a combination of field devices assumed to be affected when the area abnormality occurs, and a search range when the area abnormality detection system searches the abnormality occurrence history. And a confirmation time indicating
    The area abnormality detection system identifies the related device of the first field device using the related device list.
    The abnormality detection system according to claim 1, wherein:
  3.  前記関連機器リストには、前記現場機器の組合せについての情報がエリア異常毎に記録されており、
     前記確認時間は、エリア異常毎に定義されている、
    ことを特徴とする、請求項2に記載の異常検出システム。
    In the related equipment list, information on the combination of the field equipment is recorded for each area abnormality,
    The confirmation time is defined for each area abnormality,
    The abnormality detection system according to claim 2, wherein:
  4.  前記確認時間は、前記現場機器ごとに定義され、前記現場機器の故障率より算出されることを特徴とする、請求項2または3に記載の異常検出システム。 4. The abnormality detection system according to claim 2, wherein the confirmation time is defined for each field device and is calculated from a failure rate of the field device.
  5.  前記エリア異常検出システムは、異常が発生した2つの前記現場機器の異常発生日時の差を算出し、
     前記警報装置は、前記異常発生日時の差を元に、前記ユーザに通知する警報の種別を決定する、
    ことを特徴とする、請求項2乃至4のいずれか一項に記載の異常検出システム。
    The area abnormality detection system calculates a difference between the abnormality occurrence dates and times of the two field devices where an abnormality has occurred,
    The alarm device determines a type of alarm to be notified to the user based on the difference in the date and time of occurrence of the abnormality.
    The abnormality detection system according to any one of claims 2 to 4, wherein the abnormality detection system is characterized in that:
  6.  前記関連機器リストは、前記現場機器の設置位置の情報を含み、
     前記エリア異常検出システムは、前記現場機器の設置位置の情報を元に、発生したエリア異常の種類を推定する
    ことを特徴とする、請求項2乃至5のいずれか一項に記載の異常検出システム。
    The related device list includes information on an installation position of the field device,
    The abnormality detection system according to any one of claims 2 to 5, wherein the area abnormality detection system estimates a type of an area abnormality that has occurred based on information on an installation position of the field device. .
  7.  前記エリア異常検出システムは、異常が発生した2つの前記現場機器の異常発生日時の差を算出し、
     前記エリア異常検出システムは、前記異常発生日時の差を元に、発生したエリア異常の種類を推定すること、
    を特徴とする、請求項1乃至5のいずれか一項に記載の異常検出システム。
    The area abnormality detection system calculates a difference between the abnormality occurrence dates and times of the two field devices where an abnormality has occurred,
    The area abnormality detection system estimates the type of area abnormality that has occurred based on the difference in the date and time of occurrence of the abnormality;
    The abnormality detection system according to any one of claims 1 to 5, wherein
  8.  前記異常検出システムは、
     前記異常発生情報と、エリア異常の発生判定結果と、発生した異常に対応するための作業内容と、前記エリア異常の推定発生確率と、の少なくとも1つ以上を含む警報情報をユーザに提示すること
    を特徴とする、請求項1乃至7のいずれか一項に記載の異常検出システム。
    The abnormality detection system includes:
    Presenting to the user alarm information including at least one of the abnormality occurrence information, the area abnormality occurrence determination result, the work content for responding to the abnormality that has occurred, and the estimated occurrence probability of the area abnormality. The abnormality detection system according to any one of claims 1 to 7, wherein
  9.  前記現場機器は正常動作時に正常動作情報を前記機器異常検出システムへ定期的に送信し、
     前記機器異常検出システムは前記現場機器からの前記正常動作情報を所定時間受信しなかった場合に、前記現場機器に異常が発生したと判定すること
    を特徴とする、請求項1乃至8のいずれか一項に記載の異常検出システム。
    The field device regularly transmits normal operation information to the device abnormality detection system during normal operation,
    9. The apparatus abnormality detection system according to claim 1, wherein the apparatus abnormality detection system determines that an abnormality has occurred in the field device when the normal operation information from the field device has not been received for a predetermined time. The abnormality detection system according to one item.
  10.  前記異常検出システムは、前記ネットワークを介して、鉄道運行管理システムと、鉄道保安システムと、変電システムと、の少なくとも1つ以上と接続されており、
     前記エリア異常検出システムは、エリア異常が発生したと判定した場合、
     前記鉄道運行管理システムと、前記鉄道保安システムと、前記変電システムと、の少なくとも1つ以上に対して、エリア異常についての情報を送信し、エリア異常の種類に応じた制御を行わせる、
    ことを特徴とする、請求項1乃至9のいずれか一項に記載の異常検出システム。
    The abnormality detection system is connected to at least one of a railway operation management system, a railway security system, and a substation system via the network,
    When the area abnormality detection system determines that an area abnormality has occurred,
    For at least one of the railway operation management system, the railway security system, and the substation system, information on area abnormality is transmitted, and control according to the type of area abnormality is performed.
    The abnormality detection system according to any one of claims 1 to 9, wherein
  11.  複数の現場機器にネットワークを介して接続された異常検出システムの異常検出方法であって、
     前記異常検出システムが、
     前記現場機器に異常が発生した時に、前記現場機器の異常についての情報である異常発生情報を、異常発生履歴としてデータベースに記録する第1工程と、
     複数の前記現場機器の中の第1の現場機器に異常が発生した時に、前記異常発生履歴を検索することで、過去の所定の時間帯に前記第1の現場機器の関連機器に異常が発生したか判定する第2工程と、
     前記関連機器に異常が発生していた場合、複数の前記現場機器の挙動に影響を及ぼす異常事象であるエリア異常が発生したと判断し、ユーザにエリア異常が発生した旨を通知する第3工程と、
    を実行することを特徴とする、異常検出方法。
    An anomaly detection method for an anomaly detection system connected to a plurality of field devices via a network,
    The abnormality detection system is
    A first step of recording abnormality occurrence information, which is information about an abnormality of the field device, in a database as an abnormality occurrence history when an abnormality occurs in the field device;
    When an abnormality occurs in the first field device among the plurality of field devices, an abnormality occurs in the related device of the first field device in the past predetermined time zone by searching the abnormality occurrence history. A second step of determining whether or not
    When an abnormality has occurred in the related device, it is determined that an area abnormality that is an abnormal event affecting the behavior of the plurality of field devices has occurred, and a third step of notifying the user that an area abnormality has occurred When,
    The abnormality detection method characterized by performing.
  12.  前記異常発生情報には、異常の発生した前記現場機器の識別情報と、異常の発生した日時情報が含まれており、
     前記データベースは、前記エリア異常が発生した場合に影響が及ぶと想定される現場機器の組合せについての情報である関連機器リストと、前記異常検出システムが前記異常発生履歴を検索する際の検索範囲を示す確認時間と、を保持しており、
     前記第2工程で前記異常検出システムは、前記関連機器リストを用いて前記第1の現場機器の関連機器を特定する、
    ことを特徴とする、請求項11に記載の異常検出方法。
    The abnormality occurrence information includes identification information of the field device where the abnormality has occurred, and date information when the abnormality has occurred,
    The database includes a related device list that is information on a combination of field devices that are assumed to be affected when the area abnormality occurs, and a search range when the abnormality detection system searches the abnormality occurrence history. The confirmation time shown, and
    In the second step, the abnormality detection system identifies the related device of the first field device using the related device list,
    The abnormality detection method according to claim 11, wherein:
  13.  前記関連機器リストには、前記現場機器の組合せについての情報がエリア異常毎に記録されており、
     前記確認時間は、エリア異常毎に定義されている、
    ことを特徴とする、請求項12に記載の異常検出方法。
    In the related equipment list, information on the combination of the field equipment is recorded for each area abnormality,
    The confirmation time is defined for each area abnormality,
    The abnormality detection method according to claim 12, wherein:
PCT/JP2018/010935 2017-05-11 2018-03-20 Abnormality detection system WO2018207469A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017094629A JP2018188094A (en) 2017-05-11 2017-05-11 Abnormality detection system
JP2017-094629 2017-05-11

Publications (1)

Publication Number Publication Date
WO2018207469A1 true WO2018207469A1 (en) 2018-11-15

Family

ID=64104565

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/010935 WO2018207469A1 (en) 2017-05-11 2018-03-20 Abnormality detection system

Country Status (2)

Country Link
JP (1) JP2018188094A (en)
WO (1) WO2018207469A1 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10322734B2 (en) 2015-01-19 2019-06-18 Tetra Tech, Inc. Sensor synchronization apparatus and method
US10349491B2 (en) 2015-01-19 2019-07-09 Tetra Tech, Inc. Light emission power control apparatus and method
US10362293B2 (en) 2015-02-20 2019-07-23 Tetra Tech, Inc. 3D track assessment system and method
US10384697B2 (en) 2015-01-19 2019-08-20 Tetra Tech, Inc. Protective shroud for enveloping light from a light emitter for mapping of a railway track
US10625760B2 (en) 2018-06-01 2020-04-21 Tetra Tech, Inc. Apparatus and method for calculating wooden crosstie plate cut measurements and rail seat abrasion measurements based on rail head height
US10730538B2 (en) 2018-06-01 2020-08-04 Tetra Tech, Inc. Apparatus and method for calculating plate cut and rail seat abrasion based on measurements only of rail head elevation and crosstie surface elevation
US10807623B2 (en) 2018-06-01 2020-10-20 Tetra Tech, Inc. Apparatus and method for gathering data from sensors oriented at an oblique angle relative to a railway track
US10908291B2 (en) 2019-05-16 2021-02-02 Tetra Tech, Inc. System and method for generating and interpreting point clouds of a rail corridor along a survey path
US11377130B2 (en) 2018-06-01 2022-07-05 Tetra Tech, Inc. Autonomous track assessment system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11278269A (en) * 1998-03-30 1999-10-12 Mitsubishi Electric Corp Track circuit monitoring device
JP2005208707A (en) * 2004-01-20 2005-08-04 Fujitsu Ltd Abnormality monitoring device, abnormality search support method, abnormality search support program
JP2011059873A (en) * 2009-09-08 2011-03-24 Mitsubishi Electric Corp Monitoring device, method, and program
JP2015228051A (en) * 2014-05-30 2015-12-17 株式会社東芝 Common failure factor detection system and common failure factor detection method of nuclear power plant
JP2016203819A (en) * 2015-04-23 2016-12-08 三菱電機株式会社 Test device and test method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11278269A (en) * 1998-03-30 1999-10-12 Mitsubishi Electric Corp Track circuit monitoring device
JP2005208707A (en) * 2004-01-20 2005-08-04 Fujitsu Ltd Abnormality monitoring device, abnormality search support method, abnormality search support program
JP2011059873A (en) * 2009-09-08 2011-03-24 Mitsubishi Electric Corp Monitoring device, method, and program
JP2015228051A (en) * 2014-05-30 2015-12-17 株式会社東芝 Common failure factor detection system and common failure factor detection method of nuclear power plant
JP2016203819A (en) * 2015-04-23 2016-12-08 三菱電機株式会社 Test device and test method

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10349491B2 (en) 2015-01-19 2019-07-09 Tetra Tech, Inc. Light emission power control apparatus and method
US10384697B2 (en) 2015-01-19 2019-08-20 Tetra Tech, Inc. Protective shroud for enveloping light from a light emitter for mapping of a railway track
US10322734B2 (en) 2015-01-19 2019-06-18 Tetra Tech, Inc. Sensor synchronization apparatus and method
US10728988B2 (en) 2015-01-19 2020-07-28 Tetra Tech, Inc. Light emission power control apparatus and method
US11196981B2 (en) 2015-02-20 2021-12-07 Tetra Tech, Inc. 3D track assessment apparatus and method
US10362293B2 (en) 2015-02-20 2019-07-23 Tetra Tech, Inc. 3D track assessment system and method
US11399172B2 (en) 2015-02-20 2022-07-26 Tetra Tech, Inc. 3D track assessment apparatus and method
US11259007B2 (en) 2015-02-20 2022-02-22 Tetra Tech, Inc. 3D track assessment method
US10625760B2 (en) 2018-06-01 2020-04-21 Tetra Tech, Inc. Apparatus and method for calculating wooden crosstie plate cut measurements and rail seat abrasion measurements based on rail head height
US10870441B2 (en) 2018-06-01 2020-12-22 Tetra Tech, Inc. Apparatus and method for gathering data from sensors oriented at an oblique angle relative to a railway track
US10807623B2 (en) 2018-06-01 2020-10-20 Tetra Tech, Inc. Apparatus and method for gathering data from sensors oriented at an oblique angle relative to a railway track
US11305799B2 (en) 2018-06-01 2022-04-19 Tetra Tech, Inc. Debris deflection and removal method for an apparatus and method for gathering data from sensors oriented at an oblique angle relative to a railway track
US11377130B2 (en) 2018-06-01 2022-07-05 Tetra Tech, Inc. Autonomous track assessment system
US10730538B2 (en) 2018-06-01 2020-08-04 Tetra Tech, Inc. Apparatus and method for calculating plate cut and rail seat abrasion based on measurements only of rail head elevation and crosstie surface elevation
US11560165B2 (en) 2018-06-01 2023-01-24 Tetra Tech, Inc. Apparatus and method for gathering data from sensors oriented at an oblique angle relative to a railway track
US11919551B2 (en) 2018-06-01 2024-03-05 Tetra Tech, Inc. Apparatus and method for gathering data from sensors oriented at an oblique angle relative to a railway track
US10908291B2 (en) 2019-05-16 2021-02-02 Tetra Tech, Inc. System and method for generating and interpreting point clouds of a rail corridor along a survey path
US11169269B2 (en) 2019-05-16 2021-11-09 Tetra Tech, Inc. System and method for generating and interpreting point clouds of a rail corridor along a survey path
US11782160B2 (en) 2019-05-16 2023-10-10 Tetra Tech, Inc. System and method for generating and interpreting point clouds of a rail corridor along a survey path

Also Published As

Publication number Publication date
JP2018188094A (en) 2018-11-29

Similar Documents

Publication Publication Date Title
WO2018207469A1 (en) Abnormality detection system
US9969508B2 (en) Aircraft LRU data collection and reliability prediction
US9823311B2 (en) System to identify potential electrical network faults combining vibration and power quality analysis
CN112134357A (en) Power distribution automation master station system based on cloud service
CN103607295A (en) Alarm processing method and alarm system
CN102404141A (en) Method and device of alarm inhibition
JP6530252B2 (en) Resource management system and resource management method
US20200278668A1 (en) Methods and systems for infrastructure-monitoring control
CN104777398A (en) Method and device for insulation monitoring including alarm diagnosis display
JP2017167708A (en) Maintenance system and maintenance method
KR20210044657A (en) Method of preserving the prediction of a device through distribution chart
CN100573512C (en) Be used to transmit the emission-monitoring system and the method for data
KR20140088712A (en) System for monitoring access to personal information and method therefor
KR101023533B1 (en) Automatic train control real time remote restore system and its control method thereof
JP6988727B2 (en) Maintenance task management device and maintenance task management method
CN202282059U (en) Alarm information prompt apparatus
KR101879943B1 (en) Tunnel traffic safety prevent disasters integrated management apparatus and method
CN107045094B (en) A kind of distribution line failure localization method and device
US8130001B1 (en) System and method for detecting a protective device has limited or interrupted current it carries
JP2019139556A (en) Maintenance management device, system, and program
JP2010108282A (en) Station service system
KR20210000540A (en) Method for maintaining the predictive value of the device of the control output signal
CN111782437B (en) Fault positioning method, device, computing equipment and medium
KR102246425B1 (en) System and Method for Detcting Fire of in advance
JP2008211313A (en) Monitor console with fault predicting function

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18798661

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18798661

Country of ref document: EP

Kind code of ref document: A1