Who Owns Door Controller Interfaces: Supplier, Integrator or Client
Decision requested. Approve the door controller interfaces ownership split before accepting controller interfaces as an evaluated subsystem. The memo assigns product evidence, design work, client decisions, change control and support closure to named roles.
Direct answer. The one-line answer — door controller interfaces ownership split is the working record for door controller interfaces ownership split. door controller interfaces ownership split is worthless until door-controller-interfaces is attached to it as evidence. A door controller interfaces ownership split is an integration view. Lock, door, reader and system have to behave together. door controller interfaces ownership split is where the first interface behind door controller interfaces ownership split fails.
door controller interfaces ownership split is used here in the narrow sense set out in door controller interfaces ownership split. It is a working definition built for door controller interfaces ownership split. It is not a statutory one, and it has to be read against the market and product concerned.
Memo scope and decision controller interfaces ownership split
| Field | Entry |
|---|---|
| To | System integrator lead, access-control engineer and client buying team |
| Subject | Allocation of door controller interface decisions and fixes |
| Stage | Evaluation |
| Scope | Reader, controller, door hardware, building platform, operations and records |
| Required result | One accountable owner, evidence and escalation route for every interface boundary |
This memo covers the door-controller-interfaces boundary between supplied equipment and the building. It does not select a lock, protocol or operating outcome. It defines who must prove capability, translate that capability into a design, approve the result and close a fault. Every commercial claim here has to be checked against the smart door locks.
Ownership here means authority to provide evidence, approve a requirement, authorise a change or close a fault. It does not mean one party must perform every task. Shared execution is acceptable; shared accountability is not.
Interface ownership map
The controller holds the door state and makes the access decision; the reader only reports. Ownership must therefore distinguish product claims from the design connecting the reader, controller, platform and operator.
| Boundary | Accountable owner | Required evidence | Supporting role |
|---|---|---|---|
| Product capability | Supplier | Confirmation on the dated product page for the specific SKU and a written response | Integrator checks fit |
| Controller decision and configuration | Integrator | Configuration baseline, logic description and change record | Client approves access rules |
| Reader-to-controller path | Supplier for capability; integrator for implementation | Path, addressing and wiring or configuration record | Client defines required use |
| Door-position input | Integrator | Point list, state definition and exception treatment | Client accepts operating response |
| Building-system or API boundary | Integrator | Interface specification, data map and error handling | Client grants system access |
| Records, clock and retention | Client for policy; integrator for implementation | Timestamp source, log schema, storage and access list | Supplier confirms available fields |
| Change and release | Integrator | Versioned interface record, regression evidence and rollback plan | Client authorises release |
| Fault closure | Party owning the failed boundary | Ticket evidence, root cause and corrective record | Client confirms acceptance |
Assign one accountable owner to each row. Where two parties appear, separate capability evidence from implementation or policy approval. A row labelled “joint” without a named decision maker is incomplete.
Three ownership tests
Use three tests when assigning a disputed line. If the statement concerns supplied hardware or a published capability, the supplier must provide dated evidence. If it combines systems, routes data or defines fallback behavior, the integrator owns the design. If it chooses an operational outcome, risk or organisational access policy, the client owns approval.
The interface ownership matrix becomes usable only when each row has one accountable owner. The supplier integrator responsibility split is not a transfer of blame: the supplier remains accountable for capability evidence, while the integrator remains accountable for applying it correctly in this building.
The client approval matrix records the outcomes the client accepts, including degraded behavior and record access. The door controller responsibility matrix then links each approval to a boundary owner and an escalation route.
Evidence gate before design acceptance
Use the following gate before an interface enters the approved design. It prevents a product description from becoming an untested building assumption.
flowchart TD
A[Requirement received] --> B{Supplier evidence supplied}
B -->|No| C[Request dated evidence]
C --> B
B -->|Yes| D{Building boundary named}
D -->|No| E[Hold interface acceptance]
D -->|Yes| F{Degraded behavior defined}
F -->|No| G[Define degraded behavior]
G --> F
F -->|Yes| H{Client approves outcome}
H -->|No| I[Revise requirement]
I --> D
H -->|Yes| J[Release responsibility schedule]
The supplier answers capability questions first. The integrator then names the building boundary and degraded behavior. Finally, the client approves the resulting outcome. An interface remains in evaluation if any gate lacks evidence.
CONFIRM-PER-SUPPLIER: Obtain a written capability response tied to the dated product page for the specific SKU.
Minimum interface schedule
Each schedule entry should state what each side sends, what it means and what happens if it does not arrive. Specify whether the boundary is a local API or cloud API and whether the design is centralised vs standalone.
| Schedule field | Required statement | Evidence owner |
|---|---|---|
| Communication | Source, destination, direction, payload, acknowledgement and timeout treatment | Integrator |
| Identity and addressing | How a reader, controller or endpoint is identified and changed | Supplier and integrator |
| Decision state | Which device holds state and where the access decision is made | Supplier and integrator |
| Door position | Door position contact reports open or closed, not the cause of that state | Integrator |
| Exit indication | Request to exit reports operation from the escape side; it is not a release command | Supplier and integrator |
| Timing | Clock source, synchronization method and correction procedure | Client and integrator |
| Records | Audit-log fields, event-memory limits, storage and reader permissions | Client and integrator |
| Degraded mode | Behavior when the network, controller or server is unavailable | Integrator |
| Changes | Version, test evidence, rollback trigger and release authority | Integrator |
CONFIRM-WITH-LOCAL-EGRESS-LEAD: Ask which authority signs off the installed door’s escape, release and fail-state arrangement.
CONFIRM-WITH-LOCAL-PRIVACY-LEAD: Ask which access-event data is retained, where it lives, who can read it and which retention period applies.
Five questions that expose an unowned boundary
What does each side send, and what happens when it does not arrive? Name the message, expected response, missing-data consequence and degraded behavior. The supplier documents product-side behavior; the integrator specifies the building response; the client accepts the outcome.
Who owns the clock? State which clock stamps each event, how devices remain aligned and how an ordering correction is recorded. A server timestamp cannot silently overwrite a controller timestamp.
What is written down, where does it live, and who can read it? Distinguish the audit log from event memory. An audit log records an event with time and source; event memory is the lock’s buffer when it cannot reach the server. State storage, access and retention ownership.
What happens when the network, controller or server is unavailable? Name the last known state, the operation that remains available and the recovery check. Which fail-safe or fail-secure outcome applies? Treat it as an approval question because the door’s role and local authority determine it.
Which side owns the fix? Define the first diagnostic evidence, escalation path and closure authority. A ticket must point to one failed boundary even when hardware, software and operations are present.
CONFIRM-WITH-LOCAL-EGRESS-LEAD: Require approval evidence for the selected degraded door state before the interface enters service.
Degraded-mode ownership
The offline case is the design, not the exception. Define the state to preserve, the event to buffer, the point of reconciliation and who can resume normal operation after recovery.
| Failure point | Supplier responsibility | Integrator responsibility | Client responsibility |
|---|---|---|---|
| Reader does not respond | Explain confirmed capability and diagnostics | Isolate path and apply approved fallback | Accept operational consequence |
| Controller is unavailable | Supply confirmed behavior and limits | Test fallback and restore sequence | Authorise return to service |
| Platform is unavailable | Explain event and configuration limits | Map local behavior and later reconciliation | Approve service continuity |
| Door-state input is missing | Explain device behavior | Prevent unsupported inference and test response | Accept temporary operating rule |
| Interface change fails | Support confirmed configuration limits | Execute rollback and document regression | Approve resumed release |
The lock reports the state; the system decides what the state means. During degraded operation, that rule prevents an open-door indication from being treated as proof of why the door is open.
Capability and change control
The schedule may ask whether the reader-to-controller path is Wiegand or OSDP. Wiegand is a legacy wiring convention between a reader and controller; it carries a data line and usually power and ground, and it says nothing about encryption or device identity. OSDP is a specified, addressed, bidirectional protocol with device addressing and a defined message structure. Whether a given lock implements either path is a per-SKU question: confirm on the dated product page for the specific SKU.
CONFIRM-PER-SUPPLIER: Attach the supplier’s written implementation statement to the schedule.
A supplier change, integrator configuration and client approval are separate events. The supplier owns capability evidence and confirmed limits; the integrator owns version compatibility, test evidence and rollback; the client owns the approved operating requirement. Re-open the schedule when any one changes.
Allocation models
The integration responsibility split should make escalation shorter, not divide every task. Compare ownership models before accepting the schedule.
| Model | Main strength | Main failure exposure | Evaluation decision |
|---|---|---|---|
| Unqualified shared ownership | Appears collaborative | No owner can close a fault | Reject |
| Supplier-led | Clear hardware authority | Building integrations and records drift | Use only for product claims |
| Integrator-led | Clear design coordination | Client outcome approval can be missed | Accept with explicit client gates |
| Boundary-led with client outcome approval | Separates capability, design and policy | Requires disciplined evidence control | Recommended |
Use boundary-led ownership as the evaluation baseline. The supplier remains the source for product claims, but it should not decide how a building platform uses those claims. Likewise, the integrator should not make the client’s operational or policy decisions.
Evidence package and handover
The evaluation file should combine site facts, interface evidence and operating decisions. The Smart Lock Retrofit Site Survey and Office Smart Lock Site Survey provide site inputs. For controller verification, use the Door Controller Interfaces: The Test Plan a Buyer Should Demand as evidence rather than another design narrative. The Documenting Door Controller Interfaces for Handover and Audit shows how controller interface handover becomes an auditable package.
The practical counterpart to this point is smart lock vs biometric access control. That is the same question door controller interfaces ownership split has to answer here.Before approval, require the ownership schedule, dated product-page extract, supplier response, point list, data map, clock source, record-access list, degraded-mode test, change procedure and support matrix. Record each unresolved item against one accountable owner and a due date.
Approval record — door controller interfaces
| Decision | Client approver | Evidence retained |
|---|---|---|
| Required access outcome | Access-control owner | Approved requirement |
| Degraded door behavior | Operational owner | Test result and approval reference |
| Record access and retention | Privacy owner | Data map and access list |
| Interface release | Change authority | Versioned baseline and rollback plan |
Approve the door controller interfaces ownership split as the evaluation baseline, not as a permanent transfer of responsibility. Issue the same ownership schedule to each shortlisted supplier and require its evidence to map to the same boundaries. This creates a comparable commercial response: the client can see the supplied capability, the integrator can see the implementation duty, and each fault has a named owner.
Nothing is binding until a supplier prices it, so request a quote.

