Asset Data

Assets are items associated with sites, buildings, floors or rooms. Each may optionally include its location. Asset data is accessed by the Space Manager and Map Enquiry modules. Each asset item is described by a row in a database table and optionally one or more image files or other associated documents.

One or more asset database tables may be defined using AssetTable* settings. Each table stores a different category of asset (for example, equipment or HAZMAT items), and may be accessed in the facility database or in other databases, as defined using DbConnectionAsset* settings. Each asset database table has the following structure:

asset_id		Asset identifier, unique in its table. This field is named after the table name, followed by _id (e.g. eq_id in table eq).
asset_std		Asset standard. Optional field. This field is named after the table name, followed by _id (e.g. eq_std in table eq).
site_id		Asset site ID, matching site.site_id in the facility database. Optional field, if absent bl_id must exist. Site assets have site_id populated and not bl_id.
bl_id		Asset building ID, matching bl.bl_id in the facility database. Optional field, if absent site_id must exist. Building assets have bl_id populated and not fl_id.
fl_id		Asset floor ID, matching fl.fl_id in the facility database. Optional field. Floor assets have bl_id,fl_id populated and not rm_id.
rm_id		Asset room ID, matching rm.rm_id in the facility database. Optional field. Room assets have bl_id,fl_id,rm_id populated.
csi_id		Asset CSI classification ID, matching csi.csi_id in the facility database. Optional field, for table eq only.
status		Asset status. Optional field, see the AssetStatusInclude setting.
bookable		Asset booking flag, value Y indicates that the asset is bookable, provided that em_id specifies a booking approver whose em.email is defined. Required field, for table eq only, if the Asset Bookings module is used. Field name may be overridden using the AssetBookEnabledField setting.
booking_comments		Asset booking approval comments, included in notification email.
em_id		Asset booking approver, matching em.em_id in the facility database. Required field, for table eq only, if the Asset Bookings module is used.
name		Asset name. This is displayed in asset search results, and asset searches match search terms in this field. If the asset table has a field for which sisfm_flds.sisfm_type=2055 (Desc) then the asset name is instead accessed from that field.
x y		Asset location. Optional fields. The coordinates of the asset in units according to the MapGPSUnit setting. The AssetLatLonFields setting can be used to access fields lon lat instead of X Y.
layer		Asset map layer name field. Optional field. When the asset is selected from a Map Enquiry search result, the layer with this name will be made visible.
access_group		Asset access group, as for sisfm_flds.review_group. Optional field, if absent, or if the asset database is not the facility database, asset access control is not available.
<features>		Asset features: zero or more additional columns for any features desired. These must correspond to the AssetFeature settings. Note that the following case-insensitive feature column values are displayed specially:    true yes y    false no n nil  -    unknown (or null, or empty string)

Additional fields named xx_bl_id xx_fl_id xx_rm_id may be included to support assets for facility type XX.

For each asset table, tables asset_amenity_type and asset_amenity may be used in conjunction with AssetFeature amenity names, and different "amenity" names used, as for the amenities of rooms, etc.

Table csi is used by the Asset Bookings module (see setting AssetBookCSI).

See also Asset documents/images.