JP2005209180A - Article tracking system, article correlation device, article tracking method, article correlation method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To specify which lot of which component is attached to which body with less error even in the case of a non-arrangement component. <P>SOLUTION: In this article tracking system, RF-ID terminals 220 to 270 read first ID data from an RF-ID tag attached to the container of a component, and read second ID data from an RF-ID tag attached to the body present near the terminals, each RF-ID terminal creates correlation data in which the body is correlated with the container which stores the component attached to the body on the basis of the read first and second ID data, transmits the created correlation data to a management server 200, and the management server 200 stores the correlation data received from each terminal in a history DB and retrieves data coincident with retrieval conditions to be specified from the history DB in which the data is stored. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention associates a part received in a container with a product to which the part is attached, and when it is found that a defect has occurred in a part of a certain lot number, the part corresponding to the lot number is The present invention relates to an article tracking system, an article association apparatus, an article tracking method, an article association method, a program, and a recording medium that enable tracking of an attached product.

  Conventional parts manufacturers such as automobiles create production plan data based on order data from assembly manufacturers, produce parts according to the production plan data, store them in a predetermined container, and include a lot number in the container. Are shipped to assembly manufacturers.

  Containers containing the above parts are loaded on trucks, etc., transported to the assembly manufacturer's platform, delivered in a package such as placing the containers on a cart at a specified location, and moved to the line side by the operator. It is assembled to the car body. At the time of delivery, the delivered parts are inspected by, for example, tracing the barcode on the actual product slip. There are various sizes of the actual product slips according to the types of parts, and the form of the actual product slip is different for each assembly manufacturer except for the common part.

  At present, modularization of parts is progressing in order to improve productivity at an assembly manufacturer and to improve added value.

  Japanese Patent Laid-Open No. 6-68101 (Patent Document 1) discloses production information storage means for collecting and storing product processing times and manufacturing records in the process. In the present invention, the product processing time is recorded, thereby associating with the product number.

In recent years, a mechanism for easily tracing a product by attaching an RF-ID tag to the product has been introduced and put into practical use in a package tracking system or the like.
JP-A-6-68101

  However, in the case of laying parts that are delivered in the order of production, if it is determined by inspection that the platform has been delivered, the ordered parts are attached to the car body in order of production, so which parts are attached to which car body. On the other hand, in the case of a non-laying part, even if it is determined by inspection that it is delivered to which platform, it is not clear at what point it moves to the line side and is attached to which car body. For example, in the past, it was possible to narrow down only to the extent of “XYZ parts attached to an ABC type vehicle on the 15th”.

  As a result, if a defective product is generated due to a temporary malfunction of a parts manufacturer, the leakage cannot be prevented by the inspection of the component manufacturer, and if a vehicle with a defective product flows into the market, It is necessary to collect all vehicle bodies that may have been fitted with the parts, including inspection and parts replacement.

  In this case, if a large number of objects are used, it takes a lot of time for inspection and collection, so that there arises a serious problem that failure and accidents due to defective parts cannot be prevented.

  In addition, the cost of parts required for collection is large, and there is a problem that it is necessary to discard even parts that do not need to be discarded, resulting in a waste of resources.

  In addition, even if it is not leaked to the market, it is necessary to find a completed vehicle with the parts of the mounting lot number to be replaced from among a huge number of completed vehicles at the motor pool and dealer of the assembly manufacturer. There is a problem that a great deal of man-hours is also required to find a car.

  Also, in the invention described in Patent Document 1, the processing time of the product is recorded, but it is not possible to record which lot of parts are attached to the non-allocated parts. It is not possible to track defects and misdelivery of parts.

  Furthermore, even in the method of attaching the RF-ID tag to the above product, if the RF-ID tag is attached to the part, the response signal is mixed with many RF-ID tags in the product to which the parts such as automobiles are attached with tens of thousands of points. End up. For this reason, there is a problem that it is impossible to attach the RF-ID tag to only the important large component and trace the component, which is not practical.

  The present invention has been made to solve the above-described problems. The object of the present invention is to provide a parts manufacturer distribution center, an assembly manufacturer platform, an assembly manufacturer line side, an assembly manufacturer assembly process place, an assembly manufacturer completion inspection place. , Each terminal installed at a plurality of locations in a distribution channel such as a store has a first ID attached to the container that accommodates a first article that is stored in the container and is delivered in the vicinity of the terminal The first ID data is read from the tag, the second ID data is read from the second ID tag attached to the second article to which the first article is attached, and based on the read first and second ID data Each terminal creates association data associating the second article with the container that has accommodated the first article attached to the second article, and the created association data is used as the association data. Transmitting from the terminal to the management server, the management server stores the association data received from each terminal in the memory, and searches the association data stored in the memory for data that matches the specified search condition. This makes it possible to identify which lot of which item (part, etc.) is attached to which item (product, etc.) even if it is not delivered in the order of production. Article tracking system that can greatly reduce the number of targets and the number of market measures for goods after sale and minimize the trouble caused by defective goods in the market because the market measures become faster, and An article association apparatus, an article tracking method, an article association method, a program, and a recording medium are provided.

  The first invention of the present invention is a management server (FIG. 1) capable of communicating with a plurality of terminals (RF-ID terminals 220 to 270 shown in FIG. 1) via a predetermined communication medium (communication line 280 shown in FIG. 1). In the article tracking system configured with the management server 200), the terminal is provided in the container that accommodates a first article (for example, a part or the like) that is stored in a container and is delivered in the vicinity of the terminal. First ID data from the attached first ID tag (container RF-ID tag), second from the second ID tag attached to the second article (for example, vehicle body) to which the first article is attached. Reading means (RF-ID communication module 39 shown in FIG. 3, steps S421 to S422 in FIG. 7), and first and second I read by the reading means. Based on the data, association means for creating association data associating the second article and the container that accommodated the first article attached to the second article (association processing by the CPU 31 shown in FIG. 3; 9 and steps S521 to S544) in FIG. 9 and transmission means for transmitting the association data created by the association means to the management server (history data transmission processing by the CPU 31 shown in FIG. 3, step S425 in FIG. 7). The management server includes storage means (hard disk 28 shown in FIG. 2, steps S441 to S443 in FIG. 7) for accumulating and storing association data received from each terminal.

  According to a second aspect of the present invention, the management server includes a search unit that specifies a search condition and searches the association data stored in the storage unit for data that matches the search condition. .

  In a third aspect of the present invention, the first and second ID tags are RF-ID tags, and the reading means transmits a data request signal (step S521 in FIGS. 9 and 10), and First and second ID data are read from the first and second RF-ID tags by receiving response signals from the first and second RF-ID tags (step S542 in FIGS. 9 and 10). It is characterized by.

  According to a fourth aspect of the present invention, when the ID data read by the reading means includes both the first and second ID data, the associating means is connected to the second article. Create association data associating with the container containing the first article attached to the second article (S521 to S526 in FIG. 9 and FIG. 10 → end, or S521 to S524 → S543 to S544) In the case where only one of the first and second ID data is included in the ID data read by the reading means, the one of the ID data is used as the association data (FIGS. 9 and 9). 10 S521 to S542).

  According to a fifth aspect of the present invention, in the first ID tag, as first ID data, information for specifying the item type of the first item, the number of accommodations, and information for specifying the production lot Is recorded (container RF-ID information shown in FIG. 5), and the second ID tag is recorded with data including information for identifying an individual of the second article ( (Car body RF-ID information shown in FIG. 6).

  The sixth invention of the present invention is characterized in that the first ID tag is attached to a product tag that is previously attached to the container.

  In a seventh aspect of the present invention, the plurality of terminals are installed at a plurality of locations including the vicinity of an installation work location for attaching the first article to the second article, and the reading means The first and second ID data from the first and second ID tags at a predetermined interval (a time interval of about [1/3] to [1/4] of the cycle time for one assembled product to flow) It is characterized by reading.

  The eighth invention of the present invention is an article association apparatus (RF-shown in FIG. 1) capable of communicating with a management server (management server 200 shown in FIG. 1) via a predetermined communication medium (communication line 280 shown in FIG. 1). In the ID terminal 250), a first ID tag (container RF-ID tag) attached to the container that accommodates a first article (for example, a part or the like) that is stored in a container and is delivered nearby. Reading means for reading second ID data (vehicle body RF-ID tag) from first ID data, a second ID tag attached to a second article (for example, a vehicle body) to which the first article is attached. Based on the RF-ID communication module 39 shown in FIG. 3, steps S421 to S422 in FIG. 7, and the first and second ID data read by the reading means, the second article and the second article Take Association means (association processing by the CPU 31 shown in FIG. 3, steps S521 to S544 in FIG. 9 and FIG. 10) for creating association data in association with the container containing the attached first article, and the association means Transmission means (historical data transmission processing by the CPU 31 shown in FIG. 3, step S425 in FIG. 7) for transmitting the association data created by the management server, and the management server receives the association received from each terminal It has a storage means for accumulating and storing data (hard disk 28 shown in FIG. 2, steps S441 to S443 in FIG. 7).

  According to a ninth aspect of the present invention, in the article tracking method in the article tracking system including a plurality of terminals and a management server capable of communicating via a predetermined communication medium, each of the terminals exists in the vicinity of the terminal. First ID data from a first ID tag attached to the container that contains a first article that is delivered in a container, and a second attached to a second article that attaches the first article. Based on the read process of reading the second ID data from the ID tag (steps S421 to S422 in FIG. 7) and the read first and second ID data, each terminal is connected to the second article and the An associating step (steps S521 to S544 in FIGS. 9 and 10) for creating associating data associating with the container that has accommodated the first article attached to the second article, and the created association Transmission step (step S425 in FIG. 7) for transmitting data from each terminal to the management server, and the management server stores the association data received from each terminal in a memory (FIG. 7). Steps S441 to S443) and a search step (step not shown) in which the management server searches the association data stored in the memory for data that matches a specified search condition. .

  According to a tenth aspect of the present invention, in the article association method in the article association apparatus capable of communicating with the management server via a predetermined communication medium, the first article that is stored in a container and delivered in the vicinity of the apparatus is provided. A reading process of reading first ID data from a first ID tag attached to the container to be accommodated, and reading second ID data from a second ID tag attached to a second article to which the first article is attached. (Steps S421 to S422 in FIG. 7) and a container containing the second article and the first article attached to the second article based on the read first and second ID data And an association step (steps S521 to S544 in FIGS. 9 and 10) for creating association data in association with each other, and a transmission step for transmitting the created association data to the management server ( Characterized in that it has 7 steps S434～S425) and.

  An eleventh aspect of the present invention is a program for executing the article tracking method described in the ninth aspect.

  According to a twelfth aspect of the present invention, a program for executing the article tracking method described in the ninth aspect is stored in a storage medium so that the computer can read the program.

  A thirteenth aspect of the present invention is a program for executing the article association method described in the tenth aspect.

  A fourteenth invention of the present invention is characterized in that a program for executing the article association method described in the tenth invention is stored in a storage medium so as to be readable by a computer.

  According to the present invention, a plurality of terminals installed at a plurality of locations in a physical distribution route are attached to the container that accommodates a first article that is stored and delivered in a container that exists in the vicinity of the terminal. The first ID data is read from the first ID tag, the second ID data is read from the second ID tag attached to the second article to which the first article is attached, and the read first and second ID data are read. Each of the terminals creates association data associating the second article with the container that has accommodated the first article attached to the second article, and the created association data The association data transmitted from each terminal to the management server is stored in the memory by the management server, and the data matching the specified search condition is detected from the association data stored in the memory. By doing so, even if it is an article that is arranged in the order of production and is not delivered, which lot of which article (first article such as a part) is attached to which article (second article such as a product) with little error Since it can be identified, it is possible to greatly reduce the number of objects to be collected at motor pools and dealers, and the number of objects to be marketed after sales.

  In addition, the waste of goods is greatly reduced, thus saving resources.

  Furthermore, even when a recall or the like is met after a long period of time has elapsed since the sale, it is possible to greatly save the recall cost and man-hours.

  In addition, since the collection target article can be searched based on the ID tag attached to the second article such as a product, it becomes easy to find the collection target article, and the collection costs of the parts manufacturer and assembly manufacturer can be greatly reduced. Furthermore, since market measures are accelerated, there are effects such as minimizing trouble caused by defective articles in the market.

  Furthermore, even when the product itself is not attached with the RF-ID and the container is refilled, the product lot in question can be traced. Furthermore, even when the RF-ID cannot be directly attached to both the second article (product) and the second article (additional material), it is possible to associate the both, and the target product at the time of occurrence of a malfunction There is an effect that it becomes possible to track.

[First Embodiment]
FIG. 1 is a system configuration diagram showing a system configuration of an article trace system to which the article tracking system and the article association apparatus according to the first embodiment of the present invention can be applied.

  Hereinafter, for the sake of explanation, a case where an automobile part is attached to a vehicle body will be described. However, the present invention is not limited to a combination of an automobile part and a vehicle body to which the automobile part is attached, but the first article and the first article. The present invention can be applied to any combination as long as it is a combination with the second article to which (or contains) the second article.

  In the figure, reference numeral 200 denotes a management server installed at a parts manufacturer. Reference numeral 210 denotes an RF-ID terminal for writing, which is installed at a parts manufacturer. A label of an invoice with an RF-ID tag is affixed to a container shipped by a parts manufacturer (a container in which a part to be shipped is stored) (or the RF-ID tag is directly attached to the container). However, in the following, it is assumed that it is attached to the actual product slip). Data is written to the RF-ID tag attached to the actual product slip by the RF-ID terminal 210 installed in the component manufacturer. Here, the data written in the RF-ID tag is data described in the actual product slip such as the number of parts, the part number, and the lot number.

  Reference numeral 220 denotes an RF-ID terminal installed in a parts manufacturer's distribution center, which reads data from an RF-ID tag attached to the actual product slip at the time of entry, delivery, etc. Data is transmitted to the management server 200 of the component manufacturer via the communication line 280.

  Reference numeral 230 denotes an RF-ID terminal installed on an assembly manufacturer's platform (where the load is unloaded by a truck, etc.), and is attached to the product slip at the timing of assembly manufacturer acceptance (when the platform unloads). Data is read from the received RF-ID tag, and the read data is transmitted to the management server 200 of the component manufacturer via the communication line 280.

  Reference numeral 240 denotes an RF-ID terminal installed on the assembly manufacturer's line side, which reads data from an RF-ID tag attached to the actual product slip at the time of carrying the carriage line side, and communicates the read data. The data is transmitted to the component manufacturer management server 200 via the line 280.

  Reference numeral 250 denotes an RF-ID terminal installed in each assembly process of the assembly manufacturer (the number corresponding to the type of assembly process is installed). Data can be read from the attached RF-ID tag and the RF-ID tag attached to the vehicle body.

  Further, an RF-ID tag is also attached to a member to which a component can be attached (corresponding to a vehicle body in the case of an automobile or the like, and will be described as a vehicle body hereinafter). Can be read.

  Then, the RF-ID terminal 250 associates history data (parts and vehicle bodies shown in FIG. 8 described later) based on the data read from the container RF-ID tags and the data read from the vehicle body RF-ID tags. Data history data) is transmitted to the component manufacturer management server 200 via the communication line 280. As a result, the management server 200 that has received data from the RF-ID terminal 250 records which vehicle body has passed the point process at what time.

  Reference numeral 260 denotes an RF-ID terminal installed at an assembly manufacturer's completion inspection station. When a completed vehicle inspection department or the like is transported, it reads data from an RF-ID tag attached to the vehicle body, and records the vehicle body history. Data is transmitted to the management server 200 of the component manufacturer via the communication line 280.

  Reference numeral 270 denotes an RF-ID terminal installed in a store, which reads data from an RF-ID tag attached to the vehicle body at the timing when it is carried to the store, etc., and transmits the history data of the vehicle body through the communication line 280. To the management server 200 of the parts manufacturer.

  In addition to the RF-ID terminals 220 to 270, a plurality of RF-ID terminals are provided. For example, when a parts maker is delivered (when a truck is loaded), an assembly manufacturer's internal motor pool, an external motor pool, an assembly maker is delivered (truck) When loading, the RF-ID terminal is provided at each position where the RF-ID can be read, and each RF-ID terminal reads the data from the actual product slip or the RF-ID tag attached to the vehicle body. The history data generated based on the above may be transmitted to the management server 200 of the component manufacturer via the communication line 280.

  With the system configuration as described above, the management server 200 installed in the component manufacturer can read data transmitted from each RF-ID terminal (from each location, each item slip, from an RF-ID tag attached to the vehicle body). Recorded history data) and record it by parts.

  Then, when a problem occurs in a part or the like after the installation, which part of which part is attached to which body is identified by the matching process from the RF-ID record managed by the management server 200. After mounting, the parts are traced not by the RF-ID tag of the container but by the RF-ID tag of the vehicle body.

  As a result, even when it is determined that a defect has occurred in a part with a certain lot number, the vehicle body to which the part corresponding to the lot number is attached can be specified to some extent. Although it is not possible to reliably identify only the vehicle body to which the parts of the lot are attached, for example, when the parts are delivered in a container containing 8 parts, the container is taken when the container is brought into the attachment process. From the data read from the RF-ID tag of the product tag attached to the vehicle body, it is possible to narrow down the vehicle body to which the container parts are attached to about 8 to 12 units. It should be noted that there is a certain range in the number of narrowed down vehicle bodies because the remaining parts in the container become small due to the attachment, so that the spare container is also placed in the attachment process at the same time (as shown in FIG. This is because it is difficult to accurately identify which container is attached from which container may have been attached).

  Each RF-ID terminal communicates with the management server 200 using IPv6 to ensure security and performance.

  Further, in the hard disk 28 (shown in FIG. 2 described later) of the management server 200, a history DB generated from the history data received from each RF-ID terminal, application programs, master data of each component, business partners ( Master data of assembly manufacturers and the like are stored. In addition, the various masters may be stored in another server and referred to by the management server 200.

  FIG. 2 is a block diagram showing a hardware configuration of the management server 200 shown in FIG.

  As shown in the figure, the management server 200 includes a CPU 21, a RAM 22, a ROM 23, a network adapter 24, a video adapter 25, a keyboard 26, a pointing device such as a mouse 27, a hard disk 28, and a CD-ROM drive. 29, a recording medium drive such as a DVD-ROM drive, and these are connected to each other via a system bus 20.

  The CPU 21 reads a program stored in the CD-ROM drive 29 in the ROM 23 or the hard disk 28 and executes various control processes described later. The hard disk 28 stores various form information and masters. The RAM 22 is a memory for temporarily storing data and the like when the CPU 21 executes a predetermined process. The network adapter 24 is a communication interface for connecting to the communication line 280.

  FIG. 3 is a block diagram showing a hardware configuration of each RF-ID terminal shown in FIG.

  As shown in the figure, each RF-ID terminal includes a CPU 31, a RAM 32, a ROM 33, a network adapter 34, a video adapter 35, a keyboard 36, a pointing device such as a mouse 37, a hard disk 38, an RF- An ID communication module 39 and a recording medium drive such as a CD-ROM drive 40 and a DVD-ROM drive are provided, and these are connected to each other via a system bus 30.

  The CPU 31 reads out a program stored in the ROM 33, the hard disk 38, or the CD-ROM drive 39 and executes various control processes. The RAM 32 is a memory for temporarily storing data and the like when the CPU 31 executes a predetermined process. The network adapter 34 is a communication interface for connecting to the communication line 280. Reference numeral 41 denotes a monitor that displays various types of information via the video adapter 35. The RF-ID communication module 39 is a module having functions of transmitting RF-ID radio waves and receiving data.

  Hereinafter, various processes in the article tracing system of the present invention will be described with reference to FIGS.

  First, a description will be given of the actual product slip delivered from the component manufacturer to the assembly manufacturer and the RF-ID attached to the actual product slip.

  FIG. 4 is a data configuration diagram showing an example of the configuration of the actual product slip data in the article trace system of the present invention.

  As shown in FIG. 4, the invoice data 600 includes orderer information 601, part number 602, part number (barcode information) 603, part number identification 604, accommodation number 605, accommodation number (barcode information) 606, part. Name 607, delivery destination 608, number of instructions 609, contractor name 610, contractor code 611, contractor code (barcode information) 612, issue number 613, issue number (barcode information) 614, delivery instruction date 615, time 616, an order side part number 617, an element 618, an unloading unit 619, a management department 620, a lot number 621, and the like.

  The orderer information 601 indicates the name of an assembler who places an order. A part number 602 indicates a management number set by the orderer for those items in order to specify the part or the like, and a part number (barcode information) 603 indicates barcode information corresponding to the part number 602. The part number identification 604 indicates identification information used when a part cannot be specified only by the part number 602.

  The accommodation number 605 indicates a standard number for each package appearance at the time of delivery. If the standard number is not reached, the fraction display shall be clearly indicated. The accommodation number (barcode information) 606 indicates barcode information corresponding to the accommodation number 605.

  A component name 607 indicates the name of a component or the like. The delivery destination 608 corresponds to information indicating the business establishment, factory, etc. of the parts delivery destination company, and information indicating the delivery location of the business establishment, factory, etc. of the parts delivery destination company.

  The number of instructions 609 indicates a delivery quantity or a shipment quantity that the orderer presents to the contractor. The contractor name 610 indicates the name of the company receiving the order. The contractor code 611 corresponds to a code indicating a company receiving an order and a code indicating a factory, a business office, a business department, etc. of the company receiving the order. The contractor code (barcode information) 612 indicates barcode information corresponding to the contractor code 611.

  The issue number 613 indicates an identification number assigned to identify the actual product slip, and the issue number (barcode information) 614 indicates barcode information corresponding to the issue number 613.

  The delivery instruction date 615 indicates the delivery date that the orderer presents to the contractor, and the time 616 indicates the delivery time or delivery time category that the orderer presents to the contractor. The order-receiving part number 617 indicates a management number set for the item by the contractor in order to specify the part or the like.

  The key point 618 indicates a requester of parts (ordering company and office). An unloading unit 619 indicates a unit for unloading at the time of delivery. The management department 620 indicates the name of the management department on the contractor side. The lot number 621 indicates the production lot number of the part.

  FIG. 5 is a data configuration diagram showing an example of the data configuration stored in the RF-ID tag attached to the actual product slip data in the article trace system of the present invention.

  An RF-ID tag is attached to the label sheet (actual product form) of the actual product data, and the actual product data 600 shown in FIG. 4 is printed by the RF-ID terminal 210 for writing data on the RF-ID tag. It is assumed that after data (container RF-ID information shown in FIG. 5) is written, it is attached to or attached to a component container and shipped.

  As shown in FIG. 5, the container RF-ID information is composed of a part number 701, an actual product issue number 702, a lot number 703, an ordering source 704, an accommodation number 705, and the like. Data is written by 210.

  The part number 701 is the same data as the part number 602 of the actual product slip data, the actual product slip issue number 702 is the same data as the issue number 613 of the actual product slip data, and the lot number 703 is the lot of the actual product slip data. The ordering source 704 is the same data as the orderer information 601 of the actual product slip data, and the accommodation number 705 is the same data as the accommodation number 605 of the actual product slip data.

  FIG. 6 is a data configuration diagram showing an example of the data configuration stored in the RF-ID tag attached to the vehicle body in the article trace system of the present invention.

  An RF-ID tag is also attached to an assembly product such as an automobile body (a member on which a part is attached), and a body number 801, a specification number 802, etc. are written by an RF-ID terminal for data writing (not shown). Yes.

  FIG. 7 is a flowchart showing an example of a first control processing procedure in the article tracing system of the present invention, and corresponds to the RF-ID data collection processing.

  S401 to S402 indicate steps executed by the RF-ID tag. S421 to S425 indicate steps executed by the RF-ID terminals 230 to 270 shown in FIG. 1, and based on a program stored in the hard disk 38 or other recording medium by the CPU 21 in the RF-ID terminal. Executed. Further, S441 to S443 indicate steps executed by the management server 200 shown in FIG. 1, and are executed by the CPU 21 in the management server 200 based on a program stored in the hard disk 28 or other recording medium.

  First, in step S421, the RF-ID terminal transmits an RF-ID data request signal at regular intervals. The fixed interval is preferably a time of “1/3” to “1/4” of the cycle time for one assembled product to flow. That is, when one product flows in “30 seconds”, the interval is about “7.5 seconds” to “10 seconds”.

  In step S401, when the RF-ID tag is within the effective distance (about 1 to 2 meters) and receives a data request signal with sufficient strength, the process proceeds to step S402, and the stored data in the RF-ID tag is transmitted.

  Next, in step S422, the RF-ID terminal receives stored data output from the RF-ID tag.

  In step S423, the RF-ID terminal executes association processing. Note that in the case of the RF-ID terminal 250 (in the case of the RF-ID terminal installed in the component attachment process), the association processing in step S423 is the RF-ID tag attached to each container at the component attachment location. Corresponding to the process of associating the (container RF-ID tag) with the RF-ID tag (vehicle RF-ID tag) attached to the vehicle body, on the other hand, in the case of an RF-ID terminal other than the RF-ID terminal 250 ( The case of an RF-ID terminal installed outside the component attachment process) corresponds to the process of recording the history of the vehicle body RF-ID tag, and details of the process will be described in detail with reference to FIG.

  Next, in step S424, based on the association information (FIG. 11) generated in step S423, the date time 1201, the production rank 1202, the vehicle body number 1203, the part number 1204, and the actual product issue number 1205 as shown in FIG. The history data including the lot number 1206, the orderer 1207, the number of attachments 1208, etc. is updated and stored in the hard disk 38 of the RF-ID terminal.

  In addition, in the case of an RF-ID terminal other than the RF-ID terminal 250 (in the case of an RF-ID terminal installed other than the part attachment process), the history data to be updated is the production rank 1202, the vehicle body number 1203, etc. Information related to parts shall not be included.

  Next, in step S425, the RF-ID terminal transmits the history data generated and stored in step S424 to the component manufacturer management server 200 at a predetermined timing (for example, once every 10 to 30 minutes). When the transmission process ends normally, a transmitted flag (not shown) of the transmitted history data is turned on. When transmitting the stored history data to the management server 200 at the predetermined timing, the RF-ID terminal checks the history data transmission flag, and if the transmission flag is on. , Do not send. This prevents the history data from being transmitted twice. If the association process in step S423 ends in error and the association fails, error information is also transmitted to the management server 200.

  Then, in step S441, the parts manufacturer management server 200 receives the history data transmitted from the RF-ID terminal, and in step S442, compares the history data with various masters such as the supplier master and the destination master. In step S443, the history DB of the hard disk 28 of the management server 200 is updated (accumulating history data) based on the converted history data, and the process ends.

  By these processes, while the parts are stored in the container, it is possible to easily detect where the parts of the specific lot are located by the RF-ID of the container.

  Further, after the parts are attached to the vehicle body, the vehicle body number and the attached parts are associated with each other, so that it is possible to easily detect where the parts of the specific lot are located.

  FIG. 8 is a data configuration diagram showing an example of history data in the article tracing system of the present invention.

  As shown in FIG. 8, the history data includes date and time 1201, production order 1202, body number 1203, part number 1204, actual product form issue number 1205, lot number 1206, ordering source 1207, number of attachments 1208, and the like.

  9 and 10 are flowcharts showing an example of the second control processing procedure in the article tracing system of the present invention, and correspond to the association processing shown in step S423 of FIG.

  S521 to S546 indicate steps executed by the RF-ID terminal 250 shown in FIG. 1, and are executed by the CPU 21 in the RF-ID terminal based on a program stored in the hard disk 38 or other recording medium. The

  In addition, the process is performed by an RF-ID terminal installed in the vicinity of the worker in the attachment process, and stored data from a plurality of RF-IDs in response to one data request transmission in step S421 in FIG. Sent.

  In order to prevent interference when receiving data stored in a plurality of RF-ID tags, for example, a unique number is stored when the RF-ID tag is manufactured, and this unique number is returned together with other data when responding. It is sufficient to change the response frequency and response time depending on the individual.

  Specifically, the radio wave transmitted from the RF-ID terminal to the RF-ID is time-division multiplexed, or the transmission frequency from the RF-ID terminal to the RF-ID and the response frequency from the RF-ID are different frequencies. The method etc. can be considered. Alternatively, the purpose can be achieved by manufacturing the RF-ID tag transmission circuit with different response times by intentionally varying the capacitance of the capacitor of the transmission circuit. Alternatively, it may be manufactured to intentionally vary the size of a small crystal incorporated in the RF-ID and oscillate different frequencies (using a plurality of channels in the RF-ID tag transmission / reception band).

  Further, the hard disk 38 of the RF-ID terminal stores a correspondence table such as the specification data (specification number 901) of the vehicle body as shown in FIG. 11 and the corresponding part number 902 and the number of attachments 903 per unit. When the power is turned on or when a predetermined time before the start time is reached, the data is read from the hard disk 38 and stored in the RAM 32. This correspondence table defines the correspondence in the case where a plurality of types of parts are attached according to the specifications of the vehicle body in a specific process (shown in FIG. 14). This correspondence table is updated by data transmission from the management server 200 or the like.

  In step S521, the type and number of received RF-ID storage data are determined. For example, “body RF-ID” is “1” and “container RF-ID” is “2”.

  In step S522, after receiving the response of the new container RF-ID tag once, it is determined whether the response from the container RF-ID tag is continuing or disappearing, and the response from the container RF-ID tag is received. If it is determined that the response has disappeared, the process proceeds to step S523 to perform post-processing. Note that the post-processing of step S523 will be described later.

  On the other hand, if it is determined in step S522 that the response from the container RF-ID tag has been received (not lost) after receiving the response of the new container RF-ID tag once, the step is continued. The process proceeds to S524.

  Next, in step S524, it is determined whether or not a response of a new vehicle body RF-ID tag has been received. If it is determined that the response has not been received, in step S543, the container RF-ID tag of the attachment-compatible component. It is determined whether a response from is received. This determination is performed by collating the correspondence table (FIG. 11) in the hard disk 38 with the specification number 1004 in the association information and the part number 704 in the received container RF-ID data.

  If it is determined in step S543 that a response from the container RF-ID tag of the attachment-compatible component has not been received, the process ends as it is.

  On the other hand, if it is determined in step S543 that a response from the container RF-ID tag of the attachment-compatible component has been received (in the case of an RF-ID terminal installed upstream from the component attachment process), The data read from the container RF-ID tag is stored in the area for storing the association information as shown in FIG. 12A, and the process ends. Specifically, first, the association information is cleared, and the date and time when the response is received from the container RF-ID tag, serial data that is sequentially numbered every time new container RF-ID data is received on that date. The production order, the part number 701 in the new container RF-ID data, the actual product slip issue number 702, the lot number 703, the ordering source 704, the number of stored 705, the part number 1005 in the association information, the actual product slip issue number 1006, lot The number 1007, the ordering source 1008, and the number of attachments 1009 are stored. In this case, the date / time 1001, the production rank 1002, the vehicle body number 1003, and the specification number 1004 are not included in the association information.

  On the other hand, if it is determined in step S524 that a new vehicle body RF-ID tag response has been received, an area for storing association information as shown in FIG. 12A in the hard disk 38 in step S525. The data read from the new vehicle body RF-ID tag is stored. Specifically, first, the association information is cleared, and the date and time when the response is received from the vehicle body RF-ID tag, serial data sequentially assigned each time new vehicle body RF-ID data is received on that date. The production order, the body number 801 and the specification number 802 in the new body RF-ID data shown in FIG. 8 are stored as the date / time 1001, the production order 1002, the body number 1003, and the specification number 1004 in the association information.

  Next, in step S526, it is determined whether a response from the container RF-ID tag of the attachment-compatible component has been received. This determination is performed by collating the correspondence table (FIG. 11) in the hard disk 38 with the specification number 1004 in the association information and the part number 704 in the received container RF-ID data.

  If it is determined in step S526 that a response from the container RF-ID tag of the attachment-compatible component has not been received, the processing ends. In the case of an RF-ID terminal other than the RF-ID terminal 250 (in the case of an RF-ID terminal installed downstream from the component attachment process), this is the case, and the process is terminated. Therefore, the generated history information is date time 1001, production rank 1002, and body number 1003, and does not include information related to parts.

  On the other hand, in step S526, it is determined whether or not a response from the container RF-ID tag of the attachment-compatible component has been received. The process after S527 is performed. In this way, the processing limited to the container corresponding to the attachment is performed when a different type of part is attached depending on the specification of the vehicle body as shown in FIG. 14 (parts not related to the current vehicle body). ) May be placed near the RF-ID device, and the RF-ID device also receives a response signal from an RF-ID tag attached to such a container. is there.

  In step S527, it is determined whether or not a response from a new container RF-ID tag has been received. If it is determined that a response has not been received, the process directly proceeds to step S529.

  On the other hand, if it is determined in step S527 that a response from the new container RF-ID tag has been received, a container information storage area for storing the container information shown in FIG. The part number 701 received from a simple container RF-ID tag, the actual product issue number 702, the lot number 703, the ordering source 704, the number of storage 705, the number of attachments 903 obtained from the correspondence table, and the part number of the container information 1101, actual product slip issue number 1102, lot number 1103, ordering source 1104, storage number 1105, and number of attachments 1106 per unit are stored.

  In step S529, the container number n is initialized to “1”. The container numbers are container 1, container 2,..., Container n, container n + 1,..., In order from the container information secured in step S528. To do. As shown in FIG. 15, there are a plurality of containers of the same type of parts as described above. As shown in FIG. 15, when an operator runs out of parts in the container 1, 2 or 3 may be placed, and this is the case.

  Next, in step S530, it is determined whether or not the number of containers n accommodated has already been attached (container n is already empty). If it is determined that it has already been attached (container is already empty), step S545 is performed. Proceed to, and increment the container number n.

  In step S546, it is determined whether or not the container number n exceeds the number of the same type of container RF-ID tags determined in step S521. If it is determined that the container number n has exceeded, there is no next container. Therefore, it ends with an error.

  On the other hand, if it is determined in step S546 that the container number n does not exceed the number of the same type of container RF-ID tags, the process returns to step S530 to perform processing for the container of the next container number.

  On the other hand, if it is determined in step S530 that the accommodation number of the container n has not already been attached (the container n is not yet empty), in step S531, the number of remaining parts Z of the container n (at this time, “accommodation number” 1105-the number of attachments 1109 ") is determined whether or not the number of attachments per unit is 1106 or more, and it is determined that the number of remaining parts Z of the container n is the number of attachments 1106 or more per unit. If so, the process proceeds to step S532.

  In step S532, it is determined whether the number of attachments 1109 of the container n is “0”. If the number of attachments 1109 is “0”, in step S533, the start vehicle body number 1107 of the container n is set. The vehicle body number 1003 in the association information is stored, and the process proceeds to step S534.

  On the other hand, when it is determined in step S532 that the number 1109 of containers n attached is not “0”, the process proceeds to step S534 as it is.

  In step S534, the number of attachments 1109 of containers n is updated (additional number of attachments 1106 is added), and the data of the containers n is stored in the association information (part number 1005 in the association information, actual product issue number) 1006, lot number 1007, ordering source 1008, and number of installations 1009 store the part number 1101, the invoice issue number 1102, the lot number 1103, the ordering source 1104, and the number of installations 1006 per unit in the container information of the container n, respectively. To do).

  Next, in step S535, it is determined whether or not the number of attachments 1109 of the container n is the accommodation number 1105. If the number of attachments 1109 is the accommodation number 1105, the end vehicle body number 1108 of the container n is determined in step S536. The vehicle body number 1003 in the association information is stored in, and the process ends.

  On the other hand, if it is determined in step S535 that the number 1109 of containers n attached is not the accommodation number 1105, the processing is ended as it is.

  On the other hand, if it is determined in step S531 that the number of remaining parts Z of the container n is less than the number of attachments 1106 per unit, in step S537, the container number n + 1 is the same type of container RF− determined in step S521. It is determined whether or not the number of ID tags has been exceeded. If it is determined that the number of ID tags has been exceeded, the next container does not exist and the process ends in error.

  On the other hand, if it is determined in step S537 that the container number n + 1 does not exceed the number of the same type of container RF-ID tags, the process proceeds to step S538.

  In step S538, the number of attachments 1109 of the container n is updated by the number of remaining parts Z, and the data of the container n is stored in the association information (part number 1005 in the association information, actual product issue number 1006, lot number 1007, The order number 1008 and the number of attachments 1009 store the part number 1101, the actual product slip issue number 1102, the lot number 1103, the order origin 1104, and the remaining part number Z in the container information of the second container, respectively.

  Next, in step S539, the vehicle body number 1003 in the association information is stored in the end vehicle body number 1108 of the container n.

  In step S540, one record is added to the association information as shown in FIG. 12B, and the same date and time 1001, production rank 1002, vehicle body number 1003, and specification number 1004 as the first record are stored.

  Next, in step S541, the vehicle body number 1003 in the association information is stored in the start vehicle body number 1107 of the container n + 1, and the process proceeds to step S542.

  In step S542, the number of attachments 1109 of the container n + 1 is updated (“number of attachments per unit—the number of remaining parts Z described above”), and the data of the container n + 1 is added to the newly added association information record. Stored (part number 1005 in association information, item number issuance number 1006, lot number 1007, ordering source 1008, number of attachments 1009 is part number 1101, item number issuance number 1102, lot number number in container information of container n + 1. 1103, ordering party 1104, “the number of attachments per unit—the number of remaining parts Z described above” is stored), and the processing is terminated.

  Hereinafter, the post-processing of step S523 will be described.

  In step S523, it is determined whether or not the end vehicle body number 1108 is stored in the container information of the container RF-ID tag whose response has disappeared. If it is determined that the end vehicle body number 1108 is not stored, “1” is set in the flag 1110. (The warning flag is turned on), and data indicating that the end vehicle number is unknown (for example, “−1”) is stored as the end vehicle number 1108, and a warning history (not shown) in the hard disk 28 is stored. In addition, the container information storage area is opened.

  On the other hand, when it is determined that the end vehicle body number 1108 is stored in the container information of the container RF-ID tag whose response has disappeared, the container information storage area is opened as it is.

  Hereinafter, with reference to FIGS. 16 and 17, a history DB search process stored in the management server 200 by the RF-ID data collection process illustrated in FIG. 7 will be described.

  FIG. 16 is a schematic diagram illustrating an example of a search screen for searching the history DB of the management server 200 illustrated in FIG. 1, and can be displayed on the monitor of the client device by accessing the management server 200.

  FIG. 17 is a schematic diagram showing an example of a search result display screen of the history DB of the management server 200 shown in FIG. 1, which can be returned from the management server 200 and displayed on the monitor of the client device.

  First, in the search screen shown in FIG. 16, as search conditions, for example, a supplier selection by a supplier selection column 1501, a selection of a component category by a component category selection column 1502, a search range of component numbers by a component number selection column 1503 to 1504. Selection, selection of lot number search range in lot number selection columns 1505-1506, search condition such as production date and destination in search condition selection columns 1507-1512, and input of the range, etc. are performed, and search button 1513 is designated. Thus, the search condition and the search instruction are transmitted from the client device to the management server 200.

  The management server 200 receives a search condition and a search instruction transmitted from the client device, searches the history DB in the hard disk 28 etc. for data corresponding to the received search condition, and based on the search result in FIG. The screen data of the search result list as shown is generated and returned to the client device described above. The client device receives and displays the screen data of this search result list. Note that these processes executed in the management server 200 are executed by the CPU 21 in the management server 200 based on a program stored in the hard disk 28 or other recording medium.

  Further, the client side processing simply displays an HTML file (screen shown in FIGS. 16 and 17) in the browser application, and the server side transmits an event to the management server 200, so that the server side can perform CGI or For example, a search process may be performed using a servlet, or a dedicated application is installed in the client device (or an applet or the like is downloaded from the management server 200), as shown in FIGS. The screen may be displayed and a search instruction may be given.

  As described above, the history DB collected by the RF-ID terminal and stored in the management server 200 is subjected to a search process under search conditions such as a part number, a lot number, a vehicle body production date, a part production date, and the like. Even so, it is possible to specify with a small error which vehicle body a part produced in a certain production lot is attached to, which distribution the vehicle body is currently in.

[Other Embodiments]
In the first embodiment, the case where the RF-ID terminal is typically a dedicated terminal or a personal computer has been described. However, the RF-ID terminals 210, 220, and 270 illustrated in FIG. It may be a multifunction machine (equipment having a complex function such as a scan function, a print function, and a copy function) equipped with means, a CPU, and a LAN adapter. In this case, it is assumed that the program for the RF-ID terminal is stored in a storage unit such as a hard disk of the multifunction device, read out to the RAM of the multifunction device, and executed by the CPU of the multifunction device.

  As described above, according to the present invention, it is possible to specify which lot of which part is attached to which vehicle body even with non-laying parts with less error. The number of vehicles subject to market measures after sales can be greatly reduced. Also, parts disposal is greatly reduced, saving resources. In addition, even if there is a recall after a long period of time has passed since the sale, it is possible to greatly save the recall cost and man-hours.

  In addition, since the vehicle to be collected can be searched based on the RF-ID attached to the vehicle body, it is easy to find the vehicle to be collected, and the collection costs of the parts manufacturer and assembly manufacturer can be greatly reduced.

  Furthermore, since market measures are accelerated, failures and accidents caused by defective parts in the market can be minimized.

  In each of the above-described embodiments, an RF-ID tag is attached to an actual product slip and a vehicle body that are attached to a container in which automobile parts are accommodated at the time of delivery, and information similar to the information described on the actual product slip is attached to the RF-ID tag of the container. In the above description, the vehicle number is stored in the RF-ID tag of the vehicle body, and the history data is stored by associating the parts attached from the container with the vehicle body. Is not limited to automobile parts and vehicle bodies, and may be applied to the association between a first article and a second article to which the first article is attached (or housed). For example, an RF-ID tag is attached to the actual product slip attached to the container in which the first article is stored and the second product at the time of delivery, and the information similar to the information described in the actual product slip is attached to the RF-ID tag of the container. The information is stored, the serial number such as the manufacturing number of the second article is stored in the RF-ID tag of the second article, and attached (or stored) from the container to the second article. The history data may be stored by associating the first article with the second article.

  In addition, for example, the first article is a food product, and the container for bringing the food into the factory is attached with an RF-ID, and the second article is a shipping container (with an RF-ID for containing the food product). It may be a package such as a bag or a box. In this case, even when a problem such as contamination of foreign matter occurs in food in a certain production lot, the RF-ID identification number of the carry-in container corresponding to the production lot is stored in the memory of the RF-ID terminal and the corresponding time By storing the RF-ID identification number of the shipping container that has flowed through the line in the memory of the RF-ID terminal, it is possible to correlate the two, and which shipping container is the food produced in the lot where the problem occurred It is possible to identify whether or not the product has been shipped in a quick and accurate manner.

  That is, according to the above-described embodiment, the product itself is not attached with the RF-ID, and the product lot in question can be traced even when the container is refilled. In particular, the use of RF-ID eliminates the need for barcode scanning, image recognition by a camera, etc., and therefore has the effect of preventing recognition errors due to barcode contamination or the like.

  As yet another example, the first article is an additional material added to the second article (seasoning, cream, etc. when the product is a food product), and the additional material has an RF-ID attached to the line side. The second article (food, etc.) flows through the line, and the second article lot number at a specific time when the second article flows through the process is externally networked. In the case where there is a defect in a specific lot of the first item, the second item in which the first item having the defect is used is also received by storing the information in the memory of the RF-ID terminal. It becomes possible to associate with an article.

  In this embodiment, even when the RF-ID cannot be directly attached to both the second article (product) and the second article (additional material), it becomes possible to associate the both, and when a malfunction occurs. It is possible to track the target product.

  In each of the above embodiments, the case of using an RF-ID tag has been described. However, a transmitter other than the RF-ID tag may be used.

  Furthermore, using normal tags (tags not composed of electronic components) that are neither RF-ID tags nor transmitters, ID data such as character strings, symbols, and patterns printed on the tags in the vicinity of the terminal, It is also possible to read the data printed on the tag by picking up an image with a CCD camera or the like provided in the terminal (non-contact), and recognizing the image pickup result with OCR or the like.

  In the present embodiment, the various types of data shown in FIGS. 7, 9, and 10 are stored in the external memory of the product information providing server 200. In addition to this, various types of data for realizing the various types of processing described above. The data may be stored in an external memory or a database.

  Further, the configuration and contents of the various data described above are not limited to this, and it is needless to say that they are configured with various configurations and contents according to applications and purposes.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The configuration of a data processing program that can be read out by the article trace system according to the present invention will be described below with reference to the memory map shown in FIG.

  FIG. 18 is a schematic diagram illustrating a memory map of a storage medium that stores various data processing programs that can be read by the article tracing system according to the present invention.

  Although not particularly illustrated, information for managing a program group stored in the storage medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, a program for installing various programs in the computer, and a program for decompressing when the program to be installed is compressed may be stored.

  The functions shown in FIGS. 7, 9, and 10 in this embodiment may be performed by a host computer by a program installed from the outside. In this case, the present invention is applied even when an information group including a program is supplied to the output device from a storage medium such as a CD-ROM, a flash memory, or an FD, or from an external storage medium via a network. Is.

  As described above, a storage medium storing software program codes for realizing the functions of the above-described embodiments is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium in the storage medium. It goes without saying that the object of the present invention can also be achieved by reading and executing the programmed program code.

  In this case, the program code itself read from the storage medium realizes the novel function of the present invention, and the storage medium storing the program code constitutes the present invention.

  Therefore, as long as it has the function of the program, the form of the program such as an object code, a program executed by an interpreter, or script data supplied to the OS is not limited.

  As a storage medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape, nonvolatile memory card, ROM, DVD, etc. Can be used.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention.

  As another program supply method, a client computer browser is used to connect to an Internet form page, and the computer program itself of the present invention or a compressed file including an automatic installation function is recorded on the hard disk or the like from the form page. It can also be supplied by downloading to a medium. It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different form page. That is, a WWW server, an ftp server, and the like that allow a plurality of users to download a program file for realizing the functional processing of the present invention on a computer are also included in the claims of the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decrypting from a form page via the Internet is given to users who have cleared predetermined conditions. It is also possible to download and use the key information to execute the encrypted program and install it on the computer.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Further, after the program code read from the storage medium is written to a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading the storage medium storing the program represented by the software for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention. .

  The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these are excluded from the scope of the present invention. is not.

  Although various examples and embodiments of the present invention have been shown and described, those skilled in the art will not limit the spirit and scope of the present invention to the specific description in the present specification.

  Moreover, all the structures which combined said each embodiment are also contained in this invention.

1 is a system configuration diagram illustrating a system configuration of an article tracing system to which an article tracking system and an article association apparatus according to a first embodiment of the present invention can be applied. It is a block diagram which shows the hardware constitutions of the management server shown in FIG. It is a block diagram which shows the hardware constitutions of each RF-ID terminal shown in FIG. It is a data block diagram which shows an example of a structure of the actual item slip data in the goods trace system of this invention. It is a data block diagram which shows an example of the data structure stored in the RF-ID tag attached to the actual item slip data in the goods trace system of this invention. It is a data block diagram which shows an example of the data structure stored in the RF-ID tag attached to the vehicle body in the goods trace system of this invention. It is a flowchart which shows an example of the 1st control processing procedure in the goods trace system of this invention. It is a data block diagram which shows an example of the historical data in the goods trace system of this invention. It is a flowchart which shows an example of the 2nd control processing procedure in the goods trace system of this invention. It is a flowchart which shows an example of the 2nd control processing procedure in the goods trace system of this invention. It is a schematic diagram which shows an example of the corresponding | compatible table in the goods trace system of this invention. It is a schematic diagram which shows an example of the association information in the article | item trace system of this invention. It is a schematic diagram which shows an example of the container information in the goods trace system of this invention. It is a schematic diagram explaining the relationship between the vehicle body and a container in the goods trace system of this invention. It is a schematic diagram explaining the relationship between the vehicle body and a container in the goods trace system of this invention. It is a schematic diagram which shows an example of the search screen for searching log | history DB of the management server shown in FIG. It is a schematic diagram which shows an example of the search result display screen of log | history DB of the management server shown in FIG. It is a schematic diagram explaining the memory map of the storage medium which stores the various data processing program which can be read by the goods trace system which concerns on this invention.

Explanation of symbols

200 Management server 210 RF-ID terminal (for writing)
220-270 RF-ID terminal 280 Communication line

Claims (14)

In an article tracking system composed of a plurality of terminals and a management server capable of communicating via a predetermined communication medium,
Each terminal is
1st ID data from the 1st ID tag attached to the said container which accommodates the 1st goods accommodated in the container and which exists near a terminal, and the 2nd article which attaches the said 1st article Reading means for reading the second ID data from the second ID tag attached to
Based on the first and second ID data read by the reading means, association data associating the second article with a container that has accommodated the first article attached to the second article. An association means to create;
Transmission means for transmitting the association data created by the association means to the management server,
The management server
An article tracking system comprising storage means for accumulating and storing association data received from each terminal.   The article tracking system according to claim 1, wherein the management server includes a search unit that specifies a search condition and searches the association data stored in the storage unit for data that matches the search condition. The first and second ID tags are RF-ID tags,
The reading means transmits a data request signal and receives a response signal from the first and second RF-ID tags, thereby receiving first and second ID data from the first and second RF-ID tags. 3. The article tracking system according to claim 1 or 2, wherein When the ID data read by the reading means includes both the first and second ID data, the associating means is attached to the second article and the second article. Create association data associating with the container that contained the first article,
When only one of the first and second ID data is included in the ID data read by the reading means, the one of the ID data is used as association data. Item tracking system in any one of claim | item 1-3. In the first ID tag, data including information for specifying the item type of the first item, the number of accommodations, and information for specifying the production lot is recorded as the first ID data.
5. The article tracking system according to claim 1, wherein data including information for specifying an individual of the second article is recorded in the second ID tag.   The article tracking system according to any one of claims 1 to 5, wherein the first ID tag is attached to an actual product tag that is affixed to the container in advance. The plurality of terminals are installed at a plurality of locations including the vicinity of an installation work location for attaching the first article to the second article,
The article tracking system according to claim 1, wherein the reading unit reads the first and second ID data from the first and second ID tags at the predetermined interval. In the article association apparatus capable of communicating with the management server via a predetermined communication medium,
From the first ID tag attached to the container containing the first article to be delivered in a container that is present in the vicinity to the first ID data, the second article to which the first article is attached Reading means for reading the second ID data from the attached second ID tag;
Based on the first and second ID data read by the reading means, association data associating the second article with a container that has accommodated the first article attached to the second article. An association means to create;
Transmission means for transmitting association data created by the association means to the management server;
An article association apparatus characterized by comprising: In the article tracking method in the article tracking system including a plurality of terminals and a management server capable of communicating via a predetermined communication medium,
Each of the terminals receives first ID data and the first article from a first ID tag attached to the container that houses the first article that is delivered in a container that is present near the terminal. A reading step of reading the second ID data from the second ID tag attached to the second article to be attached;
On the basis of the read first and second ID data, each terminal associates the second article with a container containing the first article attached to the second article. An association step to create data;
A transmission step of transmitting the created association data from each terminal to the management server;
The management server accumulates the association data received from each terminal in a memory;
A search step in which the management server searches the association data stored in the memory for data that matches a specified search condition;
An article tracking method characterized by comprising: In the article association method in the article association apparatus capable of communicating with the management server via a predetermined communication medium,
1st ID data from the 1st ID tag attached to the said container which accommodates the 1st goods accommodated in the container and which exists near the apparatus, and the 2nd article which attaches the said 1st article A reading step of reading the second ID data from the second ID tag attached to
An associating step of creating associating data associating the second article and the container containing the first article attached to the second article based on the read first and second ID data When,
A transmission step of transmitting the created association data to the management server;
An article association method characterized by comprising:   A program for executing the article tracking method according to claim 9.   A storage medium storing a computer-readable program for executing the article tracking method according to claim 9.   A program for executing the article association method according to claim 10.   A storage medium storing a computer-readable program for executing the article association method according to claim 10.

Images