Management Device

Abstract

To shorten a period from a failure of a platform fence to beginning of the fence repair.SOLUTION: An acquisition part 711 acquires movement data indicating a movement from a monitoring device which monitors the movement of a platform fence that blocks the platform from a rail track. A prediction part 713 predicts a timing when the platform fence fails from the acquired movement data. An alarming part 714 not only acquires information on a failure timing from the prediction part 713 but also refers a period table 723 to specify a period required for preparing a repair of the failure. Also, the alarming part 714 issues an alarm at a timing preparing-period earlier than a timing of the predicted failure.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to a technology for monitoring platform fences and predicting their failure. [Background technology]

[0002] Various technologies have been developed to monitor platform fences and diagnose signs of malfunction. Patent Document 1 discloses a platform gate condition diagnosis system that acquires electrical values ​​related to a motor as acquired numerical values ​​when the platform gate is opened or closed using a belt driven by a motor, and determines whether maintenance of the belt is required based on these acquired numerical values. Patent Document 2 also discloses a platform gate condition diagnosis system that acquires vibration information related to the vibration of a drive mechanism when the platform gate is opened or closed by the drive mechanism, and determines whether maintenance is required based on this vibration information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2020-104610 [Patent Document 1] Japanese Patent Application Publication No. 2020-104611 Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, the time required to prepare for repairs of platform gates varies depending on the manufacturer, model, configuration, specifications, settings, operating environment, etc. Furthermore, the availability of parts required for repairs and the availability of repair technicians may change with the seasons. Therefore, even if a certain failure is predicted, the time required for restoration will vary depending on the particular failure.

[0005] One of the objects of the present invention is to shorten the period from when a platform gate breaks down to when repairs can begin. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, the present invention predicts the time when a platform fence that separates the station platform from the tracks will fail based on operation data showing the operation of the platform fence, and issues a warning when the time required to prepare for repairs of the platform fence is calculated from the time when the failure will occur. If there is no malfunction in the platform fence at the time of the warning, or In a first aspect, a management device is provided that, if a malfunction occurs in the platform fence before a warning is issued, extracts predictive data indicating a sign of the malfunction from operational data indicating the operation of the platform fence, and corrects the timing prediction process using the predictive data.

[0007] According to the management device of the first aspect, when issuing a warning about a platform fence failure, the period from when the platform fence fails to when repairs begin can be shortened compared to when the period required to prepare for the repairs is not counted back. Furthermore, according to the management device of the first aspect, it is possible to improve the accuracy of the prediction process by taking into account cases where advance warning of a platform fence failure has not been given.

[0008] In the management device of the first aspect, a configuration may be adopted as a second aspect in which the timing is predicted for each section of the platform fence, and an alert is issued when the period required to prepare for repair of that section is counted back from that timing.

[0009] According to the management device of the second aspect, it is possible to shorten the period from when a part of the platform fence breaks down until repairs for that part begin.

[0010] In the management device of the second aspect, a configuration may be adopted as a third aspect in which an alarm is issued for a failure of each of the parts in an order according to the priority levels set for the parts.

[0011] According to the management device of the third aspect, it is possible to give priority to warnings of malfunctions in important parts, parts that affect the overall operation of the platform fence, and the like.

[0012] In the management device according to any one of the first to third aspects, a fourth aspect may be adopted in which the period includes a time required to arrange for resources necessary for the repair.

[0013] According to the management device of the fourth aspect, it is possible to arrange for the resources required to repair the platform fence before the platform fence breaks down.

[0014] In the management device of the fourth aspect, a configuration may be adopted as a fifth aspect, in which the time required for the arrangement varies depending on the availability of the resource.

[0015] According to the management device of the fifth aspect, resources required to repair the platform fence can be arranged in advance of a breakdown of the platform fence, depending on the availability of the resources.

[0016] In the management device of the fourth or fifth aspect, a configuration may be adopted as a sixth aspect, in which the resources include at least one of parts for the platform fence and a person who repairs the platform fence.

[0017] According to the management device of the sixth aspect, it is possible to arrange for at least one of the parts required to repair the platform fence and the person who will repair the platform fence before the platform fence breaks down.

[0018] In a seventh aspect, a configuration may be adopted in which, in the management device of any one of the fourth to sixth aspects, a repair plan for the platform gate is formulated according to the predicted time and the status of the resource arrangements.

[0019] According to the management device of the seventh aspect, the user can obtain a repair plan according to the timing of predicted failure of the platform gate and the status of resource arrangements.

[0020] In an eighth embodiment, the management device of any one of the first to seventh embodiments may be configured to correct operation data indicating the operation of each of the plurality of platform fences based on the respective positions of the platform fences, predict the time when each of the platform fences will fail from the corrected operation data, and issue a warning when the time required to prepare for repair of the platform fence is counted back from that time.

[0021] According to the management device of the eighth aspect, it is possible to correct the disturbances to which the operation data of the platform fences are subjected based on the positions of the plurality of platform fences, thereby increasing the reliability of the operation data. [Brief explanation of the drawings]

[0024] [Figure 1] 1 is a diagram showing an example of the configuration of a management system 9 according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram showing an example of the configuration of a monitoring device 1. [Figure 3] A diagram showing an example of the configuration of the platform fence 2. [Figure 4] FIG. 2 is a diagram showing an example of the configuration of a control device 3. [Figure 5] FIG. 2 is a diagram showing an example of the configuration of the control panel 4. [Figure 6] FIG. 2 is a diagram showing an example of the configuration of a management device 7. [Figure 7] FIG. 10 is a diagram showing an example of an operation DB 721. [Figure 8] FIG. 7 is a diagram showing an example of a resource DB 722. [Figure 9] FIG. 7 is a diagram showing an example of a period table 723. [Figure 10] FIG. 7 is a diagram showing an example of an arrangement DB 724. [Figure 11] FIG. 2 is a diagram showing an example of the functional configuration of a management device 7. [Figure 12] FIG. 10 is a diagram showing an example of an operation DB 721a in a modified example. [Figure 13] FIG. 10 is a diagram showing an example of a resource DB 722a according to a modified example. DETAILED DESCRIPTION OF THE INVENTION

[0025] <Embodiment> <Management system configuration> 1 is a diagram showing an example of the configuration of a management system 9 according to an embodiment of the present invention. The management system 9 is a system in which a monitoring device 1 monitors the operation of one or more platform fences 2 installed at one or more business establishments P, transmits the monitoring results to a management device 7, and the management device 7 predicts failures of each of the platform fences 2.

[0026] The management system 9 shown in FIG. 1 includes a monitoring device 1, a platform fence 2, a control device 3, an operation panel 4, a relay device 5, a communication line 6, and a management device 7.

[0027] When there are multiple monitoring devices 1, platform gates 2, and control panels 4, etc., they are each represented by adding a hyphen and a serial number to the end of the reference numeral, such as "-1" or "-2," to distinguish them from one another. Therefore, the management system 9 shown in Fig. 1 has n monitoring devices 1 and platform gates 2 that are distinguished by serial numbers from 1 to n (n is an integer of 2 or more), and two control panels 4 that are distinguished by serial numbers 1 and 2.

[0028] 1 connects the monitoring device 1, platform gates 2, control device 3, operation panel 4, and relay device 5 belonging to one business establishment P to the management device 7 via a communication line 6. However, the management system 9 may also connect the monitoring device 1, platform gates 2, control device 3, operation panel 4, and relay device 5 belonging to two or more business establishments P to the management device 7 via the communication line 6, respectively.

[0029] The platform fence 2 is a device that separates the station platform from the tracks under the control of the control device 3. The control device 3 is a device that controls one or more platform fences 2.

[0030] The control panel 4 is a device that receives operations from a train crew member or station attendant (hereinafter also referred to as an operator) to instruct the platform fence 2 to operate. In the management system 9 shown in Fig. 1, for example, the control panel 4-1 is the control panel 4 operated by the train crew member, and the control panel 4-2 is the control panel 4 operated by the station attendant.

[0031] In the management system 9 shown in Figure 1, n platform gates 2, one control device 3, and two control panels 4 are connected in a ring shape, for example, by a so-called daisy chain such as a serial cable. In Figure 1, these serial cables are called communication lines L1. These communication lines L1 connect the platform gates 2, control device 3, and control panel 4 described above so that they can communicate with each other. Note that these n platform gates 2, one control device 3, and two control panels 4 were previously installed in the business establishment P, and are also referred to as the existing equipment group.

[0032] The monitoring devices 1 are installed in association with one or more platform fences 2. The monitoring devices 1 are devices that monitor the operation of the platform fences 2 associated with them.

[0033] The relay device 5 is connected to one or more monitoring devices 1 via a wired or wireless connection, acquires operational data monitored by these monitoring devices 1, and relays (i.e., transmits) the data to the management device 7 via a communication line 6.

[0034] In the management system 9 shown in Fig. 1, one relay device 5 and n monitoring devices 1 are connected by wire or wirelessly in a star shape with the relay device 5 at the center. As shown in Fig. 1, the relay device 5 and the monitoring device 1 are communicatively connected by a communication line L2, which is different from the above-mentioned communication line L1.

[0035] The communication line 6 connects the relay device 5 and the management device 7 so that they can communicate with each other. The communication line 6 may be a local area network (LAN), a wide area network (WAN), the Internet, or a combination of these. The communication line 6 may also include a public switched telephone network (PSTN), an integrated services digital network (ISDN), or the like.

[0036] The management device 7 receives operational data monitored by one or more monitoring devices 1 from the relay device 5 via the communication line 6, aggregates this data, and predicts failures that may occur in the platform fences 2 monitored by each monitoring device 1.

[0037] These n monitoring devices 1, one relay device 5, and management device 7 were not previously installed in the business establishment P, but were all devices added to an existing equipment group. These are also referred to as an additional equipment group.

[0038] <Configuration of monitoring device> 2 is a diagram showing an example of the configuration of the monitoring device 1. The monitoring device 1 has a processor 11, a memory 12, an interface 13, and a sensor control unit 16. These components are connected to each other so that they can communicate with each other, for example, by a bus.

[0039] The processor 11 reads and executes programs stored in the memory 12 to control each part of the monitoring device 1. The processor 11 is, for example, a CPU (Central Processing Unit).

[0040] The memory 12 is a storage means for storing an operating system, various programs, data, etc., which are loaded into the processor 11. The memory 12 includes a RAM (Random Access Memory) and a ROM (Read Only Memory). The memory 12 may also include a solid state drive, a hard disk drive, etc.

[0041] The interface 13 is a wired or wireless interface that communicatively connects the monitoring device 1 to the relay device 5 via a communication line L2 different from the communication line L1. The processor 11 transmits operation data to the relay device 5 via this interface 13.

[0042] The sensor control unit 16 is a controller that is connected to one or more sensors 17 and controls each of the sensors 17. In the drawings, when there are multiple sensors 17 and it is necessary to distinguish between them, they are represented by adding a hyphen and a serial number to the end of the reference numeral, such as "-1" or "-2." The sensor control unit 16 shown in FIG. 2 has four sensors 17, sensor 17-1 to sensor 17-4. The number of sensors 17 that the monitoring device 1 has is not limited to four, as long as it is one or more.

[0043] The sensor 17 monitors various operations of the platform fence 2 associated with the monitoring device 1, generates operation data indicating the operations, and outputs the data to the processor 11. The operation of the platform fence 2 monitored by the sensor 17 is, for example, the number of rotations per unit time of a motor 29, which will be described later. In this case, the sensor 17 may be a tachometer using a strobe, a tachometer using an eddy current, or the like.

[0044] The sensor 17 may also monitor vibrations occurring in various devices (also referred to as driving devices), such as the motor 29, or belts, fences, doors, etc. (not shown) driven by the motor 29, as the operation of the platform fence 2. In this case, the sensor 17 is, for example, an optical, capacitance, piezoelectric, or other type of vibration meter.

[0045] Sensor 17 may also measure the sound emitted from the above-mentioned equipment. Sensor 17 may also measure the temperature of the air around the above-mentioned equipment and platform fence 2. Sensor 17 may also measure the delay time from when motor 29 starts to rotate until when the equipment rotated by motor 29 starts to rotate. Sensor 17 may also measure the load that motor 29 places on the equipment rotated by motor 29.

[0046] Furthermore, the sensor 17 may measure the current and voltage that drive the above-mentioned motor 29. For example, the sensor control unit 16 shown in FIG. 2 is configured to read out operation data such as current values ​​and voltage values ​​from a bus or the like behind the platform fence 2. When the operation data is read out directly from a bus or the like behind the platform fence 2, the monitoring device 1 does not need to have the sensor 17.

[0047] This monitoring device 1 is associated with one platform fence 2, but monitors the operation of the platform fence 2 without being involved in the above-mentioned communication line L1 that connects the platform fences 2. The monitoring device 1 then transmits operation data indicating the results of the monitoring from the interface 13 via the communication line L2 to the relay device 5. The relay device 5 transmits the operation data to the management device 7 via the above-mentioned communication line 6.

[0048] The monitoring device 1 also monitors the rotation speed, vibration, temperature, delay time, load, and sound of the driving equipment measured by the sensor 17 using the sensor control unit 16. The monitoring device 1 also monitors the current value and voltage value supplied from the platform fence 2 to the driving equipment.

[0049] The monitoring device 1 may be operated by a power source different from the power source of the existing facilities. In this case, the monitoring device 1 is driven only by a power source different from the power source of the driving devices described above.

[0050] <Configuration of platform fences> FIG. 3 is a diagram showing an example of the configuration of the platform fence 2. The platform fence 2 has a processor 21, a memory 22, an interface 23, a sensor control unit 26, and a motor control unit 28. These components are connected to each other so that they can communicate with each other, for example, by a bus. Furthermore, the sensor control unit 26 is connected to an opening / closing sensor 27 by a signal line, and the motor control unit 28 is connected to a motor 29 by a signal line.

[0051] The processor 21 reads and executes a program stored in the memory 22 to control each part of the platform fence 2. The processor 21 is, for example, a CPU.

[0052] The memory 22 is a storage means for storing an operating system, various programs, data, etc., which are loaded into the processor 21. The memory 22 includes RAM and ROM. The memory 22 may also include a solid state drive, a hard disk drive, etc.

[0053] The interface 23 is an interface that communicatively connects the platform fence 2 to the control device 3, the operation panel 4, and other platform fences 2 via the communication line L1. The processor 21 exchanges information with the control device 3, the operation panel 4, and other platform fences 2 via this interface 23.

[0054] In addition, the interface 23 provided on one platform gate 2 does not need to be connected to all of the control devices 3, operation panels 4, and other platform gates 2, as long as a ring-shaped network as shown in Figure 1 is formed.

[0055] The sensor control unit 26 is a controller that transmits a control signal issued by the processor 21 to the open / close sensor 27 to control it, and also acquires information on the open / close state of a barrier member (not shown) of the platform fence 2 detected by the open / close sensor 27 and outputs it to the processor 21. The barrier member is, for example, a rod-shaped fence that is installed horizontally and moves up and down, or a door that slides horizontally, etc., that separates the station platform from the tracks.

[0056] The open / close sensor 27 is a sensor that detects the open / closed state of the blocking member of the platform fence 2. The open / close sensor 27 is, for example, a blocking detection sensor that uses infrared rays or the like.

[0057] The motor control unit 28 transmits a control signal issued by the processor 21 to the motor 29 to control it. The motor control unit 28 is also connected to the monitoring device 1 via a signal line, and transmits information such as the current value and voltage value of the power used to drive the motor 29 to the monitoring device 1 via this signal line.

[0058] <Control device configuration> 4 is a diagram showing an example of the configuration of the control device 3. The control device 3 has a processor 31, a memory 32, and an interface 33. These components are connected to each other so that they can communicate with each other, for example, by a bus.

[0059] The processor 31 reads and executes a program stored in the memory 32 to control each part of the control device 3. The processor 31 is, for example, a CPU.

[0060] The memory 32 is a storage means for storing an operating system, various programs, data, etc., which are loaded into the processor 31. The memory 32 includes RAM and ROM. The memory 32 may also include a solid state drive, a hard disk drive, etc.

[0061] The interface 33 is an interface that communicatively connects the control device 3 to the platform fence 2 and the operation panel 4 via the communication line L1. The processor 31 exchanges information with the platform fence 2 and the operation panel 4 via this interface 33.

[0062] It should be noted that the interface 33 provided in the control device 3 does not need to be connected to all of the platform gates 2 and the operation panel 4 as long as the ring-shaped network shown in FIG. 1 is formed.

[0063] <Configuration of the control panel> 5 is a diagram showing an example of the configuration of the operation panel 4. The operation panel 4 has a processor 41, a memory 42, an interface 43, an operation unit 44, and a display unit 45. These components are connected to each other so that they can communicate with each other, for example, by a bus.

[0064] The processor 41 reads and executes a program stored in the memory 42 to control each part of the operation panel 4. The processor 41 is, for example, a CPU.

[0065] The memory 42 is a storage means for storing an operating system, various programs, data, etc., which are loaded into the processor 41. The memory 42 includes RAM and ROM. The memory 42 may also include a solid state drive, a hard disk drive, etc.

[0066] The interface 43 is an interface that communicatively connects the operation panel 4 to the platform fence 2, the control device 3, and other operation panels 4 via the communication line L1. The processor 31 exchanges information with the platform fence 2, the control device 3, and other operation panels 4 via this interface 43.

[0067] It should be noted that the interface 43 provided on the operation panel 4 does not need to be connected to all of the platform gates 2, the control device 3, and other operation panels 4, as long as the ring-type network shown in FIG. 1 is formed.

[0068] The operation unit 44 includes operation buttons, keys, a touch panel, and other operators for issuing various instructions, and receives operations from the operator and sends a signal corresponding to the operation content to the processor 41. This operation is, for example, pressing a key or making a gesture on the touch panel.

[0069] The display unit 45 has a display screen such as a liquid crystal display, and displays images under the control of the processor 41. A transparent touch panel of the operation unit 44 may be placed on top of the display screen. Note that the operation panel 4 does not necessarily have to have the display unit 45. The operation panel 4 may present information to an external device via the interface 43.

[0070] <Configuration of management device> 6 is a diagram showing an example of the configuration of the management device 7. The management device 7 has a processor 71, a memory 72, and an interface 73. These components are connected to each other via, for example, a bus so that they can communicate with each other.

[0071] The processor 71 reads and executes programs stored in the memory 72 to control each part of the management device 7. The processor 71 is, for example, a CPU.

[0072] The interface 73 is an interface that communicatively connects the management device 7 to the relay device 5 shown in Fig. 1 via the communication line 6. The processor 31 exchanges information with the relay device 5 via this interface 73.

[0073] The memory 72 is a storage means for storing an operating system, various programs, data, etc., which are loaded into the processor 71. The memory 72 includes RAM and ROM. The memory 72 may also include a solid state drive, a hard disk drive, etc. The memory 72 also stores an operation DB 721, a resource DB 722, a period table 723, and an arrangement DB 724.

[0074] Fig. 7 is a diagram showing an example of an action DB 721. The action DB 721 is a database that stores action data measured by the sensor 17 of the monitoring device 1. The action DB 721 shown in Fig. 7 has an establishment list 7211, a platform fence list 7212, a sensor list 7213, and an action data table 7214.

[0075] The establishment list 7211 is a list listing establishments where monitoring devices 1 that transmit operation data to the management device 7 are installed. The establishment list 7211 shown in Fig. 7 stores establishment IDs that are identification information for identifying establishments.

[0076] The platform fence list 7212 is provided for each establishment ID listed in the establishment list 7211, and is a list listing the platform fences 2 installed at the establishment identified by that establishment ID. The platform fence list 7212 shown in Fig. 7 stores the platform fence ID, which is identification information for identifying the platform fence 2 described above, in association with the model ID, which is identification information for identifying the model of the platform fence 2.

[0077] The sensor list 7213 is provided for each platform fence ID listed in the platform fence list 7212, and is a list listing the sensors 17 possessed by the monitoring device 1 installed in association with the platform fence 2 identified by that platform fence ID. The sensor list 7213 shown in Fig. 7 stores sensor IDs, which are identification information for identifying the sensors 17 described above.

[0078] The sensor list 7213 also stores the installation information and threshold value of the sensor 17 identified by the sensor ID in association with the sensor ID.

[0079] The installation information in the sensor list 7213 is information relating to the installation of the sensor 17, such as the location where the sensor 17 is installed, the installation state, and the arrangement relative to surrounding objects such as walls, doors, and pillars.

[0080] This installation information may be used to correct operation data measured by a sensor 17 identified by the corresponding sensor ID. For example, when there are multiple sensors 17 placed close enough to affect each other, those sensors 17 may be subjected to a common disturbance from the source of that disturbance. In this case, for example, the operation data is acquired by the management device 7 along with the installation information of the sensor 17 that measured the operation data. The management device 7 may calculate the position of the source of the disturbance and the magnitude of the disturbance from the arrangement of those sensors 17 and the operation data, and may correct each of the above-mentioned operation data by performing a calculation to cancel out the disturbance based on the calculated values.

[0081] The thresholds in the sensor list 7213 are thresholds for determining that the operation data measured by the corresponding sensor 17 is abnormal, and are, for example, upper limits, lower limits, or both.

[0082] This threshold may be expressed by a relational expression with operation data measured by other sensors 17. This relational expression may include installation information of other sensors 17. For example, when there are multiple sensors 17 placed close enough to affect each other, the above-mentioned threshold may reflect the arithmetic mean of operation data measured by these sensors 17. The threshold may be weighted by installation information of the sensors 17 identified by the sensor ID. As a result, the threshold at which operation data measured by the sensors 17 is determined to be abnormal varies depending on the installation information.

[0083] The operation data table 7214 is provided for each sensor ID listed in the sensor list 7213, and is a table that stores operation data measured by the sensor 17 identified by that sensor ID in correspondence with the measurement date and time indicating the date and time the measurement was made.

[0084] Fig. 8 is a diagram showing an example of the resource DB 722. The resource DB 722 is a database that stores, for each model of platform fence 2, information on failures that may occur in that model and information on resources that are required to recover from the failure, in association with each other. The resource DB 722 shown in Fig. 8 has a model ID list 7221 and a resource table 7222.

[0085] The model ID list 7221 is a list of model IDs, which are identification information that identify the model (also called model number, model, etc.) of the platform gate 2. The resource table 7222 is a table that is associated with each model ID listed in the model ID list 7221, and is a table that describes information about malfunctions that may occur in the platform gate 2 of the model identified by that model ID.

[0086] 8 is associated with a model ID "M1," and lists "B1," "B2," etc. as failure IDs that are identification information for failures that can occur at the platform gate 2 of the model identified by this "M1." This resource table 7222 stores prediction conditions and resource information in association with each failure ID.

[0087] The prediction condition is a condition under which a failure identified by a corresponding failure ID is predicted. The prediction condition describes, for example, a combination of sensors 17 that detect operational data exceeding a threshold when the above-mentioned failure occurs. The prediction condition may also store information about the timing of the predicted occurrence of the failure.

[0088] Resource information is information about the resources required to repair a fault identified by the corresponding fault ID. The resources referred to here are parts for the platform fence 2 and the person who repairs the platform fence 2. The resource may be at least one of these. The parts for the platform fence 2 include the parts that make up the platform fence 2 itself after repair, as well as the energy and materials consumed during the repair. The person who repairs the platform fence 2 may include not only the technician who directly performs the repair, but also a supervisor who supervises the technician. In other words, the resources referred to here are an example of resources that include at least one of parts for the platform fence and the person who repairs the platform fence.

[0089] FIG. 9 is a diagram showing an example of the period table 723. The period table 723 is a table that describes, for each resource, the period required to prepare that resource. The period table 723 shown in FIG. 9 stores resource type IDs in association with periods. In this period table 723, the resource type ID is identification information that identifies the type of resource, such as the model number of a part of the platform fence 2 or the qualifications required of a technician who repairs the platform fence 2.

[0090] In this period table 723, the period is the period required to prepare the resource identified by the corresponding resource type ID (also called the preparation period), and includes, for example, the time required to arrange the resource. The time required for arrangement is the time from ordering the resource to receiving it. In other words, the period described in this period table 723 is an example of a period that includes the time required to arrange the resources required for repair. Once the preparation of all resources required to repair a certain failure has been completed, the repair can begin.

[0091] Furthermore, the period table 723 may be rewritten depending on the actual availability of resources. In this case, the processor 71 obtains information on the availability of resources from external devices via the communication line 6 and the interface 73, and each time the processor 71 obtains information, it overwrites the periods in the period table 723 based on that information. In other words, the periods described in the period table 723 are examples of periods that change depending on the availability of the resource identified by the corresponding resource ID, and that include the time required to arrange the resource.

[0092] The periods listed in the period table 723 may include the time required for pre-processing of the resource. This pre-processing is a process for making the resource available for repair.

[0093] Fig. 10 is a diagram showing an example of the arrangement DB 724. The arrangement DB 724 is a database that stores information about predicted and warned failures and the status of arrangements for resources required to repair the failures, in association with each other. The arrangement DB 724 shown in Fig. 10 stores an alarm table 7241 and an arrangement table 7242.

[0094] The warning table 7241 is a table that describes warnings issued by the management device 7. The warning table 7241 shown in Fig. 10 has fields for a warning ID, a business establishment ID, a platform fence ID, a warning date and time, and a failure ID.

[0095] The warning ID is identification information that identifies each warning that the processor 71 of the management device 7 issues to the operation panel 4, for example, via the interface 73, the communication line 6, and the relay device 5. The platform fence ID and the business ID are identification information for the platform fence 2 that is predicted to fail due to the warning identified by the corresponding warning ID, and identification information for the business P where the platform fence 2 is installed. The warning date and time is information on the date and time when the warning identified by the corresponding warning ID was issued. The failure ID is identification information for the failure of the platform fence 2 included in the warning identified by the corresponding warning ID.

[0096] The arrangement table 7242 is a table showing information on resource arrangements provided for each warning ID listed in the warning table 7241. The arrangement table 7242 shown in FIG. 10 is associated with the warning ID "W1." This arrangement table 7242 stores, in association with each other, the resources required to repair the failure indicated in the warning identified by this "W1," the number of resources, the arrangement date and time, and the acquisition date and time. The arrangement date and time is the date and time when the arrangement of the resource began. The acquisition date and time is the date and time when the resource was acquired, or the date and time when the resource is scheduled to be acquired.

[0097] <Functional configuration of the monitoring device> Fig. 11 is a diagram illustrating an example of the functional configuration of the management device 7. The processor 71 of the management device 7 illustrated in Fig. 11 executes programs stored in the memory 72 to function as an acquisition unit 711, a correction unit 712, a prediction unit 713, a warning unit 714, and a planning unit 715.

[0098] The acquisition unit 711 acquires operation data from the monitoring device 1 via the interface 73, the communication line 6, and the relay device 5. This operation data is data indicating the operation of the platform fence 2 monitored by the monitoring device 1. The acquisition unit 711 stores the acquired operation data in the operation DB 721 in association with the measurement date and time.

[0099] The correction unit 712 corrects the acquired operation data based on the operation DB 721. For example, the correction unit 712 corrects the multiple pieces of operation data acquired by the acquisition unit 711 so as to remove the influence of disturbances on the operation data by taking into account the positions indicated by the installation information of the sensors 17 that measured the operation data. In other words, the management device 7 including the processor 71 that functions as this correction unit 712 is an example of a management device that corrects operation data indicating the operation of each of the multiple platform fences 2 based on the positions of the platform fences 2.

[0100] The prediction unit 713 predicts when the platform fence 2 will break down from the acquired operation data. The prediction unit 713 determines whether the operation data acquired by the acquisition unit 711 exceeds a threshold based on the operation DB 721. Then, the prediction unit 713 refers to the resource DB 722, and predicts when the corresponding failure will occur, for example, if a combination of operation data that exceeds a threshold satisfies a prediction condition.

[0101] In other words, the management device 7 equipped with a processor 71 that functions as this prediction unit 713 is an example of a management device that predicts when the platform fence that separates the station platform from the tracks will fail based on operation data indicating the operation of the platform fence.

[0102] 11 predicts, from the corrected operation data, when there is corrected operation data, when the platform fence 2 will fail. In other words, the management device 7 including the processor 71 that functions as the prediction unit 713 is an example of a management device that predicts, from the corrected operation data, when each of the multiple platform fences will fail.

[0103] The warning unit 714 acquires information about the time of the failure from the prediction unit 713, and identifies the time period required to prepare for repair of the failure (i.e., the preparation period) by referring to the period table 723. Then, the warning unit 714 issues a warning at a timing that is the preparation period prior to the predicted time of the failure.

[0104] In other words, the management device 7 equipped with the processor 71 functioning as this warning unit 714 is an example of a management device that warns of a failure when going back from the time of the failure of the platform fence 2 predicted by the prediction unit 713 to the period required to prepare for repair of the platform fence 2.

[0105] The warning issued by the warning unit 714 is transmitted to, for example, the operation panel 4 via the interface 73, the communication line 6, and the relay device 5, and is then conveyed to the operator who operates this operation panel 4.

[0106] As described above, the period table 723 referred to by the warning unit 714 may change depending on the availability of resources. In this case, the acquisition unit 711 acquires information on the period required for preparing resources from an external device via the interface 73, and rewrites the period table 723 based on the information.

[0107] For example, during busy periods, it may take longer to arrange for a technician to handle repairs than during slow periods. Furthermore, when parts inventory decreases in the market, it may take longer to arrange for those parts than usual. Even if the time required to arrange resources changes dynamically as described above, the management device 7 can warn of the time required to prepare the technicians, parts, and other resources by going back from the time when the failure was predicted.

[0108] When the prediction unit 713 predicts a failure of the platform fence 2, the planning unit 715 plans the repair (referred to as a repair plan) according to the status of arrangements for resources required to repair the failure. When the warning unit 714 issues a warning, the train crew or station staff who receive the warning operate, for example, the operation panel 4 or another terminal connected to the communication line 6 to arrange for resources required to repair the failure indicated by the warning. The status of arrangements is then transmitted to the management device 7 via the communication line 6.

[0109] The acquisition unit 711 acquires information indicating the status of resource arrangement from the above-mentioned terminals, etc. via the interface 73, and updates the arrangement DB 724 based on this information. The planning unit 715 refers to the arrangement DB 724, identifies the timing when the necessary resources will be available to repair the platform fence 2 for which a warning of predicted failure has been issued, and creates a repair plan.

[0110] For example, if multiple failures occur and repairing those failures requires engineers with the same qualifications, it may be more efficient for the same engineer to repair all of those failures together on the same day. In this case, the planning unit 715 creates a repair plan that adjusts the engineers who will repair the multiple failures that have occurred so that they will be invited on a day when all of the other resources required to repair those failures are available.

[0111] Furthermore, parts and the like are sometimes sold in fixed quantities, and surplus stock may remain after an order is placed and repairs are completed. For example, if multiple malfunctions occur on multiple platform fences 2 and common parts are required for those repairs, the planning unit 715 will create a repair plan that uses surplus parts, if any, that have been ordered for other malfunctions.

[0112] In other words, the management device 7 equipped with the processor 71 that functions as this planning unit 715 is an example of a management device that plans a repair plan for the platform fence based on the timing of the platform fence failure predicted by the prediction unit 713 and the status of arrangements for the resources required to repair the failure.

[0113] The configurations, shapes, sizes, and layout relationships described in the above embodiments are merely schematic illustrations to enable understanding and implementation of the present invention. Therefore, the present invention is not limited to the described embodiments, and can be modified in various forms without departing from the scope of the technical ideas set forth in the claims.

[0114] <Modification> The above is a description of the embodiment, but the contents of this embodiment can be modified as follows. In addition, the following modifications can be combined.

[0115] <1> In the above-described embodiment, the processor 71 functions as the corrector 712 and the planner 715, but it is not necessary to realize these functions.

[0116] <2> In the above-described embodiment, the processor 11 is a CPU, but other configurations are also possible. For example, the processor 11 may include a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), a programmable logic device, etc.

[0117] <3> In the above-described embodiment, the operation panel 4 may have the function of the control device 3. Furthermore, the platform fence 2 may have the function of the operation panel 4.

[0118] <4> In the above-described embodiment, the management device 7 alerts the operation panel 4 to a failure of the platform fence 2 via the communication line 6 and the relay device 5, but the destination of the alert is not limited to the operation panel 4. The management device 7 may also send the alert to, for example, another terminal connected to the communication line 6. In this case, this terminal is an information processing terminal such as a personal computer, slate PC, tablet PC, or mobile phone, and is a terminal used by a manager of the business establishment P where the platform fence 2 predicted to fail is installed, a station attendant, or the like.

[0119] <5> In the above-described embodiment, the management device 7 predicts when the platform fence 2 will fail based on the operation data indicating the operation of the platform fence 2. However, the management device 7 may also predict when each of the one or more components that make up the platform fence 2 will fail. In this case, the management device 7 may issue a warning when it looks back from the predicted time of failure for each component to the time required to prepare for repair of that component. This allows the management device 7 to manage failures of the platform fence 2 for each component.

[0120] In this modification, the management device 7 may store, in the memory 72, for example, an action DB 721a instead of the action DB 721 and a resource DB 722a instead of the resource DB 722.

[0121] Fig. 12 is a diagram showing an example of an operation DB 721a in a modified example. This operation DB 721a is a database that stores operation data indicating the operation of each part of the platform fence 2, measured by the sensor 17 of the monitoring device 1. The operation DB 721a shown in Fig. 12 differs from the operation DB 721 shown in Fig. 7 in that it includes a parts list 7215.

[0122] This parts list 7215 is provided for each platform fence ID listed in the platform fence list 7212, and is a list listing part IDs related to the platform fence 2 identified by that platform fence ID. These part IDs are identification information that respectively identify one or more parts that make up the corresponding platform fence 2.

[0123] 12, a sensor list 7213 is provided for each part ID listed in the part list 7215. This sensor list 7213 lists the sensor IDs of the sensors 17 that measure the operation of the part identified by the associated part ID.

[0124] Fig. 13 is a diagram showing an example of a resource DB 722a in a modified example. This resource DB 722a is a database that stores, for each model of platform fence 2, information on failures that may occur in the components that make up the platform fence 2 of that model, in association with the resources that are required to recover from those failures. The resource DB 722a shown in Fig. 13 differs from the resource DB 722 shown in Fig. 8 in that it includes a parts list 7223.

[0125] This parts list 7223 is provided for each model ID listed in the model ID list 7221, and is a list listing part IDs related to the platform fence 2 of the model identified by that model ID. These part IDs are identification information that respectively identify one or more parts that make up the platform fence 2 of the corresponding model.

[0126] 13, a resource table 7222 is provided for each part ID listed in the parts list 7223. This resource table 7222 is a table in which information about failures that may occur in parts identified by the associated part IDs is described.

[0127] When the processor 71 of the management device 7 acquires operation data from the monitoring device 1, the processor 71 stores the operation data in the operation DB 721a. As a result, the operation data is stored in association with each portion of the platform fence 2 that indicates the operation indicated by the operation data.

[0128] Then, when the operation data satisfies the prediction condition corresponding to the failure ID recorded in the resource DB 722a shown in FIG. 13, the processor 71 predicts the time when the failure identified by that failure ID will occur. Failure IDs are assigned not to each platform fence 2, but to each component that makes up the platform fence 2. Therefore, the management device 7 predicts the time when each component will fail. In this way, the management device 7 manages failures that occur in the platform fence 2 for each component, predicts the time when each component will fail, and issues a warning retroactively for each component, including the time required to repair the failure.

[0129] In other words, this management device 7 is an example of a management device that predicts when each part of the platform fence will break down and issues a warning when the time required to prepare for repairs for that part is calculated back from that time.

[0130] <6> In the above-described modified example, the management device 7 issues a fault warning for each component, but the warnings may be issued in an order according to the priority of those components. For example, in the resource DB 722a shown in Fig. 13, priority information is assigned to each component ID in the component list 7223. This priority information is information indicating the importance of the components that make up the platform fence 2 for the model identified by the model ID with which one component list 7223 is associated.

[0131] For example, in the resource DB 722a shown in FIG. 13, part IDs "C1" and "C2" are associated with model ID "M1." If the part indicated by part ID "C1" breaks down, the platform gate 2 for the model indicated by this model ID "M1" may stop functioning as a whole, even if the part indicated by part ID "C2" is not broken. On the other hand, even if the part indicated by part ID "C2" breaks down, the platform gate 2 for the model indicated by this model ID "M1" may continue to function, for example, if the part indicated by part ID "C1" does not break down for a predetermined period of time. In such a case, the part indicated by part ID "C1" is more important than the part indicated by part ID "C2," and therefore the priority information is written so that the former takes precedence over the latter.

[0132] When the processor 71 of the management device 7 detects a failure in two or more components, it may refer to this resource DB 722a and, based on the priority information in the component list 7223, decide which of the two or more components to give priority to informing about.

[0133] In other words, this management device 7 is an example of a management device that issues warnings about failures in the parts in an order according to the priorities set for those parts.

[0134] <7> In the above-described embodiment, the management device 7 refers to the resource DB 722 and predicts when a combination of operational data exceeding a threshold will occur if the combination satisfies the prediction condition. However, the prediction condition may be updated if the prediction is incorrect, for example.

[0135] For example, when the prediction of a failure is incorrect, such as when the platform fence 2 does not fail at the time when the management device 7 issues a warning, or when one of the platform fences 2 fails before the management device 7 issues a warning, the control device 3 notifies the management device 7 of this. When the processor 71 of the management device 7 receives this notification via the interface 73 as the acquisition unit 711 shown in FIG. 11 , it passes it on to the correction unit 712.

[0136] 11 updates the prediction conditions stored in the resource table 7222 of the resource DB 722 in response to the notification acquired by the acquisition unit 711. For example, the correction unit 712 refers to the content of the notification and reads from the operation DB 721 operation data for a period when a failure actually occurred but the management device 7 did not issue a warning, and extracts predictive data indicating a sign of a failure from the operation data. The correction unit 712 then uses the predictive data to change the prediction conditions. When the correction unit 712 finds a sign indicated by the predictive data in the operation data to be acquired next, it only has to correct the prediction conditions described above so that it can predict the timing of a failure and issue a warning.

[0137] In other words, in this case, the management device 7 is an example of a management device that, if a malfunction occurs in the platform fence before a warning is issued, extracts predictive data indicating signs of the malfunction from the operation data indicating the operation of the platform fence, and uses the predictive data to correct the prediction process for the timing of the platform fence malfunction. [Explanation of symbols]

[0138] 1...monitoring device, 11...processor, 12...memory, 13...interface, 16...sensor control unit, 17...sensor, 2...platform gate, 21...processor, 22...memory, 23...interface, 26...sensor control unit, 27...opening / closing sensor, 28...motor control unit, 29...motor, 3...control device, 31...processor, 32...memory, 33...interface, 4...operation panel, 41...processor, 42...memory, 43...interface, 44...operation unit, 45...display unit, 5...relay device, 6...communication line, 7...management device, 71...processor, 71 1...acquisition unit, 712...correction unit, 713...prediction unit, 714...warning unit, 715...planning unit, 72...memory, 721, 721a...operation DB, 7211...business location list, 7212...platform gate list, 7213...sensor list, 7214...operation data table, 7215...parts list, 722, 722a...resource DB, 7221...model ID list, 7222...resource table, 7223...parts list, 723...period table, 724...procurement DB, 7241...warning table, 7242...procurement table, 73...interface, 9...management system, L1...communication line, L2...communication line.

Claims

1. The system predicts when a platform fence that separates the station platform from the tracks will fail based on operation data showing the operation of the platform fence, and issues a warning when the time required to prepare for repairs of the platform fence is calculated from the predicted time. If the platform fence does not malfunction at the time the warning is issued, or if the platform fence malfunctions before the warning is issued, a management device extracts predictive data indicating signs of the malfunction from operation data showing the operation of the platform fence, and uses the predictive data to correct the prediction process for the timing.

2. The timing is predicted for each section of the platform fence, and a warning is issued when the time required to prepare for repairs for that section is counted back from that time. The management device according to claim 1 .

3. A warning is given for each failure of the part in the order according to the priority set for the part. The management device according to claim 2 .

4. The period includes the time required to arrange for the resources necessary for the repair. The management device according to claim 1 .

5. The time required for the arrangement varies depending on the availability of the resources. The management device according to claim 4 .

6. The resources include at least one of parts for the platform fence and a person who repairs the platform fence. The management device according to claim 4 or 5.

7. A repair plan for the platform fence is created according to the predicted time and the status of the resource arrangements. The management device according to any one of claims 4 to 6.

8. Operation data showing the operation of each of the plurality of platform fences is corrected based on the position of each of the platform fences, and the time when each of the platform fences will fail is predicted from the corrected operation data, and a warning is issued when the time required to prepare for repair of the platform fence is calculated from the time back. The management device according to claim 1 .

Images