Skip to main content
BluINFO

A Quick Explanation of the BluSKY Access Level Structure

Overview

A Quick Explanation of the BluSKY Access Level Structure

Instructions 

An Access Right is a “Security Point / Schedule pair” – where a Security Point is either a “Reader” or a “Floor Stop”.  The Access Right specifies that a user shall have access at the security point pursuant to the associated schedule.

  • A Floor Stop is an elevator accessing a floor - (so a Floor Stop might be named "24th Floor - Front Car 1".  
  • Some Elevators may have 2 Doors (Ex:Front or Rear): in that case, a Floor Stop for that elevator becomes an Elevator Door accessing the floor; (it might be named "CAR1 Front Door - 24x7).

An Access Level (AL) is a list of Access Rights.

  • There is one "Best Practice" to follow for ALs: Do NOT mix “Reader / Schedule” and “Floor Stop / Schedule” pairs in an Access Level.  Instead, create an AL for each floor that contains all the “Floor Stops” for that floor – so if you have six (6) elevators accessing FL24, the AL for that floor might be named FL24 and contain six (6) “Floor Stop / Schedule pairs" (24th Floor - Front Car 1, 24th Floor - Front Car 2, 24th Floor - Front Car 3, etc).  

An Access Level Group (ALG) is a group of ALs.  The group can also include individual “Reader / Schedule pairs” if they are needed.

  • If you create an ALG with several ALs in it, it gives access to ALL the readers and the floor stops that are contained in the Access Levels, per the schedules associated with each device (The most comprehensive schedule prevails for each device, ex if one AL gives access for business day to a reader or floor stop, and another give access 24/7 to the same reader or floorstop, then the 24/7 access is the one used).
  • There is no need to add individual “Reader / Schedule pairs" to an ALG if they are already contained in one of the listed ALs.

NOTE that there is no harm in a “Reader / Schedule pair” or a “Floor Stop / Schedule pair” showing up in more than one of the Access Levels listed in the ALG, or being listed as an additional “Reader / Schedule pair” in the ALG.   In fact, there may be good reason for it to be that way.  But it is best to avoid unnecessary redundancy where possible.

 

  • Was this article helpful?