Patent Grant
9235821
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.
In the construction industry, for example, the process of locating and marking underground facilities is an example of a field service application, often referred to as a “locate and marking operation” (or more simply referred to as a “locate operation”). In locate operations, a locate technician may use one or more locate devices (e.g., a locate transmitter and a locate receiver) and a marking device in order to perform the locate operation. A locate receiver is an instrument for detecting the presence or absence of facilities that are concealed in some manner, such as cables and pipes that are located underground. A locate receiver is used to detect electromagnetic fields that are generated by a detection signal that is emitted from the facility (the detection signal typically is provided to the facility via a locate transmitter). A signal, or lack thereof, detected by the locate receiver indicates the presence or absence of the facility.
Once the presence or absence of the facility is detected, a marking material is dispensed on, for example, the surface of the ground at the location of the 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.
With respect to locate operations, there may be an associated work request (i.e., locate request, also referred to as locate request ticket or merely “ticket”) that is originated by, for example, an excavator or other party who wishes to ascertain and/or mark the presence or absence of one or more underground facilities in a certain geographic region. A locate request may be any communication or instruction to perform a locate operation at a certain work site, or in some cases multiple work sites, at which one or more dig areas may be designated for planned excavation (or more generally, some disturbance of the ground). Today, excavators and other parties are required to notify one-call centers in advance of their excavation activities and identify through the locate request the work site(s)/dig area(s) where individual excavating activities/disturbances of the ground are planned. One-call centers may be any organizations, entities, and/or systems that receive, process, and/or transmit locate requests.
The information on the locate request may include, for example, the physical address or other location information about the dig area to which the locate technician is dispatched and the type of service that is requested, such as detecting and marking one or more types of facilities within a certain area of interest at a certain geographic site. Additionally, the locate request may specify a “must be complete by” date, a “must be performed on” date, and/or a “do not perform until” date.
In many instances, excavators and other parties who request a locate operation receive very limited or no notification as to whether or when the operation is complete. Once the locate request ticket is in a “closed” status, the one-call center may communicate to the excavator that the locate operation is complete. However, this communication may not be provided in a timely manner. Any delay between performing the locate operation and the planned excavation represents an inefficiency in the excavation process and, perhaps, lost profit by the excavation companies whose excavators may be unnecessarily idle. Additionally, because there is limited exchange of information between the excavators, other parties requesting locate operations, and locate service providers, there may be confusion as to the scope and status of the locate operation. In some instances, excavators arrive on site and find the locate/marking operation not done or done incorrectly; excavators often wait for the “complete by” date to pass, then arrive at the dig area under the assumption that the locate operation has been performed. Consequently, excavators may perform the planned excavation uncertain as to whether the locate operation is complete as requested or has been performed satisfactorily prior to beginning the excavation activities. As a result, there is a certain amount of risk of damage to underground facilities.
Applicants have recognized and appreciated that a need exists for an information exchange process not just between excavators and other parties who may request locate and marking operations (hereafter a “requesting party,” e.g., excavators, property owners, facilities owners, regulatory authorities, damage investigators, etc.) and locate service providers, but also among other key players involved in and relating to locate and/or marking operations. More specifically, a need exists for better ways of providing information to one or more requesting parties in a timely manner, for example, to reduce uncertainty and thereby reduce the risk of damage to underground facilities, and in some instances to also improve excavator efficiency.
In view of the foregoing, various inventive embodiments disclosed herein relate generally to providing information relating to a locate and/or marking operation to excavators, other parties requesting locate and/or marking operations (a requesting party), and/or any other party associated with locate and/or marking activities.
In one embodiment, one or more computing devices (e.g., having a processor, memory, communications interface, user interface/display, and/or input/output interface, etc.) may be configured so as to provide a graphical user interface (GUI) that may be accessed by a requesting party for a locate and/or marking operation, so as to facilitate submission of locate requests as well as selection and/or customization of “positive response” notifications. For purposes of the present disclosure, a “positive response” notification (also referred to herein simply as “positive response” and/or “notification”) refers to one or more communications to one or more requesting parties for a locate and/or marking operation, which communications provide some indication of the status of the operation and/or information relating to one or more elements of performance of the operation (or a link/pointer to such an indication/information, such as a website address containing the indication/information). In some exemplary implementations, such computing devices/GUI may be provided by a one-call-center in a given jurisdiction, to both facilitate submission of locate requests in general, and to further provide for customization in the manner of receiving, and contents of, one or more positive response notifications that may be provided to the requesting party/parties. In other implementations, such computing devices/GUI may be provided by a third party that may be in communication both with one or more requesting parties and a one-call-center issuing locate request tickets.
In exemplary embodiments, in addition to submitting a locate request, in various aspects a requesting party may specify, via such a GUI, that they would like to receive one or more positive response notifications relating to the requested locate and/or marking operation. In addition to merely selecting an option to receive one or more positive response notifications, the requesting party may specify a particular communication mode in which they wish to receive notification(s) (e.g., text message; e-mail; voice message; etc.) and/or a particular format in which they wish to receive notification(s) (e.g., text based; HTML; images; text and images; tables with particular fields; flat files; etc.). Alternatively or additionally, the requesting party may specify one or more particular times/events during an operation at which they wish to receive notification(s) (e.g., when a locate ticket is dispatched by a one call center; when a ticket is received by a utility owner/locate contractor; when a locate technician is dispatched; when a locate technician arrives at a work site/dig area; when a locate technician begins an operation; when an operation is complete; if and when an operation is approved by a supervisor/quality control assessment; if and when there is some anomaly regarding the operation with respect to information in the ticket; etc.). Likewise, alternatively or additionally, the requesting party may specify particular content that they wish to receive in one or more notifications (e.g., upon arrival of technician to work site, send arrival time and geo-location data/GPS coordinates of technician location; upon completion of the operation send a simple notification indicating such; upon completion of the operation, send a complete electronic manifest of all work performed during the operation; upon completion of the operation, send one or more images of the work site/dig area illustrating dispensed markings; send a quality assessment report or other quality assessment-related information, etc.).
Once a locate request is submitted, along with selection of positive response notification and preferences for same, the computing device(s) may be configured to thereafter receive further information from a variety of sources (e.g., facility owners; locate contractors; various equipment, instrumentation, and/or vehicles associated with dispatched technicians to perform locate and/marking operations; etc.) relating to allocating tickets to available technicians and dispatching technicians, as well as various steps/events toward performance of the locate and marking operation. The computing device(s) acquire and process such information so as to appropriately provide positive response notification(s) to requesting parties pursuant to their selected preferences. In some embodiments, following receipt of a notification, a requesting party may optionally provide, or in some instances be mandated to provide (e.g., by contractual obligation, applicable statutes/regulations, etc.) an acknowledgement of receipt (e.g., a “return receipt”) for one or more received notifications.
In yet another embodiment, one or more computing devices may be configured so as to provide a graphical user interface (GUI) that not only facilitates submission of locate requests and positive response notification preferences, but also allows for the requesting party to prepare and submit a “virtual white lines” (VWL) image as part of the locate request. As discussed in greater detail herein, a VWL image may contain a digital image of the work site (or some other suitable digital data representing the geographic location of the work site) along with electronic annotations delimiting one or more dig areas in which excavation or disturbances to the ground are planned. Such electronic annotations also are referred to as “dig area indicators,” which may be any electronically generated markings indicating a point, line, path and/or area of the planned excavation. To facilitate generation of a VWL image, the computing device(s) may be configured to execute a VWL application which may be implemented, for example, as described in the following references: U.S. patent application Ser. No. 12/366,853 filed Feb. 6, 2009, entitled “Virtual white lines for delimiting planned excavation sites;” U.S. patent application Ser. No. 12/475,905 filed Jun. 1, 2009, entitled “Virtual white lines for delimiting planned excavation sites of staged excavation projects;” and U.S. patent application Ser. No. 12/422,364 filed Apr. 13, 2009, entitled “Virtual white lines (VWL) application for indicating a planned excavation or locate path,” each of which patent applications is hereby incorporated by reference herein in its entirety.
In some implementations relating to VWL images, the digital image on which dig area indicators are drawn may be geotagged (i.e., associated with geospatial metadata), and the one or more computing devices may be configured to execute the VWL application so as to use the geospatial metadata associated with the digital image to convert location information regarding the dig area indicators and/or landmarks shown in the digital image into geographic coordinates such as Global Positioning System (GPS) coordinates. These geographic coordinates may be stored in a separate data set that may be attached to a locate request instead of, or in addition to, the VWL image. Accordingly, pursuant to this embodiment, via a suitably-implemented GUI and a VWL application, a party requesting a locate and/or marking information may: 1) submit a locate request; 2) generate a VWL image and attach the image and/or a data set relating to a VWL image; and/or 3) select to receive one or more positive response notifications, and preferences for receiving same.
In yet other embodiments, according to the methods, apparatus and systems described herein an enhanced positive response may be generated to inform one or more parties of locate and/or marking operation status. In one exemplary implementation, an enhanced positive response may include one or both of time-stamp information to provide proof of a time at which the locate and/or marking operation was completed by a locate technician, and place-stamp information to provide proof of a presence of the locate technician sufficiently proximate to or at a geographic location specified on the locate request ticket (and corresponding to the dig area). In one aspect, the enhanced positive response may include an electronic manifest (EM) image that itself includes such a time-stamp and/or place-stamp. As discussed in further detail below, an EM image is an electronic image depicting a work site/dig area and its surroundings (e.g., a digital photograph, an aerial photograph, an electronic map, etc.), on which is overlaid various information relating to work performed in the field at the work site/dig area by a locate technician. In one aspect, the inclusion of an EM image in an enhanced positive response provides comprehensive feedback regarding performance of the locate and/or marking operation. Examples of other information that may be included in such an enhanced positive response (and in some cases as part of an EM image) include, but are not limited to, a signature and/or a user identification that identifies the locate technician, one or more member codes for facility owners who may have facilities in or proximate to the dig area, one or more positive response codes representing a status of the locate and/or marking operation, and various textual information. In another aspect, the enhanced positive response may include a virtual white line (VWL) image, in addition to the EM image, that includes one or more dig area indicators to indicate the dig area on an image; alternatively, the EM image itself may include one or more such dig area indicators. As discussed in further detail below, one or both of an EM image and a VWL image may include geo-referenced information (e.g., GPS coordinates) in connection with dig area indicators, environmental landmarks present in and around the work site/dig area, and/or the locate and/or marking operation performed by the technician.
In another embodiment relating to an enhanced positive response, various environmental information may be provided in such a response regarding one or more environmental conditions present at or near the dig area/work site during a locate and/or marking operation. Examples of environmental conditions about which environmental information may be provided includes, but is not limited to, an ambient temperature, and ambient humidity, and an ambient light level. Various environmental sensors may be employed, alone or together with exemplary locate and marking devices discussed herein, to acquire such environmental information. Additionally, digital photographs and/or digital audio files may be acquired at or near the dig area/work site and included in an enhanced positive response to provide additional information.
In yet another embodiment relating to an enhanced positive response, according to the methods, apparatus and systems described herein an enhanced positive response may be generated in which an electronic manifest (EM) image and a virtual white line (VWL) image associated with the locate and/or marking operation are bundled together based on respective descriptor files (or descriptor metadata) for the EM image and the VWL image. In one aspect, the descriptor files or descriptor metadata associate the corresponding images with one or more particular tickets in response to which the locate and/or marking operation is performed so as to link the images and relevant information in the locate request ticket. In this manner, a comprehensive enhanced positive response may be generated so as to inform one or more parties of a completed status of the locate and/or marking operation. As noted above, in addition to the EM image and the VWL image, a variety of other information also may be included in an enhanced positive response resulting from bundling of images based on descriptor files/descriptor metadata.
In sum, one embodiment of the present invention is directed to an apparatus for providing information regarding a locate and/or marking operation. The locate and/or marking operation comprises detecting and/or marking by a locate technician, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises: a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively 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 receive input indicating that the locate and/or marking operation is complete; and based on the input indicating that the locate and/or marking operation is complete, further controls the communication interface and/or the memory to electronically transmit and/or electronically store performance information concerning the locate and/or marking operation. The performance information includes at least one of the following: time-stamp information to provide proof of a time at which the locate and/or marking operation was completed by the locate technician; and place-stamp information to provide proof of a presence of the locate technician sufficiently proximate to or at a geographic location specified on the locate request ticket and corresponding to the dig area.
Another embodiment is directed to a computer-implemented method for providing information regarding a locate and/or marking operation. The locate and/or marking operation comprises detecting and/or marking by a locate technician, 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 is planned to be excavated or disturbed during excavation activities. The method comprises: A) receiving input indicating that the locate and/or marking operation is complete; and B) based on the input indicating that the locate and/or marking operation is complete, electronically transmitting and/or electronically storing performance information concerning the locate and/or marking operation. The performance information includes at least one of the following: time-stamp information to provide proof of a time at which the locate and/or marking operation was completed by the locate technician; and place-stamp information to provide proof of a presence of the locate technician sufficiently proximate to or at a geographic location specified on the locate request ticket and corresponding to the dig area.
Another embodiment is directed to at least one non-transitory computer readable medium encoded with instructions that, when executed on at least one processing unit, perform a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking by a locate technician, 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 is planned to be excavated or disturbed during excavation activities, the method comprising: A) receiving input indicating that the locate and/or marking operation is complete; and B) based on the input indicating that the locate and/or marking operation is complete, electronically transmitting and/or electronically storing performance information concerning the locate and/or marking operation, the performance information including at least one of the following: time-stamp information to provide proof of a time at which the locate and/or marking operation was completed by the locate technician; and place-stamp information to provide proof of a presence of the locate technician sufficiently proximate to or at a geographic location specified on the locate request ticket and corresponding to the dig area.
Another embodiment is directed to an apparatus for providing information regarding a locate and/or marking operation. The locate and/or marking operation comprises detecting and/or marking by a locate technician, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises: a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively 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 receive input indicating that the locate and/or marking operation is complete; and based on the input indicating that the locate and/or marking operation is complete, further controls the communication interface and/or the memory to electronically transmit and/or electronically store environmental information regarding at least one environmental condition present at or near the dig area during the locate and/or marking operation, so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the at least one environmental condition.
Another embodiment is directed to an apparatus for providing an enhanced positive response regarding a locate and/or marking operation. The locate and/or marking operation comprises detecting and/or marking by a locate technician, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises: a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively coupled to the communication interface and the memory. Upon execution of the processor-executable instructions by the processing unit, the processing unit implements an image assembly component, wherein the image assembly component: bundles together at least one at least one electronic manifest (EM) image and at least one virtual white line (VWL) image associated with the locate and/or marking operation, based on respective descriptor files for the at least one EM image and the at least one VWL image, so as to generate the enhanced positive response; and controls the communication interface and/or the memory to electronically transmit and/or electronically store the enhanced positive response so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of a completed status of the locate and/or marking operation.
Another embodiment is directed to a computer-implemented method for generating a locate report that describes a completed underground facility locate operation. The method comprises: receiving, by a report application on a computing device, locate information from a locate request ticket, the locate information defining a requested locate operation in a dig area; receiving, by the report application, locate data acquired during the locate operation; receiving, by the report application, at least one image showing the dig area; generating, by the report application, a locate report identifying the locate request ticket and including information based on the locate data and the at least one image; and notifying, by the report application, at least one user that the locate report is available.
Another embodiment is directed to a computer-readable storage medium encoded with computer-readable instructions that, as a result of being executed by a computing device, controls the computing device to perform a method for generating a locate report that describes a completed underground facility locate operation. The method comprises: receiving locate information from a locate request ticket, the locate information defining a requested locate operation in a dig area; receiving locate data acquired during the locate operation; receiving at least one image showing the dig area; generating a locate report identifying the locate request ticket and including information based on the locate data and the at least one image; and notifying at least one user that the locate report is available.
Another embodiment is directed to a system for generating a locate report that describes a completed underground facility locate operation. The system comprises: a processing device; and a memory containing a report application, for execution by the processing device, to receive locate information from a locate request ticket, the locate information defining a requested locate operation in a dig area, to receive locate data acquired during the locate operation, to receive at least one image showing the dig area, to generate a locate report identifying the locate request ticket and including information based on the locate data and the at least one image, and to notify at least one user that the locate report is available.
Another embodiment is directed to an apparatus for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively 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 receive user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; generates the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and further controls the communication interface and/or the memory to electronically transmit and/or electronically store the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
Another embodiment of the present invention 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 providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; B) generating the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and C) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
A further embodiment of the present invention is directed to a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; B) generating the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and C) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
Another embodiment of the present invention is directed to an apparatus for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively 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 receive an input indicating that the locate and/or marking operation is in progress or complete; generates at least one notification indicating that the locate and/or marking operation is in progress or complete; and further controls the communication interface and/or the memory to electronically transmit and/or electronically store the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation that the locate and/or marking operation is in progress or complete.
A further embodiment of the present invention 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 providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving an input indicating that the locate and/or marking operation is in progress or complete; B) generating at least one notification indicating that the locate and/or marking operation is in progress or complete; and C) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation that the locate and/or marking operation is in progress or complete.
Another embodiment of the present invention is directed to a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving an input indicating that the locate and/or marking operation is in progress or complete; B) generating at least one notification indicating that the locate and/or marking operation is in progress or complete; and C) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation that the locate and/or marking operation is in progress or complete.
A further embodiment of the present invention is directed to an apparatus for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively 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 receive an input indicating that the locate and/or marking operation is complete; and based on the input indicating that the locate and/or marking operation is complete, further controls the communication interface and/or the memory to electronically transmit and/or electronically store at least one of the following so as to provide information concerning the locate and/or marking operation to at least one party associated with providing at least one locate request relating to the locate and/or marking operation: (a) a virtual white line image indicating the dig area; (b) an electronic copy of a completed locate request ticket; (c) an electronic manifest image showing details of the locate and/or marking operation; and (d) an electronic representation of the locate and/or marking operation.
Another embodiment of the present invention 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 providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving an input indicating that the locate and/or marking operation is complete; and B) based on the input indicating that the locate and/or marking operation is complete, electronically transmitting and/or electronically storing at least one of the following so as to provide information concerning the locate and/or marking operation to at least one party associated with providing at least one locate request relating to the locate and/or marking operation: (a) a virtual white line image indicating the dig area; (b) an electronic copy of a completed locate request ticket; (c) an electronic manifest image showing details of the locate and/or marking operation; and (d) an electronic representation of the locate and/or marking operation.
A further embodiment of the present invention is directed to a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving an input indicating that the locate and/or marking operation is complete; and B) based on the input indicating that the locate and/or marking operation is complete, electronically transmitting and/or electronically storing at least one of the following so as to provide information concerning the locate and/or marking operation to at least one party associated with providing at least one locate request relating to the locate and/or marking operation: (a) a virtual white line image indicating the dig area; (b) an electronic copy of a completed locate request ticket; (c) an electronic manifest image showing details of the locate and/or marking operation; and (d) an electronic representation of the locate and/or marking operation.
Another embodiment of the present invention is directed to an apparatus for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively coupled to the communication interface and the memory. Upon execution of the processor-executable instructions by the processing unit, the processing unit electronically receives, via the communication interface, first user input relating to the dig area; based on the first user input, renders a digital virtual white line image including at least one dig area indicator to provide at least one indication of the dig area with respect to a geographic area; controls the communication interface and/or the memory to electronically transmit and/or electronically store information relating to the digital virtual white line image so as to facilitate the locate and/or marking operation; further controls the communication interface to electronically receive second user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; generates the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and further controls the communication interface and/or the memory to electronically transmit and/or electronically store the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
Another embodiment of the present invention 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 providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving first user input relating to the dig area; B) based on the first user input, rendering a digital virtual white line image including at least one dig area indicator to provide at least one indication of the dig area with respect to a geographic area; C) electronically transmitting and/or electronically storing information relating to the digital virtual white line image so as to facilitate the locate and/or marking operation; D) electronically receiving second user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; E) generating the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and F) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
A further embodiment of the present invention is directed to a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving first user input relating to the dig area; B) based on the first user input, rendering a digital virtual white line image including at least one dig area indicator to provide at least one indication of the dig area with respect to a geographic area; C) electronically transmitting and/or electronically storing information relating to the digital virtual white line image so as to facilitate the locate and/or marking operation; D) electronically receiving second user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; E) generating the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and F) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
Another embodiment of the present invention is directed to an apparatus for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The apparatus comprises a communication interface; a memory to store processor-executable instructions; and a processing unit communicatively coupled to the communication interface and the memory. Upon execution of the processor-executable instructions by the processing unit, the processing unit electronically receives a locate request via the communication interface; based on the locate request, generates the at least one locate request ticket; controls the communication interface and/or the memory to electronically transmit and/or electronically store the locate request ticket so as to initiate the locate and/or marking operation; further controls the communication interface to electronically receive user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; generates the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and further controls the communication interface and/or the memory to electronically transmit and/or electronically store the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
Another embodiment of the present invention 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 providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving a locate request; B) based on the locate request, generating the at least one locate request ticket; C) electronically transmitting and/or electronically storing the locate request ticket so as to initiate the locate and/or marking operation; D) electronically receiving user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; E) generating the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and F) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
A further embodiment of the present invention is directed to a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving a locate request; B) based on the locate request, generating the at least one locate request ticket; C) electronically transmitting and/or electronically storing the locate request ticket so as to initiate the locate and/or marking operation; D) electronically receiving user input regarding a preferred notification type and/or a preferred notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; E) generating the at least one notification based at least in part on the preferred notification type and/or the preferred notification communication method; and F) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation.
Another embodiment of the present invention is directed to a method for providing information regarding a locate and/or marking operation comprising detecting and/or marking, 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 is planned to be excavated or disturbed during excavation activities. The method comprises A) electronically receiving user input regarding at least one notification type and/or at least one notification communication method for at least one notification indicating a status and/or providing information relating to the performance of the locate and/or marking operation; B) generating the at least one notification based at least in part on the at least one notification type and/or the at least one notification communication method; and C) electronically transmitting and/or electronically storing the at least one notification so as to inform at least one party associated with providing at least one locate request relating to the locate and/or marking operation of the status and/or performance of the locate and/or marking operation. According to some implementations, the at least one notification type and/or the at least one notification communication method may be mandated by at least one regulation and/or required by at least one contract.
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.
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 “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,” “excavation notice,” and “work order” are used herein 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 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. 2010-0094553-A1, published Apr. 15, 2010, filed Dec. 16, 2009, and entitled “Systems and Methods for Using Location Data and/or Time Data to Electronically Display Dispensing of Markers by A Marking System or Marking Tool;”
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. 2010-0090858-A1, published Apr. 15, 2010, filed Dec. 16, 2009, and entitled “Systems and Methods for Using Marking Information to Electronically Display Dispensing of Markers by a Marking System or Marking Tool;”
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. 2010-0085694 A1, published Apr. 8, 2010, filed Sep. 30, 2009, and entitled, “Marking Device Docking Stations and Methods of Using Same;”
U.S. publication no. 2010-0085701 A1, published Apr. 8, 2010, filed Sep. 30, 2009, and entitled, “Marking Device Docking Stations Having Security Features and Methods of Using Same;”
U.S. publication no. 2010-0084532 A1, published Apr. 8, 2010, filed Sep. 30, 2009, and entitled, “Marking Device Docking Stations Having Mechanical Docking and Methods of Using Same;”
U.S. publication no. 2010-0088032-A1, published Apr. 8, 2010, filed Sep. 29, 2009, and entitled, “Methods, Apparatus and Systems for Generating Electronic Records of Locate And Marking Operations, and Combined Locate and Marking Apparatus for Same;”
U.S. publication no. 2010-0117654 A1, published May 13, 2010, filed Dec. 30, 2009, and entitled, “Methods and Apparatus for Displaying an Electronic Rendering of a Locate and/or Marking Operation Using Display Layers;”
U.S. publication no. 2010-0086677 A1, published Apr. 8, 2010, filed Aug. 11, 2009, and entitled, “Methods and Apparatus for Generating an Electronic Record of a Marking Operation Including Service-Related Information and Ticket Information;”
U.S. publication no. 2010-0086671 A1, published Apr. 8, 2010, filed Nov. 20, 2009, and entitled, “Methods and Apparatus for Generating an Electronic Record of A Marking Operation Including Service-Related Information and Ticket Information;”
U.S. publication no. 2010-0085376 A1, published Apr. 8, 2010, filed Oct. 28, 2009, and entitled, “Methods and Apparatus for Displaying an Electronic Rendering of a Marking Operation Based on an Electronic Record of Marking Information;”
U.S. publication no. 2010-0088164-A1, published Apr. 8, 2010, filed Sep. 30, 2009, and entitled, “Methods and Apparatus for Analyzing Locate and Marking Operations with Respect to Facilities Maps;”
U.S. publication no. 2010-0088134 A1, published Apr. 8, 2010, filed Oct. 1, 2009, and entitled, “Methods and Apparatus for Analyzing Locate and Marking Operations with Respect to Historical Information;”
U.S. publication no. 2010-0088031 A1, published Apr. 8, 2010, filed Sep. 28, 2009, and entitled, “Methods and Apparatus for Generating an Electronic Record of Environmental Landmarks Based on Marking Device Actuations;”
U.S. publication no. 2010-0188407 A1, published Jul. 29, 2010, filed Feb. 5, 2010, and entitled “Methods and Apparatus for Displaying and Processing Facilities Map Information and/or Other Image Information on a Marking Device;”
U.S. publication no. 2010-0198663 A1, published Aug. 5, 2010, filed Feb. 5, 2010, and entitled “Methods and Apparatus for Overlaying Electronic Marking Information on Facilities Map Information and/or Other Image Information Displayed on a Marking Device;”
U.S. publication no. 2010-0188215 A1, published Jul. 29, 2010, filed Feb. 5, 2010, and entitled “Methods and Apparatus for Generating Alerts on a Marking Device, Based on Comparing Electronic Marking Information to Facilities Map Information and/or Other Image Information;”
U.S. publication no. 2010-0188088 A1, published Jul. 29, 2010, filed Feb. 5, 2010, and entitled “Methods and Apparatus for Displaying and Processing Facilities Map Information and/or Other Image Information on a Locate Device;”
U.S. publication no. 2010-0189312 A1, published Jul. 29, 2010, filed Feb. 5, 2010, and entitled “Methods and Apparatus for Overlaying Electronic Locate Information on Facilities Map Information and/or Other Image Information Displayed on a Locate Device;”
U.S. publication no. 2010-0188216 A1, published Jul. 29, 2010, filed Feb. 5, 2010, and entitled “Methods and Apparatus for Generating Alerts on a Locate Device, Based ON Comparing Electronic Locate Information TO Facilities Map Information and/or Other Image Information;”
U.S. publication no. 2010-0189887 A1, published Jul. 29, 2010, filed Feb. 11, 2010, and entitled “Marking Apparatus Having Enhanced Features for Underground Facility Marking Operations, and Associated Methods and Systems;”
U.S. publication no. 2010-0188245 A1, published Jul. 29, 2010, filed Feb. 11, 2010, and entitled “Locate Apparatus Having Enhanced Features for Underground Facility Locate Operations, and Associated Methods and Systems;”
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. 2010-0205264-A1, published Aug. 12, 2010, filed Feb. 10, 2010, and entitled “Methods, Apparatus, and Systems for Exchanging Information Between Excavators and Other Entities Associated with Underground Facility Locate and Marking Operations;”
U.S. publication no. 2010-0205031-A1, published Aug. 12, 2010, filed Feb. 10, 2010, and entitled “Methods, Apparatus, and Systems for Exchanging Information Between Excavators and Other Entities Associated with Underground Facility Locate and Marking Operations;”
U.S. publication no. 2010-0201706-A1, published Aug. 12, 2010, filed Jun. 1, 2009, and entitled “Virtual White Lines (VWL) for Delimiting Planned Excavation Sites of Staged Excavation Projects;”
U.S. publication no. 2010-0205555-A1, published Aug. 12, 2010, filed Jun. 1, 2009, and entitled “Virtual White Lines (VWL) for Delimiting Planned Excavation Sites of Staged Excavation Projects;”
U.S. publication no. 2010-0205195-A1, published Aug. 12, 2010, filed Jun. 1, 2009, and entitled “Methods and Apparatus for Associating a Virtual White Line (VWL) Image with Corresponding Ticket Information for an Excavation Project;”
U.S. publication no. 2010-0205536-A1, published Aug. 12, 2010, filed Jun. 1, 2009, and entitled “Methods and Apparatus for Controlling Access to a Virtual White Line (VWL) Image for an Excavation Project;”
U.S. publication no. 2010-0228588-A1, published Sep. 9, 2010, filed Feb. 11, 2010, and 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;”
U.S. publication no. 2010-0201690-A1, published Aug. 12, 2010, filed Apr. 13, 2009, and entitled “Virtual White Lines (VWL) Application for Indicating a Planned Excavation or Locate Path;”
U.S. publication no. 2010-0205554-A1, published Aug. 12, 2010, filed Apr. 13, 2009, and entitled “Virtual White Lines (VWL) Application for Indicating an Area of Planned Excavation;”
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. 2010-0205032-A1, published Aug. 12, 2010, filed Feb. 11, 2010, and entitled “Marking Apparatus Equipped with Ticket Processing Software for Facilitating Marking Operations, and Associated Methods;”
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;”
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;”
U.S. publication no. 2010-0010883-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 Quality Assessment Criteria;”
U.S. publication no. 2010-0088135 A1, published Apr. 8, 2010, filed Oct. 1, 2009, and entitled, “Methods and Apparatus for Analyzing Locate and Marking Operations with Respect to Environmental Landmarks;”
U.S. publication no. 2010-0085185 A1, published Apr. 8, 2010, filed Sep. 30, 2009, and entitled, “Methods and Apparatus for Generating Electronic Records of Locate Operations;”
U.S. publication no. 2010-0090700-A1, published Apr. 15, 2010, filed Oct. 30, 2009, and entitled “Methods and Apparatus for Displaying an Electronic Rendering of a Locate Operation Based on an Electronic Record of Locate Information;” and
U.S. publication no. 2010-0085054 A1, published Apr. 8, 2010, filed Sep. 30, 2009, and entitled, “Systems and Methods for Generating Electronic Records of Locate And Marking Operations.”
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 drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention.
Following below are more detailed descriptions of various concepts related to, and embodiments of, inventive systems, methods and apparatus for providing an information exchange process between excavators and other entities associated with underground facility locate operations and, in particular, providing enhanced positive response notifications (also referred to herein simply as an “enhanced positive response” or “locate report”) in connection with such operations. In various aspects, these methods, apparatus, and systems provide communication infrastructure and mechanisms by which information exchange regarding locate and/or marking operations, such as status information, may be reported in real-time and/or other times to excavators or other parties who originate locate requests.
For purposes of illustrating exemplary embodiments, in the more detailed discussion below an exemplary requesting party is taken to be an excavator, and the systems, methods and apparatus discussed herein are sometimes referred to as “informed excavator” systems, methods and apparatus or “positive response” systems, methods and apparatus. However, it should be appreciated that any reference to an “excavator” or “informed excavator” is merely exemplary, as the concepts discussed herein are contemplated as applying more generally to various parties who may request a locate and/or marking operation, examples of which parties may include, but are not limited to, property owners (e.g., home owners, business owners), facility owners, regulatory authorities, damage investigators, and the like. More generally, 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.
While currently a simple conventional communication process may exist between requesting parties and one-call centers and, likewise, a communication process may exist between one-call centers and locate parties, an aspect of the informed excavator systems, methods and apparatus disclosed herein is that they provide an information exchange process among requesting parties, one-call centers and locate parties (independent locate service providers, and/or facility owners who perform their own locate and/or marking operations) which is otherwise not present in current processes with respect to locate operations. Another aspect of the informed excavator system and associated methods of the present disclosure is that it provides improved information exchange between excavators and locate service providers.
Yet another aspect of the informed excavator system and associated methods of the present disclosure is that it provides better ways of communicating the status of locate operations to excavators in a timely manner, which may significantly reduce, and preferably entirely eliminate, the uncertainty as to whether the locate operation is complete.
Still another aspect of the informed excavator system and associated methods of the present disclosure is that it provides information to the excavator about the locate operation prior to beginning the excavation activities. This substantially improves the confidence of the excavator that the locate operation has been performed satisfactorily, which may significantly reduce, and preferably entirely eliminate, the risk of damage to underground facilities.
Still another aspect of the informed excavator system and associated methods of the present disclosure is that it provides improved project planning, decision making, management, and/or tracking with respect to locate operations.
Referring to
Excavation companies, such as excavation companies 110, may be any companies that provide excavation services for any purpose, such as, but not limited to, excavation services related to the construction industry and excavation services related to the installation and/or maintenance of underground facilities. Excavators 114 may be any personnel associated with excavation companies 110, such as, but not limited to, individuals who are requesting and/or performing the excavation operations. In particular, excavators 114 generate locate requests (i.e., tickets), which may be processed via a certain one-call center 120. A ticket may be any communication or instruction to perform a locate operation at a certain dig area, which is any specified geographic area within which excavation may occur.
One-call centers, such as one-call centers 120, may be any organizations, entities, and/or systems that receive, process, and/or transmit locate requests. The locate request (or ticket) may be any communication or instruction to perform a locate operation. One-call centers are generally owned, controlled, or funded by underground facility owners, such as telephone companies, cable television multiple system operators, electric utilities, gas utilities, or others. One-call center operations may be managed by a non-profit entity or outsourced to a for-profit firm. Excavators, such as excavators 114, are required to notify one-call centers in advance of their excavation activities and identify through the locate request the dig area where individual excavating activities will be performed. Locate requests may include information supplied by the excavator to the one-call center regarding the specific geographic location of the dig area, date, time, purpose of excavation, and so on. The locate request, in turn, requires activity from an underground facility owner to perform a locate operation in the specified dig area.
Locate parties/entities, such as locate parties 130, may be any parties that provide locate services. Multiple locate personnel 134 may be associated with each locate party 130. Locate personnel 134 may be, for example, locate technicians and/or quality control technicians that, for example, perform locate operations.
While a communication process may exist between excavation companies and one-call centers and also may exist between one-call centers and locate parties in current processes, an aspect of the information exchange process flow 100 of the present disclosure is that it further includes a communications link between excavation companies and locate parties, which is otherwise not present in current processes for generating and processing locate requests. In this way, the communications loop among, for example, excavation companies 110, one-call centers 120, and locate parties 130 is closed. As a result, a free flow of information with respect to information about locate operations may occur. More details of an example of a system for facilitating a closed loop communications flow, such as information exchange process flow 100, with respect to locate operations are described with reference to
Referring to
Informed excavator system 200 may include, but is not limited to, the one or more one-call centers 120 of
In order to connect to network 224, each entity of informed excavator system 200 includes a communication interface (not shown). For example, the respective communication interfaces of one-call centers 120, image server 210, central server 222, and onsite computers 220, as well as excavator and locate personnel devices, may be any wired and/or wireless communication interface by which information may be exchanged between any entities of informed excavator system 200. Examples of wired communication interfaces may include, but are not limited to, USB ports, RS232 connectors, RJ45 connectors, Ethernet, and any combinations thereof. Examples of wireless communication interfaces may include, but are not limited to, an Intranet connection, Internet, Bluetooth® technology, Wi-Fi, Wi-Max, IEEE 802.11 technology, radio frequency (RF), Infrared Data Association (IrDA) compatible protocols, Local Area Networks (LAN), Wide Area Networks (WAN), Shared Wireless Access Protocol (SWAP), any combinations thereof, and other types of wireless networking protocols.
In exemplary implementations, each entity of the informed excavator system 200 shown in
Informed excavator system 200 is not limited to the types and numbers of entities that are shown in
Image server 210 may be any application server, such as a web application server and/or web portal, by which excavators 114, one-call center 120, and locate parties and their personnel may access certain tools with respect to submitting and/or processing locate requests (or tickets) and/or for processing notifications about locate operations, including access to various images relating to the locate operations and excavation activities. Application server 210 may be accessed by excavators 114 via any networked computing device (not shown).
Central server 222 may be a centralized computer, such as a central server of, for example, a certain locate party 130 of
Each onsite computer 220 may be any computer, such as, but not limited to, a computer that is present in the vehicle that is being used by the field service personnel. Each onsite computer 220 may be, for example, any 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 user interface. Preferably, onsite computer 220 is a portable computing device, such as laptop computer or tablet device. Residing on onsite computer 220 may be certain tools, such as, but not limited to, a VWL viewer, an electronic manifest (EM) application, and a workforce management client.
VWL applications 232 and 234, which may be accessed via the image server 210 and downloaded for use on an onsite computer 220, an excavator device 212 and/or a one-call center 120, is a tool for electronically delimiting the particular geographic location of the proposed excavation in order to provide a substantially permanent and reproducible record of the planned excavation. For example, VWL application 232 (and similarly VWL application 234) may be a drawing application, which, in excavation applications, may be used by the excavator 114 as a dig area marking tool. More specifically, VWL application 232 may be used by the excavator 114 to add markings to an input image to graphically delimit a dig area. For example, VWL application 232 may be used to superimpose over or otherwise display “virtual white lines” on an input image (e.g., an aerial image) that may be received from, for example, the image server 210. As used herein, the virtual white lines may include lines, drawing shapes, shades, points, symbols, coordinates, data sets, or other indicators to delimit on an input image the dig area in which excavation is to occur.
Additionally, VWL application 232 may be the application by which excavators 114 may submit locate requests 236 to one-call centers 120, wherein the locate requests 236 may include the VWL image(s) 238 that are generated by excavators 114. Alternatively, excavators 114 may submit locate requests without virtual white line marked-up images to one-call centers 120, and in turn the one-call centers 120 may use the information in the locate request submitted by the excavator to in turn generate a virtual white line marked-up image 238, via VWL application 234, that is then forwarded to one or more locate parties 130 as locate request 236.
A project component of VWL applications 232 or 234 allows excavators 114 or a one-call center 120 to generate a series of VWL images that may be associated with multiple phases of a “project ticket,” meaning a locate request for an ongoing project that requires multiple locate operations over, for example, a span of several days. An example of such a project may be excavation to lay fiber optics along a 20 mile stretch of a highway. With respect to locate operations, the project ticket may be generated that specifies certain subsections to be located and a timetable. Further to the example, the project component of the VWL application may allow the excavator 114 or the one-call center 120 to generate a first VWL image for mile 1 of 20, a second VWL image for mile 2 of 20, a third VWL image for mile 3 of 20, a fourth VWL image for mile 4 of 20, and so on. Each image of the series may be named and/or labeled in a manner that allows the VWL application to read in the series of VWL images in the correct order and geographic position and then overlay all of the VWL images to show the full scope of the locate operation with respect to the project ticket.
Hereafter, the term “VWL image” means a single VWL image of a locate request (or ticket) and/or a series of VWL images of a project ticket.
In one embodiment of the informed excavator system 200 shown in
For example, an excavator 114 may login to the informed excavator application 258 and specify (e.g., via a menu) the types of notifications that he/she wishes to receive and the methods by which notifications may be automatically received. For each excavator 114, the selected types and methods of notification may be saved in a respective “excavator profile” of informed excavator application 258. In this case, the specified preferences may be applied, by default, to all locate requests originated by that excavator. However, notification preferences may also be established in connection with individual locate operations or the like. For example, the excavator may be prompted to separately specify his or her preferences for notifications in connection with each requested locate operation. An excavator may override globally established notification preferences by specifying notification preferences for a particular locate operation without affecting the preferences set forth in the excavator profile.
Examples of types of notifications may include, but are not limited to, the following:
“Locate technician dispatched to dig area,” which means that the locate technician is in route to the dig area. For example, the notification that is transmitted to the originating excavator 114 may be—“For Ticket No. 2645134, the locate technician Jack Stewart, telephone no. 622-222-2222, has been dispatched to dig area on Friday, Dec. 5, 2008 at 9:30 AM.” Such a notification may include a map or a link to a map that shows the locate technician's current location. The locate technician's location may be based on location information derived from a global positioning system (GPS) device or other positioning system device associated with the locate technician. For example, the locate technician's location may be based on coordinates received from a GPS-enabled vehicle, computer, or personal digital assistant (PDA) in proximity to the locate technician while traveling between dig areas and/or during locate operations. The workforce management application 254 described in connection with
“Locate technician on site at dig area,” which means that locate technician has arrived at the dig area. For example, the notification that is transmitted to the originating excavator 114 may be—“For Ticket No. 2645134, the locate technician is on site at dig area on Friday, Dec. 5, 2008 at 10:05 AM.”
“Ticket marked,” which means that locate technician has completed the locate operation. However, a ticket approval process may be pending. For example, the notification that is transmitted to the originating excavator 114 may be—be “Ticket No. 2645134 is marked on Friday, Dec. 5, 2008 at 11:46 AM and is pending approval.”
“Ticket approved,” which means that the locate operation associated with the ticket has been certified by supervisors and/or quality control personnel of locate parties 130 to meet a certain quality standard. The certification process may be via ticket approval application 224 of central server 212. For example, the notification that is transmitted to the originating excavator 114 may be—“Ticket No. 2645134 is approved on Friday, Dec. 5, 2008 at 12:35 PM.” Since approval of the ticket may be the last step of the locate process, such a notification may also include a positive indication that the locate operation is complete and/or that the excavator may proceed with excavation activities.
“Locate details,” which means that detailed information about the locate operation may be transmitted to excavators 114, such as information generated by locate personnel 134 using EM application 232 of onsite computers 214.
“Locate operation delayed,” which means that the locate operation has been delayed for some reason (e.g., rain).
“Ticket expired” or “Ticket about to expire,” which means that the specified time frame for the locate operation has or is about to expire without the locate operation having been completed.
“Locate Request Submitted,” which means that the locate request has been submitted to the one-call center. This notification may include, for example, the name of the person who originated the locate request and/or the locate party or parties who will be responsible for performing the locate operation.
The types of notifications listed above are merely exemplary, and it should be appreciated that many additional types of notifications are possible. For example, notifications may have a high degree of specificity. Rather than simply electing to be notified when a locate technician is on-site, a user may elect to be notified when the locate technician has turned on his marking device, begun marking, changed paint colors, etc. A notification can also relate to a planned event so that, for example, an excavator may be informed when the locate technician plans to be on-site so that the excavator can meet with the locate technician at the specified time.
Examples of methods by which notifications may be automatically received by excavators 114 may include, but are not limited to, email, SMS text message, instant message, phone call (such as from an interactive voice response (IVR) system), pager message, and rich site summary (RSS) feed, which is a family of Web feed formats used to publish frequently updated works, such as blog entries, news headlines, audio, and video, in a standardized format. The notifications may optionally include image(s) or video. For example, an image showing details of the completed locate and/or marking activities may be transmitted to an excavator 114 as an attachment to an email or text message.
Alternatively, an authorized excavator 114 may query the status of certain locate requests by, for example, accessing a secure web site. For example, text-based notifications (e.g., emails or SMS text messages) received by excavators 114 may include a link or reference to a web site, such as one maintained by a locate service provider, that includes information on the status of a locate request and/or locate operation. By accessing the web site, such as by clicking on the hyperlink in an email, the excavator 114 may view periodically updated, recent, and/or real-time information on the status of a locate request and/or locate operation.
Such a web site may display an image showing details of a locate operation and/or a corresponding electronic representation of the locate operation. Further, such a web site may display aggregate information, such that an excavator 114 can view information supplied by multiple locate technicians or parties and/or information relating to a multiple submitted locate requests or multiple dig areas. According to one illustrative example, an excavator 114 may receive an email with a notification that a locate party has completed its locate activities, along with a link to a web site that includes an image and/or electronic representation showing details of the locate activities completed by that locate party as well as the locate activities previously completed by other locate parties.
In some instances, it may be desirable for a single entity or a limited number of entities to retain control over the status or other information relating to a locate operation. For example, it may be desirable for the entity that provides access to an electronic manifest (EM) creation application (e.g., the EM application 246) and has initial control of one or more created EM images (e.g., EM images 248) to retain control of such images. One potential benefit of retaining control of the EM image(s) once created is avoiding unauthorized edits to or unauthorized use of the image(s).
According to one example, a “controlling” entity that provides access to an EM creation application (e.g., the EM application 246) retains control of one or more created images, but allows other entities to access the images in some instances in a limited manner. For example, the controlling entity may provide a link (e.g., a hyperlink) to one or more EM images (e.g., via an e-mail) or otherwise provide an interface allowing the EM image(s) to be accessed (e.g., via a customized or proprietary image viewing application). Such a link may have a pre-established expiration date, such that clicking on the link will not access the EM image(s)/web page after the specified expiration date. To maintain the integrity of the EM image(s), the application providing access to the EM image(s) may prohibit copying of, saving of, or writing to the images. For example, the EM image may be viewable only using a corresponding image file viewer that allows limited access to the EM image. In particular, copy, save and/or write access to the EM image may be prohibited. In these and other respects discussed below, one or more EM image files may be stored and/or transmitted as “limited access files.”
The EM image may, for example, be transmitted to a party associated with the at least one underground facility with the corresponding image file viewer so that the party may view the EM image. For example, an executable file comprising the EM image and image file viewer may be transmitted (e.g., a customized image viewer may be transmitted to one or more onsite computers). Alternatively, the image file viewer may be downloaded/installed separately, e.g., from a web site of the controlling entity, or the EM image may be viewed using an image file viewer stored and executed on a server of the controlling entity.
In one implementation, the controlling entity may allow access to the EM image(s) only when a certain condition or conditions are met. For example, the controlling entity may require a password protected log-in procedure for access to the EM image(s). In particular, the image file viewer may require a password to permit access to the EM image. As another example, the controlling entity may require acceptance of certain terms and/or conditions to permit access to the EM image. According to one implementation, the image file viewer may be programmed to require an indication of acceptance of terms and/or conditions prior to permitting access to the EM image. According to yet another example, the controlling entity may charge a fee for permitting a third party to access one or more EM images, such as a per-transaction fee or a subscription fee.
To prevent access to the EM image unless or until a condition or conditions are met, the EM image may be encrypted and require decryption to be readable. A corresponding image file viewer may be required to decrypt the EM image. The EM image and/or the corresponding image file viewer may also or alternatively be proprietary, and may have a format specific to the controlling entity. The image file viewer may optionally be programmed to determine whether an updated version of the image file viewer is available. For example, the image file viewer may interrogate information associated with the EM image to determine a corresponding version of the image file viewer. If an updated version is found, the viewer may prompt the user to upgrade the application or otherwise facilitate an update.
The EM image may be transmitted in a variety of different formats. For example, the EM image may be transmitted as an image including locate mark indicators thereon. Alternatively, the EM image may be transmitted as a base image with associated metadata and/or a separate file (e.g., an XML file) including information that allows the locate mark indicators to be rendered on or in connection with the base image. Such information may comprise geographic coordinates specifying the locate mark indicators to be displayed on the base image. The information included in the metadata and/or separate file may also specify access permissions for the locate mark indicators. For example, in the case where the information that allows locate mark indicators to be rendered relates to a plurality of dig sites, locate mark information for one or more dig sites may have restricted access such that the corresponding locate mark indicators are not rendered unless certain access conditions are met.
While the status information described above as being stored and/or transmitted as a “limited access file” corresponds to one or more EM images, the same principles may be applied to other types of image-based or non-image files to limit the access to the status information.
In some implementations, an acknowledgement is required from the recipient of a positive response notification that he or she has received and/or reviewed the information included in the notification. Thus, a return receipt may be solicited from the recipient of an notification in the form of an automatic confirmation that the notification was opened or received, for example by an automatic return email or text message. A notification may also be automatically generated when the notification recipient logs in to a web site or otherwise accesses information via a web site. Alternatively, a recipient-generated confirmation may be solicited. For example, the recipient may be requested to reply to a text or email with a certain word or code when a notification is received, accessed and/or reviewed.
Turning again to
Once received at a certain onsite computer or device, a certain locate personnel 134 may view the locate request and may view the corresponding VWL image via the VWL viewer 230. VWL viewer 230 may be any graphical viewer application that is capable of reading and displaying the VWL images. Alternatively, VWL images may be read into and viewed by an “electronic manifest” (EM) application 246. EM application 246 may be a drawing application, which, in underground facility locate applications, may be used by locate personnel 134 as a marking tool for documenting the locate operation.
More specifically, EM application 246 may be used by locate personnel 134 to add markings (one or more “locate mark indicators”) to an input image of a geographic area including the dig area, so as to graphically indicate (digitally represent in an electronic image) the work performed in the locate operation. The input image may be received from, for example, the image server 210 that may be associated with a party that provides images for a fee. In some implementations, the input image may be an aerial image 230. EM application 246 may superimpose over or otherwise display these markings on the displayed input image and save them as, for example, an EM image 248. The markings may include lines, drawing shapes, shades, points, symbols, coordinates, data sets, or other indicators to graphically depict the work performing in the locate operation. The EM image may then be associated with a marked ticket that may be transmitted to central server 222.
The resulting EM image generated by EM application 246 may show, for example, the original virtual white lines 260 from the original VWL image; a mark-up of one or more types of facilities, the presence or absence of which have been determined during the locate operation, and a mark-up of 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 environmental landmarks 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.
Alternatively, EM application 246 may read in information about the locate operation from a data-enabled electronic marking device 216 that is used during the locate operation. The data-enabled electronic marking device may, for example, be based on the marking devices that are described with reference to U.S. Patent Application publication no. 2008-0245299-A1, filed Apr. 4, 2007, entitled “Marking system and method,” and U.S. Patent Application publication no. 2008-0228294-A1, filed Mar. 13, 2007, entitled “Marking system and method with location and/or time tracking,” which publications are incorporated by reference herein in their entirety.
By way of example, the marking device 216 may include certain software components and/or applications, such as, but not limited to, a device health component, a marking data algorithm 244, a map viewer application, ticket processing software, a speech synthesis component, and an operating mode controller that allows the marking device to operate in multiple modes, such as, but not limited to, marking mode, landmark identification mode, solo mode, and group mode. Additionally, the marking device 216 may include certain input devices 240, such as, but not limited to, a marking material detection mechanism, a location tracking system, a temperature sensor, a humidity sensor, a light sensor, a compass, an inclinometer, an accelerometer, a digital camera, and an audio recorder.
Subsequently, the information from the data-enabled electronic marking device 216 may then be rendered into the graphical depiction of the work performed in the locate operation. More specifically, the information from the data-enabled electronic marking device may be processed by EM application 246 and a graphical depiction of the locate operation may be superimposed over or otherwise displayed on the input image and saved as the EM image 248. Again, the EM image 248 may then be associated with a marked or completed ticket 250 that may be transmitted to central server 222. When excavators 114 select “Locate information” as one type of notification in their excavator profiles, the source of this information may be, for example, the marked up EM images 248.
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 246 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 party 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 (e.g., forward to an excavator or other party as part of a notification) to verify that the locate operation was indeed completed, even though no underground facilities were found.
Workforce management client of onsite computers 220 and/or locate personnel devices 218 may be a counterpart to workforce management application 254 of central server 222. That is, workforce management client may be used to transmit the current status of locate operations from onsite computers/locate personnel devices to workforce management application 254. During locate operations, workforce management application 254 monitors status and other information returned from workforce management client and/or ticket approval application 256 of central server 222. Workforce management client exposes this information to the informed excavator application 258. As discussed above, certain status conditions may include, but are not limited to, “ticket received” by locate party 130, “ticket dispatched,” “locate operation in progress,” “ticket marked,” “ticket approved,” “ticket closed,” and the like.
Ticket approval application 256 of central server 222 may be used for collecting data associated with locate operations that are performed in the field and by which quality control functions may be performed. In one example, one or more approvers (not shown) are associated with ticket approval application 224. The approvers may be, for example, any personnel associated with the underground facility locate service provider, such as, but not limited to, the supervisors of locate technicians that are dispatched into the field, quality control supervisors, and/or any management personnel.
Ticket approval application 256 may use the information found in the of EM images 248 of marked or completed tickets 250 that are returned from onsite computers 220/locate personnel devices 218 in order to rapidly assess the quality of the work performed in the field. This assessment may be by visual inspection of each marked ticket by one or more approvers and/or by analyzing the information of each marked ticket against one or more facilities maps (not shown) that correspond to the geographic location associated with marked ticket. Ticket approval application 256 may be a source of locate operation status information that may be monitored by informed excavator application 258.
Referring to
At step 610, excavators 114 access informed excavator application 256 and enter profile information. More specifically, excavators 114 may log into the informed excavator application 256 and enter profile information, such as information about their identity and the preferred types of notifications (e.g., Locate technician dispatched to dig area, Locate technician on site at dig area, Ticket marked, Ticket approved, Locate details) and preferred methods of notifications (e.g., email, SMS text message, phone call, pager message).
At the bottom of the screen, the user is prompted to indicate, via check box and prompt 1006, whether the user would like to submit a locate request and/or generate a VWL image. If the user indicates such interest by selecting the check box, the GUI 1000 will display an interface such as the VWL application interface shown in
In the example described above, the user who establishes a user profile using the GUI 1000 of
Returning now to
At step 614, notification component 516 of informed excavator application 258 generates notifications to excavators 114 based on the current status of locate requests and then transits the notifications based on the types and methods of notifications that are selected in the respective excavator profiles 512 of excavators 114.
In one example, when the types of notifications selected in the profile information is “All types of notifications,” the preferred method of notification is “SMS text message,” and the current status is “ticket dispatched,” a “Locate technician dispatched to dig area” notification may be automatically transmitted to the excavator 114. For example, a text message may be generated and transmitted to the cell phone of the excavator 114 as follows—“For Ticket No. 2645134, locate technician has been dispatched to dig area on Friday, Dec. 5, 2008 at 9:30 AM.” Continuing the example, when the current status changes to “ticket marked,” a “Ticket marked” notification may be automatically transmitted to the excavator 114. For example, a text message may be generated and transmitted to the cell phone of the excavator 114 as follows—“Ticket No. 2645134 is marked on Friday, Dec. 5, 2008 at 11:46 AM.”
In another example, when the types of notifications selected in the profile information is “Ticket closed” only and the preferred method of notification is a phone call, only when the current status is “ticket closed” will the excavator 114 receive a phone call notification. For example, when the current status is “ticket closed,” the excavator 114 may receive a phone call directly from the locate technician who performed the locate operation to inform the excavator 114 that the ticket of interest has been closed on a certain date and time. Alternatively, the excavator 114 may receive a phone call from a certain locate party 130 and/or one-call center 120 in order to inform the excavator 114 that the ticket of interest has been closed. The phone call may be a manually generated phone call from personnel of a certain locate party 130 and/or one-call center 120. Alternatively, the phone call is automatically initiated via an IVR system.
At step 616, notification component 516 of informed excavator application 258 transmits detailed information about locate operations to the excavators. More specifically, when “Locate information” is selected in the excavator profile, detailed information about the locate operation of a certain ticket may be transmitted by notification application 226 to the excavator 114 who originated the locate request. For example, the excavator 114 may receive the following information about a certain locate operation: (1) the original VWL image and/or series of VWL images; (2) an electronic copy of the completed ticket, which may include a status code indicating whether or not the locate operation was completed; (3) the corresponding EM image 248 that was generated by locate personnel 134 via EM application 246 and that shows various details of the locate operation; (4) the corresponding electronic representation of the locate operation, which may include, e.g., the locate technician's name, the locate equipment used, the diagnosis software used on the locate equipment, the locate technician's history at the site, and a description of the conditions in and/or around the dig area (e.g., whether there is a fence and the number of houses or other structures present); (5) an assessment of the risk of excavation in the dig area (e.g., a descriptive or numeric risk assigned based on such factors as whether there is a buried line, a high pressure gas line, or other high risk condition within or near the dig area); and (6) any combinations thereof.
Referring to
At step 710, a locate request that includes a VWL image and/or a project ticket that includes a series of VWL images of the proposed dig area is submitted to a one-call center. More specifically, a certain excavator 114 may use VWL application to generate a VWL image and/or series of VWL images and then submit a locate request and/or project ticket, respectively, to a certain one-call center 120.
At step 712, the locate request that includes a VWL image and/or a project ticket that includes a series of VWL images is passed from a certain one-call center 120 to a certain locate party 130. More specifically, the locate request that is generated in step 710 is transmitted from the one-call center 120 to central server 212 of a certain locate party 130 that is to perform the locate operation.
In various exemplary implementations, a locate request ticket provided to a locate party 130 may include one or both of image data and non-image data associated with the dig area. As discussed above, the image data may include at least one marked-up image of a geographic area including the dig area, wherein the marked-up image(s) includes at least one dig area indicator (e.g., virtual white lines) to provide an indication of the dig area. Again, the dig area indicator(s) (e.g., virtual white lines) typically are placed on the image (e.g., by the excavator or one-call center) before the ticket is received by the locate party. In some implementations, the dig indicator(s)/virtual white lines may be added to the image at a first user location remote from the dig area and/or without acquiring geographic coordinates for the dig area indicator(s). Examples of non-image data that may be included in or otherwise associated with the 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 the at least one dig area indicator; 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; and a ticket identifier for the locate request ticket. Any of the image data or non-image data associated with the locate request ticket may be provided to one or more parties in connection with one or more notifications regarding the status of locate operations, as discussed in greater detail below.
At step 714, workforce management application 254 assigns the locate request that is generated in step 712 to a certain locate personnel 134, such as a locate technician, and the locate technician is dispatched to dig area.
At step 716, the originating excavator 114 may be notified by informed excavator application 258, which is monitoring the status of the locate request, that the locate technician is in route to the dig area. For example, notification component 516 may generate a “Locate technician dispatched to dig area” notification, which may be received by the excavator 114 by the notification method selected in his/her excavator profile. Receiving this notification allows the excavator 114 the opportunity to proceed to the dig area in the event that he/she wishes to discuss any details of the planned excavation with locate personnel 134, in order to avoid any misunderstanding and/or miscommunications about the locate operation and, thereby, reduce the risk of damage to underground facilities during excavation.
At step 718, the locate technician that was dispatched in step 714 arrives at dig area.
At step 720, the originating excavator 114 may be notified by informed excavator application 258, which is monitoring the status of the locate request, that the locate technician has arrived at the dig area. For example, notification component 516 may generate a “Locate technician on site at dig area” notification, which may be received by the excavator 114 by the notification method selected in his/her excavator profile. Again, receiving this notification allows the excavator 114 the opportunity to proceed to the dig area in the event that the excavator 114 wishes to discuss any details of the planned excavation with the locate personnel.
At step 722, the locate technician performs the locate operation at the dig area according to the instructions of the locate request to which he/she has been assigned. 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.
In particular, at step 724, the locate technician completes the locate operation and the ticket status is updated accordingly. For example, a “ticket marked” status may be communicated by workforce management client of onsite computer/locate personnel device to workforce management application 254.
At step 726, the excavator 114 may be notified by informed excavator application 258, which is monitoring the status of the locate request, that the ticket is marked, which means that the locate operation has been completed by the locate technician, but may be pending approval. More specifically, notification component 516 may generate a “Ticket marked (but pending approval)” notification. This notification may be received by the excavator 114 by the notification method selected in his/her excavator profile.
At decision step 728, it is determined whether the ticket of the current locate operation is to be subjected to a quality control process. If yes, method 700 may proceed to step 730. If no, method 700 may proceed to step 732.
At step 730, the ticket of the current locate operation is processed by ticket approval application 256. If the ticket passes the quality control process satisfactorily, method 700 may proceed directly to step 732 with no further action. If the ticket does not pass the quality control process satisfactorily, quality control action is taken until the ticket passes the quality control process satisfactorily, method 700 may then proceed to step 732.
At step 732, the ticket of the current locate operation is classified as ticket approved. In this way, the quality of the locate operation is certified.
At step 734, the originating excavator 114 may be notified by informed excavator application 258, which is monitoring the status of the locate request, that the ticket is approved. For example, notification component 516 may generate a “Ticket approved” notification, which may be received by the excavator 114 by the notification method selected in his/her excavator profile. Receiving this notification allows the excavator 114 the opportunity to proceed to the dig area to perform the planned excavation with little or no delay from the date and time at which the locate operation was completed.
At step 736, the originating excavator 114 may receive the original VWL image plus other information about the locate operation. More specifically, when “Locate information” is selected in the excavator profile, detailed information about the locate operation of a certain ticket (e.g., one or both of image data and non-image data, some examples of which were discussed above) may be transmitted by informed excavator application 258 to the originating excavator 114. For example, the excavator 114 may receive (1) the original VWL image and/or series of VWL images; (2) an electronic copy of the completed ticket (including image and/or non-image data); (3) the corresponding EM image that was generated via EM application 246 and that shows details of the locate operation (including “clears” in which an image is not necessarily marked-up with locate mark indicators, but other important non-image data is associated with the EM image), including an EM image that may also show the original virtual white lines; (4) the corresponding electronic representation of the locate operation (e.g., non-image data or information without a marked-up image component); (5) an assessment of the risk of excavation in the dig area (e.g., a descriptive or numeric risk assigned based on such factors as whether there is a buried line, a high pressure gas line, or other high risk condition within or near the dig area); and (6) any combinations thereof.
At step 738, having detailed knowledge of the locate operation from the information provided in step 736, the excavator 114 may perform the planned excavation of the dig area with increased confidence, which has the result of reducing the risk of damage to underground facilities during excavation.
Referring again to
Referring again to
At step 810, an excavator accesses the excavator information application and enters profile information. This step is analogous to step 610 of
At step 812, the excavator enters locate information and/or generates a VWL image. The excavator information application may include the functionality of VWL application 232 or 234, such that the locate information may be entered and the VWL image may be generated in the manner described in connection with those applications. For example, a VWL image 238 may be created using the VWL application 232 shown in
Steps 814, 816 and 818 may proceed as discussed in connection with analogous steps 612, 614 and 616 of
“Enhanced” Positive Response Notifications
In yet other embodiments, according to the methods, apparatus and systems described herein an enhanced positive response notification (also referred to as an “enhanced positive response” or a “locate report”) may be generated to inform one or more parties of locate and/or marking operation status. In exemplary implementations, an enhanced positive response may be an electronic communication, alert or document that may include (or have a link/pointer to) textual information and/or graphical information, including image information, relating to performance of a locate and/or marking operation.
In one example, an enhanced positive response may include one or both of time-stamp information to provide proof of a time at which the locate and/or marking operation was completed by a locate technician, and place-stamp information to provide proof of a presence of the locate technician sufficiently proximate to or at a geographic location specified on the locate request ticket (and corresponding to the dig area). In another example, the enhanced positive response may include an electronic manifest (EM) image that itself includes such a time-stamp and/or place-stamp to provide comprehensive feedback regarding performance of the locate and/or marking operation. Examples of other information that may be included in such an enhanced positive response (and in some cases as part of an EM image) include, but are not limited to, a signature and/or a user identification that identifies the locate technician, one or more member codes for facility owners who may have facilities in or proximate to the dig area, one or more positive response codes representing a status of the locate and/or marking operation, and various textual information.
In another embodiment, an enhanced positive response may include a virtual white line (VWL) image, in addition to the EM image, that includes one or more dig area indicators to indicate the dig area on an image; alternatively, the EM image itself may include one or more such dig area indicators. As discussed above, one or both of an EM image and a VWL image constituting an enhanced positive response may include geo-referenced information (e.g., GPS coordinates) in connection with dig area indicators, environmental landmarks present in and around the work site/dig area, and/or the locate and/or marking operation performed by the technician.
In another embodiment relating to an enhanced positive response, various environmental information may be provided in such a response regarding one or more environmental conditions present at or near the dig area/work site during a locate and/or marking operation. Examples of environmental conditions about which environmental information may be provided include, but are not limited to, an ambient temperature, and ambient humidity, and an ambient light level. Various environmental sensors may be employed, alone or together with exemplary locate and/or marking devices discussed herein, to acquire such environmental information. Digital photographs and/or digital audio files also may be acquired at or near the dig area/work site and included in an enhanced positive response to provide additional information.
In yet another embodiment relating to an enhanced positive response, according to the methods, apparatus and systems described herein an enhanced positive response may be generated in which an electronic manifest (EM) image and a virtual white line (VWL) image associated with the locate and/or marking operation are bundled together based on respective descriptor files (or descriptor metadata) for the EM image and the VWL image. In one aspect, the descriptor files or descriptor metadata associate the corresponding images with one or more particular tickets in response to which the locate and/or marking operation is performed, so as to link the images and relevant information in the locate request ticket. In this manner, a comprehensive enhanced positive response may be generated so as to inform one or more parties of a completed status of the locate and/or marking operation. As noted above, in addition to the EM image and the VWL image, a variety of other information also may be included in an enhanced positive response resulting from bundling of images based on descriptor files/descriptor metadata.
As shown in
Positive response codes 1114 may be unique codes that have particular meaning with respect to locate and/or marking operations. The unique positive response codes may be determined by a certain controlling entity with respect to underground facility locate operations (again, SSOCOF is one example of a such a controlling entity). By way of example, a sample of positive response codes 1114 of the SSOCOF and their meanings are shown in Table 2 below.
As also shown in
An EM application 246 may provide yet another input to positive response application 1100 as shown in
With respect to the place-stamp 1136 shown in
In view of the foregoing, in some embodiments the EM application 246 employed to generate the EM image 248 shown in
To ensure that the place-stamp 1136 provides reasonable proof that the locate technician was sufficiently proximate to or at the work site/dig area, in one embodiment the EM application 246 may determine whether two or more of the geographic locations indicated above (i.e., work site/dig area specified on ticket, technician whereabouts, and image coordinates) are within some predetermined distance (i.e., a “threshold distance”) of each other. A variety of values for the threshold distance may be used as a metric for sufficient proximity to the work site/dig area; in some cases these metrics may be based at least in part on recommended best practices for a particular jurisdiction, operating procedures for a given locate company/contractor, and/or contractual obligations imposed by one or more facility owners and/or one-call centers. In one exemplary implementation, the threshold distance for sufficient proximity may be on the order of tens of feet, while in other implementations the threshold distance may be greater depending on various circumstances (e.g., hundreds or thousands of feet).
Additional details relating to the place-stamp 1136 and a quality assessment analysis regarding same are discussed in U.S. application publication US2009-0327024-A1, entitled “Methods and Apparatus for Quality Assessment of a Field Service Operation,” published Dec. 31, 2009, which publication is hereby incorporated herein by reference.
With reference again to
In
In one example and referring to Tables 1 and 2, status code 1120 is “VZ-1 Marked; TWC-5 No conflict; FPL-4 Clear.” In this example, “VZ-1 Marked” means that with respect to facilities owned by Verizon—a locate technician has been to your excavation site and marked the approximate horizontal location of underground facilities within the boundaries described on the ticket. “TWC-5 No conflict” means that with respect to facilities owned by Time Warner Cable—the utility has a facility near the excavation site, but it is not within the area that was either described on the ticket or white lined. “FPL-4 Clear” means that with respect to facilities owned by Florida Power & Light—the utility has no underground facilities at the specified excavation site.
The enhanced positive response 1110 shown in
With respect to the optional VWL image 238, the digital image has been marked up electronically using VWL application 232 to show a dig area indicator 260 that indicates the extent of the dig area in which locate operations are performed. Additionally, enhanced positive response 1110 shown in
With reference again to
In yet another aspect, as discussed in part above in connection with
Enhanced positive responses 1110, such as those shown in
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.
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 |
|---|---|---|---|
| 2690239 | Feb 2010 | CA | national |
The present application claims a priority benefit, under 35 U.S.C. §120, as a continuation (CON) of U.S. non-provisional patent application Ser. No. 12/915,516, entitled “Methods, Apparatus and Systems for Providing an Enhanced Positive Response in Underground Facility Locate and Marking Operations,” filed on Oct. 29, 2010. U.S. non-provisional application Ser. No. 12/915,516 claims a priority benefit, under 35 U.S.C. §120, as a continuation-in-part (CIP) of U.S. non-provisional patent application Ser. No. 12/703,313, entitled “Methods, Apparatus, and Systems for Exchanging Information Between Excavators and Other Entities Associated with Underground Facility Locate and Marking Operations,” filed on Feb. 10, 2010. U.S. non-provisional application Ser. No. 12/915,516 also claims a priority benefit, under 35 U.S.C. §119(e), to U.S. provisional patent application Ser. No. 61/256,007, entitled “System For and Method of Providing an Enhanced Positive Response in Underground Facility Locate Applications,” filed on Oct. 29, 2009. Ser. No. 12/703,313 claims a priority benefit, under 35 U.S.C. §119(a), to Canadian application serial no. 2,690,239, entitled “Methods and Apparatus for Excavator Notification of Underground Facility Locate Operation Status,” filed on Feb. 9, 2010. Ser. No. 12/703,313 also claims a priority benefit, under 35 U.S.C. §119(e), to U.S. provisional patent application Ser. No. 61/151,419, entitled “Methods and Apparatus for Excavator Notification of Underground Facility Locate Operation Status,” filed on Feb. 10, 2009. Ser. No. 12/703,313 also claims a priority benefit, under 35 U.S.C. §119(e), to U.S. provisional patent application No. 61/151,425, entitled “Methods and Apparatus for Exchanging Information Between Excavators and Other Entities Associated with Underground Facility Locate Operations,” filed on Feb. 10, 2009. Each of the above-identified applications is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3916298 | Ulrich | Oct 1975 | A |
| 3986777 | Roll | Oct 1976 | A |
| 4600356 | Bridges | Jul 1986 | A |
| 4623282 | Allen | Nov 1986 | A |
| 4688921 | Wakabayashi | Aug 1987 | A |
| 5414462 | Veatch | May 1995 | A |
| 5448263 | Martin | Sep 1995 | A |
| 5576973 | Haddy | Nov 1996 | A |
| 5644237 | Eslambolchi et al. | Jul 1997 | A |
| 5689415 | Calotychos et al. | Nov 1997 | A |
| 5699244 | Clark, Jr. | Dec 1997 | A |
| 5815411 | Ellenby | Sep 1998 | A |
| 5825660 | Cagan et al. | Oct 1998 | A |
| 5920194 | Lewis et al. | Jul 1999 | A |
| 5987380 | Backman | Nov 1999 | A |
| 5991694 | Gudat et al. | Nov 1999 | A |
| 6101087 | Sutton | Aug 2000 | A |
| 6127827 | Lewis | Oct 2000 | A |
| 6141000 | Martin | Oct 2000 | A |
| 6169517 | Eslambolchi | Jan 2001 | B1 |
| 6195922 | Stump | Mar 2001 | B1 |
| 6201883 | Mizui | Mar 2001 | B1 |
| 6299934 | Manning | Oct 2001 | B1 |
| 6337681 | Martin | Jan 2002 | B1 |
| 6345281 | Kardos et al. | Feb 2002 | B1 |
| 6351707 | Ichikawa | Feb 2002 | B1 |
| 6371692 | Fatigati | Apr 2002 | B1 |
| 6421725 | Vermilyea et al. | Jul 2002 | B1 |
| 6426872 | Sutton | Jul 2002 | B1 |
| 6430499 | Nakano | Aug 2002 | B1 |
| 6430562 | Kardos et al. | Aug 2002 | B1 |
| 6430604 | Ogle | Aug 2002 | B1 |
| 6437708 | Brouwer | Aug 2002 | B1 |
| 6470976 | Alft | Oct 2002 | B2 |
| 6477475 | Takaoka et al. | Nov 2002 | B1 |
| 6493650 | Rodgers | Dec 2002 | B1 |
| 6532409 | Fujishima | Mar 2003 | B1 |
| 6567116 | Aman et al. | May 2003 | B1 |
| 6597992 | Rooney et al. | Jul 2003 | B2 |
| 6650293 | Eslambolchi | Nov 2003 | B1 |
| 6650834 | Ume | Nov 2003 | B2 |
| 6701647 | Stump | Mar 2004 | B2 |
| 6710741 | Tucker | Mar 2004 | B2 |
| 6723375 | Zeck et al. | Apr 2004 | B2 |
| 6747636 | Martin | Jun 2004 | B2 |
| 6751552 | Minelli | Jun 2004 | B1 |
| 6751553 | Young | Jun 2004 | B2 |
| 6751554 | Asher et al. | Jun 2004 | B1 |
| 6772142 | Kelling et al. | Aug 2004 | B1 |
| 6778128 | Tucker et al. | Aug 2004 | B2 |
| 6798379 | Tucker et al. | Sep 2004 | B2 |
| 6803906 | Morrison et al. | Oct 2004 | B1 |
| 6825793 | Taylor, Jr. et al. | Nov 2004 | B2 |
| 6850161 | Elliott et al. | Feb 2005 | B1 |
| 6853905 | Barton | Feb 2005 | B2 |
| 6873998 | Dorum | Mar 2005 | B1 |
| 6895356 | Brimhall | May 2005 | B2 |
| 6898525 | Minelli | May 2005 | B1 |
| 6904361 | Tallman et al. | Jun 2005 | B1 |
| 6941890 | Cristo et al. | Sep 2005 | B1 |
| 6950535 | Sibayama | Sep 2005 | B2 |
| 6956524 | Tucker et al. | Oct 2005 | B2 |
| 6957250 | Nakano | Oct 2005 | B1 |
| 6958690 | Asher et al. | Oct 2005 | B1 |
| 6972698 | Deguchi | Dec 2005 | B2 |
| 6975942 | Young et al. | Dec 2005 | B2 |
| 6981001 | Reddick et al. | Dec 2005 | B1 |
| 6999021 | Taylor, Jr. | Feb 2006 | B2 |
| 7003138 | Wilson | Feb 2006 | B2 |
| 7009399 | Olsson et al. | Mar 2006 | B2 |
| 7027653 | Hino | Apr 2006 | B2 |
| 7113124 | Waite | Sep 2006 | B2 |
| 7117445 | Berger | Oct 2006 | B2 |
| 7120564 | Pacey | Oct 2006 | B2 |
| 7136765 | Maier et al. | Nov 2006 | B2 |
| 7142196 | Connor | Nov 2006 | B1 |
| 7185021 | Kishigami | Feb 2007 | B2 |
| 7216034 | Vitikainen | May 2007 | B2 |
| 7222986 | Mah | May 2007 | B2 |
| 7236162 | Morrison et al. | Jun 2007 | B2 |
| 7262797 | Weldum | Aug 2007 | B2 |
| 7274756 | Kuijk | Sep 2007 | B2 |
| 7281263 | LaMastres et al. | Oct 2007 | B1 |
| 7295119 | Rappaport et al. | Nov 2007 | B2 |
| 7363345 | Austin-Lane et al. | Apr 2008 | B2 |
| 7372247 | Giusti et al. | May 2008 | B1 |
| 7400976 | Young et al. | Jul 2008 | B2 |
| 7417641 | Barber | Aug 2008 | B1 |
| 7437830 | Kulavic | Oct 2008 | B1 |
| 7469247 | Cossins et al. | Dec 2008 | B2 |
| 7482973 | Tucker et al. | Jan 2009 | B2 |
| 7579960 | Cheng et al. | Aug 2009 | B2 |
| 7584123 | Karonis et al. | Sep 2009 | B1 |
| 7605590 | Mulcahey | Oct 2009 | B2 |
| 7613331 | Maeda | Nov 2009 | B2 |
| 7626496 | Asher et al. | Dec 2009 | B1 |
| 7636901 | Munson | Dec 2009 | B2 |
| 7640105 | Nielsen et al. | Dec 2009 | B2 |
| 7664530 | Skelton | Feb 2010 | B2 |
| 7773095 | Badrak et al. | Aug 2010 | B1 |
| 7777648 | Smith et al. | Aug 2010 | B2 |
| 7783507 | Schick | Aug 2010 | B2 |
| 7834806 | Tucker et al. | Nov 2010 | B2 |
| 7886616 | Hayman | Feb 2011 | B1 |
| 7889888 | Deardorff et al. | Feb 2011 | B2 |
| 7917292 | Du | Mar 2011 | B1 |
| 7978129 | Sawyer et al. | Jul 2011 | B2 |
| 7990151 | Olsson | Aug 2011 | B2 |
| 8045995 | King | Oct 2011 | B2 |
| 8054343 | Cheatle et al. | Nov 2011 | B2 |
| 8060304 | Nielsen et al. | Nov 2011 | B2 |
| 8081112 | Tucker et al. | Dec 2011 | B2 |
| 8144058 | Sawyer, Jr. et al. | Mar 2012 | B2 |
| 8150826 | Arrouye et al. | Apr 2012 | B2 |
| 8155390 | Nielsen et al. | Apr 2012 | B2 |
| 8194932 | Nielsen et al. | Jun 2012 | B2 |
| 8204642 | Tanaka et al. | Jun 2012 | B2 |
| 8218827 | Nielsen et al. | Jul 2012 | B2 |
| 8248056 | Olsson et al. | Aug 2012 | B1 |
| 8249306 | Nielsen et al. | Aug 2012 | B2 |
| 8260489 | Nielsen et al. | Sep 2012 | B2 |
| 8265344 | Nielsen et al. | Sep 2012 | B2 |
| 8270666 | Nielsen et al. | Sep 2012 | B2 |
| 8280117 | Nielsen et al. | Oct 2012 | B2 |
| 8280631 | Nielsen et al. | Oct 2012 | B2 |
| 8280969 | Nielsen et al. | Oct 2012 | B2 |
| 8290204 | Nielsen et al. | Oct 2012 | B2 |
| 8290215 | Nielsen et al. | Oct 2012 | B2 |
| 8296308 | Nielsen et al. | Oct 2012 | B2 |
| 8300895 | Nielsen et al. | Oct 2012 | B2 |
| 8300925 | Kunieda | Oct 2012 | B2 |
| 8301380 | Nielsen et al. | Oct 2012 | B2 |
| 8311765 | Nielsen et al. | Nov 2012 | B2 |
| 8340359 | Nielsen et al. | Dec 2012 | B2 |
| 8355542 | Nielsen et al. | Jan 2013 | B2 |
| 8356255 | Nielsen et al. | Jan 2013 | B2 |
| 8361543 | Nielsen et al. | Jan 2013 | B2 |
| 8374789 | Nielsen et al. | Feb 2013 | B2 |
| 8384742 | Nielsen et al. | Feb 2013 | B2 |
| 8386178 | Nielsen et al. | Feb 2013 | B2 |
| 8401791 | Nielsen et al. | Mar 2013 | B2 |
| 8407001 | Nielsen et al. | Mar 2013 | B2 |
| 8416995 | Nielsen et al. | Apr 2013 | B2 |
| 8457893 | Nielsen et al. | Jun 2013 | B2 |
| 8463487 | Nielsen et al. | Jun 2013 | B2 |
| 8467932 | Nielsen et al. | Jun 2013 | B2 |
| 8467969 | Nielsen et al. | Jun 2013 | B2 |
| 8468206 | Nielsen et al. | Jun 2013 | B2 |
| 8473148 | Nielsen et al. | Jun 2013 | B2 |
| 8473209 | Nielsen et al. | Jun 2013 | B2 |
| 8476906 | Nielsen et al. | Jul 2013 | B2 |
| 8478523 | Nielsen et al. | Jul 2013 | B2 |
| 8478524 | Nielsen et al. | Jul 2013 | B2 |
| 8478525 | Nielsen et al. | Jul 2013 | B2 |
| 8478617 | Nielsen et al. | Jul 2013 | B2 |
| 8478635 | Nielsen et al. | Jul 2013 | B2 |
| 8480332 | Miller | Jul 2013 | B2 |
| 8484300 | Nielsen et al. | Jul 2013 | B2 |
| 8532341 | Nielsen et al. | Sep 2013 | B2 |
| 8532342 | Nielsen et al. | Sep 2013 | B2 |
| 8540141 | Petrich et al. | Sep 2013 | B2 |
| 8543651 | Nielsen et al. | Sep 2013 | B2 |
| 8543937 | Nielsen et al. | Sep 2013 | B2 |
| 8549084 | Nielsen et al. | Oct 2013 | B2 |
| 8560164 | Nielsen et al. | Oct 2013 | B2 |
| 8566737 | Nielsen et al. | Oct 2013 | B2 |
| 8572193 | Nielsen et al. | Oct 2013 | B2 |
| 8583372 | Nielsen et al. | Nov 2013 | B2 |
| 8620726 | Nielsen et al. | Dec 2013 | B2 |
| 8626571 | Nielsen et al. | Jan 2014 | B2 |
| 8630463 | Nielsen et al. | Jan 2014 | B2 |
| 8700325 | Nielsen et al. | Apr 2014 | B2 |
| 8990100 | Nielsen et al. | Mar 2015 | B2 |
| 20010036295 | Hendrickson | Nov 2001 | A1 |
| 20010049470 | Mault et al. | Dec 2001 | A1 |
| 20020013704 | Finney | Jan 2002 | A1 |
| 20020044690 | Burgess | Apr 2002 | A1 |
| 20020046259 | Glorikian | Apr 2002 | A1 |
| 20020052755 | Whatley | May 2002 | A1 |
| 20020059296 | Hayashi et al. | May 2002 | A1 |
| 20020122119 | Takakura | Sep 2002 | A1 |
| 20020145617 | Kennard | Oct 2002 | A1 |
| 20020184235 | Young | Dec 2002 | A1 |
| 20030012411 | Sjostrom | Jan 2003 | A1 |
| 20030055666 | Roddy | Mar 2003 | A1 |
| 20030095708 | Pittel | May 2003 | A1 |
| 20030110184 | Gibson et al. | Jun 2003 | A1 |
| 20030164053 | Ignagni | Sep 2003 | A1 |
| 20030222815 | Tucker | Dec 2003 | A1 |
| 20040006425 | Wood | Jan 2004 | A1 |
| 20040008883 | Shi et al. | Jan 2004 | A1 |
| 20040073578 | Nam | Apr 2004 | A1 |
| 20040146185 | Blair | Jul 2004 | A1 |
| 20040148191 | Hoke | Jul 2004 | A1 |
| 20040150556 | Tucker et al. | Aug 2004 | A1 |
| 20040151388 | Maeda | Aug 2004 | A1 |
| 20040168358 | Stump | Sep 2004 | A1 |
| 20040199410 | Feyen et al. | Oct 2004 | A1 |
| 20040203909 | Koster | Oct 2004 | A1 |
| 20040210370 | Gudat | Oct 2004 | A1 |
| 20040210386 | Wood | Oct 2004 | A1 |
| 20040220731 | Tucker | Nov 2004 | A1 |
| 20040225444 | Young et al. | Nov 2004 | A1 |
| 20040252303 | Giorgianni et al. | Dec 2004 | A1 |
| 20050033513 | Gasbarro | Feb 2005 | A1 |
| 20050034074 | Munson | Feb 2005 | A1 |
| 20050046584 | Breed | Mar 2005 | A1 |
| 20050057745 | Bontje | Mar 2005 | A1 |
| 20050104775 | Tucker et al. | May 2005 | A1 |
| 20050122518 | Overbeck et al. | Jun 2005 | A1 |
| 20050125389 | Hazzard et al. | Jun 2005 | A1 |
| 20050183028 | Clough et al. | Aug 2005 | A1 |
| 20050192752 | Rooney | Sep 2005 | A1 |
| 20050203768 | Florance | Sep 2005 | A1 |
| 20050219268 | Kyle | Oct 2005 | A1 |
| 20050254704 | Komiya et al. | Nov 2005 | A1 |
| 20060020417 | Koch et al. | Jan 2006 | A1 |
| 20060026020 | Waite et al. | Feb 2006 | A1 |
| 20060058945 | Watanabe | Mar 2006 | A1 |
| 20060077095 | Tucker et al. | Apr 2006 | A1 |
| 20060085396 | Evans | Apr 2006 | A1 |
| 20060091888 | Holman et al. | May 2006 | A1 |
| 20060161349 | Cross | Jul 2006 | A1 |
| 20060229809 | Chen | Oct 2006 | A1 |
| 20060235741 | Deaton et al. | Oct 2006 | A1 |
| 20060239560 | Sternby | Oct 2006 | A1 |
| 20060282191 | Gotfried | Dec 2006 | A1 |
| 20060282280 | Stotz et al. | Dec 2006 | A1 |
| 20070010925 | Yokoyama | Jan 2007 | A1 |
| 20070011271 | Baker et al. | Jan 2007 | A1 |
| 20070027591 | Goldenberg | Feb 2007 | A1 |
| 20070031029 | Sasaki | Feb 2007 | A1 |
| 20070076920 | Ofek | Apr 2007 | A1 |
| 20070100768 | Boccon-Gibod et al. | May 2007 | A1 |
| 20070106784 | Dickman | May 2007 | A1 |
| 20070110316 | Ohashi | May 2007 | A1 |
| 20070118278 | Finn et al. | May 2007 | A1 |
| 20070143676 | Chen | Jun 2007 | A1 |
| 20070182721 | Watanabe et al. | Aug 2007 | A1 |
| 20070187574 | Lia | Aug 2007 | A1 |
| 20070219722 | Sawyer, Jr. | Sep 2007 | A1 |
| 20070258642 | Thota | Nov 2007 | A1 |
| 20070286021 | Hoenmans et al. | Dec 2007 | A1 |
| 20080021863 | Evans | Jan 2008 | A1 |
| 20080025614 | Hintz et al. | Jan 2008 | A1 |
| 20080059889 | Parker et al. | Mar 2008 | A1 |
| 20080075368 | Kuzmin | Mar 2008 | A1 |
| 20080109751 | Fitzmaurice et al. | May 2008 | A1 |
| 20080125942 | Tucker et al. | May 2008 | A1 |
| 20080133128 | Koch | Jun 2008 | A1 |
| 20080180322 | Islam | Jul 2008 | A1 |
| 20080192235 | Komiya et al. | Aug 2008 | A1 |
| 20080208415 | Vik | Aug 2008 | A1 |
| 20080284902 | Konno et al. | Nov 2008 | A1 |
| 20080285805 | Luinge et al. | Nov 2008 | A1 |
| 20080288267 | Asher | Nov 2008 | A1 |
| 20080292295 | Konno et al. | Nov 2008 | A1 |
| 20090004410 | Thomson et al. | Jan 2009 | A1 |
| 20090012418 | Gerlach et al. | Jan 2009 | A1 |
| 20090013806 | Miller | Jan 2009 | A1 |
| 20090067695 | Komiya et al. | Mar 2009 | A1 |
| 20090070071 | Wood | Mar 2009 | A1 |
| 20090092297 | Kitoh et al. | Apr 2009 | A1 |
| 20090100185 | Shehan et al. | Apr 2009 | A1 |
| 20090121937 | Kaegebein | May 2009 | A1 |
| 20090185712 | Wong et al. | Jul 2009 | A1 |
| 20090201311 | Nielsen et al. | Aug 2009 | A1 |
| 20090204238 | Nielsen et al. | Aug 2009 | A1 |
| 20090204466 | Nielsen et al. | Aug 2009 | A1 |
| 20090207019 | Nielsen et al. | Aug 2009 | A1 |
| 20090208642 | Nielsen et al. | Aug 2009 | A1 |
| 20090210285 | Nielsen et al. | Aug 2009 | A1 |
| 20090210298 | Nielsen et al. | Aug 2009 | A1 |
| 20090237263 | Sawyer, Jr. et al. | Sep 2009 | A1 |
| 20090237297 | Davis et al. | Sep 2009 | A1 |
| 20090238415 | Nielsen et al. | Sep 2009 | A1 |
| 20090257620 | Hicks | Oct 2009 | A1 |
| 20090322868 | Ikeda | 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 |
| 20100045517 | Tucker et al. | Feb 2010 | A1 |
| 20100084532 | Nielsen et al. | Apr 2010 | A1 |
| 20100085694 | Nielsen et al. | Apr 2010 | A1 |
| 20100085701 | 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 |
| 20100109670 | Arnaud | May 2010 | A1 |
| 20100117654 | Nielsen et al. | May 2010 | A1 |
| 20100188088 | 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 |
| 20100205031 | Nielsen et al. | Aug 2010 | A1 |
| 20100205032 | Nielsen et al. | Aug 2010 | A1 |
| 20100205536 | Nielsen et al. | Aug 2010 | A1 |
| 20100228588 | Nielsen et al. | Sep 2010 | A1 |
| 20100245086 | 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 |
| 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 |
| 20100263591 | Nielsen et al. | Oct 2010 | A1 |
| 20100272885 | Olsson | Oct 2010 | A1 |
| 20100285211 | Nielsen et al. | Nov 2010 | A1 |
| 20100318401 | Nielsen et al. | Dec 2010 | A1 |
| 20100318402 | Nielsen et al. | Dec 2010 | A1 |
| 20100318465 | Nielsen et al. | Dec 2010 | A1 |
| 20100324967 | Nielsen et al. | Dec 2010 | 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 |
| 20110060549 | Nielsen et al. | Mar 2011 | A1 |
| 20110093306 | Nielsen et al. | Apr 2011 | A1 |
| 20110117272 | Nielsen et al. | May 2011 | A1 |
| 20110131081 | Nielsen et al. | Jun 2011 | A1 |
| 20110137769 | Nielsen et al. | Jun 2011 | A1 |
| 20110236588 | Nielsen et al. | Sep 2011 | A1 |
| 20110241936 | Sawyer, Jr. et al. | Oct 2011 | A1 |
| 20110249394 | Nielsen et al. | Oct 2011 | A1 |
| 20110279229 | Nielsen et al. | Nov 2011 | A1 |
| 20110279230 | Nielsen et al. | Nov 2011 | A1 |
| 20110279476 | Nielsen et al. | Nov 2011 | A1 |
| 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 |
| 20120083968 | Greiner | Apr 2012 | A1 |
| 20120110019 | Nielsen et al. | May 2012 | A1 |
| 20120113244 | Nielsen et al. | May 2012 | A1 |
| 20120257785 | Narayan et al. | Oct 2012 | A1 |
| 20120259550 | Du | Oct 2012 | A1 |
| 20120274476 | Nielsen et al. | Nov 2012 | A1 |
| 20120290901 | Kim | Nov 2012 | A1 |
| 20120328162 | Nielsen et al. | Dec 2012 | A1 |
| 20120330849 | Nielsen et al. | Dec 2012 | A1 |
| 20130002854 | Nielsen et al. | Jan 2013 | A1 |
| 20130006718 | Nielsen et al. | Jan 2013 | A1 |
| 20130044918 | Nielsen et al. | Feb 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 |
| 20130233883 | Nielsen et al. | Sep 2013 | A1 |
| 20130251894 | Nielsen et al. | Sep 2013 | A1 |
| 20130315449 | Nielsen et al. | Nov 2013 | A1 |
| 20130325542 | Tucker et al. | Dec 2013 | A1 |
| 20140278661 | Nielsen et al. | Sep 2014 | A1 |
| 20140321717 | Nielsen et al. | Oct 2014 | A1 |
| 20140334878 | Miller | Nov 2014 | A1 |
| 20140347396 | Nielsen et al. | Nov 2014 | A1 |
| 20150009608 | Nielsen et al. | Jan 2015 | A1 |
| 20150149242 | Nielsen et al. | May 2015 | A1 |
| 20150170089 | Nielsen et al. | Jun 2015 | A1 |
| 20150193717 | Nielsen et al. | Jul 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2386200 | Apr 2000 | CA |
| 2418157 | Jul 2004 | CA |
| 2423148 | Sep 2004 | CA |
| 2574595 | Feb 2006 | CA |
| 2811172 | Feb 2006 | CA |
| 2528795 | Jun 2007 | CA |
| 2632267 | Jun 2007 | CA |
| 2643844 | Sep 2007 | CA |
| 2713282 | Mar 2013 | CA |
| 1726722 | Nov 2006 | EP |
| 1769270 | Apr 2007 | EP |
| WO02067083 | Aug 2002 | WO |
| WO2005052627 | Jun 2005 | WO |
| WO2006014724 | Feb 2006 | WO |
| WO2007067898 | Jun 2007 | WO |
| WO2007106871 | Sep 2007 | WO |
| WO2008005837 | Jan 2008 | WO |
| Entry |
|---|
| U.S. Appl. No. 13/943,350, filed Jul. 16, 2013, Nielsen et al. |
| 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]. |
| 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. |
| Doyle, K., UGI Utilities: Delivering enhanced service, Energy Digital, http://www.energydigital.com/company-report/ugi-utilities-delivering-enhanced-service (original publication date unknown), retrieved Aug. 1, 2011, 3 pages. |
| Georgia UPC EDEN, Web Entry Instruction Manual, www.gaupc.org, Jan. 22, 2009, 60 pages. |
| GPS Technology Enhancing Underground Utility Locating, Underground Construction Magazine, Apr. 7, 2010, 4 pages, http://www.undergroundconstructionmagazine.com/print/1034?page=show. |
| Haas, J. et al., “Feed the FLAME—Utility Integrates Field Applications,” GeoWorld, Mar. 2007, 5 pages, online: Systems Integration Articles/Enspiria Solutions. |
| InMaps Develops Critical Database Link to Keep UGI Automation on Track, Holderness, NH, Sep. 2006, http://www.inmaps.com/InMaps-develops-critical-database-link-to-keep-ugi-automation-on-track, 1 page. |
| International Search Report and Written Opinion, Application No. PCT/2010/00378 , Apr. 20, 2010. |
| International Search Report and Written Opinion, Application No. PCT/US2011/45203, Dec. 22, 2011. |
| 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, printed Jun. 5, 2010 (original publication date unknown), 2 pages. |
| Notice of Allowance dated Feb. 21, 2013 from U.S. Appl. No. 12/824,612. |
| Notice of Allowance dated May 9, 2013 from U.S. Appl. No. 12/824,635. |
| Notice of Allowance dated May 22, 2013 from U.S. Appl. No. 12/703,313. |
| Notice of Allowance dated May 23, 2013 from U.S. Appl. No. 12/824,655. |
| Notice of Allowance dated Jun. 6, 2013 from U.S. Appl. No. 12/824,635. |
| Notice of Allowance dated Jun. 20, 2013 from U.S. Appl. No. 12/915,516. |
| Notice of Allowance dated Jun. 25, 2012 from U.S. Appl. No. 12/824,671. |
| NTDPC One-Call Mapping Notification Processes, http://www.ntdpc.com/ntdpc/faces/ntscf.jsp, (original publication date unknown), 12 pages. |
| Office Action dated Jan. 19, 2012 from U.S. Appl. No. 12/824,671. |
| Office Action dated Jan. 29, 2013 from U.S. Appl. No. 13/185,174. |
| Office Action dated Jan. 31, 2012 from U.S. Appl. No. 12/703,322. |
| Office Action dated Mar. 26, 2013 from U.S. Appl. No. 12/824,655. |
| Office Action dated Mar. 27, 2012 from U.S. Appl. No. 12/824,635. |
| Office Action dated Apr. 3, 2012 from U.S. Appl. No. 12/703,313. |
| Office Action dated Apr. 8, 2013 from Canadian Application No. 2,690,239. |
| Office Action dated May 7, 2012 from U.S. Appl. No. 13/193,337. |
| Office Action dated May 20, 2013 from U.S. Appl. No. 12/915,516. |
| Office Action dated Jul. 8, 2013 from U.S. Appl. No. 13/185,174. |
| Office Action dated Jul. 13, 2012 from Canadian Application No. 2,690,239. |
| Office Action dated Jul. 15, 2010 from Canadian Application No. 2,690,239, filed Feb. 9, 2010. |
| Office Action dated Aug. 23, 2012 from U.S. Appl. No. 12/824,635. |
| Office Action dated Oct. 2, 2012 from Australian Patent Application No. 2010214044. |
| Office Action dated Oct. 11, 2011 from Canadian Application No. 2,690,239. |
| Office Action dated Oct. 12, 2012 from U.S. Appl. No. 12/824,612. |
| Office Action dated Oct. 15, 2012 from U.S. Appl. No. 12/703,322. |
| Office Action dated Oct. 26, 2011 from U.S. Appl. No. 12/703,313. |
| Office Action dated Dec. 19, 2012 from U.S. Appl. No. 12/915,516. |
| Office Action dated Dec. 28, 2012 from U.S. Appl. No. 13/193,337. |
| Patent Examination Report dated Sep. 5, 2013 from Australian Application No. 2010214044. |
| 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>. |
| Supplemental Notice of Allowability dated May 20, 2013 from U.S. Appl. No. 12/824,612. |
| Supplemental Notice of Allowability dated Aug. 20, 2013 from U.S. Appl. No. 12/703,313. |
| Supplemental Notice of Allowability dated Sep. 24, 2013 from U.S. Appl. No. 12/915,516. |
| Supplemental Notice of Allowability from U.S. Appl. No. 12/824,612 dated Apr. 4, 2013. |
| UGI Utilities Selects KEMA for FLAME Project Implementation, Burlington, Massachusetts, Electric Energy Publications, Inc., Feb. 10, 2004, http://www.eet-d.com/?page=show—news&id=17641, 2 pages. |
| Office Action dated Sep. 20, 2013 from Canadian Application No. 2,690,239. |
| Examination Report dated Oct. 23, 2013 from Australian Application No. 2010214044. |
| Virginia Pilot Project, Incorporating GPS Technology to Enhance One-Call Damage Prevention, Phase I—Electronic White Lining Project Report, Nov. 2007, 50 pages. |
| Phase II of the Virginia Pilot Program, Electronic Manifests, VUPS Project Proposal, Jul. 31, 2007, 7 pages. |
| Virginia State Damage Prevention Program Grants Progress Report, Phase 2, Dec. 23, 2008, 7 pages. |
| Virginia Pilot Project Phase II, Project Team Meeting report, Aug. 31, 2009, 12 pages. |
| Virginia Pilot Project Incorporating GPS Technology to Enhance One-Call Damage Prevention, Phase 2: Electronic Manifests, Project Plan (Business Case), Feb. 2009, 22 pages. |
| UGI Utilities, Inc., FLAME Project White Paper, (original publication date unknown), received Aug. 3, 2011, 12 pages. |
| “Online Service, Software Enable Faster Data Collection,” Mapping underground in real-time, Mar. 2007, pp. 18-19. |
| ArcFM UT, “A GIS for Utilities Based on Standards,” White Paper, AED SICAD, Sep. 2008, 1-28. |
| ArcFM, White Paper, 2006, 1-28. |
| ArcGIS 9, Geocoding in ArcGIS, Manual, 2004, 1-192. |
| ArcPad, Mobile GIS Software for Field Mapping Applications, brochure, 2006, http:/www.esri.com/library/brochures/pdfs/arcpadbro.pdf. |
| ArcPad: Mobile GIS, ESRI White Paper, Sep. 2004, 1-17, http://www.esri.com/library/whitepapers/pdfs/arcpad.pdf. |
| Ayers, S., Technology Update, 21 pages. |
| Bernold, L.E. et al., “A Multi-Sensory Approach to 3-D Mapping of Underground Utilities,” article by Bernold, Venkatesan, and Suvarna, pp. 1-6. |
| Borsan, T. et al., “Setting Up a Database to Record Preventive and Salvage Archeological Excavations,” article by Borsan, Ludsan, Dimen, Ienciu, and Oprea, Dec. 1, 1918, pp. 237-242. |
| Chhabra, K. “Integrated GIS Work Environment with ESRI Products,” A paper for the ESRI Users Conference 2004, 7 pages. |
| Chmura, A. “Project to Create GPS Excavation Monitoring System,” Development of Encroachment Notification, Jul./Aug. 2008, 1 page. |
| Clark et al., “Using ArcPad,” ArcPad 6, 398 pages. |
| Complaint for Patent Infringement dated Apr. 10, 2013, CertusView Technologies LLC v. United States Infrastructure Corporation et al., Case No. 2:13CV182, USDC Eastern District of Virginia. |
| Complaint for Patent Infringement dated May 28, 2013, CertusView Technologies LLC v. S&N Locating Services, LLC et al., Case No. 1:13CV346, USDC Eastern District of Virginia. |
| Corrected Notice of Allowability dated Apr. 25, 2014 from U.S. Appl. No. 13/191,048. |
| Corrected Notice of Allowability dated May 22, 2014 from U.S. Appl. No. 13/191,048. |
| Corrected Notice of Allowability dated May 22, 2014 from U.S. Appl. No. 13/191,058. |
| Corrected Notice of Allowability dated Aug. 21, 2012 from U.S. Appl. No. 12/369,565. |
| Corrected Notice of Allowabilty dated Feb. 27, 2014 from U.S. Appl. No. 13/191,058. |
| Cut Field-Mapping Time in Half Using Mobile GIS, Edgecomb County, 4 pages. |
| DigiTerra Explorer, brochure, v. 6, 2009, 1-2. |
| DigiTerra Explorer, User Manual, v. 5, 2007, 1-64. |
| Edgecomb County, North Carolina, Maps and Inventories Water/Wastewater Infrastructure with GIS and GPS, Field Mapping Time Cut in Half, 4 pages. |
| Eide, S.E. et al., “3D Utility Mapping Using Electronically Scanned Antenna Array,” 9th International Conference on Ground Penetrating Radar, Apr. 29-May 2, 2002, 5 pages. |
| Farag, A., R&D for Damage Prevention, Damage Prevention Conference paper, Apr. 2008, 24 pages. |
| GIS Landbase Solutions, 2 pages. |
| Ground Penetrating Radar Systems webpage, Feb. 28, 2008, 3 pages. |
| H.L. Smith, Letter dated Jan. 14, 2011, with two attachments each dated Jan. 5, 2011. |
| H.L. Smith, Letter dated Oct. 27, 2010. |
| Heath, M. et al., “Comparison of Edge Detectors: A Methodology and Initial Study,” 1996, IEEE Computer Society Press; http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.45.5214. |
| International Search Report and Written Opinion, Application No. PCT/US2009/000859, Apr. 14, 2009. |
| International Search Report, Application No. PCT/US10/041160, Oct. 6, 2010. |
| Kolera, B.T. et al., “Intelligent Utility Locating Tool for Excavators,” Journal of Construction Engineering and Management, Sep. 2006, pp. 919-927. |
| Letter from Norfield Data Products to Wolf Greenfield & Sacks, P.C., May 5, 2010, 2 pages. |
| Loeber, P.C., “An Investigation of Geobase Mission Data Set Design, Implementation, and Usage Within Air Force Civil Engineer Electrical and Utilities Work Centers,” Msgt, USAF, Mar. 2005, 139 pages. |
| Meehan, B., “Empowering Electric and Gas Utilities with GIS,” 264 pages. |
| Miss Utility webpage, Dec. 30, 2007, 2 pages. |
| MobileMapper 6 vs. Juno SC in Real World Conditions, White Paper, 2009 1-16, http://www.sidwellco.com/php/gps—solutions/docs/MM6—vs—Juno—WP—en.pdf. |
| MobileMapper 6, brochure, 2008, 1-4. |
| New Breakthroughs in GIS/GPS Technology Focus on Underground Utility Damage Prevention, Press Release, Jan. 27, 2003, 2 pages. |
| New Technologies Virginia Pilot Project Phases I, II and III, 38 pages. |
| Notice of Alllowance dated Feb. 28, 2014 from U.S. Appl. No. 12/703,322. |
| Notice of Allowability dated Jul. 26, 2013 from U.S. Appl. No. 13/796,487. |
| Notice of Allowance dated Jan. 31, 2013 from U.S. Appl. No. 12/363,046. |
| Notice of Allowance dated Feb. 10, 2014 from U.S. Appl. No. 13/758,336. |
| Notice of Allowance dated Feb. 14, 2014 from U.S. Appl. No. 13/741,080. |
| Notice of Allowance dated Feb. 18, 2014 from U.S. Appl. No. 13/193,337. |
| Notice of Allowance dated Apr. 3, 2014 from U.S. Appl. No. 12/831,330. |
| Notice of Allowance dated Apr. 30, 2012 from U.S. Appl. No. 12/208,846. |
| Notice of Allowance dated Jun. 6, 2013 from U.S. Appl. No. 13/796,487. |
| Notice of Allowance dated Jul. 11, 2012 from U.S. Appl. No. 12/366,050. |
| Notice of Allowance dated Jul. 19, 2013 from U.S. Appl. No. 13/734,415. |
| Notice of Allowance dated Jul. 23, 2012 from U.S. Appl. No. 12/369,565. |
| Notice of Allowance dated Jul. 26, 2013 from U.S. Appl. No. 12/029,732. |
| Notice of Allowance dated Aug. 21, 2012 from U.S. Appl. No. 12/369,232. |
| Notice of Allowance dated Sep. 11, 2013 from U.S. Appl. No. 13/191,048. |
| Notice of Allowance dated Sep. 13, 2013 from U.S. Appl. No. 13/625,436. |
| Notice of Allowance dated Oct. 1, 2012 from U.S. Appl. No. 12/607,843. |
| Notice of Allowance dated Oct. 25, 2012 from U.S. Appl. No. 12/639,373. |
| Notice of Allowance dated Nov. 7, 2012 from U.S. Appl. No. 12/639,041. |
| Notice of Allowance dated Nov. 16, 2012 from U.S. Appl. No. 12/208,846. |
| Notice of Allowance dated Dec. 6, 2013 from U.S. Appl. No. 13/191,048. |
| Notice of Allowance dated Dec. 13, 2011 from U.S. Appl. No. 12/369,565. |
| Notice of Allowance dated Dec. 20, 2013 from U.S. Appl. No. 13/191,058. |
| Notice of Allowance dated Oct. 6, 2011 from Canadian Application No. 2,715,312. |
| Office Action dated Jan. 2, 2013 from U.S. Appl. No. 12/363,009. |
| Office Action dated Jan. 15, 2013 from U.S. Appl. No. 12/029,732. |
| Office Action dated Jan. 15, 2014 from U.S. Appl. No. 13/185,174. |
| Office Action dated Jan. 20, 2012 from U.S. Appl. No. 13/190,138. |
| Office Action dated Feb. 4, 2013 from Australian Application No. 2010270589. |
| Office Action dated Feb. 4, 2013 from Canadian Application No. 2,707,246. |
| Office Action dated Feb. 5, 2014 from U.S. Appl. No. 13/185,194. |
| Office Action dated Feb. 12, 2013 from U.S. Appl. No. 12/833,117. |
| Office Action dated Feb. 16, 2012 from U.S. Appl. No. 12/369,232. |
| Office Action dated Feb. 29, 2012 from U.S. Appl. No. 12/833,117. |
| Office Action dated Mar. 2, 2012 from U.S. Appl. No. 12/831,330. |
| Office Action dated Mar. 8, 2012 from U.S. Appl. No. 13/190,185. |
| Office Action dated Mar. 19, 2012 from U.S. Appl. No. 12/208,846. |
| Office Action dated Apr. 5, 2012 from U.S. Appl. No. 13/191,048. |
| Office Action dated Apr. 6, 2012 from U.S. Appl. No. 13/191,058. |
| Office Action dated Apr. 11, 2012 from U.S. Appl. No. 12/029,732. |
| Office Action dated Apr. 17, 2012 from U.S. Appl. No. 12/607,843. |
| Office Action dated Apr. 22, 2013 from U.S. Appl. No. 13/734,415. |
| Office Action dated Apr. 23, 2012 from U.S. Appl. No. 12/366,050. |
| Office Action dated Apr. 23, 2013 from U.S. Appl. No. 13/191,048. |
| Office Action dated Apr. 25, 2012 from U.S. Appl. No. 12/363,046. |
| Office Action dated May 1, 2012 from U.S. Appl. No. 12/363,009. |
| Office Action dated May 7, 2013 from U.S. Appl. No. 13/191,058. |
| Office Action dated May 20, 2013 from U.S. Appl. No. 13/741,080. |
| Office Action dated May 24, 2012 from U.S. Appl. No. 13/190,138. |
| Office Action dated May 24, 2012 from U.S. Appl. No. 13/194,121. |
| Office Action dated May 28, 2013 from U.S. Appl. No. 13/193,337. |
| Office Action dated Jun. 8, 2012 from U.S. Appl. No. 13/194,163. |
| Office Action dated Jun. 23, 2011 from U.S. Appl. No. 12/208,846. |
| Office Action dated Jun. 28, 2012 from U.S. Appl. No. 12/369,565. |
| Office Action dated Jul. 1, 2013 from U.S. Appl. No. 12/029,732. |
| Office Action dated Jul. 3, 2013 from Canadian Application No. 2,707,246. |
| Office Action dated Jul. 3, 2013 from U.S. Appl. No. 13/758,336. |
| Office Action dated Jul. 13, 2011 from U.S. Appl. No. 12/029,732, filed Feb. 12, 2008. |
| Office Action dated Jul. 17, 2012 from U.S. Appl. No. 12/369,232. |
| Office Action dated Jul. 26, 2012 from Canadian Application No. 2,707,246. |
| Office Action dated Aug. 1, 2013 from U.S. Appl. No. 13/190,138. |
| Office Action dated Aug. 7, 2012 from U.S. Appl. No. 13/190,185. |
| Office Action dated Aug. 9, 2012 from U.S. Appl. No. 12/831,330. |
| Office Action dated Sep. 4, 2013 from U.S. Appl. No. 12/363,009. |
| Office Action dated Oct. 4, 2011 from Canadian Application No. 2,707,246. |
| Office Action dated Oct. 9, 2012 from U.S. Appl. No. 13/190,138. |
| Office Action dated Oct. 10, 2012 from U.S. Appl. No. 13/191,048. |
| Office Action dated Oct. 10, 2012 from U.S. Appl. No. 13/191,058. |
| Office Action dated Oct. 31, 2013 from U.S. Appl. No. 13/953,998. |
| Office Action dated Nov. 4, 2013 from U.S. Appl. No. 13/193,337. |
| Office Action dated Nov. 4, 2013 from U.S. Appl. No. 13/758,336. |
| Office Action dated Nov. 6, 2013 from U.S. Appl. No. 13/741,080. |
| Office Action dated Nov. 21, 2012 from U.S. Appl. No. 13/194,121. |
| Office Action dated Nov. 23, 2011 from U.S. Appl. No. 12/208,846. |
| Office Action dated Nov. 23, 2011 from U.S. Appl. No. 12/363,009. |
| Office Action dated Nov. 27, 2012 from U.S. Appl. No. 13/194,163. |
| Office Action dated Nov. 28, 2013 from Canadian Application No. 2,759,932. |
| Office Action dated Dec. 30, 2013 from Canadian Application No. 2,707,246. |
| Office Action dated Nov. 26, 2010 from Australian Application No. 2009213151. |
| Office Action dated Nov. 29, 2011 from Australian Application No. 2009213151. |
| Office Action dated Oct. 6, 2011 from U.S. Appl. No. 12/366,050. |
| Olst, R. van, “Using I.T. to improve the efficiency and accuracy of Network Data Collection,” IEEE AFRICON 2004, pp. 927-932. |
| 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. |
| One Call Technology Pilot Project, 41 pages. |
| Patent Examination Report dated Dec. 16, 2013 from Australian Application No. 2010214044. |
| Patent Examination Report No. 1 dated Jan. 16, 2014 from Australian Application No. 2011282957. |
| Patent Examination Report No. 1 dated Jan. 21, 2014 from Australian Application No. 2012241082. |
| Patent Examination Report No. 5 dated Apr. 23, 2014 from Australian Application No. 2010214044. |
| 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. |
| Pickering, D. et al., “Utility Mapping and Record Keeping for Infrastructure,” Urban Management Programme, 1946, 84 pages. |
| Plaintiff CertusView Technologies, LLC's Claim Construction Reply Brief dated Mar. 21, 2014, CertusView Technologies, LLC v. S&N Locating Services, LLC et al., Case No. 2:13-cv-346, USDC Eastern District of Virginia. |
| Preliminary Proposed Claim Constructions and Identification of Structure(s), Act(s), or Material(s) Corresponding to Claims Governed by 35 U.S.C. § 112(6), CertusView Technologies, LLC v. S&N Locating Services, LLC et al., Case No. 2:13-cv-346, USDC Eastern District of Virginia. |
| Preliminary Proposed Constructions dated Feb. 14, 2014, CertusView Technologies, LLC v. S&N Locating Services, LLC et al., Case No. 2:13-cv-346, USDC Eastern District of Virginia. |
| Quiroga, C. et al., “A Data Platform for Managing Utilities Along Highway Corridors,” Project No. 0-2110, Report 2110-1, Texas Transportation Institute, Feb. 2002, 88 pages. |
| R. Pevarski, Letter from the Virginia Utility Protection Service, Inc., dated Apr. 7, 2010. |
| Ross, C., “2d Tile Map Editor,” Oct. 19, 2005, http://www.blitzbasic.com/Community/posts.php?topic=52152, pp. 1-3. |
| Ruggiero, K., “Using ArcGIS for Clearing Cable Locates,” ESRI 2006. |
| S&N Location Services, LLC and S&N Communication, Inc.'s Opening Claim Construction Brief dated Mar. 18, 2014, CertusView Technologies, LLC v. S&N Locating Services, LLC et al., Case No. 2:13-cv-346, USDC Eastern District of Virginia. |
| S&N Location Services, LLC and S&N Communication, Inc.'s Reply Claim Construction Brief dated Mar. 21, 2014, CertusView Technologies, LLC v. S&N Locating Services, LLC et al., Case No. 2:13-cv-346, USDC Eastern District of Virginia. |
| Schempf, H. et al., “GRISLEE: Gasmain Repair & Inspection System for Live Entry Environments,” article by Schempf, Mutschler, Goltsberg, and Crowley, 12 pages. |
| Sentinel USA Announces New Alliance with Guardian Angel Protection, Press Release: Jan. 26, 2003, 2 pages. |
| Supplemental Notice of Allowability dated Jul. 2, 2013 from U.S. Appl. No. 13/796,487. |
| Supplemental Notice of Allowance dated Jul. 27, 2012 from U.S. Appl. No. 12/366,050. |
| Toyama, K. et al., “Geographic Location Tags on Digital Images,” article by Toyama, Logan, Roseway, and Anandan, pp. 156-166. |
| Trimble Comprehensive Utilities, brochure, 2010, 1-6. |
| Ultimate Utility Management System to be Unveiled at Planet Underground, The Planet Underground, 2 pages. |
| Underground, pages from magazine, Jan./Feb. 2003 issue, 4 pages. |
| Utility Notification Center webpage, Mar. 4, 2008, 2 pages. |
| Utility Sciences Corporation to Attend Trade Show, SpatialNews.com Press Release, 2 pages. |
| Vanaartsen, S.J., GIS Automates Utility One Call Process, Proceeding ESRI, 1-15, http://proceedings.esri.com/library/useconf/proc06/papers/papers/pap—1148.pdf. |
| Vandeberg, G., “Introduction to ArcPad: Mobile GIS,” ND GIS Users Conference, Oct. 26, 2006, 30 pages. |
| Virginia Damage Prevention Conference Agenda, Apr. 20-22, 2010, 6 pages. |
| Virginia Damage Prevention Conference Agenda, Apr. 21-23, 2009, 5 pages. |
| Virginia Damage Prevention Conference Agenda, Apr. 8-10, 2008, 5 pages. |
| w3schools; “JavaScript Pop Up Boxes,” Aug. 11, 2005; http://www.w3schools.com/js/js—popup.asp, pp. 1-2. |
| Nielsen et al., Co-pending U.S. Publication No. 2014, published Jan. 23, 2014. |
| Notice of Allowance dated Aug. 21, 2014 from U.S. Appl. No. 13/185,174. |
| Notice of Allowance dated Aug. 4, 2014 from U.S. Appl. No. 13/741,080. |
| Office Action dated Jul. 18, 2014 from U.S. Appl. No. 13/185,194. |
| Office Action dated Jul. 30, 2014 from U.S. Appl. No. 13/194,121. |
| Notice of Allowance dated Jul. 18, 2014 from U.S. Appl. No. 13/193,337. |
| Notice of Allowance dated Aug. 13, 2014 from U.S. Appl. No. 12/831,330. |
| Notice of Allowance dated Aug. 18, 2014 from U.S. Appl. No. 13/190,138. |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and of U.S. Patent No. 8,290,204 in view of American Society of Civil Engineers Standard Guideline for the Collection and Depiction of Existing Subsurface Utility Data (“ASCE”) (Exhibit 11-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of American Society of Civil Engineers Standard Guideline for the Collection and Depiction of Existing Subsurface Utility Data (“ASCE”) (Exhibit 11-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of American Society of Civil Engineers Standard Guideline for the Collection and Depiction of Existing Subsurface Utility Data (“ASCE”) (Exhibit 11-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of American Society of Civil Engineers Standard Guideline for the Collection and Depiction of Existing Subsurface Utility Data (“ASCE”) (Exhibit 11-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of American Society of Civil Engineers Standard Guideline for the Collection and Depiction of Existing Subsurface Utility Data (“ASCE”) (Exhibit 11-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Department of Transportation Federal Highway Administration, Publication No. FHWA-IF-02-049 (Exhibit 12-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Department of Transportation Federal Highway Administration, Publication No. FHWA-IF-02-049 (Exhibit 12-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Department of Transportation Federal Highway Administration, Publication No. FHWA-IF-02-049 (Exhibit 12-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Department of Transportation Federal Highway Administration, Publication No. FHWA-IF-02-049 (Exhibit 12-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Department of Transportation Federal Highway Administration, Publication No. FHWA-IF-02-049 (Exhibit 12-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Finding Buried Utilities Before They Find You,” article by Daniel P. Duffy (Exhibit 13-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Finding Buried Utilities Before They Find You,” article by Daniel P. Duffy (Exhibit 13-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Finding Buried Utilities Before They Find You,” article by Daniel P. Duffy (Exhibit 13-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Finding Buried Utilities Before They Find You,” article by Daniel P. Duffy (Exhibit 13-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of “Finding Buried Utilities Before They Find You,” article by Daniel P. Duffy (Exhibit 13-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Triangulation, http://searchnetworking.techtarget.com/definition/triangulation (Exhibit 14-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Triangulation, http://searchnetworking.techtarget.com/definition/triangulation (Exhibit 14-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Triangulation, ttp://searchnetworking.techtarget.com/definition/triangulation (Exhibit 14-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Triangulation, http://searchnetworking.techtarget.com/definition/triangulation (Exhibit 14-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Triangulation, http://searchnetworking.techtarget.com/definition/triangulation (Exhibit 14-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” presentation by Joe Zhou at Canberra Joint Technical Meeting (Exhibit 15-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” presentation by Joe Zhou at Canberra Joint Technical Meeting (Exhibit 15-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of New Approaches for Preventing Damage to Gas and Oil Pipelines, presentation by Joe Zhou at Canberra Joint Technical Meeting (Exhibit 15-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” presentation by Joe Zhou at Canberra Joint Technical Meeting (Exhibit 15-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” presentation by Joe Zhou at Canberra Joint Technical Meeting (Exhibit 15-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” article by Joe Zhou for Canberra Joint Technical Meeting (Exhibit 16-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” article by Joe Zhou for Canberra Joint Technical Meeting (Exhibit 16-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” article by Joe Zhou for Canberra Joint Technical Meeting (Exhibit 16-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” article by Joe Zhou for Canberra Joint Technical Meeting (Exhibit 16-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “New Approaches for Preventing Damage to Gas and Oil Pipelines,” article by Joe Zhou for Canberra Joint Technical Meeting (Exhibit 16-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Phase I—Electronic White Lining Project Report (Nov. 2007) (Exhibit 17-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Phase I—Electronic White Lining Project Report (Nov. 2007) (Exhibit 17-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Phase I—Electronic White Lining Project Report (Nov. 2007) (Exhibit 17-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Phase I—Electronic White Lining Project Report (Nov. 2007) (Exhibit 17-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Phase I—Electronic White Lining Project Report (Nov. 2007) (Exhibit 17-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Technologies to Accurately and Cost-Effectively Detect and Identify Unauthorized Acitivity Near Pipelines (Exhibit 18-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Technologies to Accurately and Cost-Effectively Detect and Identify Unauthorized Activity Near Pipelines (Exhibit 18-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Technologies to Accurately and Cost-Effectively Detect and Identify Unauthorized Activity Near Pipelines (Exhibit 18-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Technologies to Accurately and Cost-Effectively Detect and Identify Unauthorized Activity Near Pipelines (Exhibit 18-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Technologies to Accurately and Cost-Effectively Detect and Identify Unauthorized Activity Near Pipelines (Exhibit 18-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Virginia Pilot Program—Phases I and II (Exhibit 1-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED; CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Virginia Pilot Program—Phases I and II (Exhibit 1-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Virginia Pilot Program—Phases I and II (Exhibit 1-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Virginia Pilot Program—Phases I and II (Exhibit 1-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 29 and 30 of U.S. Patent No. 8,407,001 in view of Virginia Pilot Program—Phases I and II (Exhibit 1-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Project to Create GPS Excavation Monitoring System,” Underground Focus (Exhibit 24-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Project to Create GPS Excavation Monitoring System,” Underground Focus (Exhibit 24-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Project to Create GPS Excavation Monitoring System,” Underground Focus (Exhibit 24-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Project to Create GPS Excavation Monitoring System,” Underground Focus (Exhibit 24-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “Project to Create GPS Excavation Monitoring System,” Underground Focus (Exhibit 24-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Edgecombe County, Cut Field-Mapping Time in Half Using Mobile GIS (Exhibit 25-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Edgecombe County, Cut Field-Mapping Time in Half Using Mobile GIS (Exhibit 25-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Edgecombe County, Cut Field-Mapping Time in Half Using Mobile GIS (Exhibit 25-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Edgecombe County, Cut Field-Mapping Time in Half Using Mobile GIS (Exhibit 25-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Edgecombe County, Cut Field-Mapping Time in Half Using Mobile GIS (Exhibit 25-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Introduction to ArcPad Mobile GIS,” Gregory Vandeberg, Ph.D., presentation at ND GIS Users Conference (Exhibit 26-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Introduction to ArcPad Mobile GIS,” Gregory Vandeberg, Ph.D., presentation at ND GIS Users Conference (Exhibit 26-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Introduction to ArcPad Mobile GIS,” Gregory Vandeberg, Ph.D., presentation at ND GIS Users Conference (Exhibit 26-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “Introduction to ArcPad Mobile GIS,” Gregory Vandeberg, Ph.D., presentation at ND GIS Users Conference (Exhibit 26-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Introduction to ArcPad Mobile GIS,” Gregory Vandeberg, Ph.D., presentation at ND GIS Users Conference (Exhibit 26-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Using ArcPad,” ArcPad 6, Clarke, Greenwald, and Spalding (Exhibit 27-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Using ArcPad,” ArcPad 6, Clarke, Greenwald, and Spalding (Exhibit 27-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Using ArcPad,” ArcPad 6, Clarke, Greenwald, and Spalding (Exhibit 27-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Using ArcPad,” ArcPad 6, Clarke, Greenwald, and Spalding (Exhibit 27-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “Using ArcPad,” ArcPad 6, Clarke, Greenwald, and Spalding (Exhibit 27-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Integrated GIS Work Environment With ESRI Products, Paper for ESRI Users Conference 2004 (Exhibit 28-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Integrated GIS Work Environment With ESRI Products, Paper for ESRI Users Conference 2004 (Exhibit 28-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Integrated GIS Work Environment With ESRI Products, Paper for ESRI Users Conference 2004 (Exhibit 28-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Integrated GIS Work Environment With ESRI Products, Paper for ESRI Users Conference 2004 (Exhibit 28-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Integrated GIS Work Environment With ESRI Products, Paper for ESRI Users Conference 2004 (Exhibit 28-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of US 2012/0259550 (Exhibit 29-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 2012/0259550 (Exhibit 29-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 2012/0259550 (Exhibit 29-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 2012/0259550 (Exhibit 29-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 2012/0259550 (Exhibit 29-E); S&N Invalidity Contentions; Case 2:13-cv00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Tucker References (Exhibit 2-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 21 and 23 of U.S. Patent No. 8,340,359 in view of Tucker References (Exhibit 2-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Tucker References (Exhibit 2-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Tucker References (Exhibit 2-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Tucker References (Exhibit 2-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of US 8150826 (Exhibit 30-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 8150826 (Exhibit 30-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 8150826 (Exhibit 30-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 8150826 (Exhibit 30-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 8150826 (Exhibit 30-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of US 2004/0168358 (Exhibit 31-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 2004/0168358 (Exhibit 31-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 2004/0168358 (Exhibit 31-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 2004/0168358 (Exhibit 31-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 2004/0168358 (Exhibit 31-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of US 6,597,992 (Exhibit 32-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 6,597,992 (Exhibit 32-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 6,597,992 (Exhibit 32-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 6,597,992 (Exhibit 32-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 6,597,992 (Exhibit 32-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of US 2007/0118278 (Exhibit 33-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 2007/0118278 (Exhibit 33-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 2007/0118278 (Exhibit 33-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 2007/0118278 (Exhibit 33-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 2007/0118278 (Exhibit 33-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Patent No. 5,991,694 (Gudat) (Exhibit 34-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Patent No. 5,991,694 (Gudat) (Exhibit 34-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Patent No. 5,991,694 (Gudat) (Exhibit 34-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Patent No. 5,991,694 (Gudat) (Exhibit 34-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Patent No. 5,991,694 (Gudat) (Exhibit 34-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of a Data Platform for Managing Utilities Along Highway Corridors (Exhibit 35-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of a Data Platform for Managing Utilities Along Highway Corridors (Exhibit 35-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of a Data Platform for Managing Utilities Along Highway Corridors (Exhibit 35-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of a Data Platform for Managing Utilities Along Highway Corridors (Exhibit 35-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of a Data Platform for Managing Utilities Along Highway Corridors (Exhibit 35-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of an Investigation of Geobase Mission Data Set Design, Implementation, & Usage Within Air Force Civil Engineer Electrical and Utilities Work Centers (Exhibit 36-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of an Investigation of Geobase Mission Data Set Design, Implementation, & Usage Within Air Force Civil Engineer Electrical and Utilities Work Centers (Exhibit 36-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of an Investigation of Geobase Mission Data Set Design, Implementation, & Usage Within Air Force Civil Engineer Electrical and Utilities Work Centers (Exhibit 36-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of an Investigation of Geobase Mission Data Set Design, Implementation, & Usage Within Air Force Civil Engineer Electrical and Utilities Work Centers (Exhibit 36-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of an Investigation of Geobase Mission Data Set Design, Implementation, & Usage Within Air Force Civil Engineer Electrical and Utilities Work Centers (Exhibit 36-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Using I.T. to Improve the Efficiency and Accuracy of Network Data Collection,” IEEE AFRICON, Rex van Olst and Barry Dwolatzky (Exhibit 37-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Using I.T. to Improve the Efficiency and Accuracy of Network Data Collection,” IEEE AFRICON, Rex van Olst and Barry Dwolatzky (Exhibit 37-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Using I.T. to Improve the Efficiency and Accuracy of Network Data Collection,” IEEE AFRICON, Rex van Olst and Barry Dwolatzky (Exhibit 37-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Using I.T. to Improve the Efficiency and Accuracy of Network Data Collection,” IEEE AFRICON, Rex van Olst and Barry Dwolatzky (Exhibit 37-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “Using I.T. to Improve the Efficiency and Accuracy of Network Data Collection,” IEEE AFRICON, Rex van Olst and Barry Dwolatzky (Exhibit 37-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Intelligent Utility Locating Tool for Excavators, Kolera and Bernold (Exhibit 38-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Intelligent Utility Locating Tool for Excavators, Kolera and Bernold (Exhibit 38-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Intelligent Utility Locating Tool for Excavators, Kolera and Bernold (Exhibit 38-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Intelligent Utility Locating Tool for Excavators, Kolera and Bernold (Exhibit 38-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Intelligent Utility Locating Tool for Excavators, Kolera and Bernold (Exhibit 38-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “GRISLEE: Gasmain Repair & Inspection System for Live Entry Environments,” article by Schempf, Mutschler, Goltsberg, and Crowley (Exhibit 39-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “GRISLEE: Gasmain Repair & Inspection System for Live Entry Environments,” article by Schempf, Mutschler, Goltsberg, and Crowley (Exhibit 39-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “GRISLEE: Gasmain Repair & Inspection System for Live Entry Environments,” article by Schempf, Mutschler, Goltsberg, and Crowley (Exhibit 39-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “GRISLEE: Gasmain Repair & Inspection System for Live Entry Environments,” article by Schempf, Mutschler, Goltsberg, and Crowley (Exhibit 39-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “GRISLEE: Gasmain Repair & Inspection System for Live Entry Environments,” article by Schempf, Mutschler, Goltsberg, and Crowley (Exhibit 39-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Guardian ProStar/ProStar Data Collection Software (PointMan and/or Predator Products (Oct. 15, 2006) (Exhibit 3-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Guardian ProStar/ProStar Data Collection Software (PointMan and/or Predator Products) (Oct. 15, 2006); (Exhibit 3-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Guardian ProStar/ProStar Data Collection Software (PointMan and/or Predator Products) (Oct. 15, 2006) (Exhibit 3-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Guardian ProStar/ProStar Data Collection Software (PointMan and/or Predator Products) (Oct. 15, 2006) (Exhibit 3-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Guardian ProStar/ProStar Data Collection Software (PointMan and/or Predator Products) (Oct. 15, 2006) (Exhibit 3-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Empowering Electric and Gas Utilities with GIS (Exhibit 40-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Empowering Electric and Gas Utilities with GIS (Exhibit 40-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Empowering Electric and Gas Utilities with GIS (Exhibit 40-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Empowering Electric and Gas Utilities with GIS (Exhibit 40-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Empowering Electric and Gas Utilities with GIS (Exhibit 40-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Pub. No. 2005/0183028A1 (Aug. 18, 2005) (Exhibit 41-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Pub. No. 2005/0183028A1 (Aug. 18, 2005) (Exhibit 41-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Pub. No. 2005/0183028A1 (Aug. 18, 2005) (Exhibit 41-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Pub. No. 2005/0183028A1 (Aug. 18, 2005) (Exhibit 41-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Pub. No. 2005/0183028A1 (Aug. 18, 2005) (Exhibit 41-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Pat. No. 6,701,647 (Mar. 9, 2004) (Exhibit 42-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Pat. No. 6,701,647 (Mar. 9, 2004) (Exhibit 42-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Pat. No. 6,701,647 (Mar. 9, 2004) (Exhibit 42-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Pat. No. 6,701,647 (Mar. 9, 2004) (Exhibit 42-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Pat. No. 6,701,647 (Mar. 9, 2004) (Exhibit 42-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Patent No. 7,372,276 (Exhibit 43-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Patent No. 7,372,276 (Exhibit 43-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Patent No. 7,372,276 (Exhibit 43-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Patent No. 7,372,276 (Exhibit 43-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Patent No. 7,372,276 (Exhibit 43-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Patent No. 6,957,250 (hereinafter referred to as “Nakano”) (Exhibit 44-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Patent No. 6,957,250 (hereinafter referred to as “Nakano”) (Exhibit 44-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Patent No. 6,957,250 (hereinafter referred to as “Nakano”) (Exhibit 44-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Patent No. 6,957,250 (hereinafter referred to as “Nakano”) (Exhibit 44-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Patent No. 6,957,250 (hereinafter referred to as “Nakano”) (Exhibit 44-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of U.S. Patent Publication No. 2002/0059296 (Exhibit 45-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of U.S. Patent Publication No. 2002/0059296 (Exhibit 45-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of U.S. Patent Publication No. 2002/0059296 (Exhibit 45-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of U.S. Patent Publication No. 2002/0059296 (Exhibit 45-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of U.S. Patent Publication No. 2002/0059296 (Exhibit 45-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view US 2007/0258642 (Exhibit 46-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 2007/0258642 (Exhibit 46-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 2007/0258642 (Exhibit 46-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 2007/0258642 (Exhibit 46-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 2007/0258642 (Exhibit 46-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of US 2002/0044690 (Exhibit 47-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of US 2002/0044690 (Exhibit 47-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of US 2002/0044690 (Exhibit 47-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of US 2002/0044690 (Exhibit 47-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of US 2002/0044690 (Exhibit 47-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Article titled “Setting Up a Database to Record Preventative and Salvage Archeological Excavations,” by Borsan, Ludusan, Dimen, Ienciu, and Oprea (hereinafter referred to as “Borsan”) (Exhibit 48-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Article titled “Setting Up a Database to Record Preventative and Salvage Archeological Excavations,” by Borsan, Ludusan, Dimen, Ienciu, and Oprea (hereinafter referred to as “Borsan”) (Exhibit 48-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Article titled “Setting Up a Database to Record Preventative and Salvage Archeological Excavations,” by Borsan, Ludusan, Dimen, Ienciu, and Oprea (hereinafter referred to as “Borsan”) (Exhibit 48-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Article titled “Setting Up a Database to Record Preventative and Salvage Archeological Excavations,” by Borsan, Ludusan, Dimen, Ienciu, and Oprea (hereinafter referred to as “Borsan”) (Exhibit 48-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Article titled “Setting Up a Database to Record Preventative and Salvage Archeological Excavations,” by Borsan, Ludusan, Dimen, Ienciu, and Oprea (hereinafter referred to as “Borsan”) (Exhibit 48-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “A Multi-Sensory Approach to 3-D Mapping of Underground Utilities” by Leonard E. Bernold and Lashminarayan Venkatesan (hereinafter referred to as the “Bernold” reference) (Exhibit 49-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “A Multi-Sensory Approach to 3-D Mapping of Underground Utilities” by Leonard E. Bernold and Lashminarayan Venkatesan (hereinafter referred to as the “Bernold” reference) (Exhibit 49-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “A Multi-Sensory Approach to 3-D Mapping of Underground Utilities” by Leonard E. Bernold and Lashminarayan Venkatesan (hereinafter referred to as the “Bernold” reference) (Exhibit 49-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “A Multi-Sensory Approach to 3-D Mapping of Underground Utilities” by Leonard E. Bernold and Lashminarayan Venkatesan (hereinafter referred to as the “Bernold” reference) (Exhibit 49-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “A Multi-Sensory Approach to 3-D Mapping of Underground Utilities” by Leonard E. Bernold and Lashminarayan Venkatesan (hereinafter referred to as the “Bernold” reference) (Exhibit 49-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Guardian ProStar/ProStar Web Services (Oct. 15, 2006) (Exhibit 4-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Guardian ProStar/ProStar Web Services (Oct. 15, 2006) (Exhibit 4-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Guardian ProStar/ProStar Web Services (Oct. 15, 2006) (Exhibit 4-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Guardian ProStar/ProStar Web Services (Oct. 15, 2006) (Exhibit 4-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Guardian ProStar/ProStar Web Services (Oct. 15, 2006) (Exhibit 4-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Geographic Location Tags on Digital Images (Exhibit 50-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Geographic Location Tags on Digital Images (Exhibit 50-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Geographic Location Tags on Digital Images (Exhibit 50C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Geographic Location Tags on Digital Images (Exhibit 50-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Geographic Location Tags on Digital Images (Exhibit 50-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “3D Utility Mapping Electronically Scanned Antenna Array” by Egil Side and Jens F. Hjelmstad (the “Eide” Reference) (Exhibit 51-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “3D Utility Mapping Electronically Scanned Antenna Array” by Egil Side and Jens F. Hjelmstad (the “Eide” Reference) (Exhibit 51-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “3D Utility Mapping Electronically Scanned Antenna Array” by Egil Side and Jens F. Hjelmstad (the “Eide” Reference) (Exhibit 51-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “3D Utility Mapping Electronically Scanned Antenna Array” by Egil Side and Jens F. Hjelmstad (the “Eide” Reference) (Exhibit 51-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “3D Utility Mapping Electronically Scanned Antenna Array” by Egil Side and Jens F. Hjelmstad (the “Eide” Reference) (Exhibit 51-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Common Ground—Study of One-Call Systems and Damage Prevention Best Practices (“Common Ground”) (Exhibit 52-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Common Ground—Study of One-Call Systems and Damage Prevention Best Practices (“Common Ground”) (Exhibit 52-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Common Ground—Study of One-Call Systems and Damage Prevention Best Practices (“Common Ground”) (Exhibit 52-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Common Ground—Study of One-Call Systems and Damage Prevention Best Practices (“Common Ground”) (Exhibit 52-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of Common Ground—Study of One-Call Systems and Damage Prevention Best Practices (“Common Ground”) (Exhibit 52-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Merging Two GIS Platforms for Utility Data into One: FRAMME to ESRI Conversion and all of the other pieces and parts” (2005) (Exhibit 53-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Merging Two GIS Platforms for Utility Data into One: FRAMME to ESRI Conversion and all of the other pieces and parts” (2005) (Exhibit 53-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Merging Two GIS Platforms for Utility Data into One: FRAMME to ESRI Conversion and all of the other pieces and parts” (2005) (Exhibit 53-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Merging Two GIS Platforms for Utility Data into One: FRAMME to ESRI Conversion and all of the other pieces and parts” (2005) (Exhibit 53-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of “Merging Two GIS Platforms for Utility Data into One: FRAMME to ESRI Conversion and all of the other pieces and parts” (2005) (Exhibit 53-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of GIS for Public Works Presentation (Aug. 2006) (Exhibit 54-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of GIS for Public Works Presentation (Aug. 2006) (Exhibit 54-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of GIS for Public Works Presentation (Aug. 2006) (Exhibit 54-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of GIS for Public Works Presentation (Aug. 2006) (Exhibit 54-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of GIS for Public Works Presentation (Aug. 2006) (Exhibit 54-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of OnPoint Software (2005) (Exhibit 55-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of OnPoint Software (2005) (Exhibit 55-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of OnPoint Software (2005) (Exhibit 55-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of OnPoint Software (2005) (Exhibit 55-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of OnPoint Software (2005) (Exhibit 55-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of ArcIMS Software (2000) (Exhibit 56-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of ArcIMS Software (2000) (Exhibit 56-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of ArcIMS Software (2000) (Exhibit 56-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of ArcIMS Software (2000) (Exhibit 56-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of ArcIMS Software (2000) (Exhibit 56-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of GO! Sync™ Software (2005) (Exhibit 57-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of GO! Sync™ Software (2005) (Exhibit 57-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of GO! Sync™ Software (2005) (Exhibit 57-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Go! Sync™ Software (2005) (Exhibit 57-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of GO! Sync™ Software (2005) (Exhibit 57-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of ArcPad 6 Software (2000) (Exhibit 58-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of ArcPad 6 Software (2000) (Exhibit 58-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of ArcPad 6 Software (2000) (Exhibit 58-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of ArcPad 6 Software (2000) (Exhibit 58-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of ArcPad 6 Software (2000) (Exhibit 58-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of ArcGIS Software (2000) (Exhibit 59-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of ArcGIS Software (2000) (Exhibit 59-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of ArcGIS Software (2000) (Exhibit 59-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of ArcGIS Software (2000) (Exhibit 59-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Patent No. 8,407,001 in view of ArcGIS Software (2000) (Exhibit 59-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Guardian ProStar/ProStar Web Portal (Oct. 15, 2006) (Exhibit 5-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Guardian ProStar/ProStar Web Portal (Oct. 15, 2006) (Exhibit 5-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Guardian ProStar/ProStar Web Portal (Oct. 15, 2006) (Exhibit 5-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Guardian ProStar/ProStar Web Portal (Oct. 15, 2006) (Exhibit 5D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Guardian ProStar/ProStar Web Portal (Oct. 15, 2006) (Exhibit 5-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 of Guardian ProStar/ProStar Data Services (Oct. 15, 2006) (Exhibit 6-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Guardian ProStar/ProStar Data Services (Oct. 15, 2006) (Exhibit 6-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Guardian ProStar/ProStar Data Services (Oct. 15, 2006) (Exhibit 6-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Guardian ProStar/ProStar Data Services (Oct. 15, 2006) (Exhibit 6-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Guardian ProStar/ProStar Data Services (Oct. 15, 2006) (Exhibit 6-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of Guardian ProStar/ProStar Mapping Components (Oct. 15, 2006) (Exhibit 7-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of Guardian ProStar/ProStar Mapping Components (Oct. 15, 2006) (Exhibit 7-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of Guardian ProStar/ProStar Mapping Components (Oct. 15, 2006) (Exhibit 7-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of Guardian ProStar/ProStar Mapping Components (Oct. 15, 2006) (Exhibit 7-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of Guardian ProStar/ProStar Mapping Components (Oct. 15, 2006) (Exhibit 7-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Patent No. 8,290,204 in view of “Online Service, Software Enable Faster Data Collection” article in Underground Focus (Mar. 2007) (Exhibit 8-A); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Patent No. 8,340,359 in view of “Online Service, Software Enable Faster Data Collection” article in Underground Focus (Mar. 2007) (Exhibit 8-B); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18, 19, 20, 23, 24, 25 and 26 of U.S. Patent No. 8,265,344 in view of “Online Service, Software Enable Faster Data Collection” article in Underground Focus (Mar. 2007) (Exhibit 8-C); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Patent No. 8,532,341 in view of “Online Service, Software Enable Faster Data Collection” article in Underground Focus (Mar. 2007) (Exhibit 8-D); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart for claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29 and 30 of U.S. Patent No. 8,407,001 in view of “Online Service, Software Enable Faster Data Collection” article in Underground Focus (Mar. 2007) (Exhibit 8-E); S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Prior Art Table; S&N Invalidity Contentions; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Opinion and Order Following Markman Hearing, May 16, 2014; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; (Eastern District of Virginia). |
| Georgia Underground Marking Standards, PSC Rule 515-9-4.14, published online May 2, 2008, http://www.gaupc.com/userfiles/file/Marking—Standards—Presentation—05—02—08.pdf. |
| Expert CV and Testimony of Ivan Zatkovich (10 pages); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of WO 2007/106871 (“Tucker '871”) to Claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Pat. No. 8,290,204 (Exhibit 2-A); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of WO 2007/106871 (“Tucker '871”) to Claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Pat. No. 8,340,359 (Exhibit 2-B); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of WO 2007/106871 (“Tucker '871”) to Claims 1-2, 4-7, 10-15, 1720, and 23-26 of U.S. Pat. No. 8,265,344 (Exhibit 2-C); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of WO 2007/106871 (“Tucker '871”) to Claims 1, 3-7, 9-10, 12, 14, 16-20, 22-23, 25 and 28 of U.S. Pat. No. 8,532,341 (Exhibit 2-D); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of WO 2007/106871 (“Tucker '871”) to Claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Pat. No. 8,407,001 (Exhibit 2-E); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II to Claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Pat. No. 8,290,204 (Exhibit 4-A); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II to Claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Pat. No. 8,340,359 (Exhibit 4-B); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II to Claims 1-2, 4-7, 10-15, 17-20, and 23-26 of U.S. Pat. No. 8,265,344 (Exhibit 4-C); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II to Claims 1, 3-7, 9-10, 12, 14, 16-20, 22-23, 25, and 28 of U.S. Pat. No. 8,532,341 (Exhibit 4-D); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II to Claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Pat. No. 8,407,001 (Exhibit 4-E); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems to Claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Pat. No. 8,290,204 (Exhibit 5-A); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems to Claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Pat. No. 8,340,359 (Exhibit 5-B); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems to Claims 1, 2, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 17, 18 19, 20, 23, 24, 25 and 26 of U.S. Pat. No. 8,265,344 (Exhibit 5-C); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems to Claims 1, 3, 4, 5, 6, 7, 9, 10, 12, 14, 16, 17, 18, 19, 20, 22, 23, 25 and 28 of U.S. Pat. No. 8,532,341 (Exhibit 5-D); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems to Claims 1, 3, 13, 14, 16, 18, 22, 27, 28, 29, and 30 of U.S. Pat. No. 8,407,001 (Exhibit 5-E); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Tel-Dig One Call Brochure (1 page) (Exhibit 6); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Tel-Dig Junior—The most advanced system on earth—and below Brochure (5 pages) (Exhibit 7); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and Avoiding Utility Regulations to Claims 1-2, 17, 19-22, 40 and 42 of U.S.P.N. 8,290,204 (Exhibit 8-A); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and Avoiding Utility Regulations to Claims 1-2, 5, 10, 12, 18, 20-21 and 23 of U.S.P.N. 8,340,359 (Exhibit 8-B); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and Avoiding Utility Regulations to Claims 1-2, 4-7, 10-15, 17-20, and 23-26 of U.S.P.N. 8,265,344 (Exhibit 8-C); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and Avoiding Utility Regulations to Claims 1, 3-7, 9-10, 12, 14, 16-20, 22-23, 25 and 28 of U.S.P.N. 8,532,341 (Exhibit 8-D); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and Avoiding Utility Regulations to Claims 1, 3, 13-14, 16, 18, 22, and 27-30 of U.S. Pat. No. 8,407,001 (Exhibit 8-E); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems and ESRI to Claims 1, 2, 17, 19, 20, 21, 22, 40 and 42 of U.S. Pat. No. 8,290,204 (Exhibit 9-A); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems and ESRI to Claims 1, 2, 5, 10, 12, 18, 20, 21 and 23 of U.S. Pat. No. 8,340,359 (Exhibit 9-B); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems and ESRI to Claims 1-2, 4-7, 10-15, 17-20, and 23-26 of U.S.P.N. 8,265,344 (Exhibit 9-C); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of TelDig Systems and ESRI to Claims 1, 3-7, 9-10, 12, 14, 16-20, 22-23, 25 and 28 of U.S. Pat. No. 8,532,341 (Exhibit 9-D); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and WO 2008/005837 (Tucker '837) to Claims 1, 2, 17, 19, 20-22, 40 and 42 of U.S.P.N. 8,290,204 (Exhibit 10-A); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and WO 2008/005837 (Tucker '837) to Claims 1-2, 5, 10, 12, 18, 20-21 and 23 of U.S.P.N. 8,340,359 (Exhibit 10-B); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and WO 2008/005837 (Tucker '837) to Claims 1-2, 4-7, 10-15, 17-20, and 23-26 of U.S.P.N. 8,265,344 (Exhibit 10-C); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Invalidity Claim Chart—Application of Virginia Pilot Program—Phases I and II and WO 2008/005837 (Tucker '837) to Claims 1, 3-7, 9-10, 12, 14, 16-20, 22-23, 25 and 28 of U.S.P.N. 8,532,341 (Exhibit 10-D); Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| Expert Report of Ivan Zatkovich Regarding the Invalidity of U.S. Pat. Nos. 8,265,344, 8,290,204, 8,340,359, 8,407,001, and 8,532,341, dated Sep. 3, 2014; Case 2:13-cv-00346-MSD-LRLVAED CertusView Technologies, LLC v. S&N Locating Services; Apr. 29, 2014 (Eastern District of Virginia). |
| GIS Best Practices, GIS for Public Works, Aug. 2006, 26 pages. |
| 2001-2004 News, Jul. 5, 2004 City of Madison Implements TelDig Utility & TelDig Mobile, 12 pages. |
| TelDig Mobile, Locate ticket-receiving software for remote users, p. 1. |
| TelDig Mobile, Locate ticket-receiving software for remote users, p. 2. |
| Mobile Computing Makes its Move on Utility Field Automotion, Mar. 1, 1996, 6 pages. |
| Progress Energy Chooses MapFrame's FieldSmart Software for Mobile Mapping & Field Automation, IntelligentUtility, Jul. 17, 2003, 3 pages. |
| Maps joining tickets on ARKUPS' computers in trucks, ARKUPS, Jan., Feb., Mar., 2003, 2 pages. |
| Collection and Depiction of Existing Subsurface Utility Data, pp. 7-9. |
| Avoiding Utility Relocations, U.S. Department of Transportation Federal Highway Administration, Publication No. FHWA-IF-02-049, Jul. 2002, 128 pages. |
| Underground Utility Damage Prevention, Virginia's Pilot Program, Jan. 2006, 15 pages. |
| Underground Facility Damage Prevention, Virginia's Pilot Program for One-call Location Technology Business Case, Jun. 2006, 37 pages. |
| Project Plan, VA Pilot Project, Draft, Aug. 24, 2009, 15 pages. |
| Virginia Pilot Project, Incorporating GPS Technology to Enhance One-Call Damage Prevention, Phase I—Electronic White Lining Project Report, Nov. 2007, 41 pages. |
| One Call Technology Pilot Project, Trimble Meeting, Aug. 25, 2006, 5 pages. |
| Virginia Utility Projection Service, Inc. (VUPS), Project Proposal to: U.S. Department of Transportation Pipeline & Hazardous Materials Safety Administration, Phase II of the Virginia Pilot Program Electronic Manifests, Jul. 31, 2007, 16 pages. |
| Office Action dated Sep. 19, 2014 from U.S. Appl. No. 13/194,163. |
| Office Action dated Aug. 26, 2014 from Canadian Application No. 2,707,246. |
| Notice of Allowance dated Sep. 12, 2014 from U.S. Appl. No. 13/191,048. |
| Office Action dated Oct. 10, 2014 from U.S. Appl. No. 13/190,185. |
| Examination Report dated Oct. 9, 2014 from Australian Application No. 2013204039. |
| Office Action dated Sep. 25, 2014 from Canadian Application No. 2,690,239. |
| 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). |
| Notice of Allowance dated Jan. 14, 2015 from U.S. Appl. No. 13/194,121. |
| Examination Report dated Aug. 17, 2015 from Australian Application No. 2014203614. |
| Office Action dated Aug. 21, 2015 from U.S. Appl. No. 14/577,353. |
| Newtin Remote Ticket Entry User's Manual, Illinois One-Call System, Jun. 12, 2007, 29 pages. |
| 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). |
| Responsive Expert Report of Dr. Randel Dymond, P.E. to the Expert Report of Mr. Ivan Zatkovich dated Sep. 30, 2014, filed Nov. 13, 2014; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| CertusView's Reply in Support of its Motion to Strike and in the Alternative Dismiss S&N'First Amended Answer and Counterclaims filed Mar. 2, 2015; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| CertusView's Request for Leave to File a Sur-Reply in Support of its Opposition to Defendants' Motion for Attorney's Fees filed Mar. 18, 2015; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Defendants' Response to CertusView's Motion to Strike and in the Alternative Dismiss S&N's First Amended Answer and Counterclaims filed Feb. 23, 2015; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Defendants' Response to CertusView's Objections to the Magistrate Judge's Order Allowing S&N's Amended Answer and Counterclaims filed Feb. 17, 2015; Case 2:13-cv-00346-MSD-TEM; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia) |
| Defendant's Response to CertusView's Objections to the Magistrate Judge's Order Awarding Sanctions on S&N's Motion to Compel filed Feb. 23, 2015; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| Opinion and Order to Plaintiff's Rule 72 Objections to the Magistrate Judge's Jan. 16, 2015 Order Granting Defendant's Leave to Amend their Answer and Counterclaims, and on Plaintiff's Motion to Strike and in the Alternative Dismiss S&N's First Amended Answer and Counterclaims, filed May 22, 2015; CertusView Technologies, LLC v. S&N Locating Services, LLC et al., (Eastern District of Virginia). |
| U.S. Appl. No. 14/612,603, filed Feb. 3, 2015, Nielsen et al. |
| U.S. Appl. No. 14/577,353, filed Dec. 19, 2014, Nielsen et al. |
| U.S. Appl. No. 14/194,718, filed Mar. 1, 2014, Nielsen et al. |
| U.S. Appl. No. 14/708,530, filed May 11, 2015, Nielsen et al. |
| Office Action dated May 12, 2015 from Canadian Application No. 2,690,239. |
| “KorTera C/S Positive Response” (KorTerra, Aug. 28, 2008), archived online: KorTerra-KorTerra Automated Positive Response for One Call Locate Tickets <https://web.archive.org/web/20080828014227/http://www.korterra.com/damage—prevention/KorTerraCS/KorTerra—Positive—Response.htm>, 2 pages. |
| “TelDig OnceCall” (TelDig Systems, Nov. 10, 2006), archived online: TelDig Systems-Products and Services <https://web.archive.org/web/20061110055008/http://www.teldig.com/en/Text/2003—OneCallWeb.pdf [TelDig One Call], 1 page. |
| TelDig Systems, Press Releases, “2001-2004 News” (Aug. 2, 2001-Jul. 5, 2004), archived online: TelDig Systems <https://web.archive.org/web/20061110055824/http://teldig.com/en/Text/2001-2004—News.doc> [TelDig Press Releases], 12 pages. |
| Office Action dated Jan. 12, 2015 from Canadian Application No. 2,690,239. |
| Nielsen et al., co-pending U.S. Pat. No. 8,907,978, issued Dec. 9, 2014. |
| Nielsen et al., co-pending U.S. Pat. No. 2014-0321717, published Oct. 30, 2014. |
| 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). |
| Notice of Filing of Defendant's 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). |
| First Action Interview Office Action dated Jun. 12, 2015 from U.S. Appl No. 14/612,603. |
| Office Action dated Jun. 18, 2015 from U.S. Appl. No. 12/703,322. |
| Office Action dated May 21, 2015 from U.S. Appl. No. 13/950,655. |
| Notice of Allowance dated Jun. 5, 2015 from U.S. Appl. No. 13/191,048. |
| Office Action dated May 15, 2015 from U.S. Appl. No. 14/194,718. |
| Notice of Allowance dated Jun. 4, 2015 from U.S. Appl. No. 13/190,185. |
| Notice of Allowance dated Jun. 19, 2015 from U.S. Appl. No. 13/194,121. |
| Office Action dated Jul. 15, 2015 from U.S. Appl. No. 13/185,194. |
| Notice of Allowance dated Jul. 7, 2015 from U.S. Appl. No. 14/612,603. |
| Potts, A., “ArcInfo Version 8: Introducing the Next Generation,” ArcUser Magazine (Apr.-Jun. 1999), 4 pages. |
| “Features and Functions of ArcInfo 8,” ESRI. Redlands, California, September. Sep. 1999, 18 pages. |
| Notice of Allowance dated Jul. 8, 2015 from U.S. Appl. No. 14/708,530. |
| ESRI Press Release. Redlands, California, Jan. 2000, 3 pages. |
| 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 Judgement 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). |
| Memoandum 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). |
| 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 fo 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 Attoneys' 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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 Attorney's 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). |
| Number | Date | Country | |
|---|---|---|---|
| 20140122149 A1 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61256007 | Oct 2009 | US | |
| 61151419 | Feb 2009 | US | |
| 61151425 | Feb 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12915516 | Oct 2010 | US |
| Child | 14063417 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12703313 | Feb 2010 | US |
| Child | 12915516 | US |
