Produce is often packaged in clamshell units. Such clamshells provide retailers and restaurant operators with a standardized merchandizing unit, offer brand owners a labeling opportunity, and offer convenience to the consumer. Clamshells are typically manufactured using a thermal forming process. Following their manufacture, clamshells are typically nested together to save space and stored in bulk containers.
Adding traceability to item-level produce requires putting a unique code on each package, such as each clamshell. In some prior art implementations, codes have been added with an inkjet system. Problems with the use of inkjet systems to mark codes onto clamshells and other packages include (a) inkjet systems require considerable maintenance, (b) codes tend to be poorly printed and therefore difficult to read, and (c) typical inkjet systems cannot reliably print small barcodes, and barcodes are needed for automated scanning such as along the distribution chain, in stores, or anywhere one has a mobile phone configured with a barcode reader.
An exemplary method comprises reading a traceability code from a clamshell of a stack of a plurality of clamshells, reading a unique identifier disposed on a container, storing the traceability code read from the clamshell of the stack in association with the unique identifier, and placing the stack in the container. In some embodiments, the method further comprises reading the traceability code from the clamshell with a first scanner disposed on a table, and in some of these embodiments the method further comprises reading the unique identifier from the container with a second scanner disposed on the table.
In some embodiments, before reading the traceability code, the method further comprises printing a traceability code on each of a plurality of labels. In some of these embodiments, the method further comprises marking each of the plurality of clamshells with a traceability code by affixing a label of the plurality of labels to each of the clamshells. In other embodiments, the method further comprises, before reading the traceability code, marking each of the plurality of clamshells with a traceability code such as by printing directly onto the clamshells. In further embodiments, such as some of the embodiments that comprise marking each of the plurality of clamshells with the traceability code, the method further comprises nesting the plurality of marked clamshells together to form the stack. In some of these embodiments, the method further comprises reading a traceability code from each of the plurality of clamshells before nesting the plurality of clamshells. The method, in some embodiments, further comprises fabricating the plurality of clamshells, labeling the plurality of clamshells each with a unique traceability code, reading the unique traceability code from each of the plurality of clamshells, and then nesting the plurality of clamshells.
Another exemplary method comprises marking each of a plurality of clamshells with a traceability code and nesting the plurality of marked clamshells together to form a stack. The method further comprises storing an association between the traceability code read from a clamshell of the stack and a unique identifier of a container and placing the stack in the container. Some embodiments further comprise reading the unique identifier from the container and determining a traceability code from the unique identifier, for example, by referencing the unique identifier in a database.
In various embodiments storing the association between the traceability code read from the clamshell of the stack and the unique identifier of the container includes uploading the traceability code and the unique identifier to a host computing system. In some of these embodiments the method further comprises reading a traceability code from each of the plurality of marked clamshells before nesting the plurality of marked clamshells. The method can further comprise uploading to the host computing system the traceability codes read from each of the plurality of marked clamshells and associating the traceability codes read from each of the plurality of marked clamshells with the unique identifier. Still further embodiments of the method further comprise uploading to the host computing system harvest event data and associating the harvest event data with the unique identifier of the container.
An exemplary table comprises a top surface, a lateral rail disposed on the top surface proximate and extending generally parallel to a front side of the top surface, and a transverse rail disposed on the top surface generally perpendicular to the lateral rail. The table also comprises a first scanner configured to read a traceability code on a clamshell held against a first side of the transverse rail and a second scanner configured to read a unique identifier disposed on a container disposed proximate to the top surface. In some embodiments, the table is configured to be mobile. The first scanner is disposed proximate to a second side of the transverse rail, in some embodiments, where the second side opposes the first side. In various embodiments, an orientation of the first scanner and/or an orientation of the second scanner is adjustable. The table can further including a calibration marking disposed on the lateral rail. The table can also further comprise a computing system having processing means including logic configured to associate a unique identifier read by the second scanner with one or more traceability codes read by the first scanner, as well as logic configured to store the association.
An exemplary system for associating clamshells with containers comprises means for consistently positioning a stack of clamshells, each clamshell including a traceability code and means for reading the traceability code from one clamshell of the stack when the stack is positioned by the means for consistently positioning the stack. The system also comprises means for reading a unique identifier from a container, and means for storing an associate between a unique identifier read by the means for reading the unique identifier and the traceability code read by the means for reading the traceability code.
Still another exemplary system for associating clamshells with containers comprises a table, including first and second scanners, and a third scanner in communication with the table. The table also includes a transverse rail disposed on a top surface thereof. The first scanner is configured to read a traceability code on a clamshell of a stack of clamshells when held against the transverse rail, and the second scanner is configured to read a unique identifier disposed on a container disposed proximate to the top surface. In various embodiments the system further comprises a labeler configured to affix labels to clamshells, and wherein the third scanner is configured to read traceability codes from the labels affixed to the clamshells by the labeler. The system can also comprise either or both of a clamshell fabricator and a host computing system. In those embodiments that comprise the host computing system, the table can further include logic configured to upload traceability codes and unique identifiers to the host computing system. In some of these embodiments the host computing system includes association logic configured to associate traceability codes with unique identifiers and configured to store the associations.
The present disclosure is directed to systems and methods for associating traceability codes on unit-level packages, such as on clamshells, with unique identifiers of the containers in which the unit-level packages are stored prior to being deployed to be filled at a harvest event. By making this association, an entire container of unit-level packages, each bearing a unique traceability code, can be later associated with the harvest event data for that harvest event, for example, by reading the unique identifier of the container when deployed at the harvest event and then associating that unique identifier with the harvest event data. It will be understood that although embodiments of the invention are described with reference to clamshells for produce, the invention is equally applicable to other unit-level packaging that when empty can be nested to form stacks, such as cups.
Some embodiments of the present invention are directed to a table that facilitates making the clamshell-to-container associations at the time that the containers are filled with clamshells. In some instances, the table is mobile so that the table can be readily moved between clamshell production areas. The table includes two scanners, one configured to read traceability codes from clamshells, and another configured to read unique identifiers on containers placed proximate to the table.
Further embodiments of the present invention are directed to systems that include the table and at least a third scanner, external to the table, and in communication with the table. The system optionally comprises one or more components of a clamshell production line including one or more clamshell fabricators, labelers, and nesting equipment. The third scanner is situated relative to the line in order to read each traceability code on each labeled clamshell prior to the clamshells being nested together into stacks. Exemplary systems can further comprise a host computing system that can upload data from the table and store associations between the traceability codes read by the first and third scanners, and unique identifications read by the second scanner. In some embodiments, the host computing system also provides the traceability codes to the labeler. Still further embodiments of the present invention are directed to methods for using tables described herein to prepare containers of pre-labeled and nested clamshells to be deployed to harvest events, and methods for associating harvest event data with the clamshells supplied in a container.
The top surface 105 is bounded by two sets of opposing sides, one set including a front side 120 and a back side 125, the other including a left side 130 and a right side 135. The table 100 also comprises a lateral rail 140 and a transverse rail 145. The lateral rail 140 can be disposed on the top surface 105 proximate to, and extending generally parallel to, the front side 120. A person using the table 100 to associate traceability codes on clamshells with unique identifiers on containers stands at the front side 120 of the table 100 and hold stacks of clamshells against the lateral rail 140 as described with respect to
The lateral rail 140, in some embodiments, includes one or more calibration markings 150 to indicate one or more lengths measured from the transverse rail 145, where each length is calibrated to a stack of a known number of clamshells, for example, sixty clamshells. Thus, a stack of the number of clamshells, when held against the transverse rail 145, will extend just to the calibration marking 150. The calibration marking 150 can be an inscribed line, notch, or other suitable marking.
The transverse rail 145 can be disposed on the top surface 105 generally perpendicular to the lateral rail 140. In some embodiments, the lateral rail 140 and transverse rail 145 are joined together, as shown, while in other embodiments the rails 140, 145 terminate separately. The table 100 can be left-handed or right-handed, depending on whether the transverse rail 145 is disposed closer to the left side 130 or the right side 135, as particularly illustrated in
The table 100 also comprises a means for reading a traceability code on a clamshell when the clamshell is held against a first side 160 of the transverse rail 145. An example of such means is a first scanner 155. The first scanner 155 is configured to read a traceability code on the clamshell by being oriented to scan in the direction of the traceability code from a position on the top surface 105 within range of the traceability code, when the clamshell is appropriately positioned. For example, the first scanner 155 can be disposed on the top surface 105 proximate to the transverse rail 145. The first scanner 155 can be adjustably attached to the top surface 105 such that the orientation of the first scanner 155 can be set to different clamshell designs and different traceability code locations thereon, for instance. In some embodiments, the first scanner 155 is disposed proximate to a second side 165 of the transverse rail 145, where the second side 165 opposes the first side 160.
The table 100 also comprises a means for reading a unique identifier disposed on a container disposed proximate to the top surface 105, such as a second scanner 170. In the illustrated embodiment, the second scanner 170 is disposed on the top surface 105 proximate to the right side 135 of the table 100 and aimed towards a location where containers can be placed proximate to the top surface 105. The second scanner 170 can be adjustably attached to the top surface 105 such that the orientation of the second scanner 170 can be set to different container dimensions and different unique identifier locations thereon, for instance.
The table 100 can also comprise a computing system including processing means 175, a display 180, and an input device (not shown) like a keyboard and/or a mouse, in some embodiments. The processing means 175 is in communication with the first and second scanners 155, 170 and optionally in communication with a host (not shown) over a wireless communication link, for example. The processing means 175 can be, in some embodiments, a personal computer (PC). The processing means 175 includes logic configured to associate a unique identifier read by the second scanner 170 with one or more traceability codes read by the first scanner 155, and logic configured to store such associations, for instance, in a database. In
The system 600 also comprises a third scanner 625 configured to read the traceability codes 210 from individual clamshells 205. As shown in
In some embodiments, the system 600 also comprises a labeler 630. In these embodiments unlabeled clamshells 205 are labeled by the labeler 630 before the third scanner 625 reads the traceability codes 210 from those clamshells 205. In the alternative, labels can be applied by hand to unlabelled clamshells 205 instead of by a labeler 630. In still other embodiments, the as-received clamshells 205 are both labeled and nested, and are subsequently de-nested and read by the third scanner 625 before being nested to form the stack 200.
In various embodiments the system 600 further comprises a fabricator 635, such as a thermoformer, that fabricates clamshells 205. In some of these embodiments the fabricator 635, labeler 630, and third scanner 625 are arranged in the series shown in
The system 600 can further comprise a host computing system 640, in some embodiments. The host computing system 640 is configured to be able to communicate with the logic 620 of the table 605 across a network 645, such as the Internet. In these embodiments the logic 620 is also configured to be able to communicate with the host computing system 640 across the network 645.
It will be appreciated that the logic 620 and the host computing system 640 do not have to be in continuous communication, but can communicate intermittently, such as when needed. Accordingly, in some embodiments the logic 620 is configured to store to a memory device (not shown) data received from the first and second scanners 610, 615, and optionally from the third scanner 625, when present. In various embodiments the memory device can comprise a volatile memory such as random access memory (RAM) or non-volatile memory, such as a hard disk drive. In embodiments in which the logic 620 stores data received from the scanners 610, 615, and 625, the logic 620 may be further configured to store a timestamp in association with each traceability code 210 read by the first scanner 610 and the third scanner 625 and each unique identifier read by the second scanner 615. The logic 620 in these embodiments can be further configured to upload the associated pairs of traceability codes 210 and timestamps, and unique identifiers and timestamps, to the host computing system 640 when the two are in communication. In the alternative, traceability codes 210 read by the third scanner 625 can be stored according to the order in which they were read, without reference to timestamps.
In some embodiments, the logic 620 is configured to associate traceability codes 210 read by the third scanner 625 with the unique identifiers read by the second scanner 615. In other embodiments, the host computing system 640 includes such association logic. One way in which to make this association is to associate a traceability code 210 read by the first scanner 610 with a unique identifier read by the second scanner 615, and then associate with that unique identifier a number of clamshells 205 read by the third scanner 625, such as a number of traceability codes 210 read by the third scanner 625 either immediately before or immediately following the particular traceability code 210 that was read by the first scanner 610. All of the associations between traceability codes 210 and unique identifiers can be stored in a database 650 in communication with the host computing system 640. The database can be queried by traceability code
For example, if stacks 200 comprises 100 clamshells 205 each, and clamshells 205 are added to the stacks 200 in the order in which they were labeled and read, then the traceability code 210 of the clamshell 205 on the bottom of a stack 200 will have been read by the third scanner 625 first, followed by the 99 other traceability codes 210 in the stack 200. If the traceability code 210 of the top clamshell 205 on the stack 200 is later read by the first scanner 610, then the 99 traceability codes 210 read by the third scanner 625 that precede the particular traceability code 210 subsequently read by the first scanner 610 can be further associated with the unique identifier read by the second scanner 615.
All of the associations between traceability codes 210 and unique identifiers can be stored by the host computing system 640 in a database 650 in communication therewith. The database 650 can be queried by traceability code 210 to find a unique identifier of a container 300 in which the clamshell 205 bearing that traceability code 210 was nested. In addition, all of the clamshells 205 in the same stack 200, and in the same container 300, as the target clamshell 205 can be identified. Further, harvest event data for one or more harvest events may be further associated with the unique identifier and therefore can be found by knowing a particular traceability code 210.
In the top example in
The method 800 optionally begins with a step 810 of printing the traceability codes 210 on labels. The labels can be disposed in sheets or on rolls, for example. It will be appreciated that each generated traceability code 210 is unique. Exemplary methods for generating and printing traceability codes 210 are described, for example, in U.S. patent application Ser. No. 11/743,648 filed on Sep. 6, 2007 and titled “System and Method of Product Information Coding and Authentication” which is a Continuation-in-Part of U.S. patent application Ser. No. 11/347,424 filed on Feb. 2, 2006 and titled “Method and System for Deterring Product Counterfeiting, Diversion and Piracy,” which claims priority from U.S. Provisional Patent Application No. 60/650,364 filed on Feb. 3, 2005 and titled “System, Method and Technique for Combating Product Counterfeiting, Piracy and Diversion,” each of which is incorporated herein by reference.
In some embodiments, the step 810 of printing the traceability codes 210 on labels includes generating the traceability codes 210 with a host computing system 640 and transmitting the traceability codes 210 from the host computing system 640 over a network connection to a secure printing device, for instance, to labeler 630. Communication between the labeler 630 and the host computing system 640 can optionally run through the logic 620. In other embodiments the labels are printed at a site remote from the labeler 630 and then transferred to the site of the labeler 630.
It will be appreciated that step 810 is optional in that some methods of the invention can be practiced by an entity using pre-printed labels supplied by another entity. Step 810 is also optional because in some embodiments labels are not used and instead the traceability codes 210 are printed directly onto the clamshells.
The method 800 optionally also comprises a step 820 of fabricating clamshells 205. Fabricating clamshells 205 can comprise, for example, thermoforming the clamshells 205. In some alternative embodiments, rather than the step 820 of fabricating the clamshells 205, the clamshells 205 are received from a manufacturer. Here, the as-received clamshells 205 are unlabeled and nested in stacks 200. In these embodiments the method 800 further comprises singulating the as-received clamshells 205 from the nested stacks 200.
The method 800 optionally also comprises a step 830 of marking each of a plurality of clamshells 205 with a traceability code. In some embodiments, such as those embodiments that include step 810 of printing the traceability codes on labels, step 830 includes affixing a label to each of the plurality of clamshells 205. Affixing the labels to the plurality of clamshells 205 can be performed either manually or mechanically, such as with a labeler 630. In other embodiments, each traceability code can be printed or otherwise inscribed directly onto the clamshell 205. Regardless of the method of marking the clamshells 205, each traceability code 210 should be marked in approximately the same location on each clamshell 205.
The method 800 optionally also comprises a step 840 of reading a traceability code 210 from each of the plurality of clamshells 205. This step can be performed, for instance, with the third scanner 625 as labeled clamshells 205 are transported past the third scanner 625. Step 840 can further comprise transmitting the traceability code 210 from the third scanner 625 to logic 620 of the table 605.
Some embodiments of the method 700 that include the step 830 of marking each of the plurality of clamshells 205 also comprise a step 850 of nesting the plurality of marked clamshells together to form a stack 200. In those embodiments of the method 800 that additionally include the optional step 840 of reading a traceability code 210 from each of the plurality of clamshells 205, the step 850 is performed after the step 840.
The method 800 comprises a step 860 of reading a traceability code 210 from a clamshell of the stack 200, and a step 870 of reading a unique identifier disposed on a container 300. Reading the traceability code 210 from the clamshell of the stack 200 can comprise, for example, scanning the traceability code 210 from the clamshell, or from a label affixed thereto, with the first scanner 155. Likewise, reading the unique identifier disposed on the container 300 can comprise, for example, scanning the unique identifier with the second scanner 170. The unique identifier can be printed or otherwise inscribed on the container 300, or provided on a label.
The steps 860, 870 can occur in either order or generally at the same time. It will be appreciated that although
In some embodiments, in step 870, a container 300 is placed proximate to the top surface of the table 100 and a user of the table 100 provides an input to the processing means 175 of the computing system to read the unique identifier, whereupon the processing means 175 controls the second scanner 170 to read and communicate the unique identifier to the processing means 175. In other embodiments simply bringing the unique identifier within range of the second scanner 170 will cause the second scanner 170 to read the unique identifier.
In some embodiments, in step 860, a stack 200 of clamshells 205 in positioned against the lateral rail 140 and the transverse rail 145 such that a top clamshell 205 of the stack 200 faces the first scanner 155. Optionally, in step 860, a user of the table 100 can verify the number of clamshells 205 in the stack 200 by reference to the calibration marking 150. In some embodiments, once the unique identifier on the container 300 has been read in step 870, whenever a stack 200 of clamshells 205 is properly positioned on the table 100, the first scanner 155 reads the traceability code 210 from the top clamshell 205 of the stack 200. In other embodiments, traceability codes 210 are read when a user of the table 100 provides an input to the processing means 175. It will be appreciated that while reading the traceability codes 210 and unique identifiers in steps 860, 870 can be performed with one or more hand-held scanners without employing the table 100, one advantage of the table 100 is that hands are freed by not having to hold a hand-held scanner, thus making the method 800 more time efficient.
In a step 880, the method 800 continues by storing the traceability code 210 read from the top clamshell 205 of the stack 200 in association with the unique identifier read from the container 300. Step 880 can also include storing traceability codes 210 read from each clamshell 205 by the third scanner in association with the unique identifier read from the container 300. In some instances, step 880 further comprises uploading the traceability codes 210 read by the first and third scanners 610, 625 and the unique identifiers read by the second scanner 615 to a host computing system 640. Step 880 can further comprise making the associations that are stored, and the associations can optionally be made by the logic 620 of the table 605, or by the host computing system 640.
After a stack 200 has been read in step 860, the stack 200 can be placed in the container 300 in a step 890. In some embodiments, either the processing means 175 or the host computing system 640 includes association logic, such as programming instructions, configured to associate a unique identifier with the one or more traceability codes 210 read by the first scanner 610 after the unique identifier was read. The association logic, in further embodiments, can be configured to also associate traceability codes 210 read by the third scanner 625 with the unique identifier. In some embodiments, the processing means 175 provides a visual display on the display 180 to show how many stacks 200 of clamshells have been associated with the container 300 and how many further stacks 200 need to be scanned to completely fill the container 300.
By having the association between containers 300 and the stacks 200 of clamshells therein, a container 300 of labeled clamshells can be scanned in a produce field, for example, and all of the traceability codes of the labeled clamshells in the container 300 can then be further associated with harvest event data such the location of the field, the date, and so forth. Accordingly, in some embodiments method 800 further comprises the optional steps of reading a unique identifier from a container 300, and associating harvest event data with that unique identifier.
Computing systems, computing means, and logic described herein can be configured to perform method step described herein, for example, through the use of hardware, such as application-specific integrated circuits (ASICs), specifically designed to perform the particular functions of the method. Computing systems, computing means, and logic described herein can also be configured to perform method step described herein, for example, through the use of firmware residing, for instance, in read only memory (ROM) or flash memory, where the firmware is programmed to perform the particular functions of the method. Computing systems, computing means, and logic described herein can further be configured to perform method step described herein, for example, through the use of a processor capable of executing software residing in a memory, for example, in random access memory (RAM), where the computer instructions embodied in the software perform steps of the methods of the invention. Computing systems, computing means, and logic described herein can also comprise any combination of two or more of hardware, firmware, and software.
In the foregoing specification, the invention is described with reference to specific embodiments thereof, but those skilled in the art will recognize that the invention is not limited thereto. Various features and aspects of the above-described invention may be used individually or jointly. Further, the invention can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. It will be recognized that the terms “comprising,” “including,” and “having,” as used herein, are specifically intended to be read as open-ended terms of art.
This application is a divisional application of U.S. patent application Ser. No. 12/501,240 filed on Jul. 10, 2009 which claims the benefit of U.S. Provisional Patent Application No. 61/080,121 filed on Jul. 11, 2008, both entitled “Mobile Table for Implementing Clamshell-to-Case Association,” and both incorporated by reference herein. This application is related to, and incorporates by reference U.S. Provisional Patent Applications No. 60/970,933 filed on Sep. 7, 2007 and titled “Attributing Harvest Information with Unique Identifiers” and No. 61/028,163 filed on Feb. 2, 2008 and titled “Systems and Methods of Associating Individual Packages with Harvest Crates” and U.S. patent application Ser. No. 12/206,156 filed on Sep. 8, 2008 and entitled “Attributing Harvest Information with Unique Identifiers,” now U.S. Pat. No. 7,909,239, and U.S. patent application Ser. No. 12/370,346 filed on Feb. 12, 2009 and entitled “Systems and Methods of Associating Individual Packages with Harvest Crates.”
Number | Name | Date | Kind |
---|---|---|---|
4385482 | Booth | May 1983 | A |
4526404 | Vazquez | Jul 1985 | A |
4544590 | Egan | Oct 1985 | A |
4832204 | Handy et al. | May 1989 | A |
4846504 | MacGregor et al. | Jul 1989 | A |
5271642 | Jahier et al. | Dec 1993 | A |
5343529 | Goldfine et al. | Aug 1994 | A |
5360628 | Butland | Nov 1994 | A |
5361904 | Kapec et al. | Nov 1994 | A |
5478990 | Montanari et al. | Dec 1995 | A |
5486686 | Zydbel, Jr. et al. | Jan 1996 | A |
5561970 | Edie et al. | Oct 1996 | A |
5569317 | Sarada et al. | Oct 1996 | A |
5592561 | Moore | Jan 1997 | A |
5611948 | Hawkins | Mar 1997 | A |
5619416 | Kosarew | Apr 1997 | A |
5668803 | Tymes et al. | Sep 1997 | A |
5695071 | Ross et al. | Dec 1997 | A |
5768384 | Berson | Jun 1998 | A |
5895073 | Moore | Apr 1999 | A |
5917925 | Moore | Jun 1999 | A |
6005960 | Moore | Dec 1999 | A |
6041929 | Brunner et al. | Mar 2000 | A |
6069955 | Coppersmith et al. | May 2000 | A |
6203069 | Outwater et al. | Mar 2001 | B1 |
6211789 | Oldham et al. | Apr 2001 | B1 |
6212638 | Lee et al. | Apr 2001 | B1 |
6226619 | Halperin et al. | May 2001 | B1 |
6231435 | Pilger | May 2001 | B1 |
6246778 | Moore | Jun 2001 | B1 |
6297508 | Barmore et al. | Oct 2001 | B1 |
6308165 | Gilham | Oct 2001 | B1 |
6314337 | Marcum | Nov 2001 | B1 |
6329920 | Morrison et al. | Dec 2001 | B1 |
6342839 | Curkendall et al. | Jan 2002 | B1 |
6346885 | Curkendall | Feb 2002 | B1 |
6349292 | Southerland et al. | Feb 2002 | B1 |
6361079 | Kirkman | Mar 2002 | B1 |
6363483 | Keshav | Mar 2002 | B1 |
6364990 | Grosskopf et al. | Apr 2002 | B1 |
6398106 | Ulvr et al. | Jun 2002 | B1 |
6409082 | Davis et al. | Jun 2002 | B1 |
6428640 | Stevens et al. | Aug 2002 | B1 |
6442276 | Doljack | Aug 2002 | B1 |
6456729 | Moore | Sep 2002 | B1 |
6473739 | Showghi et al. | Oct 2002 | B1 |
6536672 | Outwater | Mar 2003 | B1 |
6547137 | Begelfer et al. | Apr 2003 | B1 |
6591252 | Young | Jul 2003 | B1 |
6612494 | Outwater | Sep 2003 | B1 |
6664897 | Pape et al. | Dec 2003 | B2 |
6680783 | Pierce et al. | Jan 2004 | B1 |
6766324 | Carlson et al. | Jul 2004 | B2 |
6788800 | Carr et al. | Sep 2004 | B1 |
6796504 | Robinson | Sep 2004 | B2 |
6805926 | Cole et al. | Oct 2004 | B2 |
6806478 | Hatfield | Oct 2004 | B1 |
6808574 | Stevens et al. | Oct 2004 | B1 |
6859672 | Roberts et al. | Feb 2005 | B2 |
6991261 | Dronzek, Jr. et al. | Jan 2006 | B2 |
6995675 | Curkendall et al. | Feb 2006 | B2 |
7013286 | Aggarwal et al. | Mar 2006 | B1 |
7040532 | Taylor et al. | May 2006 | B1 |
7043442 | Levy et al. | May 2006 | B2 |
7104450 | Khovaylo | Sep 2006 | B2 |
7137000 | Hohberger et al. | Nov 2006 | B2 |
7207481 | Barenburg et al. | Apr 2007 | B2 |
7211163 | Kennedy | May 2007 | B2 |
7222791 | Heilper et al. | May 2007 | B2 |
7261235 | Barenburg et al. | Aug 2007 | B2 |
7277601 | Zorab et al. | Oct 2007 | B2 |
7283630 | Doljack | Oct 2007 | B1 |
7295114 | Drzaic et al. | Nov 2007 | B1 |
7321310 | Curkendall et al. | Jan 2008 | B2 |
7412461 | Sholl et al. | Aug 2008 | B2 |
7519825 | Geoffrey | Apr 2009 | B2 |
7614546 | Grant et al. | Nov 2009 | B2 |
7686513 | Knoerzer et al. | Mar 2010 | B2 |
7705735 | Pape et al. | Apr 2010 | B2 |
7714729 | Pape et al. | May 2010 | B2 |
7766240 | Grant | Aug 2010 | B1 |
7770783 | Grant et al. | Aug 2010 | B2 |
7810726 | de la Huerga | Oct 2010 | B2 |
7823768 | Grant et al. | Nov 2010 | B2 |
7827058 | Mortimer | Nov 2010 | B2 |
7909239 | Grant et al. | Mar 2011 | B2 |
7992772 | Grant et al. | Aug 2011 | B2 |
8019662 | Lucas | Sep 2011 | B2 |
8152063 | Grant et al. | Apr 2012 | B1 |
8155313 | Grant | Apr 2012 | B2 |
8196827 | Grant | Jun 2012 | B1 |
8210430 | Grant et al. | Jul 2012 | B1 |
20010056359 | Abreu | Dec 2001 | A1 |
20020004767 | Okamoto et al. | Jan 2002 | A1 |
20020131442 | Garg et al. | Sep 2002 | A1 |
20020158765 | Pape et al. | Oct 2002 | A1 |
20020178363 | Ambrogio et al. | Nov 2002 | A1 |
20030019186 | Hakansson | Jan 2003 | A1 |
20030070520 | Gawazawa | Apr 2003 | A1 |
20030080191 | Lubow et al. | May 2003 | A1 |
20030089078 | Christina | May 2003 | A1 |
20030164934 | Nishi et al. | Sep 2003 | A1 |
20030177025 | Curkendall et al. | Sep 2003 | A1 |
20030177095 | Zorab et al. | Sep 2003 | A1 |
20030185948 | Garwood | Oct 2003 | A1 |
20030221108 | Rupp | Nov 2003 | A1 |
20040065053 | Rice et al. | Apr 2004 | A1 |
20040159527 | Williamson | Aug 2004 | A1 |
20040200892 | Curkendall et al. | Oct 2004 | A1 |
20040205343 | Forth et al. | Oct 2004 | A1 |
20040230796 | Lundvall et al. | Nov 2004 | A1 |
20050004682 | Gaddis et al. | Jan 2005 | A1 |
20050038756 | Nagel | Feb 2005 | A1 |
20050097054 | Dillon | May 2005 | A1 |
20050108044 | Koster | May 2005 | A1 |
20050182695 | Lubow et al. | Aug 2005 | A1 |
20050206586 | Capurso et al. | Sep 2005 | A1 |
20050247778 | Roberts | Nov 2005 | A1 |
20050251449 | Pape et al. | Nov 2005 | A1 |
20050288947 | Mallonee et al. | Dec 2005 | A1 |
20060004907 | Pape et al. | Jan 2006 | A1 |
20060022059 | Juds | Feb 2006 | A1 |
20060054682 | de la Huerga et al. | Mar 2006 | A1 |
20060100964 | Wilde et al. | May 2006 | A1 |
20060111845 | Forbis et al. | May 2006 | A1 |
20060161443 | Rollins | Jul 2006 | A1 |
20060180661 | Grant et al. | Aug 2006 | A1 |
20060187048 | Curkendall et al. | Aug 2006 | A1 |
20060259182 | Mantell | Nov 2006 | A1 |
20060260495 | Siedlaczek | Nov 2006 | A1 |
20060289654 | Robinson et al. | Dec 2006 | A1 |
20070001006 | Schuessler et al. | Jan 2007 | A1 |
20070051362 | Sullivan et al. | Mar 2007 | A1 |
20070119954 | Barenburg et al. | May 2007 | A1 |
20070119955 | Barenburg et al. | May 2007 | A1 |
20070170240 | Grant et al. | Jul 2007 | A1 |
20070175974 | Self et al. | Aug 2007 | A1 |
20070203724 | Farmer et al. | Aug 2007 | A1 |
20070203818 | Farmer et al. | Aug 2007 | A1 |
20070205258 | Self et al. | Sep 2007 | A1 |
20070219916 | Lucas | Sep 2007 | A1 |
20080011841 | Self et al. | Jan 2008 | A1 |
20080011843 | Barenburg et al. | Jan 2008 | A1 |
20080030348 | Pape et al. | Feb 2008 | A1 |
20080046263 | Sager et al. | Feb 2008 | A1 |
20080143094 | Goetz | Jun 2008 | A1 |
20080178197 | Pape et al. | Jul 2008 | A1 |
20080215484 | Oldham et al. | Sep 2008 | A1 |
20090065579 | Grant | Mar 2009 | A1 |
20090242631 | Wishnatzki et al. | Oct 2009 | A1 |
20100106660 | Farmer et al. | Apr 2010 | A1 |
20100145730 | Abreu | Jun 2010 | A1 |
20120037697 | Boone et al. | Feb 2012 | A1 |
Number | Date | Country |
---|---|---|
1350265 | May 2002 | CN |
2000011114 | Jan 2000 | JP |
2002140449 | May 2002 | JP |
03007252 | Jan 2003 | WO |
2006084090 | Aug 2006 | WO |
2007140018 | Jun 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20120181334 A1 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
61080121 | Jul 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12501240 | Jul 2009 | US |
Child | 13431983 | US |