Read range definition: define read range for B2B smart-lock buyers and turn field conditions, credential limits, and test evidence into a procurement checklist.

Közzétéve:: nov. 12, 2025

Smart Lock Glossary: Read Range Definition for B2B Buyers

Smart Lock Glossary: Read Range Definition for B2B Buyers

Smart-lock specifications often collapse several distances into one line. A read range definition gives procurement, installation and acceptance teams one controlled boundary for presenting a contactless credential. This runbook uses the phrase as a buyer-side working definition, not as a claim that it has one universal technical meaning across products or projects.

Direct answer. In brief, this article covers read range definition from read range definition to read-range. It states what to confirm about read range definition on the dated product page where a figure is involved. A read range definition is the general entry point for this category. read range definition anchors the vocabulary. read range definition has to survive later projects.

This article defines read range definition through read range definition. The definition of read range definition is deliberately narrow. It is non-statutory, and it applies to the market and product being discussed.

Runbook card What can be supplied for read range definition

  • Purpose: Convert an unqualified range statement into a testable and traceable requirement.
  • Owner: The importer or procurement engineer, with input from the installer and acceptance owner.
  • Trigger: A quotation, submittal, RFQ or installation record uses read range without supporting conditions.
  • Inputs: Exact reader and SKU, credential reference, door details, mounting arrangement, intended user action and proposed acceptance method.
  • Output: A programme definition, baseline test record, decision and evidence package.
  • Scope: Contactless credential detection. Recognition behavior for fingerprint or face readers requires a different test method.

Define the term before measuring it

The read range definition used in this programme is the controlled distance and presentation zone within which a specified electronic credential is expected to be detected by a specified reader under documented credential, door, mounting and environmental conditions.

This definition decides whether users can present a credential at the intended position, whether the supplier statement can be tested on the actual door, and whether installation meets the written acceptance condition. It does not decide whether the credential is authorized. Record detection and authorization as separate outcomes.

The common confusion is treating one unqualified distance as transferable. A supplier may have measured under a particular credential, reader, door, mounting position and presentation method. When a quotation says RFID read range, ask what was tested. When it says NFC reading distance, ask whether the same credential and reference point apply. Do not carry a value from one SKU into another quotation.

Working labelMeaning in this runbookDo not substitute it with
Read rangeThe agreed detection envelope and presentation zoneA number without test conditions
Credential read distanceDistance from the agreed reference point to the credential when detection is recordedA distance measured from a different point
Reader operating rangeThe broader envelope described by the supplier for the readerNetwork reach or a site acceptance result
Wireless signal rangeThe reach of a communication linkThe distance at which a credential is presented and detected

Step 1 — Classify the range being asked

Before requesting evidence, answer six questions:

  • Credential: Which card, tag, fob or other contactless medium is included, and which physical samples will be used?
  • Purpose: Is the requirement intended to guide a user, define a placement tolerance, or establish a site acceptance boundary?
  • Reference point: From which defined surface is distance measured, and how will the measuring reference be marked on site?
  • Installation: Is the reader surface-mounted, recessed or integrated into the door or frame arrangement?
  • Environment: Which surrounding materials, nearby equipment and door positions can affect the test?
  • Acceptance outcome: What event must be recorded, at which positions, and who accepts the result?

Do not apply this procedure to keypad entry or biometric recognition without changing the test objective. The relevant question then concerns presentation position, recognition behavior and false acceptance or rejection evidence rather than a radio-distance boundary.

Step 2 — Freeze the programme definition

Write the read-range requirement as one sentence inside the procurement specification. Include the intended user action, the credential, the exact reader configuration, the distance reference and the event that proves success.

The specification should also state:

  1. The exact reader and SKU being evaluated.
  2. The credential type and sample identity.
  3. The reference point and test direction.
  4. The credential orientation and permitted presentation zone.
  5. The door position, reader mounting and relevant surroundings.
  6. The required detection event and the acceptance owner’s pass rule.

If the workflow needs both a reliable inner position and an outer limit, define both. If it needs only guidance for users, do not turn that guidance into an unsupported maximum-distance claim.

A quotation should request the same structure. What an RFQ Should Contain: Procurement Version provides the broader document checklist. Site assumptions can be added through an Office Smart Lock Site Survey or a Smart Lock Retrofit Site Survey.

CONFIRM-WITH-SUPPLIER: Confirm on the dated product page for the specific SKU whether a read-range value is stated, which credential and reader were used, the distance reference point and the test conditions.

Step 3 — Establish a controlled baseline

Freeze one baseline before changing any variable. The diagram shows the sequence from programme conditions to an attached acceptance record.

flowchart TD
    A[Set the programme conditions] --> B[Freeze one credential and reader configuration]
    B --> C[Measure the defined presentation positions]
    C --> D[Record detection and authorization separately]
    D --> E{Does the written criterion pass?}
    E -->|No| F[Change one variable and retest]
    F --> C
    E -->|Yes| G[Repeat at the agreed boundary positions]
    G --> H[Attach evidence to the acceptance record]

During door access testing, identify the reader, door, credential and mounting state before each run. Door swing, reader position, nearby materials and the person presenting the credential may be part of the condition rather than incidental details.

VariableRecord before testingWhy it matters
Reader and SKUExact identification and configurationKeeps the result tied to the supplied item
CredentialType, sample identity and conditionPrevents results from being generalized without evidence
GeometryReference point, direction and marked positionsMakes repeated tests comparable
Door and mountingDoor position, frame condition and reader fixingRecords the installed configuration
OutcomeDetection, authorization and reader eventPrevents detection from being mistaken for access
AcceptancePass rule and approving personMakes the decision auditable

CONFIRM-WITH-ACCEPTANCE-OWNER: Confirm the required presentation zone, credential set, door position, recorded event and pass criterion for this project.

Step 4 — Execute the presentation test

Use the same sequence for every position:

  1. Confirm that the reader, door, credential and software state match the baseline record.
  2. Mark the agreed reference point and test positions using the project’s chosen method.
  3. Present the credential with the agreed orientation and user action.
  4. Record whether the reader detected the credential and whether access was separately authorized.
  5. Repeat at each defined position without changing another variable.
  6. Test the agreed boundary condition and note any position that produced an inconsistent result.
  7. Restore the original configuration and attach the completed record to the test package.

Use representative credentials from the defined population rather than relying on one sample. Do not report a result from one position as proof of the entire envelope. If a result changes between repetitions, preserve every observation and move it to the exception path rather than selecting the preferred outcome.

Step 5 — Compare the result with the written criterion

Test outcomeEvidence requiredProcurement action
PassAll required positions met the written criterion and the record identifies the tested configurationApprove the evidence for that configuration
ConditionalThe baseline passed, but a position, credential sample or installation variable was not verifiedHold the requirement and define the missing test
FailThe result did not meet the stated criterion in a required presentation zoneReview placement, configuration or the requirement before acceptance
Not comparableCredential, reference point, reader state, environment or outcome was missingReject the claim as evidence and request a controlled retest

A supplier statement without comparable conditions is not a pass. Conversely, a failed site test does not by itself prove that the supplied unit differs from the documented product. First establish what was tested, then determine whether the issue lies in the product statement, installation, credential or acceptance criterion.

Any model-level distance or acceptance claim must be confirmed on the dated product page for the specific SKU. Keep the dated record, test method and result together so the importer can trace what was approved before the goods are issued to the installation team.

The build-up behind that decision is in smart lock quality inspection china. That is the same question read range definition has to answer here.

Step 6 — Pack and trace the evidence

A usable evidence package contains:

  • The programme read-range definition and acceptance rule.
  • Photographs or drawings showing the reader position and measurement reference.
  • The exact reader and credential references.
  • The dated product-page extract or supplier response, without extending it to another SKU.
  • The completed test log, including failed and repeated presentations.
  • A record of changes made between the baseline and final test.

Supplier verification should cover both the document and the configuration behind it. How a Supplier Is Actually Verified: Diagram Walkthrough provides the wider verification sequence. When reader installation affects the result, review How a Door Is Prepared for a Lock: Plain Explanation before repeating the test.

An importer should retain the evidence package with the purchase and receiving records. This preserves the link between the approved baseline, the supplied configuration and the unit issued to site.

Handle the common exception paths

  • Credential variation: If different samples produce different results, test the defined credential population and revise the evidence request.
  • Mounting changed: If the reader or door moves after baseline testing, treat the original result as historical and repeat the affected positions.
  • Unexplained inconsistency: Preserve the raw observations, identify the last controlled variable and repeat with one change at a time.
  • Competing site needs: A workflow range and a technical maximum are different requirements. Define both rather than forcing one number to serve both.
  • Local project scope: Keep site-specific access-control, radio and fire-door questions separate from the supplier’s product statement.

CONFIRM-WITH-LOCAL-INSTALLER: Confirm on-site radio conditions, door construction, reader mounting and any project-specific access-control or fire-door requirements before the result is accepted.

Hand the requirement into procurement

The quotation and submittal should separate the product statement from the project acceptance condition. Replace an unqualified range entry with a reference to the approved definition, the dated product-page evidence, the intended credential and the test method.

Before issuing the purchase request:

  • Confirm that the requirement identifies the exact reader and SKU.
  • Attach the definition and evidence request to the procurement specification.
  • State which installation variables the supplier must define.
  • Preserve the acceptance owner’s decision rule.
  • Route unresolved site conditions back to the survey rather than treating them as product facts.

For a specific unit or project, use the request-a-quote page to submit the exact configuration and the evidence required. A supplier can then respond to a defined test case instead of repeating an unqualified distance.

Definition card

Working read-range definition: The controlled distance and presentation zone within which a specified electronic credential is expected to be detected by a specified reader under documented credential, door, mounting and environmental conditions.

The commercial consequence is acceptance of the configuration and evidence, not permission to reuse a distance across products. Keep five items together:

  1. The exact reader and SKU.
  2. The credential reference.
  3. The measurement reference point.
  4. The installation and environmental conditions.
  5. The result and acceptance decision.

If any item is missing, label the claim unverified and route it through the relevant confirmation line. That discipline keeps the term useful without presenting a programme working definition as a universal industry standard.

Kosár
A cookie-k engedélyezésével javítható a felhasználói élmény ezen a weboldalon. Cookie-szabályzat
Chat on WhatsApp