Who Owns Video Intercom and Door Station: Supplier, Integrator or Client
Most disputes over a door station begin after the equipment has been selected: a call reaches the wrong endpoint, an authorised visitor is denied, or a door state and its record disagree. The management problem behind the video intercom and door station ownership split is not who sold the hardware. It is who owns each outcome from call to release, evidence, maintenance and handover.
Direct answer. Short version — video intercom and door station ownership split is treated here as video intercom and door station ownership split first. video-intercom-and-door-station comes second. The evidence for video intercom and door station ownership split is named in the sections below. A video intercom and door station ownership split treats the handover as the unit of work. video intercom and door station ownership split decides the interface. video intercom and door station ownership split is operable on day one only if it does.
This runbook gives the system integrator a way to assign supplier, integrator and client duties while the design is still being evaluated. It separates product evidence, configuration work, policy approval and operating acceptance, so a boundary does not become a permanent phone call.
Set the accountable owner before comparing equipment
Use supplier for the manufacturer or component vendor, integrator for the company assembling and connecting the system, and client for the organisation operating the building. A contract may combine those roles, but it should not blur them. Reference the catalogue record: the SLK-1105 3D Face Recognition Smart Lock with Remote Video Intercom, SKU confirmed on its dated product page.
| Outcome | Supplier owns | Integrator owns | Client owns |
|---|---|---|---|
| Product evidence | Dated behaviour and limits | Check against design | Accept suitability |
| Installation | Requirements and support | Install and configure | Provide site conditions |
| Network | Required conditions | Configure and test | Control approvals |
| Call and release | Explain delivered behaviour | Map endpoint and controller rules | Decide access policy |
| Records | Define fields and device limits | Route, store and export | Set purpose, access and retention |
| Faults | Escalate product issues | Triage and coordinate | Run site support process |
The video intercom and door station ownership split is therefore a contract map, not a product category. If one company performs two roles, name both deliverables and keep a separate acceptance owner for each. Use Video Intercom and Door Station for Smart Lock Projects: What Buyers Must Define First to capture the design inputs before applying this map. The baseline reading is Private Label Glass Door Lock Supplier.
Open the ownership intake
The integrator opens one intake record per door, not one per supplier. It records:
- The physical door identifier and hardware location.
- The call endpoint, ringing plan and response objective.
- Identity sources and credential groups.
- The approved release path and exception handling.
- Degraded behaviour when a component is unavailable.
- The time source, event destinations and support route.
- Physical interface and site constraints.
CONFIRM-WITH-LOCAL-PRIVACY: Confirm the permitted purpose, recording scope, retention period, authorised viewers, export route and notice obligations for call, image, credential and door-event data with the client’s privacy adviser and the relevant local authority.
Any unanswered intake item becomes an explicit design action, not an assumption carried into commissioning. Assign its owner and required evidence before accepting quotations or equipment.
Trace the call-to-release workflow
Trace the call-to-release workflow as six hand-offs: call event, endpoint delivery, identity and policy decision, release request, controller action and state or event feedback. The system integrator writes the expected result for every hand-off, including the result when the message is absent.
flowchart LR
A[Door station call event] --> B[Client endpoint]
B --> C{Identity and policy check}
C -->|Allowed| D[Release request]
C -->|Denied| E[Deny and record outcome]
D --> F[Door controller]
F --> G[Lock reports door state]
G --> H[Audit and event evidence]
Each interface should identify whether the requirement concerns a local API or cloud API, because availability ownership differs. The controller holds the door state and makes the decision; the door station reports a call. If the call arrives but the policy service is unavailable, silence must not be interpreted as a release without an approved degraded mode.
The integrator owns the clock design: nominate one time source, document the expected offset and make endpoint, controller and lock timestamps comparable. The supplier confirms timestamp behaviour for the exact SKU. An audit log is an event record with a time and source; event memory is the lock’s buffer when it cannot reach the server. The two are not interchangeable.
Convert roles into decision rights
The integrator converts roles into decision rights before configuration begins.
| Decision | Supplier input | Integrator action | Client approval |
|---|---|---|---|
| Authorised responder | Document available inputs | Map role to endpoint | Approve roles |
| Release exception | Explain delivered behaviour | Implement approved rule | Authorise exception |
| Degraded mode | State local behaviour | Configure and test | Accept operating risk |
| Record use | Define generated fields | Map storage and export | Approve purpose and retention |
| Production change | Supply change procedure | Version and deploy | Authorise window |
Write each decision with one accountable owner, an approver, a date and evidence. The fail-safe or fail-secure choice follows the door’s role and formal approval, not a product default. Request to exit is a signal that the exit device was operated, not a release command; release on the escape side remains the default behaviour of the exit device.
It is worth pairing this with sl 6301 narrow edge door compatibility. That is the same question video intercom and door station ownership split has to answer here.CONFIRM-WITH-LOCAL-EGRESS: Confirm any door release, request-to-exit, fire-alarm or life-safety interface with the client’s approved authority and the relevant local building or fire authority; the video intercom must not become an unreviewed release authority.
Demand a supplier handoff package
The video intercom supplier responsibility is evidence, not an assumption. Ask for:
- Dated product documents for the exact SKU and installed software version.
- An architecture diagram and interface boundaries.
- An event catalogue with identifiers, timestamps and state changes.
- Installation, power, network and environmental requirements.
- Local behaviour, event-memory and reconnection behaviour.
- Configuration, update, rollback and escalation procedures.
- Known limitations and the evidence needed to reproduce a fault.
Mark each item as received, unresolved or excluded from scope. For any model-level statement, confirm on the dated product page for the specific SKU.
CONFIRM-PER-SUPPLIER: Require written confirmation for every capability, interface condition and handling limitation, tied to the delivered SKU and software version.
Freeze the integrator configuration baseline
The door station integrator scope should be a configuration baseline, not a collection of screenshots. It records:
- Device, door and owner identifiers.
- Hardware, software and firmware versions.
- IP addressing, VLAN, firewall and name-resolution settings.
- The time source and permitted offset.
- Endpoint, role and release-rule mappings.
- Event mappings, log destinations and change history.
Provisioning means bringing a device into service with its identity, door and owner. Decommissioning is a separate, recorded operation that removes the device from service. The client signs the baseline, and every later change produces a new reviewed version rather than an undocumented field edit.
The same question is worked through in more detail in the sl 6301 installation. That is the same question video intercom and door station ownership split has to answer here.
Obtain client policy decisions
Client access control ownership covers decisions, not button presses. The client should answer:
- Who may answer, verify identity and request release.
- Which identity source is authoritative and how visitors are handled.
- What happens after a missed, denied or repeated call.
- Which offline or emergency procedure staff may use.
- Who may view call, image, credential and door-event records.
- Which production changes require client approval.
A credential is what a person holds or presents; identity is the person or role behind it; personalisation is the per-person data carried by that credential. The integrator translates these client decisions into mappings and testable rules, but does not invent the access policy while configuring the system.
Run the ownership acceptance sequence
Evaluate ownership with scenarios rather than box inspection. Video Intercom and Door Station: The Test Plan a Buyer Should Demand expands the technical cases; this runbook adds the decision owner for each result.
| Scenario | Required result | Decision owner |
|---|---|---|
| Normal authorised call | Call, response, release and door state correlate | Integrator; client accepts |
| Unknown caller | No unauthorised release; denial is visible | Integrator |
| Network or server unavailable | Approved degraded mode is followed | Client and integrator |
| Controller unavailable | No undocumented release path | Integrator |
| Clock or event mismatch | Events remain ordered and correlatable | Integrator |
| Door state disagreement | DPS state and event are reconciled | Integrator; client approves |
Run each scenario with a named tester, witness, evidence location and signatory. A door position contact reports an open or closed state, not its cause, so a discrepancy investigation checks the controller mapping and source event rather than inferring the reason. The supplier joins where delivered product behaviour is questioned.
Route failures by first observable symptom
Route faults by the first observable symptom so one failure does not create three competing tickets. Video Intercom and Door Station Failure Patterns and How to Recover provides recovery detail; ownership starts with the symptom.
- The station cannot place a call: the integrator checks the documented setup and network path; the client owns site-network approval; the supplier investigates product behaviour if it is reproduced under that setup.
- The call reaches the wrong endpoint: the integrator owns routing and account configuration; the client confirms the endpoint roster.
- The call is answered but denied: the client confirms the policy, while the integrator corrects the role mapping.
- The release targets the wrong door or no door: the integrator checks door and controller mapping; the supplier confirms the documented interface behaviour.
- The door state disagrees: the integrator checks the DPS, controller and event source; the reported state is evidence, not a cause.
- An event is missing or duplicated: the integrator checks the clock, identifiers and delivery path; the supplier confirms event semantics for the exact SKU.
Do not close an incident as a product fault until the documented setup has been checked. Likewise, do not assign it to the client when the failure sits inside the integration configuration.
Transfer operational ownership with evidence
The intercom handover checklist turns ownership into evidence. At handover, the client accepts operational responsibility only for procedures, approvals and support routes that have named owners. The package contains:
- The as-built architecture and ownership boundaries.
- The configuration baseline and change history.
- Accepted test results and known issues.
- The supplier escalation route and evidence requirements.
- The client procedure, support rota and authority matrix.
- Record-purpose, access and retention ownership.
- The move, change and decommissioning procedure.
See Documenting Video Intercom and Door Station for Handover and Audit for the document set. At each review, name what the client will operate, what the integrator will support and what remains a supplier escalation.
Before purchase approval, require the selected supplier to map every open issue to one accountable owner and one acceptance document. If Smart Lock Factory is shortlisted, request the SKU-specific product evidence and interface documents needed to complete that map.
Put the answer on paper and request a quote against that document.

