Operation data storage device, train coupler, car assembly, system, computer-implemented method for storing operation data, and non-transitory computer-readable storage medium

Abstract

Storing operational data of a rail-guided vehicle, e.g., a train, wagon, or coupling, has not yet been adequately solved, particularly due to the amount of data involved. This problem is solved by an operational data storage device (10) comprising the following: - a communication unit (11) for receiving operational data (16) related to at least one rail-guided vehicle (1, 1', 1"); - a processing unit (12) for generating cumulative operational data (17) to be stored from the received operational data (16); - a storage unit (13) for storing the cumulative operational data (17).

Description

[0001] The invention relates generally to the field of track-guided vehicles and, in particular, rail vehicles. Specifically, the invention relates to solutions for the continuous recording and / or analysis of operational data. Specifically, the invention relates to an operational data storage device, a rail-guided vehicle, a train coupling or wagon, a wagon arrangement, a system, a computer-implemented method, and a non-volatile, computer-readable storage medium.

[0002] The service life of rail vehicles, especially wagons and couplings, is 30-35 years. During this period, numerous maintenance procedures are performed, for example, every six or twelve years. The scope of the maintenance can vary depending on the service interval. Individual components may also need to be replaced before the end of the vehicle's service life.

[0003] To perform maintenance and determine the wear of individual components, operating data for each component is collected throughout its entire service life. To carry out maintenance efficiently and cost-effectively, it is essential to consider how many coupling operations a coupler has performed or how many minutes a railcar has been in operation. Based on this data, decisions can be made about which components need to be replaced or serviced and when. Overall, data-driven maintenance planning leads to more targeted maintenance. However, the recording and storage of this operating data remains a challenge that has not yet been adequately addressed.

[0004] One way to store operational data is to save specific parameters, such as sensor data, at defined intervals. For example, the current speed of a railcar can be saved every two seconds. It is also possible to record each coupling operation. The resulting log files would then contain one line for each measurement. However, this leads to very large log files over a long maintenance period, which cannot be stored on the relevant device, such as a railcar control unit, because their size would exceed the storage capacity. One option is to transfer the data to a data center during operation. However, the problem here, too, is that the amount of data becomes very large.

[0005] It is therefore an object of the invention to provide a way to store operating data of a rail-guided vehicle or a component of a rail-guided vehicle in a memory-efficient manner. In particular, it is an object of the invention to reduce the storage space required for the operating data to be stored. Furthermore, it is a particular object of the invention to enable the operating data to be stored locally, i.e., on the relevant component. Finally, it is a particular object of the invention to accelerate the processing of stored operating data.

[0006] The problem is solved by the subject matter of the independent claims.

[0007] The problem is solved in particular by an operational data storage device, especially for a rail-guided vehicle, e.g. a wagon and / or a traction vehicle, preferably for a coupling of a rail-guided vehicle, comprising the following: a communication unit for receiving operational data related to at least one rail-guided vehicle; a computing unit for generating cumulative operational data to be stored from the received operational data; a storage unit for storing the cumulative operational data.

[0008] A key consideration of the above embodiment is to store cumulative data rather than individual operational data points, such as sensor measurements. This cumulative approach significantly reduces the amount of data to be stored. However, it still ensures that the data necessary for maintenance or wear determination remains available.

[0009] In one embodiment, the storage unit can be configured to store the accumulated operating data to be stored in a defined number of storage locations in the storage unit.

[0010] The above embodiment makes it possible to determine the necessary storage space for storing the accumulated operating data. This allows for the design of a storage device, or storage unit, and ensures that the accumulated operating data can be stored there.

[0011] Each memory location can have a defined memory width. This means that each memory location can store a defined number of bits. Such an allocation of memory width can be achieved, for example, by defining a data type, such as integer, string, boolean, state (a collection of states), or float. Furthermore, in one embodiment, it is also possible that each memory location stores data of a complex data type, such as an object, a matrix, and / or a tensor.

[0012] In one embodiment, the computing unit can be configured to combine the received operating data with stored accumulated operating data when accumulating the operating data.

[0013] In the embodiment described above, the accumulation process can thus involve combining previously stored cumulative operating data with newly received operating data. For example, in the case of storing mileage, i.e., the number of kilometers or meters driven, the value stored in the memory unit can be added to the newly received data. Combining the previously stored cumulative operating data with the newly received operating data ensures that the information in the stored cumulative operating data is not lost.

[0014] In one embodiment, the computing unit can be configured to perform a mathematical and / or logical operation using accumulated operating data stored in the storage unit and the received operating data in order to generate the accumulated operating data to be stored.

[0015] It is therefore fundamentally possible to perform any mathematical and / or logical operation on the stored cumulative operating data with the received operating data. For example, addition, subtraction, multiplication, or division can be performed. Furthermore, it is possible to perform complex mathematical operations, such as calculating an average value. It is also possible to store a current maximum or minimum value, such as a maximum or minimum speed. If, for example, the operating data indicates a speed greater than a maximum speed, a logical operation—in this case, a greater-than operation—can determine whether the operating data is greater than the cumulative operating data stored in the memory unit. In principle, a logical operation can be value-based, meaning...For example, a minimum operation, maximum operation, equality operation, or inequality operation can be performed, or it can be performed bitwise. It is also possible to compare bit patterns of data, e.g., using AND, NAND, OR, XOR, and to store a value in the memory device as cumulative operational data based on the result.

[0016] In one embodiment, it is possible that the storage unit has a defined number of storage locations for storing the accumulated operational data, wherein a storage location can be assigned to a type and / or class of operational data.

[0017] One type of operating data could, for example, specify whether the operating data includes speed, distance, temperature, resistance, force, and / or weight. Other types of operating data are also conceivable.

[0018] Operational data can also be assigned to a class. For example, the storage device can define multiple memory locations for different speed ranges. It is conceivable that a first memory location is assigned to a speed range of 0-10 km / h, a second to a speed range of 10-50 km / h, and a third to a speed range of 50-100 km / h. Received operational data, such as a speed reading, can then be stored in the corresponding location in the memory, i.e., a specific memory location. In the example above, it is thus possible to store how long a rail vehicle has traveled at a specific speed.

[0019] In one embodiment, each class of operational data can be assigned to a specific type of operational data. For example, a class could indicate whether it represents speed, distance, temperature, and / or another type of operational data. This ensures that only operational data of the correct type is stored at a specific location or memory location within the storage unit.

[0020] In one embodiment, the storage unit can be configured to store cumulative operational data as an N-dimensional matrix, where N can be a natural number, and where a cell of the matrix is ​​preferably assigned to a class of a type of operational data.

[0021] It is therefore possible to store a matrix in a single memory location, where each cell of the matrix can be assigned to a class of a specific type of operational data. Thus, it is also possible to store different classes in a single memory location. For example, a matrix can specify speed ranges, with each cell of the matrix assigned to a speed range.

[0022] In one embodiment, the computing unit is designed to accumulate operational data in response to an event, in particular to accumulate only in response to an event.

[0023] It is conceivable that the communication unit receives operational data continuously or at defined intervals. The processing unit can then be configured to perform an accumulation of operational data only in response to an event. For example, it is conceivable that, upon the occurrence of an event, the most recently received operational data is used to generate the accumulated operational data.

[0024] In one embodiment, the communication unit can be connected to a data line, e.g., a communication bus, and furthermore be configured to receive data via the data line, which can indicate an event. It is therefore conceivable that an event has an external component. This means that the event can be subject to external influences. For example, it is conceivable that an event is triggered when a wagon coupler is engaged, so that the current coupling state is received as operational data and used for data accumulation. The data line could, for example, be an Ethernet connection. Other bus systems such as EtherCAT or Wire Train Bus (WTB), Multi Function Vehicle Bus (MVB), or UIC-based systems are conceivable. Furthermore, the use of Single Pair Ethernet is also conceivable.

[0025] In one embodiment, the event can be specified by a timer, wherein the timer can be configured to provide the event preferably at a defined frequency.

[0026] The embodiment described above enables the regular accumulation of operational data. For this purpose, a timer can be provided in the operational data storage device. The timer can be implemented, for example, by program logic. It is also conceivable that the timer is implemented by a physical timer unit, such as a quartz crystal, or a combination of both. By using the timer, it is possible for operational data to be accumulated at regular intervals. It is also possible for the timer to be synchronized with the provision of operational data received via the communication unit. This means that accumulation is always performed when new operational data is available. It is also conceivable that accumulation is performed once a day, once an hour, once a minute, once a second, or once a millisecond.Furthermore, it is conceivable that the timer triggers an event (only) when defined boundary conditions are met. For example, the boundary conditions could specify that a particular coupling position exists or that a wagon or train is in motion. It is also conceivable that a load state or a maximum / minimum speed is considered as a boundary condition. Naturally, any combination of the aforementioned conditions is also possible.

[0027] In one embodiment, a readout unit may be provided, which may in particular be a wireless communication unit, which may be configured to transmit the stored cumulative operating data to an external storage unit, e.g. a mass storage device or a data center, wherein the storage unit may preferably be configured to delete the stored cumulative operating data in response to the transmission.

[0028] The accumulated operational data stored in the storage unit can be made available to external systems via a readout unit. For example, during maintenance, a data set can be read from a mass storage device, such as a USB flash drive or a hard drive. Additionally or alternatively, a wireless communication unit can transmit the data via a wireless communication medium. For example, the wireless communication unit could be a WLAN, Bluetooth, or cellular module. It is also conceivable that the accumulated operational data could be transmitted via a wireless communication unit to an external storage device, such as a data center. The operational data storage device could thus be connected to a cloud infrastructure, enabling the accumulated operational data to be transmitted at regular intervals.The transmission of accumulated operating data via the readout unit can also be implemented in response to an event. The readout unit can be configured to detect an external event or an event triggered by a timer. In one embodiment, for example, the detection of the removal of a component from a train consist, such as a coupling, can trigger a readout process. Furthermore, the accumulated operating data stored in the memory unit can be transmitted via the readout unit to the external device via a wired connection, e.g., a data line. It is conceivable that transmission to the external device can be carried out within the train consist, e.g., wirelessly. For this purpose, a corresponding communication and / or routing device can be provided in the individual components of a train consist.

[0029] In response to, or after, the transmission of the stored cumulative operational data, the operational data storage device can be configured to delete, or partially delete, the stored cumulative operational data. This ensures that storage space is freed up and a new, independent recording can begin.

[0030] The task is further solved by a rail-guided vehicle, a train coupling or a wagon, in particular a train wagon with an operational data storage device as described above.

[0031] The rail-guided vehicle could be, for example, a freight wagon, passenger car, or railcar. A coupling, especially for trains, can be a device for connecting train or shunting units. Common types of couplings are screw couplings, where the coupling process must be carried out manually. Another type of coupling is an automatic train coupling, where the coupling process can be automated. During a coupling process, for example with a Scharfenberg-type coupling, in addition to the frictional connection of the respective coupling elements, compressed air lines, such as the main air reservoir line, main air line, or uncoupling air line, can also be connected. Additionally, in one embodiment, a data line can be connected, through which data, for example, operational data about different wagons, can be transmitted.can be transferred between wagon and railcar.

[0032] The problem is further solved in particular by a wagon arrangement comprising at least two wagons, as described above, wherein the respective operational data storage devices are connected to each other via a data line, in particular via a communication bus.

[0033] The task is further solved in particular by a system for operational data acquisition, comprising: At least one operational data storage device as described above; at least one server device designed to receive and store cumulative operational data from the at least one operational data storage device.

[0034] In one embodiment, the at least one server system can be a server program implemented on a computer. In other embodiments, the at least one server system can be a data center comprising a multitude of storage devices and configured to communicate with at least one operational data storage device via a communication medium, e.g., the internet.

[0035] In one embodiment, the at least one server device can be configured to perform a fleet analysis using the accumulated operational data for a plurality of operational data storage devices.

[0036] In one embodiment, the server can be configured to compare the accumulated operating data of a multitude of operational data storage devices. Deviations in the accumulated operating data stored can serve as an indicator of a malfunction. For example, a maximum measured temperature stored in an operational data storage device that deviates from an average of the maximum temperatures can indicate a malfunction. In another embodiment, it is conceivable that a grouping, e.g., clustering, is performed based on the accumulated operating data of the respective operational data storage devices. This allows operational data storage devices with similar accumulated operating data to be grouped together. The identification of outliers or deviations exceeding a threshold can then be performed for each individual group.the cluster will be executed.

[0037] In one embodiment, the fleet analysis can include the identification of at least one operational data storage device whose cumulative operational data, preferably for a type of operational data and / or a class, exhibits a statistical anomaly, e.g., lies outside a normal range.

[0038] The merging of the accumulated operating data from a large number of operational data storage devices thus enables statistical analysis, so that malfunctions or increased wear can be detected early.

[0039] The task is further solved in particular by a computer-implemented method for storing operational data, comprising the following steps: Receiving operational data via a communication unit, wherein the operational data relates to at least one rail-guided vehicle; generating cumulative operational data to be stored from the received operational data; storing the cumulative operational data in a storage unit.

[0040] In one embodiment, storing the accumulated operational data to be stored may include storing it in a defined number of storage locations in the storage unit.

[0041] In one embodiment, the accumulation of operating data can include combining the received operating data with stored accumulated operating data.

[0042] In one embodiment, storing the accumulated operational data may include storing it in a defined number of storage locations, where a storage location may be assigned to a type and / or class of operational data.

[0043] In one embodiment, each class of operational data can be assigned to a type of operational data.

[0044] In one embodiment, storing the accumulated operational data can include storing it as an N-dimensional matrix, where N can be a natural number, and where a cell of the matrix can preferably be assigned to a class of a type of operational data.

[0045] In one embodiment, the accumulation of operating data can be performed in response to an event, in particular only in response to an event.

[0046] In one embodiment, the method may include the communication unit receiving a data point via a data line, e.g., a communication bus, where the data point may specify an event.

[0047] In one embodiment, the method may include providing an event by means of a timer, preferably with a defined frequency.

[0048] In one embodiment, the method can include transmitting the stored cumulative operating data to an external storage unit, e.g. a mass storage device or a data center, via a readout unit, in particular a wireless communication unit, wherein the stored cumulative operating data can preferably be deleted in response to the transmission.

[0049] In one embodiment, generating the accumulated operating data may involve the use of a mathematical and / or logical operation using accumulated operating data stored in the memory unit and the received operating data.

[0050] The advantages are similar or identical to those already described in connection with the items described above.

[0051] The problem is further solved in particular by a non-volatile, computer-readable storage medium designed to store instructions that cause at least one processor to implement the procedure described above when the instructions are executed by the at least one processor.

[0052] Further embodiments are described in the dependent claims.

[0053] Further examples of implementation are explained in more detail below with reference to the figures. These show Fig. 1 a schematic representation of a wagon with an operational data storage device; Fig. 2 a wagon arrangement and server unit; Fig. 3 a system with several wagons and a server unit; Fig. 4 a schematic representation of an operational data storage device; Fig. 5 a matrix for storing operational data; Fig. 6 a tree structure for storing accumulated operational data; Fig. 7 a method for accumulating operational data; Fig. 8 another method for accumulating operational data.

[0054] The Fig. 1Figure 1 shows a schematic representation of a wagon 1. In the illustrated embodiment, wagon 1 is designed as a freight wagon, i.e., for transporting goods. Freight wagons are rail-guided vehicles that move on rails. Wagon 1 has a loading space 4 for receiving cargo. To connect wagon 1 to another wagon or a railcar, wagon 1 has two couplings 2. In the illustrated embodiment, the couplings 2 are digital automatic couplings (DACs). The DAC is designed to connect the air, data, and power lines of wagon 1. A data line 3 is provided above the couplings 2, which can be connected to the data line of another wagon. This allows data to be transmitted between individual wagons. The data line 3 can be configured as a bus system.In the illustrated embodiment, sensors are connected to data line 3, which provide their sensor values ​​via data line 3.

[0055] Wagon 1 is further equipped with an operational data storage device 10, as well as additional operational data storage devices 10', 10" at the couplings. Each of the operational data storage devices 10, 10', 10" is designed to store operational data, in particular to store it cumulatively, that is relevant for wagon 1 or the couplings 2. The operational data storage device 10 of wagon 1 can, for example, be arranged on a wagon control unit. The following operational data can be stored cumulatively for wagon 1: Operating data can be generated for each trip with wagon 1, which is accumulated by the operational data storage device 10. Thus, the number of trips with wagon 1 can be counted by incrementing a counter in the operational data storage device 10. A trip can be defined as the period between two stops of wagon 1, i.e.,The counter can be incremented after a braking process that results in a complete standstill. To determine the movement, a position determination device 5 is arranged on the wagon 1, which communicates with the operational data storage device 10, e.g., via data line 3. The position determination device 5 can be, for example, a GPS or GLONASS system. The position determination device 5 can indicate a speed, or the speed can be calculated from the position data by the operational data storage device 10.

[0056] During a brake test, the functionality and technical condition of the braking system are checked. While stationary, the technical condition, application, and release of the brakes to be tested are monitored. For this purpose, wagon 1 is equipped with a brake 7. In the illustrated embodiment, brake 7 is a compressed air brake. Therefore, the storage unit of the operational data storage device 10 has two memory locations, one for successful and one for unsuccessful brake tests. For each successful or unsuccessful brake test, the corresponding counter is incremented by the operational data storage device 10.

[0057] The operational data storage device 10 is designed to store in a memory location how often an automatic parking brake has been applied.

[0058] In the illustrated embodiment, the operational data storage device 10 is further configured to store how long the wagon 1 has moved within a specific speed range. The operational data storage device can thus include a plurality of classes, each corresponding to a speed range. The operational data storage device 10 is then configured to store, for each class, how long the wagon 1 moves at a speed within that speed range.

[0059] According to the speed classes over time proportions, it can be provided that individual classes define speed intervals, whereby the distance traveled is stored for each class, i.e., the distance traveled is stored cumulatively for a speed interval.

[0060] Corresponding further classes can be defined for time components in acceleration classes, deceleration classes, standstill classes, loading classes, stop time classes, route distance classes (each between coupling and uncoupling operations), temperature classes based on outside temperature, interior temperature, control unit temperature, battery temperature, generator temperature, rubber part temperature (e.g. on bogies, especially rubber springs), shock classes (e.g. in three (spatial) dimensions, each measured on the car body, on the coupling or on the bogie or rolling classes).

[0061] Furthermore, it is planned that individual classes will specify stop times, i.e., the time required for wagon 1 to transition from a moving state to a stationary state through a braking process. Thus, the number of times a stop process has been performed is recorded cumulatively, sorted by stop time.

[0062] The operational data storage device also includes a memory location in which an average speed is stored, taking into account times when wagon 1 is stationary. Correspondingly, a memory location may be provided in which an average speed without stops, i.e., an average speed only when the wagon is in motion, is stored.

[0063] The operational data storage device 10 is further configured to store how long wagon 1 remains in a corresponding altitude segment assigned to a class. The altitude segment specifies a range in the elevation profile, for example 50-100 m.

[0064] The operational data storage device 10 also stores the total kilometers traveled by wagon 1 in a storage space.

[0065] Similarly, the operational data storage device 10 stores the operating hours of wagon 1. An operating hour can be indicated, for example, by the fact that a power supply is provided and / or a railcar is coupled to wagon 1. Furthermore, an operating hour can be specified in relation to an operating mode, e.g., driving mode, parking mode, or shunting.

[0066] In addition, the operational data storage device can cumulatively store the average distance between stops and / or the average idle time between stops.

[0067] Furthermore, the operational data storage device can cumulatively record how long the brakes of wagon 1 remain in a P or G position. The P or G position indicates the braking position with which the effect of the compressed air brake 7 can be adjusted. Particularly with long train sets, the braking effect is artificially slowed to prevent the rear section of the train from colliding with already braked front sections. The P braking position indicates a fast-acting braking position, and the G braking position indicates a slow-acting braking position.

[0068] The operational data storage device is further provided to have a storage location for each brake position, in which the cumulative time components in each brake position are stored.

[0069] The operational data storage device 10 is further configured to store cumulative time shares and cumulative mileage for different load classes. The load class can specify the load of wagon 1.

[0070] The operational data storage device is further designed to store multidimensional class combinations. It is intended that the time spent in a topography class is stored across a speed class and a load class. This means, for example, that the system cumulatively stores how long wagon 1 travels in a specific topography class at a specific speed (assigned to a speed class) with a specific load (assigned to a load class).

[0071] Furthermore, the operational data storage device 10 is designed to store cumulative operational data for a battery assigned to the wagon. For example, the average battery capacity is stored. In addition, battery capacity classes are defined, and the duration for which the battery maintains a capacity corresponding to a specific battery capacity class is stored cumulatively. Additionally or alternatively, the number of charging cycles for the battery is stored cumulatively. Furthermore, the average state of charge of the battery during aborted charging cycles is stored. Finally, the number of charging cycles of the battery over a given charging cycle period is also stored.

[0072] The operational data storage device 10 is further equipped to store data relating to braking operations. For example, the number of braking operations per kilometer is stored cumulatively, as well as the braking time during different speed classes. The braking force over the braking time can also be stored, in particular categorized into braking force and braking time classes.

[0073] Carriage 1 may also be equipped with temperature sensors that measure the temperature of circuit boards and / or other external sensors. The operational data storage device 10 is then configured to store an average temperature and / or maximum and minimum temperatures for the circuit boards and / or external sensors.

[0074] Furthermore, wagon 1 is equipped with an accelerometer, e.g., an inertial measurement unit (IMU), which is designed to measure accelerations in different spatial directions. The sensor data from the accelerometer is provided to the operational data storage unit 10, so that the operational data storage unit 10 can store the number of accelerations separately for individual directions. For this purpose, the operational data storage unit 10 can be configured to only begin storing accelerations above a certain acceleration value.

[0075] The operating data storage device 10', 10", each assigned to couplings 2, is designed to cumulatively store the following coupling-specific operating data: A coupling 2 can be in one of several coupling positions. Possible coupling positions are ready to couple, closed, or in buffer position. Corresponding sensor data can be provided to the operating data storage device 10', 10" via data line 3.

[0076] The operational data storage device is further configured to store the number of clutch position changes. Several classes can be defined for this purpose, where each class can specify a type of position change. For example, a first class can specify that a clutch position change is performed from "ready to clutch" to "closed," and a second class can specify that a change is performed from "closed" to "ready to clutch." Corresponding classes can be defined for the buffer position. In addition to the absolute count, the frequency of a change within a time interval, for example, daily, or average values ​​over a longer period can also be stored.

[0077] It is also planned to record the total number of errors occurring during coupling operations, i.e., coupling operations that are not performed correctly.

[0078] If a coupling operation is unsuccessful, it can be repeated until a successful connection is established. The task of the operational data storage device is therefore to store the average number of repetitions required for a successful coupling operation in a memory location. Additionally, some embodiments provide for the recording and cumulative storage of supplementary coupling information for each coupling operation. Separate classes can be defined for this supplementary coupling information, allowing the coupling information to be stored cumulatively within these classes. For example, it is conceivable that a multitude of classes could be defined for the duration of a coupling operation, each specifying a time period for a coupling operation. Furthermore, current consumption can be recorded as coupling information for individual classes, with different classes specifying different time intervals.The current consumption of an actuator performing the coupling operation can then be stored cumulatively for each class. Correspondingly, the voltage can also be stored cumulatively. Furthermore, it is conceivable to define classes for electrical power and to store cumulatively the time that an actuator performing the coupling operation consumes power within a given power interval. The aforementioned coupling information can also be recorded separately for each operation, i.e., opening, closing, or buffer position, and stored cumulatively. The change in power consumption or the time spent in specific power classes is a particularly good indicator of coupling wear.

[0079] In addition, or alternatively, it is conceivable to store cumulatively how often a coupling process is triggered manually via a switch on the wagon or via data line 3.

[0080] Furthermore, the number of bouncing events that occur during a coupling operation can be recorded cumulatively. For example, bouncing will frequently occur when using the buffer position on a hump yard, such as when a wagon that has already been uncoupled runs into a train section where coupling is not desired (the buffer position prevents automatic coupling in this case). Since large forces are involved in bouncing, the number of bouncing events is also relevant for determining wear. Bouncing can be measured, for example, with an accelerometer, such as an inertial measurement unit, where a large acceleration in one spatial direction during the buffer position of the coupling can indicate bouncing.

[0081] Additionally or alternatively, connection setup times can be stored for specific classes, where a class can define a time interval. The measured connection setup times can indicate the time a train component needs to fully connect to other systems. For example, connection setup times can indicate the time required to fully connect file line 3 and enable communication via this file line 3 with the connected systems. For example, contamination can cause the connection to be attempted multiple times, thus extending the connection setup time. In this respect, connection setup times are another indicator of wear and tear.

[0082] The total number of kilometers driven with the clutch can be stored in another memory location of the operating data storage device.

[0083] The total number of operating hours of the clutch can be stored in a separate memory location of the operating data storage device. An operating hour can be defined as the time during which the clutch's electronics are powered.

[0084] The operational data storage device 10 can be configured to store the average coupling speed. This is the speed assumed by the rail-guided vehicle, to which the coupling 2 is attached, during the coupling process. It is also conceivable to store the minimum and / or maximum coupling speed.

[0085] It is also possible that the operating data storage device 10', 10" stores the average temperature of the on-board electronics of coupling 2. It is also conceivable to store maximum and minimum temperature values.

[0086] In addition to the operating data for individual couplings 2 or wagons 1, the operating data for a wagon train or a train with a power car can also be stored. An operating data storage device 10, 10', 10" can be used for this purpose, which is arranged either in a coupling 2, a wagon 1, or a power car. The operating data storage device 10, 10', 10" can be configured, in particular, to store the number of journeys over specific train lengths. Train lengths can be divided into individual classes, so that the number of journeys for each train length class can be stored. Similarly, the number of journeys for individual classes of train weight can be stored. Furthermore, the number of train integrity violations can be stored. Train integrity refers to whether all wagons intended for a train are present, i.e., coupled together.If an unintentional uncoupling occurs, the train integrity is violated.

[0087] Additionally or alternatively, voltage or current requirements, e.g., an average, can be stored cumulatively. Furthermore, average setup times of a train bus can be stored, for example, via data line 3.

[0088] The Fig. 2 Figure 1 shows a schematic representation of a wagon arrangement 6, consisting of a first wagon 1 and a second wagon 1'. Further wagons are indicated in the diagram. Wagons 1 and 1' correspond to the wagon of the Fig. 1The wagons 1, 1' have corresponding operational data storage devices 10, 10'. In the illustrated embodiment, the operational data storage devices 10, 10' are configured to transmit the stored cumulative operational data to a server unit 20. The server unit 20 can thus store the operational data of a plurality of operational data storage devices 10, 10', 10". The server unit 20 is configured to store relationships between operational data storage devices 10, 10', 10". For example, the server unit 20 can be configured to store which operational data storage device 10, 10', 10" belongs to a wagon train 6, a wagon 1, 1', and / or a coupling 2. This allows for the implementation of a hierarchical storage arrangement (see Figure 10). Fig. 6 ).

[0089] Carriages 1 and 1' are communicatively connected to each other via data line 3.

[0090] In the embodiment shown, the wagon 1' has a positioning unit 5 which provides a position information, e.g. GPS coordinates, via the data line 3, so that the operational data storage device 10 can use this data provided by the positioning unit 5 for accumulation.

[0091] The Fig. 3Figure 1 shows a schematic representation of a system 100 with wagons 1, 1', 1", which in the illustrated embodiment are arranged independently of one another, i.e., they are not part of the same wagon train. The operational data storage devices arranged in the wagons 1, 1', 1" transmit the accumulated operational data via a communication network 22, for example, a mobile communication network, to a server unit 20. The server unit 20 can be located in a data center; in particular, the server unit 20 can be a distributed storage system. The server unit 20 has storage units 21, 21', 21". The storage units 21, 21', 21" can be database units, e.g., relational database systems. Server unit 20 is designed to store the operational data received from the operational data storage units 10, 10', 10" in the storage units 21, 21', 21".Server unit 20 also includes a computing unit (not shown) designed to perform a fleet analysis using the cumulative operational data stored in storage units 21, 21', 21".

[0092] The Fig. 4Figure 10 shows a schematic representation of an operational data storage device 10. The operational data storage device 10 comprises a communication unit 11, a processing unit 12, a storage unit 13, and an optional wireless communication unit 14. The communication unit 11 is configured to receive operational data 16. The operational data 16 is processed by the processing unit 12, in particular in aggregate form, so that aggregated operational data 17 is stored by the storage unit 13. Optionally, the stored aggregated operational data 18 can be transmitted via the wireless communication unit 14 to a remote server unit 20. For this purpose, the wireless communication unit has an antenna 15 to establish a connection with a mobile network, for example.

[0093] In the illustrated embodiment, the stored cumulative operating data 18 are transmitted once per time unit, for example, once per week, once per month, once per year, via the wireless communication unit 14. After the stored cumulative operating data 18 have been transmitted, they are deleted from the storage unit 13 by the processing unit 12. However, it is also conceivable that the most recently existing cumulative values ​​are not deleted, so that the accumulation can continue even after transmission.

[0094] The Fig. 5 shows a schematic representation of a matrix 60, which shows the storage of cumulative operational data 17.

[0095] In matrix 16, each column corresponds to a class C1-C5 of operating data. In the illustrated embodiment, classes C1-C5 represent speed ranges. Thus, class C1 represents a speed range of 0-10 km / h, class C2 a speed range of 11-50 km / h, class C3 a speed range of 51-100 km / h, class C4 a speed range of 101-200 km / h, and class C5 a speed range above 201 km / h, with this range being open-ended. Classes where speed ranges have negative signs are also conceivable, in which case the sign can indicate a direction of travel.

[0096] For each class C1-C5, cumulative values ​​are now stored. In the illustrated embodiment, 17 hours of operating data are stored. Cell S1 indicates that the operating data storage device 10, which stores matrix 60, moved for 100 minutes at a speed specified by the speed range of class C1. Corresponding values ​​are stored for cells S2-S5.

[0097] Of course, it is possible that other cumulative operating data 17 are stored in cells S1-S5 instead of operating hours or minutes. For example, the distance traveled in kilometers could be stored for each class C1-C5. It is also conceivable that the matrix 60 is configured as a multidimensional tensor, allowing operating data 17 to be assigned to multiple classes or types. Thus, a multidimensional tensor could be used to cumulatively store information such as whether an operating data storage device 10 was operated at a certain speed within a specific speed range in a particular country.

[0098] The Fig. 6 shows one way of storing the accumulated operational data 17. In the example of the Fig. 6A tree 30 is used as a data type, containing nodes 31-37. Using tree 30, it is possible to store a hierarchy of operational data storage devices. Tree 30 has a root node 31, which can be used to store the cumulative operational data 17, which is train-specific. For example, the operational data 17 stored by an operational data storage device located in a power car of a train can be stored.

[0099] In nodes 32 and 33, which are located on the second level of tree 30, the operational data 17, which is wagon-specific, can be stored. For example, the operational data 17, which is accumulated by operational data storage devices arranged on wagons, for example as part of a wagon control unit, can be stored.

[0100] Nodes 34-37 of tree 30 form leaves that can be used to store cumulative operational data 17, which are generated by

[0101] Operational data storage devices are stored, for example, on couplings, e.g., as part of a coupling control unit. Such hierarchical storage makes it possible to maintain relationships between operational data storage devices. Furthermore, when a change occurs, e.g., a wagon from one wagon arrangement to another, the corresponding subtree 38 can be copied or moved and inserted into another tree representing a second wagon train. Similarly, individual nodes 31-37 can also be moved.

[0102] Fig. 7Figure 47 shows a flowchart for a process 40 for accumulating operational data 17. The process 40 begins with a measurement step 41 in which operational data are measured, e.g., a speed, a position, and / or a temperature. In the subsequent accumulation step 42, the measured operational data are accumulated and stored in a memory unit in the following storage step 43. Optionally, event data 44 can be used in the accumulation step 42 or in the storage step 43 to trigger the accumulation or storage, respectively. The event data 44 can, for example, be provided by a timer that supplies event data 44 at regular intervals. Alternatively, it is conceivable that external factors are taken into account when generating the event data 44.After saving the accumulated operating data in step 43, the procedure continues with another measurement step 41, thus ensuring a cyclic execution of the procedure 40.

[0103] The Fig. 8 Figure 50 shows a flowchart illustrating a procedure for accumulating operational data. Steps 51-53 correspond to steps 41-43 of the previous figure. Fig. 7After storage step 53, a test step 54 checks whether the stored cumulative operating data should be transmitted to an external storage device. In test step 54, a transmission criterion can be checked, for example, whether a certain period of time has elapsed since the last transmission or whether a specific number of operating data points have been accumulated. If it is determined that the test criterion is met, the memory contents of the associated storage unit are read in a transmission step 55, and the stored cumulative operating data is transmitted to an external storage unit, for example, via a wireless communication unit. In this case, the procedure continues with measurement step 51.

[0104] If it is determined that the test criterion in test step 54 is not met, the procedure proceeds directly to measurement step 51.

[0105] It should be noted that all the parts described above, individually—even without additional features described in the respective context, even if these have not been explicitly identified as optional features in the respective context, e.g., by using "in particular," "preferably," "for example," "if applicable," parentheses, etc.—and in combination or any sub-combination, are to be considered independent embodiments or further developments of the invention, as defined in particular in the introduction and the claims. Deviations from this are possible. Specifically, it should be noted that the word "in particular" or parentheses do not indicate features that are mandatory in the respective context. Reference symbol list

[0106] 1, 1', 1" Wagon 2Coupling 3Data line 4Cargo space 5Positioning unit 6Wagon arrangement 7Brake 10, 10', 10"Operational data storage device 11Communication unit 12Computer unit 13Storage unit 14Wireless communication unit 15Antenna 16Operational data 17Cumulative operational data 18Stored cumulative operational data 20Server unit 21, 21', 21"Storage unit 22Communication network C1, C2, C3, C4, C5Class S1, S2, S3, S4, S5Cell 30Tree 31-37Node 38Subtree 40Operational data accumulation method 41Measurement step 42Amount step 43Storage step 44Event data 50Operational data accumulation method 51 Measurement step 52 Accumulation step 53 Storage step 54 Test step 55 Transmission step 60 Matrix 100 System

Claims

1. Operational data storage device (10), in particular for a rail-guided vehicle (1, 1', 1"), e.g. a wagon (1, 1', 1") and / or a traction vehicle, preferably for a coupling (2) of a rail-guided vehicle (1, 1', 1"), comprising the following: - a communication unit (11) for receiving operational data (16) relating to at least one rail-guided vehicle (1, 1', 1"); - a processing unit (12) for generating cumulative operational data (17) to be stored from the received operational data (16); - a storage unit (13) for storing the cumulative operational data (17).

2. Operational data storage device (10) according to claim 1 characterized by the fact that the storage unit (13) is designed to store the cumulative operating data (17) to be stored in a defined number of storage locations (S1-S5) in the storage unit (13).

3. Operational data storage device (10) according to one of the preceding claims, characterized by the fact that the computing unit (12) is designed to combine the received operating data (16) with stored cumulative operating data (18) when accumulating the operating data (16).

4. Operational data storage device (10) according to one of the preceding claims, characterized by the fact that the computing unit (12) is designed to perform a mathematical and / or logical operation using the cumulative operating data (18) stored in the storage unit (13) and the received operating data (16) in order to generate the cumulative operating data (16) to be stored.

5. Operational data storage device (10) according to one of the preceding claims, characterized by the fact thatthe storage unit (13) has a defined number of storage locations for storing the accumulated operational data (17), wherein a storage location (S1-S5) is assigned to a type and / or class (C1-C5) of operational data (16).

6. Operational data storage device (10) according to one of the preceding claims, in particular according to claim 4, characterized by the fact that Each class (C1-C5) of operational data (16) is assigned to a type of operational data (16).

7. Operational data storage device (10) according to one of the preceding claims, in particular according to claim 4 or 5, characterized by the fact that the storage unit (13) is configured to store cumulative operational data (17) as an n-dimensional matrix (30), where n is a natural number, wherein a cell of the matrix (30) is preferably assigned to a class (C1-C5) of a type of operational data (16).

8. Operational data storage device (10) according to one of the preceding claims, characterized by the fact thatthe computing unit (12) is designed to accumulate operational data (16) in response to an event, in particular to accumulate only in response to an event.

9. Operational data storage device (10) according to one of the preceding claims, in particular according to claim 7, characterized by the fact that the communication unit (11) is designed to be connectable to a data line, in particular to a communication bus (3), and is further designed to receive a data (44) via the data line, preferably via the communication bus (3), which indicates an event.

10. Operational data storage device (10) according to one of the preceding claims, in particular according to claim 7, characterized by the fact that an event is specified by a timer, wherein the timer is configured to provide the event preferably at a defined frequency.

11. Operational data storage device (10) according to one of the preceding claims, characterized by a readout unit, in particular a wireless communication unit (14), which is configured to transfer the stored cumulative operating data (18) to an external storage unit (20), e.g. a mass storage device or a data center (20), wherein the storage unit (13) is preferably configured to delete the stored cumulative operating data (18) in response to the transfer.

12. Rail-guided vehicle, train coupling (2) or wagon (1), in particular train wagon (1) with an operational data storage device (10) according to one of the preceding claims.

13. Wagon arrangement (6) comprising at least two wagons (1, 1') according to claim 12, wherein the respective operational data storage devices (10) are connected to each other via a data line, in particular via a communication bus (3).

14. System (100) for operational data acquisition, comprising: - At least one operational data storage device (10) according to any one of claims 1-10; - At least one server device (20) configured to receive and store cumulative operational data (18) from the at least one operational data storage device (10).

15. System (100) according to claim 14, characterized by the fact that which includes at least one server facility (20) trained to perform a fleet analysis using the cumulative operational data (18) for a plurality of operational data storage facilities (10).

16. System according to claim 15, characterized by the fact that The fleet analysis includes the identification of at least one operational data storage device (10) whose cumulative operational data (18), preferably for a type of operational data (16) and / or a class (C1-C6), exhibits a statistical anomaly, e.g., is outside a normal range.

17. Computer-implemented method (40) for storing operational data (16) comprising the following steps: - Receiving (41) operational data (16) via a communication unit (11), wherein the operational data (16) are related to at least one rail-guided vehicle (1, 1'); - Generating (42) cumulative operational data (17) to be stored from the received operational data (16); - Storing (43) the cumulative operational data (17) in a storage unit (13).

18. Computer-implemented method according to claim 17, characterized by the fact that Storing the cumulative operational data to be stored involves storing it in a defined number of storage locations within the storage unit.

19. Non-volatile, computer-readable storage medium configured to store instructions that cause at least one processor to implement the method of claim 15 when the instructions are executed by the at least one processor.

Images