JPH04287274A - System for controlling quality information of electronic equipment mounted on printed board - Google Patents

Abstract

PURPOSE:To recognize the failure rate of electronic equipment mounted on a printed board by types and parts and to unitarily control the fault history of the equipment by providing a mounting history and component tables of the printed board and receiving information from a production control line in an on-line state. CONSTITUTION:Ordering data and mounting designing data are respectively supplied to a floor control system 1 from a production control line 6 and CAD system 7 and an order/PCB mounting position file 14 is prepared. Received goods inspected results and warehoused/delivered result data are sent to the system 1 from a warehousing/delivering section 2 and stored in a warehousing/ delivering file 12. Data from a PCB assembly testing section 3 and PCB mounting/device testing section 4 are respectively stored in a PCB manufacturing/parts mounting file 13 and PCB mounted result file 15. When a fault occurs in a product, a customer facility 5 stores the fault data in a field fault file 16. From these files 12-16, the failure rate can be calculated and the influential extent of a fault can be investigated.

Description

[Detailed description of the invention]

0001

[Field of Industrial Application] The present invention relates to a quality information management system for electronic equipment equipped with printed boards, and in particular, information on the printed board mounting history of electronic equipment that mainly uses printed boards and failure information that has occurred during operation at the delivery destination. Regarding a quality information management system that utilizes field failure information.

[0002] When a frame is constructed by mounting a device (unit) such as a communication device or an information processing device assembled with printed circuit boards on a shelf, the design conditions of the device are based on the customer's order (
The functions and scale of each product differed depending on the requirements (requirements) and the existence of various options, and the circuit design was frequently changed. Since there is no data on the shipping history of what kind of printed boards (type, number of editions, etc.) are used, where and how many are used in these various electronic devices, it is difficult to calculate the failure rate of printed boards for quality control purposes. It takes a huge amount of work to investigate and trace the location of each part in which equipment when replacing a defective part that is being manufactured or used in a shipped product when a defective part is discovered. It takes.

0003

2. Description of the Related Art FIG. 11 is an explanatory diagram of a conventional example. This example illustrates conventional manufacturing processes and information handling for the case of integrated circuits (ICs). When an IC is first delivered, an acceptance inspection is performed in the receiving/acceptance inspection process 90. At this time, the data 90b of the IC name and rod code for each IC is held as a history information file 90a together with the input, date of arrival, quantity, etc. Next, each IC is transferred to a parts warehouse 91 in the production department. At this time, a history information file 91a for managing parts in a first-in, first-out format is created. In this file 91a, the date, number of arrivals, number of departures, inventory, etc. are recorded for each type of IC corresponding to each date, and can be output in paper format 91b.

Next, the production department produces printed boards (PCBs).
The process moves to an assembly test step 92, in which ICs are taken out from the parts warehouse 91, mounted on printed boards on which various ICs are wired, and tested. At this time, a history information file 92a for this production department is created. Next, print the printed circuit board (PWCB-Print Wired Circuit) on which this part is mounted.
t Board - (hereinafter also referred to as PCB) is stored in the PCB warehouse 93 of the production department. At this time, a first-in, first-out file (or paper ledger) 93a is created as reservation information (the contents of this file are
(Stores the assembly serial number for CB).

Next, the PCBs are taken out from the PCB warehouse 93, and the device is assembled and tested in a device assembly test step 94. Here, a unit is manufactured by mounting a PCB on a shelf, and assembly such as mounting it on a frame is performed, and a test is also performed. In this case, instructions are given from each customer to provide the required functions, and the corresponding PCB is mounted in a predetermined position according to the instructions, a device with the specified specifications is assembled, and a test is conducted. At this time, a slip 94a displaying the details of the device is created for each customer, and a delivery date list 94b is created. These slips and documents are handed over together with the equipment when it is delivered to the customer.

[0006]

[Problems to be Solved by the Invention] As mentioned above, in the conventional system, the shipping history of printed circuit boards is not converted into data, and in order to control the quality of parts, it is necessary to calculate the actual failure rate by model and customer in the field. To determine the failure rate under operating conditions, it is necessary to go to the site (where the equipment is delivered), investigate the delivered equipment, unfold (disassemble) the parts used in each equipment, and calculate the number of parts. There is a need. The failure rate is determined from this quantity, operating time, and number of failures in the field. However, in reality, it is impossible to manually inspect delivered products in the field and examine the parts used in the investigation due to the huge number of parts used.There is a problem in that it is not possible to grasp the failure rate of individual parts or equipment. was there.

On the other hand, when it is later discovered that a component lot defect (defect in the manufacturing lot of parts) or manufacturing lot defect (defect during assembly of printed circuit boards) has occurred, and action is taken to replace the part in the field. As the shipping history of printed boards was not digitized (in paper format such as slips), the accuracy was poor, and the delivery destination was estimated based on the date of receipt of parts and the date of assembly of printed boards, and inspections and replacements were performed. For this reason, there was a problem in that it was difficult to achieve a 100% recovery rate for defective parts. The present invention provides quality information management for electronic devices equipped with printed circuit boards, which makes it possible to easily grasp the failure rate of each component or printed board of electronic devices that mainly use printed boards, and the extent to which the product is affected when a defective component occurs. The purpose is to provide a system.

[0008]

[Means for Solving the Problems] FIG. 1 is a diagram showing the overall principle configuration of the present invention. In FIG. 1, 1 is a floor control system installed in a factory (or a location away from the factory), 10 is a tracking processing unit that manages quality information, 11 is a failure rate calculation unit, and 12 is a parts receiving and processing unit. Input/output file, 13 is PCB manufacturing and component mounting file, 14 is order and PCB mounting position file, 15 is P
The CB mounting result file 16 is a field failure file.

[0009] 2 to 4 are each department on the manufacturing factory side, and data is transmitted and received online with the floor control system, 2 is the parts receiving/input/output department, 3 is the printed board assembly test department, and 4 is the printed board mounting department. -Equipment testing department. 5 is the customer equipment to which the product is delivered. Reference numeral 6 indicates a production management system, 7 indicates a CAD system for designing parts, printed circuit boards, equipment mounting, etc., and 8 indicates each manufacturing base connected via a network.

[0010] The present invention is capable of obtaining field failure data by providing printed circuit board (PCB) mounting history and printed circuit board component list, and then using that information to grasp the failure rate of each model and component. Can be done. Additionally, when a lot failure occurs, the extent of the impact can be known by centrally managing the history in the manufacturing process and the shipping history of printed circuit boards.

[0011]

[Operation] Orders and ordering data are input to the floor control system 1 from the production control system 6, and design data for parts, PCB component mounting, and equipment supply mounting is supplied to the floor control system 1 from the CAD system 7. As a result, the order and PCB mounting position file 14
is created, and this information is supplied to each department within the factory as instruction information. When the parts corresponding to the order are received in the receiving/in/out department 2 of the factory, they are inspected and then stored in a parts warehouse, from where they are delivered to the next PCB assembly testing department 3. When the receiving/warehousing unit 2 outputs the data of the receiving inspection results and the warehousing/distributing results to the floor control system 1, it is stored in the parts receiving/warehousing/distributing file 12.

[0012] The PCB assembly testing department 3 processes the parts that have been delivered to the PC.
After being mounted and assembled on PCB, it is tested and then stored in the PCB warehouse. Data on the manufacturing progress at this time is stored in the PCB manufacturing and component mounting file 13. Next, the PCB mounting/device testing section 4 carries out a step of mounting the PCB on the shelf, and performs a device test after mounting. At this time, if a defective product is detected, the PCB is mounted in a different position, or the type of PCB is different from the specified one, the PCB is replaced with the correct one. From this PCB mounting/equipment testing section 4, data on PCB mounting results and replacement results are sent to the floor control system 1 and stored in a PCB mounting result file 15.

In the customer equipment 5, when a failure or the like occurs while operating the product, it is output to the floor control system 1 as field failure information. This is stored as field fault file 16. The tracking processing unit 10 in the floor control system 1 reconstructs each file, that is, the parts receiving and warehousing file 12, the PCB manufacturing and parts mounting file 13, the PCB mounting result file 15, and the field failure file 16. You can search for the data you need.

[0014] In other words, when a parts lot failure or manufacturing defect failure occurs, the tracking processing unit 10 investigates the extent of its influence, and the files 12, 13, 15 are
By tracking using , it is possible to search for and output how much information is being used in which device and at which location. In addition, based on the failure status in the field stored in the field failure file 16, the failure rate calculation unit 11 calculates the actual failure rate for each product model and the failure rate for each printed board for the data in each file 12 to 15. be able to.

[0015]

Embodiment FIG. 2 is a block diagram of a floor control system in which the present invention is implemented, and FIG. 3 is a block diagram of an embodiment of an information unified management and retrieval mechanism in tracking processing. In the floor control system in Figure 2 (1 in Figure 1), 20 is a central processing unit (CPU), 21 is an interface (I/F) for communicating with an external computer, etc.
), 22 is a memory (stores programs, etc.), 23 is a terminal device with a display, 24 is a printer that prints search data and investigation results, 25 is a parts receiving data file, 26 is a parts warehouse data file, 27 is a printed board (PCB) manufacturing process data file, 28 is a printed board mounting history data file, 29 is a field failure data file, 30 is a tracking data file, 31
is an actual failure rate data file, 32 is an interface (I/F) for communicating with the PCB finished product automated warehouse 33 (its control unit), and 34 is an interface (I/F) for communicating with the CPU of the testing machine 35. It is.

The above-mentioned floor control system 1 is provided with a tracking processing unit that realizes a quality information management system for electronic devices mounted on printed circuit boards, and FIG. 3 shows the configuration of an embodiment of the information unified management and search mechanism in this tracking processing Explain using. In Figure 3, the parts acceptance inspection (
The parts name, rod code, quantity, etc. generated by the process (executed in the receiving/input/output section 2 in Fig. 1) are input to the floor control system from the acceptance inspection position of the factory, and the parts receiving data file 25 (Fig. 2) is processed by the receiving process 36. is stored in When parts are placed in and out of the parts warehouse (installed in the receiving/input/output section 2), the in/out data is input to the floor control system 1, the warehouse processing 37 is executed, and the parts in/out data is processed. This data is stored in file 26.

Furthermore, when the PCB is assembled (components are mounted) during PCB assembly (executed in PCB assembly test 3 in FIG. 1), the generated assembly data is input to the floor control system 1 and the PCB processing process 38 is executed. The data is stored in the printed board (PCB) manufacturing process data file 27. Next, when the PCBs enter and exit the PCB warehouse (installed at 3 in FIG. 1), PCB entry and exit data is generated.

[0018] Furthermore, when mounting result data is generated during equipment mounting (executed in the PCB mounting/equipment testing section 4 in Fig. 1) and PCB replacement is executed during the equipment test (also executed in the PCB mounting/equipment testing section 4). Replacement data associated with replacement (extracted PCB and newly inserted PCB)
information) occurs. Of these, except for the storage/output data (this data is used for PCB warehouse management), the mounting result data and replacement data are processed in the device processing 39 and stored in the PCB mounting history data file 28.

The tracking processing unit 10 in FIG.
5, 26, 27, and 28 to search for necessary related information and output necessary data. In other words, as shown in ■ in Figure 3, when component defect A occurs and the component name and lot code are input from the terminal device 23, the name of the PCB that uses the component and the name of this component are input using the related data file. Search for the delivery destination (delivery station) of the installed equipment and select terminal device 2.
Display on display 3 (or output to printer 24)
do.

[0020] In this case, the tracking processing unit 10 extracts the quantity, storage date, number of shipments, date of shipment, assembly serial number, etc. of the component with the relevant name and the corresponding lot code from the related data file, and stores the PCB. From the manufacturing process data file 27 and PCB mounting history data file 28, the serial number, version number, manufacturing date, assembly serial number, equipment name, delivery destination (station name), mounting position, etc. of the PCB on which the relevant component is mounted are obtained for each PCB. Each board is examined and the name of the PCB on which the defective part is mounted and the delivery station of the equipment using that PCB are output.

Similarly, as shown in FIG. 3, the terminal device 23
If you enter the name and manufacturing date of the defective PCB from
Search and output the delivery destination and mounting position of the device using the corresponding PCB. Furthermore, as shown in ■, when there is a station status inquiry from the terminal device 23 (when you want to know the version number of each PCB used in equipment delivered to a certain station), this time the related data file is sent based on the station name. The search is performed and the version numbers of all PCBs delivered to the corresponding station are output as the search results.

Next, FIG. 4 shows a processing flow for investigating the range of influence of a lot failure, FIG. 5 shows an example of data display of the investigation results, and FIG. 6 shows an example of the structure of input data used in the processing. In Figure 4, as a specific example, if a part lot defect occurs in a part with part code IC11 and lot code 901A00 (40 in Figure 4), first find the purchase serial number of the part from the parts acceptance data (41 in Figure 4). . An example of this parts receipt data (see 25 in Figure 2) is shown in Figure 6 (a), and the data is divided into items such as part name, date of receipt, quantity received, purchase serial number, and lot code. is stored, and in this example, it can be seen that the purchased part number is "PA01".

Next, parts storage/output data (see 26 in FIG. 2)
Then, it is found out which assembly serial number the purchase serial number of the relevant part was issued from the warehouse (42). As shown in the example of part storage/output data in Figure 6 (b), the purchase serial number and assembly serial number are included along with the part name, storage/output date, number of storage/outputs, etc. The assembly serial number of the part with the serial number is “N”
G00001NA". Next, the PC
From the B manufacturing process data (see 27 in Figure 2), find the PCB drawing number, manufacturing date, and manufacturing model (number of the same type of device) of the relevant assembly serial number (43 in Figure 2). PC in Figure 6(d)
An example of B manufacturing process data is shown, which includes the assembly serial number "NG00001NA", which includes the PCB drawing number (E20B-4514-R000).
, manufacturing date (9012), and manufacturing number (0001).

Next, loading history data (see 28 in FIG. 2)
Find the mounting shelf and delivery destination of the relevant PCB (
44). An example of the mounting history data is shown in FIG. 6(c), and in this example, information on the shelf on which the PCB with the PCB drawing number, manufacturing date, and manufacturing number found in step 43 is loaded and the delivery address (XX telephone number) are shown. stations) can be found. In this way, the results of the search process are stored in the tracking data file (30 in FIG. 2) and displayed on the display of the terminal device (23 in FIG. 2) as shown in FIG. In this way, the scope of impact when a lot failure occurs can be investigated instantly online (in the case of a component lot defect, the part name and lot code; in the case of a manufacturing defect, the PCB name and manufacturing date).

7 and 8 are processing flows for calculating actual failure rates, FIG. 9 is a display example of calculation results, and FIG. 10 is an example of each input data used for calculation. The actual failure rate is calculated using the two A. B. It is composed of three processing flows: two processing flows shown as , and one processing flow shown in FIG. 8 .

A. in FIG. is the processing flow for counting the number of component failures. When started, the number of failures for each component is totaled from the field failure data (see 29 in Figure 2) (70 in Figure 7).
,finish. FIG. 10(a) shows a specific example of field failure data. This field fault data is fault data that occurred and was found at the delivery destination, and consists of the name of the PCB where the fault occurred, drawing number, version number, etc., as well as the delivery destination, shelf information, part name, etc. In this example, when the component name of the failure is "IC11", the number of failures of the component is summed up from each field failure data, and in this case, a total of 51 failures (referred to as M) is obtained.

Next, B. of FIG. The processing flow for calculating the operation time of parts shown in will be explained. First, the loading history data (
Match the PCB drawing number and version number (see 28 in Figure 2) with the component data (71 in B.). FIG. 10(b) shows an example of installation history data, and FIG. 10(c) shows an example of a component list (not provided in FIG. 2, but created separately by key input, etc.). In this step 71, the PCB drawing number containing the specific part (in this example, part name IC11) and the PCB
Find the version number from the component list and find the PCB that matches this.
is detected from installation history data.

Next, while counting the number of parts used,
The operating time is calculated by subtracting the delivery date from the current day (72). The number of parts used is determined from the component list shown in FIG. 10(c) and the mounting history data (b), and the delivery date is stored in the mounting history data and can be calculated. Furthermore, the operating hours (component hours) for each part are totaled (73). In this example,
The operating time (assumed to be H) of the part name "IC11" is 99.
99 is required.

To explain the processing flow for calculating the actual failure rate shown in FIG. 8, the processing flow shown in A. The number of failures M for each component obtained by B. The failure rate E is obtained by dividing by the operating time H calculated by (74 in FIG. 8). This calculation is repeated for each part (75). An example of displaying the results of this calculation is shown in FIG. In this way, the actual failure rate for each product type and the failure rate for each printed board can be determined based on the failure occurrence situation in the field, and the actual failure rate for parts can also be determined based on the component list of the printed circuit board. Can be done.

[0030]

[Effects of the Invention] According to the present invention, the actual failure rate of parts and equipment can be grasped, and this can be utilized in designing the next product. In addition, it can be used to calculate standards for the number of maintenance parts in stock at the time of product discontinuation and to change acceptance inspection methods. In addition, when a lot defect occurs, manual work is not required as in the past, which reduces the time needed to investigate the scope of influence, and significantly reduces the time it takes to start work such as replacing parts in the field, which improves equipment reliability and improves customer service. serviceability can be improved.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing the general principle configuration of the present invention.

FIG. 2 is a configuration diagram of a floor control system in which the present invention is implemented.

FIG. 3 is a configuration diagram of an embodiment of an information unified management and search mechanism in tracking processing.

FIG. 4 is a processing flow of investigating the range of influence of lot failure.

FIG. 5 is an example of data display of results of investigation of lot failure influence range.

FIG. 6 is an example of the configuration of input data used for processing the lot failure influence range investigation process.

FIG. 7 is a processing flow for calculating actual failure rate; B. is the processing flow for counting the number of component failures. is a processing flow for calculating the operation time of parts.

FIG. 8 is a processing flow for calculating actual failure rate.

FIG. 9 is a display example of the calculation result of the actual failure rate.

FIG. 10 is an example of each input data used to calculate the actual failure rate.

FIG. 11 is an explanatory diagram of a conventional example.

[Explanation of symbols]

1 Floor control system 10
Tracking processing unit 11 Failure rate calculation unit 12 Parts receiving and warehousing file 13
PCB manufacturing and component mounting file 14 Order and PCB mounting position file 15 PCB mounting result file 16 Field failure file

Claims (3)

[Claims] [Claim 1] In a quality information management system for electronic devices mounted on printed boards, information generated at each stage of parts acceptance, parts storage, printed board assembly, and printed board mounting on equipment is accepted online, and each Equipped with a floor control system that stores data in corresponding data files, the floor control system uses field failure data that has occurred at the delivery destination and the data files for each of the manufacturing processes mentioned above to track actual failures of product models, printed circuit boards, and parts. A quality information management system for electronic equipment equipped with a printed board, characterized by comprising means for calculating and outputting a rate. [Claim 2] In claim 1, the plurality of data files that store data generated at each stage of manufacturing include a loading history data file representing the contents loaded in each device and the shipping destination at the time of shipping the device; A quality information management system for electronic devices equipped with printed circuit boards, characterized by comprising a component list showing parts included in each device. [Claim 3] In a quality information management system for electronic devices equipped with printed boards, receiving data generated when parts are received, data on entering and leaving a parts warehouse, manufacturing process data generated when assembling parts onto printed boards, and information on equipment. Equipped with a data file that stores each piece of mounting history data that occurs when mounting printed boards, and when a lot failure of parts or printed boards occurs, each of the above data files is used to identify the delivery destination and equipment of the corresponding parts or printed boards. 1. A quality information management system for electronic devices equipped with printed circuit boards, characterized by comprising means for searching and outputting a range of influence including a usage position within the system.