Introduction to the Sigmafine Elements

After an Element template has been created, you can create elements that are based on the template. Elements represent either physical or logical entities in your process. They exist at the Database level, and can be used in multiple Models in the database. Tools are available to build elements one at a time, or to build a large number of similar elements. You can create elements that are specific to a particular model, and that cannot be used in other Models of the database; these are referred to as 'Child Elements'.

Note: It is not recommended that you define child elements for a Sigmafine Model except in very specific situations.

Element Types

Type	Sigmafine Elements
Boundaries	Receipt points and Shipment points are of the Boundary type. Boundary objects are the anchoring points for a Model analysis.
Flows	Material flows are of the Flow type. To use a flow in multiple models, you must create it as a global element. Otherwise it is a local element. Flows are connected on both ends to tanks, process units or receipt\shipment points. Measurements (flow meters and analyzers) can be attached to flows on their undirected port.
Measurements	Meters and analyzers are of the Measurement type. Use the undirected connection on a flow or an inventory (tank) to attach Measurements.
Nodes	Inventories (tanks), manifolds and process units are of the Node type. The SF_Model is also a node type element. Nodes have an input and output port where numerous connections can be made with flow and transfer elements.
Others	Sigmafine uses the Other Element type for holding Case results (of analyses) and for holding the global factors. Note that only one Case element (SF_CaseResults) is needed per Model and one global factors (SF_GlobalFactors) Element is needed per database. These Element types do not have connections.