GB2505381A - Operation Management system and alarm output system - Google Patents

Operation Management system and alarm output system Download PDF

Info

Publication number
GB2505381A
GB2505381A GB1322205.4A GB201322205A GB2505381A GB 2505381 A GB2505381 A GB 2505381A GB 201322205 A GB201322205 A GB 201322205A GB 2505381 A GB2505381 A GB 2505381A
Authority
GB
United Kingdom
Prior art keywords
alarm
terminal
output
server
network
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
GB1322205.4A
Other versions
GB2505381B (en
GB201322205D0 (en
GB2505381B8 (en
Inventor
Rie Naito
Atsushi Nabeshima
Takumi Fushiki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
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 Hitachi Ltd filed Critical Hitachi Ltd
Publication of GB201322205D0 publication Critical patent/GB201322205D0/en
Publication of GB2505381A publication Critical patent/GB2505381A/en
Publication of GB2505381B publication Critical patent/GB2505381B/en
Application granted granted Critical
Publication of GB2505381B8 publication Critical patent/GB2505381B8/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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 trains
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B61RAILWAYS
    • B61LGUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/50Trackside diagnosis or maintenance, e.g. software upgrades
    • B61L27/53Trackside diagnosis or maintenance, e.g. software upgrades for trackside elements or systems, e.g. trackside supervision of trackside control system conditions

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Debugging And Monitoring (AREA)
  • Train Traffic Observation, Control, And Security (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The objective of the present invention is to provide an alarm output system and an operation management system that prevent user confusion and automatically stop an alarm with a simple system configuration when a network failure has occurred. The alarm output system is provided with: a server that detects abnormalities in on-site installations connected via a network or detects failure of the network, and transmits an alarm output command; and an alarm terminal that receives the alarm output command from the server via a second network, and outputs an alarm to a user. The alarm output system is characterized by the alarm terminal stopping output of the alarm to the user when the alarm output command has not been received from the server for at least a predetermined time period.

Description

DESCRIPTION
Title of Invention: OPERATION CONTROL SYSTEM AND ALARM OUTPUT
SYSTEM
Technical Field
[0001] The present invention relates to an operation control system and an alarm output system that output an alarm when abnormality has occurred.
Background Art
[0002] A train operation control system is a system that collects the drive states of signals placed on the on-site side, train location information, and the like, and performs overall control of the operation of trains. Here, when a failure or abnormality has occurred in equipment on the on-site side, for example, as described in PTL 1, a system having detected abnormality information outputs an alarm to inform a commander of the abnormality.
Citation List Patent Literature [0003] PTL 1: JP 10-147242 A
Summary of Invention
Technical Problem 10004] For an exemplary configuration of a general control system for railroads, there is a system configured to allow the server side to control the output to a terminal and the input from the terminal, e.g., a server placed in a server room or the like outputs information, such as a display screen and audio, to a terminal placed in a command room, and the terminal simply outputs the received output information onto, for example, a display screen. It is considered that the system is configured such that upon occurrence of abnormality such as that described in PTL 1, in order to prevent a user such as a commander from missing an accident due to the user not being aware of the abnormal state, an alarm screen and alarm sound are continuously output to the terminal placed in the command room until the user confirms them.
[0005] Here, in the case in which, as described above, the system is configured to allow the server side to control the output to the terminal and the input from the terminal, once alarm information has been received if rom the server, when a network failure between the server and the alarm terminal has occurred thereafter, user' s alarm confirmation cannot be transmitted to the server. Thus, there is a possibility that despite the fact that the alarm has been confirmed, an alarm output such as alarm sound may continue. By this, there is a possibility that the user may get confused due to the continuation of an uncertain alarm.
[0006] In addition, a configuration is considered in which the terminal side that issues an alarm is provided with means for monitoring the connection status with the server at all times, and upon a network failure, an alarm output stops in order to prevent an uncertain alarm output. However, since the system on the terminal side becomes complex, such a configuration is not desirable.
[0007] An obj ect of the present invention is therefore to provide an operation control system and an alarm output system, in which upon occurrence of a network failure, an alarm stops automatically with a simple system configuration, preventing user confusion.
Solution to Problem [0008] To solve the above-described problems, for example, configurations described in the claims are adopted.
[0009] The present application includes a plurality of means for solving the above-described problems, and an example thereof is an alarm output system including: a server that detects abnormality in on-site equipment connected thereto through a network or a failure of the network, and transmits an alarm output instruction; and an alarm tenn!nal that receives the alarm output instruction from the server through a second network, and outputs an alarm to a user, wherein the alarm terminal stops outputting the alarm to the user when the alarm terminal has not received the alarm output instruction from the server for a predetermined period of time or more.
Advantageous Effects of Invention [0010] According to the present invention, a terminal that outputs an alarm outputs an alarm in response to an alarm request from a server on a one-by-one basis. Thus, upon occurrence of a network failure, the alarm stops automatically. By this, user confusion due to a continuation of an uncertain alarm output can be prevented.
Brief Description of Drawings
[0011] [FIG. 1] FIG. 1 is a system configuration diagram of an alarm output system (first eithodiment).
[FIG. 2] FIG. 2 isasequence diagramof the present alarm output system (first embodiment).
(FIG. 3] FIG. 3 is a sequence diagram of the present alarm output system upon a network failure (first embodiment).
[FIG. 4] FIG. 4 isaflowchartofthepresentalarmoutput system (first embodiment).
(FIG. 5] FIG. 5 is a flowchart of an alarm processing unit of the present alarm output system (first embodiment).
[FIG. 6] FIG. 6 is a system configuration diagram of an alarm output system (a network failure detecting unit is added) (second embodiment).
(FIG. 7] FIG.7 isasequence diagramof the present alarm output system upon a network failure (second embodiment).
[FIG. 8] FIG. 8 is a system configuration diagram of an alarm output system (a plurality of terminals) (third embodiment).
[FIG. 9] FIG. 9 is a system configuration diagram of an alarm output system (with alarm level selection) (fourth embodiment).
[FIG. 10] FIG. 10 is a flowchart of the present alarm output system (fourth embodiment).
[FIG. 11] FIG. 11 is a flowchart of an alarm processing unit of the present alarm output system (fourth embodiment).
[FIG. 12] FIG. 12 is a system configuration diagram for the case in which the present alarm output systems are connected to each other by a network (fifth embodiment).
Description of Embodiments
10012] Details of systems of the present invention will be described in detail below using embodiments, but the scope of the present invention is not limited thereto.
First Embodiment [0013] FIG. 1 is a configuration diagram of an alarm output system of the present invention. In the present embodiment, description is made using an example in which an alarm output system of the present invention is applied to a train operation control system.
[0014] A server 100 provided in a central system has a communication receiving unit 103 that receives through a network 119 information from station systems 120 set up at respective stations; an output determining unit 104 that makes an alarm output determination from the information received by the communication receiving unit 103, and makes an alarm output request; a screen creating unit 105 that creates an alarm message to be output onto a screen, in response to the alarm output request from the output determining unit 104; a screen transmitting unit 106 that creates an alarm output screen from the alarm message created by the screen creating unit 105, and transmits generated screen data; a sound output requesting unit 107 that makes an alarm sound output request to a terminal A 101, in response to the alarm output request from the output determining unit 104; an alarm confirming unit 108 that accepts from the terminal 101 that an alarm has been confinned; and a communication transmitting and receiving unit 110 that transmits and receives data to/from the terminal A 101. A network 102 connects the server 100 to the terminal A 101.
[0015] The terminal A 101 placed on a command console has a communication transmitting and receiving unit 111 that transmits and receives data to/from the server 100; a screen output unit 112 that displays alanu messages and alarm screens; a sound output unit 113 that outputs alarm sound; an input interface 114 that accepts an input from a user such as a commander; and an abnormality confirming unit 115 that accepts confirmation from the commander. In addition, though not shown, the terminal A 101 is provided with an alarm confirmation button, and a signal indicating that an alarm has been confirmed is input thereto through the input interface 114.
[0016] Each of the station systems 120 provided at the respective stations has on-site equipment 124 including signals and switches for controlling the paths of trains in a control area, a track circuit that detects the location of a train, etc.; an interlocking apparatus 122 that provides a drive instruction to the on-site equipment 124; a path control apparatus 121 that provides path control instructions to the interlocking apparatus to control the paths of trains in the control area based on operation diagram information received from the aforementioned central system; and a station system terminal 123 that displays the current operation conditions from the path control apparatus 121.
[0017] Upon occurrence of an alarm, the communication receiving unit 103 of the server 100 receives alarm information from a station system 120 present in a remote location. The alarm information from the station system 120 is, for example, a malfunction or abnormality information of the on-site equipment 124 or the interlocking apparatus 122. In addition, when the network 119 undergoes a network failure, too, the communication receiving unit 103 detects alarm information.
[0018] The output determining unit 104 having received the alarm information from the communication receiving unit 103 repeatedly requests the screen creating unit 105 and the sound output requesting unit 107 to output an alarm, according to the received alarm information. At this time, the output determining unit 104 continues the alarm output request until receiving an alarm stop request from the alarm confirming unit 108.
[0019] The screen creating unit 105 creates an alarm message to be output onto a screen of the terminal A 101, from the alarm information. The screen transmitting unit 106 creates a screen containing the alarm message and transmits generated screen data to the terminal A 101. The sound output requesting unit 107 sends a sound output request message to the terminal A 101 through the network 102 to allow the terminal to output sound.
The communication transmitting and receiving unit 110 transmits the screen data and the sound output request message to the terminal A 101, and receives a response from the terminal A 101.
The communication transmitting and receiving unit ill receives the screen data and the sound output request message from the server 100, and transmits a response to the server 100 from the terminal A 101.
[0020] The command console has the terminal A 101 placed thereon, and the screen output unit 112 of the terminal A 101 displays the alarm message and alarm screen transmitted from the server, on the screen of the terminal A 101. By thus performing the process of creating an alarm output screen by the server 100 instead of by the side of the terminal A 101, the configuration of the terminal A 101 can be simplified. In addition, the sound output unit 113 receives the sound output request message requested by the server, and outputs alarm sound from the terminal according to the message. It is assumed that an alarm sound file is held on the terminal, but it may be distributed from the server 100 through the network 102.
[0021] As such, by the alarm screen and alarm sound output from the terminal A 101, a commander at the command console can be made aware of abnormality of the on-site equipment 124, etc. The alarm confirmation button is provided on the screen of the terminal A 101, and can accept alarm confirmation from the commander having confirmed an alarm. The input interface 114 sends a response to the abnormality confirming unit 115 when a user presses the alarm confirmation button displayed on the screen of the terminal. The abnormality confirming unit 115 informs the server of the fact that the alarm has been confirmed on the terminal A 101.
[0022] When the alarm confirmation button placed on the terminal is pressed, the alarm confirming unit 108 of the server detects that the alarm has been confirmed on the terminal, and makes a stop request to the output determining unit 104 to stop the alarm output. The output determining unit 104 having received the stop request stops the alarm output request having been output continuously. The terminal A 101 stops the output of the alarm screen and the alarm sound along with the stop of the alarm output request from the server 100.
[0023] As such, the server 100 continuously transmits an alarm output request to the terminal A 101 until certainly detecting that the user (commander) has confirmed an alarm. Thus, the user can be prevented from missing an alarm, enabling to securely allow the user to confirm an alarm. In addition, the server 100 can also be configured to detect by the communication receiving unit 103 that abnormality from a station system 120 has been resolved, upon which an alarm output request made by the output determining unit 104 stops. By this, a situation can be prevented where an alarm is output despite the fact that the cause of the alarm has been resolved, confusing the user.
[0024] In addition, upon a network failure between the server and the terminal A 101, alarm output requests are transmitted to the terminal A 101 from the screen transmitting unit 106 and the sound output requesting unit 107 of the server 100, but due to the failure of the network 102 the alarm output requests are not received by the terminal A 101 and thus an alarm output from the terminal A 101 stops. Upon network recovery, the terminal A 101 can receive alarm output requests transmitted from the screen transmitting unit 106 and the sound output requesting unit 107 of the server 100, and thus can output an alarm again.
[0025] That is, in the present embodiment, in a state in which the server 100 cannot receive alarm confirmation from the user, i.e., upon a network failure, an alarm output stops automatically, and when the network has recovered and the server goes into a state of being able to receive alarm confirmation from the user, an alarm is output again. By this, since an alarm output from the terminal A 101 is considered to be an alarm whose alarm confirmation has not yet been made by the user, user confusion due to a continuation of an uncertain alarm can be prevented. In addition, it is considered that when the terminal A 101 outputs an alarm, the server 100 always recognizes alarm information. Thus, the user can certainly detect an alarm that reflects the current conditions.
[0026] FIG. 2 is a sequence diagram showing the flow of processes from when abnormality is detected in the present system in FIG. 1 and an alarm is output from the terminal A 101 until the user confirms the alarm thereafter and stops the alarm output.
[0027) First, the server 100 receives alarm output information [S400]. The server having received the alarm output information starts an alarm output process [S401] and repeatedly requests the terminal A 101 for an alarm output, through the network 102 every any second(s) (repeatedly requests for display of alarm characters and an alarm confirmation button and for an alarm sound output) [3402, 3404, and 3406]. The terminal A 101 having received the requests outputs an alarm for a predetermined period of time every time the terminal A 101 receives an alarm output request (displays alarm characters and an alarm confirmation button on the terminal and plays back alarm sound) [S403, 3405, and 3407].
Here, the period of time during which the alarm is output can be set in advance to any period of time. When the user clicks the confirmation button displayed on a monitor of the terminal A 101 with a mouse connected to the terminal A 101 [3408], a confirmation response is transmitted from the mouse to the terminal A 101 [3409], and the terminal A 101 having received the confirmation response transmits an alarm output stop request to the server 100 [3410]. The server 100 having received the alarm output stop request stops the alarm output process [3411]. The alarm output from the terminal A 101 stops automatically after a lapse of the playback length of the alarm sound from [3403] (the alarm characters and the alarm confirmation button are hidden on the command console, and the alarm sound stops [S412] [0028] As such, in the present enthodiment, an alarm output request from the server 100 and an alarm output from the terminal A 101 have one-to-one correspondence. Specificafly, if an alarm output request is continuously received from the server 100, then an alarm is continuously output from the terminal A 101, but when reception of the alarm output request from the server 100 stops, the alarm stops automatically. By this, since an alarm is output from the terminal A 101 so as to reflect abnormality information that is currently recognized by the server, user confusion can be prevented. In addition, the configuration of the terminal A 101 can be such that focusing on the reception intervals of an alarm output request from the server 100, when an alarm output request has not been received for a predetermined period of time, an alarm output stops.
[0029] FIG. 3 is a sequence diagram showing the flow of processes from when abnormality (alarm) is detected in the present system in FIG. 1 and an alarm is output from the terminal A 101 and thereafter a failure occurs in the network 102 between the server 100 and the command console, until, upon recovery of the network 102, the user confirms the alarm and stops the alarm output.
[0030) First, the server 100 receives alarm output information [S500]. The server 100 having received the alarm output information starts an alarm output process [S501] and repeatedly requests the terminal A 101 for an alarm output every any second(s) (requests for display of alarm characters and an alarm confirmation button and for an alarm sound output) [5502 and 6504]. The terminal A 101 having received the requests outputs an alarm (displays alarm characters and an alarm confirmation button on the terminal and plays back alarm sound) [5503 and 5505]. After the alarm output at 5505, a failure occurs in the network 102 between the server 100 and the command console [3506]. After a lapse of any second after the alarm output request at 5504, an alarm output is requested to the terminal A 101 again [S507a and S507b].
[0031] However, since the network failure between the server 100 and the terminal A 101 is occurring, the terminal A 101 cannot receive the alarm output request and thus the alarm output from the terminal A 101 stops automatically (3507c]. After network recovery [6510], the terminal A 101 receives an alarm output requested by the server [S513], and outputs an alarm [5514).
When the user clicks the confirmation button displayed on the monitor of the terminal with the mouse connected to the terminal A 101 [5515], a confirmation response is transmitted from the mouse to the terminalA 10]. [S516], and the terminalA 101 having received the confirmation response transmits an alarm output stop request to the server 100 [6517]. The server 100 having received the alarm output stop request stops the alarm output process (6518]. The alarm output from the terminal A 101 stops (the alarm characters and the alarm confirmation button are hidden on the terminal, and the alarm sound stops [S519].
[0032] As such, when a network failure occurs and thus the server cannot receive alarm confirmation from the user, the terminal A 101 automatically stops an alarm output. By this, a situation can be prevented where the terminal A 101 continues alarm sound despite the fact that the user has confirmed an alarm, confusing the user by uncertain alarm sound. In addition, if abnormality still continues upon recovery of the network, then the terminal A 101 receives an alarm output request from the server 100 again and outputs an alarm to the user. Thus, the user can securely confirm the current abnormal conditions.
[0033] In addition, the configuration can be such that a history of alarms having been output once is displayed on the terminal A 101. By this, even when alarm sound is not output, the user can confirm abnormality by looking at the screen of the terminal A 101.
[0034] FIGS. 4 and 5 are flowcharts showing the flow of processes from when an alarm is detected in the present system in FIG. 1 and an alarm is output from the terminal A 101 until the user confirms the alarm thereafter and stops outputting the alarm.
[0035] In FIG. 4, first, it is determined whether the server 100 has received alarm output information [S 600]. If alarm output information has been received, then the server 100 performs an alarm output process (S602].
[0036] FIG. 5 is a flowchart showing the flow of the alarm output process. In the alarm output process in FIG. 5, alarm characters to be displayed on a screen are created by the screen creating unit 105 [5702], and an alarm character string to be displayed on the screen is transmitted from the screen transmitting unit of the server 100 [S703]. In addition, the sound output requesting unit of the server requests the terminal A 101 to play back alarm sound [5704]. The screen output unit of the terminal A 101 displays the alarm character string transmitted at S703 on the screen [S705]. The sound output unit of the terminal A 101 plays back the alarm sound requested at 5704 from a speaker connected to the terminal A 101 [5706].
[0037] Then, the process transitions to an alarm loop in FIG. 4. The alarm loop is repeated endlessly until user confirmation [S607] is made by an abnormality confirmation determining unit of the server [5606] [5603 to 5609]. The abnormality confirmation determining unit of the server [S606] determines whether the user has confirmed the alarm on the terminal [5607].
If the user has not confirmed the alarm, then an alarm output process is performed [5608]. If the user has confirmed the alarm, then the process leaves the alarm loop and the alarm output is terminated.
10038] By the above-described processes, the user can certainly detect an alarm that reflects the current conditions, with a simple system configuration and processes. In addition, the user can stop and detect an alarm without any special operation.
Second Embodiment [0039] Examples of when an alarm occurs and when a network failure occurs for the case of a server 100 of the first embodiment including a network failure detecting unit will be described.
[0040] FIG. 6 is a system configuration diagram for the case of a server 100 of the present alarm output system including a network failure detecting unit 109. Differences from FIG. 1 will be described below. Upon occurrence of a network failure between the server 100 and a terminal A 101, the network failure detecting unit 109 of the server 100 detects the network failure, and transmits network failure information to an output determining unit 104. By the output determining unit 104 receiving the network failure information and stopping an alarm output request, an alarm sound output from the terminal A 101 stops automatically. In addition, upon network recovery, the network failure detecting unit 109 transmits to the output determining unit 104 information indicating that a network between the server 100 and the terminal A 101 is normal, and the terminal A 101 outputs an alarm again.
[0041] FIG. 7 is a sequence diagram showing the flow of processes from when alarm output information is detected in the system having the configuration shown in FIG. 6 and an alarm is output from the terminal and thereafter a network failure between the server and a command console occurs, until, upon recovery of the failure, a user confirms the alarm and stops the alarm output.
[0042] Differences from FIG. 3 will be described belcw. When, after occurrence of a network failure between the server and the command console 1S506], an alarm output request is transmitted from the server to the terminal [S507], due to the occurrence of the network failure, the terminal cannot receive the request, and thus, the server receives a network failure occurrence notification [S508]. The server having received the notification stops the alarm output process [S509]. After network recovery ESS1O], the server receives a network recovery notification (5511] and starts an alarm output process [5512].
[0043] By thus stopping transmission of an unnecessary alarm output request from the server upon network disconnection, unnecessary information conuuunication can be eliminated, enabling to improve the performance of the system.
Third Embodiment [0044] In the present embodiment, an embodiment for the case in which the present alarm output system has a plurality of terminals will be described.
[0045] FIG. 8 is a system configuration diagram for the case in which the present alarm output system has a plurality of terminals. Differences from FIG. 6 will be described below.
An output terminal determining unit 104a of a server 100 determines a terminal (a terminal A 101, a terminal B 116, a terminal C 117, or a terminal D 118) that outputs an alarm among terminals that can normally communicate with the server through a network 102, and requests the terminal to output an alarm until a user confirms the alarm through any of the terminals. The network 102 connects the server 100 to the terminal A 101, the terminal B 116, the terminal C 117, and the terminal D 118. In addition, the terminal A 101, the terminal B 116, the terminal C 117, and the terminal D 118 are placed in the same command room. Though not shown, the internal configurations of the terminal B 116, the terminal C 117, and the terminal D 118 are the same as that of the terminal A 101, and the terminal B 116, the terminal C 117, and the terminal D 118 each are provided with an alarm confirmation button.
10046] Upon occurrence of an alarm, a communication receiving unit 103 of the server receives alarm information from a station system 120 placed in a remote location. The output terminal determining unit 104a determines a terminal (the terminal A 101, the terminal B 116, the terminal C 117, or the terminal D 118) that outputs an alarm among terminals that can normally communicate with the server through the network 102, and requests the terminal to output an alarm until the user confirms the alarm or a network failure occurs. A screen creating unit creates an alarm message to be output onto a screen. A screen transmitting unit 106 sends generated screen data to the terminal determined by the output terminal determining unit 104a, through the network 102. A sound output requesting unit 107 sends a request message to the terminal through the network 102 to allow the terminal to output sound in accordance with an alarm level. A communication transmitting and receiving unit 110 transmits the screen data and the sound output request message to the terminal, and receives a response from the terminal to the server.
[0047] A communication transmitting and receiving unit 111 of the terminal A receives the screen data and the sound output request message from the server and transmits a response to the server from the terminal. A screen output unit 112 displays the alarm message transmitted from the server, on a screen of the terminal. A sound output unit 113 outputs alarm sound requested by the server, from the terminal. When an alarm confirmation button displayed on the screen of the terminal is pressed, an input interface 114 sends a response to an abnormality confirming unit 115. The abnormality confirming unit 115 informs the server of the fact that the alarm has been confirmed on the terminal.
[0048] An alarm confirming unit 108 of the server detects that the alarm has been confirmed on the terminal, and stops the alarm output. A network failure detecting unit 109 monitors communication over the network 102 and monitors terminals that can output an alarm.
[0049] Upon occurrence of a network failure between the network 102 and the terminal outputting an alarm, the network failure detecting unit 109 of the server 100 detects abnormality and transmits to the output terminal determining unit 104a terminal information that undergoes the network trouble. In the case of the occurrence of a network failure between the network 102 and the terminal A 101, the output terminal determining unit 104a selects the connectable terminal B 116 from terminal information list data which is registered in advance, and outputs an alarm again. When the alarm has been confirmed on the terminal B 116 to which the alarm has been output again, the alarm output stops. When a network failure has occurred in the terminal B 116 to which the alarm has been output again, a terminal that can issue an alarm is selected again by the output terminal determining unit 104a, and an alarm output is performed on another terminal C. In the present system that repeatedly performs this process, even when a network failure between the network 102 and a terminal occurs, an alarm can be continuously output from a terminal connected to the server 100, and the alarm can be output until the user confirms the alarm, enabling the user to certainly detect the alarm. In addition, it is also possible that the server 100 detects not only a terminal in which a network failure has occurred, but also failures of the terminal A 101 to the terminal D 118, and makes an alarm output request to a normal terminal.
[0050] In the present example, the configuration is such that a network failure on a terminal-by-terminal basis is detected and an alarm output request is made to a normal terminal.
However, it is also possible that, for example, when an alarm output request is made to the terminal A 101 first but there has been no confirmation from the user for a fixed period of time or more, the output destination of the alarm output request is automatically changed to the terminal B 116. In addition, the order in which terminals are changed can be stored in the server 100 in advance. By this, even when the user cannot recognize an alarm on a certain terminal, since a terminal to output an alarm is sequentially changed, the user can certainly detect an alarm.
Fourth Embodiment [0051] In the present embodiment, an example of the case in which the present alarm output system has a plurality of terminals and an alarm level is selectable will be described.
[0052] FIG. 9 is a system configuration diagram of an alarm output system of the present system (with alarm level selection).
FIG. 9 has an alarm level output determining unit 104b in addition to the configuration of a server 100 in FIG. 8. The alarm level output determining unit 104b accepts, as input, an alarm received by a communication receiving unit 103 and determines an alarm level for each terminal which is selected by an output terminal determining unit 104a, and requests a screen creating unit 105 and a sound output requesting unit 107 for an alarm output. By the alarm level determined here, the types (character color, character size, etc.) of the alarm output to be displayed on a screen and whether to play back alarm sound, the type of alarm sound, and the length of playback (continue until a confirmation button is pressed/only a length of alarm sound of N second(s)/a set length of MXN second(s)) are determined, and an alarm output is requested to the screen creating unit 105 and the sound output requesting unit 107. In the case of no playback of alarm sound, the time during which display is requested repeatedly is set arbitrarily (set to N second(s)), and an alarm output is requested to the screen creating unit 105 and the sound output requesting unit 107.
[0053] FIGS. 10 and 11 are flowcharts showing the flow of processes from when abnormality is detected in the present system in FIG. 9, and a server selects an alarm level for each received alarm and changes, by the alarm level, whether to give alarm sound which is output from a terminal, the type of the alarm sound, and the length of playback of the alarm sound, until a user confirms an alarm thereafter and stops an alarm output.
[0054] In FIG. 10, first, it is determined whether the server has received alarm output information [S 600]. If alarm output information has been received, then the server performs an alarm output process [5602].
[0055] FIG. 11 is a flowchart showing the flow of the alarm output process. In the alarm output process, the terminal output determining unit selects a terminal that outputs an alarm [S601].
Selectable terminals are only those for which a terminal abnormal flag is not set by a network failure detecting unit at S604. As used herein, the abnormal flag refers to a terminal in which a network failure has occurred, or a terminal that itself has failed. Then, the alarm level output determining unit selects an alarm level by the alarm output information received at S600 [3700]. Bytheselectedalarmlevel, selection of character color to be displayed on a screen and whether to playback alarm sound, the type of the alarm sound, and the length of playback (continue until a confirmation button is pressed/only a length of alarm sound of N second(s) / a set length of MxN second(s)) are determined. In the case of no playback of alarm sound, the time during which display is requested repeatedly is set arbitrarily (set to N second(s)). Then, if there is an alarm sound output, based on the alarm level determined by the alarm level output determining unit at S700 [S701], then the screen creating unit creates alarm characters to be displayed on the screen [S702], and a screen transmitting unit transmits a character string to be displayed on the screen from the server to the terminal selected at 3700 [3703]. In addition, a request to play back alarm sound is made from the server to the terminal by the sound output requesting unit [3704]. A screen output unit of the terminal displays the alarm character string transmitted at S703 on the screen [3705]. A sound output unit of the terminal plays back the alarm sound requested at 3704, from a speaker connected to the terminal [3706]. If there is no alarm sound output [3701], then processes where the processes at S704 and 3706 are excluded from the case in which there is an alarm output are performed [3707, 3708, and 3709] [0056] Then, in FIG. 10, an alarm loop is performed every N second(s) which is the length of playback of alarm sound determined at S700, or at intervals according to a specified repetition time of N second(s) [3603 to 3609]. The network failure detecting unit (S604] determines whether a network between the server and terminals is normal [S605]. If abnormal, then a flag is set for a terminal in which a network failure is occurring [3605b]. Then, an abnormality confirmation determining unit (3606] determines whether a user has confirmed the alarm on the terminal [3607]. If the user has not confirmed the alarm, then an alarm output process is performed [3608].
If the user has confirmed the alarm, then the process leaves the alarm loop and the alarm output is terminated.
[0057) According to the present embodiment, upon occurrence of an alarm, the user can set any alarm level for each alarm or each terminal and select, for each alarm level, the types of alarm screen display and alarm sound to be output. In addition, it is also possible that, depending on the alarm level, a plurality of terminals is selected and an alarm output request is transmitted thereto.
Fifth Eltodiment [0058] In the present embodiment, an example of the case in which the present systems are connected to each other by a network will be described.
[0059] FIG. 12 is a system configuration diagram for the case in which the present systems are connected to each other by a network. A server Y 800 and a server Z 807 have the same configuration as a server 100 in FIG. 9. A network 801 and a network 808 are the same as a network 102 in FIG. 1. A terminal A 802, a terminal B 803, a terminal C 804, a terminal D 805, a terminal 0 810, a terminal P 811, a terminal Q 812, and a terminal P. 813 have the same configuration as a terminal A 101 in FIG. 1. A network 806 connects the server Y 800 to the server Z 807. The network 801 connects the server Y 800 to the terminal A 802, the terminal B 803, the terminal C 804, and the terminal D 805. The network 808 connects the server Z 807 to the terminal 0 810, the terminal p 811, the terminal Q 812, and the terminal P. 813.
[0060] Here, the server Y and the server Z are servers that handle different operation control systems, and the terminal A 802 to the terminal D 805 and the terminal 0 810 to the terminal R 813 may be provided on different floors of the same operation command center, or may be provided on the same floor.
[0061] When the system of the server Y 800 has crashed, the server Z 807 detects the system crash of the server Y 800, and outputs an alarm to the terminals (the terminal 0 810, the terminal P 811, the terminal Q 812, and the terminal R 813) connected to the side of the server Z 807.
[0062] In addition, when a failure has occurred in the network 801, the server Z 807 detects the system crash of the network 801, and outputs an alarm to the terminals (the terminal 0 810, the terminal P 811, the terminal Q 812, and the terminal R 813) connected to the side of the server Z 807.
[0063) The above is also effective for the case in which the server Y 800 is replaced by the server Z 801, and the network 801 is replaced by the network 802.
[0064] According to the present embodiment, in the case in which the present systems are connecced to each other by a network, even when the server Y 800 itself has failed, an alarm output from a terminal connected to the server 1 800 can stop automatically, and an alarm can be output to the side of the server Z 807 which is operating normally. As such, upon a failure of a server itself or upon a failure of the network 801 or the network 808 itself, too, a terminal operating normally can be detected and an alarm can be output.
[0065] As described above, in the present invention, a server controls the output and stop of an alarm to a terminal.
Specifically, when abnormality that causes an alarm has occurred, an alarm output request is continuously output until the server recognizes that a user has confirmed the alarm. This can prevent the user from missing the alarm. Furthermore, when a plurality of terminals is connected, the server detects a terminal that cannot output an alarm, and outputs at alarm to a normal terminal. Thus, user's alarm confirmation can be performed more securely.
[0066) In addition, in the present invention, in a state in which the server cannot receive alarm confirmation from the user, i.e., upon a network failure, an alarm output stops automatically by the above-described configuration. Then, when the network has recovered and the server 100 goes into a state of being able to receive alarm confirmation from the user, an alarm is output again. By this, since an alarm output from a terminal is considered to be an alarm whose alarm confirmation has not yet been made by the user, user confusion due to a continuation of a user-confirmed alarm can be prevented. In addition, since the terminal outputs an alarm for each reception of an alarm output request from the server, the user can certainly detect an alarm relevant to the current conditions.
[0067] In addition, as described above, a terminal that outputs an alarm can be implemented with a simple configuration in which an alarm is output for a fixed period of tine upon reception of an alarm output request. Thus, there is no need to allow the terminal to perform complex processes, and the whole system can be constructed with a simple configuration.
[0068] Although in the above-described first:o fifth embodiments the case is described in which the present invention is applied to a train operation control system, the present system is not limited thereto. The present system can be adapted for, for example, monitoring systems such as power generation systems using nuclear energy, etc., and water supply control systems.
[0069) Note that the present system is not limited to the above-described embodiments and includes various variants.
For example, the above-described embodiments are described in detail to describe the present invention in an easy-to-understand manner, and thus, the system is not necessarily limited to including all of the described configurations. In addition, a part of the configuration of a given embodiment can be replaced by the configuration of another embodiment, or to the configuration of a given embodiment the configuration of another embodiment can be added.
In addition, for a part of the configuration of each embodiment, addition, elimination, or replacement of another configuration can be performed. In addition, for a part of the configuration of each embodiment, addition, elimination, or replacement of another configuration can be performed.
[0070] In addition, a part or all of the above-described configurations, functions, processing units, processing means, etc., may be implemented by hardware by, for example, designing using an integrated circuit. In addition, the above-described configurations, functions, etc., may be implemented by software by a processor interpreting and executing a program that implements the functions. Information such as a program that implements the functions, tables, and files can be placed in a recording apparatus such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC card, an SD card, or a DVD.
[0071] In addition, control lines and information lines which are considered to be necessary for description are shown, and thus, not all control lines and information lines for products are always shown. It can be considered that in practice almost all configurations are connected to each other.
Reference Signs List [0072] server 101 terminal A 102 and 119 network 103 communication receiving unit 104 output determining unit lO4a output terminal determining unit 104b alarm level output determining unit screen creating unit 106 screen transmitting unit 107 sound output requesting unit 108 alarm confirming unit 109 network failure detecting unit communication transmitting and receiving unit (server side) 111 communication transmitting and receiving unit (terminal side) 112 screen output unit 113 sound output unit 114 input interface abnormality confirming unit 116 terminal B 117 terminal C 118 terminal D station system 121 path control apparatus 122 interlocking apparatus 123 station system terminal 124 on-site equipment
GB1322205.4A 2011-06-22 2011-06-22 Operation control system and alarm output system Active GB2505381B8 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/003556 WO2012176234A1 (en) 2011-06-22 2011-06-22 Operation management system and alarm output system

Publications (4)

Publication Number Publication Date
GB201322205D0 GB201322205D0 (en) 2014-01-29
GB2505381A true GB2505381A (en) 2014-02-26
GB2505381B GB2505381B (en) 2015-07-22
GB2505381B8 GB2505381B8 (en) 2015-08-05

Family

ID=47422119

Family Applications (1)

Application Number Title Priority Date Filing Date
GB1322205.4A Active GB2505381B8 (en) 2011-06-22 2011-06-22 Operation control system and alarm output system

Country Status (3)

Country Link
JP (1) JP5657114B2 (en)
GB (1) GB2505381B8 (en)
WO (1) WO2012176234A1 (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08310398A (en) * 1995-05-18 1996-11-26 Toshiba Eng Co Ltd Railroad control system
JPH10147242A (en) * 1996-11-19 1998-06-02 Hitachi Ltd Train operation control system
JP2000127973A (en) * 1998-10-29 2000-05-09 Hitachi Ltd Operation management system
JP2005253233A (en) * 2004-03-05 2005-09-15 Koito Ind Ltd Reception failure determining device and radio signal receiving system, and radio communication system
JP2006260038A (en) * 2005-03-16 2006-09-28 Toyota Motor Corp Vehicle alarm unit
JP2007334797A (en) * 2006-06-19 2007-12-27 Saga Univ Educational system
JP2009126386A (en) * 2007-11-26 2009-06-11 Mitsubishi Electric Corp Train accident detection system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01316899A (en) * 1988-06-17 1989-12-21 Yamato Protec Co Fire alarm system
JP3095116B2 (en) * 1995-09-14 2000-10-03 矢崎総業株式会社 Alarm device and anti-theft device in multiplex communication system for vehicle
JP2001273020A (en) * 2000-03-23 2001-10-05 Denso Corp Control system of production line
JP2010204723A (en) * 2009-02-27 2010-09-16 Toshiba Corp Monitoring system and alarm reporting method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08310398A (en) * 1995-05-18 1996-11-26 Toshiba Eng Co Ltd Railroad control system
JPH10147242A (en) * 1996-11-19 1998-06-02 Hitachi Ltd Train operation control system
JP2000127973A (en) * 1998-10-29 2000-05-09 Hitachi Ltd Operation management system
JP2005253233A (en) * 2004-03-05 2005-09-15 Koito Ind Ltd Reception failure determining device and radio signal receiving system, and radio communication system
JP2006260038A (en) * 2005-03-16 2006-09-28 Toyota Motor Corp Vehicle alarm unit
JP2007334797A (en) * 2006-06-19 2007-12-27 Saga Univ Educational system
JP2009126386A (en) * 2007-11-26 2009-06-11 Mitsubishi Electric Corp Train accident detection system

Also Published As

Publication number Publication date
JPWO2012176234A1 (en) 2015-02-23
GB2505381B (en) 2015-07-22
WO2012176234A1 (en) 2012-12-27
GB201322205D0 (en) 2014-01-29
JP5657114B2 (en) 2015-01-21
GB2505381B8 (en) 2015-08-05

Similar Documents

Publication Publication Date Title
US7836208B2 (en) Dedicated redundant links in a communicaton system
JP5706347B2 (en) Redundant control system
JP2008020969A (en) Process and method for abnormality/trouble report for monitoring control system
GB2505381A (en) Operation Management system and alarm output system
JP5005425B2 (en) Control device return system
JP2006338600A (en) Duplex switching system
JP5755076B2 (en) Remote monitoring system
JP4419617B2 (en) Fault location determination method for multi-loop network
JP5847064B2 (en) Simple monitoring and control device
JP6762032B2 (en) Power receiving device and control method
JP2009187428A (en) Security system
JP5964682B2 (en) Transmission device, transmission device control method, and transmission system
JP6234388B2 (en) Dual system controller
JP5951520B2 (en) Multiple processing system
JP2018153015A (en) Power monitor control system, failure detection device for power monitor control system, program for power monitor control system, and failure detection method for power monitor control system
JP7082493B2 (en) Fire notification system and disconnection detection method
JP2009089229A (en) Equipment monitoring system
JP2006344023A (en) Control unit
JP2014071773A (en) Duplex control device and control method of the same
JP2015115054A (en) Monitoring and control system
JP2013226926A (en) Railway security system
JP2004086698A (en) Communication system and method for detecting communication abnormality
JP2004334548A (en) Failure monitoring system for distributed supervisory control system
JP2020194495A (en) Monitoring apparatus and monitoring system
JP5602071B2 (en) CPU duplex control system