JP2006190340A - Repair examination system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a repair examination system by which repair examination is automatically performed to speedily obtain a more uniform and exact repair examination result. <P>SOLUTION: The repair examination system in this invention has an examination means for examining whether or not an entity of repair request contents between checked repair request data read from a second storage means and product information is valid based on repair examination conditions for specifying validity of repair by every predetermined product type, outputting a valid code when the entity is valid and outputting examined repair request data to which an examination result representing a code representing unsuitable description is attached when the entity is not valid and an operating system is constituted so as to load an application program corresponding to the request to a second storage means among a plurality of application programs stored in a program area of a first storage means based on an execution request of the application program from a terminal. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a repair screening system for performing a repair screening on whether or not the repair request content of repair request data related to home appliances in an extended warranty contract is appropriate.

  In this specification, the term “extended warranty contract” refers to a contract that guarantees the product of a product failure or malfunction that occurs within a certain period of time after the end of the manufacturer's warranty period or after a certain period of time. Say. “Repair request data” refers to the date of failure, failure symptom, failure related to failure repair or product replacement reported by the customer company or repair company, etc. when the product fails in the above extended warranty contract. Data including causes, measures, repair charges, etc. Further, “repair examination” means judging (examining) whether or not the contents of the repair request represented by the repair request data are appropriate. Specifically, in the repair examination, the contents of the repair request are examined from the following viewpoints. (1) The failed product must be subject to an extended warranty contract. (2) The failure date is within the warranty period of the extended warranty contract. (3) The cause and treatment of the failure shall be the subject of the failure and treatment that are subject to the warranty terms of the extended warranty contract. (4) The repair request amount is reasonable.

  When a home appliance breaks down, the repair of the failure is required by one repair engineer at the customer company that has signed an extended warranty contract, and the cause is investigated from the failure symptoms of the home appliance. We will take appropriate measures. When the repair of the home appliance is completed, the customer company communicates the input repair request data describing the failure occurrence date, the failure symptom, the cause of the failure, the treatment, the repair request amount, etc. related to the above-mentioned failure repair or product replacement. Transfer to the guarantee company over the line.

  On the other hand, after receiving the input repair request data as the received repair request data, the guarantee company confirms that the repair request contents indicated by the received repair request data by the person in charge of repair, that is, the repair examiner, are appropriate. By judging whether or not, repair inspection is performed.

  Specifically, the repair examiner determines whether the repair of the home appliance reported in the received repair request data is a repair subject to warranty, and whether the repair request content and the repair request amount are appropriate.

  In order to conduct such a repair examination, the person in charge of the repair examination needs know-how equivalent to that of a repair engineer. For example, regarding electrical equipment, knowledge of the principle of the motor, the actual circuit of the control circuit, the electrical / mechanical operating principle, and the components constituting the electrical equipment is required. However, the repair examiner cannot check the failure symptoms or the products that have been repaired. In other words, the person in charge of repair review conducts a repair review on the repair request for the home appliance based on the contents of each item of the information reported as the repair request represented by the repair request data and the relationship between the items. .

  In any case, conventionally, a person in charge of repair examination judges a repair request for a repair request related to a home appliance from one piece of repair request data. Then, if the repair request for the repair request is valid, the repair reviewer accepts the repair request as the result of the repair request, and if not, requests the request as the repair review result. Dismiss.

  As described above, the repair examination of the conventional repair request data is performed by the person in charge of the repair judgment with the eyes of each person. Therefore, manpower must be increased in proportion to the increase in the number of repair inspections. In addition, in order to investigate the cause from the failure symptoms of home appliances and determine whether or not necessary measures have been taken, a high level of expertise is required for the person in charge of repair examination. In addition, due to the depth of expertise of the person in charge of repair examination, there is a possibility that the results of the repair examination will vary.

  As described above, in the prior art, (1) the amount of work increases in proportion to the number of requests for repair, and (2) there is a possibility that the results of the repair examination may vary, and a uniform and accurate repair examination result can be obtained. There is a problem that it cannot be obtained.

  Accordingly, an object of the present invention is to provide a repair screening system that can automatically perform repair screening and obtain a more uniform and accurate repair screening result in a speedy manner.

  The above-mentioned problem of the present invention is a repair inspection system for performing a repair inspection to determine whether or not the content of repair request data of repair request data related to home appliances in an extended warranty contract is valid. The server includes an operating system, receiving means for receiving repair request data transferred from a customer company through a communication line, and storing the repair request data received by the receiving means First storage means having a data area and a program area for storing a plurality of application programs, and repair of the repair request data read from the first storage means in response to an execution request from the terminal device Check means for checking whether the format of the content of the claim is valid, and the check means The second storage means for storing the checked repair request data that has been checked and the product information of the warranty product table corresponding to the checked repair request data, and the validity of the repair for each predetermined product type Based on the repair examination condition, it is examined whether or not the substance of the repair request contents of the checked repair request data and the product information read from the second storage means is valid. And an examination unit that outputs examination repair request data attached with examination results indicating a code that is valid and a code indicating an unsuitable type if not valid, and the operating system receives the terminal device from the terminal device. Based on the application program execution request, the plurality of applications stored in the program area of the first storage means. It is achieved by repairing examination system application program corresponding to the request from the emission program is configured to load in the second storage means.

From the beginning of the business, the applicant has fostered a person in charge of repair examination based on the acquisition of certifications in order to provide more appropriate services. In addition, with the goal of developing this system, we have analyzed the events necessary for repair review, designed the system, and accumulated the repair request data that has been reviewed. As a result, the applicant currently has about 600,000 examined repair request data stored in the applicant's database.
The examined repair request data stored in this database is a data reflecting a repair examination result by a repair examination by a person in charge of repair examination having one case and one case. Therefore, the present inventor has analyzed a repair request data stored in the database, discovered a new repair screening rule, and developed a repair screening system that automatically performs a repair screening according to the repair screening rule. By doing so, the above problems were solved.

Here, the “repair review rule” is the experience that the same measures are taken for the repairs of similar home appliances due to the same cause of failure, and the same repair costs are required. It is a rule. In other words, the repair examination rule defines the validity of repair for each predetermined product type. Therefore, if the repair request data is automatically reviewed according to this repair review rule, it will be easier to determine whether the repair request data in the repair request data is appropriate or not in a short time than manually. It is possible to obtain a uniform and accurate repair examination result.
In order to discover this repair examination rule, the present inventor actually selects a specific home appliance from the examined repair request data stored in the database, and causes the failure and failure in the selected home appliance. I compared repair, treatment, and repair costs. As a result, as expected from the rule of thumb, the present inventor has taken the same measures for repairing the same home appliance due to the same cause of failure, and requires almost the same repair cost. I confirmed (discovered) that it was. Therefore, the present inventor has come up with the idea of applying this repair screening rule to automatic repair screening.

If it is determined that the substance of the repair request content of the repair request data is not valid based on the repair screening rule, a review result indicating a code indicating the inappropriate type is attached to the repair request data. As a result, the repair request data excluded from the repair review rule will be manually reviewed for repairs as before, but a code indicating an inappropriate type is attached, so Repair inspection can be performed more easily and accurately.
According to the present invention, the repair examination rule of the repair request obtained by analyzing the examined repair request data accumulated from the past is processed by the computer system, so that the above-mentioned conventional technology (1), ( The problem of 2) was solved to reduce costs and improve customer service.
Here, the “repair request content format” is an item necessary for repair request data. On the other hand, the “substance of repair request content” means the actual content of items included in the repair request data, that is, the cause of failure, treatment, the amount of repair request, and the like.

As described above, according to the present invention, by realizing systematization, a person in charge of repair examination in the past performs a substantive examination on the basis of a repair examination rule for a repair request that has been reviewed for one case and one case. The repair examination is automatically performed to determine whether or not the contents of the repair request in the repair request data are appropriate. As a result of the repair examination, a code that is valid if appropriate and a code that represents an inappropriate type if not valid are added to the examined repair request data.
In practice, a segment code and an exit module code are used as the code, and are added to the examined repair request data. Here, the “segment code” is divided into the following two categories depending on the presence or absence of an error as a result of checking the format of the content of the received repair request data by a computer. (1) If there is an error, the type of error. (2) If there is no error, the repair request amount range that is below, within, or above the lower limit of the repair request range subject to the repair request rule for repair request amount. Classification. The “Exit Module Code” classifies the conditions under which repair inspection rules were judged inappropriate and excluded from the scope of inspection when substantive inspection was performed on the repaired repair request data according to the repair inspection rules. .

The repair examiner can specify the repair request data that has been examined by designating the product type, segment code, and exit module code from the terminal device. In this way, it is possible to carry out the repair examination operation continuously from the terminal screen with similar examined repair request data segmented according to the product type, which is manually conducted in the order of acceptance. This improves the accuracy and efficiency of the repair review.
The resulting productivity gain leads to cost savings. In addition, improvement in accuracy can be expected to improve customer service by speeding up uniform screening.

  In the repair examination system of the present invention, the receiving means receives repair request data transferred from a customer company through a communication line in response to a repair request data processing request from the terminal device, and receives the first storage. Configured to be realized by a daily billing data recording program which is one of the application programs stored in the program area of the first storage means, which is configured to be stored in the data area of the means May be.

  In the repair examination system of the present invention, the check means reads the repair request data from the first storage means of the server in response to the repair request data processing request from the terminal device, and the format of the repair request content is You may comprise so that it may be implement | achieved by the monthly billing data recording program which checks whether it is appropriate.

  In the repair examination system of the present invention, the monthly billing data recording program further has a function of storing the checked repair billing data and the warranty product data in the corresponding warranty product table in the second storage means of the server. It may be provided.

  In the repair examination system of the present invention, the examination means includes a guarantee product in the guarantee product table corresponding to the checked repair request data based on the repair examination condition that prescribes the validity of repair for each predetermined product type. Examining whether the substance of the repair request content with the data is valid or not, if it is valid, the examination result indicating a valid code, and if not valid, the examination result indicating a code indicating an inappropriate type A repair examination program, which is one of the application programs stored in the program area of the first storage means, is configured to output the repair request data with the examination attached. May be.

  In the repair examination system of the present invention, the first storage means totalizes information recording the examination result added to the examined repair request data, and displays the result of aggregation for each product type on the display device of the terminal device The examination result monitor program that is one of the application programs stored in the program area of the first storage means may be further stored.

  The repair examination system of the present invention further comprises registration means for registering the repair examination condition determined by analyzing the repair claim data item and the repair claim amount in response to the repair examination condition registration request from the terminal device. May be configured.

  In the repair examination system of the present invention, the registration means is configured to be realized by a repair examination condition registration program which is one of application programs stored in the program area of the first storage means. Also good.

  In the repair examination system of the present invention, the repair examination condition may be stored in the data area of the first storage means as a repair examination condition table.

  In the repair examination system of the present invention, the operating system allocates necessary hardware devices in the execution order of the specific program stored in the program area of the first storage means and executes instructions, When the above instruction is executed, the terminal device may be informed of the end of program execution, and the hardware device reserved for executing the application program may be released.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a hardware configuration diagram of a repair examination system according to an embodiment of the present invention.
The illustrated repair examination system includes a server device 10 and a terminal device 20, which are connected via a local area network (LAN) 30. In the illustrated example, the server device 10 and the terminal device 20 are connected via the LAN 30, but other networks may be used. In the illustrated example, only one terminal device 20 is illustrated, but it is needless to say that a large number of terminal devices may be provided.

  The server device 10 is connected to a public line (communication line) via the first communication control device 11 and is connected to the LAN 30 via the second communication control device 12. On the other hand, the terminal device 20 is connected to the LAN 30 via the third communication control device 21. Further, the server device 10 includes a disk device 40.

  The server device 10 includes a CPU 51, a first system bus 52, a database management system 53, an operating system (OS) 54, a real storage area (memory) 55, and a second system bus 56. And have. The first system bus 52 is connected to the first communication controller 11, and the second system bus 56 is connected to the second communication controller 12.

  As will be described later, the terminal device 20 sends a daily repair request data processing request, a monthly repair request data processing request, a repair screening condition registration request, and a repair screening result monitor request to the server device 10.

  The disk device 40 has a data area for storing data and tables and a program area for storing application programs. The data area includes input repair request data T1, received repair request data T2, inspected repair request data T3, repair inspection condition table T4, warranty product table T5, various code tables T6, and products to be inspected. A table T7 is stored. On the other hand, the program area includes a billing data recording (daily) program P1, a billing data recording (monthly) program P2, a repair screening condition registration program P3, a repair screening program P4, and a screening result monitoring program as will be described later. P5 is stored.

  The first communication control device 11 operates according to a communication control program. That is, the communication control program stores the input repair request data in the text format transferred from the customer company (not shown) through the communication line in the data area of the disk device 40 as the input repair request data T1. In this example, a file transfer protocol is used for this transfer.

  FIG. 2 shows the configuration of the input repair request data T1. The input repair request data T1 has a unique product slip number as an item name. That is, the product slip number is given a different number for each input repair request data T1. The product slip number indicates a number assigned by the POS system at the time of product sales.

  The input repair request data T1 includes, as the item name, the account date, product CD, manufacturer warranty period, product model, serial number, product replacement flag, repair reception date, repair completion date, failure status 1, failure status 2, There are failure status 3, failure cause, failure treatment 1, failure treatment 2, repair part 1, repair part 2, repair part 3, repair shop, billing part fee, billing fee, billing business trip cost, and billing consumption tax. The account date indicates the reporting month (1st to last month) of repair request data. The product CD means a product type code, of which the first 4 digits indicate the product type. The manufacturer warranty period indicates the repair warranty period of the manufacturer and is usually one year. The product model indicates the product model, and the serial number indicates the serial number. The product replacement flag indicates whether the product has been replaced in response to the repair request. The repair reception date indicates the date when the repair report is received from the user. The repair completion date indicates the date when the repair is completed. Failure statuses 1 to 3 indicate failure status codes. The cause of failure indicates a failure cause code. Failure measures 1 and 2 indicate codes of measures taken for the failure. Repair parts 1 to 3 indicate codes of parts exchanged for repair. The repair execution store shows the store code where the repair was executed. The billing part indicates the part billing amount. The billing fee indicates the amount billed. The billing business trip cost indicates the bill for the business trip cost. The invoiced consumption tax indicates the consumption tax for the sum of each invoiced amount. Here, the sum of the billing parts fee, billing fee, billing business trip cost, and billing consumption tax is the repair billing amount.

  The input repair request data T1 includes, as item names, parts cost, construction fee, business trip cost, and consumption tax. The part cost indicates the part cost determined after the examination. The construction fee indicates the confirmed construction fee after the examination. The business trip cost indicates the confirmed business trip cost after the examination. The consumption tax indicates the consumption tax on the total of parts cost, construction fee, and business trip expenses. These parts charges, construction fees, business trip expenses, and consumption tax are left blank until a formal check by the billing data recording (monthly) program P2, which will be described later, and an automatic repair examination by substantive examination by the repair examination program P4 are finalized. is there. In addition, the sum of the parts fee, construction fee, business trip cost, and consumption tax is the repair amount.

  Returning to FIG. 1, the operating system 54 stores the application program registered in the disk device 40 through the second system bus 56 based on the program execution request from the terminal device 20. Load to area 55. The operating system 54 assigns necessary devices in the order of execution of the program and executes the instructions.

  The second system bus 56 exchanges data with each device necessary for execution of instructions. When all the instructions are executed, the operating system 54 notifies the terminal device 20 of the end of the program execution and releases each device reserved for the program execution.

  Note that the repair examination system shown in FIG. 1 can also be implemented by a general-purpose computer and an online terminal, or other device configurations such as a personal computer.

  FIG. 3 is a system outline diagram showing the relationship between the program, data, and table stored in the disk device 40 of the repair examination system shown in FIG.

  The billing data recording (daily) program P1 receives the input repair billing data transferred from the customer company through the communication line in response to the daily repair billing data processing request from the terminal device 20, and the server device 10 This is a program for realizing a receiving means for storing the received repair request data T2 in the disk device 40. Here, the disk device 40 functions as first storage means.

  FIG. 4 shows the configuration of the received repair request data T2. The received repair request data T2 is shown in FIG. 2 except that errors 1 to 5, an answer input date, an inquiry status, a status code (status), a segment code, and an exit module code are added as item names. The same structure as the input repair request data T1 shown in FIG.

  Errors 1 to 5 indicate error codes detected by the data check. The response input date indicates the date when the response is input for the content introduction. The inquiry status indicates the response status (answer waiting, inquiry again, etc.) to the inquiry. The status code (status) indicates the handling status of the repair request data (holding, settlement of payment, withdrawal of request). The segment code is a code that indicates the type of error and the amount range of the repair request amount. The Exit module code is a code representing the result of the repair examination.

  That is, the received repair request data T2 is data obtained by accumulating the input repair request data T1 on the disk device 40 of the server device 10 every day. Of the item names in the received repair request data T2, the errors 1 to 5, the answer input date, the segment code, and the exit module code are blank.

  Returning to FIG. 3, the billing data recording (monthly) program P <b> 2 receives the repair request data received from the disk device 40 of the server device 10 in response to the monthly repair request data processing request (execution request) from the terminal device 20. A means for checking whether the format of the repair request content of T2 is valid and storing the checked repair request data and the warranty product data of the corresponding warranty product table T5 in the real storage area 55 of the server device 10 is realized. It is a program. Here, the real storage area 55 serves as second storage means.

  The repair examination program P4 is a program for checking the contents of the repair request contents of the checked repair request data and the warranty product data in the corresponding warranty product table T5 based on a repair examination rule that prescribes the appropriateness of repair for each product type. Examine whether the entity is valid or not, and if it is valid, output a code that is valid, and if not valid, output examination repair request data T3 with an examination result indicating a code indicating an inappropriate type It is a program that realizes screening means.

  FIG. 5 shows the configuration of the examined repair request data T3. The examined repair request data T3 has the same configuration as the received repair request data T2 shown in FIG.

  That is, the examined repair request data T3 is subjected to a format check by the claim data recording (monthly) program P2 and a substantive examination by the repair review program P4 with respect to the received repair request data T2, and as a result, an error code, This is data with segment code and Exit module code added.

  The repair examination condition registration program P3 responds to the repair examination condition registration request from the terminal device 20 and, as will be described later, the repair examination conditions (repair examination rules) determined by analyzing the repair request data items and the repair request amount. ). The repair screening conditions registered by the repair screening condition registration program P3 are stored in the disk device 40 as a repair screening condition table T4.

  FIG. 6 shows the configuration of the repair examination condition table T4, and FIG. 7 shows a specific example of the repair examination condition table T4.

  As shown in FIG. 6, the repair examination condition table T4 includes, as item names, examination condition numbers, product types, condition items, conditions, and registration dates. The examination condition number indicates a table registration key. The product type indicates the product type. The condition item indicates an item name for specifying the condition. The condition indicates the value and range of the condition for determining the validity of the repair request for each item. The registration date indicates the update date of the condition table.

  As shown in FIG. 7, the repair examination condition table T4 includes conditions for determining whether or not the substance of the repair request content of the repair request data is valid for each product type. The product type, manufacturer, cause This is data in which the procedure is a code, the purchase price (amount), the repair request amount is specified in a numerical range, and the contents are recorded.

  FIG. 7 illustrates an example in which the examination condition is “A002” and the product type is a color television. If the product type to be repaired is color television repair request data, it is determined whether the product type is built-in 14-inch VTR, built-in 20-inch VTR, or 28-wide. Next, it is determined whether the manufacturer of guaranteed product data corresponding to the repair request data is any one of company A, company B, company C, or company D. Similarly, the cause and treatment of the repair request data are also compared with the values given in the conditions of the repair examination condition table T4. Then, it is compared whether the purchase price of the warranty product data corresponding to the repair request data and the repair request amount of the repair request data are included in the lower limit and upper limit ranges of the purchase price of the repair examination condition and the repair request amount. In this way, if the items of the warranty product data in the warranty product table T5 corresponding to the repair request data satisfy each item of the repair examination condition table T4, it is determined that the repair request is an appropriate repair request.

  In addition, when each item of the repair examination condition table T4 is compared, information on the product specified by the repair request data is obtained by referring to the warranty product data. For example, regarding the manufacturer, since this item does not exist in the repair request data, the manufacturer information is obtained by referring to the warranty product data.

  Returning to FIG. 3, the examination result monitoring program P5 is a program for monitoring the repair examination result, and as will be described later, totals information that records the examination result added to the examined repair request data T3. This is a program for displaying the result of aggregation for each product type on the terminal device 20.

  FIG. 8 shows the configuration of the guaranteed product table T5 used in the billing data recording (monthly) program P2. The guaranteed product table T5 has a unique product slip number as an item name. This product slip number is the same as that assigned to the above-mentioned input repair request data T1, received repair request data T2, and examined repair request data T3.

  Warranty product table T5 includes item name, account date, sales store, sales date, purchase price, purchaser, product CD, product model, manufacturer code, manufacturer warranty period, manufacturer warranty completion date, extended warranty start date, extension There are warranty completion date, registration date, renewal date, notes, and status.

  The accounting date indicates the reporting month (1st to last month) of warranty product data. The sales store indicates the store code where the product was sold. The sales date indicates the product sales date. The purchase price indicates the purchase price of the product. The purchaser indicates a product purchaser (customer number, customer name, etc.). The product CD means a product type code, of which the first 4 digits indicate the product type. The product model indicates the product model. The manufacturer code indicates the code of the product manufacturer. The manufacturer warranty period indicates the repair warranty period of the manufacturer (usually one year). The manufacturer warranty completion date indicates the end date of the manufacturer's repair warranty period. The extended warranty start date indicates the day after the end date of the manufacturer's repair warranty period. The extended warranty completion date indicates the end date of the extended warranty period. The registration date indicates the date when the product data is registered in the table. The update date indicates the date when the product data is updated. Notes indicate special notes. The status indicates the validity (valid / invalid) of the data.

  In other words, the warranty product table T5 shows the product information that is the subject of the extended warranty contract. In the guaranteed product table T5, information such as a purchaser, a product purchase date, a warranty period, a product type, and a purchase price is recorded when the product is purchased.

  FIG. 9 shows the configuration of various code tables T6 used in the billing data recording (monthly) program P2. The various code tables T6 have item types such as code type, code, code name, registration date, and status (status). The code type indicates the code type. The code indicates the code. The code name indicates a code name (content represented by the code). The registration date indicates the code registration date. The status indicates the validity (valid / invalid) of the code.

  That is, the various code table T6 is a table in which various codes are recorded for checking the code of the repair request data and displaying the code and the code name on the terminal screen when the repair examination condition is registered. There are six types of codes: failure status, failure cause, failure treatment, parts, product type, and manufacturer.

  FIG. 10 shows examples of codes used as codes of various code tables T6.

  As shown in FIG. 10A, as the failure status code that is the code when the code type is the failure status, for example, “111001” is the code name “no power supply”, and “111002” is the code name “ “No video or audio is output (lights but is not displayed)”, “111004” is the code name “No video is displayed”, “1111011” is the code name “Remote control does not work”, “1111026” Represents the code name “Power cannot be turned off”.

  As shown in FIG. 10 (2), for example, “02” is the code name “degraded” and “03” is the code name “electrical” as the failure cause code that is the code when the code type is the cause of the failure. "04" represents the code name "bad contact", "10" represents the code name "short", and "11" represents the code name "disconnected". .

  As shown in FIG. 10 (3), for example, “01” is the code name “part replacement” and “02” is the code name “adjustment” as the failure treatment code that is the code when the code type is the failure treatment. "05" represents the code name "lubricating", "16" represents the code name "soldering", and "31" represents the code name "unit replacement".

  As shown in FIG. 10 (4), for example, “1021” is a code name “antenna part” and “1030” is a code name “air filter” as a part code that is a code when the code type is a part. “1037” represents the code name “tank cap”, “1058” represents the code name “glow lamp”, and “1105” represents the code name “timer”.

  As shown in FIG. 10 (5), as a product type code that is a code when the code type is a product type, for example, “1111012” is a code name “color TV 30 or more wide”, and “111022” is a code. The name “Color TV 28 Wide”, “111050” is the code name “Color TV 20, 21 type 4: 3”, “1111054” is the code name “Color TV 20 type VTR built-in”, and “111074” is the code name. “Built-in color TV 14-inch VTR” is shown.

  As shown in FIG. 10 (6), for example, “01110” is a code name “C company” and “01310” is a code name “E company” as a maker code that is a code when the code type is a maker. “02110” represents the code name “Company D”, “02210” represents the code name “Company A”, and “03920” represents the code name “Company B”.

  In the present embodiment, the various code tables T6 are configured as one data file, but it is needless to say that each code table T6 may be configured with six code tables.

  FIG. 11 shows the configuration of the product table for inspection T7 used in the repair inspection program P4. In the examination table T7, the item name includes product type, automatic examination object on / off, switching registration date, and initial registration date. The product type indicates the product. On / off of the automatic screening target, ON indicates a screening target and OFF indicates a non-screening target. The switching registration date indicates the date when the on / off switching is performed. The initial registration date indicates the date when the product type is registered.

  In other words, the examination target product table T7 records the product types that are subject to the repair examination conditions specified by the examination method switching program (not shown).

  Next, the billing data recording (daily) program P1 executed in the server device 10 will be described with reference to FIG.

  The billing data recording (daily) program P <b> 1 is executed by the operating system 54 of the server device 10 based on the daily repair billing data processing request from the terminal device 20. The operating system 54 loads the billing data recording (daily) program P1 requested by the application program registered in the disk device 40 into the real storage area 55 via the second system bus 56. . The operating system 54 executes the instructions of the billing data recording (daily) program P1 as described below according to the flowchart shown in FIG.

  The operating system 54 first reads the input repair request data T1 transferred from the customer company system to the disk device 40 through the communication line from the disk device 40 (step S101), and passes through the second system bus 56. The read input repair request data T1 is moved to the real storage area 55 (step S102).

  Subsequently, the operating system 54 sends the input repair request data T1 read from the real storage area 55 to the disk device 40 via the second system bus 56, as described above. The received repair request data T2 is written in a state where items such as a code and an exit module code are added (step S103).

  Here, the input repair request data T1 does not limit the medium and the recording format. Also, the processing cycle such as daily or monthly is not particularly limited.

  Next, the billing data recording (monthly) program P2 executed in the server device 10 will be described with reference to FIG.

  The billing data recording (monthly) program P <b> 2 is executed by the operating system 54 of the server device 10 based on a monthly repair billing data processing request from the terminal device 20. The operating system 54 loads the billing data recording (monthly) program P2 requested from the application program registered in the disk device 40 into the real storage area 55 via the second system bus 56. . The operating system 54 executes the instructions of the billing data recording (monthly) program P2 as described below according to the flowchart shown in FIG.

  The operating system 54 reads the received repair request data T2 from the disk device 40, and passes it to the checked repair request data storage area (not shown) of the real storage area 55 via the second system bus 56. (Step S201).

  Subsequently, the operating system 54 has warranty product data having the same product slip number in the warranty product table T5 with the product slip number of the received repair request data T2 moved to the real storage area 55 as a key. Search whether or not. If it exists, the product data is transferred to a guaranteed product data storage area (not shown) in the real storage area 55 (step S202). The key item described above is not limited to the product slip number, and may be any item that can specify a product.

  Next, when the operating system 54 determines that the product data does not exist in the guaranteed product table T5 (Yes in step S203), the product data that has been checked as the error code is added to the checked repair request data in the real storage area 55. '3052' indicating "is not registered" is set (step S204), and the process proceeds to step S207.

  On the other hand, when the product data exists in the guaranteed product table T5 (No in step S203), the operating system 54 performs the actual operation when the failure occurrence date is not within the warranty period of the guaranteed product data (No in step S205). In the checked repair request data in the storage area 55, “3132” indicating “the repair reception date is out of the warranty period” is set as an error code (step S206), and the process proceeds to step S207.

  When the product data exists in the warranty product table T5 (No in step S203) and the failure occurrence date is within the warranty period of the warranty product data (Yes in step S205), the operating system 54 The process proceeds directly to step S207.

  In step S207, the operating system 54 checks the failure status, the cause of the failure, the failure treatment, and the code of the repair part in the received repair request data T2. That is, the operating system 54 collates each code of the checked repair request data recorded in the real storage area 55 with various code tables T6 of the disk device 40.

  If the failure status code of the received repair request data T2 does not exist in the various code tables T6 (Yes in step S208), the operating system 54 adds an error code to the checked repair request data in the real storage area 55. '3162' indicating "failure status code error" is set (step S209). If the failure cause code of the received repair request data T2 does not exist in the various code tables T6 (Yes in step S210), the operating system 54 indicates “failed” as an error code in the checked repair request data on the real storage area 55. “3212” indicating “cause code error” is set (step S211). If the failure treatment code of the received repair request data T2 does not exist in the various code tables T6 (Yes in step S212), the operating system 54 indicates “failed” as the error code in the checked repair request data on the real storage area 55. “3222” indicating “treatment code error” is set (step S213). If the failed part code of the received repair request data T2 does not exist in the various code tables T6 (Yes in step S214), the operating system 54 indicates “failed” as the error code in the checked repair request data on the real storage area 55. “3282” indicating “part code error” is set (step S215).

  Next, the operating system 54 checks the limit of the repair request amount (step S216). That is, the operating system 54 checks other items of the received repair request data T2. In addition, as other items, for example, the presence or absence of the history of repair requests for the same product is confirmed. If there is an error (Yes in step S216), the operating system 54 sets the error code of the checked repair request data in the real storage area 55 (step S217).

  In this manner, when an error is detected, an error code indicating the content of the error is edited in the checked repair request data in the real storage area 55. When the check is completed, the operating system 54 activates the repair examination program P4 (step S218). The repair screening program P4 will be described in detail later with reference to the flowchart shown in FIG.

  When the execution of the repair examination program P4 is completed, the operating system 54 executes a write command for the examination-requested repair request data T3 (step S219). In other words, the operating system 54 writes the checked repair request data in the real storage area 55 to the disk device 40 as the examined repair request data T3 via the second system bus 56.

  Next, the repair examination condition registration program P3 executed in the server device 10 will be described with reference to FIG.

  The repair examination condition registration program P3 is executed by the operating system 54 of the server apparatus 10 based on the repair examination condition registration request from the terminal device 20. The operating system 54 loads the repair examination condition registration program P3 requested by the application program registered in the disk device 40 into the real storage area 55 via the second system bus 56. The operating system 54 executes the instructions of the repair examination condition registration program P3 as described below according to the flowchart shown in FIG.

  The operating system 54 displays a repair examination condition input screen on the terminal device 20 (step S301). Subsequently, the operating system 54 reads the product type code specified on the repair examination condition input screen of the terminal device 20 (step S302). The product type code input from the terminal device 20 is recorded in the real storage area 55 via the communication control device 21, the LAN 30, the communication control device 12, and the second system bus 56.

  The operating system 54 extracts various types of tables necessary for the recorded product types from the various code tables T6 of the disk device 40, and extracts the product type, manufacturer code, failure cause code, and action code into the real storage area 55. Recording is performed (step S303). Various codes related to the product type recorded in the real storage area 55 are input to the repair examination condition input screen of the terminal device 20 via the second system bus 56, the communication control device 12, the LAN 30, and the communication control device 21. Displayed above.

  FIG. 15 shows an example of the repair examination condition input screen. As is clear from FIG. 15, the examination conditions are (1) product, (2) manufacturer, (3) purchase price, (4) cause, (5) treatment, (6) total loss, and (7) repair request amount. There are seven items. In the example shown in FIG. 15, the product type code is “1110”, which indicates that the product type is a color television. (1) As a product of the review conditions, the product type code “111074” has a built-in 14-inch VTR, the product type code “1111054” has a built-in 20-type VTR, the product type code “111022” has a 28-wide product type code. “1111012” indicates 30 or more wide, product type code “111050” indicates 20.21 type 4: 3, product type code “1111040” indicates 25 type 4-3, and product type code “1111070” indicates 14 type ing.

  (2) As a manufacturer of the examination conditions, the manufacturer code “02210” is Company A, the manufacturer code “03920” is Company B, the manufacturer code “01110” is Company C, the manufacturer code “02110” is Company D, The manufacturer code “01310” indicates the company E, the manufacturer code “01410” indicates the company F, and the manufacturer code “01210” indicates the company G.

  As the (3) purchase price of the examination conditions, a range of 10,000 yen to 230000 yen is set. As the cause of the examination condition (4), the failure cause code “03” indicates the electrical characteristic deviation, the failure cause code “02” indicates the deterioration, the failure cause code “04” indicates the contact failure, and the failure cause code “11”. "" Indicates a disconnection, failure cause code "29" indicates a mechanical operation failure, failure cause code "10" indicates a short circuit, and failure cause code "12" indicates a capacity loss.

  As the examination condition (5) treatment, the treatment code “01” indicates component replacement, and the treatment code “16” indicates soldering. As the (6) total loss of examination conditions, a loss is set. The range of 3500 yen to 20000 yen is set as the (7) repair request amount of the examination conditions.

  The operating system 54 reads the examination conditions (1) to (5) and (7) from the repair examination condition input screen shown in FIG. 15 (step S304). The read examination conditions (1) to (5) and (7) are sent to the real storage area 55 via the communication control device 21, the LAN 30, the communication control device 12, and the second system bus 56. Then, it is edited into the format of the repair examination condition table T4. Subsequently, the operating system 54 writes the repair examination condition table T4 edited in the real storage area 55 into the disk device 40 as the repair examination condition table T4 (step S305).

  Next, a method for analyzing repair examination conditions using a database storing examination repair request data will be described.

  In the operation described in the prior art described above, the results of one case and one case of repair examination are organized and recorded in a database in a code system in which causes and measures are subdivided. And the starting point of the idea of the present invention is that if the data accumulated in these databases is such that a large number of laws can be applied, a certain repair examination rule can be found from a statistical method.

  The present inventor analyzed the relationship between each item of the repair request data accumulated in the database and the repair request amount using a data mining technique. Here, the “data mining technique” refers to a technique for discovering a meaningful pattern such as regularity or relevance buried in a large amount of data. As a result, the inventor was able to specify repair request data with little variation in the repair request amount by the value and range of the item.

  The repair review rules are the same measures for repairs caused by the same cause of failure of similar products that can be specified by the value and range of items, and the same repair costs are incurred. The requirement is that it is necessary.

  As an example, the analysis results of the video deck, which is the product type with the largest number of repair examinations, will be described. The present inventor calculated the average repair amount per failure repair for each product type of the repair request data of the video deck. As a result, the average repair amount of Hi-Fi, BS built-in Hi-Fi, SVHS, and BS built-in SVHS was almost the same amount, and at the same time, the average repair amount of the entire VCR was almost the same amount.

  In addition, the present inventor calculated the average repair amount per failure repair for the repair request data that has been examined for each failure repair procedure. As a result, there were variations in treatment, but repairs handled by replacing parts were almost the same as the average repair amount for the entire VCR.

  Similarly, the present inventor calculates the average repair amount per failure repair for items such as product purchase price, manufacturer, failure symptom, failure cause, etc., and is close to the average repair amount of the entire video deck. I was able to identify the value and range of the item.

  The inventor confirmed that the repair request data that had been examined after satisfying the value and range of the code so that each item such as product type, manufacturer, failure treatment, etc. was close to the average repair amount of the entire video deck was repaired after the review. We found that the standard deviation of the forehead is small and the variation is small. The present inventor has stipulated conditions for extracting repair request data satisfying the value and range of this code as a repair examination rule. The repair inspection system according to the present invention automatically executes a repair inspection by a computer system in which the repair inspection rules are programmed.

  FIG. 16 shows a decision tree and a simulation result using a video deck as an example.

  In the decision tree, first, the product type is identified from the target video decks of the guarantee contract (step B1). Here, monaural, WVHS, digital, and 8 mm are excluded. Next, for example, company A, company B, and company F were specified as manufacturers (step B2). Subsequently, as a range of product purchase price, a range of less than 130,000 yen is specified (step B3), a failure due to wetting is excluded as a cause of failure (step B4), and measures taken for the failure are as follows: Only parts replacement was specified (step B5), and a range of 8,000 yen or more and less than 15,000 yen was specified as the range of the repair request amount (step B6). Then, segmentation is performed based on the repair request amount (step B7).

  The simulation results were as follows. The total number of VCR repair data reported over a period was 3,535. As a result of performing the repair examination by applying the decision tree, it was confirmed that 2,340 cases passed all the conditions and the repair request contents were appropriate. In FIG. 16, two line graphs indicating the number of repair request amount bands are displayed. In this line graph, the white square represents the number of repair requests. And the range limited by the black paint rhombus represents the repair request whose repair is confirmed.

  Next, the repair examination program P4 executed in the server device 10 will be described with reference to FIG.

  The repair examination program P4 is executed by the operating system 54 based on an execution request for the billing data recording (monthly) program P2 (step S218 in FIG. 13). The operating system 54 loads the repair examination program P4 requested by the application program registered in the disk device 40 into the real storage area 55 via the second system bus 56. The operating system 54 executes the instructions of the repair examination program P4 according to the flowchart shown in FIG.

  The operating system 54 reads the examination target product table T 7 from the disk device 40 and records it in the real storage area 55 via the second system bus 56. Then, the operating system 54 stores the checked repair request data recorded in the real storage area 55 in the process of the claim data recording (monthly) program P2 and the examination target product table recorded in the real storage area 55. Compare with T7 product type.

  The operating system 54 checks whether or not the product type of the checked repair request data is the product type specified in the product table to be examined (table that records the product type subject to the repair examination) T7, and performs the repair examination. It is determined whether or not the product is to be performed (step S401). If the product type of the checked repair request data is not the target (No in step S401), the operating system 54 checks whether there is an error in the checked repair request data (step S402). If there is no error in the checked repair request data (No in step S402), the operating system 54 sets “19” indicating “no error is not subject to examination” in the exit module code (step S403). Proceed to the exit.

  If there is an error in the checked repair request data (Yes in step S402), the operating system 54 sets "11" indicating "existing and not in error" in the exit module code (step S404). Then, the operating system 54 sets the segment code according to the error code (step S405), and proceeds to the module exit.

  On the other hand, when the product type of the checked repair request data is the product to be inspected (Yes in step S401), the operating system 54 determines the conditions (product type identification) specified from the repair inspection condition registration screen (FIG. 15). The repair examination condition table T4 specifying the cause of failure, the manufacturer, the action, etc. is read, and the necessary data is recorded in the real storage area 55 via the second system bus 56 (step S406). From here, the operating system 54 compares each item of the guaranteed product data in the guaranteed product table T5 corresponding to the checked repair request data with the repair examination condition recorded in step S406, and determines whether or not the condition is met. Judge.

  The operating system 54 first determines whether the product type of the checked repair request data exists in the registered product code in the repair examination condition table T4 (step S407). When the product type of the checked repair request data does not exist in the repair examination condition table T4 (No in step S407), the operating system 54 indicates “Excluded from examination by product” in the exit module code '31. 'Is set (step S408), and the process proceeds to step S424.

  When the product type of the checked repair request data exists in the repair examination condition table T4 (Yes in step S407), the operating system 54 makes the manufacturer code of the warranty product data in the warranty product table T5 corresponding to the checked repair request data. Is present in the manufacturer registered in the repair examination condition table T4 (step S409). If the manufacturer code of the warranty product data in the warranty product table T5 corresponding to the checked repair request data does not exist in the repair examination condition table T4 (No in step S409), the operating system 54 adds “Exit module code” to “Exit module code”. “32” indicating “excluded from examination by manufacturer” is set (step S410), and the process proceeds to step S424.

  When the manufacturer code of the warranty product data in the warranty product table T5 corresponding to the checked repair request data exists in the repair examination condition table T4 (Yes in step S409), the operating system 54 corresponds to the checked repair request data. It is determined whether or not the purchase price of the guaranteed product data in the guaranteed product table T5 is a price within the range registered in the repair examination condition table T4 (step S411). When the purchase price of the guaranteed product data in the guaranteed product table T5 corresponding to the checked repair request data is not included in the registered range of the repair examination condition table T4 (No in step S411), the operating system 54 Then, “33” indicating “excluded from examination by purchase price” is set in the Exit module code (step S412), and the process proceeds to step S424.

  When the purchase price of the guaranteed product data in the guaranteed product table T5 corresponding to the checked repair request data is included in the registered range of the repair examination condition table T4 (Yes in step S411), the operating system 54 It is determined whether or not the failure cause of the checked repair request data exists in the registered failure cause code in the repair examination condition table T4 (step S413). When the cause of failure of the checked repair request data does not exist in the repair examination condition table T4 (No in step S413), the operating system 54 indicates “excluded from examination due to failure cause” in the Exit module code. 34 'is set (step S414), and the process proceeds to step S424.

  When the cause of failure of the checked repair request data exists in the repair examination condition table T4 (Yes in step S413), the operating system 54 registers the failure action of the checked repair request data in the repair examination condition table T4. It is determined whether or not the fault handling code is present (step S415). When the failure treatment of the checked repair request data does not exist in the repair examination condition table T4 (No in step S415), the operating system 54 indicates “excluded from examination by failure treatment” in the exit module code. 35 'is set (step S416), and the process proceeds to step S424.

  When the failure treatment of the checked repair request data exists in the repair examination condition table T4 (Yes in step S415), the operating system 54 determines whether the failure treatment of the checked repair request data is supported by product replacement. Confirmation is made (step S417). In the case of product replacement (Yes in step S417), the operating system 54 sets “36” indicating “excluded from examination by product replacement” in the exit module code (step S418), and proceeds to step S424. .

  If it is not a product exchange (No in step S417), the operating system 54 determines whether the amount charged for the checked repair request data is within the registered range of the repair examination condition table T4 (step S419). If the repair request amount does not fall within the range (No in step S419), the operating system 54 sets “37” indicating “excluded from examination by the repair request amount” in the Exit module code (step S419). S420), the process proceeds to step S424.

  When the repair request amount is included in the range (Yes in step S419), the operating system 54 checks whether or not there is an error in the checked repair request data that passes all the repair examination conditions (step S419). S421). If there is an error (Yes in step S421), the operating system 54 sets “98” indicating that “the repair has been confirmed but an error exists” in the exit module code (step S422), and step S425. Proceed to

  If the checked repair request data has no error and passes all the examination conditions (No in step S421), the operating system 54 sets “99” indicating “fixed” to the exit module code (step 421). S423), go to the exit.

  In step S424, the operating system 54 checks whether there is an error in the checked repair request data that is determined to be unsuitable during the repair screening process and excluded from the screening target. If there is an error, the operating system 54 sets the segment code with the error code (step S425) and proceeds to the exit of the module.

  On the other hand, if there is no error in step S424 (No in step S424), the operating system 54 indicates that the checked repair request data is within the repair claim amount range of the repair examination condition table T4. 01 is set. If the amount is smaller than the lower limit, “02” is set in the segment code. If the amount is higher than the upper limit, “03” is set in the segment code (step S426). To the exit of the module.

  In this way, the segment code and the exit module code of the checked repair request data in the real storage area 55 are edited.

  Next, the examination result monitor program P5 executed in the server device 10 will be described with reference to FIG.

  The examination result monitor program P5 is executed by the operating system 54 based on the repair examination result monitor request from the terminal device 20. The operating system 54 loads the examination result monitor program P5 requested from the application program registered in the disk device 40 into the real storage area 55 via the second system bus 56. The operating system 54 executes the instruction of the examination result monitor program P5 according to the flowchart shown in FIG.

  The operating system 54 displays an examination result monitor screen on the terminal device 20 (step S501). FIG. 19 shows an example of a screening result monitor screen.

  Next, the operating system 54 records the accounting month input from the examination result monitor screen in the real storage area 55 via the second system bus 56 (step S502). Subsequently, the operating system 54 reads the examined repair request data T3 from the disk device 40 (step S503), and records it in the real storage area 55 via the second system bus 56.

  Next, the operating system 54 extracts examined repair request data for the designated accounting month (step S504). In other words, the operating system 54 determines whether or not the accounting date of the repair request data is the same as the designated accounting month.

  When the account date of the repair request data is the same as the designated accounting month (Yes in step S504), the operating system 54 exits the repair request data in the work area for each product type secured in the real storage area 55. The number of examined repair request data T3 is tabulated for each module code (step S505). In other words, the operating system 54 adds 1 to the tabulation table that matches the product type and the exit module code of the examined repair request data.

  Next, the operating system 54 totals the number of repair request data examined for each segment code of the repair request data in the work area for each product type secured in the real storage area 55 (step S506). . In other words, the operating system 54 adds 1 to the tabulation table that matches the product type and segment code of the examined repair request data.

  When all the examined repair request data has been read, the operating system 54 collects the result of counting by the exit module code and the segment code by product type from the real storage area 55, and sends the second system bus 56. Via, it is displayed on the monitor screen of the terminal device 20 (step S507).

  As is clear from FIG. 19, from the screening screen for the screening result, the number of cases judged to be appropriate after the repair screening for each product type and the screening conditions for the repair screening conditions are judged to be inappropriate and subject to automatic repair screening. It is possible to check the number of exit modules / codes and the number of segments / codes that indicate whether or not they are excluded.

  Needless to say, the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the present invention. For example, in the above-described embodiment, the received repair request data is stored in the disk device of the server, but it goes without saying that it may be stored in other storage means. In the embodiment described above, the checked repair request data is stored in the real storage area, but it is needless to say that it may be stored in other storage means.

  The applicant introduced a repair examination system according to the present invention in June 2002. The monthly average number of repair requests during the 10 months after installation was approximately 20,800. Of these, about 12,600 cases, corresponding to about 61%, were automatically repaired by the repair screening system according to the present invention. Only the remaining 39% of the repair request data was improved to be manually repaired by the repair reviewer, resulting in a dramatic reduction in the work of the repair reviewer.

  The table and graph shown in FIG. 20 show the number of repair requests processed for 6 months before the introduction of the repair inspection system and 10 months after the introduction, and the processing time of the person in charge of repair inspection. Before introducing this repair inspection system, it took 120 hours on average for inspection of repair inspection, but it can be seen that it has changed to 66 hours on average after introduction.

  As a result, the problem that the amount of work increased in proportion to the number of repair requests was solved.

  Repair request data excluded from the scope of repair inspection by the computer (repair inspection system) is classified by segment code and exit module code. Therefore, the repair examiner can specify repair request data by specifying the product type, exit module code, and segment code from the terminal device. As a result, manual repair screening, which has conventionally been performed in the order of acceptance, can be performed manually from a terminal screen on similar repair request data segmented by product type, thus improving accuracy and efficiency.

  As a result, the variation in the repair examination results is reduced, and a more uniform and accurate repair examination result can be obtained speedily.

  In this way, it is possible to solve the problems in the conventional manual repair examination, reduce costs and improve customer service.

It is a block diagram which shows the hardware constitutions of the repair examination system which concerns on one embodiment of this invention. It is a figure which shows one structural example of the input repair request data used in the repair examination system shown by FIG. It is a block diagram which shows the system outline | summary of the repair examination system shown in FIG. It is a figure which shows one structural example of the reception repair request data used in the repair examination system shown by FIG. It is a figure which shows one structural example of the examined repair request data used in the repair examination system shown by FIG. It is a figure which shows the example of 1 structure of the repair examination condition table used in the repair examination system shown by FIG. It is a figure which shows one specific example of the repair examination condition table shown by FIG. It is a figure which shows the example of 1 structure of a guarantee product table used in the repair examination system shown by FIG. It is a figure which shows one structural example of the various code tables used in the repair examination system shown by FIG. FIG. 10 is a diagram illustrating a specific example of codes in various code tables illustrated in FIG. 9. It is a figure which shows the example of 1 structure of the inspection object product table used in the repair inspection system shown by FIG. It is a flowchart which shows the claim data recording (daily) program which is one of the application programs for implement | achieving the repair examination system shown in FIG. It is a flowchart which shows the claim data recording (monthly) program which is one of the application programs for implement | achieving the repair examination system shown in FIG. It is a flowchart which shows the repair screening condition registration program which is one of the application programs for implement | achieving the repair screening system shown in FIG. It is a figure which shows an example of the terminal screen which registers the repair examination condition of the repair request data for every product type in the repair examination condition registration program shown in FIG. It is a figure which shows the decision tree which made the video deck an example, and its simulation result. It is a flowchart which shows the repair screening program which is one of the application programs for implement | achieving the repair screening system shown in FIG. It is a flowchart which shows the examination result monitor program which is one of the application programs for implement | achieving the repair examination system shown in FIG. It is a figure which shows an example of the screen for an examination result monitor in the examination result monitor program shown in FIG. 2 is a table and a graph showing the number of repair requests processed before and after the introduction of the repair screening system shown in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Server apparatus 11, 12 Communication control apparatus 20 Terminal apparatus 21 Communication control apparatus 30 LAN
40 disk unit 51 CPU
52 System Bus 53 Database Management System 54 Operating System (OS)
55 Real storage (memory)
56 System bus T1 Input repair request data T2 Received repair request data T3 Reviewed repair request data T4 Repair review condition table T5 Warranty product table T6 Various code tables T7 Review target product table P1 Claim data recording (daily) program P2 Request Data recording (monthly) program P3 Repair examination condition registration program P4 Repair examination program P5 Examination result monitoring program

Claims (10)

  A repair inspection system for performing a repair inspection of whether or not the content of repair request data related to home appliances in an extended warranty contract is valid, comprising: a server; and a terminal device connected to the server via a network. The server includes an operating system, receiving means for receiving repair request data transferred from a customer company through a communication line, a data area for storing the repair request data received by the receiving means, and a plurality of applications The first storage means having a program area for storing a program and the form of the repair request content of the repair request data read from the first storage means in response to the execution request from the terminal device are valid. Check means for checking whether or not there is a check means checked by the check means Based on second storage means for storing repair request data and product information in the guaranteed product table corresponding to the checked repair request data, and a repair examination condition that prescribes the appropriateness of repair for each product type And checking whether the substance of the repair request contents of the checked repair request data and the product information read from the second storage means is valid, and if valid, a code that is valid And an examination unit that outputs examination repair request data attached with an examination result indicating a code indicating an unsuitable type if not appropriate, and the operating system executes the application program from the terminal device. Based on the request, among the plurality of application programs stored in the program area of the first storage means Repair examination system characterized by being configured to load the application program corresponding to et the request to the second storage means.   The receiving means receives the repair request data transferred from the customer company through the communication line in response to the repair request data processing request from the terminal device, and stores it in the data area of the first storage means. The computer system according to claim 1, wherein the program is realized by a daily billing data recording program that is one of application programs stored in the program area of the first storage unit. Repair examination system.   In response to a repair request data processing request from the terminal device, the check means reads repair request data from the first storage means of the server and checks whether the format of the repair request content is valid The repair examination system according to claim 1, which is realized by a next billing data recording program.   The monthly billing data recording program further includes a function of storing checked repair billing data and warranty product data of a corresponding warranty product table in the second storage unit of the server. The repair examination system according to claim 3.   Based on the repair examination condition that prescribes the validity of repair for each product type determined in advance, the examination means is the entity of the repair request contents of the checked repair request data and the warranty product data in the corresponding warranty product table If it is valid, the examination result indicating the code that is valid, and if not valid, the examination request data that includes the examination result indicating the code indicating the inappropriate type is attached. The system is implemented by a repair examination program, which is one of application programs stored in the program area of the first storage means, configured to output Repair examination system.   The first storage means is configured to tabulate information recording the examination result added to the examined repair request data, and to display the result of aggregation for each product type on the display device of the terminal device, 2. The repair examination system according to claim 1, further comprising an examination result monitor program which is one of application programs stored in the program area of the first storage means.   The apparatus further comprises registration means for registering the repair examination condition determined by analyzing the repair claim data item and the repair claim amount in response to the repair examination condition registration request from the terminal device. The repair examination system according to Item 1.   8. The repair examination according to claim 7, wherein the registration unit is realized by a repair examination condition registration program which is one of application programs stored in the program area of the first storage unit. system.   9. The repair examination system according to claim 8, wherein the repair examination condition is stored in the data area of the first storage means as a repair examination condition table.   The operating system allocates necessary hardware devices in the execution order of the specific program stored in the program area of the first storage means and executes instructions, and when all instructions are executed, 10. The terminal device according to claim 1, wherein the terminal device is configured to notify the end of program execution and to release the hardware device reserved for executing the application program. The repair examination system according to any one of the above.

Images