KR20040107895A - Network system for managing fault - Google Patents

Abstract

PURPOSE: A system for managing faults on transport fields through the network is provided to output fault particulars according to a user's request by making a management server transfer fault data to an inspection client and analyze the fault, if a filed client registers/reports the fault and management particulars to the management server. CONSTITUTION: The first communication module(102) undertakes communication with the field client. The second communication module(102') undertakes the communication with the inspection team client. A fault registration module(104) registers a fault report from the field client and transmits the fault data(200) to the inspection team client. A management particulars registration module(106) registers the management particulars from the filed client. An inspection result registration module(112) registers an inspection result received from the inspection result. A fault analysis module(116) analyzes the fault based on the data registered to each module and outputs the result by the request of an inquiry request module(118). An output module(120) outputs analyzed result to the field or/and inspection team client.

Description

Network system for managing fault

The present invention relates to a system for managing failures occurring in the field where the airline, subway, train, submarine, ship, etc. are operated through a network such as the Internet or mobile.

At present, since there is no system for reporting and managing failures at each airline, subway, train, submarine, ship, etc., it is not possible to know the failure trends because information on the failure is not accumulated. In addition, failures that occur frequently in the subway do not know what is the problem, it does not know the problem of purchasers, producers, parts, manufacturers. Without systematic management of such breakdowns, subway accidents, train accidents, airline accidents, ship accidents and submarine accidents will continue to occur in the future.

The present invention is an absolutely necessary system to protect the lives of the people when using the air, subway, train, submarine, ship, etc. to travel or do business, the management server to manage the breakdown and action history occurred in the field-side client When registered and reported in the management server, the management server delivers the failure data to the inspection client, and analyzes the failure to output the failure history according to the user's request, the purpose of providing a failure management system through the network.

1 is a basic workflow of the present invention

2 is a block diagram of a management server of the present invention.

1 is a flowchart of a failure reporting and management system (also referred to as an SDR system) according to the present invention. Here, "on-site" means a place for operating a mechanical device, such as aircraft, trains, trains, ships, submarines.

1, if a failure is found during operation or inspection of the machine in the field, the details of the failure are recorded and a failure report is made. In the problem report, record the history of the object, the location of the failure, the section, the classification of the failure, the parts of the failure, and the cause in a predetermined form. If possible, it is preferable to attach a video such as a photograph.

If a fault can be corrected at the site, take action. Otherwise, register the fault with the system management team. The system management team accepts the fault. The fault registration details are the reason for the fault, the control number, the delay time, the place of occurrence, the date and time of the fault, the fault code, the manufacturer of the faulted part, the part number, the serial number, and the lot number.

On the other hand, if the fault is corrected at the site, the action details are registered in the system management team. In the matters to be registered, the result of the action is added to the fault registration contents.

The system management team forwards the fault report to the inspection team when it receives a fault report. All fault reports can be forwarded to the inspection team for inspection, or a failure classification code can be set in advance and sent only to the inspection team for failures that correspond to a specific code.

When the inspection team receives the failure report, the inspection team performs the inspection based on the predetermined inspection criteria, and the inspection result is reported back to the system management team. The items included in the inspection result report will be the fault registration contents and the inspection result data.

The system management team analyzes the faults from the site and reports the faults from the inspection team. The failure analysis can be performed in various ways. The following failure analysis can be performed according to an inquiry request from a site or an inspection team (which may be other users). These are the number of failures by condition, object, defect rate of parts, and failure history by object. In addition, the reliability of the parts may be included. Reliability judgment is a judgment method that checks the frequency of occurrence of a specific failure part and compares it with the standard failure frequency.

This method of failure analysis may depend on the type of inquiry request. That is, the system management team can analyze and manipulate the failure data registered in the past by requesting inquiry by condition, failure occurrence inquiry by object, material defect inquiry, object history inquiry, and comprehensive fault inquiry. On the other hand, the output form is not only a simple report form but also a graph form.

In the above workflow, the site-system management team-testing team can be connected through a network such as the Internet or mobile. In this case, the system administration team will act as the server, and the site and inspection teams will each act as clients.

Hereinafter, a server performing a system management team's work will be referred to as a management server, and the configuration and operation of the management server performing the basic business of the present invention will be described.

2 is a block diagram of the management server 100 of the failure report management system according to the present invention. There is a first communication module 102 in charge of communication with the field-side client and a second communication module 102 'in communication with the client of the inspection team side. Although these communication modules are shown as functionally separated in FIG. 2, they are generally physically integrated and configured. However, it is not limited thereto.

In addition, there is a failure registration module 104 and the action history registration module 106 to receive a failure report and action history from the field client through the first communication module 102. The fault registration form 108 and the action history registration form 110 are stored in a predetermined storage device for fault registration and action history registration in each module.

As described above, items to be filled out in the fault registration form include the reason for the failure, the control number, the delay time, the occurrence place, the date and time of the fault, the fault code, the manufacturer of the fault part, the part number, the serial number, and the lot number. .

In addition to the above items, action history data is added to the action history registration form.

On the other hand, the failure registration module 104 is connected to the second communication module 102 ', and transmits a failure report to the inspection team client. In this case, as explained earlier, the inspection team will inspect the failure according to the failure report.

In addition, the management server 100, the inspection result registration module 112 and the inspection result registration form for registering the inspection result transmitted from the inspection team client through the second communication module 102 'after the inspection team completes the inspection ( 114). The inspection result registration items are preferably classified by code or the like for easy processing.

In addition, there is a failure analysis module 116 for analyzing a failure based on the data registered in the action history registration module 106 and the test result registration module 112. As described above, the failure analysis module 116 analyzes failure data according to a request of the inquiry request module 118 and outputs the result. For example, failure data is analyzed according to the inquiry request such as the number of failures by condition, by object, part defect rate, and failure history by object.

In addition, reliability determination is possible. Reliability judgment is a judgment method that checks the frequency of occurrence of a specific failure part and compares it with the standard failure frequency. It can provide detailed specifications of the parts and manufacturer's information, provide a report that can identify the failure trend of the object, and can provide a failure tracking report.

The failure information analyzed by the failure analysis module 116 receives the request of the field client, the inspection team client, or another user to the inquiry request module 118 and outputs the output to the output module 12. The output can be in the form of a general report or a graph, as described earlier. In addition, if a specific object repeatedly fails, it may be possible to output it in the form of an alert. Since the selection of the format of the output is extremely obvious to those skilled in the art, a detailed description thereof will be omitted.

On the other hand, in Figure 2, the management server 100 is connected to the failure data DB (200). The failure data DB 200 serves to store failure data registered in the failure registration module 104. In addition to the database connected to the management server 100, the action history DB (not shown), the inspection result DB (not shown) is possible. Although these are not shown and described separately, the construction of these database servers is naturally accompanied by the management server.

An example of the failure data stored in the failure data DB 200 is shown in the table.

The data shown in the table below is the data of the failures that can occur in the case of an aircraft, which is largely divided into a failure report table (Table 1), a replacement part table (Table 2), a failure image table (Table 3), and a failure code table (Table 4). ), A manufacturer table (Table 5), a model table (Table 6), and a part name table (Table 7).

Fault Report Table: A table that stores the data on which fault reports have occurred. Delays and malfunctions of more than 15 minutes are registered and stored. English name Hangul Name Field ID Explanation SDR Number Report number SDRNumber Manage the number of failures on a yearly basis. Line Target Carrier AirLine Breakdown Carrier Year count Airline Count Yearcount Occurrence number by carrier Difficulty Date Fault Date DiffDate Date of failure User Id User ID UserID User who registered the failure report Report submitter reporter Reporter Report of failure report Report Date Report date RepDate Date reported Report Time Report time RepTime Time reported Registration No. Registration code RegNumber Unique registration number Type emphysema ACType We display model of aircraft Submitter Type Type of processing SubmitType Mechanic and Repair Shop Common Code Air work Business AirWork It means business division of object. Difficulty Place occuring area DiffPlace Indicates where the failure occurred Direction Name Flight number DirecName Transport direction of object Take off 1 Segment 1 TakeOff1 Transport section of the object 1 Take off 2 Section 2 TakeOff2 Transport section of the object 2 Take off 3 Segment 3 TakeOff3 Transport section of the object 3 Plan start Start planning AirPlanStart Departure plan hour: minute Plan end End of plan AirPlanEnd Arrival plan hour: minute Air Actual Start Actual flight AirActualStart Actual departure plan hour: minute Air Actual End Actual flight ends AirActualEnd Actual arrival plan hour: minute Difficulty section Breakdown DiffSection Type of failure Delay, return, ISFD, etc. Difficulty Detail section Delay DiffDetailSection Detailed classification of delay and cancellation Delay Time Delay time DelayTime Maintenance delay time (hours) Non Maint Time Non Maint Delay Time NonDelayTime Non-maintenance delay time: minutes Non Maint Code Non Maint Code NonDelayCo Delay sort code, not maintenance ATA Code ATA code ATACode Breakdown Code for Failure SDR type SDR Type SDRType Maintenance, inspection, etc. Stage of Operation Fault Detection Time stgOperation When a breakdown was found NatureofCondition1 Fault condition 1 NatureCond1 State of failure NatureofCondition2 Fault state 2 Naturecond2 State of failure NatureofCondition3 Fault state 3 NatureCond3 State of failure PrecautionaryProcedure 1 Pilot Action 1 PreProcedure1 Pilot Action PrecautionaryProcedure 2 Pilot Action 2 PreProcedure2 Pilot Action PrecautionaryProcedure 3 Pilot Action 3 PreProcedure3 Pilot Action PrecautionaryProcedure 4 Pilot Action 4 PreProcedure4 Pilot Action

Region Jurisdiction Region Jurisdiction Aircraft time Aircraft time Aircrafttime Gas use time Air landing count Aircraft Landing Frequency AirLandCount Landings Aircraft Make Gas manufacturer Airmake Gas manufacturer Aircraft model Aircraft Model AirModel Airframe model AircraftSerialNumber Serial Number AirSerial Aircraft Serial Number AircraftSeat Number Seating capacity Airseat Seats AircraftTotalTime Gas use time AircraftTotalTime Gas use time Aircraft L / D Cycles Machine gun cycle AirLDCycle Gas cycle total cycle Engine Make Engine failure manufacturer Enginemark Engine manufacturers Engine model Engine model EngineModel Engine model Engine SerialNumber Engine Serial Number EngineSerial Engine serial number Engine Seat Number Engine Seats Engineeat Engine seats Engine TotalTime Engine Hours EngineTotalTime Engine usage time Engine TotalCycles Engine gun cycle EngineTotalCycle Engine use total cycle Propellor Make Propeller failure manufacturer Propellermeak Propeller manufacturers Propellor Model Propeller Model PropellorModel Propeller Model PropellorSerialNumber Propeller serial PropellorSerial Propeller Serial Number Propellor Seat Number Propeller seats PropellorSeat Propeller seats Propellor TotalTime Propeller Hours PropellorTTime Propeller Hours Propellor TotalCycles Propeller Gun Cycle PropellorTCycle Propeller Gun Cycle ComponentMake Component Manufacturer CompMake Component Manufacturer ComponentName Component Name CompName Component Name ComponentPartNumber Component number CompNumber Component part number ComponentSerialNumber Component serial number CompSerial Component serial number ComponentModel Component Model CompModel Component Model Number ComponentLocation Component location CompLocation Component mounting position ComponentTotalTime Total usage time CompTTime Total usage time ComponentTotalCycles Total cycle CompTCycle Total cycle ComponentTimeSince usage time CompTimeSince usage time ComponentSincecode Usage code CompCodeSince Usage code Discrepancy Fault details Discrepancy Breakdown Content Take Action Date Date of Action TakeActDate Date of Action Take Action Time Action time TakeActTime Action time Take Action Code Action code TakeActCode Action code MEL No MEL No Melno MEL No Difficulty cause code Fault code DiffCauseCode Fault code Difficulty cause Cause of trouble DiffCauseComment Cause of trouble Pilot name Millet name Pilotname Millet name Crew count Crew Crewcount Crew Passenger count Passenger Passengercount Passenger Cargo count Cargo volume Cargocount Cargo volume Passengertakeakection Passenger Action PasTakeAct Passenger Action TakeActionComment Action Details TakeActComment Action Details Other Comment Other information Othercomment Other information ASI Check ASI CHeck ASICheck ASI CHeck

Detachable parts table: A table that stores parts that have failed. English name Hangul Name Field ID Explanation SDR Number Report number SDRNumber Report number Number turn Numbers turn Air line Target Airlines AirLine Target Airlines User Id User ID UserID User ID Partmake Component Manufacturer Partmake Parts manufacturer PartName Part Name PartName Part Name PartNumber Part number PartNumber Part number PartSerialNumber Part serial number PartSerialNum Part serial number Manag code Management code ManagCode Part grade management code PartCondition Part Status PartCondition Part status Part Location Mounting position PartLocation Mounting position Install Date Date of Installation InstallDate Date of Installation TSN Total usage time TimeSinceNew Total usage time CSN Total cycle CycleSinceNew Total cycle TSI Usage time after installation TimeSinceInstall Usage time after installation CSI Post-Mount Cycle CycleSinceInstall Post-mount cycle PartTimeSince usage time PartTimeSince Parts usage time PartSincecode Usage code PartSincecode Usage classification code Security Level Security level SecuriLevel Security level

Fault image table: A table that stores images of faulty parts or parts. English name Hangul Name Field ID Explanation SDR Number Report number SDRNumber Report number Number turn Numbers turn User Id User ID UseID User ID File location File location FileLocation File location File type File type Filetype File type Selection division Selection 1, SDR, 2.Action

Fault code table: A table that stores basic data by coding details of a fault. English name Hangul Name Field ID Explanation SDR Code code SDRCode Fault classification code SDR Name designation SDRName Fault name SDR Name Short Abbreviation SDRName Shorten Fault abbreviation ASI_YN ASI presence ASIYN Inspection Required Processing Inspector_ Section Inspector Inspector Section Gas inspector, electronic inspector, operation Display sequance Order of display Displayseq Order of display User Id User ID UserID User ID

Manufacturer Table: A table that stores the name of the manufacturer that has failed. English name Hangul Name Field ID Explanation Manufacture Code code Manucode Publisher code Manufacture name designation Manuname Manufacturer Name Manufacture Short Abbreviation Manuhorten Publisher Abbreviation Manufacture sel division Manuselection 01: gas, 02: engine, 3: propeller, State country State country Address address Address address User Id User ID UserID User ID

Model Table: A table that stores the name of the model that has failed. English name Hangul Name Field ID Explanation Model Code code ModelCode code Model name designation ModelName designation model Short Abbreviation ModelShorten Abbreviation Model sel division ModelSelection 01: Gas, 02: Engine, 3: Propeller State country State country

Part Name Table: A table that stores the part names where a fault occurs. English name Hangul Name Field ID Explanation Part Name code code PartNameCode code Part Name Part Name PartName Part Name Part Name shortened Part Name Abbreviation PartNameShorten Part Name Abbreviation State country State country TSO Technical standard TSO Technical standard Display sequance Order of display Displayseq Order of display User Id User ID UserID User ID

Technical effect

1. Predictive failures in aviation, trains, trains, ships, submarines, and appliances.

2. Identify the maker, model, part number, serial number, problem of failure, action history, and diagram of parts used in aviation, train, train, ship, submarine, and equipment.

3. Identify trends in components and failures in aviation, trains, trains, ships, submarines, and appliances.

-Determination of maintenance trends for effective safety inspection

-Efficient management of the place of purchase, producer, training, safety maintenance procedures, etc.

-Effective evaluation of maintenance programs, inspection procedures, etc.

4. Track down faulty parts and components.

Economic effect

1. Standardize safety tasks in aviation, trains, trains, ships, submarines and appliances.

2. Improve the safety of aviation, trains, trains, ships, submarines and appliances.

3. We can protect the lives of the people.

4. Feedback from the evaluation of the products (parts) produced by the company can lead the company to produce improved products.

Commercial effect

1. Support for safety decision making and unforeseen accident prevention programs through data analysis through standardization of safety work processes of aviation, train, train, ship, submarine, and mechanism

2. Commercial effects that cannot be converted into wealth by protecting the lives of the people.

3. Improve the competitiveness of our company in the global market by feeding back the evaluation of the products (parts) produced by the company, allowing the company to produce improved products.

4. Strengthen the training of aviation, train, train, ship, and submarine sectors.

Claims (9)

In the failure management system in which the client on the field side, the client on the inspection team side, and the management server are connected through a network to report and manage a failure in the field, the management server is The first communication module 102 in charge of communication with the site-side client and the second communication module 102 'in communication with the inspection team-side client, Failure registration module 104 to register the failure report from the on-site client through the first communication module 102 and to transmit failure data to the client of the inspection team side through the second communication module, Action history registration module 106 that receives the action history from the on-site client through the first communication module 102, An inspection result registration module 112 which registers the inspection result when the inspection team client transmits the inspection result through the second communication module 102 '; The failure analysis module 116 analyzes the failure based on the data registered in the action history registration module 106 and the inspection result registration module 112 and analyzes the data according to the request of the inquiry request module and outputs the result. , And an output module for outputting the fault content analyzed by the fault analysis module 116 to a site-side client or / and an inspection team client. The fault management system according to claim 1, further comprising a fault data DB for storing fault data registered in the fault registration module (104). The apparatus of claim 1, further comprising a memory device in which a fault registration form 108 and a measure history registration form 110 for registering faults and action details are stored in the fault registration module and the action history registration module. Fault management system through network. The fault registration form according to claim 3, wherein the fault registration form includes a reason for the fault, a control number, a delay time, a place of occurrence, a date and time of occurrence of a fault, a fault code, a maker of a fault part and a part number. Management system. The method of claim 3, wherein the action history registration form includes a reason for failure, a control number, a delay time, a place of occurrence, a date and time of occurrence of a failure, a failure code, a manufacturer of a failure part, a part number, and a description of a failure action history. Fault management system through the network. The fault management system according to claim 1, further comprising a storage device that stores a test result registration form for registering a test result in the test result registration module. The system of claim 1, wherein the failure analysis module includes a reliability determination module that checks a frequency of occurrence of a specific failure part and compares the failure rate with a standard failure frequency. The system of claim 1, wherein the output module outputs an output in a report format or a graph format. The system of claim 1, wherein the failure analysis module comprises an alarm module that alerts when a specific object is repeatedly broken.