V2/Concepts/Senfi Classes and Relationships

From Senfi Docs
Jump to: navigation, search

Senfi Classes and Relationships

This section describes how Brick information is used within Senfi's Class and Relationship concepts.

Senfi Classes

Senfi 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

In addition, the Senfi class can have Brick Equipment Class declared, which can be one or more Brick equipment classes.

Senfi Asset Relationships

Brick relationships are represented in Senfi as Senfi 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