Equipment management method based on equipment management system and computer equipment

Abstract

The invention discloses a device management method based on a device management system and a computer device, the device management system is used for managing at least one device, and the method comprises the following steps: obtaining device information of a target device and at least one operation and maintenance responsibility account associated with the target device; the target device is any device in the at least one device; if it is detected that the target equipment is abnormal based on the equipment information of the target equipment, generating an operation and maintenance work order of the target equipment based on the equipment information of the target equipment and the abnormal type of the target equipment; and determining a target responsibility account matched with the abnormal type of the target equipment from the at least one operation and maintenance responsibility account, and sending the operation and maintenance work order of the target equipment to the target responsibility account. The embodiment of the invention can improve the equipment operation and maintenance efficiency.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a device management method based on a device management system and a computer device. Background Technology

[0002] In numerous fields such as industrial production, smart buildings, and public services, various types of equipment serve as key production and operational carriers. Their stable and efficient operation directly impacts enterprise production efficiency, operating costs, and service quality. Traditional equipment management models are limited by the experience, energy, and inspection cycles of inspection personnel, making it difficult to capture early abnormal signals in equipment in real time. This often leads to minor faults escalating into major malfunctions, increasing maintenance costs and potentially causing serious consequences such as equipment downtime and production interruptions. Especially with the deep integration of industrialization and intelligentization, the types and numbers of equipment are becoming increasingly complex, exhibiting characteristics such as distributed deployment, high levels of intelligence, and diversified maintenance needs. Traditional equipment management models are no longer adequate to meet the demands of modern, efficient, and precise equipment management. Summary of the Invention

[0003] This application provides an equipment management method and computer equipment based on an equipment management system, which can improve equipment operation and maintenance efficiency.

[0004] On one hand, embodiments of this application provide a device management method based on a device management system, wherein the device management system is used to manage at least one device, and the method includes:

[0005] Obtain the device information of the target device, as well as at least one operation and maintenance responsibility account associated with the target device; the target device is any one of at least one devices;

[0006] If an anomaly is detected in the target device based on the device information of the target device, a maintenance work order for the target device will be generated based on the device information and the anomaly type of the target device.

[0007] Identify the target responsibility account from at least one operation and maintenance responsibility account that matches the anomaly type of the target device, and send the operation and maintenance work order of the target device to the target responsibility account.

[0008] On one hand, embodiments of this application provide a device management apparatus based on a device management system, the device management system being used to manage at least one device, the apparatus comprising:

[0009] The acquisition unit is used to acquire the device information of the target device and at least one operation and maintenance responsibility account associated with the target device; the target device is any one of the at least one devices.

[0010] The processing unit is used to generate a maintenance work order for the target device based on the device information and the type of the target device if an anomaly is detected in the target device based on the device information of the target device.

[0011] The processing unit is also used to determine the target responsibility account that matches the anomaly type of the target device from at least one operation and maintenance responsibility account, and send the operation and maintenance work order of the target device to the target responsibility account.

[0012] On one hand, embodiments of this application provide a computer device, the computer device comprising:

[0013] Processor, memory, and network interface;

[0014] The processor is connected to the memory and the network interface. The network interface is used to provide network communication functions, the memory is used to store program code, and the processor is used to call the program code to implement the above-mentioned device management method based on the device management system.

[0015] On one hand, embodiments of this application provide a computer-readable storage medium storing a computer program, the computer program including computer instructions adapted to be loaded by a processor and executed by the above-described device management method based on a device management system.

[0016] On the one hand, embodiments of this application provide a computer program product, which includes a computer program or computer instructions. When the computer program or computer instructions are executed by a processor, the above-described device management method based on a device management system is implemented.

[0017] This application proposes an equipment management method based on an equipment management system. By using the operation and maintenance resources associated with the equipment (such as equipment information and at least one operation and maintenance responsibility account), a targeted work order is automatically generated when the equipment is abnormal, and the professionally matched operation and maintenance responsibility account is matched. This realizes the automated and accurate flow of anomaly detection, work order generation, and responsibility allocation, avoiding the inefficiency and mismatch of traditional manual intervention. Attached Figure Description

[0018] The technical solution and beneficial effects of this application will become apparent and easily understood from the following description in conjunction with the accompanying drawings, wherein:

[0019] Figure 1 This is a schematic diagram of the architecture of a device management system provided in an embodiment of this application;

[0020] Figure 2 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0021] Figure 3This is a flowchart illustrating a device management method provided in an embodiment of this application;

[0022] Figure 4 This is a flowchart illustrating a device management scheme provided in an embodiment of this application;

[0023] Figure 5 This is a schematic diagram of the structure of a device management apparatus provided in an embodiment of this application;

[0024] Figure 6 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0025] 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.

[0026] This application proposes an integrated equipment management system covering the entire lifecycle. Through deep collaboration between front-end visual interaction and back-end intelligent scheduling, it can achieve standardized input and association of equipment information, accurate identification of multi-dimensional anomalies, efficient matching of operation and maintenance responsibilities, and automated control of the entire operation and maintenance process. This system accurately solves common pain points in traditional equipment management, such as scattered and uninterrupted information, delayed anomaly response, ambiguous operation and maintenance responsibilities, and fragmented and non-closed-loop processes.

[0027] Please see Figure 1 This is a schematic diagram of the architecture of an equipment management system provided in an embodiment of this application. The equipment management system can adopt a "layered architecture + modular" design, and is divided into five layers: front-end interaction layer, API (Application Programming Interface) gateway layer, back-end service layer, data storage layer, and support layer. Each layer works together to support the stable operation of three major functional modules (basic information and association management module, anomaly handling and work order flow core module, and front-end visualization and operation and maintenance module). Each functional module can focus on key business logic to avoid functional dispersion.

[0028] For example, the components and functional positioning of each layer of the front-end interaction layer, API gateway layer, back-end service layer, data storage layer, and support layer are as follows:

[0029] (1) Front-end interaction layer: The hierarchical components may include role-based customized interfaces such as equipment management interface, map visualization interface, operation and maintenance work order interface, consumable inventory interface, and account configuration interface; the function is positioned to provide exclusive visual interaction entry for different roles such as administrators, equipment operators, maintenance personnel, and suppliers, and supports general operations such as equipment information entry, equipment location viewing, work order operation, and information query and statistics. The interface display fields and operation options can be adapted according to the characteristics of equipment in different industries.

[0030] (2) API Gateway Layer: Layer components may include a unified interface adaptation module, a permission verification module, a request forwarding module, and a data format conversion module; its function is positioned as a "bridge" for front-end and back-end data interaction, responsible for receiving various requests initiated by the front-end, verifying user tokens and operation permissions, accurately forwarding legitimate requests to the corresponding back-end services, and converting back-end response data into a format that the front-end can recognize, so as to ensure the security, standardization and efficiency of front-end and back-end data interaction.

[0031] (3) Backend service layer: The layer components may include equipment information management service, account association service, anomaly detection service, work order generation service, responsibility account matching service, and message push service; the function is positioned as the system business logic processing center, which can be responsible for the storage and synchronization of various equipment information, the determination of the association between accounts and equipment, the real-time monitoring of equipment anomalies, the creation and distribution of standardized work orders, and the accurate push of operation and maintenance messages, etc.

[0032] (4) Data storage layer: Layered components may include structured databases (such as MySQL, used to store structured data such as device information, account information, work order information, and relationship information), unstructured storage systems (such as OSS object storage service, which can be used to store unstructured data such as scanned copies of device contracts, technical documents, maintenance record photos, and operation and maintenance videos), and data backup modules; the function is positioned as a "reservoir" for system data, which can realize standardized storage, related query, and persistent backup of various types of data, providing reliable data support for the entire process of system business operation.

[0033] (5) Support layer: Layered components may include a unified authentication module, intelligent messaging module, file storage module, log monitoring module, and system monitoring module; the function is positioned as the "cornerstone" for the stable operation of the system, and can provide basic support capabilities such as user identity authentication, multi-channel message push, file upload and download management, operation log auditing, and system operation status monitoring, so as to promptly detect and handle system operation anomalies and ensure the continuous and stable operation of the system.

[0034] For example, the basic information and association management module, the exception handling and work order workflow module, and the front-end visualization and operation module are as follows:

[0035] (1) Basic Information and Association Management Module: This module forms the foundation for system operation and is responsible for the collection, verification, association, and storage of device and account information, enabling precise binding of "device-account-responsibility." It should include at least the following functions:

[0036] Equipment Information Management: The front-end supports three methods for entering equipment information: scanning (e.g., scanning the equipment's unique QR code or barcode), manual entry, and batch import from documents. Entry fields can cover basic attribute information (e.g., equipment name, model, specifications, serial number, manufacturer, purchase date, product serial number, etc.), warranty period information (e.g., warranty start date, warranty expiration date, warranty scope, warranty service provider, etc.), contract period information (e.g., contract number, contract signing date, contract expiration date, renewal advance reminder period, etc.), supplier information (e.g., supplier name, contact person, contact information, delivery cycle, after-sales response time, etc.), and supporting consumable information (e.g., consumable model, compatible specifications, recommended replacement cycle, consumable inventory association code, etc.). The system can deploy location information (such as detailed address, area code, building, floor, room number, precise location coordinates, etc.) and supports custom extended fields based on equipment type (such as production equipment, office equipment). After receiving the equipment information entered by the front end, the back end can automatically verify the integrity and format validity of the fields (such as date format YYYY-MM-DD, contact information in 11-digit numerical format). After the verification is successful, the equipment information is bound to a unique equipment identifier (with global uniqueness, such as equipment SN (Serial Number) code) and stored in a structured database. At the same time, it is synchronized to related modules such as anomaly detection and map visualization. The equipment identifier serves as a retrieval key to support subsequent work order generation, responsibility matching and other full-process management operations.

[0037] Account Information and Association Management: The front-end supports administrators in configuring basic account information and permission information, including account roles (such as internal management personnel (e.g., equipment operators, department administrators), maintenance personnel, external partners (e.g., suppliers, third-party technical service providers)), responsibility areas (e.g., production workshop A area, office building 3rd floor, campus east area, etc., supporting multi-level area division), operation and maintenance skill tags (e.g., electrical repair, mechanical repair, printer maintenance, server operation and maintenance, quality inspection and calibration, etc., supporting multi-tag combination configuration), operation permission identifiers (e.g., permission code prefix is ​​"DEVICE-", suffix distinguishes operation type), etc., and also supports real-time viewing of the device and account association list; The back-end automatically collects information of all accounts in the system, and performs multi-dimensional matching based on attributes such as device deployment location, device type, supplier, etc., and account responsibility area, skill tags, and attribution information, automatically determining whether the account is the operation and maintenance responsibility account for the device and the specific responsibility type (e.g., maintenance responsibility account, internal management responsibility account, external partner responsibility account), and finally establishes and stores the "device identifier-account identifier-responsibility type" association table. The association relationship supports manual adjustment and batch update, and update records are automatically logged.

[0038] (2) Exception handling and work order circulation module: This is a system business module that can cover the entire chain of "exception detection - work order generation - responsibility matching - message push", realize automatic exception identification and efficient work order circulation, and can include at least the following functions:

[0039] Multi-dimensional anomaly detection: The backend can perform real-time anomaly monitoring based on device information, covering at least five types of anomalies: ① Quality inspection anomalies, such as extracting reference performance parameters from the device's basic attributes (e.g., rated speed of production equipment, printing speed of office equipment) and real-time collected performance parameters from the operating status information. If the collected performance parameters exceed the normal range set by the reference performance parameters (e.g., rated speed ±5%, this threshold can be customized according to the device type), it is determined to be a quality inspection anomaly; ② Equipment failure, such as if the on-site verification result of the quality inspection anomaly is that the device cannot operate normally, or the device's operating status sensor directly triggers a fault signal (e.g., power failure, overload, temperature exceeding the standard), it is determined to be an equipment failure; ③ Contract expiration anomalies, such as calculating the current system time and the equipment contract period. The system calculates the remaining valid days from the contract expiration date. If the remaining valid days are less than the preset renewal advance reminder period (e.g., 30 days, customizable based on contract type), it is considered an abnormal contract expiration. ④ Warranty expiration: Calculates the remaining warranty days from the current system time to the warranty expiration date. If the remaining warranty days are less than the preset warning period (e.g., 15 days, customizable based on device importance), it is considered an abnormal warranty expiration. ⑤ Insufficient consumables: Extracts consumable usage information from the device's operating status (e.g., remaining consumable quantity, usage time, consumption rate). If the remaining consumable usage time is less than the preset usage time (e.g., 10 days), or the remaining consumable quantity is less than the preset consumable quantity (e.g., 20%), it is considered an abnormal consumable quantity. The front-end can add differentiated markers for different types of abnormal devices on the map visualization interface (e.g., yellow for quality inspection abnormalities, red for equipment malfunctions, orange for time-related abnormalities, and blue for insufficient consumables), and display the abnormality level (general, important, urgent).

[0040] Standardized work order generation: The backend can call the corresponding template based on the exception type to integrate equipment information and exception data to generate standardized work orders such as quality inspection, maintenance, contract expiration reminders, warranty expiration reminders, and consumable replenishment. The work order includes fields such as a unique number (e.g., "exception type abbreviation-date-serial number"), exception description, processing requirements, and time limit requirements. The frontend supports displaying work order details and manually creating work orders (requiring the filling in of mandatory fields such as exception type, equipment information, and processing requirements).

[0041] Precise matching of responsibility accounts: The backend can filter the appropriate operation and maintenance responsibility accounts based on preset adaptation rules of exception type and responsibility account type; the frontend allows administrators to view the status information details of all adapted accounts, manually intervene to adjust the dispatch objects, and receive automatic dispatch result notifications in real time.

[0042] Message push synchronization: The backend can generate standardized messages when the work order status changes or an exception is triggered, and push them accurately to the corresponding accounts through multiple channels such as system messages, SMS, and email (custom push preferences for accounts are supported); the frontend receives real-time reminders and supports quick jump from the message interface to the work order or device location. Operation feedback is synchronized to the backend to update the work order status, and status change records are automatically retained.

[0043] (3) Front-end visualization and operation module: Focusing on front-end interaction and operation support for the entire operation process, realizing "visual positioning - role-based operation - operation and maintenance closed loop", it can include at least the following functions:

[0044] Map visualization positioning: Supports both 2D and 3D map viewing modes, accurately locating devices in the map visualization interface (positioning accuracy down to the room and device location); supports generating navigation routes from the current user's location to the target device; supports statistics on the total number of devices, the number of normal devices, and the number of abnormal devices by internal area or device type, generating visual statistical charts such as bar charts and pie charts; supports clicking on abnormal devices in the map visualization interface to directly trigger the work order details viewing interface, realizing one-click linkage of "device positioning - abnormal viewing - work order processing".

[0045] Role-based operation and maintenance: Precise operation options can be provided based on account roles and work order status. For example, equipment administrators can view progress, manually dispatch work orders, and adjust association relationships; maintenance personnel can accept or reject work orders (rejection requires a reason), navigate to operation and maintenance, report progress in real time, and upload maintenance results; external cooperation accounts can handle contract and warranty-related matters, submit operation and maintenance plans, and view the cooperative equipment ledger, achieving "minimum permissions + precise operation". All operation behaviors are automatically recorded in audit logs.

[0046] Please see Figure 2 This is a schematic diagram illustrating an application scenario of a device management system provided in an embodiment of this application. The application scenario includes at least one terminal device and a backend server. A network connection is established between the at least one terminal device and the backend server; this network connection can be wireless or wired.

[0047] Terminal devices can include, but are not limited to, mobile phones, tablets, desktop computers, laptops, PDAs, smartwatches, in-vehicle devices, and other mobile internet devices (MIDs) with network access capabilities. Backend servers can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, vehicle-to-everything (V2X) communication, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0048] The business implementation process and system operation and maintenance closed-loop process in this application scenario correspond one-to-one. The interaction logic between the terminal devices and the backend server in each link is as follows:

[0049] (a) Basic information filing and equipment interaction in related processes:

[0050] Terminal-side operation: Front-end operators (such as administrators and equipment operators) log in to the system through terminal devices such as desktop computers and tablets (supporting authentication methods such as account password, SMS verification, and single sign-on). Using the terminal's input devices (keyboard, touch screen, barcode scanner), they enter equipment information (such as basic attributes, warranty period, deployment location, etc.) through the equipment management interface, and enter or improve account information (such as role type, responsibility area, skill tags, etc.) through the account configuration interface.

[0051] Data transmission and server processing: Terminal devices can transmit the entered information to the backend server. After receiving the information, the backend server starts the verification module to perform multi-dimensional verification of the information (such as field integrity, format legality, permission identifier validity, role information standardization). After the verification is passed, the backend server binds the device information with a unique device identifier and stores it in the corresponding database. At the same time, the account information is entered into the account management database. The backend server can perform multi-dimensional matching with the account information based on the device deployment location, type and other attributes, and automatically establish a "device-account-responsibility" association. The matching rules can be configured and adjusted in the system backend.

[0052] Results feedback and terminal interaction: The backend server can send the association list data back to the administrator terminal. The administrator can view the association results through the terminal interface, and initiate manual adjustment commands for inaccurate matching associations through the terminal. After the adjustment command is confirmed by the server, the association is updated, the update record is stored in the log, and the basic filing process is completed.

[0053] (II) Equipment interaction in the anomaly detection and work order flow process:

[0054] Server-initiated detection and work order generation: The backend server's anomaly detection service can retrieve device operation data and basic information from the data storage layer at a preset frequency (e.g., once every minute, with customizable configuration). It performs multi-dimensional detection according to preset anomaly judgment criteria (e.g., deviation of performance parameters, insufficient deadline, etc.). Once an anomaly is detected, the backend server automatically calls the corresponding work order template, integrates device information and anomaly details to generate a standardized maintenance work order, initializes the work order status to "pending dispatch," and stores it in the work order management database.

[0055] Responsibility matching and message push: The responsibility account matching service on the backend server filters the appropriate maintenance responsibility account based on the anomaly type corresponding to the work order. After determining the appropriate target responsibility account, it generates a standardized message (which may include information such as work order number, anomaly type, device location, and processing time limit) and pushes it to the target responsibility account's terminal device (such as maintenance personnel's mobile phone or supplier's laptop) through multiple channels such as system messages, SMS, and email. The push record is automatically saved.

[0056] Terminal reception and viewing: The target responsibility account can receive work order push reminders (such as mobile SMS notifications and system pop-up reminders) through the terminal device. When the reminder message is clicked directly, it will jump to the work order details page to view the complete work order information, so as to prepare for subsequent operation and maintenance. Unread work orders will be highlighted on the terminal interface.

[0057] (III) Equipment interaction in operation and maintenance execution and closed-loop process:

[0058] Terminal order acceptance and maintenance navigation: The maintenance responsibility account can confirm the order acceptance through the terminal device (such as the maintenance personnel's mobile phone). The terminal device uploads the order acceptance instruction to the backend server. The server calls the map visualization service to generate a navigation route from the maintenance personnel's current location to the location of the equipment, and sends the navigation route data back to the terminal device. The maintenance personnel can view the navigation information through the terminal and go to the site to perform maintenance operations.

[0059] Progress reporting and data synchronization: During operation and maintenance, maintenance personnel can report the operation and maintenance progress in real time through terminal devices (such as "arrived on site", "under maintenance", "waiting for parts"). After the reported data is received by the backend server, the work order status can be updated synchronously and pushed to the administrator terminal. If it is necessary to apply for parts, a parts application form can be submitted through the terminal device (the part model, quantity and reason for application must be filled in). The backend server will transfer the application form to the corresponding management terminal for approval, and the approval result will be fed back to the applicant's terminal in real time.

[0060] Result Submission and Closed-Loop Confirmation: After maintenance is completed, the maintenance responsibility account can upload maintenance results (such as repair reports, replacement parts records, on-site photos, and test data) through terminal devices and submit a maintenance completion application. After receiving the application, the backend server can verify the completeness and compliance of the maintenance results (such as whether required fields are complete and whether photos are clear). After the verification is passed, the work order status is updated to "completed" synchronously, and the running status in the device information is updated to "normal". The closed-loop result is then sent back to the terminal devices of the relevant roles (such as administrators, maintenance responsibility accounts, etc.) to complete the entire maintenance closed loop.

[0061] This application scenario, through the architecture design of "terminal device-backend server", realizes collaborative operation of multiple roles and multiple devices. It not only ensures the convenience of front-end operation, but also achieves efficient processing of operation and maintenance closed-loop logic by relying on the computing power support of the backend server. It fully leverages the system's characteristics of strong versatility, high efficiency of collaboration, precise responsibility, and convenient operation, and can be widely adapted to the equipment management needs of various industries such as production, office, campus, and medical institutions.

[0062] This application proposes an equipment management method based on the above-described equipment management system, which will be described in detail below.

[0063] Please see Figure 3 This is a flowchart illustrating a device management method provided in an embodiment of this application. The device management method can be executed by the aforementioned server and may include the following steps S31-S33:

[0064] S31. Obtain the device information of the target device, and at least one operation and maintenance responsibility account associated with the target device; the target device is any one of the at least one devices.

[0065] The target device refers to any one of at least one device that is already documented and managed in the equipment management system (meaning that basic information has been entered into the system and bound to a unique device identifier, meeting the prerequisites of being searchable and associatable). The types of equipment may include, but are not limited to: production equipment (such as CNC machine tools, stamping machines), office equipment (such as printers, servers), public facilities (such as elevators, streetlights), teaching equipment (such as experimental instruments, projectors), medical equipment (such as ultrasound machines, sterilization machines), etc.

[0066] Equipment information for the target device refers to data stored in the system related to the target device. For example, equipment information may include at least one of the following: basic attribute information (such as equipment name, model, specifications, serial number, manufacturer, purchase date, product serial number), warranty period information (such as warranty start date, expiration date, warranty scope, warranty service provider), contract period information (such as contract number, signing date, expiration date, renewal advance notice period), equipment supply information (such as supplier name, contact person, contact information, delivery cycle, after-sales response time), supporting consumable information (such as compatible consumable models, replacement cycle, current inventory association, consumable supplier), deployment location information (such as detailed address, area code, building-floor-room number, precise location coordinates), internal affiliation information (such as department, responsible office, user team), operating status information (such as real-time performance parameters, usage duration, current working status, cumulative runtime), and anomaly detection records (such as historical anomaly types, occurrence time, processing results, and detection data).

[0067] In one embodiment, an information entry request for a target device can be received, containing the device information of the target device. The information entry request can be initiated by an authorized system account, such as a device administrator, device operator, or certified data entry personnel who can request the entry of basic attribute information, warranty period information, contract period information, equipment supply information, supporting consumables information, deployment location information, and internal affiliation information of the target device through the device management interface. It can also be automatically initiated by IoT data acquisition devices associated with the target device (e.g., real-time collection of the target device's operating status information and anomaly detection records, uploaded to the system, generating an information entry request; the collection frequency is configurable). Furthermore, it can be initiated by an authorized account through a batch import tool provided by the system (uploading standardized Excel template files, supporting template download and format verification, batch submission of device information for multiple devices, with the system automatically splitting and generating a single device's information entry request), or initiated by an external cooperative system with interface authentication (e.g., a device supplier's supply system, a third-party operation and maintenance platform, pushing target device supply information, warranty update information, etc., through a preset API interface, triggering the information entry request). The device information of the target device is associated with and stored with the device identifier of the target device; the device identifier of the target device is used to retrieve the device information of the target device. The device identifier of a target device is a unique and non-repeatable identifier assigned by the system (such as a custom device code, device serial number, or a system-generated unique identifier). It possesses global uniqueness and searchability, enabling rapid retrieval and access to device information throughout the system's workflow. This supports subsequent functions such as anomaly detection, work order generation, and responsibility matching. During associated storage, the system can use the device identifier as an index key to categorize and store various types of device information in corresponding databases (e.g., structured data in a relational database, and unstructured data (such as scanned contracts and technical documents) in an object storage service). A "device identifier - information type" mapping table is established to ensure accurate location and retrieval of device information during retrieval. It also supports subsequent updates and supplementary entries of device information, with updated data remaining associated with the original device identifier. Update records are automatically retained, ensuring information continuity and integrity.

[0068] At least one maintenance responsibility account associated with the target equipment refers to the set of accounts identified by the system based on preset association rules as having maintenance and management responsibility for the target equipment. Each account corresponds to a specific responsible entity (such as internal management personnel, dedicated maintenance technicians, equipment suppliers, third-party technical service providers) and responsibility type (such as maintenance, quality inspection, contract renewal, consumable replenishment, warranty service, etc.), and is the recipient of subsequent work orders. The types of maintenance responsibility accounts may include internal management accounts (such as accounts used by equipment administrators, workshop leaders, and department administrators), maintenance responsibility accounts (such as dedicated maintenance technicians and equipment inspectors), and external cooperation accounts (such as equipment suppliers and equipment supplier maintenance departments). This application can establish associations through multi-dimensional and precise matching of "equipment attributes - account attributes." For example, the equipment deployment location corresponds to the account responsibility area; the equipment type (such as CNC machine tools) and the account maintenance skill tag (such as electrical maintenance) are highly compatible (the matching threshold can be set to 80%); the equipment supplier (such as XX equipment manufacturer) is directly associated with the account's ownership information (such as XX manufacturer's maintenance department); and the internal department of the equipment is consistent with the account's management authority scope. A single target device can be associated with multiple operation and maintenance responsibility accounts to adapt to the division of responsibilities under different abnormal scenarios (such as simultaneously associating with an internal management account responsible for daily quality inspection and a maintenance responsibility account responsible for fault repair).

[0069] In one embodiment, at least one account can be registered in the equipment management system. The account information of the target account can be obtained, and the target account is any one of the at least one accounts. The account information of the target account is the basis for the system to determine the association between the target account and the target equipment. For example, the account information may include at least one of the following: (1) Role type, the identity classification of the account, which can determine the basic scope of responsibility of the account, such as internal management personnel, maintenance personnel, external cooperative personnel (such as suppliers or third-party service providers), etc. The role type is preset in the system and supports the addition of custom roles. (2) Internal affiliation information, the internal organizational unit to which the account belongs, such as the department (production department, administration department), section, team, etc., used to match the internal management affiliation of the equipment, and supports multi-level organizational structure association. (3) Operation and maintenance skill tags, describing the operation and maintenance professional capabilities of the account, such as "electrical repair", "printer maintenance", "server operation and maintenance", "quality inspection and calibration", etc., which can be used to match the technical requirements corresponding to the equipment type, and supports the addition and batch configuration of tags. (4) Responsibility Area: The physical area under the account's responsibility for operation and maintenance management, such as "Production Workshop Area A", "Office Building 3rd Floor", "East Campus", etc., which can be used to match the deployment location of equipment and support multi-level area association. (5) Permission Identifier: The operation permission code of the account in the system, such as "DEVICE-REPAIR-XXX" (maintenance permission), "DEVICE-OPERATE-XXX" (operation permission), "DEVICE-PURCHASE-XXX" (purchase permission), etc. XXX is the unique identifier of the target device, used to help determine whether the account has the corresponding operation and maintenance qualification.

[0070] The association between a target account and a target device can be determined based on one or more of the account information of the target account and the device information of the target device. This association can be used to indicate whether a target account is an operation and maintenance responsibility account associated with a target device. For example, the association used to indicate that a target account is an operation and maintenance responsibility account associated with a target device may include at least one of the following: the target account's responsibility area matches the target device's deployment location information (e.g., the account's responsibility area is "Workshop 1", and the device's deployment location is "Workshop 1 - Production Line 2"). The target account's internal affiliation information matches the target device's internal affiliation information (e.g., the account belongs to "Administration Department", and the device belongs to "Administration Department Office Area"). The target account's maintenance skill tag matches the target device's basic attribute information (e.g., device type, model) (e.g., the account tag is "CNC machine tool maintenance", and the device is "XX model CNC machine tool").

[0071] When the target account is an operation and maintenance (O&M) responsibility account associated with the target device, the association can also be used to indicate the type of O&M responsibility account corresponding to the target account. The O&M responsibility account type can include at least one of the following: maintenance responsibility account, internal management responsibility account, and external cooperation responsibility account. A maintenance responsibility account refers to an account with professional capabilities in equipment maintenance, fault handling, and performance calibration, and can be responsible for technical O&M work such as equipment fault repair, preventative maintenance, and periodic inspections. An internal management responsibility account can refer to the management account of an internal organizational unit, and can be responsible for management-related O&M work such as daily equipment management, consumable replenishment, contract or warranty monitoring, and work order dispatch. An external cooperation responsibility account can refer to the account of external entities such as equipment suppliers and third-party technical service providers, and can be responsible for cooperative O&M work such as equipment warranty services, dedicated repairs, contract renewals, and technical support.

[0072] For example, the situation where the target account is a maintenance responsibility account associated with the target device may include at least one of the following:

[0073] (1) The target account's role type is Maintenance Engineer (a system-preset role, which has maintenance responsibilities by default). No additional fields need to be matched, and it is directly determined to be a maintenance responsibility account. (2) The matching degree between the target account's maintenance skill tag and the target equipment's basic attribute information (such as equipment type, model, specifications, etc.) is higher than the preset matching degree (such as 80%, this threshold can be customized). For example, if the equipment's basic attribute is "XX model CNC machine tool", the target account's maintenance skill tag is "CNC machine tool maintenance"; if the equipment is "laser printer", the target account's maintenance skill tag is "office equipment maintenance - printer special". (3) The target account's permission identifier contains maintenance permissions for the target equipment (such as permission code "DEVICE-REPAIR-XXX", where XXX is the unique identifier of the target equipment), indicating that it has been authorized by the system and can perform maintenance operations on the equipment, and is determined to be a maintenance responsibility account.

[0074] For example, the situation where the target account is an internal management responsibility account associated with the target device may include at least one of the following:

[0075] (1) The target account's role type is internal employee (system preset role, which can cover internal management personnel, equipment operators, and other internal identities), and the target account's internal affiliation information (such as department, section, or team) is consistent with the target equipment's internal affiliation information (such as the target account belonging to Workshop 1 of the Production Department, and the target equipment belonging to Production Line 3 of Workshop 1 of the Production Department). (2) The target account's role type is internal employee, and the target account's responsibility area (preset physical scope of operation and maintenance management) matches the target equipment's deployment location information (such as the account's responsibility area being the 5th floor of the office building, and the equipment's deployment location being the administrative office on the 5th floor of the office building). (3) The target account's role type is internal employee, and the target account's permission identifier includes operation permissions for the target equipment (such as permission code "DEVICE-OPERATE-XXX"), indicating that it is responsible for the daily operation and management of the target equipment, and is determined to be an internal management responsibility account.

[0076] For example, the situation where the target account is an external cooperative responsibility account associated with the target device may include: the role type of the target account is a supplier or a third-party technical service provider, and the subject information corresponding to the target account (such as supplier name, unified social credit code) matches the equipment supply information of the target device (such as supplier name, cooperative subject code) (matching degree 100%). For example, if the equipment supply information is "XX Equipment Manufacturing Co., Ltd." and the role type of the target account is "XX Equipment Manufacturing Co., Ltd. - Operation and Maintenance Department", then it is determined to be an external cooperative responsibility account.

[0077] S32. If an anomaly is detected in the target device based on the device information of the target device, a maintenance work order for the target device is generated based on the device information and the anomaly type of the target device.

[0078] This application can utilize the equipment information of the target device to achieve multi-dimensional anomaly identification. Simultaneously, by combining equipment information and anomaly type, it generates standardized work orders that can be directly used for operation and maintenance execution, providing a clear basis for subsequent responsibility matching and operation and maintenance implementation.

[0079] In one embodiment, if an anomaly is detected in the target device based on its device information, a maintenance work order is generated for the target device based on the device information and the anomaly type. This includes extracting reference performance parameters from the target device's basic attribute information and collected performance parameters from the target device's operating status information. The reference performance parameters, derived from the target device's basic attribute information, are standardized performance benchmarks set at the factory (e.g., rated speed of a CNC machine tool, printing speed of a printer), serving as the "standard line" for determining whether the device is functioning correctly. The collected performance parameters, derived from the target device's operating status information, are real-time collected data on the device's actual operation (e.g., current operating speed of a CNC machine tool, actual printing rate of a printer), reflecting the device's current operating status as "actual values." The system can automatically extract both types of parameters from the corresponding information fields without manual intervention, ensuring the timeliness and accuracy of parameter extraction. If the collected performance parameters meet the device anomaly conditions indicated by the reference performance parameters, the target device is determined to have a quality inspection anomaly. Equipment anomaly conditions include judgment thresholds based on reference performance parameters (such as "collected performance parameters exceed reference value ±5%", "collected performance parameters remain below the lower limit of reference performance parameters for 3 consecutive minutes", etc., and the thresholds can be customized according to equipment type). The collected performance parameters can be compared with the equipment anomaly conditions indicated by the reference performance parameters. If the collected performance parameters meet the equipment anomaly conditions (e.g., printer reference printing speed 20 pages / minute, actual collected speed 10 pages / minute, below the lower limit), it indicates that the current performance of the equipment is substandard and requires further verification through quality inspection, directly determining that the target equipment has a quality inspection anomaly. A quality inspection work order for the target equipment can be generated based on the work order template corresponding to the quality inspection anomaly, the collected performance parameters (the basis for the anomaly data), and the basic attribute information of the target equipment (such as equipment name, model, and other identity information) and deployment location information (locating the specific location of the equipment). In other words, the work order template corresponding to the quality inspection anomaly can be filled using the collected performance parameters, the basic attribute information of the target equipment, and the deployment location information to obtain the quality inspection work order for the target equipment. This quality inspection work order clearly defines the inspection task (e.g., "investigate the reason why the equipment printing speed is not up to standard"), the testing standards (refer to performance parameters), the abnormal data (collect performance parameters), the equipment location information, and the processing time limit (e.g., complete the quality inspection within 24 hours). This allows the person being inspected to quickly understand "what to check, what standards to use, where to check, and when to complete." It is evident that anomaly judgment can be quantified through parameter comparison, avoiding subjective misjudgments.

[0080] Furthermore, the work order integrates key information and a dedicated template, ensuring that quality inspection operations have a clear basis and improving operation and maintenance efficiency.

[0081] In one feasible implementation, if the execution result of the quality inspection work order indicates a device malfunction in the target equipment, or if the operating status information of the target equipment indicates a device malfunction, a maintenance work order for the target equipment can be generated based on the work order template corresponding to the device malfunction, as well as the basic attribute information and deployment location information of the target equipment. In other words, this application can, on the one hand, first complete the equipment performance verification through the quality inspection work order. If the execution result clearly points to a "substantial malfunction in the target equipment" (such as quality inspection confirming printhead wear in a printer or gear jamming in a CNC machine tool, rather than parameter setting deviations), then a maintenance work order is triggered. This is a progressive scenario of "verification before repair." On the other hand, if a fault signal directly appears in the operating status information of the target equipment (such as a "mechanical jamming signal" or "power interruption signal" collected in real time by a sensor), then a maintenance work order is directly triggered. This is a direct scenario of "rapid response to emergency faults." The work order template corresponding to the device malfunction can include standardized modules such as fault description fields, repair step guidance, parts application entry, and fault level identifiers to avoid aimless repair operations. The basic attribute information and deployment location information of the target equipment can be used to fill in the work order template corresponding to the device malfunction to obtain the maintenance work order for the target equipment. The basic attribute information in this maintenance work order allows the responsible party to quickly identify the equipment and match suitable maintenance solutions and parts. The deployment location information in the maintenance work order clearly indicates the detailed physical location of the target equipment (e.g., "Workshop A - Production Line 3 - Equipment Position 5"), supporting maintenance personnel to quickly arrive at the scene. Therefore, the dual trigger path is suitable for both conventional scenarios of "performance failure requiring verification" and special scenarios of "sudden malfunctions requiring emergency handling," ensuring no faults are missed. Furthermore, the work order integrates equipment identity, location, and fault information, avoiding repeated data queries by maintenance personnel and improving fault handling efficiency. Connecting the entire chain of "quality inspection-maintenance" or "real-time monitoring-maintenance" ensures seamless transition from fault discovery to maintenance execution, reducing time spent in intermediate steps.

[0082] In one embodiment, if an anomaly is detected in the target device based on its device information, a maintenance work order is generated for the target device based on the device information and the anomaly type. This includes: determining the remaining valid days based on the current system time and the contract expiration date in the contract term information of the target device (calculated by subtracting the current system time from the contract expiration date, with the result in calendar days). For example, if the current time is October 1, xxx5, and the contract expiration date is October 20, xxx5, the remaining valid days are 19 days. If the remaining valid days are less than the renewal advance reminder period (e.g., 30 days, 15 days, which can be customized according to the contract type), for example, 19 days < 30 days reminder period, then the target device is determined to have a contract expiration anomaly, meaning the contract is about to expire and the renewal process needs to be initiated. A contract expiration reminder work order for the target device is generated based on the work order template corresponding to the contract expiration anomaly, as well as the device supply information and anomaly detection records of the target device. The work order template corresponding to the contract expiration anomaly can include standardized fields such as the renewal deadline, integration process guidance, a list of required materials, and a summary of key contract terms. In other words, the equipment supply information and anomaly detection records of the target equipment can be used to fill in the work order template corresponding to the contract expiration anomaly, resulting in a contract expiration reminder work order for the target equipment. This allows for convenient direct contact with the supplier regarding the equipment supply information in the contract expiration reminder work order, and the anomaly detection records can be used for internal decision-making reference, such as assessing whether to renew the contract in conjunction with historical fault records. Therefore, this application can achieve "proactive reminders before expiration" by setting a reminder period, avoiding service interruptions due to contract expiration (such as the failure of equipment warranty or after-sales support); moreover, the work order directly integrates supplier information and historical background, eliminating the need for the responsible party to query data separately, shortening the renewal coordination cycle; and it promotes renewal matters in a standardized work order format, clarifying responsibilities and time limits, ensuring that the renewal process is monitorable and traceable.

[0083] In one embodiment, if an anomaly is detected in the target device based on its device information, a maintenance work order is generated for the target device based on the device information and the anomaly type. This includes determining the remaining warranty days based on the current system time and the warranty expiration date in the target device's warranty period information (calculated by subtracting the current system time from the warranty expiration date, with the result in calendar days). For example, if the current time is November 5th, xxx5, and the warranty expiration date is November 20th, xxx5, the remaining warranty days are 15 days. If the remaining warranty days are less than a preset warning period (e.g., 15 days, 30 days, which can be customized according to the importance of the device), for example, 10 days less than the 15-day warning period, then the target device is determined to have a warranty expiration anomaly, meaning the warranty is about to expire, and the warranty extension or renewal process needs to be initiated. A warranty expiration reminder work order for the target device can be generated based on the work order template corresponding to the warranty expiration anomaly, as well as the target device's warranty period information, equipment supply information, and anomaly detection records. The work order template for warranty expiration anomalies can include standardized fields such as warranty expiration date, warranty extension process guidelines, required application materials, and original warranty coverage. In other words, the work order template for warranty expiration anomalies can be filled using the target equipment's warranty period information, equipment supply information, and anomaly detection records to generate a warranty expiration reminder work order for the target equipment. This way, the warranty period information in the warranty expiration reminder work order clearly defines the warranty expiration date and original warranty coverage; the equipment supply information directly provides the supplier's warranty contact person and contact information; and the historical fault data in the anomaly detection records can provide a reference for internal assessments of whether warranty renewal is needed and for negotiating warranty terms with the supplier, making warranty decisions more reasonable. Therefore, this application can achieve "proactive reminders before warranty expiration" through a preset warning period, avoiding warranty expiration due to forgetfulness and the inability to enjoy free repair, calibration, and other warranty services; moreover, the work order can directly integrate supplier warranty contact information, eliminating the need for additional inquiries by the responsible party and shortening the warranty extension contact cycle.

[0084] In one embodiment, if an anomaly is detected in the target device based on the device information of the target device, a maintenance work order for the target device is generated based on the device information and the anomaly type of the target device, including: extracting consumable usage information (such as remaining consumable quantity, usage duration, consumption rate, and last replacement time) from the operating status information of the target device.

[0085] If the remaining consumable usage time indicated by the consumable usage information is less than the preset usage time (e.g., 5 days remaining < preset 10 days, this time can be customized according to the consumable type), or the remaining consumable quantity indicated by the consumable usage information is less than the preset consumable quantity (e.g., 100 remaining < preset 200, this quantity can be customized), then the target device is determined to have a consumable shortage anomaly, and the consumable replenishment process needs to be initiated. A consumable replenishment reminder work order for the target device can be generated based on the work order template corresponding to the consumable shortage anomaly, the consumable usage information, and the target device's matching consumable information and deployment location information. The work order template corresponding to the consumable shortage anomaly can include standardized fields such as the purchase application process, delivery requirements, replenishment deadline, and consumable specifications. In other words, the work order template corresponding to the consumable shortage anomaly can be filled using the consumable usage information, the target device's matching consumable information, and deployment location information to obtain the target device's consumable replenishment reminder work order. This consumable replenishment reminder work order clearly indicates the degree of insufficiency (e.g., "5 days of usage time remaining"), specifies the model, supplier, and recommended quantity of the consumables, and clarifies the delivery destination. Therefore, by setting a threshold, proactive reminders before consumables run out can be implemented, preventing equipment downtime due to shortages (e.g., printers running out of toner cartridges, production equipment lacking spare parts). Furthermore, the work order directly integrates key procurement and delivery information, eliminating the need for additional inquiries by the responsible party and shortening the consumable replenishment cycle. The specific model of the consumables is clearly identified based on the matching information, preventing the purchase of incorrect or incompatible consumables and reducing procurement costs and time losses.

[0086] S33. Determine the target responsibility account that matches the anomaly type of the target device from at least one operation and maintenance responsibility account, and send the operation and maintenance work order of the target device to the target responsibility account.

[0087] In other words, the responsible party can be matched by the type of anomaly of the target device, and work orders can be pushed in a targeted manner to ensure that maintenance work orders are sent to the appropriate maintenance responsibility account, thereby avoiding work order confusion and improving the efficiency of anomaly handling.

[0088] In one embodiment, the target responsibility account that matches the anomaly type of the target equipment is determined from at least one operation and maintenance responsibility account, including: (1) If the anomaly type of the target equipment is a quality inspection anomaly, the internal management responsibility account associated with the target equipment (such as equipment administrator, workshop manager, department administrator) is determined as the target responsibility account. This is because quality inspection anomalies are checks on equipment performance parameters (such as whether the parameters meet the standards or whether calibration is required), which fall within the scope of daily equipment management and usually do not require professional maintenance skills or external cooperation support. (2) If the anomaly type of the target equipment is a contract expiration anomaly or a warranty expiration anomaly, one or both of the internal management responsibility account and external cooperation responsibility account associated with the target equipment are determined as the target responsibility account. This is because both contract expiration anomalies and warranty expiration anomalies involve "term extension coordination" (contract renewal, warranty extension or renewal), which requires internal overall planning and coordination with external suppliers, thus supporting single-account or dual-account collaborative handling. If only internal overall planning is required (such as first assessing whether to renew or renew the warranty), the internal management responsibility account can be determined as the target responsibility account separately. If direct external collaboration is required (e.g., contract renewal has been confirmed and a contract needs to be signed with the supplier), a separate external cooperation responsibility account (equipment supplier) can be designated as the target responsibility account. If internal and external collaboration is required (e.g., internal assessment + external negotiation of terms), both types of accounts can be designated as target responsibility accounts simultaneously, with tasks divided to advance the collaboration.

[0089] (3) If the anomaly type of the target equipment is insufficient consumables, the internal management responsibility account associated with the target equipment shall be determined as the target responsibility account. This is because consumable replenishment falls under the scope of internal material procurement and management (such as administrative procurement, warehouse allocation), and does not require the direct intervention of maintenance skills or external suppliers. (4) If the anomaly type of the target equipment is equipment failure, one or both of the external cooperation responsibility account and maintenance responsibility account associated with the target equipment shall be determined as the target responsibility account. This is because equipment failure requires professional maintenance capabilities, and external suppliers (within the warranty period) and dedicated maintenance personnel may have the corresponding capabilities, supporting single-account or dual-account collaboration. If dedicated maintenance personnel can handle the problem independently (such as minor failures, where dedicated maintenance personnel have the corresponding skills), the maintenance responsibility account can be determined as the target responsibility account separately. If external support is required (such as failures within the warranty period, where there is no corresponding internal maintenance capability), the external cooperation responsibility account (such as equipment supplier, third-party service provider) can be determined as the target responsibility account separately. If complex failures are handled collaboratively (such as internal preliminary investigation + external technical support), both types of accounts can be determined as target responsibility accounts simultaneously to jointly promote failure repair.

[0090] In one feasible implementation, there are multiple target responsibility accounts. Sending maintenance work orders for target equipment to these target responsibility accounts includes: obtaining status information for each target responsibility account, which includes at least one of the following: work order completion rate (the proportion of work orders completed within a historical period (e.g., 3 months) out of the total number of work orders received, such as 95%, reflecting the account's reliability and handling capability); work order resolution time (the average time taken for the account to complete work orders historically, such as 2 hours).

[0091] Time / Order, categorized by work order type, reflects the account's operational efficiency; Workload pressure (refers to the number of incomplete work orders currently in the account, such as 3 orders; supports setting a load limit threshold to reflect the account's current busy level and avoid excessive order assignment);

[0092] The physical distance to the target equipment (referring to the actual straight-line distance between the account holder (e.g., the current location of maintenance personnel, service outlet address) and the equipment deployment location, such as 3 kilometers, which affects on-site response speed). Based on the status information of each target responsibility account, target responsibility accounts that meet preset status conditions are selected from multiple target maintenance responsibilities. Preset status conditions can be customized according to business needs. For example, preset status conditions may include at least one of the following: work order completion rate ≥ 90% (ensuring reliable capability); work order resolution time ≤ 24 hours (differentiated configuration according to the urgency of the work order, such as ≤ 4 hours for urgent work orders); workload pressure ≤ 3 orders (ensuring reasonable load); physical distance to the target equipment ≤ 5 kilometers (can be adjusted according to equipment type, such as 10 kilometers for large equipment). The maintenance work orders for the target equipment are sent to the target responsibility accounts that meet the preset status conditions. If there are still multiple target responsibility accounts after filtering by preset status conditions, they can also be sorted by field weight (e.g., "work order completion rate > workload > physical distance", the weight ratio can be customized), and one or more target responsibility accounts with comprehensive priority can be locked to receive the maintenance work orders for the target equipment. For example, the system can use its preset multi-channel push methods (such as in-system messages, SMS, email, etc.) to simultaneously send maintenance work orders to the target devices. After a maintenance work order is sent, the system can automatically update the work order status to "pending acceptance" and record information such as the sending time and the receiving account. At the same time, the system can feed back the filtering results and sending status to the corresponding device management account (such as administrator or device operator) to facilitate progress monitoring. If no target responsible account meets the preset status conditions, the system can push an alert to the system administrator, who can then manually assign work orders or adjust the preset status conditions (such as relaxing physical distance restrictions) to avoid work order backlog. The alert information is retained until the work order loop is closed.

[0093] In summary, please refer to Figure 4 This is a flowchart illustrating a device management scheme provided in an embodiment of this application. The device management scheme includes the following steps S41-S44:

[0094] S41. Obtain the device information of the target device, and at least one operation and maintenance responsibility account associated with the target device; the target device is any one of the at least one devices.

[0095] S42. Based on the equipment information of the target equipment, detect whether the target equipment has any of the following abnormalities: quality inspection abnormality, equipment failure, contract expiration abnormality, warranty expiration abnormality, or insufficient consumables abnormality.

[0096] S43. If an anomaly is detected in the target device based on the device information of the target device, a maintenance work order is generated for the target device based on the device information and the anomaly type of the target device. The maintenance work order includes at least one of the following: quality inspection work order, repair work order, contract expiration reminder work order, warranty expiration reminder work order, and consumable replenishment reminder work order.

[0097] S44. Determine the target responsibility account that matches the anomaly type of the target device from at least one operation and maintenance responsibility account, and send the operation and maintenance work order of the target device to the target responsibility account.

[0098] This solution constructs a closed-loop management system for the entire equipment lifecycle, using "precise data support - intelligent anomaly early warning - targeted work order routing - efficient operation and maintenance execution" as its key logic. It effectively addresses pain points in traditional equipment management such as scattered information, delayed anomaly response, ambiguous responsibility attribution, and wasted operation and maintenance resources. Through multi-dimensional equipment information collection and correlation, it achieves automated and accurate detection and early warning of anomalies such as quality inspection, faults, expired contracts, expired warranties, and insufficient consumables. Combined with precise matching rules of "anomaly type - responsible account" and a multi-dimensional status filtering mechanism, it ensures that work orders are targeted to the responsible parties with matching capabilities, reasonable workloads, and efficient responses, significantly shortening the anomaly handling cycle. Simultaneously, it supports customized adaptation for equipment types across multiple industries and multi-role collaborative operation. This achieves standardized and regulated management of operation and maintenance processes, clarifies responsibility boundaries to avoid shirking responsibility, and reduces operation and maintenance costs through balanced resource allocation and precise scheduling, ensuring continuous and stable equipment operation. Ultimately, it provides an efficient, reliable, and flexible solution for equipment management in various scenarios such as enterprise production, government and enterprise offices, and university campuses, significantly improving business operation efficiency and management refinement.

[0099] The methods of the embodiments of this application have been described in detail above. To facilitate better implementation of the methods described in the embodiments of this application, a device management apparatus is correspondingly proposed based on the aforementioned device management system. Please refer to... Figure 5 This is a schematic diagram of a device management apparatus provided in an embodiment of this application. The device management apparatus can be built into a backend server and includes:

[0100] The acquisition unit 51 is used to acquire the device information of the target device and at least one operation and maintenance responsibility account associated with the target device;

[0101] The target device is any one of at least one devices;

[0102] The processing unit 52 is used to generate a maintenance work order for the target device based on the device information of the target device and the type of the target device if an anomaly is detected in the target device based on the device information of the target device.

[0103] The processing unit 52 is also used to determine the target responsibility account that matches the anomaly type of the target device from at least one operation and maintenance responsibility account, and send the operation and maintenance work order of the target device to the target responsibility account.

[0104] In one embodiment, the processing unit 52 is further configured to: receive an information entry request for a target device, the information entry request including device information of the target device, the device information including at least one of the following: basic attribute information, warranty period information, contract period information, equipment supply information, supporting consumable information, deployment location information, internal affiliation information, operating status information, and anomaly detection records; associate and store the device information of the target device with the device identifier of the target device; the device identifier of the target device is used to retrieve the device information of the target device.

[0105] In one embodiment, at least one account is registered in the device management system, and the acquisition unit 51 is further configured to: acquire account information of a target account, wherein the target account is any one of the at least one accounts; the account information includes at least one of the following:

[0106] The processing unit 52 is further configured to: determine the association between the target account and the target device based on one or more of the account information of the target account and the device information of the target device; wherein, the association is used to indicate whether the target account is an operation and maintenance responsibility account associated with the target device; when the target account is an operation and maintenance responsibility account associated with the target device, the association is also used to indicate the operation and maintenance responsibility account type corresponding to the target account; the operation and maintenance responsibility account type includes at least one of the following: maintenance responsibility account, internal management responsibility account, and external cooperation responsibility account.

[0107] In one embodiment, the device information includes basic attribute information, deployment location information, and operating status information. If the processing unit 52 detects an anomaly in the target device based on the device information of the target device, it generates a maintenance work order for the target device based on the device information and the anomaly type of the target device. This includes: extracting reference performance parameters from the basic attribute information of the target device and data acquisition performance parameters from the operating status information of the target device; if the data acquisition performance parameters meet the device anomaly conditions indicated by the reference performance parameters, it determines that the target device has a quality inspection anomaly; and generating a quality inspection work order for the target device based on the work order template corresponding to the quality inspection anomaly, the data acquisition performance parameters, and the basic attribute information and deployment location information of the target device.

[0108] If the execution result of the quality inspection work order is that the target device has a fault, then a maintenance work order for the target device will be generated based on the work order template corresponding to the fault, as well as the basic attribute information and deployment location information of the target device.

[0109] In one embodiment, the equipment information includes contract term information, equipment supply information, and anomaly detection records. If the processing unit 52 detects an anomaly in the target equipment based on the equipment information of the target equipment, it generates a maintenance work order for the target equipment based on the equipment information and the anomaly type of the target equipment. This includes: determining the remaining valid days based on the current system time and the contract expiration date in the contract term information of the target equipment; if the remaining valid days are less than the renewal advance reminder period, it is determined that the target equipment has a contract expiration anomaly; and generating a contract expiration reminder work order for the target equipment based on the work order template corresponding to the contract expiration anomaly, as well as the equipment supply information and anomaly detection records of the target equipment.

[0110] In one embodiment, the equipment information includes warranty period information, equipment supply information, and anomaly detection records. If the processing unit 52 detects an anomaly in the target equipment based on the equipment information of the target equipment, it generates a maintenance work order for the target equipment based on the equipment information and the anomaly type of the target equipment. This includes: determining the remaining warranty days based on the current system time and the warranty expiration date in the warranty period information of the target equipment; if the remaining warranty days are less than a preset warning period, it is determined that the target equipment has an expired warranty anomaly; and generating a warranty expiration reminder work order for the target equipment based on the work order template corresponding to the expired warranty anomaly, as well as the warranty period information, equipment supply information, and anomaly detection records of the target equipment.

[0111] In one embodiment, the device information includes supporting consumable information, operating status information, and deployment location information; if the processing unit 52 detects an anomaly in the target device based on the device information of the target device, it generates a maintenance work order for the target device based on the device information and the anomaly type of the target device, including: extracting consumable usage information from the operating status information of the target device; if the remaining consumable usage time indicated by the consumable usage information is less than a preset usage time, or the remaining consumable quantity indicated by the consumable usage information is less than a preset consumable quantity, it determines that the target device has a consumable shortage anomaly; based on the consumable shortage...

[0112] The system generates a consumable replenishment reminder work order for the target device by providing the corresponding work order template, consumable usage information, and the matching consumable information and deployment location information for the target device.

[0113] In one embodiment, the processing unit 52 determines a target responsibility account from at least one operation and maintenance responsibility account that matches the anomaly type of the target device, including: if the anomaly type of the target device is a quality inspection anomaly, then the internal management responsibility account associated with the target device is determined as the target responsibility account; if the anomaly type of the target device is a contract expiration anomaly or a warranty expiration anomaly, then one or both of the internal management responsibility account and the external cooperation responsibility account associated with the target device are determined as the target responsibility account; if the anomaly type of the target device is a consumable shortage anomaly, then the internal management responsibility account associated with the target device is determined as the target responsibility account; if the anomaly type of the target device is a device malfunction, then one or both of the external cooperation responsibility account and the maintenance responsibility account associated with the target device are determined as the target responsibility account.

[0114] In one embodiment, the target responsibility account includes multiple accounts; the processing unit 52 sends the maintenance work order of the target device to the target responsibility account, including: calling the acquisition unit 51 to acquire the status information of each target responsibility account, the status information including at least one of the following: work order completion rate, work order resolution time, workload pressure, and physical distance to the target device; based on the status information of each target responsibility account, selecting the target responsibility account that meets the preset status conditions from multiple target maintenance responsibilities; and sending the maintenance work order of the target device to the target responsibility account that meets the preset status conditions.

[0115] Based on the same application concept, the principle and beneficial effects of the device management device based on the device management system provided in the embodiments of this application are similar to the principle and beneficial effects of the device management method based on the device management system in the embodiments of this application. For the sake of brevity, the principle and beneficial effects of the method implementation can be referred to.

[0116] Please see Figure 6This is a schematic diagram of the structure of a computer device 60 provided in an embodiment of this application. The computer device 60 may include an input device 61, an output device 62, a processor 63, a memory 64, a network interface 65, and at least one communication bus 66. The processor 63 may be a Central Processing Unit (CPU). The processor may further include a hardware chip. The hardware chip may be an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), etc. The PLD may be a Field-Programmable Gate Array (FPGA), a Generic Array Logic (GAL), etc. Memory 64 may include volatile memory, such as random-access memory (RAM); memory 64 may also include non-volatile memory, such as flash memory, solid-state drive (SSD), etc.; memory 64 may be high-speed RAM or non-volatile memory, such as at least one disk drive. Optionally, memory 64 may also be at least one storage device located remotely from the aforementioned processor 63. Memory 64 may also include combinations of the above-mentioned types of memory. Figure 6 As shown, the memory 64, which is a computer-readable storage medium, may include an operating system, a network communication module, an object interface module, and a device control application.

[0117] The network interface 65 may include a standard wired interface or a wireless interface (such as a Wi-Fi interface) for providing data communication functions; the communication bus 66 is responsible for connecting various communication components; the input device 61 receives instructions from the object input to generate signal inputs related to the object settings and function control of the terminal device. In one embodiment, the input device 61 includes, but is not limited to, one or more of a touch panel, a physical keyboard or virtual keyboard, function keys, and a mouse; the output device 62 is used to output data information and may include a display screen or other display device; the processor 63 is the control center of the terminal device, connected to various parts of the entire terminal device by various interfaces and lines, and performs various functions by scheduling and running computer programs stored in the memory 64. The processor 63 can be used to call the computer programs in the memory to perform the following operations:

[0118] Obtain the device information of the target device, as well as at least one operation and maintenance responsibility account associated with the target device; the target device is any one of at least one devices;

[0119] If an anomaly is detected in the target device based on the device information of the target device, a maintenance work order for the target device will be generated based on the device information and the anomaly type of the target device.

[0120] Identify the target responsibility account from at least one operation and maintenance responsibility account that matches the anomaly type of the target device, and send the operation and maintenance work order of the target device to the target responsibility account.

[0121] In one embodiment, the processor 63 is further configured to: receive an information entry request for a target device, the information entry request including device information of the target device, the device information including at least one of the following: basic attribute information, warranty period information, contract period information, equipment supply information, supporting consumable information, deployment location information, internal affiliation information, operating status information, and anomaly detection records; associate and store the device information of the target device with the device identifier of the target device; the device identifier of the target device is used to retrieve the device information of the target device.

[0122] In one embodiment, at least one account is registered in the device management system, and the processor 63 is further configured to: obtain account information of a target account, wherein the target account is any one of the at least one accounts; the account information includes at least one of the following: role type, internal affiliation information, operation and maintenance skill tags, responsibility area, and permission identifier; determine the association relationship between the target account and the target device based on one or more of the account information of the target account and the device information of the target device; wherein the association relationship is used to indicate whether the target account is an operation and maintenance responsibility account associated with the target device; when the target account is an operation and maintenance responsibility account associated with the target device, the association relationship is also used to indicate the operation and maintenance responsibility account type corresponding to the target account; the operation and maintenance responsibility account type includes at least one of the following: maintenance responsibility account, internal management responsibility account, and external cooperation responsibility account.

[0123] In one embodiment, the device information includes basic attribute information, deployment location information, and operating status information. If the processor 63 detects an anomaly in the target device based on the device information of the target device, it generates a maintenance work order for the target device based on the device information and the anomaly type of the target device. This includes: extracting reference performance parameters from the basic attribute information of the target device and data acquisition performance parameters from the operating status information of the target device; if the data acquisition performance parameters meet the device anomaly conditions indicated by the reference performance parameters, it determines that the target device has a quality inspection anomaly; generating a quality inspection work order for the target device based on the work order template corresponding to the quality inspection anomaly, the data acquisition performance parameters, and the basic attribute information and deployment location information of the target device; if the execution result corresponding to the quality inspection work order is that the target device has a device failure, it generates a repair work order for the target device based on the work order template corresponding to the device failure and the basic attribute information and deployment location information of the target device.

[0124] In one embodiment, the device information includes contract term information, device supply information, and anomaly detection records. If the processor 63 detects an anomaly in the target device based on the device information, it generates a maintenance work order for the target device based on the device information and the anomaly type of the target device. This includes: determining the remaining valid days based on the current system time and the contract expiration date in the contract term information of the target device; if the remaining valid days are less than the renewal advance reminder period, it is determined that the target device has a contract expiration anomaly; and generating a contract expiration reminder work order for the target device based on the work order template corresponding to the contract expiration anomaly, as well as the device supply information and anomaly detection records of the target device.

[0125] In one embodiment, the device information includes warranty period information, device supply information, and anomaly detection records. If the processor 63 detects an anomaly in the target device based on the device information of the target device, it generates a maintenance work order for the target device based on the device information and the anomaly type of the target device. This includes: determining the remaining warranty days based on the current system time and the warranty expiration date in the warranty period information of the target device; if the remaining warranty days are less than a preset warning period, it is determined that the target device has an expiration warranty anomaly; and generating a warranty expiration reminder work order for the target device based on the work order template corresponding to the warranty expiration anomaly, as well as the warranty period information, device supply information, and anomaly detection records of the target device.

[0126] In one embodiment, the device information includes supporting consumable information, operating status information, and deployment location information. If the processor 63 detects an anomaly in the target device based on the device information of the target device, it generates a maintenance work order for the target device based on the device information and the anomaly type of the target device. This includes: extracting consumable usage information from the operating status information of the target device; determining that the target device has a consumable shortage anomaly if the remaining consumable usage time indicated by the consumable usage information is less than a preset usage time, or the remaining consumable quantity indicated by the consumable usage information is less than a preset consumable quantity; and generating a consumable replenishment reminder work order for the target device based on the work order template corresponding to the consumable shortage anomaly, the consumable usage information, and the supporting consumable information and deployment location information of the target device.

[0127] In one embodiment, the processor 63 determines a target responsibility account from at least one operation and maintenance responsibility account that matches the anomaly type of the target device, including: if the anomaly type of the target device is a quality inspection anomaly, then the internal management responsibility account associated with the target device is determined as the target responsibility account; if the anomaly type of the target device is a contract expiration anomaly or a warranty expiration anomaly, then one or both of the internal management responsibility account and the external cooperation responsibility account associated with the target device are determined as the target responsibility account; if the anomaly type of the target device is a consumable shortage anomaly, then the internal management responsibility account associated with the target device is determined as the target responsibility account; if the anomaly type of the target device is a device malfunction, then one or both of the external cooperation responsibility account and the maintenance responsibility account associated with the target device are determined as the target responsibility account.

[0128] In one embodiment, the target responsibility account includes multiple accounts; the processor 63 sends the maintenance work order of the target device to the target responsibility account, including: obtaining the status information of each target responsibility account, the status information including at least one of the following: work order completion rate, work order resolution time, workload pressure, and physical distance to the target device; based on the status information of each target responsibility account, filtering out the target responsibility account that meets the preset status conditions from multiple target maintenance responsibilities; and sending the maintenance work order of the target device to the target responsibility account that meets the preset status conditions.

[0129] Based on the same application concept, the principle and beneficial effects of the computer device provided in the embodiments of this application in solving the problem are similar to the principle and beneficial effects of the device management method based on the device management system in the embodiments of this application in solving the problem. Please refer to the principle and beneficial effects of the implementation of the method. For the sake of brevity, they will not be repeated here.

[0130] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0131] This application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned device management method based on a device management system.

[0132] This application also provides another computer program product, which includes a computer program or computer instructions that, when executed by a processor, implement the above-described device management method based on a device management system.

[0133] In this application embodiment, the collection and processing of relevant data should strictly comply with the requirements of relevant laws and regulations. The acquisition of personal information must be based on the knowledge or consent of the individual (or have a legal basis for information acquisition), and subsequent data use and processing should be carried out within the scope of laws and regulations and the authorization of the personal information subject.

[0134] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A device management method based on a device management system, characterized in that, The device management system is used to manage at least one device, and the method includes: Obtain the device information of the target device, and at least one operation and maintenance responsibility account associated with the target device; the target device is any one of the at least one devices; If an anomaly is detected in the target device based on the device information of the target device, a maintenance work order for the target device is generated based on the device information of the target device and the anomaly type of the target device. From the at least one maintenance responsibility account, determine the target responsibility account that matches the anomaly type of the target device, and send the maintenance work order of the target device to the target responsibility account.

2. The method as described in claim 1, characterized in that, The method further includes: Receive an information entry request for the target device, the information entry request containing device information of the target device, the device information including at least one of the following: basic attribute information, warranty period information, contract period information, equipment supply information, supporting consumable information, deployment location information, internal ownership information, operating status information, and anomaly detection records; The device information of the target device is associated with and stored with the device identifier of the target device; the device identifier of the target device is used to retrieve the device information of the target device.

3. The method as described in claim 1, characterized in that, The device management system has at least one registered account, and the method further includes: Obtain account information of the target account, wherein the target account is any one of the at least one accounts; the account information includes at least one of the following: role type, internal affiliation information, operation and maintenance skill tags, responsibility area, and permission identifier; Based on one or more of the account information of the target account and the device information of the target device, the association relationship between the target account and the target device is determined; The association relationship is used to indicate whether the target account is an operation and maintenance responsibility account associated with the target device; when the target account is an operation and maintenance responsibility account associated with the target device, the association relationship is also used to indicate the operation and maintenance responsibility account type corresponding to the target account; the operation and maintenance responsibility account type includes at least one of the following: maintenance responsibility account, internal management responsibility account, and external cooperation responsibility account.

4. The method according to any one of claims 1-3, characterized in that, The device information includes basic attribute information, deployment location information, and operating status information; If an anomaly is detected in the target device based on the device information of the target device, then a maintenance work order is generated for the target device based on the device information and the anomaly type of the target device, including: Extract reference performance parameters from the basic attribute information of the target device, and acquisition performance parameters from the operating status information of the target device; If the collected performance parameters meet the equipment abnormality conditions indicated by the reference performance parameters, then the target equipment is determined to have a quality inspection abnormality. Based on the work order template corresponding to the quality inspection anomaly, the data collection performance parameters, and the basic attribute information and deployment location information of the target device, a quality inspection work order for the target device is generated. If the execution result of the quality inspection work order is that the target device has a device failure, then a maintenance work order for the target device is generated based on the work order template corresponding to the device failure and the basic attribute information and deployment location information of the target device.

5. The method according to any one of claims 1-3, characterized in that, The equipment information includes contract term information, equipment supply information, and anomaly detection records; If an anomaly is detected in the target device based on the device information of the target device, then a maintenance work order is generated for the target device based on the device information and the anomaly type of the target device, including: Based on the current system time and the contract expiration date in the contract term information of the target device, determine the remaining valid days; If the remaining valid days are less than the renewal advance reminder period, the target device is determined to have a contract expiration anomaly. Based on the work order template corresponding to the contract expiration anomaly, as well as the equipment supply information and anomaly detection records of the target equipment, a contract expiration reminder work order for the target equipment is generated.

6. The method according to any one of claims 1-3, characterized in that, The equipment information includes warranty period information, equipment supply information, and abnormal detection records; If an anomaly is detected in the target device based on the device information of the target device, then a maintenance work order is generated for the target device based on the device information and the anomaly type of the target device, including: Based on the current system time and the warranty expiration date in the warranty period information of the target device, determine the remaining warranty days; If the remaining warranty days are less than the preset warning period, the target device is determined to have an expired warranty. Based on the work order template corresponding to the warranty expiration anomaly, as well as the warranty period information, equipment supply information, and anomaly detection records of the target equipment, a warranty expiration reminder work order for the target equipment is generated.

7. The method according to any one of claims 1-3, characterized in that, The equipment information includes information on supporting consumables, operating status, and deployment location. If an anomaly is detected in the target device based on the device information of the target device, then a maintenance work order is generated for the target device based on the device information and the anomaly type of the target device, including: Extract consumable usage information from the operating status information of the target device; If the remaining consumable usage time indicated by the consumable usage information is less than the preset usage time, or the remaining consumable quantity indicated by the consumable usage information is less than the preset consumable quantity, then the target device is determined to have a consumable shortage abnormality. Based on the work order template corresponding to the consumable shortage anomaly, the consumable usage information, and the matching consumable information and deployment location information of the target device, a consumable replenishment reminder work order for the target device is generated.

8. The method according to any one of claims 1-3, characterized in that, The step of determining the target responsibility account from the at least one operation and maintenance responsibility account that matches the anomaly type of the target device includes: If the anomaly type of the target device is a quality inspection anomaly, then the internal management responsibility account associated with the target device will be determined as the target responsibility account; If the anomaly type of the target equipment is contract expiration anomaly or warranty expiration anomaly, then one or both of the internal management responsibility account and external cooperation responsibility account associated with the target equipment shall be determined as the target responsibility account; If the anomaly type of the target device is insufficient consumables, then the internal management responsibility account associated with the target device will be identified as the target responsibility account. If the anomaly type of the target device is device failure, then one or both of the external cooperation responsibility account and maintenance responsibility account associated with the target device will be identified as the target responsibility account.

9. The method according to any one of claims 1-3, characterized in that, The target responsibility account includes multiple accounts; sending the maintenance work order of the target device to the target responsibility account includes: Obtain the status information of each target responsibility account, the status information including at least one of the following: work order completion rate, work order resolution time, workload pressure, and physical distance to the target device; Based on the status information of each target responsibility account, target responsibility accounts that meet preset status conditions are selected from multiple target operation and maintenance responsibilities; The maintenance work order for the target device is sent to the target responsible account that meets the preset status conditions.

10. A computer device, characterized in that, include: Processor, memory, and network interface; The processor is connected to the memory and the network interface, wherein the network interface is used to provide network communication functions, the memory is used to store program code, and the processor is used to call the program code to execute the device management method based on the device management system as described in any one of claims 1 to 9.

Images