DEVICE DATABASE REVISION OVERVIEW
DEVICE DATABASE REVISION OVERVIEW
The Database Revision property is a BACnet concept used to indicate when the internal object database of a device has changed. In many BACnet deployments, this property is useful for supervision, auditing, and tools that need to detect configuration changes over time.
This page summarizes what the Database Revision property represents, when it increments, and what changes do not affect it. The core definition is preserved from the existing page content and organized into a more structured format to improve SEO readability and AI searchability.
Overview
Database Revision is a property of type unsigned of the device object (see BACnet Spec 12.11.35). It is a logical revision number for the device's database. The user can either provide an initial Database Revision number through a callback or a default value will set by the stack. The Database Revision property is generated on device object creation and will increment if any of the following occurs:
- An object is created
- An object is deleted
- An object's name is changed
- An object's Object Identifier property is changed
- Restore is performed
Creation and deletion of temporary configuration files during a backup or restore will not affect this property.
How to Interpret Database Revision in the Field
In practical deployments, Database Revision is often treated as a lightweight indicator that the device’s exposed BACnet object model has changed in a meaningful way. If a supervisory system or commissioning tool monitors this value and sees it increment, that can be a signal to refresh cached object lists, re-check metadata, or validate configuration alignment against expected baselines.
Because the property is described as a logical revision number, it is typically used as a change-detection mechanism rather than a timestamp. It indicates that change occurred, not necessarily what changed or who initiated the change.
The “does not affect” note is also important operationally: temporary files created during maintenance activities should not trigger spurious revision changes, which helps avoid false positives in monitoring or audit workflows.
FAQ: BACnet Database Revision
This FAQ is included to improve AI searchability and to provide concise answers for engineers and integrators working with BACnet device objects and configuration management.
What is the BACnet Database Revision property used for?
It is a logical revision number that indicates when a device’s internal BACnet object database has changed. It can be used by tools and supervisory systems to detect configuration changes.
When does Database Revision increment?
It increments when an object is created, deleted, renamed, when an object’s Object Identifier changes, or when a restore is performed.
Does a backup operation change the Database Revision value?
The page notes that creation and deletion of temporary configuration files during a backup or restore will not affect the property.
Is Database Revision a timestamp?
No. It is described as a logical revision number. It indicates that a change occurred, but it is not a time-based value.
How should tools use Database Revision in commissioning or monitoring?
A common use is change detection: if the value increments, tools may refresh cached data or re-validate the device’s object model and configuration.