V2/Concepts/Zone

From Senfi Docs
Revision as of 19:52, 6 June 2022 by Huiyan (talk | contribs) (Created page with "<h1 class="main-heading">Zone</h1> On top of BBL, a Site can also have '''Zones''' being defined. BBL is an organization of building structure, while Zone is an organization...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Zone

On top of BBL, a Site can also have Zones being defined. BBL is an organization of building structure, while Zone is an organization of spaces. Zones will allow end-users to define locations in the building at higher level of granularity, and it can be utilized in automations, especially for scenarios that requires real-time location tracking of assets (E.g. detection of unauthorized personnel in restricted access zone).

Zones can be classified into two general types of zones:

  • Physical zones
  • Abstract zones

Physical vs Abstract Zones

Physical Zones

The physical zones defines physical spaces such as a level, stairwell, rooms in a building etc. BBL zones are a specialized type of physical zone which are automatically created by Senfi when BBL is defined. BBL zones are:

  • Read-only zones
  • Created when BBL is created (BBL zones boundary are created based on BBL model object assignment)
  • Deleted when BBL is deleted
Examples of physical Zones in a building

Abstract Zones

The abstract zones defines abstract spaces such as restricted access zones, VIP zones, public zones etc.

Zone Boundary

Zone uses boundary (volume box) to represent area of the zone. It is optional for a Zone to have a boundary (especially if it's an abstract zone). Zone boundaries are colored, and they can have relationships between zones.

Zone Relationship

There are two types of relationships between zones:

  • hasPart
  • intersect

hasPart relationship

The hasPart relationship is a inclusion/part of relationship. It means one zone is completely included or is a part of another zone. Example:

  • Level 2 includes/has parts MR1, MR2, Pantry
  • Implied: MR1 is part of Level 2
Example of hasPart relationship

intersect relationship

The intersect relationship is a partial overlapping of zones. It means one zone partially overlaps certain part of another zone. Example:

  • Zone Lobby A intersects Level 1, Level 2, Level 3
  • Implied: Lobby A overlaps certain part of Level 1, Level 2, Level 3
Example of intersect relationship

What's Next