US 8,060,304 B2Grant
Marking system and method
Issue Date:2011-11-15
•43 Claims
•9 Drawing Sheets
Abstract
A marking system may hold a container from which markers are dispensed and identify a marker characteristic regarding the markers in the container. The marking system may also receive activation of a trigger, dispense a marker from the container when the trigger is activated, and store the marker characteristic and time data when the trigger is activated.
Metadata
Assignee
- Certusview Technologies, LLC
Inventors
- Steven Nielsen
- Curtis Chambers
- Jeffrey Farr
- Rene Vazquez
Application Information
Application Number:US 11/696,606
Filing Date:2007-04-04
Priority Date:2007-04-04
Art Unit:3663
Classifications
IPC:
G01C21/00
Patent Drawings (9 sheets)
Description
Background
[0001] Underground man-made objects, such as utility lines and pipes (hereinafter “utility lines”), are very susceptible to damage from excavation activities. Local and federal laws require that notification be given to owners of underground utility lines in an area to be excavated before any excavation takes place. The owners of the utility lines typically must locate and mark the location of any underground utility lines.
[0002] The tasks of locating and marking underground utility lines can be performed by either the utility line owner or by third party contractors. A marking tool is typically used to mark the ground, pavement or other surfaces in order to provide a visual indication of the location of underground utilities. Paint is commonly used as the marker, and it is typically applied using a paint marking tool. The color of the paint is typically chosen based on the type of utility line being marked (e.g., red for a power line). However, other types of markers, such as other types of liquids, flags and stakes are also used, and different visual or other characteristics of the marker are used for representing different types of underground utility lines. For example, the color, shape or other characteristic of a flag marker can represent a particular type of underground utility line (e.g., a square shaped flag can be used to mark a power line).
[0003] When paint is used as the marker, a worker marks the location of an underground utility line using a paint marking tool to spray paint on the ground above the utility line. The paint marking tools typically used have a paint canister holder that is adapted to hold a single aerosol can of paint in an axial orientation with respect to the long axis of the aerosol can. The paint marking tool is typically designed to enable a user to walk or stand erect while dispensing the paint.
[0004] When an underground utility line is located, the worker will load a paint can of the appropriate color for the utility line being marked into the paint marking tool. When it is time to mark a different type of utility line, the worker must change the paint can to one of the appropriate color for the new utility line being marked.
Summary
[0005] According to one aspect, a marking system may include a marker dispenser to hold and dispense a marker; a processor to determine at least one characteristic regarding the marker; and a triggering system in communication with the marker dispenser and the processor to trigger the marker dispenser to dispense the marker and the processor to store the at least one characteristic regarding the marker and time data associated with the dispensing of the marker.
[0006] According to another aspect, a marking tool may include a marker dispenser to hold and dispense a marker from a marker container. A tag may be affixed to the marker container, where the tag may store information regarding at least one characteristic of the marker. The marking tool may further include a tag reader to read the information from the tag, a processor to receive the information from the tag reader, and a triggering system to trigger the marker dispenser to dispense the marker from the marker container and the processor to store the information and time data associated with the dispensing of the marker by the marker dispenser.
[0007] According to yet another aspect, a method may include identifying a marker characteristic regarding a marker loaded into a marking tool; receiving activation of a trigger of the marking tool; dispensing the marker when the activation of the trigger is received; and storing the marker characteristic and time data when the activation of the trigger is received.
[0008] According to a further aspect, a system may include means for holding a container from which a marker is dispensed; means for identifying a marker characteristic regarding the marker in the container; means for receiving activation of a trigger; means for dispensing the marker from the container when the trigger is activated; and means for storing the marker characteristic and a timestamp when the trigger is activated.
[0009] According to another aspect, a system may include means for holding a container from which a marker is dispensed; means for identifying a marker characteristic regarding the marker in the container; means for receiving activation of a trigger; means for dispensing the marker from the container when the trigger is activated; and means for increasing a count value when the trigger is activated.
[0010] According to yet another aspect, a marking system may include means for providing a holder for a container from which a marker is dispensed; and means for identifying a marker characteristic regarding the marker in the container only when the container is initially placed into the holder.
Brief Description of the Drawings
[0011] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments described herein and, together with the description, explain these embodiments. In the drawings:
[0012] FIG. 1 is a block diagram of an exemplary marking system;
[0013] FIG. 2 is a diagram of an exemplary marking tool;
[0014] FIG. 3 is a diagram of an exemplary triggering system that may be used in the marking tool of FIG. 2 ;
[0015] FIG. 4 is a diagram of another exemplary marking tool;
[0016] FIG. 5 is a flowchart of an exemplary process for marking an area; and
[0017] FIGS. 6A-6C are diagrams of exemplary entries that can created.
Detailed Description
[0018] The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention.
[0019] FIG. 1 is a block diagram of an exemplary marking system 100. The system 100 may include a communication system 110, an interface 120, a local memory 130, a processor 140, a marker dispenser 150, a triggering system 160 and a tag reader 170. In other implementations, system 100 may include additional or different components.
[0020] The system 100 may be used to dispense markers. In one exemplary application of the system 100, the markers may be used to mark underground utility lines, such as telecommunications (e.g., telephone and/or cable), power, gas, water, or sewer. The marker that is used to mark underground utility lines may include a liquid, such as paint, or objects, such as flags, stakes, etc.
[0021] A user may control the operation of the system 100 via interface 120. In one implementation, interface 120 may include a touch screen interface that can provide various operational controls and status indicators of the system 100, and can allow the user to navigate the controls by touching particular areas of the screen. In another implementation, the interface 120 may include another form of input and/or output, such as, for example, a display for displaying information and a keypad for entering information. In either situation, the interface 120 may provide operational controls to function as the triggering system 160.
[0022] The triggering system 160 may trigger the dispensing of markers and the storing of marking information. The marking information, which will be described in more detail below, may include information regarding a characteristic of the marker(s) being dispensed, time data (e.g., a timestamp and/or elapsed time information), and/or count data (e.g., a number of times that markers were dispensed). In operation, a user may engage a triggering mechanism in the triggering system 160 (explained in more detail below) in order to dispense the markers. When the triggering mechanism is engaged, the triggering system 160 may also initiate storing of the marking information. This may be done by sending a signal to the processor 140, which may cause processor 140 to store the marking information in local memory 130. Alternatively, or additionally, the processor 140 may store the marking information by transmitting the marking information for storage by a device or system external to system 100. In one implementation, marking information may be stored only when a marker is being dispensed by the marker dispenser 150.
[0023] The marker dispenser 150 may hold the markers and may also contain an actuation mechanism (not shown in FIG. 1 ) that causes the markers to be dispensed when the triggering system 160 is activated. As described above, the markers dispensed by the marker dispenser 150 may include a liquid (e.g., paint) or an object (e.g., flags or stakes). Details of the marker dispenser 150 will be discussed in more detail below.
[0024] The system 100 may also include a tag reader 170. In one implementation, tag reader 170 may include a device that can read tags. A “tag,” as the term is used herein, may refer to any item that is capable of storing machine-readable information, such as a barcode, a radio frequency identification (RFID) device, or a near field communication (NFC) device. A tag may be passive, active, or any combination thereof. A passive tag may transmit data in response to signals received from tag reader 170. An active tag may continuously transmit data. Tags can be attached to the markers that are loaded into the marker dispenser 150 and can incorporate data that corresponds to one or more characteristics of the marker (e.g., paint color if the marker is paint). Other examples of marker characteristics include, but are not limited to, the type of marker and a shape of marker. The tag reader 170 may incorporate an antenna (not shown) to read the data from a tag (whether passive, active, or any combination thereof). The data read by the tag reader 170 can then be sent to the processor 140 for a determination of the corresponding characteristic. The corresponding characteristic can then be stored in local memory 130, displayed by the interface 120, and/or transmitted external to system 100.
[0025] Communication system 110 may include an interface for transmitting data to and/or receiving data from one or more external devices and/or systems located either local to or remote from the system 100. Communication system 110 may include any type of interface, such as an interface for communicating via Ethernet, Bluetooth, Wifi, radio frequency (RF), a wide area network (WAN), or another type of network or protocol.
[0026] In one implementation, communication system 110 may send marking information stored in local memory 130 to an external device/system and/or receive information from an external device/system. The marking information may be used by the external device/system to identify a marker dispensed by a user of system 100, identify a time at which the marker was dispensed, and/or determine an amount of the marker used at a particular location.
[0027] System 100, as broadly described herein, may be particularly suited for incorporation into marking tools for marking underground utilities. As discussed above, a marking tool is used to mark the ground, pavement or other surfaces in order to provide a visual indication of the location of underground utilities. The type of marker that may be used includes paint that may be supplied in aerosol canisters that are oriented axially with respect to the long axis of the aerosol canisters. The marking tool enables a user to walk or stand erect while dispensing the markers.
[0028] If system 100 is incorporated into a paint marking tool, a tag may be attached to the paint canisters to identify a characteristic of the paint, such as the color of the paint in the paint canister. The tag reader 170 can read this paint characteristic (e.g., the color information) from the tag when the paint canister is inserted into the marker dispenser 150, and the processor 140 can display the color information read by the tag reader 170 on the interface 120. Alternatively, or additionally, the color information may be provided to the user in other ways. For example, the color information may be audibly provided to the user (e.g., via a generated voice or a series of beeps or honks). The color information may also, or alternatively, be provided to the user visually in a manner other than via interface 120. For example, the color information may be provided on an object worn or carried by the user (e.g., a pair of glasses, a bracelet, a ring, etc. having display capabilities and/or being capable of changing color).
[0029] In one implementation, the processor 140 can estimate how much paint of a particular color has been dispensed. The processor 140 could do this by maintaining a separate timer for each color. The timer for a particular color would increase its count every time the triggering mechanism is activated and that color is mounted in the marker dispenser 150 (which can be determined by reading the tag on the paint canister using the tag reader 170). This information can be useful for managing paint inventory or determining whether the amount of paint used at a particular location is reasonable given the job to be performed at that location.
[0030] A paint marking tool is just one possible application of system 100. System 100 can be applied to any marking system that uses markers that can be affixed with tags. Any marker characteristic that a user would find useful can be stored on the tag that is affixed to the marker.
[0031] FIG. 2 is a diagram of an exemplary marking tool 200. For the description to follow, assume that the marking tool 200 uses paint as the marker. However, it should be appreciated that any other marker, such as another type of liquid, flags, stakes, etc., may be used in other implementations.
[0032] The marking tool 200 may include a housing 220 with an elongated center housing portion 240, a top housing portion 260 and a bottom housing portion 280. The housing 220 may be formed of any at least semi-rigid material, and may be formed of a lightweight material such as aluminum or plastic.
[0033] A paint canister holder 282 may be attached to the bottom housing portion 280. The paint canister holder 282 may include an open-ended tubular structure that is attached to the bottom housing portion 280 by any suitable attachment mechanisms, such as rivets, adhesive, mechanical fasteners or the like. The paint canister holder 282 may be formed of any material such as injection-molded plastic, formed sheet metal or any other appropriate material that may be fabricated into an open tubular configuration or any other configuration that will serve to support a paint canister 284 with the paint canister axis substantially parallel to the housing 220.
[0034] A tag reader 246, which may include a device that can read tags, may be mounted on or located within the housing 220. The tag reader 246 may incorporate an antenna (not shown) that is capable of reading data from a tag. When a tag 286 is attached to a paint canister 284 that incorporates data that corresponds to characteristics of the paint (e.g., paint color), the tag reader 246 may read that data. Other examples of marker characteristics include, but are not limited to, the type of marker and the shape of marker. The data read by the tag reader 246 can then be sent to a processor 268 for a determination of the corresponding characteristic. The corresponding characteristic can then be provided to the user, stored in local memory 270, and/or transmitted external to marking tool 200.
[0035] The tag reader 246 may be mounted anywhere on the housing or on the paint canister holder 282. However, the tag reader 246 does not have to be mounted anywhere on the marking tool 200 itself. For example, the tag reader 246 may be carried by a user. In general, the tag reader 246 may be mounted or located at any location, as long as it can receive data transmitted from the tag 286.
[0036] An actuation mechanism 288 may be attached to the bottom housing portion 280 at a location from which it can actuate the nozzle 290 of the paint canister 284. The actuation mechanism 288 may include a rigid material that depresses the nozzle 290 when actuated. However, any mechanism may be used to actuate the nozzle 290 of the paint canister 284.
[0037] A handle 262 may be provided at the top housing portion 260. The handle 262 may be formed of injection-molded plastic or any other appropriate material, and may be attached to the top housing portion 260 by rivets, adhesive, or any other suitable means. A mechanical trigger 264 may be provided on the top housing portion 260. The mechanical trigger 264 may be located on the handle 262 and attached using any suitable means.
[0038] The display 266 may be provided on the top housing portion 260. The display 266 may include a touch-screen display for displaying information to a user, as well as acting as an input device. The processor 268 and the local memory 270 are located in the housing 220. In one implementation, the processor 268 and local memory 270 may be located in the top housing portion 260 so as to be in close proximity to the display 266 and mechanical trigger 264. In another implementation, the processor 268 and local memory 270 may be located elsewhere within the housing 220.
[0039] A timer 272 may be provided on the top housing portion 260. The timer 272 may include any device that can output time data to some level of accuracy (e.g., accuracy to the minute, the second, the millisecond, etc.). In one implementation, the timer 272 may be capable of generating the time data itself. In this situation, the timer 272 may take the form of a clock. In another implementation, the timer 272 may receive the time data from another device external to marking tool 200. In this situation, the timer 272 may take the form of a receiver. In some situations, it may be beneficial for the timer 272 to be synchronized to another timer. The timer 272 may output time data to the processor 268.
[0040] A wireless communication antenna 242 may be located on the housing 220, and used to transmit data, such as marking information stored in local memory 270, to an external device/system and/or to receive information from an external device/system.
[0041] The marking tool 200 may also include one or more input/output ports 244, such as USB, SCSI, Firewire, Ethernet and/or other ports, for interfacing with other equipment and/or computers.
[0042] In operation, a user operates the marking tool 200 while standing or walking in an upright manner. A user may control the operation of the tool 200 via display 266, a mechanical trigger 264, and/or a wireless or wired (hereinafter “wireless/wired”) interface that may be provided via wireless communication antenna 242 and/or input/output ports 244.
[0043] The various operational controls and status indicators of the tool 200 are displayed on display 266, and the user can also navigate the controls by touching particular areas of the display 266. Although a touch-screen display is one form of the display 266, any other type of display or interface may be used such as, for example, a display for displaying information and a keypad for entering information. The user may use the display 266 to trigger the dispensing of paint and the storing of marking information.
[0044] The mechanical trigger 264 may trigger the dispensing of paint and the storing of marking information. In one implementation, the tool 200 may store the marking information only when paint is being dispensed. This may be accomplished by using a mechanical trigger 264 that, when activated by the user, triggers both the actuation mechanism 288 for the paint canister 284 and the storing of the marking information by the processor 268.
[0045] The mechanical trigger 264 can trigger the actuation mechanism 288 via a mechanical connection between the trigger 264 and the actuation mechanism 288. For example, the actuation mechanism 288 can be a rigid material that is connected to the mechanical trigger 264 via a mechanical linkage (not shown), in which case depressing the mechanical trigger 264 may cause the actuation mechanism to apply pressure to the nozzle 290 of the paint canister 284. However, the mechanical trigger 264 may also, or alternatively, trigger the actuation mechanism 288 via an electronic connection. The electronic connection may be a hardwired connection or a wireless connection. If the connection between the mechanical trigger 264 and the actuation mechanism 288 is an electronic connection, the actuation mechanism 288 may include a mechanism for generating the force necessary to depress the nozzle 290 of the paint canister 284.
[0046] The wireless/wired interface may be capable of capturing signals that reflect a user's intent. For example, the wireless/wired interface may include a microphone that can capture a user's intent by capturing the user's audible commands. Alternatively, the wireless/wired interface may interact with a device that monitors a condition of the user, such as eye movement, brain activity, or heart rate. In either event, the wireless/wired interface may generate signals that may be sent to the processor 268 for processing. The processor 268 may use the signals to trigger the dispensing of paint and the storing of marking information.
[0047] FIG. 3 is a diagram of one embodiment of a triggering system 300 that may be used in the marking tool 200 of FIG. 2 . As shown in FIG. 3 , the triggering system 300 may include the mechanical trigger 264, a wireless/wired trigger 320, and/or a touch screen display 266, the mechanical actuation device 288, and a signal generator 310.
[0048] In operation, a user may trigger the storing of the marking information and the dispensing of paint by activating the mechanical trigger 264. The storing of the marking information and the dispensing of paint may also, or alternatively, be triggered by a trigger signal from wireless/wired trigger 320 or by choosing a command that is displayed on the touch screen display 266. It should be appreciated that triggering system 300 may include a mechanical trigger 264, a trigger signal from wireless/wired trigger 320, a trigger command on a touch screen display 266, or a combination of a mechanical trigger 264, a trigger signal from wireless/wired trigger 320, and/or a trigger command on a touch screen display 266 for initiating the storing of the marking information and the dispensing of paint.
[0049] When a user activates the mechanical trigger 264, the mechanical actuation device 288 and the signal generator 310 are both activated. The mechanical actuation device 288 actuates the nozzle 290 of the paint canister 284, thus dispensing paint out of the paint canister 284. The signal generator 310, when activated, sends a signal to the processor 268 indicating that the mechanical trigger is being activated. As discussed above, this signal could be used to trigger the storing of marking information and/or a timer for keeping track of how much paint of a particular color has been dispensed when a tag 286 that identifies the paint color is attached to the paint canister 284 that is mounted in the paint canister holder 282.
[0050] The mechanical trigger 264 can activate the mechanical actuation device 288 via a mechanical connection, e.g., a mechanical linkage, between the mechanical trigger 264 and the mechanical actuation device 288. Alternatively, the mechanical trigger 264 can activate the mechanical actuation device 288 via a wired or wireless electronic connection between the mechanical trigger 264 and the mechanical actuation device 288.
[0051] If a trigger signal from wireless/wired trigger 320 is used by the user to initiate marking information storing and paint dispersal, the wireless/wired trigger 320 may send a signal to both the mechanical actuation device 288 and the processor 268. The signal sent to the mechanical actuation device 288 by the wireless/wired trigger 320 may result in the actuation of the nozzle 290 of the paint canister 284 by the mechanical actuation device 288. The signal sent to the processor 268 by the wireless/wired trigger 320 may trigger the storing of the marking information. The signals sent by the wireless/wired trigger 320 to the mechanical actuation device 288 and the processor 268 may be sent via a wired or wireless connection.
[0052] If a command on the touch screen display 266 is used by the user to initiate storing of marking information and paint dispersal, the touch screen display 266 can send a signal to both the mechanical actuation device 288 and the processor 268. The signal sent to the mechanical actuation device 288 by the touch screen display 266 may result in the actuation of the nozzle 290 of the paint canister 284 by the mechanical actuation device 288. The signal sent to the processor 268 by the touch screen display 266 may trigger the storing of the marking information. The signals sent by the touch screen display 266 to the mechanical actuation device 288 and the processor 268 may be sent via a wired or wireless connection.
[0053] The marking information may be used by an external device and/or system to identify which markers were dispensed, when the markers were dispensed, and/or an amount of markers that were dispensed. The marking information may be useful to determine whether a user dispensed the correct marker(s) (e.g., the correct color paint) in a particular location. Also, the marking information may be used to visually depict (e.g., in real time as the dispensing occurs) or reconstruct (e.g., at a later time after the dispensing is complete) the dispensing of the markers on an electronic representation of the area that is currently being marked or was previously marked. Also, the marking information may be used to determine whether the job was completed correctly (e.g., that the amount of paint dispensed at the location was reasonable given the job that was to be performed at the location).
[0054] As shown in FIG. 4 , the marking system 100 may be incorporated into already existing marking tools by locating the electronics on a board 410 that can be mounted onto an existing marking tool 400. The processor 268, local memory 270, input/output ports 244, tag reader 246 and/or wireless communication antenna 242 may be mounted on the board 410. The board 410 can be attached to the marking tool 400 using any means, such as with fasteners, clamps, glue, etc.
[0055] FIG. 5 is a flowchart of an exemplary process for marking an area. The process of FIG. 5 may begin with a user of a marking tool, such as marking tool 200 (FIG. 2 ), being dispatched to a location to be marked. The user might be given a ticket that identifies what utilities the user needs to mark at the location. The ticket might specify, for example, the location to be marked, the day and/or time that the location is to be marked, and/or whether the user is to mark the location for telecommunications (e.g., telephone and/or cable), power, gas, water, and/or sewer. The user might arrive at the location and take his/her marking tool out of his/her vehicle. In some situations, the user might load his/her pockets with extra markers (e.g., extra canisters of the same color of paint or different colors of paint).
[0056] A marker may be loaded into the marking tool (block 510). For example, the user may load a paint canister 284 of the appropriate color into paint canister holder 282. If the user is going to mark power, for example, the user might load a paint canister 284 containing red paint. The paint canister 284 may be loaded such that nozzle 290 extends out of the bottom of the marking tool 200, as illustrated in FIG. 2 .
[0057] In one implementation, as described above, a tag 286 may be affixed to the paint canister 284. The tag 286 may store information regarding one or more characteristics of the marker. For example, the tag 286 may identify the type of marker (e.g., paint, flag, stake, etc.), the color of marker (e.g., orange, red, yellow, blue, or green), and/or the shape of the marker (e.g., square, triangular, circular, etc.).
[0058] The marker characteristic(s) may be identified (block 520). In one implementation, the marker characteristic(s) may be automatically determined. For example, data from the tag 286 may be read by tag reader 246 and sent to processor 268. The processor 268 may determine the marker characteristic(s) from this data, and cause information regarding the marker characteristic(s) to be presented to the user (e.g., visually and/or audibly).
[0059] For example, a user interface may identify a characteristic of the marker. The user interface may optionally request the user to confirm that the user intended to load a marker with the identified characteristic. The confirmation may establish that the user actually looked at the user interface before performing any marking operation. In one implementation, the user may be unable to activate a trigger for dispensing a marker if the user does not confirm that the correct marker is loaded.
[0060] In another implementation, the marker characteristic(s) may be manually determined. For example, the user may specify the marker characteristic(s) via a user interface. The user interface may identify a number of possible characteristics (e.g., paint colors) of the marker. In this case, the user interface may request that that user select the paint color to be dispensed. The user interface may also identify the utility that corresponds to each of the possible paint colors so that the user can confirm that the correct marker is loaded.
[0061] Trigger activation may be received (block 530). For example, the user may effect trigger activation by applying pressure to the mechanical trigger 264 with his/her hand. Alternatively, or additionally, the user may effect trigger activation by, for example, speaking a particular command to cause a trigger signal to be output by wireless/wired trigger 320. Alternatively, or additionally, the user may effect trigger activation by touching a particular area of display 266 to cause a trigger command to be output by display 266.
[0062] It may optionally be determined whether to permit trigger activation (block 540). For example, the user may be required to confirm that a marker with the correct marker characteristic was loaded before trigger activation may be permitted. Alternatively, the marking tool 200 may be loaded with information from the user's ticket. In this case, trigger activation may be prevented when the marker characteristic of the marker does not match the ticket information. For example, if the ticket information indicates that the user is to dispense blue and yellow paint at a particular location, then activation of the trigger may be permitted if blue or yellow paint is loaded into the marking tool 200, and activation of the trigger may be prevented otherwise.
[0063] If activation of the trigger is permitted, then a marker may be dispensed (block 550), and marking information may be stored (block 560). To dispense a marker (block 550), the actuation device 288 may be activated to cause the nozzle 290 of the paint canister 284 to be depressed, which may cause paint from the paint canister 284 to be output via the nozzle 290.
[0064] To store marking information (block 560), a signal may be sent to the processor 268. The signal may be sent from the signal generator 310, the wireless/wired trigger 320, and/or the display 266, as described above. The signal may instruct the processor 268 to store the marking information. For example, the processor 268 may store the marking information in local memory 270. In this case, the processor 268 may create an entry in local memory 270. Alternatively, or additionally, the processor 268 may store the marking information by transmitting the marking information for storage by a device or system external to marking tool 200.
[0065] FIG. 6A is a diagram of an exemplary entry that may be created. As shown in FIG. 6A , an entry may include a marker characteristic(s) field 610 and a timestamp field 620. The marker characteristic(s) field 610 may include information regarding one or more marker characteristics, such as marker color, marker shape, or marker type. The information in the marker characteristic(s) field 610 is shown in FIG. 6A as “yellow” or “yellow paint”—although any type of descriptive information may be used. The timestamp field 620 may include time data that identifies the day and/or time that the marker was dispensed. The time data in the timestamp field 620 is shown in FIG. 6A as 10:45 a.m. on Oct. 20, 2005—although any type of date and/or time code may be used. As explained above, the marking information may be useful to determine whether the user dispensed the correct marker(s) (e.g., the correct color paint) in a particular location. For example, the user's ticket may identify what utility lines were to be marked in the area. The marking information may help insure that the job was completed correctly.
[0066] FIG. 6B is a diagram of another exemplary entry that may be created. As shown in FIG. 6B , an entry may include a marker characteristic(s) field 610, a timestamp field 620, and a count field 630. The marker characteristic(s) field 610 and the timestamp field 620 may be similar to the similarly named fields in FIG. 6A . The count field 630 may include information that identifies the number of times that the user activated the trigger to dispense a marker (e.g., yellow paint). The information in the count field 630 is shown in FIG. 6B as twenty-three—although any count value can be used. The information in the count field 630 may be useful to determine or estimate an amount of paint that was dispensed at the location and, thus, whether the amount of paint was reasonable given the job that was to be performed.
[0067] FIG. 6C is a diagram of another exemplary entry that may be created. As shown in FIG. 6C , an entry may include a marker characteristic(s) field 640, a timestamp field 620, and an elapsed time field 650. The marker characteristic(s) field 640 and the timestamp field 620 may be similar to the similarly named fields in FIG. 6A . In this case, however, the marker characteristic(s) field 640 may additionally store an identifier that identifies a particular marker (e.g., a particular canister of paint). The identifier is shown in FIG. 6C as “12345”—although any type of identifier may be used.
[0068] The elapsed time field 650 may include information that identifies the amount of time that has elapsed from when the user activated the trigger for dispensing a marker (e.g., yellow paint) to when the user ceased activating the trigger. The information in the elapsed time field 650 is shown in FIG. 6C as three minutes, forty five seconds, and three one hundredths of a second—although any time code can be used. The information in the elapsed time field 650 may be useful to determine or estimate when a supply of markers is nearly empty. The information in the elapsed time field 650 may help determine when to replace the canister. The elapsed time or a signal indicating that a supply of markers needs to be replaced may be presented to the user visually and/or audibly. The information in the elapsed time field 650 may also, or alternatively, be useful to determine or estimate an amount of markers used in a particular location.
[0069] While three exemplary entries have been described with regard to FIGS. 6A-6C , an entry may include more, fewer, different, or combinations of the fields shown in FIGS. 6A-6C .
[0070] The foregoing description is not intended to be exhaustive or to limit the description to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the invention.
[0071] For example, the processors 140 and 268 can be general purpose computers. Alternatively, they can be special purpose computers, programmed microprocessors or microcontrollers and peripheral integrated circuit elements, ASICs or other integrated circuits, hardwired electronic or logic circuits such as discrete element circuits, programmable logic devices such as FPGA, PLD, PLA or PAL or the like. In general, any device capable of executing code can be used to implement processors 140 and 268. Local memories 130 and 270 can be implemented with any type of electronic memory and/or storage device using any type of media, such as magnetic, optical or other media.
[0072] Further, while a series of blocks have been illustrated in FIG. 5 , the order of the blocks may differ in other implementations. Also, non-dependent blocks may be performed in parallel.
[0073] Also, it has been described that information regarding an elapsed time can be used to determine or estimate when a supply of markers is nearly empty. In another implementation, a sensor may be used to detect a weight of a paint canister 284. The sensor may be placed on the paint canister 284 or within the paint canister holder 282. The weight of the paint canister 284 may be used to estimate how full or empty the paint canister 284 is. This information may be provided to an operator of the marking tool 200 visually and/or audibly. In one implementation, replacing the paint canister 284 may trigger the identification of the marker characteristic (e.g., paint color) by the tag reader 246. This may help reduce the overall battery life of the tag reader 246 and/or the tag 286 by limiting the number of times that the tag reader 246 is used (e.g., only obtain the marker characteristic when the paint canister 284 is initially loaded into paint canister holder 282).
[0074] It will be apparent that aspects, as described above, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these aspects is not limiting of the description provided herein. Thus, the operation and behavior of the aspects were described without reference to the specific software code—it being understood that software and control hardware can be designed to implement the aspects based on the description herein.
[0075] No element, act, or instruction used in the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A marking system, comprising:
a marker dispenser to hold and dispense at least one marker;
a processor to record at least one characteristic of the dispensed marker; and
a triggering system in communication with the marker dispenser and the processor to trigger the marker dispenser to dispense the marker and the processor to store the at least one characteristic regarding the marker and time data associated with the dispensing of the marker,
wherein a tag is associated with the marker, the tag storing the at least one characteristic; and
wherein the system further comprises:
a tag reader to read the at least one characteristic from the tag, and
wherein the at least one characteristic comprises a type of the dispensed marker, a color of the dispensed marker, or a shape of the dispensed marker.
2. The system of claim 1, wherein the tag is affixed to a container that holds the marker.
3. The system of claim 1, wherein the tag is a radio frequency identification (RFID) tag and the tag reader is an RFID reader.
4. The system of claim 1, wherein the processor is further configured to present the at least one characteristic on a user interface.
5. The system of claim 4, wherein the user interface is configured to identify the at least one characteristic and a type of utility line to which the at least one characteristic corresponds.
6. The system of claim 4, wherein the user interface is configured to request confirmation that the at least one characteristic is correct before the triggering system can trigger the marker dispenser or the processor.
7. The system of claim 1, further comprising:
a user interface to:
present a number of possible marker characteristics, and
receive selection of at least one of the possible marker characteristics as the at least one characteristic.
8. The system of claim 1, wherein the marker dispenser comprises:
a paint canister holder adapted to support a paint canister, and
an actuation mechanism to dispense paint from the paint canister when the triggering system is activated.
9. The system of claim 1, wherein the triggering system comprises:
a trigger,
an actuation mechanism to cause a marker container to dispense the marker when the trigger is activated, and
a signal generator to send a signal to the processor when the trigger is activated.
10. The system of claim 9, wherein the marker container comprises an aerosol canister and the actuation mechanism comprises a rigid material that applies pressure to a nozzle on the aerosol canister when the trigger is activated.
11. The system of claim 9, wherein a decision of whether the trigger is permitted to be activated is based on the at least one characteristic.
12. The system of claim 11, wherein the decision is based on a comparison of the at least one characteristic to information from a ticket.
13. The system of claim 11, wherein the decision is based on a confirmation that the at least one characteristic is correct.
14. The system of claim 1, wherein the time data indicates when the marker was dispensed or an amount of time that the marker was dispensed.
15. A marking system, comprising:
a marker dispenser to hold and dispense at least one marker;
a processor to record at least one characteristic of the dispensed marker; and
a triggering system in communication with the marker dispenser and the processor to trigger the marker dispenser to dispense the marker and the processor to store the at least one characteristic regarding the marker and time data associated with the dispensing of the marker,
wherein triggering system is configured to:
receive a trigger activation, and
cause the processor to increase a count value in response to the trigger activation.
16. A marking tool, comprising:
a marker dispenser to hold and dispense a marker from a marker container, a tag being affixed to the marker container, the tag storing information regarding at least one characteristic of the marker;
a tag reader to read the information from the tag;
a processor to receive the information from the tag reader; and
a triggering system to trigger the marker dispenser to dispense the marker from the marker container and the processor to store the information and time data associated with the dispensing of the marker by the marker dispenser.
17. The tool of claim 16, wherein the tag is a radio frequency identification (RFID) tag and the tag reader is an RFID reader.
18. The tool of claim 16, wherein the at least one characteristic comprises a type of the marker, a color of the marker, or a shape of the marker.
19. The tool of claim 16, wherein the processor is further configured to present the information on a user interface.
20. The tool of claim 19, wherein the user interface is configured to identify the at least one characteristic and a type of utility line to which the at least one characteristic corresponds.
21. The tool of claim 19, wherein the user interface is configured to request confirmation that the at least one characteristic is correct before the triggering system can trigger the marker dispenser or the processor.
22. The tool of claim 16, wherein the marker dispenser comprises:
a paint canister holder adapted to support a paint canister, and
an actuation mechanism to dispense paint from the paint canister when the triggering system is activated.
23. The tool of claim 16, wherein the triggering system comprises:
a trigger,
an actuation mechanism to cause the marker container to dispense the marker when the trigger is activated, and
a signal generator to send a signal to the processor when the trigger is activated.
24. The tool of claim 23, wherein the marker container comprises an aerosol canister and the actuation mechanism comprises a rigid material that applies pressure to a nozzle on the aerosol canister when the trigger is activated.
25. The tool of claim 23, wherein a decision of whether the trigger is permitted to be activated is based on the at least one characteristic.
26. The tool of claim 25, wherein the decision is based on a comparison of the at least one characteristic to information from a ticket.
27. The tool of claim 25, wherein the decision is based on a confirmation that the at least one characteristic is correct.
28. The tool of claim 16, wherein the time data indicates when the marker was dispensed or an amount of time that the marker was dispensed.
29. The tool of claim 26, wherein the triggering system is further configured to:
receive a trigger activation, and
cause the processor to increase a count value based on the received trigger activation.
31. The tool of claim 30, wherein information regarding the weight of the marker container is provided to a user of the tool.
32. A method, comprising:
identifying a marker characteristic regarding a marker loaded into a marking tool;
receiving activation of a trigger of the marking tool;
dispensing the marker when the activation of the trigger is received; and
storing the marker characteristic and time data when the activation of the trigger is received,
wherein a tag is associated with the marker, the tag storing the marker characteristic; and
wherein identifying the marker characteristic includes:
reading the marker characteristic from the tag.
33. The method of claim 32, wherein the tag is a radio frequency identification (RFID) tag.
34. The method of claim 32, wherein the marker characteristic comprises a type of the marker, a color of the marker, or a shape of the marker.
35. The method of claim 32, wherein identifying the marker characteristic includes:
presenting a number of possible marker characteristics on a user interface, and
receiving selection of one of the possible marker characteristics as the marker characteristic.
36. The method of claim 32, further comprising:
determining whether to permit the trigger to be activated based on the marker characteristic.
37. The method of claim 36, wherein the determination is based on a comparison of the marker characteristic to information from a ticket.
38. The method of claim 37, wherein the determination is based on a confirmation that the marker characteristic is correct.
39. The method of claim 32, further comprising:
increasing a count value when the activation of the trigger is received.
40. The method of claim 32, further comprising:
presenting information regarding the marker characteristic audibly or visually.
41. The system of claim 1, further comprising:
a communication system to send to an external device the at least one characteristic regarding the marker and the time data associated with the dispensing of the marker.
42. The marking tool of claim 16, further comprising:
a communication system to send to an external device the information and the time data associated with the dispensing of the marker by the marker dispenser.
43. The method of claim 32, further comprising:
sending the marker characteristic and the time data to an external device.
Patent Citations (347)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3871557(A) | 1975-03-01 | Smrt | Applicant |
| US3972038(A) | 1976-07-01 | Fletcher et al. | Applicant |
| US3974491(A) | 1976-08-01 | Sipe | Applicant |
| US3988922(A) | 1976-11-01 | Clark et al. | Applicant |
| US4258320(A) | 1981-03-01 | Schonstedt | Applicant |
| US4387340(A) | 1983-06-01 | Peterman | Applicant |
| US4388592(A) | 1983-06-01 | Schonstedt | Applicant |
| US4520317(A) | 1985-05-01 | Peterman | Applicant |
| US4536710(A) | 1985-08-01 | Dunham | Applicant |
| US4539522(A) | 1985-09-01 | Schonstedt | Applicant |
| US4590425(A) | 1986-05-01 | Schonstedt | Applicant |
| US4639674(A) | 1987-01-01 | Rippingale | Applicant |
| US4712094(A) | 1987-12-01 | Bolson, Sr. | Applicant |
| US4747207(A) | 1988-05-01 | Schonstedt et al. | Applicant |
| US4803773(A) | 1989-02-01 | Schonstedt | Applicant |
| US4818944(A) | 1989-04-01 | Rippingale | Applicant |
| US4839623(A) | 1989-06-01 | Schonstedt et al. | Applicant |
| US4839624(A) | 1989-06-01 | Schonstedt | Applicant |
| US4873533(A) | 1989-10-01 | Oike | Applicant |
| US5001430(A) | 1991-03-01 | Peterman et al. | Applicant |
| US5006806(A) | 1991-04-01 | Rippingale et al. | Applicant |
| US5014008(A) | 1991-05-01 | Flowerdew | Applicant |
| US5017873(A) | 1991-05-01 | Rippingale et al. | Applicant |
| US5025150(A) | 1991-06-01 | Oldham et al. | Applicant |
| US5043666(A) | 1991-08-01 | Tavernetti et al. | Applicant |
| US5045368(A) | 1991-09-01 | Cosman et al. | Applicant |
| US5065098(A) | 1991-11-01 | Salsman et al. | Applicant |
| US5093622(A) | 1992-03-01 | Balkman | Applicant |
| US5097211(A) | 1992-03-01 | Schonstedt | Applicant |
| US5114517(A) | 1992-05-01 | Rippingale et al. | Applicant |
| US5122750(A) | 1992-06-01 | Rippingale et al. | Applicant |
| US5136245(A) | 1992-08-01 | Schonstedt | Applicant |
| US5138761(A) | 1992-08-01 | Schonstedt | Applicant |
| US5173139(A) | 1992-12-01 | Rippingale et al. | Applicant |
| US5206065(A) | 1993-04-01 | Rippingale et al. | Applicant |
| US5214757(A) | 1993-05-01 | Mauney et al. | Applicant |
| US5231355(A) | 1993-07-01 | Rider et al. | Applicant |
| US5239290(A) | 1993-08-01 | Schonstedt | Applicant |
| US5260659(A) | 1993-11-01 | Flowerdew et al. | Applicant |
| US5264795(A) | 1993-11-01 | Rider | Applicant |
| US5361029(A) | 1994-11-01 | Rider et al. | Applicant |
| US5365163(A) | 1994-11-01 | Satterwhite et al. | Applicant |
| US5373298(A) | 1994-12-01 | Karouby | Applicant |
| US5430379(A) | 1995-07-01 | Parkinson et al. | Applicant |
| US5444364(A) | 1995-08-01 | Satterwhite et al. | Applicant |
| US5471143(A) | 1995-11-01 | Doany | Applicant |
| US5519329(A) | 1996-05-01 | Satterwhite | Applicant |
| US5530357(A) | 1996-06-01 | Cosman et al. | Applicant |
| US5543931(A) | 1996-08-01 | Lee et al. | Applicant |
| US5568162(A) | 1996-10-01 | Samsel et al. | Applicant |
| US5576973(A) | 1996-11-01 | Haddy | Applicant |
| US5621325(A) | 1997-04-01 | Draper et al. | Applicant |
| US5629626(A) | 1997-05-01 | Russell et al. | Applicant |
| US5644237(A) | 1997-07-01 | Eslambolchi et al. | Applicant |
| US5739785(A) | 1998-04-01 | Allison et al. | Applicant |
| US5751289(A) | 1998-05-01 | Myers | Applicant |
| US5764127(A) | 1998-06-01 | Hore et al. | Applicant |
| US5769370(A) | 1998-06-01 | Ashjaee | Applicant |
| US5828219(A) | 1998-10-01 | Hanlon et al. | Applicant |
| US5916300(A) | 1999-06-01 | Kirk et al. | Applicant |
| US5917325(A) | 1999-06-01 | Smith | Applicant |
| US5920194(A) | 1999-07-01 | Lewis et al. | Applicant |
| US5955667(A) | 1999-09-01 | Fyfe | Applicant |
| US6026135(A) | 2000-02-01 | McFee et al. | Applicant |
| US6031454(A) | 2000-02-01 | Lovejoy et al. | Applicant |
| US6032530(A) | 2000-03-01 | Hock | Applicant |
| US6037010(A) | 2000-03-01 | Kahmann et al. | Applicant |
| US6053260(A) | 2000-04-01 | Boon | Applicant |
| US6061632(A) | 2000-05-01 | Dreier | Applicant |
| US6064940(A) | 2000-05-01 | Rodgers | Applicant |
| US6074693(A) | 2000-06-01 | Manning | Examiner |
| US6107801(A) | 2000-08-01 | Hopwood | Applicant |
| US6127827(A) | 2000-10-01 | Lewis | Applicant |
| US6130539(A) | 2000-10-01 | Polak | Applicant |
| US6138906(A) | 2000-10-01 | DeMayo | Applicant |
| US6140819(A) | 2000-10-01 | Peterman et al. | Applicant |
| US6169958(B1) | 2001-01-01 | Nagasamy et al. | Applicant |
| US6188777(B1) | 2001-02-01 | Darrell et al. | Applicant |
| US6206282(B1) | 2001-03-01 | Hayes, Sr. et al. | Applicant |
| US6234218(B1) | 2001-05-01 | Boers | Applicant |
| US6268731(B1) | 2001-07-01 | Hopwood et al. | Applicant |
| US6292108(B1) | 2001-09-01 | Straser et al. | Applicant |
| US6297736(B1) | 2001-10-01 | Lewis et al. | Applicant |
| US6299934(B1) | 2001-10-01 | Manning | Applicant |
| US6308565(B1) | 2001-10-01 | French et al. | Applicant |
| USRE37574(E) | 2002-03-01 | Rawlins | Examiner |
| US6356082(B1) | 2002-03-01 | Alkire et al. | Applicant |
| US6363320(B1) | 2002-03-01 | Chou | Applicant |
| US6375038(B1) | 2002-04-01 | Daansen et al. | Applicant |
| US6378220(B1) | 2002-04-01 | Baioff et al. | Applicant |
| US6390336(B1) | 2002-05-01 | Orozco | Applicant |
| US6407550(B1) | 2002-06-01 | Parakulam et al. | Applicant |
| US6411094(B1) | 2002-06-01 | Gard et al. | Applicant |
| US6437708(B1) | 2002-08-01 | Brouwer | Applicant |
| US6438239(B1) | 2002-08-01 | Kuechen | Applicant |
| US6459266(B1) | 2002-10-01 | Fling | Applicant |
| US6476708(B1) | 2002-11-01 | Johnson | Applicant |
| US6490524(B1) | 2002-12-01 | White et al. | Applicant |
| US6512478(B1) | 2003-01-01 | Chien | Examiner |
| US6549011(B2) | 2003-04-01 | Flatt | Applicant |
| US6552548(B1) | 2003-04-01 | Lewis et al. | Applicant |
| US6585133(B1) | 2003-07-01 | Brouwer | Applicant |
| US6600420(B2) | 2003-07-01 | Goff et al. | Applicant |
| US6617856(B1) | 2003-09-01 | Royle et al. | Applicant |
| US6633163(B2) | 2003-10-01 | Fling | Applicant |
| US6650798(B2) | 2003-11-01 | Russell et al. | Applicant |
| US6674276(B2) | 2004-01-01 | Morgan et al. | Applicant |
| US6710741(B2) | 2004-03-01 | Tucker | Applicant |
| US6717392(B2) | 2004-04-01 | Pearson | Applicant |
| US6723375(B2) | 2004-04-01 | Zeck et al. | Applicant |
| US6728662(B2) | 2004-04-01 | Frost et al. | Applicant |
| US6751554(B1) | 2004-06-01 | Asher et al. | Applicant |
| US6777923(B2) | 2004-08-01 | Pearson | Applicant |
| US6778128(B2) | 2004-08-01 | Tucker et al. | Applicant |
| US6798379(B2) | 2004-09-01 | Tucker et al. | Applicant |
| US6799116(B2) | 2004-09-01 | Robbins | Applicant |
| US6815953(B1) | 2004-11-01 | Bigelow | Applicant |
| US6819109(B2) | 2004-11-01 | Sowers et al. | Applicant |
| US6825775(B2) | 2004-11-01 | Fling et al. | Applicant |
| US6825793(B2) | 2004-11-01 | Taylor, Jr. et al. | Applicant |
| US6833811(B2) | 2004-12-01 | Zeitfuss et al. | Applicant |
| US6836231(B2) | 2004-12-01 | Pearson | Applicant |
| US6845171(B2) | 2005-01-01 | Shum et al. | Applicant |
| US6850161(B1) | 2005-02-01 | Elliott et al. | Applicant |
| US6850843(B2) | 2005-02-01 | Smith et al. | Applicant |
| US6853303(B2) | 2005-02-01 | Chen et al. | Applicant |
| US6865484(B2) | 2005-03-01 | Miyasaka et al. | Applicant |
| US6898550(B1) | 2005-05-01 | Blackadar et al. | Applicant |
| US6904361(B1) | 2005-06-01 | Tallman et al. | Applicant |
| US6947028(B2) | 2005-09-01 | Shkolnikov | Applicant |
| US6954071(B2) | 2005-10-01 | Flatt et al. | Applicant |
| US6956524(B2) | 2005-10-01 | Tucker et al. | Applicant |
| US6958690(B1) | 2005-10-01 | Asher et al. | Applicant |
| US6968296(B2) | 2005-11-01 | Royle | Applicant |
| US6975942(B2) | 2005-12-01 | Young et al. | Applicant |
| US6977508(B2) | 2005-12-01 | Pearson et al. | Applicant |
| US6992584(B2) | 2006-01-01 | Dooley et al. | Applicant |
| US6993088(B2) | 2006-01-01 | Fling et al. | Applicant |
| US7009519(B2) | 2006-03-01 | Leonard et al. | Applicant |
| US7038454(B2) | 2006-05-01 | Gard et al. | Applicant |
| US7042358(B2) | 2006-05-01 | Moore | Applicant |
| US7053789(B2) | 2006-05-01 | Fling et al. | Applicant |
| US7057383(B2) | 2006-06-01 | Schlapp et al. | Applicant |
| US7062414(B2) | 2006-06-01 | Waite et al. | Applicant |
| US7079591(B2) | 2006-07-01 | Fling et al. | Applicant |
| US7091872(B1) | 2006-08-01 | Bigelow et al. | Applicant |
| US7113124(B2) | 2006-09-01 | Waite | Applicant |
| US7116244(B2) | 2006-10-01 | Fling et al. | Applicant |
| US7120564(B2) | 2006-10-01 | Pacey | Applicant |
| US7235980(B2) | 2007-06-01 | Pearson et al. | Applicant |
| US7285958(B2) | 2007-10-01 | Overby et al. | Applicant |
| US7304480(B1) | 2007-12-01 | Pearson | Applicant |
| US7310584(B2) | 2007-12-01 | Royle | Applicant |
| US7319387(B2) | 2008-01-01 | Willson et al. | Applicant |
| US7331340(B2) | 2008-02-01 | Barney | Applicant |
| US7336078(B1) | 2008-02-01 | Merewether et al. | Applicant |
| US7339379(B2) | 2008-03-01 | Thompson et al. | Applicant |
| US7342537(B2) | 2008-03-01 | Pearson et al. | Applicant |
| US7356421(B2) | 2008-04-01 | Gudmundsson et al. | Applicant |
| US7358738(B2) | 2008-04-01 | Overby et al. | Applicant |
| US7372247(B1) | 2008-05-01 | Giusti et al. | Applicant |
| US7372276(B2) | 2008-05-01 | Mulcahey | Applicant |
| US7396177(B2) | 2008-07-01 | Lapstun et al. | Applicant |
| US7396178(B2) | 2008-07-01 | Lapstun et al. | Applicant |
| US7403012(B2) | 2008-07-01 | Worsley et al. | Applicant |
| US7413363(B2) | 2008-08-01 | Lapstun et al. | Applicant |
| US7482973(B2) | 2009-01-01 | Tucker et al. | Applicant |
| US7500583(B1) | 2009-03-01 | Cox | Applicant |
| US7640105(B2) | 2009-12-01 | Nielsen et al. | Applicant |
| US2001/0029996(A1) | 2001-10-01 | Robinson | Applicant |
| US2002/0053608(A1) | 2002-05-01 | Zeck et al. | Applicant |
| US2002/0115472(A1) | 2002-08-01 | Andress | Applicant |
| US2002/0130806(A1) | 2002-09-01 | Taylor et al. | Applicant |
| US2003/0080897(A1) | 2003-05-01 | Tranchina | Applicant |
| US2003/0184300(A1) | 2003-10-01 | Bigelow | Applicant |
| US2003/0196585(A1) | 2003-10-01 | McDonald et al. | Applicant |
| US2004/0051368(A1) | 2004-03-01 | Caputo et al. | Applicant |
| US2004/0057795(A1) | 2004-03-01 | Mayfield et al. | Applicant |
| US2004/0168358(A1) | 2004-09-01 | Stump | Applicant |
| US2004/0220731(A1) | 2004-11-01 | Tucker et al. | Applicant |
| US2005/0023367(A1) | 2005-02-01 | Reighard | Applicant |
| US2005/0040222(A1) | 2005-02-01 | Robinson | Applicant |
| US2005/0055142(A1) | 2005-03-01 | McMurtry et al. | Applicant |
| US2005/0057745(A1) | 2005-03-01 | Bontje | Applicant |
| US2005/0150399(A1) | 2005-07-01 | Wiley | Examiner |
| US2005/0192727(A1) | 2005-09-01 | Shostak et al. | Applicant |
| US2005/0278371(A1) | 2005-12-01 | Funk et al. | Applicant |
| US2006/0026020(A1) | 2006-02-01 | Waite et al. | Applicant |
| US2006/0055584(A1) | 2006-03-01 | Waite et al. | Applicant |
| US2006/0077095(A1) | 2006-04-01 | Tucker et al. | Applicant |
| US2006/0109131(A1) | 2006-05-01 | Sen et al. | Applicant |
| US2006/0169776(A1) | 2006-08-01 | Hornbaker et al. | Examiner |
| US2006/0220955(A1) | 2006-10-01 | Hamilton | Applicant |
| US2006/0244454(A1) | 2006-11-01 | Gard et al. | Applicant |
| US2006/0254820(A1) | 2006-11-01 | Cole et al. | Applicant |
| US2006/0276198(A1) | 2006-12-01 | Michelon et al. | Applicant |
| US2006/0282280(A1) | 2006-12-01 | Stotz et al. | Applicant |
| US2006/0285913(A1) | 2006-12-01 | Koptis | Applicant |
| US2006/0287900(A1) | 2006-12-01 | Fiore et al. | Applicant |
| US2006/0289679(A1) | 2006-12-01 | Johnson et al. | Applicant |
| US2007/0013379(A1) | 2007-01-01 | Staples et al. | Applicant |
| US2007/0018632(A1) | 2007-01-01 | Royle | Applicant |
| US2007/0100496(A1) | 2007-05-01 | Forell | Applicant |
| US2007/0219722(A1) | 2007-09-01 | Sawyer et al. | Applicant |
| US2007/0268110(A1) | 2007-11-01 | Little | Applicant |
| US2007/0288195(A1) | 2007-12-01 | Waite et al. | Applicant |
| US2008/0125942(A1) | 2008-05-01 | Tucker et al. | Applicant |
| US2008/0204322(A1) | 2008-08-01 | Oswald et al. | Applicant |
| US2008/0228294(A1) | 2008-09-01 | Nielsen et al. | Applicant |
| US2008/0255795(A1) | 2008-10-01 | Shkolnikov | Applicant |
| US2009/0013928(A1) | 2009-01-01 | Nielsen et al. | Applicant |
| US2009/0085568(A1) | 2009-04-01 | Cole | Applicant |
| US2009/0109081(A1) | 2009-04-01 | Ryerson et al. | Applicant |
| US2009/0121933(A1) | 2009-05-01 | Tucker et al. | Applicant |
| US2009/0171616(A1) | 2009-07-01 | Zhang et al. | Applicant |
| US2009/0201178(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0201311(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0202101(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0202110(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0202111(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0202112(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0204238(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0204466(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0204614(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0204625(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0207019(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0208642(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0210098(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0210284(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0210285(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0210297(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0210298(A1) | 2009-08-01 | Nielsen et al. | Applicant |
| US2009/0237408(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0238414(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0238415(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0238416(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0238417(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0241045(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0241046(A1) | 2009-09-01 | Nielsen et al. | Applicant |
| US2009/0324815(A1) | 2009-12-01 | Nielsen et al. | Applicant |
| US2009/0327024(A1) | 2009-12-01 | Nielsen et al. | Applicant |
| US2010/0006667(A1) | 2010-01-01 | Nielsen et al. | Applicant |
| US2010/0010862(A1) | 2010-01-01 | Nielsen et al. | Applicant |
| US2010/0010863(A1) | 2010-01-01 | Nielsen et al. | Applicant |
| US2010/0010882(A1) | 2010-01-01 | Nielsen et al. | Applicant |
| US2010/0010883(A1) | 2010-01-01 | Nielsen et al. | Applicant |
| US2010/0084532(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0085054(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0085185(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0085376(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0085694(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0085701(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0086671(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0086677(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0088031(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0088032(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0088134(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0088135(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0088164(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0090700(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0090858(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0094553(A1) | 2010-04-01 | Nielsen et al. | Applicant |
| US2010/0097224(A1) | 2010-04-01 | Prodanovich et al. | Examiner |
| US2010/0117654(A1) | 2010-05-01 | Nielsen et al. | Applicant |
| US2010/0188088(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0188215(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0188216(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0188245(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0188407(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0189312(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0189887(A1) | 2010-07-01 | Nielsen et al. | Applicant |
| US2010/0198663(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0201690(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0201706(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205031(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205032(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205195(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205264(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205536(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205554(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0205555(A1) | 2010-08-01 | Nielsen et al. | Applicant |
| US2010/0228588(A1) | 2010-09-01 | Nielsen et al. | Applicant |
| US2010/0245086(A1) | 2010-09-01 | Nielsen et al. | Applicant |
| US2010/0247754(A1) | 2010-09-01 | Nielsen et al. | Applicant |
| US2010/0253511(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0253513(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0253514(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0255182(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0256825(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0256863(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0256912(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0256981(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0257029(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0257477(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0259381(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0259414(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0262470(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0262670(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0263591(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0268786(A1) | 2010-10-01 | Nielsen et al. | Applicant |
| US2010/0272885(A1) | 2010-10-01 | Olsson | Applicant |
| US2010/0285211(A1) | 2010-11-01 | Nielsen et al. | Applicant |
| US2010/0318401(A1) | 2010-12-01 | Nielsen et al. | Applicant |
| US2010/0318402(A1) | 2010-12-01 | Nielsen et al. | Applicant |
| US2010/0318465(A1) | 2010-12-01 | Nielsen et al. | Applicant |
| US2010/0324967(A1) | 2010-12-01 | Nielsen et al. | Applicant |
| US2011/0007076(A1) | 2011-01-01 | Nielsen et al. | Applicant |
| US2011/0020776(A1) | 2011-01-01 | Nielsen et al. | Applicant |
| US2011/0022433(A1) | 2011-01-01 | Nielsen et al. | Applicant |
| US2011/0035245(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0035251(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0035252(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0035260(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0035324(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0035328(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0040589(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0040590(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0046993(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0046994(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0046999(A1) | 2011-02-01 | Nielsen et al. | Applicant |
| US2011/0060496(A1) | 2011-03-01 | Nielsen et al. | Applicant |
| US2011/0060549(A1) | 2011-03-01 | Nielsen et al. | Applicant |
| US2011/0095885(A9) | 2011-04-01 | Nielsen et al. | Applicant |
| US2011/0131081(A1) | 2011-06-01 | Nielsen et al. | Applicant |
| US2011/0135163(A1) | 2011-06-01 | Nielsen et al. | Applicant |
| US2011/0137769(A1) | 2011-06-01 | Nielsen et al. | Applicant |
| CH695087(A5) | 2005-12-01 | Applicant | |
| EP636393 | 1995-02-01 | Applicant | |
| EP1521331(A2) | 2005-04-01 | Applicant | |
| EP1852365(A1) | 2007-11-01 | Applicant | |
| EP1974638 | 2008-10-01 | Applicant | |
| GB2266863 | 1993-11-01 | Applicant | |
| WO-9112119 | 1991-08-01 | Applicant | |
| WO-9424584(A1) | 1994-10-01 | Applicant | |
| WO9516827 | 1995-06-01 | Applicant | |
| WO-9629572 | 1996-09-01 | Applicant | |
| WO-9854600(A1) | 1998-12-01 | Applicant | |
| WO-9854601(A1) | 1998-12-01 | Applicant | |
| WO-9900679(A1) | 1999-01-01 | Applicant | |
| WO-0228541 | 2002-04-01 | Applicant | |
| WO-2004100044(A1) | 2004-11-01 | Applicant | |
| WO-2004102242(A1) | 2004-11-01 | Applicant | |
| WO-2005052627(A2) | 2005-06-01 | Applicant | |
| WO-2006015310(A3) | 2006-02-01 | Applicant | |
| WO-2006136776(A1) | 2006-12-01 | Applicant | |
| WO-2006136777(A1) | 2006-12-01 | Applicant | |
| WO-2007067898(A2) | 2007-06-01 | Applicant |
Non-Patent Literature (47)
- Co-pending U.S. Appl. No. 12/539,497, filed Aug. 11, 2009.Applicant
- Co-Pending U.S. Appl. No. 12/568,087, filed Sep. 28, 2009.Applicant
- Co-pending U.S. Appl. No. 12/607,843, filed Oct. 28, 2009.Applicant
- Co-pending U.S. Appl. No. 12/622,768, filed Nov. 20, 2009.Applicant
- Co-pending U.S. Appl. No. 12/639,041, filed Dec. 16, 2009.Applicant
- Co-pending U.S. Appl. No. 12/639,373, filed Dec. 16, 2009.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2008/55796, Oct. 14, 2008.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2008/55798, Jul. 28, 2008.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2009/005299, Dec. 12, 2009.Applicant
- Notice of Allowance dated Nov. 6, 2009 from Co-Pending U.S. Appl. No. 11/685,602.Applicant
- Office Action dated Nov. 18, 2009 from Co-Pending Canadian Application No. 2,623,466, filed Mar. 4, 2008.Applicant
- Office Action dated Nov. 23, 2009 from Co-Pending Canadian Application No. 2,623,761, filed Mar. 4, 2008.Applicant
- Office Action dated Sep. 17, 2009 from Co-Pending U.S. Appl. No. 11/685,602.Applicant
- “New Identification Technology Raises Concerns over Privacy”; PBS Online NewsHour Report; Aug. 17, 2006; pp. 1-5; http://www.pbs.org/newshour/bb/science/july-dec06/rfid—08-17.html.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2009/005348, Mar. 2, 2010.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2009/005359, Feb. 8, 2010.Applicant
- Office Action mailed Apr. 28, 2009 from Co-Pending U.S. Appl. No. 11/685,602.Applicant
- Carey, B., “Tracking Shoes,” Chicago Tribune Online Edition, Jan. 29, 2007; pp. 1-3; http://www.chicagotribune.com/services/site/premium/access-registered.intercept.Applicant
- Fox, G. et al., “GPS Provides Quick, Accurate Data for Underground Utility Location” (as featured in Apr. 2002 issue of Trenchless Technology, http://www.woolpert.com/asp/articles/GPS-Provides.asp, Sep. 14, 2007, pp. 1 and 2.Applicant
- Trimble Navigation Limited, H-Star Technology Explained, www.trimble.com, pp. 1-9, 2005.Applicant
- Co-pending U.S. Appl. No. 11/685,602, filed Mar. 13, 2007.Applicant
- Co-pending U.S. Appl. No. 12/236,688, filed Sep. 24, 2008.Applicant
- Co-pending U.S. Appl. No. 12/429,929, filed Apr. 24, 2009.Applicant
- Co-pending U.S. Appl. No. 12/363,951, filed Feb. 2, 2009.Applicant
- Co-pending U.S. Appl. No. 12/364,369, filed Feb. 2, 2009.Applicant
- Co-pending U.S. Appl. No. 12/364,359, filed Feb. 2, 2009.Applicant
- Co-pending U.S. Appl. No. 12/364,339, filed Feb. 2, 2009.Applicant
- GPS Technology Enhancing Underground Utility Locating, Underground Construction Magazine, Apr. 2010, 3 pages.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/2010/000389, 11 pages.Applicant
- Office Action dated Jun. 16, 2010 from Co-Pending Canadian Application No. 2,691,707, filed Feb. 10, 2010.Applicant
- Office Action for Canadian Patent Application No. 2,623,761, dated Oct. 6, 2010 (2 pages).Applicant
- Notice of Allowance dated Apr. 28, 2011 from U.S. Appl. No. 29/356,631.Applicant
- Notice of Allowance dated Nov. 12, 2010 from U.S. Appl. No. 29/356,634.Applicant
- Notice of Allowance dated Nov. 12, 2010 from U.S. Appl. No. 29/356,633.Applicant
- Notice of Allowance dated Nov. 12, 2010 from U.S. Appl. No. 29/356,635.Applicant
- European Search Report, Application No. 08743673.9, Feb. 28, 2011.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US10/45409, Nov. 18, 2010.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US10/45969, Nov. 18, 2010.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US10/45161, Oct. 29, 2010.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2009/003957, Mar. 21, 2011.Applicant
- International Search Report and Written Opinion, Application Serial No. PCT/US2010/036029, Sep. 7, 2010.Applicant
- Office Action dated Oct. 6, 2010 from Canadian Application No. 2623761.Applicant
- Office Action dated Mar. 9, 2011 from Australian Application No. 2008236526.Applicant
- Office Action dated Mar. 9, 2011 from Australian Application No. 2008226627.Applicant
- Bernold, L.. et al. “Equipment operator training in the age of internet2,” Proceedings of 19th International Symposium on Automation and Robotics In Construction (ISRAC 2002), Sep. 2002 [retrieved on Nov. 12, 2010]. Retrieved from the Internet: <URL: http://fire.nist.gov/bfrIpubsibuild02IPDF/b02059.pdf>. p. 4, col. 2, para 2.Applicant
- Office Action dated Feb. 1, 2011 from Canadian Application No. 2,691,707.Applicant
- Office Action dated May 24, 2011 from U.S. Appl. No. 12/363,951.Applicant