System Maintenance Suggestions
This page is intended to be used as suggestions for system maintenance. It is in no way a requirement to follow these guidelines.
These suggestions are set to help identify potential issues, develop and schedule maintenance, test the system and make sure it is operating correctly, document the system, and allows technicians to get to know they system, simplifying service calls.
Use the document linked here to keep a checklist of the system’s maintenance upon each visit: https://docs.google.com/document/d/14zqDpGejEqoOIOuj29mk3py50jdrS1AV9mezpIo19f0/edit
Table of Contents for System Maintenance:
- 1 Log All Test Results
- 2 Update System Software and Firmware Regularly
- 3 Test Readers Once a Month
- 4 Test System Alarms Once a Month
- 5 Test System Inputs and Outputs Once a Month
- 6 Test System Operation Upon Power Loss Monthly
- 7 Verify Lockdown Devices Work Monthly
- 8 Check Health of the Memory and Backup Battery Monthly
- 9 Check Battery Voltage Once a Year
- 10 Verify Site Documentation is Correct Yearly
- 11 Visually Inspect and Clean Each Component Yearly
- 12 Check Equipment Mounting Condition Yearly
- 13 Check Each Workstation’s Status Yearly
- 14 Check Data Logs Yearly
- 15 Train Operators Yearly
Log All Test Results
Each test performed below should be logged and stored to have a record of system conditions over time.
Take photos and detailed notes.
Update System Software and Firmware Regularly
Both Velocity software and Controller firmware should be updated regularly to ensure each system has the most up to date features and protections.
Test Readers Once a Month
Test all readers once a month to verify that they communicate correctly with the controller.
Test System Alarms Once a Month
Testing alarms to verify the system is monitoring them, and proving they show themselves on Velocity is vital.
A common list of these alarms includes:
DOTL
Door Forced Open
Power Fail
Battery Fail
Any Alarm Inputs Used
Duress
Tampers
Troubles (Open, Short, Excessive Noise, Line Out of Spec)
Any other alarms that the system may be used for
Test System Inputs and Outputs Once a Month
Verify that the system’s input and output terminals operate correctly, and that the devices connected to them function as desired.
Test System Operation Upon Power Loss Monthly
When testing for Power Fail, verify the system operates correctly on battery power
Verify Lockdown Devices Work Monthly
Each month, test the lockdown feature to verify it works to lock and release doors correctly.
Check Health of the Memory and Backup Battery Monthly
By using the diagnostic report labeled #25 System and Power Status, the user can check the health of the memory and backup battery.
Check Battery Voltage Once a Year
The Mx-2 must be installed with a 24V 1.3Ah battery.
The Mx-4 and Mx-8 must be installed with a 24V 7.2Ah battery.
Upon testing the battery each year, the Voltage should read between 28V-24V, with a UPS Battery Low coming in at 24V-17V, and a UPS Fail coming in at anything below 17V.
A Weak Battery will show a higher charge than 28V when under charge (connected to the controller) and a lower charge of 24V-17V when not under charge.
A Dead Battery will show below 17V at all times.
Any battery condition that is close to or past the Weak or Dead threshold should be monitored or replaced.
Verify Site Documentation is Correct Yearly
Each year, verify that the system documentation is correct.
Verify door names, locations, component labels and instructions are still up to date.
Visually Inspect and Clean Each Component Yearly
Verify each piece of system equipment is in good condition, with no major physical defects. These defects include frayed wires, rusting, cracks or scratches.
Clean each piece of equipment by wiping away dust, cob webs, etc. to ensure each piece will be able to function correctly.
Check Equipment Mounting Condition Yearly
Verify each enclosure, reader, sensor, etc. is mounted securely.
Check Each Workstation’s Status Yearly
Verify each workstation is connected to the intended system and is actively:
Getting events
Able to control the system
Able to retrieve programming
Able to set day/time
Verify the workstation time is correct
Perform system performance tests
Check Data Logs Yearly
Verify the data is being stored and logging correctly in the SQL Database.
Train Operators Yearly
Each year, it is important to ensure that each system operator is properly trained on the system and able to operate it correctly.