Introduction
This guide discusses the Occupancy (FIFO) register type. This register enables the number of people in a room, or area, to be calculated and communicated separately.
The 'FIFO' suffix relates to additional ‘First In First Out’ time out functionality, which operates on a per person basis. This is designed to help with any positive occupancy counting bias. Essentially any person who is counted IN but is not counted OUT will be timed out and removed from the occupancy count after a configurable timeout value.
When occupancy reporting on rooms with multiple doors is required, multiple devices may be used in wide tracker mode, or preferably using Remote registers, to pass counts to a primary unit to consolidate into a single occupancy number.
This register type is ideal for applications as room utilization reporting, room booking applications, and building controls management.
Optionally, an Irisys Fine Motion Room Sensor may be used connected via Bluetooth. This PIR based sensor provides an automatic ‘Occupancy reset’ function when a long period of inactivity has been seen, although the built in FIFO functionality will most likely negate this requirement.
The alternative Occupancy register type is also available which works in a very similar way but does not include the FIFO functionality.
Pre-Requisites
It is strongly recommended that your Vectors are updated to very latest firmware before starting to ensure full compatibility.
If utilising multiple Vectors installed at various entrances and exits into the occupancy area, all Vectors should be on the same (latest) firmware version.
It should be noted that the Occupancy FIFO register should only be configured on one device. The additional IN and OUT count register values from any other devices are passed into the Occupancy FIFO register via the Remote register types. Those remote registers should be configured on all the additional Vectors first before continuing with the Occupancy FIFO register setup.
Instructions
Before starting, there needs to be two counting lines configured which will feed into the Occupancy FIFO register. These lines need to simply count IN and OUT of the area of interest and should be configured to operate in a count mode conducive to the occupancy calculation – Immediate Count Mode (with Anti-dither disabled), Deferred count mode, or they can be the Smart Boundary line register type instead. 
Both directional lines should be configured with the same settings. Specifically, the count mode must be the same for each, with lines placed on top of each other in the field of view with only their direction being different – this is important to prevent any dithering on or around the count lines from generating more increments in one direction than the other.
Similarly, if any height filtering or staff detection settings are configured these too must be the same on both lines.
If using the Smart Boundary line types the grouping functionality should not be employed.
It is also recommended to label the count lines with meaningful names to indicate the directions. This will help with configuration of the Occupancy (FIFO) register later on. E.g. “IN” and “OUT”.
If connected to a Vector via an Estate Manager connection, make sure you select the ‘Live View’ option to make changes.
To add an Occupancy (FIFO) register:
If you're using the Fine Motion Room Sensor, ensure it is shown in the registers dialog before proceeding:
Click the plus symbol (+) on the Register dialog window:
Then choose the "Occupancy (FIFO)" type register and click 'Next':
Give the register a meaningful name and click 'Next':
Under 'Occupancy Inputs', select all the appropriate registers for counting IN to the zone:
If using Remote registers to access additional IN and OUT counts from other Vectors installed at others doors into the same Occupancy area, ensure they are all ticked correctly:
Under 'Occupancy Outputs', select all the appropriate registers for counting OUT of the zone:
If using multiple Vectors to cover all other doorways into the Occupancy area, again ensure that the OUT registers are all assigned correctly:
If you have a Fine Motion Room Sensor, ensure that it is enabled under the 'Occupancy Reset' section. (Note: this only prevents the "Reset Timeout" from resetting, an "Individual Timeout" will still reset when its time has expired):
Enter a suitable Individual Timeout value for the area, in seconds. This should be based on the maximum length of time that someone would be expected to be in the area.
For meeting rooms, washrooms, or other low timeframe for occupancies, the "Individual Timeout: can be used and should be greater than the longest expected time a person would be in the area.
For larger areas the "Reset Timeout" should be used (see further down) and be greater than the minimum time that people would normally be accessing the area, or the other 'Occupancy' register can be used instead.
For the FIFO functionality to work correctly, you must specify a higher main Reset Timeout value, unless the "area occupancy register" is also being used then it can be a lower value:
It should be noted that if you do not want to have an automatic reset, simply configure both the timeout values to a large value. Note that this is not recommended as the occupancy value should reset over night at the very least to ensure that everything starts from zero the next day.
Click Next.
A summary of the settings you have chosen will be shown. Click Back to make changes. Click 'Add Register' to finish:
Once the Occupancy FIFO Register has been added, you will see three components:
The Reset register count is how many times the Occupancy register has reset using the 'Main Reset Timeout'. When using the Individual Reset Timeout (the main reason for using the Occupancy FIFO register type), this will remain at zero.
The Timeout component will increase every few seconds and when the configured main Reset value is reached, occupancy will be reset to zero - again this won't occur if the Individual Reset is configured correctly. Because this value changes regularly, when using MQTT for data collection, it may be preferable to disable this.