V2/Concepts/Asset Classes and Relationships

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:

1. Type
2. Capability
3. Senfi measurements
4. (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 Relationships

Brick relationships are represented in Senfi as Asset relationships.

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

What's Next

---

• Learn about Senfi Classes and Relationships