What DM-RD-B Is
DM-RD-B (Device Management-ReinitializeDevice-B) is the BACnet Interoperability Building Block (BIBB) for a device that executes ReinitializeDevice: the remote-restart and backup/restore state machine. A device claiming DM-RD-B accepts the reinitialized-state choices the service defines and, where applicable, updates Last_Restart_Reason and Time_Of_Device_Restart on its own Device object to reflect what happened.
What It Requires
| Piece | What it does |
|---|---|
| Password handling | A device requiring a password refuses reinitialization without it |
| Coldstart / warmstart | The two restart states most integrators exercise, covered in detail here |
| Backup/restore bracket | startbackup, endbackup, startrestore, endrestore, and the abortrestore escape hatch |
activate-changes | Applies staged Network Port configuration without necessarily restarting |
Where You Meet It in the Field
Any controller an operator can restart from the head end, or any device a backup tool can snapshot and restore over the network, is claiming DM-RD-B. It matters most on a device that has to run unattended for years, where a remote coldstart or a scripted backup avoids a site visit.
[!NOTE] DM-RD-B says nothing on its own about which specific states a device implements. Confirm coldstart, warmstart, and the backup/restore bracket separately against a device’s PICS (Protocol Implementation Conformance Statement) before assuming all of them are supported.
What Chipkin Provides
The CAS BACnet Stack supports DM-RD-B today: the ReinitializeDevice processor handles all seven restart and backup/restore choices, covered by a dedicated backup/restore/reinitialize test panel. The positive BTL rows for this behavior are operator-walled, requiring a human to confirm a visible reboot, so treat this as every flavor and its password gating exercised in test, not a blanket auto-green BTL claim. Talk to us about your specific restart scenario.