JPH06162036A - Product information management system - Google Patents

Abstract

PURPOSE:To unify details of the product loaded contents from an equipment mounting design to manufacture, inspection and shipment by preparing an appa ratus mounting file corresponding to an order by using a design data file and a design know-how data file in each separate customer order unit. CONSTITUTION:An equipment mounting design part 10 executes functions of an arrangement design of the equipment and the check of each design condition, etc., based on order information of a customer order file 13a and an estimate in accordance with a request of a design of a conversational format in a terminal equipment 2. In this case, a design data file 13b and design know-how file 13c are used, and an equipment mounting change file 14a is prepared. Also, when the contents of the design data file 13b are changed, a design change/ version number file 14b is prepared, based on design change information, in a design change information managing part 11a and a design version number information managing part 11b of a design change managing part 11. Subsequently, from this information, basic information of a version number unit of an electronic circuit printed board is prepared in a PKG basic information file 14c.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a product information management system, and more particularly, to a device design which comprises an electronic circuit printed circuit board unit, a device unit mounting the same, and a device rack, and which requires a device mounting design or the like to meet customer needs. It relates to a total product information management system that can centrally manage the detailed contents of equipment from the process to manufacturing / inspection and field (equipment installation site).

In the field of communication equipment and the like, there are a wide variety of equipment combinations and installation conditions due to differences in communication systems in different countries and different conditions (options) required by customers. ) Corresponding to the equipment mounting design is required. In addition, after the equipment is delivered, there is a constant demand for additional functions and lines due to the customer's requirements, and it is indispensable to accurately grasp the history information of the delivered equipment, and the establishment of an information management system for it. Is required. For this reason, it is necessary to centrally manage product installation information such as the collection of device history information during manufacturing / inspection and field information after device delivery from the design process of the device mounting diagram for each customer and order.

[0003]

2. Description of the Related Art FIG. 23 is an explanatory view of a conventional method for mounting and designing a device for each customer, FIG. 24 is an explanatory view of a conventional method of collecting manufacturing / inspection / manufacturing history information, and FIG. 25 is a conventional delivery device information management method. FIG. As shown in FIG. 23, in the conventional equipment packaging design for a customer, an order sheet b is created from a quotation / order information a. Further, the parts arrangement list, the mounting drawing, and the structure information d are output on paper by CAD using the parts arrangement information and the basic mounting information c. Based on these b and d, the designer uses the know-how and the manual e that he has as knowledge to perform the design work f manually while confirming and checking each item, and for manufacturing and facility design. A drawing g such as a device mounting drawing is created. For this work, it was necessary to check the quantity of equipment against the order and check against the mounting drawings, which required enormous design man-hours.

Next, as shown in FIG. 24, in the conventional manufacturing / inspection / collection of manufacturing history information, an electronic circuit printed board unit (PKG) a or a shelf (SH: unit mounting equipment) b for each customer order is used. The electronic circuit printed circuit board unit mounting c was carried out while delivering goods on an order basis and distributing them to each device unit. Therefore, it takes time to align the surfaces of the electronic circuit printed circuit board units, and the shipping history information d
Had to manually read the total version number and list it on the shipping list.

Further, as shown in FIG. 25, in the conventional management of delivered equipment information, order information, design information, and design information are set for the total version number information of the electronic circuit printed board collected by the shipping list a from the inspection section. All sheets b to d created by the change information are manually put into the computer (e),
A database f for delivering device information management has been constructed, which requires enormous work man-hours.

[0006]

As described above, according to the conventional method, the product management of electronic devices, which requires the device mounting design for each customer and for each order and in which the delivery history management is indispensable, is performed individually in each department. However, there is a problem that a huge number of man-hours are required because of going to the factory. In addition, since each department works individually, there is a problem in terms of ensuring the quality of the delivered device history information because mutual cooperation is not sufficient. It is an object of the present invention to provide a product information management system that can unify details of product mounting contents from device mounting design to manufacturing / inspection / shipment for each customer / order.

[0007]

FIG. 1 is a diagram showing the overall principle configuration of the present invention. In FIG. 1, 1 is a center device for managing and processing design information, 2 is a terminal device for performing design and management work, 3 is part management / manufacturing management control provided in the manufacturing department, and mounting history management. It is a floor control system that controls and processes such as. In the center device 1, reference numeral 10 is a device mounting design section that performs processing such as device mounting design based on each file data 13 of customer order, design data, and design know-how, and 11 is a management section related to design change. Design change information management unit 11a for managing
And a design version number information management unit 11b that manages design version number information, 12 is a delivered device information management unit that manages information about devices to be shipped to customers, and 13 is each data of customer order, design data, and design know-how. Files 13a-13c
Is a design data file constituted by, a device mounting diagram designed by the device mounting design unit 10, a design change management unit 11
Each data file 14a of the package (PKG) basic information composed of the design change (displayed on EC) / version number and the number of printed boards and the information about the parts to be attached, created in
14c is a manufacturing data file configured by 14c. 15
Is a data file 15 of delivery history information sent from the factory
It is an interface unit on the side of the center device that includes a.

The terminal device 2 is provided with a display unit for designing in a conversational manner, a keyboard, a printer for outputting various materials such as device mounting drawings, and an input / output unit for other necessary information.
In the floor control system 3 on the factory side, 3
0 is a manufacturing history information file 30a (the same as the above 15a) which stores various kinds of information for interfacing with the center device 1, that is, information of all printed boards mounted on the completed device, and is sent from the center device 1. An interface unit including a design change (EC) / version number information file 30b (same as 14b above) and a device mounting diagram file (same as 14a above), 31 performs processing of all information in the factory and control of devices The processing device 32 is a product information management unit that controls product information management in the processing device 31.

Further, 33 is an electronic circuit printed circuit board unit assembly part which is assembled by the parts taken out by the parts arrangement from the production management system, 34 is a shelf assembly part which is assembled by the parts supplied by the parts arrangement, and 35 is a package to the shelf. Device / unit part that mounts 3
Reference numeral 6 denotes a device rack mounting unit that mounts the shelf on the device rack.
The present invention centrally manages product information from mounting design of electronic equipment in which an electronic circuit printed circuit board unit is optionally mounted for each customer to assembly test and field shipping.

[0010]

The device mounting design section 10 of the center device 1 responds to a request for conversational design in the terminal device 2, based on the order information and the estimate of the customer order file 13a, the device layout design and the check of each design condition. Perform the function of. At this time, the design data file 13b and the design know-how file 13c are used. Thus, the device mounting diagram file 1
4a is created. When the contents of the design data file 13b are changed, the design change information management unit 11a and the design version number information management unit 11b of the design change management unit 11 design change / version number file 1 based on the design change information.
4b is created, and from this information, basic information (history information) of electronic circuit printed circuit board unit in version number unit is PKG.
It is created in the basic information file 14c. Therefore, a system is created that can manage design changes and version management in a unified manner at the same time as design changes.

In the floor control system 3 of the factory, respective parts taken out from a conventional production management system (not shown) by arrangement of parts are supplied to the electronic circuit printed board unit 33 and the shelf assembly part 34, respectively. Each can be assembled as a single unit. The processing device 31 uses the device mounting diagram file 30c sent from the center device 1 provided in the interface unit 30, and controls the product information management unit 32 to complete the unit test of the electronic circuit printed board unit assembly unit 33. Electronic circuit printed circuit board units are unloaded from the automated warehouse in order of the mounting positions in the apparatus, and the robots are automatically controlled and mounted on the assembled shelves output from the shelf assembling unit 34.

In this way, the electronic circuit printed board unit and the like are mounted, the device / unit is manufactured in the device / unit section 35, and each device / unit is mounted on the frame in the device rack mounting section 36. In this mounting work, the mounting history information generated in the device / unit part 35 and the device rack mounting part 36 is collected in the processing device 31, and the manufacturing history information file 30a is created. The contents of this file are sent to the center device 1 and the delivery history information file 15
a is created. When the design history is changed or folded after the manufacturing history information file 30a is created, the manufacturing history information file 30a is updated by rereading the mounting history information.
From the manufacturing history information file 30a and the version number history information of the electronic circuit printed board unit (stored in the file 30b), it is possible to perform various tabulations for devices shipped (which are called field products) and operated by customers. In addition, the actual results such as the FIT number (failure rate) are tabulated based on the failure information generated in the field, and the results can be used for parts selection and parts inspection.

[0013]

2 is a system configuration diagram of an embodiment of the present invention. In FIG. 2, 1 is a center computer (corresponding to the center device 1 in FIG. 1), and 3 is a floor control and roll system (similar to 3 in FIG. 1). Center computer 1
The CPU 16, the memory 17, the terminal device 27, the printer 28, and various files 18 to 22 and 24 to 26 for manufacturing / managing design, manufacturing, shipping, history information and the like are provided in the terminal for designing / managing. An apparatus 27 and a printer 28 are used, and data is transferred online with an interface (I / F) 23 to the floor control apparatus on the factory side.

In the information file, 18 is a CAD parts arrangement information file (not included in FIG. 1) created in the design to arrange the necessary parts based on the design information,
Reference numeral 19 denotes a CAD version number management information file (corresponding to a part of 14b in FIG. 1) in which version number information corresponding to a change of a printed board or device is stored, and 20 denotes a design change processing information file (one of 14b in FIG. 1). , 21 is a CAD electronic circuit printed board (displayed as PWCB: Print Wired Circuit Board))
Equipment basic information file (corresponding to 14c in FIG. 1), 22 is a customer order information file (13a in FIG. 1), 23 is an interface for communicating with the factory side (floor control system 3), and 24 is to the factory side Design change notification information file for notification (corresponding to a part of 14b in FIG. 1), 25 is a device mounting information file for each customer (14 in FIG. 1)
a), 26 is shipping history information for each customer (15a in FIG. 1)
It corresponds to).

Center computer 1 and interface (I / F) 23, communication line, interface (I / F)
The floor control system 3 on the manufacturing factory side is connected online via 38. The floor control system 3 also has the same CP as the center computer 1.
A U37, a memory 39, a terminal device 46, a printer 47, and a CAD parts arrangement information file 40 (18) which is an information file having the same contents as the center computer 1.
, CAD version management information file 41 (corresponding to 19), design change notification information file 42 (corresponding to 24),
The device mounting information file for each customer 43 (corresponding to 25) and the shipping history information file for each customer 45 (corresponding to 26) are provided.

Further, the manufacturing history information file 44 stores information on each manufactured device / unit or rack device, and the PWCB inventory information file 48 stores in a PWCB finished product automatic warehouse 50 (described later) of electronic circuit printed boards. Inventory information of PWCB is stored. Further, the shelf manufacturing information file 49 stores shelf manufacturing information. PWC installed at the product assembly site of the factory
The B finished product automatic warehouse 50, the product warehouse 51 of the product, and the testing machine 52 are respectively CPU 37 through the interface 53.
Data is transmitted / received to / from the control units and CPUs of the respective devices 50 to 52, and the contents of related files are referred to and updated.

FIG. 3 shows an operation flow of the entire management system according to the present invention. First, when the customer request A is received, the device estimate / device calculation 1 is performed in the system design B, the customer request request specification change 3 is created, and the device calculation 2 such as the number of devices required by the device estimate is performed. Be seen. Based on the equipment quotation, order issuance is performed by order issuance C, then manufacturing arrangement 1 is issued for manufacturing / inspection D in the factory, parts arrangement 2 and inspection 3 when parts are received.
After that, the shelf manufacturing 4 and the electronic circuit unit manufacturing 7 are started. In the case of the shelf, after the frame assembly 5, the electronic circuit unit (completed the unit test 8) is taken out from the automatic warehouse 9, mounted on the shelf 6 and stored in the product warehouse 13 after completion of the comprehensive test 12. . When the electronic circuit unit is mounted on the shelf, the electronic circuit unit manufacturing history collection 10 is executed, and when the device including the shelf is shipped, the information file is used to determine whether the version number of the mounted electronic circuit unit is appropriate. To determine whether the product can be shipped.

On the other hand, in the system design B, according to the device calculation and the customer device layout condition 2, in the customer-specific design E, the layout design 1, the rack layout 2, the shelf layout 3, and the electronic circuit unit mounting design information (file in FIG. 2). 25) is created and sent to the factory side as a device mounting information file (file 43 in FIG. 2). Similarly, in the system design B, when the customer requirement specification change 3 is obtained, in the design change notification F, the change occurs due to the design change occurrence 1 and the corresponding circuit change design 2 is performed, and then the mounting design 3 and A design change request / version number information 4 (file 24 in FIG. 2) is generated. This information is sent to the factory side by design version information 2 (Fig. 2
41) and design change notification information 3 (file 42 in FIG. 2).

On the control side G (floor control system 1) of the factory, the device mounting information (file 43 in FIG. 2) and the electronic circuit shipment determination result 11 from the manufacturing / inspection D
Information and manufacturing and shipping history information 4 (file 4 in FIG. 2
5) is created. Further, the design change notification information 3 is received, a file (file 42 in FIG. 2) is formed, and the manufacturing and shipping history information 4 and the on-site modification material 5 are supplied to the field support H that supports the shipping destination device, respectively.
Each file of failure information 2 and modification information 3 is created. The failure information 2 is collected in the FIT (failure rate) number grasping section 1 together with the failure information declared by the customer after the equipment is installed, and is notified from this to the maintenance parts management 14 of the manufacturing / inspection D. The customer informs the fault information that has occurred in the operation of the shipped product.

The configuration of the individual system included in the operation flow of the entire management system shown in FIG. 3 will be described below. [Explanation of Example of Device Mounting Design] First, the configuration of an example of the device mounting design for each customer shown in FIG. 4 will be described. This configuration corresponds to the device packaging design unit 10 in FIG. Reference numeral 60 in FIG. 4 constitutes a device mounting design system, and a design know-how file 6
1, a computer 62, and a data file 63. The design know-how file 61 is a design know-how file consisting of logical allocation conditions, equipment mounting conditions, and layout conditions. These are databases of knowledge of conventional manual design methods and are used for PWCB (printed board) by CAD, mounting design, structural design, and the like.

The computer (consisting of a memory including a CPU and a program) 62 is provided with a customer-specific device mounting design program and a delivered device information management program. The data file 63 includes the method mounting file obtained as a result of the design, and the manufacturing mounting file 25 (the customer-specific device mounting information file 25 in FIG. 2) created from the method mounting file.
2) and a delivered device information file 26 (corresponding to the customer-specific shipping history information file 26 in FIG. 2).

As the design data (CAD) file 65, a data file for each CAD having the same parts table, mounting drawing, and structure as the conventional CAD is used.
PWCB-equipped devices (exchanges, etc.) that support (see Fig. 2)
Is implemented in a conversational manner between the computer 62 and the terminal device 27 (see FIG. 2). At this time, the device / PWCB basic information file 21 (see FIG. 2) is used.

5 and 6 are examples of customer-specific order information (file 22 in FIGS. 2 and 4). Is set as customer data such as order number, destination, installation location,
Product name as ordering device data (frame, unit, PWCB
Etc.), specifications, quantity, etc., and the device configuration is judged from the information of the specifications. Also, as shown in FIG. And FIG. 6 shows C
5 is an example of input data of AD information, which is shown in FIG. Is a device
It is an example of the PWCB basic design information stored in the PWCB basic information file 21, in which numerical values such as the structure, mounting width, power consumption, and heat generation coefficient are stored for each PWCB. Further, FIG. 6 shows shelf information / fixed and designated (option) mounted PWCB data. In this case, for each shelf in which the PWCB is mounted, the product name, specification, mounting width, and mounting of the PWCB to be mounted in each slot position. The classification (fixed / designated) etc. are stored.

Further, FIG. 7 shows a design know-how file (see FIG. 4).
The example of the data of the file 61) of FIG. A. of FIG. Is
This is an example of floor layout information, and an arrangement example as shown in the example of the drawings is stored for a plurality of patterns P1, P2, ... Corresponding to a layout design condition for a rack arrangement condition (standardized arrangement pattern). B. of FIG. Is a designated PWCB mounting standard pattern in the shelf, and various patterns for arranging which PWCB in the shelf and at which position are prepared, and a pattern suitable for the condition can be selected from among them. In addition, C.I. Is an example of a standard pattern for mounting shelves on a rack, and shows patterns P1, P2, ... Of combinations of devices mounted on shelves (6 stages of 0 to 5).

[Explanation of an Example of Device Mounting Design] FIG. 8 is a processing flow of the device mounting design, which is executed interactively by the terminal device 27 of FIGS. 2 and 4 by the device mounting design program for each customer of FIG. To be done. In FIG. 8, when the corresponding customer order designated installation condition is input (an example in FIG. 5 is shown) and the rack layout condition is instructed, the layout design condition of the design know-how (an example in A. in FIG. 7) is used. Select the rack layout number and shelf mounting conditions, and confirm the rack layout (1 to 4 in FIG. 8). Next, a rack is extracted from the customer-specific order information and displayed on the rack layout, and the rack layout number is input from the rack (5).

The rack layout layout number displayed in response to this is confirmed (step 6), and if it is inappropriate, another rack layout number is selected. When it is confirmed that the shelf information is appropriate, the shelf of the order information is extracted and displayed, and the standard pattern for mounting the shelf on the rack is output from the design know-how. On the other hand, the shelf rack mounting pattern is selected and input (Same as 7). After this, it is judged whether or not the mounting pattern of the shelf is confirmed (Same as 8), and if confirmed, the figure number (FIG No.) is given (Same as 9) and the number of PWCBs mounted is confirmed. (Ibid. 10).

After the confirmation, the standard pattern information for mounting PWCB on the shelf of the design know-how is input, and an instruction to mount the option PWCB is given for each figure number (see 1 above).
1). Next, it is checked whether the number of mounted devices matches the order (at 12). When the collation is obtained, the device mounting diagram data is output (at 13) and the data is transferred to the factory (at 14). In the floor control system 1 on the factory side, the information is stored as device mounting diagram information for each customer / order (15). As a result, the PWCB is mounted and at the same time, the manufacturing history information is collected.

FIG. 9 shows an example of the device mounting design information (file 25 in FIGS. 2 and 4) created in this way. 9A. Is P corresponding to customer delivery order information
Example of equipment mounting diagram (PWCB product name, specifications, mounting position) information of WCB mounting shelf, B. Shows an example of shelf mount information (frame name, specifications, rack layout number, etc.).

[Description of Example of Design Change] FIG. 10 is a processing flow of design change information, FIG. 11 is an example of version management information, FIG. 12 is an example of design change information, and FIG. 13 is an output by design change. It is an example of data. In FIG. 10, when a problem occurs in the device (printed board or the like), it is determined whether or not the hardware should be changed (1 in FIG. 10). If not, the software is changed to deal with it. It is judged whether the circuit is to be designed (2), and when the circuit is designed, the circuit is changed (3). If the circuit is not designed or the circuit is changed, the mounting design is changed (4). At this time, the parts arrangement list of the CAD information is revised, and the version number management list is further revised (the same as 5), and the CAD information is updated (a and b in FIG. 10). An example of this version number management information is shown in FIG. In this example, a version number management list before revision and a version number management list after revision (including additional data) are shown.

In steps 6 to 8 of FIG. 10, design change information c such as numbering of design change management number, representative model, device drawing number and old / new total version number input, in-house manufacturing process status investigation / application instruction, etc. Is input and the change request information is input (same as in 9), it is automatically imported from the version number list / parts arrangement list information d of the CAD information file and is stored in the design change information file 10 (corresponding to 24 in FIG. 2). Is stored. An example of the design change information is shown in FIG. This includes the design change management number (EC No. 201625) that is automatically generated and managed by the system.
And the representative model to be changed, product name of the target model, drawing number,
The operation start date, version number, change summary, etc. are entered in detail. The design change information file 10 and the CAD information d (version number management list revision, parts arrangement list revision) are transferred to the factory (at 11).

In the step 8, if there is an instruction to revise the manufacturing process, it is judged whether or not there is a modification to the already shipped product (at 12), and if there is not, the process is terminated. (Same as 13), survey the delivered amount (Same as 14), and create a modification instruction sheet for shipped products (Same as 1).
5). Next, the field product (the product delivered to the shipping destination) is remodeled (16) and the shipping history information data (45 in FIG. 2) is updated (17). A. of FIG. Is design change (EC)
3 is an example of revision of the drawing version number management list (corresponding to the file 19 in FIG. 2) stored in the CAD total version number data due to occurrence of the error. It is shown that the drawing version numbers / PT (printed) boards corresponding to the total version numbers "03C" and "04C" are revised from a specific date or new manufacturing. B. of FIG. Is an example of the output data of the design change notice, and the above A. It is created corresponding to the revision of the drawing version number management list, and is stored in the design change information database (corresponding to the file 24 in FIG. 2). This content is also sent to the floor control system 3 and stored in the file 42.

System Configuration for Collecting Manufacturing History Information and Confirming Change of Design Change FIG. 14 is a system configuration for realizing collection of manufacturing history information and confirmation of change of design change, which is mainly executed in the floor control system 3 on the factory side. And the outline of operation is shown. On the side of the center computer, based on the customer order (22 in FIG. 2), the device mounting diagram (FIG.
The device mounting drawing file 14a) is created and stored in the device mounting information (device mounting drawing) file 43 of the floor control system 3 on the factory side. The management device a of the automated warehouse (corresponding to 50 in FIG. 2) of the floor control system 3 controls the loading / unloading operation of the electronic circuit printed board (PWCB). When the PWCB loading and unloading is executed, the loading / unloading information is supplied to the PWCB inventory information file 48 of the floor control system 3 and the contents are updated.

When it is detected by the PWCB inventory information file 48 that the PWCBs for assembling the device are prepared, the automatic warehouse is instructed to issue the PWCBs, and the PWCBs that have been issued are sent to the mounting work place. . Here, the information indicating the contents of the printed board (attached with a bar coded label) is read by the bar code reader and sent to the floor control system 3. Floor control system 3 is a device mounting diagram (information) file 4
3 indicates to the terminal device b (or the automatic mounting device) of the mounting work the mounting position (in the shelf) of the PWCB, and when the mounting is performed, the mounting result (the mounting position of the PWCB, etc.) is input by the magnetic card or the like. To do.

In response to this, the floor control system 3 transfers the mounting result to the mounting result (manufacturing history information) file 4
Store in 4. Next, the mounted device is sent to the test process and tested, and if a defective PWCB is found here, it is replaced, and the replacement result (old and new PWCBs) is obtained at each terminal device c in this test process. The PWCB is sent to the floor control system 3 by reading it with a bar code reader, and the file 44 is updated with its contents.

When the test is completed, the process of shipping determination is started. Here, the design change information (corresponding to the file 24 in FIG. 2) sent from the center computer is stored in the design change (EC) / version number information files 42, 43 (see FIG. 2) of the floor control system 3. And the information (file 44) of the mounting result of the device is the files 42, 4
The PWCB installed in the device is collated with each piece of information No. 3 to determine whether the PWCB is compatible with the subsequent revision or design change or is not compatible with the PWCB to determine whether the product can be shipped. When shipping is possible, the shipping list is printed before shipping. Unsupported items will be replaced.

The mounting result file 44 stores information on the mounting state input according to the manufacturing line and the final mounting result according to the replacement result, etc. When the device is shipped, the mounting contents at that time are shipping history information. It is saved as a file (45 in FIG. 2). The shipping history information file is used as field information such as function addition by customer request.

[Configuration of Manufacturing History Information Collection] FIG. 15 to FIG. 18 show the configuration of the embodiment for collecting the manufacturing history (mounting result) information and confirming the folding of the design change, which is roughly described in FIG.
Will be explained. FIG. 15 and FIG. 16 are processing flows of PWCB, shelf output, history information collection, and design change insertion confirmation, which are executed in the floor control system 3. FIG. 17 shows an example of input data used, FIG.
8 is an example of output data of the processing result.

In FIG. 15, when a manufacturing plan is performed and a dispatch plan / order instruction is generated (1, 2 in FIG. 15),
Completion of the material to be released and confirmation of the total version number based on the device mounting data (3). For this confirmation, the total version number data (see A in FIG. 13) and the device mounting diagram data (see FIG. 9) are input as the CAD information a, and the PWCB finished product is produced as the production information b from the manufacturing (factory) side. Warehouse status and shelf assembly completion status are entered. This PWCB finished product warehouse status and shelf assembly completion status data are shown in FIG. And B. An example of each data is shown in, and it is composed of each information such as product name, drawing number, total version number, manufacturing date, manufacturing date and month machine.

Items required to complete the equipment (PWC
Judge whether or not (B and shelves) are complete (4),
If there is no article (not available), check the manufacturing progress status, adjust the dispatch schedule and wait (Sections 5 and 6). If there is an item, the version number is confirmed (7), and if it does not match, a modification instruction is issued and a modification inspection is performed (8, 9). If the version numbers match, a shelf / PWCB issue instruction is issued (10).

In response to this, when the PWCB finished product warehouse c and the completed shelf d at the shelf assembly position are delivered, the PWC is completed.
B mounting is executed, history information (mounting result) is read (Same as 11), and device test is performed (Same as 12). The read history information is stored in the manufacturing history information e (file 44 in FIG. 2, data example is shown in FIG. 18).

Moving on to FIG. 16 through the next of device testing,
The test is judged (13 in FIG. 16), and if good, it is shipped or stored in the product warehouse (14). When a defect is detected by the test, it is judged whether it is a manufacturing problem (see 1
5) If it is not a manufacturing problem, the design will be reviewed and remodeled (16, 17). In case of manufacturing problems, request modification and exchange for modified product (18). Step 17, 1
After 8, the manufacturing history information e is corrected (the updated PWCB is reloaded) and updated to the new manufacturing history information f (see 1
After the device test (12) is performed via 9), if it is good, it is shipped or stored in the product warehouse.

For products in the product warehouse, the order / version number and manufacturing history are inquired (step 20). At this time, the latest version number information g (see A in FIG. 13) and the final order information h of the customer
(Similar to FIG. 5) and the latest manufacturing history information f are input and collation is performed. As a result, when it is found that the product corresponds to the order and the version number is changed, the product is shipped, and at the same time, each information is stored and stored as customer-specific shipping history information i (file 45 in FIG. 2). If they do not match, the process returns to the manufacturing history correction process (19 in FIG. 16). FIG. 18 shows an example of data obtained by collecting manufacturing history / shipping history information. That is, customer delivery destination / order information, manufacturing shelf / installed PWCB, and manufacturing / history information of individual shipment are mounted on each shelf mounting PWCB, manufacturing / shipping history information (total version number, manufacturing date, manufacturing date, and manufacturing date). Unit No.) and.

[Field Information Management] The field information management manages information generated by remodeling or changing the device shipped and delivered to the customer. FIG. 19
6 is a block diagram of field information management, in which the center computer 1 uses the PWCB basic information file 21 and the customer-specific shipping history information file 26 to perform processing by a program in the processing device (CPU 16, memory 17). Equipment delivered to field 4 as shown in Fig. 19 (exchanges delivered to each station in each country)
The contents installed in the are stored in the shipping history information file 26, and this file is used as field information for adding a function by a customer request.

FIG. 20 shows a processing flow of field information. Is the processing flow for totaling the number of modified jumper wires for each customer order, B. Is a process flow of change folding management for shipped products, and these processes are executed in the center computer 1. 21 is an example of PWCB device basic information used for the processing of FIG. 20, and FIG.
3 is an example of output data by the processing of FIG. Is an example of output data of totals corresponding to customer orders, B. Is an example of output data of a change folding request for a field-shipped product. A. When the order number designated by the customer is designated (1 in FIG. 20), the customer shipping history information a (see FIG. 18) for the customer is input to extract the corresponding physical quantity and total edition number (2). . Extracted physical quantity / total version number and PWCB device basic information b (file 21 in FIG. 2, example is shown in FIG. 21)
Is input, and the jumper / pattern wiring of each PWCB or device and the number of pattern cuts are totaled (the same as 3).

FIG. 21 shows an example of PWCB device basic information. This information is output data such as design changes for each PWCB,
This information is collected for each device, and in this example, the product name, the total version number corresponding to the drawing number, the change history information, the modification amount (the number of modified jumper wires, the number of pattern cuts), and the like are included.
The total number of jumper wirings and pattern cuts for each customer / order correspondence is totaled based on the totalized result of each PWCB that is totaled with reference to this information (4 in FIG. 20). 22A. Is an output example of jumper wiring for customer orders and total amount of pattern cuts. In this case, the order number,
For the order information such as the destination, the quantity of the corresponding device, the quantity of each PWCB mounted on the equipment, and the total are included.

FIG. 20B. In the process flow of the change folding management, when there is an instruction of the change device drawing number first (same as 5), the customer name and the total version number are input by inputting the device and the total version number of the customer shipping history information a (see FIG. 18). And the quantity (6), and indicate the total version number before and after modification (7). Then PW
By using the CB device basic information b, the modification man-hours and costs for each customer are totaled (8), a local modification request is created, and the result of the local modification insertion is input to manage the change modification information for the local station (9). ~ 11). As a result, the device and total version number of the customer shipping history information a are updated. FIG. 22 shows an output example of the change insertion request (step 9 above) for this field-shipped product.
B. Shown in. That is, the PWCB of the design change, the change material number, the total version number, the contents of the function addition, and the like, as well as the installation location of the PWCB to be changed, the order number, and the like are included.

As field information management, in addition to the above,
Based on the analysis result of the failure information generated by the operation of the delivery destination, it has a totaling function by grasping the number of FITs (failure occurrence rate) such as PWCB, and can be used for feedback to parts selection and inspection.

[0048]

According to the present invention, the know-how of the equipment mounting design for each customer, which has been conventionally created manually, is made into a library, and the customer order file and the design data file (C
By utilizing AD) and systematizing, it is possible to realize the efficiency and quality improvement of the device mounting design work for each customer and for each order. In response to design changes and version number changes, related data files can be updated and reflected in the manufacturing stage, shipping stage, etc. Further, by providing the manufacturing mounting information file to the factory, it is possible to rationalize the work in the manufacturing stage, and it is possible to automate the determination of the shipment possibility by collecting the shipping history information and checking the version number at the time of shipping. This makes it possible to centrally manage from the device mounting design for each customer and order to the collection of shipping history information, which improves the efficiency of design work, labor saving of manufacturing, and the efficiency and quality of information management of shipping (delivery) devices. Improvement can be achieved.

[Brief description of drawings]

FIG. 1 is an overall principle configuration diagram of the present invention.

FIG. 2 is a system configuration diagram of an embodiment of the present invention.

FIG. 3 is an operation flow of the entire management system according to the present invention.

FIG. 4 is an example configuration of a device mounting design for each customer.

FIG. 5 is an example of customer-specific order information.

FIG. 6 is an example of customer-specific order information.

FIG. 7 is an example of data of a design know-how file.

FIG. 8 is a processing flow of device mounting design.

FIG. 9 is an example of device mounting design information.

FIG. 10 is a processing flow of design change information.

FIG. 11 is an example of version number management information.

FIG. 12 is an example of design change information.

FIG. 13 is an example of output data due to a design change.

FIG. 14 is an outline of a system configuration and operation for realizing the collection of manufacturing history information and the confirmation of design change insertion.

FIG. 15 is a processing flow (1) of warehousing of PWCB, shelf, collection of history information, and confirmation of folding of design change.

FIG. 16 is a process flow (2) of PWCB, shelf delivery, history information collection, and design change insertion confirmation.

FIG. 17 is an example of data of a PWCB finished product warehouse status and a shelf assembly completion status.

FIG. 18 is an example of data obtained by collecting manufacturing history / shipping history information.

FIG. 19 is a configuration diagram of field information management.

FIG. 20 is a processing flow of field information. Is the processing flow for totaling the number of modified jumper wires for each customer order, B. Is a process flow of change insert management for shipped products.

FIG. 21 is an example of PWCB device basic information.

22 is an example of output data by the processing of FIG. 20,
A. Is an example of output data of totals corresponding to customer orders, B. Is an example of output data of a change folding request for a field-shipped product.

FIG. 23 is an explanatory diagram of a conventional customer-specific device packaging design method.

FIG. 24 is an explanatory diagram of a conventional method of collecting manufacturing, inspection, and manufacturing history information.

FIG. 25 is an explanatory diagram of a conventional delivery device information management method.

[Explanation of symbols]

1 Center device 2 Terminal device 3 Floor control system installed on the factory side 10 Equipment implementation design department 11 Design change management department 11a Design change information management department 11b Design version information management department 12 Delivered device information management department 13 Design data file 14 Manufacturing data file 15 Interface unit side of center device 30 Interface unit 31 Processing device 32 Product information management unit 33 Electronic circuit printed board unit assembly unit 34 Shelf assembly unit 35 Device / unit unit 36 Device rack mounting unit

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Masao Sudani 1015 Kamiodanaka, Nakahara-ku, Kawasaki City, Kanagawa Prefecture, Fujitsu Limited (72) Inventor, Katsuo Okuyama 1015, Kamedotachu, Nakahara-ku, Kawasaki, Kanagawa Prefecture, Fujitsu Limited ( 72) Inventor Masao Ishiwata 1015 Kamiodanaka, Nakahara-ku, Kawasaki City, Kanagawa Prefecture, Fujitsu Limited (72) Inventor, Hidetoshi Uchibori, 3-9-18 Shin-Yokohama, Kohoku Ward, Yokohama City, Kanagawa Prefecture Fujitsu Communication Systems Limited ( 72) Inventor Tori Matsui, 1015 Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa, Fujitsu Limited (72) Inventor Shigeru Kubo 1015, Kamikodanaka, Nakahara-ku, Kawasaki, Kanagawa Prefecture, Fujitsu Limited (72) Inventor, Kinen Matsubayashi, Kanagawa 1015 Kamiodanaka, Nakahara-ku, Kawasaki-shi, Japan Within Fujitsu Limited (72) Inventor Kazuhide Tada 3-9-18 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa Within Fujitsu Communication Systems Ltd. (72) Inventor, Yuko Takei 3--9-18 Shin-Yokohama, Kohoku-ku, Yokohama, Kanagawa Prefecture Fujitsu Communication Systems Inc. In the company

Claims (5)

[Claims] 1. In a product information management system of an electronic device on which an electronic circuit printed circuit board unit is mounted, the center device stores a customer-specific order data file storing customer-specific order information, and various electronic circuit printed circuit board units.
An apparatus design data file, a design know-how data file of equipment arrangement, line length, etc., a processor including a memory, and a terminal device with a display are provided, and the equipment mounting design section is provided in the processing apparatus, and the equipment mounting design section. Is a product information management system characterized by creating a device mounting file of a device including an electronic circuit printed circuit board unit corresponding to an order by using a design data file and a design know-how data file for each customer-specific order. 2. The design change information management unit and the design version number information management unit according to claim 1, wherein the design change information management unit creates a design change data file when a change occurs in the design data file. In addition to storing, a basic information file for electronic circuit printed circuit board unit that corresponds to the change is created, and the design version number management unit stores it in the version number information file when the design version number is changed. A product information management system characterized by checking design contents with files and version number information files. 3. The delivery (shipment) device information management unit according to claim 1, wherein the delivery (shipment) device information management unit is provided, and the delivery (shipment) device management unit creates a device equipped with an electronic circuit printed board unit at the time of delivery to a customer. A product information management system characterized by calculating data on the equipment at the destination of shipping and failure rate data using the delivered history information file. 4. The floor control system according to claim 1, wherein a floor control system is provided on a factory side for manufacturing the device, and the floor control system receives the device mounting data created by the center device through a communication line and has the same contents. Holding the mounting data file, outputting an instruction for manufacturing a device equipped with an electronic circuit printed board unit based on the device mounting file, collecting the contents mounted on each manufactured device, and creating a manufacturing history file. A product information management system characterized by transmitting the manufacturing history file to a center device. 5. The floor control system according to claim 2, wherein the factory has a floor control system for receiving the device mounting data created by the center device via a communication line and holding a file having the same content, and further, the design change data file and the design version. When the data of the numerical information file is received and a file having the same content is provided, the contents installed in each device manufactured in the factory are collected to create a manufacturing history file, and when the device is shipped, the contents of the manufacturing history file A product management information system, characterized in that the contents of each data file of the design change and the design version number are collated to check whether the design change or the version number is suitable to judge whether the product can be shipped.