CN112182233A

CN112182233A - Knowledge base for storing equipment fault records and method and system for assisting in locating equipment fault by using knowledge base

Info

Publication number: CN112182233A
Application number: CN201910605357.5A
Authority: CN
Inventors: 张文渊; 王腾飞; 温晓宇; 彭奇斌; 陈鹏; 龙丽君
Original assignee: Beijing Xushui Interconnection Technology Co ltd
Current assignee: Beijing Xushui Interconnection Technology Co ltd
Priority date: 2019-07-05
Filing date: 2019-07-05
Publication date: 2021-01-05
Anticipated expiration: 2039-07-05
Also published as: CN112182233B

Abstract

The invention discloses a knowledge base for storing equipment fault records, and a method and a system for assisting in positioning equipment faults by using the knowledge base, wherein the knowledge base comprises root nodes determined by fault classification identifiers and fault record branches positioned under the fault classification identifiers, and the knowledge base adopts a tree chain table form to store all the fault classification identifier root nodes and the fault record branches positioned under the fault classification identifiers, wherein the fault classification identifiers are used for identifying the types of the equipment faults; the fault recording branch comprises at least one leaf node for recording the detail information of the current equipment fault, the detail information comprises fault information and maintenance information, and the leaf node is related to a parent node and a child node thereof through a node identifier. According to the scheme disclosed by the invention, the maintenance experience can be continuously expanded through the maintenance knowledge base, the fault of the medical equipment can be positioned in an auxiliary manner, the processing efficiency is greatly improved, and the manpower is saved.

Description

Knowledge base for storing equipment fault records and method and system for assisting in locating equipment fault by using knowledge base

Technical Field

The invention relates to the technical field of equipment maintenance management, in particular to a knowledge base for storing equipment fault records, and a method and a system for assisting in positioning equipment faults by using the knowledge base.

Background

Nowadays, the system complexity and the equipment precision of large medical equipment such as magnetic resonance imaging equipment, CT, digital X-ray machine and the like are higher and higher, and the daily use and maintenance of the equipment require professional technicians to operate the equipment. In particular, once the equipment fails, common operation technicians and hospital staff cannot deal with the equipment and can only rely on professional maintenance engineering to solve the problem.

After receiving the repair report from the hospital, the professional maintenance engineer needs to arrive at the equipment site for troubleshooting at the first time. In the troubleshooting process, the maintenance engineering finds out the failure reason of the equipment according to the error reporting information of the equipment at the moment and the self maintenance experience, and then orders corresponding accessories for replacement and debugging. If the equipment still can not work normally after the relevant accessories are replaced, the process is repeated to conduct troubleshooting again until the fault is solved.

It follows that existing repair methods rely heavily on the experience of the repair project. When meeting related maintenance problems, engineers with abundant experience can easily solve the problems at one time through troubleshooting, and young engineers with insufficient experience often need to troubleshoot for the final solution. Therefore, the traditional maintenance method which depends heavily on the experience of the maintenance engineer has high maintenance cost and can not ensure the maintenance efficiency.

Disclosure of Invention

In order to solve the above problems, an object of the present invention is to provide a knowledge database storing maintenance experience data for a maintenance engineer to learn and refer to, so as to accumulate and store maintenance experiences. The content in the database can be edited by experienced engineers, and is updated by combining with the actual maintenance condition, so that the reliability and the utilization value of the maintenance experience data in the knowledge base are ensured. For convenience of utilization, the constructed knowledge database can be designed to be based on the idea of branch management to perform data architecture, for example, the data architecture is divided according to different branches, problem fields and the like, so that the empirical data can be fully utilized to provide a learning platform for maintenance engineers, and a sharing and communication platform for experienced engineers is also provided.

Another objective of the present invention is to provide a repair suggestion for a fault through the repair knowledge database, so as to assist engineers in implementing a fault module, fault information, and related information beneficial to rapid repair of a device, which are quickly located by accumulating data based on actual faults and repair experiences, thereby reducing the disadvantages caused by the high dependence of the existing repair methods on the experience of the repair engineers, and greatly improving the efficiency.

According to a first aspect of the present invention, a knowledge base for storing device fault records comprises a root node determined by fault classification identifiers and fault record branches located under each fault classification identifier, and the knowledge base stores all fault classification identifier root nodes and fault record branches under the root nodes in the form of a tree-like linked list, wherein,

the fault classification identification is used for identifying the type of the equipment fault;

the fault recording branch comprises at least one leaf node for recording the detail information of the current equipment fault, the detail information comprises fault information and maintenance information, and the leaf node is related to a parent node and a child node thereof through a node identifier.

According to a second aspect of the present invention, there is provided a method of assisting in locating a fault in a device, comprising the steps of:

constructing a maintenance knowledge base, wherein the maintenance knowledge base is the knowledge base used for storing equipment fault records;

responding to a fault reporting instruction, and acquiring a first type of input parameters of equipment, wherein the first type of input parameters comprise fault description;

acquiring a matched fault type from a maintenance knowledge base according to the first type of input parameters;

and determining recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type.

According to a third aspect of the present invention, there is provided a system for assisting in locating a device fault, comprising:

the maintenance knowledge base is a knowledge base for storing equipment fault records;

the data acquisition module is used for acquiring a first type of input parameters of the reporting equipment;

and the fault positioning module is used for acquiring the matched fault type from the maintenance knowledge base according to the first-class input parameters and determining recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type.

According to a fourth aspect of the present invention, there is provided an electronic apparatus comprising: the computer-readable medium includes at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the steps of the above-described method.

According to a fifth aspect of the present invention, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method.

According to the method and the system provided by the invention, all maintenance experience data which are in line with the actual situation are fully utilized, the fault of the medical equipment can be positioned in an auxiliary mode, the problem that a large amount of human resources and time are consumed to accurately position the fault in the prior art is solved, the fault of the medical equipment is positioned intelligently, the maintenance experience is continuously expanded through the maintenance knowledge base, the processing efficiency is greatly improved, and the manpower is saved. And intelligent early warning, delivery and maintenance quotation can be realized, the application range is wide, the functions are diversified, and great convenience is provided for related workers.

Drawings

FIG. 1 is a data structure diagram of a knowledge base for storing device fault records according to an embodiment of the present invention;

FIG. 2 is a flow chart of a method for assisting in locating a device fault according to an embodiment of the present invention;

FIG. 3 is a flow chart of a method for assisting in locating a device fault according to yet another embodiment of the present invention;

FIG. 4 is a block diagram of a system for assisting in locating a device failure in accordance with an embodiment of the present invention;

FIG. 5 is a block diagram of a system for assisting in locating a device failure in accordance with yet another embodiment of the present invention;

FIG. 6 is a block diagram of a system for assisting in locating a device failure in accordance with another embodiment of the present invention;

FIG. 7 is a block diagram of a system for assisting in locating a device failure in accordance with yet another embodiment of the present invention;

FIG. 8 is a block diagram of an electronic device in accordance with an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

As used in this disclosure, "module," "device," "system," and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, or software in execution. In particular, for example, an element may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. Also, an application or script running on a server, or a server, may be an element. One or more elements may be in a process and/or thread of execution and an element may be localized on one computer and/or distributed between two or more computers and may be operated by various computer-readable media. The elements may also communicate by way of local and/or remote processes based on a signal having one or more data packets, e.g., from a data packet interacting with another element in a local system, distributed system, and/or across a network in the internet with other systems by way of the signal.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The present invention will be described in further detail with reference to the accompanying drawings.

In order to better serve the maintenance engineering by the maintenance experience data and reduce the dependence on the personal experience of engineers in the maintenance process of medical equipment, the knowledge base for storing the fault records of the equipment is provided, adopts the idea of branch management, classifies the faults of the medical equipment, and establishes branches according to the specific faults and the maintenance records, so that the management (such as storage and dynamic update) of the experience data is facilitated, and the experience data can better provide reference for new faults.

As a specific implementation example, as shown in fig. 1, a knowledge base provided in an embodiment of the present invention includes a root node a determined by a fault classification identifier and fault recording branches B located under each fault classification identifier, and the knowledge base stores all fault classification identifier root nodes and fault recording branches below the root node in a form of a tree-like linked list, where the fault classification identifier is used to identify a type to which an equipment fault belongs, the fault recording branch includes at least one leaf node C used to record details of the current equipment fault, the details include fault information and maintenance information, and the leaf node associates a parent node and a child node thereof through a node identifier.

Illustratively, by taking fault information including fault identification, equipment identification, fault time, fault description, and fault log and parameter characteristics, and detailed information including fault classification, fault classification identification, fault severity, fault cause, diagnostic test step, test check step, repair method, replacement spare part, spare part cost and labor hour, the node identification including parent node identification and child node identification as an example, in combination with a specific fault record, the following branch management knowledge base data structure may be formed:

the fault classification data structure is as follows:

and (3) fault classification identification: [ T001]

The fault log data structure is formed as follows:

a first failure:

fault label E001 (the fault record is unique number)

Equipment identification: d001 (unique equipment number)

Failure time: 2019-4-199:45

And (3) fault description: the user observes that a liquid helium pressure alarm lamp of the liquid helium monitor is on.

And (4) fault classification: liquid helium pressure anomaly (according to fault description, this fault is classified into liquid helium pressure anomaly)

And (3) fault classification identification: t001 (unique mark of fault classification)

Severity of failure: 4(0. suggestive information 1. trouble hidden trouble 2. affecting image quality 3. machine can not scan 4. serious trouble can be caused)

Equipment snapshot: after receiving the fault report of the user, the data acquisition box automatically acquires and stores the current data of the equipment, including fault logs, operation parameters and user operation records.

The failure reason is as follows: and checking a liquid helium pressure fluctuation curve, a helium compressor working log and a water cooling machine working log in the equipment snapshot. When the fault occurs, the change period of the liquid helium pressure is abnormal for a long time, and the descending speed is very slow after the liquid helium pressure rises. The cold head of the equipment has low working efficiency and needs to be replaced. From the helium compressor working log, the helium compressor of the equipment can work normally.

And (3) a diagnostic test step: and checking the work log of the helium compressor to see that the helium compressor works normally. And the water temperature and water flow data are checked, so that the water cooling machine can work normally. And looking up a liquid helium pressure change curve, finding that the pressure change period is abnormal for a long time, and after the liquid helium pressure rises, the falling speed is very slow, and determining that the cold head efficiency is reduced. And (4) conclusion: and replacing the cold head.

(1) Is the helium press operating properly? Is that

(2) Is water temperature and water flow normal? Is that

(3) Is cold head efficiency normal? Whether or not

And (4) conclusion: and replacing the cold head.

Fault log and parameter characterization: liquid helium pressure above threshold, liquid helium fluctuation curve anomaly, cold head efficiency below threshold (cold head efficiency can be calculated using prior art)

Testing and checking: and starting the system, operating for more than 24 hours, checking liquid helium data, and ensuring that all data are in a normal range.

The repairing method comprises the following steps: replacement cold head

Replacement of spare parts: cold head

Spare part cost: 10000 yuan

Working hours: 10 hours

And parent node identification: [ T001]

And (3) child node identification: []

And (4) failure II:

fault label E002 (the fault record is unique number)

Equipment identification: d002 (unique equipment number)

Failure time: 2019-4-188:45

The failure reason is as follows: and checking a liquid helium pressure fluctuation curve, a helium compressor working log and a water cooling machine working log in the equipment snapshot. When the fault occurs, the change period of the liquid helium pressure is normal, which shows that the cold head efficiency of the equipment is normal. And checking the work log of the helium press, and finding that the helium press is stopped, thereby causing the abnormal rise of the liquid helium pressure. And checking the log of the water cooler, wherein the water temperature is normal, and the water cooler works normally. Further checking the state of the helium compressor, and finding out that the power supply of the helium compressor fails, so that the helium compressor is stopped.

And (3) a diagnostic test step: and checking the work log of the helium compressor, and finding that the helium compressor is stopped. And checking the power state of the helium compressor, and finding out the power failure of the helium compressor. The helium press fuse was checked and found to be normal. And (4) conclusion: and replacing the power supply of the helium compressor.

(1) Is the helium press operating properly? Whether or not

(2) Is the helium press power supply operating properly? Whether or not

(3) Is the helium press power fuse normal? Is that

And (4) conclusion: and replacing the power supply of the helium compressor.

Fault log and parameter characterization: the liquid helium pressure is higher than the threshold value, the cold head efficiency is normal, and the helium compressor is stopped.

The repairing method comprises the following steps: and replacing the power supply of the helium compressor.

Replacement of spare parts: helium compressor power supply

Spare part cost: 5000 yuan

Working hours: 8 hours

And parent node identification: [ T001]

And (3) child node identification: [E004]

and (3) failure three:

fault label E003 (the only number of the fault record)

Equipment identification: d003 (unique equipment number)

Failure time: 2019-4-1710:45

The failure reason is as follows: and checking a liquid helium pressure fluctuation curve, a helium compressor working log and a water cooling machine working log in the equipment snapshot. When the fault occurs, the change period of the liquid helium pressure is normal, which shows that the cold head efficiency of the equipment is normal. And checking the work log of the helium press, and finding that the helium press is stopped, thereby causing the abnormal rise of the liquid helium pressure. And checking the log of the water cooler, wherein the water temperature is normal, and the water cooler works normally. Further checking the state of the helium compressor, and finding out that the power supply of the helium compressor fails, so that the helium compressor is stopped. Further inspection revealed that the helium press power fuse was blown.

And (3) a diagnostic test step: and checking the work log of the helium compressor, and finding that the helium compressor is stopped. And checking the power state of the helium compressor, and finding out the power failure of the helium compressor. The helium press fuse was inspected and found to be blown. And (4) conclusion: and replacing the power fuse of the helium press.

(1) Is the helium press operating properly? Whether or not

(2) Is the helium press power supply operating properly? Whether or not

(3) Is the helium press power fuse normal? Whether or not

And (4) conclusion: and replacing the power fuse of the helium press.

The repairing method comprises the following steps: helium press power fuse.

Replacement of spare parts: power fuse of helium press

Spare part cost: 10 Yuan

Working hours: 1 hour

And parent node identification: [ T001]

And (3) child node identification: [E003]

and (4) failure four:

fault label E004 (the fault record is unique number)

Equipment identification: d004 (unique device number)

Failure time: 2019-4-158:45

(1) Is the helium press operating properly? Whether or not

(2) Is the helium press power supply operating properly? Whether or not

(3) Is the helium press power fuse normal? Is that

And (4) conclusion: and replacing the power supply of the helium compressor.

Replacement of spare parts: helium compressor power supply

Spare part cost: 5000 yuan

Working hours: 6 hours

And parent node identification: [E002]

and (3) child node identification: [E005]

and (5) failure:

fault label E005 (the only number of the fault record)

Equipment identification: d005 (unique equipment number)

Failure time: 2019-4-1618:45

1) Is the helium press operating properly? Whether or not

2) Is the helium press power supply operating properly? Whether or not

3) Is the helium press power fuse normal? Is that

And (4) conclusion: and replacing the power supply of the helium compressor.

Replacement of spare parts: helium compressor power supply

Spare part cost: 5000 yuan

Working hours: 7 hours

And parent node identification: [E004]

and (3) child node identification: []

In particular, when data storage is performed, a fault data table can be established by an existing appropriate database, for example, a relational database (e.g., mysql), names of fault examples listed above (i.e., the foregoing description of each row colon is used as column names) are used as columns required by the table, and a "fault identifier" is set as a unique index of the fault data table, so that a knowledge base of the branch management data structure shown in fig. 1 can be formed.

Preferably, a faulty branch flag column may also be set for the knowledge base to perform branch management based on the faulty branch flag column. Specifically, the formation and update of the fault recording branch may be set to be determined based on a change in the content of the fault branch flag column, which may be set to include fault severity, fault cause, diagnostic test steps, fault log and parameter characteristics, test verification steps, repair methods, and replacement spare parts. In specific practice, a judgment is performed according to the received newly input fault record content (the newly input fault record content is generally based on a leaf node of a certain fault record branch, and therefore, the newly input content is compared with the content of a fault branch mark column of the leaf node based on the newly input fault record content during the judgment), and as long as the content of any fault branch mark column is judged to be modified, a new branch needs to be generated from the fault record; if the content of the fault branch mark column is not changed at all, the fault record is continuously added to the original branch. Therefore, in specific application, the content of the recommended branch node can be output as a recommendation strategy, and an engineer is allowed to modify the branch node according to a specific maintenance condition, so that a new branch can be formed or the number of leaf nodes of an original branch can be increased based on the modification of the content of the recommended branch node according to whether the modified content is the content of the fault branch mark column, and thus, the longer the number of the leaf nodes of the branch is, the more times the maintenance strategy of the node is adopted is indicated, the more times the leaf nodes of the branch are quoted can be effectively represented, and the efficiency and the accuracy of auxiliary fault location are further improved; meanwhile, the user is allowed to modify the content of the branch node according to the specific maintenance condition, the maintenance knowledge base can be dynamically updated, and the updated content is based on the actual condition and has high reference value.

Fig. 2 schematically shows a flowchart of a method for assisting in locating a device fault according to an embodiment of the present invention, and as shown in fig. 2, taking the implementation of the assisted locating device fault by using the above knowledge base for storing device fault records as an example, the present embodiment includes the following steps:

step S101: constructing a maintenance knowledge base, wherein the constructed maintenance knowledge base is the knowledge base for storing the device fault records, which can be implemented by a mysql database, and the specific implementation manner comprises establishing fault data tables in the mysql database, taking the names of the fault examples listed above (namely, the description in front of each row colon as the column name) as the columns required by the tables, wherein "fault identification" is set as the unique index of the fault data tables, so that a corresponding fault data table can be established for each fault record, an association relationship is established between each fault data table, namely between each fault record through a parent node identification and a child node identification, thereby forming a fault classification identification as a root node, each fault classification identification is associated with a plurality of fault records, and the associated fault records are connected in series through the node identifications to form a fault record branch, thereby, a maintenance knowledge base based on branch management can be formed.

Step S102: and responding to the fault reporting instruction, and acquiring a first type of input parameters of the equipment, wherein the first type of input parameters comprise fault description. The fault reporting instruction is an operation instruction for reporting the fault when the user finds the equipment fault, and can be manually issued through a user interface by the user, when the problem of the equipment fault is encountered, relevant working personnel in a hospital can send the fault reporting instruction, and simultaneously, the fault condition of the fault equipment is simply described and sent out. In response to the instruction, a user-generated description of the fault is received.

Step S103: and acquiring the matched fault type from the maintenance knowledge base according to the first type of input parameters.

When receiving a repair report (a fault report instruction), classifying repair report phenomena, wherein the classification method can perform semantic analysis through the acquired fault description, and the semantic analysis method can be realized by extracting keywords according to the prior art, so that the keywords are determined to be matched with the content of a knowledge base, and the matched fault types are positioned.

In other embodiments, the fault description keywords can be manually selected and reported when the user reports the fault; the fault classification can be matched and positioned by automatically identifying fault information and abnormal parameters (which are inconsistent with the threshold value of the stored standard parameters) by automatically acquiring typical fault reports in the fault log in combination with the second type of input parameters of the equipment (in this case, the equipment fault can be automatically found and positioned, and automatic dispatching and/or real-time early warning can be further realized); and determining fault classification by combining the latest fault log of the called reporting equipment and related parameter data. The classification methods can be used simultaneously, and the embodiment of the invention is not limited to this, as long as the fault classification can be determined by effective matching.

Illustratively, for example: newly received fault is

Fault label E006 (the fault record is unique number)

Equipment identification: d006 (unique equipment number)

Failure time: 2019-4-2418:45

The fault classification in the repair repository is matched according to the fault description, and as an example of the fault stored in the repository above, the fault classification can be determined as T001 by this matching.

Step S104: and determining recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type.

After matching the fault classification in the fault database according to the fault description, the recommended maintenance strategy can be determined according to the specific situation of the fault record branch corresponding to the fault type. Specifically, the recommended maintenance strategy may be determined according to the number of leaf nodes included in the fault record branch, and the maintenance cost and the labor hour corresponding to the leaf nodes.

Illustratively, the branch corresponding to T001 is searched in the fault database, and the longest branch under the branch is found to be E002- - > E004- - > E005, because the longest branch identifies the case with the highest occurrence probability in the type of fault and also identifies the case with the largest number of references. The node E005 in the longest branch may be selected to be displayed as the recommended repair strategy on the repair advice page (i.e., the one with the highest number of references as the better recommended strategy). And judging the reason of the fault by an engineer according to the maintenance suggestion by combining the actual condition of the fault. If the engineer determines that the current failure is identical to E005, the repair is completed according to the content of E005, and the parent node of E006 is defined as E005. If the engineer considers that the current fault is not consistent with the fault of E005, the engineer may select to obtain the branch node with the second branch length, as shown in the figure, the branch nodes with the second branch lengths of E001 and E003. If the branch lengths are the same, the branch that preferentially displays the shortest average repair man-hour or the lowest repair cost may be selected. If the engineer considers that the current fault is inconsistent with E003, the engineer is displayed with a branch node E001 with the third branch length. By analogy, traversing all possible branches, and still not finding the corresponding branch, or an engineer considers that the maintenance is different from the previous maintenance of the same type of fault, a new branch is newly built in the T001 type of fault, and the father node of the E006 is defined as T001, so that a new fault record branch can be formed according to the actual maintenance record after the maintenance, and the content of the maintenance knowledge base is enriched.

Through the data storage and the maintenance suggestion recommendation process, the automatic accumulation, the automatic iteration and the automatic recommendation of the maintenance suggestions of the maintenance knowledge base can be completed, good maintenance experience can be fully utilized, experienced individual engineers can be relied on, and the fault positioning and maintenance efficiency is greatly improved.

In order to expand and promote the use of the repair knowledge base, in a preferred embodiment, the repair knowledge base can be dynamically updated, and an engineer can edit the repair knowledge base according to the actual situation of the current repair, modify unreasonable contents, and supplement missing contents. The modification of the maintenance knowledge base adopts a data structure of branch management, namely, each engineer generates a new branch (namely, a new branch is generated when the content of the fault branch marking column changes) or generates a new leaf node (when the content of the fault branch marking column does not change), and the engineer can choose to continue modification based on the own branch or pull the latest content from the branches of other engineers or from the main branch or modify based on the node where the recommended fault record content is located during each editing. Thus, over time, a detailed and accurate repair knowledge base of various common problems may be developed. And the error report of the equipment fault log can be corresponding to the actual fault.

According to the method provided by the embodiment, the recommended maintenance strategy can be generated through the maintenance knowledge base which is established by a plurality of engineers and has experience data support, the maintenance success rate of the equipment is effectively improved, the human resources are greatly saved, the practicability is high, the knowledge base can be updated in real time and continuously expanded, and the utilization rate is high.

Fig. 3 schematically shows a flowchart of a method for assisting in locating a device fault according to another embodiment of the present invention, and the method of this embodiment is different from the embodiment shown in fig. 2 in that the method of this embodiment determines the type of the fault not based on a reporting instruction, but based on a second type of input parameters, such as a fault log and parameter characteristics, which are automatically collected in real time, so that functions such as automatic dispatch, real-time warning, and the like can be implemented, and full-automatic monitoring is implemented. As shown in fig. 3, the method comprises the steps of:

step S201: a repair knowledge base is constructed, and the implementation manner thereof can refer to step S101.

Step S202: and automatically acquiring a second type of input parameters of the target equipment, wherein the second type of input parameters comprise fault logs and parameter characteristics. The method can be specifically realized as follows: the fault log of the target equipment is collected in real time, the obtaining mode can be timed through a data collecting device, the equipment log of the target equipment is obtained every 15 minutes exemplarily, and the fault log is obtained according to abnormal parameters in the equipment log. The data acquisition device is an acquisition device in the prior art, and log information of equipment can be acquired by placing the data acquisition device and the medical equipment in the same network segment.

Step S203: and determining the matched fault type from the maintenance knowledge base according to the second type of input parameters.

When a new device log is acquired, the log content is firstly analyzed, semantic analysis can be performed on the acquired fault log, the semantic analysis method can be realized by referring to the extracted keywords in the prior art, so that the determined keywords are matched with the content of a knowledge base, and the matched fault type is positioned.

Step S204: and determining recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type. The implementation thereof may refer to step S104.

The fault is analyzed by automatically acquiring the device log, the matched information such as the fault type and the like can be pushed to an engineer in real time to realize automatic dispatching, so that the engineer can purchase spare parts in advance according to given maintenance parameters after the fault is analyzed and confirmed through a remote maintenance tool, and then the spare parts are checked on site to repair the fault in time.

In the preferred embodiment, matching failure information is generated according to the failure log and the maintenance knowledge base, wherein the failure information comprises failure reasons, labor hour cost, spare part quotation and the like, and the failure information is pushed to hospital users, so that the users can know the possible reasons of the failure, the spare part quotation and the labor hour cost quotation, and count to generate a budget table, thereby realizing the function of automatic quotation. Thus, the hospital user can purchase and purchase maintenance service by placing orders online according to the quotation table and after the quotation table is confirmed by engineers.

In the preferred embodiment, matching is further performed according to the fault log and the maintenance knowledge base to generate matching fault information, and an early warning message is generated according to the matching fault information and output to realize real-time early warning. The early warning message is output according to the severity of the fault, if the severity of the fault is high, the user needs to take measures immediately to avoid further loss, the early warning message immediately sends a message to relevant managers in a hospital in a mode of WeChat push and the like, and informs the managers of the measures which need to be taken immediately.

According to the method provided by the embodiment, the operations of early warning, dispatching, automatic quotation and the like on equipment faults by utilizing the maintenance database can be intelligently realized, convenience is provided for users in a diversified manner, manpower resources are greatly saved, and the efficiency is improved.

Fig. 4 schematically shows a block diagram of a system for assisting in locating a device failure according to an embodiment of the present invention, as shown in fig. 4,

the system for assisting in locating a device failure comprises: the system comprises a maintenance knowledge base 1, a data acquisition module 2 and a fault positioning module 3.

The repair repository 1 is used for storing fault records of the equipment, and is implemented as the repository of the branch management structure, and the specific construction mode can refer to the method part.

The data obtaining module 2 is configured to receive a fault reporting instruction, and obtain a first type of input parameter of a reporting device, which may be a fault description specifically.

The fault location module 3 is configured to determine an adapted fault type from the maintenance knowledge base 1 according to the fault description of the reporting device, and generate a recommended maintenance policy output according to the fault type and a condition of a fault record branch corresponding to the fault type, where the determination of the recommended maintenance policy according to the condition of the fault record branch may be based on the number of leaf nodes in the branch, that is, the length of the branch, or based on a cost condition required by a maintenance policy corresponding to a corresponding node in the branch, and the like, and the description of the method part may be specifically referred to, and details of the method part are not repeated here.

In a preferred embodiment, the system further comprises an update module 11 for dynamically updating the service repository 1 according to branches, in a manner referred to above in the method section.

According to the system that this embodiment provided, not only can build the maintenance knowledge base that the data is diversified and the coverage is wide, can also generate the maintenance strategy of recommending through the maintenance knowledge base that has the data support that a plurality of engineers established, the effectual maintenance success rate that has improved equipment, great saving manpower resources, the practicality is high to this knowledge base can be updated in real time, constantly expands, has very high utilization ratio.

Fig. 5 schematically shows a block diagram of a system for assisting in locating a device failure according to yet another embodiment of the present invention, as shown in fig. 5,

the system also comprises an automatic diagnosis module which is used for automatically acquiring second-class input parameters of the target equipment, wherein the second-class input parameters comprise fault logs and parameter characteristics, and the second-class input parameters of the target equipment are automatically acquired by adopting a device with a data acquisition function and being placed in the same network segment with the medical equipment, so that log information of the equipment can be acquired in real time. In this embodiment, the fault location module is further configured to obtain a matched fault type from the maintenance knowledge base according to the second type of input parameter, and determine a recommended maintenance policy output according to a fault record branch condition corresponding to the matched fault type.

As a preferred embodiment, the fault location module may be implemented to include a quotation unit 4, configured to obtain maintenance quotation information from the maintenance knowledge base 1 according to the type of the located fault, and generate a maintenance quotation information output display, where the maintenance quotation information may be implemented as a quotation budget table, which includes possible reasons of the fault, a spare part quotation and a labor cost quotation, and is generated by counting the possible reasons of the fault and the corresponding spare part quotation and labor cost quotation, so as to implement an automatic quotation function. Therefore, the hospital user can acquire the possible reasons and the cost of the fault according to the budget quotation table, and after the hospital user really needs an engineer, the hospital user can purchase and buy the maintenance service by ordering on line.

In another embodiment, as shown in fig. 6, the fault location module may also be implemented to include an automatic dispatch unit 5, which is configured to obtain the matched maintenance parameters (e.g., fault reason, test and verification step, repair method, replacement of spare parts, etc.) from the maintenance knowledge base according to the located fault type, and output the parameters, so that an engineer may purchase the spare parts in advance according to the given maintenance parameters after analyzing and confirming the fault through a remote maintenance tool, and then go to the site for troubleshooting, and repair the fault in time.

In yet another embodiment, as shown in fig. 7, the fault location module may also be implemented to include an early warning unit 6, which is configured to generate an early warning message output display according to the severity of the fault corresponding to the located fault type. The early warning message is output according to the severity of the fault, if the severity of the fault is high, the user needs to take measures immediately to avoid further loss, the early warning message immediately sends a message to relevant managers in a hospital in a mode of WeChat push and the like, and informs the managers of the measures which need to be taken immediately.

In other embodiments, the quotation unit 4, the automatic dispatch unit 5 and the early warning unit 6 of the system are not limited to the above implementation manner, and may be implemented as a combination system of two or three of the three.

Fig. 8 is a schematic diagram of a hardware structure of an electronic device for assisting a method for locating a device fault according to an embodiment of the present invention, as shown in fig. 8, the electronic device includes:

one or more processors 310 and a memory 320, with one processor 310 being illustrated in FIG. 8.

The apparatus performing the method of assisting in locating a device failure may further include: an input device 330 and an output device 340.

The processor 310, the memory 320, the input device 330, and the output device 340 may be connected by a bus or other means, as exemplified by the bus connection in fig. 8.

The memory 320 is a non-volatile computer-readable storage medium and can be used for storing non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the method for assisting in locating a device failure in the embodiments of the present application. The processor 310 executes various functional applications and data processing of the server by executing the nonvolatile software programs, instructions and modules stored in the memory 320, so as to implement the method for assisting in locating the equipment failure according to the above method embodiment.

The memory 320 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created from use of the system for assisting in locating device failure, and the like. Further, the memory 320 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 320 may optionally include memory located remotely from processor 310, which may be connected to a system that assists in locating device faults via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 330 may receive input numeric or character information and generate signals related to user settings and function control of the device behavior contrastive analysis device among multiple devices. The output device 340 may include a display device such as a display screen.

The one or more modules described above are stored in the memory 320 and, when executed by the one or more processors 310, perform a method of assisting in locating a device failure in any of the method embodiments described above.

The product can execute the method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the methods provided in the embodiments of the present application.

The electronic device of the embodiments of the present application exists in various forms, including but not limited to:

(1) mobile communication devices, which are characterized by mobile communication capabilities and are primarily targeted at providing voice and data communications. Such terminals include smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.

(2) The ultra-mobile personal computer equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include PDA, MID, and UMPC devices, such as ipads.

(3) The server is similar to a general computer architecture, but has higher requirements on processing capability, stability, reliability, safety, expandability, manageability and the like because of the need of providing highly reliable services.

(4) And other electronic devices with data interaction functions.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a general hardware platform, and certainly can also be implemented by hardware. Based on such understanding, the above technical solutions substantially or contributing to the related art may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. The knowledge base for storing the fault records of the equipment is characterized by comprising root nodes determined by fault classification identifiers and fault record branches positioned under the fault classification identifiers, and the knowledge base adopts a tree chain table form to store all the fault classification identifier root nodes and the fault record branches positioned under the fault classification identifiers, wherein,

the fault recording branch comprises at least one leaf node for recording detail information of the current equipment fault, the detail information comprises fault information and maintenance information, and the leaf node is associated with a parent node and a child node of the leaf node through a node identifier.

2. The knowledge base of claim 1, wherein the fault information comprises fault identification, equipment identification, fault time, fault description, fault log and parameter characteristics, the detail information comprises fault classification, fault classification identification, fault severity, fault reason, diagnostic test step, test check step, repair method, replacement spare parts, spare part cost and labor hour, and the node identification comprises father node identification and son node identification.

3. The knowledge base of claim 2, wherein the formation and updating of the fault record branch is determined based on changes in the contents of a fault branch flag column, the fault branch flag column including fault severity, fault cause, diagnostic test steps, fault log and parameter characteristics, test verification steps, repair methods, and replacement spare parts.

4. The method for assisting in locating the equipment fault is characterized by comprising the following steps:

constructing a maintenance knowledge base, wherein the maintenance knowledge base is the knowledge base for storing equipment fault records in any one of claims 1 to 3;

acquiring a matched fault type from the maintenance knowledge base according to the first type of input parameters;

5. The method of claim 4, wherein determining the recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type comprises determining the recommended maintenance strategy according to the number of leaf nodes contained in the fault record branch, and maintenance cost and working hours corresponding to the leaf nodes.

6. The method of claim 5, further comprising

Dynamically updating the repair knowledge base, which is implemented as:

and receiving a modification instruction of the output recommended maintenance strategy from the user, and forming an updated fault record branch according to the modification content.

7. The method according to any one of claims 4 to 6, further comprising the steps of:

automatically acquiring a second type of input parameters of the target equipment, wherein the second type of input parameters comprise fault logs and parameter characteristics;

and determining the matched fault type from the maintenance knowledge base according to the second type of input parameters, and determining recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type.

8. A system for assisting in locating a device fault, comprising:

a repair repository, the repair repository being the repository for storing equipment fault records of any of claims 1 to 3;

9. The system of claim 8, further comprising:

and the updating module is used for forming updated fault record branch storage according to the modification content of the output recommended maintenance strategy by the user.

10. The system of claim 8, further comprising:

the automatic diagnosis module is used for automatically acquiring a second type of input parameters of the target equipment, and the second type of input parameters comprise fault logs and parameter characteristics;

and the fault positioning module is also used for acquiring the matched fault type from the maintenance knowledge base according to the second type of input parameters and determining recommended maintenance strategy output according to the fault record branch condition corresponding to the matched fault type.