V2/Concepts/Asset Classes and Relationships
Contents
Asset Classes and Relationships
This section describes how Brick information is used within Asset Class and Relationship concepts.
Asset Classes
Asset classes are used as a template to group Senfi assets with identical properties based on their:
- Type
- Capability
- Senfi measurements
- (For brick schema support) Brick equipment classes
For example, all AHU equipment using an example measurement my_ahu_v1 can be grouped with a class:
- Name: My AHU
- Measurement: my_ahu_v1
- Brick equipment class: AHU
The Asset class can have zero, one or more Measurement/Brick equipment classes declared. View here for the full list of Brick equipment classes supported. Asset Class with brick equipment classes can export to brick schema .ttl (Turtle/TTL) format.
An Asset:
- can have 0, 1 or more asset classes assigned to it
- inherits measurements of the classes assigned
- Class' measurement source can set the brick point names for each metric (which can later be exported to brick schema)
User can add Asset Class manually via CMS or import from ttl file.
Asset Relationships
Brick relationships are represented in Senfi as Asset relationships. It defines the relationship between:
- Asset and Asset
- Asset and BBL/Location
Currently, there is a 1:1 direct mapping between Senfi asset-asset relationships and brick equipment-equipment relationships:
- brick:hasPart/brick:isPartOf -> hasPart
- brick:controls/brick:isControlledBy -> controls
- brick:feeds/brick:isFedBy -> feeds
- brick:serves/brick:isServedBy -> serves
- brick:monitors/brick:isMonitoredBy -> monitors
CMS will automatically add the BBL relationship from asset BBL attachment. User can add Asset Relationship manually via CMS or import from ttl file.
What's Next
- Start creating Asset Class