Overview of the Database
The latest version of the GAM database is available in versions for Oracle and MySQL. It runs under Oracle version 12 and newer and MySQL version 8.0.19 .
The main table in the database is the GAM_OBJECT table. This table represents an object, which is an individual piece of equipment used for helium management: an individual level meter, an individual cryostat, and so on.
Objects are classified into object types, which are themselves classified into object classes, which are classified into functions. There are many attributes in the GAM_OBJECT table, and many have their exact meaning determined by the class the object belongs to.
For each object, the database can store measurements whose meaning is again defined by the object class. Each object can have its own display format, which specifies the levels at which alarms are activated for the values in the measurements.
In addition, the database stores relationships between individual objects, which are used different purposes. One example is the relation between positions which represent the network of the helium recovery system. These realtions can be used for the graphical representation of the network on the web client and for analysing the Helium gas flow through the network. A second example is the relation between a device and a position localising the device in the network. A third example is the relation between a measurement module (e.g. a levelmeter) and an object (e.g. a vessel) which defines to which object the measurement finally is related to.
The database has the GAM_COORDINATE, GAM_DISPLAYGROUP, and GAM_IMAGE tables, which provide information used for the graphical UI representation of the helium management system and the and GAM_NETWORK table which allow for separate analysis and graphical representation of closed helium recovery systems.
In the GAM_VERSION table we keep track of the updates to the GAM database.
The GAM_USER table allows together with the GAM_OBJECTINFO table for the exchange of information concerning individual objects (e.g. when a vessel has to be repaired or the parameters of a vessel have to be checked).
Below you can see the Entity Relationship Diagram of the database (unfortunately outdated, has to be replaced):
