Door Lock Schedule Integration

If you are using Avigilon Alter (formerly OpenPath) door access with Events2HVAC, Rock Room Management plugin can be configured to create door schedules along with room schedules.  This gives you the option to unlock doors using either or both of these event schedules to control door schedules.

Enabling Door Functions
In Rock RMS Options - New Function tab - Enable Door Lock Functions = checked.  This creates 2 event functions:  1 for regular room occupancy schedules and 1 for door lock schedules.  The event data will have a field that is normal empty in the "FunctionID" column and the actual event schedules will be tagged with one or the other function names.

If you enable the “Fallback to Room Schedules” option, an additional function “Door Unlock with Room Fallback” will be shown.  This allows the assigned actions to use door schedules if they are present, otherwise fall back to use the room schedule.
 

 
Event List Data Changes
I included hidden field for FunctionID,EventID to show the differences.  This normally wouldn't be visible.
 

 
The event name will have "[Door Schedule - X] appended to the original event name to indicate that this is a Rock door lock schedule.  The "X" value is the index of the door schedules in the Rock UI.  The event name without this is the normal room schedule.  You can see the function id is populated with "roomSchedule" or "doorSchedule" functions.  The event ID field also has a descriptor at the end for D1, D2, etc.
 
Zone Action Changes
In your zones, you normally have actions for OpenPath that will have a disabled Function Trigger dropdown box.  This becomes active when you enable the door schedules above.  You can see you have selections:
 

 
This selection allows the schedules for the action to be further filtered based on the function trigger selected.  

•      <<Any>> will combine room and door schedule event data into one schedule source for the action

•      roomSchedule - will filter only the roomSchedule functionID from the event data

•      doorSchedule - will filter only the door schedule functionID from the event data

•      doorWithFallback – will filter only events with “doorWithFallback” function id.  This is assigned dynamically so that door schedules are tagged with this Function Id if they exist, otherwise the room schedule will be tagged with the function Id.  This allows the door lock schedule to be assigned the Rock RMS door schedule otherwise it falls back to the room schedule.

Rules for Actions:

1.  You can't have the entry assigned to multiple actions within the same zone event if they are using different filter triggers.  (this will cause conflicting schedules between actions)

2.  You can't have same entry defined in any other zone in use (this will cause conflicting schedules between zones)

3.  For a single door entry zone, you would typically only define one action and either use the roomSchedule or doorSchedule functionId selection

4.  If you disable door lock schedules or change the “Fallback to Room Schedules” option after assigning functions to events, those functions will not have a schedule until your edit the action and save it again to clear out the existing function assignment.

5.  If you enabled door schedules for the first time on existing actions that had no function assigned, the default will use the <<any>> function trigger, so the door schedule will be the combined room and door schedule if a door schedule exists on the event schedules.  You’ll need to select which function each zone action will be assigned.

Example Zone Views
 
Actions Tab
Action list shows which functions each action is defined with.  Note: I can do this because each action is pointing to a different Entry.

 
Equipment Schedules tab
Shows the two actions resultant occupancy period.  Entry 3 - 6am-8am (combined overlap between the 2 door schedules) and Entry 3 is the room schedule.

 
Events Tab
Shows all events for the zone (door and room schedules)