Visitor management integration ownership split: A split of visitor management integration ownership across the lock supplier, the system integrator.

Δημοσιεύτηκε στις: Απρ 10, 2024

Who Owns Visitor Management Integration: Supplier, Integrator or Client

Who Owns Visitor Management Integration: Supplier, Integrator or Client

On the Tuesday after the quotation came back, I asked three people the same question: who owns the visitor record when a sponsor disputes a visit? The supplier said the record lives in the building system. The integrator said the building system was chosen by the client. The client said the lock produced the event that started the argument. Nobody was lying, and every answer was defensible. That is why the visitor management integration ownership split has to be written down first: ownership held in people's heads survives a quiet week, then fails on the first dispute, outage or holiday.

Direct answer. Short version — visitor management integration ownership split is treated here as visitor management integration ownership split first. visitor-management-integration comes second. The evidence for visitor management integration ownership split is named in the sections below. A visitor management integration ownership split shows what each component must assume about the others. visitor management integration ownership split is the interface that must be satisfied. Then commissioning starts on visitor management integration ownership split.

This article defines visitor management integration ownership split through visitor management integration ownership split. The definition of visitor management integration ownership split is deliberately narrow. It is non-statutory, and it applies to the market and product being discussed.

  • Draw the interface — write down what hands over between lock, door and system at visitor management integration ownership split
  • Exercise the handover — record the sequence that proves visitor-management-integration works end to end
  • Archive the record — store the commissioning evidence with the file for five questions
  • In visitor management integration ownership split, this sequence is what visitor management integration is checked against.

So this is the version I attach to a pricing run. It is written for the system integrator handed three things at once — a visitor requirement, a lock quotation, and a door schedule only one of them understands — who then has to make all three meet at a door at eight in the morning. The split I use attaches to decisions rather than to companies, because a company owns a product while a decision owns a behaviour. The question that follows is who owns the integration when the behaviour at the door turns out to be wrong, and it has one answer or none.

Crossing 1: the device belongs to the supplier, the behaviour

The supplier's obligation ends at the documented behaviour of the SKU it sells: what the device reports, what it accepts, what it cannot do, and the evidence for each claim on the dated product page for the specific SKU. It also owns the limits of its own product, including doors where its device is the wrong answer.

What the supplier must not absorb is somebody else's decision. A credential refused because the visitor is not on the approved list is a policy outcome that the lock reports; the lock is not the party deciding who visits. Whether the reader-to-controller path is a legacy Wiegand wiring convention or a specified bidirectional protocol such as OSDP is a per-SKU question — confirm on the dated product page for the specific SKU, and let that answer decide who owns commissioning the link. For the checklist this decision feeds into, use Hotel Smart Lock Property Management Integration. The commercial end of this decision is the smart door locks.

I ask for a written boundary rather than a friendly assurance. The sentence I want in the quotation is a refusal: this offer covers the device, its documented interfaces and the evidence for the specific SKU, and it does not cover the visitor policy, the controller configuration, the entitlement mapping, or the records kept in the building system. A supplier that will not write that sentence is telling you the integration is unpriced.

Crossing 2: the wiring, the controller and the degraded case

The integrator owns the path and the mapping: reader to controller to lock, the door position contact that reports a door is open, the exit device signal from the escape side, the translation of a client policy into entitlements per door, and the design of what still works when the network or the server does not. Degraded mode ownership sits with the integrator, subject to the client's approval of the state each door takes.

Two distinctions carry the weight. The reader only reports; the controller holds the door state and decides. And an audit log in the building system is not the event memory the device keeps when it cannot reach the server — the difference is exactly where events are quietly lost. The integrator owns both, and the routine that reconciles them.

The clock is also the integrator's to name. One authoritative time source has to cover authorisation, issuance, presentation, the access decision and expiry. Two clocks that disagree produce two honest records of one visit and a dispute nobody can settle from the data.

Crossing 3: the policy and the approvals belong to the client

The client owns who may visit, which doors a visit can reach, whether an escort is required, how long the credential stays valid, and what happens when a sponsor cancels. A client owned visitor policy is a rule the client wrote and the integrator implements; the integrator cannot change it, and the client cannot change the wiring. Visitor credential expiry ownership sits with the client, with an integrator consequence: the schedule that runs expiry and reconciles it.

The client also owns the approvals nobody can buy from a supplier — the local rule on visitor identity and screening, the retention of visitor records, and the approved release behaviour for the doors in the visitor path. These are questions to ask, not answers to assume. The retention period for visitor records is set by someone; the honest integration question is who confirms it and who signs.

CONFIRM-WITH-LOCAL-PRIVACY-LEAD: Confirm who sets the visitor record retention period here, who may read or export those records, and who signs the rule.

CONFIRM-WITH-LOCAL-EGRESS-LEAD: Confirm the approved release behaviour and degraded state for each door on the visitor path before the flow is signed off.

CONFIRM-WITH-LOCAL-SITE-APPROVER: Confirm the named owner of the visitor policy and of the door entitlements at handover, and when those names took effect.

Where the split lands: one decision, one owner

Every row has exactly one owner of the decision and one owner of the evidence. Those two are often the same party, and when they are not, the difference belongs in the same row. This is the visitor management integration ownership split stated as working positions, not as a chart of organisations.

Lifecycle momentSupplier ownsIntegrator ownsClient owns
Visit sponsored and approvedCredential formats its reader accepts, per SKUThe issuance route that produces themWho may be sponsored, and by whom
Credential handed to a visitorDevice behaviour when it is presentedWhere the issuing station sits, and its securityThe desk procedure and the escort rule
Door decisionThe event and state its device reportsThe controller holding door state and applying policyThe entitlement list and the door list
Door position and exit signalThe contact and device reporting the stateThe wiring and the controller inputsThe approved release behaviour per door
Expiry of the credentialDevice behaviour when validity endsThe schedule running expiry and reconciliationThe validity window and the exception route
Records of the visitThe event structure the device emitsThe repository, the export, the correction routeThe retention rule, the reader list, approvals

Read the table as a set of refusals. The supplier does not own the visitor policy, the integrator does not own the retention rule, and the client does not own the wiring. Each row carries a second question: if it is wrong at commissioning, who may change it, and who must be told? The row owner answers the first, the evidence owner answers the second. Most disputes here are not about the lock but about supplier versus integrator responsibility for a behaviour neither party wrote down.

The five questions that expose an empty owner

The five questions I ask in every handover meeting find an undrawn boundary faster than a questionnaire. Each needs a named answer, in writing, with evidence an outsider can check.

QuestionParty that answers itEvidence that closes itCost of an unanswered row
What does each side send, and what happens when it does not arriveIntegrator, against the supplier per-SKU interface noteInterface map plus degraded behaviour for one doorEvents vanish in the gap and nobody can say where
Who owns the clockIntegrator names the single authoritative sourceClock mapping across authorisation, issuance, decision, expiryTwo timestamps and one unresolvable dispute
What is written down, where it lives, who can read itClient confirms the rule, integrator supplies the repositoryAs-built register with a reader list the privacy lead confirmsRecords held longer than approved, or shorter than needed
What happens when the network or the server is unavailableClient approves the degraded state, integrator implements itRunbook countersigned by the egress and site approversThe door state is decided by nobody, at the worst possible hour
Which side owns the fixNamed per fault class before commissioningEscalation path with a receiving team and a closure recordA ticket that moves between three companies and closes nowhere

The escalation path

Once the rows have owners, faults stop being a negotiation. I classify the fault before I route it, because the first guess about who owns a fault is usually the first guess about who caused it. The integration escalation path belongs in the same schedule, with a receiving team on each branch.

flowchart TD
    A[Client policy decides who may visit] --> B[Integrator maps policy to doors and entitlements]
    B --> C[Supplier confirms device behaviour on the dated product page]
    C --> D[Controller holds the door state]
    D --> E[Device reports the event]
    E --> F[System decides what the event means]
    F --> G[Records keep the trail]
    G --> H{Fault class}
    H -->|Device behaviour| I[Supplier receives the defect]
    H -->|Interface or configuration| J[Integrator receives the defect]
    H -->|Policy or permission| K[Client receives the request]

Each receiving route needs a named team, the evidence it expects, and a closure record. The supplier route is not the dumping ground for what the integrator cannot configure, and the client route is not where the supplier's dated product page should have answered.

The evening the controller stopped answering

A scene from a pilot, because it is where the split either holds or fails. At 19:40 the controller became unreachable. A visitor whose credential was due to expire that hour was still on site with an escort on the other side of the door. Staff released the door manually, and the next morning's visit record contained a gap.

Nothing about that evening was an engineering surprise. It was an approval question wearing an outage costume. The offline case is the design, not the exception, so the runbook had to name in advance who may authorise a manual release, what is written down by hand, and how that release is reconciled against the event memory once the controller returns. If the answer would have been that the door simply fails locked, that is a decision the client's own approvers make, with their egress and fire review.

The folder that travels with the handover

The ownership split becomes real when it becomes documents with names on them: the as-built interface map, the door and device register, the entitlement matrix, the clock mapping, the account and service-identity register, the outage runbook, the reconciliation procedure, the open-defect list, and the ownership schedule.

It is worth pairing this with sl 6301 for wooden doors. That is the same question visitor management integration ownership split has to answer here.Retention and privacy live in that folder as a question rather than a number. The integrator supplies the capability and the export route; the client's privacy lead confirms the period, the reader list, the correction route and the export authority, and the signed answer is filed against the build.

The same question is worked through in more detail in the sl 6301 office application. That is the same question visitor management integration ownership split has to answer here.

Three sentences I put in the scope

The split survives a real project because it is written into the document the parties already sign. Three sentences do most of the work. For each behaviour in the visitor flow, one named party owns the decision and one named party owns the evidence that proves it. No party accepts a behaviour it cannot change and explain. Anything a party cannot own in writing is an open item with a name and a date attached, not a caveat in an email.

Send that schedule with the pricing run rather than after it: the ownership column tells you whether the integration you are buying is a product, a project, or a disagreement waiting for a holiday. The commercial route is request a quote with the schedule attached, and order samples puts the device behaviour on your own doors before the rows are signed. For the document side, the Visitor Management Integration Requirements Document Template gives the fields the rows land in, the Visitor Management Integration for Smart Lock Projects: What Buyers Must Define First sets the questions that come before ownership is assigned, and the Documenting Visitor Management Integration for Handover and Audit covers the folder carrying the evidence out.

Το καλάθι σας
Η εμπειρία σας σε αυτόν τον ιστότοπο θα βελτιωθεί με την ενεργοποίηση των cookies Πολιτική cookies
Chat on WhatsApp