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.
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.
Field device 104 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 104 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 104 is depicted as an industrial process fluid pressure transmitter having a pressure manifold 106 coupled thereto, and an electronics enclosure 108. Field device 104 is provided for illustrative purposes only. In reality, field device 104 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 102 generally includes a user interface that comprises a display 120 as well as a number of user input buttons 122. Display 120 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 122 may comprise any suitable arrangement of buttons relative to any number of functions to which the handheld field maintenance tool may be directed. Buttons 122 may comprise a numeric keypad, an alphanumeric keypad, any suitable number of custom functions and/or navigation buttons, or any combination thereof.
Handheld field maintenance tool 52 also includes at least one secondary wireless communication protocol module 123. Wireless communication protocol module 123 can communicate in accordance with one or more of the options shown in phantom in
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 130 is preferably a microprocessor that executes a sequence of instructions stored therein, or in memory coupled to controller 130, to perform handheld field maintenance tasks. Wired process communication module 138 allows handheld field maintenance tool 52 to be physically coupled via a wired connection at terminals 142, 144 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 52 includes a user interface module 156 for generating a user interface using display 120 and keys 122. Module 156 can include suitable display driver circuitry 158 and/or memory to interact with display 120. Module 156 also includes input circuitry 160 which is configured to interact with buttons 122 to receive user input. Additionally, in embodiments where display 120 includes a touchscreen, module 160 can include circuitry to generate user input data to controller 130 based upon a user's touch and/or gestures received by the touchscreen.
Handheld field maintenance tool 52 can include a number of additional items that facilitate additional functionality. Specifically, tool 52 can include a position detection module, such as GPS module 150. GPS module 150 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 150 is coupled to controller 130 to provide controller 130 with an indication of the geographic position of tool 52. While position detection module 150 is preferably an internal component of tool 52, it may be external and communicatively coupled thereto using a suitable wireless or wired communication protocol, such as Bluetooth 124, RFID 128, et cetera. Further still, while position detection module 150 is generally described as GPS module 150, 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 52 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 121. 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 52 are described above, they can also be used in conjunction with one another to provide additional accuracy and/or redundancy. Additionally, tool 52 also preferably comprises compass module 152 coupled to controller 130 such that tool 52 can indicate the compass direction in which it is pointing. Finally, tool 52 can also include tilt module 154 coupled to controller 130 to provide an indication to controller 130 relative to an angle of inclination of tool 52 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.
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 120 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.
At block 276, the handheld field maintenance tool obtains a test scheme for the specific field device to which it was communicatively coupled in block 272. 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 280, 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 278. 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 282, 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 284. 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 286, 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 290. 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 292, 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.
At block 304, 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 306. Snapshot information may also include specific electrical measurements obtained or otherwise determined relative to the field device, as indicated at block 310. 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 312. Snapshot information may also include a trace log to track the steps that were taken by the technician, as indicated at block 314. 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 300 provides a description of block 302 before block 304, 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 318, 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.
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.
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.
Number | Name | Date | Kind |
---|---|---|---|
5195392 | Moore et al. | Mar 1993 | A |
5309351 | McCain et al. | May 1994 | A |
5442632 | Crowder et al. | Aug 1995 | A |
5650940 | Tonozuka et al. | Jul 1997 | A |
5903455 | Sharpe, Jr. et al. | May 1999 | A |
6033226 | Bullen | Mar 2000 | A |
6211649 | Matsuda | Apr 2001 | B1 |
6236223 | Brady et al. | May 2001 | B1 |
6377859 | Brown et al. | Apr 2002 | B1 |
6591201 | Hyde | Jul 2003 | B1 |
6633782 | Schleiss et al. | Oct 2003 | B1 |
6697894 | Mitchell | Feb 2004 | B1 |
6714846 | Trsar | Mar 2004 | B2 |
6725182 | Pagnano et al. | Apr 2004 | B2 |
6961586 | Barbosa | Nov 2005 | B2 |
6971063 | Rappaport et al. | Nov 2005 | B1 |
6975219 | Eryurek et al. | Dec 2005 | B2 |
7013184 | Romagnoli et al. | Mar 2006 | B2 |
7120391 | Stengele et al. | Oct 2006 | B2 |
7188200 | Griech | Mar 2007 | B2 |
7245271 | Nixon et al. | Jul 2007 | B2 |
7251534 | Walls et al. | Jul 2007 | B2 |
7308331 | Bjornson | Dec 2007 | B2 |
7337369 | Barthel et al. | Feb 2008 | B2 |
7400255 | Horch | Jul 2008 | B2 |
7402086 | Pomerantz | Jul 2008 | B2 |
7454252 | El-Sayed | Nov 2008 | B2 |
7505819 | El-Sayed | Mar 2009 | B2 |
7506812 | von Mueller et al. | Mar 2009 | B2 |
7675406 | Baier et al. | Mar 2010 | B2 |
7733833 | Kalika et al. | Jun 2010 | B2 |
7797061 | El-Sayed | Sep 2010 | B2 |
8000815 | John et al. | Aug 2011 | B2 |
8036007 | Woehrle | Oct 2011 | B2 |
8059101 | Westerman et al. | Nov 2011 | B2 |
8060862 | Eldridge et al. | Nov 2011 | B2 |
8060872 | Da Silva Neto | Nov 2011 | B2 |
8074172 | Kocienda et al. | Dec 2011 | B2 |
8086175 | Nakagawa | Dec 2011 | B2 |
8112669 | Zimmerman | Feb 2012 | B2 |
8126145 | Tewari et al. | Feb 2012 | B1 |
8150462 | Guenter et al. | Apr 2012 | B2 |
8180948 | Kreider et al. | May 2012 | B2 |
8214243 | Graham et al. | Jul 2012 | B2 |
8224256 | Citrano, III et al. | Jul 2012 | B2 |
8782539 | Bump et al. | Jul 2014 | B2 |
20010047504 | Aoyama | Nov 2001 | A1 |
20020004370 | Stengele et al. | Jan 2002 | A1 |
20020007237 | Phung et al. | Jan 2002 | A1 |
20020027504 | Davis et al. | Mar 2002 | A1 |
20020086642 | Ou et al. | Jul 2002 | A1 |
20020167904 | Borgeson et al. | Nov 2002 | A1 |
20020171558 | Bartelheim et al. | Nov 2002 | A1 |
20030050737 | Osann, Jr. | Mar 2003 | A1 |
20030109937 | Zielinski et al. | Jun 2003 | A1 |
20030200058 | Ogawa et al. | Oct 2003 | A1 |
20030204373 | Zielinski et al. | Oct 2003 | A1 |
20030229472 | Kantzes et al. | Dec 2003 | A1 |
20040039458 | Mathiowetz et al. | Feb 2004 | A1 |
20040111238 | Kantzes et al. | Jun 2004 | A1 |
20040193287 | Lefebvre et al. | Sep 2004 | A1 |
20040204193 | Li et al. | Oct 2004 | A1 |
20040228184 | Mathiowetz | Nov 2004 | A1 |
20040230327 | Opheim et al. | Nov 2004 | A1 |
20040234338 | Monroe et al. | Nov 2004 | A1 |
20050010323 | Cocciadiferro et al. | Jan 2005 | A1 |
20050114086 | Zielinski et al. | May 2005 | A1 |
20050164684 | Chen et al. | Jul 2005 | A1 |
20050180437 | Twomey | Aug 2005 | A1 |
20050210278 | Conklin | Sep 2005 | A1 |
20050222698 | Eryurek et al. | Oct 2005 | A1 |
20050223120 | Scharold et al. | Oct 2005 | A1 |
20060014533 | Warren | Jan 2006 | A1 |
20060073464 | Baldus et al. | Apr 2006 | A1 |
20060085108 | Grier | Apr 2006 | A1 |
20060087402 | Manning et al. | Apr 2006 | A1 |
20060095230 | Grier | May 2006 | A1 |
20060155908 | Rotvold et al. | Jul 2006 | A1 |
20060206277 | Horch | Sep 2006 | A1 |
20060290496 | Peeters | Dec 2006 | A1 |
20060291438 | Karschnia et al. | Dec 2006 | A1 |
20070161352 | Dobrowski et al. | Jul 2007 | A1 |
20070161371 | Dobrowski et al. | Jul 2007 | A1 |
20070179645 | Nixon et al. | Aug 2007 | A1 |
20070208279 | Panella et al. | Sep 2007 | A1 |
20080114911 | Schumacher | May 2008 | A1 |
20080234837 | Samudrala et al. | Sep 2008 | A1 |
20080268784 | Kantzes et al. | Oct 2008 | A1 |
20080275605 | Murphy et al. | Nov 2008 | A1 |
20090065578 | Peterson et al. | Mar 2009 | A1 |
20090094466 | Matthew et al. | Apr 2009 | A1 |
20090125713 | Karschnia et al. | May 2009 | A1 |
20090171483 | Scheuermann | Jul 2009 | A1 |
20090177970 | Jahl et al. | Jul 2009 | A1 |
20090248362 | Manegold et al. | Oct 2009 | A1 |
20090271726 | Gavimath et al. | Oct 2009 | A1 |
20090284390 | Lahner et al. | Nov 2009 | A1 |
20090296601 | Citrano et al. | Dec 2009 | A1 |
20090326852 | Vetter et al. | Dec 2009 | A1 |
20100061703 | Pham | Mar 2010 | A1 |
20100100766 | Bengtsson et al. | Apr 2010 | A1 |
20100114347 | Dheenathayalan et al. | May 2010 | A1 |
20100114549 | Kolavi | May 2010 | A1 |
20100145476 | Junk et al. | Jun 2010 | A1 |
20100220630 | Kalika et al. | Sep 2010 | A1 |
20100290084 | Russell, III et al. | Nov 2010 | A1 |
20100290351 | Toepke et al. | Nov 2010 | A1 |
20100290359 | Dewey et al. | Nov 2010 | A1 |
20100293363 | Meyer et al. | Nov 2010 | A1 |
20110117529 | Barash et al. | May 2011 | A1 |
20110238188 | Washiro | Sep 2011 | A1 |
20120038548 | Toepke et al. | Feb 2012 | A1 |
20120038760 | Kantzes et al. | Feb 2012 | A1 |
20120040316 | Mathiowetz et al. | Feb 2012 | A1 |
20120040698 | Ferguson et al. | Feb 2012 | A1 |
20120041744 | Kantzes et al. | Feb 2012 | A1 |
20120046911 | Mathiowetz et al. | Feb 2012 | A1 |
20130103353 | Kloppner | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
101763576 | Jun 2010 | CN |
10245176 | Apr 2004 | DE |
102007035158 | Jan 2009 | DE |
102008029406 | Dec 2009 | DE |
102009028195 | Feb 2011 | DE |
1515208 | Mar 2005 | EP |
1916582 | Apr 2008 | EP |
2071427 | Jun 2009 | EP |
2077473 | Jul 2009 | EP |
2148259 | Jan 2010 | EP |
2204705 | Jul 2010 | EP |
2382418 | May 2003 | GB |
2 394 124 | Apr 2004 | GB |
9051583 | Feb 1997 | JP |
2001337004 | Jul 2001 | JP |
2007080194 | Mar 2007 | JP |
2007-91381 | Apr 2007 | JP |
2008165193 | Jul 2008 | JP |
2009086983 | Apr 2009 | JP |
20060078883 | Jul 2006 | KR |
WO 0135190 | May 2001 | WO |
WO 02086662 | Oct 2002 | WO |
WO 2006016845 | Feb 2006 | WO |
W02006053211 | May 2006 | WO |
WO 2008042074 | Apr 2008 | WO |
WO 2008077358 | Jul 2008 | WO |
WO 2008096216 | Aug 2008 | WO |
WO 2008127632 | Oct 2008 | WO |
WO 2009003146 | Dec 2008 | WO |
WO 2009003148 | Dec 2008 | WO |
WO 2009074544 | Jun 2009 | WO |
Entry |
---|
Industrial Scientific, The Gas Detection People; Accessed Sep. 4, 2013; Copyright 1988, 1996, p. 5. |
Merriam Webster “Context” definition, accessed Jan. 30, 2013, screen capture Jan. 18, 2006. |
Merriam Webster “Snapshot” definition, accessed Jan. 30, 2013, screen capture Apr. 22, 2009. |
Invitation to Pay Additional Fees for international patent application No. PCT/US2010/034889 dated Sep. 15, 2010. |
ABB Limited: “Wireless Instrumentation Jargon Buster”. Information bulletin instrumentation ABB No. IB/INST-018, Mar. 3, 2009, XP002596601. Retrieved from the Internet: URL:http://www05.abb.com/global/scot/scot203.nsf/veritydisplay/be00ec76ef07e978c125756e003157b9/$File/IB—INST—018—1.pdf. |
Notification of Transmittal of the International Search Report and the Written Opinion from the International Application No. PCT/US2010/021764. |
David Gustafsson: “WirelessHART—Implementation and Evaluation on Wireless Sensors”. Masters's Degree Project, KTH University, Electrical Engineering, Apr. 1, 2009, pp. 1-39, XP002596602, Stockholm, Sweden. Retrieved from the Internet: URL:http://www.ee.kth.se/php/modules/publications/reports/2009/XR-EE-RT%202009:003.pdf. |
Notification of Transmittal of the International Search Report and the Written Opinion for the International application No. PCT/US2010/034848 dated Aug. 26, 2010. |
Possio Bluetooth to WLAN Gateway PX20: Full Product Description retrieved from http://www.blueunplugged.com/p.aspx?p=105816. |
1420 Wireless Gateway: Product Data Sheet 00813-0100-4420, Rev BA Mar. 2008. Emerson Process Management. |
Smart Wireless Gateway (WirelessHART™). Quick installation Guide 00825-0200-4420, Rev BA. Aug. 2009. Emerson Process Management. |
Rosemount 3051S Wireless Series Scalable Pressure, Flow, and Level Solutions. Reference Manual 00809-0100-4802, rev BA. Aug. 2007. Emerson Process Management. |
EPO Communication pursuant to Rules 161(1) and 162 EPC for European patent application No. 10701430.0 dated Aug. 30, 2011. |
Invitation to Pay Additional Fees for international patent application No. PCT/US2010/034949 dated Sep. 17, 2010. |
Technical Data Sheet: VIATOR® USB HART® Interface (Model 010031). MACTek Measurement and Control Technologies. |
VIATOR® Bluetooth® Wireless Technology Interface for use with HART field devices. MACTek Measurement and Control Technologies retrieved from www.mactekcorp.com/product5.htm. |
Product Data Sheet: VIATOR RS232. MACTek Measurement and Control Technologies retrieved from www.mactekcorp.com/product1.htm. |
Notification of Transmittal of the International Search Report and the Written Opinion from the International Application No. PCT/US2010/034889. |
Notification of Transmittal of the International Search Report and the Written Opinion from the International Application No. PCT/US2010/034949. |
EPO Communication from related European application No. 10730279.6 dated Jan. 13, 2012. |
EPO Communication from related European application No. 10730281.2 dated Jan. 13, 2012. |
EPO Communication from related European application No. 10725543.2 dated Jan. 12, 2012. |
Rosemount 3051SMV Quick Installation Guide 00825-0100-4803 Rev BA. Apr. 2011. |
Invitation to Pay Additional Fees from the International Application No. PCT/US2011/045673 dated Jan. 16, 2012. |
Notification of Transmittal of the International Search Report and the Written Opinion from the International Application No. PCT/US2011/045680 dated Jul. 6, 2012. |
Notification of Transmittal of the International Search Report and the Written Opinion from the International Application No. PCT/US2011/045681 dated Jan. 5, 2012. |
475 Field Communicator. User's Guide XP007919976. Aug. 2009. www.fieldcommunicator.com by Emerson Process Management. |
1420 Wireless Gateway. Reference Manual 00809-0100-4420. Rev BA. Aug. 2007. Emerson Process Management. |
Invitation to pay additional fees from the related international patent application No. PCT/US2011/045679 dated Aug. 6, 2012. |
Invitation to pay additional fees from the related International patent application No. PCT/US2011/045664 dated Aug. 9, 2012. |
Invitation to pay additional fees from the related International patent application No. PCT/US2011/045676 dated Jul. 30, 2012. |
First Communication from related European patent application No. 107392796 dated Oct. 19, 2012. |
Office Action from related Russian application No. 2011151063 dated Nov. 12, 2012. |
First Office Action from related Japanese application No. 2015511048, dated Jan. 29, 2013. |
Lee S W et al: “Honam Petrochemical Corporation Uses Simulator for Ethylene Plant Operator Training”, Processing of the Industrial Computing Conference. Houston, Oct. 18-23, 1992, pp. 219-222. |
Kurrle H-P et al.: “Trainingssimulator Aur Ausbildung Von Chemikanten und Anlagenfahrern. Otraining Simulator For the Training of Process Workers (Chemikanten) and Operators”, Automatisierungstechnische Praxis—ATP, Oldenbourg Indusrieverlag, Munchen, DE, vol. 36. No. 7. Jul. 1, 1994. Abstract. Section 2. |
Invitation to pay additional fees from the related international patent application No. PCT/US2011/045665 dated Aug. 23, 2012. |
Bushman J B: “Ally: An Operator's Associate for Cooperative Supervisory Control Systems”, IEEE Transactions on Systems, Man and Cybernetics, IEEE Inc. New York, US. vol. 23, No. 1, Jan. 1, 1993, pp. 111-128. |
First Communication for the related European patent application No. 107302812 dated Oct. 11, 2012. |
International Search Report and Written Opinion from the related International patent application No. PCT/US2011/045664 dated Nov. 6, 2012. |
International Search Report and Written Opinion from the related International patent application No. PCT/US2011/045679 dated Nov. 6, 2012. |
International Search Report and Written Opinion from the related International patent application No. PCT/US2011/045665 dated Nov. 6, 2012. |
First Communication from related European patent application No. 107255432 dated Oct. 11, 2012. |
First Office Action from related Japanese patent application No. 2013-521964, dispatched on Jan. 21, 2014. 9 pages. |
Notification on the results of patentability check from Russian counterpart application No. 2013108860, dated May 28, 2014. 9 pages. |
Office Action from Canadian patent application No. 2,806,242 dated Jul. 28, 2014. 6 pages. |
Office Action from Counterpart Chinese Patent Application No. 201180001614.6, issuing date: Dec. 25, 2014, 9 pages with English translation. |
Decision on Refusal to Grant a Patent for Invention for Russian Application No. 2013108860, dated Mar. 30, 2015, 15 pages with English Translation. |
Canadian patent application No. 2,806,242, from Oct. 7, 2015, 6 pages. |
Office Action for Chinese Patent Application No. 201510374161.1, dated Apr. 24, 2017, 9 pages including English translation. |
Number | Date | Country | |
---|---|---|---|
20120038458 A1 | Feb 2012 | US |
Number | Date | Country | |
---|---|---|---|
61368477 | Jul 2010 | US |