Wiegand vs OSDP Cost and Effort Drivers Without Quoting Prices
Wiegand versus osdp effort drivers is what this piece addresses for the system that has to work on a real door. A reader-to-controller decision gets argued as a technical question and priced as a hardware question. Someone asks which path carries the credential better, the supplier answers with a datasheet, and the quotation that arrives carries a part number, a quantity and a figure per door. Nowhere in that exchange does anyone say what the choice will do to the working life of the people who install, commission, support and audit the system afterwards.
- Chart the interface — write down what hands over between lock, door and system at wiegand versus osdp effort drivers
- Trial the handover — record the sequence that proves wiegand-vs-osdp works end to end
- Retain the trace — store the commissioning evidence with the file for two contenders
- In wiegand versus osdp effort drivers, this sequence is what wiegand vs osdp is checked against.
That is the gap this comparison closes. Wiegand versus OSDP effort drivers are not the price of the reader and not the price of the panel; they are the labour, the site visits, the documents, the escalations and the second guesses each option creates across the life of the system. One option concentrates effort on the installation day, the other on the month the first ticket arrives. A comparison that quotes only the hardware has compared the cheapest part of the bill.
The two paths are a legacy wiring convention and a specified, addressed, bidirectional protocol. That difference in kind is why effort lands differently: a convention that carries a data line and says nothing about identity or encryption creates a system whose failures are silent by construction, while an addressed protocol carries device identity, message structure and acknowledgements, and creates a system whose configuration has to be built, described and proven. Which statements hold for a given product is confirmed on the dated product page for the specific SKU.
Direct answer. Effort in a reader path is counted in five arenas: the per-door work at commissioning, the calendar of fault-finding afterwards, the evidence the client will eventually ask for, the number of parties who must be reconciled to keep the thing alive, and the years of operation that follow handover. The Wiegand convention keeps the door simple and makes the diagnosis expensive; the addressed protocol makes the diagnosis cheap and the documentation heavy. Which one costs less depends less on the protocol than on how many doors hang off one controller and how many vendors sit in the stack. What follows is an effort schedule you can put into a quotation, and the questions that must be answered in writing before any of it becomes a number.
The scope is narrow on purpose. This is not a test plan, not a procurement guide and not a security assessment. The proofs that a path works belong in Wiegand vs OSDP: The Test Plan a Buyer Should Demand; the contractual question of who owns the outcome when a door misbehaves belongs in Who Owns Wiegand vs OSDP: Supplier, Integrator or Client; the record set the client expects at handover belongs in Documenting Wiegand vs OSDP for Handover and Audit. What follows is the work each path asks for, in the units an integrator already budgets in, with no prices attached.
The two contenders in plain terms
Wiegand is a wiring convention between a reader and a controller. It carries a data line and usually a power line and a ground, and the credential leaves the reader as a burst of clocked pulses on that data line. What the controller does with those pulses is not fixed by the convention: each panel vendor decides which code widths it will decode and how it reads the parity. The convention says nothing about encryption, and it says nothing about device identity. A reader on this path cannot introduce itself, and the controller cannot ask it a question and get an answer.
OSDP is a protocol specification, addressed and bidirectional, ordinarily carried over a half-duplex pair. Devices on the bus hold addresses, the controller addresses a device, the device answers, and the exchange carries sequence and integrity information so that a damaged or duplicated frame is visible rather than silent. It also defines the reverse direction: the controller can drive the reader's indicator, and a device can raise an event. Which of those capabilities a given product implements, at which revision, and with which optional features enabled, is a per-SKU question to confirm on the dated product page for the specific SKU and against the other party's dated datasheet. The catalogue side of this is the smart door locks.
| Property of the path | Legacy wiring convention | Addressed bidirectional protocol |
|---|---|---|
| Identifies the device | The input channel it is wired to | An address held on the bus |
| Controller can ask it | Nothing | Status, indicator control, event reports, per implementation |
| A damaged message | May still decode as a valid code | Sequence and integrity fields make it visible |
| Format agreed | Between two vendors, informally | In a specification, per implementation and pairing |
| A swapped reader | Keeps the channel's identity | Carries its own address, which may not match the door |
| Panel needs per reader | An input, sometimes a reader module | A bus port, a termination plan, an address in the map |
None of these rows argues one path over the other. Each argues about where a person will have to spend a day.
Where the work lands: a driver map
The effort does not arrive as a single item. It arrives as recurring mechanisms, each of which produces work, and each of which behaves differently on the two paths.
mindmap
root((Reader path effort))
Commissioning
Door level setup
Bus addressing
Format agreement
Fault finding
On site triage
Remote diagnosis
Second visits
Evidence
Assumption ledger
Degraded mode
Clock ownership
Coordination
Conformance chase
Datasheet reconcile
Licence admin
Credentials
Desk encoding
Mobile delivery
Visitor issuing
Mixed estate
Dual path operation
Spares and skill
Eventual replacement
Unquoted
Helpdesk time
Data questions
Egress approvals
Six branches are structural and one is organisational, and the split matters for a quotation. The structural branches land on the integrator's own time and are visible in a project plan if somebody is asked to name them. The organisational branch lands on the client's facilities and IT teams, appears in nobody's budget, and is the source of the cost that most often surprises a project sponsor two years in.
| Effort driver | What it produces | Which path carries more of it |
|---|---|---|
| Per-door commissioning | Setup time per door and panel | Addressed path on the per-door tail, legacy path on one-off cable work |
| Fault diagnosis | Time to isolate a failing door | Legacy path on site visits, addressed path on diagnostic complexity |
| Evidence production | Documents per door and pairing | Legacy path, on statements written from outside the protocol |
| Vendor reconciliation | Written confirmations per pairing | Addressed path, on the number of dated documents to reconcile |
| Credential origin | Upstream work to get a code to the door | Addressed path on format agreement, legacy path on upstream tolerance |
| Mixed estate | Running two paths at once | Whichever path the existing doors already carry |
| Unquoted effort | Client-side time and approvals | Neither, which is why it gets budgeted separately or not at all |
The last row is the one buyers forget to ask about. The engineering hours of the two paths can be nearly identical in a small building, and the difference between them still shows up in the client's helpdesk, its audit requests and its fire-safety sign-off.
Driver one: commissioning hours per door
Commissioning is where the comparison is usually settled, and usually settled badly, because both options are described as a wiring task and only one of them still is.
On the legacy path, commissioning a door means terminating the data, power and ground at the reader, running the cable to the panel, landing it on an input, configuring the panel to read the format the reader emits, adding the credential to the database, and binding that input to a door in the software. Each step is a known operation for anyone who has fitted access control before. The subtlety is concentrated in one place: the format agreement. If the widths or the parity do not match, the door can open for the wrong credential while the log shows an ordinary grant, which is why the format has to be proven at the desk before it reaches the door.
On the addressed path, commissioning adds a layer the legacy path does not have. The device has to be given an address, the address bound to a door, the bus planned so that topology and termination match what the implementation supports, and the reader's indicator behaviour checked so that a granted credential and a denied one look different to the person at the door. On a bus with many readers the address map becomes a document in its own right, with a version, because the day somebody adds a reader the map is the only thing that tells them which address is free.
| Commissioning activity | Legacy wiring convention | Addressed bidirectional protocol |
|---|---|---|
| Physical termination | Per reader, per door | Per run, when readers share a bus |
| Panel configuration | An input and a format per door | A port, a bus parameter, an address per device |
| Identity record | Held in the wiring | Held in an address map and the device table |
| First successful read | Confirms the format | Confirms format, address and the indicator channel |
| Failure signature | A denial, or a grant that should not have happened | A denial, a device-status fault, or no answer at all |
| Effort shape | Scales with the number of doors | Scales with device count plus a smaller per-door tail |
Two observations follow. The per-door tail on the addressed path is heavier, because more can go wrong per device, while the one-off cost is lighter when many readers share a run; which effect dominates depends on door density on each panel, which is the first axis of the two-axis reading later in this article. The second is that commissioning effort is only visible if somebody writes down the count. A project that quotes a reader per door has quoted a part, not the work. The counting rule applies on the first site visit: commissioning hours per door, times the doors on the densest panel, times the panels, plus one bench session per vendor pairing to agree the format or the address convention before anyone opens a ceiling.
Driver two: the fault-finding calendar
This is where the two paths part company most clearly, because a fault calendar is a recurring cost with no end date, and it lands on whoever holds the maintenance contract rather than on whoever sold the hardware.
A legacy path tells the controller very little. The controller sees a credential code or nothing, and a tamper line if the reader has one and the panel was told about it. When a door stops working, the technician's starting position is physical: is the cable intact, is the reader powered, is it still passing a code, is the panel reading the format it expects. Each check is a site visit, and several are sequential, because the information needed to choose the next check does not exist until the previous one has been made in person. The method scales badly with door count, because each door needs its own visit and none can be short-circuited.
An addressed path produces more information about the device behind the door: a device that has lost the bus, a device answering with errors, a device whose indicator channel is being driven and not received. These are states the controller can hold, report or alarm on, subject to what the specific implementation reports. That does not remove site visits; it converts some into decisions made from a console, which turns the trip from exploratory into targeted.
| Fault class | Legacy path: what the technician can see | Addressed path: what the technician can see |
|---|---|---|
| Reader not responding | Absence of a code, identical to a failed reader | A device absent from the bus, where the implementation reports it |
| Damaged cable | Nothing, until the cable is physically tested | Often a device that has stopped answering, still ambiguous |
| Wrong format configured | A denial, or worse, an incorrect grant | A denial, plus a configured-format reference to check |
| Reader swapped by a contractor | The channel keeps working; nothing is detected | The device answers with an address that no longer matches |
| Reader alive, credential refused | Hard to tell apart from a reader fault | Device status may be healthy, narrowing it to the credential |
| Controller or server unreachable | The door's local behaviour, which must be designed in | The same, plus whatever the bus reports about the path |
The table is not a scoring sheet. It says that the diagnostic information available to a first-line technician is not the same on the two paths, and that first-line information decides whether a fault is closed on a console or carried to a door. That difference compounds quietly: invisible in the quotation, visible in the maintenance log.
Two things belong here because they are frequently confused with the path choice. The first is the door hardware: an electric strike that behaves differently under power loss will generate tickets that look like reader faults and get diagnosed as reader faults, because the reader is where the site visit starts. The second is the network: a controller whose management link drops presents differently from a reader whose bus dropped, but the ticket text tends to name the door rather than the layer. In both cases the effort driver is diagnostic discipline, and the path choice is only one way to reduce it.
Driver three: the evidence each path demands
Every reader path eventually has to be described to somebody who was not there: a client's auditor, an insurer, an authority, or the technician who takes over the account in year three. The work this creates is one of the largest recurring items in the comparison, and it behaves in opposite directions on the two paths.
The legacy convention asks the integrator to supply from outside the protocol the things the protocol does not carry. The list is long and unglamorous: which credential formats are accepted at which doors, what a denial means and does not mean, what happens to the door when the line is cut, who owns the clock for an event, where the audit log lives as distinct from the buffer the device keeps when it cannot reach the server, and which assumptions nobody can support and are simply not held. Each item that cannot be evidenced from the path becomes either a written statement or a risk entry somebody has to accept and sign. Those entries are cheap to write and expensive to carry, because each one is a question that will be asked again at the next review.
The addressed protocol carries more structure, and that structure is the point. The specification defines a message structure, device addressing, acknowledgement and error visibility, so the record can be written as a description of a defined behaviour rather than an account of what happens to happen. The catch is that a specification is not a product. What the integrator has to obtain, per pairing, is a dated statement naming the revision implemented, the optional features enabled, the event list, the buffer behaviour and the timeout behaviour, and that statement has to be reconciled against the panel vendor's own document. The effort is in the reconciliation, because two companies are describing the same link and neither document is subordinate to the other.
CONFIRM-PER-SUPPLIER — any statement about protocol implementation, revision level, optional feature support, event list or buffer behaviour must be confirmed in writing for the exact model, and reconciled against the other party's dated datasheet before it is entered into a specification or a quotation.
| Evidence item | Legacy path | Addressed path |
|---|---|---|
| Format agreement | A note per panel family, often oral in practice | A written agreement per pairing and product revision |
| Device identity | Not available; the wiring is the identity | An address map, versioned, with a change process |
| Event list | Short, often only a grant and a denial | Longer, defined by the implementation, which must be obtained |
| Offline behaviour | Written from scratch per door role | Defined in the specification, still per implementation and role |
| Clock ownership | Declared and reconciled by the integrator | Still declared; the protocol does not own a clock |
| Buffer behaviour | Established with the panel and the device | Usually documented, at the level the implementation provides |
| Integrity in transit | Cannot be evidenced; a compensating control is needed | Can be evidenced where the implementation and licence support it |
| Handover pack | Built by the integrator from scratch | Assembled from dated vendor documents plus the address map |
CONFIRM-WITH-LOCAL-PRIVACY — who presented which credential at which door and at what time is personal data in most jurisdictions, and the retention period, the lawful basis and the roles permitted to read the record are set by the data controller under the local regime. Confirm the retention setting, the access list and the lawful basis with the local data-protection contact before the path is put into service, and write the answer into the evidence pack rather than into a configuration screen.
Driver four: parties, datasheets and the conformance chase
The biggest single effort driver in most reader-path projects is not technical. It is the number of people whose documents have to agree before a door works.
Consider the ordinary case: a lock supplier, a reader supplier who may be the same company, a panel vendor, a network team, and a client's IT or security policy group. On the legacy path the number of written statements that must be reconciled is small, because the convention settles most of the questions. What replaces it is not paperwork but assumptions: the integrator carries a set of beliefs about what the reader and the panel will do together, and those beliefs are usually untested until they cause a ticket.
On the addressed path, the convention settles fewer questions and the specification raises more, so the reconciliation workload moves upstream and becomes explicit. Each pairing needs a conformance statement from the reader side, a matching document from the panel side, and a written answer to the questions where the two differ. With several reader types, a mixed building, or two panel families, that is not one reconciliation but a matrix of them. The effort is real, it is front-loaded, and it comes out of engineering time rather than a hardware line.
| Coordination task | Legacy path | Addressed path |
|---|---|---|
| Conformance statement from the reader supplier | Narrow, often one page | Broader, naming revision, features and event list |
| Reconciliation with the panel document | Light, one format to check | Deeper, because the implementation set has to match |
| Format or address agreement | A short conversation, if it happens at all | A documented agreement, per pairing |
| Licence or administration questions | Usually none for the path itself | Sometimes present, and they need a named owner |
| Documents per door family | Small | Larger, and repeated per pairing rather than per door |
| Where the reconciliation sits | Informal, in the installer's head | On the record, in a dated file |
The counting rule for this driver is the one most often missing from a quotation: reconciliation sessions, times vendor pairs, times the number of document versions. The point is not that the addressed path is worse. The point is that the work exists, it lands early, and it is paid for out of engineering time rather than out of a hardware line.
One caution about how this driver is used commercially. A supplier who offers a written conformance statement naming the model, the revision and the feature set has done something genuinely useful, and a quotation that asks for it separates suppliers who can answer from suppliers who will not. A supplier offering a family-level assurance has done much less, and that assurance cannot safely be read across every model on a schedule. The difference shows up later, in the fault calendar rather than in the negotiation.
Driver five: credentials that arrive from somewhere else
The reader-to-controller path is rarely the only path in the building. Credentials usually originate elsewhere: a front desk that encodes cards, a property management system that allocates rooms, a visitor system issuing temporary passes, a phone-held credential a resident carries, a payroll-driven process granting and revoking entitlements. Each origin hands the controller a code, and each has an opinion about what that code should look like.
This driver is about how tolerant the reader path is of what upstream hands it. A legacy path with broadly supported formats tends to absorb upstream variation without effort, because the panel will decode a family of well-known code widths and the encoding desk was already producing one of them. An addressed path narrows the agreement, because the credential arriving at the controller is typically a formatted payload whose derivation must be agreed between the issuing side and the reader side, and because a reader supporting several credential types does not necessarily present all of them in a format the controller will accept.
| Upstream origin | What the path has to tolerate | Effort created |
|---|---|---|
| Front desk encoding | The encoder's output format must match what the door accepts | Testing at the desk, before any card is issued |
| Property management system | Allocation events must reach a reader in a format the controller understands | Mapping between two systems and one agreed format |
| Visitor issuing | Temporary credentials must expire on the reader, not only in the issuing system | Expiry behaviour demonstrated per path |
| Phone-held credential | Whether the controller is given a code at all, and in what format | A per-SKU question, answered on the dated product page |
| Contractor and staff entitlement | Revocation must reach the controller on both paths | Latency testing on the decision, not on the wire |
| Personalisation data | The credential carries per-person data and the reader only reports a code | A boundary decision, so personal data stays upstream of the path |
The personalisation row is a common design mistake worth naming. A reader on the path reports a credential code and the identity lookup happens at the controller; the personal data on the credential does not need to travel the path at all. The lock reports the state; the system decides what the state means. Deciding that boundary early keeps the reader path simple and keeps personal data inside the systems entitled to hold it.
Driver six: the retrofit that carries both paths
Most projects that matter are not greenfield. They are buildings where some doors were fitted years ago with a legacy reader and a panel input, and other doors are being replaced now. This is where the effort comparison stops being a choice and becomes a coexistence problem, and it is where a lot of confident single-path arithmetic goes wrong.
Running both paths at once has costs that appear only once the two are on the same wall. The panel may need to carry input-based readers and bus-based readers at once, which is a platform question and a licensing question rather than a wiring question, and the answer may not come from the same panel family the building already owns. Diagnostic procedures differ, so a technician carries two habits and applies them at random. Spares are two kinds of part rather than one. Training has two vocabularies: channel and format on one side, address and bus on the other.
| Retrofit condition | Legacy path contribution | Addressed path contribution |
|---|---|---|
| Existing doors left as they are | No new effort, they keep running | Cannot adopt an address without a physical change |
| New doors added to an old building | New input and new cable per door | New bus segment, an address block, a plan for the mix |
| Panel replaced to modernise | Every legacy door re-terminated or migrated | Migration may be a re-address rather than a re-termination |
| One panel family forced on both | Simple, because everything speaks one convention | Depends entirely on the panel's dual-path support |
| Spares and skill | One spares list, one habit | Two spares lists, two habits, two training days |
| End of life of the old path | A planned replacement programme | A planned replacement programme, with an address map to rebuild |
The line that matters most is the third. Replacing a panel can cost more effort on the legacy path than on the addressed path, because every reader has to be physically re-terminated and re-bound, whereas an addressed reader surviving the panel change is mostly an entry in a new address map. That is a genuine argument in favour of the addressed path in a retrofit, and it is invisible unless somebody asks the question during the survey.
CONFIRM-WITH-LOCAL-EGRESS — the state a door takes when power is removed is decided by the door's role and by the approval, not by the product. Confirm with the approving authority and the local fire-safety regime what each door must do on loss of power and on the escape side, and put the answer in the record before either path is chosen, because the answer changes the hardware and the work at the door.
Driver seven: the effort nobody quotes
The last driver belongs to the client rather than the integrator, and it is the one that most changes a project's true cost without appearing anywhere in a lock quotation.
Three streams of client-side effort follow from the path decision. The first is the helpdesk: a reader path that produces few signals generates a ticket stream, and each ticket is somebody's afternoon in the client's own organisation. The second is the data stream: questions about who came through which door and when, how long records are kept, who may read them and what happens to the record when a person leaves, get raised by a facilities manager or a compliance officer and land on the integrator whether or not they land in the invoice. The third is the approvals stream: fire-alarm interface sign-off, escape-side release verification and the accessibility question at each door. These are not lock decisions, but they are door decisions, and the record the integrator produces on the path determines how long each approval takes.
| Client-side stream | What it consumes | What the path changes |
|---|---|---|
| First-line ticket triage | Technician time per ticket | The number of tickets, and how far one can be diagnosed from a desk |
| Data-protection questions | Compliance and engineering time | Nothing directly, which is why it must be budgeted separately |
| Audit and export requests | Engineering time to reconstruct a period | The richness of the event record and clarity of the buffer description |
| Fire-alarm interface sign-off | Approval time per door | The evidence assembled for the approving authority |
| Escape-side release verification | Engineering time per door | Wiring and reporting changes, not product changes |
| Accessibility verification | Engineering time per door | The operable force and motion that have to be demonstrated |
| Supplier escalation | Time spent chasing a statement never written down | The confirmations still outstanding after handover |
The row that surprises people is the last one. A project can be delivered, handed over, and still carry a running cost of chasing statements that were never obtained, because the effort driver was identified as somebody's responsibility and nobody was named. Naming the owner of each outstanding confirmation is the cheapest form of cost control available to an integrator, and it costs nothing but attention.
CONFIRM-WITH-LOCAL-FIRE-INTERFACE — how a fire-alarm signal reaches the lock and how release is coordinated with the escape side is an interface between two systems, and the rule that release is never the lock's own decision belongs to the approving authority and the local fire-safety regime. Confirm which authority signs the interface off and in what evidence format it expects, because the effort of producing that evidence depends on the format.
Where the effort lands, and which path carries it
The comparison resolves into two variables that a survey can establish before any hardware is ordered, and everything else here hangs off them.
The first axis is door density: how many doors one controller carries. The second is party count: how many vendors and how many separate documents stand between the lock and the panel. Neither axis is about the protocol, and that is the point.
quadrantChart
title Where reader path effort concentrates
x-axis Sparse doors per controller --> Dense doors per controller
y-axis One party to reconcile --> Several parties to reconcile
quadrant-1 Cable and panel work dominates
quadrant-2 Conformance evidence dominates
quadrant-3 Diagnostics and support dominate
quadrant-4 Point to point simplicity dominates
"Small site, single vendor": [0.15, 0.15]
"Dense site, single vendor": [0.82, 0.18]
"Small site, multi vendor": [0.18, 0.82]
"Dense site, multi vendor": [0.86, 0.88]
In the sparse, single-party quadrant, the point-to-point simplicity of the legacy convention is hard to beat: few doors, one vendor, one document set, short per-door work, trivial reconciliation. The dense, single-party quadrant is where the addressed path earns its keep, because a shared run carries many doors without consuming an input and a cable each, and because one vendor means the conformance burden is paid once. The multi-party quadrants are where the addressed protocol's extra rigour shows up as evidence effort rather than installation effort, and where the diagnostic advantage of device-level status starts to pay back in truck rolls.
The practical use of this reading is to decide where to spend the specification effort, not to pick a protocol. A dense, single-party site should spend its time on the address map and the bus plan. A multi-party site should spend its time on the conformance file and the escalation boundary, whichever path is chosen. A sparse, single-party site should spend its time on the desk test of the credential format, because that is where its failures will come from.
| Project shape | Where the effort concentrates | Dominant effort, legacy path | Dominant effort, addressed path | Counting rule |
|---|---|---|---|---|
| Modest door count, one vendor | Per-door wiring and format agreement | Cable routing and panel input count | Device addressing and a bus plan | Hours per door times doors, plus one bench session |
| High door count, one vendor | Bus topology, addressing and commissioning | Input count, cable volume, panel capacity | Bus design, addressing, commissioning per device | Hours per panel plus hours per device, plus one address map |
| Several sites, different panels | Cross-document reconciliation | A format agreement repeated per panel family | A conformance statement repeated per pairing | Reconciliations times pairings times panel families |
| Legacy estate plus new doors | Coexistence, training and spares | Mixed diagnostics and two spares lists | Mixed diagnostics and a re-addressing plan | Years of coexistence plus the migration effort |
| Client runs its own support | Support and approval effort absorbed internally | Support effort, booked as an internal service line | Support effort reduced, evidence effort increased | Internal hours per month, tracked as a service line |
The last row is the one most quotations miss. Where the client maintains the system themselves, the two paths change the split between the integrator's scope and the client's internal scope rather than changing the total, and a quotation pricing only the integrator's hours will understate one path and overstate the other. The fix is to name the split in the schedule, not to argue about the total.
The shape of the site is knowable from the survey, which is the cheapest document in the whole programme and the one that most reliably prevents a wrong protocol decision. The published survey material is Smart Lock Retrofit Site Survey and Office Smart Lock Site Survey, and the effort schedule is only as good as the survey behind it, because every counting rule here needs a door count, a door density and a vendor list before it can be applied.
The effort schedule to put into a quotation
Everything above resolves into one artefact: a schedule of effort line items that can be attached to a request for quotation, each item naming what sets it and who carries it. The supplier quotes the capability answers and the hardware; the integrator supplies the effort structure; the two meet in the document the client signs. This is where the labour planning for a reader-to-controller path becomes a priced object, because every line below is a counting unit rather than a rate.
| Schedule line | What sets it | Effort unit | Where it is incurred | Usually carried by |
|---|---|---|---|---|
| Path design and door schedule | Surveyed door list and panel layout | Hours per panel | Pre-installation | Integrator |
| Format or address agreement | Reader and panel datasheets | Sessions per pairing | Pre-installation | Both vendors |
| Address map build and version control | Device count per bus | Hours per hundred devices | Pre-installation | Integrator |
| Per-door commissioning | Path type and door density | Hours per door | Installation | Integrator |
| Bench verification | Credential set and the real article | Sessions per door family | Pre-installation | Integrator and supplier |
| First-fix and second-visit rate | Commissioning quality and path type | Visits per month | Operation | Client or maintainer |
| Fault triage allowance | Diagnostic information available | Hours per incident class | Operation | Maintainer |
| Evidence pack and handover record | Implementation statements obtained | Documents per door and pairing | Handover | Integrator |
| Helpdesk and training | Number of paths in service | Sessions per path per year | Operation | Client |
| Data and audit request handling | Event record richness and retention rules | Hours per request | Operation | Client and integrator |
| Approvals and interface sign-off | Door roles and local regime | Days per door | Pre-installation | Client |
| Migration of the legacy path | Estate size and panel change | Doors per year | Programme | Client |
Two rules make the schedule usable. Every line names a counting unit, so that the client's own survey can fill it in without asking the supplier's opinion — that is what separates an effort schedule from a price list. And the lines the supplier cannot answer are still present, marked as outstanding, with a named owner and a date. An effort schedule in which everything is resolved on the day it is issued is a schedule nobody checked.
The commercial framing matters as much as the arithmetic. The published guidance on what belongs in a quotation is What Should Be Included in a Smart Lock Quotation?, and the request itself is covered in How to Request a Smart Lock Quotation. The addition this comparison makes is narrow and specific: a quotation for an access-control reader path that does not carry an effort schedule will be compared on unit price, and the two options judged on the cheapest number in the document while the real difference sits in the lines that were never asked for.
Taking the schedule into the next quotation
The practical output of this comparison is a page you can attach to a request for quotation: the seven drivers, the counting unit for each, and the outstanding confirmations that will set them. It takes an afternoon to assemble, and it changes the shape of the conversation, because the comparison stops being about a unit price and becomes about where the work is.
Start from the survey, not from the reader. Smart Lock Installation Requirements and the published commissioning material — Smart Lock Commissioning Checklist and Smart Lock Testing After Installation — are where the effort lines get their counting units, because every line in the schedule above is an operation somebody performs on a door. The record the client expects at the end of that work is described in Smart Lock Handover Checklist, and the annual review that follows is where the migration lines either prove themselves or become complaints.
On our side, the model list, the configuration and the documentation set go on the record at request a quote, where the reader-path questions can be answered in writing rather than in a meeting, and the first physical units can be sent out at order samples so that the format and addressing questions are answered against the real article. Bring the door schedule, the panel model and the vendor list, and the effort schedule can be filled in rather than argued over.

