Customer Login >
Data Reconciliation
Graphical User Interface

 

 

 

 

 

 

 

dotted rule
Graphical User Interface

logo bug  Inlibra’s object-oriented graphics architecture makes it easy to create your own plant flow diagram.

logo bug  Draw process units, nodes, tanks and receipts/shipments from the tool bar by dragging and dropping.

logo bug  In the same point-and-click fashion, connect objects to each other
with stream objects.

logo bug  Each stream object contains a flow measurement tag whose value can be read from the built-in interface to Process Historians such as PHD and PI on demand.

logo bug  This user interface automatically constructs the balance equations that are necessary to reconcile raw data.

logo bug  As you change the flow diagram, it modifies the balance equations
internally to match.

logo bug  You don’t need to deal with equations -- just the graphics of the plant.

logo bug  As meters and streams go into or out of service, the model will notice. When an object is taken out of service in the flow diagram, balance equations are automatically changed to reflect the new configuration.

logo bug  You don’t have to keep up with changes daily. Unlike other systems, keeping the process model current is not a major obstacle for getting precise and updated information.

logo bug  Move the cursor over to the processes, streams or inventories: It automatically shows the flow summary with the measured and reconciled value.

logo bug  The Graphical User Interface graphically pinpoints problems by automatically changing the color of the object on the screen.

logo bug  Running the reconciliation algorithm results in a recolorization of all displayed objects based on their new status.

logo bug  Out of service streams, streams that have a gross error, and balanced streams are all shown in different colors.

logo bug  To simplify the user’s view, you can use a filter to disable the display of certain types of streams.

Object oriented graphical user interface
Figure 1 - Object oriented graphical user interface

Object oriented graphical user interface
Figure 2 - Object oriented graphical user interface, second example

Object oriented graphical user interface
Figure 3 - Colorful graphics show the DR results

dotted rule
Relative Strengths of the User Interface

Magnitude of the Model

Inlibra’s competitors often have difficulty working with large numbers of configured streams, even when the number of streams falls within the magnitude often encountered in real plants. Inlibra performs very well with large numbers of streams. Configurations with 4000 streams and 200 tanks are not unwieldy and are currently in use by customers.

Even with configurations of this size, the daily reconciliation takes about an hour of processing. This includes the time necessary to obtain the data from the real-time historian, LIMS, the oil movement database; executing the reconciliation; identifying gross errors and losses; finalization and passing of finalized results to an ERP system.

Model Connector

A common problem with other Graphical User Interfaces is that users draw their entire process in one gigantic graphic model -- and it ends up as an incomprehensibly cluttered image.

This limits the complexity of building models to size and results in high maintenance costs.

Inlibra allows you to build multiple models of maintainable sizes and provides a Model Connector. All individual models are used to construct the whole balance model, which is solved as one.

Object oriented graphical user interface
Figure 4 - Each Detail Model is connected by Connection Object

Logical Model

With an add-on Smart Object feature, Inlibra can display a logical model for plant summary report purposes. It’s defined by the user with the goal of showing key inlet and outlet values for each unit. Logical models make use of the built-in calculation ability of Inlibra’s Smart Objects to come up with the key values containing the most useful data for the unit, including key performance indicators, loss and product cost in terms of resources.

The logical model is visually separate from the balance model.

Object oriented graphical user interface
Figure 5 - Example Plant Summary Logical Model

Compare the complexity of the logical models in Figure 5 to the complexity of the physical models in Figure 4. Validation of the daily reconciliation results is normally performed from the Logical Model view of the plant, which is much simpler than the detailed physical model, thus reducing the daily effort.

Object oriented graphical user interface
Figure 6 - Further examples of Plant Summary Logical Models

dotted rule


Products >
Data Reconciliation
   Introduction >
   Robust and Accurate DR >
   Graphical User Interface >
Composition Tracking
   Introduction >
   Relationship of CT to DR >
   Technology Description >
Smart Objects
   Overview>
Stockpile Tracker
   Introduction >
   The Problem >
   What ST Provides >
   What Your Plant Needs >
   GUI Features >
   Goals of ST Design >
   Modeling Method >
   Security >

rule190Downloads (pdf)
Product Brochures
Data Reconciliation >
Composition Tracking >
Stockpile Tracker >
White Paper
What is Data Reconciliation? >
Case Studies >

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to Top >

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to Top >

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to Top >

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to Top >

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to Top >