JP2016538643A - Industrial process simulation - Google Patents

Abstract

A method for simulating an industrial process is disclosed. This method can be applied to the simulation of hydrocarbon and petrochemical processes. The method includes generating and storing a simulation workflow that includes a plurality of rules that specify processing operations associated with simulation inputs, operations, or outputs. Process information defining an industrial process for simulation is received. The process information specifies a process topology including process components and connections between process components and associated process parameters. The simulation workflow is executed, which involves applying specified rules. For at least one of the rules, applying the rule includes modifying the received process information based on the rule for changing the process topology and / or parameters. The process simulator is called to execute a computer simulation of the industrial process based on the corrected process information, and simulation result data based on the executed simulation is generated. [Selection figure] None

Description

  The present invention relates to methods and apparatus for industrial process simulation, particularly for hydrocarbon processing including oil and gas processing and production, refining, and petrochemical processing.

  Industrial processes such as chemical product manufacture and hydrocarbon purification are complex processes with many variables that affect the quality and output of the final product as well as the efficiency and reliability of the process itself. In order to make such processes commercially viable, these processes are generally performed on a very large scale. For this reason, it is often impractical to perform a test process to determine optimal conditions. Furthermore, physical testing of various scenarios would be impractical, risking damage to equipment and presenting safety risks to the operator.

  The present invention seeks to ameliorate the above problems by using industrial process simulation.

  Embodiments of the present invention simulate industrial processes that allow engineers to determine optimal configuration settings based on rules and / or a given set of conditions without physically performing experiments. Provide a way. The output of the simulation results can assist the engineer in selecting the type of equipment to use in the design and operating conditions for that equipment. Further capabilities that allow engineers to predict for known future effects (such as well depletion or equipment performance degradation) that may alter engineering decisions based purely on the current situation Sex is revealed.

  The disclosed approach allows engineers to create certain metrics associated with industrial processes with certain selected process conditions and design characteristics, resulting in a variety of real-world locations at the appropriate location. It is possible to operate the process in an optimally efficient, reliable and safe manner, given the limitations of

  In a first aspect of the invention, a computer-implemented method for simulating an industrial process is provided. This method creates and stores a simulation workflow that contains multiple rules that specify the processing behavior associated with the input to the simulation or the execution or output of the simulation, and defines the industrial process for the simulation. Process information, wherein the process information specifies a process topology including a connection between a process component (eg, equipment) and a process parameter associated with the process component, and simulation Executing a workflow, the execution including applying the specified rule, and applying the rule for at least one of the rules, the received process information, Process Including modifying the rules and / or parameters based on rules to invoke the process simulator to perform a computer simulation of the industrial process based on the modified process information; The method further includes generating and outputting simulation result data based on the executed simulation.

  In a further aspect, the present invention provides a computer-implemented method for simulating industrial processes. The method receives process information defining an industrial process for simulation, wherein the process information specifies a process topology including a connection between a process component and a process parameter associated with the process component. And creating and storing at least one rule defining a time-dependent characteristic of the process information, wherein the rule sets a time step size according to a change in the time-dependent characteristic. Simulating a process based on the received process information under a specification and a change in a time-dependent characteristic of the process information, wherein the simulation is defined by the rules Due to the unusual time-dependent characteristics, the specified time For each of a plurality of time steps, based on the step size, including, and performing process simulator to simulate industrial processes based on the received process information.

  In a further aspect, the present invention provides a computer-implemented method for simulating industrial processes. The method includes receiving process information defining a process for simulation, simulating a process based on the received process information, and selecting first and second flow portions of the simulated process. And a phase analysis selection, performing a selected phase analysis for the first selected process flow portion, and performing a selected phase analysis for the second selected process flow portion And outputting a comparison of the phase analysis results derived from the first and second process flow portions.

  A further aspect is a system or apparatus having means (eg, in the form of at least one software module and / or appropriately programmed processor) for performing all the methods described herein, and described herein at runtime. A computer program product or a non-transitory computer readable medium containing software code configured to perform any method is provided.

  Preferred features are set forth in the appended claims. Some additional aspects and features of the invention are described at the end of this specification.

  Any device feature as described herein may also be provided as a method feature, and vice versa. As used herein, means plus function features may alternatively be expressed in terms of their corresponding structure, such as a memory associated with an appropriately programmed processor.

  Any feature in one aspect of the invention may be applied to other aspects of the invention in any suitable combination. In particular, method features can be applied to device features and vice versa. Further, any and / or some and / or all functions in one aspect, any and / or some and / or any feature in any other aspect, any It can be applied in any appropriate combination.

  It should also be understood that the specific combinations of the various features described and defined in any aspect of the invention can be independently implemented and / or provided and / or used. is there.

  In addition, functions implemented in hardware may generally be implemented in software and vice versa. Any reference to software and hardware features herein should be understood accordingly.

  These and other aspects of the invention will be apparent from the following exemplary embodiments, which are described with reference to the following drawings.

1 shows a system for a simulation process. An additional system is shown for the simulation process. Indicates an interface for workflow input. Shows the interface for setting the workflow. Shows a toolbar for the workflow. Shows the interface for workflow management. An example of workflow design is shown. The workflow of FIG. 7 is shown. An additional system is shown for the simulation process. An additional system is shown for the simulation process. Show toolbar for time series management. , Fig. 4 shows a scenario interface with examples of separate scenarios. A data recorder interface is shown. , , , Shows separate functions in the time series setup interface. , Describe alternative topography in the process and corresponding state in the scenario. Shows key performance indicator interface. An example of an accumulation setting tab is shown. Indicates an interface for net present value information. An additional system is shown for the simulation process. Shows a toolbar for laboratory analysis. , Two examples of the display of stream phase information are shown. , Two examples of phase envelope displays are shown. Input for analysis of solid formation.

  Process simulation for the hydrocarbon processing industry is used to design, evaluate and optimize processing equipment. Typical areas of application include upstream oil and gas production facilities, midstream gas processing, refining, and petrochemistry.

  Process simulation is used for the design, development, analysis, and optimization of industrial processes such as chemical factories, chemical processes, and power plants. Process simulation is a software based model-based representation of chemical, physical, biological, industrial and other technical processes, and unit operations. Process simulation is based on calculations in a computer based on information about the chemical and physical properties of the processing units, components and mixtures, reactions, and mathematical models.

As used herein, a case or model is a set of process information that defines the process being simulated. A flow sheet is a subset of process information that defines energy flow and mass flow. A flow sheet generally contains unknown elements to be determined by simulation. The result of the simulation is generally a fully implemented flow sheet. Flow sheets generally contain physical and chemical information associated with mass flow, such as mass flow rate, volume flow rate, molar flow rate, pressure, temperature, and synthesis. A topography (also referred to as a process flow diagram) is a subset of process information that defines a connection between a process component (equipment, processor, facility, or sub-group of facilities) and a process component. Topography typically includes information associated with process elements such as components, power consumption, and physical or chemical properties given by performance limits.
Workflow Simulation FIG. 1 shows a system 10 for facilitating simulation of industrial processes. The rule information 12 is input to define a workflow simulation 14 (also referred to as “workflow”). The rule information 12 may be input by a user or by external software, for example. Process information 16 is input to allow process simulator 18 to simulate a process based on process information 16. The process simulation executed by the process simulator 18 follows the workflow 14. Process simulation results 20 are produced under the application of rules. The actions taken by the workflow include, for example, changing process information before or after the simulation, reviewing process information before or after the simulation, running the simulation, changing the simulator, Can include producing. The workflow provides a rule-based framework within the framework where the simulation is manipulated by applying the rules to the simulation. By embedding the simulation within the workflow framework, a custom workflow can be added to the process simulation as a supplemental layer.

  The process simulation can also start (ie, trigger) a workflow based on the results of the simulation, for example. This is illustrated in FIG. 2 where a different system 30 for facilitating simulation of industrial processes is shown. Although the components are the same as in the system 10 described above, the workflow 14 is embedded in the process simulator 16.

  The workflow allows the user to define “rules” for application to the process simulator. For example, a rule defines a step or series of steps (connected or not connected) that shape the procedure applied to the simulation. Users can combine separate workflows together to form sophisticated custom layers or frameworks. The framework can exist outside of the process simulator (and its built-in simulation solver). The framework can apply logic to simulation models that can be reused and standardized.

  The use of workflows allows customization of simulation tools with best practices, design methods, and operational knowledge. This in turn allows the user of the simulation tool to create a process model of the facility that is a more accurate representation of the actual plant or design being built or modified. This can result in design savings, reduced operating expenses, and safety and avoidance of environmental disasters.

A workflow can be thought of as consisting of several distinct rules. Rules can be considered in terms of three basic parts.
1. 1. Input-information needed to complete a step Instructions / actions / algorithms / tasks / functions / procedures-executed (for example but not necessarily) by a process simulator.
3. Output-information converted or reported based on the input and the action / algorithm applied to the input.
Rules can be linked, grouped or chained together to create complex processes from simple processes. Not all of the three basic parts listed above need to be included to shape the rules.

The workflow may be as simple as:
1. Select a device, select a variable, and open a case.
2. Report on the selection.
Or 1. Select equipment.
2. Change the value.
3. Report on found equipment and what has changed.

  Rules can be combined to create an increasingly more complex process. In the extreme, the user can describe the entire “design basis” for complex processes such as oil and gas refinery operations or oil and gas offshore platform design and input / instruction / output It is possible to add sets.

  A workflow can produce information in a graphical format. A workflow can be executed as an application to run a process. A workflow can combine inputs from several sources. Such sources include running instances of simulation tools, historical data in simulation databases, data from other stand-alone applications such as analytical applications, data from spreadsheets, text documents, or third-party applications Not limited to them. The workflow system can be easily used by the user within the simulation tool to set the simulation model scenario. The workflow system can also be used from outside the simulation tool to run the simulator as a “black box”.

Examples of workflow simulation include:
Change the value in the flow sheet or change the topography in the flow sheet.
Apply the criteria to the case and re-run the simulation of the case (eg select all compressors and add standard power (eg an existing 3.56 MW compressor will match the settings that are actually available) To be changed to a 5 MW compressor to ensure that-for example, part of an industrial process facility can be designed and / or built based on the output of a simulation)).
Add cases from databases or third-party applications.
• Open several cases sequentially and have the same changes applied to each case and compare the results. This allows a comparison of multiple, very different designs.
Open some cases and some logic (eg master case calls one of three different available dew point units (separate cases) depending on the date) or other logic (processing Based on (capabilities) and execute them together (linked) together.
Allow cases from separate users to collaborate with each other under defined conditions.
The workflow can access historical data associated with the model (from past simulations and also from real past measurements) and perform their analysis.

  The workflow system is included in a “host” simulation case and can be displayed in other called cases. The workflow system can also be provided in an external programming interface for experienced programmers. The workflow can visually display the progress and status of the execution of the workflow. In any case, there may be multiple independent or dependent workflows.

  A separate sub-workflow can define alternative simulation cases generated by applying the workflow. Options are predefined or defined to the user in a self-contained workflow. Multiple sub-workflows can interact with each other in the workflow. An activity or task is a single step in the workflow. An activity may consist of obtaining data from a simulation database or calculating and reporting results from within a workflow or sub-workflow. An activity may be associated with a sub-workflow, or it may be a stand-alone workflow. An example of an activity is to compare the results of two options by workflow. Decisions can be made in a workflow where one or the other option can be selected, or a decision can be made to set a conditional variable on another variable, or to choose between two or more criteria. Logic within the activity. The decision can cause other activities in the workflow.

  A design criteria is a collection or library of workflows that creates design or operational criteria for a facility. The actor or user is a person or software / hardware system that interacts with the workflow. They can be builders or consumers. The actors can generate results without knowing the workflow with which they interact. The actor can generate results without using a simulation tool. A warning is a message triggered by a workflow to notify the user that something has happened. The alert can be stored for further analysis.

  Workflow increases the power and flexibility of process simulation and can provide a powerful system for design, evaluation and optimization. The system allows simple drag and drop workflow definitions and is designed to be as simple as possible for non-programmers users, but is sufficient to enable a person with programming skills to complete a powerful and complex workflow It is powerful. The workflow in the context of simulation software available to process engineers is similar to “Rules and Alerts” in Microsoft Outlook®. A user can group tasks or workflows or collections of tasks or workflows into a master workflow. This can be a simple single instruction or a set of complex conditional logic rules applied across a complete simulation model with multiple versions over a specific date range. This allows you to understand and use complex and powerful systems that can scale down to something simple.

  Rules can be tied together and complex workflows can be built from simple components in a fully user extensible manner. An example of a system for defining such a complex workflow, referred to as “designed workflow” will now be described. The designed workflow has one or more selection rules that result in a list of objects, zero or more filter rules that can modify the list of objects by deleting objects that do not meet the filter criteria, Has three parts of zero or more rules of operation that process the list. With the designed workflow, each selection or filter or rule of operation supports receiving and returning an object list as well as other input arguments created as needed by the workflow author and expected calls It can be a workflow created using a commercial workflow engine that supports signing. Further, each selection or filter or action rule may be a workflow implemented as a method in the process simulator and embedded in the process simulator itself. Further, each selection or filter or action rule may be a designed workflow already set up in the simulator or in a workflow library subscribed by the simulator. To ensure reliable operation, a check may be included that there is no designed workflow that includes itself. Designed workflows can be implemented with the support of additional applications, such as “Petro-SIM®”, thereby “hybrid” where functionality from multiple applications is integrated into a single user interface Create a mechanism.

  An example of a tool for workflow implementation will now be described in more detail. FIG. 3 shows an interface 32 for workflow input. In FIG. 3, a structured input of a workflow is possible by three panels of “Select” 36, “Filter” 38 and “Action” 40. The field “Applies To” 34 allows the type of object to be pre-selected and in the “Select” panel 36 a selection among available instances of that type of object can be made. The “Filter” panel 38 can define a condition, and the “Action” panel 40 can specify an action to be executed in response to a filter condition that is satisfied for the selection. Filtering and selecting can be viewed as applying various types of conditions. Within each panel, multiple items can be entered and combined. A “Trigger” field 42 is provided to specify what triggers the applied workflow.

  FIG. 4 shows an interface 44 for setting a workflow, and in the example described, one filter defines one condition. Parameters 46 for setting the workflow, such as user selection of variables and values, can be entered in the interface 44.

  FIG. 5 shows a toolbar 48 for the workflow. The toolbar provides different actions related to the workflow, designing a new workflow, importing an existing workflow, viewing all available workflows, creating a new library of workflows, Includes deleting, importing libraries (including grouped workflows), and joining libraries. Such subscription allows access to an externally provided and maintained library of workflows. Tools for performing the workflow are also provided.

  FIG. 6 shows an interface 44 for workflow management. In FIG. 4, two different workflows belong to the selected workflow library and are listed. Each of the available workflows can be enabled or disabled by tick box 46. Also, the connection point in the simulation to which the sub-workflow is applied is indicated by the “Trigger” field and can be modified. One selection of available workflows allows review of workflow details and modification of the workflow (if the user is authorized).

  FIG. 7 shows an example 56 of a workflow design created in Visual Studio 2010. The described example causes the compressor to assign a user-specified efficiency value depending on whether the power limit is exceeded. FIG. 8 shows the workflow of Example 56 above as provided to the user for user designation, power limits, and efficiency values for the compressor to which the workflow applies.

Several additional considerations are meaningful for creating a workflow within a programming interface. A workflow is designed to be general enough that it can be reused in many cases and in many applications. To facilitate interoperability, special argument types can be provided to pass unique simulator objects and values as arguments. Thereby, it is possible to define a workflow that can receive a dynamic argument from a simulation case. In addition, many predefined activities for normal workflow operations can be provided to facilitate workflow creation. When multiple copies are running, predefined activities are provided that return the instance of the simulator that launched the workflow or start a new instance of the simulator to control the simulator instance to which the workflow connects. Can.
Application examples and workflow features will now be described in more detail.

Engineering design standards workflow : Oil and gas operators have their own standard and recommended choices commonly known as “design standards”. Providers of engineering services to operators are also required to adhere to the operator's design standards. Design criteria can be, for example, using constant units of measurement, adding rules of thumb for equipment design, defining constant flowsheet topography, in certain standards, such as top fractionation column It can include applying speed limits, having certain steps that need to be addressed and checked. To ensure consistent compliance with design standards, the engineering design standards workflow can be fixed, shared and enforced by all team members of the project. Administrators can apply appropriate engineering design criteria workflows to cases associated with team members and specific projects. The workflow system allows default and independent variables and user-entered variables and dependent variables set (automatically) by the workflow, or the user's selection can be limited to certain options, or A warning can be generated if the user does not adhere to the design criteria.

Cross-enterprise standardization : Using a lockdown workflow for all team members of a project can ensure compliance with the standard. The workflow can ensure that, for example, only certain types of structural packing or only shell and tube heat exchangers can be used in the flowsheet.

Knowledge management : Users can add their own equations or logic to the flowsheet. As a result, it can be reused personally or in group settings by the mechanism of embedding in this workflow. For example, the user may know that the simulated values are generally too low, and that in reality and the facts that were present (on the plant), higher values are likely to be observed. The user can specify that the actual value is higher than the simulated value due to known factors, or that there is some + /-% uncertainty margin above and below the simulated value. The workflow can be run in the background that recognizes the variable and alerts the user about known activities.

Custom reports : Workflows can be provided with the ability to design custom reports that can change during operation as a function of the case itself. For example, for a flow sheet with many production streams, if a stream report is generated starting from the highest flow rate and the flow rates are all within a certain range, instead of the highest heating value, A report starting in sequence is created, and if any sulfur capacity value exceeds a certain limit, a report starting in sequence from the highest sulfur content is generated.

Specifying conditions : Users can easily add single or multiple conditional actions to the model. For example, if there are two gas processing trains and the inlet supply is cut off, the flow rate to each unit is reduced by a certain amount. Or, if the flow rate falls below the threshold, close one entire train and increase the other load. Conditions and actions can be easily written and assembled in a drag-and-drop fashion with access to all independent and dependent variables, default variables, and topographic variables in the flowsheet. Another example could be a workflow that adds more trays into the column or moves the column supply position for a constant supply until a certain minimum energy condition is found. Another workflow defines additional tray capital costs and energy operational costs, and allows the workflow to optimize the optimizer over many supply conditions to find the optimal column design based on what the user currently knows. It can be what is executed. A user can have many conditions and optimizations to design a flow sheet. As described above, these separate workflows can form engineering design criteria when collected.

Replenishment process calculation : The workflow is a simple way to add a replenishment process calculation, for example to get the calculated energy and increase it by 20% for known heat loss conditions. This can be advantageous for information that cannot be calculated or verified through simulation.

External data load / export : A common requirement is to load external data from an external system or export calculated data to an external system at some point in the model or after certain events That is. An example is a simulation tool that interacts with an engineering design database and loads data and instructions when there is a change in the design database.

Multivariable case study : Another common application is to design alternative case studies. The user completely defines the alternative (it can be anything, it can change from one alternative to the next or create the next from one alternative). The user defines a trigger for storing the results or things that will be stored, for example, only for storing a stream that has changed from one case to the next. The user can also specify that certain cases are opened and saved for examination.

Model revision, case management : The user can save and classify simulation results during any workflow execution, eg all models modeled in a workflow where compressor C1 exceeds 13.2MW within the required power You may want to save, remember, and maintain the case.

Decision maker : The user can specify a decision tree analysis that creates many alternatives to be compared with each other. For example, a user may specify a flow sheet with one large distillation column or two smaller ones on the same service, change many feed conditions, and between two at one level by a decision tree. Lets determine and select one (eg, a two-column design) and then work through that more activity under the decision tree for that particular design (eg, between two separate reboilers in two columns, Or decide between shared utility streams).

Alternative designs : Perhaps one of the most valuable and simplest workflows is to compare two or more alternative designs. For example, compressors come in two different sizes, 3MW and 5MW. The workflow applies two alternatives and provides the user with pre-selected characteristics of the models compared against each other. The user can save either alternative for later use and choose one as the basis for future work. The number of alternative designs can be quite large, and multiple changes can be made per alternative, for example, five compressors can be exchanged with a fixed size per alternative.

Private design : An alternative design extension is to let the workflow determine a certain design and continue based on criteria. For example, given two possible compressor sizes have the smallest average or standard deviation in% of (+/-) rated output from a set of calculated alternatives with varying supply flow rates or flow sheet conditions. Choose what you have.

Third-party engine or method integration : Third-party solvers, engines, applications, etc. can connect to a workflow management system and interact with simulation tools and simulation solvers. This allows plugging in engineering and non-engineering applications where existing simulation tools are not interacting. An example would be to add equipment sizing routines that do not rely on simulation solvers, such as rules for volume design and internals for isolation. For example, for gases over a certain pressure with a certain amount of water, a bullet separator with a weir internal is used and those internals are derived from the data in the simulation tool. Determine the size of the.

Event-driven modeling : Event-driven modeling can ensure that the model accurately represents the operation of the processing facility. One example is that when an operating condition is reached, an event occurs and changes are applied to the model. In one example, the flow conditions are polled and the occurrence of a low flow condition causes the application of a zero flow rate on a constant train.

Custom calculations : Workflows can provide a way to add custom calculations, especially when decision logic needs to be widely applied to flow sheets. For example, find all heat exchangers above 1 MW and apply a 10% increase to 1.1 MW as a design factor.

Workflow Variables vs. Calculation Results : The use of custom calculations and “design criteria” requires the simulator to report the calculated process simulation values and design criteria values at the same time. For the above example, both the heat exchanger process simulation required power and the selected design reference power are reported. “Calculated process simulations” and “current workflow values” can be reported for all stream and unit operations.

Simulation engine as a black box to other applications : A workflow can be used to allow a simulation engine to be called by other applications and provide a “black box” service. This may be particularly beneficial when conditions or logic need to be passed to the simulator, for example from an engineering design database or an upstream model (with integrated assets). For example, criteria for gas treatment can be passed to the simulator. Thus, the simulator can choose to activate a new compression train when the reservoir reaches the flow threshold as it reduces gas flow. Alternatively, the simulator can wait for instructions from the reservoir simulation to activate a new compression train (in which case the reservoir simulation is determined and communicates changes in one time step to the process simulation).

Additional solvers : The workflow can allow the simulation tool to add additional solvers for units, streams, or subflow sheets. An example would be to add a new separator carry-over model that runs for certain conditions.

Repetitive work : The workflow can perform simple repetitive tasks such as creating a flow sheet, designing a compressor in a certain way, and solving a distillation column in repeatable steps. Here the user can record manual steps that would otherwise be executed, which builds a repeatable workflow that can be applied to any similar task.

Flow sheet quality assurance and warning : Users can set certain workflow tasks to known design criteria to enable quality assurance (QA) of their own flow sheet. For example, a warning can be displayed when a simulation variable falls below a certain value, or deviates from a desired value by some factor, exceeds a certain value, or reaches a certain value. Also, conditional values based on other events and calculations can trigger alerts.

Who did what? : Who performed which workflow when, and who set the design criteria, and other similar metadata related to the workflow can be recorded to allow management of the system.

Additional factors to note are listed below.
The workflow engine can generate an executable program (or web application) that can be executed to execute the workflow.
The workflow engine can access data on the simulation database using any database management system implemented.
The workflow engine can access processes running on a Windows computer via automation, get data from those processes, and add data.
The workflow engine allows specific activities that may be associated with external applications and data to be added.
The workflow engine can start processes and then wait for them to complete before continuing.
Workflow configuration and maintenance may be enabled by non-programmers using activities defined by themselves or more complex activities defined by programmers.
The user can do the following:
○ Use a pre-created workflow ■ Mapping up to a stream with the same name or mapping to a new one ○ Creating a simple workflow through graphical Ul ■ All simulation variables can be used ○ Cases Use an external interface (for example for programmers) to create a workflow that can be loaded into or used to load / execute / add externally ○ “Lockdown” the workflow and make it non-editable ■ Make the workflow visible or make it function like a black box.
• Workflows can interact efficiently with any part of the simulator, eg thermodynamic principles, reevaporation (flash), stream characteristics, unit operations, etc.
• Under workflow management, any flow sheet or part of a flow sheet can be easily identified for the user or the consumer of the results.
Workflow results are clearly distinguished and tracked by the level of result storage set by the user.
• The results of alternatives executed by the workflow are clearly displayed.
-Progress of workflow execution is clearly displayed to the user.
• Workflow steps are visual and have the ability to rewind and look back throughout the workflow steps during a “live” session.
A simulator case may include any mix / nesting of unrestricted workflows that are independent or subordinate to each other.
The workflow system (“PWM”) runs jointly at any level of the flowsheet or subflowsheet or across any number of them.
• The user must be able to mark or tag the workflow to indicate the beginning.
• One case executing a workflow can give rise to another.
・ Revision in “tree format” is supported. For example, a tree structure arranges alternatives to create different revisions as follows:
Rev_1
Rev_1_1
Rev_1_1_1
Rev_1_2
Rev_2
(Where Rev_1_1_1 is Rev_1 plus other changes plus other changes)
It is easy for a user to move workflows, workflow components, and sub-workflows around and reposition them (same for activities, alternatives, and other workflow components).
PWM supports decision tree analysis that allows the workflow to define a decision tree that is executed when the simulator computes parts of the tree. For example, if a new compression train is needed and if so, add it and add the appropriate gas turbine model.

  In the following, an example of a workflow use case applied to a process simulation will be described in more detail. In all instances, the workflow management system is fully documented. Any workflow logic error is stopped and displayed in the workflow management environment. Application to errors / cases over workflow execution is included in the simulator's trace environment with any diagnostics that are clear, self-explanatory, and repeated in the workflow management environment. Clear logic and execution error diagnostics are built-in.

Setting flowsheet values from a workflow The purpose of this workflow is to monitor the flowsheet and to change some parameters based on user-defined workflow logic. In general, changes will be due to design limits or other information apart from process simulation. The changes may affect the simulation and require resolving or may be supplementary information that is “carried” in parallel with the simulation. An example is the power “selected” from the available machine size that is optimal for the calculated power. This use case focuses on compressor simulation and design and relates to changes to both the independent calculation variable and the second reporting variable in parallel with the simulation to demonstrate both requirements. The user then adds a second workflow around the separator to indicate that multiple independent workflows can be supported in one case. Users are generally process engineers who use without programming ability. This type of use case occurs many times each day and is repeated throughout the day by many users.

The simulator is started and the converged simulation model is available to the user (previously created or incorporated during this session). This case includes at least two converged compressor models with default compressor parameters.
1. In the simulator, the user opens the simulator workflow management environment (never leaves the simulator). This is a simple workflow interface that is easy to use and requires minimal training.
2. The user adds a workflow and gives it the name “My Compressor Design”.
3. The user enters a workflow description for others to understand.
4). The user has the option to lock the workflow so that only that person can see the internal definition. If you use a shared locked workflow, any other user will only see the name and result of the workflow.
5. In a flow sheet that can follow this workflow, the user sees a list of all stream and unit operations.
6). The user selects all compressor objects in the flowsheet to place under workflow management.
7). The user is prompted to <save> or <auto-save> is in effect (autosave can be set as the default in user preferences).
8). The user adds a new sub-workflow to this workflow and names it “Adiabatic Efficiency Adjust”.
9. The user selects <adiabatic efficiency> as the sub-workflow independent variable.
10. The user then adds two activities graphically:
a. If the compressor inlet gas flow rate is greater than 10MMSCFD, set the adiabatic efficiency of any selected compressor to 95%,
b. If the compressor inlet gas flow rate is less than 10MMSCFD, set the adiabatic efficiency of any selected compressor to 65%.
11. The user is prompted to <save> or <auto-save> is in effect (autosave can be set as the default in user preferences).
12 At any time while creating a workflow, the user can cut, paste, and import previously created workflows, or export them as an example of a library (eg locally or on a server) so).
13. The user then adds a second sub-workflow to the same workflow and calls it “actual design of the compressor”.
14 The user then adds four activities to this second sub-workflow under the same one workflow. The user selects the unit as the <compressor power> and activity variable:
a. The user defines a “workflow variable” as <Design Compressor Power>;
b. The user defines the standard design size used as the choice (eg 3MW, 5MW, 9MW, 13MW);
c. The user defines that if the calculated power is less than 3 MW, the Design Compressor Power variable is added to the flow sheet to select the 3 MW compressor as the design criterion;
d. The user defines that if the calculated power is greater than 13 MW, the Design Compressor Power variable is added to the flow sheet to select the 13 MW compressor as the design criterion. ;
e. The user defines that if the calculated power is between 3 MW and 13 MW, the nearest standard design size is used and rounded up or down to determine the Design Compressor Power. The user can also add logic to select one of the standard design sizes, eg define a certain percentage margin above and / or below a given standard design.
15. The user is prompted to <save> or <auto-save> is in effect (autosave can be set as the default in user preferences).
16. The user then activates the workflow on the flow sheet. The workflow is currently always running in the background before, after, or during execution of the solver and is applied when the model is resolved.
17. The user opens a tab in the simulator workflow manager displaying the workflow execution. This tab shows the workflow status, shows the workflow when fully executed, summarizes the changes caused by the workflow, and displays "from" and "to" numbers .
18. The flow sheet ends with a new thermal insulation efficiency and is recalculated with the appropriate operating power. From there, the final part of the worksheet has selected Design Compressor Powers for the two compressors, which is the result of both unit operations, the summary of the flow sheet and the actual calculated power and parallel to it. Includes selected "Design Compressor Powers" to do.
19. The user can now save the original state case, or the end state as a replacement to the original, or an automatic revision. Users can also save, export, import, cut, copy, and paste at any level of workflow (including alternatives or activities).
20. The user adds a second unrelated workflow to a case called <Separator Carry-Over>.
21. The user imports a pre-existing workflow from the library.
22. The workflow manager recognizes the imported workflow as being associated with a separator and provides a drop-down selection to apply it to all separators or individual separators.
23. The user chooses all separators. The workflow is a separator entrainment calculation, in simple terms, for every incoming stream, 20% of the light liquid in the gas is separated by more than (approximately) 40% by weight of the liquid (aggregate) in the gas stream. Carried away to the machine. The workflow manager “asks” whether it applies to all separators in the flowsheet, or only those with a predefined <carryover>. The user selects <all separators> and starts the workflow.
24. The user is prompted to <save> or <auto-save> is in effect (autosave can be set as the default in user preferences).
25. The simulator recognizes the workflow as a pre-solve change to the flow sheet and sets all <carryover> conditions for the separator. The flowsheet is resolved and the flowsheet is ready to determine if the user wants to see the solutions that are lined up in the workflow results environment and in what state they want to save the flowsheet.

  The simulator has finished the simulation and includes a converged flow sheet with both a change in compressor independent variables and the calculated compressor power in this re-resolved new default and number of workflow design choices in an easy-to-read side-by-side layout. The user has the option of saving the new flowsheet as either replacing the original, reversioning the original, or saving the workflow in the library for the future. Workflows are stored in a centralized manner and can be reused by many.

Setting Flowsheet Alerts The purpose of this workflow is to allow users to set modern techniques for flowsheet quality assurance in “real time” when it is run and builds a model. is there. The user selects one of the pre-configured workflows that are equipped with the simulator, quickly customizes for their own use, and saves them for future use. Users are generally process engineers who use without programming ability. In addition, a process engineering manager is involved, who does not use a simulator but can get reports of any warnings for QA flowsheet design violations. This type of use case is a routine task and can occur multiple times daily.

The simulator is started and the converged simulation model is available to the user (previously created or incorporated during this session).
1. In the simulator, the user opens the simulator workflow management environment (never leaves the simulator). This is a simple workflow interface that is easy to use and requires minimal training.
2. The user selects a pre-configured workflow provided from a drop down box. The user selects <Alerts> and gives it the name “QA My Energy”.
3. The simulator acknowledges that this workflow should warn of violations of independent, dependent, or default variables that are above or beyond a threshold by looking at the flow sheet.
4). The simulator prompts the user to select an independent variable, dependent variable, or default variable in the flow sheet.
5. The user selects all stream or unit operations with a <Power> calculation.
6). The simulator adds actions to the workflow to see all power calculations.
7). The user defines a warning for any individual power requirement above <1 MW>.
8). The user is prompted to <save> or <auto-save> is in effect (autosave can be set as the default in user preferences).
9. The user activates the workflow. The flow sheet is scanned-it doesn't need to be resolved if nothing changed-the PWM environment reports any warning above 1 MW and displays the offender in a list. The flow sheet process flow diagram also highlights offenders in some way.
10. The user adds a second action to this workflow to sum all the power conditions in the flow sheet, and adds a warning if the sum exceeds <50 MW>.
11. The user is prompted to <save> or <auto-save> is in effect (autosave can be set as default in user preferences).
12 The user activates the second action, deactivates the first action, and orders it to be applied to the workflow. The flow sheet was scanned a second time and reached a warning about total power consumption. Warnings are displayed in the workflow manager and flowsheet environment.
13. Both are active because the user reactivates the first action. The workflow manager remembers that nothing has changed and still has the stored value (eg, in the database) of the first action and displays the results of both actions.
14 The user exports or prints the workflow report as a QA report for the process engineering manager and saves the case.
15. The process engineering manager checks one after another by connecting to the simulator database for the case, and checks the current workflow results for itself (eg in a web service) without starting the simulator.

  The workflow provides a report detailing any warnings that convey a violation of the flow sheet QA design criteria. Create very advanced alert workflow templates and share them with your team.

Workflow that triggers the workflow The purpose of this workflow is to trigger further workflows. Users are generally process engineers who use without programming ability. Further process engineers are also involved in use. This type of use case is routine for some users and probably not everyday for others.
1. The simulator is started and the converged simulation model is available to the user (previously created or incorporated during this session).
2. In the simulator, the user opens the simulator workflow management environment (never leaves the simulator). This is a simple workflow interface that is easy to use and requires minimal training.
3. To see all available workflows (eg on local disk, database, shared server), the user selects the drop-down box. The user sees the workflow name and description of the workflow and any sub-workflows. The user selects a workflow and loads it into the simulator case.
4). This workflow has a sub-workflow that investigates cases and finds all streams with "Flare" anywhere in their name. When activated, the workflow proceeds through each of the identified streams and asks the user to check if this is "Flare". Finally, the workflow asks the user to map or classify any missed streams that are actually "Flare" streams (which do not have "Flare" anywhere in their name). The report is generated as a table with all these streams showing the selected characteristics to the user for display (set in the sub-workflow).
5. The workflow also says that if sub-workflow 1 finds any flare stream with a non-zero flow rate, a second workflow called "Flare2Excel" should be loaded from the shared server and executed automatically It includes a second sub-workflow that simply states:
6. The "Flare2Excel" workflow is started and added to the identified flare stream to load and have an activity that defines a saved spreadsheet template (or links to a defined spreadsheet template) .

  Some workflows are triggered sequentially by each other, and the final combined computation of all workflows is the final state of the case. A history of which workflow caused which workflow and why is stored in the message history.

Upstream Oil and Gas Design Standard Designer The purpose of this use case is, for example, to assist contractors who need to follow “design standards”. Contractors can have complete design standards for projects dictated by instructors, their own internal standards, or a mixture of both. Design standards provide a wealth of knowledge in facility design and operation, along with a workflow that allows users to “add in” knowledge to the simulator and share or protect it. These design basis workflows can be very large, including many individual workflows with many included activities. There may also be workflows that trigger other workflows. The user is typically a design criteria designer and may be a programmer who is not familiar with using a simulator, or who generally only uses the simulator for simple tasks. Design criteria designers typically program on design criteria within a powerful external programming interface.
1. The programmer opens a workflow designer environment.
2. The programmer chooses a new workflow.
3. Programmers can copy / paste / import / export existing workflows.
4). The programmer creates an advanced design standard and identifies it by project name or number to instruct the simulator how to simulate the facility and QA results. Multiple workflows, sub-workflows, and activities, decision trees, QA and alerts are all possible.
5. The programmer decided whether the flow sheet changes were automatic or received manually by the consumer.
6). The programmer chooses it as negotiable. All users of the simulator for that project will be forced to use it.
7). The programmer chooses whether it is a recommendation and can be changed by the user, or it is locked and not negotiable.
8). The programmer can test the workflow logic in the workflow designer environment by opening the simulator or by requesting the process engineer to test it in the simulator.
9. The workflow is saved as a shared workflow for the project team.

  Complex workflows can be created that can be loaded into any simulator case for validation first and then for use by project team members as design criteria for the project. Full documentation of the workflow designer environment is available.

Upstream Oil and Gas Design Standard Consumer The purpose of this use case is, for example, to assist contractors who need to follow “design standards”. Contractors can have complete design standards for projects dictated by instructors, their own internal standards, or a mixture of both. Design standards provide a wealth of knowledge in facility design and operation, along with a workflow that allows users to “add in” knowledge to the simulator and share or protect it. These design basis workflows can be very large, including many individual workflows with many included activities. There may also be workflows that trigger other workflows. The consumer can load a pre-created workflow from an external workflow designer inside the simulator. Users are typically process engineers working on project teams that are required to use pre-built design criteria in the form of workflows. This may be, for example, an engineer who wants to use best practices and know-how. This type of use case is routine and can occur multiple times daily.

Pre-created simulation models exist and the workflow or set of workflows that make up the design basis are created by the programmer in an external workflow designer interface.
1. The user opens or creates a simulator case. The administrator identifies this user as a simulator user for project “X”.
2. The simulator associates project “X” with the pre-built design criteria, which is loaded from above into the case and scans the case to execute a workflow that may include flow sheet changes. All changes are specified for the user to see.
3. The user receives this change and executes the flowchart.
4). Warnings from design standards and QA violations are emphasized and repaired automatically or manually.
5. The user works through the identified issues and saves the case once the design criteria QA report, which is part of the workflow, is closed and published.
6). The process engineering manager can obtain the design criteria QA report from the user or directly from the shared simulator project database.

  The result is a design standard that is applied to the flowsheet for simulation, along with the applied design standard standard, and then the QA that opposes the extension of the design standard in the same workflow.

Alternative Distillation Column Design The purpose of this use case is that the workflow compares two different designs in the case of a simulator for changing one flow sheet / feed. This workflow is typically done by a process engineer within an engineering service provider, or a single Toll column with 40 trays (eg DE-IC4 tower), or each with approximately 20 trays, smaller twin reboilers. And used by operators who need to decide on one of two split columns with capacitors. This type of use case can occur daily by an engineering service provider or monthly by upstream oil and gas operators.

There are pre-built simulation models for the gas plant front-end, including high flow rate, medium flow rate, or low flow rate and flow synthesis conditions. This simulation model is ready for additional distillation column (s). There is a need to determine whether the best design is a single tower or split two tower system. There are two subflow sheets with two possible distillation column designs.
1. In the case of including two alternative subflowsheet designs, the user opens a workflow.
2. The user sets up a workflow called <Compare Distillation Column Designs>.
3. The user sets up a first sub-workflow to evaluate the first alternative, attaches or activates sub-flow sheet 1 (single column design), and supplies the first sub-workflow with a low flow rate supply, Three activities are added to the first sub-workflow for the use of medium flow rate supply and high flow rate supply. The user instructs the first sub-workflow to track the total energy consumption for each activity and to track any flow sheet non-convergence. The user can also add a variable to be tracked, for example n-butane capacity of the overheads stream.
4). The user sets up a second sub-workflow to evaluate the second alternative, attaches or activates sub-flow sheet 2 (2-column design), and provides low flow rate supply, medium flow rate supply and high flow rate supply. Add three activities for use. The user instructs the second sub-workflow to also track the total energy consumption for each activity and to track any flow sheet non-convergence. The user can also add a variable to be tracked, for example n-butane capacity in the top stream.
5. The user then compares the two sub-workflows and adds a reporting activity to the workflow that ranks them for average total energy for the three feed rates, average n-butane purity in the top, and number of flow sheet non-convergences Giving a weight of 50% to convergence, 30% to energy, and 20% to purity.
6). The user is prompted to <save> or <auto-save> is in effect (autosave can be set as the default in user preferences).
7). A user activates a workflow that activates two sub-workflows and associated activities. The workflow allows the model to be simulated and the user is given clear ranked design options.
8). The user selects the selected subflow sheet and activates it. The alternative design remains unactivated. Simulation cases including alternative comparisons are saved.

  The workflow triggers simulations of both design alternatives against changes in the inlet supply, ranks the designs based on criteria entered by the user, and selects the best design. The user can choose to save the original or final or any case at any time step. The final case contains cumulative information generated from the execution of the workflow.

Field management instructions The purpose of this workflow is to support field management or refinery operation instructions. Users typically use reservoir simulation tools and want the simulator to connect a field simulation technology with a process simulation model with specific instructions to do x, y, z with time (date) An engineer. This type of use case occurs daily by reservoir engineers.

The user accesses a pre-created simulation case that can be run without opening the workflow manager and can have workflow requests communicated from an external system.
1. Reservoir engineers interrogate the process model and process model structure (streams, unit operations, variables) from within the reservoir simulator tool for any existing workflow.
2. Reservoir engineers map process model variables on demand.
3. Reservoir engineers can create a field model with a certain field logic that also includes instructions that the process model resolves and changes over time, along with any built-in time series functionality, for example, in units on the stream in future years. Set.
4). Field management instructions from the reservoir simulator can instruct the process simulator to “maximize”, “reduce gas” or “produce with constant” gas flow at each time step.
5. The simulator workflow management system must be mapped (easily repeatable) to external field management instructions so that it can respond.
The process simulator returns the requested value to the reservoir simulation tool and shuts down.

Automated Simulator Execution The purpose of this workflow (built in or out of the simulator) is to join a third-party database and map simulation variables to values in the database. This workflow then defines the scheduled or automated execution of the simulation and stores the results for that value. The user may be a process engineer, an IT manager, a programmer, or the like. This type of case can occur daily.

The user accesses a pre-generated simulator case and a third party database with measured feed stream flow rates and components.
1. The user (programmer and / or engineer) sets up a new workflow called <Mapping>.
2. The user selects the feed stream 1 flow rate and all components, and the activity checks the well test database at 9am all weekdays for any new values, loads those values, simulates the facility, Add to sub-workflow 1 defined to publish new results in the form of a morning report to another database or spreadsheet.
3. The user selects the flow rate and all components of feed stream 2, adds the activity to sub-workflow 2 that is defined to load any new values from the database when the database is modified, and sends a message. Send to workflow (eg via web service). The simulator then simulates the facility and publishes the new results in the form of a morning report in another database or spreadsheet.
4). The user activates a workflow that generates a service that is external to the simulator and independent of the simulator.
A new set of simulation results is generated using the updated measured feed stream flow rate and components. External services can manage workflows independent of simulators.

Timeline diagram 9 shows a further system 58 for facilitating the simulation of industrial processes. A rule 60 that defines time-dependent characteristics of process information is input. Rule 60 may be entered, for example, by a user or by external software. Process information 16 is input to allow process simulator 18 to simulate a process based on process information 16. The process simulator 18 simulates the process under changes in the time-dependent characteristics of the process information. A series of simulation results 62 is generated, which may be further manipulated, for example, for cumulative calculations. The time-dependent characteristic can be related to, for example, a decreasing inlet flow, or a planned change in process topography, and the time dependence can be linear or non-linear.

  Process simulators traditionally do not resolve with dates for months and years of plant operation in a single model with events occurring and alternative scenarios considered. The time series adds time dependency as a layer to the process simulation to enable event-driven simulation over accumulation, date correspondence, and time (ie enabling time-dependent changes in the simulation). In the future, instead of several days of manual checks, time series can be used to design the facility's operation for known changes in the processing environment or changes that need to be tested. Time series allows users to define a single process simulation model (as opposed to many different ones) and produce, refine, or petrochemical oil and gas over a day, week, month, or year It is possible to calculate the cumulative response at.

For example, the time dependence can be as follows.
Change user-specified events and logic on a certain date or when conditions are met. For example, add a second gas train and start operation on August 1, 2017, or add a second gas train and start operation when the gas / oil ratio reaches 71%.
・ Decreased (reservoir) supply rate to facility ・ Switching supply ・ New equipment to be operated ・ Deterioration of equipment ・ Deterioration of catalyst ・ Increased compressor suction requirements ・ Replacement at a fixed time Necessity of replacement to compressor • Distillate hydrogen increasing non-linearly over the course of the year when the unit is supplied with varying concentrations of sulfur and nitrogen under certain upward or downward conditions (in refining) Weight average floor temperature of processing equipment (WABT)
A recurring scenario and / or a periodic scenario.

  Time Series Management (TSM) is a time series tool for defining, generating, storing, managing and applying rules defining time dependent characteristics. TSM is a simulator for performing calculations over time (where the user wants to see the effects of a supply stream that gradually changes over time), as well as new equipment being brought into operation or accumulated production And for use in combination with energy balance. Most of this use case is related to the facility's response to supply changes or scheduled equipment or facility changes.

  If the user knows all the necessary changes and timing in advance, TSM can implement time dependency. To provide versatile and powerful process simulation management if the timing of the required changes is related to conditions (eg, partial replacement when threshold cumulative exposure to flow components occurs) The time series is combined with the workflow described above. By combining workflow and time series, separate scenarios or alternative simulation cases can be evaluated over time. The scenario tool is included in TSM (but may also be included in the workflow manager) and can define many state, value pairs that apply based on date. A scenario can include a state that is not time-dependent, but the alternatives described above can be defined within the context of the workflow.

  FIG. 10 shows a system 64 for facilitating the simulation of an industrial process that combines the workflow 14 and the time dependency 60 to generate a simulation result 66 under changes in process information time dependency and workflow application. Show. This can allow advanced logic and decisions within and over time ranges.

  The smallest time step in the time series is a day (followed by week, month, year, 10 years), so it should not be confused with a dynamic process simulation that resolves at the second level for process control. The time series uses a steady state solver that participates in time in successive cases with changes added via the event scheduler and actions, and a new case that is assembled, executed, and the results saved.

  Time Series Management (TSM) allows users to calculate the cumulative performance of a facility over time using known changes, and the facility evolves, changes, expands and reconfigures over time. Or intended to be a part that can be degraded and discarded. A time series is a discrete event simulation in which system operation is shown as a time sequence of events. Each event occurs at some instant in time and indicates a change in state in the system. For TSM, the user must specify all changes before resolving the case. Any unknown element or compound or decision-based criteria can be performed by a TSM coupled with a workflow manager at a time step or over a time step.

  A common use of TSM is in upstream and midstream oil and gas, where supply and facilities change over time. In oil and gas, TSM is advantageous, for example, in the context of “field analysis lifetime”. There, a model scenario of the oil and gas production system is essential during the conceptual stage of field development and the continuous reaction to reservoirs and production conditions that change over time. The subsurface and surface engineering options employed have immeasurable relationships with the local economic situation. Date validity (the ability to combine simulation models with dates and events related to dates) allows analysis of reservoir-facility performance as a function of time. An example of a TSM use case in oil and gas is that with a reservoir production stream that changes (decreases) over time, with simultaneous changes in properties such as pressure, temperature, and composition, and works on a certain date With a new production stream that comes in and a compressed train planned to run on a certain date. TSM can also have applications in downstream refining and petrochemistry, which simulates production processes in historical time and compares simulator predictions against actual plant measurement results, or in the future Simulation of the generation process and giving performance predictions. In both cases, TSM can show how equipment operations degrade over time due to, for example, catalyst degradation, equipment clogging, and contamination, or other such phenomena predicted by detailed equipment models. Can be considered.

  Time series management allows process simulation cases, including variables and inputs for the flowsheet, to change over time and cumulative results are calculated. A TSM can work within a single due date or across multiple due dates. TSM does not require a workflow management system to work, but can be combined with that for more powerful analysis.

  Examples of time series usage and features will now be described in detail.

Feed stream affected by time : The user specifies how multiple streams change over time-eg in flow rate, pressure, temperature, and / or composition. Changes can be specified in tabular form as an extension of the stream property editor, for example. The user can enter a decreasing curve / table that is interpolated in time steps. The user can specify an increasing stream for production or a new stream coming into production at a certain time. Existing flow sheets or flow sheet responses that change over time are then recorded against these production profiles.

Specification influenced by time : The user can specify that the specification of the flow sheet changes over time. For example, the dew point designation, TVP, WobbeIndex, and / or pressure of the outlet gas plant can change or become tight over time.

Unit operations affected by time : The user can indicate whether the device is on or off at a certain time. Thereby, for example, operation of a new facility and maintenance of an existing part of the facility can be considered. The main application is to model known changes to a facility over time that may counter common supply and designation or change.

Field management case : The user can specify a specific action at a point in time to line up a process facility with a reservoir field development plan. For example, a water jet is activated at a certain date and all the water is collected in one stream at the required flow rate.

Cumulative product and energy : The user can specify that any input or calculated variable can be recorded in time steps and plotted against others. Cumulative values can be tabulated and graphed over time steps for selected variables.

Maximum and minimum : The user can select variables for “observation” and can monitor the maximum and minimum values over a series of time steps.

External time step : Users can desire a time-dependent process simulation that can be used by date, which is simultaneously connected to a third-party simulation system. For a flow sheet that can be used with a simple date (no flow sheet changes at a given time or one), in one case the field life required by the time stepper indicated by the external system is reduced. Can be handed over. For complex cases, TSM can be combined with a workflow.

Part of a flow sheet : The user can request that only a part of the flow sheet, for example a sub-flow sheet, be resolved at a particular time.

TSM workflow : Advanced optimization and analysis is provided by combining TSM into a workflow as described above. For example, the workflows made available by TSM can be applied to a model to execute a number of scenarios at a certain time, and how much depends on the results from stored violation cases for further analysis. Calculate how many scenarios fall out of a certain standard, for example how much meets the certain total power requirement and how much violates it. Another example of a workflow that can be used by TSM is to make the simulation results time-dependent, so that, for example, the second compression train is below a certain gas flow rate (or other flowsheet variable) threshold. This is to operate on the falling date. It is also possible to optimize the net present value with time and date. For example, as to the extent and quality of the change in the inlet to the supply flow, two cases are best or best, such as the current one large compressor or the current small compressor and the second small compressor within x years, It is.

Event-driven modeling : Event-driven modeling can ensure that time-based model simulations well represent operating conditions. TSM can allow time dependency, and the workflow can allow conditional application of any number of design criteria, such as alternative topography. One example in a cumulative simulation is to implement a shutdown and work-over period. Another example is to implement a reuse period in the startup of a cryogenic unit. One operating condition (eg, a low flow condition), for example, sets a zero flow rate for a given train when an event or measurement result is triggered.

Recurring scenario : The user can enter an event, condition or rule that repeats at a specific period. An example is scheduled maintenance that reduces / stops plant operations. Such events can occur approximately every six months, and such events can be incorporated into the simulation.

Periodic scenario : The user can enter a time-dependent event, condition or rule that repeats periodically. An example scenario in which such functionality may be used would specify an environmental temperature or a temperature of a coolant (eg, seawater, etc.) that varies with a seasonal cycle and / or with a daily cycle.

Additional factors to mention are listed below.
Time series tools allow users to define a single case that changes over time rather than defining (potentially large) numbers (eg 100) of cases with different settings.
Time series management can be shown as “environment” in a simulation tool similar to the optimizer or other simulation tools.
• Time series management has an event environment to define events on stream and unit operations.
Time series management has a results environment for users to declare the level of results stored in time steps.
Time series management has a progress environment that remembers messages and diagnostics for each time step.
• Time series management has a table and graphical environment to plot and compare results during the application of the time series to the simulation or any time after values are stored.
The user specifies the start time (default is the current simulation time) and end time along with the size of the required step, so that the solver steps from start to end. The user can specify and execute events for cases that are completely affected by time within the simulation tool. Alternatively, the user can specify the start time, step size or number of steps.
Alternatively, the user can specify a start time (default is the current simulation time) and conditions for ending the simulation (eg, cumulative production reaches X or full compressor power is obtained).
Users can clearly define dates and events in the event scheduler.
When the time stepper moves through time, the value of the flow sheet independent variable or program default changes are triggered from the event schedule.
Flow sheet topography can change in time. For example, alternative topographies are declared and their execution is scheduled.
The event schedule in time series management records all applied and processed changes and clearly displays all streams, unit operations, utilities, etc. that have time dependencies (and changes that occur).
The user can request a cumulative number generated for any declared independent or dependent variable and may have to define how they are calculated.

  ○ Example-whether the event changes between time steps. For example, the supply changes every six months, but the time stepper steps several years. The user should specify whether the actual number is resolved and accumulated in the time stepped time, or whether supply and production will vary by supply change% for 6 months.

O The time stepper can automatically delay the time to capture most finite events and then roll it up again to increase the step size, or nothing will affect the simulation results. In this case, the accumulation is calculated by summing the product of a value and the period associated with that value.
The event scheduler includes functionality to indicate when the next adjusted event will occur, so that the time stepper can verify that it hits that particular point in time.
• TSM will provide a report if the application of time dependency to the simulation fails, for example because the simulator is unable to constrain due to flow sheet limitations, or no changes are seen.
TSM can be combined with advanced functionality suitable for time step mode (eg as known for dynamic simulation). Examples are strip charts from dynamics simulation mode (charts that plot variables over time), event schedulers from dynamics simulation mode (tools that allow the user to set what happens based on simulation variables reaching user-set states), historian Tools (tools that have access to the history of plant measurement results), and cause and result matrices from dynamic simulation models, where the user can perform a complex series of cascading actions or results depending on the possible events or causes Can be defined).
• Most equipment items, such as reservoirs, spreadsheets, compressors, columns, user variables, etc. are time dependent and may change over time.
・ Workflow cumulative value (defined by user) that can be used by date is clearly displayed. ・
Along with the workflow, the workflow can select a date and set the specification as a function of the input date or time.
Cases can be defined as time-series management functions that change over time and can be manipulated or tracked by workflow.

  In the following, an example of a time series management use case applied to a process simulation will be described in more detail. In all instances, the time series management system is fully documented. Any time step logic error is stopped and displayed in the TSM environment. Errors over time series execution to cases are included in the simulator's trace environment with any diagnostics that are clear, self-explanatory, and repeated in the TSM environment. Clear logic and execution error diagnostics are built-in.

Supply stream and designation affected by time :
The purpose of this use case is to set up a supply with a decreasing curve. As the gas reservoir descends, the supply to the gas plant decreases in flow rate, component changes (eliminate heavier components), pressures also drop, and generally gas treatment pressures (approximately It is necessary to increase the gas compression pressure at the inlet to reach 70-100bar) and push it back. At a certain time, the value of the incoming stream “drops” and the available flow rate is lower than before. The time-varying field causes the processing facility to experience lower productivity and higher energy requirements. The questions the engineer wants to answer are how much he can recover over the next decade, how much cost, and whether a particular compressor can raise the pressure. Users are generally process engineers with no programming skills. This type of use case can occur many times a week by some users, but never by other users.

The simulator is started and the converged simulation model is available to the user (previously created or incorporated during this session). This case includes a gas plant with inlet separation, inlet gas compression, acid gas sweetening, dewpointing, and pressure gas transport with known pipeline specifications.
1. In the simulator, the user opens a time series management environment (never leaves the simulator). This is a simple time series interface that is easy to use and requires minimal training.
2. The user specifies 10 years in 6-month steps.
3. The user can add feed stream 1 as a time dependency of this environment, but instead choose to open feed stream 1 and check the box labeled <Date Enabled>.
4). The ability to add decreasing curves for pressure, flow rate, temperature and components emerges. The user can add time-dependent data with any time granularity, eg, day, month, quarter, or year granularity. Input data is interpolated and stored according to selected time steps as specified in the TSM environment. The user enters a reduction condition for supply stream 1 at a quarterly rate. All other streams remain the same.
5. The user returns to the TSM environment and notices that feed stream 1 appears as a time-sensitive feed stream with a summary of the applied changes.
6). The user knows that in 2015 the export pipeline will be depressurized by 10 bar and the export requirement will be reduced by 10 bar.
7). The user selects the <Export Sales Gas> stream from the TSM environment variable list, and selects a stream for time series management. The user selects the pressure designation and lowers it by 10 bar in 2015.
8). Since the device does not change, the user does not change other flow sheets.
9. The user goes to the resulting environment in TSM, and the simulator is the volumetric flow rate for supply stream 1, export sales gas volumetric flow rate, export sales gas pressure, inlet field gas compressor efficiency (duty), and total flow sheet efficiency ( duty) to be recorded. The user can choose the frequency of saving and reporting, but instead determines the same default as the selected time step period (6 months in this case). The user also chooses to calculate the cumulative export sales gas volume flow rate and cumulative total flow sheet efficiency. The user decides to save this data in the simulation database.
10. The user changes the default to save the original case and the last resolved case in the last time step as one revision, to save all cases and all time steps as a (master) original case revision .
11. The user saves the TSM definition and selects <Run Time Stepper>.
12 The simulator starts the simulation under time series application. A simulation progress bar is displayed and the result of the time step is added as each time step is completed.
13. The case ends and a graph of inlet field gas compression efficiency over time is displayed as well as a plot of cumulative energy and export flow rate. This graph clearly shows the compressor power requirements, which are growing rapidly in later years and have reached the highest point at the maximum active power of the machine. The user decides that it is preferable to put a larger machine in place in a future year.

  The time series produces a 10-year time step simulation that includes cumulative gas plant production and cumulative total facility and individual unit energy requirements. It can be determined whether the compressor performance requirements that meet the changing field conditions can be determined, or whether the defined compressor can meet the booster pressure requirements.

Unit operations affected by time:
The purpose of this use case was to build the “time-sensitive supply stream and specifications” use case described above and create a second new compressor train (separator, compressor, final chiller) in April 2017. Be prepared and understand how it will change the process. Users are again process engineers who generally do not have programming skills. This type of use case occurs many times in a week by some users and never by other users.

The simulator is launched and a 10-year time step simulation containing cumulative data is available to the user (as produced by the TSM use case above).
1. The user adds a new compressed train to the model and selects the instrument associated with it with a right mouse click <Select>. Users make all devices date-enable together and set a new compressed train to be active in April 2017.
2. The user keeps everything else equal and executes the case.
3. The TSM environment reports new time step results and cumulative production. This time, the two compressors can meet the power requirements and release the processing pressure.

  The time series includes a 10-year time step simulation, including cumulative gas plant production and cumulative total facility and individual unit energy demand, including a second inlet field gas pressure system operating in August 2017. produce.

During the period that reflects the field management expiration date for the field management expiration asset, the user specifies many changes. Certain known changes can be added directly to the simulation case data via date enablement. More elaborate decisions with causes and consequences or deployed logic can be achieved using date enablement and workflow management systems within the simulator. Users are generally process engineers who do not have programming skills. This type of use case can occur many times a week by some users, but never by other users.

The simulator is launched and the centralized process simulation model (for that facility as the facility exists at the beginning of the time period) is used by the user as well as a list of known changes over the required time period Is possible.
1. The user opens an existing resolved facility case.
2. The user makes the simulation available for use on the date (i.e., possible under a time dependent change in the simulation).
3. Users add multiple changes to existing equipment status, supply changes, product specifications or other simulation characteristics in a tabular format that is easy to enter. The user designates the change indicated by date and by priority for the change on the same day.
4). The user selects variables for recording, tracking, reports and graphs.
5. The user chooses a number of cumulative numbers to calculate and chooses an appropriate method for averaging between time steps.
6). The user defines all stored simulation cases (the default is the base and final case with user selection of cases at other allowed time steps).
7). The user saves the case.
8). The user executes the case and sees the process simulation results over the time period and the change to the selected process variable and cumulative number.

  The time series includes changes and additions to the facility over time, resolved to the final time step, and includes a graph and report of the required (user-defined) variables tracked over time, during a period Causes a time step simulation.

Maximum and minimum design users can specify maximum, standard, and minimum design criteria for selected process variables or conditions, change time-dependent factors such as date conditions, change supply specifications, change product specifications Can track the performance of maximum, standard, and minimum designs. Users are generally process engineers who do not have programming skills. This type of use case can occur many times a week by some users, but never by other users.

The simulator is activated and the centralized process simulation model (for that facility when the facility is at the beginning of the time period) is available to the user as well as the minimum, standard, and maximum design parameters.
1. The user opens an existing resolved facility case.
2. The user makes the simulation date-enabled (ie, allows time-dependent changes in the simulation) and chooses the minimum, standard, and maximum modes.
3. The user identifies and selects variables, defaults, design conditions, or other flowsheet variables that are to be defined with three values: minimum, standard and maximum. The user enters values in a simple tabular format.
4). The user selects other flow sheet variables, such as supply rate, components that change over time, by date-enabled simulation. The user inputs these values as in the use case described above.
5. The user chooses the variables and / or cumulative values to report and calculations for output in those reports, tables, or graphical formats.
6). The user defines the complete simulation case to be stored (the default is the base case and the final case with user selection of cases at other allowed time steps).
7). The user saves the case.
8). The user executes the case and sees process simulation results for the maximum, standard, and minimum designs over time. Selected reported variables are shown as maximum, standard, and minimum over time.

  The time series is resolved to the final time step, includes maximum, standard, and minimum design conditions, and also includes graphs and reports of required (user-defined) variables tracked over time and a comparison of the three designs , Causing a simulation of time steps during one cycle.

External time step
TSM can be executed from outside the simulator via a direct call to TSM or via the workflow management system described above. Users are typically non-process engineers who call process simulation cases from an integrated management system, in which reservoirs and product simulators are time-stamped supply and designation instructions, energy consumption, injection stream conditions And a return of the result, including the production rate, is sent to a pre-built process simulator for solution at a certain time step. This type of use case occurs many times in a week by some users and never by other users.

In addition to pre-built process simulation cases for facilities (assuming they exist at the beginning of the time period) with all definitions of changes in TSM and time, add and command cases, Predefined connectivity for remote execution is available to the user.
1. The user points to a pre-created process simulation case with TSM.
2. Users connect to supply streams, unit operations and / or product streams.
3. The user defines a value sent from the host system to the process simulation case.
4). The user defines the results returned from the process simulation to the host system.
5. The user can watch any change to the process simulation case over time and send an instruction to change any value at the time step, or the user can open the process simulation case and use the date Changes can be added to the process simulation case.
6). The user runs the host system, and the process simulator is invoked at each time step with connected inputs, instructions, and all date-enabled changes to the case (eg, equipment that starts operating on the stream).
7． The user queries the results on the host system over time.

  The process simulation is stepped by the host system over time and the required reported value is returned to the host system.

Refinery Cumulative Production The purpose of this use case is to provide a refinery example based around a diesel hydrotreater. A hydrotreating unit is a fixed bed unit in which the catalytic activity decreases with time, i.e. the target reactor temperature required to maintain a steady desulfurization level increases with time. The actual rate of inactivation is a function of feed rate, quality and previous activity throughout the cumulative lifetime that the refinery is being investigated. The user is generally a process engineer or an operations engineer. This type of use case occurs daily for planning purposes by an operations engineer.

  The simulator is launched and a centralized process simulation model (for those as the refinery and hydrotreater are present at the beginning of the time period with reactors calibrated for known performance) It is available to the user as well as a list of known changes in hydroprocessing equipment supply and operation over time.

  This example looks at a year in the life of a hydroprocessing unit where feed and quality (sulfur and nitrogen content) vary every month. This model represents catalyst age by the feed volume processed per weight of catalyst. TSM accumulates the total supply and calculates the catalyst age at each time step. The catalyst age at each time step is provided to the reactor with its own internal tracking turned on. The chart plots reactor weighted average bed temperature (WABT) showing the expected increase. The conditions are changing-for example, supply drops significantly in September-so the trend line is increasing, although WABT increases are not linear.

  The time series is resolved to the last time step, the cumulative reaction change of the hydrotreater in the refinery to the change, and the recommended time to replace the catalyst (eg when WABT is above threshold) To simulate a time step during a period, including details on how the WABT grows over time.

Cumulative production and changing facilities The purpose of this use case is to further extend the use of time series management and to have a date-based workflow. Time series functional students can add variable supplies (decreasing and new) over time to the model and be directed to the equipment, train or entire process on a certain date (no need for workflow) To) can be switched on. Time series functionality can be controlled by the workflow to add more versatility and sophistication to the time series. In the illustrated example, the user adds a more complex standard for the selection of new process equipment startups. Users are generally process engineers on upstream oil and gas front-end engineering and design projects seeking to find the best time to operate a new facility. This type of use case can happen daily in upstream oil and gas companies that seek to analyze site degradation.

The simulator is activated and a pre-built process simulation model (for that facility as the facility exists at the beginning of the time period) is available to the user. This model has time-series functionality modeled with a stream that is decreasing over time and a new supply stream to the unit that changes pressure, flow rate, and component profile to become operational. It was. Within this model, the gas / oil ratio (GOR) increases with time, and there are three different designs that need to be evaluated for new gas processing trains (for these-separate simulation models). Are available for use in).
1. The user opens a date-usable main simulator case with a stream that is decreasing over time and a new separate supply that occurs on the stream.
2. There are three gas processing plant design alternatives represented by three other simulator cases with different operating / usable times (ie, three subflow sheets / trains in the base model). The three design alternatives also differ in size, cost, throughput, operating cost, and capacity.
3. Scenario 1 is supposed to cause gas plant 1 (Model 1), Scenario 2 is supposed to cause Gas Plant 2 (Model 2), Gas Plant 2 is caused at different times (Model 3) The user sets up a new workflow with scenario 3. All gas plant models include their respective available dates and estimated (capital investment) costs for creation, stored in user input variables.
4). The user defines costs for various types of energy over a month or year and enters prices for products over the month or year.
5. Users define respectable constraints that can change over time, such as pipe export pressure, emission control, product specifications, and the like.
6). The user defines a net present value type calculation that will be used to rank the options, and the user defines a discount factor for the net present value calculation.
7． The user defines what level of result details should be saved for each case.
8). The user defines several criteria for ranking design choices by weight (eg respect designation, product price, capital investment, operating costs, etc.).
9. The user saves the workflow and executes it. The main model is executed and combined through a new alternative train according to the workflow, and the workflow uses time series functionality to calculate the cumulative and above rankings.
10. The output is a table of ranked options that produce feasible and non-feasible options (damaging according to non-negotiable requirements), then from the top net present value to the bottom List possible options.
11. The user can save the results in a database for later investigation.

  The workflow adds several design criteria to perform three different gas plant designs that have been added to an existing facility and rank the three possible alternatives. The system can track what case was connected to what software component for review of the solution path.

Compressor placement The purpose of this workflow is to assist in design decisions around the facility, with the user specifying criteria, comparing options, or specifying sufficient criteria to evaluate other possible ways the workflow can be It is even possible to select the optimal design. Compressor placement is a typical design issue for offshore production assets. New compressors are needed to promote and expand reservoir gas production. The compressor can be placed offshore or onshore, and the time for compressor installation needs to be determined. The decision affects the decline curve and total cumulative production from its composition and usually the interaction with the facility, but is closely related to significant capital investment and operating costs. This use case adds time series functionality to the workflow. Users are typically process engineers who evaluate alternatives for on-site compressor placement. This type of use case can occur weekly, especially by upstream oil and gas operators.

There are existing production cases that are ready to add a compressor workflow. There is a supply decrease curve based on pressure, flow rate and time, which may be related to the decrease over time for supply and components,
1. The user makes the simulation available for dates (i.e., allows time dependent changes in the simulation).
2. The user adds a set of pressure difference-flow-time reduction curves. The pressure differential is the pressure difference between the decreasing reservoir and the facility entrance and is the driving force of production. Time series functionality can interpolate between decreasing curves.
3. The user opens a workflow management system inside the simulator and within the workflow system, and adds a workflow called <compressor placements>.
4). The user then adds scenario 1 which is an offshore compressor on the platform. Placing the compressor offshore closer to the reservoir reduces facility entrance pressure and can provide higher pressure differentials, higher production flow rates, and longer reservoir life prior to disposal. The user adds the selected power and cost (higher than onshore). The user indicates the month, year that the compressor will be operational, usually the year after the onshore.
5. The user adds scenario 2, which is an onshore compressor. This compressor is larger in size, cheaper in capital investment, and can be used in earlier years than offshore ones.
6). The user adds a net present value calculation with a discount factor for the cumulative production value and sets the workflow to run production over 15 years.
7). The user defines ranking criteria for net present value, capital investment, operating costs, and the like.
8). The user selects the results to be compared for both cases, such as cumulative production, cumulative energy, and flow sheet characteristics.
9. The workflow is executed and interacts with the time series, where the workflow manages the scenario, stores the results, and steps the scenario over time.
10. The workflow ranks the two alternatives and displays the comparison.

The workflow system provides decisions and rankings for optimal design. Time series management is used to interact with the workflow. In a time series, each case is a step in time with a workflow that directs non-time-specific changes within a time step or changes at a certain time. More examples of tools for time series implementation now This will be described in detail.
FIG. 11 shows a toolbar 64 for time series management. The toolbar is related to the time series and includes separate actions including setting, executing, stopping and resetting the time series (tools for defining scenarios, tools for scheduling events, and event summary tools, Provides timeline tools for reviewing results, and historian connectivity tools for connectivity to past data (from past simulations and from real past measurements).

  12 and 13 show a scenario interface 70 with examples of separate scenarios. The scenario of FIG. 12 has a time dependent state associated with a decreasing supply. Although the state included in the scenario of FIG. 13 is not time-dependent, it relates to a design alternative. The selected state can be applied to the model via the provided “Apply State” button. In the scenario interface 70, various information is provided for different states, including the name 72 of the associated process information, the activation option 74, the date 76, and the specification 78. Activation options 74 include reset, manual, date, date interpolation, invalidation, and user logic.

  FIG. 14 shows a data recorder interface 80 that allows selection of dates to be recorded for time series. A number of tabs are provided to manage the executable data, for example to allow certain variables to be included or excluded from the process data table or strip chart.

  FIGS. 15-18 illustrate separate functions within the time series setup interface. FIG. 15 shows the data setting tab 82, where not only the current date but also the period in which the time series is implemented can be specified. FIG. 16 shows a timeline tab 84 where data from the scenario is plotted once the time series is calculated. FIG. 17 shows a strip chart tab 86 where data from the scenario is plotted once the time series is calculated. FIG. 18 shows the accumulation setting tab 88, where data to be accumulated over time is selected.

  19 and 20 illustrate an alternative topography in the process. In FIG. 19, the topography is shown with two alternatives 90, 92 for the compressor process element K-100. Alternatives 90 and 92 are colored to indicate that they are alternatives. FIG. 20 shows a scenario interface 70 having a state for each alternative. One of the states (in Line1, one of the topographic alternatives 90 is active and the other 92 is not active. In the other state ("Line2"), the other topographical alternative 92 is active and the first 90 is not active, the question mark indicates that the value (pressure in the example shown) does not change when the condition is applied.

  FIG. 21 shows a key performance indicator interface 94. This interface 94 allows for the definition of a warning for when the efficiency drops below 3e5 KJ / h in the illustrated example. Alerts are shown on the Alerts tab of the Time Series Settings interface.

  FIG. 22 shows an example of the Accumulation settings tab 88, where supply and production costs for many streams are defined based on stream characteristics in an (external) table and accumulated over time. Used to calculate a value. FIG. 23 shows an interface for designating and displaying net present value information.

Time step simulation includes instructions to change independent parameters and variables at different times. The time for the change or action to occur may be any of the following:
Fixed and predefined by the user, for example by determining that an action should occur on a specific date.
• The result of interpolation over time at a preset frequency, where changes in one part of the system may affect other parts at different frequencies, for example, the flow rate decreases every successive month. The parts are subject to maintenance every 5 years.
The size of a preset step applied to the entire simulation, for example to record the results at regular intervals throughout the simulation.

  In order to ensure efficiency in the computation, the time stepper takes each of these methods of imposing changes and uses them to determine the duration of the next time step. The time stepper compares objects in the system that contain any type of date indication and uses the shortest step returned by those objects subject to the shortest step greater than any given minimum step.

Once the step size to be taken is determined, the time stepper then interacts with the simulation solver to make the necessary changes. The time stepper processes the following sequence of operations:
1. Execute any rules set by the user,
2. Get all objects containing date instructions related to the next step, implement the changes for that step,
3. Allow the simulation solver to solve the new steady state operation,
4. Record the result of that step and test any warning conditions.

  At each step, the simulation solver must start with the resolved case from the previous step and resolve for the given change. If a step is given only for the purpose of recording results without any change in any independent parameters or variables, the simulation solver should not be performed and the above action (3) can be omitted, resulting in a computational load. Is omitted and the acquisition of time-series results is accelerated.

Laboratory Analysis FIG. 24 shows an additional system 96 for a simulation process for a processing facility. The process information 16 is input to enable the process simulator 18 to simulate a process based on the process information 16 and generate a simulation result 98. The simulation result flow portion selection 100 is provided to the laboratory analysis tool 102 as well as the phase analysis selection 104 to be performed. To generate the phase analysis result 108, the laboratory analysis tool 102 performs the phase analysis by the phase analysis engine 106.

  Laboratory analysis is a tool for process simulation that can provide a standard environment for analyzing streams of process flow sheets. Laboratory analysis allows for simple, non-flow sheet type, different streams, pressure / volume / temperature (PVT) conditions, oils, analytical samples, and thermodynamic analysis, while the user has multiple stream phase envelopes and / or Or, it is possible to compare the transition of the operating point in the pressure temperature space across the facility.

This analysis can enable, for example:
-Phase envelope generation-Simultaneous display of phase envelopes of two or more different streams for comparison-Flow rate guarantee prediction-Hydrate calculation-Automatic calculation of injection inhibitors-Pressure-volume-temperature (PVT) calculation-Black oil Calculation, oil analysis, blending calculation, compositional flash calculation.

  A phase envelope is a phase diagram used to indicate the conditions under which thermodynamically distinct phases can occur in equilibrium.

  Analysis can be performed on stream components without generating a complex flowsheet, or the ability to generate phase analysis information associated with all streams that can be easily extracted from a complex flowsheet In position, it is possible to evaluate the transition from the reservoir through the treatment facility into the downstream. This type of analysis is particularly important for upstream production and gas production sectors with further downstream use in refining and petrochemistry.

  For example, a laboratory analysis tool can allow a user to simultaneously examine the input stream to the gas plant and the output stream from the gas plant for changes in phase envelope morphology and behavior within one graphical environment. Covering other streams with the characteristics of one stream is very beneficial to users who do not have any tools to do so in conventional process simulators.

  A reference environment is also provided for fluid destinations. This enables comparison and verification with a reference library, prediction of physical characteristics, and evaluation of characteristics of mixed operations. PVT data from the reference library can be used for oil analysis, analytical data or data calculated by thermodynamics. This can provide a powerful tool for thermodynamic and flow assurance analysis of process chemical streams.

  Traditionally, an envelope can only be shown for one stream at a time. How system changes will affect the phase envelope is not provided for analysis. In addition, solid configurations (such as wax and asphaltenes) are conventionally transported and mixed as stream analysis sample properties (which may not provide a more reliable prediction of the solid configuration).

  This laboratory analysis tool for process simulation currently includes a range of functionality that either does not exist, exists in multiple locations, or is difficult to access. More specifically, the user can select many streams from the process flow diagram in the process simulator and is provided with an option to send them to the laboratory analysis tool. The stream is then immediately available (with a single click) in the laboratory analysis graphic interface. An example of such a laboratory analysis graphic interface will now be described in more detail.

  By selecting the streams and sending them to the laboratory analysis, the user can decide which streams are available for which set of experiments. All streams being sent to the laboratory analysis have a checkbox of choice to determine if they are available.

  FIG. 25 shows a toolbar for laboratory analysis. This toolbox provides different actions for laboratory analysis, including adding envelope experiments, adding streams to laboratory analysis, and refreshing component groups.

  26 and 27 show two examples of the stream phase information page 110 of the laboratory analysis graphic interface. This page gives envelope and hydrate details for all streams that have been added to or sent to the laboratory analysis. By sending streams from different locations in the flowsheet to the laboratory analysis, phase characteristics can be reviewed and compared as the flow progresses through the process.

Each stream that is being analyzed is listed in the left panel 112. The middle panel 114 provides a phase diagram for the available streams. When the listed stream is selected (118) in the left panel 112, the right panel 116 updates with stream related information (hydrate, critical properties, CO ₂ population, etc.). Alternatively, the right panel 116 may include a number of columns that contain relevant information for different available streams.

  In FIG. 27, an example of a stream phase information page 110 is shown with a right panel 116 entitled “Current Conditions”, where “With Inhibitors” is shown. The section contains the current stream and the inhibitor components entered by the user in the bottom table of the right panel 116 entitled “Inhibitors-% of water + inhibitors”. The analysis results are displayed using the complex components. If the user enters inhibitor values in this table, two sets of curves are displayed in the plot in the middle panel 114. One curve is for a stream without a designated inhibitor and one curve is for a stream containing a designated inhibitor. In this example, the inhibitor value is water +% inhibitor. One of the fields in this table is labeled “Amount Required”. This field is a value calculated by laboratory analysis to show how much of the specified inhibitor component is needed to avoid hydrate formation (in moles or mass depending on the selection base) Added by.

  The user can analyze the additional effects of the inhibitor via the information displayed on the phase diagram, for example by comparing several different scenarios at the same time. The system can provide an output corresponding to the optimal inhibitor concentration / volume given by certain rules (eg, most efficient and lowest hydrate formation, etc.). The user can also handle the moisture content of the stream being analyzed to analyze the effects of different conditions-the system will also work to provide optimal conditions to achieve a specific objective. It may be possible to adjust this value.

  FIGS. 28 and 29 show two examples of a laboratory analysis graphic interface envelope page 120 for detailed phase envelope analysis. The envelope page 120 displays various envelope experiments for each of the component groups as well as the envelope experiments created for the user. The main page for each envelope “experiment” shows the envelope-important results. This can include many plots and many result sets per plot. Numerical results (such as critical points) can also be provided. In the example described in FIG. 29, the envelope is divided into component groups (which tie the stream to the same component). Selecting each component group will display its respective envelope curve and all operating points of the included stream. Any number of custom envelope experiments can be created using the “Add Envelope Experiment” button. An option called "Envelopes-Combined" is provided that displays the envelopes for all component loops simultaneously.

  Within the settings page, the user can determine which streams are available for laboratory analysis and which streams are displayed (eg, in an envelope plot in the summary page). It supports multiple plots with any number of streams on each plot per view. The user can also decide to plot using many different property packages. The plot also includes any number of baselines for each stream. In general, the simulator plots a curve for only the current stream component and presents a new curve to the user each time the stream component changes due to other changes in the simulation. It may be difficult to see the effect of the change because the original curve is not shown. The laboratory analysis graphic interface allows the user to save any curve as a baseline and allows both original and new curves to be shown. For some operations (such as adding a hydrate inhibitor), such a baseline curve is created automatically.

  A laboratory analysis graphic interface hydrate page 130 for detailed hydrate analysis is shown in FIG. The user can set up any number of hydrate experiments 132. The main results page for each experiment contains hydrate formation plots (with or without phase envelope) and some numerical results based on how each experiment was set up. Hydrate is calculated by a suitable engine and in particular includes hydrate phase component results.

  Within the settings page, the user can perform advanced hydrate tests (eg, hydrate estimation at stream conditions, stream conditions with +2 kg / hr injection of methanol, formation temperature at stream pressure in both of these settings) Can be defined. The user can easily set up many different experiments per hydrate group shown in the laboratory analysis view.

The type of experiment can include:
-Formation at stream conditions-Formation temperature at specified pressure-Formation pressure inhibitor at specified temperature can be further added to each of these experiments via a settings page.

  A laboratory analysis graphic interface distillation curve page is provided for detailed distillation curve analysis. The distillation curve is shown in this page along the same line as the envelope curve. A baseline curve can be used. Numerical results are shown on the summary page. Multiple stream / multiple plot combinations per “experiment” are supported. The user can select which type of distillation curve is of interest in the setting part of each experiment.

More than wax formation, asphaltenes, CO ₂ freezing, low temperature properties (viscosity, cloud point, pour point, and octane number, Reid vapor pressure, or other properties used in traffic fuel or pipeline specifications, etc. Other functionalities such as low temperature fluidity, including general low temperature properties), and critical properties can be provided and reported. Property table utility functionality can also be provided and reported. Combining these functional elements provides a centralized analysis platform for process simulation that can avoid more distributed reports and is more powerful and easy to use.

  An engine for calculating phase analysis results, such as hydrate formation, may not necessarily support the same number of phases as a process simulator. For example, an engine for calculating phase analysis results can support seven different phases (including a hydrate phase, a wax phase, and various solid phases), whereas a process simulator is a steady state simulation. It only supports 4 phases in, or 3 phases in dynamic process simulation. In order to fully integrate the phase analysis engine for the laboratory analysis Ul, the process simulator can support any number of phases. Streams and fluid objects can handle any number of phases in structure. The separation routine that drives the separation in the container is adapted to precisely separate liquid phases.

Character matching is provided to assist the user with laboratory analysis tools for process simulation. Once the characteristics of the fluid have been determined in the laboratory analysis, the user can then take the form of dew point, boiling point, gas / oil ratio, viscosity, and concentration curves (similar to wax, asphaltenes, and other phase formation measurements). One can attempt to match the characteristics of the fluid being analyzed to the measured test values. The user can enter for example many P, T and characteristic points (obtained from actual measurement results)
The characterization routine within the laboratory analysis then adjusts the characterization in an attempt to match those measurements. Character matching can be provided for any characterization method.

  Engines and process simulators for the calculation of phase analysis results generally have the ability to mix fluids that have two or more different characteristics and generate a third fluid with the combined characteristics of the two fluids have. The manner in which mixing is performed may differ between the phase analysis engine and the process simulator. For example, the process simulator may include separate mixing rules for each property being mixed and a consistent set of cut points for all streams involved in the mixing process. it can. In contrast, the phase analysis engine's mixing routine can process all properties in the same way, and can also handle fluids with different cuts, and a separate set of fractions for the mixed fluid. (Ie, to say, you can mix streams with different ingredient lists and regenerate different ingredient lists for the mixed fluid). Since the mixing phase analysis engine may also be told by the user how to cut the mixed fluid, it is completely flexible in that way. Due to the different nature of the mixing calculation, the results can vary depending on whether the user mixes two oils in a phase analysis or creates the same two oils in a process simulation, and then You can use a process simulator mixer to mix.

Other aspects and features In addition to certain preferred aspects and features of the invention as set forth in the appended claims, as well as in the introductory section above, the invention includes the following additional aspects, features, and implementations. Forms or features may be provided, which may be combined in any suitable manner with the previously mentioned aspects and features.

  According to one aspect of the present invention, a method for facilitating simulation of an industrial process, applicable to any simulation, creating, storing and storing at least one rule defining operation A method is provided that includes receiving process information defining a process, applying the rules by simulating the process based on the received process information and performing the prescribed operation. Application of rules to process simulation can be reused and standardized, resulting in quality maintenance and efficiency. A rule may define an operation or action under defined conditions, for example. A rule (also referred to herein as a workflow) may be referred to as a function, task, instruction or procedure. Preferably, the defined operation is performed for at least one of an input to the simulation, execution of the simulation, and output of the simulation.

  Process information may include various types of process information, including process topography, process parameters, and process variables. Process topography preferably determines the components and their connections. Process parameters are preferably used in the simulation to determine process variables. Prior to the simulation, there may be unknown process information. Simulation results can be part of the process information after simulation. Process information can include data from previous simulations and / or historical data including measurement data previously obtained from real processes. The process information may be associated with a stream, product, component or unit, component operation, component group, component operation group, process subgroup, or process.

  Process information includes, for example, independent variables, independent parameters, dependent variables, dependent parameters (eg, with dependency on other independent parameters), default variables, default parameters, topographic variables, topographic parameters, thermodynamic variables, thermodynamic parameters Material variables, material parameters, stream variables, stream parameters, physical constants, relationships, operating costs, capital expenditures, costs, selling prices, period discount factors, currency and / or (metric) units.

  For standardization, the rules preferably define the conversion to the desired unit of measure, and applying the rules preferably includes converting the process information received from the user to the desired unit of measure. . In order to add custom calculations, ensure uniform application and avoid human error, the rules preferably specify calculations for adapting process parameters, and conditions for performing those calculations, Applying the rules preferably includes adapting the process parameters in response to calculating whether the condition is met. For the implementation of know-how and heuristic knowledge, the rules may specify suitable process information, and applying the rules preferably adapts the process information received from the user to the suitable process information. Can be included. For adaptation to a user's “best case” design, suitable process information may include the performance, configuration, specifications, capabilities, and / or topography of the component or component group. Applying the rules can further include adding additional components or component groups to the process topography and / or removing components or component groups from the process topography. Applying the rules further includes providing notification of adaptation to the user, providing only process information suitable for user selection, and / or providing an alert requesting user adaptation. be able to.

For the convenience and ease of user control, the rules preferably specify warning conditions, and applying the rules preferably depends on the occurrence of the warning condition, preferably when the warning condition occurs. At least one of interrupting the simulation, providing a report of the occurrence of a warning condition to the user, or waiting for instructions from the user to revise the simulation, interrupt the simulation, or continue the simulation. Including one. For ease of simulation monitoring and rule application, warning conditions are defined as process information limits, threshold values above and / or below process information values, conditional values, and conditional conditions based on the occurrence of an event. It may be associated with calculations based on values and / or simulation results. For ease of checking and reliability, a warning condition can specify a process information value, and applying a rule determines whether the process information value is exceeded or approached in the simulation. Generating and providing notifications can be included. The preferred approach is
It is within a certain percentage range (for example, 90%, 95%, 99%) or within a certain value range (for example, 5 units, 1 unit, 0.5 units).

  For optimization of simulation results (including maximization and minimization), the rules preferably include at least one variable of process information to be optimized and at least one parameter and / or topography of changing process information. Defining the optimization associated with and applying the rule preferably includes optimization of the variable under changes in at least one of the parameters and / or topography.

  In order to determine information that is not otherwise available in the process simulation, the rules preferably define the calculations that are performed on the process information values, and applying the rules preferably Including applying to process information values. For access to external resources, the rules preferably define an external system and process information received from the external system, and applying the rules preferably imports data from the external system and processes Including using it as information. For compatibility with external resources, the rules preferably specify the external system and process information submitted to the external system, and applying the rules preferably exports the process information to the external system. Including doing.

  For conditional adaptation of the process being simulated and optimization of the process, the rules preferably define changing process information, and applying the rules preferably accounts for changes in changing process information. Including. For the automation of a series of simulations and user ease and convenience, rules preferably define the operations to be performed, conditions, and changing process information, and applying the rules preferably Including performing an operation when the condition is met under change. This avoids human error and improves accuracy and uniformity.

  For efficiency and redundancy avoidance, the operation performed may save a simulation result, the condition including a comparison of the simulation result of the current process variable with the simulation result of the previous process variable. But you can. For selective storage of specific cases, the executed operation may store simulation results, the condition being a comparison of the simulation result value with a limit value or target value for the process information value. May be included.

  For ease of analysis of alternatives, the rules preferably specify at least two alternatives for process information and comparative criteria, and applying the rules is preferably based on the comparative criteria. A comparison of the simulation results of the alternatives. Alternatives may be associated with alternative process information, alternative process variables, alternative process parameters, and / or alternative process topography. For alternative conditional selection and process optimization, the rules may further specify selection criteria for one of the alternatives based on the comparison, and applying the rules may result in the simulation results of the alternatives. It may further include a selection of alternatives based on the selection criteria being applied to the comparison.

  In order to analyze the results of the selection following the selection of alternatives, the process information is preferably adapted according to the selected alternative.

  Preferably, the plurality of rules are combined to form a decision tree. As a result, sophistication and user control can be enhanced.

  To adjust the simulation, the rules preferably define a solver (or solution) for the simulation, and applying the rules preferably includes using the solver to simulate the process. . Thus, a specified solver may be associated with a particular unit, stream, or subgroup, for example.

  For uniform execution, convenience, and reliability of tasks, rules preferably define an operation or set of operations, and applying the rules is preferably prior to simulating the process. Or optionally waiting for their completion without simulating the process. For efficiency and redundancy avoidance, this method determines whether results from previous simulations of the process are usable, and if such results are available, the application of the rule It further includes determining whether to affect the simulation result and simulating the process if the rule affects the simulation result.

  Due to the ability to adjust, the method may further include adaptation of rules depending on the process simulation results. Due to its adaptability, the application of rules can generate new rules for application to simulation. For flexibility, application of the rules may be mandatory or user selectable.

  For uniformity over multiple users working on the same category of work, one or more rules are preferably associated with a category and process information is designated as belonging to that category. If so, the one or more rules associated with the category are applied. Preferably, the category is associated with a process type, project, user, or process owner. All processes undertaken by one or more users, where one or more rules may be associated with one or more users for the ability to coordinate reflection of user knowledge and pool knowledge within a group of users The simulation can follow the associated rules.

  For compatibility with external resources, the method may further include receiving data from the external system and / or transferring the data to the external system. Preferably, if applying the rules includes adaptation or change of process information, the original process that has not changed based on process information that has not changed is based on process information that has been applied or changed, Simulated as well as adapted or unusual processes. This allows for comparison and control of changes caused by the application of rules.

  For user control over how the simulation is affected by the rules, this method provides a report specifying the rules applied to the simulation and / or the rules that resulted in adaptation or change of process information May further be included.

For inclusion of rule metadata, the method further includes recording information associated with receipt of the rule from the user, including a receipt timestamp, a user identifier, a unique rule identifier, and / or a user annotation. May include. Thereby, rule management (including rule search) can be facilitated. For the inclusion of rule metadata, this method was brought about by a grouping or application timestamp to the simulation, a user identifier associated with the simulation or rule grouping, and / or a rule in the simulation. Including adaptation or change,
It may further include recording information associated with applying the rules to the simulation or grouping the rules. Thereby, rule management (including rule search) can be facilitated.

  For efficiency and convenience, the method may further include generating an executable that can execute the rules.

  For efficiency and convenience, the method may further include accessing a database, providing data to the database, and / or receiving data from the database. For efficiency and convenience, the method may further include accessing external software, providing data to the external software, and / or receiving data from the external software. For compatibility, the rules preferably include designation of an interface module that is suitable for receiving action specifications from further simulators. This makes it possible to define rules upstream (for example, reservoir simulation) or downstream (for example, market price simulation). This allows the external system to drive the simulator as a “black box” by convention.

  For ease of use, the rules are preferably created by the user through a graphical user interface. For versatility, the method preferably further includes receiving from the user a rule that operates with and / or on the input. For versatility, the method preferably further includes receiving from the user the rules that operate with and / or on the outputs. For versatility, the method preferably further includes receiving an action definition from the user.

  For ease of specification of user rules, the method preferably further includes providing process information associated with a process for user specification of the rules. For ease of specification of user rules, process information may be selectable by the user by drag and drop and / or drop-down menus and / or input fields and / or point and click.

  For adaptability, the rules are preferably created by the user via the command language. For efficiency and convenience, the method may further include providing an interface for entering a command language. For efficiency and convenience, the rules may be created by the user's selection of preset rules provided to the user for selection. The method may also include providing a preset rule for the default application without selection by the user. Pre-set rules can be entered by interface or command language. For reliability and versatility, the preset rules may or may not be modifiable by the user. The preset rule may provide the rule details to the user or hide the rule details from the user.

  For clarity and ease of use, the method preferably provides an indication of whether the process information conforms to the rules, changes introduced by the rules, and / or alternatives for the process information provided by the rules. Further comprising providing. For clarity and ease of use, the instructions can include listing, sorting, coloring, and / or displaying symbols.

  In order to avoid storing data more than necessary, receiving a rule from the user preferably includes receiving an indication of the data stored when the rule is applied.

  For convenience, the method preferably further includes providing an indication of the progress of rule application and / or the progress of the simulation. For clarity and convenience, the method may further include providing a series of simulation results, and may provide the ability to review any result in the series in detail.

  Multiple rules may be combined for the ability to adjust. Due to the ability to coordinate, the rules may be combined in a nested manner, dependent on each other and / or independent of each other. Preferably, rules for selecting process information, rules for filtering the selection of process information, and rules defining actions to be performed in connection with the filtered selection of process information Are combined. This combination is efficient and intuitive for tailoring particularly sophisticated rules.

  For analysis of the effects of factors that change over time, rules can specify the time-dependent characteristics of process information, and applying rules can simulate processes under changes in the time-dependent characteristics of process information May be included.

  According to a further aspect of the invention, a method for facilitating simulation of an industrial process, comprising receiving process information defining a process for simulation and defining time dependent characteristics of said process information A method is provided for creating and storing rules and simulating the process based on the received process information depending on the time-dependent characteristics of the process information. According to a further aspect of the invention, there is provided a method for facilitating simulation of an industrial process that receives process information defining a process for simulation and defines time-dependent characteristics of the process information. A method is provided for creating and storing rules, changing the time-dependent characteristic, and simulating the process based on the received process information in dependence on changing the time-dependent characteristic.

  According to a further aspect of the invention, a method for facilitating simulation of an industrial process, comprising receiving process information defining a process for simulation and defining time dependent characteristics of said process information A method is provided for creating and storing rules and simulating the process based on the received process information depending on the time-dependent characteristics of the process information. Changes in the time-dependent characteristics of the process information make it possible to analyze the influence of factors that change over time.

  Application of rules to process simulation can be reused and standardized, resulting in quality maintenance and efficiency. A rule may define an operation or action under defined conditions, for example. A rule may also be referred to as a function, task, instruction or procedure. Process information may include various types of process information, including process topography, process parameters, and process variables. Process topography preferably determines the components and their connections. Process parameters are preferably used in the simulation to determine process variables. The process information may be associated with a stream, product, component or unit, component operation, component group, component operation group, process subgroup, or process.

  Process information includes, for example, independent variables, independent parameters, dependent variables, dependent parameters, default variables, default parameters, topographical variables, topographical parameters, thermodynamic variables, thermodynamic parameters, material variables, material parameters, stream variables, stream parameters Physical constants, relationships, operating costs, capital expenditures, costs, selling prices, period discount factors, currency and / or (metric) units.

  For speed and ease of analysis, the simulation is preferably a steady state simulation of a quasi steady state process. Simulation results can affect subsequent simulations to account for process changes. Preferably, the rule includes a time step size in response to changes in the time dependent characteristics. This makes it possible to adapt time-series resolution and selection of an appropriate trade-off between speed and resolution. The minimum time step size is preferably 1 day. This avoids inaccuracies due to the quasi-steady state assumption not being useful. The time step is preferably week, month, year or 10 years. For computational efficiency, the time step size may be variable. For example, the time step size may be shorter with a high rate of change and the time step size may be longer with a low rate of change.

  For the analysis of the desired period starting and / or ending at the desired time, the rules are preferably time periods according to changes in start time, end time, end condition, number of time steps and / or time dependent properties. including.

  For versatility and utility, the time dependent property is preferably a process parameter and / or a process topography. The time dependent process parameters may be pressure, flow rate, temperature, composition, dew point, true vapor pressure, Wobbe index and / or all other characterization characteristics or parameters. This allows consideration of process information that is particularly susceptible to changes over the life of the treatment facility.

  For ease of entry and specification, time-dependent characteristics are preferably specified by a set of discrete time / characteristic pairs such as a table or list. A time step corresponding to a discrete time set may be used. The time steps may be selected to match the discrete time set, or they may be selected to be different from the discrete time set. For ease of entry and specification, the time step is preferably adapted according to a discrete time set. For accuracy, the method may interpolate between the first and second provided time-dependent characteristic data to determine unknown time-dependent characteristic data. This makes it possible to estimate time-dependent characteristics when the time step is different from the discrete time set.

  For ease of entry and specification, the time-dependent characteristics are preferably a continuous set of time / characteristic pairs such as curves or mathematical functions. For convenience, time dependent properties may also be received by an interface to an external source.

  Preferably, the rule specifies the time, period and / or condition associated with the process information, and an alternative for the process information, and applying the rule ends the period and / or the condition is met Including applying alternatives at that time. This can allow for events such as periodic maintenance, installation and / or replacement of process components, or implementation of process measurement results generally in response to changes over time. The condition may be, for example, a process variable that intersects the threshold or a process parameter that changes over time across the threshold. The process alternative may be, for example, a process parameter alternative, a process topography alternative, and / or a process variable alternative.

  The rule may further specify a maintenance cycle, and applying the rule may include applying a topography alternative to the duration of the maintenance cycle and returning to the previous topography at the end of the maintenance cycle. Thereby, for example, it is possible to return to normal operation after completion of regular maintenance.

  For accuracy, the time dependent characteristic may be component performance degradation. Components may include equipment and / or materials (such as catalysts). For accuracy and realistic results, the time dependent property may be a reduction of the supply reservoir.

  For extensive perspective analysis, the rules preferably specify at least one process information value to be accumulated, and applying the rules preferably includes the accumulation of process information values across a simulation. The accumulated process information value may be a resource input and / or a resource output. The accumulated process information value may include at least one of a power requirement, a production amount, and a consumption amount. The rule can specify an accumulated merit value based on the process information value, and the merit value includes at least one of a capital cost, an operating cost, a supply cost, a processing cost, and a process product value. This enables long-term merit analysis. The merit value preferably depends on a process information value including at least one of a resource component, a resource flow rate, a resource heating value, and a resource Wobbbe index. This allows the inclusion of accuracy and further factors in the calculation of the accumulated merit. For accuracy and realistic results, the rules can further specify penalty calculations for deviations from production sharing parameters and / or target values, and applying the rules is a process for accumulation. Information value adaptation and / or merit value adaptation may further be included. The rules preferably further specify calculation of merit values based on process information values.

  For ease of effect comparison and review, the rules preferably specify the process information of interest, and applying the rules preferably records the process information of interest at each change in time-dependent characteristics, Providing an indication of the transition of the process information of interest under changes in the time dependent characteristics may be included. For convenience, the display may include charts, plots, lists, tables and / or graphs. Preferably, the method further includes providing an indication of the transition of the cumulative value of the process information of interest. Thereby, further information content can be provided.

  In order to monitor the extreme, the rule can specify the process information of interest, and applying the rule records the upper and / or lower limit assumed by the process information of interest under the change of time-dependent characteristics And displaying. For accuracy and analysis of benefits, the rules may specify period, cost information and / or revenue information in relation to resource input, resource output, operating costs and / or capital investment, and Computing net present value, total cost and / or total profit for the period.

  For computational efficiency, time-dependent characteristics may be associated only with process subgroups for simulation, and changes in time-dependent characteristics and simulations may be limited to associated subgroups.

  For ease of use, rules are preferably created by an event definition interface and / or a result definition interface. The event definition interface may be for user specification of time-dependent process information. The result definition interface may be for user specification of the level of results stored at a time step. For ease of use, the method preferably further includes providing a progress display interface and / or a result display interface. For example, the progress display interface may display messages about time steps and diagnostic information. The result display interface may display tables, charts, plots, and other displays.

  For clarity and ease of use, the method preferably further includes providing an indication of whether the process information complies with the rules. The method may further include providing an indication of the change caused by the rule.

  Preferably, the method further includes receiving a selection of a process flow portion and a selection of a phase analysis, and performing a selected phase analysis for the selected process flow portion.

  According to yet a further aspect of the invention, a method for facilitating simulation of an industrial process, receiving process information defining a process for simulation, simulating the process based on the received process information, A selection of a simulated process flow portion and a phase analysis selection are received, and a selected phase analysis is performed on the selected process flow portion.

  By performing the phase analysis on the process flow part, it is possible to combine the analysis of the phase characteristics with the simulation. Benefits can include efficiency and ease of use. The selection of the process flow portion may include a stream in a continuous process or a collection of things in the case of a discontinuous process. The phase analysis is preferably related to the phase characteristics of the flow portion. Performing phase analysis on the process flow portion can be particularly beneficial in the case of complex configurations of the process flow portion.

In order to study the operating point in the process, the phase analysis preferably determines the determination of the phase envelope, determination of solids formation information, determination of distillation information, determination of fluids with matching properties and / or flow guarantee. Including that. The solid product, for example hydrates, asphaltenes, wax may comprise frozen C0 _2.

  For ease of review, the method preferably selects a further simulated process flow portion, performs a selected phase analysis for the further process flow portion, and results of the phase analysis from the process flow portion. Further comprising providing a comparison of This makes it possible to study flow transitions throughout the process. For ease of review, the comparison preferably includes overwriting the results or providing the results side by side.

  Preferably, the method further comprises selecting a further phase analysis, performing a further phase analysis for the selected process flow portion, and providing a comparison of the phase analysis results from the process flow portion. . For ease of review, the comparison may include overwriting the results or providing the results side by side.

For accuracy, the phase analysis may include an assessment of the phase components of the complex mixture, preferably under a range of physical conditions. The physical state range may be a pressure, volume and / or temperature range. Phase components may be evaluated by black-oil equations, oil analysis and / or solids generation analysis. The solid production analysis may include an estimate of solids or solid production rate. The solids production analysis is preferably associated with conditions that correspond to conditions in the process flow portion. The solid production analysis preferably determines the solid production temperature for a given pressure, or the solid production pressure for a given temperature. Solid production can include, for example, hydrates, asphaltenes, waxes, frozen CO ₂ . The solid production analysis preferably includes determining solid production when a solid inhibitor is added and / or a mixing equation. In the case of hydrate formation analysis, the hydrate inhibitor may include methanol or glycol.

  The phase analysis may further include an evaluation of the critical properties, critical points and / or flash points of the composite mixture. The flash point assessment may include a flash point calculation for the mixture and / or a flash point calculation for the components. Phase analysis may further include an assessment of the physical properties of the composite mixture. The physical properties of the composite mixture may include low temperature properties.

  For ease of specification of user rules, the method may further include process information for the simulated process for user selection of the process flow portion. Preferably, one or more process flow portions are user selectable by drag and drop, drop down menus, input fields, and / or point and click. Thereby, it is possible to provide easy specification of user rules. For user convenience and ease of analysis, the method may further include a graphical plot of the analysis results and / or display of numerical values of the analysis results.

  For versatility, the phase analysis preferably evaluates multiple phases, preferably more than three phases, more preferably more than four phases, and even more preferably more than seven phases. The plurality of phases may be solid, liquid and / or gas and include a plurality of liquid phases and / or a plurality of solid phases.

  For verification and reference, the determination of a fluid with matching properties preferably receives the fluid property information and compares it with property information from a sample of the measured fluid and the closest measurement Determining a sample of the treated fluid.

  According to yet a further aspect of the invention, a method is provided that includes applying a workflow to a process simulation of an industrial process.

  According to yet a further aspect of the invention, an apparatus for facilitating simulation of an industrial process, optionally applicable to any simulation, and generating and storing at least one rule defining operation. A configured module, and optionally a module configured to receive process information defining a process for simulation, and optionally configured to simulate the process based on the received process information. There is provided an apparatus comprising a simulator configured and a module configured to apply the rules to a simulation by performing a prescribed action.

  According to yet a further aspect of the invention, an apparatus for facilitating simulation of an industrial process, optionally a module configured to receive process information defining a process for simulation, and optionally A module configured to create and store at least one rule defining a time-dependent characteristic of the process information; and the process information received under a change in the time-dependent characteristic of the process information And a module configured to simulate the process based on the above.

  According to yet a further aspect of the invention, an apparatus for facilitating simulation of an industrial process, optionally a module configured to receive process information defining a process for simulation, and optionally, A module configured to simulate the process based on the received process information; a module configured to receive a selection of a flow portion and a phase analysis of the simulated process; and the selected process And a module configured to perform the selected phase analysis for a flow portion.

  According to a still further aspect of the invention, a method is provided for designing and / or building a portion of an industrial processing facility using the output of the simulation described above.

  According to a still further aspect of the invention, there is provided a method as described above, which is executed by a microprocessor. According to yet a further aspect of the invention, there is provided a processor configured to perform the method described above.

  According to a still further aspect of the invention, a method for designing and evaluating a facility is provided, including the method described above.

A workflow-based embodiment can provide any of the following functions:
Rule-based framework in which simulation is embedded Framework for simulation operations (before, during, or after simulation) The framework framework persists across simulation cases and users-reusable Uniform, reproducible and convenient.
The same individual operations that can be performed manually by the user. The complex operation of the simulation is allowed by connecting the individual operations with the logic.
-Ability to save and publish the framework.

An embodiment of a time series simulation can include any of the following functions:
• Time stepping for steady state simulations • Long-term review of processes • Calculation of merit values for cumulative processes • Consider changes over time.
Laboratory analysis tool embodiments can include any of the following functions.
• Side-by-side analysis across partial processes • Impact of solid inhibitor additions • Determination of the amount of inhibitor needed to avoid hydrate formation.

  It will be understood that the present invention has been described above purely by way of example, and modifications of detail can be made within the scope of the invention.

  Each feature disclosed in the description and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination.

  Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.

Claims (55)

A computer-implemented method of simulating an industrial process,
Creating and storing a simulation workflow that includes multiple rules that specify the processing behavior associated with the input to the simulation or the execution or output of the simulation;
Receiving process information defining an industrial process for simulation, said process information specifying a process topology including process components and connections between process components and associated process parameters; ,
To execute the simulation workflow,
Applying the specified rule, wherein for at least one of the rules, applying the rule includes receiving the process information from the rule to change the process topology and / or parameters. To make corrections based on
Invoking a process simulator to perform a computer simulation of the industrial process based on the modified process information;
Generating and outputting simulation result data based on the executed simulation.   2. A method according to claim 1, wherein the industrial process is a process for chemical treatment, preferably a hydrocarbon or petrochemical treatment, and the process component preferably comprises chemical treatment equipment.   The method according to claim 1 or 2, further comprising designing and / or building a part of an industrial processing facility based on the output simulation results.   Applying the rules includes adding additional components or component groups to the process topography and / or removing components or component groups from the process topography. 4. The method according to any one of 3.   The rules define at least two alternatives for the process information and a comparison criterion, and applying the rules includes a comparison of simulation results of the alternatives based on the comparison criterion 5. A method according to any one of claims 1 to 4.   Executing the simulation workflow includes activating the process simulator to execute a plurality of simulations of the industrial process based on different versions of the process information generated based on the simulation rules. 6. The method according to any one of claims 1 to 5, comprising:   The simulation workflow rule specifies adaptation of the process information according to first and second process topologies, and executing the simulation workflow performs a first simulation based on the first process topology; The method according to claim 1, further comprising activating the process simulator to perform a second simulation based on the second process topology.   The method according to any one of claims 5 to 7, comprising performing analysis and / or comparison of processing result data of each of the plurality of simulations.   The rules further define selection criteria for selection of one of the alternatives based on the comparison, and applying the rules further applies the selection criteria applied to the comparison of the simulation results of the alternatives. 9. A method according to any one of claims 5 to 8, further comprising selecting one of the alternatives based on.   Following selection of an alternative, the process information is adapted in accordance with the selected alternative, preferably a subsequent workflow rule is applied and / or a simulation is performed based on the adapted process information. 10. The method of claim 9, wherein:   At least one rule defines an optimization associated with at least one variable of the process information to be optimized and at least one parameter and / or topography of the changing process information, and applying the rule 11. A method according to any one of the preceding claims, comprising optimization of the variable under changes of at least one of the parameters and / or topography. The rules are
A rule defining conversion to a desired unit of measure, wherein applying the rule includes converting process information received from a user to the desired unit of measure;
A rule defining a calculation for adapting a process parameter and a condition for performing the calculation, wherein applying the rule determines a process parameter according to the calculation of whether the condition is satisfied. Rules including adapting, and
Rules defining preferred process information, wherein applying the rules adapts the process information received from a user to the preferred process information, preferably the preferred process information is a component or component Rules including at least one of the group's performance, composition, designation, capability and / or topography;
A rule defining a calculation to be performed on a process information value, wherein applying the rule includes at least one of rules including applying the calculation to the process information value The method according to any one of claims 1 to 11.   The rule includes a rule that specifies a warning condition, and applying the rule is preferably in response to the occurrence of the warning condition, preferably interrupting the simulation when the warning condition occurs, the user Providing a report of occurrence of the warning condition or waiting for instructions from the user to revise the simulation, interrupt the simulation or continue the simulation. 13. A method according to any one of claims 1 to 12, characterized in that   The warning condition specifies a process information value and applying the rule generates and provides a notification in the simulation whether the process information value has been exceeded or approached. 14. The method of claim 13, comprising.   At least one rule defines an external system and process information received from or submitted to the external system, and applying the rule imports data from the external system to process information 15. A method according to any one of the preceding claims, comprising using the process information or exporting the process information to the external system.   A rule specifies the operation to be performed, the condition, and the process information to be changed, and applying the rule means that the operation is performed when the condition is satisfied under a change in the process information. 16. The method according to any one of claims 1 to 15, comprising:   The method according to claim 1, wherein a plurality of rules are combined to form a decision tree.   18. A rule as defined in any one of the preceding claims, wherein a rule defines a solver for the simulation, and applying the rule includes using the solver to simulate the process. the method of.   If one or more rules are associated with a category and process information is specified as belonging to the category, the one or more rules associated with the category are applied, and the category is preferably a process. 19. A method according to any one of the preceding claims, wherein the method is associated with a type, project, user or process owner.   The method according to any one of claims 1 to 19, further comprising generating an executable form capable of executing the simulation workflow.   21. A method as claimed in any preceding claim, wherein rules are created by a user in a command language, and the method preferably further comprises an interface for entering a command language.   Multiple rules are optionally combined in a nested manner, dependent on each other and / or independent of each other, preferably a rule for selection of process information, a filter on said selection of process information 22. The rules for applying and the rules defining the actions to be performed in connection with the filtered selection of process information. The method described in 1. At least one rule defines the time-dependent characteristic of the process information, and applying the rule includes simulating the process under a change in the time-dependent characteristic of the process information;
To perform a simulation of the industrial process based on the received process information for each of a plurality of time steps based on the specified time step size, with a time dependent property that is changed as defined by the rule. The method according to claim 1, further comprising: executing a process simulator. A computer-implemented method of simulating an industrial process, receiving process information defining an industrial process for simulation, the process information comprising: a process component and a process component and associated process parameters; Specifying a process topology that includes connections between
Creating and storing at least one rule defining a time-dependent characteristic of the process information, wherein the rule specifies a time step size according to a change in the time-dependent characteristic; ,
Simulating a process based on the received process information under a change in the time-dependent characteristic of the process information, the simulating the time-dependent being changed as defined by the rules Running a process simulator to perform a simulation of the industrial process based on the received process information for each of a plurality of time steps based on the specified time step size according to characteristics. Feature method.   25. A method according to claim 23 or 24, wherein the time-dependent characteristic is related to performance degradation of equipment components or a reduction in supply reservoir.   26. A method according to any one of claims 23 to 25, wherein the simulation is a steady state simulation of a quasi steady state process.   27. A method according to any one of claims 23 to 26, wherein the result of a simulation affects subsequent simulations.   28. The rule according to any one of claims 23 to 27, wherein the rule includes a start time, an end time, an end condition, a number of time steps and / or a time period corresponding to a change in the time-dependent characteristic. the method of.   The time-dependent characteristic is a process parameter and / or process topology, preferably the time-dependent process information includes flow rate, component, pressure, temperature, dew point, true vapor pressure, wobbe index, operating parameter and / or characteristics. 29. A method according to any one of claims 23 to 28, wherein the method is a weighting parameter.   24. The time-dependent characteristic is optionally specified by a table or list with a set of discrete time / characteristic pairs, preferably using a time step corresponding to the discrete time. 30. A method according to any one of 29.   31. The method of any one of claims 23 to 30, further comprising interpolating between first and second provided time-dependent characteristic data to determine unknown time-dependent characteristic data. the method of.   32. A method as claimed in any one of claims 23 to 31 wherein the time-dependent characteristic is optionally specified by a curve or mathematical function by a continuous set of time / characteristic pairs.   33. A method according to any one of claims 23 to 32, wherein the time dependent characteristic is received by an interface to an external source.   The rule specifies a time, period and / or condition associated with process information, and an alternative for process information, and applying the rule means that the period ends and / or the condition is met 34. A method according to any one of claims 23 to 33, comprising applying the alternative at that time.   The rule specifies at least one process information value to be accumulated, and applying the rule includes accumulation of the process information value over a simulation, preferably the accumulated process information value is a resource input and 35. A method according to any one of claims 23 to 34, wherein the method is a resource output.   36. The method of claim 35, wherein the accumulated process information values include at least one of power requirements, production, and consumption.   The rule specifies the target process information, and applying the rule further records the target process information in each change of the time-dependent characteristic, and the transition of the target process information under the change of the time-dependent characteristic 37. A method according to any one of claims 23 to 36, comprising providing an indication of the cumulative value, minimum value or maximum value thereof.   24. The time-dependent characteristic may only be associated with a subgroup of the process for simulation, and the change and simulation of the time-dependent characteristic is limited to the related subgroup. 38. A method according to any one of 37.   39. The method of claim 23, further comprising providing one or more of an event definition interface and / or a result definition interface for generating the rule, and a progress display interface and / or a result display interface. The method according to any one of the above.   40. The method of any of claims 1-39, further comprising receiving a process flow portion selection and a phase analysis selection and performing the selected phase analysis for the selected process flow portion. The method according to claim 1. A computer-implemented method of simulating an industrial process,
Receiving process information defining the process for simulation;
Simulating a process based on the received process information;
Receiving a selection of first and second flow portions of the simulated process and a choice of phase analysis;
Performing the selected phase analysis for the first selected process flow portion; performing the selected phase analysis for the second selected process flow portion;
Outputting a comparison of the phase analysis derived from the first and second process flow portions.   The phase analysis includes determining a phase envelope, determining solids production information, determining distillation information, determining a fluid with matching properties, and / or providing flow assurance. 42. A method according to claim 40 or 41, wherein:   43. A method according to any one of claims 40 to 42, wherein the first and second simulated process flow portions correspond to a flow with an inhibitor present.   44. The method of claim 43, wherein the amount of inhibitor present is determined to avoid hydrate formation.   Said phase analysis is preferably performed under a range of physical conditions, evaluation of the phase components of the composite mixture, evaluation of the physical properties of the composite mixture, and / or critical properties, critical points and / or of the composite mixture. 45. A method according to any one of claims 40 to 44, comprising an evaluation of the reevaporation point.   46. The method of claim 45, wherein the assessment of the phase components of the complex mixture is by black oil equation, oil analysis and / or solid formation analysis.   The method of claim 46, wherein the solid formation analysis comprises determining solid information in the case of addition of an individual inhibitor.   41. The phase analysis evaluates a plurality of phases, preferably more than three phases, more preferably more than four phases, and even more preferably more than seven phases. 48. A method according to any one of claims 47 to 47.   Determining a fluid with matching properties includes receiving fluid property information, comparing it with property information from the measured fluid sample, and determining the closest matching measured fluid sample. 49. A method according to any one of claims 40 to 48, comprising: An apparatus or system for simulating an industrial process,
Means for creating and storing a simulation workflow including a plurality of rules specifying processing actions associated with inputs to the simulation or execution of the simulation or output of the simulation;
Means for receiving process information defining an industrial process for simulation, the process information specifying a process topology including process components and connections between process components and associated process parameters; ,
Means for executing the simulation workflow, wherein the means for executing is configured to apply the specified rule, and applying the rule for at least one of the rules comprises: receiving the process information; Modifying the process topology and / or parameters based on rules, wherein the means for performing comprises a process simulator for performing a computer simulation of the industrial process based on the modified process information Means configured to activate
Means for generating and outputting simulation result data based on the executed simulation. An apparatus or system for simulating an industrial process,
Means for receiving process information defining an industrial process for simulation, the process information specifying a process topology including process components and connections between process components and associated process parameters; ,
Means for creating and storing at least one rule defining a time-dependent characteristic of the process information, wherein the rule specifies a time step size according to a change in the time-dependent characteristic; ,
Means for simulating a process based on the received process information under a change in the time-dependent characteristic of the process information, the means for simulating the time-dependent being changed as defined by the rules Means for executing a process simulator to execute a simulation of the industrial process for each of a plurality of time steps based on the time step size specified by characteristics. Or system. An apparatus or system for performing a simulation of an industrial process,
A means of receiving process information defining the process for simulation;
Means for simulating the process based on the received process information;
Means for receiving a selection of first and second flow portions of the simulated process and a selection of phase analysis;
Means for performing the selected phase analysis for the first selected process flow portion;
Means for performing the selected phase analysis for the second selected process flow portion;
Means for outputting a comparison of said phase analysis derived from said first and second process flow portions.   50. A method of designing and / or building a part of an industrial processing facility using the output of the simulation according to any one of claims 1 to 49.   50. Preferably comprising means (for example one or more software modules and / or suitably programmed processors) for performing the method according to any one of claims 1 to 49. 53. The apparatus or system according to any one of claims to 52.   50. A computer program product or non-transitory computer readable medium comprising software code configured to perform the method of any one of claims 1 to 49 when executed.