Wiegand vs OSDP for a Multifamily or Office Portfolio
A portfolio asks the reader-to-controller question once per building and again every time a wing is re-fitted or a panel is replaced. Underneath those repeats sits one technical question: what actually crosses the path between the credential reader and the controller, and what is each side entitled to assume about the other. The answer changes across the estate because the buildings were commissioned in different decades and sit on panels of different ages, so the risk in a portfolio is not choosing the wrong technology — it is producing a programme in which the same question has four answers and nobody can say which answer governs which door. A wiegand versus osdp portfolio case is therefore a scheduling problem before it is a technical one.
- Outline the interface — write down what hands over between lock, door and system at wiegand versus osdp portfolio case
- Rehearse the handover — record the sequence that proves wiegand-vs-osdp works end to end
- Log the exchange — store the commissioning evidence with the file for estate schedule
- wiegand versus osdp portfolio case runs this sequence, and wiegand vs osdp is the record it produces.
What follows is an annotated dialogue between two people who would really have this conversation. The integrator lead runs a multi-site programme and owns the door schedule. The portfolio engineer is the owner's access-control engineer and owns the panels on every site. The exchange is illustrative: it assembles the questions a portfolio programme raises into a plausible conversation, and it is not a record of any real meeting, client, estate or supplier, and no figure in it describes a market.
Two rules govern the transcript. No protocol or ecosystem name is asserted for any product in it; where one comes up it becomes a question with a place to get a written answer, and per-model facts are confirmed on the dated product page for the specific SKU. The annotations after each turn are the working output: a turn ending in a margin note has produced something the integrator can file.
Direct answer. A wiegand versus osdp portfolio case is decided by a classification step before any protocol is named. The estate is sorted into path classes — doors where the lock decides alone, doors on a legacy wiring convention with one channel per reader, doors on an addressed bus, doors read by a controller rather than a reader, and doors a third party controls — and the programme then writes one rule per class. Every rule carries five answers: what each side sends and what happens when it does not arrive, who owns the clock, what is written down and who may read it, what the door does when the link dies, and which side owns the fix.
The estate schedule and the cell nobody filled in The range
Integrator lead: Here is the estate as it arrived. Several buildings, two generations of panel, one owner's team holding all of it. Every door line carries a column called reader interface, and on every line it says the same two words: to be confirmed. Whoever filled that schedule in was asked for a door type and a finish, not for a data path, so the column was never a column.
Portfolio engineer: And now somebody wants to confirm it. That is the wrong verb. You cannot confirm a column that says the same thing on six hundred rows and expect the answer to mean anything.
Integrator lead: I have been asked to price smart locks against this schedule. If the column has one answer, I price against one answer. If it has five, the schedule has to say which door sits in which group before anything goes in the quotation.
Portfolio engineer: Then the first deliverable is not a protocol and not a lock. It is a re-cut of your own schedule: split it by door population rather than by door, add a column for the path class, and add a column for who owns the system behind that door. The moment you do that, most of the argument dissolves, because the estate was never one thing.
Margin note — integrator action: Re-cut the estate schedule into one row per door population with four new columns: path class, decision point, panel owner and system owner. Keep the original row-per-door schedule untouched beside it as the evidence of what changed and why.
Portfolio engineer: It is. The oldest panel predates the newest by more than a decade. The middle building was fitted by a different contractor who bought readers from a different supplier. One wing sits on a controller the owner's IT team reaches remotely; another sits in a cupboard nobody has opened since handover. A single rule across all of that is a fiction, and the fiction is what you are being asked to price.
Margin note — integrator action: Record the panel make, the panel vintage and the last documented commissioning for every site before the schedule is re-cut. Where that record does not exist, list the site as unverified rather than assuming continuity from the neighbouring building.
Sorting the estate into paths before a protocol is named
Portfolio engineer: Five classes, and the first one quietly saves the programme money. Class A is every door where the lock reads the credential and decides alone. Nothing crosses a wire to anybody. That covers the in-unit doors of a multifamily portfolio and the single-occupancy doors of an office estate, and in a portfolio of any size it is usually the largest population by door count. There is no reader-to-controller segment to specify, so that is the answer to the schedule column on those rows — and it must be printed as a sentence with a reason, because a blank cell is an invitation somebody will fill with a tick.
Integrator lead: What is Class B?
Portfolio engineer: Class B is the legacy wiring convention: a formatted code on a data line, one channel per reader, into a controller that has been there since before most of the estate team were hired. Class C is the addressed bidirectional path, several devices on a run, each with an address, on a building commissioned recently or since refreshed. Class D is where the endpoint is a controller rather than a reader, because one building's doors are read by the panel in the next building. Class E is everything the owner does not control: base-build plant rooms, demised tenant areas, a third party's own system. Class E is not a problem to solve, but it is a problem to record, because it is where the estate's assumptions quietly stop.
flowchart TD
ESTATE["Portfolio of buildings"] --> A["Class A - lock reads and decides alone"]
ESTATE --> B["Class B - legacy wiring, one channel per reader"]
ESTATE --> C["Class C - addressed bus, a device address per reader"]
ESTATE --> D["Class D - the endpoint is a controller"]
ESTATE --> E["Class E - a third party controls the door"]
A --> A1["Nothing crosses a wire"]
B --> B1["Controller decides, the panel channel is the identity"]
C --> C1["Controller decides, the address names the source"]
D --> D1["Two panels, a mapping between them"]
E --> E1["Recorded as outside our scope"]
| Path class | What crosses it | Where the decision is made | What the schedule must print |
|---|---|---|---|
| Class A · lock decides alone | Nothing crosses a wire | Inside the lock, against data written at the issuing desk | Not applicable, and why |
| Class B · legacy wiring | A formatted code on a shared data line, one channel per reader | At the panel | Panel, channel number, reader model, cable type |
| Class C · addressed bus | A framed payload inside a message that names its source | At the controller | Controller, device address, run and termination |
| Class D · controller reads controller | The same payload, but the endpoint is a panel | At the receiving panel | Both panel identities and the mapping between them |
| Class E · third-party controlled | Whatever the third party's own system carries | On the third party's system | Out of scope, plus the interface we rely on |
Margin note — integrator action: Mark every Class A door explicitly, and price it as a standalone decision rather than as a door waiting for a reader to be specified. In a portfolio this is usually the largest saving available before anyone discusses cabling.
What the legacy wiring carries and what nobody may assume
Integrator lead: Say the uncomfortable part. On Class B, what is the reader actually telling the controller?
Portfolio engineer: A burst of clocked pulses representing a code of an agreed width, usually with parity added. The convention fixes neither the width nor the parity scheme nor what the controller does with the result, because each panel vendor decided that separately and has kept deciding it separately ever since. It carries a power line and a ground as well as the data line, and it carries no encryption and no device identity at all.
Integrator lead: So when the panel tells me a card was presented at input four, what it is really telling me is that something happened on the wire at input four.
Portfolio engineer: It is telling you that input four changed state in a way the panel could decode, which is a smaller statement than it sounds. That is why the ledger below exists: silence on that line and a code the panel did not expect look the same from the controller's side, so the two failures get confused for ever unless somebody separates them on purpose.
Integrator lead: Then what is honest to write in the assumption ledger for Class B?
Portfolio engineer: Write the assumption, say plainly whether it is held or not held, and name who closes it. An assumption that is not held is a legitimate entry, and it is what lets the owner see the risk instead of inferring it from silence.
| Assumption a party might make | On the legacy wiring convention | Who must close it |
|---|---|---|
| The code that arrived is the code that was presented | Not safe to assume on a long or shared run | The integrator, by test on the installed door |
| I know which reader sent this | Not held; the input channel is the identity | The commissioning engineer, by the mapping record |
| The reader is alive and answering | Not held; silence resembles a refused credential | The integrator, by fault injection |
| The panel heard about it | Not held; the convention has no acknowledgement | The integrator, by observing the input state |
| The credential format is what I expected | Agreed informally, years ago, between two vendors | The integrator, from two dated datasheets |
| Nothing was altered in transit | Not held | The owner, with a named compensating control |
Margin note — integrator action: Keep the ledger as a live document with three columns: assumption, held or not held, and who closes it. A row marked not held needs a compensating control and a name beside it, or it is a risk the estate is carrying without knowing it.
What changes when a building is wired for an addressed path
Integrator lead: Put one building on the addressed path. What actually changes for me as the integrator?
Portfolio engineer: Two things change and one thing does not. The first is that identity becomes a property of the wire rather than a property of the wiring. The protocol is a written specification with an addressed, bidirectional message structure, so the controller can ask a device a question and receive an answer, and a damaged or duplicated message is meant to be visible rather than silently accepted — subject to what the two implementations actually do, and to which optional features are licensed and enabled.
Integrator lead: And the second change?
Portfolio engineer: The commissioning record becomes the deliverable. On a legacy path, a wrong channel assignment is caught by a person opening the door. On an addressed path with several devices sharing a run, a wrong address assignment can leave two doors answering to each other and nobody notices for a season. Provisioning is bringing a device into service with its identity, its door and its owner, and the address book that comes out of it proves the estate is not running on memory.
Integrator lead: And the thing that does not change?
Portfolio engineer: The credential format problem does not change. The reader still has to emit something the controller decodes, and that agreement is still made between two organisations who have never spoken to each other. A framed message tells you which device spoke and whether the frame survived the trip. It does not tell you that the code inside it means the credential the person is holding.
sequenceDiagram
participant Holder
participant Reader
participant Controller
participant Platform
Holder->>Reader: Credential presented
Reader->>Controller: Code on the data line
Controller->>Controller: Decide against the held list
Controller-->>Reader: Release indication where supported
Controller->>Platform: Event with time and source
Platform-->>Controller: Acknowledgement
| Work item on the path | Class B on legacy wiring | Class C on an addressed bus |
|---|---|---|
| Identifying a reader at the controller | The channel number in the panel configuration | The address assigned at commissioning |
| Proving a reader is the commissioned device | A mapping record plus a physical check | An address book reconciled against the door schedule |
| Telling a dead reader from a refused credential | Not possible from the panel alone | The controller can poll, subject to the implementation |
| Noticing a lost path | Easy to miss, easy to misread as a denial | Usually visible as an error, subject to the implementation |
Margin note — estate action: Treat the address book and the door schedule as two lists that must be reconciled at handover, after every panel replacement and after every controller move. A device in one list and not the other is a finding; a door in the second list with nothing behind it is a door nobody controls.
One rule per class, the exceptions, and the timetable
Integrator lead: A class rule per building sounds tidy until somebody hands me the exception list.
Portfolio engineer: The exceptions are the rule. A standard with no register attached does not survive a portfolio, because a portfolio is where the odd door lives — the demised area, the stair door with an approved arrangement, the plant room on somebody else's panel. So you write the class rule and the exception register, and the register is reviewed on the same cycle as the rule. The rule says what applies by default; the register says what was carved out, why, and who approved it. An exception without an approver is a hole, and a hole is found at the worst possible moment by somebody carrying a ladder.
| Exception family | Why it breaks the class rule | How the estate standard handles it |
|---|---|---|
| A demised area under the tenant's own system | The path crosses into a system the owner does not administer | Recorded as Class E and named in the door schedule |
| A stair door with an approved release arrangement | The escape-side behaviour is fixed by an approval, not by the class | The fail state is recorded per door against the approval reference |
| A door served from a panel the schedule does not name | The endpoint is not the panel the class assumes | Class D, with both panel identities printed on the schedule |
CONFIRM-WITH-LOCAL-EGRESS: Ask the approving authority in the jurisdiction of each building what the escape side of each door type must do when power is removed, when a fire signal is present, and when the controller stops answering; ask which authority signs the installed assembly off; and ask what evidence they require. Verify the scope for every door type and every building separately — a portfolio crosses jurisdictions, and one building's answer is not another's.
Integrator lead: The estate standard is one document, but the egress position is not one document. Can the class rule still hold if the answer changes by site?
Portfolio engineer: It can hold for the data path and must not be allowed to cover the door's release behaviour. Release on the escape side is the default behaviour of the exit device, and the request-to-exit signal is a report that it happened, not a command to release. Keep the fail state per door, per approval, out of the class rule, or the class rule will quietly become an approval you never obtained.
Integrator lead: What sets the timetable, then? Not my preference and not the brochure.
Portfolio engineer: The panel replacement cycle, the capital programme and the fabric works. Write the standard against two horizons. On the refresh horizon, for anything being commissioned, replaced or extended now, the class rule applies at full strength and the written confirmations are part of the tender. On the retention horizon, for a building whose panel is staying, the class rule is Class B and the estate accepts, in writing and with a named owner, the gaps that come with it. Either way the estate runs two standards and one schedule, and the schedule says which standard applies to which building on which date, because the moment you upgrade one building and not its neighbour the people servicing the estate hold two rulebooks and assume they are the same.
Margin note — integrator action: Add two columns to the estate schedule that are usually missing: the planned refresh date for the panel on that building, and the date on which that building's class rule was last reviewed. The first tells a future contractor what the estate expects; the second stops an unreviewed rule from outliving its evidence.
Integrator lead: And decommissioning is not decorative.
Portfolio engineer: It is not. Decommissioning is removing a device from service, and it is a separate, recorded operation with its own date, its own author and its own evidence. On a legacy path a retired reader still wired to the panel still holds a channel; on an addressed path a device left on the bus still answers, and an address that still answers is an orphan credential on a live network.
One clock per site and the arithmetic that breaks the record
Integrator lead: I want to talk about time, because it is the one thing that silently ruins a record and never shows up as a fault.
Portfolio engineer: It is the one thing that cannot be reconstructed after the fact. If two systems disagree about the time, the disagreement is permanent and it corrupts the ordering rather than the content.
Integrator lead: And in a portfolio it is worse, because you have several sites and possibly more than one time zone, and the clocks drift at different rates.
Portfolio engineer: Which is why the estate answers the clock question before it answers anything else, per class, with four columns: the authoritative clock for a credential event, the clock that is actually recorded, the permitted difference, and who corrects it. Without the permitted difference, nobody can say whether a two-minute gap is a fault or a rounding.
Integrator lead: And there is a second problem, the one noticed by a person rather than a monitor.
Portfolio engineer: Order. Two events recorded by two devices whose clocks differ by a few minutes can be stored in the wrong order, and then a report that reads as a sequence of events reads as a different sequence of events. The rule that survives this is simple: the recorded event keeps the time it was stamped with at capture, and a system that receives it later may attach its own arrival time without overwriting the original.
| Path class | Authoritative clock | What is recorded | Permitted difference | Who corrects it |
|---|---|---|---|---|
| Class A | The lock's own clock, against the window written on the credential | The lock's own timestamp | Set by the owner as an estate tolerance | The portfolio engineer, at the scheduled check |
| Class B | The panel's clock | The panel's timestamp, forwarded unchanged | Set by the owner as an estate tolerance | The portfolio engineer, from the estate time source |
| Class C | The controller's clock | The controller's timestamp plus the platform's arrival time | Set by the owner as an estate tolerance | The portfolio engineer |
| Class D | The receiving panel's clock | The receiving panel's timestamp | Set by the owner as an estate tolerance | The portfolio engineer |
| Class E | The third party's own system | Whatever the third party preserves | Not ours to set | The third party, under the interface agreement |
Margin note — estate action: Fix one tolerance for the whole estate and record it. Where a site crosses a daylight-saving change or sits in another time zone, record the site, the zone and the correction rule, because an estate-wide report that mixes local and coordinated time is a report nobody trusts twice.
Integrator lead: This is the question I would have answered last, and I can see that it should be answered first.
Portfolio engineer: It is answered first because it is the only one of the five that cannot be repaired retrospectively. A wrong credential format can be corrected in the schedule. A missing event cannot be reconstructed. A mis-stated fail state can be re-approved. A clock that was wrong on the night stays wrong on the night.
Where a record is born, where it waits
And who may read it.
Portfolio engineer: Take it from the end. Three questions: what is written down, where does it live, and who can read it. If nobody can answer all three, the integration has not been specified, however good the cabling is.
Integrator lead: And the part that trips people is the middle one.
Portfolio engineer: It is. The audit log and the event memory are not the same thing, and the difference between them is exactly where events are lost. The audit log is a record with a time and a source, held by the system that owns the estate. The event memory is the holding area inside a controller or a lock when it cannot reach that system. Every event that never reached the audit log was somewhere in a buffer, and that buffer has a finite depth and a flush condition somebody needs to know.
erDiagram
DEVICE_EVENT {
string door_id
string credential_id
datetime stamped_at
string decision
}
CONTROLLER_BUFFER {
int depth
string flush_rule
}
PLATFORM_LOG {
string event_id
datetime recorded_at
string source_device
}
ESTATE_REPORT {
string join_source
datetime window
}
DEVICE_EVENT ||--o{ CONTROLLER_BUFFER : held_in
CONTROLLER_BUFFER ||--o{ PLATFORM_LOG : flushed_to
PLATFORM_LOG ||--o{ ESTATE_REPORT : joined_into
Integrator lead: So the loss point is the flush, and a long outage fills the buffer faster than the estate realises.
Portfolio engineer: It does, and the estate answer is a number: the buffer depth, the flush condition and the period the door keeps working without the platform. Those three are what you tell the owner when they ask how long the estate can be disconnected before the record has holes. The generic answer is that the door keeps working; the useful answer is a figure with a condition attached, taken from the vendor's dated document.
Integrator lead: And who reads it? In an office portfolio the record is employees entering and leaving their workplace. In a multifamily portfolio it is residents moving around their own building. Neither of those is a neutral dataset.
Portfolio engineer: Neither. An access log is a record of people's movements, so the estate treats it as personal data by default until the local regime says otherwise, and the questions go to the owner's counsel and the local data-protection contact rather than to a supplier.
| Record | What it says about a person | The question the owner must answer |
|---|---|---|
| Resident entry log | Who came into which building, and when | How long it is kept and who may read it |
| Employee access log | Where a member of staff was, and when | Whether staff are told, and what local workplace rules require |
| Multi-site estate view | Movement patterns across several buildings | Whether one site can see another site's doors |
CONFIRM-WITH-LOCAL-PRIVACY: Ask the owner's counsel and the data-protection authority for each jurisdiction the estate operates in what an access record may be used for, how long it must be kept, who inside the estate and who outside it may read it, and what an occupant or an employee is entitled to see about their own record. Confirm the scope per record category and per site; a resident log and a contractor window are not the same question.
Integrator lead: That last row frightens me, because we are proposing one platform for the whole estate.
Portfolio engineer: Then say so in the specification rather than leaving it to be discovered. One platform, several sites, and a rule that no site's doors are visible to another site's operators unless the owner grants it in writing, is a design decision. The Cloud Multi Tenant Management for a Multifamily or Office Portfolio treatment covers the mechanics of that separation, and Audit Export and Legal Hold for a Multifamily or Office Portfolio handles where an access record sits and who may read it.
What every path does when the link dies
Integrator lead: Tell me the estate's answer to the question I cannot answer for any single door.
Portfolio engineer: Each class has its own degraded mode and the estate names all of them. For a standalone lock the credential carries its own authority, so the door keeps working when the network is down and its events wait in the device's own memory. For a panel it depends entirely on where the credential list lives, and that is a configuration decision the estate imposes on the panel vendor: the list is held at the controller, not fetched from the platform on every read. If the list is fetched from the platform, a platform outage becomes a door outage across every building on it.
stateDiagram-v2
[*] --> Enforcing
Enforcing --> Degraded : the platform cannot be reached
Degraded --> Enforcing : the link returns and events flush
Degraded --> Held : the buffer fills
Held --> Enforcing : recovery flush and reconciliation
Enforcing --> Absent : the controller loses power
Absent --> Enforcing : the controller restarts and reloads its list
Absent --> [*]
| Failure | Class A | Class B | Class C | Who decides |
|---|---|---|---|---|
| The platform is unreachable | The lock keeps enforcing the credential; events wait in its memory | The panel keeps deciding, provided it holds the list | The controller keeps deciding, provided it holds the list | The owner, in writing, before handover |
| The controller is powered down | Not applicable | The door takes its approved fail state | The door takes its approved fail state | The owner and the approving authority |
| The reader cable is cut | Not applicable | The panel shows an inactive input or a refusal | The controller sees the device stop answering | The integrator, by fault injection |
| Power is removed at the door | The lock takes its approved state | The lock and strike take the approved fail state | The lock and strike take the approved fail state | The owner and the approving authority |
Integrator lead: Every row in the last two columns ends with somebody else's decision.
Portfolio engineer: Because it does. Fail-safe or fail-secure is decided by the role the door plays and by the approval behind it, never by the product or by the integrator's convenience. If the answer for a door is that it fails locked, that is an approval question for the owner and the approving authority, not an engineering choice the integrator can close inside a test report.
CONFIRM-WITH-LOCAL-FIRE-INTERFACE: Ask which authority signs off the interface between the access control system and the fire alarm system in each building, what the release logic is, who is permitted to place the system in a released state, and what happens if the fire signal arrives while a credential is being presented. Confirm the scope per building, and do not accept the name of a standard as an answer.
Integrator lead: One more piece of the door arrives on the same cable as the credential, and it gets confused with it constantly.
Portfolio engineer: The door position contact. It reports open or closed and it reports a state rather than a cause, so it cannot tell you whether the door was opened by a valid credential, by the handle, by a wedge, or by somebody who had no business there. The Door Position Contacts for a Multifamily or Office Portfolio treatment covers that signal on its own; the point here is narrower, which is that the path boundary in the schedule has to name which device is which, or the panel's view of a door-open bit gets confused with the panel's view of a credential event. The same applies to the exit-side signal, covered in Request to Exit Devices for a Multifamily or Office Portfolio.Integrator lead: So the offline case gets designed, not discovered.
Portfolio engineer: Treat it as the design rather than the exception, and write it into the class rule before the first door is signed. The Offline and Degraded Mode Operation: The Test Plan a Buyer Should Demand treatment runs the same discipline over the outage cases.
Who answers the call at two in the morning
Integrator lead: Here is the question the site managers actually ask me: when it goes wrong, who do they call, and who does not call anyone else?
Portfolio engineer: That is the fifth question and it is the one that decides whether a programme is finished. In a portfolio there are three parties before you reach a supplier: the site's own building manager, the portfolio engineer who owns the systems, and the integrator who commissioned the work. Each has a decision they are allowed to take alone, and a decision they are not. Write the boundaries as decisions rather than as people, because people move jobs; the same reason applies to vendors, since a boundary row with a name beside it is a contract while a row with a role beside it is a service model that survives a reorganisation.
| Situation | The first call goes to | The decision that can be taken at once | The decision that must not be taken at once |
|---|---|---|---|
| An occupant cannot enter at the entrance | The site's building manager | Check the credential's status and the door's reported state | Removing a reader or changing a panel configuration |
| The panel reports denials across several doors | The portfolio engineer | Read the controller state and identify the affected input | Declaring the site closed |
| A reader or a door has failed | The integrator's service desk | First-line test on the installed path under the class rule | Replacing a device that appears on the exception register |
| A credential was presented and the record shows nothing | The portfolio engineer | Compare the event memory with the audit log | Concluding that no event occurred |
Margin note — estate action: Publish the escalation order as one page, with the out-of-hours route for each class, and confirm that the first-line technician can test a path without holding a privileged account. The Smart Lock Commissioning Checklist and Smart Lock Testing After Installation are the published material most portfolios use as the basis for that first line.
Integrator lead: Where does the contractual half sit?
Portfolio engineer: Separately, and it is a different conversation. Whether the supplier or the integrator carries the cost of a path that behaves as its dated document said it would is a contract question, not an operations one, and Who Owns Wiegand vs OSDP: Supplier, Integrator or Client sets that out. What belongs in the estate document is the operating boundary: who answers first, who decides, and what evidence each party produces before the next party is involved.
Getting the supplier to answer in writing
Integrator lead: Let us deal with the hardware, because this is where the programme usually stalls. A supplier tells me a lock is fine with our panel. Fine how?
Portfolio engineer: Then the supplier has not answered. The question was never whether the lock is fine with your panel in general; it is what this model code does, what it carries, and what it will not do. Any capability, protocol or holding claim is per-model and per-SKU, confirmed on the dated product page for the specific SKU rather than accepted from a conversation. A family-level assurance read across every SKU on the schedule is how one building ends up with a device that behaves unlike the sample.
Integrator lead: So I send a list of questions and get dated documents back, and the answers have to arrive with the quotation rather than after it.
| Question to put to the lock supplier | The answer that closes it | Why the estate cannot proceed without it |
|---|---|---|
| Does this model code expose a wired interface to a third-party controller at all | A yes or no in writing, naming the model code | It decides whether the door is Class A or something the estate has to specify |
| What credential format is emitted, including width and parity | A table | It decides whether the panel decodes it at all |
| Which events does the device raise on its own | A list | It decides what the record can contain when nothing else is listening |
| What is the buffer depth, what flushes it, what happens on power removal, and which clock stamps the events | A figure, a rule and a sentence for each | It decides what is lost in an outage, whether the approved fail state is achievable, and whether two clocks can be reconciled |
| Does any named ecosystem or radio standard apply to this model, and at which version | A written statement naming the standard and the version | It decides whether a credential issued elsewhere can be presented at a door at all |
CONFIRM-PER-SUPPLIER: Ask the supplier, in writing and against a specific model code, whether the lock exposes any wired interface to a third-party controller, what that interface carries, which credential format it emits, which events it raises on its own, how deep its event buffer is, what it does when power is removed, and which clock stamps its events. Ask for the answer to be dated and tied to the model code rather than to a product family.
Integrator lead: And the ecosystem names people throw around in these meetings?
Portfolio engineer: They are radio and provisioning terms, not reader-to-controller path terms. Where a credential is provisioned over a mesh network, or held on a phone, or presented over a short-range radio, the controller still receives a code whose format both ends must agree on, and what the controller is handed becomes part of that format agreement. Treat any answer about Matter, Thread, Zigbee, Z-Wave, Apple Home Key, HomeKit or UWB as a question to verify, and close it with a written confirmation against the dated product page for the specific SKU.
Integrator lead: Where does the API question belong?
Portfolio engineer: Name which boundary the requirement is about. A local API on the controller and a cloud API on the platform are different products with different failure modes, and a requirement that the estate shall be able to read its own door records is satisfied by one and not by the other. The Door Controller Interfaces for a Multifamily or Office Portfolio treatment covers the controller-side exposure in detail.
Changing the estate while it is still in use
Integrator lead: One last practical thing. We cannot decant the whole estate to migrate it.
Portfolio engineer: Nobody expects that. A portfolio migration is a sequence of buildings, and the estate standard has to be written for the middle of that sequence, when two conventions are live at the same time and the people servicing it work across both. Which means one thing above all: no door may be without a class on its record. The failure that costs the estate money is not a door running on the old convention, it is a door nobody can classify. A physical label at the controller cabinet, carrying the building, the panel, the channel or address and the class, costs a label and saves an afternoon.
| Phase | What is true in the estate | The risk to manage | The artefact that closes it |
|---|---|---|---|
| Before anything changes | One class per building | The schedule hides the classes | The re-cut schedule with the class column |
| During the mixed window | Two conventions live at once | A door with no class on its record | The labelled cabinet index, checked against the schedule |
| After a building is refreshed | The new class is the only class on that building | The old controller still answers for doors it no longer serves | A decommissioning record for the retired equipment |
Margin note — integrator action: Print the path class on the door schedule and on a label at each controller cabinet, and treat the two as one artefact. A class that exists only in a spreadsheet is lost the first time the spreadsheet and the cupboard disagree.
What the estate receives at handover, and where the schedule
Integrator lead: Give me the list I hand over, per estate, and tell me which of those items would have saved me a bad week.
Portfolio engineer: The class schedule, the ledger per class with held and not-held rows, the clock table, the degraded-mode table, the exception register, the escalation page, the written confirmations from each supplier, and the decommissioning log. Of those, the ledger and the exception register are the two that get used: everything else is read once, and those two are read every time a door misbehaves.
| Handover item | What it settles | Who signs |
|---|---|---|
| Portfolio path schedule, one row per door population, with the class | Which rule governs which door | The integrator and the owner's engineer |
| Assumption ledger per class, each row held or not held | What the estate may rely on and what it carries | The owner's engineer |
| Clock ownership and tolerance table | Whether two records can be reconciled | The portfolio engineer and the owner's IT |
| Degraded-mode table per class | What happens at each point of failure | The owner's responsible person |
| Exception register with approvers | Which doors sit outside the rules and why | The owner |
| Written supplier confirmations per model code | What each device does and does not do | The integrator and the supplier |
| Escalation page by class, and the address book reconciled to the schedule | Who answers first, and which device serves which door | The owner's responsible person and the commissioning engineer |
Integrator lead: And the published material that supports the physical side of it?
Portfolio engineer: The site surveys for the two populations that dominate this estate are Office Smart Lock Site Survey and Apartment Smart Lock Site Survey, and where the doors are old rather than new, Smart Lock Retrofit Site Survey is the one that asks the right questions. The class schedule then travels with the quotation and the written confirmations come back with it.
Integrator lead: I can take this to the owner as a plan.
Portfolio engineer: Take it as a plan, not as a protocol decision, because that is what it is. The protocol question is answered per class, in writing, with dated documents behind it; the estate question is whether every door in the portfolio has a class, an owner, a clock and a degraded mode against its name. When you send the schedule, send the class column with it, because a schedule without classes comes back with the cell blank and the blank is the whole problem. The Wiegand vs OSDP Requirements Document Template is the specification form these answers belong in, and Documenting Wiegand vs OSDP for Handover and Audit is the handover discipline that goes with them.
Send the door schedule and the class column through the request a quote route with the model codes and the interface questions attached, and the answers come back as dated documents against those codes rather than as a family-level assurance. The Smart Lock Manufacturer for System Integrators page is where that exchange starts, and order samples puts the sample in the integrator's hands rather than on a courier's, so that the bench checks happen against the article that will actually be installed.

