Data-driven safety production management method and system, and device and storage medium

Abstract

The present application relates to the technical field of data processing. Disclosed are a data-driven safety production management method and system, and a device and a storage medium. The method comprises: on the basis of an event level of accident data and a preset indicator of each event level, obtaining an accident safety indicator achievement result of an enterprise; analyzing the accident safety indicator achievement result in at least one preset dimension, so as to obtain accident distribution information; and generating action item tracking information on the basis of the accident distribution information, wherein the action item tracking information is used for tracking a handling progress of an accident. The present application can fully tap into the value of enterprise production data.

Description

Data-driven safety production management methods, systems, equipment, and storage media

[0001] This application claims priority to the earlier application, application number 202410417443.4, entitled "Data-driven safety production management method, system, equipment and storage medium", with a priority date of 2024-04-09. Technical Field

[0002] This application belongs to the field of data processing technology, and in particular relates to a data-driven method, system, equipment and storage medium for safe production management. Background Technology

[0003] Safety in production is a crucial foundation for the sustainable development of an enterprise. Therefore, monitoring and managing safety indicators is an important step in production.

[0004] Current safety monitoring of enterprise production mainly relies on data collection and data quantification to reduce the workload of staff. However, it only collects data and does not analyze enterprise production data from different dimensions, nor does it deeply explore the value of enterprise production data.

[0005] It should be noted that the above statements are only used to provide background information related to this application and do not necessarily constitute prior art.

[0006] Summary of the Invention

[0007] In view of this, the purpose of this application is to propose a data-driven safety production management method, system, equipment and storage medium, which can specifically solve the problem that existing solutions cannot fully tap the value of enterprise production data.

[0008] Based on the above objectives, in a first aspect, this application proposes a data-driven safety production management method, the method comprising: obtaining the enterprise's accident safety indicator achievement results based on the event level of accident data and preset indicators for each event level; analyzing the accident safety indicator achievement results from at least one preset dimension to obtain accident distribution information; and generating action item tracking information based on the accident distribution information, the action item tracking information being used to track the progress of accident handling.

[0009] The above embodiments obtain the enterprise's accident safety indicator achievement results by using the event level of accident data and the preset indicators of each event level. This can comprehensively display the enterprise's accident status, analyze the accident safety indicator achievement results from at least one preset dimension, obtain accident distribution information based on different dimensions, and mine and analyze enterprise accident data from different angles. This can uncover the relationship between data from different dimensions, improve the analytical capabilities of accident data, realize multi-dimensional cross-analysis of enterprise accident data, and generate action item tracking information based on accident distribution information to track the progress of accident handling. This enables tracking of handling measures after an accident occurs and achieves closed-loop improvement of accidents.

[0010] In some embodiments, before obtaining the results of the enterprise's accident safety indicators, the method further includes: determining the event level of the accident data based on one or more of the following: the subject of the accident, the number of injured persons, the degree of injury, and the type of accident; and determining a preset indicator for each event level based on the number of occurrences of each event level in historical accident data within a preset period.

[0011] Before obtaining the results of the enterprise's accident safety indicators, the above embodiments help to improve the accuracy of the accident safety indicator achievement results by determining the event level of the accident data and the preset indicators for each event level.

[0012] In some embodiments, analyzing the achievement results of the accident safety indicators from at least one preset dimension to obtain accident distribution information includes: analyzing the achievement results of the accident safety indicators according to a combination of preset dimensions and preset time periods to obtain the accident distribution information; wherein, the combination of preset dimensions and preset time periods includes at least one of the following: a combination of the same preset dimension and different preset time periods, and a combination of different preset dimensions and the same time period.

[0013] The above embodiments analyze the results of accident safety indicators by combining preset dimensions and preset time periods, which can realize multi-dimensional cross-analysis of enterprise accident data and mine and analyze enterprise accident data from different perspectives.

[0014] In some embodiments, after obtaining accident distribution information, the method further includes: in response to accident cause query information, obtaining the cause of the accident according to a preset accident cause analysis table, wherein the accident cause analysis table stores the correspondence between accidents and accident causes.

[0015] The above embodiments can analyze the causes of accidents through an accident cause analysis table, which can help enterprise managers analyze the causes of accidents and improve safety management efficiency.

[0016] In some embodiments, generating action item tracking information based on the accident distribution information includes: issuing an early warning when the event level of an accident occurring in the accident distribution information is greater than a preset indicator; and generating the action item tracking information based on the early warning information.

[0017] The above embodiments can monitor and warn about enterprise safety, improve enterprise safety performance, and generate action item tracking information based on the early warning information. On the one hand, it can track the handling measures after the accident and realize closed-loop improvement of the accident. On the other hand, it can provide experience data for the future occurrence of similar accidents and improve safety management efficiency.

[0018] In some embodiments, the method further includes: classifying accident data according to the type of base where the accident occurred, into manufacturing bases and non-manufacturing bases; calculating and ranking the safety performance of each manufacturing base and non-manufacturing base respectively, to obtain safety performance data for each base.

[0019] The above embodiments help to compare the security of bases of the same type, reduce ranking errors caused by different base properties, make performance data more reasonable, and help improve the efficiency of enterprise security management.

[0020] In some embodiments, the calculation and ranking of the safety performance of each manufacturing base and non-manufacturing base to obtain safety performance data for each base includes: weighting the events of each level according to preset weights and the incidence rate of accidents of different event levels in preset statistical units to obtain the performance score of each base; and ranking the performance scores in order of magnitude to obtain the safety performance data of each base.

[0021] The above embodiments calculate the performance score of each base by weighting the occurrence rate of accidents of different event levels under preset statistical units and using preset weights and events of different event levels. This results in a comprehensive evaluation, making the performance score of each base more reasonable and improving the accuracy of safety performance data for each base.

[0022] Secondly, a data-driven safety production management system is also provided. The system includes: a safety monitoring module, used to obtain the enterprise's accident safety indicator achievement results based on the event level of accident data and preset indicators for each event level; an accident analysis module, used to analyze the accident safety indicator achievement results from at least one preset dimension to obtain accident distribution information; and an accident tracking module, used to generate action item tracking information based on the accident distribution information, wherein the action item tracking information is used to track the progress of accident handling.

[0023] Thirdly, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor running the computer program to implement the method of the first aspect.

[0024] Fourthly, a computer-readable storage medium is also provided, on which a computer program is stored, the program being executed by a processor to implement the method described in any one of the first aspects.

[0025] The above description is merely an overview of the technical solution of this application. To enable a clearer understanding of the technical means of this application and to facilitate its implementation according to the description, and to make the above and other objects, features, and advantages of this application more apparent, specific embodiments of this application are described below. Attached Figure Description

[0026] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments disclosed in this application and should not be construed as limiting the scope of this application. Furthermore, the same reference numerals denote the same parts throughout all the drawings.

[0027] Figure 1 shows a flowchart of the steps of a data-driven safety production management method provided in an embodiment of this application;

[0028] Figure 2 shows a display interface diagram of the accident safety indicator achievement results of an enterprise according to an embodiment of this application;

[0029] Figure 3 shows a display interface for accident distribution information provided in an embodiment of this application;

[0030] Figure 4 shows a display interface diagram of action item tracking information provided in an embodiment of this application;

[0031] Figure 5 shows the display interface of the warning information in an embodiment of this application;

[0032] Figure 6 shows a schematic diagram of the structure of a data-driven safety production management system provided in an embodiment of this application;

[0033] Figure 7 shows a schematic diagram of an electronic device provided in an embodiment of this application;

[0034] Figure 8 shows a schematic diagram of a storage medium provided in an embodiment of this application. Detailed Implementation

[0035] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0037] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0038] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0039] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0040] In the description of the embodiments of this application, the term "multiple" refers to two or more (including two), similarly, "multiple sets" refers to two or more (including two sets), and "multiple pieces" refers to two or more (including two pieces).

[0041] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0042] Safe production is a crucial foundation for a company's sustainable development, and monitoring and managing safety indicators is a vital step in production. While existing companies can reduce staff workload by developing data management platforms to monitor production safety primarily through data collection and quantification, this often involves merely data collection. In other words, the data management platforms in these technologies serve only as output terminals for storing, recording, and displaying single data points, without analyzing production data across different dimensions or deeply exploring its value. This results in a low level of data-driven operation.

[0043] Based on this, this application provides a data-driven safety production management method. According to the event level of accident data and preset indicators for each event level, the method obtains the enterprise's accident safety indicator achievement results. It can present the event level of accidents occurring in the enterprise and the comparison results of each event level with preset indicators to enterprise managers, providing users with a comprehensive overview of accident occurrences. By analyzing the accident safety indicator achievement results from at least one preset dimension, accident distribution information is obtained. This allows for analysis of accident occurrences from multiple dimensions, enabling cross-analysis of accident data, uncovering relationships between data from different dimensions, and improving the analytical capabilities of accident data. Based on the accident distribution information, action item tracking information is generated to track the progress of accident handling, enabling the tracking of post-accident handling measures and achieving closed-loop improvement of accidents.

[0044] The data-driven safety production management method in this embodiment can be applied to enterprises of different industries and sizes. This embodiment takes a battery company as an example.

[0045] Figure 1 shows a flowchart of the steps of a data-driven safety production management method provided in an embodiment of this application. As shown in Figure 1, in an embodiment of this application, a data-driven safety production management method includes the following steps S101 to S103:

[0046] S101. Based on the event level of the accident data and the preset indicators for each event level, obtain the results of the company's accident safety indicator achievement.

[0047] S102. Analyze the achievement results of the accident safety indicators from at least one preset dimension to obtain accident distribution information.

[0048] S103. Generate action item tracking information based on accident distribution information. The action item tracking information is used to track the progress of accident handling.

[0049] The executing entity in this application embodiment can be an electronic device capable of executing a data-driven safety production management method, and the electronic device may include, but is not limited to, a terminal or a server.

[0050] In this embodiment of the application, the accident data includes information on safety-related accidents that have occurred in the enterprise. For example, one accident information is "an employee of the enterprise suffered a work-related injury", and another accident information is "a smoke and fire incident occurred in a factory that the enterprise has delivered".

[0051] In one example, a battery company may include different types of subsidiaries, such as Class I, Class II, and Class III subsidiaries.

[0052] In this embodiment, potential safety incidents for battery companies may include incidents of the same or different levels occurring in different types of subsidiary companies. For example, a Class I subsidiary may experience a Level 4 incident, and a Class II subsidiary may also experience a Level 4 incident. Another example is a Class III subsidiary experiencing a Level 3 incident, and a Class II subsidiary experiencing a Level 2 incident.

[0053] The severity level of an accident event is characterized by its degree of severity, and is set from low to high. In this embodiment, the accident event levels may include near misses, minor abnormal events, Level 1 events, Level 2 events, Level 3 events, and Level 4 events. For example, an event that results in loss of life is a Level 4 event, an event that results in serious injury is a Level 3 event, an event that results in extensive damage to property is a Level 2 event, and an event that results in slurry leakage is a Level 1 event.

[0054] Different incidents may fall under the same incident level. For example, a Level 4 incident could be one that results in loss of life or one that causes significant direct economic losses to the company. Specific incident levels can be customized by the company's safety management personnel, and will not be elaborated upon here.

[0055] In this embodiment, the preset index for each event level is used to control the number of accident events at each level. For example, in one year, the preset index for level 4 events is 0, the preset index for level 3 events is 1, the preset index for level 2 events is 2, and the preset index for level 1 events is 4. The specific preset index for each event level can be customized according to the company's own safety management status or the number of historical accidents.

[0056] In this embodiment, the results of the enterprise's accident safety indicators can reflect the actual accident situation that occurred within a preset period, and whether the accidents that occurred within the preset period exceeded the preset indicators, thereby enabling the enterprise's safety managers to clearly understand the enterprise's safety status.

[0057] In one example, the accident safety indicator achievement results of an enterprise according to an embodiment of this application can be displayed on a page. Figure 2 shows a display interface diagram of the accident safety indicator achievement results of an enterprise according to an embodiment of this application. As shown in Figure 2, the user can select the display period through the control panel, such as "Monthly KPI" in Figure 2. The display period can also be changed by selecting the "Annual" selection control on the control panel.

[0058] The control panel can be divided into multiple display areas according to the event level. Each display area shows the "target value" and the "actual value". The "target value" is the preset indicator for each event level in the selected period, and the "actual value" is the actual number of occurrences of each event level in the selected period.

[0059] In one example, performance values ​​can be set according to different event levels, as shown in Figure 2. Four display areas are set up according to the severity of the incident, corresponding to "Level 4 Personnel Injury Incidents in Category I Enterprises," "Level 4 Incidents in Category II and III Enterprises," "Level 1-3 Work-Related Injury Incidents and Fire Alarm Incidents," and "Level 1-3 Chemical Leakage Incidents." Fire alarm incidents refer to fire alarm events, including combustion events with open flames and fire-related events that produce smoke but not open flames. The events represented by the four display areas can also be represented by performance labels, such as Performance A, Performance B, Performance C, and Performance D, to indicate the severity of safety incidents occurring in the enterprise within the selected period.

[0060] The preset dimensions in this application embodiment may include different dimensions such as event dimension, time dimension, accident cause dimension, various types of enterprise dimension, base dimension, factory dimension, process dimension, and line dimension. By analyzing the achievement results of accident safety indicators from at least one preset dimension, accident distribution information can be obtained. This can realize multi-dimensional cross-analysis of enterprise accident data and mine and analyze enterprise accident data from different perspectives.

[0061] Different preset dimensions can be set to achieve grid division, grid management, and grid monitoring for the entire group. For example, dividing the group into base, factory, process, and production line dimensions can form grids of levels 1-4. When managing the group's safety indicators, grid management can be achieved by decomposing employee safety production tasks to each level of grid for implementation. Furthermore, grid monitoring can be achieved by monitoring and providing real-time feedback on the execution of safety tasks and the safety production status of each grid.

[0062] In one example, a safety performance evaluation mechanism can be established based on the safety task execution of each grid, such as the achievement of accident safety indicators, thereby realizing grid-based evaluation for the group and benefiting the overall safety management of the group.

[0063] Weak links in the grid-based safety indicators can be identified to form production management improvement actions, which can then be tracked and implemented in a closed loop to achieve corrective action.

[0064] In one example, task assignment and management for each grid can be shown in Table 1 below.

[0065] Table 1:

[0066] In one example, the results of accident safety indicator achievement are analyzed using event and time dimensions. The resulting accident distribution information is shown in Figure 3, which illustrates a display interface for accident distribution information provided in an embodiment of this application. Users can select the time period to query using the time selection control, such as "2023-09-01~2023-09-06". They can also select specific events to query using the event selection control, such as "personnel injury", "chemical leak", or "base fire". After determining the query dimensions, the system displays the specific event levels and quantities occurring within the queried time period, along with the corresponding warning values, providing a clear and intuitive view of accident distribution information across different dimensions.

[0067] In this embodiment of the application, action item tracking information is generated based on accident distribution information. The action item tracking information is used to track the progress of accident handling. For example, after an accident occurs, this embodiment of the application can generate a list of action items, and users can check the progress of accident handling by viewing the list of action items.

[0068] Figure 4 shows the display interface of action item tracking information provided in this embodiment of the application. As shown in Figure 4, the action item list can display information such as "Action Item Name", "Responsible Person", "Initiator", "Associated Module", "Action Item Description", "Planned Completion Time", "Actual Completion Time", "Current Status", and "Operation Item". Among them, "Action Item Name" can be the specific accident name, "Associated Module" can display the accident cause associated with the accident, "Action Item Description" can display the person in charge's description of the current accident, and "Operation Item" can change the progress of the action item list, such as marking the action item of the accident as "Completed" after the current accident has been handled.

[0069] The above embodiments obtain the enterprise's accident safety indicator achievement results by using the event level of accident data and the preset indicators of each event level. This can comprehensively display the enterprise's accident status, analyze the accident safety indicator achievement results from at least one preset dimension, obtain accident distribution information based on different dimensions, and mine and analyze enterprise accident data from different angles. This can uncover the relationship between data from different dimensions, improve the analytical capabilities of accident data, realize multi-dimensional cross-analysis of enterprise accident data, and generate action item tracking information based on accident distribution information to track the progress of accident handling. This enables tracking of handling measures after an accident occurs and achieves closed-loop improvement of accidents.

[0070] In this embodiment of the application, before obtaining the results of the enterprise's accident safety indicators, the method of this embodiment of the application further includes: determining the event level of the accident data based on one or more of the following: the subject of the accident, the number of injured persons, the degree of injury, and the type of accident; and determining the preset indicator for each event level based on the number of occurrences of each event level in the historical accident data of a preset period.

[0071] In this embodiment, the subjects of the accident include the enterprise and its type, the base where the accident occurred, etc., and the accident types include casualties, economic losses, fires, raw material leaks, etc.

[0072] In one example, relevant personnel within the company can customize the event level range for incident data based on actual circumstances, for example:

[0073] Level 4 incidents include: For Class I enterprises, incidents involving the loss of life of employees, suppliers, visitors, etc., who are engaged in production, research and development, or renovation work within the delivered factory due to work-related reasons; or for Class II and III enterprises, incidents resulting in the following outcomes: 1) incidents causing the loss of life of n or more people; 2) incidents causing serious injury to m or more people; 3) incidents causing direct economic losses of x million or more; 4) incidents throughout the year that are reported by relevant authorities due to violations of safety, occupational health, and environmental protection regulations.

[0074] Level 1 to 3 incidents include: incidents that result in workplace injuries to employees or smoke and fire at factories under construction or already built, classified as Level 1 to 3 according to the severity of the consequences; or incidents that result in leaks of powders, slurries, electrolytes, laboratory reagents, etc., classified as Level 1 to 3 according to the severity of the consequences.

[0075] Minor abnormal events include: incidents where people fall and suffer minor injuries, and incidents that trigger warnings of equipment aging.

[0076] Near misses include events such as equipment warnings that do not affect production, and taking timely measures before tools are lost.

[0077] Specific events and their severity levels can be customized and adjusted by relevant personnel within the company, and will not be elaborated upon here. In one example, the above-mentioned accident events and their severity levels can be compiled into a severity level range lookup table and stored. When new accident data is added, the severity level corresponding to the new accident data can be obtained by analyzing the specific content of the new accident data and comparing it with the severity level range lookup table.

[0078] Based on the number of occurrences of each event level in historical accident data within a preset period, preset indicators for each event level are determined. In other words, the preset indicators in this application can be obtained from historical data, which improves the accuracy of setting preset indicators and allows for comparison of the company's current safety situation with historical situations, making it easier for relevant personnel to understand the company's safety status. The preset period can be a custom period such as one week, one month, or one year.

[0079] Before obtaining the results of the enterprise's accident safety indicators, the above embodiments help to improve the accuracy of the accident safety indicator achievement results by determining the event level of the accident data and the preset indicators for each event level.

[0080] In this embodiment of the application, the above-mentioned analysis of the achievement results of the accident safety indicators from at least one preset dimension to obtain accident distribution information includes: analyzing the achievement results of the accident safety indicators according to the combination conditions of preset dimensions and preset time periods to obtain accident distribution information; wherein, the combination conditions of preset dimensions and preset time periods include at least one of the combination conditions of the same preset dimension and different preset time periods, and the combination conditions of different preset dimensions and the same time period.

[0081] In this embodiment, the preset dimensions may include different dimensions such as event dimension, time dimension, accident cause dimension, various types of enterprise dimension, and base dimension. The preset time period may include a week, a month, a year, etc.

[0082] The combination of the same preset dimension and different preset time periods, such as the accident distribution information of chemical spill events during the period from "2023-09-01 to 2023-09-06" and from "2023-10-01 to 2023-10-06".

[0083] Combination conditions of different preset dimensions and the same time period, such as the distribution information of chemical spill incidents and fire alarm incidents during the period of "2023-09-01~2023-09-06" and "2023-10-01~2023-10-06", respectively.

[0084] Users can select any combination of preset dimensions and preset time periods through the interface shown in Figure 3, and then output the corresponding accident distribution information.

[0085] The above embodiments analyze the results of accident safety indicators by combining preset dimensions and preset time periods, which can realize multi-dimensional cross-analysis of enterprise accident data and mine and analyze enterprise accident data from different perspectives.

[0086] In this embodiment of the application, after obtaining the accident distribution information, the method further includes: responding to the accident cause query information, obtaining the cause of the accident according to a preset accident cause analysis table, wherein the accident cause analysis table stores the correspondence between accidents and accident causes.

[0087] Among them, the accident cause query information can be triggered by the user, or it can be automatically brought out after the cause distribution information is obtained. For example, the accident cause query can be automatically triggered through the association module in Figure 3.

[0088] In this embodiment, the preset accident cause analysis table stores the correspondence between accidents and their causes. For example, the causes of a chemical spill include 30% personnel violating regulations and engaging in risky operations, 50% equipment defects, and 20% management failures; the causes of a fire alarm include 50% inadequate fire-fighting measures, 20% improper personnel operation, and 30% aging equipment; and the causes of personnel injury include 25% improper use of equipment, 25% construction and installation defects, 25% risky operations, and 25% violations of safe operating procedures. The specific settings can be based on historical data and will not be elaborated here.

[0089] In one example, after determining the cause of the accident, the cause can be displayed in the form of a table or pie chart.

[0090] The above embodiments can analyze the causes of accidents through an accident cause analysis table, which can help enterprise managers analyze the causes of accidents and improve safety management efficiency.

[0091] In this embodiment of the application, generating action item tracking information based on accident distribution information includes: issuing a warning when the event level of an accident occurring in the accident distribution information is greater than a preset indicator; and generating action item tracking information based on the warning information.

[0092] If the event level of an accident in the accident distribution information is greater than the preset indicator, it indicates that the number of accidents in the current period is greater than that in the historical period within a preset cycle. This indicates that the company's safety capabilities have declined and it needs to increase its safety attention, so an early warning message will be issued.

[0093] Figure 5 shows the display interface of the warning information in the embodiment of this application. As shown in Figure 5, users can obtain warning information by viewing the risk warning list. The warning information may include information such as "warning name", "actual value", "preset indicator value", "indicator deviation", "warning time", "warning level", "warning reason" and "related action items".

[0094] In one example, for the event level that triggers the warning, the system can automatically generate an action item list as shown in Figure 4, or the user can trigger the action item command, input improvement requirements and implementation plans, and the system can generate an action item list to track and manage the work progress of the relevant responsible persons, as shown in the action item list in Figure 4.

[0095] In the above embodiments, when the event level of an accident in the accident distribution information exceeds a preset indicator, an early warning message is issued, which can realize the monitoring and early warning of enterprise safety, improve the enterprise's safety performance, and generate the action item tracking information based on the early warning information. On the one hand, it can track the handling measures after the accident occurs, realize the closed-loop improvement of the accident, and on the other hand, it can provide experience data for the occurrence of similar accidents in the future, thereby improving the efficiency of safety management.

[0096] In this embodiment of the application, the data-driven safety production management method further includes: classifying accident data according to the type of base where the accident occurred, into manufacturing bases and non-manufacturing bases; calculating and ranking the safety performance of each manufacturing base and non-manufacturing base respectively, to obtain safety performance data for each base.

[0097] In this embodiment, accident data is classified according to manufacturing base and non-manufacturing base. For example, it can be classified according to battery cell manufacturing base and non-battery cell manufacturing base to facilitate safety comparison between bases of the same type, reduce ranking errors caused by different base nature, and make performance data more reasonable.

[0098] The safety performance of each manufacturing and non-manufacturing base is calculated and ranked separately to obtain safety performance data for each base. This data helps enterprise safety managers understand the safety ranking of each base and obtain the monthly and yearly safety ranking trends, which helps improve the efficiency of enterprise safety management.

[0099] The above embodiments help to compare the security of bases of the same type, reduce ranking errors caused by different base properties, make performance data more reasonable, and help improve the efficiency of enterprise security management.

[0100] In this embodiment of the application, the safety performance of each manufacturing base and non-manufacturing base is calculated and ranked to obtain safety performance data for each base. This includes: calculating a weighted average of events of each level based on preset weights and the occurrence rate of accidents of different event levels under preset statistical units to obtain a performance score for each base; and ranking the performance scores in order of magnitude to obtain the safety performance data for each base.

[0101] In one example, the preset weights can be set by relevant personnel according to the actual situation. For example, the weight of attempted events is 20%, the weight of minor abnormal events is 20%, the weight of level 1 to 3 events is 20%, and the weight of level 4 events is negative, that is, when a level 4 event occurs, points are deducted directly.

[0102] In one example, the preset statistical unit can be per million work hours, per person, per month, etc. In this embodiment, we take per million work hours as an example. The near miss rate per million work hours is the percentage of the number of near misses at the base in the current month to the total work hours of the base employees in the current month. The level 1 to 3 event rate per million work hours is the percentage of the number of level 1 to 3 events at the base in the current month to the total work hours of the base employees in the current month. And so on, we can obtain the occurrence rate of accidents of different event levels under the preset statistical unit.

[0103] Based on preset weights and the incidence rates of accidents of different event levels within preset statistical units, a weighted average is calculated for each event level to obtain the performance score for each base. This allows for the calculation of the total performance score for each month, quarter, year, and other periods. The performance scores are then ranked in order of magnitude to obtain the safety performance data for each base. This data can be presented to the company's safety management personnel in the form of charts to facilitate the company's assessment of the safety status of each base within each period.

[0104] The above embodiments calculate the performance score of each base by weighting the occurrence rate of accidents of different event levels under preset statistical units and using preset weights and events of different event levels. This results in a comprehensive evaluation, making the performance score of each base more reasonable and improving the accuracy of safety performance data for each base.

[0105] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

[0106] The following example illustrates the safety production management method in some embodiments of this application. The method is illustrated using a battery cell production base as an example.

[0107] All accident data from three battery cell production bases (Base 1, Base 2, and Base 3) over the past year were obtained. Bases 1, 2, and 3 belong to the same company. For each of these bases, the event level of the accident data was analyzed. Based on the preset indicators for each event level (e.g., the preset indicator for Level 4 events is 0, for Level 3 events is 1, for Level 2 events is 2, and for Level 1 events is 4), the actual occurrence of all accidents over the past year was compared with the preset indicators. This comparison serves as the accident safety indicator achievement result for each base. The accident safety indicator achievement results for Bases 1, 2, and 3 can be summarized to obtain the company's overall accident safety indicator achievement result. Company safety management personnel can access the company's accident safety indicator achievement result through the display interface shown in Figure 2.

[0108] When it is necessary to analyze the results of the achievement of the accident safety indicators from different dimensions, enterprise safety management personnel can select the specific event to query through the accident distribution information display interface shown in Figure 3. The results of the achievement of the accident safety indicators can be analyzed from at least one preset dimension, such as event dimension, time dimension, accident cause dimension, enterprise type dimension, and base dimension, to obtain accident distribution information. For example, by selecting "2023-09-01~2023-09-06" as the time period to be queried through the time selection control, and selecting "personnel injury", "chemical leak" and "base fire" as the specific events to be queried through the event selection control, after determining the query dimension, the accident distribution information of different dimensions can be intuitively displayed to the user by displaying the specific event level and number that occurred within the above query time period and the warning value corresponding to the event level.

[0109] After an incident occurs, this embodiment of the application can also generate an action item list, which users can view to check the progress of the incident handling. As shown in Figure 4, the action item list can display information such as "Action Item Name," "Responsible Person," "Initiator," "Associated Module," "Action Item Description," "Planned Completion Time," "Actual Completion Time," "Current Status," and "Operation Item." Among these, "Action Item Name" can be the specific incident name, "Associated Module" can display the incident cause associated with the incident, "Action Item Description" can display the responsible person's explanation of the current incident, and "Operation Item" can modify the progress of the action item list, such as marking the action item of the incident as "Completed" after the current incident has been handled. This allows for tracking of the handling measures after an incident occurs, achieving closed-loop improvement of the incident.

[0110] This application provides a data-driven safety production management system. Figure 6 shows a schematic diagram of the structure of a data-driven safety production management system provided in this application. Referring to Figure 6, the system 600 includes:

[0111] The safety monitoring module 601 is used to obtain the company's accident safety indicator achievement results based on the event level of the accident data and the preset indicators for each event level.

[0112] The accident analysis module 602 is used to analyze the achievement results of the accident safety indicators from at least one preset dimension to obtain accident distribution information.

[0113] The accident tracking module 603 is used to generate action item tracking information based on the accident distribution information, and the action item tracking information is used to track the progress of accident handling.

[0114] In one example, the safety monitoring module 601 is used to determine the event level of the accident data based on one or more of the following: the subject of the accident, the number of injured persons, the degree of injury, and the type of accident, before obtaining the results of the achievement of the enterprise's accident safety indicators; and to determine the preset indicator for each event level based on the number of occurrences of each event level in the historical accident data of a preset period.

[0115] In one example, the accident analysis module 602 is used to analyze the achievement results of the accident safety indicators according to the combination of preset dimensions and preset time periods to obtain the accident distribution information; wherein, the combination of preset dimensions and preset time periods includes at least one of the following: the combination of the same preset dimension and different preset time periods, and the combination of different preset dimensions and the same time period.

[0116] In one example, the accident analysis module 602 is used to obtain the accident distribution information and, in response to the accident cause query information, obtain the cause of the accident according to a preset accident cause analysis table, wherein the accident cause analysis table stores the correspondence between accidents and accident causes.

[0117] In one example, the accident tracking module 603 is used to issue an early warning message when the event level of an accident in the accident distribution information is greater than a preset indicator; and to generate the action item tracking information based on the early warning message.

[0118] In one example, the system 600 also includes a ranking module, which categorizes accident data into manufacturing and non-manufacturing bases based on the type of base where the accident occurred; calculates and ranks the safety performance of each manufacturing and non-manufacturing base separately, and obtains the safety performance data for each base.

[0119] In one example, the ranking module is also used to perform a weighted average of events of each level based on preset weights and the occurrence rate of accidents of different event levels under preset statistical units, to obtain the performance score of each base; and to rank the performance scores in order of size to obtain the safety performance data of each base.

[0120] The system and method provided in this application are based on the same inventive concept and have the same beneficial effects as the methods they employ, operate, or implement.

[0121] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

[0122] This application provides an electronic device. FIG7 shows a schematic diagram of an electronic device provided by this application. As shown in FIG7, the electronic device 20 includes: a processor 200, a memory 201, a bus 202 and a communication interface 203. The processor 200, the communication interface 203 and the memory 201 are connected through the bus 202. The memory 201 stores a computer program that can run on the processor 200. When the processor 200 runs the computer program, it executes the method provided by any of the foregoing embodiments of this application.

[0123] The memory 201 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 203 (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network.

[0124] Bus 202 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 201 is used to store programs. After receiving an execution instruction, the processor 200 executes the program. The data-driven safety production management method disclosed in any of the foregoing embodiments of this application can be applied to the processor 200, or implemented by the processor 200.

[0125] The processor 200 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 200 or by instructions in software form. The processor 200 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 201. The processor 200 reads the information in memory 201 and, in conjunction with its hardware, completes the steps of the above method.

[0126] The electronic device provided in this application embodiment and the data-driven safety production management method provided in this application embodiment are based on the same application concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0127] This application also provides a computer-readable storage medium corresponding to the data-driven safety production management method provided in the foregoing embodiments. Figure 8 shows a schematic diagram of a storage medium provided in an embodiment of this application. Referring to Figure 8, the computer-readable storage medium shown is an optical disc 30, on which a computer program (i.e., a program product) is stored. When the computer program is run by a processor, it will execute the data-driven safety production management method provided in any of the foregoing embodiments.

[0128] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0129] The computer-readable storage medium provided in the above embodiments of this application and the data-driven safety production management method provided in the embodiments of this application are based on the same application concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0130] Finally, it should be noted that in the foregoing text, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0131] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the data-driven security production management method provided in the embodiments of this application.

[0132] The embodiments of this application have been described above with reference to the accompanying drawings. These are merely specific implementations of this application, but this application is not limited to the specific implementations described above. The specific implementations described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A data-driven safety production management method, wherein, The method comprises: According to the event level of the accident data and the preset index of each event level, the accident safety index achievement result of the enterprise is obtained; The accident distribution information is obtained by analyzing the accident safety index achievement result from at least one preset dimension; Action item tracking information is generated according to the accident distribution information, and the action item tracking information is used to track the processing progress of the accident.

2. The data-driven safety production management method of claim 1, wherein, Before obtaining the accident safety index achievement result of the enterprise, the method further comprises: According to one or more of the accident occurrence subject, the number of injured personnel in the accident, the degree of personnel injury, and the type of accident, the event level of the accident data is determined; According to the number of occurrences of each event level in the historical accident data of the preset period, the preset index of each event level is determined.

3. The data-driven safety production management method according to any one of claims 1 or 2, wherein, The accident distribution information is obtained by analyzing the accident safety index achievement result from at least one preset dimension, comprising: According to the combination condition of the preset dimension and the preset time period, the accident safety index achievement result is analyzed to obtain the accident distribution information; The combination condition of the preset dimension and the preset time period includes at least one of the combination condition of the same preset dimension and different preset time periods, and the combination condition of different preset dimensions and the same time period.

4. The data-driven safety production management method according to any one of claims 1-3, wherein, After obtaining the accident distribution information, the method further comprises: In response to the accident cause query information, the accident occurrence reason is obtained according to the preset accident cause analysis table, and the accident cause analysis table stores the corresponding relationship between the accident and the accident occurrence reason.

5. The data-driven safety production management method according to any one of claims 1-4, wherein, According to the accident distribution information, the action item tracking information is generated, comprising: In the case that the event level of the accident in the accident distribution information is greater than the preset index, an early warning information is sent out; The action item tracking information is generated based on the early warning information.

6. The data-driven safety production management method according to any one of claims 1-5, wherein, The method further comprises: According to the base type of the accident occurrence, the accident data is classified according to the manufacturing base and the non-manufacturing base; The safety performance of each manufacturing base and non-manufacturing base is calculated and ranked respectively to obtain the base safety performance data.

7. The data-driven safety production management method according to any one of claims 1-6, wherein, The safety performance of each manufacturing base and non-manufacturing base is calculated and ranked respectively to obtain the base safety performance data, comprising: According to the preset weight and the occurrence rate of accidents of different event levels in the preset statistical unit, the weighted average of each level event is obtained to obtain the performance score of each base; The performance scores are ranked in size order to obtain the base safety performance data.

8. A data-driven safety production management system, wherein, The system comprises: A safety monitoring module is used to obtain the accident safety index achievement result of the enterprise according to the event level of the accident data and the preset index of each event level; An accident analysis module is used to analyze the accident safety index achievement result from at least one preset dimension to obtain the accident distribution information; An accident tracking module is used to generate action item tracking information according to the accident distribution information, and the action item tracking information is used to track the processing progress of the accident.

9. An electronic device, comprising: The computer program product comprises a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor runs the computer program to implement the data-driven safety production management method according to any one of claims 1-7.

10. A computer readable storage medium having stored thereon a computer program, wherein, The program is executed by the processor to implement the data-driven safety production management method according to any one of claims 1-7.

Images