OMNIA Hardware Offline Validation 

This article refers to the offline validation capabilities of the following OMNIA hardware: 

1. Control Module (CM) with up to 8 directly connected reader modules (WM). 
2. Door Controller (DC) An OMNIA Control module set via dipswitch to operate in door controller mode with up to 8 reader modules directly connected. 
3. iTRT Door Controller. 

1. CM (Control Module) – requires no offline mode – it is the primary decision maker/controller hence it can only be offline from the server; in which case it will not receive any tagholder/site configuration updates while offline and will not be able to upload any transaction data from its cluster to the server. Once back online, all these updates occur. All (up to 8) reader modules connected directly to the CM will work with full offline validation. 

Risks: 

• The only real risk here is the transaction buffer eventually being overwritten. Transaction buffer = 10 000 transactions. 

   2.  DC (Door Controller) – A Control Module in DC mode, emulates an iTT/iTRT. There are          two offline modes: a). If there are less than 10 000 tagholders on the site, then DC’s make access control                             decisions by referring to a set of tables containing the access rights of all tagholders on site.             There is essentially no difference to the behavior as compared to a CM, except that only              the first two of the connected cluster modules will be supported in this                            manner. 

Risks: 

• Only the first 2 modules are supported in this manner. 
• In this mode, only 10 access groups per tagholder are supported as opposed to the 25 that would be if the DC was online. 
• A high traffic door that is left offline for a long time will start to overwrite the transaction buffer. 
  

 b).  If there are more than 10 000 tagholders on site, then the number of tagholders exceeds                 the DC’s local tagholder database (set of tables) capacity. It can’t use this method of                           validation. Instead, it refers to its transaction buffer (of 10 000 transactions). If the                           tagholder that is attempting to tag appears in the transaction buffer with an allowed                         transaction, then that tagholder is allowed access in offline mode.  

 Risks: 

• Again, only the first 2 modules are supported in this manner.  
• A high traffic door that is left offline for a long time will start to overwrite the transaction buffer.

3.  iTRT – Identical to above (2) DC, Unit only has 2 reader ports, can not be expanded.