JP3335402B2 - Manufacturing history management system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a manufacturing history management system suitable for use in a vehicle production line or the like.

[0002]

2. Description of the Related Art Factory automation (FA) technology has brought great achievements to the manufacturing industry in improving product quality, reducing manufacturing costs and improving productivity. According to a production system in which this type of FA technology is introduced, all operations related to the manufacture of a product, such as transfer of a workpiece and control of processing, are performed under the control of a computer. That is, under the control of the computer, the workpiece is sequentially conveyed to various processing machines, and each processing machine is provided with control data determined according to product specifications and the like. In this way, the target product is automatically produced without any labor. For processes that require strict control,
For example, the result of the work performed by the processing machine, such as the tightening of bolts, is measured by a sensor or the like, and it is inspected whether or not the measurement result matches a common set value prepared for each product or each part. Then, only the workpiece that has passed the inspection is flowed to the next process. In this way, the work and the monitoring thereof are integrated, and a high quality product is stably produced.

[0003]

By the way, in the above-mentioned production system, since many products usually flow on the production line, a large-capacity memory is required to store all of these data. For example, when the work contents in each process are stored, a method for storing the work contents may be used as it is as a save file, or another method may be used to store the file. However, according to such a method, data is always written from a work terminal provided in each process, and there is a problem that the data input response deteriorates as the amount of data increases. In addition, there is a problem that it takes time to search for input data, and input and search cannot be performed simultaneously. Conventionally,
Since there was no effective means to overcome this problem, no effective system meeting the above significance was realized.

The present invention has been made in view of the above circumstances, and has as its object to provide a manufacturing history management system capable of collecting and managing a history of manufacturing a product.

[0005]

According to a first aspect of the present invention, there is provided a manufacturing history management system for identifying an assembling object flowing through a manufacturing line including a plurality of manufacturing steps. A work control unit (for example, the work terminal WT of the embodiment) including an assembly detection unit (for example, the ETC wrench of the embodiment) that outputs a work result performed on the assembly in the manufacturing process. Inspection confirmation means (e.g., the middle inspection terminal MIT, the complete inspection terminal FIT according to the embodiment) that is provided for each manufacturing process and that confirms and inspects the content of work performed on an assembly in the production line
Etc.) and storage means for giving a work instruction to the work control means for each manufacturing process and for storing data output from the work control means and the inspection confirmation means (for example, the file server FSn (n = 1 to 3)) and management means for controlling data transfer between respective files in the storage means (for example, the management terminal MTn of the embodiment)
(N = 1 to 3)), wherein the storage means comprises:
A transmission / reception file for transmitting / receiving data relating to an assembly to be assembled on the production line from a host computer, and a work data file corresponding to each of the work control means, and having work data corresponding to the assembly;
A checker data file for writing the result of the work based on the work data of the work data file, and a storage file for storing the data of the checker data file after all the processes in the manufacturing line are completed. The management means reads out work data in the inspection device data file based on shipping information transmitted and received by the transmission / reception file, and stores the read out work data in the storage file. Change to and save
And the factory return information is written in the send / receive file.
The storage file based on the factory return information.
Read the stored data related to the assembly from the
Saved data can be written to the inspection unit data file
It is characterized by being changed and written as described above.

[0006]

According to the manufacturing history management system according to the first aspect, the identification of the assembly is performed by the assembly identifying means in each manufacturing process, and the assembly detecting means applies the identification to the assembly in the manufacturing process. The work result is output. Then, the work result is written in the inspection device data file with respect to the management terminal. Then, after completing all the steps in the manufacturing line, the management means changes the data of the inspection device data file into the format of the storage file and stores it. Also send
When the factory return information is written to the received file,
The column indicates the storage data related to the assembly from the storage file.
Data and read the saved data
Was changed so that it could be written to and was saved
Change the data so that it can be modified.

[0007]

An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a manufacturing history management system according to an embodiment of the present invention. This manufacturing management system is a safety device (Supplement
al Restraint System (hereinafter abbreviated as SRS) is applied to an SRS assembly line, and is installed in a factory together with equipment for performing each operation of the line.

First, prior to describing the manufacturing history management system, an SRS assembly line will be described. SRS
Is composed of the following five types of parts. Dash Sensor-R Dash Sensor-L SRS Unit Cable Reel Module Assembly

The SRS assembling line has a plurality of steps for assembling the above-mentioned parts, and in each step, basically one type of operation is performed. Each of the above components is prepared in advance for each process corresponding to each component.

Here, not only vehicles to which the SRS is to be mounted (hereinafter, this type of vehicle is referred to as SRS specification vehicles) but also vehicles that do not need to be mounted are put into the SRS mounting line. Also, there are SRS specification vehicles of various specifications, and the configuration of the SRS to be assembled differs depending on each specification. For example, a vehicle with a certain specification has an SRS that includes all of the above five items.
, And some parts are not required for vehicles of different specifications. In this SRS assembly line, each time a vehicle arrives at each process, the vehicle is identified, and based on the identification result, it is determined whether or not the parts prepared for the process should be assembled to the vehicle. Will be Also,
It also indicates the difference in assembled parts due to the difference in specifications. By such control, only the parts required for each vehicle are assembled. The specific control method will be described later.

Each of the above-mentioned parts is provided with a serial number, a specification and a type of the part, and the like by a bar code. The serial number of each part is collected when the part is assembled into a vehicle. In each step,
When an assembling operation of each component such as a bolt tightening operation and a fitting operation is performed, information indicating a result of the operation such as a tightening torque value and a fitting state is collected. The manufacturing history management system according to the present embodiment collects the serial numbers of the respective components and the work status at the time of assembling them as work data, and manages the collected work data for each vehicle.

At this factory, the first to third lines are installed as the SRS assembly lines described above. Each vehicle manufactured in the factory is put into one of these lines, and the SRS is assembled as necessary.

Next, the configuration of the manufacturing history management system will be described. In FIG. 1, FS1 to FS3 are file servers provided corresponding to the first to third lines, respectively. These file servers FS1 to FS3 hold various files for storing information for controlling the work performed by each line or the work data and the like.

Each of CT1 and CT2 is a communication terminal, and is an ALC (Assembly) that controls the entire automobile production line.
le Line Control; assembly line control) It is connected to the host computer HST via a communication line. When data is transferred from the host computer HST, both of them receive data during normal operation. Also, when it becomes necessary to transmit data from the manufacturing history management system to the host computer HST, both communication terminals try to transmit data, but the terminal that transmitted the data first deletes the transmitted data. Therefore,
One piece of data is usually transmitted by one terminal. However, since it takes a certain period of time for the terminal that has transmitted the data to delete the data, the other terminal rarely transmits the data before the deletion. Thus, two communication terminals CT1 and CT2 are provided for duplexing the communication function. Therefore, hereinafter, these communication terminals CT1 and CT2 are simply referred to as communication terminals CTn. When a vehicle is inserted into the SRS assembly line, AF-ON, which is reception data related to the input vehicle
Data is transmitted from the host computer HST. The communication terminal CTn receives the AF-ON data transmitted in this manner. When the vehicle is line-off from the SRS assembly line, the communication terminal CTn transmits the history information and the AF-OFF data for reporting the shipping determination of the vehicle on the SRS assembly line to the host computer HST.

Each of the work terminals WT, WT,... Is arranged for each process constituting each line. Each of the work terminals WT, WT,... Performs the following functions in the process under their control. Control of the work to be performed in the process under their control. This control includes identification of an incoming vehicle, determination of workability,
The control includes a control of an ETC (electric torque control) wrench or a constant torque wrench for performing the work content determination, the assemblable parts determination and the tightening work. Confirmation of the content of work actually performed in the process each has jurisdiction over, specifically, the value of torque in tightening work,
Collect the status of the fitting part after fitting work, serial number of assembled parts, etc. Forming work data based on the collected results. Determination of whether or not the work has been performed in a manner that satisfies a predetermined standard, and display of the determination result. Here, the predetermined criterion is set based on a work table described later each time the work terminal is used. This operation will be described later.

One management terminal MTn (n = 1 to 3) is provided for each line n, and manages various files corresponding to each line. The specific management contents will be described together with the contents of each file.
In addition, as terminals installed for each line n, there are a middle inspection terminal MIT, a complete inspection terminal FIT, a monitoring terminal OVT, a maintenance terminal MET, a form terminal BT, an adjustment terminal ADT, a reexamination terminal RT, and the like. The roles of these terminals will also be described as needed when describing the contents of each file. N1 and N2 are token ring networks, respectively, which are used as data transmission paths between terminal devices in the manufacturing history management system.

Next, various files used in the manufacturing history management system will be described. Each file server FSn (n = 1 to 3) manages an ALC reception file F shown in FIG.
1, ALC transmission file F2, trigger file F3, S
It has an RS work table F4, a terminal operation confirmation file F5, an inspection unit data file F6, and a storage data file F7. Hereinafter, the specific contents of each of these files will be described, and the role of each of the above-mentioned terminals that handles them will be described.

(1) SRS work table F4 The SRS work table F4 defines work contents when assembling SRS parts to a vehicle in this SRS assembling line. As shown in FIG.
It consists of S symbol content, part table data, fastening table data, and fitting table data. Of these data, the SRS symbol and the SRS symbol content are
This is information describing the SRS attached in the S assembly line.

The parts table data contains S for each SRS symbol.
It is data that defines the components of the RS, and up to N1 items can be defined. If the number of components in the SRS is less than N1, only the component data corresponding to the components is written in the component table data field, and the remaining fields in the component table data field have no meaning as component data. Data (eg space)
Is written. Each part table data contains the name of the part or the content of the work performed on the part (tightening / fitting)
For the operator, a symbol for designating an assemblable part determined in advance for each SRS symbol, a number of a step for performing the work, and a search key. The search key is data written for associating the component data with the tightening data or the fitting data corresponding to the component data.

The tightening table data is data defining a tightening operation required when assembling the SRS parts, and a maximum of N2 pieces can be defined. Each tightening table data is defined for each SRS symbol, and includes information for specifying a tightening location or the content of a tightening operation, a symbol indicating a tightening torque range, a number of a process for performing the operation, and a search key. Become. Here, the search key is defined in the tightening table data for associating the component data with the work data (in this case, the tightening data) when the component data and the work data (in this case, the tightening data) are obtained with the tightening operation of the parts. . That is, in the fastening table data, if the search key of the component data relating to a certain component A is a and the component is to be attached by fastening, the component A
Are written as those corresponding to the tightening data whose search key is a in the tightening table data. When a plurality of tightening operations are performed on the same part, a plurality of tightening data having the same search key as the search key of the part data of the part is defined.

The fitting table data is stored in the SRS
This is data defining a fitting operation required when assembling parts, and up to N3 pieces can be defined. Each fitting data is defined for each SRS symbol, and includes information for specifying a fitting position or the content of a fitting operation, a symbol, a step number for performing the relevant operation, and a search key. The search key in the fitting table data also associates with the component data, like the search key in the fastening data. As for the tightening table data and the fitting table data described above, only necessary ones are written in the fields of each table data as in the case of the component table data.

Each work terminal WT searches for part data, tightening data and fitting data in the work table F4 using the process number of the process under its control as a key, and fetches the corresponding data. Of these, the tightening data and the fitting data are used for controlling the tightening work and the fitting work in the jurisdiction process in each work terminal WT that has taken in the data. In addition, each work terminal WT includes component data,
When taking in the tightening data and the fitting data, the work table F4 stores the area in which they are described. The contents stored in these areas are stored in the work terminal WT.
Is referred to when forming work data described later. Further, the work table F4 is also referred to when the management terminal MTn creates storage data relating to the entering vehicle.

(2) ALC reception file F1 The AF-ON data received by the communication terminal CTn is sequentially written in the ALC reception file F1. These AF-ON data include each information shown in FIG. Of these pieces of information, the header part is data for communication control, and includes a destination of the AF-ON data (in this case, an SRS assembly line) and a transmission source (in this case, an ALC host computer). The identification code is A
This is information indicating whether the vehicle corresponding to the F-ON data is newly inserted into the SRS assembly line or is returned after returning to the factory. The handling of the vehicle by the SRS assembly line (new assembly / adjustment, etc.) is determined by the identification code. Following the identification code, there is a line number of a line into which the vehicle is to be inserted, and further information on the vehicle such as a lot number and a frame number. AF-
The ON data includes AF-ON serial number, transmission serial number, AF-O
Information related to the birth of the AF-ON data, such as N years / month / day / hour / minute / second, is included. In addition, AF-OFF, repair-in, repair-out, AF-OFF cancellation, factory return,
Information such as AF-ON cancellation, factory return cancellation, and pass is received from the host computer HST and written into the ALC reception file.

(3) Inspection Unit Data File F6 This inspection unit data file F6 stores work data corresponding to each vehicle to be put into the SRS assembly line. Each time new AF-ON data is written in the ALC reception file F1, these operation data are stored in the management terminal M.
Created by Tn. FIG. 5 shows the format of the work data. The work data is AF-ON as shown in FIG.
Contains the content of the data. The work data includes N1 parts data, N2 tightening data, and N3 fitting data as items not included in the AF-ON data. These items are reserved for recording the results of work performed on the vehicle, and are blank without any content when created by the management terminal MTn. In these blanks, work results (part numbers, fastening data, fitting data) collected by the work terminal WT when the vehicle corresponding to the work data passes through each process are sequentially written. Further, the work data includes items corresponding to various inspection processes and adjustment processes, such as middle inspection determination date, ..., complete inspection determination date, ..., adjustment determination date, .... For each of these items, data collected in each step when the vehicle passes through the corresponding step is written. Also,
In the work data, data indicating which terminal (adjustment terminal, work terminal, etc.) the work result was written is also written.

(4) ALC transmission file F2 The ALC transmission file F2 stores AF-OFF data shown in FIG. The AF-OFF data is created by the management terminal MTn for each vehicle that has completed the work on the SRS assembly line. ALC transmission file F
The AF-OFF data created in the communication terminal CTn
To the host computer HST. A
Among the items included in the F-OFF data, the search key (line number, series number, frame number), N1 part data, N2 fastening data, and N3 fitting data are the AF data of the vehicle. -Created based on the contents of ON data. However, unlike the AF-ON data,
Each of the component data, the fastening data, and the fitting data has a key. The host computer HST that has received the AF-OFF data associates each data based on these keys. Further, the AF-OFF data has an item of shipping determination. This item is completed terminal FIT, adjustment terminal AD
T, the maintenance terminal MET, and the retest terminal RT.

(5) Trigger File F3 In this trigger file F3, a frame number of a vehicle that is permitted to create and transmit AFF-OFF data is written (see FIG. 7). The writing of the frame number is performed by the middle test terminal MIT, the adjustment terminal ADT, the complete test terminal FIT or the maintenance terminal MET, and the retest terminal RT. The management terminal MTn creates the above-described AFF-OFF data with reference to the inspection device data file corresponding to the trigger data.

(6) Save Data File F7 The save data file F7 stores the save data shown in FIG. This storage data is for the purpose of storing, as a record, the manufacturing history of each vehicle that has completed work on the SRS assembly line, and is created by the management terminal MTn. As shown in FIG. 8, the stored data has substantially the same contents as the work data. However, unlike the case of the work data, the component data, the fastening data, and the fitting data in the saved data each have a key. By using these keys, it is possible to easily grasp the relationship between the used parts of the shipped vehicle and the work performed on each part. This stored data is also used when the vehicle is returned to the factory due to a defect found during transportation.

That is, in such a case, the returned vehicle is put into a repairing process, in which the bar code of the vehicle is read, and the data of the vehicle in the storage file is transferred to the work file, where the data is stored. Then, the defect of the vehicle is corrected and the correction data is written into the work file, and then the shipment is determined. The vehicle is shipped and the stored data is created again.

(7) Terminal operation confirmation file F5 This file is provided to grasp the operation status of each terminal in this system. Each terminal writes the current time to the terminal operation status confirmation file F5 periodically (for example, every five minutes). These times written in the terminal operation confirmation file F5 are read by the monitoring terminal OVT. The monitoring terminal OVT displays that the terminal is operating when these times are normal. On the other hand, when the monitoring terminal OVT compares these times with the time of the monitoring terminal, if there is a difference of not less than a certain time, the monitoring terminal OVT displays that the terminal is stopped.

The operation of the manufacturing history management system will be described below. §1. System Initialization When the power supply of each terminal in the SRS assembly line is turned on and initialized, the manufacturing history management system becomes operable. Here, when an operation for initialization is performed on the work terminal WT, the work terminal WT
Work table F via the file server FSn
4 is accessed, and the data corresponding to the process to which the work terminal WT belongs out of the component data, the tightening data, or the fitting data in the table is read. Thereafter, the work terminal WT in each process controls the tightening work or the fitting work in the process according to the read tightening data or fitting data. When reading data from the work table, the work terminal WT stores the order of each data in component data, fastening data, or fitting data. Thereafter, the work terminal W
When the serial number of the part, the measurement result of the tightening torque, or the fitting state is collected by T, the writing position of the collected result on the work data is determined according to the order stored at the time of reading. . That is, when the work terminal WT in a certain process reads the third component data in the work table F4, the work terminal WT thereafter incorporates the serial number collected from the component into the work data as the third component data. The same applies to the fastening data and the fitting data.

§2. AF-ON data reception When a vehicle is inserted into the SRS assembly line, AF-ON data relating to the vehicle is transmitted from the host computer HST to the communication terminal CTn. When receiving the AF-ON data, the communication terminal CTn reads the line number in the data and sends the AF-ON to the file server corresponding to the line number among the file servers FSn (n = 1 to 3).
Send data. As a result, the received AF-ON data is written to the ALC reception file F1 held by the file server.

§3. Creation of Work Data On the other hand, the management terminal MTn constantly repeatedly determines whether or not there is new data in the ALC reception file F1.
Then, when finding new AF-ON data, the management terminal MTn creates work data (FIG. 5) combining the contents of the AF-ON data and the contents of the work table in the inspection device data file F6. I do.

§4. Issuance of manufacturing history management table After transmitting AF-ON data to the manufacturing history management system, the host computer HST issues a manufacturing history management table for vehicles to be put into the SRS assembly line.
The manufacturing history management table is printed with a bar code representing a frame number and a model series code of the vehicle to be put into the SRS assembly line. This barcode is also printed on the assembly specification. The manufacturing history management table issued by the host computer HST is input to the corresponding vehicle.

§5. Processing in each work process Then, the vehicle is transported by a conveyor and sequentially sent to each process in the SRS assembly line. In each process, the process described below is performed each time a vehicle arrives. First, when the vehicle arrives in front of the work terminal WT, the barcode of the assembly specification is scanned by the barcode reader, and the frame number and model sequence code represented by the barcode are read. However, if the assembly specification is broken, the bar code in the manufacturing history management table in the vehicle is read. The frame number and model code read in this way are displayed on the display screen of the work terminal. Next, the work terminal WT searches for work data in the inspection device data file F6 using the line number, the frame number read by the barcode reader, and the model sequence code as keys. Next, based on the search result, the work table data corresponding to the SRS symbol of the work data is read out, and it is determined whether or not parts constituting the SRS should be assembled to the vehicle.

Here, in any of the following cases a to d, it is determined that the SRS component should not be assembled in the process. a. When the arriving vehicle is not an SRS target vehicle b. When the arriving vehicle is an SRS target vehicle but there is no work to be performed on the vehicle in the process c. When the bar code in the manufacturing history management table of the arriving vehicle is not correctly read d. Appropriate AF-ON data is stored in the host computer HS
When not supplied from T In these cases, which of the above cases corresponds is displayed as an abnormal message on the screen of the work terminal. When the frame number or the model sequence code is not correctly read and an abnormal message is displayed, the operator can read the barcode again. If the re-execution is not performed, the vehicle is sent to the next process without performing any work in the process. Then, the work terminal WT waits until the barcode of the new vehicle is read.

On the other hand, if the arriving vehicle is an SRS-specified vehicle and the work is to be performed in the process, the work data corresponding to the line number, the frame number read by the bar code reader, and the model series code are stored. The work data is read out from the inspection device data file F6, and this work data is written to the work data storage area in the memory of the work terminal WT. The contents of the work data are displayed on the screen of the work terminal WT. Then, the work assigned to the process is performed. Hereinafter, the details will be described for each step.

(1) Dash sensor R assembling step and dash sensor L assembling step
The assembling step will be described as an example as follows. a. The bar code such as the serial number of the dash sensor R and the specifications and types of parts are read by a bar code reader. b. Attach the dash sensor R to the vehicle body, insert a bolt into a predetermined location, and tighten the bolt with an ETC (electric torque control) wrench.
To the vehicle body. c. Further tighten and confirm the bolts with a constant torque wrench. The same operation is performed in the assembly process of the dash sensor L.

<Process of Work Terminal Associated with Each Step> The serial number of the dash sensor R is input to the work terminal WT. Further, the tightening torque value by the ETC wrench and the tightening value confirmation result (pass / fail) by the constant torque wrench are measured by the sensors of the respective wrenches, and these measurement results are input to the work terminal WT. Then, it is determined whether or not the measurement result of each torque is within a predetermined allowable range, and the determination result is displayed on the work terminal. Next, the work terminal WT determines whether or not the dash sensor is to be assembled in the process by referring to the component data area corresponding to the process in the work data storage area, and the determination result is “Yes”. In the case, the serial number of the dash sensor R is written. Also,
The measurement result of each torque is written to each tightening data area corresponding to each tightening operation in the process in the work data storage area.

(3) Sensor & Unit Fitting Inspection Step a. The barcode of the serial number of the SRS unit is read by a barcode reader. b. The fitted state of the dash sensor and the connector of the SRS unit is inspected by a fitted mouse. That is, the fitting portion of each connector of the dash sensor and the SRS unit is formed with a through hole of a predetermined pattern, and when both are normally fitted, a predetermined bar code is formed. Has become. Then, the barcode formed in this manner is optically read by the fitting mouse, and it is determined whether or not the fitting state is normal. <Process of work terminal accompanying the above process> Information read by the mating mouse is sent to the semi-mating inspection device, and information indicating whether the mating state is pass or fail is sent from the device to the work terminal. Sent to At the same time, information indicating the type of the mating connector and, in the case of rejection, the type of rejection is also sent to the work terminal. Whether or not the fitting state is normal is displayed on the work terminal. Next, the work terminal WT reads the work table data, and determines whether the connector that has determined the mating state is a connector to be inspected in the process,
If the result of the determination is "Yes", the SR is stored in the part data area corresponding to the process in the work data storage area.
Write the serial number of the S unit. In addition, the determination result of the fitting state is written in the fitting data area corresponding to the fitting work of the process in the work data storage area.
Here, even if the mating state is normal, if the connector for which the mating check was performed is not the target connector, it is regarded as rejected. In addition to the steps described above, the following steps are performed, and necessary SRS parts are attached to the vehicle body and a fitting inspection is performed as necessary.

When all the work in the process is completed in this way, the work terminal WT writes the work data in which the work contents have been written into the inspection machine data file F6. Writing of work data is performed for each vehicle. If the other terminal changes the work data before completing all the work, the work terminal reads the changed work data,
Inspection unit data file F
Return to 6. Here, when the work terminal attempts to write data and another terminal similarly changes the data, the above is repeated until the data is written normally up to N times (specified number of times). repeat. If normal writing is not performed even after executing N times, NG is displayed on the screen.
Is displayed, and processing for the next vehicle is performed. The allowable number of times of data writing is limited to N or less in order to prevent a prolonged data writing for one vehicle from interrupting the processing of a subsequent vehicle for a long time. In this way, each time the vehicle passes through each process, the work in each process is performed,
Work data is sequentially formed based on the work monitoring results. Then, when the vehicle passes through all the steps necessary for assembling the SRS, the writing of the component data, the tightening data, and the fitting data constituting the work data of the vehicle is completed.

§8. Completed Vehicle Inspection A vehicle that has passed the intermediate inspection is put into the completed vehicle inspection process and arrives before the complete inspection terminal FIT in that process. Then, the worker increases the barcode of the manufacturing history management table, displays the work data on the screen of the complete inspection terminal, and makes a comprehensive determination as to whether or not the operation has been completed normally. If a defect is found as a result of this determination, information that means "passing" is written as an item of the complete inspection determination of the work data. After the completion of the completed vehicle inspection, the complete inspection terminal FIT writes the complete inspection end time in the “complete inspection determination date” and “complete inspection determination time” of the work data shown in FIG. The adjustment terminal ADT writes the adjustment end time in the “adjustment determination date” and “adjustment determination time” of the work data shown in FIG. A shipping determination is made from the inspection and adjustment results, and when the determination is successful, the result is written to a work file, and then the frame number is written to a trigger file to be transmitted to the host computer HST.

§9. Creation of Saved Data The host computer HST determines whether the vehicle can be shipped based on the AF-OFF data sent from the communication terminal CTn. As a result, when it is determined that the vehicle can be shipped, the inspection device data file F6 is searched based on the frame number, and the work data of the vehicle determined to be shipped is read. Then, the management terminal MTn
A key is added to the component data, the tightening data, and the fitting data for the read work data, and the current time is written in “factory shipping date” and “factory shipping time” of the stored data shown in FIG. The storage data is created and written to the storage data file F7. After writing the stored data, the management terminal MTn transmits the work data and A
The F-ON data is deleted from the inspection device data file F6 and the ALC reception file F1, respectively. As described above, since the data corresponding to the vehicle is automatically deleted from the management file when the vehicle is shipped, the capacity of the management file can be reduced. Further, as the capacity of the management file is reduced, the response at the time of accessing the file can be increased, and the efficiency of the system can be improved. In particular, the inspection unit data file F
6 requires a high response since each work terminal WT accesses the work terminal WT. However, as described above, since the data of the shipping vehicle is automatically deleted from the inspection device data file F6, the work terminal WT can quickly search and rewrite the work data.

§10. Factory Return Processing A vehicle that has been determined to have completed the SRS assembly work normally and that has been paid out as a passable car may be broken down during transportation before shipment and returned to the factory. In this case, the host computer HST transmits AF-ON data having the series number and the frame number of the vehicle returned to the factory and an identification code corresponding to “return to factory” to the communication terminal CTn. AF-ON received by the communication terminal CTn
The data is held in the ALC reception file F1. The management terminal MTn searches the storage data file F7 based on the AF-ON data and reads the storage data of the corresponding vehicle. Then, the management terminal MTn creates work data based on the read saved data, and writes the created work data into the inspection device data file F6. At this time, the factory return date is written as “date” in the “transmission serial number” of the work data shown in FIG. 5, and information indicating “passing stop” is written in “shipment judgment” of the work data. I will After writing the work data, the management terminal MTn stores the storage data and the AF-ON data of the vehicle in the storage data file F, respectively.
7 and deleted from the ALC reception file F1. on the other hand,
The inspection of the vehicle returned to the factory is performed, and as a result of the inspection, the vehicle where the defect in the SRS assembling work is found is adjusted by the adjustment terminal ADT at the defective portion.
Also, the work data is updated with the contents of the work accompanying the adjustment. Then, the repaired vehicle is inspected again. Then, a shipping determination is made from the inspection and adjustment results, and if the determination is successful, the frame is written to a work file, and then the frame number is written to a trigger file to be transmitted to the host computer HST. Host computer HS
T determines shipping based on this AF-OFF data,
If it is determined that the shipment can be performed, the AF-ON data added with the identification code indicating “pass” is transmitted to the communication terminal C.
Transmit to Tn. A received by the communication terminal CTn
The F-ON data is held in the ALC reception file F1. The management terminal MTn reads the work data of the vehicle from the inspection device data file F6 based on the AF-ON data. And, as before, create saved data,
Write to the storage data file F7. At this time, a flag “1” indicating that a factory return has been made is written and stored in the “factory return flag” of the stored data in FIG. And
The work data and AF-ON data of the vehicle are transferred to the inspection device data file F6 and the ALC reception file F1.
Remove from.

[0044]

As described above, according to the present invention,
The following effects can be obtained. (1) The data input response and the search response are improved by providing the inspection device data file, which is a file dedicated to writing work results, and the storage file for storing data in the storage means. (2) Re-read the data to the data record in the save file
When inputting, data can be corrected from the saved file
Transfer to a valid inspection unit data file
And that the data in the saved file is erroneously modified
To ensure the reliability of the data in the stored files.
Can be.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a manufacturing history management system according to an embodiment of the present invention.

FIG. 2 is a diagram showing a relationship between various management files and terminals that handle them in the embodiment.

FIG. 3 is a diagram showing a data format in a management file used in the embodiment.

FIG. 4 is a diagram showing a data format in a management file used in the embodiment.

FIG. 5 is a diagram showing a data format in a management file used in the embodiment.

FIG. 6 is a diagram showing a data format in a management file used in the embodiment.

FIG. 7 is a diagram showing a data format in a management file used in the embodiment.

FIG. 8 is a diagram showing a data format in a management file used in the embodiment.

[Explanation of symbols]

MT1 to MT3: management terminal, WT: work terminal, FS
1 to FS3 file server, F1 ALC reception file, F2 ALC transmission file, F3 trigger file, F4 work table, F6 inspection machine data file, F7 storage data file HST
...... Host computer.

──────────────────────────────────────────────────続 き Continued on front page (58) Field surveyed (Int. Cl. ⁷ , DB name) G05B 19/418 B23Q 37/00-41/08

Claims (1)

(57) [Claims] An assembly identifying means for identifying an assembly flowing through a manufacturing line including a plurality of manufacturing processes, and an assembly detecting means for outputting a work result performed on the assembly in the manufacturing process. A work control means provided for each manufacturing process, an inspection check means for checking and inspecting work contents to be performed on an assembly in the manufacturing line, and a work instruction to the work control means for each manufacturing process. Storage means for storing data output from the work control means and the inspection confirmation means, and a management means for controlling data transfer between respective files in the storage means, The storage means is a transmission / reception file for transmitting / receiving data relating to an object to be assembled in the production line from a host computer, and A work data file having work data corresponding to the assembly; an inspection machine data file for writing a result of the work based on the work data of the work data file; And a storage file for storing the data of the inspection unit data file.The management unit reads out the work data in the inspection unit data file based on shipping information transmitted and received by the transmission and reception file, The read work data is changed to data to be stored in the storage file and stored , and
When the factory return information is written to the received file, the factory
From the storage file based on the return information
Read the stored data related to
Change to be able to write to the No.
A production history management system characterized by incorporating