Sections

Wiki > Sections

Description

Sections are segmentations of networks. They help to determine the use of Helium in certain regions of the network, e.g. a lab or a building. Positions and vessels can be assigned to sections with object relationships.
The amount of Helium that is lost in a section can be determined by the evaluation of

1. the difference of the weight measurements of assigned vessels,
2. the difference of the amount of gas entering and leaving the section.

Vessels can be assigned to sections by creating an object relationship with the section and performing book-in and book-out measurements with a balance (see MEA_BOOKINGCODE 3 and 4). Positions with gas counters (assigned gas counter modules) which are on the boundary of the section must set the OR_SYSTEMFEED attribute to 1 (feed) or 2 (drain) when creating the object relationship with the section. All position in the section should have an object relationship with the section.

Section class

By default, there is only one object class for the Section function in the database. That is the Section class. It has OC_ID 20.

Position type	Display priority
1	NULL

Section object type

By default, the Section object class only has one object type in the database. It is called section.

Comments

Sections must belong to a network. OB_NETWORK_ID therefore must not be NULL.

Relationships

The only objects that can be assigned to a section are positions and vessels.

Attributes

Attribute	Type	Note
OB_ID	integer
OB_OBJECTTYPE_ID	integer
OB_NAME	string
OB_COMMENT	string
OB_POSINFORMATION	string
OB_ENDOFOPERATION	date & time
OB_ENABLED1	number, 0 or 1	section is displayed on the network plan (future application)
OB_INSTALLED	date & time
OB_NW_ID	number	ID of network (must not be NULL)
OB_CODE	string, max. 100 characters	password/code for identification of users for the vessel program