GS4: Pipe-It Processes (Basic) editor
Text boxes that have no bearing on the execution of a project. They are useful in providing titles and notes to the user of the project.
Format translators from 3rd party applications to Pipe-It/Streamz stream file (*.str) format. Ecl2Str (from EclipseTM ) and Sen2Str (from SensorTM ) are shipped with Pipe-It. Large scale usage of Pipe-It with other programs are likely to result in newer App2Str utilities.
The graphical “playing field” displayed by Pipe-It. It is, by default, gray in color with an image of the Pipe-It logo in the background. There always exists the main “top level” canvas, but the user may create multiple cascading composites, each having their own canvases.
A flexible collection of components, and optionally their properties, that may be used to represent streams in stream files. Quantities of each component (of the characterization) are stored as values in stream files. Quantities may be in mass, moles, volumes, or a generic “amount”. Usually defined in simple text files that are imported into Pipe-It Streamz Library prior to use.
A brownish rectangle with round corners and double lines. Used to group logically related base elements (Resources, Processes or other Composites). Used to define the extent of execution of a part of a project.
An elbowed (or straight) line with an arrow-head defining a connection between Resources and Processes. Connections transcending composites go via sockets but can always be tracked back to the originating Resource or Process.
A translation of streams from one characterization to another. A Streamz conversion “method” is defined in a simple file and imported into the Streamz Library, automatically connecting to pre-existing in-out characterization pairs. In case of ambiguity user assistance is need. Once in the library, their usage is mostly automatic.
The Pipe-It proprietary technology that allows the user to pin-point numbers in text (and Excel) files and denote them as variables of the Pipe-It project. An intuitive and robust fingerprinting method is used customized by the user to uniquely define the location of the number with respect to surrounding “tokens”. These numbers can then be read and written by Pipe-It. Repeatedly and without regard to their original line in the file. Columns/Rows and whole matrices are supported. Text tokens too!
The customized Pipe-It process that manages mapping of Linkz variables from one resource to another (read one file to another). Enables quick and easy way to pass results of one application as input to another.
Pipe-It “supervisor” that can control multiple launches of the underlying Pipe-It model. Works with Linkz variables to cause values to written (VAR and AUX) to files before the launch of the model, or cause the values to be read (AUX, OBJ and KPI) after the completion of the model run. Can launch multiple user-specified (Case Matrix) or automated (Solver Driven) executions of the underlying model. The underlying model may be the full project or parts of it (Composites).
Is the Trondheim, Norway based company that develops and sells Pipe-It. It also offers consultancy and training around Pipe-It.
Is the software application developed and sold by Petrostreamz AS. Conceptually it allows piping together the various computational models used in a value chain, or workflow, into an integrated & automated project. Once integrated and automated, it allows the user to optimize on any key result computed by the integrated poject.
Strictly the model part of a Pipe-It project. The Pipe-It Project Model (ppm) file is the main entry point for Pipe-It’s Runner and is only needed to execute a project. For typical usage of Pipe-It, the term model is interchangeably used with the term project.
A collection of files that represent all the graphical (*.ppv) and logical (*.ppm) parts of a Pipe-It data-set. The Pipe-It Project View (ppv) file is the main entry point into Pipe-It and is the point of interaction for the user. Ppv files are associated with Pipe-It upon installation and double-clicking a project’s ppv file loads it into Pipe-It.
The command line version of Pipe-It, enabling Pipe-It to be called from any 3rd party application that can launch applications. Since Pipe-It is such an application, Pipe-It can call Pipe-It itself!
The visualization tool of Pipe-It. Runs as any 3rd party application. Can make 2-d plots of any tabulated data in text or Excel files. Can easily mix-n-match. Special handling of stream files allows users to be up-and-running with most frequent of Resources. Command line usage allows dump of scores created plots as PDF (or image) files ready for reports or presentations.
A greenish oval. Represents a launch of an application (program, script etc.) from within Pipe-It. Can only connect to Resources on input/output, never directly to another Process.
A pale-bluish rectangle with round corners. Can be dropped from the toolbar using an icon of the same appearance. Represents a file on the disk. If no file is specified, it will report a broken status to the Runner.
Often called the “brain” of Pipe-It, it is the hidden entity that come into play when the user hits the Run (or Play) button on the Pipe-It toolbar. It analyses the myriad of interconnected Pipe-It Resources, Processes and Composites and determines the most efficient way of launching the entire project. All dependencies are worked out and possibilities of parallel / sequential executions considered. It sets up the queue of resources & applications to be “run”, causing the dependent applications to be waiting for the completion of upstream portions of the project.
Connection ports that drive the connectors in and out of composites. Also the connections points on Resources and Processes. Single Input and Output sockets pre-exists on each such graphical element, more of each type can be added and renamed by the user.
A Pipe-It supplied or user plugged-in algorithm to control the multiple launches of Pipe-It from the Optimizer automatically driving the currently selected OBJ (Objective) to a maximum, minimum or first-feasible value. User specified bounds of all variables (VAR/AUX/KPI) will be honored during the optimization.
Tab-delimited text files following rules of Streamz. Contain a header section followed by stream data that can easily run into millions of streams. Each line is a single stream. Each stream contains optional “tags” of variables followed by quantity of all components making up the stream.
Is the petroleum engineering application package with Pipe-It that excels in performing efficient and consistent petroleum streams management. It is often referred to as “engine” of Pipe-It.
Copies of all streams from all incoming stream files to all connected output stream files. Unless filters are invoked. Automatically performs characterization conversions if needed.
A user specified Stream management “task” implemented as a ready-to-run Pipe-It Process. All connected stream file Resources, and their corresponding characterizations, are made available on-the-fly. The user can concentrate on writing Streamz “code” to define the non-vanilla task at hand. Great for learning and validating Streamz commands.
These are a collection of automated ready-to-run Streamz tasks embedded into Pipe-It to get the user up-and-running with streams management.
Aggregates incoming streams, whether from a single or multiple stream file to produced, usually smaller, aggregated stream files. Conversions performed automatically. Typical usage: aggregate well streams to field streams.
Stream file editor allowing manipulation of existing Streamz variables and/or components, including mathematical manipulations. All such actions are recorded in Macros that can be used on command-line mode in Pipe-It with no user interference. Sum of Squares of differences (SSQ) between columns of stream data can easily be computed allowing, for example, history matching of measured data by optimizing the computational model.