System and method for comparing and visualizing data entities and data entity series

Abstract

Systems and methods for creating and using a workflow template for analyzing data entities stored in the one or more databases. After a desired workflow is identified, one or more series, data source, and/or entity restrictions based upon the workflow may be received. In addition, one or more chart configuration settings based upon the workflow may also be received. The restrictions and configuration settings may be saved as the workflow template. The workflow may then be performed by loading the saved workflow template, in order to automatically generate charts in accordance with the configuration settings of the template, based upon a received selection of series, data sources, and entities that adheres to the restrictions defined in the template.

Description

TECHNICAL FIELD

The present disclosure relates to systems and techniques for querying databases and displaying queried data in an interactive user interface.

BACKGROUND

A database may store a large quantity of data. For example, a system may comprise a large number of sensors that each collect measurements at regular intervals, and the measurements may be stored in the database. The measurement data can be supplemented with other data, such as information regarding events that occurred while the system was operational, and the supplemental data can also be stored in the database.

In some cases, a user may attempt to analyze a portion of the stored data. For example, the user may attempt to identify and analyze a portion of the stored data associated with one or more devices, such as data from multiple sensors associated with a geological formation, such as an oil well. However, as the number of measurements increases over time, it can become very difficult for the user to identify the relevant data and perform the analysis.

SUMMARY

In one embodiment, a computerized system enables accessing one or more databases in substantially real-time to create and use a workflow template for analyzing data entities stored in the one or more databases. A workflow may be performed to generate one or more charts or visualizations based upon a received selection of one or more series, data sources, and entities, and wherein data source is used to determine values of a series for a particular entity. A workflow template for a particular workflow may be used by a user to perform the workflow without having to specify the restrictions and/or configuration settings associated with the workflow each time the workflow is performed. Thus, the template allows the workflow to be performed without the user having to be familiar with the restrictions and configuration settings associated with the workflow.

In some embodiments, after a desired workflow is identified, one or more series, data source, and/or entity restrictions based upon the workflow are defined based at least in part upon one or more user inputs. In addition, one or more chart or visualization configuration settings based upon the workflow may also be defined. The restrictions and configuration options are saved as the workflow template. The workflow may then be performed by loading the saved workflow template, and based upon the defined restrictions of the saved template, receiving a selection of one or more series, data sources, and entities. One or more charts or visualizations may then be automatically generated and displayed based upon the defined configuration options of the saved template.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system that may be used to implement data entity analysis, in accordance with some embodiments.

FIG. 2 illustrates a flowchart of a process for comparing a potential entity with similar entities, in accordance with some embodiments.

FIGS. 3A-E illustrates user interfaces that may be used by a user to view and analyze the entities stored in the database, in accordance in some embodiments.

FIG. 4 illustrates a flowchart of a process for defining and using a baseline entity, in accordance with some embodiments.

FIG. 5 illustrates an interface that may be used to establish a baseline entity, in accordance with some embodiments.

FIG. 6 illustrates a flowchart of a process for generating one or more charts based upon selected series, data sources, and entities, in accordance with some embodiments.

FIGS. 7A-K illustrates a chart creation interface that may be presented to a user, in accordance with some embodiments.

FIG. 8 illustrates a flowchart of a process for defining a workflow template in accordance with some embodiments.

FIGS. 9A-B illustrates a chart creation interface being used with templates, in accordance in some embodiments.

FIG. 10 illustrates a computer system with which certain methods discussed herein may be implemented, according to one embodiment.

DETAILED DESCRIPTION

Overview

As described above, it can become very difficult for the user to identify relevant data and perform an analysis when a database includes a large amount of data. In some cases, the database may contain data from a plurality of sensors at least of a plurality of entities, such as geological formations, that are of interest to the user. The data may also include historical data relating to attributes of the entities (e.g., measurements collected by one or more sensors associated with the entity over time), and/or models generated to predict or forecast attributes of the entity.

For example, in some embodiments, a database may contain data relating to a plurality of geological formations or structures related to the drilling of oil, such as regions, fields, reservoirs, and/or wells. This data may be used by a user (e.g., a surveyor or analyst) to determine which regions, fields, reservoirs, and/or wells to develop or invest in, to analyze historical data, and/or to construct models to forecast future performance. As used herein, a “data entity” or “entity” describes any object or system for which data may be provided, such as from sensors. Example data entities include individual oil wells, groups of oil wells, oil platforms, geographic regions, reservoirs, fields, etc. Data entities may include other objects or systems unrelated to oil well development, such as electronic devices, landfills, robotics, mechanical systems, etc.

For example, the user may identify an entity corresponding to a particular geological formation (e.g., a potential reservoir), and assess the entity for one or more attributes or characteristics (e.g., suitability for future development and/or investment). In order to assess the selected entity, the entity may be compared with other entities (e.g., other reservoirs) having similar attributes or characteristics. In addition, in some embodiments, in response to a user selecting a baseline data entity (e.g., another oil reservoir or modeled oil reservoir), the system may rank a plurality of data entities based upon similarity to the baseline data entity, allowing the user to select and analyze the most relevant data entities.

In some embodiments, the user may also wish to view attribute time series for various fields, reservoirs, and/or other data entities, such as to compare performance of models with collected historical data, compare different models, and/or the like. In some embodiments, the user may select one or more series, data sources, and entities for chart creation, and specify chart configuration options controlling how the charts are to be displayed. In some embodiments, a template may be constructed based upon a selected chart creation workflow, allowing a user to perform the workflow without having to re-specify the configuration parameters associated with the workflow.

Accordingly, disclosed herein are various systems and methods for analyzing data entities and visualizing data entity series. While the present disclosure will refer primarily to the use case of analyzing oil fields/reservoirs, the systems and methods disclosed herein may be applied to other fields and use cases, such as mining, market research, financial investments, scientific studies, geographical surveys, and/or the like. For example, in other embodiments, entities may correspond to various types of geological structures or formations, markets, financial entities, people, events, and/or the like.

Description of the Figures

FIG. 1 illustrates a system that may be used for data entity analysis in accordance with some embodiments. The system comprises a user station 1000, an application server 1030, and a database 1040, which may communicate directly with each other or over a network (not shown).

The user station 1000 may correspond to any type of computing station that may be used to operate or interface with the applications in the system (e.g., applications on application server 1030). Examples of such user stations include for example, workstations, personal computers, or remote computing terminals. User stations may also include mobile devices, such as smartphones, tablets, or touchscreen devices. The user station 1000 comprises a display device 1012, such as a display monitor, for displaying a user interface to users at the user station. The user station 1000 also comprises one or more input devices 1014 for the user to provide operational control over the activities of the system, such as a mouse, keyboard, or touchscreen to manipulate a graphical user interface to generate user inputs (e.g., by manipulating a cursor or pointing object in the graphical user interface).

Application server 1030 may be used to run one or more modules or applications that can be accessed by a user at user station 1000, such as a user interface module 104 and a data analysis application 105.

Data analysis application 105 may comprise a software application accessible by the user at user station 1000 to perform a variety of operations on received data from database 1040 or another data source. In some embodiments, data analysis application 105 may be a web application that is accessed by the user at user station 1000 through an internet or web browser, such as Internet Explorer, Mozilla Firefox, or Google Chrome. Data analysis application 105 may contain data analysis tools to be used by the user to identify and select data entities for analysis and comparison, based upon data received from database 1040 and/or other data sources. For example, the user may select data entities based upon one or more filters based upon data entity attributes, and/or identify data entities that are similar to a baseline data entity. Data analysis application 105 may also contain chart creation tools to be used by the user to create one or more charts, graphs, and/or other visualizations based upon received data from database 1040 and/or other data sources.

User interface module 104 may comprise a module configured to generate a user interface that may be viewed and interacted with by a user at user station 1000, allowing the user to use the tools and modules contained within data analysis application 105.

Database 1040 may contain entity data 106, model data 107, and template data 108. Entity data 106 comprises data related to a plurality of data entities which, as described above, may correspond to any object or system for which data may be provided, such as from sensors. In some embodiments, entity data 106 may also comprise historical data associated with the data entities. Model data 107 may comprise one or more models. In some embodiments, models may be constructed and used to predict or forecast attributes associated with a data entity. Template data 108 may comprise one or more workflow templates. In some embodiments, workflow templates constructed based upon a selected workflow, allowing a user to perform the workflow without having to re-specify the configuration parameters associated with the workflow.

The database 1040 may be a Relational Database Management System (RDBMS) that stores the data as rows in relational tables. The term “database,” as used herein, may refer to an database (e.g., RDBMS or SQL database), or may refer to any other data structure, such as, for example a comma separated values (CSV), extensible markup language (XML), text (TXT) file, flat file, spreadsheet file, and/or any other widely used or proprietary format. While the database 1040 is shown as a distinct computing system, the database 1040 may operate on the same computing system as the application server 1030 and/or user station 1000. In some embodiments, database 1040 may correspond to multiple databases, and/or span multiple servers or computing devices.

In some embodiments, the data analysis application 105 may be used to allow a user to filter entities based upon attribute values, and compare the filtered entities. For example, entities may correspond to fields or reservoirs used in the oil or gas industries. A potential or prospective reservoir may be identified as a candidate for development or investment by an oil company. However, because investment in a new field or reservoir can be extremely expensive, often costing tens to hundreds of millions of dollars, it is important to be able to learn more about the potential field or reservoir, so that the investment may be made with confidence. One of the primary ways to learn about a new potential field or reservoir is to compare the field or reservoir with other fields or reservoirs that have similar characteristics. By examining other fields/reservoirs with similar characteristics that have been previously invested in, a more informed decision can be made as to whether to invest in the new potential field/reservoir. As noted above, although oil fields/reservoirs are used for purpose of example, these functions may be applied to use cases in a variety of other areas, such as market research, insurance investigations, financial investments, scientific studies, and/or the like.

FIG. 2 is a flowchart of a process for comparing a potential entity with similar entities, in accordance with some embodiments. In some embodiments, the process may be executed using the system illustrated in FIG. 1, such as by the user station 101 and/or the application server 102. Depending on the embodiment, the method of FIG. 2 may include fewer or additional blocks and/or the blocks may be performed in an order different than is illustrated.

At block 202, an entity for analysis is received, such as via a user input in a user interface provided to the user station 101. In some embodiments, the entity corresponds to a prospective or potential entity, such as a potential field or reservoir that an oil company is considering investing in or developing, a potential market that a manufacturer is considering entering, and/or the like.

At block 204, one or more attributes of the received entity are identified. For example, attributes of an entity corresponding to a potential reservoir may include reservoir depth, depositional environment, depletion mechanism, porosity, location, and/or the like. In some embodiments, the identified attributes are attributes that may be determined at relatively low cost.

At block 206, a database storing data regarding a plurality of entities is accessed. At block 208, one or more filters are provided by the user, such as via a user interface provided to the user station 101. In some embodiments, one or more of the filters may correspond directly to attribute value ranges, maximums, or minimums of the entity. For example, if the entity corresponding to a potential reservoir has a location attribute value of “United States,” a filter may be defined that filters for reservoirs also having a location attribute value of “United States.” In some embodiments, one or more of the filters may correspond to a range or category that encompasses or includes an attribute value of the entity. For example, if the potential reservoir has a depth of 1200 m, a filter may be defined that filters for reservoirs having a depth attribute value of between 1000 m and 1500 m. In some embodiments, one or more of the filters may correspond to values related to attribute value of the entity. For example, a filter may be defined that filters for reservoirs having a location attribute value that is located near the location value of the prospective reservoir.

In some embodiments, the filters may be determined automatically, or be based at least in part upon one or more user inputs. Once the filters are defined based upon the identified attributes of the prospective entity, the database entities may be filtered using the defined filters, in order to form one or more filtered entities.

FIG. 3A-E illustrates user interfaces that may be used by a user to view and analyze data associated with entities stored in the database, in accordance with some embodiments. In the illustrated interfaces, the entities and attribute types shown relate to oil fields and reservoirs. For example, as illustrated in FIG. 3A, the interface may contain a plurality of columns or display panels. For example, column 302 of the interface contains a list of entity attribute types (e.g., attribute types pertaining to oil fields and reservoirs, while column 304 of the interface contains a list of entities (e.g., oil fields and reservoirs), and column 306 of the interface contains information for a specific selected entity (e.g., a specific oil field or reservoir).

As illustrated in FIG. 3B, a user may use the attribute types shown in panel 302 to define filters to be used to filter the entities. For example, a user may specify a location filter (“U.S.”), a depletion mechanism filter (“waterflood”), a “depositional environment” filter (“turbidite”), and a “depth below mudline” filter (0-2000 m).

In some embodiments, when a user clicks on an attribute type (e.g., depositional environment), a drop-down menu 308 or other interface feature may appear that displays available attribute values that may be selected to be used as a filter. In some embodiments, the search box 310 may be displayed that allows the user to search the available attribute values. In some embodiments, a user may be able to select multiple values of an attribute to filter. For example, if the prospective reservoir has a location attribute of “France,” the user may click on a location attribute and select “France,” “Germany” (a neighboring country of France), and/or another location value.

In some embodiments, for attribute types that correspond to range filters (such as a “depth” attribute), when a user clicks on the attribute type, a visualization 312 such as a graph (e.g., a bar chart) may be displayed that shows a distribution of entities in the databases between the different ranges. One or more user controls may be displayed allowing the user to specify a range to be filtered. In some embodiments, as the user specifies a range, the graph may be visually updated to reflect the selected range (e.g., bars falling within the specified range are shaded). When the user has defined one or more filters at 302, entities that satisfy the filter conditions may be displayed in column 304.

Returning to FIG. 2, at block 210, one or more visualizations may be generated based upon the entities that satisfy the filters. For example, as illustrated in FIG. 3B, one or more visualizations may be displayed in display area 314. For example, the visualizations may include one or more graphs, such as a scatter plot. In some embodiments, the entity attributes to be used in generating the graphs may be preconfigured, or may be specified by a user. In some embodiments, the graphs may include one or more additional interface elements. For example, a benchmark curve 314 may be displayed that indicates desirable combinations of attributes, such that data points in the graph that fall on one side of the benchmark curve are considered to have a desirable attribute combination, while data points on the other side of the curve are considered to have an undesirable attribute combination.

In some embodiments, other types of visualizations, such as a comparison table comparing one or more attributes of the filtered entities, may be displayed.

In some embodiments, as illustrated in FIG. 3C, data points on visualization panel 310 may be selected or clicked on. For example, a user may wish to further analyze one or more particular entities, such as an entity below a benchmark curve in order to find out why that entity is below the benchmark. In some embodiments, clicking on a data point corresponding to an entity may cause a text box 316 or other interface element to be displayed, which may contain the name of the entity, as well as information pertaining to the entity (e.g., the plotted attribute values of the entity). In addition, an action may be performed in response to a click on a displayed text box 316, such as selecting the entity in column 304, and/or displaying a full information page for the selected entity (e.g., as illustrated in display area 306 in FIG. 3A).

As illustrated in FIG. 3D, one or more entities in column 304 may be selected. When one or more entities have been selected, a toolbar 318 may be displayed indicating that entities have been selected. The toolbar 318 may contain one or more interface elements (e.g., buttons) corresponding to actions that may be taken on the selected entities. For example, by clicking on a table button 320, a comparison table is generated using the selected entities. In addition, in some embodiments, a visualization displayed at 306 may be updated in response to a selection of entities at 304 (e.g., a graph may be updated to only include the selected entities).

FIG. 3E illustrates a comparison table that may be generated based on data associated with one or more selected entities. The comparison table allows the user to compare multiple attributes of one or more selected entities. For example, through the use of a comparison table, the user may be able to better assess and determine the most relevant attributes for achieving a desired performance.

Baseline Entities

In many instances, a large number of entities may be returned to the user, even after applying one or more filters. While a chart having a large number of data points may be easy to read, a user may wish to more closely examine a smaller number of entities in greater detail. For example, a user may wish to view a comparison table between different entities, so that they can more easily compare a large number of different attributes between the entities. However, some types of visualizations, such as comparison tables, may be difficult to read if the number of entities in the table is too large. Thus, the user may wish to be able to first select the most relevant entities before constructing a table. However, when there are a large number of entities, which entities are the most relevant may be difficult to ascertain.

In order to find and select the most relevant entities, a user may first establish an entity to serve as a comparison baseline. The remaining entities may then be ranked based upon their similarity to the baseline entity, allowing the user to select the entities deemed to be most relevant for more detailed comparison. For example, a baseline entity may correspond to a well or reservoir having desirable attributes. In some embodiments, the baseline entity can correspond to an actual entity (e.g., an existing well/reservoir), or may correspond to a hypothetical entity having hypothetical or user-defined characteristics. In some embodiments, the baseline entity may correspond to a potential or prospective entity (e.g., a potential reservoir being assessed for future development or investment), in order to identify the entities that are most similar to the potential entity.

FIG. 4 illustrates a flowchart of a process for defining and using a baseline entity in accordance with some embodiments. In some embodiments, the process may be executed using the system illustrated in FIG. 1, such as by the user station 1000 and/or the application server 1030. Depending on the embodiment, the method of FIG. 4 may include fewer or additional blocks and/or the blocks may be performed in an order different than is illustrated.

At block 402, a selection of a baseline entity is received. In some embodiments, selecting a baseline entity comprises a user viewing or searching a list of existing entities, and selecting an entity with desirable attributes to serve as a baseline entity. In some embodiments, the baseline entity may be a fictional or hypothetical entity having attributes deemed desirable by the user. In some embodiments, a fictional or hypothetical entity may be created by a user using a user interface to enter one or more attributes. In some embodiments, a user may select more than one existing entity, and a hypothetical baseline entity may be created based upon the plurality of selected entities (e.g., a hypothetical entity with attribute values that are aggregated or averaged from the attribute values of the selected entities).

At block 404, entities are ranked based upon their similarity to the baseline entity. The entities may comprise all available entities in the database, or may be restricted to entities that satisfy one or more filters. In some embodiments, the entities are ranked by calculating a quantity (also may be referred to as a “similarity score”) for each entity, based on how similar the entity is to the baseline entity, and then ranking the entities by their similarity scores.

A variety of methods may be used to calculate a similarity score for an entity. For example, in one embodiment, the similarity score between an entity and the baseline entity may be calculated by computing a difference between corresponding attributes of the entity and the baseline entity, and aggregating the differences as a weighted sum. For example, in some embodiments the following formula may be used:

$\mathrm{Similarity}\mathrm{Score}=\sum _{i=1}^n{w}_i{\mathrm{attribute}}_{i,\mathrm{baseline}}-{\mathrm{attribute}}_i$ wherein the entity and the baseline entity are compared based upon n attributes, and each attribute is associated with a weight w. In the above formula, |attribute_i,baseline−attributed_i| denotes a difference between an attribute value of the baseline entity and the corresponding attribute value of the entity being compared. In some embodiments, this may comprise subtraction for attributes values that can be expressed quantitatively. However, in some embodiments, certain attributes are not expressed quantitatively. In such cases, quantitative scores may be assigned to attribute values based upon whether they are the same or different from the baseline attribute. For example, for a “color” attribute, a score of 0 may be assigned if the color attributes are the same, and a score 1 is assigned if they are different. In some embodiments, quantitative scores may be based at least in part on different degrees of similarity between the attribute value of the baseline entity and those of the entities being ranked (e.g., red and orange may be considered to have a small difference, and have a score of ½, while red and blue may be considered to have a large difference, and have a score of 1).

The above formula is provided for purpose of example, and that in various embodiments, any type of formula or methodology may be used to calculate a similarity score and/or rank the entities based upon a level of similarity or difference from the baseline entity.

At block 406, once the entities have been ranked (e.g., sorted by similarity scores), a selection of one or more entities is received. In some embodiments, this may comprise a user selecting a top n entities from the ranked entities, corresponding to the n entities determined to be most similar to the baseline entity. In some embodiments, the user may specify a desired number of entities and/or a threshold similarity score, whereupon the entities that meet those criteria will be automatically selected.

At block 408, one or more visualizations may be generated based upon the selected entities. For example, the visualization may comprise a comparison table constructed based upon the selected entities (e.g., as illustrated in FIG. 3E).

FIG. 5 illustrates an interface that may be used to establish a baseline entity in accordance with some embodiments. Similar to the interface shown in FIG. 3A, the interface may be divided into a plurality of columns or display areas. The interface may contain a display area 502 that contains a button 508 or other interface element allowing a user to set a baseline entity. For example, upon clicking the button the user may be shown an interface where they may specify a baseline entity (e.g., by selecting an entity from a list of existing entities, defining one or more attributes for a hypothetical baseline entity, and/or the like). Display area 502 may also comprise controls 510 for configuring one or more filters.

If a baseline entity has been selected, it may be displayed at 512 of display area 504. One or more entities may be displayed below the baseline entity, and ranked based upon their similarity to the baseline entity. The displayed entities may correspond to entities that satisfy the one or more filters shown in display area 502.

Display area 506 may be used to display detailed information on a selected entity (e.g., an entity listed in display area 504). In some embodiments, display area 506 may also be used to display visualizations associated with a plurality of entities, such as a chart or a comparison table.

Chart Creation

In some embodiments, entities may be associated with one or more series (may also be referred to as “data series”). In some embodiments, a series may indicate values of an attribute over time or over a particular time period. For example, an entity corresponding to a well or reservoir may be associated with an oil production rate series that plots an oil production rate value in relation to time. In some embodiments, a series associated with an entity may correspond to any attribute of the entity that may be measured over time, such as temperature, price, revenue, and/or the like. For the purposes of the present specification, use of the term “series” may generally refer to a time series that indicates values of a selected attribute of an entity (e.g., temperature, price, revenue, and/or the like) in relation to time. For example, a temperature series may indicate values of a temperature attribute over time. However, in other embodiments, the term “series” may also be used to refer to other types of series that plot attribute values of an entity in relation to an attribute or measurement other than time.

In some embodiments, values of a series for an entity may be determined through one or more different data sources. For example, historical data may be recorded for an entity (e.g., using one or more sensors, monitors, and/or the like) indicating the value of an attribute series at various times in the past. In addition, one or more models may be constructed to model past, present, and/or future values of an attribute series. In some embodiments, the models may be based at least in part upon recorded historical data.

For example, a reservoir entity may be associated with an oil production rate series. The actual oil production rate of the reservoir can be measured over time to produce historical data. In addition, an analyst (and/or automated machine learning software) may construct a model of the reservoir that can be used to compute or predict an oil production rate for the reservoir for any given time. In some embodiments, different models may be constructed based upon assumptions of different conditions. For example, a first model may be constructed that predicts the oil production rate of the reservoir should a new investment of $10 million be received, while a second model may be constructed that predicts the oil production rate with the assumption that no new investment occurs.

A user may wish to be able to generate one or more time series charts based upon series, data sources, and entities. For example, charts may be constructing allowing a user to compare a series over time between different entities, compare a series as determined by different data sources, and/or the like.

Although the present disclosure will refer primarily to time series charts for purposes of example, in other embodiments other types of charts may be constructed. For example, in some embodiments charts may be generated with x-axis attributes other than time. These attributes may include location, temperature, cumulative oil production, cumulative voidage, and/or the like. In some embodiments, charts having an x-axis other than time may be referred to as “cross-plots.”

FIG. 6 illustrates a flowchart of a process for generating one or more charts based upon selected series, data sources, and entities, in accordance with some embodiments. In some embodiments, the process may be executed using the system illustrated in FIG. 1, such as by the user station 101 and/or the application server 102. Depending on the embodiment, the method of FIG. 6 may include fewer or additional blocks and/or the blocks may be performed in an order different than is illustrated. FIGS. 7A-I illustrates screens of a chart creation interface that may be presented to a user, in accordance with some embodiments. Description of FIGS. 7A-I is included below alongside discussion of FIG. 6 to illustrate one example of the method.

At block 602, a workflow template may be selected. The workflow template may correspond to a commonly performed workflow. In some embodiments, a “basic template” may be available for performing workflows that do not have their own corresponding template. As illustrated in FIG. 7A, the user has selected the “Basic Template.” The interface may comprise a plurality of columns or display areas. For example, display area 702 may contain one or more interface elements that can be used by a user to define series, data sources, and/or entities to be used in the creation of one or more charts, which may be displayed in display area 704

At block 604, a selection of one or more series is received. A series may correspond to any attribute associated with an entity that varies over time, such as oil production rate, gross profits, temperature, rainfall, customer satisfaction, and/or the like. In the context of oil wells and reservoirs, series may correspond to gas, oil, and/or water saturation measures; gas and/or water injection measures (e.g., injection rate, cumulative injection); oil, gas, water, and/or condensate production measures; pressure measures (e.g., drawdown pressure, bottom hole pressure); gas/oil ratio, and/or the like. In some embodiments, a series corresponds to data that may be received as direct readings from a sensor or derived data based on information from one or more sensors. FIG. 7B illustrates an interface where a user may select series to be used in the creation of charts, in accordance with some embodiments. In some embodiments, in response to a user action (e.g., clicking on a button or interface element associated with “Series” in display area 702), a menu 706 or other interface element may be displayed showing series that are available to be selected. In addition, the user may be presented with a search bar allowing the user to search through the displayed attributes. In some embodiments, the interface may contain an interface element such as an “Add” button 708 allowing a user to add additional series for chart creation.

At block 606, a selection of one or more data sources is received. In some embodiments, data sources may comprise historical data. Historical data may be received based upon readings from one or more sensors operating over a period of time. For example, a temperature sensor may be used to generate historical data for a temperature series of a region entity. Historical data may also be received through other means, such as data derived through readings from one or more sensors, periodic observation logs, data retrieved from a database (e.g., price data), and/or the like. Types of sensors that may be used may include temperature sensors, pressure sensors, depth sensors, oil/gas rating sensors (e.g., to measure a quality rating of extracted oil or gas), liquid volume sensors (e.g., to measure a volume of extracted oil), water level sensors, and/or the like.

In addition, data sources may also comprise data computed using one or more models. Models may be constructed by analysts in order to predict future series behavior (e.g., future oil production quantity, future price trends, and/or the like). In some embodiments, models may be based upon previously received historical data. For example, a model may be generated based upon historical pressure or flow rate data for a region entity, in order to predict future pressures or flow rate.

In some embodiments, models may correspond to specific entities. However, models may also be used that can be applied to multiple entities, all entities of a certain type, and/or the like. In some embodiments, models may correspond to specific series, or be able to compute multiple different series.

FIG. 7C illustrates an interface where a user may select data sources to be used in the creation of charts, in accordance with some embodiments. Similar to the interface illustrated in FIG. 7A, the user may be presented with a menu showing available data sources that may be selected. In some embodiments, the menu may contain a search bar allowing the user to search through the displayed data sources. The menu may also contain a button or other interface element 710 allowing the user to restrict the displayed data sources to historical data or models. In some embodiments, the displayed models and/or historical data sources may be based at least in part upon the selected series. In some embodiments, the interface may contain an interface element such as an “Add” button allowing a user to add additional data sources for chart creation.

At block 608, a selection of one or more entities may be received. In some embodiments, the one or more entities may correspond to one or more entities selected based upon a prospective entity and/or a baseline entity (e.g., entities similar to the baseline entity). FIG. 7D illustrates an interface where a user may select entities to be used in the creation of charts, in accordance with some embodiments. Similar to interfaces illustrated in FIGS. 7B and 7C, the interface may contain a menu 706 showing available entities that may be selected. In some embodiments, the menu may contain a search bar allowing the user to search through the displayed entities. In some embodiments, the interface may contain an interface element such as an “Add” button allowing a user to add additional entities for chart creation.

In some embodiments, multiple types of entities may be available for selection. For example, in the context of oil production, entities may include fields, reservoirs, regions, region groups, wells, and/or well groups. In some embodiments, some entities may be aggregates of one or more other entities. For example, a region group entity may be an aggregate of a plurality of different region entities, such that a series value for the region group entity (e.g., oil production) may be an aggregate of the corresponding series values of the region entities that comprise it. The menu may contain a button or other interface element 712 allowing the user to restrict the displayed entities to those of a particular type or category.

At block 610, one or more charts are generated based upon the received series, data sources, and entities. In some embodiments, the created charts may be based upon the number of series, data sources, and/or entities selected. For example, in some embodiments, one chart may be created for each series, data source, entity combination. In some embodiments, one or more of these charts may be combined or overlaid on top of each other for easier comparison. An interface may be presented to the user, allowing the user to specify which charts to create and how they are to be combined or overlaid.

In some embodiments, additional charts relating to how the different series, data sources, and entities relate to each other may also be created. For example, a user wishing to compare how two data sources (e.g., two different models) compare may wish to view a graph showing a difference between values of series using one data source, and the values of the series using the other data source. In some embodiments, an interface may be presented to the user allowing them specify what types of additional graphs to create.

FIG. 7E illustrates an interface containing a chart that may be generated in response to a user selecting a series, data source, and entity. The chart 714 plots values for the series (“Production Rate Oil”) corresponding to the selected entity, as determined by the selected data source.

In some embodiments, the interface may contain one or more controls specifying how the charts are to be displayed. For example, the interface may contain one or more controls 716 allow a user to separate the charts based upon series, data source, and/or entity.

FIG. 7F illustrates an interface where a user has selected two series, one data source, and one entity. In addition, the user has selected to separate the charts by data series. As a result, two charts are produced and displayed, one corresponding to a first selected series (“Cumulative Production Gas”), and another corresponding to a second selected series (“Production Rate Oil”).

FIG. 7G illustrates an interface where a user has selected two series, one data source, and two entities. In addition, the user has specified that the charts are to be separated by series, resulting in two charts, a first chart showing the “Cumulative Production Gas” series for each of the selected entities, and a second chart showing the “Production Rate Oil” series for each of the selected entities.

FIG. 7H illustrates an interface where a user has specified that the charts are to be separated by entity. As a result, two charts are produced, which include a first chart corresponding to a first selected entity, and a second chart corresponding to a second selected entity, wherein in each chart the “Cumulative Production Gas” series and “Production Rate Oil” series are overlaid on top of each other.

FIG. 7I illustrates an interface where a user has chosen to not separate the charts by series, data source, or entity. As a result, only a single chart has been displayed, showing the two series for each of the two selected entities all overlaid on each other.

FIG. 7J illustrates an interface where a user has selected two series, two data sources, and two entities. In the illustrated example, the two data sources comprise a historical data source and a model data source. The charts are separated by entity such that two charts are displayed: a first chart showing the two data series for each data source (historical and model) for the first selected entity, and a second chart showing two data series for each data source (historical and model) for the second selected entity. For example, the first chart contains the historical oil production rate, model oil production rate, historical cumulative gas production, and model cumulative gas production for the first entity.

FIG. 7K illustrates an interface where a user has selected one series, two data source, and two entities, and has selected that the charts be separated by entity. As a result, two charts are created, a first chart showing the series value as computed by the two data sources for the first entity, and a second chart showing the series value as computed by the two data sources for the second entity. In the illustrated example, the two data sources comprise a historical data source and a model data source. As can be seen in the generated charts, the model data source series (shown as a line graph) follows the historical data source series (shown as a scatter plot) closely until a certain point in time, whereupon the model data source begins to diverge from the historical data. This may indicate the date when the model was first produced, as the model may have been constructed to adhere closely to the historical data that was recorded before its creation, but may not always be able to accurately predict the value of the series after the model has been created. In addition, after a certain point in time, the scatter point corresponding to the historical data source stops, while the line graph corresponding to the model continues to predict future series values. By plotting a historical data source and a model data source on the same chart, the effectiveness of the model may thus be assessed by the user.

Workflow Templates

While being able to select any number of series, data sources, and/or entities may allow for a user to generate many different combinations of charts and visualizations, in some cases, the number of options available may be overwhelming or inconvenient for a user who only needs to perform a limited number of different tasks. There may be specific workflows that are frequently executed that make use of specific configuration options, and it may be desirable to be able to execute those workflows without having to configure those options each time the workflow is to be executed.

For example, a commonly used workflow may be one that compares two different data sources. A user may wish to compare a historical data source with a model data source, in order to assess how well the model is performing. Alternatively, the user may desire to compare two different models to see how they differ. In some embodiments, a model may be constructed based on the assumption of an occurrence of a particular event or condition. Different models may be compared in order to forecast how a series may change based upon whether or not the event or condition is fulfilled.

In some embodiments, templates corresponding to particular workflows may be defined and saved. By loading a saved template, configuration options associated with the workflow may be automatically set, saving time and also allowing users who may be unfamiliar with the configuration options to execute the workflow.

FIG. 8 illustrates a flowchart of a process for defining a workflow template in accordance with some embodiments. In some embodiments, the process may be executed using the system illustrated in FIG. 1, such as by the user station 101 and/or the application server 102. Depending on the embodiment, the method of FIG. 8 may include fewer or additional blocks and/or the blocks may be performed in an order different than is illustrated.

At block 802, a workflow for which a template to be created is specified. The workflow may correspond to a workflow expected to be performed regularly, or have unique or seldom used configuration options. For example, a common workflow that may be performed may be a workflow to compare two different data sources (hereinafter also referred to as a “Profile Comparison” workflow). By creating a “Profile Comparison” template corresponding to the “Profile Comparison” workflow, a user will be able to perform the workflow by loading the template, without having to be familiar with the various configuration settings and options available in the application.

At block 804, one or more series restrictions, data source restrictions, and/or entity restrictions are defined. These restrictions may limit the number and/or type of series, data sources, and/or entities that may be selected in a particular workflow. For example, as described above, in some embodiments, a “basic template” may be used with any number of series, data sources, and/or entities. However, certain workflows may require a certain number of series, data sources, and/or entities. For example, a “Profile Comparison” workflow, used to compare two different data sources, may require the user to select two data sources. In addition, the user of the “Profile Comparison” workflow may only be able to select one series and one entity, so that the data sources being compared will be with reference to the same series and entity. As such, the “Profile Comparison” workflow may contain a series restriction restricting the number of selected series to one, an entity restriction restricting the number of selected entities to one, and a data source restriction restricting the number of selected data sources to two.

In some embodiments, restrictions may be placed on the types of series, data sources, and/or entities that can be selected (e.g., only model data sources, only reservoir entities, and/or the like). The restrictions may be defined based at least in part upon one or more user-specified criteria. The user may be presented with a user interface with which they may specify the criteria indicating restrictions associated with the workflow. For example, the user may wish to define a template for a workflow for comparing model data to historical data, and thus may define a data source restriction restricting the selected data sources to one historical data source and one model data source.

In some embodiments, at block 806, the user may also specify one or more configurations or restrictions regarding the charts that are generated. Certain charts or combinations of charts may be desired for certain workflows. For example, for a “Profile Comparison” workflow used to compare two different data sources, it would be useful to have a chart that plots a series for the different data sources, as well as a chart that plots a computed difference between the different data source series. By setting a configuration (e.g., a chart configuration specifying a first chart plotting a series for the first selected data source, a second chart plotting a series for the second selected data source, and a third chart plotting a difference between the first and second data sources), these charts may be automatically created once the user has specified the desired series, data sources, and entity, without the user having to set additional configuration settings or perform additional manipulations. At block 808, the workflow template is saved, allowing it to be later loaded and the workflow associated with the template to be performed by a user.

In some embodiments, the restrictions and configurations may be defined based upon one or more inputs from a user. The user may be different from a user who later performs the workflow (e.g., using the process illustrated in FIG. 6). For example the user from which the inputs are received may be an administrator or other personnel who is familiar with the restrictions and configuration settings associated with the workflow, while the user who performs the workflow does not have to be familiar with the settings and restrictions.

FIG. 9A illustrates a template selection interface that may be used in accordance in some embodiments. When a user launches the chart creation tool or application, they may first select a template that they wish to use. For example, they may select the “Profile Comparisons” template in order to perform a workflow for comparing two different data sources. On the other hand, if there does not exist a specialized template associated with the workflow that the user wishes to perform, a “Basic Template” may be selected.

FIG. 9B illustrates an interface using a “Profile Comparisons” template, in accordance with some embodiments. As described above, the “Profile Comparisons” template may be used to compare two different data sources (e.g., models and/or historical data). In some embodiments, the data sources may comprise a historical data source and a model data source, allowing the user to assess how well the model has been performing compared to the actual recorded data. Alternatively, two different model data sources may be selected, allowing the user to assess how the models perform relative to each other. In some embodiments, different models may be constructed based upon an assumption that some event or condition has occurred (e.g., if an additional investment is made, if a particular advertising campaign is adopted, and/or the like). For example, a first model may be constructed based upon an assumption of a first event or condition, while a second model may be constructed based on an assumption of a different event or condition. By comparing the two models, the user may be able to determine how the series will be expected to behave in different “what if” scenarios.

As illustrated at display area 902, the user is only able to select a single series, two different data sources, and a single entity. Upon the user having selected the desired series, entity, and data sources, two charts are created in display area 904, a first chart that plots the two data source series for the selected entity against each other, and a second chart that plots the difference between the two data source series. Thus, a user will be able to easily assess how the data sources compare and are different from each other.

Implementation Mechanisms

According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.

Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.

For example, FIG. 10 is a block diagram that illustrates a computer system 1000 upon which an embodiment may be implemented. For example, any of the computing devices discussed herein may include some or all of the components and/or functionality of the computer system 1000.

Computer system 1000 includes a bus 1002 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 1004 coupled with bus 1002 for processing information. Hardware processor(s) 1004 may be, for example, one or more general purpose microprocessors.

Computer system 1000 also includes a main memory 1006, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 1002 for storing information and instructions to be executed by processor 1004. Main memory 1006 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1004. Such instructions, when stored in storage media accessible to processor 1004, render computer system 1000 into a special-purpose machine that is customized to perform the operations specified in the instructions. Main memory 1006 may also store cached data, such as zoom levels and maximum and minimum sensor values at each zoom level.

Computer system 1000 further includes a read only memory (ROM) 1008 or other static storage device coupled to bus 1002 for storing static information and instructions for processor 1004. A storage device 1010, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 1002 for storing information and instructions. For example, the storage device 1010 may store measurement data obtained from a plurality of sensors.

Computer system 1000 may be coupled via bus 1002 to a display 1012, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. For example, the display 1012 can be used to display any of the user interfaces described herein with respect to FIGS. 1A through 8. An input device 1014, including alphanumeric and other keys, is coupled to bus 1002 for communicating information and command selections to processor 1004. Another type of user input device is cursor control 1016, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 1004 and for controlling cursor movement on display 1012. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.

Computing system 1000 may include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage

Computer system 1000 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 1000 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 1000 in response to processor(s) 1004 executing one or more sequences of one or more instructions contained in main memory 1006. Such instructions may be read into main memory 1006 from another storage medium, such as storage device 1010. Execution of the sequences of instructions contained in main memory 1006 causes processor(s) 1004 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 1010. Volatile media includes dynamic memory, such as main memory 1006. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between non-transitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 1002. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 1004 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 1000 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 1002. Bus 1002 carries the data to main memory 406, from which processor 1004 retrieves and executes the instructions. The instructions received by main memory 1006 may retrieve and execute the instructions. The instructions received by main memory 1006 may optionally be stored on storage device 1010 either before or after execution by processor 1004.

Computer system 1000 also includes a communication interface 1018 coupled to bus 1002. Communication interface 1018 provides a two-way data communication coupling to a network link 1020 that is connected to a local network 1022. For example, communication interface 1018 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 1018 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 1018 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 1020 typically provides data communication through one or more networks to other data devices. For example, network link 1020 may provide a connection through local network 1022 to a host computer 1024 or to data equipment operated by an Internet Service Provider (ISP) 1026. ISP 1026 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 1028. Local network 1022 and Internet 1028 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 1020 and through communication interface 1018, which carry the digital data to and from computer system 1000, are example forms of transmission media.

Computer system 1000 can send messages and receive data, including program code, through the network(s), network link 1020 and communication interface 1018. In the Internet example, a server 1030 might transmit a requested code for an application program through Internet 1028, ISP 1026, local network 1022 and/or communication interface 1018. In addition, a database 1040 may be accessed by computer system and/or server 1030 through Internet 1028, ISP 1026, local network 1022 and/or communication interface 1018.

The received code may be executed by processor 1004 as it is received, and/or stored in storage device 1010, or other non-volatile storage for later execution.

Terminology

Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry.

The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.

Claims

1. A computing system configured to create a template by a template creator for a workflow chart template, wherein the workflow chart template can be used by a template user to automatically generate one or more workflow charts based on analysis of attributes values of sensors associated with a plurality of entities, each entity generating attribute values of sensors over time, the computing system comprising: a computer processor;one or more databases storing data generated by the plurality of entities, the data comprising sensor data generated by the entities by sensors located at each entity for collecting the sensor data, the sensor data comprising: a plurality of time series, each time series comprising values of an attribute over time, wherein the attribute values indicate characteristics or features of the entity and are measured by the sensors, wherein each of the attribute values are measured by one or more sensors, each of the time series configured to be plotted on workflow charts with the Y axis indicating the attribute values of the times series and the X axis indicating time;wherein each of the time series is associated with one or more of a plurality of data sources, the plurality of data sources including: one or more historical data sources of actual sensor data measured at each entity; andone or more modeled data source comprising modeled attribute values generated by one or more models for modeling time series data; anda computer readable storage medium storing program instructions configured for execution by the computer processor in order to cause the computing system to:create a workflow chart template based on input from the template creator and usable by the template user to automatically create a plurality of workflow charts, each workflow chart indicating attribute values of at least one time series, wherein the workflow chart template is configured responsive to selections of criteria by the template creator, wherein the criteria comprise attributes, configuration settings and data restrictions including one or more of: time series selectable by the template user;data sources selectable by the template user; andentities selectable by the template user;wherein the workflow chart template is configured to receive selections of one or more time series, data sources, and entities from the template user in accordance with the criteria of the workflow chart template, wherein the selections of one or more entities comprises selection of a baseline comparison entity, one or more actual entities other than the baseline comparison entity, or one or more prospective hypothetical entities;wherein the workflow chart template is configured to further receive from the template creator indications of how time series selected by the template user are to be combined in generated workflow charts, wherein the workflow chart template is configured to, in response to a first selection from the template creator, automatically cause generation of each of the time series selections on the Y axis and to plot time on the X axis on a single workflow charts, wherein the workflow chart template is configured to automatically plot on the Y axis each of the attribute values measured by the one or more sensors associated with the time series selections over a time period plotted on the X axis;in response to a second selection from the template creator, automatically cause multiple workflow charts to be separated by time series such that when the template user selects a first time series and a second time series, a first workflow chart plots the first time series on a first Y axis and time on a first X axis, and a second workflow chart plots the second time series on a second Y axis and time on the second X axis;in response to a third selection from the template creator, automatically cause multiple workflow charts to be separated by entity such that when the template user selects a first entity and a second entity, a first workflow chart plots one or more time series selections associated with the first entity on a first Y axis and time on a first X axis, and one or more time series selections associated with the second entity on a second Y axis and time on the second X axis; save the workflow chart template; and

2. The computing system of claim 1, wherein the plurality of entities correspond to a plurality of geological structures.

3. The computing system of claim 1, wherein the one or more modeled data sources are constructed based at least in part upon attribute values of sensors indicated in one or more of the historical data source.

4. The computing system of claim 1, wherein the workflow chart creation further comprises selecting one or more entities based at least in part upon similarity to a baseline entity selected by the template user.

5. The computing system of claim 4, wherein a similarity of an entity to the baseline entity is determined based at least in part upon a calculated similarity score, the similarity score being calculated as a weighted average.

6. The computing system of claim 1, wherein criteria received from the template creator indicate one or more restrictions on a number of series, number of data sources, or number of entities that can be received by the template user.