Patent Grant
9185176
Field service operations may be any operation in which companies dispatch technicians and/or other staff to perform certain activities, for example, installations, services and/or repairs. Field service operations may exist in various industries, examples of which include, but are not limited to, network installations, utility installations, security systems, construction, medical equipment, heating, ventilating and air conditioning (HVAC) and the like.
An example of a field service operation in the construction industry is a so-called “locate and marking operation,” also commonly referred to more simply as a “locate operation” (or sometimes merely as “a locate”). In a typical locate operation, a locate technician visits a work site in which there is a plan to disturb the ground (e.g., excavate, dig one or more holes and/or trenches, bore, etc.) so as to determine a presence or an absence of one or more underground facilities (such as various types of utility cables and pipes) in a dig area to be excavated or disturbed at the work site. In some instances, a locate operation may be requested for a “design” project, in which there may be no immediate plan to excavate or otherwise disturb the ground, but nonetheless information about a presence or absence of one or more underground facilities at a work site may be valuable to inform a planning, permitting and/or engineering design phase of a future construction project.
In many states, an excavator who plans to disturb ground at a work site is required by law to notify any potentially affected underground facility owners prior to undertaking an excavation activity. Advanced notice of excavation activities may be provided by an excavator (or another party) by contacting a “one-call center.” One-call centers typically are operated by a consortium of underground facility owners for the purposes of receiving excavation notices and in turn notifying facility owners and/or their agents of a plan to excavate. As part of an advanced notification, excavators typically provide to the one-call center various information relating to the planned activity, including a location (e.g., address) of the work site and a description of the dig area to be excavated or otherwise disturbed at the work site.
Using the information provided in a locate request for planned excavation or design projects, the one-call center identifies certain underground facilities that may be present at the indicated work site. For this purpose, many one-call centers typically maintain a collection “polygon maps” which indicate, within a given geographic area over which the one-call center has jurisdiction, generally where underground facilities may be found relative to some geographic reference frame or coordinate system.
Polygon maps typically are provided to the one-call centers by underground facilities owners within the jurisdiction of the one call center (“members” of the one-call center). A one-call center first provides the facility owner/member with one or more maps (e.g., street or property maps) within the jurisdiction, on which are superimposed some type of grid or coordinate system employed by the one-call center as a geographic frame of reference. Using the maps provided by the one-call center, the respective facilities owners/members draw one or more polygons on each map to indicate an area within which their facilities generally are disposed underground (without indicating the facilities themselves). These polygons themselves do not precisely indicate geographic locations of respective underground facilities; rather, the area enclosed by a given polygon generally provides an over-inclusive indication of where a given facilities owner's underground facilities are disposed. Different facilities owners/members may draw polygons of different sizes around areas including their underground facilities, and in some instances such polygons can cover appreciably large geographic regions (e.g., an entire subdivision of a residential area), which may further obfuscate the actual/precise location of respective underground facilities.
Based on the polygon maps collected from the facilities owners/members, the one-call center may in some instances create composite polygon maps to show polygons of multiple different members on a single map. Whether using single member or composite polygon maps, the one-call center examines the address or location information provided in the locate request and identifies a significant buffer zone around an identified work site so as to make an over-inclusive identification of facilities owners/members that may have underground facilities present (e.g., to err on the side of caution). In particular, based on this generally over-inclusive buffer zone around the identified work site (and in some instances significantly over-inclusive buffer zone), the one-call center consults the polygon maps to identify which member polygons intersect with all or a portion of the buffer zone so as to notify these underground facility owners/members and/or their agents of the proposed excavation or design project. Again, it should be appreciated that the buffer zones around an indicated work site utilized by one-call centers for this purpose typically embrace a geographic area that includes but goes well beyond the actual work site, and in many cases the geographic area enclosed by a buffer zone is significantly larger than the actual dig area in which excavation or other similar activities are planned. Similarly, as noted above, the area enclosed by a given member polygon generally does not provide a precise indication of where one or more underground facilities may in fact be found.
In some instances, one-call centers may also or alternatively have access to various existing maps of underground facilities in their jurisdiction, referred to as “facilities maps.” Facilities maps typically are maintained by facilities owners/members within the jurisdiction and show, for respective different utility types, where underground facilities purportedly may be found relative to some geographic reference frame or coordinate system (e.g., a grid, a street or property map, GPS latitude and longitude coordinates, etc.). Facilities maps generally provide somewhat more detail than polygon maps provided by facilities owners/members; however, in some instances the information contained in facilities maps may not be accurate and/or complete. For at least this reason, whether using polygon maps or facilities maps, as noted above the one-call center utilizes a significant buffer zone around an identified work site so as to make an over-inclusive identification of facilities owners/members that may have underground facilities present.
Once facilities implicated by the locate request are identified by a one-call center (e.g., via the polygon map/buffer zone process), the one-call center generates a “locate request ticket” (also known as a “locate ticket,” or simply a “ticket”). The locate request ticket essentially constitutes an instruction to inspect a work site and typically identifies the work site of the proposed excavation or design and a description of the dig area, typically lists on the ticket all of the underground facilities that may be present at the work site (e.g., by providing a member code for the facility owner whose polygon falls within a given buffer zone), and may also include various other information relevant to the proposed excavation or design (e.g., the name of the excavation company, a name of a property owner or party contracting the excavation company to perform the excavation, etc.). The one-call center sends the ticket to one or more underground facility owners 140 and/or one or more locate service providers 130 (who may be acting as contracted agents of the facility owners) so that they can conduct a locate and marking operation to verify a presence or absence of the underground facilities in the dig area. For example, in some instances, a given underground facility owner 140 may operate its own fleet of locate technicians (e.g., locate technician 145), in which case the one-call center 120 may send the ticket to the underground facility owner 140. In other instances, a given facility owner may contract with a locate service provider to receive locate request tickets and perform a locate and marking operation in response to received tickets on their behalf.
Upon receiving the locate request, a locate service provider or a facility owner (hereafter referred to as a “ticket recipient”) may dispatch a locate technician to the work site of planned excavation to determine a presence or absence of one or more underground facilities in the dig area to be excavated or otherwise disturbed. A typical first step for the locate technician includes utilizing an underground facility “locate device,” which is an instrument or set of instruments (also referred to commonly as a “locate set”) for detecting facilities that are concealed in some manner, such as cables and pipes that are located underground. The locate device is employed by the technician to verify the presence or absence of underground facilities indicated in the locate request ticket as potentially present in the dig area (e.g., via the facility owner member codes listed in the ticket). This process is often referred to as a “locate operation.”
In one example of a locate operation, an underground facility locate device is used to detect electromagnetic fields that are generated by an applied signal provided along a length of a target facility to be identified. In this example, a locate device may include both a signal transmitter to provide the applied signal (e.g., which is coupled by the locate technician to a tracer wire disposed along a length of a facility), and a signal receiver which is generally a hand-held apparatus carried by the locate technician as the technician walks around the dig area to search for underground facilities.
In yet another example, a locate device employed for a locate operation may include a single instrument, similar in some respects to a conventional metal detector. In particular, such an instrument may include an oscillator to generate an alternating current that passes through a coil, which in turn produces a first magnetic field. If a piece of electrically conductive metal is in close proximity to the coil (e.g., if an underground facility having a metal component is below/near the coil of the instrument), eddy currents are induced in the metal and the metal produces its own magnetic field, which in turn affects the first magnetic field. The instrument may include a second coil to measure changes to the first magnetic field, thereby facilitating detection of metallic objects.
In addition to the locate operation, the locate technician also generally performs a “marking operation,” in which the technician marks the presence (and in some cases the absence) of a given underground facility in the dig area based on the various signals detected (or not detected) during the locate operation. For this purpose, the locate technician conventionally utilizes a “marking device” to dispense a marking material on, for example, the ground, pavement, or other surface along a detected underground facility. Marking material may be any material, substance, compound, and/or element, used or which may be used separately or in combination to mark, signify, and/or indicate. Examples of marking materials may include, but are not limited to, paint, chalk, dye, and/or iron. Marking devices, such as paint marking wands and/or paint marking wheels, provide a convenient method of dispensing marking materials onto surfaces, such as onto the surface of the ground or pavement.
In
In some environments, arrows, flags, darts, or other types of physical marks may be used to mark the presence or absence of an underground facility in a dig area, in addition to or as an alternative to a material applied to the ground (such as paint, chalk, dye, tape) along the path of a detected utility. The marks resulting from any of a wide variety of materials and/or objects used to indicate a presence or absence of underground facilities generally are referred to as “locate marks.” Often, different color materials and/or physical objects may be used for locate marks, wherein different colors correspond to different utility types. For example, the American Public Works Association (APWA) has established a standardized color-coding system for utility identification for use by public agencies, utilities, contractors and various groups involved in ground excavation (e.g., red=electric power lines and cables; blue=potable water; orange=telecommunication lines; yellow=gas, oil, steam). In some cases, the technician also may provide one or more marks to indicate that no facility was found in the dig area (sometimes referred to as a “clear”).
As mentioned above, the foregoing activity of identifying and marking a presence or absence of one or more underground facilities generally is referred to for completeness as a “locate and marking operation.” However, in light of common parlance adopted in the construction industry, and/or for the sake of brevity, one or both of the respective locate and marking functions may be referred to in some instances simply as a “locate operation” or a “locate” (i.e., without making any specific reference to the marking function). Accordingly, it should be appreciated that any reference in the relevant arts to the task of a locate technician simply as a “locate operation” or a “locate” does not necessarily exclude the marking portion of the overall process. At the same time, in some contexts a locate operation is identified separately from a marking operation, wherein the former relates more specifically to detection-related activities and the latter relates more specifically to marking-related activities.
Inaccurate locating and/or marking of underground facilities can result in physical damage to the facilities, property damage, and/or personal injury during the excavation process that, in turn, can expose a facility owner or contractor to significant legal liability. When underground facilities are damaged and/or when property damage or personal injury results from damaging an underground facility during an excavation, the excavator may assert that the facility was not accurately located and/or marked by a locate technician, while the entity who dispatched the technician (e.g., locate contractor, facility owner, municipality, etc.) may in turn assert that the facility was indeed properly located and marked. Proving whether the underground facility was properly located and marked can be difficult after the excavation (or after some damage, e.g., a gas explosion), because in many cases the physical locate marks (e.g., the marking material or other physical marks used to mark the facility on the surface of the dig area) will have been disturbed or destroyed during the excavation process (and/or damage resulting from excavation).
Entities that oversee the performance of locate operations, such as locate contractors, facility owners, and municipalities, may manage locate technician work forces of various sizes. Applicants have recognized and appreciated that even for relatively modest-sized technician work forces, implementing and performing meaningful oversight and quality control activities in a timely fashion in connection with locate operations may be difficult; for example, each technician may be assigned numerous locate tickets to complete during the course of a given time period, and may cover appreciable geographic territory.
Conventionally, at best there are limited oversight and/or quality control activities in connection with underground facility locate operations, and in many instances there are no quality control activities whatsoever. As a result, in some cases locate operations may not even be performed pursuant to issued tickets (e.g., technicians don't go to work sites); in other instances, poor performance, increased risk of damage to facilities, and/or a failure to comply with various regulations or contract requirements may go undetected, thereby adversely affecting customer satisfaction. Perhaps more importantly, locate operations that are not in fact performed pursuant to issued tickets, or poorly performed and/or poorly managed locate operations, may jeopardize public safety and/or the safety of workers in and around work sites, and may lead to wide scale utility outages having dramatic economic impact on businesses and communities. Additionally, the time, effort and cost that is associated with re-performing work in the field requiring correction and/or improvement of poorly performed locate operations may be unacceptable.
Moreover, data and infrastructure generally is lacking to facilitate tracking activities and processes in conventional underground facility locate operations and other field service operations. Consequently, in order to provide improved oversight and quality control, improved instrumentation is required so as to acquire and communicate relevant data pertaining to operations, as well as computer-implemented methods (e.g., computing devices executing software applications) for effectively and efficiently acquiring, analyzing and processing relevant data, and communicating relevant information pursuant to such analysis at multiple operational levels (e.g., regulators, auditors, management, supervisors, technicians) and/or with all interested parties (excavators or other requesting parties, one-call centers and their members, municipalities, facility owners, locate contractors, locate technicians).
Accordingly, a need exists for ways of providing oversight, quality control and proof of compliance with applicable regulations and relevant customer-supplier agreements in field service applications in order to remove uncertainty, improve customer satisfaction, identify and reduce the number of poorly performed field calls, and improve management's visibility into the activities of its distributed workforce operations. More specifically, a need exists for improved approaches to quality control in the underground facility locate industry in order to improve customer satisfaction, prove performance of relevant customer-supplier agreements, insure compliance with applicable federal, state or local regulations and reduce the risk of damage to underground facilities due to poorly performed underground facility locate operations.
In view of the foregoing, various embodiments disclosed herein relate to inventive systems, methods and apparatus for managing locate operations (i.e., locate and/or marking operations) to identify (e.g., detect and/or mark) a presence or absence of one or more underground facilities within a dig area. In various aspects described herein, the systems, methods and apparatus according to the present invention provide a holistic approach to management and oversight of locate operations in one or more of the following ways:
In some exemplary implementations, an improved locate request including image data (and optionally non-image data/information associated with the image data) is electronically created (e.g., by a requesting party, such as an excavator, property owner, facility owner, regulatory authority, damage investigator, etc.), in which one or more dig areas at a work site are identified by one or more dig area indicators superimposed on an image of the work site, so as to create a marked-up image. Such a request may form the basis of a locate request ticket to be forwarded to one or more parties that may have underground facilities in an area surrounding the work site (e.g., via a one-call center polygon map process as discussed above), in which the locate request ticket includes accompanying image data for the dig area indicator(s) and/or the marked-up image itself.
In some implementations, a party receiving such a ticket may parse the ticket to extract relevant information, and/or perform a comprehensive assessment process based on information extracted from the ticket (i.e., “ticket information”), to provide information that can be used to improve activity scheduling, resource allocation, quality control, and/or regulatory compliance. In some aspects, a ticket assessment process may establish the integrity, accuracy, and/or completeness of ticket information in connection with specified location of planned excavation, and provide assessments relating to scope of work (amount and nature of work), complexity involved, duration (amount of time required), risk (potential liability for damages), business value (penalty and/or profitability), and skill/certification requirements for technicians in performing the operation.
In another aspect of the inventive embodiments discussed herein, ticket assessment outcomes may be employed to inform a scheduling process for dispatching technicians. More generally, according to exemplary scheduling processes relating to the management systems and methods disclosed herein, scheduling of technicians and allocation of technicians to particular locate operations may be based at least in part on one or more of: performance deadlines for the operations and relevant shift times of available technicians; various parameters relating to the operations themselves (job performance information and/or quality assessment information), technicians (e.g., historical efficiencies, particular skills/certification, security clearance), and/or relevant environmental conditions (e.g., weather, traffic); ticket assessment outcomes (e.g., risk information; penalty or profitability information; complexity information; technician skill/certification requirements); contractual obligations between the entity dispatching technicians and responsible for/overseeing the locate operations, and one or more parties for which the operation(s) is/are being performed; statutory and/or regulatory requirements, such as wage and hour compliance for resources (e.g., availability of resources for scheduling complies with applicable wage and hour statutes/regulations), and/or the time and/or manner in which a given operation needs to be performed pursuant to applicable statutes/regulations.
In yet other embodiments of management systems and methods, a process guide may be provided to a technician, once dispatched, to facilitate performance of the locate operation. For example, ticket information (which may include an original locate request ticket issued by a one-call center, a work order derived from one or more locate request tickets, or other process guide) may be displayed and/or processed on one or more pieces of locating equipment used in the field by a technician, and/or one or more other computing devices (e.g., tablet computer, personal digital assistant, smart phone, or other portable/handheld computing device). As part of performing the locate operation, the technician may provide some input to generate an electronic record or log of technician activity during the operation. In one exemplary implementation, a process guide in the form of a checklist may be generated (e.g., based at least in part on the ticket information), either at a remote computer and then downloaded to the locating equipment, or generated at the locate equipment itself, and displayed locally to the technician as a guide to perform and verify various aspects of the operation(s). In another exemplary implementation, a set of instructions or “workflow” may be generated (either remotely or on the locate equipment) to guide the technician through a sequence of steps to perform the locate operation. Performance via a process guide (e.g., checklist or workflow) may be interactive in that the technician may provide input, or automated/semi-automated by analyzing various information collected by the locating equipment with respect to the ticket information and/or other available information germane to the operation(s).
With respect to information collected by locating equipment, in various implementations of the inventive concepts disclosed herein, a technician may employ one more pieces of “intelligent locating equipment,” e.g., one or more of a marking device, a locate transmitter, a locate receiver, or a combined locate and marking device, that is configured to acquire, store, process, analyze and/or transmit a variety of information germane to the locate operation. In exemplary aspects, such intelligent locating equipment typically comprises a communication interface, memory, one or more processors, a user interface/display device, and one or more input devices/sensors for acquiring various information germane to the operation. Acquired information may be logged into an electronic record stored in memory, analyzed/processed in any of a variety of manners, and/or transmitted to one or more other devices (e.g., remote computers, other locating equipment, etc.). In some implementations, multiple pieces of intelligent locating equipment may be communicatively coupled to each other, as well as one or more other computing devices, and work in tandem to acquire, analyze or otherwise process various information collected in connection with the locate operation.
For example, intelligent locating equipment may be configured with a location tracking system to acquire geo-location data relating to where underground facilities are detected and/or marked. Locate devices may be configured with processor-controlled detection electronics to receive signals relating to facility detection and to analyze one or more characteristics of such signals. Marking devices may be configured with marking material detection mechanisms to provide various information relating to characteristics of marking material dispensed to mark ground, pavement or other surfaces. Both locate and marking devices may be equipped with various environmental and/or operational sensors to acquire information relating to environmental conditions in and around the area of use and/or storage of the locating equipment, and/or operational conditions of the locate equipment itself. Additionally, both locate and marking devices may include one or more input devices to acquire information relating to landmarks in and around the work site. Further, one or both of the user interface and the communication interface of such intelligent locating equipment may serve as conduits for receiving various information relating to the operation; for example, as discussed above, ticket information or other service-related information may be received via the communication interface, and/or entered in via a user interface, and such information may also be logged into an electronic record of the locate operation.
Whether intelligent locating equipment is utilized in the field by a technician, or conventional locating equipment is employed (e.g., as discussed above in connection with
In some implementations in which the technician employs one or more pieces of intelligent locating equipment, information stored in one or more electronic records of the locating equipment, or information generated in real-time by the locating equipment, may be passed to the electronic manifest application and used to automatically populate/mark-up an image with electronic detection marks, electronic locate marks, and/or electronic landmarks indicating where facilities/landmarks were detected and/or marked. In the event that no underground facilities are found (e.g., a “clear”), in some instances one or more physical locate marks may nonetheless be applied to the dig area to indicate the absence of an underground facility, and as such one or more electronic locate mark indicators may be added to the electronic manifest; however, in other instances, no physical locate marks may be applied to the dig area in the event of a “clear,” and accordingly in some cases no electronic locate mark indicators may be added to the electronic manifest in the event of a “clear.” In yet another aspect, the image used by the electronic manifest application to create an electronic manifest may be derived from image information included with the original locate request, which image information may include information relating to one or more dig area indicators; in this manner, visual information regarding the locate operation as performed may be superimposed upon an image that includes the dig area indicator(s) provided as part of the original locate request, so as to generate an electronic manifest.
In some implementations, an electronic manifest generated either manually by a technician via a drawing tool, or automatically populated at least in part with information acquired via intelligent locating equipment, may accompany or constitute a “completed” electronic locate request ticket. For purposes of the present disclosure, a “completed” electronic locate request ticket refers to an electronic communication generated by a technician indicating that a locate operation has been attempted or performed, at least to some extent. Accordingly, it should be appreciated that a “completed” ticket does not necessarily imply that a locate operation itself was successfully performed in its entirety (as dictated by one or more locate request tickets), but that it was at least initiated and attempted in some fashion. For example, a technician may be dispatched to a work site, may begin performing a locate operation, and may encounter some unforeseen impediment to completing the operation, or some condition or circumstance that warrants special action or attention. Accordingly, the technician may generate a “completed” ticket that reflects the attempted operation but in some manner reflects the anomalous situation attendant to the attempted locate operation. In any event, according to various embodiments, an electronic manifest, including a marked-up image, and/or any of the data/information associated with the image contents, may be provided as part of, or an attachment to, a completed locate request ticket so as to augment the information content provided pursuant to the locate operation.
In yet other aspects of the inventive systems, methods and apparatus disclosed herein, completed tickets may be reviewed, in essentially real-time during performance of a locate operation, and/or at any time following attempt/completion of a locate operation, to provide a quality assessment of the locate operation (e.g., an assessment of the completeness, accuracy, and/or efficiency of the operation). Quality assessment processes according to various embodiments may be primarily under the discretion of a human reviewer, albeit facilitated in some respects by computer-aided display of information, and electronic record keeping and communication functions associated with the quality assessment result(s). In other embodiments, information related to a locate operation (e.g., electronic manifest information accompanying or constituting a completed ticket) is electronically analyzed such that a quality assessment is based at least in part on some predetermined criteria and/or metrics that facilitate an automated determination of quality assessment. In one aspect, if the locate operation represented by the completed ticket complies with a predetermined quality standard (e.g., based on predetermined criteria and/or metrics), the locate operation may be “approved” (e.g., a quality assessment process/engine may generate an “approved completed locate request ticket”). In another aspect, real-time quality assessment during performance of a locate operation may facilitate identification of risks or problems that may be flagged for proactive corrective action (e.g., immediately, or as soon as practicable).
In yet other aspects, various quality assessment functions may be implemented in a centralized or distributed fashion. For example, in one implementation, a central server or other computing device(s) operated by a locate service provider or other entity may collect relevant information from the field relating to locate operations and perform quality assessments of same. In another implementation, intelligent locating equipment may be configured to perform some degree of quality assessment local to the work site; for example, intelligent locating equipment may be configured to acquire information about the locate operation and its environs, compare elements of acquired information to various criteria relating to functionality and/or use of the locating equipment, and/or one or more environmental conditions proximate to the locating equipment and/or work site in which it is being used, and provide one or more local alerts (e.g., visual, audible, and/or tactile indications) to a technician to indicate any detected out-of-tolerance conditions. Such locally detected conditions also may be transmitted by intelligent locating equipment to one or more other pieces of intelligent locate equipment in the area, and or one or more remote computing devices, for further and/or corroborative quality assessment or other analysis. In this fashion, a host of quality assessment functionality may be facilitated at various organizational levels, and/or amongst multiple distributed computing resources.
In other aspects, any information acquired in connection with the locate operation (e.g., electronic records acquired by intelligent locating equipment, electronic manifests), as well as quality assessment results, may be archived (e.g., in a database and/or central data store) for future reference/access by various parties that may be interested in such information (e.g., excavators, one-call centers, facility owners, locate contractors, municipalities, regulatory authorities, damage investigators/assessors, insurance companies, etc.). In particular, any information relating to an approved completed locate request ticket may be electronically transmitted and/or electronically stored so as to provide a searchable, secure, and unalterable electronic record of the locate operation (e.g., using any of a variety of conventionally available encryption algorithms, such as TripleDES/TDEA, or the Blowfish keyed symmetric block cipher). Such an electronic record provides for improved visibility, quality control and audit capability for underground facility locate operations.
In yet other embodiments of management systems and methods according to the present invention, at one or more points during the processes discussed above, one or more “positive response” notifications indicating a status of the locate operation and/or disposition of the technician, and/or more detailed information about the progress of the locate operation, may be electronically transmitted and/or stored so as to inform at least one party associated with requesting the operation of the status of the operation and/or details thereof. In one aspect, a requesting party may designate a particular format, content, and/or method of receiving notifications regarding the locate operation. In another aspect, a computer-generated GUI may be provided to facilitate submission of locate requests, generation of image information to indicate one or more dig areas on a digital image of a work site as part of a locate request, and/or selection of notifications and preferences for same. In yet another aspect, a requesting party may provide an acknowledgement of receipt (e.g., a “return receipt”) for one or more received notifications.
In sum, one embodiment of the present invention is directed to an apparatus for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The apparatus comprises a communication interface, a memory to store processor-executable instructions, and a processing unit coupled to the communication interface and the memory. Upon execution of the processor-executable instructions by the processing unit, the processing unit: controls the communication interface to electronically receive the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; controls the communication interface to transmit the locate request ticket to at least one locate personnel device; controls the communication interface to receive from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including an updated marked-up image, the updated marked-up image including the at least one dig area indicator and at least one locate mark indicator to digitally represent a location of at least one physical locate mark applied to the dig area during the locate operation; processes the completed locate request ticket and electronically marks the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and controls the communication interface and/or the memory to electronically transmit and/or electronically store information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to at least one computer-readable medium encoded with instructions that, when executed on at least one processing unit, perform a method for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The method comprises: A) electronically receiving the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; B) transmitting the locate request ticket received in A) to at least one locate personnel device; C) receiving from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including an updated marked-up image, the updated marked-up image including the at least one dig area indicator and at least one locate mark indicator to digitally represent a location of at least one physical locate mark applied to the dig area during the locate operation; D) electronically marking the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and E) electronically transmitting and/or electronically storing information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to a method for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The method comprises: A) electronically receiving the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; B) transmitting the locate request ticket received in A) to at least one locate personnel device; C) receiving from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including an updated marked-up image, the updated marked-up image including the at least one dig area indicator and at least one locate mark indicator to digitally represent a location of at least one physical locate mark applied to the dig area during the locate operation; D) electronically marking the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and E) electronically transmitting and/or electronically storing information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to an apparatus for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The apparatus comprises a communication interface; a memory to store processor-executable instructions; and a processing unit coupled to the communication interface and the memory. Upon execution of the processor-executable instructions by the processing unit, the processing unit: A) controls the communication interface to electronically receive the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; B) controls the communication interface to transmit the locate request ticket to at least one locate personnel device; C) controls the communication interface to receive from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including image data and non-image data associated with the locate operation, the non-image data including at least one of: a timestamp for the locate operation; geographic information associated with the dig area; and at least one identifier for a locate technician and/or a locate company; D) processes the completed locate request ticket and electronically marks the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and E) controls the communication interface and/or the memory to electronically transmit and/or electronically store information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to a method for performing a locate operation. The locate operation comprises identifying, in response to at least one locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The method comprises: A) electronically receiving the at least one locate request ticket identifying the dig area, the at least one locate request ticket including image data associated with the dig area, wherein the image data includes at least one marked-up image of a geographic area including the dig area, the at least one marked-up image including at least one dig area indicator to provide an indication of the dig area; B) inspecting the dig area based at least in part on the at least one dig area indicator in the at least one marked-up image received in A) so as to determine the presence or the absence of the at least one underground facility; C) if the presence of the at least one underground facility is determined, using a marking device to physically mark the dig area with at least one physical locate mark to indicate the presence of the at least one underground facility; D) adding to the at least one marked-up image at least one locate mark indicator to digitally represent a location of the at least one physical locate mark on the at least one marked-up image, together with the at least one dig area indicator, so as to generate a completed locate request ticket including the at least one marked-up image; E) reviewing the completed locate request ticket and, if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, electronically marking the completed locate request ticket as approved so as to provide an approved completed locate request ticket; and F) electronically transmitting and/or electronically storing information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation. In one aspect, prior to D), the method comprises: D1) electronically receiving from the marking device location information regarding the location of the at least one physical locate mark applied in C), wherein D) comprises adding the at least one locate mark indicator to the at least one marked-up image based at least in part on the location information received in D1).
Another embodiment is directed to a method for performing a locate operation. The locate operation comprises identifying, in response to at least one locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The method comprises: A) electronically receiving the at least one locate request ticket identifying the dig area, the at least one locate request ticket including image data associated with the dig area, wherein the image data includes at least one marked-up image of a geographic area including the dig area, the at least one marked-up image including at least one dig area indicator to provide an indication of the dig area; B) adding to the at least one marked-up image at least one locate mark indicator to digitally represent a location of the at least one physical locate mark on the at least one marked-up image, together with the at least one dig area indicator, so as to generate a completed locate request ticket including the at least one marked-up image; C) reviewing the completed locate request ticket and, if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, electronically marking the completed locate request ticket as approved so as to provide an approved completed locate request ticket; and D) electronically transmitting and/or electronically storing information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to an apparatus for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The apparatus comprises: a communication interface; a memory to store processor-executable instructions; and a processing unit coupled to the communication interface and the memory. Upon execution of the processor-executable instructions by the processing unit, the processing unit: generates the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; controls the communication interface to transmit the locate request ticket to at least one locate personnel device; controls the communication interface to receive from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including an updated marked-up image, the updated marked-up image including the at least one dig area indicator and at least one locate mark indicator to digitally represent a location of at least one physical locate mark applied to the dig area during the locate operation; processes the completed locate request ticket and electronically marks the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and controls the communication interface and/or the memory to electronically transmit and/or electronically store information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to at least one computer-readable medium encoded with instructions that, when executed on at least one processing unit, perform a method for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The method comprises: A) generating the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; B) transmitting the locate request ticket received in A) to at least one locate personnel device; C) receiving from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including an updated marked-up image, the updated marked-up image including the at least one dig area indicator and at least one locate mark indicator to digitally represent a location of at least one physical locate mark applied to the dig area during the locate operation; D) electronically marking the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and E) electronically transmitting and/or electronically storing information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
Another embodiment is directed to a method for managing a locate operation. The locate operation comprises identifying, in response to a locate request ticket, a presence or an absence of at least one underground facility within a dig area, wherein at least a portion of the dig area may be excavated or disturbed during excavation activities. The method comprises: A) generating the locate request ticket identifying the dig area, the locate request ticket including image data associated with the dig area, wherein the image data includes a marked-up image of a geographic area including the dig area, the marked-up image including at least one dig area indicator to provide an indication of the dig area; B) transmitting the locate request ticket received in A) to at least one locate personnel device; C) receiving from the at least one locate personnel device a completed locate request ticket, the completed locate request ticket including an updated marked-up image, the updated marked-up image including the at least one dig area indicator and at least one locate mark indicator to digitally represent a location of at least one physical locate mark applied to the dig area during the locate operation; D) electronically marking the completed locate request ticket as approved if the locate operation represented by the completed locate request ticket complies with a predetermined quality standard, so as to provide an approved completed locate request ticket; and E) electronically transmitting and/or electronically storing information relating to the approved completed locate request ticket so as to provide a searchable electronic record of the locate operation.
For purposes of the present disclosure, the term “dig area” refers to a specified area of a work site within which there is a plan to disturb the ground (e.g., excavate, dig holes and/or trenches, bore, etc.), and beyond which there is no plan to excavate in the immediate surroundings. Thus, the metes and bounds of a dig area are intended to provide specificity as to where some disturbance to the ground is planned at a given work site. It should be appreciated that a given work site may include multiple dig areas.
The term “facility” refers to one or more lines, cables, fibers, conduits, transmitters, receivers, or other physical objects or structures capable of or used for carrying, transmitting, receiving, storing, and providing utilities, energy, data, substances, and/or services, and/or any combination thereof. The term “underground facility” means any facility beneath the surface of the ground. Examples of facilities include, but are not limited to, oil, gas, water, sewer, power, telephone, data transmission, cable television (TV), and/or internet services.
The term “locate device” refers to any apparatus and/or device for detecting and/or inferring the presence or absence of any facility, including without limitation, any underground facility. In various examples, a locate device may include both a locate transmitter and a locate receiver (which in some instances may also be referred to collectively as a “locate instrument set,” or simply “locate set”).
The term “marking device” refers to any apparatus, mechanism, or other device that employs a marking dispenser for causing a marking material and/or marking object to be dispensed, or any apparatus, mechanism, or other device for electronically indicating (e.g., logging in memory) a location, such as a location of an underground facility. Additionally, the term “marking dispenser” refers to any apparatus, mechanism, or other device for dispensing and/or otherwise using, separately or in combination, a marking material and/or a marking object. An example of a marking dispenser may include, but is not limited to, a pressurized can of marking paint. The term “marking material” means any material, substance, compound, and/or element, used or which may be used separately or in combination to mark, signify, and/or indicate. Examples of marking materials may include, but are not limited to, paint, chalk, dye, and/or iron. The term “marking object” means any object and/or objects used or which may be used separately or in combination to mark, signify, and/or indicate. Examples of marking objects may include, but are not limited to, a flag, a dart, and arrow, and/or an RFID marking ball. It is contemplated that marking material may include marking objects. It is further contemplated that the terms “marking materials” or “marking objects” may be used interchangeably in accordance with the present disclosure.
The term “locate mark” means any mark, sign, and/or object employed to indicate the presence or absence of any underground facility. Examples of locate marks may include, but are not limited to, marks made with marking materials, marking objects, global positioning or other information, and/or any other means. Locate marks may be represented in any form including, without limitation, physical, visible, electronic, and/or any combination thereof.
The terms “actuate” or “trigger” (verb form) are used interchangeably to refer to starting or causing any device, program, system, and/or any combination thereof to work, operate, and/or function in response to some type of signal or stimulus. Examples of actuation signals or stimuli may include, but are not limited to, any local or remote, physical, audible, inaudible, visual, non-visual, electronic, mechanical, electromechanical, biomechanical, biosensing or other signal, instruction, or event. The terms “actuator” or “trigger” (noun form) are used interchangeably to refer to any method or device used to generate one or more signals or stimuli to cause or causing actuation. Examples of an actuator/trigger may include, but are not limited to, any form or combination of a lever, switch, program, processor, screen, microphone for capturing audible commands, and/or other device or method. An actuator/trigger may also include, but is not limited to, a device, software, or program that responds to any movement and/or condition of a user, such as, but not limited to, eye movement, brain activity, heart rate, other data, and/or the like, and generates one or more signals or stimuli in response thereto. In the case of a marking device or other marking mechanism (e.g., to physically or electronically mark a facility or other feature), actuation may cause marking material to be dispensed, as well as various data relating to the marking operation (e.g., geographic location, time stamps, characteristics of material dispensed, etc.) to be logged in an electronic file stored in memory. In the case of a locate device or other locate mechanism (e.g., to physically locate a facility or other feature), actuation may cause a detected signal strength, signal frequency, depth, or other information relating to the locate operation to be logged in an electronic file stored in memory.
The terms “locate and marking operation,” “locate operation,” and “locate” generally are used interchangeably and refer to any activity to detect, infer, and/or mark the presence or absence of an underground facility. In some contexts, the term “locate operation” is used to more specifically refer to detection of one or more underground facilities, and the term “marking operation” is used to more specifically refer to using a marking material and/or one or more marking objects to mark a presence or an absence of one or more underground facilities. The term “locate technician” refers to an individual performing a locate operation. A locate and marking operation often is specified in connection with a dig area, at least a portion of which may be excavated or otherwise disturbed during excavation activities.
The term “user” refers to an individual utilizing a locate device and/or a marking device and may include, but is not limited to, land surveyors, locate technicians, and support personnel.
The terms “locate request” and “excavation notice” are used interchangeably to refer to any communication to request a locate and marking operation. The term “locate request ticket” (or simply “ticket”) refers to any communication or instruction to perform a locate operation. A ticket might specify, for example, the address or description of a dig area to be marked, the day and/or time that the dig area is to be marked, and/or whether the user is to mark the excavation area for certain gas, water, sewer, power, telephone, cable television, and/or some other underground facility. The term “historical ticket” refers to past tickets that have been completed.
The following U.S. published applications are hereby incorporated herein by reference:
U.S. Pat. No. 7,640,105, issued Dec. 29, 2009, filed Mar. 13, 2007, and entitled “Marking System and Method With Location and/or Time Tracking;”
U.S. publication no. 2008-0245299-A1, published Oct. 9, 2008, filed Apr. 4, 2007, and entitled “Marking System and Method;”
U.S. publication no. 2009-0013928-A1, published Jan. 15, 2009, filed Sep. 24, 2008, and entitled “Marking System and Method;”
U.S. publication no. 2009-0238414-A1, published Sep. 24, 2009, filed Mar. 18, 2008, and entitled “Virtual White Lines for Delimiting Planned Excavation Sites;”
U.S. publication no. 2009-0241045-A1, published Sep. 24, 2009, filed Sep. 26, 2008, and entitled “Virtual White Lines for Delimiting Planned Excavation Sites;”
U.S. publication no. 2009-0238415-A1, published Sep. 24, 2009, filed Sep. 26, 2008, and entitled “Virtual White Lines for Delimiting Planned Excavation Sites;”
U.S. publication no. 2009-0241046-A1, published Sep. 24, 2009, filed Jan. 16, 2009, and entitled “Virtual White Lines for Delimiting Planned Excavation Sites;”
U.S. publication no. 2009-0238416-A1, published Sep. 24, 2009, filed Jan. 16, 2009, and entitled “Virtual White Lines for Delimiting Planned Excavation Sites;”
U.S. publication no. 2009-0237408-A1, published Sep. 24, 2009, filed Jan. 16, 2009, and entitled “Virtual White Lines for Delimiting Planned Excavation Sites;”
U.S. publication no. 2009-0202101-A1, published Aug. 13, 2009, filed Feb. 12, 2008, and entitled “Electronic Manifest of Underground Facility Locate Marks;”
U.S. publication no. 2009-0202110-A1, published Aug. 13, 2009, filed Sep. 11, 2008, and entitled “Electronic Manifest of Underground Facility Locate Marks;”
U.S. publication no. 2009-0201311-A1, published Aug. 13, 2009, filed Jan. 30, 2009, and entitled “Electronic Manifest of Underground Facility Locate Marks;”
U.S. publication no. 2009-0202111-A1, published Aug. 13, 2009, filed Jan. 30, 2009, and entitled “Electronic Manifest of Underground Facility Locate Marks;”
U.S. publication no. 2009-0204625-A1, published Aug. 13, 2009, filed Feb. 5, 2009, and entitled “Electronic Manifest of Underground Facility Locate Operation;”
U.S. publication no. 2009-0204466-A1, published Aug. 13, 2009, filed Sep. 4, 2008, and entitled “Ticket Approval System For and Method of Performing Quality Control In Field Service Applications;”
U.S. publication no. 2009-0207019-A1, published Aug. 20, 2009, filed Apr. 30, 2009, and entitled “Ticket Approval System For and Method of Performing Quality Control In Field Service Applications;”
U.S. publication no. 2009-0210284-A1, published Aug. 20, 2009, filed Apr. 30, 2009, and entitled “Ticket Approval System For and Method of Performing Quality Control In Field Service Applications;”
U.S. publication no. 2009-0210297-A1, published Aug. 20, 2009, filed Apr. 30, 2009, and entitled “Ticket Approval System For and Method of Performing Quality Control In Field Service Applications;”
U.S. publication no. 2009-0210298-A1, published Aug. 20, 2009, filed Apr. 30, 2009, and entitled “Ticket Approval System For and Method of Performing Quality Control In Field Service Applications;”
U.S. publication no. 2009-0210285-A1, published Aug. 20, 2009, filed Apr. 30, 2009, and entitled “Ticket Approval System For and Method of Performing Quality Control In Field Service Applications;”
U.S. publication no. 2009-0324815-A1, published Dec. 31, 2009, filed Apr. 24, 2009, and entitled “Marking Apparatus and Marking Methods Using Marking Dispenser with Machine-Readable ID Mechanism;”
U.S. publication no. 2010-0006667-A1, published Jan. 14, 2010, filed Apr. 24, 2009, and entitled, “Marker Detection Mechanisms for use in Marking Devices And Methods of Using Same;”
U.S. publication no. 2009-0204238-A1, published Aug. 13, 2009, filed Feb. 2, 2009, and entitled “Electronically Controlled Marking Apparatus and Methods;”
U.S. publication no. 2009-0208642-A1, published Aug. 20, 2009, filed Feb. 2, 2009, and entitled “Marking Apparatus and Methods For Creating an Electronic Record of Marking Operations;”
U.S. publication no. 2009-0210098-A1, published Aug. 20, 2009, filed Feb. 2, 2009, and entitled “Marking Apparatus and Methods For Creating an Electronic Record of Marking Apparatus Operations;”
U.S. publication no. 2009-0201178-A1, published Aug. 13, 2009, filed Feb. 2, 2009, and entitled “Methods For Evaluating Operation of Marking Apparatus;”
U.S. publication no. 2009-0238417-A1, published Sep. 24, 2009, filed Feb. 6, 2009, and entitled “Virtual White Lines for Indicating Planned Excavation Sites on Electronic Images;”
U.S. publication no. 2009-0202112-A1, published Aug. 13, 2009, filed Feb. 11, 2009, and entitled “Searchable Electronic Records of Underground Facility Locate Marking Operations;”
U.S. publication no. 2009-0204614-A1, published Aug. 13, 2009, filed Feb. 11, 2009, and entitled “Searchable Electronic Records of Underground Facility Locate Marking Operations;”
U.S. publication no. 2009-0327024-A1, published Dec. 31, 2009, filed Jun. 26, 2009, and entitled “Methods and Apparatus for Quality Assessment of a Field Service Operation;”
U.S. publication no. 2010-0010862-A1, published Jan. 14, 2010, filed Aug. 7, 2009, and entitled, “Methods and Apparatus for Quality Assessment of a Field Service Operation Based on Geographic Information;”
U.S. publication No. 2010-0010863-A1, published Jan. 14, 2010, filed Aug. 7, 2009, and entitled, “Methods and Apparatus for Quality Assessment of a Field Service Operation Based on Multiple Scoring Categories;” and
U.S. publication no. 2010-0010882-A1, published Jan. 14, 2010, filed Aug. 7, 2009, and entitled, “Methods and Apparatus for Quality Assessment of a Field Service Operation Based on Dynamic Assessment Parameters.”
It should be appreciated that all combinations of the foregoing concepts and additional concepts discussed in greater detail below (provided such concepts are not mutually inconsistent) are contemplated as being part of the inventive subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the inventive subject matter disclosed herein. It should also be appreciated that terminology explicitly employed herein that also may appear in any disclosure incorporated by reference should be accorded a meaning most consistent with the particular concepts disclosed herein.
The present disclosure, both as to its organization and manner of operation, together with further objectives and advantages, may be best understood by reference to the following description, taken in connection with the accompanying drawings as set forth below. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of various inventive embodiments.
Various embodiments of the present invention relate to a management system, and associated methods and apparatus, for providing increased visibility, improved quality control, proof of compliance and/or significant audit capability for underground facility locate operations. In various aspects described in detail herein, such systems, methods and apparatus in some instances employ improved instrumentation for performing locate operations to facilitate data acquisition, storage and analysis, as well as an improved communication infrastructure amongst various parties/entities with interest in, or otherwise related to, locate operations. Example of such parties/entities include, but are not limited to, excavators, property owners, municipalities, facility owners, locate contractors, regulatory authorities, industry associations (e.g., industry consortia or alliances), insurance companies, damage investigators (assessors/adjustors), and auditors.
In particular, facilities locate management systems and associated methods and apparatus according to various embodiments disclosed herein provide communication infrastructure, software applications and computing devices, and various instruments for providing oversight and quality control across substantially the full scope of the underground facility locate process. Methods and apparatus disclosed herein encompass a broad management process associated with locate operations, which process may include, but is not limited to, one or more of: 1) submission of locate requests to a one-call center; 2) generation of locate request tickets (“tickets”) based on locate requests, and transmission of such tickets to various parties (locate contractors/service providers, utility owners, municipalities overseeing locate operations in their jurisdiction, technicians in the field, etc.); 3) assessment of locate request tickets to appropriately allocate technician resources; 4) dispatching of technicians to perform locate operations pursuant to tickets; 5) provision of process guides and/or locally displayed information to facilitate technician performance of operations; 6) acquisition of various information in connection with performance of locate operations (and providing such information in conjunction with, or as part of, a “completed” ticket); 7) quality assessment of operations (e.g., by processing “completed” tickets); 8) archiving of information relating to the locate operations and/or assessment of same; and 9) communication of relevant information to one or more parties associated with the operations (e.g., apprising parties requesting locate operations of the status of operations and/or various information germane to performance). In various exemplary implementations, one or more steps of the management process utilize automated applications and instruments for electronically documenting the work performed, processing and/or analyzing the electronic information, and verifying the work performed in underground facility locate operations.
Following below are more detailed descriptions of various concepts related to, and embodiments of, inventive systems, methods and apparatus for managing locate operations. It should be appreciated that various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways, as the disclosed concepts are not limited to any particular manner of implementation. Examples of specific implementations and applications are provided primarily for illustrative purposes.
I. Overview
In general, as shown in
In order to connect to network 126, each element/entity of or communicating with facilities locate management system 100 includes one or more communication interfaces to provide a communication link to and from each entity. For example, a communication interface 128 of central server 110, a communication interface 130 of image server 112, a communication interface 132 of facilities maps server 114, a communication interface 134 of one-call center 116, a communication interface 136 of excavator device 118, a communication interface 138 of marking device 120, a communication interface 139 of locate device 119, a communication interface 140 of locate personnel device 122, and a communication interface 142 of onsite computer 124 may be used in order to provide connectivity to network 126.
Communication interfaces 128, 130, 132, 134, 136, 138, 139, 140, and 142 may be any wired and/or wireless communication interfaces by which information may be exchanged between any entities of facilities locate management system 100. Example wired communication interfaces may include, but are not limited to, USB ports, RS232 connectors, RJ45 connectors, Ethernet, and any combinations thereof. Example wireless communication interfaces may include, but are not limited to, Bluetooth® technology, Wi-Fi, Wi-Max, IEEE 802.11 technology, radio frequency (RF), LAN, WAN, Internet, shared wireless access protocol (SWAP), Infrared Data Association (IrDA) compatible protocols and other types of wireless networking protocols, and any combinations thereof.
As also shown in
Facilities locate management system 100 is not limited to the applications and instruments shown in
Before providing additional details of respective elements/entities of, or in communication with, the facilities locate management system 100 shown in
In the method outlined in
At step 712, a locate request ticket that includes a VWL image and/or information relating to a VWL image (e.g., metadata for one or more dig area indicators), and/or a project ticket that includes a series of VWL images and/or information relating to the images, is generated by the one-call center 116 and transmitted from the one-call center to a party referred to herein as a “ticket recipient.” Examples of ticket recipients include, but are not limited to, one or more locate companies/locate service providers, facility owners (responsible for their own locate operations), and municipalities (also responsible for their own locate operations). For example, in one embodiment, with reference again to
At step 714, one or more applications executing on the central server 110 of the ticket recipient may process incoming tickets to assess various aspects of the requested locate operation (e.g., work scope, risk, complexity, etc.), may consult various information relating to available technician resources (e.g., shift information, technician skill set and history, certification, security clearance, etc.), and may allocate, schedule, and appropriately dispatch one or more technicians to perform a locate operation pursuant to the received ticket. Dispatched technicians may be provided with “ticket information,” e.g., various relevant information derived from the received locate request ticket to facilitate performance of the locate operation, upon dispatch, during travel to a work site, upon arrival to the work site, and/or upon use of locating equipment.
At step 716, the locate technician that was dispatched in step 714 arrives at the work site/dig area indicated in the ticket information.
At step 718, the locate technician performs the locate operation at the work site/dig area according to the ticket information. As noted earlier, it should be appreciated that during a given locate operation, underground facilities may or may not be found at the dig area, but that given either a presence or absence of facilities, the performance of the locate operation, including an inspection of the dig area, may be verified as completed by the locate technician. To this end, at step 720, and also with reference again to
At decision step 722, it is determined whether the completed ticket of the current locate operation is to be subjected to a quality assessment process, which may be performed at least in part, for example, at the central server of the ticket recipient. If the completed ticket is to undergo a quality assessment process, method 700 may proceed to step 724; if not, method 700 may proceed to the end.
At step 724, with reference again to
At step 726, the completed ticket of the current locate operation is classified as “approved.” In this way, the quality of the locate operation may be certified. While not shown explicitly in
It should be appreciated that while the method 700 provides one exemplary process for managing a locate operation according to the present invention, the underlying functionalities encompassed by the method 700 may be performed by any of the various entities shown in
Additionally, as noted above, the one-call center, excavator, or some entity other than the locate company may operate/oversee the central server 110 or a server with similar functionalities, such that various functions attributed above to the central server 110 may instead be performed/managed by the one-call center, excavator, or other entity. For example, in one exemplary implementation, the one-call center (or other entity) may receive information from a locate technician or locate company regarding the performance of a locate operation and the presence or absence of underground facilities, and the one-call center itself may generate an EM image of the locate operation based on this received information, provide relevant non-image data with the image data, and mark a locate request ticket as completed. Furthermore, the one-call center (or other entity) may perform/manage a ticket approval process for ensuring compliance of the locate operation with a predetermined quality standard, and then store and/or transmit approved completed locate request tickets as searchable electronic records.
Having generally outlined a method of managing locate operations according to various embodiments of the present invention, additional details of the various elements/entities illustrated in
I. Excavators/Requesting Parties
With reference again to
As noted above, an excavator or other requesting party generally submits a locate request to a one-call center. When a locate request is submitted by an excavator 154 to a one-call center, such as one-call center 116, it may be beneficial for the excavator to indicate the particular geographic location of the proposed excavation in a permanent and reproducible manner. The dig area thusly identified indicates to a locate technician the extent of the boundaries where a locate operation is to be performed at the request of the excavator. Physical white lines, that may include chalk or paint on the surface of the ground, may be used to physically delimit a dig area. However, these physical white lines provide only a temporary indication of the dig area, as physical white lines may deteriorate or be eliminated over time by certain events such as precipitation, excessive pedestrian or vehicle traffic, erosion, the excavation process, or numerous other events. Consequently, each excavator 154 may utilize an excavator device 118 that has a “virtual white line” (VWL) application 156 installed thereon.
Excavator device 118 may be a computing device, such as portable computer, a personal computer, a general purpose computer, a tablet device, a personal digital assistant (PDA), a cellular radiotelephone, a mobile computing device, a touch-screen device, a touchpad device, or generally any device including, or connected to, a processor and a display. Preferably, excavator device 118 is a portable computing device, such as laptop computer or tablet device.
VWL application 156 that resides on excavator device 118 may be a drawing application, which, in excavation applications, may be used by the excavator 154 as a dig area marking tool. More specifically, VWL application 156 may be used by the excavator 154 to add markings to a displayed input image (e.g., which input image may be represented by source data 150 retrieved from image server 112 or facilities maps server 114) to indicate the dig area, thereby creating a marked-up image. For example, VWL application 156 may be used in order to superimpose over or otherwise display one or more dig area indicators on the digital image to indicate the dig area. As used herein, a “dig area indicator” may include one or more lines, drawing shapes, shades, points, symbols, coordinates, data sets, or other indicators to indicate or delimit on a digital image the dig area in which excavation is planned.
A local image cache 178 of excavator device 118 may be used to store, for example, source data 150 from image server 112 and/or from central server 110 (discussed in further detail below). Source data 150 may be used by VWL application 156 to display one or more input images that may be marked up (e.g., with a dig area indicator 180) to indicate a dig area and thereby create VWL image 170, which may also be stored in local image cache 178.
In one example, one or more dig area indicators 180 that are placed upon the displayed input image represented by source data 150 may be dotted or dashed lines (e.g., rendered in the color white) as shown in
II. Image Server
With reference again to
For purposes of the present disclosure, an input image is any image represented by source data 150 that may be electronically processed (e.g., the source data is in a computer-readable format) to display the image on a display device. An input image may include any of a variety of paper/tangible image sources that are scanned (e.g., via an electronic scanner) or otherwise converted so as to create source data (e.g., in various formats such as XML, PDF, JPG, BMP, etc.) that can be processed to display the input image. An input image also may include an image that originates as source data or an electronic file without necessarily having a corresponding paper/tangible copy of the image (e.g., an image of a “real-world” scene acquired by a digital still frame or video camera or other image acquisition device, in which the source data, at least in part, represents pixel information from the image acquisition device).
In some exemplary implementations, input images according to the present disclosure may be created, provided, and/or processed by a geographic information system (GIS) that captures, stores, analyzes, manages and presents data referring to (or linked to) location, such that the source data representing the input image includes pixel information from an image acquisition device (corresponding to an acquired “real world” scene or representation thereof), and/or spatial/geographic information (“geo-encoded information”). In this manner, a GIS provides a framework for data manipulation and display of images that may facilitate one or more of (a) location verification, (b) location correlation, (c) locational relationships, (d) district coding, (e) route analysis, (f) area analysis and (g) mapping/display creation, for example.
In view of the foregoing, various examples of input images and source data 150 representing input images according to the present disclosure, to which the inventive concepts disclosed herein may be applied, include but are not limited to:
It should also be appreciated that source data 150 representing an input image may be compiled from multiple data/information sources; for example, any two or more of the examples provided above for input images and source data representing input images, or any two or more other data sources, can provide information that can be combined or integrated to form source data that is electronically processed to display an image on a display device.
Image server 112 may be associated with the same, or a different, party that maintains central server 110. For example, image server 112 may be associated with a party that provides source data 150 for a fee. As noted above, source data 150 from image server 112 may include geo-coding or other geographical identification metadata and may be provided in any computer-readable format, such as JPEG file interchange format (JPEG), tagged image file format (TIFF), portable document format (PDF), graphics interchange format (GIF), bitmap (BMP), portable network graphics (PNG), Windows® metafile (WMF), and/or the like. In addition, source data 150 from image server 112 may include a combination of images or overlays, such as overlays of street names, regions, landmark descriptions, and/or other information about areas displayed in an image. Source data 150 from image server 112 may be supplied by a third-party provider if the coverage area of the third-party image provider overlaps with the desired area of the user.
III. Facilities Maps Server
As noted above, the source data 150 provided by image server 112 may encompass data representing facility maps. However, in some implementations a dedicated server, such as facilities maps server 114, may be included in the management system 100 shown in
Facilities maps 152 are any electronic representation of the geographic location, type, number, and/or other attributes of a facility or facilities. Facilities maps may be supplied by various facility owners and may indicate the geographic location of the facility lines (e.g., pipes, cables, and the like) owned and/or operated by the facility owner. For example, facilities maps may be supplied by the owner of the gas facilities, power facilities, telecommunications facilities, water and sewer facilities, and so on.
Facilities maps may be provided in any of a variety of different formats. As facilities maps often are provided by facility owners of a given type of facility, typically a set of facilities maps includes a group of maps covering a particular geographic region and directed to showing a particular type of facility disposed/deployed throughout the geographic region. One facilities map of such a set of maps is sometimes referred to in the relevant arts as a “plat.”
An electronic facilities map may in some instances simply be an electronic conversion (i.e., a scan) of a paper facilities map that includes no other information (e.g., electronic information) describing the content of the map, other than what is printed on the paper maps. Alternatively, however, more sophisticated facilities maps also are available which include a variety of electronic information, including geographic information and other detailed information, regarding the contents of various features included in the maps. In particular, facilities maps may be formatted as geographic information system (GIS) map data, in which map features (e.g., facility lines and other features) are represented as shapes and/or lines, and the metadata that describes the geographic locations and types of map features is associated with the map features. In some examples, a GIS map data may indicate a facility line using a straight line (or series of straight lines), and may include some symbol or other annotation (e.g., a diamond shape) at each endpoint of the line to indicate where the line begins and terminates. From the foregoing, it should be appreciated that in some instances in which the geo-locations of two termination or end-points of a given facility line may be provided by the map, the geo-location of any point on the facility line may be determined from these two end-points.
Examples of a wide variety of environmental landmarks and other features that may be represented in GIS facilities map data include, but are not limited to: landmarks relating to facilities such as pedestal boxes, utility poles, fire hydrants, manhole covers and the like; one or more architectural elements (e.g., buildings); and/or one or more traffic infrastructure elements (e.g., streets, intersections, curbs, ramps, bridges, tunnels, etc.). GIS facilities map data may also include various shapes or symbols indicating different environmental landmarks relating to facilities, architectural elements, and/or traffic infrastructure elements.
Examples of information provided by metadata include, but are not limited to, information about the geo-location of various points along a given line, the termination points of a given line (e.g., the diamond shapes indicating the start and end of the line), the type of facility line (e.g., facility type and whether the line is a service line or main), geo-location of various shapes and/or symbols for other features represented in the map (environmental landmarks relating to facilities, architectural elements, and/or traffic infrastructure elements), and type information relating to shapes and/or symbols for such other features.
The GIS map data and metadata may be stored in any of a variety of ways. For example, in some embodiments, the GIS map data and metadata may be organized into files, where each file includes the map data and metadata for a particular geographic region. In other embodiments, the GIS map data and metadata may be stored in database and may be indexed in the database by the geographical region to which the map data and metadata corresponds.
Facilities maps may include additional information that may be useful to facilitate a locate and/or marking operation. For example, various information that may be included in a legend of the facilities map, or otherwise associated with the facilities map (e.g., included in the metadata or otherwise represented on the map), may include, but is not limited to, a date of the facilities map (e.g., when the map was first generated/created, and/or additional dates corresponding to updates/revisions), a number of revisions to the facilities map (e.g., revision number, which may in some instances be associated with a date), one or more identifiers for a source, creator, owner and/or custodian of the facilities map (e.g., the owner of the facility type represented in the map), various text information (e.g., annotations to update one or more aspects or elements of the map), and any other legend information that may be included or represented in the map.
For facilities maps in electronic form, a variety of digital formats of facilities maps may be used including, but not limited to, a vector image format that is the typical output format of computer-aided design (CAD) tools. In one example, some facilities maps may be in a DWG (“drawing”) format, which is a format that used for storing two and three dimensional design data and metadata, and is a native used by several CAD packages including AutoCAD, Intellicad, and PowerCAD. However, those skilled in the art will recognize that facilities maps may be in any of several vector and/or raster image formats, such as, but not limited to, DWG, DWF, DGN, PDF, TIFF, MFI, PMF, and JPG.
As noted above, in some instances in which facilities maps are in a vector image format, a certain line on the facilities map may be represented by a starting point geo-location, an ending point geo-location, and metadata about the line (e.g., type of line, depth of line, width of line, distance of line from a reference point (i.e., tie-down), overhead, underground, line specifications, etc.). According to one embodiment of the present invention as discussed in greater detail below, to facilitate display of facilities map information relating to multiple different types of facilities, each vector image may be assembled in layers, in which respective layers correspond, for example, to different types of facilities (e.g., gas, water, electric, telecommunications, etc.). In one aspect of such an embodiment, each layer is, for example, a set of vector images that are grouped together in order to render the representation of the certain type of facility.
IV. One-Call Centers
With reference again to
When optional VWL application 158 is present at one-call center 116, one-call center 116 may additionally include a local image cache 176. Stored in local image cache 176 may be, for example, certain source data 150 from image server 112 and/or from central server 110. Source data 150 may be used by VWL application 158 as the input image(s) that may be marked up in order to create VWL images 170, which may also be stored in local image cache 176, that show in a graphical (or other) manner the dig area.
V. Central Server
With reference again to
In some implementations, the central server 110 essentially serves as the “heart” of the facilities locate management system 100 shown in
An image cache 166 may reside at data store 144. Image cache 166 may be used to store cached images, such as cached source data 150 from image server 112, and the like. For example, the cached source data 150 of image cache 166 may be used by certain applications of facilities locate management system 100, such as, but not limited to, ticket approval application 146, VWL applications 156 or 158, and EM application 164. Additionally, any collection of facilities maps 152 or facilities map information from facilities maps server 114 may reside at data store 144. Additionally, a collection of locate request tickets 168B that are generated by and received from one-call center 116 may reside at data store 144. As discussed above, each locate request ticket 168B may include a VWL image 170 and/or image information relating to the contents of a VWL image.
The central server 110 may also be configured to execute a workforce management application 145, which may have various components to facilitate assessment and/or processing of locate request tickets 168B, dispatching of technicians (locate personnel 160) to perform locate operations pursuant to locate request tickets, and/or provide various notifications (“positive response notifications”) to requesting parties or other parties regarding the status of locate operations and/or various information attendant thereto.
For example, in one implementation, the workforce management application 145 may include a ticket assessment and/or processing component 145A. In exemplary aspects, the ticket assessment and/or processing component 145A may parse received tickets to extract relevant information, and/or perform a comprehensive assessment process based on information extracted from the ticket (i.e., “ticket information”), to facilitate efficient scheduling of locate activities and appropriate allocation of technician resources to locate operations. In other aspects, the ticket assessment and/or processing component 145A may review received tickets to establish the integrity, accuracy, and/or completeness of ticket information in connection with specified location of planned excavation, and provide assessments relating to scope of work (amount and nature of work), complexity involved, duration (amount of time required), risk (potential liability for damages), business value (penalty and/or profitability), and skill/certification requirements for technicians in performing the operation. Additional details of the ticket assessment and/or processing component 145A are discussed in U.S. provisional patent application No. 61/220,491, filed Jun. 25, 2009, entitled, “Methods and Apparatus for Assessing Field Service Operation Tickets,” which application is hereby incorporated herein by reference.
As shown in
In yet another aspect of the workforce management application 145 of the central server 110 shown in
In one exemplary implementation, pursuant to execution at the central server 110 of the ticket assessment/processing component 145A, a process guide in the form of a checklist may be generated (e.g., based at least in part on the ticket information), for example at the central server 110 and then downloaded to the locating equipment (e.g., locate device 119 and/or marking device 120 shown in
As discussed further below, once a technician is dispatched, arrives at a work site, and perform a locate operation, a wide variety of information may be available and acquired to electronically document performance of the operation, as well as environmental and other information germane to the locate operation, the technician, and/or the work site. Performance of a locate operation typically is associated with a “completed” ticket, wherein a technician provides some electronic communication or indication that the locate operation was at least attempted, if not completed pursuant to the locate request ticket. As discussed above, for purposes of the present disclosure, a “completed” electronic locate request ticket refers to an electronic communication generated by a technician indicating that a locate operation has been attempted or performed, at least to some extent. Accordingly, it should be appreciated that a “completed” ticket does not necessarily imply that a locate operation itself was successfully performed in its entirety (as dictated by one or more locate request tickets), but that it was at least initiated and attempted in some fashion. For example, a technician may be dispatched to a work site, may begin performing a locate operation, and may encounter some unforeseen impediment to completing the operation, or some condition or circumstance that warrants special action or attention. Accordingly, the technician may generate a “completed” ticket that reflects the attempted operation but in some manner reflects the anomalous situation attendant to the attempted locate operation.
With reference again to
More specifically, an EM image 174 may show the original dig area indicator(s) from the original VWL image 170. Additionally, the EM image 174 may show one or more types of facilities, the presence of which have been determined (detected and/or marked) during the locate operation. Each facility type may be graphically represented with a certain color line in EM image 174; as discussed above, in some implementations such a line represents where a presence of a facility was detected (e.g., electronic detection marks) and/or where physical locate marks were applied to the dig area to indicate the presence of the facility (e.g., electronic locate marks). Additionally, the EM image 174 may show one or more environmental landmarks. An environmental landmark may be any location specified by any means that is used or can be used as a reference point for measurement or orientation. Examples of an environmental landmark may include, but are not limited to, a tree, a curb, a driveway, a utility pole, a fire hydrant, a storm drain, a pedestal, a water meter box, a manhole lid, a building structure, a light post, or a set of global positioning system coordinates. An example of an EM image 174 is shown with reference to
As also noted above, in some implementations an EM image 174 need not include one or more dig area indicators previously placed on an input image by an excavator, other requesting party, or one-call center to indicate a dig area, but may merely include one or more electronic detection marks and/or electronic locate marks to digitally represent the presence of an underground facility. Also, as noted above, in some completed tickets an EM image 174 may have no markings on it at all, and nonetheless be useful for documenting a “clear” locate operation in which no underground facilities were found.
In sum, with respect to completed locate request tickets 172, a completed ticket may include one or both of image data and non-image data associated with the dig area. The image data may include at least one image of a geographic area including the dig area, wherein the image(s) may not be marked-up at all (e.g., in the case of a “clear”), or the image(s) may be marked-up images including one or more dig area indicators (e.g., virtual white lines) to provide an indication of the dig area, and/or one or more electronic detection marks and/or electronic locate marks to indicate a presence (or in some cases an absence) of one or more underground facilities. Examples of non-image data that may be included in or otherwise associated with the completed locate request ticket may include, but are not limited to, one or more of the following: a text description of the dig area; a plurality of geographic coordinates associated with one or more dig area indicators and/or one or more electronic detection marks or electronic locate mark indicators; an address or a lot number of at least one property within which the dig area is located; a street intersection in a vicinity of the dig area; a date and/or time of day for an excavation of the dig area; a first identifier associated with an excavator to perform the excavation activities; a second identifier associated with at least one environmental landmark in the vicinity of the dig area; a ticket identifier for the locate request ticket; a timestamp to indicate when a locate operation was performed; one or more identifiers (e.g., name, ID number, phone number, address, signature, etc.) for a locate technician, a locate company, and/or a utility associated with one or more underground facilities. The image data and the non-image data may be formatted in any of a number of ways; for example, the non-image data may be associated with the image data as a separate data set linked to the image data, as metadata to the image data, as some other type of combined file including both image and non-image data, etc., so as to create a searchable electronic record that may be consulted to verify that the locate operation was indeed completed, and assess the integrity (e.g., quality, timeliness, accuracy, etc.) of the locate operation.
To this end, the central server 110 shown in
In some implementations, ticket approval application 146 may use and share the information of each completed ticket 172 that has an EM image 174 in order to rapidly access the quality of the work performed in the field. This assessment may be by visual inspection of each completed ticket 172 by one or more approvers 148 and/or by processing the information contained in a completed ticket to assess compliance with a predetermined quality standard for the locate operation. For example, in one implementation, the information of each completed ticket 172 that has an EM image 174 may be analyzed by comparing the EM image against one or more facilities maps 152 or facilities map information that correspond to the geographic location associated with the completed ticket 172.
Thus, ticket approval application 146 provides for quality control and/or assessment of compliance functions (e.g., compliance with a predetermined quality standard for the locate operation). In exemplary implementations, the ticket approval process may comprise obtaining a field service ticket, performing a task according to the field service ticket, collecting data associated with the field service ticket and transmitting the data to a work management server that includes a database and approval applications for processing and analyzing information contained in the ticket and assessing compliance with a predetermined quality standard. In yet other aspects of the ticket approval application 146, completed tickets may be reviewed, in essentially real-time during performance of a locate operation, and/or at any time following attempt/completion of a locate operation, to provide a quality assessment of the locate operation (e.g., an assessment of the completeness, accuracy, and/or efficiency of the operation).
In sum, quality assessment processes according to various embodiments, as facilitated by the ticket approval application 146, may be primarily under the discretion of a human reviewer, albeit facilitated in some respects by computer-aided display of information, and electronic record keeping and communication functions associated with the quality assessment result(s). In other embodiments, information related to a locate operation (e.g., electronic manifest information accompanying or constituting a completed ticket) is electronically analyzed such that a quality assessment is based at least in part on some predetermined criteria and/or metrics that facilitate an automated determination of quality assessment. In one aspect, if the locate operation represented by the completed ticket complies with a predetermined quality standard (e.g., based on predetermined criteria and/or metrics), the locate operation may be “approved” (e.g., a quality assessment process/engine may generate an “approved completed locate request ticket”). In another aspect, real-time quality assessment during performance of a locate operation may facilitate identification of risks or problems that may be flagged for proactive corrective action (e.g., immediately, or as soon as practicable).
Additional details regarding the ticket approval application 146 and execution of same by the central server are described in the following applications, each of which is incorporated herein by reference: U.S. patent application Ser. No. 12/493,109, filed on Jun. 26, 2009, entitled “Methods and Apparatus for Quality Assessment of a Field Service Operation;” U.S. patent application Ser. No. 12/557,732, filed on Aug. 7, 2009, entitled “Methods and Apparatus for Quality Assessment of a Field Service Operation Based on Geographic Information;” U.S. patent application Ser. No. 12/571,356, filed on Sep. 30, 2009, entitled “Methods and Apparatus for Analyzing Locate and Marking Operations with Respect to Facilities Maps;” U.S. patent application Ser. No. 12/572,202, filed on Oct. 1, 2009, entitled “Methods and Apparatus for Analyzing Locate and Marking Operations with Respect to Historical Information;” U.S. patent application Ser. No. 12/568,087, filed on Sep. 28, 2009, entitled “Methods and Apparatus for Generating an Electronic Record of Environmental Landmarks Based on Marking Device Actuations;” and U.S. patent application Ser. No. 12/572,260, filed on Oct. 1, 2009, entitled “Methods and Apparatus for Analyzing Locate and Marking Operations with Respect to Environmental Landmarks.”
For example, in accordance with various embodiments described in above-referenced applications, a quality assessment of a locate operation may be performed based on the collected locating equipment data (which may or may not form part of an EM image or the date underlying same), with or without human input. In some embodiments, the collected locating equipment data may be compared to “reference information” or “reference data” (which in some instances is derived from information/data contained in a “reference” electronic record). Examples of types of reference information/data used in a quality assessment process may include, but are not limited to: 1) information/data derived from or relating to one or more facilities maps that illustrate the presumed locations of underground facilities purportedly present in a geographic area proximate to or surrounding and subsuming the work site; 2) information/data derived from or relating to one or more previous locate and/or marking operations at or near the work site (referred to herein as “historical tickets” or “historical data”); and/or 3) information/data relating to one or more environmental landmarks present in a geographic area proximate to or surrounding and subsuming the dig area (e.g., the work site and its environs), or within the dig area itself (referred to herein as “landmark information,” which may be available, for example, from facilities maps, historical tickets, and/or field data collected at or around the time of the locate and/or marking operation being assessed). For each type of reference information, suitable criteria and/or metrics may be developed to facilitate an automated determination of quality assessment.
In yet other aspects, various quality assessment functions may be implemented in a centralized or distributed fashion. For example, in one implementation, alternatively to or in addition to the central server 110 receiving and analyzing completed tickets, other computing device(s) operated by a locate service provider or other entity may collect relevant information from the field relating to locate operations and perform quality assessments of same. In some implementations discussed in further detail below, intelligent locating equipment may be configured to perform some degree of quality assessment local to the work site; for example, intelligent locating equipment may be configured to acquire information about the locate operation and its environs, compare elements of acquired information to various criteria relating to functionality and/or use of the locating equipment, and/or one or more environmental conditions proximate to the locating equipment and/or work site in which it is being used, and provide one or more local alerts (e.g., visual, audible, and/or tactile indications) to a technician to indicate any detected out-of-tolerance conditions. Such locally detected conditions also may be transmitted by intelligent locating equipment to one or more other pieces of intelligent locate equipment in the area, and or one or more remote computing devices, for further and/or corroborative quality assessment or other analysis. In this fashion, a host of quality assessment functionality may be facilitated at various organizational levels, and/or amongst multiple distributed computing resources.
In other aspects, any information acquired in connection with the locate operation (e.g., electronic records acquired by intelligent locating equipment, electronic manifests), as well as quality assessment results, may be archived (e.g., in a database and/or central data store, e.g. data store 144 of central server 110, or memory 956 of ASP server 950 in
In yet other embodiments, the workforce management application 145 of the central server 100 may include a positive response notification component 145C. Via execution of this component, at one or more points during the processes discussed above, one or more “positive response” notifications indicating a status of the locate operation and/or disposition of the technician, and/or more detailed information about the progress of the locate operation, may be electronically transmitted and/or stored so as to inform at least one party associated with requesting the operation of the status of the operation and/or details thereof. In one aspect, a requesting party may designate a particular format, content, and/or method of receiving notifications regarding the locate operation. In another aspect, the central server, via execution of the positive response notification component 145C, may generate and send to a one-call center, and/or an excavator device (or any portal, such as a web page made available to a requesting part) a computer-generated GUI may be provided to facilitate submission of locate requests, generation of image information to indicate one or more dig areas on a digital image of a work site as part of a locate request, and/or selection of notifications and preferences for same. In yet another aspect, a requesting party may provide an acknowledgement of receipt (e.g., a “return receipt”) for one or more received notifications. Additional details of the positive response notification component are discussed in U.S. non-provisional application Ser. No. 12/703,313, filed on Feb. 10, 2010, entitled “Methods, Apparatus, and Systems for Exchanging Information Between Excavators and Other Entities Associated with Underground Facility Locate and Marking Operations,” which application is hereby incorporated by reference herein.
VI. Locate Personnel and Locating Equipment
Multiple locate personnel 160 may be associated with facilities locate management system 100. Locate personnel 160 may be, for example, locate technicians and/or quality control technicians. Each locate personnel 160 may utilize a locate device 119, a marking device 120, and/or a combined locate and marking device (not shown), in combination with a locate personnel device 122 that has an electronic manifest (EM) application 164 installed thereon. As discussed above, in some exemplary implementations, conventional locate devices and conventional marking devices may be employed, and the creation of an electronic manifest via the electronic manifest application 164 may be an essentially manual process performed by the technician as part of completing a ticket. In yet other implementations, intelligent locating equipment, e.g., one or more of a locate device 119, a marking device 120, or a combined locate and marking device, which have a variety of data acquisition, processing and storage functionality, may be employed by the technician to perform a locate operation. In this manner, the intelligent locating equipment itself may provide a host of information relating to the locate operation that can be used to facilitate automated or semi-automated generation of an electronic manifest, and/or provide one or more electronic records of valuable information that may be included in and/or accompany a completed ticket. Examples of intelligent locating equipment that may be employed in connection with various embodiments of the facilities locate management system described herein are discussed in U.S. non-provisional application Ser. No. 12/569,192, filed Sep. 29, 2009, entitled “Methods, Apparatus, and Systems for Generating Electronic Records of Locate and Marking Operations, and Combined Locate and Marking Apparatus for Same,” which application is incorporated herein by reference.
A. Locate Devices
As discussed above in connection with
In one embodiment, the locate device 119 may be an intelligent locate device, as illustrated in
Locate device 119 further includes one or more input devices 183, which may be any devices that are capable of returning useful information with respect to an underground facility location application. By way of example, input devices 183 may include, but are not limited to, a timing system (e.g., for generating a timestamp), a location tracking system (e.g., GPS technology), an underground probe (e.g., for capturing accurate facility location data by traversing the underground facility), survey apparatus, a temperature sensor, a humidity sensor, a light sensor, a compass, an inclinometer, an accelerometer, a digital camera, an audio recorder, an illumination source, and one or more receiver antenna 185 to facilitate detection of magnetic fields generated by underground facilities. Locate device 119 may also include control software (e.g., stored in the memory) for managing the overall operations of the locate device 119. Additionally, the locate device may include any device-specific control software or electronics for managing input devices 183 and/or processing information from input devices 183.
The information that is returned from input devices 183, also referred to as “locate information,” may be processed and/or otherwise analyzed by use of locate data algorithm 169, and/or transmitted to the central server 110 via the network 126 for processing, analysis, and/or storage. In particular, locate data algorithm 169 may use the locate information acquired from input devices 183 for analyzing locate operations and creating an electronic record, in some instances in order to render a recreation of the locate operation. In one exemplary implementation, the processing unit of the locate device, executing the locate data algorithm, may generate locate information relating to the geographic location of detected facilities, and this location information may be in turn conveyed to other entities of the management system (e.g., to the locate personnel device 122) via the communication interface 139 of the locate device and the communication interface associated with the entity (e.g., the communication interface 140). Additional details of an intelligent locate device are described in U.S. non-provisional application Ser. No. 12/704,087, filed Feb. 11, 2010, entitled “Locate Apparatus having Enhanced Features for Underground Facility Locate Operations, and Associated Methods and Systems,” which application is hereby incorporated by reference herein.
B. Marking Devices
As discussed above in connection with
In one embodiment, the marking device 120 is an intelligent marking device, in that it may be a global positioning system (GPS)-enabled electronic marking device that includes certain mechanisms for sensing and logging the operations performed therewith during a locate operation. With reference to
Marking device 120 may be based, for example, on the marking device that is described in the following U.S. published patent applications: U.S. publication no. 2008-0228294-A1, published Sep. 18, 2008, filed Mar. 13, 2007, and entitled “Marking System and Method With Location and/or Time Tracking;” and U.S. publication no. 2008-0245299-A1, published Oct. 9, 2008, filed Apr. 4, 2007, and entitled “Marking System and Method.” In an alternative embodiment, the separate marking and locate devices (e.g., locate device 119 and marking device 120) may be replaced with a combination locate and marking device, as noted above.
Marking device 120 further includes one or more input devices 182, which may be any devices that are capable of returning useful information with respect to an underground facility location application. By way of example, input devices 182 may include, but are not limited to, a timing system (e.g., for generating a timestamp), a location tracking system (e.g., GPS technology), an underground probe (e.g., for capturing accurate facility location data by traversing the underground facility), survey apparatus, a temperature sensor, a humidity sensor, a light sensor, a compass, an inclinometer, an accelerometer, a digital camera, an audio recorder, an illumination source, and a marking material detection mechanism (e.g., radio-frequency identification (RFID) technology). Marking device 120 may also include control software (e.g., stored in the memory) for managing the overall operations of marking device 120. Additionally, the marking device may include any device-specific control software or electronics for managing input devices 182 and/or processing information from input devices 182.
The information that is returned from input devices 182 of marking device 120 may be captured, for example, with each actuation of marking device 120, such as with, but not limited to, each actuation to dispense marking material from ID-enabled marker dispenser 188. The information that is returned from input devices 182, which is hereafter referred to as “marking information,” may be processed and/or otherwise analyzed by use of marking data algorithm 162. In particular, marking data algorithm 162 may use the marking information from input devices 182 for analyzing locate operations based on actuations of marking device 120 and in order to render a recreation of the locate operation. In one exemplary implementation, the processing unit of the marking device, executing the marking data algorithm, may generate marking information relating to the geographic location of locate marks that are applied to the dig area via the marker dispenser 188, and this location information may be in turn conveyed to other entities of the management system (e.g., to the locate personnel device 122) via the communication interface 138 of the marking device 120 and the communication interface associated with the entity (e.g., the communication interface 140).
Additional details of an intelligent locate device are described in U.S. non-provisional application Ser. No. 12/703,958, filed Feb. 11, 2010, entitled “Marking Apparatus having Enhanced Features for Underground Facility Marking Operations, and Associated Methods and Systems,” which application is hereby incorporated by reference herein.
C. Locate Personnel Devices
Locate personnel device 122 may be a computing device, such as portable computer, a personal computer, a tablet device, a PDA, a cellular radiotelephone, a mobile computing device, a touch-screen device, a touchpad device, or generally any device including, or connected to, a processor and a display. Preferably, locate personnel device 122 is a portable computing device, such as laptop computer, tablet device, smart phone, and the like.
As discussed above, an “Electronic Manifest” or “EM” application 164 that resides on locate personnel device 122 may be a drawing application, which, in underground facility locate operations, may be used by locate personnel 160 as a locate operation “digital” marking tool to create a searchable electronic record of a locate operation. More specifically, EM application 164 may be used by locate personnel 160 to add one or more electronic detection marks and/or electronic locate marks (generally referred to as “locate mark indicators”) to a displayed input image of the dig area in order to graphically depict (digitally represent) on the displayed image one or more detected facilities and/or physical locate marks applied to the dig area during the locate operation. In exemplary implementations, locate personnel 160 may add such locate mark indicators to the displayed image via a user input device associate with a display device displaying the image (e.g., via a stylus, keyboard, touchpad, touch-screen, mouse, etc. associated with the locate personnel device 122). EM application 164 may superimpose over or otherwise display these locate mark indicators on any of a variety of input images (e.g., received from image server 112 or facilities maps server 114), including input images that have been previously marked-up with one or more dig area indicators as discussed above. The locate mark indicators may include lines, grids, drawing shapes, shades, points, symbols, coordinates, data sets, or other indicators to graphically depict the work performed in the locate operation (i.e., the detection of one or more underground facilities and/or the physical marking of the dig area to indicate a presence or an absence of one or more underground facilities).
Alternatively, EM application 164 may read in locate information and/or marking information about the locate operation from locate device 119 and/or marking device 120 (or a combined locate and marking device), which may then be rendered into a graphical (or other) depiction of the work performed in the locate operation. More specifically, information provided by locate device 119 and/or marking device 120 to the locate personnel device 122 (e.g., via communication link 140) may include geographic information relating to a location of one or more detected facilities, and/or the applied physical locate mark(s), which is processed by EM application 164 to provide on an input image one or more locate mark indicators to digitally represent the detection and/or physical locate mark(s). Such a graphical depiction of the locate operation may be superimposed over or otherwise displayed on the input image (which, as discussed above, may have been previously marked-up with one or more dig area indicators). Additional details of locate personnel device 122 and the components thereof are described with reference to
In some locate operations, no underground facilities are determined to be present in a designated dig area. Such locate operations are sometimes referred to as “clears.” In some implementations of the inventive concepts discussed herein, the EM application 164 may nonetheless be employed to provide an electronic record of a “clear;” more specifically, although no locate mark indicators may be added to an input image (because there are no physical locate marks to digitally represent), the EM application may be employed to provide other information associated with the “clear” locate operation (e.g., a timestamp of when the locate operation was performed, an identifier for a technician or locate company performing the locate operation, a text address or other geographical identifier for the dig area, etc.) and this other information may be associated with the input image (e.g., as a separate data set linked to the input image, as metadata, a combined file of image and non-image data, etc.) to create a searchable electronic record that may be consulted to verify that the locate operation was indeed completed, even though no underground facilities were found.
In some implementations, as discussed above EM application 164 may read in locate information from locate device 119, and/or marking information from marking device 120 Subsequently, EM application 164 may superimpose over or otherwise display this information on VWL image 170.
In either case, an EM image 174 is formed that shows the original VWL image 170 and a representation of the locate operation marked thereon. Alternatively, in either case, the EM image 174 may be any input image represented by source data 150, rather than a VWL image 170, that has a representation of the locate operation marked thereon, or perhaps no locate mark indicators in the case of a “clear.”
Referring again to
VII. Application Service Provider Models
It should also be appreciated that the various functionalities described herein in connection with inventive locate operation management techniques may be implemented as an application service provider (ASP) model.
In exemplary implementations of an ASP model 900, a user/subscriber 826 may access the application tools 910 and information database(s) 920 resident on ASP server(s) 950 (including at least one processing unit 952, at least one communication interface 954, and at least one memory 956) via a website using a log-in procedure 930 to facilitate secure access to the server(s) (e.g., via user name and password, etc.). Fees 932 may be associated with access to the ASP website (e.g., on a per use, multiple use, periodic use, or other basis). Users/subscribers 826 may maintain information profiles 934 on the ASP server(s) 950 to identify themselves and/or provide preferences for access to certain applications/information database(s). The ASP also may maintain information in connection with such user/subscriber profiles relating to any selective access permissions 936 or restrictions regarding the available applications/information database(s). A user/subscriber access procedure may include information entry by a user/subscriber to provide relevant information to initiate a locate request (e.g., an excavator providing relevant information to begin a request), and also may include a search engine 938, such that the user/subscriber 826 may find relevant information based on a host of indicia associated with a locate operation for which a locate request ticket already has been generated (address of dig area, ticket numbers, excavator and/or locate company identifiers, utility company identifiers, etc.).
From the foregoing, it should be readily appreciated that the various information compiled during the locate operation management process described herein, and particularly various stages of the locate request ticket and especially an approved completed locate request ticket, may be readily generated and made readily available as searchable electronic records to significantly improve the execution of locate operations and the integrity of such operations. More specifically, a database of searchable electronic records of locate operations facilitates auditing of such records by regulators, insurance companies, utility companies, and other parties to improve quality and efficiency of locate operations.
VIII. Conclusion
With respect to providing improved visibility, quality control, audit capability and automation in underground facility locate operations and referring to
With respect to providing improved visibility, quality control, audit capability and automation in underground facility locate operations and referring to
With respect to providing improved visibility, quality control, audit capability and automation in underground facility locate operations and referring to
With respect to providing improved visibility, quality control, audit capability and automation in underground facility locate operations and referring to
In one example, with respect to providing improved visibility, quality control, audit capability and automation in underground facility locate operations and referring to
Additionally, a feature of ticket approval application 146 and/or a separate application of central server 110 may include the ability to assess locate operations with respect to historical records of facilities maps (e.g., facilities maps 152 of facilities maps server 114). In one example, the assessment of locate operations with respect to historical facilities maps may be performed.
Additionally, a feature of ticket approval application 146 and/or a separate application of central server 110 may include the ability to assess locate operations with respect to historical records of tickets (e.g., historical records of completed tickets 172 of central server 110). In one example, the assessment of locate operations with respect to historical tickets may be performed.
Additionally, a feature of ticket approval application 146 and/or a separate application of central server 110 may include the ability to assess locate operations with respect to historical records of environmental landmarks (not shown). In one example, the assessment of locate operations with respect to historical environmental landmarks may be performed.
Referring again to
Referring again to
Referring again to
While various inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.
The above-described embodiments can be implemented in any of numerous ways. For example, the embodiments may be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer or distributed among multiple computers.
Further, it should be appreciated that a computer may be embodied in any of a number of forms, such as a rack-mounted computer, a desktop computer, a laptop computer, or a tablet computer. Additionally, a computer may be embedded in a device not generally regarded as a computer but with suitable processing capabilities, including a Personal Digital Assistant (PDA), a smart phone or any other suitable portable or fixed electronic device.
Also, a computer may have one or more input and output devices. These devices can be used, among other things, to present a user interface. Examples of output devices that can be used to provide a user interface include printers or display screens for visual presentation of output and speakers or other sound generating devices for audible presentation of output. Examples of input devices that can be used for a user interface include keyboards, and pointing devices, such as mice, touch pads, and digitizing tablets. As another example, a computer may receive input information through speech recognition or in other audible format.
Such computers may be interconnected by one or more networks in any suitable form, including a local area network or a wide area network, such as an enterprise network, and intelligent network (IN) or the Internet. Such networks may be based on any suitable technology and may operate according to any suitable protocol and may include wireless networks, wired networks or fiber optic networks.
Any of the computing devices discussed herein (e.g., servers, computers, locate personnel devices, marking devices, locate devices, excavator devices, etc.) may include memory, one or more processing units (also referred to herein simply as “processors”), one or more communication interfaces, one or more display units, and one or more user input devices. The memory may comprise any computer-readable media, and may store computer instructions (also referred to herein as “processor-executable instructions”) for implementing the various functionalities described herein. The processing unit(s) may be used to execute the instructions. The communication interface(s) may be coupled to a wired or wireless network, bus, or other communication means and may therefore allow the computing device to transmit communications to and/or receive communications from other devices. The display unit(s) may be provided, for example, to allow a user to view various information in connection with execution of the instructions. The user input device(s) may be provided, for example, to allow the user to make manual adjustments, make selections, enter data or various other information, and/or interact in any of a variety of manners with the processor during execution of the instructions.
The various methods or processes outlined herein may be coded as software that is executable on one or more processors that employ any one of a variety of operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages and/or programming or scripting tools, and also may be compiled as executable machine language code or intermediate code that is executed on a framework or virtual machine.
In this respect, various inventive concepts may be embodied as a computer readable storage medium (or multiple computer readable storage media) (e.g., a computer memory, one or more floppy discs, compact discs, optical discs, magnetic tapes, flash memories, circuit configurations in Field Programmable Gate Arrays or other semiconductor devices, or other non-transitory medium or tangible computer storage medium) encoded with one or more programs that, when executed on one or more computers or other processors, perform methods that implement the various embodiments of the invention discussed above. The computer readable medium or media can be transportable, such that the program or programs stored thereon can be loaded onto one or more different computers or other processors to implement various aspects of the present invention as discussed above.
The terms “program” or “software” are used herein in a generic sense to refer to any type of computer code or set of computer-executable instructions that can be employed to program a computer or other processor to implement various aspects of embodiments as discussed above. Additionally, it should be appreciated that according to one aspect, one or more computer programs that when executed perform methods of the present invention need not reside on a single computer or processor, but may be distributed in a modular fashion amongst a number of different computers or processors to implement various aspects of the present invention.
Computer-executable instructions may be in many forms, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.
Also, data structures may be stored in computer-readable media in any suitable form. For simplicity of illustration, data structures may be shown to have fields that are related through location in the data structure. Such relationships may likewise be achieved by assigning storage for the fields with locations in a computer-readable medium that convey relationship between the fields. However, any suitable mechanism may be used to establish a relationship between information in fields of a data structure, including through the use of pointers, tags or other mechanisms that establish relationship between data elements.
Also, various inventive concepts may be embodied as one or more methods, of which an example has been provided. The acts performed as part of the method may be ordered in any suitable way. Accordingly, embodiments may be constructed in which acts are performed in an order different than illustrated, which may include performing some acts simultaneously, even though shown as sequential acts in illustrative embodiments.
All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms.
The indefinite articles “a” and “an,” as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean “at least one.”
The phrase “and/or,” as used herein in the specification and in the claims, should be understood to mean “either or both” of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with “and/or” should be construed in the same fashion, i.e., “one or more” of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the “and/or” clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to “A and/or B”, when used in conjunction with open-ended language such as “comprising” can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc.
As used herein in the specification and in the claims, “or” should be understood to have the same meaning as “and/or” as defined above. For example, when separating items in a list, “or” or “and/or” shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as “only one of” or “exactly one of,” or, when used in the claims, “consisting of,” will refer to the inclusion of exactly one element of a number or list of elements. In general, the term “or” as used herein shall only be interpreted as indicating exclusive alternatives (i.e. “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.” “Consisting essentially of,” when used in the claims, shall have its ordinary meaning as used in the field of patent law.
As used herein in the specification and in the claims, the phrase “at least one,” in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase “at least one” refers, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, “at least one of A and B” (or, equivalently, “at least one of A or B,” or, equivalently “at least one of A and/or B”) can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.
In the claims, as well as in the specification above, all transitional phrases such as “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” “holding,” “composed of,” and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases “consisting of” and “consisting essentially of” shall be closed or semi-closed transitional phrases, respectively, as set forth in the United States Patent Office Manual of Patent Examining Procedures, Section 2111.03.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2691780 | Feb 2010 | CA | national |
The application claims the benefit, under 35 U.S.C. §120, as a continuation (CON) of U.S. Non-provisional application Ser. No. 12/704,485, entitled “Management System, and Associated Methods and Apparatus, for Providing Improved Visibility, Quality Control and Audit Capability for Underground Facility Locate and/or Marking Operations,” filed Feb. 11, 2010. U.S. Ser. No. 12/704,485 claims a priority benefit, under 35 U.S.C. §119(a), to Canadian application serial no. 2,691,780, entitled “Management System, and Associated Methods and Apparatus, for Providing Improved Visibility, Quality Control and Audit Capability for Underground Facility Locate and/or Marking Operations,” filed on Feb. 10, 2010. U.S. Ser. No. 12/704,485 claims a priority benefit, under 35 U.S.C. §119(e), to U.S. provisional application Ser. No. 61/151,826, entitled “Management System for Providing Improved Visibility, Quality Control and Audit Capability for Underground Facility Locate Applications,” filed on Feb. 11, 2009. Each of the above-identified applications is hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3871557 | Smrt | Mar 1975 | A |
| 3972038 | Fletcher et al. | Jul 1976 | A |
| 3974491 | Sipe | Aug 1976 | A |
| 4208653 | Abe | Jun 1980 | A |
| 4251813 | Carre | Feb 1981 | A |
| 4258320 | Schonstedt | Mar 1981 | A |
| 4387340 | Peterman | Jun 1983 | A |
| 4388592 | Schonstedt | Jun 1983 | A |
| 4455509 | Crum et al. | Jun 1984 | A |
| 4520317 | Peterman | May 1985 | A |
| 4536710 | Dunham | Aug 1985 | A |
| 4539522 | Schonstedt | Sep 1985 | A |
| 4550376 | Maciejczak | Oct 1985 | A |
| 4590425 | Schonstedt | May 1986 | A |
| 4623282 | Allen | Nov 1986 | A |
| 4638289 | Zottnik | Jan 1987 | A |
| 4639674 | Rippingale | Jan 1987 | A |
| 4712094 | Bolson, Sr. | Dec 1987 | A |
| 4747207 | Schonstedt et al. | May 1988 | A |
| 4803773 | Schonstedt | Feb 1989 | A |
| 4818944 | Rippingale | Apr 1989 | A |
| 4819162 | Webb, Jr. et al. | Apr 1989 | A |
| 4839623 | Schonstedt et al. | Jun 1989 | A |
| 4839624 | Schonstedt | Jun 1989 | A |
| 4873533 | Oike | Oct 1989 | A |
| 4899293 | Dawson et al. | Feb 1990 | A |
| 4943238 | Gregorio | Jul 1990 | A |
| 4970683 | Harshaw et al. | Nov 1990 | A |
| 4972319 | Delorme | Nov 1990 | A |
| 4984279 | Kidney et al. | Jan 1991 | A |
| 4987412 | Vaitekunas et al. | Jan 1991 | A |
| 5001430 | Peterman et al. | Mar 1991 | A |
| 5006806 | Rippingale et al. | Apr 1991 | A |
| 5014008 | Flowerdew | May 1991 | A |
| 5017873 | Rippingale et al. | May 1991 | A |
| 5025150 | Oldham et al. | Jun 1991 | A |
| 5032989 | Tornetta | Jul 1991 | A |
| 5043666 | Tavernetti et al. | Aug 1991 | A |
| 5045368 | Cosman et al. | Sep 1991 | A |
| 5065098 | Salsman et al. | Nov 1991 | A |
| 5074244 | Byers | Dec 1991 | A |
| 5093622 | Balkman | Mar 1992 | A |
| 5097211 | Schonstedt | Mar 1992 | A |
| 5103920 | Patton | Apr 1992 | A |
| 5114517 | Rippingale et al. | May 1992 | A |
| 5122750 | Rippingale et al. | Jun 1992 | A |
| 5122959 | Nathanson et al. | Jun 1992 | A |
| 5136245 | Schonstedt | Aug 1992 | A |
| 5138761 | Schonstedt | Aug 1992 | A |
| 5150295 | Mattingly | Sep 1992 | A |
| 5164607 | Weigert et al. | Nov 1992 | A |
| 5173139 | Rippingale et al. | Dec 1992 | A |
| 5206065 | Rippingale et al. | Apr 1993 | A |
| 5214757 | Mauney et al. | May 1993 | A |
| 5231355 | Rider et al. | Jul 1993 | A |
| 5239290 | Schonstedt | Aug 1993 | A |
| 5260659 | Flowerdew et al. | Nov 1993 | A |
| 5264795 | Rider | Nov 1993 | A |
| 5267147 | Harshaw et al. | Nov 1993 | A |
| 5276613 | Schlumberger | Jan 1994 | A |
| 5293911 | Akeel | Mar 1994 | A |
| 5311195 | Mathis et al. | May 1994 | A |
| 5329464 | Sumic et al. | Jul 1994 | A |
| 5361029 | Rider et al. | Nov 1994 | A |
| 5365163 | Satterwhite et al. | Nov 1994 | A |
| 5373298 | Karouby | Dec 1994 | A |
| 5399844 | Holland | Mar 1995 | A |
| 5414462 | Veatch | May 1995 | A |
| 5430379 | Parkinson et al. | Jul 1995 | A |
| 5444364 | Satterwhite et al. | Aug 1995 | A |
| 5454074 | Hartel et al. | Sep 1995 | A |
| 5467271 | Abel et al. | Nov 1995 | A |
| 5471143 | Doany | Nov 1995 | A |
| 5486067 | Huynh | Jan 1996 | A |
| 5487139 | Saylor et al. | Jan 1996 | A |
| 5517419 | Lanckton et al. | May 1996 | A |
| 5519329 | Satterwhite | May 1996 | A |
| 5519809 | Husseiny et al. | May 1996 | A |
| 5529432 | Huynh et al. | Jun 1996 | A |
| 5530357 | Cosman et al. | Jun 1996 | A |
| 5543931 | Lee et al. | Aug 1996 | A |
| 5568162 | Samsel et al. | Oct 1996 | A |
| 5576973 | Haddy | Nov 1996 | A |
| 5596494 | Kuo | Jan 1997 | A |
| 5621325 | Draper et al. | Apr 1997 | A |
| 5629626 | Russell et al. | May 1997 | A |
| 5644237 | Eslambolchi et al. | Jul 1997 | A |
| 5652717 | Miller et al. | Jul 1997 | A |
| 5699244 | Clark, Jr. et al. | Dec 1997 | A |
| 5717922 | Hohensee et al. | Feb 1998 | A |
| 5738525 | Davies | Apr 1998 | A |
| 5739785 | Allison et al. | Apr 1998 | A |
| 5742509 | Goldberg et al. | Apr 1998 | A |
| 5751289 | Myers | May 1998 | A |
| 5764127 | Hore et al. | Jun 1998 | A |
| 5769370 | Ashjaee | Jun 1998 | A |
| 5815411 | Ellenby et al. | Sep 1998 | A |
| 5819859 | Stump et al. | Oct 1998 | A |
| 5828219 | Hanlon et al. | Oct 1998 | A |
| 5848373 | DeLorme et al. | Dec 1998 | A |
| 5864632 | Ogawa et al. | Jan 1999 | A |
| 5913201 | Kocur | Jun 1999 | A |
| 5916300 | Kirk et al. | Jun 1999 | A |
| 5917325 | Smith | Jun 1999 | A |
| 5918565 | Casas | Jul 1999 | A |
| 5920194 | Lewis et al. | Jul 1999 | A |
| 5920846 | Storch et al. | Jul 1999 | A |
| 5955667 | Fyfe | Sep 1999 | A |
| 5961569 | Craport et al. | Oct 1999 | A |
| 5987380 | Backman et al. | Nov 1999 | A |
| 5992620 | Holtom | Nov 1999 | A |
| 6024655 | Coffee | Feb 2000 | A |
| 6026135 | McFee et al. | Feb 2000 | A |
| 6026345 | Shah et al. | Feb 2000 | A |
| 6031454 | Lovejoy et al. | Feb 2000 | A |
| 6032530 | Hock | Mar 2000 | A |
| 6049776 | Donnelly et al. | Apr 2000 | A |
| 6061632 | Dreier | May 2000 | A |
| 6061940 | Rice | May 2000 | A |
| 6074693 | Manning | Jun 2000 | A |
| 6075481 | Eslambolchi et al. | Jun 2000 | A |
| 6079114 | Toews | Jun 2000 | A |
| 6101087 | Sutton et al. | Aug 2000 | A |
| 6107801 | Hopwood et al. | Aug 2000 | A |
| 6127827 | Lewis | Oct 2000 | A |
| 6130539 | Polak | Oct 2000 | A |
| 6138906 | DeMayo | Oct 2000 | A |
| 6140798 | Krieger | Oct 2000 | A |
| 6140819 | Peterman et al. | Oct 2000 | A |
| 6148262 | Fry | Nov 2000 | A |
| 6154658 | Caci | Nov 2000 | A |
| 6169517 | Eslambolchi et al. | Jan 2001 | B1 |
| 6169958 | Nagasamy et al. | Jan 2001 | B1 |
| 6185490 | Ferguson | Feb 2001 | B1 |
| 6188777 | Darrell et al. | Feb 2001 | B1 |
| 6195922 | Stump | Mar 2001 | B1 |
| 6206282 | Hayes, Sr. et al. | Mar 2001 | B1 |
| 6217253 | Eslambolchi et al. | Apr 2001 | B1 |
| 6234218 | Boers | May 2001 | B1 |
| 6246933 | Bague | Jun 2001 | B1 |
| 6262720 | Jeffrey et al. | Jul 2001 | B1 |
| 6268731 | Hopwood et al. | Jul 2001 | B1 |
| 6282477 | Gudat et al. | Aug 2001 | B1 |
| 6294022 | Eslambolchi et al. | Sep 2001 | B1 |
| 6297736 | Lewis et al. | Oct 2001 | B1 |
| 6298290 | Abe et al. | Oct 2001 | B1 |
| 6299934 | Manning | Oct 2001 | B1 |
| 6301533 | Markow | Oct 2001 | B1 |
| 6308565 | French et al. | Oct 2001 | B1 |
| 6320518 | Saeki et al. | Nov 2001 | B2 |
| 6327533 | Chou | Dec 2001 | B1 |
| 6330503 | Sharp et al. | Dec 2001 | B1 |
| 6337693 | Roy et al. | Jan 2002 | B1 |
| 6343290 | Cossins et al. | Jan 2002 | B1 |
| 6353767 | Wakeman et al. | Mar 2002 | B1 |
| 6356082 | Alkire et al. | Mar 2002 | B1 |
| 6360931 | Morford | Mar 2002 | B1 |
| 6362778 | Neher | Mar 2002 | B2 |
| 6363320 | Chou | Mar 2002 | B1 |
| 6375038 | Daansen et al. | Apr 2002 | B1 |
| 6378220 | Baioff et al. | Apr 2002 | B1 |
| 6390336 | Orozco | May 2002 | B1 |
| 6397147 | Whitehead | May 2002 | B1 |
| 6401051 | Merriam | Jun 2002 | B1 |
| 6407550 | Parakulam et al. | Jun 2002 | B1 |
| 6411094 | Gard et al. | Jun 2002 | B1 |
| 6414629 | Curcio | Jul 2002 | B1 |
| 6421725 | Vermilyea et al. | Jul 2002 | B1 |
| 6426872 | Sutton et al. | Jul 2002 | B1 |
| 6430496 | Smith et al. | Aug 2002 | B1 |
| 6434258 | Wiens | Aug 2002 | B2 |
| 6437708 | Brouwer | Aug 2002 | B1 |
| 6459266 | Fling | Oct 2002 | B1 |
| 6459988 | Fan et al. | Oct 2002 | B1 |
| 6476708 | Johnson | Nov 2002 | B1 |
| 6490524 | White et al. | Dec 2002 | B1 |
| 6493650 | Rodgers et al. | Dec 2002 | B1 |
| 6496137 | Johansson | Dec 2002 | B1 |
| 6501501 | Miyazawa | Dec 2002 | B1 |
| 6512312 | Herkenrath et al. | Jan 2003 | B1 |
| 6526352 | Johnson et al. | Feb 2003 | B1 |
| 6526443 | Goldsmith et al. | Feb 2003 | B1 |
| 6526526 | Dong et al. | Feb 2003 | B1 |
| 6549011 | Flatt | Apr 2003 | B2 |
| 6552548 | Lewis et al. | Apr 2003 | B1 |
| 6557738 | Meintzer | May 2003 | B1 |
| 6585133 | Brouwer | Jul 2003 | B1 |
| 6587851 | Ditcharo et al. | Jul 2003 | B1 |
| 6600420 | Goff et al. | Jul 2003 | B2 |
| 6601017 | Kennedy et al. | Jul 2003 | B1 |
| 6606557 | Kotzin | Aug 2003 | B2 |
| 6617856 | Royle et al. | Sep 2003 | B1 |
| 6617996 | Johansson et al. | Sep 2003 | B2 |
| 6629030 | Klausner et al. | Sep 2003 | B2 |
| D481054 | Hennig | Oct 2003 | S |
| 6633163 | Fling | Oct 2003 | B2 |
| 6650293 | Eslambolchi et al. | Nov 2003 | B1 |
| 6650798 | Russell et al. | Nov 2003 | B2 |
| 6674276 | Wiesemann et al. | Jan 2004 | B2 |
| 6693585 | MacLeod | Feb 2004 | B1 |
| 6704644 | Kobayashi et al. | Mar 2004 | B1 |
| 6710741 | Tucker | Mar 2004 | B2 |
| 6717392 | Pearson | Apr 2004 | B2 |
| 6723375 | Zeck et al. | Apr 2004 | B2 |
| 6728662 | Frost et al. | Apr 2004 | B2 |
| 6735293 | Doherty et al. | May 2004 | B2 |
| 6750816 | Kunysz | Jun 2004 | B1 |
| 6751341 | Oosawa | Jun 2004 | B2 |
| 6751552 | Minelli | Jun 2004 | B1 |
| 6751553 | Young et al. | Jun 2004 | B2 |
| 6751554 | Asher et al. | Jun 2004 | B1 |
| 6753891 | Chohan et al. | Jun 2004 | B1 |
| 6754582 | Smith et al. | Jun 2004 | B1 |
| 6769462 | Larson et al. | Aug 2004 | B2 |
| 6772142 | Kelling et al. | Aug 2004 | B1 |
| 6777923 | Pearson | Aug 2004 | B2 |
| 6778128 | Tucker et al. | Aug 2004 | B2 |
| 6792079 | Boggs et al. | Sep 2004 | B1 |
| 6798319 | Tucker et al. | Sep 2004 | B2 |
| 6799116 | Robbins | Sep 2004 | B2 |
| 6815953 | Bigelow | Nov 2004 | B1 |
| 6819109 | Sowers et al. | Nov 2004 | B2 |
| 6825775 | Fling et al. | Nov 2004 | B2 |
| 6825793 | Taylor, Jr. et al. | Nov 2004 | B2 |
| 6833811 | Zeitfuss et al. | Dec 2004 | B2 |
| 6836231 | Pearson | Dec 2004 | B2 |
| 6845171 | Shum et al. | Jan 2005 | B2 |
| 6850161 | Elliott et al. | Feb 2005 | B1 |
| 6850843 | Smith et al. | Feb 2005 | B2 |
| 6853303 | Chen et al. | Feb 2005 | B2 |
| 6853905 | Barton | Feb 2005 | B2 |
| 6865484 | Miyasaka et al. | Mar 2005 | B2 |
| 6876945 | Emord | Apr 2005 | B2 |
| 6882912 | DiLodovico et al. | Apr 2005 | B2 |
| 6895356 | Brimhall et al. | May 2005 | B2 |
| 6898518 | Padmanabhan | May 2005 | B2 |
| 6898525 | Minelli | May 2005 | B1 |
| 6898550 | Blackadar et al. | May 2005 | B1 |
| 6904361 | Tallman et al. | Jun 2005 | B1 |
| 6915211 | Kram et al. | Jul 2005 | B2 |
| 6915955 | Jung et al. | Jul 2005 | B2 |
| 6937853 | Hall | Aug 2005 | B2 |
| 6944542 | Eschenbach | Sep 2005 | B1 |
| 6949052 | Millington et al. | Sep 2005 | B2 |
| 6954071 | Flatt et al. | Oct 2005 | B2 |
| 6956524 | Tucker et al. | Oct 2005 | B2 |
| 6958690 | Asher et al. | Oct 2005 | B1 |
| 6968296 | Royle | Nov 2005 | B2 |
| 6972698 | Deguchi | Dec 2005 | B2 |
| 6972719 | Swope et al. | Dec 2005 | B1 |
| 6973291 | Bellows | Dec 2005 | B1 |
| 6975942 | Young et al. | Dec 2005 | B2 |
| 6977508 | Pearson et al. | Dec 2005 | B2 |
| 6980929 | Aronstam et al. | Dec 2005 | B2 |
| 6983036 | Esty et al. | Jan 2006 | B2 |
| 6990458 | Harrison et al. | Jan 2006 | B2 |
| 6992584 | Dooley et al. | Jan 2006 | B2 |
| 6993088 | Fling et al. | Jan 2006 | B2 |
| 6996210 | Esty et al. | Feb 2006 | B2 |
| 6999021 | Taylor, Jr. et al. | Feb 2006 | B2 |
| 7003138 | Wilson | Feb 2006 | B2 |
| 7003443 | Ford et al. | Feb 2006 | B2 |
| 7003475 | Friedland et al. | Feb 2006 | B1 |
| 7009519 | Leonard et al. | Mar 2006 | B2 |
| 7016855 | Eaton et al. | Mar 2006 | B2 |
| 7038454 | Gard et al. | May 2006 | B2 |
| 7042358 | Moore | May 2006 | B2 |
| 7048320 | Rubel et al. | May 2006 | B2 |
| 7053789 | Fling et al. | May 2006 | B2 |
| 7054741 | Harrison et al. | May 2006 | B2 |
| 7057383 | Schlapp et al. | Jun 2006 | B2 |
| 7062414 | Waite et al. | Jun 2006 | B2 |
| 7079591 | Fling et al. | Jul 2006 | B2 |
| 7079990 | Haller et al. | Jul 2006 | B2 |
| 7091852 | Mason et al. | Aug 2006 | B2 |
| 7091872 | Bigelow et al. | Aug 2006 | B1 |
| 7110142 | Mestha et al. | Sep 2006 | B2 |
| 7111318 | Vitale et al. | Sep 2006 | B2 |
| 7113124 | Waite | Sep 2006 | B2 |
| 7114648 | Ginskey et al. | Oct 2006 | B2 |
| 7116244 | Fling et al. | Oct 2006 | B2 |
| 7120564 | Pacey | Oct 2006 | B2 |
| 7133802 | Koch et al. | Nov 2006 | B2 |
| 7136765 | Maier et al. | Nov 2006 | B2 |
| 7142196 | Connor et al. | Nov 2006 | B1 |
| 7143130 | Lin | Nov 2006 | B2 |
| 7162367 | Lin et al. | Jan 2007 | B2 |
| 7171389 | Harrison | Jan 2007 | B2 |
| 7197214 | Elkins, II et al. | Mar 2007 | B2 |
| 7216034 | Vitikainen et al. | May 2007 | B2 |
| 7233394 | Odhner | Jun 2007 | B2 |
| 7235980 | Pearson et al. | Jun 2007 | B2 |
| 7236091 | Kiang et al. | Jun 2007 | B2 |
| 7240839 | Jung et al. | Jul 2007 | B2 |
| 7245215 | Gollu et al. | Jul 2007 | B2 |
| 7266571 | Botzer et al. | Sep 2007 | B2 |
| 7269002 | Turner et al. | Sep 2007 | B1 |
| 7272498 | Singh | Sep 2007 | B2 |
| 7285958 | Overby et al. | Oct 2007 | B2 |
| 7289890 | Mitchell et al. | Oct 2007 | B2 |
| 7298323 | Park | Nov 2007 | B2 |
| 7298483 | Jung et al. | Nov 2007 | B2 |
| 7298673 | Pappas et al. | Nov 2007 | B2 |
| 7304480 | Pearson et al. | Dec 2007 | B1 |
| 7310584 | Royle | Dec 2007 | B2 |
| 7313759 | Sinisi | Dec 2007 | B2 |
| 7319387 | Willson et al. | Jan 2008 | B2 |
| 7323969 | Delgado et al. | Jan 2008 | B1 |
| 7324905 | Droubie et al. | Jan 2008 | B2 |
| 7331340 | Barney | Feb 2008 | B2 |
| 7333631 | Roh et al. | Feb 2008 | B2 |
| 7336078 | Merewether et al. | Feb 2008 | B1 |
| 7339379 | Thompson et al. | Mar 2008 | B2 |
| 7340037 | Jean et al. | Mar 2008 | B1 |
| 7342537 | Pearson et al. | Mar 2008 | B2 |
| 7345617 | Friborg et al. | Mar 2008 | B2 |
| 7346531 | Jacobs | Mar 2008 | B2 |
| 7353110 | Kim | Apr 2008 | B2 |
| 7353938 | Moldolan | Apr 2008 | B2 |
| 7356406 | Harrison et al. | Apr 2008 | B2 |
| 7356421 | Gudmundsson et al. | Apr 2008 | B2 |
| 7358738 | Overby et al. | Apr 2008 | B2 |
| 7359821 | Smith et al. | Apr 2008 | B1 |
| 7363126 | Zhong et al. | Apr 2008 | B1 |
| 7372247 | Giusti et al. | May 2008 | B1 |
| 7372276 | Mulcahey | May 2008 | B2 |
| 7379015 | Workman | May 2008 | B2 |
| 7379879 | Sloo | May 2008 | B1 |
| 7386376 | Basir et al. | Jun 2008 | B2 |
| 7392320 | Bookman et al. | Jun 2008 | B2 |
| 7392486 | Gyde et al. | Jun 2008 | B1 |
| 7396177 | Lapstun et al. | Jul 2008 | B2 |
| 7396178 | Lapstun et al. | Jul 2008 | B2 |
| 7398184 | Chen | Jul 2008 | B1 |
| 7400976 | Young et al. | Jul 2008 | B2 |
| 7403012 | Worsley et al. | Jul 2008 | B2 |
| 7403853 | Janky et al. | Jul 2008 | B1 |
| 7413363 | Lapstun et al. | Aug 2008 | B2 |
| 7432938 | Reuter et al. | Oct 2008 | B1 |
| 7433830 | Ingman et al. | Oct 2008 | B2 |
| 7439866 | Wallner et al. | Oct 2008 | B2 |
| 7441249 | Adachi et al. | Oct 2008 | B2 |
| 7447509 | Cossins et al. | Nov 2008 | B2 |
| 7448048 | Nesamoney et al. | Nov 2008 | B1 |
| 7457762 | Wetzer et al. | Nov 2008 | B2 |
| 7464046 | Wilson et al. | Dec 2008 | B2 |
| 7469247 | Cossins et al. | Dec 2008 | B2 |
| 7472181 | Hollinger et al. | Dec 2008 | B2 |
| 7482973 | Tucker et al. | Jan 2009 | B2 |
| 7487106 | Levine et al. | Feb 2009 | B2 |
| 7500583 | Cox | Mar 2009 | B1 |
| 7538724 | Baillot | May 2009 | B1 |
| 7586433 | Johansson et al. | Sep 2009 | B1 |
| 7612682 | Staples et al. | Nov 2009 | B2 |
| 7626496 | Asher | Dec 2009 | B1 |
| 7640105 | Nielsen et al. | Dec 2009 | B2 |
| 7773095 | Badrak et al. | Aug 2010 | B1 |
| 8127865 | Watson et al. | Mar 2012 | B2 |
| 8473148 | Nielsen et al. | Jun 2013 | B2 |
| 8480332 | Miller | Jul 2013 | B2 |
| 8532341 | Nielsen et al. | Sep 2013 | B2 |
| 8543937 | Nielsen et al. | Sep 2013 | B2 |
| 8612148 | Nielsen et al. | Dec 2013 | B2 |
| 8612271 | Nielsen et al. | Dec 2013 | B2 |
| 8612276 | Nielsen et al. | Dec 2013 | B1 |
| 8620726 | Nielsen et al. | Dec 2013 | B2 |
| 8626571 | Nielsen et al. | Jan 2014 | B2 |
| 8700325 | Nielsen et al. | Apr 2014 | B2 |
| 20010029996 | Robinson | Oct 2001 | A1 |
| 20010048757 | Oosawa | Dec 2001 | A1 |
| 20020027521 | Clodfelter | Mar 2002 | A1 |
| 20020029161 | Brodersen | Mar 2002 | A1 |
| 20020032028 | Kaupe | Mar 2002 | A1 |
| 20020038076 | Sheehan et al. | Mar 2002 | A1 |
| 20020046259 | Glorikian | Apr 2002 | A1 |
| 20020052750 | Hirooka | May 2002 | A1 |
| 20020052755 | Whatley et al. | May 2002 | A1 |
| 20020055870 | Thomas | May 2002 | A1 |
| 20020077876 | O'Meara et al. | Jun 2002 | A1 |
| 20020078035 | Frank et al. | Jun 2002 | A1 |
| 20020124177 | Harper | Sep 2002 | A1 |
| 20020130806 | Taylor et al. | Sep 2002 | A1 |
| 20020143596 | Carmody | Oct 2002 | A1 |
| 20020145559 | Sullivan | Oct 2002 | A1 |
| 20020146272 | Conover | Oct 2002 | A1 |
| 20020153134 | Newman | Oct 2002 | A1 |
| 20020184235 | Young et al. | Dec 2002 | A1 |
| 20030012411 | Sjostrom et al. | Jan 2003 | A1 |
| 20030023476 | Gainey | Jan 2003 | A1 |
| 20030028676 | Pangrac et al. | Feb 2003 | A1 |
| 20030046003 | Smith et al. | Mar 2003 | A1 |
| 20030061211 | Shultz et al. | Mar 2003 | A1 |
| 20030064705 | Desiderio | Apr 2003 | A1 |
| 20030100316 | Odamura | May 2003 | A1 |
| 20030110184 | Gibson et al. | Jun 2003 | A1 |
| 20030125853 | Takagi et al. | Jul 2003 | A1 |
| 20030130820 | Lane | Jul 2003 | A1 |
| 20030168834 | Ulrich | Sep 2003 | A1 |
| 20030177027 | DiMarco | Sep 2003 | A1 |
| 20030177051 | Driscoll et al. | Sep 2003 | A1 |
| 20030184300 | Bigelow | Oct 2003 | A1 |
| 20030196585 | McDonald et al. | Oct 2003 | A1 |
| 20030212621 | Poulter | Nov 2003 | A1 |
| 20030216949 | Kram et al. | Nov 2003 | A1 |
| 20040006425 | Wood et al. | Jan 2004 | A1 |
| 20040030706 | Evans | Feb 2004 | A1 |
| 20040057795 | Mayfield et al. | Mar 2004 | A1 |
| 20040110515 | Blumberg et al. | Jun 2004 | A1 |
| 20040111313 | Ingman et al. | Jun 2004 | A1 |
| 20040168358 | Stump | Sep 2004 | A1 |
| 20040203909 | Koster | Oct 2004 | A1 |
| 20040210370 | Gudat et al. | Oct 2004 | A1 |
| 20040215701 | Vrajich | Oct 2004 | A1 |
| 20040220731 | Tucker et al. | Nov 2004 | A1 |
| 20040236620 | Chauhan et al. | Nov 2004 | A1 |
| 20040237077 | Cole et al. | Nov 2004 | A1 |
| 20050021428 | Costello | Jan 2005 | A1 |
| 20050033492 | Mendelson et al. | Feb 2005 | A1 |
| 20050033513 | Gasbarro | Feb 2005 | A1 |
| 20050033620 | Gloor et al. | Feb 2005 | A1 |
| 20050038825 | Tarabzouni et al. | Feb 2005 | A1 |
| 20050040222 | Robinson | Feb 2005 | A1 |
| 20050055142 | McMurtry et al. | Mar 2005 | A1 |
| 20050057745 | Bontje | Mar 2005 | A1 |
| 20050062475 | Nakanishi et al. | Mar 2005 | A1 |
| 20050094772 | Harrison et al. | May 2005 | A1 |
| 20050101334 | Brown et al. | May 2005 | A1 |
| 20050108523 | West | May 2005 | A1 |
| 20050125389 | Hazzard et al. | Jun 2005 | A1 |
| 20050192727 | Shostak et al. | Sep 2005 | A1 |
| 20050232475 | Floeder | Oct 2005 | A1 |
| 20050240649 | Elkington | Oct 2005 | A1 |
| 20050243084 | Smith et al. | Nov 2005 | A1 |
| 20050273346 | Frost | Dec 2005 | A1 |
| 20050278371 | Funk et al. | Dec 2005 | A1 |
| 20060015389 | Perham | Jan 2006 | A1 |
| 20060015475 | Birkner et al. | Jan 2006 | A1 |
| 20060026020 | Waite et al. | Feb 2006 | A1 |
| 20060031110 | Benbassat et al. | Feb 2006 | A1 |
| 20060055584 | Waite et al. | Mar 2006 | A1 |
| 20060073464 | Baldus et al. | Apr 2006 | A1 |
| 20060077095 | Tucker et al. | Apr 2006 | A1 |
| 20060085133 | Young et al. | Apr 2006 | A1 |
| 20060085396 | Evans et al. | Apr 2006 | A1 |
| 20060091888 | Holman et al. | May 2006 | A1 |
| 20060109131 | Sen et al. | May 2006 | A1 |
| 20060125644 | Sharp | Jun 2006 | A1 |
| 20060161349 | Cross et al. | Jul 2006 | A1 |
| 20060178812 | Affleck et al. | Aug 2006 | A1 |
| 20060178918 | Mikurak | Aug 2006 | A1 |
| 20060200305 | Sheha et al. | Sep 2006 | A1 |
| 20060206370 | Skopal | Sep 2006 | A1 |
| 20060208927 | Poor et al. | Sep 2006 | A1 |
| 20060212195 | Veith et al. | Sep 2006 | A1 |
| 20060217876 | Houri et al. | Sep 2006 | A1 |
| 20060229923 | Adi et al. | Oct 2006 | A1 |
| 20060235741 | Deaton et al. | Oct 2006 | A1 |
| 20060244454 | Gard et al. | Nov 2006 | A1 |
| 20060254820 | Cole et al. | Nov 2006 | A1 |
| 20060276198 | Michelon et al. | Dec 2006 | A1 |
| 20060282280 | Stotz et al. | Dec 2006 | A1 |
| 20060285913 | Koptis | Dec 2006 | A1 |
| 20060287900 | Fiore et al. | Dec 2006 | A1 |
| 20060289679 | Johnson et al. | Dec 2006 | A1 |
| 20070013379 | Staples et al. | Jan 2007 | A1 |
| 20070018632 | Royle | Jan 2007 | A1 |
| 20070044539 | Sabol et al. | Mar 2007 | A1 |
| 20070050232 | Chang et al. | Mar 2007 | A1 |
| 20070073610 | Marugabandhu et al. | Mar 2007 | A1 |
| 20070094034 | Berlin et al. | Apr 2007 | A1 |
| 20070094708 | Hess | Apr 2007 | A1 |
| 20070100496 | Forell | May 2007 | A1 |
| 20070100521 | Grae | May 2007 | A1 |
| 20070100768 | Boccon-Gibod et al. | May 2007 | A1 |
| 20070112936 | Harrison | May 2007 | A1 |
| 20070118545 | Chandrasekharan et al. | May 2007 | A1 |
| 20070127694 | Hajj et al. | Jun 2007 | A1 |
| 20070129817 | Cadiz et al. | Jun 2007 | A1 |
| 20070143676 | Chen | Jun 2007 | A1 |
| 20070150140 | Seymour | Jun 2007 | A1 |
| 20070155360 | An | Jul 2007 | A1 |
| 20070185746 | Chieu et al. | Aug 2007 | A1 |
| 20070191025 | McBrierty et al. | Aug 2007 | A1 |
| 20070195011 | Hatori et al. | Aug 2007 | A1 |
| 20070198992 | Mirlas et al. | Aug 2007 | A1 |
| 20070219722 | Sawyer et al. | Sep 2007 | A1 |
| 20070226004 | Harrison | Sep 2007 | A1 |
| 20070255529 | Biazetti et al. | Nov 2007 | A1 |
| 20070260569 | Biger et al. | Nov 2007 | A1 |
| 20070288159 | Skelton | Dec 2007 | A1 |
| 20070288195 | Waite et al. | Dec 2007 | A1 |
| 20070294258 | Caldwell et al. | Dec 2007 | A1 |
| 20080001009 | Young | Jan 2008 | A1 |
| 20080010338 | Curtis et al. | Jan 2008 | A1 |
| 20080017416 | Watson | Jan 2008 | A1 |
| 20080021863 | Evans et al. | Jan 2008 | A1 |
| 20080025614 | Hintz et al. | Jan 2008 | A1 |
| 20080042410 | Breed et al. | Feb 2008 | A1 |
| 20080077290 | Weinmann et al. | Mar 2008 | A1 |
| 20080084329 | Davies | Apr 2008 | A1 |
| 20080103695 | Whiting | May 2008 | A1 |
| 20080114683 | Neveu et al. | May 2008 | A1 |
| 20080120129 | Seubert et al. | May 2008 | A1 |
| 20080125942 | Tucker et al. | May 2008 | A1 |
| 20080133128 | Koch | Jun 2008 | A1 |
| 20080137589 | Barrett | Jun 2008 | A1 |
| 20080141281 | Ramsey et al. | Jun 2008 | A1 |
| 20080161996 | Chang et al. | Jul 2008 | A1 |
| 20080162242 | Schneur et al. | Jul 2008 | A1 |
| 20080167911 | Hatakeda | Jul 2008 | A1 |
| 20080180319 | Islam et al. | Jul 2008 | A1 |
| 20080180322 | Islam et al. | Jul 2008 | A1 |
| 20080186166 | Zhou et al. | Aug 2008 | A1 |
| 20080194268 | Koch | Aug 2008 | A1 |
| 20080208657 | Chessell et al. | Aug 2008 | A1 |
| 20080228294 | Nielsen et al. | Sep 2008 | A1 |
| 20080235658 | Adi et al. | Sep 2008 | A1 |
| 20080245299 | Nielsen et al. | Oct 2008 | A1 |
| 20080288267 | Asher et al. | Nov 2008 | A1 |
| 20080294988 | Nicholas et al. | Nov 2008 | A1 |
| 20080299534 | Richardson | Dec 2008 | A1 |
| 20090005977 | Chung et al. | Jan 2009 | A1 |
| 20090013928 | Nielsen et al. | Jan 2009 | A1 |
| 20090043504 | Bandyopadhyay et al. | Feb 2009 | A1 |
| 20090051515 | Fujinawa et al. | Feb 2009 | A1 |
| 20090073191 | Smith et al. | Mar 2009 | A1 |
| 20090085568 | Cole | Apr 2009 | A1 |
| 20090121933 | Tucker et al. | May 2009 | A1 |
| 20090157746 | More et al. | Jun 2009 | A1 |
| 20090184823 | Tessier | Jul 2009 | A1 |
| 20090201178 | Nielsen et al. | Aug 2009 | A1 |
| 20090201311 | Nielsen et al. | Aug 2009 | A1 |
| 20090202101 | Nielsen et al. | Aug 2009 | A1 |
| 20090202110 | Nielsen et al. | Aug 2009 | A1 |
| 20090202111 | Nielsen et al. | Aug 2009 | A1 |
| 20090202112 | Nielsen et al. | Aug 2009 | A1 |
| 20090204238 | Nielsen et al. | Aug 2009 | A1 |
| 20090204466 | Nielsen et al. | Aug 2009 | A1 |
| 20090204614 | Nielsen et al. | Aug 2009 | A1 |
| 20090204625 | Nielsen et al. | Aug 2009 | A1 |
| 20090207019 | Nielsen et al. | Aug 2009 | A1 |
| 20090208642 | Nielsen et al. | Aug 2009 | A1 |
| 20090210098 | Nielsen et al. | Aug 2009 | A1 |
| 20090210284 | Nielsen et al. | Aug 2009 | A1 |
| 20090210285 | Nielsen et al. | Aug 2009 | A1 |
| 20090210297 | Nielsen et al. | Aug 2009 | A1 |
| 20090210298 | Nielsen et al. | Aug 2009 | A1 |
| 20090223355 | Manders | Sep 2009 | A1 |
| 20090233573 | Gray | Sep 2009 | A1 |
| 20090237408 | Nielsen et al. | Sep 2009 | A1 |
| 20090238414 | Nielsen et al. | Sep 2009 | A1 |
| 20090238415 | Nielsen et al. | Sep 2009 | A1 |
| 20090238416 | Nielsen et al. | Sep 2009 | A1 |
| 20090238417 | Nielsen et al. | Sep 2009 | A1 |
| 20090241045 | Nielsen et al. | Sep 2009 | A1 |
| 20090241046 | Nielsen et al. | Sep 2009 | A1 |
| 20090265430 | Bechtel | Oct 2009 | A1 |
| 20090324815 | Nielsen et al. | Dec 2009 | A1 |
| 20090327024 | Nielsen et al. | Dec 2009 | A1 |
| 20100006667 | Nielsen et al. | Jan 2010 | A1 |
| 20100010862 | Nielsen et al. | Jan 2010 | A1 |
| 20100010863 | Nielsen et al. | Jan 2010 | A1 |
| 20100010882 | Nielsen et al. | Jan 2010 | A1 |
| 20100010883 | Nielsen et al. | Jan 2010 | A1 |
| 20100033684 | Thiebaud | Feb 2010 | A1 |
| 20100034483 | Giuffrida | Feb 2010 | A1 |
| 20100084532 | Nielsen et al. | Apr 2010 | A1 |
| 20100085054 | Nielsen et al. | Apr 2010 | A1 |
| 20100085185 | Nielsen et al. | Apr 2010 | A1 |
| 20100085376 | Nielsen et al. | Apr 2010 | A1 |
| 20100085694 | Nielsen et al. | Apr 2010 | A1 |
| 20100085701 | Nielsen et al. | Apr 2010 | A1 |
| 20100086671 | Nielsen et al. | Apr 2010 | A1 |
| 20100086677 | Nielsen et al. | Apr 2010 | A1 |
| 20100088031 | Nielsen et al. | Apr 2010 | A1 |
| 20100088032 | Nielsen et al. | Apr 2010 | A1 |
| 20100088134 | Nielsen et al. | Apr 2010 | A1 |
| 20100088135 | Nielsen et al. | Apr 2010 | A1 |
| 20100088164 | Nielsen et al. | Apr 2010 | A1 |
| 20100090700 | Nielsen et al. | Apr 2010 | A1 |
| 20100090858 | Nielsen et al. | Apr 2010 | A1 |
| 20100091200 | Vigouroux | Apr 2010 | A1 |
| 20100094553 | Nielsen et al. | Apr 2010 | A1 |
| 20100097224 | Prodanovich | Apr 2010 | A1 |
| 20100117654 | Nielsen et al. | May 2010 | A1 |
| 20100146454 | Sugahara | Jun 2010 | A1 |
| 20100164787 | Khosravy et al. | Jul 2010 | A1 |
| 20100170453 | Betzer-Zilevitch | Jul 2010 | A1 |
| 20100188088 | Nielsen et al. | Jul 2010 | A1 |
| 20100188215 | Nielsen et al. | Jul 2010 | A1 |
| 20100188216 | Nielsen et al. | Jul 2010 | A1 |
| 20100188245 | Nielsen et al. | Jul 2010 | A1 |
| 20100188407 | Nielsen et al. | Jul 2010 | A1 |
| 20100189312 | Nielsen et al. | Jul 2010 | A1 |
| 20100189887 | Nielsen et al. | Jul 2010 | A1 |
| 20100198663 | Nielsen et al. | Aug 2010 | A1 |
| 20100201690 | Nielsen et al. | Aug 2010 | A1 |
| 20100201706 | Nielsen et al. | Aug 2010 | A1 |
| 20100205031 | Nielsen et al. | Aug 2010 | A1 |
| 20100205032 | Nielsen et al. | Aug 2010 | A1 |
| 20100205195 | Nielsen et al. | Aug 2010 | A1 |
| 20100205264 | Nielsen et al. | Aug 2010 | A1 |
| 20100205536 | Nielsen et al. | Aug 2010 | A1 |
| 20100205554 | Nielsen et al. | Aug 2010 | A1 |
| 20100205555 | Nielsen et al. | Aug 2010 | A1 |
| 20100228588 | Nielsen et al. | Sep 2010 | A1 |
| 20100245086 | Nielsen et al. | Sep 2010 | A1 |
| 20100247754 | Nielsen et al. | Sep 2010 | A1 |
| 20100253511 | Nielsen et al. | Oct 2010 | A1 |
| 20100253513 | Nielsen et al. | Oct 2010 | A1 |
| 20100253514 | Nielsen et al. | Oct 2010 | A1 |
| 20100255182 | Nielsen et al. | Oct 2010 | A1 |
| 20100256825 | Nielsen et al. | Oct 2010 | A1 |
| 20100256912 | Nielsen et al. | Oct 2010 | A1 |
| 20100256981 | Nielsen et al. | Oct 2010 | A1 |
| 20100257029 | Nielsen et al. | Oct 2010 | A1 |
| 20100257477 | Nielsen et al. | Oct 2010 | A1 |
| 20100259381 | Nielsen et al. | Oct 2010 | A1 |
| 20100259414 | Nielsen et al. | Oct 2010 | A1 |
| 20100262470 | Nielsen et al. | Oct 2010 | A1 |
| 20100262670 | Nielsen et al. | Oct 2010 | A1 |
| 20100263591 | Nielsen et al. | Oct 2010 | A1 |
| 20100268786 | Nielsen et al. | Oct 2010 | A1 |
| 20100285211 | Nielsen et al. | Nov 2010 | A1 |
| 20100318401 | Nielsen et al. | Dec 2010 | A1 |
| 20100318465 | Nielsen et al. | Dec 2010 | A1 |
| 20100324967 | Nielsen et al. | Dec 2010 | A1 |
| 20110006772 | Olsson | Jan 2011 | A1 |
| 20110007076 | Nielsen et al. | Jan 2011 | A1 |
| 20110020776 | Nielsen et al. | Jan 2011 | A1 |
| 20110022433 | Nielsen et al. | Jan 2011 | A1 |
| 20110035245 | Nielsen et al. | Feb 2011 | A1 |
| 20110035251 | Nielsen et al. | Feb 2011 | A1 |
| 20110035252 | Nielsen et al. | Feb 2011 | A1 |
| 20110035260 | Nielsen et al. | Feb 2011 | A1 |
| 20110035324 | Nielsen et al. | Feb 2011 | A1 |
| 20110035328 | Nielsen et al. | Feb 2011 | A1 |
| 20110040589 | Nielsen et al. | Feb 2011 | A1 |
| 20110040590 | Nielsen et al. | Feb 2011 | A1 |
| 20110045175 | Nielsen et al. | Feb 2011 | A1 |
| 20110046993 | Nielsen et al. | Feb 2011 | A1 |
| 20110046994 | Nielsen et al. | Feb 2011 | A1 |
| 20110046999 | Nielsen et al. | Feb 2011 | A1 |
| 20110060496 | Nielsen et al. | Mar 2011 | A1 |
| 20110060549 | Nielsen et al. | Mar 2011 | A1 |
| 20110095885 | Nielsen et al. | Apr 2011 | A9 |
| 20110131081 | Nielsen et al. | Jun 2011 | A1 |
| 20110135163 | Nielsen et al. | Jun 2011 | A1 |
| 20110137769 | Nielsen et al. | Jun 2011 | A1 |
| 20110236588 | Nielsen et al. | Sep 2011 | A1 |
| 20110279229 | Nielsen et al. | Nov 2011 | A1 |
| 20110279230 | Nielsen et al. | Nov 2011 | A1 |
| 20110279476 | Nielsen et al. | Nov 2011 | A1 |
| 20110282542 | Nielsen et al. | Nov 2011 | A9 |
| 20110283217 | Nielsen et al. | Nov 2011 | A1 |
| 20110285749 | Nielsen et al. | Nov 2011 | A1 |
| 20120019380 | Nielsen et al. | Jan 2012 | A1 |
| 20120036140 | Nielsen et al. | Feb 2012 | A1 |
| 20120065924 | Nielsen et al. | Mar 2012 | A1 |
| 20120065944 | Nielsen et al. | Mar 2012 | A1 |
| 20120066137 | Nielsen et al. | Mar 2012 | A1 |
| 20120066273 | Nielsen et al. | Mar 2012 | A1 |
| 20120066506 | Nielsen et al. | Mar 2012 | A1 |
| 20120069178 | Nielsen et al. | Mar 2012 | A1 |
| 20120072035 | Nielsen et al. | Mar 2012 | A1 |
| 20120110019 | Nielsen et al. | May 2012 | A1 |
| 20120113244 | Nielsen et al. | May 2012 | A1 |
| 20130006718 | Nielsen et al. | Jan 2013 | A1 |
| 20130085670 | Nielsen et al. | Apr 2013 | A1 |
| 20130101180 | Nielsen et al. | Apr 2013 | A1 |
| 20130103318 | Nielsen et al. | Apr 2013 | A1 |
| 20130116855 | Nielsen et al. | May 2013 | A1 |
| 20130135343 | Nielsen et al. | May 2013 | A1 |
| 20130147637 | Nielsen et al. | Jun 2013 | A1 |
| 20130162431 | Nielsen et al. | Jun 2013 | A1 |
| 20130174072 | Nielsen et al. | Jul 2013 | A9 |
| 20130182009 | Nielsen et al. | Jul 2013 | A1 |
| 20130186333 | Nielsen et al. | Jul 2013 | A1 |
| 20130194303 | Nielsen et al. | Aug 2013 | A1 |
| 20130231984 | Nielsen et al. | Sep 2013 | A1 |
| 20130233883 | Nielsen et al. | Sep 2013 | A1 |
| 20130251894 | Nielsen et al. | Sep 2013 | A1 |
| 20130265138 | Nielsen et al. | Oct 2013 | A1 |
| 20130268199 | Nielsen et al. | Oct 2013 | A1 |
| 20130287500 | Miller | Oct 2013 | A1 |
| 20130315449 | Nielsen et al. | Nov 2013 | A1 |
| 20140022272 | Nielsen et al. | Jan 2014 | A1 |
| 20140035587 | Nielsen et al. | Feb 2014 | A1 |
| 20140074970 | Nielsen et al. | Mar 2014 | A1 |
| 20140122149 | Nielsen et al. | May 2014 | A1 |
| 20140278661 | Nielsen et al. | Sep 2014 | A1 |
| 20140304041 | Nielsen et al. | Oct 2014 | A1 |
| 20140321717 | Nielsen et al. | Oct 2014 | A1 |
| 20140334878 | Miller | Nov 2014 | A1 |
| 20140347396 | Nielsen et al. | Nov 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2386200 | Apr 2000 | CA |
| 2435290 | Aug 2002 | CA |
| 2458050 | Mar 2003 | CA |
| 2510111 | Jul 2004 | CA |
| 2641355 | Aug 2007 | CA |
| 100324 | Feb 1984 | EP |
| 522862 | Jan 1993 | EP |
| 0636393 | Feb 1995 | EP |
| 683401 | Nov 1995 | EP |
| 890927 | Jan 1999 | EP |
| 1281816 | Feb 2003 | EP |
| 1521331 | Apr 2005 | EP |
| 1635299 | Mar 2006 | EP |
| 1679232 | Jul 2006 | EP |
| 1726722 | Nov 2006 | EP |
| 1852365 | Nov 2007 | EP |
| 2266863 | Nov 1993 | GB |
| 7128061 | May 1995 | JP |
| 7128061 | May 1995 | JP |
| 11072348 | Mar 1999 | JP |
| 11072348 | Mar 1999 | JP |
| 2001043471 | Feb 2001 | JP |
| 2001043471 | Feb 2001 | JP |
| 2001319016 | Nov 2001 | JP |
| 2001319016 | Nov 2001 | JP |
| 2005327228 | Nov 2005 | JP |
| 2005327228 | Nov 2005 | JP |
| 2006003206 | Jan 2006 | JP |
| 2006003206 | Jan 2006 | JP |
| 2006189930 | Jul 2006 | JP |
| 2006189930 | Jul 2006 | JP |
| 2006236292 | Sep 2006 | JP |
| 2006236292 | Sep 2006 | JP |
| WO-9112119 | Aug 1991 | WO |
| WO-9424584 | Oct 1994 | WO |
| WO-9516827 | Jun 1995 | WO |
| WO-9629572 | Sep 1996 | WO |
| WO-9844364 | Oct 1998 | WO |
| WO-9854600 | Dec 1998 | WO |
| WO-9854601 | Dec 1998 | WO |
| WO-9900679 | Jan 1999 | WO |
| WO-0228541 | Apr 2002 | WO |
| WO-2004100044 | Nov 2004 | WO |
| WO-2004102242 | Nov 2004 | WO |
| WO-2005052627 | Jun 2005 | WO |
| WO2006013338 | Feb 2006 | WO |
| WO-2006015310 | Feb 2006 | WO |
| WO-2006069383 | Jun 2006 | WO |
| WO-2006136776 | Dec 2006 | WO |
| WO-2006136777 | Dec 2006 | WO |
| WO-2007014072 | Feb 2007 | WO |
| WO-2007067898 | Jun 2007 | WO |
| WO-2007128050 | Nov 2007 | WO |
| WO-2008112461 | Sep 2008 | WO |
| Entry |
|---|
| CGA 3.0, “Common Ground Alliance, Best Practices Version 3.0,” Mar. 2006, 100 pages. |
| CGA, “Common Ground Alliance, Best Practices Version 3.0,” Mar. 2006, 100 pages. |
| Binder 1: “Virginia Utility Protection Service, Inc. Response to US Patent Application Publication . . . ,” pp. DY0001-DY0755, Nov. 3, 2010. |
| Binder 2: “Patent US 2009 0237408,” pp. DY0756-DY1271, Nov. 3, 2010. |
| Binder 3: “Patent US 2009 0238414,” pp. DY1272-DY2210, Nov. 3, 2010. |
| Binder 4: “Patent US 2009 0238415,” pp. DY2211-DY3308, Nov. 3, 2010. |
| Binder 5: “Patent US 2009 0238416,” pp. DY3309-DY3889, Nov. 3, 2010. |
| Binder 6: “Patent US 2009 0238417,” pp. DY3890-DY4133, Nov. 3, 2010. |
| Binder 7: “Patent US 2009 0241045,” pp. DY4134-DY4276, Nov. 3, 2010. |
| Binder 8: “Patent US 2009 0241046,” pp. DY4277-DY4499, Nov. 3, 2010. |
| R. Pevarski, Letter from the Virginia Utility Protection Service, Inc., dated Apr. 7, 2010. |
| H.L. Smith, Letter dated Oct. 27, 2010. |
| H.L Smith, Letter dated Jan. 14, 2011, with two attachments each dated Jan. 5, 2011. |
| 360 Scheduling, 360 Concepts Guide 4.9.6 User Guide, 360 Technologies Ltd., Nottingham, UK, 2005-2008, 99 pages. |
| Alabama 1 Call, Annual Operations Report, 2005, 32 pages, selected pages from website http://www.a11call.com, printed on Apr. 2, 2009 (original publication date unknown). |
| Alabama 1 Call, GeoRemote, Remote Ticket Entry Manual, 35 pages, selected pages from website http://www.a11call.com, printed on Apr. 2, 2009 (original publication date unknown). |
| Alabama 1 Call, Guidelines and Requirements, 1 page, http://www.a11call.com/rte—proc.html, printed on Apr. 14, 2009 (original publication date unknown). |
| Bearden, T., “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. |
| Blue Stakes of Utah Utility Notification Center, Inc., Association Newsletter, vol. 1, No. 1, 8 pages, Nov. 1, 2005. |
| Blue Stakes of Utah Utility Notification Center, Inc., Association Newsletter, vol. 1, No. 2, 5 pages, Jul. 15, 2006. |
| Blue Stakes of Utah Utility Notification Center, Inc., Association Newsletter, vol. 3, No. 1, 7 pages, Nov. 2007. |
| Blue Stakes of Utah Utility Notification Center, Inc., Association Newsletter, vol. 4, No. 1, pp. 1-8, Nov. 2008. |
| Blue Stakes of Utah Utility Notification Center, Inc., Association Newsletter, vol. 5, No. 1, 7 pages, Dec. 2009. |
| Carey, B., “Tracking Shoes,” Chicago Tribune Online Edition, Jan. 29, 2007, pp. 1-3, http://www.chicagotribune.com/services/site/premium/access-registered.intercept. |
| Case Study: Wireless mash-up keeps track of Vegas' pipes, TechWorld, http://howto.techworld.com/mobile-wireless/2297/case-study-wireless-mash-up-keeps tra . . . , printed Dec. 16, 2009 (original publication date unknown), 2 pages. |
| CGA, Common Ground Alliance, Best Practices, Version 1.0, Apr. 2003, 93 pages. |
| CGA, Common Ground, Study of One-Call Systems and Damage Prevention Best Practices, Aug. 1999, 262 pages. |
| DigSafely New York, i-Notice, http://www.ufpo.org/excv/Inotice/, (original publication date unknown), printed Jun. 5, 2010, 4 pages. |
| Eastern Virginia Damage Prevention Committee, Meeting Minutes, Mar. 26, 2009 and May 12, 2009, 6 pages. |
| ESRI Corporate Introduction, http://www.esri.com/library/brochures/pdfs/corporate-intro.pdf, printed on Dec. 9, 2009 (original publication date unknown). |
| 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. |
| Fredericksburg Area Damage Prevention Committee, Meeting Minutes, Dec. 2009. |
| Georgia UPC EDEN, Web Entry Instruction Manual, www.gaupc.org, Jan. 22, 2009, 60 pages. |
| Gopher State One Call—History and Background, http://www.gopherstateonecall.org/history.aspx, printed on Dec. 12, 2009 (original publication date unknown), 2 pages. |
| Gopher State One Call—Virtual Polygon Fact Sheet, http://www.gopherstateonecall.org/docs/Virtual%20Polygon%20Fact%20Sheet.pdf, printed on Dec. 16, 2009 (original publication date unknown), 4 pages. |
| GPS Technology Enhancing Underground Utility Locating, Underground Construction Magazine, Apr. 2010, 3 pages. |
| Hanneman, J., “Notification and the NMOC Map System,” http://nmonecall.org/articles.htm, printed on Dec. 16, 2009 (original publication date unknown), 10 pages. |
| Illinois One-Call System, NEWTIN Remote Ticket Entry User's Manual, Jun. 12, 2007, 29 pages. |
| International Search Report (Partial), Application Serial No. PCT/US2009/005401, Mar. 3, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/2009/05416, Jun. 7, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/2009/05443, Apr. 5, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/2010/000130, May 18, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/2010/000131, Apr. 23, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/2010/000343, 11 pages. |
| International Search Report and Written Opinion, Application Serial No. PCT/2010/000389, 11 pages. |
| International Search Report and Written Opinion, Application Serial No. PCT/2010/00378 , Apr. 20, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2008/55796, Oct. 14, 2008. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2008/55798, Jul. 28, 2008. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/000859, Apr. 14, 2009. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/005299, Dec. 22, 2009. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/005348, Mar. 2, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/005359, Feb. 8, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/005401, Jun. 18, 2010, 18 pages. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/005413, Feb. 8, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/005444, Feb. 8, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2009/01707, May 14, 2009, 13 pages. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2010/000997, Jun. 15, 2010. |
| International Search Report and Written Opinion, Application Serial No. PCT/US2010/000998, Jun. 29, 2010. |
| IRTH Internet Manual, Arizona Bluestake, Call Before you Dig, http://www.azbluestake.com/main/download/IRTHNetFeatures.pdf, (original publication date unknown), 47 pages. |
| IRTH Internet Manual, Georgia Utilities Protection Center, Feb. 16, 2006, 20 pages. |
| IRTH One Call Centers, Underground Utility Damage Prevention, Ticket Management, http://www.irth.com/SOLUTIONS/IRTH—ONE—CALL/index.aspx, (original publication date unknown), 2 pages. |
| Letter from Norfield Data Products to Wolf Greenfield & Sacks, P.C., May 5, 2010, 2 pages. |
| MALA Application Note—Using MALA GPR systems with GPS equipment, Printed Matter No. 2894, 5 pages, www.malags.se, printed Apr. 9, 2010 (original publication date unknown). |
| MALA Application Note—Visualizing GPR data in Google Earth using MALA GPS Mapper, Printed Matter No. 2896, 3 pages, www.malags.se, printed Apr. 9, 2010 (original publication date unknown). |
| MALA GPS Mapper—Processing, 1 page, http://www.malags.se/Downloads/Software/processing/MALA-GPS-Mapper.aspx, printed on Apr. 9, 2010 (original publication date unknown). |
| MALA GPS Mapper—Product Releases, Sep. 19, 2007, 1 page, http://www.malags.se/News-and-Events/Product-Releases/MALA-GPS-Mapper.aspx, printed Apr. 9, 2010. |
| MALA Object Mapper—Processing, 1 page, http://www.malags.se/Downloads/Software/Processing/Object-Mapper.aspx, printed Apr. 9, 2010 (original publication date unknown). |
| North Carolina One-Call Center, Newtin Remote Ticket Entry Application Tutorial, Sep. 17, 2009, 24 pages. |
| North Carolina One-Call Center, Newtin Remote Ticket Entry Quick Map Tutorial, Nov., 2008, 13 pages. |
| Notice of Allowance dated Nov. 6, 2009 from Co-Pending U.S. Appl. No. 11/685,602. |
| NTDPC One-Call Mapping Notification Processes, http://www.ntdpc.com/ntdpc/faces/ntscf.jsp, (original publication date unknown), 12 pages. |
| Office Action dated Jun. 16, 2010 from Co-Pending Canadian Application No. 2,691,707, filed Feb. 10, 2010. |
| Office Action dated Nov. 18, 2009 from Co-Pending Canadian Application No. 2,623,466, filed Mar. 4, 2008. |
| Office Action dated Nov. 23, 2009 from Co-Pending Canadian Application No. 2,623,761, filed Mar. 4, 2008. |
| Office Action dated Apr. 28, 2009 from Co-Pending U.S. Appl. No. 11/685,602. |
| Office Action dated Sep. 17, 2009 from Co-Pending U.S. Appl. No. 11/685,602. |
| One Call Concepts Inc.—Company News & Executive Profiles, BNET Industries, http://resources.bnet.com/topic/one—call+concepts+inc..html, printed on Dec. 15, 2009 (original publication date unknown), 6 pages. |
| One Call Concepts Inc.—Prism Software, http://www.occinc.com/services/prism—software.asp, printed on Dec. 16, 2009 (original publication date unknown), 1 page. |
| Pevarski, R., 'Virginia Pilot Project: Technology Meets Damage Prevention, http://www.excavationsafetyonline.com/esg/guidePDFs/2009—2009—ESG—Page—9.pdf, printed on Nov. 3, 2009, 1 page. |
| Pickus, J., “Call USA—Automating “Call Before You Dig” Processes for a Major Utility,” GITA's Annual Conference on Apr. 25-28, 2004, 19 pages. |
| Pickus, J., “Internet GIS for the Municipality,” Las Vegas Water District, http://spatialnews.geocomm.com/geonetcom/seminar3.html, printed Dec. 16, 2009 (original publication date unknown), 3 pages. |
| Polaris Workforce Solutions, 2 pages, http://www.polarisworkforce.com, printed on Apr. 26, 2010 (original publication date unknown). |
| Schutzberg, A., “Autodesk Positions Itself for 2008 and Beyond,” Location Intelligence Articles, Feb. 22, 2008, http://www.locationintelligence.net/articles/2693.html, printed Dec. 16, 2009, 4 pages. |
| Stocking, A., “Betting on Technology,” Mar. 2007, http://www.resources.autodesk.com/files/government/customer—stories/A137-LVTBVWD—Municipal—Sewer—and—Water—article.pdf, 3 pages. |
| Trimble Navigation Limited, “H-Star Technology Explained,” pp. 1-9, 2005, www.trimble.com. |
| Utility Notification Center—Membership Details, http://www.callbeforeyoudig.org/himember.htm, printed on Dec. 12, 2009 (original publication date unknown), 12 pages. |
| Utility Notification Center of Colorado, Annual Report for Fiscal Year 2004, 41 pages. |
| Utility Notification Center of Colorado, Annual Report for Fiscal Year 2005, 39 pages. |
| Utility Notification Center of Colorado, Annual Report for Fiscal Year 2006, 49 pages. |
| Utility Notification Center of Colorado, Annual Report for Fiscal Year 2007, 44 pages. |
| Utility Notification Center of Colorado, Annual Report for Fiscal Year 2008, 39 pages. |
| Virginia Pilot Project for One-call Location Technology, Project Plan, Aug. 2006, 28 pages. |
| Virginia Pilot Project, Incorporating GPS Technology to Enhance One-Call Damage Prevention, Phase I—Electronic White Lining Project Report, Nov. 2007, 50 pages. |
| Co-pending U.S. Appl. No. 12/704,485, filed Feb. 11, 2010. |
| Co-pending U.S. Appl. No. 12/833,103, filed Jul. 9, 2010. |
| Co-pending U.S. Appl. No. 12/833,117, filed Jul. 9, 2010. |
| Co-pending U.S. Appl. No. 12/833,127, filed Jul. 9, 2010. |
| U.S. Appl. No. 12/204,454, filed Sep. 4, 2008, Nielsen et al. |
| U.S. Appl. No. 12/364,339, filed Feb. 2, 2009, Nielsen et al. |
| U.S. Appl. No. 12/432,849, filed Apr. 30, 2009, Nielsen et al. |
| U.S. Appl. No. 12/432,860, filed Apr. 30, 2009, Nielsen et al. |
| U.S. Appl. No. 12/432,870, filed Apr. 30. 2009, Nielsen et al. |
| U.S. Appl. No. 12/432,878, filed Apr. 30, 2009, Nielsen et al. |
| U.S. Appl. No. 12/432,909, filed Apr. 30, 2009, Nielsen et al. |
| U.S. Appl. No. 12/493,109, filed Jun. 26, 2009, Nielsen et al. |
| U.S. Appl. No. 12/537,732, filed Aug. 7, 2009, Nielsen et al. |
| U.S. Appl. No. 12/537,856, filed Aug. 7, 2009, Nielsen et al. |
| U.S. Appl. No. 12/537,894, filed Aug. 7, 2009, Nielsen et al. |
| U.S. Appl. No. 12/537,917, filed Aug. 7, 2009, Nielsen et al. |
| U.S. Appl. No. 12/571,356, filed Sep. 30, 2009, Nielsen et al. |
| U.S. Appl. No. 12/572,202, filed Oct. 1, 2009, Nielsen et al. |
| U.S. Appl. No. 12/572,260, filed Oct. 1, 2009, Nielsen et al. |
| U.S. Appl. No. 12/850,187, filed Aug. 4, 2010, Nielsen et al. |
| U.S. Appl. No. 12/850,712, filed Aug. 5, 2010, Nielsen et al. |
| CGA, Common Ground Alliance, Best Practices, Version 3.0, Mar. 2006, 100 pages. |
| CGA, Common Ground Alliance, Best Practices, Version 5.0, Mar. 2008, http://web.archive.org/web/20101009040317/http://www.commongroundalliance.com/Content/NavigationMenu/Best—Practices/Best—Practices—2008/BP—5.0—March2008—Fial.pdf. |
| Charlton, B.G. et al., “Auditing as a tool of public policy—The misuse of quality assurance techniques in the UK university expansion,” Final draft of a paper published in European Political Science 2002; 2: 24-35. |
| GPS Visualizer: Free geocoder: Convert address to coordinates, http://web.archive.org/web/20070304090412/http://www.gpsvisualizer.com/geocoding.html, Mar. 2007, 1 page. |
| Haas, J. et al., “Feed the FLAME—Utility Integrates Field Applications,” GeoWorld, Mar. 2007, 5 pages, online: Systems Integration Articles/Enspiria Solutions. |
| International Search Report and Written Opinion, Application No. PCT/2010/00406, Aug. 30, 2010. |
| International Search Report and Written Opinion, Application No. PCT/US2009/03810, Aug. 17, 2010. |
| Office Action dated Feb. 1, 2011 from Canadian Application No. 2,691,707. |
| Office Action dated Apr. 28, 2011 from U.S. Appl. No. 12/204,454. |
| Office Action dated Jul. 8, 2010 from Canadian Application No. 2,691,780, filed Feb. 10, 2010. |
| Office Action dated Sep. 26, 2011 from Canadian Application No. 2,739,090. |
| Office Action dated Sep. 26, 2011 from Canadian Application No. 2,739,110. |
| Office Action dated Sep. 27, 2011 from Canadian Application No. 2,739,094. |
| Office Action dated Oct. 11, 2011 from U.S. Appl. No. 12/432,849. |
| Office Action dated Oct. 11, 2011 from U.S. Appl. No. 12/432,878. |
| Office Action dated Oct. 11, 2011 from U.S. Appl. No. 12/432,909. |
| Office Action dated Nov. 21, 2011 from U.S. Appl. No. 12/204,454. |
| Office Action dated Dec. 6, 2011 from U.S. Appl. No. 12/432,870. |
| Office Action dated Dec. 7, 2011 from U.S. Appl. No. 12/537,856. |
| Office Action dated Dec. 9, 2011 from U.S. Appl. No. 12/493,109. |
| Office Action dated Dec. 13, 2011 from U.S. Appl. No. 12/537,894. |
| Office Action dated Dec. 22, 2011 from U.S. Appl. No. 12/537,732. |
| One Call Concepts Locating Services, Inc., Point Positive Utility Mapping & GIS, http://www.occls.com/Default.aspx?content=pointpositive, original publication date unknown, retrieved Sep. 21, 2011, 1 page. |
| Pelican Corp., beforeUdig mobile, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=145&Itemid=133, original publication date unknown, printed Aug. 30, 2011, 1 page. |
| Pelican Corp., DigSAFE OneCall Key Capabilities, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=104&Itemid=121, original publication date unknown, printed Aug. 30, 2011, 2 pages. |
| Pelican Corp., DigSAFE Pro Automated Plan Response Server, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=48&Itemid=68, original publication date unknown, printed Aug. 30, 2011, 2 pages. |
| Pelican Corp., DigSAFE Pro Automation Workflow, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=119&Itemid=124, original publication date unknown, printed Aug. 30, 2011, 2 pages. |
| Pelican Corp., DigSAFE Pro New and Updated features for version 2.4, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=151&Itemid=91, original publication date unknown, printed Aug. 30, 2011, 2 pages. |
| Pelican Corp., How beforeUdig works, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=114&Itemid=105, original publication date unknown, printed Aug. 30, 2011, 1 page. |
| Pelican Corp., Using beforeUdig, http://www.pelicancorp.com/index.php?option=com—content&view=article&id=115&Itemid=106, original publication date unknown, printed Aug. 30, 2011, 1 page. |
| Stahovich, David M. et al., “Automated and Integrated Call Before You Dig,” Proceedings of GITA 2005, GITA's 18th Annual Conference, Mar. 6-9, 2005, Denver, CO, online: GIS for Oil & Gas Conference 2002 <http://www.gisdevelopment.net/proceedings/gita/2005/papers/76.pdf>. |
| Tetra Tech NUS, “Standard Operation Procedures,” Dec. 2003 [retrieved on Jul. 27, 2010, http://htl.mclinc.org/%5CWillowGroveNASAdminRecord%5CPdfs%5CFinal21345—appendA.pdf>, 315 pages. |
| Whiting, P., “No role for quality scores in systematic reviews of diagnostic accuracy studies,” BMC Medical Research Methodology, 2005, 5:19, 9 pages. |
| U.S. Appl. No. 12/571,408, filed Sep. 30, 2009, Nielsen et al. |
| CARDNO TBE, “Locating Underground Utilities Before Construction,” Airport Facilities, Fall 2004, http://www.subsurfaceutilityengineering.com/articles/Locating—Utilities.asp, 2 pages. |
| Notice of Allowance dated Apr. 17, 2012 from U.S. Appl. No. 12/432,870. |
| Office Action dated Feb. 14, 2012 from U.S. Appl. No. 12/833,103. |
| Office Action dated Feb. 29, 2012 from U.S. Appl. No. 12/704,485. |
| Office Action dated Feb. 29, 2012 from U.S. Appl. No. 12/833,117. |
| Office Action dated Feb. 29, 2012 from U.S. Appl. No. 12/833,127. |
| Office Action dated Mar. 19, 2012 from U.S. Appl. No. 12/204,454. |
| Office Action dated Apr. 4, 2012 from U.S. Appl. No. 12/572,202. |
| Office Action dated May 9, 2012 from U.S. Appl. No. 12/432,909. |
| Office Action dated May 11, 2012 from Australian Application No. 2009300343. |
| Office Action dated May 22, 2012 from U.S. Appl. No. 12/432,849. |
| Office Action dated May 22, 2012 from U.S. Appl. No. 12/572,260. |
| Office Action dated May 22, 2012 from U.S. Appl. No. 12/432,878. |
| Office Action dated May 31, 2012 from Australian Application No. 2009300323. |
| Office Action dated Jun. 1, 2012 from Australian Application No. 2009300342. |
| Office Action dated Jun. 14, 2012 from U.S. Appl. No. 12/432,860. |
| Office Action dated Jul. 9, 2012 from U.S. Appl. No. 12/493,109. |
| Office Action dated Jul. 12, 2012 from U.S. Appl. No. 12/537,856. |
| Office Action dated Jul. 16, 2012 from Canadian Application No. 2,691,780. |
| Office Action dated Jul. 26, 2012 from Canadian Application No. 2,712,126. |
| Office Action dated Apr. 24, 2013 from U.S. Appl. No. 12/432,909. |
| Office Action dated Apr. 29, 2013 from U.S. Appl. No. 12/432,849. |
| Office Action dated Jul. 26, 2013 from Canadian Application No. 2,706,195. |
| Office Action dated Jul. 8, 2013 from U.S. Appl. No. 12/840,467. |
| Bauer, S. et al., “Quantification of groundwater contamination in an urban area using integral pumping tests,” Journal of Contaminant Hydrology; vol. 75, Issues 3-4; Dec. 2004, pp. 183-213. |
| Holder, T. et al., A new approach for source zone characterization: the Neckar Valley study. Groundwater Quality: Remediation and Protection, IAHS Publication, vol. 250, IAHS Press, Wallingford, Oxfordshire, UK, pp. 49-55. |
| Maqsood, I et al., Simulation-based risk assessment of contaminated sites under remediation scenarios, planning periods, and land-use patterns-a Canadian case study, Stoch Environ Res Risk Assess 2005, 19:146-157. |
| Mike Herbert, Karel Kovar, Universitat Tubingen Geological Institute “Groundwater Quality: Remediation and Projection” IAHS Publication No. 250, Proceedings of the GQ conference held in Tubingen, German from Sep. 21 to 25 (1998). |
| Office Action dated Jun. 3, 2013 from Canadian Application No. 2,691,780. |
| Office Action dated Jun. 20, 2013 from U.S. Appl. No. 12/833,127. |
| Patent Examination Report No. 2, Australian Application No. 2009300342, Jul. 1, 2013. |
| Schwarz, R. et al., 1998 Groundwater risk assessment at contaminated sites: a new investigation approach. In: Herbert, M., Kovar, K. (Eds.), GQ'98 Groundwater Quality: Remediation and Protection, IAHS Publication, vol. 250, pp. 68-71. |
| Notice of Allowance dated Jun. 21, 2013 from U.S. Appl. No. 12/572,260. |
| Office Action dated Jun. 19, 2013 from U.S. Appl. No. 12/704,485. |
| Patent Examination Report No. 2, Australian Application No. 2009300323, May 29, 2013. |
| Office Action dated Jun. 20, 2013 from U.S. Appl. No. 12/833,117. |
| Office Action dated Aug. 21, 2013 from Canadian Application No. 2,739,110. |
| Office Action dated Aug. 29, 2013 from U.S. Appl. No. 13/465,524. |
| Notice of Allowance dated Aug. 21, 2013 from U.S. Appl. No. 12/850,187. |
| Office Action dated Oct. 9, 2013 from U.S. Appl. No. 13/186,116. |
| Weld County: Department of Public Works, “Permits and Applications—Public Works,” available online Jun. 7, 2010 at http://www.co.weld.co.us/Departments/PublicWorks/Permits/Applications.html. |
| Office Action dated Oct. 10, 2013 from U.S. Appl. No. 12/850,712. |
| Notice of Allowance dated May 20, 2013 from U.S. Appl. No. 12/432,860. |
| Office Action dated May 23, 2013 from U.S. Appl. No. 12/572,202. |
| U.S. Appl. No. 14/075,011, filed Nov. 8, 2013, Nielsen et al. |
| Office Action dated Mar. 26, 2014 from U.S. Appl. No. 12/537,917. |
| Office Action dated Mar. 7, 2014 from U.S. Appl. No. 12/432,878. |
| Office Action dated Mar. 26, 2014 from U.S. Appl. No. 12/204,454. |
| Office Action dated Apr. 9, 2014 from U.S. Appl. No. 12/537,732. |
| Office Action dated Sep. 24, 2013 from Canadian Application No. 2,739,094. |
| Office Action dated Oct. 16, 2013 from Canadian Application No. 2,691,780. |
| Office Action dated Aug. 29, 2013 from Canadian Application No. 2,739,090. |
| Office Action dated Sep. 24, 2013 from Canadian Application No. 2,739,090. |
| Office Action dated Oct. 8, 2013 from Canadian Application No. 2,692,110. |
| Notice of Allowance dated Nov. 26, 2013 from U.S. Appl. No. 12/833,103. |
| Office Action dated Nov. 12, 2013 from Canadian Application No. 2,712,126. |
| Notice of Allowance dated Dec. 16, 2013 from U.S. Appl. No. 12/704,485. |
| Common Ground Alliance, Mar. 2008, “Best Practices Version 5.0”, archived online: CGA | Best Practices 2008 <http://web.archive.org/web/20101009040317/http://www.commongroundalliance.com/Content/NavigationMenu/Best—Practices—2008/BP—5.0—March2008—Final.pdf[Best Practices 5.0]. |
| Office Action dated Feb. 11, 2014 from Canadian Application No. 2,729,590. |
| Office Action dated Feb. 11, 2014 from U.S. Appl. No. 12/432,849. |
| Office Action dated Feb. 20, 2014 from Canadian Application No. 2,691,780. |
| Turner, R., “Standard Operating Procedures,” Appendix A for Sampling and Analysis Plan for Interim Groundwater Monitoring Site 3—Ninth Street Landfill (Tetra Tech NUS, 2008), retrieved online at: Horsham Township Library: Willow Grove Naval Air Station Administrative Record Index <http://htl.mclinc.org/%5CWillowGroveNASAdminRecord%5CPdfs%5CFnial21345—appendA.pdf. |
| Office Action dated Jan. 15, 2014 from U.S. Appl. No. 12/432,909. |
| Office Action dated Jul. 17, 2014 from U.S. Appl. No. 12/537,894. |
| Office Action dated Aug. 4, 2014 from U.S. Appl. No. 12/833,127. |
| Office Action dated May 22, 2014 from U.S. Appl. No. 12/850,712. |
| Office Action dated May 23, 2014 from U.S. Appl. No. 12/537,894. |
| Office Action dated Jun. 10, 2014 from U.S. Appl. No. 13/465,524. |
| Office Action dated Jul. 30, 2014 from U.S. Appl. No. 12/572,202. |
| Office Action dated Jul. 31, 2014 from U.S. Appl. No. 12/833,117. |
| Office Action dated Jun. 19, 2013 from U.S. Appl. No. 12/833,103. |
| Office Action dated Oct. 31, 2013 from U.S. Appl. No. 12/572,202. |
| U.S. Appl. No. 14/579,223, filed Dec. 22, 2014, Nielsen et al. |
| Office Action dated Feb. 11, 2015 from U.S. Appl. No. 12/493,109. |
| Office Action dated Dec. 18, 2014 from U.S. Appl. No. 12/537,917. |
| Notice of Allowance dated Oct. 24, 2014 from U.S. Appl. No. 14/075,011. |
| Office Action dated Jan. 12, 2015 from U.S. Appl. No. 12/571,356. |
| Office Action dated Nov. 19, 2014 from U.S. Appl. No. 12/204,454. |
| Office Action dated Sep. 29, 2014 from Canadian Application No. 2,691,780. |
| Office Action dated Sep. 2, 2014 from Canadian Application No. 2,729,590. |
| Patent Examination Report dated Sep. 5, 2014 from Australian Application No. 2010358572. |
| S&N Locating Services, LLC's and S&N Communications, Inc.'s First Amended Answer, Affirmative Defenses, and Counterclaims to Plaintiff's First Amended Complaint filed Jan. 23, 2015; Case No. 2:13-cv-346 (MSD) (TEM); CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| CertusView's Objections to The Magistrate Judge's Order Allowing S&N's Amended Answer and Counterclaims filed Feb. 2, 2015; Case No. 2:13-cv-346 (MSD) (TEM); CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Office Action dated Apr. 8, 2015 from U.S. Appl. No. 12/432,878. |
| Notice of Allowance dated Apr. 8, 2015 from U.S. Appl. No. 14/665,518. |
| Office Action dated Apr. 8, 2015 from U.S. Appl. No. 12/204,454. |
| Office Action dated Mar. 20, 2015 from Canadian Application No. 2,739,110. |
| Office Action dated Mar. 17, 2015 from Canadian Application No. 2,712,126. |
| Office Action dated Mar. 17, 2015 from Canadian Application No. 2,739,090. |
| First Action Interview Pre-Interview Communication dated Apr. 23, 2015 from U.S. Appl. No. 14/332,352. |
| Grant, Anthony M., Workplace, Executive and Life Coaching: An Annotated Bibliography from the Behavioural Science Literature, Coaching Publications from 1937 to Jul. 2008, 87 pages. |
| Office Action dated Apr. 24, 2015 from Canadian Application No. 2,776,434. |
| Office Action dated May 7, 2015 from U.S. Appl. No. 12/537,894. |
| Office Action dated Jun. 5, 2015 from U.S. Appl. No. 12/537,856. |
| Section 330523-1 Guidelines for Utility Horizontal Directional Borings, published on Oct. 26, 2007 at www.nashville.gov, 9 pages. |
| Notice of Filing of Defendants' Second Amended Answer and Counterclaims filed Jun. 12, 2015; Case No. 2:13-cv-346 (MSD) (TEM); CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| S&N Locating Services, LLC's and S&N Communications, Inc.'s Second Amended answer, Affirmative Defenses, and Counterclaims to Plaintiff's First Amended Complaint filed Jun. 12, 2015; Case No. 2:13-cv-346 (MSD) (TEM); CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Opinion and Order Following Motion for Judgment on Pleadings, Jan. 21, 2015; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; (Eastern District of Virginia). |
| Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit A to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al. (Eastern District of Virginia). |
| Exhibit J to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-1 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al. (Eastern District of Virginia). |
| Exhibit J-2 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-3 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al. (Eastern District of Virginia). |
| Exhibit J-4 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-5 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-6 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-7 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al. (Eastern District of Virginia). |
| Exhibit J-8 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-9 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-10 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-11 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-12 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-13 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-14 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-15 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-16 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-17 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-18 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-19 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-20 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-21 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-22 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Exhibit J-23 to Memorandum of Law in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 4, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| CertusView's Response in Opposition to S&N's Motion for Exceptional Case Finding and Attorneys' Fees filed Feb. 27, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Reply in Support of Defendants' Motion for Exceptional Case Finding and Attorneys' Fees filed Mar. 9, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Memorandum Order regarding Functional Equivalency Objections and Sanctions Objections filed Mar. 11, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Office Action dated Mar. 25, 2015 from U.S. Appl. No. 14/063,417. |
| Office Action dated Mar. 20, 2015 from U.S. Appl. No. 12/572,202. |
| Office Action dated Mar. 20, 2015 from U.S. Appl. No. 12/833,117. |
| Office Action dated Mar. 19, 2015 from U.S. Appl. No. 12/833,127. |
| Office Action dated Feb. 9, 2015 from Canadian Application No. 2,729,590. |
| Office Action dated Jul. 7, 2015 from Canadian Application No. 2,739,094. |
| Patent Examination Report dated Jun. 29, 2015 from Australian Application No. 2014201054. |
| Memorandum in Support of CertusView's Motion for Summary Judgment on S&N's Inequitable Conduct Counterclaims filed Jul. 22, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia) (Parts 1, 2, 3 and 4). |
| Memorandum in Support of S&N's Response to CertusView's Motion for Summary Judgment on S&N's Inequitable Conduct Counterclaims filed Jul. 29, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| CertusView's Reply in Support of its Motion for Summary Judgment on S&N's Inequitable Conduct Counterclaims filed Aug. 3, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Memorandum Order filed Aug. 7, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia) |
| Office Action dated Sep. 1, 2015 from Canadian Application No. 2,897,462. |
| Office Action dated Aug. 5, 2015 from U.S. Appl. No. 13/465,524. |
| Supplemental Notice of Allowability dated Aug. 31, 2015 from U.S. Appl. No. 12/572,202. |
| Notice of Allowance and Issue Fee Due dated Jul. 31, 2015 from U.S. Appl. No. 12/571,356. |
| Examiners Answer to Appeal Brief dated Aug. 28, 2015 from U.S. Appl. No. 12/543,849. |
| Examiners Answer to Appeal Brief dated Aug. 20, 2015 from U.S. Appl. No. 12/432,909. |
| Examiners Answer to Appeal Brief dated Aug. 20, 2015 from U.S. Appl. No. 12/537,732. |
| Office Action dated Aug. 11, 2015 from U.S. Appl. No. 12/537,917. |
| Notice of Allowance dated Aug. 7, 2015 from U.S. Appl. No. 12/572,202. |
| Number | Date | Country | |
|---|---|---|---|
| 20100318402 A1 | Dec 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61151826 | Feb 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12704485 | Feb 2010 | US |
| Child | 12833121 | US |
