Lubricator monitoring management platform

Abstract

The invention discloses a lubricator monitoring management platform, and belongs to the technical field of intelligent monitoring of industrial equipment. The platform comprises a data board module, a lubricator management module, a personnel management module and an operation log module. And the data board module is used for intensively displaying the lubricator state, the failure rate, the annual consumption statistics, the alarm information, the state proportion and the multi-dimensional statistical chart. And the lubricator management module is used for configuring and managing equipment parameters and working parameters of the lubricator. And the personnel management module realizes fine-grained data access authority control based on an organization structure and roles. And the operation log module records all user operations for auditing. Through integrated and visual data monitoring and refined authority management, the problems that in the prior art, the data statistics dimension is single, cross-department authority management and control are lacked, and operation traceability is difficult are solved, and the comprehensive management efficiency, data transparency and operation and maintenance safety of lubricating equipment are remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of industrial equipment monitoring and management technology, and in particular to a lubricator monitoring and management platform, especially a software platform for centralized monitoring, configuration, management and data analysis of multiple lubricators (oil injectors, grease injectors). Background Technology

[0002] In modern industrial production, the reliable operation of mechanical equipment (such as bearings, guide rails, and gears) is crucial. Automatic lubricators (including oil lubricators and grease lubricators) are key auxiliary devices that ensure the continuous and stable operation of equipment by supplying lubricating media on a timed and quantitative basis. With the increasing automation and intelligence of factories, the deployment scale of lubricators is expanding, making their effective monitoring and management complex and necessary.

[0003] Currently, there are some monitoring solutions on the market for individual or similar lubricators, typically implemented through handheld devices or simple host computer software. These existing solutions generally suffer from the following shortcomings:

[0004] The existing solutions suffer from limited data statistics and a lack of macro-level analysis and decision support. Most solutions only display basic real-time information such as current oil level, lubrication volume per cycle, and fault alarms. They lack in-depth mining and comprehensive analysis of historical data; for example, they cannot calculate total annual or monthly lubricant consumption, generate time-series distribution charts of lubrication behavior, or compare consumption trends across different equipment or time periods. This makes it difficult for managers to comprehensively assess lubrication costs, predict consumable needs, and optimize lubrication strategies, remaining at a level where they "see faults" but "cannot see trends." Furthermore, existing solutions typically view each piece of equipment in isolation, lacking aggregated analysis and key performance indicator (KPI) metrics at the equipment group, production line, workshop, or even factory level. This fails to provide managers at different levels with decision-making views aligned with their responsibilities. For instance, a factory manager needs to understand the total lubrication cost and reliability of the entire plant, while a workshop supervisor is more concerned with equipment availability and downtime risks within their workshop. Existing technologies struggle to provide this layered, decentralized data perspective.

[0005] The current lubricant management system suffers from a lack of sophisticated access control based on organizational structure. It is typically geared towards equipment maintenance personnel and fails to consider the collaborative management needs of multiple departments and roles within large enterprises. The system lacks effective personnel and access control, meaning all authorized users can typically access data from all equipment across the entire plant. This fails to meet data security and confidentiality requirements (such as data isolation between different production workshops) and cannot accommodate the varying data concerns of different personnel (such as workshop directors, maintenance workers, and equipment procurement staff). Especially in large manufacturing enterprises with complex production processes and clearly defined departmental responsibilities, equipment data often involves sensitive information such as production efficiency and material consumption. The existing "one-size-fits-all" data access model not only poses a risk of data leakage but may also lead to information overload, reducing the work efficiency of personnel in specific positions. Furthermore, the lack of approval or review mechanisms matching the operator's identity and responsibilities for critical operations such as modifying equipment parameters and starting / stopping equipment increases the risk of misoperation or malicious operation.

[0006] Operations lack traceability and auditing capabilities: Existing systems mostly lack detailed records of operations such as lubricator parameter modifications and start-up / shutdown. In the event of misoperation or malicious tampering of equipment parameters, it is difficult to trace the responsible party and the operational process, hindering standardized equipment management and safety auditing. In industries with stringent requirements regarding production safety, quality traceability, or compliance (such as food, pharmaceuticals, and aerospace), any changes to production auxiliary equipment should be documented completely and irrefutably. The current lack of technology makes it impossible to quickly and accurately pinpoint the root cause of lubrication-related equipment failures or product quality deviations, hindering effective responsibility determination and impeding continuous improvement and compliance verification.

[0007] In summary, existing technologies lack a comprehensive lubricator monitoring and management platform that integrates full data monitoring, refined access control, and complete operational auditing, thus failing to meet the demands of modern factories for lean and intelligent equipment management. The functionalities of existing technologies are often fragmented; for example, there may be simple data acquisition tools or independent personnel management systems, but these capabilities are not organically integrated to form a closed-loop management ecosystem centered on lubrication equipment, constrained by organizational permissions, and guaranteed by operation logs. This invention addresses this systemic deficiency. Summary of the Invention

[0008] To address the shortcomings of existing technologies, the purpose of this invention is to provide a lubricator monitoring and management platform. This platform aims to solve the problems of incomplete data statistics, lack of access control, and untraceable operations in existing technologies. Through integrated data dashboards, refined equipment and personnel management, and complete operation logs, it enables comprehensive, efficient, and safe monitoring and management of large-scale deployed lubricators.

[0009] The above-mentioned objective of this invention is achieved through the following technical solutions:

[0010] This invention provides a lubricator monitoring and management platform, comprising: a data dashboard module for centralized monitoring and data visualization of all lubricators connected to the platform; a lubricator management module, communicatively connected to the data dashboard module, for configuring and managing the equipment parameters and operating parameters of each lubricator; a personnel management module, communicatively connected to both the data dashboard module and the lubricator management module, for managing user information, organizational structure, user roles, and data access permissions based on roles and organizational structure; and an operation log module, communicatively connected to the data dashboard module, the lubricator management module, and the personnel management module, for recording and storing the operation behavior logs of all users within the platform.

[0011] The core of this invention lies in the deep integration and collaborative work of four modules, forming a complete closed loop of "monitoring-management-control-audit". The data dashboard module is the "window" for information presentation, its content and scope constrained by the real-time and dynamic constraints of the personnel management module; the lubricant management module is the "means" for execution control, its executable operations also subject to user permissions, and every critical operation is captured indiscriminately by the operation log module; the personnel management module is the "rule engine" for security and order, defining who can see what and who can do what, mapping the organizational structure—a real-world management model—to the digital space; and the operation log module is the "black box" for traceability and accountability, ensuring that all actions within the rules (or attempts to break the rules) are recorded. This tight coupling between modules and the organic interaction of data and control flows transcends the simple functional superposition of existing technologies, constituting a novel system architecture with inherent logical unity and management depth.

[0012] According to one embodiment of the present invention, the data dashboard module specifically includes: a status and overview unit, used to display the total number of lubricators, the number of online lubricators, the number of abnormal lubricators, the number of lubricators shut down, and the number of lubricators offline in real time, and to display the overall status distribution of lubricators in the form of a percentage chart; a fault statistics unit, used to count and display the lubrication failure rate within a specified time period; a consumption statistics unit, used to count and display the total consumption of lubricating oil or grease within an annual, monthly, or custom period; an early warning unit, used to monitor and display the alarm status of lubricators in real time, the alarm status including at least one of insufficient grease, insufficient power, and communication failure; a time distribution unit, used to generate and display the execution time distribution chart of lubrication events; and a replacement prediction unit, based on consumption data and equipment configuration, to predict the number of lubricators that need grease replacement within the next week or a specified period.

[0013] Furthermore, the data dashboard module features drill-down functionality. For example, by clicking the "Abnormal" section in the overall factory-level status overview, a user can drill down to a workshop-level view displaying a list of all abnormal equipment. Clicking on a specific workshop allows further drilling down to a view of the specific production line or equipment group within that workshop. This design enables data analysis to provide both a comprehensive overview and in-depth detail, meeting the needs of different management levels. Simultaneously, all view levels are subject to real-time filtering by data scope rules in the personnel management module, ensuring that users can only drill down within their authorized scope.

[0014] According to one embodiment of the present invention, the lubricator management module specifically includes: a device configuration unit, used to input and edit the static attribute information of the lubricator, the static attribute information including device name, installation location, lubricator model, lubricator number, lubrication application scenario, oil bottle number, battery model, and grease model; a parameter setting unit, used to set the dynamic operating parameters of the lubricator, the dynamic operating parameters including full oil drain time, lubrication cycle, single lubrication volume, and lubrication switch status; and a device status synchronization unit, used to receive and update real-time operating status data from the physical lubricator.

[0015] Furthermore, the lubricator management module supports the "equipment template" function. For a large number of lubricators with identical or similar configurations, the administrator can create an equipment template, predefining its static attributes and dynamic operating parameters. When adding new equipment in batches, simply select the template and specify a few differences (such as installation location and number) to quickly complete the configuration, greatly improving the efficiency of large-scale equipment entry and ensuring configuration standardization. In addition, the parameter setting unit supports the "batch parameter distribution" function, allowing users to filter a group of equipment (such as equipment on the same production line using the same type of grease) and distribute the modified operating parameters to all selected equipment at once, achieving efficient group management.

[0016] According to one embodiment of the present invention, the personnel management module specifically includes: an organizational structure management unit for creating and maintaining the company's multi-level departmental structure; a user account management unit for managing user account information and associating users with corresponding departments; a role and permission definition unit for defining different roles and assigning operation permissions and data viewing scope rules to each role; a permission verification and filtering unit for dynamically filtering the data content presented in the data dashboard module and the lubricant management module according to the user's department and role when the user accesses data; and a notification configuration unit for configuring the alarm notification receiving method and frequency for users or roles.

[0017] Furthermore, the personnel management module implements a flexible mapping of "position-role-permission". A role can be assigned to multiple users, and a user can hold multiple roles (e.g., someone is both a "workshop supervisor" and a "maintenance team member"). The final permission is the union of the permissions for each role. Data viewing scope rules support more complex logic, such as: "View data from this department and related departments upstream and downstream of the process," which is very useful in process-oriented production. The permission verification and filtering unit not only filters data during interface presentation but also intercepts data at the data interface layer and database query layer, ensuring end-to-end security from the data source to the final display and preventing unauthorized data access through abnormal interface channels.

[0018] According to one embodiment of the present invention, the data viewing scope rules include: viewing only the data of the department to which the data belongs, viewing the data of a specified related department, or viewing the data of the entire platform; the operation permissions include the configuration, modification, start / stop operation permissions of the lubricator management module, and the export and filtering permissions of the data dashboard module.

[0019] According to one embodiment of the present invention, the operation log module specifically includes: a log recording unit for capturing and recording user operation behavior, wherein the operation behavior includes at least operation time, operation user identifier, operation module, operation type, operation object identifier, pre-operation parameters, post-operation parameters, and IP address or geographical location information of the operation terminal; a log storage and indexing unit for storing the operation log in a structured manner and establishing an index; and a log query and analysis unit for providing a multi-dimensional combined query interface based on time, user, operation type, and device identifier, and supporting source tracing analysis of operation behavior.

[0020] Crucially, the operation log module's recording is "non-bypassable." The logging unit is deeply embedded into the core operation processes of each business module through underlying framework hooks or Aspect-Oriented Programming (AOP) technology. Regardless of whether the operation is initiated through a graphical interface, API interface, or any other authorized channel, as long as a platform-defined key business action is triggered (such as modifying parameters, starting or stopping devices, or changing permissions), the logging unit will automatically and forcibly execute recording, ensuring the integrity and reliability of the audit trail. The log storage and indexing unit adopts a write-first (WAL) or similar mechanism to ensure that log recording is persisted before business operations, preventing log loss due to system failures.

[0021] According to one embodiment of the present invention, the platform further includes a data interface module for interacting with physical lubricators distributed in the field via wired or wireless communication protocols, or for integrating data with an upper-level enterprise resource planning system.

[0022] The data interface module possesses protocol adaptation and data cleansing capabilities. For different types and manufacturers of physical lubricators, this module has built-in or configurable parsers for various industrial communication protocols (such as Modbus RTU / TCP, OPC UA, MQTT, PROFINET, etc.), uniformly converting heterogeneous raw data into a standard data model within the platform. Simultaneously, the module includes data cleansing logic, which can filter abnormal signal jumps, supplement short-term missing data, and preliminarily determine the validity of the data, providing a high-quality data source for upper-layer applications. When integrating with upper-layer systems (such as ERP, MES), the data interface module provides standard RESTful APIs or Web Services and supports bidirectional data synchronization. For example, it can push the platform's predicted consumable demand to the ERP system to generate purchase requests, or receive production plans from the MES system to dynamically adjust lubrication strategies.

[0023] According to one embodiment of the present invention, the lubrication time distribution chart displayed by the data dashboard module is specifically a bar chart or heat map showing the number or frequency of lubrication events occurring in different time periods within a 24-hour day.

[0024] According to one embodiment of the present invention, the consumption statistics unit is further configured to generate a monthly grease consumption statistics comparison chart to compare the consumption differences between different months or different lubricator groups.

[0025] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the functions of any module in the above-described embodiments. The present invention also provides a lubricator monitoring and management platform.

[0026] In summary, compared with the prior art, the present invention has at least one of the following beneficial technical effects:

[0027] It improves the overall efficiency and decision-making level of equipment management: Through the multi-dimensional and visualized statistics provided by the data dashboard module (such as annual consumption statistics, time distribution charts, and monthly comparison charts), managers can clearly grasp the overall operating status, consumption patterns, and cost composition of the entire plant's lubrication equipment. It upgrades from "passive alarm response" to "proactive trend analysis and prediction," enabling data-driven optimization of lubrication strategies, precise procurement of consumables, and preventative maintenance arrangements, achieving a leap from experience-based management to data-driven management.

[0028] It achieves refined and secure access control: through the personnel management module, the enterprise's organizational structure, user roles, and data and functional permissions are tightly bound together. This ensures that employees in different departments and positions can only access and operate devices and data within their scope of responsibility. This not only protects the security of the enterprise's core production data and prevents information leakage and unauthorized operations, but also enables the platform to adapt to collaborative workflows under large and complex organizational structures, with clear responsibilities and rights.

[0029] The system enhances operational standardization and traceability: the operation log module comprehensively records all critical operations within the platform, forming an auditable and traceable operational chain. In the event of equipment malfunction, parameter errors, or safety incidents, the operator, operation time, and specific operation details can be quickly and accurately located. This significantly strengthens employees' awareness of standardized operations and their sense of responsibility, and provides irrefutable evidence for subsequent problem analysis, accountability, and process improvement, thereby enhancing the overall standardization and security of operations and maintenance management.

[0030] The invention enhances the platform's practicality and scalability by integrating monitoring, configuration, management, and auditing functions into a complete and highly practical solution. Its modular design facilitates platform expansion; for example, it allows for easy addition of new data analysis models, connection to more types of lubrication equipment, or deep integration with other factory management systems, demonstrating promising application prospects and significant potential for widespread adoption.

[0031] Furthermore, through the synergy of its various modules, this invention produces a combined beneficial effect of "1+1>2":

[0032] The combination of data-driven approaches and access control: Fine-grained access control ensures that data analysis and decision support are conducted in a controlled and secure environment. Managers at different levels see filtered data views that match their responsibilities, making the data-driven decision-making process more focused and efficient, and avoiding information noise interference.

[0033] The platform achieves a balance between operational flexibility and rigorous auditing: while granting authorized users flexible equipment management capabilities (such as remote parameter modification), the operation log module ensures that every instance of this flexibility is fully recorded. This "open yet controlled" model encourages efficient remote operation and maintenance while establishing a solid risk control baseline, aligning with the modern industrial management philosophy of pursuing both efficiency and safety.

[0034] Balancing standardized management with personalized adaptation: Features such as equipment templates and batch operations promote the standardization of lubrication equipment management. Meanwhile, the permission system based on organizational structure allows for flexible adaptation to the personalized management needs of different enterprises and departments. The platform becomes a configurable management framework, rather than a rigid software product.

[0035] Reduced Total Cost of Ownership (TCO): Through preventative maintenance prediction, precise consumable management, reduced unplanned downtime, and improved maintenance personnel efficiency, this invention platform can significantly reduce the management cost of lubrication equipment throughout its entire lifecycle and improve return on investment. Attached Figure Description

[0036] Figure 1 This is a system architecture diagram of the present invention. Detailed Implementation

[0037] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0038] In the description of this application, it should be noted that the terms "upper," "lower," "inner," "outer," "top / bottom," etc., indicating the orientation or positional relationship are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0039] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installed," "equipped with," "sleeved / connected," "connected," etc., should be interpreted broadly. For example, "connection" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be a connection within two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0040] The purpose of this invention is to overcome the shortcomings of existing technologies and provide a lubricator monitoring and management platform. This platform aims to solve the problems of incomplete data statistics, lack of access control, and untraceable operations in existing technologies. Through integrated data dashboards, refined equipment and personnel management, and comprehensive operation logs, it achieves comprehensive, efficient, and safe monitoring and management of large-scale deployed lubricators.

[0041] To achieve the above-mentioned objectives, refer to Figure 1The present invention adopts the following technical solution: a lubricator monitoring and management platform, including a data dashboard module, a lubricator management module, a personnel management module and an operation log module.

[0042] The data dashboard module, as the core display interface of the platform, is used for centralized monitoring and multi-dimensional data visualization of all lubricants configured and connected to the platform. It is more than just a simple list of information; it provides managers with an intuitive overall situational awareness and in-depth data insights through charts and dashboards.

[0043] The lubricator management module, communicating with the data dashboard module, is responsible for the mapping and management of lubricator entities in the digital space. It is used to configure detailed parameters for each lubricator, including its static attributes (such as identification information and installation information) and dynamic operating parameters (such as lubrication strategies). This module is the foundation for the platform's control and management of physical equipment.

[0044] The personnel management module communicates with the data dashboard module and the lubricator management module, respectively, and introduces an "organization-role-permission" model. It manages platform users, builds enterprise departmental structures, defines different roles (such as administrators, workshop supervisors, and maintenance personnel), and dynamically controls the range of data a user can see (data permissions) and the operations they can perform (functional permissions) in different modules based on their department and role. This ensures secure data isolation and a clear division of responsibilities.

[0045] The operation log module connects to all other core modules of the platform, acting as the platform's "black box." It automatically and completely records and stores all user actions within the platform, forming an immutable audit trail. This provides a reliable basis for fault tracing, liability determination, and operational compliance checks.

[0046] Furthermore, the data dashboard module may specifically include multiple functional units:

[0047] Status and Overview Unit: Displays the macro status of lubricants within the platform in numerical and graphical ways (such as pie charts and cards), including the total number, number of online / offline, number and percentage of normal / abnormal / off states.

[0048] Fault statistics unit: Calculates and displays the lubrication failure rate for a specific time period (such as today, this week, this month) to help assess equipment reliability.

[0049] Consumption statistics unit: aggregates and statistically analyzes the consumption of lubricating oil / grease, supports viewing the total consumption by year, month or custom period, and generates trend charts or comparison charts (such as monthly consumption statistics charts).

[0050] Warning Unit: Centrally displays a list of all lubricators currently in an alarm state and alarm details (such as insufficient grease, low battery, communication interruption), supports color coding (such as red highlighting) and sound prompts.

[0051] Time distribution unit: Analyze historical lubrication event data to generate lubrication time distribution maps (e.g., 24-hour heatmaps), revealing the temporal patterns of lubrication behavior, which helps to identify abnormal lubrication patterns or optimize lubrication plans.

[0052] Replacement prediction unit: Based on the current grease level, historical consumption rate, and configured full grease drain time, the algorithm predicts the list and quantity of lubricators that may need to be replenished or replaced within a specified period in the future (such as the next week), assisting in preventive maintenance.

[0053] Furthermore, the replacement prediction unit employs a weighted moving average model. This model considers not only the equipment's historical consumption rate but also incorporates equipment operating condition coefficients (such as the operating load rate of the equipment, which can be obtained from the MES system) and environmental coefficients (such as the impact of seasonal temperature changes on grease viscosity) as weighting factors. The prediction formula can be simplified to: Predicted remaining days = (Current remaining percentage * Theoretical full oil emptying time) / (Historical average daily consumption rate * Operating condition coefficient * Environmental coefficient). When the predicted remaining days are less than a set warning threshold (such as 7 days), the equipment is included in the replacement prediction list. This algorithm is closer to reality and has higher accuracy than simple linear prediction.

[0054] Furthermore, the lubricator management module may specifically include:

[0055] Equipment configuration unit: Provides a form interface for entering or editing the static attributes of the lubricator, such as: equipment name, precise installation location (which can be linked to the factory map), lubricator model, unique number, application scenario (e.g., "XX production line main shaft bearing"), currently used oil bottle / grease tank number, battery model, grease type, etc. This information constitutes the equipment's "digital profile".

[0056] Parameter setting unit: Provides a setting interface for adjusting the lubricator's operating parameters, which is crucial for the platform's remote control of the equipment. Parameters include: the emptying time under theoretical full oil conditions (used for calculating consumption and prediction), lubrication interval cycle, oil / grease supply per operation, and the "lubrication switch" for remote start / stop. Once set, these parameters can be sent to the physical equipment.

[0057] Equipment Status Synchronization Unit: Responsible for communicating with the physical lubricator (usually through an IoT gateway), periodically acquiring or receiving real-time equipment operating status data (such as current oil level, battery voltage, signal strength, last lubrication time, etc.), and updating it to the platform database for display by the data dashboard module.

[0058] Furthermore, when a user modifies key parameters (such as significantly shortening the lubrication cycle or significantly increasing the amount of grease injected in a single operation), the parameter setting unit can trigger a "secondary confirmation" or "approval process" mechanism. For ordinary maintenance workers, such modifications may require electronic approval from their superiors (such as the maintenance foreman) on the platform before taking effect. The approval process is also recorded by the operation log module. This increases the control level for high-risk operations, further ensuring the safe operation of the equipment.

[0059] Furthermore, the personnel management module may specifically include:

[0060] Organizational structure management unit: Allows administrators to create and maintain company departmental levels in a tree structure, such as "Company -> Production Department -> Workshop 1 -> Maintenance Team".

[0061] User Account Management Unit: Manages users' basic information (name, employee ID, etc.) and assigns each user to one or more departments.

[0062] Role-based permission definition unit: Predefined or custom roles (such as "System Administrator", "Equipment Administrator", "Workshop Viewer", "Maintenance Technician"), and each role is assigned two types of permissions: a) Functional permissions: such as whether the role can add equipment, modify parameters, start and stop equipment, export reports, etc.; b) Data scope permissions: defining which departments' data the role can view. Rules can be "only this department", "this department and its subordinate departments", "specified cross-department", or "all".

[0063] Access Control and Filtering Unit: This unit runs in the background when a user accesses any data page after logging in. It generates a data filter based on the data scope rules of the user's department and role. When querying the database for lubricator lists or statistics, this condition is automatically applied, thus returning only the data that the user is authorized to view. For example, a maintenance worker in Workshop 1 can only see lubricators assigned to Workshop 1 on the data dashboard.

[0064] Notification Configuration Unit: Allows users or administrators to configure the method (such as platform in-site messages, email, SMS) and frequency (such as real-time, daily summary) for receiving alarm notifications for specific roles or users.

[0065] Furthermore, the permission verification and filtering unit is implemented using a "row-level security" strategy. At the database level, this is achieved through views, row-level security policies (such as PostgreSQL's RLS), or by dynamically adding query conditions in an application-layer persistence framework (such as Hibernate's Filter). For example, a database view created for the "repairman" role might contain a WHERE clause like: WHERE department_id IN (SELECT accessible_dept_id FROM user_permission_view WHERE user_id=CURRENT_USER_ID). This approach ensures isolation from the data source, providing the highest level of security while remaining transparent to upper-layer business logic.

[0066] Furthermore, the operation log module may specifically include:

[0067] Log recording unit: Deeply integrated into the operational workflow of various business modules. Whenever a user performs a critical operation (such as logging in, modifying device parameters, starting or stopping a device, exporting data, or modifying user permissions), this unit automatically captures the operation context and generates a log record. The record content includes at least: timestamp, user ID, user name, module of operation (e.g., "Lubricator Management"), operation type (e.g., "Modify Parameters"), operation object (e.g., device number "Lub-001"), parameter values ​​before the operation, parameter values ​​after the operation, and the IP address of the terminal initiating the operation. For sensitive operations, more detailed information can be recorded.

[0068] Log storage and indexing unit: Persistently stores structured log data in a database or dedicated log file, and builds efficient indexes (such as indexes by time, user ID, and device number) to support fast retrieval.

[0069] Log Query and Analysis Unit: Provides a dedicated query interface. Administrators can combine multiple conditions (such as time period, user, operation type, and device) for precise queries. Query results are displayed in list format and can be exported. This can be used to audit the parameter change history of a device, track all operations of a specific user, or reconstruct the operation sequence in the event of a failure.

[0070] Furthermore, the operation log module supports an "operation replay" simulation function. In the log query results, for operations such as modifying device parameters, the administrator can select a record and initiate "simulation replay." The system will read the "parameters before operation" from that log record and display the device's historical state at the moment before the operation in a sandbox environment or read-only interface; then, it will apply the "parameters after operation" to display the changed state. This visual replay function allows auditors to intuitively understand the specific impact of each operation, greatly improving the efficiency of problem diagnosis and root cause analysis.

[0071] Preferably, the platform may also include a data interface module. This module serves as a bridge for communication between the platform and external systems. On the one hand, it uses industrial communication protocols such as Modbus, OPC UA, MQTT, and 4G / 5G to collect data and issue commands to lubricators or their gateways in the field. On the other hand, it provides standard APIs (such as RESTful APIs) for integration with existing ERP (Enterprise Resource Planning), EAM (Enterprise Asset Management System), or MES (Manufacturing Execution System) systems to achieve data sharing and business process integration.

[0072] Example 1

[0073] refer to Figure 1 This embodiment provides a lubricator monitoring and management platform. The platform can be deployed using a B / S (Browser / Server) architecture or a C / S (Client / Server) architecture. The platform mainly includes four core functional modules: a data dashboard module, a lubricator management module, a personnel management module, and an operation log module. In addition, the platform typically includes a data interface module, a database, and an application server running these modules.

[0074] Data Interface Module: Responsible for exchanging data with external entities. On one hand, it collects real-time data (such as oil level, battery voltage, and operating status) from multiple physical lubricators deployed in the factory site via an Industrial Internet of Things (IIoT) gateway or direct connection, using the MQTT protocol. On the other hand, it can send control commands to the lubricators (such as modifying lubrication parameters). The data interface module can also provide a Web Service or REST API for enterprise ERP systems to call, synchronizing equipment ledgers or consumption data.

[0075] Database: Used for persistent storage of all data, including: lubricator equipment file data, real-time and historical operating data, user and permission data, operation log data, statistical results data, etc.

[0076] Application server: Runs the platform's core business logic, processes user requests, and generates dynamic pages and data.

[0077] Users access the platform through a browser or dedicated client on a terminal device (such as a computer or tablet).

[0078] The data dashboard module is the default homepage after a user logs in. Its interface is designed as a comprehensive dashboard containing multiple information windows (widgets):

[0079] Window 1: Displays key performance indicators (KPI) cards, such as "Total number of lubricators: 150", "Online: 142", "Abnormal: 5", "Offline: 3".

[0080] Window 2: Displays the lubricator status percentages in a pie chart, such as "Normal: 90%", "Abnormal: 3.3%", "Off: 4%", and "Offline: 2.7%".

[0081] Window 3: Displays "This week's failure rate: 1.2%" and its trend line graph.

[0082] Window 4: Displays "Annual cumulative fat loss: 1250kg" and a monthly bar chart comparing fat loss, clearly showing which month burned the most fat.

[0083] Window 5: Lists all current alarms, such as "Device Lub-023: Insufficient grease (15% remaining)" and "Device Lub-087: Low battery".

[0084] Window 6: Displays "Equipment to be replaced in the next week: 8 units" and provides a list.

[0085] Window 7: Displays a lubrication time distribution chart. This is a 24-hour heat map, with the horizontal axis representing 0-23 hours and the vertical axis representing equipment groups or areas. The shade of color indicates the number of devices requiring lubrication during that time period. The chart clearly shows that lubrication activity is mainly concentrated during the day shift from 9-11 AM and 2-4 PM (darkest color), while there is virtually no lubrication activity during the night shift, consistent with production patterns.

[0086] The lubricator management module provides the ability to manage individual lubricators in a granular manner, and its interface may be divided into two columns or in tab format.

[0087] The left column or the first tab is a list of devices, displaying all lubricators that users have permission to view, and supports filtering by status and location.

[0088] When a user clicks on a device in the list (such as Lub-001), the detailed management interface for that device is displayed in the right column or the second tab. This interface is further divided into two sub-sections:

[0089] Device Configuration Area: Displays and allows editing of the device's static attribute forms, such as:

[0090] Equipment Name: Lubrication Point A of Main Spindle on Line 1;

[0091] Installation location: Production Department 1 / Workshop 1 / Production Line 1 / Spindle position;

[0092] Lubricator model: AutoLub X200;

[0093] Lubricator part number: Lub-001 (unique);

[0094] Lubrication application: Spindle bearing lubrication;

[0095] Oil bottle number: Cartridge-2024-05-001;

[0096] Battery model: Lithium battery pack ER34615;

[0097] Grease type: Extreme pressure lithium-based grease LGEP2;

[0098] Parameter setting area: Displays and allows adjustment of the device's operating parameters, such as:

[0099] Full oil draining time: 180 days (based on grease type and equipment operating conditions);

[0100] Lubrication cycle: every 4 hours;

[0101] Single injection volume: 0.1cm 3 ;

[0102] Lubrication switch: Enable, Enable / Disable, Disable, Radio button;

[0103] After the user modifies the parameters, clicking the "Save and Send" button will send the new parameters to the physical device Lub-001 through the data interface module.

[0104] The personnel management module is responsible for the platform's account and permission system. Its interface typically includes an organizational structure tree, a user list, and a role and permission configuration panel.

[0105] The organizational structure tree displays company departments in a collapsible tree diagram. For example, under the "root company" are "Production Department", "Equipment Department", and "Quality Assurance Department". Under "Production Department" are "Workshop 1" and "Workshop 2".

[0106] The user list displays all registered users. Clicking on a user (such as "Zhang San") allows you to view and edit their basic information, and then drag and drop them onto the "Workshop 1" node in the organizational structure tree to complete the department affiliation setting.

[0107] The role and permission configuration panel is used to define and modify roles. Administrators can create a new role, such as "Workshop Maintenance Foreman". Permission configuration is divided into two parts:

[0108] Functional permissions: Select the allowed operations for this role, such as "View data dashboard", "Export department reports", "Modify department equipment parameters", and "Start / Stop department equipment". Do not select high-risk permissions such as "Delete device" and "Manage users".

[0109] Data range rule: Select "View data for this department and its subordinate departments". This means that users assigned this role can only see all lubricator data for their own department (e.g., Zhang San in Workshop 1) and all lubricator data for the subordinate work groups (if any) of Workshop 1, and cannot see the data for Workshop 2.

[0110] After setting the user "Zhang San" to the role of "Workshop Maintenance Foreman", his permissions took effect immediately. When he logs into the platform, the data presented to him by the data dashboard module and the lubricator management module has already been automatically filtered by the permission verification and filtering unit.

[0111] The operation log module provides powerful auditing capabilities, and its interface offers a multi-condition query form and a log display list.

[0112] The query form allows administrators to set query criteria, such as:

[0113] Time range: 00:00 on May 10, 2024 to 23:59 on May 12, 2024;

[0114] User: Zhang San;

[0115] Operation module: Lubricator management;

[0116] Operation object (device number): Lub-001;

[0117] Clicking the "Search" button will display a list of all log records that match your criteria. Each record contains detailed fields, such as:

[0118] Operation time: 2024-05-11 14:25:36;

[0119] User: Zhang San;

[0120] Operation module: Lubricator management;

[0121] Operation type: Modify parameters;

[0122] Target of operation: Lub-001;

[0123] Operation details: Change "Lubrication cycle" from "every 6 hours" to "every 4 hours"; change "Single grease injection volume" from "0.08cm³" to "0.1cm³". 3 ".

[0124] Operating terminal IP: 192.168.1.105;

[0125] By analyzing these logs, the entire process of parameter changes for device Lub-001 on the afternoon of May 11 can be clearly reconstructed.

[0126] Example 2

[0127] Building upon Example 1, this example further emphasizes the platform's prediction and integration capabilities.

[0128] The logic for changing the predictive unit can be made more intelligent. It not only relies on a fixed "full oil evacuation time" but also incorporates the equipment's average daily consumption rate over the past 30 days and considers seasonal variations in its workload (if the platform integrates production data such as spindle speed). The predictive algorithm can provide a confidence interval, such as "there is a 90% probability that Lub-045 grease needs to be replaced within the next 7 days." The prediction results can directly generate a draft purchase requisition, which is then pushed to the ERP system's purchasing module via the data interface module, achieving an automated chain from prediction to execution.

[0129] The data interface module is integrated with the MES system. When the MES system issues a work order for "Stop maintenance of Production Line 1," the platform receives this information through the interface. Subsequently, the lubricator management module can automatically and in batches set the "lubrication switch" of all lubricators belonging to Production Line 1 to "disable," avoiding ineffective lubrication during downtime. After maintenance is completed and the MES sends a "Resume Production" signal, the platform automatically enables these lubricators. This integration automates cross-system workflows.

[0130] This embodiment also demonstrates the deep integration of the personnel management module and alarm notification. For example, alarm notification rules can be configured for the role of "Workshop 1 Maintenance Team": for "insufficient grease" alarms, a real-time SMS message is sent to all team members; for "insufficient power" alarms, a summary email is sent to the team leader at 5 PM every day. When a lubricator belonging to Workshop 1 experiences an "insufficient grease" alarm, the early warning unit triggers the alarm, notifying the configuration unit to immediately call the SMS gateway to send alarm SMS messages to the mobile phones of maintenance team members such as Zhang San and Li Si, according to the rules. The messages include the equipment number, location, and alarm details, ensuring a rapid response to emergency information.

[0131] Example 3

[0132] This embodiment describes one possible software implementation. The platform can be developed using a Java-based Spring Boot microservice architecture or a Python-based Django framework. The front-end uses modern frameworks such as Vue.js or React to build a responsive user interface.

[0133] Charts in the data dashboard module can be rendered using the ECharts or D3.js libraries.

[0134] Access filtering in the personnel management module can be achieved by dynamically concatenating WHERE conditions at the database query level (such as WHERE department_id IN (a list of department IDs that the user has permission to view)). This is an efficient data filtering method.

[0135] The operation logging module can utilize Spring AOP (Aspect-Oriented Programming) or Django's middleware mechanism to automatically capture log information before and after the execution of business methods in a non-intrusive manner, ensuring the comprehensiveness and consistency of log recording.

[0136] Furthermore, to handle the monitoring of massive amounts of equipment data, the platform can employ distributed time-series databases (such as InfluxDB and TimescaleDB) to store real-time status data and historical time-series data (such as oil level changes and battery voltage). These databases are optimized for timestamp indexing and high-throughput writes. For relational data such as equipment files, user information, and operation logs, traditional relational databases (such as MySQL and PostgreSQL) are used. This hybrid data storage architecture balances efficient processing of time-series data with the relational integrity of transactional data.

[0137] The platform's security is ensured through multiple mechanisms: 1) Communication security: Communication between the data interface module and field devices and external systems uses TLS / SSL encryption. 2) Authentication and session management: Strong password policies and multi-factor authentication (such as SMS verification codes) are used, and session timeouts are managed. 3) Access control: As mentioned above, strict access control is implemented through the personnel management module. 4) Input validation: All user input and interface parameters are strictly validated and filtered to prevent attacks such as SQL injection and cross-site scripting. 5) Log auditing: The operation log module provides the last line of defense.

[0138] Example 4

[0139] This embodiment uses an automobile manufacturing plant painting workshop as an example to illustrate the specific application and value of the present invention.

[0140] Scenario: This painting workshop has over 300 automatic lubricators used in critical equipment such as conveyor chains, elevators, and fan bearings. In the past, lubrication management relied on regular manual inspections and paper records, resulting in slow fault response and inefficient consumable management.

[0141] After implementing the platform of this invention:

[0142] Data Dashboard: Every day, the workshop director opens the platform homepage first thing when he arrives at work. He sees the KPI display: 298 online devices, 2 with communication failures (already dispatched), and 5 abnormal alarms (3 with insufficient grease, 2 with low battery). The monthly consumption comparison chart shows that this month's lubricating grease consumption increased by 15% compared to last month. He clicks drill down and finds that the main increase comes from the equipment in the "pre-treatment conveyor chain" area.

[0143] Lubricator Management: Maintenance worker Wang Wu received a "low grease" text message alarm for equipment "Lub-152". He logged into the platform on his tablet and quickly located Lub-152 through the lubricator management module. He found its installation location to be "Pre-treatment Line - Inlet Lift - Drive Side Bearing", and the grease type was "High-Temperature Silicone Grease". He took the correct grease to the site for replacement. After replacement, he updated the equipment's "Oil Bottle Number" to the new number on the platform, and the system automatically reset the oil level calculation baseline.

[0144] Personnel Management: Platform access permissions are set as follows: Workshop directors can view all workshop data and export reports; section chiefs can only view and manage the equipment in their respective sections; maintenance workers can only view and handle the alarm equipment assigned to them and have the right to modify the parameters of the equipment they are responsible for (but major modifications require section chief approval). Equipment department engineers have full platform viewing permissions but do not have the right to operate the equipment in the production workshop.

[0145] Operation Log and Audit: One month later, the "Lub-200" equipment (responsible for lubricating the guide rails of the painting robot) experienced poor lubrication, leading to wear on the guide rails. A review of all historical operations of the Lub-200 through the operation log module revealed that two weeks prior, maintenance worker Zhao Liu had changed its "lubrication cycle" from "2 hours" to "8 hours," citing an attempt to "reduce consumption." However, this modification was made without approval (Zhao Liu's authority should not have allowed him to make such a significant change directly). The log clearly recorded the operator, time, and content of the modification. Based on this, the cause of the incident was identified, and authorization rules and operational training were strengthened accordingly.

[0146] Integration and Forecasting: The platform integrates with the factory's MES and ERP systems. Based on changes in production plans (such as changes in cycle time due to vehicle model switching), the platform can automatically fine-tune the lubrication cycles of relevant lubricants. The replacement forecasting unit generates a consumables demand forecast list for the following week every weekend and automatically submits it to the ERP system, allowing the warehouse to prepare inventory in advance and avoiding downtime due to material shortages.

[0147] As can be seen from this embodiment, the platform of the present invention not only provides tools, but also constructs a new lubrication management system covering "data perception, intelligent analysis, precise execution, permission constraints, and full traceability", transforming the traditional discrete, passive, and experience-based lubrication work into a centralized, proactive, data-driven, and process-oriented modern asset management practice.

[0148] The implementation principle of this invention is as follows: This invention discloses a lubricator monitoring and management platform, belonging to the field of intelligent monitoring technology for industrial equipment. The platform includes a data dashboard module, a lubricator management module, a personnel management module, and an operation log module. The data dashboard module is used to centrally display lubricator status, failure rate, annual consumption statistics, alarm information, status percentage, and multi-dimensional statistical charts. The lubricator management module is used to configure and manage the equipment parameters and operating parameters of the lubricator. The personnel management module implements fine-grained data access permission control based on organizational structure and roles. The operation log module records all user operations for auditing purposes. This invention, through integrated and visualized data monitoring and refined permission management, solves the problems of single data statistical dimensions, lack of cross-departmental permission control, and difficulty in operation traceability in existing technologies, significantly improving the overall management efficiency, data transparency, and operational security of lubrication equipment.

[0149] The above are merely preferred embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention. For example, replacing the lubricator with other types of periodic feeding equipment monitoring; or extending the permission model to a more complex attribute-based access control (ABAC); or using machine learning algorithms to analyze historical fault logs to achieve fault root cause prediction, etc., these variations and improvements based on the core concept of the present invention all fall within the scope of protection of the present invention.

[0150] The embodiments described herein are preferred embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Therefore, all equivalent changes made in accordance with the structure, shape, and principle of the present invention should be covered within the scope of protection of the present invention.

Claims

1. A lubricator monitoring and management platform, characterized in that, include: The data dashboard module is used for centralized monitoring and data visualization of all lubricators connected to the platform; The lubricator management module is communicatively connected to the data dashboard module and is used to configure and manage the equipment parameters and operating parameters of each lubricator. The personnel management module is communicatively connected to the data dashboard module and the lubricator management module, and is used to manage user information, organizational structure, user roles, and data access permissions based on roles and organizational structure. The operation log module is communicatively connected to the data dashboard module, lubricator management module, and personnel management module, and is used to record and store the operation behavior logs of all users within the platform.

2. The lubricator monitoring and management platform according to claim 1, characterized in that, The data dashboard module specifically includes: The status and overview unit is used to display the total number of lubricators, the number of online lubricators, the number of abnormal lubricators, the number of lubricators that are shut down, and the number of lubricators that are offline in real time, and to show the overall status distribution of lubricators in the form of a percentage chart; The fault statistics unit is used to statistically analyze and display the lubrication failure rate within a specified time period. The consumption statistics unit is used to calculate and display the total consumption of lubricating oil or grease within an annual, monthly, or custom period. The early warning unit is used to monitor and display the alarm status of the lubricator in real time, and the alarm status includes at least one of insufficient grease, insufficient power, and communication failure. The time distribution unit is used to generate and display the execution time distribution map of the lubrication event; The replacement prediction unit, based on consumption data and equipment configuration, predicts the number of lubricators that will require grease replacement within the next week or a specified period.

3. The lubricator monitoring and management platform according to claim 1, characterized in that, The lubricator management module specifically includes: The equipment configuration unit is used to input and edit the static attribute information of the lubricator, which includes equipment name, installation location, lubricator model, lubricator number, lubrication application scenario, oil bottle number, battery model, and grease model. The parameter setting unit is used to set the dynamic operating parameters of the lubricator, including full oil evacuation time, lubrication cycle, single lubrication amount, and lubrication switch status. The equipment status synchronization unit is used to receive and update real-time operating status data from the physical lubricator.

4. The lubricator monitoring and management platform according to claim 1, characterized in that, The personnel management module specifically includes: Organizational structure management unit, used to create and maintain the company's multi-level departmental structure; The user account management unit is used to manage user account information and associate users with corresponding departments; The role permission definition unit is used to define different roles and assign operation permissions and data viewing scope rules to each role; The permission verification and filtering unit dynamically filters the data content presented in the data dashboard module and the lubricant management module based on the user's department and role when the user accesses data. The notification configuration unit is used to configure the receiving method and frequency of alarm notifications for users or roles.

5. A lubricator monitoring and management platform according to claim 4, characterized in that, The data viewing scope rules include: viewing only the data of the department to which the data belongs, viewing data of a specified related department, or viewing data of the entire platform; the operation permissions include the configuration, modification, start and stop operation permissions of the lubricator management module, as well as the export and filtering permissions of the data dashboard module.

6. The lubricator monitoring and management platform according to claim 1, characterized in that, The operation log module specifically includes: The log recording unit is used to capture and record the user's operation behavior, which includes at least the operation time, operation user ID, operation module, operation type, operation object ID, parameters before operation, parameters after operation, and IP address or geographical location information of the operation terminal. The log storage and indexing unit is used to store operation logs in a structured manner and create indexes. The log query and analysis unit provides a multi-dimensional query interface based on time, user, operation type, and device identifier, and supports source tracing analysis of operation behavior.

7. A lubricator monitoring and management platform according to any one of claims 1 to 6, characterized in that, The platform also includes a data interface module for interacting with physical lubricators distributed on-site via wired or wireless communication protocols, or for integrating data with the upper-level enterprise resource planning system.

8. A lubricator monitoring and management platform according to claim 1, characterized in that, The data dashboard module displays a lubrication time distribution chart, specifically a bar chart or heat map showing the number or frequency of lubrication events occurring in different time periods within a 24-hour day.

9. A lubricator monitoring and management platform according to claim 2, characterized in that, The consumption statistics unit is also used to generate a monthly grease consumption statistics comparison chart to compare the consumption differences between different months or different lubricator groups.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the functions of any module in the lubricator monitoring and management platform as described in any one of claims 1 to 9.

Images