Handheld field maintenance tool with improved diagnostics
Claim Score by NHIP
Abstract
A handheld field maintenance tool with improved diagnostic functions is provided. The tool includes a process communication module configured to interact with a field device. A controller is coupled to the process communication module. The controller is configured to execute a number of improved diagnostic functions relative to the field device. The controller may obtain contextual information relative to a current field maintenance operation and preload at least one resource relative to a next field operation step. The controller may obtain process alarm information through a wireless communication module, and field device alert information through the process communication module and provide an indication on a display relative to both process alarm information and field device alert information. The controller may execute a sequence of field device maintenance operations on the field device in response to a signal from a user input device. The controller may obtain snapshot information in response to a signal from a user input device.

Term
5.4 yearsleft in the term
Expires 18 February 2032, including 206 days of term adjustment.
- Priority
- Filed
- Granted
- Today
- Expires
24 claims: 5 independent, 19 dependent
- 1Broadest claimClaim Score 48, average(NHIP)A handheld field maintenance tool comprising:a wired process communication module configured to interact with a field device, wherein the wired process communication module is configured to be physically coupled to the field device to interact with the field device;a wireless communication protocol module configured to communicatively couple the handheld field maintenance tool to a remote source;a controller coupled to the wired process communication module and the wireless communication protocol module, the controller being configured to support a workflow mode, in which the controller is configured to: automatically obtain contextual information relative to an unknown current step in a field maintenance operation;identify the unknown current step being executed in the field maintenance operation based on the contextual information obtained;identify a subsequent step of the field maintenance operation, in a workflow currently being executed, based on the identification of the unknown current step;pre-load at least one resource based on the identified subsequent step;and present the user with subsequent step information through a display, wherein the subsequent step information is displayed after the identified current step is completed and comprises the at least one resource and the subsequent step of the field maintenance operation.
- 6A handheld field maintenance tool comprising:a wired process communication module configured to interact with a field device, wherein the wired process communication module is configured to be physically coupled to the field device to interact with the field device;a wireless communication protocol module configured to communicatively couple the handheld field maintenance tool to a remote source;a controller coupled to the wired process communication module and the wireless communication protocol module, the controller being configured to, upon entering a workflow mode of operation: automatically obtain contextual information relative to an unknown current step in a field maintenance operation from the field device, using the wired process communication module;identify the unknown current step of the field maintenance operation based on the contextual information obtained from the field device;identify a plurality of optional next steps based on the identification of the unknown current step in the field maintenance operation;organize the plurality of optional next steps based on a statistical weight ranking, wherein the plurality of optional next steps is organized based on a probability of occurrence after the identified current step of the field maintenance operation is completed;determine at least one resource related to a most likely next step of the organized plurality of optional next steps, wherein the at least one resource is configured to assist a technician with the most likely next step;obtain the at least one resource from the remote source using the wireless communication protocol module prior to the completion of the identified current step of the field maintenance operation;and present the organized plurality of optional next steps, the most likely next step and the at least one resource on a display after completion of the identified current step of the field maintenance operation.
- 9The handheld field maintenance tool of clam 6 , wherein the handheld field maintenance tool complies with an intrinsic safety specification.
- 10A method of facilitating a field maintenance operation using a handheld field maintenance tool, the method comprising:receiving a user input on the handheld field maintenance tool, wherein the user input indicates that the handheld field maintenance tool enter a workflow mode of operation, and upon entering the workflow mode of operation, performing the steps of: automatically obtaining contextual information from a field device, using a wired process communication module of the handheld field maintenance tool, wherein the contextual information comprises at least information regarding an unknown current step of the field maintenance operation;identifying the unknown current step of the field maintenance operation, using a controller of the handheld field maintenance tool, based on the contextual information received;identifying, based on the identified current step of the field maintenance operation, a likely next step of the field maintenance operation;obtaining a resource associated with the likely next step of the field maintenance operation from a remote source, using a wireless communication protocol module of the handheld field maintenance tool;presenting the likely next step and the resource on a display of the handheld field maintenance tool after completion of the identified current step of the field maintenance operation;and storing a set of results based on the completion of the identified current step.
- 16A method of facilitating a diagnostic task using a handheld field maintenance tool, the method comprising:receiving a user input on the handheld field maintenance tool, wherein the user input indicates that the handheld field maintenance tool enter a workflow mode of operation, and upon entering the workflow mode of operation, performing the steps of;automatically obtaining contextual information from a remote source, using a wireless communication module of the handheld field maintenance tool, wherein the contextual information comprises at least information regarding an unknown current step of the diagnostic task;identifying the unknown current step of the diagnostic task based on the contextual information received;identifying, based on the identified current step of the diagnostic task, a likely next step of the diagnostic task and an alternative likely next step;obtaining a resource associated with the likely next step of the diagnostic task from the remote source, using the wireless communication protocol module of the handheld field maintenance tool;presenting the likely next step and the resource on a display of the handheld field maintenance tool after completion of the identified current step of the diagnostic task;receiving an additional user input indicating that the likely next step and the resource are not relevant;and presenting the alternative likely next step on the display of the handheld field maintenance tool.
Independent claims5
40 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATION
The present application is based on and claims the benefit of U.S. provisional patent application Ser. No. 61/368,477, filed Jul. 28, 2010, the content of which is hereby incorporated by reference in its entirety.
BACKGROUND
Handheld field maintenance tools are known. Such tools are highly useful in the process control and measurement industry to allow operators to conveniently communicate with and/or interrogate field devices in a given process installation. Examples of such process installations include petroleum, pharmaceutical, chemical, pulp, and other fluid processing installations. In such installations, the process control and measurement network may include tens or even hundreds of various field devices which periodically require maintenance to ensure that such devices are functioning properly and/or calibrated. Moreover, when one or more errors in the process control and measurement installation are detected, the use of a handheld field maintenance tool allows a technician to quickly diagnose such errors in the field. Handheld field maintenance tools are generally used to configure, calibrate, and diagnose problems relative to intelligent field devices using digital process communication protocols.
Since at least some process installations may involve highly volatile, or even explosive, environments, it is often beneficial, or even required, for field devices and the handheld field maintenance tools used with such field devices to comply with intrinsic safety requirements. These requirements help ensure that compliant electrical devices will not generate a source of ignition even under fault conditions. One example of Intrinsic Safety requirements is set forth in: APPROVAL STANDARD INTRINSICALLY SAFE APPARATUS AND ASSOCIATED APPARATUS FOR USE IN CLASS I, II and III, DIVISION NUMBER 1 HAZARDOUS (CLASSIFIED) LOCATIONS, CLASS NUMBER 3610, promulgated by Factory Mutual Research October, 1998. An example of a handheld field maintenance tool that complies with intrinsic safety requirements includes that sold under trade designation Model 475 Field Communicator, available from Emerson Process Management of Austin, Tex.
SUMMARY
A handheld field maintenance tool with improved diagnostic functions is provided. The tool includes a process communication module configured to interact with a field device. A controller is coupled to the process communication module. The controller is configured to execute a number of improved diagnostic functions relative to the field device. The controller may obtain contextual information relative to a current field maintenance operation and preload at least one resource relative to a next field operation step. The controller may obtain process alarm information through a wireless communication module and field device alert information through the process communication module and provide an indication on a display relative to both process alarm information and field device alert information. The controller may execute a sequence of field device maintenance operations on the field device in response to a signal from a user input device. The controller may obtain snapshot information in response to a signal from a user input device.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idref="DRAWINGS">FIGS. 1A and 1B</figref> are diagrammatic views of a handheld field maintenance tool with which embodiments of the invention are particularly useful.
<figref idref="DRAWINGS">FIG. 2</figref> is a diagrammatic view of a handheld field maintenance tool with which embodiments of the present invention are particularly useful.
<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of a handheld field maintenance tool in accordance with an embodiment of the present invention.
<figref idref="DRAWINGS">FIG. 4</figref> is a diagrammatic view of a method of facilitating field maintenance with a handheld field maintenance tool in accordance with an embodiment of the present invention.
<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of a method of providing device alert and process alarm conditions on a handheld field maintenance tool in accordance with an embodiment of the present invention.
<figref idref="DRAWINGS">FIG. 6</figref> is a flow diagram of a method of simply executing complex, device-specific diagnostics using a handheld field maintenance tool in accordance with an embodiment of the present invention.
<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram of a method of providing diagnostic information to a remote party using a handheld field maintenance tool in accordance with an embodiment of the present invention.
<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram of a method of receiving remote support using a handheld field maintenance tool in accordance with an embodiment of the present invention.
DETAILED DESCRIPTION
<figref idref="DRAWINGS">FIGS. 1A and 1B</figref> are diagrammatic views of a handheld field maintenance tool <b>22</b> coupled to field devices <b>20</b>, <b>23</b>. As shown in <figref idref="DRAWINGS">FIG. 1A</figref>, handheld field maintenance tool <b>22</b> includes a pair of terminals <b>25</b>, <b>27</b> that couple to test leads <b>30</b>, <b>32</b>, respectively, which are then coupled to terminals <b>24</b> of field device <b>20</b>. Terminals <b>24</b> may be dedicated terminals to allow such a handheld field maintenance tool to couple to device <b>20</b> and interact with device <b>20</b>. The utilization of terminals <b>25</b>, <b>27</b> to couple to field device illustrates an example of a wired connection between handheld field maintenance tool <b>22</b> and field device <b>20</b>.
<figref idref="DRAWINGS">FIG. 1B</figref> shows an alternate arrangement where handheld field maintenance tool <b>22</b> couples directly to the process control loop <b>34</b> to which field device <b>23</b> is coupled. In either case, the wired connection between the handheld field maintenance tool and the field device allows the handheld field maintenance tool to interact with the desired field device <b>20</b>, <b>23</b>.
<figref idref="DRAWINGS">FIG. 2</figref> is a diagrammatic view of handheld field maintenance tool <b>102</b> interacting with wireless field device <b>104</b>. System <b>100</b> includes handheld field maintenance tool <b>102</b> communicating with field device <b>104</b>. Handheld field maintenance tool <b>102</b> is communicatively coupled to field device <b>104</b> via communication link <b>114</b>. Communication link <b>114</b> can take any suitable form including wired connections as shown in <figref idref="DRAWINGS">FIGS. 1A and 1B</figref>, as well as wireless communication techniques that are currently being used or being developed. Handheld field maintenance tool <b>102</b> allows a technician to interact with field device <b>104</b> to configure, calibrate, and/or diagnose problems with respect to field device <b>104</b> using a digital process communication protocol such as FOUNDATION™ Fieldbus and/or the HART® protocol. Handheld field maintenance tools, such as tool <b>102</b> can be used to save configuration data from field devices, such as field device <b>104</b>.
Field device <b>104</b> may be any device that senses a variable in the process and transmits information related to the variable over a process communication loop; such as a pressure or temperature. Field device <b>104</b> may also be a device that receives information from a process communication loop and sets a physical parameter, such as a valve closure, based on the information. Field device <b>104</b> is depicted as an industrial process fluid pressure transmitter having a pressure manifold <b>106</b> coupled thereto, and an electronics enclosure <b>108</b>. Field device <b>104</b> is provided for illustrative purposes only. In reality, field device <b>104</b> may be any industrial device, such as a process fluid temperature transmitter, process fluid level transmitter, process fluid flow transmitter, valve controller, or any other device that is useful in the measurement and/or control of industrial processes.
Handheld field maintenance tool <b>102</b> generally includes a user interface that comprises a display <b>120</b> as well as a number of user input buttons <b>122</b>. Display <b>120</b> may be any suitable display such as an active-matrix liquid crystal display, or any other suitable display that is able to provide useful information. Buttons <b>122</b> may comprise any suitable arrangement of buttons relative to any number of functions to which the handheld field maintenance tool may be directed. Buttons <b>122</b> may comprise a numeric keypad, an alphanumeric keypad, any suitable number of custom functions and/or navigation buttons, or any combination thereof.
<figref idref="DRAWINGS">FIG. 3</figref> is a diagrammatic system block diagram of a handheld field maintenance tool in accordance with the embodiment of the present invention. It is preferred that tool <b>52</b> comply with at least one intrinsic safety specification, such as that listed above, in order to help ensure safety in potentially explosive environments. Handheld field maintenance tool <b>52</b> preferably includes at least one wireless process communication module <b>121</b>. Suitable examples for wireless process communication module <b>121</b> include a module that generates and/or receives proper signals in accordance with a known wireless communication protocol, such as the known WirelessHART protocol (IEC 62591). Another wireless process communication protocol is set forth in ISA100.11a. While <figref idref="DRAWINGS">FIG. 3</figref> shows a single wireless process communication module <b>121</b>, it is expressly contemplated that any suitable number of wireless process communication modules can be used to communicate in accordance with various wireless process communication protocols now in existence or later developed.
Handheld field maintenance tool <b>52</b> also includes at least one secondary wireless communication protocol module <b>123</b>. Wireless communication protocol module <b>123</b> can communicate in accordance with one or more of the options shown in phantom in <figref idref="DRAWINGS">FIG. 3</figref>. Specifically, wireless communication protocol module <b>123</b> may communicate in accordance with a Bluetooth specification <b>124</b> (such as Bluetooth Specification 2.1 rated at Power Class 2); a Wi-Fi specification <b>126</b> (such as IEEE 802.11.a/b/g/n); a known RFID specification <b>128</b>; cellular communication techniques <b>130</b> (such as GSM/CDMA); WiMAX (IEEE 802.16m), and/or satellite communication <b>132</b>. These communication techniques and methodologies allow handheld field maintenance tool <b>52</b> to communicate directly with a wireless gateway or other suitable device either via direct wireless communication, or using the Internet. While one wireless communication protocol module <b>123</b> is shown in <figref idref="DRAWINGS">FIG. 3</figref>, any suitable number may be used. Each of the wireless process communication protocol module <b>121</b> and wireless communication protocol module <b>123</b> is coupled to controller <b>130</b> which is also coupled to the wired process communication module <b>138</b>.
Embodiments of the present invention generally leverage the wireless communication abilities of the handheld field maintenance tool to create a persistent, real-time data communication pathway or channel with the process installation network or cloud. Such access can be done using a direct wireless connection to the process installation network, or through a Virtual Private Network (VPN) tunnel into the process installation network through a process installation network firewall. This provides the ability for the handheld field maintenance tool to automatically interact and/or synchronize with systems within the process installation data network, such as an asset management system, a Computerized Maintenance Management System (CMMS), a Distributed Control System (DCS), et cetera. In some process installations, wireless communication may not be possible due to interference or the lack of a wireless access point within range of the handheld field maintenance tool. In such situations, the controller of the handheld field maintenance tool is preferably configured to store various data to be synchronized, such that when a suitable “hot spot” is found where wireless connectivity is available, the handheld field maintenance tool can connect and synchronize with suitable servers or other remote devices.
Controller <b>130</b> is preferably a microprocessor that executes a sequence of instructions stored therein, or in memory coupled to controller <b>130</b>, to perform handheld field maintenance tasks. Wired process communication module <b>138</b> allows handheld field maintenance tool <b>52</b> to be physically coupled via a wired connection at terminals <b>142</b>, <b>144</b> to a field device. Examples of suitable wired process communication include the highway addressable remote transducer (HART®) protocol, the FOUNDATION™ Fieldbus protocol, Profibus and others.
Handheld field maintenance tool <b>52</b> includes a user interface module <b>156</b> for generating a user interface using display <b>120</b> and keys <b>122</b>. Module <b>156</b> can include suitable display driver circuitry <b>158</b> and/or memory to interact with display <b>120</b>. Module <b>156</b> also includes input circuitry <b>160</b> which is configured to interact with buttons <b>122</b> to receive user input. Additionally, in embodiments where display <b>120</b> includes a touchscreen, module <b>160</b> can include circuitry to generate user input data to controller <b>130</b> based upon a user's touch and/or gestures received by the touchscreen.
Handheld field maintenance tool <b>52</b> can include a number of additional items that facilitate additional functionality. Specifically, tool <b>52</b> can include a position detection module, such as GPS module <b>150</b>. GPS module <b>150</b> can be configured to additionally use the Wide Area Augmentation System (WAAS) for improved accuracy and/or can be configured to operate using differential GPS techniques as appropriate. Module <b>150</b> is coupled to controller <b>130</b> to provide controller <b>130</b> with an indication of the geographic position of tool <b>52</b>. While position detection module <b>150</b> is preferably an internal component of tool <b>52</b>, it may be external and communicatively coupled thereto using a suitable wireless or wired communication protocol, such as Bluetooth <b>124</b>, RFID <b>128</b>, et cetera. Further still, while position detection module <b>150</b> is generally described as GPS module <b>150</b>, other techniques for triangulating the position of the handheld field maintenance tool based upon relative strength of wireless communication with wireless transceivers having known fixed positions can be employed. Examples of such wireless triangulation techniques include triangulation of the position of handheld field maintenance tool <b>52</b> based upon communication with three or more fixed-position WiFi communication points, or access points. Further still, as set forth above, embodiments of the present invention may include the ability to employ one or more wireless process communication protocol modules, such as module <b>121</b>. Such triangulation techniques can also be employed if a suitable number of wireless interactions with fixed-position wireless field devices can be achieved. Finally, while the various methods provided for obtaining the position of handheld field maintenance tool <b>52</b> are described above, they can also be used in conjunction with one another to provide additional accuracy and/or redundancy. Additionally, tool <b>52</b> also preferably comprises compass module <b>152</b> coupled to controller <b>130</b> such that tool <b>52</b> can indicate the compass direction in which it is pointing. Finally, tool <b>52</b> can also include tilt module <b>154</b> coupled to controller <b>130</b> to provide an indication to controller <b>130</b> relative to an angle of inclination of tool <b>52</b> relative to gravity. However, additional axes of sensing are also contemplated.
When one or more field devices are not functioning properly the entire process installation may be affected. It is thus very important for problems with such devices to be identified and remedied as quickly as possible. Moreover, with modern smart field devices growing more complex, finding a root cause of a specific problem is becoming more difficult.
In accordance with an embodiment of the present invention, a handheld field maintenance tool provides advanced diagnostic and troubleshooting functions for a field technician. Additionally, such advanced functionality is preferably provided using simplified user interface techniques such that the overall diagnostic task for the field technician is simplified while the actual diagnostics performed using the handheld field maintenance tool become more complex or advanced.
One manner in which field maintenance is simplified is by providing a handheld field maintenance tool that supports work flows. Field maintenance tasks are preferably grouped with applications and other information in a logical arrangement that is consistent with work flows used by technicians in the field. When in “workflow” mode, the handheld field maintenance tool senses, measures, or otherwise obtains, information about what the technician is currently doing, the next step(s) that the technician will likely take. With such information, the handheld field maintenance tool can make relevant information and applications readily accessible to the technician. Examples of such context information that can inform the handheld field maintenance tool about what the technician is currently doing includes, but is not limited to, digital interactions with a connected field device; errors or other diagnostic information provided by the field device; field device status information; field device audit trail information (preferably obtained wirelessly from an asset management system in real-time); asset history information (either stored locally in the handheld field maintenance tool or obtained wirelessly from a remote host); process parameters relative to the process installation, which are provided by one or more other field devices or the process controller; field device alert information (available from the connected field device or another field device); process alarm conditions; local environmental conditions (such as ambient temperature, barometric pressure, humidity, et cetera); measurement of electromagnetic interference using any of the wireless communication modules within the handheld field maintenance tool; vibration measurement; time of day; information relative to the technician (such as technician name or ID, technician security clearance, et cetera). Any such parameters, either alone or in combination with other parameters, can inform the handheld field maintenance tool about what the technician is currently doing. While the result of analyzing such information preferably indicates a specific tack for which next steps, information and/or application can be provided, it is expressly contemplated that a number of viable results can be determined with a statistical weight ranking the results. Thus, next step information, applications, et cetera can be provided for not only the top result, but even the top plurality of results. Moreover, while such diverse information is preferably automatically analyzed by the handheld field maintenance tool in order to assist the technician with the next logical step(s) in his or her field maintenance, it is also contemplated that all such information can also be made available to the technician.
<figref idref="DRAWINGS">FIG. 4</figref> is a diagrammatic view of a method of facilitating field maintenance with a handheld field maintenance tool in accordance with an embodiment of the present invention. Method <b>200</b> begins at block <b>202</b> where a handheld field maintenance tool is communicatively coupled to a field device. Such communicative coupling may be a wired coupling (either directly to the field device or through a process communication loop or segment) or a wireless coupling. Next, at block <b>204</b>, the handheld field maintenance tool is used to execute at least one field maintenance function relative to the field device. At block <b>206</b>, the handheld field maintenance tool acquires context information regarding the current field maintenance activity. This step is preferably done automatically without technician input. Based on the information obtained at step <b>206</b>, controller <b>130</b> in handheld field maintenance tool <b>52</b> determines what activity the technician is currently performing. Based on the current technician activity, controller <b>130</b> determines one or more next steps, and determines resources needed for the one or more next steps. The resources are loaded at block <b>208</b>, such that when the technician completes the current activity, the resource(s) required for the probable next step is/are already available. At block <b>210</b>, the most likely next step is indicated to the user through display <b>120</b>. The technician may select the indicated step, or may indicate that the proposed next step is not accepted. In such case, method <b>200</b> may provide the next most likely next step to the technician, or may simply allow the technician to end the context-sensitive resource pre-loading.
Embodiments of the present invention can also be used to facilitate documentation of the maintenance steps performed by the technician. For example, upon completion of each step performed, the results of that step may be stored in the handheld field maintenance tool, an asset management system, a CMMS system, et cetera to maintain a historical record of the work performed on a particular field device. Such information may include a description of the work done, whether the work was successful or not, a pass/fail rating, notes, et cetera. The handheld field maintenance tool preferably automates the acquisition of such information, but embodiments of the present invention also include receiving manual data entry from the technician on the handheld field maintenance tool relative to any of the information listed above. The results for individual maintenance steps are preferably aggregated to produce summary information about the whole procedure. This summary rating/information could include a check mark, or other suitable flag, for completion, a pass/fail rating, data, notes et cetera. The results are preferably stored on the handheld field maintenance tool and uploaded to an asset management system or higher level information system, et cetera for analysis and/or archival. The results could then be used by a maintenance manager to ensure that work had been completed as expected.
While embodiments of the present invention generally obtain and process significant amounts of diagnostic and/or contextual information, it is prefer that at least some embodiments of the present invention provide the technician with a simplified display that combines such data. This simplified indication may be provided on display <b>120</b> automatically, or may be selected or otherwise invoked by the technician. For example, one such simplified diagnostic indication is a simple good/bad indicator that provides a general indication of the health of the field device. It may be as simple as a good/bad flag or icon, or it may indicate a continuum between good and bad. Additionally, device-specific help information is also provided to the technician as desired. For example, the technician may select the “help” function or key, and the handheld field maintenance tool automatically generates a query to a remote host or system relative to the specific field device to which the handheld field maintenance tool is communicatively coupled. The query results are received wirelessly and displayed to the technician. Preferably, the help results are analyzed based on current field device context information, and more particular items of help information are offered to the technician based on the context information. Help results can include any information that is helpful to the technician drawn from any source, local or remote. Examples of help results include help information from a field device manual, a list of tasks (with links to the DD tasks) to perform based on the status, as well as one or more resources to “fix” the field device. Help results can also include links to videos where the technician is shown how to diagnose/troubleshoot/fix the field device. In embodiments where the handheld field maintenance tool has sufficient memory capacity, all device-specific help information may actually be stored locally. However, in such embodiments, it is still preferred that the help query results be ordered or organized based on the context information. Thus, if a technician is performing a specific calibration operation on a specific field device and presses the help button, the result will be device-specific help information, and the highest ranking result will be directed to the calibration operation the technician is currently performing.
One difficulty that faces technicians when they investigate, troubleshoot and diagnose problems in a running process is not having visibility to the field device alert and process alarm conditions simultaneously. In order to diagnose problems, the technician must generally be in constant contact with another worker inside the control room who is looking at the alarm banner on the operator screen.
<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of a method of providing device alert and process alarm conditions on a handheld field maintenance tool in accordance with an embodiment of the present invention. Method <b>250</b> begins at block <b>252</b> where the handheld field maintenance tool is communicatively coupled to the field device. Preferably, whenever the handheld field maintenance tool is communicatively coupled to a field device, the tool will automatically identify the field device and load, or otherwise obtain a device description for the connected field device. At block <b>254</b>, the field device is interrogated and one or more device alerts are obtained from the field device. Such alerts may indicate the occurrence of a specified event or condition that has occurred or is currently occurring. At block <b>256</b>, the handheld field maintenance tool communicates with a control room host or system that is currently running the process. Such communication is preferably wireless communication. The control room host or system provides information to the handheld field maintenance tool relative to one or more process alarms. A process alarm is an indication that a specified alarm condition has been satisfied and is not yet resolved. A process alarm can be related to a number of process conditions. For example, a process alarm can be related to a process variable, such as a process pressure, a field device failure or deterioration, process communication difficulties, et cetera. At block <b>258</b>, the handheld field maintenance tool generates an indication on display <b>120</b> that shows both device alerts and process alarms simultaneously. This provides the technician, in the field, with a display of process alarm conditions that the process operator sees, along with a summary of detected field device alerts. Using both displays, the technician in the field can quickly pinpoint the source of the problem and arrive at a diagnosis for resolution. While the description above is provided relative to process alarms and device alerts, any relevant process information from the process control system can be provided. Examples include process variables, analog output values, setpoints, et cetera.
<figref idref="DRAWINGS">FIG. 6</figref> is a flow diagram of a method of simply executing complex, device-specific diagnostics using a handheld field maintenance tool in accordance with an embodiment of the present invention. Method <b>270</b> begins at block <b>272</b> where a handheld field maintenance tool is communicatively coupled to a field device. At block <b>274</b>, the handheld field maintenance tool receives a technician input that selects the automatic diagnostic function. This selection may be generated in any suitable manner, however, it is preferred that the automatic diagnostic function be selectable with a single keypress. For example, a function-specific physical button may be included among buttons <b>122</b>. Additionally, once the handheld field maintenance tool is communicatively coupled to a field device, a soft-key may be available that allows the automatic diagnostic function to be invoked with the single keypress. The soft-key may be a physical button <b>122</b> in proximity to display <b>120</b>, such that display <b>120</b> may indicate a label proximate the soft-key that is indicative of the soft-key function.
At block <b>276</b>, the handheld field maintenance tool obtains a test scheme for the specific field device to which it was communicatively coupled in block <b>272</b>. Obtaining the test scheme can be done in any suitable manner, but is preferably done as indicated by the blocks in phantom. Specifically, the handheld field maintenance tool first identifies the field device to which it is coupled. This identification may include obtaining device tag information or some other identifier. The field device may also provide an indication of model number, manufacturer, device revision number, and device description revision number. In instances where the field device is not able to provide such information, the handheld field maintenance tool can preferably use its wireless communication to interact with an asset management system to obtain such information based on a lookup of the device tag. In any event, at block <b>280</b>, the handheld field maintenance tool accesses an electronic device description (EDD) file that corresponds with the exact field device manufacturer, model number and revision number that was obtained at block <b>278</b>. Such access may be performed using wireless communication, and/or may be performed using a local database lookup (in embodiments where the handheld field maintenance tool stores one or more EDD files). An electronic device descriptor (EDD) is written using electronic device description language (EDDL) and includes an exhaustive list of all tests that the specific field device needs to pass in order to be considered free of errors and defects. Field devices include or are provided with this information, but it is not easily usable by a technician. Thus, at block <b>282</b>, the handheld field maintenance tool causes controller to parse, or otherwise process, the EDD file to generate one or more automated test scripts that comprise a test scheme, as indicated at block <b>284</b>. While the description provided above specifically references EDD files, any computer-readable media that provides a description of an associated field device can be used in accordance with embodiments of the present invention. Suitable examples include Field Device Tool/Device Type Manager (FDT/DTM) in accordance with the FDT Specification managed by FDT Group AISBL, Field Device Integration (FDI), et cetera.
At block <b>286</b>, the handheld field maintenance tool begins automatically executing the test scheme. Preferably, the test scheme is executed without any technician intervention. However, it is contemplated that if certain tests or scripts require physical acts (such as connecting a reference resistance to a pair of field device sensor terminals). Even with technician intervention, the sequence of individual test scripts as well as communication with the field device is still preferably performed automatically. Once all test scripts in the scheme have run, the handheld field maintenance tool preferably provides a summary of the results to the technician, as indicated at block <b>290</b>. The summary preferably lists each test script, and a result of each script. Results can include an indication of whether the field device passed the test, failed the test, or whether the result was indeterminate. Moreover, the results summary can also include alert conditions and/or problems discovered. Preferably, the automatic diagnostic will also include as-found data that was recorded prior to running the test scheme. Additionally, if the field device does have problems or failures the final summary or report can provide one-click access to device-specific help relative to the specific problem(s) encountered and/or steps for the technician to correct or further investigate the problem. Moreover, the handheld field maintenance tool may also access a repair manual relative to the specific problem, such that the manual can be consulted directly on the handheld field maintenance tool. Field device manuals are typically available online in a standard format such as the known .pdf format. At block <b>292</b>, the results can also be delivered as required. Delivery can include printing a hardcopy (for example, printing via a Bluetooth printer), or emailing the results to an address specified by the technician.
Embodiments described above generally help the technician to perform a number of tasks or operations to ascertain a cause of a problem in a field device. However, sometimes, after all tests have been run, and information has been studied, the problem is still not identified. In such instances, embodiments of the present invention also facilitate interaction with a third-party support entity, such as the customer-support group of the field device's manufacturer.
<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram of a method of providing diagnostic information to a remote entity using a handheld field maintenance tool in accordance with an embodiment of the present invention. Method <b>300</b> beings at block <b>302</b> wherein a technician provides an input indicating a request for remote support. The user input may also be indicative of one particular remote support provider among a plurality of providers. For example, one provider may be an expert group located at the process installation, while another provider may be the manufacturer's customer support group. For each such provider, the handheld field maintenance tool preferably includes, or otherwise obtains, a pointer or indicator. One example of such an indicator is an email address. However, the pointer or indicator may also be a uniform resource locator (URL) of a secure ftp server that is configured to receive diagnostic information from handheld field maintenance tools. Moreover, embodiments of the present invention also contemplate the ability of the technician to select a plurality of providers.
At block <b>304</b>, the handheld field maintenance tool gathers snapshot information. As used herein, snapshot information includes any information relative to the field device, interaction with the field device, and/or contextual information. Snapshot information may include an actual photograph, video, and/or audio of the field device operating, or otherwise, in the field, as indicated at block <b>306</b>. Snapshot information may also include specific electrical measurements obtained or otherwise determined relative to the field device, as indicated at block <b>310</b>. The snapshot information may also include a copy of any or all communication between the handheld field maintenance tool and the field device, as indicated at block <b>312</b>. Snapshot information may also include a trace log to track the steps that were taken by the technician, as indicated at block <b>314</b>. Snapshot information may further include any suitable device information, such as device tag, model number, revision number, serial number, lot code, et cetera. Further still, snapshot information may include any of the context information listed above with respect to the embodiment that pre-loads resources based on what the technician is currently doing. While the description of method <b>300</b> provides a description of block <b>302</b> before block <b>304</b>, the order can, in fact, be reversed. Thus, a technician may gather snapshot information before requesting remote support. The acquisition of the snapshot information may happen automatically, where the system simply gathers the data in anticipation of the remote support request, or it could be technician-invoked.
At block <b>318</b>, the snapshot information is transmitted to the remote support provider. In embodiments where the handheld field maintenance tool has real-time wireless communication, the transmission may be done while the handheld field maintenance tool is still communicatively coupled to the field device. Additionally, or alternatively, the transmission may be stored until the handheld field maintenance tool has a wireless, or wired connection. Additionally, the snapshot information may also be transmitted to an asset management system for archival relative to the field device.
<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram of a method of receiving remote support using a handheld field maintenance tool in accordance with an embodiment of the present invention. Method <b>320</b> preferably executes after method <b>300</b> described above. However, this may not always be necessary. While it is probable, that snapshot information is very informative for the method of providing remote support, embodiments of the present invention can be practiced where a technician simply selects remote support relative to a specific field device and receives one or more test scripts or resources from the remote support provider. At block <b>322</b>, the handheld field maintenance tool establishes a communication connection with the selected remote support provider. At block <b>324</b>, the handheld field maintenance tool receives a test script <b>326</b> and/or a repair script <b>328</b>. As set forth above, the scripts received from the remote support provider are preferably in response, or after, the submission of a snapshot to the remote support provider as described with respect to <figref idref="DRAWINGS">FIG. 7</figref>. Next, at block <b>330</b>, the handheld field maintenance tool automatically executes one or more test/repairs scripts received from the remote support provider on the field device. At block <b>340</b>, the handheld field maintenance tool determines the results of the remote script execution. These results may be provided locally <b>342</b> on the display <b>120</b> of the handheld field maintenance tool, and/or remotely <b>344</b> to the remote support provider. Upon providing the results to the remote support provider, one or more additional test or repair scripts may be received thus returning control to block <b>324</b> via line <b>346</b>.
Although the present invention has been described with reference to particular embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.
Contents5
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both waysCites: the store holds 250 of 251
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11587005B2 | Cited by | United States of America | Search report |
| WO0135190A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO02086662A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| CN101763576A | Cites | China | Applicant |
| DE102007035158A1 | Cites | Germany | Applicant |
| DE102008029406A1 | Cites | Germany | Applicant |
| DE102009028195A1 | Cites | Germany | Applicant |
| DE10245176A1 | Cites | Germany | Applicant |
| EP1515208A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1916582A1 | Cites | European Patent Office (EPO) | Applicant |
| US2001047504A1 | Cites | United States of America | Applicant |
| JP2001337004A | Cites | Japan | Applicant |
| US2002004370A1 | Cites | United States of America | Applicant |
| US2002007237A1 | Cites | United States of America | Applicant |
| US2002027504A1 | Cites | United States of America | Applicant |
| US2002086642A1 | Cites | United States of America | Applicant |
| US2002167904A1 | Cites | United States of America | Applicant |
| US2002171558A1 | Cites | United States of America | Applicant |
| US2003050737A1 | Cites | United States of America | Applicant |
| US2003109937A1 | Cites | United States of America | Applicant |
| US2003200058A1 | Cites | United States of America | Search report |
| US2003204373A1 | Cites | United States of America | Applicant |
| US2003229472A1 | Cites | United States of America | Applicant |
| US2004039458A1 | Cites | United States of America | Applicant |
| US2004111238A1 | Cites | United States of America | Applicant |
| US2004193287A1 | Cites | United States of America | Applicant |
| US2004204193A1 | Cites | United States of America | Applicant |
| US2004228184A1 | Cites | United States of America | Applicant |
| US2004230327A1 | Cites | United States of America | Applicant |
| US2004234338A1 | Cites | United States of America | Search report |
| US2005010323A1 | Cites | United States of America | Search report |
| US2005114086A1 | Cites | United States of America | Applicant |
| US2005164684A1 | Cites | United States of America | Applicant |
| US2005180437A1 | Cites | United States of America | Search report |
| US2005210278A1 | Cites | United States of America | Search report |
| US2005222698A1 | Cites | United States of America | Applicant |
| US2005223120A1 | Cites | United States of America | Applicant |
| KR20060078883A | Cites | Republic of Korea | Applicant |
| US2006014533A1 | Cites | United States of America | Applicant |
| WO2006016845A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2006053211A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2006073464A1 | Cites | United States of America | Search report |
| US2006085108A1 | Cites | United States of America | Search report |
| US2006087402A1 | Cites | United States of America | Applicant |
| US2006095230A1 | Cites | United States of America | Search report |
| US2006155908A1 | Cites | United States of America | Applicant |
| US2006206277A1 | Cites | United States of America | Applicant |
| US2006290496A1 | Cites | United States of America | Applicant |
| US2006291438A1 | Cites | United States of America | Applicant |
| JP2007080194A | Cites | Japan | Applicant |
| JP2007091381A | Cites | Japan | Applicant |
| US2007161352A1 | Cites | United States of America | Applicant |
| US2007161371A1 | Cites | United States of America | Applicant |
| US2007179645A1 | Cites | United States of America | Applicant |
| US2007208279A1 | Cites | United States of America | Applicant |
| WO2008042074A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2008077358A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2008096216A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2008114911A1 | Cites | United States of America | Applicant |
| WO2008127632A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| JP2008165193A | Cites | Japan | Applicant |
| US2008234837A1 | Cites | United States of America | Applicant |
| US2008268784A1 | Cites | United States of America | Applicant |
| US2008275605A1 | Cites | United States of America | Search report |
| WO2009003146A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2009003148A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2009065578A1 | Cites | United States of America | Applicant |
| WO2009074544A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| JP2009086983A | Cites | Japan | Applicant |
| US2009094466A1 | Cites | United States of America | Applicant |
| US2009125713A1 | Cites | United States of America | Applicant |
| US2009171483A1 | Cites | United States of America | Applicant |
| US2009177970A1 | Cites | United States of America | Applicant |
| US2009248362A1 | Cites | United States of America | Search report |
| US2009271726A1 | Cites | United States of America | Applicant |
| US2009284390A1 | Cites | United States of America | Applicant |
| US2009296601A1 | Cites | United States of America | Applicant |
| US2009326852A1 | Cites | United States of America | Applicant |
| US2010061703A1 | Cites | United States of America | Search report |
| US2010100766A1 | Cites | United States of America | Applicant |
| US2010114347A1 | Cites | United States of America | Applicant |
| US2010114549A1 | Cites | United States of America | Applicant |
| US2010145476A1 | Cites | United States of America | Applicant |
| US2010220630A1 | Cites | United States of America | Applicant |
| US2010290084A1 | Cites | United States of America | Applicant |
| US2010290351A1 | Cites | United States of America | Applicant |
| US2010290359A1 | Cites | United States of America | Applicant |
| US2010293363A1 | Cites | United States of America | Applicant |
| US2011117529A1 | Cites | United States of America | Applicant |
| US2011238188A1 | Cites | United States of America | Applicant |
| US2012038548A1 | Cites | United States of America | Applicant |
| US2012038760A1 | Cites | United States of America | Applicant |
| US2012040316A1 | Cites | United States of America | Applicant |
| US2012040698A1 | Cites | United States of America | Applicant |
| US2012041744A1 | Cites | United States of America | Applicant |
| US2012046911A1 | Cites | United States of America | Applicant |
| US2013103353A1 | Cites | United States of America | Search report |
| EP2071427A2 | Cites | European Patent Office (EPO) | Applicant |
| EP2077473A1 | Cites | European Patent Office (EPO) | Applicant |
| EP2148259A1 | Cites | European Patent Office (EPO) | Applicant |
102 members in 10 offices
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 36847710 | United States of America | P | |
| 36847710 | United States of America | P | |
| 201113191644 | United States of America | A | |
| 61368477 | – | – | – |
| US20100368477P | – | – | – |
| US201113191644 | – | – | – |
Members102
| Document | Office | Kind | |
|---|---|---|---|
| CA2806242A1 | Canada | A1 | |
| CA2806244A1 | Canada | A1 | |
| CA2806560A1 | Canada | A1 | |
| CA2806564A1 | Canada | A1 | |
| CA2806722A1 | Canada | A1 | |
| CA2806946A1 | Canada | A1 | |
| CA2806949A1 | Canada | A1 | |
| WO2012016003A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012016004A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012016008A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012016010A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012016012A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012016013A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012016014A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2012038458A1 | United States of America | A1 | |
| US2012038548A1 | United States of America | A1 | |
| US2012038760A1 | United States of America | A1 | |
| US2012040316A1 | United States of America | A1 | |
| US2012040698A1 | United States of America | A1 | |
| US2012041744A1 | United States of America | A1 | |
| US2012046911A1 | United States of America | A1 | |
| CN102483618A | China | A | |
| WO2012016008A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2012016013A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN102804085A | China | A | |
| WO2012016003A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2012016012A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN102859452A | China | A | |
| WO2012016004A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN103069349A | China | A | |
| CN103119524A | China | A | |
| EP2598955A2 | European Patent Office (EPO) | A2 | |
| EP2598956A1 | European Patent Office (EPO) | A1 | |
| EP2598957A2 | European Patent Office (EPO) | A2 | |
| EP2598958A2 | European Patent Office (EPO) | A2 | |
| EP2598959A2 | European Patent Office (EPO) | A2 | |
| EP2598960A2 | European Patent Office (EPO) | A2 | |
| EP2598961A2 | European Patent Office (EPO) | A2 | |
| CN103210357A | China | A | |
| JP2013535739A | Japan | A | |
| JP2013535740A | Japan | A | |
| JP2013535741A | Japan | A | |
| JP2013535742A | Japan | A | |
| JP2013535743A | Japan | A | |
| WO2012016010A3 | World Intellectual Property Organization (WIPO) | A3 | |
| JP2013538394A | Japan | A | |
| CN103392155A | China | A | |
| JP2014500986A | Japan | A | |
| US8766794B2 | United States of America | B2 | |
| JP5588068B2 | Japan | B2 | |
| RU2013108780A | Russian Federation | A | |
| RU2013108799A | Russian Federation | A | |
| RU2013108819A | Russian Federation | A | |
| RU2013108821A | Russian Federation | A | |
| RU2013108826A | Russian Federation | A | |
| RU2013108860A | Russian Federation | A | |
| RU2013108906A | Russian Federation | A | |
| JP5620579B2 | Japan | B2 | |
| JP5636106B2 | Japan | B2 | |
| JP5636107B2 | Japan | B2 | |
| RU2553415C2 | Russian Federation | C2 | |
| RU2554528C2 | Russian Federation | C2 | |
| IN280CHN2013A | India | A | |
| IN286CHN2013A | India | A | |
| IN288CHN2013A | India | A | |
| RU2557468C2 | Russian Federation | C2 | |
| RU2560797C2 | Russian Federation | C2 | |
| CN103210357B | China | B | |
| RU2563775C2 | Russian Federation | C2 | |
| RU2564634C2 | Russian Federation | C2 | |
| CN105045175A | China | A | |
| CN103069349B | China | B | |
| US9201414B2 | United States of America | B2 | |
| CN103119524B | China | B | |
| JP5907964B2 | Japan | B2 | |
| CN102804085B | China | B | |
| JP5955841B2 | Japan | B2 | |
| CA2806949C | Canada | C | |
| CN103392155B | China | B | |
| RU2608242C1 | Russian Federation | C1 | |
| US2017146977A1 | United States of America | A1 | |
| US9703279B2 | United States of America | B2 | |
| US9709973B2This record | United States of America | B2 | |
| CA2806946C | Canada | C | |
| CN102859452B | China | B | |
| US9864357B2 | United States of America | B2 | |
| GB201720241D0 | United Kingdom | D0 | |
| CN105045175B | China | B | |
| JP6307273B2 | Japan | B2 | |
| GB2559464A | United Kingdom | A | |
| DE102017128904A1 | Germany | A1 | |
| JP2018124983A | Japan | A | |
| CN108388207A | China | A | |
| EP2598959B1 | European Patent Office (EPO) | B1 | |
| US10268180B2 | United States of America | B2 | |
| US10678213B2 | United States of America | B2 | |
| EP2598961B1 | European Patent Office (EPO) | B1 | |
| EP2598960B1 | European Patent Office (EPO) | B1 | |
| EP2598956B1 | European Patent Office (EPO) | B1 | |
| EP2598955B1 | European Patent Office (EPO) | B1 |
137 transactions on the USPTO file
Allowed after 5 non-final rejections, 4 final rejections and 4 RCEs.
- Non-final rejections
- 5
- Final rejections
- 4
- RCEs
- 4
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Printer Rush- No mailingTCPB | TCPB | |
| Printer Rush- No mailingTCPB | TCPB | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Certificate of correctionCC | CC | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 09709973
- Publication, DOCDB
- 9709973
- Publication, EPODOC
- US9709973
- Application
- 13191644
- Application, DOCDB
- 201113191644
- Application, EPODOC
- US201113191644
Titles
- English
- Handheld field maintenance tool with improved diagnostics
Patent term adjustment
- A delay
- +349 daysthe office missed an examination deadline
- B delay
- +24 dayspendency past three years
- Applicant delay
- −167 days
- Net adjustment
- 206 days
Classification
- CPC, 42
- G05B19/042
- G05B19/4185
- G05B19/0426
- G05B19/418
- G05B19/409
- G05B2219/31088
- G05B2219/23018
- G05B2219/23054
- G05B2219/23126
- G05B2219/23163
- G05B2219/23406
- G05B2219/23445
- G05B2219/23446
- G05B2219/24001
- G05B2219/24056
- G05B2219/25062
- G05B2219/25428
- G05B2219/31121
- G05B2219/31197
- G05B2219/31475
- G05B2219/32007
- G05B2219/32144
- G05B2219/32226
- G05B2219/33331
- G05B2219/35422
- G05B2219/35429
- G05B2219/36122
- G05B2219/36128
- Y02P90/14
- G06Q40/04
- G06Q10/06315
- G06Q30/0601
- G05B2219/24012
- G05B2219/24028
- Y02P90/02
- G05B15/02
- G05B19/4184
- G06Q20/204
- C07C29/1518
- Y04S10/50
- G05B19/4068
- G05B2219/50193
- IPC, 5
- G08B5 22
- G08B25 00
- G05B11 01
- G08C19 16
- G05B19 042
- USPC, 1
- 001001000