Abstract:
Methods and apparatus to create process plant operator interfaces are disclosed. A disclosed example method to create a process plant operator interface comprises receiving a search criterion, identifying a user interface module based on the search criterion, and adding the identified user interface module to the process plant operator interface.

Description:
FIELD OF THE DISCLOSURE 
       [0001]    This disclosure relates generally to process plants and, more particularly, to methods and apparatus to create process-plant operator interfaces. 
       BACKGROUND 
       [0002]    Distributed process control systems, like those used in chemical, petroleum and/or other processes, systems, and/or process plants typically include one or more process controllers communicatively coupled to one or more field devices via any of a variety of analog, digital and/or combined analog/digital buses. In such systems and/or processes, field devices including, for example, valves, valve positioners, switches and/or transmitters (e.g., temperature, pressure, level and flow rate sensors), are located within the process environment and perform process control, alarm and/or management functions such as opening or closing valves, measuring process parameters, etc. Process controllers, which may also be located within the plant environment, receive signals indicative of process measurements made by the field devices and/or other information pertaining to the field devices. Based on, for example, the received signals, the process controllers execute a controller application to realize any number and/or type(s) of control modules, software modules, software sub-systems, routines and/or software threads to initiate alarms, make process control decisions, generate control signals, and/or coordinate with other control modules and/or function blocks performed by field devices, such as HART and Foundation Fieldbus devices. The control modules in the controller(s) send the control signals over the communication lines to the field devices to control the operation of the process plant. 
         [0003]    Information from the field devices and/or the controller is usually made available over a data highway or communication network to one or more other hardware devices, such as operator workstations, personal computers, data historians, report generators, centralized databases, etc. Such devices are typically located in control rooms and/or other locations remotely situated relative to the harsher plant environment. These hardware devices, for example, run applications that enable an operator to perform any of a variety of functions with respect to the process(es) of a process plant, such as changing an operating state, changing settings of the process control routine(s), modifying the operation of the control modules within the process controllers and/or the field devices, viewing the current state of the process(es), viewing alarms generated by field devices and/or process controllers, simulating the operation of the process(es) for the purpose of training personnel and/or testing the process control software, keeping and/or updating a configuration database, etc. 
         [0004]    As an example, the DeltaV™ digital automation system sold by Fisher-Rosemount Systems, Inc., an Emerson Process Management company, supports multiple applications stored within and/or executed by different devices located at potentially diverse locations within a process plant. A configuration application, which resides in and/or is executed by one or more operator workstations, enables users to create and/or change process control applications, and/or download process control applications via a data highway or communication network to dedicated distributed controllers. Typically, these control applications are made up of communicatively coupled and/or interconnected control modules, software modules, software sub-systems, routines, software threads and/or function blocks that perform functions within the control scheme (e.g., process control and/or alarm generation) based on received inputs and/or that provide outputs to other blocks within the control scheme. Each dedicated controller and, in some cases, field devices, stores and/or executes a control application that runs the control modules assigned to implement actual process control functionality. 
         [0005]    The configuration application also allows a configuration engineer to create one or more displays (e.g., a viewing application), for use by operators, maintenance personnel, etc. of the process plant, by selecting and/or building display objects using, for example, a display creation application. An example viewing application displays data for a process-plant operator and/or enables the operator to change settings, such as set points and/or operating states, with the process control routines. These displays are typically implemented on a system-wide basis via one or more of the workstations, and present preconfigured displays to the operator and/or maintenance persons regarding the operating state(s) of the control system(s) and/or the devices within the plant. Example displays take the form of alarming displays that receive and/or display alarms generated by controllers or devices within the process plant, control displays that indicate the operating state(s) of the controller(s) and other device(s) within the process plant, maintenance displays that indicate the functional state of the device(s) and/or equipment within the process plant, etc. 
       SUMMARY 
       [0006]    Methods and apparatus to create process-plant operator interfaces are disclosed. A disclosed example method to create a process-plant operator interface includes receiving a search criterion, identifying a user interface module based on the search criterion, and adding the identified user interface module to the process plant operator interface. 
         [0007]    A disclosed example operator station apparatus includes a display, an operator display module to present a process plant operator interface on the display, and a search engine to identify a user interface module based upon a search criterion, the operator display module to display an output of the user interface module. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0008]      FIG. 1  is a schematic illustration of an example process control system constructed in accordance with the teachings of the invention. 
           [0009]      FIG. 2  illustrates an example manner of implementing the example operator station of  FIG. 1 . 
           [0010]      FIGS. 3 ,  4  and  5  illustrate example user interfaces that may be used to create a process-plant operator interface and/or, more generally, the example operator station of  FIG. 1 . 
           [0011]      FIG. 6  is a flowchart representative of an example process that may be carried out to implement the example operator station of  FIG. 1 . 
           [0012]      FIG. 7  is a schematic illustration of an example processor platform that may be used and/or programmed to carry out the example process of  FIG. 6  and/or, more generally, to implement the example operator station of  FIG. 1 . 
       
    
    
     DETAILED DESCRIPTION 
       [0013]    Process plants are becoming increasingly complicated and difficult to configure and/or monitor. For example, there may be thousands of process control variables that may be set, controlled, viewed and/or monitored by process plant personnel. Moreover, in a process control system it is common for thousands of alarms to be defined within the process control system to notify operators of the process plant of potential problems. 
         [0014]    In general, the examples, apparatus, methods, and articles of manufacture described herein may be used to allow a process-plant operator to easily and/or dynamically create process-plant operator displays and/or interfaces. Today, many process-plant operator displays are pre-configured and do not allow a process-plant operator to configure or customize the display of information based upon personal experience, personal preferences, and/or current conditions resulting in an overload of information presented to process-plant operators and/or potentially causing the operators to miss critical process plant conditions. While, a process configuration engineer could conceivably design different process plant display applications for different process plant states and/or conditions, and/or for individual and/or groups of operators, the implementation of such large numbers of display applications is expensive, difficult to maintain and/or otherwise burdensome and is not as flexible as the example apparatus, methods and articles of manufactured described herein. 
         [0015]    In particular, the examples described herein allow a process-plant operator to create tailored, dynamic and/or customized process-plant operator interfaces and/or displays. As described, elements of process-plant operator interfaces (e.g., graphs of process variables, displays of current process variables, transaction based interfaces to control and/or configure the process plant, etc.) are modularized into user interface modules (i.e., so-called gadgets and/or plug-ins). To facilitate the identification and/or selection of potentially desirable user interface modules, example user interface modules described herein have associated metadata (e.g., title, description, keywords, associated equipment names, etc.) and/or embedded text which could be indexed. Based on one or more search criteria (e.g., word(s), keyword(s), phrase(s), and/or logical expression(s) of words, keywords and/or phrases) provided by a process-plant operator, user interface module metadata is used to search for and/or identify one or more user interface modules of potential interest to the operator. The operator may then select one or more of the identified user interface modules, and the operator workstation creates and/or updates a process-plant operator interface based on the selection(s). In some examples, the user interface modules are carried out, implemented and/or executed on, by and/or within the operator workstation. In other examples, one or more user interface modules are carried out, implemented and/or executed on, by and/or within other workstations and/or process plant controllers, with the outputs and/or input elements of the user interface module(s) being displayed at the operator workstation. 
         [0016]      FIG. 1  is a schematic illustration of an example process control system  105 . The example process control system  105  of  FIG. 1  includes one or more process controllers (one of which is designated at reference numeral  110 ), one or more operator stations (one of which is designated at reference numeral  115 ), and one or more workstations (one of which are designated at reference numeral  120 ). The example process controller  110 , the example operator station  115  and the workstation  120  are communicatively coupled via a bus and/or local area network (LAN)  125 , which is commonly referred to as an application control network (ACN). 
         [0017]    The example operator station  115  of  FIG. 1  allows a process-plant operator to review and/or operate one or more operator display screens and/or applications that allow the process-plant operator to view process plant variables, view process plant states, view process plant conditions, view process plant alarms, and/or to change process plant settings (e.g., set points and/or operating states, clear alarms, silence alarms, etc.). Such screens and/or applications are typically designed and/or implemented by process configuration engineers. An example manner of implementing the example operator station  115  of  FIG. 1  is described below in connection with  FIG. 2 . Example operator display applications and/or interfaces that may be used to implement the example operator station  115  are described below in connection with  FIGS. 3 ,  4  and  5 . 
         [0018]    The example operator station  115  of  FIG. 1  includes and/or implements one or more user interfaces (e.g., the example interfaces of  FIGS. 3-5 ) to allow a process-plant operator to search for, identify and/or select one more user interface modules useful to create, modify, customize and/or augment a process plant operator display and/or interface. User interface modules are modularized interfaces and/or software entities that may be used to create and/or construct a process plant operator interface and/or display. User interface modules may be used to monitor and/or control one or more portions of a process plant, and/or one or more specific pieces and/or collections of process plant equipment. Example user interface modules include, but are not limited to, modules that collect and graph one or more current and/or historical process variables, that collect and/or display one or more current and/or historical process variables, more or more control elements (e.g., check boxes, slider bars, etc.) that allow a process plant operator to control and/or configure a process plant, and/or transaction based interfaces to control and/or configure the process plant, etc. To facilitate the selection and/or identification of applicable user interface modules, user interface modules have associated metadata and/or embedded text, such as, title, description, keywords, associated equipment names, process names, etc., which could be indexed and/or searched by a search engine. 
         [0019]    In some examples, user interface modules are carried out, implemented and/or executed on, by and/or within the operator workstation being used to implement the process plant operator display. In other examples, one or more user interface modules are carried out, implemented and/or executed on, by and/or within other workstations and/or process plant controllers, with the outputs and/or input elements of the user interface module(s) being displayed at the operator workstation. 
         [0020]    The example workstation  120  of  FIG. 1  may be configured as an application station to perform one or more information technology applications, user-interactive applications and/or communication applications. For example, the application station  120  may be configured to perform primarily process control-related applications, while another application station (not shown) may be configured to perform primarily communication applications that enable the process control system  105  to communicate with other devices or systems using any desired communication media (e.g., wireless, hardwired, etc.) and protocols (e.g., HTTP, SOAP, etc.). The example operator station  115  and the example workstation  120  of  FIG. 1  may be implemented using one or more workstations and/or any other suitable computer systems and/or processing systems. For example, the operator station  115  and/or workstation  120  could be implemented using single processor personal computers, single or multi-processor workstations, etc. 
         [0021]    The example LAN  125  of  FIG. 1  may be implemented using any desired communication medium and protocol. For example, the example LAN  125  may be based on a hardwired and/or wireless Ethernet communication scheme. However, as will be readily appreciated by those having ordinary skill in the art, any other suitable communication medium(s) and/or protocol(s) could be used. Further, although a single LAN  125  is illustrated in  FIG. 1 , more than one LAN and/or other alternative pieces of communication hardware (e.g., hubs and/or switches) may be used to provide redundant communication paths between the example systems of  FIG. 1 . 
         [0022]    The example controller  110  of  FIG. 1  is coupled to a plurality of smart field devices  130 ,  131  and  132  via a digital data bus  135  and an input/output (I/O) gateway  140 . The smart field devices  130 - 132  may be Fieldbus compliant valves, actuators, sensors, etc., in which case the smart field devices  130 - 132  communicate via the digital data bus  135  using the well-known Foundation Fieldbus protocol. Of course, other types of smart field devices and communication protocols could be used instead. For example, the smart field devices  130 - 132  could instead be Profibus and/or HART compliant devices that communicate via the data bus  135  using the well-known Profibus and HART communication protocols. Additional I/O devices (similar and/or identical to the I/O gateway  140  may be coupled to the controller  110  to enable additional groups of smart field devices, which may be Foundation Fieldbus devices, HART devices, etc., to communicate with the controller  110 . Such smart field devices may provide significantly more data and/or information than non-smart field devices and, thus, may contribute to the information overload problem(s) addressed by the methods and apparatus described herein. 
         [0023]    In addition to the example smart field devices  130 - 132 , one or more non-smart field devices  145  and  146  may be communicatively coupled to the example controller  110 . The example non-smart field devices  145  and  146  of  FIG. 1  may be, for example, conventional 4-20 milliamp (mA) or 0-10 volts direct current (VDC) devices that communicate with the controller  110  via respective hardwired links. 
         [0024]    The example controller  110  of  FIG. 1  may be, for example, a DeltaV™ controller sold by Fisher-Rosemount Systems, Inc., an Emerson Process Management company. However, any other controller could be used instead. Further, while only one controller  110  in shown in  FIG. 1 , additional controllers and/or process control platforms of any desired type and/or combination of types could be coupled to the LAN  125 . In any case, the example controller  110  performs one or more process control routines associated with the process control system  105  that have been generated by a system engineer and/or other system operator using the operator station  115  and which have been downloaded to and/or instantiated in the controller  110 . 
         [0025]    While  FIG. 1  illustrates an example process control system  105  within which the methods and apparatus to create process plant operator interfaces and/or displays described in greater detail below may be advantageously employed, persons of ordinary skill in the art will readily appreciate that the methods and apparatus to control how and/or what information is presented to process plant operators described herein may, if desired, be advantageously employed in other process plants and/or process control systems of greater or less complexity (e.g., having more than one controller, across more than one geographic location, etc.) than the illustrated example of  FIG. 1 . 
         [0026]      FIG. 2  illustrates an example manner of implementing the example operator station  115  of  FIG. 1 . The example operator station  115  of  FIG. 2  includes at least one programmable processor  205 . The example processor  205  of  FIG. 2  executes coded instructions present in a main memory  210  of the processor  205  (e.g., within a random-access memory (RAM) and/or a read-only memory (ROM)). The processor  205  may be any type of processing unit, such as a processor core, a processor and/or a microcontroller. The processor  205  may execute, among other things, an operating system  215 , an operator display module  220 , one or more user interface modules (one of which is designated at reference numeral  225 ), and a search engine  230 . An example operating system  215  is an operating system from Microsoft®. The example main memory  210  of  FIG. 2  may be implemented by and/or within the processor  205  and/or may be one or more memories and/or memory devices operatively coupled to the processor  205 . 
         [0027]    To allow an operator to interact with the example processor  205 , the example operator station  115  of  FIG. 2  includes any number and/or type(s) of displays (one of which is designated at reference numeral  235 ). Example displays  235  include, but are not limited to, a computer monitor, a computer screen, a television, a mobile device (e.g., a smart phone, a Blackberry™ and/or an iPhone™), etc. capable to display user interfaces and/or applications implemented by the processor  205  and/or, more generally, the example operator station  115 . 
         [0028]    The example operating system  215  of  FIG. 2  displays and/or facilitates the display of application user interfaces (e.g., created by the example operator display module  220  using the example user interface module  225 ) by and/or at the example display  235 . To facilitate the creation, definition and/or modification of process plant operator interfaces, the example operating system  215  implements an application programming interface (API) by which the example operator display module  220  and/or the example search engine  230  can define and/or select one or more user interface modules (e.g., the user interface module  225 ), and cause and/or instruct the operating system  215  to display the selected user interface module(s)  225 . Example user interface modules  225  are described below in connection with  FIG. 5 . 
         [0029]    To create, modify and/or present process plant operator displays and/or applications, the example operator station  115  of  FIG. 2  includes the example operator display module  220 . The example operator display module  220  of  FIG. 2  collects graphics, user interface elements (e.g., graphs, slider bars, tables, etc.), data (e.g., current and/or historical) and/or information (e.g., state information) from one or more user interface modules (e.g., the example user interface module  225 ), and uses the collected graphics, user interface elements, data and/or information to create and/or define a particular user interface (e.g., the example interface of  FIG. 5 ) based on the state of the process plant and/or a portion of the process plant selected by an operator. The created and/or defined display is displayed at the example display  235  by and/or via the example operating system  215 . The example operator display module  220  can also receives operator inputs via the user interface module  225  (e.g., in response to the operator selecting, adjusting and/or operating user interface elements of the user interface module(s)  225 ) and sends appropriate commands, data and/or information to the controller  110  and/or, more generally, the process control system  105 . 
         [0030]    To store user interface modules (e.g., the example user interface module  225 ), the example operator station  115  of  FIG. 2  includes an interface module library  240 . Using any type(s) and/or numbers of database records, fields and/or entries, the example interface module library  240  of  FIG. 2  stores data and/or information used by, carried out by, implemented by and/or executed by the example operator display module  220 . User interface modules may be stored in the interface module library  240  using any data structure(s) and/or file format(s). To facilitate the selection and/or identification of applicable user interface modules, user interface modules are stored in the interface module library  240  together with associated metadata and/or embedded text, such as, title, description, keywords, associated equipment names, process names, etc., which could be indexed and/or searched by a search engine. The example interface module library  240  may be stored using any type(s) and/or numbers of memory(-ies) and/or memory device(s). When a particular user interface module (e.g., the example module  225 ) is to be part of a process plant operator display, the user interface module together with the appropriate data matching the search criterion is copied from the interface module library  240  into the main memory  210 . 
         [0031]    To communicatively couple the example operator station  115  of  FIG. 2  with other workstations (e.g., the example workstation  120  of  FIG. 1 ) and/or process plant controllers (e.g., the example controller  110 ), the example operator station  115  includes any type(s) and/or number(s) of network interface (one of which is designated at reference numeral  245 ). The example network interface  245  can be used by the example search engine  230  to search one or more alternative and/or additional interface module libraries stored within, by and/or at one or more other process plant devices (e.g., the example workstation  120  and/or the example controller  110 ). 
         [0032]    When a user of operator station  115  indicates a desire to create and/or modify an operator display (e.g., by initiating a search as described below in connection with  FIG. 3 ), the example search engine  230  of  FIG. 2  performs a search of the example interface module library  240  (and/or one or more interface modules libraries implemented and/or stored at, by and/or within other process plant devices) for user interface modules having one or more associated metadata elements matching one or more of the search criteria (e.g., word(s), keyword(s), phrase(s), and/or logical expression(s) of words, keywords and/or phrases) provided by the process plant operator. Based on the user interface modules identified by the example search engine  230 , the example operator display module  220  presents a user interface module selection interface (e.g., the example interface of  FIG. 4 ). When user interface module selections are made and/or completed by the process plant operator, the example operator display module  220  creates a corresponding process plant operator interface (e.g., the example interface of  FIG. 5 ) based on the selected user interface modules. 
         [0033]    While an example manner of implementing the example operator station  115  of  FIG. 1  has been illustrated in  FIG. 2 , the data structures, elements, processes and devices illustrated in  FIG. 2  may be combined, divided, re-arranged, omitted, shared, eliminated and/or implemented in any other way. Further, the example operating system  215 , the example operator display module  220 , the example user interface module  225 , the example search engine  230 , the example display  235 , the example interface module library  240 , the example network interface  245  and/or, more generally, the example operator station  115  of  FIG. 2  may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Further still, the example operator station  115  may include additional elements, processes and/or devices instead of, or in addition to, those illustrated in  FIG. 2 , and/or may include more than one of any or all of the illustrated data structures, elements, processes and devices. 
         [0034]      FIGS. 3 and 4  illustrate example user interfaces that may be used to create an operator display and/or operator application (e.g., the example operator display of  FIG. 5 ), and/or, more generally, the example operator station  115  of  FIG. 1 . The example user interfaces of  FIGS. 3 ,  4  and/or  5  are implemented using a web browser (e.g., Internet Explorer, Firefox, Safari, etc.) wherein user interface modules are implemented as web-based plug-ins and/or gadgets. Additionally or alternatively, the example interfaces of  FIGS. 3-5  may be implemented using custom applications and/or user interfaces. While example user interfaces that may be used to implement the example operator stations  115  of  FIGS. 1 and 2  are illustrated in  FIGS. 3-5 , the example operator station  115  of  FIGS. 1  and/or  2  may be implemented using any number and/or type of additional and/or alternative user interfaces. 
         [0035]    To allow an operator to specify a search criterion, the example user interface of  FIG. 3  includes a search-term text-entry box  305 . The example search-term text-entry box  305  of  FIG. 3  can be used to type and/or enter one or more search criteria to be used to search for and/or identify user interface modules of potential interest. Example search criteria include, but are not limited to, one or more words (e.g., separated by commas, semi-colons, spaces or quotation marks), keywords, phrases, and/or logical expressions of words, keywords and/or phrases. To initiate a search, the example user interface of  FIG. 3  includes a button  310 . When the example button  310  is activated (e.g., by clicking on the button  310  with a computer mouse, and/or by pressing the ENTER or RETURN key while typing in the text-entry box  305 ), the example search engine  230  uses the search criterion entered in the text-entry box  305  to identify one or more user interface modules, having metadata and/or embedded text matching the search criterion, of potential interest to the operator. 
         [0036]    The example user interface of  FIG. 4  displays a user interface provided and/or presented by the example operator display module  220  to present the results  405  of a user interface module search completed by the example search engine  230 . In the example interface of  FIG. 3 , the text-entry box  305  contained the search criterion “Distillation.” As such, the example user interface of  FIG. 4  presents the results  405  corresponding to user interface modules having the word “Distillation” in their metadata and/or embedded text (e.g., title, description, etc.). To allow the operator to select all or a subset of the listed user interface modules  405 , each of the listed user interface modules  405  has an associated check box  410 . To select the user interface modules to be displayed, the operator clicks on the associated check box(es)  410 . To allow the operator to name the display, the example user interface of  FIG. 4  includes a name text-entry box  415 . In the illustrated example of  FIG. 4 , the operator chooses a historical pressure graph and a display of current operating conditions for “Distillation Column1.” To create the operator display based on the selected user interface modules and the display name  415 , the example user interface of  FIG. 4  includes a button  420 . When the button  420  is activated (e.g., by clicking on the button  420  with a computer mouse), the example operator display module  220  creates the desired operator interface (e.g., the example user interface of  FIG. 5 ). Alternatively, the operator can initiate a different search using the text-entry box  305  and the button  310 . 
         [0037]      FIG. 5  illustrates an example process plant operator display resulting from the example user interfaces of  FIGS. 3 and 4 . In the illustrated example of  FIG. 5 , two plug-ins  505  and  510  are displayed corresponding to the two user interface modules selected in the example user interface of  FIG. 4 . The example plug-in  505  of  FIG. 5  displays the current values of a number of operating parameters. The example plug-in  505  also includes a button  515  that allows the operator to refresh the values. In other examples, the plug-in  505  could periodically or aperiodically update itself based upon a timer or some other triggering event. The example plug-in  510  of  FIG. 5  displays a graph of historical pressure values and includes a button  520  that allows the operator to configure the graph (e.g., which days and/or times are to be included in the graph). The example process plant operator display of  FIG. 5  is a dynamic interface wherein a process plant operator can close individual interface modules, browse a library of interface modules, manually add modules, search for additional interface modules (e.g., using methods that are substantially similar to those described above in connection with  FIGS. 3 and 4 ), and/or drag and/or drop interface modules around the display (e.g., into different columns or arrangements). 
         [0038]      FIG. 6  is a flowchart representative of an example process that may be carried out by the example operator station  115  of  FIGS. 1  and/or  2 . The example process of  FIG. 6  may be carried out by a processor, a controller and/or any other suitable processing device. For example, the example process of  FIG. 6  may be embodied in coded instructions stored on a tangible machine accessible or readable medium such as a flash memory, a ROM and/or random-access memory RAM associated with a processor (e.g., the example processor  705  discussed below in connection with  FIG. 7 ). Alternatively, some or all of the example operations of  FIG. 6  may be implemented using any combination(s) of application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic device(s) (FPLD(s)), discrete logic, hardware, firmware, etc. Also, one or more of the operations depicted in  FIG. 6  may be implemented manually or as any combination of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. Further, although the example process of  FIG. 6  is described with reference to the flowchart of  FIG. 6 , persons of ordinary skill in the art will readily appreciate that many other methods of implementing the example process of  FIG. 6  may be employed. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, persons of ordinary skill in the art will appreciate that any or all of the example operations of  FIG. 6  may be carried out sequentially and/or carried out in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc. 
         [0039]    The example process of  FIG. 6  begins with an operator station (e.g., the example operator display module  220  of  FIG. 2 ) displaying a user interface (e.g., the example user interface of  FIG. 3 ) (block  605 ). When a user (e.g., a process plant operator) selects a control user interface element and/or graphic (e.g., the example button  310 ) to initiate a search (block  610 ), the operator station (e.g., the example search engine  230 ) performs a search for applicable user interface modules based on the operator provided search criterion (e.g., keywords) (block  615 ). The operator station may search a local interface module library and/or one or more shared interface module libraries. 
         [0040]    Based upon the search results, the operator display module presents the search results (e.g., using the example user interface of  FIG. 4 ) (block  620 ). Once the operator makes their user interface module selections (block  625 ), the operator display module creates the process plant operator display (e.g., the example user interface of  FIG. 5 ) based on the selected user interface modules (block  630 ). Control then returns to block  605  to allow the operator to initiate another search and/or to modify the created operator display. 
         [0041]      FIG. 7  is a schematic diagram of an example processor platform  700  that may be used and/or programmed to implement any or all of the example operator stations  115  of  FIGS. 1  and/or  2 . For example, the processor platform  700  can be implemented by one or more general purpose processors, processor cores, microcontrollers, etc. 
         [0042]    The processor platform  700  of the example of  FIG. 7  includes at least one general purpose programmable processor  705 . The processor  705  executes coded instructions  710  and/or  712  present in main memory of the processor  705  (e.g., within a RAM  715  and/or a ROM  720 ). The processor  705  may be any type of processing unit, such as a processor core, a processor and/or a microcontroller. The processor  705  may execute, among other things, the example process of  FIG. 6  to implement the example operator stations  115  described herein. The processor  705  is in communication with the main memory (including a ROM  720  and/or the RAM  715 ) via a bus  725 . The RAM  715  may be implemented by DRAM, SDRAM, and/or any other type of RAM device, and ROM may be implemented by flash memory and/or any other desired type of memory device. Access to the memories  715  and  720  may be controlled by a memory controller (not shown). 
         [0043]    The processor platform  700  also includes an interface circuit  730 . The interface circuit  730  may be implemented by any type of interface standard, such as a USB interface, a Bluetooth interface, an external memory interface, serial port, general purpose input/output, etc. One or more input devices  735  and one or more output devices  740  are connected to the interface circuit  730 . The input devices  735  and/or output devices  740  may be used to, for example, provide the example user interfaces of  FIGS. 3 ,  4  and/or  5  to the example display  235  of  FIG. 2 . 
         [0044]    Although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. Such example are intended to be non-limiting illustrative examples. 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.