# Matching ISMP demo site

Use a dedicated demo tenant chosen by the site owner. The simulator neither creates a tenant nor writes authorization data directly to the controller database. Devices, users and credentials arrive through the existing onboarding/download process.

| Item | Required setup |
| --- | --- |
| Controller | One onboarded controller, online to ISMP, configured RabbitMQ consumer and debug outbound transaction capture |
| Lobby Door / Server Room | Two distinct DDM EM/HSM120/HSM220 doors with enabled contact/lock inputs and fresh feedback; simulated IN or OUT readers in normal mode; toggle mode off |
| Third Door | Optional supported DDM door; map every configured door affected by a selected fire input |
| Staff | Active card and user with valid access groups/time schedules for both selected doors |
| Visitor | Separate, known card that is denied at both demo doors, without granting access merely for the demo |
| Blacklisted | Separate card configured as blacklisted in ISMP; tile card picker permits this demonstration |
| Held-open timer | Set a practical demo timer (for example 5–10 seconds); the recipe waits for the real alarm, up to 120 seconds |
| Interlock | Enabled group containing exactly the two mapped doors; Staff must first be able to enter either independently |
| Fire | Configure the board’s real simulator fire-release jumpers in Advanced during preparation; all enabled affected locks must produce fresh release feedback |
| Baseline | Door contacts closed, locks secured, wiring automatic, key/break-glass inputs restored and prior alarms cleared |

In Demo setup, map aliases `lobby`, `server` and optional `third` to the discovered devices. The profile is local presentation metadata; **Load demo site** does not overwrite controller configuration, users, access groups, reader modes or other sessions’ inputs. Card IDs are selected from current provisioned records. No enrollment records or personal credentials ship in the profile.

Verify on the bench before sales acceptance:

- Staff grant and Visitor denial for the selected credential/direction; correct ISMP user and door.
- Break-In state 30 / DDM transaction 2030; close-failure state 32 / transaction 2032; relock to Normal (state 1).
- Operator unlock 2035; fire release and restoration; interlock denial 3023 at the second reader.
- Reset completes within ten seconds on a healthy configured bench, with no remaining alarms. The runner waits for recovery; it must report pending/unknown instead of claiming success if telemetry or commands are delayed.
- Existing engineering plays, controls, diagnostics, issue recording and enrollment continue to work.

These are acceptance checks, not claimed live results. The tenant choice and real bench observations are still required. Windows/Mac/ARM64 release validation remains separate from the native Pi deployment.
