CN116166194B - Equipment guarantee maintenance and management method and system - Google Patents
Equipment guarantee maintenance and management method and system Download PDFInfo
- Publication number
- CN116166194B CN116166194B CN202310086249.8A CN202310086249A CN116166194B CN 116166194 B CN116166194 B CN 116166194B CN 202310086249 A CN202310086249 A CN 202310086249A CN 116166194 B CN116166194 B CN 116166194B
- Authority
- CN
- China
- Prior art keywords
- equipment
- server
- state
- low cost
- memory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 124
- 238000007726 management method Methods 0.000 title claims description 22
- 230000008439 repair process Effects 0.000 claims abstract description 50
- 238000000034 method Methods 0.000 claims abstract description 41
- 230000008569 process Effects 0.000 description 7
- 239000007787 solid Substances 0.000 description 6
- 238000010586 diagram Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0616—Improving the reliability of storage systems in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
Abstract
The invention discloses a method and a system for equipment guarantee maintenance and management, wherein the method comprises the following steps: generating, by the server, a repair order a for equipment a, wherein the server does not update the status of equipment a in the main memory when generating repair order a; reading, by the server, a state of equipment a in the main memory; updating, by the server, the state of equipment a such that the state of equipment a changes from state a to state B, and storing, by the server, the state B of equipment a in a first low cost memory; the server sends the maintenance work order A to maintenance personnel; updating, by the server, state B of equipment a in the first low cost memory to state a if one of the following conditions is met: the server receives feedback which is sent by maintenance personnel and does not need maintenance; or the server receives the feedback of the maintenance completion sent by the maintenance personnel within a preset time.
Description
Technical Field
The invention relates to the technical field of equipment guarantee, in particular to a method and a system for equipment guarantee maintenance and management.
Background
The equipment guarantee maintenance management system is a core of the equipment guarantee process and is a management system for coordinating related resources to carry out a series of maintenance work. The equipment guarantee maintenance management system needs to generate a work order and send the work order to the handheld electronic equipment held by the execution body, and then the execution body completes equipment guarantee maintenance tasks according to the work order.
At present, a certain problem exists in the operation process of the equipment protection maintenance management system, for example, in certain practical application scenes, the maintenance process of a certain equipment or a certain equipment can be very simple but frequent, the whole maintenance process can last for not more than 10 minutes, but the maintenance frequency can reach a plurality of times a day, if the management system also continuously updates the state of the equipment in the memory in the maintenance process, the management system is caused to write operations to the memory frequently, and the service life of the memory is greatly reduced.
Disclosure of Invention
In order to achieve the above object, the present invention provides a method for equipment maintenance, repair and management, which is characterized in that the method comprises:
generating, by the server, a repair order a for equipment a, wherein the server does not update the status of equipment a in the main memory when generating repair order a;
reading, by the server, a state of equipment a in the main memory;
updating, by the server, the state of equipment a such that the state of equipment a changes from state a to state B, and storing, by the server, the state B of equipment a in a first low cost memory;
the server sends the maintenance work order A to maintenance personnel;
updating, by the server, state B of equipment a in the first low cost memory to state a if one of the following conditions is met:
the server receives feedback which is sent by maintenance personnel and does not need maintenance; or alternatively
The server receives a feedback of maintenance completion sent by a maintenance person within a predetermined time.
In a preferred embodiment, the method further comprises:
after storing, by the server, state B of equipment a in the first low cost memory, establishing, by the server, an entry for equipment a in the second low cost memory;
receiving, by the server, a first query message sent by the terminal a for a status of the equipment a;
after the server receives the first query message for the status of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by the server, for a status of equipment a in the first low cost memory if the server determines that an entry for equipment a is stored in the second low cost memory;
the state B of the equipment a stored in the first low cost memory is sent by the server to the terminal a.
In a preferred embodiment, the method further comprises:
after updating, by the server, the state B of equipment a in the first low cost memory to state a, comparing, by the server, the state of equipment a in the first low cost memory with the state of equipment a in the main memory;
if the state of equipment A in the first low cost memory and the state of equipment A in the main memory are both state A, deleting, by the server, a record of the state of equipment A in the first low cost memory;
if the state of equipment A in the first low cost memory and the state of equipment A in the main memory are both state A, then the entry for equipment A stored in the second low cost memory is deleted by the server.
In a preferred embodiment, the method further comprises:
after the server deletes the entry for equipment a stored in the second low cost memory, receiving, by the server, a second query message for the status of equipment a sent by terminal B;
after the server receives the second query message for the status of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by the server, for a status of equipment a in the main memory if the server determines that no entry for equipment a is stored in the second low cost memory;
the state a of the equipment a stored in the main memory is transmitted to the terminal B by the server.
In a preferred embodiment, the method further comprises:
the state B of equipment a in the first low cost memory is maintained by the server if the following two conditions are met:
the server does not receive the feedback which is sent by the maintenance personnel and does not need maintenance; and
the server does not receive feedback of repair completion sent by the serviceman within a predetermined time.
In a preferred embodiment, the method further comprises:
after maintaining, by the server, a state B of equipment a in the first low cost memory, comparing, by the server, the state of equipment a in the first low cost memory with the state of equipment a in the main memory;
if the state of equipment A in the first low cost memory is different from the state of equipment A in the main memory, updating, by the server, the state A of equipment A stored in the main memory to a state B;
after the server updates the state a of the equipment a stored in the main memory to the state B, deleting, by the server, a record of the state of the equipment a in the first low cost memory;
after the server updates the state a of equipment a stored in the main memory to state B, the entry for equipment a stored in the second low cost memory is deleted by the server.
In a preferred embodiment, the server sends the maintenance work order a to the maintenance personnel, specifically comprising the steps of:
dividing the maintenance work order A into a first part and a second part by a server;
the server sends a first message to a terminal C held by a maintenance person, wherein the first message comprises a first part of a maintenance work order A and a mark code of the maintenance work order A;
after the terminal C receives the first message, the terminal C displays the first part of the maintenance work order A to maintenance personnel;
after the serviceman reads the first part of the service ticket a, a request message for requesting the second part of the service ticket a is sent by the terminal C to the server.
In a preferred embodiment, the server sends the repair order a to the repair person further comprising the steps of:
after the server receives the request message for requesting the second part of the maintenance work order A, the server sends a second message to the terminal C held by the maintenance personnel, wherein the second message comprises the second part of the maintenance work order A and the mark code of the maintenance work order A;
the terminal C combines the first part and the second part of the maintenance work order A into a complete maintenance work order A based on the mark code of the maintenance work order A;
the complete repair worksheet a is presented to the repair person by terminal C.
The invention provides an equipment assurance maintenance management system, which is characterized in that the system is configured to execute the following operations:
generating, by the server, a repair order a for equipment a, wherein the server does not update the status of equipment a in the main memory when generating repair order a;
reading, by the server, a state of equipment a in the main memory;
updating, by the server, the state of equipment a such that the state of equipment a changes from state a to state B, and storing, by the server, the state B of equipment a in a first low cost memory;
the server sends the maintenance work order A to maintenance personnel;
updating, by the server, state B of equipment a in the first low cost memory to state a if one of the following conditions is met:
the server receives feedback which is sent by maintenance personnel and does not need maintenance; or alternatively
The server receives a feedback of maintenance completion sent by a maintenance person within a predetermined time.
In a preferred embodiment, the system is further configured to:
after storing, by the server, state B of equipment a in the first low cost memory, establishing, by the server, an entry for equipment a in the second low cost memory;
receiving, by the server, a first query message sent by the terminal a for a status of the equipment a;
after the server receives the first query message for the status of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by the server, for a status of equipment a in the first low cost memory if the server determines that an entry for equipment a is stored in the second low cost memory;
the state B of the equipment a stored in the first low cost memory is sent by the server to the terminal a.
The invention has the advantage over the prior art that even for maintenance procedures which are very simple but relatively frequent, the management system constantly updates the status of the relevant equipment in the memory, which operational logic results in a reduced lifetime of the memory. The invention provides a new method which can prevent the data of the same storage address in the memory from being frequently erased under the unnecessary condition, thereby prolonging the service life of the expensive memory.
Drawings
Fig. 1 is a schematic structural view of an embodiment of the present invention.
FIG. 2 is a method flow diagram of one embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the invention is, therefore, to be taken in conjunction with the accompanying drawings, and it is to be understood that the scope of the invention is not limited to the specific embodiments.
As described in the background, if the management system continuously updates the status of the equipment in the memory during maintenance, which is very simple but relatively frequent in maintenance, the life of the memory will be reduced. The specific analysis for this technical problem is as follows: during operation of the equipment management system, the equipment management system server needs to maintain a database of equipment status, and the server needs to operate internal memory to continuously update the status of the equipment according to the current status of the equipment in order to prevent misoperation of the equipment. For example, for a certain equipment X, if the equipment X is in an operating state, the server needs to operate the memory so as to write the state of the equipment X in the memory as "in operation (normal, running, using, etc. terms may also be used)", if the equipment X is in a maintenance state, the server needs to operate the memory so as to rewrite the state of the equipment X in the memory as "in maintenance (disabling, maintaining, unavailable, etc. terms may also be used)", and if the equipment X is completed, the server needs to operate the memory so as to rewrite the state of the equipment X in the memory as "in operation" again. Counting the erasing and writing times of the memory in one maintenance process, wherein the erasing and writing times are as follows: erasing 2 times, writing 2 times. If such repair activities occur frequently, the number of erasures and writes to the memory will increase exponentially. In the prior art, an enterprise-level solid state disk is generally used in a management system server, and it is well known that the service life of the solid state disk is mainly determined by the erasing times, and once the erasing times reach a threshold value, a storage unit loses the capacity of storing charges (such as a floating gate type solid state disk), so that the solid state disk is invalid. The cost of the solid state disk of the common enterprise level is over ten thousand yuan, and a plurality of important data are stored in the memory, so that the operation and maintenance cost of the management system is greatly increased by replacing the memory. The present invention proposes a solution to the problems of the prior art.
Example 1
Fig. 1 is a schematic structural view of an embodiment of the present invention. As shown, the system of the present invention may include a server, a first low cost memory, a second low cost memory, and a main memory. The server may operate the first low-cost memory, the second low-cost memory, and the main memory through a processor, a software program, and a memory controller, and a specific manner of the processor operating the memory is common knowledge in the modern computer field, which is not described in detail herein. In the present invention, the main memory may refer to an enterprise-level solid state disk inside the management system, and theoretically, all data required to be used by the management system are stored inside the main memory. The first low cost memory is a separate memory physically isolated from the main memory, which need not have the same lifetime as the main memory, e.g. the first low cost memory may be a simple 128Mb storage capacity flash memory, which may currently be several tens of bits worth of memory chips. The first low cost memory is physically isolated from the second low cost memory at the same time, the first low cost memory and the second low cost memory are two independent memory chips, for example, the second low cost memory can also be a simple 128Mb memory capacity flash memory.
Example 2
FIG. 2 is a method flow diagram of one embodiment of the present invention. As shown, the method of the present invention comprises the steps of:
step 1: generating, by the server, a repair order a for equipment a, wherein the server does not update the status of equipment a in the main memory when generating repair order a; in one example, before the server generates a repair worksheet a for equipment a, the state of equipment a in main memory may be an "in-service" state;
step 2: reading, by the server, a state of equipment a in the main memory; in one example, the server may read the status of equipment A in main memory "in-flight" and store the status of equipment A "in-flight" in the cache of the server, and in one example, the server may read the status of equipment A in main memory "in-flight" and store the status of equipment A "in-flight" in the first low cost memory;
step 3: updating, by the server, the state of equipment a such that the state of equipment a changes from state a to state B, and storing, by the server, the state B of equipment a in a first low cost memory; in one example, the cache of the server may be operated to change the status "in service" of equipment a to "in repair"; it will be appreciated by those skilled in the art that in the present invention, the state a of equipment a may represent that the state of equipment a is in operation, normal, running or in use, etc.; the status B of equipment a may indicate that the status of equipment a is in repair, out of service, in maintenance, unavailable, etc.;
step 4: the server sends the maintenance work order A to maintenance personnel;
step 5: updating, by the server, state B of equipment a in the first low cost memory to state a if one of the following conditions is met:
the server receives feedback which is sent by maintenance personnel and does not need maintenance; or alternatively
The server receives a feedback of maintenance completion sent by a maintenance person within a predetermined time. In one example, for some high importance level equipment, the server may send a maintenance work order to a maintenance person if the equipment is not damaged, and if the equipment specifically needs maintenance, the maintenance person needs to check the equipment on site to make a judgment, so the server may receive feedback that the maintenance person sends and does not need maintenance; in one example, certain simple maintenance operations may be completed within 10-20 minutes, for example, due to equipment load transient overloads, resulting in equipment downtime, and again for example, equipment fuse burn-out, such maintenance operations may typically be completed within 10-20 minutes; in one example, the predetermined time may be set to 10 minutes, 20 minutes, 30 minutes. In the present invention, the predetermined time is not set too long, for example, if the predetermined time is set to 48 hours, which means that the current state of the equipment a will be stored in the first low cost memory all the time within 48 hours, but the first low cost memory is a low cost device, so that its stability is far lower than the main memory, for example, if a current surge occurs, the data stored in the first low cost memory may be damaged, or the data stored in the first low cost memory may be erroneously rewritten, which will cause a display error of the current state of the subsequent equipment a. Furthermore, if the current state of the equipment a is stored in the first low cost memory for a long period of time, this will result in the first low cost memory storing a large amount of the current state of the equipment, which easily results in the memory space of the first low cost memory being filled.
Example 3
In embodiment 3, the method further comprises:
after storing, by the server, state B of equipment a in the first low cost memory, establishing, by the server, an entry for equipment a in the second low cost memory; it will be appreciated by those skilled in the art that this step occurs after step 3 of embodiment 2 or simultaneously with step 3 of embodiment 2, in one example, while the server stores state B of equipment a in the first low cost memory, the server creates an entry for equipment a in the second low cost memory; the second low cost memory is used for preventing the server from failing to define the data reading error and preventing the logic error from occurring in the operation process of the server, for example, assuming that the second low cost memory is not set, when a certain terminal requests to inquire the current state of the equipment A, the server does not know whether the state of the equipment A in the main memory should be read or the current state of the equipment A in the first low cost memory is read, and then the logic error may occur; in addition, when the terminal reads the current state of the equipment a to the first low cost memory, the current state of the equipment a stored in the first low cost memory may be deleted or the first low cost memory is entirely disabled due to a defect of the first low cost memory, and if there is no entry for the equipment a recorded in the second low cost memory, the server cannot determine whether to store the state of the equipment a in the first low cost memory, thereby causing the server to be unable to define a cause of the data read error. The reason for designing the second low cost memory separately is that if the entries for equipment a are all stored in the first low cost memory, if the first low cost memory fails, the server will still have a problem that the data read error and the logic error cannot be defined;
receiving, by the server, a first query message sent by the terminal a for a status of the equipment a;
after the server receives the first query message for the status of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by the server, for a status of equipment a in the first low cost memory if the server determines that an entry for equipment a is stored in the second low cost memory;
the state B of the equipment a stored in the first low cost memory is sent by the server to the terminal a.
Example 4
In embodiment 4, the method further comprises:
after updating, by the server, the state B of equipment a in the first low cost memory to state a, comparing, by the server, the state of equipment a in the first low cost memory with the state of equipment a in the main memory; in one example, the current state of equipment a in the first low cost memory is "in operation", and the state of equipment a in the main memory is also "in operation" since it has not been erased yet;
if the state of equipment A in the first low cost memory and the state of equipment A in the main memory are both state A, deleting, by the server, a record of the state of equipment A in the first low cost memory; in one example, the record of the status of equipment a in the current first low cost memory is that the status of equipment a is "in operation"; in one example, the storage space of the first low cost memory is small for cost saving and data recovery convenience, so the server needs to delete the record of the state of equipment a in the first low cost memory at any time;
if the state of equipment A in the first low cost memory and the state of equipment A in the main memory are both state A, then the entry for equipment A stored in the second low cost memory is deleted by the server. In one example, since the server has deleted the record of the state of equipment a in the first low cost memory, it is necessary to delete the entry for equipment a stored in the second low cost memory, so that when the terminal queries the state of equipment a, the server will search the main memory for the current state of equipment a since there is no entry for equipment a in the second low cost memory.
The method further comprises the steps of: after the server deletes the entry for equipment a stored in the second low cost memory, receiving, by the server, a second query message for the status of equipment a sent by terminal B; after the server receives the second query message for the status of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory; searching, by the server, for a status of equipment a in the main memory if the server determines that no entry for equipment a is stored in the second low cost memory; the state a of the equipment a stored in the main memory is transmitted to the terminal B by the server.
Example 5
In embodiment 5, the method further comprises:
the state B of equipment a in the first low cost memory is maintained by the server if the following two conditions are met: the server does not receive the maintenance-free feedback sent by the maintenance personnel (within a predetermined time); and the server does not receive feedback of repair completion sent by the repair person within a predetermined time. In one example, the predetermined time may be set to 10 minutes, 20 minutes, 30 minutes.
In a preferred embodiment, the method further comprises: after maintaining, by the server, a state B of equipment a in the first low cost memory, comparing, by the server, the state of equipment a in the first low cost memory with the state of equipment a in the main memory; if the state of equipment A in the first low cost memory is different from the state of equipment A in the main memory, updating, by the server, the state A of equipment A stored in the main memory to a state B; after the server updates the state a of the equipment a stored in the main memory to the state B, deleting, by the server, a record of the state of the equipment a in the first low cost memory; after the server updates the state a of equipment a stored in the main memory to state B, the entry for equipment a stored in the second low cost memory is deleted by the server. In one example, some repair work may take 5 hours, 10 hours to complete, in which case there has been no problem of frequent erasing of memory locations in main memory, at which point the updated state of equipment a ("e.g., in-repair state") is written to main memory in order to be able to empty memory space in the first low cost memory as soon as possible. As can be seen from the above embodiments, the present invention can avoid frequently erasing the data of the same memory address in the expensive main memory, thereby improving the service life of the main memory.
Example 6
In embodiment 6, the server sends the maintenance work order a to the maintenance personnel specifically includes the following steps:
dividing the maintenance work order A into a first part and a second part by a server; in one example, the content of the repair worksheet may be divided into a necessary portion and an unnecessary portion, for example, in the repair worksheet, the position of the equipment to be repaired, the required repair parts are the necessary portion of the repair worksheet, and the repair details requiring the repair personnel in the repair process are the unnecessary portion of the repair worksheet; in some scenarios, the server may need to send multiple repair worksheets to multiple terminals at the same time, and the data volume of each complete repair worksheet is large, if the server is required to send the complete repair worksheets to multiple terminals at the same time, the instantaneous data sending volume of the server may be too large, which results in slow data sending. In the embodiment, the server divides the maintenance work order into at least two parts, and even in the scene that the server simultaneously transmits the complete maintenance work order to a plurality of terminals, the server only simultaneously transmits one part of the complete maintenance work order, thereby greatly reducing the instantaneous data transmission quantity of the server;
the server sends a first message to a terminal C held by a maintenance person, wherein the first message comprises a first part of a maintenance work order A and a mark code of the maintenance work order A;
after the terminal C receives the first message, the terminal C displays the first part of the maintenance work order A to maintenance personnel; in one example, terminal C may display the first portion of repair worksheet a to a repair person via a screen;
after the serviceman reads the first part of the service ticket a, a request message for requesting the second part of the service ticket a is sent by the terminal C to the server. In one example, after reading the first portion of the service ticket a, the serviceman may click a virtual button on terminal C, informing terminal C that the serviceman needs to read the second portion of the service ticket a; in this embodiment, even though the server transmits the first portion of the maintenance work order to the plurality of terminals at the same time, the server does not transmit the second portion of the maintenance work order to the plurality of terminals at the same time substantially because each terminal displays the difference in speed of the maintenance work order, the difference in speed of the maintenance person reading the work order, and the difference in timing of the maintenance person clicking the button on the terminal, and thus the embodiment can solve the aforementioned technical problems in this manner.
In a preferred embodiment, the server sends the repair order a to the repair person further comprising the steps of: after the server receives the request message for requesting the second part of the maintenance work order A, the server sends a second message to the terminal C held by the maintenance personnel, wherein the second message comprises the second part of the maintenance work order A and the mark code of the maintenance work order A; the terminal C combines the first part and the second part of the maintenance work order A into a complete maintenance work order A based on the mark code of the maintenance work order A; the complete repair worksheet a is presented to the repair person by terminal C.
Example 7
The present invention provides an equipment warranty repair maintenance management system capable of performing the method described in the foregoing embodiments of the present invention.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explanation of the principles of the present invention and are in no way limiting of the invention. Accordingly, any modification, equivalent replacement, improvement, etc. made without departing from the spirit and scope of the present invention should be included in the scope of the present invention. Furthermore, the appended claims are intended to cover all such changes and modifications that fall within the scope and boundary of the appended claims, or equivalents of such scope and boundary.
Claims (10)
1. An equipment assurance maintenance management method, characterized in that the method comprises:
generating, by a server, a repair order a for equipment a, wherein the server does not update the status of equipment a in main memory when generating the repair order a;
reading, by a server, a status of equipment a in the main memory;
updating, by the server, the state of equipment a such that the state of equipment a changes from state a to state B, and storing, by the server, the state B of equipment a in a first low cost memory;
the server sends the maintenance work order A to maintenance personnel;
updating, by a server, state B of the equipment a in the first low cost memory to state a if one of the following conditions is met:
the server receives maintenance-free feedback sent by the maintenance personnel; or alternatively
And the server receives feedback of maintenance completion sent by the maintenance personnel within a preset time.
2. The method of claim 1, wherein the method further comprises:
after storing, by the server, state B of equipment a in the first low cost memory, establishing, by the server, an entry for equipment a in the second low cost memory;
receiving, by a server, a first query message sent by a terminal a for a status of the equipment a;
after the server receives the first query message for the state of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by a server, for a status of equipment a in the first low cost memory if the server determines that an entry for the equipment a is stored in the second low cost memory;
the state B of the equipment a stored in the first low cost memory is sent by a server to the terminal a.
3. The method of claim 2, wherein the method further comprises:
after updating, by a server, a state B of the equipment a in the first low cost memory to a state a, comparing, by a server, the state of the equipment a in the first low cost memory with a state of the equipment a in the main memory;
deleting, by a server, a record of the state of equipment a in the first low cost memory if both the state of equipment a in the first low cost memory and the state of equipment a in the main memory are state a;
if the state of equipment A in the first low cost memory and the state of equipment A in the main memory are both state A, then deleting, by a server, an entry for equipment A stored in the second low cost memory.
4. A method as claimed in claim 3, wherein the method further comprises:
after the server deletes the entry for equipment a stored in the second low cost memory, receiving, by the server, a second query message for the status of equipment a sent by terminal B;
after the server receives the second query message for the status of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by a server, for a status of equipment a in the main memory if the server determines that no entry for the equipment a is stored in the second low cost memory;
the state a of the equipment a stored in the main memory is transmitted to the terminal B by a server.
5. The method of claim 4, wherein the method further comprises:
the state B of the equipment a in the first low cost memory is maintained by a server if the following two conditions are met:
the server does not receive the feedback which is sent by the maintenance personnel and does not need maintenance; and
the server does not receive feedback of repair completion sent by the repair person within a predetermined time.
6. The method of claim 5, wherein the method further comprises:
after maintaining, by a server, a state B of the equipment a in the first low cost memory, comparing, by a server, the state of the equipment a in the first low cost memory with a state of equipment a in the main memory;
updating, by a server, a state a of equipment a stored in the main memory to a state B if the state of equipment a in the first low cost memory is different from the state of equipment a in the main memory;
after the server updates the state a of the equipment a stored in the main memory to the state B, deleting, by the server, a record of the state of the equipment a in the first low cost memory;
after the server updates the state a of equipment a stored in the main memory to state B, the entry for equipment a stored in the second low cost memory is deleted by the server.
7. The method of claim 6, wherein the sending, by the server, the service ticket a to the service personnel comprises the steps of:
dividing the maintenance work order A into a first part and a second part by a server;
a server sends a first message to a terminal C held by the maintenance personnel, wherein the first message comprises a first part of the maintenance work order A and a mark code of the maintenance work order A;
after terminal C receives the first message, displaying, by terminal C, the first portion of the repair order a to the repair person;
after the serviceman reads the first part of the serviceman a, a request message for requesting the second part of the serviceman a is sent to the server by the terminal C.
8. The method of claim 7, wherein the sending of the repair order a by the server to the repair person further comprises the steps of:
after the server receives the request message for requesting the second part of the maintenance work order A, the server sends a second message to a terminal C held by the maintenance personnel, wherein the second message comprises the second part of the maintenance work order A and the mark code of the maintenance work order A;
the terminal C combines the first part and the second part of the maintenance work order A into a complete maintenance work order A based on the mark code of the maintenance work order A;
and displaying the complete maintenance work order A to the maintenance personnel by the terminal C.
9. An equipment warranty repair maintenance management system, characterized in that the system is configured to perform the following operations:
generating, by a server, a repair order a for equipment a, wherein the server does not update the status of equipment a in main memory when generating the repair order a;
reading, by a server, a status of equipment a in the main memory;
updating, by the server, the state of equipment a such that the state of equipment a changes from state a to state B, and storing, by the server, the state B of equipment a in a first low cost memory;
the server sends the maintenance work order A to maintenance personnel;
updating, by a server, state B of the equipment a in the first low cost memory to state a if one of the following conditions is met:
the server receives maintenance-free feedback sent by the maintenance personnel; or alternatively
And the server receives feedback of maintenance completion sent by the maintenance personnel within a preset time.
10. The system of claim 9, wherein the system is further configured to:
after storing, by the server, state B of equipment a in the first low cost memory, establishing, by the server, an entry for equipment a in the second low cost memory;
receiving, by a server, a first query message sent by a terminal a for a status of the equipment a;
after the server receives the first query message for the state of equipment a, determining, by the server, whether an entry for equipment a is stored in the second low cost memory;
searching, by a server, for a status of equipment a in the first low cost memory if the server determines that an entry for the equipment a is stored in the second low cost memory;
the state B of the equipment a stored in the first low cost memory is sent by a server to the terminal a.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310086249.8A CN116166194B (en) | 2023-01-16 | 2023-01-16 | Equipment guarantee maintenance and management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310086249.8A CN116166194B (en) | 2023-01-16 | 2023-01-16 | Equipment guarantee maintenance and management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116166194A CN116166194A (en) | 2023-05-26 |
| CN116166194B true CN116166194B (en) | 2023-11-03 |
Family
ID=86412776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310086249.8A Active CN116166194B (en) | 2023-01-16 | 2023-01-16 | Equipment guarantee maintenance and management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116166194B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20010067604A (en) * | 2001-02-21 | 2001-07-13 | 이동헌 | A method and apparatus for managemant of equipment |
| JP2002032880A (en) * | 2000-07-14 | 2002-01-31 | Hitachi Service & Engineering (East) Ltd | Remote maintenance system for equipment |
| CN1719422A (en) * | 2005-08-18 | 2006-01-11 | 北京中星微电子有限公司 | Virtual access method of storage document data |
| CN105824667A (en) * | 2016-03-15 | 2016-08-03 | 深圳市硅格半导体股份有限公司 | Management method, device and system for storage equipment |
| CN106068507A (en) * | 2014-03-11 | 2016-11-02 | 亚马逊科技公司 | Dynamically revise the durability characteristics of independent book |
| CN109739435A (en) * | 2018-12-03 | 2019-05-10 | 中科恒运股份有限公司 | File storage and update method and device |
| DE102019118631A1 (en) * | 2018-08-03 | 2020-02-06 | Samsung Electronics Co., Ltd. | Storage device that initiates maintenance work independently without command from the host and electronic system with the same |
| CN111527511A (en) * | 2017-12-26 | 2020-08-11 | 株式会社普利司通 | Hose management system |
| WO2021067232A1 (en) * | 2019-10-03 | 2021-04-08 | Landis+Gyr Innovations, Inc. | Restricting write cycles to extend the lifetime of nonvolatile memory |
| CN114282695A (en) * | 2021-12-27 | 2022-04-05 | 中电金信软件有限公司 | Fault maintenance method, fault maintenance device, electronic equipment and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030046433A1 (en) * | 2001-07-25 | 2003-03-06 | Omer Luzzatti | Method to synchronize information between online devices |
| US6954737B2 (en) * | 2001-11-05 | 2005-10-11 | Johnsondiversey, Inc. | Method and apparatus for work management for facility maintenance |
| JP5026102B2 (en) * | 2007-02-07 | 2012-09-12 | 株式会社日立製作所 | Storage control device and data management method |
| US8694678B2 (en) * | 2008-11-10 | 2014-04-08 | Telefonaktiebolaget L M Ericsson (Publ) | Method of providing data to a client |
| US20130145077A1 (en) * | 2011-12-01 | 2013-06-06 | International Business Machines Corporation | Dynamically managing memory lifespan in hybrid storage configurations |
-
2023
- 2023-01-16 CN CN202310086249.8A patent/CN116166194B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002032880A (en) * | 2000-07-14 | 2002-01-31 | Hitachi Service & Engineering (East) Ltd | Remote maintenance system for equipment |
| KR20010067604A (en) * | 2001-02-21 | 2001-07-13 | 이동헌 | A method and apparatus for managemant of equipment |
| CN1719422A (en) * | 2005-08-18 | 2006-01-11 | 北京中星微电子有限公司 | Virtual access method of storage document data |
| CN106068507A (en) * | 2014-03-11 | 2016-11-02 | 亚马逊科技公司 | Dynamically revise the durability characteristics of independent book |
| CN105824667A (en) * | 2016-03-15 | 2016-08-03 | 深圳市硅格半导体股份有限公司 | Management method, device and system for storage equipment |
| CN111527511A (en) * | 2017-12-26 | 2020-08-11 | 株式会社普利司通 | Hose management system |
| DE102019118631A1 (en) * | 2018-08-03 | 2020-02-06 | Samsung Electronics Co., Ltd. | Storage device that initiates maintenance work independently without command from the host and electronic system with the same |
| CN109739435A (en) * | 2018-12-03 | 2019-05-10 | 中科恒运股份有限公司 | File storage and update method and device |
| WO2021067232A1 (en) * | 2019-10-03 | 2021-04-08 | Landis+Gyr Innovations, Inc. | Restricting write cycles to extend the lifetime of nonvolatile memory |
| CN114282695A (en) * | 2021-12-27 | 2022-04-05 | 中电金信软件有限公司 | Fault maintenance method, fault maintenance device, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 新安防时代下超融合云存储的具体实现;许嗣强;;中国安防(第06期);全文 * |
| 车载无线设备动态管理系统研制与应用;方冲;;上海铁道科技(第03期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116166194A (en) | 2023-05-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101019192B (en) | Methods and apparatuses to track failing memory locations | |
| CN108646982B (en) | Automatic data restoration method and device based on UBIFS | |
| US20070118693A1 (en) | Method, apparatus and computer program product for cache restoration in a storage system | |
| JP2005242897A (en) | Flash disk drive | |
| JP2006235960A (en) | Method for increasing speed of garbage collection | |
| CN108733306B (en) | File merging method and device | |
| US20060224639A1 (en) | Backup system, program and backup method | |
| KR20040017276A (en) | Non-volatile memory and non-volatile memory data rewriting method | |
| CN110399333B (en) | Method, apparatus and computer program product for deleting snapshots | |
| US20180357142A1 (en) | Reporting defects in a flash memory back-up system | |
| CN111966287B (en) | Data storage method, electronic device and storage medium | |
| CN115951839A (en) | Data writing method and device for partition name space solid state disk and electronic equipment | |
| CN110795044B (en) | Bad block management method and system of NAND Flash memory | |
| CN112506710B (en) | Distributed file system data restoration method, device, equipment and storage medium | |
| CN109669889B (en) | Light Nor Flash control method and device | |
| CN116166194B (en) | Equipment guarantee maintenance and management method and system | |
| US8321626B2 (en) | Management of configuration data using persistent memories requiring block-wise erase before rewriting | |
| CN114089915B (en) | File additional writing operation method and device based on FLASH memory | |
| AU2013380500B2 (en) | Database device, program, and data processing method | |
| KR101676175B1 (en) | Apparatus and method for memory storage to protect data-loss after power loss | |
| CN110658981B (en) | Method for prolonging service life of Flash | |
| JP2012174106A (en) | Control device for reading and writing data from and to flash memory | |
| JP2003036209A (en) | Nonvolatile memory and data rewriting method thereof | |
| JPH06282386A (en) | Disk storage device | |
| CN112988037A (en) | Static wear leveling method, terminal and computer-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |