Patent ID: 12216887

DETAILED DESCRIPTION

An industrial enterprise can include multiple industrial machines (e.g., oil and gas industrial machines) that can be distributed over multiple industrial sites distributed over various geographical locations (e.g., across the globe). A monitoring system can monitor the operations of the industrial machines in the industrial enterprise. For example, the monitoring system can determine whether an industrial machine is operating as desired (e.g., based on detection of operating parameters of the machine). The monitoring system can include a graphical user interface (GUI) that can allow a user to interact with the monitoring system. For example, the user can view alerts (e.g., alarm events) that have been activated in the industrial enterprise, can review existing reports on the industrial machines generated by different users, etc. In some implementations, one or more monitoring system GUIs can be presented via a web browser. For example, the web browser can include multiple tabs and each tab can include a monitoring system GUI.

A monitoring system GUI can allow a user to interact with multiple applications that can be executed by the monitoring system. Each application and can provide a particular type of information associated with the industrial machines in the industrial enterprise (or a subset thereof). For example, an alert application can present the various alarm events of the industrial machines, a report application can present the various reports associated with the different industrial machines (e.g., generated by other users), etc. The applications can be represented by interactive graphical objects in the monitoring system GUI. A user can select an application by interacting with the graphical object (e.g., by the clicking on it).

The user can provide monitoring system GUI with one or more filter criteria based on which information associated with the plurality of industrial machines in the industrial enterprise (e.g., information that fulfils the filter criteria provided by the user via the GUI). In some implementations, the application selected in the GUI application is applied to the subset of industrial machines based on the selected filter criteria. In existing implementations of the web-browser-based monitoring system GUIs, when the user navigates through the various applications, the filter criteria is not preserved. In other words, when the user decides to select an application after working on a previous application, the filter criteria associated with the latter (e.g., which may be entered by the user) may not be applied to the former. This may not be desirable as the user may have to provide the filter criteria all over again. This may be undesirable and inefficient (e.g., when the user wants to use the same filter criteria for multiple applications).

In some implementations of the current subject matter described herein, a technical solution to the technical problem associated with the lack of persistence of the filter criteria for multiple applications is provided. For example, the filter criteria can be preserved and applied to multiple applications for a GUI in a given tab of the web-browser. The user may also generate a new filter criteria (e.g., by adding a new filter criterion to the preserved filter criteria, edit the fields of the preserved filter criteria, etc.) when using a new application in the web-browser-based monitoring system GUI. In some implementations, the user may store the new filter criteria that can be used for a different application. This can increase the efficiency of user interaction with the web-browser-based monitoring system GUI (e.g., reduce the time taken to switch between applications when same or similar filter criteria are used).

FIG.1is a flow chart of an exemplary method for executing an application based on preserved filter criteria. At step102, data characterizing selection of a first application of a plurality of applications associated with an industrial enterprise can be received (e.g., via a first tab of a web browser that includes a graphical user interface (GUI)). The industrial enterprise can include a plurality of industrial assets.FIG.2illustrates and exemplary web-browser200of a monitoring system of an industrial enterprise. The web-browser can include multiple tabs202-208. A tab of the web-browser can include a web-browser based GUI that can allow the user to interact with the monitoring system (e.g., via different applications). For example, the first tab202can include a web-browser based GUI210.

FIG.3illustrates the web-browser based GUI210. The GUI210includes a first region302and a second region304. The first region302includes a plurality of interactive objects310-320. Each interactive object is representative of an application of the monitoring system. An application can be used to interact with the monitoring system of the industrial enterprise (e.g., to retrieve information associated with industrial machines, monitor/control the operation of industrial machine(s), perform operations (e.g., respond to alarm events) on the industrial machine(s), etc.). For example, the first interactive object310is representative of the home application; the second interactive graphical object312is representative of the alert application (e.g., associated with the alarms generated in the industrial enterprise); the third interactive graphical object314is representative of the findings application; the fourth interactive graphical object316is representative of the reports application; the fifth interactive graphical object318is representative of the entities application; and the sixth interactive graphical object320is representative of the work orders application.

The second region304can include a first portion306that includes a plurality of interactive objects representative of filter criteria for information associated with the industrial machines in the industrial enterprise. The interactive objects representative of filter criteria can include, for example, a level graphical object322, a date range graphical object324, etc. In some implementations, the industrial machines in the industrial enterprise can be arranged in levels of a hierarchical structure. Each level of the hierarchical structure can include one or more industrial machines. The level graphical object322can allow for selection of industrial machines associated with one or more layers (e.g., first layer, second layer, or both). The date range graphical object324can allow for selection of information associated with industrial machines based on a time stamp associated with the information (e.g., based on the time an alarm event or a report was generated). For example, information having a time stamp temporally located in the date range can be selected.

A user can select an application based on interaction with the corresponding graphical object. For example, as illustrated inFIG.3, a user can select the fourth graphical object316(representative of the reports application) based on a first user interaction with the first interactive graphical object316. The user can select filter criteria based on interaction with level graphical object322, date range graphical object324, and graphical object326. In some implementations, as described below, the user can apply a previously used filter criteria (e.g., associated with a different application) to the interaction with the current application (e.g., report application). Based on the selection of the filters in the first portion306of the second region304, the search results can be displayed in the second portion308of the second region304.

FIG.4illustrates another implementation of the GUI210in which the second graphical object312(associated with alert application) and filter criteria associated with the levels of the industrial machine and date range are selected (e.g., via the level graphical object322and date range graphical object324, respectively). Additional filter criteria can be selected from a drop-down menu328generated by interacting with the graphical object326. For example, the drop down box328can include additional filter criteria associated with alert severity, alert type, inspection type, equipment repair status.

Returning toFIG.1, at step104, a first context dataset associated with the first application can be generated. The generation of the first context dataset can be based on a second context dataset associated with a second application (e.g., a previously used application). The second context dataset associated with a second application (e.g., reports application) can be generated prior to the generation of the first context dataset (e.g. associated with the alert application). In some implementations, the second application can be selected based on a second user interaction indicative of selection of a second interactive object (e.g., fourth graphical object316representative of the reports application) in the first region302of the GUI210. Additionally, filter criteria associated with the second application can be selected based on a third user interaction with graphical objects in the first portion306of the second region304. For example, as discussed above forFIG.3, filter criteria for the reports application can be selected based on interaction with level graphical object322, date range graphical object324, and graphical object326. The second context dataset can be generated and the selected filter criteria associated with the second application can be included in the second context dataset.

The second context dataset can be stored (e.g., in memory) and may be retrieved by the first application (e.g., when the user begins working on the first application (alerts application) after working on the second application (e.g., reports application)). The first context dataset of the first application can be generated based on the retrieved second context dataset. For example, the set of filter criteria included in the second context dataset can be included in the set of filter criteria included in the first context dataset. In some implementations, a context dataset (e.g., the first context dataset, the second context dataset, etc.) can include an identifier indicative of the tab (e.g., tab202, tab204, tab206, etc.) of the web-browser200in that supports the GUI associated with the first and second applications. For example, the first context data set and second context data set associated with the reports application and alert application, respectively, can include an identifier for the tab202that includes the web-browser based GUI210.

In some implementations, when the user begins working with the first application (e.g., alerts application), the graphical objects in the first portion306of the second region304can be automatically populated based on the filter criteria used in the previously used second application (e.g., reports application). For example, the level graphical object322inFIG.4is populated with entries to the level graphical object322inFIG.3and the date range graphical object324inFIG.4is populated with entries to the level graphical object324inFIG.3(associated with reports application).

In some implementations, the first context dataset can be modified based on user interaction with the graphical objects in the first portion306of the second region304inFIG.4. For example, the user can change the entries of the level graphical object322, date range graphical object324, etc., inFIG.4(e.g., which can be populated based on the first context dataset that includes filter criteria in the second context dataset). Based on the change to the entries, the first context dataset can be modified. In some implementations, when the user interacts with a third application (e.g., after interaction with the first application), a third context dataset can be generated that includes filter criteria of the first context dataset.

At step106, the first context dataset can be provided to the first application. At step108, a first operation summary can be provided in the graphical user interface of the first tab of the web browser (e.g., GUI210of tab202of the web browser200). In some implementations, the first application can receive the first context dataset and generate a query format. Based on the query format a search can be performed on an industrial enterprise database, and information that satisfy the filter criteria in the first context dataset can be retrieved. For example, if the level filter criterion (associated with level graphical object322) is set to level1and level2(e.g., as illustrated inFIG.3), a search result that includes information from the enterprise database associated with industrial machines in level1or level2of the industrial enterprise hierarchy can be retrieved. If additional filter criteria are provided (e.g., a date range associated with the information is provided via the date range graphical object324), the search result can be further modified to satisfy the additional filter criteria.

The first operation summary can be provided in the second region304of the GUI210. As illustrated inFIG.3, the operation summary associated with the alert application is provided in the second portion308of the second region304. The operation summary includes the identity of the selected report(s), the report type, the date of inspection associated with the report(s), and the corresponding date of creation of the report. Alternately, as illustrated inFIG.4, the operation summary associated with the alert application is provided in the second portion308of the second region304. The operation summary can include the identity of the selected alert event(s) (e.g., alarms), severity of the alert event(s), the industrial machines associated with the alert event(s), alert status, date(s) the alert status was generated, date(s) the alert status was detected, etc.

FIG.5illustrates an exemplary data flow diagram of preserving filter criteria in a web-browser based GUI. At502, a user can select an application (e.g., report application) from a plurality of applications. The selection can be based on interaction with the corresponding graphical object (e.g., fourth interactive graphical object316) in the graphical user interface (e.g., first region302of GUI210). At504, the selected application is assigned a tab identifier (e.g., by the report application). The tab identifier can be a unique identifier associated with the tab of the web-browser that includes the GUI with the selected application (e.g., identifier associated with tab202that includes the GUI210). At506, the user can select the filter criteria (e.g., via interactive graphical objects322-326in the first portion306of the second region304of the GUI) associated with the selected application and provide instructions to the filter engine for generation of a context dataset that can include the selected filter criteria. At508, the filter engine can add the selected filter criteria to the context dataset, and at510the filter engine can store the context dataset in a data storage (e.g., browser data storage). At512, the filter engine can share the context dataset with the application selected at502. At514, the application selected at502can parse the context dataset and generate a query format. At516, the application can provide the query format to the search engine and instruct the search engine to execute the search (e.g., at the industrial enterprise database). At518, the search engine can provide the search result to the application selected at step502. At520, the application can provide the search result to the user (e.g., via the second portion308of the second region304of the GUI210).

At522, the user can select another application (e.g., alert application) from the plurality of applications. The selection can be based on interaction with the corresponding graphical object (e.g., second interactive graphical object312) in the graphical user interface (e.g., first region302of GUI210). At524, the selected application is assigned the unique tab identifier (e.g., the alert application can assign the unique tab identifier assigned at504). At526, the filter engine can retrieve the context dataset stored in the data storage at510and assign the filter criteria of the context dataset to a new context dataset. At528, the filter engine can share the new context dataset with the application selected at522. At530, the application selected at522can parse the new context dataset and generate a new query format. At532, the application can instruct the search engine to execute the search based on the new query format (e.g., at the industrial enterprise database), and at534, the search engine can provide the search result to the application selected at step522.

FIG.6illustrates an exemplary computing system600configured to execute the data flow described inFIG.5. The computing system600can include a processor610, a memory620, a storage device630, and input/output devices640. The processor610, the memory620, the storage device630, and the input/output devices640can be interconnected via a system bus650. The processor610is capable of processing instructions for execution within the computing system600. Such executed instructions can implement one or more steps for preserving filter criteria in the web-browser based GUI (e.g., as described inFIG.1,FIG.5, etc.). In some example embodiments, the processor610can be a single-threaded processor. Alternately, the processor610can be a multi-threaded processor. The processor610is capable of processing instructions stored in the memory620and/or on the storage device630to display graphical information for a user interface provided via the input/output device640. The processor610can support/execute one or more of the applications, filter engine and the search engine described inFIG.5.

The memory620is a computer readable medium such as volatile or non-volatile that stores information within the computing system600. The memory620can store the context datasets. The storage device630is capable of providing persistent storage for the computing system600. The storage device630can be a floppy disk device, a hard disk device, an optical disk device, a tape device, a solid state drive, and/or other suitable persistent storage means. The input/output device640provides input/output operations for the computing system600.

In some example embodiments, the input/output device640includes a keyboard and/or pointing device. In various implementations, the input/output device640includes a display unit for displaying graphical user interfaces. In some implementations, the web-browser200of the monitoring system can be displayed in a display of the input/output device640. In some implementations, the computing device600can be communicatively coupled to an industrial enterprise database660. The search engine (e.g., executed by the processor610) can perform the search (based on a query format) in the industrial enterprise database660.

Certain exemplary embodiments will now be described to provide an overall understanding of the principles of the structure, function, manufacture, and use of the systems, devices, and methods disclosed herein. One or more examples of these embodiments are illustrated in the accompanying drawings. Those skilled in the art will understand that the systems, devices, and methods specifically described herein and illustrated in the accompanying drawings are non-limiting exemplary embodiments and that the scope of the present invention is defined solely by the claims. The features illustrated or described in connection with one exemplary embodiment may be combined with the features of other embodiments. Such modifications and variations are intended to be included within the scope of the present invention. Further, in the present disclosure, like-named components of the embodiments generally have similar features, and thus within a particular embodiment each feature of each like-named component is not necessarily fully elaborated upon.

Other embodiments are within the scope and spirit of the disclosed subject matter. For example, the monitoring system described in this application can be used oil fields that can include multiple oil wells. The monitoring system can also be used in facilities that have complex machines with multiple operational parameters that need to be altered to change the performance of the machines (e.g., power generating turbines).

The subject matter described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described herein can be implemented as one or more computer program products, such as one or more computer programs tangibly embodied in an information carrier (e.g., in a machine-readable storage device), or embodied in a propagated signal, for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). A computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification, including the method steps of the subject matter described herein, can be performed by one or more programmable processors executing one or more computer programs to perform functions of the subject matter described herein by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus of the subject matter described herein can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processor of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks, (e.g., internal hard disks or removable disks); magneto-optical disks; and optical disks (e.g., CD and DVD disks). The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, the subject matter described herein can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, (e.g., a mouse or a trackball), by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user can be received in any form, including acoustic, speech, or tactile input.

The techniques described herein can be implemented using one or more modules. As used herein, the term “module” refers to computing software, firmware, hardware, and/or various combinations thereof. At a minimum, however, modules are not to be interpreted as software that is not implemented on hardware, firmware, or recorded on a non-transitory processor readable recordable storage medium (i.e., modules are not software per se). Indeed “module” is to be interpreted to always include at least some physical, non-transitory hardware such as a part of a processor or computer. Two different modules can share the same physical hardware (e.g., two different modules can use the same processor and network interface). The modules described herein can be combined, integrated, separated, and/or duplicated to support various applications. Also, a function described herein as being performed at a particular module can be performed at one or more other modules and/or by one or more other devices instead of or in addition to the function performed at the particular module. Further, the modules can be implemented across multiple devices and/or other components local or remote to one another. Additionally, the modules can be moved from one device and added to another device, and/or can be included in both devices.

The subject matter described herein can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a web interface through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

Approximating language, as used herein throughout the specification and claims, may be applied to modify any quantitative representation that could permissibly vary without resulting in a change in the basic function to which it is related. Accordingly, a value modified by a term or terms, such as “about” and “substantially,” are not to be limited to the precise value specified. In at least some instances, the approximating language may correspond to the precision of an instrument for measuring the value. Here and throughout the specification and claims, range limitations may be combined and/or interchanged, such ranges are identified and include all the sub-ranges contained therein unless context or language indicates otherwise.