The Motor and Gearbox Test Evidence a Buyer Can Actually Request
Use this bid and specification sheet when a system integrator is comparing electronic smart locks and needs motor and gearbox test evidence that can be audited. It separates a durability claim from a repeatable test record: what was tested, how it was loaded, what the instruments measured, and which results were accepted. The same sheet can be attached to a pilot RFQ, a supplier qualification file, or a production release review.
Direct answer. The short answer is that motor and gearbox test evidence is not one decision. It is a sequence. This article takes motor and gearbox test evidence from motor and gearbox test evidence through motor-and-gearbox to the record you keep. A motor and gearbox test evidence describes how one component behaves under load. The datasheet makes claims. motor and gearbox test evidence is what motor and gearbox test evidence can be tested against.
motor and gearbox test evidence is taken here as motor and gearbox test evidence, deliberately narrowly. It is a working definition of motor and gearbox test evidence. It is specific to this market and product, and it is not a statutory or certified term.
- Confirm the feature — confirm on the dated product page for the specific SKU behind motor and gearbox test evidence
- Confirm the constraint — record where the technology in motor-and-gearbox stops working
- Confirm the contingency — name the mechanical path that remains if motor and gearbox test evidence fails
- For motor and gearbox test evidence, the order below is fixed and motor and gearbox is the reference point.
Every populated field should point to a traceable artifact rather than a brochure sentence. For an illustrative retrofit, a supplier may show a long successful cycle claim but cannot demonstrate fit with the actual door set, closing force, latch geometry, and repeated command sequence until the buyer receives the records behind it. The first-party catalogue includes 79 published models, so a generic component statement should never be accepted as proof for the ordered configuration. The response schedule must bind evidence to model, revision, sample identity, and test conditions.
1. Fill-in bidder and configuration schedule
Start by fixing the exact configuration under qualification. Do not leave the motor and gearbox evidence attached only to a family name when the project may include several body, panel, or door-fit variants.
| Bid field | Buyer entry | Evidence attached |
|---|---|---|
| Project or bid reference | [enter] | [enter] |
| Bidder legal name | [enter] | [enter] |
| Offered model and commercial designation | [enter] | Dated product-page copy |
| Hardware revision | [enter] | Revision photograph or drawing |
| Firmware and control-board revision | [enter] | Version record |
| Lock body, spindle, and latch configuration | [enter] | Configuration drawing |
| Intended door type and fit envelope | [enter] | Door-fit test plan |
| Qualification phase | [enter] | [enter] |
| Buyer test owner | [enter] | [enter] |
| Supplier evidence owner | [enter] | [enter] |
| Response date and revision | [enter] | [enter] |
The configuration baseline is the reference for every later result. Record whether the evidence covers the complete lock, the motor and gearbox assembly alone, or a representative bench fixture. Also identify the production release that will ship if the sample passes. A generic “latest model” response is insufficient when the ordered hardware or control firmware differs from the tested sample. The product family this applies to is the smart door locks.
Set exclusions in writing. A supplier may test a narrow spindle range or one latch geometry while offering other options in the catalogue. Those exclusions belong in the deviation register rather than being silently omitted from the response.
2. Mandatory evidence index for the bid
Ask for an evidence index instead of a collection of disconnected reports. Name the folder or file group motor-and-gearbox, then make every attachment traceable through a stable reference.
| Evidence ID | Buyer question | Required content | Acceptable format |
|---|---|---|---|
| EQ-01 | What exactly was tested? | Model, revision, sample identity, build state and component configuration | Configuration record |
| EQ-02 | How were the methods selected? | Test purpose, fixture, load, instrumentation and calculation method | Approved test plan |
| EQ-03 | How were samples allocated? | Sampling rule, sample classes and exclusions | Sample schedule |
| EQ-04 | What was observed? | Raw readings, event sequence, calculated results and exceptions | Native data plus report |
| EQ-05 | Can the measurements be trusted? | Instrument identity, calibration traceability and uncertainty treatment | Calibration records |
| EQ-06 | What happened after a failure? | Failure analysis, disassembly record and proposed corrective action | Failure report |
| EQ-07 | What changed after testing? | Change notices, revision impacts and retest scope | Change-control log |
| EQ-08 | Does the sample represent production? | Production-equivalence statement and release identifier | Signed record |
The index should state which requirement each report satisfies. A table of results without the associated setup, sample identity, and raw file cannot be independently interpreted. Conversely, the buyer does not need every irrelevant internal document; it needs the records needed to reproduce a decision.
Use Reading the Motor and Gearbox Claims in a Supplier Datasheet as the desk-review companion. That article addresses the gap between a written claim and a test record; this bid schedule defines the record the bidder must provide.
3. Qualification gates from desk review to release
Treat qualification as a sequence of gates. Each gate has an owner, an entry condition, and a defined record. A failure does not automatically end the process, but it cannot be cleared without documented corrective action and an approved retest scope.
flowchart TD
A["Complete bidder and configuration schedule"] --> B["Review the evidence index"]
B --> C["Approve methods and acceptance rules"]
C --> D["Receive controlled samples"]
D --> E["Run motor gearbox and lock cycle tests"]
E --> F["Review raw data and failures"]
F --> G{"Mandatory gates passed"}
G -->|Yes| H["Release qualification record"]
G -->|No| I["Open deviation and corrective action"]
I --> C
At the desk-review gate, confirm that the bidder understands the requested operating envelope and can map its proposed tests to the offered configuration. At the method gate, approve the fixture, load definition, measurement positions, pass rules and report format before physical testing begins. At the sample gate, verify that the delivered hardware matches the bid schedule.
The final gate is a buyer decision, not an automatic result of the supplier’s report. Confirm the evidence package, open deviations, proposed corrections and any restricted coverage. For an illustrative pilot, the released sample may be used for installation trials, but pilot use should not be represented as full production qualification unless the configuration and test coverage meet the agreed scope.
4. Smart lock motor testing schedule
Smart lock motor testing should reveal how the motor behaves during a commanded movement under a defined door and latch load. Request a synchronized record of command, current, motion and any detected fault. The buyer must set acceptable limits before seeing the results.
| Test ID | Test method | Measurements and observations | Buyer acceptance field |
|---|---|---|---|
| MT-01 | Running-current profile | Command timing, current trace, motion state and fault flags | [enter limit and rule] |
| MT-02 | Commanded movement under load | Travel time, current demand, stall indication and final position | [enter] |
| MT-03 | Output-load response | Applied load, response, current change and recovery after load removal | [enter] |
| MT-04 | Thermal response | Motor or gearbox temperature over the approved duty sequence | [enter] |
| MT-05 | Direction and end-of-travel response | Direction confirmation, travel limit behaviour and unintended reversal | [enter] |
| MT-06 | Power-interruption response | Controller behaviour, stored state and next permitted command | [enter] |
| MT-07 | Post-test functional inspection | Movement, fastening, retraction and fault reporting after the test sequence | [enter] |
The test plan must define where current is measured, how the load is applied and how the reference point for motion is established. “Motor works normally” is not an acceptance rule. A usable criterion states the permitted current band, commanded-position result, permitted timing range and required behaviour under interruption, with the values supplied by the buyer.
MT-02 should use a fixture that represents an approved door-fit condition rather than an unloaded motor mounted outside the lock. If the supplier cannot reproduce the intended latch or bolt load, the report must identify that limitation. The result may still be useful as component evidence, but it cannot close the integrated lock qualification.
5. Gearbox durability evidence schedule
Gearbox durability evidence must connect output behaviour, wear observations and the conditions that produced them. Backlash, output force, retained position and internal condition should be recorded before and after the agreed duty sequence.
| Test ID | Test method | Evidence required | Buyer acceptance field |
|---|---|---|---|
| GB-01 | Initial visual and dimensional baseline | Housing, gear, shaft, lubricant and mounting condition | [enter] |
| GB-02 | Backlash measurement | Measurement position, method, instrument and repeated readings | [enter] |
| GB-03 | Output-force response | Applied output load, travel, hold behaviour and release response | [enter] |
| GB-04 | Reversal and retention check | Direction changes, retained position and unexpected movement | [enter] |
| GB-05 | Post-cycle backlash comparison | Before-and-after readings and uncertainty treatment | [enter] |
| GB-06 | Internal inspection after duty | Debris, wear marks, lubricant condition and photographs | [enter] |
| GB-07 | Function check after inspection | Remanufacture, reassembly or teardown effects on operation | [enter] |
The buyer should define whether backlash means lost motion at the motor coupling, output shaft or final latch drive. Without that definition, two suppliers can report different quantities while both using the same word. The test record must also state the measurement direction, applied position and number of repetitions.
Use The Motor and Gearbox Trade-Offs: Cost, Durability and Service when reviewing why a proposed gearbox option may carry a different cost or service burden. The present sheet does not award a technical score for one design preference; it asks whether the bidder can show how its selected gearbox behaves under the buyer-defined conditions.
6. Lock cycle testing inside the approved door fit test plan
The motor and gearbox operate inside a door system. A door fit test plan must therefore connect component movement to the latch or bolt, strike, frame, spindle, door closer and access-control command. Lock cycle testing covers the complete commanded movement rather than only the electrical signature of the motor.
| Fit condition | Test action | Required record | Buyer acceptance field |
|---|---|---|---|
| Door leaf and rebate | Install and operate the lock in each representative door | Dimensions, template fit and installation notes | [enter] |
| Backset and spindle alignment | Cycle from the installed position | Interference points and alignment measurements | [enter] |
| Latch or bolt travel | Observe the complete stroke against the strike | Travel, final position and contact evidence | [enter] |
| Strike and keeper contact | Repeat operation under normal alignment | Contact patch, frame movement and bolt seating | [enter] |
| Door closer interaction | Operate with the intended closer setup | Applied resistance, current trace and movement result | [enter] |
| Frame alignment over repeated use | Repeat cycles and inspect for cumulative shift | Before-and-after geometry and defect record | [enter] |
| Access-control command | Authenticate, command and complete each movement | Event sequence, motor response and final door state | [enter] |
Use actual or representative door sets selected from the project boundary. Cover the tightest approved fit, the intended operating condition and any configuration the bidder has not tested. An Office Smart Lock Site Survey or Smart Lock Retrofit Site Survey can supply the field measurements that define the fit plan.
The door-fit envelope has its own qualification logic. The Motor and Gearbox and Door Compatibility: The Fit Envelope is useful for separating a hardware mismatch from a motor or gearbox failure. In this sheet, any installed-cycle anomaly must be recorded against both the component trace and the door geometry.
7. Failure injection and recovery protocol
Ask the supplier to show how the assembly behaves when movement is interrupted, the load becomes excessive or power is removed at a defined point. Use protected fixtures and buyer-approved limits. The purpose is not to create an uncontrolled hazard; it is to reproduce a defined interruption and document the response.
| Test ID | Condition | Evidence required | Recovery acceptance field |
|---|---|---|---|
| FI-01 | Obstruction before completed travel | Command trace, current trace, position and fault output | [enter] |
| FI-02 | Obstruction after initial movement | Motion sequence, load response and attempt termination | [enter] |
| FI-03 | Power removed during movement | Electrical state, stored position and restart behaviour | [enter] |
| FI-04 | Repeated command during an active cycle | Controller response and duplicate movement record | [enter] |
| FI-05 | Load beyond the approved operating band | Protection response and post-test condition | [enter] |
| FI-06 | Reset after an interrupted cycle | Restart command, door state and event record | [enter] |
The failure analysis protocol should preserve the failed sample, identify the interruption point and show the teardown sequence. Supplier qualification evidence is stronger when the report includes what was observed, how the cause was isolated and which corrective action was retested. “Intermittent” or “mechanical issue” is not a sufficient root-cause record.
The Motor and Gearbox Failure Modes Seen on Smart Lock Projects provides a separate comparison of failure patterns. Use that comparison to structure the supplier’s explanation, while keeping the bid decision focused on whether the proposed method and records support the claimed qualification.
8. Sample selection and configuration control
The number of samples should follow the risk, variability and production plan. Do not accept an unspecified “several samples” statement. Define sample classes, selection method and the role each sample plays in the test sequence.
| Sample class | Purpose | Minimum record | Buyer rule |
|---|---|---|---|
| Configuration sample | Confirms the exact build under review | Photographs, revision and serial identifiers | [enter] |
| Initial test sample | Provides the pre-test baseline | Setup and calibration records | [enter] |
| Repeated-use samples | Reveal variation across units | Unit-level results and anomalies | [enter] |
| Worst-fit sample | Checks the approved boundary condition | Door and load configuration | [enter] |
| Change sample | Confirms a proposed substitution or revision | Before-and-after configuration | [enter] |
Record component substitutions, firmware changes, tooling changes and supplier changes that occur after qualification. A modification should trigger a documented impact review. The buyer then chooses whether existing evidence remains applicable or a focused retest is required.
Configuration control also applies to test fixtures. A fixture change can alter load direction, stiffness or travel and invalidate comparison with earlier samples. Record the fixture revision alongside each run and preserve the setup used for the referenced result.
9. Raw-data package and report schema
A report may summarize the qualification, but it cannot replace the source data needed to inspect the result. Require native files where available and a human-readable report that maps each conclusion to the relevant run.
| Data element | Required content | Example format |
|---|---|---|
| Run index | Unique reference used in the report | Numbered index |
| Sample and fixture identity | Hardware revision, sample identifier and fixture revision | Data table |
| Setup record | Door, load, instrument and connection details | Form plus photographs |
| Raw time series | Current, motion, command, fault and time-base records | Native data file |
| Processed results | Calculations, summaries, plots and comparison with limits | Report and spreadsheet |
| Exceptions | Interrupted runs, invalid channels and operator notes | Exception log |
| Calibration traceability | Instrument identity, status and relevant measurement uncertainty | Controlled record |
| Images and video | Failure appearance, disassembly and final condition | Controlled media folder |
Files should retain their native structure and use a naming convention that connects them to the run index. Any conversion, filtering or calculation must be disclosed. A smooth plotted line is useful for review, but the raw observations are needed to determine whether the curve supports it.
The supplier qualification evidence package should include the test plan, approved deviations, raw data, processed report, failure records and configuration records under one index. The buyer can then trace any pass decision back to the measurement, setup and sample that produced it.
10. Motor and gearbox test evidence acceptance matrix
The motor and gearbox test evidence acceptance matrix converts the bid into a decision. The weighting below is an editable example for a system integrator, not a universal benchmark. Mandatory evidence and critical functional gates remain separate from the weighted score.
| Criterion | Example weight | Pass evidence | Decision effect |
|---|---|---|---|
| Configuration and sample traceability | 15 | Exact build identity linked to every result | Mandatory |
| Test-method suitability and instrument records | 10 | Approved method, setup and calibration traceability | Mandatory |
| Nominal command and door-fit performance | 20 | Complete movement within approved fit envelope | Major |
| Load, thermal and duty response | 20 | Results within approved operating limits | Major |
| Failure recovery and diagnostic record | 10 | Defined response supported by trace and analysis | Major |
| Raw-data completeness and traceability | 15 | Reproducible data linked to the report | Major |
| Change-control and deviation handling | 10 | Written impact assessment and disposition | Mandatory |
| Total | 100 | Buyer-completed evaluation | — |
Apply the rules in this order:
- Missing mandatory evidence produces a conditional or failed qualification, regardless of the weighted score.
- A failed critical function cannot be offset by strengths elsewhere in the matrix.
- A conditional result must name the restriction, corrective action, owner and retest scope.
- A pass applies only to the configuration, revision and operating envelope recorded in the evidence package.
The bidder may propose different weights before testing begins, but the buyer should approve them with the test method. Changing the weighting after unfavorable results would make the comparison unreliable.
11. Bidder deviation and clarification register
Require every departure from the requested method or acceptance rule to appear in one register. A short response such as “available on request” is a deviation from an evidence requirement and should be evaluated as such.
| Requirement | Bidder status | Evidence reference | Deviation and impact | Proposed resolution | Owner and date |
|---|---|---|---|---|---|
| [enter ID] | Comply, deviate, partial or not included | [enter] | [enter] | [enter] | [enter] |
| [enter ID] | [enter] | [enter] | [enter] | [enter] | [enter] |
| [enter ID] | [enter] | [enter] | [enter] | [enter] | [enter] |
| [enter ID] | [enter] | [enter] | [enter] | [enter] | [enter] |
Attach the approved method and acceptance rule to each response line. When the bidder proposes an alternative, ask how it preserves the buyer’s measurement question. A cheaper or faster method is not automatically equivalent, and the bidder should not substitute it without written agreement.
Clarifications should preserve the version history. Record the question, the supplier response, the buyer decision and the affected report. If a clarification changes the test method, identify every run and conclusion affected by that change.
12. Qualification sign-off and next-stage release
The release record states what has been qualified and what remains outside scope. It is more useful than a general statement that a model has been approved, especially when a project uses several door or hardware variants.
| Sign-off field | Buyer entry |
|---|---|
| Qualified model and revision | [enter] |
| Hardware and firmware baseline | [enter] |
| Qualified door-fit envelope | [enter] |
| Approved duty and load conditions | [enter] |
| Evidence index reference | [enter] |
| Accepted deviations and restrictions | [enter] |
| Retest triggers and change owners | [enter] |
| Buyer approver | [enter] |
| Approval date and record revision | [enter] |
A qualification should remain linked to the tested configuration. If the bidder changes the motor, gearbox, controller, spindle, latch drive or related software, the buyer should apply the agreed retest trigger. The exact trigger depends on the change and the approved qualification record; a generic statement that the product is unchanged is not enough.
Before releasing the result, verify that the final report and raw data use the same sample and revision identifiers. Resolve missing attachments, unexplained failed runs and open deviations. Record any restriction directly on the release sheet so it travels with later quotations, purchase orders and project handovers.
13. Buyer request package and commercial handoff
Send the completed schedule with the RFQ and request the following in one indexed response:
- Completed bidder and configuration schedule
- Signed evidence index
- Proposed test methods and acceptance rules
- Sample and configuration-control plan
- Raw-data and report template
- Failure-analysis and change-control procedures
- Deviations, exclusions and retest proposal
For a catalogue-led project, request the current catalogue and then bind each offered configuration to its evidence package. Buyers can request a catalog for the commercial scope and request a quote with this qualification sheet attached, so the technical response and the proposed supply configuration remain aligned.
The same question is worked through in more detail in smart lock cost vs access control. That is the same question motor and gearbox test evidence has to answer here.The practical purpose of the sheet is simple: it lets the system integrator ask for evidence that can be opened, traced and challenged before the motor and gearbox are accepted for the project. A completed response gives the buyer more than a longevity statement. It provides a defensible basis for sample approval, pilot use, configuration control and the next production decision.

