This patent relates generally to computer software, and more particularly, to computer software used in asset management systems to provide help information.
Process plants, like those used in chemical, petroleum or other processes, typically include one or more centralized or decentralized process controllers communicatively coupled to at least one host or operator workstation and to one or more process control and instrumentation devices, such as field devices, via analog, digital or combined analog/digital buses. Field devices, which may be, for example valves, valve positioners, switches, transmitters, and sensors (e.g., temperature, pressure and flow rate sensors), perform functions within the process such as opening or closing valves and measuring process parameters. While a typical process plant has many process control and instrumentation devices, such as valves, transmitters, sensors, etc. connected to one or more process controllers which execute software that controls these devices during the operation of the process, there are many other supporting devices which are also necessary for or related to process operation.
Still further, many process plants have other computers associated therewith which execute applications related to business functions or maintenance functions. Many process plants, and especially those which use smart field devices, use asset management applications to help monitor, track, and maintain the devices within the plant regardless of whether these devices are process control and instrumentation devices or are other types of devices. For example, an Asset Management Solutions (AMS) application sold by Fisher-Rosemount Systems, Inc. enables communication with and stores data pertaining to field devices to ascertain and track the operating state of various field devices. An example of such a system is disclosed in U.S. Pat. No. 5,960,214 entitled “Integrated Communication Network for use in a Field Device Management System.”
Maintenance personnel who are primarily responsible for ensuring that the actual equipment within the process is operating efficiently and for repairing and replacing malfunctioning equipment, use tools such as maintenance interfaces, the AMS application discussed above, and many other diagnostic tools which provide information about operating states of the devices within the process. To maintain information about various field devices in a process control system, the AMS application maintains a database of information about a number of devices. Generally, various devices used in a process control system can be expected to be manufactured by a number of different manufacturers. It is quite likely that not all of the devices communicate with each other or with the process control devices in the same manner. To overcome the problem of incompatibility among devices manufactured by different manufacturers, the process instrumentation industry uses a standardized digital device communications protocol as defined by a foundation such as the HART Foundation, or the Fieldbus Foundation in order to allow a single application to communicate with multiple device types. Typically, these foundations will have a standard that defines how each device identifies itself to a process control system using a standard communication protocol and a device description (DD), where the DD defines the protocol's application layer and various user interface definitions necessary to communicate with the device. Each device type would typically have its own DD, which is a formal description of the data and operating procedures for a field device, including variables, methods, commands, menus and display formats associated with the device. Information about every accessible variable of the device is included in the DD. Such variables include, for example, process measurements, any derived values, and all the internal parameters such as range, sensor type, choice of linearization, materials of construction, etc.
When the AMS application is implemented in a process plant that uses such a device, the maintenance personal responsible for maintaining up to date device related information may need to get help information about various parameters used to describe such a device. System designers using the AMS software, the 375 Communicator or the HART communicator may use a DD to gain further information about a device. As per the FOUNDATION Fieldbus' or the HART Communication Foundation's DD Language, all HART devices have the option to include DD help text to explain each parameter, method, etc., defined for a specific device. Such DD help text can be displayed on applications such as 275 HART Communicator, AMS, etc. However, not all device manufacturers provide DD help for all parameters, and if they do, this help information is generally not very descriptive. Moreover, DD help provided by a device manufacturer is limited to text information only, i.e., it does not include images, sound, etc.
The present patent is illustrated by way of examples and not limitations in the accompanying figures, in which like references indicate similar elements, and in which:
A system enables a user to get help information regarding a device description (DD) in a number of different formats. In a preferred embodiment, a system providing help information in a DDHelp format also allows a user to receive help information in alternate formats, such as WinHelp format, etc. In this embodiment, a system using the DDHelp format provides a user with an option to get help information in an alternate format. The user can select this option by clicking or selecting a button provided with the help information displayed in DDHelp format. When a user selects such a button, the system searches various alternate formats available for providing help information. If an alternate format of providing help information is found, an alternate method of providing help information using such an alternate format is activated. Help information provided by such an alternate format may also include multimedia content, such as images, audio and video.
Generally, computers using any of the Microsoft Windows® family of operating systems have an executable file named Winhelp.exe as a part of such an operating system. Winhelp.exe allows an application running on such a computer to display help information to a user in a WinHelp format. Software applications, such as AMS, use another file named DDHelp.exe to provide help information in a DD format. Enabling a software application using DDHelp.exe to provide help information to a user with Winhelp.exe thereby allows that application to provide help information to a user in more than one format. Moreover, allowing the WinHelp.exe to be executed from a template provided by the DDHelp.exe allows a user to easily access help information in more than one format from a single location.
Referring now specifically to the accompanying drawings,
A block 126 causes the help program 120 to determine if there is a WinHelp file available within the computer 100 for a device relating to the device information template presented by the block 122. If such a WinHelp file is available, a block 128 determines if the parameter selected by the user at the block 124 has a WinHelp topic defined within the computer 100. If no WinHelp topic is defined for such a parameter, a block 130, displays help information in a DDHelp format by presenting a DDHelp window. Typically, the help program 120 may use a DDHelp.exe file, which may be available on the computer 100, to display the help information in the DDHelp format. However, DDHelp is optional, i.e., various parameters, variables and methods within a DD may or may not have an associated DDHelp.
After the block 120 displays the help information in DDHelp format, a block 132 waits for a further input from the user. If the user clicks a mouse or a key on a keyboard attached to the computer 100 to provide such an input, a block 136 closes the DDHelp window.
If, at the block 128, the help program 120 determines that the parameter selected by the user at the block 124 has a WinHelp topic defined within the computer 100, a block 140 displays help information in a DDHelp format, where such help information includes a “More” button. Subsequently, a block 142 waits for an input from the user. When a block 144 determines that the user has clicked on the appropriate mouse button or a key on the keyboard attached to the computer 100, a block 146 determines whether the user selected the “More” button. If the block 146 determines that the user has selected the “More” button, a block 148, displays a help information template in the WinHelp format. If not, the block 136 closes the DDHelp window.
A block 151 presents a user with a device information template displaying information about various parameters of a device. An example of such a device information template is illustrated in
A block 153 causes the help program 150 to present a user with a help format selection template 154 that allows the user to select a format used to display the help information. An example of such a help format selection template 154 is illustrated in
A block 156 causes the help program 150 to determine if the help information is available within the computer 100 in a format selected by the user. If the help information is available in the format selected by the user, a block 157 displays help information in a format selected by the user.
If, at the block 156, the help program 150 determines that the help information is not available within the computer 100 in a format selected by the user, the help program 150 returns to block 153 and presents the help format-selection template 154 to the user.
The network computer 304 may be a server computer of the type commonly employed in networking solutions and may be used to accumulate, analyze, and download data provided by each of the computing facilities 302. For example, the network computer 304 may periodically receive data from each of the computing facilities 302 indicative of information pertaining to various parameters of various devices, various types of help information available for each of these devices, etc. The computing facilities 302 may include one or more facility servers 308 that may be utilized to store help information about a plurality of devices, device parameters, etc., associated with each facility. Moreover, such information may be stored in different formats, such as in audio information files, video information files, etc.
Although the data network 300 is shown to include one network computer 304 and three computing facilities 302, it should be understood that different numbers of computers 304 and computing facilities 302 may be utilized. For example, the network 306 may include a plurality of network computers 304 and dozens of computing facilities 302, all of which may be interconnected via the network 306. Such a configuration may provide several advantages, such as, for example, enabling near real time uploads and downloads of help information as well as periodic uploads and downloads of help information.
The controller 402 may include a program memory 408, a microcontroller or a microprocessor (MP) 410, a random-access memory (RAM) 412, and an input/output (I/O) circuit 414, all of which may be interconnected via an address/data bus 416. It should be appreciated that although only one microprocessor 410 is shown, the controller 402 may include multiple microprocessors 410. Similarly, the controller 402 may include multiple RAMs 412 and multiple program memories 408. Although the I/O circuit 414 is shown as a single block, it should be appreciated that the I/O circuit 414 may include a number of different types of I/O circuits. The RAM(s) 412 and programs memories 408 may be implemented as semiconductor memories, magnetically readable memories, and/or optically readable memories, for example. The controller 402 may also be operatively connected to the network 306 via a communication link 418.
If desired, the help program 120 may be implemented in the program memory 408 and adapted to operate on the microprocessor 410. In yet another embodiment, the help information such as that displayed on the templates 170, 180 and 190 of
Similar to the controller 402 of
The client device terminals 504 may include a display 518, a controller 520 and a keyboard 522 as well as a variety of other input/output devices (not shown) such as a printer, a mouse, a touch screen, a track pad, a track ball, an isopoint, a voice recognition system, etc. Each client device terminal 504 may be signed onto and occupied by a computing employee to assist them in performing their duties. Computing employees may sign onto a client device terminal 504 using any generically available technique, such as entering a user name and password. If a computing employee is required to sign onto a client device terminal 504, this information may be passed via the link 506 to the facility server 308, so that the controller 502 will be able to identify which computing employees are signed onto the system and which client device terminals 504 the employees are signed onto.
Typically, the facility servers 308 store a plurality of files, programs, and other data for use by the client device terminals 504 and the network computer 304. One facility server 308 may handle requests for data from a large number of client device terminals 504. Accordingly, each facility server 308 may include a high end computer with a large storage capacity, one or more fast microprocessors, and one or more high speed network connections. Conversely, relative to a typical facility server 308, each client device terminal 504 may include less storage capacity, a single microprocessor, and a single network connection.
If desired, the help information to be displayed using one or more of the templates 170, 180, 190, etc. may be stored in the program memory 508. Likewise the help program 120 may be stopped in part or in full on the RAM(s) 512 of the computing facilities 302, and one or more of the help information templates 140, 160, 180, etc., may be presented to a user on one or more of the client device terminals 504. Moreover, whereas the help program 120 illustrated by the examples above provides help information in WinHelp and DDHelp formats, in an alternate embodiment, the help program 120 may also provide help information in other help formats in addition to or instead of WinHelp and DDHelp formats.
Although the forgoing text sets forth a detailed description of numerous different embodiments of the invention, it should be understood that the legal scope of the invention is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment of the invention because describing every possible embodiment would be impractical, if not impossible. Numerous alternative embodiments could be implemented, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims defining the invention.
Thus, many modifications and variations may be made in the techniques and structures described and illustrated herein without departing from the spirit and scope of the present invention. Accordingly, it should be understood that the methods and apparatus described herein are illustrative only and are not limiting upon the scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
4527271 | Hallee et al. | Jul 1985 | A |
4607325 | Horn | Aug 1986 | A |
4657179 | Aggers et al. | Apr 1987 | A |
4734873 | Malloy et al. | Mar 1988 | A |
4763243 | Barlow et al. | Aug 1988 | A |
4764862 | Barlow et al. | Aug 1988 | A |
4885694 | Pray et al. | Dec 1989 | A |
4899276 | Stadler | Feb 1990 | A |
4907167 | Skeirik | Mar 1990 | A |
4910691 | Skeirik | Mar 1990 | A |
4944035 | Aagardl et al. | Jul 1990 | A |
4956793 | Bonne et al. | Sep 1990 | A |
4965742 | Skeirik | Oct 1990 | A |
5006992 | Skeirik | Apr 1991 | A |
5008810 | Kessel et al. | Apr 1991 | A |
5015934 | Holley et al. | May 1991 | A |
5018215 | Nasr et al. | May 1991 | A |
5043863 | Bristol et al. | Aug 1991 | A |
5050095 | Samad | Sep 1991 | A |
5070458 | Gilmore et al. | Dec 1991 | A |
5121467 | Skeirik | Jun 1992 | A |
5134574 | Beaverstock et al. | Jul 1992 | A |
5140530 | Guha et al. | Aug 1992 | A |
5142612 | Skeirik | Aug 1992 | A |
5161013 | Rylander et al. | Nov 1992 | A |
5167009 | Skeirik | Nov 1992 | A |
5187674 | Bonne | Feb 1993 | A |
5193143 | Kaemmerer et al. | Mar 1993 | A |
5197114 | Skeirik | Mar 1993 | A |
5212765 | Skeirik | May 1993 | A |
5224203 | Skeirik | Jun 1993 | A |
5282261 | Skeirik | Jan 1994 | A |
5291190 | Scarola et al. | Mar 1994 | A |
5301101 | MacArthur et al. | Apr 1994 | A |
5311447 | Bonne | May 1994 | A |
5333298 | Bland et al. | Jul 1994 | A |
5351184 | Lu et al. | Sep 1994 | A |
5353207 | Keeler et al. | Oct 1994 | A |
5369599 | Sadjadi et al. | Nov 1994 | A |
5373452 | Guha | Dec 1994 | A |
5384698 | Jelinek | Jan 1995 | A |
5390326 | Shah | Feb 1995 | A |
5396415 | Konar et al. | Mar 1995 | A |
5398303 | Tanaka | Mar 1995 | A |
5408406 | Mathur et al. | Apr 1995 | A |
5442544 | Jelinek | Aug 1995 | A |
5486920 | Killpatrick et al. | Jan 1996 | A |
5486996 | Samad et al. | Jan 1996 | A |
5488697 | Kaemmerer et al. | Jan 1996 | A |
5537310 | Tanake et al. | Jul 1996 | A |
5541833 | Bristol et al. | Jul 1996 | A |
5546301 | Agrawal et al. | Aug 1996 | A |
5559690 | Keeler et al. | Sep 1996 | A |
5561599 | Lu | Oct 1996 | A |
5566065 | Hansen et al. | Oct 1996 | A |
5570282 | Hansen et al. | Oct 1996 | A |
5572420 | Lu | Nov 1996 | A |
5574638 | Lu | Nov 1996 | A |
5596704 | Geddes et al. | Jan 1997 | A |
5640491 | Bhat et al. | Jun 1997 | A |
5666297 | Britt et al. | Sep 1997 | A |
5687090 | Chen et al. | Nov 1997 | A |
5692158 | Degeneff et al. | Nov 1997 | A |
5704011 | Hansen et al. | Dec 1997 | A |
5715158 | Chen | Feb 1998 | A |
5729661 | Keeler et al. | Mar 1998 | A |
5740324 | Mathur et al. | Apr 1998 | A |
5742513 | Bouhenguel et al. | Apr 1998 | A |
5761518 | Boehling et al. | Jun 1998 | A |
5777872 | He | Jul 1998 | A |
5781432 | Keeler et al. | Jul 1998 | A |
5790898 | Kishima et al. | Aug 1998 | A |
5796609 | Tao et al. | Aug 1998 | A |
5798939 | Ochoa et al. | Aug 1998 | A |
5809490 | Guiver et al. | Sep 1998 | A |
5819050 | Boehling et al. | Oct 1998 | A |
5819232 | Shipman | Oct 1998 | A |
5825645 | Konar et al. | Oct 1998 | A |
5826249 | Skeirik | Oct 1998 | A |
5842189 | Keeler et al. | Nov 1998 | A |
5847952 | Samad | Dec 1998 | A |
5859773 | Keeler et al. | Jan 1999 | A |
5877954 | Klimasauskas et al. | Mar 1999 | A |
5892679 | He | Apr 1999 | A |
5892939 | Call et al. | Apr 1999 | A |
5898869 | Anderson | Apr 1999 | A |
5901058 | Steinman et al. | May 1999 | A |
5905989 | Biggs | May 1999 | A |
5907701 | Hanson | May 1999 | A |
5909370 | Lynch | Jun 1999 | A |
5909541 | Sampson et al. | Jun 1999 | A |
5909586 | Anderson | Jun 1999 | A |
5917840 | Cheney et al. | Jun 1999 | A |
5918233 | La Chance et al. | Jun 1999 | A |
5924086 | Mathur et al. | Jul 1999 | A |
5940290 | Dixon | Aug 1999 | A |
5948101 | David et al. | Sep 1999 | A |
5949417 | Calder | Sep 1999 | A |
5960214 | Sharpe, Jr. et al. | Sep 1999 | A |
5960441 | Bland et al. | Sep 1999 | A |
5971581 | Gretta et al. | Oct 1999 | A |
5984502 | Calder | Nov 1999 | A |
5988847 | McLaughlin et al. | Nov 1999 | A |
6008985 | Lake et al. | Dec 1999 | A |
6033257 | Lake et al. | Mar 2000 | A |
6041263 | Boston et al. | Mar 2000 | A |
6047221 | Piche et al. | Apr 2000 | A |
6055483 | Lu | Apr 2000 | A |
6067505 | Bonoyer et al. | May 2000 | A |
6076124 | Korowitz et al. | Jun 2000 | A |
6078843 | Shavit | Jun 2000 | A |
6093211 | Hamielec et al. | Jul 2000 | A |
6106785 | Havlena et al. | Aug 2000 | A |
6108616 | Borchers et al. | Aug 2000 | A |
6110214 | Klimasaukas | Aug 2000 | A |
6122555 | Lu | Sep 2000 | A |
6128279 | O'Neil et al. | Oct 2000 | A |
6188402 | Csipkes et al. | Feb 2001 | B1 |
6297822 | Feldman | Oct 2001 | B1 |
6421571 | Spriggs et al. | Jul 2002 | B1 |
6477531 | Sullivan et al. | Nov 2002 | B1 |
6788313 | Heil | Sep 2004 | B1 |
6799198 | Huboi et al. | Sep 2004 | B1 |
6999990 | Sullivan et al. | Feb 2006 | B1 |
20020022894 | Eryurek et al. | Feb 2002 | A1 |
20040139073 | Bauchot et al. | Jul 2004 | A1 |
20040186927 | Eryurek et al. | Sep 2004 | A1 |
20060080607 | Cohen et al. | Apr 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20040255057 A1 | Dec 2004 | US |