Require a gateway placement and coverage test plan that proves each lock path, defines outage behavior, and assigns evidence before installation is accepted.

ประกาศเมื่อ: มี.ค. 07, 2024

Gateway Placement and Coverage: The Test Plan a Buyer Should Demand

Gateway Placement and Coverage: The Test Plan a Buyer Should Demand

Use this sheet as a contractual attachment to any smart-lock gateway proposal. It converts a placement assertion into a repeatable acceptance test. A buyer should receive the gateway placement and coverage test plan with the bid, not after equipment has been ordered or installed.

Direct answer. To put it plainly: gateway placement and coverage test plan has to hold for gateway placement and coverage test plan. gateway-placement-and-coverage has to hold at the same time. The sections below describe the order gateway placement and coverage test plan is settled in. A gateway placement and coverage test plan treats the handover as the unit of work. gateway placement and coverage test plan decides the interface. gateway placement and coverage test plan is operable on day one only if it does.

gateway placement and coverage test plan is used here in the sense given under gateway placement and coverage test plan. It is a working definition of gateway placement and coverage test plan that carries no regulatory weight. The buyer still has to check it against the dated product page.

  • Draw the interface — write down what hands over between lock, door and system at gateway placement and coverage test plan
  • Exercise the handover — record the sequence that proves gateway-placement-and-coverage works end to end
  • Archive the record — store the commissioning evidence with the file for gp- issue instruction
  • For gateway placement and coverage test plan, gateway placement and coverage is what each step has to answer to.

The sheet defines the evidence required from the survey, the tests that must use the final installation configuration, the outage cases that must be demonstrated, and the person who owns each correction. It is intended for the system integrator coordinating access control, networking, installation, and the client’s operating teams.

A floor plan, signal-prediction graphic, or model datasheet can support planning, but none substitutes for a documented test against the buyer’s designated doors and operating conditions. The Office Smart Lock Site Survey can support door and area preparation; this document defines what the buyer should demand before treating that survey as accepted.

GP-01 — Issue instruction and mandatory bid return

Add the following instruction to the request for proposal: “Each bidder shall return a completed gateway placement and coverage test plan with its technical response. Unanswered fields must carry a written explanation and an owner. A proposed threshold remains proposed until the buyer approves it.”

Return itemRequired bidder contentAcceptance evidence
Compliance matrixResponse to every clause, including exceptionsSigned or attributed revision
Placement proposalGateway position, enclosure, power, network path, and service accessMarked drawing and photographs
Survey methodInstruments, test points, setup, calibration controls, and recorded conditionsMethod statement and sample record
Coverage test planDoor-level method, pass threshold, retest rule, and test sequenceCompleted test schedule
Outage matrixExpected behavior and evidence for each degraded modeFault-injection record
Responsibility matrixNamed role and contact for every failure domainContract schedule
Handover packageAs-built records, configuration evidence, exceptions, and maintenance inputsIndexed electronic package

The bidder must distinguish a committed design from a proposed option. “To be confirmed after survey” is acceptable only where the affected door, dependency, owner, and release date are recorded. A blanket exception covering unknown site conditions should be treated as an incomplete bid unless the buyer has accepted it in writing. The commercial end of this decision is the smart door locks.

The bidder shall also identify which evidence will be produced before installation, which will be produced at commissioning, and which will remain open after handover. This prevents a coverage problem from being carried into operation without a documented hold point or concession.

GP-02 — Scope boundary for the signal path

The gateway is one component in a larger path. It does not decide whether a person may enter, and coverage at the gateway does not prove that the controller, lock, credential, and server have completed the intended transaction. The bidder must document both directions of the path and the behavior when a message does not arrive.

LayerContract questionRequired evidenceAccountable role
Gateway and networkWhat path carries the relevant radio or network traffic?Final placement, configuration, and path recordSupplier or integrator named in bid
ControllerWhere is door state held, and which decision is made locally?Controller configuration extractAccess-control integrator
Lock and credentialWhich event is produced, and how does the installed combination respond?Controlled point testSupplier and access-control team
Service platformWhich event reaches the platform, and what happens if it cannot?Timestamped transaction or written interface rulePlatform owner
Building servicesWhich other systems share the relevant space or network route?Coordination recordClient or prime integrator

Centralised and standalone are architectural choices, not interchangeable labels for local and cloud operation. The response must state where the lock state resides, which functions remain available without the server, and which failures cause a local denial. The lock reports the state; the system decides what the state means.

Local API and cloud API requirements must be separated. A buyer asking whether an event reaches the platform has a different acceptance question from one asking whether an access decision can be made at the door. For a retrofit, begin with the constraints identified in the Smart Lock Retrofit Site Survey, then trace each requirement through the complete path.

GP-03 — Design inputs required before testing

No coverage result is meaningful until the buyer and bidder use the same door list, operating conditions, and acceptance basis. The following inputs should be frozen or marked provisional before the survey:

InputMinimum contentStatus treatment
Door scheduleDoor identifier, area, access role, priority, and operating stateFreeze before baseline test
Survey drawingsCurrent plans, reflected layouts, and identified construction zonesRecord revision and source
Proposed equipmentGateway, controller, lock, credential, and candidate product referencesLabel each item proposed or approved
Physical environmentWall, partition, door, enclosure, and nearby equipment observationsInclude photographs
Power and network routeIntended supply source, route, interface, and service accessMark unverified items
Existing radio environmentNearby devices and systems relevant to the test areaRecord observed conditions
Coverage thresholdThe buyer-defined condition that every designated door must meetNo implied default
Degraded behaviorRequired local, controlled, and failed states for each door roleRequire approval before test
Test authorityWho witnesses, records, receives, and closes exceptionsName roles and contacts

If a bidder identifies a specific SKU, radio characteristics, port behavior, power requirements, and environmental limits must be confirmed on the dated product page for the specific SKU. A family-level value cannot be transferred to another model. Where an input remains unknown, the test plan must show which conclusion is blocked and who must supply the missing evidence.

GP-04 — Smart lock gateway site survey deliverable

The smart lock gateway site survey is a measured record, not a drawing exercise. It must connect each test point to a door identifier and each proposed gateway to a serviceable physical location. A predicted heat map without the instrument, setup, and point records does not demonstrate acceptance readiness.

The bidder shall return a survey package containing the survey date and responsible personnel; instrument identification and calibration status; all test-point coordinates or marked locations; measured observations; photographs; obstruction notes; candidate gateway positions; and a list of unresolved design changes. The bidder must also identify which observations came from a temporary setup and which came from production-equivalent equipment.

flowchart TD
  A[Door schedule] --> B[Site survey]
  B --> C[Candidate positions]
  C --> D[Configure test unit]
  D --> E[Run coverage and outage tests]
  E --> F{Result accepted}
  F -->|Yes| G[Issue evidence record]
  F -->|No| H[Adjust and retest]
  H --> D
  G --> I[Release installation hold point]
Survey record fieldWhat it prevents
Test-point and door-ID cross-referenceA passing result with no assigned door
Equipment and configuration revisionA test performed with a different setup
Physical-condition notesA later unexplained coverage change
Photograph indexDisputes about obstructions or access
Exception and owner listAn unidentified outstanding action

A survey may recommend a placement, but it cannot waive the final acceptance test. Where relocation would affect power, cabling, enclosure, maintenance access, or a door’s physical operation, the bidder must identify the affected trade and obtain the required approval before installation.

GP-05 — Placement arrangements the bidder must compare

The gateway placement and coverage test plan must compare the physical arrangements available to the project rather than presenting one location without context. The comparison below is a decision aid, not a performance ranking. The bidder completes it using the survey evidence.

ArrangementIntended project conditionEvidence requiredHold or reject conditionDecision owner
Distributed local unitSeparate coverage zones with independent access needsDoor-level tests and a location for each unitCoverage fails or the service path is unresolvedAccess-control integrator
Shared enclosureEquipment grouped in an accessible technical areaEnclosure survey and end-to-end testsRequired doors cannot meet the approved thresholdClient and integrator
Central shared unitCommon path for a defined areaWhole-area test matrix and interference testAny protected door lacks an approved resultBuyer’s project authority
Hybrid arrangementDifferent areas have materially different constraintsSeparate evidence for each zoneZone boundaries or responsibilities remain ambiguousNamed design authority

A candidate location must have confirmed power, a confirmed network route, safe service access, and no unapproved structural or building-services work. These are entry conditions, not substitutes for radio and connectivity testing. A location also becomes a hold point if the physical arrangement obstructs required access, alters the approved door behavior, or leaves the equipment owner unidentified.

The buyer records the selected arrangement, rejected alternatives, reasons, and residual exceptions. A later change to the arrangement triggers the change-control process in GP-08; it does not rely on memory of the original survey.

GP-06 — Wireless coverage acceptance test

The wireless coverage acceptance test must use the proposed production gateway in its intended physical position and with the configuration intended for operation. Predictive results remain planning inputs. Acceptance comes from recorded observations at designated door locations under the buyer’s approved operating conditions.

Test IDMethodPass criterionEvidence
W-01Establish a site baseline at every designated test pointResult meets the buyer-approved thresholdDoor-level measurement record
W-02Operate the selected gateway from its proposed positionEvery linked designated door meets the thresholdFinal placement record
W-03Repeat tests in the listed door and traffic statesResults remain within the approved acceptance conditionTest-state matrix
W-04Run the planned nearby-equipment conditionNo designated door becomes an approved exceptionCoordination and result record
W-05Repeat a defined subset to check repeatabilityRepeated results meet the agreed conditionRepeat-test log
W-06Test after any approved physical or configuration changeAffected points remain within the acceptance conditionChange and retest record

The buyer must state the acceptance threshold before comparing bids. If the bidder proposes a threshold, label it as proposed and identify the measurement method with which it is comparable. Do not allow a bidder to redefine the threshold after a failed test.

Each result record must contain the door identifier, test-point identifier, gateway identifier, physical location, configuration revision, operating condition, measured result, acceptance criterion, tester, timestamp, and disposition. An exception must state the affected door, likely cause, temporary arrangement, accountable owner, retest condition, and buyer disposition.

GP-07 — Lock connectivity test

A lock connectivity test proves more than a radio observation. It demonstrates that the final gateway, controller, lock, credential, and service path behave as the approved design expects. The bidder must identify whether a failed step belongs to association, policy exchange, event delivery, door response, or platform reporting.

Test IDControlled actionPass criterionRequired record
L-01Establish the intended lock and gateway path using final configurationThe path forms and retains the approved identityConfiguration and connection evidence
L-02Present a valid test credentialThe response matches the approved access policyTimestamped transaction
L-03Present a credential outside the test policyThe response matches the approved rejection behaviorTimestamped transaction
L-04Observe the controller-side and platform-side recordsBoth represent the same test event correctlyReconciled event record
L-05Operate the controlled door under the approved test methodDoor response matches the specified behaviorDoor and controller record
L-06Restore service after the approved interruption sequenceRecovery and event state match the designRestart and recovery log

The credential is the item a person holds or presents; identity is the person or role behind it. Test records should identify both so a successful device test is not mistaken for proof of the correct person-to-door entitlement. Use dedicated test identities and remove them under the approved decommissioning process.

A product reference included in the test record must remain tied to the exact approved SKU. Radio reach, pairing behavior, and operating limits must be confirmed on the dated product page for the specific SKU rather than inferred from the gateway alone.

GP-08 — Interference, physical changes, and retesting

Coverage is an observed condition at a particular time. The buyer therefore needs defined triggers that reopen the test. The bidder should include any additional trigger required by the physical environment or installation sequence.

Change or conditionRequired responseAffected evidence
Partition, wall, door, or finish changeReview the location and retest affected pointsSurvey and W-series records
Gateway, lock, controller, or credential changeVerify configuration compatibility and rerun linked testsConfiguration baseline and L-series records
Nearby radio equipment added or relocatedRecreate the approved coexistence conditionW-04 record
Power or network route changedRevalidate service availability and outage behaviorCommissioning and outage records
Gateway relocatedRepeat coverage and connectivity testsNew placement package
Door or furniture arrangement materially changedConfirm the operating condition still represents the approved useSurvey update and affected test points

The bidder must not close an open test point by substituting a nearby passing door. Coverage evidence transfers to another point only when the buyer approves the transfer and the physical and configuration conditions are demonstrably equivalent.

GP-09 — Outage and degraded-mode acceptance

For each door role, specify the approved fail-safe or fail-secure state and identify who approved it. That decision belongs to the door design and approval process, not to a generic product claim. The offline case is the design, not the exception.

ScenarioControlled methodPass criterionEvidence and owner
Upstream network unavailableInterrupt the defined upstream path under the approved methodLocal behavior and event handling match the door-specific designConfiguration, event record, and integration owner
Controller unavailableApply the approved controller-loss conditionDoor response and credential handling match the stated degraded modeFault log and access-control owner
Service platform unavailableSeparate platform loss from local network lossLocal operations continue or fail exactly as the design statesLocal transaction and platform-recovery record
Gateway restart or power interruptionRestore service through the approved sequenceRecovery, retained events, and door mapping match the designRestart log and supplier owner
Radio path degradedReproduce the buyer-approved degraded conditionEach designated door has the approved resultDoor-level test record
Partial communication failureInterfere with one path component at a timeThe system identifies the lost path and follows the fallback ruleInterface trace and named owner

Do not accept “works offline” as a pass statement. The response must name the door, the component that failed, the local function that remained available, the event that was not delivered, and the recovery action. If a transaction moves from the server-side audit log to local event memory, preserve the distinction and demonstrate how the record is reconciled later.

The bidder and buyer should agree which tests are safe for the installed door and how they will be performed. The test method must not depend on an improvised release or bypass. Any exception receives a written buyer concession, an owner, and a retest condition before the installation hold point is released.

GP-10 — Clock, event, and record ownership

One authoritative clock must be identified for each event class. The bid response must state how controller, lock, gateway, and platform timestamps are aligned, what happens during clock loss, and which timestamp is used when reconciliation is required. Two unexplained clocks cannot support a reliable incident chronology.

RecordAuthoritative ownerAccess and retention requirementExport or reconciliation evidence
Door-access eventNamed access-control ownerDefine readers, purpose, and storage locationSample export tied to a test identity
Local event memoryNamed lock or controller ownerDefine buffer boundary and recovery procedureBefore-and-after recovery test
Audit logNamed platform ownerDefine access permissions and auditabilityPermission test and sample record
Coverage resultNamed integrator or supplierPreserve test conditions and configuration revisionSigned door-level result set
Configuration baselineNamed configuration ownerPreserve approved and observed versionsChange log and file hash or equivalent control
Gateway commissioning recordNamed commissioning ownerRetain with the access-control handoverIndexed handover package

Audit log and event memory must not be treated as the same record. The audit log is an event record with a time and source; event memory is the buffer used when the lock cannot reach the server. The buyer must know which events exist in each place, how they are reconciled, and whether an outage leaves a visible gap.

CONFIRM-WITH-LOCAL-PRIVACY-ADVISOR: Confirm the records, purposes, access rights, retention periods, export recipients, and authority approvals allowed for the jurisdiction in which the system operates before commissioning.

This line remains with the completed record schedule. It identifies the approval needed; it does not substitute for the client’s local decision or the integrator’s documented configuration.

GP-11 — Gateway commissioning checklist

Use the gateway commissioning checklist to close physical, logical, and evidentiary gaps before the equipment enters normal service. The checklist is completed against the same identifiers used in the coverage and connectivity tests.

CheckRequired confirmationSign-off evidence
Identity and mappingGateway, controller, door, and physical location are correctly associatedConfiguration extract and label photograph
Power and networkIntended supply and path are confirmed without an unresolved holdInstaller record
Configuration baselineHardware, software, and relevant settings are recordedApproved configuration snapshot
Door credentialsTest identities work only where intendedTransaction and reconciliation record
ClockApproved time source and recovery behavior are recordedClock comparison and recovery log
Coverage and connectivityAll required tests and dispositions are attachedSigned test package
Outage behaviorEvery required degraded-mode case has a resultOutage matrix
Labels and service recordsEquipment is identifiable and maintainableAsset register and location schedule
Decommissioning planRemoval, credential cancellation, and record disposal have ownersApproved offboarding procedure

The Gateway Placement and Coverage Requirements Document Template can carry these requirements into the project’s formal document set. Its fields should point to the actual test records; an empty or future-tense field is not completed evidence.

Provisioning brings a device into service with its identity, door, and owner. Decommissioning is a separate recorded operation and must not be represented by an unchecked box on the commissioning sheet.

GP-12 — Property-specific application notes

A hotel deployment may organize the schedule by property area and room type, but the gateway test still identifies an exact door or approved location. The Gateway Placement and Coverage for a Hotel Property provides the property-specific decision context; it does not replace the door-level evidence in this sheet.

A multifamily or office portfolio may reuse a test template, but it cannot reuse a result. The Gateway Placement and Coverage for a Multifamily or Office Portfolio addresses portfolio-scale application. Each building, common area, and distinct physical arrangement still needs its own baseline and accepted exceptions.

For either case, record which parts of the evidence package may be standardized and which must be regenerated at the site. Reusing a drawing, configuration, or test point without confirming the site conditions is an open assumption, not an efficiency measure.

GP-13 — Access control integration handover package

The access control integration handover is the transfer of an operating and evidentiary package. The Documenting Gateway Placement and Coverage for Handover and Audit should be used to align the package with the client’s audit and maintenance requirements.

Package itemRequired contentReceiving owner
As-built placementFinal gateway locations, enclosures, routes, and photographsFacilities and access-control owner
Door-to-gateway mapPermanent identifiers and controlled test-point referencesCommissioning owner
Configuration baselineApproved hardware, software, settings, and change recordConfiguration owner
Test evidenceCoverage, connectivity, clock, and outage resultsAcceptance authority
Exception registerCause, owner, concession, retest condition, and closure evidenceProject manager
Event ownershipClock, event sources, readers, retention, and recovery procedurePlatform and privacy owners
Maintenance procedureInspection access, known weak points, change triggers, and contact routeService provider
Decommissioning procedureEquipment removal, credential cancellation, and record handlingClient operations owner

A handover list containing equipment locations is insufficient. The receiving team must be able to trace each accepted door result to the installed configuration, reproduce the test conditions, identify unresolved exceptions, and determine who acts when the condition changes.

GP-14 — Failure ownership and acceptance decisions

A boundary that is not drawn becomes a dispute after installation. Each bidder must insert the actual company, contact, and escalation route for every failure domain in the contract schedule. Generic labels such as “vendor” or “integrator” do not satisfy this clause.

Failure domainRequired ownership entryClosure evidence
Coverage shortfall or changed radio conditionEquipment supplier and survey ownerCorrected placement and passing retest
Lock or credential path failureApproved product and integration ownersTransaction, configuration, and recovery evidence
Controller or interface failureAccess-control integratorController log and agreed correction
Network path failureNetwork service ownerPath record and outage retest
Server or platform failurePlatform ownerRecovery and event-reconciliation evidence
Configuration driftNamed configuration ownerApproved baseline and change record
Test dispositionMeaningBuyer action
AcceptedEvery mandatory criterion has passing evidence and no unapproved exceptionRelease the associated hold point
Conditionally acceptedA bounded exception has a documented concession, owner, and retest conditionRecord the limitation and responsible party
FailedA mandatory criterion lacks acceptable evidence or the result conflicts with the approved designCorrect and retest before acceptance

Every closure record must identify the failed test, the revised condition, the retest result, and the person authorized to accept it. A supplier claim that another party owns the cause is not closure. The named accountable role remains responsible for coordinating the evidence until the buyer accepts the outcome.

It is worth pairing this with how to choose between smart lock technologies. That is the same question gateway placement and coverage test plan has to answer here.

GP-15 — Acceptance certificate and issue instruction

The final acceptance certificate should reference the immutable test package rather than summarize results from memory.

Acceptance fieldBuyer confirmation
ScopeApproved door schedule and coverage areas
PlacementFinal locations and associated test-point identifiers
Coverage and connectivityAccepted test records and exception dispositions
Degraded modeApproved outage behavior and recovery evidence
Records and clockEvent ownership, synchronization method, and recovery procedure
ResponsibilityNamed owners and escalation routes
HandoverIndexed package received and access confirmed
Open itemsWritten concessions, deadlines, and retest conditions

Attach this sheet to the request for proposal, issue it with the survey brief, and require the completed version with the technical bid. A comparison becomes meaningful only when bidders are proving the same door paths against the same acceptance basis. Close unresolved inputs before bid close; after award, convert every accepted location into an installation and commissioning obligation with named evidence.

A quote request turns the written requirement into something a supplier can price: request a quote.

ตะกร้าสินค้าของคุณ
การใช้คุกกี้จะช่วยปรับปรุงประสบการณ์การใช้งานเว็บไซต์นี้ของคุณให้ดียิ่งขึ้น นโยบายคุกกี้
Chat on WhatsApp