Patent Application
20140130874
This disclosure relates generally to control systems and, more particularly, to a method and apparatus for validating the operability and availability of a field device within a control system.
Control systems, which include process control systems and safety instrumented systems (SIS), typically include one or more controllers to control the process or safety system. The controllers in these systems frequently use field devices to perform a variety of functions within the control environment. For example, in a liquid level control system, the field devices may be used to monitor and/or control the amount of a liquid in a holding tank. When the level of the liquid has reached a predetermined position (high or low), the control system may respond by utilizing one of the field devices, such as a valve, to adjust the flow of liquid entering or exiting the holding tank.
Proper maintenance of the process control system or the SIS of a process plant may include monitoring the operation of the field devices, testing the field devices, and repairing or replacing the field devices. An important concern for control personnel managing a control system is knowing whether the field devices being used are available and operational. In a level control system implementing a high-level detection application, the field device is commonly considered to be operating in a “dry” state or condition because the field device is not tripped or actuated until the level of the liquid rises to reach a high-level target or limit. The field device may therefore appear idle or static during the time the liquid level remains below the high-level target. If a movable portion of the field device is stationary or idle for an extended period of time, there is a concern that the field device will not function or may otherwise be inhibited from operating properly when the liquid does reach the high-level target. Control personnel may therefore prefer to periodically validate that the level detecting field device is operational and available.
Commonly utilized techniques to validate the operability and/or availability of a level detecting field device generally require control personnel to visit the site of the control system to replicate a rise or fall of the liquid level or simulate a level detection by the field device. One known validation technique involves changing the liquid level to engage or trip the level detecting field device and confirm that the field device is operational. However, changing the liquid level may require an extensive amount of time to raise or lower the liquid to the target level so that the field device can be tripped. Another known validation technique requires control personnel to manually manipulate the field device to simulate the tripping of the field device. However, manually manipulating the field device may not be possible with some level controllers, such as electronic devices, which are not mechanical in nature.
Example systems and methods to validate the availability and/or operability of a field device within a control plant are herein described. In accordance with a first exemplary aspect of a control system for controlling a process, the control system includes a field device coupled to the process and arranged to control a process condition. A sensor is coupled to the process and arranged to monitor the process for an occurrence of an event trigger associated with the process condition. A controller includes a processor for controlling the field device and the controller is operatively coupled to the field device. A memory is coupled to the controller and a diagnostic module is stored on the memory and coupled to the processor. The diagnostic module is capable of being executed on the processor to move the field device and simulate the occurrence of the event trigger.
In accordance with a second exemplary aspect, a control system having a holding tank for one or more liquids includes a displacer responsive to the liquid within the holding tank. An actuator is operatively coupled to the displacer and a processor is coupled to the actuator and capable of moving the displacer. A sensor includes an input and an output, wherein the input of the sensor is operatively coupled to the displacer for receiving an input signal representative of a characteristic of the displacer or an operating environment, and the output of the sensor is operatively coupled to the controller for providing an output signal associated with the input signal. An output device and a memory are coupled to the processor. An actuating module is stored on the memory, which when executed on the processor, actuates the actuator, and an exhibiting module is stored on the memory, which when executed on the processor, exhibits the output signal of the sensor on the output device.
In accordance with a third exemplary aspect, a level control system includes a movable assembly including a bar having a proximate end and a distal end. A displacer is attached to the distal end of the bar and an actuator is operatively connected to the movable assembly. A processor is coupled to the actuator and is capable of moving the displacer via the movable assembly. A sensor includes an input and an output, wherein the input of the sensor is operatively coupled to the movable assembly for receiving an input signal representative of one or more characteristics of the displacer or an operating environment, and the output of the sensor is operatively coupled to the processor for providing an output signal associated with the input signal. An output device and a memory are coupled to the processor. An actuating module is stored on the memory, which when executed on the processor, actuates the actuator, and an exhibiting module is stored on the memory, which when executed on the processor, exhibits the output signal of the sensor on the output device.
In accordance with a fourth exemplary aspect, a method is provided for validating a level control system having a controller coupled to an actuator and a movable assembly, a displacer connected to the movable assembly, and a sensor for measuring a physical quantity representative of a characteristic of the displacer or the displacer's operating environment coupled between the movable assembly and the controller. The method includes actuating the actuator to move the movable assembly and receiving an input signal representative of a characteristic of the displacer or the displacer's operating environment. The method includes receiving an output from a sensor coupled to the movable assembly, and exhibiting a state of the displacer.
In further accordance with any one or more of the foregoing first, second, third, or fourth aspects, a control system and/or method may further include any one or more of the following preferred forms.
In one preferred form, the output signal of the sensor includes a discrete value representative of the characteristic of the displacer or the operating environment. The discrete value may indicate a first state corresponding to the displacer positioned below a predetermined level or a second state corresponding to the displacer positioned at or above the predetermined level.
In another preferred form, the output signal of the sensor includes a continuous value representative of the characteristic of the displacer or the operating environment.
In another preferred form, an analyzing module and at least one previous output signal of the sensor are stored on the memory. The analyzing module, which when executed on the processor, compares the output signal of the sensor to the at least one previous output signal of the sensor.
In another preferred form, the sensor includes an input and an output, wherein the input of the sensor is operatively coupled to the field device for receiving an input signal representative of a characteristic of the field device or an operating environment, and the output of the sensor is operatively coupled to the controller for providing an output signal associated with the input signal.
In another preferred form, the control system includes a movable assembly including a bar, a displacer attached to a distal end of the bar, and an actuator coupled to the processor, which is capable of moving the displacer via the movable assembly.
In another preferred form, the control system includes an actuating module stored on the memory, which when executed on the processor, actuates the actuator.
In another preferred form, the control system includes an output device coupled to the controller and/or processor, and an exhibiting module stored on the memory, which when executed on the processor, exhibits the output signal on an output device.
In another preferred form, the characteristic of the displacer or the operating environment includes at least one of the following: level position of the displacer, weight of the displacer, mass of the displacer, density of a liquid, buoyancy of the liquid, and viscosity of the liquid.
In another preferred form, the output signal of the sensor is visually and/or audibly exhibited on the output device.
In another preferred form, the actuator includes a solenoid.
In another preferred form, the sensor includes a switch and/or Hall effect sensor.
In another preferred form, a zero spring is attached to the proximate end of the bar.
In a preferred method form, exhibiting the state of the displacer includes visually and/or audibly exhibiting the state of the displacer.
In another preferred method form, the steps may include storing the output from a sensor on a memory.
In another preferred method form, the steps may include comparing the output from a sensor to a previous output from the sensor stored on and retrieved from a memory device.
In another preferred method form, the steps may include sending an alert in response to the output received from a sensor.
In another preferred method form, the steps may include sending an alert in response to a comparison of an output from a sensor to a previous output from the sensor.
In
The process plant 10 also includes one or more host workstations 17 or computing devices, which may be any type of computer, for example. Each workstation 17 may include a processor 18, memory device 19, and/or a user interface 20 such as a display monitor and/or keyboard that are accessible by control personnel. In the example process plant 10 illustrated in
The process plant 10 includes both process control system devices and safety system devices operatively connected together via the bus structure that may be provided on a common backplane 24 into which different process controllers and input/output devices are attached. The process plant 10 illustrated in
The process controller 26, which may be, by way of example only, a DeltaV™ controller sold by Emerson Process Management or any other desired type of process controller, is programmed to provide process control functionality using the I/O devices 30, 32, 34 and the field devices 40, 42. In particular, the processor 28 of the controller 26 implements or oversees one or more control processes or control strategies in cooperation with the field devices 40, 42 and the workstations 17 to control the process plant 10 or a portion of the process plant in any desired manner. The field devices 40, 42 may be any desired type, such as sensors, valves, transmitters, positioners, etc., and may conform to any desired open, proprietary, or other communication or programming protocol including, for example, the HART or the 4-20 ma protocol (as illustrated for the field devices 40), any bus protocol such as the Foundation® Fieldbus protocol (as illustrated for the field devices 42), or the CAN, Profibus, and AS-Interface protocols, to name but a few. Similarly, each of the I/O devices 30, 32, 34 may be any known type of process control I/O device using any appropriate communication protocol.
The controller 26 may be configured to implement the control process or the control strategy in any desired manner. For example, the controller 26 may implement a control strategy using what are commonly referred to as function blocks, wherein each function block is a part or object of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process control system 14. Function blocks typically perform one of: an input function such as that associated with a transmitter, a sensor, or other process parameter measurement device; a control function such as that associated with a control routine that performs PID, fuzzy logic, etc. control; or, an output function that controls the operation of some device such as a valve to perform some physical function within the process control system 14. Hybrids of these function blocks, as well as other types of function blocks, may also exist. While the description of the control system is provided herein using a function block control strategy that incorporates an object oriented programming paradigm, the control strategy or control routines or control loops or control modules could also be implemented or designed using other conventions, such as ladder logic or sequential function charts, for example, or using any other desired programming language or paradigm.
For the purposes of this disclosure, the terms control strategy, control routine, control module, control function block, safety module, safety logic module, and control loop essentially denote a control program executed to control the process and these terms may be interchangeably used herein. However, for the purposes of the following discussion, the term control module will be used. It should further be noted that control module described herein may have parts thereof implemented or executed on by different controllers or other devices if so desired. In addition, the control modules described herein to be implemented within the process control system 14 and/or the safety system 16 may take any form, including software, firmware, hardware, and any combination thereof. For example, the control modules, which may be control routines or any part of a control procedure such as a subroutine or parts of a subroutine (such as lines of code), may be implemented in any desired software format, such as using ladder logic, sequential function charts, control routine diagrams, object oriented programming or any other software programming language or design paradigm. Likewise, the control modules described herein may be hard-coded into, for example, one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), programmable logic controllers (PLCs), or any other hardware or firmware elements. The control modules may be designed using any design tools, including graphical design tools or any other type of software/hardware/firmware programming or design tools.
One or more control modules 36 may be stored on memory 38 in the controller 26 and executed on the processor 28 of the controller 26, which is typically the case when these function blocks are used or associated with standard 4-20 ma devices and some types of smart field devices such as HART devices. The control modules 36 may also be stored on other memory locations 19, 21 within the system 10 or implemented by the field devices 40, 42 themselves, which may be the case with Fieldbus devices.
The safety system 16 of the process control/safety control node 12 includes one or more safety system logic solvers 50, 52. Each of the logic solvers 50, 52 is a safety controller (also invariably referred to as an I/O device) having a processor 54 capable of executing safety logic modules 58. The safety logic modules 58, which may be similar to the control modules 36, may be stored in a memory 56 location of one or both logic solvers 50, 52. The logic solvers 50, 52 are communicatively connected to provide control signals to and/or receive signals from safety system field devices 60, 62. The safety controllers 50, 52 and the safety system field devices 60, 62 generally make up the safety system 16 of
The safety field devices 60, 62 may be any desired type of field device conforming to or using any known or desired communication protocol, such as those mentioned above. In particular, the field devices 60, 62 may be safety-related field devices of the type that are conventionally controlled by a separate, dedicated safety-related control system, such as a liquid level detector or an emergency shutdown (ESD) valve. In the process plant 10 illustrated in
The backplane 24 (indicated by a dashed line through the process controller 26, the I/O devices 30, 32, 34, and the safety controllers 50, 52) is used to connect the process controller 26 to the process control I/O cards 30, 32, 34 as well as to the safety controllers 50, 52. The process controller 26 is also communicatively coupled to the bus 22 and operates as a bus arbitrator to enable each of the I/O devices 30, 32, 34 and the safety controllers 50, 52 to communicate with any of the workstations 17 or the memory device 21 via the bus 22. The backplane 24 also enables the safety controllers 50, 52 to communicate with one another and coordinate safety functions implemented by each of these devices, to communicate data to one another, or to perform other integrated functions.
The workstations 17 may each include a workstation processor 18 and a memory 19. One or more control modules 36 and/or safety logic modules 58 may be stored on the memory 19 and may be capable of being executed by any of the processors 18, 28, 54 within the process plant 10. In general, one or more of the modules 36, 58 may be executed by one of the processors to control and/or monitor a process via one or more field devices 40, 42, 60, 62. A display module 48 is illustrated in an exploded view in
By and large, a control system includes a controller that is configured to respond to a target or an occurrence of an event trigger associated with a process condition. One or more control modules may be executed by one or more processors to monitor and/or control the process via one or more field devices. Process or safety information is attained by the field device and passed on to the controller wherein the controller may adjust the process, if necessary. For example, in a level control system, a controller may monitor the process for the occurrence of an event trigger relating to a liquid level exceeding an upper threshold limit within a holding tank. The controller may utilize a sensor to detect the position of a device such as a float or displacer situated within the liquid. Should the displacer exceed the upper threshold limit, the sensor will be tripped and related information may be provided to the controller. The controller may store and/or report the information to control personnel and/or adjust a set-point or position of another field device, such as a valve, to prevent liquid from entering the holding tank.
In some control systems, there may be one or more components that are required to move during normal operation, and yet some of these components may be normally inactive or idle during a significant portion of its operation. For example, the movable components associated with the detecting mechanism of a high-level sensor may be idle for a considerable amount of time if the liquid level rarely reaches the upper threshold limit. However, when the liquid level does rise to the upper threshold limit, there is a concern that the movable components of the sensor may not function properly due to the prolonged inactivity. To validate that the field device is available and to ensure its operability, a diagnostic check of the field device may be performed wherein the controller may simulate the occurrence of the event trigger to trip the sensor portion by moving the movable components of the field device. The periodic excitation of the movable components may protect against the sedentary nature of the high-level detecting field device and its normally “dry” state of operation. After excitation of the movable components of the field device, the controller may record the operation and take the necessary actions depending on the observed proper or improper result, such as recording and/or transmitting corresponding information associated with the diagnostic check and adjusting other field devices in the control system.
One example implementation of the present invention for validating the availability and operability of a field device 240 used in a control system 12 of a process plant is shown in
The displacer 74 includes one or more characteristics, such as a mass, volume, and buoyancy, for example, and is situated within the liquid of the holding tank 90. The displacer 74 is responsive to its operating environment and, in particular, to one or more properties or characteristics of the liquid, such as the level, viscosity, density, and temperature, for example. The displacer 74 essentially floats within the liquid held within the holding tank 90 and is adaptable to the fluctuating level of the liquid. The position of the displacer 74 within the liquid of the holding tank 90 is monitored by a processor 228 via a communication link or bus 222 and related information may be provided to control personnel at any of the workstations within the plant.
An actuator 78 is operatively connected to the movable assembly 70. In the example embodiment shown in
Control modules 250, which may include one or more diagnostic modules, are stored on a memory 219 that is communicatively coupled to the processor 228. When executed on the processor 228, the diagnostic module is capable of performing a diagnostic check, or a portion of a diagnostic check, on the field device 240. For example, the diagnostic module may include: an actuating module 252 that facilitates actuating the actuator 78, an exhibiting module 254 that facilitates exhibiting the result of the diagnostic check at an output device 248, and an analyzing module 256 that may analyze and compare the results of one or more diagnostic checks. The diagnostic module includes commands or instructions that may be sent to the actuator 78, via the processor 228, to impart movement to the displacer 74. The commands may be initiated by control personnel and discretely transmitted via the processor 228 as needed and/or the commands may be programmed for periodic transmission or in response to an event trigger, such as the passage of a period of inactivity for the field device 240, for example. Control personnel may designate the time and/or the event trigger for executing the diagnostic check of the level control field device 240, which may provide increased flexibility in maintaining the field device 240. All formulations, comparisons, and determinations involving the diagnostic check and any subsequent response action may be administered through the cooperation of the control node 12.
A sensor 80 is mechanically connected and/or operatively coupled to the movable assembly 70 in any desired configuration wherein the sensor is able to measure a quantity that is representative of a characteristic of the field device 240 and/or its operating environment. A characteristic of the field device 240 or the operating environment may include the level of the liquid, the viscosity of the liquid, the buoyancy of the liquid, the density of the liquid, the mass of the displacer, the weight of the displacer, or the buoyancy of the displacer, for example. The sensor 80 is capable of converting the measured quantity into a signal of information, which may be in the form of a mechanical signal or an electrical signal, such as an analog or digital voltage, for example.
In the example implementation shown in
Another example embodiment of the invention for validating the operability and availability of a field device integrated in a control system is shown in
The displacer 474 includes one or more characteristics, such as a mass, volume, and buoyancy, for example, and is situated within the liquid of the holding tank 490. The displacer 474 is responsive to its operating environment and, in particular, to one or more properties or characteristics of the liquid, such as the level, viscosity, density, and temperature, for example. The displacer 474 essentially floats within the liquid held within the holding tank 490 and is adaptable to the fluctuating level of the liquid. The position of the displacer 474 within the liquid of the holding tank 490 is monitored by a processor 428 via a communication link or bus 422 and related information may be provided to control personnel at any of the workstations within the plant.
An actuator 478 is operatively connected to the movable assembly 470 and may be connected between the bar 472 and the processor 428 of the control node 412. The actuator 478 may be any type of device that is capable of imparting movement to the movable assembly 470, which ultimately causes movement to the displacer 474. The actuator 478 may be an electric, mechanical, or electromechanical device, such as a solenoid or electromagnet, for example. The processor 428, which is coupled to the actuator 478 via a communication line or bus 422, is capable of actuating the actuator 478 and facilitating movement of the displacer 474.
Control modules 450, which may include one or more diagnostic modules, are stored on a memory 419 that is communicatively coupled to the processor 428. When executed on the processor 428, the diagnostic module is capable of performing a diagnostic check, or a portion of a diagnostic check, on the field device 440. For example, the diagnostic modules may include: an actuating module 452 that facilitates actuating the actuator 478, an exhibiting module 454 that facilitates exhibiting the result of the diagnostic check at an output device 448, and an analyzing module 456 that may analyze and compare the results of one or more diagnostic checks. The diagnostic module includes commands or instructions that may be sent to the actuator 478, via the processor 428, to impart movement to the displacer 474. The commands may be initiated by control personnel and discretely transmitted via the processor 428 as needed and/or the commands may be programmed for periodic transmission or in response to an event trigger, such as the passage of an inactive period for the field device 440, for example. Control personnel may designate one or more times or event triggers for executing the diagnostic check of the level control field device 440, which may provide increased flexibility in maintaining the field device 440. All formulations, comparisons, and determinations involving the diagnostic check and any subsequent response action may be administered through the cooperation of the control node 412.
The operating environment and/or one or more characteristics of the displacer 474 may be monitored by the processor 428 via a sensor 480 mechanically connected and/or electrically coupled to the movable assembly 470. The sensor 480 may be a discrete or digital sensor capable of receiving and/or taking one or more measurements of a quantity that is representative of the operating environment or one or more of the characteristics of the field device 440. Alternately, the sensor 480 may be a proportional or analog sensor capable of continuously receiving and/or measuring a quantity or that is representative of the operating environment or one or more of the characteristics of the field device 440. A characteristic of the field device 440 or the operating environment may include the level of the liquid, the viscosity of the liquid, the buoyancy of the liquid, the density of the liquid, the mass of the displacer, the weight of the displacer, or the buoyancy of the displacer, for example. The sensor 480 is capable of converting the received and/or measured quantity into a signal of information, which may be in the form of a mechanical signal or an electrical signal, such as an analog or digital voltage, for example.
The information provided by the sensor 480 may be analyzed by the control processor 428 to determine the operating condition of the displacer 474. The analysis may include a comparison of standard information to information attained through the measurement. In addition, the analysis may include a comparison of information attained through several measurements taken at different times. The standard information and the information attained by measurement may be stored in the memory 419 of the control system. Depending on the result of the comparison, the control processor 428 may store the resultant analysis in memory 419 within the control system 412 and/or display the resultant analysis visually and/or audibly at the output device 448.
In the implementation shown in
An analysis of the information may uncover that one or more characteristics of the displacer 474 have changed from its initial condition. Any change to the displacer's characteristics may affect the measurement capability and accuracy of the field device 440 and repair or replacement of the displacer 474 may be needed. For example, paraffin and other foreign substances have been known to attach to a displacer during use, which may affect the buoyant characteristics of the displacer. The change in the buoyant characteristic of the displacer may be deduced through an observed change in the frequency, amplitude, dampening, and/or resonance of the bobbing displacer.
The analysis of the information may also uncover that the operating environment of the displacer has changed from its initial condition. In particular, any change to the fluid within the holding tank 490 may be detectable by a change in respect to the initially measured characteristics of the displacer 474. That is, if a different liquid was added to the holding tank 490, a change in the viscosity, density, or grade of the liquid may be detectable by a change in the frequency, amplitude, dampening, and/or resonance of the displacer 474. Thus, by knowing the characteristic property(ies) of the displacer 474 and the environment in which the displacer is expected to operate in, changes detected in any of the characteristic property(ies) of the displacer may represent a change in the operating condition of the displacer or the operating environment of the displacer, such as the level or density of the liquid.
Past validation techniques for liquid holding tanks incorporating level control field devices required control personnel to be present at the site of the field device. In addition, for holding tanks with integrated bridles, the level control system must be suspended while the bridle is removed, drained, refilled, and checked. It is apparent from the description above that the present invention is readily adaptable to existing electromechanical level control systems and is capable of providing a quick and accurate assessment of the components and operating environment of a remote field device without interruption to the control system and without the need for control personnel to be present at the site of the field device.
Although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus, and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
For example, the control system 10 may include, but is not limited to, any combination of a LAN, a MAN, a WAN, a mobile, a wired or wireless network, a private network, or a virtual private network. Moreover, while only two workstations are illustrated in
Additionally, certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules. A hardware module is tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations.
Accordingly, the term hardware should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware and software modules can provide information to, and receive information from, other hardware and/or software modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple of such hardware or software modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware or software modules. In embodiments in which multiple hardware modules or software are configured or instantiated at different times, communications between such hardware or software modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware or software modules have access. For example, one hardware or software module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware or software module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware and software modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
Similarly, the methods or routines described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or processors or processor-implemented hardware modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a plant environment, an office environment, or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
The one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., application program interfaces (APIs).)
The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the one or more processors or processor-implemented modules may be located in a single geographic location (e.g., within a plant or office environment). In other example embodiments, the one or more processors or processor-implemented modules may be distributed across a number of geographic locations.
Some portions of this specification are presented in terms of algorithms or symbolic representations of operations on data stored as bits or binary digital signals within a machine memory (e.g., a computer memory). These algorithms or symbolic representations are examples of techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. As used herein, an “algorithm” or a “routine” is a self-consistent sequence of operations or similar processing leading to a desired result. In this context, algorithms, routines and operations involve physical manipulation of physical quantities. Typically, but not necessarily, such quantities may take the form of electrical, magnetic, or optical signals capable of being stored, accessed, transferred, combined, compared, or otherwise manipulated by a machine. It is convenient at times, principally for reasons of common usage, to refer to such signals using words such as “data,” “content,” “bits,” “values,” “elements,” “symbols,” “characters,” “terms,” “numbers,” “numerals,” or the like. These words, however, are merely convenient labels and are to be associated with appropriate physical quantities.
Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “presenting,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.
As used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
Some embodiments may be described using the expression “coupled” and “connected” along with their derivatives. For example, some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. The embodiments are not limited in this context.
As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the description. This description should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.
Still further, for the purposes of illustration only, the figures depict preferred embodiments of a verification system for a field device within a control system. One skilled in the art will readily recognize from the discussion above that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein.
