Vehicle management program, vehicle management device, and vehicle management method
The vehicle management device improves maintenance accuracy by collecting sensor data to adapt to changing track conditions, addressing the challenge of predicting maintenance needs in railway vehicles.
Patent Information
- Application Number
- JP2023073764
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-27
- Publication Date
- 2024-11-08
AI Technical Summary
Existing railway vehicle maintenance systems fail to accurately predict maintenance needs due to changes in track conditions over the long life of the vehicles, leading to increased operating and maintenance costs.
A vehicle management device that collects strain data from sensors, determines abnormal loads, and records past abnormalities, using a database to estimate maintenance timing and adjust for changing track conditions.
Enhances the accuracy of abnormality detection and maintenance timing estimation, reducing maintenance costs by considering dynamic track conditions.
Smart Images

Figure 2024158508000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a railway vehicle management program, a vehicle management device, and a vehicle management method. [Background technology]
[0002] In general, because railway vehicles have a long product lifespan, it is desirable to reduce their life cycle costs (LCC). LCC is primarily comprised of the manufacturing costs for manufacturing railway vehicles, the electricity costs required for operation and the operating costs related to maintenance, the maintenance costs for inspecting and maintaining various equipment, and the disposal costs when the vehicle is scrapped.
[0003] Since the proportion of operation and maintenance costs related to maintenance in LCC is very large, efforts are being made to reduce LCC by properly estimating the fatigue and lifespan of each part of railway vehicles.
[0004] Traditionally, in the strength design of railway vehicles, test runs are conducted on the track on which the vehicle will actually run in order to estimate its lifespan, and distortion in each part of the railway vehicle is measured. The lifespan of each part of the railway vehicle is then estimated based on the actual operating conditions, taking into account the condition of the rails on the running section.
[0005] In addition, in Patent Document 1, a spring displacement calculation unit and a damper abnormality determination unit are arranged inside the vehicle, and a spring displacement estimation unit is arranged outside the vehicle. The spring displacement calculation unit calculates the vertical displacement of the air spring as "air spring displacement ΔX" using the air spring pressure value P output from the pressure sensor. The spring displacement estimation unit estimates the vertical displacement of the air spring as "air spring displacement estimated value ΔXc" using a railway vehicle model and position information transmitted from the vehicle and the pressure value P, and transmits it to the vehicle. The invention of an operating state diagnosis device is disclosed in which the damper abnormality determination unit compares the "air spring displacement ΔX" calculated by the spring displacement calculation unit with the "air spring displacement estimated value ΔXc" estimated by the spring displacement estimation unit to determine an abnormality. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] Patent Publication No. 2021-126912 Summary of the Invention [Problem to be solved by the invention]
[0007] Patent Document 1 proposes judging an abnormality using a railway vehicle model that is a model of a railway vehicle.
[0008] However, as the condition of the rail changes over the long product life of a railway vehicle, the impact that the rail has on each part of the vehicle changes, raising concerns that errors in fatigue and lifespan predictions could lead to increased operating and maintenance costs.
[0009] Therefore, the present invention aims to provide a means for constantly measuring the running condition of a railway vehicle, recording and comparing the measurements, detecting abnormal conditions in each part of the railway vehicle while taking into account changes in the track condition, and estimating the appropriate timing for maintenance. [Means for solving the problem]
[0010] The object of the present invention is to provide a vehicle management device for managing railway vehicles, comprising: a data collection unit that receives strain data from a strain sensor attached to a vehicle; a load determination unit that determines whether the strain data received by the data collection unit exceeds a predetermined value; a calibration determination unit that corrects the received strain data when the load determination unit determines that the strain data exceeds the predetermined value and determines whether the load exceeds the predetermined value, and when it determines that the load is abnormal, registers a strain sensor identifier and the value of the abnormal load in the abnormality history information; and an abnormality history confirmation unit that determines whether an abnormal load has occurred in the strain sensor in the past when the calibration determination unit determines that the load is abnormal. This can be achieved by a vehicle management device including an output section that outputs information indicating that an abnormal load has occurred when the abnormality history checking section determines that an abnormal load has occurred in the past. Effect of the Invention
[0011] According to the present invention, it is possible to provide a method for improving the accuracy of detecting abnormalities in railway vehicles by comparing with recorded measurement results and estimating the appropriate timing for performing maintenance. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration according to an embodiment of the present invention. [Diagram 2] 1 is an example of a vehicle management device according to an embodiment of the present invention. [Diagram 3] 2 is an example of a database server according to an embodiment of the present invention. [Figure 4] 4 is an example of abnormality history information according to an embodiment of the present invention. [Diagram 5] 4 is an example of occupancy rate dependent information in an embodiment of the present invention. [Figure 6] 4 is an example of vehicle maintenance information according to an embodiment of the present invention. [Figure 7(a)] 4 is an example of time-dependent information according to an embodiment of the present invention. [Figure 7(b)] 4 is an example of time-dependent information according to an embodiment of the present invention. [Figure 8] 4 is an example of speed-dependent information according to an embodiment of the present invention. [Figure 9] 4 is an example of acceleration-dependent information according to an embodiment of the present invention. [Figure 10] 4 is an example of a sensor management table according to the embodiment of the present invention. [Figure 11] 1 is an example of a flowchart illustrating an abnormality detection process according to an embodiment of the present invention. [Figure 12] 13 is an example of an output screen according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing for explaining the embodiments, the same components are given the same names and reference numerals as much as possible, and repeated description will be omitted.
[0014] The present invention is not limited to the following examples, and includes various modifications and equivalent configurations within the spirit of the appended claims. For example, the above-mentioned examples have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations.
[0015] In addition, the processing units described in the embodiments may be realized in hardware, some or all of which may be designed as integrated circuits, or may be realized in software by a processor interpreting and executing a program that realizes each function.
[0016] The tables, areas, etc. described in the embodiments may be a database (DB) or may be data stored in the main memory.
[0017] Hereinafter, a first embodiment of the present invention will be described with reference to the drawings.
[0018] 1 shows an example of a vehicle management device according to an embodiment of the present invention. A railcar (vehicle) 1 consisting of a car body 2 and a bogie 3 is equipped with an air pressure measurement unit 5 that measures the air pressure of an air spring 4, a strain sensor 6 that measures strain data of each part of the railcar, a speed measurement unit 7 that measures the speed of the railcar, an acceleration measurement unit 8 that measures the acceleration of the railcar, a position measurement unit 9 that measures the running position of the railcar, and a measurement end terminal 10 that collects the measured measurement data.
[0019] Specifically, air pressure measurement unit 5 is attached to each of air springs 4 located at the front and rear of railway vehicle 1, and acceleration measurement unit 8 is composed of acceleration sensors 8 installed on car body 2 and bogie 3, respectively.
[0020] The vehicle management device 13 receives the measurement data obtained from the measurement end terminal 10 via a network 12 using a wireless transmission terminal 11 that wirelessly transmits the data, and judges and analyzes any abnormalities. The abnormalities judged by the vehicle management device and the analyzed railway vehicle information are referenced by a user terminal 14 connected to the vehicle management device 13.
[0021] The user terminal 14 may be directly connected to the vehicle management device 13 or may be connected to the vehicle management device 13 via the network 12 .
[0022] 2 shows an example of a vehicle management device according to an embodiment of the present invention. The vehicle management device 13 is made up of a CPU (Central Processing Unit) 20, an input / output unit 21, a network interface 22, an external storage device 23, and a storage unit 24.
[0023] The memory unit 24 stores processing modules such as a data collection unit 25 that receives sensor information and the like from the wireless transmission terminal 11, a load determination unit 26 that determines the load from the received strain data, a calibration determination unit 27 that obtains data such as load taking into account the sensor correction value, an abnormality history confirmation unit 28 that checks for past abnormalities, and an analysis unit 29 that analyzes the information received by the data collection unit 25. These processing modules are realized by software and executed by the CPU 20.
[0024] Furthermore, a database 16 is stored in the external storage device 23, which stores information referenced by the processing module. In this embodiment, an example is described in which the vehicle management device 13 is realized by a stand-alone computer, but some or all of the computers described may be realized by computers such as a cloud system. The database may also be stored in an external storage system. By using a cloud system or an external storage system, a vehicle management device with more flexible scalability can be realized.
[0025] 3 shows an example of a database server in an embodiment of the present invention. Database server 16 includes vehicle maintenance information 35 storing vehicle delivery dates and inspection records, abnormality history information 39 storing abnormality information detected by a sensor in association with location information, occupancy rate dependent information storing occupancy rates created based on air spring information, and a sensor management table storing information on sensors attached to the vehicle.
[0026] In addition, time-dependent information 36, speed-dependent information 37, acceleration-dependent information 38, etc., which are the results of analysis by the analysis unit 29 based on information obtained from the vehicle's sensors, are also stored and can be referenced from the user terminal 14.
[0027] This information may be in the form of a table or a database.
[0028] 4 shows an example of abnormality history information in an embodiment of the present invention. The abnormality history information stores a vehicle number 50 for identifying the vehicle, a sensor ID 51 for the sensor attached to the vehicle that output an abnormal value, an occurrence date and time 52 indicating the date and time when the abnormality was detected, and a traveling position 53 indicating the traveling position of the vehicle when the abnormality was detected.
[0029] The traveling position 53 is indicated by position information measured by a GPS, etc., and position information indicating the center of a position having a certain range is stored. Furthermore, if the driving position is a curve, the curvature 54 of the curve is calculated from the map information and stored. Based on this information, it is possible to determine whether the load is increasing due to the curve or due to other factors.
[0030] The load 55 stores the load value when an abnormality is detected. This value is used to determine how serious the problem is. If the load value exceeds a certain threshold, the vehicle management device 13 automatically determines that an emergency response is required, and the user's attention is drawn to the load 55 by setting Y in the column for emergency response required 59.
[0031] Air spring pressure 56 is a value that indicates the state of the air spring when an abnormality is detected. Based on this value, passenger occupancy rate 57 can be calculated, and it is possible to know at what passenger occupancy rate the abnormality was detected.
[0032] However, since the air spring pressure 56 makes it possible to estimate the number of people using the train, it is important information for the railway operator. Therefore, it is not essential information because it may not be available when the company that provides the train operates the train management device 13.
[0033] The abnormality count 58 is a number indicating the number of times the same sensor has detected an abnormality in the past. This value may be used to determine whether or not an emergency response is required 59. By resetting the abnormality count 58 when replacing or adjusting the sensor, or periodically, it is possible to grasp the latest vehicle condition.
[0034] In the case of car No. 004, where a large load was detected due to a primary cause even though the load on the car was not high (10% occupancy rate) on a straight section with a curvature of 0, it is acceptable to indicate that no emergency action is required by entering "noise" in column 59 for emergency response necessity as abnormal data due to a primary cause. A separate column for temporary causes may be provided for clarification.
[0035] FIG. 5 is an example of occupancy rate dependent information in an embodiment of the present invention. Normally, four air springs are installed in a vehicle. Vehicle No. 60 indicates the vehicle in which an abnormality was detected and the air pressure measurement unit 5. Air spring pressure 61 stores the pressure value of the air spring when the abnormality was detected by the air pressure measurement unit 5. Partial occupancy rate 62 indicates the occupancy rate for each area when the vehicle is divided into four. Total vehicle occupancy rate 63 stores the occupancy rate for the entire vehicle. It is possible to grasp the imbalance of people in the vehicle based on partial occupancy rate 62, and to determine the impact of the imbalance on the vehicle.
[0036] 6 is an example of vehicle maintenance information in an embodiment of the present invention. For each vehicle number 70, the last inspection date 71, remaining life 72 indicating the usable period, delivery date 73 indicating the date the vehicle was delivered, useful life 74 indicating the designed life of the vehicle, and repair history 75 indicating the repair record are stored in association with each other.
[0037] The abnormality history information 39 may be reset when the previous inspection date 71 in the vehicle maintenance information 35 is updated or when the repair history 75 is updated. Furthermore, if the number of abnormalities 58 in the abnormality history information 39 exceeds a predetermined number in a short period of time, the maintenance costs may be reduced by setting the remaining life 72 to a shorter number of years rather than setting the remaining life 72 to the number of years obtained by subtracting the elapsed time from the delivery date to the present from the useful life 74.
[0038] Figures 7(a) and 7(b) are examples of time-dependent information in an embodiment of the present invention. The horizontal axis shows time, the vertical axis shows load, and the dotted line 81 is the design value of the load. Since the design value is usually a value multiplied by a safety factor, exceeding the design value does not immediately cause a breakdown, but if the graph shows the solid line 82 as in Figure 7(a), it is possible that a strong impact has been applied, and therefore inspection is necessary. However, since the operating environment of the sensor can be harsh and there is a possibility of noise, it is necessary to make a judgment based on the magnitude and duration of the load.
[0039] In Figure 7(b), the load does not exceed the design value, but it is always close to the design value, dotted line 81. In this case, fatigue may have accumulated in the sensor installation area, so it is necessary to check this during inspection.
[0040] Fig. 8 is an example of speed-dependent information in an embodiment of the present invention. When the speed increases, the load increases along the dotted line 84, but in this case, after the speed exceeds a certain value, the load increases suddenly and exceeds the design value. Problems like this can occur due to component deterioration, etc., so it is necessary to check during inspection.
[0041] Fig. 9 is an example of acceleration-dependent information in an embodiment of the present invention. The horizontal axis shows the value obtained by Fourier transforming the acceleration, and the vertical axis shows the value obtained by Fourier transforming the load. If values like vertical line 86 appear in this graph, there is a possibility that resonance is occurring. In such cases, confirmation during inspection is also required.
[0042] 10 is an example of a sensor management table in an embodiment of the present invention. This table is prepared for each vehicle and records, in association with each other, the installation position 91 of the sensor installed in the vehicle, the most recent calibration date 92, the number of calibrations 93, the deterioration degree 94 indicating the deterioration degree of the sensor, the correction value 95 which is the current calibration value, the replacement necessity 96 indicating the necessity of sensor replacement, the design value 97 which is the allowable value of distortion at the sensor installation location, and the remarks 98 which record the state of the sensor.
[0043] 11 is an example of a flowchart showing an abnormality detection process in an embodiment of the present invention. First, the air pressure data from the air pressure measuring means 5, the strain data from the strain sensor 6, the speed data from the speed measuring unit 7, the acceleration data from the acceleration measuring unit 8, the position data, the speed data, the acceleration data, etc., collected by the measurement end terminal 10 are received by the data collecting unit via the network (step S3).
[0044] Next, the load determination unit 26 refers to the sensor management table and determines whether a load equal to or greater than the design load is occurring (step S6). If a load equal to or greater than the design load is not occurring, it is determined to be a normal state and no action is taken.
[0045] If a load equal to or greater than the design load has occurred, the abnormality history information 39 and the sensor management table 41 are referenced (step S8), and the correction value 95 in the sensor management table 41 is used to determine whether the strain data exceeds the design value (step S9).
[0046] If the design value is not exceeded in step S6, the following method is used for correction. That is, a travel section separated by two points in time at which the speed data and acceleration data values are 0 at the time closest to the time at which a value equal to or greater than the predetermined load was calculated is identified, and a determination is made as to whether the strain values at the start and end points of the travel section are 0 or sufficiently small when a value taking into account the initial state of the sensor is divided from the strain data values at the start and end points of the travel section. If it is determined that the value dependent on the initial state of the sensor has not been divided appropriately, the sensor information and the value to be divided that is dependent on the initial state are stored in the sensor management table as one-to-one information, and the sensor information used in subsequent measurement data processing is updated (step S10).
[0047] If it is difficult to automatically update the correction values using this method, information indicating that manual correction is required at the time of the next inspection may be recorded in the sensor management table 41.
[0048] If it is determined in step S9 that the design value is exceeded, the abnormality history information 39 is referenced to determine whether an abnormal load has occurred at the same position in the past. If the abnormality history information 39 includes the occupancy rate, it may be determined whether the occupancy rate is the same (step S11).
[0049] If no abnormal load has occurred in the past, noise or the like is recorded as a temporary external factor in the abnormality history information 39, and the detected load, etc. are recorded (step S12). The accuracy of the judgment as to whether or not the abnormality is due to a temporary external factor can be further improved by using other data values such as curvature and occupancy rate as judgment criteria.
[0050] If an abnormal load has occurred at the same position in the past, it is stored in the abnormality history information, the number of abnormalities is updated, and the analysis unit 29 creates time-dependent information 36, speed-dependent information 37, acceleration-dependent information 38, etc. (step S15).
[0051] Next, if the load exceeds the set number of abnormal loads within a predetermined period, the remaining life 72 of the vehicle maintenance information 35 is displayed in a manner different from other manners, such as in red, so that the user can consider continuing to use the vehicle. Furthermore, the remaining life may be changed to a shorter remaining life than the normal remaining life calculated based on the useful life 74 (step S13).
[0052] Finally, information on the vehicle in which the abnormal load is occurring is output to the user terminal (step S14). Although the output to the user depends on the operation method of the vehicle management device 13, if an emergency response is required, an interface may be provided that cooperates with the vehicle operation system and notifies the user by e-mail or the like together with information such as the current location of the vehicle.
[0053] The information in the database server 16 updated at each step of the above processing flow is displayed on the user terminal 14, making it possible to refer to the fatigue state and remaining life of each part of the railway vehicle.
[0054] 12 is an example of an output screen in an embodiment of the present invention. Vehicle identification information 101 for identifying the vehicle for which the remaining life is to be displayed, a map 102 of the location where the abnormal load was detected by the vehicle, vehicle characteristic information 103 showing the time-dependent information, speed-dependent information, and acceleration-dependent information of the vehicle in graph form, and a table correlating measurement points 104, dates 105, previous occurrence dates 106, loads 107, locations 108, and track curvatures 109 are displayed on a single screen.
[0055] The above-described railway vehicle management device is capable of updating the fatigue state and lifespan of each part of the railway vehicle while the railway vehicle is running, using the measurement data of each part of the railway vehicle and the database table. This makes it possible to provide a method for detecting abnormalities in each part of the railway vehicle, taking into account changes in the condition of the rails that occur over the long product life of the railway vehicle, and estimating the timing for maintenance. [Explanation of symbols]
[0056] Reference Signs List 1 Railway vehicle, 2 Car body, 3 Bogie, 4 Air spring, 5 Air pressure measurement unit, 6 Strain sensor, 7 Speed measurement unit, 8 Acceleration measurement unit, 9 Position measurement unit, 10 Measurement end terminal, 11 Wireless transmission terminal, 12 Network, 13 Vehicle management device, 14 User terminal, 16 Database, 20 CPU, 21 Input / output unit, 22 Network interface Interface, 23... external storage device, 24... storage section, 25... data collection section, 26... load determination section, 27... calibration determination section, 28... abnormality history confirmation section, 29... analysis section, 30... DB management system, 35... vehicle maintenance information, 36... time-dependent information, 37... speed-dependent information, 38... acceleration-dependent information, 39... abnormality history information, 40... occupancy rate-dependent information, 41... sensor management table
Claims
1. A vehicle management program for managing rail vehicles, a data collection unit receiving strain data from the strain sensors mounted on both sides; The load judgment unit judges whether the received strain data exceeds a predetermined value. a calibration determination unit correcting the received strain data when the excessive determination unit determines that the strain data exceeds a predetermined value, determining whether the load is an abnormal load exceeding the predetermined strain data, and registering a strain sensor identifier and the value of the abnormal load in the abnormality history information when the abnormal load is determined; The abnormality history confirmation unit determines whether an abnormal load has occurred in the strain sensor in the past when the calibration determination unit determines that an abnormal load has occurred; The output unit is a vehicle management program that causes a computer to execute a procedure for outputting information indicating that an abnormal load has occurred when the history checking unit determines that an abnormal load has occurred in the past.
2. 2. The vehicle management program according to claim 1, a sensor management table that stores a vehicle on which a strain sensor is attached, a mounting position, and a design value of strain data; The load determination unit is a vehicle management program that refers to the sensor management table and compares the strain data received from the data collection unit with the design value to make a determination.
3. 3. The vehicle management program according to claim 2, The sensor management table stores the correction values of the distortion sensors. A vehicle management program in which the calibration judgment unit refers to the sensor management table, obtains distortion data by correcting the distortion data received from the data collection unit with a correction value, and compares the corrected distortion data with the design value to determine whether or not the load is abnormal.
4. 2. The vehicle management program according to claim 1, The abnormality history information stores the vehicle on which the strain sensor is installed, the vehicle's running position, and the number of times abnormal loads have been detected in the past. The abnormality history confirmation unit is a vehicle management program that refers to abnormality history information and determines whether an abnormal load has occurred at the same driving position in the past.
5. 5. The vehicle management program according to claim 4, The data collection unit receives the pressure information of the air spring when it receives the strain data from the strain sensor, When the calibration judgment unit judges that the load is abnormal, it calculates the occupancy rate from the pressure information of the air spring, associates the abnormal load value with the occupancy rate, and registers the abnormal load value in the abnormality history information. The abnormality history confirmation unit is a vehicle management program that refers to abnormality history information and determines whether an abnormal load has occurred in the past at the same driving position and with the same occupancy rate.
6. A vehicle management method for managing railroad vehicles, comprising: The data collector receives strain data from the strain sensors installed on both sides. The load judgment unit judges whether the received strain data exceeds a predetermined value. The calibration judgment unit corrects the received strain data when the excessive judgment unit judges that the strain data exceeds a predetermined value, judges whether the load is an abnormal load exceeding the predetermined strain data, and registers the strain sensor identifier and the value of the abnormal load in the abnormality history information when the excessive judgment unit judges that the load is an abnormal load. The abnormality history confirmation unit determines whether an abnormal load has occurred in the strain sensor in the past when the calibration determination unit determines that an abnormal load has occurred, The vehicle management method includes an output unit that outputs information indicating that an abnormal load has occurred when the history checking unit determines that an abnormal load has occurred in the past.
7. 7. The vehicle management method according to claim 6, a sensor management table that stores a vehicle on which a strain sensor is attached, a mounting position, and a design value of strain data; A vehicle management method in which the load determination unit refers to a sensor management table and compares the strain data received from the data collection unit with a design value to make a determination.
8. A vehicle management device that manages railroad vehicles, a data collection unit that receives strain data from a strain sensor mounted on the vehicle; a load determination unit that determines whether the strain data received by the data collection unit exceeds a predetermined value; a calibration determination unit which corrects the received strain data when the load determination unit determines that the load exceeds a predetermined value, determines whether the load exceeds the predetermined strain data, and registers a strain sensor identifier and the abnormal load value in the abnormality history information when the load determination unit determines that the load exceeds the predetermined value; an abnormality history checking unit that determines whether an abnormal load has occurred in the strain sensor in the past when the calibration determination unit determines that an abnormal load has occurred; A vehicle management device comprising: an output unit that outputs information indicating that an abnormal load has occurred when an abnormality history checking unit determines that an abnormal load has occurred in the past.
9. 9. The vehicle management device according to claim 8, a sensor management table that stores a vehicle on which a strain sensor is attached, a mounting position, and a design value of strain data; The load determination unit refers to the sensor management table, and compares the strain data received from the data collection unit with the design value to make a determination.
Citation Information
Patent Citations
Working state diagnosis device
JP2021126912A
