What is the SIA alarm protocol?
SIA means Security Industry Association. In alarm reporting, the name may refer to its DC-03 event format or to DC-09 reporting over IP. These formats let a receiver interpret alarm information from premises equipment. When you choose a receiver, name the standard and reporting settings so it reads your account, event and restoration correctly.
What does the DC-09 protocol carry?
DC-09 carries alarm event information over an Internet Protocol (IP) connection from premises equipment to a central-station receiver. It can carry Contact ID event content as ADM-CID over IP as well as supporting SIA reporting. Match your receiver settings, account numbers and supported events to the sender.
For example, if you test a door contact at a shop and the Hub records the alarm, your next check is at the receiver: did the DC-09 report arrive with the right account, event and restoration? Compare sender and receiver versions, event codes, acknowledgement records and network settings. Arrange monitoring, operator verification and physical response separately under the service agreement.
How can a Roombanker Hub report to an ARC?
| Route | Event path | When it fits |
|---|---|---|
| Direct DC-09 | Hub → ARC’s compatible receiver or built-in converter | The ARC already accepts the Hub’s reporting profile. Main or backup use must be agreed and tested. |
| IP receiver | Hub → receiver software or hardware → ARC automation | An intermediary translates the supported input into the ARC software’s accepted format. Both interfaces need matching. |
An IP receiver is useful when the ARC software cannot accept the Hub’s output directly or the ARC architecture requires a separate receiver. Specify its input and output formats and set up access protection for both connections. If you connect a shop Hub to ARC software that needs an intermediary, check the receiver input against the Hub output and its output against the ARC software before ordering.
Which RB Link settings are needed?
The ARC administrator prepares event reception and supplies the account and receiver details. An authorised installer enables the ARC/CMS connection in RB Link and enters Main Address, Port Number and Account Number. Roombanker Hub supports encrypted DC-09 reporting. If your ARC receiver also supports it, agree the encryption settings with the ARC and configure both ends to match.
RB Link does not display whether the Hub’s report reached the ARC. If you test a shop entrance contact, trigger the agreed event and ask the ARC to read back your account, event and point. Keep monitoring-administration permissions with the people authorised to manage the service.
What does SIA DC-09 cover—and what does it leave to the project?

The Security Industry Association’s public page for ANSI/SIA DC-09-2026 describes a protocol for carrying event content from premises equipment to a central station using IP, possibly across the public internet. SIA says the standard is intended to support compatibility between control-panel and central-station receiver manufacturers, and that compliance is voluntary.
You still need the rest of the alarm service. A security alarm system still has to detect a site event, apply its local zone and mode logic, send an agreed representation of that event, and make the result available to a responsible recipient. DC-09 addresses the reporting path between defined endpoints. Use these questions to plan your installation:
- Which detector, zone or system condition created the local event?
- Which events, restorals, troubles or supervisory conditions are included in the project?
- Which sender and receiver implementations are compatible?
- Who owns the premises network, wide-area path, receiver, automation platform and service account?
- Which logs and tests show acknowledgement, timing, ordering, duplicate handling and loss behavior?
- Who reviews the event, verifies it and decides what happens next?
If you have a warehouse detector reporting locally but no event at the ARC, follow its report through the Hub, network and receiver. You need to know where it stops and who can fix that part before signing off the installation.
Keep the SIA standards scope map clear
SIA documents describe different parts of alarm communication. Use the document number and revision to identify which part you need. For example, if you are connecting an IP communicator at a shop, start with DC-09; when you check the Contact ID event content, also read the Contact ID specification.
| SIA document | What it covers | What you must arrange or check separately |
|---|---|---|
| ANSI/SIA DC-09-2026 | Event reporting from protected-premises equipment to a central-station receiver using IP | Arrange monitoring, operator verification and dispatch; check the actual sender and receiver together |
| SIA DC-05-2016 (Contact ID) | The Contact ID signaling format, using standard DTMF tones, for compatible transmitters and receivers | Use DC-09 for the IP transport design; check whether the actual product supports Contact ID |
| DC-03-2017 | A digital communication format for alarm-industry transmitters and receivers | Check the DC-09 network route, receiver-to-automation connection and actual product compatibility separately |
| ANSI/SIA CP-01-2019 | Control-panel and arming/disarming features intended to reduce false alarms | Use the reporting standard to check transport from premises to central station |
The separate Contact ID guide explains DC-05/Contact ID. The ARC guide explains the receiving-centre role and service scope.
SIA announced the 2026 DC-09 revision on March 3, 2026. Its public release notice lists ANSI approval, autocommissioning features, encryption-key rotation, security enhancements, additional examples and continued backward compatibility. For an older receiver, ask its supplier which of these features your installed version supports, then test it with the sender version you plan to use.
DC-07 covers a different link: the interface from an alarm receiver to an automation computer. DC-03, DC-05, DC-07 and DC-09 therefore describe different formats or interfaces, not four generations in which each replaces the last.
Map the reporting architecture before selecting a path

Follow an event from the detector through DC-09 reporting to the operator’s screen. A sender may create a valid event while an account number, network route, receiver setting, software translation or operator procedure goes wrong later. If you test a warehouse door contact and the ARC sees another zone, compare your local event with the receiver and operator display to locate the mismatch before buying more equipment.
| Layer | Input | Output | Main dependencies | Who handles it | Fault records to keep |
|---|---|---|---|---|---|
| Protected-premises event source | Detector, contact, user action or system condition included in the design | Local device or zone event | Correct device, placement, power, enrollment and zone assignment | Installer and system designer | Final-position functional result and local event identity |
| Control panel, hub or transmitter | Local event plus set/unset state and configured logic | Event selected for reporting | Exact model, firmware, supported event set and configuration baseline | Installer/integrator and system administrator | Local log, configuration record and event timestamp |
| Account and event mapping | Sender identity, account context, zone/user/event definitions | Receiver-recognizable project mapping | Agreed naming, receiver profile and service provisioning | Integrator and monitoring-service technical contact | Approved mapping sheet and controlled test result |
| Premises network | Sender network traffic | Reachable upstream path | Addressing, routing, firewall policy, DNS when used, local power and maintenance contacts | Customer IT or named network contact | Connectivity state, outage record and who approved the network rules; keep live configuration values private |
| Wide-area transport | Premises egress | Receiver or intermediary ingress | Carrier or internet service, routing, service availability and any approved alternate path | Network/service contact | Dated availability and loss/restoration records |
| Receiver or approved intermediary | Supported input from the sender path | Accepted, rejected or transformed event for the next system | Exact model/software revision, licensed profile and supported mapping | Receiver/service contact | Acceptance/rejection record, acknowledgement state and receiver log reference |
| Automation or central-station software | Receiver output | Operator-visible event and workflow entry | Interface mapping, account provisioning, event priority and current software revision | Monitoring-platform contact | Operator display record and automation correlation |
| Acknowledgement and supervision | Sender/receiver transaction state | Records that the configured layer recognized or lost a transaction/path | Exact implementation behavior, timers, service rules and log retention | Integrator plus receiver/service contact | Correlated sender and receiver timestamps; loss and restoration results |
| Operator workflow | Visible event plus account instructions | Verification, escalation or closure decision | Contracted service, trained operator, current contacts and procedure | ARC/monitoring-service operator and service manager | Procedure result, audit record and exception handling |
| Response contact | Verified or escalated information | Action by the named person or service | Authority, local policy, availability and contract | Customer, guard service, emergency contact or other named responder | Handover record and response-procedure acknowledgement |
For the local device-to-system path, the wireless alarm communication guide explains why a detector indication is not the same as a system view or remote outcome. The current Smart Hub page and RB Link page provide product and software information. Use the current model instructions to check the selected receiver, security profile and service region.
Choose the reporting path your equipment supports
Choose direct DC-09 reporting or reporting through an IP receiver to match the equipment and service you will actually use. If you use an IP receiver for a shop Hub, include the receiver in your loss and restoration tests as well as the site network. The ARC integration planning guide provides the broader project inputs that should exist before an integration route is chosen.
| Path category | Architecture question | What to check before choosing | Availability and failover question | Who secures and handles data | Commissioning contact | Who provides support |
|---|---|---|---|---|---|---|
| Direct sender-to-receiver | Can the exact premises sender revision communicate with the exact central-station receiver revision under the licensed profile? | Sender and receiver model/revision documents, supported standard revision/profile, event mapping, acknowledgement/supervision behavior, region and named support confirmation | What happens on premises network, carrier, receiver or endpoint loss? Any alternate path must be documented and tested separately | Define each endpoint contact, permitted service identity, secret lifecycle, log source and change authority | Integrator with receiver technical contact | Sender vendor, network contact and receiver/service contact each support only their documented layer |
| Receiver- or gateway-mediated | Is an approved intermediary required, and what exact input/output profiles does it support? | Intermediary model/software revision, both interface documents, who manages format conversion and event mapping, receiver records and support status | Does loss of the intermediary create a single point of failure? If redundancy is claimed, which design and test results show it works? | Define where data is received, transformed, logged and administered; do not assume an intermediary creates a security barrier | Integrator plus intermediary and receiver teams | Support must cover both sides of the intermediary and the mapping between them |
| Cloud-mediated | Is a named service a documented component of this sender-to-receiver design? | Exact service, sender and receiver revisions; supported topology; region; account/service scope; current release/manual records; data-flow and task record | What is the behavior during premises internet, service, upstream or receiver loss? Any queueing, retry or alternate behavior needs exact records | Define service operator, data region, privileges, secret custody, retention, update path and incident escalation | Integrator plus service and receiver teams | Service availability and feature support are bounded by the named region, account, release and contract |
For the two Roombanker routes in “How can a Roombanker Hub report to an ARC?”—direct DC-09 and an IP receiver—select your Hub, firmware, receiver and region before using this comparison. The commercial integration solution and ARC integration route help you send those details to the integration team for review.
Build the compatibility record before configuration

Compare the sender and receiver revisions, reporting settings, events, account numbers, acknowledgements, supervision and security controls before configuring either end. If you replace a receiver at an existing shop, keep the old and new details side by side and mark each difference you need to test. Ask each supplier or service team to sign off its part of your worksheet.
| Compatibility field | What to record | Acceptance question | Who to ask |
|---|---|---|---|
| Sender identity | Manufacturer, model, hardware where relevant, firmware/software revision and current source revision | Is this exact sender release in support? | Sender vendor and integrator |
| Receiver identity | Receiver/intermediary model, software revision, licensed modules and current source revision | Is this exact receiving release in support? | Receiver/service contact |
| Standard and profile | Exact standard revision and implementation/profile reference available to authorized parties | Do both sides support the same approved use? | Both vendors/teams |
| Project topology | Approved architecture diagram with components, connections and support contacts | Does the diagram match the path that will be commissioned? | System designer |
| Region and service | Country/region, service availability and account/contract scope | Is the feature supported in this deployment region and service tier? | Commercial/service contact |
| Event scope | Project event list, restorals, troubles and supervisory conditions | Are only agreed, supported events included? | Designer, integrator and ARC |
| Account, zone and event mapping | Controlled mapping record without public account identifiers | Does each test event reach the intended account/zone/event display? | Integrator and ARC |
| Acknowledgement and supervision | Vendor-documented behavior and agreed acceptance records | Can accepted, rejected, lost and restored states be distinguished? | Sender and receiver teams |
| Timing, order and duplicates | Documented behavior plus acceptance scenarios | Are delayed, repeated and out-of-order observations handled as designed? | Integrator and automation contact |
| Network contacts | Named premises, carrier/service and receiver-side teams | Who diagnoses each connection without exposing production configuration? | IT/network/service teams |
| Security profile | Supported control profile, role model, secret-management contact and current records | Are access and secret lifecycle controls defined without public disclosure? | Security and service teams |
| Time synchronization | Named authoritative time sources and who monitors them | Can sender, receiver and automation records be correlated? | IT and system teams |
| Power and resilience | Power dependencies and any documented alternate path | Does each claimed loss/restoration behavior have a test? | Designer and site contact |
| Manuals and releases | Current licensed/public documents with dates and revision identifiers | Can every exact claim be traced to a current source? | Procurement and technical approver |
| Support and change control | Support contacts, maintenance contact, approval flow and re-test trigger | Who owns updates and compatibility after change? | Service manager and system contact |
Mark unknown items on your worksheet and ask the relevant supplier for the model and version details needed to resolve them.
Set access rules for your reporting connection

Protect access to both ends of your IP reporting connection. Decide who can hold or change keys, administer each endpoint, install updates, read logs and act on a suspected compromise. If you prepare a shop installation screenshot for a support request, hide live account identifiers and keys before sharing it.
NISTIR 8259A provides a baseline for technical IoT device cybersecurity features, while NISTIR 8259B addresses non-technical support needed from manufacturers or other parties. Use them to write your security requirements, and arrange the project’s risk review and any product certification checks separately.
Apply these control principles to the integration design:
- Least privilege: Give each installer, administrator, service account and operator only the access needed for its assigned task. Normal users should not receive integration-administration authority merely to operate the alarm system.
- Separation of duties: Separate system use, integration configuration, secret custody, receiver administration, change approval and monitoring operations where the project risk requires it.
- Secret lifecycle: Define approved generation or enrollment, protected storage, controlled distribution, rotation, revocation, recovery and destruction. Public documents should never contain live secret material or reusable examples.
- Logging and correlation: Retain enough sender, network, receiver and automation logs that you are authorized to keep to reconstruct a commissioning result or incident without exposing it publicly.
- Change control: Identify who can approve changes, the maintenance window, rollback contact, affected records and mandatory re-test scope.
- Update and support: Record supported versions, who installs updates, security-notification route and what happens when a component leaves support.
- Incident escalation: Define who contains a suspected account, endpoint, software, key or service compromise and who coordinates receiver-side action.
- Public redaction: Keep credentials, secret or key material, private endpoints, customer account identifiers, administrator screens and executable configuration out of public articles, screenshots and handover extracts.
The wireless security guide explains the same disclosure principle across alarm-system layers: explain who manages each part while keeping live access details private.
Test the path before the service team takes over

Test the full DC-09 reporting path in a controlled environment, then repeat the relevant tests on the installed system. If you move a tested Hub onto the shop’s final network, send your agreed events again and compare the receiver and operator results with the earlier test.
- Collect the equipment and test details. Record sender, receiver/intermediary, automation and service identities; revisions; manuals; licensed profile; region; topology; event scope and teams.
- Approve the topology. Confirm that the diagram matches the commercial scope, network contacts, access restrictions, service dependency and support model.
- Arrange the test window. Use project-approved test arrangements, contacts and maintenance controls. Do not test with unapproved production accounts or public credentials.
- Set up the equipment. Authorized personnel work from licensed standard and vendor instructions. Record a configuration baseline without copying sensitive values into public records.
- Prove basic connectivity. Confirm each planned connection can reach the next approved component and can distinguish normal from unavailable states.
- Run the event matrix. Generate every configured project event, restoration, trouble, tamper, panic or supervisory condition that the system and service are contracted to handle. The exact list is project-specific.
- Verify mapping. Match sender records to receiver and automation display, including account context, zone or source identity, event meaning and restoration state.
- Verify acknowledgement and supervision. Demonstrate the documented accepted, rejected, missing and restored conditions for the exact implementation.
- Check time, sequence and duplicates. Correlate timestamps and observe the agreed handling of delayed, repeated or out-of-order records without inventing universal timing thresholds.
- Exercise approved loss scenarios. Test relevant premises-network, wide-area, receiver/intermediary, service and power interruptions within a controlled window.
- Prove any claimed alternate path. Failover or fallback is accepted only when the exact design, trigger, contact, limitations and restoration behavior are documented and tested.
- Check operator presentation. Check the correct information reaches the intended workflow and that exceptions do not create misleading or silent states.
- Save the test results. Preserve test ID, scenario, expected and observed result, correlated timestamps, teams, exceptions, corrective action and re-test result.
- Give the service team its contacts and instructions. Record operational contacts, service scope, maintenance and update contacts, change approval, incident escalation and re-test triggers.
- Retain rollback and re-test criteria. A failed or changed integration returns to the last approved baseline and repeats every affected acceptance scenario.
The wireless site-survey guide explains premises signal planning. The installation workflow covers field sequencing before devices are mounted, while the troubleshooting guide helps separate local wireless, enrollment, placement and configuration faults from later reporting-path faults.
Build an event-test and acceptance matrix
Build your test list from the system design, supported sender and receiver events, monitoring contract and local procedure. If you test a warehouse door contact, include the agreed alarm and restoration: check that both arrive under the same account and point, with the correct meaning on the operator’s screen.
| Test family | Example project question | Records to compare | Pass condition | Re-test trigger |
|---|---|---|---|---|
| Alarm event | Does each included zone/event reach the intended receiver and operator context? | Local log, receiver result and automation display | Meaning, source and account context match the approved map | Zone, event map, sender, receiver or automation change |
| Restoration | Does return-to-normal produce the configured and understood result? | Local state and receiver/automation state | Restoration is correctly associated with the original condition | Event-profile or mapping change |
| Trouble or fault | Can a defined device, path or system fault be distinguished from an alarm? | Fault source, reporting result and operator procedure | Fault meaning and contact match the design | Component, supervision or procedure change |
| Tamper | Are the included tamper conditions represented and handled as agreed? | Local tamper records and receiving workflow | Correct event identity and escalation path | Hardware, enclosure, profile or service change |
| Panic or user-initiated event | Does the configured action reach the correct high-priority workflow without assuming response? | Local action, receiver display and procedure result | Correct presentation and documented operator action | User-role, mapping or service-procedure change |
| Rejection | Can an unsupported or invalid transaction be recognized and investigated? | Sender state and receiver rejection records | Rejection is visible to the responsible contact; no silent acceptance is assumed | Profile, account or receiver change |
| Lost acknowledgement | Can a missing acknowledgement be distinguished from accepted delivery? | Correlated sender and receiver records | The designed fault/supervision behavior is observable | Network, timeout/profile or software change |
| Delay, duplicate or order exception | Can operators and systems recognize the agreed exceptional sequence? | Correlated timestamps and event identifiers | Observed behavior matches documented implementation and procedure | Time, network, queueing or automation change |
| Network or service loss | What becomes unavailable, who sees it and how is restoration proved? | Layer-specific loss and restoration records | Loss and return are visible at the correct connection | Network, service, routing or topology change |
| Power loss | Does each powered component behave as documented? | Power state, device/receiver records and restoration | Test results show the stated resilience and recovery | Power design or component change |
| Alternate path, when documented | Does the exact alternate path take over and return as designed? | Trigger, path selection, receiver result and restoration | No untested “backup” claim remains | Any path, service or policy change |
| Operator/contact exception | What happens when the first workflow contact cannot complete the procedure? | Automation record and escalation audit | The contracted exception path is followed | Contact, contract or procedure change |
Diagnose failures by layer
Find the first point where the DC-09 report differs from what you expected. If you see a warehouse alarm at the receiver but not on the operator’s screen, compare the receiver output with the automation software’s account and event mapping. Start there instead of changing the detector or Hub settings.
| Failure mode | Signal to inspect | Who to call first | Safe containment | What to check before re-testing |
|---|---|---|---|---|
| No connection | Sender network state, path availability and receiver reachability | Network contact, then endpoint teams | Hold production use of the unproved path; use only an approved operating fallback | Dated layer-by-layer connectivity and restoration record |
| Receiver rejection | Receiver result and supported profile/revision | Receiver contact with sender vendor/integrator | Stop repeated uncontrolled attempts; validate compatibility records | Exact rejection records, revisions and approved corrective action |
| Wrong account, zone or event mapping | Sender event versus receiver/automation display | Integrator and monitoring-platform contact | Mark affected mapping unavailable for operational reliance | Corrected controlled map plus full affected event re-test |
| Lost acknowledgement | Sender state versus receiver transaction records | Sender and receiver teams | Treat delivery as unproved; follow documented fault procedure | Correlated records showing accepted, missing and restored conditions |
| Delayed event | Sender, network, receiver and automation timestamps | Team handling the first delayed part | Preserve records and use the contracted exception procedure | Time correlation and repeat test under controlled conditions |
| Duplicate event | Sender transmission records and receiver/automation records | Implementation teams | Prevent duplicate workflow from being mistaken for multiple incidents | Identifiers/timestamps and documented duplicate handling |
| Out-of-order event | Cross-layer sequence | Automation/integration contact after transport review | Flag sequence as uncertain until reconciled | Correlated order records and approved logic/procedure result |
| Time drift | Time-source and timestamp correlation | IT/system contact | Do not use unaligned timestamps as proof of sequence | Correct time-source records and repeated correlation test |
| Security-profile mismatch | Supported-profile and authentication failure records | Security/service teams | Revoke or quarantine affected access according to incident procedure; do not disclose values | Approved security settings and test results and authorized re-test record |
| Network or power loss | Connection state and component power records | Site/network contact | Follow the approved loss procedure | Loss/restoration records for every affected component |
| Alternate path does not take over | Trigger, routing/path selection and receiver result | Designer and service teams | Withdraw the alternate-path claim until corrected and re-tested | Exact topology, failure trigger and successful controlled re-test |
| Receiver-to-automation mismatch | Receiver acceptance versus operator display | Receiver/automation contact | Route to the approved exception workflow | Mapping/interface records and operator-display re-test |
| Operator or contact failure | Workflow audit and contact/escalation record | Monitoring-service manager/customer contact | Follow the contracted exception process | Updated contacts/procedure and controlled scenario result |
This layered approach complements the intrusion-system event workflow: detection, reporting, receiving, verification and response are connected, but they are not interchangeable.
Keep transport, monitoring, verification and response separate

Track these six steps in your proposal and test results. If you receive an acknowledgement after testing a shop door contact, ask the ARC to check the operator display and agreed procedure too; the acknowledgement is only one step:
- Follow the local event. Check that it passes through your configured sender and reporting path.
- Check acknowledgement. Compare the sender and receiver logs to see whether the receiver accepted the report.
- Check the operator display. Test the software mapping and how the event appears to the operator.
- Check verification. Follow the contracted procedure using the available alarm information.
- Check dispatch or attendance. Use the agreed authority, contacts, local policy and service terms to decide the next action.
- Read the response terms. Check the actual agreement for service scope, response times and exceptions.
The ARC basics guide explains the receiving-centre role; it should be read alongside the specific contract and local operating procedure. Arrange police, guard, installer or emergency-service response through the agreed service procedure.
Prepare a qualified SIA DC-09 integration inquiry
Give the integration team the models, versions and reporting route you want to connect. If you are replacing an IP receiver at a shop, send your existing Hub details, the proposed receiver and the events the ARC needs to handle. Before you contact the team, prepare:
- sender manufacturer, model and firmware/software revision;
- receiver or intermediary manufacturer, model, software revision and licensed profile;
- country/region and required service context;
- proposed topology and named contact for each network/service connection;
- required event, restoration, trouble, tamper and supervisory scope;
- acknowledgement, supervision, timing, sequence and duplicate-handling requirements;
- security, access, logging, update and incident-response requirements;
- availability, power and any alternate-path requirement;
- monitoring/verification/response contact and project stage;
- current manuals or release notes for the functions you plan to use.
Roombanker’s integration solution lets you submit an integration inquiry. The Support Center is the next step for current product manuals and supported-service questions, while the wireless security system solution shows the wider product range. Send your sender and receiver details, revisions, region, connection diagram, events and service requirements through the integration inquiry form. Say whether you are planning, installing or troubleshooting. If you need current manuals first, contact Support.
SIA DC-09 FAQs
Is SIA DC-09 the same as Contact ID?
No. SIA’s public DC-09 page describes IP event transport from premises equipment to a central station. Its DC-05 page describes the Contact ID signaling format using DTMF tones. Contact ID event content can also be transported over DC-09 as ADM-CID. A receiver may support more than one format, but support and translation must be confirmed for the exact models, revisions and licensed profiles.
Does using DC-09 mean an alarm is monitored?
No. DC-09 describes event reporting between defined technical endpoints. To receive monitoring, you need an active service, a set-up account, agreed events, an operator procedure and current contacts. Verification and response are additional operational layers.
Does ANSI/SIA DC-09-2026 automatically work with an older receiver?
Not automatically. SIA’s 2026 release announcement refers to continued backward compatibility. Compare your sender and receiver revisions, reporting settings, event mapping and supplier support, then test the pair in a controlled environment before putting it into service.
Does an acknowledgement prove that someone handled the alarm?
No. An acknowledgement tells you about the tested sender/receiver exchange. Check receiver acceptance, the operator display, operator action, verification and response separately to find out how far your alarm has travelled.
How should integration credentials be handled?
Keep integration access restricted to authorised personnel. Live credentials, secret or key material, private endpoints, customer account identifiers, administrator workflows and executable configuration belong in controlled project manuals available only to authorized parties.
What should trigger re-commissioning?
Re-test the affected scope after sender or receiver firmware/software changes, profile or event-map changes, network or topology changes, service or region changes, account/workflow changes, security-control changes, power/resilience changes, support-status changes or a relevant incident. Use impact analysis to determine which earlier acceptance scenarios must be repeated.
