Medeco Security Locks Inc. 20736 Manuale Utente

recorded by the key will be "forced" back into the software database during the required servicing of the key.  This process should be
considered when maintaining a full and accurate historical perspective of the system is desired. 

In the 

 Mode, the Key will manage audit events on a First-In-First-Out (F-I-F-O) basis.  When the audit memory of the key is filled,

the key will continue to function by actively managing the filled memory condition by "rolling" out the first recorded audit event (oldest event
recorded on the key) and recording or storing the most recent audit event.  The primary consideration in using a key configured in a Rolling Audit
mode is that only the audit events that are stored on the key at the time of servicing will be transferred back to the software database.  If the key
has exercised a F-I-F-O condition (meaning that the key memory has filled), then some audits may have been processed off the key prior to the
key being serviced.  As a result, any audit removed from the key based on the F-I-F-O condition will not be transferred to the software database
and, therefore, will not be historically retained.  However, keys having the Rolling Audit mode selected at time of servicing will never need to be
serviced based on the audit memory being filled.