CN108885724A - Information processing unit, information processing method and message handling program - Google Patents
Information processing unit, information processing method and message handling program Download PDFInfo
- Publication number
- CN108885724A CN108885724A CN201680083889.1A CN201680083889A CN108885724A CN 108885724 A CN108885724 A CN 108885724A CN 201680083889 A CN201680083889 A CN 201680083889A CN 108885724 A CN108885724 A CN 108885724A
- Authority
- CN
- China
- Prior art keywords
- fault
- maintenance person
- similar
- information
- disposition
- 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.)
- Granted
Links
- 230000010365 information processing Effects 0.000 title claims description 14
- 238000003672 processing method Methods 0.000 title claims description 4
- 238000012423 maintenance Methods 0.000 claims abstract description 230
- 238000000605 extraction Methods 0.000 claims abstract description 27
- 239000000284 extract Substances 0.000 claims abstract description 11
- 238000012545 processing Methods 0.000 claims description 12
- 238000009825 accumulation Methods 0.000 description 34
- 238000004891 communication Methods 0.000 description 25
- 238000000034 method Methods 0.000 description 17
- 230000004888 barrier function Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 238000012797 qualification Methods 0.000 description 2
- TVEXGJYMHHTVKP-UHFFFAOYSA-N 6-oxabicyclo[3.2.1]oct-3-en-7-one Chemical compound C1C2C(=O)OC1C=CC2 TVEXGJYMHHTVKP-UHFFFAOYSA-N 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000004092 self-diagnosis Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- 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
-
- 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
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- 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
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Tourism & Hospitality (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Maintenance And Inspection Apparatuses For Elevators (AREA)
Abstract
Similar fault history determination unit (5) from describe faulty situation occurred respectively, in the disposition of failure and multiple fault history information of the maintenance person disposed, extract the similar fault historical information for describing and having and being appointed as 2 or more fault history information of the similar situation occurred of the situation occurred of extraction conditions by maintenance person (200) as 2 or more, from 2 or more extracted similar fault historical informations, extracting to describe has the similar fault historical information of maintenance person (200) as maintenance person's fault history information.Display priority determination unit (8) is according to each similar fault historical information, the similarity in similar fault historical information between the disposition described and the disposition described in maintenance person's fault history information is calculated, higher priority is set for the similar fault historical information lower with related similarity is disposed.The high similar fault historical information of the preferential output priority in similar fault history output section (9).
Description
Technical field
The present invention relates to provide the technology of information related with past equipment fault to maintenance person.
Background technique
In patent document 1, disclose according to the difficulty of the degree of being familiar with of the maintenance person of machinery equipment and countermeasure come
The method for selecting the countermeasure of the failure shown to maintenance person.In the maintenance system of patent document 1, specified in advance for true
Determine the fault code and countermeasure corresponding with fault code of defect content.Maintenance person is set in countermeasure to implement
Degree of being familiar with.Degree of being familiar with is calculated according to the value related with ability such as the experience year of maintenance person or the time that accumulates experience, is remembered
It records in the portable terminal possessed by maintenance person.Machinery equipment is when recognizing failure by self diagnosis etc., by fault code
It is stored in the storage region in machinery equipment.In machinery equipment of the maintenance person close to failure, machinery equipment and maintenance person institute
The portable terminal having is communicated, the degree of being familiar with of the machinery equipment person of being maintained.If the degree of being familiar with of maintenance person is and failure
More than the degree of being familiar with set in the corresponding countermeasure of code, then machinery equipment is shown in the portable terminal of maintenance person answers other side
Method.In the case where the degree of being familiar with of maintenance person is lower than the degree of being familiar with set in countermeasure, machinery equipment is in the portable of maintenance person
Such countermeasure that makes a request for help is shown in terminal.In addition, being not only maintenance person's in the maintenance system of patent document 1
Degree of being familiar with, additionally it is possible to which qualification or tool required for countermeasure are implemented in setting, can be only to these qualifications or tool
Maintenance person shows countermeasure.
In patent document 2, it discloses and is provided according to the proficiency of the maintenance person of operation robot system to maintenance person
The technology of optimal upkeep operation step.Proficiency be maintenance person according to maintenance person's past experience the index of self judgment.
In the patent literature, the lower maintenance person of proficiency uses using part replacement as the picture of the operation form of main body, proficiency
Higher maintenance person use carried out after the investigation for implementing to determine trouble location part replacement, by operation of the investigation as main body
The picture of form.
Existing technical literature
Patent document
Patent document 1：Japanese Unexamined Patent Publication 2008-257433 bulletin
Patent document 2：Japanese Unexamined Patent Publication 2002-154085 bulletin
Summary of the invention
Subject to be solved by the invention
In the prior art, degree of being familiar with or proficiency are determined according to the experience year of maintenance person or accumulation activity duration, because
This, shows identical disposition to degree of being familiar with or the identical maintenance person of proficiency.Each maintenance person is for the knowledge and experience of failure
Different, still, in the prior art, uniformly select the disposition prompted to maintenance person.In order to realize that the early stage of failure solves, with
Maintenance person's past experience is crossed and the disposition being proficient in is compared, and the unknown disposition not lived through in the past to maintenance person prompting maintenance person is that have
Effect, still, in the prior art, there is the appropriate disposition that no normal direction maintenance person prompt reflects the knowledge and experience of maintenance person
Such project.
It is a primary object of the present invention to solve this project, it is therefore intended that according to the knowledge and experience of maintenance person, according to
Each maintenance person prompts disposition appropriate.
Means for solving the problems
Information processing unit of the invention has：Extraction unit, described in describing faulty situation occurred respectively, being directed to
The disposition of failure and carried out in multiple fault history information of maintenance person of the disposition, extract describe have with by arbitrarily safeguarding
Member is appointed as 2 or more fault history information of the similar situation occurred of situation occurred of extraction conditions as 2 or more
Similar fault historical information extracts description and specifies institute from described 2 or more extracted similar fault historical informations
The similar fault historical information of the maintenance person of extraction conditions is stated as maintenance person's fault history information；Priority level initializing portion, is pressed
According to each similar fault historical information, calculates the disposition described in similar fault historical information and maintenance person's fault history is believed
The similarity between disposition described in breath, more for the similar fault historical information setting lower with related similarity is disposed
High priority；And output section, the high similar fault historical information of preferential output priority.
Invention effect
In the present invention, the similarity between disposition preferentially crossed to maintenance person's prompt and maintenance person's past experience is lower
Disposition.According to the invention it is thus possible to preferentially to the unversed unknown disposition of maintenance person prompting maintenance person, it can be to maintenance person
Prompt reflects the appropriate disposition of the knowledge and experience of maintenance person.
Detailed description of the invention
Fig. 1 is the figure for showing the functional structure example of elevator similar fault searching system of embodiment 1.
Fig. 2 is the figure for showing the example of fault history information of embodiment 1.
Fig. 3 is the figure for showing the example of similar fault historical information of embodiment 1.
Fig. 4 is the figure for showing the example of maintenance person's fault history information of embodiment 1.
Fig. 5 is the flow chart of the maintenance person authentication department for showing embodiment 1 and the action example of fault state acquisition unit.
Fig. 6 is the flow chart for showing the action example of similar fault history determination unit of embodiment 1.
Fig. 7 is the flow chart for showing the action example of display priority determination unit of embodiment 1.
Fig. 8 is the flow chart for showing the action example of display priority determination unit of embodiment 1.
Fig. 9 is the flow chart for showing the action example of similar fault history output section of embodiment 1.
Figure 10 is the flow chart for showing the example of vectorization processing of embodiment 1.
Figure 11 is the figure for showing the example of fault history information of embodiment 5.
Figure 12 is the figure for showing the example of Deal with Time information of embodiment 5.
Figure 13 is the figure for showing the hardware configuration example of elevator similar fault searching system of Embodiments 1 to 5.
Specific embodiment
Embodiment 1
* * structure illustrates * * *
Fig. 1 shows the functional structure example of the elevator similar fault searching system 100 of present embodiment.The similar event of elevator
Barrier searching system 100 is the example of information processing unit.Also, the movement carried out by elevator similar fault searching system 100
It is the example of information processing method and message handling program.
Elevator similar fault searching system 100 stores the fault history information for describing the fault history for having elevator, mentions
The fault history information to match with the knowledge and experience of maintenance person is taken, the fault history information extracted to maintenance person.
In the following, the example as maintenance object-based device, is illustrated elevator, still, maintenance object-based device is not limited to
Elevator.
Communication terminal 1 is the communication equipments such as computer or smart phone.Maintenance person 200 uses the access lifting of communication terminal 1
Machine similar fault searching system 100.
More specifically, maintenance person 200 logs in elevator similar fault searching system 100 using communication terminal 1.Also,
Maintenance person 200 sends retrieval request to elevator similar fault searching system 100 using communication terminal 1.Communication terminal 1 is from lifting
Machine similar fault searching system 100 receives the fault history information extracted by elevator similar fault searching system 100, display
The fault history information received.
Elevator similar fault searching system 100 is the computer with hardware configuration shown in Figure 13.Shown in Figure 13
Hardware describes in detail below.
In the following, being illustrated to the functional structure of elevator similar fault searching system 100 shown in FIG. 1.
Maintenance person authentication department 2 receives logging request from communication terminal 1.Then, maintenance person authentication department 2 asks to communication terminal 1
Ask the input of maintenance person ID (Identifier) and password of maintenance person 200.In turn, maintenance person authentication department 2 connects from communication terminal 1
Maintenance person ID and password that maintenance person 200 inputs are received, to the maintenance person ID and password and maintenance person's information accumulation unit 10 received
The maintenance person ID and password of middle storage are checked.Then, in the maintenance person ID and password that are received from communication terminal 1 and maintenance
Under the maintenance person ID and password unanimous circumstances that store in member's information accumulation unit 10,2 permit maintenance person 200 of maintenance person authentication department is stepped on
Record elevator similar fault searching system 100.Maintenance person authentication department 2 is after permit maintenance person 200 logs in, by maintenance person's 200
Maintenance person ID is output to fault state acquisition unit 3.
The situation occurred of the acquirement of fault state acquisition unit 3 maintenance person ID and the failure as extraction conditions.By maintenance person
After the license of authentication department 2 logs in, maintenance person 200 sends retrieval to elevator similar fault searching system 100 using communication terminal 1 and asks
It asks.Include situation occurred (hereinafter referred to as situation or fault state) mentioning as fault history information of failure in retrieval request
Take condition.Fault state acquisition unit 3 receives retrieval request, and the generation as extraction conditions is taken out from the retrieval request received
Situation notifies the maintenance person ID and situation occurred that notify from maintenance person authentication department 2 to similar fault history determination unit 5.
Similar fault history determination unit 5 extracts 2 or more fault history information as 2 or more similar fault history
Information, 2 or more fault history information description have and are appointed as the situation occurred of extraction conditions (i.e. from failure by maintenance person
The situation occurred that situation acquisition unit 3 notifies) similar situation occurred.Also, similar fault history determination unit 5 is from 2 extracted
In a above similar fault historical information, extracting to describe has the maintenance person ID of maintenance person 200 (i.e. from fault state acquisition unit 3
The maintenance person ID of notice) similar fault historical information as maintenance person's fault history information.
Then, similar fault historical information is stored in similar fault history accumulation unit 6 by similar fault history determination unit 5
In, also, maintenance person's fault history is stored in maintenance person's fault history accumulation unit 7.
In addition, similar fault history determination unit 5 is the example of extraction unit.Also, it is carried out by similar fault history determination unit 5
Movement be extraction process example.
Fault history accumulation unit 4 accumulates fault history information.
Fig. 2 shows the examples of the fault history information of present embodiment.Each row of Fig. 2 is fault history information.
As shown in Fig. 2, fault history information is sent out by fault history ID, type, situation, disposition, responsible maintenance person ID, failure
Birthday etc. is constituted.In this way, describing the attribute for having the failure occurred in the past in fault history information.
Fault history ID is the ID for uniquely determining failure.
Type is the type that the elevator of failure has occurred.
Situation is the situation occurred of the failure of elevator, can freely be described by maintenance person.
Disposition is the disposition that maintenance person is directed to that failure carries out, and can freely be described by maintenance person.
It is responsible for the ID that maintenance person ID is the maintenance person disposed to failure.
Failure generation day is the date that failure has occurred.In Fig. 2, describes failure and day occurs, but it is also possible to remember
State failure date time (comprising the moment).
Similar fault history accumulation unit 6 temporarily keeps the similar fault history extracted by similar fault history determination unit 5
Information.Similar fault historical information is output to display priority determination unit 8 by similar fault history accumulation unit 6.
Maintenance person's fault history accumulation unit 7 temporarily keeps the maintenance person's failure extracted by similar fault history determination unit 5
Historical information.Maintenance person's fault history information is output to display priority determination unit 8 by maintenance person's fault history accumulation unit 7.
Display priority determination unit 8 obtains similar fault historical information from similar fault history accumulation unit 6, from maintenance person's event
Hinder history accumulation unit 7 and obtains maintenance person's fault history information.Then, display priority determination unit 8 is by similar fault historical information
It is checked with maintenance person's fault history information, sets priority in similar fault historical information.More specifically, it shows excellent
First grade determination unit 8 calculates the disposition described in similar fault historical information and maintenance person according to each similar fault historical information
The similarity between disposition described in fault history information, for the similar fault history lower with related similarity is disposed
The higher priority of information setting.
Also, display priority determination unit 8 calculates in similar fault historical information according to each similar fault historical information
The similarity of the situation described in the situation of description and maintenance person's fault history information, for similarity related with situation
Higher similar fault historical information sets higher priority.
Display priority determination unit 8 is the example in priority level initializing portion.Also, it is carried out by display priority determination unit 8
Movement is the example of priority level initializing processing.
The higher similar fault of the priority set by display priority determination unit 8 is gone through in similar fault history output section 9
History information is preferentially output to communication terminal 1.
Similar fault history output section 9 is the example of output section.Also, it is carried out by similar fault history output section 9 dynamic
Work is the example of output processing.
The maintenance person ID and password of the accumulation maintenance person of maintenance person's information accumulation unit 10.
* * movement illustrates * * *
Then, using the flow chart of Fig. 5~Fig. 9 to the dynamic of the elevator similar fault searching system 100 of present embodiment
It is illustrated as example.
Fig. 5 is the flow chart for showing the action example of maintenance person authentication department 2 and fault state acquisition unit 3.Fig. 6 be show it is similar
The flow chart of the action example of fault history determination unit 5.Fig. 7 and Fig. 8 is the process for showing the action example of display priority determination unit 8
Figure.Fig. 9 is the flow chart for showing the action example of similar fault history output section 9.
Firstly, maintenance person 200 accesses maintenance person authentication department 2 using communication terminal 1, to log in the retrieval of elevator similar fault
System 100.
Then, maintenance person authentication department 2 sends to communication terminal 1 for making maintenance person 200 input maintenance person ID and password
Input picture.
Then, maintenance person authentication department 2 receives the maintenance person ID and password (step that maintenance person 200 inputs from communication terminal 1
S10)。
Maintenance person authentication department 2 investigates whether the maintenance person ID received and password are maintenance person ID and password appropriate (step
Rapid S11).That is, maintenance person authentication department 2 investigate the maintenance person ID that receives and password whether with deposited in maintenance person's information accumulation unit 10
The maintenance person ID of storage is consistent with password.The case where the maintenance person ID and password received is maintenance person ID and password appropriate
Under, 2 permit maintenance person 200 of maintenance person authentication department logs in elevator similar fault searching system 100.Also, maintenance person authentication department 2
The maintenance person ID of maintenance person 200 is output to fault state acquisition unit 3.
In the case where the maintenance person ID and password received is not maintenance person ID and password appropriate, again eventually to communication
End 1 sends input picture, receives the maintenance person ID and password that maintenance person 200 inputs from communication terminal 1 again.
After permitting to log in elevator similar fault searching system 100 by maintenance person authentication department 2, maintenance person 200 uses logical
Believe that terminal 1 sends retrieval request to elevator similar fault searching system 100.As described above, including failure in retrieval request
Extraction conditions of the situation occurred as fault history information.Fault state acquisition unit 3 receives retrieval request from communication terminal 1
(step S20).Fault state acquisition unit 3 takes out the situation occurred as extraction conditions from the retrieval request received, will be from
The maintenance person ID and situation occurred that maintenance person authentication department 2 notifies are notified to similar fault history determination unit 5.
Similar fault history determination unit 5 calculates the situation notified from fault state acquisition unit 3 and (is specified by maintenance person 200
Situation) similarity with the situation of each fault history information stored in fault history accumulation unit 4, extract describe have with from failure
The fault history information for the similar situation of situation that situation acquisition unit 3 notifies is as similar fault historical information (step S30~step
Rapid S40).
More specifically, the sentence for the situation specified by maintenance person 200 is converted to vector by similar fault history determination unit 5
(step S30).Then, similar fault history determination unit 5 reads fault history information from fault history accumulation unit 4 one by one, until
Until the whole fault history information of reading (step S31, step S32).Then, similar fault history determination unit 5 will be acquired
The situation described in i-th of fault history information is converted to vector (step S33).Then, similar fault history determination unit 5 uses
Vector obtained in vector sum step S33 obtained in step S30, calculate in i-th of fault history information the situation that describes with
Similarity (step S34) between the situation that fault state acquisition unit 3 notifies.Similar fault history determination unit 5 uses cosine
Similarity or the distance of vector etc. calculate similarity.Then, similar fault history determination unit 5 is by phase calculated in step S34
The value (step S35) between 0~1 is converted to like the value of degree.It is bigger to be set as value, then similarity is higher.
Then, similarity obtained in step S35 is compared (step with threshold value by similar fault history determination unit 5
S36), in the case that the similarity obtained in step s 35 is threshold value or more, using i-th of fault history information as similar event
Barrier historical information is stored in similar fault history accumulation unit 6 (step S37).Also, similar fault history determination unit 5 is to i-th
It the responsible maintenance person ID that is described in a fault history information and is compared from the maintenance person ID that fault state acquisition unit 3 notifies
(step S38).Under maintenance person's ID unanimous circumstances, similar fault history determination unit 5 also using i-th of fault history information as
Maintenance person's fault history information is stored in maintenance person's fault history accumulation unit 7 (step S39).
Then, similar fault history determination unit 5 adds 1 (step S40) in i, anti-for next fault history information
The later movement of step S31 is carried out again.
The method that sentence is converted to vector of step S30 and step S33 are shown specifically in Figure 10.
Similar fault history determination unit 5 passes through morphemic analysis for the situation notified from fault state acquisition unit 3 or i-th of event
The sentence of barrier historical information is divided into word (step S100).
Then, the word after 5 pairs of similar fault history determination unit segmentations assigns weight (step S101).For example, similar event
Barrier history determination unit 5 can be carried out by TF-IDF (Term Frequency-Inverse Document Frequency) method
Weighting corresponding with the occurrence frequency of word.Also, compared with other terms, the dialect of elevator can be carried out larger
Weighting.
Then, word is converted to vector (step using Bag-of-Words method etc. by similar fault history determination unit 5
S102)。
The movement of similar fault history determination unit 5 is illustrated using concrete example.
Assuming that fault history information shown in Fig. 2 is stored in fault history accumulation unit 4.
At this time, it is assumed that maintenance person ID is that the maintenance person 200 of " 123 " inputs " having sound when driving " as extraction conditions.
Similar fault history determination unit 5 calculates the situation " having sound when driving " and fault history accumulation unit 4 of extraction conditions
The similarity of the situation of each fault history information of middle storage.Then, it is threshold value that similar fault history determination unit 5, which extracts similarity,
Above fault history information is as similar fault historical information.Here, the extraction of similar fault history determination unit 5 failure is set as to go through
The fault history information that history ID is 1,2,4,5,7 is as similar fault historical information.As a result, as shown in figure 3, in similar fault
It is 1,2,4,5,7 fault history information as similar fault historical information that fault history ID is stored in history accumulation unit 6.
Also, similar fault history determination unit 5, which extracts to describe in the column for being responsible for maintenance person ID, has the similar fault of " 123 " to go through
History information is as maintenance person's fault history information.As a result, as shown in figure 4, storing event in maintenance person's fault history accumulation unit 7
Hinder the similar historical information that history ID is 1,4 as maintenance person's fault history information.
Then, it is illustrated referring to action example of the Fig. 7 and Fig. 8 to display priority determination unit 8.
In the case where having read whole fault history information in the step S31 of Fig. 6, display priority determination unit 8 is from phase
Similar fault historical information is read one by one like fault history accumulation unit 6, (step until reading whole similar fault historical informations
Rapid S50, step S51).Then, display priority determination unit 8 is by the situation of i-th acquired of similar fault historical information
Sentence and the sentence of disposition are converted to vector (step S52, step S53).Display priority determination unit 8 utilizes side shown in Fig. 10
Sentence is converted to vector by method.Then, display priority determination unit 8 reads maintenance from maintenance person's fault history accumulation unit 7 one by one
Member's fault history information, until reading whole maintenance person's fault history information (step S54, step S55).Then, it shows
Priority determination unit 8 is converted to the sentence of situation of j-th read-out of maintenance person's fault history information and the sentence of disposition
Vector (step S56, step S57).Sentence is converted to vector using method shown in Fig. 10 by display priority determination unit 8.
Then, display priority determination unit 8 is tieed up according to j-th of vector sum of the situation of i-th of similar fault historical information
The vector of the situation of shield person's fault history information calculates the situation and j-th of maintenance person's failure of i-th of similar fault historical information
The similarity (step S58) of the situation of historical information.Then, display priority determination unit 8 will be calculated similar in step S58
The value of degree is converted to the value (step S59) between 0~1.It is bigger to be set as value, then similarity is higher.
Then, display priority determination unit 8 is tieed up according to j-th of vector sum of the disposition of i-th of similar fault historical information
The vector of the disposition of shield person's fault history information calculates the disposition and j-th of maintenance person's failure of i-th of similar fault historical information
The similarity (step S60) of the disposition of historical information.Then, display priority determination unit 8 will be calculated similar in step S60
The value of degree is converted to the value (step S61) between 0~1.It is bigger to be set as value, then similarity is higher.
Then, it is obtained in the similarity of the situation according to obtained in step S59 of display priority determination unit 8 and step S61
Disposition similarity, calculate i-th of similar fault historical information priority (step S62).More specifically, display is preferential
Grade determination unit 8 calculates priority using following formula (1).
Priorityi,j=a*Sim_ri,j+b*(1-Sim_ai,j) formula (1)
Here, a is Sim_ri,jCoefficient.Sim_ri,jIt is the situation and j-th of maintenance of i-th of similar fault historical information
Similarity between the situation of member's fault history information.B is Sim_ai,jCoefficient.Sim_ai,jIt is i-th of similar fault history
Similarity between the disposition and the disposition of j-th of maintenance person's fault history information of information.
In the case where maintenance person 200 has carried out disposition similar with the disposition taken under certain situation in the past, maintenance person
200 have knowledge and experience related with the disposition, and therefore, display priority determination unit 8, which reduces to describe, the similar of the disposition
The priority of fault history information.On the contrary, about the disposition that maintenance person 200 did not carried out in the past, maintenance person 200 does not have knowledge
And experience, therefore, display priority determination unit 8 improves the priority for describing the similar fault historical information for having the disposition.According to
Above-mentioned formula, description has situation similar with the situation for the failure that maintenance person 200 coped in the past and description has maintenance person 200
The priority of i-th of similar fault historical information of the disposition that do not took is higher.
Display priority determination unit 8 calculates priorityijAfterwards, 1 (step S63) is added in j, uses next maintenance person's event
Hinder historical information and calculates priorityi,j+1。
Then, display priority determination unit 8 uses i-th of similar fault historical information and maintenance person's fault history accumulation unit
The whole maintenance person's fault history information stored in 7 calculate priorityijAfterwards, the preferential of i-th of similar fault historical information is determined
Grade.
In the case where maintenance person carried out similar disposition under similar conditions in 200 past, in multiple priorityijMiddle presence
Lesser value.Therefore, display priority determination unit 8 selects priority according to formula (2)ijIn minimum value as i-th it is similar therefore
Hinder priority (the referred to as priority of historical informationi) (step S64).
Priorityi=min (priorityi,j) formula (2)
Display priority determination unit 8 selects priorityiAfterwards, 1 (step S65) is added in i, calculates the similar event of i+1
Hinder the priority of historical informationi+1。
In this way, the display priority determination unit 8 of present embodiment is directed to the similar event lower to related similarity is disposed
Hinder historical information and set higher priority, more for the higher similar fault historical information setting of similarity related with situation
High priority.
Using similar fault historical information shown in Fig. 3 and maintenance person's fault history information shown in Fig. 4 to priority
The example of calculating is illustrated.
According to Fig. 4, maintenance person 200 carried out the disposition for door boots under the situation of " having sound when driving ".In Fig. 3
In, the disposition for the similar fault historical information that fault history ID is 1,4,7 is the disposition for door boots, therefore, these similar events
The priority for hindering historical information is lower.On the other hand, in Fig. 3, the place for the similar fault historical information that fault history ID is 2,5
Set be oil supply or bolt to guide rail amendment, maintenance person 200 do not took these to dispose, therefore, these similar fault history
The priority of information is higher.
In the step S50 of Fig. 7, whole similar fault historical informations are read by display priority determination unit 8 and are calculated
After priority, as shown in figure 9, similar fault history output section 9 rearranges similar fault information (step according to the descending of priority
Rapid S70).Then, the similar fault historical information after similar fault history output section 9 will rearrange is output to maintenance person 200
Communication terminal 1 (step S71).
As a result, in communication terminal 1, shown from the higher similar fault historical information of priority.
The effect of * * embodiment illustrates * * *
As described above, in the present embodiment, between the disposition preferentially crossed to maintenance person's prompt and maintenance person's past experience
The lower disposition of similarity.It therefore, according to the present embodiment, can be preferentially unversed unknown to maintenance person prompting maintenance person
Disposition.Maintenance person it can be considered that the disposition of being proficient in of crossing of past experience and the disposition newly prompted come cope with elevator therefore
Barrier.
Embodiment 2
In above embodiment 1, determined according to the similarity of the situation of fault history and the similarity of disposition preferential
Grade.Even if maintenance person has sufficient knowledge and experience for certain type, do not have sometimes for other types sufficient yet
Knowledge and experience.Therefore, in the present embodiment, display priority determination unit 8 determines priority according to the similarity of type.Tool
For body, display priority determination unit 8 is calculated and is described in similar fault historical information according to each similar fault historical information
The similarity of the type described in type and maintenance person's fault history information, for higher similar of similarity related to type
The higher priority of fault history information setting.That is, if the type described in similar fault historical information and maintenance person's failure
The type described in historical information is identical, then display priority determination unit 8 is set higher in the similar fault historical information
Priority.Also, even if the type described in similar fault historical information and the type described in maintenance person's fault history information
Difference, if similar (for example, new architecture and older models of same model), display priority determination unit 8 is also to the similar event
Hinder historical information setting priority lower than same model but higher than entirely different type.Also, in similar fault history
In the case that the type described in the type and maintenance person's fault history information described in information is entirely different, in the similar fault
Lower priority is determined in historical information.
The additional item related with the similarity of type in above-mentioned formula (1), display priority determination unit 8 can be counted as a result,
Calculate the priority for reflecting the similarity of the similarity of situation, the similarity of disposition and type.
In addition, in the present embodiment, other than reflecting this point of the similitude of type in the calculating in priority, with reality
It is identical to apply mode 1.Therefore, the functional structure of elevator similar fault searching system 100 is as shown in Figure 1, elevator similar fault
The hardware configuration of searching system 100 is also as shown in figure 13.Also, the elevator similar fault searching system 100 of present embodiment
Movement also as shown in Fig. 5~Fig. 9.
Among the above, the priority of same model or similar type is improved, still, known to preferentially show with maintenance person
Know similar fault historical information related with the less type of experience, the setting of priority can also be made opposite.
As described above, according to the present embodiment, it can be considered that each maintenance person is directed to the knowledge and warp of possessed type
It tests, prompts similar fault historical information to maintenance person.
Embodiment 3
In above embodiment 2, according to the similarity of the situation of fault history, the similarity of disposition and type
Similarity determines priority.In the present embodiment, when calculating priority, consider the time.If proposing new disposition side
Method then preferably makes the new method of disposal proposed it is well known that more maintenance person is reminded to utilize new method of disposal.Cause
This in order to notify new method of disposal to maintenance person, preferentially shows new fault history information in the present embodiment.That is,
In present embodiment, display priority determination unit 8 calculates in similar fault historical information according to each similar fault historical information
The date-time of description and the difference of current time of day are set higher preferential for the smaller similar fault historical information of difference
Grade.
The additional item related to time in above-mentioned formula (1), display priority determination unit 8 can be calculated and be reflected as a result,
The priority of the similarity of situation, the similarity of disposition and time.
In addition, in the present embodiment, other than this point of reflecting time in the calculating in priority, with embodiment 1
It is identical.Therefore, the functional structure of elevator similar fault searching system 100 is as shown in Figure 1, elevator similar fault searching system
100 hardware configuration is also as shown in figure 13.Also, the movement of the elevator similar fault searching system 100 of present embodiment
As shown in Fig. 5~Fig. 9.
As described above, according to the present embodiment, it can be considered that the time prompts similar fault historical information to maintenance person.
Embodiment 4
In above Embodiments 1 to 3, similar fault historical information is shown according to the sequence of priority.It not only can be with
Similar fault historical information is shown according to the sequence of priority, and threshold value can also be set in priority, only more than display threshold
Priority similar fault historical information.
In addition, in the present embodiment, in addition to the similar fault historical information of priority this point more than only display threshold
In addition, identical as embodiment 1.Therefore, the functional structure of elevator similar fault searching system 100 is as shown in Figure 1, elevator
The hardware configuration of similar fault searching system 100 is also as shown in figure 13.Also, the elevator similar fault of present embodiment is retrieved
The movement of system 100 is also as shown in Fig. 5~Fig. 9.
According to the present embodiment, even if the quantity of similar fault historical information is more, maintenance person also can only read preferentially
The higher similar fault historical information of grade.
Embodiment 5
In above Embodiments 1 to 4, one by one read similar fault historical information and with maintenance person's fault history information
It is compared.Therefore, in the disposition such as " replacement of door boots " or " to the oil supply of guide rail ", it is not known that the disposition that each maintenance person spends
Time.Therefore, in the present embodiment, advance with the similar disposition such as " replacement of door boots " or " to oil supply of guide rail " and carry out group
It divides.Then, disposition the time it takes is calculated, in group, calculates what disposition was spent according to each responsible maintenance person ID
Time is averaged, it follows that each disposition the time it takes.By considering the disposition the time it takes, flower can be improved
The priority of time taking disposition.
In the present embodiment, display priority determination unit 8 is when calculating priority referring to Deal with Time information.When disposition
Between information be directed to grouping carried out and multiple disposition groups for being formed to similar disposition, according to each disposition group, description has
Belong to time i.e. Deal with Time required for the disposition of each maintenance person when the disposition of disposition group.Then, it shows excellent
First grade determination unit 8 sets higher priority to the similar fault historical information for describing the disposition for belonging to following disposition group, should
Disposition group is the longer place of Deal with Time of the maintenance person 200 (specifying the maintenance person of extraction conditions) in multiple disposition groups
Set group.
System operator can read the content of disposition and carry out group division manually.And it is possible to use K-means method
The methods of summarize the higher disposition of similarity.
Figure 11 shows the example of the fault history information of present embodiment.
Fault history information shown in Figure 11 has added live arrival time compared with fault history information shown in Fig. 2
Column, processing complete the moment column, dispose group number column.Moment calculating can be completed according to live arrival time and processing
Time when disposition.
At the time of live arrival time is that the scene of failure has occurred in maintenance person's arrival.
At the time of the disposition completion moment is that maintenance person completes disposition.
Disposition group number is the number of each disposition group.
Figure 12 shows the example of the Deal with Time information of present embodiment.
As shown in figure 12, in Deal with Time information, according to each disposition group number, place is shown with the unit of maintenance person
Set the time.
Display priority determination unit 8 is when calculating priority, according to the disposition group for including in similar fault historical information
Number and responsible maintenance person ID obtain the Deal with Time of maintenance person 200 according to Deal with Time information, and it is longer to improve Deal with Time
The priority of similar fault historical information.
For example, in the example in figure 12, about maintenance person ID：123 maintenance person, with disposition group：1 Deal with Time phase
Than the Deal with Time for disposing group 3 is longer.Therefore, display priority determination unit 8 makes to belong to disposition group：3 fault history
ID：The priority of 3 similar fault historical information, which is higher than, belongs to disposition group：1 fault history ID：1 similar fault history
The priority and fault history ID of information：The priority of 4 similar fault historical information.
As described above, according to the present embodiment, it can be considered that the Deal with Time of each maintenance person is similar to maintenance person's prompt
Fault history information.
Embodiments of the present invention are explained above, but it is also possible to combine 2 or more implemented in these embodiments
Embodiment.
Alternatively, a part of an embodiment in these embodiments also can be implemented.
Alternatively, a part for implementing 2 or more embodiments in these embodiments can also be combined.
In addition, the present invention is not restricted to these embodiment, can make various changes as needed.
* * hardware configuration illustrates * * *
Finally, showing the structural example of the elevator similar fault searching system 100 of Embodiments 1 to 5 in Figure 13.
Elevator similar fault searching system 100 is computer.
As hardware, elevator similar fault searching system 100 has processor 901, storage device 902, communication interface
903。
Processor 901 is IC (the Integrated Circuit handled：Integrated circuit).
Processor 901 is CPU (Central Processing Unit：Central processing unit), DSP (Digital
Signal Processor：Digital signal processor) etc..
Storage device 902 is RAM (Random Access Memory：Random access memory), ROM (Read Only
Memory：Read-only memory), flash memory, HDD (Hard Disk Drive：Hard disk drive) etc..Fault history accumulation unit 4, phase
It is real by storage device 902 like fault history accumulation unit 6, maintenance person's fault history accumulation unit 7, maintenance person's information accumulation unit 10
It is existing.
Communication device 903 includes the receiver for receiving data and the transmitter for sending data.
Communication device 903 is, for example, communication chip or NIC (Network Interface Card：Network interface card).
It is stored in storage device 902 and realizes that maintenance person authentication department 2, fault state acquisition unit 3, similar fault history are sentenced
Determine the function in portion 5, display priority determination unit 8 and similar fault history output section 9 (in the following, they are collectively referred to as " portion ")
Program.
Moreover, processor 901 executes these programs, the movement in " portion " is carried out.
Schematically illustrated in Figure 13 processor 901 execute realization " portion " function program state.
Also, OS (Operating System is also stored in storage device 902：Operating system).
Moreover, at least part of OS is executed by processor 901.
Processor 901 executes at least part of OS, and executes the program of the function of realization " portion ".
Also, indicate information, data, signal value and the storage of variable values of the processing result in " portion " in storage device 902 or
In register or cache memory in processor 901.
Also, realize that the program of the function in " portion " can store in disk, floppy disk, CD, compact disc, blue light (registration
Trade mark) in the mobile memory mediums such as disk, DVD.
Also, " portion " can also be rewritten into " circuit " or " process " or " step " or " processing ".
Also, elevator similar fault searching system 100 can pass through logic IC (Integrated Circuit：It is integrated
Circuit), GA (Gate Array：Gate array), ASIC (Application Specific Integrated Circuit：Towards
The integrated circuit of special-purpose), FPGA (Field-Programmable Gate Array：Field programmable gate array) in this way
Electronic circuit realize.
In this case, " portion " is realized respectively as a part of electronic circuit.
In addition, processor and above-mentioned electronic circuit are referred to as process circuit system.
Label declaration
1：Communication terminal；2：Maintenance person authentication department；3：Fault state acquisition unit；4：Fault history accumulation unit；5：Similar event
Hinder history determination unit；6：Similar fault history accumulation unit；7：Maintenance person's fault history accumulation unit；8：Display priority determination unit；
9：Similar fault history output section；10：Maintenance person's information accumulation unit；100：Elevator similar fault searching system；200：Maintenance
Member.
Claims (8)
1. a kind of information processing unit, has：
Extraction unit, from describe respectively faulty situation occurred, for the failure disposition and carried out the disposition
In multiple fault history information of maintenance person, the situation occurred phase for describing and having and being appointed as extraction conditions by arbitrarily maintenance person is extracted
As situation occurred 2 or more fault history information as 2 or more similar fault historical informations, from the institute extracted
It states in 2 or more similar fault historical informations, extracts the similar fault for describing and having the maintenance person for specifying the extraction conditions
Historical information is as maintenance person's fault history information；
Priority level initializing portion calculates the disposition described in similar fault historical information according to each similar fault historical information
With the similarity between the disposition that is described in maintenance person's fault history information, for to dispose related similarity lower
Similar fault historical information sets higher priority；And
Output section, the high similar fault historical information of preferential output priority.
2. information processing unit according to claim 1, wherein
The priority level initializing portion calculates the generation described in similar fault historical information according to each similar fault historical information
The similarity between situation occurred described in situation and maintenance person's fault history information, for related with situation occurred
The higher similar fault historical information of similarity sets higher priority.
3. information processing unit according to claim 1, wherein
The extraction unit extracts described 2 or more from multiple fault history information that description has the type that failure has occurred respectively
Similar fault historical information,
The priority level initializing portion calculates the type described in similar fault historical information according to each similar fault historical information
It is higher for similarity related with type with the similarity between the type that is described in maintenance person's fault history information
Similar fault historical information sets higher priority.
4. information processing unit according to claim 1, wherein
The extraction unit extracts described 2 from multiple fault history information that description has the date-time that failure has occurred respectively
Above similar fault historical information,
The priority level initializing portion calculates the date described in similar fault historical information according to each similar fault historical information
The difference of time and current time of day set higher priority for the smaller similar fault historical information of difference.
5. information processing unit according to claim 1, wherein
The output section only exports the similar fault historical information of the priority of threshold value or more.
6. information processing unit according to claim 1, wherein
The priority level initializing portion is referring to Deal with Time information, in the Deal with Time information, carries out for similar disposition
Grouping and the multiple disposition groups formed describe when having the disposition for belong to disposition group according to each disposition group
Each maintenance person disposition required for time, that is, Deal with Time,
The priority level initializing portion is higher to the similar fault historical information setting for describing the disposition for belonging to following disposition group
Priority, the disposition group be it is the multiple disposition group in the maintenance person for specifying the extraction conditions Deal with Time compared with
Long disposition group.
7. a kind of information processing method, wherein
Computer from describe respectively faulty situation occurred, for the failure disposition and carried out the maintenance of the disposition
In multiple fault history information of member, extraction description has similar with the situation occurred for being appointed as extraction conditions by arbitrarily maintenance person
2 or more fault history information of situation occurred is as 2 or more similar fault historical informations, from described 2 extracted
In a above similar fault historical information, the similar fault history for describing and having the maintenance person for specifying the extraction conditions is extracted
Information as maintenance person's fault history information,
The computer according to each similar fault historical information, calculate the disposition that is described in similar fault historical information with it is described
The similarity between disposition described in maintenance person's fault history information, for the similar event lower to related similarity is disposed
Hinder historical information and set higher priority,
The high similar fault historical information of the preferential output priority of computer.
8. a kind of message handling program makes computer execute following processing：
Extraction process, from describe respectively faulty situation occurred, for the failure disposition and carried out the disposition
In multiple fault history information of maintenance person, the situation occurred phase for describing and having and being appointed as extraction conditions by arbitrarily maintenance person is extracted
As situation occurred 2 or more fault history information as 2 or more similar fault historical informations, from the institute extracted
It states in 2 or more similar fault historical informations, extracts the similar fault for describing and having the maintenance person for specifying the extraction conditions
Historical information is as maintenance person's fault history information；
Priority level initializing processing calculates the disposition described in similar fault historical information according to each similar fault historical information
With the similarity between the disposition that is described in maintenance person's fault history information, for to dispose related similarity lower
Similar fault historical information sets higher priority；And
Output processing, the high similar fault historical information of preferential output priority.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/JP2016/061537 WO2017175378A1 (en) | 2016-04-08 | 2016-04-08 | Information processing device, information processing method, and information processing program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108885724A true CN108885724A (en) | 2018-11-23 |
| CN108885724B CN108885724B (en) | 2022-02-25 |
Family
ID=60000938
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201680083889.1A Active CN108885724B (en) | 2016-04-08 | 2016-04-08 | Information processing apparatus, information processing method, and computer-readable recording medium |
Country Status (6)
| Country | Link |
|---|---|
| JP (1) | JP6359228B2 (en) |
| KR (1) | KR101950660B1 (en) |
| CN (1) | CN108885724B (en) |
| DE (1) | DE112016006545T5 (en) |
| TW (1) | TWI597682B (en) |
| WO (1) | WO2017175378A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113396119A (en) * | 2019-02-14 | 2021-09-14 | 三菱电机株式会社 | Fault assistance device, fault assistance program, and fault assistance method |
| CN114730443A (en) * | 2019-11-06 | 2022-07-08 | 三菱电机楼宇解决方案株式会社 | Building information processing device |
| CN116109116A (en) * | 2023-04-13 | 2023-05-12 | 中建安装集团有限公司 | Cloud computing-based comprehensive application program supervision control system and method |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6649416B2 (en) * | 2018-02-02 | 2020-02-19 | ファナック株式会社 | Failure classification device, failure classification method, and failure classification program |
| JP6705845B2 (en) * | 2018-02-08 | 2020-06-03 | ファナック株式会社 | Failure site identification device, failure site identification method, and failure site identification program |
| US20220129862A1 (en) * | 2019-03-20 | 2022-04-28 | Nec Corporation | Display control device, display control method, and recording medium |
| JP6717555B1 (en) * | 2019-03-27 | 2020-07-01 | 三菱ロジスネクスト株式会社 | Troubleshooting system with notification function |
| KR102235728B1 (en) * | 2019-05-28 | 2021-04-05 | 한국철도기술연구원 | Fault prediction apparatus and method of electric type side entrance door of electric train |
| JP6736733B1 (en) * | 2019-07-22 | 2020-08-05 | 日東電工株式会社 | Facility abnormality action timing determination system, facility abnormality action timing determination method, and computer program |
| JP2023176269A (en) * | 2022-05-31 | 2023-12-13 | 横河電機株式会社 | Apparatus, method, and program for maintaining facility |
| JP2024146402A (en) * | 2023-03-31 | 2024-10-15 | 横河電機株式会社 | Recommendation method, recommendation program, and recommendation device |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010257066A (en) * | 2009-04-22 | 2010-11-11 | Hitachi Software Eng Co Ltd | Troubleshooting support system |
| JP2011227601A (en) * | 2010-04-16 | 2011-11-10 | Mitsubishi Electric Corp | Information providing device and program therefor |
| CN102271054A (en) * | 2010-06-02 | 2011-12-07 | 微软公司 | Bookmarks and performance history for network software deployment evaluation |
| CN102270485A (en) * | 2010-06-07 | 2011-12-07 | 索尼公司 | Information processing apparatus, information processing method, and program |
| CN104091290A (en) * | 2014-07-11 | 2014-10-08 | 国家电网公司 | Intelligent substation monitoring information diagnosing and analyzing method |
| JP2014199618A (en) * | 2013-03-29 | 2014-10-23 | Ｎｅｃネッツエスアイ株式会社 | Fault monitoring system |
| WO2015002930A1 (en) * | 2013-07-01 | 2015-01-08 | Kabam, Inc. | System and method for facilitating gifting of virtual items between users in a game |
| CN104298476A (en) * | 2013-07-15 | 2015-01-21 | 日本冲信息株式会社 | Information processing device and information processing method |
| CN104637021A (en) * | 2013-11-08 | 2015-05-20 | 广州市地下铁道总公司 | Condition-maintenance-mode city rail vehicle auxiliary maintenance system |
| US20150199854A1 (en) * | 2008-04-07 | 2015-07-16 | United Parcel Service Of America, Inc. | Vehicle maintenance systems and methods |
| CN105069509A (en) * | 2015-08-05 | 2015-11-18 | 上海古鳌电子科技股份有限公司 | Transaction processing system and processing method |
| JP5820072B2 (en) * | 2012-07-11 | 2015-11-24 | 株式会社日立製作所 | Similar failure case search device |
| US9226368B2 (en) * | 2012-01-17 | 2015-12-29 | Cimcon Lighting, Inc. | Fault management for streetlights |
| JP5855036B2 (en) * | 2013-02-28 | 2016-02-09 | 三菱電機株式会社 | Equipment inspection order setting device |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW575818B (en) * | 2000-05-31 | 2004-02-11 | Hannstar Display Corp | Product maintenance recording device |
| JP4004222B2 (en) | 2000-11-15 | 2007-11-07 | トヨタ自動車株式会社 | Maintenance support method and maintenance support device for work robot system |
| JP2007140997A (en) * | 2005-11-18 | 2007-06-07 | Mitsubishi Electric System & Service Co Ltd | Apparatus for diagnosing fault |
| JP2007141128A (en) * | 2005-11-22 | 2007-06-07 | Tokiko Techno Kk | Maintenance management system |
| US20080059120A1 (en) * | 2006-08-30 | 2008-03-06 | Fei Xiao | Using fault history to predict replacement parts |
| JP2008257433A (en) | 2007-04-04 | 2008-10-23 | Matsushita Electric Ind Co Ltd | Reception/transmission device, mobile terminal, program and recording medium |
| JP2008310582A (en) * | 2007-06-14 | 2008-12-25 | Hitachi Ltd | Maintenance work support apparatus and system, and maintenance work support method |
| JP2009187097A (en) * | 2008-02-04 | 2009-08-20 | Hitachi Omron Terminal Solutions Corp | Automatic teller machine |
| US20090292956A1 (en) * | 2008-05-23 | 2009-11-26 | Microsoft Corporation | Trend based test failure prioritization |
| US9081888B2 (en) * | 2010-03-31 | 2015-07-14 | Cloudera, Inc. | Collecting and aggregating log data with fault tolerance |
| US20130073271A1 (en) * | 2010-05-24 | 2013-03-21 | Nec Corporation | Static fault tree analysis system and method from system models |
| KR20140036375A (en) * | 2012-09-12 | 2014-03-26 | 현대로템 주식회사 | Intelligent failure asset management system for railway car |
| JP6079243B2 (en) * | 2013-01-10 | 2017-02-15 | 日本電気株式会社 | Failure analysis support device, failure analysis support method, and program |
| WO2015029300A1 (en) | 2013-08-29 | 2015-03-05 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ | Information provision apparatus, server apparatus, information provision method, and information provision program |
-
2016
- 2016-04-08 DE DE112016006545.0T patent/DE112016006545T5/en not_active Ceased
- 2016-04-08 WO PCT/JP2016/061537 patent/WO2017175378A1/en active Application Filing
- 2016-04-08 KR KR1020187023993A patent/KR101950660B1/en active IP Right Grant
- 2016-04-08 CN CN201680083889.1A patent/CN108885724B/en active Active
- 2016-04-08 JP JP2018510208A patent/JP6359228B2/en active Active
- 2016-07-15 TW TW105122355A patent/TWI597682B/en active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150199854A1 (en) * | 2008-04-07 | 2015-07-16 | United Parcel Service Of America, Inc. | Vehicle maintenance systems and methods |
| JP2010257066A (en) * | 2009-04-22 | 2010-11-11 | Hitachi Software Eng Co Ltd | Troubleshooting support system |
| JP2011227601A (en) * | 2010-04-16 | 2011-11-10 | Mitsubishi Electric Corp | Information providing device and program therefor |
| CN102271054A (en) * | 2010-06-02 | 2011-12-07 | 微软公司 | Bookmarks and performance history for network software deployment evaluation |
| CN102270485A (en) * | 2010-06-07 | 2011-12-07 | 索尼公司 | Information processing apparatus, information processing method, and program |
| US9226368B2 (en) * | 2012-01-17 | 2015-12-29 | Cimcon Lighting, Inc. | Fault management for streetlights |
| JP5820072B2 (en) * | 2012-07-11 | 2015-11-24 | 株式会社日立製作所 | Similar failure case search device |
| JP5855036B2 (en) * | 2013-02-28 | 2016-02-09 | 三菱電機株式会社 | Equipment inspection order setting device |
| JP2014199618A (en) * | 2013-03-29 | 2014-10-23 | Ｎｅｃネッツエスアイ株式会社 | Fault monitoring system |
| WO2015002930A1 (en) * | 2013-07-01 | 2015-01-08 | Kabam, Inc. | System and method for facilitating gifting of virtual items between users in a game |
| CN104298476A (en) * | 2013-07-15 | 2015-01-21 | 日本冲信息株式会社 | Information processing device and information processing method |
| CN104637021A (en) * | 2013-11-08 | 2015-05-20 | 广州市地下铁道总公司 | Condition-maintenance-mode city rail vehicle auxiliary maintenance system |
| CN104091290A (en) * | 2014-07-11 | 2014-10-08 | 国家电网公司 | Intelligent substation monitoring information diagnosing and analyzing method |
| CN105069509A (en) * | 2015-08-05 | 2015-11-18 | 上海古鳌电子科技股份有限公司 | Transaction processing system and processing method |
Non-Patent Citations (2)
| Title |
|---|
| 李国正: "《基于RAMS的地铁列车车载设备维修策略与故障诊断研究》", 《万方数据库》 * |
| 江志农 等: "《基于案例与规则推理的故障诊断专家系统》", 《计算机工程》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113396119A (en) * | 2019-02-14 | 2021-09-14 | 三菱电机株式会社 | Fault assistance device, fault assistance program, and fault assistance method |
| CN113396119B (en) * | 2019-02-14 | 2022-11-29 | 三菱电机株式会社 | Failure support device, computer-readable recording medium, and failure support method |
| CN114730443A (en) * | 2019-11-06 | 2022-07-08 | 三菱电机楼宇解决方案株式会社 | Building information processing device |
| CN116109116A (en) * | 2023-04-13 | 2023-05-12 | 中建安装集团有限公司 | Cloud computing-based comprehensive application program supervision control system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| TWI597682B (en) | 2017-09-01 |
| KR20180097768A (en) | 2018-08-31 |
| JPWO2017175378A1 (en) | 2018-08-30 |
| CN108885724B (en) | 2022-02-25 |
| JP6359228B2 (en) | 2018-07-18 |
| DE112016006545T5 (en) | 2018-11-15 |
| WO2017175378A1 (en) | 2017-10-12 |
| TW201810161A (en) | 2018-03-16 |
| KR101950660B1 (en) | 2019-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108885724A (en) | Information processing unit, information processing method and message handling program | |
| US11256712B2 (en) | Rapid design, development, and reuse of blockchain environment and smart contracts | |
| CN110287696B (en) | Detection method, device and equipment for rebound shell process | |
| CN107003931B (en) | Decoupling test validation from test execution | |
| CN109766697A (en) | Vulnerability scanning method, storage medium, equipment and system applied to linux system | |
| WO2017023299A1 (en) | Composing future tests | |
| CN101965558B (en) | Event history tracking device | |
| CN110414806B (en) | Employee risk early warning method and related device | |
| CN117009626A (en) | Service processing method, device, equipment and storage medium of game scene | |
| CN107463555B (en) | Method, system and device for deleting intermediate layer data | |
| CN106529281A (en) | Executable file processing method and device | |
| CN117236304A (en) | Method for realizing Excel general import based on template configuration | |
| CN114282795B (en) | Network target range personnel skill evaluation method, device, equipment and readable storage medium | |
| JP2013077124A (en) | Software test case generation device | |
| CN115328786A (en) | Automatic testing method and device based on block chain and storage medium | |
| CN114064510A (en) | Function testing method and device, electronic equipment and storage medium | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| TW202131179A (en) | Computer-implemented system and method for diagnosis of live virtual server performance data | |
| CN112559331A (en) | Test method and device | |
| CN105844176A (en) | Security strategy generation method and equipment | |
| CN111104963A (en) | Target user determination method and device, storage medium and electronic equipment | |
| Chai et al. | A software defect management system based on knowledge base | |
| CN105718253B (en) | A kind of device selection method and system of automatic test | |
| CN110968467A (en) | Remote automatic test method for GPU and algorithm | |
| CN104866559B (en) | A kind of collecting method of data warehouse, apparatus and system |
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 |