Composition Tracking - Required Tables
The Composition Tracking Analysis Rule uses a table that contains material information. The default table is the "SF_Material table." The two fields (columns) that are required to exist in the table are material and material density. The material density column can have a UOM of density or Specific Gravity (SG). The special material column and the quality column are optional.
SF_Material Table – Required Columns
| Column | UOM Class | Description |
|---|---|---|
| Material | \<none> | The name of the material. |
| Material Density | Specific Gravity or Density | The typical density or specific gravity of the material. The table default UOM is API for databases created with the Sigmafine library or kg/m3 for databases created with the SigmafineSI library |
| Special Material | \<none> | Material index for handling materials with special mixing properties. |
| Quality column 1 | Any UOM according to the quality property | Material quality property value. |
| SF_CompositionTracking | \<none> | This is an optional column of type Boolean that can be added to the SF_Material table. If this column is configured, then all material codes having this flag = False will be excluded by the Composition Tracking analysis. |
| 1 The name of this column can be assigned according the quality property. For example: |
Note:
The new feature for skipping from Composition Tracking analysis all the MATERIAL tagged with SF_CompositionTracking = FALSE in the “SF_Material Table” may trigger some unexpected and abnormal calculations since some materials may not be accounted according to user’s selection.
There might be some scenarios where the final composition may be empty even the reconciled mass of the inventory over the tank is greater than zero (e.g. tank is filled with only material not participating to the CT analysis). In this case, the next Case CT may be not able to run and user should act manually with a small adjustment for correcting this abnormal situation. This feature may have more negative consequences at reporting or visualization level. Even this option has been introduced, Pimsoft strongly suggest avoiding the usage of this option.